Versions Compared

Old Version 80

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.

...

  • Planning sessions for June DTF:
    • ONAP CNF sessions/demos
      • Additional ONAP CNF sessions may be submitted after travel decision is made.
    • Plenary/General-interest
      • Ranny Haiby pointed out general interest sessions on the proposal page and recommended participation.
    • Who's planning to attend?
  • We had a very short meeting. Discussed DTF attendance plans and adjourned early.
  • AI - Please add topics to next week's call

May 26th, 2022 at 1pm UTC - Cancelled?

  • Update on DTF planned attendance and topic proposals
  • AOB?

June 2nd, 2022 at 1pm UTC 

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

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

June 30th, 2022 at 1pm UTC 

  • Nephio/ONAP/EMCO integration

    • What did we learn at the Nephio summit?

      • Not attempting to compete with ONAP
      • Focusing on Infra, K8S and workload, as well as configuration
      • It is clear that Google is not in favor of Helm charts. They try to push the KPT packaging.
      • TSC and four SIGs were formed. SIG1 (Architecture) is expected to be led by a service provider.
      • Blog post by Aarna with some details - https://www.aarnanetworks.com/post/what-is-the-linux-foundation-nephio-project
      • Where is this discussion going to continue? TSC according to Google.
  • XGVela
    • Started using OKD
    • Topology management will be in the first release. Configuration is a stretch goal.
    • Seshu Kumar Mudiganti is working on a PoC integrating ONAP and XGVela. Will share a demo soon.
  • Anuket Assured program 
    • Follow up on last week's presentation by the Anuket team - What do we want to include in the certification? Resources? - Discuss in TSC.


July 7th, 2022 at 1pm UTC

  • Nephio summit recording are now available - https://drive.google.com/drive/folders/1o_VwSifi1_Ksy5YaCixCHKjACvksztQB
    • Recommended session - Day1 recording, starting at 3:06:20 (pdf slide deck starting at slide #48) (Brian Grant). The two sessions after that by Stephen and John from Google are also not bad.
  • SO/EMCO integration - planned to be merged soon, hopefully during August.
  • We had a short meeting due to the light agenda, and no recording because Ranny Haiby forgot to click the button.

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

...