addressed comments from SOL WG (f7a91d5b) · Commits · NFV - Network Functions Virtualisation / SOL005

src/SOL005/NFVICapacityInformation/NFVICapacityInformation.yaml

+110 −3

Original line number	Diff line number	Diff line
		@@ -157,7 +157,7 @@ paths:
		"406":
		$ref: ../responses/SOL005_resp.yaml#/components/responses/406
		"422":
		$ref: ../responses/SOL005_resp.yaml#/components/responses/422
		$ref: '#/components/responses/CapacityThresholds.Post.422'
		"500":
		$ref: ../responses/SOL005_resp.yaml#/components/responses/500
		"503":
		@@ -218,9 +218,9 @@ paths:
		"406":
		$ref: ../responses/SOL005_resp.yaml#/components/responses/406
		"412":
		$ref: ../responses/SOL005_resp.yaml#/components/responses/412
		$ref: '#/components/responses/IndividualCapacityThreshold.Patch.412'
		"422":
		$ref: ../responses/SOL005_resp.yaml#/components/responses/422
		$ref: '#/components/responses/IndividualCapacityThreshold.Patch.422'
		"500":
		$ref: ../responses/SOL005_resp.yaml#/components/responses/500
		"503":
		@@ -442,6 +442,44 @@ components:
		schema:
		$ref: ./definitions/NFVICapacityInformation_def.yaml#/components/schemas/CapacityThreshold

		CapacityThresholds.Post.422:
		description: \|
		422 UNPROCESSABLE ENTITY

		Shall be returned upon the following error: The content type of the payload body is supported and the payload
		body 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],
		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
		the Notification endpoint as described in clause 10.4.6.3.2 and the test has failed.
		In this case, the "detail" attribute in the "ProblemDetails" structure shall convey more information about the error.
		headers:
		Version:
		description: \|
		Version of the API used in the response.
		style: simple
		explode: false
		schema:
		type: string
		WWW-Authenticate:
		description: \|
		Challenge if the corresponding HTTP request has not provided authorization, or error details if the
		corresponding HTTP request has provided an invalid authorization token.
		style: simple
		explode: false
		schema:
		type: string
		Content-Type:
		description: The MIME type of the body of the response.
		style: simple
		explode: false
		schema:
		type: string
		content:
		application/json:
		schema:
		$ref: $ref: "../definitions/SOL005_def.yaml#/definitions/ProblemDetails"

		IndividualCapacityThreshold.Get.200:
		description: \|
		Shall be returned when information about an individual capacity threshold has been read successfully.
		@@ -505,6 +543,75 @@ components:
		schema:
		$ref: ./definitions/NFVICapacityInformation_def.yaml#/components/schemas/CapacityThresholdModifications

		IndividualCapacityThreshold.Patch.412:
		description: \|
		412 PRECONDITION FAILED

		A precondition given in an HTTP request header is not fulfilled.
		Typically, this is due to an ETag mismatch, indicating that the resource was modified by another entity.
		The response body should contain a ProblemDetails structure, in which the "detail" attribute should convey
		more information about the error
		headers:
		Version:
		description: \|
		Version of the API used in the response.
		style: simple
		explode: false
		schema:
		type: string
		WWW-Authenticate:
		description: \|
		Challenge if the corresponding HTTP request has not provided authorization, or error details if the
		corresponding HTTP request has provided an invalid authorization token.
		style: simple
		explode: false
		schema:
		type: string
		Content-Type:
		description: The MIME type of the body of the response.
		style: simple
		explode: false
		schema:
		type: string

		IndividualCapacityThreshold.Patch.422:
		description: \|
		422 UNPROCESSABLE ENTITY

		content type of the payload body is supported and the payload body 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],
		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
		the Notification endpoint as described in clause 10.4.6.3.2 and the test has failed.
		In this case, the "detail" attribute in the "ProblemDetails" structure shall convey more information about the error.
		headers:
		Version:
		description: \|
		Version of the API used in the response.
		style: simple
		explode: false
		schema:
		type: string
		WWW-Authenticate:
		description: \|
		Challenge if the corresponding HTTP request has not provided authorization, or error details if the
		corresponding HTTP request has provided an invalid authorization token.
		style: simple
		explode: false
		schema:
		type: string
		Content-Type:
		description: The MIME type of the body of the response.
		style: simple
		explode: false
		schema:
		type: string
		content:
		application/json:
		schema:
		$ref: $ref: "../definitions/SOL005_def.yaml#/definitions/ProblemDetails"

		IndividualCapacityThreshold.Delete.204:
		description: \|
		Shall be returned when the NFVI capacity threshold has been deleted successfully.