Commit 1f887009 authored by rameshnaraya's avatar rameshnaraya

Merge Request Issue. Re committing NSD Files.

parent 7a10c8d8
Pipeline #159 passed with stage
in 0 seconds
...@@ -2,13 +2,13 @@ swagger: "2.0" ...@@ -2,13 +2,13 @@ swagger: "2.0"
info: info:
description: > description: >
"DRAFT - SOL005 - NSD Management Interface IMPORTANT: Please note that "SOL005 - NSD Management Interface IMPORTANT: Please note that
this file might be not aligned to the current version of the ETSI Group Specification this file might be not aligned to the current version of the ETSI Group Specification
it refers to and has not been approved by the ETSI NFV ISG. In case of discrepancies it refers to and has not been approved by the ETSI NFV ISG. In case of discrepancies
the published ETSI Group Specification takes precedence. Please report bugs the published ETSI Group Specification takes precedence. Please report bugs
to https://forge.etsi.org/bugzilla/buglist.cgi?component=Nfv-Openapis" to https://forge.etsi.org/bugzilla/buglist.cgi?component=Nfv-Openapis"
version: "2.4.1" version: "2.4.1"
title: "DRAFT - SOL005 - NSD Management Interface" title: "SOL005 - NSD Management Interface"
contact: contact:
name: "NFV-SOL WG" name: "NFV-SOL WG"
license: license:
...@@ -100,22 +100,30 @@ paths: ...@@ -100,22 +100,30 @@ paths:
responses: responses:
200: 200:
description: > description: >
"Information about zero or more NS descriptors. 200 OK.
Information about zero or more NS descriptors.
The response body shall contain a representation of The response body shall contain a representation of
zero or more NS descriptors, as defined in zero or more NS descriptors, as defined in
clause 5.5.2.2" clause 5.5.2.2
schema:
$ref: "definitions/SOL005NSDescriptorManagement_def.yaml#/definitions/NsdInfo"
headers: headers:
Content-Type: Content-Type:
type: string
description: The MIME type of the body of the response. description: The MIME type of the body of the response.
type: string
maximum: 1
minimum: 1
WWW-Authenticate: WWW-Authenticate:
type: string type: string
description: > description: >
Challenge if the corresponding HTTP request has not provided Challenge if the corresponding HTTP request has not provided
authorization, or error details if the corresponding HTTP authorization, or error details if the corresponding HTTP
request has provided an invalid authorization token. request has provided an invalid authorization token.
schema:
type: array
items:
properties:
NsdInfo:
$ref: "definitions/SOL005NSDescriptorManagement_def.yaml#/definitions/NsdInfo"
400: 400:
$ref: "responses/SOL005_resp.yaml#/responses/400" $ref: "responses/SOL005_resp.yaml#/responses/400"
401: 401:
...@@ -141,19 +149,8 @@ paths: ...@@ -141,19 +149,8 @@ paths:
post: post:
summary: "Create a new NS descriptor resource." summary: "Create a new NS descriptor resource."
description: > description: >
"The POST method is used to create a new NS descriptor resource or a new version of an on-boarded NS descriptor The POST method is used to create a new NS descriptor resource or a new version of an on-boarded NS descriptor.
resource. This method shall follow the provisions specified in the parameters:
Tables 5.4.2.3.1-1 and 5.4.2.3.1-2 for URI query parameters,
request and response data structures, and response codes."
parameters:
- name: "createNsdInfoRequest"
description: >
"The CreateNsdInfoRequest contains parameters for creating
an NS descriptor resource, as defined in clause 5.5.2.4 of GS NFV-SOL 005."
in: "body"
required: true
schema:
$ref: "definitions/SOL005NSDescriptorManagement_def.yaml#/definitions/CreateNsdInfoRequest"
- name: Accept - name: Accept
description: > description: >
Content-Types that are acceptable for the response. Content-Types that are acceptable for the response.
...@@ -174,20 +171,56 @@ paths: ...@@ -174,20 +171,56 @@ paths:
Reference: IETF RFC 7231 Reference: IETF RFC 7231
in: header in: header
required: true required: true
type: string type: string
- name: "body"
in: "body"
required: true
schema:
type: "object"
required:
- "CreateNsdInfoRequest"
properties:
CreateNsdInfoRequest:
$ref: "definitions/SOL005NSDescriptorManagement_def.yaml#/definitions/CreateNsdInfoRequest"
description: >
The CreateNsdInfoRequest contains parameters for creating
an NS descriptor resource, as defined in clause 5.5.2.4 of GS NFV-SOL 005.
responses: responses:
201: 201:
description: > description: "Status 201"
Status 201 schema:
type: "object"
description: >
201 Created.
An NS descriptor resource was created An NS descriptor resource was created successfully, as a
successfully, as a new NS descriptor resource. new NS descriptor resource. The response body shall contain a representation
The response body shall contain a representation of of the new NS descriptor resource, as defined in clause 5.5.2.2 of
the new NS descriptor resource, as defined in GS NFV-SOL 005.
clause 5.5.2.2. The HTTP response shall include a "Location"
The HTTP response shall include a "Location" HTTP header that contains the resource URI of the
HTTP header that contains the resource URI of the new NS descriptor resource.
new NS descriptor resource. properties:
NsdInfo:
$ref: "definitions/SOL005NSDescriptorManagement_def.yaml#/definitions/NsdInfo"
headers:
Location:
type: "string"
description: >
The HTTP response shall include a Location HTTP header
that contains the resource URI of the new NS descriptor resource.
Content-Type:
type: "string"
description: >
The MIME type of the body of the response.This header
field shall be present if the response has a non-empty message
body.
WWW-Authenticate:
type: "string"
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.
400: 400:
$ref: "responses/SOL005_resp.yaml#/responses/400" $ref: "responses/SOL005_resp.yaml#/responses/400"
401: 401:
...@@ -209,23 +242,8 @@ paths: ...@@ -209,23 +242,8 @@ paths:
500: 500:
$ref: "responses/SOL005_resp.yaml#/responses/500" $ref: "responses/SOL005_resp.yaml#/responses/500"
503: 503:
$ref: "responses/SOL005_resp.yaml#/responses/503" $ref: "responses/SOL005_resp.yaml#/responses/503"
schema:
type: "object"
description: >
"An NS descriptor resource was created successfully, as a
new NS descriptor resource. The response body shall contain a representation
of the new NS descriptor resource, as defined in clause 5.5.2.2 of
GS NFV-SOL 005."
properties:
NsdInfo:
$ref: "definitions/SOL005NSDescriptorManagement_def.yaml#/definitions/NsdInfo"
headers:
Location:
type: "string"
description: >
"The HTTP response shall include a "Location" HTTP header
that contains the resource URI of the new NS descriptor resource."
############################################################################### ###############################################################################
# Individual NS Descriptor # # Individual NS Descriptor #
############################################################################### ###############################################################################
...@@ -254,71 +272,36 @@ paths: ...@@ -254,71 +272,36 @@ paths:
type: string type: string
responses: responses:
200: 200:
description: > description: "Status 201"
200 OK
Information about the individual NS descriptor.
The response body shall contain a representation of
the individual NS descriptor, as defined in
clause 5.5.2.2.
schema: schema:
$ref: "definitions/SOL005NSDescriptorManagement_def.yaml#/definitions/NsdInfo" type: "object"
400: description: >
$ref: "responses/SOL005_resp.yaml#/responses/400-attr-selector" 200 OK.
401:
$ref: "responses/SOL005_resp.yaml#/responses/401" Information about the individual NS descriptor.
403: The response body shall contain a representation of
$ref: "responses/SOL005_resp.yaml#/responses/403" the individual NS descriptor, as defined in
404: clause 5.5.2.2.
$ref: "responses/SOL005_resp.yaml#/responses/404" properties:
405: NsdInfo:
$ref: "responses/SOL005_resp.yaml#/responses/405" $ref: "definitions/SOL005NSDescriptorManagement_def.yaml#/definitions/NsdInfo"
406:
$ref: "responses/SOL005_resp.yaml#/responses/406"
409:
$ref: "responses/NSDescriptorManagement_resp.yaml#/responses/409"
412:
$ref: "responses/SOL005_resp.yaml#/responses/412"
416:
$ref: "responses/SOL005_resp.yaml#/responses/416"
500:
$ref: "responses/SOL005_resp.yaml#/responses/500"
503:
$ref: "responses/SOL005_resp.yaml#/responses/503"
delete:
summary: "Delete an individual NS descriptor resource."
description: >
"The DELETE method deletes an individual NS descriptor resource.
An individual NS descriptor resource can only be deleted when there is no
NS instance using it (i.e. usageState = NOT_IN_USE) and has been disabled
already (i.e. operationalState = DISABLED). Otherwise, the DELETE method
shall fail. This method shall follow the provisions specified in the Tables
5.4.3.3.5-1 and 5.4.3.3.5-2 of GS NFV-SOL 005 for URI query parameters,
request and response data structures, and response codes."
parameters:
- name: Authorization
description: >
The authorization token for the request.
Reference: IETF RFC 7235
in: header
required: false
type: string
responses:
204:
description: >
204 No Content
The operation has completed successfully.
The response body shall be empty.
headers: headers:
Location:
type: "string"
description: >
The HTTP response shall include a Location HTTP header
that contains the resource URI of the new NS descriptor resource.
Content-Type:
type: "string"
description: >
The MIME type of the body of the response.This header
field shall be present if the response has a non-empty message body.
WWW-Authenticate: WWW-Authenticate:
type: "string"
description: > description: >
Challenge if the corresponding HTTP request has not provided Challenge if the corresponding HTTP request has not provided
authorization, or error details if the corresponding HTTP authorization, or error details if the corresponding HTTP request
request has provided an invalid authorization token. has provided an invalid authorization token.
type: string
maximum: 1
minimum: 0
400: 400:
$ref: "responses/SOL005_resp.yaml#/responses/400-attr-selector" $ref: "responses/SOL005_resp.yaml#/responses/400-attr-selector"
401: 401:
...@@ -334,17 +317,17 @@ paths: ...@@ -334,17 +317,17 @@ paths:
409: 409:
$ref: "responses/NSDescriptorManagement_resp.yaml#/responses/409" $ref: "responses/NSDescriptorManagement_resp.yaml#/responses/409"
412: 412:
$ref: "responses/SOL005_resp.yaml#/responses/412" $ref: "responses/SOL005_resp.yaml#/responses/412"
416: 416:
$ref: "responses/SOL005_resp.yaml#/responses/416" $ref: "responses/SOL005_resp.yaml#/responses/416"
500: 500:
$ref: "responses/SOL005_resp.yaml#/responses/500" $ref: "responses/SOL005_resp.yaml#/responses/500"
503: 503:
$ref: "responses/SOL005_resp.yaml#/responses/503" $ref: "responses/SOL005_resp.yaml#/responses/503"
patch: patch:
summary: "Update NSD Info" summary: Modify the operational state and/or the user defined data of an individual NS descriptor resource.
description: > description: >
"The PATCH method modifies the operational state and/or user defined The PATCH method modifies the operational state and/or user defined
data of an individual NS descriptor resource. This method can be used to: data of an individual NS descriptor resource. This method can be used to:
1) Enable a previously disabled individual NS descriptor resource, allowing 1) Enable a previously disabled individual NS descriptor resource, allowing
again its use for instantiation of new network service with this descriptor. again its use for instantiation of new network service with this descriptor.
...@@ -353,11 +336,8 @@ paths: ...@@ -353,11 +336,8 @@ paths:
any further use for instantiation of new network service(s) with this descriptor. any further use for instantiation of new network service(s) with this descriptor.
The usage state (i.e. "IN_USE/NOT_IN_USE") shall not changes a result. The usage state (i.e. "IN_USE/NOT_IN_USE") shall not changes a result.
3) Modify the user defined data of an individual NS descriptor resource. 3) Modify the user defined data of an individual NS descriptor resource.
This method shall follow the provisions specified in the Tables 5.4.3.3.4-1
and 5.4.3.3.4-2 for URI query parameters,request and response data structures,
and response codes."
parameters: parameters:
- name: "NsdInfoModifications" - name: "body"
in: "body" in: "body"
required: true required: true
schema: schema:
...@@ -368,9 +348,7 @@ paths: ...@@ -368,9 +348,7 @@ paths:
NsdInfoModifications: NsdInfoModifications:
$ref: "definitions/SOL005NSDescriptorManagement_def.yaml#/definitions/NsdInfoModifications" $ref: "definitions/SOL005NSDescriptorManagement_def.yaml#/definitions/NsdInfoModifications"
description: > description: >
"The operation was completed successfully. The response body Parameters for the modification of an individual NS descriptor resource.
shall contain attribute modifications for an 'Individual NS Descriptor'
resource (see clause 5.5.2.6 of GS NFV SOL-005)."
- name: Authorization - name: Authorization
description: > description: >
The authorization token for the request. The authorization token for the request.
...@@ -388,10 +366,11 @@ paths: ...@@ -388,10 +366,11 @@ paths:
responses: responses:
200: 200:
description: > description: >
Information about the individual NS descriptor. 200 OK.
The response body shall contain a representation of The operation was completed successfully.
the individual NS descriptor, as defined in The response body shall contain attribute
clause 5.5.2.2. modifications for an 'Individual NS Descriptor'
resource.
headers: headers:
Content-Type: Content-Type:
description: The MIME type of the body of the response. description: The MIME type of the body of the response.
...@@ -409,7 +388,63 @@ paths: ...@@ -409,7 +388,63 @@ paths:
schema: schema:
type: array type: array
items: items:
$ref: "definitions/SOL005NSDescriptorManagement_def.yaml#/definitions/NsdInfoModifications" properties:
NsdInfoModifications:
$ref: "definitions/SOL005NSDescriptorManagement_def.yaml#/definitions/NsdInfoModifications"
400:
$ref: "responses/SOL005_resp.yaml#/responses/400-attr-selector"
401:
$ref: "responses/SOL005_resp.yaml#/responses/401"
403:
$ref: "responses/SOL005_resp.yaml#/responses/403"
404:
$ref: "responses/SOL005_resp.yaml#/responses/404"
405:
$ref: "responses/SOL005_resp.yaml#/responses/405"
406:
$ref: "responses/SOL005_resp.yaml#/responses/406"
409:
$ref: "responses/NSDescriptorManagement_resp.yaml#/responses/409"
412:
$ref: "responses/SOL005_resp.yaml#/responses/412"
416:
$ref: "responses/SOL005_resp.yaml#/responses/416"
500:
$ref: "responses/SOL005_resp.yaml#/responses/500"
503:
$ref: "responses/SOL005_resp.yaml#/responses/503"
delete:
summary: "Delete an individual NS descriptor resource."
description: >
The DELETE method deletes an individual NS descriptor resource.
An individual NS descriptor resource can only be deleted when there is no NS instance using it (i.e. usageState =
NOT_IN_USE) and has been disabled already (i.e. operationalState = DISABLED). Otherwise, the DELETE method
shall fail.
parameters:
- name: Authorization
description: >
The authorization token for the request.
Reference: IETF RFC 7235
in: header
required: false
type: string
responses:
204:
description: >
204 No Content
The operation has completed successfully.
The response body shall be empty.
headers:
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
400: 400:
$ref: "responses/SOL005_resp.yaml#/responses/400-attr-selector" $ref: "responses/SOL005_resp.yaml#/responses/400-attr-selector"
401: 401:
...@@ -440,6 +475,7 @@ paths: ...@@ -440,6 +475,7 @@ paths:
in: "path" in: "path"
required: true required: true
type: "string" type: "string"
############################################################################### ###############################################################################
# NSD Content # # NSD Content #
############################################################################### ###############################################################################
...@@ -447,9 +483,9 @@ paths: ...@@ -447,9 +483,9 @@ paths:
get: get:
summary: "Fetch the content of a NSD." summary: "Fetch the content of a NSD."
description: > description: >
"The GET method fetches the content of the NSD.The NSD can The GET method fetches the content of the NSD.
be implemented as a single file or as a collection of multiple files. If The NSD can be implemented as a single file or as a collection of multiple files.
the NSD is implemented in the form of multiple files, a ZIP file embedding If the NSD is implemented in the form of multiple files, a ZIP file embedding
these files shall be returned. If the NSD is implemented as a single file, these files shall be returned. If the NSD is implemented as a single file,
either that file or a ZIP file embedding that file shall be returned. either that file or a ZIP file embedding that file shall be returned.
The selection of the format is controlled by the "Accept" HTTP header passed The selection of the format is controlled by the "Accept" HTTP header passed
...@@ -461,7 +497,7 @@ paths: ...@@ -461,7 +497,7 @@ paths:
"Accept" header contains both "text/plain" and "application/zip", "Accept" header contains both "text/plain" and "application/zip",
it is up to the NFVO to choose the format to return for a single-file NSD; it is up to the NFVO to choose the format to return for a single-file NSD;
for a multi-file NSD, a ZIP file shall be returned.NOTE: The structure for a multi-file NSD, a ZIP file shall be returned.NOTE: The structure
of the NSD zip file is outside the scope of the present document." of the NSD zip file is outside the scope of the present document.
parameters: parameters:
- name: Accept - name: Accept
description: > description: >
...@@ -493,12 +529,16 @@ paths: ...@@ -493,12 +529,16 @@ paths:
responses: responses:
200: 200:
description: > description: >
"On success, the content of the NSD is returned. The payload OK.
body shall contain a copy of the file representing the NSD or a ZIP On success, the content of the NSD is returned.
file that contains the file or multiple files representing the NSD, The payload body shall contain a copy of the file
as specified above. The "Content-Type" HTTP header shall be set according representing the NSD or a ZIP file that contains the file
to the format of the returned file, i.e. to "text/plain" for a YAML or multiple files representing the NSD, as specified
file or to "application/zip" for a ZIP file." above.
The "Content-Type" HTTP header shall be set
according to the format of the returned file, i.e. to
"text/plain" for a YAML file or to "application/zip" for a
ZIP file.
headers: headers:
Content-Type: Content-Type:
description: The MIME type of the body of the response. description: The MIME type of the body of the response.
...@@ -513,7 +553,6 @@ paths: ...@@ -513,7 +553,6 @@ paths:
type: string type: string
maximum: 1 maximum: 1
minimum: 0 minimum: 0
206: 206:
$ref: "responses/SOL005_resp.yaml#/responses/206" $ref: "responses/SOL005_resp.yaml#/responses/206"
400: 400:
...@@ -529,7 +568,7 @@ paths: ...@@ -529,7 +568,7 @@ paths:
406: 406:
$ref: "responses/SOL005_resp.yaml#/responses/406" $ref: "responses/SOL005_resp.yaml#/responses/406"
409: 409:
$ref: "responses/NSDescriptorManagement_resp.yaml#/responses/409" $ref: "responses/NSDescriptorManagement_resp.yaml#/responses/409-nsd-onboarding-state-NOT-ONBOARDED"
412: 412:
$ref: "responses/SOL005_resp.yaml#/responses/412" $ref: "responses/SOL005_resp.yaml#/responses/412"
416: 416:
...@@ -544,21 +583,26 @@ paths: ...@@ -544,21 +583,26 @@ paths:
description: > description: >
"The PUT method is used to upload the content of a NSD. The NSD "The PUT method is used to upload the content of a NSD. The NSD
to be uploaded can be implemented as a single file or as a collection of to be uploaded can be implemented as a single file or as a collection of
multiple files, as defined in clause 5.4.4.3.2 of GS NFV-SOL 005. If the multiple files, as defined in clause 5.4.4.3.2 of GS NFV-SOL 005.
NSD is implemented in the form of multiple files, a ZIP file embedding these If the NSD is implemented in the form of multiple files, a ZIP file embedding these
files shall be uploaded. If the NSD is implemented as a single file, either files shall be uploaded.
that file or a ZIP file embedding that file shall be uploaded. The "Content-Type" If the NSD is implemented as a single file, either that file or a ZIP file
embedding that file shall be uploaded. The "Content-Type"
HTTP header in the PUT request shall be set accordingly based on the format HTTP header in the PUT request shall be set accordingly based on the format
selection of the NSD. If the NSD to be uploaded is a text file, the "Content-Type" selection of the NSD.
header is set to "text/plain". If the NSD to be uploaded is a zip file, If the NSD to be uploaded is a text file, the "Content-Type"
the "Content-Type" header is set to "application/zip". This method shall header is set to "text/plain".
follow the provisions specified in the Tables 5.4.4.3.3-1 and 5.4.4.3.3-2 If the NSD to be uploaded is a zip file,
the "Content-Type" header is set to "application/zip".
This method shall follow the provisions specified in the Tables 5.4.4.3.3-1 and 5.4.4.3.3-2
of GS-NFV-SOL 005 for URI query parameters, request and response data structures, of GS-NFV-SOL 005 for URI query parameters, request and response data structures,
and response codes." and response codes."
parameters: parameters:
- name: Accept - name: Accept
description: > description: >
Content-Types that are acceptable for the response. Content-Types that are acceptable for the response.
The payload body contains a copy of the file representing the NSD
or a ZIP file that contains the file or multiple files representing the NSD.
in: header in: header
required: true required: true
type: string type: string
...@@ -575,7 +619,7 @@ paths: ...@@ -575,7 +619,7 @@ paths:
responses: responses:
202: 202:
description: > description: >
"Status 202" 202 Accepted
headers: headers:
Content-Type: Content-Type:
description: The MIME type of the body of the response. description: The MIME type of the body of the response.
...@@ -592,8 +636,10 @@ paths: ...@@ -592,8 +636,10 @@ paths:
minimum: 0 minimum: 0
204: 204:
description: > description: >
"The NSD content was successfully uploaded and validated (synchronous 204 No Content
mode). The response body shall be empty."
The NSD content was successfully uploaded and validated (synchronous mode).
The response body shall be empty.
206: 206:
$ref: "responses/SOL005_resp.yaml#/responses/206" $ref: "responses/SOL005_resp.yaml#/responses/206"
400: 400:
...@@ -609,7 +655,7 @@ paths: ...@@ -609,7 +655,7 @@ paths:
406: 406:
$ref: "responses/SOL005_resp.yaml#/responses/406" $ref: "responses/SOL005_resp.yaml#/responses/406"
409: 409:
$ref: "responses/NSDescriptorManagement_resp.yaml#/responses/409" $ref: "responses/NSDescriptorManagement_resp.yaml#/responses/409-nsd-onboarding-state-NOT-ONBOARDED"
412: 412:
$ref: "responses/SOL005_resp.yaml#/responses/412" $ref: "responses/SOL005_resp.yaml#/responses/412"
416: 416:
...@@ -624,6 +670,7 @@ paths: ...@@ -624,6 +670,7 @@ paths:
in: "path" in: "path"
required: true required: true
type: "string" type: "string"
############################################################################### ###############################################################################
# PNF Descriptors # # PNF Descriptors #
############################################################################### ###############################################################################
...@@ -700,9 +747,11 @@ paths: ...@@ -700,9 +747,11 @@ paths:
maximum: 1 maximum: 1
minimum: 0 minimum: 0
schema: schema:
type: array type: "array"
items: items:
$ref: "definitions/SOL005NSDescriptorManagement_def.yaml#/definitions/PnfdInfo" properties:
PnfdInfo:
$ref: "definitions/SOL005NSDescriptorManagement_def.yaml#/definitions/PnfdInfo"
400: 400:
$ref: "responses/SOL005_resp.yaml#/responses/400-attr-selector" $ref: "responses/SOL005_resp.yaml#/responses/400-attr-selector"
401: 401:
...@@ -728,15 +777,8 @@ paths: ...@@ -728,15 +777,8 @@ paths:
post: post:
summary: "Create a new PNF descriptor resource." summary: "Create a new PNF descriptor resource."
description: > description: >
"The POST method is used to create a new PNF descriptor resource." The POST method is used to create a new PNF descriptor resource
parameters: parameters:
- name: "CreatePnfdInfoRequest"
description: >
"Parameters of creating a PNF descriptor resource, as defined in clause 5.5.2.6."
in: "body"
required: true
schema:
$ref: "definitions/SOL005NSDescriptorManagement_def.yaml#/definitions/CreatePnfdInfoRequest"
- name: Accept - name: Accept
description: > description: >
Content-Types that are acceptable for the response. Content-Types that are acceptable for the response.
...@@ -758,32 +800,52 @@ paths: ...@@ -758,32 +800,52 @@ paths:
in: header in: header
required: true required: true
type: string type: string
responses: - name: "body"
in: "body"
required: true
schema:
type: "object"
required:
- "CreatePnfdInfoRequest"
properties:
CreatePnfdInfoRequest:
$ref: "definitions/SOL005NSDescriptorManagement_def.yaml#/definitions/CreatePnfdInfoRequest"
description: >
Parameters of creating a PNF descriptor resource.
responses:
201: 201:
description: > description: 201 Created.
Status 201 schema:
type: "object"
A PNF descriptor resource was created successfully, as a description: >
new PNF descriptor resource. The response body shall contain a representation A PNF descriptor resource was created successfully,
of the new PNF descriptor resource, as defined in clause 5.5.2.5. as a new PNF descriptor resource.
The HTTP response shall include a "Location" HTTP header that contains The response body shall contain a representation of
the resource URI of the new PNF descriptor resource. the new PNF descriptor resource.
The HTTP response shall include a "Location" HTTP
header that contains the resource URI of the new
PNF descriptor resource
properties:
PnfdInfo:
$ref: "definitions/SOL005NSDescriptorManagement_def.yaml#/definitions/PnfdInfo"
headers: headers:
Location: