From efd773ec75f7c23f7d7a602dc168e7c3b5eeee23 Mon Sep 17 00:00:00 2001
From: Giacomo Bernini <g.bernini@nextworks.it>
Date: Wed, 21 Aug 2019 16:32:46 +0200
Subject: [PATCH] more fixes
---
.../VNFPackageManagement.yaml | 266 +++++++++---------
1 file changed, 133 insertions(+), 133 deletions(-)
diff --git a/src/SOL003/VNFPackageManagement/VNFPackageManagement.yaml b/src/SOL003/VNFPackageManagement/VNFPackageManagement.yaml
index c72b6c54..c6f8bcda 100644
--- a/src/SOL003/VNFPackageManagement/VNFPackageManagement.yaml
+++ b/src/SOL003/VNFPackageManagement/VNFPackageManagement.yaml
@@ -818,143 +818,143 @@ paths:
in: path
type: string
required: true
- get:
- description: >
- Fetch VNF Package.
- The GET method fetches the content of a VNF package identified by the
- VNF package identifier allocated by the NFVO.
- This method shall follow the provisions specified in the tables
- 10.4.5.3.2-1 and 10.4.5.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
- enum:
- - text/plain
- - application/zip
- - 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.
+ The GET method fetches the content of a VNF package identified by the
+ VNF package identifier allocated by the NFVO.
+ This method shall follow the provisions specified in the tables
+ 10.4.5.3.2-1 and 10.4.5.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
+ enum:
+ - text/plain
+ - application/zip
+ - 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 VNF package file has been read successfully.
- The response body shall include a copy of the VNF package file.
- The "Content-Type HTTP" header shall be set according to the type of the file,
- i.e. to "application/zip" for a VNF Package as defined in ETSI GS NFV SOL 004.
- headers:
- 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
- 206:
- description: >
- 206 PARTIAL CONTENT
+ Shall be returned when the whole content of the VNF package file has been read successfully.
+ The response body shall include a copy of the VNF package file.
+ The "Content-Type HTTP" header shall be set according to the type of the file,
+ i.e. to "application/zip" for a VNF Package as defined in ETSI GS NFV SOL 004.
+ headers:
+ 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
+ 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 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-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 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-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".
- $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".
+ $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 VNF package file (e.g. "access after end of file").
- $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 VNF package file (e.g. "access after end of file").
+ $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"
###############################################################################
# Individual VNF package artifact #
--
GitLab