3 .. This work is licensed under a Creative Commons Attribution 4.0 International License.
4 .. SPDX-License-Identifier: CC-BY-4.0
5 .. (c) Open Platform for NFV Project, Inc. and its contributors
14 Network Functions Virtualization (NFV) is transforming the networking industry via
15 software-defined infrastructures and open source is the proven method for quickly developing
16 software for commercial products and services that can move markets.
17 Open Platform for NFV (OPNFV) facilitates the development and evolution of NFV
18 components across various open source ecosystems. Through system level integration,
19 deployment and testing, OPNFV constructs a reference NFV platform to accelerate the
20 transformation of enterprise and service provider networks.
21 As an open source project, OPNFV is uniquely positioned to bring together the work
22 of standards bodies, open source communities, service providers and commercial suppliers to deliver
23 a de facto NFV platform for the industry.
25 By integrating components from upstream projects, the community is able to conduct performance
26 and use case-based testing on a variety of solutions to ensure the platform’s suitability for
27 NFV use cases. OPNFV also works upstream with other open source communities to bring contributions
28 and learnings from its work directly to those communities in the form of blueprints, patches, bugs,
31 OPNFV focuses on building NFV Infrastructure (NFVI) and Virtualised Infrastructure
32 Management (VIM) by integrating components from upstream projects such as OpenDaylight, ONOS, Tungsen Fabric,
33 OVN, OpenStack, Kubernetes, Ceph Storage, KVM, Open vSwitch, and Linux.
34 More recently, OPNFV has extended its portfolio of forwarding solutions to include DPDK, fd.io and ODP,
35 is able to run on both Intel and ARM commercial and white-box hardware, support VM, Container and
36 BareMetal workloads, and includes Management and Network Orchestration MANO components primarily
37 for application composition and management in the Fraser release.
39 These capabilities, along with application programmable interfaces (APIs) to other NFV
40 elements, form the basic infrastructure required for Virtualized Network Functions (VNF)
43 Concentrating on these components while also considering proposed projects on additional
44 topics (such as the MANO components and applications themselves), OPNFV aims to enhance
45 NFV services by increasing performance and power efficiency improving reliability,
46 availability and serviceability, and delivering comprehensive platform instrumentation.
49 OPNFV Platform Architecture
50 ===========================
52 The OPNFV project addresses a number of aspects in the development of a consistent virtualisation
53 platform including common hardware requirements, software architecture, MANO and applications.
56 OPNFV Platform Overview Diagram
58 .. image:: ../images/diagram_fraser.png
59 :alt: Overview infographic of the opnfv platform and projects.
62 To address these areas effectively, the OPNFV platform architecture can be decomposed
63 into the following basic building blocks:
65 * Hardware: Infrastructure working group, Pharos project and associated activities
66 * Software Platform: Platform integration and deployment projects
67 * MANO: MANO working group and associated projects
68 * Tooling and testing: Testing working group and test projects
69 * Applications: All other areas and drive requirements for OPNFV
71 OPNFV Lab Infrastructure
72 ========================
74 The infrastructure working group oversees such topics as lab management, workflow,
75 definitions, metrics and tools for OPNFV infrastructure.
77 Fundamental to the WG is the
78 `Pharos Specification <https://wiki.opnfv.org/display/pharos/Pharos+Specification>`_
79 which provides a set of defined lab infrastructures over a geographically and technically
80 diverse federated global OPNFV lab.
82 Labs may instantiate bare-metal and virtual environments that are accessed remotely by the
83 community and used for OPNFV platform and feature development, build, deploy and testing.
84 No two labs are the same and the heterogeneity of the Pharos environment provides the ideal
85 platform for establishing hardware and software abstractions providing well understood
86 performance characteristics.
88 Community labs are hosted by OPNFV member companies on a voluntary basis.
89 The Linux Foundation also hosts an OPNFV lab that provides centralized CI
90 and other production resources which are linked to community labs.
92 The Lab-as-a-service (LaaS) offering provides developers to readily access NFV infrastructure on demand.
93 Ongoing lab capabilities will include the ability easily automate deploy and test of any OPNFV install
94 scenario in any lab environment using a concept called “Dynamic CI”.
96 OPNFV Software Platform Architecture
97 ====================================
99 The OPNFV software platform is comprised exclusively of open source implementations of
100 platform component pieces. OPNFV is able to draw from the rich ecosystem of NFV related
101 technologies available in open source communities, and then integrate, test, measure and improve these
102 components in conjunction with our upstream communities.
104 ---------------------------------
105 Virtual Infrastructure Management
106 ---------------------------------
108 OPNFV derives it's virtual infrastructure management from one of our largest upstream ecosystems
109 OpenStack. OpenStack provides a complete reference cloud management system and associated technologies.
110 While the OpenStack community sustains a broad set of projects, not all technologies are relevant in
111 the NFV domain, the OPNFV community consumes a sub-set of OpenStack projects and the usage and
112 composition may vary depending on the installer and scenario.
114 For details on the scenarios available in OPNFV and the specific composition of components
115 refer to the :ref:`OPNFV User Guide & Configuration Guide <opnfv-user-config>`.
117 OPNFV now also has initial support for containerized VNFs.
123 OPNFV currently uses Linux on all target machines, this can include Ubuntu, Centos or SUSE Linux. The
124 specific version of Linux used for any deployment is documented in the installation guide.
126 Networking Technologies
127 =======================
132 OPNFV, as an NFV focused project, has a significant investment on networking technologies
133 and provides a broad variety of integrated open source reference solutions. The diversity
134 of controllers able to be used in OPNFV is supported by a similarly diverse set of
135 forwarding technologies.
137 There are many SDN controllers available today relevant to virtual environments
138 where the OPNFV community supports and contributes to a number of these. The controllers
139 being worked on by the community during this release of OPNFV include:
141 * Neutron: an OpenStack project to provide “network connectivity as a service” between
142 interface devices (e.g., vNICs) managed by other OpenStack services (e.g. Nova).
143 * OpenDaylight: addresses multivendor, traditional and greenfield networks, establishing the
144 industry’s de facto SDN platform and providing the foundation for networks of the future.
145 * Tungsen Fabric: An open source SDN controller designed for cloud and NFV use cases. It has an
146 analytics engine, well defined northbound REST APIs to configure and gather ops/analytics data.
147 * OVN: A virtual networking solution developed by the same team that created OVS. OVN stands for
148 Open Virtual Networking and is dissimilar from the above projects in that it focuses only on overlay networks.
153 OPNFV extends Linux virtual networking capabilities by using virtual switching
154 and routing components. The OPNFV community proactively engages with the following open source
155 communities to address performance, scale and resiliency needs apparent in carrier
158 * OVS (Open vSwitch): a production quality, multilayer virtual switch designed to enable massive
159 network automation through programmatic extension, while still supporting standard management interfaces and protocols.
160 * FD.io (Fast data - Input/Output): a high performance alternative to Open vSwitch, the core engine of
161 FD.io is a vector processing engine (VPP). VPP processes a number of packets in parallel instead of one at
162 a time thus significantly improving packet throughput.
163 * DPDK: a set of libraries that bypass the kernel and provide polling mechanisms, instead of interrupt based operations,
164 to speed up packet processing. DPDK works with both OVS and FD.io.
169 OPNFV integrates open source MANO projects for NFV orchestration and VNF management. New MANO projects are constantly being added.
171 Deployment Architecture
172 =======================
174 A typical OPNFV deployment starts with three controller nodes running in a high availability
175 configuration including control plane components from OpenStack, SDN controllers, etc. and a minimum
176 of two compute nodes for deployment of workloads (VNFs).
177 A detailed description of the hardware requirements required to support the 5 node configuration
178 can be found in pharos specification: `Pharos Project <https://www.opnfv.org/developers/pharos>`_
180 In addition to the deployment on a highly available physical infrastructure, OPNFV can be
181 deployed for development and lab purposes in a virtual environment. In this case each of the hosts
182 is provided by a virtual machine and allows control and workload placement using nested virtualization.
184 The initial deployment is done using a staging server, referred to as the "jumphost".
185 This server-either physical or virtual-is first installed with the installation program
186 that then installs OpenStack and other components on the controller nodes and compute nodes.
187 See the :ref:`OPNFV User Guide & Configuration Guide <opnfv-user-config>` for more details.
190 The OPNFV Testing Ecosystem
191 ===========================
193 The OPNFV community has set out to address the needs of virtualization in the carrier
194 network and as such platform validation and measurements are a cornerstone to the
195 iterative releases and objectives.
197 To simplify the complex task of feature, component and platform validation and characterization
198 the testing community has established a fully automated method for addressing all key areas of
199 platform validation. This required the integration of a variety of testing frameworks in our CI
200 systems, real time and automated analysis of results, storage and publication of key facts for
201 each run as shown in the following diagram.
203 .. image:: ../images/OPNFV_testing_working_group.png
204 :alt: Overview infographic of the OPNFV testing Ecosystem
209 The OPNFV community relies on its testing community to establish release criteria for each OPNFV
210 release. With each release cycle the testing criteria become more stringent and better representative
211 of our feature and resiliency requirements. Each release establishes a set of deployment scenarios to validate,
212 the testing infrastructure and test suites need to accommodate these features and capabilities.
214 The release criteria as established by the testing teams include passing a set of test cases
215 derived from the functional testing project ‘functest,’ a set of test cases derived from our
216 platform system and performance test project ‘yardstick,’ and a selection of test cases for
217 feature capabilities derived from other test projects such as bottlenecks, vsperf, cperf and
218 storperf. The scenario needs to be able to be deployed, pass these tests, and be removed from
219 the infrastructure iteratively in order to fulfill the release criteria.
224 Functest provides a functional testing framework incorporating a number of test suites
225 and test cases that test and verify OPNFV platform functionality.
226 The scope of Functest and relevant test cases can be found in the :ref:`Functest User Guide <functest-userguide>`
228 Functest provides both feature project and component test suite integration, leveraging
229 OpenStack and SDN controllers testing frameworks to verify the key components of the OPNFV
230 platform are running successfully.
235 Yardstick is a testing project for verifying the infrastructure compliance when running VNF applications.
236 Yardstick benchmarks a number of characteristics and performance vectors on the infrastructure making it
237 a valuable pre-deployment NFVI testing tools.
239 Yardstick provides a flexible testing framework for launching other OPNFV testing projects.
241 There are two types of test cases in Yardstick:
243 * Yardstick generic test cases and OPNFV feature test cases;
244 including basic characteristics benchmarking in compute/storage/network area.
245 * OPNFV feature test cases include basic telecom feature testing from OPNFV projects;
246 for example nfv-kvm, sfc, ipv6, Parser, Availability and SDN VPN
248 System Evaluation and compliance testing
249 ========================================
251 The OPNFV community is developing a set of test suites intended to evaluate a set of reference
252 behaviors and capabilities for NFV systems developed externally from the OPNFV ecosystem to
253 evaluate and measure their ability to provide the features and capabilities developed in the
256 The Dovetail project will provide a test framework and methodology able to be used on any NFV platform,
257 including an agreed set of test cases establishing an evaluation criteria for exercising
258 an OPNFV compatible system. The Dovetail project has begun establishing the test framework
259 and will provide a preliminary methodology for the Fraser release. Work will continue to
260 develop these test cases to establish a stand alone compliance evaluation solution
266 Besides the test suites and cases for release verification, additional testing is performed to validate
267 specific features or characteristics of the OPNFV platform.
268 These testing framework and test cases may include some specific needs; such as extended measurements,
269 additional testing stimuli, or tests simulating environmental disturbances or failures.
271 These additional testing activities provide a more complete evaluation of the OPNFV platform.
272 Some of the projects focused on these testing areas include:
277 Bottlenecks provides a framework to find system limitations and bottlenecks, providing
278 root cause isolation capabilities to facilitate system evaluation.
283 NFVbench is a lightweight end-to-end dataplane benchmarking framework project.
284 It includes traffic generator(s) and measures a number of packet performance related metrics.
289 QTIP boils down NFVI compute and storage performance into one single metric for easy comparison.
290 QTIP crunches these numbers based on five different categories of compute metrics and relies on
291 Storperf for storage metrics.
296 Storperf measures the performance of external block storage. The goal of this project is
297 to provide a report based on SNIA’s (Storage Networking Industry Association) Performance Test Specification.
302 VSPERF provides an automated test-framework and comprehensive test suite for measuring data-plane
303 performance of the NFVI including switching technology, physical and virtual network interfaces.
304 The provided test cases with network topologies can be customized while also allowing individual
305 versions of Operating System, vSwitch and hypervisor to be specified.
310 .. _`OPNFV Configuration Guide`: `OPNFV User Guide & Configuration Guide`
311 .. _`OPNFV User Guide`: `OPNFV User Guide & Configuration Guide`
312 .. _`Dovetail project`: https://wiki.opnfv.org/display/dovetail
Code Review / opnfvdocs.git / blob