+.. _opnfv-overview:
+
.. This work is licensed under a Creative Commons Attribution 4.0 International License.
-.. http://creativecommons.org/licenses/by/4.0
+.. SPDX-License-Identifier: CC-BY-4.0
.. (c) Open Platform for NFV Project, Inc. and its contributors
===============
============
Network Functions Virtualization (NFV) is transforming the networking industry via
-software-defined infrastructures and open source is the proven method for developing
-software quickly for commercial products and services that can move markets.
+software-defined infrastructures and open source is the proven method for quickly developing
+software for commercial products and services that can move markets.
Open Platform for NFV (OPNFV) facilitates the development and evolution of NFV
components across various open source ecosystems. Through system level integration,
deployment and testing, OPNFV constructs a reference NFV platform to accelerate the
transformation of enterprise and service provider networks.
As an open source project, OPNFV is uniquely positioned to bring together the work
-of standards bodies, open source communities, and commercial suppliers to deliver a
-de facto NFV platform for the industry.
+of standards bodies, open source communities, service providers and commercial suppliers to deliver
+a de facto NFV platform for the industry.
By integrating components from upstream projects, the community is able to conduct performance
and use case-based testing on a variety of solutions to ensure the platform’s suitability for
-NFV use cases. OPNFV also works upstream with other open source communities to bring both contributions
-and learnings from its work directly to those communities in the form of blueprints, patches,
+NFV use cases. OPNFV also works upstream with other open source communities to bring contributions
+and learnings from its work directly to those communities in the form of blueprints, patches, bugs,
and new code.
OPNFV initially focused on building NFV Infrastructure (NFVI) and Virtualised Infrastructure
Management (VIM) by integrating components from upstream projects such as OpenDaylight,
OpenStack, Ceph Storage, KVM, Open vSwitch, and Linux.
More recently, OPNFV has extended its portfolio of forwarding solutions to include fd.io and ODP,
-is able to run on both Intel and ARM commercial and white-box hardware, and includes
-Management and Network Orchestration MANO components primarily for application composition
-and management in the Colorado release.
+is able to run on both Intel and ARM commercial and white-box hardware, support VM, Container and
+BareMetal workloads, and includes Management and Network Orchestration MANO components primarily
+for application composition and management in the Danube release.
These capabilities, along with application programmable interfaces (APIs) to other NFV
elements, form the basic infrastructure required for Virtualized Network Functions (VNF)
The infrastructure working group oversees such topics as lab management, workflow,
definitions, metrics and tools for OPNFV infrastructure.
-Fundamental to the WG is the `Pharos Project <https://www.opnfv.org/developers/pharos>`_
+Fundamental to the WG is the
+`Pharos Specification <https://wiki.opnfv.org/display/pharos/Pharos+Specification>`_
which provides a set of defined lab infrastructures over a geographically and technically
diverse federated global OPNFV lab.
composition may vary depending on the installer and scenario.
For details on the scenarios available in OPNFV and the specific composition of components
-refer to the OPNFV installation instruction:
-http://artifacts.opnfv.org/opnfvdocs/colorado/2.0/docs/installationprocedure/index.html
+refer to the :ref:'OPNFV User Guide & Configuration Guide <opnfv-user-config>'
-----------------
Operating Systems
configuration including control plane components from OpenStack, SDN, etc. and a minimum
of two compute nodes for deployment of workloads (VNFs).
A detailed description of the hardware requirements required to support the 5 node configuration
-can be found in pharos specification: http://artifacts.opnfv.org/pharos/colorado/2.0/docs/specification/index.html
+can be found in pharos specification: `Pharos Project <https://www.opnfv.org/developers/pharos>`_
In addition to the deployment on a highly available physical infrastructure, OPNFV can be
deployed for development and lab purposes in a virtual environment. In this case each of the hosts
The initial deployment is done using a staging server, referred to as the "jumphost".
This server-either physical or virtual-is first installed with the installation program
that then installs OpenStack and other components on the controller nodes and compute nodes.
-See the `OPNFV User Guide`_ for more details.
+See the :ref:'OPNFV User Guide & Configuration Guide <opnfv-user-config>' for more details.
The OPNFV Testing Ecosystem
each run as shown in the following diagram.
.. image:: ../images/OPNFV_testing_group.png
- :alt: Overview infographic of the Colorado OPNFV testing Ecosystem
+ :alt: Overview infographic of the OPNFV testing Ecosystem
Release Verification
====================
platform system and performance test project ‘yardstick,’ and a selection of test cases for
feature capabilities derived from other test projects such as bottlenecks, vsperf, cperf and
storperf. The scenario needs to be able to be deployed, pass these tests, and be removed from
-the infrastructure iteratively (no less that 4 times) in order to fulfill the release criteria.
+the infrastructure iteratively (no less that 4 times) in order to fulfil the release criteria.
--------
Functest
The Dovetail project will provide a test framework and methodology able to be used on any NFV platform,
including an agreed set of test cases establishing an evaluation criteria for exercising
an OPNFV compatible system. The Dovetail project has begun establishing the test framework
-and will provide a preliminary methodology for the Colorado release. Work will continue to
+and will provide a preliminary methodology for the Danube release. Work will continue to
develop these test cases to establish a stand alone compliance evaluation solution
in future releases.
VSPERF
------
-VSPERF provides a generic and architecture agnostic vSwitch testing framework and associated tests.
-This serves as a basis for validating the suitability of different vSwitch implementations and deployments.
+VSPERF provides an automated test-framework and comprehensive test suite for measuring data-plane
+performance of the NFVI including switching technology, physical and virtual network interfaces.
+The provided test cases with network topologies can be customized while also allowing individual
+versions of Operating System, vSwitch and hypervisor to be specified.
-----------
Bottlenecks
root cause isolation capabilities to facilitate system evaluation.
-.. _`OPNFV Configuration Guide`: http://artifacts.opnfv.org/opnfvdocs/colorado/2.0/docs/configguide
-.. _`OPNFV User Guide`: http://artifacts.opnfv.org/opnfvdocs/colorado/2.0/docs/userguide
+.. _`OPNFV Configuration Guide`: `OPNFV User Guide & Configuration Guide`
+.. _`OPNFV User Guide`: `OPNFV User Guide & Configuration Guide`
.. _`Dovetail project`: https://wiki.opnfv.org/display/dovetail
Code Review / opnfvdocs.git / blobdiff