Versions Compared

Old Version 91

changes.mady.by.user Ranny Haiby

Saved on

compared with

New Version Current

changes.mady.by.user Yan Yang

Saved on

Key

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

...

  • Follow-up on DTF sessions, if necessary
    • No open action items
  • 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 )
    • Move to next week

  • For CNFO there is CNF Upgrade work to be completed in Kohn. (Lukasz Rajewski )

    • On track to deliver in Kohn

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

    • Wait until after the Nephio summit. Follow up next week.

  • I would like to discuss further about the plans of ASD integration into ONAP, beyond the PoC phase.  (Lukasz Rajewski )

    • Concern about the separate flows/APIs for CNF orchestration using ASD. 
    • Need input from Ericsson about the effort to merge the flows.

  • Drafting the ONAP CNF requirements for CNF conformance and verification badges. Understand if we are mature enough to start with a first iteration of a “ONAP compliance CNF” verification/badge?   Yan Yang  (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 )

    • Olivier Smith  Yan Yang presented the different certification types of Anuket Assured, present and future. AAP2022 Planning and VNFCNF badging Requirements for ONAP.pdf
    • For the CNF workload, there could be three different certifications - (1) Compliance with Cloud Native best practices. (2) Compliance with Anuket infra (3) Compliance with ONAP orchestration (or EMCO, Nephio)
    • It is up to the ONAP community to determine the best practices, requirements and test cases for the certification
    • Lukasz Rajewski presented the current set of best practices for designing and packaging CNFs for ONAP orchestration. These could be turned into requirements, and test cases.
    • We need to have a discussion in the ONAP community on how to create the tests and how it will be resourced. We will follow up with the Anuke Assured team in a couple of weeks.

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

    • Wait until after the Nephio summit. Follow up next week.

...

July 14th, 2022 at 1pm UTC

July 21st, 2022 at 1pm UTC

  • (Reminder - record the meeting)
  • Follow up questions related to the ASD PoC presentation from July 14th
    • Is the PoC using the service instance API? Byung-Woo Jun - not yet. Building block implemented, but no macro.Lukasz Rajewski recommends using the API for better integration with other workflows. That will enable orchestrating CNFs together with other parts of the Network Service.
    • Marian Darula - There is a need to model a distributed service, which is deployed in multiple edge locations. ETSI-NSD concept is one option for that. EMCO seems to have support for a similar concept and may be an option, too.
    • Byung-Woo Jun - The CNFM functionality is separated in the SO, and it may use multicloud, or call EMCO in the future. The motivation was to minimize changes on existing ONAP modules. The only difference between ASD orchestration and other orchestration flows is the interface to the "ASD repository" and "Helm Artifact Repository". CNFO does not interact with the "Image Artifact Repository", this is done directly from the K8S cluster. Parameterization is done by SO providing the overridable parameters (based on user input) to the CNFM. The CNFM uses these parameters to crate the instance level Helm chart. (Referring to slide #9 in last week's presentation ASD-PoC-Update-Plans-2022-07-14-v3.pptx
    • Lukasz Rajewski - The existing orchestration macro is very close in its functionality to what was done in the ASD PoC. Recommends the ASD PoC be merged with the CNFO approach.
    • Question about whether K8S API is used directly or through kubectl? currently kubectl is used.
    • Lukasz Rajewski - The SO integration with EMCO was done in a different way than depicted in the ASD PoC diagram. 

July 28th, 2022 at 1pm UTC


August 4th, 2022 at 1pm UTC

  • (Reminder - record the meeting)
  • Byung-Woo Jun provided a sneak preview of proposed work for ASD considerations for NSD, where NSD may consist of ETSI VNF/CNF and ASD CNF.
    • Proposed architecture keeps the ASD CNFM as a separate module, with an API that can be called by the SO CNFO.
    • The ASD CNFO will not rely on multi-cloud. 
    • Will be presented in future meeting when the Ericsson team is ready to present. Byung-Woo Jun will add to the agenda when ready.
    • The team working on CNFO may have a slightly different view - prefer having the ASD CNFM integrated inside the SO BPMN infra, not as a separate module. 


August 11th, 2022 at 1pm UTC

  • This meeting is cancelled due to summer vacations


August 18th, 2022 at 1pm UTC


August 25th, 2022 at 1pm UTC

  • (Reminder - record the meeting)
  • No topics to discuss - should the meeting be cancelled?

September 1st, 2022 at 1pm UTC

  • (Reminder - record the meeting)
  • What do we want to do next on our meetings?




Action Item(s) (In Progress)

  •  (CNF Task Force): What do we need to ask to CNF Vendors to be onboarded on the ONAP Platform? These reqs could be shared with Anuket Assurance for the CNF badging

...