OVP 2.0 Workstreams
WS01 Scope: Governance/Structure/Marketing/Badging Process and Framework
Definition of the minimum initial program (MIP) - that we will launch a Cloud Native OVP badge with
Note the other work streams MUST deliver on their components, i.e. minimum requirement set, tooling to implement the testing of requirements, etc.
Cloud Native OVP Charter - eg. program operation, define the review criteria, program processes
Portal and submissions.
Approval/Review process.
Relationship with other industry initiatives (ONAP, CNCF, CNTT, OPNFV).
Longer term road map(s) for the evolution of the programs.
WS02 Scope: Definition of Requirements Activities (CNTT/ONAP/SDOs)
Overall Requirement:
badging types, etc.
Lab/Framework Requirements:
CNTT RI-2/RC-2
State the requirements for community labs including HW requirements
Testing requirements for each category:
CNTT RI-2/RC-2/CNF Conformance, CNCF, etc.
Highlight the sources of requirements
WS03 Scope: Lab and tooling
Define the set of labs available for the CNOVP use
LaaS outline
Review the testing frameworks - eg. CNCF testbed, xtesting OPNFV, badging testing framework
WS04 Scope: Cloud Platform Conformance (A. Category) Testing
Infrastructure focus
What projects have test cases that have the desired tests?
Define the catalog of tests that exist today and the gaps
WS05 Scope: CNF On-boarding (B. Category) Testing
On-boarding focus
What projects have test cases that have the desired tests?
Define the catalog of tests that exist today and the gaps
Review of ONAP capabilities
WS06 Scope: CNF Conformance (C. Category) Testing
CNFs - functionality, performance, Cloud Native principle adherance
What projects have test cases that have the desired tests?
Define the catalog of tests that exist today and the gaps
WS07 Scope: ONAP POCs & Existing Development Work to support CNFs
Initial experimentations with basic CNF(s) in order to validate onboarding, instantiation, monitoring processes
Implement what you learn from ETSI-based CNF support
Pursue our Cloud Native Security journey by leveraging the benefits of a Service Mesh