From c57f262f875161a3ac299b4b7c6abde096df4735 Mon Sep 17 00:00:00 2001 From: jjewitt58 Date: Thu, 12 Jul 2018 09:18:34 -0700 Subject: Create new ONAP Papyrus model Issue-ID: MODELING-103 Change-Id: I2c2543321b16dab8b14d41d136eac329cea8dddd Signed-off-by: jjewitt58 --- papyrus/ONAP Information Model/Vnf.uml | 3293 ++++++++++++++++++++++++++++++++ 1 file changed, 3293 insertions(+) create mode 100644 papyrus/ONAP Information Model/Vnf.uml (limited to 'papyrus/ONAP Information Model/Vnf.uml') diff --git a/papyrus/ONAP Information Model/Vnf.uml b/papyrus/ONAP Information Model/Vnf.uml new file mode 100644 index 0000000..e32370b --- /dev/null +++ b/papyrus/ONAP Information Model/Vnf.uml @@ -0,0 +1,3293 @@ + + + + + + +
+ + + Defines descriptors of virtual compute resources to be used by the VNF. + + + + + +
+ + + References to Vdus that are part of this group. + + + + + +
+ + + Represents the type of network connectivity mandated by the VNF provider between two or more CPs which includes at least one internal CP. + + + References to VnfVirtualLinkDesc that are part of this group. + + + + + + + + + + + + +
+ + + + + +
+ + + Describes external interface(s) exposed by this VNF enabling connection with a VL. + + + + + + + + +
+ + + + + +
+ + + + + + + + +
+ + + + + + + + +
+ + + + + +
+ + + + + +
+ + + Describes CPU, Memory and acceleration requirements of the Virtualisation Container realising this Vdu. + + + + + + + + +
+ + + Describes storage requirements for a VirtualStorage instance attached to the virtualisation container created from virtualComputeDesc defined for this Vdu. support: + + + + + + + + +
+ + + Describes the software image which is directly loaded on the virtualisation container realising this Vdu. + +NOTE: More software images can be attached to the virtualisation container using VirtualStorage resources. + + + + + + + + + +
+ + + + + + + + + + + + +
+ + + Describes a specific flavour of the VL with specific bitrate requirements. + + + + + + + + + +
+ + + + + + + + +
+ + + Identifies a flavour within a VnfVirtualLinkDesc. + + + + + + +
+ + + + + + + + +
+ + + + + +
+ + + + + +
+ + + + + + + + +
+ + + + + + + + +
+ + + + + +
+ + + + + + + + +
+ + + 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 associated elements of a VNFD for a certain purpose during VNF lifecycle management. + + + Missing in clean, but in Sparx and ifa011 + + + A few quick observations +1. Using integer for number. Jessie: Created a primitive called Number which is a superset of integer and real. +2. created a datatype called enum. Deleted enum. Created "enums" where needed. +3. Seems like we are just using ETSI (beyound what we have in the works). Jessie: It appears that way. +4. Is monitoring param a class or a data type? Jessie: It is a datatype. Due to it's relationship to event, maybe a class?? +5. Class versus datatype?? + + + Not Defined in Clean + + + + + ResourceDesc??? + + + Red items are proposed to be deleted. + + + gold indicates an add or a change + + + + + + + The Virtualisation Deployment Unit (VDU) is a construct supporting the description of the deployment and operational behavior of a VNFC. + +A VNFC instance created based on the VDU maps to a single virtualisation container (e.g. a VM). + +A VNFC will only be in one VNFDesc. If a vendor wants to use the VNFC in mupliple VNFDesc (their product) they can do so, but it will be 'repeated'. + +References: +tosca-nfv-YAML-v1.0-wd05-rev02 +ETSI GS NFV-IFA 011 V2.1.3 + + + + + + Unique identifier of this Vdu in VNFD. + + + + + + + Human readable name of the Vdu. + + + + + + Human readable description of the Vdu. + + + + + + Boot order of valid boot devices. + +NOTE: If no boot order is defined the default boot order defined in the VIM or NFVI shall be used. + + + + + + + + + Describes constraints on the NFVI for the VNFC instance(s) created from this Vdu. For example, aspects of a secure hosting environment for the VNFC instance that involve additional entities or processes. + +NOTE: These are constraints other than stipulating that a VNFC instance has access to a certain resource, as a prerequisite to instantiation. The attributes virtualComputeDesc and virtualStorageDesc define the resources required for instantiation of the VNFC instance. + + + + + + + + + Defines the virtualised resources monitoring parameters on VDU level. + + + + + + + Describes the information (e.g. URL) about the scripts, config drive metadata, etc. which can be used during Vdu booting process. + + + + + + + + Describes the configurable properties of all VNFC instances based on this VDU. + + + + + Describes network connectivity between a VNFC instance (based on this Vdu) and an Virtual Link (VL). + + + + + Describes CPU, Memory and acceleration requirements of the Virtualisation Container realising this Vdu. + + + + + + + Describes storage requirements for a VirtualStorage instance attached to the virtualisation container created from virtualComputeDesc defined for this Vdu. + + + + + + + Describes the software image which is directly loaded on the virtualisation container realising this Vdu. + +NOTE: More software images can be attached to the virtualisation container using VirtualStorage resources. + + + + + + + + + A Vnfd, or VNF Descriptor, is template which describes a VNF in terms of deployment and operational behaviour requirements. It also contains connectivity, interface and virtualised resource requirements. + +References: +tosca-nfv-YAML-v1.0-wd05-rev02 (tosca.nodes.nfv.vnfd, but node details are not defined) +ETSI GS NFV-IFA 011 V2.1.3 (VNFD) + + + + Provider of the VNF and of the VNFD. + + + + + + Name to identify the VNF Product. Invariant for the VNF Product lifetime. + + + + + + Software version of the VNF. This is changed when there is any change to the software that is included in the VNF Package. + + + + + + Identifies the version of the VNFD. + + + + + + Human readable name for the VNF Product. Can change during the VNF Product lifetime. + + + + + + + + Human readable description of the VNF Product. Can change during the VNF Product lifetime. + + + + + + + + Identifies VNFM(s) compatible with the VNF described in this version of the VNFD. + + + + + + + + Information about localization languages of the VNF (includes e.g. strings in the VNFD). + +NOTE: This allows to provide one or more localization languages to support selecting a specific localization language at VNF instantiation time. + + + + + + + + + Defines the VNF-specific extension and metadata attributes of the VnfInfo that are writeable via the ModifyVnfInfo operation. + + + + + + + + Identifier of this VNFD information element. This attribute shall be globally unique. + +NOTE: The VNFD Identifier shall be used as the unique identifier of the VNF Package that contains this VNFD. +Any modification of the content of the VNFD or the VNF Package shall result in a new VNFD Identifier. + + + + + + Information about localization languages of the VNF (includes e.g. strings in the VNFD). + +NOTE: This allows to provide one or more localization languages to support selecting a specific localization language at VNF instantiation time. + + + + + + + + + Describes the configurable properties of the VNF (e.g. related to auto scaling and auto healing). + + + + + + + Includes a list of events and corresponding management scripts performed for the VNF. + + + + + + + File path of the vendor specified logo. + + + + + + + + UUID of the vendor guide/documentation which is attached to VNF and can be downloaded from the model. + + + + + + + + Virtualisation Deployment Unit. + + + + + + + Describes external interface(s) exposed by this VNF enabling connection with a VL. + + + + + + + Describes specific DF(s) of a VNF with specific requirements for capacity and performance. + + + + + + + Declares the VNF indicators that are supported by this VNF. + + + + + + + Describes the associated elements of a VNFD for a certain purpose during VNF lifecycle management. + + + + + + + Defines descriptors of virtual compute resources to be used by the VNF. + + + + + + + Defines descriptors of virtual storage resources to be used by the VNF. + + + + + + + Represents the type of network connectivity mandated by the VNF provider between two or more CPs which includes at least one internal CP. + + + + + + + Reserved IP Address for VNF which is not bounded to any specific VNFC, but assigned manually from outside and potentially shared as a floating IP among VNFCs. + + + + + + + + The SwImageDesc information element describes requested additional capability for a particular VDU. Such a capability may be for acceleration or specific tasks. Storage not necessarily related to the compute, may be Network Attached Storage (NAS) + +References: +tosca-nfv-YAML-v1.0-wd05-rev02 +ETSI GS NFV-IFA 011 V2.1.3 + + + + + The identifier of this software image. + + + + + + The name of this software image. + + + + + + The version of this software image. + + + + + + The checksum of the software image file. + + + + + + The container format describes the container file format in which software image is provided. + + + + + + The disk format of a software image is the format of the underlying disk image. + + + + + + The minimal RAM requirement for this software image. The value of the "size" attribute of VirtualMemoryData of the Vdu referencing this SwImageDesc shall not be smaller than the value of minRam. + + + + + + + + The minimal disk size requirement for this software image. The value of the "size of storage" attribute of the VirtualStorageDesc referencing this SwImageDesc shall not be smaller than the value of minDisk. + + + + + + The size of the software image. + + + + + + +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. + support: + + + + + + + + Identifies the virtualisation environments (e.g. hypervisor) compatible with this software image. + + + + + + + + The minimal disk size requirement for this software image. The value of the "size of storage" attribute of the VirtualStorageDesc referencing this SwImageDesc shall not be smaller than the value of minDisk. + + + + + + + The VduProfile describes additional instantiation data for a given VDU used in a DF. + + + + Uniquely identifies a VDU. + + + + + + + Minimum number of instances of the VNFC based on this VDU that is permitted to exist for this flavour. + + + + + + + Maximum number of instances of the VNFC based on this VDU that is permitted to exist for this flavour. + + + + + + + Specifies affinity or anti-affinity rules applicable between the virtualisation containers (e.g. virtual machines) to be created based on this VDU. + + + + + + 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. + + + + + + + + + Watchdog action to be triggered by the VIM for the VNF in case the heart beat fails, e.g. reset or hard shutdown, etc. + + + + + + + + Timeout value for the VNFM to wait before the successful booting up of the VDU. + + + + + + + + + The VirtualComputeDesc information element supports the specification of requirements related to virtual compute resources. + + + + Unique identifier of this VirtualComputeDesc in the VNFD + + + + + + The logical Node requirements. + + + + + + + Specifies requirements for additional capabilities. These may be for a range of purposes. One example is acceleration related capabilities. + + + + + + + Specifies compute requirements. + + + + + + + + The virtual memory of the virtualised compute. + + + + + The virtual CPU(s) of the virtualised compute. + + + + + + + Unique identifier of this VirtualStorageDesc in the VNFD. + + + + + + + Type of virtualised storage resource +(e.g. volume, object). + + + + + + + Size of virtualised storage resource +(e.g. size of volume, in GB). + + + + + + + An array of key-value pairs that articulate the storage deployment requirements. + + + + + + + + + Indicate if the storage support RDMA. + + + + + + + + + Software image to be loaded on the VirtualStorage resource created based on this VirtualStorageDesc. + + + + + + + + + + + Unique identifier of this internal VLD in VNFD. + + + + + + + + Specifies test access facilities expected on the VL (e.g. none, passive monitoring, or active (intrusive) loopbacks at endpoints). + + + + + + + + Provides human-readable information on the purpose of the VL (e.g. control plane traffic). + + + + + + + + Defines the virtualised resources monitoring parameters on VLD level. + + + + + + + Describes a specific flavour of the VL with specific bitrate requirements. + + + + + + + + A VduCpd information element is a type of Cpd and describes network connectivity between a VNFC instance (based on this VDU) and an internal VL. + + + + + Bitrate requirement on this CP. + + + + + + + + + Describes the name of the vNIC this CP attaches to, e.g. eth0. It will be configured during the Vdu booting process. + + + + + + + + + Describes the order to create the vNIC within the scope of this Vdu. + + + + + + + + + Describes the type of the vNIC this CP attaches to. + + + + + + + + Specifies requirements on a virtual network interface realising the CPs instantiated from this CPD. + + + + + + + + The VnfDf describes a specific deployment version of a VNF. + + + + Identifier of this DF within the VNFD. + + + + + + + Human readable description of the DF. + + + + + + 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. + + + + + + + + The scaling aspects supported by this DF of the VNF. scalingAspect shall be present if the VNF supports scaling. + + + + + + + Describes additional instantiation data for the VDUs used in this flavor. + + + + + + + Determine where VNFC's (VDU's) are placed with respect to the VNF + + + + + + + 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. + + + + + + DeploymentGroup provides the minimum viable VDU and associated VNFC configuration for a useable VNF. + + + + + + + Identifies the vaious scaling groups within the VNF which identify which vnfcs that need to be scaled together. + + + + + + + + + Reference to the internal VDU CPD which is used to instantiate internal CPs. These internal CPs are, in turn, exposed as external CPs defined by this external CPD. + + + + + + + + Specifies requirements on a virtual network interface realising the CPs instantiated from this CPD. + +NOTE: In case of referencing an intCpd via its identifier, the virtualNetworkInterfaceRequirements attribute of the referenced intCpd applies. + + + + + + + + Reference to the internal Virtual Link +Descriptor (VLD) to which CPs instantiated +from this external CP Descriptor (CPD) +connect. Either intVirtualLinkDesc or +intCpd shall be present. + + + + + + + + + + + + A VNFD Element Group is a mechanism for associating elements of a VNFD (Vdus and VnfVirtualLinkDesc(s)) for a +certain purpose, for example, scaling aspects. + +A given element can belong to multiple groups. + + + + Unique identifier of this group in the VNFD. + + + + + + Human readable description of the group. + + + + + + + + + + + + + + + The VnfIndicator information element defines the indicator the VNF supports. + + + + Unique identifier. + + + + + + The human readable name of the VnfIndicator. + + + + + + + + Defines the allowed values or value ranges of this indicator. + + + + + + + + Describe the source of the indicator. This tells the consumer where to send the subscription request. + + + + + + A Cpd information element describes network connectivity to a compute resource or a VL. This is an abstract class used +as parent for the various Cpd classes. + + + + Identifier of this Cpd information element. + + + + + + + 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. + + + + + + + + + Provides human-readable information on the purpose of the CP (e.g. CP for control plane traffic). + + + + + + + + + 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. + + + + + + + + Information about whether the CP instantiated from this CPD is in Trunk mode (802.1Q or other). + + + + + + + For specifying floating IP(s) to be shared among Cpds, which are reserved for vnfReservedCpd described in the VNFD. + + + + + + + + + The VirtualLinkDescFlavour describes additional instantiation data for a given internal VL used in a DF. + + + + QoS of the VL. + + + + + + + Identifies a flavour within a VnfVirtualLinkDesc. + + + + + + + + + The VirtualLinkProfile describes additional instantiation data for a given VL used in a DF. + + + + 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 minimum bitrate requirements for a VL instantiated according to this profile. + + + + + + Specifies the minimum bitrate requirements for a VL instantiated according to this profile. + + + + + + Specifies initiation parameters for the virtual link. + + + + + + + + Type of the network + + + + + + + Indicating whether DHCP is enabled. Default is "FALSE" if not specified otherwise. + + + + + + + + Indicating whether "VLAN Transparent Mode" is supported. Default is "FALSE" if not specified otherwise. + + + + + + + + Identifies a flavour within the VnfVirtualLinkDesc. + + + + + Uniquely identifies a Vnf VLD. + + + + + + This class specifies requirements on a virtual network interface. + + + + Provides a human readable name for the requirement. + + + + + + + + + Provides a human readable description of the requirement. + + + + + + + + + Indicates whether fulfilling the constraint is mandatory (TRUE) for successful operation or desirable (FALSE). + + + + + + The network interface requirements. An element from an array of key-value pairs that articulate the network interface deployment requirements + + + + + + + + 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. + + + + + + + + + The InstantiationLevel class describes a given level of resources to be instantiated within a DF in term of the number of VNFC instances to be created from each VDU. +All the VDUs referenced in the level shall be part of the corresponding DF and their number shall be within the range (min/max) for this DF. + + + + + + + Uniquely identifies a level with the DF. + + + + + + Human readable description of the level. + + + + + + Represents for each aspect the scale level that corresponds to this instantiation level. scaleInfo shall be present if the VNF supports scaling. + + + + + + + Indicates the number of instance of this VDU to deploy for this level. + + + + + + + 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. + + + + + + + + + The AffinityOrAntiAffinityGroup class describes the affinity or anti-affinity relationship. + + + + Identifies an affinity or anti-affinity group to which the affinity or anti-affinity rule applies. + + + + + + + Specifies whether the rule is an affinity rule or an anti-affinity rule. + + + + + Specifies the scope of the rule. + + + + + + The ScalingAspect class describes the details of an aspect used for horizontal scaling. + + + + + The VduLevel information element indicates for a given VDU in a given level the number of instances to deploy. + + + + Uniquely identifies a VDU. + + + + + + Number of instances of VNFC based on this VDU to deploy for an instantiation level or for a scaling delta. + + + + + + + Every VNF contains a BaseConfigGroup. + +BaseConfigGroup may set Access Control Lists (ACL's) and establish security groups and server groups. +BaseConfigGroup reates/establishs storage for the VM's (OpenStack Cinder). +BaseConfigGroup may establish internal networks such as OAM (VNF Mgmt) or MNS (Maintenance & Surveillance) established. + +A very simple VNF may only have a BaseConfig VNFElementGroup. + + + + + + + DeploymentGroup provides the minimum viable VDU and associated VNFC configuration for a useable VNF. I can have a small, medium, large deployment configuration. + + + + + + + Homing selects what cloud selection strategy will be used. + +HomingGroup is used to determine where VNF's within a given group are placed with respect to a service component. + +Homing strategy is as follows: +Colocation - members of the group share the same cloud region (VIM Domain) +isolation - members of the group do not share the same cloud region. + + + + + + + + The homing strategy can be one of the following: + +Exclusivity - Resources within the cloud region are exclusive to the group +Inclusively - Resources are co-located in the same cloud-region. +Diversity - Resources are geo-diverse ( cannot be co-located). + + + + + + + + + + + + + + A ScalingGroup determines which VNFC's (VDU's) are scaled together based on demand. + + + + + + + + + + Describes an external CP exposed by a VNF. + + + + + + + + + An implementation of an NF that can be deployed on a Network Function Virtualisation Infrastructure (NFVI). + + + + + + + External CP of the VNF. + + + + + + + + An implementation of an NF that can be deployed on a Network Function Virtualisation Infrastructure (NFVI). + + + + identifier of the VNF instance + + + + + + name of the VNF instance + + + + + + alternative name of the VNF instance + + + + + + + + name to identify the VNF Product, invariant for the VNF Product lifetime + + + + + + + + description of the VNF instance + + + + + + + provider of the VNF model + + + + + identifier of the VNF model + + + + + + version of the VNF model + + + + + + Software version of the VNF. This is changed when there is any change to the software that is included in the VNF package + + + + + + identifier of the specific VNF package on which the VNF instance is based + + + + + availability zone information of the VNF instance + + + + + provisioning status, used as a trigger for operational monitoring of this resource by service assurance systems + valid value example: PROVISIONED, PREPROVISIONED, CAPPED + + + + + + + indicator for whether the resource is considered operational. Valid values are in-service-path and out-of-service-path. + + + + + + + whether the VNF instance is instantiated + + + + + oam ip address, ipv4 + + + + + + + oam ip address, ipv6 + + + + + + + information specific to an instantiated VNF instance, e.g., vm information + + + + + + + whether the VNF instance is in maintenance mode, if yes, DCAE will not observe alarms/traps, etc. + + + + + + + + whether closed loop function is enabled + + + + + + + + whether this VNF is accessed using SSH + + + + + + + + indicator for whether autoHeal and autoScale is enabled + + + + + + + String assigned to this model used for naming purpose. + + + + + + Identifier of the policy which has the naming logic for this VNF instance + + + + + + Identifier of the policy which provides homing conditions. + + + + + + Generic description of the type of network function + + + + + + English description of network function that the specific VNF deployment is providing. + + + + + + Role in the network this model will be providing + + + + + + Whether closed loop capabilities are enabled for this or not. + + + + + Relatonship to the NF components that are part of this VNF. + + + + + + + Relatinship to the VNF descriptor + + + + + + + + + + + + + + + + + + An internal component of a VNF providing a VNF Provider a defined sub-set of that VNF's functionality, with the main characteristic that a single instance of this component maps 1:1 against a single Virtualisation Container. + + + + identifier of the NFC instance + + + + + + short code of the NFC instance + + + + + + + description of the NFC instance + + + + + + + identifier of the model of the NFC instance + + + + + + layer-3 interface addresses, ipv4 + + + + + + + layer-3 interface addresses, ipv6 + + + + + + + operating status of the VM + valid value example: STARTED (POWER_ON), STOPPED (POWER_OFF) + + + + + + + provisioning status, used as a trigger for operational monitoring of this resource by service assurance systems + valid value example: PROVISIONED, PREPROVISIONED, CAPPED + + + + + + + whether the NFC instance is in maintenance mode, if yes, DCAE will not observe alarms/traps, etc. + + + + + + + + whether closed loop function is enabled + + + + + + + + An intelligent or human readable name of the vnfc instance + + + + + + Reference to the connection points of the vnfc + + + + + + + Identifier of the policy which has the naming logic for this VNFC instance + + + + + + Additional intelligent or human readable name of the vnfc instance + + + + + + + English description of network function component that the specific VNFC deployment is providing. + + + + + + indicator for whether the resource is considered operational. Valid values are in-service-path and out-of-service-path. + + + + + whether the VNFC instance is instantiated + + + + + Whether closed loop capabilities are enabled for this or not. + + + + + Reference to the VDU + + + + + + + + + + + + + + + + This information element describes compute, memory and I/O requirements that are to be associated with the logical node of infrastructure. The logical node requirements are a sub-component of the VDU level requirements. As an example for illustration purposes, a logical node correlates to the concept of a NUMA cell in libvirt terminology. + + + + 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. + + + + + + + + + + This information element describes requested additional capability for a particular VDU. Such a capability may be for acceleration or specific tasks. + + + + Indicates whether the requested additional capability is mandatory for successful operation. + + + + + + Identifies a requested additional capability for the VDU. + + + + + + + Identifies the minimum version of the requested additional capability. + + + + + + + + Identifies the preferred version of the requested additional capability. + + + + + + + + Identifies specific attributes, dependent on the requested additional capability type. + + + + + + + + + + Amount of virtual Memory (e.g. in MB). + + + + + + The 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. + + + + + + + + Array of key-value pair requirements on the memory for the VDU. + + + + + + + + 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. + + + + + + + + + + The VirtualCpuData information element supports the specification of requirements related to virtual CPU(s) of a virtual compute resource. + + + + CPU architecture type. Examples are x86, ARM. The cardinality can be 0 during the allocation request, if no particular CPU architecture type is requested. + + + + + + + + Number of virtual CPUs. + + + + + + Minimum virtual CPU clock rate (e.g. in MHz). The cardinality can be 0 during the allocation request, if no particular value is requested. + + + + + + + + The 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. + + + + + + + + Array of key-value pair requirements on the Compute (CPU) for the VDU. + + + + + + + + The virtual CPU pinning configuration for the virtualised compute resource. + + + + + + + + The VirtualCpuPinningData information element supports the specification of requirements related to the virtual CPU pinning configuration of a virtual compute resource. + + + + 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). + + + + + + + + A list of rules that should be considered during the allocation of the virtual CPUs to logical CPUs in case of "static" virtualCpuPinningPolicy. + + + + + + + + The AddressData information element supports providing information about the addressing scheme and parameters applicable to a CP. + + + + 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. + + + + + + + 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. + + + + + + + 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. + + + + + + + + A CpProtocolData information element describes and associates the protocol layer that a CP uses together with other protocol and connection point information. + + + + One of the values of the attribute layerProtocol of the Cpd IE. + + + + + + Provides information on the addresses to be assigned to the CP(s) instantiated from the CPD. + + + + + + + + + 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. + + + + + + + + The L3AddressData information element supports providing information about Layer 3 level addressing scheme and parameters applicable to a CP. + + + + 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. + + + + + + + Specify if the floating IP scheme is activated on the CP or not. + + + + + + Define address type. + +NOTE: The address type should be aligned with the address type supported by the layerProtocol attribute of the parent Cpd. + + + + + + + + + Minimum number of IP addresses to be assigned based on this L3AddressData information element. + + + + + + + + + The LocalAffinityOrAntiAffinityRule describes the affinity or anti-affinity rule applicable between the virtualization containers to be created based on a particular VDU, or between internal VLs to be created based on a particular VnfVirtualLinkDesc. +Per VNF, the affinity/anti-affinity rules defined using this information element, using the AffinityOrAntiAffinityGroup information element, and using the placement constraints in the GrantLifecycleOperation as defined in ETSI GS NFV IFA 007 [i.3] should be conflict-free. In case of conflicts, the placement constraints in the GrantLifecycleOperation shall take precedence. + + + + + Specifies whether the rule is an affinity rule or an anti-affinity rule. + + + + + + Specifies the scope of the rule. + + + + + + The QoS information element describes QoS data for a given VL used in a DF. + + + + Maximum latency in ms. + + + + + + + Maximum jitter in ms. + + + + + + Maximum packet loss ratio. Cardinality is 0 if no packetLossRatio requirement exists. + + + + + + + + + + Identifies the protocol this VL gives access to (Ethernet, MPLS, ODU2, IPV4, IPV6, Pseudo-Wire). + + + + + + Identifies the flow pattern of the connectivity (Line, Tree, Mesh). + + + + + + + + + The LinkBitrateRequirements information element describes the requirements in terms of bitrate for a VL. + + + + 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). + + + + + + + + + + This datatype defines the configurable properties of a VNF (e.g. related to auto scaling and auto healing). For a VNF instance, the value of these properties can be modified by the VNFM + + + + 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. + + + + + + + + + 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. + + + + + + + + + + + + + + + This datatype defines the VNF-specific extension and metadata attributes of the VnfInfo that are writeable via the ModifyVnfInfo operation. + + + + + + "Extension" attributes of VnfInfo that are writeable. + + + + + + + Metadata" attributes of VnfInfo that are writeable + + + + + + + + + Describes VNF lifecycle event(s) or an external stimulus detected on a VNFM reference point. + + + + + + + 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. + + + + + + + + + Information 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. + + + + + + Defines the domain specific language (i.e. the type) of script that is provided. Types of scripts could include bash, python, etc. + + + + + + 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. + + + + + + + + + + Specifies the virtualised resource related performance metric to be tracked by the VNFM, e.g. for auto-scaling purposes. The VNFM collects the values of performance metrics identified by this information element from the VIM(s) using one or more locally initiated PM Jobs. These values can be used as inputs to auto-scaling rules. + + + + Unique identifier of the monitoring parameter. + + + + + + Human readable name of the monitoring parameter. + + + + + + + + + + + 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. + + + + + + + + + This datatype defines the configurable properties of a VNFC. For a VNFC instance, the value of these properties can be modified through the VNFM. + + + + It provides VNFC configurable properties that can be modified using the ModifyVnfInfo operation. + + + + + + + + + Describes the type of VNIC to which a CP attaches. + + + + + + + + + + + Type of network supported. + + + + + + + The ScaleInfo information element represents a scale level for a particular scaling aspect. + + + + Reference to the scaling aspect. + + + + + + The scale level, greater than or equal to 0 + + + + + + + Specifies the type of rule. + + + + + + + Defines the scope of the rule. + + + + + + + + + Identifies the protocol this VL gives access to + + + + + + + + + + + Defines the CPU pinning policy. + + + + + + + Describes VNF lifecycle event(s) or an external stimulus detected on a VNFM reference point. + + + + + Describes the source of the indicator. + + + + + + + + Specifies the periodicity at which the producer will collect performance information. + + + + + + + + + + + + + + The VirtualLinkBitRateLevel information element specifies bitrate requirements applicable to a virtual link instantiated from a particular VnfVirtualLinkDesc. + + + + + + + + + Provisioning status, used as a trigger for operational monitoring of this resource by service assurance systems. + + + + + + + + Indicator for whether the resource is considered operational. Valid values are in-service-path and out-of-service-path. + + + + + + + + + + + + + +
+
+
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + -- cgit 1.2.3-korg