Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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 (Suggest that we include Rabi's overview diagram illustrating relationships between the different contributing organizations in LFhighlighting open questions on who does what.)


The evolving architecture from VNFs to CNFs

(Needs describing and 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 only with VNFs.)specifically for VNFs. If this is not the case, 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.

Catherine - comments and questions regarding the E2E Compliance & Verification Slide (below):

#1 CNF Conformance has been removed from the CNF boxes in alignment with the CNF Conformance definition - https://github.com/cncf/cnf-conformance

#2 VIM (

...

Openstack) and VIM (K8S) are part of CNTT NFVI boxes in alignment with https://github.com/cntt-n/CNTT/tree/master/doc/ref_arch

#3 NFVi, PFNi → NFVI, PFNI – spelling aligned with ETSI

#4 Remove "for CNFs and" from "Hybrid (PNF/VNF & CNF) Compliance and Verification with OVP Ph2 in partnership with CNCF Conformance tests for CNFs and for K8s in CNCF'

Additional changes to be made:

#5 Picture under "Today" should include PNF, not only VNF

Questions:

#6 Reduce Testing Intervals by 50% - How "50%" have been determined?

#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

...