Commit 36dda968 authored by moscatelli's avatar moscatelli
Browse files

SOL003_31/SOL003_33/SOL003_34: Responses' codes updated according to SOL003 and SOL013

parent a9e90dfd

src/SOL003/VNFLifecycleManagement/VNFLifecycleManagement.yaml

+49 −15
Original line number Diff line number Diff line
@@ -338,7 +338,7 @@ paths: 
      responses:

        200:

          description: >

            OK

            200 OK



            Information about zero or more VNF instances was queried

            successfully. The response body shall contain
@@ -374,23 +374,21 @@ 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"

        416:

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

        500:

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

        503:

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

        504:

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

    patch:

      #SOL003 location: 5.4.3.3.4

      description: >

        Modify VNF Information





        Modify VNF Information.

        This method modifies an individual VNF instance resource. Changes to

        the VNF configurable properties are applied to the configuration in

        the VNF instance, and are reflected in the representation of this
@@ -428,7 +426,36 @@ paths: 
          type: string

      responses:

        202:

          $ref: "responses/VNFLifecycleManagement_resp.yaml#/responses/202-with-Location-empty"

          description: >

            202 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

              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

          schema:

            $ref: "../../definitions/SOL002SOL003VNFLifecycleManagement_def.yaml#/definitions/VnfInstance"

        400:

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

        401:
@@ -442,7 +469,11 @@ paths: 
        406:

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

        409:

          $ref: "responses/VNFLifecycleManagement_resp.yaml#/responses/409-another-lcm-operation-ongoing"

          description: >

            Shall be returned upon the following error: The operation cannot be executed currently,

            due to a conflict with the state of the "Individual VNF instance" resource.

            Typically, this is due to the fact that another LCM operation is ongoing.

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

        412:

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

        500:
@@ -452,9 +483,7 @@ paths: 
    delete:

      #SOL003 location: 5.4.3.3.5

      description: >

        Delete VNF Identifier





        Delete VNF Identifier.

        This method deletes an individual VNF instance resource.

      parameters:

        - name: Authorization
@@ -473,7 +502,7 @@ paths: 
      responses:

        204:

          description: >

            No Content

            204 NO CONTENT



            The VNF instance resource and the associated VNF identifier were

            deleted successfully.
@@ -506,13 +535,18 @@ paths: 
        406:

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

        409:

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

          description: >

            Shall be returned upon the following error: The operation cannot be executed currently,

            due to a conflict with the state of the resource.

            Typically, this is due to the fact that the "Individual VNF instance" resource is in INSTANTIATED state.

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

        412:

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

        500:

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

        503:

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

          

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

  # Instantiate VNF task                                                        #

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