Topic Leader(s)
- CNF Orchestrator: Lukasz Rajewski , Seshu Kumar Mudiganti
- ETSI Alignment & CNF: Fernando Oliveira, Byung-Woo Jun
- CNF Task Force Leads: Ranny Haiby, Catherine Lefevre
Topic Overview
This session will be an interactive one. The leaders of this activity will provide a quick recap of the work done so far, and then open the floor for questions and suggestions. The Taskforce is very much interested in the priorities of the community with regards for making ONAP orchestrate Cloud Native network functions. Anyone who is interested Cloud Native Network Functions (CNF) is welcome to join this session and share their thoughts on this subject.
Slides & Recording
Slides
Recording & Chat
Agenda
Awesome presentation
- (20 mins) - Where we are - covered through demo - Lukasz Rajewski, Seshu Kumar M
- (10 mins) - Recap Honolulu requirements (ETSI ) Fernando Oliveira, Byung-Woo Jun + (CNF Orchestration) Seshu Kumar M, Lukasz Rajewski
- (30 mins) - Open discussions - Ranny Haiby
- Collecting feedback from the ONAP Community or external Communities/SDOs about 2021 CNF priorities
- Call for new requirements?
- Call for developers
Minutes
- Live demonstration of our CNF Orchestrator based on ONAP Service Orchestrator (SO):
- Onboarding of CNF package via ONAP Service Design & Creation (SDC)
- Update/Configuration Helm Package
- Presentation of SDC (Onboarding/Design) ETSI Alignment Enhancements (SOL004/SOL007), package distribution for CNF, Alignment with CNF/O-RAN O2, SO NFVO (SOL003)- Adapter refactoring
- There is an on-going synchronization between SO and ETSI, to make sure there is a unified data model.
- https://wiki.onap.org/display/DW/ETSI-Alignment+Architecture+-+Honolulu
- Clarifications about K8s Orchestrator and ONAP Orchestrator added-value
- Interested - Join us
:- ONAP CNF Task Force - Weekly call every Tuesday @2pm UTC - https://lists.onap.org/g/onap-meetings/viewevent?repeatid=31872&eventid=1040241&calstart=2021-02-16
- ETSI TF meeting, every Monday from 12-1 UTC - https://wiki.onap.org/display/DW/Orchestration+Scenarios
- More info here: ONAP CNF Wiki page: https://wiki.onap.org/display/DW/TSC+Task+Force+-+Cloud+Native
Q&A
- Q:@Seshu, We used to have SDC Client in Multi-Cloud project to get notified whenever NS/VNF package is onboarded in SDC, and if it is Helm related NS/VNF package, then it used to upload that in "Multi Cloud K8s plugin". With the CNF adapter in SO, is that SDC Client still required?
Srini Addepalli (Intel) to Everyone (5:39 AM)- A: Yes Srini, the notification is still there in place as of Guilin to keep the backward compatibility
- Q: @Seshu, Second question: Does CNF adapter call Multicloud-k8s APIs directly or the flow is still via Multi Cloud APIs & Multi Cloud broker?
SaiSeshu MUDIGANTI (Huawei) to Everyone (5:39 AM)- A: @Srini, we make the direct API call
its not through MC
we intent to extend it further it to the V2 API in future
- A: @Srini, we make the direct API call
- Q: Vijay Venkatesh Kumar - What about monitoring and control loop
- A: DCAE is on the todo list, but not started yet. Prometheus is a candidate for telemetry, may be an alternative to VES
- What is your recommendation for end users - should they experiment with CNF orchestration in Guilin? Wait until Honolulu is out?
- Guilin maintenance release has all the functionality presented today
- Where is the documentation for CNF on-boarding and deployment?
- The vFW CNF Documentation has all the necessary details
- How could developers get involved? Where do you mostly need help?
- See the "Interested - join us" section above in the minutes. Everyone is welcome to join the conversation and start contributing.