...
In the below diagram the “?” indicate processes that need definition and refinement for the differing execution environment of OVP Phase 2.
Test Categories (NOT for MVP)
- Cloud Infrastructure Validation Testing
- Cloud Native ready post-install
- Security patches
- Functional
- Manifest validation
- Performance
- CNF Compliance Testing
- Packaging: (Helm v3.0, TOSCA, HEAT)
- Cloud Native.
- On-Boarding and Lifecycle Management.
- CNF Validation Testing:
- API/Interfaces Testing
- Major subsytem connectivity
- Functional Testing
- Performance Testing
- Interoperability (?)
- Platform Testing
- Management Stack (K8s, ONAP) testing.
- integration with the infrastructure.
Evolving architecture from VNFs to CNFs
...
#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.?
Yes, That was the assumption. Closed loop control, Analytics etc..
Verification and Certification Process
...
- Identify cloud infrastructure installation tools.
- Identify Labs for testing .and human resources who will manage the labs (in addition to the testers)
- Identify projects to develop test scripts and tools to perform Cloud infrastructure functional testing and agree on scope.
- Agree on scope of CNF Onboarding testing.
- Identify projects to develop test scripts and tools to perform CNF testing and agree on scope.
- Agree on CVC portal.
...