Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: change the format of marking the lifecycle stereotype

...

Attribute NameTypeMultiplicityDescriptionApplied Stereotypes
virtualComputeDescIdIdentifier1Unique identifier of this VirtualComputeDesc in the VNFD.support: MANDATORY
logicalNodeLogicalNodeData1..NThe logical Node requirements.support: MANDATORY
requestAdditionalCapabilitiesRequestedAdditionalCapabilityData0..NSpecifies requirements for additional capabilities. These may be for a range of purposes. One example is acceleration related capabilities.lifecycle: OBSOLETE
computeRequirementsKeyValuePair0..NSpecifies compute requirements.support: MANDATORY
virtualMemory

VirtualMemoryData

1The virtual memory of the virtualised compute.support: MANDATORY
virtualCpu

VirtualCpuData

1The virtual CPU(s) of the virtualised compute.support: MANDATORY

...

Attribute NameTypeMultiplicityDescriptionApplied Stereotypes
cpuArchitectureString0..1CPU architecture type. Examples are x86, ARM. The cardinality can be 0 during the allocation request, if no particular CPU architecture type is requested.support: MANDATORY
numVirtualCpuInteger1Number of virtual CPUs.support: MANDATORY
virtualCpuClockNumber(recommended DM type: Scalar-Unit-Freq)0..1Minimum virtual CPU clock rate (e.g. in MHz). The cardinality can be 0 during the allocation request, if no particular value is requested.support: MANDATORY
virtualCpuOversubscriptionPolicyString0..1The CPU core oversubscription policy e.g. the relation of virtual CPU cores to physical CPU cores/threads. The cardinality can be 0 during the allocation request, if no particular value is requested.lifecycle: OBSOLETE
vduCpuRequirementsKeyValuePair0..NArray of key-value pair requirements on the Compute (CPU) for the VDU.support: MANDATORY
virtualCpuPinningVirtualCpuPinningData0..1The virtual CPU pinning configuration for the virtualised compute resource.

lifecycle: OBSOLETE

specification moved to vduCpuRequirements

editor's note: need to check whether can be optional

...

Attribute NameTypeMultiplicityDescriptionApplied Stereotypes
virtualMemSizeNumber (recommended DM type: Scalar-Unit-Size)1Amount of virtual Memory (e.g. in MB).support: MANDATORY
virtualMemOversubscriptionPolicyString0..1The memory core oversubscription policy in terms of virtual memory to physical memory on the platform. The cardinality can be 0 during the allocation request, if no particular value is requested.lifecycle: OBSOLETE
vduMemRequirementsKeyValuePair0..NArray of key-value pair requirements on the memory for the VDU.support: MANDATORY
numaEnabledBoolean
0..1

It specifies the memory allocation to be cognisant of the relevant process/core allocation. The cardinality can be 0 during the allocation request, if no particular value is requested.

lifecycle: OBSOLETE

specification moved to vduMemRequirements

...

Attribute NameTypeMultiplicityDescriptionApplied Stereotypes

id

Identifier

1

Unique identifier of this VirtualStorageDesc in the VNFD.

support: MANDATORY

typeOfStorage

String

1

Type of virtualised storage resource
(e.g. volume, object).

support: MANDATORY

sizeOfStorage

Number (recommended DM type: Scalar-Unit-Size)

1

Size of virtualised storage resource
(e.g. size of volume, in GB).

support: MANDATORY

vduStorageRequirements

KeyValuePair

0..N

An array of key-value pairs that articulate the storage deployment requirements.

support: MANDATORY

rdmaEnabled

Boolean

0..1

Indicate if the storage support RDMA.

lifecycle: OBSOLETE

swImageDesc

Identifier (Reference to SwImageDesc)

0..1

Software image to be loaded on the VirtualStorage resource created based on this VirtualStorageDesc.

support: MANDATORY

...

Attribute NameTypeMultiplicityDescriptionApplied Stereotypes

virtualCpuPinningPolicy

Enum

0..1

The policy can take values of "static" or "dynamic". In case of "static" the virtual CPU cores are requested to be allocated to logical CPU cores according to the rules defined in virtualCpuPinningRules. In case of "dynamic" the allocation of virtual CPU cores to logical CPU cores is decided by the VIM. (e.g.: SMT (Simultaneous Multi-Threading) requirements).

lifecycle: OBSOLETE

valueRange: "static", "dynamic"

virtualCpuPinningRule

Not specified

Editor's note: need to be specified

0..1A list of rules that should be considered during the allocation of the virtual CPUs to logical CPUs in case of "static" virtualCpuPinningPolicy.

lifecycle: OBSOLETE

Class: RequestedAdditionalCapabilityData (OBSOLETE)

Attribute NameTypeMultiplicityDescriptionApplied Stereotypes

requestedAdditionalCapabilityName

String

1

Identifies a requested additional capability for the VDU.

lifecycle: OBSOLETE

valueRange: For acceleration capabilities, reference to ETSI GS NFV-IFA 002.

supportMandatory

Boolean

1Indicates whether the requested additional capability is mandatory for successful operation.

lifecycle: OBSOLETE

minRequestedAdditionalCapabilityVersionString0..1Identifies the minimum version of the requested additional capability.

lifecycle: OBSOLETE

preferredRequestedAdditionalCapabilityVersionString0..1Identifies the preferred version of the requested additional capability.lifecycle: OBSOLETE
targetPerformanceParametersKeyValuePair1..NIdentifies specific attributes, dependent on the requested additional capability type.lifecycle: OBSOLETE

Class: VnfConfigurableProperties

...