4.2.1 changes fix some issues around supporting OsContainer based VNFs
Changes from v4.1.1
New Classes/Types:
- New datatype VipCpProfile
Attribute Name | Type | Mult. | Access | Stereotypes | Description |
vipCpdId | Identifier | 1 | RW | OpenModelAttribute · isInvariant: false · valueRange: no range constraint · support: MANDATORY | Uniquely references a VIP CPD. |
minNumberOfInstances | Integer | 1 | RW | OpenModelAttribute · isInvariant: false · valueRange: no range constraint · support: MANDATORY | Minimum number of instances of the VIP CP based on the referenced VIP CPD that is permitted to exist for this flavour. Shall be zero or greater. |
maxNumberOfInstances | Integer | 1 | RW | OpenModelAttribute · isInvariant: false · valueRange: no range constraint · support: MANDATORY | Maximum number of instances of the VIP CP based on the referenced VIP CPD that is permitted to exist for this flavour. Shall be greater than zero and not less than the value of "minNumberOfInstances". |
Other changes:
- 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
GenDoc Output: