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. Goals include accelerating time to market for NFV solutions, ensuring the platform meets the industry’s needs, and enabling end user choice in specific technology components based on their use cases and deployment architectures.

OPNFV Platform Overview

OPNFV Diagram
As a testing and integration project, OPNFV brings together upstream components across compute, storage and network virtualization in order create an end-to-end platform. Activities within OPNFV focus on integration of components and automated build and deployment of the integrated environment. Continuous integration and automated testing of the platform for key NFV use cases is key to ensure that the platform meets NFV industry needs. Another key focus is refining new requirements and features necessary to the platform and working closely with upstream communities to incorporate these capabilities within their code bases.

Colorado Release

The third release of OPNFV is Colorado, which builds on the foundation laid by the Arno and Brahmaputra releases to improve the underlying platform support for NFV applications as well as to set the stage for improved application on-boarding and management. Learn about Colorado.

Use Cases

Virtual network functions range from mobile deployments, where mobile gateways (e.g. SGW, PGW, etc.) and related functions (e.g. MME, HLR, PCRF, etc.) are deployed as VNFs, to deployments with “virtual” customer premise equipment (CPE), tunneling gateways (e.g. VPN gateways), firewalls or application level gateways and filters (e.g. web and email traffic filters) to test and diagnostic equipment (e.g. SLA monitoring).

These VNF deployments need to be easy to operate, scale, and evolve – independently from the type of VNF being deployed. OPNFV is a flexible platform, which can support a set of qualities and use-cases such as the following:

  • The common mechanism for life-cycle management of VNFs, which include deployment, instantiation, configuration, start and stop, upgrade/downgrade and final decommissioning.
  • The consistent mechanism for specifying and interconnecting VNFs, VNFCs and PNFs; agnostic of the physical network infrastructure, network overlays, etc., i.e., virtual link.
  • The common mechanism for dynamically instantiating new VNF instances or decommissioning sufficient VNF instances to meet the current performance, scale and network bandwidth needs.
  • The mechanism for detecting faults and failure in the NFVI, VIM and other components of the infrastructure and recovering from those failures.
  • The mechanism for sourcing/sinking traffic from/to a physical network function to/from a virtual network function.
  • NFVI as a Service for hosting different VNF instances from different vendors on the same infrastructure

See the white paper: Virtualizing Customer Premises with Service Function Chaining: How OpenDaylight and OPNFV Members Implement NFV’s Top Use Cases

Pharos Community Labs

A key part of OPNFV is the Pharos Community Labs project [insert link to new Pharos page] as well as the OPNFV bare metal lab infrastructure hosted by the Linux Foundation. Pharos is a federated NFV test lab capability that is geographically and technically diverse. It enables the deployment and testing of OPNFV builds on a variety of different hardware environments and helps ensure that OPNFV is not tied to one particular hardware architecture or vendor. Pharos compliant labs are also used in the creation and testing of each OPNFV software releases. Learn more about Pharos.

Upstream Projects

OPNFV integrates components from upstream projects [insert link to upstream projects page], such as OpenStack [insert link to OpenStack page], OpenDaylight [insert link to OpenDaylight page], FD.io [insert link to FD.io page], ONOS, OpenContrail, OVS, Open-O,Ceph, DPDK, ODP, OpenBaton, KVM, and the Linux kernel community. OPNFV will continue working with these and other relevant upstream communities for future releases.

OPNFV has an “upstream first” philosophy. We do not look to fork upstream projects or create OPNFV specific versions of these projects. When, through our requirements projects or our testing activities, we discover gaps, desired features, or bugs; we will participate in the appropriate community process of the upstream organization to incorporate patches. For more information on our upstream activities, please visit the communities page on our wiki: https://wiki.opnfv.org/display/COM

Standards Developing Organizations

The OPNFV project also works in collaboration with Standards Developing Organizations (SDO) such as ETSI NFV ISG, IETF, MEF, TM Forum, and others. We believe that collaboration amongst organizations will enable the industry to move forward together and that both standards and open source are needed to meet shared goals for NFV.

OPNFV SecurityCII Best Practices Badge

Core Infrastructure Initiative (CII) is a project managed by The Linux Foundation that enables technology companies, industry stakeholders and esteemed developers to collaboratively identify, fund and improve the security of critical open source projects. OPNFV has been awarded the Core Infrastructure Initiative Best Practices badge and is 100% compliant with CII best practices. See details on the OPNFV Badge here and the CII badge program here.