All members are encouraged to contribute directly into this working draft.  See also the OVP 2.0 Technical Ideas page

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 (CNTT)

• Reference Architecture 2 workstream (RA2)
• Reference Implementation 2 workstream (RI2)

Cloud Native Computing Foundation (CNCF)

• Telecom User Group (TUG)

How to engage

1. Join the mailing list:  https://lists.opnfv.org/g/OVP-p2
2. Subscribe to the calendar for the meetings: https://lists.opnfv.org/g/OVP-p2/ics/7337234/1823902251/feed.ics
3. Engage in the discussions at the weekly meetings
4. Share your ideas on these wiki pages and comment sections at the bottom of every page

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.

MVP proposal

Objective:

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

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

Proposed content of an MVP (needs refinement and assigned owners)

• Tooling:
  • Cloud installation tools into a given lab.
  • Basic Testing Tools.
• Lab:
  • Community development resource access
  • Platform details - specific HW details, login info,etc.
• 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:
  • Test results review process
  • Portal and badging process

Workstreams Proposal

R2 Definition Requirements Activities (RA2/RI2/RC2) [Primary Owner: CNTT]

Development/Lab environment [Primary Owner OPNFV+CNTT] - What are the lab resources for hosting configurations for developing the NVFI and running on-going CI/CD verification tests? How can a “Lab as a Service” (LaaS) be instantiated for CNF/NFVI testing, development, and validation efforts? Does the CNCF TestBed meet the needs?

Test Tooling/Test Suite Development Based on Above Categories [Primary Owner:  OPNFV]: Understand dependencies and what can be parallel processed. Also, what is the overall program test framework (e.g., Dovetail or something similar) that can plug in tests from projects and communities….

• On-boarding/Lifecycle Management testing - What are the preferred tools/methodologies for repeatably creating an NFVI environment supporting containers? Can CNFs be deployed and respond to basic lifecycle events? 
• Platform test - What is the source for the tests and toolchains for developing and verifying the NFVI platform for container based CNFs? Are there existing CNCF infrastructure tests/standards that should be co-opted? What level of micro-services should be integrated into the standard platform? How do we validate each of the micro-services against a specific version of the platform?
• CNF test - What is the source for the tests and toolchains for developing and verifying the CNFs as the SUT atop a verified NFVI? How does the CNCF test bed integrate into the OVPp2 workflow and test process? With many micro-services as “helper functions”, how do we validate each of the micro-services against a specific version of the CNF?
• Performance testing - Both the infrastructure and CNF performance characterization would be useful - this is very difficult to cooperatively define/execute (DEFER)

CVC portal [Primary Owner: CVC] - Define the UI for consumers of the CVC and on-ramp for producers of NFVIs and CNFs to publish their successful validation process results? How to the CNF compliance tests (CNCF) figure into the telco focused OVPp2 process? 

Governance/Structure/Mktg Framework [Primary Owner: CVC] - Includes 3rd party labs, white papers, slide decks. With input from MAC

MVP Roadmap

• Define MVP - by April 1
• Validate approach with partners (CNTT, CNCF, LFN projects) - during weekly OVP p2 meetings <ADD LINK>
• Implement “HelloWorld” sampleCNF test - Hackfest at June Developer and Testing Forum
• Implement MVP - by Q1/Q2 2021

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.