Loading src/SOL005/NSDManagement/NSDManagement.yaml +6 −6 Original line number Original line Diff line number Diff line Loading @@ -1576,7 +1576,7 @@ components: shall be returned when a single consecutive byte range from the content of the NSD file has been read shall be returned when a single consecutive byte range from the content of the NSD file has been read successfully according to the request. successfully according to the request. The response body shall contain the requested part of the NSD archive. The response body shall contain the requested part of the NSD archive. The "Content-Range" HTTP header shall be provided according to IETF RFC 9110. 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. The "Content-Type" HTTP header shall be set as defined above for the "200 OK" response. headers: headers: Content-Type: Content-Type: Loading Loading @@ -1982,7 +1982,7 @@ components: Shall be returned when the content of the artifact file has been read successfully. Shall be returned when the content of the artifact file has been read successfully. If the "include_signatures" request URI parameter was not provided in the related request, 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 NSD archive, as defined the message content shall contain a copy of the artifact file from the NSD archive, as defined by ETSI GS NFV-SOL 007, and the "Content-Type" HTTP header shall be set according to the by ETSI GS NFV-SOL 007, 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 content type of the artifact file. If the artifact is encrypted, the header shall be set to the value "application/cms" (IETF RFC 7193). the value "application/cms" (IETF RFC 7193). Loading @@ -1990,7 +1990,7 @@ components: If the content type cannot be determined, the header shall be set to the value 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 "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" 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: and the message content shall contain a ZIP archive which includes: - a copy of the artifact file from the VNF package, as defined by ETSI GS NFVSOL 007 - a copy of the artifact file from the VNF package, as defined by ETSI GS NFVSOL 007 - the related security information (individual signature file and optional related individual - the related security information (individual signature file and optional related individual certificate file). certificate file). Loading Loading @@ -2695,14 +2695,14 @@ components: read successfully. read successfully. If the "include_signatures" URI query parameter was absent in the If the "include_signatures" URI query parameter was absent in the request, or if the manifest file has all security-related information request, or if the manifest file has all security-related information embedded (i.e. there is no separate certificate file), the payload embedded (i.e. there is no separate certificate file), the message body shall contain a copy of the manifest file of the PNFD archive, content shall contain a copy of the manifest file of the PNFD archive, and the "Content-Type" HTTP header shall be set to "text/plain". and the "Content-Type" HTTP header shall be set to "text/plain". If the "include_signatures" URI query parameter was present in the If the "include_signatures" URI query parameter was present in the related request and the manifest file does not have all the related request and the manifest file does not have all the security-related information embedded (i.e. there is a separate certificate file), security-related information embedded (i.e. there is a separate certificate file), the "Content-Type" HTTP header shall be set to "application/zip" and the "Content-Type" HTTP header shall be set to "application/zip" and the payload body shall contain a ZIP archive which includes: the message content shall contain a ZIP archive which includes: - a copy of the manifest file of the PNFD archive; - a copy of the manifest file of the PNFD archive; - a copy of the related individual certificate file. - a copy of the related individual certificate file. headers: headers: Loading src/SOL005/NSLifecycleManagement/NSLifecycleManagement.yaml +1 −1 Original line number Original line Diff line number Diff line Loading @@ -1139,7 +1139,7 @@ components: NsLcmOpOccCancelRequest: NsLcmOpOccCancelRequest: description: | description: | The POST request to this resource shall include a CancelMode structure in the payload body to choose between The POST request to this resource shall include a CancelMode structure in the message content to choose between "graceful" and "forceful" cancellation. "graceful" and "forceful" cancellation. content: content: application/json: application/json: Loading src/SOL005/NSLifecycleManagement/definitions/SOL005NSLifecycleManagement_def.yaml +5 −5 Original line number Original line Diff line number Diff line Loading @@ -2537,7 +2537,7 @@ definitions: as it may describe the version dependencies of the descriptor referenced in the as it may describe the version dependencies of the descriptor referenced in the profile or of other descriptors with the same external invariant identifier. profile or of other descriptors with the same external invariant identifier. NOTE 3: The "overridingVersionDependency" attribute may only be present if NOTE 3: The "overridingVersionDependency" attribute may only be present if the "overrridingNsdId" attribute is present. the "overridingNsdId" attribute is present. type: object type: object required: required: - nsProfileId - nsProfileId Loading Loading @@ -3310,10 +3310,10 @@ definitions: InstantiateVnfData: InstantiateVnfData: description: > description: > This type represents the information related to a SAP of a NS. The InstantiateVnfData data type specifies the The InstantiateVnfData data type specifies the parameters that are needed for VNF instantiation. This parameters that are needed for VNF instantiation. This information element is used for the bottom-up NS creation when information element is used for the bottom-up NS creation when the OSS/BSS explicitly requests VNF the OSS/BSS explicitly requests VNF instantiation for a given NS. When the NFVO invokes the Instantiate VNF instantiation for a given NS. When the NFVO invokes the Instantiate VNF update operation, a set of update operation, a set of these parameters are then passed by the NFVO to the VNFM. these parameters are then passed by the NFVO to the VNFM. NOTE 1: It is possible to have several ExtManagedVirtualLinkData for the same VNF internal NOTE 1: It is possible to have several ExtManagedVirtualLinkData for the same VNF internal VL in case of a multi-site VNF spanning several VIMs. The set of ExtManagedVirtualLinkData VL in case of a multi-site VNF spanning several VIMs. The set of ExtManagedVirtualLinkData Loading src/SOL005/NSPerformanceManagement/NSPerformanceManagement.yaml +1 −1 Original line number Original line Diff line number Diff line Loading @@ -635,7 +635,7 @@ paths: # Identifier of the subscription. # Identifier of the subscription. # This identifier can be retrieved from the resource referenced by the "Location" HTTP header in the response # This identifier can be retrieved from the resource referenced by the "Location" HTTP header in the response # to a POST request creating a new subscription resource. It can also be retrieved from the "id" attribute in the # to a POST request creating a new subscription resource. It can also be retrieved from the "id" attribute in the # payload body of that response. # message content of that response. # in: path # in: path # type: string # type: string # required: true # required: true Loading src/SOL005/VNFPackageManagement/VNFPackageManagement.yaml +1 −1 Original line number Original line Diff line number Diff line Loading @@ -780,7 +780,7 @@ components: description: | description: | Identifier of this subscription. This identifier can be retrieved from the resource referenced by the "Location" Identifier of this subscription. This identifier can be retrieved from the resource referenced by the "Location" HTTP header in the response to a POST request creating a new "Individual subscription" resource. It can also be retrieved HTTP header in the response to a POST request creating a new "Individual subscription" resource. It can also be retrieved from the "id" attribute in the payload body of that response. from the "id" attribute in the message content of that response. required: true required: true style: simple style: simple explode: false explode: false Loading Loading
src/SOL005/NSDManagement/NSDManagement.yaml +6 −6 Original line number Original line Diff line number Diff line Loading @@ -1576,7 +1576,7 @@ components: shall be returned when a single consecutive byte range from the content of the NSD file has been read shall be returned when a single consecutive byte range from the content of the NSD file has been read successfully according to the request. successfully according to the request. The response body shall contain the requested part of the NSD archive. The response body shall contain the requested part of the NSD archive. The "Content-Range" HTTP header shall be provided according to IETF RFC 9110. 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. The "Content-Type" HTTP header shall be set as defined above for the "200 OK" response. headers: headers: Content-Type: Content-Type: Loading Loading @@ -1982,7 +1982,7 @@ components: Shall be returned when the content of the artifact file has been read successfully. Shall be returned when the content of the artifact file has been read successfully. If the "include_signatures" request URI parameter was not provided in the related request, 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 NSD archive, as defined the message content shall contain a copy of the artifact file from the NSD archive, as defined by ETSI GS NFV-SOL 007, and the "Content-Type" HTTP header shall be set according to the by ETSI GS NFV-SOL 007, 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 content type of the artifact file. If the artifact is encrypted, the header shall be set to the value "application/cms" (IETF RFC 7193). the value "application/cms" (IETF RFC 7193). Loading @@ -1990,7 +1990,7 @@ components: If the content type cannot be determined, the header shall be set to the value 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 "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" 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: and the message content shall contain a ZIP archive which includes: - a copy of the artifact file from the VNF package, as defined by ETSI GS NFVSOL 007 - a copy of the artifact file from the VNF package, as defined by ETSI GS NFVSOL 007 - the related security information (individual signature file and optional related individual - the related security information (individual signature file and optional related individual certificate file). certificate file). Loading Loading @@ -2695,14 +2695,14 @@ components: read successfully. read successfully. If the "include_signatures" URI query parameter was absent in the If the "include_signatures" URI query parameter was absent in the request, or if the manifest file has all security-related information request, or if the manifest file has all security-related information embedded (i.e. there is no separate certificate file), the payload embedded (i.e. there is no separate certificate file), the message body shall contain a copy of the manifest file of the PNFD archive, content shall contain a copy of the manifest file of the PNFD archive, and the "Content-Type" HTTP header shall be set to "text/plain". and the "Content-Type" HTTP header shall be set to "text/plain". If the "include_signatures" URI query parameter was present in the If the "include_signatures" URI query parameter was present in the related request and the manifest file does not have all the related request and the manifest file does not have all the security-related information embedded (i.e. there is a separate certificate file), security-related information embedded (i.e. there is a separate certificate file), the "Content-Type" HTTP header shall be set to "application/zip" and the "Content-Type" HTTP header shall be set to "application/zip" and the payload body shall contain a ZIP archive which includes: the message content shall contain a ZIP archive which includes: - a copy of the manifest file of the PNFD archive; - a copy of the manifest file of the PNFD archive; - a copy of the related individual certificate file. - a copy of the related individual certificate file. headers: headers: Loading
src/SOL005/NSLifecycleManagement/NSLifecycleManagement.yaml +1 −1 Original line number Original line Diff line number Diff line Loading @@ -1139,7 +1139,7 @@ components: NsLcmOpOccCancelRequest: NsLcmOpOccCancelRequest: description: | description: | The POST request to this resource shall include a CancelMode structure in the payload body to choose between The POST request to this resource shall include a CancelMode structure in the message content to choose between "graceful" and "forceful" cancellation. "graceful" and "forceful" cancellation. content: content: application/json: application/json: Loading
src/SOL005/NSLifecycleManagement/definitions/SOL005NSLifecycleManagement_def.yaml +5 −5 Original line number Original line Diff line number Diff line Loading @@ -2537,7 +2537,7 @@ definitions: as it may describe the version dependencies of the descriptor referenced in the as it may describe the version dependencies of the descriptor referenced in the profile or of other descriptors with the same external invariant identifier. profile or of other descriptors with the same external invariant identifier. NOTE 3: The "overridingVersionDependency" attribute may only be present if NOTE 3: The "overridingVersionDependency" attribute may only be present if the "overrridingNsdId" attribute is present. the "overridingNsdId" attribute is present. type: object type: object required: required: - nsProfileId - nsProfileId Loading Loading @@ -3310,10 +3310,10 @@ definitions: InstantiateVnfData: InstantiateVnfData: description: > description: > This type represents the information related to a SAP of a NS. The InstantiateVnfData data type specifies the The InstantiateVnfData data type specifies the parameters that are needed for VNF instantiation. This parameters that are needed for VNF instantiation. This information element is used for the bottom-up NS creation when information element is used for the bottom-up NS creation when the OSS/BSS explicitly requests VNF the OSS/BSS explicitly requests VNF instantiation for a given NS. When the NFVO invokes the Instantiate VNF instantiation for a given NS. When the NFVO invokes the Instantiate VNF update operation, a set of update operation, a set of these parameters are then passed by the NFVO to the VNFM. these parameters are then passed by the NFVO to the VNFM. NOTE 1: It is possible to have several ExtManagedVirtualLinkData for the same VNF internal NOTE 1: It is possible to have several ExtManagedVirtualLinkData for the same VNF internal VL in case of a multi-site VNF spanning several VIMs. The set of ExtManagedVirtualLinkData VL in case of a multi-site VNF spanning several VIMs. The set of ExtManagedVirtualLinkData Loading
src/SOL005/NSPerformanceManagement/NSPerformanceManagement.yaml +1 −1 Original line number Original line Diff line number Diff line Loading @@ -635,7 +635,7 @@ paths: # Identifier of the subscription. # Identifier of the subscription. # This identifier can be retrieved from the resource referenced by the "Location" HTTP header in the response # This identifier can be retrieved from the resource referenced by the "Location" HTTP header in the response # to a POST request creating a new subscription resource. It can also be retrieved from the "id" attribute in the # to a POST request creating a new subscription resource. It can also be retrieved from the "id" attribute in the # payload body of that response. # message content of that response. # in: path # in: path # type: string # type: string # required: true # required: true Loading
src/SOL005/VNFPackageManagement/VNFPackageManagement.yaml +1 −1 Original line number Original line Diff line number Diff line Loading @@ -780,7 +780,7 @@ components: description: | description: | Identifier of this subscription. This identifier can be retrieved from the resource referenced by the "Location" Identifier of this subscription. This identifier can be retrieved from the resource referenced by the "Location" HTTP header in the response to a POST request creating a new "Individual subscription" resource. It can also be retrieved HTTP header in the response to a POST request creating a new "Individual subscription" resource. It can also be retrieved from the "id" attribute in the payload body of that response. from the "id" attribute in the message content of that response. required: true required: true style: simple style: simple explode: false explode: false Loading
