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
923e8cb9
Commit
923e8cb9
authored
Aug 21, 2019
by
Giacomo Bernini
Browse files
more fixes for Jenkins build
parent
efd773ec
Pipeline
#1359
passed with stage
in 0 seconds
Changes
1
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
src/SOL003/VNFPackageManagement/VNFPackageManagement.yaml
View file @
923e8cb9
...
...
@@ -1155,154 +1155,154 @@ paths:
in
:
path
type
:
string
required
:
true
get
:
description
:
>
Fetch VNF Package Artifacts.
The GET method fetches the content of an artifact within a VNF package.
This method shall follow the provisions specified in the tables
10.4.6.3.2-1 and 10.4.6.3.2-2 for URI query parameters, request
and response data structures, and response codes.
parameters
:
-
name
:
Accept
description
:
>
Content-Types that are acceptable for the response.
in
:
header
required
:
true
type
:
string
-
name
:
Authorization
description
:
>
The authorization token for the request.
Reference: IETF RFC 7235
in
:
header
required
:
false
type
:
string
-
name
:
Range
description
:
>
The request may contain a "Range" HTTP header to obtain single
range of bytes from the VNF package file. This can be used to
continue an aborted transmission.
If the NFVO does not support range requests, it should return the
whole file with a 200 OK response instead.
in
:
header
type
:
string
-
name
:
Version
description
:
>
Version of the API requested to use when responding to this request.
in
:
header
required
:
true
type
:
string
responses
:
200
:
description
:
>
200 OK
get
:
description
:
>
Fetch VNF Package Artifacts.
The GET method fetches the content of an artifact within a VNF package.
This method shall follow the provisions specified in the tables
10.4.6.3.2-1 and 10.4.6.3.2-2 for URI query parameters, request
and response data structures, and response codes.
parameters
:
-
name
:
Accept
description
:
>
Content-Types that are acceptable for the response.
in
:
header
required
:
true
type
:
string
-
name
:
Authorization
description
:
>
The authorization token for the request.
Reference: IETF RFC 7235
in
:
header
required
:
false
type
:
string
-
name
:
Range
description
:
>
The request may contain a "Range" HTTP header to obtain single
range of bytes from the VNF package file. This can be used to
continue an aborted transmission.
If the NFVO does not support range requests, it should return the
whole file with a 200 OK response instead.
in
:
header
type
:
string
-
name
:
Version
description
:
>
Version of the API requested to use when responding to this request.
in
:
header
required
:
true
type
:
string
responses
:
200
:
description
:
>
200 OK
Shall be returned when the whole content of the artifact file has been read successfully.
The payload body shall contain a copy of the artifact file from the VNF package,
as defined by ETSI GS NFV-SOL 004.
The "Content-Type" HTTP header shall be set according to the content type of the artifact file.
If the content type cannot be determined, the header shall be set to the value "application/octet-stream".
headers
:
Content-Type
:
description
:
>
The MIME type of the body of the response.
The "Content-Type" HTTP header shall be set according to the
content type of the artifact file. If the content type cannot
be determined, the header shall be set to the value
"application/octet-stream".
type
:
string
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
206
:
description
:
>
206 PARTIAL CONTENT
Shall be returned when the whole content of the artifact file has been read successfully.
The payload body shall contain a copy of the artifact file from the VNF package,
as defined by ETSI GS NFV-SOL 004.
The "Content-Type" HTTP header shall be set according to the content type of the artifact file.
If the content type cannot be determined, the header shall be set to the value "application/octet-stream".
headers
:
Content-Type
:
description
:
>
The MIME type of the body of the response.
The "Content-Type" HTTP header shall be set according to the
content type of the artifact file. If the content type cannot
be determined, the header shall be set to the value
"application/octet-stream".
type
:
string
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
206
:
description
:
>
206 PARTIAL CONTENT
If the NFVO supports range requests, this response shall be returned
when a single consecutive byte range from the content of the artifact
file, if the NFVO supports range requests has been read successfully
according to the request.
The response body shall contain the requested part of the VNF
package file.
The "Content-Range" HTTP header shall be provided according to
IETF RFC 7233.
The "Content-Type" HTTP header shall be set as defined above for
the "200 OK" response.
headers
:
Content-Range
:
type
:
string
maximum
:
1
minimum
:
1
Content-Type
:
description
:
The MIME type of the body of the response.
type
:
string
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
:
$ref
:
"
../../responses/SOL002SOL003_resp.yaml#/responses/401"
403
:
$ref
:
"
../../responses/SOL002SOL003_resp.yaml#/responses/403"
404
:
$ref
:
"
../../responses/SOL002SOL003_resp.yaml#/responses/404"
405
:
$ref
:
"
../../responses/SOL002SOL003_resp.yaml#/responses/405"
406
:
$ref
:
"
../../responses/SOL002SOL003_resp.yaml#/responses/406"
409
:
description
:
>
409 CONFLICT
If the NFVO supports range requests, this response shall be returned
when a single consecutive byte range from the content of the artifact
file, if the NFVO supports range requests has been read successfully
according to the request.
The response body shall contain the requested part of the VNF
package file.
The "Content-Range" HTTP header shall be provided according to
IETF RFC 7233.
The "Content-Type" HTTP header shall be set as defined above for
the "200 OK" response.
headers
:
Content-Range
:
type
:
string
maximum
:
1
minimum
:
1
Content-Type
:
description
:
The MIME type of the body of the response.
type
:
string
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
:
$ref
:
"
../../responses/SOL002SOL003_resp.yaml#/responses/401"
403
:
$ref
:
"
../../responses/SOL002SOL003_resp.yaml#/responses/403"
404
:
$ref
:
"
../../responses/SOL002SOL003_resp.yaml#/responses/404"
405
:
$ref
:
"
../../responses/SOL002SOL003_resp.yaml#/responses/405"
406
:
$ref
:
"
../../responses/SOL002SOL003_resp.yaml#/responses/406"
409
:
description
:
>
409 CONFLICT
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 "onboardingState" of the
VNF package has a value different from "ONBOARDED".
The response body shall contain a ProblemDetails structure,
in which the "detail" attribute shall convey more information
about the error.
$ref
:
"
../../responses/SOL002SOL003_resp.yaml#/responses/409"
416
:
description
:
>
416 RANGE NOT SATISFIABLE
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 "onboardingState" of the
VNF package has a value different from "ONBOARDED".
The response body shall contain a ProblemDetails structure,
in which the "detail" attribute shall convey more information
about the error.
$ref
:
"
../../responses/SOL002SOL003_resp.yaml#/responses/409"
416
:
description
:
>
416 RANGE NOT SATISFIABLE
Shall be returned upon the following error: The byte range passed in the
"Range" header did not match any available byte range in the artifact file
(e.g. "access after end of file").
The response body may contain a ProblemDetails structure.
$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"
Shall be returned upon the following error: The byte range passed in the
"Range" header did not match any available byte range in the artifact file
(e.g. "access after end of file").
The response body may contain a ProblemDetails structure.
$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"
###############################################################################
# Subscriptions #
...
...
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