Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Update on DTF planned attendance and topic proposals
    • CNFO by Lukasz Rajewski 
    • SO Intent based orchestration - Huawei, DT - This is a discussion about SO plans for intent based during 2022. This will be the first broad forum discussion about this topic. More of a brainstorming, not presentation. Expectation is to complete the planning by November, and start implementation right after that.
    • General interest session - ONAP/EMCO - Face recognition app as CNF - 3 different NF modules composing one composite application.
  • Kohn planned work - ASD, SO Integration, EMCO...
    • ASD PoC is on-going. Expected to be completed. Then the ASD specification will be re-visited, in case there is a need to approve a "v2" of the model.
    • SO - Still several on-going discussions. Ready for sign-off, but planning more design work. SO-EMCO integration PoC was successful. Plan is to make it part of the release.
  • Should we switch to bi-weekly meeting cadence?
    • We need to go back to having technical discussions and collecting ideas, not just reporting progress
    • AI - CNF Taskforce members - Add topics to future agendas
    • Proposal to do a email poll about the desired meeting cadence. Desired purpose of these meeting.
    • We will cancel the next two meetings, while having an email discussion+f2f discussion about purpose of this taksforce.
  • AOB?

June 23rd, 2022 at 1pm UTC 

  • 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 )

  • 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)

...