...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
****** Moved to actual landing page - please make all edits there and not here! ******
CNF Taskforce Meeting Minutes
Table of contents:
| Table of Contents |
|---|
...
1.1.1 Evolving from VNFs to CNFs
1.1.2 ONAP as a CNFO
- Hybrid services CNF/VNF/PNF, leveraging open-source
and standards- Support Greenfield and Brownfield environment
- E.g., CNF on bare-metal, CNF on VM, VNF on VM, PNF
- Day 0/1/2 configuration
- Not just infrastructure orchestration
- Configuration and Update
- Standard alignment (ETSI, 3GPP) and beyond (ASD)
- Evolve existing investment, no need to start from scratch
- Common Infrastructure for model/package onboarding, design and distribution
- Support both ETSI-Aligned and Cloud Native Orchestration
- 5G slicing use case – 3GPP compliant
1.2 ONAP as a Cloud Native application
TODO: Break digram into two sections.
1.2.1 Relationship with SDOs
1.3.1 ETSI-NFV - Alignment on packaging
...
- Application Service Descriptor (ASD) - the modelling and packaging approach for CNFs, rAPP/xApps.
- O-RAN: ASD solution
1.2.2 Alignment and integration with other Open Source
...
Projects
- EMCO
- CNCF - K8S
- 5G Super blueprint
- Anuket
2. Work accomplished and available functionality
...
- Deployment maturation and Day2
- Improvement of Helm Distribution (SDC/SO)
- Helm Deployment Maturity
- Helm package validation
- Helm 3.5
- Helm pre-/post-installation/deletionhooks
- Simple CNF Healthcheck
- Basic AAI CNF Changes
2.2 Honolulu
3. Future roadmap
- Support for 5G Super Blueprint & Magma CNF orchestrations requirements
- New joint onboarding package to design the NS with CNFs
- Merging the paths of the Native Helm & ETSI flows
- Enhance the CNF resource orchestration functionalities further
- Multi-cluster deployment with inter-cluster connectivity setup
- CNF Upgrade
- Coordinated CNF components deployment
- Runtime model evolution based upon the standard
- AAI persistence of the CNF resources
- Control loop enhancements for CNFs
- Cluster management and CNF observability (integration with XGVela)
- Prometheus based monitoring in DCAE
...
- documentation
- Jira items in progress for the current release
4.2 Demos
- Recording from June 2021 DDF
- ONAP: Orchestration of xNF Based 5G Service
- ONAP: CNF Orchestration Tutorial
5. FAQ
Q: What is the value-add of ONAP for CNF orchestration (CNFO)? What does it provide on top of K8S?
...
- You can create a JIRA ticket - https://jira.onap.org/
- You can post any question on the #integration-team channel in the onapproject.slack.com Slack instance
- You can also join the CNF Task Force, every Thursday prior the ONAP TSC Call (1pm UTC) calendar link
- You can also write to the onap cnf mailing list - onap-cnf-taskforce@lists.onap.org
...
- Call for developers to implement in Jakarta new features:
- CNF Control Loop
- Integration with XGVela
- Merging Native Helm/ETSI flows
- Entreprise use cases
- etc
- Istanbul CNF Orchestrator Requirements:
REQ-627 - ONAP CNF orchestration - Istanbul Enhancements DONE - Those are the short term goals. Have a great deal more in the backlog for future released. refer to 2021-06-09 - ONAP TSC Taskforce: Cloud Native (Roadmap)
...
- No integration with C&PS, but it may happen at a later stage. But this is a good approach and may be discussed further in the CNF Taskforce.
Q: Does the CNF Orchestration support only Openstack VF-Module?
A:
- VF Module is the design aspect of the SDC, we represent each helm with a VFM. The current processing is per VFM for CNF as it is with the other resources
Recent Presentation Material
2022-01-13 - ONAP: Orchestration of xNF Based 5G Service
2022-01-12 - ONAP: ASD and Application Onboarding and LCM Orchestration
2022-01-12 - ONAP: Application Service Descriptor (ASD) for K8s NFs
2022-01-11 - ONAP: CNF Orchestration Tutorial
2021-10-12 ONE-Summit_Cloud_Native_Service_Orchestration_ONAP v0.4.pptx
...