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
9d6ca422
Commit
9d6ca422
authored
Nov 01, 2022
by
Ayesha Ayub
Browse files
update descriptions in SOL003
parent
992f0d8c
Pipeline
#13221
passed with stage
in 0 seconds
Changes
2
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
src/SOL003/VNFPackageManagement/VNFPackageManagement.yaml
View file @
9d6ca422
...
...
@@ -2014,7 +2014,7 @@ components:
a single consecutive byte range from the content of the VNF package file
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-Range" HTTP header shall be provided according to IETF RFC
9110
.
The "Content-Type" HTTP header shall be set as defined above for the "200 OK" response.
headers
:
Content-Range
:
...
...
@@ -2176,7 +2176,7 @@ components:
Shall be returned when the whole content of the archive containing
the artifact files has been read successfully.
The
payload body
shall be a ZIP archive containing the requested
The
message content
shall be a ZIP archive containing the requested
set of artifacts selected according to the provisions specified above
in this clause, and, if the flag "include_signatures" was provided in
the related request, the applicable signature files and, if available,
...
...
@@ -2219,7 +2219,7 @@ components:
successfully according to the request.
The response body shall contain the requested part of the archive.
The "Content-Type" HTTP header shall be set to "application/zip".
The "Content-Range" HTTP header shall be provided according to IETF RFC
7233
.
The "Content-Range" HTTP header shall be provided according to IETF RFC
9110
.
headers
:
Content-Range
:
required
:
true
...
...
@@ -2261,7 +2261,7 @@ components:
been read successfully.
If the "include_signatures" request URI parameter was not provided in
the related request, the
payload body
shall contain a copy of the artifact
the related request, the
message content
shall contain a copy of the artifact
file from the VNF package, as defined by ETSI GS NFV-SOL 004 and the "Content-Type"
HTTP header shall be set according to the content type of the artifact file.
If the artifact is encrypted, the header shall be set to the value "application/cms"
...
...
@@ -2269,7 +2269,7 @@ components:
to the value "application/octet-stream".
If the "include_signatures" request URI parameter was provided in the related request,
the "Content-Type" HTTP header shall be set to "application/zip and the
payload body
the "Content-Type" HTTP header shall be set to "application/zip and the
messgae content
shall contain a ZIP archive which includes:
• a copy of the artifact file from the VNF package, as defined by ETSI GS NFV SOL 004;
• the related security information (individual signature file and optional related
...
...
@@ -2305,17 +2305,14 @@ components:
description
:
|
206 PARTIAL CONTENT
If the NFVO supports range requests and the "include_signatures" request
URI parameter was not present in the related request, 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.
If the NFVO supports range requests and the "include_signatures" request URI parameter was not present
in the related request, this response shall be returned when a single consecutive byte range from the
content of the artifact file has been read successfully according to the request.
The response body shall contain the requested part 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".
The "Content-Range" HTTP header shall be provided according to IETF RFC 9110.
headers
:
Content-Range
:
required
:
true
...
...
src/SOL003/VNFPackageManagement/definitions/SOL003VNFPackageManagement_def.yaml
View file @
9d6ca422
...
...
@@ -382,8 +382,8 @@ definitions:
This type represents an artifact other than a software image which is
contained in or external to a VNF package.
NOTE : The attribute name "artifactURI" does not comply with the naming convention defined in clause 4.3 in ETSI GS
NFV-SOL 015. This is to maintain the backward compatibility.
NOTE :
The attribute name "artifactURI" does not comply with the naming convention defined in clause 4.3 in ETSI GS
NFV-SOL 015. This is to maintain the backward compatibility.
type
:
object
required
:
-
artifactPath
...
...
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