All members are encouraged to contribute directly into this working draft.
...
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?
What is the Minimum Viable Program
The end state vision is spelled out above and since it is likely a multi-year endevour, what can we do this year to chart the direction and set in motion the program that achieves the vision?
E2E CNF Conformance Cycle
(Below is from Jim's mail to OVP members (3/4/2020). Will be discussed on next meeting (3/9/2020).
...
| Note |
|---|
We should probably look to add key components such as SDN controllers and other functions that are required for the end-to-end functionality of a network service, if that's what we want to be testing (as per cl664y@att.com's comments in the call on . |
...
Test Categories (NOT for MVP)
...
#6 Reduce Testing Intervals by 50% - How "50%" have been determined?
it was an early estimate based on discussions with Industry analysts and consultants. They looked at the POC/Interop phase for several carriers and the fact that VNF/CNF would be tested with NFVI across at least 2 vendors gives that number. BUT we would love to see actual numbers as a test case if possible.
#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.?
...