Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 105 Next »

Meeting Minutes 

Jan 4th, 2022 at 2pm UTC 

Jan 18th, 2022 at 2pm UTC

Jan 25th, 2022 at 2pm UTC

Feb 1st, 2022 at 2pm UTC

  • Chaker Al-Hakim Sharing suggestions for the CNF landing Page (E2E flows, HL diagrams)
  • Do we want to move the comments from the landing page to 2020 MoM etc?

Feb 8th, 2022 at 2pm UTC

  • Update on ASD
    • Result from [onap-modelingsub] Email Poll on ASD Information Model andPackaging Format Marian Darula , @Thinh Nguyenphu
      • Huawei is objecting  the ASD concept on grounds that it is not aligned with ETSI-NFV
      • During the poll there were no merit based objections. The only objection was the procedural one above.
      • ASD is seeing support in the O-RAN community. Thinh Nguyenphu (Unlicensed): Dropping ASD in ONAP might hurt it and put it behind other projects.
      • Marian Darula - There is a need to escalate the issue and reach a decision.
      • What could be the alternative? -
        • Fernando Oliveira : The ETSI proposal is capable and satisfactory, providing the necessary functionality without significant complexity.
        • Byung-Woo Jun : There was an attempt to align with ETSI. There were some challenges converting policies to VF module. The conclusion was this attempt  did not work well.
        • Marian Darula : There is a challenge synchronizing content between Helm chart and VNFD. That was the main concern by Ericsson that drove to the development of the ASD.
        • Thinh Nguyenphu (Unlicensed) : Another  motivation for ASD was parametrization, and the desire to  use cloud-native approach to that.
      • Can there (and should there) be one solution for packaging? Marian Darula - It was clear from day-1 of the ASD effort that there might be more than one approach. There was never an attempt to make ASD the only winning solution.
      • Marian Darula , Thinh Nguyenphu (Unlicensed) : If ONAP does not adopt ASD, the development effort might move to another community, leaving ONAP "behind".
      • Huawei is not objecting continuing the ASD PoC. 
      • Kenny Paul : The modeling subcommittee can make recommendations to the TSC, but ultimately it is a TSC decision.
      • POC definition Approved PoC policy since the Dublin release. A subcommittee cannot block a PoC,. All that is required is that the PoC needs to be reviewed with the committee.
      • Ranny Haiby : Any request to the TSC should be clear about keeping both approaches alive, and let them be developed in parallel, as alternatives.
      • Next  step: Bring this to the TSC to decide the future of the ASD PoC.
      • Timo Perala notes that REQ-993 - Getting issue details... STATUS is listed in Jakarta Release Requirements
        • note: this requirement covers ASD IM/DM. The ASD onboarding, distribution and LCM orchestration plans to be handled as a PoC during Jakarta. - Byung
    • Network Service modeling/ASD - Latest Updates - Byung-Woo Jun , Fernando Oliveira 

Feb 15th, 2022 at 2pm UTC

  • Clarify the benefits of ASD  over the ETSI-NFV SOL001
    • There was a  meeting on feb-14th on the modeling subcommittee  - no consensus reached - Modeling Subcommittee 2022-02-14
    • Decision was to escalate the decision to the TSC. The request from the TSC is to enforce adherence to the modeling subcommittee procedure. Andy Mayer - CLEAN state is a result of a subcommittee decision, based on rough consensus. The poll is just an input to the rough consensus. Xu Yang - "rough consensus" means there are no un-addressed objections. Marian Darula - the objection cannot technically be resolved.
    • Xu Yang -  Based on input from ETSI experts, it may be possible to unify the models.
    • Zu Qiang - Why is there an attempt to create a single model/package?  Xu Yang - There is no such limitation to have one model. The ASD model is referencing ETSI models.  Therefore it seems that it should be possible to find a unified model. For example, the ASD may become part of the ETSI-NFV NSD. Thinh Nguyenphu (Unlicensed) -  ASD is not "built around" ETSI models. It may reference ETSI, just like it may reference any other SDO. It may be a good idea to aspire for more alignment, but it  is inappropriate to block progress on the ASD initiative. Requests to follow the letter of the governing document (Approved ONAP Model Governance), and decide based on the poll.
    • Byung-Woo Jun - The ASD PoC is NOT using elements from ETSI (e.g., SOL005, SOL003, NFVO, VNFM), so it cannot reconcile, as it will require major changes in the ETSI specifications. The "ONAP Native" orchestration approach is planning to adopt ASD,  and is also not using ETSI specs. Why not use the same approach for the ASD and allow it to exist as an alternative?  Xu Yang - The ONAP Native approach was approved because there was no reference to ETSI and it seemed like a stand alone approach.
    • Xu Yang - Expectation from the TSC - Decide whether the current ASD proposal is technically mature enough, or does it need more work for reconciliation with ETSI?
    • Timo Perala -  Is there an estimated expected time line for the potential ETSI NFV - ASD aligned solution? For all I know it may easily take until 2023 to get there.
    • cl664y@att.com - What if ETSI endorses the ASD? Byung-Woo Jun - It  will require major changes in the ETSI MANO  architecture, may take time as stated above.
    • Xu Yang The ASD IM does make references to ETSI.  There are references to Virtual Links for example.
    • Zu Qiang - ASD Information model does not make a reference to ETSI. It may use identical attribute  names, but that can be changed to avoid confusion.
    • Thinh Nguyenphu (Unlicensed) -  TF (Catherine), ONAP MODCOM (Xu), ONAP-NFV Contact (Thinh) Bridge info: TBD Document depository: TBD (my recommendation is CNF TF wiki page) Tentative Agenda (information sharing and no decision making):
  • Prepare for Joint workshop with ETSI-NFV regarding ASD

Feb 22nd, 2022 at 2pm UTC

Mar 1st, 2022 at 2pm UTC

  • Prepare for LFN CNF workshop on Mar 13/14 - https://wiki.lfnetworking.org/display/LN/2022+LFN+DTF+Workshop+Topics
    • cl664y@att.com will work with EMCO (Bob Monkman) to prepare an integration proposal. Lukasz RajewskiRanny Haiby  will take part in the discussion

    • The goal is to have a clear roles and responsibilities definition for cases like the 5G super blueprint

  • ASD Model approval - Can we come up with a compromise proposal that will put everyone's mind at ease?
    • Focus on the technical aspects, not the procedural and vision aspects .
    • Keep the momentum going and avoid future re-work.
    • Path to move forward:
      • Work on 'definition" problem raised by Fernando Oliveira , Zu Qiang , Marian Darula  + Thinh Nguyenphu
      • Position ASD Model as an alternative to current ETSI Standard proposal to move forward with "Cloud Native Architecture"
        • ASD implemented as plug & play (you choose onboarding ASD / ETSI / others)
        • Known Impacts: SO e.g. CNF O (particular Camunda) + SDC /AAI (to be determined by POC work) + particular VES Collector - Byung-Woo Jun to review this part 
      • Work with the Modeling Team cl664y@att.com 
      • Continue to share to ETSI what we do Thin, Byung-Woo Jun  - increase visibility

Mar 8th, 2022 at 2pm UTC

  • Follow up on ASD Model Action Items
    • Work on 'definition" problem raised by Fernando Oliveira , Zu Qiang , Marian Darula  + Thinh Nguyenphu.
      • Presentation by Marian Darula - <please upload deck here>
      • Reviewed the difference in approach between ASD and ETSI - ASD adds a "slim" descriptor that only fills the gaps of the Helm charts. The ETSI approach creates a full SOL001 IFA11 descriptors with the full set of attributes. The ETSI approach may lead to duplication of information and two separate entities trying to control the lifecycle of the CNF (orchestrator and K8S)
      • The ASD approach is using the IM of K8S/Helm
      • Fernando Oliveira - Contention point is about the variation between IM and implementation. The old ECOMP model or ETSI model is satisfactory,  there is no need for a new IM.
      • Zu Qiang - Explains the xNF modeling with ASD
      • lishitao - There is no real duplication with the ETSI approach - Many of the attributes are  optional. The comparison of LCM approaches may not be accurate
      • Thinh Nguyenphu (Unlicensed) - In reality, it is not possible to use IFA11 to model a CNF.  Ericsson tried that in the last two releases and proved it cannot  be done. ONAP does not  have a general CNF IM. The ASD goal is to simplify the onboarding of CNFs, removing the need for VNFM
      • Thinh Nguyenphu (Unlicensed) - Proposes to respond to Fernando Oliveira 's comments
      • guochuyi - It sounds like there is a need to continue the technical aspects in the modeling subcommittee. Proposes to use the upcoming meeting for this technical discussion.
      • Thinh Nguyenphu (Unlicensed) , Marian Darula - What is the point of continued discussion?
      • cl664y@att.com - We need to move forward with implementation. Let's treat the ASD IM as v1, and work towards a v2 that will address the concerns of the modeling subcommittee.
      • AI  - Marian Darula - upload the existing ASD model as a v1
      • AI  - cl664y@att.com - Will follow up in the TSC.
  • Presentation ONAP/EMCO Alignment prior LFN DDF
  • No meeting on Mar 15th - replaced by LFN CNF workshop

Mar 22nd, 2022 at 2pm UTC

  • Feedback from the LFN DTF Event:
    • CNFs
    • EMCO/ONAP Alignment
      • There are clearly two profiles. Not clear how to make progress on both
      • Issue with profile #2 - How to use the policy functionality of ONAP, without the inventory components.
      • Seshu Kumar Mudiganti - We should go to the next level of details on the integration points between ONAP and EMCO - We need a simple use case. 
      • What use case should we start with? We should find a use case that demonstrates the value of the integrated solution. It should showcases functionality that is not available with ONAP-only or EMCO-only.
      • Seshu Kumar Mudiganti - Who is responsible to turn the wishlists to implementation? Who will take responsibility?
      • Lukasz Rajewski - What is the right motivation for profile #2? Is it to make the solution lightweight? Is it to address edge use cases?
      • Vishal Sharma  - Initial use case UDC on a single cluster or multiple clusters. Might be on-prem (OpenShift) cloud or public cloud. Lukasz Rajewski - Deployment on public cloud might require EMCO, as it is not currently supported by ONAP. Seshu Kumar Mudiganti - No guarantee upfront that the UDC will work out of the box. Experience shows it might require some tweaking. Seshu Kumar Mudiganti - Suggests to start with ONAP-only, then identify gaps where EMCO may be useful.
      • Vishal Sharma - Slicing scenarios might require multiple clouds, which calls for EMCO. Lukasz Rajewski If 3GPP slice API are required, they are not provided by EMCO. ONAP does provide this API.
      • Vishal Sharma - Mentioned the AMCOP solution from Aarna Networks, that uses EMCO API for 5G Core deployment, and ONAP CDS for Day-1/2 configuration.
      • Vishal Sharma - How can ASD be used today? Especially when ETSI is still working on specifications? Marian Darula - There is documentation and on-going PoC. Byung-Woo Jun is the main contact person for more information. On-boarding and deployment are expected to be completed in the Jakarta time frame. PoC wiki space - ASD-Based CNF Orchestration PoC
      • Vishal Sharma - Will provide future updates on his progress using the CNF Taskforce mailing list, wiki, or meeting.
    • Next Steps
  • Decision on new meeting time
    • Starting next week the meeting will be at 13:00 UTC
  • Are we good with ASD Information model? What are the next steps?
    • No immediate blockers.
    • @thinh - There is a planned workshop with ETSI today. At the moment there is no plan for further workshops


Mar 29th, 2022 at 1pm UTC (← New time!)

  • ASD PoC Status update - Byung-Woo Jun 
    • SO and SDC teams from Ericsson are working on the PoC
    • SDC team is working on the resource VF. working on TOSCA parser. Map ASD into VF, Wrap in CSAR and distribute.
    • SO team working on LCM swagger definition for northbound API. Waiting for creation of PoC branch. Focusing on calls from BPMN to CNFM.
    • Lukasz Rajewski - Will the ASD LCM API be integrated with the rest of the LCM API? 
    • The PoC handles onboarding and instantiation with variables.
    • Slide deck - Byung-Woo Jun , ASD-PoC-Status-20220329.pdf
    • Vishal Sharma - ETSI is expected to come up with SOL003 specifications, is there work planned to support it? Byung-Woo Jun , Fernando Oliveira - There is definition work ongoing for the ETSI approach, but actual development has not yet started.
    • Target for PoC - Initially was Jakarta, but now it is clear some functionality will slide into Kohn

Apr 5th, 2022 at 1pm UTC 

  • Updates from ETSI workshop - @Thinh
  • Attendance in today's meeting is lower than usual and we are missing some key people. Should we re-visit the meeting time? Ranny Haiby will follow-up on the mailing list.

Apr 12th, 2022 at 1pm UTC 

  • Low attendance. New meeting time? Poll - https://doodle.com/meeting/participate/id/axkGzYqe
  • Update from the requirements workgroup - Ranny Haiby 
  • Question - How does EMCO fit the picture with ASD? What can ONAP delegate to EMCO? What will be mapped to EMCO's "composite application"?
  • Byung-Woo Jun - It should be possible to create an adapter from CNFO to EMCO, but more details are required, expecting to learn from Seshu Kumar Mudiganti's experimenting with EMCO.
  • some update from Catherine: Raghu from aarna will be on the enterprise meeting tomorrow to update us about ONAP/Magma integration.
  • Project Nephio - To be announced this week. 
  • Updates from ETSI workshop - @Thinh
    • The last workshop was about handling the Q&A from previous meeting. No action items
    • The ETSI-NFV folks understand the rationale behind ASD. 
    • Future collaboration will probably take place through our modeling subcommittee.
    • Current modeling work is focused on the ETSI-alignment path. 


Apr 19th, 2022 at 1pm UTC 


Apr 26th, 2022 at 1pm UTC 

  • Update from Seshu Kumar Mudiganti on SO EMCO integration.
  • Nephio update - The project TSC meetings are tentatively scheduled to start on the week of May 9th. ONAP project members are welcome to join and ask questions. Once an official invite is sent, Ranny Haiby will share it on the CNF Taskforce mailing list.
  • Reach out to Seshu Kumar Mudiganti over email to figure out best time for him to attend (AI Ranny Haiby )

May 3rd, 2022 at 1pm UTC 

  • ?

May 10th, 2022 at 1pm UTC 

  • Meeting is cancelled - no topics to discuss.
  •  Nephio:
    • F2F Hybrid Nephio community event is scheduled for June 22&23 (US Pacific time zone). Ranny Haiby will share more details as they become available.
    • TSC weekly meetings starting on May 17th (Please reach out to Ranny Haiby if you would like to have the invite forwarded)


May 12th, 2022 at 1pm UTC - Special Thursday meeting

  • SO Integration with EMCO - Discussion with Seshu Kumar Mudiganti 
    • The motivation for the PoC is to show that the EMCO/ONAP integration is technically not that complicated
    • Integration required little to no changes in SO
    • Proves the "plug and play" approach in SO works.
    • No changes required in EMCO
    • PoC available in Azure lab
    • Focused on instantiation, Day1. Day2 and control loop are planned.
    • Using a Face Recognition app
    • The "Deployment Intent" functionality of EMCO is supported, allowing EMCO to automatically select the K8S cluster for deployment.
    • Marian Darula - Question about modeling of the EMCO intent. Seshu Kumar Mudiganti - The EMCO modeling is done in an opaque way for the user - there is no exposure of the EMCO intent during the service design.
    • Request to share the code of the PoC. Seshu Kumar Mudiganti will make it available.
  • Nephio Technical Summit:
    • F2F in Silicon Valley + Virtual
    • June 22&23 
    • Registration will be open soon 
  • New weekly meeting time
    • #agreeed to move the weekly meeting to Thursday 1PM UTC, starting next week.

May 19th, 2022 at 1pm UTC 

  • 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) (cl664y@att.com )
    • 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?  (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. (Former user (Deleted) )

    • Olivier Smith presented the different certification types of Anuket Assured, present and future. 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



  • 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

Action Item(s) (Closed in 2022)


  • No labels