VNFPackageManagement.yaml 110 KB
Newer Older
Giacomo Bernini's avatar
Giacomo Bernini committed
              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#/components/responses/400"
Giacomo Bernini's avatar
Giacomo Bernini committed
        401:
          $ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/401"
Giacomo Bernini's avatar
Giacomo Bernini committed
        403:
          $ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/403"
Giacomo Bernini's avatar
Giacomo Bernini committed
        404:
          $ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/404"
Giacomo Bernini's avatar
Giacomo Bernini committed
        405:
          $ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/405"
Giacomo Bernini's avatar
Giacomo Bernini committed
        406:
          $ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/406"
Giacomo Bernini's avatar
Giacomo Bernini committed
        409:
          $ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/409"
Giacomo Bernini's avatar
Giacomo Bernini committed
        416:
          $ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/416"
Giacomo Bernini's avatar
Giacomo Bernini committed
        500:
          $ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/500"
Giacomo Bernini's avatar
Giacomo Bernini committed
        503:
          $ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/503"
Giacomo Bernini's avatar
Giacomo Bernini committed
        504:
          $ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/504"
  ###############################################################################
  ###############################################################################
  '/vnf_packages/{vnfPkgId}/package_content':
    parameters:
      - name: vnfPkgId
        description: >
          Identifier of the VNF package. The identifier is
          allocated by the NFVO.
          This identifier can be retrieved from the "vnfPkgId"
          attribute in the VnfPackageOnboardingNotification or
          VnfPackageChangeNotification.
        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.
        The content of the package is provided as onboarded, i.e. depending on
        the security option used, the CSAR or the CSAR wrapped in a ZIP archive
        together with an external signature is returned, as defined in clause
        5.1 of ETSI GS NFV-SOL 004.

        NOTE:	Information about the applicable security option can be obtained
        by evaluating the "packageSecurityOption" attribute in the "VnfPkgInfo"
        structure.

        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
        - name: Authorization
          description: >
            The authorization token for the request.
            Reference: IETF RFC 7235
          in: header
Gergely Csatari's avatar
Gergely Csatari committed
          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 "Range" header is present in the request and the NFVO
            does not support responding to range requests with a 206 response,
            it shall return a 200 OK response instead as defined below.
          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: >
            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
Gergely Csatari's avatar
Gergely Csatari committed
            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
          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
Gergely Csatari's avatar
Gergely Csatari committed
            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
          $ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/400"
          $ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/401"
          $ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/403"
          $ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/404"
          $ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/405"
          $ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/406"
#          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#/components/responses/409"
#          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#/components/responses/416"
          $ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/500"
          $ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/503"
          $ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/504"
  '/onboarded_vnf_packages/{vnfdId}/package_content':
    parameters:
      - name: vnfdId
        description: >
          Identifier of the VNFD and the VNF package.
          The identifier is allocated by the VNF provider.
          This identifier can be retrieved from the "vnfdId" attribute
          in the VnfPackageOnboardingNotification or VnfPackageChangeNotification.
        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.
        The content of the package is provided as onboarded, i.e. depending on
        the security option used, the CSAR or the CSAR wrapped in a ZIP archive
        together with an external signature is returned, as defined in clause
        5.1 of ETSI GS NFV-SOL 004.

        NOTE:	Information about the applicable security option can be obtained
        by evaluating the "packageSecurityOption" attribute in the "VnfPkgInfo"
        structure.

        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 "Range" header is present in the request and the NFVO
            does not support responding to range requests with a 206 response,
            it shall return a 200 OK response instead as defined below.
          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

            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#/components/responses/400"
          $ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/401"
          $ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/403"
          $ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/404"
          $ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/405"
          $ref: "../../responses/SOL002SOL003_resp.yaml#/components/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#/components/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#/components/responses/416"
          $ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/500"
          $ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/503"
          $ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/504"

  ###############################################################################
  # VNF package artifacts                                                       #
  ###############################################################################
  '/vnf_packages/{vnfPkgId}/artifacts':
    parameters:
      - name: vnfPkgId
        description: >
          Identifier of the VNF package. The identifier is allocated by the NFVO.
          This identifier can be retrieved from the "vnfPkgId" attribute in the
          VnfPackageOnboardingNotification or VnfPackageChangeNotification
        in: path
        required: true
        type: string
    get:
      description: >
        Fetch VNF Package Artifacts.

        The GET method shall return an archive that contains a set of artifacts
        according to the provisions for inclusion/exclusion defined below,
        embedded in a directory structure being the same as in the VNF package.
        The criteria for exclusion/inclusion of an artifact in the archive are defined as follows:
        -	Artifacts that are software images shall be excluded from the archive.
        -	Artifacts that are not software images and that are external to the VNF package shall be 
            excluded from the archive unless the URI query parameter "include_external_artifacts" has 
            been provided. External artifacts shall be included in the archive using the content of 
            the "artifactPath" attribute as the path.
        -	All additional artifacts included in the VNF package that are MANO artifacts shall
            be included in the archive, unless the URI query parameter "exclude_all_mano_artifacts"
            has been provided, in which case such artifacts shall be excluded.
        -	All additional artifacts included in the VNF package that are non-MANO artifacts
            shall be included in the archive, unless:
            	the URI query parameter "exclude_all_non_mano_artifacts" has been provided,
                in which case such artifacts shall be excluded;
            	the URI query parameter "select_non_mano_artifact_sets" has been provided and
                is supported by the NFVO, in which case only those non-MANO artifacts shall be
                included whose non-MANO artifact set identifier matches one of the values of the query parameter.
        Package metadata such as manifest file or VNFD shall not be included in the archive.
        This method shall follow the provisions specified in the tables 10.4.5a.3.2-1 and
        10.4.5a.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.
            The "Accept" HTTP header shall be set to "application/zip".
          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 archive containing
            the artifact files has been read successfully.
            The payload body 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,
            the separate certificate files from the VNF package.
            The "Content-Type" HTTP header shall be set to "application/zip".
          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 archive
            that would have been returned in a "200 OK" response has been read
            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.
          headers:
            Content-Range:
              type: string
              maximum: 1
              minimum: 1
            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
        400:
          $ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/400"
          $ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/401"
          $ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/403"
          $ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/404"
          $ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/405"
          $ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/406"
          $ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/409"
          $ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/416"
          $ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/500"
          $ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/503"
          $ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/504"

  '/onboarded_vnf_packages/{vnfdId}/artifacts':
    parameters:
      - name: vnfdId
        description: >
          Identifier of the VNFD and the VNF package.
          The identifier is allocated by the VNF provider.
          This identifier can be retrieved from the "vnfdId" attribute
          in the VnfPackageOnboardingNotification or VnfPackageChangeNotification.
        in: path
        required: true
        type: string
    get:
      description: >
        Fetch VNF Package Artifacts.

        The GET method shall return an archive that contains a set of artifacts
        according to the provisions for inclusion/exclusion defined below,
        embedded in a directory structure being the same as in the VNF package.
        The criteria for exclusion/inclusion of an artifact in the archive are defined as follows:
        -	Artifacts that are software images shall be excluded from the archive.
        -	Artifacts that are not software images and that are external to the VNF package shall be 
            excluded from the archive unless the URI query parameter "include_external_artifacts" has 
            been provided. External artifacts shall be included in the archive using the content of 
            the "artifactPath" attribute as the path.
        -	All additional artifacts included in the VNF package that are MANO artifacts shall
            be included in the archive, unless the URI query parameter "exclude_all_mano_artifacts"
            has been provided, in which case such artifacts shall be excluded.
        -	All additional artifacts included in the VNF package that are non-MANO artifacts
            shall be included in the archive, unless:
            	the URI query parameter "exclude_all_non_mano_artifacts" has been provided,
                in which case such artifacts shall be excluded;
            	the URI query parameter "select_non_mano_artifact_sets" has been provided and
                is supported by the NFVO, in which case only those non-MANO artifacts shall be
                included whose non-MANO artifact set identifier matches one of the values of the query parameter.
        Package metadata such as manifest file or VNFD shall not be included in the archive.
        This method shall follow the provisions specified in the tables 10.4.5a.3.2-1 and
        10.4.5a.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.
            The "Accept" HTTP header shall be set to "application/zip".
          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 archive containing
            the artifact files has been read successfully.
            The payload body 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,
            the separate certificate files from the VNF package.
            The "Content-Type" HTTP header shall be set to "application/zip".
          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 archive
            that would have been returned in a "200 OK" response has been read
            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.
          headers:
            Content-Range:
              type: string
              maximum: 1
              minimum: 1
            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
        400:
          $ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/400"
          $ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/401"
          $ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/403"
          $ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/404"
          $ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/405"
          $ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/406"
          $ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/409"
          $ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/416"
          $ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/500"
          $ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/503"
          $ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/504"

  ###############################################################################
  # Individual VNF package artifact                                             #
  ###############################################################################
  '/vnf_packages/{vnfPkgId}/artifacts/{artifactPath}':
    parameters:
      - name: artifactPath
        description: >
          SequenceFor an artifact contained as a file in the VNF package,
          this variable shall contain a sequence of one or more path segments
          representing the path of the artifact within the VNF package,
          relative to the root of the package.

          EXAMPLE: foo/bar/m%40ster.sh

          For an external artifact represented as a URI in the VNF package
          manifest, this variable shall contain a sequence of one or more path
          segments as synthesized by the NFVO (see clause 10.5.3.3),
          representing this artifact.

          Since multiple path segments are allowed to be contained in this variable,
          the "/" character that separates these segments is not percent-encoded.
          Each individual segment is percent-encoded if necessary as defined in clause
          4.1 of ETSI GS NFV-SOL 013.
        in: path
        type: string
        required: true
      - name: vnfPkgId
        description: >
          Identifier of the VNF package. The identifier is
          allocated by the NFVO.
          This identifier can be retrieved from the "vnfPkgId"
          attribute in the VnfPackageOnboardingNotification or
          VnfPackageChangeNotification.
        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 "Range" header is present in the request and the NFVO
            does not support responding to range requests with a 206 response,
            it shall return a 200 OK response instead as defined below.
          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
        - name: include_signatures
          description: >
            If this parameter is provided, the NFVO shall return the artifact
            and related security information (such as signature and optional
            certificate) in a ZIP archive.
            If this parameter is not given, the NFVO shall provide only a copy
            of the artifact file.
            This URI query parameter is a flag, i.e. it shall have no value.
            The NFVO shall support this parameter.
          in: query
          required: false
          type: string
      responses:
        200:
          description: >
            200 OK
            Shall be returned when the whole content of the artifact file has
            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
            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"
            (IETF RFC 7193). If the content type cannot be determined, the header shall be set
            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
            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
                individual certificate file).
          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 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.
          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#/components/responses/400"
          $ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/401"
          $ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/403"
          $ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/404"
          $ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/405"
          $ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/406"
#          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#/components/responses/409"
#          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#/components/responses/416"
          $ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/500"
          $ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/503"
          $ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/504"

  '/onboarded_vnf_packages/{vnfdId}/artifacts/{artifactPath}':
    parameters:
      - name: artifactPath
        description: >
          SequenceFor an artifact contained as a file in the VNF package,
          this variable shall contain a sequence of one or more path segments
          representing the path of the artifact within the VNF package,
          relative to the root of the package.

          EXAMPLE: foo/bar/m%40ster.sh

          For an external artifact represented as a URI in the VNF package
          manifest, this variable shall contain a sequence of one or more path
          segments as synthesized by the NFVO (see clause 10.5.3.3),
          representing this artifact.

          Since multiple path segments are allowed to be contained in this variable,
          the "/" character that separates these segments is not percent-encoded.
          Each individual segment is percent-encoded if necessary as defined in clause
          4.1 of ETSI GS NFV-SOL 013.
        in: path
        type: string
        required: true
      - name: vnfdId
        description: >
          Identifier of the VNFD and the VNF package.
          The identifier is allocated by the VNF provider.
          This identifier can be retrieved from the "vnfdId" attribute
          in the VnfPackageOnboardingNotification or VnfPackageChangeNotification.
        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 "Range" header is present in the request and the NFVO
            does not support responding to range requests with a 206 response,
            it shall return a 200 OK response instead as defined below.
          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
        - name: include_signatures
          description: >
            If this parameter is provided, the NFVO shall return the artifact
            and related security information (such as signature and optional
            certificate) in a ZIP archive.
            If this parameter is not given, the NFVO shall provide only a copy
            of the artifact file.
            This URI query parameter is a flag, i.e. it shall have no value.
            The NFVO shall support this parameter.
          in: query
          required: false
          type: string
      responses:
        200:
          description: >
            200 OK