SOL003_39: Responses' codes updated according to SOL003 and SOL013

src/SOL003/VNFLifecycleManagement/VNFLifecycleManagement.yaml

@@ -465,7 +465,7 @@ 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:
@@ -531,7 +531,7 @@ 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:
@@ -607,8 +607,7 @@ paths:
           description: >
             202 ACCEPTED
 
-            The request was accepted for processing, but the  processing has
-            not been completed.
+            Shall be returned when the request has been accepted for processing
             The response body shall be empty.
             The HTTP response shall include a "Location" HTTP header that
             contains the URI of the newly-created "VNF LCM operation
@@ -643,7 +642,7 @@ 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:
@@ -682,9 +681,7 @@ paths:
     post:
       #SOL003 location: 5.4.5.3.1
       description: >
-        Scale VNF
-
-
+        Scale VNF.
         The POST method requests to scale a VNF instance resource
         incrementally.
       parameters:
@@ -723,7 +720,35 @@ paths:
           type: string
       responses:
         202:
-          $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/202-with-Location"
+          description: >
+            202 ACCEPTED
+
+            Shall be returned when the request has been accepted for processing.
+            The response body shall be empty.
+            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:
+            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
+            Version:
+              description: >
+                Version of the API used in the response.
+              type: string
+              maximum: 1
+              minimum: 1
         400:
           $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/400"
         401:
@@ -731,17 +756,35 @@ paths:
         403:
           $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/403"
         404:
+          description: >
+            Shall be returned upon the following error: The API producer did not find a current representation
+            for the target resource or is not willing to disclose that one exists.
+            The general cause for this error and its handling is specified in clause 4.3.5.4,6.4 of ETSI GS NFV-SOL 013,
+            including rules for the presence of the response body.
+            Specifically in case of this task resource, the response code 404 shall also returned if
+            the task is not supported for the VNF instance represented by the parent resource, which means that the
+            task resource consequently does not exist.
           $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-state-conflict-NOT-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
+            NOT_INSTANTIATED state, or that another lifecycle management operation is ongoing, or that
+            a required child attribute of the "extensions" attribute has not been set.
+            Those attributes are marked as "required" in the VNFD.
+          $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409"
         500:
           $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500"
         503:
           $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503"
+        504:
+          $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504"
+
   ###############################################################################
   # Scale VNF to Level task                                                     #
   ###############################################################################
@@ -761,9 +804,7 @@ paths:
     post:
       #SOL003 location: 5.4.6.3.1
       description: >
-        Scale VNF to Level
-
-
+        Scale VNF to Level.
         The POST method requests to scale a VNF instance resource to a target
         level.
       parameters: