From 2d9a0e5cc3ec032c3b401d09eedca8f197d6eace Mon Sep 17 00:00:00 2001 From: FernandoOliveira Date: Wed, 16 Sep 2020 13:59:13 -0400 Subject: Updated the VNF model to align with IFA011 v3.3.1 - Added VnfPackageChangeInfo Class used in the VNFD and various subclasses - Added VnfLcmOperationCoordination Class used in the VNFD and various subclasses - A few minor changes to the NS model to align with ETSI IFA014 v3.3.1 - Added new VNF types to the VNF type diagram Issue-ID: MODELING-334 Signed-off-by: Fernando Oliveira Change-Id: Icd1fa97f2d519d0d208c989f0cc1b8689fb4a440 --- ONAP_Information_Model/Common.notation | 136 +- ONAP_Information_Model/Ns.notation | 580 +++--- ONAP_Information_Model/Ns.uml | 48 +- ONAP_Information_Model/Vnf.notation | 3178 +++++++++++++------------------- ONAP_Information_Model/Vnf.uml | 937 +++++----- 5 files changed, 2135 insertions(+), 2744 deletions(-) (limited to 'ONAP_Information_Model') diff --git a/ONAP_Information_Model/Common.notation b/ONAP_Information_Model/Common.notation index e36d41e..0097b88 100644 --- a/ONAP_Information_Model/Common.notation +++ b/ONAP_Information_Model/Common.notation @@ -156,45 +156,45 @@ - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + @@ -274,55 +274,55 @@ - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + @@ -1708,24 +1708,6 @@ - - - - - - - - - - - - - - - - - - @@ -1784,24 +1766,6 @@ - - - - - - - - - - - - - - - - - - diff --git a/ONAP_Information_Model/Ns.notation b/ONAP_Information_Model/Ns.notation index 318b96a..67e9f49 100644 --- a/ONAP_Information_Model/Ns.notation +++ b/ONAP_Information_Model/Ns.notation @@ -376,69 +376,69 @@ - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + @@ -674,85 +674,85 @@ - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + @@ -1173,93 +1173,93 @@ - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + @@ -1728,115 +1728,115 @@ - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + @@ -2252,85 +2252,85 @@ - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + @@ -2704,105 +2704,105 @@ - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + diff --git a/ONAP_Information_Model/Ns.uml b/ONAP_Information_Model/Ns.uml index 946eedd..0472b73 100644 --- a/ONAP_Information_Model/Ns.uml +++ b/ONAP_Information_Model/Ns.uml @@ -385,6 +385,20 @@ NOTE: Every VNF, VL and nested NS whose descriptor is referenced by the NS DF sh + + + Specifies the priority for the NS instance. + + + + + + + If present, specifies the service availability level for the NS instance created from this DF. + + + + @@ -457,6 +471,13 @@ NOTE: Each identifier references an affinity or anti-affinity group which expres + + + If present, specifies the service availability level for the VNF instance created from this profile. + + + + @@ -1089,13 +1110,14 @@ NOTE 2: A minimum set of external stimulus includes: the receipt of request mess - + Specifies one of the three levels defined in ETSI GS NFV-REL 001: • Level 1 • Level 2 • Level 3 + @@ -1287,18 +1309,6 @@ When only one value is provided, the ingress and egress traffic is associated to - - - Specifies one of the three levels defined in ETSI GS NFV-REL 001: -• Level 1 -• Level 2 -• Level 3 - - - - - - @@ -1560,7 +1570,7 @@ When only one value is provided, the ingress and egress traffic is associated to - + @@ -1572,4 +1582,14 @@ When only one value is provided, the ingress and egress traffic is associated to + + + + + + + + + + diff --git a/ONAP_Information_Model/Vnf.notation b/ONAP_Information_Model/Vnf.notation index f371437..c3e8287 100644 --- a/ONAP_Information_Model/Vnf.notation +++ b/ONAP_Information_Model/Vnf.notation @@ -97,24 +97,6 @@ - - - - - - - - - - - - - - - - - - @@ -666,56 +648,7 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + @@ -855,7 +788,7 @@ - + @@ -935,7 +868,7 @@ - + @@ -1042,7 +975,7 @@ - + @@ -1141,7 +1074,7 @@ - + @@ -1211,141 +1144,193 @@ - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - - - - - - - - - - - - - - - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -1380,7 +1365,7 @@ - + @@ -1448,40 +1433,9 @@ - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + @@ -1544,7 +1498,7 @@ - + @@ -1641,37 +1595,6 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - @@ -1714,11 +1637,11 @@ - + - + @@ -1730,7 +1653,7 @@ - + @@ -1741,7 +1664,7 @@ - + @@ -1853,7 +1776,7 @@ - + @@ -1875,30 +1798,38 @@ - + - + + - + + - + + - + + - + + - + + + + @@ -1907,7 +1838,7 @@ - + @@ -1942,7 +1873,7 @@ - + @@ -1958,9 +1889,9 @@ - - - + + + @@ -1993,175 +1924,237 @@ - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - - - - - - - - - - - - - - - - - - - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2261,24 +2254,6 @@ - - - - - - - - - - - - - - - - - - @@ -3153,101 +3128,101 @@ - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + @@ -3421,37 +3396,6 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - @@ -3776,125 +3720,125 @@ - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + @@ -4991,736 +4935,6 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - @@ -8456,333 +7670,537 @@ - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -8790,415 +8208,455 @@ - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -10269,173 +9727,173 @@ - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + - - - + + + - + @@ -10863,215 +10321,215 @@ - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + diff --git a/ONAP_Information_Model/Vnf.uml b/ONAP_Information_Model/Vnf.uml index 118f385..1883021 100644 --- a/ONAP_Information_Model/Vnf.uml +++ b/ONAP_Information_Model/Vnf.uml @@ -44,24 +44,6 @@ - - -
- - - - - - - - -
- - - - - -
@@ -151,15 +133,6 @@ NOTE: More software images can be attached to the virtualisation container using - - -
- - - - - -
@@ -201,12 +174,6 @@ NOTE 2: virtualLinkProfile needs to be provided for all VLs that the CPs of the - - -
- - -
@@ -228,43 +195,6 @@ NOTE 2: virtualLinkProfile needs to be provided for all VLs that the CPs of the - - -
- - - - - - - - - - - - -
- - - - - -
- - - - - -
- - - - - -
- - -
@@ -575,130 +505,21 @@ The Uses relationship is covered by the service instance expressing the sharable - Pnfs cannot run on Pnfs, etc. + + +
+ + + + + +
+ + + - - - 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'. - - - - - - - - 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. "key/name" indicates the the boot index "value" references a descriptor from which a valid boot device is created e.g. VirtualStorageDesc from which a VirtualStorage instance is created. - -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. "key/name" includes "AvailabilityZone", "HostAggregates". - -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. - - - - - - Contains a string or a URL to a file contained in the VNF package used to customize a virtualised compute resource at boot time. The bootData may contain variable parts that are replaced by deployment specific values before being sent to the VIM. -NOTE: The parameters of each variable part shall be declared in the VnfLcmOperationsConfiguration information element as "volatile" parameters available to the bootData template during the respective VNF lifecycle management operation execution and/or in the extension attribute of the VnfInfoModifiableAttributes information element as "persistent" parameters available to the bootData template during the lifetime of the VNF instance. For VNF lifecycle management operations resulting in multiple VNFC instantiations, the VNFM supports the means to provide the appropriate parameters to appropriate VNFC instances Experimental - - - - - - - - - - - - Describes network connectivity between a VNFC instance (based on this Vdu) and an internal 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. @@ -708,6 +529,15 @@ NOTE: More software images can be attached to the virtualisation container using + + + 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. + + + Provider of the VNF and of the VNFD. @@ -767,23 +597,6 @@ NOTE: This allows to provide one or more localization languages to support selec - - - 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). Refer to ISO936 https://www.iso.org/iso-639-language-codes.html @@ -795,57 +608,93 @@ NOTE: This allows to provide one or more localization languages to support selec - - - Describes the configurable properties of the VNF (e.g. related to auto scaling and auto healing). + + + Virtualisation Deployment Unit. - - + + - - - Includes a list of events and corresponding management scripts performed for the VNF. + + + Defines descriptors of virtual compute resources to be used by the VNF. - - + + - - - File path of the vendor specified logo. + + + Defines descriptors of virtual storage resources to be used by the VNF. - - - + + - - - UUID of the vendor guide/documentation which is attached to VNF and can be downloaded from the model. + + + Defines descriptors of software images to be used by the VNF. +NOTE: This shall be used to describe both the software image loaded on the virtualization container used to realize a VDU and the software images to be stored on VirtualStorage resources (e.g., volumes) attached to a virtualization container. + - - - + + - - - Virtualisation Deployment Unit. + + + Represents the type of network connectivity mandated by the VNF provider between two or more CPs which includes at least one internal CP. - - + + + + + + Defines security group rules to be used by the VNF. + + + - + Describes external interface(s) exposed by this VNF enabling connection with a VL. - + + + Describes virtual IP addresses to be shared among instances of connection points. + + + + + Describes specific DF(s) of a VNF with specific requirements for capacity and performance. + + + Describes the configurable properties of the VNF (e.g. related to auto scaling and auto healing). + + + + + + + Defines the VNF-specific extension and metadata attributes of the VnfInfo that are writeable via the ModifyVnfInfo operation. + + + + + + + + Includes a list of events and corresponding management scripts performed for the VNF. + + + + Declares the VNF indicators that are supported by this VNF. @@ -853,63 +702,148 @@ NOTE: This allows to provide one or more localization languages to support selec - - - Defines descriptors of virtual compute resources to be used by the VNF. + + + Rule that determines when a scaling action needs to be triggered on a VNF instance e.g. based on certain VNF indicator values or VNF indicator value changes or a combination of VNF indicator value(s) and monitoring parameter(s). + + + + + + + + Information used for performing the change of the current VNF Package. More than one VNF Package Change Info construct is possible to cater the possibility that changes of the current VNF Package can be performed for different source VNFDs. + + + + + + + Provides information used for the coordination in VNF LCM operations. + + + + + + + + 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'. + + + + + + + + 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. "key/name" indicates the the boot index "value" references a descriptor from which a valid boot device is created e.g. VirtualStorageDesc from which a VirtualStorage instance is created. + +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. "key/name" includes "AvailabilityZone", "HostAggregates". + +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. - - + + - - - Defines descriptors of virtual storage resources to be used by the VNF. + + + Describes the information (e.g. URL) about the scripts, config drive metadata, etc. which can be used during Vdu booting process. - - + + + - - - 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. + + + Describes the configurable properties of all VNFC instances based on this VDU. - - + - - - Describes the associated elements of a VNFD for a certain purpose during VNF lifecycle management. + + + Contains a string or a URL to a file contained in the VNF package used to customize a virtualised compute resource at boot time. The bootData may contain variable parts that are replaced by deployment specific values before being sent to the VIM. +NOTE: The parameters of each variable part shall be declared in the VnfLcmOperationsConfiguration information element as "volatile" parameters available to the bootData template during the respective VNF lifecycle management operation execution and/or in the extension attribute of the VnfInfoModifiableAttributes information element as "persistent" parameters available to the bootData template during the lifetime of the VNF instance. For VNF lifecycle management operations resulting in multiple VNFC instantiations, the VNFM supports the means to provide the appropriate parameters to appropriate VNFC instances Experimental + + + + - - + + + - - - Defines descriptors of software images to be used by the VNF. -NOTE: This shall be used to describe both the software image loaded on the virtualization container used to realize a VDU and the software images to be stored on VirtualStorage resources (e.g., volumes) attached to a virtualization container. - + + + Describes network connectivity between a VNFC instance (based on this Vdu) and an internal Virtual Link (VL). - - - - - Represents the type of network connectivity mandated by the VNF provider between two or more CPs which includes at least one internal CP. + + + Describes CPU, Memory and acceleration requirements of the Virtualisation Container realising this Vdu. - - + + - - - Defines security group rules to be used by the VNF. + + + Describes storage requirements for a VirtualStorage instance attached to the virtualisation container created from virtualComputeDesc defined for this Vdu. - - + + - - - Describes virtual IP addresses to be shared among instances of connection points. + + + 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. + - - + + + + + + @@ -1376,35 +1310,6 @@ NOTE: In the present specification, including either VDU(s) or VnfVirtualLinkDes - - - 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. - - - - Declares the VNF indicators that are supported by this VNF (specific to this DF). @@ -1619,92 +1524,36 @@ NOTE: If not present, it is assumed that the bitrate requirements can be derived - - - 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. + + + A VipCpd is a type of Cpd and describes a requirement to allocate one or a set of virtual IP addresses. A VipCpd inherits from the Cpd Class . All attributes of the Cpd are also attributes of the VipCpd. When intCpds are indicated, instances of VduCps created from those intCpds share the addresses created from the VipCpd. When vnfExtCpds are indicated, instances of VnfExtCps created from those vnfExtCpds share the addresses created from the VipCpd. - - - Unique identifier of this group in the VNFD. + + + + + + References the internal VDU CPD which is used to instantiate internal CPs. These internal CPs share the virtual IP addresses allocated when a VipCp instance is created from the VipCpd. + + - - - Human readable description of the group. - - - - - - References to Vdus that are part of this group. - - - - - - - References to VnfVirtualLinkDesc that are part of this group. + + + References the VNF external CPD which is used to instantiate external CPs. These external CPs share the virtual IP addresses allocated when a VipCp instance is created from the VipCpd. - - - + + + - - - - 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). - - + + + It indicates the function the virtual IP address is used for. - - - - - - - + + + @@ -2100,15 +1949,6 @@ NOTE : Each identifier references an affinity or anti-affinity group which expr - - - A ScalingGroup determines which VNFC's (VDU's) are scaled together based on demand. - - - - - - A graph of logical links connecting NF nodes,where at least one node is a VNF, for the purpose of describing traffic flow between these network functions @@ -2334,37 +2174,6 @@ Note: IFA011 defines this as an enum, but as the list is not complete, made this - - - A VipCpd is a type of Cpd and describes a requirement to allocate one or a set of virtual IP addresses. A VipCpd inherits from the Cpd Class . All attributes of the Cpd are also attributes of the VipCpd. When intCpds are indicated, instances of VduCps created from those intCpds share the addresses created from the VipCpd. When vnfExtCpds are indicated, instances of VnfExtCps created from those vnfExtCpds share the addresses created from the VipCpd. - - - - - - - References the internal VDU CPD which is used to instantiate internal CPs. These internal CPs share the virtual IP addresses allocated when a VipCp instance is created from the VipCpd. - - - - - - - - References the VNF external CPD which is used to instantiate external CPs. These external CPs share the virtual IP addresses allocated when a VipCp instance is created from the VipCpd. - - - - - - - - It indicates the function the virtual IP address is used for. - - - - - The VnfInterfaceDetails information element specifies the details of an interface produced by the VNF on the Ve-Vnfm reference point. @@ -2390,6 +2199,123 @@ Note: IFA011 defines this as an enum, but as the list is not complete, made this + + + The ChecksumData information element supports providing information about the result of performing a checksum operation over some arbitrary data. + + + + Species the algorithm used to obtain the checksum value. + + + + + + Contains the result of applying the algorithm indicated by the algorithm attribute to the data to which this ChecksumData refers. + + + + + + + A VnfPackageChangeInfo information element describes the processes and rules to be used for performing the resource related tasks while assisting the "change current VNF Package" to change a VNF instance to a different VNF Package (destination package). When creating a VNF package, the VNF vendor can include VnfPackageChangeInfo information elements in the package which allow the package to act as a source package or as a destination package for a modification in relation to another package, which has been created earlier or at the same time. +To populate a VnfPackageChangeInfo information element and the underlying related information elements, knowledge of both the source package and the destination package is required. + + + + Information to identify the source and destination VNFD for the change, and the related deployment flavours. + + + + + References the ChangeCurrentVnfPackageOpConfig information element that defines the valid additional parameters for the change. + + + + + + + Specifies the type of modification resulting from transitioning from srcVnfdId to dstVnfdId. The possible values are: UP - indicating that the destination VNF version is newer than the source version, DOWN - indicating that the destination VNF version is older than the source version. + + + + + A VNF provider may define additional information to qualify further the change between the two versions, such as "VNF upgrade", "VNF update", "VNF downgrade", etc. + + + + + + + + Mapping information related to identifiers of components in source VNFD and destination VNFD that concern to the change process. + + + + + + + References a lifecycle management script that is executed as part of this "change current VNF Package" process. + + + + + + References applicable VNF LCM operation coordination actions. + + + + + + + + Identifies the deployment flavour in the destination VNF package for which this change applies. The flavour ID is defined in the destination VNF package. + + + + + + + + + + + This information element defines the sets of information needed for a coordination action in a VNF lifecycle management operation. + + + + Identifies the specific VNF LCM operation coordination action. + + + + + + Human readable description of the coordination action. + + + + + + Specifies the type of the endpoint exposing the LCM operation coordination such as other operations supporting or management systems (e.g. an EM) or the VNF instance. Allowed values: • MGMT: coordination with other operation supporting management systems. • VNF: coordination with the VNF instance. + + + + + Indicates the coordination stage during the VNF LCM operation. + + + + + + Input information needed by the external coordinating entity. + + + + + + + + @@ -3007,21 +2933,56 @@ The attached VDUs shall connect to the same internal VLD. - - - The ChecksumData information element supports providing information about the result of performing a checksum operation over some arbitrary data. + + + The VersionSelector information element allows to identify the source and destination VNFDs (and implicitly, VNF packages) for a "change current VNF Package", as well as the applicable source deployment flavour. The triplet (srcVnfdId, srcFlavourId, dstVnfdId) uniquely determines a change. - - - Species the algorithm used to obtain the checksum value. + + + Identifier of the source VNFD and the source VNF package. - + - - - Contains the result of applying the algorithm indicated by the algorithm attribute to the data to which this ChecksumData refers. + + + Identifier of the destination VNFD and the destination VNF package - + + + + + Identifier of the deployment flavour in the source VNF package for which this modification applies. + + + + + + + With respect to a "change current VNF Package" process, a ComponentMapping information element defines a mapping between the identifier of a components or property in the source VNFD and the identifier of the corresponding component or property in the destination VNFD. Examples for components are VDUs, VLDs, etc., and an example for a property is a scaling aspect of the VNF. + + + + The type of component or property. Possible values differentiate whether changes concern to some VNF component (e.g. VDU, internal VLD, etc.) or property (e.g. a Scaling Aspect, etc.). + + + + + Identifier of the component or property in the source VNFD. + + + + + + Identifier of the component or property in the destination VNFD. + + + + + + Human readable description of the component changes. + + + @@ -3050,8 +3011,6 @@ The attached VDUs shall connect to the same internal VLD. - - @@ -3064,25 +3023,13 @@ The attached VDUs shall connect to the same internal VLD. - - - - - - - - - - - - @@ -3110,16 +3057,12 @@ The attached VDUs shall connect to the same internal VLD. - - - - @@ -3164,11 +3107,6 @@ The attached VDUs shall connect to the same internal VLD. - - - - - @@ -3194,20 +3132,6 @@ The attached VDUs shall connect to the same internal VLD. - - - - - - - - - - - - - - @@ -3318,8 +3242,6 @@ The attached VDUs shall connect to the same internal VLD. - - @@ -3338,9 +3260,6 @@ The attached VDUs shall connect to the same internal VLD. - - - @@ -3461,15 +3380,12 @@ The attached VDUs shall connect to the same internal VLD. - - - @@ -3479,12 +3395,8 @@ The attached VDUs shall connect to the same internal VLD. - - - - @@ -3582,12 +3494,10 @@ The attached VDUs shall connect to the same internal VLD. - + - - @@ -3681,7 +3591,6 @@ The attached VDUs shall connect to the same internal VLD. - @@ -3703,7 +3612,6 @@ The attached VDUs shall connect to the same internal VLD. - @@ -3716,8 +3624,6 @@ The attached VDUs shall connect to the same internal VLD. - - @@ -3884,4 +3790,47 @@ The attached VDUs shall connect to the same internal VLD. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + -- cgit 1.2.3-korg