SOL005_56 to SOL005_86 (ded35a71) · Commits · NFV - Network Functions Virtualisation / SOL005

src/SOL005/NSLifecycleManagement/NSLifecycleManagement.yaml

+10 −10

Original line number	Original line	Diff line number	Diff line
	@@ -998,7 +998,7 @@ components:
	in: path		in: path
	description: \|		description: \|
	Identifier of the "Individual VNF snapshot" resource.		Identifier of the "Individual VNF snapshot" resource.
	This identifier can be retrieved from the "id" attribute in the payload body of a response to a query to		This identifier can be retrieved from the "id" attribute in the message content of a response to a query to
	"VNF snapshots" resource.		"VNF snapshots" resource.
	required: true		required: true
	style: simple		style: simple
	@@ -1063,7 +1063,7 @@ components:

	NsLcmOpOccCancelRequest:		NsLcmOpOccCancelRequest:
	description: \|		description: \|
	The POST request to this resource shall include a CancelMode structure in the payload body to choose between		The POST request to this resource shall include a CancelMode structure in the message content to choose between
	"graceful" and "forceful" cancellation.		"graceful" and "forceful" cancellation.
	content:		content:
	application/json:		application/json:
	@@ -1715,7 +1715,7 @@ components:
	202 ACCEPTED		202 ACCEPTED

	Shall be returned when the request has been accepted for processing, but processing has not been completed.		Shall be returned when the request has been accepted for processing, but processing has not been completed.
	The response shall have an empty payload body.		The response shall have an empty message content.
	headers:		headers:
	Version:		Version:
	description: \|		description: \|
	@@ -1828,7 +1828,7 @@ components:
	202 ACCEPTED		202 ACCEPTED

	Shall be returned when the request has been accepted for processing, but processing has not been completed.		Shall be returned when the request has been accepted for processing, but processing has not been completed.
	The response shall have an empty payload body.		The response shall have an empty message content.
	headers:		headers:
	Version:		Version:
	description: \|		description: \|
	@@ -1941,7 +1941,7 @@ components:
	202 ACCEPTED		202 ACCEPTED

	Shall be returned when the request has been accepted for processing, but processing has not been completed.		Shall be returned when the request has been accepted for processing, but processing has not been completed.
	The response shall have an empty payload body.		The response shall have an empty message content.

	headers:		headers:
	Version:		Version:
	@@ -2241,7 +2241,7 @@ components:

	Shall be returned upon the following error: The operation cannot be executed currently, due to a conflict		Shall be returned upon the following error: The operation cannot be executed currently, due to a conflict
	with the state of the NS LCM operation occurrence resource.		with the state of the NS LCM operation occurrence resource.
	Typically, this is due to the fact that the operation occurrence is not in STARTING, PROCESSING or ROLLING_BACK state.		Typically, this is due to the fact that the operation occurrence is not in PROCESSING or ROLLING_BACK state.
	The response body shall contain a ProblemDetails structure, in which the "detail" attribute shall convey more		The response body shall contain a ProblemDetails structure, in which the "detail" attribute shall convey more
	information about the error.		information about the error.
	headers:		headers:
	@@ -2383,10 +2383,10 @@ components:

	NsLcmSubscriptions.Post.422:		NsLcmSubscriptions.Post.422:
	description: \|		description: \|
	422 Unprocessable Entity		422 Unprocessable Content

	Shall be returned upon the following error: The content type of the payload body is supported and the		Shall be returned upon the following error: The content type of the message content is supported and the
	payload body of a request contains syntactically correct data but the data cannot be processed.		message content of a request contains syntactically correct data but the data cannot be processed.
	The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013 [16],		The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013 [16],
	including rules for the presence of the response body.		including rules for the presence of the response body.
	Specifically in case of this resource, the response code 422 shall also be returned if the NFVO has tested		Specifically in case of this resource, the response code 422 shall also be returned if the NFVO has tested

src/SOL005/NSLifecycleManagement/definitions/SOL005NSLifecycleManagement_def.yaml

+15 −14

Original line number	Original line	Diff line number	Diff line
	@@ -176,13 +176,15 @@ definitions:
	description: >		description: >
	Cancellation mode.		Cancellation mode.

	The NFVO shall not start any new VNF lifecycle management and resource		If the NS LCM operation occurrence is in "PROCESSING" or "ROLLING_BACK" state,
			the NFVO shall not start any new VNF lifecycle management and resource
	management operation, and shall wait for the ongoing VNF lifecycle management		management operation, and shall wait for the ongoing VNF lifecycle management
	and resource management operations in the underlying system, typically the VNFM		and resource management operations in the underlying system, typically the VNFM
	and VIM, to finish execution or to time out. After that, the NFVO shall put the		and VIM, to finish execution or to time out. After that, the NFVO shall put the
	operation occurrence into the FAILED_TEMP state.		operation occurrence into the FAILED_TEMP state.

	The NFVO shall not start any new VNF lifecycle management and resource		If the NS LCM operation occurrence is in "PROCESSING" or "ROLLING_BACK" state,
			the NFVO shall not start any new VNF lifecycle management and resource
	management operation, shall cancel the ongoing VNF lifecycle management and		management operation, shall cancel the ongoing VNF lifecycle management and
	resource management operations in the underlying system, typically the VNFM and		resource management operations in the underlying system, typically the VNFM and
	VIM, and shall wait for the cancellation to finish or to time out. After that, the NFVO		VIM, and shall wait for the cancellation to finish or to time out. After that, the NFVO
	@@ -197,7 +199,7 @@ definitions:
	This type represents a response for Query NS operation.		This type represents a response for Query NS operation.
	It shall comply with the provisions defined in Table 6.5.2.10-1.		It shall comply with the provisions defined in Table 6.5.2.10-1.

	NOTE 1: If the "nsState" attribute is INSTANTIATED, at least either one		NOTE 1: Void.
	"vnfInstance" attribute or one "nestedNsInstanceId" attribute shall be present.		"vnfInstance" attribute or one "nestedNsInstanceId" attribute shall be present.
	NOTE 2: The “priority” attribute of the NS instance is configured in the NSD in the NsDf structure.		NOTE 2: The “priority” attribute of the NS instance is configured in the NSD in the NsDf structure.
	The mapping from application-specific priority values to a value in the NsDf is under OSS/BSS responsibility.		The mapping from application-specific priority values to a value in the NsDf is under OSS/BSS responsibility.
	@@ -250,7 +252,6 @@ definitions:
	vnfInstance:		vnfInstance:
	description: >		description: >
	Information on constituent VNF(s) of the NS instance.		Information on constituent VNF(s) of the NS instance.
	See note 1.
	type: array		type: array
	items:		items:
	$ref: "#/definitions/VnfInstance"		$ref: "#/definitions/VnfInstance"
	@@ -284,7 +285,6 @@ definitions:
	nestedNsInstanceId:		nestedNsInstanceId:
	description: >		description: >
	Identifier of the nested NS(s) of the NS instance.		Identifier of the nested NS(s) of the NS instance.
	See note.
	type: array		type: array
	items:		items:
	$ref: "../../definitions/SOL005_def.yaml#/definitions/Identifier"		$ref: "../../definitions/SOL005_def.yaml#/definitions/Identifier"
	@@ -402,7 +402,7 @@ definitions:
	This type represents a VNF instance. It shall comply with the provisions defined in table 6.5.3.57-1.		This type represents a VNF instance. It shall comply with the provisions defined in table 6.5.3.57-1.

	NOTE: Clause B.3.2 of ETSI GS NFV-SOL 003 provides examples illustrating the relationship among the		NOTE: Clause B.3.2 of ETSI GS NFV-SOL 003 provides examples illustrating the relationship among the
	different run-time information elements (CP, VL and link ports) used to represent the connectivity		different run-time idata types (CP, VL and link ports) used to represent the connectivity
	of a VNF.		of a VNF.

	NOTE 1: Modifying the value of this attribute shall not be performed when conflicts exist between the		NOTE 1: Modifying the value of this attribute shall not be performed when conflicts exist between the
	@@ -1521,6 +1521,7 @@ definitions:
	$ref: "#/definitions/IdentifierInVim"		$ref: "#/definitions/IdentifierInVim"

	ExtManagedVirtualLinkInfo:		ExtManagedVirtualLinkInfo:
			description: This type provides information about an externally-managed internal virtual link for VNFs.
	type: object		type: object
	required:		required:
	- id		- id
	@@ -4344,13 +4345,13 @@ definitions:
	description: >		description: >
	Value \| Description		Value \| Description
	------\|------------		------\|------------
	PROCESSING \| The LCM operation is currently in execution.		PROCESSING \| The NS LCM operation is currently in execution.
	COMPLETED \| The LCM operation has been completed successfully.		COMPLETED \| The NS LCM operation has been completed successfully.
	PARTIALLY_COMPLETED \| The LCM operation has been partially completed with accepTable errors.		PARTIALLY_COMPLETED \| The NS LCM operation has been partially completed with accepTable errors.
	FAILED_TEMP \| The LCM operation has failed and execution has stopped, but the execution of the operation is not considered to be closed.		FAILED_TEMP \| The NS LCM operation has failed and execution has stopped, but the execution of the operation is not considered to be closed.
	FAILED \| The LCM operation has failed and it cannot be retried or rolled back, as it is determined that such action will not succeed.		FAILED \| The NS LCM operation has failed and it cannot be retried or rolled back, as it is determined that such action will not succeed.
	OLLING_BACK \| The LCM operation is currently being rolled back.		ROLLING_BACK \| The NS LCM operation is currently being rolled back.
	ROLLED_BACK \| The LCM operation has been successfully rolled back, i.e. The state of the NS prior to the original operation invocation has been restored as closely as possible.		ROLLED_BACK \| The NS LCM operation has been successfully rolled back, i.e. The state of the NS prior to the original operation invocation has been restored as closely as possible.
	type: string		type: string
	enum:		enum:
	- PROCESSING		- PROCESSING
	@@ -6635,7 +6636,7 @@ definitions:
	properties:		properties:
	cpInstanceId:		cpInstanceId:
	description: >		description: >
	Identifier of this VIP CP instance and of this VipCpInfo information element.		Identifier of this VIP CP instance and of this VipCpInfo structure.
	$ref: "#/definitions/IdentifierInVnf"		$ref: "#/definitions/IdentifierInVnf"
	cpdId:		cpdId:
	description: >		description: >

src/SOL005/NSPerformanceManagement/NSPerformanceManagement.yaml

+20 −20

Original line number	Original line	Diff line number	Diff line
	@@ -127,8 +127,8 @@ paths:
	#ETSI GS NFV-SOL 005 V2.4.1 location: 7.4.3		#ETSI GS NFV-SOL 005 V2.4.1 location: 7.4.3
	parameters:		parameters:
	- $ref: '#/components/parameters/PmJobId'		- $ref: '#/components/parameters/PmJobId'
	- $ref: ../components/SOL005_params.yaml#/components/parameters/Authorization		- $ref: '../components/SOL005_params.yaml#/components/parameters/Authorization'
	- $ref: ../components/SOL005_params.yaml#/components/parameters/Version		- $ref: '../components/SOL005_params.yaml#/components/parameters/Version'

	get:		get:
	description: \|		description: \|
	@@ -328,8 +328,8 @@ paths:
	#ETSI GS NFV-SOL 005 V2.4.1 location: 7.4.6		#ETSI GS NFV-SOL 005 V2.4.1 location: 7.4.6
	parameters:		parameters:
	- $ref: '#/components/parameters/ThresholdId'		- $ref: '#/components/parameters/ThresholdId'
	- $ref: ../components/SOL005_params.yaml#/components/parameters/Authorization		- $ref: '../components/SOL005_params.yaml#/components/parameters/Authorization'
	- $ref: ../components/SOL005_params.yaml#/components/parameters/Version		- $ref: '../components/SOL005_params.yaml#/components/parameters/Version'

	get:		get:
	description: \|		description: \|
	@@ -798,7 +798,7 @@ components:
	Identifier of the PM job.		Identifier of the PM job.
	This identifier can be retrieved from the resource referenced by the "Location" HTTP header in the response		This identifier can be retrieved from the resource referenced by the "Location" HTTP header in the response
	to a POST request creating a new PM job resource. It can also be retrieved from the "id" attribute in the		to a POST request creating a new PM job resource. It can also be retrieved from the "id" attribute in the
	payload body of that response.		message content of that response.
	required: true		required: true
	style: simple		style: simple
	explode: false		explode: false
	@@ -824,7 +824,7 @@ components:
	This identifier can be retrieved from the resource referenced by the		This identifier can be retrieved from the resource referenced by the
	"Location" HTTP header in the response to a POST request creating a		"Location" HTTP header in the response to a POST request creating a
	new threshold resource. It can also be retrieved from the "id"		new threshold resource. It can also be retrieved from the "id"
	attribute in the payload body of that response.		attribute in the message content of that response.
	required: true		required: true
	style: simple		style: simple
	explode: false		explode: false
	@@ -906,10 +906,10 @@ components:

	PmJobs.Post.422:		PmJobs.Post.422:
	description: \|		description: \|
	422 Unprocessable Entity		422 Unprocessable Content

	content type of the payload body is supported and the payload body of a request contains syntactically correct		Shall be returned upon the following error: The content type of the message content is supported and the
	data but the data cannot be processed.		message content of a request contains syntactically correct data but the data cannot be processed.
	The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013 [16],		The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013 [16],
	including rules for the presence of the response body.		including rules for the presence of the response body.
	Specifically in case of this resource, the response code 422 shall also be returned if the NFVO has tested		Specifically in case of this resource, the response code 422 shall also be returned if the NFVO has tested
	@@ -1090,10 +1090,10 @@ components:

	IndividualPmJob.Patch.422:		IndividualPmJob.Patch.422:
	description: \|		description: \|
	422 Unprocessable entity		422 Unprocessable Content

	Shall be returned upon the following error: The content type of the payload body is supported and the payload		Shall be returned upon the following error: The content type of the message content is supported and the
	body of a request contains syntactically correct data but the data cannot be processed.		message content of a request contains syntactically correct data but the data cannot be processed.
	The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013 [16],		The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013 [16],
	including rules for the presence of the response body.		including rules for the presence of the response body.
	Specifically in case of this resource, the response code 422 shall also be returned if the NFVO has tested		Specifically in case of this resource, the response code 422 shall also be returned if the NFVO has tested
	@@ -1222,11 +1222,11 @@ components:

	Thresholds.Post.422:		Thresholds.Post.422:
	description: \|		description: \|
	422 Unprocessable entity		422 Unprocessable Content

	Shall be returned upon the following error: The content type of the payload body is supported and the payload		Shall be returned upon the following error: The content type of the message content is supported and the
	body of a request contains syntactically correct data but the data cannot be processed.		message content of a request contains syntactically correct data but the data cannot be processed.
	The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013 [16],		The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013,
	including rules for the presence of the response body.		including rules for the presence of the response body.
	Specifically in case of this resource, the response code 422 shall also be returned if the NFVO has tested		Specifically in case of this resource, the response code 422 shall also be returned if the NFVO has tested
	the Notification endpoint as described in clause 7.4.9.3.2 and the test has failed.		the Notification endpoint as described in clause 7.4.9.3.2 and the test has failed.
	@@ -1403,11 +1403,11 @@ components:

	IndividualThreshold.Patch.422:		IndividualThreshold.Patch.422:
	description: \|		description: \|
	422 Unprocessable Entity		422 Unprocessable Content

	Shall be returned upon the following error: The content type of the payload body is supported and the payload		Shall be returned upon the following error: The content type of the message content is supported and the
	body of a request contains syntactically correct data but the data cannot be processed.		message content of a request contains syntactically correct data but the data cannot be processed.
	The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013 [16],		The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013,
	including rules for the presence of the response body.		including rules for the presence of the response body.
	Specifically in case of this resource, the response code 422 shall also be returned if the NFVO has tested		Specifically in case of this resource, the response code 422 shall also be returned if the NFVO has tested
	the Notification endpoint as described in clause 7.4.9.3.2 and the test has failed.		the Notification endpoint as described in clause 7.4.9.3.2 and the test has failed.

Admin message