...
- Follow-up on DTF sessions, if necessary
- Review roadmap from Jakarta. It would be great that we reviewed what we defined in our roadmap for Jakarta. What has been done and what it is left.image2022-1-18_15-54-1.png (1166×618) (onap.org) (Catherine Lefevre )
For CNFO there is CNF Upgrade work to be completed in Kohn. (Lukasz Rajewski )
For other more heavy topics we need to discuss further on ONAP/EMCO, especially when Nephio came to the picture. I believe Nephio will become more a requirement for deployment of specific CNFs and it must be firstly adopted by CNF vendors, but ONAP will have to integrate with it at some point. Also, due to the fact the Nephio opts against orchestration of helm packages we should think on consequences of this approach in a long term as helm is used in CNFO, ASD and EMCO. (Lukasz Rajewski )
I would like to discuss further about the plans of ASD integration into ONAP, beyond the PoC phase. (Lukasz Rajewski )
Understand if we are mature enough to start with a first iteration of a “ONAP compliance CNF” verification/badge? (Olivier Smith ). Anuket Assured Program (AAP) - we were discussing on how to draft and establish the basic requirements for CNF conformance and validation badging using ONAP. So I would like to bring this to your notice to discuss further on it. (user-67d6f )
Nephio vs. MANO (no ETSI NFVO, no VNFM/CNFM, may not CNFO) and pushes down CNF management to Kubernetes; i.e., Kubernetes-based Cloud automation. They are using CRDs (for Infrastructure, Workload and configuration). I expect significant changes around the way of helm chart-based CNF management if Nephio is applied. We will see… (Byung-Woo Jun )
During the yesterday meeting on Anuket Assured Program (AAP), we were discussing on how to draft and establish the basic requirements for CNF conformance and validation badging using ONAP. So I would like to bring this to your notice to discuss further on it. (user-67d6f)
Action Item(s) (In Progress)
...