Commit c4705b0f authored by moscatelli's avatar moscatelli
Browse files

SOL003_61: 202 response description fixes

parent 5b535633

src/SOL003/VNFLifecycleManagement/VNFLifecycleManagement.yaml

+17 −17
Original line number Diff line number Diff line
@@ -1506,9 +1506,7 @@ paths: 
    #SOL003 location: 5.4.12

    get:

      description: >

        Get Operation Status





        Get Operation Status.

        The client can use this method to query status information about

        multiple VNF lifecycle management operation occurrences.

      parameters:
@@ -1592,14 +1590,17 @@ paths: 
          description: >

            200 OK



            Status information for zero or more VNF lifecycle management

            operation occurrences was queried successfully. The response body

            shall contain in an array the status information about zero or 

            more VNF lifecycle operation occurrences.

            If the VNFM supports alternative 2 (paging) according to 

            clause 4.7.2.1 for this resource, inclusion of the Link 

            HTTP header in this response shall follow the provisions 

            in clause 4.7.2.3.

            Shall be returned when status information for zero or more VNF lifecycle management

            operation occurrences has been queried successfully.

            The response body shall contain in an array the status information about zero or more

            VNF lifecycle operation occurrences, as defined in clause 5.5.2.13.

            If the "filter" URI parameter or one of the "all_fields", "fields" (if supported),

            "exclude_fields" (if supported) or "exclude_default" URI parameters was supplied in the request,

            the data in the response body shall have been transformed according to the rules specified

            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:

            Content-Type:

              description: The MIME type of the body of the response.
@@ -1637,15 +1638,16 @@ paths: 
        404:

          $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/404"

        405:

          $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/404"

          $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405"

        406:

          $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406"

        409:

          $ref: "responses/VNFLifecycleManagement_resp.yaml#/responses/409-inconsistent-state"

        500:

          $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500"

        503:

          $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503"

        504:

          $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504"



  ###############################################################################

  # Individual VNF LCM operation occurrence                                     #

  ###############################################################################
@@ -1665,9 +1667,7 @@ paths: 
        type: string

    get:

      description: >

        Get Operation Status





        Get Operation Status.

        The client can use this method to retrieve status information about a

        VNF lifecycle management operation occurrence by reading an individual

        "VNF LCM operation occurrence" resource.