4.2.1 changes fix some issues around VipCP and supporting OsContainer based VNFs

Changes from v4.1.1 ETSI IFA011 v3.3.1 & v4.1.1 Changes to ONAP Resource Model.

New Classes/Types:

1. New Class  VirtualCpd.  New datatypes AdditionalServiceData and ServicePortData 

Other changes:

1. New property vnfd::osContainerDesc of type OsContainerDesc with cardinality 0..N which defines descriptors of container compute resources to be used by the VNF when the VDUs of the VNF are realized by a set of OS Containers sharing the same host and same networking namespace.  Only one of virtualComputeDesc or osContanerDesc may be present in the vnfd
2. New property vnfd::virtualCpd which describes a virtual connection point(s) allowing to access a set of VNFC instances (based on their respective VDUs).
3. New property VnfExtCpd::virtualCpd which references the Virtual CPD which is used to describe a virtual connection point allowing to access a set of VNFC instances (based on their respective VDUs). 
4. New property vdu::osContainerDesc of type identifier (Reference to osContainerDesc) with cardinality 0..N which describes CPU, memory requirements and limits, and software images of the OS Containers realizing this Vdu corresponding to OS Containers sharing the same host and same network namespace. Each unique identifier is referenced only once within one VDU.
5. Modification of VduCpd::vnictype to include several new types (BRIDGE, IPVLAN, LOOPBACK, MACVLAN, PTP, VLAN, HOST-DEVICE)
6. Modification to the cardinality of SwImageDesc::diskFormat, SwImageDesc::minDisk to allow cardinality of 0..N
7. New property VndDf::mciopProfile of type mciopProfile with cardinality 0..N which describes additional instantiation data for the MCIOPs used in this deployment flavour. This attribute shall be present if the DF references containerized workloads based on a MCIOP.
8. New property VirtualStorageDesc::volumeTemplate of type Boolean with cardinality 0..1 which indicates whether the virtual storage descriptor shall be used as template, i.e. if the virtual storage resource shall be instantiated per VNFC instance. If the value is true (default), a persistent virtual storage resource shall be instantiated for each VNFC instance that is based on a VDU referring to this virtual storage descriptor. If the value is false, a single persistent virtual storage resource shall be instantiated with a lifetime independent of the lifetime of individual VNFC instances based on a VDU referring to this virtual storage descriptortype VipCpProfile

2.New type VipCpLevel

3. New type LcmCoordinationActionMapping

Other changes:

1. New property Vnfd::vnfdExtInvariantId of type Identifier -Identifies a VNFD in a version independent manner. This attribute is invariant across versions of the VNFD that fulfill certain conditions related to the external connectivity and management of the VNF. Different versions of a VNFD have different vnfdIds but can have the same vnfdExtInvariantId. Different versions of the VNFD with the same vnfdExtInvariantId shall expose:

   • same external connectivity, i.e. same number of vnfExtCpds and same identifiers

   • same VNFD attributes used in an NSD when referring to this VNFD:

     • VNF deployment flavours, VNF instantiation levels: in both cases the identifiers and the number of them shall be the same, but the content of e.g. a particular deployment flavour can change
     • VNF indicators: same identifiers and possible values

     • ScaleInfo: same scalingAspects identifiers and same levels per scalingAspect

   This condition implies that VNFDs with the same vnfdExtInvariantId preserve external invariancy. Therefore, fulfilling this condition allows to use a different version of a VNFD in an NS instance without modification of the NSD on which the NS instance is based. The use of a different version is ultimately under the control of the service provider and it should consider if the NSD fulfils the requirements of the VnfExtCpds (e.g. bitrate, IP version, etc.).

2. New property Vdu::logicalNode of type LogicalNodeRequirement - The logical node requirements.
3. New property Vdu::requestAdditionalCapabilities of type RequestedAdditionalCapabilityData - Specifies requirements for additional capabilities. These can be for a range of purposes. One example is acceleration related capabilities.
4. New property Vdu::mcioConstraintParams of type Enum - The parameter names for constraints expected to be assigned to MCIOs realizing this Vdu. The value specifies the standardized semantical context of the MCIO constraints and the parameter names for the MCIO constraints in the MCIO declarative descriptor. The mcioConstraintParams attribute shall have one of the following values, expressing the associated semantical context.

   • affinityNfviPop

   • affinityZone

   • affinityZoneGroup

   • affinityNfviNode

   • affinityCisNode

   • antiAffinityNfviPop

   • antiAffinityZone

   • antiAffinityZoneGroup

   • antiAffinityNfviNode

   • antiAffinityCisNode

   • localAffinityNfviPop

   • localAffinityZone

   • localAffinityZoneGroup

   • localAffinityNfviNode

   • localAffinityCisNode

   • localAntiAffinityNfviPop

   • localAntiAffinityZone

   • localAntiAffinityZoneGroup

   • localAntiAffinityNfviNode

   • localAntiAffinityCisNode

   • nodeAdditionalCapabilitySsd

   • nodeAdditionalCapabilityDpdk

   • nodeAdditionalCapabilitySriov

   • nodeAdditionalCapabilityGpu

   • nodeAdditionalCapabilityFpga

   • nodeAdditionalCapabilityCpuPin

   • nodeCapabilityLogicalNuma

   • nodePool

5. New property VnfDf::vipCpProfile of type VipCpProfile - Defines the minimum and maximum number of VIP CP instances created from each of the VipCpds used in this flavour. Shall be present if the deployment flavour can contain VIP CP instances.
6. New property VnfDf::supportedCoordinationActions of type LcmCoordinationActionMapping - References applicable LCM coordination actions that can be invoked during each of the listed VNF LCM operations.
7. New property InstantiationLevel::vipCpLevel of type VipCpLevel - Indicates the number of VIP CP instances based on a particular VipCpd to be part of this level. If a particular VipCpd is defined with minNumberOfInstances= maxNumberOfInstances=1 in the vipCpProfile of the DF, that vipCpd may be omitted from the "vipCpLevel" attribute, which shall be interpreted that one related VIP CP instance is part of this level.
8. Changed VirtualStorageDesc::volumeTemplate property name to VirtualStorageDesc::perVnfcInstance
9. New property ScalingDelta::vipCpDelta of type VipCpLevel - Number of VIP CP instances based on a particular VipCpd to be created or removed.
10. New property VipCpd::intVirtualLinkDesc of type Identifier - Reference of the internal VLD which this VipCpd connects to.
11. New property VipCpd::dedicatedIpAddress of type Boolean - If set to true, it indicates that the VIP address shall be different from the addresses allocated to all of the VduCp instances associated to it. If set to false, the VIP address shall be the same as one of the VduCp instances associated to it.

GenDoc Output: