Skip to content
GitLab
Commit efa77b60 authored by moscatelli's avatar moscatelli
Browse files

SOL005: NSD Management and NS Lifecycle Management overall consolidation

parent 1c43fa02
Pipeline #1266 failed with stage
in 0 seconds
Hide whitespace changes
Inline Side-by-side
src/SOL005/NSDManagement/NSDManagement.yaml
View file @ efa77b60
...@@ -62,7 +62,7 @@ paths: ...@@ -62,7 +62,7 @@ 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.
parameters: parameters:
- name: Accept - name: Accept
description: > description: >
...@@ -90,11 +90,14 @@ paths: ...@@ -90,11 +90,14 @@ paths:
description: > description: >
201 CREATED 201 CREATED
An NS descriptor resource has been created successfully, as a new NS descriptor resource. An NS descriptor resource has been created
The response body shall contain a representation of the new NS descriptor resource, successfully, as a new NS descriptor resource.
as defined in clause 5.5.2.2. The response body shall contain a representation
The HTTP response shall include a "Location" HTTP header that contains the resource URI of the new NS descriptor resource, as defined in
of the new NS descriptor resource. clause 5.5.2.2.
The HTTP response shall include a "Location"
HTTP header that contains the resource URI of the
new NS descriptor resource.
schema: schema:
$ref: "definitions/SOL005NSDescriptorManagement_def.yaml#/definitions/NsdInfo" $ref: "definitions/SOL005NSDescriptorManagement_def.yaml#/definitions/NsdInfo"
headers: headers:
...@@ -134,14 +137,13 @@ paths: ...@@ -134,14 +137,13 @@ paths:
$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"
504:
$ref: "../responses/SOL005_resp.yaml#/responses/504"
get: get:
summary: Query information about multiple NS descriptor resources. summary: Query information about multiple NS descriptor resources.
description: > description: >
The GET method queries information about multiple NS descriptor resources. The GET method queries information about multiple NS descriptor resources.
This method shall follow the provisions specified in the
Tables 5.4.2.3.2-1 and 5.4.2.3.2-2 for URI query parameters,
request and response data structures, and response codes.
parameters: parameters:
- name: filter - name: filter
in: query in: query
...@@ -206,10 +208,14 @@ paths: ...@@ -206,10 +208,14 @@ paths:
200 OK 200 OK
Information about zero or more NS descriptors. Information about zero or more NS descriptors.
The response body shall contain in an array the representations of zero or more NS descriptors, The response body shall contain in an array the
as defined in clause 5.5.2.2. representations of zero or more NS descriptors, as
If the NFVO supports alternative 2 (paging) according to clause 4.7.2.1 for this resource, defined in clause 5.5.2.2.
inclusion of the Link HTTP header in this response shall follow the provisions in clause 4.7.2.3. If the NFVO supports alternative 2 (paging) according
to clause 5.4.2.1 of ETSI GS NFV-SOL 013 for
this resource, inclusion of the Link HTTP header in
this response shall follow the provisions in clause
5.4.2.3 of ETSI GS NFV-SOL 013.
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.
...@@ -256,6 +262,8 @@ paths: ...@@ -256,6 +262,8 @@ paths:
$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"
504:
$ref: "../responses/SOL005_resp.yaml#/responses/504"
############################################################################### ###############################################################################
# Individual NS Descriptor # # Individual NS Descriptor #
...@@ -287,9 +295,6 @@ paths: ...@@ -287,9 +295,6 @@ paths:
summary: Read information about an individual NS descriptor resource. summary: Read information about an individual NS descriptor resource.
description: > description: >
The GET method reads information about an individual NS descriptor. The GET method reads information about an individual NS descriptor.
This method shall follow the provisions specified in GS NFV-SOL 005 Tables
5.4.3.3.2-1 and 5.4.3.3.2-2 of GS NFV-SOL 005 for URI query parameters,
request and response data structures, and response codes.
parameters: parameters:
- name: Accept - name: Accept
description: > description: >
...@@ -304,8 +309,9 @@ paths: ...@@ -304,8 +309,9 @@ paths:
200 OK 200 OK
Information about the individual NS descriptor. Information about the individual NS descriptor.
The response body shall contain a representation of the individual NS descriptor, The response body shall contain a representation of
as defined in clause 5.5.2.2. the individual NS descriptor, as defined in
clause 5.5.2.2.
schema: schema:
$ref: "definitions/SOL005NSDescriptorManagement_def.yaml#/definitions/NsdInfo" $ref: "definitions/SOL005NSDescriptorManagement_def.yaml#/definitions/NsdInfo"
headers: headers:
...@@ -344,18 +350,20 @@ paths: ...@@ -344,18 +350,20 @@ paths:
$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"
504:
$ref: "../responses/SOL005_resp.yaml#/responses/504"
patch: patch:
summary: Modify the operational state and/or the user defined data of an individual NS descriptor resource. 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.
data of an individual NS descriptor resource. This method can be used to: 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
again its use for instantiation of new network service with this descriptor. network service with this descriptor. The usage state (i.e. "IN_USE/NOT_IN_USE") shall not change as a
The usage state (i.e. "IN_USE/NOT_IN_USE") shall not change as result. result.
2) Disable a previously enabled individual NS descriptor resource, preventing 2) Disable a previously enabled individual NS descriptor resource, preventing any further use for instantiation of
any further use for instantiation of new network service(s) with this descriptor. new network service(s) with this descriptor. The usage state (i.e. "IN_USE/NOT_IN_USE") shall not change
The usage state (i.e. "IN_USE/NOT_IN_USE") shall not changes a result. as 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.
parameters: parameters:
- name: NsdInfoModifications - name: NsdInfoModifications
...@@ -418,10 +426,15 @@ paths: ...@@ -418,10 +426,15 @@ paths:
description: > description: >
409 CONFLICT 409 CONFLICT
Error: The operation cannot be executed currently, due to a conflict with the state of the resource. Error: The operation cannot be executed currently,
Typically, this is due to an operational state mismatch, i.e. enable an already enabled or disable due to a conflict with the state of the resource.
an already disabled individual NS descriptor resource, or the "nsdOnboardingState" is not ONBOARDED. Typically, this is due to an operational state
The response body shall contain a ProblemDetails structure, in which the "detail" attribute shall convey mismatch, i.e. enable an already enabled or
disable an already disabled individual NS
descriptor resource, or the "nsdOnboardingState"
is not ONBOARDED.
The response body shall contain a ProblemDetails
structure, in which the "detail" attribute shall convey
more information about the error. more information about the error.
$ref: "../responses/SOL005_resp.yaml#/responses/409" $ref: "../responses/SOL005_resp.yaml#/responses/409"
412: 412:
...@@ -430,6 +443,8 @@ paths: ...@@ -430,6 +443,8 @@ paths:
$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"
504:
$ref: "../responses/SOL005_resp.yaml#/responses/504"
delete: delete:
summary: Delete an individual NS descriptor resource. summary: Delete an individual NS descriptor resource.
...@@ -490,17 +505,23 @@ paths: ...@@ -490,17 +505,23 @@ paths:
description: > description: >
409 CONFLICT 409 CONFLICT
Error: The operation cannot be executed currently, due to a conflict with the state of the resource. Error: The operation cannot be executed currently,
Typically, this is due to the fact the NS descriptor resource is in the enabled operational state due to a conflict with the state of the resource.
(i.e. operationalState = ENABLED) or there are running NS instances using the concerned individual Typically, this is due to the fact the NS descriptor
NS descriptor resource (i.e. usageState = IN_USE). resource is in the enabled operational state (i.e.
The response body shall contain a ProblemDetails structure, in which the "detail" attribute shall operationalState = ENABLED) or there are running
convey more information about the error. NS instances using the concerned individual NS
descriptor resource (i.e. usageState = IN_USE).
The response body shall contain a ProblemDetails
structure, in which the "detail" attribute shall convey
more information about the error.
$ref: "../responses/SOL005_resp.yaml#/responses/409" $ref: "../responses/SOL005_resp.yaml#/responses/409"
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"
504:
$ref: "../responses/SOL005_resp.yaml#/responses/504"
############################################################################### ###############################################################################
# NSD Content # # NSD Content #
...@@ -530,20 +551,16 @@ paths: ...@@ -530,20 +551,16 @@ paths:
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 GET method fetches the content of the NSD.
The NSD can be implemented as a single file or as a collection of multiple files. The NSD can be implemented as a single file or as a collection of multiple files. If the NSD is implemented in the form
If the NSD is implemented in the form of multiple files, a ZIP file embedding of multiple files, a ZIP file embedding these files shall be returned. If the NSD is implemented as a single file, either
these files shall be returned. If the NSD is implemented as a single file, 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 in the GET request:
The selection of the format is controlled by the "Accept" HTTP header passed • If the "Accept" header contains only "text/plain" and the NSD is implemented as a single file, the file shall be
in the GET request:• If the "Accept" header contains only "text/plain" returned; otherwise, an error message shall be returned.
and the NSD is implemented as a single file, the file shall be returned; • If the "Accept" header contains only "application/zip", the single file or the multiple files that make up the
otherwise, an error message shall be returned.• If the "Accept" header NSD shall be returned embedded in a ZIP file.
contains only "application/zip", the single file or the multiple files • If the "Accept" header contains both "text/plain" and "application/zip", it is up to the NFVO to choose the
that make up the NSD shall be returned embedded in a ZIP file.• If the format to return for a single-file NSD; for a multi-file NSD, a ZIP file shall be returned.
"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;
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.
parameters: parameters:
- name: Accept - name: Accept
description: > description: >
...@@ -570,15 +587,16 @@ paths: ...@@ -570,15 +587,16 @@ paths:
description: > description: >
200 OK 200 OK
Shall be returned when the content of the NSD has been read successfully. Shall be returned when the content of the NSD has
been read successfully.
The payload body shall contain a copy of the file The payload body shall contain a copy of the file
representing the NSD or a ZIP file that contains the file representing the NSD or a ZIP file that contains the
or multiple files representing the NSD, as specified file or multiple files representing the NSD, as
above. specified above.
The "Content-Type" HTTP header shall be set The "Content-Type" HTTP header shall be set
according to the format of the returned file, i.e. to according to the format of the returned file, i.e. to
"text/plain" for a YAML file or to "application/zip" for a "text/plain" for a YAML file or to "application/zip" for
ZIP file. 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.
...@@ -603,11 +621,15 @@ paths: ...@@ -603,11 +621,15 @@ paths:
description: > description: >
206 PARTIAL CONTENT 206 PARTIAL CONTENT
On success, if the NFVO supports range requests, a single consecutive byte range from the content On success, if the NFVO supports range requests,
of the NSD file is returned. a single consecutive byte range from the content of
The response body shall contain the requested part of the NSD file. the NSD file is returned.
The "Content-Range" HTTP header shall be provided according to IETF RFC 7233. The response body shall contain the requested part
The "Content-Type" HTTP header shall be set as defined above for the "200 OK" response. of the NSD 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.
$ref: "../responses/SOL005_resp.yaml#/responses/206" $ref: "../responses/SOL005_resp.yaml#/responses/206"
400: 400:
$ref: "../responses/SOL005_resp.yaml#/responses/400" $ref: "../responses/SOL005_resp.yaml#/responses/400"
...@@ -620,49 +642,61 @@ paths: ...@@ -620,49 +642,61 @@ paths:
405: 405:
$ref: "../responses/SOL005_resp.yaml#/responses/405" $ref: "../responses/SOL005_resp.yaml#/responses/405"
406: 406:
description: >
406 NOT ACCEPTABLE
If the "Accept" header does not contain at least one
name of a content type for which the NFVO can
provide a representation of the NSD, the NFVO
shall respond with this response code.
The "ProblemDetails" structure may be included
with the "detail" attribute providing more information
about the error.
$ref: "../responses/SOL005_resp.yaml#/responses/406" $ref: "../responses/SOL005_resp.yaml#/responses/406"
409: 409:
description: > description: >
409 CONFLICT 409 CONFLICT
Shall be returned upon the following error: Shall be returned upon the following error: The
The operation cannot be executed currently, due to a conflict with the state of the resource. operation cannot be executed currently, due to a
Typically, this is due to the fact "nsdOnboardingState" has a value different from ONBOARDED. conflict with the state of the resource.
The response body shall contain a ProblemDetails structure, in which the "detail" attribute shall Typically, this is due to the fact
convey more information about the error. "nsdOnboardingState" 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/SOL005_resp.yaml#/responses/409" $ref: "../responses/SOL005_resp.yaml#/responses/409"
416: 416:
description: > description: >
416 RANGE NOT SATISFIABLE 416 RANGE NOT SATISFIABLE
The byte range passed in the "Range" header did not match any available byte range in the NSD file The byte range passed in the "Range" header did
not match any available byte range in the NSD file
(e.g. "access after end of file"). (e.g. "access after end of file").
The response body may contain a ProblemDetails structure. The response body may contain a ProblemDetails
structure.
$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"
504:
$ref: "../responses/SOL005_resp.yaml#/responses/504"
put: put:
summary: Upload the content of a NSD. summary: Upload the content of a NSD.
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.
to be uploaded can be implemented as a single file or as a collection of The NSD to be uploaded can be implemented as a single file or as a collection of multiple files, as defined in
multiple files, as defined in clause 5.4.4.3.2 of GS NFV-SOL 005. clause 5.4.4.3.2. If the NSD is implemented in the form of multiple files, a ZIP file embedding these files shall be
If the NSD is implemented in the form of multiple files, a ZIP file embedding these uploaded. If the NSD is implemented as a single file, either that file or a ZIP file embedding that file shall be uploaded.
files shall be uploaded. ETSI
If the NSD is implemented as a single file, either that file or a ZIP file 47 ETSI GS NFV-SOL 005 V2.6.1 (2019-04)
embedding that file shall be uploaded. The "Content-Type" The "Content-Type" HTTP header in the PUT request shall be set accordingly based on the format selection of the
HTTP header in the PUT request shall be set accordingly based on the format NSD:
selection of the NSD. • If the NSD to be uploaded is a text file, the "Content-Type" header is set to "text/plain".
If the NSD to be uploaded is a text file, the "Content-Type" • If the NSD to be uploaded is a zip file, the "Content-Type" header is set to "application/zip".
header is set to "text/plain".
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,
and response codes."
parameters: parameters:
- name: Accept - name: Accept
description: > description: >
...@@ -680,13 +714,16 @@ paths: ...@@ -680,13 +714,16 @@ paths:
description: > description: >
202 ACCEPTED 202 ACCEPTED
The NSD content has been accepted for uploading, but the processing has not been completed. The NSD content has been accepted for uploading,
It is expected to take some time for processing (asynchronous mode). but the processing has not been completed. It is
expected to take some time for processing
(asynchronous mode).
The response body shall be empty. The response body shall be empty.
The client can track the uploading progress by
The client can track the uploading progress by receiving the "NsdOnBoardingNotification" and receiving the "NsdOnBoardingNotification" and
"NsdOnBoardingFailureNotification" from the NFVO or by reading the status of the individual "NsdOnBoardingFailureNotification" from the NFVO
NS descriptor resource using the GET method. or by reading the status of the individual NS descriptor
resource using the GET method.
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.
...@@ -711,7 +748,8 @@ paths: ...@@ -711,7 +748,8 @@ paths:
description: > description: >
204 NO CONTENT 204 NO CONTENT
The NSD content successfully uploaded and validated (synchronous mode). The NSD content successfully uploaded and
validated (synchronous mode).
The response body shall be empty. The response body shall be empty.
headers: headers:
WWW-Authenticate: WWW-Authenticate:
...@@ -744,15 +782,21 @@ paths: ...@@ -744,15 +782,21 @@ paths:
description: > description: >
409 CONFLICT 409 CONFLICT
Error: The operation cannot be executed currently, due to a conflict with the state of the resource. Error: The operation cannot be executed currently,
Typically, this is due to the fact that the NsdOnboardingState has a value other than CREATED. due to a conflict with the state of the resource.
The response body shall contain a ProblemDetails structure, in which the "detail" attribute shall Typically, this is due to the fact that the
convey more information about the error. NsdOnboardingState has a value other than
CREATED.
The response body shall contain a ProblemDetails
structure, in which the "detail" attribute shall convey
more information about the error.
$ref: "../responses/SOL005_resp.yaml#/responses/409" $ref: "../responses/SOL005_resp.yaml#/responses/409"
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"
504:
$ref: "../responses/SOL005_resp.yaml#/responses/504"
############################################################################### ###############################################################################
# PNF Descriptors # # PNF Descriptors #
...@@ -805,13 +849,14 @@ paths: ...@@ -805,13 +849,14 @@ paths:
description: > description: >
201 CREATED 201 CREATED
A PNF descriptor resource has been created successfully, as a new PNF descriptor resource. A PNF descriptor resource has been created
successfully, as a new PNF descriptor resource.
The response body shall contain a representation of The response body shall contain a representation of
the new PNF descriptor resource, as defined in the new PNF descriptor resource, as defined in
clause 5.5.2.5. clause 5.5.2.5.
The HTTP response shall include a "Location" HTTP The HTTP response shall include a "Location"
header that contains the resource URI of the new HTTP header that contains the resource URI of the
PNF descriptor resource. new PNF descriptor resource.
schema: schema:
$ref: "definitions/SOL005NSDescriptorManagement_def.yaml#/definitions/PnfdInfo" $ref: "definitions/SOL005NSDescriptorManagement_def.yaml#/definitions/PnfdInfo"
headers: headers:
...@@ -851,6 +896,8 @@ paths: ...@@ -851,6 +896,8 @@ paths:
$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"
504:
$ref: "../responses/SOL005_resp.yaml#/responses/504"
get: get:
summary: Query information about multiple PNF descriptor resources. summary: Query information about multiple PNF descriptor resources.
...@@ -914,13 +961,14 @@ paths: ...@@ -914,13 +961,14 @@ paths:
200 OK 200 OK
Information about zero or more PNF descriptors. Information about zero or more PNF descriptors.
The response body shall contain a representation of The response body shall contain in an array the
zero or more PNF descriptors, as defined in representations of zero or more PNF descriptors, as
clause 5.5.2.5 defined in clause 5.5.2.5.
If the NFVO supports alternative 2 (paging) according
If the NFVO supports alternative 2 (paging) according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 to clause 5.4.2.1 of ETSI GS NFV-SOL 013 for
for this resource, inclusion of the Link HTTP header in this response shall follow the provisions this resource, inclusion of the Link HTTP header in
in clause 5.4.2.3 of ETSI GS NFV-SOL 013. this response shall follow the provisions in clause
5.4.2.3 of ETSI GS NFV-SOL 013.
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.
...@@ -973,6 +1021,8 @@ paths: ...@@ -973,6 +1021,8 @@ paths:
$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"
504:
$ref: "../responses/SOL005_resp.yaml#/responses/504"
############################################################################### ###############################################################################
# Individual PNF Descriptor # # Individual PNF Descriptor #
...@@ -991,9 +1041,6 @@ paths: ...@@ -991,9 +1041,6 @@ paths:
summary: Read an individual PNFD resource. summary: Read an individual PNFD resource.
description: > description: >
The GET method reads information about an individual PNF descriptor. The GET method reads information about an individual PNF descriptor.
This method shall follow the provisions specified in the Tables 5.4.6.3.2-1
and 5.4.6.3.2-2 of GS NFV-SOL 005 for URI query parameters, request and
response data structures, and response codes.
parameters: parameters:
- name: Accept - name: Accept
in: header in: header
...@@ -1023,7 +1070,8 @@ paths: ...@@ -1023,7 +1070,8 @@ paths:
Information about the individual PNFD descriptor. Information about the individual PNFD descriptor.
The response body shall contain a representation of The response body shall contain a representation of
the individual PNF descriptor. the individual PNF descriptor, as defined in
clause 5.5.2.5.
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.
...@@ -1062,6 +1110,8 @@ paths: ...@@ -1062,6 +1110,8 @@ paths:
$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"
504:
$ref: "../responses/SOL005_resp.yaml#/responses/504"
patch: patch:
summary: Modify the user defined data of an individual PNF descriptor resource. summary: Modify the user defined data of an individual PNF descriptor resource.
...@@ -1096,7 +1146,8 @@ paths: ...@@ -1096,7 +1146,8 @@ paths:
200 OK