The following depicts the ETSI-based CNF support.
Summary
- Hybrid orchestration templates – TOSCA VNFD and Helm Charts (MCIO)
-TOSCA VNFD drives the interaction between NFVO and VNFM and NS/VNF LCMs
-Helm Charts are included as a binary archive in the VNF package, and are consumed by VNFM
- Container images are either included in the VNF package or referenced in the descriptors (URL to CIR)
-If the VNF package includes Container images, NFVO/ETSI Catalog Manager uploads them to the CIR
-Otherwise, operators store Container images to the CIR
- Parameter mapping from Or-Vnfm (SOL003) incoming information to Helm input parameters
- Resource Mapping between resources in TOSCA VNFD and K8S resources described in Helm chart (for granting between VNFM and NFVO)
- Mapping the LCM operations to HELM commands (VNFM behavior triggered on Or-Vnfm), etc.
- VNFM-K8S communication prefers Helm APIs to lower level K8S APIs
- K8S-VIM communication uses de facto open source standards (Nova/Cinder/Neutron/Keystone/Octavia)
- CISM-CIS communication uses de facto open source standards
The ETSI-based CNF support is conforming to IFA029 and IFA040. Based on the ETSI specification progresses, we plan to apply necessary changes.
ETSI NFV Team's Modeling Challenges
- Package multiple NFs into a single CNF and manage them independent from each other. (Deployment flavors, aspects, …)
- Building an NF which spans multiple CNFs. The single CNF would not necessarily be a self-sufficient entity anymore. (Network Services)
- CI/CD based upgrades of microservices within a CNF. (ChangeVnfPackage)
