The ETSI-based CNF support is conforming to IFA029 and IFA040. Based on the ETSI specification progresses, we plan to apply necessary changes.
Mission Statement
- TBD
Benefits
- TBD
ETSI NFV Team's Modeling Challenges
- Mapping VNF-Descriptor to SDC AID DM?
- How to identify Pods in AAI?
- 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)
ETSI-Based CNF Orchestration Architecture
- 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
- It leverages the ONAP ETSI-Alignment Architecture.
The following diagram depicts ETSI-based CNF orchestration architecture.
CNF Models
- Conforms to ETSI IFA 029 and 040.
- Those specifications would be available by end of June / July 2020, but their SOL specifications plan to be available by end of 2020 or Q1, 2021.
- Until then, ONAP designs CNF models and packages, based on the current IFA 029 and 040 (it is an assumption).
- A Managed Container Infrastructure Object (MCIO) is an abstract NFV object for OS Container management and orchestration.
- The declarative MCIO descriptor is used as descriptor object interpreted by the CISM.
- A MCIO is created by the CISM by allocating its requested infrastructure resources on Container Infrastructure Service (CIS) instances
- Depending on its type, the creation of a MCIO may include the deployment of an OS Container Image.
- MCIO’s are lifecycle managed via change requests on their desired state, utilizing a modified declarative descriptor sent to the CISM, which adapts the
- infrastructure resource allocations according to the changed infrastructure resource requests.
- MCIO’s requesting compute and/or storage infrastructure resources are modeled as a VNF Component (VNFC).
- Properties of the MCIO’s relevant to be exposed to NFV-MANO.
<Source: IFA 040>
CNF Package Onboarding and Distribution
The following diagram depicts CNF package onboarding and distribution.
- OSS/BSS onboards SOL004 VNF package to SDC
- SOL004 VNF package consists of:
-SOL001 VNFD with Helm Chart References
-Helm Charts (hierarchical)
-Mapping Scripts
-Container Images / References
- SDC preserves the SOL004 VNF Packages in the Onboarded_Package directory of SDC Resource CSAR
- SDC Service CSAR including SDC Resource CSAR(s) is distributed to ONAP Runtime components: SO, AAI, VID and others
- ETSI Catalog Manager extracts the SOL004 VNF Packages and stores in its Database
- If VNF Package contains Container Images, ETSI Catalog Manager pushes the images to Container Image Repository
- SOL003 Adapter gets SOL004 VNF packages from ETSI Catalog Manager
- SOL003 Adapter sends SOL004 VNF packages to sVNFMs
- Optionally, if operators use local CIRs, VNFM can push the Container Images to the local CIRs.
- SVNFMs invokes K8S CSIM for CNF operations
- K8S CSIM pulls Container Images from the CIR
SOL001 VNFD Mapping to SDC AID DM
- TBD
ONAP Component Requirements
SDC
- TBD
SO
- TBD
SO NFVO
- TBD
SOL003 Adapter
- TBD
ETSI Catalog Manager
- TBD
AAI
- TBD
VID
- TBD
UUI
- TBD
OOF
- TBD
CIR
- TBD