Commit c4705b0f authored by moscatelli's avatar moscatelli
Browse files

SOL003_61: 202 response description fixes

parent 5b535633
Pipeline #1168 passed with stage
in 0 seconds
...@@ -1506,9 +1506,7 @@ paths: ...@@ -1506,9 +1506,7 @@ paths:
#SOL003 location: 5.4.12 #SOL003 location: 5.4.12
get: get:
description: > description: >
Get Operation Status Get Operation Status.
The client can use this method to query status information about The client can use this method to query status information about
multiple VNF lifecycle management operation occurrences. multiple VNF lifecycle management operation occurrences.
parameters: parameters:
...@@ -1592,14 +1590,17 @@ paths: ...@@ -1592,14 +1590,17 @@ paths:
description: > description: >
200 OK 200 OK
Status information for zero or more VNF lifecycle management Shall be returned when status information for zero or more VNF lifecycle management
operation occurrences was queried successfully. The response body operation occurrences has been queried successfully.
shall contain in an array the status information about zero or The response body shall contain in an array the status information about zero or more
more VNF lifecycle operation occurrences. VNF lifecycle operation occurrences, as defined in clause 5.5.2.13.
If the VNFM supports alternative 2 (paging) according to If the "filter" URI parameter or one of the "all_fields", "fields" (if supported),
clause 4.7.2.1 for this resource, inclusion of the Link "exclude_fields" (if supported) or "exclude_default" URI parameters was supplied in the request,
HTTP header in this response shall follow the provisions the data in the response body shall have been transformed according to the rules specified
in clause 4.7.2.3. in clauses 5.2.2 and 5.3.2 of ETSI GS NFV-SOL 013, respectively.
If the VNFM supports alternative 2 (paging) according to clause 5.4.2.1 of ETSI GS NFV-SOL 013
for this resource, inclusion of the Link HTTP header in this response shall follow the provisions
in clause 5.4.2.3 of ETSI GS NFV-SOL 013.
headers: headers:
Content-Type: Content-Type:
description: The MIME type of the body of the response. description: The MIME type of the body of the response.
...@@ -1637,15 +1638,16 @@ paths: ...@@ -1637,15 +1638,16 @@ paths:
404: 404:
$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/404" $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/404"
405: 405:
$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/404" $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405"
406: 406:
$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406"
409:
$ref: "responses/VNFLifecycleManagement_resp.yaml#/responses/409-inconsistent-state"
500: 500:
$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500" $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500"
503: 503:
$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503"
504:
$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504"
############################################################################### ###############################################################################
# Individual VNF LCM operation occurrence # # Individual VNF LCM operation occurrence #
############################################################################### ###############################################################################
...@@ -1665,9 +1667,7 @@ paths: ...@@ -1665,9 +1667,7 @@ paths:
type: string type: string
get: get:
description: > description: >
Get Operation Status Get Operation Status.
The client can use this method to retrieve status information about a The client can use this method to retrieve status information about a
VNF lifecycle management operation occurrence by reading an individual VNF lifecycle management operation occurrence by reading an individual
"VNF LCM operation occurrence" resource. "VNF LCM operation occurrence" resource.
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment