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.

...

Cloud Native Computing Foundation (CNCF)

• Telecom User Group (TUG)
• CNF Conformance

5G Cloud Native Network Demo (Brandon Wick)

• Community Page

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

...

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

Image Removed

MVP proposal

...

Image Added

Categories of Conformance:

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)

• A. Cloud Platform Conformance
  • A1. Functional (i.e. CNTT RA-2 Compliance)
• B. CNF Conformance
  • B1. Cloud Native (i.e. CNF Conformance)
  • B2. Functional (i.e. CNTT RA-2 Compatibility)
  • B3. ONAP
  • B4. Performance
• C. Cloud Platform Benchmarking

MVP proposal

Not every thing can be tackled in the MVP, here are two elements that can be tackled for MVP.  

• A1: Cloud Platform Conformance (may be partial)
• B1 & B2: CNF Compliance

What needs to happen/Decided on:

• Decide on Tooling:
  • Cloud installation tools into a given lab.
  • Basic Testing Tools.
  • what open source project is responsible of this.
• Decide on 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

...

• • what open source project is responsible of this.
• Decide on Badging Process:
  • Test results review process
  • Portal and badging process
• Decide on OpenSource Testing Projects
  • What project will deliver what test category (A, B, and C)
    • A: ?
    • B: ?
    • C: ?

Workstreams Proposal (see OVP 2.0 Workstreams)

• WS01: Governance/Structure/Mktg, Badging Process and Framework[Primary Owner: CVC] Rabi Abdel Lincoln Lavoie Heather Kirksey
• WS02: Definition Requirements Activities (CNTT/ONAP/SDOs) [Primary Owner: CNTT] Bill Mulligan Trevor Lovett Ryan Hallahan Olivier Smith Fernando Oliveira  
• WS03: Lab and tooling [Primary Owner ONAP+OPNFV+CNCF]  Frederick Kautz Kanagaraj Manickam Trevor Cooper Ryan Hallahan
• WS04: A. Cloud Platform Conformance [Primary Owner XX] Taylor Carpenter (cloud native)
• WS05: B3. CNF Compliance - ONAP  Kanagaraj Manickam Catherine Lefevre Amar Kapadia Seshu Kumar Mudiganti  Ranny Haiby Srinivasa AddepalliFernando Oliveira Byung-Woo Jun
• WS06: B1/B2. CNF Compliance - Cloud Native & Functional [Primary Owner CNCF Taylor Carpenter ] Olivier Smith Trevor Lovett
• WS07:  ONAP POC and existing development work [Primary Owner ONAP  ] Merged with WS05
• WS08: B4/C - Performance: Trevor Cooper

MVP Roadmap - NEEDS COMMUNITY REVIEW/UPDATE

• 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 and AIs:

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.

OLD: Workstreams Proposal

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?

...

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:

...