...
- Low attendance. New meeting time? Poll - https://doodle.com/meeting/participate/id/axkGzYqe
- Updates from ETSI workshop - @Thinh
- Update from Seshu Kumar Mudiganti on SO EMCO integrationUpdate from the requirements workgroup - Ranny Haiby
- Sign up page https://wiki.lfnetworking.org/display/LN/Requirements+and+Use+Case+Advisory+Group
- Lukasz Rajewski - The chosen integration option will most likely be influenced by whoever steps up to implement the integration
- 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
- Low attendance. New meeting time? Poll - https://doodle.com/meeting/participate/id/axkGzYqe
- Looks like there is no clear preference.
- We are still missing some key folks such as Seshu Kumar Mudiganti
- Reach out to Seshu Kumar Mudiganti over email.
- Analysis Mason report - https://oneef2022.sched.com/event/zxHD/cloud-transformation-benchmark-how-ready-are-csps-for-cloud-native-networks-caroline-chappell-analysys-mason-heather-kirksey-the-linux-foundation
- Some good data in the report about the motivation of CSPs to go cloud-native.
- Interesting information about open source activity from CSPs - looks like there is potential to recruit more players to our open source communities.
- Project Nephio - Take a deeper look.
- https://nephio.org
- This approach will require different packaging of CNFs. It does not rely on Helm charts
- It seems that Nephew is "K8S intrusive" and requires support from the underlying K8S.
- It is not clear if Nephio is a replacement for something like EMCO
- The ASD approach might support CRDs instead of Helm charts, but it will require a deeper analysis of how this might work.
- How will ONAP CDS interact with Nephio? What will configuration CRDs look like under Nephio?
- Will Nephio become an integral part of K8S? Since it is backed by Google, there are chances it will be.
- Request to have Nephio project leaders share information with this Taskforce - AI Ranny Haiby
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?
- Byung-Woo Jun - Not decided yet - Health safety concerns
- Fernando Oliveira - Will attend remotely
- Ranny Haiby - Will attend in person
- ONAP CNF sessions/demos
- 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
- 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 )
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
- (Reminder - record the meeting)
- ONE Summit CFP is open until July 29th - https://events.linuxfoundation.org/one-summit-north-america/program/cfp/
- A great opportunity to share our experience with a broader audience.
Plans of ASD integration into ONAP, beyond the PoC phase.
- Concern about the separate flows/API endpoint for CNF orchestration using ASD.
- Need input from Ericsson about the effort to merge the flows.
- ASD PoC Update and Plans presentation slide deck, ASD-PoC-Update-Plans-2022-07-14-v3.pptx
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
- (Reminder - record the meeting)
- Follow up questions related to the ASD PoC presentation from July 14th
- Alignment with Nephio, CNF-WG under CNCF, and other initiatives
- Nephio weekly meetings started:
- ASD update - The team is working on a good reference CNF.Started looking at Magma using Helm charts provided by Aarna.
- https://github.com/electrocucaracha/gw-tester - This could be an option. "Reference CNF" created by Victor Morales
- We may want to invite Victor Morales to one of our upcoming CNF Taskforce meeting, to discuss both the reference CNF and the CNF-WG which he co-chairs. Ranny Haiby will reach out to him.
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
- (Reminder - record the meeting)
- Review and update the ONAP CNF landing page (TSC Task Force - Cloud Native)
- Add Jakarta release highlights to section 2 TSC Task Force - Cloud Native#2.Workaccomplishedandavailablefunctionality
- Update roadmap section - Remove items that are completed or no longer relevant. Add new items - TSC Task Force - Cloud Native#3.Futureroadmap
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
...