SOL005: Common definitions file updated + NSD mgmt and NS Performance mgmt def files updated (efe5fa2f) · Commits · NFV - Network Functions Virtualisation / SOL005

src/SOL005/NSDManagement/NSDManagement.yaml

+11 −11

Original line number	Diff line number	Diff line
		@@ -406,9 +406,9 @@ paths:
		an already disabled individual NS descriptor resource, or the "nsdOnboardingState" is not ONBOARDED.
		The response body shall contain a ProblemDetails structure, in which the "detail" attribute shall convey
		more information about the error.
		$ref: "responses/SOL005NSDescriptorManagement_resp.yaml#/responses/409"
		$ref: "../responses/SOL005_resp.yaml#/responses/409"
		412:
		$ref: "responses/SOL005NSDescriptorManagement_resp.yaml#/responses/412"
		$ref: "../responses/SOL005_resp.yaml#/responses/412"
		500:
		$ref: "../responses/SOL005_resp.yaml#/responses/500"
		503:
		@@ -477,7 +477,7 @@ paths:
		NS descriptor resource (i.e. usageState = IN_USE).
		The response body shall contain a ProblemDetails structure, in which the "detail" attribute shall
		convey more information about the error.
		$ref: "responses/SOL005NSDescriptorManagement_resp.yaml#/responses/409"
		$ref: "../responses/SOL005_resp.yaml#/responses/409"
		500:
		$ref: "../responses/SOL005_resp.yaml#/responses/500"
		503:
		@@ -587,7 +587,7 @@ paths:
		The response body shall contain the requested part of the NSD file.
		The "Content-Range" HTTP header shall be provided according to IETF RFC 7233.
		The "Content-Type" HTTP header shall be set as defined above for the "200 OK" response.
		$ref: "responses/SOL005NSDescriptorManagement_resp.yaml#/responses/206"
		$ref: "../responses/SOL005_resp.yaml#/responses/206"
		400:
		$ref: "../responses/SOL005_resp.yaml#/responses/400"
		401:
		@@ -606,13 +606,13 @@ paths:
		Typically, this is due to the fact "nsdOnboardingState" has a value different from ONBOARDED.
		The response body shall contain a ProblemDetails structure, in which the "detail" attribute shall
		convey more information about the error.
		$ref: "responses/SOL005NSDescriptorManagement_resp.yaml#/responses/409"
		$ref: "../responses/SOL005_resp.yaml#/responses/409"
		416:
		description: >
		The byte range passed in the "Range" header did not match any available byte range in the NSD file
		(e.g. "access after end of file").
		The response body may contain a ProblemDetails structure.
		$ref: "responses/SOL005NSDescriptorManagement_resp.yaml#/responses/416"
		$ref: "../responses/SOL005_resp.yaml#/responses/416"
		500:
		$ref: "../responses/SOL005_resp.yaml#/responses/500"
		503:
		@@ -705,7 +705,7 @@ paths:
		Typically, this is due to the fact that the NsdOnboardingState has a value other than CREATED.
		The response body shall contain a ProblemDetails structure, in which the "detail" attribute shall
		convey more information about the error.
		$ref: "responses/SOL005NSDescriptorManagement_resp.yaml#/responses/409"
		$ref: "../responses/SOL005_resp.yaml#/responses/409"
		500:
		$ref: "../responses/SOL005_resp.yaml#/responses/500"
		503:
		@@ -1086,7 +1086,7 @@ paths:
		406:
		$ref: "../responses/SOL005_resp.yaml#/responses/406"
		412:
		$ref: "responses/SOL005NSDescriptorManagement_resp.yaml#/responses/412"
		$ref: "../responses/SOL005_resp.yaml#/responses/412"
		500:
		$ref: "../responses/SOL005_resp.yaml#/responses/500"
		503:
		@@ -1214,7 +1214,7 @@ paths:
		Typically, this is due to the fact pnfdOnboardingState has a value different from ONBOARDED.
		The response body shall contain a ProblemDetails structure, in which the "detail" attribute
		shall convey more information about the error.
		$ref: "responses/SOL005NSDescriptorManagement_resp.yaml#/responses/409"
		$ref: "../responses/SOL005_resp.yaml#/responses/409"
		500:
		$ref: "../responses/SOL005_resp.yaml#/responses/500"
		503:
		@@ -1261,7 +1261,7 @@ paths:
		Typically, this is due to the fact that the PnfdOnboardingState has a value other than CREATED.
		The response body shall contain a ProblemDetails structure, in which the "detail" attribute shall
		convey more information about the error.
		$ref: "responses/SOL005NSDescriptorManagement_resp.yaml#/responses/409"
		$ref: "../responses/SOL005_resp.yaml#/responses/409"
		500:
		$ref: "../responses/SOL005_resp.yaml#/responses/500"
		503:
		@@ -1368,7 +1368,7 @@ paths:
		The HTTP response shall include a "Location" HTTP header that contains the resource URI of the existing
		subscription resource.
		The response body shall be empty.
		$ref: "responses/SOL005NSDescriptorManagement_resp.yaml#/responses/303"
		$ref: "../responses/SOL005_resp.yaml#/responses/303"
		400:
		$ref: "../responses/SOL005_resp.yaml#/responses/400"
		401:

src/SOL005/NSDManagement/definitions/SOL005NSDescriptorManagement_def.yaml

+305 −403

File changed.

Preview size limit exceeded, changes collapsed.

src/SOL005/NSDManagement/definitions/SOL005_def.yaml

deleted100644 → 0

+0 −90

Original line number	Diff line number	Diff line
		# Copyright (c) ETSI 2017.
		# https://forge.etsi.org/etsi-forge-copyright-notice.txt
		definitions:
		Identifier:
		description: >
		An identifier with the intention of being globally unique.
		type: string
		KeyValuePairs:
		description: >
		This type represents a list of key-value pairs. The order of the pairs in the list is not significant.
		In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions
		defined in clause 4 of IETF RFC 7159.
		type: object
		String:
		description: >
		This type represents stack of string values
		type: string

		Version:
		description: >
		A Version.
		type: string

		Uri:
		description: >
		String formatted according to IETF RFC 3986.
		type: string
		DateTime:
		description: >
		Date-time stamp.
		Representation: String formatted according to IETF RFC 3339.
		type: string
		format: "date-time"
		ProblemDetails:
		#SOL005 location: 4.3.5.3-1
		description: >
		The definition of the general "ProblemDetails" data structure from
		IETF RFC 7807 [19] is reproduced in this 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].
		type: object
		required:
		- statussss
		- detail
		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".
		type: string
		format: URI
		title:
		description: >
		A short, human-readable summary of the problem type. It should not
		change from occurrence to occurrence of the problem, except for
		purposes of localization. If type is given and other than
		"about:blank", this attribute shall also be provided.
		A short, human-readable summary of the problem
		type. It SHOULD NOT change from occurrence to occurrence of the
		problem, except for purposes of localization (e.g., using
		proactive content negotiation; see [RFC7231], Section 3.4).
		type: string
		status:
		description: >
		The HTTP status code for this occurrence of the problem.
		The HTTP status code ([RFC7231], Section 6) generated by the origin
		server for this occurrence of the problem.
		type: integer
		detail:
		description: >
		A human-readable explanation specific to this occurrence of the
		problem.
		type: string
		instance:
		description: >
		A URI reference that identifies the specific occurrence of the
		problem. It may yield further information if dereferenced.
		type: string
		format: URI
		No newline at end of file

src/SOL005/NSDManagement/responses/SOL005NSDescriptorManagement_resp.yaml

deleted100644 → 0

+0 −142

Original line number	Diff line number	Diff line
		# Copyright (c) ETSI 2017.
		# https://forge.etsi.org/etsi-forge-copyright-notice.txt
		responses:
		206:
		description: >
		206 PARTIAL CONTENT
		headers:
		Content-Type:
		description: >
		The MIME type of the body of the response.
		type: string
		maximum: 1
		minimum: 1
		Content-Range:
		description: >
		The Content-Range response HTTP header indicates where in a full body message a partial message belongs.
		type: string
		maximum: 1
		minimum: 1
		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.
		type: string
		maximum: 1
		minimum: 0
		Version:
		description: >
		Version of the API used in the response.
		type: string
		maximum: 1
		minimum: 1
		schema:
		$ref: "../../definitions/SOL005_def.yaml#/definitions/ProblemDetails"

		303:
		description: >
		303 SEE OTHER
		headers:
		Content-Type:
		description: The MIME type of the body of the response.
		type: string
		maximum: 1
		minimum: 1
		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.
		type: string
		maximum: 1
		minimum: 0
		Version:
		description: >
		Version of the API used in the response.
		type: string
		maximum: 1
		minimum: 1

		409:
		description: >
		409 CONFLICT
		headers:
		Content-Type:
		description: The MIME type of the body of the response.
		type: string
		maximum: 1
		minimum: 1
		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.
		type: string
		maximum: 1
		minimum: 0
		Version:
		description: >
		Version of the API used in the response.
		type: string
		maximum: 1
		minimum: 1
		schema:
		$ref: "../../definitions/SOL005_def.yaml#/definitions/ProblemDetails"

		412:
		description: >
		412 PRECONDITION FAILED

		Error: 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:
		Content-Type:
		description: The MIME type of the body of the response.
		type: string
		maximum: 1
		minimum: 1
		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.
		type: string
		maximum: 1
		minimum: 0
		Version:
		description: >
		Version of the API used in the response.
		type: string
		maximum: 1
		minimum: 1
		schema:
		$ref: "../../definitions/SOL005_def.yaml#/definitions/ProblemDetails"

		416:
		description: >
		416 RANGE NOT SATISFIABLE
		headers:
		Content-Type:
		description: The MIME type of the body of the response.
		type: string
		maximum: 1
		minimum: 1
		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.
		type: string
		maximum: 1
		minimum: 0
		Version:
		description: >
		Version of the API used in the response.
		type: string
		maximum: 1
		minimum: 1
		schema:
		$ref: "../../definitions/SOL005_def.yaml#/definitions/ProblemDetails"
		No newline at end of file

src/SOL005/NSDManagement/responses/SOL005_resp.yaml

deleted100644 → 0

+0 −418

File deleted.

Preview size limit exceeded, changes collapsed.