From 7b9027042d60ac4cb344916fa73da687c9ceacc2 Mon Sep 17 00:00:00 2001 From: Samir Medjiah Date: Wed, 17 Jul 2019 08:17:14 +0200 Subject: [PATCH] SOL002_36 POST method (on Scale VNF task) response updated --- .../VNFLifecycleManagement/VNFLifecycleManagement.yaml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 158567ef..d5744923 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -674,10 +674,10 @@ paths: description: > 202 ACCEPTED - The request was accepted for processing, but the processing has not been completed. + The request has been accepted for processing, but the processing has not been completed. 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. + newly-created "Individual VNF LCM operation occurrence" resource corresponding to the operation. headers: Content-Type: description: The MIME type of the body of the response. @@ -724,7 +724,7 @@ paths: 409 CONFLICT 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 VNF instance resource is in NOT_INSTANTIATED state, + 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. The response body shall contain a ProblemDetails structure, in which the "detail" attribute shall convey more information about the error. -- GitLab