Meeting Minutes
Table of Contents maxLevel 2
...
- ONAP slide(s) for the LFN Cloud Native messaging - continue work on the slides
- Updated version (Byung added Security description; will refine it further) - ONAP_Cloud_Native_v0.3.pptx
- Continue editing offline - proposal to use Google docs
- Keep diagrams in block/wire level - Brandon Wick will work with LF creative team to polish graphics.
- Updated slides with edits made during the meeting - ONAP_Cloud_Native_v0.4.pptx
- ASD progress: Update on ASD example and requirements, ASD & packaging examples by Thinh Nguyenphu
- Marian Darula - proposes to promote the use of ASD for O-RAN rApps and xApps in addition to CNFs
- Thinh Nguyenphu - requests review of the requirements in the page linked above. Wiki page comments are welcome.
- Interested parties may join the "orchestration scenarios" meeting on Mondays 8AM EDT - Orchestration Scenarios
- Fernando Oliveira - Verizon is proposing an ETSI based packaging for rApps/xApps
- ONE Summit sessions
- "Building modern cloud-native network services with ONAP" - accepted. Will be a virtual session. Ranny Haiby reached out to LF events team to figure out the details of how to still allow panel members to attend the event in-person if they wish.
- ASD session - waitlisted
...
- Review ONAP Cloud Native journey slides after editing based on feedback submitted on Wiki - Brandon Wick
- Brandon Wick will set up a Google doc collaboration space. Ranny Haiby and Byung-Woo Jun will collaborate.
- Proposed edits to tighten up infographic available here. Please review/approve by tomorrow (Sept 10).
- Review ONE Summit slides to be prepared by Ranny Haiby
- ASD Updates
Action Items (In Progress)
- Catherine Lefevre: Plan CNF Task Force readout with the ONAP TSC
- Brandon Wick- will collect additional information about the ONES event (virtual, F2F present, etc.)
- Lukasz Rajewski - Ask Orange colleagues to present EMCO↔Multicloud comparison
- (All) Feel free to provide feedback about ASD packaging (Orchestration Scenarios)
- (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
- (Modeling/Requirements): Need to determine what ETSI CNF package solution we want to move forward (Fernando Oliveira, Byung-Woo Jun vs Thinh Nguyenphu)
- (Olivier): Check with CNCF if any cross-meeting with ONAP could be scheduled
- (All): Collect feedback about our current CNF onboarding capabilities from 3rd party vendors
- Slides for review - ONE-Summit_Cloud_Native_Service_Orchestration_ONAP v0.1.pptx
- Prepare "canned" questions - Ranny Haiby will re-circulate the June DDF questions over email to the panel participants
- Request to address the CNF packaging - What should operators request from the vendors? What is the proper short term approach to packaging? There is basic certification in the VNF-SDK project that validates Helm charts. SDC onboarding using Helm charts is available today. Some relevant work is done in the context of the 5G Super blueprint - https://wiki.lfnetworking.org/display/LN/LFN+Demo%3A+5G+Super+Blueprint
- Agree on presentation and speaking order
- ASD Updates
- There is progress in planning the PoC
- Discussion on how to provide additional parameters external to the Helm charts
- ASD Onboarding and Orchestration PoC - Please review and comment
- Ericsson is finalizing work on parameters. Will sync with Nokia
- Looking for reference CNF to be used in the PoC. First goal may be adapting the "direct path" package of cFW to ASD.
September 16th, 2021 at 1pm UTC
- ASD Update (Marian Darula )
- Ericsson/Nokia had a meeting. Good progress made. Certain items are still under discussion.
- Next step will be to have a PoC with an ONAP sample application (vFW and/or Magma Controller/AGW?). A stage 3 data model that is TOSCA based is required for the PoC. Ericsson is working on that.
- There is a proposal from Ericsson to add network specific descriptors, like L2 connectivity.
- Figuring out how to validate parameter consistency
- Feel free to provide feedback about ASD packaging (Orchestration Scenarios) including suggestions for the POC
- Plan CNF/Cloud Native Task Force readout with the ONAP TSC
- Proposed Topics:
- Session 1 - ASD Readout and ETSI CNF Package Evolution (45 mins) - tentative date: Oct 7th, 2021 (TBC) - Fernando Oliveira , Marian Darula , Byung-Woo Jun , Thinh Nguyenphu
- Session 2 - Jakarta requirement candidates
- Implementation of ASD/ETSI CNF Packaging - Fernando Oliveira , Marian Darula , Byung-Woo Jun , Thinh Nguyenphu
- Continuity of CNF O & potentially EMCO Integration - Lukasz Rajewski , Seshu Kumar Mudiganti , Byung-Woo Jun
- Proposed Topics:
- Convert our ONAP Cloud Native Evolution into a Roadmap
September 23rd, 2021 at 1pm UTC
- ASD Readout (Marian Darula , Byung-Woo Jun )
- Work on our ONAP CNF_Cloud Native Roadmap_V2.pptx
- Jakarta Timeline: Kick-Off on 10/14 and submit reqs no later than 12/2 (M1)
- Plan CNF/Cloud Native Task Force readout with the ONAP TSC
- Session 1 - ASD Readout and ETSI CNF Package Evolution (45 mins) - date: Oct 7th, 2021 (TBC) - Fernando Oliveira , Marian Darula , Byung-Woo Jun , Thinh Nguyenphu
- Session 2 - Jakarta requirement candidates - Nov 4th & Nov 18th
September 30th, 2021 at 1pm UTC
- ASD Readout (Marian Darula , Byung-Woo Jun ,Thinh Nguyenphu )
- Marian Darula - There is fine tuning going on between Ericsson and Nokia, especially around network interfaces (secondary interface)
- Official presentation to the forum will be done next week
- ASD POC (Byung-Woo Jun , Lukasz Rajewski , Seshu Kumar Mudiganti )
- Working on the details of the architecture - ASD Onboarding and Orchestration PoC
- Analyzing impact to existing ONAP components.
- Starting with on-boarding - what are the implications on SDC.
- Next items for discussion include modeling for A&AI, How to extract parameter values, how to create custom workflow.
- Trying to re-use existing flows, where possible.
- Marian Darula - Final version of ASD is not finalized. Can the PoC progress with the existing version? Byung-Woo Jun - Probably yes. There is enough to start with.
- Zu Qiang (Ericsson) - Modeling should not be driven entirely by the PoC. It should happen independently.
- Kamel Idir - What will be the impact on service design in SDC? There might be some impact, but exact details are TBD based on the architecture discussion. However, the focus of the PoC is not on instantiation, but rather day 2 configuration and control loop.
- ASD presentation to the TSC - ASD proposal is ready to be presented, although it is still WIP. Details of the presentation will be discussed on Monday's 'orchestration scenarios' call.
October 7th, 2021 at 1pm UTC
- EMCO v2.0 vs Multicloud (Orange)
- EMCO analysis and trial presentation by ilhem fajjari EMCO & Ongoing Work in Orange
- Trial - Several applications (Core and RAN), several Helm charts. Placement based on labels. Placement was done by assigning labels.
- Kubernetes plugin presentation by Lukasz Rajewski K8s plugin - Summary and use in ONAP for CNFO
- Next steps - There is a need for a discussion with the Architecture Subcommittee about the role of Multicloud. Clarification from Lukasz Rajewski - SO can decide whether to call EMCO or multicloud.
- EMCO analysis and trial presentation by ilhem fajjari EMCO & Ongoing Work in Orange
October 14th, 2021 at 1pm UTC
- EMCO integration with ONAP - Continue the discussion
- ASD Readout: https://wiki.onap.org/display/DW/Application+Service+Descriptor+%28ASD%29+and+packaging+Proposals+for+CNF
October 21st, 2021 at 1pm UTC
- Review the "Welcome" Task Force page (including our HL Vision, etc)
- Collect the latest versions of CNF Taskforce presentations from recent events - ONE Summit, DDF,
- Ranny Haiby - Propose a new high level structure for the landing page
- New meeting time after DST ends in the US (Nov-7th)
- Questions for EMCO
- What is the division of roles and responsibilities between ONAP and EMCO?
- Please add questions here: ___
- Ranny Haiby - Request EMCO rep to join one of the upcoming task force meetings
- ASD Update
A Jira ticket was createdASD ONAP REQ ticket:
(modeling, not PoC)Jira server ONAP Jira serverId 425b2b0a-557c-3c0c-b515-579789cceedb key REQ-993 ASD Requirement at J release wiki page : Jakarta release - functional requirements proposed list#ApplicationServiceDescriptor(ASD)onboardingpackageIM/DM
There is an upcoming presentation the requirements subcommittee.
- TOSCA will be used for the descriptor
- There is a need to adapt the packaging format to align with SOL004
- Seshu Kumar Mudiganti - There is a need to discuss with additional projects, like SDC
- There is another requirement for the PoC - Application Package Onboarding to SDC . Requirements are still in progress.
October 28th, 2021 at 1pm UTC
- Continue work on CNF Taskforce landing page. - Please add more items as you see fit - New Landing Page
- New meeting time after DST ends in the US (Nov-7th) - Ranny Haiby will create a Doodle poll.
- Cancel CNF Task Force meetings on Nov 11th and Nov 25th? - Tentatively cancel both.
- ASD review by Requirements subcommittee and IM subcommittee
- Proposal was well received
- Modeling subcommittee raised a question regarding other types of deployment items except Helm charts (E.g. Terraform) - This could be a future version functionality
- ASD information will be populated under the modeling section in the wiki.
- The ASD workgroup is working on an official data model, preparing for an official review by the modeling subcommittee.
- Jakarta PoC plan was presented and was well received. Additional meeting with SDC is planned. On-boarding process may be adjusted based on data model. ASD onboarding to SDC (WIP) - Application Package Onboarding to SDC
- SOL004- ETSI is working on Release 4. Now would be a good time to provide the ONAP feedback to ETSI. Thinh Nguyenphu proposes a liaison mechanism between ONAP and ETSI on this topic. ASD workgroup will follow-up as necessary.
November 4th, 2021 at 1pm UTC
- Meeting cancelled
November 16th, 2021 at 2pm UTC
- Continue work on CNF Taskforce landing page. - Please add more items as you see fit - New Landing Page
- Prepare for upcoming meeting with EMCO to discuss details of future integration - Roles and responsibilities, API calls, Integration points (Multicloud vs. directly from SO), any other open technical questions.
November 23rd, 2021 at 2pm UTC
- Thanksgiving week in the US - Meeting is cancelled.
November 30th, 2021 at 2pm UTC
- Proposed joint meeting with EMCO technical leaders (Sharad Mishra , Srinivasa Addepalli ) to discuss details of future integration - Roles and responsibilities, API calls, Integration points (Multicloud vs. directly from SO), any other open technical questions.
- Follow-up on analysis done by Orange - EMCO & Ongoing Work in Orange , K8s plugin - Summary and use in ONAP for CNFO
- Why was EMCO created in the first place? What were the motivations? What ONAP gaps does EMCO address?
- A few initial gaps for integration were identified by Lukasz Rajewski
- Srinivasa Addepalli - EMCOs goal is to deploy "complex" applications (or CNFs) across multiple K8S clusters. It continues monitoring the deployed applications and provides status. EMCO assumes K8S is the cloud infrastructure, but it supports VMs as well. It can communicate with public cloud APIs (Azure, GCP). EMCO v1 was integrated with ONAP multicloud, which handles single CNFs. EMCO v2 can handle a network service (multiple CNFs). EMCO does not have a "standard compliant" northbound API (e.g. ETSI VNFM or NFVO)
- Seshu Kumar Mudiganti - Proposes a Service-Orchestration/Resource-Orchestration approach. EMCO can handle Helm charts deployment (=resource). SO will handle the service level.
- Lukasz Rajewski - We should compare the terminology between ONAP/EMCO/ETSI.
- Srinivasa Addepalli - EMCO handles "composite applications" described by a Helm chart. It provides value by interconnecting the components of the composite service, e.g. using ISTIO.
- What will be the demarcation between ONAP and EMCO? Will EMCO handle an entire CNF? Each Helm chart separately? In EMCO, One application may have multiple micro services. ONAP has "services" consisting of "VF"s, That may have "VF modules". Each "VF module" is a Helm chart.
- Lukasz Rajewski - The main difference between ONAP and EMCO is that ONAP deploys each "VF module" (=Helm chart) separately, using an API call to multicloud. We need to find a way to preserve this approach, making multiple API calls to EMCO.
- First step for integration - ONAP will call EMCO for each "VF module". This will not take full advantage of EMCO's capabilities, but will only serve as a first step toward deeper integration. CNF adapter in SO will be the integration point. Multicloud will not be used for this integration.
- Future steps for integration - Have EMCO handle an entire VF as one composite application.
December 7th, 2021 at 2pm UTC
- <meeting was not recorded - Ranny Haiby - sorry, my bad.>
- Plan EMCO integration - PoC in Jakarta? Full feature later?
- There is a need to go to the next level of details
- Highest impact will probably be on SO
- ASD Updates?
- Planned review in modeling committee - Application Service Descriptor (ASD) onboarding IM
- Updated package description - Application Service Descriptor (ASD) Onboarding Packaging Format
- TOSCA descriptor - Application Service Descriptor (ASD) Resource Data Model
- January Developer forum sessions:
- https://wiki.lfnetworking.org/display/LN/2022-01-DD+-+ONAP%3A+CNF+Orchestration+Tutorial
- https://wiki.lfnetworking.org/display/LN/2022-01-DD+-+ONAP%3A+Application+Service+Descriptor+%28ASD%29+for+K8s+NFs
- https://wiki.lfnetworking.org/display/LN/2022-01-DD+-+ONAP%3A+ASD+and+Application+Onboarding+and+LCM+Orchestration
- https://wiki.lfnetworking.org/display/LN/2022-01-DD+-+ONAP%3A+Orchestration+of+xNF+Based+5G+Service
- Plans for certification program?
- No plans yet. All relevant requirements will soon be accessible from the new CNF Taskforce landing page
December 14th, 2021 at 2pm UTC
- MEETING WAS CANCELED - low attendance
- Finalize new landing pageDecember 14th, 2021 at 2pm UTC
Action Items (Closed in 2021)
...
It would be great to highlight more clearly the purpose of XGVela as a platform to build CNFs and get feedback from 3rd party vendors, who are today already creating CNFS for carriers, to assess the value proposition
After the CNF is created via XGVela – can we then deploy the CNF on any Cloud environment without using XGVela at run-time?
If we need XGVela then have we performed an analysis to demonstrate the value proposition vs K8S and its ecosystem?
Build a slide to highlight how XGVela (i.e. create CNF) is complementary to ONAP (onboard CNF/orchestrate CNF, etc.) and how it will fit to the CNCF Landscape
- Catherine LefevreFollow-up with the Modeling Subcommittee about yan yanrequest
- @Thin to upload presentation from May 6th call
- Kenny Paul - Reach out to FB to meet us on May 12th, 2021 (ONAP For Enterprise Task Force) - request made to LF PM - just checked no name yet.
- Catherine Lefevre: Introduce Amy Zwarico to Anuket, CNCF and OVP PH2 Communities and share SECCOM Container Logging specs
- (ALL): Provide feedback regarding Thin's proposal presented on May 6th, 2021
- (Andy Mayer , Hui Deng ) Follow up regarding Modeling team about CVC request - Re: Request from CVC
- Kamel Idir - Will repeat onboarding with Honolulu (once he has the lab resources) and will report back
- (Byung-Woo Jun: Bring the discussions to the ONAP Architecture Subcommittee about SO/SDNC role etc (see notes from 4/29)
- Ranny Haiby - Create a first draft of the "ONAP cloud-native" messaging slide and share with the Taskforce.
- Ranny Haiby , Byung-Woo Jun , Timo Perala , Seshu Kumar Mudiganti to discuss the enhancement of our ONAP Cloud Native Vision/Roadmap, this with Architecture, Requirement & MAC subcommittees
the value proposition
After the CNF is created via XGVela – can we then deploy the CNF on any Cloud environment without using XGVela at run-time?
If we need XGVela then have we performed an analysis to demonstrate the value proposition vs K8S and its ecosystem?
Build a slide to highlight how XGVela (i.e. create CNF) is complementary to ONAP (onboard CNF/orchestrate CNF, etc.) and how it will fit to the CNCF Landscape
- Catherine LefevreFollow-up with the Modeling Subcommittee about yan yanrequest
- @Thin to upload presentation from May 6th call
- Kenny Paul - Reach out to FB to meet us on May 12th, 2021 (ONAP For Enterprise Task Force) - request made to LF PM - just checked no name yet.
- Catherine Lefevre: Introduce Amy Zwarico to Anuket, CNCF and OVP PH2 Communities and share SECCOM Container Logging specs
- (ALL): Provide feedback regarding Thin's proposal presented on May 6th, 2021
- (Andy Mayer , Hui Deng ) Follow up regarding Modeling team about CVC request - Re: Request from CVC
- Kamel Idir - Will repeat onboarding with Honolulu (once he has the lab resources) and will report back
- (Byung-Woo Jun: Bring the discussions to the ONAP Architecture Subcommittee about SO/SDNC role etc (see notes from 4/29)
- Ranny Haiby - Create a first draft of the "ONAP cloud-native" messaging slide and share with the Taskforce.
- Ranny Haiby , Byung-Woo Jun , Timo Perala , Seshu Kumar Mudiganti to discuss the enhancement of our ONAP Cloud Native Vision/Roadmap, this with Architecture, Requirement & MAC subcommittees
- Brandon Wick- will collect additional information about the ONES event (virtual, F2F present, etc.)
- Catherine Lefevre: Plan CNF Task Force readout with the ONAP TSC
- Lukasz Rajewski - Ask Orange colleagues to present EMCO↔Multicloud comparison
- (All) Feel free to provide feedback about ASD packaging (Orchestration Scenarios)
- (Modeling/Requirements): Need to determine what ETSI CNF package solution we want to move forward (Fernando Oliveira, Byung-Woo Jun vs Thinh Nguyenphu)
- (Olivier): Check with CNCF if any cross-meeting with ONAP could be scheduled
- (All): Collect feedback about our current CNF onboarding capabilities from 3rd party vendors
- Try to locate missing meeting recordings (Sept 30th & Oct 14th, 2021) - Catherine Lefevre
- Lukasz Rajewski - Follow up with Seshu to plan EMCO integration