...
- Feedback from OVP PH2 meeting: https://wiki.lfnetworking.org/display/LN/2020-03-09+OVP+2.0+Meeting+notes
- Review of our previous feedback concerning Compliance & Verification Program - https://wiki.lfnetworking.org/display/LN/OVP+2.0+Boot+Strap
- 2 presentations:
- CNCF Compliance (Bill Mulligan) (PDF version)
- OVP Workstream (Rabi Abdel)
- Do we need to extend our ONAP VNFReqs to consider CNF Reqs or shall we suggest a "LFN CNF Reqs" Board or will it be driven by CNCF?
- Need to connect with CNCF to avoid duplicated effort, divergent effort
- Architecture, Modeling, Security reqs will feed VNFReqs+ to define what it is requested to onboard CNFs on ONAP — Shall we draft a Diagram flow?
- Need also to consider CNF Security reqs from SECCOM
- Need to consider the Architecture, Requirement Subcommittees' perspectives
- ETSI Activities to define packages - candidate for the Guilin Release ETSI CNF Support
- ESTI reqs/packages availability - End of Q4
- Need to define an intermediate (Helm v3.0, TOSCA, HEAT) then try to push back our findings to ESTI
- Hydrid approach (supporting all together - CNFs, VNFs, PNFs) - need to address the network partpart ONAP SO ETSI-Aligned Hierarchical Orchestration
- Migration Strategy from Openstack (VNFs) to K8S (CNFs)
- New artifacts for containers
- New packages while offering the same functionality than formerly VNFs
- Define the mapping (Helm v3.0, TOSCA, HEAT)
- Review "Features/Capabilities - How We complement each other?"
...