SOL002 VNF Lifecycle Management - Implementation of deltas between v3.5.1 and v3.3.1 (!220) · Merge requests · NFV - Network Functions Virtualisation / api-tests

SOL002/VNFLifecycleManagement-API/environment/variables.txt

+8 −24

Changes for SOL002/VNFLifecycleManagement-API/environment/variables.txt: 8 added lines, 24 removed lines.
Original line number	Diff line number	Diff line
		* Variables *
		${VNFM_HOST} localhost # Hostname of the VNFM
		${VNFM_PORT} 8080 # Listening port of the VNFM
		${NFVO_HOST} localhost # Hostname of the NFVO
		${NFVO_PORT} 8081 # Listening port of the NFVO

		${VNFM_SCHEMA} https
		${NFVO_SCHEMA} https

		${AUTHORIZATION_HEADER} Authorization
		${AUTHORIZATION_TOKEN} Bearer 0b79bab50daca910b000d4f1a2b675d604257e42
		${CONTENT_TYPE} application/json
		@@ -15,35 +14,22 @@ ${apiRoot} /
		${apiName} vnflcm
		${apiMajorVersion} v2
		${AUTH_USAGE} 1
		${WRONG_AUTHORIZATION} Bearer XXXXXWRONGXXXXX

		${vnfInstanceId} 6fc3539c-e602-4afa-8e13-962fb5a7d81f
		${vnfInstanceId_NoSnapshotTask} vnfInstanceIdForWhichSnapshotResourceDoesNotExist
		${vnfInstanceId_NOT_INSTANTIATED} vnfResourceIsInNOT_INSTANTIATEDstate
		${badVnfInstanceId} wrongId

		${instantiatedVnfInstanceId} 6fc3539c-e602-4afa-8e13-962fb5a7d81f #Change with an instantiated vnfInstanceID
		${conflicVnfInstanceId} 6fc3539c-e602-4afa-8e13-962fb5a7d81f
		${vnfInstanceName} Test-VnfInstance
		${vnfInstanceDescription} description vnf
		${vnfInstanceDescription_Update} Updated description vnf
		${SINGLE_FILE_VNFD} 1 # If VNFD is PLAIN TEXT
		${ACCEPT_PLAIN} text/plain
		${ACCEPT_ZIP} application/zip
		${vnfPkgId_processing} 007c111c-38a1-42c0-a666-7475ecb1567c
		${ARTIFACT_TYPE} application/octet-stream
		${ARTIFACT_ID} artifactId
		${WRONG_ACCEPT} application/json

		${vnfLcmOpOccId} 6fc3539c-e602-4afa-8e13-962fb5a7d81d
		${CancelMode} GRACEFUL
		${VNFM_DUPLICATION} 0
		${sub_filter} filter
		${sub_filter_invalid} filter_invalid
		${subscriptionId} 6fc3539c-e602-4afa-8e13-962fb5a7d81f
		${VnfLcmOperationOccurrenceNotification} {}
		${VnfIdentifierCreationNotification} {}
		${VnfIdentifierDeletionNotification} {}

		${notInstantiatedVnfInstanceId} NOT_INSTANTIATED_VNF_INSTANCE_ID
		${NOT_EXISTANT_VNF_INSTANCE_ID} NOT_EXISTANT_VNF_INSTANCE_ID
		${SYNC_MODE} 0

		${PAGING_SUPPORTED} 0

		@@ -56,7 +42,6 @@ ${callback_uri} http://localhost
		${callback_port} 9091
		${callback_endpoint} /endpoint
		${callback_endpoint_fwd} /endpoint/check
		${callback_endpoint_error} /endpoint_404
		${sleep_interval} 20s
		${total_polling_time} 2 min
		${polling_interval} 10 sec
		@@ -96,6 +81,7 @@ ${descriptorType} SOL006
		${check_multiple_instances} 0

		#############internal variables used for descriptor parsing################

		${tosca_type_VDU_compute} tosca.nodes.nfv.Vdu.Compute
		${tosca_type_VNF} tosca.nodes.nfv.VNF
		${tosca_type_virtual_link} tosca.nodes.nfv.VnfVirtualLink
		@@ -104,9 +90,7 @@ ${tosca_type_storage} tosca.nodes.nfv.Vdu.VirtualBlockStorage
		${tosca_type_derived_from_VNF}

		${VDU_IDs}
		${VNF_IDs}
		${virtualLink_IDs}
		${CP_IDs}

		${Storage_IDs}
		${internalCP_IDs}
		${externalCP_IDs}

SOL002/VNFLifecycleManagement-API/schemas/VnfLcmOperationOccurrenceNotification.schema.json

+91 −34

Changes for SOL002/VNFLifecycleManagement-API/schemas/VnfLcmOperationOccurrenceNotification.schema.json: 91 added lines, 34 removed lines.
Original line number	Diff line number	Diff line
		{
		"description": "This type represents a VNF lifecycle management operation occurrence notification, which informs the receiver of changes in the VNF lifecycle caused by a VNF LCM operation occurrence. The support of the notification is mandatory. This notification shall be triggered by the VNFM when there is a change in the VNF lifecycle caused by a VNF LCM operation occurrence, including: * Instantiation of the VNF * Scaling of the VNF instance (including auto-scaling) * Healing of the VNF instance (including auto-healing) * Change of the state of the VNF instance (i.e. Operate VNF) * Change of the deployment flavour of the VNF instance * Change of the external connectivity of the VNF instance * Termination of the VNF instance * Modification of VNF instance information and/or VNF configurable\n properties through the \"PATCH\" method on the \"Individual VNF instance\"\n resource.\nIf this is the initial notification about the start of a VNF LCM operation occurrence, it is assumed that the notification is sent by the VNFM before any action (including sending the grant request) is taken as part of the LCM operation. Due to possible race conditions, the \"start\" notification, the grant request and the LCM operation acknowledgment can arrive in any order at the NFVO, and the NFVO shall be able to handle such a situation. If this is a notification about a final or intermediate result state of a VNF LCM operation occurrence, the notification shall be sent after all related actions of the LCM operation that led to this state have been executed. The new state shall be set in the \"Individual VNF LCM operation occurrence\" resource before the notification about the state change is sent.\n",
		"description": "This type represents a VNF lifecycle management operation occurrence notification, which informs the receiver of changes in the VNF lifecycle caused by a VNF LCM operation occurrence. The support of the notification is mandatory. This notification shall be triggered by the VNFM when there is a change in the VNF lifecycle caused by a VNF LCM operation occurrence, including: * Instantiation of the VNF * Scaling of the VNF instance (including auto-scaling) * Healing of the VNF instance (including auto-healing) * Change of the state of the VNF instance (i.e. Operate VNF) * Change of the deployment flavour of the VNF instance * Change of the external connectivity of the VNF instance * Termination of the VNF instance * Modification of VNF instance information and/or VNF configurable\n properties through the \"PATCH\" method on the \"Individual VNF instance\"\n resource.\nIf this is the initial notification about the start of a VNF LCM operation occurrence, it is assumed that the notification is sent by the VNFM before any action (including sending the grant request) is taken as part of the LCM operation. Due to possible race conditions, the \"start\" notification, the grant request and the LCM operation acknowledgment can arrive in any order at the NFVO, and the NFVO shall be able to handle such a situation. If this is a notification about a final or intermediate result state of a VNF LCM operation occurrence, the notification shall be sent after all related actions of the LCM operation that led to this state have been executed. The new state shall be set in the \"Individual VNF LCM operation occurrence\" resource before the notification about the state change is sent. * NOTE 1:\tShall be present if the \"notificationStatus\" is set to \"RESULT\", the \"verbosity\" attribute is set\n to \"FULL\" and the operation has performed any resource modification. Shall be absent otherwise.\n This attribute contains information about the cumulative changes to virtualised resources that\n were performed so far by the VNF LCM operation occurrence and by any of the error handling\n procedures for that operation occurrence.\n NOTE 2:\tFor a particular affected VL, there shall be as many \"AffectedVirtualLink\" entries as needed\n for signalling the different types of changes, i.e. one per virtual link and change type.\n For instance, in the case of signaling affected VL instances involving the addition of a particular\n VL instance with links ports, one \"AffectedVirtualLink\" entry signals the addition of the VL by using\n the \"changeType\" attribute of \"AffectedVirtualLink\" structure equal to \"ADDED\", and another\n \"AffectedVirtualLink\" entry signals the addition of VNF link ports of the VL by using the\n \"changeType\" equal to \"LINK_PORT_ADDED\".\n",
		"type": "object",
		"required": [
		"id",
		@@ -61,7 +61,7 @@
		"type": "string"
		},
		"operation": {
		"description": "Value \| Description ------\|------------ INSTANTIATE \| Represents the \"Instantiate VNF\" LCM operation. SCALE \| Represents the \"Scale VNF\" LCM operation. SCALE_TO_LEVEL \| Represents the \"Scale VNF to Level\" LCM operation. CHANGE_FLAVOUR \| Represents the \"Change VNF Flavour\" LCM operation. TERMINATE \| Represents the \"Terminate VNF\" LCM operation. HEAL \| Represents the \"Heal VNF\" LCM operation. OPERATE \| Represents the \"Operate VNF\" LCM operation. CHANGE_EXT_CONN \| Represents the \"Change external VNF connectivity\" LCM operation. MODIFY_INFO \| Represents the \"Modify VNF Information\" LCM operation. CREATE_SNAPSHOT \| Represents the \"Create VNF Snapshot\" LCM operation. REVERT_TO_SNAPSHOT \| Represents the “Revert-To VNF Snapshot\" LCM operation. CHANGE_VNFPKG \| Represents the \"Change current VNF package\" LCM operation.\n",
		"description": "The enumeration LcmOpType defines the permitted values to represent VNF lifecycle operation types in VNF lifecycle management operation occurrence resources and VNF lifecycle management operation occurrence notifications. It shall comply with the provisions defined in table 5.5.4.5-1.\nValue \| Description ------\|------------ INSTANTIATE \| Represents the \"Instantiate VNF\" LCM operation. SCALE \| Represents the \"Scale VNF\" LCM operation. SCALE_TO_LEVEL \| Represents the \"Scale VNF to Level\" LCM operation. CHANGE_FLAVOUR \| Represents the \"Change VNF Flavour\" LCM operation. TERMINATE \| Represents the \"Terminate VNF\" LCM operation. HEAL \| Represents the \"Heal VNF\" LCM operation. OPERATE \| Represents the \"Operate VNF\" LCM operation. CHANGE_EXT_CONN \| Represents the \"Change external VNF connectivity\" LCM operation. MODIFY_INFO \| Represents the \"Modify VNF Information\" LCM operation. CREATE_SNAPSHOT \| Represents the \"Create VNF Snapshot\" LCM operation. REVERT_TO_SNAPSHOT \| Represents the ΓÇ£Revert-To VNF Snapshot\" LCM operation. CHANGE_VNFPKG \| Represents the \"Change current VNF package\" LCM operation.\n",
		"type": "string",
		"enum": [
		"INSTANTIATE",
		@@ -95,7 +95,7 @@
		"type": "string"
		},
		"affectedVnfcs": {
		"description": "Information about VNFC instances that were affected during the lifecycle operation. Shall be present if the \"notificationStatus\" is set to \"RESULT\" and the operation has performed any resource modification. Shall be absent otherwise. This attribute contains information about the cumulative changes to virtualised resources that were performed so far by the VNF LCM operation occurrence and by any of the error handling procedures for that operation occurrence.\n",
		"description": "Information about VNFC instances that were affected during the lifecycle operation. See note 1.\n",
		"type": "array",
		"items": {
		"description": "This type provides information about added, deleted, modified and temporary VNFCs.\n",
		@@ -186,10 +186,10 @@
		}
		},
		"affectedVirtualLinks": {
		"description": "Information about VL instances that were affected during the lifecycle operation. Shall be present if the \"notificationStatus\" is set to \"RESULT\" and the operation has performed any resource modification. Shall be absent otherwise. This attribute contains information about the cumulative changes to virtualised resources that were performed so far by the VNF LCM operation occurrence and by any of the error handling procedures for that operation occurrence.\n",
		"description": "Information about VL instances that were affected during the lifecycle operation. See note 1 and note 2.\n",
		"type": "array",
		"items": {
		"description": "This type provides information about added, deleted, modified and temporary VLs, and added or removed VNF link ports.\n",
		"description": "This type provides information about added, deleted, modified and temporary VLs, and added or removed VNF link ports.\nNOTE:\tWhen signalling the addition (LINK_PORT_ADDED) or removal (LINK_PORT_REMOVED) of VNF link ports, \n the \"networkResource\" attribute refers to the affected virtual link instance, not the link port \n instance. The resource handles of the affected VNF link ports can be found by dereferencing the \n identifiers in the \"vnfLinkPortIds\" attribute.\n",
		"type": "object",
		"required": [
		"id",
		@@ -248,7 +248,7 @@
		}
		},
		"vnfLinkPortIds": {
		"description": "Identifiers of the link ports of the affected VL (reference to the vnfLinkPortInfo) related to the change. Each identifier references a \"VnfLinkPortInfo\" structure. Shall be set when changeType is equal to \"LINK_PORT_ADDED\" or \"LINK_PORT_REMOVED\", and the related “VnfLinkPortInfo” structures are present (case \"added\") or have been present (case \"removed\") in the “VnfVirtualLinkResourceInfo” or \"ExtManagedVirtualLinkInfo\" structures that are represented by the \"vnfVirtualLinkResourceInfo\" or \"extManagedVirtualLinkInfo\" attribute in the \"VnfInstance\" structure. When signalling the addition (LINK_PORT_ADDED) or removal (LINK_PORT_REMOVED) of VNF link ports, the \"networkResource\" attribute refers to the affected virtual link instance, not the link port instance. The resource handles of the affected VNF link ports can be found by dereferencing the identifiers in the \"vnfLinkPortIds\" attribute.\n",
		"description": "Identifiers of the link ports of the affected VL related to the change. Each identifier references a \"VnfLinkPortInfo\" structure.\nShall be set when changeType is equal to \"LINK_PORT_ADDED\" or \"LINK_PORT_REMOVED\", and the related \"VnfLinkPortInfo\" structures are present (case \"added\") or have been present (case \"removed\") in the \"VnfVirtualLinkResourceInfo\" or \"ExtManagedVirtualLinkInfo\" structures that are represented by the \"vnfVirtualLinkResourceInfo\" or \"extManagedVirtualLinkInfo\" attribute in the \"VnfInstance\" structure. See note.\n",
		"type": "array",
		"items": {
		"description": "An identifier that is unique within a VNF descriptor.\n",
		@@ -263,7 +263,7 @@
		}
		},
		"affectedExtLinkPorts": {
		"description": "Information about external VNF link ports that were affected during the lifecycle operation. Shall be present if the \"notificationStatus\" is set to \"RESULT\", the \"verbosity\" attribute is set to \"FULL\" and the operation has performed any resource modification. Shall be absent otherwise. This attribute contains information about the cumulative changes to virtualised resources that were performed so far by the VNF LCM operation occurrence and by any of the error handling procedures for that operation occurrence.\n",
		"description": "Information about external VNF link ports that were affected during the lifecycle operation. See note 1.\n",
		"type": "array",
		"items": {
		"description": "This type provides information about added and deleted external link ports (link ports attached to external virtual links).\n",
		@@ -320,7 +320,7 @@
		}
		},
		"affectedVirtualStorages": {
		"description": "Information about virtualised storage instances that were affected during the lifecycle operation. Shall be present if the \"notificationStatus\" is set to \"RESULT\" and the operation has performed any resource modification. Shall be absent otherwise. This attribute contains information about the cumulative changes to virtualised resources that were performed so far by the VNF LCM operation occurrence and by any of the error handling procedures for that operation occurrence.\n",
		"description": "Information about virtualised storage instances that were affected during the lifecycle operation. See note 1.\n",
		"type": "array",
		"items": {
		"description": "This type provides information about added, deleted, modified and temporary virtual storage resources.\n",
		@@ -387,15 +387,15 @@
		}
		},
		"changedInfo": {
		"description": "This type represents attribute modifications that were performed on an \"Individual VNF instance\" resource. The attributes that can be included consist of those requested to be modified explicitly in the \"VnfInfoModificationRequest\" data structure, and additional attributes of the \"VnfInstance\" data structure that were modified implicitly e.g. when modifying the referenced VNF package.\n",
		"description": "This type represents attribute modifications that were performed on an \"Individual VNF instance\" resource. The attributes that can be included consist of those requested to be modified explicitly in the \"VnfInfoModificationRequest\" data structure, and additional attributes of the \"VnfInstance\" data structure that were modified implicitly e.g. when modifying the referenced VNF package. * NOTE:\tIf present, this attribute (which depends on the value of the \"vnfdId\" attribute)\n was modified implicitly following a request to modify the \"vnfdId\" attribute, by\n copying the value of this attribute from the VNFD in the VNF Package identified\n by the \"vnfdId\" attribute.\n",
		"type": "object",
		"properties": {
		"vnfInstanceName": {
		"description": "If present, this attribute signals modifications of the \"vnfInstanceName\" attribute in \"VnfInstance\".\n",
		"description": "If present, this attribute signals modifications of the \"vnfInstanceName\" attribute in \"VnfInstance\" as defined in clause 5.5.2.12..\n",
		"type": "string"
		},
		"vnfInstanceDescription": {
		"description": "If present, this attribute signals modifications of the \"vnfInstanceDescription\" attribute in \"VnfInstance\".\n",
		"description": "If present, this attribute signals modifications of the \"vnfInstanceDescription\" attribute in \"VnfInstance\", as defined in clause 5.5.2.12..\n",
		"type": "string"
		},
		"vnfConfigurableProperties": {
		@@ -415,11 +415,11 @@
		"type": "string"
		},
		"vnfProvider": {
		"description": "If present, this attribute signals modifications of the \"vnfProvider\" attribute in \"VnfInstance\". If present, this attribute (which depends on the value of the \"vnfPkgId\" attribute) was modified implicitly following a request to modify the \"vnfPkgId\" attribute, by copying the value of this attribute from the VNFD in the VNF Package identified by the \"vnfPkgId” attribute.\n",
		"description": "If present, this attribute signals modifications of the \"vnfProvider\" attribute in \"VnfInstance\". See note.\n",
		"type": "string"
		},
		"vnfProductName": {
		"description": "If present, this attribute signals modifications of the \"vnfProductName\" attribute in \"VnfInstance\". If present, this attribute (which depends on the value of the \"vnfPkgId\" attribute) was modified implicitly following a request to modify the \"vnfPkgId\" attribute, by copying the value of this attribute from the VNFD in the VNF Package identified by the \"vnfPkgId” attribute.\n",
		"description": "If present, this attribute signals modifications of the \"vnfProductName\" attribute in \"VnfInstance\". See note.\n",
		"type": "string"
		},
		"vnfSoftwareVersion": {
		@@ -431,10 +431,10 @@
		"type": "string"
		},
		"vnfcInfoModifications": {
		"description": "If present, this attribute signals modifications of certain entries in the \"vnfcInfo\" attribute array in the \"instantiatedVnfInfo\" attribute of \"VnfInstance\", as defined in clause 5.5.2.12\n",
		"description": "If present, this attribute signals modifications of certain entries in the \"vnfcInfo\" attribute array in the \"instantiatedVnfInfo\" attribute of \"VnfInstance\", as defined in clause 5.5.2.12.\n",
		"type": "array",
		"items": {
		"description": "This type represents modifications of an entry in an array of \"VnfcInfo\" objects. It shall comply with the provisions defined in table 5.5.3.24-1.\n",
		"description": "This type represents modifications of an entry in an array of \"VnfcInfo\" objects. * NOTE:\tThe attribute \"id\" in this data type represents the same identifier as the attribute\n \"vnfcInstanceId\" in other related data types in the present document. For reasons of backward\n compatibility, this misalignment is not corrected.\n",
		"type": "object",
		"required": [
		"id",
		@@ -454,10 +454,47 @@
		}
		}
		},
		"affectedVipCps": {
		"description": "Information about virtual IP CP instances that were affected during the execution of the lifecycle management operation, if this notification represents the result of a lifecycle management operation occurrence. Shall be present if the \"notificationStatus\" is set to \"RESULT\", the \"verbosity\" attribute is set to \"FULL\" and the operation has made any changes to the VIP CP instances of the VNF instance. Shall be absent otherwise. Only information about VIP CP instances that have been added, deleted or modified shall be provided.\n",
		"type": "array",
		"items": {
		"description": "This type provides information about added, deleted and modified virtual IP CP instances.\n",
		"type": "object",
		"required": [
		"cpInstanceId",
		"cpdId",
		"changeType"
		],
		"properties": {
		"cpInstanceId": {
		"description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
		"type": "string"
		},
		"cpdId": {
		"description": "An identifier that is unique within a VNF descriptor.\n",
		"type": "string"
		},
		"vnfdId": {
		"description": "An identifier with the intention of being globally unique.\n",
		"type": "string"
		},
		"changeType": {
		"description": "Signals the type of change. Permitted values: -\tADDED -\tREMOVED -\tMODIFIED\n",
		"type": "string",
		"enum": [
		"ADDED",
		"REMOVED",
		"MODIFIED"
		]
		}
		}
		}
		},
		"changedExtConnectivity": {
		"description": "Information about changed external connectivity, if this notification represents the result of a lifecycle operation occurrence. Shall be present if the \"notificationStatus\" is set to \"RESULT\" and the \"operation\" has made any change of the external connectivity of the VNF instance. Shall be absent otherwise.\n",
		"type": "array",
		"items": {
		"description": "This type represents information about an external VL. It shall comply with the provisions defined in table 5.5.3.2-1.\nNOTE:\tThis attribute reflects the current configuration information that has resulted from merging into this attribute \n the \"VnfExtCpData\" information which was passed as part of the \"ExtVirtualLinkData\" structure in the input of the \n most recent VNF LCM operation such as \"InstantiateVnfRequest\", \"ChangeExtVnfConnectivityRequest\", \"ChangeVnfFlavourRequest\" \n or \"ChangeCurrentVnfPkgRequest\", or in the Grant response. If applying such change results in an empty list of \n \"currentVnfExtCpData\" structure instances, the affected instance of \"ExtVirtualLinkInfo\" shall be removed from its \n parent data structure.\n",
		"type": "object",
		"required": [
		"id",
		@@ -498,7 +535,7 @@
		"description": "Link ports of this VL.\n",
		"type": "array",
		"items": {
		"description": "This type represents information about a link port of an external VL, i.e. a port providing connectivity for the VNF to an NS VL.\n",
		"description": "This type represents information about a link port of an external VL, i.e. a port providing connectivity for the VNF to an NS VL. It shall comply with the provisions defined in table 5.5.3.9-1.\nNOTE 1:\tThe use cases UC#4 and UC#5 in Annex A.4 of ETSI GS NFV-IFA 007 provide examples for such a configuration. NOTE 2:\tThe value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\" attribute.\n",
		"type": "object",
		"required": [
		"id",
		@@ -537,15 +574,23 @@
		"cpInstanceId": {
		"description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
		"type": "string"
		},
		"secondaryCpInstanceId": {
		"description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
		"type": "string"
		},
		"trunkResourceId": {
		"description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
		"type": "string"
		}
		}
		}
		},
		"currentVnfExtCpData": {
		"description": "Allows the API consumer to read the current CP configuration information for the connection of external CPs to the external virtual link. This attribute reflects the current configuration information that has resulted from merging into this attribute the \"VnfExtCpData\" information which was passed as part of the \"ExtVirtualLinkData\" structure in the input of the most recent VNF LCM operation such as \"InstantiateVnfRequest\", \"ChangeExtVnfConnectivityRequest\", \"ChangeVnfFlavourRequest\" or \"ChangeCurrentVnfPkgRequest\", or has been provided by the NFVO during the granting procedure. If applying such change results in an empty list of \"currentVnfExtCpData\" structure instances, the affected instance of \"ExtVirtualLinkInfo\" shall be removed from its parent data structure.\n",
		"description": "Allows the API consumer to read the current CP configuration information for the connection of external CPs to the external virtual link. See note.\n",
		"type": "array",
		"items": {
		"description": "This type represents configuration information for external CPs created from a CPD.\n",
		"description": "This type represents configuration information for external CPs created. * NOTE 1: \tIn case this identifier refers to a CPD with trunking enabled, the external CP instances created\n from this CPD will represent ports in a trunk.\n* NOTE 2: \tWithin one VNF instance, all VNFC instances created from a particular VDU have the same external\n connectivity. Thus, given a particular value of the \"cpdId\" attribute, there shall be one\n \"cpConfig\" entry for each VNFC instance that has been or can be created from a VDU which includes\n a CPD identified by the \"cpdId\" attribute. If the cpConfig represents a subport in a trunk,\n all \"cpConfig\" entries in this list shall have the same segmentationId, which means they are\n connected to the same set of external VLs via the trunk.\n* NOTE 3: \tThe map entry value shall be set to \"null\" in order to delete a \"VnfExtCpConfig\" entry identified\n by a particular key value from the map, i.e. for the disconnection of an existing external\n CP instance addressed by cpInstanceId in the deleted map entry from a particular external\n virtual link, and deletion of that instance in case it represents a subport. Deleting the\n last key from the map removes the affected instance of the \"VnfExtCpData\" structure from\n its parent data structure.\n",
		"type": "object",
		"required": [
		"cpdId"
		@@ -556,10 +601,10 @@
		"type": "string"
		},
		"cpConfig": {
		"description": "Map of instance data that need to be configured on the CP instances created from the respective CPD. The key of the map which identifies the individual VnfExtCpConfig entries is managed by the API consumer. The entries shall be applied by the VNFM according to the rules of JSON Merge Patch (see IETF RFC 7396). Within one VNF instance, all VNFC instances created from a particular VDU have the same external connectivity. Thus, given a particular value of the “cpdId” attribute, there shall be one “cpConfig” entry for each VNFC instance that has been or can be created from a VDU which includes a CPD identified by the “cpdId” attribute. If the cpConfig represents a subport in a trunk, all “cpConfig” entries in this list shall have the same segmentationId, which means they are connected to the same set of external VLs via the trunk. The map entry value shall be set to \"null\" in order to delete a \"VnfExtCpConfig\" entry identified by a particular key value from the map, i.e. for the disconnection of an existing external CP instance addressed by cpInstanceId in the deleted map entry from a particular external virtual link, and deletion of that instance in case it represents a subport. Deleting the last key from the map removes the affected instance of the \"VnfExtCpData\" structure from its parent data structure.\n",
		"description": "Map of instance data that need to be configured on the CP instances created from the respective CPD. The key of the map which identifies the individual VnfExtCpConfig entries is managed by the API consumer. The entries shall be applied by the VNFM according to the rules of JSON Merge Patch (see IETF RFC 7396). See note 2 and note 3.\n",
		"type": "object",
		"additionalProperties": {
		"description": "This type represents an externally provided link port or network address information per instance of an external connection point. In case a link port is provided, the VNFM shall use that link port when connecting the external CP to the external VL. In a link port is not provided, the VNFM shall create a link port on the external VL, and use that link port to connect the external CP to the external VL.\n",
		"description": "This type represents an externally provided link port or network address information per instance of an external connection point. In case a link port is provided, the VNFM shall use that link port when connecting the external CP to the external VL. In a link port is not provided, the VNFM shall create a link port on the external VL, and use that link port to connect the external CP to the external VL. * NOTE: The following conditions apply to the attributes \"linkPortId\" and \"cpProtocolData\":\n 1) Void.\n 2) At least one of the \"linkPortId\" and \"cpProtocolData\" attributes shall be present for an external\n CP instance representing a subport that is to be created, or an external CP instance that is to be\n created by creating the corresponding VNFC or VNF instance during the current or a subsequent LCM\n operation, or for an existing external CP instance that is to be re-configured or added to a\n particular external virtual link.\n 3) If the \"linkPortId\" attribute is absent, the VNFM shall create a link port.\n 4) If the \"cpProtocolData\" attribute is absent, the \"linkPortId\" attribute shall be provided referencing\n a pre created link port, and the VNFM can use means outside the scope of the present document to obtain\n the pre-configured address information for the connection point from the resource representing\n the link port.\n 5) If both \"cpProtocolData\" and \"linkportId\" are provided, the API consumer shall ensure that the\n cpProtocolData can be used with the pre-created link port referenced by \"linkPortId\".\n",
		"anyOf": [{
		"required": [
		"linkPortId"
		@@ -581,25 +626,29 @@
		"description": "An identifier with the intention of being globally unique.\n",
		"type": "string"
		},
		"createExtLinkPort": {
		"description": "Indicates to the VNFM the need to create a dedicated link port for the external CP. If set to True, the VNFM shall create a link port. If set to False, the VNFM shall not create a link port. This attribute is only applicable for external CP instances without a floating IP address that expose a VIP CP instance for which a dedicated IP address is allocated. It shall be present in that case and shall be absent otherwise.\n",
		"type": "boolean"
		},
		"cpProtocolData": {
		"description": "Parameters for configuring the network protocols on the link port that connects the CP to a VL. The following conditions apply to the attributes \"linkPortId\" and \"cpProtocolData\": 1) Void 2) At least one of the \"linkPortId\" and \"cpProtocolData\" attributes \n shall be present for an external CP instance representing a subport \n that is to be created, or an external CP instance that is to be created \n by creating the corresponding VNFC or VNF instance during the current or \n a subsequent LCM operation, or for an existing external CP instance \n that is to be re-configured or added to a particular external virtual link.\n3) If the \"linkPortId\" attribute is absent, the VNFM shall create a\n link port.\n4) If the \"cpProtocolData\" attribute is absent, the \"linkPortId\"\n attribute shall be provided referencing a pre-created link port,\n and the VNFM can use means outside the scope of the present\n document to obtain the pre-configured address information for the\n connection point from the resource representing the link port.\n5) If both \"cpProtocolData\" and \"linkportId\" are provided, the API\n consumer shall ensure that the cpProtocolData can be used with the\n pre-created link port referenced by \"linkPortId\".\n",
		"description": "Parameters for configuring the network protocols on the link port that connects the CP to a VL. See note.\n",
		"type": "array",
		"items": {
		"description": "This type represents network protocol data.\n",
		"description": "This type represents network protocol data. * NOTE:\tThis attribute allows to signal the addition of further types of layer and protocol\n in future versions of the present document in a backwards-compatible way. In the current\n version of the present document, only IP over Ethernet is supported.\n",
		"type": "object",
		"required": [
		"layerProtocol"
		],
		"properties": {
		"layerProtocol": {
		"description": "Identifier of layer(s) and protocol(s). This attribute allows to signal the addition of further types of layer and protocol in future versions of the present document in a backwards-compatible way. In the current version of the present document, only IP over Ethernet is supported.\n",
		"description": "Identifier of layer(s) and protocol(s). See note.\n",
		"type": "string",
		"enum": [
		"IP_OVER_ETHERNET"
		]
		},
		"ipOverEthernet": {
		"description": "This type represents network address data for IP over Ethernet.\n",
		"description": "This type represents network address data for IP over Ethernet. * NOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. * NOTE 2:\tExactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present. * NOTE 3:\tIf the CP instance represents a subport in a trunk, segmentationId shall be present.\n Otherwise it shall not be present.\n* NOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the actual\n network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header\n of the packets or it may be an identifier used between the application and the NFVI networking\n infrastructure to identify the network sub-interface of the trunk port in question. In the latter\n case the NFVI infrastructure will map this local segmentationId to whatever segmentationId is\n actually used by the NFVIΓÇÖs transport technology.\n",
		"type": "object",
		"anyOf": [{
		"required": [
		@@ -634,12 +683,20 @@
		"type": "string",
		"format": "MAC"
		},
		"segmentationType": {
		"description": "Specifies the encapsulation type for the traffics coming in and out of the trunk subport. Permitted values: -\tVLAN: the subport uses VLAN as encapsulation type. -\tINHERIT: the subport gets its segmentation type from the network itΓÇÖs connected to. This attribute may be present for CP instances that represent subports in a trunk and shall be absent otherwise. If this attribute is not present for a subport CP instance, default value VLAN shall be used.\n",
		"type": "string",
		"enum": [
		"VLAN",
		"INHERIT"
		]
		},
		"segmentationId": {
		"description": "Identification of the network segment to which the Cp instance connects to. If the Cp instance represents a subport in a trunk, segmentationId shall be present. Otherwise it shall not be present. Depending on the NFVI networking infrastructure, the segmentationId may indicate the actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header of the packets or it may be an identifier used between the application and the NFVI networking infrastructure to identify the network sub-interface of the trunk port in question. In the latter case the NFVI infrastructure will map this local segmentationId to whatever segmentationId is actually used by the NFVI’s transport technology.\n",
		"description": "Identification of the network segment to which the CP instance connects to. See note 3 and note 4.\n",
		"type": "string"
		},
		"ipAddresses": {
		"description": "List of IP addresses to assign to the CP instance. Each entry represents IP address data for fixed or dynamic IP address assignment per subnet. If this attribute is not present, no IP address shall be assigned.\n",
		"description": "List of IP addresses to assign to the CP instance. Each entry represents IP address data for fixed or dynamic IP address assignment per subnet. If this attribute is not present, no IP address shall be assigned. See note 1.\n",
		"type": "array",
		"items": {
		"type": "object",
		@@ -656,7 +713,7 @@
		]
		},
		"fixedAddresses": {
		"description": "Fixed addresses to assign (from the subnet defined by \"subnetId\" if provided). Exactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present.\n",
		"description": "Fixed addresses to assign (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
		"type": "array",
		"items": {
		"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
		@@ -665,11 +722,11 @@
		}
		},
		"numDynamicAddresses": {
		"description": "Number of dynamic addresses to assign (from the subnet defined by \"subnetId\" if provided). Exactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present.\n",
		"description": "Number of dynamic addresses to assign (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
		"type": "integer"
		},
		"addressRange": {
		"description": "An IP address range to be used, e.g. in case of egress connections. In case this attribute is present, IP addresses from the range will be used.\n",
		"description": "An IP address range to be used, e.g. in case of egress connections. In case this attribute is present, IP addresses from the range will be used. See note 2.\n",
		"type": "object",
		"required": [
		"minAddress",
		@@ -710,7 +767,7 @@
		}
		},
		"modificationsTriggeredByVnfPkgChange": {
		"description": "This type represents attribute modifications that were performed on an \"Individual VNF instance\" resource when changing the current VNF package. The attributes that can be included consist of those requested to be modified explicitly in the \"ChangeCurrentVnfPkgRequest\" data structure, and additional attributes of the \"VnfInstance\" data structure that were modified implicitly during the operation.\n",
		"description": "This type represents attribute modifications that were performed on an \"Individual VNF instance\" resource when changing the current VNF package. The attributes that can be included consist of those requested to be modified explicitly in the \"ChangeCurrentVnfPkgRequest\" data structure, and additional attributes of the \"VnfInstance\" data structure that were modified implicitly during the operation. The \"ModificationsTriggeredByVnfPkgChange\" data type shall comply with the provisions defined in table 5.5.3.21-1.\nNOTE 1:\tThis attribute represents the delta (semantics as per IETF RFC 7396, JSON Merge Patch) between the value \n of the attribute at the start of the \"Change current VNF package\" operation and the value of the attribute \n at its completion.\nNOTE 2:\tIf present, this attribute (which depends on the value of the \"vnfdId\" attribute) was modified implicitly \n during the related operation and contains a copy of the value of the related attribute from the VNFD in the \n VNF Package identified by the \"vnfdId\" attribute.\n",
		"type": "object",
		"properties": {
		"vnfConfigurableProperties": {
		@@ -730,11 +787,11 @@
		"type": "string"
		},
		"vnfProvider": {
		"description": "If present, this attribute signals the new value of the \"vnfProvider\" attribute in \"VnfInstance\". If present, this attribute (which depends on the value of the \"vnfdId\" attribute) was modified implicitly during the related operation, and contains a copy of the value of he related attribute from the VNFD in the VNF Package identified by the \"vnfdId\" attribute.\n",
		"description": "If present, this attribute signals the new value of the \"vnfProvider\" attribute in \"VnfInstance\". See note 2.\n",
		"type": "string"
		},
		"vnfProductName": {
		"description": "If present, this attribute signals the new value of the \"vnfProductName\" attribute in \"VnfInstance\". If present, this attribute (which depends on the value of the \"vnfdId\" attribute) was modified implicitly during the related operation, and contains a copy of the value of he related attribute from the VNFD in the VNF Package identified by the \"vnfdId\" attribute.\n",
		"description": "If present, this attribute signals the new value of the \"vnfProductName\" attribute in \"VnfInstance\". See note 2.\n",
		"type": "string"
		},
		"vnfSoftwareVersion": {
		@@ -748,7 +805,7 @@
		}
		},
		"error": {
		"description": "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 [19] is reproduced inthis structure. Compared to the general framework defined in IETF RFC 7807 [19], the \"status\" and \"detail\" attributes are mandated to be included by the present document, to ensure that the response contains additional textual information about an error. IETF RFC 7807 [19] foresees extensibility of the \"ProblemDetails\" type. It is possible that particular APIs in the present document, or particular implementations, define extensions to define additional attributes that provide more information about the error. The description column only provides some explanation of the meaning to Facilitate understanding of the design. For a full description, see IETF RFC 7807 [19].\n",
		"description": "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 is reproduced inthis structure. Compared to the general framework defined in IETF RFC 7807, the \"status\" and \"detail\" attributes are mandated to be included by the present document, to ensure that the response contains additional textual information about an error. IETF RFC 7807 foresees extensibility of the \"ProblemDetails\" type. It is possible that particular APIs in the present document, or particular implementations, define extensions to define additional attributes that provide more information about the error. The description column only provides some explanation of the meaning to Facilitate understanding of the design. For a full description, see IETF RFC 7807.\n",
		"type": "object",
		"required": [
		"status",
		@@ -756,7 +813,7 @@
		],
		"properties": {
		"type": {
		"description": "A URI reference according to IETF RFC 3986 [5] that identifies the problem type. It is encouraged that the URI provides human-readable documentation for the problem (e.g. using HTML) when dereferenced. When this member is not present, its value is assumed to be \"about:blank\".\n",
		"description": "A URI reference according to IETF RFC 3986 that identifies the problem type. It is encouraged that the URI provides human-readable documentation for the problem (e.g. using HTML) when dereferenced. When this member is not present, its value is assumed to be \"about:blank\".\n",
		"type": "string",
		"format": "URI"
		},

SOL002/VNFLifecycleManagement-API/schemas/VnfSnapshotInfo.schema.json

+266 −115

File changed.

Preview size limit exceeded, changes collapsed.

SOL002/VNFLifecycleManagement-API/schemas/VnfSnapshotsInfo.schema.json

+267 −117

File changed.

Preview size limit exceeded, changes collapsed.

SOL002/VNFLifecycleManagement-API/schemas/vnfInstance.schema.json

+272 −51

File changed.

Preview size limit exceeded, changes collapsed.

SOL002 VNF Lifecycle Management - Implementation of deltas between v3.5.1 and v3.3.1

Merge request reports