Obsolete Legacy Attributes

swImage

Identifies the operating system used in the software image. This attribute may also identify if a 32 bit or 64 bit software image is used.

VirtualMemoryData

VirtualCpuData

OBSOLETE

specification moved to vduCpuRequirements

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

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.

OBSOLETE

specification moved to vduMemRequirements

id

Identifier

1

Unique identifier of this VirtualStorageDesc in the VNFD.

typeOfStorage

String

1

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

sizeOfStorage

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

1

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

vduStorageRequirements

KeyValuePair

0..N

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

rdmaEnabled

Boolean

0..1

Indicate if the storage support RDMA.

swImageDesc

Identifier (Reference to SwImageDesc)

0..1

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

support: MANDATORY

logicalNodeRequirements

KeyValuePair

0..N

The logical node-level compute, memory and I/O requirements. An array of key-value pairs that articulate the deployment requirements.

This could include the number of CPU cores on this logical node, a memory configuration specific to a logical node (e.g. such as available in the Linux kernel via the libnuma library) or a requirement related to the association of an I/O device with the logical node.

cpdId

Identifier

1

Identifier of this Cpd information element.

cpRole

String

0..1

Identifies the role of the port in the context of the traffic flow patterns in the VNF or parent NS.

For example a VNF with a tree flow pattern within the VNF will have legal cpRoles of ROOT and LEAF.

description

String

0..1

Provides human-readable information on the purpose of the CP (e.g. CP for control plane traffic).

cpProtocol

CpProtocolData

1..N

Identifies the protocol layering information the CP uses for connectivity purposes and associated information. There shall be one cpProtocol for each layer protocol as indicated by the attribute layerProtocol.

Editor's note: the attribute "layerProtocol" still needs further discussion and not included in this table.

trunkMode

Boolean

1

Information about whether the CP instantiated from this CPD is in Trunk mode (802.1Q or other).

allowedAddressData

AddressData

0..N

For specifying floating IP(s) to be shared among Cpds, which are reserved for vnfReservedCpd described in the VNFD.

support: MANDATORY

bitrateRequirement

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

0..1

Bitrate requirement on this CP.

vnicName

String

0..1

Describes the name of the vNIC this CP attaches to, e.g. eth0. It will be configured during the Vdu booting process.

vnicOrder

Integer

0..1

Describes the order to create the vNIC within the scope of this Vdu.

vnicType

Enum

0..1

Describes the type of the vNIC this CP attaches to.

support: MANDATORY

valueRange: normal, macvtap, direct, baremetal, direct-physical and virtio-forwarder

vduId

Identifier (Reference to Vdu)

1

Uniquely identifies a VDU.

minNumberOfInstances

Integer

1

Minimum number of instances of the VNFC based on this VDU that is permitted to exist for this flavour.

maxNumberOfInstances

Integer

1

Maximum number of instances of the VNFC based on this VDU that is permitted to exist for this flavour.

localAffinityOrAntiAffinityRule

LocalAffinityOrAntiAffinityRule

0..N

Specifies affinity or anti-affinity rules applicable between the virtualisation containers (e.g. virtual machines) to be created based on this VDU.

When the cardinality is greater than 1, both affinity rule(s) and anti-affinity rule(s) with different scopes (e.g. "Affinity with the scope resource zone and anti-affinity with the scope NFVI node") are applicable to the virtualisation containers (e.g. virtual machines) to be created based on this VDU.

support: MANDATORY

Identifier(s) of the affinity or anti-affinity group(s) the VDU belongs to.

NOTE: Each identifier references an affinity or anti-affinity group which expresses affinity or anti-affinity relationships between the virtualisation container(s) (e.g. virtual machine(s)) to be created using this VDU and the virtualisation container(s) (e.g. virtual machine(s)) to be created using other VDU(s) in the same group.

name

String

0..1

Provides a human readable name for the requirement.

description

String

0..1

Provides a human readable description of the requirement.

This references (couples) the CPD with any logical node I/O requirements (for network devices) that may have been created. Linking these attributes is necessary so that so that I/O requirements that need to be articulated at the logical node level can be associated with the network interface requirements associated with the CPD.

virtualLinkDescId

Identifier

1

Unique identifier of this internal VLD in VNFD.

flavorId

Identifier

1

Identifier of this DF within the VNFD.

Defines the internal VLD along with additional data which is used in this DF.

NOTE 1: This allows for different VNF internal topologies between DFs.

NOTE 2: virtualLinkProfile needs to be provided for all VLs that the CPs of the VDUs in the VDU profiles connect to.

Describes the various levels of resources that can be used to instantiate the VNF using this flavour.

Examples: Small, Medium, Large.

If there is only one "instantiationLevel" entry, it shall be treated as the default instantiation level for this DF.

Specifies affinity or anti-affinity relationship applicable between the virtualisation containers (e.g. virtual machines) to be created using different VDUs or internal VLs to be created using different VnfVirtualLinkDesc(s) in the same affinity or anti-affinity group.

NOTE: In the present specification, including either VDU(s) or VnfVirtualLinkDesc(s) into the same affinity or anti-affinity group is supported. Extension to support including both VDU(s) and VnfVirtualLinkDesc(s) into the same affinity or anti-affinity group is left for future specification.

support:

MANDATORY

support:

MANDATORY

• BaseConfigGroup may set Access Control Lists (ACL's) and establish security groups and server groups.
• BaseConfigGroup creates/establishs storage for the VM's (OpenStack Cinder).
• BaseConfigGroup may establish internal networks such as OAM (VNF Mgmt) or MNS (Maintenance & Surveillance)  established.

vnfVirtualLinkDescId

Identifier (Reference to VnfVirtualLinkDesc)

1

Uniquely identifies a Vnf VLD.

Specifies affinity or anti-affinity rules applicable between the VLs based on this VnfVirtualLinkDesc.

When the cardinality is greater than 1, both affinity rule(s) and anti-affinity rule(s) with different scopes are applicable to the VLs based on this VnfVirtualLinkDesc.

Identifier(s) of the affinity or anti-affinity group(s) the VnfVirtualLinkDesc belongs to.

NOTE: Each identifier references an affinity or anti-affinity group which expresses affinity or anti-affinity relationship between the VL(s) using this VnfVirtualLinkDesc and the VL(s) using other VnfVirtualLinkDesc(s) in the same group.

Specifies the maximum bitrate requirements for a VL instantiated according to this profile.

NOTE: These attributes are used to control scaling boundaries.

Specifies the minimum bitrate requirements for a VL instantiated according to this profile.

support: MANDATORY

valueRange: specified values include: cidr, allocationPools (represented by [starting ip address, ending ip address]), gatewayIp, networkName, segmentationId, physicalNetwork.

support: MANDATORY

valueRange: "VLAN", "VXLAN"

flavourId

Identifier

1

Identifies a flavour within a VnfVirtualLinkDesc.

root

Number

1

Throughput requirement of the link (e.g. bitrate of E-Line, root bitrate of E-Tree, aggregate capacity of E-LAN).

Throughput requirement of leaf connections to the link when applicable to the connectivity type (e.g. for E-Tree and E?LAN branches).

NOTE: The present document does not specify the means to declare different bitrate requirements for leaf connections (e.g. E-LAN leaves).

levelId

Identifier

1

Uniquely identifies a level with the DF.

Specifies bitrate requirements applicable to virtual links created from particular virtual link descriptors for this level.

NOTE: If not present, it is assumed that the bitrate requirements can be derived from those specified in the VduCpd instances applicable to the internal VL. If present in both the InstantiationLevel and the VduCpd instances applicable to the internal VL, the highest value takes precedence.

aspectId

Identifier (Reference to ScalingAspect)

1

Reference to the scaling aspect.

vduId

Identifier (Reference to Vdu)

1

Uniquely identifies a VDU.

latency

Number

1

Maximum latency in ms.

type

Enum

1

Specifies whether the rule is an affinity rule or an anti-affinity rule.

support: MANDATORY

valueRange: "Affinity", "Anti-Affinity"

support: MANDATORY

valueRange: "NFVI-PoP", "Zone", "ZoneGroup", "NFVI-node"

groupId

Identifier

1

Identifies an affinity or anti-affinity group to which the affinity or anti-affinity rule applies.

support: MANDATORY

support: MANDATORY

valueRange: "Affinity", "Anti-Affinity"

support: MANDATORY

valueRange: "NFVI-PoP", "Zone", "ZoneGroup", "NFVI-node"

macAddressAssignment

Boolean

1

Specify if the MAC address assignment is the responsibility of management and orchestration function or not.

If it is set to True, it is the management and orchestration function responsibility.

If it is set to False, it will be provided by an external entity, e.g. OSS/BSS. 

support: MANDATORY

iPAddressAssignment

Boolean

1

Specify if the address assignment is the responsibility of management and orchestration function or not.

If it is set to True, it is the management and orchestration function responsibility.

support: MANDATORY

support: MANDATORY

Define address type.

NOTE: The address type should be aligned with the address type supported by the layerProtocol attribute of the parent Cpd.

support: MANDATORY

valueRange: "IPv4", "IPv6"

support: MANDATORY

associatedLayerProtocol

Enum

1

One of the values of the attribute layerProtocol of the Cpd IE.

support: MANDATORY

support: MANDATORY

layerProtocol

Enum

1

Identifies the protocol this VL gives access to (Ethernet, MPLS, ODU2, IPV4, IPV6, Pseudo-Wire).

support: MANDATORY

support: MANDATORY

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

OBSOLETE

valueRange: "static", "dynamic"

Not specified

Editor's note: need to be specified

OBSOLETE

requestedAdditionalCapabilityName

String

1

Identifies a requested additional capability for the VDU.

OBSOLETE

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

Boolean

OBSOLETE

OBSOLETE

isAutoscaleEnabled

Boolean

0..1

It permits to enable (TRUE)/disable (FALSE) the auto-scaling functionality.

NOTE: A cardinality of "0" indicates that configuring this present VNF property is not supported.

support: MANDATORY

It permits to enable (TRUE)/disable (FALSE) the auto-healing functionality.

NOTE: A cardinality of "0" indicates that configuring this present VNF property is not supported.

support: MANDATORY

support: MANDATORY

additionalVnfcConfigurableProperty

String

0..N

It provides VNFC configurable properties that can be modified using the ModifyVnfInfo operation.

NOTE: A cardinality of "0" indicates that configuring this present VNF property is not supported.

support: MANDATORY

event

Enum

0..N

Describes VNF lifecycle event(s) or an external stimulus detected on a VNFM reference point.

NOTE: At least one of these two attributes shall be included.

support: MANDATORY

valueRange: for lifecycle events, include: "EVENT_START_INSTANTIATION", "EVENT_END_INSTANTIATION", "EVENT_START_SCALING", "EVENT_END_SCALING", "EVENT_START_SCALING_TO_LEVEL", "EVENT_END_SCALING_TO_LEVEL", "EVENT_START_HEALING", "EVENT_END_HEALING", "EVENT_START_TERMINATION", "EVENT_END_TERMINATION", "EVENT_START_VNF_FLAVOR_CHANGE", "EVENT_END_VNF_FLAVOR_CHANGE", "EVENT_START_VNF_OPERATION_CHANGE", "EVENT_END_VNF_OPERATION_CHANGE", "EVENT_START_VNF_EXT_CONN_CHANGE", "EVENT_END_VNF_EXT_CONN_CHANGE", "EVENT_START_VNFINFO_MODIFICATION", "EVENT_END_VNFINFO_MODIFICATION"; for external stimulus, include: receipt of request message of instantiation, scaling, healing, termination, change of VNF flavour, change of the operation state of the VNF, change of external VNF connectivity, modification of VNF information or the receipt of a notification regarding the change of a VNF indicator value.

Describes the transition VNF lifecycle event(s) that cannot be mapped to any of the enumerated values defined for the event attribute.

NOTE: At least one of these two attributes shall be included.

support: MANDATORY

Array of KVP requirements with the key as the parameter name and the value as the parameter that need to be passed as an input to the script.

NOTE: The scriptInput values are passed to the scripts in addition to the parameters received in the operation invocation request or indicator value change.

support: MANDATORY

valueRange: "VNF", "EM", "Both"

Not specified

Editor's note: need to be specified

An attribute that describes the recommended periodicity at which to collect the performance information.

VNFM determines if this parameter is considered.

The vendor may provide this information as a guidance for creating PmJobs if needed.

NOTE: The MANO or NFVI may not support the recommended collectionPeriod based on their functionalities, and can reject the requests based on the recommended collectionPeriod in this case.

Identifier (Reference to VnfVirtualLinkDesc) 

support: MANDATORY

valueRange: "co-location", "isolation", "exclusively"

NOTE:

• Co-location - members of the group share the same physical host or rack.
• isolation - members of the group do not share the same physical host or rack.
• Exclusivity - members have sole use of a given physical host or rack (not shared with any vnfcs outside the group).

Not specified

(should it be Identifier (Reference to Vdu)?)

support: MANDATORY

valueRange: "host", "rack"

Not specified

Editor's note: need to be specified

Not specified

Editor's note: need to be specified