Skip to content

GitLab

Commit 800cfa4b authored by moscatelli's avatar moscatelli
Browse files

SOL005: Fix in VNF Pkg mgmt interface references

parent fcc3b122
Pipeline #803 passed with stage
in 0 seconds
Hide whitespace changes
Inline Side-by-side
Showing with 12 additions and 189 deletions
src/SOL005/NSDManagementNotification/definitions/SOL005NSDescriptorManagementNotification_def.yaml
View file @ 800cfa4b
......@@ -20,7 +20,7 @@ definitions:
Discriminator for the different notification types. Shall be
set to "NsdOnboardingNotification" for this notification type.
subscriptionId:
$ref: "../../NSDManagement/SOL005_def.yaml#/definitions/Identifier"
$ref: "../../NSDManagement/definitions/SOL005_def.yaml#/definitions/Identifier"
timeStamp:
description: >
Date-time of the generation of the notification.
......
src/SOL005/VNFPackageManagement/VNFPackageManagement.yaml
View file @ 800cfa4b
......@@ -124,7 +124,7 @@ paths:
items:
properties:
VnfPkgInfo:
$ref: "definitions/SOL005VNFPMManagement_def.yaml#/definitions/VnfPkgInfo"
$ref: "definitions/SOL005VNFPackageManagement_def.yaml#/definitions/VnfPkgInfo"
400:
$ref: "responses/SOL005_resp.yaml#/responses/400"
401:
......@@ -179,7 +179,7 @@ paths:
- "CreateVnfPkgInfoRequest"
properties:
CreateVnfPkgInfoRequest:
$ref: "definitions/SOL005VNFPMManagement_def.yaml#/definitions/CreateVnfPkgInfoRequest"
$ref: "definitions/SOL005VNFPackageManagement_def.yaml#/definitions/CreateVnfPkgInfoRequest"
description: >
IndividualVNF package resource creation parameters, as defined in clause 9.5.2.2
......@@ -198,7 +198,7 @@ paths:
schema:
properties:
VnfPkgInfo:
$ref: "definitions/SOL005VNFPMManagement_def.yaml#/definitions/VnfPkgInfo"
$ref: "definitions/SOL005VNFPackageManagement_def.yaml#/definitions/VnfPkgInfo"
headers:
Content-Type:
type: "string"
......@@ -257,7 +257,7 @@ paths:
type: "object"
properties:
VnfPkgInfo:
$ref: "definitions/SOL005VNFPMManagement_def.yaml#/definitions/VnfPkgInfo"
$ref: "definitions/SOL005VNFPackageManagement_def.yaml#/definitions/VnfPkgInfo"
headers:
Content-Type:
type: "string"
......@@ -347,7 +347,7 @@ paths:
- "VnfPkgInfoModifications"
properties:
VnfPkgInfoModifications:
$ref: "definitions/SOL005VNFPMManagement_def.yaml#/definitions/VnfPkgInfoModifications"
$ref: "definitions/SOL005VNFPackageManagement_def.yaml#/definitions/VnfPkgInfoModifications"
description: >
Parameters for VNF package information modifications.
- name: Authorization
......@@ -390,7 +390,7 @@ paths:
schema:
properties:
VnfPkgInfoModifications:
$ref: "definitions/SOL005VNFPMManagement_def.yaml#/definitions/VnfPkgInfoModifications"
$ref: "definitions/SOL005VNFPackageManagement_def.yaml#/definitions/VnfPkgInfoModifications"
409:
$ref: "responses/VNFPackageManagement_resp.yaml#/responses/409"
400:
......@@ -723,7 +723,7 @@ paths:
- "UploadVnfPkgFromUriRequest"
properties:
UploadVnfPkgFromUriRequest:
$ref: "definitions/SOL005VNFPMManagement_def.yaml#/definitions/UploadVnfPkgFromUriRequest"
$ref: "definitions/SOL005VNFPackageManagement_def.yaml#/definitions/UploadVnfPkgFromUriRequest"
description: >
The payload body contains the address information based on
which the NFVO can obtain the content of the VNF package.
......@@ -935,7 +935,7 @@ paths:
- "PkgmSubscriptionRequest"
properties:
PkgmSubscriptionRequest:
$ref: "definitions/SOL005VNFPMManagement_def.yaml#/definitions/PkgmSubscriptionRequest"
$ref: "definitions/SOL005VNFPackageManagement_def.yaml#/definitions/PkgmSubscriptionRequest"
description: >
Representation of the created subscription resource.
The HTTP response shall include a "Location" HTTP header that
......@@ -968,7 +968,7 @@ paths:
items:
properties:
PkgmSubscription:
$ref: "definitions/SOL005VNFPMManagement_def.yaml#/definitions/PkgmSubscription"
$ref: "definitions/SOL005VNFPackageManagement_def.yaml#/definitions/PkgmSubscription"
303:
$ref: "responses/SOL005_resp.yaml#/responses/303"
400:
......@@ -1047,7 +1047,7 @@ paths:
items:
properties:
PkgmSubscription:
$ref: "definitions/SOL005VNFPMManagement_def.yaml#/definitions/PkgmSubscription"
$ref: "definitions/SOL005VNFPackageManagement_def.yaml#/definitions/PkgmSubscription"
400:
$ref: "responses/SOL005_resp.yaml#/responses/400"
401:
......@@ -1126,7 +1126,7 @@ paths:
schema:
properties:
PkgmSubscription:
$ref: "definitions/SOL005VNFPMManagement_def.yaml#/definitions/PkgmSubscription"
$ref: "definitions/SOL005VNFPackageManagement_def.yaml#/definitions/PkgmSubscription"
400:
$ref: "responses/SOL005_resp.yaml#/responses/400"
401:
......@@ -1188,182 +1188,5 @@ paths:
$ref: "responses/SOL005_resp.yaml#/responses/416"
500:
$ref: "responses/SOL005_resp.yaml#/responses/500"
503:
$ref: "responses/SOL005_resp.yaml#/responses/503"
##################################################################################
# Notification endpoint #
# Dummy URI is used for testing. #
# In real, resource URI is provided by the client when creating the subscription.#
##################################################################################
'/URI_is_provided_by_the_client_when_creating_the_subscription-VnfPackageOnboardingNotification':
#ETSI GS NFV-SOL 005 V2.4.1 location: 9.4.10
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.
parameters:
- name: VnfPackageOnboardingNotification
description: >
A notification about on-boarding of a VNF package.
in: body
required: true
schema:
properties:
VnfPackageOnboardingNotification:
$ref: "definitions/SOL005VNFPMManagement_def.yaml#/definitions/VnfPackageOnboardingNotification"
- 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: Content-Type
description: >
The MIME type of the body of the request.
Reference: IETF RFC 7231
in: header
required: true
type: string
responses:
204:
description: >
204 No Content
The notification was delivered successfully.
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
400:
$ref: "responses/SOL005_resp.yaml#/responses/400"
401:
$ref: "responses/SOL005_resp.yaml#/responses/401"
403:
$ref: "responses/SOL005_resp.yaml#/responses/403"
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':
#ETSI GS NFV-SOL 005 V2.4.1 location: 9.4.10
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.
parameters:
- name: VnfPackageChangeNotification
description: >
A notification about changes of status in a VNF package.
in: body
required: true
schema:
properties:
VnfPackageChangeNotification:
$ref: "definitions/SOL005VNFPMManagement_def.yaml#/definitions/VnfPackageChangeNotification"
- 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: Content-Type
description: >
The MIME type of the body of the request.
Reference: IETF RFC 7231
in: header
required: true
type: string
responses:
204:
description: >
204 No Content
The notification was delivered successfully.
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
400:
$ref: "responses/SOL005_resp.yaml#/responses/400"
401:
$ref: "responses/SOL005_resp.yaml#/responses/401"
403:
$ref: "responses/SOL005_resp.yaml#/responses/403"
500:
$ref: "responses/SOL005_resp.yaml#/responses/500"
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.
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: >
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
responses:
204:
description: >
204 No Content
The notification endpoint was tested successfully.
The response body shall be empty.
400:
$ref: "responses/SOL005_resp.yaml#/responses/400"
401:
$ref: "responses/SOL005_resp.yaml#/responses/401"
403:
$ref: "responses/SOL005_resp.yaml#/responses/403"
500:
$ref: "responses/SOL005_resp.yaml#/responses/500"
503:
$ref: "responses/SOL005_resp.yaml#/responses/503"
\ No newline at end of file
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