All members are encouraged to contribute directly into this working draft.  

...

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

Adding Kubernetes to ETSI NFV/MANO

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.?

...

• Define MVP - by April 1
• Validate approach with partners (CNTT, CNCF, LFN projects) - during ONES technicall event (April 20)
• Implement “HelloWorld” sampleCNF test - Hackfest at June Developer and Testing Forum
• Implement MVP - by Q1/Q2 2021

MVP:

Objective:

Option A: Supporting a telco CNF for a Greenfield telco.

Option B: having a consistent telco container platform for telco workloads.

• Tooling:
  • Cloud installation tools into a given lab.
  • Testing Tools.
• Lab:
  • Platform details.
• Cloud Infrastructure Validation TestingConformance
  • Cloud Native ready post-install
  • Security patches ? 
• Functional (CNTT RC2)
• Manifest validation 
• CNF Compliance TestingCompliance Conformance
• Packaging: (Helm v3.0, TOSCA, HEAT)
• Cloud Native.
• On-Boarding and Lifecycle Management.
• CNF Validation TestingConformance:
  • API/Interfaces Testing
• Functional Testing (CNTT RC2)
• Badging:
  • Portal and process

...