Reference implementation and test automation ahead of 5G & Edge

Current Release: Iruya 9.0

Iruya, the ninth OPNFV release, contains tools, script and automation is an enabler for the Common NFVI Telco Taskforce (CNTT) Reference Implementation (RI), Reference Compliance (RC), the OPNFV Verification Program (OVP), and cross-project testing. Functest, Yardstick, VSPerf, Bottlenecks, and NFVBench saw an increase in capabilities and test cases. Along with the introduction of the OpenStack Airship installer, these test projects primarily test the NFVI layer utilizing OPNFV scenarios based on OpenStack, Kubernetes, OpenDaylight, OVS, OVN, and FD.io upstream projects. The CI and testing projects also form the basis of the critical collaboration between OPNFV and CNTT, where OPNFV will assist with the CNTT RI and RC badging through OVP. Moreover, OVP continues to make progress with over 12 verified NFVI products. Iruya also contains a number of important edge computing features through projects such as Rocket, Edge Cloud, and Container4NFV. Several feature projects such as Barometer, Doctor, and LaaS made progress as well.

Architecture

Learn about the OPNFV architecture on the Technical Overview page.

Cross-community Collaboration (CNTT & OVP)

The collaboration between OPNFV and the Common NFVI Telco Taskforce (CNTT) continues as OPNFV Scenarios will provide an implementation of CNTT Reference Architectures in 2020. CNTT has a hierarchy of Reference Model ⇒ Reference Architecture ⇒ Reference Implementation ⇒ Reference Compliance (via OPNFV testing projects and OVP). OPNFV will work on Reference Implementations and Reference Compliance.

The OPNFV Verification Program (OVP) continues to make progress across its two tracks: NFVI and VNF. The NFVI track now has over 12 verified solutions. For the VNF track, the OVP community has also been working on VNF validation tests that will be introduced in 2020. In 2020, OVP will also badge CNTT compliant implementations.

In addition to the enhancements around Functest, CNTT collaboration during Iruya also included the introduction of the new OpenStack Airship installer via a new OPNFV Scenario. The Airship Scenario will help implement the CNTT RI and the RI CI gates conforming to CNTT RI/RC requirements.

Test Projects

OPNFV continues to make progress on the various test projects that fill a critical gap of testing the NFVI layer in an operator’s CI pipeline. These projects were used to test OPNFV Scenarios based on the Fuel and Airship installers with OpenStack, Kubernetes, OpenDaylight, OVS, OVN, and FD.io upstream projects.

  • Functest: The functional testing project published new CNTT specific containers, increased test coverage, and includes CNTT compliance cookbook. It also includes rally_full in daily CI jobs making it more robust and has published new Ansible playbooks to deploy the OPNFV CI/CD toolchain with greater ease. Functest contains several test cases that run a VNF to provide a more realistic load on NFVI. During Iruya, these VNF test cases were hardened and reduced in footprint.
  • Yardstick: The performance testing project has enhanced its support for several traffic generators such as TRex, Pktgen, and IxNextgen. New test cases have been added that include greater testing for DPDK, SR-IOV, and specific security and networking features. The NSB sub-project that measures the performance of Network Services, as opposed to NFVI, has an improved report generation capability to make it easier to read.
  • VSPerf: The project used for virtual switch performance characterization is now ready for containerization for easier deployment. It  also adds support for new traffic generation tools and the ETSI GS NFV-TST 009 specification (Specification of Networking Benchmarks and Measurement Methods for NFVI).  
  • Bottlenecks: The project used for NFVI stress and longevity testing, has further enhanced its AI-based historical test results correlation/anomaly analysis capability to predict failures in subsequent test runs.
  • NFVBench: a project used for NFVI data plane performance testing includes bug fixes and code enhancements.

Edge Computing

The Airship Scenario along with new documentation and features in Rocket, Edge Cloud, and Container4NFV represent important progress to enable edge computing.

  • Rocket: The Rocket project that works on vEPC hardware acceleration defined the GPRS Tunneling Protocol (GTP) offloading interface and process. 
  • Edge Cloud: The project produced an “edge OpenStack test cases” document that captures use cases and functional requirements for OpenStack telco edge clouds.
  • Container4NFV: The project now supports Kata containers with the Multus CNI thus providing a secure container with multiple IP addresses for edge computing and CNF use cases.

Additional Enhancements

Some of the more important feature projects in OPNFV saw increased functionality and capability in addition to bug fixes and documentation improvement:

  • Barometer: Features an improved one-click installer experience with new Ansible scripts along with the ability to include pre-release versions of Collectd, furthering the spirit of the continuous delivery (CD).
  • Doctor: Includes updates to the rolling maintenance use case first introduced in the Hunter release along with the implementation of the latest OpenStack Felix project.
  • LaaS: Supports the ability to allocate an entire Pharos POD instead of just a server and allows automated virtual deployment of OPNFV.

Community Bridge Progress

As part of the Community Bridge initiative, announced by LFN at ONS NA last year, OPNFV embarked on the process of migrating the project to EasyCLA, one of the tools in the Community Bridge suite.  EasyCLA automates the process of managing contributor agreement and access to code repositories. EasyCLA also enables participating organizations to have direct control over which employees are authorized to be contributors. An onboarding plan was presented to the TSC in November.  Subsequently, each participating organization identified a CLA manager, who was provided instructions for creating a white list for their organization. As of late January, most organizations had created a white list, and the EasyCLA tool is scheduled to go live on February 12.

Python 3 Migration

The Python project ended support for Python 2 at the end of 2019.  OPNFV projects migrated to Python 3 and ended all dependency on Python 2 as of the Iruya release.

What’s Next?

The OPNFV community will convene at ONES North America, April 20-21, and the LFN Technical Meetings, April 22-24.