Skip to main content


OPNFV was formed to integrate the best of existing open source code into a reference platform that can be tested and deployed. OPNFV is committed to an upstream first methodology, only developing code when necessary to avoid proprietary forks of the upstream components. OPNFV adopts upstream open source projects and devotes development resources towards integration and testing tools that become a part of the releases.

OPNFV performs system integration as an open community effort, which means OPNFV creates and evolves components in lock-step with upstream communities, composes and integrates those components, deploys and tests the integrated system, and finally publishes the test results – all in an iterative and fully automated way. OPNFV can be viewed as an example of DevOps for networking in the open.

DevOps CI/CD methodologies are the backbone of OPNFV. On a nightly basis, scenarios are built and deployed in an automated fashion to Pharos labs across the globe on multiple hardware platforms. This level of built-in testing and automation enables network provisioning, speed, and technical diversity. OPNFV releases now have two tracks  – traditional and CD. The CD release gives users access to the latest upstream stable code rather than having to wait months as is the case with a traditional release.

Jerma, the 10th and final stand-alone release of OPNFV, culminates over six years of development effort, integration, and testing — supporting the Cloud iNfrastructure Telco Taskforce (CNTT)’s evolution, and advancing testing and service assurance to further enable telco-grade infrastructure maintenance, upgrades, testing, benchmarking, and service assurance. The project is well positioned with CNTT to develop further capabilities according to the needs of network operators and telco ecosystems into the future. Learn about Jerma.


Development of missing features or components.


Select components and features that match up with scenarios.


Automatically deploy your system onto targeted hardware infrastructure.


A scenario is a system, does it work?


Components evolve, and systems follow.