...
- 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 the MCIO’s relevant to be exposed to 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.
<Source: IFA 040>
- SDC enhancements to understand and parse new IFA 011 VNFD
- AAI enhancements to represent VNF instance inventories, based on IFA 011
- NFVO/VNFM enhancements to handle new NS/VNF models and packages
...
- Conforms to new ETSI IFA 011.
- ETSI NFV Team Discussions and Resolutions:
- VNFD enables the modelling of MCIOs (e.g., Kubernetes Pods) as VDU and introduces a new IE OsContainerDesc.
- A VNF could consist of VM-based and/or container-based components (hybrid VNF) – at least one of them
- Either the virtualComputeDesc or the osContainerDesc, but not both
- The relationship between the NFV abstract objects and their relationship have been described in IFA 049 040 (clause 5.3)
- Changes due to differences between networking in VM-s and in pods shall be investigated
- The properties of MCIOs specifying networking resource requests can be modelledAs modeled as CPs or derived classes and their properties are specified in CPDs or derived types in the VNFD
- Each reference of an identifier of an OsContainerDesc is unique; each OsContainerDesc is only referenced once in a VDU. This is in alignment with the Kubernetes PodSpec
- No hybrid VNFCs shall be allowed
- intCpd attribute of the VDU information element is changed from 1..N to 0..N.
- VNFD Note 6: Either the virtualComputeDesc or the osContainerDesc shall contain at lease one element
- VDU Note 5: Only one of virtualComputeDesc or osContainerDesc shall be part of a Vdu. If the Vdu includes osContainerDesc, then bootOrder, swImageDesc, monitoringParameter and bootData shall not be present in the Vdu.
- The following tables depicts the changes in the VNFD and VDU attributes:
...
- Reason for change:
- An important object which is to be included in the VNF package is the MCIOP. The MCIOP needs to be identified in the VNF package, but also additional properties of the MCIOP are required to be specified.
- This information related to the MCIOP needs to be provided via a dedicated profile information element for the MCIOP.
- Change:
- Add a descriptor information element for a MCIOP profile to the VnfDf.
- Enhance the scope attribute of the AffinityOrAntiAffinityGroup information element with a new scope type “container-namespace”.
- The “container-namespace” scope is used to express the affinity or anti-affinity relationship between containerized workloads which are deployed based on a MCIOP.
- A Managed Container Infrastructure Object Package (MCIOP) is a hierarchical aggregate of information objects for OS container management and orchestration.
- Multiple MCIOPs can be included in a VNF Package.
- The MciopProfile information element provides properties of the MCIOP which are used during deployment of containerized workloads based on a MCIOP, associated to a VNF deployment flavor.
Access Information for VNF Package Content
...
OsContainerDesc
- The OsContainerDesc information element describes the members properties of a set of co-located container compute resources when these are realizing a VDU.
- OsContainerDesc Attributes are defined
...
- The VNFD introduces a new resource template OsContainerDesc for OS containers.
- The ResourceDefinition information element used in the grant request message needs to be enabled to reference resource templates for OS containers, the same way as the other resource template
- Enhance the ResourceDefinition information element attributes with references to OS container resource definition types and resource templates.
- OsContainer Type is added
- Reference to OsContainerDesc is added
IFA 011 411 Draft Proposal addition to VipCpd
- VipCpd in SOL001 2.7.1 describes the mapping of a “virtual IP” address to connection points in a VNF.
- Either HA (Active/Standby) or Load Balancing.
Proposed for 4.1.1
- 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
...
- 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 CSIM for CISM for CNF operations
- K8S CSIM CISM pulls Container Images from the CIR
...