Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. 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:

  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 vnfdvnfdExtInvariantId - 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.).



GenDoc Output:

View file
nameVnfModel-2021-07-29-144015.docx
height250

...