Versions Compared

Key

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

This page shows the attributes that are proposed to be marked as "obsoletedobsolete" for ONAP R3 model.

The base model is copied from ONAP R2 resource design time model.

Note
titleLegend
  • attributes proposed to be "obsoletedobsolete" are marked in red and crossed out
  • please note that once the proposal is agreed, in the clean version, the attributes/datatypes will NOT be crossed out nor marked in red, but only be applied the "obsolete" stereotype
  • attributes/classes/datatypes that are different from ETSI IFA011 v2.4.1 specification are marked in orange

Proposed Changes:

Table of Contents
printablefalse

...

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.supportlifecycle: OBSOLETEDOBSOLETE
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.supportlifecycle: MANDATORYOBSOLETE
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.

supportlifecycle: OBSOLETEDOBSOLETE

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.supportlifecycle: MANDATORYOBSOLETE
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.

supportlifecycle: OBSOLETEDOBSOLETE

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.

supportlifecycle: OBSOLETEDOBSOLETE

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

flavorId

Identifier

1

Identifier of this DF within the VNFD.

support: MANDATORY
descriptionString1Human readable description of the DF.support: MANDATORY
vduProfileVduProfile1..NDescribes additional instantiation data for the VDUs used in this flavor.support: MANDATORY
virtualLinkProfileVirtualLinkProfile0..N

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.

support: MANDATORY
instantiationLevelInstantiationLevel1..N

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.

support: MANDATORY
affinityOrAntiAffinityGroupAffinityOrAntiAffinityGroup0..N

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

scalingAspectScalingAspect0..NThe scaling aspects supported by this DF of the VNF. scalingAspect shall be present if the VNF supports scaling.

support:

MANDATORY

placementGroupPlacementGroup0..NDetermine where VNFC's (VDU's) are placed with respect to the VNFsupport: EXPERIMENTAL
baseConfigGroupBaseConfigGroup0..1
  • 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.
support: EXPERIMENTAL
deploymentGroupDeploymentGroup1..NDeploymentGroup provides the minimum viable VDU and associated VNFC configuration for a useable VNF.support: EXPERIMENTAL

...

Attribute NameTypeMultiplicityDescriptionApplied Stereotypes

vduId

Identifier (Reference to Vdu)

1

Uniquely identifies a VDU.

support: MANDATORY
numberOf InstancesInteger1Number of instances of VNFC based on this VDU to deploy for an instantiation level or for a scaling delta.support: MANDATORY

...

Attribute NameTypeMultiplicityDescriptionApplied Stereotypes

latency

Number

1

Maximum latency in ms.

support: MANDATORY
packetDelayVariationNumber1Maximum jitter in ms.support: MANDATORY
packetLossRatioNumber0..1Maximum packet loss ratio. Cardinality is 0 if no packetLossRatio requirement exists.support: MANDATORY

...

Attribute NameTypeMultiplicityDescriptionApplied Stereotypes

type

Enum

1

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

support: MANDATORY

valueRange: "Affinity", "Anti-Affinity"

scopeEnum1Specifies the scope of the rule.

support: MANDATORY

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

...

Attribute NameTypeMultiplicityDescriptionApplied Stereotypes

groupId

Identifier

1

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

support: MANDATORY

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

support: MANDATORY

valueRange: "Affinity", "Anti-Affinity"

scopeEnum1Specifies the scope of the rule.

support: MANDATORY

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

...

Attribute NameTypeMultiplicityDescriptionApplied Stereotypes

addressType

Identifier

1

Describes the type of the address to be assigned to the CP instantiated from the parent CPD. The content type shall be aligned with the address type supported by the layerProtocol attribute of the parent CPD.

support: MANDATORY

l2AddressData

L2AddressData

0..1

Provides the information on the MAC addresses to be assigned to the CP(s) instantiated from the parent CPD.

Shall be present when the addressType is MAC address.

support: MANDATORY

l3AddressDataL3AddressData0..1

Provides the information on the IP addresses to be assigned to the CP instantiated from the parent CPD.

Shall be present when the addressType is IP address.

support: MANDATORY

...

Attribute NameTypeMultiplicityDescriptionApplied Stereotypes

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

floatingIpActivatedBoolean1Specify if the floating IP scheme is activated on the CP or not.

support: MANDATORY

iPAddressTypeEnum0..1

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"

numberOfIpAddressInteger0..1Minimum number of IP addresses to be assigned based on this L3AddressData information element.

support: MANDATORY

...

Attribute NameTypeMultiplicityDescriptionApplied Stereotypes

associatedLayerProtocol

Enum

1

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

support: MANDATORY

addressDataAddressData0..NProvides information on the addresses to be assigned to the CP(s) instantiated from the CPD.

support: MANDATORY

...

Attribute NameTypeMultiplicityDescriptionApplied Stereotypes

layerProtocol

Enum

1

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

support: MANDATORY

flowPatternString0..1Identifies the flow pattern of the connectivity (Line, Tree, Mesh).

support: MANDATORY

Class: VirtualCpuPinningData (

...

OBSOLETE)

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

supportlifecycle: OBSOLETEDOBSOLETE

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.

supportlifecycle: OBSOLETEDOBSOLETE

Class: RequestedAdditionalCapabilityData (

...

OBSOLETE)

Attribute NameTypeMultiplicityDescriptionApplied Stereotypes

requestedAdditionalCapabilityName

String

1

Identifies a requested additional capability for the VDU.

supportlifecycle: DEPRECATEDOBSOLETE

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

supportMandatory

Boolean

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

supportlifecycle: DEPRECATEDOBSOLETE

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

supportlifecycle: DEPRECATEDOBSOLETE

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

Class: VnfConfigurableProperties

Attribute NameTypeMultiplicityDescriptionApplied Stereotypes

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

isAutohealEnabledBoolean0..1

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

additionalConfigurablePropertyString0..NIt provides VNF specific configurable properties that can be modified using the ModifyVnfInfo operation.

support: MANDATORY

...

Attribute NameTypeMultiplicityDescriptionApplied Stereotypes

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

Class: LifecycleManagementScript

Attribute NameTypeMultiplicityDescriptionApplied Stereotypes

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.

lcmTransitionEventString0..N

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

scriptString1Information to locate a VNF LCM script (e.g. written in a DSL as specified in requirement VNF_PACK.LCM.001) triggered to react to one of the events listed in the event attribute.support: MANDATORY
scriptDslString1Defines the domain specific language (i.e. the type) of script that is provided. Types of scripts could include bash, python, etc.support: MANDATORY
scriptInputKeyValuePair0..N

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

...