Identifier of the "vnfcCpInfo" structure in "VnfcResourceInfo" structure that
represents the VNFC CP which is exposed by this external CP instance, either
directly or via a floating IP address. Shall be present in case this CP instance
maps to a VNFC CP.
The attributes "associatedVnfcCpId", "associatedVipCpId" and "associatedVnfVirtualLinkId"
are mutually exclusive. Exactly one shall be present.
Identifier of the "vnfcCpInfo" structure in "VnfcResourceInfo" structure that represents the VNFC CP which
is exposed by this external CP instance, either directly or via a floating IP address. Shall be present in
case this CP instance maps to a VNFC CP. See note 1.
$ref:"#/definitions/IdentifierInVnf"
associatedVipCpId:
description:>
...
...
@@ -1133,9 +1141,7 @@ definitions:
the internal VL or of the "ExtManagedVirtualLinkInfo" structure that represents
the externally-managed internal VL, which is exposed by this external CP instance.
Shall be present in case this CP instance maps to an internal VL (including
externally-managed internal VL).
The attributes "associatedVnfcCpId", "associatedVipCpId" and
"associatedVnfVirtualLinkId" are mutually exclusive. Exactly one shall be present.
externally-managed internal VL). See note 1.
$ref:"#/definitions/IdentifierInVnf"
CpGroupInfo:
...
...
@@ -1562,16 +1568,11 @@ definitions:
description:>
This type represents a link port of an internal VL of a VNF.
It shall comply with the provisions defined in table 6.5.3.64-1.
NOTE 1: Either cpInstanceId with cpInstanceType set to "EXT_CP"
or any combination of cpInstanceId with cpInstanceType set to "VNFC_CP"
and vipCpInstanceId (i.e. one or both of them) shall be present
for a VnfLinkPortInfo. In case both cpInstanceId with cpInstanceType.
NOTE 2: Annex A.4 of ETSI GS NFV-IFA 007 [19] provides examples for
configurations where both vipCpInstanceId and vnfcCpInstanceId are
present (UC#5 and UC#5-b), only vnfcCpInstanceId is present (UC#2),
or only vipCpInstanceId is present (UC#6 and UC#6-b).
NOTE 3: The value of "trunkResourceId" is scoped by the value of
"vimConnectionId" in the "resourceHandle" attribute.
NOTE 1: Either cpInstanceId with cpInstanceType set to "EXT_CP" or any combination of cpInstanceId with
cpInstanceType set to "VNFC_CP" and vipCpInstanceId (i.e. one or both of them) shall be present for a
VnfLinkPortInfo. In case both cpInstanceId with cpInstanceType set to "VNFC_CP" and vipCpInstanceId are present,
the two different CP instances share the linkport.
required:
-id
-resourceHandle
...
...
@@ -2361,15 +2362,14 @@ definitions:
description:>
This operation supports the update of a NS instance operation.
NOTE 1: The DF of the VNF instance shall match the VNF DF present in the associated VNF Profile.
NOTE 2: The NS DF of each nested NS shall be one of the allowed flavours in the associated NSD
(as referenced in the nestedNsd attribute of the NSD of the NS to be instantiated).
NOTE 3: The NSD of each referenced NSs (i.e. each nestedInstanceId) shall match the one of
the nested NSD in the composite NSD.
NOTE 4: When the NS is deployed over several sites, the VLs of this NS will include VNs
in each site connected over the WAN. In this case, the "wanConnectionData" provides the needed
information required to connect each VN to the WAN. Annex E provides additional information and
guidelines about the usage of the "wanConnectionData" attribute.
NOTE 1: If a VNF instance is removed from an NS and this NS was the last one for which this VNF instance was a
part, the VNF instance is terminated by the NFVO.
NOTE 2: It depends on the VNF capabilities, and is declared in the VNFD whether the operation is supported for
a particular VNF.
NOTE 3: The operation might be service-disruptive.
NOTE 4: For each of the referred vnfInstanceId in the terminateVnfData, there shall be a corresponding value
in the removeVnfInstanceId.
type:object
required:
-updateType
...
...
@@ -4013,7 +4013,7 @@ definitions:
description:>
Match particular notification types.
Permitted values:
- NsLcmOperationOccurenceNotification
- NsLcmOperationOccurrenceNotification
- NsIdentifierCreationNotification
- NsIdentifierDeletionNotification
- NsLcmCapacityShortageNotification
...
...
@@ -4433,23 +4433,48 @@ definitions:
LcmOpOccStatusForChangeNotificationType:
description:>
The enumeration LcmOpOccStatusForChangeNotificationType represents the status of the lifecycle management
operation occurrence that impacts the NS component and triggers an NS change notification. It shall comply with the
provisions defined in Table 6.5.4.7-1.
Value | Description
------|------------
START | The impact on the NS component is identified.
COMPLETED | The impact on the NS component stops and related lifecycle operation completes successfully.
PARTIALLY_COMPLETED | The impact on the NS component stops and related lifecycle operation partially completes. Inconsistency state may exist on the NS component.
FAILED | The impact on the NS component stops and related lifecycle operation fails. Inconsistency state may exist for the NS component.
ROLLED_BACK | The impact on the NS component stops and related lifecycle operation is rolled back.
The enumeration LcmOpNameForChangeNotificationType represents the name of the lifecycle operation that impacts the
NS component and trigger an NS change notification. It shall comply with the provisions defined in table 6.5.4.6-1.
Value | Description
VNF_INSTANTIATE Represents the "Instantiate VNF" LCM operation.
VNF_SCALE Represents the "Scale VNF" LCM operation.
VNF_SCALE_TO_LEVEL Represents the "Scale VNF to Level" LCM operation.
VNF_CHANGE_FLAVOUR Represents the "Change VNF Flavour" LCM operation.
VNF_TERMINATE Represents the "Terminate VNF" LCM operation.
VNF_HEAL Represents the "Heal VNF" LCM operation.
VNF_OPERATE Represents the "Operate VNF" LCM operation.
VNF_CHANGE_EXT_CONN Represents the "Change external VNF connectivity" LCM operation.
VNF_MODIFY_INFO Represents the "Modify VNF Information" LCM operation.
VNF_CREATE_SNAPSHOT Represents the "Create VNF Snapshot" LCM operation.
VNF_REVERT_TO_SNAPSHOT Represents the "Revert To VNF Snapshot" LCM operation.
VNF_CHANGE_VNFPKG Represents the "Change current VNF package" LCM operation.
NS_INSTANTIATE Represents the "Instantiate NS" LCM operation.
NS_SCALE Represents the "Scale NS" LCM operation.
NS_UPDATE Represents the "Update NS" LCM operation.
NS_TERMINATE Represents the "Terminate NS" LCM operation.
NS_HEAL Represents the "Heal NS" LCM operation.
type:string
enum:
-START
-COMPLETED
-PARTIALLY_COMPLETED
-FAILED
-ROLLED_BACK
-VNF_INSTANTIATE
-VNF_SCALE
-VNF_SCALE_TO_LEVEL
-VNF_CHANGE_FLAVOUR
-VNF_TERMINATE
-VNF_HEAL
-VNF_OPERATE
-VNF_CHANGE_EXT_CONN
-VNF_MODIFY_INFO
-VNF_CREATE_SNAPSHOT
-VNF_REVERT_TO_SNAPSHOT
-VNF_CHANGE_VNFPKG
-NS_INSTANTIATE
-NS_SCALE
-NS_UPDATE
-NS_TERMINATE
-NS_HEAL
NsLcmOpOcc:
description:>
...
...
@@ -4525,7 +4550,7 @@ definitions:
description:>
Input parameters of the LCM operation. This attribute
shall be formatted according to the request data type of
the related LCM operation.
the related LCM operation. In addition, the provisions in clause 6.7 shall apply.
The following mapping between lcmOperationType and
the data type of this attribute shall apply:
- INSTANTIATE: InstantiateNsRequest
...
...
@@ -4680,16 +4705,6 @@ definitions:
This attribute shall be present if the last known HTTP response related to this coordination has
contained a "Retry-After" header, and shall be absent otherwise.
