Commit d803cf7f authored by bernini's avatar bernini

updates to SOL005 VNF Pckg mgmt

parent 728f153c
Pipeline #1285 passed with stage
in 0 seconds
......@@ -101,9 +101,7 @@ definitions:
$ref: "../../definitions/SOL005_def.yaml#/definitions/Link"
vnfd:
description: >
Link to the VNFD resource. This link shall
be present after the VNF package content
is on-boarded.
Link to the VNFD resource.
$ref: "../../definitions/SOL005_def.yaml#/definitions/Link"
packageContent:
description: >
......@@ -121,8 +119,10 @@ definitions:
properties:
artifactPath:
description: >
Path in the VNF package, which identifies the artifact
and also allows to access a copy of the artifact.
Path in the VNF package, which identifies the artifact and also allows to access a copy of the artifact.
The value of this attribute shall start with the name of the first segment in the path,
i.e. it shall not be prefixed by path separator characters such as "." and "/".
EXAMPLE: foo/bar/run.sh
$ref: "../../definitions/SOL005_def.yaml#/definitions/String"
checksum:
description: >
......@@ -410,7 +410,7 @@ definitions:
description: >
Authentication parameters to conFigure the use of
authorization when sending notifications corresponding
to this subscription, as defined in clause 4.5.3.4.
to this subscription, as defined in clause 8.3.4 of ETSI GS NFV SOL 013.
This attribute shall only be present if the subscriber
requires authorization of notifications.
$ref: "../../definitions/SOL005_def.yaml#/definitions/SubscriptionAuthentication"
......
......@@ -30,10 +30,8 @@ paths:
post:
summary: Notify about VNF package onboarding or change
description: >
The POST method delivers a notification from the server to the client.
This method shall follow the provisions specified in the
Tables 9.4.10.3.1-1 and 9.4.10.3.1-2 for URI query parameters,
request and response data structures, and response codes.
The POST method delivers a notification from the API producer to an API consumer.
The API consumer shall have previously created an "individual subscription resource" with a matching filter.
parameters:
- name: VnfPackageOnboardingNotification
description: >
......@@ -74,7 +72,7 @@ paths:
description: >
204 No Content
The notification was delivered successfully.
Shall be returned when the notification has been delivered successfully.
headers:
WWW-Authenticate:
type: string
......@@ -101,6 +99,71 @@ paths:
503:
$ref: "../responses/SOL005_resp.yaml#/responses/503"
get:
summary: Test the notification endpoint.
description: >
The GET method allows the server to test the notification endpoint that is provided by
the client, e.g. during subscription.
parameters:
- name: Accept
description: >
Content-Types that are acceptable for the response.
Reference: IETF RFC 7231
in: header
required: true
type: string
- name: Authorization
description: >
The authorization token for the request.
Reference: IETF RFC 7235
in: header
required: false
type: string
- name: Version
description: >
Version of the API requested to use when responding to this request.
in: header
required: true
type: string
responses:
204:
description: >
204 No Content
Shall be returned to indicate that the notification endpoint has been tested successfully.
The response body shall be empty.
headers:
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.
maximum: 1
minimum: 0
Version:
description: >
Version of the API used in the response.
type: string
maximum: 1
minimum: 1
400:
$ref: "../responses/SOL005_resp.yaml#/responses/400"
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"
500:
$ref: "../responses/SOL005_resp.yaml#/responses/500"
503:
$ref: "../responses/SOL005_resp.yaml#/responses/503"
'/URI_is_provided_by_the_client_when_creating_the_subscription-VnfPackageChangeNotification':
post:
summary: Notify about VNF package onboarding or change
......@@ -149,7 +212,8 @@ paths:
description: >
204 No Content
The notification was delivered successfully.
Shall be returned to indicate that the notification endpoint has been tested successfully.
The response body shall be empty.
headers:
WWW-Authenticate:
type: string
......@@ -181,8 +245,6 @@ paths:
description: >
The GET method allows the server to test the notification endpoint that is provided by the client, e.g. during
subscription.
This method shall follow the provisions specified in the Tables 9.4.10.3.2-1 and 9.4.10.3.2-2 for URI query parameters,
request and response data structures, and response codes.
parameters:
- name: Accept
description: >
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment