Loading src/SOL005/NSLifecycleManagement/NSLifecycleManagement.yaml +8 −8 Original line number Diff line number Diff line Loading @@ -1074,7 +1074,7 @@ components: in: path description: | 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. required: true style: simple Loading Loading @@ -1800,7 +1800,7 @@ components: 202 ACCEPTED 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: Version: description: | Loading Loading @@ -1913,7 +1913,7 @@ components: 202 ACCEPTED 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: Version: description: | Loading Loading @@ -2026,7 +2026,7 @@ components: 202 ACCEPTED 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: Version: Loading Loading @@ -2326,7 +2326,7 @@ components: 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. 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 information about the error. headers: Loading Loading @@ -2468,10 +2468,10 @@ components: NsLcmSubscriptions.Post.422: 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 body of a request contains syntactically correct data but the data cannot be processed. Shall be returned upon the following error: The content type of the message content is supported and the 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], 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 Loading src/SOL005/NSLifecycleManagement/definitions/SOL005NSLifecycleManagement_def.yaml +260 −171 File changed.Preview size limit exceeded, changes collapsed. Show changes Loading
src/SOL005/NSLifecycleManagement/NSLifecycleManagement.yaml +8 −8 Original line number Diff line number Diff line Loading @@ -1074,7 +1074,7 @@ components: in: path description: | 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. required: true style: simple Loading Loading @@ -1800,7 +1800,7 @@ components: 202 ACCEPTED 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: Version: description: | Loading Loading @@ -1913,7 +1913,7 @@ components: 202 ACCEPTED 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: Version: description: | Loading Loading @@ -2026,7 +2026,7 @@ components: 202 ACCEPTED 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: Version: Loading Loading @@ -2326,7 +2326,7 @@ components: 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. 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 information about the error. headers: Loading Loading @@ -2468,10 +2468,10 @@ components: NsLcmSubscriptions.Post.422: 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 body of a request contains syntactically correct data but the data cannot be processed. Shall be returned upon the following error: The content type of the message content is supported and the 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], 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 Loading
src/SOL005/NSLifecycleManagement/definitions/SOL005NSLifecycleManagement_def.yaml +260 −171 File changed.Preview size limit exceeded, changes collapsed. Show changes
