SOL002: VNF Lifecycle mgmt interface consolidated + error codes fixed (23383090) · Commits · NFV - Network Functions Virtualisation / SOL002-SOL003

src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml

+2 −2

Original line number	Diff line number	Diff line
		@@ -161,7 +161,7 @@ paths:
		schema:
		$ref: "./definitions/VNFFaultManagement_def.yaml#/definitions/Alarm"
		400:
		$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/400-attr-based-filtering-error"
		$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/400"
		401:
		$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/401"
		403:
		@@ -605,7 +605,7 @@ paths:
		schema:
		$ref: "../../definitions/SOL002SOL003VNFFaultManagement_def.yaml#/definitions/FmSubscription"
		400:
		$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/400-attr-based-filtering-error"
		$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/400"
		401:
		$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/401"
		403:

src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml

+926 −212

File changed.

Preview size limit exceeded, changes collapsed.

src/SOL002/VNFLifecycleManagement/responses/VNFLifecycleManagement_resp.yaml

deleted100644 → 0

+0 −190

Original line number	Diff line number	Diff line
		# Copyright (c) ETSI 2017.
		# https://forge.etsi.org/etsi-forge-copyright-notice.txt

		responses:
		202-with-Location:
		description: >
		Accepted

		The request was accepted for processing, but the processing has not
		been completed. On success, the HTTP response shall include a
		"Location" HTTP header that contains the URI of the newly-created
		"VNF LCM operation occurrence" resource corresponding to the
		operation.
		headers:
		Content-Type:
		description: The MIME type of the body of the response.
		type: string
		maximum: 1
		minimum: 1
		Location:
		description: The resource URI of the created VNF instance
		type: string
		format: url
		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: The used API version.
		type: string
		maximum: 1
		minimum: 1
		schema:
		$ref: "../definitions/VNFLifecycleManagement_def.yaml#/definitions/VnfInstance"
		409-another-lcm-operation-ongoing:
		description: >
		Conflict

		The operation cannot be executed currently, due to a conflict with the
		state of the VNF instance resource.
		Typically, this is due to the fact that another LCM operation is
		ongoing.
		The response body shall 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: The used API version.
		type: string
		maximum: 1
		minimum: 1
		schema:
		$ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/ProblemDetails"
		409-inconsistent-state:
		description: >
		Conflict

		Another request is in progress that prohibits the fulfilment of
		the current request, or the current resource state is inconsistent
		with the request.
		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: The used API version.
		type: string
		maximum: 1
		minimum: 1
		schema:
		$ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/ProblemDetails"
		409-state-conflict-INSTANTIATED:
		description: >
		Conflict

		The operation cannot be executed currently, due to a conflict with the
		state of the VNF instance resource.
		Typically, this is due to the fact that the VNF instance resource is in
		INSTANTIATED state.
		The response body shall 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: The used API version.
		type: string
		maximum: 1
		minimum: 1
		schema:
		$ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/ProblemDetails"
		409-state-conflict-not-FAILED_TEMP:
		description: >
		The operation cannot be executed currently, due to a conflict with the
		state of the VNF instance resource.
		Typically, this is due to the fact that the VNF instance resource is
		not in FAILED_TEMP state, or another error handling action is starting,
		such as rollback or fail.
		The response body shall 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: The used API version.
		type: string
		maximum: 1
		minimum: 1
		schema:
		$ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/ProblemDetails"
		409-state-conflict-NOT-INSTANTIATED:
		description: >
		Conflict

		The operation cannot be executed currently, due to a conflict with the
		state of the VNF instance resource.
		Typically, this is due to the fact that the VNF instance resource is in
		NOT-INSTANTIATED state, or that another lifecycle management operation
		is ongoing.
		The response body shall 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: The used API version.
		type: string
		maximum: 1
		minimum: 1
		schema:
		$ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/ProblemDetails"

src/SOL002/VNFLifecycleManagementNotification/VNFLifecycleManagementNotification.yaml

+3 −3

Original line number	Diff line number	Diff line
		@@ -104,7 +104,7 @@ paths:
		403:
		$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/403"
		404:
		$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/404-task-not-suported-VNF-LCM"
		$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/404"
		405:
		$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405"
		406:
		@@ -180,7 +180,7 @@ paths:
		403:
		$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/403"
		404:
		$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/404-task-not-suported-VNF-LCM"
		$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/404"
		405:
		$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405"
		406:
		@@ -256,7 +256,7 @@ paths:
		403:
		$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/403"
		404:
		$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/404-task-not-suported-VNF-LCM"
		$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/404"
		405:
		$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405"
		406:

src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml

+3 −3

Original line number	Diff line number	Diff line
		@@ -270,7 +270,7 @@ paths:
		items:
		$ref: "../../definitions/SOL002SOL003VNFPerformanceManagement_def.yaml#/definitions/PmJob"
		400:
		$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/400-attr-based-filtering-error"
		$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/400"
		401:
		$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/401"
		403:
		@@ -695,7 +695,7 @@ paths:
		items:
		$ref: "../../definitions/SOL002SOL003VNFPerformanceManagement_def.yaml#/definitions/Threshold"
		400:
		$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/400-attr-based-filtering-error"
		$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/400"
		401:
		$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/401"
		403:
		@@ -1038,7 +1038,7 @@ paths:
		items:
		$ref: "../../definitions/SOL002SOL003VNFPerformanceManagement_def.yaml#/definitions/PmSubscription"
		400:
		$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/400-attr-based-filtering-error"
		$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/400"
		401:
		$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/401"
		403:

Admin message