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.

Linux Foundation ecosystem relationships to OVP 2.0

(Olivier - Include Rabi's overview diagram illustrating relationships between the different contributing organizations highlighting open questions on who does what.)

...

E2E CNF Conformance Cycle 

(Below is from Jim's mail to OVP members (3/4/2020).  Will be discussed on next meeting. 

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

(insert diagram)

Test Categories

• Cloud Infrastructure Testing
  • Cloud Native ready post-install
  • Security patches
• Functional
• Manifest validation 
• Performance
• CNF Compliance Testing
• Cloud Native:
• Helm v3.0 testing:
• TOSCA (?)
• CNF Validation Testing:
  • API/Interfaces Testing
  • Major subsytem connectivity
• Functional Testing
• On-Boarding and Lifecycle Mgmt:
• Performance Testing
• Interoperability (?)

Evolving architecture from VNFs to CNFs

(Olivier - Add short description and I would like to gain clarity around CNF orchestration.  Specifically, we should clarify that CNFs are to be orchestrated by Kubernetes and that MANO is utilized specifically for VNFs. If this is not the case, document why?  Add clarity to the CNF Architecutre below. 

Source:  LF Networking

Compliance & Verification Program

OVP2.0 E2E Compliance and Verification Program adds additional collaboration with the CNCF in the testing and verification of Cloud Native Network Functions.

...

#7 MANO++ - is it to confirm that ONAP is Mano++ meaning that ONAP is providing additional capabilities than Mano functions i.e. Control Loops, etc.?

Source: LF Networking

Verification and Certification Process

OPV 2.0 will provide an open source test suite which enables both open and closed source CNFs to demonstrate conformance and implementation of cloud-native practices. Compliance to the verification process will result in a LFN Cloud Native CNF badge(s). The LFN CNF badges should provide value for both operators and commercial vendors.

...

(We should outline the types of testing as well as clarify where these tests belong.  Workload testing, Platform testing, etc.)

Cloud Native Network Function (CNF) Best Practices Criteria

Propose that the below should be aligned, agreed, and later decomposed into testable items.  We should sort with mandatory first and optional (but still verifiable) criteria at the end.  Organize into levels of Gold, Silver, Bronze if this makes sense.  What will the value of a Bronze be for operators and vendors?

...