Commit d6f174f1 authored by Samir Medjiah's avatar Samir Medjiah
Browse files

SOL003: Consolidation of SOL003 interfaces

parent 1a59b664
Pipeline #915 passed with stage
in 0 seconds
......@@ -101,7 +101,7 @@ paths:
responses:
200:
description: >
OK
200 OK
Information about zero or more alarms was queried successfully.
The response body shall contain in an array the representations
......@@ -196,7 +196,7 @@ paths:
responses:
200:
description: >
OK
200 OK
Information about an individual alarm was read successfully.
The response body shall contain a representation of the individual
......@@ -270,7 +270,7 @@ paths:
responses:
200:
description: >
OK
200 OK
The request was accepted and completed. The response body shall
contain attribute modifications for an ‘Individual alarm’
......@@ -369,7 +369,7 @@ paths:
responses:
201:
description: >
Created
201 CREATED
The subscription was created successfully. The response body shall
contain a representation of the created subscription resource.
......@@ -472,7 +472,7 @@ paths:
responses:
200:
description: >
OK
200 OK
The list of subscriptions was queried successfully. The response
body shall contain in an array the representations of all active
......@@ -582,7 +582,7 @@ paths:
responses:
200:
description: >
OK
200 OK
The operation has completed successfully.
The response body shall contain a representation of the
......@@ -648,7 +648,7 @@ paths:
responses:
204:
description: >
No Content
204 NO CONTENT
The subscription resource was deleted successfully.
The response body shall be empty.
......
......@@ -83,7 +83,7 @@ paths:
responses:
204:
description: >
No Content
204 NO CONTENT
The notification was delivered successfully.
The response body shall be empty.
......@@ -137,7 +137,7 @@ paths:
responses:
204:
description: >
No Content
204 NO CONTENT
The notification endpoint was tested successfully.
The response body shall be empty.
......@@ -214,7 +214,7 @@ paths:
responses:
204:
description: >
No Content
204 NO CONTENT
The notification was delivered successfully.
The response body shall be empty.
......@@ -268,7 +268,7 @@ paths:
responses:
204:
description: >
No Content
204 NO CONTENT
The notification endpoint was tested successfully.
The response body shall be empty.
......@@ -345,7 +345,7 @@ paths:
responses:
204:
description: >
No Content
204 NO CONTENT
The notification was delivered successfully.
The response body shall be empty.
......@@ -399,7 +399,7 @@ paths:
responses:
204:
description: >
No Content
204 NO CONTENT
The notification endpoint was tested successfully.
The response body shall be empty.
......
......@@ -88,7 +88,7 @@ paths:
responses:
200:
description: >
OK
200 OK
Information about zero or more VNF indicators was queried
successfully.
......@@ -218,7 +218,7 @@ paths:
responses:
200:
description: >
OK
200 OK
Information about zero or more VNF indicators was queried
successfully.
......@@ -337,7 +337,7 @@ paths:
responses:
200:
description: >
OK
200 OK
The VNF indicator was read successfully.
The response body shall contain the representation of the VNF
......@@ -437,7 +437,7 @@ paths:
responses:
201:
description: >
Created
201 CREATED
The subscription was created successfully.
The response body shall contain a representation of the created
......@@ -548,7 +548,7 @@ paths:
responses:
200:
description: >
OK
200 OK
The list of subscriptions was queried successfully.
The response body shall contain in an array the representations
......@@ -662,7 +662,7 @@ paths:
responses:
200:
description: >
OK
200 OK
The operation has completed successfully.
The response body shall contain a representation of the
......@@ -735,7 +735,7 @@ paths:
responses:
204:
description: >
No Content
204 NO CONTENT
The subscription resource was deleted successfully.
The response body shall be empty.
......
......@@ -75,7 +75,7 @@ paths:
responses:
204:
description: >
No Content
204 NO CONTENT
The notification was delivered successfully.
The response body shall be empty.
......@@ -129,7 +129,7 @@ paths:
responses:
204:
description: >
No Content
204 NO CONTENT
The notification endpoint was tested successfully.
The response body shall be empty.
......
......@@ -1260,7 +1260,7 @@ paths:
responses:
200:
description: >
OK
200 OK
Status information for zero or more VNF lifecycle management
operation occurrences was queried successfully. The response body
......@@ -1365,7 +1365,7 @@ paths:
responses:
200:
description: >
OK
200 OK
Information about an individual VNF instance was queried
successfully. The response body shall contain status
......@@ -1607,7 +1607,7 @@ paths:
responses:
200:
description: >
OK
200 OK
The state of the VNF lifecycle management operation occurrence was
changed successfully. The response shall include a representation
......@@ -1812,7 +1812,7 @@ paths:
responses:
201:
description: >
Created
201 CREATED
The subscription was created successfully. The response body shall
contain a representation of the created subscription resource.
......@@ -1940,7 +1940,7 @@ paths:
responses:
200:
description: >
OK
200 OK
The list of subscriptions was queried successfully. The response
body shall contain the in an array representations of all active
......@@ -2064,7 +2064,7 @@ paths:
responses:
200:
description: >
OK
200 OK
The operation has completed successfully.
The response body shall contain a representation of the
......@@ -2130,7 +2130,7 @@ paths:
responses:
204:
description: >
No Content
204 NO CONTENT
The subscription resource was deleted successfully.
The response body shall be empty.
......
......@@ -79,7 +79,7 @@ paths:
responses:
204:
description: >
No Content
204 NO CONTENT
The notification was delivered successfully.
headers:
......@@ -155,7 +155,7 @@ paths:
responses:
204:
description: >
No Content
204 NO CONTENT
The notification was delivered successfully.
headers:
......@@ -231,7 +231,7 @@ paths:
responses:
204:
description: >
No Content
204 NO CONTENT
The notification was delivered successfully.
headers:
......
......@@ -93,7 +93,7 @@ paths:
responses:
201:
description: >
Created
201 CREATED
The grant was created successfully (synchronous mode).
A representation of the created "Individual grant" resource shall
......@@ -128,7 +128,7 @@ paths:
$ref: "definitions/VNFLifecycleOperationGranting_def.yaml#/definitions/Grant"
202:
description: >
Accepted
202 ACCEPTED
The request was accepted for processing, but the processing has
not been completed. It is expected to take some time to create
......@@ -239,7 +239,7 @@ paths:
responses:
200:
description: >
OK
200 OK
The grant was read successfully.
A representation of the "individual grant" resource shall be
......@@ -268,7 +268,7 @@ paths:
$ref: "definitions/VNFLifecycleOperationGranting_def.yaml#/definitions/Grant"
202:
description: >
Accepted
202 ACCEPTED
The process of creating the grant is ongoing, no grant is
available yet.
......
......@@ -134,7 +134,7 @@ paths:
responses:
200:
description: >
OK
200 OK
Information about zero or more VNF packages was queried successfully.
The response body shall contain in an array the VNF package info
......@@ -236,7 +236,7 @@ paths:
responses:
200:
description: >
OK
200 OK
Information of the selected VNF packages.
headers:
......@@ -351,7 +351,7 @@ paths:
responses:
200:
description: >
OK
200 OK
On success, the content of the VNFD is returned.
The payload body shall contain a copy of the file representing the
......@@ -460,7 +460,7 @@ paths:
responses:
200:
description: >
OK
200 OK
On success, a copy of the VNF package file is returned.
The response body shall include a copy of the VNF package file.
......@@ -489,7 +489,7 @@ paths:
minimum: 1
206:
description: >
Partial Content
206 PARTIAL CONTENT
On success, if the NFVO supports range requests, a single
consecutive byte range from the content of the VNF package file is
......@@ -610,7 +610,7 @@ paths:
responses:
200:
description: >
OK
200 OK
On success, the content of the artifact is returned.
The payload body shall contain a copy of the artifact file from
......@@ -646,7 +646,7 @@ paths:
minimum: 1
206:
description: >
Partial Content
206 PARTIAL CONTENT
On success, if the NFVO supports range requests, a single
consecutive byte range from the content of the VNF package file is
......@@ -761,7 +761,7 @@ paths:
responses:
201:
description: >
Created
201 CREATED
Representation of the created subscription resource.
The HTTP response shall include a "Location" HTTP header that
......@@ -865,7 +865,7 @@ paths:
responses:
200:
description: >
OK
200 OK
The list of subscriptions was queried successfully.
The representations body shall contain in an array the representations
......@@ -969,7 +969,7 @@ paths:
responses:
200:
description: >
OK
200 OK
Representation of the subscription resource.
headers:
......@@ -1035,7 +1035,7 @@ paths:
responses:
204:
description: >
No Content
204 NO CONTENT
The subscription resource was deleted successfully.
headers:
......
......@@ -80,7 +80,7 @@ paths:
responses:
204:
description: >
No Content
204 NO CONTENT
The notification was delivered successfully.
headers:
......@@ -133,7 +133,7 @@ paths:
responses:
204:
description: >
No Content
204 NO CONTENT
The notification endpoint was tested successfully.
The response body shall be empty.
......@@ -208,7 +208,7 @@ paths:
responses:
204:
description: >
No Content
204 NO CONTENT
The notification was delivered successfully.
headers:
......@@ -261,7 +261,7 @@ paths:
responses:
204:
description: >
No Content
204 NO CONTENT
The notification endpoint was tested successfully.
The response body shall be empty.
......
......@@ -93,7 +93,7 @@ paths:
responses:
201:
description: >
Created
201 CREATED
The PM job was created successfully. The response body shall
contain a representation of the created PM job resource.
......@@ -215,7 +215,7 @@ paths:
responses:
200:
description: >
OK
200 OK
Information about zero or more PM jobs was queried successfully.
The response body shall contain in an array representations of
......@@ -316,7 +316,7 @@ paths:
responses:
200:
description: >
OK
200 OK
Information about an individual PM job was queried successfully.
The response body shall contain a representation of the PM job
......@@ -382,7 +382,7 @@ paths:
responses:
204:
description: >
No Content
204 NO CONTENT
The PM job was deleted successfully.
The response body shall be empty.
......@@ -461,7 +461,7 @@ paths:
responses:
200:
description: >
OK
200 OK
Information of an individual performance report was read
successfully.
......@@ -554,7 +554,7 @@ paths:
responses:
201:
description: >
Created
201 CREATED
A threshold was created successfully. The response body shall
contain a representation of the created threshold resource.
......@@ -655,7 +655,7 @@ paths:
responses:
200:
description: >
OK
200 OK
Information about zero or more thresholds was queried
successfully.
......@@ -761,7 +761,7 @@ paths:
responses:
200:
description: >
OK
200 OK
Information about an individual threshold was queried
successfully. The response body shall contain a
......@@ -827,7 +827,7 @@ paths:
responses:
204:
description: >
No Content
204 NO CONTENT
The threshold was deleted successfully.
The response body shall be empty.
......@@ -919,7 +919,7 @@ paths:
responses:
201:
description: >
Created
201 CREATED
The subscription was created successfully. A representation of the
created subscription resource shall be returned in the response
......@@ -1021,7 +1021,7 @@ paths:
responses:
200:
description: >
OK
200 OK
The list of subscriptions was queried successfully.
The response body shall contain in an array the representations
......@@ -1124,7 +1124,7 @@ paths:
responses:
200:
description: >
OK
200 OK
The subscription was read successfully. The response body shall
contain a representation of the subscription resource.
......@@ -1189,7 +1189,7 @@ paths:
responses:
204:
description: >
No Content
204 NO CONTENT
The subscription resource was deleted successfully.
The response body shall be empty.
......
# Copyright (c) ETSI 2017.
# https://forge.etsi.org/etsi-forge-copyright-notice.txt
definitions:
......@@ -82,7 +82,7 @@ paths:
responses:
204:
description: >
No Content
204 NO CONTENT
The notification was delivered successfully.
headers:
......@@ -135,7 +135,7 @@ paths:
responses:
204:
description: >
No Content
204 NO CONTENT
The notification endpoint was tested successfully.
headers:
......@@ -210,7 +210,7 @@ paths:
responses:
204:
description: >
No Content
204 NO CONTENT
The notification was delivered successfully.
headers:
......@@ -263,7 +263,7 @@ paths:
responses:
204:
description: >
No Content
204 NO CONTENT
The notification endpoint was tested successfully.
headers:
......
......@@ -103,7 +103,7 @@ paths:
responses:
201:
description: >
Created
201 CREATED
Representation of the created subscription resource.
The HTTP response shall include a "Location" HTTP header that
......@@ -195,7 +195,7 @@ paths:
responses:
200:
description: >
OK
200 OK
The list of subscriptions was queried successfully.
The representations body shall contain in an array the representations
......