...
Gliffy Diagram | ||||
---|---|---|---|---|
|
CNF Package Onboarding and Distribution
The following diagram depicts CNF package onboarding and distribution.
Gliffy Diagram | ||||||
---|---|---|---|---|---|---|
|
- 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
- <note: it is under discussion that ETSI Catalog Manager pushes the helm charts from the CSAR to a MANO local helm charts repository if we use the helm charts 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 CISM for CNF operations
- K8S CISM pulls Container Images from the CIR
CNF Models
- Conforms to ETSI IFA 011, 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 an MCIO described in declarative descriptors and relevant being exposed to NFV-MANO are mirrored in attributes of the descriptors of the corresponding objects of the existing NFV-MANO information model.
...
- Use VipCp to model K8S service connectivity (under discussion)
- AdditionalVipData – Expose information about a port and service data
- Name of the VIP (uService)
- L4 Protocol exposed (TCP, UDP, SCTP, )
- Port exposed
- intCpd attribute is optional (changes from 1..N to 0..N)
- Service Data
- L7 info (unspecified in VNF-D)
CNF Package Onboarding and Distribution
The following diagram depicts CNF package onboarding and distribution.
Gliffy Diagram | ||||||
---|---|---|---|---|---|---|
|
- 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
- <note: it is under discussion that ETSI Catalog Manager pushes the helm charts from the CSAR to a MANO local helm charts repository if we use the helm charts 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 CISM for CNF operations
- K8S CISM pulls Container Images from the CIR
SOL001 VNFD Mapping to SDC AID DM
...