Skip to content
GitLab
Projects
Groups
Snippets
/
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Sign in
Toggle navigation
Menu
Open sidebar
NFV - Network Functions Virtualisation
SOL002-SOL003
Commits
ce879fd0
Commit
ce879fd0
authored
Jun 26, 2019
by
moscatelli
Browse files
SOL003_74: responses description fixed
parent
367724c5
Pipeline
#1171
passed with stage
in 0 seconds
Changes
1
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
src/SOL003/VNFLifecycleManagement/VNFLifecycleManagement.yaml
View file @
ce879fd0
...
...
@@ -1873,7 +1873,7 @@ paths:
description
:
>
202 ACCEPTED
T
he request
w
as accepted for processing
, but processing has not been completed
.
Shall be returned when t
he request
h
as
been
accepted for processing.
The response shall have an empty payload body.
headers
:
WWW-Authenticate
:
...
...
@@ -1896,17 +1896,33 @@ 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 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 be returned if the task
is not supported for the VNF LCM operation occurrence 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/40
4
"
$ref
:
"
../../responses/SOL002SOL003_resp.yaml#/responses/40
5
"
406
:
$ref
:
"
../../responses/SOL002SOL003_resp.yaml#/responses/406"
409
:
$ref
:
"
responses/VNFLifecycleManagement_resp.yaml#/responses/409-state-conflict-not-FAILED_TEMP"
description
:
>
Shall be returned upon the following error: The operation cannot be executed currently,
due to a conflict with the state of the VNF LCM operation occurrence.
Typically, this is due to the fact that the VNF LCM operation occurrence is not in FAILED_TEMP state,
or another error handling action is starting, such as rollback or fail.
$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"
###############################################################################
# Fail operation task #
###############################################################################
...
...
Write
Preview
Supports
Markdown
0%
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment