Fetch NSD archive
Use this API to obtain package content for a specific NSD archive. The GET method fetches the content of the NSD archive. The NSD archive is implemented as a single compressed file, the content of the NSD archive is provided as onboarded, and a CSAR is provided according to ETSI GS NFV-SOL 007.
The following elements of the request, example, and responses are described:
Request
| Aspect | Value |
|---|---|
| Endpoint URL | /api/etsi/nsd/v2/ns_descriptors/<nsd-id>/nsd_content |
| HTTP Method | GET |
Request headers
| Header | Value |
|---|---|
| Content-Type | applicaion/zip |
| Version | 2.1.0 |
| Range | This value is optional. Can be used to continue an aborted transmission. Example value to commence from 1000 bytes:bytes=1000- |
Request data
None
Request data example
None
Response codes
| HTTP status code | Description |
|---|---|
| 200 | OK. The NSD package content was successfully retrieved. |
| 206 | If Range header is provided, then the response indicates partial content. |
| 400 | The response body contains details about the error. |
| 404 | When No Package for supplied ID is found. |
| 409 | Typically, this code is because nsdOnboardingState of the NS descriptor has
a value different from ONBOARDED. |
| 416 | Range Not Satisfiable – when range provided is invalid or cannot be obtained. |
| 500 | Internal Server Error |
| 4xx/5xx | In addition to the response codes defined in this table, any common error response codes. |
Response headers
| Header | Value |
|---|---|
| Content-Type | application/zip |
| Content-Range (only set for 206 HTTP response code) | bytes 1000-/* |
Response data
A successful response payload body contains a compressed file, which is the content of the NSD archive.