Versions Compared

Old Version 151

changes.mady.by.user Byung-Woo Jun

Saved on

compared with

New Version Current

changes.mady.by.user Catherine Lefevre

Saved on

Key

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

Meeting Minutes 

Table of Contents
maxLevel2

...

  • ONAP slide(s) for the LFN Cloud Native messaging - continue work on the slides

Action Items (In Progress)

  •  Ranny Haiby - Create a first draft of the "ONAP cloud-native" messaging slide and share with the Taskforce.
  •  Lukasz Rajewski - Ask Orange colleagues to present EMCO↔Multicloud comparison
  •  (All) Feel free to provide feedback about ASD packaging (Orchestration Scenarios)
  •  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
  •  (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

Action Items (Closed in 2021)

    • 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

August 5th, 2021 at 1pm UTC

August 12th, 2021 at 1pm UTC

  • ONAP slide(s) for the LFN Cloud Native messaging - continue work on the slides
  • ASD session - we are on waitlisted - Thinh Nguyenphu and virtual. No unconference this year but maybe room for ad-hoc meeting.

August 19th, 2021 at 1pm UTC

  • We had lower than average participation in the meeting today.
  • Brandon Wick is working with LF creative services. Will be ready for review in two weeks. Scheduled for Sep-2nd.
  • Any concern for Istanbul M3 (8/26)
  • ASD - Not much progress. Some Nokia folks on vacation.
  • Slides for ONES - We can re-use the cloud native roadmap slides, with minimal edits.

August 26th, 2021 at 1pm UTC

September 2nd, 2021 at 1pm UTC

  • Review ONAP Cloud Native journey slides after LF Creative services design. Gather feedback and produce final version - Brandon Wick
  • Slides for ONES - Are we OK with re-using the roadmap slides?
    • The topic of the session is CNF orchestration, so let's focus on slides #1 and #3.
    • Ranny Haiby - Add an introduction slide and create a draft slide deck for the ONE Summit.
  • ASD updates

September 9th, 2021 at 1pm UTC

September 16th, 2021 at 1pm UTC

September 23rd, 2021 at 1pm UTC

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

October 14th, 2021 at 1pm UTC

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 

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

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)

  •  (Thinh Nguyenphu) / Marian Darula / Byung-Woo Jun : Nokia and Ericsson share an alternative (Common CNF Packaging) to what was proposed by Fernando Oliveira , Byung-Woo Jun
  •  (All) Try to identify where we are on the CNCF Trail Journey - Needs clarification to comment, need to dig into the details of the actual ask.
  •  (All): Build an ONAP proposition value to collaborate with XGVela Community
  •  (Timo): Ask the Nokia team to present preview material on 1/26
  •  (Catherine): Contact Policy/DCAE/AAI/SO PTLs to attend January 26th CNF Task Force call to review Satoshi FujiiCNF Closed Loop proposal
  •  (Catherine): Send Calendar invite - every Tuesday @2pm UTC
  •  (Catherine): Reconnect with the CNF sub-Task force: Modeling/AAI (Andy Mayer) and ETSI (Byung-Woo Jun and Fernando Oliveira ) to understand their 2021 goals on January 19th 
  •  (
  •  (Thinh Nguyenphu) / Marian Darula / Byung-Woo Jun : Nokia and Ericsson share an alternative (Common CNF Packaging) to what was proposed by Fernando Oliveira , Byung-Woo Jun
  •  (All) Try to identify where we are on the CNCF Trail Journey - Needs clarification to comment, need to dig into the details of the actual ask.
  •  (All): Build an ONAP proposition value to collaborate with XGVela Community
  •  (Timo): Ask the Nokia team to present preview material on 1/26
  •  (Catherine): Contact Policy/DCAE/AAI/SO PTLs to attend January 26th CNF Task Force call to review Satoshi FujiiCNF Closed Loop proposal
  •  (Catherine): Send Calendar invite - every Tuesday @2pm UTC
  •  (Catherine): Reconnect with the CNF sub-Task force: Modeling/AAI (Andy Mayer) and ETSI (Byung-Woo Jun and Fernando Oliveira ) to understand their 2021 goals on January 19th 
  •  (Kenny): Follow up with EUAG in order to determine if any particular CNF reqs (or 2021 ONAP requirements including an update to the ONAP TSC)
  •  (Seshu/Lukasz): Invite EMCO representatives
  •  (Olivier): Organise a call with Trevor Lovettand any interested CNF team members to determine how ONAP could contribute to the OVP 2021 activities
  •  (Ranny): Post the topic for the event
  •  (Catherine) Check with Olivier Smithif we can postpone OVP/ONAP discussion to another week so CNF PDN Gateway discussions can be scheduled on  March 2nd, 2021
  •  (Victor Morales/ Ranny Haiby): Setup additional follow-ups about CNF PDN Gateway
  •  (Timo/Catherine): Promote 2021 goals from OVP program and collect any particular requirement through ONAP Requirement and TSC meetings
  •  (Kenny): Contact EUAG about any CNF badging requirement (OVP)
  •  (Seshu): Check if user-67d6f , Lei Huang , Yan Yang can join March 9th, 2021 to discuss about OVP/ONAP & VNFSDK
  •  (Thinh): Share the ETSI event link when it will be available
  •  (Seshu): Questions for XGVela

...

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

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