All members are encouraged to contribute directly into this working draft.  

Charter

The LFN OPNFV Verification Program Phase 2 (OVP 2.0) is an open source, community-led compliance and verification program to promote, enable, and evolve a thriving ecosystem of cloud-native telecoms where Cloud Native Network Functions (CNFs) from different vendors can inter-operate and run on the same immutable infrastructure.  It includes CNF compliance and verification testing based on requirements and best practices put forth by both the CNCF and CNTT.  These requirements feed tool-sets and testing scripts developed within OPNFV, ONAP and CNCF communities.

Vision

An end to end set of compliance/conformance tests and testing toolchain for independently verified Cloud Native Functions for use in Telco environments.

Who are participating?

Linux Foundation Networking

• Open NFVI project (OPNFV)
• Open Networking Automation Project (ONAP)
• Compliance and Verification Committee (CVC)

Common NFVI Telco Taskforce

Cloud Native Computing Foundation

What is the Minimum Viable Program

The end state vision is spelled out above and since it is likely a multi-year endeavor, what can we do this year to chart the direction and set in motion the program that achieves the vision?

First, the envisioned process is diagrammed below:

E2E CNF Conformance Cycle 

In the below diagram the “?” indicate processes that need definition and refinement for the differing execution environment of OVP Phase 2.

Roadmap

• Define MVP - by April 1
• Validate approach with partners (CNTT, CNCF, LFN projects) - during ONES technicall event (April 20)
• Implement “HelloWorld” sampleCNF test - Hackfest at June Developer and Testing Forum
• Implement MVP - by Q1/Q2 2021

MVP:

Objective:

Option A: Supporting a telco CNF for a Greenfield telco.

Option B: having a consistent telco container platform for telco workloads.

• Tooling:
  • Cloud installation tools into a given lab.
  • Testing Tools.
• Lab:
  • Platform details.
• Cloud Infrastructure Validation Conformance
  • Cloud Native ready post-install
  • Security patches ? 
• Functional (CNTT RC2)
• Manifest validation 
• CNF Compliance Conformance
• Packaging: (Helm v3.0, TOSCA, HEAT)
• Cloud Native.
• On-Boarding and Lifecycle Management.
• CNF Validation Conformance:
  • API/Interfaces Testing
• Functional Testing (CNTT RC2)
• Badging:
  • Portal and process

Immediate tasks:

1. Identify cloud infrastructure installation tools.
2. Identify Labs for testing and human resources who will manage the labs (in addition to the testers)
3. Identify projects to develop test scripts and tools to perform Cloud infrastructure functional testing and agree on scope.
4. Agree on scope of CNF Onboarding testing.
5. Identify projects to develop test scripts and tools to perform CNF testing and agree on scope.
6. Agree on CVC portal.