From db5555aa6d9fd5a1d754e51825788dd04f571551 Mon Sep 17 00:00:00 2001 From: Giacomo Bernini Date: Thu, 23 Jan 2020 18:02:17 +0100 Subject: [PATCH 001/260] updated README - devel phase --- Readme.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Readme.md b/Readme.md index 5f2370de..354a209e 100644 --- a/Readme.md +++ b/Readme.md @@ -8,7 +8,7 @@ The APIs described in this repository are defined for the following reference po * `Or-Vnfm` * `Ve-vnfm` -**IMPORTANT: In case of discrepancies the published ETSI Group Specification takes precedence.** +**IMPORTANT: These [OpenAPI](https://www.openapis.org/) specifications are in development phase. In case of discrepancies the published ETSI Group Specification takes precedence.** More information at [NFV Solutions wiki](https://nfvwiki.etsi.org/index.php?title=NFV_Solutions). -- GitLab From 334a1f3d5be489e2c99ef3a7587b0f5ae833754f Mon Sep 17 00:00:00 2001 From: Francesca Moscatelli Date: Wed, 5 Feb 2020 10:20:05 +0100 Subject: [PATCH 002/260] SOL003_001: APIs' version updated --- src/SOL003/VNFFaultManagement/VNFFaultManagement.yaml | 2 +- src/SOL003/VNFIndicator/VNFIndicator.yaml | 2 +- src/SOL003/VNFLifecycleManagement/VNFLifecycleManagement.yaml | 2 +- src/SOL003/VNFPackageManagement/VNFPackageManagement.yaml | 2 +- .../VNFPerformanceManagement/VNFPerformanceManagement.yaml | 2 +- .../VirtualisedResourcesQuotaAvailableNotification.yaml | 2 +- 6 files changed, 6 insertions(+), 6 deletions(-) diff --git a/src/SOL003/VNFFaultManagement/VNFFaultManagement.yaml b/src/SOL003/VNFFaultManagement/VNFFaultManagement.yaml index b5b3ec17..2d3c48a6 100644 --- a/src/SOL003/VNFFaultManagement/VNFFaultManagement.yaml +++ b/src/SOL003/VNFFaultManagement/VNFFaultManagement.yaml @@ -1,7 +1,7 @@ swagger: "2.0" info: - version: "1.2.0-impl:etsi.org:ETSI_NFV_OpenAPI:1" + version: "1.3.0-impl:etsi.org:ETSI_NFV_OpenAPI:1" title: SOL003 - VNF Fault Management interface description: > SOL003 - VNF Fault Management interface diff --git a/src/SOL003/VNFIndicator/VNFIndicator.yaml b/src/SOL003/VNFIndicator/VNFIndicator.yaml index 81b9f87e..4c4ba478 100644 --- a/src/SOL003/VNFIndicator/VNFIndicator.yaml +++ b/src/SOL003/VNFIndicator/VNFIndicator.yaml @@ -1,7 +1,7 @@ swagger: "2.0" info: - version: "1.2.0-impl:etsi.org:ETSI_NFV_OpenAPI:1" + version: "1.2.1-impl:etsi.org:ETSI_NFV_OpenAPI:1" title: SOL003 - VNF Indicator interface description: > SOL003 - VNF Indicator interface diff --git a/src/SOL003/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL003/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 3d1a37f7..2854c0e3 100644 --- a/src/SOL003/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL003/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -1,7 +1,7 @@ swagger: "2.0" info: - version: "1.3.0-impl:etsi.org:ETSI_NFV_OpenAPI:1" + version: "1.4.0-impl:etsi.org:ETSI_NFV_OpenAPI:1" title: SOL003 - VNF Lifecycle Management interface description: > SOL003 - VNF Lifecycle Management interface definition diff --git a/src/SOL003/VNFPackageManagement/VNFPackageManagement.yaml b/src/SOL003/VNFPackageManagement/VNFPackageManagement.yaml index 63fc3ce8..2f9817f4 100644 --- a/src/SOL003/VNFPackageManagement/VNFPackageManagement.yaml +++ b/src/SOL003/VNFPackageManagement/VNFPackageManagement.yaml @@ -1,7 +1,7 @@ swagger: "2.0" info: - version: "1.3.0-impl:etsi.org:ETSI_NFV_OpenAPI:1" + version: "2.0.0-impl:etsi.org:ETSI_NFV_OpenAPI:1" title: SOL003 - VNF Package Management interface description: > SOL003 - VNF Package Management interface diff --git a/src/SOL003/VNFPerformanceManagement/VNFPerformanceManagement.yaml b/src/SOL003/VNFPerformanceManagement/VNFPerformanceManagement.yaml index 390c3706..02510fbe 100644 --- a/src/SOL003/VNFPerformanceManagement/VNFPerformanceManagement.yaml +++ b/src/SOL003/VNFPerformanceManagement/VNFPerformanceManagement.yaml @@ -1,7 +1,7 @@ swagger: "2.0" info: - version: "1.2.0-impl:etsi.org:ETSI_NFV_OpenAPI:1" + version: "2.0.0-impl:etsi.org:ETSI_NFV_OpenAPI:1" title: SOL003 - VNF Performance Management interface description: > SOL003 - VNF Performance Management interface diff --git a/src/SOL003/VirtualisedResourcesQuotaAvailableNotification/VirtualisedResourcesQuotaAvailableNotification.yaml b/src/SOL003/VirtualisedResourcesQuotaAvailableNotification/VirtualisedResourcesQuotaAvailableNotification.yaml index 8acca4d0..fae2c745 100644 --- a/src/SOL003/VirtualisedResourcesQuotaAvailableNotification/VirtualisedResourcesQuotaAvailableNotification.yaml +++ b/src/SOL003/VirtualisedResourcesQuotaAvailableNotification/VirtualisedResourcesQuotaAvailableNotification.yaml @@ -1,7 +1,7 @@ swagger: "2.0" info: - version: "1.2.0-impl:etsi.org:ETSI_NFV_OpenAPI:1" + version: "1.2.1-impl:etsi.org:ETSI_NFV_OpenAPI:1" title: SOL003 - Virtualised Resources Quota Available Notification interface description: > SOL003 - Virtualised Resources Quota Available Notification interface -- GitLab From 5fd99143ca88fda85798656a8c7bdef7097d38c6 Mon Sep 17 00:00:00 2001 From: Francesca Moscatelli Date: Wed, 5 Feb 2020 10:29:28 +0100 Subject: [PATCH 003/260] SOL003_002: VimConnectionInfo updated --- src/definitions/SOL002SOL003_def.yaml | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/src/definitions/SOL002SOL003_def.yaml b/src/definitions/SOL002SOL003_def.yaml index c1827f37..4e72e507 100644 --- a/src/definitions/SOL002SOL003_def.yaml +++ b/src/definitions/SOL002SOL003_def.yaml @@ -243,6 +243,20 @@ definitions: body, sensitive attributes that are children of this attribute (such as passwords) shall be present if they have not been provisioned out of band. + + If applicable, this attribute also provides information about the + resourceGroupIds that are accessible using a particular set of credentials. + See definition of "resourceGroupId" in clause 9.5.3.3. + + Once the connectivity between VNFM and VIM is provided through a secure + connection over HTTP Secure (HTTP over SSL/TLS), and the connection might + also be established through a VPN (for example TLS-based VPN tunnelling) + for site-to-site connection, the "accessInfo" JSON data structure, + and the sensitive data related information ("username"/"password" as required + properties for authentication purpose), will be transmitted as plain text through + a TLS tunnel without additional encoding/encryption before transmitting it, + making the sensitive data visible to the endpoint. The base64 encoded certificates + are only used by the VNFM to verify the authenticity of the interface endpoint of the VIM. $ref: "#/definitions/KeyValuePairs" extra: description: > -- GitLab From 32cc52cb9786c83dd170a6509f09e32c843623ba Mon Sep 17 00:00:00 2001 From: Francesca Moscatelli Date: Wed, 5 Feb 2020 10:57:47 +0100 Subject: [PATCH 004/260] SOL003_023: Terminate description updated --- .../VNFLifecycleManagement.yaml | 157 +++++++++--------- 1 file changed, 79 insertions(+), 78 deletions(-) diff --git a/src/SOL003/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL003/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 2854c0e3..dad21dd1 100644 --- a/src/SOL003/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL003/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -25,8 +25,8 @@ info: url: https://forge.etsi.org/etsi-forge-copyright-notice.txt externalDocs: - description: ETSI GS NFV-SOL 003 V2.6.1 - url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.06.01_60/gs_NFV-SOL003v020601p.pdf + description: ETSI GS NFV-SOL 003 V2.7.1 + url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.07.01_60/gs_NFV-SOL003v020701p.pdf basePath: "/vnflcm/v1" @@ -491,12 +491,12 @@ paths: 406: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" 409: - description: > - 409 CONFLICT + #description: > + #409 CONFLICT - Shall be returned upon the following error: The operation cannot be executed currently, - due to a conflict with the state of the "Individual VNF instance" resource. - Typically, this is due to the fact that another LCM operation is ongoing. + #Shall be returned upon the following error: The operation cannot be executed currently, + #due to a conflict with the state of the "Individual VNF instance" resource. + #Typically, this is due to the fact that another LCM operation is ongoing. $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" 412: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/412" @@ -566,12 +566,12 @@ paths: 406: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" 409: - description: > - 409 CONFLICT + #description: > + #409 CONFLICT - Shall be returned upon the following error: The operation cannot be executed currently, - due to a conflict with the state of the resource. - Typically, this is due to the fact that the "Individual VNF instance" resource is in INSTANTIATED state. + #Shall be returned upon the following error: The operation cannot be executed currently, + #due to a conflict with the state of the resource. + #Typically, this is due to the fact that the "Individual VNF instance" resource is in INSTANTIATED state. $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" 412: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/412" @@ -686,14 +686,14 @@ paths: 406: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" 409: - description: > - 409 CONFLICT - - Shall be returned upon the following error: The operation cannot be executed currently, - due to a conflict with the state of the resource. - Typically, this is due to the fact that the "Individual VNF instance" resource is in INSTANTIATED state, - or that a required child attribute of the "extensions" attribute has not been set. - Those attributes are marked as "required" in the VNFD. + #description: > + #409 CONFLICT + + #Shall be returned upon the following error: The operation cannot be executed currently, + #due to a conflict with the state of the resource. + #Typically, this is due to the fact that the "Individual VNF instance" resource is in INSTANTIATED state, + #or that a required child attribute of the "extensions" attribute has not been set. + #Those attributes are marked as "required" in the VNFD. $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" 416: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" @@ -804,31 +804,31 @@ paths: 403: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/403" 404: - description: > - 404 NOT FOUND - - Shall be returned upon the following error: The API producer did not find a current representation - for the target resource or is not willing to disclose that one exists. - The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013, - including rules for the presence of the response body. - Specifically in case of this task resource, the response code 404 shall also returned if - the task is not supported for the VNF instance represented by the parent resource, which means that the - task resource consequently does not exist. + #description: > + #404 NOT FOUND + + #Shall be returned upon the following error: The API producer did not find a current representation + #for the target resource or is not willing to disclose that one exists. + #The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013, + #including rules for the presence of the response body. + #Specifically in case of this task resource, the response code 404 shall also returned if + #the task is not supported for the VNF instance represented by the parent resource, which means that the + #task resource consequently does not exist. $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/404" 405: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" 406: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" 409: - description: > - 409 CONFLICT - - Shall be returned upon the following error: The operation cannot be executed currently, - due to a conflict with the state of the resource. - Typically, this is due to the fact that the "Individual VNF instance" resource is in - NOT_INSTANTIATED state, or that another lifecycle management operation is ongoing, or that - a required child attribute of the "extensions" attribute has not been set. - Those attributes are marked as "required" in the VNFD. + #description: > + #409 CONFLICT + + #Shall be returned upon the following error: The operation cannot be executed currently, + #due to a conflict with the state of the resource. + #Typically, this is due to the fact that the "Individual VNF instance" resource is in + #NOT_INSTANTIATED state, or that another lifecycle management operation is ongoing, or that + #a required child attribute of the "extensions" attribute has not been set. + #Those attributes are marked as "required" in the VNFD. $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" 500: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500" @@ -937,31 +937,31 @@ paths: 403: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/403" 404: - description: > - 404 NOT FOUND - - Shall be returned upon the following error: The API producer did not find a current representation - for the target resource or is not willing to disclose that one exists. - The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013, - including rules for the presence of the response body. - Specifically in case of this task resource, the response code 404 shall also returned if the task - is not supported for the VNF instance represented by the parent resource, which means that the task resource - consequently does not exist. + #description: > + #404 NOT FOUND + + #Shall be returned upon the following error: The API producer did not find a current representation + #for the target resource or is not willing to disclose that one exists. + #The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013, + #including rules for the presence of the response body. + #Specifically in case of this task resource, the response code 404 shall also returned if the task + #is not supported for the VNF instance represented by the parent resource, which means that the task resource + #consequently does not exist. $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/404" 405: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" 406: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" 409: - description: > - 409 CONFLICT - - Shall be returned upon the following error: The operation cannot be executed currently, - due to a conflict with the state of the resource. - Typically, this is due to the fact that the VNF instance resource is in NOT_INSTANTIATED state, - that another lifecycle management operation is ongoing, or that a required child attribute of - the "extensions" attribute has not been set. - Those attributes are marked as "required" in the VNFD. + #description: > + #409 CONFLICT + + #Shall be returned upon the following error: The operation cannot be executed currently, + #due to a conflict with the state of the resource. + #Typically, this is due to the fact that the VNF instance resource is in NOT_INSTANTIATED state, + #that another lifecycle management operation is ongoing, or that a required child attribute of + #the "extensions" attribute has not been set. + #Those attributes are marked as "required" in the VNFD. $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" 500: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500" @@ -1070,31 +1070,31 @@ paths: 403: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/403" 404: - description: > - 404 NOT FOUND - - Shall be returned upon the following error: The API producer did not find a current representation - for the target resource or is not willing to disclose that one exists. - The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013, - including rules for the presence of the response body. - Specifically in case of this task resource, the response code 404 shall also returned if the task - is not supported for the VNF instance represented by the parent resource, which means that the task resource - consequently does not exist. + #description: > + #404 NOT FOUND + + #Shall be returned upon the following error: The API producer did not find a current representation + #for the target resource or is not willing to disclose that one exists. + #The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013, + #including rules for the presence of the response body. + #Specifically in case of this task resource, the response code 404 shall also returned if the task + #is not supported for the VNF instance represented by the parent resource, which means that the task resource + #consequently does not exist. $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/404" 405: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" 406: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" 409: - description: > - 409 CONFLICT - - Shall be returned upon the following error: The operation cannot be executed currently, - due to a conflict with the state of the resource. - Typically, this is due to the fact that the VNF instance resource is in NOT_INSTANTIATED state, - that another lifecycle management operation is ongoing, or that a required child attribute of - the "extensions" attribute has not been set. - Those attributes are marked as "required" in the VNFD. + #description: > + #409 CONFLICT + + #Shall be returned upon the following error: The operation cannot be executed currently, + #due to a conflict with the state of the resource. + #Typically, this is due to the fact that the VNF instance resource is in NOT_INSTANTIATED state, + #that another lifecycle management operation is ongoing, or that a required child attribute of + #the "extensions" attribute has not been set. + #Those attributes are marked as "required" in the VNFD. $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" 500: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500" @@ -1122,7 +1122,8 @@ paths: post: description: > Terminate VNF. - The POST method terminates a VNF instance. + The POST method triggers the VNFM to terminate a VNF instance and to request to the VIM + the release of its used virtualised resources. This method shall follow the provisions specified in the tables 5.4.8.3.1-1 and 5.4.8.3.1-2 for URI query parameters, request and response data structures, and response codes. The steps and conditions that apply as the result of successfully executing this method -- GitLab From 2f63a037f378b7ea236038a906c851d94eeba54c Mon Sep 17 00:00:00 2001 From: Francesca Moscatelli Date: Wed, 5 Feb 2020 11:10:38 +0100 Subject: [PATCH 005/260] SOL003_031/033: GET description updated --- .../VNFLifecycleManagement.yaml | 102 +++++++++--------- 1 file changed, 51 insertions(+), 51 deletions(-) diff --git a/src/SOL003/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL003/VNFLifecycleManagement/VNFLifecycleManagement.yaml index dad21dd1..bcc7ef4e 100644 --- a/src/SOL003/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL003/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -1209,15 +1209,15 @@ paths: 406: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" 409: - description: > - 409 CONFLICT + #description: > + #409 CONFLICT - Shall be returned upon the following error: The operation cannot be executed currently, - due to a conflict with the state of the resource. - Typically, this is due to the fact that the VNF instance resource is in NOT_INSTANTIATED state, - that another lifecycle management operation is ongoing, or that a required child attribute of - the "extensions" attribute has not been set. - Those attributes are marked as "required" in the VNFD. + #Shall be returned upon the following error: The operation cannot be executed currently, + #due to a conflict with the state of the resource. + #Typically, this is due to the fact that the VNF instance resource is in NOT_INSTANTIATED state, + #that another lifecycle management operation is ongoing, or that a required child attribute of + #the "extensions" attribute has not been set. + #Those attributes are marked as "required" in the VNFD. $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" 500: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500" @@ -1322,31 +1322,31 @@ paths: 403: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/403" 404: - description: > - 404 NOT FOUND + #description: > + #404 NOT FOUND - Shall be returned upon the following error: The API producer did not find a current representation - for the target resource or is not willing to disclose that one exists. - The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013, - including rules for the presence of the response body. - Specifically in case of this task resource, the response code 404 shall also returned if the task is - not supported for the VNF instance represented by the parent resource, which means that the task resource - consequently does not exist. + #Shall be returned upon the following error: The API producer did not find a current representation + #for the target resource or is not willing to disclose that one exists. + #The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013, + #including rules for the presence of the response body. + #Specifically in case of this task resource, the response code 404 shall also returned if the task is + #not supported for the VNF instance represented by the parent resource, which means that the task resource + #consequently does not exist. $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/404" 405: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" 406: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" 409: - description: > - 409 CONFLICT + #description: > + #409 CONFLICT - Shall be returned upon the following error: The operation cannot be executed currently, - due to a conflict with the state of the resource. - Typically, this is due to the fact that the VNF instance resource is in NOT_INSTANTIATED state, - that another lifecycle management operation is ongoing, or that a required child attribute of - the "extensions" attribute has not been set. - Those attributes are marked as "required" in the VNFD. + #Shall be returned upon the following error: The operation cannot be executed currently, + #due to a conflict with the state of the resource. + #Typically, this is due to the fact that the VNF instance resource is in NOT_INSTANTIATED state, + #that another lifecycle management operation is ongoing, or that a required child attribute of + #the "extensions" attribute has not been set. + #Those attributes are marked as "required" in the VNFD. $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" 500: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500" @@ -1454,31 +1454,31 @@ paths: 403: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/403" 404: - description: > - 404 NOT FOUND + #description: > + #404 NOT FOUND - Shall be returned upon the following error: The API producer did not find a current representation - for the target resource or is not willing to disclose that one exists. - The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013, - including rules for the presence of the response body. - Specifically in case of this task resource, the response code 404 shall also returned if the task is - not supported for the VNF instance represented by the parent resource, which means that the task resource - consequently does not exist. + #Shall be returned upon the following error: The API producer did not find a current representation + #for the target resource or is not willing to disclose that one exists. + #The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013, + #including rules for the presence of the response body. + #Specifically in case of this task resource, the response code 404 shall also returned if the task is + #not supported for the VNF instance represented by the parent resource, which means that the task resource + #consequently does not exist. $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/404" 405: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" 406: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" 409: - description: > - 409 CONFLICT + #description: > + #409 CONFLICT - Shall be returned upon the following error: The operation cannot be executed currently, - due to a conflict with the state of the resource. - Typically, this is due to the fact that the VNF instance resource is in NOT_INSTANTIATED state, - that another lifecycle management operation is ongoing, or that a required child attribute of - the "extensions" attribute has not been set. - Those attributes are marked as "required" in the VNFD. + #Shall be returned upon the following error: The operation cannot be executed currently, + #due to a conflict with the state of the resource. + #Typically, this is due to the fact that the VNF instance resource is in NOT_INSTANTIATED state, + #that another lifecycle management operation is ongoing, or that a required child attribute of + #the "extensions" attribute has not been set. + #Those attributes are marked as "required" in the VNFD. $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" 500: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500" @@ -1591,14 +1591,14 @@ paths: 406: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" 409: - description: > - 409 CONFLICT + #description: > + #409 CONFLICT - Shall be returned upon the following error: The operation cannot be executed currently, - due to a conflict with the state of the resource. - Typically, this is due to the fact that another lifecycle management operation is ongoing, - or that a required child attribute of the "extensions" attribute has not been set. - Those attributes are marked as "required" in the VNFD. + #Shall be returned upon the following error: The operation cannot be executed currently, + #due to a conflict with the state of the resource. + #Typically, this is due to the fact that another lifecycle management operation is ongoing, + #or that a required child attribute of the "extensions" attribute has not been set. + #Those attributes are marked as "required" in the VNFD. $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" 500: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500" @@ -1615,7 +1615,7 @@ paths: get: description: > Get Operation Status. - The client can use this method to query status information about multiple + The API consumer can use this method to query status information about multiple VNF lifecycle management operation occurrences. This method shall follow the provisions specified in the tables 5.4.12.3.2-1 and 5.4.12.3.2-2 for URI query parameters, request and response data structures, and response codes. @@ -1777,7 +1777,7 @@ paths: get: description: > Get Operation Status. - The client can use this method to retrieve status information about a VNF lifecycle + The API consumer can use this method to retrieve status information about a VNF lifecycle management operation occurrence by reading an "Individual VNF LCM operation occurrence" resource. This method shall follow the provisions specified in the tables 5.4.13.3.2-1 and 5.4.13.3.2-2 for URI query parameters, request and response data structures, and response codes. -- GitLab From 649f45c5ccf36fda8ffb016de99d9aa9128a2514 Mon Sep 17 00:00:00 2001 From: Francesca Moscatelli Date: Wed, 5 Feb 2020 11:17:49 +0100 Subject: [PATCH 006/260] SOL003_036: Rollback POST description updated --- .../VNFLifecycleManagement.yaml | 34 +++++++++++-------- 1 file changed, 19 insertions(+), 15 deletions(-) diff --git a/src/SOL003/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL003/VNFLifecycleManagement/VNFLifecycleManagement.yaml index bcc7ef4e..4292a2f8 100644 --- a/src/SOL003/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL003/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -1921,29 +1921,29 @@ paths: 403: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/403" 404: - description: > - 404 NOT FOUND + #description: > + #404 NOT FOUND - Shall be returned upon the following error: The API producer did not find a current representation - for the target resource or is not willing to disclose that one exists. - The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013, - including rules for the presence of the response body. - Specifically in case of this task resource, the response code 404 shall also be returned if the task - is not supported for the VNF LCM operation occurrence represented by the parent resource, - which means that the task resource consequently does not exist. + #Shall be returned upon the following error: The API producer did not find a current representation + #for the target resource or is not willing to disclose that one exists. + #The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013, + #including rules for the presence of the response body. + #Specifically in case of this task resource, the response code 404 shall also be returned if the task + #is not supported for the VNF LCM operation occurrence represented by the parent resource, + #which means that the task resource consequently does not exist. $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/404" 405: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" 406: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" 409: - description: > - 409 CONFLICT + #description: > + #409 CONFLICT - Shall be returned upon the following error: The operation cannot be executed currently, - due to a conflict with the state of the VNF LCM operation occurrence. - Typically, this is due to the fact that the VNF LCM operation occurrence is not in FAILED_TEMP state, - or another error handling action is starting, such as rollback or fail. + #Shall be returned upon the following error: The operation cannot be executed currently, + #due to a conflict with the state of the VNF LCM operation occurrence. + #Typically, this is due to the fact that the VNF LCM operation occurrence is not in FAILED_TEMP state, + #or another error handling action is starting, such as rollback or fail. $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" 500: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500" @@ -1974,6 +1974,10 @@ paths: The POST method initiates rolling back a VNF lifecycle operation if that operation has experienced a temporary failure, i.e. the related "Individual VNF LCM operation occurrence" resource is in "FAILED_TEMP" state. + In case of rolling back an occurrence of the "InstantiateVnf" operation, the VNFM shall + request to the VIM the release of the virtualised resources that were allocated for the related VNF instance. + The "rollback" task shall be supported by the VNFM for any VNF LCM operation occurrence that represents an + "InstantiateVnf" operation in FAILED_TEMP state. This method shall follow the provisions specified in the tables 5.4.15.3.1-1 and 5.4.15.3.1-2 for URI query parameters, request and response data structures, and response codes. In case of success of processing the asynchronous request, the "operationState" attribute -- GitLab From f93078e27b08ed4c16a0ffbd502656d1f2cbceef Mon Sep 17 00:00:00 2001 From: Francesca Moscatelli Date: Wed, 5 Feb 2020 11:23:35 +0100 Subject: [PATCH 007/260] SOL003_040: 422 error code added to Subscriptions POST --- .../VNFLifecycleManagement.yaml | 88 ++++++++++--------- 1 file changed, 45 insertions(+), 43 deletions(-) diff --git a/src/SOL003/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL003/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 4292a2f8..c1d007af 100644 --- a/src/SOL003/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL003/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -2026,29 +2026,29 @@ paths: 403: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/403" 404: - description: > - 404 NOT FOUND + #description: > + #404 NOT FOUND - Shall be returned upon the following error: The API producer did not find a current representation - for the target resource or is not willing to disclose that one exists. - The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013, - including rules for the presence of the response body. - Specifically in case of this task resource, the response code 404 shall also be returned if the task - is not supported for the VNF LCM operation occurrence represented by the parent resource, - which means that the task resource consequently does not exist. + #Shall be returned upon the following error: The API producer did not find a current representation + #for the target resource or is not willing to disclose that one exists. + #The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013, + #including rules for the presence of the response body. + #Specifically in case of this task resource, the response code 404 shall also be returned if the task + #is not supported for the VNF LCM operation occurrence represented by the parent resource, + #which means that the task resource consequently does not exist. $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/404" 405: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" 406: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" 409: - description: > - 409 CONFLICT + #description: > + #409 CONFLICT - Shall be returned upon the following error: The operation cannot be executed currently, - due to a conflict with the state of the VNF LCM operation occurrence. - Typically, this is due to the fact that the VNF LCM operation occurrence is not in FAILED_TEMP state, - or another error handling action is starting, such as rollback or fail. + #Shall be returned upon the following error: The operation cannot be executed currently, + #due to a conflict with the state of the VNF LCM operation occurrence. + #Typically, this is due to the fact that the VNF LCM operation occurrence is not in FAILED_TEMP state, + #or another error handling action is starting, such as rollback or fail. $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" 500: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500" @@ -2142,29 +2142,29 @@ paths: 403: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/403" 404: - description: > - 404 NOT FOUND + #description: > + #404 NOT FOUND - Shall be returned upon the following error: The API producer did not find a current representation - for the target resource or is not willing to disclose that one exists. - The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013, - including rules for the presence of the response body. - Specifically in case of this task resource, the response code 404 shall also returned if the task - is not supported for the VNF LCM operation occurrence represented by the parent resource, which means - that the task resource consequently does not exist. + #Shall be returned upon the following error: The API producer did not find a current representation + #for the target resource or is not willing to disclose that one exists. + #The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013, + #including rules for the presence of the response body. + #Specifically in case of this task resource, the response code 404 shall also returned if the task + #is not supported for the VNF LCM operation occurrence represented by the parent resource, which means + #that the task resource consequently does not exist. $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/404" 405: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" 406: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" 409: - description: > - 409 CONFLICT + #description: > + #409 CONFLICT - Shall be returned upon the following error: The operation cannot be executed currently, due to a conflict - with the state of the VNF LCM operation occurrence. - Typically, this is due to the fact that the VNF LCM operation occurrence is not in FAILED_TEMP state, - or another error handling action is starting, such as retry or rollback. + #Shall be returned upon the following error: The operation cannot be executed currently, due to a conflict + #with the state of the VNF LCM operation occurrence. + #Typically, this is due to the fact that the VNF LCM operation occurrence is not in FAILED_TEMP state, + #or another error handling action is starting, such as retry or rollback. $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" 500: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500" @@ -2264,13 +2264,13 @@ paths: 406: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" 409: - description: > - 409 CONFLICT + #description: > + #409 CONFLICT - Shall be returned upon the following error: The operation cannot be executed currently, - due to a conflict with the state of the VNF LCM operation occurrence. - Typically, this is due to the fact that the operation occurrence is not in STARTING, - PROCESSING or ROLLING_BACK state. + #Shall be returned upon the following error: The operation cannot be executed currently, + #due to a conflict with the state of the VNF LCM operation occurrence. + #Typically, this is due to the fact that the operation occurrence is not in STARTING, + #PROCESSING or ROLLING_BACK state. $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" 500: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500" @@ -2371,14 +2371,14 @@ paths: schema: $ref: "../../definitions/SOL002SOL003VNFLifecycleManagement_def.yaml#/definitions/LccnSubscription" 303: - description: > - 303 SEE OTHER + #description: > + #303 SEE OTHER - Shall be returned if a subscription with the same callbackURI and the same filter already exists - and the policy of the VNFM is to not create redundant subscriptions. - The HTTP response shall include a "Location" HTTP header that contains the resource URI of the existing - "Individual subscription" resource. - The response body shall be empty. + #Shall be returned if a subscription with the same callbackURI and the same filter already exists + #and the policy of the VNFM is to not create redundant subscriptions. + #The HTTP response shall include a "Location" HTTP header that contains the resource URI of the existing + #"Individual subscription" resource. + #The response body shall be empty. $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/303" 400: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/400" @@ -2392,6 +2392,8 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/404" 406: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" + 422: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/422" 500: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500" 503: -- GitLab From 1b022497412cc6122f9d228b17807f00181b8b1a Mon Sep 17 00:00:00 2001 From: Francesca Moscatelli Date: Wed, 5 Feb 2020 12:27:23 +0100 Subject: [PATCH 008/260] SOL003_42: VnfInstance data type updated --- .../SOL003VNFLifecycleManagement_def.yaml | 23 ++++++++++++++++++- .../VNFLifecycleManagementNotification.yaml | 12 +++++----- 2 files changed, 28 insertions(+), 7 deletions(-) diff --git a/src/SOL003/VNFLifecycleManagement/definitions/SOL003VNFLifecycleManagement_def.yaml b/src/SOL003/VNFLifecycleManagement/definitions/SOL003VNFLifecycleManagement_def.yaml index 28a170a3..eb40c55b 100644 --- a/src/SOL003/VNFLifecycleManagement/definitions/SOL003VNFLifecycleManagement_def.yaml +++ b/src/SOL003/VNFLifecycleManagement/definitions/SOL003VNFLifecycleManagement_def.yaml @@ -32,6 +32,14 @@ definitions: vnfdId: description: > Identifier of the VNFD on which the VNF instance is based. + + Modifying the value of this attribute shall not be performed when conflicts + exist between the previous and the newly referred VNF package, + i.e. when the new VNFD is not changed with respect to the previous VNFD + in other aspects than merely referencing to other VNF software images. + In order to avoid misalignment of the VnfInstance with the current VNF's + on-boarded VNF Package, the values of attributes in the VnfInstance that + have corresponding attributes in the VNFD shall be kept in sync with the values in the VNFD. $ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/Identifier" vnfProvider: description: > @@ -73,7 +81,13 @@ definitions: * isAutohealEnabled: If present, the VNF supports auto-healing. If set to true, auto-healing is currently enabled. If set to false, auto-healing is currently disabled. - This attribute can be modified with the PATCH method. + These configurable properties can be initialized with default values + from the VNFD (see note 4) or with values passed in the InstantiateVnfRequest + structure (see clause 5.5.2.4). + Configurable properties initialized with default values from the VNFD can be + updated with values passed in the InstantiateVnfRequest structure. + Further, these configurable properties can be created, modified or + deleted with the PATCH method. $ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/KeyValuePairs" vimConnectionInfo: description: > @@ -119,6 +133,13 @@ definitions: type: array items: $ref: "../../../definitions/SOL002SOL003VNFLifecycleManagement_def.yaml#/definitions/ScaleInfo" + maxScaleLevels: + description: > + Maximum allowed scale levels of the VNF, one entry per aspect. + This attribute shall be present if the VNF supports scaling. + type: array + items: + $ref: "../../../definitions/SOL002SOL003VNFLifecycleManagement_def.yaml#/definitions/ScaleInfo" extCpInfo: description: > Information about the external CPs exposed by the VNF instance. diff --git a/src/SOL003/VNFLifecycleManagementNotification/VNFLifecycleManagementNotification.yaml b/src/SOL003/VNFLifecycleManagementNotification/VNFLifecycleManagementNotification.yaml index 47458062..d26037d1 100644 --- a/src/SOL003/VNFLifecycleManagementNotification/VNFLifecycleManagementNotification.yaml +++ b/src/SOL003/VNFLifecycleManagementNotification/VNFLifecycleManagementNotification.yaml @@ -1,7 +1,7 @@ swagger: "2.0" info: - version: "1.3.0-impl:etsi.org:ETSI_NFV_OpenAPI:1" + version: "1.4.0-impl:etsi.org:ETSI_NFV_OpenAPI:1" title: SOL003 - VNF Lifecycle Management Notification interface description: > SOL003 - VNF Lifecycle Management Notification interface @@ -25,8 +25,8 @@ info: url: https://forge.etsi.org/etsi-forge-copyright-notice.txt externalDocs: - description: ETSI GS NFV-SOL 003 V2.6.1 - url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.06.01_60/gs_NFV-SOL003v020601p.pdf + description: ETSI GS NFV-SOL 003 V2.7.1 + url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.07.01_60/gs_NFV-SOL003v020701p.pdf basePath: "/callback/v1" @@ -115,7 +115,7 @@ paths: get: description: > - The GET method allows the server to test the notification endpoint that is provided by the client, + The GET method allows the server to test the notification endpoint that is provided by the API consumer, e.g. during subscription. This method shall follow the provisions specified in the tables 5.4.20.3.2-1 and 5.4.20.3.2-2 for URI query parameters, request and response data structures, and response codes. @@ -247,7 +247,7 @@ paths: get: description: > - The GET method allows the server to test the notification endpoint that is provided by the client, + The GET method allows the server to test the notification endpoint that is provided by the API consumer, e.g. during subscription. This method shall follow the provisions specified in the tables 5.4.20.3.2-1 and 5.4.20.3.2-2 for URI query parameters, request and response data structures, and response codes. @@ -379,7 +379,7 @@ paths: get: description: > - The GET method allows the server to test the notification endpoint that is provided by the client, + The GET method allows the server to test the notification endpoint that is provided by the API consumer, e.g. during subscription. This method shall follow the provisions specified in the tables 5.4.20.3.2-1 and 5.4.20.3.2-2 for URI query parameters, request and response data structures, and response codes. -- GitLab From 750d92491075f265c0e67f91d7d75edb8692aa83 Mon Sep 17 00:00:00 2001 From: Francesca Moscatelli Date: Wed, 5 Feb 2020 12:42:05 +0100 Subject: [PATCH 009/260] =?UTF-8?q?SOL003=5F044:=20=C2=96InstantiateVnfReq?= =?UTF-8?q?uest=20updated?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- .../SOL003VNFLifecycleManagement_def.yaml | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/src/SOL003/VNFLifecycleManagement/definitions/SOL003VNFLifecycleManagement_def.yaml b/src/SOL003/VNFLifecycleManagement/definitions/SOL003VNFLifecycleManagement_def.yaml index eb40c55b..adec411c 100644 --- a/src/SOL003/VNFLifecycleManagement/definitions/SOL003VNFLifecycleManagement_def.yaml +++ b/src/SOL003/VNFLifecycleManagement/definitions/SOL003VNFLifecycleManagement_def.yaml @@ -357,6 +357,21 @@ definitions: to the VNF being instantiated, as declared in the VNFD as part of "InstantiateVnfOpConfig". $ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/KeyValuePairs" + extensions: + description: > + If present, this attribute provides values for the "extensions" attribute + in "VnfInstance", as defined in clause 5.5.2.2. If an entry with the same + key exists in the VnfInstance data structure, the VNFM shall replace its + value with the value passed in the InstantiateVnfRequest data structure. + $ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/KeyValuePairs" + vnfConfigurableProperties: + description: > + This parameter provides values for the VNF configurable properties + attribute in the "VnfInstance", as defined in clause 5.5.2.2. + If an entry with the same key exists in the VnfInstance data structure, + the VNFM shall replace its value with the value passed in the + InstantiateVnfRequest data structure. + $ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/KeyValuePairs" ChangeVnfFlavourRequest: #SOL003 location: 5.5.2.7 -- GitLab From 8f065fd7f5130c38683372c27ebb814403fbb650 Mon Sep 17 00:00:00 2001 From: Francesca Moscatelli Date: Wed, 5 Feb 2020 12:44:00 +0100 Subject: [PATCH 010/260] SOL003_0445: ChangeVnfFlavourRequest updated --- .../definitions/SOL003VNFLifecycleManagement_def.yaml | 1 + 1 file changed, 1 insertion(+) diff --git a/src/SOL003/VNFLifecycleManagement/definitions/SOL003VNFLifecycleManagement_def.yaml b/src/SOL003/VNFLifecycleManagement/definitions/SOL003VNFLifecycleManagement_def.yaml index adec411c..62b4fffb 100644 --- a/src/SOL003/VNFLifecycleManagement/definitions/SOL003VNFLifecycleManagement_def.yaml +++ b/src/SOL003/VNFLifecycleManagement/definitions/SOL003VNFLifecycleManagement_def.yaml @@ -394,6 +394,7 @@ definitions: extVirtualLinks: description: > Information about external VLs to connect the VNF to. + Entries in the list of external VLs that are unchanged need not be supplied as part of this request. type: array items: $ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/ExtVirtualLinkData" -- GitLab From 612a8fb0782a954629cd4948c47b0b8f144e4315 Mon Sep 17 00:00:00 2001 From: Francesca Moscatelli Date: Wed, 5 Feb 2020 12:48:58 +0100 Subject: [PATCH 011/260] SOL003_046: ChangeExtVnfConnectivityRequest updated --- .../definitions/SOL003VNFLifecycleManagement_def.yaml | 1 + 1 file changed, 1 insertion(+) diff --git a/src/SOL003/VNFLifecycleManagement/definitions/SOL003VNFLifecycleManagement_def.yaml b/src/SOL003/VNFLifecycleManagement/definitions/SOL003VNFLifecycleManagement_def.yaml index 62b4fffb..abc6e30d 100644 --- a/src/SOL003/VNFLifecycleManagement/definitions/SOL003VNFLifecycleManagement_def.yaml +++ b/src/SOL003/VNFLifecycleManagement/definitions/SOL003VNFLifecycleManagement_def.yaml @@ -535,6 +535,7 @@ definitions: extVirtualLinks: description: > Information about external VLs to change (e.g. connect the VNF to). + Entries in the list of external VLs that are unchanged need not be supplied as part of this request. type: array items: $ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/ExtVirtualLinkData" -- GitLab From c8d6e69b35c9fc103356b3c99519d1b8e4b1ff35 Mon Sep 17 00:00:00 2001 From: Francesca Moscatelli Date: Wed, 5 Feb 2020 12:51:33 +0100 Subject: [PATCH 012/260] SOL003_028: VnfLcmOperationOccurrenceNotification description updated --- src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml b/src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml index 68547f2f..d552ad86 100644 --- a/src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml +++ b/src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml @@ -1210,7 +1210,7 @@ definitions: notification is mandatory. This notification shall be triggered by the VNFM when there is a change in the state of a VNF LCM operation occurrence that changes the VNF lifecycle, - including: + which represents an occurrence of one the following LCM operations: * Instantiation of the VNF * Scaling of the VNF instance (including auto-scaling) * Healing of the VNF instance (including auto-healing) -- GitLab From d68c6c1cc5cbb207b2c9c897c2fd5404e85d89f4 Mon Sep 17 00:00:00 2001 From: Francesca Moscatelli Date: Wed, 5 Feb 2020 12:53:32 +0100 Subject: [PATCH 013/260] SOL003_048: VnfLcmOperationOccurrenceNotification description updated --- src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml b/src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml index d552ad86..8ca3c5b4 100644 --- a/src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml +++ b/src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml @@ -1363,6 +1363,8 @@ definitions: Shall be present if the "notificationStatus" is set to "RESULT" and the "operation" has made any changes to the external connectivity of the VNF instance. Shall be absent otherwise. + Only information about external VL instances that have been added or + modified shall be provided. type: array items: $ref: "#/definitions/ExtVirtualLinkInfo" @@ -1370,8 +1372,8 @@ definitions: description: > Details of the latest error, if one has occurred during executing the LCM operation (see clause 6.3 of ETSI GS NFV-SOL 013). - Shall be present if the "operationState" attribute is "FAILED_TEMP" or "FAILED", - and shall be absent otherwise. + Shall be present if the "operationState" attribute is "FAILED_TEMP", "FAILED" + or "ROLLED_BACK" and shall be absent otherwise. $ref: "SOL002SOL003_def.yaml#/definitions/ProblemDetails" _links: description: > -- GitLab From ac503713fd686c394a42c9e3ac32e3db74bf1b6b Mon Sep 17 00:00:00 2001 From: Francesca Moscatelli Date: Wed, 5 Feb 2020 12:57:17 +0100 Subject: [PATCH 014/260] SOL003_049: VnfcResourceInfo updated --- .../SOL002SOL003VNFLifecycleManagement_def.yaml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml b/src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml index 8ca3c5b4..91d4aa14 100644 --- a/src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml +++ b/src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml @@ -577,6 +577,13 @@ definitions: description: > Reference to the VirtualCompute resource. $ref: "SOL002SOL003_def.yaml#/definitions/ResourceHandle" + zoneId: + description: > + The identifier of the resource zone, as managed by the + resource management layer (typically, the VIM), where + the referenced VirtualCompute resource is placed. + Shall be provided if this information is available from the VIM. + $ref: "SOL002SOL003_def.yaml#/definitions/Identifier" storageResourceIds: description: > References to the VirtualStorage resources. The value refers to a -- GitLab From c610e256bad60241155d2ec9348a7f587dd2b670 Mon Sep 17 00:00:00 2001 From: Francesca Moscatelli Date: Wed, 5 Feb 2020 13:37:04 +0100 Subject: [PATCH 015/260] SOL003_050: VnfVirtualLinkResourceInfo updated --- .../SOL002SOL003VNFLifecycleManagement_def.yaml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml b/src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml index 91d4aa14..490bb392 100644 --- a/src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml +++ b/src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml @@ -666,6 +666,13 @@ definitions: description: > Reference to the VirtualNetwork resource. $ref: "SOL002SOL003_def.yaml#/definitions/ResourceHandle" + zoneId: + description: > + The identifier of the resource zone, as managed by the resource + management layer (typically, the VIM), where the referenced + VirtualNetwork resource is placed. Shall be provided if this + information is available from the VIM. + $ref: "SOL002SOL003_def.yaml#/definitions/Identifier" reservationId: description: > The reservation identifier applicable to the resource. It shall be -- GitLab From b3bd7b9c7e2a04ee6d0e9f9b35c6e36ee6a6bf09 Mon Sep 17 00:00:00 2001 From: Francesca Moscatelli Date: Wed, 5 Feb 2020 14:59:13 +0100 Subject: [PATCH 016/260] SOL003_051: VirtualStorageResourceInfo updated --- .../SOL002SOL003VNFLifecycleManagement_def.yaml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml b/src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml index 490bb392..522e8463 100644 --- a/src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml +++ b/src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml @@ -714,6 +714,13 @@ definitions: description: > Reference to the VirtualStorage resource. $ref: "SOL002SOL003_def.yaml#/definitions/ResourceHandle" + zoneId: + description: > + The identifier of the resource zone, as managed by the resource + management layer (typically, the VIM), where the referenced + VirtualStorage resource is placed. Shall be provided if this + information is available from the VIM. + $ref: "SOL002SOL003_def.yaml#/definitions/Identifier" reservationId: description: > The reservation identifier applicable to the resource. It shall be -- GitLab From 53385ee11621ccf9a7cdc81dd0d8e99cc98db978 Mon Sep 17 00:00:00 2001 From: Francesca Moscatelli Date: Wed, 5 Feb 2020 15:01:17 +0100 Subject: [PATCH 017/260] SOL003_052: VnfLinkPortInfo updated --- src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml b/src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml index 522e8463..f4debb7b 100644 --- a/src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml +++ b/src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml @@ -752,7 +752,7 @@ definitions: this attribute represents the identifier of the external CP of the VNF to be connected to this link port. When the link port is used for internal connectivity in the VNF, - this attribute represents the VNFC CP to be connected to this link + this attribute represents the identifier of the VNFC CP to be connected to this link port. Shall be present when the link port is used for external connectivity by the VNF. -- GitLab From ddd502d4da83479a1030afb5303a953befbbbe26 Mon Sep 17 00:00:00 2001 From: Francesca Moscatelli Date: Wed, 5 Feb 2020 15:03:16 +0100 Subject: [PATCH 018/260] SOL003_053: ExtLinkPortData removed from VNF Lifecycle Management def (already present in common generic def) --- ...OL002SOL003VNFLifecycleManagement_def.yaml | 20 ------------------- 1 file changed, 20 deletions(-) diff --git a/src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml b/src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml index f4debb7b..937e3483 100644 --- a/src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml +++ b/src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml @@ -802,26 +802,6 @@ definitions: "extCpInfo" item in the VnfInstance. $ref: "SOL002SOL003_def.yaml#/definitions/IdentifierInVnf" - ExtLinkPortData: - description: > - This type represents an externally provided link port to be used to connect - an external connection point to an external VL. - type: object - required: - - id - - resourceHandle - properties: - id: - description: > - Identifier of this link port as provided by the entity that - has created the link port. - $ref: 'SOL002SOL003_def.yaml#/definitions/Identifier' - resourceHandle: - description: > - Reference to the virtualised resource realizing this link - port. - $ref: 'SOL002SOL003_def.yaml#/definitions/ResourceHandle' - CpProtocolInfo: description: > This type describes the protocol layer(s) that a CP uses together with -- GitLab From 8fbfc30691b36cbc9a7b14c439e642cfd100eaf8 Mon Sep 17 00:00:00 2001 From: Francesca Moscatelli Date: Wed, 5 Feb 2020 15:04:45 +0100 Subject: [PATCH 019/260] SOL003_054: IpOverEthernetAddressInfo updated --- src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml | 1 + 1 file changed, 1 insertion(+) diff --git a/src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml b/src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml index 937e3483..3040236d 100644 --- a/src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml +++ b/src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml @@ -844,6 +844,7 @@ definitions: Addresses assigned to the CP instance. Each entry represents IP addresses assigned by fixed or dynamic IP address assignment per subnet. + At least one of "macAddress" or "ipAddresses" shall be present. type: array items: type: object -- GitLab From c716c9f5cb7790c5435ba230de8eb8c33121a028 Mon Sep 17 00:00:00 2001 From: Francesca Moscatelli Date: Wed, 5 Feb 2020 15:10:23 +0100 Subject: [PATCH 020/260] SOL003_055: AffectedVnfc updated --- src/definitions/SOL002SOL003_def.yaml | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/src/definitions/SOL002SOL003_def.yaml b/src/definitions/SOL002SOL003_def.yaml index 4e72e507..5f3b6bbb 100644 --- a/src/definitions/SOL002SOL003_def.yaml +++ b/src/definitions/SOL002SOL003_def.yaml @@ -901,6 +901,18 @@ definitions: (for new and modified resources) or has been (for removed resources) available from the VIM. $ref: "#/definitions/ResourceHandle" + resourceDefinitionId: + description: > + The identifier of the "ResourceDefinition" in the granting exchange + related to the LCM operation occurrence. It shall be present when + an applicable GrantInfo for thegranted resource exists. See note. + $ref: "#/definitions/IdentifierLocal" + zoneId: + description: > + The identifier of the resource zone, as managed by the resource management + layer (typically, the VIM), where the referenced VirtualCompute resource is placed. + Shall be provided if this information is available from the VIM. + $ref: "#/definitions/Identifier" metadata: description: > Metadata about this resource. -- GitLab From e524b7512cc44deea281c45a3c54b870a846c91e Mon Sep 17 00:00:00 2001 From: Francesca Moscatelli Date: Wed, 5 Feb 2020 15:14:26 +0100 Subject: [PATCH 021/260] SOL003_056: AffectedVirtualLink updated --- ...SOL002SOL003VNFLifecycleManagement_def.yaml | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml b/src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml index 3040236d..977bbb06 100644 --- a/src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml +++ b/src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml @@ -1019,6 +1019,24 @@ definitions: (for new and modified resources) or has been (for removed resources) available from the VIM. $ref: "SOL002SOL003_def.yaml#/definitions/ResourceHandle" + resourceDefinitionId: + description: > + The identifier of the "ResourceDefinition" in the granting exchange + related to the LCM operation occurrence. It shall be present when an + applicable GrantInfo for the granted resource exists. + The "resourceDefinitionId" attribute provides information to the API + consumer (i.e. the NFVO) to assist in correlating the resource changes + performed during the LCM operation with the granted resources in a + specific Grant exchange, which is identified by the "grantId" available + in the "Individual VNF lifecycle management operation occurrence" and + the "id" in the "Individual Grant". + $ref: "SOL002SOL003_def.yaml#/definitions/IdentifierLocal" + zoneId: + description: > + The identifier of the resource zone, as managed by the resource + management layer (typically, the VIM), where the referenced VirtualNetwork + resource is placed. Shall be provided if this information is available from the VIM. + $ref: "SOL002SOL003_def.yaml#/definitions/Identifier" metadata: description: > Metadata about this resource. -- GitLab From 26a5d305d1c7d71740e16e5981a34f73371815a6 Mon Sep 17 00:00:00 2001 From: Francesca Moscatelli Date: Wed, 5 Feb 2020 15:16:53 +0100 Subject: [PATCH 022/260] SOL003_057: AffectedVirtualStorage updated --- ...SOL002SOL003VNFLifecycleManagement_def.yaml | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml b/src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml index 977bbb06..8bef37c7 100644 --- a/src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml +++ b/src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml @@ -1085,6 +1085,24 @@ definitions: (for new and modified resources) or has been (for removed resources) available from the VIM. $ref: "SOL002SOL003_def.yaml#/definitions/ResourceHandle" + resourceDefinitionId: + description: > + The identifier of the "ResourceDefinition" in the granting exchange + related to the LCM operation occurrence. It shall be present when an + applicable GrantInfo for the granted resource exists. + The "resourceDefinitionId" attribute provides information to the API + consumer (i.e. the NFVO) to assist in correlating the resource changes + performed during the LCM operation with the granted resources in a + specific Grant exchange, which is identified by the "grantId" available + in the "Individual VNF lifecycle management operation occurrence" and + the "id" in the "Individual Grant". + $ref: "SOL002SOL003_def.yaml#/definitions/IdentifierLocal" + zoneId: + description: > + The identifier of the resource zone, as managed by the resource + management layer (typically, the VIM), where the referenced VirtualNetwork + resource is placed. Shall be provided if this information is available from the VIM. + $ref: "SOL002SOL003_def.yaml#/definitions/Identifier" metadata: description: > Metadata about this resource. -- GitLab From c03b88a274da6d95d7f1c07bd051724fbc658b6d Mon Sep 17 00:00:00 2001 From: Francesca Moscatelli Date: Wed, 5 Feb 2020 15:52:09 +0100 Subject: [PATCH 023/260] SOL003_072/094: Individual PmJob PATCH added + PmJobMOdifications added --- .../VNFPerformanceManagement.yaml | 85 +++++++++++++++++-- ...002SOL003VNFPerformanceManagement_def.yaml | 21 +++++ 2 files changed, 101 insertions(+), 5 deletions(-) diff --git a/src/SOL003/VNFPerformanceManagement/VNFPerformanceManagement.yaml b/src/SOL003/VNFPerformanceManagement/VNFPerformanceManagement.yaml index 02510fbe..a40b3d7f 100644 --- a/src/SOL003/VNFPerformanceManagement/VNFPerformanceManagement.yaml +++ b/src/SOL003/VNFPerformanceManagement/VNFPerformanceManagement.yaml @@ -25,8 +25,8 @@ info: url: https://forge.etsi.org/etsi-forge-copyright-notice.txt externalDocs: - description: ETSI GS NFV-SOL 003 V2.6.1 - url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.06.01_60/gs_NFV-SOL003v020601p.pdf + description: ETSI GS NFV-SOL 003 V2.7.1 + url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.07.01_60/gs_NFV-SOL003v020701p.pdf basePath: "/vnfpm/v1" @@ -147,7 +147,7 @@ paths: get: description: > Query PM Job. - The client can use this method to retrieve information about PM jobs. + The API consumer can use this method to retrieve information about PM jobs. This method shall follow the provisions specified in the tables 6.4.2.3.2-1 and 6.4.2.3.2-2 for URI query parameters, request and response data structures, and response codes. The client can use this method to retrieve information about PM jobs. @@ -205,7 +205,7 @@ paths: The following attributes shall be excluded from the PmJob structure in the response body if this parameter is provided, or none of the parameters "all_fields", "fields", "exclude_fields", "exclude_default" are provided: - - Reports + - reports in: query required: false type: string @@ -310,7 +310,7 @@ paths: get: description: > Query PM Job. - The client can use this method for reading an individual PM job. + The API consumer can use this method for reading an individual PM job. This method shall follow the provisions specified in the tables 6.4.3.3.2-1 and 6.4.3.3.2-2 for URI query parameters, request and response data structures, and response codes. parameters: @@ -387,6 +387,81 @@ paths: 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" + patch: + description: > + This method allows to modify an "individual PM job" resource. + This method shall follow the provisions specified in the tables + 6.4.3.3.4-1 and 6.4.3.3.4-2 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 + - name: Version + description: > + Version of the API requested to use when responding to this request. + in: header + required: true + type: string + responses: + 200: + description: > + 200 OK + + Shall be returned when the request has been processed successfully. + The response body shall contain a data structure of type "PmJobModifications". + headers: + Content-Type: + description: > + The MIME type of the body of the request. + Reference: IETF RFC 7231 + type: string + maximum: 1 + minimum: 1 + 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 + Version: + description: > + Version of the API used in the response. + type: string + maximum: 1 + minimum: 1 + schema: + $ref: "../../definitions/SOL002SOL003VNFPerformanceManagement_def.yaml#/definitions/PmJobModifications" + 400: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/400" + 401: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/401" + 403: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/403" + 404: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/404" + 405: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + 406: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" + 412: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/412" + 422: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/422" + 500: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500" + 503: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" + 504: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" + + delete: description: > Delete PM Job. diff --git a/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml b/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml index 61160e4f..521a34a8 100644 --- a/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml +++ b/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml @@ -273,6 +273,27 @@ definitions: items: $ref: "SOL002SOL003_def.yaml#/definitions/Link" + PmJobModifications: + description: > + This type represents modifications to a PM job. + It shall comply with the provisions defined in table 6.5.2.12-1. + type: object + properties: + callbackUri: + description: > + New value of the "callbackUri" attribute. + The value "null" is not permitted. See note. + $ref: "SOL002SOL003_def.yaml#/definitions/Uri" + authentication: + description: > + New value of the "authentication" attribute, or "null" + to remove the attribute. If present in a request body, + these modifications shall be applied according to the + rules of JSON Merge PATCH. + This attribute shall not be present in response bodies. + At least one of the attributes defined in this type shall be present in request bodies. + $ref: "SOL002SOL003_def.yaml#/definitions/SubscriptionAuthentication" + PmJobCriteria: description: > Criteria of the collection of performance information. -- GitLab From 86c85f0b4bb57bf7b226d8f940a297ee63fca3e3 Mon Sep 17 00:00:00 2001 From: Francesca Moscatelli Date: Wed, 5 Feb 2020 15:54:26 +0100 Subject: [PATCH 024/260] SO003_074: GET description updated --- .../VNFPerformanceManagement/VNFPerformanceManagement.yaml | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/src/SOL003/VNFPerformanceManagement/VNFPerformanceManagement.yaml b/src/SOL003/VNFPerformanceManagement/VNFPerformanceManagement.yaml index a40b3d7f..689382bb 100644 --- a/src/SOL003/VNFPerformanceManagement/VNFPerformanceManagement.yaml +++ b/src/SOL003/VNFPerformanceManagement/VNFPerformanceManagement.yaml @@ -461,7 +461,6 @@ paths: 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" - delete: description: > Delete PM Job. @@ -546,7 +545,7 @@ paths: required: true get: description: > - The client can use this method for reading an individual performance report. + The API consumer can use this method for reading an individual performance report. This method shall follow the provisions specified in the tables 6.4.4.3.2-1 and 6.4.4.3.2-2 for URI query parameters, request and response data structures, and response codes. parameters: -- GitLab From e67ae7a7d6b0e22e61eaa1912dab57bc0be5d37f Mon Sep 17 00:00:00 2001 From: Francesca Moscatelli Date: Wed, 5 Feb 2020 16:03:29 +0100 Subject: [PATCH 025/260] SOL003_80/93: Individual Threshold PATCH added + ThresholdModifications added --- .../VNFPerformanceManagement.yaml | 80 ++++++++++++++++++- ...002SOL003VNFPerformanceManagement_def.yaml | 21 +++++ 2 files changed, 98 insertions(+), 3 deletions(-) diff --git a/src/SOL003/VNFPerformanceManagement/VNFPerformanceManagement.yaml b/src/SOL003/VNFPerformanceManagement/VNFPerformanceManagement.yaml index 689382bb..968d4b11 100644 --- a/src/SOL003/VNFPerformanceManagement/VNFPerformanceManagement.yaml +++ b/src/SOL003/VNFPerformanceManagement/VNFPerformanceManagement.yaml @@ -630,7 +630,7 @@ paths: post: description: > Create Threshold. - The POST method can be used by the client to create a threshold. + The POST method can be used by the API consumer to create a threshold. This method shall follow the provisions specified in the tables 6.4.5.3.1-1 and 6.4.5.3.1-2 for URI query parameters, request and response data structures, and response codes. As the result of successfully executing this method, a new "Individual threshold" resource @@ -732,7 +732,7 @@ paths: get: description: > Query Threshold. - The client can use this method to query information about thresholds. + The API consumer can use this method to query information about thresholds. This method shall follow the provisions specified in the tables 6.4.5.3.2-1 and 6.4.5.3.2-2 for URI query parameters, request and response data structures, and response codes. parameters: @@ -864,7 +864,7 @@ paths: get: description: > Query Threshold. - The client can use this method for reading an individual threshold + The API consumer can use this method for reading an individual threshold This method shall follow the provisions specified in the tables 6.4.6.3.2-1 and 6.4.6.3.2-2 for URI query parameters, request and response data structures, and response codes. parameters: @@ -940,6 +940,80 @@ paths: 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" + patch: + description: > + This method allows to modify an "Individual threshold" resource. + This method shall follow the provisions specified in the tables + 6.4.6.3.4-1 and 6.4.6.3.4-2 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 + - name: Version + description: > + Version of the API requested to use when responding to this request. + in: header + required: true + type: string + responses: + 200: + description: > + 200 OK + + Shall be returned when the request has been processed successfully. + The response body shall contain a data structure of type "ThresholdModifications". + headers: + Content-Type: + description: > + The MIME type of the body of the request. + Reference: IETF RFC 7231 + type: string + maximum: 1 + minimum: 1 + 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 + Version: + description: > + Version of the API used in the response. + type: string + maximum: 1 + minimum: 1 + schema: + $ref: "../../definitions/SOL002SOL003VNFPerformanceManagement_def.yaml#/definitions/ThresholdModifications" + 400: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/400" + 401: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/401" + 403: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/403" + 404: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/404" + 405: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + 406: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" + 412: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/412" + 422: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/422" + 500: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500" + 503: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" + 504: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" + delete: description: > Delete Threshold. diff --git a/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml b/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml index 521a34a8..f462c3f8 100644 --- a/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml +++ b/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml @@ -480,6 +480,27 @@ definitions: performance information is collected. Shall be present if the VNF instance information is accessible as a resource. + ThresholdModifications: + description: > + This type represents modifications to a threshold. + It shall comply with the provisions defined in table 6.5.2.11-1. + type: object + properties: + callbackUri: + description: > + New value of the "callbackUri" attribute. + The value "null" is not permitted. See note. + $ref: "SOL002SOL003_def.yaml#/definitions/Uri" + authentication: + description: > + New value of the "authentication" attribute, or "null" + to remove the attribute. If present in a request body, + these modifications shall be applied according to the + rules of JSON Merge PATCH. + This attribute shall not be present in response bodies. + At least one of the attributes defined in this type shall be present in request bodies. + $ref: "SOL002SOL003_def.yaml#/definitions/SubscriptionAuthentication" + ThresholdCriteria: description: > This type represents criteria that define a threshold. -- GitLab From 09e3e54abab9e0356ca575558c5d9949ee26094e Mon Sep 17 00:00:00 2001 From: Francesca Moscatelli Date: Wed, 5 Feb 2020 16:11:46 +0100 Subject: [PATCH 026/260] SOL003_081/082/083: Subscriptions and Individual Subscription endpoints deleted + Notification endpoints updated --- .../VNFPerformanceManagement.yaml | 790 +++++++++--------- .../VNFPerformanceManagementNotification.yaml | 12 +- 2 files changed, 401 insertions(+), 401 deletions(-) diff --git a/src/SOL003/VNFPerformanceManagement/VNFPerformanceManagement.yaml b/src/SOL003/VNFPerformanceManagement/VNFPerformanceManagement.yaml index 968d4b11..9edb7d99 100644 --- a/src/SOL003/VNFPerformanceManagement/VNFPerformanceManagement.yaml +++ b/src/SOL003/VNFPerformanceManagement/VNFPerformanceManagement.yaml @@ -1079,398 +1079,398 @@ paths: 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" - ############################################################################### - # Subscriptions # - ############################################################################### - '/subscriptions': - #SOL003 location: 6.4.7 - post: - description: > - Subscribe. - The POST method creates a new subscription. - This method shall follow the provisions specified in the tables 6.4.7.3.1-1 and 6.4.7.3.1-2 - for URI query parameters, request and response data structures, and response codes. - As the result of successfully executing this method, a new "Individual subscription" resource - as defined in clause 6.4.8 shall have been created. This method shall not trigger any notification. - Creation of two "Individual subscription" resources with the same callbackURI and the same filter - can result in performance degradation and will provide duplicates of notifications to the NFVO, - and might make sense only in very rare use cases. Consequently, the VNFM may either allow creating - a new "Individual subscription" resource if another "Individual subscription" resource with the same - filter and callbackUri already exists (in which case it shall return the "201 Created" response code), - or may decide to not create a duplicate "Individual subscription" resource (in which case it shall - return a "303 See Other" response code referencing the existing "Individual subscription" resource - with the same filter and callbackUri). - parameters: - - name: PmSubscriptionRequest - description: > - Details of the subscription to be created. - in: body - required: true - schema: - $ref: "../../definitions/SOL002SOL003VNFPerformanceManagement_def.yaml#/definitions/PmSubscriptionRequest" - - 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 - - name: Version - description: > - Version of the API requested to use when responding to this request. - in: header - required: true - type: string - responses: - 201: - description: > - 201 CREATED - - Shall be returned when the subscription has been created successfully. - A representation of the created "Individual subscription" resource shall be - returned in the response body, as defined in clause 6.5.2.3. - The HTTP response shall include a "Location" HTTP header that contains the - resource URI of the created "Individual subscription" resource. - headers: - Location: - description: The resource URI of the created VNF instance - type: string - format: url - Content-Type: - description: > - The MIME type of the body of the request. - Reference: IETF RFC 7231 - type: string - maximum: 1 - minimum: 1 - 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 - Version: - description: > - Version of the API used in the response. - type: string - maximum: 1 - minimum: 1 - schema: - $ref: "../../definitions/SOL002SOL003VNFPerformanceManagement_def.yaml#/definitions/PmSubscription" - 303: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/303" - 400: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/400" - 401: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/401" - 403: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/403" - 404: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/404" - 405: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - 406: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" - 422: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/422" - 500: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500" - 503: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" - 504: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" - - get: - description: > - Query Subscription Information. - TThe client can use this method to query the list of active subscriptions - to Performance management notifications subscribed by the client. - This method shall follow the provisions specified in the tables 6.4.7.3.2-1 and 6.4.7.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 - - name: filter - description: > - Attribute-based filtering expression according to clause 5.2 of ETSI GS NFV-SOL 013. - The VNFM shall support receiving this parameter as part of the - URI query string. The NFVO may supply this parameter. - All attribute names that appear in the PmSubscription and in - data types referenced from it shall be supported by the VNFM - in the filter expression. - in: query - required: false - type: string - - name: nextpage_opaque_marker - description: > - Marker to obtain the next page of a paged response. Shall be - supported by the VNFM if the VNFM supports alternative 2 (paging) - according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 for this resource. - in: query - 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: - 200: - description: > - 200 OK - - Shall be returned when the list of subscriptions has been queried successfully. - The response body shall contain in an array the representations of all active subscriptions - of the functional block that invokes the method, i.e. zero or more representations of - PM subscriptions as defined in clause 6.5.2.3. - If the "filter" URI parameter was supplied in the request, the data in the response body - shall have been transformed according to the rules specified in clause 5.2.2 of ETSI GS NFV-SOL 013. - If the VNFM 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: - Content-Type: - description: > - The MIME type of the body of the request. - Reference: IETF RFC 7231 - type: string - maximum: 1 - minimum: 1 - 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 - Version: - description: > - Version of the API used in the response. - type: string - maximum: 1 - minimum: 1 - Link: - description: > - Reference to other resources. Used for paging in the present document, see clause 4.7.2.1. - type: string - maximum: 1 - minimum: 0 - schema: - type: array - items: - $ref: "../../definitions/SOL002SOL003VNFPerformanceManagement_def.yaml#/definitions/PmSubscription" - 400: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/400" - 401: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/401" - 403: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/403" - 404: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/404" - 405: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - 406: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" - 422: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/422" - 500: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500" - 503: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" - 504: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" - - ############################################################################### - # Individual subscription # - ############################################################################### - '/subscriptions/{subscriptionId}': - #SOL003 location: 6.4.8 - parameters: - - name: subscriptionId - description: > - This identifier can be retrieved from the resource referenced by the - "Location" HTTP header in the response to a POST request creating a - new "Individual subscription" resource. It can also be retrieved from the "id" - attribute in the payload body of that response. - in: path - type: string - required: true - get: - description: > - Query Subscription Information. - The client can use this method for reading an individual subscription about - Performance management notifications subscribed by the client. - This method shall follow the provisions specified in the tables 6.4.8.3.2-1 and 6.4.8.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 - - name: Version - description: > - Version of the API requested to use when responding to this request. - in: header - required: true - type: string - responses: - 200: - description: > - 200 OK - - Shall be returned when the subscription has been read successfully. - The response body shall contain a representation of the "Individual subscription" resource, - as defined in clause 6.5.2.3. - headers: - Content-Type: - description: > - The MIME type of the body of the request. - Reference: IETF RFC 7231 - type: string - maximum: 1 - minimum: 1 - 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 - Version: - description: > - Version of the API used in the response. - type: string - maximum: 1 - minimum: 1 - schema: - $ref: "../../definitions/SOL002SOL003VNFPerformanceManagement_def.yaml#/definitions/PmSubscription" - 400: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/400" - 401: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/401" - 403: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/403" - 404: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/404" - 405: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - 406: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" - 422: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/422" - 500: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500" - 503: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" - 504: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" - - delete: - description: > - Terminate Subscription. - This method terminates an individual subscription. - This method shall follow the provisions specified in the tables 6.4.8.3.5-1 and 6.4.8.3.5-2 - for URI query parameters, request and response data structures, and response codes. - As the result of successfully executing this method, the "Individual subscription" resource - shall not exist any longer. This means that no notifications for that subscription shall - be sent to the formerly-subscribed API consumer. - - NOTE: Due to race conditions, some notifications might still be received by the formerly-subscribed - API consumer for a certain time period after the deletion. - parameters: - - 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 when the "Individual subscription" resource has been deleted 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 - Version: - description: > - Version of the API used in the response. - type: string - maximum: 1 - minimum: 1 - 400: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/400" - 401: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/401" - 403: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/403" - 404: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/404" - 405: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - 406: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" - 422: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/422" - 500: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500" - 503: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" - 504: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" \ No newline at end of file +# ############################################################################## +# # Subscriptions # +# ############################################################################## +# '/subscriptions': +# #SOL003 location: 6.4.7 +# post: +# description: > +# Subscribe. +# The POST method creates a new subscription. +# This method shall follow the provisions specified in the tables 6.4.7.3.1-1 and 6.4.7.3.1-2 +# for URI query parameters, request and response data structures, and response codes. +# As the result of successfully executing this method, a new "Individual subscription" resource +# as defined in clause 6.4.8 shall have been created. This method shall not trigger any notification. +# Creation of two "Individual subscription" resources with the same callbackURI and the same filter +# can result in performance degradation and will provide duplicates of notifications to the NFVO, +# and might make sense only in very rare use cases. Consequently, the VNFM may either allow creating +# a new "Individual subscription" resource if another "Individual subscription" resource with the same +# filter and callbackUri already exists (in which case it shall return the "201 Created" response code), +# or may decide to not create a duplicate "Individual subscription" resource (in which case it shall +# return a "303 See Other" response code referencing the existing "Individual subscription" resource +# with the same filter and callbackUri). +# parameters: +# - name: PmSubscriptionRequest +# description: > +# Details of the subscription to be created. +# in: body +# required: true +# schema: +# $ref: "../../definitions/SOL002SOL003VNFPerformanceManagement_def.yaml#/definitions/PmSubscriptionRequest" +# - 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 +# - name: Version +# description: > +# Version of the API requested to use when responding to this request. +# in: header +# required: true +# type: string +# responses: +# 201: +# description: > +# 201 CREATED +# +# Shall be returned when the subscription has been created successfully. +# A representation of the created "Individual subscription" resource shall be +# returned in the response body, as defined in clause 6.5.2.3. +# The HTTP response shall include a "Location" HTTP header that contains the +# resource URI of the created "Individual subscription" resource. +# headers: +# Location: +# description: The resource URI of the created VNF instance +# type: string +# format: url +# Content-Type: +# description: > +# The MIME type of the body of the request. +# Reference: IETF RFC 7231 +# type: string +# maximum: 1 +# minimum: 1 +# 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 +# Version: +# description: > +# Version of the API used in the response. +# type: string +# maximum: 1 +# minimum: 1 +# schema: +# $ref: "../../definitions/SOL002SOL003VNFPerformanceManagement_def.yaml#/definitions/PmSubscription" +# 303: +# $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/303" +# 400: +# $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/400" +# 401: +# $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/401" +# 403: +# $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/403" +# 404: +# $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/404" +# 405: +# $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" +# 406: +# $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" +# 422: +# $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/422" +# 500: +# $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500" +# 503: +# $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" +# 504: +# $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" +# +# get: +# description: > +# Query Subscription Information. +# TThe client can use this method to query the list of active subscriptions +# to Performance management notifications subscribed by the client. +# This method shall follow the provisions specified in the tables 6.4.7.3.2-1 and 6.4.7.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 +# - name: filter +# description: > +# Attribute-based filtering expression according to clause 5.2 of ETSI GS NFV-SOL 013. +# The VNFM shall support receiving this parameter as part of the +# URI query string. The NFVO may supply this parameter. +# All attribute names that appear in the PmSubscription and in +# data types referenced from it shall be supported by the VNFM +# in the filter expression. +# in: query +# required: false +# type: string +# - name: nextpage_opaque_marker +# description: > +# Marker to obtain the next page of a paged response. Shall be +# supported by the VNFM if the VNFM supports alternative 2 (paging) +# according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 for this resource. +# in: query +# 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: +# 200: +# description: > +# 200 OK +# +# Shall be returned when the list of subscriptions has been queried successfully. +# The response body shall contain in an array the representations of all active subscriptions +# of the functional block that invokes the method, i.e. zero or more representations of +# PM subscriptions as defined in clause 6.5.2.3. +# If the "filter" URI parameter was supplied in the request, the data in the response body +# shall have been transformed according to the rules specified in clause 5.2.2 of ETSI GS NFV-SOL 013. +# If the VNFM 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: +# Content-Type: +# description: > +# The MIME type of the body of the request. +# Reference: IETF RFC 7231 +# type: string +# maximum: 1 +# minimum: 1 +# 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 +# Version: +# description: > +# Version of the API used in the response. +# type: string +# maximum: 1 +# minimum: 1 +# Link: +# description: > +# Reference to other resources. Used for paging in the present document, see clause 4.7.2.1. +# type: string +# maximum: 1 +# minimum: 0 +# schema: +# type: array +# items: +# $ref: "../../definitions/SOL002SOL003VNFPerformanceManagement_def.yaml#/definitions/PmSubscription" +# 400: +# $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/400" +# 401: +# $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/401" +# 403: +# $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/403" +# 404: +# $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/404" +# 405: +# $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" +# 406: +# $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" +# 422: +# $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/422" +# 500: +# $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500" +# 503: +# $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" +# 504: +# $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" +# +# ############################################################################### +# # Individual subscription # +# ############################################################################### +# '/subscriptions/{subscriptionId}': +# #SOL003 location: 6.4.8 +# parameters: +# - name: subscriptionId +# description: > +# This identifier can be retrieved from the resource referenced by the +# "Location" HTTP header in the response to a POST request creating a +# new "Individual subscription" resource. It can also be retrieved from the "id" +# attribute in the payload body of that response. +# in: path +# type: string +# required: true +# get: +# description: > +# Query Subscription Information. +# The client can use this method for reading an individual subscription about +# Performance management notifications subscribed by the client. +# This method shall follow the provisions specified in the tables 6.4.8.3.2-1 and 6.4.8.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 +# - name: Version +# description: > +# Version of the API requested to use when responding to this request. +# in: header +# required: true +# type: string +# responses: +# 200: +# description: > +# 200 OK +# +# Shall be returned when the subscription has been read successfully. +# The response body shall contain a representation of the "Individual subscription" resource, +# as defined in clause 6.5.2.3. +# headers: +# Content-Type: +# description: > +# The MIME type of the body of the request. +# Reference: IETF RFC 7231 +# type: string +# maximum: 1 +# minimum: 1 +# 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 +# Version: +# description: > +# Version of the API used in the response. +# type: string +# maximum: 1 +# minimum: 1 +# schema: +# $ref: "../../definitions/SOL002SOL003VNFPerformanceManagement_def.yaml#/definitions/PmSubscription" +# 400: +# $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/400" +# 401: +# $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/401" +# 403: +# $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/403" +# 404: +# $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/404" +# 405: +# $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" +# 406: +# $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" +# 422: +# $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/422" +# 500: +# $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500" +# 503: +# $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" +# 504: +# $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" +# +# delete: +# description: > +# Terminate Subscription. +# This method terminates an individual subscription. +# This method shall follow the provisions specified in the tables 6.4.8.3.5-1 and 6.4.8.3.5-2 +# for URI query parameters, request and response data structures, and response codes. +# As the result of successfully executing this method, the "Individual subscription" resource +# shall not exist any longer. This means that no notifications for that subscription shall +# be sent to the formerly-subscribed API consumer. +# +# NOTE: Due to race conditions, some notifications might still be received by the formerly-subscribed +# API consumer for a certain time period after the deletion. +# parameters: +# - 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 when the "Individual subscription" resource has been deleted 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 +# Version: +# description: > +# Version of the API used in the response. +# type: string +# maximum: 1 +# minimum: 1 +# 400: +# $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/400" +# 401: +# $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/401" +# 403: +# $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/403" +# 404: +# $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/404" +# 405: +# $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" +# 406: +# $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" +# 422: +# $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/422" +# 500: +# $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500" +# 503: +# $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" +# 504: +# $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" \ No newline at end of file diff --git a/src/SOL003/VNFPerformanceManagementNotification/VNFPerformanceManagementNotification.yaml b/src/SOL003/VNFPerformanceManagementNotification/VNFPerformanceManagementNotification.yaml index 19268878..c28018ca 100644 --- a/src/SOL003/VNFPerformanceManagementNotification/VNFPerformanceManagementNotification.yaml +++ b/src/SOL003/VNFPerformanceManagementNotification/VNFPerformanceManagementNotification.yaml @@ -1,7 +1,7 @@ swagger: "2.0" info: - version: "1.2.0-impl:etsi.org:ETSI_NFV_OpenAPI:1" + version: "2.0.0-impl:etsi.org:ETSI_NFV_OpenAPI:1" title: SOL003 - VNF Performance Management Notification interface description: > SOL003 - VNF Performance Management Notification interface @@ -25,8 +25,8 @@ info: url: https://forge.etsi.org/etsi-forge-copyright-notice.txt externalDocs: - description: ETSI GS NFV-SOL 003 V2.6.1 - url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.06.01_60/gs_NFV-SOL003v020601p.pdf + description: ETSI GS NFV-SOL 003 V2.7.1 + url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.07.01_60/gs_NFV-SOL003v020701p.pdf basePath: "/callback/v1" @@ -49,7 +49,7 @@ paths: Notify. The POST method delivers a notification regarding a performance management event from the server to the client.API producer to an API consumer. - The API consumer shall have previously created an "Individual subscription resource" with a matching filter. + The API consumer shall have previously created an "Individual PM Job" or "Individual threshold" resource. This method shall follow the provisions specified in the tables 6.4.9.3.1-1 and 6.4.9.3.1-2 for URI query parameters, request and response data structures, and response codes. parameters: @@ -118,8 +118,8 @@ paths: get: description: > - The GET method allows the server to test the notification endpoint that is provided by the client, - e.g. during subscription. + The GET method allows the server to test the notification endpoint that is provided by the API consumer, + e.g. during the creation of the PM job or threshold resource. This method shall follow the provisions specified in the tables 6.4.9.3.2-1 and 6.4.9.3.2-2 for URI query parameters, request and response data structures, and response codes. parameters: -- GitLab From 57c9ccc32fbce6948e0f39e4502ef0ffa5b1b284 Mon Sep 17 00:00:00 2001 From: Francesca Moscatelli Date: Wed, 5 Feb 2020 16:14:43 +0100 Subject: [PATCH 027/260] SOL003_084/085: PmSubscriptionRequest and PmSubscription deleted --- ...002SOL003VNFPerformanceManagement_def.yaml | 122 +++++++++--------- 1 file changed, 61 insertions(+), 61 deletions(-) diff --git a/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml b/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml index f462c3f8..c1ae9b5a 100644 --- a/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml +++ b/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml @@ -378,68 +378,68 @@ definitions: - ThresholdCrossedNotification - PerformanceInformationAvailableNotification - PmSubscription: - description: > - This type represents a subscription. - type: object - required: - - id - - callbackUri - - _links - properties: - id: - description: > - Identifier that identifies the subscription. - $ref: "SOL002SOL003_def.yaml#/definitions/Identifier" - filter: - description: > - Filter settings for this subscription, to define the subset of all - notifications this subscription relates to. A particular - notification is sent to the subscriber if the filter matches, or if - there is no filter. - $ref: "#/definitions/PmNotificationsFilter" - callbackUri: - description: > - The URI of the endpoint to send the notification to. - type: string - format: url - _links: - description: > - Links to resources related to this resource. - type: object - required: - - self - properties: - self: - description: > - URI of this resource. - $ref: "SOL002SOL003_def.yaml#/definitions/Link" +# PmSubscription: +# description: > +# This type represents a subscription. +# type: object +# required: +# - id +# - callbackUri +# - _links +# properties: +# id: +# description: > +# Identifier that identifies the subscription. +# $ref: "SOL002SOL003_def.yaml#/definitions/Identifier" +# filter: +# description: > +# Filter settings for this subscription, to define the subset of all +# notifications this subscription relates to. A particular +# notification is sent to the subscriber if the filter matches, or if +# there is no filter. +# $ref: "#/definitions/PmNotificationsFilter" +# callbackUri: +# description: > +# The URI of the endpoint to send the notification to. +# type: string +# format: url +# _links: +# description: > +# Links to resources related to this resource. +# type: object +# required: +# - self +# properties: +# self: +# description: > +# URI of this resource. +# $ref: "SOL002SOL003_def.yaml#/definitions/Link" - PmSubscriptionRequest: - description: > - This type represents a subscription request. - type: object - required: - - callbackUri - properties: - filter: - description: > - Filter settings for this subscription, to define the subset of all - notifications this subscription relates to. A particular - notification is sent to the subscriber if the filter matches, or if - there is no filter. - $ref: "#/definitions/PmNotificationsFilter" - callbackUri: - description: > - The URI of the endpoint to send the notification to. - type: string - format: url - authentication: - description: > - Authentication parameters to configure the use of Authorization when sending notifications - corresponding 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: "SOL002SOL003_def.yaml#/definitions/SubscriptionAuthentication" +# PmSubscriptionRequest: +# description: > +# This type represents a subscription request. +# type: object +# required: +# - callbackUri +# properties: +# filter: +# description: > +# Filter settings for this subscription, to define the subset of all +# notifications this subscription relates to. A particular +# notification is sent to the subscriber if the filter matches, or if +# there is no filter. +# $ref: "#/definitions/PmNotificationsFilter" +# callbackUri: +# description: > +# The URI of the endpoint to send the notification to. +# type: string +# format: url +# authentication: +# description: > +# Authentication parameters to configure the use of Authorization when sending notifications +# corresponding 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: "SOL002SOL003_def.yaml#/definitions/SubscriptionAuthentication" Threshold: description: > -- GitLab From f521f64514e52a0d44f854ebda01a6a9afab1166 Mon Sep 17 00:00:00 2001 From: Francesca Moscatelli Date: Wed, 5 Feb 2020 16:30:52 +0100 Subject: [PATCH 028/260] SOL003_086: ThresholdCrossedNotification updated --- ...002SOL003VNFPerformanceManagement_def.yaml | 24 ++++++++++--------- 1 file changed, 13 insertions(+), 11 deletions(-) diff --git a/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml b/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml index c1ae9b5a..08601375 100644 --- a/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml +++ b/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml @@ -592,10 +592,6 @@ definitions: type: string enum: - ThresholdCrossedNotification - subscriptionId: - description: > - Identifier of the subscription that this notification relates to. - $ref: "SOL002SOL003_def.yaml#/definitions/Identifier" timeStamp: description: > Date and time of the generation of the notification. @@ -609,6 +605,11 @@ definitions: An indication of whether the threshold was crossed in upward or downward direction. $ref: "#/definitions/CrossingDirectionType" + objectType: + description: > + Type of the measured object. + The applicable measured object type for a measurement is defined in clause 7.2 of ETSI GS NFV-IFA 027. + type: string objectInstanceId: description: > Identifier that identifies a VNF instance. @@ -633,22 +634,23 @@ definitions: The type of this attribute shall correspond to the related "Measurement Unit" as defined in clause 7.2 of ETSI GS NFV-IFA 027. type: object + context: + description: > + Measurement context information related to the measured value. + The set of applicable keys is defined per measurement in the + related "Measurement Context" in clause 7.2 of ETSI GS NFV-IFA 027. + $ref: "SOL002SOL003_def.yaml#/definitions/KeyValuePairs" _links: description: > Links to resources related to this notification. type: object required: - - subscription - threshold properties: - subscription: - description: > - Link to the related subscription. - $ref: "SOL002SOL003_def.yaml#/definitions/NotificationLink" objectInstance: description: > - Link to the resource representing the VNF instance to which the - notified change applies. Shall be present if the VNF instance + Link to the resource representing the measured object instance to which the + notified change applies. Shall be present if the measured object instance information is accessible as a resource. $ref: "SOL002SOL003_def.yaml#/definitions/NotificationLink" threshold: -- GitLab From 210e819dd89aca3c84270a865c41149430f5fd42 Mon Sep 17 00:00:00 2001 From: Francesca Moscatelli Date: Wed, 5 Feb 2020 16:36:29 +0100 Subject: [PATCH 029/260] SOL003_084/085: fix --- ...002SOL003VNFPerformanceManagement_def.yaml | 122 +++++++++--------- 1 file changed, 61 insertions(+), 61 deletions(-) diff --git a/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml b/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml index 08601375..8341485c 100644 --- a/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml +++ b/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml @@ -378,68 +378,68 @@ definitions: - ThresholdCrossedNotification - PerformanceInformationAvailableNotification -# PmSubscription: -# description: > -# This type represents a subscription. -# type: object -# required: -# - id -# - callbackUri -# - _links -# properties: -# id: -# description: > -# Identifier that identifies the subscription. -# $ref: "SOL002SOL003_def.yaml#/definitions/Identifier" -# filter: -# description: > -# Filter settings for this subscription, to define the subset of all -# notifications this subscription relates to. A particular -# notification is sent to the subscriber if the filter matches, or if -# there is no filter. -# $ref: "#/definitions/PmNotificationsFilter" -# callbackUri: -# description: > -# The URI of the endpoint to send the notification to. -# type: string -# format: url -# _links: -# description: > -# Links to resources related to this resource. -# type: object -# required: -# - self -# properties: -# self: -# description: > -# URI of this resource. -# $ref: "SOL002SOL003_def.yaml#/definitions/Link" + PmSubscription: + description: > + This type represents a subscription. + type: object + required: + - id + - callbackUri + - _links + properties: + id: + description: > + Identifier that identifies the subscription. + $ref: "SOL002SOL003_def.yaml#/definitions/Identifier" + filter: + description: > + Filter settings for this subscription, to define the subset of all + notifications this subscription relates to. A particular + notification is sent to the subscriber if the filter matches, or if + there is no filter. + $ref: "#/definitions/PmNotificationsFilter" + callbackUri: + description: > + The URI of the endpoint to send the notification to. + type: string + format: url + _links: + description: > + Links to resources related to this resource. + type: object + required: + - self + properties: + self: + description: > + URI of this resource. + $ref: "SOL002SOL003_def.yaml#/definitions/Link" -# PmSubscriptionRequest: -# description: > -# This type represents a subscription request. -# type: object -# required: -# - callbackUri -# properties: -# filter: -# description: > -# Filter settings for this subscription, to define the subset of all -# notifications this subscription relates to. A particular -# notification is sent to the subscriber if the filter matches, or if -# there is no filter. -# $ref: "#/definitions/PmNotificationsFilter" -# callbackUri: -# description: > -# The URI of the endpoint to send the notification to. -# type: string -# format: url -# authentication: -# description: > -# Authentication parameters to configure the use of Authorization when sending notifications -# corresponding 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: "SOL002SOL003_def.yaml#/definitions/SubscriptionAuthentication" + PmSubscriptionRequest: + description: > + This type represents a subscription request. + type: object + required: + - callbackUri + properties: + filter: + description: > + Filter settings for this subscription, to define the subset of all + notifications this subscription relates to. A particular + notification is sent to the subscriber if the filter matches, or if + there is no filter. + $ref: "#/definitions/PmNotificationsFilter" + callbackUri: + description: > + The URI of the endpoint to send the notification to. + type: string + format: url + authentication: + description: > + Authentication parameters to configure the use of Authorization when sending notifications + corresponding 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: "SOL002SOL003_def.yaml#/definitions/SubscriptionAuthentication" Threshold: description: > -- GitLab From 8e25d633d78df55cea1554b333f62746a572a198 Mon Sep 17 00:00:00 2001 From: Francesca Moscatelli Date: Wed, 5 Feb 2020 17:39:14 +0100 Subject: [PATCH 030/260] SOL003_087: PerformanceInformationAvailableNotification updated --- ...002SOL003VNFPerformanceManagement_def.yaml | 31 ++++++++++++------- 1 file changed, 19 insertions(+), 12 deletions(-) diff --git a/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml b/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml index 8341485c..a031447a 100644 --- a/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml +++ b/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml @@ -75,35 +75,42 @@ definitions: type: string enum: - PerformanceInformationAvailableNotification - subscriptionId: - description: > - Identifier of the subscription that this notification relates to. - $ref: "SOL002SOL003_def.yaml#/definitions/Identifier" timeStamp: description: > Date and time of the generation of the notification. $ref: "SOL002SOL003_def.yaml#/definitions/DateTime" + objectType: + description: > + Type of the measured object. + The applicable measured object type for a measurement + is defined in clause 7.2 of ETSI GS NFV-IFA 027. + type: string objectInstanceId: description: > - Identifier that identifies a VNF instance. + Identifier of the measured object instance. as per clause 6.2 of ETSI GS NFV-IFA 027. $ref: "SOL002SOL003_def.yaml#/definitions/Identifier" + subObjectInstanceIds: + description: > + Identifiers of the sub-object instances of the measured + object instance for which the measurements have been taken. + Shall be present if the related PM job has been set up to + measure only a subset of all sub-object instances of the + measured object instance and a sub-object is defined in clause + 6.2 of ETSI GS NFV-IFA 027 for the related measured object type. + Shall be absent otherwise. + $ref: "SOL002SOL003_def.yaml#/definitions/IdentifierInVnf" _links: description: > Links to resources related to this notification. type: object required: - - subscription - pmJob - performanceReport properties: - subscription: - description: > - Link to the related subscription. - $ref: "SOL002SOL003_def.yaml#/definitions/NotificationLink" objectInstance: description: > - Link to the resource representing the VNF instance to which the - notified change applies. Shall be present if the VNF instance + Link to the resource representing the measured object instance to which the + notified change applies. Shall be present if the measured object instance information is accessible as a resource. $ref: "SOL002SOL003_def.yaml#/definitions/NotificationLink" pmJob: -- GitLab From f3bdc511f25e0c352a2431cb648985371a74f052 Mon Sep 17 00:00:00 2001 From: Francesca Moscatelli Date: Wed, 5 Feb 2020 18:02:23 +0100 Subject: [PATCH 031/260] SOL003_088: CreatePmJobRequest updated --- ...002SOL003VNFPerformanceManagement_def.yaml | 39 ++++++++++++++++++- 1 file changed, 37 insertions(+), 2 deletions(-) diff --git a/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml b/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml index a031447a..1648b4a1 100644 --- a/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml +++ b/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml @@ -24,19 +24,54 @@ definitions: This type represents a request to create a PM job. type: object required: + - objectType + - objectInstanceIds - criteria + - callbackUri properties: + objectType: + description: > + Type of the measured object. + The applicable measured object type for a measurement + is defined in clause 7.2 of ETSI GS NFV-IFA 027. + type: string objectInstanceIds: description: > - Identifiers of the VNF instances for which performance information - is requested to be collected. + Identifiers of the measured object instances for + which performance information is requested to be collected. type: array items: $ref: "SOL002SOL003_def.yaml#/definitions/Identifier" + subObjectInstanceIds: + description: > + Identifiers of the sub-object instances of the measured + object instance for which performance information is requested to be collected. + May be present if a sub-object is defined in clause 6.2 + of ETSI GS NFV-IFA 027for the related measured object type. + If this attribute is present, the cardinality of the "objectInstanceIds" + attribute shall be 1. + If this attribute is absent and a sub-object is defined in clause 6.2 + of ETSI GS NFV IFA 027 for the related measured object type, measurements + will be taken for all sub-object instances of the measured object instance. + type: array + item: + $ref: "SOL002SOL003_def.yaml#/definitions/IdentifierInVnf" criteria: description: > Criteria of the collection of performance information. $ref: "#/definitions/PmJobCriteria" + callbackUri: + description: > + The URI of the endpoint to send the notification to. + $ref: "SOL002SOL003_def.yaml#/definitions/Uri" + authentication: + description: > + Authentication parameters to configure the use of Authorization + when sending notifications corresponding to this PM job, as defined + in clause 8.3.4 of ETSI GS NFV-SOL 013. + This attribute shall only be present if the API consumer + requires authorization of notifications. + $ref: "SOL002SOL003_def.yaml#/definitions/SubscriptionAuthentication" CrossingDirectionType: type: string -- GitLab From abce1576dae41ea8386d648f1f60b1dc94d480bc Mon Sep 17 00:00:00 2001 From: Francesca Moscatelli Date: Wed, 5 Feb 2020 18:14:14 +0100 Subject: [PATCH 032/260] SOL003_089: PmJob updated --- ...002SOL003VNFPerformanceManagement_def.yaml | 32 +++++++++++++++++-- 1 file changed, 29 insertions(+), 3 deletions(-) diff --git a/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml b/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml index 1648b4a1..4c7aceb8 100644 --- a/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml +++ b/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml @@ -239,13 +239,21 @@ definitions: type: object required: - id + - objectType - objectInstanceIds - criteria + - callbackUri properties: id: description: > Identifier of this PM job. $ref: "SOL002SOL003_def.yaml#/definitions/Identifier" + objectType: + description: > + Type of the measured object. + The applicable measured object type for a measurement + is defined in clause 7.2 of ETSI GS NFV-IFA 027. + $ref: "SOL002SOL003_def.yaml#/definitions/Identifier" objectInstanceIds: description: > Identifiers of the VNF instances for which performance information @@ -253,10 +261,28 @@ definitions: type: array items: $ref: "SOL002SOL003_def.yaml#/definitions/Identifier" + subObjectInstanceIds: + description: > + Identifiers of the sub-object instances of the measured object + instance for which performance information is requested to be collected. + May be present if a sub-object is defined in clause 6.2 of + ETSI GS NFV-IFA 027 for the related measured object type. + If this attribute is present, the cardinality of the "objectInstanceIds" + attribute shall be 1. + If this attribute is absent and a sub-object is defined in clause 6.2 of + ETSI GS NFV IFA 027 for the related measured object type, measurements will + be taken for all sub-object instances of the measured object instance. + type: array + items: + $ref: "SOL002SOL003_def.yaml#/definitions/IdentifierInVnf" criteria: description: > Criteria of the collection of performance information. $ref: "#/definitions/PmJobCriteria" + callbackUri: + description: > + The URI of the endpoint to send the notification to. + $ref: "SOL002SOL003_def.yaml#/definitions/Uri" reports: description: > Information about available reports collected by this PM job. @@ -268,7 +294,7 @@ definitions: properties: href: description: > - The Uri where the report can be obtained. + The URI where the report can be obtained. type: string format: url readyTime: @@ -308,9 +334,9 @@ definitions: $ref: "SOL002SOL003_def.yaml#/definitions/Link" objects: description: > - Links to resources representing the VNF instances for which + Links to resources representing the measured object instances for which performance information is collected. Shall be present if - the VNF instance information is accessible as a resource. + the measured object instance information is accessible as a resource. type: array items: $ref: "SOL002SOL003_def.yaml#/definitions/Link" -- GitLab From 168efa1157ba812af2edc8200b54dc854c623816 Mon Sep 17 00:00:00 2001 From: Francesca Moscatelli Date: Wed, 5 Feb 2020 18:20:41 +0100 Subject: [PATCH 033/260] SOL003_089: fix --- src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml b/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml index 4c7aceb8..c68cf954 100644 --- a/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml +++ b/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml @@ -133,7 +133,9 @@ definitions: measured object instance and a sub-object is defined in clause 6.2 of ETSI GS NFV-IFA 027 for the related measured object type. Shall be absent otherwise. - $ref: "SOL002SOL003_def.yaml#/definitions/IdentifierInVnf" + type: array + items: + $ref: "SOL002SOL003_def.yaml#/definitions/IdentifierInVnf" _links: description: > Links to resources related to this notification. -- GitLab From 3c3e4d229dc0eb12f64f46bf8a3a843457b28d71 Mon Sep 17 00:00:00 2001 From: Francesca Moscatelli Date: Wed, 5 Feb 2020 18:38:37 +0100 Subject: [PATCH 034/260] SOL003_089: fix --- src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml b/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml index c68cf954..f2dae5a6 100644 --- a/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml +++ b/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml @@ -54,7 +54,7 @@ definitions: of ETSI GS NFV IFA 027 for the related measured object type, measurements will be taken for all sub-object instances of the measured object instance. type: array - item: + items: $ref: "SOL002SOL003_def.yaml#/definitions/IdentifierInVnf" criteria: description: > -- GitLab From e93b111be0959b899e33f25f69eef26908f99fd0 Mon Sep 17 00:00:00 2001 From: Francesca Moscatelli Date: Thu, 6 Feb 2020 12:59:18 +0100 Subject: [PATCH 035/260] SOL003_090: CreateThresholdRequest updated --- ...002SOL003VNFPerformanceManagement_def.yaml | 33 +++++++++++++++++++ 1 file changed, 33 insertions(+) diff --git a/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml b/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml index f2dae5a6..03c650af 100644 --- a/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml +++ b/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml @@ -7,17 +7,50 @@ definitions: This type represents a request to create a threshold. type: object required: + - objectType - objectInstanceId - criteria + - callbackUri properties: + objectType: + description: > + Type of the measured object. + The applicable measured object type for a measurement + is defined in clause 7.2 of ETSI GS NFV-IFA 027. + type: string objectInstanceId: description: > Identifier of the VNF instance associated with this threshold. $ref: "SOL002SOL003_def.yaml#/definitions/Identifier" + subObjectInstanceIds: + description: > + Identifiers of the sub-object instances of the measured + object instance associated with this threshold. + May be present if a sub-object is defined in clause 6.2 + of ETSI GS NFV-IFA 027 for the related measured object type. + If this attribute is absent and a sub-object is defined in + clause 6.2 of ETSI GS NFV-IFA 027 for the measured object type, + measurements will be taken for all sub-object instances of + the measured object instance. + type: array + items: + $ref: "SOL002SOL003_def.yaml#/definitions/IdentifierInVnf" criteria: description: > Criteria that define this threshold. $ref: "#/definitions/ThresholdCriteria" + callbackUri: + description: > + The URI of the endpoint to send the notification to. + $ref: "SOL002SOL003_def.yaml#/definitions/Uri" + authentication: + description: > + Authentication parameters to configure the use of Authorization + when sending notifications corresponding to this threshold, + as defined in clause 8.3.4 of ETSI GS NFV-SOL 013. + This attribute shall only be present if the API consumer requires + authorization of notifications. + $ref: "SOL002SOL003_def.yaml#/definitions/SubscriptionAuthentication" CreatePmJobRequest: description: > -- GitLab From ca034dafb9fbace4557673ee1cad169a929ba84b Mon Sep 17 00:00:00 2001 From: Francesca Moscatelli Date: Thu, 6 Feb 2020 14:25:46 +0100 Subject: [PATCH 036/260] SOL003_91: Threshold updated --- ...002SOL003VNFPerformanceManagement_def.yaml | 29 +++++++++++++++++-- 1 file changed, 27 insertions(+), 2 deletions(-) diff --git a/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml b/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml index 03c650af..06eb4dc0 100644 --- a/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml +++ b/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml @@ -550,22 +550,47 @@ definitions: type: object required: - id + - objectType - objectInstanceId - criteria + - callbackUri - _links properties: id: description: > Identifier of this threshold resource. $ref: "SOL002SOL003_def.yaml#/definitions/Identifier" + objectType: + description: > + Type of the measured object. + The applicable measured object type for a measurement + is defined in clause 7.2 of ETSI GS NFV-IFA 027. + type: string objectInstanceId: description: > Identifier of the VNF instance associated with the threshold. $ref: "SOL002SOL003_def.yaml#/definitions/Identifier" + subObjectInstanceIds: + description: > + Identifiers of the sub-object instances of the measured object + instance associated with the threshold. + May be present if a sub-object is defined in clause 6.2 of + ETSI GS NFV-IFA 027 for the related measurement type. + If this attribute is absent and a sub-object is defined in clause 6.2 + of ETSI GS NFV-IFA 027 for the related measured object type, + measurements will be taken for all sub-object instances of the + measured object instance. + type: array + items: + $ref: "SOL002SOL003_def.yaml#/definitions/IdentifierInVnf" criteria: description: > Criteria that define this threshold. $ref: "#/definitions/ThresholdCriteria" + callbackUri: + description: > + The URI of the endpoint to send the notification to. + $ref: "SOL002SOL003_def.yaml#/definitions/Uri" _links: description: > Links for this resource. @@ -579,9 +604,9 @@ definitions: $ref: "SOL002SOL003_def.yaml#/definitions/Link" object: description: > - Link to a resource representing the VNF instance for which + Link to a resource representing the measured object instance for which performance information is collected. Shall be present if the - VNF instance information is accessible as a resource. + measured object instance information is accessible as a resource. ThresholdModifications: description: > -- GitLab From 6a97b1f7d63104c56089da17a8f4e7c7b9bee6fb Mon Sep 17 00:00:00 2001 From: Francesca Moscatelli Date: Thu, 6 Feb 2020 14:36:47 +0100 Subject: [PATCH 037/260] SOL003_92: PerformanceReport updated --- ...002SOL003VNFPerformanceManagement_def.yaml | 25 +++++++++++-------- 1 file changed, 15 insertions(+), 10 deletions(-) diff --git a/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml b/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml index 06eb4dc0..1a132e31 100644 --- a/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml +++ b/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml @@ -218,23 +218,22 @@ definitions: properties: objectType: description: > - Defines the object type for which performance information is - reported (i.e. VNF type). The string value shall be set to the - vnfdId of the VNF instance to which the performance - information relates. + Type of the measured object. + The applicable measured object type for a measurement is defined + in clause 7.2 of ETSI GS NFV-IFA 027. type: string objectInstanceId: description: > - The object instance (i.e. VNF instance) for which the - performance metric is reported. + Identifier of the measured object instance for which the performance metric is reported $ref: "SOL002SOL003_def.yaml#/definitions/Identifier" subObjectInstanceId: description: > - Identifier of the sub-object of the measured object (i.e. a VNFC instance) + Identifier of the sub-object instance of the measured object (i.e. of the measured object instance) for which the performance metric is reported. - Shall be present if this is required in the measurement specification. - The sub-object allows to structure the measured object, - but is not to be confused with sub-counters which allow to structure the measurement. + Shall be present if this is required in clause 6.2 of ETSI GS NFV-IFA 027 + for the related measured object type. + The sub-object allows to structure the measured object but is not to be confused + with sub-counters which allow to structure the measurement value. EXAMPLE: Measured object: VnfInstanceXYZ Sub-object: VnfcInstance1 @@ -267,6 +266,12 @@ definitions: The type of this attribute shall correspond to the related "Measurement Unit" as defined in clause 7.2. of ETSI GS NFV-IFA 027. type: object + context: + description: > + Measurement context information related to the measured value. + The set of applicable keys is defined per measurement in the + related "Measurement Context" in clause 7.2 of ETSI GS NFV-IFA 027. + $ref: "SOL002SOL003_def.yaml#/definitions/KeyValuePairs" PmJob: description: > -- GitLab From a436c196b65eda84c1b92a331d123e774773e263 Mon Sep 17 00:00:00 2001 From: Francesca Moscatelli Date: Thu, 6 Feb 2020 16:15:01 +0100 Subject: [PATCH 038/260] SOL003_95: PmNotificationFilter deleted --- ...002SOL003VNFPerformanceManagement_def.yaml | 46 +++++++++---------- 1 file changed, 23 insertions(+), 23 deletions(-) diff --git a/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml b/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml index 1a132e31..9c02a8c0 100644 --- a/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml +++ b/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml @@ -462,29 +462,29 @@ definitions: reporting up to the boundary. $ref: "SOL002SOL003_def.yaml#/definitions/DateTime" - PmNotificationsFilter: - description: > - This type represents a filter that can be used to subscribe for - notifications related to performance management events. - type: object - properties: - vnfInstanceSubscriptionFilter: - description: > - Filter criteria to select VNF instances about which to notify. - $ref: "SOL002SOL003_def.yaml#/definitions/VnfInstanceSubscriptionFilter" - notificationTypes: - description: > - Match particular notification types. - Permitted values: - * ThresholdCrossedNotification - * PerformanceInformationAvailableNotification - The permitted values of the "notificationTypes" attribute are - spelled exactly as the names of the notification types to facilitate - automated code generation systems. - type: string - enum: - - ThresholdCrossedNotification - - PerformanceInformationAvailableNotification +# PmNotificationsFilter: +# description: > +# This type represents a filter that can be used to subscribe for +# notifications related to performance management events. +# type: object +# properties: +# vnfInstanceSubscriptionFilter: +# description: > +# Filter criteria to select VNF instances about which to notify. +# $ref: "SOL002SOL003_def.yaml#/definitions/VnfInstanceSubscriptionFilter" +# notificationTypes: +# description: > +# Match particular notification types. +# Permitted values: +# * ThresholdCrossedNotification +# * PerformanceInformationAvailableNotification +# The permitted values of the "notificationTypes" attribute are +# spelled exactly as the names of the notification types to facilitate +# automated code generation systems. +# type: string +# enum: +# - ThresholdCrossedNotification +# - PerformanceInformationAvailableNotification PmSubscription: description: > -- GitLab From 868502235bffd8302be7eb95363e0d1320dcc0d1 Mon Sep 17 00:00:00 2001 From: Francesca Moscatelli Date: Thu, 6 Feb 2020 16:27:30 +0100 Subject: [PATCH 039/260] SOL003_95: fix --- ...002SOL003VNFPerformanceManagement_def.yaml | 46 +++++++++---------- 1 file changed, 23 insertions(+), 23 deletions(-) diff --git a/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml b/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml index 9c02a8c0..1a132e31 100644 --- a/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml +++ b/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml @@ -462,29 +462,29 @@ definitions: reporting up to the boundary. $ref: "SOL002SOL003_def.yaml#/definitions/DateTime" -# PmNotificationsFilter: -# description: > -# This type represents a filter that can be used to subscribe for -# notifications related to performance management events. -# type: object -# properties: -# vnfInstanceSubscriptionFilter: -# description: > -# Filter criteria to select VNF instances about which to notify. -# $ref: "SOL002SOL003_def.yaml#/definitions/VnfInstanceSubscriptionFilter" -# notificationTypes: -# description: > -# Match particular notification types. -# Permitted values: -# * ThresholdCrossedNotification -# * PerformanceInformationAvailableNotification -# The permitted values of the "notificationTypes" attribute are -# spelled exactly as the names of the notification types to facilitate -# automated code generation systems. -# type: string -# enum: -# - ThresholdCrossedNotification -# - PerformanceInformationAvailableNotification + PmNotificationsFilter: + description: > + This type represents a filter that can be used to subscribe for + notifications related to performance management events. + type: object + properties: + vnfInstanceSubscriptionFilter: + description: > + Filter criteria to select VNF instances about which to notify. + $ref: "SOL002SOL003_def.yaml#/definitions/VnfInstanceSubscriptionFilter" + notificationTypes: + description: > + Match particular notification types. + Permitted values: + * ThresholdCrossedNotification + * PerformanceInformationAvailableNotification + The permitted values of the "notificationTypes" attribute are + spelled exactly as the names of the notification types to facilitate + automated code generation systems. + type: string + enum: + - ThresholdCrossedNotification + - PerformanceInformationAvailableNotification PmSubscription: description: > -- GitLab From 8836e14d09997e757af1ee6ec0716dcd14766df3 Mon Sep 17 00:00:00 2001 From: Francesca Moscatelli Date: Thu, 6 Feb 2020 17:03:12 +0100 Subject: [PATCH 040/260] SOL003_95: fix --- src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml b/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml index 1a132e31..bdc9844b 100644 --- a/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml +++ b/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml @@ -224,7 +224,7 @@ definitions: type: string objectInstanceId: description: > - Identifier of the measured object instance for which the performance metric is reported + Identifier of the measured object instance for which the performance metric is reported $ref: "SOL002SOL003_def.yaml#/definitions/Identifier" subObjectInstanceId: description: > -- GitLab From 6d8beab0cc621fb9584697ec67df2d2018ad00d0 Mon Sep 17 00:00:00 2001 From: Francesca Moscatelli Date: Thu, 6 Feb 2020 17:19:26 +0100 Subject: [PATCH 041/260] SOL003_100->108: fixes in API methods' description --- .../VNFFaultManagement.yaml | 44 +++++++++---------- 1 file changed, 22 insertions(+), 22 deletions(-) diff --git a/src/SOL003/VNFFaultManagement/VNFFaultManagement.yaml b/src/SOL003/VNFFaultManagement/VNFFaultManagement.yaml index 2d3c48a6..5cdf76a6 100644 --- a/src/SOL003/VNFFaultManagement/VNFFaultManagement.yaml +++ b/src/SOL003/VNFFaultManagement/VNFFaultManagement.yaml @@ -25,8 +25,8 @@ info: url: https://forge.etsi.org/etsi-forge-copyright-notice.txt externalDocs: - description: ETSI GS NFV-SOL 003 V2.6.1 - url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.06.01_60/gs_NFV-SOL003v020601p.pdf + description: ETSI GS NFV-SOL 003 V2.7.1 + url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.07.01_60/gs_NFV-SOL003v020701p.pdf basePath: "/vnffm/v1" @@ -53,7 +53,7 @@ paths: get: description: > Get Alarm List. - The client can use this method to retrieve information about the alarm list. + The API consumer can use this method to retrieve information about the alarm list. This method shall follow the provisions specified in the tables 7.4.2.3.2-1 and 7.4.2.3.2-2 for URI query parameters, request and response data structures, and response codes. parameters: @@ -172,7 +172,7 @@ paths: required: true get: description: > - The client can use this method to read an individual alarm. + The API consumer can use this method to read an individual alarm. This method shall follow the provisions specified in the tables 7.4.3.3.2-1 and 7.4.3.3.2-2 for URI query parameters, request and response data structures, and response codes. parameters: @@ -322,13 +322,13 @@ paths: 406: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" 409: - description: > - 409 CONFLICT - - Shall be returned upon the following error: The operation cannot be executed currently, - due to a conflict with the state of the "Individual alarm" resource. - Typically, this is due to the fact that the alarm is already in the state that is - requested to be set (such as trying to acknowledge an already-acknowledged alarm). +# description: > +# 409 CONFLICT +# +# Shall be returned upon the following error: The operation cannot be executed currently, +# due to a conflict with the state of the "Individual alarm" resource. +# Typically, this is due to the fact that the alarm is already in the state that is +# requested to be set (such as trying to acknowledge an already-acknowledged alarm). $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" 412: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/412" @@ -431,17 +431,17 @@ paths: schema: $ref: "../../definitions/SOL002SOL003VNFFaultManagement_def.yaml#/definitions/FmSubscription" 303: - description: > - 303 SEE OTHER - - Shall be returned when a subscription with the - same callbackURI and the same filter already exists - and the policy of the VNFM is to not create - redundant subscriptions. - The HTTP response shall include a "Location" - HTTP header that contains the resource URI of the - existing "Individual subscription" resource. - The response body shall be empty. +# description: > +# 303 SEE OTHER +# +# Shall be returned when a subscription with the +# same callbackURI and the same filter already exists +# and the policy of the VNFM is to not create +# redundant subscriptions. +# The HTTP response shall include a "Location" +# HTTP header that contains the resource URI of the +# existing "Individual subscription" resource. +# The response body shall be empty. $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/303" 400: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/400" -- GitLab From 619e042071b84633292731d0d3b66e9437df82e0 Mon Sep 17 00:00:00 2001 From: Francesca Moscatelli Date: Thu, 6 Feb 2020 17:35:40 +0100 Subject: [PATCH 042/260] SOL003_109: Alarm updated --- .../VNFFaultManagement/VNFFaultManagement.yaml | 2 +- .../VNFFaultManagementNotification.yaml | 12 ++++++------ .../SOL002SOL003VNFFaultManagement_def.yaml | 9 +++++++-- 3 files changed, 14 insertions(+), 9 deletions(-) diff --git a/src/SOL003/VNFFaultManagement/VNFFaultManagement.yaml b/src/SOL003/VNFFaultManagement/VNFFaultManagement.yaml index 5cdf76a6..e6f40394 100644 --- a/src/SOL003/VNFFaultManagement/VNFFaultManagement.yaml +++ b/src/SOL003/VNFFaultManagement/VNFFaultManagement.yaml @@ -469,7 +469,7 @@ paths: Query Subscription Information - The client can use this method to retrieve the list of active + The API consumer can use this method to retrieve the list of active subscriptions for VNF alarms subscribed by the client. It can be used e.g. for resynchronization after error situations. parameters: diff --git a/src/SOL003/VNFFaultManagementNotification/VNFFaultManagementNotification.yaml b/src/SOL003/VNFFaultManagementNotification/VNFFaultManagementNotification.yaml index f99c9621..bf184d75 100644 --- a/src/SOL003/VNFFaultManagementNotification/VNFFaultManagementNotification.yaml +++ b/src/SOL003/VNFFaultManagementNotification/VNFFaultManagementNotification.yaml @@ -1,7 +1,7 @@ swagger: "2.0" info: - version: "1.2.0-impl:etsi.org:ETSI_NFV_OpenAPI:1" + version: "1.3.0-impl:etsi.org:ETSI_NFV_OpenAPI:1" title: SOL003 - VNF Fault Management Notification interface description: > SOL003 - VNF Fault Management Notification interface @@ -25,8 +25,8 @@ info: url: https://forge.etsi.org/etsi-forge-copyright-notice.txt externalDocs: - description: ETSI GS NFV-SOL 003 V2.6.1 - url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.06.01_60/gs_NFV-SOL003v020601p.pdf + description: ETSI GS NFV-SOL 003 V2.7.1 + url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.07.01_60/gs_NFV-SOL003v020701p.pdf basePath: "/callback/v1" @@ -119,7 +119,7 @@ paths: get: description: > - The GET method allows the server to test the notification endpoint that is provided by the client, + The GET method allows the server to test the notification endpoint that is provided by the API consumer, e.g. during subscription. This method shall follow the provisions specified in the tables 7.4.6.3.2-1 and 7.4.6.3.2-2 for URI query parameters, request and response data structures, and response codes. @@ -254,7 +254,7 @@ paths: get: description: > - The GET method allows the server to test the notification endpoint that is provided by the client, + The GET method allows the server to test the notification endpoint that is provided by the API consumer, e.g. during subscription. This method shall follow the provisions specified in the tables 7.4.6.3.2-1 and 7.4.6.3.2-2 for URI query parameters, request and response data structures, and response codes. @@ -389,7 +389,7 @@ paths: get: description: > - The GET method allows the server to test the notification endpoint that is provided by the client, + The GET method allows the server to test the notification endpoint that is provided by the API consumer, e.g. during subscription. This method shall follow the provisions specified in the tables 7.4.6.3.2-1 and 7.4.6.3.2-2 for URI query parameters, request and response data structures, and response codes. diff --git a/src/definitions/SOL002SOL003VNFFaultManagement_def.yaml b/src/definitions/SOL002SOL003VNFFaultManagement_def.yaml index 7702495b..9fdf9b88 100644 --- a/src/definitions/SOL002SOL003VNFFaultManagement_def.yaml +++ b/src/definitions/SOL002SOL003VNFFaultManagement_def.yaml @@ -72,7 +72,6 @@ definitions: required: - id - managedObjectId - - rootCauseFaultyResource - alarmRaisedTime - ackState - perceivedSeverity @@ -93,6 +92,7 @@ definitions: rootCauseFaultyResource: description: > The virtualised resources that are causing the VNF fault. + Shall be present if the alarm affects virtualized resources. $ref: "#/definitions/FaultyResourceInfo" alarmRaisedTime: description: > @@ -109,6 +109,11 @@ definitions: Time stamp indicating when the alarm was cleared. It shall be present if the alarm has been cleared. $ref: "SOL002SOL003_def.yaml#/definitions/DateTime" + alarmAcknowledgedTime: + description: > + Time stamp indicating when the alarm was acknowledged. + It shall be present if the alarm has been acknowledged. + $ref: "SOL002SOL003_def.yaml#/definitions/DateTime" ackState: description: > Acknowledgement state of the alarm. @@ -143,7 +148,7 @@ definitions: description: > Attribute indicating if this fault is the root for other correlated alarms. If true, then the alarms listed in the attribute - CorrelatedAlarmId are caused by this fault. + "correlatedAlarmId" are caused by this fault. type: boolean correlatedAlarmIds: description: > -- GitLab From 1beaaf7457b78080a08056a80847e417acb85a38 Mon Sep 17 00:00:00 2001 From: Francesca Moscatelli Date: Thu, 6 Feb 2020 17:39:28 +0100 Subject: [PATCH 043/260] SOL003_110: AlarmModifications updated --- src/definitions/SOL002SOL003VNFFaultManagement_def.yaml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/src/definitions/SOL002SOL003VNFFaultManagement_def.yaml b/src/definitions/SOL002SOL003VNFFaultManagement_def.yaml index 9fdf9b88..6573a27e 100644 --- a/src/definitions/SOL002SOL003VNFFaultManagement_def.yaml +++ b/src/definitions/SOL002SOL003VNFFaultManagement_def.yaml @@ -300,7 +300,8 @@ definitions: rebuilt, e.g. if the VNFM detects its storage holding the alarm list is corrupted. The notification shall be triggered by the VNFM when the alarm list has - been rebuilt. + been rebuilt, e.g. because the VNFM has detected that its storage + holding the alarm list was corrupted. type: object required: - id @@ -362,9 +363,11 @@ definitions: New value of the "ackState" attribute in "Alarm". Permitted values: * ACKNOWLEDGED + * UNACKNOWLEDGED type: string enum: - ACKNOWLEDGED + - UNACKNOWLEDGED EventType: description: > -- GitLab From 16cd89dd8307fe711e9cf13a91e892e32bc1b0b3 Mon Sep 17 00:00:00 2001 From: Francesca Moscatelli Date: Thu, 6 Feb 2020 18:11:54 +0100 Subject: [PATCH 044/260] SOL003_127/128: Grant and PlacementConstraint updated --- src/SOL003/VNFIndicator/VNFIndicator.yaml | 22 +++++++++---------- .../VNFLifecycleOperationGranting_def.yaml | 13 +++++++++-- 2 files changed, 22 insertions(+), 13 deletions(-) diff --git a/src/SOL003/VNFIndicator/VNFIndicator.yaml b/src/SOL003/VNFIndicator/VNFIndicator.yaml index 4c4ba478..eeb906a6 100644 --- a/src/SOL003/VNFIndicator/VNFIndicator.yaml +++ b/src/SOL003/VNFIndicator/VNFIndicator.yaml @@ -490,17 +490,17 @@ paths: items: $ref: "../../definitions/SOL002SOL003VNFIndicator_def.yaml#/definitions/VnfIndicatorSubscription" 303: - description: > - 303 SEE OTHER - - Shall be returned when a subscription with the - same callbackURI and the same filter already - exists and the policy of the VNFM is to not create - redundant subscriptions. - The HTTP response shall include a "Location" - HTTP header that contains the resource URI of - the existing "Individual subscription" resource. - The response body shall be empty. +# description: > +# 303 SEE OTHER +# +# Shall be returned when a subscription with the +# same callbackURI and the same filter already +# exists and the policy of the VNFM is to not create +# redundant subscriptions. +# The HTTP response shall include a "Location" +# HTTP header that contains the resource URI of +# the existing "Individual subscription" resource. +# The response body shall be empty. $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/303" 400: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/400" diff --git a/src/SOL003/VNFLifecycleOperationGranting/definitions/VNFLifecycleOperationGranting_def.yaml b/src/SOL003/VNFLifecycleOperationGranting/definitions/VNFLifecycleOperationGranting_def.yaml index 29c51635..786eb8b5 100644 --- a/src/SOL003/VNFLifecycleOperationGranting/definitions/VNFLifecycleOperationGranting_def.yaml +++ b/src/SOL003/VNFLifecycleOperationGranting/definitions/VNFLifecycleOperationGranting_def.yaml @@ -329,6 +329,15 @@ definitions: VL instances that have been passed previously in the associated VNF lifecycle management request, if the lifecycle management request has originated from the NFVO itself. + If this attribute is present , it need not contain + those entries that are unchanged compared to the entries that were passed + in the LCM operation which is related to this granting exchange. + External and/or externally-managed internal VLs can be passed in + VNF lifecycle management operation requests such as InstantiateVnf + or ChangeVnfFlavour, and/or in the grant response. The NFVO may choose + to override in the grant response external and/or externally-managed VL + instances that have been passed previously in the associated VNF lifecycle + management request, if the lifecycle management request has originated from the NFVO itself. type: array items: $ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/ExtVirtualLinkData" @@ -563,8 +572,8 @@ definitions: that they are placed in the same Network Function Virtualisation Infrastructure Point of Presence (NFVI-PoP) but in different resource zones: - {type="affinity"; scope="NFVI_POP"; {resource1,resource2}} - {type="anti-affinity"; scope="ZONE"; {resource1,resource2}} + {type="AFFINITY"; scope="NFVI_POP"; {resource1,resource2}} + {type="ANTI_AFFINITY"; scope="ZONE"; {resource1,resource2}} type: object required: - affinityOrAntiAffinity -- GitLab From 527601780049b3e68720e26a13b5785142751f4b Mon Sep 17 00:00:00 2001 From: Francesca Moscatelli Date: Thu, 6 Feb 2020 18:37:00 +0100 Subject: [PATCH 045/260] SOL003_141: Added endpoints for getting VNF pkg manifest --- .../VNFLifecycleOperationGranting.yaml | 16 +- .../VNFPackageManagement.yaml | 303 ++++++++++++++++-- 2 files changed, 282 insertions(+), 37 deletions(-) diff --git a/src/SOL003/VNFLifecycleOperationGranting/VNFLifecycleOperationGranting.yaml b/src/SOL003/VNFLifecycleOperationGranting/VNFLifecycleOperationGranting.yaml index e3022347..9196c04e 100644 --- a/src/SOL003/VNFLifecycleOperationGranting/VNFLifecycleOperationGranting.yaml +++ b/src/SOL003/VNFLifecycleOperationGranting/VNFLifecycleOperationGranting.yaml @@ -156,10 +156,10 @@ paths: 401: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/401" 403: - description: > - 403 FORBIDDEN - - Shall be returned upon the following error: The grant has been rejected. +# description: > +# 403 FORBIDDEN +# +# Shall be returned upon the following error: The grant has been rejected. $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/403" 404: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/404" @@ -274,10 +274,10 @@ paths: 401: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/401" 403: - description: > - 403 FORBIDDEN - - Shall be returned upon the following error: The grant has been rejected. +# description: > +# 403 FORBIDDEN +# +# Shall be returned upon the following error: The grant has been rejected. $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/403" 404: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/404" diff --git a/src/SOL003/VNFPackageManagement/VNFPackageManagement.yaml b/src/SOL003/VNFPackageManagement/VNFPackageManagement.yaml index 2f9817f4..69d83473 100644 --- a/src/SOL003/VNFPackageManagement/VNFPackageManagement.yaml +++ b/src/SOL003/VNFPackageManagement/VNFPackageManagement.yaml @@ -25,7 +25,7 @@ info: url: https://forge.etsi.org/etsi-forge-copyright-notice.txt externalDocs: - description: ETSI GS NFV-SOL 003 V2.6.1 + description: ETSI GS NFV-SOL 003 V2.7.1 url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.06.01_60/gs_NFV-SOL003v020601p.pdf basePath: "/vnfpkgm/v1" @@ -100,6 +100,14 @@ paths: description: > Complex attributes to be excluded from the response. See clause 5.3 of ETSI GS NFV SOL 013 for details. The VNFM should support this parameter. + The following attributes shall be excluded from the VnfPkgInfo structure in the response + body if this parameter is provided, or none of the parameters "all_fields," "fields", "exclude_fields", + "exclude_default" are provided: + - softwareImages + - additionalArtifacts + - userDefinedData. + - checksum + - onboardingFailureDetails in: query required: false type: string @@ -239,6 +247,15 @@ paths: in: header required: true type: string + - name: include_signature + description: > + If this parameter is provided, the NFVO shall include in the ZIP + archive the security information as specified above. + This URI query parameter is a flag, i.e. it shall have no value. + The NFVO shall support this parameter. + in: query + required: false + type: string responses: 200: description: > @@ -278,8 +295,6 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/404" 405: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - 406: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" 416: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" 500: @@ -378,6 +393,236 @@ paths: 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" + ############################################################################### + # Manifest in an individual VNF package # + ############################################################################### + '/vnf_packages/{vnfPkgId}/manifest': + parameters: + - name: vnfPkgId + description: > + Identifier of the on-boarded VNF package. The identifier is + allocated by the NFVO. + This identifier can be retrieved from the "vnfPkgId" + attribute in the VnfPackageOnboardingNotification or + VnfPackageChangeNotification. + in: path + type: string + required: true + get: + description: > + Query VNF Package Manifest + + The GET method reads the content of the manifest within a VNF package. + This method shall follow the provisions specified in the tables 10.4.4a.3.2-1 + and 10.4.4a.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. + Permitted values: "text/plain" and/or "application/zip" + Reference: IETF RFC 7231 + in: header + required: true + type: string + enum: + - text/plain + - application/zip + - text/plain+application/zip + - 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 + - name: include_signature + description: > + If this parameter is provided, the NFVO shall return the manifest and related security + information (such as certificate) in a ZIP archive. + If this parameter is not given, the NFVO shall provide only a copy of the manifest file. + This URI query parameter is a flag, i.e. it shall have no value. + The NFVO shall support this parameter. + in: query + required: false + type: string + responses: + 200: + description: > + 200 OK + + Shall be returned when the content of the VNFD has been read successfully. + The payload body shall contain a copy of the file representing the VNFD or + a ZIP file that contains the file or multiple files representing the VNFD, + as specified 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: + Content-Type: + description: The MIME type of the body of the response. + type: string + enum: + - text/plain + - application/zip + maximum: 1 + minimum: 1 + 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 + Version: + description: > + Version of the API used in the response. + type: string + maximum: 1 + minimum: 1 + 400: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/400" + 401: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/401" + 403: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/403" + 404: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/404" + 405: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + 406: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" + 409: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" + 416: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" + 500: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500" + 503: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" + 504: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" + + '/vnf_packages/{vnfId}/manifest': + parameters: + - name: vnfId + description: > + Identifier of the VNFD and the VNF package. + The identifier is allocated by the VNF provider. + This identifier can be retrieved from the "vnfdId" attribute + in the VnfPackageOnboardingNotification or VnfPackageChangeNotification. + in: path + type: string + required: true + get: + description: > + Query VNF Package Manifest + + The GET method reads the content of the manifest within a VNF package. + This method shall follow the provisions specified in the tables 10.4.4a.3.2-1 + and 10.4.4a.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. + Permitted values: "text/plain" and/or "application/zip" + Reference: IETF RFC 7231 + in: header + required: true + type: string + enum: + - text/plain + - application/zip + - text/plain+application/zip + - 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 + - name: include_signature + description: > + If this parameter is provided, the NFVO shall return the manifest and related security + information (such as certificate) in a ZIP archive. + If this parameter is not given, the NFVO shall provide only a copy of the manifest file. + This URI query parameter is a flag, i.e. it shall have no value. + The NFVO shall support this parameter. + in: query + required: false + type: string + responses: + 200: + description: > + 200 OK + + Shall be returned when the content of the VNFD has been read successfully. + The payload body shall contain a copy of the file representing the VNFD or + a ZIP file that contains the file or multiple files representing the VNFD, + as specified 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: + Content-Type: + description: The MIME type of the body of the response. + type: string + enum: + - text/plain + - application/zip + maximum: 1 + minimum: 1 + 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 + Version: + description: > + Version of the API used in the response. + type: string + maximum: 1 + minimum: 1 + 400: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/400" + 401: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/401" + 403: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/403" + 404: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/404" + 405: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + 406: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" + 409: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" + 416: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" + 500: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500" + 503: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" + 504: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" + ############################################################################### # VNFD in an individual VNF package # ############################################################################### @@ -493,21 +738,21 @@ paths: 405: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" 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 VNFD, the NFVO shall respond with this response code. +# 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 VNFD, the NFVO shall respond with this response code. $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" 409: - description: > - 409 CONFLICT - - Shall be returned upon the following error: The operation cannot - be executed currently, due to a conflict with the state of the resource. - Typically, this is due to the fact that "onboardingState" of the - VNF package has a value different from "ONBOARDED". +# description: > +# 409 CONFLICT +# +# Shall be returned upon the following error: The operation cannot +# be executed currently, due to a conflict with the state of the resource. +# Typically, this is due to the fact that "onboardingState" of the +# VNF package has a value different from "ONBOARDED". $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" 416: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" @@ -629,21 +874,21 @@ paths: 405: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" 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 VNFD, the NFVO shall respond with this response code. +# 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 VNFD, the NFVO shall respond with this response code. $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" 409: - description: > - 409 CONFLICT - - Shall be returned upon the following error: The operation cannot - be executed currently, due to a conflict with the state of the resource. - Typically, this is due to the fact that "onboardingState" of the - VNF package has a value different from "ONBOARDED". +# description: > +# 409 CONFLICT +# +# Shall be returned upon the following error: The operation cannot +# be executed currently, due to a conflict with the state of the resource. +# Typically, this is due to the fact that "onboardingState" of the +# VNF package has a value different from "ONBOARDED". $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" 416: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" -- GitLab From e67aab7d1181567f2721c0b7ee4b30f4d32333d4 Mon Sep 17 00:00:00 2001 From: Francesca Moscatelli Date: Thu, 6 Feb 2020 18:46:07 +0100 Subject: [PATCH 046/260] SOL003_141: fix in endpoints for getting VNF pkg manifest --- src/SOL003/VNFPackageManagement/VNFPackageManagement.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/SOL003/VNFPackageManagement/VNFPackageManagement.yaml b/src/SOL003/VNFPackageManagement/VNFPackageManagement.yaml index 69d83473..f4e9037c 100644 --- a/src/SOL003/VNFPackageManagement/VNFPackageManagement.yaml +++ b/src/SOL003/VNFPackageManagement/VNFPackageManagement.yaml @@ -510,7 +510,7 @@ paths: 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" - '/vnf_packages/{vnfId}/manifest': + '/onboarded_vnf_packages/{vnfId}/manifest': parameters: - name: vnfId description: > -- GitLab From 3e331383d7e80eb0b64b581e3fd27ddeb26f28b3 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Fri, 7 Feb 2020 12:16:02 +0100 Subject: [PATCH 047/260] SOL002_5 filter description in table 5.4.2.3.2-1 updated (URI query parameter "nextpage_opaque _marker" added) --- .../VNFLifecycleManagement/VNFLifecycleManagement.yaml | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 3463d2d4..86e663d9 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -225,6 +225,15 @@ paths: in: query required: false type: string + - name: nextpage_opaque_marker + description: > + Marker to obtain the next page of a paged response. + Shall be supported by the VNFM if the VNFM supports + alternative 2 (paging) according to clause 5.4.2.1 + of ETSI GS NFV-SOL 013 for this resource. + in: query + required: false + type: string responses: 200: description: > -- GitLab From 1e584d24a85b942e6c6fd03b93a27f12d0b998d3 Mon Sep 17 00:00:00 2001 From: Giacomo Bernini Date: Fri, 7 Feb 2020 13:03:31 +0100 Subject: [PATCH 048/260] solved bugs #245 #185 --- .../definitions/SOL002VNFConfiguration_def.yaml | 12 ++++++++---- src/definitions/SOL002SOL003_def.yaml | 1 - 2 files changed, 8 insertions(+), 5 deletions(-) diff --git a/src/SOL002/VNFConfiguration/definitions/SOL002VNFConfiguration_def.yaml b/src/SOL002/VNFConfiguration/definitions/SOL002VNFConfiguration_def.yaml index 36c24796..0a2e6bb8 100644 --- a/src/SOL002/VNFConfiguration/definitions/SOL002VNFConfiguration_def.yaml +++ b/src/SOL002/VNFConfiguration/definitions/SOL002VNFConfiguration_def.yaml @@ -76,7 +76,9 @@ definitions: extCpConfig: description: > Configuration parameters for the external CPs of the VNF instance. - $ref: '#/definitions/CpConfiguration' + type: array + items: + $ref: $ref: '#/definitions/CpConfiguration' dhcpServer: description: > IP address of the DHCP server that the VNF instance can use to obtain @@ -99,10 +101,12 @@ definitions: description: > Identifier of a VNFC instance to which this set of configuration data applies. $ref: '../../../definitions/SOL002SOL003_def.yaml#/definitions/IdentifierInVnf' - extCpConfig: + intCpConfig: description: > - Configuration parameters for the external CPs of the VNFC instance. - $ref: '#/definitions/CpConfiguration' + Configuration parameters for the internal CPs of the VNFC instance. + type: array + items: + $ref: $ref: '#/definitions/CpConfiguration' dhcpServer: description: > IP address of the DHCP server that the VNF instance can use to obtain diff --git a/src/definitions/SOL002SOL003_def.yaml b/src/definitions/SOL002SOL003_def.yaml index c1827f37..b8db90f0 100644 --- a/src/definitions/SOL002SOL003_def.yaml +++ b/src/definitions/SOL002SOL003_def.yaml @@ -253,7 +253,6 @@ definitions: ResourceHandle: required: - - vimConnectionId - resourceId type: object description: > -- GitLab From e51c2409180ec4edaf6eb6afd81d4bbeaac829aa Mon Sep 17 00:00:00 2001 From: Francesca Moscatelli Date: Mon, 10 Feb 2020 11:31:06 +0100 Subject: [PATCH 049/260] SOL003_140->145: VNF Packages APIs updated --- .../VNFPackageManagement.yaml | 813 ++++++++++++++---- 1 file changed, 653 insertions(+), 160 deletions(-) diff --git a/src/SOL003/VNFPackageManagement/VNFPackageManagement.yaml b/src/SOL003/VNFPackageManagement/VNFPackageManagement.yaml index f4e9037c..741c21ef 100644 --- a/src/SOL003/VNFPackageManagement/VNFPackageManagement.yaml +++ b/src/SOL003/VNFPackageManagement/VNFPackageManagement.yaml @@ -394,9 +394,9 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" ############################################################################### - # Manifest in an individual VNF package # + # VNFD in an individual VNF package # ############################################################################### - '/vnf_packages/{vnfPkgId}/manifest': + '/vnf_packages/{vnfPkgId}/vnfd': parameters: - name: vnfPkgId description: > @@ -410,12 +410,94 @@ paths: required: true get: description: > - Query VNF Package Manifest + Query VNF Package Info - The GET method reads the content of the manifest within a VNF package. - This method shall follow the provisions specified in the tables 10.4.4a.3.2-1 - and 10.4.4a.3.2-2 for URI query parameters, request and response data structures, - and response codes. + The GET method reads the content of the VNFD within a VNF package. + The VNFD is implemented as a collection of one or more files. + A ZIP archive embedding these files shall be returned when reading this resource. + The default format of the ZIP archive shall be the one specified in ETSI GS NFV-SOL 004 + where only the files representing the VNFD and information needed to navigate the ZIP + archive and to identify the file that is the entry point for parsing the VNFD, and, + if requested, further security information are included. This means that the structure + of the ZIP archive shall correspond to the directory structure used in the VNF package + and that the archive shall contain the following files from the package: + • TOSCA.meta (if available in the package) + • The main TOSCA definitions YAML file (either as referenced from TOSCA.meta + or available as a file with the extension ".yml" or ".yaml" from the root of the archive) + • Every component of the VNFD referenced (recursively) from the main TOSCA definitions YAML file + • The related security information, if the "include_signatures" URI parameter is provided, as follows: + - the manifest file + - the singleton certificate file in the root of the VNF package (if available in the package) + - the signing certificates of the individual files included in the ZIP archive (if available in the package) + - the signatures of the individual files (if available in the package) + Three examples are provided below. + + NOTE: These examples do not show the security related files. + + EXAMPLE 1: Assuming a request is sent for the following VNF package + (as described in clause A.1 in ETSI GS NFV-SOL 004): + !------TOSCA-Metadata + !----- TOSCA.meta (metadata for navigating the ZIP file) + !------Definitions + !----- MRF.yaml (main VNFD file) + !----- OtherTemplates (e.g. type definitions, referenced by the main VNFD file) + !------Files + !----- ChangeLog.txt + !----- image(s) + !----- other artifacts + !------Tests + !----- file(s) + !------Licenses + !----- file(s) + !------Scripts + !----- install.sh + !----- MRF.mf + + The NFVO will return a ZIP file of the following format: + !------TOSCA-Metadata + !----- TOSCA.meta + !------Definitions + !----- MRF.yaml + !----- OtherTemplates + + EXAMPLE 2: Assuming a request is sent for the following VNF package + (a VNF package without a TOSCA-Metadata directory, as + described in clause A.2 in ETSI GS NFV-SOL 004): + !------MRF.yaml (main VNFD file) + !------MRF.mf + !------ChangeLog.txt + !------Tests + !----- file(s) + !------Licenses + !----- file(s) + !------Artifacts + !----- install.sh + !----- start.yang + + The NFVO will return a ZIP file of the following format: + !------MRF.yaml + + EXAMPLE 3: Assuming a request is sent for the following VNF package + (a VNF package with the YANG VNFD without a TOSCA-Metadata directory, + as described in clause A.3 in ETSI GS NFV SOL 004): + !----CompanyVNFD.yaml + !----CompanyVNFD.xml + !----CompanyVNFD.mf + !----ChangeLog.txt + !-----Files + !-----Instance Data Files + !---- start.xml + !-----Licenses + !-----Scripts + !----- install.sh + + The NFVO will return a ZIP file of the following format: + !----CompanyVNFD.yaml + !----CompanyVNFD.xml (indicated in the yang_definitions metadata in CompanyVNFD.yaml) + + This method shall follow the provisions specified in the tables 10.4.4.3.2-1 + and 10.4.4.3.2-2 for URI query parameters, request and response data structures, + nd response codes. parameters: - name: Accept description: > @@ -442,11 +524,10 @@ paths: in: header required: true type: string - - name: include_signature + - name: include_signatures description: > - If this parameter is provided, the NFVO shall return the manifest and related security - information (such as certificate) in a ZIP archive. - If this parameter is not given, the NFVO shall provide only a copy of the manifest file. + If this parameter is provided, the NFVO shall include in the ZIP + archive the security information as specified above. This URI query parameter is a flag, i.e. it shall have no value. The NFVO shall support this parameter. in: query @@ -497,9 +578,14 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/404" 405: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - 406: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" 409: + # description: > + # 409 CONFLICT + # + # Shall be returned upon the following error: The operation cannot + # be executed currently, due to a conflict with the state of the resource. + # Typically, this is due to the fact that "onboardingState" of the + # VNF package has a value different from "ONBOARDED". $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" 416: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" @@ -510,9 +596,9 @@ paths: 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" - '/onboarded_vnf_packages/{vnfId}/manifest': + '/onboarded_vnf_packages/{vnfdId}/vnfd': parameters: - - name: vnfId + - name: vnfdId description: > Identifier of the VNFD and the VNF package. The identifier is allocated by the VNF provider. @@ -523,12 +609,94 @@ paths: required: true get: description: > - Query VNF Package Manifest + Query VNF Package Info - The GET method reads the content of the manifest within a VNF package. - This method shall follow the provisions specified in the tables 10.4.4a.3.2-1 - and 10.4.4a.3.2-2 for URI query parameters, request and response data structures, - and response codes. + The GET method reads the content of the VNFD within a VNF package. + The VNFD is implemented as a collection of one or more files. + A ZIP archive embedding these files shall be returned when reading this resource. + The default format of the ZIP archive shall be the one specified in ETSI GS NFV-SOL 004 + where only the files representing the VNFD and information needed to navigate the ZIP + archive and to identify the file that is the entry point for parsing the VNFD, and, + if requested, further security information are included. This means that the structure + of the ZIP archive shall correspond to the directory structure used in the VNF package + and that the archive shall contain the following files from the package: + • TOSCA.meta (if available in the package) + • The main TOSCA definitions YAML file (either as referenced from TOSCA.meta + or available as a file with the extension ".yml" or ".yaml" from the root of the archive) + • Every component of the VNFD referenced (recursively) from the main TOSCA definitions YAML file + • The related security information, if the "include_signatures" URI parameter is provided, as follows: + - the manifest file + - the singleton certificate file in the root of the VNF package (if available in the package) + - the signing certificates of the individual files included in the ZIP archive (if available in the package) + - the signatures of the individual files (if available in the package) + Three examples are provided below. + + NOTE: These examples do not show the security related files. + + EXAMPLE 1: Assuming a request is sent for the following VNF package + (as described in clause A.1 in ETSI GS NFV-SOL 004): + !------TOSCA-Metadata + !----- TOSCA.meta (metadata for navigating the ZIP file) + !------Definitions + !----- MRF.yaml (main VNFD file) + !----- OtherTemplates (e.g. type definitions, referenced by the main VNFD file) + !------Files + !----- ChangeLog.txt + !----- image(s) + !----- other artifacts + !------Tests + !----- file(s) + !------Licenses + !----- file(s) + !------Scripts + !----- install.sh + !----- MRF.mf + + The NFVO will return a ZIP file of the following format: + !------TOSCA-Metadata + !----- TOSCA.meta + !------Definitions + !----- MRF.yaml + !----- OtherTemplates + + EXAMPLE 2: Assuming a request is sent for the following VNF package + (a VNF package without a TOSCA-Metadata directory, as + described in clause A.2 in ETSI GS NFV-SOL 004): + !------MRF.yaml (main VNFD file) + !------MRF.mf + !------ChangeLog.txt + !------Tests + !----- file(s) + !------Licenses + !----- file(s) + !------Artifacts + !----- install.sh + !----- start.yang + + The NFVO will return a ZIP file of the following format: + !------MRF.yaml + + EXAMPLE 3: Assuming a request is sent for the following VNF package + (a VNF package with the YANG VNFD without a TOSCA-Metadata directory, + as described in clause A.3 in ETSI GS NFV SOL 004): + !----CompanyVNFD.yaml + !----CompanyVNFD.xml + !----CompanyVNFD.mf + !----ChangeLog.txt + !-----Files + !-----Instance Data Files + !---- start.xml + !-----Licenses + !-----Scripts + !----- install.sh + + The NFVO will return a ZIP file of the following format: + !----CompanyVNFD.yaml + !----CompanyVNFD.xml (indicated in the yang_definitions metadata in CompanyVNFD.yaml) + + This method shall follow the provisions specified in the tables 10.4.4.3.2-1 + and 10.4.4.3.2-2 for URI query parameters, request and response data structures, + nd response codes. parameters: - name: Accept description: > @@ -555,11 +723,10 @@ paths: in: header required: true type: string - - name: include_signature + - name: include_signatures description: > - If this parameter is provided, the NFVO shall return the manifest and related security - information (such as certificate) in a ZIP archive. - If this parameter is not given, the NFVO shall provide only a copy of the manifest file. + If this parameter is provided, the NFVO shall include in the ZIP + archive the security information as specified above. This URI query parameter is a flag, i.e. it shall have no value. The NFVO shall support this parameter. in: query @@ -610,9 +777,14 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/404" 405: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - 406: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" 409: + # description: > + # 409 CONFLICT + # + # Shall be returned upon the following error: The operation cannot + # be executed currently, due to a conflict with the state of the resource. + # Typically, this is due to the fact that "onboardingState" of the + # VNF package has a value different from "ONBOARDED". $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" 416: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" @@ -624,9 +796,9 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" ############################################################################### - # VNFD in an individual VNF package # + # Manifest in an individual VNF package # ############################################################################### - '/vnf_packages/{vnfPkgId}/vnfd': + '/vnf_packages/{vnfPkgId}/manifest': parameters: - name: vnfPkgId description: > @@ -640,32 +812,12 @@ paths: required: true get: description: > - Query VNF Package Info - + Query VNF Package Manifest - The GET method reads the content of the VNFD within a VNF package. - The VNFD can be implemented as a single file or as a collection of - multiple files. If the VNFD is implemented in the form of multiple - files, a ZIP file embedding these files shall be returned. If the VNFD - is implemented as a single file, 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. - * If the "Accept" header contains only "text/plain" and the VNFD is - implemented as a single file, the file shall be returned; - otherwise, an error message shall be returned. - * If the "Accept" header contains only "application/zip", the single - file or the multiple files that make up the VNFD shall be returned - embedded in a ZIP file. - * If the "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 VNFD; for a multi-file VNFD, a ZIP file - shall be returned. - The default format of the ZIP file shall be the one specified in - ETSI GS NFV-SOL 004 where only the YAML files representing the VNFD, - and information needed to navigate the ZIP file and to identify the - file that is the entry point for parsing the VNFD (such as TOSCA-meta - or manifest files or naming conventions) are included. + The GET method reads the content of the manifest within a VNF package. + This method shall follow the provisions specified in the tables 10.4.4a.3.2-1 + and 10.4.4a.3.2-2 for URI query parameters, request and response data structures, + and response codes. parameters: - name: Accept description: > @@ -692,18 +844,35 @@ paths: in: header required: true type: string + - name: include_signatures + description: > + If this parameter is provided, the NFVO shall return the manifest and related security + information (such as certificate) in a ZIP archive. + If this parameter is not given, the NFVO shall provide only a copy of the manifest file. + This URI query parameter is a flag, i.e. it shall have no value. + The NFVO shall support this parameter. + in: query + required: false + type: string responses: 200: description: > 200 OK - Shall be returned when the content of the VNFD has been read successfully. - The payload body shall contain a copy of the file representing the VNFD or - a ZIP file that contains the file or multiple files representing the VNFD, - as specified 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. + Shall be returned when the content of the manifest has been read successfully. + If the "include_signatures" URI query parameter was absent in the request, + or if the manifest file has all security-related information embedded + (i.e. there is no separate certificate file), the payload body shall contain + a copy of the manifest file of the VNF package and the "Content-Type" HTTP + header shall be set to "text/plain". + + If the "include_signatures" URI query parameter was present in the related + request and the manifest file does not have all the security-related + information embedded (i.e. there is a separate certificate file), + the "Content-Type" HTTP header shall be set to "application/zip and the + payload body shall contain a ZIP archive which includes: + • a copy of the manifest file of the VNF package; + • a copy of the related individual certificate file. headers: Content-Type: description: The MIME type of the body of the response. @@ -738,21 +907,8 @@ paths: 405: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" 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 VNFD, the NFVO shall respond with this response code. $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" 409: -# description: > -# 409 CONFLICT -# -# Shall be returned upon the following error: The operation cannot -# be executed currently, due to a conflict with the state of the resource. -# Typically, this is due to the fact that "onboardingState" of the -# VNF package has a value different from "ONBOARDED". $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" 416: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" @@ -763,7 +919,7 @@ paths: 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" - '/onboarded_vnf_packages/{vnfdId}/vnfd': + '/onboarded_vnf_packages/{vnfdId}/manifest': parameters: - name: vnfdId description: > @@ -776,32 +932,12 @@ paths: required: true get: description: > - Query VNF Package Info - + Query VNF Package Manifest - The GET method reads the content of the VNFD within a VNF package. - The VNFD can be implemented as a single file or as a collection of - multiple files. If the VNFD is implemented in the form of multiple - files, a ZIP file embedding these files shall be returned. If the VNFD - is implemented as a single file, 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. - * If the "Accept" header contains only "text/plain" and the VNFD is - implemented as a single file, the file shall be returned; - otherwise, an error message shall be returned. - * If the "Accept" header contains only "application/zip", the single - file or the multiple files that make up the VNFD shall be returned - embedded in a ZIP file. - * If the "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 VNFD; for a multi-file VNFD, a ZIP file - shall be returned. - The default format of the ZIP file shall be the one specified in - ETSI GS NFV-SOL 004 where only the YAML files representing the VNFD, - and information needed to navigate the ZIP file and to identify the - file that is the entry point for parsing the VNFD (such as TOSCA-meta - or manifest files or naming conventions) are included. + The GET method reads the content of the manifest within a VNF package. + This method shall follow the provisions specified in the tables 10.4.4a.3.2-1 + and 10.4.4a.3.2-2 for URI query parameters, request and response data structures, + and response codes. parameters: - name: Accept description: > @@ -828,18 +964,35 @@ paths: in: header required: true type: string + - name: include_signatures + description: > + If this parameter is provided, the NFVO shall return the manifest and related security + information (such as certificate) in a ZIP archive. + If this parameter is not given, the NFVO shall provide only a copy of the manifest file. + This URI query parameter is a flag, i.e. it shall have no value. + The NFVO shall support this parameter. + in: query + required: false + type: string responses: 200: description: > 200 OK - Shall be returned when the content of the VNFD has been read successfully. - The payload body shall contain a copy of the file representing the VNFD or - a ZIP file that contains the file or multiple files representing the VNFD, - as specified 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. + Shall be returned when the content of the manifest has been read successfully. + If the "include_signatures" URI query parameter was absent in the request, + or if the manifest file has all security-related information embedded + (i.e. there is no separate certificate file), the payload body shall contain + a copy of the manifest file of the VNF package and the "Content-Type" HTTP + header shall be set to "text/plain". + + If the "include_signatures" URI query parameter was present in the related + request and the manifest file does not have all the security-related + information embedded (i.e. there is a separate certificate file), + the "Content-Type" HTTP header shall be set to "application/zip and the + payload body shall contain a ZIP archive which includes: + • a copy of the manifest file of the VNF package; + • a copy of the related individual certificate file. headers: Content-Type: description: The MIME type of the body of the response. @@ -874,21 +1027,8 @@ paths: 405: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" 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 VNFD, the NFVO shall respond with this response code. $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" 409: -# description: > -# 409 CONFLICT -# -# Shall be returned upon the following error: The operation cannot -# be executed currently, due to a conflict with the state of the resource. -# Typically, this is due to the fact that "onboardingState" of the -# VNF package has a value different from "ONBOARDED". $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" 416: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" @@ -919,6 +1059,15 @@ paths: Fetch VNF Package. The GET method fetches the content of a VNF package identified by the VNF package identifier allocated by the NFVO. + The content of the package is provided as onboarded, i.e. depending on + the security option used, the CSAR or the CSAR wrapped in a ZIP archive + together with an external signature is returned, as defined in clause + 5.1 of ETSI GS NFV-SOL 004. + + NOTE: Information about the applicable security option can be obtained + by evaluating the "packageSecurityOption" attribute in the "VnfPkgInfo" + structure. + This method shall follow the provisions specified in the tables 10.4.5.3.2-1 and 10.4.5.3.2-2 for URI query parameters, request and response data structures, and response codes. @@ -944,8 +1093,10 @@ paths: The request may contain a "Range" HTTP header to obtain single range of bytes from the VNF package file. This can be used to continue an aborted transmission. - If the NFVO does not support range requests, it should return the - whole file with a 200 OK response instead. + + If the "Range" header is present in the request and the NFVO + does not support responding to range requests with a 206 response, + it shall return a 200 OK response instead as defined below. in: header type: string - name: Version @@ -1030,20 +1181,20 @@ paths: 406: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" 409: - description: > - 409 CONFLICT - - Shall be returned upon the following error: The operation cannot be executed currently, - due to a conflict with the state of the resource. - Typically, this is due to the fact that "onboardingState" of the VNF package has - a value different from "ONBOARDED". +# description: > +# 409 CONFLICT +# +# Shall be returned upon the following error: The operation cannot be executed currently, +# due to a conflict with the state of the resource. +# Typically, this is due to the fact that "onboardingState" of the VNF package has +# a value different from "ONBOARDED". $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" 416: - description: > - 416 RANGE NOT SATISFIABLE - - Shall be returned upon the following error: The byte range passed in the "Range" header - did not match any available byte range in the VNF package file (e.g. "access after end of file"). +# description: > +# 416 RANGE NOT SATISFIABLE +# +# Shall be returned upon the following error: The byte range passed in the "Range" header +# did not match any available byte range in the VNF package file (e.g. "access after end of file"). $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" 500: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500" @@ -1068,6 +1219,15 @@ paths: Fetch VNF Package. The GET method fetches the content of a VNF package identified by the VNF package identifier allocated by the NFVO. + The content of the package is provided as onboarded, i.e. depending on + the security option used, the CSAR or the CSAR wrapped in a ZIP archive + together with an external signature is returned, as defined in clause + 5.1 of ETSI GS NFV-SOL 004. + + NOTE: Information about the applicable security option can be obtained + by evaluating the "packageSecurityOption" attribute in the "VnfPkgInfo" + structure. + This method shall follow the provisions specified in the tables 10.4.5.3.2-1 and 10.4.5.3.2-2 for URI query parameters, request and response data structures, and response codes. @@ -1093,8 +1253,10 @@ paths: The request may contain a "Range" HTTP header to obtain single range of bytes from the VNF package file. This can be used to continue an aborted transmission. - If the NFVO does not support range requests, it should return the - whole file with a 200 OK response instead. + + If the "Range" header is present in the request and the NFVO + does not support responding to range requests with a 206 response, + it shall return a 200 OK response instead as defined below. in: header type: string - name: Version @@ -1179,20 +1341,351 @@ paths: 406: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" 409: +# description: > +# 409 CONFLICT +# +# Shall be returned upon the following error: The operation cannot be executed currently, +# due to a conflict with the state of the resource. +# Typically, this is due to the fact that "onboardingState" of the VNF package has +# a value different from "ONBOARDED". + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" + 416: +# description: > +# 416 RANGE NOT SATISFIABLE +# +# Shall be returned upon the following error: The byte range passed in the "Range" header +# did not match any available byte range in the VNF package file (e.g. "access after end of file"). + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" + 500: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500" + 503: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" + 504: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" + + ############################################################################### + # VNF package artifacts # + ############################################################################### + '/vnf_packages/{vnfPkgId}/artifacts': + parameters: + - name: vnfPkgId + description: > + Identifier of the VNF package. The identifier is allocated by the NFVO. + This identifier can be retrieved from the "vnfPkgId" attribute in the + VnfPackageOnboardingNotification or VnfPackageChangeNotification + in: path + required: true + type: string + get: + description: > + Fetch VNF Package Artifacts. + + The GET method shall return an archive that contains a set of artifacts + according to the provisions for inclusion/exclusion defined below, + embedded in a directory structure being the same as in the VNF package. + The criteria for exclusion/inclusion of an artifact in the archive are defined as follows: + - Artifacts that are software images shall be excluded from the archive. + - Artifacts that are external to the VNF package shall be excluded from the archive. + - All additional artifacts included in the VNF package that are MANO artifacts shall + be included in the archive, unless the URI query parameter "exclude_all_mano_artifacts" + has been provided, in which case such artifacts shall be excluded. + - All additional artifacts included in the VNF package that are non-MANO artifacts + shall be included in the archive, unless: +  the URI query parameter "exclude_all_non_mano_artifacts" has been provided, + in which case such artifacts shall be excluded; +  the URI query parameter "select_non_mano_artifact_sets" has been provided and + is supported by the NFVO, in which case only those non-MANO artifacts shall be + included whose non-MANO artifact set identifier matches one of the values of the query parameter. + Package metadata such as manifest file or VNFD shall not be included in the archive. + This method shall follow the provisions specified in the tables 10.4.5a.3.2-1 and + 10.4.5a.3.2-2 for URI query parameters, request and response data structures, and response codes. + parameters: + - name: Accept description: > - 409 CONFLICT + Content-Types that are acceptable for the response. + The "Accept" HTTP header shall be set to "application/zip". + 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: Range + description: > + The request may contain a "Range" HTTP header to obtain single + range of bytes from the VNF package file. This can be used to + continue an aborted transmission. + If the NFVO does not support range requests, it should return the + whole file with a 200 OK response instead. + in: header + type: string + - name: Version + description: > + Version of the API requested to use when responding to this request. + in: header + required: true + type: string + responses: + 200: + description: > + 200 OK - Shall be returned upon the following error: The operation cannot be executed currently, - due to a conflict with the state of the resource. - Typically, this is due to the fact that "onboardingState" of the VNF package has - a value different from "ONBOARDED". + Shall be returned when the whole content of the archive containing + the artifact files has been read successfully. + The payload body shall be a ZIP archive containing the requested + set of artifacts selected according to the provisions specified above + in this clause, and, if the flag "include_signatures" was provided in + the related request, the applicable signature files and, if available, + the separate certificate files from the VNF package. + The "Content-Type" HTTP header shall be set to "application/zip". + headers: + Content-Type: + description: > + The MIME type of the body of the response. + The "Content-Type" HTTP header shall be set according to the + content type of the artifact file. If the content type cannot + be determined, the header shall be set to the value + "application/octet-stream". + type: string + maximum: 1 + minimum: 1 + 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 + Version: + description: > + Version of the API used in the response. + type: string + maximum: 1 + minimum: 1 + 206: + description: > + 206 PARTIAL CONTENT + + If the NFVO supports range requests, this response shall be returned + when a single consecutive byte range from the content of the archive + that would have been returned in a "200 OK" response has been read + successfully according to the request. + The response body shall contain the requested part of the archive. + The "Content-Type" HTTP header shall be set to "application/zip". + The "Content-Range" HTTP header shall be provided according to IETF RFC 7233. + headers: + Content-Range: + type: string + maximum: 1 + minimum: 1 + Content-Type: + description: > + The MIME type of the body of the response. + The "Content-Type" HTTP header shall be set according to the + content type of the artifact file. If the content type cannot + be determined, the header shall be set to the value + "application/octet-stream". + type: string + maximum: 1 + minimum: 1 + 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 + Version: + description: > + Version of the API used in the response. + type: string + maximum: 1 + minimum: 1 + 400: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/400" + 401: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/401" + 403: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/403" + 404: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/404" + 405: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + 406: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" + 409: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" 416: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" + 500: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500" + 503: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" + 504: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" + + '/onboarded_vnf_packages/{vnfPkgId}/artifacts': + parameters: + - name: vnfPkgId + description: > + Identifier of the VNF package. The identifier is allocated by the NFVO. + This identifier can be retrieved from the "vnfPkgId" attribute in the + VnfPackageOnboardingNotification or VnfPackageChangeNotification + in: path + required: true + type: string + get: + description: > + Fetch VNF Package Artifacts. + + The GET method shall return an archive that contains a set of artifacts + according to the provisions for inclusion/exclusion defined below, + embedded in a directory structure being the same as in the VNF package. + The criteria for exclusion/inclusion of an artifact in the archive are defined as follows: + - Artifacts that are software images shall be excluded from the archive. + - Artifacts that are external to the VNF package shall be excluded from the archive. + - All additional artifacts included in the VNF package that are MANO artifacts shall + be included in the archive, unless the URI query parameter "exclude_all_mano_artifacts" + has been provided, in which case such artifacts shall be excluded. + - All additional artifacts included in the VNF package that are non-MANO artifacts + shall be included in the archive, unless: +  the URI query parameter "exclude_all_non_mano_artifacts" has been provided, + in which case such artifacts shall be excluded; +  the URI query parameter "select_non_mano_artifact_sets" has been provided and + is supported by the NFVO, in which case only those non-MANO artifacts shall be + included whose non-MANO artifact set identifier matches one of the values of the query parameter. + Package metadata such as manifest file or VNFD shall not be included in the archive. + This method shall follow the provisions specified in the tables 10.4.5a.3.2-1 and + 10.4.5a.3.2-2 for URI query parameters, request and response data structures, and response codes. + parameters: + - name: Accept description: > - 416 RANGE NOT SATISFIABLE + Content-Types that are acceptable for the response. + The "Accept" HTTP header shall be set to "application/zip". + 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: Range + description: > + The request may contain a "Range" HTTP header to obtain single + range of bytes from the VNF package file. This can be used to + continue an aborted transmission. + If the NFVO does not support range requests, it should return the + whole file with a 200 OK response instead. + in: header + type: string + - name: Version + description: > + Version of the API requested to use when responding to this request. + in: header + required: true + type: string + responses: + 200: + description: > + 200 OK + + Shall be returned when the whole content of the archive containing + the artifact files has been read successfully. + The payload body shall be a ZIP archive containing the requested + set of artifacts selected according to the provisions specified above + in this clause, and, if the flag "include_signatures" was provided in + the related request, the applicable signature files and, if available, + the separate certificate files from the VNF package. + The "Content-Type" HTTP header shall be set to "application/zip". + headers: + Content-Type: + description: > + The MIME type of the body of the response. + The "Content-Type" HTTP header shall be set according to the + content type of the artifact file. If the content type cannot + be determined, the header shall be set to the value + "application/octet-stream". + type: string + maximum: 1 + minimum: 1 + 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 + Version: + description: > + Version of the API used in the response. + type: string + maximum: 1 + minimum: 1 + 206: + description: > + 206 PARTIAL CONTENT - Shall be returned upon the following error: The byte range passed in the "Range" header - did not match any available byte range in the VNF package file (e.g. "access after end of file"). + If the NFVO supports range requests, this response shall be returned + when a single consecutive byte range from the content of the archive + that would have been returned in a "200 OK" response has been read + successfully according to the request. + The response body shall contain the requested part of the archive. + The "Content-Type" HTTP header shall be set to "application/zip". + The "Content-Range" HTTP header shall be provided according to IETF RFC 7233. + headers: + Content-Range: + type: string + maximum: 1 + minimum: 1 + Content-Type: + description: > + The MIME type of the body of the response. + The "Content-Type" HTTP header shall be set according to the + content type of the artifact file. If the content type cannot + be determined, the header shall be set to the value + "application/octet-stream". + type: string + maximum: 1 + minimum: 1 + 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 + Version: + description: > + Version of the API used in the response. + type: string + maximum: 1 + minimum: 1 + 400: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/400" + 401: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/401" + 403: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/403" + 404: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/404" + 405: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + 406: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" + 409: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" + 416: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" 500: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500" @@ -1350,25 +1843,25 @@ paths: 406: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" 409: - description: > - 409 CONFLICT - - Shall be returned upon the following error: The operation cannot - be executed currently, due to a conflict with the state of the resource. - Typically, this is due to the fact that "onboardingState" of the - VNF package 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. +# description: > +# 409 CONFLICT +# +# Shall be returned upon the following error: The operation cannot +# be executed currently, due to a conflict with the state of the resource. +# Typically, this is due to the fact that "onboardingState" of the +# VNF package 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/SOL002SOL003_resp.yaml#/responses/409" 416: - description: > - 416 RANGE NOT SATISFIABLE - - Shall be returned upon the following error: The byte range passed in the - "Range" header did not match any available byte range in the artifact file - (e.g. "access after end of file"). - The response body may contain a ProblemDetails structure. +# description: > +# 416 RANGE NOT SATISFIABLE +# +# Shall be returned upon the following error: The byte range passed in the +# "Range" header did not match any available byte range in the artifact file +# (e.g. "access after end of file"). +# The response body may contain a ProblemDetails structure. $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" 500: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500" -- GitLab From 4399706ee0fd3b3016dee33b5935c1647974e46a Mon Sep 17 00:00:00 2001 From: Giacomo Bernini Date: Mon, 10 Feb 2020 12:06:17 +0100 Subject: [PATCH 050/260] fixed indentation --- .../definitions/SOL002VNFConfiguration_def.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/SOL002/VNFConfiguration/definitions/SOL002VNFConfiguration_def.yaml b/src/SOL002/VNFConfiguration/definitions/SOL002VNFConfiguration_def.yaml index 0a2e6bb8..62b8adff 100644 --- a/src/SOL002/VNFConfiguration/definitions/SOL002VNFConfiguration_def.yaml +++ b/src/SOL002/VNFConfiguration/definitions/SOL002VNFConfiguration_def.yaml @@ -78,7 +78,7 @@ definitions: Configuration parameters for the external CPs of the VNF instance. type: array items: - $ref: $ref: '#/definitions/CpConfiguration' + $ref: '#/definitions/CpConfiguration' dhcpServer: description: > IP address of the DHCP server that the VNF instance can use to obtain -- GitLab From 7e3e3c0dcbc11476d4f680963c04dde42c7f5d5a Mon Sep 17 00:00:00 2001 From: Giacomo Bernini Date: Mon, 10 Feb 2020 12:20:36 +0100 Subject: [PATCH 051/260] fix --- .../definitions/SOL002VNFConfiguration_def.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/SOL002/VNFConfiguration/definitions/SOL002VNFConfiguration_def.yaml b/src/SOL002/VNFConfiguration/definitions/SOL002VNFConfiguration_def.yaml index 62b8adff..71fd7e55 100644 --- a/src/SOL002/VNFConfiguration/definitions/SOL002VNFConfiguration_def.yaml +++ b/src/SOL002/VNFConfiguration/definitions/SOL002VNFConfiguration_def.yaml @@ -77,8 +77,8 @@ definitions: description: > Configuration parameters for the external CPs of the VNF instance. type: array - items: - $ref: '#/definitions/CpConfiguration' + items: + $ref: '#/definitions/CpConfiguration' dhcpServer: description: > IP address of the DHCP server that the VNF instance can use to obtain -- GitLab From 751ff3e16e48717800c49c82424a33bf643d34b2 Mon Sep 17 00:00:00 2001 From: Giacomo Bernini Date: Mon, 10 Feb 2020 12:54:08 +0100 Subject: [PATCH 052/260] fix-bis --- .../definitions/SOL002VNFConfiguration_def.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/SOL002/VNFConfiguration/definitions/SOL002VNFConfiguration_def.yaml b/src/SOL002/VNFConfiguration/definitions/SOL002VNFConfiguration_def.yaml index 71fd7e55..45d66889 100644 --- a/src/SOL002/VNFConfiguration/definitions/SOL002VNFConfiguration_def.yaml +++ b/src/SOL002/VNFConfiguration/definitions/SOL002VNFConfiguration_def.yaml @@ -105,8 +105,8 @@ definitions: description: > Configuration parameters for the internal CPs of the VNFC instance. type: array - items: - $ref: $ref: '#/definitions/CpConfiguration' + items: + $ref: '#/definitions/CpConfiguration' dhcpServer: description: > IP address of the DHCP server that the VNF instance can use to obtain -- GitLab From f9520ff7b7e8573454e4fed27ab3e334ebc7eac1 Mon Sep 17 00:00:00 2001 From: Francesca Moscatelli Date: Mon, 10 Feb 2020 15:50:11 +0100 Subject: [PATCH 053/260] SOL003_146: Individual VNF package artifact endpoints updated --- .../VNFPackageManagement.yaml | 149 +++++++++++++----- 1 file changed, 110 insertions(+), 39 deletions(-) diff --git a/src/SOL003/VNFPackageManagement/VNFPackageManagement.yaml b/src/SOL003/VNFPackageManagement/VNFPackageManagement.yaml index 741c21ef..820b9d60 100644 --- a/src/SOL003/VNFPackageManagement/VNFPackageManagement.yaml +++ b/src/SOL003/VNFPackageManagement/VNFPackageManagement.yaml @@ -1530,13 +1530,14 @@ paths: 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" - '/onboarded_vnf_packages/{vnfPkgId}/artifacts': + '/onboarded_vnf_packages/{vnfdId}/artifacts': parameters: - - name: vnfPkgId + - name: vnfdId description: > - Identifier of the VNF package. The identifier is allocated by the NFVO. - This identifier can be retrieved from the "vnfPkgId" attribute in the - VnfPackageOnboardingNotification or VnfPackageChangeNotification + Identifier of the VNFD and the VNF package. + The identifier is allocated by the VNF provider. + This identifier can be retrieved from the "vnfdId" attribute + in the VnfPackageOnboardingNotification or VnfPackageChangeNotification. in: path required: true type: string @@ -1701,13 +1702,22 @@ paths: parameters: - name: artifactPath description: > - Sequence of one or more path segments representing the path of - the artifact within the VNF package, relative to the root of the package. - EXAMPLE: foo/bar/run.sh - This identifier can be retrieved from the "artifactPath" attribute - of the applicable "additionalArtifacts" entry in the body of the - response to a GET request querying the "Individual VNF package" or - the "VNF packages" resource. + SequenceFor an artifact contained as a file in the VNF package, + this variable shall contain a sequence of one or more path segments + representing the path of the artifact within the VNF package, + relative to the root of the package. + + EXAMPLE: foo/bar/m%40ster.sh + + For an external artifact represented as a URI in the VNF package + manifest, this variable shall contain a sequence of one or more path + segments as synthesized by the NFVO (see clause 10.5.3.3), + representing this artifact. + + Since multiple path segments are allowed to be contained in this variable, + the "/" character that separates these segments is not percent-encoded. + Each individual segment is percent-encoded if necessary as defined in clause + 4.1 of ETSI GS NFV-SOL 013. in: path type: string required: true @@ -1747,8 +1757,9 @@ paths: The request may contain a "Range" HTTP header to obtain single range of bytes from the VNF package file. This can be used to continue an aborted transmission. - If the NFVO does not support range requests, it should return the - whole file with a 200 OK response instead. + If the "Range" header is present in the request and the NFVO + does not support responding to range requests with a 206 response, + it shall return a 200 OK response instead as defined below. in: header type: string - name: Version @@ -1757,16 +1768,40 @@ paths: in: header required: true type: string + - name: include_signatures + description: > + If this parameter is provided, the NFVO shall return the artifact + and related security information (such as signature and optional + certificate) in a ZIP archive. + If this parameter is not given, the NFVO shall provide only a copy + of the artifact file. + This URI query parameter is a flag, i.e. it shall have no value. + The NFVO shall support this parameter. + in: query + required: false + type: string responses: 200: description: > 200 OK - Shall be returned when the whole content of the artifact file has been read successfully. - The payload body shall contain a copy of the artifact file from the VNF package, - as defined by ETSI GS NFV-SOL 004. - The "Content-Type" HTTP header shall be set according to the content type of the artifact file. - If the content type cannot be determined, the header shall be set to the value "application/octet-stream". + Shall be returned when the whole content of the artifact file has + been read successfully. + + If the "include_signatures" request URI parameter was not provided in + the related request, the payload body shall contain a copy of the artifact + file from the VNF package, as defined by ETSI GS NFV-SOL 004 and the "Content-Type" + HTTP header shall be set according to the content type of the artifact file. + If the artifact is encrypted, the header shall be set to the value "application/cms" + (IETF RFC 7193). If the content type cannot be determined, the header shall be set + to the value "application/octet-stream". + + If the "include_signatures" request URI parameter was provided in the related request, + the "Content-Type" HTTP header shall be set to "application/zip and the payload body + shall contain a ZIP archive which includes: + • a copy of the artifact file from the VNF package, as defined by ETSI GS NFV SOL 004; + • the related security information (individual signature file and optional related + individual certificate file). headers: Content-Type: description: > @@ -1796,9 +1831,10 @@ paths: description: > 206 PARTIAL CONTENT - If the NFVO supports range requests, this response shall be returned - when a single consecutive byte range from the content of the artifact - file, if the NFVO supports range requests has been read successfully + If the NFVO supports range requests and the "include_signatures" request + URI parameter was not present in the related request, this response shall + be returned when a single consecutive byte range from the content of the + artifact file, if the NFVO supports range requests has been read successfully according to the request. The response body shall contain the requested part of the VNF package file. @@ -1874,13 +1910,22 @@ paths: parameters: - name: artifactPath description: > - Sequence of one or more path segments representing the path of - the artifact within the VNF package, relative to the root of the package. - EXAMPLE: foo/bar/run.sh - This identifier can be retrieved from the "artifactPath" attribute - of the applicable "additionalArtifacts" entry in the body of the - response to a GET request querying the "Individual VNF package" or - the "VNF packages" resource. + SequenceFor an artifact contained as a file in the VNF package, + this variable shall contain a sequence of one or more path segments + representing the path of the artifact within the VNF package, + relative to the root of the package. + + EXAMPLE: foo/bar/m%40ster.sh + + For an external artifact represented as a URI in the VNF package + manifest, this variable shall contain a sequence of one or more path + segments as synthesized by the NFVO (see clause 10.5.3.3), + representing this artifact. + + Since multiple path segments are allowed to be contained in this variable, + the "/" character that separates these segments is not percent-encoded. + Each individual segment is percent-encoded if necessary as defined in clause + 4.1 of ETSI GS NFV-SOL 013. in: path type: string required: true @@ -1919,8 +1964,9 @@ paths: The request may contain a "Range" HTTP header to obtain single range of bytes from the VNF package file. This can be used to continue an aborted transmission. - If the NFVO does not support range requests, it should return the - whole file with a 200 OK response instead. + If the "Range" header is present in the request and the NFVO + does not support responding to range requests with a 206 response, + it shall return a 200 OK response instead as defined below. in: header type: string - name: Version @@ -1929,16 +1975,40 @@ paths: in: header required: true type: string + - name: include_signatures + description: > + If this parameter is provided, the NFVO shall return the artifact + and related security information (such as signature and optional + certificate) in a ZIP archive. + If this parameter is not given, the NFVO shall provide only a copy + of the artifact file. + This URI query parameter is a flag, i.e. it shall have no value. + The NFVO shall support this parameter. + in: query + required: false + type: string responses: 200: description: > 200 OK - Shall be returned when the whole content of the artifact file has been read successfully. - The payload body shall contain a copy of the artifact file from the VNF package, - as defined by ETSI GS NFV-SOL 004. - The "Content-Type" HTTP header shall be set according to the content type of the artifact file. - If the content type cannot be determined, the header shall be set to the value "application/octet-stream". + Shall be returned when the whole content of the artifact file has + been read successfully. + + If the "include_signatures" request URI parameter was not provided in + the related request, the payload body shall contain a copy of the artifact + file from the VNF package, as defined by ETSI GS NFV-SOL 004 and the "Content-Type" + HTTP header shall be set according to the content type of the artifact file. + If the artifact is encrypted, the header shall be set to the value "application/cms" + (IETF RFC 7193). If the content type cannot be determined, the header shall be set + to the value "application/octet-stream". + + If the "include_signatures" request URI parameter was provided in the related request, + the "Content-Type" HTTP header shall be set to "application/zip and the payload body + shall contain a ZIP archive which includes: + • a copy of the artifact file from the VNF package, as defined by ETSI GS NFV SOL 004; + • the related security information (individual signature file and optional related + individual certificate file). headers: Content-Type: description: > @@ -1968,9 +2038,10 @@ paths: description: > 206 PARTIAL CONTENT - If the NFVO supports range requests, this response shall be returned - when a single consecutive byte range from the content of the artifact - file, if the NFVO supports range requests has been read successfully + If the NFVO supports range requests and the "include_signatures" request + URI parameter was not present in the related request, this response shall + be returned when a single consecutive byte range from the content of the + artifact file, if the NFVO supports range requests has been read successfully according to the request. The response body shall contain the requested part of the VNF package file. -- GitLab From 252a4d8515930884301c94ce43349ce586a9847e Mon Sep 17 00:00:00 2001 From: Francesca Moscatelli Date: Mon, 10 Feb 2020 16:18:23 +0100 Subject: [PATCH 054/260] SOL003_150: VnfPkgInfo updated --- .../VNFPackageManagement.yaml | 50 +++++++++---------- .../definitions/VNFPackageManagement_def.yaml | 41 +++++++++++++++ .../VNFPackageManagementNotification.yaml | 8 +-- 3 files changed, 70 insertions(+), 29 deletions(-) diff --git a/src/SOL003/VNFPackageManagement/VNFPackageManagement.yaml b/src/SOL003/VNFPackageManagement/VNFPackageManagement.yaml index 820b9d60..d6837479 100644 --- a/src/SOL003/VNFPackageManagement/VNFPackageManagement.yaml +++ b/src/SOL003/VNFPackageManagement/VNFPackageManagement.yaml @@ -2086,25 +2086,25 @@ paths: 406: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" 409: - description: > - 409 CONFLICT - - Shall be returned upon the following error: The operation cannot - be executed currently, due to a conflict with the state of the resource. - Typically, this is due to the fact that "onboardingState" of the - VNF package 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. +# description: > +# 409 CONFLICT +# +# Shall be returned upon the following error: The operation cannot +# be executed currently, due to a conflict with the state of the resource. +# Typically, this is due to the fact that "onboardingState" of the +# VNF package 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/SOL002SOL003_resp.yaml#/responses/409" 416: - description: > - 416 RANGE NOT SATISFIABLE - - Shall be returned upon the following error: The byte range passed in the - "Range" header did not match any available byte range in the artifact file - (e.g. "access after end of file"). - The response body may contain a ProblemDetails structure. +# description: > +# 416 RANGE NOT SATISFIABLE +# +# Shall be returned upon the following error: The byte range passed in the +# "Range" header did not match any available byte range in the artifact file +# (e.g. "access after end of file"). +# The response body may contain a ProblemDetails structure. $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" 500: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500" @@ -2212,14 +2212,14 @@ paths: items: $ref: "definitions/VNFPackageManagement_def.yaml#/definitions/PkgmSubscription" 303: - description: > - 303 SEE OTHER - - Shall be returned when a subscription with the same callbackURI and the same filter - already exists and the policy of the NFVO is to not create redundant subscriptions. - The HTTP response shall include a "Location" HTTP header that contains the resource - URI of the existing "Individual subscription" resource. - The response body shall be empty. +# description: > +# 303 SEE OTHER +# +# Shall be returned when a subscription with the same callbackURI and the same filter +# already exists and the policy of the NFVO is to not create redundant subscriptions. +# The HTTP response shall include a "Location" HTTP header that contains the resource +# URI of the existing "Individual subscription" resource. +# The response body shall be empty. $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/303" 400: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/400" diff --git a/src/SOL003/VNFPackageManagement/definitions/VNFPackageManagement_def.yaml b/src/SOL003/VNFPackageManagement/definitions/VNFPackageManagement_def.yaml index f48254f3..c923d38a 100644 --- a/src/SOL003/VNFPackageManagement/definitions/VNFPackageManagement_def.yaml +++ b/src/SOL003/VNFPackageManagement/definitions/VNFPackageManagement_def.yaml @@ -8,8 +8,10 @@ definitions: type: object required: - id + - packageSecurityOption - operationalState - usageState + - vnfmInfo - _links properties: id: @@ -51,12 +53,32 @@ definitions: It shall be present after the VNF package content has been on-boarded and absent otherwise. $ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/Version" + compatibleSpecificationVersions: + description: > + Indicates which versions of the ETSI GS NFV-SOL 004 specification the + package complies to, as defined in the manifest of the package. + Each entry shall be formatted as defined in clause 4.3.2 of ETSI GS NFV-SOL 004. + type: array + items: + $ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/Version" checksum: description: > Checksum of the on-boarded VNF package. It shall be present after the VNF package content has been on-boarded and absent otherwise. $ref: "#/definitions/Checksum" + packageSecurityOption: + description: > + Signals the security option used by the package as defined in clause 5.1 of ETSI GS NFV-SOL 004. + Valid values: OPTION_1, OPTION_2 + type: string + enum: + - OPTION_1 + - OPTION_2 + signingCertificate: + description: > + The singleton signing certificate if it is included as a file in the VNF package. + type: string softwareImages: description: > Information about VNF package artifacts that are software images. @@ -70,6 +92,12 @@ definitions: description: > Information about VNF package artifacts contained in the VNF package that are not software images. + Every local and external artifact declared in the manifest shall be + included, except the software images and the files that make up the + parts of the VNFD (see clause 10.4.4.3.2). + Signature files and certificate files are not considered as artifacts, + however, the content of the "Licenses" and "Testing" directories in the + VNF package is. This attribute shall not be present before the VNF package content is on-boarded. Otherwise, this attribute shall be present if the VNF package contains additional artifacts. @@ -94,10 +122,23 @@ definitions: "ONBOARDED", the value of the usageState attribute shall be equal to "NOT_IN_USE". $ref: "#/definitions/PackageUsageStateType" + vnfmInfo: + description: > + Specifies VNFMs compatible with the VNF. This information is copied from the VNFD. + ETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on + TOSCA specifications. userDefinedData: description: > User defined data for the VNF package. $ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/KeyValuePairs" + onboardingFailureDetails: + description: > + Failure details of current onboarding procedure. See clause 6.3 of ETSI GS NFV-SOL 013 + for the details of "ProblemDetails" structure. + If "onboardingState" is "ERROR", this attribute shall be present and contain error + information (such as failed onboarding or processing operation, affected artifact etc.), + unless it has been requested to be excluded via an attribute selector. + $ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/ProblemDetails" _links: description: > Links to resources related to this resource. diff --git a/src/SOL003/VNFPackageManagementNotification/VNFPackageManagementNotification.yaml b/src/SOL003/VNFPackageManagementNotification/VNFPackageManagementNotification.yaml index 89c29219..52e16d94 100644 --- a/src/SOL003/VNFPackageManagementNotification/VNFPackageManagementNotification.yaml +++ b/src/SOL003/VNFPackageManagementNotification/VNFPackageManagementNotification.yaml @@ -1,7 +1,7 @@ swagger: "2.0" info: - version: "1.3.0-impl:etsi.org:ETSI_NFV_OpenAPI:1" + version: "2.0.0-impl:etsi.org:ETSI_NFV_OpenAPI:1" title: SOL003 - VNF Package Management Notification interface description: > SOL003 - VNF Package Management Notification interface @@ -25,7 +25,7 @@ info: url: https://forge.etsi.org/etsi-forge-copyright-notice.txt externalDocs: - description: ETSI GS NFV-SOL 003 V2.6.1 + description: ETSI GS NFV-SOL 003 V2.7.1 url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.06.01_60/gs_NFV-SOL003v020601p.pdf basePath: "/callback/v1" @@ -116,7 +116,7 @@ paths: get: description: > - The GET method allows the server to test the notification endpoint that is provided by the client + The GET method allows the server to test the notification endpoint that is provided by the API consumer e.g. during subscription. This method shall follow the provisions specified in the tables 10.4.9.3.2-1 and 10.4.9.3.2-2 for URI query parameters, request and response data structures, and response codes. @@ -249,7 +249,7 @@ paths: get: description: > - The GET method allows the server to test the notification endpoint that is provided by the client + The GET method allows the server to test the notification endpoint that is provided by the API consumer e.g. during subscription. This method shall follow the provisions specified in the tables 10.4.9.3.2-1 and 10.4.9.3.2-2 for URI query parameters, request and response data structures, and response codes. -- GitLab From 54c82e235782d15e6dc5966bd1099769680d20e1 Mon Sep 17 00:00:00 2001 From: Francesca Moscatelli Date: Mon, 10 Feb 2020 16:25:14 +0100 Subject: [PATCH 055/260] SOL003_151: VnfPackageOnboardingNotification updated --- .../definitions/VNFPackageManagementNotification_def.yaml | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/src/SOL003/VNFPackageManagementNotification/definitions/VNFPackageManagementNotification_def.yaml b/src/SOL003/VNFPackageManagementNotification/definitions/VNFPackageManagementNotification_def.yaml index 7f70a108..8ff365b9 100644 --- a/src/SOL003/VNFPackageManagementNotification/definitions/VNFPackageManagementNotification_def.yaml +++ b/src/SOL003/VNFPackageManagementNotification/definitions/VNFPackageManagementNotification_def.yaml @@ -18,6 +18,7 @@ definitions: - timeStamp - vnfPkgId - vnfdId + - vnfmInfo - _links properties: id: @@ -54,6 +55,13 @@ definitions: the VNF package and the VNFD in a globally unique way. It's copied from the VNFD of the on-boarded VNF package. $ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/Identifier" + vnfmInfo: + description: > + Specifies VNFMs compatible with the VNF. + This information is copied from the VNFD. See table 10.5.2.2-1. + type: array + items: + $ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/String" _links: description: > Links to resources related to this notification. -- GitLab From 83f8a04400de0e3a0d63a85326b346dd73588174 Mon Sep 17 00:00:00 2001 From: Francesca Moscatelli Date: Mon, 10 Feb 2020 16:28:18 +0100 Subject: [PATCH 056/260] SOL003_152: VnfPackageSoftwareImageInfo updated --- .../definitions/VNFPackageManagement_def.yaml | 5 +++++ .../definitions/VNFPackageManagementNotification_def.yaml | 3 ++- 2 files changed, 7 insertions(+), 1 deletion(-) diff --git a/src/SOL003/VNFPackageManagement/definitions/VNFPackageManagement_def.yaml b/src/SOL003/VNFPackageManagement/definitions/VNFPackageManagement_def.yaml index c923d38a..4babc872 100644 --- a/src/SOL003/VNFPackageManagement/definitions/VNFPackageManagement_def.yaml +++ b/src/SOL003/VNFPackageManagement/definitions/VNFPackageManagement_def.yaml @@ -236,6 +236,7 @@ definitions: - provider - version - checksum + - isEncrypted - containerFormat - diskFormat - createdAt @@ -264,6 +265,10 @@ definitions: description: > Checksum of the software image file. $ref: "#/definitions/Checksum" + isEncrypted: + description: > + Reflects whether the image is encrypted (true) or not (false). + $ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/Boolean" containerFormat: description: > Container format indicates whether the software image is in a file diff --git a/src/SOL003/VNFPackageManagementNotification/definitions/VNFPackageManagementNotification_def.yaml b/src/SOL003/VNFPackageManagementNotification/definitions/VNFPackageManagementNotification_def.yaml index 8ff365b9..52d66fe3 100644 --- a/src/SOL003/VNFPackageManagementNotification/definitions/VNFPackageManagementNotification_def.yaml +++ b/src/SOL003/VNFPackageManagementNotification/definitions/VNFPackageManagementNotification_def.yaml @@ -80,7 +80,8 @@ definitions: * The "operationalState" attribute of a VNF package has changed, and the "onboardingState" attribute of the package has the value "ONBOARDED" (i.e. the package has been onboarded previously). - * The on-boarded VNF package has been deleted. + * The on-boarded VNF package has been deleted, and the "onboardingState" + attribute of the deleted package had the value "ONBOARDED". type: object required: - id -- GitLab From d8de4cd96cb2a9d583816091a4a3c5e5508357a7 Mon Sep 17 00:00:00 2001 From: Francesca Moscatelli Date: Mon, 10 Feb 2020 16:34:59 +0100 Subject: [PATCH 057/260] SOL003_153: VnfPackageArtifactInfo updated --- .../definitions/VNFPackageManagement_def.yaml | 60 +++++++++++++++++-- 1 file changed, 55 insertions(+), 5 deletions(-) diff --git a/src/SOL003/VNFPackageManagement/definitions/VNFPackageManagement_def.yaml b/src/SOL003/VNFPackageManagement/definitions/VNFPackageManagement_def.yaml index 4babc872..6f6cae63 100644 --- a/src/SOL003/VNFPackageManagement/definitions/VNFPackageManagement_def.yaml +++ b/src/SOL003/VNFPackageManagement/definitions/VNFPackageManagement_def.yaml @@ -356,20 +356,70 @@ definitions: required: - artifactPath - checksum + - isEncrypted properties: artifactPath: description: > - 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 "/". + Path in the VNF package, which identifies the artifact and + also allows to access a copy of the artifact. The + + For an artifact contained as a file in the VNF package, + this attribute shall be present, and the value of this + attribute shall start with the name of the first segment + in the path in the package, i.e. it shall not be prefixed + by path separator characters such as "." and "/". - EXAMPLE: foo/bar/run.sh + EXAMPLE: foo/bar/runm@ster.sh + + For an external artifact represented as a URI in the + VNF descriptor, this attribute shall be present if the + artifact has been downloaded by the NFVO and shall be + absent otherwise. If present, it shall contain the + artifactPath under which the artifact can be obtained + using the "Individual artifact in a VNF package" resource + defined in clause 10.4.6. It is the responsibility of the + NFVO to synthesize this path in a manner that avoids any + collision of the synthesized artifact path with the paths + and names of artifacts included in the package. type: string checksum: description: > Checksum of the artifact file. $ref: "#/definitions/Checksum" + isEncrypted: + description: > + Reflects whether the artifact is encrypted (true) or not (false). + $ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/Boolean" + artifactURI: + description: > + URI of the artifact as defined in the VNF package manifest. + Shall be present if the artifact is external to the package + and shall be absent otherwise. + + EXAMPLE: https://example.com/m%40ster.sh + type: array + items: + $ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/Uri" + nonManoArtifactSetId: + description: > + Non-MANO artifact set identifier of the non-MANO artifact set to + which the artifact belongs, as defined in clause 4.3.7 of ETSI GS NFV-SOL 004. + Shall be provided if the artifact is a non-MANO artifact, and shall be omitted otherwise. + $ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/String" + artifactClassification: + description: > + Marks specific types of artifacts as defined in the VNF package. + If none of the specific classes listed below applies, the attribute shall not be present. + + Valid values: + - HISTORY: a history artifact as per clause 4.3.3 in ETSI GS NFV-SOL 004 + - TESTING: a testing artifact as per clause 4.3.4 in ETSI GS NFV-SOL 004 + - LICENSE: a license artifact as per clause 4.3.5 in ETSI GS NFV-SOL 004 + type: string + enum: + - HISTORY + - TESTING + - LICENSE metadata: description: > The metadata of the artifact that are available in the VNF package, -- GitLab From a66e54324129e098a3908cc0497fedbab3744719 Mon Sep 17 00:00:00 2001 From: Francesca Moscatelli Date: Mon, 10 Feb 2020 16:40:14 +0100 Subject: [PATCH 058/260] SOL003_154: PkgmNotificationsFilter updated --- .../definitions/VNFPackageManagement_def.yaml | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/src/SOL003/VNFPackageManagement/definitions/VNFPackageManagement_def.yaml b/src/SOL003/VNFPackageManagement/definitions/VNFPackageManagement_def.yaml index 6f6cae63..802a6079 100644 --- a/src/SOL003/VNFPackageManagement/definitions/VNFPackageManagement_def.yaml +++ b/src/SOL003/VNFPackageManagement/definitions/VNFPackageManagement_def.yaml @@ -535,19 +535,25 @@ definitions: $ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/Identifier" operationalState: description: > - Match particular operational state of the VNF package. + Match particular operational states of the VNF package. May be present if the "notificationTypes" attribute contains the value "VnfPackageChangeNotification", and shall be absent otherwise. $ref: "#/definitions/PackageOperationalStateType" usageState: description: > - Match particular usage state of the VNF package. + Match particular usage states of the VNF package. May be present if the "notificationTypes" attribute contains the value "VnfPackageChangeNotification", and shall be absent otherwise. $ref: "#/definitions/PackageUsageStateType" - + vnfmInfo: + description: > + Match strings that specify VNFMs compatible with the VNF. See table 10.5.2.2-1. + type: array + items: + $ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/String" + Checksum: description: > This type represents the checksum of a VNF package or an artifact file. -- GitLab From 76b75986d53e9f18b2f2eab5c22b34db652ed247 Mon Sep 17 00:00:00 2001 From: Francesca Moscatelli Date: Mon, 10 Feb 2020 16:43:21 +0100 Subject: [PATCH 059/260] SOL003_155: PackageOperationalStateType updated --- .../definitions/VNFPackageManagement_def.yaml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/src/SOL003/VNFPackageManagement/definitions/VNFPackageManagement_def.yaml b/src/SOL003/VNFPackageManagement/definitions/VNFPackageManagement_def.yaml index 802a6079..0196f2e0 100644 --- a/src/SOL003/VNFPackageManagement/definitions/VNFPackageManagement_def.yaml +++ b/src/SOL003/VNFPackageManagement/definitions/VNFPackageManagement_def.yaml @@ -553,7 +553,7 @@ definitions: type: array items: $ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/String" - + Checksum: description: > This type represents the checksum of a VNF package or an artifact file. @@ -575,10 +575,10 @@ definitions: PackageOperationalStateType: description: > - ENABLED: The VNF package is enabled, i.e. it can be used for - instantiation of new VNF instances. - - DISABLED: The VNF package is disabled, i.e. it cannot be used for - further VNF instantiation requests (unless and until the VNF package - is re-enabled). + the creation of new "Individual VNF instance" resources. + - DISABLED: The VNF package is disabled, i.e. it shall not be used for + the creation of further "Individual VNF instance" resources + (unless and until the VNF package is re-enabled). type: string enum: - ENABLED -- GitLab From 6bb8dbf1f4e11c5b474b6f7646f9a54a69950cb9 Mon Sep 17 00:00:00 2001 From: Francesca Moscatelli Date: Mon, 10 Feb 2020 16:46:15 +0100 Subject: [PATCH 060/260] SOL003_156: PackageOnboardingStateType updated --- .../definitions/VNFPackageManagement_def.yaml | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/src/SOL003/VNFPackageManagement/definitions/VNFPackageManagement_def.yaml b/src/SOL003/VNFPackageManagement/definitions/VNFPackageManagement_def.yaml index 0196f2e0..1fb06e84 100644 --- a/src/SOL003/VNFPackageManagement/definitions/VNFPackageManagement_def.yaml +++ b/src/SOL003/VNFPackageManagement/definitions/VNFPackageManagement_def.yaml @@ -599,12 +599,14 @@ definitions: CREATED: The "Individual VNF package" resource has been created. UPLOADING: The associated VNF package content is being uploaded. PROCESSING: The associated VNF package content is being processed, e.g., - validation. - ONBOARDED: The associated VNF package content has been successfully - on-boarded. + validation. + ONBOARDED: The associated VNF package content has been on-boarded successfully. + ERROR: There was an error during upload of the VNF package content or external + artifacts, or during VNF package processing. type: string enum: - CREATED - UPLOADING - PROCESSING - - ONBOARDED \ No newline at end of file + - ONBOARDED + - ERROR \ No newline at end of file -- GitLab From 1fc06ec49157ed7584179d1b7ec0dd4ce52930c8 Mon Sep 17 00:00:00 2001 From: Francesca Moscatelli Date: Mon, 10 Feb 2020 17:04:54 +0100 Subject: [PATCH 061/260] SOL003: overall consolidation --- src/SOL003/APIVersion/APIVersion.yaml | 4 ++-- .../VNFFaultManagement.yaml | 6 ++--- src/SOL003/VNFIndicator/VNFIndicator.yaml | 4 ++-- .../VNFIndicatorNotification.yaml | 6 ++--- .../SOL003VNFLifecycleManagement_def.yaml | 16 +++++++------- .../VNFLifecycleOperationGranting.yaml | 4 ++-- .../VNFPackageManagement.yaml | 2 +- .../definitions/VNFPackageManagement_def.yaml | 22 +++++++++---------- .../VNFPackageManagementNotification.yaml | 2 +- .../VNFPerformanceManagement.yaml | 2 +- .../VNFPerformanceManagementNotification.yaml | 6 ++--- ...edResourcesQuotaAvailableNotification.yaml | 20 ++++++++--------- 12 files changed, 47 insertions(+), 47 deletions(-) diff --git a/src/SOL003/APIVersion/APIVersion.yaml b/src/SOL003/APIVersion/APIVersion.yaml index 4ca4ae57..1efc11ef 100644 --- a/src/SOL003/APIVersion/APIVersion.yaml +++ b/src/SOL003/APIVersion/APIVersion.yaml @@ -15,8 +15,8 @@ info: contact: name: "NFV-SOL WG" externalDocs: - description: ETSI GS NFV-SOL 003 V2.6.1 - url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.06.01_60/gs_NFV-SOL003v020601p.pdf + description: ETSI GS NFV-SOL 003 V2.7.1 + url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.07.01_60/gs_NFV-SOL003v020701p.pdf schemes: - http - https diff --git a/src/SOL003/VNFFaultManagement/VNFFaultManagement.yaml b/src/SOL003/VNFFaultManagement/VNFFaultManagement.yaml index e6f40394..503d84d7 100644 --- a/src/SOL003/VNFFaultManagement/VNFFaultManagement.yaml +++ b/src/SOL003/VNFFaultManagement/VNFFaultManagement.yaml @@ -470,7 +470,7 @@ paths: The API consumer can use this method to retrieve the list of active - subscriptions for VNF alarms subscribed by the client. It can be used + subscriptions for VNF alarms subscribed by the API consumer. It can be used e.g. for resynchronization after error situations. parameters: - name: Accept @@ -604,8 +604,8 @@ paths: get: description: > Query Subscription Information. - The client can use this method for reading an individual subscription for VNF alarms - subscribed by the client. + The API consumer can use this method for reading an individual subscription for VNF alarms + subscribed by the API consumer. This method shall follow the provisions specified in the tables 7.4.5.3.2-1 and 7.4.5.3.2-2 for URI query parameters, request and response data structures, and response codes. parameters: diff --git a/src/SOL003/VNFIndicator/VNFIndicator.yaml b/src/SOL003/VNFIndicator/VNFIndicator.yaml index eeb906a6..6e1740b2 100644 --- a/src/SOL003/VNFIndicator/VNFIndicator.yaml +++ b/src/SOL003/VNFIndicator/VNFIndicator.yaml @@ -14,8 +14,8 @@ info: url: https://forge.etsi.org/etsi-forge-copyright-notice.txt externalDocs: - description: ETSI GS NFV-SOL 003 V2.6.1 - url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.06.01_60/gs_NFV-SOL003v020601p.pdf + description: ETSI GS NFV-SOL 003 V2.7.1 + url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.07.01_60/gs_NFV-SOL003v020701p.pdf basePath: "/vnfind/v1" diff --git a/src/SOL003/VNFIndicatorNotification/VNFIndicatorNotification.yaml b/src/SOL003/VNFIndicatorNotification/VNFIndicatorNotification.yaml index eabfcf97..94194ad0 100644 --- a/src/SOL003/VNFIndicatorNotification/VNFIndicatorNotification.yaml +++ b/src/SOL003/VNFIndicatorNotification/VNFIndicatorNotification.yaml @@ -25,8 +25,8 @@ info: url: https://forge.etsi.org/etsi-forge-copyright-notice.txt externalDocs: - description: ETSI GS NFV-SOL 003 V2.6.1 - url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.06.01_60/gs_NFV-SOL003v020601p.pdf + description: ETSI GS NFV-SOL 003 V2.7.1 + url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.07.01_60/gs_NFV-SOL003v020701p.pdf basePath: "/callback/v1" @@ -111,7 +111,7 @@ paths: get: description: > - The GET method allows the server to test the notification endpoint that is provided by the client, + The GET method allows the server to test the notification endpoint that is provided by the API consumer, e.g. during subscription. This method shall follow the provisions specified in the tables 8.4.7.3.2-1 and 8.4.7.3.2-2 for URI query parameters, request and response data structures, and response codes. diff --git a/src/SOL003/VNFLifecycleManagement/definitions/SOL003VNFLifecycleManagement_def.yaml b/src/SOL003/VNFLifecycleManagement/definitions/SOL003VNFLifecycleManagement_def.yaml index abc6e30d..11b3331c 100644 --- a/src/SOL003/VNFLifecycleManagement/definitions/SOL003VNFLifecycleManagement_def.yaml +++ b/src/SOL003/VNFLifecycleManagement/definitions/SOL003VNFLifecycleManagement_def.yaml @@ -350,7 +350,7 @@ definitions: description: > Localization language of the VNF to be instantiated. The value shall comply with the format defined in IETF RFC 5646. - type: string + $ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/String" additionalParams: description: > Additional input parameters for the instantiation process, specific @@ -466,7 +466,7 @@ definitions: cause: description: > Indicates the reason why a healing procedure is required. - type: string + $ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/String" additionalParams: description: > Additional parameters passed by the NFVO as input to the healing @@ -566,12 +566,12 @@ definitions: description: > New value of the "vnfInstanceName" attribute in "VnfInstance", or "null" to remove the attribute. - type: string + $ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/String" vnfInstanceDescription: description: > New value of the "vnfInstanceDescription" attribute in "VnfInstance", or "null" to remove the attribute. - type: string + $ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/String" vnfPkgId: description: > New value of the "vnfPkgId" attribute in "VnfInstance". @@ -625,12 +625,12 @@ definitions: description: > If present, this attribute signals modifications of the "vnfInstanceName" attribute in "VnfInstance". - type: string + $ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/String" vnfInstanceDescription: description: > If present, this attribute signals modifications of the "vnfInstanceDescription" attribute in "VnfInstance". - type: string + $ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/String" vnfConfigurableProperties: description: > If present, this attribute signals modifications of the @@ -674,7 +674,7 @@ definitions: modify the "vnfPkgId" attribute, by copying the value of this attribute from the VNFD in the VNF Package identified by the "vnfPkgId” attribute. - type: string + $ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/String" vnfProductName: description: > If present, this attribute signals modifications of the @@ -684,7 +684,7 @@ definitions: modify the "vnfPkgId" attribute, by copying the value of this attribute from the VNFD in the VNF Package identified by the "vnfPkgId” attribute. - type: string + $ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/String" vnfSoftwareVersion: description: > If present, this attribute signals modifications of the diff --git a/src/SOL003/VNFLifecycleOperationGranting/VNFLifecycleOperationGranting.yaml b/src/SOL003/VNFLifecycleOperationGranting/VNFLifecycleOperationGranting.yaml index 9196c04e..79d7f229 100644 --- a/src/SOL003/VNFLifecycleOperationGranting/VNFLifecycleOperationGranting.yaml +++ b/src/SOL003/VNFLifecycleOperationGranting/VNFLifecycleOperationGranting.yaml @@ -25,8 +25,8 @@ info: url: https://forge.etsi.org/etsi-forge-copyright-notice.txt externalDocs: - description: ETSI GS NFV-SOL 003 V2.6.1 - url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.06.01_60/gs_NFV-SOL003v020601p.pdf + description: ETSI GS NFV-SOL 003 V2.7.1 + url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.07.01_60/gs_NFV-SOL003v020701p.pdf basePath: "/grant/v1" diff --git a/src/SOL003/VNFPackageManagement/VNFPackageManagement.yaml b/src/SOL003/VNFPackageManagement/VNFPackageManagement.yaml index d6837479..39356d35 100644 --- a/src/SOL003/VNFPackageManagement/VNFPackageManagement.yaml +++ b/src/SOL003/VNFPackageManagement/VNFPackageManagement.yaml @@ -26,7 +26,7 @@ info: externalDocs: description: ETSI GS NFV-SOL 003 V2.7.1 - url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.06.01_60/gs_NFV-SOL003v020601p.pdf + url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.07.01_60/gs_NFV-SOL003v020701p.pdf basePath: "/vnfpkgm/v1" diff --git a/src/SOL003/VNFPackageManagement/definitions/VNFPackageManagement_def.yaml b/src/SOL003/VNFPackageManagement/definitions/VNFPackageManagement_def.yaml index 1fb06e84..efb7f5c8 100644 --- a/src/SOL003/VNFPackageManagement/definitions/VNFPackageManagement_def.yaml +++ b/src/SOL003/VNFPackageManagement/definitions/VNFPackageManagement_def.yaml @@ -31,14 +31,14 @@ definitions: description: > Provider of the VNF package and the VNFD. This information is copied from the VNFD. - type: string + $ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/String" vnfProductName: description: > Name to identify the VNF product. Invariant for the VNF product lifetime. This information is copied from the VNFD. It shall be present after the VNF package content has been on-boarded and absent otherwise. - type: string + $ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/String" vnfSoftwareVersion: description: > Software version of the VNF. This is changed when there is any @@ -78,7 +78,7 @@ definitions: signingCertificate: description: > The singleton signing certificate if it is included as a file in the VNF package. - type: string + $ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/String" softwareImages: description: > Information about VNF package artifacts that are software images. @@ -252,11 +252,11 @@ definitions: name: description: > Name of the software image. - type: string + $ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/String" provider: description: > Provider of the software image. - type: string + $ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/String" version: description: > Version of the software image. @@ -346,7 +346,7 @@ definitions: description: > Path in the VNF package, which identifies the image artifact and also allows to access a copy of the image artifact. - type: string + $ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/String" VnfPackageArtifactInfo: description: > @@ -381,7 +381,7 @@ definitions: NFVO to synthesize this path in a manner that avoids any collision of the synthesized artifact path with the paths and names of artifacts included in the package. - type: string + $ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/String" checksum: description: > Checksum of the artifact file. @@ -470,7 +470,7 @@ definitions: vnfProvider: description: > Name of the VNF provider to match. - type: string + $ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/String" vnfProducts: description: > If present, match VNF packages that contain VNF products with @@ -484,7 +484,7 @@ definitions: vnfProductName: description: > Name of the VNF product to match. - type: string + $ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/String" versions: description: > If present, match VNF packages that contain VNF products @@ -566,11 +566,11 @@ definitions: description: > Name of the algorithm used to generate the checksum, as defined in ETSI GS NFV-SOL 004. For example, SHA-256, SHA-512. - type: string + $ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/String" hash: description: > The hexadecimal value of the checksum. - type: string + $ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/String" PackageOperationalStateType: description: > diff --git a/src/SOL003/VNFPackageManagementNotification/VNFPackageManagementNotification.yaml b/src/SOL003/VNFPackageManagementNotification/VNFPackageManagementNotification.yaml index 52e16d94..ad849f19 100644 --- a/src/SOL003/VNFPackageManagementNotification/VNFPackageManagementNotification.yaml +++ b/src/SOL003/VNFPackageManagementNotification/VNFPackageManagementNotification.yaml @@ -26,7 +26,7 @@ info: externalDocs: description: ETSI GS NFV-SOL 003 V2.7.1 - url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.06.01_60/gs_NFV-SOL003v020601p.pdf + url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.07.01_60/gs_NFV-SOL003v020701p.pdf basePath: "/callback/v1" diff --git a/src/SOL003/VNFPerformanceManagement/VNFPerformanceManagement.yaml b/src/SOL003/VNFPerformanceManagement/VNFPerformanceManagement.yaml index 9edb7d99..408c2134 100644 --- a/src/SOL003/VNFPerformanceManagement/VNFPerformanceManagement.yaml +++ b/src/SOL003/VNFPerformanceManagement/VNFPerformanceManagement.yaml @@ -150,7 +150,7 @@ paths: The API consumer can use this method to retrieve information about PM jobs. This method shall follow the provisions specified in the tables 6.4.2.3.2-1 and 6.4.2.3.2-2 for URI query parameters, request and response data structures, and response codes. - The client can use this method to retrieve information about PM jobs. + The API consumer can use this method to retrieve information about PM jobs. parameters: - name: Accept description: > diff --git a/src/SOL003/VNFPerformanceManagementNotification/VNFPerformanceManagementNotification.yaml b/src/SOL003/VNFPerformanceManagementNotification/VNFPerformanceManagementNotification.yaml index c28018ca..3379bb8b 100644 --- a/src/SOL003/VNFPerformanceManagementNotification/VNFPerformanceManagementNotification.yaml +++ b/src/SOL003/VNFPerformanceManagementNotification/VNFPerformanceManagementNotification.yaml @@ -48,7 +48,7 @@ paths: description: > Notify. The POST method delivers a notification regarding a performance management - event from the server to the client.API producer to an API consumer. + event from the API producer to an API consumer. The API consumer shall have previously created an "Individual PM Job" or "Individual threshold" resource. This method shall follow the provisions specified in the tables 6.4.9.3.1-1 and 6.4.9.3.1-2 for URI query parameters, request and response data structures, and response codes. @@ -182,7 +182,7 @@ paths: description: > Notify. The POST method delivers a notification regarding a performance management - event from the server to the client.API producer to an API consumer. + event from the API producer to an API consumer. The API consumer shall have previously created an "Individual subscription resource" with a matching filter. This method shall follow the provisions specified in the tables 6.4.9.3.1-1 and 6.4.9.3.1-2 for URI query parameters, request and response data structures, and response codes. @@ -252,7 +252,7 @@ paths: get: description: > - The GET method allows the server to test the notification endpoint that is provided by the client, + The GET method allows the server to test the notification endpoint that is provided by the API consumer e.g. during subscription. This method shall follow the provisions specified in the tables 6.4.9.3.2-1 and 6.4.9.3.2-2 for URI query parameters, request and response data structures, and response codes. diff --git a/src/SOL003/VirtualisedResourcesQuotaAvailableNotification/VirtualisedResourcesQuotaAvailableNotification.yaml b/src/SOL003/VirtualisedResourcesQuotaAvailableNotification/VirtualisedResourcesQuotaAvailableNotification.yaml index fae2c745..cfa61fb3 100644 --- a/src/SOL003/VirtualisedResourcesQuotaAvailableNotification/VirtualisedResourcesQuotaAvailableNotification.yaml +++ b/src/SOL003/VirtualisedResourcesQuotaAvailableNotification/VirtualisedResourcesQuotaAvailableNotification.yaml @@ -25,8 +25,8 @@ info: url: https://forge.etsi.org/etsi-forge-copyright-notice.txt externalDocs: - description: ETSI GS NFV-SOL 003 V2.6.1 - url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.06.01_60/gs_NFV-SOL003v020601p.pdf + description: ETSI GS NFV-SOL 003 V2.7.1 + url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.07.01_60/gs_NFV-SOL003v020701p.pdf basePath: "/vrqan/v1" @@ -137,14 +137,14 @@ paths: schema: $ref: "definitions/VirtualisedResourcesQuotaAvailableNotification_def.yaml#/definitions/VrQuotaAvailSubscription" 303: - description: > - 303 SEE OTHER - - Shall be returned when a subscription with the same callbackURI and the same - filter already exists and the policy of the NFVO is to not create redundant subscriptions. - The HTTP response shall include a "Location" HTTP header that contains the resource URI - of the existing "Individual subscription" resource. - The response body shall be empty. +# description: > +# 303 SEE OTHER +# +# Shall be returned when a subscription with the same callbackURI and the same +# filter already exists and the policy of the NFVO is to not create redundant subscriptions. +# The HTTP response shall include a "Location" HTTP header that contains the resource URI +# of the existing "Individual subscription" resource. +# The response body shall be empty. $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/303" 400: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/400" -- GitLab From a66defa05db9ec4245455689ccd66f350a5d84f6 Mon Sep 17 00:00:00 2001 From: Francesca Moscatelli Date: Wed, 12 Feb 2020 15:10:41 +0100 Subject: [PATCH 062/260] SOL003: fix in VNF pkg mgmt and VNF performance mgmt API version --- src/SOL003/VNFPackageManagement/VNFPackageManagement.yaml | 2 +- .../VNFPackageManagementNotification.yaml | 2 +- .../VNFPerformanceManagement/VNFPerformanceManagement.yaml | 2 +- .../VNFPerformanceManagementNotification.yaml | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/src/SOL003/VNFPackageManagement/VNFPackageManagement.yaml b/src/SOL003/VNFPackageManagement/VNFPackageManagement.yaml index 39356d35..99cd9c19 100644 --- a/src/SOL003/VNFPackageManagement/VNFPackageManagement.yaml +++ b/src/SOL003/VNFPackageManagement/VNFPackageManagement.yaml @@ -28,7 +28,7 @@ externalDocs: description: ETSI GS NFV-SOL 003 V2.7.1 url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.07.01_60/gs_NFV-SOL003v020701p.pdf -basePath: "/vnfpkgm/v1" +basePath: "/vnfpkgm/v2" schemes: - https diff --git a/src/SOL003/VNFPackageManagementNotification/VNFPackageManagementNotification.yaml b/src/SOL003/VNFPackageManagementNotification/VNFPackageManagementNotification.yaml index ad849f19..664b2b15 100644 --- a/src/SOL003/VNFPackageManagementNotification/VNFPackageManagementNotification.yaml +++ b/src/SOL003/VNFPackageManagementNotification/VNFPackageManagementNotification.yaml @@ -28,7 +28,7 @@ externalDocs: description: ETSI GS NFV-SOL 003 V2.7.1 url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.07.01_60/gs_NFV-SOL003v020701p.pdf -basePath: "/callback/v1" +basePath: "/callback/v2" schemes: - https diff --git a/src/SOL003/VNFPerformanceManagement/VNFPerformanceManagement.yaml b/src/SOL003/VNFPerformanceManagement/VNFPerformanceManagement.yaml index 408c2134..5439f47e 100644 --- a/src/SOL003/VNFPerformanceManagement/VNFPerformanceManagement.yaml +++ b/src/SOL003/VNFPerformanceManagement/VNFPerformanceManagement.yaml @@ -28,7 +28,7 @@ externalDocs: description: ETSI GS NFV-SOL 003 V2.7.1 url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.07.01_60/gs_NFV-SOL003v020701p.pdf -basePath: "/vnfpm/v1" +basePath: "/vnfpm/v2" schemes: - https diff --git a/src/SOL003/VNFPerformanceManagementNotification/VNFPerformanceManagementNotification.yaml b/src/SOL003/VNFPerformanceManagementNotification/VNFPerformanceManagementNotification.yaml index 3379bb8b..c6be960a 100644 --- a/src/SOL003/VNFPerformanceManagementNotification/VNFPerformanceManagementNotification.yaml +++ b/src/SOL003/VNFPerformanceManagementNotification/VNFPerformanceManagementNotification.yaml @@ -28,7 +28,7 @@ externalDocs: description: ETSI GS NFV-SOL 003 V2.7.1 url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.07.01_60/gs_NFV-SOL003v020701p.pdf -basePath: "/callback/v1" +basePath: "/callback/v2" schemes: - https -- GitLab From b662818474eef993c2e303a9d107a426099428d8 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Thu, 13 Feb 2020 11:43:41 +0100 Subject: [PATCH 063/260] SOL002_02 Api version Updated --- src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 86e663d9..757bec9d 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -1,7 +1,7 @@ swagger: "2.0" info: - version: "1.3.0-impl:etsi.org:ETSI_NFV_OpenAPI:1" + version: "1.4.0-impl:etsi.org:ETSI_NFV_OpenAPI:1" title: SOL002 - VNF Lifecycle Management interface description: > SOL002 - VNF Lifecycle Management interface -- GitLab From 58cbaf786d354fcab6731d84aa7aa2f0d07e25e2 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Thu, 13 Feb 2020 13:07:16 +0100 Subject: [PATCH 064/260] SOL002_125 Api Version Updated to 2.0.0 & v2 --- .../VNFPerformanceManagement/VNFPerformanceManagement.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml b/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml index 1a4c1780..b95c9f8e 100644 --- a/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml +++ b/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml @@ -1,7 +1,7 @@ swagger: "2.0" info: - version: "1.2.0-impl:etsi.org:ETSI_NFV_OpenAPI:1" + version: "2.0.0-impl:etsi.org:ETSI_NFV_OpenAPI:1" title: SOL002 - VNF Perfomance Management interface description: > SOL002 - VNF Performance Management interface @@ -20,7 +20,7 @@ externalDocs: description: ETSI GS NFV-SOL 002 V2.6.1 url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/002/02.06.01_60/gs_nfv-sol002v020601p.pdf -basePath: /vnfpm/v1 +basePath: /vnfpm/v2 schemes: - http -- GitLab From 7c83abc006705d7ab2664466463ff2a1a9d5dd32 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Thu, 13 Feb 2020 13:16:47 +0100 Subject: [PATCH 065/260] SOL002_168 Api version update to 1.3.0 --- src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml b/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml index c29936c7..389f3597 100644 --- a/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml +++ b/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml @@ -1,7 +1,7 @@ swagger: "2.0" info: - version: "1.2.0-impl:etsi.org:ETSI_NFV_OpenAPI:1" + version: "1.3.0-impl:etsi.org:ETSI_NFV_OpenAPI:1" title: SOL002 - VNF Fault Management interface description: > SOL002 - VNF Fault Management interface -- GitLab From 0124274da80e35ffad8b0900b6b6a923a32e077f Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Thu, 13 Feb 2020 13:21:21 +0100 Subject: [PATCH 066/260] SOL002_201 Api version Updated to 1.2.1 --- src/SOL002/VNFIndicator/VNFIndicator.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/SOL002/VNFIndicator/VNFIndicator.yaml b/src/SOL002/VNFIndicator/VNFIndicator.yaml index 83a0b779..699b246e 100644 --- a/src/SOL002/VNFIndicator/VNFIndicator.yaml +++ b/src/SOL002/VNFIndicator/VNFIndicator.yaml @@ -1,7 +1,7 @@ swagger: "2.0" info: - version: "1.2.0-impl:etsi.org:ETSI_NFV_OpenAPI:1" + version: "1.2.1-impl:etsi.org:ETSI_NFV_OpenAPI:1" title: SOL002 - VNF Indicator interface description: > SOL002 - VNF Indicator interface -- GitLab From aa029fe2d53a2f26a96178dc516815761e4beadf Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Fri, 14 Feb 2020 07:17:50 +0100 Subject: [PATCH 067/260] SOL002_08, SOL002_9 & SOL002_10 Updated --- .../VNFLifecycleManagement.yaml | 38 +++++++++++++++++++ 1 file changed, 38 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 757bec9d..54fb3cd5 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -289,7 +289,45 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" + put: + description: > + The PUT method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + patch: + description: > + The PATCH method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + delete: + description: > + The DELETE method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Individual VNF instance # ############################################################################### -- GitLab From d54cf01b7f79771663720b209023ea54f084cc17 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Fri, 14 Feb 2020 08:00:52 +0100 Subject: [PATCH 068/260] SOL002_12 unsupported method POST Added --- .../VNFLifecycleManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 54fb3cd5..618a096f 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -357,6 +357,19 @@ paths: in: header required: false type: string + post: + description: > + The POST method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" get: description: > Information about a VNF instance by reading an "Individual VNF instance". -- GitLab From d9b9fd5166b4723c8b250c55e06c1d04194e44d9 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Fri, 14 Feb 2020 08:06:52 +0100 Subject: [PATCH 069/260] SOL002_13 unsupported method PUT Added --- .../VNFLifecycleManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 618a096f..ecc307e6 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -426,6 +426,19 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" + put: + description: > + The PUT method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" patch: #SOL003 location: 5.4.3.3.4 description: > -- GitLab From 647a43c80d4e839393f99449a84db55d37872a44 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Fri, 14 Feb 2020 11:05:02 +0100 Subject: [PATCH 070/260] fix 409 Conflict response in patch operation --- src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index ecc307e6..4a662d37 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -515,7 +515,8 @@ paths: Typically, this is due to the fact that another LCM operation is ongoing. The response body shall contain a ProblemDetails structure, in which the "detail" attribute should convey more information about the error. - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" 412: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/412" 416: -- GitLab From 96fb2d1a0b083bf44d9eaae7a63054599a8f128e Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Fri, 14 Feb 2020 11:10:15 +0100 Subject: [PATCH 071/260] fix 409 Conflict response in delete operation --- src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 4a662d37..d4a49029 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -576,7 +576,8 @@ paths: Typically, this is due to the fact that the "Individual VNF instance" resource is in INSTANTIATED state. The response body shall contain a ProblemDetails structure, in which the "detail" attribute shall convey more information about the error. - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" 416: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" 422: -- GitLab From b447c3db7e03a15df548b342d39626eecfa519af Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Fri, 14 Feb 2020 11:20:02 +0100 Subject: [PATCH 072/260] fix 409 Conflict response in post operation --- src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index d4a49029..ddda55b7 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -689,7 +689,8 @@ paths: Typically, this is due to the fact that the "Individual VNF instance" resource is in INSTANTIATED state. The response body shall contain a ProblemDetails structure, in which the "detail" attribute shall convey more information about the error. - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" 416: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" 422: -- GitLab From 276c8377e67614b016cfa39b775589667f62ebb5 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Fri, 14 Feb 2020 11:26:03 +0100 Subject: [PATCH 073/260] SOL002_17 unsupported method GET Added --- .../VNFLifecycleManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index ddda55b7..2831c87e 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -703,6 +703,19 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" + get: + description: > + The GET method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Scale VNF task # -- GitLab From 5049f4763f3cb8647ff6b807adc33f012e14a3c8 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Fri, 14 Feb 2020 11:27:22 +0100 Subject: [PATCH 074/260] SOL002_18 unsupported method PUT Added --- .../VNFLifecycleManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 2831c87e..e1a4d773 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -716,7 +716,20 @@ paths: response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. schema: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + put: + description: > + The PUT method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + ############################################################################### # Scale VNF task # ############################################################################### -- GitLab From 6c30c8baa120b66053015c88b995b374ec523b32 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Fri, 14 Feb 2020 11:28:20 +0100 Subject: [PATCH 075/260] SOL002_19 unsupported method PATCH Added --- .../VNFLifecycleManagement.yaml | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index e1a4d773..0ec9b846 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -729,7 +729,19 @@ paths: response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. schema: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - + patch: + description: > + The PATCH method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Scale VNF task # ############################################################################### -- GitLab From c6a0c6c17aa2b33816cfbc1f3e88c2bd9bfd5a20 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Fri, 14 Feb 2020 11:29:04 +0100 Subject: [PATCH 076/260] SOL002_20 unsupported method DELETE Added --- .../VNFLifecycleManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 0ec9b846..59326b1b 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -737,6 +737,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + delete: + description: > + The DELETE method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From a24f8459bce2698cd8ffd96c2e38129954aeed38 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Fri, 14 Feb 2020 12:29:44 +0100 Subject: [PATCH 077/260] SOL002_237 fix 409 Conflict_response post operation --- src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 59326b1b..85e3deee 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -855,7 +855,8 @@ paths: or that another lifecycle management operation is ongoing. The response body shall contain a ProblemDetails structure, in which the "detail" attribute shall convey more information about the error. - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" 416: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" 422: -- GitLab From 2bdb08a8fbd3530d61706a26ca0584b06ca249fa Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Fri, 14 Feb 2020 12:32:56 +0100 Subject: [PATCH 078/260] SOL002_23 unsupported method GET Added --- .../VNFLifecycleManagement.yaml | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 85e3deee..bd5a2b1d 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -869,7 +869,19 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" + get: + description: > + The GET method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Scale VNF to Level task # ############################################################################### -- GitLab From c09aa86404965abdaea705448b3c2c8ea1eeaf12 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Fri, 14 Feb 2020 12:33:38 +0100 Subject: [PATCH 079/260] SOL002_24 unsupported method PUT Added --- .../VNFLifecycleManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index bd5a2b1d..0cea3c29 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -877,6 +877,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + put: + description: > + The PUT method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From 82a0c183f38ae0062426c88e8049ad11d9ee71e4 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Fri, 14 Feb 2020 12:34:16 +0100 Subject: [PATCH 080/260] SOL002_25 unsupported method PATCH Added --- .../VNFLifecycleManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 0cea3c29..dda98c1b 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -890,6 +890,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + patch: + description: > + The PATCH method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From 62fe31da9c1c2431e57e9dfdb49090a5b2f861cf Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Fri, 14 Feb 2020 12:34:51 +0100 Subject: [PATCH 081/260] SOL002_26 unsupported method DELETE Added --- .../VNFLifecycleManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index dda98c1b..d8c39e42 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -903,6 +903,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + delete: + description: > + The DELETE method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From 57339c09f187fc7fd89dff7f6ab436dff19a8219 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 07:06:36 +0100 Subject: [PATCH 082/260] SOL002_238 fix 409 Conflict_response post operation --- src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index d8c39e42..2f063ea2 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -1021,7 +1021,8 @@ paths: or that another lifecycle management operation is ongoing. The response body shall contain a ProblemDetails structure, in which the "detail" attribute shall convey more information about the error. - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" 416: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" 422: -- GitLab From d47f62bf536c75ea6d9ad10fac303b1327a19324 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 07:12:28 +0100 Subject: [PATCH 083/260] SOL002_29 unsupported method GET Added --- .../VNFLifecycleManagement.yaml | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 2f063ea2..8969b430 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -1035,7 +1035,19 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" + get: + description: > + The GET method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Change VNF Flavour task # ############################################################################### -- GitLab From 8a669d08d24e27fee8231d2ce9de249f2cc90cbd Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 07:13:21 +0100 Subject: [PATCH 084/260] SOL002_30 unsupported method PUT Added --- .../VNFLifecycleManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 8969b430..2c233e6a 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -1043,6 +1043,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + put: + description: > + The PUT method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From e6c3bb7cfbe797823133e15836f1b20f1637b57e Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 07:13:54 +0100 Subject: [PATCH 085/260] SOL002_31 unsupported method PATCH Added --- .../VNFLifecycleManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 2c233e6a..15c99180 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -1056,6 +1056,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + patch: + description: > + The PATCH method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From 114dec6fef5fa97c645848382ba7713a259eecbb Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 07:14:40 +0100 Subject: [PATCH 086/260] SOL002_32 unsupported method DELETE Added --- .../VNFLifecycleManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 15c99180..275aac6a 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -1069,6 +1069,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + delete: + description: > + The DELETE method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From 6d5ee06b366cc3032b6fc1f89e75196ff4c6ec6f Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 07:17:22 +0100 Subject: [PATCH 087/260] SOL002_239 fix 409 Conflict_response post operation --- src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 275aac6a..72897e4d 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -1186,7 +1186,8 @@ paths: or that another lifecycle management operation is ongoing. The response body shall contain a ProblemDetails structure, in which the "detail" attribute shall convey more information about the error. - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" + schema + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" 416: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" 422: -- GitLab From 2213c55c820da65ad67fc79a8a2c7611866f67af Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 07:20:35 +0100 Subject: [PATCH 088/260] SOL002_35 unsupported method GET Added --- .../VNFLifecycleManagement.yaml | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 72897e4d..87923c75 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -1200,7 +1200,19 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" + get: + description: > + The GET method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Terminate VNF task # ############################################################################### -- GitLab From 8aec8b3778dce34a78024e714b526a6d20940b27 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 07:21:17 +0100 Subject: [PATCH 089/260] SOL002_36 unsupported method PUT Added --- .../VNFLifecycleManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 87923c75..907e4a17 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -1208,6 +1208,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + put: + description: > + The PUT method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From d3358249dae00ba60426b8ec360fa0392aaafade Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 07:21:51 +0100 Subject: [PATCH 090/260] SOL002_37 unsupported method PATCH Added --- .../VNFLifecycleManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 907e4a17..2658df7e 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -1221,6 +1221,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + patch: + description: > + The PATCH method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From e405da4551209e4b47fe9fe64e1e63d0e67692e5 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 07:22:32 +0100 Subject: [PATCH 091/260] SOL002_38 unsupported method DELETE Added --- .../VNFLifecycleManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 2658df7e..559338ed 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -1234,6 +1234,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + delete: + description: > + The DELETE method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From d1bd640b928a3ae9342e58022be02343c2d0f918 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 07:30:26 +0100 Subject: [PATCH 092/260] SOL002_240 fix 409 Conflict_response post operation --- src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 559338ed..d436aeb4 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -1350,7 +1350,8 @@ paths: or that another lifecycle management operation is ongoing. The response body shall contain a ProblemDetails structure, in which the "detail" attribute shall convey more information about the error. - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" 416: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" 422: -- GitLab From 06fac516df6b42daddf38dc003a0c1a1a5fe24d3 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 07:33:58 +0100 Subject: [PATCH 093/260] SOL002_41 unsupported method GET Added --- .../VNFLifecycleManagement.yaml | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index d436aeb4..f969d95d 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -1364,7 +1364,19 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" + get: + description: > + The GET method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Heal VNF task # ############################################################################### -- GitLab From f32d49491bd1a474a25f462f1c9a295271f6b26a Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 07:35:08 +0100 Subject: [PATCH 094/260] SOL002_42 unsupported method PUT Added --- .../VNFLifecycleManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index f969d95d..7192a97f 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -1372,6 +1372,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + put: + description: > + The PUT method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From 450da84e25a49575e4263fd89b921b5643b29684 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 07:36:05 +0100 Subject: [PATCH 095/260] SOL002_43 unsupported method PATCH Added --- .../VNFLifecycleManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 7192a97f..e4266519 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -1385,6 +1385,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + patch: + description: > + The PATCH method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From 80dc89351031420135ebf66304f4d39a2714bf1e Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 07:36:34 +0100 Subject: [PATCH 096/260] SOL002_44 unsupported method DELETE Added --- .../VNFLifecycleManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index e4266519..2de98bb4 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -1398,6 +1398,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + delete: + description: > + The DELETE method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From ced67f404c85012a81f5e50149abca7c1f324381 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 07:39:28 +0100 Subject: [PATCH 097/260] SOL002_241 fix 409 Conflict_response post operation --- src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 2de98bb4..44af501d 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -1514,7 +1514,8 @@ paths: or that another lifecycle management operation is ongoing. The response body shall contain a ProblemDetails structure, in which the "detail" attribute shall convey more information about the error. - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" 416: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" 422: -- GitLab From 24ab4ca3eff76e0ecfc5ea528075799d39d8d0f0 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 07:43:22 +0100 Subject: [PATCH 098/260] SOL002_47 unsupported method GET Added --- .../VNFLifecycleManagement.yaml | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 44af501d..bc494a01 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -1528,7 +1528,19 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" + get: + description: > + The GET method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Operate VNF task # ############################################################################### -- GitLab From 1b29a5f8c7bbfd0f3082abcd45c72ca3a71ad163 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 07:43:56 +0100 Subject: [PATCH 099/260] SOL002_48 unsupported method PUT Added --- .../VNFLifecycleManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index bc494a01..f656ca03 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -1536,6 +1536,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + put: + description: > + The PUT method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From 99a60f93d381213d780498cf85d62fc63ff98396 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 07:44:28 +0100 Subject: [PATCH 100/260] SOL002_49 unsupported method PATCH Added --- .../VNFLifecycleManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index f656ca03..b7b808aa 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -1549,6 +1549,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + patch: + description: > + The PATCH method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From 3ebda0c16ff97e460610359f70e38037028db9d0 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 07:45:29 +0100 Subject: [PATCH 101/260] SOL002_52 unsupported method DELETE Added --- .../VNFLifecycleManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index b7b808aa..b19a78d4 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -1562,6 +1562,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + delete: + description: > + The DELETE method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From 7a5e0dabca1f39e7d22ed63dc217497848fec0b1 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 07:47:41 +0100 Subject: [PATCH 102/260] SOL002_242 fix 409 Conflict_response post operation --- src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index b19a78d4..766fc3f7 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -1678,7 +1678,8 @@ paths: or that another lifecycle management operation is ongoing. The response body shall contain a ProblemDetails structure, in which the "detail" attribute shall convey more information about the error. - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" 416: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" 422: -- GitLab From 4966dd25d5c6e61ecaa65faa07552aa887be7da1 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 07:49:38 +0100 Subject: [PATCH 103/260] SOL002_53 unsupported method GET Added --- .../VNFLifecycleManagement.yaml | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 766fc3f7..77811953 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -1692,7 +1692,19 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" + get: + description: > + The GET method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Change external VNF connectivity task # ############################################################################### -- GitLab From 8047e12e05bde235edceccbbe6b813d181094e7c Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 07:50:46 +0100 Subject: [PATCH 104/260] SOL002_54 unsupported method PUT Added --- .../VNFLifecycleManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 77811953..a2655fef 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -1700,6 +1700,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + put: + description: > + The PUT method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From 4573a6f036c9feb053e3750962f3736c8c0a9378 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 07:51:38 +0100 Subject: [PATCH 105/260] SOL002_55 unsupported method PATCH Added --- .../VNFLifecycleManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index a2655fef..84548c6d 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -1713,6 +1713,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + patch: + description: > + The PATCH method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From 78426966994837ac9ef5ce14dea016335c51e694 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 07:52:24 +0100 Subject: [PATCH 106/260] SOL002_56 unsupported method DELETE Added --- .../VNFLifecycleManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 84548c6d..487f8e9c 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -1726,6 +1726,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + delete: + description: > + The DELETE method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From 2b4a44a550d322f22be81c4c9e469424658c5a03 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 07:55:40 +0100 Subject: [PATCH 107/260] SOL002_243 fix 409 Conflict_response post operation --- src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 487f8e9c..e516290d 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -1843,7 +1843,8 @@ paths: Typically, this is due to the fact that another lifecycle management operation is ongoing. The response body shall contain a ProblemDetails structure, in which the "detail" attribute shall convey more information about the error. - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" 416: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" 422: -- GitLab From 2ad7942f684b84e932aebe3f03f5726ba18a1091 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 07:59:12 +0100 Subject: [PATCH 108/260] SOL002_59 unsupported method GET Added --- .../VNFLifecycleManagement.yaml | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index e516290d..291c2792 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -1857,7 +1857,19 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" + get: + description: > + The GET method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # VNF LCM operation occurrences # ############################################################################### -- GitLab From 3cb6ec51c665df172d9600bf80a02c0f49258cf1 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 07:59:59 +0100 Subject: [PATCH 109/260] SOL002_60 unsupported method PUT Added --- .../VNFLifecycleManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 291c2792..12e26f6f 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -1865,6 +1865,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + put: + description: > + The PUT method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From 856acc36de3d5df7775574b9dc89e329a7e0c73e Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 08:00:32 +0100 Subject: [PATCH 110/260] SOL002_61 unsupported method PATCH Added --- .../VNFLifecycleManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 12e26f6f..560377ae 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -1878,6 +1878,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + patch: + description: > + The PATCH method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From 9eff2be85b95bada98652127ff4be584a5a6096b Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 08:01:17 +0100 Subject: [PATCH 111/260] SOL002_62 unsupported method DELETE Added --- .../VNFLifecycleManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 560377ae..ee9ddbce 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -1891,6 +1891,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + delete: + description: > + The DELETE method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From 43283a3ba96f819937434dea9a1654530e668574 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 08:04:47 +0100 Subject: [PATCH 112/260] SOL002_64 unsupported method POST Added --- .../VNFLifecycleManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index ee9ddbce..5ecfc96f 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -1928,6 +1928,19 @@ paths: in: header required: false type: string + post: + description: > + The POST method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" get: description: > The client can use this method to query status information about -- GitLab From 6c5e146cf5d805614cfc3c89dc49c8252effc522 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 08:06:59 +0100 Subject: [PATCH 113/260] SOL002_65 unsupported method PUT Added --- .../VNFLifecycleManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 5ecfc96f..6c057b1b 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -2089,6 +2089,19 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" + put: + description: > + The PUT method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Individual VNF LCM operation occurrence # ############################################################################### -- GitLab From fa8dc4ee839d82389ddf558634c361979e50e6c4 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 08:07:33 +0100 Subject: [PATCH 114/260] SOL002_66 unsupported method PATCH Added --- .../VNFLifecycleManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 6c057b1b..39fb832f 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -2097,6 +2097,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + patch: + description: > + The PATCH method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From 16cf372419bcc35737a9e1632908cc02dad1455f Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 08:08:18 +0100 Subject: [PATCH 115/260] SOL002_67 unsupported method DELETE Added --- .../VNFLifecycleManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 39fb832f..a768b507 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -2110,6 +2110,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + delete: + description: > + The DELETE method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From fa87b327f43e2c5a43d297c5d7294f7a301d916d Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 08:10:15 +0100 Subject: [PATCH 116/260] SOL002_70 unsupported method POST Added --- .../VNFLifecycleManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index a768b507..e2c04ee6 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -2158,6 +2158,19 @@ paths: in: header required: false type: string + post: + description: > + The POST method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" get: description: > The client can use this method to retrieve status information about a -- GitLab From 35b2bbf49c549a0fcbf4058370f4fb40808b4c0a Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 08:19:12 +0100 Subject: [PATCH 117/260] SOL002_71 unsupported method PUT Added --- .../VNFLifecycleManagement.yaml | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index e2c04ee6..14fc45d7 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -2229,7 +2229,19 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" + put: + description: > + The PUT method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Retry operation task # ############################################################################### -- GitLab From ce05bbef8a974dcacc724f8049e64126fba14a7c Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 08:19:52 +0100 Subject: [PATCH 118/260] SOL002_72 unsupported method PATCH Added --- .../VNFLifecycleManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 14fc45d7..064a77d9 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -2237,6 +2237,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + patch: + description: > + The PATCH method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From 86fa4e8aa7cc6606c3741437f925c41b65f6f417 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 08:20:24 +0100 Subject: [PATCH 119/260] SOL002_73 unsupported method DELETE Added --- .../VNFLifecycleManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 064a77d9..32f1716d 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -2250,6 +2250,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + delete: + description: > + The DELETE method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From 998512b203561209408aea5ef5ca57f80e1f34f0 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 08:23:20 +0100 Subject: [PATCH 120/260] SOL002_244 fix 409 Conflict_response post operation --- src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 32f1716d..7d758765 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -2348,7 +2348,8 @@ paths: or another error handling action is starting such as rollback or fail. The response body shall contain a ProblemDetails structure, in which the "detail" attribute shall convey more information about the error. - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" 416: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" 422: -- GitLab From 816d992caea790458fb150694809d781df90a6d3 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 08:24:47 +0100 Subject: [PATCH 121/260] SOL002_76 unsupported method GET Added --- .../VNFLifecycleManagement.yaml | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 7d758765..d1a0ae1a 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -2362,7 +2362,19 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" + get: + description: > + The GET method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Rollback operation task # ############################################################################### -- GitLab From dff3a0dc90f1af70204036f4c3484615e1c6e594 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 08:25:29 +0100 Subject: [PATCH 122/260] SOL002_77 unsupported method PUT Added --- .../VNFLifecycleManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index d1a0ae1a..99f84369 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -2370,6 +2370,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + put: + description: > + The PUT method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From 1fc190262051247e159f972ef766e58c54a7de2b Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 08:26:28 +0100 Subject: [PATCH 123/260] SOL002_78 unsupported method PATCH Added --- .../VNFLifecycleManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 99f84369..b0f5b612 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -2383,6 +2383,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + patch: + description: > + The PATCH method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From 58cd64b433f8f4aa21423e583b796f647db020df Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 08:27:08 +0100 Subject: [PATCH 124/260] SOL002_79 unsupported method DELETE Added --- .../VNFLifecycleManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index b0f5b612..94915489 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -2396,6 +2396,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + delete: + description: > + The DELETE method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From 29867a603b8f72c21591ecb83797e91b2bc951b7 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 08:28:50 +0100 Subject: [PATCH 125/260] SOL002_245 fix 409 Conflict_response post operation --- src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 94915489..ec273233 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -2493,7 +2493,8 @@ paths: or another error handling action is starting such as rollback or fail. The response body shall contain a ProblemDetails structure, in which the "detail" attribute shall convey more information about the error. - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" 416: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" 422: -- GitLab From 7a1786923a7c0df095523c5a24046a721e939ada Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 10:21:59 +0100 Subject: [PATCH 126/260] SOL002_82 unsupported method GET Added --- .../VNFLifecycleManagement.yaml | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index ec273233..06f36265 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -2507,7 +2507,19 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" + get: + description: > + The GET method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Fail operation task # ############################################################################### -- GitLab From 346fa53e3d3fb063fd0b7173519d62eccd6bdabf Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 10:23:29 +0100 Subject: [PATCH 127/260] SOL002_83 unsupported method PUT Added --- .../VNFLifecycleManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 06f36265..dd250ec3 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -2515,6 +2515,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + put: + description: > + The PUT method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From 8e1c4ba6f78717a1a13b5b41bef3e92500d2d05f Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 10:24:06 +0100 Subject: [PATCH 128/260] SOL002_84 unsupported method PATCH Added --- .../VNFLifecycleManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index dd250ec3..f2e33fa8 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -2528,6 +2528,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + patch: + description: > + The PATCH method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From 5efc512043a3a2ccbba8b892f01ce8438f581e7b Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 10:24:38 +0100 Subject: [PATCH 129/260] SOL002_85 unsupported method DELETE Added --- .../VNFLifecycleManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index f2e33fa8..055204f0 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -2541,6 +2541,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + delete: + description: > + The DELETE method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From 16d6d79dd41e06902e3a9dbbf12769d864e1418c Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 10:26:19 +0100 Subject: [PATCH 130/260] SOL002_246 fix 409 Conflict_response post operation --- src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 055204f0..71f25a3e 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -2645,7 +2645,8 @@ paths: or another error handling action is starting such as rollback or fail. The response body shall contain a ProblemDetails structure, in which the "detail" attribute shall convey more information about the error. - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" 416: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" 422: -- GitLab From 14d79740d43ed55e6cebc0edd0f252649642a6c9 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 10:29:08 +0100 Subject: [PATCH 131/260] SOL002_88 unsupported method GET Added --- .../VNFLifecycleManagement.yaml | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 71f25a3e..82d5d62e 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -2659,7 +2659,19 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" + get: + description: > + The GET method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Cancel operation task # ############################################################################### -- GitLab From d7ee306352a3ca57292fd376624188788990c7b4 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 10:29:58 +0100 Subject: [PATCH 132/260] SOL002_89 unsupported method PUT Added --- .../VNFLifecycleManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 82d5d62e..c720bbe0 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -2667,6 +2667,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + put: + description: > + The PUT method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From 990f2c2c637cef7148da3ba8a9ce8320bd0ed607 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 10:30:33 +0100 Subject: [PATCH 133/260] SOL002_90 unsupported method PATCH Added --- .../VNFLifecycleManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index c720bbe0..788a1df1 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -2680,6 +2680,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + patch: + description: > + The PATCH method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From fb63819383f65901b515f2b29660cd803fe6fa87 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 10:31:05 +0100 Subject: [PATCH 134/260] SOL002_91 unsupported method DELETE Added --- .../VNFLifecycleManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 788a1df1..dfc7b6a7 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -2693,6 +2693,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + delete: + description: > + The DELETE method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From d61b8adc44ed02c1d309db8fc68440934b199ba8 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 10:32:28 +0100 Subject: [PATCH 135/260] SOL002_247 fix 409 Conflict_response post operation --- src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index dfc7b6a7..e264c432 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -2792,7 +2792,8 @@ paths: PROCESSING or ROLLING_BACK state. The response body shall contain a ProblemDetails structure, in which the "detail" attribute shall convey more information about the error. - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" 416: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" 422: -- GitLab From ad9c938f181a14504a05e03d8fe92bf451549b71 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 10:33:55 +0100 Subject: [PATCH 136/260] SOL002_94 unsupported method GET Added --- .../VNFLifecycleManagement.yaml | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index e264c432..94fbc1ad 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -2806,7 +2806,19 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" + get: + description: > + The GET method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Subscriptions # ############################################################################### -- GitLab From 452b5e118d571037de824fdcfd20f705139ac4aa Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 10:35:02 +0100 Subject: [PATCH 137/260] SOL002_95 unsupported method PUT Added --- .../VNFLifecycleManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 94fbc1ad..ee0481c5 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -2814,6 +2814,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + put: + description: > + The PUT method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From 730d7d772d539c1268c07fed7af92566caa79690 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 10:35:39 +0100 Subject: [PATCH 138/260] SOL002_96 unsupported method PATCH Added --- .../VNFLifecycleManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index ee0481c5..60da7956 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -2827,6 +2827,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + patch: + description: > + The PATCH method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From 5cbffbbfd39a8b20d7b385430f6d49eddbd28b3d Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 10:36:29 +0100 Subject: [PATCH 139/260] SOL002_97 unsupported method DELETE Added --- .../VNFLifecycleManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 60da7956..aa732166 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -2840,6 +2840,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + delete: + description: > + The DELETE method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From 13074513a7959e1a6ab4254e8d934e10858a95b2 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 10:40:30 +0100 Subject: [PATCH 140/260] SOL002_248 fix 303 see_other post operation --- src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index aa732166..77d12032 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -2931,7 +2931,8 @@ paths: The HTTP response shall include a "Location" HTTP header that contains the resource URI of the existing subscription resource. The response body shall be empty. - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/303" + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/303" 400: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/400" 401: -- GitLab From 867a8fddaf85b4502487ca1edd3345f4bac466a8 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 10:44:01 +0100 Subject: [PATCH 141/260] SOL002_103 unsupported method PUT Added --- .../VNFLifecycleManagement.yaml | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 77d12032..b3d6e6bd 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -3049,7 +3049,19 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" + put: + description: > + The PUT method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Individual subscription # ############################################################################### -- GitLab From 342d6b8501446a601ff7aca68742c3e4d7107a2a Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 10:44:37 +0100 Subject: [PATCH 142/260] SOL002_104 unsupported method PATCH Added --- .../VNFLifecycleManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index b3d6e6bd..06577d6c 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -3057,6 +3057,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + patch: + description: > + The PATCH method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From 9c210d1926f1a4dca7452ee63947408a052836e3 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 10:45:07 +0100 Subject: [PATCH 143/260] SOL002_105 unsupported method DELETE Added --- .../VNFLifecycleManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 06577d6c..85f257d0 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -3070,6 +3070,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + delete: + description: > + The DELETE method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From 6697e2aaa15a9dcfa8a590bd303a82445350e0a1 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 10:48:19 +0100 Subject: [PATCH 144/260] SOL002_107 unsupported method POST Added --- .../VNFLifecycleManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 85f257d0..c215ffc6 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -3117,6 +3117,19 @@ paths: in: header required: false type: string + post: + description: > + The POST method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" get: description: > The GET method retrieves information about a subscription by reading -- GitLab From f3dbcca1ecd2f2019e55975f3188b3098b1bb1ce Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 10:49:25 +0100 Subject: [PATCH 145/260] SOL002_108 unsupported method PUT Added --- .../VNFLifecycleManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index c215ffc6..e61a1eee 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -3187,6 +3187,19 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" + put: + description: > + The PUT method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" delete: description: > The DELETE method terminates an individual subscription. -- GitLab From 9b0dc53eb2f34e7454da0f57699250083a187b70 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 10:50:53 +0100 Subject: [PATCH 146/260] SOL002_109 unsupported method PATCH Added --- .../VNFLifecycleManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index e61a1eee..6af01454 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -3195,6 +3195,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + patch: + description: > + The PATCH method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From 0050dfc324339d3449e83060e4df7266b8b46e20 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 11:20:31 +0100 Subject: [PATCH 147/260] SOL002_112 unsupported method PUT Added to all three DataType in Request_body VnfLcmOperationOccurenceNotification, VnfIdentifierCreationNotification & VnfIdentifierDeletionNotification --- .../VNFLifecycleManagementNotification.yaml | 45 ++++++++++++++++++- 1 file changed, 44 insertions(+), 1 deletion(-) diff --git a/src/SOL002/VNFLifecycleManagementNotification/VNFLifecycleManagementNotification.yaml b/src/SOL002/VNFLifecycleManagementNotification/VNFLifecycleManagementNotification.yaml index c9436051..1564ab0e 100644 --- a/src/SOL002/VNFLifecycleManagementNotification/VNFLifecycleManagementNotification.yaml +++ b/src/SOL002/VNFLifecycleManagementNotification/VNFLifecycleManagementNotification.yaml @@ -168,7 +168,21 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500" 503: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" + put: + description: > + Notify + + The PUT method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Notification endpoint VnfIdentifierCreationNotification # ############################################################################### @@ -306,7 +320,21 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500" 503: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" + put: + description: > + Notify + The PUT method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Notification endpoint VnfIdentifierDeletionNotification # ############################################################################### @@ -443,4 +471,19 @@ paths: 500: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500" 503: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" \ No newline at end of file + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" + put: + description: > + Notify + + The PUT method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" \ No newline at end of file -- GitLab From 246d6935c922c23d4353ea07da29f4c8acfe9718 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 11:24:59 +0100 Subject: [PATCH 148/260] SOL002_113 unsupported method PATCH Added to all three DataType in Request_body VnfLcmOperationOccurenceNotification, VnfIdentifierCreationNotification & VnfIdentifierDeletionNotification --- .../VNFLifecycleManagementNotification.yaml | 39 +++++++++++++++++++ 1 file changed, 39 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagementNotification/VNFLifecycleManagementNotification.yaml b/src/SOL002/VNFLifecycleManagementNotification/VNFLifecycleManagementNotification.yaml index 1564ab0e..32a38a38 100644 --- a/src/SOL002/VNFLifecycleManagementNotification/VNFLifecycleManagementNotification.yaml +++ b/src/SOL002/VNFLifecycleManagementNotification/VNFLifecycleManagementNotification.yaml @@ -178,6 +178,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + patch: + description: > + The PATCH method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. @@ -330,6 +343,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + patch: + description: > + The PATCH method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. @@ -482,6 +508,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + patch: + description: > + The PATCH method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From e8a70dad3a723eb42bb5b81d2e2e76f358fcb1e7 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 11:28:06 +0100 Subject: [PATCH 149/260] SOL002_114 unsupported method DELETE Added to all three DataType in Request_body VnfLcmOperationOccurenceNotification, VnfIdentifierCreationNotification & VnfIdentifierDeletionNotification --- .../VNFLifecycleManagementNotification.yaml | 39 +++++++++++++++++++ 1 file changed, 39 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagementNotification/VNFLifecycleManagementNotification.yaml b/src/SOL002/VNFLifecycleManagementNotification/VNFLifecycleManagementNotification.yaml index 32a38a38..3684dea6 100644 --- a/src/SOL002/VNFLifecycleManagementNotification/VNFLifecycleManagementNotification.yaml +++ b/src/SOL002/VNFLifecycleManagementNotification/VNFLifecycleManagementNotification.yaml @@ -191,6 +191,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + delete: + description: > + The DELETE method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. @@ -356,6 +369,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + delete: + description: > + The DELETE method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. @@ -521,6 +547,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + delete: + description: > + The DELETE method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From 0cc38648d2259d788b04b48db9d2571d84a99abe Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 12:21:07 +0100 Subject: [PATCH 150/260] SOL002_131 unsupported method PUT Added --- .../VNFPerformanceManagement.yaml | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml b/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml index b95c9f8e..c9de8285 100644 --- a/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml +++ b/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml @@ -306,7 +306,19 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" + put: + description: > + The PUT method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Individual PM job # ############################################################################### -- GitLab From 844395467f5c92f36024c77e52d343168b3bfd74 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 12:21:48 +0100 Subject: [PATCH 151/260] SOL002_132 unsupported method PATCH Added --- .../VNFPerformanceManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml b/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml index c9de8285..43fcc025 100644 --- a/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml +++ b/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml @@ -314,6 +314,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + patch: + description: > + The PATCH method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From ce9927e101cfb22198c2c5f93732d240614d2b92 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 12:22:46 +0100 Subject: [PATCH 152/260] SOL002_133 unsupported method DELETE Added --- .../VNFPerformanceManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml b/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml index 43fcc025..a788de91 100644 --- a/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml +++ b/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml @@ -327,6 +327,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + delete: + description: > + The DELETE method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From feb365609937a68d92587f268b1018d509792612 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 12:26:15 +0100 Subject: [PATCH 153/260] SOL002_135 unsupported method POST Added --- .../VNFPerformanceManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml b/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml index a788de91..ac19bae4 100644 --- a/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml +++ b/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml @@ -374,6 +374,19 @@ paths: in: header required: false type: string + post: + description: > + The POST method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" get: description: > The client can use this method for reading an individual PM job. -- GitLab From 3d2af88a9e0751945e9720625005560a38fb9d6c Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 12:28:25 +0100 Subject: [PATCH 154/260] SOL002_136 unsupported method PUT Added --- .../VNFPerformanceManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml b/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml index ac19bae4..1042e1f1 100644 --- a/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml +++ b/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml @@ -452,6 +452,19 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" + put: + description: > + The PUT method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" delete: description: > This method terminates an individual PM job. -- GitLab From bc10063e1f1019f9fd8b98c66643a7e5b6dfa05e Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 12:33:40 +0100 Subject: [PATCH 155/260] SOL002_139 unsupported method POST Added --- .../VNFPerformanceManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml b/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml index 1042e1f1..04b3e9d5 100644 --- a/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml +++ b/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml @@ -552,6 +552,19 @@ paths: in: header required: false type: string + post: + description: > + The POST method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" get: description: > The client can use this method for reading an individual performance -- GitLab From ee9cf9dedbc92504ca4d180570b22d73d0ed9a51 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 12:34:40 +0100 Subject: [PATCH 156/260] SOL002_140 unsupported method PUT Added --- .../VNFPerformanceManagement.yaml | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml b/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml index 04b3e9d5..30613dfc 100644 --- a/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml +++ b/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml @@ -631,7 +631,19 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" + put: + description: > + The PUT method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Thresholds # ############################################################################### -- GitLab From 30160e5e73a11979a08f37cf2959a46636b90352 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 12:35:17 +0100 Subject: [PATCH 157/260] SOL002_141 unsupported method PATCH Added --- .../VNFPerformanceManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml b/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml index 30613dfc..547ba99c 100644 --- a/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml +++ b/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml @@ -639,6 +639,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + patch: + description: > + The PATCH method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From 987a863e79f869b8ff06e31e7adbb6894f6ea9a3 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 12:36:47 +0100 Subject: [PATCH 158/260] SOL002_142 unsupported method DELETE Added --- .../VNFPerformanceManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml b/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml index 547ba99c..8d508191 100644 --- a/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml +++ b/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml @@ -652,6 +652,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + delete: + description: > + The DELETE method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From 3a9fee5e25e4331689c22abb3187b58cc2ba06a6 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 12:39:32 +0100 Subject: [PATCH 159/260] SOL002_144 unsupported method PUT Added --- .../VNFPerformanceManagement.yaml | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml b/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml index 8d508191..e897bac7 100644 --- a/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml +++ b/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml @@ -899,7 +899,19 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" + put: + description: > + The PUT method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Individual threshold # ############################################################################### -- GitLab From 04020323a60652c3c1a95f953460132a212ec3db Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 12:40:14 +0100 Subject: [PATCH 160/260] SOL002_145 unsupported method PATCH Added --- .../VNFPerformanceManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml b/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml index e897bac7..be301092 100644 --- a/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml +++ b/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml @@ -907,6 +907,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + patch: + description: > + The PATCH method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From 05938f3cd6664fdd616472fe5773b3394339ea69 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 12:41:01 +0100 Subject: [PATCH 161/260] SOL002_146 unsupported method DELETE Added --- .../VNFPerformanceManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml b/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml index be301092..5fd53f5a 100644 --- a/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml +++ b/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml @@ -920,6 +920,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + delete: + description: > + The DELETE method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From 16f82c6035ca07780ff3222d0d0fbc18f2b4458f Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 12:47:04 +0100 Subject: [PATCH 162/260] SOL002_148 unsupported method POST Added --- .../VNFPerformanceManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml b/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml index 5fd53f5a..96f3b1b4 100644 --- a/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml +++ b/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml @@ -967,6 +967,19 @@ paths: in: header required: false type: string + post: + description: > + The POST method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" get: description: > The client can use this method for reading an individual threshold. -- GitLab From 93f0b7b71707cd44e62e35fa65a819e99e455730 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Mon, 17 Feb 2020 12:48:10 +0100 Subject: [PATCH 163/260] SOL002_149 unsupported method PUT Added --- .../VNFPerformanceManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml b/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml index 96f3b1b4..bc07f861 100644 --- a/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml +++ b/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml @@ -1044,6 +1044,19 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" + put: + description: > + The PUT method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" delete: description: > This method allows to delete a threshold. -- GitLab From 8f94c6e1869c3adc6159717ce7b27649a5d466b3 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 18 Feb 2020 07:48:14 +0100 Subject: [PATCH 164/260] SOL002_153 unsupported method PUT Added to all two DataType in Request_body PerformanceInformationAvailableNotification & ThresholdCrossedNotification --- .../VNFPerformanceManagementNotification.yaml | 27 ++++++++++++++++++- 1 file changed, 26 insertions(+), 1 deletion(-) diff --git a/src/SOL002/VNFPerformanceManagementNotification/VNFPerformanceManagementNotification.yaml b/src/SOL002/VNFPerformanceManagementNotification/VNFPerformanceManagementNotification.yaml index 239a1fbb..f556ab1c 100644 --- a/src/SOL002/VNFPerformanceManagementNotification/VNFPerformanceManagementNotification.yaml +++ b/src/SOL002/VNFPerformanceManagementNotification/VNFPerformanceManagementNotification.yaml @@ -163,7 +163,19 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500" 503: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" + put: + description: > + The PUT method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Notification endpoint ThresholdCrossedNotification # ############################################################################### @@ -293,4 +305,17 @@ paths: 500: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500" 503: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" \ No newline at end of file + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" + put: + description: > + The PUT method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" \ No newline at end of file -- GitLab From 68f6f719c3b37e2dd3e4ab5bc66665454acd7550 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 18 Feb 2020 07:52:29 +0100 Subject: [PATCH 165/260] SOL002_154 unsupported method PATCH Added to all two DataType in Request_body PerformanceInformationAvailableNotification & ThresholdCrossedNotification --- .../VNFPerformanceManagementNotification.yaml | 26 +++++++++++++++++++ 1 file changed, 26 insertions(+) diff --git a/src/SOL002/VNFPerformanceManagementNotification/VNFPerformanceManagementNotification.yaml b/src/SOL002/VNFPerformanceManagementNotification/VNFPerformanceManagementNotification.yaml index f556ab1c..5b35f861 100644 --- a/src/SOL002/VNFPerformanceManagementNotification/VNFPerformanceManagementNotification.yaml +++ b/src/SOL002/VNFPerformanceManagementNotification/VNFPerformanceManagementNotification.yaml @@ -171,6 +171,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + patch: + description: > + The PATCH method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. @@ -314,6 +327,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + patch: + description: > + The PATCH method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From 3e69e0eb2880048b7d114de5b5b827b5d02fa391 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 18 Feb 2020 07:53:14 +0100 Subject: [PATCH 166/260] SOL002_155 unsupported method DELETE Added to all two DataType in Request_body PerformanceInformationAvailableNotification & ThresholdCrossedNotification --- .../VNFPerformanceManagementNotification.yaml | 26 +++++++++++++++++++ 1 file changed, 26 insertions(+) diff --git a/src/SOL002/VNFPerformanceManagementNotification/VNFPerformanceManagementNotification.yaml b/src/SOL002/VNFPerformanceManagementNotification/VNFPerformanceManagementNotification.yaml index 5b35f861..0a8e28ce 100644 --- a/src/SOL002/VNFPerformanceManagementNotification/VNFPerformanceManagementNotification.yaml +++ b/src/SOL002/VNFPerformanceManagementNotification/VNFPerformanceManagementNotification.yaml @@ -184,6 +184,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + delete: + description: > + The DELETE method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. @@ -340,6 +353,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + delete: + description: > + The DELETE method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From edf22844e7ba824d3e1bac417f3f851cfe8af3d6 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 18 Feb 2020 07:58:55 +0100 Subject: [PATCH 167/260] SOL002_170 unsupported method POST Added --- .../VNFFaultManagement/VNFFaultManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml b/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml index 389f3597..31b313e1 100644 --- a/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml +++ b/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml @@ -58,6 +58,19 @@ paths: in: header required: false type: string + post: + description: > + The POST method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" get: description: > The client can use this method to retrieve information about the alarm -- GitLab From 971c3bdbc3bc406d3b1ffe0eea534680f6a968ae Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 18 Feb 2020 07:59:49 +0100 Subject: [PATCH 168/260] SOL002_171 unsupported method PUT Added --- .../VNFFaultManagement/VNFFaultManagement.yaml | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml b/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml index 31b313e1..67068db9 100644 --- a/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml +++ b/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml @@ -199,7 +199,19 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" + put: + description: > + The PUT method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Individual alarm # ############################################################################### -- GitLab From 986314c5f915d34a387a2b8d75197759aba82cdc Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 18 Feb 2020 08:00:23 +0100 Subject: [PATCH 169/260] SOL002_172 unsupported method PATCH Added --- .../VNFFaultManagement/VNFFaultManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml b/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml index 67068db9..7cc281a9 100644 --- a/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml +++ b/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml @@ -207,6 +207,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + patch: + description: > + The PATCH method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From eda24ddb60afb66c0afb48220affcb0134a9e89b Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 18 Feb 2020 08:00:52 +0100 Subject: [PATCH 170/260] SOL002_173 unsupported method DELETE Added --- .../VNFFaultManagement/VNFFaultManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml b/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml index 7cc281a9..58266877 100644 --- a/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml +++ b/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml @@ -220,6 +220,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + delete: + description: > + The DELETE method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From 5f1e12435459b4907d538bc2fb1a987b13f6204a Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 18 Feb 2020 08:05:26 +0100 Subject: [PATCH 171/260] SOL002_175 unsupported method POST Added --- .../VNFFaultManagement/VNFFaultManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml b/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml index 58266877..4174e4da 100644 --- a/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml +++ b/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml @@ -268,6 +268,19 @@ paths: in: header required: false type: string + post: + description: > + The POST method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" get: description: > The client can use this method to read an individual alarm. -- GitLab From bfb5a03dc6852ca8e909ffab64a4fe6c9741812d Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 18 Feb 2020 08:07:14 +0100 Subject: [PATCH 172/260] SOL002_176 unsupported method PUT Added --- .../VNFFaultManagement/VNFFaultManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml b/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml index 4174e4da..2fa8dd0c 100644 --- a/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml +++ b/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml @@ -353,6 +353,19 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" + put: + description: > + The PUT method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" patch: description: > This method modifies an individual alarm resource. -- GitLab From e5781f46fd4df4def49612f9b013b0464836a703 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 18 Feb 2020 08:10:07 +0100 Subject: [PATCH 173/260] SOL002_249 fix 409 Conflict_response patch operation --- src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml b/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml index 2fa8dd0c..a3091314 100644 --- a/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml +++ b/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml @@ -442,7 +442,8 @@ paths: alarm). The response body shall contain a ProblemDetails structure, in which the "detail" attribute shall convey more information about the error. - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" 412: description: > 412 PRECONDITION FAILED -- GitLab From 79363a59fbbd077f54cfc94a62d8732684c00685 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 18 Feb 2020 08:12:56 +0100 Subject: [PATCH 174/260] SOL002_250 fix 412 PreCondition_Failed_response patch operation --- src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml b/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml index a3091314..03fa1e6b 100644 --- a/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml +++ b/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml @@ -454,7 +454,8 @@ paths: modified by another entity. The response body should contain a ProblemDetails structure, in which the "detail" attribute should convey more information about the error. - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/412" + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/412" 416: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" 422: -- GitLab From b294b4011133ae926ccc0a76a6e363e4a00c3843 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 18 Feb 2020 08:14:21 +0100 Subject: [PATCH 175/260] SOL002_177 unsupported method DELETE Added --- .../VNFFaultManagement/VNFFaultManagement.yaml | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml b/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml index 03fa1e6b..1bc5648a 100644 --- a/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml +++ b/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml @@ -468,7 +468,19 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" + delete: + description: > + The DELETE method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Escalate Perceived Severity task # ############################################################################### -- GitLab From a6d6b9ac1d9123a01dc21335131de29e6b642f7a Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 18 Feb 2020 08:17:11 +0100 Subject: [PATCH 176/260] SOL002_179 unsupported method GET Added --- .../VNFFaultManagement/VNFFaultManagement.yaml | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml b/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml index 1bc5648a..eb0a5c35 100644 --- a/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml +++ b/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml @@ -561,7 +561,19 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" + get: + description: > + The GET method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Subscriptions # ############################################################################### -- GitLab From 551243afd1a41cd6acbceb6e2f4c4cdb8d24f10a Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 18 Feb 2020 08:17:54 +0100 Subject: [PATCH 177/260] SOL002_180 unsupported method PUT Added --- .../VNFFaultManagement/VNFFaultManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml b/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml index eb0a5c35..ed1f56a7 100644 --- a/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml +++ b/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml @@ -569,6 +569,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + put: + description: > + The PUT method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From 0700b8d9ad211f45886292f33f2672538691efef Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 18 Feb 2020 08:18:29 +0100 Subject: [PATCH 178/260] SOL002_181 unsupported method PATCH Added --- .../VNFFaultManagement/VNFFaultManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml b/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml index ed1f56a7..69fe050b 100644 --- a/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml +++ b/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml @@ -582,6 +582,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + patch: + description: > + The PATCH method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From ff9261430386b5cc9703c0ca15886ab72725ad3c Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 18 Feb 2020 08:19:01 +0100 Subject: [PATCH 179/260] SOL002_182 unsupported method DELETE Added --- .../VNFFaultManagement/VNFFaultManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml b/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml index 69fe050b..ab97a92a 100644 --- a/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml +++ b/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml @@ -595,6 +595,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + delete: + description: > + The DELETE method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From 54754f831cfb96f6a50edc8a752b90e15b17e4af Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 18 Feb 2020 08:32:29 +0100 Subject: [PATCH 180/260] SOL002_251 fix 303 See_Other_response post operation --- src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml b/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml index ab97a92a..cb879f70 100644 --- a/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml +++ b/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml @@ -700,7 +700,8 @@ paths: The HTTP response shall include a "Location" HTTP header that contains the resource URI of the existing subscription resource. The response body shall be empty. - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/303" + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/303" 400: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/400" 401: -- GitLab From baa80603dd68d882320e02fa23dedae17aed2c63 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 18 Feb 2020 08:34:27 +0100 Subject: [PATCH 181/260] SOL002_185 unsupported method PUT Added --- .../VNFFaultManagement/VNFFaultManagement.yaml | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml b/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml index cb879f70..662910d9 100644 --- a/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml +++ b/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml @@ -854,7 +854,19 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" + put: + description: > + The PUT method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Individual subscription # ############################################################################### -- GitLab From f9480b76128d0d5d16cca31cfdbf99af3709e8c3 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 18 Feb 2020 08:34:57 +0100 Subject: [PATCH 182/260] SOL002_186 unsupported method PATCH Added --- .../VNFFaultManagement/VNFFaultManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml b/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml index 662910d9..dbf09ea8 100644 --- a/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml +++ b/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml @@ -862,6 +862,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + patch: + description: > + The PATCH method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From d59f56609aaed5a320911c2436bcb14e53c2bf09 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 18 Feb 2020 08:35:23 +0100 Subject: [PATCH 183/260] SOL002_187 unsupported method DELETE Added --- .../VNFFaultManagement/VNFFaultManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml b/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml index dbf09ea8..324354b1 100644 --- a/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml +++ b/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml @@ -875,6 +875,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + delete: + description: > + The DELETE method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From ff1697b262368c982ca07edf79b69e155f0ea2d1 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 18 Feb 2020 08:37:49 +0100 Subject: [PATCH 184/260] SOL002_189 unsupported method POST Added --- .../VNFFaultManagement/VNFFaultManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml b/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml index 324354b1..d87d36e2 100644 --- a/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml +++ b/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml @@ -922,6 +922,19 @@ paths: in: header required: false type: string + post: + description: > + The POST method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" get: description: > The client can use this method for reading an individual subscription -- GitLab From 2fdeddaf58666feb1b3cf32c2fbcb451e060a8a7 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 18 Feb 2020 08:38:55 +0100 Subject: [PATCH 185/260] SOL002_190 unsupported method PUT Added --- .../VNFFaultManagement/VNFFaultManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml b/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml index d87d36e2..0ec928b3 100644 --- a/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml +++ b/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml @@ -1008,6 +1008,19 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" + put: + description: > + The PUT method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" delete: description: > This method terminates an individual subscription. -- GitLab From 3807c8f772806735d4c8db5a46ff4b5871adfa90 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 18 Feb 2020 08:40:10 +0100 Subject: [PATCH 186/260] SOL002_191 unsupported method PATCH Added --- .../VNFFaultManagement/VNFFaultManagement.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml b/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml index 0ec928b3..309e1ca2 100644 --- a/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml +++ b/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml @@ -1016,6 +1016,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + patch: + description: > + The PATCH method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From 651b1d7891d707f4c647e5a1c9ac1c38263ccb33 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 18 Feb 2020 08:48:28 +0100 Subject: [PATCH 187/260] SOL002_192 unsupported method PUT Added to all three DataType in Request_body AlarmNotification, AlarmClearedNotification & AlarmListBuiltNotification --- .../VNFFaultManagementNotification.yaml | 39 ++++++++++++++++++- 1 file changed, 38 insertions(+), 1 deletion(-) diff --git a/src/SOL002/VNFFaultManagementNotification/VNFFaultManagementNotification.yaml b/src/SOL002/VNFFaultManagementNotification/VNFFaultManagementNotification.yaml index f817f87c..32fc01d0 100644 --- a/src/SOL002/VNFFaultManagementNotification/VNFFaultManagementNotification.yaml +++ b/src/SOL002/VNFFaultManagementNotification/VNFFaultManagementNotification.yaml @@ -151,7 +151,19 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500" 503: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" + put: + description: > + The PUT method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Notification endpoint AlarmClearedNotification # ############################################################################### @@ -270,7 +282,19 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500" 503: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" + put: + description: > + The PUT method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Notification endpoint AlarmListRebuiltNotification # ############################################################################### @@ -388,4 +412,17 @@ paths: 500: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500" 503: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" \ No newline at end of file + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" + put: + description: > + The PUT method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" \ No newline at end of file -- GitLab From 2435521f5c7eb381a9aff43f0c7558a1a98af43f Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 18 Feb 2020 08:49:45 +0100 Subject: [PATCH 188/260] SOL002_193 unsupported method PATCH Added to all three DataType in Request_body AlarmNotification, AlarmClearedNotification & AlarmListBuiltNotification --- .../VNFFaultManagementNotification.yaml | 39 +++++++++++++++++++ 1 file changed, 39 insertions(+) diff --git a/src/SOL002/VNFFaultManagementNotification/VNFFaultManagementNotification.yaml b/src/SOL002/VNFFaultManagementNotification/VNFFaultManagementNotification.yaml index 32fc01d0..076b8f63 100644 --- a/src/SOL002/VNFFaultManagementNotification/VNFFaultManagementNotification.yaml +++ b/src/SOL002/VNFFaultManagementNotification/VNFFaultManagementNotification.yaml @@ -159,6 +159,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + patch: + description: > + The PATCH method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. @@ -290,6 +303,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + patch: + description: > + The PATCH method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. @@ -421,6 +447,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + patch: + description: > + The PATCH method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From 7b9937b060fa45e155b829ec262477953f7c5796 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 18 Feb 2020 08:50:40 +0100 Subject: [PATCH 189/260] SOL002_194 unsupported method DELETE Added to all three DataType in Request_body AlarmNotification, AlarmClearedNotification & AlarmListBuiltNotification --- .../VNFFaultManagementNotification.yaml | 39 +++++++++++++++++++ 1 file changed, 39 insertions(+) diff --git a/src/SOL002/VNFFaultManagementNotification/VNFFaultManagementNotification.yaml b/src/SOL002/VNFFaultManagementNotification/VNFFaultManagementNotification.yaml index 076b8f63..28267df6 100644 --- a/src/SOL002/VNFFaultManagementNotification/VNFFaultManagementNotification.yaml +++ b/src/SOL002/VNFFaultManagementNotification/VNFFaultManagementNotification.yaml @@ -172,6 +172,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + delete: + description: > + The DELETE method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. @@ -316,6 +329,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + delete: + description: > + The DELETE method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. @@ -460,6 +486,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + delete: + description: > + The DELETE method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From 3767992fecdcb1dd58b893d9311e0f7ea17c8e21 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 18 Feb 2020 08:54:23 +0100 Subject: [PATCH 190/260] SOL002_203 unsupported method POST Added --- src/SOL002/VNFIndicator/VNFIndicator.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFIndicator/VNFIndicator.yaml b/src/SOL002/VNFIndicator/VNFIndicator.yaml index 699b246e..6caf6def 100644 --- a/src/SOL002/VNFIndicator/VNFIndicator.yaml +++ b/src/SOL002/VNFIndicator/VNFIndicator.yaml @@ -57,6 +57,19 @@ paths: in: header required: false type: string + post: + description: > + The POST method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" get: summary: Query multiple indicators description: Get a list of indicators. Support of attribute based filtering via query parameters. -- GitLab From 27afb65454c5b9999406c62684840b1a0abfce78 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 18 Feb 2020 08:55:44 +0100 Subject: [PATCH 191/260] SOL002_204 unsupported method PUT Added --- src/SOL002/VNFIndicator/VNFIndicator.yaml | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/src/SOL002/VNFIndicator/VNFIndicator.yaml b/src/SOL002/VNFIndicator/VNFIndicator.yaml index 6caf6def..4f5e0643 100644 --- a/src/SOL002/VNFIndicator/VNFIndicator.yaml +++ b/src/SOL002/VNFIndicator/VNFIndicator.yaml @@ -178,7 +178,19 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" + put: + description: > + The PUT method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # VNF indicators related to a VNF instance # ############################################################################### -- GitLab From 0c6aa5c46451c947b5dea3269219f2ec77b0620a Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 18 Feb 2020 08:56:14 +0100 Subject: [PATCH 192/260] SOL002_205 unsupported method PATCH Added --- src/SOL002/VNFIndicator/VNFIndicator.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFIndicator/VNFIndicator.yaml b/src/SOL002/VNFIndicator/VNFIndicator.yaml index 4f5e0643..88cc4969 100644 --- a/src/SOL002/VNFIndicator/VNFIndicator.yaml +++ b/src/SOL002/VNFIndicator/VNFIndicator.yaml @@ -186,6 +186,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + patch: + description: > + The PATCH method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From 5b6e8082c1c5fa49e11bd685c18816c784b1975e Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 18 Feb 2020 08:56:48 +0100 Subject: [PATCH 193/260] SOL002_206 unsupported method DELETE Added --- src/SOL002/VNFIndicator/VNFIndicator.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFIndicator/VNFIndicator.yaml b/src/SOL002/VNFIndicator/VNFIndicator.yaml index 88cc4969..5f0d5ed3 100644 --- a/src/SOL002/VNFIndicator/VNFIndicator.yaml +++ b/src/SOL002/VNFIndicator/VNFIndicator.yaml @@ -199,6 +199,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + delete: + description: > + The DELETE method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From 7823fa55301eac8d0f080a7c8f37ff05c288f9d6 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 18 Feb 2020 10:30:36 +0100 Subject: [PATCH 194/260] SOL002_208 unsupported method POST Added --- src/SOL002/VNFIndicator/VNFIndicator.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFIndicator/VNFIndicator.yaml b/src/SOL002/VNFIndicator/VNFIndicator.yaml index 5f0d5ed3..52a21959 100644 --- a/src/SOL002/VNFIndicator/VNFIndicator.yaml +++ b/src/SOL002/VNFIndicator/VNFIndicator.yaml @@ -246,6 +246,19 @@ paths: in: header required: false type: string + post: + description: > + The POST method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" get: summary: Query multiple indicators related to a VNF instance. description: > -- GitLab From 67f1496fba1f9a5297778090ea3ce50bbdf5c6f8 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 18 Feb 2020 10:31:21 +0100 Subject: [PATCH 195/260] SOL002_209 unsupported method PUT Added --- src/SOL002/VNFIndicator/VNFIndicator.yaml | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/src/SOL002/VNFIndicator/VNFIndicator.yaml b/src/SOL002/VNFIndicator/VNFIndicator.yaml index 52a21959..fc2577f1 100644 --- a/src/SOL002/VNFIndicator/VNFIndicator.yaml +++ b/src/SOL002/VNFIndicator/VNFIndicator.yaml @@ -369,7 +369,19 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" + put: + description: > + The PUT method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Individual VNF indicator # ############################################################################### -- GitLab From 1aa656e298ef490573a19b8d72e1a0f8cf5cd30b Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 18 Feb 2020 10:32:04 +0100 Subject: [PATCH 196/260] SOL002_210 unsupported method PATCH Added --- src/SOL002/VNFIndicator/VNFIndicator.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFIndicator/VNFIndicator.yaml b/src/SOL002/VNFIndicator/VNFIndicator.yaml index fc2577f1..2f5cd662 100644 --- a/src/SOL002/VNFIndicator/VNFIndicator.yaml +++ b/src/SOL002/VNFIndicator/VNFIndicator.yaml @@ -377,6 +377,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + patch: + description: > + The PATCH method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From d34da5721626060e0458ae79dee9cab6cce12f03 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 18 Feb 2020 10:32:41 +0100 Subject: [PATCH 197/260] SOL002_211 unsupported method DELETE Added --- src/SOL002/VNFIndicator/VNFIndicator.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFIndicator/VNFIndicator.yaml b/src/SOL002/VNFIndicator/VNFIndicator.yaml index 2f5cd662..e9abb3ea 100644 --- a/src/SOL002/VNFIndicator/VNFIndicator.yaml +++ b/src/SOL002/VNFIndicator/VNFIndicator.yaml @@ -390,6 +390,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + delete: + description: > + The DELETE method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From 58cf8c8865481e3235804b3165dbd923c76b0100 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 18 Feb 2020 10:35:50 +0100 Subject: [PATCH 198/260] SOL002_213 unsupported method POST Added --- src/SOL002/VNFIndicator/VNFIndicator.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFIndicator/VNFIndicator.yaml b/src/SOL002/VNFIndicator/VNFIndicator.yaml index e9abb3ea..e066760f 100644 --- a/src/SOL002/VNFIndicator/VNFIndicator.yaml +++ b/src/SOL002/VNFIndicator/VNFIndicator.yaml @@ -444,6 +444,19 @@ paths: in: header required: false type: string + post: + description: > + The POST method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" get: summary: Read an inidividual VNF indicator related to a VNF instance. description: > -- GitLab From 976c5296c0cfe98d4966c7ccfa562c5fc3be46c3 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 18 Feb 2020 10:36:27 +0100 Subject: [PATCH 199/260] SOL002_214 unsupported method PUT Added --- src/SOL002/VNFIndicator/VNFIndicator.yaml | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/src/SOL002/VNFIndicator/VNFIndicator.yaml b/src/SOL002/VNFIndicator/VNFIndicator.yaml index e066760f..239018ea 100644 --- a/src/SOL002/VNFIndicator/VNFIndicator.yaml +++ b/src/SOL002/VNFIndicator/VNFIndicator.yaml @@ -508,7 +508,19 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" + put: + description: > + The PUT method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Subscriptions # ############################################################################### -- GitLab From 1a9584e9b5cf851fe010d463dba43410566cf6f7 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 18 Feb 2020 10:37:02 +0100 Subject: [PATCH 200/260] SOL002_215 unsupported method PATCH Added --- src/SOL002/VNFIndicator/VNFIndicator.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFIndicator/VNFIndicator.yaml b/src/SOL002/VNFIndicator/VNFIndicator.yaml index 239018ea..106cff1e 100644 --- a/src/SOL002/VNFIndicator/VNFIndicator.yaml +++ b/src/SOL002/VNFIndicator/VNFIndicator.yaml @@ -516,6 +516,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + patch: + description: > + The PATCH method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From 248aa69f5d206153641b27dd770ad7599417e9e9 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 18 Feb 2020 10:37:32 +0100 Subject: [PATCH 201/260] SOL002_216 unsupported method DELETE Added --- src/SOL002/VNFIndicator/VNFIndicator.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFIndicator/VNFIndicator.yaml b/src/SOL002/VNFIndicator/VNFIndicator.yaml index 106cff1e..da90d866 100644 --- a/src/SOL002/VNFIndicator/VNFIndicator.yaml +++ b/src/SOL002/VNFIndicator/VNFIndicator.yaml @@ -529,6 +529,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + delete: + description: > + The DELETE method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From 2b9b58f2fbdc7a011b49417b6f6fc5f6e975bfda Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 18 Feb 2020 10:41:05 +0100 Subject: [PATCH 202/260] SOL002_251 fix 303 See_other_response post operation --- src/SOL002/VNFIndicator/VNFIndicator.yaml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/SOL002/VNFIndicator/VNFIndicator.yaml b/src/SOL002/VNFIndicator/VNFIndicator.yaml index da90d866..a986a981 100644 --- a/src/SOL002/VNFIndicator/VNFIndicator.yaml +++ b/src/SOL002/VNFIndicator/VNFIndicator.yaml @@ -615,7 +615,8 @@ paths: The HTTP response shall include a "Location" HTTP header that contains the resource URI of the existing "Individual subscription" resource. The response body shall be empty. - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/303" + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/303" 400: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/400" 401: -- GitLab From c5b58c6fe32cc92718d6fecb58acb84916b19466 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 18 Feb 2020 10:42:53 +0100 Subject: [PATCH 203/260] SOL002_219 unsupported method PUT Added --- src/SOL002/VNFIndicator/VNFIndicator.yaml | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/src/SOL002/VNFIndicator/VNFIndicator.yaml b/src/SOL002/VNFIndicator/VNFIndicator.yaml index a986a981..64de4adc 100644 --- a/src/SOL002/VNFIndicator/VNFIndicator.yaml +++ b/src/SOL002/VNFIndicator/VNFIndicator.yaml @@ -754,7 +754,19 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" + put: + description: > + The PUT method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Individual Subscription # ############################################################################### -- GitLab From 4e18cb75a5a7a43bde88cfbb33835f35a83b7705 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 18 Feb 2020 10:43:31 +0100 Subject: [PATCH 204/260] SOL002_220 unsupported method PATCH Added --- src/SOL002/VNFIndicator/VNFIndicator.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFIndicator/VNFIndicator.yaml b/src/SOL002/VNFIndicator/VNFIndicator.yaml index 64de4adc..4d7b074d 100644 --- a/src/SOL002/VNFIndicator/VNFIndicator.yaml +++ b/src/SOL002/VNFIndicator/VNFIndicator.yaml @@ -762,6 +762,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + patch: + description: > + The PATCH method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From fad1cfcce4bf53667d4ab30e0761bb498534bc0f Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 18 Feb 2020 10:44:07 +0100 Subject: [PATCH 205/260] SOL002_221 unsupported method DELETE Added --- src/SOL002/VNFIndicator/VNFIndicator.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFIndicator/VNFIndicator.yaml b/src/SOL002/VNFIndicator/VNFIndicator.yaml index 4d7b074d..bacc6fb4 100644 --- a/src/SOL002/VNFIndicator/VNFIndicator.yaml +++ b/src/SOL002/VNFIndicator/VNFIndicator.yaml @@ -775,6 +775,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + delete: + description: > + The DELETE method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From 72035850f7edd07225929919a1221d597f05cb76 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 18 Feb 2020 10:46:42 +0100 Subject: [PATCH 206/260] SOL002_223 unsupported method POST Added --- src/SOL002/VNFIndicator/VNFIndicator.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFIndicator/VNFIndicator.yaml b/src/SOL002/VNFIndicator/VNFIndicator.yaml index bacc6fb4..6aa1b4cc 100644 --- a/src/SOL002/VNFIndicator/VNFIndicator.yaml +++ b/src/SOL002/VNFIndicator/VNFIndicator.yaml @@ -811,6 +811,19 @@ paths: in: header required: false type: string + post: + description: > + The POST method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" get: summary: Read an individual subscription. description: > -- GitLab From 5d52355171c6612402a80c769b8333395842ad03 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 18 Feb 2020 10:47:49 +0100 Subject: [PATCH 207/260] SOL002_224 unsupported method PATCH Added --- src/SOL002/VNFIndicator/VNFIndicator.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFIndicator/VNFIndicator.yaml b/src/SOL002/VNFIndicator/VNFIndicator.yaml index 6aa1b4cc..2a32d8b1 100644 --- a/src/SOL002/VNFIndicator/VNFIndicator.yaml +++ b/src/SOL002/VNFIndicator/VNFIndicator.yaml @@ -888,6 +888,19 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" + put: + description: > + The PUT method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" delete: summary: Delete a subscription description: > -- GitLab From 8d76b10734bd596140607f2d6493464fb49db0d3 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 18 Feb 2020 10:48:36 +0100 Subject: [PATCH 208/260] Revert "SOL002_224 unsupported method PATCH Added" This reverts commit 5d52355171c6612402a80c769b8333395842ad03 --- src/SOL002/VNFIndicator/VNFIndicator.yaml | 13 ------------- 1 file changed, 13 deletions(-) diff --git a/src/SOL002/VNFIndicator/VNFIndicator.yaml b/src/SOL002/VNFIndicator/VNFIndicator.yaml index 2a32d8b1..6aa1b4cc 100644 --- a/src/SOL002/VNFIndicator/VNFIndicator.yaml +++ b/src/SOL002/VNFIndicator/VNFIndicator.yaml @@ -888,19 +888,6 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" - put: - description: > - The PUT method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" delete: summary: Delete a subscription description: > -- GitLab From 963601a2c1164e41d695f1b4f13f260f18682b76 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 18 Feb 2020 11:06:11 +0100 Subject: [PATCH 209/260] SOL002_224 unsupported method PUT Added --- src/SOL002/VNFIndicator/VNFIndicator.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFIndicator/VNFIndicator.yaml b/src/SOL002/VNFIndicator/VNFIndicator.yaml index 6aa1b4cc..2a32d8b1 100644 --- a/src/SOL002/VNFIndicator/VNFIndicator.yaml +++ b/src/SOL002/VNFIndicator/VNFIndicator.yaml @@ -888,6 +888,19 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" + put: + description: > + The PUT method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" delete: summary: Delete a subscription description: > -- GitLab From 39f72fd9332718c0fa18eccee83294e1566d8286 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 18 Feb 2020 11:06:52 +0100 Subject: [PATCH 210/260] SOL002_225 unsupported method PATCH Added --- src/SOL002/VNFIndicator/VNFIndicator.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFIndicator/VNFIndicator.yaml b/src/SOL002/VNFIndicator/VNFIndicator.yaml index 2a32d8b1..6c0855f1 100644 --- a/src/SOL002/VNFIndicator/VNFIndicator.yaml +++ b/src/SOL002/VNFIndicator/VNFIndicator.yaml @@ -896,6 +896,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + patch: + description: > + The PATCH method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From 7b083bc4133dcafede23ff50e1a687e96f1a8098 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 18 Feb 2020 11:17:49 +0100 Subject: [PATCH 211/260] SOL002_226 unsupported method PUT Added to DataType in Request_body VnfIndicatorValueChangeNotification --- .../VNFIndicatorNotification.yaml | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-) diff --git a/src/SOL002/VNFIndicatorNotification/VNFIndicatorNotification.yaml b/src/SOL002/VNFIndicatorNotification/VNFIndicatorNotification.yaml index 15490369..1b870f51 100644 --- a/src/SOL002/VNFIndicatorNotification/VNFIndicatorNotification.yaml +++ b/src/SOL002/VNFIndicatorNotification/VNFIndicatorNotification.yaml @@ -134,4 +134,17 @@ paths: 500: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500" 503: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" \ No newline at end of file + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" + put: + description: > + The PUT method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" \ No newline at end of file -- GitLab From 22cd803c1ffc45da76eb7c0bdedcd930aea9434c Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 18 Feb 2020 11:19:07 +0100 Subject: [PATCH 212/260] SOL002_227 unsupported method PATCH Added to DataType in Request_body VnfIndicatorValueChangeNotification --- .../VNFIndicatorNotification.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFIndicatorNotification/VNFIndicatorNotification.yaml b/src/SOL002/VNFIndicatorNotification/VNFIndicatorNotification.yaml index 1b870f51..57431cbb 100644 --- a/src/SOL002/VNFIndicatorNotification/VNFIndicatorNotification.yaml +++ b/src/SOL002/VNFIndicatorNotification/VNFIndicatorNotification.yaml @@ -143,6 +143,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + patch: + description: > + The PATCH method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From 1a3ebe532319c09365573249e90182e5382f06d0 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 18 Feb 2020 11:20:21 +0100 Subject: [PATCH 213/260] SOL002_228 unsupported method DELETE Added to DataType in Request_body VnfIndicatorValueChangeNotification --- .../VNFIndicatorNotification.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFIndicatorNotification/VNFIndicatorNotification.yaml b/src/SOL002/VNFIndicatorNotification/VNFIndicatorNotification.yaml index 57431cbb..691b1358 100644 --- a/src/SOL002/VNFIndicatorNotification/VNFIndicatorNotification.yaml +++ b/src/SOL002/VNFIndicatorNotification/VNFIndicatorNotification.yaml @@ -156,6 +156,19 @@ paths: description: > 405 Method Not Allowed + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + delete: + description: > + The DELETE method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + This method is not supported. When this method is requested on this resource, the VNFM shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. -- GitLab From 153436b578b1f0ecccd8098b1afc6b1e16f30cc4 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 18 Feb 2020 12:17:44 +0100 Subject: [PATCH 214/260] SOL002_231 unsupported method POST Added --- src/SOL002/VNFConfiguration/VNFConfiguration.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFConfiguration/VNFConfiguration.yaml b/src/SOL002/VNFConfiguration/VNFConfiguration.yaml index 134144ce..d6918eb6 100644 --- a/src/SOL002/VNFConfiguration/VNFConfiguration.yaml +++ b/src/SOL002/VNFConfiguration/VNFConfiguration.yaml @@ -57,6 +57,19 @@ paths: in: header required: false type: string + post: + description: > + The POST method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" get: summary: Read VNF/VNFC configuration from VNF description: > -- GitLab From 1386a7830bd7ca587ee51c19aa3f0210f98b8d50 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 18 Feb 2020 12:19:09 +0100 Subject: [PATCH 215/260] SOL002_232 unsupported method PUT Added --- src/SOL002/VNFConfiguration/VNFConfiguration.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/SOL002/VNFConfiguration/VNFConfiguration.yaml b/src/SOL002/VNFConfiguration/VNFConfiguration.yaml index d6918eb6..19e63cd4 100644 --- a/src/SOL002/VNFConfiguration/VNFConfiguration.yaml +++ b/src/SOL002/VNFConfiguration/VNFConfiguration.yaml @@ -127,6 +127,19 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" + put: + description: > + The PUT method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" patch: summary: Modify VNF/VNFC configuration. description: This method sets or modifies a configuration resource. -- GitLab From 6145356b035e3789320b8b6e173fb7e10310e1f1 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 18 Feb 2020 12:21:47 +0100 Subject: [PATCH 216/260] SOL002_253 fix 412 Precondition_Failed_response patch operation --- src/SOL002/VNFConfiguration/VNFConfiguration.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/SOL002/VNFConfiguration/VNFConfiguration.yaml b/src/SOL002/VNFConfiguration/VNFConfiguration.yaml index 19e63cd4..f28c6215 100644 --- a/src/SOL002/VNFConfiguration/VNFConfiguration.yaml +++ b/src/SOL002/VNFConfiguration/VNFConfiguration.yaml @@ -195,8 +195,8 @@ paths: was modified by another entity. The response body should contain a ProblemDetails structure, in which the "detail" attribute should convey more information about the error. - - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/412" + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/412" 416: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" 422: -- GitLab From 0ed9893ab9c3da3ac88e4c715ef255c58047c6cb Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 18 Feb 2020 12:23:32 +0100 Subject: [PATCH 217/260] SOL002_233 unsupported method DELETE Added --- src/SOL002/VNFConfiguration/VNFConfiguration.yaml | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-) diff --git a/src/SOL002/VNFConfiguration/VNFConfiguration.yaml b/src/SOL002/VNFConfiguration/VNFConfiguration.yaml index f28c6215..97ef6d7a 100644 --- a/src/SOL002/VNFConfiguration/VNFConfiguration.yaml +++ b/src/SOL002/VNFConfiguration/VNFConfiguration.yaml @@ -208,4 +208,17 @@ paths: 503: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" \ No newline at end of file + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" + delete: + description: > + The DELETE method is not supported. + responses: + 405: + description: > + 405 Method Not Allowed + + This method is not supported. When this method is requested on + this resource, the VNFM shall return a "405 Method Not Allowed" + response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" \ No newline at end of file -- GitLab From 3298a3bf38fd6376909aea4f43343495eefe7929 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 25 Feb 2020 08:40:25 +0100 Subject: [PATCH 218/260] SOL002_14 DELETE description is Updated for triggering VnfIdentifierDeletionNotification for 204 response --- src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 6af01454..5eb9f474 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -556,6 +556,8 @@ paths: type: string maximum: 1 minimum: 1 + schema: + $ref: "../../definitions/SOL002SOL003VNFLifecycleManagement_def.yaml#/definitions/VnfIdentifierDeletionNotification" 400: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/400" 401: -- GitLab From aed4051247bb6a5e3d74f8dae7f809f013cd9bed Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 25 Feb 2020 12:09:33 +0100 Subject: [PATCH 219/260] SOL002_101 Filter description in table 5.4.18.3.2-1 updated --- .../VNFLifecycleManagement/VNFLifecycleManagement.yaml | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 5eb9f474..56251ad0 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -2997,6 +2997,15 @@ paths: in: query required: false type: string + - name: nextpage_opaque_marker + description: > + Marker to obtain the next page of a paged response. + Shall be supported by the VNFM if the VNFM supports + alternative 2 (paging) according to clause 5.4.2.1 + of ETSI GS NFV-SOL 013 for this resource. + in: query + required: false + type: string responses: 200: description: > -- GitLab From c4f03d78f9987fd838daa41e801a6d3ddd0bfa4e Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 25 Feb 2020 12:37:07 +0100 Subject: [PATCH 220/260] SOL002_115 VnfInstance datatype, table 5.5.2.2-1 updated --- .../definitions/SOL002VNFLifecycleManagement_def.yaml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/definitions/SOL002VNFLifecycleManagement_def.yaml b/src/SOL002/VNFLifecycleManagement/definitions/SOL002VNFLifecycleManagement_def.yaml index f278f185..ecde9ac3 100644 --- a/src/SOL002/VNFLifecycleManagement/definitions/SOL002VNFLifecycleManagement_def.yaml +++ b/src/SOL002/VNFLifecycleManagement/definitions/SOL002VNFLifecycleManagement_def.yaml @@ -134,6 +134,13 @@ definitions: type: array items: $ref: "../../../definitions/SOL002SOL003VNFLifecycleManagement_def.yaml#/definitions/ScaleInfo" + maxScaleLevels: + description: > + Maximum allowed scale levels of the VNF, one entry per aspect. + This attribute shall be present if the VNF supports scaling. + type: array + items: + $ref: "../../../definitions/SOL002SOL003VNFLifecycleManagement_def.yaml#/definitions/ScaleInfo" extCpInfo: description: > Information about the external CPs exposed by the VNF instance. -- GitLab From 52e93f69a580578cc6a8d66ad952d343a0c1aaa3 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 25 Feb 2020 12:44:44 +0100 Subject: [PATCH 221/260] SOL002_116 InstantiateVnfRequest datatype, table 5.5.2.4-1 update --- .../definitions/SOL002VNFLifecycleManagement_def.yaml | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/src/SOL002/VNFLifecycleManagement/definitions/SOL002VNFLifecycleManagement_def.yaml b/src/SOL002/VNFLifecycleManagement/definitions/SOL002VNFLifecycleManagement_def.yaml index ecde9ac3..733f90f6 100644 --- a/src/SOL002/VNFLifecycleManagement/definitions/SOL002VNFLifecycleManagement_def.yaml +++ b/src/SOL002/VNFLifecycleManagement/definitions/SOL002VNFLifecycleManagement_def.yaml @@ -349,6 +349,15 @@ definitions: as defined in clause 5.5.2.2. If an entry with the same key exists in the VnfInstance data structure, the VNFM shall replace its value with the value passed in the InstantiateVnfRequest data structure. $ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/KeyValuePairs" + vnfConfigurableProperties: + description: > + This parameter provides values for the VNF configurable + properties attribute in the "VnfInstance", as defined in + clause 5.5.2.2. If an entry with the same key exists in the + VnfInstance data structure, the VNFM shall replace its + value with the value passed in the InstantiateVnfRequest + data structure. + $ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/KeyValuePairs" ChangeVnfFlavourRequest: description: > -- GitLab From e6a9de74999ba89f60daacb5d230b1171764cf32 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 25 Feb 2020 13:04:30 +0100 Subject: [PATCH 222/260] SOL002_254 fix reference in vnfInfoModificationRequest --- .../definitions/SOL002VNFLifecycleManagement_def.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/SOL002/VNFLifecycleManagement/definitions/SOL002VNFLifecycleManagement_def.yaml b/src/SOL002/VNFLifecycleManagement/definitions/SOL002VNFLifecycleManagement_def.yaml index 733f90f6..8aa8d8e3 100644 --- a/src/SOL002/VNFLifecycleManagement/definitions/SOL002VNFLifecycleManagement_def.yaml +++ b/src/SOL002/VNFLifecycleManagement/definitions/SOL002VNFLifecycleManagement_def.yaml @@ -543,7 +543,7 @@ definitions: "instantiatedVnfInfo" attribute of "VnfInstance"." to be used as "newList" as defined below this table. type: array items: - $ref: "#/definitions/VnfcInfoModifications" + $ref: ""../../../definitions/SOL002SOL003VNFLifecycleManagement_def.yaml#/definitions/VnfcInfoModifications"" vnfcInfoModificationsDeleteIds: description: > List of identifiers entries to be deleted from the 'vnfcInfoModifications" attribute array -- GitLab From c5f62328ccca934851bfd8d4bbda9495dafc5aed Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 25 Feb 2020 13:19:39 +0100 Subject: [PATCH 223/260] SOL002_117 InstantiatevnfInfoModifications datatype, table 5.5.2.12a-1 update --- ...SOL002SOL003VNFLifecycleManagement_def.yaml | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml b/src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml index 8bef37c7..dd215f42 100644 --- a/src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml +++ b/src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml @@ -223,6 +223,24 @@ definitions: attribute from the VNFD in the VNF Package identified by the "vnfdId” attribute. $ref: "SOL002SOL003_def.yaml#/definitions/Version" + vnfcInfoModifications: + description: > + If present, this attribute signals modifications of certain + entries in the "vnfcInfo" attribute array in the + "instantiatedVnfInfo" attribute of "VnfInstance", as defined + in clause 5.5.2.12 + type: array + items: + $ref: "#/definitions/VnfcInfoModifications" + vnfcInfoModificationsDeleteIds: + description: > + If present, this attribute signals the deletion of certain + entries in the "vnfcInfo" attribute array in the + "instantiatedVnfInfo" attribute of "VnfInstance", as defined + in clause 5.5.2.12 + type: array + items: + $ref: "SOL002SOL003_def.yaml#/definitions/Identifier" VnfLcmOpOcc: description: > -- GitLab From 9c1f77f22a30824eb1acb5acf5446f385366a23c Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 25 Feb 2020 13:49:59 +0100 Subject: [PATCH 224/260] SOL002_122 VnfcInfo datatype, table 5.5.3.23-1 Added --- ...OL002SOL003VNFLifecycleManagement_def.yaml | 47 +++++++++++++++++++ 1 file changed, 47 insertions(+) diff --git a/src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml b/src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml index dd215f42..9883960f 100644 --- a/src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml +++ b/src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml @@ -1542,4 +1542,51 @@ definitions: vnfcConfigurableProperties: description: > Changes of the configurable properties of the VNFC instance. + $ref: "SOL002SOL003_def.yaml#/definitions/KeyValuePairs" + VnfcInfo: + description: > + This type represents the information about a VNFC instance that is part of a VNF instance. It shall comply with the + provisions defined in table 5.5.3.23-1. + type: object + required: + - id + - vduId + - vnfcResourceInfoId + - vnfcState + properties: + id: + description: > + Identifier of the VNFC instance. + $ref: "SOL002SOL003_def.yaml#/definitions/IdentifierInVnf" + vduId: + description: > + Reference to the applicable VDU information element in + the VNFD. + $ref: "SOL002SOL003_def.yaml#/definitions/IdentifierInVnf" + vnfcResourceInfoId: + description: > + Identifier of the VnfcResourceInfo instance representing + the virtualised resources used by this VNFC instance. + $ref: "SOL002SOL003_def.yaml#/definitions/IdentifierInVnf" + vnfcState: + description: > + Identifier of the VnfcResourceInfo instance representing + the virtualised resources used by this VNFC instance. + State of the VNFC instance. + Permitted values: + • STARTED: The VNFC instance is up and + running. + • STOPPED: The VNFC instance has been shut down + type: string + enum: + - STARTED + - STOPPED + $ref: "SOL002SOL003_def.yaml#/definitions/IdentifierInVnf" + vnfcConfigurableProperties: + description: > + Current values of the configurable properties of the + VNFC instance. + Configurable properties referred in this attribute are + declared in the VNFD. + This attribute can be modified with the PATCH method $ref: "SOL002SOL003_def.yaml#/definitions/KeyValuePairs" \ No newline at end of file -- GitLab From 3445d723124a4e79edc3e149163c057bf5cd78dd Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 25 Feb 2020 14:25:16 +0100 Subject: [PATCH 225/260] SOL002_150 Resource method PATCH Added --- .../VNFPerformanceManagement.yaml | 83 +++++++++++++++++++ 1 file changed, 83 insertions(+) diff --git a/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml b/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml index bc07f861..c89398b6 100644 --- a/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml +++ b/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml @@ -465,6 +465,89 @@ paths: response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. schema: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + patch: + description: > + This method allows to modify an "individual PM job" resource. + This method shall follow the provisions specified in the tables 6.4.3.3.4-1 and 6.4.3.3.4-2 for URI query parameters, + request and response data structures, and response codes. + parameters: + - name: PmJobModifications + description: Parameters for the PM job modification + required: true + in: body + schema: + $ref: "../../definitions/SOL002SOL003VNFPerformanceManagement_def.yaml#/definitions/PmJobModifications" + responses: + 200: + description: > + 200 OK + + Shall be returned when the request has been + processed successfully. + The response body shall contain a data structure of + type "PmJobModifications". + headers: + Content-Type: + description: The MIME type of the body of the response. + type: string + maximum: 1 + minimum: 1 + Version: + description: The used API version. + type: string + maximum: 1 + minimum: 1 + 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 + schema: + $ref: "../../definitions/SOL002SOL003VNFPerformanceManagement_def.yaml#/definitions/PmJobModifications" + 400: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/400" + 401: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/401" + 403: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/403" + 404: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/404" + 405: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + 406: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" + 409: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" + 412: + description: > + PRECONDITION FAILED + + Shall be returned upon the following error: + A precondition given in an HTTP request header is + not fulfilled. + Typically, this is due to an ETag mismatch, + indicating that the resource was modified by another + entity. + The response body should contain a ProblemDetails + structure, in which the "detail" attribute should + convey more information about the error. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/412" + 416: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" + 422: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/422" + 429: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/429" + 500: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500" + 503: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" + 504: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" delete: description: > This method terminates an individual PM job. -- GitLab From a790bb6a1ec9fb1d28295627415abd7e7ba5e956 Mon Sep 17 00:00:00 2001 From: Giacomo Bernini Date: Tue, 25 Feb 2020 15:54:00 +0100 Subject: [PATCH 226/260] Fixed bug #77 --- src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml | 2 +- src/definitions/SOL002SOL003VNFFaultManagement_def.yaml | 7 +++++++ 2 files changed, 8 insertions(+), 1 deletion(-) diff --git a/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml b/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml index 309e1ca2..e83112f1 100644 --- a/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml +++ b/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml @@ -527,7 +527,7 @@ paths: responses: 200: description: > - 200 OK + 204 No Content Shall be returned when the VNFM has received the proposed "escalated perceived severity" value successfully. The response body shall be empty. diff --git a/src/definitions/SOL002SOL003VNFFaultManagement_def.yaml b/src/definitions/SOL002SOL003VNFFaultManagement_def.yaml index 6573a27e..02f33bee 100644 --- a/src/definitions/SOL002SOL003VNFFaultManagement_def.yaml +++ b/src/definitions/SOL002SOL003VNFFaultManagement_def.yaml @@ -72,6 +72,7 @@ definitions: required: - id - managedObjectId + - vnfcInstanceIds - alarmRaisedTime - ackState - perceivedSeverity @@ -89,6 +90,12 @@ definitions: description: > Identifier of the affected VNF instance. $ref: "SOL002SOL003_def.yaml#/definitions/Identifier" + vnfcInstanceIds: + description: > + Identifiers of the affected VNFC instances. + type: array + items: + $ref: "SOL002SOL003_def.yaml#/definitions/IdentifierInVnf" rootCauseFaultyResource: description: > The virtualised resources that are causing the VNF fault. -- GitLab From 1efa257439ca26ddd904a1f360b20a8a6d8ff1d0 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 25 Feb 2020 15:54:40 +0100 Subject: [PATCH 227/260] SOL002_158 ThresholdCrossedNotification datatype, table 6.5.2.4-1 updated --- src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml b/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml index bdc9844b..9db26695 100644 --- a/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml +++ b/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml @@ -703,10 +703,10 @@ definitions: required: - id - notificationType - - subscriptionId - timeStamp - thresholdId - crossingDirection + - objectType - objectInstanceId - performanceMetric - performanceValue -- GitLab From 8dfa19cf8202d5d8cebc0f8bda0004b232edecc6 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 25 Feb 2020 16:00:58 +0100 Subject: [PATCH 228/260] SOL002_159 PerformanceInformationAvailableNotification datatype, table 6.5.2.5-1 Updated --- src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml b/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml index 9db26695..2d8c89d3 100644 --- a/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml +++ b/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml @@ -124,8 +124,8 @@ definitions: required: - id - notificationType - - subscriptionId - timeStamp + - objectType - objectInstanceId - _links properties: -- GitLab From 78b6adf29f65a0106b2b1235201199f1024f6eb7 Mon Sep 17 00:00:00 2001 From: Giacomo Bernini Date: Tue, 25 Feb 2020 16:03:57 +0100 Subject: [PATCH 229/260] Fixed bug #71 --- src/SOL002/VNFConfiguration/VNFConfiguration.yaml | 2 -- 1 file changed, 2 deletions(-) diff --git a/src/SOL002/VNFConfiguration/VNFConfiguration.yaml b/src/SOL002/VNFConfiguration/VNFConfiguration.yaml index 97ef6d7a..19dff4c7 100644 --- a/src/SOL002/VNFConfiguration/VNFConfiguration.yaml +++ b/src/SOL002/VNFConfiguration/VNFConfiguration.yaml @@ -115,8 +115,6 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" 406: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" - 416: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" 422: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/422" 429: -- GitLab From 3b1b412db3a6de4b6a56c12860aeacd205889373 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 25 Feb 2020 16:19:33 +0100 Subject: [PATCH 230/260] SOL002_161 PmJob datatype, table 6.5.2.7-1 updated --- src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml b/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml index 2d8c89d3..275e2e15 100644 --- a/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml +++ b/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml @@ -293,7 +293,8 @@ definitions: Type of the measured object. The applicable measured object type for a measurement is defined in clause 7.2 of ETSI GS NFV-IFA 027. - $ref: "SOL002SOL003_def.yaml#/definitions/Identifier" + type: + string objectInstanceIds: description: > Identifiers of the VNF instances for which performance information -- GitLab From 539aabdb326be07c653a909fca274a5e34152bbb Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 25 Feb 2020 16:26:16 +0100 Subject: [PATCH 231/260] SOL002_163 PerformanceReport datatype, table 6.5.2.10-1 updated --- src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml b/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml index 275e2e15..6c939ca6 100644 --- a/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml +++ b/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml @@ -254,7 +254,7 @@ definitions: type: object required: - timeStamp - - performanceValue + - value properties: timeStamp: description: > -- GitLab From c4ece2d101e1d39bb81fb8329143d922211c22ee Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 25 Feb 2020 16:31:37 +0100 Subject: [PATCH 232/260] SOL002_165 Threshold datatype, table 6.5.2.9-1 updated --- src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml | 1 + 1 file changed, 1 insertion(+) diff --git a/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml b/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml index 6c939ca6..62ea7ae2 100644 --- a/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml +++ b/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml @@ -613,6 +613,7 @@ definitions: Link to a resource representing the measured object instance for which performance information is collected. Shall be present if the measured object instance information is accessible as a resource. + $ref: "SOL002SOL003_def.yaml#/definitions/Link" ThresholdModifications: description: > -- GitLab From 16c328435389199f70170c7735deea6edfa46d59 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 25 Feb 2020 16:40:31 +0100 Subject: [PATCH 233/260] SOL002_184 Response body description in table 7.4.5.3.1-2 updated --- .../VNFFaultManagement.yaml | 19 ++++++++++++++++++- 1 file changed, 18 insertions(+), 1 deletion(-) diff --git a/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml b/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml index e83112f1..0fc53533 100644 --- a/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml +++ b/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml @@ -717,7 +717,24 @@ paths: 416: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" 422: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/422" + description: > + 422 UNPROCESSABLE ENTITY + + Shall be returned upon the following error: The content + type of the payload body is supported and the payload + body of a request contains syntactically correct data but + the data cannot be processed. + The general cause for this error and its handling is + specified in clause 6.4 of ETSI GS NFV-SOL 013 [6], + including rules for the presence of the response body. + Specifically in case of this resource, the response code + 422 shall also be returned if the VNFM has tested the + Notification endpoint as described in clause 7.4.7.3.2 + and the test has failed. + In this case, the "detail" attribute in the "ProblemDetails" + structure shall convey more information about the error + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/422" 429: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/429" 500: -- GitLab From 87c278ef02c176b3a1fbb3971676744b3f4e3606 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Wed, 26 Feb 2020 05:58:36 +0100 Subject: [PATCH 234/260] SOL002_255 fix 303 See other in post operation --- .../VNFPerformanceManagement/VNFPerformanceManagement.yaml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml b/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml index c89398b6..968fa20e 100644 --- a/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml +++ b/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml @@ -1291,7 +1291,8 @@ paths: The HTTP response shall include a "Location" HTTP header that contains the resource URI of the existing "Individual subscription" resource. The response body shall be empty. - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/303" + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/303" 400: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/400" 401: -- GitLab From 4c5ffbce7b687bd1a4e8cbde47f0885e145d9a5e Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Wed, 26 Feb 2020 06:06:21 +0100 Subject: [PATCH 235/260] SOL002_195 Alarm datatype, table 7.5.2.4-1 updated --- .../definitions/SOL002VNFFaultManagement_def.yaml | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/src/SOL002/VNFFaultManagement/definitions/SOL002VNFFaultManagement_def.yaml b/src/SOL002/VNFFaultManagement/definitions/SOL002VNFFaultManagement_def.yaml index 716f5924..e2b4c336 100644 --- a/src/SOL002/VNFFaultManagement/definitions/SOL002VNFFaultManagement_def.yaml +++ b/src/SOL002/VNFFaultManagement/definitions/SOL002VNFFaultManagement_def.yaml @@ -9,8 +9,6 @@ definitions: required: - id - managedObjectId - - vnfcInstanceIds - - rootCauseFaultyResource - alarmRaisedTime - ackState - perceivedSeverity @@ -53,6 +51,12 @@ definitions: Time stamp indicating when the alarm was cleared. It shall be present if the alarm has been cleared. $ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/DateTime" + alarmAcknowledgedTime: + description: > + Time stamp indicating when the alarm was + acknowledged. It shall be present if the alarm has + been acknowledged. + $ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/DateTime" ackState: description: > Acknowledgement state of the alarm. -- GitLab From a96b3ef5e94c1ee267f40023ef60c7b23e1eef4f Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Wed, 26 Feb 2020 06:14:17 +0100 Subject: [PATCH 236/260] Revert "SOL002_195 Alarm datatype, table 7.5.2.4-1 updated" This reverts commit 4c5ffbce7b687bd1a4e8cbde47f0885e145d9a5e --- .../definitions/SOL002VNFFaultManagement_def.yaml | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/src/SOL002/VNFFaultManagement/definitions/SOL002VNFFaultManagement_def.yaml b/src/SOL002/VNFFaultManagement/definitions/SOL002VNFFaultManagement_def.yaml index e2b4c336..716f5924 100644 --- a/src/SOL002/VNFFaultManagement/definitions/SOL002VNFFaultManagement_def.yaml +++ b/src/SOL002/VNFFaultManagement/definitions/SOL002VNFFaultManagement_def.yaml @@ -9,6 +9,8 @@ definitions: required: - id - managedObjectId + - vnfcInstanceIds + - rootCauseFaultyResource - alarmRaisedTime - ackState - perceivedSeverity @@ -51,12 +53,6 @@ definitions: Time stamp indicating when the alarm was cleared. It shall be present if the alarm has been cleared. $ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/DateTime" - alarmAcknowledgedTime: - description: > - Time stamp indicating when the alarm was - acknowledged. It shall be present if the alarm has - been acknowledged. - $ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/DateTime" ackState: description: > Acknowledgement state of the alarm. -- GitLab From 754703a5b5b973a5ff384b5fcd4f583275fafaaf Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Wed, 26 Feb 2020 06:19:31 +0100 Subject: [PATCH 237/260] SOL002_195 Alarm datatype, table 7.5.2.4-1 updated --- src/definitions/SOL002SOL003VNFFaultManagement_def.yaml | 1 - 1 file changed, 1 deletion(-) diff --git a/src/definitions/SOL002SOL003VNFFaultManagement_def.yaml b/src/definitions/SOL002SOL003VNFFaultManagement_def.yaml index 02f33bee..dddcf03a 100644 --- a/src/definitions/SOL002SOL003VNFFaultManagement_def.yaml +++ b/src/definitions/SOL002SOL003VNFFaultManagement_def.yaml @@ -72,7 +72,6 @@ definitions: required: - id - managedObjectId - - vnfcInstanceIds - alarmRaisedTime - ackState - perceivedSeverity -- GitLab From d2487e12858cb8123ff542477866a536bbd0cd7a Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Wed, 26 Feb 2020 06:23:10 +0100 Subject: [PATCH 238/260] SOL002_197 AlarmClearedNotification datatype, table 7.5.2.6-1 updated --- src/definitions/SOL002SOL003VNFFaultManagement_def.yaml | 1 + 1 file changed, 1 insertion(+) diff --git a/src/definitions/SOL002SOL003VNFFaultManagement_def.yaml b/src/definitions/SOL002SOL003VNFFaultManagement_def.yaml index dddcf03a..1a3ef012 100644 --- a/src/definitions/SOL002SOL003VNFFaultManagement_def.yaml +++ b/src/definitions/SOL002SOL003VNFFaultManagement_def.yaml @@ -283,6 +283,7 @@ definitions: alarmClearedTime: description: > The time stamp indicating when the alarm was cleared. + $ref: "SOL002SOL003_def.yaml#/definitions/DateTime" _links: description: > Links to resources related to this notification. -- GitLab From 21162cc463eb96a90f0ece5620ac37e11cfc0b37 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Wed, 26 Feb 2020 06:32:39 +0100 Subject: [PATCH 239/260] SOL002_167 PmNotificationFilter datatype, type removed --- ...002SOL003VNFPerformanceManagement_def.yaml | 24 ------------------- 1 file changed, 24 deletions(-) diff --git a/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml b/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml index 62ea7ae2..a5d00976 100644 --- a/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml +++ b/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml @@ -463,30 +463,6 @@ definitions: reporting up to the boundary. $ref: "SOL002SOL003_def.yaml#/definitions/DateTime" - PmNotificationsFilter: - description: > - This type represents a filter that can be used to subscribe for - notifications related to performance management events. - type: object - properties: - vnfInstanceSubscriptionFilter: - description: > - Filter criteria to select VNF instances about which to notify. - $ref: "SOL002SOL003_def.yaml#/definitions/VnfInstanceSubscriptionFilter" - notificationTypes: - description: > - Match particular notification types. - Permitted values: - * ThresholdCrossedNotification - * PerformanceInformationAvailableNotification - The permitted values of the "notificationTypes" attribute are - spelled exactly as the names of the notification types to facilitate - automated code generation systems. - type: string - enum: - - ThresholdCrossedNotification - - PerformanceInformationAvailableNotification - PmSubscription: description: > This type represents a subscription. -- GitLab From 6cb941486e7174121645cd01195abc5168d5940b Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Wed, 26 Feb 2020 06:52:35 +0100 Subject: [PATCH 240/260] SOL002_157 PmSubscription datatype, type removed --- ...002SOL003VNFPerformanceManagement_def.yaml | 37 ------------------- 1 file changed, 37 deletions(-) diff --git a/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml b/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml index a5d00976..37382886 100644 --- a/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml +++ b/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml @@ -463,43 +463,6 @@ definitions: reporting up to the boundary. $ref: "SOL002SOL003_def.yaml#/definitions/DateTime" - PmSubscription: - description: > - This type represents a subscription. - type: object - required: - - id - - callbackUri - - _links - properties: - id: - description: > - Identifier that identifies the subscription. - $ref: "SOL002SOL003_def.yaml#/definitions/Identifier" - filter: - description: > - Filter settings for this subscription, to define the subset of all - notifications this subscription relates to. A particular - notification is sent to the subscriber if the filter matches, or if - there is no filter. - $ref: "#/definitions/PmNotificationsFilter" - callbackUri: - description: > - The URI of the endpoint to send the notification to. - type: string - format: url - _links: - description: > - Links to resources related to this resource. - type: object - required: - - self - properties: - self: - description: > - URI of this resource. - $ref: "SOL002SOL003_def.yaml#/definitions/Link" - PmSubscriptionRequest: description: > This type represents a subscription request. -- GitLab From 57038f8ad1f34585c16f454a787ddea4b7aaf03a Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Wed, 26 Feb 2020 06:53:54 +0100 Subject: [PATCH 241/260] SOL002_156 PmSubscriptionRequest datatype, type removed --- ...002SOL003VNFPerformanceManagement_def.yaml | 26 ------------------- 1 file changed, 26 deletions(-) diff --git a/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml b/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml index 37382886..b31de24e 100644 --- a/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml +++ b/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml @@ -463,32 +463,6 @@ definitions: reporting up to the boundary. $ref: "SOL002SOL003_def.yaml#/definitions/DateTime" - PmSubscriptionRequest: - description: > - This type represents a subscription request. - type: object - required: - - callbackUri - properties: - filter: - description: > - Filter settings for this subscription, to define the subset of all - notifications this subscription relates to. A particular - notification is sent to the subscriber if the filter matches, or if - there is no filter. - $ref: "#/definitions/PmNotificationsFilter" - callbackUri: - description: > - The URI of the endpoint to send the notification to. - type: string - format: url - authentication: - description: > - Authentication parameters to configure the use of Authorization when sending notifications - corresponding 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: "SOL002SOL003_def.yaml#/definitions/SubscriptionAuthentication" - Threshold: description: > This type represents a threshold. -- GitLab From b040edc21cf0eb8b62ea6ce137f391e4bcccfbf2 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Wed, 26 Feb 2020 07:28:31 +0100 Subject: [PATCH 242/260] SOL002_152 Resource: Individual subscription, resource removed --- .../VNFPerformanceManagement.yaml | 156 ------------------ 1 file changed, 156 deletions(-) diff --git a/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml b/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml index 968fa20e..f98c5b2d 100644 --- a/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml +++ b/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml @@ -1436,161 +1436,5 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500" 503: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" - 504: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" - - ############################################################################### - # Individual subscription # - ############################################################################### - '/subscriptions/{subscriptionId}': - #SOL002 location: 6.4.8 - parameters: - - name: subscriptionId - description: > - This identifier can be retrieved from the resource referenced by the - "Location" HTTP header in the response to a POST request creating a - new subscription resource. It can also be retrieved from the "id" - attribute in the payload body of that response. - in: path - type: string - required: true - - name: Version - description: > - Version of the API requested to use when responding to this request. - 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 - get: - description: > - The client can use this method for reading an individual subscription - about Performance management notifications subscribed by the client. - parameters: - - name: Accept - description: > - Content-Types that are acceptable for the response. - Reference: IETF RFC 7231 - in: header - required: true - type: string - responses: - 200: - description: > - 200 OK - - Shall be returned when the subscription has been read successfully. - The response body shall contain a representation of the "Individual - subscription" resource. - headers: - Content-Type: - description: The MIME type of the body of the response. - type: string - maximum: 1 - minimum: 1 - Version: - description: The used API version. - type: string - maximum: 1 - minimum: 1 - 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 - schema: - $ref: "../../definitions/SOL002SOL003VNFPerformanceManagement_def.yaml#/definitions/PmSubscription" - 400: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/400" - 401: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/401" - 403: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/403" - 404: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/404" - 405: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - 406: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" - 416: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" - 422: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/422" - 429: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/429" - 500: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500" - 503: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" - 504: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" - delete: - description: > - This method terminates an individual subscription. - As the result of successfully executing this method, the "Individual subscription" - resource shall not exist any longer. This means that no notifications for that - subscription shall be sent to the formerly-subscribed API consumer. - NOTE: Due to race conditions, some notifications might still be received by the - formerly-subscribed API consumer for a certain time period after the deletion. - parameters: - - name: Accept - description: > - Content-Types that are acceptable for the response. - Reference: IETF RFC 7231 - in: header - required: true - type: string - responses: - 204: - description: > - 204 NO CONTENT - - Shall be returned when the "Individual subscription" resource has been - deleted successfully. - The response body shall be empty. - headers: - Version: - description: The used API version. - type: string - maximum: 1 - minimum: 1 - 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: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/400" - 401: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/401" - 403: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/403" - 404: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/404" - 405: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - 406: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" - 416: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" - 422: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/422" - 429: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/429" - 500: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500" - 503: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" \ No newline at end of file -- GitLab From 0b76b6af40a2f836afc0d2f8fcbf3030070c52cc Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Wed, 26 Feb 2020 07:29:53 +0100 Subject: [PATCH 243/260] SOL002_151 Resource: Subscriptions, resource removed --- .../VNFPerformanceManagement.yaml | 240 ------------------ 1 file changed, 240 deletions(-) diff --git a/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml b/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml index f98c5b2d..bf66bd95 100644 --- a/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml +++ b/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml @@ -1196,245 +1196,5 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500" 503: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" - 504: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" - - ############################################################################### - # Subscriptions # - ############################################################################### - '/subscriptions': - #SOL003 location: 6.4.7 - parameters: - - name: Version - description: > - Version of the API requested to use when responding to this request. - 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 - post: - description: > - The POST method creates a new subscription. - As the result of successfully executing this method, a new - "Individual subscription" resource as defined in clause 6.4.8 - shall have been created. This method shall not trigger any notification. - parameters: - - name: PmSubscriptionRequest - description: > - Details of the subscription to be created. - in: body - required: true - schema: - $ref: "../../definitions/SOL002SOL003VNFPerformanceManagement_def.yaml#/definitions/PmSubscriptionRequest" - - name: Accept - description: > - Content-Types that are acceptable for the response. - Reference: IETF RFC 7231 - in: header - required: true - 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: - 201: - description: > - 201 CREATED - - Shall be returned when the subscription was created successfully. - A representation of the created "Individual subscription" resource - shall be returned in the response body. - The HTTP response shall include a "Location" HTTP header that contains - the resource URI of the created "Individual subscription" resource. - headers: - Content-Type: - description: The MIME type of the body of the response. - type: string - maximum: 1 - minimum: 1 - Version: - description: The used API version. - type: string - maximum: 1 - minimum: 1 - Location: - description: The resource URI of the created VNF instance - type: string - format: url - 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 - schema: - $ref: "../../definitions/SOL002SOL003VNFPerformanceManagement_def.yaml#/definitions/PmSubscription" - 303: - description: > - 303 SEE OTHER - - Shall be returned when a subscription with the same callbackURI and - the same filter already exists and the policy of the VNFM is to not - create redundant subscriptions. - The HTTP response shall include a "Location" HTTP header that contains - the resource URI of the existing "Individual subscription" resource. - The response body shall be empty. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/303" - 400: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/400" - 401: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/401" - 403: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/403" - 404: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/404" - 405: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - 406: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" - 416: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" - 422: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/422" - 429: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/429" - 500: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500" - 503: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" - 504: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" - get: - description: > - The client can use this method to query the list of active - subscriptions to Performance management notifications subscribed by - the client. - parameters: - - name: Accept - description: > - Content-Types that are acceptable for the response. - Reference: IETF RFC 7231 - in: header - required: true - type: string - - name: filter - description: > - Attribute-based filtering expression according to clause 5.2 of ETSI GS NFV-SOL 013. - The VNFM shall support receiving this parameter as part of the URI query string. - The EM may supply this parameter. All attribute names that appear in the PmSubscription - and in data types referenced from it shall be supported by the VNFM in attribute-based filtering expression. - - EXAMPLE - objects - obj1: {"id":123, "weight":100, "parts":[{"id":1, "color":"red"}, {"id":2, "color":"green"}]} - obj2: {"id":456, "weight":500, "parts":[{"id":3, "color":"green"}, {"id":4, "color":"blue"}]} - - Request 1: - GET …/container - - Response 1: - [ - {"id":123, "weight":100, "parts":[{"id":1, "color":"red"}, {"id":2, "color":"green"}]}, - {"id":456, "weight":500, "parts":[{"id":3, "color":"green"}, {"id":4, "color":"blue"}]} - ] - - Request 2: - GET …/container?filter=(eq.weight,100) - - Response 2: - [ - {"id":123, "weight":100, "parts":[{"id":1, "color":"red"}, {"id":2, "color":"green"}]} - ] - #Request 2 in EXAMPLE from clause 4.3.2 probably wrong, since "," should be used after opOne (eq), "." is used - in: query - required: false - type: string - - name: nextpage_opaque_marker - description: > - Marker to obtain the next page of a paged response. - Shall be supported by the VNFM if the VNFM supports alternative 2 - (paging) according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 for this resource. - in: query - required: false - type: string - responses: - 200: - description: > - 200 OK - - Shall be returned when the list of subscriptions was queried successfully. - The response body shall contain in an array the representations - of all active subscriptions of the functional block that invokes the method, - i.e. zero or more representations of PM subscriptions as defined in clause 6.5.2.3. - If the "filter" URI parameter was supplied in the request, the data in the response - body shall have been transformed according to the rules specified in clause 5.2.2 - of ETSI GS NFV-SOL 013. - If the VNFM 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: - Content-Type: - description: The MIME type of the body of the response. - type: string - maximum: 1 - minimum: 1 - Version: - description: The used API version. - type: string - maximum: 1 - minimum: 1 - 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 - Link: - description: > - Reference to other resources. Used for paging in the present document, see clause 4.7.2.1. - type: string - maximum: 1 - minimum: 0 - schema: - type: array - items: - $ref: "../../definitions/SOL002SOL003VNFPerformanceManagement_def.yaml#/definitions/PmSubscription" - 400: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/400" - 401: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/401" - 403: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/403" - 404: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/404" - 405: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - 406: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" - 416: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" - 422: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/422" - 429: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/429" - 500: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500" - 503: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" \ No newline at end of file -- GitLab From 1017a00524ac9ff43c60674df4db9a70c389a9a7 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Wed, 26 Feb 2020 08:36:24 +0100 Subject: [PATCH 244/260] SOL002_256 fix 409 Conflict response in post operation --- src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 56251ad0..02d7e0ca 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -1188,7 +1188,7 @@ paths: or that another lifecycle management operation is ongoing. The response body shall contain a ProblemDetails structure, in which the "detail" attribute shall convey more information about the error. - schema + schema: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" 416: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" -- GitLab From e7fbdc2ea6ecfe0ac1558f2b96d02b07c43ed034 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Thu, 27 Feb 2020 08:59:42 +0100 Subject: [PATCH 245/260] Revert Unsupported Methods and Implemented SOL002_184 --- .../VNFConfiguration/VNFConfiguration.yaml | 41 +- .../VNFFaultManagement.yaml | 221 ----- .../VNFFaultManagementNotification.yaml | 119 +-- src/SOL002/VNFIndicator/VNFIndicator.yaml | 245 +---- .../VNFIndicatorNotification.yaml | 41 +- .../VNFLifecycleManagement.yaml | 872 ------------------ .../SOL002VNFLifecycleManagement_def.yaml | 2 +- .../VNFLifecycleManagementNotification.yaml | 133 +-- .../VNFPerformanceManagement.yaml | 258 ++---- .../VNFPerformanceManagementNotification.yaml | 80 +- 10 files changed, 99 insertions(+), 1913 deletions(-) diff --git a/src/SOL002/VNFConfiguration/VNFConfiguration.yaml b/src/SOL002/VNFConfiguration/VNFConfiguration.yaml index 19dff4c7..8ad36731 100644 --- a/src/SOL002/VNFConfiguration/VNFConfiguration.yaml +++ b/src/SOL002/VNFConfiguration/VNFConfiguration.yaml @@ -57,19 +57,6 @@ paths: in: header required: false type: string - post: - description: > - The POST method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" get: summary: Read VNF/VNFC configuration from VNF description: > @@ -125,19 +112,6 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" - put: - description: > - The PUT method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" patch: summary: Modify VNF/VNFC configuration. description: This method sets or modifies a configuration resource. @@ -206,17 +180,4 @@ paths: 503: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" - delete: - description: > - The DELETE method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" \ No newline at end of file + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" \ No newline at end of file diff --git a/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml b/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml index 0fc53533..6a2a250f 100644 --- a/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml +++ b/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml @@ -58,19 +58,6 @@ paths: in: header required: false type: string - post: - description: > - The POST method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" get: description: > The client can use this method to retrieve information about the alarm @@ -199,45 +186,6 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" - put: - description: > - The PUT method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - patch: - description: > - The PATCH method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - delete: - description: > - The DELETE method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Individual alarm # ############################################################################### @@ -268,19 +216,6 @@ paths: in: header required: false type: string - post: - description: > - The POST method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" get: description: > The client can use this method to read an individual alarm. @@ -353,19 +288,6 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" - put: - description: > - The PUT method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" patch: description: > This method modifies an individual alarm resource. @@ -468,19 +390,6 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" - delete: - description: > - The DELETE method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Escalate Perceived Severity task # ############################################################################### @@ -561,58 +470,6 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" - get: - description: > - The GET method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - put: - description: > - The PUT method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - patch: - description: > - The PATCH method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - delete: - description: > - The DELETE method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Subscriptions # ############################################################################### @@ -871,45 +728,6 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" - put: - description: > - The PUT method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - patch: - description: > - The PATCH method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - delete: - description: > - The DELETE method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Individual subscription # ############################################################################### @@ -939,19 +757,6 @@ paths: in: header required: false type: string - post: - description: > - The POST method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" get: description: > The client can use this method for reading an individual subscription @@ -1025,32 +830,6 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" - put: - description: > - The PUT method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - patch: - description: > - The PATCH method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" delete: description: > This method terminates an individual subscription. diff --git a/src/SOL002/VNFFaultManagementNotification/VNFFaultManagementNotification.yaml b/src/SOL002/VNFFaultManagementNotification/VNFFaultManagementNotification.yaml index 28267df6..dd9ba280 100644 --- a/src/SOL002/VNFFaultManagementNotification/VNFFaultManagementNotification.yaml +++ b/src/SOL002/VNFFaultManagementNotification/VNFFaultManagementNotification.yaml @@ -151,45 +151,6 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500" 503: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" - put: - description: > - The PUT method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - patch: - description: > - The PATCH method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - delete: - description: > - The DELETE method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Notification endpoint AlarmClearedNotification # ############################################################################### @@ -308,45 +269,6 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500" 503: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" - put: - description: > - The PUT method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - patch: - description: > - The PATCH method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - delete: - description: > - The DELETE method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Notification endpoint AlarmListRebuiltNotification # ############################################################################### @@ -464,43 +386,4 @@ paths: 500: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500" 503: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" - put: - description: > - The PUT method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - patch: - description: > - The PATCH method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - delete: - description: > - The DELETE method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" \ No newline at end of file + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" \ No newline at end of file diff --git a/src/SOL002/VNFIndicator/VNFIndicator.yaml b/src/SOL002/VNFIndicator/VNFIndicator.yaml index 6c0855f1..3e4aee72 100644 --- a/src/SOL002/VNFIndicator/VNFIndicator.yaml +++ b/src/SOL002/VNFIndicator/VNFIndicator.yaml @@ -57,19 +57,6 @@ paths: in: header required: false type: string - post: - description: > - The POST method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" get: summary: Query multiple indicators description: Get a list of indicators. Support of attribute based filtering via query parameters. @@ -178,45 +165,6 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" - put: - description: > - The PUT method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - patch: - description: > - The PATCH method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - delete: - description: > - The DELETE method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # VNF indicators related to a VNF instance # ############################################################################### @@ -246,19 +194,6 @@ paths: in: header required: false type: string - post: - description: > - The POST method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" get: summary: Query multiple indicators related to a VNF instance. description: > @@ -369,45 +304,6 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" - put: - description: > - The PUT method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - patch: - description: > - The PATCH method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - delete: - description: > - The DELETE method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Individual VNF indicator # ############################################################################### @@ -444,19 +340,6 @@ paths: in: header required: false type: string - post: - description: > - The POST method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" get: summary: Read an inidividual VNF indicator related to a VNF instance. description: > @@ -508,45 +391,6 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" - put: - description: > - The PUT method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - patch: - description: > - The PATCH method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - delete: - description: > - The DELETE method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Subscriptions # ############################################################################### @@ -632,7 +476,16 @@ paths: 416: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" 422: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/422" + description: > + 422 UNPROCESSABLE ENTITY + + Shall be returned upon the following error: The + content type of the payload body is supported and + the payload body of a request contains + syntactically correct data but the data cannot be + processed. + schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/422" 429: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/429" 500: @@ -754,45 +607,6 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" - put: - description: > - The PUT method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - patch: - description: > - The PATCH method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - delete: - description: > - The DELETE method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Individual Subscription # ############################################################################### @@ -811,19 +625,6 @@ paths: in: header required: false type: string - post: - description: > - The POST method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" get: summary: Read an individual subscription. description: > @@ -888,32 +689,6 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" - put: - description: > - The PUT method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - patch: - description: > - The PATCH method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" delete: summary: Delete a subscription description: > diff --git a/src/SOL002/VNFIndicatorNotification/VNFIndicatorNotification.yaml b/src/SOL002/VNFIndicatorNotification/VNFIndicatorNotification.yaml index 691b1358..15490369 100644 --- a/src/SOL002/VNFIndicatorNotification/VNFIndicatorNotification.yaml +++ b/src/SOL002/VNFIndicatorNotification/VNFIndicatorNotification.yaml @@ -134,43 +134,4 @@ paths: 500: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500" 503: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" - put: - description: > - The PUT method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - patch: - description: > - The PATCH method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - delete: - description: > - The DELETE method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" \ No newline at end of file + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" \ No newline at end of file diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 02d7e0ca..3eaa9679 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -289,45 +289,6 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" - put: - description: > - The PUT method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - patch: - description: > - The PATCH method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - delete: - description: > - The DELETE method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Individual VNF instance # ############################################################################### @@ -357,19 +318,6 @@ paths: in: header required: false type: string - post: - description: > - The POST method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" get: description: > Information about a VNF instance by reading an "Individual VNF instance". @@ -426,19 +374,6 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" - put: - description: > - The PUT method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" patch: #SOL003 location: 5.4.3.3.4 description: > @@ -592,7 +527,6 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" - ############################################################################### # Instantiate VNF task # ############################################################################### @@ -705,58 +639,6 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" - get: - description: > - The GET method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - put: - description: > - The PUT method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - patch: - description: > - The PATCH method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - delete: - description: > - The DELETE method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Scale VNF task # ############################################################################### @@ -871,58 +753,6 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" - get: - description: > - The GET method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - put: - description: > - The PUT method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - patch: - description: > - The PATCH method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - delete: - description: > - The DELETE method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Scale VNF to Level task # ############################################################################### @@ -1037,58 +867,6 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" - get: - description: > - The GET method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - put: - description: > - The PUT method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - patch: - description: > - The PATCH method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - delete: - description: > - The DELETE method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Change VNF Flavour task # ############################################################################### @@ -1202,58 +980,6 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" - get: - description: > - The GET method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - put: - description: > - The PUT method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - patch: - description: > - The PATCH method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - delete: - description: > - The DELETE method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Terminate VNF task # ############################################################################### @@ -1366,58 +1092,6 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" - get: - description: > - The GET method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - put: - description: > - The PUT method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - patch: - description: > - The PATCH method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - delete: - description: > - The DELETE method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Heal VNF task # ############################################################################### @@ -1530,58 +1204,6 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" - get: - description: > - The GET method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - put: - description: > - The PUT method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - patch: - description: > - The PATCH method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - delete: - description: > - The DELETE method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Operate VNF task # ############################################################################### @@ -1694,58 +1316,6 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" - get: - description: > - The GET method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - put: - description: > - The PUT method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - patch: - description: > - The PATCH method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - delete: - description: > - The DELETE method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Change external VNF connectivity task # ############################################################################### @@ -1859,58 +1429,6 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" - get: - description: > - The GET method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - put: - description: > - The PUT method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - patch: - description: > - The PATCH method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - delete: - description: > - The DELETE method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # VNF LCM operation occurrences # ############################################################################### @@ -1930,19 +1448,6 @@ paths: in: header required: false type: string - post: - description: > - The POST method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" get: description: > The client can use this method to query status information about @@ -2091,45 +1596,6 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" - put: - description: > - The PUT method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - patch: - description: > - The PATCH method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - delete: - description: > - The DELETE method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Individual VNF LCM operation occurrence # ############################################################################### @@ -2160,19 +1626,6 @@ paths: in: header required: false type: string - post: - description: > - The POST method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" get: description: > The client can use this method to retrieve status information about a @@ -2231,45 +1684,6 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" - put: - description: > - The PUT method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - patch: - description: > - The PATCH method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - delete: - description: > - The DELETE method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Retry operation task # ############################################################################### @@ -2364,58 +1778,6 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" - get: - description: > - The GET method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - put: - description: > - The PUT method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - patch: - description: > - The PATCH method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - delete: - description: > - The DELETE method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Rollback operation task # ############################################################################### @@ -2509,58 +1871,6 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" - get: - description: > - The GET method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - put: - description: > - The PUT method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - patch: - description: > - The PATCH method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - delete: - description: > - The DELETE method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Fail operation task # ############################################################################### @@ -2661,58 +1971,6 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" - get: - description: > - The GET method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - put: - description: > - The PUT method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - patch: - description: > - The PATCH method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - delete: - description: > - The DELETE method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Cancel operation task # ############################################################################### @@ -2808,58 +2066,6 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" - get: - description: > - The GET method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - put: - description: > - The PUT method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - patch: - description: > - The PATCH method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - delete: - description: > - The DELETE method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Subscriptions # ############################################################################### @@ -3060,45 +2266,6 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" - put: - description: > - The PUT method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - patch: - description: > - The PATCH method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - delete: - description: > - The DELETE method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Individual subscription # ############################################################################### @@ -3128,19 +2295,6 @@ paths: in: header required: false type: string - post: - description: > - The POST method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" get: description: > The GET method retrieves information about a subscription by reading @@ -3198,32 +2352,6 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" - put: - description: > - The PUT method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - patch: - description: > - The PATCH method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" delete: description: > The DELETE method terminates an individual subscription. diff --git a/src/SOL002/VNFLifecycleManagement/definitions/SOL002VNFLifecycleManagement_def.yaml b/src/SOL002/VNFLifecycleManagement/definitions/SOL002VNFLifecycleManagement_def.yaml index 8aa8d8e3..58ea2c3c 100644 --- a/src/SOL002/VNFLifecycleManagement/definitions/SOL002VNFLifecycleManagement_def.yaml +++ b/src/SOL002/VNFLifecycleManagement/definitions/SOL002VNFLifecycleManagement_def.yaml @@ -543,7 +543,7 @@ definitions: "instantiatedVnfInfo" attribute of "VnfInstance"." to be used as "newList" as defined below this table. type: array items: - $ref: ""../../../definitions/SOL002SOL003VNFLifecycleManagement_def.yaml#/definitions/VnfcInfoModifications"" + $ref: "../../../definitions/SOL002SOL003VNFLifecycleManagement_def.yaml#/definitions/VnfcInfoModifications" vnfcInfoModificationsDeleteIds: description: > List of identifiers entries to be deleted from the 'vnfcInfoModifications" attribute array diff --git a/src/SOL002/VNFLifecycleManagementNotification/VNFLifecycleManagementNotification.yaml b/src/SOL002/VNFLifecycleManagementNotification/VNFLifecycleManagementNotification.yaml index 3684dea6..7b87c2d8 100644 --- a/src/SOL002/VNFLifecycleManagementNotification/VNFLifecycleManagementNotification.yaml +++ b/src/SOL002/VNFLifecycleManagementNotification/VNFLifecycleManagementNotification.yaml @@ -55,7 +55,7 @@ paths: description: > Notify - The POST method delivers a notification from the server to the client. + The POST method delivers a notification from the API producer to an API consumer. parameters: - name: VnfLcmOperationOccurrenceNotification description: A notification about lifecycle changes triggered by a VNF LCM operation occurrence. @@ -168,47 +168,6 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500" 503: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" - put: - description: > - Notify - - The PUT method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - patch: - description: > - The PATCH method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - delete: - description: > - The DELETE method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Notification endpoint VnfIdentifierCreationNotification # ############################################################################### @@ -231,7 +190,7 @@ paths: description: > Notify - The POST method delivers a notification from the server to the client. + The POST method delivers a notification from the API producer to an API consumer. parameters: - name: VnfIdentifierCreationNotification description: > @@ -346,47 +305,6 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500" 503: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" - put: - description: > - Notify - - The PUT method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - patch: - description: > - The PATCH method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - delete: - description: > - The DELETE method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Notification endpoint VnfIdentifierDeletionNotification # ############################################################################### @@ -407,9 +325,7 @@ paths: type: string post: description: > - Notify - - The POST method delivers a notification from the server to the client. + The POST method delivers a notification from the API producer to an API consumer. parameters: - name: VnfIdentifierDeletionNotification description: > @@ -523,45 +439,4 @@ paths: 500: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500" 503: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" - put: - description: > - Notify - - The PUT method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - patch: - description: > - The PATCH method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - delete: - description: > - The DELETE method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" \ No newline at end of file + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" \ No newline at end of file diff --git a/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml b/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml index bf66bd95..88cb5973 100644 --- a/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml +++ b/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml @@ -306,45 +306,6 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" - put: - description: > - The PUT method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - patch: - description: > - The PATCH method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - delete: - description: > - The DELETE method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Individual PM job # ############################################################################### @@ -374,19 +335,6 @@ paths: in: header required: false type: string - post: - description: > - The POST method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" get: description: > The client can use this method for reading an individual PM job. @@ -452,19 +400,6 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" - put: - description: > - The PUT method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" patch: description: > This method allows to modify an "individual PM job" resource. @@ -525,7 +460,7 @@ paths: description: > PRECONDITION FAILED - Shall be returned upon the following error: + Shall be returned upon the following error A precondition given in an HTTP request header is not fulfilled. Typically, this is due to an ETag mismatch, @@ -635,19 +570,6 @@ paths: in: header required: false type: string - post: - description: > - The POST method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" get: description: > The client can use this method for reading an individual performance @@ -714,45 +636,6 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" - put: - description: > - The PUT method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - patch: - description: > - The PATCH method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - delete: - description: > - The DELETE method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Thresholds # ############################################################################### @@ -982,45 +865,6 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" - put: - description: > - The PUT method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - patch: - description: > - The PATCH method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - delete: - description: > - The DELETE method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Individual threshold # ############################################################################### @@ -1050,19 +894,6 @@ paths: in: header required: false type: string - post: - description: > - The POST method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" get: description: > The client can use this method for reading an individual threshold. @@ -1127,19 +958,90 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" - put: + patch: description: > - The PUT method is not supported. + This method allows to modify an "Individual threshold" resource. + This method shall follow the provisions specified in the tables 6.4.6.3.4-1 and 6.4.6.3.4-2 for URI query parameters, + request and response data structures, and response codes. + parameters: + - name: ThresholdModifications + description: Parameters for the threshold modification. + required: true + in: body + schema: + $ref: "../../definitions/SOL002SOL003VNFPerformanceManagement_def.yaml#/definitions/ThresholdModifications" responses: - 405: + 200: description: > - 405 Method Not Allowed + 200 OK - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. + Shall be returned when the request has been + processed successfully. + The response body shall contain a data structure of + type "ThresholdModifications". + headers: + Content-Type: + description: The MIME type of the body of the response. + type: string + maximum: 1 + minimum: 1 + Version: + description: The used API version. + type: string + maximum: 1 + minimum: 1 + 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 + schema: + $ref: "../../definitions/SOL002SOL003VNFPerformanceManagement_def.yaml#/definitions/ThresholdModifications" + 400: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/400" + 401: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/401" + 403: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/403" + 404: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/404" + 405: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + 406: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" + 409: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" + 412: + description: > + PRECONDITION FAILED + + Shall be returned upon the following error + A precondition given in an HTTP request header is + not fulfilled. + Typically, this is due to an ETag mismatch, + indicating that the resource was modified by + another entity. + The response body should contain a + ProblemDetails structure, in which the "detail" + attribute should convey more information about the + error. schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/412" + 416: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" + 422: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/422" + 429: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/429" + 500: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500" + 503: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" + 504: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" delete: description: > This method allows to delete a threshold. diff --git a/src/SOL002/VNFPerformanceManagementNotification/VNFPerformanceManagementNotification.yaml b/src/SOL002/VNFPerformanceManagementNotification/VNFPerformanceManagementNotification.yaml index 0a8e28ce..df5c0108 100644 --- a/src/SOL002/VNFPerformanceManagementNotification/VNFPerformanceManagementNotification.yaml +++ b/src/SOL002/VNFPerformanceManagementNotification/VNFPerformanceManagementNotification.yaml @@ -163,45 +163,6 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500" 503: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" - put: - description: > - The PUT method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - patch: - description: > - The PATCH method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - delete: - description: > - The DELETE method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" ############################################################################### # Notification endpoint ThresholdCrossedNotification # ############################################################################### @@ -331,43 +292,4 @@ paths: 500: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500" 503: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" - put: - description: > - The PUT method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - patch: - description: > - The PATCH method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" - delete: - description: > - The DELETE method is not supported. - responses: - 405: - description: > - 405 Method Not Allowed - - This method is not supported. When this method is requested on - this resource, the VNFM shall return a "405 Method Not Allowed" - response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [6]. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405" \ No newline at end of file + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" \ No newline at end of file -- GitLab From b069811b7635dfff810c299a31a33e17d0b38d95 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Thu, 27 Feb 2020 10:33:23 +0100 Subject: [PATCH 246/260] bug fix # SOL002_257 --- .../VNFConfiguration/VNFConfiguration.yaml | 20 ++-- src/SOL002/VNFIndicator/VNFIndicator.yaml | 95 ++++++++++++------- 2 files changed, 69 insertions(+), 46 deletions(-) diff --git a/src/SOL002/VNFConfiguration/VNFConfiguration.yaml b/src/SOL002/VNFConfiguration/VNFConfiguration.yaml index 8ad36731..80444a2a 100644 --- a/src/SOL002/VNFConfiguration/VNFConfiguration.yaml +++ b/src/SOL002/VNFConfiguration/VNFConfiguration.yaml @@ -158,17 +158,17 @@ paths: 406: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" 412: - description: > - 412 PRECONDITION FAILED + # description: > + # 412 PRECONDITION FAILED - Shall be returned upon the following error: A precondition given - in an HTTP request header is not fulfilled. - Typically, this is due to an ETag mismatch, indicating that the resource - was modified by another entity. The response body should contain a - ProblemDetails structure, in which the "detail" attribute should convey - more information about the error. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/412" + # Shall be returned upon the following error: A precondition given + # in an HTTP request header is not fulfilled. + # Typically, this is due to an ETag mismatch, indicating that the resource + # was modified by another entity. The response body should contain a + # ProblemDetails structure, in which the "detail" attribute should convey + # more information about the error. + # schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/412" 416: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" 422: diff --git a/src/SOL002/VNFIndicator/VNFIndicator.yaml b/src/SOL002/VNFIndicator/VNFIndicator.yaml index 3e4aee72..dd1f832a 100644 --- a/src/SOL002/VNFIndicator/VNFIndicator.yaml +++ b/src/SOL002/VNFIndicator/VNFIndicator.yaml @@ -395,20 +395,6 @@ paths: # Subscriptions # ############################################################################### /subscriptions: - parameters: - - name: Version - description: > - Version of the API requested to use when responding to this request. - 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 post: summary: Create a new subscription to VNF indicator change notifications description: > @@ -416,6 +402,15 @@ paths: As the result of successfully executing this method, a new "Individual subscription" resource as defined in clause 8.4.6 shall have been created. This method shall not trigger any notification. + Creation of two "Individual subscription" resources with the same callbackURI and the same filter can result in + performance degradation and will provide duplicates of notifications to the VNFM, and might make sense only in very + rare use cases. Consequently, the API producer may either allow creating a new "Individual subscription" resource if + another "Individual subscription" resource with the same filter and callbackUri already exists (in which case it shall + return the "201 Created" response code), or may decide to not create a duplicate "Individual subscription" resource (in + which case it shall return a "303 See Other" response code referencing the existing "Individual subscription" resource + with the same filter and callbackUri). + This method shall follow the provisions specified in the tables 8.4.5.3.1-1 and 8.4.5.3.1-2 for URI query parameters, + request and response data structures, and response codes parameters: - name: vnfIndicatorSubscriptionRequest in: body @@ -423,6 +418,33 @@ paths: required: true schema: $ref: '../../definitions/SOL002SOL003VNFIndicator_def.yaml#/definitions/VnfIndicatorSubscriptionRequest' + - name: Accept + description: > + Content-Types that are acceptable for the response. + Reference: IETF RFC 7231 + in: header + required: true + 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 + - 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: 201: description: > @@ -432,7 +454,9 @@ paths: The response body shall contain a representation of the created "Individual subscription" resource. schema: - $ref: '../../definitions/SOL002SOL003VNFIndicator_def.yaml#/definitions/VnfIndicatorSubscription' + type: array + items: + $ref: '../../definitions/SOL002SOL003VNFIndicator_def.yaml#/definitions/VnfIndicatorSubscription' headers: Location: description: > @@ -444,23 +468,31 @@ paths: type: string maximum: 1 minimum: 1 + 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 Version: description: The used API version. type: string maximum: 1 minimum: 1 303: - description: > - 303 SEE OTHER - - Shall be returned when a subscription with the same callbackURI and - the same filter already exists and the policy of the VNFM is to not - create redundant subscriptions. - The HTTP response shall include a "Location" HTTP header that contains - the resource URI of the existing "Individual subscription" resource. - The response body shall be empty. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/303" + # description: > + # 303 SEE OTHER + + # Shall be returned when a subscription with the same callbackURI and + # the same filter already exists and the policy of the VNFM is to not + # create redundant subscriptions. + # The HTTP response shall include a "Location" HTTP header that contains + # the resource URI of the existing "Individual subscription" resource. + # The response body shall be empty. + # schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/303" 400: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/400" 401: @@ -476,16 +508,7 @@ paths: 416: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" 422: - description: > - 422 UNPROCESSABLE ENTITY - - Shall be returned upon the following error: The - content type of the payload body is supported and - the payload body of a request contains - syntactically correct data but the data cannot be - processed. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/422" + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/422" 429: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/429" 500: -- GitLab From 543bbb2d6c73ba476022a5e1aad04d48c558372a Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Thu, 27 Feb 2020 10:55:03 +0100 Subject: [PATCH 247/260] Bug fix # SOL002_258 --- .../VNFFaultManagement.yaml | 94 +++++++++---------- .../VNFPerformanceManagement.yaml | 54 +++++------ 2 files changed, 74 insertions(+), 74 deletions(-) diff --git a/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml b/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml index 6a2a250f..13b78ecf 100644 --- a/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml +++ b/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml @@ -354,30 +354,30 @@ paths: 406: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" 409: - description: > - 409 CONFLICT + # description: > + # 409 CONFLICT - Shall be returned upon the following error: The operation cannot be executed - currently, due to a conflict with the state of the "Individual alarm" resource. - Typically, this is due to the fact that the alarm is already in the state that - is requested to be set (such as trying to acknowledge an already-acknowledged - alarm). - The response body shall contain a ProblemDetails structure, in which the - "detail" attribute shall convey more information about the error. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" + # Shall be returned upon the following error: The operation cannot be executed + # currently, due to a conflict with the state of the "Individual alarm" resource. + # Typically, this is due to the fact that the alarm is already in the state that + # is requested to be set (such as trying to acknowledge an already-acknowledged + # alarm). + # The response body shall contain a ProblemDetails structure, in which the + # "detail" attribute shall convey more information about the error. + # schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" 412: - description: > - 412 PRECONDITION FAILED + # description: > + # 412 PRECONDITION FAILED - ErrorShall be returned upon the following error: A precondition given in an - HTTP request header is not fulfilled. - Typically, this is due to an ETag mismatch, indicating that the resource was - modified by another entity. - The response body should contain a ProblemDetails structure, in which the - "detail" attribute should convey more information about the error. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/412" + # ErrorShall be returned upon the following error: A precondition given in an + # HTTP request header is not fulfilled. + # Typically, this is due to an ETag mismatch, indicating that the resource was + # modified by another entity. + # The response body should contain a ProblemDetails structure, in which the + # "detail" attribute should convey more information about the error. + # schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/412" 416: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" 422: @@ -549,16 +549,16 @@ paths: schema: $ref: "../../definitions/SOL002SOL003VNFFaultManagement_def.yaml#/definitions/FmSubscription" 303: - description: > - 303 SEE OTHER + # description: > + # 303 SEE OTHER - A subscription with the same callbackURI and the same filter already exists and the policy of - the VNFM is to not create redundant subscriptions. - The HTTP response shall include a "Location" HTTP header that contains the resource URI of the - existing subscription resource. - The response body shall be empty. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/303" + # A subscription with the same callbackURI and the same filter already exists and the policy of + # the VNFM is to not create redundant subscriptions. + # The HTTP response shall include a "Location" HTTP header that contains the resource URI of the + # existing subscription resource. + # The response body shall be empty. + # schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/303" 400: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/400" 401: @@ -574,24 +574,24 @@ paths: 416: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" 422: - description: > - 422 UNPROCESSABLE ENTITY + # description: > + # 422 UNPROCESSABLE ENTITY - Shall be returned upon the following error: The content - type of the payload body is supported and the payload - body of a request contains syntactically correct data but - the data cannot be processed. - The general cause for this error and its handling is - specified in clause 6.4 of ETSI GS NFV-SOL 013 [6], - including rules for the presence of the response body. - Specifically in case of this resource, the response code - 422 shall also be returned if the VNFM has tested the - Notification endpoint as described in clause 7.4.7.3.2 - and the test has failed. - In this case, the "detail" attribute in the "ProblemDetails" - structure shall convey more information about the error - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/422" + # Shall be returned upon the following error: The content + # type of the payload body is supported and the payload + # body of a request contains syntactically correct data but + # the data cannot be processed. + # The general cause for this error and its handling is + # specified in clause 6.4 of ETSI GS NFV-SOL 013 [6], + # including rules for the presence of the response body. + # Specifically in case of this resource, the response code + # 422 shall also be returned if the VNFM has tested the + # Notification endpoint as described in clause 7.4.7.3.2 + # and the test has failed. + # In this case, the "detail" attribute in the "ProblemDetails" + # structure shall convey more information about the error + # schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/422" 429: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/429" 500: diff --git a/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml b/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml index 88cb5973..7547f3a1 100644 --- a/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml +++ b/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml @@ -457,20 +457,20 @@ paths: 409: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" 412: - description: > - PRECONDITION FAILED + # description: > + # PRECONDITION FAILED - Shall be returned upon the following error - A precondition given in an HTTP request header is - not fulfilled. - Typically, this is due to an ETag mismatch, - indicating that the resource was modified by another - entity. - The response body should contain a ProblemDetails - structure, in which the "detail" attribute should - convey more information about the error. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/412" + # Shall be returned upon the following error + # A precondition given in an HTTP request header is + # not fulfilled. + # Typically, this is due to an ETag mismatch, + # indicating that the resource was modified by another + # entity. + # The response body should contain a ProblemDetails + # structure, in which the "detail" attribute should + # convey more information about the error. + # schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/412" 416: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" 422: @@ -1015,21 +1015,21 @@ paths: 409: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" 412: - description: > - PRECONDITION FAILED + # description: > + # PRECONDITION FAILED - Shall be returned upon the following error - A precondition given in an HTTP request header is - not fulfilled. - Typically, this is due to an ETag mismatch, - indicating that the resource was modified by - another entity. - The response body should contain a - ProblemDetails structure, in which the "detail" - attribute should convey more information about the - error. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/412" + # Shall be returned upon the following error + # A precondition given in an HTTP request header is + # not fulfilled. + # Typically, this is due to an ETag mismatch, + # indicating that the resource was modified by + # another entity. + # The response body should contain a + # ProblemDetails structure, in which the "detail" + # attribute should convey more information about the + # error. + # schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/412" 416: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" 422: -- GitLab From 18f4fe94a439e534de0a95b65585c53f8956f097 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Thu, 27 Feb 2020 11:30:16 +0100 Subject: [PATCH 248/260] Bug fix # SOL002_259 --- .../VNFLifecycleManagement.yaml | 272 +++++++++--------- 1 file changed, 136 insertions(+), 136 deletions(-) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 3eaa9679..96d30bd5 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -442,16 +442,16 @@ paths: 406: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" 409: - description: > - 409 CONFLICT + # description: > + # 409 CONFLICT - Error: The operation cannot be executed currently, due to a conflict with the state - of the "Individual VNF instance" resource. - Typically, this is due to the fact that another LCM operation is ongoing. - The response body shall contain a ProblemDetails structure, in which the "detail" - attribute should convey more information about the error. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" + # Error: The operation cannot be executed currently, due to a conflict with the state + # of the "Individual VNF instance" resource. + # Typically, this is due to the fact that another LCM operation is ongoing. + # The response body shall contain a ProblemDetails structure, in which the "detail" + # attribute should convey more information about the error. + # schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" 412: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/412" 416: @@ -506,15 +506,15 @@ paths: 406: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" 409: - description: > - 409 CONFLICT + # description: > + # 409 CONFLICT - Error: The operation cannot be executed currently, due to a conflict with the state of the resource. - Typically, this is due to the fact that the "Individual VNF instance" resource is in INSTANTIATED state. - The response body shall contain a ProblemDetails structure, in which the "detail" attribute shall - convey more information about the error. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" + # Error: The operation cannot be executed currently, due to a conflict with the state of the resource. + # Typically, this is due to the fact that the "Individual VNF instance" resource is in INSTANTIATED state. + # The response body shall contain a ProblemDetails structure, in which the "detail" attribute shall + # convey more information about the error. + # schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" 416: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" 422: @@ -618,15 +618,15 @@ paths: 406: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" 409: - description: > - 409 CONFLICT + # description: > + # 409 CONFLICT - Error: The operation cannot be executed currently, due to a conflict with the state of the resource. - Typically, this is due to the fact that the "Individual VNF instance" resource is in INSTANTIATED state. - The response body shall contain a ProblemDetails structure, in which the "detail" attribute shall - convey more information about the error. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" + # Error: The operation cannot be executed currently, due to a conflict with the state of the resource. + # Typically, this is due to the fact that the "Individual VNF instance" resource is in INSTANTIATED state. + # The response body shall contain a ProblemDetails structure, in which the "detail" attribute shall + # convey more information about the error. + # schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" 416: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" 422: @@ -731,16 +731,16 @@ paths: 406: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" 409: - description: > - 409 CONFLICT + # description: > + # 409 CONFLICT - Error: The operation cannot be executed currently, due to a conflict with the state of the resource. - Typically, this is due to the fact that the "Individual VNF instance" resource is in NOT_INSTANTIATED state, - or that another lifecycle management operation is ongoing. - The response body shall contain a ProblemDetails structure, in which the "detail" attribute shall - convey more information about the error. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" + # Error: The operation cannot be executed currently, due to a conflict with the state of the resource. + # Typically, this is due to the fact that the "Individual VNF instance" resource is in NOT_INSTANTIATED state, + # or that another lifecycle management operation is ongoing. + # The response body shall contain a ProblemDetails structure, in which the "detail" attribute shall + # convey more information about the error. + # schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" 416: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" 422: @@ -845,16 +845,16 @@ paths: 406: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" 409: - description: > - 409 CONFLICT + # description: > + # 409 CONFLICT - Error: The operation cannot be executed currently, due to a conflict with the state of the resource. - Typically, this is due to the fact that the "Individual VNF instance" resource is in NOT_INSTANTIATED state, - or that another lifecycle management operation is ongoing. - The response body shall contain a ProblemDetails structure, in which the "detail" attribute shall - convey more information about the error. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" + # Error: The operation cannot be executed currently, due to a conflict with the state of the resource. + # Typically, this is due to the fact that the "Individual VNF instance" resource is in NOT_INSTANTIATED state, + # or that another lifecycle management operation is ongoing. + # The response body shall contain a ProblemDetails structure, in which the "detail" attribute shall + # convey more information about the error. + # schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" 416: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" 422: @@ -958,16 +958,16 @@ paths: 406: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" 409: - description: > - 409 CONFLICT + # description: > + # 409 CONFLICT - Error: The operation cannot be executed currently, due to a conflict with the state of the resource. - Typically, this is due to the fact that the "Individual VNF instance" resource is in NOT_INSTANTIATED state, - or that another lifecycle management operation is ongoing. - The response body shall contain a ProblemDetails structure, in which the "detail" attribute shall - convey more information about the error. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" + # Error: The operation cannot be executed currently, due to a conflict with the state of the resource. + # Typically, this is due to the fact that the "Individual VNF instance" resource is in NOT_INSTANTIATED state, + # or that another lifecycle management operation is ongoing. + # The response body shall contain a ProblemDetails structure, in which the "detail" attribute shall + # convey more information about the error. + # schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" 416: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" 422: @@ -1070,16 +1070,16 @@ paths: 406: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" 409: - description: > - 409 CONFLICT + # description: > + # 409 CONFLICT - Error: The operation cannot be executed currently, due to a conflict with the state of the resource. - Typically, this is due to the fact that the "Individual VNF instance" resource is in NOT_INSTANTIATED state, - or that another lifecycle management operation is ongoing. - The response body shall contain a ProblemDetails structure, in which the "detail" attribute shall - convey more information about the error. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" + # Error: The operation cannot be executed currently, due to a conflict with the state of the resource. + # Typically, this is due to the fact that the "Individual VNF instance" resource is in NOT_INSTANTIATED state, + # or that another lifecycle management operation is ongoing. + # The response body shall contain a ProblemDetails structure, in which the "detail" attribute shall + # convey more information about the error. + # schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" 416: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" 422: @@ -1182,16 +1182,16 @@ paths: 406: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" 409: - description: > - 409 CONFLICT + # description: > + # 409 CONFLICT - Error: The operation cannot be executed currently, due to a conflict with the state of the resource. - Typically, this is due to the fact that the "Individual VNF instance" resource is in NOT_INSTANTIATED state, - or that another lifecycle management operation is ongoing. - The response body shall contain a ProblemDetails structure, in which the "detail" attribute shall - convey more information about the error. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" + # Error: The operation cannot be executed currently, due to a conflict with the state of the resource. + # Typically, this is due to the fact that the "Individual VNF instance" resource is in NOT_INSTANTIATED state, + # or that another lifecycle management operation is ongoing. + # The response body shall contain a ProblemDetails structure, in which the "detail" attribute shall + # convey more information about the error. + # schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" 416: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" 422: @@ -1294,16 +1294,16 @@ paths: 406: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" 409: - description: > - 409 CONFLICT + # description: > + # 409 CONFLICT - Error: The operation cannot be executed currently, due to a conflict with the state of the resource. - Typically, this is due to the fact that the VNF instance resource is in NOT_INSTANTIATED state, - or that another lifecycle management operation is ongoing. - The response body shall contain a ProblemDetails structure, in which the "detail" attribute shall - convey more information about the error. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" + # Error: The operation cannot be executed currently, due to a conflict with the state of the resource. + # Typically, this is due to the fact that the VNF instance resource is in NOT_INSTANTIATED state, + # or that another lifecycle management operation is ongoing. + # The response body shall contain a ProblemDetails structure, in which the "detail" attribute shall + # convey more information about the error. + # schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" 416: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" 422: @@ -1408,15 +1408,15 @@ paths: 406: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" 409: - description: > - 409 CONFLICT + # description: > + # 409 CONFLICT - Error: The operation cannot be executed currently, due to a conflict with the state of the resource. - Typically, this is due to the fact that another lifecycle management operation is ongoing. - The response body shall contain a ProblemDetails structure, in which the "detail" attribute shall - convey more information about the error. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" + # Error: The operation cannot be executed currently, due to a conflict with the state of the resource. + # Typically, this is due to the fact that another lifecycle management operation is ongoing. + # The response body shall contain a ProblemDetails structure, in which the "detail" attribute shall + # convey more information about the error. + # schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" 416: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" 422: @@ -1755,17 +1755,17 @@ paths: 406: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" 409: - description: > - 409 CONFLICT + # description: > + # 409 CONFLICT - Error: The operation cannot be executed currently, due to a conflict with the state of - the VNF LCM operation occurrence resource. - Typically, this is due to the fact that the VNF LCM operation occurrence is not in FAILED_TEMP state - or another error handling action is starting such as rollback or fail. - The response body shall contain a ProblemDetails structure, in which the "detail" attribute shall - convey more information about the error. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" + # Error: The operation cannot be executed currently, due to a conflict with the state of + # the VNF LCM operation occurrence resource. + # Typically, this is due to the fact that the VNF LCM operation occurrence is not in FAILED_TEMP state + # or another error handling action is starting such as rollback or fail. + # The response body shall contain a ProblemDetails structure, in which the "detail" attribute shall + # convey more information about the error. + # schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" 416: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" 422: @@ -1848,17 +1848,17 @@ paths: 406: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" 409: - description: > - 409 CONFLICT + # description: > + # 409 CONFLICT - Error: The operation cannot be executed currently, due to a conflict with the state of - the VNF LCM operation occurrence resource. - Typically, this is due to the fact that the VNF LCM operation occurrence is not in FAILED_TEMP state - or another error handling action is starting such as rollback or fail. - The response body shall contain a ProblemDetails structure, in which the "detail" attribute shall - convey more information about the error. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" + # Error: The operation cannot be executed currently, due to a conflict with the state of + # the VNF LCM operation occurrence resource. + # Typically, this is due to the fact that the VNF LCM operation occurrence is not in FAILED_TEMP state + # or another error handling action is starting such as rollback or fail. + # The response body shall contain a ProblemDetails structure, in which the "detail" attribute shall + # convey more information about the error. + # schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" 416: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" 422: @@ -1948,17 +1948,17 @@ paths: 406: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" 409: - description: > - 409 CONFLICT + # description: > + # 409 CONFLICT - Error: The operation cannot be executed currently, due to a conflict with the state of - the VNF LCM operation occurrence resource. - Typically, this is due to the fact that the VNF LCM operation occurrence is not in FAILED_TEMP state - or another error handling action is starting such as rollback or fail. - The response body shall contain a ProblemDetails structure, in which the "detail" attribute shall - convey more information about the error. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" + # Error: The operation cannot be executed currently, due to a conflict with the state of + # the VNF LCM operation occurrence resource. + # Typically, this is due to the fact that the VNF LCM operation occurrence is not in FAILED_TEMP state + # or another error handling action is starting such as rollback or fail. + # The response body shall contain a ProblemDetails structure, in which the "detail" attribute shall + # convey more information about the error. + # schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" 416: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" 422: @@ -2043,17 +2043,17 @@ paths: 406: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406" 409: - description: > - 409 CONFLICT + # description: > + # 409 CONFLICT - Error: The operation cannot be executed currently, due to a conflict with the state of - the VNF LCM operation occurrence resource. - Typically, this is due to the fact that the operation occurrence is not in STARTING, - PROCESSING or ROLLING_BACK state. - The response body shall contain a ProblemDetails structure, in which the "detail" attribute shall - convey more information about the error. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" + # Error: The operation cannot be executed currently, due to a conflict with the state of + # the VNF LCM operation occurrence resource. + # Typically, this is due to the fact that the operation occurrence is not in STARTING, + # PROCESSING or ROLLING_BACK state. + # The response body shall contain a ProblemDetails structure, in which the "detail" attribute shall + # convey more information about the error. + # schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409" 416: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/416" 422: @@ -2131,16 +2131,16 @@ paths: schema: $ref: "../../definitions/SOL002SOL003VNFLifecycleManagement_def.yaml#/definitions/LccnSubscription" 303: - description: > - 303 SEE OTHER + # description: > + # 303 SEE OTHER - A subscription with the same callbackURI and the same filter already exists and the policy of the VNFM - is to not create redundant subscriptions. - The HTTP response shall include a "Location" HTTP header that contains the resource URI of the existing - subscription resource. - The response body shall be empty. - schema: - $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/303" + # A subscription with the same callbackURI and the same filter already exists and the policy of the VNFM + # is to not create redundant subscriptions. + # The HTTP response shall include a "Location" HTTP header that contains the resource URI of the existing + # subscription resource. + # The response body shall be empty. + # schema: + $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/303" 400: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/400" 401: -- GitLab From 9e5759544658cc31f5cf70b83374ee93de3aa094 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Thu, 27 Feb 2020 13:14:17 +0100 Subject: [PATCH 249/260] SOL002_260 Updated --- .../VNFLifecycleManagementNotification.yaml | 17 +++++++++++------ 1 file changed, 11 insertions(+), 6 deletions(-) diff --git a/src/SOL002/VNFLifecycleManagementNotification/VNFLifecycleManagementNotification.yaml b/src/SOL002/VNFLifecycleManagementNotification/VNFLifecycleManagementNotification.yaml index 7b87c2d8..e93060e2 100644 --- a/src/SOL002/VNFLifecycleManagementNotification/VNFLifecycleManagementNotification.yaml +++ b/src/SOL002/VNFLifecycleManagementNotification/VNFLifecycleManagementNotification.yaml @@ -55,7 +55,8 @@ paths: description: > Notify - The POST method delivers a notification from the API producer to an API consumer. + 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: VnfLcmOperationOccurrenceNotification description: A notification about lifecycle changes triggered by a VNF LCM operation occurrence. @@ -118,7 +119,7 @@ paths: get: description: > The GET method allows the server to test the notification endpoint - that is provided by the client, e.g. during subscription. + that is provided by the API consumer, e.g. during subscription. parameters: - name: Authorization description: > @@ -190,7 +191,8 @@ paths: description: > Notify - The POST method delivers a notification from the API producer to an API consumer. + 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: VnfIdentifierCreationNotification description: > @@ -255,7 +257,7 @@ paths: get: description: > The GET method allows the server to test the notification endpoint - that is provided by the client, e.g. during subscription. + that is provided by the API consumer, e.g. during subscription. parameters: - name: Authorization description: > @@ -325,7 +327,10 @@ paths: type: string post: description: > - The POST method delivers a notification from the API producer to an API consumer. + Notify + + 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: VnfIdentifierDeletionNotification description: > @@ -390,7 +395,7 @@ paths: get: description: > The GET method allows the server to test the notification endpoint - that is provided by the client, e.g. during subscription. + that is provided by the API consumer, e.g. during subscription. parameters: - name: Authorization description: > -- GitLab From ae807e28be819a789973e0995037be3b7ce18c33 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Fri, 28 Feb 2020 06:57:17 +0100 Subject: [PATCH 250/260] SOL002_115&120 Updated --- src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml | 2 +- .../definitions/SOL002VNFLifecycleManagement_def.yaml | 1 + src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml | 4 ++-- 3 files changed, 4 insertions(+), 3 deletions(-) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 96d30bd5..8b0936a8 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -1596,7 +1596,7 @@ paths: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503" 504: $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504" - ############################################################################### + ############################################################################### # Individual VNF LCM operation occurrence # ############################################################################### '/vnf_lcm_op_occs/{vnfLcmOpOccId}': diff --git a/src/SOL002/VNFLifecycleManagement/definitions/SOL002VNFLifecycleManagement_def.yaml b/src/SOL002/VNFLifecycleManagement/definitions/SOL002VNFLifecycleManagement_def.yaml index 58ea2c3c..18e47b42 100644 --- a/src/SOL002/VNFLifecycleManagement/definitions/SOL002VNFLifecycleManagement_def.yaml +++ b/src/SOL002/VNFLifecycleManagement/definitions/SOL002VNFLifecycleManagement_def.yaml @@ -15,6 +15,7 @@ definitions: - vnfdVersion - vnfPkgInfoId - instantiationState + - _links properties: id: description: > diff --git a/src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml b/src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml index 9883960f..9a26b7f7 100644 --- a/src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml +++ b/src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml @@ -504,7 +504,7 @@ definitions: description: > URI of this resource. $ref: "SOL002SOL003_def.yaml#/definitions/Link" - + ExtVirtualLinkInfo: type: object required: @@ -915,7 +915,7 @@ definitions: the VIM. In case this attribute is present, IP addresses are bound to that subnet. - $ref: "SOL002SOL003_def.yaml#/definitions/IpAddress" + $ref: "SOL002SOL003_def.yaml#/definitions/IdentifierInVim" MonitoringParameter: type: object -- GitLab From 66c2b630a4444f9def9bfd226b264e6aa0bfcb82 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Fri, 28 Feb 2020 08:12:37 +0100 Subject: [PATCH 251/260] SOL002_161,163,261&262 Updated --- ...002SOL003VNFPerformanceManagement_def.yaml | 42 ++++++++++--------- 1 file changed, 22 insertions(+), 20 deletions(-) diff --git a/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml b/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml index b31de24e..f952509c 100644 --- a/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml +++ b/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml @@ -201,6 +201,8 @@ definitions: of collecting performance information as part of a PM job. The type shall comply with the provisions defined in table 6.5.2.10-1. type: object + required: + - entries properties: entries: description: > @@ -283,6 +285,7 @@ definitions: - objectInstanceIds - criteria - callbackUri + - _links properties: id: description: > @@ -331,7 +334,6 @@ definitions: required: - href - readyTime - - _links properties: href: description: > @@ -349,8 +351,11 @@ definitions: fileSize: description: > The size of the report file in bytes, if known. - type: integer - # TODO: How to express unsigned int? + type: integer + minimum: 0 + maximum: 1024 + # TODO: How to express unsigned int? + # Done using min and max params to set a range for positive int. _links: description: > Links for this resource. @@ -364,23 +369,14 @@ definitions: $ref: "SOL002SOL003_def.yaml#/definitions/Link" objects: description: > - Links for this resource. - type: object - required: - - self - properties: - self: - description: > - URI of this resource. - $ref: "SOL002SOL003_def.yaml#/definitions/Link" - objects: - description: > - Links to resources representing the measured object instances for which - performance information is collected. Shall be present if - the measured object instance information is accessible as a resource. - type: array - items: - $ref: "SOL002SOL003_def.yaml#/definitions/Link" + Links to resources representing the measure + object instances for which performance + information is collected. Shall be present if the + measured object instance information is + accessible as a resource. + type: array + items: + $ref: "SOL002SOL003_def.yaml#/definitions/Link" PmJobModifications: description: > @@ -442,7 +438,10 @@ definitions: collection periods within one reporting period are reported together. type: integer + minimum: 0 + maximum: 1024 # TODO: How to express unsigned int? + # Done using min and max params to set a range for positive int. reportingPeriod: description: > Specifies the periodicity at which the producer will report to the @@ -455,7 +454,10 @@ definitions: collection periods within one reporting period are reported together. type: integer + minimum: 0 + maximum: 1024 # TODO: How to express unsigned int? + # Done using min and max params to set a range for positive int. reportingBoundary: description: > Identifies a time boundary after which the reporting will stop. -- GitLab From 0ed6988a9321f4f7a72d0506328461ae8d6eab67 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Fri, 28 Feb 2020 09:00:21 +0100 Subject: [PATCH 252/260] SOL002_195 Updated --- .../definitions/SOL002VNFFaultManagement_def.yaml | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/src/SOL002/VNFFaultManagement/definitions/SOL002VNFFaultManagement_def.yaml b/src/SOL002/VNFFaultManagement/definitions/SOL002VNFFaultManagement_def.yaml index 716f5924..e2b4c336 100644 --- a/src/SOL002/VNFFaultManagement/definitions/SOL002VNFFaultManagement_def.yaml +++ b/src/SOL002/VNFFaultManagement/definitions/SOL002VNFFaultManagement_def.yaml @@ -9,8 +9,6 @@ definitions: required: - id - managedObjectId - - vnfcInstanceIds - - rootCauseFaultyResource - alarmRaisedTime - ackState - perceivedSeverity @@ -53,6 +51,12 @@ definitions: Time stamp indicating when the alarm was cleared. It shall be present if the alarm has been cleared. $ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/DateTime" + alarmAcknowledgedTime: + description: > + Time stamp indicating when the alarm was + acknowledged. It shall be present if the alarm has + been acknowledged. + $ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/DateTime" ackState: description: > Acknowledgement state of the alarm. -- GitLab From 860a3208166474214aa3ed3e3c9e1c985b6daf88 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Fri, 28 Feb 2020 09:18:04 +0100 Subject: [PATCH 253/260] SOL002_229 & 263 Updated --- src/definitions/SOL002SOL003VNFIndicator_def.yaml | 1 + .../SOL002SOL003VNFPerformanceManagement_def.yaml | 15 +++++++++++---- 2 files changed, 12 insertions(+), 4 deletions(-) diff --git a/src/definitions/SOL002SOL003VNFIndicator_def.yaml b/src/definitions/SOL002SOL003VNFIndicator_def.yaml index e1328e0d..36baa383 100644 --- a/src/definitions/SOL002SOL003VNFIndicator_def.yaml +++ b/src/definitions/SOL002SOL003VNFIndicator_def.yaml @@ -199,6 +199,7 @@ definitions: Links for this resource. type: object required: + - vnfInstance - subscription properties: vnfInstance: diff --git a/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml b/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml index f952509c..3ae56e89 100644 --- a/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml +++ b/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml @@ -589,8 +589,10 @@ definitions: description: > The threshold value. Shall be represented as a floating point number. - # TODO: This should be floating. - type: integer + # TODO: This should be floating. + # Done using Number type and floating formate + type: number + format: float hysteresis: description: > The hysteresis of the threshold. Shall be represented as a @@ -605,8 +607,13 @@ definitions: threshold, implementations should enforce a suitable minimum value for this attribute (e.g. override the value or reject the request). - # TODO: This should be floating. - type: integer + # TODO: This should be floating. + # Done using Number type and floating format. + # Range is for non-negative + type: number + minimum: 0 + maximum: 1024 + format: float ThresholdCrossedNotification: description: > -- GitLab From 38ca1789d43e555b8f0f2da5c49781fc0cdbec2b Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Fri, 28 Feb 2020 10:24:23 +0100 Subject: [PATCH 254/260] Bug fix --- .../SOL002SOL003VNFPerformanceManagement_def.yaml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml b/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml index 3ae56e89..9b6e1c47 100644 --- a/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml +++ b/src/definitions/SOL002SOL003VNFPerformanceManagement_def.yaml @@ -609,12 +609,12 @@ definitions: request). # TODO: This should be floating. # Done using Number type and floating format. - # Range is for non-negative type: number - minimum: 0 - maximum: 1024 + minimum: 0 + maximum: 1024 format: float + ThresholdCrossedNotification: description: > This type represents a notification that is sent when a threshold has -- GitLab From e536dd87f139d780f6ba449ab63bc81445d45394 Mon Sep 17 00:00:00 2001 From: Francesca Moscatelli Date: Tue, 3 Mar 2020 11:49:03 +0100 Subject: [PATCH 255/260] SOL002-SOL003: fix in API Versions endpoints --- src/SOL002/APIVersion/APIVersion.yaml | 10 +++++----- src/SOL002/VNFConfiguration/VNFConfiguration.yaml | 2 +- src/SOL002/VNFIndicator/VNFIndicator.yaml | 2 +- .../VNFLifecycleManagement.yaml | 2 +- .../VNFPerformanceManagement.yaml | 2 +- src/SOL003/APIVersion/APIVersion.yaml | 14 +++++++------- .../VNFFaultManagement/VNFFaultManagement.yaml | 2 +- src/SOL003/VNFIndicator/VNFIndicator.yaml | 2 +- .../VNFLifecycleManagement.yaml | 2 +- .../VNFLifecycleOperationGranting.yaml | 2 +- .../VNFPackageManagement/VNFPackageManagement.yaml | 2 +- ...ualisedResourcesQuotaAvailableNotification.yaml | 2 +- 12 files changed, 22 insertions(+), 22 deletions(-) diff --git a/src/SOL002/APIVersion/APIVersion.yaml b/src/SOL002/APIVersion/APIVersion.yaml index c2ff8bbc..8e76144a 100644 --- a/src/SOL002/APIVersion/APIVersion.yaml +++ b/src/SOL002/APIVersion/APIVersion.yaml @@ -34,17 +34,17 @@ paths: ############################################################################### # API Versions # ############################################################################### - '/vnfconfig/api-versions': + '/vnfconfig/api_versions': $ref: '../../endpoints/SOL002SOL003_endpoints.yaml#/endpoints/api-versions' - '/vnffm/api-versions': + '/vnffm/api_versions': $ref: '../../endpoints/SOL002SOL003_endpoints.yaml#/endpoints/api-versions' - '/vnfind/api-versions': + '/vnfind/api_versions': $ref: '../../endpoints/SOL002SOL003_endpoints.yaml#/endpoints/api-versions' - '/vnflcm/api-versions': + '/vnflcm/api_versions': $ref: '../../endpoints/SOL002SOL003_endpoints.yaml#/endpoints/api-versions' - '/vnfpm/api-versions': + '/vnfpm/api_versions': $ref: '../../endpoints/SOL002SOL003_endpoints.yaml#/endpoints/api-versions' \ No newline at end of file diff --git a/src/SOL002/VNFConfiguration/VNFConfiguration.yaml b/src/SOL002/VNFConfiguration/VNFConfiguration.yaml index 134144ce..2fd261f1 100644 --- a/src/SOL002/VNFConfiguration/VNFConfiguration.yaml +++ b/src/SOL002/VNFConfiguration/VNFConfiguration.yaml @@ -36,7 +36,7 @@ paths: ############################################################################### # API Versions # ############################################################################### - '/api-versions': + '/api_versions': $ref: '../../endpoints/SOL002SOL003_endpoints.yaml#/endpoints/api-versions' ############################################################################### diff --git a/src/SOL002/VNFIndicator/VNFIndicator.yaml b/src/SOL002/VNFIndicator/VNFIndicator.yaml index 83a0b779..f73925e3 100644 --- a/src/SOL002/VNFIndicator/VNFIndicator.yaml +++ b/src/SOL002/VNFIndicator/VNFIndicator.yaml @@ -36,7 +36,7 @@ paths: ############################################################################### # API Versions # ############################################################################### - '/api-versions': + '/api_versions': $ref: '../../endpoints/SOL002SOL003_endpoints.yaml#/endpoints/api-versions' ############################################################################### diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 86e663d9..366f3f66 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -36,7 +36,7 @@ paths: ############################################################################### # API Versions # ############################################################################### - '/api-versions': + '/api_versions': $ref: '../../endpoints/SOL002SOL003_endpoints.yaml#/endpoints/api-versions' ############################################################################### diff --git a/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml b/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml index 1a4c1780..95bca323 100644 --- a/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml +++ b/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml @@ -36,7 +36,7 @@ paths: ############################################################################### # API Versions # ############################################################################### - '/api-versions': + '/api_versions': $ref: '../../endpoints/SOL002SOL003_endpoints.yaml#/endpoints/api-versions' ############################################################################### diff --git a/src/SOL003/APIVersion/APIVersion.yaml b/src/SOL003/APIVersion/APIVersion.yaml index 1efc11ef..77aaf6e0 100644 --- a/src/SOL003/APIVersion/APIVersion.yaml +++ b/src/SOL003/APIVersion/APIVersion.yaml @@ -28,23 +28,23 @@ paths: ############################################################################### # API Versions # ############################################################################### - '/vrqan/api-versions': + '/vrqan/api_versions': $ref: '../../endpoints/SOL002SOL003_endpoints.yaml#/endpoints/api-versions' - '/vnffm/api-versions': + '/vnffm/api_versions': $ref: '../../endpoints/SOL002SOL003_endpoints.yaml#/endpoints/api-versions' - '/vnfind/api-versions': + '/vnfind/api_versions': $ref: '../../endpoints/SOL002SOL003_endpoints.yaml#/endpoints/api-versions' - '/vnflcm/api-versions': + '/vnflcm/api_versions': $ref: '../../endpoints/SOL002SOL003_endpoints.yaml#/endpoints/api-versions' - '/vnfpm/api-versions': + '/vnfpm/api_versions': $ref: '../../endpoints/SOL002SOL003_endpoints.yaml#/endpoints/api-versions' - '/grant/api-versions': + '/grant/api_versions': $ref: '../../endpoints/SOL002SOL003_endpoints.yaml#/endpoints/api-versions' - '/vnfpkgm/api-versions': + '/vnfpkgm/api_versions': $ref: '../../endpoints/SOL002SOL003_endpoints.yaml#/endpoints/api-versions' \ No newline at end of file diff --git a/src/SOL003/VNFFaultManagement/VNFFaultManagement.yaml b/src/SOL003/VNFFaultManagement/VNFFaultManagement.yaml index 503d84d7..62292e43 100644 --- a/src/SOL003/VNFFaultManagement/VNFFaultManagement.yaml +++ b/src/SOL003/VNFFaultManagement/VNFFaultManagement.yaml @@ -42,7 +42,7 @@ paths: ############################################################################### # API Versions # ############################################################################### - '/api-versions': + '/api_versions': $ref: '../../endpoints/SOL002SOL003_endpoints.yaml#/endpoints/api-versions' ############################################################################### diff --git a/src/SOL003/VNFIndicator/VNFIndicator.yaml b/src/SOL003/VNFIndicator/VNFIndicator.yaml index 6e1740b2..13e161d6 100644 --- a/src/SOL003/VNFIndicator/VNFIndicator.yaml +++ b/src/SOL003/VNFIndicator/VNFIndicator.yaml @@ -31,7 +31,7 @@ paths: ############################################################################### # API Versions # ############################################################################### - '/api-versions': + '/api_versions': $ref: '../../endpoints/SOL002SOL003_endpoints.yaml#/endpoints/api-versions' ############################################################################### diff --git a/src/SOL003/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL003/VNFLifecycleManagement/VNFLifecycleManagement.yaml index c1d007af..5c0768f1 100644 --- a/src/SOL003/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL003/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -42,7 +42,7 @@ paths: ############################################################################### # API Versions # ############################################################################### - '/api-versions': + '/api_versions': $ref: '../../endpoints/SOL002SOL003_endpoints.yaml#/endpoints/api-versions' ############################################################################### diff --git a/src/SOL003/VNFLifecycleOperationGranting/VNFLifecycleOperationGranting.yaml b/src/SOL003/VNFLifecycleOperationGranting/VNFLifecycleOperationGranting.yaml index 79d7f229..9b96ab20 100644 --- a/src/SOL003/VNFLifecycleOperationGranting/VNFLifecycleOperationGranting.yaml +++ b/src/SOL003/VNFLifecycleOperationGranting/VNFLifecycleOperationGranting.yaml @@ -42,7 +42,7 @@ paths: ############################################################################### # API Versions # ############################################################################### - '/api-versions': + '/api_versions': $ref: '../../endpoints/SOL002SOL003_endpoints.yaml#/endpoints/api-versions' ############################################################################### diff --git a/src/SOL003/VNFPackageManagement/VNFPackageManagement.yaml b/src/SOL003/VNFPackageManagement/VNFPackageManagement.yaml index 99cd9c19..2e4de3ac 100644 --- a/src/SOL003/VNFPackageManagement/VNFPackageManagement.yaml +++ b/src/SOL003/VNFPackageManagement/VNFPackageManagement.yaml @@ -42,7 +42,7 @@ paths: ############################################################################### # API Versions # ############################################################################### - '/api-versions': + '/api_versions': $ref: '../../endpoints/SOL002SOL003_endpoints.yaml#/endpoints/api-versions' ############################################################################### diff --git a/src/SOL003/VirtualisedResourcesQuotaAvailableNotification/VirtualisedResourcesQuotaAvailableNotification.yaml b/src/SOL003/VirtualisedResourcesQuotaAvailableNotification/VirtualisedResourcesQuotaAvailableNotification.yaml index cfa61fb3..457871e2 100644 --- a/src/SOL003/VirtualisedResourcesQuotaAvailableNotification/VirtualisedResourcesQuotaAvailableNotification.yaml +++ b/src/SOL003/VirtualisedResourcesQuotaAvailableNotification/VirtualisedResourcesQuotaAvailableNotification.yaml @@ -42,7 +42,7 @@ paths: ############################################################################### # API Versions # ############################################################################### - '/api-versions': + '/api_versions': $ref: '../../endpoints/SOL002SOL003_endpoints.yaml#/endpoints/api-versions' ############################################################################### -- GitLab From acdd8f4b45c9ced8963f273ec73a34768857f2b5 Mon Sep 17 00:00:00 2001 From: Ahmed Butt Date: Tue, 3 Mar 2020 12:27:35 +0100 Subject: [PATCH 256/260] Api versions updated --- src/SOL002/APIVersion/APIVersion.yaml | 4 ++-- src/SOL002/VNFConfiguration/VNFConfiguration.yaml | 4 ++-- src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml | 6 +++--- .../VNFFaultManagementNotification.yaml | 6 +++--- src/SOL002/VNFIndicator/VNFIndicator.yaml | 4 ++-- .../VNFIndicatorNotification/VNFIndicatorNotification.yaml | 6 +++--- .../VNFLifecycleManagement/VNFLifecycleManagement.yaml | 4 ++-- .../VNFLifecycleManagementNotification.yaml | 6 +++--- .../VNFPerformanceManagement/VNFPerformanceManagement.yaml | 4 ++-- .../VNFPerformanceManagementNotification.yaml | 6 +++--- 10 files changed, 25 insertions(+), 25 deletions(-) diff --git a/src/SOL002/APIVersion/APIVersion.yaml b/src/SOL002/APIVersion/APIVersion.yaml index 8e76144a..85bd3471 100644 --- a/src/SOL002/APIVersion/APIVersion.yaml +++ b/src/SOL002/APIVersion/APIVersion.yaml @@ -17,8 +17,8 @@ info: name: NFV-SOL WG externalDocs: - description: ETSI GS NFV-SOL 002 V2.5.1 - url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/002/02.05.01_60/gs_nfv-sol002v020501p.pdf + description: ETSI GS NFV-SOL 002 V2.7.1 + url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/002/02.07.01_60/gs_nfv-sol002v020701p.pdf schemes: - http diff --git a/src/SOL002/VNFConfiguration/VNFConfiguration.yaml b/src/SOL002/VNFConfiguration/VNFConfiguration.yaml index 99891d36..b70febcf 100644 --- a/src/SOL002/VNFConfiguration/VNFConfiguration.yaml +++ b/src/SOL002/VNFConfiguration/VNFConfiguration.yaml @@ -17,8 +17,8 @@ info: name: NFV-SOL WG externalDocs: - description: ETSI GS NFV-SOL 002 V2.6.1 - url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/002/02.06.01_60/gs_nfv-sol002v020601p.pdf + description: ETSI GS NFV-SOL 002 V2.7.1 + url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/002/02.07.01_60/gs_nfv-sol002v020701p.pdf basePath: /vnfconfig/v1 diff --git a/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml b/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml index 13b78ecf..0b7df075 100644 --- a/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml +++ b/src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml @@ -17,8 +17,8 @@ info: name: NFV-SOL WG externalDocs: - description: ETSI GS NFV-SOL 002 V2.6.1 - url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/002/02.06.01_60/gs_nfv-sol002v020601p.pdf + description: ETSI GS NFV-SOL 002 V2.7.1 + url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/002/02.07.01_60/gs_nfv-sol002v020701p.pdf basePath: /vnffm/v1 @@ -36,7 +36,7 @@ paths: ############################################################################### # API Versions # ############################################################################### - '/api-versions': + '/api_versions': $ref: '../../endpoints/SOL002SOL003_endpoints.yaml#/endpoints/api-versions' ############################################################################### diff --git a/src/SOL002/VNFFaultManagementNotification/VNFFaultManagementNotification.yaml b/src/SOL002/VNFFaultManagementNotification/VNFFaultManagementNotification.yaml index dd9ba280..061f08c2 100644 --- a/src/SOL002/VNFFaultManagementNotification/VNFFaultManagementNotification.yaml +++ b/src/SOL002/VNFFaultManagementNotification/VNFFaultManagementNotification.yaml @@ -1,7 +1,7 @@ swagger: "2.0" info: - version: "1.2.0-impl:etsi.org:ETSI_NFV_OpenAPI:1" + version: "1.3.0-impl:etsi.org:ETSI_NFV_OpenAPI:1" title: SOL002 - VNF Fault Management Notification interface description: > SOL002 - VNF Fault Management Notification interface @@ -17,8 +17,8 @@ info: name: NFV-SOL WG externalDocs: - description: ETSI GS NFV-SOL 002 V2.6.1 - url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/002/02.06.01_60/gs_nfv-sol002v020601p.pdf + description: ETSI GS NFV-SOL 002 V2.7.1 + url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/002/02.07.01_60/gs_nfv-sol002v020701p.pdf basePath: /callback/v1 diff --git a/src/SOL002/VNFIndicator/VNFIndicator.yaml b/src/SOL002/VNFIndicator/VNFIndicator.yaml index 48dc0c44..cb5532d7 100644 --- a/src/SOL002/VNFIndicator/VNFIndicator.yaml +++ b/src/SOL002/VNFIndicator/VNFIndicator.yaml @@ -17,8 +17,8 @@ info: name: NFV-SOL WG externalDocs: - description: ETSI GS NFV-SOL 002 V2.6.1 - url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/002/02.06.01_60/gs_nfv-sol002v020601p.pdf + description: ETSI GS NFV-SOL 002 V2.7.1 + url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/002/02.07.01_60/gs_nfv-sol002v020701p.pdf basePath: /vnfind/v1 diff --git a/src/SOL002/VNFIndicatorNotification/VNFIndicatorNotification.yaml b/src/SOL002/VNFIndicatorNotification/VNFIndicatorNotification.yaml index 15490369..3bc5145b 100644 --- a/src/SOL002/VNFIndicatorNotification/VNFIndicatorNotification.yaml +++ b/src/SOL002/VNFIndicatorNotification/VNFIndicatorNotification.yaml @@ -1,7 +1,7 @@ swagger: "2.0" info: - version: "1.2.0-impl:etsi.org:ETSI_NFV_OpenAPI:1" + version: "1.2.1-impl:etsi.org:ETSI_NFV_OpenAPI:1" title: SOL002 - VNF Indicator Notification Endpoint interface description: > SOL002 - VNF Indicator Notification Endpoint interface @@ -17,8 +17,8 @@ info: name: NFV-SOL WG externalDocs: - description: ETSI GS NFV-SOL 002 V2.6.1 - url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/002/02.06.01_60/gs_nfv-sol002v020601p.pdf + description: ETSI GS NFV-SOL 002 V2.7.1 + url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/002/02.07.01_60/gs_nfv-sol002v020701p.pdf schemes: - http diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index b166efb9..65a81e7e 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -17,8 +17,8 @@ info: name: NFV-SOL WG externalDocs: - description: ETSI GS NFV-SOL 002 V2.6.1 - url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/002/02.06.01_60/gs_nfv-sol002v020601p.pdf + description: ETSI GS NFV-SOL 002 V2.7.1 + url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/002/02.07.01_60/gs_nfv-sol002v020701p.pdf basePath: /vnflcm/v1 diff --git a/src/SOL002/VNFLifecycleManagementNotification/VNFLifecycleManagementNotification.yaml b/src/SOL002/VNFLifecycleManagementNotification/VNFLifecycleManagementNotification.yaml index e93060e2..f3c25abf 100644 --- a/src/SOL002/VNFLifecycleManagementNotification/VNFLifecycleManagementNotification.yaml +++ b/src/SOL002/VNFLifecycleManagementNotification/VNFLifecycleManagementNotification.yaml @@ -1,7 +1,7 @@ swagger: "2.0" info: - version: "1.3.0-impl:etsi.org:ETSI_NFV_OpenAPI:1" + version: "1.4.0-impl:etsi.org:ETSI_NFV_OpenAPI:1" title: SOL002 - VNF Lifecycle Management Notification interface description: > SOL002 - VNF Lifecycle Management Notification interface @@ -17,8 +17,8 @@ info: name: NFV-SOL WG externalDocs: - description: ETSI GS NFV-SOL 002 V2.6.1 - url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/002/02.06.01_60/gs_nfv-sol002v020601p.pdf + description: ETSI GS NFV-SOL 002 V2.7.1 + url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/002/02.07.01_60/gs_nfv-sol002v020701p.pdf basePath: /callback/v1 diff --git a/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml b/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml index 8f9bc8ac..143e76e2 100644 --- a/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml +++ b/src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml @@ -17,8 +17,8 @@ info: name: NFV-SOL WG externalDocs: - description: ETSI GS NFV-SOL 002 V2.6.1 - url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/002/02.06.01_60/gs_nfv-sol002v020601p.pdf + description: ETSI GS NFV-SOL 002 V2.7.1 + url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/002/02.07.01_60/gs_nfv-sol002v020701p.pdf basePath: /vnfpm/v2 diff --git a/src/SOL002/VNFPerformanceManagementNotification/VNFPerformanceManagementNotification.yaml b/src/SOL002/VNFPerformanceManagementNotification/VNFPerformanceManagementNotification.yaml index df5c0108..030a04b3 100644 --- a/src/SOL002/VNFPerformanceManagementNotification/VNFPerformanceManagementNotification.yaml +++ b/src/SOL002/VNFPerformanceManagementNotification/VNFPerformanceManagementNotification.yaml @@ -1,7 +1,7 @@ swagger: "2.0" info: - version: "1.2.0-impl:etsi.org:ETSI_NFV_OpenAPI:1" + version: "2.0.0-impl:etsi.org:ETSI_NFV_OpenAPI:1" title: SOL002 - VNF Performance Management Notification interface description: > SOL002 - VNF Performance Management Notification interface @@ -17,8 +17,8 @@ info: name: NFV-SOL WG externalDocs: - description: ETSI GS NFV-SOL 002 V2.6.1 - url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/002/02.06.01_60/gs_nfv-sol002v020601p.pdf + description: ETSI GS NFV-SOL 002 V2.7.1 + url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/002/02.07.01_60/gs_nfv-sol002v020701p.pdf basePath: /callback/v1 -- GitLab From 4a8fa02872ccf5926be5ce0b16416d19a66a299f Mon Sep 17 00:00:00 2001 From: Giacomo Bernini Date: Tue, 10 Mar 2020 14:30:09 +0100 Subject: [PATCH 257/260] fix bug#76 --- .../VNFLifecycleManagement/VNFLifecycleManagement.yaml | 9 +++++++++ .../definitions/SOL002VNFLifecycleManagement_def.yaml | 3 ++- .../SOL002SOL003VNFLifecycleManagement_def.yaml | 1 + 3 files changed, 12 insertions(+), 1 deletion(-) diff --git a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml index 65a81e7e..51bbbc5c 100644 --- a/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml +++ b/src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml @@ -2001,6 +2001,15 @@ paths: in: header required: false type: string + - name: cancelMode + description: > + The POST request to this resource shall include a CancelMode + structure in the payload body to choose between "graceful" and + "forceful" cancellation. + in: body + required: true + schema: + $ref: "../../definitions/SOL002SOL003VNFLifecycleManagement_def.yaml#/definitions/CancelMode" post: description: > The POST method initiates cancelling an ongoing VNF lifecycle diff --git a/src/SOL002/VNFLifecycleManagement/definitions/SOL002VNFLifecycleManagement_def.yaml b/src/SOL002/VNFLifecycleManagement/definitions/SOL002VNFLifecycleManagement_def.yaml index 18e47b42..61385094 100644 --- a/src/SOL002/VNFLifecycleManagement/definitions/SOL002VNFLifecycleManagement_def.yaml +++ b/src/SOL002/VNFLifecycleManagement/definitions/SOL002VNFLifecycleManagement_def.yaml @@ -60,7 +60,7 @@ definitions: description: > Identifies the version of the VNFD. The value is copied from the VNFD. $ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/Version" - vnfPkgInfoId: + vnfPkgId: description: > Identifier of information held by the NFVO about the specific VNF package on which the VNF is based. This identifier was allocated by the @@ -119,6 +119,7 @@ definitions: - flavourId - vnfState - extCpInfo + - _links properties: flavourId: description: > diff --git a/src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml b/src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml index 9a26b7f7..658fcdfb 100644 --- a/src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml +++ b/src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml @@ -534,6 +534,7 @@ definitions: required: - id - vnfVirtualLinkDescId + - networkResource properties: id: description: > -- GitLab From 74e4bcd5c125ffd25038cc608e11bc468f495997 Mon Sep 17 00:00:00 2001 From: Giacomo Bernini Date: Thu, 26 Mar 2020 16:14:28 +0100 Subject: [PATCH 258/260] fixed openapi version of sol003 vnf indicator interface --- .../VNFIndicatorNotification/VNFIndicatorNotification.yaml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/SOL003/VNFIndicatorNotification/VNFIndicatorNotification.yaml b/src/SOL003/VNFIndicatorNotification/VNFIndicatorNotification.yaml index 94194ad0..e93597ed 100644 --- a/src/SOL003/VNFIndicatorNotification/VNFIndicatorNotification.yaml +++ b/src/SOL003/VNFIndicatorNotification/VNFIndicatorNotification.yaml @@ -1,10 +1,10 @@ swagger: "2.0" info: - version: "1.2.0-impl:etsi.org:ETSI_NFV_OpenAPI:1" - title: SOL003 - VNF Indicator Notification interface + version: "1.2.1-impl:etsi.org:ETSI_NFV_OpenAPI:1" + title: SOL003 - VNF Indicator interface description: > - SOL003 - VNF Indicator Notification interface + SOL003 - VNF Indicator interface IMPORTANT: Please note that this file might be not aligned to the current -- GitLab From 3922c0356ece32081a7b9703791361a6e663eac2 Mon Sep 17 00:00:00 2001 From: Giacomo Bernini Date: Tue, 31 Mar 2020 14:13:16 +0200 Subject: [PATCH 259/260] updated api version --- src/SOL002/APIVersion/APIVersion.yaml | 2 +- src/SOL003/APIVersion/APIVersion.yaml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/SOL002/APIVersion/APIVersion.yaml b/src/SOL002/APIVersion/APIVersion.yaml index 85bd3471..c050b054 100644 --- a/src/SOL002/APIVersion/APIVersion.yaml +++ b/src/SOL002/APIVersion/APIVersion.yaml @@ -1,7 +1,7 @@ swagger: "2.0" info: - version: "1.2.0-impl:etsi.org:ETSI_NFV_OpenAPI:1" + version: "1.0.0-impl:etsi.org:ETSI_NFV_OpenAPI:1" title: SOL002 - API version interface description: > SOL002 - API version Interface diff --git a/src/SOL003/APIVersion/APIVersion.yaml b/src/SOL003/APIVersion/APIVersion.yaml index 77aaf6e0..5076f848 100644 --- a/src/SOL003/APIVersion/APIVersion.yaml +++ b/src/SOL003/APIVersion/APIVersion.yaml @@ -1,6 +1,6 @@ swagger: "2.0" info: - version: "1.2.0-impl:etsi.org:ETSI_NFV_OpenAPI:1" + version: "1.0.0-impl:etsi.org:ETSI_NFV_OpenAPI:1" title: "SOL003 - API version interface" description: > SOL003 - API version Interface -- GitLab From 70adcec5de003ed1449b12b6341e234d4b8dd465 Mon Sep 17 00:00:00 2001 From: Giacomo Bernini Date: Tue, 7 Apr 2020 12:34:04 +0200 Subject: [PATCH 260/260] Updated readme --- Readme.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Readme.md b/Readme.md index 354a209e..59baacd0 100644 --- a/Readme.md +++ b/Readme.md @@ -1,14 +1,14 @@ # NFV SOL002 and SOL003 APIs This repository hosts the [OpenAPI](https://www.openapis.org/) specificatons and other documentation -for the APIs defined in ETSI NFV GSs [SOL002](https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/002/02.06.01_60/gs_NFV-SOL002v020601p.pdf) and [SOL003](https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.06.01_60/gs_NFV-SOL003v020601p.pdf). +for the APIs defined in ETSI NFV GSs [SOL002](https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/002/02.07.01_60/gs_NFV-SOL002v020701p.pdf) and [SOL003](https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.07.01_60/gs_nfv-sol003v020701p.pdf). The APIs described in this repository are defined for the following reference points: * `Or-Vnfm` * `Ve-vnfm` -**IMPORTANT: These [OpenAPI](https://www.openapis.org/) specifications are in development phase. In case of discrepancies the published ETSI Group Specification takes precedence.** +**IMPORTANT: In case of discrepancies the published ETSI Group Specification takes precedence.** More information at [NFV Solutions wiki](https://nfvwiki.etsi.org/index.php?title=NFV_Solutions). -- GitLab