diff --git a/README.md b/README.md
index 2f9381fdd8688514f6bd06895f909644ef49d7e7..e1c5660ec792550fc5645f8ffedb6a8b186f0433 100644
--- a/README.md
+++ b/README.md
@@ -1,14 +1,14 @@
# NFV API Conformance Test Specification (NFV-TST 010)
This repository hosts the NFV API Conformance test specification for
-the APIs defined in ETSI NFV GS [SOL002](https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/002/04.03.01_60/gs_NFV-SOL002v040301p.pdf),
-[SOL003](https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/03.06.01_60/gs_NFV-SOL003v030601p.pdf),
-[SOL005](https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/005/03.06.01_60/gs_NFV-SOL005v030601p.pdf),
-[SOL009](https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/009/03.06.01_60/gs_NFV-SOL009v030601p.pdf) in their versions
-4.3.1, [SOL011](https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/011/03.03.01_60/gs_NFV-SOL011v030301p.pdf) in its version 3.3.1,
-and [SOL012](https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/012/03.04.01_60/gs_NFV-SOL012v030401p.pdf) in its version 3.4.1.
+the APIs defined in ETSI NFV GS [SOL002](https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/002/04.04.01_60/gs_NFV-SOL002v040401p.pdf),
+[SOL003](https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/04.04.01_60/gs_NFV-SOL003v040401p.pdf),
+[SOL005](https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/005/04.04.01_60/gs_NFV-SOL005v040401p.pdf),
+[SOL009](https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/009/04.04.01_60/gs_NFV-SOL009v040401p.pdf) in their versions
+4.3.1, [SOL011](https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/011/04.04.01_60/gs_NFV-SOL011v040401p.pdf) in its version 4.4.1,
+and [SOL012](https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/012/04.04.01_60/gs_NFV-SOL012v040401p.pdf) in its version 4.4.1.
-More information and download is available at [DGS/NFV-TST010ed431](https://portal.etsi.org/webapp/WorkProgram/Report_WorkItem.asp?WKI_ID=68072).
+More information and download is available at [DGS/NFV-TST010ed441]().
## Available versions
@@ -32,7 +32,7 @@ The NFV API Conformance test specification is available in the following version
| v3.6.1-maintenance | SOL002 SOL003 SOL005 v3.6.1
SOL009 v3.6.1
SOL011 v3.3.1
SOL012 v3.4.1 | [v3.6.1-fix-plu](https://forge.etsi.org/rep/nfv/api-tests/tree/3.6.1-fix-plu/) |
| v4.3.1 | SOL002 SOL003 SOL005 v4.3.1
SOL009 v4.3.1
SOL011 v3.3.1
SOL012 v3.4.1 | [v4.3.1](https://forge.etsi.org/rep/nfv/api-tests/tree/4.3.1/) |
| v4.3.1-maintenance | SOL002 SOL003 SOL005 v4.3.1
SOL009 v4.3.1
SOL011 v3.3.1
SOL012 v3.4.1 | [v4.3.1-fix-plu](https://forge.etsi.org/rep/nfv/api-tests/tree/4.3.1-fix-plu/) |
-
+| v4.4.1 | SOL002 SOL003 SOL005 v4.4.1
SOL009 v4.4.1
SOL011 v4.4.1
SOL012 v4.4.1 | work in progress |
## Test Specification Overview
diff --git a/SOL002/README.md b/SOL002/README.md
index 4a4d6a18fa680be9bfe5dcf2bfc7897963e0cdb1..ee46293ea8c00de5aa2cd08a367331f1529a3ca3 100644
--- a/SOL002/README.md
+++ b/SOL002/README.md
@@ -2,4 +2,4 @@
This folder includes the NFV API conformance test descriptions for NFV SOL002 APIs.
-The reference spec version is v4.3.1: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/002/04.03.01_60/gs_NFV-SOL002v040301p.pdf
+The reference spec version is v4.4.1: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/002/04.04.01_60/gs_NFV-SOL002v040401p.pdf
diff --git a/SOL002/VNFConfiguration-API/ApiVersion.robot b/SOL002/VNFConfiguration-API/ApiVersion.robot
index 601b261d26c567853b54e6b9ad992fbf083fe3fa..a392e48ceca165769811add868e486e2f820a4ed 100644
--- a/SOL002/VNFConfiguration-API/ApiVersion.robot
+++ b/SOL002/VNFConfiguration-API/ApiVersion.robot
@@ -11,7 +11,7 @@ POST API Version - Method not implemented
... Test title: POST API version - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -23,7 +23,7 @@ GET API Version
... Test title: GET API Version
... Test objective: The objective is to test that GET method successfully return ApiVersionInformation
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -36,7 +36,7 @@ PUT API Version - Method not implemented
... Test title: PUT API Version - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -48,7 +48,7 @@ PATCH API Version - Method not implemented
... Test title: PATCH API Version - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -60,7 +60,7 @@ DELETE API Version - Method not implemented
... Test title: DELETE API Version - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -72,7 +72,7 @@ POST API Version with apiMajorVerion - Method not implemented
... Test title: POST API version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -84,7 +84,7 @@ GET API Version with apiMajorVerion
... Test title: GET API Version with apiMajorVerion
... Test objective: The objective is to test that GET method successfully return ApiVersionInformation
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -97,7 +97,7 @@ PUT API Version with apiMajorVerion - Method not implemented
... Test title: PUT API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -109,7 +109,7 @@ PATCH API Version with apiMajorVerion - Method not implemented
... Test title: PATCH API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -121,7 +121,7 @@ DELETE API Version with apiMajorVerion - Method not implemented
... Test title: DELETE API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL002/VNFConfiguration-API/Configuration.robot b/SOL002/VNFConfiguration-API/Configuration.robot
index df2794519a13bd8c6285c6858699bdcae205908b..5ab2c41484b273c74318ba534d361baebea8b2d5 100644
--- a/SOL002/VNFConfiguration-API/Configuration.robot
+++ b/SOL002/VNFConfiguration-API/Configuration.robot
@@ -13,7 +13,7 @@ Set new VNF Configuration
... Test title: Set a new VNF Configuration
... Test objective: The objective is to test the creation of a new VNF configuration and perform a JSON schema validation of the returned configuration data structure
... Pre-conditions: A VNF instance is instantiated
- ... Reference: Clause 9.4.2.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 9.4.2.3.4 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation of HTTP Etag opaque identifiers
... Post-Conditions: The configuration is successfully set in the VNF and it matches the issued configuration
@@ -29,7 +29,7 @@ Get information about a VNF configuration
... Test title: Get information about a VNF configuration
... Test objective: The objective is to test the retrieval of an existing VNF instance configuration and perform a JSON schema validation of the collected configuration data structure
... Pre-conditions: A VNF instance is instantiated. The VNF instance is already configured.
- ... Reference: Clause 9.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 9.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -43,7 +43,7 @@ Get information about a VNF configuration with HTTP Etag
... Test title: Get information about a VNF configuration with HTTP Etag
... Test objective: The objective is to test the retrieval of an existing VNF instance configuration, check the generation by the VNF of an HTTP Etag opaque identifier, and perform a JSON schema validation of the collected configuration data structure
... Pre-conditions: A VNF instance is instantiated. The VNF instance is already configured
- ... Reference: Clause 9.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 9.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation of HTTP Etag opaque identifiers
... Post-Conditions: none
@@ -58,7 +58,7 @@ Set new VNF Configuration - HTTP Etag precondition unsuccessful
... Test title: Set a new VNF Configuration - HTTP Etag precondition unsuccessful
... Test objective: The objective is to test the unsuccess in setting a duplication of VNF configuration identified by an already used HTTP Etag identifier. The test also checks the JSON schema of the unsuccessful operation HTTP response.
... Pre-conditions: A VNF instance is instantiated. The VNF instance is already configured (Test ID 6.3.1.1.1) with a given HTTP Etag identifier.
- ... Reference: Clause 9.4.2.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 9.4.2.3.4 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation of HTTP Etag opaque identifiers
... Post-Conditions: The VNF configuration is not modified by the unsuccessful operation and it matches the configuration issued in Test ID 6.3.1.1.1
@@ -72,7 +72,7 @@ POST VNF Configuration - Method not implemented
... Test title: POST VNF Configuration - Method not implemented
... Test objective: The objective is to test that POST method is not allowed to create a new VNF configuration
... Pre-conditions: none
- ... Reference: Clause 9.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 9.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -84,7 +84,7 @@ PUT VNF Configuration - Method not implemented
... Test title: PUT VNF Configuration - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to modify an existing VNF configuration
... Pre-conditions: none
- ... Reference: Clause 9.4.2.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 9.4.2.3.3 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -96,7 +96,7 @@ DELETE VNF Configuration - Method not implemented
... Test title: Delete VNF Configuration - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to delete an existing VNF configuration
... Pre-conditions: none
- ... Reference: Clause 9.4.2.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 9.4.2.3.5 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -108,7 +108,7 @@ Set new VNF Configuration With Attribute vnfConfigurationData
... Test title: Set a new VNF Configuration with Attribute vnfConfigurationData
... Test objective: The objective is to test the creation of a new VNF configuration and perform a JSON schema validation of the returned configuration data structure
... Pre-conditions: A VNF instance is instantiated
- ... Reference: Clause 9.4.2.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 9.4.2.3.4 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation of HTTP Etag opaque identifiers
... Post-Conditions: The configuration is successfully set in the VNF and it matches the issued configuration
@@ -123,7 +123,7 @@ Set new VNF Configuration With Attribute vnfcConfigurationData
... Test title: Set a new VNF Configuration with Attribute vnfcConfigurationData
... Test objective: The objective is to test the creation of a new VNF configuration and perform a JSON schema validation of the returned configuration data structure
... Pre-conditions: A VNF instance is instantiated
- ... Reference: Clause 9.4.2.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 9.4.2.3.4 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation of HTTP Etag opaque identifiers
... Post-Conditions: The configuration is successfully set in the VNF and it matches the issued configuration
diff --git a/SOL002/VNFConfiguration-API/jsons/vnfConfigModifications.json b/SOL002/VNFConfiguration-API/jsons/vnfConfigModifications.json
index 16f8c15d54cb83ec0993d537872f7dfd3283deff..dac9060fd5f47e4562c766a1020615337f60ff49 100644
--- a/SOL002/VNFConfiguration-API/jsons/vnfConfigModifications.json
+++ b/SOL002/VNFConfiguration-API/jsons/vnfConfigModifications.json
@@ -35,7 +35,6 @@
]
}
],
- "dhcpServer": "string",
"vnfcSpecificData": {}
}
],
diff --git a/SOL002/VNFConfiguration-API/jsons/vnfConfigModificationsWithvnfcConfigurationData.json b/SOL002/VNFConfiguration-API/jsons/vnfConfigModificationsWithvnfcConfigurationData.json
index dbbeb16ea50e8e479d670b6566826ca0851df5a5..30148cb609725b2421e5492bb4820d6bd86f88e9 100644
--- a/SOL002/VNFConfiguration-API/jsons/vnfConfigModificationsWithvnfcConfigurationData.json
+++ b/SOL002/VNFConfiguration-API/jsons/vnfConfigModificationsWithvnfcConfigurationData.json
@@ -18,7 +18,6 @@
]
}
],
- "dhcpServer": "string",
"vnfcSpecificData": {}
}
],
diff --git a/SOL002/VNFConfiguration-API/schemas/vnfConfigModifications.schema.json b/SOL002/VNFConfiguration-API/schemas/vnfConfigModifications.schema.json
index 01f6087b6a3ef0f8551d13d2bb7348f6a1826f86..d6d51413ecd46dc2328a566d7c183aa2100f3a4c 100644
--- a/SOL002/VNFConfiguration-API/schemas/vnfConfigModifications.schema.json
+++ b/SOL002/VNFConfiguration-API/schemas/vnfConfigModifications.schema.json
@@ -200,11 +200,6 @@
}
}
},
- "dhcpServer": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
"vnfcSpecificData": {
"description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of keyvalue pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 8259. In the following example, a list of key-value pairs with four keys (\"aString\", \"aNumber\", \"anArray\" and \"anObject\") is provided to illustrate that the values associated with different keys can be of different type.\n",
"type": "object"
diff --git a/SOL002/VNFConfiguration-API/schemas/vnfConfiguration.schema.json b/SOL002/VNFConfiguration-API/schemas/vnfConfiguration.schema.json
index c28f9c65ee72d004a5a7d0824181b1e377184023..d99f14882e434195fdb467b627048b7aef38834b 100644
--- a/SOL002/VNFConfiguration-API/schemas/vnfConfiguration.schema.json
+++ b/SOL002/VNFConfiguration-API/schemas/vnfConfiguration.schema.json
@@ -383,11 +383,6 @@
}
}
},
- "dhcpServer": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
"vnfcSpecificData": {
"description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of keyvalue pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 8259. In the following example, a list of key-value pairs with four keys (\"aString\", \"aNumber\", \"anArray\" and \"anObject\") is provided to illustrate that the values associated with different keys can be of different type.\n",
"type": "object"
diff --git a/SOL002/VNFFaultManagement-API/Alarms.robot b/SOL002/VNFFaultManagement-API/Alarms.robot
index 806b40f8691d36b8712137455e6160493cc866b3..85e66e5ede230c3bda250beab7c7e0ae2fc1e11f 100644
--- a/SOL002/VNFFaultManagement-API/Alarms.robot
+++ b/SOL002/VNFFaultManagement-API/Alarms.robot
@@ -13,7 +13,7 @@ POST Alarms - Method not implemented
... Test title: POST Alarms - Method not implemented
... Test objective: The objective is to test that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 7.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -25,7 +25,7 @@ GET information about multiple alarms
... Test title: GET information about multiple alarms
... Test objective: The objective is to retrieve information about the alarm list
... Pre-conditions: none
- ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -38,7 +38,7 @@ GET information about multiple alarms with attribute-based filter
... Test title: GET information about multiple alarms with attribute-based filter
... Test objective: The objective is to retrieve information about the alarm list with attribute-based filter
... Pre-conditions: none
- ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -51,7 +51,7 @@ GET information about multiple alarms with invalid attribute-based filter
... Test title: GET information about multiple alarms with invalid attribute-based filter
... Test objective: The objective is to retrieve information about the alarm list
... Pre-conditions: none
- ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -64,7 +64,7 @@ GET information about multiple alarms with "all_fields" attribute selector
... Test title: GET information about multiple alarms with "all_fields" attribute selector
... Test objective: The objective is to retrieve information about the alarm list
... Pre-conditions: none
- ... Reference: Clause 7.4.2.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.2.3.3 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -77,7 +77,7 @@ GET information about multiple alarms with exclude_default attribute selector
... Test title: GET information about multiple alarms with "exclude_default" attribute selector
... Test objective: The objective is to retrieve information about the alarm list
... Pre-conditions: none
- ... Reference: Clause 7.4.2.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.2.3.3 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -90,7 +90,7 @@ GET information about multiple alarms with fields attribute selector
... Test title: GET information about multiple alarms with fields attribute selector
... Test objective: The objective is to retrieve information about the alarm list
... Pre-conditions: none
- ... Reference: Clause 7.4.2.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.2.3.3 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -103,7 +103,7 @@ GET information about multiple alarms with "exclude_fields" attribute selector
... Test title: GET information about multiple alarms with "exclude_fields" attribute selector
... Test objective: The objective is to retrieve information about the alarm list
... Pre-conditions: none
- ... Reference: Clause 7.4.2.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.2.3.3 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -116,7 +116,7 @@ PUT Alarms - Method not implemented
... Test title: PUT Alarms - Method not implemented
... Test objective: The objective is to test that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 7.4.2.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.2.3.3 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -128,7 +128,7 @@ PATCH Alarms - Method not implemented
... Test title: PATCH Alarms - Method not implemented
... Test objective: The objective is to test that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 7.4.2.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.2.3.4 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -140,7 +140,7 @@ DELETE Alarms - Method not implemented
... Test title: DELETE Alarms - Method not implemented
... Test objective: The objective is to test that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 7.4.2.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.2.3.5 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -152,7 +152,7 @@ GET information about multiple alarms to get Paged Response
... Test title: GET information about multiple alarms to get Paged Response
... Test objective: The objective is to retrieve information about the alarms to get paged response
... Pre-conditions: none
- ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -165,7 +165,7 @@ GET information about multiple alarms for Bad Request Response too big
... Test title: GET information about multiple alarms for Bad Request Response too big
... Test objective: The objective is to test that GET method fail retrieving status information about Alarms when Response is too big, and perform the JSON schema validation of the failed operation HTTP response
... Pre-conditions: none
- ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -178,7 +178,7 @@ GET information about alarms with attribute-based filter "id"
... Test title: GET information about alarms with attribute-based filter "id"
... Test objective: The objective is to retrieve information about the alarm list with alarm filter "id"
... Pre-conditions: none
- ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -192,7 +192,7 @@ GET information about multiple alarms with attribute-based filter "vnfcInstanceI
... Test title: GET information about multiple alarms with attribute-based filter "vnfcInstanceIds"
... Test objective: The objective is to retrieve information about the alarm list with attribute filter "vnfcInstanceIds"
... Pre-conditions: none
- ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -206,7 +206,7 @@ GET information about multiple alarms with attribute-based filter "rootCauseFaul
... Test title: GET information about multiple alarms with attribute-based filter "rootCauseFaultyResource.faultyResourceType"
... Test objective: The objective is to retrieve information about the alarm list with attribute filter "rootCauseFaultyResource.faultyResourceType"
... Pre-conditions: none
- ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -220,7 +220,7 @@ GET information about multiple alarms with attribute-based filter "eventType"
... Test title: GET information about multiple alarms with attribute-based filter "eventType"
... Test objective: The objective is to retrieve information about the alarm list with attribute filter "eventType"
... Pre-conditions: none
- ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -234,7 +234,7 @@ GET information about multiple alarms with attribute-based filter "perceivedSeve
... Test title: GET information about multiple alarms with attribute-based filter "perceivedSeverity"
... Test objective: The objective is to retrieve information about the alarm list with attribute filter "perceivedSeverity"
... Pre-conditions: none
- ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -248,7 +248,7 @@ GET information about multiple alarms with attribute-based filter "probableCause
... Test title: GET information about multiple alarms with attribute-based filter "probableCause"
... Test objective: The objective is to retrieve information about the alarm list with attribute filter "probableCause"
... Pre-conditions: none
- ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL002/VNFFaultManagement-API/ApiVersion.robot b/SOL002/VNFFaultManagement-API/ApiVersion.robot
index 630a5705ec97ef3567adc542e8daa7dc673c9e86..e86481de002f4c1a8ae4f6f744d0e0565b0117a9 100644
--- a/SOL002/VNFFaultManagement-API/ApiVersion.robot
+++ b/SOL002/VNFFaultManagement-API/ApiVersion.robot
@@ -13,7 +13,7 @@ POST API Version - Method not implemented
... Test title: POST API version - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -25,7 +25,7 @@ GET API Version
... Test title: GET API Version
... Test objective: The objective is to test that GET method successfully return ApiVersionInformation
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -38,7 +38,7 @@ PUT API Version - Method not implemented
... Test title: PUT API Version - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -50,7 +50,7 @@ PATCH API Version - Method not implemented
... Test title: PATCH API Version - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -62,7 +62,7 @@ DELETE API Version - Method not implemented
... Test title: DELETE API Version - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -74,7 +74,7 @@ POST API Version with apiMajorVerion - Method not implemented
... Test title: POST API version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -86,7 +86,7 @@ GET API Version with apiMajorVerion
... Test title: GET API Version with apiMajorVerion
... Test objective: The objective is to test that GET method successfully return ApiVersionInformation
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -99,7 +99,7 @@ PUT API Version with apiMajorVerion - Method not implemented
... Test title: PUT API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -111,7 +111,7 @@ PATCH API Version with apiMajorVerion - Method not implemented
... Test title: PATCH API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -123,7 +123,7 @@ DELETE API Version with apiMajorVerion - Method not implemented
... Test title: DELETE API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL002/VNFFaultManagement-API/EscalatePerceivedSeverityTask.robot b/SOL002/VNFFaultManagement-API/EscalatePerceivedSeverityTask.robot
index 66bbc3465bdac0a97f0908beca234d227b75fd90..9f5720799b896943d11dcf9ad33b6e3a3b5942c5 100644
--- a/SOL002/VNFFaultManagement-API/EscalatePerceivedSeverityTask.robot
+++ b/SOL002/VNFFaultManagement-API/EscalatePerceivedSeverityTask.robot
@@ -12,7 +12,7 @@ Escalate the perceived severity
... Test title: Escalate the perceived severity
... Test objective: To enable the consumer to escalate the perceived severity of an alarm that is represented by an individual alarm resource.
... Pre-conditions: The resource representing the individual alarm has been created
- ... Reference: Clause 7.4.4.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.4.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -24,7 +24,7 @@ GET Escalate the perceived severity - Method not implemented
... Test title: GET Escalate the perceived severity - Method not implemented
... Test objective: The objective is to test that the GET HTTP method not implemented for escalate perceived severity
... Pre-conditions: none
- ... Reference: Clause 7.4.4.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.4.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -36,7 +36,7 @@ PUT Escalate the perceived severity - Method not implemented
... Test title: PUT Escalate the perceived severity - Method not implemented
... Test objective: The objective is to test that the PUT HTTP method not implemented for escalate perceived severity
... Pre-conditions: none
- ... Reference: Clause 7.4.4.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.4.3.3 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -48,7 +48,7 @@ PATCH Escalate the perceived severity - Method not implemented
... Test title: PATCH Escalate the perceived severity - Method not implemented
... Test objective: The objective is to test that the PATCH HTTP method not implemented for escalate perceived severity
... Pre-conditions: none
- ... Reference: Clause 7.4.4.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.4.3.4 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -60,7 +60,7 @@ DELETE Escalate the perceived severity - Method not implemented
... Test title: DELETE Escalate the perceived severity - Method not implemented
... Test objective: The objective is to test that the DELETE HTTP method not implemented for escalate perceived severity
... Pre-conditions: none
- ... Reference: Clause 7.4.4.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.4.3.5 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL002/VNFFaultManagement-API/IndividualAlarm.robot b/SOL002/VNFFaultManagement-API/IndividualAlarm.robot
index 07c739c29d5474c2efe384509d7870390389f0b0..2bc4beff66b675052fbda2c328db5b6e09818c15 100644
--- a/SOL002/VNFFaultManagement-API/IndividualAlarm.robot
+++ b/SOL002/VNFFaultManagement-API/IndividualAlarm.robot
@@ -15,7 +15,7 @@ POST Alarm - Method not implemented
... Test title: POST Alarm - Method not implemented
... Test objective: The objective is to test that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 7.4.3.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.3.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -27,7 +27,7 @@ GET information about an individual alarm
... Test title: GET information about an individual alarm
... Test objective: The objective is to read an individual alarm.
... Pre-conditions: The related alarm exists
- ... Reference: Clause 7.4.3.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.3.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -41,7 +41,7 @@ PUT Individual Alarm - Method not implemented
... Test title: PUT Individual Alarm - Method not implemented
... Test objective: The objective is to test that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 7.4.3.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.3.3.3 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -53,7 +53,7 @@ PATCH Individual Alarm
... Test title: PATCH Individual Alarm
... Test objective: The objective is to Modify an individual alarm resource
... Pre-conditions: The related alarm exists
- ... Reference: Clause 7.4.3.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.3.3.4 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -67,7 +67,7 @@ PATCH Individual Alarm - Precondition failed
... Test title: PATCH Individual Alarm - Precondition failed
... Test objective: The objective is to attempt to Modify an individual alarm resource, where the precondition was not met
... Pre-conditions: The related alarm exists
- ... Reference: Clause 7.4.3.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.3.3.4 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: The alarm resource is not modified
@@ -81,7 +81,7 @@ PATCH Individual Alarm - Conflict
... Test title: PATCH Individual Alarm - Conflict
... Test objective: The objective is to Modify an individual alarm resource
... Pre-conditions: The related alarm exists
- ... Reference: Clause 7.4.3.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.3.3.4 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: The alarm resource is not modified
@@ -95,7 +95,7 @@ DELETE Individual Alarm - Method not implemented
... Test title: DELETE Individual Alarm - Method not implemented
... Test objective: The objective is to test that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 7.4.3.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.3.3.5 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -107,7 +107,7 @@ GET information about an individual alarm - Not Found
... Test title: GET information about an individual alarm - Not Found
... Test objective: The objective is to test that GET method fail retrieving status information about individaual Alarms when alarm is not present.
... Pre-conditions: The related alarm doesnot exists
- ... Reference: Clause 7.4.3.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.3.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL002/VNFFaultManagement-API/IndividualSubscription.robot b/SOL002/VNFFaultManagement-API/IndividualSubscription.robot
index 52438e58acaf8fc90e7183e69a356c2c21c368c1..829a9b580a712331170f665823735fe4d30af9e8 100644
--- a/SOL002/VNFFaultManagement-API/IndividualSubscription.robot
+++ b/SOL002/VNFFaultManagement-API/IndividualSubscription.robot
@@ -13,7 +13,7 @@ POST Individual Subscription - Method not implemented
... Test title: POST Individual Subscription - Method not implemented
... Test objective: The objective is to test that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 7.4.6.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.6.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -25,7 +25,7 @@ GET Information about an individual subscription
... Test title: GET Information about an individual subscription
... Test objective: The objective is to read an individual subscription for VNF alarms subscribed by the client
... Pre-conditions: The subscription with the given id exists
- ... Reference: Clause 7.4.6.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.6.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -38,7 +38,7 @@ PUT an individual subscription - Method not implemented
... Test title: PUT an individual subscription - Method not implemented
... Test objective: The objective is to test that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 7.4.6.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.6.3.3 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -50,7 +50,7 @@ PATCH an individual subscription - Method not implemented
... Test title: PATCH an individual subscription - Method not implemented
... Test objective: The objective is to test that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 7.4.6.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.6.3.4 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -62,7 +62,7 @@ DELETE an individual subscription
... Test title: DELETE an individual subscription
... Test objective: The objective is to test that the deletion of a individual subscription resource.
... Pre-conditions: one or more subscription already exsist
- ... Reference: Clause 7.4.6.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.6.3.5 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: the subscription is deleted
@@ -75,7 +75,7 @@ GET Information about an individual subscription - Not Found
... Test title: GET Information about an individual subscription - Not Found
... Test objective: The objective is to test that GET method fail retrieving individual subscription for VNF alarms subscribed by the client because it is not present.
... Pre-conditions: The subscription with the given id donot exists
- ... Reference: Clause 7.4.6.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.6.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL002/VNFFaultManagement-API/NotificationEndpoint.robot b/SOL002/VNFFaultManagement-API/NotificationEndpoint.robot
index 7432ceebe2cb54c16a4531ad5d7916ac0ac180e5..9c4284213752802b68953105d2f0b9f6bec1974e 100644
--- a/SOL002/VNFFaultManagement-API/NotificationEndpoint.robot
+++ b/SOL002/VNFFaultManagement-API/NotificationEndpoint.robot
@@ -13,7 +13,7 @@ VNF Fault Alarm Notification
... Test title: VNF Fault Alarm Notification
... Test objective: The objective is to test that VNF Fault Alarm Notification is delivered with success to the notification consumer
... Pre-conditions: A VNF instance is instantiated, and a subscription for fault alarm notifications is available in the VNFM.
- ... Reference: Clause 7.4.7.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.7.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
@@ -25,7 +25,7 @@ VNF Fault Alarm Cleared Notification
... Test title: VNF Fault Alarm Cleared Notification
... Test objective: The objective is to test that VNF Fault Alarm Cleared Notification is delivered with success to the notification consumer
... Pre-conditions: A VNF instance is instantiated, and a subscription for fault alarm cleared notifications is available in the VNFM.
- ... Reference: Clause 7.4.7.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.7.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
@@ -37,7 +37,7 @@ VNF Fault Alarm List Rebuilt Notification
... Test title: VNF Fault List Rebuilt Alarm List Rebuilt Notification
... Test objective: The objective is to test that VNF Fault Alarm List Rebuilt Notification is delivered with success to the notification consumer
... Pre-conditions: A VNF instance is instantiated, and a subscription for fault alarm list rebuilt notifications is available in the VNFM.
- ... Reference: Clause 7.4.7.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.7.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
diff --git a/SOL002/VNFFaultManagement-API/Notifications.robot b/SOL002/VNFFaultManagement-API/Notifications.robot
index 7f2da3b2cac8d56f095896ff8d41bad642ee5043..e42ad091d386fc421b1e24ab33ccf6948e11ec18 100644
--- a/SOL002/VNFFaultManagement-API/Notifications.robot
+++ b/SOL002/VNFFaultManagement-API/Notifications.robot
@@ -15,7 +15,7 @@ VNF Fault Alarm Notification
... Test title: VNF Fault Alarm Notification
... Test objective: The objective is to test the dispatch of VNF Fault Alarm Notification when a virtualised resource within an VNF instance fails, and perform a JSON schema and content validation of the delivered notification. The action that triggers the notification under test is an explicit test step, but it is not performed by the test system.
... Pre-conditions: A VNF instance is instantiated, and a subscription for fault alarm notifications is available in the VNFM.
- ... Reference: Clause 7.4.7.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.7.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -28,7 +28,7 @@ VNF Fault Alarm Cleared Notification
... Test title: VNF Fault Alarm Cleared Notification
... Test objective: The objective is to test the dispatch of VNF Fault Alarm Cleared Notification when a faulty virtualised resource within an VNF instance is cleared, and perform a JSON schema and content validation of the delivered notification. The action that triggers the notification under test is an explicit test step, but it is not performed by the test system.
... Pre-conditions: A VNF instance is instantiated, a virtualised resource is in faulty state, and a subscription for fault alarm cleared notifications is available in the VNFM.
- ... Reference: Clause 7.4.7.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.7.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -41,7 +41,7 @@ VNF Fault Alarm List Rebuilt Notification
... Test title: VNF Fault Alarm List Rebuilt Notification
... Test objective: The objective is to test the dispatch of VNF Fault Alarm List Rebuilt Notification when the VNFM decides to rebuild the list of its VNF alarms, e.g. due to a corruption in the alarm storage, and perform a JSON schema and content validation of the delivered notification. The action that triggers the notification under test is an explicit test step, but it is not performed by the test system.
... Pre-conditions: A VNF instance is instantiated, one or more virtualised resource are in faulty state, and a subscription for fault alarm list rebuilt notifications is available in the VNFM.
- ... Reference: Clause 7.4.7.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.7.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL002/VNFFaultManagement-API/Subscriptions.robot b/SOL002/VNFFaultManagement-API/Subscriptions.robot
index bfee46e5c62923bf6501d3d90e38af1498ecc8b3..2e3b5b7db3c316a75d39e9db4613109ea586e478 100644
--- a/SOL002/VNFFaultManagement-API/Subscriptions.robot
+++ b/SOL002/VNFFaultManagement-API/Subscriptions.robot
@@ -16,7 +16,7 @@ Create a new subscription
... Test title: Create a new subscription
... Test objective: The objective is to create a new subscription.
... Pre-conditions: no subscription with the same filter and callbackUri exists
- ... Reference: Clause 7.4.5.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.5.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: Resource created successfully
@@ -31,7 +31,7 @@ Create a duplicated Subscription
... Test title: Create a duplicated Subscription
... Test objective: The objective is to create a duplicate subscription.
... Pre-conditions: subscription with the same filter and callbackUri exists
- ... Reference: Clause 7.4.5.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.5.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability:
... Post-Conditions: duplicated subscription is created if the IUT allows duplications, otherwise the duplicated subscription is not created
@@ -54,7 +54,7 @@ GET Subscriptions
... Test title: GET Subscriptions
... Test objective: The objective is to retrieve the list of active subscriptions
... Pre-conditions: none
- ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -67,7 +67,7 @@ GET Subscription - Filter
... Test title: GET Subscription - Filter
... Test objective: The objective is to retrieve the list of active subscriptions with filter
... Pre-conditions: none
- ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -80,7 +80,7 @@ GET subscriptions - Bad Request Invalid attribute-based filtering parameters
... Test title: GET subscriptions - Bad Request Invalid attribute-based filtering parameters
... Test objective: The objective is to retrieve the list of active subscriptions with Invalid attribute-based filtering parameters
... Pre-conditions: none
- ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -93,7 +93,7 @@ GET subscriptions with "all_fields" attribute selector
... Test title: GET subscriptions with "all_fields" attribute selector
... Test objective: The objective is to retrieve the list of active subscriptions with attribute selector
... Pre-conditions: none
- ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -106,7 +106,7 @@ GET subscriptions with "exclude_default" attribute selector
... Test title: GET subscriptions with "exclude_default" attribute selector
... Test objective: The objective is to retrieve the list of active subscriptions with attribute selector
... Pre-conditions: none
- ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -119,7 +119,7 @@ GET subscriptions with "fields" attribute selector
... Test title: GET subscriptions with "fields" attribute selector
... Test objective: The objective is to retrieve the list of active subscriptions with attribute selector
... Pre-conditions: none
- ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -132,7 +132,7 @@ GET subscriptions with "exclude_fields" attribute selector
... Test title: GET subscriptions with "exclude_fields" attribute selector
... Test objective: The objective is to retrieve the list of active subscriptions with attribute selector
... Pre-conditions: none
- ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -145,7 +145,7 @@ PUT subscriptions - Method not implemented
... Test title: PUT subscriptions - Method not implemented
... Test objective: The objective is to test that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 7.4.5.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.5.3.3 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -157,7 +157,7 @@ PATCH subscriptions - Method not implemented
... Test title: PUT subscriptions - Method not implemented
... Test objective: The objective is to test that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 7.4.5.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.5.3.4 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -169,7 +169,7 @@ DELETE subscriptions - Method not implemented
... Test title: DELETE subscriptions - Method not implemented
... Test objective: The objective is to test that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 7.4.5.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.5.3.5 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -181,7 +181,7 @@ GET Subscriptions to get Paged Response
... Test title: GET Subscriptions to get Paged Response
... Test objective: The objective is to retrieve the list of active subscriptions to get paged response
... Pre-conditions: none
- ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -194,7 +194,7 @@ GET subscriptions - Bad Request Response too Big
... Test title: GET subscriptions - Bad Request Response too Big
... Test objective: The objective is to test that GET method fail retrieving list of active subscription because Response is too big, and perform the JSON schema validation of the failed operation HTTP response
... Pre-conditions: none
- ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -207,7 +207,7 @@ GET Subscription with attribute-based filter "id"
... Test title: GET Subscription with attribute-based filter "id"
... Test objective: The objective is to retrieve the list of active subscriptions with filter "id"
... Pre-conditions: none
- ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -221,7 +221,7 @@ Get subscriptions with filter "filter.notificationTypes"
... Test title: GET Subscription with attribute-based filter "filter.notificationTypes"
... Test objective: The objective is to retrieve the list of active subscriptions with filter "filter.notificationTypes"
... Pre-conditions: none
- ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -235,7 +235,7 @@ Get subscriptions with filter "filter.faultyResourceTypes"
... Test title: GET Subscription with attribute-based filter "filter.faultyResourceTypes"
... Test objective: The objective is to retrieve the list of active subscriptions with filter "filter.faultyResourceTypes"
... Pre-conditions: none
- ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -249,7 +249,7 @@ Get subscriptions with filter "filter.perceivedSeverities"
... Test title: GET Subscription with attribute-based filter "filter.perceivedSeverities"
... Test objective: The objective is to retrieve the list of active subscriptions with filter "filter.perceivedSeverities"
... Pre-conditions: none
- ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -263,7 +263,7 @@ Get subscriptions with filter "filter.eventTypes"
... Test title: GET Subscription with attribute-based filter "filter.eventTypes"
... Test objective: The objective is to retrieve the list of active subscriptions with filter "filter.eventTypes"
... Pre-conditions: none
- ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -277,7 +277,7 @@ Get subscriptions with filter "filter.probableCauses"
... Test title: GET Subscription with attribute-based filter "filter.probableCauses"
... Test objective: The objective is to retrieve the list of active subscriptions with filter "filter.probableCauses"
... Pre-conditions: none
- ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -286,12 +286,12 @@ Get subscriptions with filter "filter.probableCauses"
Check HTTP Response Body Json Schema Is FmSubscriptions
Check PostCondition HTTP Response Body Subscriptions Matches the requested attribute-based filter "filter_probableCauses"
-POST Create a new Subscription - Unprocessable Entity
+POST Create a new Subscription - Unprocessable Content
[Documentation] Test ID: 6.3.4.4.22
- ... Test title: POST Create a new Subscription - Unprocessable Entity
- ... Test objective: The objective is to test that 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.
+ ... Test title: POST Create a new Subscription - Unprocessable Content
+ ... Test objective: The objective is to test that content type of the message content is supported and the message content of a request contains syntactically correct data but the data cannot be processed.
... re-conditions: none
- ... Reference: Clause 7.4.5.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 7.4.5.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL002/VNFIndicator-API/ApiVersion.robot b/SOL002/VNFIndicator-API/ApiVersion.robot
index d3205fd50acfa8812aee3ae9685e95117874a0c9..728274e98eb3f0069ad1fd66cc21d5b193748a05 100644
--- a/SOL002/VNFIndicator-API/ApiVersion.robot
+++ b/SOL002/VNFIndicator-API/ApiVersion.robot
@@ -13,7 +13,7 @@ POST API Version - Method not implemented
... Test title: POST API version - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -25,7 +25,7 @@ GET API Version
... Test title: GET API Version
... Test objective: The objective is to test that GET method successfully return ApiVersionInformation
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -38,7 +38,7 @@ PUT API Version - Method not implemented
... Test title: PUT API Version - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -50,7 +50,7 @@ PATCH API Version - Method not implemented
... Test title: PATCH API Version - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -62,7 +62,7 @@ DELETE API Version - Method not implemented
... Test title: DELETE API Version - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -74,7 +74,7 @@ POST API Version with apiMajorVerion - Method not implemented
... Test title: POST API version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -86,7 +86,7 @@ GET API Version with apiMajorVerion
... Test title: GET API Version with apiMajorVerion
... Test objective: The objective is to test that GET method successfully return ApiVersionInformation
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -99,7 +99,7 @@ PUT API Version with apiMajorVerion - Method not implemented
... Test title: PUT API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -111,7 +111,7 @@ PATCH API Version with apiMajorVerion - Method not implemented
... Test title: PATCH API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -123,7 +123,7 @@ DELETE API Version with apiMajorVerion - Method not implemented
... Test title: DELETE API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL002/VNFIndicator-API/IndividualSubscription.robot b/SOL002/VNFIndicator-API/IndividualSubscription.robot
index 4a1e6e24200a79e9772ebbcd440d9335f7b0b744..73e01f6ce37d30c77343cd1e0ad0282cdca3fd54 100644
--- a/SOL002/VNFIndicator-API/IndividualSubscription.robot
+++ b/SOL002/VNFIndicator-API/IndividualSubscription.robot
@@ -10,7 +10,7 @@ GET Individual VNF Indicator Subscription
... Test title: Get individual subscription to VNF performance indicators
... Test objective: The objective is to test the retrieval of individual VNF performance indicator subscription and perform a JSON schema validation of the returned subscription data structure
... Pre-conditions: A VNF instance is instantiated. At least one VNF indicator subscription is available in the VNF.
- ... Reference: Clause 8.4.6.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.6.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation and maintenance of performance indicators
... Post-Conditions: none
@@ -23,7 +23,7 @@ GET Individual VNF Indicator Subscription with invalid resource identifier
... Test title: Get individual subscription to VNF performance indicators
... Test objective: The objective is to test that the retrieval of individual VNF performance indicator subscription fails when using an invalid resource identifier. The test also checks the JSON schema of the unsuccessful operation HTTP response.
... Pre-conditions: A VNF instance is instantiated. At least one VNF indicator subscription is available in the VNF.
- ... Reference: Clause 8.4.6.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.6.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation and maintenance of performance indicators
... Post-Conditions: none
@@ -36,7 +36,7 @@ DELETE Individual VNF Indicator Subscription
... Test title: Delete individual subscription to VNF performance indicators
... Test objective: The objective is to test the deletion of an individual VNF performance indicator subscription.
... Pre-conditions: A VNF instance is instantiated. At least one VNF indicator subscription is available in the VNF.
- ... Reference: clause 8.4.6.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: clause 8.4.6.3.5 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation and maintenance of performance indicators
... Post-Conditions: The subscription to VNF performance indicators is deleted
@@ -49,7 +49,7 @@ DELETE Individual VNF Indicator Subscription with invalid resource identifier
... Test title: Delete individual subscription to VNF performance indicators
... Test objective: The objective is to test that the deletion of an individual VNF performance indicator subscription fails when using an invalid resource identifier. The test also checks the JSON schema of the unsuccessful operation HTTP response.
... Pre-conditions: A VNF instance is instantiated. At least one VNF indicator subscription is available in the VNF.
- ... Reference: clause 8.4.6.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: clause 8.4.6.3.5 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation and maintenance of performance indicators
... Post-Conditions: none
@@ -62,7 +62,7 @@ PUT Individual VNF Indicator Subscription - Method not implemented
... Test title: PUT individual VNF indicator subscription - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to modify an individual VNF performance indicator subscription
... Pre-conditions: none
- ... Reference: Clause 8.4.6.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.6.3.3 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation and maintenance of performance indicators.
... Post-Conditions: none
@@ -74,7 +74,7 @@ PATCH Individual VNF Indicator Subscription - Method not implemented
... Test title: PUT individual VNF indicator subscription - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update an individual VNF performance indicator subscription
... Pre-conditions: none
- ... Reference: Clause 8.4.6.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.6.3.4 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation and maintenance of performance indicators.
... Post-Conditions: none
@@ -86,7 +86,7 @@ POST Individual VNF Indicator Subscription - Method not implemented
... Test title: PUT individual VNF indicator subscription - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to modify an individual VNF performance indicator subscription
... Pre-conditions: none
- ... Reference: Clause 8.4.6.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.6.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation and maintenance of performance indicators.
... Post-Conditions: none
diff --git a/SOL002/VNFIndicator-API/IndividualVNFindicator.robot b/SOL002/VNFIndicator-API/IndividualVNFindicator.robot
index e70906560f907e0672731a41b22e6ee9b2ba6001..106f4deb1d4493aeecdb8c24273fce33c54af5a7 100644
--- a/SOL002/VNFIndicator-API/IndividualVNFindicator.robot
+++ b/SOL002/VNFIndicator-API/IndividualVNFindicator.robot
@@ -9,7 +9,7 @@ Get Individual Indicator for VNF Instance
... Test title: Get individual performance indicator for a VNF instance
... Test objective: The objective is to test the retrieval of a performance indicator for a given VNF instance and perform a JSON schema validation of the returned indicator data structure
... Pre-conditions: A VNF instance is instantiated. At least one measure of performance indicator is available for the given VNF instance.
- ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation and maintenance of performance indicators
... Post-Conditions: none
@@ -24,7 +24,7 @@ Get Individual Indicator for VNF Instance with invalid indicator identifier
... Test title: Get individual performance indicator for a VNF instance with invalid indicator identifier
... Test objective: The objective is to test that the retrieval of a performance indicator for a given VNF instance fails when using an invalid resource identifier. The test also checks the JSON schema of the unsuccessful operation HTTP response.
... Pre-conditions: A VNF instance is instantiated. At least one measure of performance indicator is available for the given VNF instance.
- ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation and maintenance of performance indicators.
... Post-Conditions: none
@@ -37,7 +37,7 @@ POST Individual VNF Indicator - Method not implemented
... Test title: POST individual performance indicator for VNF instance - Method not implemented
... Test objective: The objective is to test that POST method is not allowed to create a new performance indicator for a VNF instance
... Pre-conditions: none
- ... Reference: Clause 8.4.4.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.4.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation and maintenance of performance indicators.
... Post-Conditions: none
@@ -49,7 +49,7 @@ PUT Individual VNF Indicator - Method not implemented
... Test title: PUT individual performance indicator for VNF instance - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to modify an existing performance indicator for a VNF instance
... Pre-conditions: none
- ... Reference: Clause 8.4.4.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.4.3.3 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation and maintenance of performance indicators.
... Post-Conditions: none
@@ -61,7 +61,7 @@ PATCH Individual VNF Indicator - Method not implemented
... Test title: PATCH individual performance indicator for VNF instance - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update an existing performance indicator for a VNF instance
... Pre-conditions: none
- ... Reference: Clause 8.4.4.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.4.3.4 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation and maintenance of performance indicators.
... Post-Conditions: none
@@ -73,7 +73,7 @@ DELETE Individual VNF Indicator - Method not implemented
... Test title: DELETE individual performance indicator indicators for VNF instance - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to delete an existing performance indicator for a VNF instance
... Pre-conditions: none
- ... Reference: Clause 8.4.3.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.3.3.5 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation and maintenance of performance indicators.
... Post-Conditions: none
@@ -85,7 +85,7 @@ Get Individual Performance Indicator
... Test title: Get Individual Performance Indicator
... Test objective: The objective is to test the retrieval of a performance indicator and perform a JSON schema validation of the returned indicator data structure
... Pre-conditions: At least one measure of performance indicator is available..
- ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation and maintenance of performance indicators
... Post-Conditions: none
@@ -99,7 +99,7 @@ Get Individual Performance Indicator with invalid indicator identifier
... Test title: Get Individual Performance Indicator with invalid indicator identifier
... Test objective: The objective is to test that the retrieval of a performance indicator fails when using an invalid resource identifier. The test also checks the JSON schema of the unsuccessful operation HTTP response.
... Pre-conditions: At least one measure of performance indicator is available.
- ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation and maintenance of performance indicators.
... Post-Conditions: none
@@ -112,7 +112,7 @@ POST Individual Performance Indicator - Method not implemented
... Test title: POST Individual Performance Indicator - Method not implemented
... Test objective: The objective is to test that POST method is not allowed to create a new performance indicator.
... Pre-conditions: none
- ... Reference: Clause 8.4.4.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.4.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation and maintenance of performance indicators.
... Post-Conditions: none
@@ -124,7 +124,7 @@ PUT Individual Performance Indicator - Method not implemented
... Test title: PUT Individual Performance Indicator - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to modify an existing performance indicator.
... Pre-conditions: none
- ... Reference: Clause 8.4.4.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.4.3.3 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation and maintenance of performance indicators.
... Post-Conditions: none
@@ -136,7 +136,7 @@ PATCH Individual Performance Indicator - Method not implemented
... Test title: PATCH Individual Performance Indicator - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update an existing performance indicator.
... Pre-conditions: none
- ... Reference: Clause 8.4.4.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.4.3.4 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation and maintenance of performance indicators.
... Post-Conditions: none
@@ -148,7 +148,7 @@ DELETE Individual Performance Indicator - Method not implemented
... Test title: DELETE Individual Performance Indicator - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to delete an existing performance indicator.
... Pre-conditions: none
- ... Reference: Clause 8.4.3.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.3.3.5 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation and maintenance of performance indicators.
... Post-Conditions: none
diff --git a/SOL002/VNFIndicator-API/NotificationEndpoint.robot b/SOL002/VNFIndicator-API/NotificationEndpoint.robot
index b85205047e30cf10ad65e5f34b1dff52cd9ff304..a537c7f44067c2ac12457cf873f2f244bc3ee038 100644
--- a/SOL002/VNFIndicator-API/NotificationEndpoint.robot
+++ b/SOL002/VNFIndicator-API/NotificationEndpoint.robot
@@ -12,7 +12,7 @@ VNF Indicator Value Change Notification
... Test title: VNF Indicator Value Change Notification
... Test objective: The objective is to test that the POST request triggers VNF Indicator Value Change Notification .
... Pre-conditions: A VNF is instantiated, and a subscription for indicator value change notifications is available in the VNF.
- ... Reference: Clause 8.4.7.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.7.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
@@ -24,7 +24,7 @@ Supported Indicators Change Notification
... Test title: Supported Indicators Change Notification
... Test objective: The objective is to test that the POST request triggers Supported Indicators Change Notification .
... Pre-conditions: A VNF is instantiated, and a subscription for supported indicators change notifications is available in the VNF.
- ... Reference: Clause 8.4.7.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.7.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
@@ -36,7 +36,7 @@ Test the Notification Endpoint - Successful
... Test title: Test the Notification Endpoint - Successful
... Test objective: The objective is to test the Notification Endpoint provided by the notification consumer.
... Pre-conditions: A notification endpoint is provided by the API consumer upon subscription.
- ... Reference: Clause 8.4.7.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.7.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
@@ -48,7 +48,7 @@ Test the Notification Endpoint - NOT FOUND
... Test title: Test the Notification Endpoint - UNREACHABLE
... Test objective: The objective is to test the Notification Endpoint provided by the notification consumer.
... Pre-conditions: A notification endpoint is provided by the API consumer upon subscription.
- ... Reference: Clause 8.4.7.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.7.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: The notification endpoint is unreachable by the API producer.
... Post-Conditions: none
@@ -61,7 +61,7 @@ PUT Notification endpoint - Method Not Implemented
... Test title: PUT Notification endpoint - Method Not Implemented
... Test objective: The objective is to test the PUT method for Notification Endpoint provided by the consumer is not implemented.
... Pre-conditions: A notification endpoint is provided by the API consumer upon subscription.
- ... Reference: Clause 8.4.7.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.7.3.3 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
@@ -73,7 +73,7 @@ PATCH Notification endpoint - Method Not Implemented
... Test title: PATCH Notification endpoint - Method Not Implemented
... Test objective: The objective is to test the PATCH method for Notification Endpoint provided by the consumer is not implemented.
... Pre-conditions: A notification endpoint is provided by the API consumer upon subscription.
- ... Reference: Clause 8.4.7.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.7.3.4 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
@@ -85,7 +85,7 @@ DELETE Notification endpoint - Method Not Implemented
... Test title: DELETE Notification endpoint - Method Not Implemented
... Test objective: The objective is to test the DELETE method for Notification Endpoint provided by the consumer is not implemented.
... Pre-conditions: A notification endpoint is provided by the API consumer upon subscription.
- ... Reference: Clause 8.4.7.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.7.3.5 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
diff --git a/SOL002/VNFIndicatorNotification-API/Notifications.robot b/SOL002/VNFIndicator-API/Notifications.robot
similarity index 98%
rename from SOL002/VNFIndicatorNotification-API/Notifications.robot
rename to SOL002/VNFIndicator-API/Notifications.robot
index 2a5b9f47f0a05947f8f654424b844195971d052c..140771bb7aece012602b5521bfd0c08baf4f3af8 100644
--- a/SOL002/VNFIndicatorNotification-API/Notifications.robot
+++ b/SOL002/VNFIndicator-API/Notifications.robot
@@ -16,7 +16,7 @@ VNF Indicator Value Change Notification
... Test title: VNF Indicator Value Change Notification
... Test objective: The objective is to test the dispatch of VNF Indicator Value Change Notification when new indicator values are available in the VNF, and perform a JSON schema and content validation of the delivered notification. The action that triggers the notification under test is an explicit test step, but it is not performed by the test system.
... Pre-conditions: A VNF is instantiated, and a subscription for indicator value change notifications is available in the VNF.
- ... Reference: Clause 8.4.7.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.7.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNF
... Applicability: none
... Post-Conditions: none
@@ -29,7 +29,7 @@ Supported Indicators Change Notification
... Test title: Supported Indicators Change Notification
... Test objective: The objective is to test the dispatch of Supported Indicators Change Notification when new indicator values are available in the VNF, and perform a JSON schema and content validation of the delivered notification. The action that triggers the notification under test is an explicit test step, but it is not performed by the test system.
... Pre-conditions: A VNF is instantiated, and a subscription for supported indicators change notifications is available in the VNF.
- ... Reference: Clause 8.4.7.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.7.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNF
... Applicability: none
... Post-Conditions: none
diff --git a/SOL002/VNFIndicator-API/Subscriptions.robot b/SOL002/VNFIndicator-API/Subscriptions.robot
index 80b7bdbf3bc15222bf3a2a3cbd09dce57f00aee4..f837e00e2dd25f70e7c276efb5da81fc0a4413ef 100644
--- a/SOL002/VNFIndicator-API/Subscriptions.robot
+++ b/SOL002/VNFIndicator-API/Subscriptions.robot
@@ -16,7 +16,7 @@ GET VNF Indicators Subscriptions
... Test title: GET VNF Indicators Subscriptions
... Test objective: The objective is to test the retrieval of all VNF indicators subscriptions and perform a JSON schema validation of the returned subscriptions data structure
... Pre-conditions: A VNF instance is instantiated. At least one VNF indicator subscription is available in the VNF.
- ... Reference: Clause 8.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation and maintenance of indicators
... Post-Conditions: none
@@ -29,7 +29,7 @@ GET VNF Indicators Subscriptions with attribute-based filter
... Test title: GET VNF Indicators Subscriptions with attribute-based filter
... Test objective: The objective is to test the retrieval of all VNF indicators subscriptions using attribute-based filter and perform a JSON schema and content validation of the returned subscriptions data structure
... Pre-conditions: A VNF instance is instantiated. At least one VNF indicator subscription is available in the VNF.
- ... Reference: Clause 8.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation and maintenance of indicators
... Post-Conditions: none
@@ -43,7 +43,7 @@ GET VNF Indicators Subscriptions with invalid attribute-based filter
... Test title: GET VNF Indicators Subscriptions with invalid attribute-based filter
... Test objective: The objective is to test that the retrieval of all VNF indicators subscriptions fails when using invalid attribute-based filter. The test also checks the JSON schema of the unsuccessful operation HTTP response.
... Pre-conditions: A VNF instance is instantiated. At least one VNF indicator subscription is available in the VNF.
- ... Reference: Clause 8.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation and maintenance of indicators
... Post-Conditions: none
@@ -56,7 +56,7 @@ GET VNF Indicators Subscriptions with invalid resource endpoint
... Test title: GET VNF Indicators Subscriptions with invalid resource endpoint
... Test objective: The objective is to test that the retrieval of all VNF indicators subscriptions fails when using invalid resource endpoint.
... Pre-conditions: A VNF instance is instantiated. At least one VNF indicator subscription is available in the VNF.
- ... Reference: Clause 8.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation and maintenance of indicators.
... Post-Conditions: none
@@ -69,7 +69,7 @@ Create new VNF indicator subscription
... Test title: Create new VNF indicator subscription
... Test objective: The objective is to test the creation of a new VNF indicator subscription perform a JSON schema and content validation of the returned subscriptions data structure
... Pre-conditions: A VNF instance is instantiated.
- ... Reference: Clause 8.4.5.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.5.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation and maintenance of indicators.
... Post-Conditions: The VNF indicator subscription is successfully set and it matches the issued subscription
@@ -84,7 +84,7 @@ PUT VNF Indicator Subscriptions - Method not implemented
... Test title: PUT VNF Indicator Subscriptions - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to modify VNF indicator subscriptions
... Pre-conditions: none
- ... Reference: Clause 8.4.5.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.5.3.3 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation and maintenance of indicators.
... Post-Conditions: none
@@ -96,7 +96,7 @@ PATCH VNF Indicator Subscriptions - Method not implemented
... Test title: PATCH VNF Indicator Subscriptions - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update VNF indicator subscriptions
... Pre-conditions: none
- ... Reference: Clause 8.4.5.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.5.3.4 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation and maintenance of indicators.
... Post-Conditions: none
@@ -108,7 +108,7 @@ DELETE VNF Indicator Subscriptions - Method not implemented
... Test title: DELETE VNF Indicator Subscriptions - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to delete VNF indicator subscriptions
... Pre-conditions: none
- ... Reference: Clause 8.4.5.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.5.3.5 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation and maintenance of indicators.
... Post-Conditions: none
@@ -120,7 +120,7 @@ GET VNF Indicators Subscriptions to get Paged Response
... Test title: GET VNF Indicators Subscriptions to get Paged Response
... Test objective: The objective is to test the retrieval of all VNF indicators subscriptions to get Paged Response.
... Pre-conditions: A VNF instance is instantiated. At least one VNF indicator subscription is available in the VNF.
- ... Reference: Clause 8.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation and maintenance of indicators
... Post-Conditions: none
@@ -133,7 +133,7 @@ GET VNF Indicators Subscriptions - Bad Request Response too Big
... Test title: GET VNF Indicators Subscriptions - Bad Request Response too Big
... Test objective: The objective is to test that the retrieval of all VNF indicators subscriptions fails because response is too big. The test also checks the JSON schema of the unsuccessful operation HTTP response.
... Pre-conditions: A VNF instance is instantiated. At least one VNF indicator subscription is available in the VNF.
- ... Reference: Clause 8.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation and maintenance of indicators
... Post-Conditions: none
@@ -141,16 +141,16 @@ GET VNF Indicators Subscriptions - Bad Request Response too Big
Check HTTP Response Status Code Is 400
Check HTTP Response Body Json Schema Is ProblemDetails
-POST Create a new Subscription - Unprocessable Entity
+POST Create a new Subscription - Unprocessable Content
[Documentation] Test ID: 6.3.2.4.11
- ... Test title: POST Create a new Subscription - Unprocessable Entity
- ... Test objective: The objective is to test that 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.
+ ... Test title: POST Create a new Subscription - Unprocessable Content
+ ... Test objective: The objective is to test that content type of the message content is supported and the message content of a request contains syntactically correct data but the data cannot be processed.
... Pre-conditions: none
- ... Reference: Clause 8.4.5.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.5.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
- Send Post Request for VNF Indicator Subscription with unprocessable entity
+ Send Post Request for VNF Indicator Subscription with unprocessable content
Check HTTP Response Status Code Is 422
Check HTTP Response Body Json Schema Is ProblemDetails
@@ -159,7 +159,7 @@ Create new VNF indicator Subscription - DUPLICATION
... Test title: POST Create a new subscription - DUPLICATION
... Test objective: The POST method creates a new subscription even if an existing subscription to same content exist
... Pre-conditions: none
- ... Reference: Clause 8.4.5.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.5.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: SUT should support duplication of subscription creation
... Post-Conditions: In response header Location shall not be null
@@ -173,7 +173,7 @@ Create new VNF indicator Subscription - NO-DUPLICATION
... Test title: POST Create a new subscription - NO-DUPLICATION
... Test objective: The POST method creates a new subscription even if an existing subscription to same content exist
... Pre-conditions: none
- ... Reference: Clause 8.4.5.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.5.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: SUT should not support duplication of subscription creation
... Post-Conditions: In response header Location shall not be null
@@ -233,7 +233,7 @@ Send Post Request for VNF Indicator Subscription
#Run Keyword If ${NFVO_CHECKS_NOTIF_ENDPOINT} == 1 #removed as the check of notif endpoint is done by NFVO while processing subscription reques
#... Check Notification Endpoint
-Send Post Request for VNF Indicator Subscription with unprocessable entity
+Send Post Request for VNF Indicator Subscription with unprocessable content
Log Trying to create a new subscription
Set Headers {"Accept": "${ACCEPT_JSON}"}
Set Headers {"Content-Type": "${CONTENT_TYPE_JSON}"}
diff --git a/SOL002/VNFIndicator-API/VNFIndicators.robot b/SOL002/VNFIndicator-API/VNFIndicators.robot
index 219ecabc60f2f139bc0c5470c1dd501f53c18ce3..6d5d5d98d2b1354a69205682431adb5183b8f919 100644
--- a/SOL002/VNFIndicator-API/VNFIndicators.robot
+++ b/SOL002/VNFIndicator-API/VNFIndicators.robot
@@ -12,7 +12,7 @@ Get all VNF Indicators
... Test title: Get all VNF Indicators
... Test objective: The objective is to test the retrieval of all the available VNF indicators and perform a JSON schema validation of the collected indicators data structure
... Pre-conditions: A VNF instance is instantiated. One or more measures of VNF performance indicators are available in the VNF.
- ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation and maintenance of performance indicators.
... Post-Conditions: none
@@ -25,7 +25,7 @@ Get VNF Indicators with attribute-based filter
... Test title: Get VNF Indicators with attribute-based filter
... Test objective: The objective is to test the retrieval of VNF indicators using attribute-based filter, perform a JSON schema validation of the collected indicators data structure, and verify that the retrieved information matches the issued attribute-based filters
... Pre-conditions: A VNF instance is instantiated. One or more measures of VNF performance indicators are available in the VNF.
- ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation and maintenance of performance indicators.
... Post-Conditions: none
@@ -39,7 +39,7 @@ Get VNF Indicators with invalid attribute-based filter
... Test title: Get VNF Indicators with invalid attribute-based filter
... Test objective: The objective is to test that the retrieval of VNF indicators fails when using invalid attribute-based filters, and perform the JSON schema validation of the failed operation HTTP response.
... Pre-conditions: A VNF instance is instantiated. One or more measures of VNF performance indicators are available in the VNF.
- ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation and maintenance of performance indicators.
... Post-Conditions: none
@@ -52,7 +52,7 @@ Get all VNF Indicators with malformed authorization token
... Test title: GET all VNF Indicators with malformed authrization token.
... Test objective: The objective is to test that the retrieval of VNF indicators fails when using malformed authorization token
... Pre-conditions: A VNF instance is instantiated. One or more measures of VNF performance indicators are available in the VNF.
- ... Reference: Clause 4.5.3.3, 8.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 4.5.3.3, 8.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation and maintenance of performance indicators. The VNF requires the usage of access tokens for authorizing the API requests.
... Post-Conditions: none
@@ -65,7 +65,7 @@ Get all VNF Indicators without authorization token
... Test title: GET all VNF Indicators without authorization token
... Test objective: The objective is to test that the retrieval of VNF indicators fails when omitting the authorization token
... Pre-conditions: A VNF instance is instantiated. One or more measures of VNF performance indicators are available in the VNF.
- ... Reference: Clause 4.5.3.3, 8.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 4.5.3.3, 8.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation and maintenance of performance indicators. The VNF requires the usage of access tokens for authorizing the API requests.
... Post-Conditions: none
@@ -78,7 +78,7 @@ GET all VNF Indicators with expired or revoked authorization token
... Test title: GET all VNF Indicators with expired or revoked authorization token
... Test objective: The objective is to test that the retrieval of VNF indicators fails when using expired or revoked authorization token
... Pre-conditions: A VNF instance is instantiated. One or more measures of VNF performance indicators are available in the VNF.
- ... Reference: Clause 4.5.3.3, 8.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 4.5.3.3, 8.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation and maintenance of performance indicators. The VNF requires the usage of access tokens for authorizing the API requests.
... Post-Conditions: none
@@ -91,7 +91,7 @@ Get all VNF Indicators with invalid resource endpoint
... Test title: GET all VNF Indicators with invalid resource endpoint
... Test objective: The objective is to test that the retrieval of VNF indicators fails when using invalid resource endpoint
... Pre-conditions: A VNF instance is instantiated. One or more measures of VNF performance indicators are available in the VNF.
- ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation and maintenance of performance indicators.
... Post-Conditions: none
@@ -104,7 +104,7 @@ POST all VNF Indicators - Method not implemented
... Test title: POST all VNF Indicators - Method not implemented
... Test objective: The objective is to test that POST method is not allowed to create new VNF indicators
... Pre-conditions: none
- ... Reference: Clause 8.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation and maintenance of performance indicators.
... Post-Conditions: none
@@ -116,7 +116,7 @@ PUT all VNF Indicators - Method not implemented
... Test title: PUT all VNF Indicators - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to modify VNF indicators
... Pre-conditions: none
- ... Reference: Clause 8.4.2.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.2.3.3 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation and maintenance of performance indicators.
... Post-Conditions: none
@@ -128,7 +128,7 @@ PATCH all VNF Indicators - Method not implemented
... Test title: PATCH all VNF Indicators - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update VNF indicators
... Pre-conditions: none
- ... Reference: Clause 8.4.2.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.2.3.4 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation and maintenance of performance indicators.
... Post-Conditions: none
@@ -140,7 +140,7 @@ DELETE all VNF Indicators - Method not implemented
... Test title: DELETE all VNF Indicators - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to delete VNF indicators
... Pre-conditions: none
- ... Reference: Clause 8.4.2.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.2.3.5 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation and maintenance of performance indicators.
... Post-Conditions: none
@@ -152,7 +152,7 @@ Get VNF Indicators to get Paged Response
... Test title: Get VNF Indicators to get Paged Response
... Test objective: The objective is to test the retrieval of all the available VNF indicators with Paged Response.
... Pre-conditions: A VNF instance is instantiated. One or more measures of VNF performance indicators are available in the VNF.
- ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation and maintenance of performance indicators.
... Post-Conditions: none
@@ -165,7 +165,7 @@ Get VNF Indicators - Bad Request Response too Big
... Test title: Get VNF Indicators - Bad Request Response too Big
... Test objective: The objective is to test that the retrieval of VNF indicators fails when response is too big, and perform the JSON schema validation of the failed operation HTTP response.
... Pre-conditions: A VNF instance is instantiated. One or more measures of VNF performance indicators are available in the VNF.
- ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation and maintenance of performance indicators.
... Post-Conditions: none
diff --git a/SOL002/VNFIndicator-API/VnfIndicatorsInVnfInstanceId.robot b/SOL002/VNFIndicator-API/VnfIndicatorsInVnfInstanceId.robot
index f5779bbe236323071ebb46067553d539f329e651..719a3fb0f8373cdbbc9237929832befcf7eb711a 100644
--- a/SOL002/VNFIndicator-API/VnfIndicatorsInVnfInstanceId.robot
+++ b/SOL002/VNFIndicator-API/VnfIndicatorsInVnfInstanceId.robot
@@ -12,7 +12,7 @@ Get Indicators for VNF Instance
... Test title: Get all performance indicators for a VNF instance
... Test objective: The objective is to test the retrieval of all performance indicators for a given VNF instance and perform a JSON schema validation of the returned indicators data structure
... Pre-conditions: A VNF instance is instantiated. One or more measures of performance indicators are available for the given VNF instance.
- ... Reference: Clause 8.4.3.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.3.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation and maintenance of performance indicators
... Post-Conditions: none
@@ -26,7 +26,7 @@ GET Indicators for VNF Instance with attribute-based filter
... Test title: Get all performance indicators for a VNF instance with attribute-based filter
... Test objective: The objective is to test the retrieval of all performance indicators for a given VNF instance using attribute-based filter and perform a JSON schema validation of the returned indicators data structure
... Pre-conditions: A VNF instance is instantiated. One or more measures of performance indicators are available for the given VNF instance.
- ... Reference: Clause 8.4.3.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.3.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation and maintenance of performance indicators
... Post-Conditions: none
@@ -40,7 +40,7 @@ Get Indicators for VNF Instance with invalid attribute-based filter
... Test title: Get all performance indicators for a VNF instance with invalid attribute-based filter
... Test objective: The objective is to test that the retrieval of all performance indicators for a given VNF instance fails using invalid attribute-based filter. The test also checks the JSON schema of the unsuccessful operation HTTP response.
... Pre-conditions: A VNF instance is instantiated. One or more measures of performance indicators are available for the given VNF instance.
- ... Reference: Clause 8.4.3.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.3.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation and maintenance of performance indicators.
... Post-Conditions: none
@@ -53,7 +53,7 @@ Get Indicators for VNF Instance with invalid resource identifier
... Test title: Get all performance indicators for a VNF instance with invalid resource identifier
... Test objective: The objective is to test that the retrieval of all performance indicators for a given VNF instance fails when using invalid resource identifier. The test also checks the JSON schema of the unsuccessful operation HTTP response.
... Pre-conditions: A VNF instance is instantiated. One or more measures of performance indicators are available for the given VNF instance.
- ... Reference: Clause 8.4.3.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.3.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation and maintenance of performance indicators.
... Post-Conditions: none
@@ -66,7 +66,7 @@ POST Indicators for VNF instance - Method not implemented
... Test title: POST performance indicators for VNF instance - Method not implemented
... Test objective: The objective is to test that POST method is not allowed to create new performance indicators for a VNF instance
... Pre-conditions: none
- ... Reference: Clause 8.4.3.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.3.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation and maintenance of performance indicators.
... Post-Conditions: none
@@ -78,7 +78,7 @@ PUT Indicators for VNF instance - Method not implemented
... Test title: PUT performance indicators for VNF instance - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to modify existing performance indicators for a VNF instance
... Pre-conditions: none
- ... Reference: Clause 8.4.3.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.3.3.3 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation and maintenance of performance indicators.
... Post-Conditions: none
@@ -90,7 +90,7 @@ PATCH Indicators for VNF instance - Method not implemented
... Test title: PATCH performance indicators for VNF instance - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update existing performance indicators for a VNF instance
... Pre-conditions: none
- ... Reference: Clause 8.4.3.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.3.3.4 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation and maintenance of performance indicators.
... Post-Conditions: none
@@ -102,7 +102,7 @@ DELETE Indicators for VNF instance - Method not implemented
... Test title: DELETE performance indicators for VNF instance - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to delete performance indicators for a VNF instance
... Pre-conditions: none
- ... Reference: Clause 8.4.3.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.3.3.5 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation and maintenance of performance indicators.
... Post-Conditions: none
@@ -114,7 +114,7 @@ Get Indicators for VNF Instance to get Paged Response
... Test title: Get Indicators for VNF Instance to get Paged Response
... Test objective: The objective is to test the retrieval of all performance indicators for a given VNF instance to get paged response.
... Pre-conditions: A VNF instance is instantiated. One or more measures of performance indicators are available for the given VNF instance.
- ... Reference: Clause 8.4.3.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.3.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation and maintenance of performance indicators
... Post-Conditions: none
@@ -127,7 +127,7 @@ Get Indicators for VNF Instance - Bad Request Response too Big
... Test title: Get Indicators for VNF Instance - Bad Request Response too Big
... Test objective: The objective is to test that the retrieval of all performance indicators for a given VNF instance fails when response is too big. The test also checks the JSON schema of the unsuccessful operation HTTP response.
... Pre-conditions: A VNF instance is instantiated. One or more measures of performance indicators are available for the given VNF instance.
- ... Reference: Clause 8.4.3.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 8.4.3.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation and maintenance of performance indicators.
... Post-Conditions: none
diff --git a/SOL002/VNFIndicator-API/environment/variables.txt b/SOL002/VNFIndicator-API/environment/variables.txt
index 038ce1412da59a0d8b8732a1fdfcdb998e299409..69e6b434993a3e4fd70ef161f55b2397886b34a8 100644
--- a/SOL002/VNFIndicator-API/environment/variables.txt
+++ b/SOL002/VNFIndicator-API/environment/variables.txt
@@ -20,6 +20,12 @@ ${callback_uri} http://localhost
${callback_port} 9091
${callback_endpoint} /endpoint
+${callback_endpoint_fwd} /endpoint/check
+${callback_endpoint_error} /endpoint_404
+
+${notification_request} []
+${notification_response} []
+
${unreachable_callback_uri} http://not-reachable-uri
${response} some_response_object
diff --git a/SOL002/VNFIndicatorNotification-API/schemas/VnfIndicatorValueChangeNotification.schema.json b/SOL002/VNFIndicator-API/schemas/VnfIndicatorValueChangeNotification.schema.json
similarity index 100%
rename from SOL002/VNFIndicatorNotification-API/schemas/VnfIndicatorValueChangeNotification.schema.json
rename to SOL002/VNFIndicator-API/schemas/VnfIndicatorValueChangeNotification.schema.json
diff --git a/SOL002/VNFIndicatorNotification-API/README.md b/SOL002/VNFIndicatorNotification-API/README.md
deleted file mode 100644
index f5f7677f55fcf78e1846a4ff3f61fb4cdef215c3..0000000000000000000000000000000000000000
--- a/SOL002/VNFIndicatorNotification-API/README.md
+++ /dev/null
@@ -1,12 +0,0 @@
-# NFV API Tests
-
-This is a development folder for ETSI STF 557.
-It includes the NFV API conformance test descriptions.
-
-## License
-
-Any software in this repository is released under the ETSI Software License.
-Licensing information is available in the attached LICENSE file.
-
-
-Copyright (c) ETSI 2018
diff --git a/SOL002/VNFIndicatorNotification-API/environment/variables.txt b/SOL002/VNFIndicatorNotification-API/environment/variables.txt
deleted file mode 100644
index 17e51a3f740921ced9f9fd7c6ad2a159568e0105..0000000000000000000000000000000000000000
--- a/SOL002/VNFIndicatorNotification-API/environment/variables.txt
+++ /dev/null
@@ -1,13 +0,0 @@
-*** Variables ***
-${callback_uri} http://localhost
-${callback_port} 9091
-${callback_endpoint} /endpoint
-${callback_endpoint_fwd} /endpoint/check
-${callback_endpoint_error} /endpoint_404
-${total_polling_time} 2 min
-${polling_interval} 10 sec
-
-${notification_request} []
-${notification_response} []
-
-${MOCK_SERVER_JAR} ../../../bin/mockserver-netty-5.5.0-jar-with-dependencies.jar
\ No newline at end of file
diff --git a/SOL002/VNFLCMCoordination-API/ApiVersion.robot b/SOL002/VNFLCMCoordination-API/ApiVersion.robot
index 8c23db3fe641f20aee540463bb68a3a69c9c6a43..0939a189f9728a6cf9df7c34bf90339d8df9abdd 100644
--- a/SOL002/VNFLCMCoordination-API/ApiVersion.robot
+++ b/SOL002/VNFLCMCoordination-API/ApiVersion.robot
@@ -14,7 +14,7 @@ POST API Version - Method not implemented
... Test title: POST API version - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -26,7 +26,7 @@ GET API Version
... Test title: GET API Version
... Test objective: The objective is to test that GET method successfully return ApiVersionInformation
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -39,7 +39,7 @@ PUT API Version - Method not implemented
... Test title: PUT API Version - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -51,7 +51,7 @@ PATCH API Version - Method not implemented
... Test title: PATCH API Version - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -63,7 +63,7 @@ DELETE API Version - Method not implemented
... Test title: DELETE API Version - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -75,7 +75,7 @@ POST API Version with apiMajorVerion - Method not implemented
... Test title: POST API version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -87,7 +87,7 @@ GET API Version with apiMajorVerion
... Test title: GET API Version with apiMajorVerion
... Test objective: The objective is to test that GET method successfully return ApiVersionInformation
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -100,7 +100,7 @@ PUT API Version with apiMajorVerion - Method not implemented
... Test title: PUT API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -112,7 +112,7 @@ PATCH API Version with apiMajorVerion - Method not implemented
... Test title: PATCH API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -124,7 +124,7 @@ DELETE API Version with apiMajorVerion - Method not implemented
... Test title: DELETE API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
diff --git a/SOL002/VNFLCMCoordination-API/CancelCoordinationActionTask.robot b/SOL002/VNFLCMCoordination-API/CancelCoordinationActionTask.robot
index 8f84fa1bd59ac08cdb3c914e103a183640bb1713..7ec37111c8f1aa05499de69b5926372cf1ca7af8 100644
--- a/SOL002/VNFLCMCoordination-API/CancelCoordinationActionTask.robot
+++ b/SOL002/VNFLCMCoordination-API/CancelCoordinationActionTask.robot
@@ -15,7 +15,7 @@ POST Cancellation of an Ongoing Individual Coordination Action
... Test title: POST Cancellation of an Ongoing Individual Coordination Action
... Test Objective: The objective is to test that POST request for cancellation of an ongoing individual coordination Action has accepted for processing.
... pre-condition: The status of the related LCM operation occurance is "PROCESSING"
- ... Reference: Clause 10.4.4.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 10.4.4.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: When there is an Ongoing individual LCM operation coordination action.
... Post-Condition: none
@@ -28,7 +28,7 @@ POST Cancellation of an Ongoing Individual Coordination Action - Conflict
... Test title: POST Cancellation of an Ongoing Individual Coordination Action - Conflict
... Test Objective: The objective is to test that POST request for cancellation of an ongoing individual coordination Action is not successfull due to a conflict with the state of the "Individual coordination action" resource.
... pre-condition: none
- ... Reference: Clause 10.4.4.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 10.4.4.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: Processing of Individual Coordination Action has 'Finished'.
... Post-Condition: none
@@ -41,7 +41,7 @@ Request a cancellation of an ongoing coordination action without authentication
... Test title: Request a cancellation of an ongoing coordination action without authentication
... Test objective: The objective is to test the failure of the request for a cancellation of a coordination task when no authentication is used
... Pre-conditions: none
- ... Reference: Clause Clause 10.4.4.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause Clause 10.4.4.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -53,7 +53,7 @@ GET Cancellation of an Ongoing Individual Coordination Action - Method not Imple
... Test title: GET Cancellation of an Ongoing Individual Coordination Action
... Test Objective: The objective is to test that GET method for cancellation of an ongoing individual coordination Action is not implemented.
... pre-condition: none
- ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: ongoing individual coordination
... Post-Condition: none
@@ -65,7 +65,7 @@ PUT Cancellation of an Ongoing Individual Coordination Action - Method not Imple
... Test title: PUT Cancellation of an Ongoing Individual Coordination Action
... Test Objective: The objective is to test that PUT method for cancellation of an ongoing individual coordination Action is not implemented.
... pre-condition: none
- ... Reference: Clause 10.4.4.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 10.4.4.3.3 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Condition: none
@@ -77,7 +77,7 @@ PATCH Cancellation of an Ongoing Individual Coordination Action - Method not Imp
... Test title: PATCH Cancellation of an Ongoing Individual Coordination Action
... Test Objective: The objective is to test that PATCH method for cancellation of an ongoing individual coordination Action is not implemented.
... pre-condition: none
- ... Reference: Clause 10.4.4.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 10.4.4.3.4 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Condition: none
@@ -89,7 +89,7 @@ DELETE Cancellation of an Ongoing Individual Coordination Action - Method not Im
... Test title: DELETE Cancellation of an Ongoing Individual Coordination Action
... Test Objective: The objective is to test that DELETE method for cancellation of an ongoing individual coordination Action is not implemented.
... pre-condition: none
- ... Reference: Clause 10.4.4.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 10.4.4.3.5 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Condition: none
diff --git a/SOL002/VNFLCMCoordination-API/Coordinations.robot b/SOL002/VNFLCMCoordination-API/Coordinations.robot
index 8020da914796eaa61eb8f30517e0aa2843943fe2..3913b947f404e5fd81ac4696339cad2dde22d8db 100644
--- a/SOL002/VNFLCMCoordination-API/Coordinations.robot
+++ b/SOL002/VNFLCMCoordination-API/Coordinations.robot
@@ -15,7 +15,7 @@ POST Coordination of LCM Operation Occurance and API Producer has Chosen the Syn
... Test title: Post Coordination of an LCM operation occurrence
... Test Objective: The objective is to test the creation of new Individual Coordination Action, and perform a JSON schema validation of the returned LCM coordination data structure.
... pre-condition: LCM operation occurrence resource is in Processing state
- ... Reference: Clause 10.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 10.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: API producer has chosen the synchronous mode
... Post-Condition: none
@@ -30,7 +30,7 @@ POST Coordination of LCM Operation Occurance and API Producer has Chosen the Asy
... Test title: Post Coordination of an LCM operation occurrence
... Test Objective: The objective is to test that the coordination of a LCM operation occurance request has been accepted for processing, and perform a JSON schema validation of the returned LCM coordination data structure.
... pre-condition: LCM operation occurrence resource is in Processing state
- ... Reference: Clause 10.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 10.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: API producer has chosen the asynchronous mode
... Post-Condition: none
@@ -44,7 +44,7 @@ POST Coordination of a LCM Operation Occurance Forbidden
... Test title: Post Coordination of an LCM operation occurrence Forbidden
... Test Objective: The objective is to test the failure of a request for the coordination of an LCM operation occurrence
... pre-condition: The status of the related LCM opeation occurrence is "PROCESSING". The request is performed by a user that has not the grant to run this operation
- ... Reference: Clause 10.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 10.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Condition: none
@@ -57,7 +57,7 @@ POST Coordination of LCM Operation Occurance Conflict
... Test title: Post Coordination of an LCM operation occurrence Conflict
... Test Objective: The objective is to verify that no coordination actions can be executed currently, due to a conflict with the state of the "Coordinations" resource.
... pre-condition: The status of the related LCM opeation occurrence is not "PROCESSING"
- ... Reference: Clause 10.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 10.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: When there are many coordination actions exist, or conflicting ones, are in progress.
... Post-Condition: none
@@ -70,7 +70,7 @@ POST Coordination of LCM Operation Occurance Service Unavailable
... Test title: Post Coordination of an LCM operation occurrence Service Unavailable
... Test Objective: The objective is to test the request for the coordination of an LCM operation occurrence and the verify that the NFVO cannot perform immediately the request, but can perform it sometime in the future.
... pre-condition: The status of the related LCM opeation occurrence is "PROCESSING" but API producer cannot perform immediately the request
- ... Reference: Clause 10.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 10.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: API producer has chosen the synchronous mode
... Post-Condition: none
@@ -84,7 +84,7 @@ POST Coordination of an LCM operation occurrence without authentication
... Test title: Request a Coordination of an LCM operation occurrence without authentication
... Test objective: The objective is to test the failure of the request for the coordination of an LCM operation occurrence without providing an authentication token
... Pre-conditions: The status of the related LCM opeation occurrence is "PROCESSING"
- ... Reference: Clause 10.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 10.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -96,7 +96,7 @@ GET Coordination of a LCM Operation Occurance - Method not implemented
... Test title: GET Coordination of a LCM Operation Occurance - Method not implemented
... Test Objective: The objective is to test that GET method for Resource Coordinations is not implemented.
... pre-condition: none
- ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Condition: none
@@ -108,7 +108,7 @@ PUT Coordination of a LCM Operation Occurance - Method not implemented
... Test title: PUT Coordination of a LCM Operation Occurance - Method not implemented
... Test Objective: The objective is to test that PUT method for Resource Coordinations is not implemented.
... pre-condition: none
- ... Reference: Clause 10.4.2.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 10.4.2.3.3 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Condition: none
@@ -120,7 +120,7 @@ PACTH Coordination of a LCM Operation Occurance - Method not implemented
... Test title: PATCH Coordination of a LCM Operation Occurance - Method not implemented
... Test Objective: The objective is to test that PATCH method for Resource Coordinations is not implemented.
... pre-condition: none
- ... Reference: Clause 10.4.2.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 10.4.2.3.4 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Condition: none
@@ -132,7 +132,7 @@ DELETE Coordination of a LCM Operation Occurance - Method not implemented
... Test title: DELETE Coordination of a LCM Operation Occurance - Method not implemented
... Test Objective: The objective is to test that DELETE method for Resource Coordinations is not implemented.
... pre-condition: none
- ... Reference: Clause 10.4.2.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 10.4.2.3.5 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Condition: none
diff --git a/SOL002/VNFLCMCoordination-API/IndividualCoordinationAction.robot b/SOL002/VNFLCMCoordination-API/IndividualCoordinationAction.robot
index 871540dac54629527625c04dc0f9b6f4f264922c..21d27d13af00f02878ea6b66bbd4f552d243f9e1 100644
--- a/SOL002/VNFLCMCoordination-API/IndividualCoordinationAction.robot
+++ b/SOL002/VNFLCMCoordination-API/IndividualCoordinationAction.robot
@@ -14,7 +14,7 @@ POST Individual LCM Operation Coordination Results - Method not implemented
... Test title: POST Individual LCM Operation Coordination Results - Method not implemented
... Test Objective: The objective is to test that POST method for individual LCM operation coordination results is not implemented.
... pre-condition: none
- ... Reference: Clause 10.4.3.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 10.4.3.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Condition: none
@@ -26,7 +26,7 @@ GET Individual LCM Operation Coordination Results - Coordination is Finished
... Test title: GET Individual LCM Operation Coordination Results
... Test Objective: The objective is to test that coordination is finished and GET method reads individual LCM operation coordination results successfully, and perform a JSON schema validation of the returned LCM coordination data structure.
... pre-condition: LCM operation occurrence resource is in Processing state
- ... Reference: Clause 10.4.3.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 10.4.3.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: When the Individual LCM Operation Coordination is finished
... Post-Condition: none
@@ -39,7 +39,7 @@ GET Individual LCM Operation Coordination Results - Coordination is Not Finished
... Test title: GET Individual LCM Operation Coordination Results
... Test Objective: The objective is to test that GET method checks that whether Individual LCM Operation Coordination is still ongoing or in the process of being cancelled.
... pre-condition: LCM operation occurrence resource is in Processing state
- ... Reference: Clause 10.4.3.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 10.4.3.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: When the Individual LCM Operation Coordination is still ongoing or in the process of being cancelled.
... Post-Condition: none
@@ -52,7 +52,7 @@ Get Individual LCM Operation Coordination Results without authentication
... Test title: Get information about a finished coordination task without authentication
... Test objective: The objective is to try to read an individual coordination task without using authentication
... Pre-conditions: none
- ... Reference: Clause 10.4.3.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 10.4.3.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -64,7 +64,7 @@ PUT Individual LCM Operation Coordination Results - Method not implemented
... Test title: PUT Individual LCM Operation Coordination Results - Method not implemented
... Test Objective: The objective is to test that PUT method for individual LCM operation coordination results is not implemented.
... pre-condition: none
- ... Reference: Clause 10.4.3.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 10.4.3.3.3 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Condition: none
@@ -76,7 +76,7 @@ PATCH Individual LCM Operation Coordination Results - Method not implemented
... Test title: PATCH Individual LCM Operation Coordination Results - Method not implemented
... Test Objective: The objective is to test that PATCH method for individual LCM operation coordination results is not implemented.
... pre-condition: none
- ... Reference: Clause 10.4.3.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 10.4.3.3.4 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Condition: none
@@ -88,7 +88,7 @@ DELETE Individual LCM Operation Coordination Results - Method not implemented
... Test title: PUT Individual LCM Operation Coordination Results - Method not implemented
... Test Objective: The objective is to test that DELETE method for individual LCM operation coordination results is not implemented.
... pre-condition: none
- ... Reference: Clause 10.4.3.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 10.4.3.3.5 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Condition: none
diff --git a/SOL002/VNFLifecycleManagement-API/ApiVersion.robot b/SOL002/VNFLifecycleManagement-API/ApiVersion.robot
index 0d713d4612c83e774205c352fafb885c07c35641..00c056ed261e0d476b9a2ea478d291d3dd886e10 100644
--- a/SOL002/VNFLifecycleManagement-API/ApiVersion.robot
+++ b/SOL002/VNFLifecycleManagement-API/ApiVersion.robot
@@ -11,7 +11,7 @@ POST API Version - Method not implemented
... Test title: POST API version - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -23,7 +23,7 @@ GET API Version
... Test title: GET API Version
... Test objective: The objective is to test that GET method successfully return ApiVersionInformation
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -36,7 +36,7 @@ PUT API Version - Method not implemented
... Test title: PUT API Version - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -48,7 +48,7 @@ PATCH API Version - Method not implemented
... Test title: PATCH API Version - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -60,7 +60,7 @@ DELETE API Version - Method not implemented
... Test title: DELETE API Version - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -72,7 +72,7 @@ POST API Version with apiMajorVerion - Method not implemented
... Test title: POST API version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -84,7 +84,7 @@ GET API Version with apiMajorVerion
... Test title: GET API Version with apiMajorVerion
... Test objective: The objective is to test that GET method successfully return ApiVersionInformation
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -97,7 +97,7 @@ PUT API Version with apiMajorVerion - Method not implemented
... Test title: PUT API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -109,7 +109,7 @@ PATCH API Version with apiMajorVerion - Method not implemented
... Test title: PATCH API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -121,7 +121,7 @@ DELETE API Version with apiMajorVerion - Method not implemented
... Test title: DELETE API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL002/VNFLifecycleManagement-API/CancelOperationTask.robot b/SOL002/VNFLifecycleManagement-API/CancelOperationTask.robot
index 79f0e080b7d85beeff7ec00b7a8cc8900336e23e..6ce7c7c1263a4eb84b762d7ec17df7b8eb705841 100644
--- a/SOL002/VNFLifecycleManagement-API/CancelOperationTask.robot
+++ b/SOL002/VNFLifecycleManagement-API/CancelOperationTask.robot
@@ -14,7 +14,7 @@ Post Cancel operation task
... Test title: POST Cancel operation task
... Test objective: The POST method initiates cancelling an ongoing VNF lifecycle operation while it is being executed or rolled back, i.e. the "VNF LCM operation occurrence" is either in "PROCESSING" or "ROLLING_BACK" state.
... Pre-conditions: the "VNF LCM operation occurrence" is either in "PROCESSING" or "ROLLING_BACK" state.
- ... Reference: Clause 5.4.17.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.17.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: the resource is in FAILED_TEMP state
@@ -27,7 +27,7 @@ Post Cancel operation task Conflict
... Test title: POST Cancel operation task Conflict
... Test objective: The POST method is NOT cancelling an ongoing VNF lifecycle operation due to the fact that the VNF instance resource is not in STARTING, PROCESSING or ROLLING_BACK state
... Pre-conditions: operation is not in STARTING, PROCESSING or ROLLING_BACK state
- ... Reference: Clause 5.4.17.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.17.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -41,7 +41,7 @@ Post Cancel operation task Not Found
... Test title: POST Cancel operation task
... Test objective: The objective is to test that POST method cannot cancel a VNF lifecycle operation because the resource is not found
... Pre-conditions:
- ... Reference: Clause 5.4.17.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.17.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -54,7 +54,7 @@ GET Cancel operation task - Method not implemented
... Test title: GET Cancel operation task - Method not implemented
... Test objective: The objective is to test that GET method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.17.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.17.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -66,7 +66,7 @@ PUT Cancel operation task - Method not implemented
... Test title: PUT Cancel operation task - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.17.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.17.3.3 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -78,7 +78,7 @@ PATCH Cancel operation task - Method not implemented
... Test title: PATCH Cancel operation task - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.17.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.17.3.4 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -90,7 +90,7 @@ DELETE Cancel operation task - Method not implemented
... Test title: DELETE Cancel operation task - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.17.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.17.3.5 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
diff --git a/SOL002/VNFLifecycleManagement-API/ChangeCurrentVNFPackageTask.robot b/SOL002/VNFLifecycleManagement-API/ChangeCurrentVNFPackageTask.robot
index f8e534e824eb86cd75214b1ec237293308582a00..918c3f54b557a52070519cce479c18f20eb79992 100644
--- a/SOL002/VNFLifecycleManagement-API/ChangeCurrentVNFPackageTask.robot
+++ b/SOL002/VNFLifecycleManagement-API/ChangeCurrentVNFPackageTask.robot
@@ -13,7 +13,7 @@ POST Change current VNF Package Task
... Test title: POST Change current VNF Package Task
... Test objective: The objective is to test that the POST method changes the current VNF package on which the VNF instance is based.
... Pre-conditions: none
- ... Reference: Clause 5.4.11a.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.11a.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: in response header Location shall not be null
@@ -26,7 +26,7 @@ POST Change current VNF Package Task - Conflict
... Test title: POST Change current VNF Package Task - Conflict
... Test objective: The objective is to test that the POST method cannot change the current VNF package task when another lifecycle management operation is ongoing.
... Pre-conditions: none
- ... Reference: Clause 5.4.11a.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.11a.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: There is another lifecycle management operation ongoing.
... Post-Conditions: none
@@ -39,7 +39,7 @@ GET Change current VNF Package Task - Method not implemented
... Test title: GET Change current VNF Package Task - Method not implemented
... Test objective: The objective is to test that GET method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.11a.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.11a.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -51,7 +51,7 @@ PUT Change current VNF Package Task - Method not implemented
... Test title: PUT Change current VNF Package Task - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.11a.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.11a.3.3 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -63,7 +63,7 @@ PATCH Change current VNF Package Task - Method not implemented
... Test title: PATCH Change current VNF Package Task - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.11a.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.11a.3.4 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -75,7 +75,7 @@ DELETE Change current VNF Package Task - Method not implemented
... Test title: DELETE Change current VNF Package Task - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.11a.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.11a.3.5 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
diff --git a/SOL002/VNFLifecycleManagement-API/ChangeExternalVNFConnectivityTask.robot b/SOL002/VNFLifecycleManagement-API/ChangeExternalVNFConnectivityTask.robot
index 7265d193c6c5d873e501b067383e9021b873bacf..4ea112541ad6e2d99fc8184a3663113a8002cada 100644
--- a/SOL002/VNFLifecycleManagement-API/ChangeExternalVNFConnectivityTask.robot
+++ b/SOL002/VNFLifecycleManagement-API/ChangeExternalVNFConnectivityTask.robot
@@ -13,7 +13,7 @@ POST Change external VNF connectivity
... Test title: POST Change external VNF connectivity
... Test objective: The objective is to test that POST method triggers a change in VNF external connectivity
... Pre-conditions: none
- ... Reference: Clause 5.4.11.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.11.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: in response header Location shall not be null
@@ -26,7 +26,7 @@ GET Change external VNF connectivity - Method not implemented
... Test title: GET Change external VNF connectivity - Method not implemented
... Test objective: The objective is to test that GET method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.11.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.11.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -38,7 +38,7 @@ PUT Change external VNF connectivity - Method not implemented
... Test title: PUT Change external VNF connectivity - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.11.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.11.3.3 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -50,7 +50,7 @@ PATCH Change external VNF connectivity - Method not implemented
... Test title: PATCH Change external VNF connectivity - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.11.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.11.3.4 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -62,7 +62,7 @@ DELETE Change external VNF connectivity - Method not implemented
... Test title: DELETE Change external VNF connectivity - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.11.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.11.3.5 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -74,7 +74,7 @@ POST Change external VNF connectivity Conflict
... Test title: POST Change external VNF connectivity Conflict
... Test objective: The objective is to test that the operation cannot be executed currently, due to a conflict with the state of the VNF instance resource or that a required child attribute of the "extensions" attribue has not been set.
... Pre-conditions: none
- ... Reference: Clause 5.4.11.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.11.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
diff --git a/SOL002/VNFLifecycleManagement-API/ChangeVNFFlavourTask.robot b/SOL002/VNFLifecycleManagement-API/ChangeVNFFlavourTask.robot
index 9d6c8939506867771bb6d556a5fd6e65d1d6bd81..335bd10303dddd57869ef657229f099bb2dfb62c 100644
--- a/SOL002/VNFLifecycleManagement-API/ChangeVNFFlavourTask.robot
+++ b/SOL002/VNFLifecycleManagement-API/ChangeVNFFlavourTask.robot
@@ -13,7 +13,7 @@ POST Change deployment flavour of a vnfInstance
... Test title: POST Change deployment flavour of a vnfInstance
... Test objective: The objective is to test that POST method trigger a change in VNF deployment flavour
... Pre-conditions: none
- ... Reference: Clause 5.4.7.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.7.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: in response header Location shall not be null
@@ -26,7 +26,7 @@ POST Change deployment flavour of a vnfInstance Conflict (Not-Instantiated)
... Test title: POST Change deployment flavour of a vnfInstance Conflict (Not-Instantiated)
... Test objective: The objective is to test that POST method cannot trigger a change in VNF deployment flavour because of a conflict with the state of the VNF instance resource or that a required child attribute of the "extensions" attribue has not been set.
... Pre-conditions: VNF instance resource is not in NOT-INSTANTIATED state
- ... Reference: Clause 5.4.7.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.7.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -39,7 +39,7 @@ POST Change deployment flavour of a vnfInstance Not Found
... Test title: POST Change deployment flavour of a vnfInstance Not Found
... Test objective: The objective is to test that POST method cannot trigger a change in VNF deployment flavour because the VNF instance resource is not found.
... Pre-conditions: VNF instance resource is not in NOT-INSTANTIATED state
- ... Reference: Clause 5.4.7.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.7.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -52,7 +52,7 @@ GET Change deployment flavour VNFInstance - Method not implemented
... Test title: GET Change deployment flavour VNFInstance - Method not implemented
... Test objective: The objective is to test that GET method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.7.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.7.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -64,7 +64,7 @@ PUT Change deployment flavour VNFInstance - Method not implemented
... Test title: PUT Change deployment flavour VNFInstance - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.7.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.7.3.3 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -76,7 +76,7 @@ PATCH Change deployment flavour VNFInstance - Method not implemented
... Test title: PATCH Change deployment flavour VNFInstance - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.7.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.7.3.4 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -88,7 +88,7 @@ DELETE Change deployment flavour VNFInstance - Method not implemented
... Test title: DELETE Change deployment flavour VNFInstance - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.7.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.7.3.5 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
diff --git a/SOL002/VNFLifecycleManagement-API/CreateVNFSnapshotTask.robot b/SOL002/VNFLifecycleManagement-API/CreateVNFSnapshotTask.robot
index 31d32e3f683f5bb0e32e43ababa746d0f5e31c18..4a4b644c20ea0c68abbf190a20ff4ed153dc075f 100644
--- a/SOL002/VNFLifecycleManagement-API/CreateVNFSnapshotTask.robot
+++ b/SOL002/VNFLifecycleManagement-API/CreateVNFSnapshotTask.robot
@@ -13,7 +13,7 @@ POST Create VNF Snapshot Task
... Test title: POST Create VNF Snapshot Task
... Test objective: The objective is to test that POST method requests taking a snapshot of a VNF instance.
... Pre-conditions: none
- ... Reference: Clause 5.4.21.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.21.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: in response header Location shall not be null
@@ -26,7 +26,7 @@ POST Create VNF Snapshot Task - NOT FOUND
... Test title: POST Create VNF Snapshot Task - NOT FOUND
... Test objective: The objective is to test that the POST method cannot request for a snapshot if the task is not supported for the VNF instance represented by the parent resource.
... Pre-conditions: none
- ... Reference: Clause 5.4.21.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.21.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: Task is not supported for the VNF instance represented by the parent resource.
... Post-Conditions: none
@@ -39,7 +39,7 @@ POST Create VNF Snapshot Task - CONFLICT
... Test title: POST Create VNF Snapshot Task - CONFLICT
... Test objective: The objective is to test that the POST method cannot request for a snapshot when the VNF instance is in NOT_INSTANTIATED state.
... Pre-conditions: none
- ... Reference: Clause 5.4.21.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.21.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: VNF instance is in NOT_INSTANTIATED state.
... Post-Conditions: none
@@ -47,17 +47,17 @@ POST Create VNF Snapshot Task - CONFLICT
Check HTTP Response Status Code Is 409
Check HTTP Response Body Json Schema Is ProblemDetails
-POST Create VNF Snapshot Task - UNPROCESSIBLE ENTITY
+POST Create VNF Snapshot Task - UNPROCESSABLE CONTENT
[Documentation] Test ID: 6.3.5.23.4
- ... Test title: POST Create VNF Snapshot Task - UNPROCESSIBLE ENTITY
+ ... Test title: POST Create VNF Snapshot Task - UNPROCESSABLE CONTENT
... Test objective: The objective is to test that the POST method cannot request for a snapshot when the provided identifier of the target "Individual VNF snapshot" resource for the VNF snapshot is invalid.
... Pre-conditions: none
- ... Reference: Clause 5.4.21.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.21.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: The identifier of the target "Individual VNF snapshot" resource for the VNF snapshot is invalid.
... Post-Conditions: none
POST Create VNF Snapshot Task INVALID IDENTIFIER
- Check HTTP Response Status Code Is 409
+ Check HTTP Response Status Code Is 422
Check HTTP Response Body Json Schema Is ProblemDetails
GET Create VNF Snapshot Task - Method not implemented
@@ -65,7 +65,7 @@ GET Create VNF Snapshot Task - Method not implemented
... Test title: GET Create VNF Snapshot Task - Method not implemented
... Test objective: The objective is to test that GET method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.21.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.21.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -77,7 +77,7 @@ PUT Create VNF Snapshot Task - Method not implemented
... Test title: PUT Create VNF Snapshot Task - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.21.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.21.3.3 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -89,7 +89,7 @@ PATCH Create VNF Snapshot Task - Method not implemented
... Test title: PATCH Create VNF Snapshot Task - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.21.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.21.3.4 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -101,7 +101,7 @@ DELETE Create VNF Snapshot Task - Method not implemented
... Test title: DELETE Create VNF Snapshot Task - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.21.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.21.3.5 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
diff --git a/SOL002/VNFLifecycleManagement-API/FailOperationTask.robot b/SOL002/VNFLifecycleManagement-API/FailOperationTask.robot
index 8fb44ad4662b0b59ce5223c44de5e37c6d47cd70..839a3513ef6067e17683e03ef301654a98d09782 100644
--- a/SOL002/VNFLifecycleManagement-API/FailOperationTask.robot
+++ b/SOL002/VNFLifecycleManagement-API/FailOperationTask.robot
@@ -12,7 +12,7 @@ POST Fail operation task
... Test title: POST Fail operation task
... Test objective: The objective is to test that POST method mark as "finally failed" a VNF lifecycle operation if that operation has experienced a failure
... Pre-conditions: the "VNF LCM operation occurrence" resource is in "FAILED_TEMP" state.
- ... Reference: Clause 5.4.16.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.16.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -26,7 +26,7 @@ POST Fail operation task Conflict (Not-FAILED_TEMP)
... Test title: POST Fail operation task Conflict (Not-FAILED_TEMP)
... Test objective: The objective is to test that POST method cannot mark as "finally failed" due to confilct with the state of LCM Operation Occurrence
... Pre-conditions: the "VNF LCM operation occurrence" resource is not in "FAILED_TEMP" state.
- ... Reference: Clause 5.4.16.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.16.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -39,7 +39,7 @@ POST Fail operation task Not Found
... Test title: POST Fail operation task Not Found
... Test objective: The objective is to test that POST method cannot mark as "finally failed" a VNF lifecycle operation because the operation is not supported
... Pre-conditions: none
- ... Reference: Clause 5.4.16.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.16.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -52,7 +52,7 @@ GET Fail operation task - Method not implemented
... Test title: GET Fail operation task- Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.16.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.16.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -64,7 +64,7 @@ PUT Fail operation task - Method not implemented
... Test title: PUT Fail operation task- Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.16.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.16.3.3 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -76,7 +76,7 @@ PATCH Fail operation task - Method not implemented
... Test title: PATCH Fail operation task - Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.16.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.16.3.4 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -88,7 +88,7 @@ DELETE Fail operation task - Method not implemented
... Test title: DELETE Fail operation task- Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.16.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.16.3.5 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
diff --git a/SOL002/VNFLifecycleManagement-API/HealVNFTask.robot b/SOL002/VNFLifecycleManagement-API/HealVNFTask.robot
index a4b85291afa6e175490d295099fa589d184334da..aa22bef90ab19f7f578d3b4b275eafa5a9fdaa41 100644
--- a/SOL002/VNFLifecycleManagement-API/HealVNFTask.robot
+++ b/SOL002/VNFLifecycleManagement-API/HealVNFTask.robot
@@ -13,7 +13,7 @@ POST Heal a vnfInstance
... Test title: POST Heal a vnfInstance
... Test objective: The objective is to test that POST method heal a VNF instance
... Pre-conditions: none
- ... Reference: Clause 5.4.9.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.9.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -26,7 +26,7 @@ POST Heal a vnfInstance Conflict (Not-Instantiated)
... Test title: POST Heal a vnfInstance (Not-Instantiated)
... Test objective: The objective is to test that the operation cannot be executed currently, due to a conflict with the state of the VNF instance resource or that a required child attribute of the "extensions" attribue has not been set.
... Pre-conditions: the VNF instance resource is in NOT-INSTANTIATED state
- ... Reference: Clause 5.4.9.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.9.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -40,7 +40,7 @@ POST Heal a vnfInstance Not Found
... Test title: POST Heal a vnfInstance Not Found
... Test objective: The objective is to test that the operation cannot be executed because the VNF instance resource is not found.
... Pre-conditions: the VNF instance resource is not existing
- ... Reference: Clause 5.4.9.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.9.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -53,7 +53,7 @@ GET Heal VNFInstance - Method not implemented
... Test title: GET Heal a vnfInstance - Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.9.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.9.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -65,7 +65,7 @@ PUT Heal VNFInstance - Method not implemented
... Test title: PUT Heal a vnfInstance - Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.9.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.9.3.3 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -77,7 +77,7 @@ PATCH Heal VNFInstance - Method not implemented
... Test title: PATCH Heal a vnfInstance - Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.9.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.9.3.4 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -89,7 +89,7 @@ DELETE Heal VNFInstance - Method not implemented
... Test title: DELETE Heal a vnfInstance - Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.9.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.9.3.5 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL002/VNFLifecycleManagement-API/IndividualSubscription.robot b/SOL002/VNFLifecycleManagement-API/IndividualSubscription.robot
index 332d6a0a7c2d2de6b314211cbe8c0843e631c69f..8583c4a1f99efce986abb8bca2d95b25922870a0 100644
--- a/SOL002/VNFLifecycleManagement-API/IndividualSubscription.robot
+++ b/SOL002/VNFLifecycleManagement-API/IndividualSubscription.robot
@@ -11,7 +11,7 @@ POST Individual Subscription - Method not implemented
... Test title: POST Individual Subscription - Method not implemented
... Test objective: The objective is to test that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.19.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.19.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -23,7 +23,7 @@ GET Individual Subscription
... Test title: GET Individual Subscription
... Test objective: The objective is to test the Get individual subscription
... Pre-conditions: none
- ... Reference: Clause 5.4.19.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.19.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -36,7 +36,7 @@ PUT an individual subscription - Method not implemented
... Test title: PUT Individual Subscription - Method not implemented
... Test objective: The objective is to test that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.19.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.19.3.3 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -48,7 +48,7 @@ PATCH an individual subscription - Method not implemented
... Test title: PATCH Individual Subscription - Method not implemented
... Test objective: The objective is to test that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.19.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.19.3.4 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -60,7 +60,7 @@ DELETE an individual subscription
... Test title: DELETE Individual Subscription
... Test objective: The objective is to test that the DELETE method removes an individual subscription
... Pre-conditions: none
- ... Reference: Clause 5.4.19.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.19.3.5 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
diff --git a/SOL002/VNFLifecycleManagement-API/IndividualVNFInstance.robot b/SOL002/VNFLifecycleManagement-API/IndividualVNFInstance.robot
index de4f26c868de4e7234fbc3fc7ecd565b33aec3e4..13d232bc7cec116150fee3837bb7241d625394f6 100644
--- a/SOL002/VNFLifecycleManagement-API/IndividualVNFInstance.robot
+++ b/SOL002/VNFLifecycleManagement-API/IndividualVNFInstance.robot
@@ -18,7 +18,7 @@ POST Individual VNFInstance - Method not implemented
... Test title: POST Individual VNFInstance - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.3.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.3.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -30,7 +30,7 @@ GET Information about an individual VNF Instance
... Test title: GET Information about an individual VNF Instance
... Test objective: The objective is to create a new VNF instance resource
... Pre-conditions: none
- ... Reference: Clause 5.4.3.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.3.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -45,7 +45,7 @@ PUT Individual VNFInstance - Method not implemented
... Test title: PUT Individual VNFInstance - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.3.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.3.3.3 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: VNF instance not modified
@@ -57,7 +57,7 @@ PATCH Individual VNFInstance
... Test title: PATCH Individual VNFInstance
... Test objective: This method modifies an individual VNF instance resource
... Pre-conditions: none
- ... Reference: Clause 5.4.3.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.3.3.4 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: VNF instance modified
@@ -70,7 +70,7 @@ PATCH Individual VNFInstance Precondition failed
... Test title: PATCH Individual VNFInstance Precondition failed
... Test objective: The objective is to that the modification of individual VNFInstance fails because 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.
... Pre-conditions: none
- ... Reference: Clause 5.4.3.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.3.3.4 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -83,7 +83,7 @@ PATCH Individual VNFInstance Conflict
... Test title: PATCH Individual VNFInstance Conflict
... Test objective: The objective is to verify that modification operation cannot be executed currently, due to a conflict with the state of the VNF instance resource because another LCM Operation is ongoing.
... Pre-conditions: none
- ... Reference: Clause 5.4.3.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.3.3.4 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -96,7 +96,7 @@ DELETE Individual VNFInstance
... Test title: DELETE Individual VNFInstance
... Test objective: The objective is to delete a VNF instance
... Pre-conditions: none
- ... Reference: Clause 5.4.3.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.3.3.5 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: VNF instance deleted
@@ -108,7 +108,7 @@ DELETE Individual VNFInstance Conflict
... Test title: DELETE Individual VNFInstance Conflict
... Test objective: The objective is to verify that The operation cannot be executed currently, due to a conflict with the state of the VNF instance resource.
... Pre-conditions: VNF instance resource is in INSTANTIATED state
- ... Reference: Clause 5.4.3.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.3.3.5 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
diff --git a/SOL002/VNFLifecycleManagement-API/IndividualVNFSnapshot.robot b/SOL002/VNFLifecycleManagement-API/IndividualVNFSnapshot.robot
index 5e737b0db488811bbb32abb157e027ec73bc14ec..a461d3f2c35abdd7e5023f76f4140e67559a7a06 100644
--- a/SOL002/VNFLifecycleManagement-API/IndividualVNFSnapshot.robot
+++ b/SOL002/VNFLifecycleManagement-API/IndividualVNFSnapshot.robot
@@ -8,7 +8,7 @@ POST Individual VNF Snapshot - Method not implemented
... Test title: POST Individual VNF Snapshot - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.24.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.24.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -20,7 +20,7 @@ GET Information about an individual VNF Snapshot - SUCCESSFUL
... Test title: GET Information about an individual VNF Snapshot - SUCCESSFUL
... Test objective: The objective is to GET information about an individual VNF Snapshot
... Pre-conditions: none
- ... Reference: Clause 5.4.24.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.24.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -33,7 +33,7 @@ GET Information about an individual VNF Snapshot - NOT FOUND
... Test title: GET Information about an individual VNF Snapshot - NOT FOUND
... Test objective: The objective is to test that the retrieval of individual VNF Snapshot fails when using an invalid resource identifier.
... Pre-conditions: At least one individual VNF Snapshot is available in the NFV-MANO.
- ... Reference: Clause 5.4.24.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.24.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -46,7 +46,7 @@ PUT Individual VNF Snapshot - Method not implemented
... Test title: PUT Individual VNF Snapshot - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.24.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.24.3.3 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: VNF Snapshot not modified
@@ -58,7 +58,7 @@ PATCH Individual VNF Snapshot - Method not implemented
... Test title: PATCH Individual VNF Snapshot - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.24.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.24.3.4 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -70,7 +70,7 @@ DELETE Individual VNF Snapshot
... Test title: DELETE Individual VNF Snapshot
... Test objective: The objective is to delete a VNF Snapshot
... Pre-conditions: none
- ... Reference: Clause 5.4.24.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.24.3.5 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: VNF Snapshot deleted
@@ -82,7 +82,7 @@ DELETE Individual VNF Snapshot - Conflict
... Test title: DELETE Individual VNF Snapshot Conflict
... Test objective: The objective is to verify that The operation cannot be executed currently, due to a conflict with the state of the VNF Snapshot resource.
... Pre-conditions: none
- ... Reference: Clause 5.4.24.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.24.3.5 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: VNF snapshot is in use by some operation such as reverting a VNF instance to a VNF snapshot or creating a VNF snapshot package.
... Post-Conditions: none
diff --git a/SOL002/VNFLifecycleManagement-API/IndividualVnfLcmOperationOccurence.robot b/SOL002/VNFLifecycleManagement-API/IndividualVnfLcmOperationOccurence.robot
index 63859ff736cf2d2be51ab9daec98815f60321ffb..e135b9a2dd67483fc4f3d001e65694343f78a010 100644
--- a/SOL002/VNFLifecycleManagement-API/IndividualVnfLcmOperationOccurence.robot
+++ b/SOL002/VNFLifecycleManagement-API/IndividualVnfLcmOperationOccurence.robot
@@ -10,7 +10,7 @@ Post Individual VNF LCM OP occurrences - Method not implemented
... Test title: Post Individual VNF LCM OP occurrences - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.13.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.13.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -22,7 +22,7 @@ Get status information about multiple VNF instances
... Test title: Get status information about multiple VNF instances
... Test objective: The objective is to test that this method retrieve status information about a VNF lifecycle management operation occurrence
... Pre-conditions: none
- ... Reference: Clause 5.4.13.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.13.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -36,7 +36,7 @@ PUT status information about multiple VNF instances - Method not implemented
... Test title: PUT status information about multiple VNF instances - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.13.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.13.3.3 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -48,7 +48,7 @@ PATCH status information about multiple VNF instances - Method not implemented
... Test title: PATCH status information about multiple VNF instances - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.13.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.13.3.4 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -60,7 +60,7 @@ DELETE status information about multiple VNF instances - Method not implemented
... Test title: DELETE status information about multiple VNF instances - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.13.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.13.3.5 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
diff --git a/SOL002/VNFLifecycleManagement-API/InstantiateVNFTask.robot b/SOL002/VNFLifecycleManagement-API/InstantiateVNFTask.robot
index 694506c6f90c5dcadbabc204bb071aced634a749..1a97b19788ff9328359dbee00871016d32a46bb9 100644
--- a/SOL002/VNFLifecycleManagement-API/InstantiateVNFTask.robot
+++ b/SOL002/VNFLifecycleManagement-API/InstantiateVNFTask.robot
@@ -15,7 +15,7 @@ POST Instantiate a vnfInstance
... Test title: POST Instantiate a vnfInstance
... Test objective: The objective is to instantiate a VNF instance
... Pre-conditions: none
- ... Reference: Clause 5.4.4.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.4.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -28,7 +28,7 @@ POST Instantiate a vnfInstance Conflict
... Test title: POST Instantiate a vnfInstance Conflict
... Test objective: The objective is to verify that the instantiation of the vnf cannot be executed currently, due to a conflict with the state of the VNF instance resource.
... Pre-conditions: VNF instance resource is in INSTANTIATED state
- ... Reference: Clause 5.4.4.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.4.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -41,7 +41,7 @@ GET Instantiate VNFInstance - Method not implemented
... Test title: GET Instantiate VNFInstance - Method not implemented
... Test objective: The objective is to test that GET method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.4.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.4.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -53,7 +53,7 @@ PUT Instantiate VNFInstance - Method not implemented
... Test title: PUT Instantiate VNFInstance - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.4.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.4.3.3 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -65,7 +65,7 @@ PATCH Instantiate VNFInstance - Method not implemented
... Test title: PATCH Instantiate VNFInstance - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.4.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.4.3.4 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -77,7 +77,7 @@ DELETE Instantiate VNFInstance - Method not implemented
... Test title: DELETE Instantiate VNFInstance - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.4.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.4.3.5 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -89,7 +89,7 @@ POST Instantiate a vnfInstance with TaretScaleLevelId
... Test title: POST Instantiate a vnfInstance with TaretScaleLevelId attribute
... Test objective: The objective is to instantiate a VNF instance
... Pre-conditions: none
- ... Reference: Clause 5.4.4.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.4.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -102,7 +102,7 @@ POST Instantiate individual vnfInstance with instantiationLevelId
... Test title: POST Instantiate a vnfInstance with instantiationLevelId attribute
... Test objective: The objective is to instantiate a VNF instance
... Pre-conditions: none
- ... Reference: Clause 5.4.4.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.4.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
diff --git a/SOL002/VNFLifecycleManagement-API/NotificationEndpoint.robot b/SOL002/VNFLifecycleManagement-API/NotificationEndpoint.robot
index 7bdd35070b6a03e91966bce108e00674080db435..df3f54cc9ecefdf625eb735e6cd778e400ac4f96 100644
--- a/SOL002/VNFLifecycleManagement-API/NotificationEndpoint.robot
+++ b/SOL002/VNFLifecycleManagement-API/NotificationEndpoint.robot
@@ -14,7 +14,7 @@ VNF LCM Operation Occurrence Notification
... Test title: VNF LCM Operation Occurrence Start Notification
... Test objective: The objective is to test that VNF LCM Operation Occurrence Notification is delivered with success to the notification consumer
... Pre-conditions: A subscription for VNF LCM Operation Occurrence notifications is available in the VNFM.
- ... Reference: Clause 5.4.20.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.20.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
@@ -26,7 +26,7 @@ VNF Identifier Creation Notification
... Test title: VNF Identifier Creation Notification
... Test objective: The objective is to test that VNF Identifier Creation Notification is delivered with success to the notification consumer
... Pre-conditions: A subscription for VNF Identifier Creation Notification is available in the VNFM.
- ... Reference: Clause 5.4.20.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.20.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
@@ -38,7 +38,7 @@ VNF Identifier Deletion Notification
... Test title: VNF Identifier Deletion Notification
... Test objective: The objective is to test that VNF Identifier Deletion Notification is delivered with success to the notification consumer
... Pre-conditions: A subscription for VNF Identifier Deletion Notification is available in the VNFM.
- ... Reference: Clause 5.4.20.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.20.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
diff --git a/SOL002/VNFLifecycleManagement-API/Notifications.robot b/SOL002/VNFLifecycleManagement-API/Notifications.robot
index 3ae386405c71240c1a7cba5582a76430380d49a5..defe022d2716943a6e479d05c2c5969b9e6ba982 100644
--- a/SOL002/VNFLifecycleManagement-API/Notifications.robot
+++ b/SOL002/VNFLifecycleManagement-API/Notifications.robot
@@ -13,7 +13,7 @@ VNF LCM Operation Occurrence Start Notification
... Test title: VNF LCM Operation Occurrence Start Notification
... Test objective: The objective is to test the dispatch of VNF LCM Operation Occurrence Start Notification when a new VNF LCM operation is started in the VNFM, and perform a JSON schema and content validation of the delivered notification. The action that triggers the notification under test is an explicit test step, but it is not performed by the test system.
... Pre-conditions: A subscription for VNF LCM Operation Occurrence notifications is available in the VNFM.
- ... Reference: Clause 5.4.20.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.20.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -27,7 +27,7 @@ VNF LCM Operation Occurrence Result Notification
... Test title: VNF LCM Operation Occurrence Result Notification
... Test objective: The objective is to test the dispatch of VNF LCM Operation Occurrence Result Notification when a VNF LCM operation is completed in the VNFM, and perform a JSON schema and content validation of the delivered notification. The action that triggers the notification under test is an explicit test step, but it is not performed by the test system.
... Pre-conditions: An VNF LCM operation is in progress, and a subscription for VNF LCM Operation Occurrence notifications is available in the VNFM.
- ... Reference: Clause 5.4.20.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.20.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -41,7 +41,7 @@ VNF Identifier Creation Notification
... Test title: VNF Identifier Creation Notification
... Test objective: The objective is to test the dispatch of VNF Identifier Creation Notification when a new VNF instance resource is created in the VNFM, and perform a JSON schema and content validation of the delivered notification. The action that triggers the notification under test is an explicit test step, but it is not performed by the test system.
... Pre-conditions: A subscription for VNF identifier creation notifications is available in the VNFM.
- ... Reference: Clause 5.4.20.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.20.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -54,7 +54,7 @@ VNF Identifier Deletion Notification
... Test title: VNF Identifier Deletion Notification
... Test objective: The objective is to test the dispatch of VNF Identifier Deletion Notification when a VNF instance resource is deleted in the VNFM, and perform a JSON schema and content validation of the delivered notification. The action that triggers the notification under test is an explicit test step, but it is not performed by the test system.
... Pre-conditions: A VNF instance resource is created, and a subscription for VNF identifier creation notifications is available in the VNFM.
- ... Reference: Clause 6.4.18.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 6.4.18.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL002/VNFLifecycleManagement-API/OperateVNFTask.robot b/SOL002/VNFLifecycleManagement-API/OperateVNFTask.robot
index efe08bea36bf39080581f9262e605fb96f10886f..0a99effcfc36cb66fa97a93cf7624b223add2c4e 100644
--- a/SOL002/VNFLifecycleManagement-API/OperateVNFTask.robot
+++ b/SOL002/VNFLifecycleManagement-API/OperateVNFTask.robot
@@ -13,7 +13,7 @@ POST Operate a vnfInstance
... Test title: POST Operate a vnfInstance
... Test objective: The objective is to test that POST method operate a VNF instance
... Pre-conditions: none
- ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -26,7 +26,7 @@ POST Operate a vnfInstance Conflict (Not-Instantiated)
... Test title: POST Operate a vnfInstance Conflict (Not-Instantiated)
... Test objective: The objective is to test that the operation cannot be executed currently, due to a conflict with the state of the VNF instance resource or that a required child attribute of the "extensions" attribue has not been set.
... Pre-conditions: the VNF instance resource is in NOT_INSTANTIATED state
- ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -39,7 +39,7 @@ POST Operate a vnfInstance Not Found
... Test title: POST Operate a vnfInstance Not Found
... Test objective: The objective is to test that the operation cannot be executed currently, because the resource is not existing
... Pre-conditions: the VNF instance resource is in not existing
- ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -52,7 +52,7 @@ GET Operate VNFInstance - Method not implemented
... Test title: GET Operate VNFInstance - Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.10.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.10.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -64,7 +64,7 @@ PUT Operate VNFInstance - Method not implemented
... Test title: PUT Operate VNFInstance - Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.10.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.10.3.3 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -76,7 +76,7 @@ PATCH Operate VNFInstance - Method not implemented
... Test title: PATCH Operate VNFInstance - Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.10.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.10.3.4 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -88,7 +88,7 @@ DELETE Operate VNFInstance - Method not implemented
... Test title: DELETE Operate VNFInstance - Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.10.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.10.3.5 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
diff --git a/SOL002/VNFLifecycleManagement-API/RetryOperationTask.robot b/SOL002/VNFLifecycleManagement-API/RetryOperationTask.robot
index 9230870040cd35ace79e321d9f08765914b332ff..ef3416da61ff45a658610ab908a13cc594172918 100644
--- a/SOL002/VNFLifecycleManagement-API/RetryOperationTask.robot
+++ b/SOL002/VNFLifecycleManagement-API/RetryOperationTask.robot
@@ -12,9 +12,9 @@ Suite Setup Check resource existence
POST Retry operation task
[Documentation] Test ID: 6.3.5.13.1
... Test title: POST Retry operation task
- ... Test objective: The objective is to test that POST method The POST method initiates retrying a VNF lifecycle operation if that operation has experienced a temporary failure
+ ... Test objective: The objective is to test that the POST method initiates retrying a VNF lifecycle operation if that operation has experienced a temporary failure
... Pre-conditions: the "VNF LCM operation occurrence" resource is in "FAILED_TEMP" state.
- ... Reference: Clause 5.4.14.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.14.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -27,7 +27,7 @@ POST Retry operation task Conflict (Not-FAILED_TEMP)
... Test title: POST Retry operation task Conflict (Not-FAILED_TEMP)
... Test objective: The objective is to test that the retry operation cannot be executed currently, due to a conflict with the state of the VNF instance resource. (i.e. the VNF instance resource is not in FAILED_TEMP state)
... Pre-conditions: the "VNF LCM operation occurrence" resource is not in "FAILED_TEMP" state.
- ... Reference: Clause 5.4.14.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.14.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -40,7 +40,7 @@ POST Retry operation task Not Found
... Test title: POST Retry operation task Not Found
... Test objective: The objective is to test that the retry operation cannot be executed because the operation is not supported
... Pre-conditions:
- ... Reference: Clause 5.4.14.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.14.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -53,7 +53,7 @@ GET Retry operation task - Method not implemented
... Test title: GET Retry operation task- Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.14.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.14.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -65,7 +65,7 @@ PUT Retry operation task - Method not implemented
... Test title: PUT Retry operation task- Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.14.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.14.3 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -77,7 +77,7 @@ PATCH Retry operation task - Method not implemented
... Test title: PATCH Retry operation task- Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.14.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.14.4 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -89,7 +89,7 @@ DELETE Retry operation task - Method not implemented
... Test title: DELETE Retry operation task- Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.14.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.14.5 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
diff --git a/SOL002/VNFLifecycleManagement-API/RevertToVNFSnapshotTask.robot b/SOL002/VNFLifecycleManagement-API/RevertToVNFSnapshotTask.robot
index 73da877d38b60dd3947ddd922fdd7cfdc6f64e5f..caef4aebacfe7f3ec9e01f8a3b00a69c482e2ac4 100644
--- a/SOL002/VNFLifecycleManagement-API/RevertToVNFSnapshotTask.robot
+++ b/SOL002/VNFLifecycleManagement-API/RevertToVNFSnapshotTask.robot
@@ -13,7 +13,7 @@ POST Revert to VNF Snapshot Task
... Test title: POST Revert to VNF Snapshot Task
... Test objective: The objective is to test that POST method requests reverting a VNF/VNFC instance to a VNF/VNFC snapshot.
... Pre-conditions: none
- ... Reference: Clause 5.4.22.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.22.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: in response header Location shall not be null
@@ -26,7 +26,7 @@ POST Revert to VNF Snapshot Task - NOT FOUND
... Test title: POST Revert to VNF Snapshot Task - NOT FOUND
... Test objective: The objective is to test that the POST method cannot request reverting to a snapshot if the task is not supported for the VNF instance represented by the parent resource.
... Pre-conditions: none
- ... Reference: Clause 5.4.22.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.22.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: Task is not supported for the VNF instance represented by the parent resource.
... Post-Conditions: none
@@ -39,7 +39,7 @@ POST Revert to VNF Snapshot Task - CONFLICT
... Test title: POST Revert to VNF Snapshot Task - CONFLICT
... Test objective: The objective is to test that the POST method cannot request reverting to a snapshot when the VNF instance is in NOT_INSTANTIATED state.
... Pre-conditions: none
- ... Reference: Clause 5.4.22.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.22.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: VNF instance is in NOT_INSTANTIATED state.
... Post-Conditions: none
@@ -52,7 +52,7 @@ GET Revert to VNF Snapshot Task - Method not implemented
... Test title: GET Revert to VNF Snapshot Task - Method not implemented
... Test objective: The objective is to test that GET method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.22.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.22.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -64,7 +64,7 @@ PUT Revert to VNF Snapshot Task - Method not implemented
... Test title: PUT Revert to VNF Snapshot Task - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.22.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.22.3.3 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -76,7 +76,7 @@ PATCH Revert to VNF Snapshot Task - Method not implemented
... Test title: PATCH Revert to VNF Snapshot Task - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.22.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.22.3.4 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -88,7 +88,7 @@ DELETE Revert to VNF Snapshot Task - Method not implemented
... Test title: DELETE Revert to sVNF Snapshot Task - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.22.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.22.3.5 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
diff --git a/SOL002/VNFLifecycleManagement-API/RollbackOperationTask.robot b/SOL002/VNFLifecycleManagement-API/RollbackOperationTask.robot
index d2bb879ad4df51e9d38dd059d0d2a79709dfab82..58be4d68a31b6840a84595cad806896ed45504c4 100644
--- a/SOL002/VNFLifecycleManagement-API/RollbackOperationTask.robot
+++ b/SOL002/VNFLifecycleManagement-API/RollbackOperationTask.robot
@@ -14,7 +14,7 @@ POST Rollback operation task
... Test title: POST Rollback operation task
... Test objective: The objective is to test that POST method initiates rollback a VNF lifecycle operation if that operation has experienced a temporary failure
... Pre-conditions: the "VNF LCM operation occurrence" resource is in "FAILED_TEMP" state.
- ... Reference: Clause 5.4.15.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.15.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -27,7 +27,7 @@ POST Rollback operation task Conflict (Not-FAILED_TEMP)
... Test title: POST Rollback operation task Conflict (Not-FAILED_TEMP)
... Test objective: The objective is to test that POST method The POST method initiates rollback a VNF lifecycle operation if that operation has experienced a temporary failure
... Pre-conditions: the "VNF LCM operation occurrence" resource is not in "FAILED_TEMP" state.
- ... Reference: Clause 5.4.15.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.15.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -40,7 +40,7 @@ POST Rollback operation task Not Found
... Test title: POST Rollback operation task Not Found
... Test objective: The objective is to test that the retry operation cannot be executed because the operation is not supported
... Pre-conditions: none
- ... Reference: Clause 5.4.15.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.15.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -53,7 +53,7 @@ GET Rollback operation task - Method not implemented
... Test title: GET Rollback operation task - Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.15.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.15.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -65,7 +65,7 @@ PUT Rollback operation task - Method not implemented
... Test title: PUT Rollback operation task - Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.15.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.15.3.3 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -77,7 +77,7 @@ PATCH Rollback operation task - Method not implemented
... Test title: PATCH Rollback operation task - Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.15.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.15.3.4 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -89,7 +89,7 @@ DELETE Rollback operation task - Method not implemented
... Test title: DELETE Rollback operation task - Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.15.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.15.3.5 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
diff --git a/SOL002/VNFLifecycleManagement-API/ScaleVNFTask.robot b/SOL002/VNFLifecycleManagement-API/ScaleVNFTask.robot
index 683870071adee0b8789c223afe28b1c1fe082424..2409e01cf76708e36a89385b4935f29e0c8576bd 100644
--- a/SOL002/VNFLifecycleManagement-API/ScaleVNFTask.robot
+++ b/SOL002/VNFLifecycleManagement-API/ScaleVNFTask.robot
@@ -13,7 +13,7 @@ POST Scale a vnfInstance
... Test title: POST Scale a vnfInstance
... Test objective: The objective is to scale a VNF instance
... Pre-conditions: none
- ... Reference: Clause 5.4.5.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.5.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -26,7 +26,7 @@ POST Scale a vnfInstance Conflict (Not-Instantiated)
... Test title: POST Scale a vnfInstance Conflict (Not-Instantiated)
... Test objective: The objective is to verify that the operation cannot be executed currently, due to a conflict with the state of the VNF instance resource.
... Pre-conditions: VNF instance resource is in NOT-INSTANTIATED state
- ... Reference: Clause 5.4.5.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.5.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -39,7 +39,7 @@ POST Scale a vnfInstance Not Found
... Test title: POST Scale a vnfInstance Not Found
... Test objective: The objective is to verify that the operation cannot be executed currently, due to a conflict with the state of the VNF instance resource.
... Pre-conditions: none
- ... Reference: Clause 5.4.5.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.5.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -52,7 +52,7 @@ GET Scale VNFInstance - Method not implemented
... Test title: GET Scale VNFInstance - Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -64,7 +64,7 @@ PUT Scale VNFInstance - Method not implemented
... Test title: PUT Scale VNFInstance - Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.5.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.5.3.3 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -76,7 +76,7 @@ PATCH Scale VNFInstance - Method not implemented
... Test title: PATCH Scale VNFInstance - Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.5.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.5.3.4 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -88,7 +88,7 @@ DELETE Scale VNFInstance - Method not implemented
... Test title: DELETE Scale VNFInstance - Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.5.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.5.3.5 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
diff --git a/SOL002/VNFLifecycleManagement-API/ScaleVNFToLevelTask.robot b/SOL002/VNFLifecycleManagement-API/ScaleVNFToLevelTask.robot
index 5ec9c25575b5a2b2af5aca46ff55cb619af678b3..8c17c8f45144689ef604681df18d4f7a71463f6a 100644
--- a/SOL002/VNFLifecycleManagement-API/ScaleVNFToLevelTask.robot
+++ b/SOL002/VNFLifecycleManagement-API/ScaleVNFToLevelTask.robot
@@ -12,7 +12,7 @@ POST Scale a vnfInstance to level with Attribute instantiationLevelId
... Test title: POST Scale a vnfInstance to level with instantiationLevelId attribute
... Test objective: The objective is to scale a VNF instance to a target level.
... Pre-conditions: none
- ... Reference: Clause 5.4.6.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.6.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -26,7 +26,7 @@ POST Scale a vnfInstance to level Conflict (Not-Instantiated)
... Test title: POST Scale a vnfInstance to level Conflict (Not-Instantiated)
... Test objective: The objective is to verify that the operation cannot be executed currently, due to a conflict with the state of the VNF instance resource or that a required child attribute of the "extensions" attribue has not been set.
... Pre-conditions: VNF instance resource is in NOT-INSTANTIATED state
- ... Reference: Clause 5.4.6.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.6.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -39,7 +39,7 @@ POST Scale a vnfInstance Not Found
... Test title: POST Scale a vnfInstance Not Found
... Test objective: The objective is to verify that the VNF Scale operation fails when the VNF instance resource is not present
... Pre-conditions: VNF instance resource is in NOT-INSTANTIATED state
- ... Reference: Clause 5.4.6.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.6.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -52,7 +52,7 @@ GET Scale to level VNFInstance - Method not implemented
... Test title: GET Scale to level VNFInstance - Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.6.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.6.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -64,7 +64,7 @@ PUT Scale to level VNFInstance - Method not implemented
... Test title: PUT Scale to level VNFInstance - Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.6.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.6.3.3 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -76,7 +76,7 @@ PATCH Scale to level VNFInstance - Method not implemented
... Test title: PATCH Scale to level VNFInstance - Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.6.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.6.3.4 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -88,7 +88,7 @@ DELETE Scale to level VNFInstance - Method not implemented
... Test title: DELETE Scale to level VNFInstance - Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.6.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.6.3.5 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
diff --git a/SOL002/VNFLifecycleManagement-API/Subscriptions.robot b/SOL002/VNFLifecycleManagement-API/Subscriptions.robot
index 2078763ebb4f838c69c069cbe1cec5b2c4f57624..a203aab8056d3130c35e7cb0555f2cf79455fd7e 100644
--- a/SOL002/VNFLifecycleManagement-API/Subscriptions.robot
+++ b/SOL002/VNFLifecycleManagement-API/Subscriptions.robot
@@ -15,7 +15,7 @@ POST Create a new subscription
... Test title: POST Create a new subscription
... Test objective: The POST method creates a new subscription
... Pre-conditions: none
- ... Reference: Clause 5.4.18.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.18.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: in response header Location shall not be null
@@ -28,7 +28,7 @@ POST Create a new Subscription - DUPLICATION
... Test title: POST Create a new subscription - DUPLICATION
... Test objective: The POST method creates a new subscription even if an existing subscription to same content exist
... Pre-conditions: none
- ... Reference: Clause 5.4.18.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.18.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: SUT should support duplication of subscription creation
... Post-Conditions: in response header Location shall not be null
@@ -41,7 +41,7 @@ POST Create a new Subscription - NO-DUPLICATION
... Test title: POST Create a new subscription - NO-DUPLICATION
... Test objective: The POST method creates a new subscription even if an existing subscription to same content exist
... Pre-conditions: none
- ... Reference: Clause 5.4.18.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.18.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: SUT should not support duplication of subscription creation
... Post-Conditions: in response header Location shall not be null
@@ -54,7 +54,7 @@ GET Subscriptions
... Test title: GET Subscriptions
... Test objective: The objective is Get the list of active subscriptions
... Pre-conditions: none
- ... Reference: Clause 5.4.18.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.18.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -67,7 +67,7 @@ GET Subscription - Filter
... Test title: GET Subscriptions - Filter
... Test objective: The objective is Get the list of active subscriptions using a "filter"
... Pre-conditions: none
- ... Reference: Clause 5.4.18.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.18.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -80,7 +80,7 @@ GET subscriptions - Bad Request Invalid attribute-based filtering parameters
... Test title: GET subscriptions - Bad Request Invalid attribute-based filtering parameters
... Test objective: The objective is Get the list of active subscriptions using a filter
... Pre-conditions: none
- ... Reference: Clause 5.4.18.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.18.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -93,7 +93,7 @@ GET subscriptions - Bad Request Invalid attribute-based filtering parameters
... Test title: GET subscriptions with all_fields attribute selector
... Test objective: The objective is Get the list of active subscriptions
... Pre-conditions: none
- ... Reference: Clause 5.4.18.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.18.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -106,7 +106,7 @@ GET subscriptions with exclude_default attribute selector
... Test title: GET subscriptions with exclude_default attribute selector
... Test objective: The objective is Get the list of active subscriptions
... Pre-conditions: none
- ... Reference: Clause 5.4.18.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.18.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -119,7 +119,7 @@ GET subscriptions with fields attribute selector
... Test title: GET subscriptions with fields attribute selector
... Test objective: The objective is Get the list of active subscriptions
... Pre-conditions: none
- ... Reference: Clause 5.4.18.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.18.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -132,7 +132,7 @@ GET subscriptions with exclude_fields attribute selector
... Test title: GET subscriptions with exclude_fields attribute selector
... Test objective: The objective is Get the list of active subscriptions
... Pre-conditions: none
- ... Reference: Clause 5.4.18.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.18.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -145,7 +145,7 @@ PUT subscriptions - Method not implemented
... Test title: PUT subscriptions - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.18.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.18.3.3 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -157,7 +157,7 @@ PATCH subscriptions - Method not implemented
... Test title: PATCH subscriptions - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.18.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.18.3.4 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -169,7 +169,7 @@ DELETE subscriptions - Method not implemented
... Test title: DELETE subscriptions - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.18.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.18.3.5 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: check that resources are not deleted
@@ -177,12 +177,12 @@ DELETE subscriptions - Method not implemented
Check HTTP Response Status Code Is 405
Check Subscription resource exist
-POST Create a new Subscription - Unprocessable Entity
+POST Create a new Subscription - Unprocessable Content
[Documentation] Test ID: 6.3.5.17.14
- ... Test title: POST Create a new Subscription - Unprocessable Entity
- ... Test objective: The objective is to test that 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.
+ ... Test title: POST Create a new Subscription - Unprocessable Content
+ ... Test objective: The objective is to test that content type of the message content is supported and the message content of a request contains syntactically correct data but the data cannot be processed.
... re-conditions: none
- ... Reference: Clause 5.4.18.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.18.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -195,7 +195,7 @@ GET information about multiple subscriptions to get Paged Response
... Test title: GET information about multiple subscriptions to get Paged Response
... Test objective: The objective is to retrieve information about the subscriptions to get paged response
... Pre-conditions:
- ... Reference: Clause 5.4.18.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.18.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability:
... Post-Conditions:
@@ -208,7 +208,7 @@ GET information about multiple subscriptions for Bad Request Response too big
... Test title: GET information about multiple subscriptions for Bad Request Response too big
... Test objective: The objective is to test that GET method fail retrieving status information about subscriptions when Response is too big, and perform the JSON schema validation of the failed operation HTTP response
... Pre-conditions:
- ... Reference: Clause 5.4.18.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.18.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability:
... Post-Conditions:
diff --git a/SOL002/VNFLifecycleManagement-API/TerminateVNFTask.robot b/SOL002/VNFLifecycleManagement-API/TerminateVNFTask.robot
index a1187ba166aece8273f1396c48a1b7f5f929feeb..3965554d07e51316f6f5a8450bdd6a48ff14b67d 100644
--- a/SOL002/VNFLifecycleManagement-API/TerminateVNFTask.robot
+++ b/SOL002/VNFLifecycleManagement-API/TerminateVNFTask.robot
@@ -13,7 +13,7 @@ POST Terminate a vnfInstance
... Test title: POST Terminate a vnfInstance
... Test objective: The objective is to test that POST method terminate a VNF instance
... Pre-conditions: none
- ... Reference: Clause 5.4.8.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.8.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -26,7 +26,7 @@ POST Terminate a vnfInstance Conflict (Not-Instantiated)
... Test title: POST Terminate a vnfInstance Conflict (Not-Instantiated)
... Test objective: The objective is to test that the operation cannot be executed currently, due to a conflict with the state of the VNF instance resource or that a required child attribute of the "extensions" attribue has not been set.
... Pre-conditions: VNF instance resource is in NOT_INSTANTIATED state
- ... Reference: Clause 5.4.8.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.8.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -39,7 +39,7 @@ GET Terminate VNFInstance - Method not implemented
... Test title: GET Terminate VNFInstance - Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.8.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.8.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -51,7 +51,7 @@ PUT Terminate VNFInstance - Method not implemented
... Test title: PUT Terminate VNFInstance - Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.8.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.8.3.3 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -63,7 +63,7 @@ PATCH Terminate VNFInstance - Method not implemented
... Test title: PATCH Terminate VNFInstance - Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.8.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.8.3.4 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -75,7 +75,7 @@ DELETE Terminate VNFInstance - Method not implemented
... Test title: DELETE Terminate VNFInstance - Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.8.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.8.3.5 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
diff --git a/SOL002/VNFLifecycleManagement-API/VNFInstances.robot b/SOL002/VNFLifecycleManagement-API/VNFInstances.robot
index 4e7410f82dbb204e972489d9be695f922b2ddb30..150f77d3a4367b80de56327524220263fad12ed9 100644
--- a/SOL002/VNFLifecycleManagement-API/VNFInstances.robot
+++ b/SOL002/VNFLifecycleManagement-API/VNFInstances.robot
@@ -12,7 +12,7 @@ POST Create a new vnfInstance
... Test title: POST Create a new vnfInstance
... Test objective: The objective is to create a new VNF instance resource
... Pre-conditions: none
- ... Reference: Clause 5.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: VNF instance created
@@ -26,7 +26,7 @@ GET information about multiple VNF instances
... Test title: GET information about multiple VNF instances
... Test objective: The objective is to get information about multiples VNF instances
... Pre-conditions: none
- ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -40,7 +40,7 @@ GET information about multiple VNF instances Bad Request Invalid attribute-based
... Test title: GET information about multiple VNF instances Bad Request Invalid attribute-based filtering parameters
... Test objective: The objective is to get information about multiples VNF instances with Invalid attribute-based filtering parameters
... Pre-conditions: none
- ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -53,7 +53,7 @@ GET information about multiple VNF instances Bad Request Invalid attribute selec
... Test title: GET information about multiple VNF instances Bad Request Invalid attribute selector
... Test objective: The objective is to get information about multiples VNF instances with Invalid attribute-based filtering parameters
... Pre-conditions: none
- ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -66,7 +66,7 @@ GET information about multiple VNF instances with "all_fields" attribute selecto
... Test title: GET information about multiple VNF instances with "all_fields" attribute selector
... Test objective: The objective is to query information about multiple VNF instances
... Pre-conditions: none
- ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -79,7 +79,7 @@ GET information about multiple VNF instances with "exclude_default" attribute se
... Test title: GET information about multiple VNF instances with "exclude_default" attribute selector
... Test objective: The objective is to query information about multiple VNF instances
... Pre-conditions: none
- ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -92,7 +92,7 @@ GET information about multiple VNF instances with "fields" attribute selector
... Test title: GET information about multiple VNF instances with "fields" attribute selector
... Test objective: The objective is to query information about multiple VNF instances
... Pre-conditions: none
- ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -105,7 +105,7 @@ GET information about multiple VNF instances with "exclude_fields" attribute sel
... Test title: GET information about multiple VNF instances with "exclude_fields" attribute selector
... Test objective: The objective is to query information about multiple VNF instances
... Pre-conditions: none
- ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -118,7 +118,7 @@ PUT VNFInstances - Method not implemented
... Test title: PUT VNFInstances - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.2.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.2.3.3 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -130,7 +130,7 @@ PATCH VNFInstances - Method not implemented
... Test title: PATCH VNFInstances - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.2.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.2.3.4 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -142,7 +142,7 @@ DELETE VNFInstances - Method not implemented
... Test title: DELETE VNFInstances - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.2.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.2.3.5 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: VNF instance not deleted
@@ -154,7 +154,7 @@ GET information about multiple VNF instances with "exclude_default" and "fields"
... Test title: GET information about multiple VNF instances with "exclude_default" and "fields" attribute selector
... Test objective: The objective is to query information about multiple VNF instances
... Pre-conditions: none
- ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -162,12 +162,12 @@ GET information about multiple VNF instances with "exclude_default" and "fields"
Check HTTP Response Status Code Is 200
Check HTTP Response Body Json Schema Is vnfInstances
-POST Create a new vnfInstance - UNPROCESSIBLE ENTITY
+POST Create a new vnfInstance - UNPROCESSABLE CONTENT
[Documentation] Test ID: 6.3.5.1.13
- ... Test title: POST Create a new vnfInstance - UNPROCESSIBLE ENTITY
+ ... Test title: POST Create a new vnfInstance - UNPROCESSABLE CONTENT
... Test objective: The objective is to test that a new VNF instance resource is not created when
... Pre-conditions: none
- ... Reference: Clause 5.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: vnfdId of the referenced VNF package is not in ENABLED state or does not exist.
... Post-Conditions: VNF instance created
diff --git a/SOL002/VNFLifecycleManagement-API/VNFSnapshots.robot b/SOL002/VNFLifecycleManagement-API/VNFSnapshots.robot
index c57ae45ad8b0b5f01812db4324c48dc7c609ee1f..6bcece86c9343bcb2a09a42e0ca76e54a448fb8f 100644
--- a/SOL002/VNFLifecycleManagement-API/VNFSnapshots.robot
+++ b/SOL002/VNFLifecycleManagement-API/VNFSnapshots.robot
@@ -8,7 +8,7 @@ POST Create a new VNF Snapshot
... Test title: POST Create a new VNF Snapshot
... Test objective: The objective is to create a new VNF snapshot
... Pre-conditions: none
- ... Reference: Clause 5.4.23.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.23.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: VNF snapshot is created
@@ -22,7 +22,7 @@ GET information about multiple VNF Snapshots
... Test title: GET information about multiple VNF Snapshots
... Test objective: The objective is to get information about multiples VNF snapshots
... Pre-conditions: none
- ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -35,7 +35,7 @@ GET information about multiple VNF Snapshots Bad Request Invalid attribute-based
... Test title: GET information about multiple VNF Snapshots Bad Request Invalid attribute-based filtering parameters
... Test objective: The objective is to get information about multiples VNF Snapshots with Invalid attribute-based filtering parameters
... Pre-conditions: none
- ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -48,7 +48,7 @@ GET information about multiple VNF Snapshots Bad Request Invalid attribute selec
... Test title: GET information about multiple VNF Snapshots Bad Request Invalid attribute selector
... Test objective: The objective is to get information about multiples VNF Snapshots with Invalid attribute-based filtering parameters
... Pre-conditions: none
- ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -61,7 +61,7 @@ GET information about multiple VNF Snapshots with "all_fields" attribute selecto
... Test title: GET information about multiple VNF Snapshots with "all_fields" attribute selector
... Test objective: The objective is to query information about multiple VNF Snapshots
... Pre-conditions: none
- ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -74,7 +74,7 @@ GET information about multiple VNF Snapshots with "exclude_default" attribute se
... Test title: GET information about multiple VNF Snapshots with "exclude_default" attribute selector
... Test objective: The objective is to query information about multiple VNF Snapshots
... Pre-conditions: none
- ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -87,7 +87,7 @@ GET information about multiple VNF Snapshots with "fields" attribute selector
... Test title: GET information about multiple VNF Snapshots with "fields" attribute selector
... Test objective: The objective is to query information about multiple VNF Snapshots
... Pre-conditions: none
- ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -100,7 +100,7 @@ GET information about multiple VNF Snapshots with "exclude_default" and "fields"
... Test title: GET information about multiple VNF Snapshots with "exclude_default" and "fields" attribute selector
... Test objective: The objective is to query information about multiple VNF Snapshots
... Pre-conditions: none
- ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -113,7 +113,7 @@ GET information about multiple VNF Snapshots with "exclude_fields" attribute sel
... Test title: GET information about multiple VNF Snapshots with "exclude_fields" attribute selector
... Test objective: The objective is to query information about multiple VNF Snapshots
... Pre-conditions: none
- ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -126,7 +126,7 @@ GET VNF Snapshots - Bad Request Response too Big
... Test title: GET VNF Snapshots - Bad Request Response too Big
... Test objective: The objective is test that the retrieval of existing VNF Snapshots list fails because response is too big, and perform the JSON schema validation of the failed operation HTTP response.
... Pre-conditions: none
- ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: VNFM does not support paged response.
... Post-Conditions: none
@@ -139,7 +139,7 @@ GET VNF Snapshots as Paged Response
... Test title: GET VNF Snapshots as Paged Response
... Test objective: The objective is to test that GET method retrieves the list of existing VNF Snapshots as paged response.
... Pre-conditions: none
- ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: VNFM supports paged response.
... Post-Conditions: none
@@ -152,7 +152,7 @@ PUT VNF Snapshots - Method not implemented
... Test title: PUT VNF Snapshots - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.23.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.23.3.3 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -164,7 +164,7 @@ PATCH VNF Snapshots - Method not implemented
... Test title: PATCH VNF Snapshots - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.23.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.23.3.4 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -176,7 +176,7 @@ DELETE VNF Snapshots - Method not implemented
... Test title: DELETE VNF Snapshots - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.23.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.23.3.5 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: VNF instance not deleted
diff --git a/SOL002/VNFLifecycleManagement-API/VnfLcmOperationOccurences.robot b/SOL002/VNFLifecycleManagement-API/VnfLcmOperationOccurences.robot
index 18bb9b59c7580fcc2e437024739aed2194fe3460..49c6c53d38ac2a59f7181f0c72f42d2628820984 100644
--- a/SOL002/VNFLifecycleManagement-API/VnfLcmOperationOccurences.robot
+++ b/SOL002/VNFLifecycleManagement-API/VnfLcmOperationOccurences.robot
@@ -13,7 +13,7 @@ POST VNF LCM operation occurrences - Method not implemented
... Test title: POST VNF LCM operation occurrences - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.12.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.12.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -25,7 +25,7 @@ GET status information about multiple VNF LCM operation occurrences
... Test title: GET status information about multiple VNF LCM operation occurrences
... Test objective: The objective is to test that GET method retrieve Query status information about multiple VNF lifecycle management operation occurrences.
... Pre-conditions: none
- ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -39,7 +39,7 @@ GET status information about multiple VNF LCM operation occurrences Bad Request
... Test title: GET status information about multiple VNF LCM operation occurrences Bad Request Invalid attribute-based filtering parameters
... Test objective: The objective is to test that GET method fail retrieving status information about multiple VNF lifecycle management operation occurrences because attribute is invalid.
... Pre-conditions: none
- ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -52,7 +52,7 @@ GET status information about multiple VNF LCM Operation occurrences Bad Request
... Test title: GET status information about multiple VNF LCM Operation occurrences Bad Request Invalid attribute selector
... Test objective: The objective is to test that GET method fail retrieving status information about multiple VNF lifecycle management operation occurrences because attribute is invalid.
... Pre-conditions: none
- ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -65,7 +65,7 @@ GET status information about multiple VNF LCM Operation occurrences with "all_fi
... Test title: GET status information about multiple VNF LCM Operation OCC with "all_fields"
... Test objective: The objective is to test that GET method retrieve Query status information about multiple VNF lifecycle management operation occurrences.
... Pre-conditions: none
- ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -78,7 +78,7 @@ GET status information about multiple VNF LCM Operation occurrences with "exlude
... Test title: GET status information about multiple VNF LCM Operation OCC with "exclude_default"
... Test objective: The objective is to test that GET method retrieve Query status information about multiple VNF lifecycle management operation occurrences.
... Pre-conditions: none
- ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -91,7 +91,7 @@ GET status information about multiple VNF LCM Operation occurrences with "fields
... Test title: GET status information about multiple VNF LCM Operation OCC with "fields"
... Test objective: The objective is to test that GET method retrieve Query status information about multiple VNF lifecycle management operation occurrences.
... Pre-conditions: none
- ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -104,7 +104,7 @@ GET status information about multiple VNF LCM Operation occurrences with "exclud
... Test title: GET status information about multiple VNF LCM Operation OCC with "exclude_fields"
... Test objective: The objective is to test that GET method retrieve Query status information about multiple VNF lifecycle management operation occurrences.
... Pre-conditions: none
- ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -117,7 +117,7 @@ PUT status information about multiple VNF LCM operation occurrences - Method not
... Test title: PUT status information about multiple VNF LCM operation occurrences - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.12.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.12.3.3 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -129,7 +129,7 @@ PATCH status information about multiple VNF LCM operation occurrences - Method n
... Test title: PATCH status information about multiple VNF LCM operation occurrences - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.12.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.12.3.4 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -141,7 +141,7 @@ DELETE status information about multiple VNF LCM operation occurrences - Method
... Test title: DELETE status information about multiple VNF LCM operation occurrences - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.12.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.12.3.5 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -153,7 +153,7 @@ GET status information about multiple VNF LCM operation occurances to get Paged
... Test title: GET status information about multiple VNF LCM operation occurances to get Paged Response
... Test objective: The objective is to test that GET method retrieve Query status information about multiple VNF lifecycle management operation occurrences to get paged response.
... Pre-conditions: none
- ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -166,7 +166,7 @@ GET status information about multiple VNF LCM Operation occurrences Bad Request
... Test title: GET status information about multiple VNF LCM Operation occurrences Bad Request Response too big
... Test objective: The objective is to test that GET method fail retrieving status information about multiple VNF lifecycle management operation occurrences because Response is too big.
... Pre-conditions: none
- ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -179,7 +179,7 @@ GET status information about multiple VNF LCM Operation occurrences with "exlude
... Test title: GET status information about multiple VNF LCM Operation OCC with "exclude_default" and "fields"
... Test objective: The objective is to test that GET method retrieve Query status information about multiple VNF lifecycle management operation occurrences.
... Pre-conditions: none
- ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
diff --git a/SOL002/VNFLifecycleManagement-API/schemas/VnfLcmOperationOccurrenceNotification.schema.json b/SOL002/VNFLifecycleManagement-API/schemas/VnfLcmOperationOccurrenceNotification.schema.json
index d5e28f6deb68735e6d86f2c21fa01121016d7f21..ab574695702807a4f3b990a52856094f7367f5fa 100644
--- a/SOL002/VNFLifecycleManagement-API/schemas/VnfLcmOperationOccurrenceNotification.schema.json
+++ b/SOL002/VNFLifecycleManagement-API/schemas/VnfLcmOperationOccurrenceNotification.schema.json
@@ -249,7 +249,7 @@
"resourceId"
],
"type": "object",
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance. Information about the resource is available from the VIM.\n* NOTE 1: The information about the VIM or CISM connection referenced by the VIM connection id is known to the\n VNFM. Moreover, the identifier of the VIM connection provides scope to the resourceId.\n\n* NOTE 2: The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or CISM or the resource \n provider and can be used as information that complements the ResourceHandle. When the container\n infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would \n correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, \n PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 3: When the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the \n following way:\n - For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide \n per resource type.\n - For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, \n i.e. the value of the 'claimName' field in the Kubernetes® manifest, or a compound name built by \n Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own \n manifest.\n - For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of \n the 'metadata.name' field in Kubernetes® manifest.\n",
+ "description": "This type represents the information that allows addressing a virtualised resource or Network MCIO that is used by a VNF instance. Information about the resource is available from the VIM.\n* NOTE 1: The information about the VIM or CISM connection referenced by the VIM connection id is known to the\n VNFM. Moreover, the identifier of the VIM connection provides scope to the resourceId.\n\n* NOTE 2: The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or CISM or the resource \n provider and can be used as information that complements the ResourceHandle. When the container\n infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would \n correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, \n PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 3: When the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the \n following way:\n - For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide \n per resource type.\n - For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, \n i.e. the value of the 'claimName' field in the Kubernetes® manifest, or a compound name built by \n Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own \n manifest.\n - For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of \n the 'metadata.name' field in Kubernetes® manifest.\n",
"properties": {
"vimConnectionId": {
"description": "An identifier with the intention of being globally unique.\n",
@@ -426,7 +426,7 @@
"resourceId"
],
"type": "object",
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance. Information about the resource is available from the VIM.\n* NOTE 1: The information about the VIM or CISM connection referenced by the VIM connection id is known to the\n VNFM. Moreover, the identifier of the VIM connection provides scope to the resourceId.\n\n* NOTE 2: The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or CISM or the resource \n provider and can be used as information that complements the ResourceHandle. When the container\n infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would \n correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, \n PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 3: When the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the \n following way:\n - For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide \n per resource type.\n - For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, \n i.e. the value of the 'claimName' field in the Kubernetes® manifest, or a compound name built by \n Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own \n manifest.\n - For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of \n the 'metadata.name' field in Kubernetes® manifest.\n",
+ "description": "This type represents the information that allows addressing a virtualised resource or Storage MCIO that is used by a VNF instance. Information about the resource is available from the VIM or the CISM.\n* NOTE 1: The information about the VIM or CISM connection referenced by the VIM connection id is known to the\n VNFM. Moreover, the identifier of the VIM connection provides scope to the resourceId.\n\n* NOTE 2: The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or CISM or the resource \n provider and can be used as information that complements the ResourceHandle. When the container\n infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would \n correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, \n PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 3: When the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the \n following way:\n - For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide \n per resource type.\n - For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, \n i.e. the value of the 'claimName' field in the Kubernetes® manifest, or a compound name built by \n Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own \n manifest.\n - For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of \n the 'metadata.name' field in Kubernetes® manifest.\n",
"properties": {
"vimConnectionId": {
"description": "An identifier with the intention of being globally unique.\n",
@@ -773,7 +773,7 @@
"description": "Map of instance data that need to be configured on the CP instances created from the respective CPD. The key of the map which identifies the individual VnfExtCpConfig entries is of type \"IdentifierInVnf\" and is managed by the NFVO. The entries shall be applied by the VNFM according to the rules of JSON Merge Patch (see IETF RFC 7396). See notes 2, 3 and 4.\n",
"type": "object",
"additionalProperties": {
- "description": "This type represents an externally provided link port, or a network attachment definition resource of secondary container cluster network, or network address information per instance of an external connection point. In the case of VM-based deployment of the VNFC exposing the external CP:\n 1. In case a link port is provided, the VNFM shall use that link port when connecting the external CP to the\n external VL.\n 2. In case a link port is not provided, the VNFM shall create a link port on the external VL and use that link port\n to connect the external CP to the external VL.\nIn the case of container-based deployment of the VNFC exposing the external CP, the VNFM shall use the network attachment definition resource of secondary container cluster network when connecting the CP to the external VL.\n* NOTE 1: The following conditions apply to the attributes \"linkPortId\" and \"cpProtocolData\" for an external CP\n instance connected or to be connected to a virtual network not categorized as secondary container cluster network:\n 1) Void.\n 2) At least one of the \"linkPortId\" and \"cpProtocolData\" attributes shall be present for an external CP instance\n representing a subport that is to be created, or an external CP instance that is to be created by creating the\n corresponding VNFC or VNF instance during the current or a subsequent LCM operation, or for an existing\n external CP instance that is to be re-configured or added to a particular external virtual link.\n 3) If the \"linkPortId\" attribute is absent, the VNFM shall create a link port.\n 4) If the \"cpProtocolData\" attribute is absent, the \"linkPortId\" attribute shall be provided referencing a\n precreated link port, and the VNFM can use means outside the scope of the present document to obtain the\n pre-configured address information for the connection point from the resource representing the link port.\n 5) If both \"cpProtocolData\" and \"linkportId\" are provided, the NFVO shall ensure that the\n cpProtocolData can be used with the pre-created link port referenced by \"linkPortId\".\n\n* NOTE 2: The following conditions apply to the attributes ΓÇ£netAttDefResourceIdΓÇ¥ and ΓÇ£cpProtocolDataΓÇ¥ for an external CP\n instance connected or to be connected to a secondary container cluster network:\n 1) The \"netAttDefResourceId\" and \"cpProtocolData\" attributes shall both be absent for the deletion of an\n existing external CP instance addressed by cpInstanceId.\n 2) The \"netAttDefResourceId\" attribute shall be present and the \"cpProtocolData\" attribute may be present for\n a to-be-created external CP instance or an existing external CP instance.\n* NOTE 3: Cardinality greater than 1 is only applicable for specific cases where more than one network attachment\n definition resource is needed to fulfil the connectivity requirements of the external CP, e.g. to build a link\n redundant mated pair in SR-IOV cases. When more than one netAttDefResourceId is indicated, all shall belong\n to the same namespace as defined by the corresponding \"netAttDefResourceNamespace\" attribute in the\n \"NetAttDefResourceData\".\n* NOTE 4: Either linkPortId or netAttDefResourceId may be included, but not both.\n",
+ "description": "This type represents an externally provided link port, or a network attachment definition resource of secondary container cluster network, or network address information per instance of an external connection point. In the case of VM-based deployment of the VNFC exposing the external CP:\n 1. In case a link port is provided, the VNFM shall use that link port when connecting the external CP to the\n external VL.\n 2. In case a link port is not provided, the VNFM shall create a link port on the external VL and use that link port\n to connect the external CP to the external VL.\nIn the case of container-based deployment of the VNFC exposing the external CP, the VNFM shall use the network attachment definition resource of secondary container cluster network when connecting the CP to the external VL.\n* NOTE 1: The following conditions apply to the attributes \"linkPortId\" and \"cpProtocolData\" for an external CP\n instance connected or to be connected to a virtual network not categorized as secondary container cluster network:\n 1) Void.\n 2) At least one of the \"linkPortId\" and \"cpProtocolData\" attributes shall be present for an external CP instance\n representing a subport that is to be created, or an external CP instance that is to be created by creating the\n corresponding VNFC or VNF instance during the current or a subsequent LCM operation, or for an existing\n external CP instance that is to be re-configured or added to a particular external virtual link.\n 3) If the \"linkPortId\" attribute is absent, the VNFM shall create a link port.\n 4) If the \"cpProtocolData\" attribute is absent, the \"linkPortId\" attribute shall be provided referencing a\n precreated link port, and the VNFM can use means outside the scope of the present document to obtain the\n pre-configured address information for the connection point from the resource representing the link port.\n 5) If both \"cpProtocolData\" and \"linkportId\" are provided, the NFVO shall ensure that the\n cpProtocolData can be used with the pre-created link port referenced by \"linkPortId\".\n\n* NOTE 2: The following conditions apply to the attributes ΓÇ£netAttDefResourceIdΓÇ¥ and ΓÇ£cpProtocolDataΓÇ¥ for an external CP\n instance connected or to be connected to a secondary container cluster network:\n 1) Void.\n 2) The \"netAttDefResourceId\" attribute shall be present and the \"cpProtocolData\" attribute may be present for\n a to-be-created external CP instance or an existing external CP instance.\n* NOTE 3: Cardinality greater than 1 is only applicable for specific cases where more than one network attachment\n definition resource is needed to fulfil the connectivity requirements of the external CP, e.g. to build a link\n redundant mated pair in SR-IOV cases. When more than one netAttDefResourceId is indicated, all shall belong\n to the same namespace as defined by the corresponding \"containerNamespace\" attribute in the\n \"resourceHandle\" attribute in the \"NetAttDefResourceData\".\n* NOTE 4: Either linkPortId or netAttDefResourceId may be included, but not both.\n",
"anyOf": [
{
"required": [
@@ -933,7 +933,7 @@
}
},
"virtualCpAddress": {
- "description": "This type represents information about a link port of an external VL, i.e. a port providing connectivity for the VNF to an NS VL.\n* NOTE 1: If the container cluster is set up to be able to configure an external load balancer this address will be used,\n otherwise it will be ignored by the CISM.\n\n* NOTE 2: In case the cluster can configure an external load balancer but no loadBalancerIp is provided the container\n cluster will assign an IP address.\n",
+ "description": "This type represents network address data for a virtual CP.\n* NOTE 1: If the container cluster is set up to be able to configure an external load balancer this address will be used,\n otherwise it will be ignored by the CISM.\n\n* NOTE 2: In case the cluster can configure an external load balancer but no loadBalancerIp is provided the container\n cluster will assign an IP address.\n\n* NOTE 3: The attribute is only relevant if the virtual CP is instantiated in a cluster that supports configuration of IP address pools for virtual CPs. Otherwise it shall be ignored. MetalLB is an example of a solution for Kubernetes® that supports configuration of address pools for load balancer services.\n\n* NOTE 4: The loadBalancerIp and the addressPoolName attributes shall not be present at the same time.\n",
"type": "object",
"required": [
"type"
@@ -951,6 +951,10 @@
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.\n",
+ "type": "string"
}
}
}
diff --git a/SOL002/VNFLifecycleManagement-API/schemas/VnfSnapshotInfo.schema.json b/SOL002/VNFLifecycleManagement-API/schemas/VnfSnapshotInfo.schema.json
index 54f0bdc98d33894d9b43f2b45bb6806b835a8b53..4c54facbf2051f9b42042050866e36e22fe42085 100644
--- a/SOL002/VNFLifecycleManagement-API/schemas/VnfSnapshotInfo.schema.json
+++ b/SOL002/VNFLifecycleManagement-API/schemas/VnfSnapshotInfo.schema.json
@@ -358,6 +358,10 @@
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.\n",
+ "type": "string"
}
}
}
@@ -559,6 +563,10 @@
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.\n",
+ "type": "string"
}
}
}
@@ -789,6 +797,10 @@
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.\n",
+ "type": "string"
}
}
}
@@ -1023,7 +1035,7 @@
"description": "Map of instance data that need to be configured on the CP instances created from the respective CPD. The key of the map which identifies the individual VnfExtCpConfig entries is of type \"IdentifierInVnf\" and is managed by the NFVO. The entries shall be applied by the VNFM according to the rules of JSON Merge Patch (see IETF RFC 7396). See notes 2, 3 and 4.\n",
"type": "object",
"additionalProperties": {
- "description": "This type represents an externally provided link port, or a network attachment definition resource of secondary container cluster network, or network address information per instance of an external connection point. In the case of VM-based deployment of the VNFC exposing the external CP:\n 1. In case a link port is provided, the VNFM shall use that link port when connecting the external CP to the\n external VL.\n 2. In case a link port is not provided, the VNFM shall create a link port on the external VL and use that link port\n to connect the external CP to the external VL.\nIn the case of container-based deployment of the VNFC exposing the external CP, the VNFM shall use the network attachment definition resource of secondary container cluster network when connecting the CP to the external VL.\n* NOTE 1: The following conditions apply to the attributes \"linkPortId\" and \"cpProtocolData\" for an external CP\n instance connected or to be connected to a virtual network not categorized as secondary container cluster network:\n 1) Void.\n 2) At least one of the \"linkPortId\" and \"cpProtocolData\" attributes shall be present for an external CP instance\n representing a subport that is to be created, or an external CP instance that is to be created by creating the\n corresponding VNFC or VNF instance during the current or a subsequent LCM operation, or for an existing\n external CP instance that is to be re-configured or added to a particular external virtual link.\n 3) If the \"linkPortId\" attribute is absent, the VNFM shall create a link port.\n 4) If the \"cpProtocolData\" attribute is absent, the \"linkPortId\" attribute shall be provided referencing a\n precreated link port, and the VNFM can use means outside the scope of the present document to obtain the\n pre-configured address information for the connection point from the resource representing the link port.\n 5) If both \"cpProtocolData\" and \"linkportId\" are provided, the NFVO shall ensure that the\n cpProtocolData can be used with the pre-created link port referenced by \"linkPortId\".\n\n* NOTE 2: The following conditions apply to the attributes ΓÇ£netAttDefResourceIdΓÇ¥ and ΓÇ£cpProtocolDataΓÇ¥ for an external CP\n instance connected or to be connected to a secondary container cluster network:\n 1) The \"netAttDefResourceId\" and \"cpProtocolData\" attributes shall both be absent for the deletion of an\n existing external CP instance addressed by cpInstanceId.\n 2) The \"netAttDefResourceId\" attribute shall be present and the \"cpProtocolData\" attribute may be present for\n a to-be-created external CP instance or an existing external CP instance.\n* NOTE 3: Cardinality greater than 1 is only applicable for specific cases where more than one network attachment\n definition resource is needed to fulfil the connectivity requirements of the external CP, e.g. to build a link\n redundant mated pair in SR-IOV cases. When more than one netAttDefResourceId is indicated, all shall belong\n to the same namespace as defined by the corresponding \"netAttDefResourceNamespace\" attribute in the\n \"NetAttDefResourceData\".\n* NOTE 4: Either linkPortId or netAttDefResourceId may be included, but not both.\n",
+ "description": "This type represents an externally provided link port, or a network attachment definition resource of secondary container cluster network, or network address information per instance of an external connection point. In the case of VM-based deployment of the VNFC exposing the external CP:\n 1. In case a link port is provided, the VNFM shall use that link port when connecting the external CP to the\n external VL.\n 2. In case a link port is not provided, the VNFM shall create a link port on the external VL and use that link port\n to connect the external CP to the external VL.\nIn the case of container-based deployment of the VNFC exposing the external CP, the VNFM shall use the network attachment definition resource of secondary container cluster network when connecting the CP to the external VL.\n* NOTE 1: The following conditions apply to the attributes \"linkPortId\" and \"cpProtocolData\" for an external CP\n instance connected or to be connected to a virtual network not categorized as secondary container cluster network:\n 1) Void.\n 2) At least one of the \"linkPortId\" and \"cpProtocolData\" attributes shall be present for an external CP instance\n representing a subport that is to be created, or an external CP instance that is to be created by creating the\n corresponding VNFC or VNF instance during the current or a subsequent LCM operation, or for an existing\n external CP instance that is to be re-configured or added to a particular external virtual link.\n 3) If the \"linkPortId\" attribute is absent, the VNFM shall create a link port.\n 4) If the \"cpProtocolData\" attribute is absent, the \"linkPortId\" attribute shall be provided referencing a\n precreated link port, and the VNFM can use means outside the scope of the present document to obtain the\n pre-configured address information for the connection point from the resource representing the link port.\n 5) If both \"cpProtocolData\" and \"linkportId\" are provided, the NFVO shall ensure that the\n cpProtocolData can be used with the pre-created link port referenced by \"linkPortId\".\n\n* NOTE 2: The following conditions apply to the attributes ΓÇ£netAttDefResourceIdΓÇ¥ and ΓÇ£cpProtocolDataΓÇ¥ for an external CP\n instance connected or to be connected to a secondary container cluster network:\n 1) Void.\n 2) The \"netAttDefResourceId\" attribute shall be present and the \"cpProtocolData\" attribute may be present for\n a to-be-created external CP instance or an existing external CP instance.\n* NOTE 3: Cardinality greater than 1 is only applicable for specific cases where more than one network attachment\n definition resource is needed to fulfil the connectivity requirements of the external CP, e.g. to build a link\n redundant mated pair in SR-IOV cases. When more than one netAttDefResourceId is indicated, all shall belong\n to the same namespace as defined by the corresponding \"containerNamespace\" attribute in the\n \"resourceHandle\" attribute in the \"NetAttDefResourceData\".\n* NOTE 4: Either linkPortId or netAttDefResourceId may be included, but not both.\n",
"anyOf": [
{
"required": [
@@ -1183,7 +1195,7 @@
}
},
"virtualCpAddress": {
- "description": "This type represents information about a link port of an external VL, i.e. a port providing connectivity for the VNF to an NS VL.\n* NOTE 1: If the container cluster is set up to be able to configure an external load balancer this address will be used,\n otherwise it will be ignored by the CISM.\n\n* NOTE 2: In case the cluster can configure an external load balancer but no loadBalancerIp is provided the container\n cluster will assign an IP address.\n",
+ "description": "This type represents network address data for a virtual CP.\n* NOTE 1: If the container cluster is set up to be able to configure an external load balancer this address will be used,\n otherwise it will be ignored by the CISM.\n\n* NOTE 2: In case the cluster can configure an external load balancer but no loadBalancerIp is provided the container\n cluster will assign an IP address.\n\n* NOTE 3: The attribute is only relevant if the virtual CP is instantiated in a cluster that supports configuration of IP address pools for virtual CPs. Otherwise it shall be ignored. MetalLB is an example of a solution for Kubernetes® that supports configuration of address pools for load balancer services.\n\n* NOTE 4: The loadBalancerIp and the addressPoolName attributes shall not be present at the same time.\n",
"type": "object",
"required": [
"type"
@@ -1201,6 +1213,10 @@
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.\n",
+ "type": "string"
}
}
}
@@ -1813,6 +1829,10 @@
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.\n",
+ "type": "string"
}
}
}
@@ -2167,7 +2187,7 @@
"type": "string",
"enum": [
"Deployment",
- "Statefulset"
+ "StatefulSet"
]
},
"desiredInstances": {
diff --git a/SOL002/VNFLifecycleManagement-API/schemas/VnfSnapshotsInfo.schema.json b/SOL002/VNFLifecycleManagement-API/schemas/VnfSnapshotsInfo.schema.json
index 7511c2097bb84ae6df599920d0287193740ae6f1..41c57dc764bc6ffb8c6f9a24cd647532e43ab333 100644
--- a/SOL002/VNFLifecycleManagement-API/schemas/VnfSnapshotsInfo.schema.json
+++ b/SOL002/VNFLifecycleManagement-API/schemas/VnfSnapshotsInfo.schema.json
@@ -360,6 +360,10 @@
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.\n",
+ "type": "string"
}
}
}
@@ -561,6 +565,10 @@
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.\n",
+ "type": "string"
}
}
}
@@ -791,6 +799,10 @@
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.\n",
+ "type": "string"
}
}
}
@@ -1025,7 +1037,7 @@
"description": "Map of instance data that need to be configured on the CP instances created from the respective CPD. The key of the map which identifies the individual VnfExtCpConfig entries is of type \"IdentifierInVnf\" and is managed by the NFVO. The entries shall be applied by the VNFM according to the rules of JSON Merge Patch (see IETF RFC 7396). See notes 2, 3 and 4.\n",
"type": "object",
"additionalProperties": {
- "description": "This type represents an externally provided link port, or a network attachment definition resource of secondary container cluster network, or network address information per instance of an external connection point. In the case of VM-based deployment of the VNFC exposing the external CP:\n 1. In case a link port is provided, the VNFM shall use that link port when connecting the external CP to the\n external VL.\n 2. In case a link port is not provided, the VNFM shall create a link port on the external VL and use that link port\n to connect the external CP to the external VL.\nIn the case of container-based deployment of the VNFC exposing the external CP, the VNFM shall use the network attachment definition resource of secondary container cluster network when connecting the CP to the external VL.\n* NOTE 1: The following conditions apply to the attributes \"linkPortId\" and \"cpProtocolData\" for an external CP\n instance connected or to be connected to a virtual network not categorized as secondary container cluster network:\n 1) Void.\n 2) At least one of the \"linkPortId\" and \"cpProtocolData\" attributes shall be present for an external CP instance\n representing a subport that is to be created, or an external CP instance that is to be created by creating the\n corresponding VNFC or VNF instance during the current or a subsequent LCM operation, or for an existing\n external CP instance that is to be re-configured or added to a particular external virtual link.\n 3) If the \"linkPortId\" attribute is absent, the VNFM shall create a link port.\n 4) If the \"cpProtocolData\" attribute is absent, the \"linkPortId\" attribute shall be provided referencing a\n precreated link port, and the VNFM can use means outside the scope of the present document to obtain the\n pre-configured address information for the connection point from the resource representing the link port.\n 5) If both \"cpProtocolData\" and \"linkportId\" are provided, the NFVO shall ensure that the\n cpProtocolData can be used with the pre-created link port referenced by \"linkPortId\".\n\n* NOTE 2: The following conditions apply to the attributes ΓÇ£netAttDefResourceIdΓÇ¥ and ΓÇ£cpProtocolDataΓÇ¥ for an external CP\n instance connected or to be connected to a secondary container cluster network:\n 1) The \"netAttDefResourceId\" and \"cpProtocolData\" attributes shall both be absent for the deletion of an\n existing external CP instance addressed by cpInstanceId.\n 2) The \"netAttDefResourceId\" attribute shall be present and the \"cpProtocolData\" attribute may be present for\n a to-be-created external CP instance or an existing external CP instance.\n* NOTE 3: Cardinality greater than 1 is only applicable for specific cases where more than one network attachment\n definition resource is needed to fulfil the connectivity requirements of the external CP, e.g. to build a link\n redundant mated pair in SR-IOV cases. When more than one netAttDefResourceId is indicated, all shall belong\n to the same namespace as defined by the corresponding \"netAttDefResourceNamespace\" attribute in the\n \"NetAttDefResourceData\".\n* NOTE 4: Either linkPortId or netAttDefResourceId may be included, but not both.\n",
+ "description": "This type represents an externally provided link port, or a network attachment definition resource of secondary container cluster network, or network address information per instance of an external connection point. In the case of VM-based deployment of the VNFC exposing the external CP:\n 1. In case a link port is provided, the VNFM shall use that link port when connecting the external CP to the\n external VL.\n 2. In case a link port is not provided, the VNFM shall create a link port on the external VL and use that link port\n to connect the external CP to the external VL.\nIn the case of container-based deployment of the VNFC exposing the external CP, the VNFM shall use the network attachment definition resource of secondary container cluster network when connecting the CP to the external VL.\n* NOTE 1: The following conditions apply to the attributes \"linkPortId\" and \"cpProtocolData\" for an external CP\n instance connected or to be connected to a virtual network not categorized as secondary container cluster network:\n 1) Void.\n 2) At least one of the \"linkPortId\" and \"cpProtocolData\" attributes shall be present for an external CP instance\n representing a subport that is to be created, or an external CP instance that is to be created by creating the\n corresponding VNFC or VNF instance during the current or a subsequent LCM operation, or for an existing\n external CP instance that is to be re-configured or added to a particular external virtual link.\n 3) If the \"linkPortId\" attribute is absent, the VNFM shall create a link port.\n 4) If the \"cpProtocolData\" attribute is absent, the \"linkPortId\" attribute shall be provided referencing a\n precreated link port, and the VNFM can use means outside the scope of the present document to obtain the\n pre-configured address information for the connection point from the resource representing the link port.\n 5) If both \"cpProtocolData\" and \"linkportId\" are provided, the NFVO shall ensure that the\n cpProtocolData can be used with the pre-created link port referenced by \"linkPortId\".\n\n* NOTE 2: The following conditions apply to the attributes ΓÇ£netAttDefResourceIdΓÇ¥ and ΓÇ£cpProtocolDataΓÇ¥ for an external CP\n instance connected or to be connected to a secondary container cluster network:\n 1) Void.\n 2) The \"netAttDefResourceId\" attribute shall be present and the \"cpProtocolData\" attribute may be present for\n a to-be-created external CP instance or an existing external CP instance.\n* NOTE 3: Cardinality greater than 1 is only applicable for specific cases where more than one network attachment\n definition resource is needed to fulfil the connectivity requirements of the external CP, e.g. to build a link\n redundant mated pair in SR-IOV cases. When more than one netAttDefResourceId is indicated, all shall belong\n to the same namespace as defined by the corresponding \"containerNamespace\" attribute in the\n \"resourceHandle\" attribute in the \"NetAttDefResourceData\".\n* NOTE 4: Either linkPortId or netAttDefResourceId may be included, but not both.\n",
"anyOf": [
{
"required": [
@@ -1185,7 +1197,7 @@
}
},
"virtualCpAddress": {
- "description": "This type represents information about a link port of an external VL, i.e. a port providing connectivity for the VNF to an NS VL.\n* NOTE 1: If the container cluster is set up to be able to configure an external load balancer this address will be used,\n otherwise it will be ignored by the CISM.\n\n* NOTE 2: In case the cluster can configure an external load balancer but no loadBalancerIp is provided the container\n cluster will assign an IP address.\n",
+ "description": "This type represents network address data for a virtual CP.\n* NOTE 1: If the container cluster is set up to be able to configure an external load balancer this address will be used,\n otherwise it will be ignored by the CISM.\n\n* NOTE 2: In case the cluster can configure an external load balancer but no loadBalancerIp is provided the container\n cluster will assign an IP address.\n\n* NOTE 3: The attribute is only relevant if the virtual CP is instantiated in a cluster that supports configuration of IP address pools for virtual CPs. Otherwise it shall be ignored. MetalLB is an example of a solution for Kubernetes® that supports configuration of address pools for load balancer services.\n\n* NOTE 4: The loadBalancerIp and the addressPoolName attributes shall not be present at the same time.\n",
"type": "object",
"required": [
"type"
@@ -1203,6 +1215,10 @@
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.\n",
+ "type": "string"
}
}
}
@@ -1815,6 +1831,10 @@
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.\n",
+ "type": "string"
}
}
}
@@ -2169,7 +2189,7 @@
"type": "string",
"enum": [
"Deployment",
- "Statefulset"
+ "StatefulSet"
]
},
"desiredInstances": {
diff --git a/SOL002/VNFLifecycleManagement-API/schemas/vnfInstance.schema.json b/SOL002/VNFLifecycleManagement-API/schemas/vnfInstance.schema.json
index eb86a9bb6e234d4814a22a061cb85bd69ae01fdd..c21a7b2237f757a8c49bd304d6a34232677a8208 100644
--- a/SOL002/VNFLifecycleManagement-API/schemas/vnfInstance.schema.json
+++ b/SOL002/VNFLifecycleManagement-API/schemas/vnfInstance.schema.json
@@ -309,6 +309,10 @@
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.\n",
+ "type": "string"
}
}
}
@@ -510,6 +514,10 @@
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.\n",
+ "type": "string"
}
}
}
@@ -740,6 +748,10 @@
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.\n",
+ "type": "string"
}
}
}
@@ -974,7 +986,7 @@
"description": "Map of instance data that need to be configured on the CP instances created from the respective CPD. The key of the map which identifies the individual VnfExtCpConfig entries is of type \"IdentifierInVnf\" and is managed by the NFVO. The entries shall be applied by the VNFM according to the rules of JSON Merge Patch (see IETF RFC 7396). See notes 2, 3 and 4.\n",
"type": "object",
"additionalProperties": {
- "description": "This type represents an externally provided link port, or a network attachment definition resource of secondary container cluster network, or network address information per instance of an external connection point. In the case of VM-based deployment of the VNFC exposing the external CP:\n 1. In case a link port is provided, the VNFM shall use that link port when connecting the external CP to the\n external VL.\n 2. In case a link port is not provided, the VNFM shall create a link port on the external VL and use that link port\n to connect the external CP to the external VL.\nIn the case of container-based deployment of the VNFC exposing the external CP, the VNFM shall use the network attachment definition resource of secondary container cluster network when connecting the CP to the external VL.\n* NOTE 1: The following conditions apply to the attributes \"linkPortId\" and \"cpProtocolData\" for an external CP\n instance connected or to be connected to a virtual network not categorized as secondary container cluster network:\n 1) Void.\n 2) At least one of the \"linkPortId\" and \"cpProtocolData\" attributes shall be present for an external CP instance\n representing a subport that is to be created, or an external CP instance that is to be created by creating the\n corresponding VNFC or VNF instance during the current or a subsequent LCM operation, or for an existing\n external CP instance that is to be re-configured or added to a particular external virtual link.\n 3) If the \"linkPortId\" attribute is absent, the VNFM shall create a link port.\n 4) If the \"cpProtocolData\" attribute is absent, the \"linkPortId\" attribute shall be provided referencing a\n precreated link port, and the VNFM can use means outside the scope of the present document to obtain the\n pre-configured address information for the connection point from the resource representing the link port.\n 5) If both \"cpProtocolData\" and \"linkportId\" are provided, the NFVO shall ensure that the\n cpProtocolData can be used with the pre-created link port referenced by \"linkPortId\".\n\n* NOTE 2: The following conditions apply to the attributes ΓÇ£netAttDefResourceIdΓÇ¥ and ΓÇ£cpProtocolDataΓÇ¥ for an external CP\n instance connected or to be connected to a secondary container cluster network:\n 1) The \"netAttDefResourceId\" and \"cpProtocolData\" attributes shall both be absent for the deletion of an\n existing external CP instance addressed by cpInstanceId.\n 2) The \"netAttDefResourceId\" attribute shall be present and the \"cpProtocolData\" attribute may be present for\n a to-be-created external CP instance or an existing external CP instance.\n* NOTE 3: Cardinality greater than 1 is only applicable for specific cases where more than one network attachment\n definition resource is needed to fulfil the connectivity requirements of the external CP, e.g. to build a link\n redundant mated pair in SR-IOV cases. When more than one netAttDefResourceId is indicated, all shall belong\n to the same namespace as defined by the corresponding \"netAttDefResourceNamespace\" attribute in the\n \"NetAttDefResourceData\".\n* NOTE 4: Either linkPortId or netAttDefResourceId may be included, but not both.\n",
+ "description": "This type represents an externally provided link port, or a network attachment definition resource of secondary container cluster network, or network address information per instance of an external connection point. In the case of VM-based deployment of the VNFC exposing the external CP:\n 1. In case a link port is provided, the VNFM shall use that link port when connecting the external CP to the\n external VL.\n 2. In case a link port is not provided, the VNFM shall create a link port on the external VL and use that link port\n to connect the external CP to the external VL.\nIn the case of container-based deployment of the VNFC exposing the external CP, the VNFM shall use the network attachment definition resource of secondary container cluster network when connecting the CP to the external VL.\n* NOTE 1: The following conditions apply to the attributes \"linkPortId\" and \"cpProtocolData\" for an external CP\n instance connected or to be connected to a virtual network not categorized as secondary container cluster network:\n 1) Void.\n 2) At least one of the \"linkPortId\" and \"cpProtocolData\" attributes shall be present for an external CP instance\n representing a subport that is to be created, or an external CP instance that is to be created by creating the\n corresponding VNFC or VNF instance during the current or a subsequent LCM operation, or for an existing\n external CP instance that is to be re-configured or added to a particular external virtual link.\n 3) If the \"linkPortId\" attribute is absent, the VNFM shall create a link port.\n 4) If the \"cpProtocolData\" attribute is absent, the \"linkPortId\" attribute shall be provided referencing a\n precreated link port, and the VNFM can use means outside the scope of the present document to obtain the\n pre-configured address information for the connection point from the resource representing the link port.\n 5) If both \"cpProtocolData\" and \"linkportId\" are provided, the NFVO shall ensure that the\n cpProtocolData can be used with the pre-created link port referenced by \"linkPortId\".\n\n* NOTE 2: The following conditions apply to the attributes ΓÇ£netAttDefResourceIdΓÇ¥ and ΓÇ£cpProtocolDataΓÇ¥ for an external CP\n instance connected or to be connected to a secondary container cluster network:\n 1) Void.\n 2) The \"netAttDefResourceId\" attribute shall be present and the \"cpProtocolData\" attribute may be present for\n a to-be-created external CP instance or an existing external CP instance.\n* NOTE 3: Cardinality greater than 1 is only applicable for specific cases where more than one network attachment\n definition resource is needed to fulfil the connectivity requirements of the external CP, e.g. to build a link\n redundant mated pair in SR-IOV cases. When more than one netAttDefResourceId is indicated, all shall belong\n to the same namespace as defined by the corresponding \"containerNamespace\" attribute in the\n \"resourceHandle\" attribute in the \"NetAttDefResourceData\".\n* NOTE 4: Either linkPortId or netAttDefResourceId may be included, but not both.\n",
"anyOf": [
{
"required": [
@@ -1134,7 +1146,7 @@
}
},
"virtualCpAddress": {
- "description": "This type represents information about a link port of an external VL, i.e. a port providing connectivity for the VNF to an NS VL.\n* NOTE 1: If the container cluster is set up to be able to configure an external load balancer this address will be used,\n otherwise it will be ignored by the CISM.\n\n* NOTE 2: In case the cluster can configure an external load balancer but no loadBalancerIp is provided the container\n cluster will assign an IP address.\n",
+ "description": "This type represents network address data for a virtual CP.\n* NOTE 1: If the container cluster is set up to be able to configure an external load balancer this address will be used,\n otherwise it will be ignored by the CISM.\n\n* NOTE 2: In case the cluster can configure an external load balancer but no loadBalancerIp is provided the container\n cluster will assign an IP address.\n\n* NOTE 3: The attribute is only relevant if the virtual CP is instantiated in a cluster that supports configuration of IP address pools for virtual CPs. Otherwise it shall be ignored. MetalLB is an example of a solution for Kubernetes® that supports configuration of address pools for load balancer services.\n\n* NOTE 4: The loadBalancerIp and the addressPoolName attributes shall not be present at the same time.\n",
"type": "object",
"required": [
"type"
@@ -1152,6 +1164,10 @@
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.\n",
+ "type": "string"
}
}
}
@@ -1764,6 +1780,10 @@
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.\n",
+ "type": "string"
}
}
}
@@ -2118,7 +2138,7 @@
"type": "string",
"enum": [
"Deployment",
- "Statefulset"
+ "StatefulSet"
]
},
"desiredInstances": {
diff --git a/SOL002/VNFLifecycleManagement-API/schemas/vnfInstances.schema.json b/SOL002/VNFLifecycleManagement-API/schemas/vnfInstances.schema.json
index 0b112657efa5cb4701761b670a6498321307ab72..d3ed91261a4acaf62de1e2fd7b5c5a0a8db7f984 100644
--- a/SOL002/VNFLifecycleManagement-API/schemas/vnfInstances.schema.json
+++ b/SOL002/VNFLifecycleManagement-API/schemas/vnfInstances.schema.json
@@ -311,6 +311,10 @@
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.\n",
+ "type": "string"
}
}
}
@@ -512,6 +516,10 @@
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.\n",
+ "type": "string"
}
}
}
@@ -742,6 +750,10 @@
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.\n",
+ "type": "string"
}
}
}
@@ -976,7 +988,7 @@
"description": "Map of instance data that need to be configured on the CP instances created from the respective CPD. The key of the map which identifies the individual VnfExtCpConfig entries is of type \"IdentifierInVnf\" and is managed by the NFVO. The entries shall be applied by the VNFM according to the rules of JSON Merge Patch (see IETF RFC 7396). See notes 2, 3 and 4.\n",
"type": "object",
"additionalProperties": {
- "description": "This type represents an externally provided link port, or a network attachment definition resource of secondary container cluster network, or network address information per instance of an external connection point. In the case of VM-based deployment of the VNFC exposing the external CP:\n 1. In case a link port is provided, the VNFM shall use that link port when connecting the external CP to the\n external VL.\n 2. In case a link port is not provided, the VNFM shall create a link port on the external VL and use that link port\n to connect the external CP to the external VL.\nIn the case of container-based deployment of the VNFC exposing the external CP, the VNFM shall use the network attachment definition resource of secondary container cluster network when connecting the CP to the external VL.\n* NOTE 1: The following conditions apply to the attributes \"linkPortId\" and \"cpProtocolData\" for an external CP\n instance connected or to be connected to a virtual network not categorized as secondary container cluster network:\n 1) Void.\n 2) At least one of the \"linkPortId\" and \"cpProtocolData\" attributes shall be present for an external CP instance\n representing a subport that is to be created, or an external CP instance that is to be created by creating the\n corresponding VNFC or VNF instance during the current or a subsequent LCM operation, or for an existing\n external CP instance that is to be re-configured or added to a particular external virtual link.\n 3) If the \"linkPortId\" attribute is absent, the VNFM shall create a link port.\n 4) If the \"cpProtocolData\" attribute is absent, the \"linkPortId\" attribute shall be provided referencing a\n precreated link port, and the VNFM can use means outside the scope of the present document to obtain the\n pre-configured address information for the connection point from the resource representing the link port.\n 5) If both \"cpProtocolData\" and \"linkportId\" are provided, the NFVO shall ensure that the\n cpProtocolData can be used with the pre-created link port referenced by \"linkPortId\".\n\n* NOTE 2: The following conditions apply to the attributes ΓÇ£netAttDefResourceIdΓÇ¥ and ΓÇ£cpProtocolDataΓÇ¥ for an external CP\n instance connected or to be connected to a secondary container cluster network:\n 1) The \"netAttDefResourceId\" and \"cpProtocolData\" attributes shall both be absent for the deletion of an\n existing external CP instance addressed by cpInstanceId.\n 2) The \"netAttDefResourceId\" attribute shall be present and the \"cpProtocolData\" attribute may be present for\n a to-be-created external CP instance or an existing external CP instance.\n* NOTE 3: Cardinality greater than 1 is only applicable for specific cases where more than one network attachment\n definition resource is needed to fulfil the connectivity requirements of the external CP, e.g. to build a link\n redundant mated pair in SR-IOV cases. When more than one netAttDefResourceId is indicated, all shall belong\n to the same namespace as defined by the corresponding \"netAttDefResourceNamespace\" attribute in the\n \"NetAttDefResourceData\".\n* NOTE 4: Either linkPortId or netAttDefResourceId may be included, but not both.\n",
+ "description": "This type represents an externally provided link port, or a network attachment definition resource of secondary container cluster network, or network address information per instance of an external connection point. In the case of VM-based deployment of the VNFC exposing the external CP:\n 1. In case a link port is provided, the VNFM shall use that link port when connecting the external CP to the\n external VL.\n 2. In case a link port is not provided, the VNFM shall create a link port on the external VL and use that link port\n to connect the external CP to the external VL.\nIn the case of container-based deployment of the VNFC exposing the external CP, the VNFM shall use the network attachment definition resource of secondary container cluster network when connecting the CP to the external VL.\n* NOTE 1: The following conditions apply to the attributes \"linkPortId\" and \"cpProtocolData\" for an external CP\n instance connected or to be connected to a virtual network not categorized as secondary container cluster network:\n 1) Void.\n 2) At least one of the \"linkPortId\" and \"cpProtocolData\" attributes shall be present for an external CP instance\n representing a subport that is to be created, or an external CP instance that is to be created by creating the\n corresponding VNFC or VNF instance during the current or a subsequent LCM operation, or for an existing\n external CP instance that is to be re-configured or added to a particular external virtual link.\n 3) If the \"linkPortId\" attribute is absent, the VNFM shall create a link port.\n 4) If the \"cpProtocolData\" attribute is absent, the \"linkPortId\" attribute shall be provided referencing a\n precreated link port, and the VNFM can use means outside the scope of the present document to obtain the\n pre-configured address information for the connection point from the resource representing the link port.\n 5) If both \"cpProtocolData\" and \"linkportId\" are provided, the NFVO shall ensure that the\n cpProtocolData can be used with the pre-created link port referenced by \"linkPortId\".\n\n* NOTE 2: The following conditions apply to the attributes ΓÇ£netAttDefResourceIdΓÇ¥ and ΓÇ£cpProtocolDataΓÇ¥ for an external CP\n instance connected or to be connected to a secondary container cluster network:\n 1) Void.\n 2) The \"netAttDefResourceId\" attribute shall be present and the \"cpProtocolData\" attribute may be present for\n a to-be-created external CP instance or an existing external CP instance.\n* NOTE 3: Cardinality greater than 1 is only applicable for specific cases where more than one network attachment\n definition resource is needed to fulfil the connectivity requirements of the external CP, e.g. to build a link\n redundant mated pair in SR-IOV cases. When more than one netAttDefResourceId is indicated, all shall belong\n to the same namespace as defined by the corresponding \"containerNamespace\" attribute in the\n \"resourceHandle\" attribute in the \"NetAttDefResourceData\".\n* NOTE 4: Either linkPortId or netAttDefResourceId may be included, but not both.\n",
"anyOf": [
{
"required": [
@@ -1136,7 +1148,7 @@
}
},
"virtualCpAddress": {
- "description": "This type represents information about a link port of an external VL, i.e. a port providing connectivity for the VNF to an NS VL.\n* NOTE 1: If the container cluster is set up to be able to configure an external load balancer this address will be used,\n otherwise it will be ignored by the CISM.\n\n* NOTE 2: In case the cluster can configure an external load balancer but no loadBalancerIp is provided the container\n cluster will assign an IP address.\n",
+ "description": "This type represents network address data for a virtual CP.\n* NOTE 1: If the container cluster is set up to be able to configure an external load balancer this address will be used,\n otherwise it will be ignored by the CISM.\n\n* NOTE 2: In case the cluster can configure an external load balancer but no loadBalancerIp is provided the container\n cluster will assign an IP address.\n\n* NOTE 3: The attribute is only relevant if the virtual CP is instantiated in a cluster that supports configuration of IP address pools for virtual CPs. Otherwise it shall be ignored. MetalLB is an example of a solution for Kubernetes® that supports configuration of address pools for load balancer services.\n\n* NOTE 4: The loadBalancerIp and the addressPoolName attributes shall not be present at the same time.\n",
"type": "object",
"required": [
"type"
@@ -1154,6 +1166,10 @@
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.\n",
+ "type": "string"
}
}
}
@@ -1766,6 +1782,10 @@
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.\n",
+ "type": "string"
}
}
}
@@ -2120,7 +2140,7 @@
"type": "string",
"enum": [
"Deployment",
- "Statefulset"
+ "StatefulSet"
]
},
"desiredInstances": {
diff --git a/SOL002/VNFLifecycleManagement-API/schemas/vnfLcmOpOcc.schema.json b/SOL002/VNFLifecycleManagement-API/schemas/vnfLcmOpOcc.schema.json
index a28e3312b7096d742102454fce9e831686809784..465863abff367dd7997d6904d67699b68eb92561 100644
--- a/SOL002/VNFLifecycleManagement-API/schemas/vnfLcmOpOcc.schema.json
+++ b/SOL002/VNFLifecycleManagement-API/schemas/vnfLcmOpOcc.schema.json
@@ -288,7 +288,7 @@
"resourceId"
],
"type": "object",
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance. Information about the resource is available from the VIM.\n* NOTE 1: The information about the VIM or CISM connection referenced by the VIM connection id is known to the\n VNFM. Moreover, the identifier of the VIM connection provides scope to the resourceId.\n\n* NOTE 2: The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or CISM or the resource \n provider and can be used as information that complements the ResourceHandle. When the container\n infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would \n correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, \n PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 3: When the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the \n following way:\n - For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide \n per resource type.\n - For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, \n i.e. the value of the 'claimName' field in the Kubernetes® manifest, or a compound name built by \n Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own \n manifest.\n - For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of \n the 'metadata.name' field in Kubernetes® manifest.\n",
+ "description": "This type represents the information that allows addressing a virtualised resource or Network MCIO that is used by a VNF instance. Information about the resource is available from the VIM or the CISM.\n* NOTE 1: The information about the VIM or CISM connection referenced by the VIM connection id is known to the\n VNFM. Moreover, the identifier of the VIM connection provides scope to the resourceId.\n\n* NOTE 2: The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or CISM or the resource \n provider and can be used as information that complements the ResourceHandle. When the container\n infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would \n correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, \n PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 3: When the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the \n following way:\n - For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide \n per resource type.\n - For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, \n i.e. the value of the 'claimName' field in the Kubernetes® manifest, or a compound name built by \n Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own \n manifest.\n - For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of \n the 'metadata.name' field in Kubernetes® manifest.\n",
"properties": {
"vimConnectionId": {
"description": "An identifier with the intention of being globally unique.\n",
@@ -465,7 +465,7 @@
"resourceId"
],
"type": "object",
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance. Information about the resource is available from the VIM.\n* NOTE 1: The information about the VIM or CISM connection referenced by the VIM connection id is known to the\n VNFM. Moreover, the identifier of the VIM connection provides scope to the resourceId.\n\n* NOTE 2: The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or CISM or the resource \n provider and can be used as information that complements the ResourceHandle. When the container\n infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would \n correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, \n PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 3: When the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the \n following way:\n - For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide \n per resource type.\n - For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, \n i.e. the value of the 'claimName' field in the Kubernetes® manifest, or a compound name built by \n Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own \n manifest.\n - For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of \n the 'metadata.name' field in Kubernetes® manifest.\n",
+ "description": "This type represents the information that allows addressing a virtualised resource or Storage MCIO that is used by a VNF instance. Information about the resource is available from the VIM or the CISM.\n* NOTE 1: The information about the VIM or CISM connection referenced by the VIM connection id is known to the\n VNFM. Moreover, the identifier of the VIM connection provides scope to the resourceId.\n\n* NOTE 2: The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or CISM or the resource \n provider and can be used as information that complements the ResourceHandle. When the container\n infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would \n correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, \n PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 3: When the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the \n following way:\n - For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide \n per resource type.\n - For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, \n i.e. the value of the 'claimName' field in the Kubernetes® manifest, or a compound name built by \n Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own \n manifest.\n - For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of \n the 'metadata.name' field in Kubernetes® manifest.\n",
"properties": {
"vimConnectionId": {
"description": "An identifier with the intention of being globally unique.\n",
@@ -778,7 +778,7 @@
"description": "Map of instance data that need to be configured on the CP instances created from the respective CPD. The key of the map which identifies the individual VnfExtCpConfig entries is of type \"IdentifierInVnf\" and is managed by the NFVO. The entries shall be applied by the VNFM according to the rules of JSON Merge Patch (see IETF RFC 7396). See notes 2, 3 and 4.\n",
"type": "object",
"additionalProperties": {
- "description": "This type represents an externally provided link port, or a network attachment definition resource of secondary container cluster network, or network address information per instance of an external connection point. In the case of VM-based deployment of the VNFC exposing the external CP:\n 1. In case a link port is provided, the VNFM shall use that link port when connecting the external CP to the\n external VL.\n 2. In case a link port is not provided, the VNFM shall create a link port on the external VL and use that link port\n to connect the external CP to the external VL.\nIn the case of container-based deployment of the VNFC exposing the external CP, the VNFM shall use the network attachment definition resource of secondary container cluster network when connecting the CP to the external VL.\n* NOTE 1: The following conditions apply to the attributes \"linkPortId\" and \"cpProtocolData\" for an external CP\n instance connected or to be connected to a virtual network not categorized as secondary container cluster network:\n 1) Void.\n 2) At least one of the \"linkPortId\" and \"cpProtocolData\" attributes shall be present for an external CP instance\n representing a subport that is to be created, or an external CP instance that is to be created by creating the\n corresponding VNFC or VNF instance during the current or a subsequent LCM operation, or for an existing\n external CP instance that is to be re-configured or added to a particular external virtual link.\n 3) If the \"linkPortId\" attribute is absent, the VNFM shall create a link port.\n 4) If the \"cpProtocolData\" attribute is absent, the \"linkPortId\" attribute shall be provided referencing a\n precreated link port, and the VNFM can use means outside the scope of the present document to obtain the\n pre-configured address information for the connection point from the resource representing the link port.\n 5) If both \"cpProtocolData\" and \"linkportId\" are provided, the NFVO shall ensure that the\n cpProtocolData can be used with the pre-created link port referenced by \"linkPortId\".\n\n* NOTE 2: The following conditions apply to the attributes ΓÇ£netAttDefResourceIdΓÇ¥ and ΓÇ£cpProtocolDataΓÇ¥ for an external CP\n instance connected or to be connected to a secondary container cluster network:\n 1) The \"netAttDefResourceId\" and \"cpProtocolData\" attributes shall both be absent for the deletion of an\n existing external CP instance addressed by cpInstanceId.\n 2) The \"netAttDefResourceId\" attribute shall be present and the \"cpProtocolData\" attribute may be present for\n a to-be-created external CP instance or an existing external CP instance.\n* NOTE 3: Cardinality greater than 1 is only applicable for specific cases where more than one network attachment\n definition resource is needed to fulfil the connectivity requirements of the external CP, e.g. to build a link\n redundant mated pair in SR-IOV cases. When more than one netAttDefResourceId is indicated, all shall belong\n to the same namespace as defined by the corresponding \"netAttDefResourceNamespace\" attribute in the\n \"NetAttDefResourceData\".\n* NOTE 4: Either linkPortId or netAttDefResourceId may be included, but not both.\n",
+ "description": "This type represents an externally provided link port, or a network attachment definition resource of secondary container cluster network, or network address information per instance of an external connection point. In the case of VM-based deployment of the VNFC exposing the external CP:\n 1. In case a link port is provided, the VNFM shall use that link port when connecting the external CP to the\n external VL.\n 2. In case a link port is not provided, the VNFM shall create a link port on the external VL and use that link port\n to connect the external CP to the external VL.\nIn the case of container-based deployment of the VNFC exposing the external CP, the VNFM shall use the network attachment definition resource of secondary container cluster network when connecting the CP to the external VL.\n* NOTE 1: The following conditions apply to the attributes \"linkPortId\" and \"cpProtocolData\" for an external CP\n instance connected or to be connected to a virtual network not categorized as secondary container cluster network:\n 1) Void.\n 2) At least one of the \"linkPortId\" and \"cpProtocolData\" attributes shall be present for an external CP instance\n representing a subport that is to be created, or an external CP instance that is to be created by creating the\n corresponding VNFC or VNF instance during the current or a subsequent LCM operation, or for an existing\n external CP instance that is to be re-configured or added to a particular external virtual link.\n 3) If the \"linkPortId\" attribute is absent, the VNFM shall create a link port.\n 4) If the \"cpProtocolData\" attribute is absent, the \"linkPortId\" attribute shall be provided referencing a\n precreated link port, and the VNFM can use means outside the scope of the present document to obtain the\n pre-configured address information for the connection point from the resource representing the link port.\n 5) If both \"cpProtocolData\" and \"linkportId\" are provided, the NFVO shall ensure that the\n cpProtocolData can be used with the pre-created link port referenced by \"linkPortId\".\n\n* NOTE 2: The following conditions apply to the attributes ΓÇ£netAttDefResourceIdΓÇ¥ and ΓÇ£cpProtocolDataΓÇ¥ for an external CP\n instance connected or to be connected to a secondary container cluster network:\n 1) Void.\n 2) The \"netAttDefResourceId\" attribute shall be present and the \"cpProtocolData\" attribute may be present for\n a to-be-created external CP instance or an existing external CP instance.\n* NOTE 3: Cardinality greater than 1 is only applicable for specific cases where more than one network attachment\n definition resource is needed to fulfil the connectivity requirements of the external CP, e.g. to build a link\n redundant mated pair in SR-IOV cases. When more than one netAttDefResourceId is indicated, all shall belong\n to the same namespace as defined by the corresponding \"containerNamespace\" attribute in the\n \"resourceHandle\" attribute in the \"NetAttDefResourceData\".\n* NOTE 4: Either linkPortId or netAttDefResourceId may be included, but not both.\n",
"anyOf": [
{
"required": [
@@ -938,7 +938,7 @@
}
},
"virtualCpAddress": {
- "description": "This type represents information about a link port of an external VL, i.e. a port providing connectivity for the VNF to an NS VL.\n* NOTE 1: If the container cluster is set up to be able to configure an external load balancer this address will be used,\n otherwise it will be ignored by the CISM.\n\n* NOTE 2: In case the cluster can configure an external load balancer but no loadBalancerIp is provided the container\n cluster will assign an IP address.\n",
+ "description": "This type represents network address data for a virtual CP.\n* NOTE 1: If the container cluster is set up to be able to configure an external load balancer this address will be used,\n otherwise it will be ignored by the CISM.\n\n* NOTE 2: In case the cluster can configure an external load balancer but no loadBalancerIp is provided the container\n cluster will assign an IP address.\n\n* NOTE 3: The attribute is only relevant if the virtual CP is instantiated in a cluster that supports configuration of IP address pools for virtual CPs. Otherwise it shall be ignored. MetalLB is an example of a solution for Kubernetes® that supports configuration of address pools for load balancer services.\n\n* NOTE 4: The loadBalancerIp and the addressPoolName attributes shall not be present at the same time.\n",
"type": "object",
"required": [
"type"
@@ -956,6 +956,10 @@
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.\n",
+ "type": "string"
}
}
}
diff --git a/SOL002/VNFLifecycleManagement-API/schemas/vnfLcmOpOccs.schema.json b/SOL002/VNFLifecycleManagement-API/schemas/vnfLcmOpOccs.schema.json
index f573bc5d1195abc46e13e4850500a29d3bd51903..197ffe0469f2cdeab98a1a28da65532ba4b94920 100644
--- a/SOL002/VNFLifecycleManagement-API/schemas/vnfLcmOpOccs.schema.json
+++ b/SOL002/VNFLifecycleManagement-API/schemas/vnfLcmOpOccs.schema.json
@@ -290,7 +290,7 @@
"resourceId"
],
"type": "object",
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance. Information about the resource is available from the VIM.\n* NOTE 1: The information about the VIM or CISM connection referenced by the VIM connection id is known to the\n VNFM. Moreover, the identifier of the VIM connection provides scope to the resourceId.\n\n* NOTE 2: The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or CISM or the resource \n provider and can be used as information that complements the ResourceHandle. When the container\n infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would \n correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, \n PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 3: When the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the \n following way:\n - For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide \n per resource type.\n - For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, \n i.e. the value of the 'claimName' field in the Kubernetes® manifest, or a compound name built by \n Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own \n manifest.\n - For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of \n the 'metadata.name' field in Kubernetes® manifest.\n",
+ "description": "This type represents the information that allows addressing a virtualised resource or Network MCIO that is used by a VNF instance. Information about the resource is available from the VIM or the CISM.\n* NOTE 1: The information about the VIM or CISM connection referenced by the VIM connection id is known to the\n VNFM. Moreover, the identifier of the VIM connection provides scope to the resourceId.\n\n* NOTE 2: The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or CISM or the resource \n provider and can be used as information that complements the ResourceHandle. When the container\n infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would \n correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, \n PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 3: When the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the \n following way:\n - For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide \n per resource type.\n - For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, \n i.e. the value of the 'claimName' field in the Kubernetes® manifest, or a compound name built by \n Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own \n manifest.\n - For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of \n the 'metadata.name' field in Kubernetes® manifest.\n",
"properties": {
"vimConnectionId": {
"description": "An identifier with the intention of being globally unique.\n",
@@ -467,7 +467,7 @@
"resourceId"
],
"type": "object",
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance. Information about the resource is available from the VIM.\n* NOTE 1: The information about the VIM or CISM connection referenced by the VIM connection id is known to the\n VNFM. Moreover, the identifier of the VIM connection provides scope to the resourceId.\n\n* NOTE 2: The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or CISM or the resource \n provider and can be used as information that complements the ResourceHandle. When the container\n infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would \n correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, \n PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 3: When the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the \n following way:\n - For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide \n per resource type.\n - For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, \n i.e. the value of the 'claimName' field in the Kubernetes® manifest, or a compound name built by \n Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own \n manifest.\n - For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of \n the 'metadata.name' field in Kubernetes® manifest.\n",
+ "description": "This type represents the information that allows addressing a virtualised resource or Storage MCIO that is used by a VNF instance. Information about the resource is available from the VIM or the CISM.\n* NOTE 1: The information about the VIM or CISM connection referenced by the VIM connection id is known to the\n VNFM. Moreover, the identifier of the VIM connection provides scope to the resourceId.\n\n* NOTE 2: The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or CISM or the resource \n provider and can be used as information that complements the ResourceHandle. When the container\n infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would \n correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, \n PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 3: When the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the \n following way:\n - For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide \n per resource type.\n - For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, \n i.e. the value of the 'claimName' field in the Kubernetes® manifest, or a compound name built by \n Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own \n manifest.\n - For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of \n the 'metadata.name' field in Kubernetes® manifest.\n",
"properties": {
"vimConnectionId": {
"description": "An identifier with the intention of being globally unique.\n",
@@ -780,7 +780,7 @@
"description": "Map of instance data that need to be configured on the CP instances created from the respective CPD. The key of the map which identifies the individual VnfExtCpConfig entries is of type \"IdentifierInVnf\" and is managed by the NFVO. The entries shall be applied by the VNFM according to the rules of JSON Merge Patch (see IETF RFC 7396). See notes 2, 3 and 4.\n",
"type": "object",
"additionalProperties": {
- "description": "This type represents an externally provided link port, or a network attachment definition resource of secondary container cluster network, or network address information per instance of an external connection point. In the case of VM-based deployment of the VNFC exposing the external CP:\n 1. In case a link port is provided, the VNFM shall use that link port when connecting the external CP to the\n external VL.\n 2. In case a link port is not provided, the VNFM shall create a link port on the external VL and use that link port\n to connect the external CP to the external VL.\nIn the case of container-based deployment of the VNFC exposing the external CP, the VNFM shall use the network attachment definition resource of secondary container cluster network when connecting the CP to the external VL.\n* NOTE 1: The following conditions apply to the attributes \"linkPortId\" and \"cpProtocolData\" for an external CP\n instance connected or to be connected to a virtual network not categorized as secondary container cluster network:\n 1) Void.\n 2) At least one of the \"linkPortId\" and \"cpProtocolData\" attributes shall be present for an external CP instance\n representing a subport that is to be created, or an external CP instance that is to be created by creating the\n corresponding VNFC or VNF instance during the current or a subsequent LCM operation, or for an existing\n external CP instance that is to be re-configured or added to a particular external virtual link.\n 3) If the \"linkPortId\" attribute is absent, the VNFM shall create a link port.\n 4) If the \"cpProtocolData\" attribute is absent, the \"linkPortId\" attribute shall be provided referencing a\n precreated link port, and the VNFM can use means outside the scope of the present document to obtain the\n pre-configured address information for the connection point from the resource representing the link port.\n 5) If both \"cpProtocolData\" and \"linkportId\" are provided, the NFVO shall ensure that the\n cpProtocolData can be used with the pre-created link port referenced by \"linkPortId\".\n\n* NOTE 2: The following conditions apply to the attributes ΓÇ£netAttDefResourceIdΓÇ¥ and ΓÇ£cpProtocolDataΓÇ¥ for an external CP\n instance connected or to be connected to a secondary container cluster network:\n 1) The \"netAttDefResourceId\" and \"cpProtocolData\" attributes shall both be absent for the deletion of an\n existing external CP instance addressed by cpInstanceId.\n 2) The \"netAttDefResourceId\" attribute shall be present and the \"cpProtocolData\" attribute may be present for\n a to-be-created external CP instance or an existing external CP instance.\n* NOTE 3: Cardinality greater than 1 is only applicable for specific cases where more than one network attachment\n definition resource is needed to fulfil the connectivity requirements of the external CP, e.g. to build a link\n redundant mated pair in SR-IOV cases. When more than one netAttDefResourceId is indicated, all shall belong\n to the same namespace as defined by the corresponding \"netAttDefResourceNamespace\" attribute in the\n \"NetAttDefResourceData\".\n* NOTE 4: Either linkPortId or netAttDefResourceId may be included, but not both.\n",
+ "description": "This type represents an externally provided link port, or a network attachment definition resource of secondary container cluster network, or network address information per instance of an external connection point. In the case of VM-based deployment of the VNFC exposing the external CP:\n 1. In case a link port is provided, the VNFM shall use that link port when connecting the external CP to the\n external VL.\n 2. In case a link port is not provided, the VNFM shall create a link port on the external VL and use that link port\n to connect the external CP to the external VL.\nIn the case of container-based deployment of the VNFC exposing the external CP, the VNFM shall use the network attachment definition resource of secondary container cluster network when connecting the CP to the external VL.\n* NOTE 1: The following conditions apply to the attributes \"linkPortId\" and \"cpProtocolData\" for an external CP\n instance connected or to be connected to a virtual network not categorized as secondary container cluster network:\n 1) Void.\n 2) At least one of the \"linkPortId\" and \"cpProtocolData\" attributes shall be present for an external CP instance\n representing a subport that is to be created, or an external CP instance that is to be created by creating the\n corresponding VNFC or VNF instance during the current or a subsequent LCM operation, or for an existing\n external CP instance that is to be re-configured or added to a particular external virtual link.\n 3) If the \"linkPortId\" attribute is absent, the VNFM shall create a link port.\n 4) If the \"cpProtocolData\" attribute is absent, the \"linkPortId\" attribute shall be provided referencing a\n precreated link port, and the VNFM can use means outside the scope of the present document to obtain the\n pre-configured address information for the connection point from the resource representing the link port.\n 5) If both \"cpProtocolData\" and \"linkportId\" are provided, the NFVO shall ensure that the\n cpProtocolData can be used with the pre-created link port referenced by \"linkPortId\".\n\n* NOTE 2: The following conditions apply to the attributes ΓÇ£netAttDefResourceIdΓÇ¥ and ΓÇ£cpProtocolDataΓÇ¥ for an external CP\n instance connected or to be connected to a secondary container cluster network:\n 1) Void.\n 2) The \"netAttDefResourceId\" attribute shall be present and the \"cpProtocolData\" attribute may be present for\n a to-be-created external CP instance or an existing external CP instance.\n* NOTE 3: Cardinality greater than 1 is only applicable for specific cases where more than one network attachment\n definition resource is needed to fulfil the connectivity requirements of the external CP, e.g. to build a link\n redundant mated pair in SR-IOV cases. When more than one netAttDefResourceId is indicated, all shall belong\n to the same namespace as defined by the corresponding \"containerNamespace\" attribute in the\n \"resourceHandle\" attribute in the \"NetAttDefResourceData\".\n* NOTE 4: Either linkPortId or netAttDefResourceId may be included, but not both.\n",
"anyOf": [
{
"required": [
@@ -940,7 +940,7 @@
}
},
"virtualCpAddress": {
- "description": "This type represents information about a link port of an external VL, i.e. a port providing connectivity for the VNF to an NS VL.\n* NOTE 1: If the container cluster is set up to be able to configure an external load balancer this address will be used,\n otherwise it will be ignored by the CISM.\n\n* NOTE 2: In case the cluster can configure an external load balancer but no loadBalancerIp is provided the container\n cluster will assign an IP address.\n",
+ "description": "This type represents network address data for a virtual CP.\n* NOTE 1: If the container cluster is set up to be able to configure an external load balancer this address will be used,\n otherwise it will be ignored by the CISM.\n\n* NOTE 2: In case the cluster can configure an external load balancer but no loadBalancerIp is provided the container\n cluster will assign an IP address.\n\n* NOTE 3: The attribute is only relevant if the virtual CP is instantiated in a cluster that supports configuration of IP address pools for virtual CPs. Otherwise it shall be ignored. MetalLB is an example of a solution for Kubernetes® that supports configuration of address pools for load balancer services.\n\n* NOTE 4: The loadBalancerIp and the addressPoolName attributes shall not be present at the same time.\n",
"type": "object",
"required": [
"type"
@@ -958,6 +958,10 @@
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.\n",
+ "type": "string"
}
}
}
diff --git a/SOL002/VNFPerformanceManagement-API/ApiVersion.robot b/SOL002/VNFPerformanceManagement-API/ApiVersion.robot
index 359048058f864d71e7eb3f10eb3aee3b7272af92..7a5bda58ea7a241c54de6896a463bf0444ecbc7d 100644
--- a/SOL002/VNFPerformanceManagement-API/ApiVersion.robot
+++ b/SOL002/VNFPerformanceManagement-API/ApiVersion.robot
@@ -11,7 +11,7 @@ POST API Version - Method not implemented
... Test title: POST API version - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -23,7 +23,7 @@ GET API Version
... Test title: GET API Version
... Test objective: The objective is to test that GET method successfully return ApiVersionInformation
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -36,7 +36,7 @@ PUT API Version - Method not implemented
... Test title: PUT API Version - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -48,7 +48,7 @@ PATCH API Version - Method not implemented
... Test title: PATCH API Version - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -60,7 +60,7 @@ DELETE API Version - Method not implemented
... Test title: DELETE API Version - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -72,7 +72,7 @@ POST API Version with apiMajorVerion - Method not implemented
... Test title: POST API version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -84,7 +84,7 @@ GET API Version with apiMajorVerion
... Test title: GET API Version with apiMajorVerion
... Test objective: The objective is to test that GET method successfully return ApiVersionInformation
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -97,7 +97,7 @@ PUT API Version with apiMajorVerion - Method not implemented
... Test title: PUT API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -109,7 +109,7 @@ PATCH API Version with apiMajorVerion - Method not implemented
... Test title: PATCH API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -121,7 +121,7 @@ DELETE API Version with apiMajorVerion - Method not implemented
... Test title: DELETE API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL002/VNFPerformanceManagement-API/IndividualPmJob.robot b/SOL002/VNFPerformanceManagement-API/IndividualPmJob.robot
index 4e73e9b703ddb1d2aa8ab85ea06d74fb7761d56b..d02951365b798aa08277dc4d84b79909d8069a21 100644
--- a/SOL002/VNFPerformanceManagement-API/IndividualPmJob.robot
+++ b/SOL002/VNFPerformanceManagement-API/IndividualPmJob.robot
@@ -13,7 +13,7 @@ GET individual VNF Performance Job
... Test title: Get individual VNF Performance Job
... Test objective: The objective is to test the retrieval of an individual VNF performance monitoring job and perform a JSON schema and content validation of the collected job data structure
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance jobs are set in the VNFM.
- ... Reference: Clause 6.4.3.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 6.4.3.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -28,7 +28,7 @@ GET individual VNF Performance Job with invalid resource identifier
... Test title: Get individual VNF Performance Job with invalid resource identifier
... Test objective: The objective is to test that the retrieval of an individual VNF performance monitoring job fails when using an invalid resource identifier, and perform the JSON schema validation of the failed operation HTTP response
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance jobs are set in the VNFM.
- ... Reference: Clause 6.4.3.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 6.4.3.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -41,7 +41,7 @@ DELETE Individual VNF Performance Job
... Test title: Delete Individual VNF Performance Job
... Test objective: The objective is to test the deletion of an individual VNF performance monitoring job
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance jobs are set in the VNFM.
- ... Reference: Clause 6.4.3.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 6.4.3.3.5 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: The VNF Performance Job is no more available in the VNFM
@@ -54,7 +54,7 @@ DELETE Individual VNF Performance Job with invalid resource identifier
... Test title: Delete individual VNF Performance Job with invalid resource identifier
... Test objective: The objective is to test that the deletion of an individual VNF performance monitoring job fails when using an invalid resource identifier, and perform the JSON schema validation of the failed operation HTTP response
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance jobs are set in the VNFM.
- ... Reference: Clause 6.4.3.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 6.4.3.3.5 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -67,7 +67,7 @@ POST Individual VNF Performance Job - Method not implemented
... Test title: POST Individual VNF Performance Job - method not implemented
... Test objective: The objective is to test that POST method is not allowed to create a new VNF Performance Monitoring Job
... Pre-conditions: none
- ... Reference: Clause 6.4.3.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 6.4.3.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -79,7 +79,7 @@ PUT Individual VNF Performance Job - Method not implemented
... Test title: PUT Individual VNF Performance Job - method not implemented
... Test objective: The objective is to test that PUT method is not allowed to update an existing VNF Performance Monitoring Job
... Pre-conditions: none
- ... Reference: Clause 6.4.3.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 6.4.3.3.3 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -91,7 +91,7 @@ PATCH Individual VNF Performance Job
... Test title: PATCH Individual VNF Performance Job
... Test objective: The objective is to test that PATCH method allows to modify an exsisting individual PM job resource.
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance jobs are set in the VNFM.
- ... Reference: Clause 6.4.3.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 6.4.3.3.4 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -105,7 +105,7 @@ PATCH Individual VNF Performance Job - Precondition failed
... Test title: PATCH Individual VNF Performance Job - Precondition failed
... Test objective: The objective is to attempt to Modify an individual alarm resource, where the precondition was not met
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance jobs are set in the VNFM.
- ... Reference: Clause 6.4.3.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 6.4.3.3.4 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: The VNF Performance Job is not modified by the operation
@@ -114,12 +114,12 @@ PATCH Individual VNF Performance Job - Precondition failed
Check HTTP Response Body Json Schema Is ProblemDetails
Check Postcondition VNF Performance Job is Unmodified (Implicit)
-PATCH Individual VNF Performance Job - UNPROCESSIBLE ENTITY
+PATCH Individual VNF Performance Job - UNPROCESSABLE CONTENT
[Documentation] Test ID: 6.3.3.2.9
- ... Test title: PATCH Individual VNF Performance Job - UNPROCESSIBLE ENTITY
+ ... Test title: PATCH Individual VNF Performance Job - UNPROCESSABLE CONTENT
... Test objective: The objective is to test that PATCH method cannot modify an exsisting individual PM job resource when the callback URI provided in the Request body is unreachable by the VNFM.
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance jobs are set in the VNFM.
- ... Reference: Clause 6.4.3.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 6.4.3.3.4 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: The VNFM cannot reach the Notification endpoint.
... Post-Conditions: none
diff --git a/SOL002/VNFPerformanceManagement-API/IndividualReport.robot b/SOL002/VNFPerformanceManagement-API/IndividualReport.robot
index 716fdafd289e70905b93db8dbc012635e9e9050f..f5c8ccb2c27d08d5ade9b84b92905f7d0b03d483 100644
--- a/SOL002/VNFPerformanceManagement-API/IndividualReport.robot
+++ b/SOL002/VNFPerformanceManagement-API/IndividualReport.robot
@@ -10,7 +10,7 @@ Get Individual Performance Report
... Test title: Get Individual Performance Report
... Test objective: The objective is to test the retrieval of an individual VNF performance report associated to a monitoring job and perform a JSON schema validation of the collected report data structure
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance reports are set for a monitoring job in the VNFM.
- ... Reference: Clause 6.4.4.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 6.4.4.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -23,7 +23,7 @@ Get Individual Performance Report with invalid resource endpoint
... Test title: Get Individual Performance Report with invalid resource endpoint
... Test objective: The objective is to test that the retrieval of an individual VNF performance report associated to a monitoring job fails when using an invalid resource endpoint
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance reports are set for a monitoring job in the VNFM.
- ... Reference: Clause 6.4.4.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 6.4.4.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -36,7 +36,7 @@ POST Individual Performance Report - Method not implemented
... Test title: POST Individual Performance Report - Method not implemented
... Test objective: The objective is to test that POST method is not allowed to create a new VNF performance report within a monitoring job
... Pre-conditions: none
- ... Reference: Clause 6.4.4.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 6.4.4.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -48,7 +48,7 @@ PUT Individual Performance Report - Method not implemented
... Test title: PUT Individual Performance Report - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to update an existing VNF performance report within a monitoring job
... Pre-conditions: none
- ... Reference: Clause 6.4.4.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 6.4.4.3.3 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -60,7 +60,7 @@ PATCH Individual Performance Report - Method not implemented
... Test title: PATCH Individual Performance Report - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to modify an existing VNF performance report within a monitoring job
... Pre-conditions: none
- ... Reference: Clause 6.4.4.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 6.4.4.3.4 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -72,7 +72,7 @@ DELETE Individual Performance Report - Method not implemented
... Test title: DELETE Individual Performance Report - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to delete an existing VNF performance report within a monitoring job
... Pre-conditions: none
- ... Reference: Clause 6.4.4.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 6.4.4.3.5 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL002/VNFPerformanceManagement-API/IndividualThreshold.robot b/SOL002/VNFPerformanceManagement-API/IndividualThreshold.robot
index 593d3eb05c17a3baec9f7485d75d0532aa18d57b..2f4a25f48a3df7d1e6bd361014360575276a2f57 100644
--- a/SOL002/VNFPerformanceManagement-API/IndividualThreshold.robot
+++ b/SOL002/VNFPerformanceManagement-API/IndividualThreshold.robot
@@ -12,7 +12,7 @@ GET Individual Threshold
... Test title: GET Individual Threshold
... Test objective: The objective is to test the retrieval of an individual VNF performance threshold and perform a JSON schema and content validation of the collected threshold data structure
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance thresholds are set in the VNFM.
- ... Reference: Clause 6.4.6.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 6.4.6.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -27,7 +27,7 @@ GET Individual Threshold with invalid resource identifier
... Test title: GET Individual Threshold with invalid resource identifier
... Test objective: The objective is to test that the retrieval of an individual VNF performance threshold fails when using an invalid resource identifier
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance jobs are set in the VNFM.
- ... Reference: Clause 6.4.6.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 6.4.6.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -40,7 +40,7 @@ DELETE Individual Threshold
... Test title: DELETE Individual Threshold
... Test objective: The objective is to test the deletion of an individual VNF performance threshold
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance thresholds are set in the VNFM.
- ... Reference: Clause 6.4.6.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 6.4.6.3.5 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: The VNF Performance Threshold is not available anymore in the VNFM
@@ -53,7 +53,7 @@ DELETE Individual Threshold with invalid resource identifier
... Test title: DELETE Individual Threshold with invalid resource identifier
... Test objective: The objective is to test the deletion of an individual VNF performance threshold
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance thresholds are set in the VNFM.
- ... Reference: Clause 6.4.6.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 6.4.6.3.5 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -66,7 +66,7 @@ POST Individual Threshold - Method not implemented
... Test title: POST Individual Threshold - Method not implemented
... Test objective: The objective is to test that POST method is not allowed to create a new VNF Performance Threshold
... Pre-conditions: none
- ... Reference: Clause 6.4.6.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 6.4.6.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: The VNF Performance Threshold is not created on the VNFM
@@ -78,7 +78,7 @@ PUT Individual Threshold - Method not implemented
... Test title: PUT Individual Threshold - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to update an existing VNF Performance threshold
... Pre-conditions: none
- ... Reference: Clause 6.4.6.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 6.4.6.3.3 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -90,7 +90,7 @@ PATCH Individual Threshold
... Test title: PATCH Individual Threshold
... Test objective: The objective is to test that PATCH method allows to modify an Individual threshold resource.
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance thresholds are set in the VNFM.
- ... Reference: Clause 6.4.6.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 6.4.6.3.4 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: The VNF Performance Threshold is not modified by the operation
@@ -104,7 +104,7 @@ PATCH Individual Threshold - Precondition failed
... Test title: PATCH Individual Threshold - Preconition failed
... Test objective: The objective is to attempt to modify an individual threshold resource, where the precondition was not met.
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance jobs are set in the VNFM.
- ... Reference: Clause 6.4.6.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 6.4.6.3.4 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: The VNF Performance Job is not modified by the operation
@@ -113,12 +113,12 @@ PATCH Individual Threshold - Precondition failed
Check HTTP Response Body Json Schema Is ProblemDetails
Check Postcondition VNF Performance Threshold is Unmodified (Implicit)
-PATCH Individual Threshold - Unprocessible Entity
+PATCH Individual Threshold - UNPROCESSABLE CONTENT
[Documentation] Test ID: 6.3.3.5.9
- ... Test title: PATCH Individual Threshold - Unprocessible Entity
+ ... Test title: PATCH Individual Threshold - UNPROCESSABLE CONTENT
... Test objective: The objective is to test that PATCH method cannot modify an exsisting individual PM job resource when the callback URI provided in the Request body is unreachable by the VNFM.
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance thresholds are set in the VNFM.
- ... Reference: Clause 6.4.6.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 6.4.6.3.4 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: The VNFM cannot reach the Notification endpoint.
... Post-Conditions: The VNF Performance Threshold is not modified by the operation
diff --git a/SOL002/VNFPerformanceManagement-API/NotificationEndpoint.robot b/SOL002/VNFPerformanceManagement-API/NotificationEndpoint.robot
index c18e20f2c52dc62639adc33534825610cc65f373..64f9d32c7c874a8f7136fec5e41d055b7a7e7432 100644
--- a/SOL002/VNFPerformanceManagement-API/NotificationEndpoint.robot
+++ b/SOL002/VNFPerformanceManagement-API/NotificationEndpoint.robot
@@ -13,7 +13,7 @@ VNF Performance Information Availability Notification
... Test title: VNF Performance Information Availability Notification
... Test objective: The objective is to test that VNF Performance Information Availability Notification is delivered with success to the notification consumer
... Pre-conditions: A VNF performance job is created, and a subscription for information availability notifications is available in the VNFM.
- ... Reference: Clause 6.4.9.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 6.4.9.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
@@ -25,7 +25,7 @@ VNF Threshold Crossed Notification
... Test title: VNF Threshold Crossed Notification
... Test objective: The objective is to test that VNF Threshold Crossed Notification is delivered with success to the notification consumer
... Pre-conditions: A VNF performance job is created, and a subscription for Threshold Crossed Notification is available in the VNFM.
- ... Reference: Clause 6.4.9.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 6.4.9.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
diff --git a/SOL002/VNFPerformanceManagementNotification-API/Notifications.robot b/SOL002/VNFPerformanceManagement-API/Notifications.robot
similarity index 98%
rename from SOL002/VNFPerformanceManagementNotification-API/Notifications.robot
rename to SOL002/VNFPerformanceManagement-API/Notifications.robot
index b2f11b8dbc0c94bda4a61b09670eac2841e1cc29..ea973feef5f810e243ddd2c0de9c8c038ab3547c 100644
--- a/SOL002/VNFPerformanceManagementNotification-API/Notifications.robot
+++ b/SOL002/VNFPerformanceManagement-API/Notifications.robot
@@ -17,7 +17,7 @@ VNF Performance Information Availability Notification
... Test title: VNF Performance Information Availability Notification
... Test objective: The objective is to test the dispatch of VNF Performance Information Availability Notification when new VNF performance information is available in the NFVO, and perform a JSON schema and content validation of the delivered notification. The action that triggers the notification under test is an explicit test step, but it is not performed by the test system.
... Pre-conditions: A VNF performance job is created, and a subscription for information availability notifications is available in the VNFM.
- ... Reference: Clause 6.4.9.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 6.4.9.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -30,7 +30,7 @@ VNF Threshold Crossed Notification
... Test title: VNF Threshold Crossed Notification
... Test objective: The objective is to test the dispatch of VNF Threshold Crossed Notification when a previously set VNF performance metric threshold is crossed, and perform a JSON schema and content validation of the delivered notification. The action that triggers the notification under test is an explicit test step, but it is not performed by the test system.
... Pre-conditions: A VNF performance job is created, and a threshold subscription is available in the VNFM.
- ... Reference: Clause 6.4.9.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 6.4.9.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL002/VNFPerformanceManagement-API/PMJobs.robot b/SOL002/VNFPerformanceManagement-API/PMJobs.robot
index e1a52d741fa5d0c4a76a8858eb6412becfd20473..044df0cca398520cb22171ea8d2a4c7aa25d22ca 100644
--- a/SOL002/VNFPerformanceManagement-API/PMJobs.robot
+++ b/SOL002/VNFPerformanceManagement-API/PMJobs.robot
@@ -12,7 +12,7 @@ GET all VNF Performance Monitoring Jobs
... Test title: GET all VNF Performance Monitoring Jobs
... Test objective: The objective is to test the retrieval of all the available VNF performance monitoring jobs and perform a JSON schema and content validation of the collected jobs data structure
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance jobs are set in the VNF.
- ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -25,7 +25,7 @@ GET VNF Performance Monitoring Jobs with attribute-based filter
... Test title: GET all VNF Performance Monitoring Jobs with attribute-based filter
... Test objective: The objective is to test the retrieval of VNF performance monitoring jobs using attribute-based filter, perform a JSON schema validation of the collected jobs data structure, and verify that the retrieved information matches the issued attribute-based filter
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance jobs are set in the VNF.
- ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -39,7 +39,7 @@ GET all VNF Performance Monitoring Jobs with all_fields attribute selector
... Test title: GET all VNF Performance Monitoring Jobs with all_fields attribute selector
... Test objective: The objective is to test the retrieval of all VNF performance monitoring jobs all_fields attribute selector, perform a JSON schema validation of the collected jobs data structure, and verify that the retrieved information matches the issued all_fileds selector
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance jobs are set in the VNF.
- ... Reference: Clause 4.3.3.2.1, 6.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 4.3.3.2.1, 6.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -53,7 +53,7 @@ GET all VNF Performance Monitoring Jobs with exclude_default attribute selector
... Test title: GET all VNF Performance Monitoring Jobs with exclude_default attribute selector
... Test objective: The objective is to test the retrieval of all VNF performance monitoring jobs exclude_default attribute selector, perform a JSON schema validation of the collected jobs data structure, and verify that the retrieved information matches the issued exclude_default selector
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance jobs are set in the VNF.
- ... Reference: Clause 4.3.3.2.1, 6.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 4.3.3.2.1, 6.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -67,7 +67,7 @@ GET all VNF Performance Monitoring Jobs with fields attribute selector
... Test title: GET all VNF Performance Monitoring Jobs with fields attribute selector
... Test objective: The objective is to test the retrieval of all VNF performance monitoring jobs fields attribute selector, perform a JSON schema validation of the collected jobs data structure, and verify that the retrieved information matches the issued fields selector
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance jobs are set in the VNF.
- ... Reference: Clause 4.3.3.2.1, 6.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 4.3.3.2.1, 6.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: The VNFM supports the use of exclude_fields attribute selector
... Post-Conditions: none
@@ -81,7 +81,7 @@ GET all VNF Performance Monitoring Jobs with exclude_fields attribute selector
... Test title: GET all VNF Performance Monitoring Jobs with exclude_fields attribute selector
... Test objective: The objective is to test the retrieval of all VNF performance monitoring jobs exclude_fields attribute selector, perform a JSON schema validation of the collected jobs data structure, and verify that the retrieved information matches the issued exclude_fields selector
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance jobs are set in the VNF.
- ... Reference: Clause 4.3.3.2.1, 6.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 4.3.3.2.1, 6.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: The VNFM supports the use of exclude_fields attribute selector
... Post-Conditions: none
@@ -95,7 +95,7 @@ GET VNF Performance Monitoring Jobs with invalid attribute-based filter
... Test title: GET VNF Performance Monitoring Jobs with invalid attribute-based filter
... Test objective: The objective is to test that the retrieval of VNF performance monitoring jobs fails when using invalid attribute-based filter, and perform the JSON schema validation of the failed operation HTTP response
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance jobs are set in the VNF.
- ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -108,7 +108,7 @@ GET VNF Performance Monitoring Jobs with invalid resource endpoint
... Test title: GET VNF Performance Monitoring Jobs with invalid resource endpoint
... Test objective: The objective is to test that the retrieval of VNF performance monitoring jobs fails when using invalid resource endpoint, and perform the JSON schema validation of the failed operation HTTP response
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance jobs are set in the VNF.
- ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -121,7 +121,7 @@ POST Create new VNF Performance Monitoring Job - SUCCESSFUL
... Test title: POST Create a new VNF Performance Monitoring Job - SUCCESSFUL
... Test objective: The objective is to test that the POST method creates a new VNF performance monitoring job and perform the JSON schema validation of the returned job data structure
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance jobs are set in the VNF.
- ... Reference: Clause 6.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 6.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: The VNF Performance Job is successfully created on the VNFM
@@ -135,7 +135,7 @@ PUT all VNF Performance Monitoring Jobs - Method not implemented
... Test title: PUT all VNF Performance Monitoring Jobs - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to modify VNF Performance Monitoring Jobs
... Pre-conditions: none
- ... Reference: Clause 6.4.2.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 6.4.2.3.3 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -147,7 +147,7 @@ PATCH all VNF Performance Monitoring Jobs - Method not implemented
... Test title: PATCH all VNF Performance Monitoring Jobs - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update VNF Performance Monitoring Jobs
... Pre-conditions: none
- ... Reference: Clause 6.4.2.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 6.4.2.3.3 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -159,7 +159,7 @@ DELETE all VNF Performance Monitoring Jobs - Method not implemented
... Test title: DELETE all VNF Performance Monitoring Jobs - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to update VNF Performance Monitoring Jobs
... Pre-conditions: none
- ... Reference: Clause 6.4.2.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 6.4.2.3.3 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -171,7 +171,7 @@ GET VNF Performance Monitoring Jobs to get Paged Response
... Test title: GET VNF Performance Monitoring Jobs to get Paged Response
... Test objective: The objective is to test the retrieval of VNF performance monitoring jobs to get Paged response.
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance jobs are set in the VNF.
- ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -184,7 +184,7 @@ GET VNF Performance Monitoring Jobs for Bad Request Response too big
... Test title: GET VNF Performance Monitoring Jobs for Bad Request Response too big
... Test objective: The objective is to test that GET method fail retrieving status information about VNF Performance Monitoring when Response is too big, and perform the JSON schema validation of the failed operation HTTP response
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance jobs are set in the VNF.
- ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -197,7 +197,7 @@ GET all VNF Performance Monitoring Jobs with exclude_default and fields attribut
... Test title: GET all VNF Performance Monitoring Jobs with exclude_default and fields attribute selector
... Test objective: The objective is to test the retrieval of all VNF performance monitoring jobs with exclude_default and fields attribute selector, perform a JSON schema validation of the collected jobs data structure, and verify that the retrieved information matches the issued exclude_default selector
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance jobs are set in the VNF.
- ... Reference: Clause 4.3.3.2.1, 6.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 4.3.3.2.1, 6.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -205,12 +205,12 @@ GET all VNF Performance Monitoring Jobs with exclude_default and fields attribut
Check HTTP Response Status Code Is 200
Check HTTP Response Body Json Schema Is PmJobs
-POST Create new VNF Performance Monitoring Job - UNPROCESSIBLE ENTITY
+POST Create new VNF Performance Monitoring Job - UNPROCESSABLE CONTENT
[Documentation] Test ID: 6.3.3.1.16
- ... Test title: POST Create a new VNF Performance Monitoring Job - UNPROCESSIBLE ENTITY
+ ... Test title: POST Create a new VNF Performance Monitoring Job - UNPROCESSABLE CONTENT
... Test objective: The objective is to test that the POST method cannot create a new VNF performance monitoring job when the callback URI provided in the Request body is unreachable by the VNFM.
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance jobs are set in the VNF.
- ... Reference: Clause 6.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 6.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: The VNFM cannot reach the Notification endpoint.
... Post-Conditions: none
diff --git a/SOL002/VNFPerformanceManagement-API/Thresholds.robot b/SOL002/VNFPerformanceManagement-API/Thresholds.robot
index 6fba18cd26767360867979ccf358dcc4f263fc96..cd718e26fc369723320d77e43d314e3b401f65ad 100644
--- a/SOL002/VNFPerformanceManagement-API/Thresholds.robot
+++ b/SOL002/VNFPerformanceManagement-API/Thresholds.robot
@@ -12,7 +12,7 @@ GET All Performance Thresholds
... Test title: GET All Performance Thresholds
... Test objective: The objective is to test the retrieval of all the available VNF performance thresholds and perform a JSON schema validation of the collected thresholds data structure
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance thresholds are set in the VNFM.
- ... Reference: Clause 6.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 6.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -25,7 +25,7 @@ GET Performance Thresholds with attribute-based filter
... Test title: GET Performance Thresholds with attribute-based filter
... Test objective: The objective is to test the retrieval of all the available VNF performance thresholds when using attribute-based filters, perform a JSON schema validation of the collected thresholds data structure, and verify that the retrieved information matches the issued attribute-based filter
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance thresholds are set in the VNFM.
- ... Reference: Clause 6.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 6.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -39,7 +39,7 @@ GET Performance Thresholds with invalid attribute-based filter
... Test title: GET Performance Thresholds with invalid attribute-based filter
... Test objective: The objective is to test that the retrieval of VNF performance thresholds fails when using invalid attribute-based filter, and perform the JSON schema validation of the failed operation HTTP response
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance thresholds are set in the VNFM.
- ... Reference: Clause 6.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 6.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -52,7 +52,7 @@ GET Performance Thresholds with invalid resource endpoint
... Test title: GET Performance Thresholds with invalid resource endpoint
... Test objective: The objective is to test that the retrieval of VNF performance thresholds fails when using invalid resource endpoint, and perform the JSON schema validation of the failed operation HTTP response
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance thresholds are set in the VNFM.
- ... Reference: Clause 6.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 6.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -65,7 +65,7 @@ POST Create new Performance Threshold
... Test title: POST Create new Performance Threshold
... Test objective: The objective is to test that the POST method creates a new VNF performance threshold and perform the JSON schema validation of the returned threshold data structure
... Pre-conditions: A VNF instance is instantiated.
- ... Reference: Clause 6.4.5.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 6.4.5.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: The VNF Performance Threshold is successfully created on the VNFM
@@ -80,7 +80,7 @@ PUT Performance Thresholds - Method not implemented
... Test title: PUT Performance Thresholds - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to modify VNF Performance Thresholds
... Pre-conditions: none
- ... Reference: Clause 6.4.5.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 6.4.5.3.3 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -92,7 +92,7 @@ PATCH Performance Thresholds - Method not implemented
... Test title: PATCH Performance Thresholds - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to modify VNF Performance Thresholds
... Pre-conditions: none
- ... Reference: Clause 6.4.5.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 6.4.5.3.4 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -104,7 +104,7 @@ DELETE Performance Thresholds - Method not implemented
... Test title: DELETE Performance Thresholds - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to update VNF Performance Thresholds
... Pre-conditions: none
- ... Reference: Clause 6.4.5.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 6.4.5.3.5 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -116,7 +116,7 @@ GET Performance Thresholds with Paged Response
... Test title: GET Performance Thresholds with Paged Response
... Test objective: The objective is to test the retrieval of all the available VNF performance thresholds with Paged response
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance thresholds are set in the VNFM.
- ... Reference: Clause 6.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 6.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -129,7 +129,7 @@ GET Performance Thresholds for Bad Request Response too big
... Test title: GET Performance Thresholds for Bad Request Response too big
... Test objective: The objective is to test that the retrieval of VNF performance thresholds fails when response is too big, and perform the JSON schema validation of the failed operation HTTP response
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance thresholds are set in the VNFM.
- ... Reference: Clause 6.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 6.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -137,12 +137,12 @@ GET Performance Thresholds for Bad Request Response too big
Check HTTP Response Status Code Is 400
Check HTTP Response Body Json Schema Is ProblemDetails
-POST Create new Performance Threshold - UNPROCESSIBLE ENTITY
+POST Create new Performance Threshold - UNPROCESSABLE CONTENT
[Documentation] Test ID: 6.3.3.4.11
- ... Test title: POST Create new Performance Threshold
+ ... Test title: POST Create new Performance Threshold - UNPROCESSABLE CONTENT
... Test objective: The objective is to test that the POST method does not create a new VNF performance threshold when the callback URI provided in the Request body is unreachable by the VNFM.
... Pre-conditions: A VNF instance is instantiated.
- ... Reference: Clause 6.4.5.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
+ ... Reference: Clause 6.4.5.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: The VNFM cannot reach the Notification endpoint.
... Post-Conditions: none
diff --git a/SOL002/VNFPerformanceManagementNotification-API/environment/notifications.txt b/SOL002/VNFPerformanceManagement-API/environment/notifications.txt
similarity index 100%
rename from SOL002/VNFPerformanceManagementNotification-API/environment/notifications.txt
rename to SOL002/VNFPerformanceManagement-API/environment/notifications.txt
diff --git a/SOL002/VNFPerformanceManagementNotification-API/jsons/PerformanceInformationAvailableNotification.json b/SOL002/VNFPerformanceManagement-API/jsons/PerformanceInformationAvailableNotification.json
similarity index 100%
rename from SOL002/VNFPerformanceManagementNotification-API/jsons/PerformanceInformationAvailableNotification.json
rename to SOL002/VNFPerformanceManagement-API/jsons/PerformanceInformationAvailableNotification.json
diff --git a/SOL002/VNFPerformanceManagementNotification-API/jsons/ThresholdCrossedNotification.json b/SOL002/VNFPerformanceManagement-API/jsons/ThresholdCrossedNotification copy.json
similarity index 100%
rename from SOL002/VNFPerformanceManagementNotification-API/jsons/ThresholdCrossedNotification.json
rename to SOL002/VNFPerformanceManagement-API/jsons/ThresholdCrossedNotification copy.json
diff --git a/SOL002/VNFPerformanceManagementNotification-API/schemas/PerformanceInformationAvailableNotification.schema.json b/SOL002/VNFPerformanceManagement-API/schemas/PerformanceInformationAvailableNotification.schema.json
similarity index 100%
rename from SOL002/VNFPerformanceManagementNotification-API/schemas/PerformanceInformationAvailableNotification.schema.json
rename to SOL002/VNFPerformanceManagement-API/schemas/PerformanceInformationAvailableNotification.schema.json
diff --git a/SOL002/VNFPerformanceManagementNotification-API/schemas/ThresholdCrossedNotification.schema.json b/SOL002/VNFPerformanceManagement-API/schemas/ThresholdCrossedNotification.schema.json
similarity index 100%
rename from SOL002/VNFPerformanceManagementNotification-API/schemas/ThresholdCrossedNotification.schema.json
rename to SOL002/VNFPerformanceManagement-API/schemas/ThresholdCrossedNotification.schema.json
diff --git a/SOL002/VNFPerformanceManagementNotification-API/README.md b/SOL002/VNFPerformanceManagementNotification-API/README.md
deleted file mode 100644
index f5f7677f55fcf78e1846a4ff3f61fb4cdef215c3..0000000000000000000000000000000000000000
--- a/SOL002/VNFPerformanceManagementNotification-API/README.md
+++ /dev/null
@@ -1,12 +0,0 @@
-# NFV API Tests
-
-This is a development folder for ETSI STF 557.
-It includes the NFV API conformance test descriptions.
-
-## License
-
-Any software in this repository is released under the ETSI Software License.
-Licensing information is available in the attached LICENSE file.
-
-
-Copyright (c) ETSI 2018
diff --git a/SOL002/VNFPerformanceManagementNotification-API/environment/variables.txt b/SOL002/VNFPerformanceManagementNotification-API/environment/variables.txt
deleted file mode 100644
index ea77433224590ab4fd67f72e91a5d7de23af5472..0000000000000000000000000000000000000000
--- a/SOL002/VNFPerformanceManagementNotification-API/environment/variables.txt
+++ /dev/null
@@ -1,6 +0,0 @@
-*** Variables ***
-${callback_uri} http://localhost
-${callback_port} 9091
-${callback_endpoint} /endpoint
-
-${MOCK_SERVER_JAR} ../../../bin/mockserver-netty-5.5.0-jar-with-dependencies.jar
\ No newline at end of file
diff --git a/SOL002/VNFPerformanceManagementNotification-API/schemas/ProblemDetails.schema.json b/SOL002/VNFPerformanceManagementNotification-API/schemas/ProblemDetails.schema.json
deleted file mode 100644
index a4c007a5c1501eaf4ae57b5973cda6ef1d4bbea5..0000000000000000000000000000000000000000
--- a/SOL002/VNFPerformanceManagementNotification-API/schemas/ProblemDetails.schema.json
+++ /dev/null
@@ -1,32 +0,0 @@
-{
- "description": "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 [19] is reproduced inthis structure. Compared to the general framework defined in IETF RFC 7807 [19], the \"status\" and \"detail\" attributes are mandated to be included by the present document, to ensure that the response contains additional textual information about an error. IETF RFC 7807 [19] foresees extensibility of the \"ProblemDetails\" type. It is possible that particular APIs in the present document, or particular implementations, define extensions to define additional attributes that provide more information about the error. The description column only provides some explanation of the meaning to Facilitate understanding of the design. For a full description, see IETF RFC 7807 [19].\n",
- "type": "object",
- "required": [
- "status",
- "detail"
- ],
- "properties": {
- "type": {
- "description": "A URI reference according to IETF RFC 3986 [5] that identifies the problem type. It is encouraged that the URI provides human-readable documentation for the problem (e.g. using HTML) when dereferenced. When this member is not present, its value is assumed to be \"about:blank\".\n",
- "type": "string",
- "format": "URI"
- },
- "title": {
- "description": "A short, human-readable summary of the problem type. It should not change from occurrence to occurrence of the problem, except for purposes of localization. If type is given and other than \"about:blank\", this attribute shall also be provided. A short, human-readable summary of the problem type. It SHOULD NOT change from occurrence to occurrence of the problem, except for purposes of localization (e.g., using proactive content negotiation; see [RFC7231], Section 3.4).\n",
- "type": "string"
- },
- "status": {
- "description": "The HTTP status code for this occurrence of the problem. The HTTP status code ([RFC7231], Section 6) generated by the origin server for this occurrence of the problem.\n",
- "type": "integer"
- },
- "detail": {
- "description": "A human-readable explanation specific to this occurrence of the problem.\n",
- "type": "string"
- },
- "instance": {
- "description": "A URI reference that identifies the specific occurrence of the problem. It may yield further information if dereferenced.\n",
- "type": "string",
- "format": "URI"
- }
- }
-}
\ No newline at end of file
diff --git a/SOL003/README.md b/SOL003/README.md
index 94ca3e8233dfa5f30c4e6260ef43d7e08ab25cdd..0f3a79785026dd01d79ee19cfc616196512eb5fa 100644
--- a/SOL003/README.md
+++ b/SOL003/README.md
@@ -2,5 +2,5 @@
This folder includes the NFV API conformance test descriptions for NFV SOL003 APIs.
-The reference spec version is v4.3.1: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/04.03.01_60/gs_nfv-sol003v040301p.pdf
+The reference spec version is v4.4.1: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/04.04.01_60/gs_nfv-sol003v040401p.pdf
diff --git a/SOL003/VNFFaultManagement-API/Alarms.robot b/SOL003/VNFFaultManagement-API/Alarms.robot
index 628c447215d10c271ca715dd9cf122a74cacf9a1..f9c057c78d3a82e91d531b388a83dd394136d49f 100644
--- a/SOL003/VNFFaultManagement-API/Alarms.robot
+++ b/SOL003/VNFFaultManagement-API/Alarms.robot
@@ -13,7 +13,7 @@ POST Alarms - Method not implemented
... Test title: POST Alarms - Method not implemented
... Test objective: The objective is to test that Post method is not allowed to create Fault management alarms on VNF
... Pre-conditions: none
- ... Reference: Clause 7.4.2.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 7.4.2.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -25,7 +25,7 @@ Get information about multiple alarms
... Test title: Get information about multiple alarms
... Test objective: The objective is to retrieve information about the alarm list and perform a JSON schema and content validation of the returned alarms data structure
... Pre-conditions: none
- ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -38,7 +38,7 @@ Get information about multiple alarms with filter
... Test title: Get information about multiple alarms with filter
... Test objective: The objective is to retrieve information about the alarm list and perform a JSON schema and content validation of the returned alarms data structure, and verify that the retrieved information matches the issued attribute-based filters
... Pre-conditions: none
- ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -51,7 +51,7 @@ Get information about multiple alarms Bad Request Invalid attribute-based filter
... Test title: Get information about multiple alarms Bad Request Invalid attribute-based filtering parameters
... Test objective: The objective is to try to retrieve information about the alarm list with invalid filters and perform a JSON schema and content validation of the returned problem details data structure
... Pre-conditions: none
- ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -109,7 +109,7 @@ PUT Alarms - Method not implemented
... Test title: PUT Alarms - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to for Fault management alarms on VNF
... Pre-conditions: none
- ... Reference: Clause 7.4.2.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 7.4.2.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -121,7 +121,7 @@ PATCH Alarms - Method not implemented
... Test title: PATCH Alarms - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to for Fault management alarms on VNF
... Pre-conditions: none
- ... Reference: Clause 7.4.2.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 7.4.2.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -133,7 +133,7 @@ DELETE Alarms - Method not implemented
... Test title: POST Alarms - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed for Fault management alarms on VNF
... Pre-conditions: none
- ... Reference: Clause 7.4.2.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 7.4.2.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -145,7 +145,7 @@ Get information about multiple alarms as a Paged Response
... Test title: Get information about multiple alarms as a Paged Response
... Test objective: The objective is to retrieve information about the alarm list as a Paged Response
... Pre-conditions: none
- ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: The VNFM supports response paging for the VNF alarm resources
... Post-Conditions: none
@@ -158,7 +158,7 @@ GET information about multiple alarms as a Paged Response with nextpage_opauque_
... Test title: GET information about multiple alarms as a Paged Response with nextpage_opauque_marker parameter
... Test objective: The objective is to query information about multiple alarms as a Paged Response and retrieve the next page using the nextpage_opaque_marker parameter
... Pre-conditions: A request for retrieving multiple alarms as a paged response has been successfully issued (Test ID 7.3.5.1.12)
- ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: The VNFM supports response paging for the VNF alarm resources
... Post-Conditions: none
@@ -171,7 +171,7 @@ Get information about multiple alarms - Bad Request Response too Big
... Test title: Get information about multiple alarms - Bad Request Response too Big
... Test objective: The objective is to try to retrieve information about the alarm list because response is too big and perform a JSON schema and content validation of the returned problem details data structure
... Pre-conditions: none
- ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFFaultManagement-API/ApiVersion.robot b/SOL003/VNFFaultManagement-API/ApiVersion.robot
index 95c9392e5fd30f7ce190bb6f9e022a8cbe0aa69c..b1a8f8ef84cc82897e1fdfc1c86d2714e6feefa1 100644
--- a/SOL003/VNFFaultManagement-API/ApiVersion.robot
+++ b/SOL003/VNFFaultManagement-API/ApiVersion.robot
@@ -13,7 +13,7 @@ POST API Version - Method not implemented
... Test title: POST API version - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -25,7 +25,7 @@ GET API Version
... Test title: GET API Version
... Test objective: The objective is to test that GET method successfully return ApiVersionInformation
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -38,7 +38,7 @@ PUT API Version - Method not implemented
... Test title: PUT API Version - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -50,7 +50,7 @@ PATCH API Version - Method not implemented
... Test title: PATCH API Version - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -62,7 +62,7 @@ DELETE API Version - Method not implemented
... Test title: DELETE API Version - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -74,7 +74,7 @@ POST API Version with apiMajorVerion - Method not implemented
... Test title: POST API version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -86,7 +86,7 @@ GET API Version with apiMajorVerion
... Test title: GET API Version with apiMajorVerion
... Test objective: The objective is to test that GET method successfully return ApiVersionInformation
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -99,7 +99,7 @@ PUT API Version with apiMajorVerion - Method not implemented
... Test title: PUT API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -111,7 +111,7 @@ PATCH API Version with apiMajorVerion - Method not implemented
... Test title: PATCH API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -123,7 +123,7 @@ DELETE API Version with apiMajorVerion - Method not implemented
... Test title: DELETE API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFFaultManagement-API/IndividualAlarm.robot b/SOL003/VNFFaultManagement-API/IndividualAlarm.robot
index 30b8f5be91c4ada8df87ebdb7b3238f6694ead84..7e0d123e10e2d3494a401d44068cff8eb4b5354d 100644
--- a/SOL003/VNFFaultManagement-API/IndividualAlarm.robot
+++ b/SOL003/VNFFaultManagement-API/IndividualAlarm.robot
@@ -14,7 +14,7 @@ POST Alarm - Method not implemented
... Test title: POST Alarm - Method not implemented
... Test objective: The objective is to test that Post method is not allowed to create Fault management individual alarm on VNF
... Pre-conditions: none
- ... Reference: Clause 7.4.3.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 7.4.3.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -26,7 +26,7 @@ Get information about an fault management individual alarm
... Test title: Get information about an fault management individual alarm
... Test objective: The objective is to retrieve information about an individual alarm and perform a JSON schema and content validation of the returned alarm data structure
... Pre-conditions: The related alarm exists
- ... Reference: Clause 7.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 7.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -40,7 +40,7 @@ PUT Alarm - Method not implemented
... Test title: PUT Alarm - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to for Fault management individual alarm on VNF
... Pre-conditions: none
- ... Reference: Clause 7.4.3.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 7.4.3.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -52,7 +52,7 @@ PATCH Fault Management Individual Alarm
... Test title: PATCH Fault Management Individual Alarm
... Test objective: The objective is to Modify an individual alarm resource and perform a JSON schema and content validation of the returned alarm data structure
... Pre-conditions: The related alarm exists
- ... Reference: Clause 7.4.3.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 7.4.3.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -66,7 +66,7 @@ Modify an individual alarm resource - Precondition failed
... Test title: Modify an individual alarm resource - Precondition failed
... Test objective: The objective is to test that an individual alarm resource cannot be modified if the resource was modified by another entity
... Pre-conditions: The related alarm exists
- ... Reference: Clause 7.4.3.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 7.4.3.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -79,7 +79,7 @@ Modify an individual alarm resource - Conflict
... Test title: Modify an individual alarm resource - Conflict
... Test objective: The objective is to test that an individual alarm resource cannot be modified if the alarm is already in the state that is requested to be set
... Pre-conditions: The related alarm exists
- ... Reference: Clause 7.4.3.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 7.4.3.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -93,7 +93,7 @@ DELETE Alarm - Method not implemented
... Test title: DELETE Alarm - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to for Fault management individual alarm on VNF
... Pre-conditions: none
- ... Reference: Clause 7.4.3.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 7.4.3.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -105,7 +105,7 @@ Get information about an fault management individual alarm - Not Found
... Test title: Get information about an fault management individual alarm - Not Found
... Test objective: The objective is to test that retrieval of information about an individual alarm fails when individual alarm is not present
... Pre-conditions: The related alarm does not exists
- ... Reference: Clause 7.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 7.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFFaultManagement-API/IndividualSubscription.robot b/SOL003/VNFFaultManagement-API/IndividualSubscription.robot
index 89dfc5b8a31a99d37216776d38c8381e2b1ba9a3..8bd03cb3cf6c951a8c8836b5f7acaf60df3ca5d2 100644
--- a/SOL003/VNFFaultManagement-API/IndividualSubscription.robot
+++ b/SOL003/VNFFaultManagement-API/IndividualSubscription.robot
@@ -11,7 +11,7 @@ Post Individual Subscription - Method not implemented
... Test title: Post Individual Subscription - Method not implemented
... Test objective: The objective is to test that POST method is not allowed for Fault management subscription on VNF
... Pre-conditions: none
- ... Reference: Clause 7.4.5.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 7.4.5.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -23,7 +23,7 @@ Get Information about an individual subscription
... Test title: Get Information about an individual subscription
... Test objective: The objective is to read an individual subscription for NFVO alarms subscribed by the client and perform a JSON schema and content validation of the returned fault management individual subscription data structure
... Pre-conditions: The subscription with the given id exists
- ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -36,7 +36,7 @@ PUT an individual subscription - Method not implemented
... Test title:PUT an individual subscription - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed for Fault management individual subscription on VNF
... Pre-conditions: none
- ... Reference: Clause 7.4.5.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 7.4.5.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -48,7 +48,7 @@ PATCH an individual subscription - Method not implemented
... Test title:PATCH an individual subscription - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed for Fault management individual subscription on VNF
... Pre-conditions: none
- ... Reference: Clause 7.4.5.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 7.4.5.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -60,7 +60,7 @@ DELETE an individual subscription
... Test title:DELETE an individual subscription
... Test objective: The objective is to test that DELETE method removes individual subscription on VNF
... Pre-conditions: The Subsbcription already exists
- ... Reference: Clause 7.4.5.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 7.4.5.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: subscription is deleted
@@ -73,7 +73,7 @@ Get Information about an individual subscription - Not Found
... Test title: Get Information about an individual subscription - Not Found
... Test objective: The objective is to test that the retrieval of an individual subscription for NFVO alarms subscribed by the client fails when subscription is not present
... Pre-conditions: The subscription with the given id does not exists
- ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFFaultManagement-API/NotificationEndpoint.robot b/SOL003/VNFFaultManagement-API/NotificationEndpoint.robot
index 26e0d3804165c9a79a32bccb939c572664823dd4..86fc0cd0bfe40747e95894f09a9aaf31896504c9 100644
--- a/SOL003/VNFFaultManagement-API/NotificationEndpoint.robot
+++ b/SOL003/VNFFaultManagement-API/NotificationEndpoint.robot
@@ -13,7 +13,7 @@ VNF Fault Alarm Notification
... Test title: VNF Fault Alarm Notification
... Test objective: The objective is to test that the POST request triggers VNF Fault Alarm Notification.
... Pre-conditions: A VNF instance is instantiated, and a subscription for fault alarm notifications is available in the VNFM.
- ... Reference: Clause 7.4.6.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 7.4.6.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
@@ -25,7 +25,7 @@ VNF Fault Alarm Cleared Notification
... Test title: VNF Fault Alarm Cleared Notification
... Test objective: The objective is to test that the POST request triggers VNF Fault Alarm Cleared Notification.
... Pre-conditions: A VNF instance is instantiated, and a subscription for fault alarm cleared notifications is available in the VNFM.
- ... Reference: Clause 7.4.6.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 7.4.6.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
@@ -37,7 +37,7 @@ VNF Fault Alarm List Reulit Notification
... Test title: VNF Fault Alarm List Rebuilt Notification
... Test objective: The objective is to test that the POST request triggers VNF Fault Alarm List Rebuilt Notification.
... Pre-conditions: A VNF instance is instantiated, and a subscription for fault alarm list rebuilt notifications is available in the VNFM.
- ... Reference: Clause 7.4.6.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 7.4.6.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFFaultManagementNotification-API/Notifications.robot b/SOL003/VNFFaultManagement-API/Notifications.robot
similarity index 99%
rename from SOL003/VNFFaultManagementNotification-API/Notifications.robot
rename to SOL003/VNFFaultManagement-API/Notifications.robot
index 74a5deb97f60381cc1c3074558016acbc55bcf53..fd4cbfdd3bd28091d58d98226c17a3a7c7b5fced 100644
--- a/SOL003/VNFFaultManagementNotification-API/Notifications.robot
+++ b/SOL003/VNFFaultManagement-API/Notifications.robot
@@ -15,7 +15,7 @@ VNF Fault Alarm Notification
... Test title: VNF Fault Alarm Notification
... Test objective: The objective is to test the dispatch of VNF Fault Alarm Notification when a virtualised resource within an VNF instance fails, and perform a JSON schema and content validation of the delivered notification. The action that triggers the notification under test is an explicit test step, but it is not performed by the test system.
... Pre-conditions: A VNF instance is instantiated, and a subscription for fault alarm notifications is available in the VNFM.
- ... Reference: Clause 7.4.6.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 7.4.6.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -28,7 +28,7 @@ VNF Fault Alarm Cleared Notification
... Test title: VNF Fault Alarm Cleared Notification
... Test objective: The objective is to test the dispatch of VNF Fault Alarm Cleared Notification when a faulty virtualised resource within an VNF instance is cleared, and perform a JSON schema and content validation of the delivered notification. The action that triggers the notification under test is an explicit test step, but it is not performed by the test system.
... Pre-conditions: A VNF instance is instantiated, a virtualised resource is in faulty state, and a subscription for fault alarm cleared notifications is available in the VNFM.
- ... Reference: Clause 7.4.6.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 7.4.6.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -41,7 +41,7 @@ VNF Fault Alarm List Rebuilt Notification
... Test title: VNF Fault Alarm List Rebuilt Notification
... Test objective: The objective is to test the dispatch of VNF Fault Alarm List Rebuilt Notification when the VNFM decides to rebuild the list of its VNF alarms, e.g. due to a corruption in the alarm storage, and perform a JSON schema and content validation of the delivered notification. The action that triggers the notification under test is an explicit test step, but it is not performed by the test system.
... Pre-conditions: A VNF instance is instantiated, one or more virtualised resource are in faulty state, and a subscription for fault alarm list rebuilt notifications is available in the VNFM.
- ... Reference: Clause 7.4.6.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 7.4.6.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFFaultManagement-API/Subscriptions.robot b/SOL003/VNFFaultManagement-API/Subscriptions.robot
index 03fcc2eeb8b0dadd82d80641925604158f9d0cf3..b0f7d57f5d9e119c3a4d60c2e97d23a2d1cead4d 100644
--- a/SOL003/VNFFaultManagement-API/Subscriptions.robot
+++ b/SOL003/VNFFaultManagement-API/Subscriptions.robot
@@ -16,7 +16,7 @@ Create a new Fault Management alarm subscription
... Test title: Create a new Fault Management alarm subscription
... Test objective: The objective is to create a new Fault management alarm subscriptions and perform a JSON schema and content validation of the returned fault management alarms subscription data structure
... Pre-conditions: No subscription with the same filter and callbackUri exists
- ... Reference: Clause 7.4.4.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 7.4.4.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: subscription is created
@@ -31,7 +31,7 @@ Create a new alarm subscription - DUPLICATION
... Test title: Create a new alarm subscription - DUPLICATION
... Test objective: The objective is to create a new subscription with the VNF allowing duplication and perform a JSON schema and content validation of the returned fault management alarms subscription data structure.
... Pre-conditions: subscription with the same filter and callbackUri exists
- ... Reference: Clause 7.4.4.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 7.4.4.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: the NFVO allows creating a subscription resource if another subscription resource with the same filter and callbackUri already exists
... Post-Conditions: duplicated subscription is created
@@ -46,7 +46,7 @@ Create a new alarm subscription - NO DUPLICATION
... Test title: Create a new alarm subscription - NO DUPLICATION
... Test objective: The objective is to create a new subscription with the VNF not allowing duplication and perform a JSON schema and content validation of the returned fault management alarms subscription data structure.
... Pre-conditions: subscription with the same filter and callbackUri exists
- ... Reference: Clause 7.4.4.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 7.4.4.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: the NFVO decides to not create a duplicate subscription resource
... Post-Conditions: duplicated subscription is not created
@@ -60,7 +60,7 @@ Retrieve a list of alarm subscriptions
... Test title: Retrieve a list of alarm subscriptions
... Test objective: The objective is to retrieve the list of active subscriptions and perform a JSON schema and content validation of the returned fault management alarms subscription data structure.
... Pre-conditions: none
- ... Reference: Clause 7.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 7.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: noe
@@ -73,7 +73,7 @@ Retrieve a list of alarm subscriptions with filter
... Test title: Retrieve a list of alarm subscriptions with filter
... Test objective: The objective is to retrieve the list of active subscriptions with filter and perform a JSON schema and content validation of the returned fault management alarms subscription data structure.
... Pre-conditions: none
- ... Reference: Clause 7.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 7.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -86,7 +86,7 @@ GET subscriptions - Bad Request Invalid attribute-based filtering parameters
... Test title: GET subscriptions - Bad Request Invalid attribute-based filtering parameters
... Test objective: The objective is to retrieve the list of active subscriptions with Invalid attribute-based filtering parameters and perform a JSON schema and content validation of the returned problem details data structure.
... Pre-conditions: none
- ... Reference: Clause 7.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 7.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -99,7 +99,7 @@ GET subscriptions with "all_fields" attribute selector
... Test title: GET subscriptions with "all_fields" attribute selector
... Test objective: The objective is to retrieve the list of active subscriptions with attribute selector
... Pre-conditions:
- ... Reference: Clause 7.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 7.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability:
... Post-Conditions:
@@ -112,7 +112,7 @@ GET subscriptions with "exclude_default" attribute selector
... Test title: GET subscriptions with "exclude_default" attribute selector
... Test objective: The objective is to retrieve the list of active subscriptions with attribute selector
... Pre-conditions:
- ... Reference: Clause 7.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 7.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability:
... Post-Conditions:
@@ -125,7 +125,7 @@ GET subscriptions with "fields" attribute selector
... Test title: GET subscriptions with "fields" attribute selector
... Test objective: The objective is to retrieve the list of active subscriptions with attribute selector
... Pre-conditions:
- ... Reference: Clause 7.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 7.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability:
... Post-Conditions:
@@ -138,7 +138,7 @@ GET subscriptions with "exclude_fields" attribute selector
... Test title: GET subscriptions with "exclude_fields" attribute selector
... Test objective: The objective is to retrieve the list of active subscriptions with attribute selector
... Pre-conditions:
- ... Reference: Clause 7.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 7.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability:
... Post-Conditions:
@@ -151,7 +151,7 @@ PUT subscriptions - Method not implemented
... Test title:PUT subscriptions - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to for Fault management subscriptions on VNF
... Pre-conditions: none
- ... RReference: Clause 7.4.4.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... RReference: Clause 7.4.4.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -163,7 +163,7 @@ PATCH subscriptions - Method not implemented
... Test title: PATCH subscriptions - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to for Fault management subscriptions on VNF
... Pre-conditions: none
- ... Reference: Clause 7.4.4.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 7.4.4.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -175,7 +175,7 @@ DELETE subscriptions - Method not implemented
... Test title: DELETE subscriptions - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to for Fault management subscriptions on VNF
... Pre-conditions: none
- ... Reference: Clause 7.4.4.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 7.4.4.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: subscription is not deleted
@@ -187,7 +187,7 @@ Retrieve a list of alarm subscriptions as Paged Response
... Test title: Retrieve a list of alarm subscriptions as Paged Response
... Test objective: The objective is to retrieve the list of active subscriptions as Paged Response.
... Pre-conditions: none
- ... Reference: Clause 7.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 7.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: noe
@@ -200,7 +200,7 @@ GET subscriptions - Bad Request Response too Big
... Test title: GET subscriptions - Bad Request Response too Big
... Test objective: The objective is to retrieve the list of active subscriptions because response is too big and perform a JSON schema and content validation of the returned problem details data structure.
... Pre-conditions: none
- ... Reference: Clause 7.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 7.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -213,7 +213,7 @@ GET Subscription with attribute-based filter "id"
... Test title: GET Subscription with attribute-based filter "id"
... Test objective: The objective is to retrieve the list of active subscriptions with filter "id"
... Pre-conditions:
- ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability:
... Post-Conditions:
@@ -227,7 +227,7 @@ Get subscriptions with filter "filter.notificationTypes"
... Test title: GET Subscription with attribute-based filter "filter.notificationTypes"
... Test objective: The objective is to retrieve the list of active subscriptions with filter "filter.notificationTypes"
... Pre-conditions:
- ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability:
... Post-Conditions:
@@ -241,7 +241,7 @@ Get subscriptions with filter "filter.faultyResourceTypes"
... Test title: GET Subscription with attribute-based filter "filter.faultyResourceTypes"
... Test objective: The objective is to retrieve the list of active subscriptions with filter "filter.faultyResourceTypes"
... Pre-conditions:
- ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability:
... Post-Conditions:
@@ -255,7 +255,7 @@ Get subscriptions with filter "filter.perceivedSeverities"
... Test title: GET Subscription with attribute-based filter "filter.perceivedSeverities"
... Test objective: The objective is to retrieve the list of active subscriptions with filter "filter.perceivedSeverities"
... Pre-conditions:
- ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability:
... Post-Conditions:
@@ -269,7 +269,7 @@ Get subscriptions with filter "filter.eventTypes"
... Test title: GET Subscription with attribute-based filter "filter.eventTypes"
... Test objective: The objective is to retrieve the list of active subscriptions with filter "filter.eventTypes"
... Pre-conditions:
- ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability:
... Post-Conditions:
@@ -283,7 +283,7 @@ Get subscriptions with filter "filter.probableCauses"
... Test title: GET Subscription with attribute-based filter "filter.probableCauses"
... Test objective: The objective is to retrieve the list of active subscriptions with filter "filter.probableCauses"
... Pre-conditions:
- ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability:
... Post-Conditions:
@@ -292,12 +292,12 @@ Get subscriptions with filter "filter.probableCauses"
Check HTTP Response Body Json Schema Is FmSubscriptions
Check PostCondition HTTP Response Body Subscriptions Matches the requested attribute-based filter "filter_probableCauses"
-POST Create a new Subscription - Unprocessable Entity
+POST Create a new Subscription - Unprocessable Content
[Documentation] Test ID: 7.3.5.3.22
- ... Test title: POST Create a new Subscription - Unprocessable Entity
- ... Test objective: The objective is to test that 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.
+ ... Test title: POST Create a new Subscription - Unprocessable Content
+ ... Test objective: The objective is to test that content type of the message content is supported and the message content of a request contains syntactically correct data but the data cannot be processed.
... re-conditions: none
- ... Reference: Clause 7.4.5.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 7.4.5.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFFaultManagement-API/environment/variables.txt b/SOL003/VNFFaultManagement-API/environment/variables.txt
index af645c81e24b10a3f70626de83e8cd480933c29f..b267ef6895851f6fb515db665e569e5b9614413d 100644
--- a/SOL003/VNFFaultManagement-API/environment/variables.txt
+++ b/SOL003/VNFFaultManagement-API/environment/variables.txt
@@ -56,4 +56,13 @@ ${vnfdIds} 6fc3539c-e602-4afa-8e13-962fb5a7d81f
${callbackResp} localhost
-${MOCK_SERVER_JAR} ../../../bin/mockserver-netty-5.5.0-jar-with-dependencies.jar
\ No newline at end of file
+${MOCK_SERVER_JAR} ../../../bin/mockserver-netty-5.5.0-jar-with-dependencies.jar
+
+${callback_endpoint_fwd} /endpoint/check
+${callback_endpoint_error} /endpoint_404
+${sleep_interval} 20s
+${total_polling_time} 2 min
+${polling_interval} 10 sec
+
+${notification_request} []
+${notification_response} []
\ No newline at end of file
diff --git a/SOL003/VNFFaultManagementNotification-API/schemas/alarmClearedNotification.schema.json b/SOL003/VNFFaultManagement-API/schemas/alarmClearedNotification.schema.json
similarity index 100%
rename from SOL003/VNFFaultManagementNotification-API/schemas/alarmClearedNotification.schema.json
rename to SOL003/VNFFaultManagement-API/schemas/alarmClearedNotification.schema.json
diff --git a/SOL003/VNFFaultManagementNotification-API/schemas/alarmListRebuiltNotification.schema.json b/SOL003/VNFFaultManagement-API/schemas/alarmListRebuiltNotification.schema.json
similarity index 100%
rename from SOL003/VNFFaultManagementNotification-API/schemas/alarmListRebuiltNotification.schema.json
rename to SOL003/VNFFaultManagement-API/schemas/alarmListRebuiltNotification.schema.json
diff --git a/SOL003/VNFFaultManagementNotification-API/schemas/alarmNotification.schema.json b/SOL003/VNFFaultManagement-API/schemas/alarmNotification.schema.json
similarity index 100%
rename from SOL003/VNFFaultManagementNotification-API/schemas/alarmNotification.schema.json
rename to SOL003/VNFFaultManagement-API/schemas/alarmNotification.schema.json
diff --git a/SOL003/VNFFaultManagementNotification-API/environment/variables.txt b/SOL003/VNFFaultManagementNotification-API/environment/variables.txt
deleted file mode 100644
index 3c260595f44e10b016d92ead7075287d413dfd72..0000000000000000000000000000000000000000
--- a/SOL003/VNFFaultManagementNotification-API/environment/variables.txt
+++ /dev/null
@@ -1,15 +0,0 @@
-*** Variables ***
-
-${callback_uri} http://localhost
-${callback_port} 9091
-${callback_endpoint} /endpoint
-${callback_endpoint_fwd} /endpoint/check
-${callback_endpoint_error} /endpoint_404
-${sleep_interval} 20s
-${total_polling_time} 2 min
-${polling_interval} 10 sec
-
-${notification_request} []
-${notification_response} []
-
-${MOCK_SERVER_JAR} ../../../bin/mockserver-netty-5.5.0-jar-with-dependencies.jar
\ No newline at end of file
diff --git a/SOL003/VNFFaultManagementNotification-API/schemas/ProblemDetails.schema.json b/SOL003/VNFFaultManagementNotification-API/schemas/ProblemDetails.schema.json
deleted file mode 100644
index 62f17612725e72a6cb3c3a6379aa697f5fc1ae08..0000000000000000000000000000000000000000
--- a/SOL003/VNFFaultManagementNotification-API/schemas/ProblemDetails.schema.json
+++ /dev/null
@@ -1,34 +0,0 @@
-{
- "definitions": {},
- "$schema": "http://json-schema.org/draft-07/schema#",
- "type": "object",
- "description": "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 [19] is reproduced inthis structure. Compared to the general framework defined in IETF RFC 7807 [19], the \"status\" and \"detail\" attributes are mandated to be included by the present document, to ensure that the response contains additional textual information about an error. IETF RFC 7807 [19] foresees extensibility of the \"ProblemDetails\" type. It is possible that particular APIs in the present document, or particular implementations, define extensions to define additional attributes that provide more information about the error. The description column only provides some explanation of the meaning to Facilitate understanding of the design. For a full description, see IETF RFC 7807 [19].\n",
- "properties": {
- "type": {
- "type": "string",
- "description": "A URI reference according to IETF RFC 3986 [5] that identifies the problem type. It is encouraged that the URI provides human-readable documentation for the problem (e.g. using HTML) when dereferenced. When this member is not present, its value is assumed to be \"about:blank\".\n",
- "format": "URI"
- },
- "title": {
- "type": "string",
- "description": "A short, human-readable summary of the problem type. It should not change from occurrence to occurrence of the problem, except for purposes of localization. If type is given and other than \"about:blank\", this attribute shall also be provided. A short, human-readable summary of the problem type. It SHOULD NOT change from occurrence to occurrence of the problem, except for purposes of localization (e.g., using proactive content negotiation; see [RFC7231], Section 3.4).\n"
- },
- "status": {
- "type": "integer",
- "description": "The HTTP status code for this occurrence of the problem. The HTTP status code ([RFC7231], Section 6) generated by the origin server for this occurrence of the problem.\n"
- },
- "detail": {
- "type": "string",
- "description": "A human-readable explanation specific to this occurrence of the problem.\n"
- },
- "instance": {
- "type": "string",
- "description": "A URI reference that identifies the specific occurrence of the problem. It may yield further information if dereferenced.\n",
- "format": "URI"
- }
- },
- "required": [
- "status",
- "detail"
- ]
-}
\ No newline at end of file
diff --git a/SOL003/VNFIndicator-API/ApiVersion.robot b/SOL003/VNFIndicator-API/ApiVersion.robot
index bd7666d7b34f07932322cef52d0b22df6b199d6a..79f573476a8756bb3017189ad8c4be0993915036 100644
--- a/SOL003/VNFIndicator-API/ApiVersion.robot
+++ b/SOL003/VNFIndicator-API/ApiVersion.robot
@@ -13,7 +13,7 @@ POST API Version - Method not implemented
... Test title: POST API version - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -25,7 +25,7 @@ GET API Version
... Test title: GET API Version
... Test objective: The objective is to test that GET method successfully return ApiVersionInformation
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -38,7 +38,7 @@ PUT API Version - Method not implemented
... Test title: PUT API Version - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -50,7 +50,7 @@ PATCH API Version - Method not implemented
... Test title: PATCH API Version - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -62,7 +62,7 @@ DELETE API Version - Method not implemented
... Test title: DELETE API Version - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -74,7 +74,7 @@ POST API Version with apiMajorVerion - Method not implemented
... Test title: POST API version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -86,7 +86,7 @@ GET API Version with apiMajorVerion
... Test title: GET API Version with apiMajorVerion
... Test objective: The objective is to test that GET method successfully return ApiVersionInformation
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -99,7 +99,7 @@ PUT API Version with apiMajorVerion - Method not implemented
... Test title: PUT API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -111,7 +111,7 @@ PATCH API Version with apiMajorVerion - Method not implemented
... Test title: PATCH API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -123,7 +123,7 @@ DELETE API Version with apiMajorVerion - Method not implemented
... Test title: DELETE API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFIndicator-API/IndividualSubscription.robot b/SOL003/VNFIndicator-API/IndividualSubscription.robot
index dc9a90a569e46391ddd78cbd1d0308cab6c4acd9..1dbe79c5936062c3956673af48d2eaa04a161549 100644
--- a/SOL003/VNFIndicator-API/IndividualSubscription.robot
+++ b/SOL003/VNFIndicator-API/IndividualSubscription.robot
@@ -11,7 +11,7 @@ GET Individual VNF Indicator Subscription
... Test title: GET Individual VNF Indicator Subscription
... Test objective: The objective is to test the retrieval of individual VNF indicator subscription and perform a JSON schema validation of the returned subscription data structure
... Pre-conditions: A VNF instance is instantiated. At least one VNF indicator subscription is available in the VNFM.
- ... Reference: Clause 8.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 8.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -24,7 +24,7 @@ GET Individual VNF Indicator Subscription with invalid resource identifier
... Test title: GET Individual VNF Indicator Subscription with invalid resource identifier
... Test objective: The objective is to test that the retrieval of individual VNF indicator subscription fails when using an invalid resource identifier.
... Pre-conditions: A VNF instance is instantiated. At least one VNF indicator subscription is available in the VNFM.
- ... Reference: Clause 8.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 8.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -37,7 +37,7 @@ DELETE Individual VNF Indicator Subscription
... Test title: DELETE Individual VNF Indicator Subscription
... Test objective: The objective is to test the deletion of an individual VNF indicator subscription.
... Pre-conditions: A VNF instance is instantiated. At least one VNF indicator subscription is available in the VNFM.
- ... Reference: Clause 8.4.6.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 8.4.6.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: The subscription to VNF indicators is deleted
@@ -50,7 +50,7 @@ DELETE Individual VNF Indicator Subscription with invalid resource identifier
... Test title: DELETE Individual VNF Indicator Subscription with invalid resource identifier
... Test objective: The objective is to test that the deletion of an individual VNF indicator subscription fails when using an invalid resource identifier.
... Pre-conditions: A VNF instance is instantiated. At least one VNF indicator subscription is available in the VNFM.
- ... Reference: Clause 8.4.6.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 8.4.6.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -62,7 +62,7 @@ PUT Individual VNF Indicator Subscription - Method not implemented
... Test title: PUT Individual VNF Indicator Subscription - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to modify an individual VNF indicator subscription
... Pre-conditions: A VNF instance is instantiated. At least one VNF indicator subscription is available in the VNFM.
- ... Reference: Clause 8.4.6.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 8.4.6.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: The individual VNF indicator subscription is not modified by the operation
@@ -74,7 +74,7 @@ PATCH Individual VNF Indicator Subscription - Method not implemented
... Test title: PATCH Individual VNF Indicator Subscription - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update an individual VNF indicator subscription
... Pre-conditions: A VNF instance is instantiated. At least one VNF indicator subscription is available in the VNFM.
- ... Reference: Clause 8.4.6.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 8.4.6.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -86,7 +86,7 @@ POST Individual VNF Indicator Subscription - Method not implemented
... Test title: POST Individual VNF Indicator Subscription - Method not implemented
... Test objective: The objective is to test that POST method is not allowed to create a new VNF indicator subscription
... Pre-conditions: A VNF instance is instantiated.
- ... Reference: Clause 8.4.6.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 8.4.6.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFIndicator-API/IndividualVNFindicator.robot b/SOL003/VNFIndicator-API/IndividualVNFindicator.robot
index 9a58f1933cc942bbc13fb099fd40693c72b18c25..a5407944d792d2a50bd1132e2970772f3adff039 100644
--- a/SOL003/VNFIndicator-API/IndividualVNFindicator.robot
+++ b/SOL003/VNFIndicator-API/IndividualVNFindicator.robot
@@ -10,7 +10,7 @@ Get Individual Indicator for VNF Instance
... Test title: Get Individual Indicator for VNF Instance
... Test objective: The objective is to test the retrieval of an indicator for a given VNF instance and perform a JSON schema validation of the returned indicator data structure
... Pre-conditions: A VNF instance is instantiated. At least one measure of VNF indicator is available in the VNFM.
- ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -25,7 +25,7 @@ Get Individual Indicator for VNF Instance with invalid indicator identifier
... Test title: Get Individual Indicator for VNF Instance with invalid indicator identifier
... Test objective: The objective is to test that the retrieval of an indicator for a given VNF instance fails when using an invalid resource identifier. The test also checks the JSON schema of the unsuccessful operation HTTP response.
... Pre-conditions: A VNF instance is instantiated. At least one measure of VNF indicator is available in the VNFM.
- ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -38,7 +38,7 @@ POST Individual VNF Indicator for VNF Instance - Method not implemented
... Test title: POST Individual VNF Indicator for VNF Instance - Method not implemented
... Test objective: The objective is to test that POST method is not allowed to create a new VNF indicator in the VNFM
... Pre-conditions: A VNF instance is instantiated.
- ... Reference: Clause 8.4.4.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 8.4.4.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -50,7 +50,7 @@ PUT Individual VNF Indicator for VNF Instance - Method not implemented
... Test title: PUT Individual VNF Indicator for VNF Instance - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to modify an existing indicator for a VNF instance
... Pre-conditions: A VNF instance is instantiated. At least one measure of VNF indicator is available in the VNFM
- ... Reference: Clause 8.4.4.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 8.4.4.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -62,7 +62,7 @@ PATCH Individual VNF Indicator for VNF Instance - Method not implemented
... Test title: PATCH Individual VNF Indicator for VNF Instance - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update an existing indicator for a VNF instance
... Pre-conditions: A VNF instance is instantiated. At least one measure of VNF indicator is available for the given VNF instance.
- ... Reference: Clause 8.4.4.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 8.4.4.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -74,7 +74,7 @@ DELETE Individual VNF Indicator for VNF Instance - Method not implemented
... Test title: DELETE Individual VNF Indicator for VNF Instance - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to delete an existing indicator for a VNF instance
... Pre-conditions: A VNF instance is instantiated. At least one measure of VNF indicator is available in the VNFM
- ... Reference: Clause 8.4.3.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 8.4.3.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFIndicator-API/NotificationEndpoint.robot b/SOL003/VNFIndicator-API/NotificationEndpoint.robot
index 691fc5657399e38b80674ebccb0dacf11bed4d6a..073cfa9269e85d4f422790275cb924fb28772621 100644
--- a/SOL003/VNFIndicator-API/NotificationEndpoint.robot
+++ b/SOL003/VNFIndicator-API/NotificationEndpoint.robot
@@ -12,7 +12,7 @@ VNF Indicator Value Change Notification
... Test title: VNF Indicator Value Change Notification
... Test objective: The objective is to test that the POST request triggers VNF Indicator Value Change Notification.
... Pre-conditions: A VNF is instantiated, and a subscription for indicator value change notifications is available in the VNFM.
- ... Reference: Clause 8.4.7.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 8.4.7.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
@@ -24,7 +24,7 @@ Supported Indicators Change Notification
... Test title: Supported Indicators Change Notification
... Test objective: The objective is to test that the POST request triggers Supported Indicators Change Notification.
... Pre-conditions: A VNF is instantiated, and a individual subscription resource for supported indicators change notifications is available in the VNFM.
- ... Reference: Clause 8.4.7.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 8.4.7.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFIndicator-API/Notifications.robot b/SOL003/VNFIndicator-API/Notifications.robot
index 0895d01f7c58adca56e18ac8f759d427f8f00552..fb16d34882e3047d1cb8e5cac5ff3751d09a3186 100644
--- a/SOL003/VNFIndicator-API/Notifications.robot
+++ b/SOL003/VNFIndicator-API/Notifications.robot
@@ -16,7 +16,7 @@ VNF Indicator Value Change Notification
... Test title: VNF Indicator Value Change Notification
... Test objective: The objective is to test the dispatch of VNF Indicator Value Change Notification when new indicator values are available in the VNFM, and perform a JSON schema and content validation of the delivered notification. The action that triggers the notification under test is an explicit test step, but it is not performed by the test system.
... Pre-conditions: A VNF is instantiated, and a subscription for indicator value change notifications is available in the VNFM.
- ... Reference: Clause 8.4.7.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 8.4.7.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFIndicator-API/Subscriptions.robot b/SOL003/VNFIndicator-API/Subscriptions.robot
index 99f78e2d5c45b763ddfeb79dcbb7b21cd614efc3..f0b69335313027e76ed8f072e4d00449c96c2484 100644
--- a/SOL003/VNFIndicator-API/Subscriptions.robot
+++ b/SOL003/VNFIndicator-API/Subscriptions.robot
@@ -16,7 +16,7 @@ GET All VNF Indicator Subscriptions
... Test title: GET All VNF Indicator Subscriptions
... Test objective: The objective is to test the retrieval of all VNF indicator subscriptions and perform a JSON schema validation of the returned subscriptions data structure
... Pre-conditions: A VNF instance is instantiated. At least one VNF indicator subscription is available in the VNFM.
- ... Reference: Clause 8.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 8.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -29,7 +29,7 @@ GET VNF Indicator Subscriptions with attribute-based filter
... Test title: GET VNF Indicator Subscriptions with attribute-based filter
... Test objective: The objective is to test the retrieval of VNF indicator subscriptions using attribute-based filter, perform a JSON schema validation of the collected indicators data structure, and verify that the retrieved information matches the issued attribute-based filters
... Pre-conditions: A VNF instance is instantiated. At least one VNF indicator subscription is available in the VNFM.
- ... Reference: Clause 8.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 8.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -43,7 +43,7 @@ GET VNF Indicator Subscriptions with invalid attribute-based filter
... Test title: GET VNF Indicator Subscriptions with invalid attribute-based filter
... Test objective: The objective is to test that the retrieval of VNF indicator subscriptions fails when using invalid attribute-based filters, and perform the JSON schema validation of the failed operation HTTP response.
... Pre-conditions: A VNF instance is instantiated. At least one VNF indicator subscription is available in the VNFM.
- ... Reference: Clause 8.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 8.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -56,7 +56,7 @@ GET VNF Indicator Subscriptions with invalid resource endpoint
... Test title: GET VNF Indicator Subscriptions with invalid resource endpoint
... Test objective: The objective is to test that the retrieval of all VNF indicator subscriptions fails when using invalid resource endpoint.
... Pre-conditions: A VNF instance is instantiated. At least one VNF indicator subscription is available in the VNFM.
- ... Reference: Clause 8.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 8.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -68,7 +68,7 @@ Create new VNF indicator subscription
... Test title: Create new VNF indicator subscription
... Test objective: The objective is to test the creation of a new VNF indicator subscription and perform a JSON schema and content validation of the returned subscription data structure
... Pre-conditions: A VNF instance is instantiated.
- ... Reference: Clause 8.4.5.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 8.4.5.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: The VNF indicator subscription is successfully set and it matches the issued subscription
@@ -84,7 +84,7 @@ Create duplicated VNF indicator subscription with VNFM not creating duplicated s
... Test title: Create duplicated VNF indicator subscription with VNFM not creating duplicated subscriptions
... Test objective: The objective is to test the attempt of a creation of a duplicated VNF indicator subscription and check that no new subscription is created by the VNFM and a link to the original subscription is returned
... Pre-conditions: A VNF instance is instantiated. At least one VNF indicator subscription is available in the VNFM.
- ... Reference: Clause 8.4.5.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 8.4.5.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: The VNFM does not support the creation of duplicated subscriptions
... Post-Conditions: The existing VNF indicator subscription returned is available in the VNFM
@@ -100,7 +100,7 @@ Create duplicated VNF indicator subscription with VNFM creating duplicated subsc
... Test title: Create duplicated VNF indicator subscription with VNFM creating duplicated subscriptions
... Test objective: The objective is to test the creation of a duplicated VNF indicator subscription and perform a JSON schema and content validation of the returned duplicated subscription data structure
... Pre-conditions: A VNF instance is instantiated. At least one VNF indicator subscription is available in the VNFM.
- ... Reference: Clause 8.4.5.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 8.4.5.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: The VNFM supports the creation of duplicated subscriptions
... Post-Conditions: The duplicated VNF indicator subscription is successfully set and it matches the issued subscription
@@ -115,7 +115,7 @@ PUT VNF Indicator Subscriptions - Method not implemented
... Test title: PUT VNF Indicator Subscriptions - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to modify VNF indicator subscriptions
... Pre-conditions: A VNF instance is instantiated. At least one VNF indicator subscription is available in the VNFM.
- ... Reference: Clause 8.4.5.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 8.4.5.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -127,7 +127,7 @@ PATCH VNF Indicator Subscriptions - Method not implemented
... Test title: PATCH VNF Indicator Subscriptions - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update VNF indicator subscriptions
... Pre-conditions: A VNF instance is instantiated. At least one VNF indicator subscription is available in the VNFM.
- ... Reference: Clause 8.4.5.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 8.4.5.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -139,7 +139,7 @@ DELETE VNF Indicator Subscriptions - Method not implemented
... Test title: DELETE VNF Indicator Subscriptions - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to delete VNF indicators subscriptions
... Pre-conditions: A VNF instance is instantiated. At least one VNF indicator subscription is available in the VNFM.
- ... Reference: Clause 8.4.5.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 8.4.5.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -151,7 +151,7 @@ GET All VNF Indicator Subscriptions as Paged Response
... Test title: GET All VNF Indicator Subscriptions as Paged Response
... Test objective: The objective is to test the retrieval of all VNF indicator subscriptions as Paged Response.
... Pre-conditions: A VNF instance is instantiated. At least one VNF indicator subscription is available in the VNFM.
- ... Reference: Clause 8.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 8.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -164,7 +164,7 @@ GET VNF Indicator Subscriptions - Bad Request Response too Big
... Test title: GET VNF Indicator Subscriptions - Bad Request Response too Big
... Test objective: The objective is to test that the retrieval of VNF indicator subscriptions fails because reponse is too big, and perform the JSON schema validation of the failed operation HTTP response.
... Pre-conditions: A VNF instance is instantiated. At least one VNF indicator subscription is available in the VNFM.
- ... Reference: Clause 8.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 8.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -172,12 +172,12 @@ GET VNF Indicator Subscriptions - Bad Request Response too Big
Check HTTP Response Status Code Is 400
Check HTTP Response Body Json Schema Is ProblemDetails
-POST Create a new Subscription - Unprocessable Entity
+POST Create a new Subscription - Unprocessable Content
[Documentation] Test ID: 7.3.6.4.13
- ... Test title: POST Create a new Subscription - Unprocessable Entity
- ... Test objective: The objective is to test that 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.
+ ... Test title: POST Create a new Subscription - Unprocessable Content
+ ... Test objective: The objective is to test that content type of the message content is supported and the message content of a request contains syntactically correct data but the data cannot be processed.
... re-conditions: none
- ... Reference: Clause 8.4.5.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 8.4.5.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFIndicator-API/VNFIndicators.robot b/SOL003/VNFIndicator-API/VNFIndicators.robot
index 1afeee3f3499eafed5c621c738f60c57eb343442..5c16a991390cc429b5617d8c24013e0ee19f22e0 100644
--- a/SOL003/VNFIndicator-API/VNFIndicators.robot
+++ b/SOL003/VNFIndicator-API/VNFIndicators.robot
@@ -11,7 +11,7 @@ Get all VNF Indicators
... Test title: Get all VNF Indicators
... Test objective: The objective is to test the retrieval of all the available VNF indicators and perform a JSON schema validation of the collected indicators data structure
... Pre-conditions: A VNF instance is instantiated. One or more measures of VNF indicators are available in the VNFM.
- ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -24,7 +24,7 @@ Get VNF Indicators with attribute-based filter
... Test title: Get VNF Indicators with attribute-based filter
... Test objective: The objective is to test the retrieval of VNF indicators using attribute-based filter, perform a JSON schema validation of the collected indicators data structure, and verify that the retrieved information matches the issued attribute-based filters
... Pre-conditions: A VNF instance is instantiated. One or more measures of VNF indicators are available in the VNFM.
- ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -38,7 +38,7 @@ Get VNF Indicators with invalid attribute-based filter
... Test title: Get VNF Indicators with invalid attribute-based filter
... Test objective: The objective is to test that the retrieval of VNF indicators fails when using invalid attribute-based filters, and perform the JSON schema validation of the failed operation HTTP response.
... Pre-conditions: A VNF instance is instantiated. One or more measures of VNF indicators are available in the VNFM.
- ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -51,7 +51,7 @@ Get all VNF Indicators with malformed authorization token
... Test title: Get all VNF Indicators with malformed authorization token
... Test objective: The objective is to test that the retrieval of VNF indicators fails when using malformed authorization token
... Pre-conditions: A VNF instance is instantiated. One or more measures of VNF indicators are available in the VNFM.
- ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: The VNFM requires the usage of access tokens for authorizing the API requests.
... Post-Conditions: none
@@ -63,7 +63,7 @@ Get all VNF Indicators without authorization token
... Test title: Get all VNF Indicators without authorization token
... Test objective: The objective is to test that the retrieval of VNF indicators fails when omitting the authorization token
... Pre-conditions: A VNF instance is instantiated. One or more measures of VNF indicators are available in the VNFM.
- ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: The VNF requires the usage of access tokens for authorizing the API requests.
... Post-Conditions: none
@@ -75,7 +75,7 @@ GET all VNF Indicators with expired or revoked authorization token
... Test title: GET all VNF Indicators with expired or revoked authorization token
... Test objective: The objective is to test that the retrieval of VNF indicators fails when using expired or revoked authorization token
... Pre-conditions: A VNF instance is instantiated. One or more measures of VNF indicators are available in the VNFM.
- ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: The VNF requires the usage of access tokens for authorizing the API requests.
... Post-Conditions: none
@@ -87,7 +87,7 @@ Get all VNF Indicators with invalid resource endpoint
... Test title: Get all VNF Indicators with invalid resource endpoint
... Test objective: The objective is to test that the retrieval of VNF indicators fails when using invalid resource endpoint
... Pre-conditions: A VNF instance is instantiated. One or more measures of VNF indicators are available in the VNFM.
- ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -99,7 +99,7 @@ POST all VNF Indicators - Method not implemented
... Test title: POST all VNF Indicators - Method not implemented
... Test objective: The objective is to test that POST method is not allowed to create new VNF indicators
... Pre-conditions: A VNF instance is instantiated. One or more measures of VNF indicators are available in the VNFM
- ... Reference: Clause 8.4.2.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 8.4.2.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -111,7 +111,7 @@ PUT all VNF Indicators - Method not implemented
... Test title: PUT all VNF Indicators - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to modify VNF indicators
... Pre-conditions: A VNF instance is instantiated. One or more measures of VNF indicators are available in the VNFM
- ... Reference: Clause 8.4.2.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 8.4.2.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -123,7 +123,7 @@ PATCH all VNF Indicators - Method not implemented
... Test title: PATCH all VNF Indicators - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update VNF indicators
... Pre-conditions: A VNF instance is instantiated. One or more measures of VNF indicators are available in the VNF
- ... Reference: Clause 8.4.2.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 8.4.2.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -135,7 +135,7 @@ DELETE all VNF Indicators - Method not implemented
... Test title: DELETE all VNF Indicators - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to delete VNF indicators
... Pre-conditions: A VNF instance is instantiated. One or more measures of VNF indicators are available in the VNF
- ... Reference: Clause 8.4.2.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 8.4.2.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: The VNF indicators are not deleted by the unsuccessful operation
@@ -148,7 +148,7 @@ Get all VNF Indicators as Paged Response
... Test title: Get all VNF Indicators as Paged Response
... Test objective: The objective is to test the retrieval of all the available VNF indicators as Paged Response.
... Pre-conditions: A VNF instance is instantiated. One or more measures of VNF indicators are available in the VNFM.
- ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -161,7 +161,7 @@ Get VNF Indicators - Bad Request Response too Big
... Test title: Get VNF Indicators - Bad Request Response too Big
... Test objective: The objective is to test that the retrieval of VNF indicators fails because reponse is too big, and perform the JSON schema validation of the failed operation HTTP response.
... Pre-conditions: A VNF instance is instantiated. One or more measures of VNF indicators are available in the VNFM.
- ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFIndicator-API/VnfIndicatorsInVnfInstanceId.robot b/SOL003/VNFIndicator-API/VnfIndicatorsInVnfInstanceId.robot
index d815b49f114623d3b851bf98014871111846a216..9d62078876e9213cfc1feec2771636e53063d223 100644
--- a/SOL003/VNFIndicator-API/VnfIndicatorsInVnfInstanceId.robot
+++ b/SOL003/VNFIndicator-API/VnfIndicatorsInVnfInstanceId.robot
@@ -11,7 +11,7 @@ Get Indicators for VNF Instance
... Test title: Get Indicators for VNF Instance
... Test objective: The objective is to test the retrieval of all indicators for a given VNF instance and perform a JSON schema validation of the returned indicators data structure
... Pre-conditions: A VNF instance is instantiated. One or more measures of VNF indicators are available in the VNFM for the given VNF instance.
- ... Reference: Clause 8.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 8.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -25,7 +25,7 @@ GET Indicators for VNF Instance with attribute-based filter
... Test title: GET Indicators for VNF Instance with attribute-based filter
... Test objective: The objective is to test the retrieval of all indicators for a given VNF instance using attribute-based filter and perform a JSON schema validation of the returned indicators data structure
... Pre-conditions: A VNF instance is instantiated. One or more measures of VNF indicators are available in the VNFM for the given VNF instance.
- ... Reference: Clause 8.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 8.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -39,7 +39,7 @@ Get Indicators for VNF Instance with invalid attribute-based filter
... Test title: Get Indicators for VNF Instance with invalid attribute-based filter
... Test objective: The objective is to test that the retrieval of all indicators for a given VNF instance fails using invalid attribute-based filter. The test also checks the JSON schema of the unsuccessful operation HTTP response.
... Pre-conditions: A VNF instance is instantiated. One or more measures of VNF indicators are available in the VNFM for the given VNF instance.
- ... Reference: Clause 8.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 8.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -52,7 +52,7 @@ Get Indicators for VNF Instance with invalid resource identifier
... Test title: Get Indicators for VNF Instance with invalid resource identifier
... Test objective: The objective is to test that the retrieval of all indicators for a given VNF instance fails when using invalid resource identifier. The test also checks the JSON schema of the unsuccessful operation HTTP response.
... Pre-conditions: A VNF instance is instantiated. One or more measures of VNF indicators are available in the VNFM for the given VNF instance.
- ... Reference: Clause 8.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 8.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -65,7 +65,7 @@ POST Indicators for VNF instance - Method not implemented
... Test title: POST Indicators for VNF instance - Method not implemented
... Test objective: The objective is to test that POST method is not allowed to create new indicators for a VNF instance
... Pre-conditions: A VNF instance is instantiated.
- ... Reference: Clause 8.4.3.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 8.4.3.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -77,7 +77,7 @@ PUT Indicators for VNF instance - Method not implemented
... Test title: PUT Indicators for VNF instance - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to modify existing indicators for a VNF instance
... Pre-conditions: A VNF instance is instantiated. One or more measures of VNF indicators are available in the VNFM for the given VNF instance.
- ... Reference: Clause 8.4.3.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 8.4.3.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -89,7 +89,7 @@ PATCH Indicators for VNF instance - Method not implemented
... Test title: PATCH Indicators for VNF instance - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update existing indicators for a VNF instance
... Pre-conditions: A VNF instance is instantiated. One or more measures of VNF indicators are available in the VNFM for the given VNF instance.
- ... Reference: Clause 8.4.3.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 8.4.3.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -101,7 +101,7 @@ DELETE Indicators for VNF instance - Method not implemented
... Test title: DELETE Indicators for VNF instance - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to delete indicators for a VNF instance
... Pre-conditions: A VNF instance is instantiated. One or more measures of VNF indicators are available in the VNFM for the given VNF instance.
- ... Reference: Clause 8.4.3.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 8.4.3.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -113,7 +113,7 @@ Get Indicators for VNF Instance as Paged Response
... Test title: Get Indicators for VNF Instance as Paged Response
... Test objective: The objective is to test the retrieval of all indicators for a given VNF instance as Paged Response.
... Pre-conditions: A VNF instance is instantiated. One or more measures of VNF indicators are available in the VNFM for the given VNF instance.
- ... Reference: Clause 8.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 8.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -126,7 +126,7 @@ Get Indicators for VNF Instance - Bad Request Response too Big
... Test title: Get Indicators for VNF Instance - Bad Request Response too Big
... Test objective: The objective is to test that the retrieval of all indicators for a given VNF instance fails because response is too big. The test also checks the JSON schema of the unsuccessful operation HTTP response.
... Pre-conditions: A VNF instance is instantiated. One or more measures of VNF indicators are available in the VNFM for the given VNF instance.
- ... Reference: Clause 8.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 8.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFLifecycleManagement-API/ApiVersion.robot b/SOL003/VNFLifecycleManagement-API/ApiVersion.robot
index 5b311ffb630b059790d1c09d6a2b3bc8441668fb..eec99366e671e1d3cfbf6027cc303ad3ee613b78 100644
--- a/SOL003/VNFLifecycleManagement-API/ApiVersion.robot
+++ b/SOL003/VNFLifecycleManagement-API/ApiVersion.robot
@@ -11,7 +11,7 @@ POST API Version - Method not implemented
... Test title: POST API version - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -23,7 +23,7 @@ GET API Version
... Test title: GET API Version
... Test objective: The objective is to test that GET method successfully return ApiVersionInformation
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -36,7 +36,7 @@ PUT API Version - Method not implemented
... Test title: PUT API Version - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -48,7 +48,7 @@ PATCH API Version - Method not implemented
... Test title: PATCH API Version - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -60,7 +60,7 @@ DELETE API Version - Method not implemented
... Test title: DELETE API Version - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -72,7 +72,7 @@ POST API Version with apiMajorVerion - Method not implemented
... Test title: POST API version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -84,7 +84,7 @@ GET API Version with apiMajorVerion
... Test title: GET API Version with apiMajorVerion
... Test objective: The objective is to test that GET method successfully return ApiVersionInformation
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -97,7 +97,7 @@ PUT API Version with apiMajorVerion - Method not implemented
... Test title: PUT API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -109,7 +109,7 @@ PATCH API Version with apiMajorVerion - Method not implemented
... Test title: PATCH API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -121,7 +121,7 @@ DELETE API Version with apiMajorVerion - Method not implemented
... Test title: DELETE API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFLifecycleManagement-API/CancelOperationTask.robot b/SOL003/VNFLifecycleManagement-API/CancelOperationTask.robot
index 777f97321481791e39d7d8357322e9eeb06086e8..5482d6018849e15ef27a7755f4bcfb0953335993 100644
--- a/SOL003/VNFLifecycleManagement-API/CancelOperationTask.robot
+++ b/SOL003/VNFLifecycleManagement-API/CancelOperationTask.robot
@@ -12,7 +12,7 @@ POST Cancel operation task
... Test title: POST Cancel operation task
... Test objective: The POST method initiates cancelling an ongoing VNF lifecycle operation while it is being executed or rolled back, i.e. the "VNF LCM operation occurrence" is either in "PROCESSING" or "ROLLING_BACK" state.
... Pre-conditions: The "VNF LCM operation occurrence" is either in "PROCESSING" or "ROLLING_BACK" state.
- ... Reference: Clause 5.4.17.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.17.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: VNF instance status equal to FAILED_TEMP
@@ -25,7 +25,7 @@ POST Cancel operation task Conflict
... Test title: POST Cancel operation task Conflict
... Test objective: The POST method is NOT cancelling an ongoing VNF lifecycle operation due to the fact that the VNF instance resource is not in STARTING, PROCESSING or ROLLING_BACK state
... Pre-conditions: The "VNF LCM operation occurrence" is not in STARTING, PROCESSING or ROLLING_BACK state
- ... Reference: Clause 5.4.17.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.17.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -38,7 +38,7 @@ POST Cancel operation task Not Found
... Test title: POST Cancel operation task Not Found
... Test objective: The objective is to test that POST method cannot cancel a VNF lifecycle operation because the resource is not found
... Pre-conditions: none
- ... Reference: Clause 5.4.17.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.17.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -51,7 +51,7 @@ GET Cancel operation task - Method not implemented
... Test title: GET Cancel operation task - Method not implemented
... Test objective: The objective is to test that GET method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.17.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.17.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -63,7 +63,7 @@ PUT Cancel operation task - Method not implemented
... Test title: PUT Cancel operation task - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.17.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.17.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -75,7 +75,7 @@ PATCH Cancel operation task - Method not implemented
... Test title: PATCH Cancel operation task - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.17.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.17.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -87,7 +87,7 @@ DELETE Cancel operation task - Method not implemented
... Test title: DELETE Cancel operation task - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.17.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.17.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFLifecycleManagement-API/CancelOperationWorkflow.robot b/SOL003/VNFLifecycleManagement-API/CancelOperationWorkflow.robot
index de51239d67e33fb112e0bd202cdccd8277083da8..f0dd71e4dff88527817fa327574ca1cd7c91c18d 100644
--- a/SOL003/VNFLifecycleManagement-API/CancelOperationWorkflow.robot
+++ b/SOL003/VNFLifecycleManagement-API/CancelOperationWorkflow.robot
@@ -18,7 +18,7 @@ Cancel a VNF LCM Operation - STARTING
... Test title: Cancel a VNF LCM Operation - STARTING
... Test objective: The objective is to test the workflow for Cancelling a VNF LCM Operation being in the STARTING state
... Pre-conditions: The VNF lifecycle management operation occurrence is in STARTING state. NFVO is subscribed to VNF LCM Operation Occurrence notifications (Test ID 5.4.20.1)
- ... Reference: Clause 5.4.17 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.17 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: NFVO is able to receive notifications from VNFM
... Post-Conditions: The VNF lifecycle management operation occurrence is in ROLLED_BACK state
@@ -34,7 +34,7 @@ Cancel a VNF LCM Operation - PROCESSING - ROLLING_BACK
... Test title: Cancel a VNF LCM Operation - PROCESSING - ROLLING_BACK
... Test objective: The objective is to test the workflow for Cancelling a VNF LCM Operation being either in the PROCESSIONG or ROLLING_BACK state
... Pre-conditions: The VNF lifecycle management operation occurrence is in PROCESSING or ROLLING_BACK state. NFVO is subscribed to VNF LCM Operation Occurrence notifications
- ... Reference: Clause 5.3.10 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.3.10 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: NFVO is able to receive notifications from VNFM
... Post-Conditions: The VNF lifecycle management operation occurrence is in FAILED_TEMP state
diff --git a/SOL003/VNFLifecycleManagement-API/ChangeCurrentVNFPackageTask.robot b/SOL003/VNFLifecycleManagement-API/ChangeCurrentVNFPackageTask.robot
index c8166226b42613fb9aaad198a1dfe5d10d8d2117..e95699840c79717807358f6a952eb6e21a41b1fd 100644
--- a/SOL003/VNFLifecycleManagement-API/ChangeCurrentVNFPackageTask.robot
+++ b/SOL003/VNFLifecycleManagement-API/ChangeCurrentVNFPackageTask.robot
@@ -13,7 +13,7 @@ POST Change current VNF Package Task
... Test title: POST Change current VNF Package Task
... Test objective: The objective is to test that the POST method changes the current VNF package on which the VNF instance is based.
... Pre-conditions: none
- ... Reference: Clause 5.4.11a.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.11a.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: in response header Location shall not be null
@@ -26,7 +26,7 @@ POST Change current VNF Package Task - Conflict
... Test title: POST Change current VNF Package Task - Conflict
... Test objective: The objective is to test that the POST method cannot change the current VNF package task when another lifecycle management operation is ongoing.
... Pre-conditions: none
- ... Reference: Clause 5.4.11a.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.11a.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: There is another lifecycle management operation ongoing.
... Post-Conditions: none
@@ -39,7 +39,7 @@ GET Change current VNF Package Task - Method not implemented
... Test title: GET Change current VNF Package Task - Method not implemented
... Test objective: The objective is to test that GET method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.11a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.11a.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -51,7 +51,7 @@ PUT Change current VNF Package Task - Method not implemented
... Test title: PUT Change current VNF Package Task - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.11a.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.11a.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -63,7 +63,7 @@ PATCH Change current VNF Package Task - Method not implemented
... Test title: PATCH Change current VNF Package Task - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.11a.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.11a.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -75,7 +75,7 @@ DELETE Change current VNF Package Task - Method not implemented
... Test title: DELETE Change current VNF Package Task - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.11a.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.11a.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFLifecycleManagement-API/ChangeExternalVNFConnectivityTask.robot b/SOL003/VNFLifecycleManagement-API/ChangeExternalVNFConnectivityTask.robot
index 2cc5c9a66a6b5a03a03fd851a4e82313dbed4613..5c6a9b2df8f5fbb6f4115ae939bd9a2591871618 100644
--- a/SOL003/VNFLifecycleManagement-API/ChangeExternalVNFConnectivityTask.robot
+++ b/SOL003/VNFLifecycleManagement-API/ChangeExternalVNFConnectivityTask.robot
@@ -12,7 +12,7 @@ POST Change external VNF connectivity
... Test title: POST Change external VNF connectivity
... Test objective: The objective is to test that POST method trigger a change in VNF external connectivity
... Pre-conditions: none
- ... Reference: Clause 5.4.11.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.11.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: in response header Location shall not be null
@@ -26,7 +26,7 @@ GET Change external VNF connectivity - Method not implemented
... Test title: GET Change external VNF connectivity - Method not implemented
... Test objective: The objective is to test that GET method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.11.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.11.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -38,7 +38,7 @@ PUT Change external VNF connectivity - Method not implemented
... Test title: PUT Change external VNF connectivity - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.11.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.11.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -50,7 +50,7 @@ PATCH Change external VNF connectivity - Method not implemented
... Test title: PATCH Change external VNF connectivity - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.11.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.11.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -62,7 +62,7 @@ DELETE Change external VNF connectivity - Method not implemented
... Test title: DELETE Change external VNF connectivity - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.11.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.11.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFLifecycleManagement-API/ChangeExternalVNFConnectivityWorkflow.robot b/SOL003/VNFLifecycleManagement-API/ChangeExternalVNFConnectivityWorkflow.robot
index 29221a24d7b6078824a55bdc1bc4080c609f971c..f419f744adbdfd25455b15e56622572d481f9872 100644
--- a/SOL003/VNFLifecycleManagement-API/ChangeExternalVNFConnectivityWorkflow.robot
+++ b/SOL003/VNFLifecycleManagement-API/ChangeExternalVNFConnectivityWorkflow.robot
@@ -17,7 +17,7 @@ Change external connectivity of VNF Workflow
... Test title: Change external connectivity of VNF Workflow
... Test objective: The objective is to change the external connectivity of a VNF instance.
... Pre-conditions: VNF instance in INSTANTIATED state
- ... Reference: Clause 5.4.11 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.11 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: NFVO is able to receive notifications from VNFM. The VNFD supports the external connectivity change
... Post-Conditions: VNF instance still in INSTANTIATED state and external connectivity of the VNF is changed
diff --git a/SOL003/VNFLifecycleManagement-API/ChangeVNFFlavourTask.robot b/SOL003/VNFLifecycleManagement-API/ChangeVNFFlavourTask.robot
index 6449c94c0d0cbe94a3a88fe7c31666744fb9680c..c0ea923096a7f21714118766b735566391ea12d5 100644
--- a/SOL003/VNFLifecycleManagement-API/ChangeVNFFlavourTask.robot
+++ b/SOL003/VNFLifecycleManagement-API/ChangeVNFFlavourTask.robot
@@ -12,7 +12,7 @@ POST Change deployment flavour of a vnfInstance
... Test title: POST Change deployment flavour of a vnfInstance
... Test objective: The objective is to test that POST method trigger a change in VNF deployment flavour
... Pre-conditions: VNF instance resource is not in NOT-INSTANTIATED state
- ... Reference: Clause 5.4.7.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.7.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: in response header Location shall not be null
@@ -26,7 +26,7 @@ POST Change deployment flavour of a vnfInstance Conflict (Not-Instantiated)
... Test title: POST Change deployment flavour of a vnfInstance Conflict (Not-Instantiated)
... Test objective: The objective is to test that POST method cannot trigger a change in VNF deployment flavour because of a conflict with the state of the VNF instance resource. (VNF instance resource is not in NOT-INSTANTIATED state)
... Pre-conditions: VNF instance resource is in NOT-INSTANTIATED state
- ... Reference: Clause 5.4.7.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.7.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -39,7 +39,7 @@ POST Change deployment flavour of a vnfInstance Not Found
... Test title: POST Change deployment flavour of a vnfInstance Not Found
... Test objective: The objective is to test that POST method cannot trigger a change in VNF deployment flavour because the VNF instance resource is not found.
... Pre-conditions: the VNF instance resource is not existing
- ... Reference: Clause 5.4.7.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.7.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -52,7 +52,7 @@ GET Change deployment flavour VNFInstance - Method not implemented
... Test title: GET Change deployment flavour VNFInstance - Method not implemented
... Test objective: The objective is to test that GET method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.7.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.7.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -64,7 +64,7 @@ PUT Change deployment flavour VNFInstance - Method not implemented
... Test title: PUT Change deployment flavour VNFInstance - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.7.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.7.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -76,7 +76,7 @@ PATCH Change deployment flavour VNFInstance - Method not implemented
... Test title: PATCH Change deployment flavour VNFInstance - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.7.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.7.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -88,7 +88,7 @@ DELETE Change deployment flavour VNFInstance - Method not implemented
... Test title: DELETE Change deployment flavour VNFInstance - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.7.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.7.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFLifecycleManagement-API/ChangeVNFFlavourWorkflow.robot b/SOL003/VNFLifecycleManagement-API/ChangeVNFFlavourWorkflow.robot
index 3d4460210e72e81e3087092c53a976c7741bb20e..178c959116fb6a54f04375553f99191e76765591 100644
--- a/SOL003/VNFLifecycleManagement-API/ChangeVNFFlavourWorkflow.robot
+++ b/SOL003/VNFLifecycleManagement-API/ChangeVNFFlavourWorkflow.robot
@@ -17,7 +17,7 @@ Change VNF Flavour Workflow
... Test title: Change VNF Flavour Workflow
... Test objective: The objective is to test the workflow for a change flavour of an existing VNF instance
... Pre-conditions: VNF instance in INSTANTIATED state . NFVO is subscribed to VNF LCM Operation Occurrence notifications
- ... Reference: Clause 5.4.7 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.7 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: Multiple flavours are supported for the VNF (as capability in the VNFD). NFVO is able to receive notifications from VNFM
... Post-Conditions: VNF instance still in INSTANTIATED state and the flavour is changed
diff --git a/SOL003/VNFLifecycleManagement-API/CreateVNFSnapshotTask.robot b/SOL003/VNFLifecycleManagement-API/CreateVNFSnapshotTask.robot
index 462c333d2746521a03f697dd8675df7cde160175..ad90d751223bfe213d97f9dc53737252c8dc5fca 100644
--- a/SOL003/VNFLifecycleManagement-API/CreateVNFSnapshotTask.robot
+++ b/SOL003/VNFLifecycleManagement-API/CreateVNFSnapshotTask.robot
@@ -13,7 +13,7 @@ POST Create VNF Snapshot Task
... Test title: POST Create VNF Snapshot Task
... Test objective: The objective is to test that POST method requests taking a snapshot of a VNF instance.
... Pre-conditions: none
- ... Reference: Clause 5.4.21.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.21.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: in response header Location shall not be null
@@ -26,7 +26,7 @@ POST Create VNF Snapshot Task - NOT FOUND
... Test title: POST Create VNF Snapshot Task - NOT FOUND
... Test objective: The objective is to test that the POST method cannot request for a snapshot if the task is not supported for the VNF instance represented by the parent resource.
... Pre-conditions: none
- ... Reference: Clause 5.4.21.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.21.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: Task is not supported for the VNF instance represented by the parent resource.
... Post-Conditions: none
@@ -39,7 +39,7 @@ POST Create VNF Snapshot Task - CONFLICT
... Test title: POST Create VNF Snapshot Task - CONFLICT
... Test objective: The objective is to test that the POST method cannot request for a snapshot when the VNF instance is in NOT_INSTANTIATED state.
... Pre-conditions: none
- ... Reference: Clause 5.4.21.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.21.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: VNF instance is in NOT_INSTANTIATED state.
... Post-Conditions: none
@@ -47,17 +47,17 @@ POST Create VNF Snapshot Task - CONFLICT
Check HTTP Response Status Code Is 409
Check HTTP Response Body Json Schema Is ProblemDetails
-POST Create VNF Snapshot Task - UNPROCESSIBLE ENTITY
+POST Create VNF Snapshot Task - Unprocessable Content
[Documentation] Test ID: 7.3.1.38.4
- ... Test title: POST Create VNF Snapshot Task - UNPROCESSIBLE ENTITY
+ ... Test title: POST Create VNF Snapshot Task - Unprocessable Content
... Test objective: The objective is to test that the POST method cannot request for a snapshot when the provided identifier of the target "Individual VNF snapshot" resource for the VNF snapshot is invalid.
... Pre-conditions: none
- ... Reference: Clause 5.4.21.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.21.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: The identifier of the target "Individual VNF snapshot" resource for the VNF snapshot is invalid.
... Post-Conditions: none
POST Create VNF Snapshot Task INVALID IDENTIFIER
- Check HTTP Response Status Code Is 409
+ Check HTTP Response Status Code Is 422
Check HTTP Response Body Json Schema Is ProblemDetails
GET Create VNF Snapshot Task - Method not implemented
@@ -65,7 +65,7 @@ GET Create VNF Snapshot Task - Method not implemented
... Test title: GET Create VNF Snapshot Task - Method not implemented
... Test objective: The objective is to test that GET method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.21.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.21.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -77,7 +77,7 @@ PUT Create VNF Snapshot Task - Method not implemented
... Test title: PUT Create VNF Snapshot Task - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.21.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.21.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -89,7 +89,7 @@ PATCH Create VNF Snapshot Task - Method not implemented
... Test title: PATCH Create VNF Snapshot Task - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.21.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.21.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -101,7 +101,7 @@ DELETE Create VNF Snapshot Task - Method not implemented
... Test title: DELETE Create VNF Snapshot Task - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.21.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.21.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFLifecycleManagement-API/CreateVNFWorkflow.robot b/SOL003/VNFLifecycleManagement-API/CreateVNFWorkflow.robot
index a9a438fd3a0b8c540a26e6f056f3d45f16792347..96ff10132f7e5072d2b514f7f583b2b99b7292a0 100644
--- a/SOL003/VNFLifecycleManagement-API/CreateVNFWorkflow.robot
+++ b/SOL003/VNFLifecycleManagement-API/CreateVNFWorkflow.robot
@@ -17,7 +17,7 @@ Create VNF Instance Resource
... Test title: Create VNF Instance workflow
... Test objective: The objective is to test the workflow for the creation of a new VNF instance resource.
... Pre-conditions: NFVO is subscribed to VNF Identifier Creation notifications
- ... Reference: Clause 5.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: NFVO is able to receive notifications from VNFM
... Post-Conditions: The VNF instance resource has been created in "NOT_INSTANTIATED" state.
diff --git a/SOL003/VNFLifecycleManagement-API/DeleteVNFWorkflow.robot b/SOL003/VNFLifecycleManagement-API/DeleteVNFWorkflow.robot
index 57788346983f33b2a488c9710631b62efb255ee6..243b8c1f1126a049bba37106399bfe4c5f134edb 100644
--- a/SOL003/VNFLifecycleManagement-API/DeleteVNFWorkflow.robot
+++ b/SOL003/VNFLifecycleManagement-API/DeleteVNFWorkflow.robot
@@ -17,7 +17,7 @@ Delete VNF Instance Resource
... Test title: Delete VNF Instance workflow
... Test objective: The objective is to test the workflow for the deleteion of an existing VNF instance resource
... Pre-conditions: The VNF Instance resource is in NOT_INSTANTIATED state. NFVO is subscribed to VNF Identifier Creation notifications
- ... Reference: Clause 5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: NFVO is able to receive notifications from VNFM
... Post-Conditions: The VNF instance resource is deleted on the VNFM.
diff --git a/SOL003/VNFLifecycleManagement-API/FailOperationTask.robot b/SOL003/VNFLifecycleManagement-API/FailOperationTask.robot
index 999ec95e2f72e97678919180b8e645415c7bf228..ad99f5a227ca36de74b85a904517733f88dd3b92 100644
--- a/SOL003/VNFLifecycleManagement-API/FailOperationTask.robot
+++ b/SOL003/VNFLifecycleManagement-API/FailOperationTask.robot
@@ -12,7 +12,7 @@ POST Fail operation task
... Test title: POST Fail operation task
... Test objective: The objective is to test that POST method mark as "finally failed" a VNF lifecycle operation
... Pre-conditions: the "VNF LCM operation occurrence" resource is in "FAILED_TEMP" state.
- ... Reference: Clause 5.4.16.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.16.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: VNF resource state is FINALLY_FAILED
@@ -26,7 +26,7 @@ Post Fail operation task Conflict (Not-FAILED_TEMP)
... Test title: Post Fail operation task Conflict (Not-FAILED_TEMP)
... Test objective: The objective is to test that POST method cannot mark as "finally failed" a VNF lifecycle operation
... Pre-conditions: the "VNF LCM operation occurrence" resource is not in "FAILED_TEMP" state.
- ... Reference: Clause 5.4.16.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.16.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -39,7 +39,7 @@ Post Fail operation task Not Found
... Test title: Post Fail operation task Not Found
... Test objective: The objective is to test that POST method cannot mark as "finally failed" a VNF lifecycle operation because the operation is not supported
... Pre-conditions: none
- ... Reference: Clause 5.4.16.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.16.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -52,7 +52,7 @@ GET Fail operation task - Method not implemented
... Test title: GET Fail operation task- Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.16.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.16.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions:
@@ -64,7 +64,7 @@ PUT Fail operation task - Method not implemented
... Test title: PUT Fail operation task- Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.16.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.16.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions:
@@ -76,7 +76,7 @@ PATCH Fail operation task - Method not implemented
... Test title: PATCH Fail operation task- Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.16.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.16.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions:
@@ -88,7 +88,7 @@ DELETE Fail operation task - Method not implemented
... Test title: DELETE Fail operation task- Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.16.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.16.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions:
diff --git a/SOL003/VNFLifecycleManagement-API/FailOperationWorkflow.robot b/SOL003/VNFLifecycleManagement-API/FailOperationWorkflow.robot
index ad52b6092e42f02edcaa17e272948b8f400f767f..5f2b0b7f800bb49b817699b5732a2ee902885ccd 100644
--- a/SOL003/VNFLifecycleManagement-API/FailOperationWorkflow.robot
+++ b/SOL003/VNFLifecycleManagement-API/FailOperationWorkflow.robot
@@ -17,7 +17,7 @@ Fail a VNF LCM Operation Workflow
... Test title: Fail a VNF LCM Operation Workflow
... Test objective: The objective is to test the workflow for a Fail VNF LCM Operation
... Pre-conditions: The VNF lifecycle management operation occurrence is in FAILED_TEMP state. NFVO is subscribed to VNF LCM Operation Occurrence notifications
- ... Reference: Clause 5.4.16 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.16 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: NFVO is able to receive notifications from VNFM
... Post-Conditions: The VNF lifecycle management operation occurrence is in FAILED state
diff --git a/SOL003/VNFLifecycleManagement-API/HealVNFTask.robot b/SOL003/VNFLifecycleManagement-API/HealVNFTask.robot
index 9456305c71c173874eac7eb55a5636dbb27ff2cd..acdca8aef5207a15037205f63fad5ae326094cfa 100644
--- a/SOL003/VNFLifecycleManagement-API/HealVNFTask.robot
+++ b/SOL003/VNFLifecycleManagement-API/HealVNFTask.robot
@@ -12,7 +12,7 @@ POST Heal a vnfInstance
... Test title: POST Heal a vnfInstance
... Test objective: The objective is to test that POST method heal a VNF instance
... Pre-conditions: the VNF instance resource is not in NOT-INSTANTIATED state
- ... Reference: Clause 5.4.9.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.9.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -26,7 +26,7 @@ POST Heal a vnfInstance Conflict (Not-Instantiated)
... Test title: POST Heal a vnfInstance Conflict (Not-Instantiated)
... Test objective: The objective is to test that the operation cannot be executed currently, due to a conflict with the state of the VNF instance resource.
... Pre-conditions: the VNF instance resource is in NOT-INSTANTIATED state
- ... Reference: Clause 5.4.9.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.9.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -39,7 +39,7 @@ POST Heal a vnfInstance Not Found
... Test title: POST Heal a vnfInstance Not Found
... Test objective: The objective is to test that the operation cannot be executed because the VNF instance resource is not found.
... Pre-conditions: the VNF instance resource is not existing
- ... Reference: Clause 5.4.9.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.9.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -52,7 +52,7 @@ GET Heal VNFInstance - Method not implemented
... Test title: GET Heal a vnfInstance - Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.9.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.9.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -64,7 +64,7 @@ PUT Heal VNFInstance - Method not implemented
... Test title: PUT Heal a vnfInstance - Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.9.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.9.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -76,7 +76,7 @@ PATCH Heal VNFInstance - Method not implemented
... Test title: PATCH Heal a vnfInstance - Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.9.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.9.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -88,7 +88,7 @@ DELETE Heal VNFInstance - Method not implemented
... Test title: DELETE Heal a vnfInstance - Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.9.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.9.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFLifecycleManagement-API/HealVNFWorkflow.robot b/SOL003/VNFLifecycleManagement-API/HealVNFWorkflow.robot
index bde625380b89ccd66ace01a3fa86ef4c9cb6a17b..7e5981a31eace31aa3718ca2cf83e37f41681e66 100644
--- a/SOL003/VNFLifecycleManagement-API/HealVNFWorkflow.robot
+++ b/SOL003/VNFLifecycleManagement-API/HealVNFWorkflow.robot
@@ -17,7 +17,7 @@ Heal a VNF Instance
... Test title: Heal a VNF Instance
... Test objective: The objective is to heal a VNF instance.
... Pre-conditions: VNF instance in INSTANTIATED state
- ... Reference: Clause 5.4.9 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.9 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: NFVO is able to receive notifications from VNFM. Heal a VNF instance is supported for the VNF (as capability in the VNFD)
... Post-Conditions: VNF instance still in INSTANTIATED state
diff --git a/SOL003/VNFLifecycleManagement-API/IndividualSubscription.robot b/SOL003/VNFLifecycleManagement-API/IndividualSubscription.robot
index 7f97967f5509d4e15e4ab9603c1f3998c76d5544..bbe48b8eb0216b75267f2269b48691be3eab6d30 100644
--- a/SOL003/VNFLifecycleManagement-API/IndividualSubscription.robot
+++ b/SOL003/VNFLifecycleManagement-API/IndividualSubscription.robot
@@ -11,7 +11,7 @@ POST Individual Subscription - Method not implemented
... Test title: POST Individual Subscription - Method not implemented
... Test objective: The objective is to test that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.19.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.19.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -23,7 +23,7 @@ GET Individual Subscription
... Test title: GET Individual Subscription
... Test objective: The objective is to test the Get individual subscription
... Pre-conditions: none
- ... Reference: Clause 5.4.19.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.19.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -36,7 +36,7 @@ PUT an individual subscription - Method not implemented
... Test title: PUT an individual subscription - Method not implemented
... Test objective: The objective is to test that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.19.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.19.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -48,7 +48,7 @@ PATCH an individual subscription - Method not implemented
... Test title: PATCH an individual subscription - Method not implemented
... Test objective: The objective is to test that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.19.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.19.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -60,7 +60,7 @@ DELETE an individual subscription
... Test title: DELETE an individual subscription
... Test objective: The objective is to test that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.19.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.19.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: subscription deleted from VNFM
@@ -72,7 +72,7 @@ GET Individual Subscription - Not Found
... Test title: GET Individual Subscription - Not Found
... Test objective: The objective is to test the retrieval of individual subscription fails when subscription is not present
... Pre-conditions: none
- ... Reference: Clause 5.4.19.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.19.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFLifecycleManagement-API/IndividualVNFInstance.robot b/SOL003/VNFLifecycleManagement-API/IndividualVNFInstance.robot
index 6564a97caa264fbaafdd75bc2ce9790167ea48a3..f9c88f3d732feb768ee2a79f410c2d52877e4d1f 100644
--- a/SOL003/VNFLifecycleManagement-API/IndividualVNFInstance.robot
+++ b/SOL003/VNFLifecycleManagement-API/IndividualVNFInstance.robot
@@ -16,7 +16,7 @@ Post Individual VNFInstance - Method not implemented
... Test title: Post Individual VNFInstance - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.3.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.3.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -28,7 +28,7 @@ Get Information about an individual VNF Instance
... Test title: Get Information about an individual VNF Instance
... Test objective: The objective is to create a new VNF instance resource
... Pre-conditions: none
- ... Reference: Clause 5.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -43,7 +43,7 @@ PUT Individual VNFInstance - Method not implemented
... Test title: PUT Individual VNFInstance - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.3.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.3.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -55,7 +55,7 @@ PATCH Individual VNFInstance
... Test title: PATCH Individual VNFInstance
... Test objective: This method modifies an individual VNF instance resource
... Pre-conditions: an existing VNF instance resource
- ... Reference: Clause 5.4.3.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.3.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: VNFInstance modified
@@ -68,7 +68,7 @@ PATCH Individual VNFInstance Precondition failed
... Test title: PATCH Individual VNFInstance Precondition failed
... Test objective: The objective is to test that modification of a VNF instance resource fails when a precondition given in an HTTP request header is not fulfilled due to an ETag mismatch
... Pre-conditions: an existing VNF instance resource
- ... Reference: Clause 5.4.3.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.3.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -81,7 +81,7 @@ PATCH Individual VNFInstance Conflict
... Test title: PATCH Individual VNFInstance Conflict
... Test objective: The objective is to test the conflict while modifying a VNF instance resource
... Pre-conditions: another LCM operation is ongoing
- ... Reference: Clause 5.4.3.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.3.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: VNFInstance not modified
@@ -94,7 +94,7 @@ DELETE Individual VNFInstance
... Test title: DELETE Individual VNFInstance
... Test objective: The objective is to delete a VNF instance
... Pre-conditions: the VNF instance resource is existing
- ... Reference: Clause 5.4.3.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.3.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: VNFInstance deleted
@@ -106,7 +106,7 @@ DELETE Individual VNFInstance Conflict
... Test title: DELETE Individual VNFInstance Conflict
... Test objective: The objective is to verify that the deletion cannot be executed currently, due to a conflict with the state of the VNF instance resource.
... Pre-conditions: VNF instance resource is in INSTANTIATED state
- ... Reference: Clause 5.4.3.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.3.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: Resources are not deleted
@@ -120,7 +120,7 @@ Get Information about an individual VNF Instance - Not Found
... Test title: Get Information about an individual VNF Instance - Not Found
... Test objective: The objective is to test that the retrieval of an individual VNF Instance fails when instance is not present.
... Pre-conditions: none
- ... Reference: Clause 5.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFLifecycleManagement-API/IndividualVNFSnapshot.robot b/SOL003/VNFLifecycleManagement-API/IndividualVNFSnapshot.robot
index dcae1ad2fe34ed2237e278671712087355b9be07..6242a630022eb9da56c7ad277580aedc9cc79408 100644
--- a/SOL003/VNFLifecycleManagement-API/IndividualVNFSnapshot.robot
+++ b/SOL003/VNFLifecycleManagement-API/IndividualVNFSnapshot.robot
@@ -7,7 +7,7 @@ POST Individual VNF Snapshot - Method not implemented
... Test title: POST Individual VNF Snapshot - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.24.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.24.4.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -19,7 +19,7 @@ GET Information about an individual VNF Snapshot - SUCCESSFUL
... Test title: GET Information about an individual VNF Snapshot - SUCCESSFUL
... Test objective: The objective is to GET information about an individual VNF Snapshot
... Pre-conditions: none
- ... Reference: Clause 5.4.24.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.24.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -33,7 +33,7 @@ GET Information about an individual VNF Snapshot - NOT FOUND
... Test title: GET Information about an individual VNF Snapshot - NOT FOUND
... Test objective: The objective is to test that the retrieval of individual VNF Snapshot fails when using an invalid resource identifier.
... Pre-conditions: none
- ... Reference: Clause 5.4.24.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.24.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -46,7 +46,7 @@ PUT Individual VNF Snapshot - Method not implemented
... Test title: PUT Individual VNF Snapshot - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.24.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.24.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: VNF Snapshot not modified
@@ -58,7 +58,7 @@ PATCH Individual VNF Snapshot - Success
... Test title: PATCH Individual VNF Snapshot - Success
... Test objective: The objective is to test that PATCH method successfully modifies an individual VNF Snapshot resource
... Pre-conditions: none
- ... Reference: Clause 5.4.24.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.24.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: VNF Snapshot modified
@@ -72,7 +72,7 @@ PATCH Individual VNF Snapshot - Conflict
... Test title: PATCH Individual VNF Snapshot - Success
... Test objective: The objective is to test that PATCH method cannot modify an individual VNF Snapshot resource due to the fact that another modification is ongoing.
... Pre-conditions: none
- ... Reference: Clause 5.4.24.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.24.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: The Individual VNF Snapshot resource is currently being modified due to an underlying VNF snapshot operation.
... Post-Conditions: none
@@ -85,7 +85,7 @@ PATCH Individual VNF Snapshot - Precondition Failed
... Test title: PATCH Individual VNF Snapshot - Precondition Failed
... Test objective: The objective is to that the modification of individual VNF Snapshot fails because precondition given in an HTTP request header is not fulfilled due to an ETag mismatch.
... Pre-conditions: none
- ... Reference: Clause 5.4.24.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.24.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: VNF snapshot is not modified
@@ -98,7 +98,7 @@ DELETE Individual VNF Snapshot
... Test title: DELETE Individual VNF Snapshot
... Test objective: The objective is to delete a VNF Snapshot
... Pre-conditions: none
- ... Reference: Clause 5.4.24.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.24.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: VNF Snapshot deleted
@@ -111,7 +111,7 @@ DELETE Individual VNF Snapshot - Conflict
... Test title: DELETE Individual VNF Snapshot Conflict
... Test objective: The objective is to verify that The operation cannot be executed currently, due to a conflict with the state of the VNF Snapshot resource.
... Pre-conditions: none
- ... Reference: Clause 5.4.24.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.24.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: VNF snapshot is in use by some operation such as reverting a VNF instance to a VNF snapshot or creating a VNF snapshot package.
... Post-Conditions: none
diff --git a/SOL003/VNFLifecycleManagement-API/IndividualVnfLcmOperationOccurence.robot b/SOL003/VNFLifecycleManagement-API/IndividualVnfLcmOperationOccurence.robot
index 6791de45b537724d0ba1c769867f7be7c9446a7b..73ab723fb2246db3cff3b8970fb72d66a1a7a9c8 100644
--- a/SOL003/VNFLifecycleManagement-API/IndividualVnfLcmOperationOccurence.robot
+++ b/SOL003/VNFLifecycleManagement-API/IndividualVnfLcmOperationOccurence.robot
@@ -11,7 +11,7 @@ Post Individual VNF LCM Operation occurrences - Method not implemented
... Test title: Post Individual VNF LCM Operation occurrences - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.13.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.13.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -23,7 +23,7 @@ Get Individual VNF LCM Operation occurrences
... Test title: Get Individual VNF LCM Operation occurrences
... Test objective: The objective is to test that this method retrieve information about a VNF lifecycle management operation occurrence
... Pre-conditions: none
- ... Reference: Clause 5.4.13.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.13.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -37,7 +37,7 @@ PUT Individual VNF LCM Operation occurrences - Method not implemented
... Test title: PUT Individual VNF LCM Operation occurrences - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.13.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.13.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -49,7 +49,7 @@ PATCH Individual VNF LCM Operation occurrences - Method not implemented
... Test title: PATCH Individual VNF LCM Operation occurrences - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.13.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.13.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -61,7 +61,7 @@ DELETE Individual VNF LCM Operation occurrences - Method not implemented
... Test title: DELETE Individual VNF LCM Operation occurrences - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.13.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.13.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -73,7 +73,7 @@ Get Individual VNF LCM Operation occurrences - Not Found
... Test title: Get Individual VNF LCM Operation occurrences - Not Found
... Test objective: The objective is to test that the retrieval of VNF lifecycle management operation occurrence fails when instance is not present.
... Pre-conditions: none
- ... Reference: Clause 5.4.13.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.13.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFLifecycleManagement-API/InstantiateVNFTask.robot b/SOL003/VNFLifecycleManagement-API/InstantiateVNFTask.robot
index f4de0362c81e0557f950abeaae0d7091dd8bad27..0d1d1acd9e863a1af4adc449c711129982a9b7f8 100644
--- a/SOL003/VNFLifecycleManagement-API/InstantiateVNFTask.robot
+++ b/SOL003/VNFLifecycleManagement-API/InstantiateVNFTask.robot
@@ -13,7 +13,7 @@ Instantiate a vnfInstance
... Test title: Post Instantiate Individual VNFInstance
... Test objective: The objective is to instantiate a VNF instance
... Pre-conditions: VNF instance resource is in NOT INSTANTIATED state
- ... Reference: Clause 5.4.4.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.4.4.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -27,7 +27,7 @@ Instantiate a vnfInstance Conflict
... Test title: Post Instantiate Individual VNFInstance
... Test objective: The objective is to verify that the instantiation of the vnf cannot be executed currently, due to a conflict with the state of the VNF instance resource.
... Pre-conditions: VNF instance resource is in INSTANTIATED state
- ... Reference: Clause 5.4.4.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.4.4.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -40,7 +40,7 @@ GET Instantiate VNFInstance - Method not implemented
... Test title: GET Instantiate Individual VNFInstance - Method not implemented
... Test objective: The objective is to test that GET method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -52,7 +52,7 @@ PUT Instantiate VNFInstance - Method not implemented
... Test title: PUT Instantiate Individual VNFInstance - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.4.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.4.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -64,7 +64,7 @@ PATCH Instantiate VNFInstance - Method not implemented
... Test title: PATCH Instantiate Individual VNFInstance - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.4.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.4.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -76,7 +76,7 @@ DELETE Instantiate VNFInstance - Method not implemented
... Test title: DELETE Instantiate Individual VNFInstance - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.4.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.4.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFLifecycleManagement-API/InstantiateVNFTaskWorkflow.robot b/SOL003/VNFLifecycleManagement-API/InstantiateVNFTaskWorkflow.robot
index c2ad47b788b3968b4b999585ce3d9f36374805d8..db6caddb1638cf3c327329b2cc4c5b11eef4ae66 100644
--- a/SOL003/VNFLifecycleManagement-API/InstantiateVNFTaskWorkflow.robot
+++ b/SOL003/VNFLifecycleManagement-API/InstantiateVNFTaskWorkflow.robot
@@ -20,7 +20,7 @@ VNF Instantiation
... Test title: VNF Instantiation workflow
... Test objective: The objective is to test the workflow for the instantiation of a VNF instance
... Pre-conditions: VNF instance resources is already created. NFVO is subscribed to VNF LCM Operation Occurrence notifications
- ... Reference: Clause 5.4.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: NFVO is able to receive notifications from VNFM
... Post-Conditions: VNF instance in INSTANTIATED state
@@ -38,7 +38,7 @@ VNF Instantiation with attribute instantiationLevelId
... Test title: VNF Instantiation workflow with attribute instantiationLevelId
... Test objective: The objective is to test the workflow for the instantiation of a VNF instance
... Pre-conditions: VNF instance resources is already created. NFVO is subscribed to VNF LCM Operation Occurrence notifications
- ... Reference: Clause 5.4.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: NFVO is able to receive notifications from VNFM
... Post-Conditions: VNF instance in INSTANTIATED state
@@ -56,7 +56,7 @@ VNF Instantiation with attribute targetScaleLevelInfo
... Test title: VNF Instantiation workflow with attribute targetScaleLevelInfo
... Test objective: The objective is to test the workflow for the instantiation of a VNF instance
... Pre-conditions: VNF instance resources is already created. NFVO is subscribed to VNF LCM Operation Occurrence notifications
- ... Reference: Clause 5.4.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: NFVO is able to receive notifications from VNFM
... Post-Conditions: VNF instance in INSTANTIATED state
diff --git a/SOL003/VNFLifecycleManagement-API/ModifyVNFInformationWorkflow.robot b/SOL003/VNFLifecycleManagement-API/ModifyVNFInformationWorkflow.robot
index 5be4723e000784a1d0bd7506addd79aeba48c5a3..e700d2caff6ba1173c883ba8e5505bae1658941d 100644
--- a/SOL003/VNFLifecycleManagement-API/ModifyVNFInformationWorkflow.robot
+++ b/SOL003/VNFLifecycleManagement-API/ModifyVNFInformationWorkflow.robot
@@ -17,7 +17,7 @@ Modify info of a VNF Instance
... Test title: Update information about a VNF instance
... Test objective: The objective is to update information about a VNF instance.
... Pre-conditions: VNF instance is created
- ... Reference: Clause 5.3.6 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.3.6 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: NFVO is able to receive notifications from VNFM. Update information of a VNF instance is supported for the VNF (as capability in the VNFD)
... Post-Conditions: VNF instance info is updated
diff --git a/SOL003/VNFLifecycleManagement-API/NotificationEndpoint.robot b/SOL003/VNFLifecycleManagement-API/NotificationEndpoint.robot
index abfaa9d5b081c3f990d74dff13df690c49d3024b..81a032c257ebdf9619fa27626f92664e61ca6d9c 100644
--- a/SOL003/VNFLifecycleManagement-API/NotificationEndpoint.robot
+++ b/SOL003/VNFLifecycleManagement-API/NotificationEndpoint.robot
@@ -13,7 +13,7 @@ VNF LCM Operation Occurrence Notification
... Test title: VNF LCM Operation Occurrence Notification
... Test objective: The objective is to test that the POST request triggers VNF LCM Operation Occurrence Notification.
... Pre-conditions: A subscription for VNF LCM Operation Occurrence notifications is available in the VNFM.
- ... Reference: Clause 5.4.20.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.20.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
@@ -25,7 +25,7 @@ VNF Identifier Creation Notification
... Test title: VNF Identifier Creation Notification
... Test objective: The objective is to test that the POST request triggers VNF Identifier Creation Notification.
... Pre-conditions: A subscription for VNF identifier creation cotification is available in the VNFM.
- ... Reference: Clause 5.4.20.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.20.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
@@ -37,7 +37,7 @@ VNF Identifier Deletion Notification
... Test title: VNF Identifier Deletion Notification
... Test objective: The objective is to test that the POST request triggers VNF Identifier Deletion Notification.
... Pre-conditions: A subscription for VNF identifier deletion notifications is available in the VNFM.
- ... Reference: Clause 5.4.20.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.20.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFLifecycleManagement-API/Notifications.robot b/SOL003/VNFLifecycleManagement-API/Notifications.robot
index d66983b1449ca07b0ccf2e32e1a548f06ae6d7b1..6f1a0c072cc4752053aa2b9991820134adf73f5b 100644
--- a/SOL003/VNFLifecycleManagement-API/Notifications.robot
+++ b/SOL003/VNFLifecycleManagement-API/Notifications.robot
@@ -13,7 +13,7 @@ VNF LCM Operation Occurrence Start Notification
... Test title: VNF LCM Operation Occurrence Start Notification
... Test objective: The objective is to test the dispatch of VNF LCM Operation Occurrence Start Notification when a new VNF LCM operation is started in the VNFM, and perform a JSON schema and content validation of the delivered notification. The action that triggers the notification under test is an explicit test step, but it is not performed by the test system.
... Pre-conditions: A subscription for VNF LCM Operation Occurrence notifications is available in the VNFM.
- ... Reference: Clause 5.4.20.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.20.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -27,7 +27,7 @@ VNF LCM Operation Occurrence Result Notification
... Test title: VNF LCM Operation Occurrence Result Notification
... Test objective: The objective is to test the dispatch of VNF LCM Operation Occurrence Result Notification when a VNF LCM operation is completed in the VNFM, and perform a JSON schema and content validation of the delivered notification. The action that triggers the notification under test is an explicit test step, but it is not performed by the test system.
... Pre-conditions: An VNF LCM operation is in progress, and a subscription for VNF LCM Operation Occurrence notifications is available in the VNFM.
- ... Reference: Clause 5.4.20.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.20.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -41,7 +41,7 @@ VNF Identifier Creation Notification
... Test title: VNF Identifier Creation Notification
... Test objective: The objective is to test the dispatch of VNF Identifier Creation Notification when a new VNF instance resource is created in the VNFM, and perform a JSON schema and content validation of the delivered notification. The action that triggers the notification under test is an explicit test step, but it is not performed by the test system.
... Pre-conditions: A subscription for VNF identifier creation notifications is available in the VNFM.
- ... Reference: Clause 5.4.20.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.20.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -54,7 +54,7 @@ VNF Identifier Deletion Notification
... Test title: VNF Identifier Deletion Notification
... Test objective: The objective is to test the dispatch of VNF Identifier Deletion Notification when a VNF instance resource is deleted in the VNFM, and perform a JSON schema and content validation of the delivered notification. The action that triggers the notification under test is an explicit test step, but it is not performed by the test system.
... Pre-conditions: A VNF instance resource is created, and a subscription for VNF identifier creation notifications is available in the VNFM.
- ... Reference: Clause 6.4.18.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 6.4.18.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFLifecycleManagement-API/OperateVNFTask.robot b/SOL003/VNFLifecycleManagement-API/OperateVNFTask.robot
index c77030125f6e4db6c600437bc0c88db5987aa758..f3b492c2ea9e3b2eaa29e26856408264db6a7a6d 100644
--- a/SOL003/VNFLifecycleManagement-API/OperateVNFTask.robot
+++ b/SOL003/VNFLifecycleManagement-API/OperateVNFTask.robot
@@ -14,7 +14,7 @@ POST Operate a vnfInstance
... Test title: POST Operate a vnfInstance
... Test objective: The objective is to test that POST method operate a VNF instance
... Pre-conditions: none
- ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -27,7 +27,7 @@ POST Operate a vnfInstance Conflict (Not-Instantiated)
... Test title: POST Operate a vnfInstance Conflict (Not-Instantiated)
... Test objective: The objective is to test that the operation cannot be executed currently, due to a conflict with the state of the VNF instance resource.
... Pre-conditions: the VNF instance resource is in NOT-INSTANTIATED state
- ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -40,7 +40,7 @@ POST Operate a vnfInstance Not Found
... Test title: POST Operate a vnfInstance Not Found
... Test objective: The objective is to test that the operation cannot be executed currently, because the resource is not existing
... Pre-conditions: the VNF instance resource is in not existing
- ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -53,7 +53,7 @@ GET Operate VNFInstance - Method not implemented
... Test title: GET Operate a vnfInstance - Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.10.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.10.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -65,7 +65,7 @@ PUT Operate VNFInstance - Method not implemented
... Test title: PUT Operate a vnfInstance - Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.10.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.10.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -77,7 +77,7 @@ PATCH Operate VNFInstance - Method not implemented
... Test title: PATCH Operate a vnfInstance - Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.10.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.10.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -89,7 +89,7 @@ DELETE Operate VNFInstance - Method not implemented
... Test title: DELETE Operate a vnfInstance - Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.10.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.10.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFLifecycleManagement-API/OperateVNFWorkflow.robot b/SOL003/VNFLifecycleManagement-API/OperateVNFWorkflow.robot
index a678af07e528d37f839a70824b6c038b9621e834..8927ca37504bb217957b975927d5ba16db2195a3 100644
--- a/SOL003/VNFLifecycleManagement-API/OperateVNFWorkflow.robot
+++ b/SOL003/VNFLifecycleManagement-API/OperateVNFWorkflow.robot
@@ -18,7 +18,7 @@ Operate a VNF Instance
... Test title: Operate a VNF Instance
... Test objective: The objective is to test the workflow of operational change of a VNF instance.
... Pre-conditions: VNF instance in INSTANTIATED state
- ... Reference: Clause 5.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: change the operational state of a VNF instance is supported for the VNF (as capability in the VNFD)
... Post-Conditions: VNF instance still in INSTANTIATED state and the operational state is changed
diff --git a/SOL003/VNFLifecycleManagement-API/RetryOperationTask.robot b/SOL003/VNFLifecycleManagement-API/RetryOperationTask.robot
index 2c480c27383427efdfb1570467a721b3dbc29ba2..3dea0a1823e6d824f86d92bc7faec83e5eebcc3d 100644
--- a/SOL003/VNFLifecycleManagement-API/RetryOperationTask.robot
+++ b/SOL003/VNFLifecycleManagement-API/RetryOperationTask.robot
@@ -15,7 +15,7 @@ Post Retry operation task
... Test title: Post Retry operation task
... Test objective: The objective is to test that POST method The POST method initiates retrying a VNF lifecycle operation if the operation is in FAILED_TEMP state
... Pre-conditions: the "VNF LCM operation occurrence" resource is in "FAILED_TEMP" state.
- ... Reference: Clause 5.4.14.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.14.4.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -29,7 +29,7 @@ Post Retry operation task Conflict (Not-FAILED_TEMP)
... Test title: Post Retry operation task Conflict (Not-FAILED_TEMP)
... Test objective: The objective is to test that the retry operation cannot be executed currently, due to a conflict with the state of the VNF instance resource. (i.e. the VNF instance resource is not in FAILED_TEMP state)
... Pre-conditions: the "VNF LCM operation occurrence" resource is not in "FAILED_TEMP" state.
- ... Reference: Clause 5.4.14.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.14.4.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -42,7 +42,7 @@ Post Retry operation task Not Found
... Test title: Post Retry operation task Not Found
... Test objective: The objective is to test that the retry operation cannot be executed because the operation is not supported
... Pre-conditions:
- ... Reference: Clause 5.4.14.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.14.4.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -55,7 +55,7 @@ GET Retry operation task - Method not implemented
... Test title: GET Retry operation task- Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.14.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.14.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -67,7 +67,7 @@ PUT Retry operation task - Method not implemented
... Test title: PUT Retry operation task- Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.14.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.14.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -79,7 +79,7 @@ PATCH Retry operation task - Method not implemented
... Test title: PATCH Retry operation task- Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.14.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.14.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -91,7 +91,7 @@ DELETE Retry operation task - Method not implemented
... Test title: DELETE Retry operation task- Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.14.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.14.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFLifecycleManagement-API/RetryOperationWorkflow.robot b/SOL003/VNFLifecycleManagement-API/RetryOperationWorkflow.robot
index 39509283ad7ae96023eae2b0165b4145182a3027..8573e1993447f05c0a841d610b78eb3f371adc71 100644
--- a/SOL003/VNFLifecycleManagement-API/RetryOperationWorkflow.robot
+++ b/SOL003/VNFLifecycleManagement-API/RetryOperationWorkflow.robot
@@ -15,7 +15,7 @@ Retry VNF LCM Operation - Successful
... Test title: Retry VNF LCM Operation - Successful
... Test objective: The objective is to test the workflow for a successful Retry VNF LCM Operation and the status notifications
... Pre-conditions: The VNF lifecycle management operation occurrence is in FAILED_TEMP state. NFVO is subscribed to VNF LCM Operation Occurrence notifications
- ... Reference: Clause 5.3.10 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.3.10 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: NFVO is able to receive notifications from VNFM
... Post-Conditions: The VNF lifecycle management operation occurrence is in COMPLETED state
@@ -30,7 +30,7 @@ Retry VNF LCM Operation - Unsuccessful
... Test title: Retry VNF LCM Operation - Unsuccessful
... Test objective: The objective is to test the workflow for an unsuccesful Retry VNF LCM Operation and the status notifications
... Pre-conditions: The VNF lifecycle management operation occurrence is in FAILED_TEMP state. NFVO is subscribed to VNF LCM Operation Occurrence notifications
- ... Reference: Clause 5.3.10 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.3.10 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: NFVO is able to receive notifications from VNFM
... Post-Conditions: The VNF lifecycle management operation occurrence is in FAILED_TEMP state
diff --git a/SOL003/VNFLifecycleManagement-API/RevertToVNFSnapshotTask.robot b/SOL003/VNFLifecycleManagement-API/RevertToVNFSnapshotTask.robot
index 5ffc640159dc82c60d2a66c275040925444f98a6..d822f3c29cf6d4a3afef95665f8b42f0a1998f8e 100644
--- a/SOL003/VNFLifecycleManagement-API/RevertToVNFSnapshotTask.robot
+++ b/SOL003/VNFLifecycleManagement-API/RevertToVNFSnapshotTask.robot
@@ -13,7 +13,7 @@ POST Revert to VNF Snapshot Task
... Test title: POST Revert to VNF Snapshot Task
... Test objective: The objective is to test that POST method requests reverting a VNF/VNFC instance to a VNF/VNFC snapshot.
... Pre-conditions: none
- ... Reference: Clause 5.4.22.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.22.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: in response header Location shall not be null
@@ -26,7 +26,7 @@ POST Revert to VNF Snapshot Task - NOT FOUND
... Test title: POST Revert to VNF Snapshot Task - NOT FOUND
... Test objective: The objective is to test that the POST method cannot request reverting to a snapshot if the task is not supported for the VNF instance represented by the parent resource.
... Pre-conditions: none
- ... Reference: Clause 5.4.22.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.22.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: Task is not supported for the VNF instance represented by the parent resource.
... Post-Conditions: none
@@ -39,7 +39,7 @@ POST Revert to VNF Snapshot Task - CONFLICT
... Test title: POST Revert to VNF Snapshot Task - CONFLICT
... Test objective: The objective is to test that the POST method cannot request reverting to a snapshot when the VNF instance is in NOT_INSTANTIATED state.
... Pre-conditions: none
- ... Reference: Clause 5.4.22.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.22.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: VNF instance is in NOT_INSTANTIATED state.
... Post-Conditions: none
@@ -52,7 +52,7 @@ GET Revert to VNF Snapshot Task - Method not implemented
... Test title: GET Revert to VNF Snapshot Task - Method not implemented
... Test objective: The objective is to test that GET method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.22.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.22.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -64,7 +64,7 @@ PUT Revert to VNF Snapshot Task - Method not implemented
... Test title: PUT Revert to VNF Snapshot Task - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.22.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.22.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -76,7 +76,7 @@ PATCH Revert to VNF Snapshot Task - Method not implemented
... Test title: PATCH Revert to VNF Snapshot Task - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.22.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.22.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -88,7 +88,7 @@ DELETE Revert to VNF Snapshot Task - Method not implemented
... Test title: DELETE Revert to sVNF Snapshot Task - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.22.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.22.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFLifecycleManagement-API/RollBackOperationWorkflow.robot b/SOL003/VNFLifecycleManagement-API/RollBackOperationWorkflow.robot
index 26556498aeace7c2599e57ca94268d94d8ff7e0b..7d12061f7850954b880ce676fd46d959f94a4ae7 100644
--- a/SOL003/VNFLifecycleManagement-API/RollBackOperationWorkflow.robot
+++ b/SOL003/VNFLifecycleManagement-API/RollBackOperationWorkflow.robot
@@ -17,7 +17,7 @@ Rollback a VNF LCM Operation - Successful
... Test title: Rollback VNF LCM Operation - Successful
... Test objective: The objective is to test the workflow for a Rolling Back a VNF LCM Operation and the operation is successful
... Pre-conditions: The VNF lifecycle management operation occurrence is in FAILED_TEMP state. NFVO is subscribed to VNF LCM Operation Occurrence notifications
- ... Reference: Clause 5.3.11 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.3.11 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: NFVO is able to receive notifications from VNFM
... Post-Conditions: The VNF lifecycle management operation occurrence is in ROLLED_BACK state
@@ -32,7 +32,7 @@ Rollback VNF LCM Operation - Unsuccessful
... Test title: Rollback VNF LCM Operation - Unsuccessful
... Test objective: The objective is to test the workflow for a Rollback VNF LCM Operation and the operation is not successful
... Pre-conditions: The VNF lifecycle management operation occurrence is in FAILED_TEMP state. NFVO is subscribed to VNF LCM Operation Occurrence notifications
- ... Reference: Clause 5.3.10 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.3.10 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: NFVO is able to receive notifications from VNFM
... Post-Conditions: The VNF lifecycle management operation occurrence is in FAILED_TEMP state
diff --git a/SOL003/VNFLifecycleManagement-API/RollbackOperationTask.robot b/SOL003/VNFLifecycleManagement-API/RollbackOperationTask.robot
index 4e1193ea2170690873ba83e3ca0547b6d8f51c31..445bb0a5a96a7859adc8aef47570b2ca1821123d 100644
--- a/SOL003/VNFLifecycleManagement-API/RollbackOperationTask.robot
+++ b/SOL003/VNFLifecycleManagement-API/RollbackOperationTask.robot
@@ -14,7 +14,7 @@ Post Rollback operation task
... Test title: Post Rollback operation task
... Test objective: The objective is to test that POST method initiates rollback on a VNF lifecycle operation
... Pre-conditions: the "VNF LCM operation occurrence" resource is in "FAILED_TEMP" state.
- ... Reference: Clause 5.4.15.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.15.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -28,7 +28,7 @@ POST Rollback operation task Conflict (Not-FAILED_TEMP)
... Test title: POST Rollback operation task Conflict (Not-FAILED_TEMP)
... Test objective: The objective is to test that POST method initiates a rollback on a VNF lifecycle operation
... Pre-conditions: the "VNF LCM operation occurrence" resource is not in "FAILED_TEMP" state.
- ... Reference: Clause 5.4.15.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.15.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -41,7 +41,7 @@ POST Rollback operation task Not Found
... Test title: POST Rollback operation task Not Found
... Test objective: The objective is to test that the retry operation cannot be executed because the operation is not supported
... Pre-conditions:
- ... Reference: Clause 5.4.15.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.15.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -54,7 +54,7 @@ GET Rollback operation task - Method not implemented
... Test title: GET Rollback operation task - Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.15.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.15.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -66,7 +66,7 @@ PUT Rollback operation task - Method not implemented
... Test title: PUT Rollback operation task - Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.15.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.15.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -78,7 +78,7 @@ PATCH Rollback operation task - Method not implemented
... Test title: PATCH Rollback operation task - Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.15.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.15.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -90,7 +90,7 @@ DELETE Rollback operation task - Method not implemented
... Test title: DELETE Rollback operation task - Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.15.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.15.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFLifecycleManagement-API/ScaleVNFTask.robot b/SOL003/VNFLifecycleManagement-API/ScaleVNFTask.robot
index d549acbab6286913e08820e33171c82c5257e94b..8d0776e3991013d708b220b9659224b6e77fa2ac 100644
--- a/SOL003/VNFLifecycleManagement-API/ScaleVNFTask.robot
+++ b/SOL003/VNFLifecycleManagement-API/ScaleVNFTask.robot
@@ -13,7 +13,7 @@ POST Scale a vnfInstance
... Test title: POST Scale a vnfInstance
... Test objective: The objective is to scale a VNF instance
... Pre-conditions: none
- ... Reference: Clause 5.4.5.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.5.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -27,7 +27,7 @@ POST Scale a vnfInstance Conflict (Not-Instantiated)
... Test title: POST Scale a vnfInstance Conflict (Not-Instantiated)
... Test objective: The objective is to verify that the scale operation cannot be executed
... Pre-conditions: VNF instance resource is in NOT-INSTANTIATED state
- ... Reference: Clause 5.4.5.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.5.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -40,7 +40,7 @@ POST Scale a vnfInstance Not Found
... Test title: POST Scale a vnfInstance Not Found
... Test objective: The objective is to verify that the operation cannot be executed currently, because the VNF instance resource is not found.
... Pre-conditions: none
- ... Reference: Clause 5.4.5.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.5.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -53,7 +53,7 @@ GET Scale VNFInstance - Method not implemented
... Test title: GET Scale VNFInstance - Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -65,7 +65,7 @@ PUT Scale VNFInstance - Method not implemented
... Test title: PUT Scale VNFInstance - Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.5.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.5.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -77,7 +77,7 @@ PATCH Scale VNFInstance - Method not implemented
... Test title: PATCH Scale VNFInstance - Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.5.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.5.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -89,7 +89,7 @@ DELETE Scale VNFInstance - Method not implemented
... Test title: DELETE Scale VNFInstance - Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.5.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.5.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFLifecycleManagement-API/ScaleVNFToLevelTask.robot b/SOL003/VNFLifecycleManagement-API/ScaleVNFToLevelTask.robot
index b083243c863af7c906d2a5a23209e99a482b578b..7f2fb029923489514cd0ad7e0d6aa9af148fc725 100644
--- a/SOL003/VNFLifecycleManagement-API/ScaleVNFToLevelTask.robot
+++ b/SOL003/VNFLifecycleManagement-API/ScaleVNFToLevelTask.robot
@@ -12,7 +12,7 @@ POST Scale a vnfInstance to level - with InstantiationLevelId attribute
... Test title: POST Scale a vnfInstance to level
... Test objective: The objective is to scale a VNF instance to a target level.
... Pre-conditions: none
- ... Reference: Clause 5.4.6.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.6.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -26,7 +26,7 @@ POST Scale a vnfInstance to level Conflict (Not-Instantiated)
... Test title: POST Scale a vnfInstance to level Conflict (Not-Instantiated)
... Test objective: The objective is to verify that the scale operation cannot be executed because the resource is not instantiated
... Pre-conditions: VNF instance resource is in NOT-INSTANTIATED state
- ... Reference: Clause 5.4.6.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.6.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -39,7 +39,7 @@ Scale a vnfInstance Not Found
... Test title: Scale a vnfInstance Not Found
... Test objective: The objective is to verify that the operation cannot be executed , because the VNF instance resource cannot be found.
... Pre-conditions: VNF instance resource is in NOT-INSTANTIATED state
- ... Reference: Clause 5.4.6.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.6.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -52,7 +52,7 @@ GET Scale to level VNFInstance - Method not implemented
... Test title: GET Scale to level VNFInstance - Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -64,7 +64,7 @@ PUT Scale to level VNFInstance - Method not implemented
... Test title: PUT Scale to level VNFInstance - Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.6.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.6.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -76,7 +76,7 @@ PATCH Scale to level VNFInstance - Method not implemented
... Test title: PATCH Scale to level VNFInstance - Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.6.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.6.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -88,7 +88,7 @@ DELETE Scale to level VNFInstance - Method not implemented
... Test title: DELETE Scale to level VNFInstance - Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.6.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.6.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -100,7 +100,7 @@ POST Scale a vnfInstance to level - with scaleInfo attribute
... Test title: POST Scale a vnfInstance to level with scaleInfo attribute
... Test objective: The objective is to scale a VNF instance to a target level.
... Pre-conditions: none
- ... Reference: Clause 5.4.6.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.6.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFLifecycleManagement-API/ScaleVNFToLevelWorkflow.robot b/SOL003/VNFLifecycleManagement-API/ScaleVNFToLevelWorkflow.robot
index 636082f6080638cbd307a4083c1e0c4966df00ea..c515f53b24b0f0e675bf4c6797798e1f41341279 100644
--- a/SOL003/VNFLifecycleManagement-API/ScaleVNFToLevelWorkflow.robot
+++ b/SOL003/VNFLifecycleManagement-API/ScaleVNFToLevelWorkflow.robot
@@ -15,7 +15,7 @@ VNF Instance Scale To Level
... Test title: VNF Instance Scale To Level workflow
... Test objective: The objective is to test the workflow for the scale to level of a VNF instance
... Pre-conditions: VNF instance in INSTANTIATED state . NFVO is subscribed to VNF LCM Operation Occurrence notifications
- ... Reference: Clause 5.4.6 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.6 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: NFVO is able to receive notifications from VNFM. Scale operation is supported for the VNF (as capability in the VNFD)
... Post-Conditions: VNF instance still in INSTANTIATED state and VNF is scaled to the new level
diff --git a/SOL003/VNFLifecycleManagement-API/ScaleVNFWorkflow.robot b/SOL003/VNFLifecycleManagement-API/ScaleVNFWorkflow.robot
index 7068248f529475e25c398acf1b78d231ff939903..73897ccd91e2f009c90141c174eca97a5f9fd53c 100644
--- a/SOL003/VNFLifecycleManagement-API/ScaleVNFWorkflow.robot
+++ b/SOL003/VNFLifecycleManagement-API/ScaleVNFWorkflow.robot
@@ -15,7 +15,7 @@ VNF Instance Scale Out
... Test title: VNF Instance Scale Out workflow
... Test objective: The objective is to test the workflow for the scaling out a VNF instance
... Pre-conditions: VNF instance in INSTANTIATED state (Test ID 5.4.4.1). NFVO is subscribed to VNF LCM Operation Occurrence notifications (Test ID 5.4.20.1)
- ... Reference: Clause 5.4.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: NFVO is able to receive notifications from VNFM. Scale operation is supported for the VNF (as capability in the VNFD)
... Post-Conditions: VNF instance still in INSTANTIATED state and VNF is scaled out
diff --git a/SOL003/VNFLifecycleManagement-API/Subscriptions.robot b/SOL003/VNFLifecycleManagement-API/Subscriptions.robot
index a32dc7cce29c4bba7c80648244a2bc9924cf0f35..81fabaf040c4042f3449deabd869236b53746050 100644
--- a/SOL003/VNFLifecycleManagement-API/Subscriptions.robot
+++ b/SOL003/VNFLifecycleManagement-API/Subscriptions.robot
@@ -15,7 +15,7 @@ POST Create a new subscription
... Test title: POST Create a new subscription
... Test objective: The POST method creates a new subscription
... Pre-conditions: none
- ... Reference: Clause 5.4.18.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.18.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: in response header Location shall not be null
@@ -28,7 +28,7 @@ Create a new Subscription - DUPLICATION
... Test title: POST Create a new subscription - DUPLICATION
... Test objective: The objective is to test request to create a duplicate (same callbackurl and filter) subscription
... Pre-conditions: none
- ... Reference: Clause 5.4.18.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.18.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: duplication is supported by SUT
... Post-Conditions: in response header Location shall not be null
@@ -41,7 +41,7 @@ Create a new Subscription - NO-DUPLICATION
... Test title: POST Create a new subscription - NO-DUPLICATION
... Test objective: The objective is to test the request that does not create a duplicate (same callbackurl and filter) subscription
... Pre-conditions: none
- ... Reference: Clause 5.4.18.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.18.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: duplication is not supported by SUT
... Post-Conditions: in response header Location shall not be null
@@ -54,7 +54,7 @@ GET Subscriptions
... Test title: GET Subscriptions
... Test objective: The objective is Get the list of active subscriptions
... Pre-conditions: none
- ... Reference: Clause 5.4.18.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.18.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -67,7 +67,7 @@ GET Subscription - Filter
... Test title: GET Subscriptions - Filter
... Test objective: The objective is Get the list of active subscriptions using a filter
... Pre-conditions: none
- ... Reference: Clause 5.4.18.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.18.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -81,7 +81,7 @@ GET subscriptions - Bad Request Invalid attribute-based filtering parameters
... Test title: GET subscriptions - Bad Request Invalid attribute-based filtering parameters
... Test objective: The objective is Get the list of active subscriptions using an invalid filter
... Pre-conditions: none
- ... Reference: Clause 5.4.18.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.18.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -138,7 +138,7 @@ PUT subscriptions - Method not implemented
... Test title: PUT subscriptions - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.18.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.18.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -150,7 +150,7 @@ PATCH subscriptions - Method not implemented
... Test title: PATCH subscriptions - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.18.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.18.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -162,7 +162,7 @@ DELETE subscriptions - Method not implemented
... Test title: DELETE subscriptions - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.18.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.18.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -174,7 +174,7 @@ GET Subscriptions as a Paged Response
... Test title: GET Subscriptions as a Paged Response
... Test objective: The objective is Get the list of active subscriptions as a Paged Response.
... Pre-conditions: none
- ... Reference: Clause 5.4.18.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.18.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: The VNFM supports response paging for the subscriptions resources
... Post-Conditions: none
@@ -187,7 +187,7 @@ GET subscriptions - Bad Request Response too Big
... Test title: GET subscriptions - Bad Request Response too Big
... Test objective: The objective is to test that the retrieval of the list of active subscriptions fails because response is too big. The test also checks the JSON schema of the unsuccessful operation HTTP response.
... Pre-conditions: none
- ... Reference: Clause 5.4.18.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.18.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -195,10 +195,10 @@ GET subscriptions - Bad Request Response too Big
Check HTTP Response Status Code Is 400
Check HTTP Response Body Json Schema Is ProblemDetails
-POST Create a new Subscription - Unprocessable Entity
+POST Create a new Subscription - Unprocessable Content
[Documentation] Test ID: 7.3.1.17.16
- ... Test title: POST Create a new Subscription - Unprocessable Entity
- ... Test objective: The objective is to test that 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.
+ ... Test title: POST Create a new Subscription - Unprocessable Content
+ ... Test objective: The objective is to test that content type of the message content is supported and the message content of a request contains syntactically correct data but the data cannot be processed.
... re-conditions: none
... Reference: Clause 5.4.18.3.1 - ETSI GS NFV-SOL 003 [2] v3.3.1
... Config ID: Config_prod_VNFM
@@ -213,7 +213,7 @@ GET Subscriptions as a Paged Response with nextpage_opauque_marker parameter
... Test title: GET Subscriptions as a Paged Response with nextpage_opauque_marker parameter
... Test objective: The objective is to Get the list of active subscriptions as a Paged Response and retrieve the next page using the nextpage_opaque_marker parameter
... Pre-conditions: A request for retrieving subscriptions as a paged response has been successfully issued (Test ID 7.3.1.17.14)
- ... Reference: Clause 5.4.18.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.18.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: The VNFM supports response paging for the subscriptions resources
... Post-Conditions: none
diff --git a/SOL003/VNFLifecycleManagement-API/TerminateVNFTask.robot b/SOL003/VNFLifecycleManagement-API/TerminateVNFTask.robot
index 71d70c8254068f5b290c7ecd1bc4c465281ba8c3..b21a1301c688372fef386f39bf7667fa9a48b8e6 100644
--- a/SOL003/VNFLifecycleManagement-API/TerminateVNFTask.robot
+++ b/SOL003/VNFLifecycleManagement-API/TerminateVNFTask.robot
@@ -13,7 +13,7 @@ POST Terminate a vnfInstance
... Test title: POST Terminate a vnfInstance
... Test objective: The objective is to test that POST method terminate a VNF instance
... Pre-conditions: none
- ... Reference: Clause 5.4.8.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.8.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -27,7 +27,7 @@ POST Terminate a vnfInstance Conflict (Not-Instantiated)
... Test title: POST Terminate a vnfInstance Conflict (Not-Instantiated)
... Test objective: The objective is to test that the vnf Instance cannot be terminated
... Pre-conditions: VNF instance resource is in NOT-INSTANTIATED state
- ... Reference: Clause 5.4.8.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.8.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -40,7 +40,7 @@ GET Terminate VNFInstance - Method not implemented
... Test title: GET Terminate VNFInstance - Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.8.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.8.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -52,7 +52,7 @@ PUT Terminate VNFInstance - Method not implemented
... Test title: PUT Terminate VNFInstance - Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.8.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.8.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -64,7 +64,7 @@ PATCH Terminate VNFInstance - Method not implemented
... Test title: PATCH Terminate VNFInstance - Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.8.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.8.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -76,7 +76,7 @@ DELETE Terminate VNFInstance - Method not implemented
... Test title: DELETE Terminate VNFInstance - Method not implemented
... Test objective: The objective is to verify that the method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.8.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.8.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFLifecycleManagement-API/TerminateVNFWorkflow.robot b/SOL003/VNFLifecycleManagement-API/TerminateVNFWorkflow.robot
index eb6c4784bded10b9841573f0d3023de2d8788ffe..d458119a4e5f862aff96ad850b9cb6771af5a11d 100644
--- a/SOL003/VNFLifecycleManagement-API/TerminateVNFWorkflow.robot
+++ b/SOL003/VNFLifecycleManagement-API/TerminateVNFWorkflow.robot
@@ -15,7 +15,7 @@ Terminate a VNF Instance
... Test title: Terminate a VNF Instance
... Test objective: The objective is to terminate a VNF instance.
... Pre-conditions: VNF instance in INSTANTIATED state
- ... Reference: Clause 5.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: NFVO is able to receive notifications from VNFM.
... Post-Conditions: VNF instance in NOT_INSTANTIATED state
diff --git a/SOL003/VNFLifecycleManagement-API/VNFInstances.robot b/SOL003/VNFLifecycleManagement-API/VNFInstances.robot
index a49eb2caaf8a8d45e271a3068429d5e2e2722b5e..3bb82db575223596a7f7fd87e7ee43a933a3f613 100644
--- a/SOL003/VNFLifecycleManagement-API/VNFInstances.robot
+++ b/SOL003/VNFLifecycleManagement-API/VNFInstances.robot
@@ -13,7 +13,7 @@ POST Create a new vnfInstance
... Test title: POST Create a new vnfInstance
... Test objective: The objective is to create a new VNF instance resource
... Pre-conditions: none
- ... Reference: Clause 5.4.2.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.2.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: VNF instance created
@@ -26,7 +26,7 @@ GET information about multiple VNF instances
... Test title: GET information about multiple VNF instances
... Test objective: The objective is to query information about multiple VNF instances
... Pre-conditions: none
- ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -38,8 +38,8 @@ GET information about multiple VNF instances Bad Request Invalid attribute-based
[Documentation] Test ID: 7.3.1.1.3
... Test title: GET information about multiple VNF instances Bad Request Invalid attribute-based filtering parameters
... Test objective: The objective is to query information about multiple VNF instances with Invalid attribute-based filtering parameters
- ... Pre-conditions: A VNF is instantiated, a bad filter selector (filter selectors are listed in Table 5.4.2.3.2-1 - ETSI GS NFV-SOL 003 [1] v4.3.1).
- ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Pre-conditions: A VNF is instantiated, a bad filter selector (filter selectors are listed in Table 5.4.2.3.2-1 - ETSI GS NFV-SOL 003 [1] v4.4.1).
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -52,8 +52,8 @@ GET information about multiple VNF instances Bad Request Invalid attribute selec
[Documentation] Test ID: 7.3.1.1.4
... Test title: GET information about multiple VNF instances Bad Request Invalid attribute selector
... Test objective: The objective is to query information about multiple VNF instances with Invalid attribute selector
- ... Pre-conditions: A VNF is instantiated, a bad attribute selector (attribute selectors are listed in Table 5.4.2.3.2-1 - ETSI GS NFV-SOL 003 [1] v4.3.1).
- ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Pre-conditions: A VNF is instantiated, a bad attribute selector (attribute selectors are listed in Table 5.4.2.3.2-1 - ETSI GS NFV-SOL 003 [1] v4.4.1).
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -66,7 +66,7 @@ GET information about multiple VNF instances with "all_fields" attribute selecto
... Test title: GET information about multiple VNF instances with "all_fields" attribute selector
... Test objective: The objective is to query information about multiple VNF instances
... Pre-conditions: none
- ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -79,7 +79,7 @@ GET information about multiple VNF instances with "exclude_default" attribute se
... Test title: GET information about multiple VNF instances with "exclude_default" attribute selector
... Test objective: The objective is to query information about multiple VNF instances
... Pre-conditions: none
- ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -92,7 +92,7 @@ GET information about multiple VNF instances with "fields" attribute selector
... Test title: GET information about multiple VNF instances with "fields" attribute selector
... Test objective: The objective is to query information about multiple VNF instances
... Pre-conditions: none
- ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -105,7 +105,7 @@ GET information about multiple VNF instances with "exclude_fields" attribute sel
... Test title: GET information about multiple VNF instances with "exclude_fields" attribute selector
... Test objective: The objective is to query information about multiple VNF instances
... Pre-conditions: none
- ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -118,7 +118,7 @@ PUT multiples VNFInstances - Method not implemented
... Test title: PUT multiples VNFInstances - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.2.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.2.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -130,7 +130,7 @@ PATCH multiples VNFInstances - Method not implemented
... Test title: PATCH multiples VNFInstances - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.2.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.2.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -142,7 +142,7 @@ DELETE VNFInstances - Method not implemented
... Test title: DELETE multiples VNFInstances - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.2.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.2.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -154,7 +154,7 @@ GET information about multiple VNF instances to get Paged Response
... Test title: GET information about multiple VNF instances to get Paged Response
... Test objective: The objective is to query information about multiple VNF instances to get Paged Response.
... Pre-conditions: none
- ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: The VNFM supports response paging for the subscriptions resources
... Post-Conditions: none
@@ -167,7 +167,7 @@ GET information about multiple VNF instances as a Paged Response with nextpage_o
... Test title: GET information about multiple VNF instances as a Paged Response with nextpage_opauque_marker parameter
... Test objective: The objective is to query information about multiple VNF instances as a Paged Response and retrieve the next page using the nextpage_opaque_marker parameter
... Pre-conditions: A request for retrieving multiple VNF instances as a paged response has been successfully issued (Test ID 7.3.1.1.12)
- ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: The VNFM supports response paging for the VNF instance resources
... Post-Conditions: none
@@ -178,8 +178,8 @@ GET information about multiple VNF instances - Bad Request Response too Big
[Documentation] Test ID: 7.3.1.1.13
... Test title: GET information about multiple VNF instances - Bad Request Response too Big
... Test objective: The objective is to query information about multiple VNF instances fails because response is too big. The test also checks the JSON schema of the unsuccessful operation HTTP response.
- ... Pre-conditions: A VNF is instantiated, a bad attribute selector (attribute selectors are listed in Table 5.4.2.3.2-1 - ETSI GS NFV-SOL 003 [1] v4.3.1).
- ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Pre-conditions: A VNF is instantiated, a bad attribute selector (attribute selectors are listed in Table 5.4.2.3.2-1 - ETSI GS NFV-SOL 003 [1] v4.4.1).
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -192,7 +192,7 @@ GET information about multiple VNF instances with "exclude_default" and "fields"
... Test title: GET information about multiple VNF instances with "exclude_default" and "fields" attribute selector
... Test objective: The objective is to query information about multiple VNF instances
... Pre-conditions: none
- ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -200,12 +200,12 @@ GET information about multiple VNF instances with "exclude_default" and "fields"
Check HTTP Response Status Code Is 200
Check HTTP Response Body Json Schema Is vnfInstances
-POST Create a new vnfInstance - Unprocessible Entity
+POST Create a new vnfInstance - Unprocessable Content
[Documentation] Test ID: 7.3.1.1.15
- ... Test title: POST Create a new vnfInstance - Unprocessible Entity
+ ... Test title: POST Create a new vnfInstance - Unprocessable Content
... Test objective: The objective is to test that correct error code is returned when VNF package referenced by the "vnfdId" attribute in the "CreateVnfRequest" structure is not in the "ENABLED" state or does not exist.
... Pre-conditions: none
- ... Reference: Clause 5.4.2.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.2.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: The VNF package referenced by the "vnfdId" attribute in the "CreateVnfRequest" structure is not in the "ENABLED" state or does not exist.
... Post-Conditions: none
@@ -218,7 +218,7 @@ GET information about multiple VNF instances using Filter
... Test title: GET information about multiple VNF instances using Filter
... Test objective: The objective is to query information about multiple VNF instances using filter
... Pre-conditions: none
- ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFLifecycleManagement-API/VNFSnapshots.robot b/SOL003/VNFLifecycleManagement-API/VNFSnapshots.robot
index 2fd0ddad8af1d2f66fcf1d7a1ec7c69b82576ae3..031f8b86f2c7e5aa9984185b006b6aad3bac2469 100644
--- a/SOL003/VNFLifecycleManagement-API/VNFSnapshots.robot
+++ b/SOL003/VNFLifecycleManagement-API/VNFSnapshots.robot
@@ -7,7 +7,7 @@ POST Create a new VNF Snapshot
... Test title: POST Create a new VNF Snapshot
... Test objective: The objective is to create a new VNF snapshot
... Pre-conditions: none
- ... Reference: Clause 5.4.23.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.23.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: VNF snapshot is created
@@ -21,7 +21,7 @@ GET information about multiple VNF Snapshots
... Test title: GET information about multiple VNF Snapshots
... Test objective: The objective is to get information about multiples VNF snapshots
... Pre-conditions: none
- ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -34,7 +34,7 @@ GET information about multiple VNF Snapshots Bad Request Invalid attribute-based
... Test title: GET information about multiple VNF Snapshots Bad Request Invalid attribute-based filtering parameters
... Test objective: The objective is to get information about multiples VNF Snapshots with Invalid attribute-based filtering parameters
... Pre-conditions: none
- ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -47,7 +47,7 @@ GET information about multiple VNF Snapshots Bad Request Invalid attribute selec
... Test title: GET information about multiple VNF Snapshots Bad Request Invalid attribute selector
... Test objective: The objective is to get information about multiples VNF Snapshots with Invalid attribute-based filtering parameters
... Pre-conditions: none
- ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -60,7 +60,7 @@ GET information about multiple VNF Snapshots with "all_fields" attribute selecto
... Test title: GET information about multiple VNF Snapshots with "all_fields" attribute selector
... Test objective: The objective is to query information about multiple VNF Snapshots
... Pre-conditions: none
- ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -73,7 +73,7 @@ GET information about multiple VNF Snapshots with "exclude_default" attribute se
... Test title: GET information about multiple VNF Snapshots with "exclude_default" attribute selector
... Test objective: The objective is to query information about multiple VNF Snapshots
... Pre-conditions: none
- ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -86,7 +86,7 @@ GET information about multiple VNF Snapshots with "fields" attribute selector
... Test title: GET information about multiple VNF Snapshots with "fields" attribute selector
... Test objective: The objective is to query information about multiple VNF Snapshots
... Pre-conditions: none
- ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -99,7 +99,7 @@ GET information about multiple VNF Snapshots with "exclude_default" and "fields"
... Test title: GET information about multiple VNF Snapshots with "exclude_default" and "fields" attribute selector
... Test objective: The objective is to query information about multiple VNF Snapshots
... Pre-conditions: none
- ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -112,7 +112,7 @@ GET information about multiple VNF Snapshots with "exclude_fields" attribute sel
... Test title: GET information about multiple VNF Snapshots with "exclude_fields" attribute selector
... Test objective: The objective is to query information about multiple VNF Snapshots
... Pre-conditions: none
- ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -125,7 +125,7 @@ GET VNF Snapshots - Bad Request Response too Big
... Test title: GET VNF Snapshots - Bad Request Response too Big
... Test objective: The objective is test that the retrieval of existing VNF Snapshots list fails because response is too big, and perform the JSON schema validation of the failed operation HTTP response.
... Pre-conditions: none
- ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: VNFM does not support paged response.
... Post-Conditions: none
@@ -138,7 +138,7 @@ GET VNF Snapshots as Paged Response
... Test title: GET VNF Snapshots as Paged Response
... Test objective: The objective is to test that GET method retrieves the list of existing VNF Snapshots as paged response.
... Pre-conditions: none
- ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: VNFM supports paged response.
... Post-Conditions: none
@@ -151,7 +151,7 @@ PUT VNF Snapshots - Method not implemented
... Test title: PUT VNF Snapshots - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.23.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.23.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -163,7 +163,7 @@ PATCH VNF Snapshots - Method not implemented
... Test title: PATCH VNF Snapshots - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.23.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.23.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -175,7 +175,7 @@ DELETE VNF Snapshots - Method not implemented
... Test title: DELETE VNF Snapshots - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.23.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.23.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: VNF instance not deleted
@@ -187,7 +187,7 @@ GET information about multiple VNF Snapshots using Filter
... Test title: GET information about multiple VNF Snapshots using Filter
... Test objective: The objective is to get information about multiples VNF snapshots using filter
... Pre-conditions: none
- ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFLifecycleManagement-API/VNFStateSnapshot.robot b/SOL003/VNFLifecycleManagement-API/VNFStateSnapshot.robot
index 18e7ebaa62b99a2e44176af1202a91e0e6c36cdf..670775dae97c9bc9c58208800d46548b9f31db74 100644
--- a/SOL003/VNFLifecycleManagement-API/VNFStateSnapshot.robot
+++ b/SOL003/VNFLifecycleManagement-API/VNFStateSnapshot.robot
@@ -7,7 +7,7 @@ POST VNF State Snapshot - Method not implemented
... Test title: POST VNF State Snapshot - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.25.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.25.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -19,7 +19,7 @@ GET VNF State Snapshot - Complete File
... Test title: GET Information about an individual VNF State Snapshot - Complete File
... Test objective: The objective is to fetch the whole content of a VNF State Snapshot using GET method.
... Pre-conditions: none
- ... Reference: Clause 5.4.25.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.25.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -32,7 +32,7 @@ GET VNF State Snapshot - Partial Content
... Test title: GET VNF State Snapshot - Partial Content
... Test objective: The objective is to fetch partial content of a VNF State Snapshot by sending a range request using GET method.
... Pre-conditions: none
- ... Reference: Clause 5.4.25.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.25.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: VNFM supports range requests
... Post-Conditions: none
@@ -46,7 +46,7 @@ GET VNF State Snapshot - Range Request Not Supported
... Test title: GET VNF State Snapshot - Range Request Not Supported
... Test objective: The objective is to test that the whole content of a VNF State Snapshot is delivered even with a range request when VNFM does not support range requests.
... Pre-conditions: none
- ... Reference: Clause 5.4.25.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.25.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: VNFM does not support range requests
... Post-Conditions: none
@@ -60,7 +60,7 @@ GET VNF State Snapshot - Range Not Satisfiable
... Test title: GET VNF State Snapshot - Range Not Satisfiable
... Test objective: The objective is to test that an error is returned when the byte range passed in the "Range" header does not match any available byte range in the VNF State Snapshot package file.
... Pre-conditions: none
- ... Reference: Clause 5.4.25.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.25.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: VNFM supports range requests
... Post-Conditions: none
@@ -72,7 +72,7 @@ GET VNF State Snapshot - Conflict
... Test title: GET VNF State Snapshot - Conflict
... Test objective: The objective is to test that an error is returned when there is a conflict with the state of the VNF snapshot resource.
... Pre-conditions: none
- ... Reference: Clause 5.4.25.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.25.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: Typically, this is due to the fact that the VNF snapshot creation process is not completed.
... Post-Conditions: none
@@ -84,7 +84,7 @@ PUT VNF State Snapshot - Method not implemented
... Test title: PUT VNF State Snapshot - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.25.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.25.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: VNF State Snapshot Package not modified
@@ -96,7 +96,7 @@ PATCH VNF State Snapshot - Method Not implemented
... Test title: PATCH VNF State Snapshot
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.25.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.25.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -108,7 +108,7 @@ DELETE VNF State Snapshot - Method Not implemented
... Test title: DELETE VNF State Snapshot - Method Not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.25.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.25.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFLifecycleManagement-API/VnfLcmOperationOccurences.robot b/SOL003/VNFLifecycleManagement-API/VnfLcmOperationOccurences.robot
index fbf69eecac88d1c043b6117db76c54cfd6d823f4..df021760f506fef4b97d79eb43d69a0e85b48824 100644
--- a/SOL003/VNFLifecycleManagement-API/VnfLcmOperationOccurences.robot
+++ b/SOL003/VNFLifecycleManagement-API/VnfLcmOperationOccurences.robot
@@ -11,7 +11,7 @@ POST VNF LCM Operation occurrences - Method not implemented
... Test title: POST VNF LCM Operation occurrences - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.12.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.12.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -23,7 +23,7 @@ GET status information about multiple VNF LCM Operation OCC
... Test title: GET status information about multiple VNF LCM Operation OCC
... Test objective: The objective is to test that GET method retrieve Query status information about multiple VNF lifecycle management operation occurrences.
... Pre-conditions: none
- ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -36,7 +36,7 @@ GET status information about multiple VNF LCM Operation OCC Bad Request Invalid
... Test title: GET status information about multiple VNF LCM Operation OCC Bad Request Invalid attribute-based filtering parameters
... Test objective: The objective is to test that GET method fail retrieving status information about multiple VNF lifecycle management operation occurrences because attribute is invalid.
... Pre-conditions: none
- ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -49,7 +49,7 @@ GET status information about multiple VNF LCM Operation OCC Bad Request Invalid
... Test title: GET status information about multiple VNF LCM Operation OCC Bad Request Invalid attribute selector
... Test objective: The objective is to test that GET method fail retrieving status information about multiple VNF lifecycle management operation occurrences because attribute is invalid.
... Pre-conditions: none
- ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -62,7 +62,7 @@ GET status information about multiple VNF LCM Operation OCC with "all_fields"
... Test title: GET status information about multiple VNF LCM Operation OCC with "all_fields"
... Test objective: The objective is to test that GET method retrieve Query status information about multiple VNF lifecycle management operation occurrences.
... Pre-conditions: none
- ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -75,7 +75,7 @@ GET status information about multiple VNF LCM Operation OCC with "exlude_default
... Test title: GET status information about multiple VNF LCM Operation OCC with "exclude_default"
... Test objective: The objective is to test that GET method retrieve Query status information about multiple VNF lifecycle management operation occurrences.
... Pre-conditions: none
- ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -88,7 +88,7 @@ GET status information about multiple VNF LCM Operation OCC with "fields"
... Test title: GET status information about multiple VNF LCM Operation OCC with "fields"
... Test objective: The objective is to test that GET method retrieve Query status information about multiple VNF lifecycle management operation occurrences.
... Pre-conditions: none
- ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -101,7 +101,7 @@ GET status information about multiple VNF LCM Operation OCC with "exclude_fields
... Test title: GET status information about multiple VNF LCM Operation OCC with "exclude_fields"
... Test objective: The objective is to test that GET method retrieve Query status information about multiple VNF lifecycle management operation occurrences.
... Pre-conditions: none
- ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -114,7 +114,7 @@ PUT status information about multiple VNF LCM Operation OCC - Method not impleme
... Test title: PUT status information about multiple VNF LCM Operation OCC - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.12.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.12.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -126,7 +126,7 @@ PATCH status information about multiple VNF LCM Operation OCC - Method not imple
... Test title: PATCH status information about multiple VNF LCM Operation OCC - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.12.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.12.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -138,7 +138,7 @@ DELETE status information about multiple VNF LCM Operation OCC - Method not impl
... Test title: DELETE status information about multiple VNF LCM Operation OCC - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 5.4.12.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.12.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -150,7 +150,7 @@ GET status information about multiple VNF LCM Operation OCC to get Paged Respons
... Test title: GET status information about multiple VNF LCM Operation OCC to get Paged Response
... Test objective: The objective is to test that GET method retrieve Query status information about multiple VNF lifecycle management operation occurrences to get a Paged Response.
... Pre-conditions: none
- ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: The VNFM supports response paging for the VNF lifecycle management operation occurrences resources
... Post-Conditions: none
@@ -163,7 +163,7 @@ GET information about multiple VNF LCM Operation OCC as a Paged Response with ne
... Test title: GET information about multiple VNF LCM Operation OCC as a Paged Response with nextpage_opauque_marker parameter
... Test objective: The objective is to query information about multiple VNF lifecycle management operation occurrences as a Paged Response and retrieve the next page using the nextpage_opaque_marker parameter
... Pre-conditions: A request for retrieving multiple VNF lifecycle management operation occurrences as a paged response has been successfully issued (Test ID 7.3.1.11.12)
- ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: The VNFM supports response paging for the VNF lifecycle management operation occurrences resources
... Post-Conditions: none
@@ -175,7 +175,7 @@ GET status information about multiple VNF LCM Operation OCC - Bad Request Respon
... Test title: GET status information about multiple VNF LCM Operation OCC - Bad Request Response too Big
... Test objective: The objective is to test that GET method fail retrieving status information about multiple VNF lifecycle management operation occurrences because response is too big. The test also checks the JSON schema of the unsuccessful operation HTTP response.
... Pre-conditions: none
- ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -188,7 +188,7 @@ GET status information about multiple VNF LCM Operation OCC with "exclude_defaul
... Test title: GET status information about multiple VNF LCM Operation OCC with "exclude_default" and "fields"
... Test objective: The objective is to test that GET method retrieve Query status information about multiple VNF lifecycle management operation occurrences.
... Pre-conditions: none
- ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFLifecycleManagement-API/schemas/VnfLcmOpOcc.schema.json b/SOL003/VNFLifecycleManagement-API/schemas/VnfLcmOpOcc.schema.json
index 3a3c6a866b53c3f7239cd52d53a07aea529cddd2..60ac77dbb52541ec7287536097e9566b0e0446fa 100644
--- a/SOL003/VNFLifecycleManagement-API/schemas/VnfLcmOpOcc.schema.json
+++ b/SOL003/VNFLifecycleManagement-API/schemas/VnfLcmOpOcc.schema.json
@@ -535,7 +535,7 @@
"description": "If present, this attribute signals modifications the \"vimConnectionInfo\" attribute array in \"VnfInstance\".\n",
"type": "object",
"additionalProperties": {
- "description": "This type represents parameters to connect to a VIM, a CISM, a CIR or a MCIOP repository for managing the resources of a VNF instance.\nThis structure is used to convey VIM-related, CISM-related, CIR-related, or MCIOP-repository-related parameters over the Or-Vnfm interface. Additional parameters for a VIM, a CISM, a CIR or a MCIOP repository may be configured into the VNFM by means outside the scope of the present document and bound to the identifier of that VIM.\n* NOTE 1:\tIf applicable, this attribute also provides information about the resourceGroupIds\n that are accessible using a particular set of credentials. See definition of\n \"resourceGroupId\" in clause 9.5.3.3.\n* NOTE 2:\tOnce the connectivity between VNFM and VIM, CISM, CIR or MCIOP repository is provided\n through a secure connection over HTTP Secure (HTTP over SSL/TLS), and the connection might also be\n established through a VPN (for example TLS-based VPN tunnelling) for site-to-site connection, the\n \"accessInfo\" JSON data structure, and the sensitive data related information (\"username\"/\"password\" as\n required properties for authentication purpose), will be transmitted as plain text through a TLS tunnel\n without additional encoding/encryption before transmitting it, making the sensitive data visible to the\n endpoint. The base64 encoded certificates are only used by the VNFM to verify the authenticity of the\n interface endpoint of the VIM, CISM, CIR or MCIOP repository.\n",
+ "description": "This type represents parameters to connect to a VIM, a CISM, a CIR or a MCIOP repository for managing the resources of a VNF instance.\nThis structure is used to convey VIM-related, CISM-related, CIR-related, or MCIOP-repository-related parameters over the Or-Vnfm interface. Additional parameters for a VIM, a CISM, a CIR or a MCIOP repository may be configured into the VNFM by means outside the scope of the present document and bound to the identifier of that VIM.\n* NOTE 1:\tIf applicable, this attribute also provides information about the resourceGroupIds\n that are accessible using a particular set of credentials. See definition of\n \"resourceGroupId\" in clause 9.5.3.3.\n* NOTE 2:\tOnce the connectivity between VNFM and VIM, CISM, CIR or MCIOP repository is provided\n through a secure connection over HTTP Secure (HTTP over SSL/TLS), and the connection might also be\n established through a VPN (for example TLS-based VPN tunnelling) for site-to-site connection, the\n \"accessInfo\" JSON data structure, and the sensitive data related information (\"username\"/\"password\" as\n required properties for authentication purpose), will be transmitted as plain text through a TLS tunnel\n without additional encoding/encryption before transmitting it, making the sensitive data visible to the\n endpoint. The base64 encoded certificates are only used by the VNFM to verify the authenticity of the\n interface endpoint of the VIM, CISM, CIR or MCIOP repository.\n \n* NOTE 3:\t ETSI GS NFV-SOL 009 [i.18] specifies the means to configure into the VNFM applicable VIM connection information via the \"NFV-MANO Configuration and Information Management\" interface. \n* NOTE 4:\t Due to the possibility of configuring such information into the VNFM out-of-band, by means outside the scope of the present document, as well as in-band, by means specified in the present document, care should be taken to avoid unintended conflicts in the VNFM when managing such information.\n",
"type": "object",
"required": ["vimType"],
"properties": {
@@ -909,6 +909,10 @@
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.\n",
+ "type": "string"
}
}
}
@@ -1040,7 +1044,7 @@
"description": "If present, this attribute signals the changes to VIM connection info that were passed in the related \"ChangeCurrentVnfPkgRequest\" structure. The provisions for sensitive information defined in clause 4.4.1.6 apply.\n",
"type": "object",
"additionalProperties": {
- "description": "This type represents parameters to connect to a VIM, a CISM, a CIR or a MCIOP repository for managing the resources of a VNF instance.\nThis structure is used to convey VIM-related, CISM-related, CIR-related, or MCIOP-repository-related parameters over the Or-Vnfm interface. Additional parameters for a VIM, a CISM, a CIR or a MCIOP repository may be configured into the VNFM by means outside the scope of the present document and bound to the identifier of that VIM.\n* NOTE 1:\tIf applicable, this attribute also provides information about the resourceGroupIds\n that are accessible using a particular set of credentials. See definition of\n \"resourceGroupId\" in clause 9.5.3.3.\n* NOTE 2:\tOnce the connectivity between VNFM and VIM, CISM, CIR or MCIOP repository is provided\n through a secure connection over HTTP Secure (HTTP over SSL/TLS), and the connection might also be\n established through a VPN (for example TLS-based VPN tunnelling) for site-to-site connection, the\n \"accessInfo\" JSON data structure, and the sensitive data related information (\"username\"/\"password\" as\n required properties for authentication purpose), will be transmitted as plain text through a TLS tunnel\n without additional encoding/encryption before transmitting it, making the sensitive data visible to the\n endpoint. The base64 encoded certificates are only used by the VNFM to verify the authenticity of the\n interface endpoint of the VIM, CISM, CIR or MCIOP repository.\n",
+ "description": "This type represents parameters to connect to a VIM, a CISM, a CIR or a MCIOP repository for managing the resources of a VNF instance.\nThis structure is used to convey VIM-related, CISM-related, CIR-related, or MCIOP-repository-related parameters over the Or-Vnfm interface. Additional parameters for a VIM, a CISM, a CIR or a MCIOP repository may be configured into the VNFM by means outside the scope of the present document and bound to the identifier of that VIM.\n* NOTE 1:\tIf applicable, this attribute also provides information about the resourceGroupIds\n that are accessible using a particular set of credentials. See definition of\n \"resourceGroupId\" in clause 9.5.3.3.\n* NOTE 2:\tOnce the connectivity between VNFM and VIM, CISM, CIR or MCIOP repository is provided\n through a secure connection over HTTP Secure (HTTP over SSL/TLS), and the connection might also be\n established through a VPN (for example TLS-based VPN tunnelling) for site-to-site connection, the\n \"accessInfo\" JSON data structure, and the sensitive data related information (\"username\"/\"password\" as\n required properties for authentication purpose), will be transmitted as plain text through a TLS tunnel\n without additional encoding/encryption before transmitting it, making the sensitive data visible to the\n endpoint. The base64 encoded certificates are only used by the VNFM to verify the authenticity of the\n interface endpoint of the VIM, CISM, CIR or MCIOP repository.\n \n* NOTE 3:\t ETSI GS NFV-SOL 009 [i.18] specifies the means to configure into the VNFM applicable VIM connection information via the \"NFV-MANO Configuration and Information Management\" interface. \n* NOTE 4:\t Due to the possibility of configuring such information into the VNFM out-of-band, by means outside the scope of the present document, as well as in-band, by means specified in the present document, care should be taken to avoid unintended conflicts in the VNFM when managing such information.\n",
"type": "object",
"required": ["vimType"],
"properties": {
diff --git a/SOL003/VNFLifecycleManagement-API/schemas/VnfLcmOpOccs.schema.json b/SOL003/VNFLifecycleManagement-API/schemas/VnfLcmOpOccs.schema.json
index 72866792b6ff21e725b212f808b025d2b4571eab..17727c4705e082163d3e32a8b18150e52ba7ff1e 100644
--- a/SOL003/VNFLifecycleManagement-API/schemas/VnfLcmOpOccs.schema.json
+++ b/SOL003/VNFLifecycleManagement-API/schemas/VnfLcmOpOccs.schema.json
@@ -537,7 +537,7 @@
"description": "If present, this attribute signals modifications the \"vimConnectionInfo\" attribute array in \"VnfInstance\".\n",
"type": "object",
"additionalProperties": {
- "description": "This type represents parameters to connect to a VIM, a CISM, a CIR or a MCIOP repository for managing the resources of a VNF instance.\nThis structure is used to convey VIM-related, CISM-related, CIR-related, or MCIOP-repository-related parameters over the Or-Vnfm interface. Additional parameters for a VIM, a CISM, a CIR or a MCIOP repository may be configured into the VNFM by means outside the scope of the present document and bound to the identifier of that VIM.\n* NOTE 1:\tIf applicable, this attribute also provides information about the resourceGroupIds\n that are accessible using a particular set of credentials. See definition of\n \"resourceGroupId\" in clause 9.5.3.3.\n* NOTE 2:\tOnce the connectivity between VNFM and VIM, CISM, CIR or MCIOP repository is provided\n through a secure connection over HTTP Secure (HTTP over SSL/TLS), and the connection might also be\n established through a VPN (for example TLS-based VPN tunnelling) for site-to-site connection, the\n \"accessInfo\" JSON data structure, and the sensitive data related information (\"username\"/\"password\" as\n required properties for authentication purpose), will be transmitted as plain text through a TLS tunnel\n without additional encoding/encryption before transmitting it, making the sensitive data visible to the\n endpoint. The base64 encoded certificates are only used by the VNFM to verify the authenticity of the\n interface endpoint of the VIM, CISM, CIR or MCIOP repository.\n",
+ "description": "This type represents parameters to connect to a VIM, a CISM, a CIR or a MCIOP repository for managing the resources of a VNF instance.\nThis structure is used to convey VIM-related, CISM-related, CIR-related, or MCIOP-repository-related parameters over the Or-Vnfm interface. Additional parameters for a VIM, a CISM, a CIR or a MCIOP repository may be configured into the VNFM by means outside the scope of the present document and bound to the identifier of that VIM.\n* NOTE 1:\tIf applicable, this attribute also provides information about the resourceGroupIds\n that are accessible using a particular set of credentials. See definition of\n \"resourceGroupId\" in clause 9.5.3.3.\n* NOTE 2:\tOnce the connectivity between VNFM and VIM, CISM, CIR or MCIOP repository is provided\n through a secure connection over HTTP Secure (HTTP over SSL/TLS), and the connection might also be\n established through a VPN (for example TLS-based VPN tunnelling) for site-to-site connection, the\n \"accessInfo\" JSON data structure, and the sensitive data related information (\"username\"/\"password\" as\n required properties for authentication purpose), will be transmitted as plain text through a TLS tunnel\n without additional encoding/encryption before transmitting it, making the sensitive data visible to the\n endpoint. The base64 encoded certificates are only used by the VNFM to verify the authenticity of the\n interface endpoint of the VIM, CISM, CIR or MCIOP repository.\n \n* NOTE 3:\t ETSI GS NFV-SOL 009 [i.18] specifies the means to configure into the VNFM applicable VIM connection information via the \"NFV-MANO Configuration and Information Management\" interface. \n* NOTE 4:\t Due to the possibility of configuring such information into the VNFM out-of-band, by means outside the scope of the present document, as well as in-band, by means specified in the present document, care should be taken to avoid unintended conflicts in the VNFM when managing such information.\n",
"type": "object",
"required": ["vimType"],
"properties": {
@@ -914,6 +914,10 @@
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.\n",
+ "type": "string"
}
}
}
@@ -1045,7 +1049,7 @@
"description": "If present, this attribute signals the changes to VIM connection info that were passed in the related \"ChangeCurrentVnfPkgRequest\" structure. The provisions for sensitive information defined in clause 4.4.1.6 apply.\n",
"type": "object",
"additionalProperties": {
- "description": "This type represents parameters to connect to a VIM, a CISM, a CIR or a MCIOP repository for managing the resources of a VNF instance.\nThis structure is used to convey VIM-related, CISM-related, CIR-related, or MCIOP-repository-related parameters over the Or-Vnfm interface. Additional parameters for a VIM, a CISM, a CIR or a MCIOP repository may be configured into the VNFM by means outside the scope of the present document and bound to the identifier of that VIM.\n* NOTE 1:\tIf applicable, this attribute also provides information about the resourceGroupIds\n that are accessible using a particular set of credentials. See definition of\n \"resourceGroupId\" in clause 9.5.3.3.\n* NOTE 2:\tOnce the connectivity between VNFM and VIM, CISM, CIR or MCIOP repository is provided\n through a secure connection over HTTP Secure (HTTP over SSL/TLS), and the connection might also be\n established through a VPN (for example TLS-based VPN tunnelling) for site-to-site connection, the\n \"accessInfo\" JSON data structure, and the sensitive data related information (\"username\"/\"password\" as\n required properties for authentication purpose), will be transmitted as plain text through a TLS tunnel\n without additional encoding/encryption before transmitting it, making the sensitive data visible to the\n endpoint. The base64 encoded certificates are only used by the VNFM to verify the authenticity of the\n interface endpoint of the VIM, CISM, CIR or MCIOP repository.\n",
+ "description": "This type represents parameters to connect to a VIM, a CISM, a CIR or a MCIOP repository for managing the resources of a VNF instance.\nThis structure is used to convey VIM-related, CISM-related, CIR-related, or MCIOP-repository-related parameters over the Or-Vnfm interface. Additional parameters for a VIM, a CISM, a CIR or a MCIOP repository may be configured into the VNFM by means outside the scope of the present document and bound to the identifier of that VIM.\n* NOTE 1:\tIf applicable, this attribute also provides information about the resourceGroupIds\n that are accessible using a particular set of credentials. See definition of\n \"resourceGroupId\" in clause 9.5.3.3.\n* NOTE 2:\tOnce the connectivity between VNFM and VIM, CISM, CIR or MCIOP repository is provided\n through a secure connection over HTTP Secure (HTTP over SSL/TLS), and the connection might also be\n established through a VPN (for example TLS-based VPN tunnelling) for site-to-site connection, the\n \"accessInfo\" JSON data structure, and the sensitive data related information (\"username\"/\"password\" as\n required properties for authentication purpose), will be transmitted as plain text through a TLS tunnel\n without additional encoding/encryption before transmitting it, making the sensitive data visible to the\n endpoint. The base64 encoded certificates are only used by the VNFM to verify the authenticity of the\n interface endpoint of the VIM, CISM, CIR or MCIOP repository.\n \n* NOTE 3:\t ETSI GS NFV-SOL 009 [i.18] specifies the means to configure into the VNFM applicable VIM connection information via the \"NFV-MANO Configuration and Information Management\" interface. \n* NOTE 4:\t Due to the possibility of configuring such information into the VNFM out-of-band, by means outside the scope of the present document, as well as in-band, by means specified in the present document, care should be taken to avoid unintended conflicts in the VNFM when managing such information.\n",
"type": "object",
"required": ["vimType"],
"properties": {
diff --git a/SOL003/VNFLifecycleManagement-API/schemas/VnfLcmOperationOccurrenceNotification.schema.json b/SOL003/VNFLifecycleManagement-API/schemas/VnfLcmOperationOccurrenceNotification.schema.json
index 8867491a38428167a017680a0ac347836f09887c..81e024130b069ba8fffaa8ee32fd5b8c93bc6406 100644
--- a/SOL003/VNFLifecycleManagement-API/schemas/VnfLcmOperationOccurrenceNotification.schema.json
+++ b/SOL003/VNFLifecycleManagement-API/schemas/VnfLcmOperationOccurrenceNotification.schema.json
@@ -491,7 +491,7 @@
"description": "If present, this attribute signals modifications the \"vimConnectionInfo\" attribute array in \"VnfInstance\".\n",
"type": "object",
"additionalProperties": {
- "description": "This type represents parameters to connect to a VIM, a CISM, a CIR or a MCIOP repository for managing the resources of a VNF instance.\nThis structure is used to convey VIM-related, CISM-related, CIR-related, or MCIOP-repository-related parameters over the Or-Vnfm interface. Additional parameters for a VIM, a CISM, a CIR or a MCIOP repository may be configured into the VNFM by means outside the scope of the present document and bound to the identifier of that VIM.\n* NOTE 1:\tIf applicable, this attribute also provides information about the resourceGroupIds\n that are accessible using a particular set of credentials. See definition of\n \"resourceGroupId\" in clause 9.5.3.3.\n* NOTE 2:\tOnce the connectivity between VNFM and VIM, CISM, CIR or MCIOP repository is provided\n through a secure connection over HTTP Secure (HTTP over SSL/TLS), and the connection might also be\n established through a VPN (for example TLS-based VPN tunnelling) for site-to-site connection, the\n \"accessInfo\" JSON data structure, and the sensitive data related information (\"username\"/\"password\" as\n required properties for authentication purpose), will be transmitted as plain text through a TLS tunnel\n without additional encoding/encryption before transmitting it, making the sensitive data visible to the\n endpoint. The base64 encoded certificates are only used by the VNFM to verify the authenticity of the\n interface endpoint of the VIM, CISM, CIR or MCIOP repository.\n",
+ "description": "This type represents parameters to connect to a VIM, a CISM, a CIR or a MCIOP repository for managing the resources of a VNF instance.\nThis structure is used to convey VIM-related, CISM-related, CIR-related, or MCIOP-repository-related parameters over the Or-Vnfm interface. Additional parameters for a VIM, a CISM, a CIR or a MCIOP repository may be configured into the VNFM by means outside the scope of the present document and bound to the identifier of that VIM.\n* NOTE 1:\tIf applicable, this attribute also provides information about the resourceGroupIds\n that are accessible using a particular set of credentials. See definition of\n \"resourceGroupId\" in clause 9.5.3.3.\n* NOTE 2:\tOnce the connectivity between VNFM and VIM, CISM, CIR or MCIOP repository is provided\n through a secure connection over HTTP Secure (HTTP over SSL/TLS), and the connection might also be\n established through a VPN (for example TLS-based VPN tunnelling) for site-to-site connection, the\n \"accessInfo\" JSON data structure, and the sensitive data related information (\"username\"/\"password\" as\n required properties for authentication purpose), will be transmitted as plain text through a TLS tunnel\n without additional encoding/encryption before transmitting it, making the sensitive data visible to the\n endpoint. The base64 encoded certificates are only used by the VNFM to verify the authenticity of the\n interface endpoint of the VIM, CISM, CIR or MCIOP repository.\n \n* NOTE 3:\t ETSI GS NFV-SOL 009 [i.18] specifies the means to configure into the VNFM applicable VIM connection information via the \"NFV-MANO Configuration and Information Management\" interface. \n* NOTE 4:\t Due to the possibility of configuring such information into the VNFM out-of-band, by means outside the scope of the present document, as well as in-band, by means specified in the present document, care should be taken to avoid unintended conflicts in the VNFM when managing such information.\n",
"type": "object",
"required": ["vimType"],
"properties": {
@@ -893,6 +893,10 @@
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.\n",
+ "type": "string"
}
}
}
@@ -1024,7 +1028,7 @@
"description": "If present, this attribute signals the changes to VIM connection info that were passed in the related \"ChangeCurrentVnfPkgRequest\" structure. The provisions for sensitive information defined in clause 4.4.1.6 apply.\n",
"type": "object",
"additionalProperties": {
- "description": "This type represents parameters to connect to a VIM, a CISM, a CIR or a MCIOP repository for managing the resources of a VNF instance.\nThis structure is used to convey VIM-related, CISM-related, CIR-related, or MCIOP-repository-related parameters over the Or-Vnfm interface. Additional parameters for a VIM, a CISM, a CIR or a MCIOP repository may be configured into the VNFM by means outside the scope of the present document and bound to the identifier of that VIM.\n* NOTE 1:\tIf applicable, this attribute also provides information about the resourceGroupIds\n that are accessible using a particular set of credentials. See definition of\n \"resourceGroupId\" in clause 9.5.3.3.\n* NOTE 2:\tOnce the connectivity between VNFM and VIM, CISM, CIR or MCIOP repository is provided\n through a secure connection over HTTP Secure (HTTP over SSL/TLS), and the connection might also be\n established through a VPN (for example TLS-based VPN tunnelling) for site-to-site connection, the\n \"accessInfo\" JSON data structure, and the sensitive data related information (\"username\"/\"password\" as\n required properties for authentication purpose), will be transmitted as plain text through a TLS tunnel\n without additional encoding/encryption before transmitting it, making the sensitive data visible to the\n endpoint. The base64 encoded certificates are only used by the VNFM to verify the authenticity of the\n interface endpoint of the VIM, CISM, CIR or MCIOP repository.\n",
+ "description": "This type represents parameters to connect to a VIM, a CISM, a CIR or a MCIOP repository for managing the resources of a VNF instance.\nThis structure is used to convey VIM-related, CISM-related, CIR-related, or MCIOP-repository-related parameters over the Or-Vnfm interface. Additional parameters for a VIM, a CISM, a CIR or a MCIOP repository may be configured into the VNFM by means outside the scope of the present document and bound to the identifier of that VIM.\n* NOTE 1:\tIf applicable, this attribute also provides information about the resourceGroupIds\n that are accessible using a particular set of credentials. See definition of\n \"resourceGroupId\" in clause 9.5.3.3.\n* NOTE 2:\tOnce the connectivity between VNFM and VIM, CISM, CIR or MCIOP repository is provided\n through a secure connection over HTTP Secure (HTTP over SSL/TLS), and the connection might also be\n established through a VPN (for example TLS-based VPN tunnelling) for site-to-site connection, the\n \"accessInfo\" JSON data structure, and the sensitive data related information (\"username\"/\"password\" as\n required properties for authentication purpose), will be transmitted as plain text through a TLS tunnel\n without additional encoding/encryption before transmitting it, making the sensitive data visible to the\n endpoint. The base64 encoded certificates are only used by the VNFM to verify the authenticity of the\n interface endpoint of the VIM, CISM, CIR or MCIOP repository.\n \n* NOTE 3:\t ETSI GS NFV-SOL 009 [i.18] specifies the means to configure into the VNFM applicable VIM connection information via the \"NFV-MANO Configuration and Information Management\" interface. \n* NOTE 4:\t Due to the possibility of configuring such information into the VNFM out-of-band, by means outside the scope of the present document, as well as in-band, by means specified in the present document, care should be taken to avoid unintended conflicts in the VNFM when managing such information.\n",
"type": "object",
"required": ["vimType"],
"properties": {
diff --git a/SOL003/VNFLifecycleManagement-API/schemas/VnfSnapshotInfo.schema.json b/SOL003/VNFLifecycleManagement-API/schemas/VnfSnapshotInfo.schema.json
index ad5405ed9333c635fbef3c8ed9f3dbcbe6c2716a..91484f61620e89015e05515484b261bb944ff51b 100644
--- a/SOL003/VNFLifecycleManagement-API/schemas/VnfSnapshotInfo.schema.json
+++ b/SOL003/VNFLifecycleManagement-API/schemas/VnfSnapshotInfo.schema.json
@@ -46,7 +46,7 @@
"type": "string"
},
"vnfInstance": {
- "description": "This type represents a VNF instance.\nNOTE:\tClause B.3.2 provides examples illustrating the relationship among the different run-time \n information elements (CP, VL and link ports) used to represent the connectivity of a VNF.\n\nNOTE 1:\tModifying the value of this attribute shall not be performed when conflicts exist between \n the previous and the newly referred VNF package, i.e. when the new VNFD is changed with \n respect to the previous VNFD in other aspects than merely referencing to other VNF software \n images. In order to avoid misalignment of the VnfInstance with the current VNF's on-boarded \n VNF Package, the values of attributes in the VnfInstance that have corresponding attributes \n in the VNFD shall be kept in sync with the values in the VNFD.\nNOTE 2:\tETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on TOSCA specifications. NOTE 3:\tVNF configurable properties are sometimes also referred to as configuration parameters applicable \n to a VNF. Some of these are set prior to instantiation and cannot be modified if the VNF is instantiated, \n some are set prior to instantiation (are part of initial configuration) and can be modified later, \n and others can be set only after instantiation. The applicability of certain configuration may \n depend on the VNF and the required operation of the VNF at a certain point in time.\nNOTE 4:\tUpon creation of the VnfInstance structure, the VNFM shall create and initialize all child attributes \n of \"vnfConfigurableProperties\", \"metadata\" and \"extensions\" that were declared in the VNFD with a defined \n initial value. The defined initial values can be declared in the VNFD, and/or, in case of \"metadata\", \n obtained from the \"CreateVnfRequest\" structure. Child attributes of \"vnfConfigurableProperties\", \n \"metadata\" and \"extensions\" that have no defined initial value shall not be created, in order to be \n consistent with the semantics of the JSON Merge Patch method (see IETF RFC 7396) that interprets null \n values as deletion request.\nNOTE 5:\tIt is possible to have several ExtManagedVirtualLinkInfo for the same VNF internal VL in case of a \n multi-site VNF spanning several VIMs. The set of ExtManagedVirtualLinkInfo corresponding to the same \n VNF internal VL shall indicate so by referencing to the same VnfVirtualLinkDesc and externally-managed \n multi-site VL instance (refer to clause 5.5.3.3).\nNOTE 6:\tEven though externally-managed internal VLs are also used for VNF-internal connectivity, they shall \n not be listed in the \"vnfVirtualLinkResourceInfo\" attribute as this would be redundant.\n",
+ "description": "This type represents a VNF instance.\nNOTE:\tClause B.3.2 provides examples illustrating the relationship among the different run-time \n data types (CP, VL and link ports) used to represent the connectivity of a VNF.\n\nNOTE 1:\tModifying the value of this attribute shall not be performed when conflicts exist between \n the previous and the newly referred VNF package, i.e. when the new VNFD is changed with \n respect to the previous VNFD in other aspects than merely referencing to other VNF software \n images. In order to avoid misalignment of the VnfInstance with the current VNF's on-boarded \n VNF Package, the values of attributes in the VnfInstance that have corresponding attributes \n in the VNFD shall be kept in sync with the values in the VNFD.\nNOTE 2:\tETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on TOSCA specifications. NOTE 3:\tVNF configurable properties are sometimes also referred to as configuration parameters applicable \n to a VNF. Some of these are set prior to instantiation and cannot be modified if the VNF is instantiated, \n some are set prior to instantiation (are part of initial configuration) and can be modified later, \n and others can be set only after instantiation. The applicability of certain configuration may \n depend on the VNF and the required operation of the VNF at a certain point in time.\nNOTE 4:\tUpon creation of the VnfInstance structure, the VNFM shall create and initialize all child attributes \n of \"vnfConfigurableProperties\", \"metadata\" and \"extensions\" that were declared in the VNFD with a defined \n initial value. The defined initial values can be declared in the VNFD, and/or, in case of \"metadata\", \n obtained from the \"CreateVnfRequest\" structure. Child attributes of \"vnfConfigurableProperties\", \n \"metadata\" and \"extensions\" that have no defined initial value shall not be created, in order to be \n consistent with the semantics of the JSON Merge Patch method (see IETF RFC 7396) that interprets null \n values as deletion request.\nNOTE 5:\tIt is possible to have several ExtManagedVirtualLinkInfo for the same VNF internal VL in case of a \n multi-site VNF spanning several VIMs. The set of ExtManagedVirtualLinkInfo corresponding to the same \n VNF internal VL shall indicate so by referencing to the same VnfVirtualLinkDesc and externally-managed \n multi-site VL instance (refer to clause 5.5.3.3).\nNOTE 6:\tEven though externally-managed internal VLs are also used for VNF-internal connectivity, they shall \n not be listed in the \"vnfVirtualLinkResourceInfo\" attribute as this would be redundant.\n",
"type": "object",
"required": [
"id",
@@ -96,10 +96,10 @@
"type": "object"
},
"vimConnectionInfo": {
- "description": "Information about VIM or CISM connections to be used for managing the resources for the VNF instance. The keys of the map, each of which identifies information about a particular VIM connection, are managed by the NFVO and referenced from other data structures via the \"vimConnectionId\" attribute. This attribute shall only be supported and present if - the resources of at least of the VNFCs are managed by a VIM and VNF-related resource management in direct mode is applicable. - the resources of at least of the VNFCs are managed by a CISM. This attribute can be modified with the PATCH method.\n",
+ "description": "Information about VIM or CISM connections to be used for managing the resources for the VNF instance. The keys of the map, each of which identifies information about a particular VIM connection, are managed by the NFVO and referenced from other data structures via the \"vimConnectionId\" attribute. This attribute shall only be supported and present if - the resources of at least of the VNFCs are managed by a VIM and VNF-related resource management in direct mode is applicable. - the resources of at least of the VNFCs are managed by a CISM. This attribute can be modified with the PATCH method. If VIM connection information is provisioned to the VNFM by means outside the scope of the present document, the information in the \"vimConnectionInfo\" attribute provides necessary information for binding the VnfInstance representing the \"Individual VNF instance\" to the applicable VIM connection information used to perform resource management for the VNF instance. See also the definition of the \"VimConnectionInfo\" in clause 4.4.1.6.\n",
"type": "object",
"additionalProperties": {
- "description": "This type represents parameters to connect to a VIM, a CISM, a CIR or a MCIOP repository for managing the resources of a VNF instance.\nThis structure is used to convey VIM-related, CISM-related, CIR-related, or MCIOP-repository-related parameters over the Or-Vnfm interface. Additional parameters for a VIM, a CISM, a CIR or a MCIOP repository may be configured into the VNFM by means outside the scope of the present document and bound to the identifier of that VIM.\n* NOTE 1:\tIf applicable, this attribute also provides information about the resourceGroupIds\n that are accessible using a particular set of credentials. See definition of\n \"resourceGroupId\" in clause 9.5.3.3.\n* NOTE 2:\tOnce the connectivity between VNFM and VIM, CISM, CIR or MCIOP repository is provided\n through a secure connection over HTTP Secure (HTTP over SSL/TLS), and the connection might also be\n established through a VPN (for example TLS-based VPN tunnelling) for site-to-site connection, the\n \"accessInfo\" JSON data structure, and the sensitive data related information (\"username\"/\"password\" as\n required properties for authentication purpose), will be transmitted as plain text through a TLS tunnel\n without additional encoding/encryption before transmitting it, making the sensitive data visible to the\n endpoint. The base64 encoded certificates are only used by the VNFM to verify the authenticity of the\n interface endpoint of the VIM, CISM, CIR or MCIOP repository.\n",
+ "description": "This type represents parameters to connect to a VIM, a CISM, a CIR or a MCIOP repository for managing the resources of a VNF instance.\nThis structure is used to convey VIM-related, CISM-related, CIR-related, or MCIOP-repository-related parameters over the Or-Vnfm interface. Additional parameters for a VIM, a CISM, a CIR or a MCIOP repository may be configured into the VNFM by means outside the scope of the present document and bound to the identifier of that VIM.\n* NOTE 1:\tIf applicable, this attribute also provides information about the resourceGroupIds\n that are accessible using a particular set of credentials. See definition of\n \"resourceGroupId\" in clause 9.5.3.3.\n* NOTE 2:\tOnce the connectivity between VNFM and VIM, CISM, CIR or MCIOP repository is provided\n through a secure connection over HTTP Secure (HTTP over SSL/TLS), and the connection might also be\n established through a VPN (for example TLS-based VPN tunnelling) for site-to-site connection, the\n \"accessInfo\" JSON data structure, and the sensitive data related information (\"username\"/\"password\" as\n required properties for authentication purpose), will be transmitted as plain text through a TLS tunnel\n without additional encoding/encryption before transmitting it, making the sensitive data visible to the\n endpoint. The base64 encoded certificates are only used by the VNFM to verify the authenticity of the\n interface endpoint of the VIM, CISM, CIR or MCIOP repository.\n \n* NOTE 3:\t ETSI GS NFV-SOL 009 [i.18] specifies the means to configure into the VNFM applicable VIM connection information via the \"NFV-MANO Configuration and Information Management\" interface. \n* NOTE 4:\t Due to the possibility of configuring such information into the VNFM out-of-band, by means outside the scope of the present document, as well as in-band, by means specified in the present document, care should be taken to avoid unintended conflicts in the VNFM when managing such information.\n",
"type": "object",
"required": ["vimType"],
"properties": {
@@ -130,7 +130,7 @@
"description": "Information about the CIR connection for managing OS container images for the VNF instance. Shall be present when all or part of the VNF is realized by a set of OS containers and shall be absent otherwise.\n",
"type": "object",
"additionalProperties": {
- "description": "This type represents parameters to connect to a VIM, a CISM, a CIR or a MCIOP repository for managing the resources of a VNF instance.\nThis structure is used to convey VIM-related, CISM-related, CIR-related, or MCIOP-repository-related parameters over the Or-Vnfm interface. Additional parameters for a VIM, a CISM, a CIR or a MCIOP repository may be configured into the VNFM by means outside the scope of the present document and bound to the identifier of that VIM.\n* NOTE 1:\tIf applicable, this attribute also provides information about the resourceGroupIds\n that are accessible using a particular set of credentials. See definition of\n \"resourceGroupId\" in clause 9.5.3.3.\n* NOTE 2:\tOnce the connectivity between VNFM and VIM, CISM, CIR or MCIOP repository is provided\n through a secure connection over HTTP Secure (HTTP over SSL/TLS), and the connection might also be\n established through a VPN (for example TLS-based VPN tunnelling) for site-to-site connection, the\n \"accessInfo\" JSON data structure, and the sensitive data related information (\"username\"/\"password\" as\n required properties for authentication purpose), will be transmitted as plain text through a TLS tunnel\n without additional encoding/encryption before transmitting it, making the sensitive data visible to the\n endpoint. The base64 encoded certificates are only used by the VNFM to verify the authenticity of the\n interface endpoint of the VIM, CISM, CIR or MCIOP repository.\n",
+ "description": "This type represents parameters to connect to a VIM, a CISM, a CIR or a MCIOP repository for managing the resources of a VNF instance.\nThis structure is used to convey VIM-related, CISM-related, CIR-related, or MCIOP-repository-related parameters over the Or-Vnfm interface. Additional parameters for a VIM, a CISM, a CIR or a MCIOP repository may be configured into the VNFM by means outside the scope of the present document and bound to the identifier of that VIM.\n* NOTE 1:\tIf applicable, this attribute also provides information about the resourceGroupIds\n that are accessible using a particular set of credentials. See definition of\n \"resourceGroupId\" in clause 9.5.3.3.\n* NOTE 2:\tOnce the connectivity between VNFM and VIM, CISM, CIR or MCIOP repository is provided\n through a secure connection over HTTP Secure (HTTP over SSL/TLS), and the connection might also be\n established through a VPN (for example TLS-based VPN tunnelling) for site-to-site connection, the\n \"accessInfo\" JSON data structure, and the sensitive data related information (\"username\"/\"password\" as\n required properties for authentication purpose), will be transmitted as plain text through a TLS tunnel\n without additional encoding/encryption before transmitting it, making the sensitive data visible to the\n endpoint. The base64 encoded certificates are only used by the VNFM to verify the authenticity of the\n interface endpoint of the VIM, CISM, CIR or MCIOP repository.\n \n* NOTE 3:\t ETSI GS NFV-SOL 009 [i.18] specifies the means to configure into the VNFM applicable VIM connection information via the \"NFV-MANO Configuration and Information Management\" interface. \n* NOTE 4:\t Due to the possibility of configuring such information into the VNFM out-of-band, by means outside the scope of the present document, as well as in-band, by means specified in the present document, care should be taken to avoid unintended conflicts in the VNFM when managing such information.\n",
"type": "object",
"required": ["vimType"],
"properties": {
@@ -161,7 +161,7 @@
"description": "Information about the MCIOP repository for the VNF instance. Shall be present when all or part of the VNF is realized by a set of OS containers and shall be absent otherwise. See note 1.\n",
"type": "object",
"additionalProperties": {
- "description": "This type represents parameters to connect to a VIM, a CISM, a CIR or a MCIOP repository for managing the resources of a VNF instance.\nThis structure is used to convey VIM-related, CISM-related, CIR-related, or MCIOP-repository-related parameters over the Or-Vnfm interface. Additional parameters for a VIM, a CISM, a CIR or a MCIOP repository may be configured into the VNFM by means outside the scope of the present document and bound to the identifier of that VIM.\n* NOTE 1:\tIf applicable, this attribute also provides information about the resourceGroupIds\n that are accessible using a particular set of credentials. See definition of\n \"resourceGroupId\" in clause 9.5.3.3.\n* NOTE 2:\tOnce the connectivity between VNFM and VIM, CISM, CIR or MCIOP repository is provided\n through a secure connection over HTTP Secure (HTTP over SSL/TLS), and the connection might also be\n established through a VPN (for example TLS-based VPN tunnelling) for site-to-site connection, the\n \"accessInfo\" JSON data structure, and the sensitive data related information (\"username\"/\"password\" as\n required properties for authentication purpose), will be transmitted as plain text through a TLS tunnel\n without additional encoding/encryption before transmitting it, making the sensitive data visible to the\n endpoint. The base64 encoded certificates are only used by the VNFM to verify the authenticity of the\n interface endpoint of the VIM, CISM, CIR or MCIOP repository.\n",
+ "description": "This type represents parameters to connect to a VIM, a CISM, a CIR or a MCIOP repository for managing the resources of a VNF instance.\nThis structure is used to convey VIM-related, CISM-related, CIR-related, or MCIOP-repository-related parameters over the Or-Vnfm interface. Additional parameters for a VIM, a CISM, a CIR or a MCIOP repository may be configured into the VNFM by means outside the scope of the present document and bound to the identifier of that VIM.\n* NOTE 1:\tIf applicable, this attribute also provides information about the resourceGroupIds\n that are accessible using a particular set of credentials. See definition of\n \"resourceGroupId\" in clause 9.5.3.3.\n* NOTE 2:\tOnce the connectivity between VNFM and VIM, CISM, CIR or MCIOP repository is provided\n through a secure connection over HTTP Secure (HTTP over SSL/TLS), and the connection might also be\n established through a VPN (for example TLS-based VPN tunnelling) for site-to-site connection, the\n \"accessInfo\" JSON data structure, and the sensitive data related information (\"username\"/\"password\" as\n required properties for authentication purpose), will be transmitted as plain text through a TLS tunnel\n without additional encoding/encryption before transmitting it, making the sensitive data visible to the\n endpoint. The base64 encoded certificates are only used by the VNFM to verify the authenticity of the\n interface endpoint of the VIM, CISM, CIR or MCIOP repository.\n \n* NOTE 3:\t ETSI GS NFV-SOL 009 [i.18] specifies the means to configure into the VNFM applicable VIM connection information via the \"NFV-MANO Configuration and Information Management\" interface. \n* NOTE 4:\t Due to the possibility of configuring such information into the VNFM out-of-band, by means outside the scope of the present document, as well as in-band, by means specified in the present document, care should be taken to avoid unintended conflicts in the VNFM when managing such information.\n",
"type": "object",
"required": ["vimType"],
"properties": {
@@ -399,6 +399,10 @@
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.\n",
+ "type": "string"
}
}
}
@@ -575,6 +579,10 @@
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.\n",
+ "type": "string"
}
}
}
@@ -780,6 +788,10 @@
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.\n",
+ "type": "string"
}
}
}
@@ -1152,6 +1164,10 @@
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.\n",
+ "type": "string"
}
}
}
@@ -1720,6 +1736,10 @@
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.\n",
+ "type": "string"
}
}
}
@@ -2041,7 +2061,7 @@
"mcioType": {
"description": "The type of MCIO. Specific values, their semantics and associated MCIO types are defined in clause 5.5.4.9. Additional values are also permitted. See note 1.\n",
"type": "string",
- "enum": ["Deployment", "Statefulset"]
+ "enum": ["Deployment", "StatefulSet"]
},
"desiredInstances": {
"description": "Number of desired MCIO instances.\n",
diff --git a/SOL003/VNFLifecycleManagement-API/schemas/VnfSnapshotInfoModifications.schema.json b/SOL003/VNFLifecycleManagement-API/schemas/VnfSnapshotInfoModifications.schema.json
index 105dc0032df6698418fc4809668a1c3b4e291667..3784f137595c4ec4b5e8ba4d7ea150e84da9b58b 100644
--- a/SOL003/VNFLifecycleManagement-API/schemas/VnfSnapshotInfoModifications.schema.json
+++ b/SOL003/VNFLifecycleManagement-API/schemas/VnfSnapshotInfoModifications.schema.json
@@ -41,7 +41,7 @@
"type": "string"
},
"vnfInstance": {
- "description": "This type represents a VNF instance.\nNOTE:\tClause B.3.2 provides examples illustrating the relationship among the different run-time \n information elements (CP, VL and link ports) used to represent the connectivity of a VNF.\n\nNOTE 1:\tModifying the value of this attribute shall not be performed when conflicts exist between \n the previous and the newly referred VNF package, i.e. when the new VNFD is changed with \n respect to the previous VNFD in other aspects than merely referencing to other VNF software \n images. In order to avoid misalignment of the VnfInstance with the current VNF's on-boarded \n VNF Package, the values of attributes in the VnfInstance that have corresponding attributes \n in the VNFD shall be kept in sync with the values in the VNFD.\nNOTE 2:\tETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on TOSCA specifications. NOTE 3:\tVNF configurable properties are sometimes also referred to as configuration parameters applicable \n to a VNF. Some of these are set prior to instantiation and cannot be modified if the VNF is instantiated, \n some are set prior to instantiation (are part of initial configuration) and can be modified later, \n and others can be set only after instantiation. The applicability of certain configuration may \n depend on the VNF and the required operation of the VNF at a certain point in time.\nNOTE 4:\tUpon creation of the VnfInstance structure, the VNFM shall create and initialize all child attributes \n of \"vnfConfigurableProperties\", \"metadata\" and \"extensions\" that were declared in the VNFD with a defined \n initial value. The defined initial values can be declared in the VNFD, and/or, in case of \"metadata\", \n obtained from the \"CreateVnfRequest\" structure. Child attributes of \"vnfConfigurableProperties\", \n \"metadata\" and \"extensions\" that have no defined initial value shall not be created, in order to be \n consistent with the semantics of the JSON Merge Patch method (see IETF RFC 7396) that interprets null \n values as deletion request.\nNOTE 5:\tIt is possible to have several ExtManagedVirtualLinkInfo for the same VNF internal VL in case of a \n multi-site VNF spanning several VIMs. The set of ExtManagedVirtualLinkInfo corresponding to the same \n VNF internal VL shall indicate so by referencing to the same VnfVirtualLinkDesc and externally-managed \n multi-site VL instance (refer to clause 5.5.3.3).\nNOTE 6:\tEven though externally-managed internal VLs are also used for VNF-internal connectivity, they shall \n not be listed in the \"vnfVirtualLinkResourceInfo\" attribute as this would be redundant.\n",
+ "description": "This type represents a VNF instance.\nNOTE:\tClause B.3.2 provides examples illustrating the relationship among the different run-time \n data types (CP, VL and link ports) used to represent the connectivity of a VNF.\n\nNOTE 1:\tModifying the value of this attribute shall not be performed when conflicts exist between \n the previous and the newly referred VNF package, i.e. when the new VNFD is changed with \n respect to the previous VNFD in other aspects than merely referencing to other VNF software \n images. In order to avoid misalignment of the VnfInstance with the current VNF's on-boarded \n VNF Package, the values of attributes in the VnfInstance that have corresponding attributes \n in the VNFD shall be kept in sync with the values in the VNFD.\nNOTE 2:\tETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on TOSCA specifications. NOTE 3:\tVNF configurable properties are sometimes also referred to as configuration parameters applicable \n to a VNF. Some of these are set prior to instantiation and cannot be modified if the VNF is instantiated, \n some are set prior to instantiation (are part of initial configuration) and can be modified later, \n and others can be set only after instantiation. The applicability of certain configuration may \n depend on the VNF and the required operation of the VNF at a certain point in time.\nNOTE 4:\tUpon creation of the VnfInstance structure, the VNFM shall create and initialize all child attributes \n of \"vnfConfigurableProperties\", \"metadata\" and \"extensions\" that were declared in the VNFD with a defined \n initial value. The defined initial values can be declared in the VNFD, and/or, in case of \"metadata\", \n obtained from the \"CreateVnfRequest\" structure. Child attributes of \"vnfConfigurableProperties\", \n \"metadata\" and \"extensions\" that have no defined initial value shall not be created, in order to be \n consistent with the semantics of the JSON Merge Patch method (see IETF RFC 7396) that interprets null \n values as deletion request.\nNOTE 5:\tIt is possible to have several ExtManagedVirtualLinkInfo for the same VNF internal VL in case of a \n multi-site VNF spanning several VIMs. The set of ExtManagedVirtualLinkInfo corresponding to the same \n VNF internal VL shall indicate so by referencing to the same VnfVirtualLinkDesc and externally-managed \n multi-site VL instance (refer to clause 5.5.3.3).\nNOTE 6:\tEven though externally-managed internal VLs are also used for VNF-internal connectivity, they shall \n not be listed in the \"vnfVirtualLinkResourceInfo\" attribute as this would be redundant.\n",
"type": "object",
"required": [
"id",
@@ -91,10 +91,10 @@
"type": "object"
},
"vimConnectionInfo": {
- "description": "Information about VIM or CISM connections to be used for managing the resources for the VNF instance. The keys of the map, each of which identifies information about a particular VIM connection, are managed by the NFVO and referenced from other data structures via the \"vimConnectionId\" attribute. This attribute shall only be supported and present if - the resources of at least of the VNFCs are managed by a VIM and VNF-related resource management in direct mode is applicable. - the resources of at least of the VNFCs are managed by a CISM. This attribute can be modified with the PATCH method.\n",
+ "description": "Information about VIM or CISM connections to be used for managing the resources for the VNF instance. The keys of the map, each of which identifies information about a particular VIM connection, are managed by the NFVO and referenced from other data structures via the \"vimConnectionId\" attribute. This attribute shall only be supported and present if - the resources of at least of the VNFCs are managed by a VIM and VNF-related resource management in direct mode is applicable. - the resources of at least of the VNFCs are managed by a CISM. This attribute can be modified with the PATCH method. If VIM connection information is provisioned to the VNFM by means outside the scope of the present document, the information in the \"vimConnectionInfo\" attribute provides necessary information for binding the VnfInstance representing the \"Individual VNF instance\" to the applicable VIM connection information used to perform resource management for the VNF instance. See also the definition of the \"VimConnectionInfo\" in clause 4.4.1.6.\n",
"type": "object",
"additionalProperties": {
- "description": "This type represents parameters to connect to a VIM, a CISM, a CIR or a MCIOP repository for managing the resources of a VNF instance.\nThis structure is used to convey VIM-related, CISM-related, CIR-related, or MCIOP-repository-related parameters over the Or-Vnfm interface. Additional parameters for a VIM, a CISM, a CIR or a MCIOP repository may be configured into the VNFM by means outside the scope of the present document and bound to the identifier of that VIM.\n* NOTE 1:\tIf applicable, this attribute also provides information about the resourceGroupIds\n that are accessible using a particular set of credentials. See definition of\n \"resourceGroupId\" in clause 9.5.3.3.\n* NOTE 2:\tOnce the connectivity between VNFM and VIM, CISM, CIR or MCIOP repository is provided\n through a secure connection over HTTP Secure (HTTP over SSL/TLS), and the connection might also be\n established through a VPN (for example TLS-based VPN tunnelling) for site-to-site connection, the\n \"accessInfo\" JSON data structure, and the sensitive data related information (\"username\"/\"password\" as\n required properties for authentication purpose), will be transmitted as plain text through a TLS tunnel\n without additional encoding/encryption before transmitting it, making the sensitive data visible to the\n endpoint. The base64 encoded certificates are only used by the VNFM to verify the authenticity of the\n interface endpoint of the VIM, CISM, CIR or MCIOP repository.\n",
+ "description": "This type represents parameters to connect to a VIM, a CISM, a CIR or a MCIOP repository for managing the resources of a VNF instance.\nThis structure is used to convey VIM-related, CISM-related, CIR-related, or MCIOP-repository-related parameters over the Or-Vnfm interface. Additional parameters for a VIM, a CISM, a CIR or a MCIOP repository may be configured into the VNFM by means outside the scope of the present document and bound to the identifier of that VIM.\n* NOTE 1:\tIf applicable, this attribute also provides information about the resourceGroupIds\n that are accessible using a particular set of credentials. See definition of\n \"resourceGroupId\" in clause 9.5.3.3.\n* NOTE 2:\tOnce the connectivity between VNFM and VIM, CISM, CIR or MCIOP repository is provided\n through a secure connection over HTTP Secure (HTTP over SSL/TLS), and the connection might also be\n established through a VPN (for example TLS-based VPN tunnelling) for site-to-site connection, the\n \"accessInfo\" JSON data structure, and the sensitive data related information (\"username\"/\"password\" as\n required properties for authentication purpose), will be transmitted as plain text through a TLS tunnel\n without additional encoding/encryption before transmitting it, making the sensitive data visible to the\n endpoint. The base64 encoded certificates are only used by the VNFM to verify the authenticity of the\n interface endpoint of the VIM, CISM, CIR or MCIOP repository.\n \n* NOTE 3:\t ETSI GS NFV-SOL 009 [i.18] specifies the means to configure into the VNFM applicable VIM connection information via the \"NFV-MANO Configuration and Information Management\" interface. \n* NOTE 4:\t Due to the possibility of configuring such information into the VNFM out-of-band, by means outside the scope of the present document, as well as in-band, by means specified in the present document, care should be taken to avoid unintended conflicts in the VNFM when managing such information.\n",
"type": "object",
"required": [
"vimType"
@@ -127,7 +127,7 @@
"description": "Information about the CIR connection for managing OS container images for the VNF instance. Shall be present when all or part of the VNF is realized by a set of OS containers and shall be absent otherwise.\n",
"type": "object",
"additionalProperties": {
- "description": "This type represents parameters to connect to a VIM, a CISM, a CIR or a MCIOP repository for managing the resources of a VNF instance.\nThis structure is used to convey VIM-related, CISM-related, CIR-related, or MCIOP-repository-related parameters over the Or-Vnfm interface. Additional parameters for a VIM, a CISM, a CIR or a MCIOP repository may be configured into the VNFM by means outside the scope of the present document and bound to the identifier of that VIM.\n* NOTE 1:\tIf applicable, this attribute also provides information about the resourceGroupIds\n that are accessible using a particular set of credentials. See definition of\n \"resourceGroupId\" in clause 9.5.3.3.\n* NOTE 2:\tOnce the connectivity between VNFM and VIM, CISM, CIR or MCIOP repository is provided\n through a secure connection over HTTP Secure (HTTP over SSL/TLS), and the connection might also be\n established through a VPN (for example TLS-based VPN tunnelling) for site-to-site connection, the\n \"accessInfo\" JSON data structure, and the sensitive data related information (\"username\"/\"password\" as\n required properties for authentication purpose), will be transmitted as plain text through a TLS tunnel\n without additional encoding/encryption before transmitting it, making the sensitive data visible to the\n endpoint. The base64 encoded certificates are only used by the VNFM to verify the authenticity of the\n interface endpoint of the VIM, CISM, CIR or MCIOP repository.\n",
+ "description": "This type represents parameters to connect to a VIM, a CISM, a CIR or a MCIOP repository for managing the resources of a VNF instance.\nThis structure is used to convey VIM-related, CISM-related, CIR-related, or MCIOP-repository-related parameters over the Or-Vnfm interface. Additional parameters for a VIM, a CISM, a CIR or a MCIOP repository may be configured into the VNFM by means outside the scope of the present document and bound to the identifier of that VIM.\n* NOTE 1:\tIf applicable, this attribute also provides information about the resourceGroupIds\n that are accessible using a particular set of credentials. See definition of\n \"resourceGroupId\" in clause 9.5.3.3.\n* NOTE 2:\tOnce the connectivity between VNFM and VIM, CISM, CIR or MCIOP repository is provided\n through a secure connection over HTTP Secure (HTTP over SSL/TLS), and the connection might also be\n established through a VPN (for example TLS-based VPN tunnelling) for site-to-site connection, the\n \"accessInfo\" JSON data structure, and the sensitive data related information (\"username\"/\"password\" as\n required properties for authentication purpose), will be transmitted as plain text through a TLS tunnel\n without additional encoding/encryption before transmitting it, making the sensitive data visible to the\n endpoint. The base64 encoded certificates are only used by the VNFM to verify the authenticity of the\n interface endpoint of the VIM, CISM, CIR or MCIOP repository.\n \n* NOTE 3:\t ETSI GS NFV-SOL 009 [i.18] specifies the means to configure into the VNFM applicable VIM connection information via the \"NFV-MANO Configuration and Information Management\" interface. \n* NOTE 4:\t Due to the possibility of configuring such information into the VNFM out-of-band, by means outside the scope of the present document, as well as in-band, by means specified in the present document, care should be taken to avoid unintended conflicts in the VNFM when managing such information.\n",
"type": "object",
"required": [
"vimType"
@@ -160,7 +160,7 @@
"description": "Information about the MCIOP repository for the VNF instance. Shall be present when all or part of the VNF is realized by a set of OS containers and shall be absent otherwise. See note 1.\n",
"type": "object",
"additionalProperties": {
- "description": "This type represents parameters to connect to a VIM, a CISM, a CIR or a MCIOP repository for managing the resources of a VNF instance.\nThis structure is used to convey VIM-related, CISM-related, CIR-related, or MCIOP-repository-related parameters over the Or-Vnfm interface. Additional parameters for a VIM, a CISM, a CIR or a MCIOP repository may be configured into the VNFM by means outside the scope of the present document and bound to the identifier of that VIM.\n* NOTE 1:\tIf applicable, this attribute also provides information about the resourceGroupIds\n that are accessible using a particular set of credentials. See definition of\n \"resourceGroupId\" in clause 9.5.3.3.\n* NOTE 2:\tOnce the connectivity between VNFM and VIM, CISM, CIR or MCIOP repository is provided\n through a secure connection over HTTP Secure (HTTP over SSL/TLS), and the connection might also be\n established through a VPN (for example TLS-based VPN tunnelling) for site-to-site connection, the\n \"accessInfo\" JSON data structure, and the sensitive data related information (\"username\"/\"password\" as\n required properties for authentication purpose), will be transmitted as plain text through a TLS tunnel\n without additional encoding/encryption before transmitting it, making the sensitive data visible to the\n endpoint. The base64 encoded certificates are only used by the VNFM to verify the authenticity of the\n interface endpoint of the VIM, CISM, CIR or MCIOP repository.\n",
+ "description": "This type represents parameters to connect to a VIM, a CISM, a CIR or a MCIOP repository for managing the resources of a VNF instance.\nThis structure is used to convey VIM-related, CISM-related, CIR-related, or MCIOP-repository-related parameters over the Or-Vnfm interface. Additional parameters for a VIM, a CISM, a CIR or a MCIOP repository may be configured into the VNFM by means outside the scope of the present document and bound to the identifier of that VIM.\n* NOTE 1:\tIf applicable, this attribute also provides information about the resourceGroupIds\n that are accessible using a particular set of credentials. See definition of\n \"resourceGroupId\" in clause 9.5.3.3.\n* NOTE 2:\tOnce the connectivity between VNFM and VIM, CISM, CIR or MCIOP repository is provided\n through a secure connection over HTTP Secure (HTTP over SSL/TLS), and the connection might also be\n established through a VPN (for example TLS-based VPN tunnelling) for site-to-site connection, the\n \"accessInfo\" JSON data structure, and the sensitive data related information (\"username\"/\"password\" as\n required properties for authentication purpose), will be transmitted as plain text through a TLS tunnel\n without additional encoding/encryption before transmitting it, making the sensitive data visible to the\n endpoint. The base64 encoded certificates are only used by the VNFM to verify the authenticity of the\n interface endpoint of the VIM, CISM, CIR or MCIOP repository.\n \n* NOTE 3:\t ETSI GS NFV-SOL 009 [i.18] specifies the means to configure into the VNFM applicable VIM connection information via the \"NFV-MANO Configuration and Information Management\" interface. \n* NOTE 4:\t Due to the possibility of configuring such information into the VNFM out-of-band, by means outside the scope of the present document, as well as in-band, by means specified in the present document, care should be taken to avoid unintended conflicts in the VNFM when managing such information.\n",
"type": "object",
"required": [
"vimType"
@@ -450,9 +450,13 @@
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.\n",
+ "type": "string"
+ }
}
- }
- }
+ }
}
}
},
@@ -652,11 +656,15 @@
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.\n",
+ "type": "string"
+ }
}
- }
+ }
}
- }
- }
+ }
},
"associatedVnfcCpIds": {
"description": "Identifiers of the VnfcCps that share the virtual IP addresse allocated to the VIP CP instance. See note.\n",
@@ -882,11 +890,15 @@
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.\n",
+ "type": "string"
+ }
}
- }
- }
+ }
}
- }
+ }
},
"vduIds": {
"description": "Reference to the VDU(s) which implement the service accessible via the virtual CP instance. See note.\n",
@@ -1302,17 +1314,21 @@
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.\n",
+ "type": "string"
+ }
}
- }
- }
+ }
}
+ }
}
- }
+ }
}
- }
- }
+ }
}
- }
+ }
},
"extNetAttDefResource": {
"description": "Network attachment definition resources that provide the specification of the interface to attach connection points to this VL.\n",
@@ -1916,10 +1932,14 @@
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.\n",
+ "type": "string"
}
+ }
}
- }
- }
+ }
}
},
"vnfLinkPortId": {
@@ -2251,7 +2271,7 @@
"type": "string",
"enum": [
"Deployment",
- "Statefulset"
+ "StatefulSet"
]
},
"desiredInstances": {
diff --git a/SOL003/VNFLifecycleManagement-API/schemas/VnfSnapshotsInfo.schema.json b/SOL003/VNFLifecycleManagement-API/schemas/VnfSnapshotsInfo.schema.json
index 29623d2df1d4b59454598ca67552abe6265c3980..8b7803429c0d515ae9458b2e190889f6c24eace9 100644
--- a/SOL003/VNFLifecycleManagement-API/schemas/VnfSnapshotsInfo.schema.json
+++ b/SOL003/VNFLifecycleManagement-API/schemas/VnfSnapshotsInfo.schema.json
@@ -48,7 +48,7 @@
"type": "string"
},
"vnfInstance": {
- "description": "This type represents a VNF instance.\nNOTE:\tClause B.3.2 provides examples illustrating the relationship among the different run-time \n information elements (CP, VL and link ports) used to represent the connectivity of a VNF.\n\nNOTE 1:\tModifying the value of this attribute shall not be performed when conflicts exist between \n the previous and the newly referred VNF package, i.e. when the new VNFD is changed with \n respect to the previous VNFD in other aspects than merely referencing to other VNF software \n images. In order to avoid misalignment of the VnfInstance with the current VNF's on-boarded \n VNF Package, the values of attributes in the VnfInstance that have corresponding attributes \n in the VNFD shall be kept in sync with the values in the VNFD.\nNOTE 2:\tETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on TOSCA specifications. NOTE 3:\tVNF configurable properties are sometimes also referred to as configuration parameters applicable \n to a VNF. Some of these are set prior to instantiation and cannot be modified if the VNF is instantiated, \n some are set prior to instantiation (are part of initial configuration) and can be modified later, \n and others can be set only after instantiation. The applicability of certain configuration may \n depend on the VNF and the required operation of the VNF at a certain point in time.\nNOTE 4:\tUpon creation of the VnfInstance structure, the VNFM shall create and initialize all child attributes \n of \"vnfConfigurableProperties\", \"metadata\" and \"extensions\" that were declared in the VNFD with a defined \n initial value. The defined initial values can be declared in the VNFD, and/or, in case of \"metadata\", \n obtained from the \"CreateVnfRequest\" structure. Child attributes of \"vnfConfigurableProperties\", \n \"metadata\" and \"extensions\" that have no defined initial value shall not be created, in order to be \n consistent with the semantics of the JSON Merge Patch method (see IETF RFC 7396) that interprets null \n values as deletion request.\nNOTE 5:\tIt is possible to have several ExtManagedVirtualLinkInfo for the same VNF internal VL in case of a \n multi-site VNF spanning several VIMs. The set of ExtManagedVirtualLinkInfo corresponding to the same \n VNF internal VL shall indicate so by referencing to the same VnfVirtualLinkDesc and externally-managed \n multi-site VL instance (refer to clause 5.5.3.3).\nNOTE 6:\tEven though externally-managed internal VLs are also used for VNF-internal connectivity, they shall \n not be listed in the \"vnfVirtualLinkResourceInfo\" attribute as this would be redundant.\n",
+ "description": "This type represents a VNF instance.\nNOTE:\tClause B.3.2 provides examples illustrating the relationship among the different run-time \n data types (CP, VL and link ports) used to represent the connectivity of a VNF.\n\nNOTE 1:\tModifying the value of this attribute shall not be performed when conflicts exist between \n the previous and the newly referred VNF package, i.e. when the new VNFD is changed with \n respect to the previous VNFD in other aspects than merely referencing to other VNF software \n images. In order to avoid misalignment of the VnfInstance with the current VNF's on-boarded \n VNF Package, the values of attributes in the VnfInstance that have corresponding attributes \n in the VNFD shall be kept in sync with the values in the VNFD.\nNOTE 2:\tETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on TOSCA specifications. NOTE 3:\tVNF configurable properties are sometimes also referred to as configuration parameters applicable \n to a VNF. Some of these are set prior to instantiation and cannot be modified if the VNF is instantiated, \n some are set prior to instantiation (are part of initial configuration) and can be modified later, \n and others can be set only after instantiation. The applicability of certain configuration may \n depend on the VNF and the required operation of the VNF at a certain point in time.\nNOTE 4:\tUpon creation of the VnfInstance structure, the VNFM shall create and initialize all child attributes \n of \"vnfConfigurableProperties\", \"metadata\" and \"extensions\" that were declared in the VNFD with a defined \n initial value. The defined initial values can be declared in the VNFD, and/or, in case of \"metadata\", \n obtained from the \"CreateVnfRequest\" structure. Child attributes of \"vnfConfigurableProperties\", \n \"metadata\" and \"extensions\" that have no defined initial value shall not be created, in order to be \n consistent with the semantics of the JSON Merge Patch method (see IETF RFC 7396) that interprets null \n values as deletion request.\nNOTE 5:\tIt is possible to have several ExtManagedVirtualLinkInfo for the same VNF internal VL in case of a \n multi-site VNF spanning several VIMs. The set of ExtManagedVirtualLinkInfo corresponding to the same \n VNF internal VL shall indicate so by referencing to the same VnfVirtualLinkDesc and externally-managed \n multi-site VL instance (refer to clause 5.5.3.3).\nNOTE 6:\tEven though externally-managed internal VLs are also used for VNF-internal connectivity, they shall \n not be listed in the \"vnfVirtualLinkResourceInfo\" attribute as this would be redundant.\n",
"type": "object",
"required": [
"id",
@@ -98,10 +98,10 @@
"type": "object"
},
"vimConnectionInfo": {
- "description": "Information about VIM or CISM connections to be used for managing the resources for the VNF instance. The keys of the map, each of which identifies information about a particular VIM connection, are managed by the NFVO and referenced from other data structures via the \"vimConnectionId\" attribute. This attribute shall only be supported and present if - the resources of at least of the VNFCs are managed by a VIM and VNF-related resource management in direct mode is applicable. - the resources of at least of the VNFCs are managed by a CISM. This attribute can be modified with the PATCH method.\n",
+ "description": "Information about VIM or CISM connections to be used for managing the resources for the VNF instance. The keys of the map, each of which identifies information about a particular VIM connection, are managed by the NFVO and referenced from other data structures via the \"vimConnectionId\" attribute. This attribute shall only be supported and present if - the resources of at least of the VNFCs are managed by a VIM and VNF-related resource management in direct mode is applicable. - the resources of at least of the VNFCs are managed by a CISM. This attribute can be modified with the PATCH method. If VIM connection information is provisioned to the VNFM by means outside the scope of the present document, the information in the \"vimConnectionInfo\" attribute provides necessary information for binding the VnfInstance representing the \"Individual VNF instance\" to the applicable VIM connection information used to perform resource management for the VNF instance. See also the definition of the \"VimConnectionInfo\" in clause 4.4.1.6.\n",
"type": "object",
"additionalProperties": {
- "description": "This type represents parameters to connect to a VIM, a CISM, a CIR or a MCIOP repository for managing the resources of a VNF instance.\nThis structure is used to convey VIM-related, CISM-related, CIR-related, or MCIOP-repository-related parameters over the Or-Vnfm interface. Additional parameters for a VIM, a CISM, a CIR or a MCIOP repository may be configured into the VNFM by means outside the scope of the present document and bound to the identifier of that VIM.\n* NOTE 1:\tIf applicable, this attribute also provides information about the resourceGroupIds\n that are accessible using a particular set of credentials. See definition of\n \"resourceGroupId\" in clause 9.5.3.3.\n* NOTE 2:\tOnce the connectivity between VNFM and VIM, CISM, CIR or MCIOP repository is provided\n through a secure connection over HTTP Secure (HTTP over SSL/TLS), and the connection might also be\n established through a VPN (for example TLS-based VPN tunnelling) for site-to-site connection, the\n \"accessInfo\" JSON data structure, and the sensitive data related information (\"username\"/\"password\" as\n required properties for authentication purpose), will be transmitted as plain text through a TLS tunnel\n without additional encoding/encryption before transmitting it, making the sensitive data visible to the\n endpoint. The base64 encoded certificates are only used by the VNFM to verify the authenticity of the\n interface endpoint of the VIM, CISM, CIR or MCIOP repository.\n",
+ "description": "This type represents parameters to connect to a VIM, a CISM, a CIR or a MCIOP repository for managing the resources of a VNF instance.\nThis structure is used to convey VIM-related, CISM-related, CIR-related, or MCIOP-repository-related parameters over the Or-Vnfm interface. Additional parameters for a VIM, a CISM, a CIR or a MCIOP repository may be configured into the VNFM by means outside the scope of the present document and bound to the identifier of that VIM.\n* NOTE 1:\tIf applicable, this attribute also provides information about the resourceGroupIds\n that are accessible using a particular set of credentials. See definition of\n \"resourceGroupId\" in clause 9.5.3.3.\n* NOTE 2:\tOnce the connectivity between VNFM and VIM, CISM, CIR or MCIOP repository is provided\n through a secure connection over HTTP Secure (HTTP over SSL/TLS), and the connection might also be\n established through a VPN (for example TLS-based VPN tunnelling) for site-to-site connection, the\n \"accessInfo\" JSON data structure, and the sensitive data related information (\"username\"/\"password\" as\n required properties for authentication purpose), will be transmitted as plain text through a TLS tunnel\n without additional encoding/encryption before transmitting it, making the sensitive data visible to the\n endpoint. The base64 encoded certificates are only used by the VNFM to verify the authenticity of the\n interface endpoint of the VIM, CISM, CIR or MCIOP repository.\n \n* NOTE 3:\t ETSI GS NFV-SOL 009 [i.18] specifies the means to configure into the VNFM applicable VIM connection information via the \"NFV-MANO Configuration and Information Management\" interface. \n* NOTE 4:\t Due to the possibility of configuring such information into the VNFM out-of-band, by means outside the scope of the present document, as well as in-band, by means specified in the present document, care should be taken to avoid unintended conflicts in the VNFM when managing such information.\n",
"type": "object",
"required": ["vimType"],
"properties": {
@@ -132,7 +132,7 @@
"description": "Information about the CIR connection for managing OS container images for the VNF instance. Shall be present when all or part of the VNF is realized by a set of OS containers and shall be absent otherwise.\n",
"type": "object",
"additionalProperties": {
- "description": "This type represents parameters to connect to a VIM, a CISM, a CIR or a MCIOP repository for managing the resources of a VNF instance.\nThis structure is used to convey VIM-related, CISM-related, CIR-related, or MCIOP-repository-related parameters over the Or-Vnfm interface. Additional parameters for a VIM, a CISM, a CIR or a MCIOP repository may be configured into the VNFM by means outside the scope of the present document and bound to the identifier of that VIM.\n* NOTE 1:\tIf applicable, this attribute also provides information about the resourceGroupIds\n that are accessible using a particular set of credentials. See definition of\n \"resourceGroupId\" in clause 9.5.3.3.\n* NOTE 2:\tOnce the connectivity between VNFM and VIM, CISM, CIR or MCIOP repository is provided\n through a secure connection over HTTP Secure (HTTP over SSL/TLS), and the connection might also be\n established through a VPN (for example TLS-based VPN tunnelling) for site-to-site connection, the\n \"accessInfo\" JSON data structure, and the sensitive data related information (\"username\"/\"password\" as\n required properties for authentication purpose), will be transmitted as plain text through a TLS tunnel\n without additional encoding/encryption before transmitting it, making the sensitive data visible to the\n endpoint. The base64 encoded certificates are only used by the VNFM to verify the authenticity of the\n interface endpoint of the VIM, CISM, CIR or MCIOP repository.\n",
+ "description": "This type represents parameters to connect to a VIM, a CISM, a CIR or a MCIOP repository for managing the resources of a VNF instance.\nThis structure is used to convey VIM-related, CISM-related, CIR-related, or MCIOP-repository-related parameters over the Or-Vnfm interface. Additional parameters for a VIM, a CISM, a CIR or a MCIOP repository may be configured into the VNFM by means outside the scope of the present document and bound to the identifier of that VIM.\n* NOTE 1:\tIf applicable, this attribute also provides information about the resourceGroupIds\n that are accessible using a particular set of credentials. See definition of\n \"resourceGroupId\" in clause 9.5.3.3.\n* NOTE 2:\tOnce the connectivity between VNFM and VIM, CISM, CIR or MCIOP repository is provided\n through a secure connection over HTTP Secure (HTTP over SSL/TLS), and the connection might also be\n established through a VPN (for example TLS-based VPN tunnelling) for site-to-site connection, the\n \"accessInfo\" JSON data structure, and the sensitive data related information (\"username\"/\"password\" as\n required properties for authentication purpose), will be transmitted as plain text through a TLS tunnel\n without additional encoding/encryption before transmitting it, making the sensitive data visible to the\n endpoint. The base64 encoded certificates are only used by the VNFM to verify the authenticity of the\n interface endpoint of the VIM, CISM, CIR or MCIOP repository.\n \n* NOTE 3:\t ETSI GS NFV-SOL 009 [i.18] specifies the means to configure into the VNFM applicable VIM connection information via the \"NFV-MANO Configuration and Information Management\" interface. \n* NOTE 4:\t Due to the possibility of configuring such information into the VNFM out-of-band, by means outside the scope of the present document, as well as in-band, by means specified in the present document, care should be taken to avoid unintended conflicts in the VNFM when managing such information.\n",
"type": "object",
"required": ["vimType"],
"properties": {
@@ -163,7 +163,7 @@
"description": "Information about the MCIOP repository for the VNF instance. Shall be present when all or part of the VNF is realized by a set of OS containers and shall be absent otherwise. See note 1.\n",
"type": "object",
"additionalProperties": {
- "description": "This type represents parameters to connect to a VIM, a CISM, a CIR or a MCIOP repository for managing the resources of a VNF instance.\nThis structure is used to convey VIM-related, CISM-related, CIR-related, or MCIOP-repository-related parameters over the Or-Vnfm interface. Additional parameters for a VIM, a CISM, a CIR or a MCIOP repository may be configured into the VNFM by means outside the scope of the present document and bound to the identifier of that VIM.\n* NOTE 1:\tIf applicable, this attribute also provides information about the resourceGroupIds\n that are accessible using a particular set of credentials. See definition of\n \"resourceGroupId\" in clause 9.5.3.3.\n* NOTE 2:\tOnce the connectivity between VNFM and VIM, CISM, CIR or MCIOP repository is provided\n through a secure connection over HTTP Secure (HTTP over SSL/TLS), and the connection might also be\n established through a VPN (for example TLS-based VPN tunnelling) for site-to-site connection, the\n \"accessInfo\" JSON data structure, and the sensitive data related information (\"username\"/\"password\" as\n required properties for authentication purpose), will be transmitted as plain text through a TLS tunnel\n without additional encoding/encryption before transmitting it, making the sensitive data visible to the\n endpoint. The base64 encoded certificates are only used by the VNFM to verify the authenticity of the\n interface endpoint of the VIM, CISM, CIR or MCIOP repository.\n",
+ "description": "This type represents parameters to connect to a VIM, a CISM, a CIR or a MCIOP repository for managing the resources of a VNF instance.\nThis structure is used to convey VIM-related, CISM-related, CIR-related, or MCIOP-repository-related parameters over the Or-Vnfm interface. Additional parameters for a VIM, a CISM, a CIR or a MCIOP repository may be configured into the VNFM by means outside the scope of the present document and bound to the identifier of that VIM.\n* NOTE 1:\tIf applicable, this attribute also provides information about the resourceGroupIds\n that are accessible using a particular set of credentials. See definition of\n \"resourceGroupId\" in clause 9.5.3.3.\n* NOTE 2:\tOnce the connectivity between VNFM and VIM, CISM, CIR or MCIOP repository is provided\n through a secure connection over HTTP Secure (HTTP over SSL/TLS), and the connection might also be\n established through a VPN (for example TLS-based VPN tunnelling) for site-to-site connection, the\n \"accessInfo\" JSON data structure, and the sensitive data related information (\"username\"/\"password\" as\n required properties for authentication purpose), will be transmitted as plain text through a TLS tunnel\n without additional encoding/encryption before transmitting it, making the sensitive data visible to the\n endpoint. The base64 encoded certificates are only used by the VNFM to verify the authenticity of the\n interface endpoint of the VIM, CISM, CIR or MCIOP repository.\n \n* NOTE 3:\t ETSI GS NFV-SOL 009 [i.18] specifies the means to configure into the VNFM applicable VIM connection information via the \"NFV-MANO Configuration and Information Management\" interface. \n* NOTE 4:\t Due to the possibility of configuring such information into the VNFM out-of-band, by means outside the scope of the present document, as well as in-band, by means specified in the present document, care should be taken to avoid unintended conflicts in the VNFM when managing such information.\n",
"type": "object",
"required": ["vimType"],
"properties": {
@@ -409,6 +409,10 @@
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.\n",
+ "type": "string"
}
}
}
@@ -588,6 +592,10 @@
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.\n",
+ "type": "string"
}
}
}
@@ -796,6 +804,10 @@
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.\n",
+ "type": "string"
}
}
}
@@ -1172,6 +1184,10 @@
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.\n",
+ "type": "string"
}
}
}
@@ -1740,6 +1756,10 @@
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.\n",
+ "type": "string"
}
}
}
@@ -2061,7 +2081,7 @@
"mcioType": {
"description": "The type of MCIO. Specific values, their semantics and associated MCIO types are defined in clause 5.5.4.9. Additional values are also permitted. See note 1.\n",
"type": "string",
- "enum": ["Deployment", "Statefulset"]
+ "enum": ["Deployment", "StatefulSet"]
},
"desiredInstances": {
"description": "Number of desired MCIO instances.\n",
diff --git a/SOL003/VNFLifecycleManagement-API/schemas/vnfInstance.schema.json b/SOL003/VNFLifecycleManagement-API/schemas/vnfInstance.schema.json
index a1c00316949b29edc813c5bdd52b02bc8d44dbdb..23b24a0327aea12712aa9b95d5ff952c8f3ea1a1 100644
--- a/SOL003/VNFLifecycleManagement-API/schemas/vnfInstance.schema.json
+++ b/SOL003/VNFLifecycleManagement-API/schemas/vnfInstance.schema.json
@@ -52,7 +52,7 @@
"description": "Information about VIM or CISM connections to be used for managing the resources for the VNF instance. The keys of the map, each of which identifies information about a particular VIM connection, are managed by the NFVO and referenced from other data structures via the \"vimConnectionId\" attribute. This attribute shall only be supported and present if - the resources of at least of the VNFCs are managed by a VIM and VNF-related resource management in direct mode is applicable. - the resources of at least of the VNFCs are managed by a CISM. This attribute can be modified with the PATCH method.\n",
"type": "object",
"additionalProperties": {
- "description": "This type represents parameters to connect to a VIM, a CISM, a CIR or a MCIOP repository for managing the resources of a VNF instance.\nThis structure is used to convey VIM-related, CISM-related, CIR-related, or MCIOP-repository-related parameters over the Or-Vnfm interface. Additional parameters for a VIM, a CISM, a CIR or a MCIOP repository may be configured into the VNFM by means outside the scope of the present document and bound to the identifier of that VIM.\n* NOTE 1:\tIf applicable, this attribute also provides information about the resourceGroupIds\n that are accessible using a particular set of credentials. See definition of\n \"resourceGroupId\" in clause 9.5.3.3.\n* NOTE 2:\tOnce the connectivity between VNFM and VIM, CISM, CIR or MCIOP repository is provided\n through a secure connection over HTTP Secure (HTTP over SSL/TLS), and the connection might also be\n established through a VPN (for example TLS-based VPN tunnelling) for site-to-site connection, the\n \"accessInfo\" JSON data structure, and the sensitive data related information (\"username\"/\"password\" as\n required properties for authentication purpose), will be transmitted as plain text through a TLS tunnel\n without additional encoding/encryption before transmitting it, making the sensitive data visible to the\n endpoint. The base64 encoded certificates are only used by the VNFM to verify the authenticity of the\n interface endpoint of the VIM, CISM, CIR or MCIOP repository.\n",
+ "description": "This type represents parameters to connect to a VIM, a CISM, a CIR or a MCIOP repository for managing the resources of a VNF instance.\nThis structure is used to convey VIM-related, CISM-related, CIR-related, or MCIOP-repository-related parameters over the Or-Vnfm interface. Additional parameters for a VIM, a CISM, a CIR or a MCIOP repository may be configured into the VNFM by means outside the scope of the present document and bound to the identifier of that VIM.\n* NOTE 1:\tIf applicable, this attribute also provides information about the resourceGroupIds\n that are accessible using a particular set of credentials. See definition of\n \"resourceGroupId\" in clause 9.5.3.3.\n* NOTE 2:\tOnce the connectivity between VNFM and VIM, CISM, CIR or MCIOP repository is provided\n through a secure connection over HTTP Secure (HTTP over SSL/TLS), and the connection might also be\n established through a VPN (for example TLS-based VPN tunnelling) for site-to-site connection, the\n \"accessInfo\" JSON data structure, and the sensitive data related information (\"username\"/\"password\" as\n required properties for authentication purpose), will be transmitted as plain text through a TLS tunnel\n without additional encoding/encryption before transmitting it, making the sensitive data visible to the\n endpoint. The base64 encoded certificates are only used by the VNFM to verify the authenticity of the\n interface endpoint of the VIM, CISM, CIR or MCIOP repository.\n \n* NOTE 3:\t ETSI GS NFV-SOL 009 [i.18] specifies the means to configure into the VNFM applicable VIM connection information via the \"NFV-MANO Configuration and Information Management\" interface. \n* NOTE 4:\t Due to the possibility of configuring such information into the VNFM out-of-band, by means outside the scope of the present document, as well as in-band, by means specified in the present document, care should be taken to avoid unintended conflicts in the VNFM when managing such information.\n",
"type": "object",
"required": ["vimType"],
"properties": {
@@ -83,7 +83,7 @@
"description": "Information about the CIR connection for managing OS container images for the VNF instance. Shall be present when all or part of the VNF is realized by a set of OS containers and shall be absent otherwise.\n",
"type": "object",
"additionalProperties": {
- "description": "This type represents parameters to connect to a VIM, a CISM, a CIR or a MCIOP repository for managing the resources of a VNF instance.\nThis structure is used to convey VIM-related, CISM-related, CIR-related, or MCIOP-repository-related parameters over the Or-Vnfm interface. Additional parameters for a VIM, a CISM, a CIR or a MCIOP repository may be configured into the VNFM by means outside the scope of the present document and bound to the identifier of that VIM.\n* NOTE 1:\tIf applicable, this attribute also provides information about the resourceGroupIds\n that are accessible using a particular set of credentials. See definition of\n \"resourceGroupId\" in clause 9.5.3.3.\n* NOTE 2:\tOnce the connectivity between VNFM and VIM, CISM, CIR or MCIOP repository is provided\n through a secure connection over HTTP Secure (HTTP over SSL/TLS), and the connection might also be\n established through a VPN (for example TLS-based VPN tunnelling) for site-to-site connection, the\n \"accessInfo\" JSON data structure, and the sensitive data related information (\"username\"/\"password\" as\n required properties for authentication purpose), will be transmitted as plain text through a TLS tunnel\n without additional encoding/encryption before transmitting it, making the sensitive data visible to the\n endpoint. The base64 encoded certificates are only used by the VNFM to verify the authenticity of the\n interface endpoint of the VIM, CISM, CIR or MCIOP repository.\n",
+ "description": "This type represents parameters to connect to a VIM, a CISM, a CIR or a MCIOP repository for managing the resources of a VNF instance.\nThis structure is used to convey VIM-related, CISM-related, CIR-related, or MCIOP-repository-related parameters over the Or-Vnfm interface. Additional parameters for a VIM, a CISM, a CIR or a MCIOP repository may be configured into the VNFM by means outside the scope of the present document and bound to the identifier of that VIM.\n* NOTE 1:\tIf applicable, this attribute also provides information about the resourceGroupIds\n that are accessible using a particular set of credentials. See definition of\n \"resourceGroupId\" in clause 9.5.3.3.\n* NOTE 2:\tOnce the connectivity between VNFM and VIM, CISM, CIR or MCIOP repository is provided\n through a secure connection over HTTP Secure (HTTP over SSL/TLS), and the connection might also be\n established through a VPN (for example TLS-based VPN tunnelling) for site-to-site connection, the\n \"accessInfo\" JSON data structure, and the sensitive data related information (\"username\"/\"password\" as\n required properties for authentication purpose), will be transmitted as plain text through a TLS tunnel\n without additional encoding/encryption before transmitting it, making the sensitive data visible to the\n endpoint. The base64 encoded certificates are only used by the VNFM to verify the authenticity of the\n interface endpoint of the VIM, CISM, CIR or MCIOP repository.\n \n* NOTE 3:\t ETSI GS NFV-SOL 009 [i.18] specifies the means to configure into the VNFM applicable VIM connection information via the \"NFV-MANO Configuration and Information Management\" interface. \n* NOTE 4:\t Due to the possibility of configuring such information into the VNFM out-of-band, by means outside the scope of the present document, as well as in-band, by means specified in the present document, care should be taken to avoid unintended conflicts in the VNFM when managing such information.\n",
"type": "object",
"required": ["vimType"],
"properties": {
@@ -114,7 +114,7 @@
"description": "Information about the MCIOP repository for the VNF instance. Shall be present when all or part of the VNF is realized by a set of OS containers and shall be absent otherwise. See note 1.\n",
"type": "object",
"additionalProperties": {
- "description": "This type represents parameters to connect to a VIM, a CISM, a CIR or a MCIOP repository for managing the resources of a VNF instance.\nThis structure is used to convey VIM-related, CISM-related, CIR-related, or MCIOP-repository-related parameters over the Or-Vnfm interface. Additional parameters for a VIM, a CISM, a CIR or a MCIOP repository may be configured into the VNFM by means outside the scope of the present document and bound to the identifier of that VIM.\n* NOTE 1:\tIf applicable, this attribute also provides information about the resourceGroupIds\n that are accessible using a particular set of credentials. See definition of\n \"resourceGroupId\" in clause 9.5.3.3.\n* NOTE 2:\tOnce the connectivity between VNFM and VIM, CISM, CIR or MCIOP repository is provided\n through a secure connection over HTTP Secure (HTTP over SSL/TLS), and the connection might also be\n established through a VPN (for example TLS-based VPN tunnelling) for site-to-site connection, the\n \"accessInfo\" JSON data structure, and the sensitive data related information (\"username\"/\"password\" as\n required properties for authentication purpose), will be transmitted as plain text through a TLS tunnel\n without additional encoding/encryption before transmitting it, making the sensitive data visible to the\n endpoint. The base64 encoded certificates are only used by the VNFM to verify the authenticity of the\n interface endpoint of the VIM, CISM, CIR or MCIOP repository.\n",
+ "description": "This type represents parameters to connect to a VIM, a CISM, a CIR or a MCIOP repository for managing the resources of a VNF instance.\nThis structure is used to convey VIM-related, CISM-related, CIR-related, or MCIOP-repository-related parameters over the Or-Vnfm interface. Additional parameters for a VIM, a CISM, a CIR or a MCIOP repository may be configured into the VNFM by means outside the scope of the present document and bound to the identifier of that VIM.\n* NOTE 1:\tIf applicable, this attribute also provides information about the resourceGroupIds\n that are accessible using a particular set of credentials. See definition of\n \"resourceGroupId\" in clause 9.5.3.3.\n* NOTE 2:\tOnce the connectivity between VNFM and VIM, CISM, CIR or MCIOP repository is provided\n through a secure connection over HTTP Secure (HTTP over SSL/TLS), and the connection might also be\n established through a VPN (for example TLS-based VPN tunnelling) for site-to-site connection, the\n \"accessInfo\" JSON data structure, and the sensitive data related information (\"username\"/\"password\" as\n required properties for authentication purpose), will be transmitted as plain text through a TLS tunnel\n without additional encoding/encryption before transmitting it, making the sensitive data visible to the\n endpoint. The base64 encoded certificates are only used by the VNFM to verify the authenticity of the\n interface endpoint of the VIM, CISM, CIR or MCIOP repository.\n \n* NOTE 3:\t ETSI GS NFV-SOL 009 [i.18] specifies the means to configure into the VNFM applicable VIM connection information via the \"NFV-MANO Configuration and Information Management\" interface. \n* NOTE 4:\t Due to the possibility of configuring such information into the VNFM out-of-band, by means outside the scope of the present document, as well as in-band, by means specified in the present document, care should be taken to avoid unintended conflicts in the VNFM when managing such information.\n",
"type": "object",
"required": ["vimType"],
"properties": {
@@ -349,6 +349,10 @@
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.\n",
+ "type": "string"
}
}
}
@@ -522,6 +526,10 @@
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.\n",
+ "type": "string"
}
}
}
@@ -719,6 +727,10 @@
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.\n",
+ "type": "string"
}
}
}
@@ -1085,6 +1097,10 @@
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.\n",
+ "type": "string"
}
}
}
@@ -1637,6 +1653,10 @@
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.\n",
+ "type": "string"
}
}
}
@@ -1950,7 +1970,7 @@
"mcioType": {
"description": "The type of MCIO. Specific values, their semantics and associated MCIO types are defined in clause 5.5.4.9. Additional values are also permitted. See note 1.\n",
"type": "string",
- "enum": ["Deployment", "Statefulset"]
+ "enum": ["Deployment", "StatefulSet"]
},
"desiredInstances": {
"description": "Number of desired MCIO instances.\n",
diff --git a/SOL003/VNFLifecycleManagement-API/schemas/vnfInstances.schema.json b/SOL003/VNFLifecycleManagement-API/schemas/vnfInstances.schema.json
index a25322e6a67dd3746cfbace583dfb30d7763ad8a..6abfe683c4dd438024a0e399b70b208e693a8054 100644
--- a/SOL003/VNFLifecycleManagement-API/schemas/vnfInstances.schema.json
+++ b/SOL003/VNFLifecycleManagement-API/schemas/vnfInstances.schema.json
@@ -54,7 +54,7 @@
"description": "Information about VIM or CISM connections to be used for managing the resources for the VNF instance. The keys of the map, each of which identifies information about a particular VIM connection, are managed by the NFVO and referenced from other data structures via the \"vimConnectionId\" attribute. This attribute shall only be supported and present if - the resources of at least of the VNFCs are managed by a VIM and VNF-related resource management in direct mode is applicable. - the resources of at least of the VNFCs are managed by a CISM. This attribute can be modified with the PATCH method.\n",
"type": "object",
"additionalProperties": {
- "description": "This type represents parameters to connect to a VIM, a CISM, a CIR or a MCIOP repository for managing the resources of a VNF instance.\nThis structure is used to convey VIM-related, CISM-related, CIR-related, or MCIOP-repository-related parameters over the Or-Vnfm interface. Additional parameters for a VIM, a CISM, a CIR or a MCIOP repository may be configured into the VNFM by means outside the scope of the present document and bound to the identifier of that VIM.\n* NOTE 1:\tIf applicable, this attribute also provides information about the resourceGroupIds\n that are accessible using a particular set of credentials. See definition of\n \"resourceGroupId\" in clause 9.5.3.3.\n* NOTE 2:\tOnce the connectivity between VNFM and VIM, CISM, CIR or MCIOP repository is provided\n through a secure connection over HTTP Secure (HTTP over SSL/TLS), and the connection might also be\n established through a VPN (for example TLS-based VPN tunnelling) for site-to-site connection, the\n \"accessInfo\" JSON data structure, and the sensitive data related information (\"username\"/\"password\" as\n required properties for authentication purpose), will be transmitted as plain text through a TLS tunnel\n without additional encoding/encryption before transmitting it, making the sensitive data visible to the\n endpoint. The base64 encoded certificates are only used by the VNFM to verify the authenticity of the\n interface endpoint of the VIM, CISM, CIR or MCIOP repository.\n",
+ "description": "This type represents parameters to connect to a VIM, a CISM, a CIR or a MCIOP repository for managing the resources of a VNF instance.\nThis structure is used to convey VIM-related, CISM-related, CIR-related, or MCIOP-repository-related parameters over the Or-Vnfm interface. Additional parameters for a VIM, a CISM, a CIR or a MCIOP repository may be configured into the VNFM by means outside the scope of the present document and bound to the identifier of that VIM.\n* NOTE 1:\tIf applicable, this attribute also provides information about the resourceGroupIds\n that are accessible using a particular set of credentials. See definition of\n \"resourceGroupId\" in clause 9.5.3.3.\n* NOTE 2:\tOnce the connectivity between VNFM and VIM, CISM, CIR or MCIOP repository is provided\n through a secure connection over HTTP Secure (HTTP over SSL/TLS), and the connection might also be\n established through a VPN (for example TLS-based VPN tunnelling) for site-to-site connection, the\n \"accessInfo\" JSON data structure, and the sensitive data related information (\"username\"/\"password\" as\n required properties for authentication purpose), will be transmitted as plain text through a TLS tunnel\n without additional encoding/encryption before transmitting it, making the sensitive data visible to the\n endpoint. The base64 encoded certificates are only used by the VNFM to verify the authenticity of the\n interface endpoint of the VIM, CISM, CIR or MCIOP repository.\n \n* NOTE 3:\t ETSI GS NFV-SOL 009 [i.18] specifies the means to configure into the VNFM applicable VIM connection information via the \"NFV-MANO Configuration and Information Management\" interface. \n* NOTE 4:\t Due to the possibility of configuring such information into the VNFM out-of-band, by means outside the scope of the present document, as well as in-band, by means specified in the present document, care should be taken to avoid unintended conflicts in the VNFM when managing such information.\n",
"type": "object",
"required": ["vimType"],
"properties": {
@@ -85,7 +85,7 @@
"description": "Information about the CIR connection for managing OS container images for the VNF instance. Shall be present when all or part of the VNF is realized by a set of OS containers and shall be absent otherwise.\n",
"type": "object",
"additionalProperties": {
- "description": "This type represents parameters to connect to a VIM, a CISM, a CIR or a MCIOP repository for managing the resources of a VNF instance.\nThis structure is used to convey VIM-related, CISM-related, CIR-related, or MCIOP-repository-related parameters over the Or-Vnfm interface. Additional parameters for a VIM, a CISM, a CIR or a MCIOP repository may be configured into the VNFM by means outside the scope of the present document and bound to the identifier of that VIM.\n* NOTE 1:\tIf applicable, this attribute also provides information about the resourceGroupIds\n that are accessible using a particular set of credentials. See definition of\n \"resourceGroupId\" in clause 9.5.3.3.\n* NOTE 2:\tOnce the connectivity between VNFM and VIM, CISM, CIR or MCIOP repository is provided\n through a secure connection over HTTP Secure (HTTP over SSL/TLS), and the connection might also be\n established through a VPN (for example TLS-based VPN tunnelling) for site-to-site connection, the\n \"accessInfo\" JSON data structure, and the sensitive data related information (\"username\"/\"password\" as\n required properties for authentication purpose), will be transmitted as plain text through a TLS tunnel\n without additional encoding/encryption before transmitting it, making the sensitive data visible to the\n endpoint. The base64 encoded certificates are only used by the VNFM to verify the authenticity of the\n interface endpoint of the VIM, CISM, CIR or MCIOP repository.\n",
+ "description": "This type represents parameters to connect to a VIM, a CISM, a CIR or a MCIOP repository for managing the resources of a VNF instance.\nThis structure is used to convey VIM-related, CISM-related, CIR-related, or MCIOP-repository-related parameters over the Or-Vnfm interface. Additional parameters for a VIM, a CISM, a CIR or a MCIOP repository may be configured into the VNFM by means outside the scope of the present document and bound to the identifier of that VIM.\n* NOTE 1:\tIf applicable, this attribute also provides information about the resourceGroupIds\n that are accessible using a particular set of credentials. See definition of\n \"resourceGroupId\" in clause 9.5.3.3.\n* NOTE 2:\tOnce the connectivity between VNFM and VIM, CISM, CIR or MCIOP repository is provided\n through a secure connection over HTTP Secure (HTTP over SSL/TLS), and the connection might also be\n established through a VPN (for example TLS-based VPN tunnelling) for site-to-site connection, the\n \"accessInfo\" JSON data structure, and the sensitive data related information (\"username\"/\"password\" as\n required properties for authentication purpose), will be transmitted as plain text through a TLS tunnel\n without additional encoding/encryption before transmitting it, making the sensitive data visible to the\n endpoint. The base64 encoded certificates are only used by the VNFM to verify the authenticity of the\n interface endpoint of the VIM, CISM, CIR or MCIOP repository.\n \n* NOTE 3:\t ETSI GS NFV-SOL 009 [i.18] specifies the means to configure into the VNFM applicable VIM connection information via the \"NFV-MANO Configuration and Information Management\" interface. \n* NOTE 4:\t Due to the possibility of configuring such information into the VNFM out-of-band, by means outside the scope of the present document, as well as in-band, by means specified in the present document, care should be taken to avoid unintended conflicts in the VNFM when managing such information.\n",
"type": "object",
"required": ["vimType"],
"properties": {
@@ -116,7 +116,7 @@
"description": "Information about the MCIOP repository for the VNF instance. Shall be present when all or part of the VNF is realized by a set of OS containers and shall be absent otherwise. See note 1.\n",
"type": "object",
"additionalProperties": {
- "description": "This type represents parameters to connect to a VIM, a CISM, a CIR or a MCIOP repository for managing the resources of a VNF instance.\nThis structure is used to convey VIM-related, CISM-related, CIR-related, or MCIOP-repository-related parameters over the Or-Vnfm interface. Additional parameters for a VIM, a CISM, a CIR or a MCIOP repository may be configured into the VNFM by means outside the scope of the present document and bound to the identifier of that VIM.\n* NOTE 1:\tIf applicable, this attribute also provides information about the resourceGroupIds\n that are accessible using a particular set of credentials. See definition of\n \"resourceGroupId\" in clause 9.5.3.3.\n* NOTE 2:\tOnce the connectivity between VNFM and VIM, CISM, CIR or MCIOP repository is provided\n through a secure connection over HTTP Secure (HTTP over SSL/TLS), and the connection might also be\n established through a VPN (for example TLS-based VPN tunnelling) for site-to-site connection, the\n \"accessInfo\" JSON data structure, and the sensitive data related information (\"username\"/\"password\" as\n required properties for authentication purpose), will be transmitted as plain text through a TLS tunnel\n without additional encoding/encryption before transmitting it, making the sensitive data visible to the\n endpoint. The base64 encoded certificates are only used by the VNFM to verify the authenticity of the\n interface endpoint of the VIM, CISM, CIR or MCIOP repository.\n",
+ "description": "This type represents parameters to connect to a VIM, a CISM, a CIR or a MCIOP repository for managing the resources of a VNF instance.\nThis structure is used to convey VIM-related, CISM-related, CIR-related, or MCIOP-repository-related parameters over the Or-Vnfm interface. Additional parameters for a VIM, a CISM, a CIR or a MCIOP repository may be configured into the VNFM by means outside the scope of the present document and bound to the identifier of that VIM.\n* NOTE 1:\tIf applicable, this attribute also provides information about the resourceGroupIds\n that are accessible using a particular set of credentials. See definition of\n \"resourceGroupId\" in clause 9.5.3.3.\n* NOTE 2:\tOnce the connectivity between VNFM and VIM, CISM, CIR or MCIOP repository is provided\n through a secure connection over HTTP Secure (HTTP over SSL/TLS), and the connection might also be\n established through a VPN (for example TLS-based VPN tunnelling) for site-to-site connection, the\n \"accessInfo\" JSON data structure, and the sensitive data related information (\"username\"/\"password\" as\n required properties for authentication purpose), will be transmitted as plain text through a TLS tunnel\n without additional encoding/encryption before transmitting it, making the sensitive data visible to the\n endpoint. The base64 encoded certificates are only used by the VNFM to verify the authenticity of the\n interface endpoint of the VIM, CISM, CIR or MCIOP repository.\n \n* NOTE 3:\t ETSI GS NFV-SOL 009 [i.18] specifies the means to configure into the VNFM applicable VIM connection information via the \"NFV-MANO Configuration and Information Management\" interface. \n* NOTE 4:\t Due to the possibility of configuring such information into the VNFM out-of-band, by means outside the scope of the present document, as well as in-band, by means specified in the present document, care should be taken to avoid unintended conflicts in the VNFM when managing such information.\n",
"type": "object",
"required": ["vimType"],
"properties": {
@@ -351,6 +351,10 @@
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.\n",
+ "type": "string"
}
}
}
@@ -524,6 +528,10 @@
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.\n",
+ "type": "string"
}
}
}
@@ -721,6 +729,10 @@
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.\n",
+ "type": "string"
}
}
}
@@ -1087,6 +1099,10 @@
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.\n",
+ "type": "string"
}
}
}
@@ -1648,6 +1664,10 @@
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.\n",
+ "type": "string"
}
}
}
@@ -1961,7 +1981,7 @@
"mcioType": {
"description": "The type of MCIO. Specific values, their semantics and associated MCIO types are defined in clause 5.5.4.9. Additional values are also permitted. See note 1.\n",
"type": "string",
- "enum": ["Deployment", "Statefulset"]
+ "enum": ["Deployment", "StatefulSet"]
},
"desiredInstances": {
"description": "Number of desired MCIO instances.\n",
diff --git a/SOL003/VNFLifecycleOperationGranting-API/ApiVersion.robot b/SOL003/VNFLifecycleOperationGranting-API/ApiVersion.robot
index 2ce93d54b60756b8078d5f82550759bd05955ab5..98a6c96bcb21e7000da23003130f1af297b26f7c 100644
--- a/SOL003/VNFLifecycleOperationGranting-API/ApiVersion.robot
+++ b/SOL003/VNFLifecycleOperationGranting-API/ApiVersion.robot
@@ -13,7 +13,7 @@ POST API Version - Method not implemented
... Test title: POST API version - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -25,7 +25,7 @@ GET API Version
... Test title: GET API Version
... Test objective: The objective is to test that GET method successfully return ApiVersionInformation
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -38,7 +38,7 @@ PUT API Version - Method not implemented
... Test title: PUT API Version - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -50,7 +50,7 @@ PATCH API Version - Method not implemented
... Test title: PATCH API Version - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -62,7 +62,7 @@ DELETE API Version - Method not implemented
... Test title: DELETE API Version - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -74,7 +74,7 @@ POST API Version with apiMajorVerion - Method not implemented
... Test title: POST API version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -86,7 +86,7 @@ GET API Version with apiMajorVerion
... Test title: GET API Version with apiMajorVerion
... Test objective: The objective is to test that GET method successfully return ApiVersionInformation
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -99,7 +99,7 @@ PUT API Version with apiMajorVerion - Method not implemented
... Test title: PUT API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -111,7 +111,7 @@ PATCH API Version with apiMajorVerion - Method not implemented
... Test title: PATCH API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -123,7 +123,7 @@ DELETE API Version with apiMajorVerion - Method not implemented
... Test title: DELETE API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFLifecycleOperationGranting-API/Grants.robot b/SOL003/VNFLifecycleOperationGranting-API/Grants.robot
index 59bfb2b27280951c7d4f05ff2e48141ccbd68e22..728c14ef9fd314458504b8686363b50455789e94 100644
--- a/SOL003/VNFLifecycleOperationGranting-API/Grants.robot
+++ b/SOL003/VNFLifecycleOperationGranting-API/Grants.robot
@@ -22,7 +22,7 @@ Requests a grant for a particular VNF lifecycle operation - Synchronous mode
... Test title: Requests a grant for a particular VNF lifecycle operation - Synchronous mode
... Test objective: The objective is to request a grant for a particular VNF lifecycle operation and perform a JSON schema validation on the returned grant data structure
... Pre-conditions: none
- ... Reference: Clause 9.4.2.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 9.4.2.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO can decide immediately what to respond to a grant request
... Post-Conditions: The grant information is available to the VNFM.
@@ -36,7 +36,7 @@ Requests a grant for a particular VNF lifecycle operation - Asynchronous mode
... Test title: Requests a grant for a particular VNF lifecycle operation - Asynchronous mode
... Test objective: The objective is to request a grant for a particular VNF lifecycle operation and perform a JSON schema validation on the returned grant data structure
... Pre-conditions: none
- ... Reference: Clause 9.4.2.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 9.4.2.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO can not decide immediately what to respond to a grant request
... Post-Conditions: The grant information is available to the VNFM.
@@ -51,7 +51,7 @@ Requests a grant for a particular VNF lifecycle operation - Forbidden
... Test title: Requests a grant for a particular VNF lifecycle operation - Forbidden
... Test objective: The objective is to request a grant for a particular VNF lifecycle operation and the grant is rejected
... Pre-conditions: none
- ... Reference: Clause 9.4.2.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 9.4.2.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -64,7 +64,7 @@ GET Grants - Method not implemented
... Test title: GET Grants - Method not implemented
... Test objective: The objective is to test that GET method is not allowed for Life cycle operation granting
... Pre-conditions: none
- ... Reference: Clause 9.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 9.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -76,7 +76,7 @@ PUT Grants - Method not implemented
... Test title: PUT Grants - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed for Life cycle operation granting
... Pre-conditions: none
- ... Reference: Clause 9.4.2.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 9.4.2.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -88,7 +88,7 @@ PATCH Grants - Method not implemented
... Test title: PATCH Grants - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed for Life cycle operation granting
... Pre-conditions: none
- ... Reference: Clause 9.4.2.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 9.4.2.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -100,7 +100,7 @@ DELETE Grants - Method not implemented
... Test title: DELETE Grants - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed for Life cycle operation granting
... Pre-conditions: none
- ... Reference: Clause 9.4.2.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 9.4.2.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: resources are not deleted
@@ -112,7 +112,7 @@ Requests a grant for a particular VNF lifecycle operation - Synchronous mode usi
... Test title: Requests a grant for a particular VNF lifecycle operation - Synchronous mode using instantiationLevelId for Target size
... Test objective: The objective is to request a grant for a particular VNF lifecycle operation and perform a JSON schema validation on the returned grant data structure
... Pre-conditions: none
- ... Reference: Clause 9.4.2.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 9.4.2.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO can decide immediately what to respond to a grant request
... Post-Conditions: The grant information is available to the VNFM.
@@ -126,7 +126,7 @@ Requests a grant for a particular VNF lifecycle operation - Synchronous mode usi
... Test title: Requests a grant for a particular VNF lifecycle operation - Synchronous mode using targetScaleLevelInfo for Target size
... Test objective: The objective is to request a grant for a particular VNF lifecycle operation and perform a JSON schema validation on the returned grant data structure
... Pre-conditions: none
- ... Reference: Clause 9.4.2.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 9.4.2.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO can decide immediately what to respond to a grant request
... Post-Conditions: The grant information is available to the VNFM.
@@ -140,7 +140,7 @@ Requests a grant for a particular VNF lifecycle operation - Synchronous mode usi
... Test title: Requests a grant for a particular VNF lifecycle operation - Synchronous mode using with attribute addResources for Target size
... Test objective: The objective is to request a grant for a particular VNF lifecycle operation and perform a JSON schema validation on the returned grant data structure
... Pre-conditions: none
- ... Reference: Clause 9.4.2.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 9.4.2.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO can decide immediately what to respond to a grant request
... Post-Conditions: The grant information is available to the VNFM.
diff --git a/SOL003/VNFLifecycleOperationGranting-API/IndividualGrant.robot b/SOL003/VNFLifecycleOperationGranting-API/IndividualGrant.robot
index 33a06584d049f6093eaaeca89e27f4c6546f7dce..2874ee4282c75c56287ca4dbcb6002b859c521f9 100644
--- a/SOL003/VNFLifecycleOperationGranting-API/IndividualGrant.robot
+++ b/SOL003/VNFLifecycleOperationGranting-API/IndividualGrant.robot
@@ -18,7 +18,7 @@ POST Individual Grant - Method not implemented
... Test title: POST Individual Grant - Method not implemented
... Test objective: The objective is to test that POST method is not allowed for Life cycle operation granting
... Pre-conditions: none
- ... Reference: Clause 9.4.2.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 9.4.2.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -30,7 +30,7 @@ GET an individual grant - Successful
... Test title: GET an individual grant - Successful
... Test objective: The objective is to retrieve a grant for a particular VNF Lifecycle Operation.
... Pre-conditions: The grant information is available to the NFVO
- ... Reference: Clause 9.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 9.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -45,7 +45,7 @@ GET an individual grant - Process ongoing
... Test title: GET an individual grant - Process ongoing
... Test objective: The objective is to retrieve a grant for a particular VNF lifecycle operation when process is ongoing and no grant is available yet.
... Pre-conditions: The process of creating the grant is ongoing, no grant is available yet.
- ... Reference: Clause 9.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 9.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -59,7 +59,7 @@ GET an individual grant - grant rejected
... Test title: GET an individual grant - grant rejected
... Test objective: The objective is to retrieve a grant for a particular VNF Lifecycle Operation but error returned because grant has been rejected.
... Pre-conditions: none
- ... Reference: Clause 9.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 9.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -72,7 +72,7 @@ PUT an individual grant - Method not implemented
... Test title: PUT an individual grant - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to for Life cycle operation granting
... Pre-conditions: none
- ... Reference: Clause 9.4.3.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 9.4.3.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -84,7 +84,7 @@ PATCH an individual grant - Method not implemented
... Test title: PATCH an individual grant - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to for Life cycle operation granting
... Pre-conditions: none
- ... Reference: Clause 9.4.3.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 9.4.3.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -96,7 +96,7 @@ DELETE an individual grant - Method not implemented
... Test title: DELETE an individual grant - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to for Life cycle operation granting
... Pre-conditions: none
- ... Reference: Clause 9.4.3.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 9.4.3.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFLifecycleOperationGranting-API/schemas/grant.schema.json b/SOL003/VNFLifecycleOperationGranting-API/schemas/grant.schema.json
index 17941f08344ef6a88c726c453ef44b29eb70210f..5efcb538b5c5053202d19a8bba7c5b4893de228d 100644
--- a/SOL003/VNFLifecycleOperationGranting-API/schemas/grant.schema.json
+++ b/SOL003/VNFLifecycleOperationGranting-API/schemas/grant.schema.json
@@ -19,7 +19,7 @@
"description": "Provides information regarding VIM and/or CISM connections that are approved to be used by the VNFM to allocate resources and provides parameters of these VIM and/or CISM connections. The VNFM shall update the \"vimConnectionInfo\" attribute of the \"VnfInstance\" structure by adding unknown entries received in this attribute. This attribute is not intended for the modification of VimConnectionInfo entries passed earlier; for that, the VnfInfoModificationRequest structure shall be used. This attribute shall only be supported when\n - all or part of the granted\n resources are managed by\n a VIM and VNF-related\n Resource Management in\n direct mode is applicable.\n - all or part of the granted\n resources are managed by\n a CISM.\nIn direct mode, this parameter shall be absent if the VIM or CISM information was configured to the VNFM in another way, present otherwise. See note 1.\n",
"type": "object",
"additionalProperties": {
- "description": "This type represents parameters to connect to a VIM, a CISM, a CIR or a MCIOP repository for managing the resources of a VNF instance.\nThis structure is used to convey VIM-related, CISM-related, CIR-related, or MCIOP-repository-related parameters over the Or-Vnfm interface. Additional parameters for a VIM, a CISM, a CIR or a MCIOP repository may be configured into the VNFM by means outside the scope of the present document and bound to the identifier of that VIM.\n* NOTE 1:\tIf applicable, this attribute also provides information about the resourceGroupIds\n that are accessible using a particular set of credentials. See definition of\n \"resourceGroupId\" in clause 9.5.3.3.\n* NOTE 2:\tOnce the connectivity between VNFM and VIM, CISM, CIR or MCIOP repository is provided\n through a secure connection over HTTP Secure (HTTP over SSL/TLS), and the connection might also be\n established through a VPN (for example TLS-based VPN tunnelling) for site-to-site connection, the\n \"accessInfo\" JSON data structure, and the sensitive data related information (\"username\"/\"password\" as\n required properties for authentication purpose), will be transmitted as plain text through a TLS tunnel\n without additional encoding/encryption before transmitting it, making the sensitive data visible to the\n endpoint. The base64 encoded certificates are only used by the VNFM to verify the authenticity of the\n interface endpoint of the VIM, CISM, CIR or MCIOP repository.\n",
+ "description": "This type represents parameters to connect to a VIM, a CISM, a CIR or a MCIOP repository for managing the resources of a VNF instance.\nThis structure is used to convey VIM-related, CISM-related, CIR-related, or MCIOP-repository-related parameters over the Or-Vnfm interface. Additional parameters for a VIM, a CISM, a CIR or a MCIOP repository may be configured into the VNFM by means outside the scope of the present document and bound to the identifier of that VIM.\n* NOTE 1:\tIf applicable, this attribute also provides information about the resourceGroupIds\n that are accessible using a particular set of credentials. See definition of\n \"resourceGroupId\" in clause 9.5.3.3.\n* NOTE 2:\tOnce the connectivity between VNFM and VIM, CISM, CIR or MCIOP repository is provided\n through a secure connection over HTTP Secure (HTTP over SSL/TLS), and the connection might also be\n established through a VPN (for example TLS-based VPN tunnelling) for site-to-site connection, the\n \"accessInfo\" JSON data structure, and the sensitive data related information (\"username\"/\"password\" as\n required properties for authentication purpose), will be transmitted as plain text through a TLS tunnel\n without additional encoding/encryption before transmitting it, making the sensitive data visible to the\n endpoint. The base64 encoded certificates are only used by the VNFM to verify the authenticity of the\n interface endpoint of the VIM, CISM, CIR or MCIOP repository.\n* NOTE 3:\t ETSI GS NFV-SOL 009 [i.18] specifies the means to configure into the VNFM applicable VIM connection information via the \"NFV-MANO Configuration and Information Management\" interface. \n* NOTE 4:\t Due to the possibility of configuring such information into the VNFM out-of-band, by means outside the scope of the present document, as well as in-band, by means specified in the present document, care should be taken to avoid unintended conflicts in the VNFM when managing such information.\n",
"type": "object",
"required": ["vimType"],
"properties": {
@@ -803,7 +803,7 @@
"description": "Information about internal VLs that are managed by other entities than the VNFM. See notes 4, 5, 7 and 8.\n",
"type": "array",
"items": {
- "description": "This type represents an externally-managed internal VL.\n* NOTE 1: It is only applicable if the externally-managed VL is realized by a secondary container cluster network. It shall\n not be present otherwise.\n* NOTE 2: A link port is not needed for a VNFC internal connection point connected to a secondary container cluster\n network.\n* NOTE 3: An example of the network attachment definition resource when the container infrastructure service\n management is a Kubernetes® instance is a network attachment definition (NAD).\n",
+ "description": "This type represents an externally-managed internal VL.\n* NOTE 1: It is only applicable if the externally-managed VL is realized by a secondary container cluster network. It shall\n not be present otherwise.\n* NOTE 2: A link port is not needed for a VNFC internal connection point connected to a secondary container cluster\n network.\n* NOTE 3: An example of the network attachment definition resource when the container infrastructure service\n management is a Kubernetes® instance is a Network Attachment Definition (NAD).\n",
"type": "object",
"required": ["id", "vnfVirtualLinkDescId", "resourceId"],
"properties": {
diff --git a/SOL003/VNFPackageManagement-API/ApiVersion.robot b/SOL003/VNFPackageManagement-API/ApiVersion.robot
index ec0708c558de9c21b4c389405a00761021de5772..1e95f9d4c0093725fb90907cb521ba4cf30e3cf0 100644
--- a/SOL003/VNFPackageManagement-API/ApiVersion.robot
+++ b/SOL003/VNFPackageManagement-API/ApiVersion.robot
@@ -13,7 +13,7 @@ POST API Version - Method not implemented
... Test title: POST API version - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -25,7 +25,7 @@ GET API Version
... Test title: GET API Version
... Test objective: The objective is to test that GET method successfully return ApiVersionInformation
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -38,7 +38,7 @@ PUT API Version - Method not implemented
... Test title: PUT API Version - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -50,7 +50,7 @@ PATCH API Version - Method not implemented
... Test title: PATCH API Version - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -62,7 +62,7 @@ DELETE API Version - Method not implemented
... Test title: DELETE API Version - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -74,7 +74,7 @@ POST API Version with apiMajorVerion - Method not implemented
... Test title: POST API version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -86,7 +86,7 @@ GET API Version with apiMajorVerion
... Test title: GET API Version with apiMajorVerion
... Test objective: The objective is to test that GET method successfully return ApiVersionInformation
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -99,7 +99,7 @@ PUT API Version with apiMajorVerion - Method not implemented
... Test title: PUT API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -111,7 +111,7 @@ PATCH API Version with apiMajorVerion - Method not implemented
... Test title: PATCH API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -123,7 +123,7 @@ DELETE API Version with apiMajorVerion - Method not implemented
... Test title: DELETE API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFPackageManagement-API/IndividualSubscription.robot b/SOL003/VNFPackageManagement-API/IndividualSubscription.robot
index 26800b0549048a1ac089fd8fe2e9fbdced8c5276..b7f2dab38cf0e660dd0b916812fdb39329249fa9 100644
--- a/SOL003/VNFPackageManagement-API/IndividualSubscription.robot
+++ b/SOL003/VNFPackageManagement-API/IndividualSubscription.robot
@@ -12,7 +12,7 @@ GET Individual VNF Package Subscription
... Test title: GET Individual VNF Package Subscription
... Test objective: The objective is to test the retrieval of individual VNF package subscription and perform a JSON schema and content validation of the returned subscription data structure
... Pre-conditions: At least one VNF package subscription is available in the NFVO.
- ... Reference: Clause 10.4.8.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.8.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -27,7 +27,7 @@ GET Individual VNF Package Subscription with invalid resource identifier
... Test title: GET Individual VNF Package Subscription with invalid resource identifier
... Test objective: The objective is to test that the retrieval of an individual VNF package subscription fails when using an invalid resource identifier
... Pre-conditions: At least one VNF package subscription is available in the NFVO.
- ... Reference: Clause 10.4.8.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.8.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -39,7 +39,7 @@ DELETE Individual VNF Package Subscription with invalid resource identifier
... Test title: DELETE Individual VNF Package Subscription with invalid resource identifier
... Test objective: The objective is to test that the deletion of an individual VNF package subscription fails when using an invalid resource identifier
... Pre-conditions: At least one VNF package subscription is available in the NFVO.
- ... Reference: Clause 10.4.8.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.8.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -51,7 +51,7 @@ POST Individual VNF Package Subscription - Method not implemented
... Test title: POST Individual VNF Package Subscription - Method not implemented
... Test objective: The objective is to test that POST method is not allowed to create a new VNF Package Subscription
... Pre-conditions: none
- ... Reference: Clause 10.4.8.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.8.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -63,7 +63,7 @@ PUT Individual VNF Package Subscription - Method not implemented
... Test title: PUT Individual VNF Package Subscription - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to update an existing VNF Package subscription
... Pre-conditions: At least one VNF package subscription is available in the NFVO.
- ... Reference: Clause 10.4.8.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.8.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -75,7 +75,7 @@ PATCH Individual VNF Package Subscription - Method not implemented
... Test title: PATCH Individual VNF Package Subscription - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to modify an existing VNF Package subscription
... Pre-conditions: At least one VNF package subscription is available in the NFVO.
- ... Reference: Clause 10.4.8.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.8.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -87,7 +87,7 @@ DELETE Individual VNF Package Subscription
... Test title: DELETE Individual VNF Package Subscription
... Test objective: The objective is to test the deletion of an individual VNF package subscription
... Pre-conditions: At least one VNF package subscription is available in the NFVO.
- ... Reference: Clause 10.4.8.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.8.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: The VNF Package Subscription is not available anymore in the NFVO
diff --git a/SOL003/VNFPackageManagement-API/IndividualVNFPackage.robot b/SOL003/VNFPackageManagement-API/IndividualVNFPackage.robot
index 6dd91307982b0baba096079225f07ac0d6187baa..2e49d3afcaf9291c81d12e1f68a94d49f5f3931e 100644
--- a/SOL003/VNFPackageManagement-API/IndividualVNFPackage.robot
+++ b/SOL003/VNFPackageManagement-API/IndividualVNFPackage.robot
@@ -12,7 +12,7 @@ GET Individual VNF Package
... Test title: GET Individual VNF Package
... Test objective: The objective is to test the retrieval of an individual VNF package information perform a JSON schema validation of the collected data structure
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -27,7 +27,7 @@ GET Individual VNF Package with invalid resource identifier
... Test title: GET Individual VNF Package with invalid resource identifier
... Test objective: The objective is to test that the retrieval of an individual VNF package fails when using an invalid resource identifier
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -40,7 +40,7 @@ POST Individual VNF Package - Method not implemented
... Test title: POST Individual VNF Package - Method not implemented
... Test objective: The objective is to test that POST method is not allowed to create new VNF Package
... Pre-conditions: none
- ... Reference: Clause 10.4.3.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.3.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -52,7 +52,7 @@ PUT Individual VNF Package - Method not implemented
... Test title: PUT Individual VNF Package - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to modify a VNF Package
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.3.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.3.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -64,7 +64,7 @@ PATCH Individual VNF Package - Method not implemented
... Test title: PATCH Individual VNF Package - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update a VNF Package
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.3.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.3.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -76,7 +76,7 @@ DELETE Individual VNF Package - Method not implemented
... Test title: DELETE Individual VNF Package - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to delete a VNF Package
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.3.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.3.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -88,7 +88,7 @@ GET Individual OnBoarded VNF Package
... Test title: GET Individual OnBoarded VNF Package
... Test objective: The objective is to test the retrieval of an individual OnBoarded VNF package information perform a JSON schema validation of the collected data structure
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -102,7 +102,7 @@ GET Individual OnBoarded VNF Package with invalid resource identifier
... Test title: GET Individual OnBoarded VNF Package with invalid resource identifier
... Test objective: The objective is to test that the retrieval of an individual OnBoarded VNF package fails when using an invalid resource identifier
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -115,7 +115,7 @@ POST Individual OnBoarded VNF Package - Method not implemented
... Test title: POST Individual OnBoarded VNF Package - Method not implemented
... Test objective: The objective is to test that POST method is not allowed to create new OnBoarded VNF Package
... Pre-conditions: none
- ... Reference: Clause 10.4.3.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.3.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -127,7 +127,7 @@ PUT Individual OnBoarded VNF Package - Method not implemented
... Test title: PUT Individual OnBoarded VNF Package - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to modify a VNF Package
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.3.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.3.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -139,7 +139,7 @@ PATCH Individual OnBoarded VNF Package - Method not implemented
... Test title: PATCH Individual OnBoarded VNF Package - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update a VNF Package
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.3.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.3.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -151,7 +151,7 @@ DELETE Individual OnBoarded VNF Package - Method not implemented
... Test title: DELETE Individual OnBoarded VNF Package - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to delete a VNF Package
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.3.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.3.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFPackageManagement-API/IndividualVNFPackageArtifacts.robot b/SOL003/VNFPackageManagement-API/IndividualVNFPackageArtifacts.robot
index f67249059144aba6069186961601276d9303b75a..f9b79963ab13a1802bc4482d507d40618f6025c5 100644
--- a/SOL003/VNFPackageManagement-API/IndividualVNFPackageArtifacts.robot
+++ b/SOL003/VNFPackageManagement-API/IndividualVNFPackageArtifacts.robot
@@ -11,7 +11,7 @@ GET Individual VNF Package Artifact
... Test title: GET Individual VNF Package Artifact
... Test objective: The objective is to test the retrieval of an individual VNF package artifact
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -23,7 +23,7 @@ GET Individual VNF Package Artifact in octet stream format
... Test title: GET Individual VNF Package Artifact in octet stream format
... Test objective: The objective is to test the retrieval of an individual VNF package artifact when the NFVO cannot determine the artifact content type. The test performs a validation that the returned artifcat in is octet-stream format
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO cannot determine the content type of the artifact
... Post-Conditions: none
@@ -36,7 +36,7 @@ GET Individual VNF Package Artifact with Range Request and NFVO supporting Range
... Test title: GET Individual VNF Package Artifact with Range Request and NFVO supporting Range Requests
... Test objective: The objective is to test the retrieval of an individual VNF package artifact when using a range request to return single range of bytes from the file, with the NFVO supporting it. The test also perform a validation that returned content matches the issued range
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO supports range requests to return single range of bytes from the VNF package artifact
... Post-Conditions: none
@@ -50,7 +50,7 @@ GET Individual VNF Package Artifact with Range Request and NFVO not supporting R
... Test title: GET Individual VNF Package Artifact with Range Request and NFVO not supporting Range Requests
... Test objective: The objective is to test that the retrieval of an individual VNF package artifact, when using a range request to return single range of bytes from the file and the NFVO not supporting it, returns the full VNF Package artifact.
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO does not support range requests to return single range of bytes from the VNF package artifact
... Post-Conditions: none
@@ -62,7 +62,7 @@ GET Individual VNF Package Artifact with invalid Range Request
... Test title: GET Individual VNF Package Artifact with invalid Range Request
... Test objective: The objective is to test that the retrieval of an individual VNF package artifact fails when using a range request that does not match any available byte range in the file.
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO supports range requests to return single range of bytes from the VNF package artifact
... Post-Conditions: none
@@ -74,7 +74,7 @@ GET Individual VNF Package Artifact with invalid resource identifier
... Test title: GET Individual VNF Package Artifact with invalid resource identifier
... Test objective: The objective is to test that the retrieval of an individual VNF package artifact fails when using an invalid resource identifier
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -87,7 +87,7 @@ GET Individual VNF Package Artifact with conflict due to onboarding state
... Test title: GET Individual VNF Package Artifact with conflict due to onboarding state
... Test objective: The objective is to test that the retrieval of an individual VNF package artifact fails due to a conflict when the VNF Package is not in onboarding state ONBOARDED in the NFVO. The test also performs a validation of the JSON schema validation of the failed operation HTTP response
... Pre-conditions: The onboarding state of the VNF package for which the content is requested is different from ONBOARDED.
- ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -100,7 +100,7 @@ POST Individual VNF Package Artifact - Method not implemented
... Test title: POST Individual VNF Package Artifact - Method not implemented
... Test objective: The objective is to test that POST method is not allowed to create new VNF Package artifact
... Pre-conditions: none
- ... Reference: Clause 10.4.6.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.6.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -112,7 +112,7 @@ PUT Individual VNF Package Artifact - Method not implemented
... Test title: PUT Individual VNF Package Artifact - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to modify a VNF Package artifact
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.6.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.6.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -124,7 +124,7 @@ PATCH Individual VNF Package Artifact - Method not implemented
... Test title: PATCH Individual VNF Package Artifact - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update a VNF Package artifact
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.6.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.6.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -136,7 +136,7 @@ DELETE Individual VNF Package Artifact - Method not implemented
... Test title: DELETE Individual VNF Package Artifact - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to delete a VNF Package artifact
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.6.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.6.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -148,7 +148,7 @@ GET Individual OnBoarded VNF Package Artifact
... Test title: GET Individual OnBoarded VNF Package Artifact
... Test objective: The objective is to test the retrieval of an individual OnBoarded VNF package artifact
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -160,7 +160,7 @@ GET Individual OnBoarded VNF Package Artifact in octet stream format
... Test title: GET Individual OnBoarded VNF Package Artifact in octet stream format
... Test objective: The objective is to test the retrieval of an individual OnBoarded VNF package artifact when the NFVO cannot determine the artifact content type. The test performs a validation that the returned artifcat in is octet-stream format
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO cannot determine the content type of the artifact
... Post-Conditions: none
@@ -173,7 +173,7 @@ GET Individual OnBoarded VNF Package Artifact with Range Request and NFVO suppor
... Test title: GET Individual OnBoarded VNF Package Artifact with Range Request and NFVO supporting Range Requests
... Test objective: The objective is to test the retrieval of an individual OnBoarded VNF package artifact when using a range request to return single range of bytes from the file, with the NFVO supporting it. The test also perform a validation that returned content matches the issued range
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO supports range requests to return single range of bytes from the VNF package artifact
... Post-Conditions: none
@@ -187,7 +187,7 @@ GET Individual OnBoarded VNF Package Artifact with Range Request and NFVO not su
... Test title: GET Individual OnBoarded VNF Package Artifact with Range Request and NFVO not supporting Range Requests
... Test objective: The objective is to test that the retrieval of an individual OnBoarded VNF package artifact, when using a range request to return single range of bytes from the file and the NFVO not supporting it, returns the full VNF Package artifact.
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO does not support range requests to return single range of bytes from the VNF package artifact
... Post-Conditions: none
@@ -199,7 +199,7 @@ GET Individual OnBoarded VNF Package Artifact with invalid Range Request
... Test title: GET Individual OnBoarded VNF Package Artifact with invalid Range Request
... Test objective: The objective is to test that the retrieval of an individual OnBoarded VNF package artifact fails when using a range request that does not match any available byte range in the file.
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO supports range requests to return single range of bytes from the VNF package artifact
... Post-Conditions: none
@@ -211,7 +211,7 @@ GET Individual OnBoarded VNF Package Artifact with invalid resource identifier
... Test title: GET Individual OnBoarded VNF Package Artifact with invalid resource identifier
... Test objective: The objective is to test that the retrieval of an individual OnBoarded VNF package artifact fails when using an invalid resource identifier
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -224,7 +224,7 @@ GET Individual OnBoarded VNF Package Artifact with conflict due to onboarding st
... Test title: GET Individual OnBoarded VNF Package Artifact with conflict due to onboarding state
... Test objective: The objective is to test that the retrieval of an individual OnBoarded VNF package artifact fails due to a conflict when the VNF Package is not in onboarding state ONBOARDED in the NFVO. The test also performs a validation of the JSON schema validation of the failed operation HTTP response
... Pre-conditions: The onboarding state of the VNF package for which the content is requested is different from ONBOARDED.
- ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -237,7 +237,7 @@ POST Individual OnBoarded VNF Package Artifact - Method not implemented
... Test title: POST Individual OnBoarded VNF Package Artifact - Method not implemented
... Test objective: The objective is to test that POST method is not allowed to create new VNF Package artifact
... Pre-conditions: none
- ... Reference: Clause 10.4.6.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.6.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -249,7 +249,7 @@ PUT Individual OnBoarded VNF Package Artifact - Method not implemented
... Test title: PUT Individual OnBoarded VNF Package Artifact - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to modify a VNF Package artifact
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.6.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.6.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -261,7 +261,7 @@ PATCH Individual OnBoarded VNF Package Artifact - Method not implemented
... Test title: PATCH Individual OnBoarded VNF Package Artifact - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update a VNF Package artifact
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.6.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.6.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -273,7 +273,7 @@ DELETE Individual OnBoarded VNF Package Artifact - Method not implemented
... Test title: DELETE Individual OnBoarded VNF Package Artifact - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to delete a VNF Package artifact
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.6.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.6.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -285,7 +285,7 @@ GET Individual VNF Package Artifact with security information
... Test title: GET Individual VNF Package Artifact with security information
... Test objective: The objective is to test the retrieval of an individual VNF package artifact shall include in the ZIP archive the security information when requested with "include_signature" parameter
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO cannot determine the content type of the artifact
... Post-Conditions: none
@@ -298,7 +298,7 @@ GET Individual OnBoarded VNF Package Artifact with security information
... Test title: GET Individual OnBoarded VNF Package Artifact with security information
... Test objective: The objective is to test the retrieval of an individual OnBoarded VNF package artifact shall include in the ZIP archive the security information when requested with "include_signature" parameter
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO cannot determine the content type of the artifact
... Post-Conditions: none
@@ -311,7 +311,7 @@ GET Individual VNF Package Artifact with encrypted artifact
... Test title: GET Individual VNF Package Artifact with encrypted artifact
... Test objective: The objective is to test the retrieval of an individual VNF package artifact shall include an encrypted artifact
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO cannot determine the content type of the artifact
... Post-Conditions: none
@@ -324,7 +324,7 @@ GET Individual OnBoarded VNF Package Artifact with encrypted artifact
... Test title: GET Individual OnBoarded VNF Package Artifact with encrypted artifact
... Test objective: The objective is to test the retrieval of an individual OnBoarded VNF package artifact shall include an encrypted artifact
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO cannot determine the content type of the artifact
... Post-Conditions: none
@@ -337,7 +337,7 @@ GET Individual VNF Package Artifact - Not Acceptable
... Test title: GET Individual VNF Package Artifact with invalid Range Request
... Test objective: The objective is to test that the retrieval of an individual VNF package artifact fails when related request contained an "Accept" header not compatible with the Content type "application/zip" but the "include_signatures" flag was provided
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -350,7 +350,7 @@ GET Individual OnBoarded VNF Package Artifact - Not Acceptable
... Test title: GET Individual OnBoarded VNF Package Artifact with invalid Range Request
... Test objective: The objective is to test that the retrieval of an individual OnBoarded VNF package artifact fails when related request contained an "Accept" header not compatible with the Content type "application/zip" but the "include_signatures" flag was provided
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFPackageManagement-API/ManifestInIndividualVNFPackage.robot b/SOL003/VNFPackageManagement-API/ManifestInIndividualVNFPackage.robot
index b6e1b9a4a0f49273584e571f73a216f796527242..8a0ce02dfdbba4f077c417f7dea4bd876ac58276 100644
--- a/SOL003/VNFPackageManagement-API/ManifestInIndividualVNFPackage.robot
+++ b/SOL003/VNFPackageManagement-API/ManifestInIndividualVNFPackage.robot
@@ -11,7 +11,7 @@ Get Manifest in Individual VNF Package
... Test title: Get Manifest in Individual VNF Package
... Test objective: The objective is to test that the Get request read the content of manifest within a NVF Package and perform a validation that returned content is in plain text format
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.4a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.4a.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -24,7 +24,7 @@ Get Manifest in Individual VNF Package with security information
... Test title: Get Manifest in Individual VNF Package with security information
... Test objective: The objective is to test the retrieval of manifest for an individual VNF package shall also security certificates when requested with "include_signature" parameter, and perform a validation that returned content is in Zip format
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.4a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.4a.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -37,7 +37,7 @@ Get Manifest in Individual VNF Package - Not acceptable
... Test title: Get Manifest in Individual VNF Package - Not acceptable
... Test objective: The objective is to test that retriveal of the of manifest for an individual VNF package fails when request contained an "Accept" header not compatible with the Content type "application/zip" but the "include_signatures" flag was provided, and perform a validation of the JSON schema validation of the failed operation HTTP response
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.4a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.4a.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -50,7 +50,7 @@ Get Manifest in Individual VNF Package - Conflict
... Test title: Get Manifest in Individual VNF Package - Conflict
... Test objective: The objective is to test that the retrieval of the manifest for an individual VNF package fails due to a conflict when the VNF Package is not in onboarding state ONBOARDED in the NFVO. The test also performs a validation of the JSON schema validation of the failed operation HTTP response
... Pre-conditions: The onboarding state of the VNF package for which the VNFD is requested is different from ONBOARDED.
- ... Reference: Clause 10.4.4a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.4a.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -63,7 +63,7 @@ POST Manifest in Individual VNF Package - Method not implemented
... Test title: POST Manifest in Individual VNF Package - Method not implemented
... Test objective: The objective is to test that POST method is not allowed to create new resource
... Pre-conditions: none
- ... Reference: Clause 10.4.4a.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.4a.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -75,7 +75,7 @@ PUT Manifest in Individual VNF Package - Method not implemented
... Test title: PUT Manifest in Individual VNF Package - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to modify resource
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.4a.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.4a.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -87,7 +87,7 @@ PATCH Manifest in Individual VNF Package - Method not implemented
... Test title: PATCH Manifest in Individual VNF Package - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update resource
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.4a.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.4a.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -99,7 +99,7 @@ DELETE Manifest in Individual VNF Package - Method not implemented
... Test title: DELETE Manifest in Individual VNF Package - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to delete resource
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.4a.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.4a.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: Resource is not deleted by the failed operation
@@ -112,7 +112,7 @@ Get Manifest in Individual OnBoarded VNF Package
... Test title: Get Manifest in Individual OnBoarded VNF Package
... Test objective: The objective is to test that the Get request read the content of manifest within a OnBoarded NVF Package and perform a validation that returned content is in plain text format
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.4a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.4a.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -125,7 +125,7 @@ Get Manifest in Individual OnBoarded VNF Package with security information
... Test title: Get Manifest in Individual OnBoarded VNF Package with security information
... Test objective: The objective is to test the retrieval of manifest for an individual OnBoarded VNF package shall also security certificates when requested with "include_signature" parameter, and perform a validation that returned content is in Zip format
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.4a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.4a.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -138,7 +138,7 @@ Get Manifest in Individual OnBoarded VNF Package - Not acceptable
... Test title: Get Manifest in Individual OnBoarded VNF Package - Not acceptable
... Test objective: The objective is to test that retriveal of the of manifest for an individual OnBoarded VNF package fails when request contained an "Accept" header not compatible with the Content type "application/zip" but the "include_signatures" flag was provided, and perform a validation of the JSON schema validation of the failed operation HTTP response
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.4a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.4a.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -151,7 +151,7 @@ Get Manifest in Individual OnBoarded VNF Package - Conflict
... Test title: Get Manifest in Individual OnBoarded VNF Package - Conflict
... Test objective: The objective is to test that the retrieval of the manifest for an individual OnBoarded VNF package fails due to a conflict when the VNF Package is not in onboarding state ONBOARDED in the NFVO. The test also performs a validation of the JSON schema validation of the failed operation HTTP response
... Pre-conditions: The onboarding state of the VNF package for which the VNFD is requested is different from ONBOARDED.
- ... Reference: Clause 10.4.4a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.4a.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -164,7 +164,7 @@ POST Manifest in Individual OnBoarded VNF Package - Method not implemented
... Test title: POST Manifest in Individual OnBoarded VNF Package - Method not implemented
... Test objective: The objective is to test that POST method is not allowed to create new resource
... Pre-conditions: none
- ... Reference: Clause 10.4.4a.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.4a.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -176,7 +176,7 @@ PUT Manifest in Individual OnBoarded VNF Package - Method not implemented
... Test title: PUT Manifest in Individual OnBoarded VNF Package - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to modify resource
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.4a.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.4a.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -188,7 +188,7 @@ PATCH Manifest in Individual OnBoarded VNF Package - Method not implemented
... Test title: PATCH Manifest in Individual OnBoarded VNF Package - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update resource
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.4a.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.4a.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -200,7 +200,7 @@ DELETE Manifest in Individual OnBoarded VNF Package - Method not implemented
... Test title: DELETE Manifest in Individual OnBoarded VNF Package - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to delete resource
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.4a.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.4a.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: Resource is not deleted by the failed operation
diff --git a/SOL003/VNFPackageManagement-API/NotificationEndpoint.robot b/SOL003/VNFPackageManagement-API/NotificationEndpoint.robot
index 9a63cc72427915f79bf9f48468e75fae38e38098..b67da1c0cd872b87d5d1cabdb8b315fd7a9e37aa 100644
--- a/SOL003/VNFPackageManagement-API/NotificationEndpoint.robot
+++ b/SOL003/VNFPackageManagement-API/NotificationEndpoint.robot
@@ -13,7 +13,7 @@ VNF Package Onboarding Notification
... Test title: VNF Package Onboarding Notification
... Test objective: The objective is to test that the POST request triggers VNF Package Onboarding notification.
... Pre-conditions: A VNF package subscription for onboarding notifications is available in the NFVO.
- ... Reference: Clause 10.4.9.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.9.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
@@ -25,7 +25,7 @@ VNF Package Change Notification
... Test title: VNF Package Change Notification
... Test objective: The objective is to test that the POST request triggers VNF Package Change notification.
... Pre-conditions: A VNF package subscription for change notifications is available in the NFVO.
- ... Reference: Clause 10.4.9.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.9.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFPackageManagement-API/Notifications.robot b/SOL003/VNFPackageManagement-API/Notifications.robot
index 4310c5a550c65ef3d41ff1d6adde60ec5e18e5a8..ace680f433a198ba2ba35d3660d940b671e94420 100644
--- a/SOL003/VNFPackageManagement-API/Notifications.robot
+++ b/SOL003/VNFPackageManagement-API/Notifications.robot
@@ -16,7 +16,7 @@ VNF Package Onboarding Notification
... Test title: VNF Package Onboarding Notification
... Test objective: The objective is to test the dispatch of VNF Package Onboarding notification when the VNF package onboarding operation is successfully completed, and perform a JSON schema and content validation of the delivered notification. The action that triggers the notification under test is an explicit test step, but it is not performed by the test system.
... Pre-conditions: A VNF package subscription for onboarding notifications is available in the NFVO.
- ... Reference: Clause 10.4.9.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.9.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -29,7 +29,7 @@ VNF Package Operational State Change Notification
... Test title: VNF Package Operational State Change Notification
... Test objective: The objective is to test the dispatch of VNF Package Change notification when the VNF package operational state is modified, and perform a JSON schema and content validation of the delivered notification. The action that triggers the notification under test is an explicit test step, but it is not performed by the test system.
... Pre-conditions: A VNF package subscription for change notifications is available in the NFVO.
- ... Reference: Clause 10.4.9.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.9.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -43,7 +43,7 @@ VNF Package Deletion Notification
... Test title: VNF Package Deletion Notification
... Test objective: The objective is to test the dispatch of VNF Package Change notification when the VNF package is deleted on the NFVO, and perform a JSON schema and content validation of the delivered notification. The action that triggers the notification under test is an explicit test step, but it is not performed by the test system.
... Pre-conditions: A VNF package subscription for change notifications is available in the NFVO.
- ... Reference: Clause 10.4.9.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.9.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFPackageManagement-API/Subscriptions.robot b/SOL003/VNFPackageManagement-API/Subscriptions.robot
index ae8a0c6f45e5f8efa8392fd383f37c7e5dd76408..f535764d36815dee751d06426ce1e3172d6dc69a 100644
--- a/SOL003/VNFPackageManagement-API/Subscriptions.robot
+++ b/SOL003/VNFPackageManagement-API/Subscriptions.robot
@@ -16,7 +16,7 @@ Get All VNF Package Subscriptions
... Test title: GET all VNF Package Subscriptions
... Test objective: The objective is to test the retrieval of all VNF package subscriptions and perform a JSON schema validation of the returned subscriptions data structure
... Pre-conditions: At least one VNF package subscription is available in the NFVO.
- ... Reference: Clause 10.4.7.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.7.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -29,7 +29,7 @@ Get VNF Package Subscriptions with attribute-based filter
... Test title: Get VNF Package Subscriptions with attribute-based filter
... Test objective: The objective is to test the retrieval of VNF package subscriptions using attribute-based filter, perform a JSON schema validation of the collected data structure, and verify that the retrieved information matches the issued attribute-based filters
... Pre-conditions: At least one VNF package subscription is available in the NFVO.
- ... Reference: Clause 10.4.7.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.7.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -43,7 +43,7 @@ Get VNF Package Subscriptions with invalid attribute-based filter
... Test title: Get VNF Package Subscriptions with attribute-based filters
... Test objective: The objective is to test that the retrieval of VNF package subscriptions fails when using invalid attribute-based filters, and perform the JSON schema validation of the failed operation HTTP response.
... Pre-conditions: At least one VNF package subscription is available in the NFVO.
- ... Reference: Clause 10.4.7.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.7.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -56,7 +56,7 @@ GET VNF Package Subscription with invalid resource endpoint
... Test title: GET VNF Package Subscription with invalid resource endpoint
... Test objective: The objective is to test that the retrieval of all VNF package subscriptions fails when using invalid resource endpoint.
... Pre-conditions: At least one VNF package subscription is available in the NFVO.
- ... Reference: Clause 10.4.7.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.7.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -69,7 +69,7 @@ Create new VNF Package subscription
... Test title: Create new VNF Package subscription
... Test objective: The objective is to test the creation of a new VNF package subscription and perform a JSON schema and content validation of the returned subscription data structure
... Pre-conditions: none
- ... Reference: Clause 10.4.7.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.7.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: The VNF package subscription is successfully set and it matches the issued subscription
@@ -86,7 +86,7 @@ Create duplicated VNF Package subscription with NFVO not creating duplicated sub
... Test title: Create duplicated VNF Package subscription with NFVO not creating duplicated subscriptions
... Test objective: The objective is to test the attempt of a creation of a duplicated VNF package subscription and check that no new subscription is created by the NFVO and a link to the original subscription is returned
... Pre-conditions: At least one VNF package subscription is available in the NFVO.
- ... Reference: Clause 10.4.7.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.7.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO does not support the creation of duplicated subscriptions
... Post-Conditions: The existing VNF package subscription returned is available in the NFVO
@@ -102,7 +102,7 @@ Create duplicated VNF Package subscription with NFVO creating duplicated subscri
... Test title: Create duplicated VNF Package subscription with NFVO creating duplicated subscriptions
... Test objective: The objective is to test the creation of a duplicated VNF package subscription and perform a JSON schema and content validation of the returned duplicated subscription data structure
... Pre-conditions: At least one VNF package subscription is available in the NFVO.
- ... Reference: Clause 10.4.7.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.7.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO supports the creation of duplicated subscriptions
... Post-Conditions: The duplicated VNF package subscription is successfully set and it matches the issued subscription
@@ -117,7 +117,7 @@ PUT VNF Package Subscriptions - Method not implemented
... Test title: PUT VNF Package Subscriptions - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to modify VNF package subscriptions
... Pre-conditions: At least one VNF package subscription is available in the NFVO.
- ... Reference: Clause 10.4.7.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.7.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -129,7 +129,7 @@ PATCH VNF Package Subscriptions - Method not implemented
... Test title: PATCH VNF Package Subscriptions - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update VNF package subscriptions
... Pre-conditions: At least one VNF package subscription is available in the NFVO.
- ... Reference: Clause 10.4.7.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.7.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -141,7 +141,7 @@ DELETE VNF Package Subscriptions - Method not implemented
... Test title: DELETE VNF Package Subscriptions - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to delete VNF package subscriptions
... Pre-conditions: At least one VNF package subscription is available in the NFVO.
- ... Reference: Clause 10.4.7.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.7.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -153,7 +153,7 @@ Get All VNF Package Subscriptions as Paged Response
... Test title: GET all VNF Package Subscriptions as Paged Response
... Test objective: The objective is to test the retrieval of all VNF package subscriptions as Paged Response.
... Pre-conditions: At least one VNF package subscription is available in the NFVO.
- ... Reference: Clause 10.4.7.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.7.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The VNFM supports response paging for the subscription resources
... Post-Conditions: none
@@ -166,7 +166,7 @@ GET All VNF Package Subscriptions as a Paged Response with nextpage_opauque_mark
... Test title: GET All VNF Package Subscriptions as a Paged Response with nextpage_opauque_marker parameter
... Test objective: The objective is to query information about all VNF package subscriptions as a Paged Response and retrieve the next page using the nextpage_opaque_marker parameter
... Pre-conditions: A request for retrieving all VNF package subscriptions as a paged response has been successfully issued (Test ID 7.3.3.6.11)
- ... Reference: Clause 10.4.7.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.7.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The VNFM supports response paging for the subscription resources
... Post-Conditions: none
@@ -178,7 +178,7 @@ Get VNF Package Subscriptions - Bad Request Response too Big
... Test title: Get VNF Package Subscriptions - Bad Request Response too Big
... Test objective: The objective is to test that the retrieval of VNF package subscriptions fails because reponse is too big, and perform the JSON schema validation of the failed operation HTTP response.
... Pre-conditions: At least one VNF package subscription is available in the NFVO.
- ... Reference: Clause 10.4.7.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.7.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -186,12 +186,12 @@ Get VNF Package Subscriptions - Bad Request Response too Big
Check HTTP Response Status Code Is 400
Check HTTP Response Body Json Schema Is ProblemDetails
-Get VNF Package Subscriptions - Unprocessable Entity
+Get VNF Package Subscriptions - Unprocessable Content
[Documentation] Test ID: 7.3.3.6.13
- ... Test title: Get VNF Package Subscriptions - Unprocessable Entity
- ... Test objective: The objective is to test that 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., and perform the JSON schema validation of the failed operation HTTP response.
+ ... Test title: Get VNF Package Subscriptions - Unprocessable Content
+ ... Test objective: The objective is to test that content type of the message content is supported and the message content of a request contains syntactically correct data but the data cannot be processed., and perform the JSON schema validation of the failed operation HTTP response.
... Pre-conditions: At least one VNF package subscription is available in the NFVO.
- ... Reference: Clause 10.4.7.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.7.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFPackageManagement-API/VNFDInIndividualVNFPackage.robot b/SOL003/VNFPackageManagement-API/VNFDInIndividualVNFPackage.robot
index c7256b1a1a18efd9a57e0cf5b52f124c8fdaff93..10a6003b8a1188349748a1692346cb38d14cceeb 100644
--- a/SOL003/VNFPackageManagement-API/VNFDInIndividualVNFPackage.robot
+++ b/SOL003/VNFPackageManagement-API/VNFDInIndividualVNFPackage.robot
@@ -11,7 +11,7 @@ Get single file VNFD in Individual VNF Package in Plain Format
... Test title: Get single file VNFD in Individual VNF Package in Plain Format
... Test objective: The objective is to test the retrieval of the VNFD in plain format for an individual VNF package and perform a validation that returned content is in plain format
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The VNFD is implemented as a single file
... Post-Conditions: none
@@ -24,7 +24,7 @@ Get VNFD in Individual VNF Package in Zip Format
... Test title: Get VNFD in Individual VNF Package in Zip Format
... Test objective: The objective is to test the retrieval of the VNFD in zip format for an individual VNF package and perform a validation that returned content is in zip format
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -37,7 +37,7 @@ Get single file VNFD in Individual VNF Package in Plain or Zip Format
... Test title: Get single file VNFD in Individual VNF Package in Plain or Zip Format
... Test objective: The objective is to test the retrieval of the single file VNFD for an individual VNF package when requesting Plain or Zip format to NFVO by including both formats in the request, and perform a validation that returned content is in Plain or Zip format
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The VNFD is implemented as a single file
... Post-Conditions: none
@@ -50,7 +50,7 @@ Get multi file VNFD in Individual VNF Package in Plain or Zip Format
... Test title: Get multi file VNFD in Individual VNF Package in Plain or Zip Format
... Test objective: The objective is to test the retrieval of the multi file VNFD for an individual VNF package when requesting Plain or Zip format to NFVO by including both formats in the request, and perform a validation that returned content is in Zip format
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The VNFD is implemented as a multi file
... Post-Conditions: none
@@ -74,7 +74,7 @@ Get VNFD in Individual VNF Package with invalid resource identifier
... Test title: Get VNFD in Individual VNF Package with invalid resource identifier
... Test objective: The objective is to test that the retrieval of the VNFD for an individual VNF package content fails when using an invalid resource identifier
... Pre-conditions: none
- ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -86,7 +86,7 @@ Get VNFD in Individual VNF Package Content with conflict due to onboarding state
... Test title: Get VNFD in Individual VNF Package Content with conflict due to onboarding state
... Test objective: The objective is to test that the retrieval of the VNFD for an individual VNF package content fails due to a conflict when the VNF Package is not in onboarding state ONBOARDED in the NFVO. The test also performs a validation of the JSON schema validation of the failed operation HTTP response
... Pre-conditions: The onboarding state of the VNF package for which the VNFD is requested is different from ONBOARDED.
- ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -99,7 +99,7 @@ POST VNFD in Individual VNF Package Content - Method not implemented
... Test title: POST VNFD in Individual VNF Package Content - Method not implemented
... Test objective: The objective is to test that POST method is not allowed to create new VNFD
... Pre-conditions: none
- ... Reference: Clause 10.4.4.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.4.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -111,7 +111,7 @@ PUT VNFD in Individual VNF Package Content - Method not implemented
... Test title: PUT VNFD in Individual VNF Package Content - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to modify a VNFD
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.4.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.4.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -123,7 +123,7 @@ PATCH VNFD in Individual VNF Package Content - Method not implemented
... Test title: PATCH VNFD in Individual VNF Package Content - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update a VNFD
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.4.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.4.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -135,7 +135,7 @@ DELETE VNFD in Individual VNF Package Content - Method not implemented
... Test title: DELETE VNFD in Individual VNF Package Content - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to delete a VNFD
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.4.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.4.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -147,7 +147,7 @@ Get single file VNFD in Individual OnBoarded VNF Package in Plain Format
... Test title: Get single file VNFD in Individual OnBoarded VNF Package in Plain Format
... Test objective: The objective is to test the retrieval of the VNFD in plain format for an individual OnBoarded VNF package and perform a validation that returned content is in plain format
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The VNFD is implemented as a single file
... Post-Conditions: none
@@ -160,7 +160,7 @@ Get VNFD in Individual OnBoarded VNF Package in Zip Format
... Test title: Get VNFD in Individual OnBoarded VNF Package in Zip Format
... Test objective: The objective is to test the retrieval of the VNFD in zip format for an individual OnBoarded VNF package and perform a validation that returned content is in zip format
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -173,7 +173,7 @@ Get single file VNFD in Individual OnBoarded VNF Package in Plain or Zip Format
... Test title: Get single file VNFD in Individual OnBoarded VNF Package in Plain or Zip Format
... Test objective: The objective is to test the retrieval of the single file VNFD for an individual OnBoarded VNF package when requesting Plain or Zip format to NFVO by including both formats in the request, and perform a validation that returned content is in Plain or Zip format
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The VNFD is implemented as a single file
... Post-Conditions: none
@@ -186,7 +186,7 @@ Get multi file VNFD in Individual OnBoarded VNF Package in Plain or Zip Format
... Test title: Get multi file VNFD in Individual OnBoarded VNF Package in Plain or Zip Format
... Test objective: The objective is to test the retrieval of the multi file VNFD for an individual OnBoarded VNF package when requesting Plain or Zip format to NFVO by including both formats in the request, and perform a validation that returned content is in Zip format
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The VNFD is implemented as a multi file
... Post-Conditions: none
@@ -210,7 +210,7 @@ Get VNFD in Individual OnBoarded VNF Package with invalid resource identifier
... Test title: Get VNFD in Individual OnBoarded VNF Package with invalid resource identifier
... Test objective: The objective is to test that the retrieval of the VNFD for an individual OnBoarded VNF package content fails when using an invalid resource identifier
... Pre-conditions: none
- ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -222,7 +222,7 @@ Get VNFD in Individual OnBoarded VNF Package Content with conflict due to onboar
... Test title: Get VNFD in Individual OnBoarded VNF Package Content with conflict due to onboarding state
... Test objective: The objective is to test that the retrieval of the VNFD for an individual OnBoarded VNF package content fails due to a conflict when the VNF Package is not in onboarding state ONBOARDED in the NFVO. The test also performs a validation of the JSON schema validation of the failed operation HTTP response
... Pre-conditions: The onboarding state of the VNF package for which the VNFD is requested is different from ONBOARDED.
- ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -235,7 +235,7 @@ POST VNFD in Individual OnBoarded VNF Package Content - Method not implemented
... Test title: POST VNFD in Individual OnBoarded VNF Package Content - Method not implemented
... Test objective: The objective is to test that POST method is not allowed to create new VNFD
... Pre-conditions: none
- ... Reference: Clause 10.4.4.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.4.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -247,7 +247,7 @@ PUT VNFD in Individual OnBoarded VNF Package Content - Method not implemented
... Test title: PUT VNFD in Individual OnBoarded VNF Package Content - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to modify a VNFD
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.4.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.4.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -259,7 +259,7 @@ PATCH VNFD in Individual OnBoarded VNF Package Content - Method not implemented
... Test title: PATCH VNFD in Individual OnBoarded VNF Package Content - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update a VNFD
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.4.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.4.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -271,7 +271,7 @@ DELETE VNFD in Individual OnBoarded VNF Package Content - Method not implemented
... Test title: DELETE VNFD in Individual OnBoarded VNF Package Content - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to delete a VNFD
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.4.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.4.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -283,7 +283,7 @@ Get multi file VNFD in Individual VNF Package with security information
... Test title: Get multi file VNFD in Individual VNF Package with security information
... Test objective: The objective is to test the retrieval of the multi file VNFD for an individual VNF package shall include in the ZIP archive the security information when requested with "include_signature" parameter, and perform a validation that returned content is in Zip format
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The VNFD is implemented as a multi file
... Post-Conditions: none
@@ -296,7 +296,7 @@ Get multi file VNFD in Individual OnBoarded VNF Package with security informatio
... Test title: Get multi file VNFD in Individual OnBoarded VNF Package with security information
... Test objective: The objective is to test the retrieval of the multi file VNFD for an individual OnBoarded VNF package shall include in the ZIP archive the security information when requested with "include_signature" parameter, and perform a validation that returned content is in Zip format
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The VNFD is implemented as a multi file
... Post-Conditions: none
diff --git a/SOL003/VNFPackageManagement-API/VNFPackageArtifacts.robot b/SOL003/VNFPackageManagement-API/VNFPackageArtifacts.robot
index 1e22a6ef52651b3392b646d05459262df0439da5..92f574334e0c858393e8aa3ccaddaa5fcdf2177c 100644
--- a/SOL003/VNFPackageManagement-API/VNFPackageArtifacts.robot
+++ b/SOL003/VNFPackageManagement-API/VNFPackageArtifacts.robot
@@ -11,7 +11,7 @@ Get VNF Package Artifact
... Test title: Get VNF Package Artifact
... Test objective: The objective is to test that the GET request read the whole content of the archive containing the artifact files successfully, and perform a validation that returned content is in Zip format
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -24,7 +24,7 @@ Get VNF Package Artifact with "exclude_all_mano_artifacts" parameter
... Test title: Get VNF Package Artifact with "exclude_all_mano_artifacts" parameter
... Test objective: The objective is to test that the GET request read the whole content of the archive containing the artifact files successfully and it doesnot contain additional MANO artifacts when requested with "exclude_all_mano_artifacts" parameter
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -37,7 +37,7 @@ Get VNF Package Artifact with "exclude_all_non_mano_artifacts" parameter
... Test title: Get VNF Package Artifact with "exclude_all_non_mano_artifacts" parameter
... Test objective: The objective is to test that the GET request read the whole content of the archive containing the artifact files successfully and it doesnot contain non-MANO Artifacts when requested with "exclude_all_non_mano_artifacts" parameter
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -50,7 +50,7 @@ Get VNF Package Artifact with "select_non_mano_artifact_sets" parameter
... Test title: Get VNF Package Artifact with "select_non_mano_artifact_sets" parameter
... Test objective: The objective is to test that the GET request read the whole content of the archive containing the artifact files successfully and also contain non_MANO artifacts set when requested with "select_non_mano_artifact_sets" parameter
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -63,7 +63,7 @@ Get VNF Package Artifact with "include_signatures" parameter
... Test title: Get VNF Package Artifact with "include_signatures" parameter
... Test objective: The objective is to test that the GET request read the whole content of the archive containing the artifact files successfully and also contain security certificates when requested with "include_signature" parameter, and perform a validation that returned content is in Zip format
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -76,7 +76,7 @@ Get VNF Package Artifact with Range Request and NFVO supporting Range Requests
... Test title: Get VNF Package Artifact with Range Request and NFVO supporting Range Requests
... Test objective: The objective is to test the GET request read the whole content of the archive containing the artifact files successfully when using a range request to return single range of bytes from the file, with the NFVO supporting it. The test also perform a validation that returned content matches the issued range
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO supports range requests to return single range of bytes from the VNF package artifact
... Post-Conditions: none
@@ -90,7 +90,7 @@ Get VNF Package Artifact with invalid URI parameters "exclude_all_non_mano_artif
... Test title: Get VNF Package Artifact with invalid URI parameters "exclude_all_non_mano_artifacts", "select_non_mano_artifact_sets"
... Test objective: The objective is to test that the GET request to read the whole content of the archive containing the artifact files fails when both "exclude_all_non_mano_artifacts" and "select_non_mano_artifact_sets" are present in request
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -103,7 +103,7 @@ Get VNF Package Artifact with invalid URI parameters "exclude_all_non_mano_artif
... Test title: Get VNF Package Artifact with invalid URI parameters "exclude_all_non_mano_artifacts", "exclude_all_mano_artifactss"
... Test objective: The objective is to test that the GET request to read the whole content of the archive containing the artifact files fails when both "exclude_all_non_mano_artifacts" and "exclude_all_mano_artifacts" are present in request
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -116,7 +116,7 @@ Get VNF Package Artifact with invalid URI parameters undifend select_non_mano_ar
... Test title: Get VNF Package Artifact with invalid URI parameters undefined select_non_mano_artifact_sets
... Test objective: The objective is to test that the GET request to read the whole content of the archive containing the artifact files fails when one or more value provided in "select_non_mano_artifact_sets" are not provided in Manifest.
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -129,7 +129,7 @@ Get VNF Package Artifact with conflict due to onboarding state
... Test title: Get VNF Package Artifact with conflict due to onboarding state
... Test objective: The objective is to test that the GET request to read the whole content of the archive containing the artifact files fails due to a conflict when the VNF Package is not in onboarding state ONBOARDED in the NFVO. The test also performs a validation of the JSON schema validation of the failed operation HTTP response
... Pre-conditions: The onboarding state of the VNF package for which the content is requested is different from ONBOARDED.
- ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -142,7 +142,7 @@ GET VNF Package Artifact with invalid Range Request
... Test title: GET VNF Package Artifact with invalid Range Request
... Test objective: The objective is to test that the GET request to read the whole content of the archive containing the artifact files fails when using a range request that does not match any available byte range in the file.
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO supports range requests to return single range of bytes from the VNF package artifact
... Post-Conditions: none
@@ -154,7 +154,7 @@ POST VNF Package Artifact - Method not implemented
... Test title: POST VNF Package Artifact - Method not implemented
... Test objective: The objective is to test that POST method is not allowed to create new VNF Package artifact
... Pre-conditions: none
- ... Reference: Clause 10.4.5a.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.5a.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -166,7 +166,7 @@ PUT VNF Package Artifact - Method not implemented
... Test title: PUT VNF Package Artifact - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to modify a VNF Package artifact
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.5a.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.5a.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -178,7 +178,7 @@ PATCH VNF Package Artifact - Method not implemented
... Test title: PATCH VNF Package Artifact - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update a VNF Package artifact
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.5a.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.5a.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -190,7 +190,7 @@ DELETE VNF Package Artifact - Method not implemented
... Test title: DELETE VNF Package Artifact - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to delete a VNF Package artifact
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.6.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.6.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -202,7 +202,7 @@ Get OnBoarded VNF Package Artifact
... Test title: Get OnBoarded VNF Package Artifact
... Test objective: The objective is to test that the GET request read the whole content of the archive containing the OnBoarded VNF Package Artifact files successfully, and perform a validation that returned content is in Zip format
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -215,7 +215,7 @@ Get OnBoarded VNF Package Artifact with "exclude_all_mano_artifacts" parameter
... Test title: Get OnBoarded VNF Package Artifact with "exclude_all_mano_artifacts" parameter
... Test objective: The objective is to test that the GET request read the whole content of the archive containing the OnBoarded VNF Package Artifact files successfully and it doesnot contain additional MANO artifacts when requested with "exclude_all_mano_artifacts" parameter
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -228,7 +228,7 @@ Get OnBoarded VNF Package Artifact with "exclude_all_non_mano_artifacts" paramet
... Test title: Get OnBoarded VNF Package Artifact with "exclude_all_non_mano_artifacts" parameter
... Test objective: The objective is to test that the GET request read the whole content of the archive containing the OnBoarded VNF Package artifact files successfully and it doesnot contain non-MANO Artifacts when requested with "exclude_all_non_mano_artifacts" parameter
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -241,7 +241,7 @@ Get OnBoarded VNF Package Artifact with "select_non_mano_artifact_sets" paramete
... Test title: Get OnBoarded VNF Package Artifact with "select_non_mano_artifact_sets" parameter
... Test objective: The objective is to test that the GET request read the whole content of the archive containing the OnBoarded VNF Package artifact files successfully and also contain non_MANO artifacts set when requested with "select_non_mano_artifact_sets" parameter
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -254,7 +254,7 @@ Get OnBoarded VNF Package Artifact with "include_signatures" parameter
... Test title: Get OnBoarded VNF Package Artifact with "include_signatures" parameter
... Test objective: The objective is to test that the GET request read the whole content of the archive containing the OnBoarded VNF Package artifact files successfully and also contain security certificates when requested with "include_signature" parameter, and perform a validation that returned content is in Zip format
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -267,7 +267,7 @@ Get OnBoarded VNF Package Artifact with Range Request and NFVO supporting Range
... Test title: Get OnBoarded VNF Package Artifact with Range Request and NFVO supporting Range Requests
... Test objective: The objective is to test the GET request read the whole content of the archive containing the OnBoarded VNF Package artifact files successfully when using a range request to return single range of bytes from the file, with the NFVO supporting it. The test also perform a validation that returned content matches the issued range
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO supports range requests to return single range of bytes from the VNF package artifact
... Post-Conditions: none
@@ -281,7 +281,7 @@ Get OnBoarded VNF Package Artifact with invalid URI parameters "exclude_all_non_
... Test title: Get OnBoarded VNF Package Artifact with invalid URI parameters "exclude_all_non_mano_artifacts", "select_non_mano_artifact_sets"
... Test objective: The objective is to test that the GET request to read the whole content of the archive containing the OnBoarded VNF Package artifact files fails when both "exclude_all_non_mano_artifacts" and "select_non_mano_artifact_sets" are present in request
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -294,7 +294,7 @@ Get OnBoarded VNF Package Artifact with invalid URI parameters "exclude_all_non_
... Test title: Get OnBoarded VNF Package Artifact with invalid URI parameters "exclude_all_non_mano_artifacts", "exclude_all_mano_artifactss"
... Test objective: The objective is to test that the GET request to read the whole content of the archive containing the OnBoarded VNF Package artifact files fails when both "exclude_all_non_mano_artifacts" and "exclude_all_mano_artifacts" are present in request
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -307,7 +307,7 @@ Get OnBoarded VNF Package Artifact with invalid URI parameters undifend select_n
... Test title: Get OnBoarded VNF Package Artifact with invalid URI parameters undefined select_non_mano_artifact_sets
... Test objective: The objective is to test that the GET request to read the whole content of the archive containing the OnBoarded VNF Package artifact files fails when one or more value provided in "select_non_mano_artifact_sets" are not provided in Manifest.
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -320,7 +320,7 @@ Get OnBoarded VNF Package Artifact with conflict due to onboarding state
... Test title: Get OnBoarded VNF Package Artifact with conflict due to onboarding state
... Test objective: The objective is to test that the GET request to read the whole content of the archive containing the OnBoarded VNF Package artifact files fails due to a conflict when the VNF Package is not in onboarding state ONBOARDED in the NFVO. The test also performs a validation of the JSON schema validation of the failed operation HTTP response
... Pre-conditions: The onboarding state of the VNF package for which the content is requested is different from ONBOARDED.
- ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -333,7 +333,7 @@ GET OnBoarded VNF Package Artifact with invalid Range Request
... Test title: GET OnBoarded VNF Package Artifact with invalid Range Request
... Test objective: The objective is to test that the GET request to read the whole content of the archive containing the OnBoarded VNF Package artifact files fails when using a range request that does not match any available byte range in the file.
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO supports range requests to return single range of bytes from the VNF package artifact
... Post-Conditions: none
@@ -345,7 +345,7 @@ POST OnBoarded VNF Package Artifact - Method not implemented
... Test title: POST OnBoarded VNF Package Artifact - Method not implemented
... Test objective: The objective is to test that POST method is not allowed to create new VNF Package artifact
... Pre-conditions: none
- ... Reference: Clause 10.4.5a.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.5a.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -357,7 +357,7 @@ PUT OnBoarded VNF Package Artifact - Method not implemented
... Test title: PUT OnBoarded VNF Package Artifact - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to modify a VNF Package artifact
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.5a.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.5a.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -369,7 +369,7 @@ PATCH OnBoarded VNF Package Artifact - Method not implemented
... Test title: PATCH OnBoarded VNF Package Artifact - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update a VNF Package artifact
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.5a.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.5a.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -381,7 +381,7 @@ DELETE OnBoarded VNF Package Artifact - Method not implemented
... Test title: DELETE OnBoarded VNF Package Artifact - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to delete a VNF Package artifact
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.6.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.6.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -393,7 +393,7 @@ Get VNF Package Artifact with "include_external_artifacts" parameter
... Test title: Get VNF Package Artifact with "include_external_artifacts" parameter
... Test objective: The objective is to test that GET request reads the whole content of the archive containing the external artifacts successfully when requested with "include_external_artifacts" parameter
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -406,7 +406,7 @@ Get OnBoarded VNF Package Artifact with "include_external_artifacts" parameter
... Test title: Get OnBoarded VNF Package Artifact with "include_external_artifacts" parameter
... Test objective: The objective is to test that the GET request read the whole content of the archive containing the external OnBoarded VNF Package Artifacts successfully when requested with "include_external_artifacts" parameter
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFPackageManagement-API/VNFPackageContent.robot b/SOL003/VNFPackageManagement-API/VNFPackageContent.robot
index 1aa94439caeaa1de545e0b2ed2cac34b3e1df36c..566df1d035ceef15c38054c3ae02c9d98cef53a4 100644
--- a/SOL003/VNFPackageManagement-API/VNFPackageContent.robot
+++ b/SOL003/VNFPackageManagement-API/VNFPackageContent.robot
@@ -11,7 +11,7 @@ GET Individual VNF Package Content
... Test title: GET Individual VNF Package Content
... Test objective: The objective is to test the retrieval of an individual VNF package content and perform a validation that returned content is in zip format
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -24,7 +24,7 @@ GET Individual VNF Package Content with Range Request and NFVO supporting Range
... Test title: GET Individual VNF Package Content with Range Request and NFVO supporting Range Requests
... Test objective: The objective is to test the retrieval of an individual VNF package content when using a range request to return single range of bytes from the file, with the NFVO supporting it. The test also perform a validation that returned content matches the issued range
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO supports range requests to return single range of bytes from the VNF package file
... Post-Conditions: none
@@ -39,7 +39,7 @@ GET Individual VNF Package Content with Range Request and NFVO not supporting Ra
... Test title: GET Individual VNF Package Content with Range Request and NFVO not supporting Range Requests
... Test objective: The objective is to test that the retrieval of an individual VNF package content, when using a range request to return single range of bytes from the file and the NFVO not supporting it, returns the full VNF Package file.
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO does not support range requests to return single range of bytes from the VNF package file
... Post-Conditions: none
@@ -52,7 +52,7 @@ GET Individual VNF Package Content with invalid Range Request
... Test title: GET Individual VNF Package Content with invalid Range Request
... Test objective: The objective is to test that the retrieval of an individual VNF package content fails when using a range request that does not match any available byte range in the file.
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO supports range requests to return single range of bytes from the VNF package file
... Post-Conditions: none
@@ -64,7 +64,7 @@ GET Individual VNF Package Content with invalid resource identifier
... Test title: GET Individual VNF Package Content with invalid resource identifier
... Test objective: The objective is to test that the retrieval of an individual VNF package content fails when using an invalid resource identifier
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -77,7 +77,7 @@ GET Individual VNF Package Content with conflict due to onboarding state
... Test title: GET Individual VNF Package Content with conflict due to onboarding state
... Test objective: The objective is to test that the retrieval of an individual VNF package content fails due to a conflict when the VNF Package is not in onboarding state ONBOARDED in the NFVO. The test also performs a validation of the JSON schema validation of the failed operation HTTP response
... Pre-conditions: The onboarding state of the VNF package for which the content is requested is different from ONBOARDED.
- ... Reference: Clause 10.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -90,7 +90,7 @@ POST Individual VNF Package Content - Method not implemented
... Test title: POST Individual VNF Package Content - Method not implemented
... Test objective: The objective is to test that POST method is not allowed to create new VNF Package content
... Pre-conditions: none
- ... Reference: Clause 10.4.3.5.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.3.5.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -102,7 +102,7 @@ PUT Individual VNF Package Content - Method not implemented
... Test title: PUT Individual VNF Package Content - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to modify a VNF Package content
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.3.5.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.3.5.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -114,7 +114,7 @@ PATCH Individual VNF Package Content - Method not implemented
... Test title: PATCH Individual VNF Package Content - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update a VNF Package content
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.3.5.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.3.5.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -126,7 +126,7 @@ DELETE Individual VNF Package Content - Method not implemented
... Test title: DELETE Individual VNF Package Content - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to delete a VNF Package content
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.3.5.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.3.5.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -138,7 +138,7 @@ GET Individual OnBoarded VNF Package Content
... Test title: GET Individual OnBoarded VNF Package Content
... Test objective: The objective is to test the retrieval of an individual OnBoarded VNF package content and perform a validation that returned content is in zip format
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -151,7 +151,7 @@ GET Individual OnBoarded VNF Package Content with Range Request and NFVO support
... Test title: GET Individual OnBoarded VNF Package Content with Range Request and NFVO supporting Range Requests
... Test objective: The objective is to test the retrieval of an individual OnBoarded VNF package content when using a range request to return single range of bytes from the file, with the NFVO supporting it. The test also perform a validation that returned content matches the issued range
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO supports range requests to return single range of bytes from the VNF package file
... Post-Conditions: none
@@ -166,7 +166,7 @@ GET Individual OnBoarded VNF Package Content with Range Request and NFVO not sup
... Test title: GET Individual OnBoarded VNF Package Content with Range Request and NFVO not supporting Range Requests
... Test objective: The objective is to test that the retrieval of an individual OnBoarded VNF package content, when using a range request to return single range of bytes from the file and the NFVO not supporting it, returns the full VNF Package file.
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO does not support range requests to return single range of bytes from the VNF package file
... Post-Conditions: none
@@ -179,7 +179,7 @@ GET Individual OnBoarded VNF Package Content with invalid Range Request
... Test title: GET Individual OnBoarded VNF Package Content with invalid Range Request
... Test objective: The objective is to test that the retrieval of an individual OnBoarded VNF package content fails when using a range request that does not match any available byte range in the file.
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO supports range requests to return single range of bytes from the VNF package file
... Post-Conditions: none
@@ -191,7 +191,7 @@ GET Individual OnBoarded VNF Package Content with invalid resource identifier
... Test title: GET Individual OnBoarded VNF Package Content with invalid resource identifier
... Test objective: The objective is to test that the retrieval of an individual OnBoarded VNF package content fails when using an invalid resource identifier
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -203,7 +203,7 @@ GET Individual OnBoarded VNF Package Content with conflict due to onboarding sta
... Test title: GET Individual OnBoarded VNF Package Content with conflict due to onboarding state
... Test objective: The objective is to test that the retrieval of an individual VNF package content fails due to a conflict when the VNF Package is not in onboarding state ONBOARDED in the NFVO. The test also performs a validation of the JSON schema validation of the failed operation HTTP response
... Pre-conditions: The onboarding state of the VNF package for which the content is requested is different from ONBOARDED.
- ... Reference: Clause 10.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -216,7 +216,7 @@ POST Individual OnBoarded VNF Package Content - Method not implemented
... Test title: POST Individual OnBoarded VNF Package Content - Method not implemented
... Test objective: The objective is to test that POST method is not allowed to create new VNF Package content
... Pre-conditions: none
- ... Reference: Clause 10.4.3.5.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.3.5.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -228,7 +228,7 @@ PUT Individual OnBoarded VNF Package Content - Method not implemented
... Test title: PUT Individual OnBoarded VNF Package Content - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to modify a VNF Package content
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.3.5.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.3.5.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -240,7 +240,7 @@ PATCH Individual OnBoarded VNF Package Content - Method not implemented
... Test title: PATCH Individual OnBoarded VNF Package Content - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update a VNF Package content
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.3.5.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.3.5.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -252,7 +252,7 @@ DELETE Individual OnBoarded VNF Package Content - Method not implemented
... Test title: DELETE Individual OnBoarded VNF Package Content - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to delete a VNF Package content
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.3.5.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.3.5.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFPackageManagement-API/VNFPackages.robot b/SOL003/VNFPackageManagement-API/VNFPackages.robot
index c04f763739cd628555930bf3c9328af54e2fe45e..15e311358e33b40cbd2305669572bb09bcfd03e3 100644
--- a/SOL003/VNFPackageManagement-API/VNFPackages.robot
+++ b/SOL003/VNFPackageManagement-API/VNFPackages.robot
@@ -11,7 +11,7 @@ GET all VNF Packages
... Test title: GET all VNF Packages
... Test objective: The objective is to test the retrieval of all the available VNF packages information and perform a JSON schema and content validation of the collected data structure
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -27,7 +27,7 @@ GET VNF Packages with attribute-based filter
... Test title: GET VNF Packages with attribute-based filter
... Test objective: The objective is to test the retrieval of VNF packages using attribute-based filter, perform a JSON schema validation of the collected jobs data structure, and verify that the retrieved information matches the issued attribute-based filter
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -41,7 +41,7 @@ GET VNF Packages with invalid attribute-based filter
... Test title: GET VNF Packages with invalid attribute-based filter
... Test objective: The objective is to test that the retrieval of VNF packages fails when using invalid attribute-based filter, and perform the JSON schema validation of the failed operation HTTP response
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -54,7 +54,7 @@ GET VNF Packages with "all_fields" attribute selector
... Test title: GET VNF Packages with "all_fields" attribute selector
... Test objective: The objective is to test the retrieval of VNF packages with "all_fields" attribute selector, perform a JSON schema validation of the collected data structure, and verify that the retrieved information matches the issued "all_fileds" selector
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -68,7 +68,7 @@ GET VNF Packages with "exclude_default" attribute selector
... Test title: GET VNF Packages with exclude_default attribute selector
... Test objective: The objective is to test the retrieval of VNF packages with "exclude_default" attribute selector, perform a JSON schema validation of the collected data structure, and verify that the retrieved information matches the issued "exclude_default" selector
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -82,7 +82,7 @@ GET VNF Packages with "fields" attribute selector
... Test title: GET VNF Packages with fields attribute selector
... Test objective: The objective is to test the retrieval of VNF packages with "fields" attribute selector, perform a JSON schema validation of the collected data structure, and verify that the retrieved information matches the issued "fields" selector
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The VNFM supports the use of fields attribute selector
... Post-Conditions: none
@@ -96,7 +96,7 @@ GET VNF Packages with "exclude_fields" attribute selector
... Test title: GET VNF Packages with exclude_fields attribute selector
... Test objective: The objective is to test the retrieval of VNF packages with "exclude_fields" attribute selector, perform a JSON schema validation of the collected data structure, and verify that the retrieved information matches the issued "exclude_fields" selector
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The VNFM supports the use of exclude_fields attribute selector
... Post-Conditions: none
@@ -110,7 +110,7 @@ GET all VNF Packages with invalid resource endpoint
... Test title: GET VNF Packages with invalid resource endpoint
... Test objective: The objective is to test that the retrieval of VNF packages fails when using invalid resource endpoint
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -122,7 +122,7 @@ POST all VNF Packages - Method not implemented
... Test title: POST all VNF Packages - Method not implemented
... Test objective: The objective is to test that POST method is not allowed to create new VNF Packages
... Pre-conditions: none
- ... Reference: Clause 10.4.2.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.2.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -134,7 +134,7 @@ PUT all VNF Packages - Method not implemented
... Test title: PUT all VNF Packages - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to modify existing VNF Packages
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.2.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.2.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -146,7 +146,7 @@ PATCH all VNF Packages - Method not implemented
... Test title: PATCH all VNF Packages - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update existing VNF Packages
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.2.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.2.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -158,7 +158,7 @@ DELETE all VNF Packages - Method not implemented
... Test title: DELETE all VNF Packages - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to delete existing VNF Packages
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.2.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.2.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -170,7 +170,7 @@ GET all VNF Packages as a Paged Response
... Test title: GET all VNF Packages as a Paged Response
... Test objective: The objective is to test the retrieval of all the available VNF packages information as a Paged Response.
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The VNFM supports response paging for the VNF package resources
... Post-Conditions: none
@@ -183,7 +183,7 @@ GET all VNF Packages as a Paged Response with nextpage_opauque_marker parameter
... Test title: GET all VNF Packages as a Paged Response with nextpage_opauque_marker parameter
... Test objective: The objective is to query information about all VNF packages as a Paged Response and retrieve the next page using the nextpage_opaque_marker parameter
... Pre-conditions: A request for retrieving all VNF packages as a paged response has been successfully issued (Test ID 7.3.3.1.13)
- ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The VNFM supports response paging for the VNF package resources
... Post-Conditions: none
@@ -196,7 +196,7 @@ GET VNF Packages - Bad Request Response too Big
... Test title: GET VNF Packages - Bad Request Response too Big
... Test objective: The objective is to test that the retrieval of VNF packages fails because response is too big, and perform the JSON schema validation of the failed operation HTTP response
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -209,7 +209,7 @@ GET all OnBoarded VNF Packages
... Test title: GET all OnBoarded VNF Packages
... Test objective: The objective is to test the retrieval of all the available onboarded VNF packages information and perform a JSON schema and content validation of the collected data structure
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -225,7 +225,7 @@ GET OnBoarded VNF Packages with attribute-based filter
... Test title: GET OnBoarded VNF Packages with attribute-based filter
... Test objective: The objective is to test the retrieval of OnBoarded VNF packages using attribute-based filter, perform a JSON schema validation of the collected jobs data structure, and verify that the retrieved information matches the issued attribute-based filter
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -239,7 +239,7 @@ GET OnBoarded VNF Packages with invalid attribute-based filter
... Test title: GET OnBoarded VNF Packages with invalid attribute-based filter
... Test objective: The objective is to test that the retrieval of OnBoarded VNF packages fails when using invalid attribute-based filter, and perform the JSON schema validation of the failed operation HTTP response
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -252,7 +252,7 @@ GET OnBoarded VNF Packages with "all_fields" attribute selector
... Test title: GET OnBoarded VNF Packages with "all_fields" attribute selector
... Test objective: The objective is to test the retrieval of OnBoarded VNF packages with "all_fields" attribute selector, perform a JSON schema validation of the collected data structure, and verify that the retrieved information matches the issued "all_fileds" selector
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 4.3.3.2.1, 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 4.3.3.2.1, 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -266,7 +266,7 @@ GET OnBoarded VNF Packages with "exclude_default" attribute selector
... Test title: GET OnBoarded VNF Packages with exclude_default attribute selector
... Test objective: The objective is to test the retrieval of OnBoarded VNF packages with "exclude_default" attribute selector, perform a JSON schema validation of the collected data structure, and verify that the retrieved information matches the issued "exclude_default" selector
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 4.3.3.2.1, 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 4.3.3.2.1, 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -280,7 +280,7 @@ GET OnBoarded VNF Packages with "fields" attribute selector
... Test title: GET OnBoarded VNF Packages with fields attribute selector
... Test objective: The objective is to test the retrieval of OnBoarded VNF packages with "fields" attribute selector, perform a JSON schema validation of the collected data structure, and verify that the retrieved information matches the issued "fields" selector
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 4.3.3.2.1, 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 4.3.3.2.1, 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The VNFM supports the use of fields attribute selector
... Post-Conditions: none
@@ -294,7 +294,7 @@ GET OnBoarded VNF Packages with "exclude_fields" attribute selector
... Test title: GET OnBoarded VNF Packages with exclude_fields attribute selector
... Test objective: The objective is to test the retrieval of OnBoarded VNF packages with "exclude_fields" attribute selector, perform a JSON schema validation of the collected data structure, and verify that the retrieved information matches the issued "exclude_fields" selector
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 4.3.3.2.1, 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 4.3.3.2.1, 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The VNFM supports the use of exclude_fields attribute selector
... Post-Conditions: none
@@ -308,7 +308,7 @@ GET all OnBoarded VNF Packages with invalid resource endpoint
... Test title: GET OnBoarded VNF Packages with invalid resource endpoint
... Test objective: The objective is to test that the retrieval of OnBoarded VNF packages fails when using invalid resource endpoint
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -320,7 +320,7 @@ POST all OnBoarded VNF Packages - Method not implemented
... Test title: POST all OnBoarded VNF Packages - Method not implemented
... Test objective: The objective is to test that POST method is not allowed to create new OnBoarded VNF Packages
... Pre-conditions: none
- ... Reference: Clause 10.4.2.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.2.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -332,7 +332,7 @@ PUT all OnBoarded VNF Packages - Method not implemented
... Test title: PUT all OnBoarded VNF Packages - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to modify existing OnBoarded VNF Packages
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.2.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.2.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -344,7 +344,7 @@ PATCH all OnBoarded VNF Packages - Method not implemented
... Test title: PATCH all OnBoarded VNF Packages - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update existing OnBoarded VNF Packages
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.2.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.2.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -356,7 +356,7 @@ DELETE all OnBoarded VNF Packages - Method not implemented
... Test title: DELETE all OnBoarded VNF Packages - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to delete existing OnBoarded VNF Packages
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.2.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.2.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -368,7 +368,7 @@ GET all OnBoarded VNF Packages as a Paged Response
... Test title: GET all OnBoarded VNF Packages as a Paged Response
... Test objective: The objective is to test the retrieval of all the available OnBoarded VNF packages information as a Paged Response.
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The VNFM supports response paging for the VNF package resources
... Post-Conditions: none
@@ -381,7 +381,7 @@ GET all OnBoarded VNF Packages as a Paged Response with nextpage_opauque_marker
... Test title: GET all OnBoarded VNF Packages as a Paged Response with nextpage_opauque_marker parameter
... Test objective: The objective is to query information about all onBoarded VNF packages as a Paged Response and retrieve the next page using the nextpage_opaque_marker parameter
... Pre-conditions: A request for retrieving all onBoarded VNF packages as a paged response has been successfully issued (Test ID 7.3.3.1.27)
- ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The VNFM supports response paging for the VNF package resources
... Post-Conditions: none
@@ -394,7 +394,7 @@ GET OnBoarded VNF Packages - Bad Request Response too Big
... Test title: GET OnBoarded VNF Packages - Bad Request Response too Big
... Test objective: The objective is to test that the retrieval of OnBoarded VNF packages fails because response is too big, and perform the JSON schema validation of the failed operation HTTP response
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -407,7 +407,7 @@ GET VNF Packages with "fields" and "exclude_default" attribute selector
... Test title: GET VNF Packages with fields and exclude_default attribute selector
... Test objective: The objective is to test the retrieval of VNF packages with "fields" and "exclude_default" attribute selector, perform a JSON schema validation of the collected data structure, and verify that the retrieved information matches the issued "fields" selector
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The VNFM supports the use of fields attribute selector
... Post-Conditions: none
@@ -421,7 +421,7 @@ GET OnBoarded VNF Packages with "fields" and "exclude_default" attribute selecto
... Test title: GET OnBoarded VNF Packages with fields and exclude_default attribute selector
... Test objective: The objective is to test the retrieval of OnBoarded VNF packages with "fields" and "exclude_default" attribute selector, perform a JSON schema validation of the collected data structure, and verify that the retrieved information matches the issued "fields" selector
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 4.3.3.2.1, 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 4.3.3.2.1, 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The VNFM supports the use of fields attribute selector
... Post-Conditions: none
diff --git a/SOL003/VNFPerformanceManagement-API/ApiVersion.robot b/SOL003/VNFPerformanceManagement-API/ApiVersion.robot
index 7ba80ff5d5a2fb1e44c154ef44fb296a9aa07f5f..bdbc3deeccabe71e14cad50daca830d308468a0e 100644
--- a/SOL003/VNFPerformanceManagement-API/ApiVersion.robot
+++ b/SOL003/VNFPerformanceManagement-API/ApiVersion.robot
@@ -13,7 +13,7 @@ POST API Version - Method not implemented
... Test title: POST API version - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -25,7 +25,7 @@ GET API Version
... Test title: GET API Version
... Test objective: The objective is to test that GET method successfully return ApiVersionInformation
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -38,7 +38,7 @@ PUT API Version - Method not implemented
... Test title: PUT API Version - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -50,7 +50,7 @@ PATCH API Version - Method not implemented
... Test title: PATCH API Version - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -62,7 +62,7 @@ DELETE API Version - Method not implemented
... Test title: DELETE API Version - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -74,7 +74,7 @@ POST API Version with apiMajorVerion - Method not implemented
... Test title: POST API version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -86,7 +86,7 @@ GET API Version with apiMajorVerion
... Test title: GET API Version with apiMajorVerion
... Test objective: The objective is to test that GET method successfully return ApiVersionInformation
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -99,7 +99,7 @@ PUT API Version with apiMajorVerion - Method not implemented
... Test title: PUT API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -111,7 +111,7 @@ PATCH API Version with apiMajorVerion - Method not implemented
... Test title: PATCH API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -123,7 +123,7 @@ DELETE API Version with apiMajorVerion - Method not implemented
... Test title: DELETE API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFPerformanceManagement-API/IndividualPmJob.robot b/SOL003/VNFPerformanceManagement-API/IndividualPmJob.robot
index bf0539c59653436f31dafb14450c5a16713b210d..0f1f8bed0ab7b38cdfece7ffa86bedc509cfeb6c 100644
--- a/SOL003/VNFPerformanceManagement-API/IndividualPmJob.robot
+++ b/SOL003/VNFPerformanceManagement-API/IndividualPmJob.robot
@@ -17,7 +17,7 @@ GET individual VNF Performance Job
... Test title: Get individual VNF Performance Job
... Test objective: The objective is to test the retrieval of an individual VNF performance monitoring job and perform a JSON schema and content validation of the collected job data structure
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance jobs are set in the VNFM.
- ... Reference: Clause 6.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 6.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -32,7 +32,7 @@ GET individual VNF Performance Job with invalid resource identifier
... Test title: Get individual VNF Performance Job with invalid resource identifier
... Test objective: The objective is to test that the retrieval of an individual VNF performance monitoring job fails when using an invalid resource identifier, and perform the JSON schema validation of the failed operation HTTP response
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance jobs are set in the VNFM.
- ... Reference: Clause 6.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 6.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -45,7 +45,7 @@ DELETE Individual VNF Performance Job
... Test title: Delete Individual VNF Performance Job
... Test objective: The objective is to test the deletion of an individual VNF performance monitoring job
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance jobs are set in the VNFM.
- ... Reference: Clause 6.4.3.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 6.4.3.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: The VNF Performance Job is no more available in the VNFM
@@ -58,7 +58,7 @@ DELETE Individual VNF Performance Job with invalid resource identifier
... Test title: Delete individual VNF Performance Job with invalid resource identifier
... Test objective: The objective is to test that the deletion of an individual VNF performance monitoring job fails when using an invalid resource identifier
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance jobs are set in the VNFM.
- ... Reference: Clause 6.4.3.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 6.4.3.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -71,7 +71,7 @@ POST Individual VNF Performance Job - Method not implemented
... Test title: POST Individual VNF Performance Job - method not implemented
... Test objective: The objective is to test that POST method is not allowed to create a new VNF Performance Monitoring Job
... Pre-conditions: A VNF instance is instantiated
- ... Reference: Clause 6.4.3.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 6.4.3.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -83,7 +83,7 @@ PUT Individual VNF Performance Job - Method not implemented
... Test title: PUT Individual VNF Performance Job - method not implemented
... Test objective: The objective is to test that PUT method is not allowed to update an existing VNF Performance Monitoring Job
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance jobs are set in the VNFM.
- ... Reference: Clause 6.4.3.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 6.4.3.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -95,7 +95,7 @@ PATCH Individual VNF Performance Job
... Test title: PATCH Individual VNF Performance Job
... Test objective: The objective is to test that PATCH method allows to modify individual performace management job
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance jobs are set in the VNFM.
- ... Reference: Clause 6.4.3.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 6.4.3.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions:
@@ -109,7 +109,7 @@ PATCH Individual VNF Performance Job - Precondition failed
... Test title: PATCH Individual VNF Performance Job - Precondition failed
... Test objective: The objective is to attempt to Modify an individual alarm resource, where the precondition was not met.
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance jobs are set in the VNFM.
- ... Reference: Clause 6.4.3.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 6.4.3.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: The VNF Performance Job is not modified by the operation
@@ -118,16 +118,16 @@ PATCH Individual VNF Performance Job - Precondition failed
Check HTTP Response Body Json Schema Is ProblemDetails
Check Postcondition VNF Performance Job is Unmodified (Implicit)
-PATCH Individual VNF Performance Job - Unprocessable Entity
+PATCH Individual VNF Performance Job - Unprocessable Content
[Documentation] Test ID: 7.3.4.2.9
- ... Test title: PATCH Individual VNF Performance Job - Unprocessable Entity
+ ... Test title: PATCH Individual VNF Performance Job - Unprocessable Content
... Test objective: The objective is to test that PATCH method cannot modify an exsisting individual PM job resource when a request contains syntactically correct data but the data cannot be processed.
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance jobs are set in the VNFM.
- ... Reference: Clause 6.4.3.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 6.4.3.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
- Send Patch request for individual VNF Performance Job with unprocessable entity
+ Send Patch request for individual VNF Performance Job with unprocessable content
Check HTTP Response Status Code Is 422
Check HTTP Response Body Json Schema Is ProblemDetails
@@ -217,7 +217,7 @@ Send Patch request for individual VNF Performance Job - Etag mismatch
${output}= Output response
Set Suite Variable ${response} ${output}
-Send Patch request for individual VNF Performance Job with unprocessable entity
+Send Patch request for individual VNF Performance Job with unprocessable content
Set Headers {"Accept":"${ACCEPT_JSON}"}
Set Headers {"Content-Type": "${CONTENT_TYPE_PATCH}"}
Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"${AUTHORIZATION_HEADER}":"${AUTHORIZATION_TOKEN}"}
diff --git a/SOL003/VNFPerformanceManagement-API/IndividualReport.robot b/SOL003/VNFPerformanceManagement-API/IndividualReport.robot
index 7e01ef3e0dfa382c95e21014f196aa280620dfd2..57ca4fdcbae5bd29dff1b4a792154aa9f4ac0ab7 100644
--- a/SOL003/VNFPerformanceManagement-API/IndividualReport.robot
+++ b/SOL003/VNFPerformanceManagement-API/IndividualReport.robot
@@ -11,7 +11,7 @@ Get Individual Performance Report
... Test title: Get Individual Performance Report
... Test objective: The objective is to test the retrieval of an individual VNF performance report associated to a monitoring job and perform a JSON schema validation of the collected report data structure
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance reports are set for a monitoring job in the VNFM.
- ... Reference: Clause 6.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 6.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -24,7 +24,7 @@ Get Individual Performance Report with invalid resource endpoint
... Test title: Get Individual Performance Report with invalid resource endpoint
... Test objective: The objective is to test that the retrieval of an individual VNF performance report associated to a monitoring job fails when using an invalid resource endpoint
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance reports are set for a monitoring job in the VNFM.
- ... Reference: Clause 6.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 6.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -37,7 +37,7 @@ POST Individual Performance Report - Method not implemented
... Test title: POST Individual Performance Report - Method not implemented
... Test objective: The objective is to test that POST method is not allowed to create a new VNF performance report within a monitoring job
... Pre-conditions: A VNF instance is instantiated.
- ... Reference: Clause 6.4.4.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 6.4.4.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -49,7 +49,7 @@ PUT Individual Performance Report - Method not implemented
... Test title: PUT Individual Performance Report - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to update an existing VNF performance report within a monitoring job
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance reports are set for a monitoring job in the VNFM.
- ... Reference: Clause 6.4.4.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 6.4.4.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -61,7 +61,7 @@ PATCH Individual Performance Report - Method not implemented
... Test title: PATCH Individual Performance Report - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to modify an existing VNF performance report within a monitoring job
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance reports are set for a monitoring job in the VNFM.
- ... Reference: Clause 6.4.4.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 6.4.4.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -73,7 +73,7 @@ DELETE Individual Performance Report - Method not implemented
... Test title: DELETE Individual Performance Report - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to delete an existing VNF performance report within a monitoring job
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance reports are set for a monitoring job in the VNFM.
- ... Reference: Clause 6.4.4.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 6.4.4.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFPerformanceManagement-API/IndividualThreshold.robot b/SOL003/VNFPerformanceManagement-API/IndividualThreshold.robot
index 9b8b6ed44c8c72704d7489a64d89e25733a9f47a..85ef306834913363145ea67169c729ffadc518be 100644
--- a/SOL003/VNFPerformanceManagement-API/IndividualThreshold.robot
+++ b/SOL003/VNFPerformanceManagement-API/IndividualThreshold.robot
@@ -17,7 +17,7 @@ GET Individual Threshold
... Test title: GET Individual Threshold
... Test objective: The objective is to test the retrieval of an individual VNF performance threshold and perform a JSON schema and content validation of the collected threshold data structure
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance thresholds are set in the VNFM.
- ... Reference: Clause 6.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 6.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -32,7 +32,7 @@ GET Individual Threshold with invalid resource identifier
... Test title: GET Individual Threshold with invalid resource identifier
... Test objective: The objective is to test that the retrieval of an individual VNF performance threshold fails when using an invalid resource identifier
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance jobs are set in the VNFM.
- ... Reference: Clause 6.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 6.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -45,7 +45,7 @@ DELETE Individual Threshold
... Test title: DELETE Individual Threshold
... Test objective: The objective is to test the deletion of an individual VNF performance threshold
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance thresholds are set in the VNFM.
- ... Reference: Clause 6.4.6.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 6.4.6.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: The VNF Performance Threshold is not available anymore in the VNFM
@@ -58,7 +58,7 @@ DELETE Individual Threshold with invalid resource identifier
... Test title: DELETE Individual Threshold with invalid resource identifier
... Test objective: The objective is to test the deletion of an individual VNF performance threshold
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance thresholds are set in the VNFM.
- ... Reference: Clause 6.4.6.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 6.4.6.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -71,7 +71,7 @@ POST Individual Threshold - Method not implemented
... Test title: POST Individual Threshold - Method not implemented
... Test objective: The objective is to test that POST method is not allowed to create a new VNF Performance Threshold
... Pre-conditions: A VNF instance is instantiated
- ... Reference: Clause 6.4.6.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 6.4.6.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -83,7 +83,7 @@ PUT Individual Threshold - Method not implemented
... Test title: PUT Individual Threshold - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to update an existing VNF Performance threshold
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance thresholds are set in the VNFM.
- ... Reference: Clause 6.4.6.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 6.4.6.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -95,7 +95,7 @@ PATCH Individual Threshold
... Test title: PATCH Individual Threshold
... Test objective: The objective is to test that PATCH method allows to modify an Individual threshold resource.
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance thresholds are set in the VNFM.
- ... Reference: Clause 6.4.6.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 6.4.6.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions:
@@ -109,7 +109,7 @@ PATCH Individual Threshold - Precondition failed
... Test title: PATCH Individual Threshold - Preconition failed
... Test objective: The objective is to attempt to modify an individual threshold resource, where the precondition was not met.
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance jobs are set in the VNFM.
- ... Reference: Clause 6.4.6.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 6.4.6.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -122,11 +122,11 @@ PATCH Individual Threshold - Unprocessible Entity
... Test title: PATCH Individual Threshold - Unprocessible Entity
... Test objective: The objective is to test that PATCH method cannot modify an individual threshold resource when a request contains syntactically correct data but the data cannot be processed.
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance thresholds are set in the VNFM.
- ... Reference: Clause 6.4.6.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 6.4.6.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
- Send Patch request for individual VNF Performance Threshold with unprocessable entity
+ Send Patch request for individual VNF Performance Threshold with unprocessable content
Check HTTP Response Status Code Is 422
Check HTTP Response Body Json Schema Is ProblemDetails
@@ -215,7 +215,7 @@ Send Patch request for individual VNF Performance Threshold - Etag mismatch
${output}= Output response
Set Suite Variable ${response} ${output}
-Send Patch request for individual VNF Performance Threshold with unprocessable entity
+Send Patch request for individual VNF Performance Threshold with unprocessable content
Log Trying to PATCH threshold
Set Headers {"Accept":"${ACCEPT_JSON}"}
Set Headers {"Content-Type": "${CONTENT_TYPE_PATCH}"}
diff --git a/SOL003/VNFPerformanceManagement-API/NotificationEndpoint.robot b/SOL003/VNFPerformanceManagement-API/NotificationEndpoint.robot
index 9ff195f698d81f2400292282f099303c695a46ef..a72911e36314c63e4c1e9ff019c5ea88aba1380a 100644
--- a/SOL003/VNFPerformanceManagement-API/NotificationEndpoint.robot
+++ b/SOL003/VNFPerformanceManagement-API/NotificationEndpoint.robot
@@ -13,7 +13,7 @@ Performance Information Available Notification
... Test title: Performance Information Available Notification
... Test objective: The objective is to test that the POST request triggers Performance Information Available Notification.
... Pre-conditions: A VNF performance job is created, and a subscription for performance information available notification is available in the VNFM.
- ... Reference: Clause 6.4.9.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 6.4.9.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
@@ -25,7 +25,7 @@ Threshold Crossed Notification
... Test title: Threshold Crossed Notification
... Test objective: The objective is to test that the POST request triggers Threshold Crossed Notification
... Pre-conditions: A VNF performance job is created, and a subscription for threshold crossed notification is available in the VNFM.
- ... Reference: Clause 6.4.9.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 6.4.9.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFPerformanceManagement-API/Notifications.robot b/SOL003/VNFPerformanceManagement-API/Notifications.robot
index f31db000f2f36f0f9ccf167fec5224992d959ec8..5f5a3d398e624e7b46c2b9ea196ca672498445c2 100644
--- a/SOL003/VNFPerformanceManagement-API/Notifications.robot
+++ b/SOL003/VNFPerformanceManagement-API/Notifications.robot
@@ -16,7 +16,7 @@ VNF Performance Information Availability Notification
... Test title: VNF Performance Information Availability Notification
... Test objective: The objective is to test the dispatch of VNF Performance Information Availability Notification when new VNF performance information is available in the NFVO, and perform a JSON schema and content validation of the delivered notification. The action that triggers the notification under test is an explicit test step, but it is not performed by the test system.
... Pre-conditions: A VNF performance job is created, and a subscription for information availability notifications is available in the VNFM.
- ... Reference: Clause 6.4.9.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 6.4.9.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -29,7 +29,7 @@ VNF Threshold Crossed Notification
... Test title: VNF Threshold Crossed Notification
... Test objective: The objective is to test the dispatch of VNF Threshold Crossed Notification when a previously set VNF performance metric threshold is crossed, and perform a JSON schema and content validation of the delivered notification. The action that triggers the notification under test is an explicit test step, but it is not performed by the test system.
... Pre-conditions: A VNF performance job is created, and a threshold subscription is available in the VNFM.
- ... Reference: Clause 6.4.9.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 6.4.9.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFPerformanceManagement-API/PMJobs.robot b/SOL003/VNFPerformanceManagement-API/PMJobs.robot
index 539649d2dee739dfc2feec3e82a3bb163ca77e87..eb92ae2bc4b3d20be62a0dbdd96100730bc36ac1 100644
--- a/SOL003/VNFPerformanceManagement-API/PMJobs.robot
+++ b/SOL003/VNFPerformanceManagement-API/PMJobs.robot
@@ -18,7 +18,7 @@ GET all VNF Performance Monitoring Jobs
... Test title: GET all VNF Performance Monitoring Jobs
... Test objective: The objective is to test the retrieval of all the available VNF performance monitoring jobs and perform a JSON schema and content validation of the collected jobs data structure
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance jobs are set in the VNF.
- ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -32,7 +32,7 @@ GET VNF Performance Monitoring Jobs with attribute-based filter
... Test title: GET all VNF Performance Monitoring Jobs with attribute-based filter
... Test objective: The objective is to test the retrieval of VNF performance monitoring jobs using attribute-based filter, perform a JSON schema validation of the collected jobs data structure, and verify that the retrieved information matches the issued attribute-based filter
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance jobs are set in the VNF.
- ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -46,7 +46,7 @@ GET all VNF Performance Monitoring Jobs with all_fields attribute selector
... Test title: GET all VNF Performance Monitoring Jobs with all_fields attribute selector
... Test objective: The objective is to test the retrieval of all VNF performance monitoring jobs all_fields attribute selector, perform a JSON schema validation of the collected jobs data structure, and verify that the retrieved information matches the issued all_fileds selector
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance jobs are set in the VNF.
- ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -60,7 +60,7 @@ GET all VNF Performance Monitoring Jobs with exclude_default attribute selector
... Test title: GET all VNF Performance Monitoring Jobs with exclude_default attribute selector
... Test objective: The objective is to test the retrieval of all VNF performance monitoring jobs exclude_default attribute selector, perform a JSON schema validation of the collected jobs data structure, and verify that the retrieved information matches the issued exclude_default selector
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance jobs are set in the VNF.
- ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -74,7 +74,7 @@ GET all VNF Performance Monitoring Jobs with fields attribute selector
... Test title: GET all VNF Performance Monitoring Jobs with fields attribute selector
... Test objective: The objective is to test the retrieval of all VNF performance monitoring jobs fields attribute selector, perform a JSON schema validation of the collected jobs data structure, and verify that the retrieved information matches the issued fields selector
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance jobs are set in the VNF.
- ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: The VNFM supports the use of exclude_fields attribute selector
... Post-Conditions: none
@@ -88,7 +88,7 @@ GET all VNF Performance Monitoring Jobs with exclude_fields attribute selector
... Test title: GET all VNF Performance Monitoring Jobs with exclude_fields attribute selector
... Test objective: The objective is to test the retrieval of all VNF performance monitoring jobs exclude_fields attribute selector, perform a JSON schema validation of the collected jobs data structure, and verify that the retrieved information matches the issued exclude_fields selector
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance jobs are set in the VNF.
- ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: The VNFM supports the use of exclude_fields attribute selector
... Post-Conditions: none
@@ -102,7 +102,7 @@ GET VNF Performance Monitoring Jobs with invalid attribute-based filter
... Test title: GET VNF Performance Monitoring Jobs with invalid attribute-based filter
... Test objective: The objective is to test that the retrieval of VNF performance monitoring jobs fails when using invalid attribute-based filter, and perform the JSON schema validation of the failed operation HTTP response
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance jobs are set in the VNF.
- ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -115,7 +115,7 @@ GET VNF Performance Monitoring Jobs with invalid resource endpoint
... Test title: GET VNF Performance Monitoring Jobs with invalid resource endpoint
... Test objective: The objective is to test that the retrieval of VNF performance monitoring jobs fails when using invalid resource endpoint
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance jobs are set in the VNF.
- ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -127,7 +127,7 @@ Create new VNF Performance Monitoring Job
... Test title: Create a new VNF Performance Monitoring Job
... Test objective: The objective is to test the creation of a new VNF performance monitoring job and perform the JSON schema validation of the returned job data structure
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance jobs are set in the VNF.
- ... Reference: Clause 6.4.2.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 6.4.2.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: The VNF Performance Job is successfully created on the VNFM
@@ -141,7 +141,7 @@ PUT all VNF Performance Monitoring Jobs - Method not implemented
... Test title: PUT all VNF Performance Monitoring Jobs - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to modify VNF Performance Monitoring Jobs
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance jobs are set in the VNF.
- ... Reference: Clause 6.4.2.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 6.4.2.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -153,7 +153,7 @@ PATCH all VNF Performance Monitoring Jobs - (Method not implemented)
... Test title: PATCH all VNF Performance Monitoring Jobs - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update VNF Performance Monitoring Jobs
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance jobs are set in the VNF.
- ... Reference: Clause 6.4.2.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 6.4.2.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -165,7 +165,7 @@ DELETE all VNF Performance Monitoring Jobs - Method not implemented
... Test title: DELETE all VNF Performance Monitoring Jobs - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to update VNF Performance Monitoring Jobs
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance jobs are set in the VNF.
- ... Reference: Clause 6.4.2.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 6.4.2.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -178,7 +178,7 @@ GET all VNF Performance Monitoring Jobs as Paged Response
... Test title: GET all VNF Performance Monitoring Jobs as Paged Response
... Test objective: The objective is to test the retrieval of all the available VNF performance monitoring jobs as Paged Response.
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance jobs are set in the VNF.
- ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: The VNFM supports response paging for the VNF performance jobs resources
... Post-Conditions: none
@@ -191,7 +191,7 @@ GET all VNF Performance Monitoring Jobs as Paged Response with nextpage_opauque_
... Test title: GET all VNF Performance Monitoring Jobs as Paged Response with nextpage_opauque_marker parameter
... Test objective: The objective is to query information about all the available VNF performance monitoring jobs as a Paged Response and retrieve the next page using the nextpage_opaque_marker parameter
... Pre-conditions: A request for retrieving the available VNF performance monitoring jobs as a paged response has been successfully issued (Test ID 7.3.4.1.13)
- ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: The VNFM supports response paging for the VNF performance jobs resources
... Post-Conditions: none
@@ -203,7 +203,7 @@ GET VNF Performance Monitoring Jobs - Bad Request Response too Big
... Test title: GET VNF Performance Monitoring Jobs - Bad Request Response too Big
... Test objective: The objective is to test that the retrieval of VNF performance monitoring jobs fails because response is too big, and perform the JSON schema validation of the failed operation HTTP response.
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance jobs are set in the VNF.
- ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -216,7 +216,7 @@ GET all VNF Performance Monitoring Jobs with fields and exclude_default attribut
... Test title: GET all VNF Performance Monitoring Jobs with fields and exclude_default attribute selector
... Test objective: The objective is to test the retrieval of all VNF performance monitoring jobs fields and exclude_default attribute selector, perform a JSON schema validation of the collected jobs data structure, and verify that the retrieved information matches the issued fields selector
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance jobs are set in the VNF.
- ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: The VNFM supports the use of fields and exclude_fields attribute selector
... Post-Conditions: none
@@ -225,16 +225,16 @@ GET all VNF Performance Monitoring Jobs with fields and exclude_default attribut
Check HTTP Response Body Json Schema Is PmJobs
Check HTTP Response Body PmJobs Matches the requested fields selector
-POST Create new VNF Performance Monitoring Job - Unprocessable Entity
+POST Create new VNF Performance Monitoring Job - Unprocessable Content
[Documentation] Test ID: 7.3.4.1.16
- ... Test title: POST Create new VNF Performance Monitoring Job - Unprocessable Entity
+ ... Test title: POST Create new VNF Performance Monitoring Job - Unprocessable Content
... Test objective: The objective is to test the creation of a new VNF performance monitoring job fails when a request contains syntactically correct data but the data cannot be processed.
... Pre-conditions: none
- ... Reference: clause 6.4.2.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: clause 6.4.2.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
- Send Post Request for VNF Performance Monitoring Job with unprocessable entity
+ Send Post Request for VNF Performance Monitoring Job with unprocessable content
Check HTTP Response Status Code Is 422
Check HTTP Response Body Json Schema Is ProblemDetails
@@ -472,7 +472,7 @@ Check LINK in Header
${linkURL}= Get Value From Json ${response['headers']} $..Link
Should Not Be Empty ${linkURL}
-Send Post Request for VNF Performance Monitoring Job with unprocessable entity
+Send Post Request for VNF Performance Monitoring Job with unprocessable content
Log trying to create a new PM Job
Set Headers {"Accept": "${ACCEPT_JSON}"}
Set Headers {"Content-Type": "${CONTENT_TYPE_JSON}"}
diff --git a/SOL003/VNFPerformanceManagement-API/Thresholds.robot b/SOL003/VNFPerformanceManagement-API/Thresholds.robot
index ee0dca470d88e048e14363fedfa3a4f9e9ed8c6c..860f1025fee3b7cc03347cbcd2f8f9ea5fde8b1e 100644
--- a/SOL003/VNFPerformanceManagement-API/Thresholds.robot
+++ b/SOL003/VNFPerformanceManagement-API/Thresholds.robot
@@ -17,7 +17,7 @@ GET All Performance Thresholds
... Test title: GET All Performance Thresholds
... Test objective: The objective is to test the retrieval of all the available VNF performance thresholds and perform a JSON schema validation of the collected thresholds data structure
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance thresholds are set in the VNFM.
- ... Reference: Clause 6.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 6.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -30,7 +30,7 @@ GET Performance Thresholds with attribute-based filter
... Test title: GET Performance Thresholds with attribute-based filter
... Test objective: The objective is to test the retrieval of all the available VNF performance thresholds when using attribute-based filters, perform a JSON schema validation of the collected thresholds data structure, and verify that the retrieved information matches the issued attribute-based filter
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance thresholds are set in the VNFM.
- ... Reference: Clause 6.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 6.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -44,7 +44,7 @@ GET Performance Thresholds with invalid attribute-based filter
... Test title: GET Performance Thresholds with invalid attribute-based filter
... Test objective: The objective is to test that the retrieval of VNF performance thresholds fails when using invalid attribute-based filter, and perform the JSON schema validation of the failed operation HTTP response
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance thresholds are set in the VNFM.
- ... Reference: Clause 6.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 6.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -56,7 +56,7 @@ GET Performance Thresholds with invalid resource endpoint
... Test title: GET Performance Thresholds with invalid resource endpoint
... Test objective: The objective is to test that the retrieval of VNF performance thresholds fails when using invalid resource endpoint, and perform the JSON schema validation of the failed operation HTTP response
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance thresholds are set in the VNFM.
- ... Reference: Clause 6.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 6.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -69,7 +69,7 @@ Create new Performance Threshold
... Test title: Create new Performance Threshold
... Test objective: The objective is to test the creation of a new VNF performance threshold and perform the JSON schema validation of the returned threshold data structure
... Pre-conditions: A VNF instance is instantiated.
- ... Reference: Clause 6.4.5.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 6.4.5.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: The VNF Performance Threshold is successfully created on the VNFM
@@ -84,7 +84,7 @@ PUT Performance Thresholds - Method not implemented
... Test title: PUT Performance Thresholds - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to modify VNF Performance Thresholds
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance thresholds are set in the VNF.
- ... Reference: Clause 6.4.5.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 6.4.5.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -96,7 +96,7 @@ PATCH Performance Thresholds - Method not implemented
... Test title: PATCH Performance Thresholds - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to modify VNF Performance Thresholds
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance thresholds are set in the VNFM.
- ... Reference: Clause 6.4.5.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 6.4.5.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -108,7 +108,7 @@ DELETE Performance Thresholds - Method not implemented
... Test title: DELETE Performance Thresholds - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to update VNF Performance Thresholds
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance thresholds are set in the VNFM.
- ... Reference: Clause 6.4.5.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 6.4.5.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: The VNF performance thresholds are not deleted by the failed operation
@@ -121,7 +121,7 @@ GET All Performance Thresholds as Paged Response
... Test title: GET All Performance Thresholds as Paged Response
... Test objective: The objective is to test the retrieval of all the available VNF performance thresholds as a Paged Response.
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance thresholds are set in the VNFM.
- ... Reference: Clause 6.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 6.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -134,7 +134,7 @@ GET Performance Thresholds - Bad Request Response too Big
... Test title: GET Performance Thresholds - Bad Request Response too Big
... Test objective: The objective is to test that the retrieval of VNF performance thresholds fails because response is too big, and perform the JSON schema validation of the failed operation HTTP response
... Pre-conditions: A VNF instance is instantiated. One or more VNF performance thresholds are set in the VNFM.
- ... Reference: Clause 6.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 6.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -142,16 +142,16 @@ GET Performance Thresholds - Bad Request Response too Big
Check HTTP Response Status Code Is 400
Check HTTP Response Body Json Schema Is ProblemDetails
-POST create new Performance Threshold - Unprocessable Entity
+POST create new Performance Threshold - Unprocessable Content
[Documentation] Test ID: 7.3.4.4.11
- ... Test title: POST create new Performance Threshold - Unprocessable Entity
+ ... Test title: POST create new Performance Threshold - Unprocessable Content
... Test objective: The objective is to test that creation of new VNF performance threshold fails when a request contains syntactically correct data but the data cannot be processed.
... Pre-conditions: A VNF instance is instantiated.
- ... Reference: Clause 6.4.5.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 6.4.5.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
- Send Post Request Create new Performance Threshold with unprocessable entity
+ Send Post Request Create new Performance Threshold with unprocessable content
Check HTTP Response Status Code Is 422
Check HTTP Response Body Json Schema Is ProblemDetails
@@ -204,7 +204,7 @@ Send Post Request Create new Performance Threshold
${output}= Output response
Set Suite Variable ${response} ${output}
-Send Post Request Create new Performance Threshold with unprocessable entity
+Send Post Request Create new Performance Threshold with unprocessable content
Log trying to create a new Threshold
Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"${AUTHORIZATION_HEADER}":"${AUTHORIZATION_TOKEN}"}
Set Headers {"Accept": "${ACCEPT_JSON}"}
diff --git a/SOL003/VNFSnapshotPackageManagement-API/ApiVersion.robot b/SOL003/VNFSnapshotPackageManagement-API/ApiVersion.robot
index bec74efda5adb3a5e6a6625200cbddc39c303a7f..90f958e4df9ce1487abe08bbff0c0e86c5d5da64 100644
--- a/SOL003/VNFSnapshotPackageManagement-API/ApiVersion.robot
+++ b/SOL003/VNFSnapshotPackageManagement-API/ApiVersion.robot
@@ -7,7 +7,7 @@ POST API Version - Method not implemented
... Test title: POST API version - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -19,7 +19,7 @@ GET API Version
... Test title: GET API Version
... Test objective: The objective is to test that GET method successfully return ApiVersionInformation
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -32,7 +32,7 @@ PUT API Version - Method not implemented
... Test title: PUT API Version - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -44,7 +44,7 @@ PATCH API Version - Method not implemented
... Test title: PATCH API Version - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -56,7 +56,7 @@ DELETE API Version - Method not implemented
... Test title: DELETE API Version - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -68,7 +68,7 @@ POST API Version with apiMajorVerion - Method not implemented
... Test title: POST API version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -80,7 +80,7 @@ GET API Version with apiMajorVerion
... Test title: GET API Version with apiMajorVerion
... Test objective: The objective is to test that GET method successfully return ApiVersionInformation
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -93,7 +93,7 @@ PUT API Version with apiMajorVerion - Method not implemented
... Test title: PUT API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -105,7 +105,7 @@ PATCH API Version with apiMajorVerion - Method not implemented
... Test title: PATCH API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -117,7 +117,7 @@ DELETE API Version with apiMajorVerion - Method not implemented
... Test title: DELETE API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFSnapshotPackageManagement-API/IndividualVNFSnapshotPackage.robot b/SOL003/VNFSnapshotPackageManagement-API/IndividualVNFSnapshotPackage.robot
index 8417e9265c8af9451aae0c2eab6b2430a2ccdcaf..0fdcedc30796680edbf1e9ce8be7e38150b904fd 100644
--- a/SOL003/VNFSnapshotPackageManagement-API/IndividualVNFSnapshotPackage.robot
+++ b/SOL003/VNFSnapshotPackageManagement-API/IndividualVNFSnapshotPackage.robot
@@ -7,7 +7,7 @@ POST Individual VNF Snapshot Package - Method not implemented
... Test title: POST Individual VNF Snapshot Package - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 12.4.3.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 12.4.3.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -19,7 +19,7 @@ GET Information about an individual VNF Snapshot Package - SUCCESSFUL
... Test title: GET Information about an individual VNF Snapshot Package - SUCCESSFUL
... Test objective: The objective is to query information about a VNF Snapshot Package resource
... Pre-conditions: none
- ... Reference: Clause 12.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 12.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -32,7 +32,7 @@ GET Information about an individual VNF Snapshot Package - NOT FOUND
... Test title: GET Information about an individual VNF Snapshot Package - NOT FOUND
... Test objective: The objective is to test that the retrieval of individual VNF Snapshot Package fails when using an invalid resource identifier.
... Pre-conditions: At least one individual VNF Snapshot Package is available in the NFV-MANO.
- ... Reference: Clause 12.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 12.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -45,7 +45,7 @@ PUT Individual VNF Snapshot Package - Method not implemented
... Test title: PUT Individual VNF Snapshot Package - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 12.4.3.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 12.4.3.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: VNF Snapshot Package not modified
@@ -57,7 +57,7 @@ PATCH Individual VNF Snapshot Package - Method Not implemented
... Test title: PATCH Individual VNF Snapshot Package
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 12.4.3.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 12.4.3.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: VNF Snapshot Package modified
@@ -69,7 +69,7 @@ DELETE Individual VNF Snapshot Package - Method Not implemented
... Test title: DELETE Individual VNF Snapshot Package - Method Not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 12.4.3.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 12.4.3.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: VNF Snapshot Package deleted
diff --git a/SOL003/VNFSnapshotPackageManagement-API/IndividualVNFSnapshotPackageArtifact.robot b/SOL003/VNFSnapshotPackageManagement-API/IndividualVNFSnapshotPackageArtifact.robot
index 8dfa012839c420dde8eb2d347f9186fb18182a72..9c4b8bfc70741f78edd50a8ca4604629b6c9f641 100644
--- a/SOL003/VNFSnapshotPackageManagement-API/IndividualVNFSnapshotPackageArtifact.robot
+++ b/SOL003/VNFSnapshotPackageManagement-API/IndividualVNFSnapshotPackageArtifact.robot
@@ -7,7 +7,7 @@ POST Individual VNF Snapshot Package Artifact - Method not implemented
... Test title: POST Individual VNF Snapshot Package Artifact - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 12.4.5.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 12.4.5.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -19,7 +19,7 @@ GET Individual VNF Snapshot Package Artifact - Complete File
... Test title: GET Information about an individual VNF Snapshot Package - Complete File
... Test objective: The objective is to fetch the whole content of a VNF snapshot package using GET method.
... Pre-conditions: none
- ... Reference: Clause 12.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 12.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -32,7 +32,7 @@ GET Individual VNF Snapshot Package Artifact - Partial Content
... Test title: GET Individual VNF Snapshot Package Artifact - Partial Content
... Test objective: The objective is to fetch partial content of a VNF snapshot package by sending a range request using GET method.
... Pre-conditions: none
- ... Reference: Clause 12.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 12.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: NFVO supports range requests
... Post-Conditions: none
@@ -47,7 +47,7 @@ GET Individual VNF Snapshot Package Artifact - Range Request Not Supported
... Test title: GET Information about an individual VNF Snapshot Package - Range Request Not Supported
... Test objective: The objective is to test that the whole content of a VNF snapshot package is delivered even with a range request when NFVO does not support range requests.
... Pre-conditions: none
- ... Reference: Clause 12.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 12.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: NFVO does not support range requests
... Post-Conditions: none
@@ -60,7 +60,7 @@ GET Individual VNF Snapshot Package Artifact - Range Not Satisfiable
... Test title: GET Information about an individual VNF Snapshot Package - Range Not Satisfiable
... Test objective: The objective is to test that an error is returned when the byte range passed in the "Range" header does not match any available byte range in the VNF snapshot package file.
... Pre-conditions: none
- ... Reference: Clause 12.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 12.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: NFVO supports range requests
... Post-Conditions: none
@@ -72,7 +72,7 @@ GET Individual VNF Snapshot Package Artifact - Conflict
... Test title: GET Information about an individual VNF Snapshot Package - Conflict
... Test objective: The objective is to test that an error is returned when the "state" of the VNF snapshot package has a value different from "AVAILABLE".
... Pre-conditions: none
- ... Reference: Clause 12.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 12.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The "state" of the VNF snapshot package has a value different from "AVAILABLE".
... Post-Conditions: none
@@ -84,7 +84,7 @@ PUT Individual VNF Snapshot Package Artifact - Method not implemented
... Test title: PUT Individual VNF Snapshot Package Artifact - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 12.4.5.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 12.4.5.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: VNF Snapshot Package not modified
@@ -96,7 +96,7 @@ PATCH Individual VNF Snapshot Package Artifact - Method Not implemented
... Test title: PATCH Individual VNF Snapshot Package Artifact
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 12.4.5.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 12.4.5.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -108,7 +108,7 @@ DELETE Individual VNF Snapshot Package Artifact - Method Not implemented
... Test title: DELETE Individual VNF Snapshot Package Artifact - Method Not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 12.4.5.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 12.4.5.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFSnapshotPackageManagement-API/VNFSnapshotPackageContent.robot b/SOL003/VNFSnapshotPackageManagement-API/VNFSnapshotPackageContent.robot
index 96f55612fe8f5b39e3a0a334db3ac2b448b75192..0b9d7b1d56e4a30b938dc53a26f55352e5610bb0 100644
--- a/SOL003/VNFSnapshotPackageManagement-API/VNFSnapshotPackageContent.robot
+++ b/SOL003/VNFSnapshotPackageManagement-API/VNFSnapshotPackageContent.robot
@@ -7,7 +7,7 @@ POST VNF Snapshot Package Content - Method not implemented
... Test title: POST VNF Snapshot Package Content - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 12.4.4.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 12.4.4.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -19,7 +19,7 @@ GET VNF Snapshot Package Content - Complete File
... Test title: GET Information about an individual VNF Snapshot Package - Complete File
... Test objective: The objective is to fetch the whole content of a VNF snapshot package using GET method.
... Pre-conditions: none
- ... Reference: Clause 12.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 12.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -32,7 +32,7 @@ GET VNF Snapshot Package Content - Partial Content
... Test title: GET VNF Snapshot Package Content - Partial Content
... Test objective: The objective is to fetch partial content of a VNF snapshot package by sending a range request using GET method.
... Pre-conditions: none
- ... Reference: Clause 12.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 12.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: NFVO supports range requests
... Post-Conditions: none
@@ -47,7 +47,7 @@ GET VNF Snapshot Package Content - Range Request Not Supported
... Test title: GET Information about an individual VNF Snapshot Package - Range Request Not Supported
... Test objective: The objective is to test that the whole content of a VNF snapshot package is delivered even with a range request when NFVO does not support range requests.
... Pre-conditions: none
- ... Reference: Clause 12.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 12.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: NFVO does not support range requests
... Post-Conditions: none
@@ -60,7 +60,7 @@ GET VNF Snapshot Package Content - Range Not Satisfiable
... Test title: GET Information about an individual VNF Snapshot Package - Range Not Satisfiable
... Test objective: The objective is to test that an error is returned when the byte range passed in the "Range" header does not match any available byte range in the VNF snapshot package file.
... Pre-conditions: none
- ... Reference: Clause 12.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 12.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: NFVO supports range requests
... Post-Conditions: none
@@ -72,7 +72,7 @@ GET VNF Snapshot Package Content - Conflict
... Test title: GET Information about an individual VNF Snapshot Package - Conflict
... Test objective: The objective is to test that an error is returned when the "state" of the VNF snapshot package has a value different from "AVAILABLE".
... Pre-conditions: none
- ... Reference: Clause 12.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 12.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The "state" of the VNF snapshot package has a value different from "AVAILABLE".
... Post-Conditions: none
@@ -84,7 +84,7 @@ PUT VNF Snapshot Package Content - Method not implemented
... Test title: PUT VNF Snapshot Package Content - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 12.4.4.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 12.4.4.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: VNF Snapshot Package not modified
@@ -96,7 +96,7 @@ PATCH VNF Snapshot Package Content - Method Not implemented
... Test title: PATCH VNF Snapshot Package Content
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 12.4.4.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 12.4.4.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -108,7 +108,7 @@ DELETE VNF Snapshot Package Content - Method Not implemented
... Test title: DELETE VNF Snapshot Package Content - Method Not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 12.4.4.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 12.4.4.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFSnapshotPackageManagement-API/VNFSnapshotPackages.robot b/SOL003/VNFSnapshotPackageManagement-API/VNFSnapshotPackages.robot
index 28e47facd7657c16b0c8cf59da0a4d7f87e2fa63..6c3f2c1c4a44d32fc1d8d6c79ed24e9652df5bdd 100644
--- a/SOL003/VNFSnapshotPackageManagement-API/VNFSnapshotPackages.robot
+++ b/SOL003/VNFSnapshotPackageManagement-API/VNFSnapshotPackages.robot
@@ -7,7 +7,7 @@ POST VNF Snapshot Packages - Method not implemented
... Test title: POST VNF Snapshot Packages - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 12.4.2.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 12.4.2.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -19,7 +19,7 @@ GET information about multiple VNF Snapshot Packages
... Test title: GET information about multiple VNF Snapshot Packages
... Test objective: The objective is to get information about multiples VNF Snapshot Packages
... Pre-conditions: none
- ... Reference: Clause 12.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 12.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -32,7 +32,7 @@ GET information about multiple VNF Snapshot Packages Bad Request Invalid attribu
... Test title: GET information about multiple VNF Snapshot Packages Bad Request Invalid attribute-based filtering parameters
... Test objective: The objective is to get information about multiples VNF Snapshot Packages with Invalid attribute-based filtering parameters
... Pre-conditions: none
- ... Reference: Clause 12.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 12.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -45,7 +45,7 @@ GET information about multiple VNF Snapshot Packages Bad Request Invalid attribu
... Test title: GET information about multiple VNF Snapshot Packages Bad Request Invalid attribute selector
... Test objective: The objective is to get information about multiples VNF Snapshot Packages with Invalid attribute-based filtering parameters
... Pre-conditions: none
- ... Reference: Clause 12.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 12.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -58,7 +58,7 @@ GET information about multiple VNF Snapshot Packages with "all_fields" attribute
... Test title: GET information about multiple VNF Snapshot Packages with "all_fields" attribute selector
... Test objective: The objective is to query information about multiple VNF Snapshot Packages
... Pre-conditions: none
- ... Reference: Clause 12.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 12.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -71,7 +71,7 @@ GET information about multiple VNF Snapshot Packages with "exclude_default" attr
... Test title: GET information about multiple VNF Snapshot Packages with "exclude_default" attribute selector
... Test objective: The objective is to query information about multiple VNF Snapshot Packages
... Pre-conditions: none
- ... Reference: Clause 12.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 12.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -84,7 +84,7 @@ GET information about multiple VNF Snapshot Packages with "fields" attribute sel
... Test title: GET information about multiple VNF Snapshot Packages with "fields" attribute selector
... Test objective: The objective is to query information about multiple VNF Snapshot Packages
... Pre-conditions: none
- ... Reference: Clause 12.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 12.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -97,7 +97,7 @@ GET information about multiple VNF Snapshot Packages with "exclude_default" and
... Test title: GET information about multiple VNF Snapshot Packages with "exclude_default" and "fields" attribute selector
... Test objective: The objective is to query information about multiple VNF Snapshot Packages
... Pre-conditions: none
- ... Reference: Clause 12.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 12.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -110,7 +110,7 @@ GET information about multiple VNF Snapshot Packages with "exclude_fields" attri
... Test title: GET information about multiple VNF Snapshot Packages with "exclude_fields" attribute selector
... Test objective: The objective is to query information about multiple VNF Snapshot Packages
... Pre-conditions: none
- ... Reference: Clause 12.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 12.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -123,7 +123,7 @@ GET VNF Snapshot Packages - Bad Request Response too Big
... Test title: GET VNF Snapshot Packages - Bad Request Response too Big
... Test objective: The objective is test that the retrieval of existing VNF Snapshot Packages list fails because response is too big, and perform the JSON schema validation of the failed operation HTTP response.
... Pre-conditions: none
- ... Reference: Clause 12.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 12.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: NFVO does not support paged response.
... Post-Conditions: none
@@ -136,7 +136,7 @@ GET VNF Snapshot Packages as Paged Response
... Test title: GET VNF Snapshot Packages as Paged Response
... Test objective: The objective is to test that GET method retrieves the list of existing VNF Snapshot Packages as paged response.
... Pre-conditions: none
- ... Reference: Clause 12.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 12.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: NFVO supports paged response.
... Post-Conditions: none
@@ -149,7 +149,7 @@ PUT VNF Snapshot Packages - Method not implemented
... Test title: PUT VNF Snapshot Packages - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 12.4.2.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 12.4.2.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -161,7 +161,7 @@ PATCH VNF Snapshot Packages - Method not implemented
... Test title: PATCH VNF Snapshot Packages - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 12.4.2.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 12.4.2.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -173,7 +173,7 @@ DELETE VNF Snapshot Packages - Method not implemented
... Test title: DELETE VNF Snapshot Packages - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 12.4.2.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 12.4.2.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: VNF snapshot package is not deleted
@@ -185,7 +185,7 @@ GET information about multiple VNF Snapshot Packages using filter
... Test title: GET information about multiple VNF Snapshot Packages using filter
... Test objective: The objective is to get information about multiples VNF Snapshot Packages using filter
... Pre-conditions: none
- ... Reference: Clause 12.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 12.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VirtualisedResourcesQuotaAvailableNotification-API/ApiVersion.robot b/SOL003/VirtualisedResourcesQuotaAvailableNotification-API/ApiVersion.robot
index ded892a98e75b4f0c38d29efde4dcc81c03e1e57..9f09365b5112d8dbabc09302d596d926fc7588dd 100644
--- a/SOL003/VirtualisedResourcesQuotaAvailableNotification-API/ApiVersion.robot
+++ b/SOL003/VirtualisedResourcesQuotaAvailableNotification-API/ApiVersion.robot
@@ -11,7 +11,7 @@ POST API Version - Method not implemented
... Test title: POST API version - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -23,7 +23,7 @@ GET API Version
... Test title: GET API Version
... Test objective: The objective is to test that GET method successfully return ApiVersionInformation
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -36,7 +36,7 @@ PUT API Version - Method not implemented
... Test title: PUT API Version - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -48,7 +48,7 @@ PATCH API Version - Method not implemented
... Test title: PATCH API Version - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -60,7 +60,7 @@ DELETE API Version - Method not implemented
... Test title: DELETE API Version - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -72,7 +72,7 @@ POST API Version with apiMajorVerion - Method not implemented
... Test title: POST API version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -84,7 +84,7 @@ GET API Version with apiMajorVerion
... Test title: GET API Version with apiMajorVerion
... Test objective: The objective is to test that GET method successfully return ApiVersionInformation
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -97,7 +97,7 @@ PUT API Version with apiMajorVerion - Method not implemented
... Test title: PUT API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -109,7 +109,7 @@ PATCH API Version with apiMajorVerion - Method not implemented
... Test title: PATCH API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -121,7 +121,7 @@ DELETE API Version with apiMajorVerion - Method not implemented
... Test title: DELETE API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VirtualisedResourcesQuotaAvailableNotification-API/IndividualSubscription.robot b/SOL003/VirtualisedResourcesQuotaAvailableNotification-API/IndividualSubscription.robot
index 4aac234ce7ce51b35619e952c8e72ca0cb622b2e..3f81fd02a30f66c269679d5ad13c886f4afc09f1 100644
--- a/SOL003/VirtualisedResourcesQuotaAvailableNotification-API/IndividualSubscription.robot
+++ b/SOL003/VirtualisedResourcesQuotaAvailableNotification-API/IndividualSubscription.robot
@@ -15,7 +15,7 @@ Create new Virtualised Resources Quota Available Notification individual subscri
... Test title: Create new Virtualised Resources Quota Available Notification individual subscription - Method not implemented
... Test objective: The objective is to test that POST method is not allowed to create a new Virtualised Resources Quota Available Notification individual subscription instance on VNF
... Pre-conditions: A VNF instance is instantiated
- ... Reference: Clause 11.4.3.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 11.4.3.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -27,7 +27,7 @@ Get Information about an individual subscription
... Test title: Get Information about an individual subscription
... Test objective: The objective is to read an individual Virtualised Resources Quota Available Notification subscription subscribed by the client and perform a JSON schema and content validation of the returned individual subscription data structure
... Pre-conditions: The subscription with the given id exists
- ... Reference: Clause 11.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 11.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -40,7 +40,7 @@ PUT an individual subscription - Method not implemented
... Test title: PUT an individual subscription - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to update a existing Virtualised Resources Quota Available Notification individual subscription instance on VNF
... Pre-conditions: A VNF instance is instantiated
- ... Reference: Clause 11.4.3.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 11.4.3.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -52,7 +52,7 @@ PATCH an individual subscription - Method not implemented
... Test title: PATCH an individual subscription - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to modify a existing Virtualised Resources Quota Available Notification individual subscription instance on VNF
... Pre-conditions: A VNF instance is instantiated
- ... Reference: Clause 11.4.3.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 11.4.3.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -64,7 +64,7 @@ DELETE an individual subscription
... Test title: DELETE an individual subscription
... Test objective: The objective is to test that Delete method is allowed to remove a existing Virtualised Resources Quota Available Notification individual subscription instance on VNF
... Pre-conditions: The subscription with the given id exists
- ... Reference: Clause 11.4.3.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 11.4.3.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -77,7 +77,7 @@ Get Information about an individual subscription - Not Found
... Test title: Get Information about an individual subscription - Not Found
... Test objective: The objective is to test that the retrieval of an individual Virtualised Resources Quota Available Notification subscription subscribed by the client fils when resource is not present
... Pre-conditions: The subscription with the given id does not exists
- ... Reference: Clause 11.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 11.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VirtualisedResourcesQuotaAvailableNotification-API/NotificationEndpoint.robot b/SOL003/VirtualisedResourcesQuotaAvailableNotification-API/NotificationEndpoint.robot
index 8b3ad2f081ab4ed54fd561073b3d27c6a9368f70..1b072bbf9e8571cb6ec2fa64bb57c1ff2138fbbb 100644
--- a/SOL003/VirtualisedResourcesQuotaAvailableNotification-API/NotificationEndpoint.robot
+++ b/SOL003/VirtualisedResourcesQuotaAvailableNotification-API/NotificationEndpoint.robot
@@ -13,7 +13,7 @@ Vr Quota Availibility Notification
... Test title: Vr Quota Availibility Notification
... Test objective: The objective is to test that Vr Quota Availibility Notification is delivered with success to the notification consumer
... Pre-conditions: The VNF has subscribed to the Vr Quota Availibility resource
- ... Reference: Clause 11.4.4.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 11.4.4.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VirtualisedResourcesQuotaAvailableNotification-API/Notifications.robot b/SOL003/VirtualisedResourcesQuotaAvailableNotification-API/Notifications.robot
index 24f1c21e83f268363ad64926d642665f2fc90859..b405cca894a14ebb3b0b19d6d6d735a8c3ac4d41 100644
--- a/SOL003/VirtualisedResourcesQuotaAvailableNotification-API/Notifications.robot
+++ b/SOL003/VirtualisedResourcesQuotaAvailableNotification-API/Notifications.robot
@@ -13,7 +13,7 @@ Virtualised Resource Quota Available Notification
... Test title: Virtualised Resource Quota Available Notification
... Test objective: The objective is to test the dispatch of Virtualised Resource Quota Available Notification, and perform a JSON schema and content validation of the delivered notification. The action that triggers the notification under test is an explicit test step, but it is not performed by the test system.
... Pre-conditions: A subscription for Virtualised Resource Quota Available Notification is available in the VNFM.
- ... Reference: Clause 11.4.4.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 11.4.4.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VirtualisedResourcesQuotaAvailableNotification-API/Subscriptions.robot b/SOL003/VirtualisedResourcesQuotaAvailableNotification-API/Subscriptions.robot
index 4b23bc3bd77993d16f6d246effa93cec21afbfa6..c8c47165135b46f8d06377c1dcc316fbc966cacd 100644
--- a/SOL003/VirtualisedResourcesQuotaAvailableNotification-API/Subscriptions.robot
+++ b/SOL003/VirtualisedResourcesQuotaAvailableNotification-API/Subscriptions.robot
@@ -15,7 +15,7 @@ Create new Virtualised Resources Quota Available Notification subscription
... Test title: Create new Virtualised Resources Quota Available Notification subscription
... Test objective: The objective is to create a new Virtualised Resources Quota Available Notification subscription and perform a JSON schema and content validation of the returned subscription data structure
... Pre-conditions: no subscription with the same filter and callback Uri exists
- ... Reference: Clause 11.4.2.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 11.4.2.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -29,7 +29,7 @@ Create new Virtualised Resources Quota Available Notification subscription - DUP
... Test title: Create new Virtualised Resources Quota Available Notification subscription - DUPLICATION
... Test objective: The objective is to create a new Virtualised Resources Quota Available Notification subscription and perform a JSON schema and content validation of the returned duplicated subscription data structure
... Pre-conditions: subscription with the same filter and callback Uri exists
- ... Reference: Clause 11.4.2.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 11.4.2.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: the VNFM allows creating a subscription resource if another subscription resource with the same filter and callbackUri already exists
... Post-Conditions: none
@@ -43,7 +43,7 @@ Create new Virtualised Resources Quota Available Notification subscription - NO-
... Test title: Create new Virtualised Resources Quota Available Notification subscription - NO-DUPLICATION
... Test objective: The objective is to create a nduplicated Virtualised Resources Quota Available Notification subscription and verify that the VNF does not allow duplication
... Pre-conditions: subscription with the same filter and callback Uri exists
- ... Reference: Clause 11.4.2.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 11.4.2.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: the VNFM decides to not create a duplicate subscription resource
... Post-Conditions: none
@@ -56,7 +56,7 @@ GET Virtualised Resources Quota Available Notification Subscriptions
... Test title: GET Virtualised Resources Quota Available Notification Subscriptions
... Test objective: The objective is to retrieve the list of active Virtualised Resources Quota Available Notification subscriptions and perform a JSON schema and content validation of the returned subscriptions data structure
... Pre-conditions: none
- ... Reference: Clause 11.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 11.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -69,7 +69,7 @@ GET Virtualised Resources Quota Available Notification Subscriptions with attrib
... Test title: GET Virtualised Resources Quota Available Notification Subscriptions with attribute-based Filter
... Test objective: The objective is to retrieve the list of active Virtualised Resources Quota Available Notification subscriptions and perform a JSON schema and content validation of the returned subscriptions data structure, and verify that the retrieved information matches the issued attribute-based filters
... Pre-conditions: none
- ... Reference: Clause 11.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 11.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -82,7 +82,7 @@ GET Virtualised Resources Quota Available Notification subscriptions - Bad Reque
... Test title: GET Virtualised Resources Quota Available Notification subscriptions - Bad Request Invalid attribute-based filtering parameters
... Test objective: The objective is to retrieve the list of active Virtualised Resources Quota Available Notification subscriptions with invalid attribute-based filtering parameters, and verify that problem details are returned
... Pre-conditions: none
- ... Reference: Clause 11.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 11.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -95,7 +95,7 @@ PUT Virtualised Resources Quota Available Notification subscriptions - Method no
... Test title: PUT Virtualised Resources Quota Available Notification subscriptions - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to update existing Virtualised Resources Quota Available Notification subscriptions instance on VNF
... Pre-conditions: A VNF instance is instantiated
- ... Reference: Clause 11.4.2.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 11.4.2.3.3 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -107,7 +107,7 @@ PATCH Virtualised Resources Quota Available Notification subscriptions - Method
... Test title: PATCH Virtualised Resources Quota Available Notification subscriptions - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to modify Virtualised Resources Quota Available Notification subscriptions instance on VNF
... Pre-conditions: A VNF instance is instantiated
- ... Reference: Clause 11.4.2.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 11.4.2.3.4 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -119,7 +119,7 @@ DELETE Virtualised Resources Quota Available Notification subscriptions - Method
... Test title: DELETE Virtualised Resources Quota Available Notification subscriptions - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to delete Virtualised Resources Quota Available Notification subscriptions instance on VNF
... Pre-conditions: A VNF instance is instantiated
- ... Reference: Clause 11.4.2.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 11.4.2.3.5 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -131,7 +131,7 @@ GET Virtualised Resources Quota Available Notification Subscriptions as Paged Re
... Test title: GET Virtualised Resources Quota Available Notification Subscriptions as Paged Response
... Test objective: The objective is to retrieve the list of active Virtualised Resources Quota Available Notification subscriptions as a Paged Response.
... Pre-conditions: none
- ... Reference: Clause 11.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 11.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: The VNFM supports response paging for the subscription resources
... Post-Conditions: none
@@ -144,7 +144,7 @@ GET Virtualised Resources Quota Available Notification Subscriptions as Paged Re
... Test title: GET Virtualised Resources Quota Available Notification Subscriptions as Paged Response with nextpage_opauque_marker parameter
... Test objective: The objective is to query the list of active Virtualised Resources Quota Available Notification subscriptions as a Paged Response and retrieve the next page using the nextpage_opaque_marker parameter
... Pre-conditions: A request for retrieving the list of active Virtualised Resources Quota Available Notification subscriptions as a paged response has been successfully issued (Test ID 7.3.7.1.10)
- ... Reference: Clause 11.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 11.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: The VNFM supports response paging for the subscription resources
... Post-Conditions: none
@@ -156,7 +156,7 @@ GET Virtualised Resources Quota Available Notification subscriptions - Bad Reque
... Test title: GET Virtualised Resources Quota Available Notification subscriptions - Bad Request Response too Big
... Test objective: The objective is to test that the retrieval of active Virtualised Resources Quota Available Notification subscriptions list fails because response is too big, and verify that problem details are returned
... Pre-conditions: none
- ... Reference: Clause 11.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 11.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -164,12 +164,12 @@ GET Virtualised Resources Quota Available Notification subscriptions - Bad Reque
Check HTTP Response Status Code Is 400
Check HTTP Response Body Json Schema Is ProblemDetails
-Create new Virtualised Resources Quota Available Notification Subscription - Unprocessable Entity
+Create new Virtualised Resources Quota Available Notification Subscription - Unprocessable Content
[Documentation] Test ID: 7.3.7.1.12
- ... Test title: Create new Virtualised Resources Quota Available Notification Subscription - Unprocessable Entity
- ... Test objective: The objective is to test that 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.
+ ... Test title: Create new Virtualised Resources Quota Available Notification Subscription - Unprocessable Content
+ ... Test objective: The objective is to test that content type of the message content is supported and the message content of a request contains syntactically correct data but the data cannot be processed.
... re-conditions: none
- ... Reference: Clause 11.4.2.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
+ ... Reference: Clause 11.4.2.3.1 - ETSI GS NFV-SOL 003 [1] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/NFVICapacityInformation-API/ApiVersion.robot b/SOL005/NFVICapacityInformation-API/ApiVersion.robot
index 7565b18839f951bdc624e10082f1cdd91a3115db..f6c9b672672067ff8de429c5d46d5e951e3cb862 100644
--- a/SOL005/NFVICapacityInformation-API/ApiVersion.robot
+++ b/SOL005/NFVICapacityInformation-API/ApiVersion.robot
@@ -7,7 +7,7 @@ POST API Version - Method not implemented
... Test title: POST API version - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -19,7 +19,7 @@ GET API Version
... Test title: GET API Version
... Test objective: The objective is to test that GET method successfully return ApiVersionInformation
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -32,7 +32,7 @@ PUT API Version - Method not implemented
... Test title: PUT API Version - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -44,7 +44,7 @@ PATCH API Version - Method not implemented
... Test title: PATCH API Version - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -56,7 +56,7 @@ DELETE API Version - Method not implemented
... Test title: DELETE API Version - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -68,7 +68,7 @@ POST API Version with apiMajorVerion - Method not implemented
... Test title: POST API version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -80,7 +80,7 @@ GET API Version with apiMajorVerion
... Test title: GET API Version with apiMajorVerion
... Test objective: The objective is to test that GET method successfully return ApiVersionInformation
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -93,7 +93,7 @@ PUT API Version with apiMajorVerion - Method not implemented
... Test title: PUT API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -105,7 +105,7 @@ PATCH API Version with apiMajorVerion - Method not implemented
... Test title: PATCH API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -117,7 +117,7 @@ DELETE API Version with apiMajorVerion - Method not implemented
... Test title: DELETE API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/NFVICapacityInformation-API/CapacityThresholds.robot b/SOL005/NFVICapacityInformation-API/CapacityThresholds.robot
index c0575ad034a5c80f1109d3f49db25270b733bf22..9584b54d384f8689bc98645b7bd1e43174d0eb5c 100644
--- a/SOL005/NFVICapacityInformation-API/CapacityThresholds.robot
+++ b/SOL005/NFVICapacityInformation-API/CapacityThresholds.robot
@@ -7,7 +7,7 @@ POST Create Capacity Threshold
... Test title: POST Create Capacity Threshold
... Test objective: The objective is to test that POST method creates a Capacity Threshold
... Pre-conditions: none
- ... Reference: Clause 10.4.4.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 10.4.4.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -16,12 +16,12 @@ POST Create Capacity Threshold
Check HTTP Response Body Json Schema Is CapacityThreshold
Check HTTP Response Contains Resource URI
-POST Create Capacity Threshold - Unprocessible Entity
+POST Create Capacity Threshold - Unprocessible Content
[Documentation] Test ID: 5.3.6.5.2
- ... Test title: POST Create Capacity Threshold - Unprocessible Entity
+ ... Test title: POST Create Capacity Threshold - Unprocessible Content
... Test objective: The objective is to test that POST method creates a Capacity Threshold
... Pre-conditions: none
- ... Reference: Clause 10.4.4.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 10.4.4.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -34,7 +34,7 @@ GET Capacity Thresholds
... Test title: GET Capacity Thresholds
... Test objective: The objective is to GET Capacity Thresholds objects
... Pre-conditions: none
- ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -47,7 +47,7 @@ GET Capacity Thresholds - Filter
... Test title: GET Capacity Thresholds - Filter
... Test objective: The objective is to GET Capacity Thresholds objects using filter
... Pre-conditions: none
- ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -60,7 +60,7 @@ GET Capacity Thresholds Bad Request Invalid attribute-based filtering parameters
... Test title: GET Capacity Thresholds Bad Request Invalid attribute-based filtering parameters
... Test objective: The objective is to get information about Capacity Thresholds with Invalid attribute-based filtering parameters
... Pre-conditions: none
- ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -73,7 +73,7 @@ GET Capacity Thresholds - Bad Request Response too Big
... Test title: GET Capacity Thresholds - Bad Request Response too Big
... Test objective: The objective is test that the retrieval of existing Capacity Thresholds list fails because response is too big, and perform the JSON schema validation of the failed operation HTTP response.
... Pre-conditions: none
- ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: NFVO does not support paged response.
... Post-Conditions: none
@@ -86,7 +86,7 @@ GET Capacity Thresholds as Paged Response
... Test title: GET Capacity Thresholds as Paged Response
... Test objective: The objective is to test that GET method retrieves the list of existing Capacity Thresholds as paged response.
... Pre-conditions: none
- ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: NFVO supports paged response.
... Post-Conditions: none
@@ -99,7 +99,7 @@ PUT Capacity Thresholds - Method not implemented
... Test title: PUT Capacity Thresholds - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 10.4.4.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 10.4.4.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -111,7 +111,7 @@ PATCH Capacity Thresholds - Method not implemented
... Test title: PATCH Capacity Thresholds - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 10.4.4.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 10.4.4.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -123,7 +123,7 @@ DELETE Capacity Thresholds - Method not implemented
... Test title: DELETE Capacity Thresholds - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 10.4.4.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 10.4.4.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/NFVICapacityInformation-API/IndividualCapacityThreshold.robot b/SOL005/NFVICapacityInformation-API/IndividualCapacityThreshold.robot
index e70d34dfce03dd7b18235b2218ace22c61da3e20..3c6051eaf124aae1d306a4c83c6b9e987281478d 100644
--- a/SOL005/NFVICapacityInformation-API/IndividualCapacityThreshold.robot
+++ b/SOL005/NFVICapacityInformation-API/IndividualCapacityThreshold.robot
@@ -7,7 +7,7 @@ POST Individual Capacity Threshold
... Test title: POST Individual Capacity Threshold
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 10.4.5.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 10.4.5.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -19,7 +19,7 @@ GET Individual Capacity Thresholds
... Test title: GET Capacity Thresholds
... Test objective: The objective is to test that GET method reads information about Individual Capacity Threshold
... Pre-conditions: none
- ... Reference: Clause 10.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 10.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -32,7 +32,7 @@ GET Individual Capacity Thresholds - NOT FOUND
... Test title: GET Capacity Thresholds - NOT FOUND
... Test objective: The objective is to test that GET method returns an error when using and invalid URI
... Pre-conditions: none
- ... Reference: Clause 10.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 10.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -45,7 +45,7 @@ PUT Individual Capacity Threshold - Method not implemented
... Test title: PUT Capacity Thresholds - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 10.4.5.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 10.4.5.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -57,7 +57,7 @@ PATCH Individual Capacity Threshold - Success
... Test title: PATCH Individual Capacity Threshold - Success
... Test objective: The objective is to test that PATCH method successfully modifies an individual Capacity Threshold resource
... Pre-conditions: none
- ... Reference: Clause 10.4.5.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 10.4.5.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: Capacity Threshold modified
@@ -70,20 +70,33 @@ PATCH Individual Capacity Threshold - Precondition Failed
... Test title: PATCH Individual Capacity Threshold - Precondition Failed
... Test objective: The objective is to that the modification of individual Capacity Threshold fails because precondition given in an HTTP request header is not fulfilled due to an ETag mismatch.
... Pre-conditions: none
- ... Reference: Clause 10.4.5.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 10.4.5.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
PATCH Individual Capacity Threshold - ETag Mismatch
Check HTTP Response Status Code Is 412
Check HTTP Response Body Json Schema Is ProblemDetails
+
+PATCH Individual Capacity Threshold - Precondition Failed HTTP Conditional Request Not Supported
+ [Documentation] Test ID: 5.3.6.4.6b
+ ... Test title: PATCH Individual Capacity Threshold - Precondition Failed HTTP Conditional Request Not Supported
+ ... Test objective: The objective is to that the modification of individual Capacity Threshold fails because the API Producer does not support "Last-Modified" and "ETag" HTTP Headers
+ ... Pre-conditions: none
+ ... Reference: Clause 10.4.5.3.4, 4.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
+ ... Config ID: Config_prod_NFVO
+ ... Applicability: API Producer does not support "Last-Modified" and "ETag" HTTP Headers
+ ... Post-Conditions: none
+ PATCH Individual Capacity Threshold - HTTP Conditional Request not supported
+ Check HTTP Response Status Code Is 412
+ Check HTTP Response Body Json Schema Is ProblemDetails
-PATCH Individual Capacity Threshold - Unprocessible Entity
+PATCH Individual Capacity Threshold - Unprocessable Content
[Documentation] Test ID: 5.3.6.4.7
- ... Test title: PATCH Individual Capacity Threshold - Precondition Failed
+ ... Test title: PATCH Individual Capacity Threshold - Unprocessable Content
... Test objective: The objective is to that the modification of individual Capacity Threshold fails because callbackUri provided in the request body is unreachable.
... Pre-conditions: none
- ... Reference: Clause 10.4.5.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 10.4.5.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -96,10 +109,10 @@ DELETE Individual Capacity Threshold
... Test title: DELETE Individual Capacity Threshold
... Test objective: The objective is to delete an Individual Capacity Threshold
... Pre-conditions: none
- ... Reference: Clause 10.4.5.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 10.4.5.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: Capacity threshold is deleted
DELETE Individual Capacity Threshold
Check HTTP Response Status Code Is 204
- Check Postcondition resource is deleted
\ No newline at end of file
+ Check Postcondition resource is deleted
diff --git a/SOL005/NFVICapacityInformation-API/IndividualVIMsNFVICapacityInformation.robot b/SOL005/NFVICapacityInformation-API/IndividualVIMsNFVICapacityInformation.robot
index bcacd63c06ae87b5a1f1b77b09cefb52a6a2cb48..68e2fdf49445fe31dad0d6f8ba6d4cb41c123980 100644
--- a/SOL005/NFVICapacityInformation-API/IndividualVIMsNFVICapacityInformation.robot
+++ b/SOL005/NFVICapacityInformation-API/IndividualVIMsNFVICapacityInformation.robot
@@ -7,7 +7,7 @@ POST Individual VIMs NFVI Capacity Information - Method not implemented
... Test title: POST Individual VIMs NFVI Capacity Information - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 10.4.3.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 10.4.3.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -19,7 +19,7 @@ GET Information about an Individual VIMs NFVI Capacity Information
... Test title: GET Information about an Individual VIMs NFVI Capacity Information
... Test objective: The objective is to retrieve information about Individual VIMs NFVI Capacity Information
... Pre-conditions: none
- ... Reference: Clause 10.4.3.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 10.4.3.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -32,7 +32,7 @@ GET Information about an Individual VIMs NFVI Capacity Information using filter
... Test title: GET Information about an Individual VIMs NFVI Capacity Information using filter query parameter
... Test objective: The objective is to retrieve information about Individual VIMs NFVI Capacity Information using filter query parameter
... Pre-conditions: none
- ... Reference: Clause 10.4.3.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 10.4.3.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -45,7 +45,7 @@ GET Information about an Individual VIMs NFVI Capacity Information - NOT FOUND
... Test title: GET Information about an Individual VIMs NFVI Capacity Information - NOT FOUND
... Test objective: The objective is to test that the retrieval of Individual VIMs NFVI Capacity Information fails when using an invalid resource identifier.
... Pre-conditions: none
- ... Reference: Clause 10.4.3.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 10.4.3.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -58,7 +58,7 @@ PUT Individual VIMs NFVI Capacity Information - Method not implemented
... Test title: PUT Individual VIMs NFVI Capacity Information - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 10.4.3.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 10.4.3.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: VNF Snapshot Package not modified
@@ -70,7 +70,7 @@ PATCH Individual VIMs NFVI Capacity Information - Method Not implemented
... Test title: PATCH Individual VIMs NFVI Capacity Information
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 10.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 10.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: VNF Snapshot Package modified
@@ -82,7 +82,7 @@ DELETE Individual VIMs NFVI Capacity Information - Method Not implemented
... Test title: DELETE Individual VIMs NFVI Capacity Information - Method Not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 10.4.3.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 10.4.3.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: VNF Snapshot Package deleted
diff --git a/SOL005/NFVICapacityInformation-API/NFVICapacityInformation.robot b/SOL005/NFVICapacityInformation-API/NFVICapacityInformation.robot
index 18da26d8e21470ee6cceb677dd74f59e1c513b38..649dea4b748b72da6693c2a9d6ef27ce31a0ab3e 100644
--- a/SOL005/NFVICapacityInformation-API/NFVICapacityInformation.robot
+++ b/SOL005/NFVICapacityInformation-API/NFVICapacityInformation.robot
@@ -7,7 +7,7 @@ POST NFVI Capacity Information - Method not implemented
... Test title: POST NFVI Capacity Information - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 10.4.2.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 10.4.2.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -19,7 +19,7 @@ GET NFVI Capacity Information
... Test title: GET NFVI Capacity Information
... Test objective: The objective is to GET NFVI Capacity Information objects
... Pre-conditions: none
- ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -32,7 +32,7 @@ GET NFVI Capacity Information - Filter
... Test title: GET NFVI Capacity Information - Filter
... Test objective: The objective is to GET NFVI Capacity Information objects using filter
... Pre-conditions: none
- ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -45,7 +45,7 @@ GET NFVI Capacity Information Bad Request Invalid attribute-based filtering para
... Test title: GET NFVI Capacity Information Bad Request Invalid attribute-based filtering parameters
... Test objective: The objective is to get information about NFVI Capacity Information with Invalid attribute-based filtering parameters
... Pre-conditions: none
- ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -58,7 +58,7 @@ GET NFVI Capacity Information Bad Request Invalid attribute selector
... Test title: GET NFVI Capacity Information Bad Request Invalid attribute selector
... Test objective: The objective is to get information about NFVI Capacity Information with Invalid attribute selector
... Pre-conditions: none
- ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -71,7 +71,7 @@ GET NFVI Capacity Information with "all_fields" attribute selector
... Test title: GET NFVI Capacity Information with "all_fields" attribute selector
... Test objective: The objective is to query NFVI Capacity Information with "all_fields" attribute selector
... Pre-conditions: none
- ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -84,7 +84,7 @@ GET NFVI Capacity Information with "exclude_default" attribute selector
... Test title: GET NFVI Capacity Information with "exclude_default" attribute selector
... Test objective: The objective is to query NFVI Capacity Information with "exclude_default" attribute selector
... Pre-conditions: none
- ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -97,7 +97,7 @@ GET NFVI Capacity Information with "fields" attribute selector
... Test title: GET NFVI Capacity Information with "fields" attribute selector
... Test objective: The objective is to query NFVI Capacity Information with "fields" attribute selector
... Pre-conditions: none
- ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -110,7 +110,7 @@ GET NFVI Capacity Information with "exclude_default" and "fields" attribute sele
... Test title: GET NFVI Capacity Information with "exclude_default" and "fields" attribute selector
... Test objective: The objective is to query NFVI Capacity Information with "exclude_default" and "fields" attribute selector
... Pre-conditions: none
- ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -123,7 +123,7 @@ GET NFVI Capacity Information with "exclude_fields" attribute selector
... Test title: GET NFVI Capacity Information with "exclude_fields" attribute selector
... Test objective: The objective is to query NFVI Capacity Information with "exclude_fields" attribute selector
... Pre-conditions: none
- ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -136,7 +136,7 @@ GET NFVI Capacity Information - Bad Request Response too Big
... Test title: GET NFVI Capacity Information - Bad Request Response too Big
... Test objective: The objective is test that the retrieval of existing NFVI Capacity Information list fails because response is too big, and perform the JSON schema validation of the failed operation HTTP response.
... Pre-conditions: none
- ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: NFVO does not support paged response.
... Post-Conditions: none
@@ -149,7 +149,7 @@ GET NFVI Capacity Information as Paged Response
... Test title: GET NFVI Capacity Information as Paged Response
... Test objective: The objective is to test that GET method retrieves the list of existing NFVI Capacity Information as paged response.
... Pre-conditions: none
- ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: NFVO supports paged response.
... Post-Conditions: none
@@ -162,7 +162,7 @@ PUT NFVI Capacity Information - Method not implemented
... Test title: PUT NFVI Capacity Information - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 10.4.2.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 10.4.2.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -174,7 +174,7 @@ PATCH NFVI Capacity Information - Method not implemented
... Test title: PATCH NFVI Capacity Information - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 10.4.2.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 10.4.2.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -186,7 +186,7 @@ DELETE NFVI Capacity Information - Method not implemented
... Test title: DELETE NFVI Capacity Information - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 10.4.2.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 10.4.2.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/NFVICapacityInformation-API/NFVICapacityInformationKeywords.robot b/SOL005/NFVICapacityInformation-API/NFVICapacityInformationKeywords.robot
index d4ce40ea15adfc90e0a0747fab991e7fb287748d..c7c754f37708a2eab2d2651998ee77acf47c0dcc 100644
--- a/SOL005/NFVICapacityInformation-API/NFVICapacityInformationKeywords.robot
+++ b/SOL005/NFVICapacityInformation-API/NFVICapacityInformationKeywords.robot
@@ -418,6 +418,18 @@ PATCH Individual Capacity Threshold - ETag mismatch
${outputResponse}= Output response
Set Global Variable ${response} ${outputResponse}
+PATCH Individual Capacity Threshold - HTTP Conditional Request not supported
+ Pass Execution If ${PRODUCER_SUPPORT_COND_REQ} == 1 NVFO allows conditional requests, skipping test
+ log Trying to perform a PATCH to modify individual VNF snapshot
+ Set Headers {"Accept":"${ACCEPT_JSON}"}
+ Set Headers {"Content-Type": "${CONTENT_TYPE_PATCH}"}
+ Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"${AUTHORIZATION_HEADER}":"${AUTHORIZATION_TOKEN}"}
+ ${template} = Get File jsons/CapacityThresholdModificationRequest.json
+ ${body}= Format String ${template} callback_uri=${new_callback_uri}
+ Patch ${apiRoot}/${apiName}/${apiMajorVersion}/capacity_thresholds/${capacityThreshold} ${body}
+ ${outputResponse}= Output response
+ Set Global Variable ${response} ${outputResponse}
+
PATCH Individual Capacity Threshold - Unreachable CallbackURI
log Trying to perform a PATCH to modify individual VNF snapshot
Set Headers {"Accept":"${ACCEPT_JSON}"}
diff --git a/SOL005/NFVICapacityInformation-API/NotificationEndpoint.robot b/SOL005/NFVICapacityInformation-API/NotificationEndpoint.robot
index d6361043b28b371e6ec39269f5fb06531903e184..7afef2e5276645be51e4cd39b54a1516163e62cc 100644
--- a/SOL005/NFVICapacityInformation-API/NotificationEndpoint.robot
+++ b/SOL005/NFVICapacityInformation-API/NotificationEndpoint.robot
@@ -8,7 +8,7 @@ Capacity Shortage Notification
... Test title: Capacity Shortage Notification
... Test objective: The objective is to test that Capacity Shortage Notification is delivered with success to the notification consumer.
... Pre-conditions: The consumer has already created an Individual Capacity Threshold resource
- ... Reference: Clause 10.4.6.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 10.4.6.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
@@ -20,7 +20,7 @@ Test the Notification Endpoint - Successful
... Test title: Test the Notification Endpoint - Successful
... Test objective: The objective is to test the Notification Endpoint provided by the notification consumer.
... Pre-conditions: The consumer has already created an Individual Capacity Threshold resource
- ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
@@ -32,7 +32,7 @@ Test the Notification Endpoint - UNREACHABLE
... Test title: Test the Notification Endpoint - UNREACHABLE
... Test objective: The objective is to test the Notification Endpoint provided by the notification consumer.
... Pre-conditions: The consumer has already created an Individual Capacity Threshold resource
- ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: The notification endpoint is unreachable by the API producer.
... Post-Conditions: none
@@ -45,7 +45,7 @@ PUT Notification endpoint - Method Not Implemented
... Test title: PUT Notification endpoint - Method Not Implemented
... Test objective: The objective is to test the PUT method for Notification Endpoint provided by the consumer is not implemented.
... Pre-conditions: A notification endpoint is provided by the API consumer upon subscription.
- ... Reference: Clause 10.4.6.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 10.4.6.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
@@ -57,7 +57,7 @@ PATCH Notification endpoint - Method Not Implemented
... Test title: PATCH Notification endpoint - Method Not Implemented
... Test objective: The objective is to test the PATCH method for Notification Endpoint provided by the consumer is not implemented.
... Pre-conditions: A notification endpoint is provided by the API consumer upon subscription.
- ... Reference: Clause 10.4.6.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 10.4.6.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
@@ -69,7 +69,7 @@ DELETE Notification endpoint - Method Not Implemented
... Test title: DELETE Notification endpoint - Method Not Implemented
... Test objective: The objective is to test the DELETE method for Notification Endpoint provided by the consumer is not implemented.
... Pre-conditions: A notification endpoint is provided by the API consumer upon subscription.
- ... Reference: Clause 10.4.6.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 10.4.6.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/NFVICapacityInformation-API/environment/variables.txt b/SOL005/NFVICapacityInformation-API/environment/variables.txt
index d5ee2bb0c86df5df96262559ea20fd6efb3a75a4..20c6351696d8304b27257a1a5af65174636651d0 100644
--- a/SOL005/NFVICapacityInformation-API/environment/variables.txt
+++ b/SOL005/NFVICapacityInformation-API/environment/variables.txt
@@ -36,4 +36,6 @@ ${callbackResp} localhost
${vimId}
${invalidVimId}
${capacityThreshold}
-${invalid_capacityThreshold}
\ No newline at end of file
+${invalid_capacityThreshold}
+
+${PRODUCER_SUPPORT_COND_REQ} 1
diff --git a/SOL005/NSDManagement-API/ApiVersion.robot b/SOL005/NSDManagement-API/ApiVersion.robot
index 1361f8086c5d896b941743f664b7bf9c34407766..56875c4796819f95c6c77c19fc099810ab7435bd 100644
--- a/SOL005/NSDManagement-API/ApiVersion.robot
+++ b/SOL005/NSDManagement-API/ApiVersion.robot
@@ -13,7 +13,7 @@ POST API Version - Method not implemented
... Test title: POST API version - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -25,7 +25,7 @@ GET API Version
... Test title: GET API Version
... Test objective: The objective is to test that GET method successfully return ApiVersionInformation
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -38,7 +38,7 @@ PUT API Version - Method not implemented
... Test title: PUT API Version - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -50,7 +50,7 @@ PATCH API Version - Method not implemented
... Test title: PATCH API Version - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -62,7 +62,7 @@ DELETE API Version - Method not implemented
... Test title: DELETE API Version - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -74,7 +74,7 @@ POST API Version with apiMajorVerion - Method not implemented
... Test title: POST API version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -86,7 +86,7 @@ GET API Version with apiMajorVerion
... Test title: GET API Version with apiMajorVerion
... Test objective: The objective is to test that GET method successfully return ApiVersionInformation
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -99,7 +99,7 @@ PUT API Version with apiMajorVerion - Method not implemented
... Test title: PUT API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -111,7 +111,7 @@ PATCH API Version with apiMajorVerion - Method not implemented
... Test title: PATCH API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -123,7 +123,7 @@ DELETE API Version with apiMajorVerion - Method not implemented
... Test title: DELETE API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/NSDManagement-API/IndividualNSDArchiveArtifact.robot b/SOL005/NSDManagement-API/IndividualNSDArchiveArtifact.robot
index 8350c492d5852d7ac3f4a2fa3a4919a45a025a5e..0e450f62b2225525e8d21c3ddd470d60057007d1 100644
--- a/SOL005/NSDManagement-API/IndividualNSDArchiveArtifact.robot
+++ b/SOL005/NSDManagement-API/IndividualNSDArchiveArtifact.robot
@@ -12,7 +12,7 @@ GET Individual NSD Archive Artifact
... Test title: GET Individual NSD Archive Artifact
... Test objective: The objective is to test the retrieval of an individual NSD Archive artifact
... Pre-conditions: One or more NSD archives are on-boarded to the NFVO.
- ... Reference: Clause 5.4.4c.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.4c.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -24,7 +24,7 @@ GET Individual NSD Archive Artifact with include_signatures parameter
... Test title: GET Individual NSD Archive Artifact with include_signatures parameter
... Test objective: The objective is to test that the GET request read the whole content of the archive containing the artifact files successfully and also contain security certificates when requested with "include_signature" parameter, and perform a validation that returned content is in Zip format
... Pre-conditions: One or more NSD archives are on-boarded to the NFVO.
- ... Reference: Clause 5.4.4c.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.4c.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -37,7 +37,7 @@ GET Individual NSD Archive Artifact in octet stream format
... Test title: GET Individual NSD Archive Artifact in octet stream format
... Test objective: The objective is to test the retrieval of an individual NSD Archive artifact when the NFVO cannot determine the artifact content type. The test performs a validation that the returned artifcat in is octet-stream format.
... Pre-conditions: One or more NSD archives are on-boarded to the NFVO.
- ... Reference: Clause 5.4.4c.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.4c.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO cannot determine the content type of the artifact
... Post-Conditions: none
@@ -50,7 +50,7 @@ GET Individual NSD Archive Artifact with Range Request and NFVO supporting Range
... Test title: GET Individual NSD Archive Artifact with Range Request and NFVO supporting Range Requests
... Test objective: The objective is to test the retrieval of an individual NSD Archive artifact when using a range request to return single range of bytes from the file, with the NFVO supporting it. The test also perform a validation that returned content matches the issued range
... Pre-conditions: One or more NSD archives are on-boarded to the NFVO.
- ... Reference: Clause 5.4.4c.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.4c.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO supports range requests to return single range of bytes from the NSD Archive artifact
... Post-Conditions: none
@@ -64,7 +64,7 @@ GET Individual NSD Archive Artifact with Range Request and NFVO not supporting R
... Test title: GET Individual NSD Archive Artifact with Range Request and NFVO not supporting Range Requests
... Test objective: The objective is to test that the retrieval of an individual NSD archive artifact, when using a range request to return single range of bytes from the file and the NFVO not supporting it, returns the full NSD Archive artifact.
... Pre-conditions: One or more NSD archives are on-boarded to the NFVO.
- ... Reference: Clause 5.4.4c.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.4c.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO does not support range requests to return single range of bytes from the NSD Archive artifact
... Post-Conditions: none
@@ -76,7 +76,7 @@ GET Individual NSD Archive Artifact with invalid resource identifier
... Test title: GET Individual NSD Archive Artifact with invalid resource identifier
... Test objective: The objective is to test that the retrieval of an individual NSD Archive Artifact fails when using an invalid resource identifier
... Pre-conditions: One or more NSD archives are on-boarded to the NFVO.
- ... Reference: Clause 5.4.4c.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.4c.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -89,7 +89,7 @@ GET Individual NSD Archive Artifact - Not Acceptable
... Test title: GET Individual NSD Archive Artifact - Not Acceptable
... Test objective: The objective is to test that the retrieval of an individual NSD Archive artifact fails when related request contained an "Accept" header not compatible with the Content type "application/zip" but the "include_signatures" flag was provided
... Pre-conditions: One or more NSD archives are on-boarded to the NFVO.
- ... Reference: Clause 5.4.4c.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.4c.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -102,7 +102,7 @@ GET Individual NSD Archive Artifact with conflict due to onboarding state
... GET Individual NSD Archive Artifact with conflict due to onboarding state
... Test objective: The objective is to test that the retrieval of an individual NSD Archive Artifact fails due to a conflict when the NSD is not in onboarding state ONBOARDED in the NFVO. The test also performs a validation of the JSON schema validation of the failed operation HTTP response
... Pre-conditions: The onboarding state of the NSD archive for which the content is requested is different from ONBOARDED.
- ... Reference: Clause 5.4.4c.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.4c.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -115,7 +115,7 @@ GET Individual NSD Archive Artifact with invalid Range Request
... Test title: GET Individual NSD Archive Artifact with invalid Range Request
... Test objective: The objective is to test that the retrieval of an Individual NSD Archive fails when using a range request that does not match any available byte range in the file.
... Pre-conditions: One or more NSD Archives are on-boarded to the NFVO.
- ... Reference: Clause 5.4.4c.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.4c.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO supports range requests to return single range of bytes from the NSD Archive artifact
... Post-Conditions: none
@@ -127,7 +127,7 @@ POST Individual NSD Archive Artifact - Method not implemented
... Test title: POST Individual NSD Archive Artifact - Method not implemented
... Test objective: The objective is to test that POST method is not allowed to create an individual artifact contained in an NSD archive.
... Pre-conditions: none
- ... Reference: Clause 5.4.4c.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.4c.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -139,7 +139,7 @@ PUT Individual NSD Archive Artifact - Method not implemented
... Test title: PUT Individual NSD Archive Artifact - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to modify an Individual NSD Archive artifact
... Pre-conditions: none
- ... Reference: Clause 5.4.4c.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.4c.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -151,7 +151,7 @@ PATCH Individual NSD Archive Artifact - Method not implemented
... Test title: PATCH Individual NSD Archive Artifact - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update an Individual NSD Archive artifact
... Pre-conditions: none
- ... Reference: Clause 5.4.4c.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.4c.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -163,7 +163,7 @@ DELETE Individual NSD Archive Artifact - Method not implemented
... Test title: DELETE Individual NSD Archive Artifact - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to delete an Individual NSD Archive artifact
... Pre-conditions: none
- ... Reference: Clause 5.4.4c.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.4c.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/NSDManagement-API/IndividualNSDescriptor.robot b/SOL005/NSDManagement-API/IndividualNSDescriptor.robot
index b0400b27f5e8b6a13e0605b3105e3141324faf14..c583a45b5798a34ced2981c4eb31ae19c34d4c9b 100644
--- a/SOL005/NSDManagement-API/IndividualNSDescriptor.robot
+++ b/SOL005/NSDManagement-API/IndividualNSDescriptor.robot
@@ -14,7 +14,7 @@ GET Individual Network Service Descriptor Information
... Test title: GET Individual Network Service Descriptor Information
... Test objective: The objective is to test the retrieval of an individual Network Service Descriptor information and perform a JSON schema validation of the collected data structure
... Pre-conditions: One or more Network Service Descriptors are onboarded in the NFVO.
- ... Reference: Clause 5.4.3.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.3.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -30,7 +30,7 @@ GET Individual Network Service Descriptor Information with invalid resource iden
... Test title: GET Individual Network Service Descriptor Information with invalid resource identifier
... Test objective: The objective is to test that the retrieval of an individual Network Service Descriptor Information fails when using an invalid resource identifier
... Pre-conditions: One or more Network Service Descriptors are onboarded in the NFVO.
- ... Reference: Clause 5.4.3.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.3.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -43,7 +43,7 @@ Disable Individual Network Service Descriptor
... Test title: Disable Individual Network Service Descriptor
... Test objective: The objective is to test the disabling of an individual Network Service Descriptor and perform a JSON schema and content validation of the collected data structure
... Pre-conditions: One or more Network Service Descriptors are onboarded in the NFVO in enabled operational state.
- ... Reference: Clause 5.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: The Network Service Descriptor is in operational state DISABLED and usage state is not modified
@@ -59,7 +59,7 @@ Enable Individual Network Service Descriptor
... Test title: Enable Individual Network Service Descriptor
... Test objective: The objective is to test the enabling of an individual Network Service Descriptor and perform a JSON schema and content validation of the collected data structure
... Pre-conditions: One or more Network Service Descriptors are onboarded in the NFVO in DISABLED operational state (Test ID 5.3.1.2.3).
- ... Reference: Clause 5.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: The Network Service Descriptor is in operational state ENABLED and usage state is not modified
@@ -74,7 +74,7 @@ Enable Individual Network Service Descriptor with conflict due to operational st
... Test title: Enable Individual Network Service Descriptor with conflict due to operational state ENABLED
... Test objective: The objective is to test that enabling an individual Network Service Descriptor that is already in ENABLED operational state failsand perform a JSON schema validation of the failed operation HTTP response
... Pre-conditions: One or more Network Service Descriptors are onboarded in the NFVO in ENABLED operational state (Test ID 5.3.1.2.4).
- ... Reference: Clause 5.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -87,7 +87,7 @@ Enable Individual Network Service Descriptor with conflict due to onboarding sta
... Test title: Enable Individual Network Service Descriptor with conflict due to onboarding state
... Test objective: The objective is to test that the retrieval of an Network Service Descriptor fails due to a conflict when the Network Service Descriptor is not in onboarding state ONBOARDED in the NFVO. The test also performs a validation of the JSON schema validation of the failed operation HTTP response
... Pre-conditions: One or more Network Service Descriptors are onboarded in the NFVO in ENABLED operational state. The onboarding state of the Network Service Descriptor for which the enabling is requested is different from ONBOARDED.
- ... Reference: Clause 5.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -100,13 +100,25 @@ Enable Individual Network Service Descriptor with HTTP Etag precondition failure
... Test title: Enable Individual Network Service Descriptor with HTTP Etag precondition failure
... Test objective: The objective is to test that the retrieval of an Network Service Descriptor fails due to a precondition failure when using an uncorrect Http Etag identified.
... Pre-conditions: One or more Network Service Descriptors are onboarded in the NFVO in ENABLED operational state (Test ID 5.3.1.2.4).
- ... Reference: Clause 5.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
Send PATCH to enable Individual Network Service Descriptor with HTTP Etag precondition failure
Check HTTP Response Status Code Is 412
+Enable Individual Network Service Descriptor with HTTP Conditional Request Not Supported Precondition Failure
+ [Documentation] Test ID: 5.3.1.2.7b
+ ... Test title: Enable Individual Network Service Descriptor with HTTP Conditional Request Not Supported Precondition Failure
+ ... Test objective: The objective is to test that the retrieval of an Network Service Descriptor fails if the API Producer does not support "Last-Modified" and "ETag" HTTP Headers
+ ... Pre-conditions: One or more Network Service Descriptors are onboarded in the NFVO in ENABLED operational state (Test ID 5.3.1.2.4).
+ ... Reference: Clause 5.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
+ ... Config ID: Config_prod_NFVO
+ ... Applicability: API Producer does not support "Last-Modified" and "ETag" HTTP Headers
+ ... Post-Conditions: none
+ Send PATCH to enable Individual Network Service Descriptor with HTTP Conditional Request not supported
+ Check HTTP Response Status Code Is 412
+
Void
[Documentation] Test ID: 5.3.1.2.8
... Test title: Void
@@ -123,7 +135,7 @@ DELETE Individual Network Service Descriptor
... Test title: DELETE Individual Network Service Descriptor
... Test objective: The objective is to test the deletion of an individual Network Service Descriptor.
... Pre-conditions: One or more Network Service Descriptors are onboarded in the NFVO in DISABLED operational state and NOT_IN_USE usage state.
- ... Reference: Clause 5.4.3.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.3.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: The Network Service Descriptor is not available anymore in the NFVO
@@ -136,7 +148,7 @@ DELETE Individual Network Service Descriptor in operational state ENABLED
... Test title: DELETE Individual Network Service Descriptor in operational state ENABLED
... Test objective: The objective is to test that the deletion of an individual Network Service Descriptor in operational state ENABLED fails. The test also performs a JSON schema validation of the failed operation HTTP response.
... Pre-conditions: One or more Network Service Descriptors are onboarded in the NFVO in ENABLED operational state (Test ID 5.3.1.2.4).
- ... Reference: Clause 5.4.3.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.3.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: The Network Service Descriptor is not deleted by the failed operation.
@@ -150,7 +162,7 @@ POST Individual Network Service Descriptor - Method not implemented
... Test title: POST Individual Network Service Descriptor - Method not implemented
... Test objective: The objective is to test that POST method is not allowed to create a new Network Service Descriptor
... Pre-conditions: none
- ... Reference: Clause 5.4.3.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.3.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -162,7 +174,7 @@ PUT Individual Network Service Descriptor - Method not implemented
... Test title: PUT Individual Network Service Descriptor - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to modify a new Network Service Descriptor
... Pre-conditions: none
- ... Reference: Clause 5.4.3.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.3.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/NSDManagement-API/IndividualPNFDArchiveArtifact.robot b/SOL005/NSDManagement-API/IndividualPNFDArchiveArtifact.robot
index 476c7abbe7e965c02a17cb8f0ebb16d950b50212..d9c4f6bed7df1d42661bea206bf0b849f4050798 100644
--- a/SOL005/NSDManagement-API/IndividualPNFDArchiveArtifact.robot
+++ b/SOL005/NSDManagement-API/IndividualPNFDArchiveArtifact.robot
@@ -12,7 +12,7 @@ GET Individual PNFD Archive Artifact
... Test title: GET Individual PNFD Archive Artifact
... Test objective: The objective is to test the retrieval of an individual PNFD Archive artifact
... Pre-conditions: One or more PNFD archives are on-boarded in the NFVO.
- ... Reference: Clause 5.4.7c.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.7c.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -24,7 +24,7 @@ GET Individual PNFD Archive Artifact with include_signatures parameter
... Test title: GET Individual PNFD Archive Artifact with include_signatures parameter
... Test objective: The objective is to test that the GET request read the whole content of the archive containing the artifact files successfully and also contain security certificates when requested with "include_signature" parameter, and perform a validation that returned content is in Zip format
... Pre-conditions: One or more PNFD archives are on-boarded to the NFVO.
- ... Reference: Clause 5.4.7c.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.7c.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -37,7 +37,7 @@ GET Individual PNFD Archive Artifact in octet stream format
... Test title: GET Individual PNFD Archive Artifact in octet stream format
... Test objective: The objective is to test the retrieval of an individual PNFD Archive artifact when the NFVO cannot determine the artifact content type. The test performs a validation that the returned artifcat in is octet-stream format.
... Pre-conditions: One or more PNFD archives are on-boarded to the NFVO.
- ... Reference: Clause 5.4.7c.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.7c.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO cannot determine the content type of the artifact
... Post-Conditions: none
@@ -50,7 +50,7 @@ GET Individual PNFD Archive Artifact with Range Request and NFVO supporting Rang
... Test title: GET Individual PNFD Archive Artifact with Range Request and NFVO supporting Range Requests
... Test objective: The objective is to test the retrieval of an individual PNFD Archive artifact when using a range request to return single range of bytes from the file, with the NFVO supporting it. The test also perform a validation that returned content matches the issued range
... Pre-conditions: One or more PNFD archives are on-boarded in the NFVO.
- ... Reference: Clause 5.4.7c.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.7c.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO supports range requests to return single range of bytes from the PNFD Archive artifact
... Post-Conditions: none
@@ -64,7 +64,7 @@ GET Individual PNFD Archive Artifact with Range Request and NFVO not supporting
... Test title: GET Individual PNFD Archive Artifact with Range Request and NFVO not supporting Range Requests
... Test objective: The objective is to test that the retrieval of an individual PNFD archive artifact, when using a range request to return single range of bytes from the file and the NFVO not supporting it, returns the full PNFD Archive artifact.
... Pre-conditions: One or more PNFD archives are on-boarded in the NFVO.
- ... Reference: Clause 5.4.7c.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.7c.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO does not support range requests to return single range of bytes from the PNFD Archive artifact
... Post-Conditions: none
@@ -76,7 +76,7 @@ GET Individual PNFD Archive Artifact with invalid resource identifier
... Test title: GET Individual PNFD Archive Artifact with invalid resource identifier
... Test objective: The objective is to test that the retrieval of an individual PNFD Archive Artifact fails when using an invalid resource identifier
... Pre-conditions: One or more PNFD archives are on-boarded in the NFVO.
- ... Reference: Clause 5.4.7c.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.7c.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -89,7 +89,7 @@ GET Individual PNFD Archive Artifact - Not Acceptable
... Test title: GET Individual PNFD Archive Artifact - Not Acceptable
... Test objective: The objective is to test that the retrieval of an individual PNFD Archive artifact fails when related request contained an "Accept" header not compatible with the Content type "application/zip" but the "include_signatures" flag was provided
... Pre-conditions: One or more PNFD archives are on-boarded to the NFVO.
- ... Reference: Clause 5.4.7c.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.7c.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -102,7 +102,7 @@ GET Individual PNFD Archive Artifact with conflict due to onboarding state
... GET Individual PNFD Archive Artifact with conflict due to onboarding state
... Test objective: The objective is to test that the retrieval of an individual PNFD Archive Artifact fails due to a conflict when the PNFD is not in onboarding state ONBOARDED in the NFVO. The test also performs a validation of the JSON schema validation of the failed operation HTTP response
... Pre-conditions: The onboarding state of the PNFD archive for which the content is requested is different from ONBOARDED.
- ... Reference: Clause 5.4.7c.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.7c.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -115,7 +115,7 @@ GET Individual PNFD Archive Artifact with invalid Range Request
... Test title: GET Individual PNFD Archive Artifact with invalid Range Request
... Test objective: The objective is to test that the retrieval of an Individual PNFD Archive fails when using a range request that does not match any available byte range in the file.
... Pre-conditions: One or more PNFD Archives are on-boarded to the NFVO.
- ... Reference: Clause 5.4.7c.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.7c.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO supports range requests to return single range of bytes from the PNFD Archive artifact
... Post-Conditions: none
@@ -128,7 +128,7 @@ POST Individual PNFD Archive Artifact - Method not implemented
... Test title: POST Individual PNFD Archive Artifact - Method not implemented
... Test objective: The objective is to test that POST method is not allowed to create an individual artifact contained in an PNFD archive.
... Pre-conditions: none
- ... Reference: Clause 5.4.7c.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.7c.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -140,7 +140,7 @@ PUT Individual PNFD Archive Artifact - Method not implemented
... Test title: PUT Individual PNFD Archive Artifact - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to modify an Individual PNFD Archive artifact
... Pre-conditions: none
- ... Reference: Clause 5.4.7c.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.7c.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -152,7 +152,7 @@ PATCH Individual PNFD Archive Artifact - Method not implemented
... Test title: PATCH Individual PNFD Archive Artifact - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update an Individual PNFD Archive artifact
... Pre-conditions: none
- ... Reference: Clause 5.4.7c.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.7c.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -164,7 +164,7 @@ DELETE Individual PNFD Archive Artifact - Method not implemented
... Test title: DELETE Individual PNFD Archive Artifact - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to delete an Individual PNFD Archive artifact
... Pre-conditions: none
- ... Reference: Clause 5.4.7c.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.7c.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/NSDManagement-API/IndividualPnfDescriptor.robot b/SOL005/NSDManagement-API/IndividualPnfDescriptor.robot
index 99e123ebb675ecf8e282c179a4af5a641710f2c4..25ff5e97cf62e349ed9448f3617ba313baacc725 100644
--- a/SOL005/NSDManagement-API/IndividualPnfDescriptor.robot
+++ b/SOL005/NSDManagement-API/IndividualPnfDescriptor.robot
@@ -13,7 +13,7 @@ GET Individual PNF Descriptor Information
... Test title: GET Individual PNF Descriptor Information
... Test objective: The objective is to test the retrieval of an individual PNF Descriptor information and perform a JSON schema validation of the collected data structure
... Pre-conditions: One or more PNF Descriptors are onboarded in the NFVO.
- ... Reference: Clause 5.4.6.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.6.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -28,7 +28,7 @@ GET Individual PNF Descriptor Information with invalid resource identifier
... Test title: GET Individual PNF Descriptor Information with invalid resource identifier
... Test objective: The objective is to test that the retrieval of an individual PNF Descriptor Information fails when using an invalid resource identifier
... Pre-conditions: One or more PNF Descriptors are onboarded in the NFVO.
- ... Reference: Clause 5.4.6.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.6.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -41,7 +41,7 @@ Update Individual PNF Descriptor
... Test title: Update Individual PNF Descriptor
... Test objective: The objective is to test the update of an individual PNF Descriptor and perform a JSON schema and content validation of the collected data structure
... Pre-conditions: One or more PNF Descriptors are onboarded in the NFVO.
- ... Reference: Clause 5.4.6.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.6.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: The PNF Descriptor is modified according to the update request
@@ -55,19 +55,31 @@ Update Individual PNF Descriptor with HTTP Etag precondition failure
... Test title: Update Individual PNF Descriptor with HTTP Etag precondition failure
... Test objective: The objective is to test that the update of a PNF Descriptor fails due to a precondition failure when using an uncorrect Http Etag identified.
... Pre-conditions: One or more PNF Descriptors are onboarded in the NFVO.
- ... Reference: Clause 5.4.6.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.6.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
Send PATCH to update Individual PNF Descriptor with HTTP Etag precondition failure
Check HTTP Response Status Code Is 412
+Update Individual PNF Descriptor with HTTP Conditional Request Not Supported Precondition Failure
+ [Documentation] Test ID: 5.3.1.5.4b
+ ... Test title: Update Individual PNF Descriptor with HTTP Conditional Request Not Supported Precondition Failure
+ ... Test objective: The objective is to test that the update of a PNF Descriptor fails due to the API Producer not supporting "Last-Modified" and "ETag" HTTP Headers
+ ... Pre-conditions: One or more PNF Descriptors are onboarded in the NFVO.
+ ... Reference: Clause 5.4.6.3.4, 4.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
+ ... Config ID: Config_prod_NFVO
+ ... Applicability: API Producer does not support "Last-Modified" and "ETag" HTTP Headers
+ ... Post-Conditions: none
+ Send PATCH to update Individual PNF Descriptor with HTTP Conditional Request Not Supported Precondition Failure
+ Check HTTP Response Status Code Is 412
+
POST Individual PNF Descriptor - Method not implemented
[Documentation] Test ID: 5.3.1.5.5
... Test title: POST Individual PNF Descriptor - Method not implemented
... Test objective: The objective is to test that POST method is not allowed to create a new PNF Descriptor
... Pre-conditions: none
- ... Reference: Clause 5.4.6.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.6.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -79,7 +91,7 @@ PUT Individual PNF Descriptor - Method not implemented
... Test title: PUT Individual PNF Descriptor - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to modify a new PNF Descriptor
... Pre-conditions: none
- ... Reference: Clause 5.4.6.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.6.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -91,7 +103,7 @@ DELETE Individual PNF Descriptor
... Test title: DELETE Individual PNF Descriptor
... Test objective: The objective is to test the deletion of an individual PNF Descriptor.
... Pre-conditions: One or more PNF Descriptors are onboarded in the NFVO.
- ... Reference: Clause 5.4.6.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.6.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: The PNF Descriptor is not available anymore in the NFVO
diff --git a/SOL005/NSDManagement-API/IndividualSubscription.robot b/SOL005/NSDManagement-API/IndividualSubscription.robot
index e79a4f0bb831007484afbad7e1e0d0cf7da79b80..c710cbc312e2bdc8f8170d9e51789f1c8e3d8fc8 100644
--- a/SOL005/NSDManagement-API/IndividualSubscription.robot
+++ b/SOL005/NSDManagement-API/IndividualSubscription.robot
@@ -12,7 +12,7 @@ GET Individual NSD Management Subscription
... Test title: GET Individual NSD Management Subscription
... Test objective: The objective is to test the retrieval of individual NSD Management subscription and perform a JSON schema and content validation of the returned subscription data structure
... Pre-conditions: At least one NSD Management subscription is available in the NFVO.
- ... Reference: Clause 5.4.9.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.9.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -27,7 +27,7 @@ GET Individual NSD Management Subscription with invalid resource identifier
... Test title: GET Individual NSD Management Subscription with invalid resource identifier
... Test objective: The objective is to test that the retrieval of an individual NSD Management subscription fails when using an invalid resource identifier
... Pre-conditions: At least one NSD Management subscription is available in the NFVO.
- ... Reference: Clause 5.4.9.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.9.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -40,7 +40,7 @@ DELETE Individual NSD Management Subscription with invalid resource identifier
... Test title: DELETE Individual NSD Management Subscription with invalid resource identifier
... Test objective: The objective is to test that the deletion of an individual NSD Management subscription fails when using an invalid resource identifier
... Pre-conditions: At least one NSD Management subscription is available in the NFVO.
- ... Reference: Clause 5.4.9.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.9.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -52,7 +52,7 @@ POST Individual NSD Management Subscription - Method not implemented
... Test title: POST Individual NSD Management Subscription - Method not implemented
... Test objective: The objective is to test that POST method is not allowed to create a new NSD Management Subscription
... Pre-conditions: none
- ... Reference: Clause 5.4.9.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.9.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -64,7 +64,7 @@ PUT Individual NSD Management Subscription - Method not implemented
... Test title: PUT Individual NSD Management Subscription - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to update an existing NSD Management subscription
... Pre-conditions: none
- ... Reference: Clause 5.4.9.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.9.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -76,7 +76,7 @@ PATCH Individual NSD Management Subscription - Method not implemented
... Test title: PATCH Individual NSD Management Subscription - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to modify an existing NSD Management subscription
... Pre-conditions: At least one NSD Management subscription is available in the NFVO.
- ... Reference: Clause 5.4.9.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.9.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -88,7 +88,7 @@ DELETE Individual NSD Management Subscription
... Test title: DELETE Individual NSD Management Subscription
... Test objective: The objective is to test the deletion of an individual NSD Management subscription
... Pre-conditions: At least one NSD Management subscription is available in the NFVO.
- ... Reference: Clause 5.4.9.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.9.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: The NSD Management Subscription is not available anymore in the NFVO
diff --git a/SOL005/NSDManagement-API/NSD.robot b/SOL005/NSDManagement-API/NSD.robot
index d154e4107db7a762338167b0ac98781fd8823ed3..6aa11f74bacc8b4fed2bb3ec7371825cb39d8193 100644
--- a/SOL005/NSDManagement-API/NSD.robot
+++ b/SOL005/NSDManagement-API/NSD.robot
@@ -12,7 +12,7 @@ Get single file NSD in Plain Format
... Test title: Get single file NSD in Plain Format
... Test objective: The objective is to test the retrieval of the NSD in plain format within a NSD archive and perform a validation that returned content is in plain format
... Pre-conditions: One or more NSDs are onboarded in the NFVO.
- ... Reference: Clause 5.4.4a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.4a.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NSD is implemented as a single file
... Post-Conditions: none
@@ -25,7 +25,7 @@ Get NSD in Zip Format
... Test title: Get NSD in Zip Format
... Test objective: The objective is to test the retrieval of the NSD in zip format within a NSD archive and perform a validation that returned content is in zip format
... Pre-conditions: One or more NSDs are onboarded in the NFVO.
- ... Reference: Clause 5.4.4a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.4a.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -38,7 +38,7 @@ Get single file NSD in Plain or Zip Format
... Test title: Get single file NSDin Plain or Zip Format
... Test objective: The objective is to test the retrieval of the single file NSD within a NSD archive when requesting Plain or Zip format to NFVO by including both formats in the request, and perform a validation that response is in Plain or Zip format
... Pre-conditions: One or more NSDs are onboarded in the NFVO.
- ... Reference: Clause 5.4.4a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.4a.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NSD is implemented as a single file
... Post-Conditions: none
@@ -51,7 +51,7 @@ Get multi file NSD in Plain or Zip Format
... Test title: Get multi file NSD in Plain or Zip Format
... Test objective: The objective is to test the retrieval of the multi file NSD within a NSD archive when requesting Plain or Zip format to NFVO by including both formats in the request, and perform a validation that returned content is in Zip format
... Pre-conditions: One or more NSDs are onboarded in the NFVO.
- ... Reference: Clause 5.4.4a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.4a.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NSD is implemented as a multi file
... Post-Conditions: none
@@ -64,7 +64,7 @@ Get multi file NSD in Plain Format
... Test title: Get multi file NSD in Plain Format
... Test objective: The objective is to test that the retrieval of the multi file NSD within a NSD archive fails when requesting it in Plain format, and perform a validation of the JSON schema validation of the failed operation HTTP response
... Pre-conditions: One or more NSDs are onboarded in the NFVO.
- ... Reference: Clause 5.4.4a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.4a.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NSD is implemented as a multi file
... Post-Conditions: none
@@ -77,7 +77,7 @@ Get NSD Content with invalid resource identifier
... Test title: Get NSD Content with invalid resource identifier
... Test objective: The objective is to test that the retrieval of the NSD within a NSD archive fails when using an invalid resource identifier
... Pre-conditions: none
- ... Reference: Clause 5.4.4a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.4a.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -90,7 +90,7 @@ Get NSD with conflict due to onboarding state
... Test title: Get NSD with conflict due to onboarding state
... Test objective: The objective is to test that the retrieval of the NSD within a NSD archive fails due to a conflict when the NSD is not in onboarding state ONBOARDED in the NFVO. The test also performs a validation of the JSON schema validation of the failed operation HTTP response
... Pre-conditions: The onboarding state of the NSD is different from ONBOARDED.
- ... Reference: Clause 5.4.4a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.4a.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -103,7 +103,7 @@ Get NSD with security information
... Test title: Get NSD with security information
... Test objective: The objective is to test the retrieval of the NSD within a NSD archive shall include in the ZIP archive the security information when requested with "include_signature" parameter
... Pre-conditions: One or more NSDs are onboarded in the NFVO.
- ... Reference: Clause 5.4.4a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.4a.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -116,7 +116,7 @@ POST NSD - Method not implemented
... Test title: POST NSD - Method not implemented
... Test objective: The objective is to test that POST method is not allowed to create a new Network Service Descriptor
... Pre-conditions: none
- ... Reference: Clause 5.4.4a.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.4a.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -128,7 +128,7 @@ PUT NSD - Method not implemented
... Test title: PUT NSD - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update Network Service Descriptor
... Pre-conditions: none
- ... Reference: Clause 5.4.4a.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.4a.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -140,7 +140,7 @@ PATCH NSD - Method not implemented
... Test title: PATCH NSD - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update Network Service Descriptor
... Pre-conditions: none
- ... Reference: Clause 5.4.4a.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.4a.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -152,7 +152,7 @@ DELETE NSD - Method not implemented
... Test title: DELETE NSD - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to delete Network Service Descriptor
... Pre-conditions: none
- ... Reference: Clause 5.4.4a.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.4a.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/NSDManagement-API/NSDArchiveContent.robot b/SOL005/NSDManagement-API/NSDArchiveContent.robot
index 7aa3c6f57a3394371df22df9966a2907393d6895..a2d8710e1e5434d9fef157e799b4f5830ef39dc3 100644
--- a/SOL005/NSDManagement-API/NSDArchiveContent.robot
+++ b/SOL005/NSDManagement-API/NSDArchiveContent.robot
@@ -24,7 +24,7 @@ Get NSD Content in Zip Format
... Test title: Get NSD Content in Zip Format
... Test objective: The objective is to test the retrieval of the NSD Content in zip format and perform a validation that returned content is in zip format
... Pre-conditions: One or more NSDs are onboarded in the NFVO.
- ... Reference: Clause 5.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -70,7 +70,7 @@ Get NSD Content with invalid resource identifier
... Test title: Get NSD Content with invalid resource identifier
... Test objective: The objective is to test that the retrieval of the NSD Content fails when using an invalid resource identifier
... Pre-conditions: none
- ... Reference: Clause 5.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -83,7 +83,7 @@ Get NSD Content with conflict due to onboarding state
... Test title: Get NSD Content with conflict due to onboarding state
... Test objective: The objective is to test that the retrieval of the NSD Content fails due to a conflict when the NSD is not in onboarding state ONBOARDED in the NFVO. The test also performs a validation of the JSON schema validation of the failed operation HTTP response
... Pre-conditions: The onboarding state of the NSD for which the NSD Content is requested is different from ONBOARDED.
- ... Reference: Clause 5.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -96,7 +96,7 @@ GET NSD Content with Range Request and NFVO supporting Range Requests
... Test title: GET NSD Content with Range Request and NFVO supporting Range Requests
... Test objective: The objective is to test the retrieval of NSD Content when using a range request to return single range of bytes from the file, with the NFVO supporting it. The test also perform a validation that returned content matches the issued range
... Pre-conditions: One or more NSDs are onboarded in the NFVO.
- ... Reference: Clause 5.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO supports range requests to return single range of bytes from the NSD file
... Post-Conditions: none
@@ -111,7 +111,7 @@ GET NSD Content with Range Request and NFVO not supporting Range Requests
... Test title: GET NSD Content with Range Request and NFVO not supporting Range Requests
... Test objective: The objective is to test that the retrieval of NSD Content, when using a range request to return single range of bytes from the file and the NFVO not supporting it, returns the full NSD file.
... Pre-conditions: One or more NSDs are onboarded in the NFVO.
- ... Reference: Clause 5.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO does not support range requests to return single range of bytes from the NSD file
... Post-Conditions: none
@@ -124,7 +124,7 @@ GET NSD Content with invalid Range Request
... Test title: GET NSD Content with invalid Range Request
... Test objective: The objective is to test that the retrieval of NSD Content fails when using a range request that does not match any available byte range in the file.
... Pre-conditions: One or more NSDs are onboarded in the NFVO.
- ... Reference: Clause 5.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO supports range requests to return single range of bytes from the NSD file
... Post-Conditions: none
@@ -137,7 +137,7 @@ Upload NSD Content as Zip file in asynchronous mode
... Test title: Upload NSD Content as Zip file in asynchronous mode
... Test objective: The objective is to test the upload of an NSD Content in Zip format when the NFVO supports the asynchronous upload mode.
... Pre-conditions: One or more NSDs are onboarded in the NFVO.
- ... Reference: Clause 5.4.4.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.4.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO supports the upload of NSD contents in asynchronous mode
... Post-Conditions: NSD Uploaded
@@ -161,7 +161,7 @@ Upload NSD Content as Zip file in synchronous mode
... Test title: Upload NSD Content as Zip file in synchronous mode
... Test objective: The objective is to test the upload of an NSD Content in Zip format when the NFVO supports the synchronous upload mode.
... Pre-conditions: One or more NSDs are onboarded in the NFVO.
- ... Reference: Clause 5.4.4.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.4.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO supports the upload of NSD contents in synchronous mode
... Post-Conditions: The NSD content is successfully uploaded and available in the NFVO
@@ -185,7 +185,7 @@ Upload NSD Content with conflict due to onboarding state
... Test title: Upload NSD Content with conflict due to onboarding state
... Test objective: The objective is to test that the upload of the NSD Content fails due to a conflict when the NSD is not in onboarding state CREATED in the NFVO. The test also performs a validation of the JSON schema validation of the failed operation HTTP response
... Pre-conditions: The onboarding state of the NSD for which the NSD Content is requested is different from ONBOARDED.
- ... Reference: Clause 5.4.4.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.4.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -198,7 +198,7 @@ POST NSD Content - Method not implemented
... Test title: POST NSD Content - Method not implemented
... Test objective: The objective is to test that POST method is not allowed to create a new Network Service Descriptor content
... Pre-conditions: none
- ... Reference: Clause 5.4.4.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.4.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -210,7 +210,7 @@ PATCH NSD Content - Method not implemented
... Test title: PATCH NSD Content - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update Network Service Descriptor content
... Pre-conditions: none
- ... Reference: Clause 5.4.4.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.4.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -222,7 +222,7 @@ DELETE NSD Content - Method not implemented
... Test title: DELETE NSD Content - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to delete Network Service Descriptor content
... Pre-conditions: none
- ... Reference: Clause 5.4.4.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.4.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/NSDManagement-API/NSDArchiveManifest.robot b/SOL005/NSDManagement-API/NSDArchiveManifest.robot
index 5fb375333da075d72c6a52041a428dbe90d8918d..87748287ab4f58c9842b6d0944b5dd320553fb88 100644
--- a/SOL005/NSDManagement-API/NSDArchiveManifest.robot
+++ b/SOL005/NSDManagement-API/NSDArchiveManifest.robot
@@ -12,7 +12,7 @@ Get NSD Archive Manifest
... Test title: Get NSD Archive Manifest
... Test objective: The objective is to test that GET method reads the content of the manifest file within an NSD archive
... Pre-conditions: One or more NSDs are onboarded in the NFVO.
- ... Reference: Clause 5.4.4b.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.4b.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -25,7 +25,7 @@ Get NSD Archive Manifest with security information
... Test title: Get NSD Archive Manifest with security information
... Test objective: The objective is to test the retrieval of content of the manifest file within an NSD archive shall include in the ZIP archive the security information when requested with "include_signature" parameter
... Pre-conditions: One or more NSDs are onboarded in the NFVO.
- ... Reference: Clause 5.4.4b.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.4b.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -38,7 +38,7 @@ Get NSD Archive Manifest with conflict due to onboarding state
... Test title: Get NSD Archive Manifest with conflict due to onboarding state
... Test objective: The objective is to test that the retrieval of content of the manifest file within an NSD archive fails due to a conflict when the NSD is not in onboarding state ONBOARDED in the NFVO. The test also performs a validation of the JSON schema validation of the failed operation HTTP response
... Pre-conditions: The onboarding state of the NSD is different from ONBOARDED.
- ... Reference: Clause 5.4.4b.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.4b.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -51,7 +51,7 @@ POST NSD Archive Manifest - Method not implemented
... Test title: POST NSD Archive Manifest - Method not implemented
... Test objective: The objective is to test that POST method is not allowed to create a new Network Service Descriptor Archive Manifest
... Pre-conditions: none
- ... Reference: Clause 5.4.4b.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.4b.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -63,7 +63,7 @@ PUT NSD Archive Manifest - Method not implemented
... Test title: PUT NSD Archive Manifest - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update Network Service Descriptor Archive Manifest
... Pre-conditions: none
- ... Reference: Clause 5.4.4b.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.4b.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -75,7 +75,7 @@ PATCH NSD Archive Manifest - Method not implemented
... Test title: PATCH NSD Archive Manifest - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update Network Service Descriptor Archive Manifest
... Pre-conditions: none
- ... Reference: Clause 5.4.4b.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.4b.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -87,7 +87,7 @@ DELETE NSD Archive Manifest - Method not implemented
... Test title: DELETE NSD Archive Manifest - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to delete Network Service Descriptor Archive Manifest
... Pre-conditions: none
- ... Reference: Clause 5.4.4b.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.4b.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/NSDManagement-API/NSDManagementKeywords.robot b/SOL005/NSDManagement-API/NSDManagementKeywords.robot
index e05cfa8b9656d61e5f8a9e3ac5798db8360d0543..d48366a4a60aac6c46792e9a893cff3b2db8b3f6 100644
--- a/SOL005/NSDManagement-API/NSDManagementKeywords.robot
+++ b/SOL005/NSDManagement-API/NSDManagementKeywords.robot
@@ -253,7 +253,7 @@ Send PATCH to enable Individual Network Service Descriptor in onboarding state d
${output}= Output response
Set Suite Variable ${response} ${output}
- Send PATCH to enable Individual Network Service Descriptor with HTTP Etag precondition failure
+Send PATCH to enable Individual Network Service Descriptor with HTTP Etag precondition failure
Log Trying to perform a PATCH. As prerequisite the nsdInfo shall be modified by another entity
Set Headers {"Accept": "${ACCEPT_JSON}"}
Set Headers {"Content-Type": "${CONTENT_TYPE_JSON}"}
@@ -264,6 +264,18 @@ Send PATCH to enable Individual Network Service Descriptor in onboarding state d
${output}= Output response
Set Suite Variable ${response} ${output}
+Send PATCH to enable Individual Network Service Descriptor with HTTP Conditional Request not supported
+ Pass Execution If ${PRODUCER_SUPPORT_COND_REQ} == 1 NVFO allows conditional requests, skipping test
+ Log Trying to perform a PATCH. As prerequisite the nsdInfo shall be in disabled operational state
+ Set Headers {"Accept": "${ACCEPT_JSON}"}
+ Set Headers {"Content-Type": "${CONTENT_TYPE_JSON}"}
+ Set Headers {"If-Match": "${original_etag}"}
+ ${body}= Get File jsons/NsdInfoModificationEnable.json
+ Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"${AUTHORIZATION_HEADER}":"${AUTHORIZATION_TOKEN}"}
+ REST.PATCH ${apiRoot}/${apiName}/${apiMajorVersion}/ns_descriptors/${nsdInfoId} ${body}
+ ${output}= Output response
+ Set Suite Variable ${response} ${output}
+
Send DELETE Request for Individual Network Service Descriptor
Log Trying to perform a DELETE nsdInfo. The nsdInfo should be in "NOT_USED" usageState and in "DISABLED" operationalState.
Set Headers {"Accept": "${ACCEPT_JSON}"}
@@ -614,6 +626,18 @@ Send PATCH to update Individual PNF Descriptor with HTTP Etag precondition failu
${output}= Output response
Set Suite Variable ${response} ${output}
+Send PATCH to update Individual PNF Descriptor with HTTP Conditional Request Not Supported Precondition Failure
+ Pass Execution If ${PRODUCER_SUPPORT_COND_REQ} == 1 NVFO allows conditional requests, skipping test
+ Log Trying to perform a PATCH.
+ Set Headers {"Accept": "${ACCEPT_JSON}"}
+ Set Headers {"Content-Type": "${CONTENT_TYPE_JSON}"}
+ Set Headers {"If-Match": "${original_etag}"}
+ ${body}= Get File jsons/PnfdInfoModification.json
+ Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"${AUTHORIZATION_HEADER}":"${AUTHORIZATION_TOKEN}"}
+ REST.PATCH ${apiRoot}/${apiName}/${apiMajorVersion}/pnf_descriptors/${pnfdInfoId} ${body}
+ ${output}= Output response
+ Set Suite Variable ${response} ${output}
+
Send DELETE Request for Individual PNF Descriptor
Log Trying to perform a DELETE pnfdInfo.
Set Headers {"Accept": "${ACCEPT_JSON}"}
diff --git a/SOL005/NSDManagement-API/NSDescriptors.robot b/SOL005/NSDManagement-API/NSDescriptors.robot
index 8927a94a74f2427e0dc8f18ebe50e538a920e231..84228945efd06ebac5fe5164534fe04d2a8ad5e0 100644
--- a/SOL005/NSDManagement-API/NSDescriptors.robot
+++ b/SOL005/NSDManagement-API/NSDescriptors.robot
@@ -13,7 +13,7 @@ GET all Network Service Descriptors Information
... Test title: GET all Network Service Descriptors Information
... Test objective: The objective is to test the retrieval of all the Network Service Descriptors information and perform a JSON schema and content validation of the collected data structure
... Pre-conditions: One or more Network Service Descriptors are onboarded in the NFVO
- ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -26,7 +26,7 @@ GET Network Service Descriptors Information with attribute-based filter
... Test title: GET Network Service Descriptors Information with attribute-based filter
... Test objective: The objective is to test the retrieval of Network Service Descriptors information using attribute-based filter, perform a JSON schema validation of the collected data structure, and verify that the retrieved information matches the issued attribute-based filter
... Pre-conditions: One or more Network Service Descriptors are onboarded in the NFVO
- ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -40,7 +40,7 @@ GET Network Service Descriptors Information with invalid attribute-based filter
... Test title: GET Network Service Descriptors Information with invalid attribute-based filter
... Test objective: The objective is to test that the retrieval of Network Service Descriptors information fails when using invalid attribute-based filter, and perform the JSON schema validation of the failed operation HTTP response
... Pre-conditions: One or more Network Service Descriptors are onboarded in the NFVO
- ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -53,7 +53,7 @@ Get all Network Service Descriptors Information with malformed authorization tok
... Test title: Get all Network Service Descriptors Information with malformed authorization token
... Test objective: The objective is to test that the retrieval of Network Service Descriptors Information fails when using malformed authorization token
... Pre-conditions: One or more Network Service Descriptors are onboarded in the NFVO
- ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO requires the usage of access tokens for authorizing the API requests.
... Post-Conditions: none
@@ -65,7 +65,7 @@ Get all Network Service Descriptors Information without authorization token
... Test title: Get all Network Service Descriptors Information without authorization token
... Test objective: The objective is to test that the retrieval of Network Service Descriptors Information fails when omitting the authorization token
... Pre-conditions: One or more Network Service Descriptors are onboarded in the NFVO
- ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO requires the usage of access tokens for authorizing the API requests.
... Post-Conditions: none
@@ -77,7 +77,7 @@ GET all Network Service Descriptors Information with expired or revoked authoriz
... Test title: GET all Network Service Descriptors Information with expired or revoked authorization token
... Test objective: The objective is to test that the retrieval of Network Service Descriptors Information fails when using expired or revoked authorization token
... Pre-conditions: One or more Network Service Descriptors are onboarded in the NFVO
- ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO requires the usage of access tokens for authorizing the API requests.
... Post-Conditions: none
@@ -89,7 +89,7 @@ GET all Network Service Descriptors Information with "all_fields" attribute sele
... Test title: GET all Network Service Descriptors Information with "all_fields" attribute selector
... Test objective: The objective is to test the retrieval of all Network Service Descriptors Information with "all_fields" attribute selector, perform a JSON schema validation of the collected data structure, and verify that the retrieved information matches the issued "all_fileds" selector
... Pre-conditions: One or more Network Service Descriptors are onboarded in the NFVO
- ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -103,7 +103,7 @@ GET all Network Service Descriptors Information with "exclude_default" attribute
... Test title: GET all Network Service Descriptors Information with "exclude_default" attribute selector
... Test objective: The objective is to test the retrieval of all Network Service Descriptors Information with "exclude_default" attribute selector, perform a JSON schema validation of the collected data structure, and verify that the retrieved information matches the issued "exclude_default" selector
... Pre-conditions: One or more Network Service Descriptors are onboarded in the NFVO
- ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -117,7 +117,7 @@ GET all Network Service Descriptors Information with "fields" attribute selector
... Test title: GET all Network Service Descriptors Information with "fields" attribute selector
... Test objective: The objective is to test the retrieval of all Network Service Descriptors Information with "fields" attribute selector, perform a JSON schema validation of the collected data structure, and verify that the retrieved information matches the issued "fields" selector
... Pre-conditions: One or more Network Service Descriptors are onboarded in the NFVO
- ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO supports the use of "fields" attribute selector
... Post-Conditions: none
@@ -131,7 +131,7 @@ GET all Network Service Descriptors Information with "exclude_fields" attribute
... Test title: GET all Network Service Descriptors Information with "exclude_fields" attribute selector
... Test objective: The objective is to test the retrieval of all Network Service Descriptors Information with "exclude_fields" attribute selector, perform a JSON schema validation of the collected data structure, and verify that the retrieved information matches the issued "exclude_fields" selector
... Pre-conditions: One or more Network Service Descriptors are onboarded in the NFVO
- ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO supports the use of "exclude_fields" attribute selector
... Post-Conditions: none
@@ -145,7 +145,7 @@ Create new Network Service Descriptor Resource
... Test title: Create new Network Service Descriptor Resource
... Test objective: The objective is to test the creation of a new Create new Network Service Descriptor resource and perform the JSON schema validation of the returned structure
... Pre-conditions: none
- ... Reference: Clause 5.4.2.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.2.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: The Network Service Descriptor resource is successfully created on the NFVO
@@ -161,7 +161,7 @@ PUT all Network Service Descriptors - Method not implemented
... Test title: PUT all Network Service Descriptors Information - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to modify Network Service Descriptors Information
... Pre-conditions: One or more Network Service Descriptors are onboarded in the NFVO
- ... Reference: Clause 5.4.2.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.2.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -173,7 +173,7 @@ PATCH all Network Service Descriptors - Method not implemented
... Test title: PATCH all Network Service Descriptors Information - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update Network Service Descriptors Information
... Pre-conditions: One or more Network Service Descriptors are onboarded in the NFVO
- ... Reference: Clause 5.4.2.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.2.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -185,7 +185,7 @@ DELETE all Network Service Descriptors - Method not implemented
... Test title: DELETE all Network Service Descriptors Information - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to delete Network Service Descriptors Information
... Pre-conditions: One or more Network Service Descriptors are onboarded in the NFVO
- ... Reference: Clause 5.4.2.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.2.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: The Network Service Descriptors are not deleted by the failed operation
@@ -198,7 +198,7 @@ GET all Network Service Descriptors Information as Paged Response
... Test title: GET all Network Service Descriptors Information as Paged Response
... Test objective: The objective is to test the retrieval of all the Network Service Descriptors information as a Paged Response.
... Pre-conditions: One or more Network Service Descriptors are onboarded in the NFVO
- ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -211,7 +211,7 @@ Get all Network Service Descriptors Information - Bad Request Response too Big
... Test title: Get all Network Service Descriptors Information - Bad Request Response too Big
... Test objective: The objective is to test that the retrieval of Network Service Descriptors Information fails because response is too big, and perform the JSON schema validation of the failed operation HTTP response
... Pre-conditions: One or more Network Service Descriptors are onboarded in the NFVO
- ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO requires the usage of access tokens for authorizing the API requests.
... Post-Conditions: none
@@ -224,7 +224,7 @@ GET all Network Service Descriptors Information with "exclude_default" and "fiel
... Test title: GET all Network Service Descriptors Information with "exclude_default" and "fields" attribute selector
... Test objective: The objective is to test the retrieval of all Network Service Descriptors Information with "exclude_default" and "fields" attribute selector, perform a JSON schema validation of the collected data structure, and verify that the retrieved information matches the issued "exclude_default" and "fields" selector
... Pre-conditions: One or more Network Service Descriptors are onboarded in the NFVO
- ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO supports the use of "exclude_default" and "fields" attribute selector
... Post-Conditions: none
diff --git a/SOL005/NSDManagement-API/NotificationEndpoint.robot b/SOL005/NSDManagement-API/NotificationEndpoint.robot
index 41ed637fec2b55a83c1ed0e854a26c5bb9bfe470..349392b92a6c22dd4cfc2037932b1f4d350ca2b9 100644
--- a/SOL005/NSDManagement-API/NotificationEndpoint.robot
+++ b/SOL005/NSDManagement-API/NotificationEndpoint.robot
@@ -14,7 +14,7 @@ NSD Onboarding Notification
... Test title: NSD Onboarding Notification
... Test objective: The objective is to test that NSD Onboarding Notification is delivered with success to the notification consumer.
... Pre-conditions: A NSD management subscription for onboarding notification is available in the NFVO.
- ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
@@ -26,7 +26,7 @@ NSD Onboarding Failure Notification
... Test title: NSD Onboarding Failure Notification
... Test objective: The objective is to test that NSD Onboarding Failure Notification is delivered with success to the notification consumer.
... Pre-conditions: A NSD management subscription for onboarding failure notification is available in the NFVO.
- ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
@@ -38,7 +38,7 @@ NSD Change Notification
... Test title: NSD Change Notification
... Test objective: The objective is to test that NSD Change Notification is delivered with success to the notification consumer.
... Pre-conditions: A NSD management subscription for change notification is available in the NFVO.
- ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
@@ -50,7 +50,7 @@ NSD Deletion Notification
... Test title: NSD Deletion Notification
... Test objective: The objective is to test that NSD Deletion Notification is delivered with success to the notification consumer.
... Pre-conditions: A NSD management subscription for deletion notification is available in the NFVO.
- ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
@@ -62,7 +62,7 @@ Pnfd Onboarding Notification
... Test title: Pnfd Onboarding Notification
... Test objective: The objective is to test that Pnfd Onboarding Notification is delivered with success to the notification consumer.
... Pre-conditions: A Pnfd management subscription for onboarding notification is available in the NFVO.
- ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
@@ -74,7 +74,7 @@ Pnfd Onboarding Failure Notification
... Test title: Pnfd Onboarding Failure Notification
... Test objective: The objective is to test that Pnfd Onboarding Failure Notification is delivered with success to the notification consumer.
... Pre-conditions: A Pnfd management subscription for onboarding failure notification is available in the NFVO.
- ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
@@ -86,7 +86,7 @@ Pnfd Deletion Notification
... Test title: pnfd Deletion Notification
... Test objective: The objective is to test that Pnfd Deletion Notification is delivered with success to the notification consumer.
... Pre-conditions: A Pnfd management subscription for deletion notification is available in the NFVO.
- ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/NSDManagement-API/Notifications.robot b/SOL005/NSDManagement-API/Notifications.robot
index c10fd6bf7cb138ddda647c27f64291f02f4410b5..34d29a01a0706f79daf470013c490fbc196228d6 100644
--- a/SOL005/NSDManagement-API/Notifications.robot
+++ b/SOL005/NSDManagement-API/Notifications.robot
@@ -15,7 +15,7 @@ NSD Onboarding Notification
... Test title: NSD Onboarding Notification
... Test objective: The objective is to test the dispatch of NSD Onboarding notification when the NSD onboarding operation is successfully completed, and perform a JSON schema and content validation of the delivered notification. The action that triggers the notification under test is an explicit test step, but it is not performed by the test system.
... Pre-conditions: A NSD management subscription for onboarding notifications is available in the NFVO.
- ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -28,7 +28,7 @@ NSD Onboarding Failure Notification
... Test title: NSD Onboarding Failure Notification
... Test objective: The objective is to test the dispatch of NSD Onboarding failure notification when the NSD onboarding operation fails, and perform a JSON schema and content validation of the delivered notification. The action that triggers the notification under test is an explicit test step, but it is not performed by the test system.
... Pre-conditions: A NSD management subscription for onboarding failure notifications is available in the NFVO.
- ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -41,7 +41,7 @@ NSD Operational State Change Notification
... Test title: NSD Operational State Change Notification
... Test objective: The objective is to test the dispatch of NSD Operational State Change notification when the NSD operational status change in the NFVO, and perform a JSON schema and content validation of the delivered notification. The action that triggers the notification under test is an explicit test step, but it is not performed by the test system.
... Pre-conditions: A NSD management subscription for operational state change notifications is available in the NFVO.
- ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -54,7 +54,7 @@ NSD Deletion Notification
... Test title: NSD Deletion Notification
... Test objective: The objective is to test the dispatch of NSD Deletion notification when the NSD is deleted from the NFVO, and perform a JSON schema and content validation of the delivered notification. The action that triggers the notification under test is an explicit test step, but it is not performed by the test system.
... Pre-conditions: A NSD management subscription for deletion notifications is available in the NFVO.
- ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -67,7 +67,7 @@ PNFD Onboarding Notification
... Test title: PNFD Onboarding Notification
... Test objective: The objective is to test the dispatch of PNFD Onboarding notification when the PNFD onboarding operation is successfully completed, and perform a JSON schema and content validation of the delivered notification. The action that triggers the notification under test is an explicit test step, but it is not performed by the test system.
... Pre-conditions: A PNFD management subscription for onboarding notifications is available in the NFVO.
- ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -80,7 +80,7 @@ PNFD Onboarding Failure Notification
... Test title: PNFD Onboarding Failure Notification
... Test objective: The objective is to test the dispatch of PNFD Onboarding failure notification when the PNFD onboarding operation fails, and perform a JSON schema and content validation of the delivered notification. The action that triggers the notification under test is an explicit test step, but it is not performed by the test system.
... Pre-conditions: A PNFD management subscription for onboarding failure notifications is available in the NFVO.
- ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -93,7 +93,7 @@ PNFD Deletion Notification
... Test title: PNFD Deletion Notification
... Test objective: The objective is to test the dispatch of PNFD Deletion notification when the PNFD is deleted from the NFVO, and perform a JSON schema and content validation of the delivered notification. The action that triggers the notification under test is an explicit test step, but it is not performed by the test system.
... Pre-conditions: A PNFD management subscription for deletion notifications is available in the NFVO.
- ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/NSDManagement-API/PNFD.robot b/SOL005/NSDManagement-API/PNFD.robot
index c2b837a407b280809be7b30cefe24c3291350f26..c75b88d28f407481f67e2c687c4ca3b2faabbe52 100644
--- a/SOL005/NSDManagement-API/PNFD.robot
+++ b/SOL005/NSDManagement-API/PNFD.robot
@@ -13,7 +13,7 @@ Get single file PNFD in Plain Format
... Test title: Get single file PNFD in Plain Format
... Test objective: The objective is to test the retrieval of the PNFD in plain format within a PNFD archive and perform a validation that returned content is in plain format
... Pre-conditions: One or more PNFDs are onboarded in the NFVO.
- ... Reference: Clause 5.4.7a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.7a.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The PNFD is implemented as a single file
... Post-Conditions: none
@@ -26,7 +26,7 @@ Get PNFD in Zip Format
... Test title: Get PNFD in Zip Format
... Test objective: The objective is to test the retrieval of the PNFD in zip format within a PNFD archive and perform a validation that returned content is in zip format
... Pre-conditions: One or more PNFDs are onboarded in the NFVO.
- ... Reference: Clause 5.4.7a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.7a.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -39,7 +39,7 @@ Get single file PNFD in Plain or Zip Format
... Test title: Get single file PNFDin Plain or Zip Format
... Test objective: The objective is to test the retrieval of the single file PNFD within a PNFD archive when requesting Plain or Zip format to NFVO by including both formats in the request, and perform a validation that response is in Plain or Zip format
... Pre-conditions: One or more PNFDs are onboarded in the NFVO.
- ... Reference: Clause 5.4.7a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.7a.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The PNFD is implemented as a single file
... Post-Conditions: none
@@ -52,7 +52,7 @@ Get multi file PNFD in Plain or Zip Format
... Test title: Get multi file PNFD in Plain or Zip Format
... Test objective: The objective is to test the retrieval of the multi file PNFD within a PNFD archive when requesting Plain or Zip format to NFVO by including both formats in the request, and perform a validation that returned content is in Zip format
... Pre-conditions: One or more PNFDs are onboarded in the NFVO.
- ... Reference: Clause 5.4.7a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.7a.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The PNFD is implemented as a multi file
... Post-Conditions: none
@@ -65,7 +65,7 @@ Get multi file PNFD in Plain Format
... Test title: Get multi file PNFD in Plain Format
... Test objective: The objective is to test that the retrieval of the multi file PNFD within a PNFD archive fails when requesting it in Plain format, and perform a validation of the JSON schema validation of the failed operation HTTP response
... Pre-conditions: One or more PNFDs are onboarded in the NFVO.
- ... Reference: Clause 5.4.7a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.7a.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The PNFD is implemented as a multi file
... Post-Conditions: none
@@ -78,7 +78,7 @@ Get PNFD Content with invalid resource identifier
... Test title: Get PNFD Content with invalid resource identifier
... Test objective: The objective is to test that the retrieval of the PNFD within a PNFD archive fails when using an invalid resource identifier
... Pre-conditions: none
- ... Reference: Clause 5.4.7a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.7a.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -91,7 +91,7 @@ Get PNFD with conflict due to onboarding state
... Test title: Get PNFD with conflict due to onboarding state
... Test objective: The objective is to test that the retrieval of the PNFD within a PNFD archive fails due to a conflict when the PNFD is not in onboarding state ONBOARDED in the NFVO. The test also performs a validation of the JSON schema validation of the failed operation HTTP response
... Pre-conditions: The onboarding state of the PNFD is different from ONBOARDED.
- ... Reference: Clause 5.4.7a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.7a.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -104,7 +104,7 @@ Get PNFD with security information
... Test title: Get PNFD with security information
... Test objective: The objective is to test the retrieval of the PNFD within a PNFD archive shall include in the ZIP archive the security information when requested with "include_signature" parameter
... Pre-conditions: One or more PNFDs are onboarded in the NFVO.
- ... Reference: Clause 5.4.7a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.7a.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -117,7 +117,7 @@ POST PNFD - Method not implemented
... Test title: POST PNFD - Method not implemented
... Test objective: The objective is to test that POST method is not allowed to create a new PNFD
... Pre-conditions: none
- ... Reference: Clause 5.4.7a.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.7a.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -129,7 +129,7 @@ PUT PNFD - Method not implemented
... Test title: PUT PNFD - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update PNFD
... Pre-conditions: none
- ... Reference: Clause 5.4.7a.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.7a.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -141,7 +141,7 @@ PATCH PNFD - Method not implemented
... Test title: PATCH PNFD - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update PNFD
... Pre-conditions: none
- ... Reference: Clause 5.4.7a.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.7a.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -153,7 +153,7 @@ DELETE PNFD - Method not implemented
... Test title: DELETE PNFD - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to delete PNFD
... Pre-conditions: none
- ... Reference: Clause 5.4.7a.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.7a.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/NSDManagement-API/PNFDArchiveContent.robot b/SOL005/NSDManagement-API/PNFDArchiveContent.robot
index 6cf83c7178a54a0c82880f21f75772019c34faff..90166c4fd3b43efea2e638ef546eac32e6f15980 100644
--- a/SOL005/NSDManagement-API/PNFDArchiveContent.robot
+++ b/SOL005/NSDManagement-API/PNFDArchiveContent.robot
@@ -13,7 +13,7 @@ Get PNFD Content
... Test title: Get PNFD Content
... Test objective: The objective is to test the retrieval of the PNFD Content in zip format and perform a validation that returned content is in plain format
... Pre-conditions: One or more PNFDs are onboarded in the NFVO.
- ... Reference: Clause 5.4.7.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.7.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -26,7 +26,7 @@ Get PNFD Content with invalid resource identifier
... Test title: Get PNFD Content with invalid resource identifier
... Test objective: The objective is to test that the retrieval of the PNFD Content fails when using an invalid resource identifier
... Pre-conditions: none
- ... Reference: Clause 5.4.7.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.7.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -39,7 +39,7 @@ Get PNFD Content with conflict due to onboarding state
... Test title: Get PNFD Content with conflict due to onboarding state
... Test objective: The objective is to test that the retrieval of the PNFD Content fails due to a conflict when the PNFD is not in onboarding state ONBOARDED in the NFVO. The test also performs a validation of the JSON schema validation of the failed operation HTTP response
... Pre-conditions: The onboarding state of the PNFD for which the PNFD Content is requested is different from ONBOARDED.
- ... Reference: Clause 5.4.7.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.7.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -52,7 +52,7 @@ Upload PNFD Content as zip file
... Test title: Upload PNFD Content as zip file
... Test objective: The objective is to test the upload of a PNFD Content in plain text format.
... Pre-conditions: One or more PNFDs are onboarded in the NFVO.
- ... Reference: Clause 5.4.7.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.7.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: The uploaded PNFD content is available in the NFVO
@@ -65,7 +65,7 @@ Upload PNFD Content with conflict due to onboarding state
... Test title: Upload PNFD Content with conflict due to onboarding state
... Test objective: The objective is to test that the upload of the PNFD Content fails due to a conflict when the PNFD is not in onboarding state CREATED in the NFVO. The test also performs a validation of the JSON schema validation of the failed operation HTTP response
... Pre-conditions: The onboarding state of the PNFD for which the PNFD Content is requested is different from CREATED.
- ... Reference: Clause 5.4.7.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.7.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -78,7 +78,7 @@ POST PNFD Content - Method not implemented
... Test title: POST PNFD Content - Method not implemented
... Test objective: The objective is to test that POST method is not allowed to create a new PNF Descriptor content
... Pre-conditions: none
- ... Reference: Clause 5.4.7.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.7.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -90,7 +90,7 @@ PATCH PNFD Content - Method not implemented
... Test title: PATCH PNFD Content - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update PNF Descriptor content
... Pre-conditions: none
- ... Reference: Clause 5.4.7.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.7.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -102,7 +102,7 @@ DELETE PNFD Content - Method not implemented
... Test title: DELETE PNFD Content - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to delete PNF Descriptor content
... Pre-conditions: none
- ... Reference: Clause 5.4.7.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.7.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -114,7 +114,7 @@ Get PNFD Content with Range Request and NFVO supporting Range Requests
... Test title: Get PNFD Content with Range Request and NFVO supporting Range Requests
... Test objective: The objective is to test the retrieval of the PNFD Content in plain format when using a range request to return single range of bytes from the file, with the NFVO supporting it
... Pre-conditions: One or more PNFDs are onboarded in the NFVO.
- ... Reference: Clause 5.4.7.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.7.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -128,7 +128,7 @@ Get PNFD Content with invalid Range Request
... Test title: Get PNFD Content with invalid Range Request
... Test objective: The objective is to test the retrieval of the PNFD Content in plain format and perform a validation that returned content is in plain format
... Pre-conditions: One or more PNFDs are onboarded in the NFVO.
- ... Reference: Clause 5.4.7.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.7.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -141,7 +141,7 @@ Upload PNFD Archive Content
... Test title: Upload PNFD Archive Content
... Test objective: The objective is to test the PNFD archive has been accepted for uploading, but the processing has not been completed.
... Pre-conditions: One or more PNFDs are onboarded in the NFVO.
- ... Reference: Clause 5.4.7.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.7.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/NSDManagement-API/PNFDArchiveManifest.robot b/SOL005/NSDManagement-API/PNFDArchiveManifest.robot
index 30502dda55b79edaf1f16ab911f77f170326c08b..d81b6947f0268e02bebf141b36c2da07bc7536f2 100644
--- a/SOL005/NSDManagement-API/PNFDArchiveManifest.robot
+++ b/SOL005/NSDManagement-API/PNFDArchiveManifest.robot
@@ -12,7 +12,7 @@ Get PNFD Archive Manifest
... Test title: Get PNFD Archive Manifest
... Test objective: The objective is to test that GET method reads the content of the manifest file within an PNFD archive
... Pre-conditions: One or more PNFDs are onboarded in the NFVO.
- ... Reference: Clause 5.4.7b.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.7b.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -25,7 +25,7 @@ Get PNFD Archive Manifest with security information
... Test title: Get PNFD Archive Manifest with security information
... Test objective: The objective is to test the retrieval of content of the manifest file within an PNFD archive shall include in the ZIP archive the security information when requested with "include_signature" parameter
... Pre-conditions: One or more PNFDs are onboarded in the NFVO.
- ... Reference: Clause 5.4.7b.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.7b.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -38,7 +38,7 @@ Get PNFD Archive Manifest with conflict due to onboarding state
... Test title: Get PNFD Archive Manifest with conflict due to onboarding state
... Test objective: The objective is to test that the retrieval of content of the manifest file within an PNFD archive fails due to a conflict when the PNFD is not in onboarding state ONBOARDED in the NFVO. The test also performs a validation of the JSON schema validation of the failed operation HTTP response
... Pre-conditions: The onboarding state of the PNFD is different from ONBOARDED.
- ... Reference: Clause 5.4.7b.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.7b.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -51,7 +51,7 @@ POST PNFD Archive Manifest - Method not implemented
... Test title: POST PNFD Archive Manifest - Method not implemented
... Test objective: The objective is to test that POST method is not allowed to create a new Network Service Descriptor Archive Manifest
... Pre-conditions: none
- ... Reference: Clause 5.4.7b.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.7b.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -63,7 +63,7 @@ PUT PNFD Archive Manifest - Method not implemented
... Test title: PUT PNFD Archive Manifest - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update Network Service Descriptor Archive Manifest
... Pre-conditions: none
- ... Reference: Clause 5.4.7b.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.7b.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -75,7 +75,7 @@ PATCH PNFD Archive Manifest - Method not implemented
... Test title: PATCH PNFD Archive Manifest - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update Network Service Descriptor Archive Manifest
... Pre-conditions: none
- ... Reference: Clause 5.4.7b.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.7b.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -87,7 +87,7 @@ DELETE PNFD Archive Manifest - Method not implemented
... Test title: DELETE PNFD Archive Manifest - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to delete Network Service Descriptor Archive Manifest
... Pre-conditions: none
- ... Reference: Clause 5.4.7b.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.7b.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/NSDManagement-API/PNFDescriptors.robot b/SOL005/NSDManagement-API/PNFDescriptors.robot
index 81bbe41f7231b4489e31e52fec0a80d2dba1c512..f649c0213379b1c342d5a85a1b811a4f25760eab 100644
--- a/SOL005/NSDManagement-API/PNFDescriptors.robot
+++ b/SOL005/NSDManagement-API/PNFDescriptors.robot
@@ -13,7 +13,7 @@ GET all PNF Descriptors Information
... Test title: GET all PNF Descriptors Information
... Test objective: The objective is to test the retrieval of all the PNF Descriptors information and perform a JSON schema and content validation of the collected data structure
... Pre-conditions: One or more PNF Descriptors are onboarded in the NFVO.
- ... Reference: Clause 5.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -26,7 +26,7 @@ GET PNF Descriptors Information with attribute-based filter
... Test title: GET PNF Descriptors Information with attribute-based filter
... Test objective: The objective is to test the retrieval of PNF Descriptors information using attribute-based filter, perform a JSON schema validation of the collected data structure, and verify that the retrieved information matches the issued attribute-based filter
... Pre-conditions: One or more PNF Descriptors are onboarded in the NFVO.
- ... Reference: Clause 5.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -40,7 +40,7 @@ GET PNF Descriptors Information with invalid attribute-based filter
... Test title: GET PNF Descriptors Information with invalid attribute-based filter
... Test objective: The objective is to test that the retrieval of PNF Descriptors information fails when using invalid attribute-based filter, and perform the JSON schema validation of the failed operation HTTP response
... Pre-conditions: One or more PNF Descriptors are onboarded in the NFVO.
- ... Reference: Clause 5.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -53,7 +53,7 @@ GET all PNF Descriptors Information with "all_fields" attribute selector
... Test title: GET all PNF Descriptors Information with "all_fields" attribute selector
... Test objective: The objective is to test the retrieval of all PNF Descriptors Information with "all_fields" attribute selector, perform a JSON schema validation of the collected data structure, and verify that the retrieved information matches the issued "all_fileds" selector
... Pre-conditions: One or more PNF Descriptors are onboarded in the NFVO.
- ... Reference: Clause 5.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -67,7 +67,7 @@ GET all PNF Descriptors Information with "exclude_default" attribute selector
... Test title: GET all PNF Descriptors Information with "exclude_default" attribute selector
... Test objective: The objective is to test the retrieval of all PNF Descriptors Information with "exclude_default" attribute selector, perform a JSON schema validation of the collected data structure, and verify that the retrieved information matches the issued "exclude_default" selector
... Pre-conditions: One or more PNF Descriptors are onboarded in the NFVO.
- ... Reference: Clause 5.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -81,7 +81,7 @@ GET all PNF Descriptors Information with "fields" attribute selector
... Test title: GET all PNF Descriptors Information with "fields" attribute selector
... Test objective: The objective is to test the retrieval of all PNF Descriptors Information with "fields" attribute selector, perform a JSON schema validation of the collected data structure, and verify that the retrieved information matches the issued "fields" selector
... Pre-conditions: One or more PNF Descriptors are onboarded in the NFVO.
- ... Reference: Clause 5.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO supports the use of "fields" attribute selector
... Post-Conditions: none
@@ -95,7 +95,7 @@ GET all PNF Descriptors Information with "exclude_fields" attribute selector
... Test title: GET all PNF Descriptors Information with "exclude_fields" attribute selector
... Test objective: The objective is to test the retrieval of all PNF Descriptors Information with "exclude_fields" attribute selector, perform a JSON schema validation of the collected data structure, and verify that the retrieved information matches the issued "exclude_fields" selector
... Pre-conditions: One or more PNF Descriptors are onboarded in the NFVO.
- ... Reference: Clause 5.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO supports the use of "exclude_fields" attribute selector
... Post-Conditions: none
@@ -109,7 +109,7 @@ Create new PNF Descriptor Resource
... Test title: Create new PNF Descriptor Resource
... Test objective: The objective is to test the creation of a new Create new PNF Descriptor resource and perform the JSON schema validation of the returned structure
... Pre-conditions: none
- ... Reference: Clause 5.4.5.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.5.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: The PNF Descriptor resource is successfully created on the NFVO
@@ -124,7 +124,7 @@ PUT all PNF Descriptors - Method not implemented
... Test title: PUT all PNF Descriptors Information - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to modify PNF Descriptors Information
... Pre-conditions: none
- ... Reference: Clause 5.4.5.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.5.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -136,7 +136,7 @@ PATCH all PNF Descriptors - Method not implemented
... Test title: PATCH all PNF Descriptors Information - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update NF Descriptors Information
... Pre-conditions: none
- ... Reference: Clause 5.4.5.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.5.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -148,7 +148,7 @@ DELETE all PNF Descriptors - Method not implemented
... Test title: DELETE all PNF Descriptors Information - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to delete PNF Descriptors Information
... Pre-conditions: none
- ... Reference: Clause 5.4.5.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.5.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -160,7 +160,7 @@ GET all PNF Descriptors Information as Paged Response
... Test title: GET all PNF Descriptors Information as Paged Response
... Test objective: The objective is to test the retrieval of all the PNF Descriptors information as a Paged Response.
... Pre-conditions: One or more PNF Descriptors are onboarded in the NFVO.
- ... Reference: Clause 5.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -173,7 +173,7 @@ GET PNF Descriptors Information - Bad Request Response too Big
... Test title: GET PNF Descriptors Information - Bad Request Response too Big
... Test objective: The objective is to test that the retrieval of PNF Descriptors information fails because response is too big, and perform the JSON schema validation of the failed operation HTTP response
... Pre-conditions: One or more PNF Descriptors are onboarded in the NFVO.
- ... Reference: Clause 5.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -186,7 +186,7 @@ GET all PNF Descriptors Information with "exclude_default" and "fields" attribut
... Test title: GET all PNF Descriptors Information with "exclude_default" and "fields" attribute selector
... Test objective: The objective is to test the retrieval of all PNF Descriptors Information with "exclude_default" and "fields" attribute selector, perform a JSON schema validation of the collected data structure, and verify that the retrieved information matches the issued "exclude_default" and "fields" selector
... Pre-conditions: One or more PNF Descriptors are onboarded in the NFVO.
- ... Reference: Clause 5.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO supports the use of "exclude_default" and "fields" attribute selector
... Post-Conditions: none
diff --git a/SOL005/NSDManagement-API/Subscriptions.robot b/SOL005/NSDManagement-API/Subscriptions.robot
index ecc2dd21eac81d5399c71fd5c845bb6e3d768a70..d50b449201454fee970b13d79a199b9c383a4e45 100644
--- a/SOL005/NSDManagement-API/Subscriptions.robot
+++ b/SOL005/NSDManagement-API/Subscriptions.robot
@@ -15,7 +15,7 @@ Get All NSD Management Subscriptions
... Test title: Get All NSD Management Subscriptions
... Test objective: The objective is to test the retrieval of all NSD Management subscriptions and perform a JSON schema validation of the returned subscriptions data structure
... Pre-conditions: At least one NSD Management subscription is available in the NFVO.
- ... Reference: Clause 5.4.8.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.8.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -28,7 +28,7 @@ Get NSD Management Subscriptions with attribute-based filter
... Test title: Get NSD Management Subscriptions with attribute-based filter
... Test objective: The objective is to test the retrieval of NSD Management subscriptions using attribute-based filter, perform a JSON schema validation of the collected data structure, and verify that the retrieved information matches the issued attribute-based filters
... Pre-conditions: At least one NSD Management subscription is available in the NFVO.
- ... Reference: Clause 5.4.8.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.8.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -42,7 +42,7 @@ Get NSD Management Subscriptions with invalid attribute-based filter
... Test title: Get NSD Management Subscriptions with attribute-based filters
... Test objective: The objective is to test that the retrieval of NSD Management subscriptions fails when using invalid attribute-based filters, and perform the JSON schema validation of the failed operation HTTP response.
... Pre-conditions: At least one NSD Management subscription is available in the NFVO.
- ... Reference: Clause 5.4.8.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.8.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -55,7 +55,7 @@ GET NSD Management Subscription with invalid resource endpoint
... Test title: GET NSD Management Subscription with invalid resource endpoint
... Test objective: The objective is to test that the retrieval of all NSD Management subscriptions fails when using invalid resource endpoint.
... Pre-conditions: At least one NSD Management subscription is available in the NFVO.
- ... Reference: Clause 5.4.8.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.8.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -68,7 +68,7 @@ Create new NSD Management subscription
... Test title: Create new NSD Management subscription
... Test objective: The objective is to test the creation of a new NSD Management subscription and perform a JSON schema and content validation of the returned subscription data structure
... Pre-conditions: none
- ... Reference: Clause 5.4.8.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.8.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: The NSD Management subscription is successfully set and it matches the issued subscription
@@ -84,7 +84,7 @@ Create duplicated NSD Management subscription with NFVO not creating duplicated
... Test title: Create duplicated NSD Management subscription with NFVO not creating duplicated subscriptions
... Test objective: The objective is to test the attempt of a creation of a duplicated NSD Management subscription and check that no new subscription is created by the NFVO and a link to the original subscription is returned
... Pre-conditions: At least one NSD Management subscription is available in the NFVO.
- ... Reference: Clause 5.4.8.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.8.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO does not support the creation of duplicated subscriptions
... Post-Conditions: The existing NSD Management subscription returned is available in the NFVO
@@ -100,7 +100,7 @@ Create duplicated NSD Management subscription with NFVO creating duplicated subs
... Test title: Create duplicated NSD Management subscription with NFVO creating duplicated subscriptions
... Test objective: The objective is to test the creation of a duplicated NSD Management subscription and perform a JSON schema and content validation of the returned duplicated subscription data structure
... Pre-conditions: At least one NSD Management subscription is available in the NFVO.
- ... Reference: Clause 5.4.8.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.8.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO supports the creation of duplicated subscriptions
... Post-Conditions: The duplicated NSD Management subscription is successfully set and it matches the issued subscription
@@ -115,7 +115,7 @@ PUT NSD Management Subscriptions - Method not implemented
... Test title: PUT NSD Management Subscriptions - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to modify NSD Management subscriptions
... Pre-conditions: At least one NSD Management subscription is available in the NFVO.
- ... Reference: Clause 5.4.8.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.8.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -127,7 +127,7 @@ PATCH NSD Management Subscriptions - Method not implemented
... Test title: PATCH NSD Management Subscriptions - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update NSD Management subscriptions
... Pre-conditions: At least one NSD Management subscription is available in the NFVO.
- ... Reference: Clause 5.4.8.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.8.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -139,7 +139,7 @@ DELETE NSD Management Subscriptions - Method not implemented
... Test title: DELETE NSD Management Subscriptions - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to delete NSD Management subscriptions
... Pre-conditions: At least one NSD Management subscription is available in the NFVO.
- ... Reference: Clause 5.4.8.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.8.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: The NSD Management subscriptions are not deleted by the failed operation
@@ -152,7 +152,7 @@ Get All NSD Management Subscriptions as Paged Response
... Test title: Get All NSD Management Subscriptions as Paged Response
... Test objective: The objective is to test the retrieval of all NSD Management subscriptions as a Paged Response.
... Pre-conditions: At least one NSD Management subscription is available in the NFVO.
- ... Reference: Clause 5.4.8.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.8.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -165,7 +165,7 @@ Get NSD Management Subscriptions - Bad Request Response too Big
... Test title: Get NSD Management Subscriptions - Bad Request Response too Big
... Test objective: The objective is to test that the retrieval of NSD Management subscriptions fails because reponse is too big, and perform the JSON schema validation of the failed operation HTTP response.
... Pre-conditions: At least one NSD Management subscription is available in the NFVO.
- ... Reference: Clause 5.4.8.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.8.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -173,14 +173,14 @@ Get NSD Management Subscriptions - Bad Request Response too Big
Check HTTP Response Status Code Is 400
Check HTTP Response Body Json Schema Is ProblemDetails
-Create new NSD Management subscription - Unprocessable Entity
+Create new NSD Management subscription - Unprocessable Content
[Documentation] Test ID: 5.3.1.7.13
- ... Test title: Create new NSD Management subscription - Unprocessable Entity
+ ... Test title: Create new NSD Management subscription - Unprocessable Content
... Test objective: The objective is to test the creation of a new NSD Management subscription fials when 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
... Pre-conditions: none
- ... Reference: Clause 5.4.8.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 5.4.8.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
Send Post Request for NSD Management Subscription
- Check HTTP Response Status Code Is 422
\ No newline at end of file
+ Check HTTP Response Status Code Is 422
diff --git a/SOL005/NSDManagement-API/environment/variables.txt b/SOL005/NSDManagement-API/environment/variables.txt
index 75fd2e67708fab86d53c14afcfdcbcee9335e9b8..1f6581e323531ce0ede03853fc3233fce50c1ffb 100644
--- a/SOL005/NSDManagement-API/environment/variables.txt
+++ b/SOL005/NSDManagement-API/environment/variables.txt
@@ -87,3 +87,5 @@ ${Designer}
${NS_Name}
${NS_Version}
${NS_InvariantId}
+
+${PRODUCER_SUPPORT_COND_REQ} 1
\ No newline at end of file
diff --git a/SOL005/NSFaultManagement-API/Alarms.robot b/SOL005/NSFaultManagement-API/Alarms.robot
index 6b81ff9de336c50a8cdac22d0c691f6f9483290b..65966d475507eabb000c34c4046afd97ba195dbb 100644
--- a/SOL005/NSFaultManagement-API/Alarms.robot
+++ b/SOL005/NSFaultManagement-API/Alarms.robot
@@ -12,7 +12,7 @@ POST Alarms - Method not implemented
... Test title:POST Alarms - Method not implemented
... Test objective: The objective is to test that Post method is not allowed to create Fault management alarms on NFV
... Pre-conditions: none
- ... Reference: Clause 8.4.2.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.2.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -24,7 +24,7 @@ GET information about multiple alarms
... Test title: GET information about multiple alarms
... Test objective: The objective is to retrieve information about the alarm list and perform a JSON schema and content validation of the returned alarms data structure
... Pre-conditions: none
- ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -37,7 +37,7 @@ GET information about multiple alarms with filters
... Test title: GET information about multiple alarms with filters
... Test objective: The objective is to retrieve information about the alarm list and perform a JSON schema and content validation of the returned alarms data structure, and verify that the retrieved information matches the issued attribute-based filters
... Pre-conditions: none
- ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -50,7 +50,7 @@ GET information about multiple alarms Bad Request Invalid attribute-based filter
... Test title: GET information about multiple alarms Bad Request Invalid attribute-based filtering parameters
... Test objective: The objective is to try to retrieve information about the alarm list with invalid filters and perform a JSON schema and content validation of the returned problem details data structure
... Pre-conditions: none
- ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -63,7 +63,7 @@ GET information about multiple alarms with "all_fields" attribute selector
... Test title: GET information about multiple alarms with "all_fields" attribute selector
... Test objective: The objective is to retrieve information about the alarm list
... Pre-conditions: none
- ... Reference: Clause 8.4.2.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.2.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -76,7 +76,7 @@ GET information about multiple alarms with exclude_default attribute selector
... Test title: GET information about multiple alarms with "exclude_default" attribute selector
... Test objective: The objective is to retrieve information about the alarm list
... Pre-conditions: none
- ... Reference: Clause 8.4.2.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.2.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -90,7 +90,7 @@ GET information about multiple alarms with fields attribute selector
... Test title: GET information about multiple alarms with fields attribute selector
... Test objective: The objective is to retrieve information about the alarm list
... Pre-conditions: none
- ... Reference: Clause 8.4.2.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.2.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -103,7 +103,7 @@ GET information about multiple alarms with "exclude_fields" attribute selector
... Test title: GET information about multiple alarms with "exclude_fields" attribute selector
... Test objective: The objective is to retrieve information about the alarm list
... Pre-conditions: none
- ... Reference: Clause 8.4.2.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.2.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -116,7 +116,7 @@ PUT Alarms - Method not implemented
... Test title: PUT Alarms - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed for Fault management alarms on NFV
... Pre-conditions: none
- ... Reference: Clause 8.4.2.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.2.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -128,7 +128,7 @@ PATCH Alarms - Method not implemented
... Test title: PATCH Alarms - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed for Fault management alarms on NFV
... Pre-conditions: none
- ... Reference: Clause 8.4.2.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.2.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -140,7 +140,7 @@ DELETE Alarms - Method not implemented
... Test title: DELETE Alarms - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed for Fault management alarms on NFV
... Pre-conditions: none
- ... Reference: Clause 8.4.2.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.2.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -152,7 +152,7 @@ GET information about multiple alarms as Paged Response
... Test title: GET information about multiple alarms as Paged Response
... Test objective: The objective is to retrieve information about the alarm list as paged response.
... Pre-conditions: none
- ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -165,7 +165,7 @@ GET information about multiple alarms - Bad Request Response too Big
... Test title: GET information about multiple alarms - Bad Request Response too Big
... Test objective: The objective is to test that the retrieval of information about the alarm list fails because response is too big, and perform a JSON schema and content validation of the returned problem details data structure
... Pre-conditions: none
- ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -178,7 +178,7 @@ GET information about multiple alarms with filter "id"
... Test title: GET information about multiple alarms with filter "id"
... Test objective: The objective is to retrieve information about the alarm list with filter "id" and perform a JSON schema and content validation of the returned alarms data structure, and verify that the retrieved information matches the issued attribute-based filters
... Pre-conditions: none
- ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -192,7 +192,7 @@ GET information about multiple alarms with filter "rootCauseFaultyComponent.faul
... Test title: GET information about multiple alarms with filter "rootCauseFaultyComponent.faultyNestedNsInstanceId"
... Test objective: The objective is to retrieve information about the alarm list with filter "rootCauseFaultyComponent.faultyNestedNsInstanceId" and perform a JSON schema and content validation of the returned alarms data structure, and verify that the retrieved information matches the issued attribute-based filters
... Pre-conditions: none
- ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -206,7 +206,7 @@ GET information about multiple alarms with filter "rootCauseFaultyComponent.faul
... Test title: GET information about multiple alarms with filter "rootCauseFaultyComponent.faultyNsVirtualLinkInstanceId"
... Test objective: The objective is to retrieve information about the alarm list with filter "rootCauseFaultyComponent.faultyNsVirtualLinkInstanceId" and perform a JSON schema and content validation of the returned alarms data structure, and verify that the retrieved information matches the issued attribute-based filters
... Pre-conditions: none
- ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -220,7 +220,7 @@ GET information about multiple alarms with filter "rootCauseFaultyComponent.faul
... Test title: GET information about multiple alarms with filter "rootCauseFaultyComponent.faultyVnfInstanceId"
... Test objective: The objective is to retrieve information about the alarm list with filter "rootCauseFaultyComponent.faultyVnfInstanceId" and perform a JSON schema and content validation of the returned alarms data structure, and verify that the retrieved information matches the issued attribute-based filters
... Pre-conditions: none
- ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -234,7 +234,7 @@ GET information about multiple alarms with filter "rootCauseFaultyResource.fault
... Test title: GET information about multiple alarms with filter "rootCauseFaultyResource.faultyResourceType"
... Test objective: The objective is to retrieve information about the alarm list with filter "rootCauseFaultyResource.faultyResourceType" and perform a JSON schema and content validation of the returned alarms data structure, and verify that the retrieved information matches the issued attribute-based filters
... Pre-conditions: none
- ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -248,7 +248,7 @@ GET information about multiple alarms with filter "eventType"
... Test title: GET information about multiple alarms with filter "eventType"
... Test objective: The objective is to retrieve information about the alarm list with filter "eventType" and perform a JSON schema and content validation of the returned alarms data structure, and verify that the retrieved information matches the issued attribute-based filters
... Pre-conditions: none
- ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -262,7 +262,7 @@ GET information about multiple alarms with filter "perceivedSeverity"
... Test title: GET information about multiple alarms with filter "perceivedSeverity"
... Test objective: The objective is to retrieve information about the alarm list with filter "perceivedSeverity" and perform a JSON schema and content validation of the returned alarms data structure, and verify that the retrieved information matches the issued attribute-based filters
... Pre-conditions: none
- ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -276,7 +276,7 @@ GET information about multiple alarms with filter "probableCause"
... Test title: GET information about multiple alarms with filter "probableCause"
... Test objective: The objective is to retrieve information about the alarm list with filter "probableCause" and perform a JSON schema and content validation of the returned alarms data structure, and verify that the retrieved information matches the issued attribute-based filters
... Pre-conditions: none
- ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/NSFaultManagement-API/ApiVersion.robot b/SOL005/NSFaultManagement-API/ApiVersion.robot
index 7d2e9a46904f8f0417e938464190de45855d3e06..11d34bb507e1697f06cea1a345ba63a97939e2fd 100644
--- a/SOL005/NSFaultManagement-API/ApiVersion.robot
+++ b/SOL005/NSFaultManagement-API/ApiVersion.robot
@@ -13,7 +13,7 @@ POST API Version - Method not implemented
... Test title: POST API version - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -25,7 +25,7 @@ GET API Version
... Test title: GET API Version
... Test objective: The objective is to test that GET method successfully return ApiVersionInformation
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -38,7 +38,7 @@ PUT API Version - Method not implemented
... Test title: PUT API Version - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -50,7 +50,7 @@ PATCH API Version - Method not implemented
... Test title: PATCH API Version - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -62,7 +62,7 @@ DELETE API Version - Method not implemented
... Test title: DELETE API Version - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -74,7 +74,7 @@ POST API Version with apiMajorVerion - Method not implemented
... Test title: POST API version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -86,7 +86,7 @@ GET API Version with apiMajorVerion
... Test title: GET API Version with apiMajorVerion
... Test objective: The objective is to test that GET method successfully return ApiVersionInformation
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -99,7 +99,7 @@ PUT API Version with apiMajorVerion - Method not implemented
... Test title: PUT API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -111,7 +111,7 @@ PATCH API Version with apiMajorVerion - Method not implemented
... Test title: PATCH API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -123,7 +123,7 @@ DELETE API Version with apiMajorVerion - Method not implemented
... Test title: DELETE API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/NSFaultManagement-API/IndividualAlarm.robot b/SOL005/NSFaultManagement-API/IndividualAlarm.robot
index 70318462838a3b21a096b2a86850058ac9f86dca..1232ef5c6e887a50be200dfd3be59fd35f3b753a 100644
--- a/SOL005/NSFaultManagement-API/IndividualAlarm.robot
+++ b/SOL005/NSFaultManagement-API/IndividualAlarm.robot
@@ -14,7 +14,7 @@ POST Individual Alarm - Method not implemented
... Test title:POST Individual Alarm - Method not implemented
... Test objective: The objective is to test that POST method is not allowed for Fault management individual alarm on NFV
... Pre-conditions: none
- ... Reference: Clause 8.4.3.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.3.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -26,7 +26,7 @@ GET information about Individual Alarm
... Test title: GET information about Individual Alarm
... Test objective: The objective is to retrieve information about individual alarm and perform a JSON schema and content validation of the returned alarm data structure
... Pre-conditions: The related alarm exists
- ... Reference: Clause 8.4.3.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.3.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -39,7 +39,7 @@ GET information about Invalid Individual Alarm
... Test title: GET information about Invalid Individual Alarm
... Test objective: The objective is to try to read an Invalid individual alarm and get 404 not found response code
... Pre-conditions: The related alarm does not exists
- ... Reference: Clause 8.4.3.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.3.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -52,7 +52,7 @@ PUT Individual Alarm - Method not implemented
... Test title:PUT Individual Alarm - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed for Fault management individual alarm on NFV
... Pre-conditions: none
- ... Reference: Clause 8.4.3.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.3.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -64,7 +64,7 @@ PATCH Alarm
... Test title: Modify an individual alarm resource
... Test objective: The objective is to Modify an individual alarm resource and perform a JSON schema and content validation of the returned alarm modifications data structure
... Pre-conditions: The related alarm exists
- ... Reference: Clause 8.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -77,7 +77,7 @@ PATCH Alarm - Conflict
... Test title: Modify an individual alarm resource - Conflict
... Test objective: The objective is to test that an individual alarm resource cannot be modified if the alarm is already in the state that is requested to be set
... Pre-conditions: The related alarm exists
- ... Reference: Clause 8.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -90,7 +90,7 @@ PATCH Alarm - Precondition failed
... Test title: Modify an individual alarm resource - Precondition failed
... Test objective: The objective is to test that an individual alarm resource cannot be modifed if the resource was modified by another entity
... Pre-conditions: The related alarm exists
- ... Reference: Clause 8.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions:
@@ -98,12 +98,25 @@ PATCH Alarm - Precondition failed
Check HTTP Response Status Code Is 412
Check HTTP Response Body Json Schema Is ProblemDetails
+PATCH Alarm - Precondition failed HTTP Conditional Request Not Supported
+ [Documentation] Test ID: 5.3.3.2.7b
+ ... Test title: Modify an individual alarm resource - Precondition failed HTTP Conditional Request Not Supported
+ ... Test objective: The objective is to test that an individual alarm resource cannot be modifed if API Producer does not support "Last-Modified" and "ETag" HTTP Headers
+ ... Pre-conditions: The related alarm exists
+ ... Reference: Clause 8.4.3.3.4, 4.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
+ ... Config ID: Config_prod_NFVO
+ ... Applicability: API Producer does not support "Last-Modified" and "ETag" HTTP Headers
+ ... Post-Conditions:
+ PATCH Individual Alarm - HTTP Conditional Request not supported
+ Check HTTP Response Status Code Is 412
+ Check HTTP Response Body Json Schema Is ProblemDetails
+
DELETE Individual Alarm - Method not implemented
[Documentation] Test ID: 5.3.3.2.8
... Test title:DELETE Individual Alarm - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed for Fault management individual alarm on NFV
... Pre-conditions: none
- ... Reference: Clause 8.4.3.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.3.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/NSFaultManagement-API/IndividualSubscription.robot b/SOL005/NSFaultManagement-API/IndividualSubscription.robot
index 8b2f372faed578303588a9ca17537e31504145fc..c917ec0ec496738662ee8fee6da22121bbe1ba69 100644
--- a/SOL005/NSFaultManagement-API/IndividualSubscription.robot
+++ b/SOL005/NSFaultManagement-API/IndividualSubscription.robot
@@ -11,7 +11,7 @@ Post Individual Subscription - Method not implemented
... Test title:Post Individual Subscription - Method not implemented
... Test objective: The objective is to test that POST method is not allowed for Fault management subscription on NFV
... Pre-conditions:none
- ... Reference: Clause 8.4.5.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.5.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -23,7 +23,7 @@ Get Information about an individual subscription
... Test title: Get Information about an individual subscription
... Test objective: The objective is to read an individual subscription for NFVO alarms subscribed by the client and perform a JSON schema and content validation of the returned fault management individual subscription data structure
... Pre-conditions: The subscription with the given id exists
- ... Reference: Clause 8.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -36,7 +36,7 @@ PUT an individual subscription - Method not implemented
... Test title:PUT an individual subscription - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed for Fault management subscription on NFV
... Pre-conditions: none
- ... Reference: Clause 8.4.5.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.5.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -48,7 +48,7 @@ PATCH an individual subscription - Method not implemented
... Test title:PATCH an individual subscription - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed for Fault management subscription on NFV
... Pre-conditions: none
- ... Reference: Clause 8.4.5.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.5.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -60,7 +60,7 @@ DELETE an individual subscription
... Test title:DELETE an individual subscription
... Test objective: The objective is to DELETE an individual subscription
... Pre-conditions: The Subsbcription already exists
- ... Reference: Clause 8.4.5.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.5.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: subscription is not deleted
diff --git a/SOL005/NSFaultManagement-API/NSFMOperationKeywords.robot b/SOL005/NSFaultManagement-API/NSFMOperationKeywords.robot
index 939ddbeebb15caf6942bafc68c3fbf50928538e6..f03589b37f8fae493147a4f963a7d702ee6a2d36 100644
--- a/SOL005/NSFaultManagement-API/NSFMOperationKeywords.robot
+++ b/SOL005/NSFaultManagement-API/NSFMOperationKeywords.robot
@@ -209,6 +209,17 @@ PATCH Individual Alarm - ETag mismatch
Patch ${apiRoot}/${apiName}/${apiMajorVersion}/alarms/${alarmId} ${body}
${outputResponse}= Output response
Set Global Variable ${response} ${outputResponse}
+
+PATCH Individual Alarm - HTTP Conditional Request not supported
+ Pass Execution If ${PRODUCER_SUPPORT_COND_REQ} == 1 NVFO allows conditional requests, skipping test
+ log Trying to perform a PATCH. This method modifies an individual alarm resource
+ Set Headers {"Accept":"${ACCEPT}"}
+ Set Headers {"Content-Type": "${CONTENT_TYPE_PATCH}"}
+ Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"${AUTHORIZATION_HEADER}":"${AUTHORIZATION_TOKEN}"}
+ ${body}= Get File jsons/alarmModifications.json
+ Patch ${apiRoot}/${apiName}/${apiMajorVersion}/alarms/${alarmId} ${body}
+ ${outputResponse}= Output response
+ Set Global Variable ${response} ${outputResponse}
POST Subscription
Log Create subscription instance by POST to ${apiRoot}/${apiName}/${apiMajorVersion}/subscriptions
diff --git a/SOL005/NSFaultManagement-API/NotificationEndpoint.robot b/SOL005/NSFaultManagement-API/NotificationEndpoint.robot
index 099e56302846958fa1cc8a67b741edbf2a710167..09a20920cc46667de6682a68476ec6a7c52595d7 100644
--- a/SOL005/NSFaultManagement-API/NotificationEndpoint.robot
+++ b/SOL005/NSFaultManagement-API/NotificationEndpoint.robot
@@ -13,7 +13,7 @@ NS Fault Alarm Notification
... Test title: NS Fault Alarm Notification
... Test objective: The objective is to test that NS Fault Alarm Notification is delivered with success to the notification consumer
... Pre-conditions: A NS instance is instantiated, and a subscription for fault alarm notifications is available in the NFVO.
- ... Reference: Clause 8.4.6.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.6.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
@@ -25,7 +25,7 @@ NS Fault Alarm Cleared Notification
... Test title: NS Fault Alarm Cleared Notification
... Test objective: The objective is to test that NS Fault Alarm Cleared Notification is delivered with success to the notification consumer
... Pre-conditions: A NS instance is instantiated, and a subscription for fault alarm cleared notifications is available in the NFVO.
- ... Reference: Clause 8.4.6.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.6.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
@@ -37,7 +37,7 @@ NS Fault Alarm List Rebuilt Notification
... Test title: NS Fault Alarm List Rebuilt Notification
... Test objective: The objective is to test that NS Fault Alarm List Rebuilt Notification is delivered with success to the notification consumer
... Pre-conditions: A NS instance is instantiated, and a subscription for fault alarm list rebuilt notifications is available in the NFVO.
- ... Reference: Clause 8.4.6.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.6.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/NSFaultManagement-API/Notifications.robot b/SOL005/NSFaultManagement-API/Notifications.robot
index 34910d3b87091e1744709f6046cbb5d339bb8ab3..52ef3b75c00673e497897cde8a6e4c08e4597523 100644
--- a/SOL005/NSFaultManagement-API/Notifications.robot
+++ b/SOL005/NSFaultManagement-API/Notifications.robot
@@ -18,7 +18,7 @@ NS Fault Alarm Notification
... Test title: NS Fault Alarm Notification
... Test objective: The objective is to test the dispatch of NS Fault Alarm Notification when a virtualised resource within an NS instance fails, and perform a JSON schema and content validation of the delivered notification. The action that triggers the notification under test is an explicit test step, but it is not performed by the test system.
... Pre-conditions: A NS instance is instantiated, and a subscription for fault alarm notifications is available in the NFVO.
- ... Reference: Clause 8.4.6.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.6.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -31,7 +31,7 @@ NS Fault Alarm Cleared Notification
... Test title: NS Fault Alarm Cleared Notification
... Test objective: The objective is to test the dispatch of NS Fault Alarm Cleared Notification when a faulty virtualised resource within an NS instance is cleared, and perform a JSON schema and content validation of the delivered notification. The action that triggers the notification under test is an explicit test step, but it is not performed by the test system.
... Pre-conditions: A NS instance is instantiated, a virtualised resource is in faulty state, and a subscription for fault alarm cleared notifications is available in the NFVO.
- ... Reference: Clause 8.4.6.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.6.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -44,7 +44,7 @@ NS Fault Alarm List Rebuilt Notification
... Test title: NS Fault Alarm List Rebuilt Notification
... Test objective: The objective is to test the dispatch of NS Fault Alarm List Rebuilt Notification when the NFVO decides to rebuild the list of its NS alarms, e.g. due to a corruption in the alarm storage, and perform a JSON schema and content validation of the delivered notification. The action that triggers the notification under test is an explicit test step, but it is not performed by the test system.
... Pre-conditions: A NS instance is instantiated, one or more virtualised resource are in faulty state, and a subscription for fault alarm list rebuilt notifications is available in the NFVO.
- ... Reference: Clause 8.4.6.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.6.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -57,7 +57,7 @@ NS Fault Alarm Notification with Instrumental Platform Hook
... Test title: NS Fault Alarm Notification with Instrumental Platform Hook
... Test objective: The objective is to test the dispatch of NS Fault Alarm Notification when a virtualised resource failure within an NS instance is automatically triggered through an instrumenation platform, and perform a JSON schema and content validation of the delivered notification.
... Pre-conditions: A NS instance is instantiated
- ... Reference: Clause 8.4.6.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.6.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: An instrumentation platform is available to trigger the NS instance failure condition
... Post-Conditions: none
@@ -70,7 +70,7 @@ NS Fault Alarm Cleared Notification with Instrumental Platform Hook
... Test title: NS Fault Alarm Cleared Notification with Instrumental Platform Hook
... Test objective: The objective is to test the dispatch of NS Fault Clear Alarm Notification when a virtualised resource failure within an NS instance is automatically cleared through an instrumenation platform, and perform a JSON schema and content validation of the delivered notification.
... Pre-conditions: A NS instance is instantiated and a virtualised resource is in faulty state.
- ... Reference: Clause 8.4.6.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.6.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: An instrumentation platform is available to trigger the NS instance failure clear condition
... Post-Conditions: none
@@ -83,7 +83,7 @@ NS Fault Alarm List Rebuilt Notification with Instrumental Platform Hook
... Test title: NS Fault Alarm List Rebuilt Notification with Instrumental Platform Hook
... Test objective: The objective is to test the dispatch of NS Fault Alarm List Rebuilt Notification when the NFVO decision to rebuild the list of its NS alarms is automatically triggered through an instrumentation platform, and perform a JSON schema and content validation of the delivered notification.
... Pre-conditions: A NS instance is instantiated and one or more virtualised resource are in faulty state
- ... Reference: Clause 8.4.6.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.6.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: An instrumentation platform is available to trigger the NS instance alarm list rebuilt condition
... Post-Conditions: none
diff --git a/SOL005/NSFaultManagement-API/Subscriptions.robot b/SOL005/NSFaultManagement-API/Subscriptions.robot
index eb6fe275e8381407aab4c0838565c3b82fec5ad2..1b8f094728bd26dfa313b79f5ab1e0deed8d1526 100644
--- a/SOL005/NSFaultManagement-API/Subscriptions.robot
+++ b/SOL005/NSFaultManagement-API/Subscriptions.robot
@@ -16,7 +16,7 @@ Create a new alarm subscription
... Test title: Create a new alarm subscription
... Test objective: The objective is to create a new Fault management alarm subscriptions and perform a JSON schema and content validation of the returned fault management alarms subscription data structure
... Pre-conditions: no subscription with the same filter and callbackUri exists
- ... Reference: Clause 8.4.4.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.4.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -30,7 +30,7 @@ Create a duplicated Subscription
... Test title: Create a duplicated alarm subscription
... Test objective: The objective is to create a new subscription with the NFV allowing duplication and perform a JSON schema and content validation of the returned fault management alarms subscription data structure..
... Pre-conditions: subscription with the same filter and callbackUri exists
- ... Reference: Clause 8.4.4.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.4.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability:
... Post-Conditions: none
@@ -54,7 +54,7 @@ Retrieve a list of alarm subscriptions
... Test title: Retrieve a list of alarm subscriptions
... Test objective: The objective is to retrieve the list of active subscriptions and perform a JSON schema and content validation of the returned fault management alarms subscription data structure.
... Pre-conditions: none
- ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -67,7 +67,7 @@ Retrieve a list of alarm subscriptions - Filter
... Test title: Retrieve a list of alarm subscriptions - Filter
... Test objective: The objective is to retrieve the list of active subscriptions with filter and perform a JSON schema and content validation of the returned fault management alarms subscription data structure.
... Pre-conditions: none
- ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -80,7 +80,7 @@ GET subscriptions - Bad Request Invalid attribute-based filtering parameters
... Test title: GET subscriptions - Bad Request Invalid attribute-based filtering parameters
... Test objective:The objective is to retrieve the list of active subscriptions with Invalid attribute-based filtering parameters and perform a JSON schema and content validation of the returned problem details data structure.
... Pre-conditions: none
- ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -93,7 +93,7 @@ GET subscriptions with "all_fields" attribute selector
... Test title: GET subscriptions with "all_fields" attribute selector
... Test objective: The objective is to retrieve the list of active subscriptions with attribute selector
... Pre-conditions:
- ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability:
... Post-Conditions:
@@ -106,7 +106,7 @@ GET subscriptions with "exclude_default" attribute selector
... Test title: GET subscriptions with "exclude_default" attribute selector
... Test objective: The objective is to retrieve the list of active subscriptions with attribute selector
... Pre-conditions: none
- ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -119,7 +119,7 @@ GET subscriptions with "fields" attribute selector
... Test title: GET subscriptions with "fields" attribute selector
... Test objective: The objective is to retrieve the list of active subscriptions with attribute selector
... Pre-conditions: none
- ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -132,7 +132,7 @@ GET subscriptions with "exclude_fields" attribute selector
... Test title: GET subscriptions with "exclude_fields" attribute selector
... Test objective: The objective is to retrieve the list of active subscriptions with attribute selector
... Pre-conditions: none
- ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -145,7 +145,7 @@ PUT subscriptions - Method not implemented
... Test title:PUT subscriptions - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to for Fault management subscriptions on NFV
... Pre-conditions: none
- ... Reference: Clause 8.4.4.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.4.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -157,7 +157,7 @@ PATCH subscriptions - Method not implemented
... Test title:PATCH subscriptions - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to for Fault management subscriptions on NFV
... Pre-conditions: none
- ... Reference: Clause 8.4.4.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.4.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -169,7 +169,7 @@ DELETE subscriptions - Method not implemented
... Test title: DELETE subscriptions - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to for Fault management subscriptions on NFV
... Pre-conditions: none
- ... Reference: Clause 8.4.4.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.4.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -181,7 +181,7 @@ Retrieve a list of alarm subscriptions as Paged Response
... Test title: Retrieve a list of alarm subscriptions as Paged Response
... Test objective: The objective is to retrieve the list of active subscriptions as paged response.
... Pre-conditions: none
- ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -194,7 +194,7 @@ GET subscriptions - Bad Request Response too Big
... Test title: GET subscriptions - Bad Request Response too Big
... Test objective:The objective is test that the retrieval of active subscriptions list fails because response is too big, and perform a JSON schema and content validation of the returned problem details data structure.
... Pre-conditions: none
- ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -207,7 +207,7 @@ Retrieve a list of alarm subscriptions with filter "id"
... Test title: Retrieve a list of alarm subscriptions with filter "id"
... Test objective: The objective is to retrieve the list of active subscriptions with filter "id" and perform a JSON schema and content validation of the returned fault management alarms subscription data structure.
... Pre-conditions: none
- ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -221,7 +221,7 @@ Retrieve a list of alarm subscriptions with filter "filter.notificationTypes"
... Test title: Retrieve a list of alarm subscriptions with filter "filter.notificationTypes"
... Test objective: The objective is to retrieve the list of active subscriptions with filter "filter.notificationTypes" and perform a JSON schema and content validation of the returned fault management alarms subscription data structure.
... Pre-conditions: none
- ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -235,7 +235,7 @@ Retrieve a list of alarm subscriptions with filter "filter.faultyResourceTypes"
... Test title: Retrieve a list of alarm subscriptions with filter "filter.faultyResourceTypes"
... Test objective: The objective is to retrieve the list of active subscriptions with filter "filter.faultyResourceTypes" and perform a JSON schema and content validation of the returned fault management alarms subscription data structure.
... Pre-conditions: none
- ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -249,7 +249,7 @@ Retrieve a list of alarm subscriptions with filter "filter.perceivedSeverities"
... Test title: Retrieve a list of alarm subscriptions with filter "filter.perceivedSeverities"
... Test objective: The objective is to retrieve the list of active subscriptions with filter "filter.perceivedSeverities" and perform a JSON schema and content validation of the returned fault management alarms subscription data structure.
... Pre-conditions: none
- ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -263,7 +263,7 @@ Retrieve a list of alarm subscriptions with filter "filter.eventTypes"
... Test title: Retrieve a list of alarm subscriptions with filter "filter.eventTypes"
... Test objective: The objective is to retrieve the list of active subscriptions with filter "filter.eventTypes" and perform a JSON schema and content validation of the returned fault management alarms subscription data structure.
... Pre-conditions: none
- ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -277,7 +277,7 @@ Retrieve a list of alarm subscriptions with filter "filter.probableCauses"
... Test title: Retrieve a list of alarm subscriptions with filter "filter.probableCauses"
... Test objective: The objective is to retrieve the list of active subscriptions with filter "filter.probableCauses" and perform a JSON schema and content validation of the returned fault management alarms subscription data structure.
... Pre-conditions: none
- ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -286,12 +286,12 @@ Retrieve a list of alarm subscriptions with filter "filter.probableCauses"
Check HTTP Response Body Json Schema Is FmSubscriptions
Check PostCondition HTTP Response Body Subscriptions Matches the requested attribute-based filter "filter_probableCauses"
-Create a new alarm subscription - Unprocessable Entity
+Create a new alarm subscription - Unprocessable Content
[Documentation] Test ID: 5.3.3.3.22
- ... Test title: Create a new alarm subscription- Unprocessable Entity
+ ... Test title: Create a new alarm subscription- Unprocessable Content
... Test objective: The objective is to test that creation of a new Fault management alarm subscriptions fials when 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.
... Pre-conditions:
- ... Reference: Clause 8.4.4.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 8.4.4.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/NSFaultManagement-API/environment/variables.txt b/SOL005/NSFaultManagement-API/environment/variables.txt
index a625ac8387b5ded7a476cb3457f6ae6d680c34dd..55f08b37190623536a85464c45bd3f2dba7ca9af 100644
--- a/SOL005/NSFaultManagement-API/environment/variables.txt
+++ b/SOL005/NSFaultManagement-API/environment/variables.txt
@@ -61,4 +61,6 @@ ${callbackResp} 127.0.0.1
### Instrumentation platform variables
${nsInstanceIdForNotifications} SOME-ID
${upperTesterUrlForAlarmNotifications} http://localhost:9999/uppertester
-${instrumentationPlatformSkip} True
\ No newline at end of file
+${instrumentationPlatformSkip} True
+
+${PRODUCER_SUPPORT_COND_REQ} 1
\ No newline at end of file
diff --git a/SOL005/NSLCMCoordination-API/ApiVersion.robot b/SOL005/NSLCMCoordination-API/ApiVersion.robot
index 2766a31ca085ed2dd256f9be3e5cb5bdabd0847b..2c0d5082254416c89f67287b9065186fb4de211f 100644
--- a/SOL005/NSLCMCoordination-API/ApiVersion.robot
+++ b/SOL005/NSLCMCoordination-API/ApiVersion.robot
@@ -13,7 +13,7 @@ POST API Version - Method not implemented
... Test title: POST API version - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_OSS/BSS
... Applicability: none
... Post-Conditions: none
@@ -25,7 +25,7 @@ GET API Version
... Test title: GET API Version
... Test objective: The objective is to test that GET method successfully return ApiVersionInformation
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_OSS/BSS
... Applicability: none
... Post-Conditions: none
@@ -38,7 +38,7 @@ PUT API Version - Method not implemented
... Test title: PUT API Version - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_OSS/BSS
... Applicability: none
... Post-Conditions: none
@@ -50,7 +50,7 @@ PATCH API Version - Method not implemented
... Test title: PATCH API Version - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_OSS/BSS
... Applicability: none
... Post-Conditions: none
@@ -62,7 +62,7 @@ DELETE API Version - Method not implemented
... Test title: DELETE API Version - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_OSS/BSS
... Applicability: none
... Post-Conditions: none
@@ -74,7 +74,7 @@ POST API Version with apiMajorVerion - Method not implemented
... Test title: POST API version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_OSS/BSS
... Applicability: none
... Post-Conditions: none
@@ -86,7 +86,7 @@ GET API Version with apiMajorVerion
... Test title: GET API Version with apiMajorVerion
... Test objective: The objective is to test that GET method successfully return ApiVersionInformation
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_OSS/BSS
... Applicability: none
... Post-Conditions: none
@@ -99,7 +99,7 @@ PUT API Version with apiMajorVerion - Method not implemented
... Test title: PUT API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_OSS/BSS
... Applicability: none
... Post-Conditions: none
@@ -111,7 +111,7 @@ PATCH API Version with apiMajorVerion - Method not implemented
... Test title: PATCH API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_OSS/BSS
... Applicability: none
... Post-Conditions: none
@@ -123,7 +123,7 @@ DELETE API Version with apiMajorVerion - Method not implemented
... Test title: DELETE API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_OSS/BSS
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/NSLCMCoordination-API/CancelCoordinationActionTask.robot b/SOL005/NSLCMCoordination-API/CancelCoordinationActionTask.robot
index 14f2befc326dcb23e89d2a0e83012a7caa710f6e..a9fb107ae11347862923e936c879ad1034ce0ad1 100644
--- a/SOL005/NSLCMCoordination-API/CancelCoordinationActionTask.robot
+++ b/SOL005/NSLCMCoordination-API/CancelCoordinationActionTask.robot
@@ -13,7 +13,7 @@ Request a cancellation of an ongoing coordination action
... Test title: Request a cancellation of an ongoing coordination action
... Test objective: The objective is to test the request for the cancellation of an ongoing coordination task
... Pre-conditions: An ongoing coordination action is available
- ... Reference: Clause 12.4.4.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 12.4.4.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_OSS/BSS
... Applicability: none
... Post-Conditions: none
@@ -26,7 +26,7 @@ Request a cancellation of a finished coordination action
... Test title: Request a cancellation of a finished coordination action
... Test objective: The objective is to test the request for the cancellation of a finished coordination action
... Pre-conditions: A finished coordination action is available
- ... Reference: Clause 12.4.4.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 12.4.4.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_OSS/BSS
... Applicability: none
... Post-Conditions: none
@@ -40,7 +40,7 @@ Request a cancellation of an ongoing coordination action without authentication
... Test title: Request a cancellation of an ongoing coordination action without authentication
... Test objective: The objective is to test the failure of the request for a cancellation of a coordination task when no authentication is used
... Pre-conditions: none
- ... Reference: Clause 12.4.4.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 12.4.4.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_OSS/BSS
... Applicability: none
... Post-Conditions: none
@@ -53,7 +53,7 @@ GET information about a cancellation of an ongoing coordination action - method
... Test title: GET information about a cancellation of an ongoing coordination action - method not implemented
... Test objective: The objective is to test that the GET method is not allowed to retrieve cancellation details of an ongoing coordination action
... Pre-conditions: A cancellation task has been activated
- ... Reference: Clause 12.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 12.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_OSS/BSS
... Applicability: none
... Post-Conditions: none
@@ -66,7 +66,7 @@ PUT information about a cancellation of an ongoing coordination action - method
... Test title: PUT information about a cancellation of an ongoing coordination action - method not implemented
... Test objective: The objective is to test that the PUT method is not allowed to modify cancellation details of an ongoing coordination action
... Pre-conditions: A cancellation task has been activated
- ... Reference: Clause 12.4.4.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 12.4.4.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_OSS/BSS
... Applicability: none
... Post-Conditions: none
@@ -79,7 +79,7 @@ PATCH information about a cancellation of an ongoing coordination action - metho
... Test title: PATCH information about a cancellation of an ongoing coordination action - method not implemented
... Test objective: he objective is to test that the PATCH method is not allowed to modify cancellation details of an ongoing coordination action
... Pre-conditions: A cancellation task has been activated
- ... Reference: Clause 12.4.4.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 12.4.4.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_OSS/BSS
... Applicability: none
... Post-Conditions: none
@@ -92,7 +92,7 @@ DELETE information about a cancellation of an ongoing coordination action - meth
... Test title: DELETE information about a cancellation of an ongoing coordination action - method not implemented
... Test objective: The objective is to test that the DELETE method is not allowed to remove cancellation details of an ongoing coordination action
... Pre-conditions: A cancellation task has been activated
- ... Reference: Clause 12.4.4.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 12.4.4.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_OSS/BSS
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/NSLCMCoordination-API/Coordinations.robot b/SOL005/NSLCMCoordination-API/Coordinations.robot
index cfb9ef73018d87fda7ccb47bd0d20daf8f76e5ea..4fb278643cd32b403ef5843ee714e12c2a2d674d 100644
--- a/SOL005/NSLCMCoordination-API/Coordinations.robot
+++ b/SOL005/NSLCMCoordination-API/Coordinations.robot
@@ -13,7 +13,7 @@ Request a Coordination of an LCM operation occurrence synchronously
... Test title: Request a Coordination of an LCM operation occurrence synchronously
... Test objective: The objective is to test the synchronous request for the coordination of an LCM operation occurrence and perform the JSON schema validation of the returned structure
... Pre-conditions: The status of the related LCM opeation occurrence is "PROCESSING"
- ... Reference: Clause 12.4.2.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 12.4.2.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_OSS/BSS
... Applicability: none
... Post-Conditions: A Individual coordination action resource is successfully created on the NFVO
@@ -29,7 +29,7 @@ Request a Coordination of an LCM operation occurrence asynchronously
... Test title: Request a Coordination of an LCM operation occurrence asynchronously
... Test objective: The objective is to test the asynchronous request for the coordination of an LCM operation occurrence and perform the validation of the headers returned
... Pre-conditions: The status of the related LCM opeation occurrence is "PROCESSING"
- ... Reference: Clause 12.4.2.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 12.4.2.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_OSS/BSS
... Applicability: none
... Post-Conditions: none
@@ -42,7 +42,7 @@ Request a Coordination of an LCM operation occurrence - FORBIDDEN
... Test title: Request a Coordination of an LCM operation occurrence - FORBIDDEN
... Test objective: The objective is to test the failure of a request for the coordination of an LCM operation occurrence
... Pre-conditions: The status of the related LCM opeation occurrence is "PROCESSING". The request is performed by a user that has not the grant to run this operation
- ... Reference: Clause 12.4.2.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 12.4.2.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_OSS/BSS
... Applicability: none
... Post-Conditions: none
@@ -55,7 +55,7 @@ Request a Coordination of an LCM operation occurrence - CONFLICT
... Test title: Request a Coordination of an LCM operation occurrence - CONFLICT
... Test objective: The objective is to test the failure of a request for the coordination of an LCM operation occurrence
... Pre-conditions: The status of the related LCM opeation occurrence is not "PROCESSING"
- ... Reference: Clause 12.4.2.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 12.4.2.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_OSS/BSS
... Applicability: none
... Post-Conditions: none
@@ -69,7 +69,7 @@ Request a Coordination of an LCM operation occurrence synchronously - Service Un
... Test title: Request a Coordination of an LCM operation occurrence synchronously - Service Unavailable
... Test objective: The objective is to test the request for the coordination of an LCM operation occurrence and the verify that the NFVO cannot perform immediately the request, but can perform it sometime in the future.
... Pre-conditions: The status of the related LCM opeation occurrence is "PROCESSING" but API producer cannot perform immediately the request
- ... Reference: Clause 12.4.2.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 12.4.2.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_OSS/BSS
... Applicability: none
... Post-Conditions: none
@@ -83,7 +83,7 @@ Request a Coordination of an LCM operation occurrence without authentication
... Test title: Request a Coordination of an LCM operation occurrence without authentication
... Test objective: The objective is to test the failure of the request for the coordination of an LCM operation occurrence without providing an authentication token
... Pre-conditions: The status of the related LCM opeation occurrence is "PROCESSING"
- ... Reference: Clause 12.4.2.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 12.4.2.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_OSS/BSS
... Applicability: none
... Post-Conditions: none
@@ -96,7 +96,7 @@ GET all Coordinations of an LCM operation occurrence - method not implemented
... Test title: GET all Coordinations of an LCM operation occurrence - method not implemented
... Test objective: The objective is to test that the GET method is not allowed to retrieve coordination requests information
... Pre-conditions: The status of the related LCM opeation occurrence is "PROCESSING"
- ... Reference: Clause 12.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 12.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_OSS/BSS
... Applicability: none
... Post-Conditions: none
@@ -109,7 +109,7 @@ PUT all Coordinations of an LCM operation occurrence - method not implemented
... Test title: PUT all Coordinations of an LCM operation occurrence - method not implemented
... Test objective: The objective is to test that the PUT method is not allowed to modify coordination requests information
... Pre-conditions: The status of the related LCM opeation occurrence is "PROCESSING"
- ... Reference: Clause 12.4.2.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 12.4.2.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_OSS/BSS
... Applicability: none
... Post-Conditions: none
@@ -122,7 +122,7 @@ PATCH all Coordinations of an LCM operation occurrence - method not implemented
... Test title: PATCH all Coordinations of an LCM operation occurrence - method not implemented
... Test objective: The objective is to test that the PATCH method is not allowed to modify coordination requests information
... Pre-conditions: The status of the related LCM opeation occurrence is "PROCESSING"
- ... Reference: Clause 12.4.2.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 12.4.2.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_OSS/BSS
... Applicability: none
... Post-Conditions: none
@@ -135,7 +135,7 @@ DELETE all Coordinations of an LCM operation occurrence - method not implemented
... Test title: DELETE all Coordinations of an LCM operation occurrence - method not implemented
... Test objective: The objective is to test that the DELETE method is not allowed to remove coordination requests information
... Pre-conditions: The status of the related LCM opeation occurrence is "PROCESSING"
- ... Reference: Clause 12.4.2.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 12.4.2.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_OSS/BSS
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/NSLCMCoordination-API/IndividualCoordinationAction.robot b/SOL005/NSLCMCoordination-API/IndividualCoordinationAction.robot
index e31cdcf44adabf2cb6336e6c608f80eb316669f2..f79a7d446d9ba35588d9ceececbf16defe843f4b 100644
--- a/SOL005/NSLCMCoordination-API/IndividualCoordinationAction.robot
+++ b/SOL005/NSLCMCoordination-API/IndividualCoordinationAction.robot
@@ -13,7 +13,7 @@ POST an individual coordination action of an LCM operation occurrence - method n
... Test title: POST an individual coordination action of an LCM operation occurrence - method not implemented
... Test objective: The objective is to test that the POST method is not allowed to submit a new individuaal coordination requests information
... Pre-conditions: One or more LCM Coordinations have been requested
- ... Reference: Clause 12.4.3.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 12.4.3.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_OSS/BSS
... Applicability: none
... Post-Conditions: none
@@ -26,7 +26,7 @@ Get information about a finished coordination task
... Test title: Get information about a finished coordination task
... Test objective: The objective is to retrieve information about an individual coordination task and perform a JSON schema validation.
... Pre-conditions: Individual coordination task is terminated
- ... Reference: Clause 12.4.3.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 12.4.3.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_OSS/BSS
... Applicability: none
... Post-Conditions: none
@@ -40,7 +40,7 @@ Get information about an ongoing coordination task
... Test title: Get information about an ongoing coordination task
... Test objective: The objective is to retrieve information about an individual coordination task that is still in running or is in the process of being cancelled
... Pre-conditions: Individual coordination task is still ongoing or is in the process of being cancelled
- ... Reference: Clause 12.4.3.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 12.4.3.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_OSS/BSS
... Applicability: none
... Post-Conditions: none
@@ -53,7 +53,7 @@ Get information about an invalid coordination task
... Test title: Get information about an invalid coordination task
... Test objective: The objective is to try to read an individual coordination task
... Pre-conditions: Individual coordination task is not present
- ... Reference: Clause 12.4.3.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 12.4.3.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_OSS/BSS
... Applicability: none
... Post-Conditions: none
@@ -66,7 +66,7 @@ Get information about a finished coordination task without authentication
... Test title: Get information about a finished coordination task without authentication
... Test objective: The objective is to try to read an individual coordination task without using authentication
... Pre-conditions: none
- ... Reference: Clause 12.4.3.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 12.4.3.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_OSS/BSS
... Applicability: none
... Post-Conditions: none
@@ -79,7 +79,7 @@ PUT an individual coordination action of an LCM operation occurrence - method no
... Test title: PUT an individual coordination action of an LCM operation occurrence - method not implemented
... Test objective: The objective is to test that the PUT method is not allowed to modify an individual coordination action
... Pre-conditions: One or more LCM Coordinations have been requested
- ... Reference: Clause 12.4.3.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 12.4.3.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_OSS/BSS
... Applicability: none
... Post-Conditions: none
@@ -92,7 +92,7 @@ PATCH an individual coordination action of an LCM operation occurrence - method
... Test title: PATCH an individual coordination action of an LCM operation occurrence - method not implemented
... Test objective: The objective is to test that the PATCH method is not allowed to modify an individual coordination action
... Pre-conditions: One or more LCM Coordinations have been requested
- ... Reference: Clause 12.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 12.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_OSS/BSS
... Applicability: none
... Post-Conditions: none
@@ -105,7 +105,7 @@ DELETE an individual coordination action of an LCM operation occurrence - method
... Test title: DELETE an individual coordination action of an LCM operation occurrence - method not implemented
... Test objective: The objective is to test that the DELETE method is not allowed to remove an individual coordination action
... Pre-conditions: One or more LCM Coordinations have been requested
- ... Reference: Clause 12.4.3.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 12.4.3.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_OSS/BSS
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/NSLifecycleManagement-API/ApiVersion.robot b/SOL005/NSLifecycleManagement-API/ApiVersion.robot
index 5434374b67a94b6c151b287d5dedcbe20472cd56..588bada5cc422df8e136cc8f6bf38912e5fa7840 100644
--- a/SOL005/NSLifecycleManagement-API/ApiVersion.robot
+++ b/SOL005/NSLifecycleManagement-API/ApiVersion.robot
@@ -13,7 +13,7 @@ POST API Version - Method not implemented
... Test title: POST API version - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -25,7 +25,7 @@ GET API Version
... Test title: GET API Version
... Test objective: The objective is to test that GET method successfully return ApiVersionInformation
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -38,7 +38,7 @@ PUT API Version - Method not implemented
... Test title: PUT API Version - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -50,7 +50,7 @@ PATCH API Version - Method not implemented
... Test title: PATCH API Version - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -62,7 +62,7 @@ DELETE API Version - Method not implemented
... Test title: DELETE API Version - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -74,7 +74,7 @@ POST API Version with apiMajorVerion - Method not implemented
... Test title: POST API version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -86,7 +86,7 @@ GET API Version with apiMajorVerion
... Test title: GET API Version with apiMajorVerion
... Test objective: The objective is to test that GET method successfully return ApiVersionInformation
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -99,7 +99,7 @@ PUT API Version with apiMajorVerion - Method not implemented
... Test title: PUT API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -111,7 +111,7 @@ PATCH API Version with apiMajorVerion - Method not implemented
... Test title: PATCH API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -123,7 +123,7 @@ DELETE API Version with apiMajorVerion - Method not implemented
... Test title: DELETE API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/NSLifecycleManagement-API/CancelOperationTask.robot b/SOL005/NSLifecycleManagement-API/CancelOperationTask.robot
index b3c5c4563a078882a709d0df48f8da69a63328f7..828e1ed74d085fababba42a9a3cea64da814bf9d 100644
--- a/SOL005/NSLifecycleManagement-API/CancelOperationTask.robot
+++ b/SOL005/NSLifecycleManagement-API/CancelOperationTask.robot
@@ -13,7 +13,7 @@ POST Cancel operation task
... Test title: POST Cancel operation task
... Test objective: The objective is to test that POST method cancel the NS LCM operation
... Pre-conditions: NS instance status equal to STARTING, PROCESSING or ROLLING_BACK
- ... Reference: Clause 6.4.15.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.15.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: NS instance status equal to FAILED_TEMP
@@ -26,7 +26,7 @@ POST Cancel operation task Not Found
... Test title: POST Cancel operation task Not Found
... Test objective: The objective is to test that POST method fail completing the Cancel NS LCM operation if the resource is not found
... Pre-conditions: none
- ... Reference: Clause 6.4.15.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.15.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -39,7 +39,7 @@ POST Cancel operation task Conflict
... Test title: POST Cancel operation task Conflict
... Test objective: The objective is to test that POST method fail if a status conflict exist on the NS LCM operation. (i.e. NS instance status not equal to STARTING, PROCESSING or ROLLING_BACK)
... Pre-conditions: NS instance status not equal to STARTING, PROCESSING or ROLLING_BACK
- ... Reference: Clause 6.4.15.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.15.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -52,7 +52,7 @@ GET Cancel operation task - Method not implemented
... Test title: GET Cancel operation task - Method not implemented
... Test objective: The objective is to test that GET method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.15.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.15.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -64,7 +64,7 @@ PUT Cancel operation task - Method not implemented
... Test title: PUT Cancel operation task - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.15.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.15.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -76,7 +76,7 @@ PATCH Cancel operation task - Method not implemented
... Test title: PATCH Cancel operation task - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.15.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.15.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -88,7 +88,7 @@ DELETE Cancel operation task - Method not implemented
... Test title: DELETE Cancel operation task - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.15.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.15.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/NSLifecycleManagement-API/ContinueOperationTask.robot b/SOL005/NSLifecycleManagement-API/ContinueOperationTask.robot
index 4e63abe8c9369e536564e05fb88b7a17b7aa1086..050be51cb2185adae945590379cd0c61236a4bbc 100644
--- a/SOL005/NSLifecycleManagement-API/ContinueOperationTask.robot
+++ b/SOL005/NSLifecycleManagement-API/ContinueOperationTask.robot
@@ -13,7 +13,7 @@ POST Continue operation task
... Test title: POST Continue operation task
... Test objective: The objective is to test that POST method trigger a continue on the LCM operation
... Pre-conditions: NS instance status equal to FAILED_TEMP
- ... Reference: Clause 6.4.13.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.13.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: NS instance status not equal to FAILED_TEMP
@@ -26,7 +26,7 @@ POST Continue operation task Not Found
... Test title: POST Continue operation task Not Found
... Test objective: The objective is to test that POST method cannot perform a continue operation task because the resource is not found
... Pre-conditions: none
- ... Reference: Clause 6.4.13.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.13.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -39,7 +39,7 @@ POST Continue operation task Conflict
... Test title: POST Continue operation task Conflict
... Test objective: The objective is to test that POST method fail in case of operation status conflict (i.e. NS instance status not equal to FAILED_TEMP )
... Pre-conditions: NS instance status not equal to FAILED_TEMP
- ... Reference: Clause 6.4.13.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.13.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -52,7 +52,7 @@ GET Continue operation task - Method not implemented
... Test title: GET Continue operation task - Method not implemented
... Test objective: The objective is to test that GET method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.13.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.13.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -64,7 +64,7 @@ PUT Continue operation task - Method not implemented
... Test title: PUT Continue operation task - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.13.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.13.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -76,7 +76,7 @@ PATCH Continue operation task - Method not implemented
... Test title: PATCH Continue operation task - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.14.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.14.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -88,7 +88,7 @@ DELETE Continue operation task - Method not implemented
... Test title: DELETE Continue operation task - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.14.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.14.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/NSLifecycleManagement-API/CreateNSInstanceWorkflow.robot b/SOL005/NSLifecycleManagement-API/CreateNSInstanceWorkflow.robot
index 5e404603a05a859118ca15b71c63c2526dd8af7f..6f13626cf16cf365c0635e2461d5dde358493960 100644
--- a/SOL005/NSLifecycleManagement-API/CreateNSInstanceWorkflow.robot
+++ b/SOL005/NSLifecycleManagement-API/CreateNSInstanceWorkflow.robot
@@ -15,7 +15,7 @@ NS Instance Creation
... Test title: NS Instance Creation
... Test objective: The objective is to test the workflow for Creating a NS instance
... Pre-conditions: none
- ... Reference: Clause 6.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: The NS resource is in NOT_ISTANTIATED state
@@ -32,7 +32,7 @@ NS Instance Creation with DISABLED Network Service Descriptor
... Test title: NS Instance Creation with DISABLED Network Service Descriptor
... Test objective: The objective is to test the workflow for Creating a NS instance with a disabled NSD
... Pre-conditions: One or more Network Service Descriptors are onboarded in the NFVO in disabled operational state.
- ... Reference: Clauses 6.4.2.3.1 and 5.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clauses 6.4.2.3.1 and 5.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/NSLifecycleManagement-API/DeleteNSInstanceWorkflow.robot b/SOL005/NSLifecycleManagement-API/DeleteNSInstanceWorkflow.robot
index 6d3fba20fb1a575ffa3bd036f9d0ce32a7274631..1d913ed0ca3dbeb434fc5ed29d8e0f2a363390c5 100644
--- a/SOL005/NSLifecycleManagement-API/DeleteNSInstanceWorkflow.robot
+++ b/SOL005/NSLifecycleManagement-API/DeleteNSInstanceWorkflow.robot
@@ -15,7 +15,7 @@ NS Instance Deletion
... Test title: NS Instance Deletion
... Test objective: The objective is to test the workflow for Deleting a NS instance
... Pre-conditions: the resource is in NOT_INSTANTIATED state
- ... Reference: Clause 6.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: NS Instance resource is deleted
diff --git a/SOL005/NSLifecycleManagement-API/FailOperationTask.robot b/SOL005/NSLifecycleManagement-API/FailOperationTask.robot
index f4ee17dfc452acafc49d518949af9e38012c3dbc..ec528bf6e2ff80db742d783f34a73320874c0954 100644
--- a/SOL005/NSLifecycleManagement-API/FailOperationTask.robot
+++ b/SOL005/NSLifecycleManagement-API/FailOperationTask.robot
@@ -13,7 +13,7 @@ POST Fail operation task
... Test title: POST Fail operation task
... Test objective: The objective is to test that POST method trigger a state change to "finally failed" on the NS LCM operation
... Pre-conditions: NS instance status equal to FAILED_TEMP
- ... Reference: Clause 6.4.14.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.14.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -26,7 +26,7 @@ POST Fail operation task Not Found
... Test title: POST Fail operation task Not Found
... Test objective: The objective is to test that POST method fail if the NS LCM resource is not found
... Pre-conditions: none
- ... Reference: Clause 6.4.14.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.14.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -39,7 +39,7 @@ POST Fail operation task Conflict
... Test title: POST Fail operation task Conflict
... Test objective: The objective is to test that POST method fail in case of status conflict on the NS LCM operation (i.e NS instance status not equal to FAILED_TEMP)
... Pre-conditions: NS instance status not equal to FAILED_TEMP
- ... Reference: Clause 6.4.14.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.14.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -52,7 +52,7 @@ GET Fail operation task - Method not implemented
... Test title: GET Fail operation task - Method not implemented
... Test objective: The objective is to test that GET method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.14.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.14.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -64,7 +64,7 @@ PUT Fail operation task - Method not implemented
... Test title: PUT Fail operation task - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.14.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.14.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -76,7 +76,7 @@ PATCH Fail operation task - Method not implemented
... Test title: PATCH Fail operation task - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.14.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.14.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -88,7 +88,7 @@ DELETE Fail operation task - Method not implemented
... Test title: DELETE Fail operation task - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.14.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.14.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/NSLifecycleManagement-API/HealNSTask.robot b/SOL005/NSLifecycleManagement-API/HealNSTask.robot
index 4991bbb487eb04e23e7ad6b31ea00073e5d1bdb0..cc688b4e7a88f0ecacef01dee68ab50bb5b8a364 100644
--- a/SOL005/NSLifecycleManagement-API/HealNSTask.robot
+++ b/SOL005/NSLifecycleManagement-API/HealNSTask.robot
@@ -13,7 +13,7 @@ POST Heal a NSInstance
... Test title: POST Heal a NSInstance
... Test objective: The objective is to test that POST method trigger a Heal NS instance
... Pre-conditions: NS Instance is in INSTANTIATED state.
- ... Reference: Clause 6.4.7.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.7.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: NS instance is still in INSTANTIATED state.
@@ -26,7 +26,7 @@ POST Heal a NSInstance - Conflict (Not Instantited)
... Test title: POST Heal a NSInstance - Conflict (Not Instantited)
... Test objective: The objective is to test that POST method fail if NS instance is in NOT_INSTANTIATE state
... Pre-conditions: NS Instance is in NOT_INSTANTIATED state
- ... Reference: Clause 6.4.7.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.7.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: NS Instance is still in NOT_INSTANTIATED state
@@ -39,7 +39,7 @@ GET Heal NSInstance- Method not implemented
... Test title: GET Heal NSInstance- Method not implemented
... Test objective: The objective is to test that GET method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.7.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.7.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -51,7 +51,7 @@ PUT Heal NSInstance - Method not implemented
... Test title: PUT Heal NSInstance - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.7.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.7.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -63,7 +63,7 @@ PATCH Heal NSInstance - Method not implemented
... Test title: PATCH Heal NSInstance - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.7.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.7.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -75,7 +75,7 @@ DELETE Heal NSInstance - Method not implemented
... Test title: DELETE Heal NSInstance - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.7.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.7.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/NSLifecycleManagement-API/HealNSTaskWorkflow.robot b/SOL005/NSLifecycleManagement-API/HealNSTaskWorkflow.robot
index bd55a78d50685954d238339e4a66b419df3149c6..526058be709f7945b9550c73d22748fa8b4f095b 100644
--- a/SOL005/NSLifecycleManagement-API/HealNSTaskWorkflow.robot
+++ b/SOL005/NSLifecycleManagement-API/HealNSTaskWorkflow.robot
@@ -14,7 +14,7 @@ Heal Flow of NS lifecycle management operations
... Test title: Heal Flow of NS lifecycle management operations
... Test objective: The objective is to test the workflow for Healing a NS instance
... Pre-conditions: the resource is in INSTANTIATED state
- ... Reference: Clause 6.4.7 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.7 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: NS Instance still in INSTANTIATED state
diff --git a/SOL005/NSLifecycleManagement-API/IndividualNSInstance.robot b/SOL005/NSLifecycleManagement-API/IndividualNSInstance.robot
index c6953f83b0712eaf252801dc9c5ded893aeb34dc..63cb732197408a2971c607a877096ced43c57afd 100644
--- a/SOL005/NSLifecycleManagement-API/IndividualNSInstance.robot
+++ b/SOL005/NSLifecycleManagement-API/IndividualNSInstance.robot
@@ -13,7 +13,7 @@ POST Individual NSInstance - Method not implemented
... Test title: POST Individual NSInstance - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.3.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.3.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -25,7 +25,7 @@ GET Information about an individual NS Instance
... Test title: GET Information about an individual NS Instance
... Test objective: The objective is to test that GET method returns an individual NS instance
... Pre-conditions: none
- ... Reference: Clause 6.4.3.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.3.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -40,7 +40,7 @@ PUT Individual NSInstance - Method not implemented
... Test title: PUT Individual NSInstance - Method not implemented
... Test objective: TThe objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.3.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.3.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -52,7 +52,7 @@ PATCH Individual NSInstance - Method not implemented
... Test title: PATCH Individual NSInstance - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -64,7 +64,7 @@ DELETE Individual NSInstance
... Test title: DELETE Individual NSInstance
... Test objective: The objective is to test that DELETE method delete a not INSTANTIATED NS instance
... Pre-conditions: NS instance is not INSTANTIATED .
- ... Reference: Clause 6.4.3.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.3.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: Check Postcondition NS Instance is deleted
@@ -77,7 +77,7 @@ DELETE Individual NSInstance Conflict
... Test title: DELETE Individual NSInstance Conflict
... Test objective: The objective is to test that DELETE method cannot delete an INSTANTIATED NS instance
... Pre-conditions: one instance of a NS in INSTANTIATED state
- ... Reference: Clause 6.4.3.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.3.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: Check Postcondition NS Instance is not deleted
diff --git a/SOL005/NSLifecycleManagement-API/IndividualNSLCMOccurences.robot b/SOL005/NSLifecycleManagement-API/IndividualNSLCMOccurences.robot
index 87aa0d02fe7cac46b9969bfdac9f25ad9a1adc1b..5320d5d49b13eb7ca1846b4d3c4f9144f7a43fcc 100644
--- a/SOL005/NSLifecycleManagement-API/IndividualNSLCMOccurences.robot
+++ b/SOL005/NSLifecycleManagement-API/IndividualNSLCMOccurences.robot
@@ -12,7 +12,7 @@ Post Individual NS LCM occurrences - Method not implemented
... Test title: Post Individual NS LCM occurrences - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -24,7 +24,7 @@ Get status information about Individual NS LCM occurrences
... Test title: Get status information about Individual NS LCM occurrences
... Test objective: The objective is to test that GET method returns the LCM occurrence of the NS
... Pre-conditions: none
- ... Reference: Clause 6.4.10.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.10.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -38,7 +38,7 @@ PUT status information about Individual NS LCM occurrences - Method not implemen
... Test title: PUT status information about Individual NS LCM occurrences - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.10.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.10.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -50,7 +50,7 @@ PATCH status information about Individual NS LCM occurrences
... Test title: PATCH status information about Individual NS LCM occurrences
... Test objective: The objective is to test that PATCH method modify an existing Individual NS LCM occurrence
... Pre-conditions: An Individual NS LCM occurrence represents a scheduled operation not yet started
- ... Reference: Clause 6.4.10.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.10.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -62,7 +62,7 @@ PATCH status information about Individual NS LCM occurrences - scheduled operati
... Test title: PATCH status information about Individual NS LCM occurrences
... Test objective: The objective is to test that PATCH method modify an existing Individual NS LCM occurrence
... Pre-conditions: An Individual NS LCM occurrence represents a scheduled operation already started
- ... Reference: Clause 6.4.10.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.10.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -70,12 +70,38 @@ PATCH status information about Individual NS LCM occurrences - scheduled operati
Check HTTP Response Status Code Is 409
Check HTTP Response Body Json Schema Is ProblemDetails
+PATCH status information about Individual NS LCM occurrences - Precondition failed
+ [Documentation] Test ID: 5.3.2.9.4c
+ ... Test title: PATCH status information about Individual NS LCM occurrences - Precondition failed
+ ... Test objective: The objective is to test that PATCH method that modifies an existing Individual NS LCM occurrence fails if the resource was modified by another entity
+ ... Pre-conditions: An Individual NS LCM occurrence represents a scheduled operation not yet started
+ ... Reference: Clause 6.4.10.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
+ ... Config ID: Config_prod_NFVO
+ ... Applicability: The resource was modified by another entity
+ ... Post-Conditions: none
+ PATCH Individual NS LCM OP Occurrence - ETag mismatch
+ Check HTTP Response Status Code Is 412
+ Check HTTP Response Body Json Schema Is ProblemDetails
+
+PATCH status information about Individual NS LCM occurrences - Precondition failed HTTP Conditional Request Not Supported
+ [Documentation] Test ID: 5.3.2.9.4d
+ ... Test title: PATCH status information about Individual NS LCM occurrences - Precondition failed HTTP Conditional Request Not Supported
+ ... Test objective: The objective is to test that PATCH method that modifies an existing Individual NS LCM occurrence fails if the API Producer does not support "Last-Modified" and "ETag" HTTP Headers
+ ... Pre-conditions: An Individual NS LCM occurrence represents a scheduled operation not yet started
+ ... Reference: Clause 6.4.10.3.4, 4.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
+ ... Config ID: Config_prod_NFVO
+ ... Applicability: API Producer does not support "Last-Modified" and "ETag" HTTP Headers
+ ... Post-Conditions: none
+ PATCH Individual NS LCM OP Occurrence - HTTP Conditional Request not supported
+ Check HTTP Response Status Code Is 412
+ Check HTTP Response Body Json Schema Is ProblemDetails
+
DELETE status information about Individual NS LCM occurrences - Method not implemented
[Documentation] Test ID: 5.3.2.9.5
... Test title: DELETE status information about Individual NS LCM occurrences - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.10.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.10.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/NSLifecycleManagement-API/IndividualSubscription.robot b/SOL005/NSLifecycleManagement-API/IndividualSubscription.robot
index f090495de1c3937d2869f97f86326edc8d9e890a..745d38f14bb5fe85161f2e07771e46a61e5ccef0 100644
--- a/SOL005/NSLifecycleManagement-API/IndividualSubscription.robot
+++ b/SOL005/NSLifecycleManagement-API/IndividualSubscription.robot
@@ -14,7 +14,7 @@ POST Individual Subscription - Method not implemented
... Test title: POST Individual Subscription - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.17.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.17.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -26,7 +26,7 @@ GET Information about an individual subscription
... Test title: GET Information about an individual subscription
... Test objective: The objective is to test the retrieval of NS lifecycle management subscription and perform a JSON schema validation of the returned subscription data structure
... Pre-conditions: none
- ... Reference: Clause 6.4.17.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.17.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -39,7 +39,7 @@ PUT an individual subscription - Method not implemented
... Test title: PUT an individual subscription - Method not implemented
... Test objective: TThe objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.17.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.17.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -51,7 +51,7 @@ PATCH an individual subscription - Method not implemented
... Test title: PATCH an individual subscription - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.17.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.17.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -63,7 +63,7 @@ DELETE an individual subscription
... Test title: DELETE an individual subscription
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: At least one lifecycle management subscription is available in the NFVO
- ... Reference: Clause 6.4.17.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.17.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: The NS lifecycle management subscription is not available anymore on NFVO
diff --git a/SOL005/NSLifecycleManagement-API/IndividualVNFSnapshot.robot b/SOL005/NSLifecycleManagement-API/IndividualVNFSnapshot.robot
index f118fb6eaa0a960ddb75641915a8de568aa258db..72dbaba07f5f425203a5774f0fc3280751e975a9 100644
--- a/SOL005/NSLifecycleManagement-API/IndividualVNFSnapshot.robot
+++ b/SOL005/NSLifecycleManagement-API/IndividualVNFSnapshot.robot
@@ -3,11 +3,11 @@ Resource NSLCMOperationKeywords.robot
*** Test Cases ***
POST Individual VNF Snapshot - Method not implemented
- [Documentation] Test ID: 5.3.2.27.1
+ [Documentation] Test ID: 5.3.2.28.1
... Test title: POST Individual VNF Snapshot - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.20.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.20.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -15,11 +15,11 @@ POST Individual VNF Snapshot - Method not implemented
Check HTTP Response Status Code Is 405
GET Information about an individual VNF Snapshot - SUCCESSFUL
- [Documentation] Test ID: 5.3.2.27.2
+ [Documentation] Test ID: 5.3.2.28.2
... Test title: GET Information about an individual VNF Snapshot - SUCCESSFUL
... Test objective: The objective is to GET information about an individual VNF Snapshot
... Pre-conditions: none
- ... Reference: Clause 6.4.20.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.20.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -28,11 +28,11 @@ GET Information about an individual VNF Snapshot - SUCCESSFUL
Check HTTP Response Body Json Schema Is VnfSnapshotInfo
GET Information about an individual VNF Snapshot - NOT FOUND
- [Documentation] Test ID: 5.3.2.27.3
+ [Documentation] Test ID: 5.3.2.28.3
... Test title: GET Information about an individual VNF Snapshot - NOT FOUND
... Test objective: The objective is to test that the retrieval of individual VNF Snapshot fails when using an invalid resource identifier.
... Pre-conditions: none
- ... Reference: Clause 6.4.20.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.20.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -41,11 +41,11 @@ GET Information about an individual VNF Snapshot - NOT FOUND
Check HTTP Response Body Json Schema Is ProblemDetails
PUT Individual VNF Snapshot - Method not implemented
- [Documentation] Test ID: 5.3.2.27.4
+ [Documentation] Test ID: 5.3.2.28.4
... Test title: PUT Individual VNF Snapshot - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.20.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.20.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -53,11 +53,11 @@ PUT Individual VNF Snapshot - Method not implemented
Check HTTP Response Status Code Is 405
PATCH Individual VNF Snapshot - Method not implemented
- [Documentation] Test ID: 5.3.2.27.5
+ [Documentation] Test ID: 5.3.2.28.5
... Test title: PATCH Individual VNF Snapshot - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.20.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.20.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: VNF Snapshot not modified
@@ -65,11 +65,11 @@ PATCH Individual VNF Snapshot - Method not implemented
Check HTTP Response Status Code Is 405
DELETE Individual VNF Snapshot
- [Documentation] Test ID: 5.3.2.27.6
+ [Documentation] Test ID: 5.3.2.28.6
... Test title: DELETE Individual VNF Snapshot
... Test objective: The objective is to delete a VNF Snapshot
... Pre-conditions: none
- ... Reference: Clause 6.4.20.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.20.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: VNF Snapshot resource is deleted.
@@ -78,11 +78,11 @@ DELETE Individual VNF Snapshot
Check Postcondition VNF Snapshot Resource Is Deleted
DELETE Individual VNF Snapshot - Conflict
- [Documentation] Test ID: 5.3.2.27.7
+ [Documentation] Test ID: 5.3.2.28.7
... Test title: DELETE Individual VNF Snapshot Conflict
... Test objective: The objective is to verify that The operation cannot be executed currently, due to a conflict with the state of the VNF Snapshot resource.
... Pre-conditions: none
- ... Reference: Clause 6.4.20.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.20.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: VNF snapshot is in use by some operation such as reverting a VNF instance to a VNF snapshot or creating a VNF snapshot package.
... Post-Conditions: VNF Snapshot resource is not deleted.
diff --git a/SOL005/NSLifecycleManagement-API/InstantiateNSTask.robot b/SOL005/NSLifecycleManagement-API/InstantiateNSTask.robot
index 322db1cf345de3c32e0f11d2b21355f112aa0ffc..90b29e0fd2b1dbecf6ab501956e6ba859913c880 100644
--- a/SOL005/NSLifecycleManagement-API/InstantiateNSTask.robot
+++ b/SOL005/NSLifecycleManagement-API/InstantiateNSTask.robot
@@ -13,7 +13,7 @@ POST Instantiate a nsInstance
... Test title: POST Instantiate a nsInstance
... Test objective: The objective is to test that POST method instantiate a new NS instance
... Pre-conditions: An NS instance created and it is in NOT_INSTANTIATED state
- ... Reference: Clause 6.4.4.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.4.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -27,7 +27,7 @@ POST Instantiate a nsInstance with feasibility check only
... Test title: POST Instantiate a nsInstance with feasibility check
... Test objective: The objective is to test that POST method instantiate a new NS instance with feasibility check only
... Pre-conditions: An NS instance created and it is in NOT_INSTANTIATED state
- ... Reference: Clause 6.4.4.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.4.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -41,7 +41,7 @@ POST Instantiate a nsInstance Conflict
... Test title: POST Instantiate a nsInstance Conflict
... Test objective: The objective is to test that the operation cannot be performed due to a conflict with the state of resource (i.e. the resource is in INSTANTIATED state)
... Pre-conditions: resource is in INSTANTIATED state
- ... Reference: Clause 6.4.4.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.4.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: The NS instance is not instantiated on the NFVO
@@ -54,7 +54,7 @@ GET Instantiate NSInstance - Method not implemented
... Test title: GET Instantiate NSInstance - Method not implemented
... Test objective: The objective is to test that the operation cannot be performed due because method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none.
@@ -66,7 +66,7 @@ PUT Instantiate NSInstance - Method not implemented
... Test title: PUT Instantiate NSInstance - Method not implemented
... Test objective: The objective is to test that the operation cannot be performed due because method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.4.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.4.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none.
@@ -78,7 +78,7 @@ PATCH Instantiate NSInstance - Method not implemented
... Test title: PATCH Instantiate NSInstance - Method not implemented
... Test objective: The objective is to test that the operation cannot be performed due because method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.4.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.4.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none.
@@ -90,7 +90,7 @@ DELETE Instantiate NSInstance - Method not implemented
... Test title: DELETE Instantiate NSInstance - Method not implemented
... Test objective: The objective is to test that the operation cannot be performed due because method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.4.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.4.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none.
diff --git a/SOL005/NSLifecycleManagement-API/InstantiateNSTaskWorkflow.robot b/SOL005/NSLifecycleManagement-API/InstantiateNSTaskWorkflow.robot
index 2074371c09633977e991d5af7d175abea958aae6..341ad1bcc8ce20ef737135f48f02405f0a9b6fe5 100644
--- a/SOL005/NSLifecycleManagement-API/InstantiateNSTaskWorkflow.robot
+++ b/SOL005/NSLifecycleManagement-API/InstantiateNSTaskWorkflow.robot
@@ -14,7 +14,7 @@ Instantiate Flow of NS lifecycle management operations
... Test title: Instantiate Flow of NS lifecycle management operations
... Test objective: The objective is to test the workflow for Instantiate a NS instance
... Pre-conditions: the resource is in NOT_INSTANTIATED state
- ... Reference: Clause 6.4.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: the resource is in INSTANTIATED state
diff --git a/SOL005/NSLifecycleManagement-API/NSInstances.robot b/SOL005/NSLifecycleManagement-API/NSInstances.robot
index 8536aa60fb9b3d11debd91f4ead1961a9615341d..57e37608533ba6ea2c65aea29f5be34bf1068c40 100644
--- a/SOL005/NSLifecycleManagement-API/NSInstances.robot
+++ b/SOL005/NSLifecycleManagement-API/NSInstances.robot
@@ -12,7 +12,7 @@ POST Create a new NsInstance
... Test title: POST Create a new NsInstance
... Test objective: The objective is to test the creation of a new Ns Instances and perform a JSON schema validation of the collected instance data structure
... Pre-conditions: none.
- ... Reference: Clause 6.4.2.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.2.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none.
... Post-Conditions: A Ns instance is instantiated.
@@ -27,7 +27,7 @@ GET information about multiple NS instances
... Test title: GET information about multiple NS instances
... Test objective: The objective is to test the retrieval of all the available NS Instances and perform a JSON schema and content validation of the collected instance data structure
... Pre-conditions: An existing Ns instance.
- ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none.
... Post-Conditions: none.
@@ -39,8 +39,8 @@ GET information about multiple NS instances Bad Request Invalid attribute-based
[Documentation] Test ID: 5.3.2.1.3
... Test title: GET information about multiple NS instances Bad Request Invalid attribute-based filtering parameters
... Test objective: The objective is to test the retrieval of all the available NS Instances using attribute-based filter and perform a JSON schema and content validation of the collected instance data structure
- ... Pre-conditions: A Ns instance is instantiated, a bad filter parameter (filter parameters are listed in Table 6.4.2.3.2-1 - ETSI GS NFV-SOL 005 [3] v4.3.1).
- ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Pre-conditions: A Ns instance is instantiated, a bad filter parameter (filter parameters are listed in Table 6.4.2.3.2-1 - ETSI GS NFV-SOL 005 [3] v4.4.1).
+ ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none.
... Post-Conditions: none.
@@ -52,8 +52,8 @@ GET information about multiple NS instances Bad Request Invalid attribute select
[Documentation] Test ID: 5.3.2.1.4
... Test title: GET information about multiple NS instances Bad Request Invalid attribute selector
... Test objective: The objective is to test the retrieval of all the available NS Instances using attribute-based filter and perform a JSON schema and content validation of the collected instance data structure
- ... Pre-conditions: A Ns instance is instantiated, a bad attribute selector (attribute selectors are listed in Table 6.4.2.3.2-1 - ETSI GS NFV-SOL 005 [3] v4.3.1).
- ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Pre-conditions: A Ns instance is instantiated, a bad attribute selector (attribute selectors are listed in Table 6.4.2.3.2-1 - ETSI GS NFV-SOL 005 [3] v4.4.1).
+ ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none.
... Post-Conditions: none.
@@ -66,7 +66,7 @@ GET NSInstances with "all_fields" attribute selector
... Test title: GET NSInstances with "all_fields" attribute selector
... Test objective: The objective is to retrieve the list of active NSInstances with attribute selector
... Pre-conditions: none
- ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -79,7 +79,7 @@ GET NSInstances with "exclude_default" attribute selector
... Test title: GET NSInstances with "exclude_default" attribute selector
... Test objective: The objective is to retrieve the list of active NSInstances with attribute selector
... Pre-conditions: none
- ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -92,7 +92,7 @@ GET NSInstances with "fields" attribute selector
... Test title: GET NSInstances with "fields" attribute selector
... Test objective: The objective is to retrieve the list of active NSInstances with attribute selector
... Pre-conditions: none
- ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -105,7 +105,7 @@ GET NSInstances with "exclude_fields" attribute selector
... Test title: GET NSInstances with "exclude_fields" attribute selector
... Test objective: The objective is to retrieve the list of active NSInstances with attribute selector
... Pre-conditions: none
- ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -118,7 +118,7 @@ PUT NSInstances - Method not implemented
... Test title: PUT Individual NS instance - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.2.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.2.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -130,7 +130,7 @@ PATCH NSInstances - Method not implemented
... Test title: PATCH NSInstances - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.2.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.2.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -142,7 +142,7 @@ DELETE NSInstances - Method not implemented
... Test title: DELETE NSInstances - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.2.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.2.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -154,7 +154,7 @@ GET information about multiple NS instances as Paged Response
... Test title: GET information about multiple NS instances as Paged Response
... Test objective: The objective is to test the retrieval of all the available NS Instances as a Paged Response.
... Pre-conditions: An existing Ns instance.
- ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none.
... Post-Conditions: none.
@@ -166,8 +166,8 @@ GET information about multiple NS instances - Bad Request Response too Big
[Documentation] Test ID: 5.3.2.1.13
... Test title: GET information about multiple NS instances - Bad Request Response too Big
... Test objective: The objective is to test the retrieval of all the available NS Instances fails because reponse is too big, and perform a JSON schema and content validation of the collected instance data structure
- ... Pre-conditions: A Ns instance is instantiated, a bad attribute selector (attribute selectors are listed in Table 6.4.2.3.2-1 - ETSI GS NFV-SOL 005 [3] v4.3.1).
- ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Pre-conditions: A Ns instance is instantiated, a bad attribute selector (attribute selectors are listed in Table 6.4.2.3.2-1 - ETSI GS NFV-SOL 005 [3] v4.4.1).
+ ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none.
... Post-Conditions: none.
@@ -180,7 +180,7 @@ GET NSInstances with "fields" and "exclude_default" attribute selector
... Test title: GET NSInstances with "fields" and "exclude_default" attribute selector
... Test objective: The objective is to retrieve the list of active NSInstances with attribute selector list and exclude_default
... Pre-conditions: none
- ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -193,7 +193,7 @@ GET information about multiple NS instances - Filter
... Test title: GET information about multiple NS instances - Filter
... Test objective: The objective is to test the retrieval of NS Instances using filter and perform a JSON schema and content validation of the collected instance data structure
... Pre-conditions: An existing Ns instance.
- ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none.
... Post-Conditions: none.
diff --git a/SOL005/NSLifecycleManagement-API/NSLCMOccurences.robot b/SOL005/NSLifecycleManagement-API/NSLCMOccurences.robot
index 74e615b64d22445ec5a8daa7f87e4241ecba2ebc..3cec36ed8c8f10e7f68c3f67b8e3eb07e69b81f1 100644
--- a/SOL005/NSLifecycleManagement-API/NSLCMOccurences.robot
+++ b/SOL005/NSLifecycleManagement-API/NSLCMOccurences.robot
@@ -12,7 +12,7 @@ POST NS LCM occurrences - Method not implemented
... Test title: POST NS LCM occurrences - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.9.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.9.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -24,7 +24,7 @@ GET status information about multiple NS LCM occurrences
... Test title: GET status information about multiple NS LCM occurrences
... Test objective: The objective is to test that GET method returns a list of LCM occurrences of the NS
... Pre-conditions: At least one LCM occurrences available in the NFVO
- ... Reference: Clause 6.4.9.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.9.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -37,7 +37,7 @@ GET status information about multiple NS LCM occurrences Bad Request Invalid att
... Test title: GET status information about multiple NS LCM occurrences Bad Request Invalid attribute-based filtering parameters
... Test objective: The objective is to test that GET method fail because of wrong query parameter
... Pre-conditions: At least one LCM occurrences available in the NFVO, Invalid filter parameter
- ... Reference: Clause 6.4.9.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.9.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -50,7 +50,7 @@ GET status information about multiple NS LCM occurrences Bad Request Invalid att
... Test title: GET status information about multiple NS LCM occurrences Bad Request Invalid attribute selector
... Test objective: The objective is to test that GET method fail because of wrong attributes selector
... Pre-conditions: At least one LCM occurrences available in the NFVO, Invalid attribute selector
- ... Reference: Clause 6.4.9.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.9.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -63,7 +63,7 @@ GET status information about multiple NS LCM occurrences with "all_fields"
... Test title: GET status information about multiple NS LCM occurrences with "all_fields"
... Test objective: The objective is to test that GET method returns a list of LCM occurrences of the NS
... Pre-conditions: At least one LCM occurrences available in the NFVO
- ... Reference: Clause 6.4.9.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.9.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -76,7 +76,7 @@ GET status information about multiple NS LCM occurrences with "exclude_default"
... Test title: GET status information about multiple NS LCM occurrences with "exclude_default"
... Test objective: The objective is to test that GET method returns a list of LCM occurrences of the NS
... Pre-conditions: At least one LCM occurrences available in the NFVO
- ... Reference: Clause 6.4.9.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.9.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -89,7 +89,7 @@ GET status information about multiple NS LCM occurrences with "fields"
... Test title: GET status information about multiple NS LCM occurrences with "fields"
... Test objective: The objective is to test that GET method returns a list of LCM occurrences of the NS
... Pre-conditions: At least one LCM occurrences available in the NFVO
- ... Reference: Clause 6.4.9.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.9.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -102,7 +102,7 @@ GET status information about multiple NS LCM occurrences with "exclude_fields"
... Test title: GET status information about multiple NS LCM occurrences with "exclude_fields"
... Test objective: The objective is to test that GET method returns a list of LCM occurrences of the NS
... Pre-conditions: At least one LCM occurrences available in the NFVO
- ... Reference: Clause 6.4.9.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.9.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -115,7 +115,7 @@ PUT status information about multiple NS LCM occurrences - Method not implemente
... Test title: PUT status information about multiple NS LCM occurrences - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.9.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.9.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -127,7 +127,7 @@ PATCH status information about multiple NS LCM occurrences - Method not implemen
... Test title: PATCH status information about multiple NS LCM occurrences - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.9.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.9.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -139,7 +139,7 @@ DELETE status information about multiple NS LCM occurrences - Method not impleme
... Test title: DELETE status information about multiple NS LCM occurrences - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.9.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.9.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -151,7 +151,7 @@ GET status information about multiple NS LCM occurrences as Paged Response
... Test title: GET status information about multiple NS LCM occurrences as Paged Reponse
... Test objective: The objective is to test that GET method returns a list of LCM occurrences of the NS as paged response.
... Pre-conditions: At least one LCM occurrences available in the NFVO
- ... Reference: Clause 6.4.9.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.9.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -164,7 +164,7 @@ GET status information about multiple NS LCM occurrences - Bad Request Response
... Test title: GET status information about multiple NS LCM occurrences - Bad Request Response too Big
... Test objective: The objective is to test that GET method fail because response is too big, and perform the JSON schema validation of the failed operation HTTP response.
... Pre-conditions: At least one LCM occurrences available in the NFVO, Invalid filter parameter
- ... Reference: Clause 6.4.9.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.9.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -177,7 +177,7 @@ GET status information about multiple NS LCM occurrences with "fields" and "excl
... Test title: GET status information about multiple NS LCM occurrences with "fields" and "exclude_default"
... Test objective: The objective is to test that GET method returns a list of LCM occurrences of the NS
... Pre-conditions: At least one LCM occurrences available in the NFVO
- ... Reference: Clause 6.4.9.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.9.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -190,7 +190,7 @@ GET status information about multiple NS LCM occurrences - Filter
... Test title: GET status information about multiple NS LCM occurrences - Filter
... Test objective: The objective is to test that GET method returns a list of LCM occurrences of the NS using filtering-based query parameters
... Pre-conditions: At least one LCM occurrences available in the NFVO
- ... Reference: Clause 6.4.9.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.9.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/NSLifecycleManagement-API/NSLCMOperationKeywords.robot b/SOL005/NSLifecycleManagement-API/NSLCMOperationKeywords.robot
index fd6825d440af72962360646b4495f653cc3401e6..bc90236bd2d92e20216d8988321b66c5ef2a1861 100644
--- a/SOL005/NSLifecycleManagement-API/NSLCMOperationKeywords.robot
+++ b/SOL005/NSLifecycleManagement-API/NSLCMOperationKeywords.robot
@@ -940,6 +940,30 @@ PATCH Individual NS LCM OP Occurrence of Already Started Scheduled Operation
${outputResponse}= Output response
Set Global Variable ${response} ${outputResponse}
+PATCH Individual NS LCM OP Occurrence - ETag mismatch
+ log Trying to perform a PATCH.
+ Set Headers {"Accept":"${ACCEPT}"}
+ Set Headers {"Content-Type": "${CONTENT_TYPE_PATCH}"}
+ Set Headers {"If-Match": "${invalid_etag}"}
+ Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"${AUTHORIZATION_HEADER}":"${AUTHORIZATION_TOKEN}"}
+ ${body}= Get File jsons/NsLcmInfoModificationRequest.json
+ ${body}= Format String ${body} scheduledTime=${schedule_for_new_operation_start}
+ Patch ${apiRoot}/${apiName}/${apiMajorVersion}/ns_lcm_op_occs/${nsLcmOpOccId_scheduledOp_notStarted} ${body}
+ ${outputResponse}= Output response
+ Set Global Variable ${response} ${outputResponse}
+
+PATCH Individual NS LCM OP Occurrence - HTTP Conditional Request not supported
+ Pass Execution If ${PRODUCER_SUPPORT_COND_REQ} == 1 NVFO allows conditional requests, skipping test
+ log Trying to perform a PATCH.
+ Set Headers {"Accept":"${ACCEPT}"}
+ Set Headers {"Content-Type": "${CONTENT_TYPE_PATCH}"}
+ Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"${AUTHORIZATION_HEADER}":"${AUTHORIZATION_TOKEN}"}
+ ${body}= Get File jsons/NsLcmInfoModificationRequest.json
+ ${body}= Format String ${body} scheduledTime=${schedule_for_new_operation_start}
+ Patch ${apiRoot}/${apiName}/${apiMajorVersion}/ns_lcm_op_occs/${nsLcmOpOccId_scheduledOp_notStarted} ${body}
+ ${outputResponse}= Output response
+ Set Global Variable ${response} ${outputResponse}
+
DELETE Individual NS LCM OP Occurrence
log Trying to perform a DELETE. This method should not be implemented
Set Headers {"Accept":"${ACCEPT}"}
diff --git a/SOL005/NSLifecycleManagement-API/NotificationEndpoint.robot b/SOL005/NSLifecycleManagement-API/NotificationEndpoint.robot
index 0c0e1daabbb14082fee45602a2d720ac1ba1b631..617d81b7085e0737aec1d03d4e7d7a8b46a3be6f 100644
--- a/SOL005/NSLifecycleManagement-API/NotificationEndpoint.robot
+++ b/SOL005/NSLifecycleManagement-API/NotificationEndpoint.robot
@@ -15,7 +15,7 @@ Ns Lcm Operation Occurrence Notification
... Test title: Ns Lcm Operation Occurrence Notification
... Test objective: The objective is to test that Ns Lcm Operation Occurrence Notification is delivered with success to the notification consumer.
... Pre-conditions: A subscription for NS LCM Operation Occurrence notifications is available in the NFVO.
- ... Reference: Clause 6.4.18.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.18.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
@@ -27,7 +27,7 @@ Ns Identifier Creation Notification
... Test title: Ns Identifier Creation Notification
... Test objective: The objective is to test that Ns Identifier Creation Notification is delivered with success to the notification consumer.
... Pre-conditions: A subscription for Ns Identifier Creation notification is available in the NFVO.
- ... Reference: Clause 6.4.18.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.18.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
@@ -39,7 +39,7 @@ Ns Identifier Deletion Notification
... Test title: Ns Identifier Deletion Notification
... Test objective: The objective is to test that Ns Identifier Deletion Notification is delivered with success to the notification consumer.
... Pre-conditions: A subscription for Ns Identifier Deletion notification is available in the NFVO.
- ... Reference: Clause 6.4.18.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.18.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
@@ -51,7 +51,7 @@ Ns Change Notification
... Test title: Ns Change Notification
... Test objective: The objective is to test that Ns Change Notification is delivered with success to the notification consumer.
... Pre-conditions: A subscription for Ns Change notification is available in the NFVO.
- ... Reference: Clause 6.4.18.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.18.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
@@ -63,7 +63,7 @@ Ns LCM Capacity Shortage Notification
... Test title: Ns LCM Capacity Shortage Notification
... Test objective: The objective is to test that Ns LCM Capacity Shortage Notification is delivered with success to the notification consumer.
... Pre-conditions: A subscription for Ns LCM Capacity Shortage notification is available in the NFVO.
- ... Reference: Clause 6.4.18.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.18.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/NSLifecycleManagement-API/Notifications.robot b/SOL005/NSLifecycleManagement-API/Notifications.robot
index 347b4a41047a4cb943ad5bf58dc9c0dd37a1ead9..d16a01eabb64a4002fe38b5961bb31a691966ff7 100644
--- a/SOL005/NSLifecycleManagement-API/Notifications.robot
+++ b/SOL005/NSLifecycleManagement-API/Notifications.robot
@@ -13,7 +13,7 @@ NS LCM Operation Occurrence Start Notification
... Test title: NS LCM Operation Occurrence Start Notification
... Test objective: The objective is to test the dispatch of NS LCM Operation Occurrence Start Notification when a new NS LCM operation is started in the NFVO, and perform a JSON schema and content validation of the delivered notification. The action that triggers the notification under test is an explicit test step, but it is not performed by the test system.
... Pre-conditions: A subscription for NS LCM Operation Occurrence notifications is available in the NFVO.
- ... Reference: Clause 6.4.18.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.18.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -27,7 +27,7 @@ NS LCM Operation Occurrence Result Notification
... Test title: NS LCM Operation Occurrence Result Notification
... Test objective: The objective is to test the dispatch of NS LCM Operation Occurrence Result Notification when a NS LCM operation is completed in the NFVO, and perform a JSON schema and content validation of the delivered notification. The action that triggers the notification under test is an explicit test step, but it is not performed by the test system.
... Pre-conditions: An NS LCM operation is in progress, and a subscription for NS LCM Operation Occurrence notifications is available in the NFVO.
- ... Reference: Clause 6.4.18.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.18.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -41,7 +41,7 @@ NS Identifier Creation Notification
... Test title: NS Identifier Creation Notification
... Test objective: The objective is to test the dispatch of NS Identifier Creation Notification when a new NS instance resource is created in the NFVO, and perform a JSON schema and content validation of the delivered notification. The action that triggers the notification under test is an explicit test step, but it is not performed by the test system.
... Pre-conditions: A subscription for NS identifier creation notifications is available in the NFVO.
- ... Reference: Clause 6.4.18.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.18.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -54,7 +54,7 @@ NS Identifier Deletion Notification
... Test title: NS Identifier Deletion Notification
... Test objective: The objective is to test the dispatch of NS Identifier Deletion Notification when a NS instance resource is deleted in the NFVO, and perform a JSON schema and content validation of the delivered notification.The action that triggers the notification under test is an explicit test step, but it is not performed by the test system.
... Pre-conditions: A NS instance resource is created, and a subscription for NS identifier deletion notifications is available in the NFVO.
- ... Reference: Clause 6.4.18.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.18.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -67,7 +67,7 @@ NS Change Notification
... Test title: NS Change Notification
... Test objective: The objective is to test the dispatch of NS Change Notification when a NS instance component is affected by an LCM operation occurrence, and perform a JSON schema and content validation of the delivered notification.The action that triggers the notification under test is an explicit test step, but it is not performed by the test system.
... Pre-conditions: A NS instance resource is created, and a subscription for NS change notifications is available in the NFVO.
- ... Reference: Clause 6.4.18.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.18.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -80,7 +80,7 @@ NS LCM Capacity Shortage Notification
... Test title: NS LCM Capacity Shortage Notification
... Test objective: The objective is to test the dispatch of NS LCM Capacity Shortage Notification when a resource shortage occurs during the execution of an NS LCM operation, and perform a JSON schema and content validation of the delivered notification.The action that triggers the notification under test is an explicit test step, but it is not performed by the test system.
... Pre-conditions: A NS instance resource is created, and a subscription for NS LCM Capacity Shortage notifications is available in the NFVO.
- ... Reference: Clause 6.4.18.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.18.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/NSLifecycleManagement-API/RetryOperationTask.robot b/SOL005/NSLifecycleManagement-API/RetryOperationTask.robot
index 7c4184bff336da33c91544a279da0fa362e1fdba..a38f60873d338e20c1dc8f57a76072880b0d6f6a 100644
--- a/SOL005/NSLifecycleManagement-API/RetryOperationTask.robot
+++ b/SOL005/NSLifecycleManagement-API/RetryOperationTask.robot
@@ -13,7 +13,7 @@ Post Retry operation task
... Test title: Post Retry operation task
... Test objective: The objective is to test that POST method trigger a retry of NS lifecycle operation in case of temporary failure
... Pre-conditions: NS instance status equal to FAILED_TEMP
- ... Reference: Clause 6.4.11.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.11.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: NS instance status not equal to FAILED_TEMP
@@ -27,7 +27,7 @@ Post Retry operation task Not Found
... Test title: Post Retry operation task Not Found
... Test objective: The objective is to test that POST method fail in case of NS lifecycle operation not found
... Pre-conditions: none
- ... Reference: Clause 6.4.11.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.11.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -40,7 +40,7 @@ Post Retry operation task Conflict
... Test title: Post Retry operation task Conflict
... Test objective: The objective is to test that POST method fail in case of NS lifecycle operation status conflict (i.e. NS instance status not equal to FAILED_TEMP)
... Pre-conditions: NS instance status not equal to FAILED_TEMP
- ... Reference: Clause 6.4.11.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.11.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -53,7 +53,7 @@ GET Retry operation task - Method not implemented
... Test title: GET Retry operation task - Method not implemented
... Test objective: The objective is to test that GET method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.11.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.11.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -65,7 +65,7 @@ PUT Retry operation task - Method not implemented
... Test title: PUT Retry operation task - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.11.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.11.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -77,7 +77,7 @@ PATCH Retry operation task - Method not implemented
... Test title: PATCH Retry operation task - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.11.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.11.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -89,7 +89,7 @@ DELETE Retry operation task - Method not implemented
... Test title: DELETE Retry operation task - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.11.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.11.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/NSLifecycleManagement-API/RollbackOperationTask.robot b/SOL005/NSLifecycleManagement-API/RollbackOperationTask.robot
index 40bc366e1e84b0c29b8697648ea525b25cb83d86..c65417b059ba1f35df97315f8e037357ad22acfa 100644
--- a/SOL005/NSLifecycleManagement-API/RollbackOperationTask.robot
+++ b/SOL005/NSLifecycleManagement-API/RollbackOperationTask.robot
@@ -13,7 +13,7 @@ POST Rollback operation task
... Test title: POST Rollback operation task
... Test objective: The objective is to test that POST method triggers a rollback on the NS LCM operation
... Pre-conditions: NS instance status equal to FAILED_TEMP
- ... Reference: Clause 6.4.12.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.12.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: NS instance status not equal to FAILED_TEMP
@@ -26,7 +26,7 @@ POST Rollback operation task Not Found
... Test title: POST Rollback operation task Not Found
... Test objective: The objective is to test that POST method fails if NS LCM operation is not found
... Pre-conditions: none
- ... Reference: Clause 6.4.12.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.12.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -39,7 +39,7 @@ POST Rollback operation task Conflict
... Test title: POST Rollback operation task Conflict
... Test objective: The objective is to test that POST method fail in case of NS LCM operation status conflict (i.e. NS instance status not equal to FAILED_TEMP)
... Pre-conditions: NS instance status not equal to FAILED_TEMP
- ... Reference: Clause 6.4.12.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.12.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -52,7 +52,7 @@ GET Rollback operation task - Method not implemented
... Test title: GET Rollback operation task - Method not implemented
... Test objective: The objective is to test that GET method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.12.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.12.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -64,7 +64,7 @@ PUT Rollback operation task - Method not implemented
... Test title: PUT Rollback operation task - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.12.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.12.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -76,7 +76,7 @@ PATCH Rollback operation task - Method not implemented
... Test title: PATCH Rollback operation task - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.12.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.12.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -88,7 +88,7 @@ DELETE Rollback operation task - Method not implemented
... Test title: DELETE Rollback operation task - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.12.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.12.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/NSLifecycleManagement-API/ScaleNSTask.robot b/SOL005/NSLifecycleManagement-API/ScaleNSTask.robot
index 5d32c1898461dd100f9bdb62c84d9309a63c5019..728b50b765b093bf5b16c9382c67f5c9a5f5d226 100644
--- a/SOL005/NSLifecycleManagement-API/ScaleNSTask.robot
+++ b/SOL005/NSLifecycleManagement-API/ScaleNSTask.robot
@@ -13,7 +13,7 @@ POST Scale a nsInstance
... Test title: POST Scale a nsInstance
... Test objective: The objective is to test that POST method scales NS instance
... Pre-conditions: NS instance is INSTANTIATED state
- ... Reference: Clause 6.4.5.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.5.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: NS instance is INSTANTIATED state and NS has been scaled
@@ -27,7 +27,7 @@ POST Scale a nsInstance - Conflict (Not Instantited)
... Test title: POST Scale a nsInstance - Conflict (Not Instantited)
... Test objective: The objective is to test that POST method cannot scale NS instance because of conflict in resource status (i.e. because the resource is in NOT_INSTANTIATED state)
... Pre-conditions: NS instance is in NOT_INSTANTIATED state.
- ... Reference: Clause 6.4.5.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.5.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: The Scale NS operation is not triggered on the NFVO
@@ -40,7 +40,7 @@ GET Scale NSInstance- Method not implemented
... Test title: GET Scale NSInstance- Method not implemented
... Test objective: The objective is to test that GET method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -52,7 +52,7 @@ PUT Scale NSInstance - Method not implemented
... Test title: PUT Scale NSInstance - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.5.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.5.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -64,7 +64,7 @@ PATCH Scale NSInstance - Method not implemented
... Test title: PATCH Scale NSInstance - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.5.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.5.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -76,7 +76,7 @@ DELETE Scale NSInstance - Method not implemented
... Test title: DELETE Scale NSInstance - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.5.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.5.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/NSLifecycleManagement-API/ScaleNSTaskWorkflow.robot b/SOL005/NSLifecycleManagement-API/ScaleNSTaskWorkflow.robot
index 5f103c786bc3e8da5ac558a4abb2d68c4f14d199..1d651432993b2be672447c88d0b47e8dd8263896 100644
--- a/SOL005/NSLifecycleManagement-API/ScaleNSTaskWorkflow.robot
+++ b/SOL005/NSLifecycleManagement-API/ScaleNSTaskWorkflow.robot
@@ -14,7 +14,7 @@ Scale Flow of NS lifecycle management operations
... Test title: Instantiate Flow of NS lifecycle management operations
... Test objective: The objective is to test the workflow for Instantiate a NS instance
... Pre-conditions: the resource is in NOT_INSTANTIATED state
- ... Reference: Clause 6.4.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: the resource is in INSTANTIATED state
diff --git a/SOL005/NSLifecycleManagement-API/Subscriptions.robot b/SOL005/NSLifecycleManagement-API/Subscriptions.robot
index bcdfb321832c266a29c0a33989ce867009140eda..8368092b32c985cb7a0ea56d7c133d9451b0ef00 100644
--- a/SOL005/NSLifecycleManagement-API/Subscriptions.robot
+++ b/SOL005/NSLifecycleManagement-API/Subscriptions.robot
@@ -15,7 +15,7 @@ POST Create a new subscription
... Test title: POST Create a new subscription
... Test objective: The objective is to test that POST method create a subscription
... Pre-conditions: none
- ... Reference: Clause 6.4.16.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.16.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: subscription is created in the NFVO
@@ -29,7 +29,7 @@ POST Create a new Subscription - DUPLICATION
... Test title: POST Create a new subscription - DUPLICATION
... Test objective: The objective is to test that POST method create a duplicate subscription
... Pre-conditions: a subscription shall already exist
- ... Reference: Clause 6.4.16.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.16.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: duplication supported by NFVO
... Post-Conditions: duplicate subscription is created in the NFVO
@@ -43,7 +43,7 @@ POST Create a new Subscription - NO-DUPLICATION
... Test title: POST Create a new subscription - NO-DUPLICATION
... Test objective: The objective is to test that POST method cannot create a duplicate subscription
... Pre-conditions: a subscription shall already exist
- ... Reference: Clause 6.4.16.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.16.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: duplication NOT supported by NFVO
... Post-Conditions: duplicate subscription is not created in the NFVO
@@ -56,7 +56,7 @@ GET Subscriptions
... Test title: GET Subscriptions
... Test objective: The objective is to test that GET method retrieve the list of existing subscriptions
... Pre-conditions: none
- ... Reference: Clause 6.4.16.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.16.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -69,7 +69,7 @@ GET Subscription - Filter
... Test title: GET Subscription - Filter
... Test objective: The objective is Get the list of active subscriptions using a filter
... Pre-conditions: none
- ... Reference: Clause 6.4.16.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.16.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -82,7 +82,7 @@ GET subscriptions - Bad Request Invalid attribute-based filtering parameters
... Test title: GET subscriptions - Bad Request Invalid attribute-based filtering parameters
... Test objective: The objective is Get the list of active subscriptions using an invalid filter
... Pre-conditions: none
- ... Reference: Clause 6.4.16.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.16.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -95,7 +95,7 @@ GET subscriptions with "all_fields" attribute selector
... Test title: GET subscriptions with "all_fields" attribute selector
... Test objective: The objective is to retrieve the list of active subscriptions with attribute selector
... Pre-conditions:
- ... Reference: Clause 6.4.16.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.16.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability:
... Post-Conditions:
@@ -108,7 +108,7 @@ GET subscriptions with "exclude_default" attribute selector
... Test title: GET subscriptions with "exclude_default" attribute selector
... Test objective: The objective is to retrieve the list of active subscriptions with attribute selector
... Pre-conditions:
- ... Reference: Clause 6.4.16.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.16.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability:
... Post-Conditions:
@@ -121,7 +121,7 @@ GET subscriptions with "fields" attribute selector
... Test title: GET subscriptions with "fields" attribute selector
... Test objective: The objective is to retrieve the list of active subscriptions with attribute selector
... Pre-conditions:
- ... Reference: Clause 6.4.16.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.16.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability:
... Post-Conditions:
@@ -134,7 +134,7 @@ GET subscriptions with "exclude_fields" attribute selector
... Test title: GET subscriptions with "exclude_fields" attribute selector
... Test objective: The objective is to retrieve the list of active subscriptions with attribute selector
... Pre-conditions:
- ... Reference: Clause 6.4.16.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.16.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability:
... Post-Conditions:
@@ -147,7 +147,7 @@ PUT subscriptions - Method not implemented
... Test title: PUT subscriptions - Method not implemented
... Test objective: The objective is to test that PUT method cannot modify a NS lifecycle management subscription
... Pre-conditions: none
- ... Reference: Clause 6.4.16.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.16.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -159,7 +159,7 @@ PATCH subscriptions - Method not implemented
... Test title: PATCH subscriptions - Method not implemented
... Test objective: The objective is to test that PUT method cannot modify a NS lifecycle management subscription
... Pre-conditions: none
- ... Reference: Clause 6.4.16.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.16.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -171,7 +171,7 @@ DELETE subscriptions - Method not implemented
... Test title: DELETE subscriptions - Method not implemented
... Test objective: The objective is to test that DELETE method cannot modify a NS lifecycle management subscription
... Pre-conditions: none
- ... Reference: Clause 6.4.16.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.16.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -183,7 +183,7 @@ GET Subscriptions as Paged Response
... Test title: GET Subscriptions as Paged Response
... Test objective: The objective is to test that GET method retrieve the list of existing subscriptions as paged response.
... Pre-conditions: none
- ... Reference: Clause 6.4.16.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.16.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: NFVO supports paged response
... Post-Conditions: none
@@ -196,7 +196,7 @@ GET subscriptions - Bad Request Response too Big
... Test title: GET subscriptions - Bad Request Response too Big
... Test objective: The objective is test that the retrieval of active subscriptions list fails because response is too big, and perform the JSON schema validation of the failed operation HTTP response.
... Pre-conditions: none
- ... Reference: Clause 6.4.16.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.16.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: NFVO does not support paged response
... Post-Conditions: none
@@ -204,14 +204,14 @@ GET subscriptions - Bad Request Response too Big
Check HTTP Response Status Code Is 400
Check HTTP Response Body Json Schema Is ProblemDetails
-POST Create a new subscription - Unprocessable Entity
+POST Create a new subscription - Unprocessable Content
[Documentation] Test ID: 5.3.2.15.16
- ... Test title: POST Create a new subscription - Unprocessable Entity
+ ... Test title: POST Create a new subscription - Unprocessable Content
... Test objective: The objective is to test the creation of a new lifecycle management subscription fials when 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
... Pre-conditions: none
- ... Reference: Clause 6.4.16.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.16.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
POST subscriptions
- Check HTTP Response Status Code Is 422
\ No newline at end of file
+ Check HTTP Response Status Code Is 422
diff --git a/SOL005/NSLifecycleManagement-API/TerminateNSTask.robot b/SOL005/NSLifecycleManagement-API/TerminateNSTask.robot
index 5a031f0bffdfc11b5414e9b0b03f05f8c5114f1b..c81445cc0fdd683101793b3d902fc223456c42a5 100644
--- a/SOL005/NSLifecycleManagement-API/TerminateNSTask.robot
+++ b/SOL005/NSLifecycleManagement-API/TerminateNSTask.robot
@@ -12,7 +12,7 @@ POST Terminate a NSInstance
... Test title: POST Terminate a NSInstance
... Test objective: The objective is to test that POST method terminate the NS
... Pre-conditions: NS instance in INSTANTIATED state
- ... Reference: Clause 6.4.8.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.8.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: NS instance has NOT_INSTANTIATED state
@@ -26,7 +26,7 @@ POST Terminate a NSInstance - Conflict (Not Instantited)
... Test title: POST Terminate a NSInstance - Conflict (Not Instantited)
... Test objective: The objective is to test that POST method cannot terminate the NS because of conflict in resource status (i.e. the resource is not in INSTANTIATED state)
... Pre-conditions: NS instance is in NOT_INSTANTIATED state
- ... Reference: Clause 6.4.8.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.8.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: NS instance is in NOT_INSTANTIATED state
@@ -40,7 +40,7 @@ GET Terminate NSInstance- Method not implemented
... Test title: GET Terminate NSInstance- Method not implemented
... Test objective: The objective is to test that GET method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.8.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.8.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -52,7 +52,7 @@ PUT Terminate NSInstance - Method not implemented
... Test title: PUT Terminate NSInstance - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.8.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.8.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -64,7 +64,7 @@ PATCH Terminate NSInstance - Method not implemented
... Test title: PATCH Terminate NSInstance - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.8.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.8.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -76,7 +76,7 @@ DELETE Terminate NSInstance - Method not implemented
... Test title: DELETE Terminate NSInstance - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.8.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.8.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/NSLifecycleManagement-API/TerminateNSTaskWorkflow.robot b/SOL005/NSLifecycleManagement-API/TerminateNSTaskWorkflow.robot
index eef642c6830ffb37721443a0501f6f845d2d4a36..6e615e273891a010423b83629b8798f97feba781 100644
--- a/SOL005/NSLifecycleManagement-API/TerminateNSTaskWorkflow.robot
+++ b/SOL005/NSLifecycleManagement-API/TerminateNSTaskWorkflow.robot
@@ -14,7 +14,7 @@ Terminate Flow of NS lifecycle management operations
... Test title: Terminate Flow of NS lifecycle management operations
... Test objective: The objective is to test the workflow for Terminate a NS instance
... Pre-conditions: the resource is in INSTANTIATED state
- ... Reference: Clause 6.4.8 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.8 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: the resource is in NOT_INSTANTIATED state
diff --git a/SOL005/NSLifecycleManagement-API/UpdateNSTask.robot b/SOL005/NSLifecycleManagement-API/UpdateNSTask.robot
index 6bc1b62a2f3f47812f0c643ac91dc9a7b1157024..e1db1334ca7af1fa8a49904859c129d024fc9b0b 100644
--- a/SOL005/NSLifecycleManagement-API/UpdateNSTask.robot
+++ b/SOL005/NSLifecycleManagement-API/UpdateNSTask.robot
@@ -13,7 +13,7 @@ POST Update a NSInstance
... Test title: POST Update a NSInstance
... Test objective: The objective is to test that POST method update a NS instance
... Pre-conditions: An NS instance is in INSTANTIATED state
- ... Reference: Clause 6.4.6.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.6.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: The NS instance is still INSTANTIATED and updated on the NFVO
@@ -26,7 +26,7 @@ POST Update a NSInstance with feasibility check only
... Test title: POST Update a NSInstance
... Test objective: The objective is to test that POST method update a NS instance with feasibility check only
... Pre-conditions: An NS instance is in INSTANTIATED state
- ... Reference: Clause 6.4.6.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.6.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -39,7 +39,7 @@ POST Update a NSInstance - Conflict (Not Instantited)
... Test title: POST Update a NSInstance - Conflict (Not Instantited)
... Test objective: The objective is to test that POST method fail if a NS Instance is not existing or is in NOT_INSTANTIATED state
... Pre-conditions: An NS instance is in INSTANTIATED state
- ... Reference: Clause 6.4.6.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.6.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: The NS instance is not updated on the NFVO
@@ -52,7 +52,7 @@ GET Update NSInstance- Method not implemented
... Test title: GET Update NSInstance- Method not implemented
... Test objective: The objective is to test that GET method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.6.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.6.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -64,7 +64,7 @@ PUT Update NSInstance - Method not implemented
... Test title: PUT Update NSInstance - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.6.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.6.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -76,7 +76,7 @@ PATCH Update NSInstance - Method not implemented
... Test title: PATCH Update NSInstance - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.6.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.6.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -88,7 +88,7 @@ DELETE Update NSInstance - Method not implemented
... Test title: DELETE Update NSInstance - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.6.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.6.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/NSLifecycleManagement-API/UpdateNSTaskWorkflow.robot b/SOL005/NSLifecycleManagement-API/UpdateNSTaskWorkflow.robot
index 8b645238e4ef13c541be7105e813906b278a210a..7c6076c3f4345fc3efdca1ee7a093bd252aee2a9 100644
--- a/SOL005/NSLifecycleManagement-API/UpdateNSTaskWorkflow.robot
+++ b/SOL005/NSLifecycleManagement-API/UpdateNSTaskWorkflow.robot
@@ -15,7 +15,7 @@ Update Flow of NS lifecycle management operations
... Test title: Update Flow of NS lifecycle management operations
... Test objective: The objective is to test the workflow for Update a NS instance
... Pre-conditions: the resource is in INSTANTIATED state
- ... Reference: Clause 6.4.6 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.6 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: the resource is in INSTANTIATED state
diff --git a/SOL005/NSLifecycleManagement-API/VNFSnapshots.robot b/SOL005/NSLifecycleManagement-API/VNFSnapshots.robot
index e731d1aad9e41a2f450da33352f175a0f7f2e5c6..2442f09e515a90a32b8238f32b06c3191f242fcd 100644
--- a/SOL005/NSLifecycleManagement-API/VNFSnapshots.robot
+++ b/SOL005/NSLifecycleManagement-API/VNFSnapshots.robot
@@ -7,7 +7,7 @@ POST VNF Snapshots - Method Not Implemented
... Test title: POST VNF Snapshots - Method Not Implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.19.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.19.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -19,7 +19,7 @@ GET information about multiple VNF Snapshots
... Test title: GET information about multiple VNF Snapshots
... Test objective: The objective is to get information about multiples VNF snapshots
... Pre-conditions: none
- ... Reference: Clause 6.4.19.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.19.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -32,7 +32,7 @@ GET information about multiple VNF Snapshots Bad Request Invalid attribute-based
... Test title: GET information about multiple VNF Snapshots Bad Request Invalid attribute-based filtering parameters
... Test objective: The objective is to get information about multiples VNF Snapshots with Invalid attribute-based filtering parameters
... Pre-conditions: none
- ... Reference: Clause 6.4.19.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.19.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -45,7 +45,7 @@ GET information about multiple VNF Snapshots Bad Request Invalid attribute selec
... Test title: GET information about multiple VNF Snapshots Bad Request Invalid attribute selector
... Test objective: The objective is to get information about multiples VNF Snapshots with Invalid attribute-based filtering parameters
... Pre-conditions: none
- ... Reference: Clause 6.4.19.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.19.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -58,7 +58,7 @@ GET information about multiple VNF Snapshots with "all_fields" attribute selecto
... Test title: GET information about multiple VNF Snapshots with "all_fields" attribute selector
... Test objective: The objective is to query information about multiple VNF Snapshots
... Pre-conditions: none
- ... Reference: Clause 6.4.19.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.19.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -71,7 +71,7 @@ GET information about multiple VNF Snapshots with "exclude_default" attribute se
... Test title: GET information about multiple VNF Snapshots with "exclude_default" attribute selector
... Test objective: The objective is to query information about multiple VNF Snapshots
... Pre-conditions: none
- ... Reference: Clause 6.4.19.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.19.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -84,7 +84,7 @@ GET information about multiple VNF Snapshots with "fields" attribute selector
... Test title: GET information about multiple VNF Snapshots with "fields" attribute selector
... Test objective: The objective is to query information about multiple VNF Snapshots
... Pre-conditions: none
- ... Reference: Clause 6.4.19.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.19.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -97,7 +97,7 @@ GET information about multiple VNF Snapshots with "exclude_default" and "fields"
... Test title: GET information about multiple VNF Snapshots with "exclude_default" and "fields" attribute selector
... Test objective: The objective is to query information about multiple VNF Snapshots
... Pre-conditions: none
- ... Reference: Clause 6.4.19.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.19.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -110,7 +110,7 @@ GET information about multiple VNF Snapshots with "exclude_fields" attribute sel
... Test title: GET information about multiple VNF Snapshots with "exclude_fields" attribute selector
... Test objective: The objective is to query information about multiple VNF Snapshots
... Pre-conditions: none
- ... Reference: Clause 6.4.19.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.19.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -123,7 +123,7 @@ GET VNF Snapshots - Bad Request Response too Big
... Test title: GET VNF Snapshots - Bad Request Response too Big
... Test objective: The objective is test that the retrieval of existing VNF Snapshots list fails because response is too big, and perform the JSON schema validation of the failed operation HTTP response.
... Pre-conditions: none
- ... Reference: Clause 6.4.19.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.19.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: NFVO does not support paged response.
... Post-Conditions: none
@@ -136,7 +136,7 @@ GET VNF Snapshots as Paged Response
... Test title: GET VNF Snapshots as Paged Response
... Test objective: The objective is to test that GET method retrieves the list of existing VNF Snapshots as paged response.
... Pre-conditions: none
- ... Reference: Clause 6.4.19.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.19.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: NFVO supports paged response.
... Post-Conditions: none
@@ -149,7 +149,7 @@ PUT VNF Snapshots - Method not implemented
... Test title: PUT VNF Snapshots - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.19.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.19.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -161,7 +161,7 @@ PATCH VNF Snapshots - Method not implemented
... Test title: PATCH VNF Snapshots - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.19.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.19.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -173,7 +173,7 @@ DELETE VNF Snapshots - Method not implemented
... Test title: DELETE VNF Snapshots - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 6.4.19.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.19.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -185,7 +185,7 @@ GET information about multiple VNF Snapshots using Filter
... Test title: GET information about multiple VNF Snapshots using Filter
... Test objective: The objective is to get information about multiples VNF snapshots using filter
... Pre-conditions: none
- ... Reference: Clause 6.4.19.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.19.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/NSLifecycleManagement-API/environment/variables.txt b/SOL005/NSLifecycleManagement-API/environment/variables.txt
index 3250455c16882b6fca4706517895cf4ba86c084d..57ba85380f9a4adb3b09699ecc682b92fa92f67e 100644
--- a/SOL005/NSLifecycleManagement-API/environment/variables.txt
+++ b/SOL005/NSLifecycleManagement-API/environment/variables.txt
@@ -117,4 +117,7 @@ ${Provider}
${Product_Name}
${Software_Version}
${Descriptor_Version}
-${Flavour_ID}
\ No newline at end of file
+${Flavour_ID}
+
+${invalid_etag}= invalid etag
+${PRODUCER_SUPPORT_COND_REQ} 1
\ No newline at end of file
diff --git a/SOL005/NSLifecycleManagement-API/schemas/NsInstance.schema.json b/SOL005/NSLifecycleManagement-API/schemas/NsInstance.schema.json
index fe1b03d4b25236b98061cf975376c89f58a725ab..a747be656c090130f565622920f53fa6470fe253 100644
--- a/SOL005/NSLifecycleManagement-API/schemas/NsInstance.schema.json
+++ b/SOL005/NSLifecycleManagement-API/schemas/NsInstance.schema.json
@@ -1,3441 +1,4135 @@
{
- "description": "This type represents a response for Query NS operation. It shall comply with the provisions defined in Table 6.5.2.10-1.\nNOTE 1: Void. \"vnfInstance\" attribute or one \"nestedNsInstanceId\" attribute shall be present.\nNOTE 2: The priority attribute of the NS instance is configured in the NSD in the NsDf structure. The mapping from application-specific priority values to a value in the NsDf is under OSS/BSS responsibility.\n The \"zero\" value expresses the highest priority and the fact that the NS instance based on this DF cannot be\n pre-empted during resource allocation.\nNOTE 3: Examples for the usage of priority include conflict resolution in case of resource shortage\n",
+ "description": "This type represents a response for Query NS operation. It shall comply with the provisions defined in Table 6.5.2.10-1.\nNOTE 1: Void.\n \"vnfInstance\" attribute or one \"nestedNsInstanceId\" attribute shall be present.\nNOTE 2: The “priority” attribute of the NS instance is configured in the NSD in the NsDf structure.\n The mapping from application-specific priority values to a value in the NsDf is under OSS/BSS responsibility.\n The \"zero\" value expresses the highest priority and the fact that the NS instance based on this DF cannot be\n pre-empted during resource allocation.\nNOTE 3: Examples for the usage of priority include conflict resolution in case of resource shortage\n",
"type": "object",
- "required": ["id", "nsInstanceName", "nsInstanceDescription", "nsdId", "nsdInfoId", "nsState", "_links"],
+ "required": [
+ "id",
+ "nsInstanceName",
+ "nsInstanceDescription",
+ "nsdId",
+ "nsdInfoId",
+ "nsState",
+ "_links"
+ ],
"properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "nsInstanceName": {
- "description": "Human readable name of the NS instance.\n",
- "type": "string"
- },
- "nsInstanceDescription": {
- "description": "Human readable description of the NS instance.\n",
- "type": "string"
- },
- "nsdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "versionDependency": {
- "description": "Describes version dependencies currently valid for the nested NS instance. Identifies versions of descriptors of other constituents in the NSD upon which the nested NS depends. The dependencies may be described for the NSD referenced in this NsInfo with nsdId and for NSDs with the same NsdExtInvariantId. There shall not be more than one versionDependency present with the same dependentConstituentId. It may be present for the NsInfo of a nested NS. It shall not be present otherwise.\n",
- "type": "array",
- "items": {
- "description": "This type represents the information related to all dependencies that an NSD constituent has on the versions of other NSD constituents. It shall comply with the provisions defined in table 6.5.3.112-1.\n",
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "nsInstanceName": {
+ "description": "Human readable name of the NS instance.\n",
+ "type": "string"
+ },
+ "nsInstanceDescription": {
+ "description": "Human readable description of the NS instance.\n",
+ "type": "string"
+ },
+ "nsdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "versionDependency": {
+ "description": "Describes version dependencies currently valid for the nested NS instance. Identifies versions of descriptors of other constituents in the NSD upon which the nested NS depends. The dependencies may be described for the NSD referenced in this NsInfo with nsdId and for NSDs with the same \"nsdExtInvariantId\". There shall not be more than one versionDependency present with the same dependentConstituentId. It may be present for the NsInfo of a nested NS. It shall not be present otherwise.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the information related to all dependencies that an NSD constituent has on the versions of other NSD constituents. It shall comply with the provisions defined in table 6.5.3.112-1.\n",
+ "type": "object",
+ "required": [
+ "dependentConstituentId"
+ ],
+ "properties": {
+ "dependentConstituentId": {
+ "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "versionDependencyStatement": {
+ "description": "Identifies one or multiple versions of an NSD constituents upon which the dependent constituent identified by dependentConstituentId has a dependency. Cardinality 0 is used to remove an existing version dependency in a profile.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the information related to one or more VNF, NS or PNF descriptor identifiers which describe one single dependency. When more than one descriptor is indicated, they correspond to different versions of the same VNF, NS or PNF and they represent alternatives to fulfil the dependency. It shall comply with the provisions defined in table 6.5.3.113-1.\n",
"type": "object",
- "required": ["dependentConstituentId"],
+ "required": [
+ "descriptorId"
+ ],
"properties": {
- "dependentConstituentId": {
- "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
- "type": "string"
- },
- "versionDependencyStatement": {
- "description": "Identifies one or multiple versions of an NSD constituents upon which the dependent constituent identified by dependentConstituentId has a dependency. Cardinality 0 is used to remove an existing version dependency in a profile.\n",
- "type": "array",
- "items": {
- "description": "This type represents the information related to one or more VNF, NS or PNF descriptor identifiers which describe one single dependency. When more than one descriptor is indicated, they correspond to different versions of the same VNF, NS or PNF and they represent alternatives to fulfil the dependency. It shall comply with the provisions defined in table 6.5.3.113-1.\n",
- "type": "object",
- "required": ["descriptorId"],
- "properties": {
- "descriptorId": {
- "description": "Identifies a VNFD, NSD or PNFD upon which the entity using this information element depends. When more than one descriptor is indicated, they shall correspond to versions of the same VNF, NS or PNF and they represent. alternatives, i.e. the presence of one of them fulfills the dependency.",
- "type": "array",
- "items": {
- "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- }
- }
+ "descriptorId": {
+ "description": "Identifies a VNFD, NSD or PNFD upon which the entity using this data type depends. When more than one descriptor is indicated, they shall correspond to versions of the same VNF, NS or PNF and they represent alternatives, i.e. the presence of one of them fulfills the dependency.",
+ "type": "array",
+ "items": {
+ "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
+ "type": "string"
}
+ }
}
+ }
}
- },
- "nsdInfoId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "flavourId": {
- "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
- "type": "string"
- },
- "priority": {
- "description": "A number as defined in IETF RFC 8259.\n",
- "type": "number"
- },
- "vnfInstance": {
- "description": "Information on constituent VNF(s) of the NS instance.\n",
- "type": "array",
- "items": {
- "description": "This type represents a VNF instance. It shall comply with the provisions defined in table 6.5.3.57-1.\nNOTE: Clause B.3.2 of ETSI GS NFV-SOL 003 provides examples illustrating the relationship among the different run-time information elements (CP, VL and link ports) used to represent the connectivity \n of a VNF.\n\nNOTE 1: 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 changed with respect to \n the previous VNFD in other aspects than merely referencing to other VNF software images. \n In order to avoid misalignment of the VnfInstance with the current VNF's on-boarded VNF Package, \n the values of attributes in the VnfInstance that have corresponding attributes in the VNFD shall \n be kept in sync with the values in the VNFD.\nNOTE 2: ETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on TOSCA specifications. NOTE 3: VNF configurable properties are sometimes also referred to as configuration parameters applicable to a VNF. Some of these are set prior to instantiation and cannot be modified if the VNF is instantiated, \n some are set prior to instantiation (are part of initial configuration) and can be modified later, \n and others can be set only after instantiation. The applicability of certain configuration may depend \n on the VNF and the required operation of the VNF at a certain point in time.\nNOTE 4: It is possible to have several ExtManagedVirtualLinkInfo for the same VNF internal VL in case of a multi-site VNF spanning several VIMs. The set of ExtManagedVirtualLinkInfo corresponding to the same \n VNF internal VL shall indicate so by referencing to the same VnfVirtualLinkDesc and externally-managed \n multi-site VL instance (refer to clause 6.5.3.59).\nNOTE 5: Even though externally-managed internal VLs are also used for VNF-internal connectivity, they shall not be listed in the \"vnfVirtualLinkResourceInfo\" attribute as this would be redundant.\n",
+ }
+ }
+ },
+ "nsdInfoId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "flavourId": {
+ "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "priority": {
+ "description": "A number as defined in IETF RFC 8259.\n",
+ "type": "number"
+ },
+ "vnfInstance": {
+ "description": "Information on constituent VNF(s) of the NS instance.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents a VNF instance. It shall comply with the provisions defined in table 6.5.3.57-1.\nNOTE: Clause B.3.2 of ETSI GS NFV-SOL 003 provides examples illustrating the relationship among the \n different run-time data types (CP, VL and link ports) used to represent the connectivity \n of a VNF.\n\nNOTE 1: Modifying the value of this attribute shall not be performed when conflicts exist between the \n previous and the newly referred VNF package, i.e. when the new VNFD is changed with respect to \n the previous VNFD in other aspects than merely referencing to other VNF software images. \n In order to avoid misalignment of the VnfInstance with the current VNF's on-boarded VNF Package, \n the values of attributes in the VnfInstance that have corresponding attributes in the VNFD shall \n be kept in sync with the values in the VNFD.\nNOTE 2: ETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on TOSCA specifications. NOTE 3: VNF configurable properties are sometimes also referred to as configuration parameters applicable \n to a VNF. Some of these are set prior to instantiation and cannot be modified if the VNF is instantiated, \n some are set prior to instantiation (are part of initial configuration) and can be modified later, \n and others can be set only after instantiation. The applicability of certain configuration may depend \n on the VNF and the required operation of the VNF at a certain point in time.\nNOTE 4: It is possible to have several ExtManagedVirtualLinkInfo for the same VNF internal VL in case of a \n multi-site VNF spanning several VIMs. The set of ExtManagedVirtualLinkInfo corresponding to the same \n VNF internal VL shall indicate so by referencing to the same VnfVirtualLinkDesc and externally-managed \n multi-site VL instance (refer to clause 6.5.3.59).\nNOTE 5: Even though externally-managed internal VLs are also used for VNF-internal connectivity, they shall not \n be listed in the \"vnfVirtualLinkResourceInfo\" attribute as this would be redundant.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "vnfdId",
+ "vnfProvider",
+ "vnfProductName",
+ "vnfSoftwareVersion",
+ "vnfdVersion",
+ "vnfPkgId",
+ "instantiationState"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfInstanceName": {
+ "description": "Name of the VNF instance. Modifications to this attribute can be requested using the \"ModifyVnfInfoData\" structure.\n",
+ "type": "string"
+ },
+ "vnfInstanceDescription": {
+ "description": "Human-readable description of the VNF instance. Modifications to this attribute can be requested using the \"ModifyVnfInfoData\" structure.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfProvider": {
+ "description": "Provider of the VNF and the VNFD. The value is copied from the VNFD.\n",
+ "type": "string"
+ },
+ "vnfProductName": {
+ "description": "Name to identify the VNF Product. The value is copied from the VNFD.\n",
+ "type": "string"
+ },
+ "vnfSoftwareVersion": {
+ "description": "A Version. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vnfdVersion": {
+ "description": "A Version. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "versionDependency": {
+ "description": "Describes version dependencies currently valid for the VNF instance. Identifies versions of descriptors of other constituents in the NSD upon which the VNF depends. The dependencies may be described for the VNFD referenced in this VnfInfo with \"vnfdId\" and for VNFDs with the same \"vnfdExtInvariantId\". There shall not be more than one \"versionDependency\" present with the same dependentConstituentId.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the information related to all dependencies that an NSD constituent has on the versions of other NSD constituents. It shall comply with the provisions defined in table 6.5.3.112-1.\n",
"type": "object",
- "required": ["id", "vnfdId", "vnfProvider", "vnfProductName", "vnfSoftwareVersion", "vnfdVersion", "vnfPkgId", "instantiationState"],
+ "required": [
+ "dependentConstituentId"
+ ],
"properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
+ "dependentConstituentId": {
+ "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "versionDependencyStatement": {
+ "description": "Identifies one or multiple versions of an NSD constituents upon which the dependent constituent identified by dependentConstituentId has a dependency. Cardinality 0 is used to remove an existing version dependency in a profile.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the information related to one or more VNF, NS or PNF descriptor identifiers which describe one single dependency. When more than one descriptor is indicated, they correspond to different versions of the same VNF, NS or PNF and they represent alternatives to fulfil the dependency. It shall comply with the provisions defined in table 6.5.3.113-1.\n",
+ "type": "object",
+ "required": [
+ "descriptorId"
+ ],
+ "properties": {
+ "descriptorId": {
+ "description": "Identifies a VNFD, NSD or PNFD upon which the entity using this data type depends. When more than one descriptor is indicated, they shall correspond to versions of the same VNF, NS or PNF and they represent alternatives, i.e. the presence of one of them fulfills the dependency.",
+ "type": "array",
+ "items": {
+ "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
+ "type": "string"
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ },
+ "vnfPkgId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfConfigurableProperties": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ },
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "instantiationState": {
+ "description": "The instantiation state of the VNF.\nPermitted values: - NOT_INSTANTIATED: The VNF instance is terminated or not instantiated. - INSTANTIATED: The VNF instance is instantiated.\n",
+ "type": "string",
+ "enum": [
+ "NOT_INSTANTIATED",
+ "INSTANTIATED"
+ ]
+ },
+ "instantiatedVnfInfo": {
+ "description": "Information specific to an instantiated VNF instance. This attribute shall be present if the instantiateState attribute value is INSTANTIATED.\n",
+ "type": "object",
+ "required": [
+ "flavourId",
+ "vnfState",
+ "extCpInfo"
+ ],
+ "properties": {
+ "flavourId": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
+ "type": "string"
+ },
+ "vnfState": {
+ "type": "string",
+ "enum": [
+ "STARTED",
+ "STOPPED"
+ ]
+ },
+ "scaleStatus": {
+ "description": "Scale status of the VNF, one entry per aspect. Represents for every scaling aspect how \"big\" the VNF has been scaled w.r.t. that aspect.\n",
+ "type": "array",
+ "items": {
+ "required": [
+ "aspectId",
+ "scaleLevel"
+ ],
+ "type": "object",
+ "properties": {
+ "aspectId": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
"type": "string"
- },
- "vnfInstanceName": {
- "description": "Name of the VNF instance. Modifications to this attribute can be requested using the \"ModifyVnfInfoData\" structure.\n",
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
"type": "string"
- },
- "vnfInstanceDescription": {
- "description": "Human-readable description of the VNF instance. Modifications to this attribute can be requested using the \"ModifyVnfInfoData\" structure.\n",
+ },
+ "scaleLevel": {
+ "description": "Indicates the scale level. The minimum value shall be 0 and the maximum value shall be <= maxScaleLevel as described in the VNFD.\n",
+ "type": "integer"
+ }
+ }
+ }
+ },
+ "maxScaleLevels": {
+ "description": "Maximum allowed scale levels of the VNF, one entry per aspect. This attribute shall be present if the VNF supports scaling.\n",
+ "type": "array",
+ "items": {
+ "required": [
+ "aspectId",
+ "scaleLevel"
+ ],
+ "type": "object",
+ "properties": {
+ "aspectId": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
"type": "string"
- },
- "vnfdId": {
+ },
+ "vnfdId": {
"description": "An identifier with the intention of being globally unique.\n",
"type": "string"
- },
- "vnfProvider": {
- "description": "Provider of the VNF and the VNFD. The value is copied from the VNFD.\n",
+ },
+ "scaleLevel": {
+ "description": "Indicates the scale level. The minimum value shall be 0 and the maximum value shall be <= maxScaleLevel as described in the VNFD.\n",
+ "type": "integer"
+ }
+ }
+ }
+ },
+ "extCpInfo": {
+ "description": "Information about the external CPs exposed by the VNF instance. When trunking is enabled, the list of entries includes both, external CPs corresponding to parent ports of a trunk, and external CPs associated to sub-ports of a trunk.\n",
+ "type": "array",
+ "minItems": 1,
+ "items": {
+ "description": "This type represents information about an external CP of a VNF. It shall comply with the provisions defined in Table 6.5.3.70-1. NOTE 1: The attributes attributes \"associatedVnfcCpId\", \"associatedVipCpId\", \"associatedVirtualCpId\" and \"associatedVnfVirtualLinkId\" are mutually exclusive. Exactly one shall be present. NOTE 2: An external CP instance is not associated to a link port in the cases indicated for the “extLinkPorts” attribute in clause 6.5.3.26. NOTE 3: Cardinality greater than 1 is only applicable for specific cases where more than one network attachment definition resource is needed to fulfil the connectivity requirements of the external CP, e.g. to build a link redundant mated pair in SR-IOV cases. NOTE 4: When more than one \"netAttDefResourceId\" is indicated, all shall belong to the same namespace.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "cpdId",
+ "cpProtocolInfo"
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "associatedVnfcCpId"
+ ]
+ },
+ {
+ "required": [
+ "associatedVipCpId"
+ ]
+ },
+ {
+ "required": [
+ "associatedVirtualCpId"
+ ]
+ },
+ {
+ "required": [
+ "associatedVnfVirtualLinkId"
+ ]
+ }
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
"type": "string"
- },
- "vnfProductName": {
- "description": "Name to identify the VNF Product. The value is copied from the VNFD.\n",
+ },
+ "cpdId": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
"type": "string"
- },
- "vnfSoftwareVersion": {
- "description": "A Version. Representation: string of variable length.\n",
+ },
+ "cpConfigId": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
"type": "string"
- },
- "vnfdVersion": {
- "description": "A Version. Representation: string of variable length.\n",
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
"type": "string"
- },
- "versionDependency": {
- "description": "Describes version dependencies currently valid for the VNF instance. Identifies versions of descriptors of other constituents in the NSD upon which the VNF depends. The dependencies may be described for the VNFD referenced in this VnfInfo with vnfdId and for VNFDs with the same VnfdExtInvariantId. There shall not be more than one versionDependency present with the same dependentConstituentId.\n",
+ },
+ "cpProtocolInfo": {
+ "description": "Network protocol information for this CP.\n",
"type": "array",
+ "minItems": 1,
"items": {
- "description": "This type represents the information related to all dependencies that an NSD constituent has on the versions of other NSD constituents. It shall comply with the provisions defined in table 6.5.3.112-1.\n",
- "type": "object",
- "required": ["dependentConstituentId"],
- "properties": {
- "dependentConstituentId": {
- "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
- "type": "string"
+ "description": "This type describes the protocol layer(s) that a CP or SAP uses together with protocol-related information, like addresses. It shall comply with the provisions defined in Table 6.5.3.58-1. NOTE: This attribute allows to signal the addition of further types of layer and protocol in future versions of the present document in a backwards-compatible way. In the current version of the present document, only IP over Ethernet is supported.\n",
+ "type": "object",
+ "required": [
+ "layerProtocol",
+ "ipOverEthernet"
+ ],
+ "properties": {
+ "layerProtocol": {
+ "description": "The identifier of layer(s) and protocol(s) associated to the network address information. Permitted values:\n - IP_OVER_ETHERNET\n - IP_FOR_VIRTUAL_CP\nSee note.\n",
+ "type": "string",
+ "enum": [
+ "IP_OVER_ETHERNET",
+ "IP_FOR_VIRTUAL_CP"
+ ]
+ },
+ "ipOverEthernet": {
+ "description": "This type represents information about a network address that has been assigned.\nNOTE 1: At least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2: Exactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3: If the Cp instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4: Depending on the NFVI networking infrastructure, the \"segmentationId\" may indicate the actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header of the packets or it may be an identifier used between the application and the NFVI networking infrastructure to identify the network sub-interface of the trunk port in question. In the latter case the NFVI infrastructure will map this local \"segmentationId\" to whatever \"segmentationId\" is actually used by the NFVI's transport technology.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "required": [
+ "macAddress"
+ ]
},
- "versionDependencyStatement": {
- "description": "Identifies one or multiple versions of an NSD constituents upon which the dependent constituent identified by dependentConstituentId has a dependency. Cardinality 0 is used to remove an existing version dependency in a profile.\n",
- "type": "array",
- "items": {
- "description": "This type represents the information related to one or more VNF, NS or PNF descriptor identifiers which describe one single dependency. When more than one descriptor is indicated, they correspond to different versions of the same VNF, NS or PNF and they represent alternatives to fulfil the dependency. It shall comply with the provisions defined in table 6.5.3.113-1.\n",
+ {
+ "required": [
+ "ipAddresses"
+ ]
+ }
+ ],
+ "properties": {
+ "macAddress": {
+ "description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
+ "type": "string",
+ "format": "MAC"
+ },
+ "segmentationId": {
+ "description": "Identification of the network segment to which the Cp instance connects to. See note 3 and note 4.\n",
+ "type": "string"
+ },
+ "ipAddresses": {
+ "description": "Addresses assigned to the CP instance. Each entry represents IP addresses assigned by fixed or dynamic IP address assignment per subnet. See note 1.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": [
+ "type"
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "addresses"
+ ]
+ },
+ {
+ "required": [
+ "addressRange"
+ ]
+ }
+ ],
+ "properties": {
+ "type": {
+ "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
+ },
+ "addresses": {
+ "description": "Fixed addresses assigned (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
+ "type": "array",
+ "items": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ }
+ },
+ "isDynamic": {
+ "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
+ "type": "boolean"
+ },
+ "addressRange": {
+ "description": "An IP address range used, e.g., in case of egress connections. Exactly one of \"addresses\" or \"addressRange\" shall be present. See note 2.\n",
"type": "object",
- "required": ["descriptorId"],
+ "required": [
+ "minAddress",
+ "maxAddress"
+ ],
"properties": {
- "descriptorId": {
- "description": "Identifies a VNFD, NSD or PNFD upon which the entity using this information element depends. When more than one descriptor is indicated, they shall correspond to versions of the same VNF, NS or PNF and they represent. alternatives, i.e. the presence of one of them fulfills the dependency.",
- "type": "array",
- "items": {
- "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
- "type": "string"
- }
- }
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ }
}
+ },
+ "subnetId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "type": {
+ "description": "The type of the IP addresses\n",
+ "type": "string",
+ "enum": [
+ "PV4",
+ "PV6"
+ ]
+ },
+ "addresses": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "isDynamic": {
+ "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
+ "type": "boolean"
+ },
+ "addressRange": {
+ "description": "An IP address range used, e.g. in case of egress connections. See note.\n",
+ "type": "object",
+ "required": [
+ "minAddress",
+ "maxAddress"
+ ],
+ "properties": {
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
}
+ }
+ },
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "subnetId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ }
+ }
+ },
+ "virtualCpAddress": {
+ "description": "This type represents information about a network address that has been assigned to a virtual CP.\n",
+ "type": "object",
+ "required": [
+ "type"
+ ],
+ "properties": {
+ "type": {
+ "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
+ },
+ "loadBalancerIp": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.",
+ "type": "string"
}
+ }
}
+ }
}
- },
- "vnfPkgId": {
+ },
+ "extLinkPortId": {
"description": "An identifier with the intention of being globally unique.\n",
"type": "string"
- },
- "vnfConfigurableProperties": {
+ },
+ "netAttDefResourceId": {
+ "description": "Identifier of the \"NetAttDefResourceInfo\" structure that provides the specification of the interface to attach the connection point to a secondary container cluster network. See notes 3 and 4.\nIt shall be present if the external CP is associated to a VNFC realized by one or a set of OS containers and is connected to a secondary container cluster network. It shall not be present otherwise.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ }
+ },
+ "metadata": {
"description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
"type": "object"
- },
- "vimId": {
+ },
+ "associatedVnfcCpId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "associatedVipCpId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "associatedVirtualCpId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "associatedVnfVirtualLinkId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "vipCpInfo": {
+ "description": "VIP CPs that are part of the VNF instance. Shall be present when that particular VIP CP of the VNFC instance is associated to an external CP of the VNF instance. May be present otherwise.\n",
+ "type": "array",
+ "items": {
+ "description": "This type provides information related to virtual IP (VIP) CP. It shall comply with the provisions defined in table 6.5.3.97 1. NOTE: It is possible that there is no associated VnfcCp because the VIP CP is available but not associated yet.\n",
+ "type": "object",
+ "required": [
+ "cpInstanceId",
+ "cpdId"
+ ],
+ "properties": {
+ "cpInstanceId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "cpdId": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
+ "type": "string"
+ },
+ "vnfdId": {
"description": "An identifier with the intention of being globally unique.\n",
"type": "string"
- },
- "instantiationState": {
- "description": "The instantiation state of the VNF.\nPermitted values: - NOT_INSTANTIATED: The VNF instance is terminated or not instantiated. - INSTANTIATED: The VNF instance is instantiated.\n",
- "type": "string",
- "enum": ["NOT_INSTANTIATED", "INSTANTIATED"]
- },
- "instantiatedVnfInfo": {
- "description": "Information specific to an instantiated VNF instance. This attribute shall be present if the instantiateState attribute value is INSTANTIATED.\n",
- "type": "object",
- "required": ["flavourId", "vnfState", "extCpInfo"],
- "properties": {
- "flavourId": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "vnfState": {
- "type": "string",
- "enum": ["STARTED", "STOPPED"]
+ },
+ "vnfExtCpId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "cpProtocolInfo": {
+ "description": "Protocol information for this CP. There shall be one cpProtocolInfo for layer 3. There may be one cpProtocolInfo for layer 2.\n",
+ "type": "array",
+ "items": {
+ "description": "This type describes the protocol layer(s) that a CP or SAP uses together with protocol-related information, like addresses. It shall comply with the provisions defined in Table 6.5.3.58-1. NOTE: This attribute allows to signal the addition of further types of layer and protocol in future versions of the present document in a backwards-compatible way. In the current version of the present document, only IP over Ethernet is supported.\n",
+ "type": "object",
+ "required": [
+ "layerProtocol",
+ "ipOverEthernet"
+ ],
+ "properties": {
+ "layerProtocol": {
+ "description": "The identifier of layer(s) and protocol(s) associated to the network address information. Permitted values:\n - IP_OVER_ETHERNET\n - IP_FOR_VIRTUAL_CP\nSee note.\n",
+ "type": "string",
+ "enum": [
+ "IP_OVER_ETHERNET",
+ "IP_FOR_VIRTUAL_CP"
+ ]
},
- "scaleStatus": {
- "description": "Scale status of the VNF, one entry per aspect. Represents for every scaling aspect how \"big\" the VNF has been scaled w.r.t. that aspect.\n",
- "type": "array",
- "items": {
- "required": ["aspectId", "scaleLevel"],
+ "ipOverEthernet": {
+ "description": "This type represents information about a network address that has been assigned.\nNOTE 1: At least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2: Exactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3: If the Cp instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4: Depending on the NFVI networking infrastructure, the \"segmentationId\" may indicate the actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header of the packets or it may be an identifier used between the application and the NFVI networking infrastructure to identify the network sub-interface of the trunk port in question. In the latter case the NFVI infrastructure will map this local \"segmentationId\" to whatever \"segmentationId\" is actually used by the NFVI's transport technology.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "required": [
+ "macAddress"
+ ]
+ },
+ {
+ "required": [
+ "ipAddresses"
+ ]
+ }
+ ],
+ "properties": {
+ "macAddress": {
+ "description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
+ "type": "string",
+ "format": "MAC"
+ },
+ "segmentationId": {
+ "description": "Identification of the network segment to which the Cp instance connects to. See note 3 and note 4.\n",
+ "type": "string"
+ },
+ "ipAddresses": {
+ "description": "Addresses assigned to the CP instance. Each entry represents IP addresses assigned by fixed or dynamic IP address assignment per subnet. See note 1.\n",
+ "type": "array",
+ "items": {
"type": "object",
+ "required": [
+ "type"
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "addresses"
+ ]
+ },
+ {
+ "required": [
+ "addressRange"
+ ]
+ }
+ ],
"properties": {
- "aspectId": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "scaleLevel": {
- "description": "Indicates the scale level. The minimum value shall be 0 and the maximum value shall be <= maxScaleLevel as described in the VNFD.\n",
- "type": "integer"
+ "type": {
+ "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
+ },
+ "addresses": {
+ "description": "Fixed addresses assigned (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
+ "type": "array",
+ "items": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ }
+ },
+ "isDynamic": {
+ "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
+ "type": "boolean"
+ },
+ "addressRange": {
+ "description": "An IP address range used, e.g., in case of egress connections. Exactly one of \"addresses\" or \"addressRange\" shall be present. See note 2.\n",
+ "type": "object",
+ "required": [
+ "minAddress",
+ "maxAddress"
+ ],
+ "properties": {
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ }
}
+ },
+ "subnetId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "type": {
+ "description": "The type of the IP addresses\n",
+ "type": "string",
+ "enum": [
+ "PV4",
+ "PV6"
+ ]
+ },
+ "addresses": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "isDynamic": {
+ "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
+ "type": "boolean"
+ },
+ "addressRange": {
+ "description": "An IP address range used, e.g. in case of egress connections. See note.\n",
+ "type": "object",
+ "required": [
+ "minAddress",
+ "maxAddress"
+ ],
+ "properties": {
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
}
+ }
+ },
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "subnetId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
}
+ }
},
- "maxScaleLevels": {
- "description": "Maximum allowed scale levels of the VNF, one entry per aspect. This attribute shall be present if the VNF supports scaling.\n",
- "type": "array",
- "items": {
- "required": ["aspectId", "scaleLevel"],
- "type": "object",
- "properties": {
- "aspectId": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "scaleLevel": {
- "description": "Indicates the scale level. The minimum value shall be 0 and the maximum value shall be <= maxScaleLevel as described in the VNFD.\n",
- "type": "integer"
- }
- }
+ "virtualCpAddress": {
+ "description": "This type represents information about a network address that has been assigned to a virtual CP.\n",
+ "type": "object",
+ "required": [
+ "type"
+ ],
+ "properties": {
+ "type": {
+ "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
+ },
+ "loadBalancerIp": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.",
+ "type": "string"
}
+ }
+ }
+ }
+ }
+ },
+ "associatedVnfcCpIds": {
+ "description": "Identifiers of the VnfcCps that share the virtual IP addresse allocated to the VIP CP instance. See note.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ }
+ },
+ "vnfLinkPortId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "metadata": {
+ "description": "Allows the OSS/BSS to provide additional parameter(s) to the termination process at the NS level.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ }
+ }
+ },
+ "virtualCpInfo": {
+ "description": "virtual CPs that are part of the VNF instance. Shall be present when a particular virtual CP is associated to an external CP of the VNF instance. May be present otherwise.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the information related to a virtual CP instance of a VNF. NOTE: A consumer of the VNF LCM interface can learn the actual VNFC instances implementing the service accessible via the virtual CP instance by querying the \"vnfcResourceInfo\" from the \"InstantiatedVnfInfo\" and filtering by corresponding \"vduId\" values.",
+ "type": "object",
+ "required": [
+ "cpInstanceId",
+ "cpdId",
+ "resourceHandle",
+ "vduId"
+ ],
+ "properties": {
+ "cpInstanceId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "cpdId": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
+ "type": "string"
+ },
+ "resourceHandle": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would correspond to the ‘kind’ field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the ‘claimName’ field in the Kubernetes® manifest, or a compound name built by Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the ‘metadata.name’ field in Kubernetes® manifest. \n",
+ "type": "object",
+ "required": [
+ "resourceId"
+ ],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceProviderId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "type": "string"
+ },
+ "vimLevelAdditionalResourceInfo": {
+ "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
+ "type": "object",
+ "properties": {
+ "hostName": {
+ "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "persistentVolume": {
+ "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ },
+ "containerNamespace": {
+ "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise. \n",
+ "type": "string"
+ }
+ }
+ },
+ "vnfExtCpId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "cpProtocolInfo": {
+ "description": "Protocol information for this CP. There shall be one cpProtocolInfo for each layer protocol supported.\n",
+ "type": "array",
+ "items": {
+ "description": "This type describes the protocol layer(s) that a CP or SAP uses together with protocol-related information, like addresses. It shall comply with the provisions defined in Table 6.5.3.58-1. NOTE: This attribute allows to signal the addition of further types of layer and protocol in future versions of the present document in a backwards-compatible way. In the current version of the present document, only IP over Ethernet is supported.\n",
+ "type": "object",
+ "required": [
+ "layerProtocol",
+ "ipOverEthernet"
+ ],
+ "properties": {
+ "layerProtocol": {
+ "description": "The identifier of layer(s) and protocol(s) associated to the network address information. Permitted values:\n - IP_OVER_ETHERNET\n - IP_FOR_VIRTUAL_CP\nSee note.\n",
+ "type": "string",
+ "enum": [
+ "IP_OVER_ETHERNET",
+ "IP_FOR_VIRTUAL_CP"
+ ]
},
- "extCpInfo": {
- "description": "Information about the external CPs exposed by the VNF instance. When trunking is enabled, the list of entries includes both, external CPs corresponding to parent ports of a trunk, and external CPs associated to sub-ports of a trunk.\n",
- "type": "array",
- "minItems": 1,
- "items": {
- "description": "This type represents information about an external CP of a VNF. It shall comply with the provisions defined in Table 6.5.3.70-1. NOTE 1: The attributes attributes \"associatedVnfcCpId\", \"associatedVipCpId\", \"associatedVirtualCpId\" and \"associatedVnfVirtualLinkId\" are mutually exclusive. Exactly one shall be present. NOTE 2: An external CP instance is not associated to a link port in the cases indicated for the extLinkPorts attribute in clause 6.5.3.26. NOTE 3: Cardinality greater than 1 is only applicable for specific cases where more than one network attachment definition resource is needed to fulfil the connectivity requirements of the external CP, e.g. to build a link redundant mated pair in SR-IOV cases. NOTE 4: When more than one \"netAttDefResourceId\" is indicated, all shall belong to the same namespace.\n",
+ "ipOverEthernet": {
+ "description": "This type represents information about a network address that has been assigned.\nNOTE 1: At least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2: Exactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3: If the Cp instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4: Depending on the NFVI networking infrastructure, the \"segmentationId\" may indicate the actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header of the packets or it may be an identifier used between the application and the NFVI networking infrastructure to identify the network sub-interface of the trunk port in question. In the latter case the NFVI infrastructure will map this local \"segmentationId\" to whatever \"segmentationId\" is actually used by the NFVI's transport technology.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "required": [
+ "macAddress"
+ ]
+ },
+ {
+ "required": [
+ "ipAddresses"
+ ]
+ }
+ ],
+ "properties": {
+ "macAddress": {
+ "description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
+ "type": "string",
+ "format": "MAC"
+ },
+ "segmentationId": {
+ "description": "Identification of the network segment to which the Cp instance connects to. See note 3 and note 4.\n",
+ "type": "string"
+ },
+ "ipAddresses": {
+ "description": "Addresses assigned to the CP instance. Each entry represents IP addresses assigned by fixed or dynamic IP address assignment per subnet. See note 1.\n",
+ "type": "array",
+ "items": {
"type": "object",
- "required": ["id", "cpdId", "cpProtocolInfo"],
- "oneOf": [{
- "required": ["associatedVnfcCpId"]
- }, {
- "required": ["associatedVipCpId"]
- }, {
- "required": ["associatedVirtualCpId"]
- }, {
- "required": ["associatedVnfVirtualLinkId"]
- }],
+ "required": [
+ "type"
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "addresses"
+ ]
+ },
+ {
+ "required": [
+ "addressRange"
+ ]
+ }
+ ],
"properties": {
- "id": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "cpdId": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "cpConfigId": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "cpProtocolInfo": {
- "description": "Network protocol information for this CP.\n",
- "type": "array",
- "minItems": 1,
- "items": {
- "description": "This type describes the protocol layer(s) that a CP or SAP uses together with protocol-related information, like addresses. It shall comply with the provisions defined in Table 6.5.3.58-1. NOTE: This attribute allows to signal the addition of further types of layer and protocol in future versions of the present document in a backwards-compatible way. In the current version of the present document, only IP over Ethernet is supported.\n",
- "type": "object",
- "required": ["layerProtocol", "ipOverEthernet"],
- "properties": {
- "layerProtocol": {
- "description": "The identifier of layer(s) and protocol(s) associated to the network address information. Permitted values: - IP_OVER_ETHERNET\n - IP_FOR_VIRTUAL_CP\nSee note.\n",
- "type": "string",
- "enum": ["IP_OVER_ETHERNET", "IP_FOR_VIRTUAL_CP"]
- },
- "ipOverEthernet": {
- "description": "This type represents information about a network address that has been assigned.\nNOTE 1: At least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2: Exactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3: If the Cp instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4: Depending on the NFVI networking infrastructure, the \"segmentationId\" may indicate the actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header of the packets or it may be an identifier used between the application and the NFVI networking infrastructure to identify the network sub-interface of the trunk port in question. In the latter case the NFVI infrastructure will map this local \"segmentationId\" to whatever \"segmentationId\" is actually used by the NFVI's transport technology.\n",
- "type": "object",
- "anyOf": [{
- "required": ["macAddress"]
- }, {
- "required": ["ipAddresses"]
- }],
- "properties": {
- "macAddress": {
- "description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
- "type": "string",
- "format": "MAC"
- },
- "segmentationId": {
- "description": "Identification of the network segment to which the Cp instance connects to. See note 3 and note 4.\n",
- "type": "string"
- },
- "ipAddresses": {
- "description": "Addresses assigned to the CP instance. Each entry represents IP addresses assigned by fixed or dynamic IP address assignment per subnet. See note 1.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": ["type"],
- "oneOf": [{
- "required": ["addresses"]
- }, {
- "required": ["addressRange"]
- }],
- "properties": {
- "type": {
- "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
- "type": "string",
- "enum": ["IPV4", "IPV6"]
- },
- "addresses": {
- "description": "Fixed addresses assigned (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
- "type": "array",
- "items": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- },
- "isDynamic": {
- "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
- "type": "boolean"
- },
- "addressRange": {
- "description": "An IP address range used, e.g., in case of egress connections. Exactly one of \"addresses\" or \"addressRange\" shall be present. See note 2.\n",
- "type": "object",
- "required": ["minAddress", "maxAddress"],
- "properties": {
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- },
- "subnetId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- }
- },
- "type": {
- "description": "The type of the IP addresses\n",
- "type": "string",
- "enum": ["PV4", "PV6"]
- },
- "addresses": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "isDynamic": {
- "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
- "type": "boolean"
- },
- "addressRange": {
- "description": "An IP address range used, e.g. in case of egress connections. See note.\n",
- "type": "object",
- "required": ["minAddress", "maxAddress"],
- "properties": {
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- },
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "subnetId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- },
- "virtualCpAddress": {
- "description": "This type represents information about a network address that has been assigned to a virtual CP.\n",
- "type": "object",
- "required": ["type"],
- "properties": {
- "type": {
- "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
- "type": "string",
- "enum": ["IPV4", "IPV6"]
- },
- "loadBalancerIp": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- }
- }
- }
- },
- "extLinkPortId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "netAttDefResourceId": {
- "description": "Identifier of the \"NetAttDefResourceInfo\" structure that provides the specification of the interface to attach the connection point to a secondary container cluster network. See notes 3 and 4.\nIt shall be present if the external CP is associated to a VNFC realized by one or a set of OS containers and is connected to a secondary container cluster network. It shall not be present otherwise.\n",
- "type": "array",
- "items": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- }
- },
- "metadata": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- },
- "associatedVnfcCpId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "associatedVipCpId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "associatedVirtualCpId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "associatedVnfVirtualLinkId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
+ "type": {
+ "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
+ },
+ "addresses": {
+ "description": "Fixed addresses assigned (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
+ "type": "array",
+ "items": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ }
+ },
+ "isDynamic": {
+ "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
+ "type": "boolean"
+ },
+ "addressRange": {
+ "description": "An IP address range used, e.g., in case of egress connections. Exactly one of \"addresses\" or \"addressRange\" shall be present. See note 2.\n",
+ "type": "object",
+ "required": [
+ "minAddress",
+ "maxAddress"
+ ],
+ "properties": {
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ }
}
+ },
+ "subnetId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "type": {
+ "description": "The type of the IP addresses\n",
+ "type": "string",
+ "enum": [
+ "PV4",
+ "PV6"
+ ]
+ },
+ "addresses": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "isDynamic": {
+ "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
+ "type": "boolean"
+ },
+ "addressRange": {
+ "description": "An IP address range used, e.g. in case of egress connections. See note.\n",
+ "type": "object",
+ "required": [
+ "minAddress",
+ "maxAddress"
+ ],
+ "properties": {
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
}
+ }
+ },
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "subnetId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
}
+ }
},
- "vipCpInfo": {
- "description": "VIP CPs that are part of the VNF instance. Shall be present when that particular VIP CP of the VNFC instance is associated to an external CP of the VNF instance. May be present otherwise.\n",
- "type": "array",
- "items": {
- "description": "This type provides information related to virtual IP (VIP) CP. It shall comply with the provisions defined in table 6.5.3.97 1. NOTE: It is possible that there is no associated VnfcCp because the VIP CP is available but not associated yet.\n",
- "type": "object",
- "required": ["cpInstanceId", "cpdId"],
- "properties": {
- "cpInstanceId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "cpdId": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfExtCpId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "cpProtocolInfo": {
- "description": "Protocol information for this CP. There shall be one cpProtocolInfo for layer 3. There may be one cpProtocolInfo for layer 2.\n",
- "type": "array",
- "items": {
- "description": "This type describes the protocol layer(s) that a CP or SAP uses together with protocol-related information, like addresses. It shall comply with the provisions defined in Table 6.5.3.58-1. NOTE: This attribute allows to signal the addition of further types of layer and protocol in future versions of the present document in a backwards-compatible way. In the current version of the present document, only IP over Ethernet is supported.\n",
- "type": "object",
- "required": ["layerProtocol", "ipOverEthernet"],
- "properties": {
- "layerProtocol": {
- "description": "The identifier of layer(s) and protocol(s) associated to the network address information. Permitted values: - IP_OVER_ETHERNET\n - IP_FOR_VIRTUAL_CP\nSee note.\n",
- "type": "string",
- "enum": ["IP_OVER_ETHERNET", "IP_FOR_VIRTUAL_CP"]
- },
- "ipOverEthernet": {
- "description": "This type represents information about a network address that has been assigned.\nNOTE 1: At least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2: Exactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3: If the Cp instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4: Depending on the NFVI networking infrastructure, the \"segmentationId\" may indicate the actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header of the packets or it may be an identifier used between the application and the NFVI networking infrastructure to identify the network sub-interface of the trunk port in question. In the latter case the NFVI infrastructure will map this local \"segmentationId\" to whatever \"segmentationId\" is actually used by the NFVI's transport technology.\n",
- "type": "object",
- "anyOf": [{
- "required": ["macAddress"]
- }, {
- "required": ["ipAddresses"]
- }],
- "properties": {
- "macAddress": {
- "description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
- "type": "string",
- "format": "MAC"
- },
- "segmentationId": {
- "description": "Identification of the network segment to which the Cp instance connects to. See note 3 and note 4.\n",
- "type": "string"
- },
- "ipAddresses": {
- "description": "Addresses assigned to the CP instance. Each entry represents IP addresses assigned by fixed or dynamic IP address assignment per subnet. See note 1.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": ["type"],
- "oneOf": [{
- "required": ["addresses"]
- }, {
- "required": ["addressRange"]
- }],
- "properties": {
- "type": {
- "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
- "type": "string",
- "enum": ["IPV4", "IPV6"]
- },
- "addresses": {
- "description": "Fixed addresses assigned (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
- "type": "array",
- "items": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- },
- "isDynamic": {
- "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
- "type": "boolean"
- },
- "addressRange": {
- "description": "An IP address range used, e.g., in case of egress connections. Exactly one of \"addresses\" or \"addressRange\" shall be present. See note 2.\n",
- "type": "object",
- "required": ["minAddress", "maxAddress"],
- "properties": {
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- },
- "subnetId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- }
- },
- "type": {
- "description": "The type of the IP addresses\n",
- "type": "string",
- "enum": ["PV4", "PV6"]
- },
- "addresses": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "isDynamic": {
- "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
- "type": "boolean"
- },
- "addressRange": {
- "description": "An IP address range used, e.g. in case of egress connections. See note.\n",
- "type": "object",
- "required": ["minAddress", "maxAddress"],
- "properties": {
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- },
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "subnetId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- },
- "virtualCpAddress": {
- "description": "This type represents information about a network address that has been assigned to a virtual CP.\n",
- "type": "object",
- "required": ["type"],
- "properties": {
- "type": {
- "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
- "type": "string",
- "enum": ["IPV4", "IPV6"]
- },
- "loadBalancerIp": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- }
- }
- }
- },
- "associatedVnfcCpIds": {
- "description": "Identifiers of the VnfcCps that share the virtual IP addresse allocated to the VIP CP instance. See note.\n",
- "type": "array",
- "items": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- }
- },
- "vnfLinkPortId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "metadata": {
- "description": "Allows the OSS/BSS to provide additional parameter(s) to the termination process at the NS level.\n",
- "type": "array",
- "items": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- }
+ "virtualCpAddress": {
+ "description": "This type represents information about a network address that has been assigned to a virtual CP.\n",
+ "type": "object",
+ "required": [
+ "type"
+ ],
+ "properties": {
+ "type": {
+ "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
+ },
+ "loadBalancerIp": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.",
+ "type": "string"
}
- },
- "virtualCpInfo": {
- "description": "virtual CPs that are part of the VNF instance. Shall be present when a particular virtual CP is associated to an external CP of the VNF instance. May be present otherwise.\n",
- "type": "array",
- "items": {
- "description": "This type represents the information related to a virtual CP instance of a VNF. NOTE: A consumer of the VNF LCM interface can learn the actual VNFC instances implementing the service accessible via the virtual CP instance by querying the \"vnfcResourceInfo\" from the \"InstantiatedVnfInfo\" and filtering by corresponding \"vduId\" values.",
- "type": "object",
- "required": ["cpInstanceId", "cpdId", "resourceHandle", "vduId"],
- "properties": {
- "cpInstanceId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "cpdId": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "resourceHandle": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes instance the vimLevelResourceType is the type of resource, as would correspond to the kind field if the resource is declared in its own Kubernetes manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the claimName field in the Kubernetes manifest, or a compound name built by Kubernetes if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the metadata.name field in Kubernetes manifest. \n",
- "type": "object",
- "required": ["resourceId"],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
- "type": "string"
- },
- "vimLevelAdditionalResourceInfo": {
- "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
- "type": "object",
- "properties": {
- "hostName": {
- "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "persistentVolume": {
- "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "containerNamespace": {
- "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
- "type": "string"
- }
- }
- },
- "vnfExtCpId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "cpProtocolInfo": {
- "description": "Protocol information for this CP. There shall be one cpProtocolInfo for each layer protocol supported.\n",
- "type": "array",
- "items": {
- "description": "This type describes the protocol layer(s) that a CP or SAP uses together with protocol-related information, like addresses. It shall comply with the provisions defined in Table 6.5.3.58-1. NOTE: This attribute allows to signal the addition of further types of layer and protocol in future versions of the present document in a backwards-compatible way. In the current version of the present document, only IP over Ethernet is supported.\n",
- "type": "object",
- "required": ["layerProtocol", "ipOverEthernet"],
- "properties": {
- "layerProtocol": {
- "description": "The identifier of layer(s) and protocol(s) associated to the network address information. Permitted values: - IP_OVER_ETHERNET\n - IP_FOR_VIRTUAL_CP\nSee note.\n",
- "type": "string",
- "enum": ["IP_OVER_ETHERNET", "IP_FOR_VIRTUAL_CP"]
- },
- "ipOverEthernet": {
- "description": "This type represents information about a network address that has been assigned.\nNOTE 1: At least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2: Exactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3: If the Cp instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4: Depending on the NFVI networking infrastructure, the \"segmentationId\" may indicate the actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header of the packets or it may be an identifier used between the application and the NFVI networking infrastructure to identify the network sub-interface of the trunk port in question. In the latter case the NFVI infrastructure will map this local \"segmentationId\" to whatever \"segmentationId\" is actually used by the NFVI's transport technology.\n",
- "type": "object",
- "anyOf": [{
- "required": ["macAddress"]
- }, {
- "required": ["ipAddresses"]
- }],
- "properties": {
- "macAddress": {
- "description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
- "type": "string",
- "format": "MAC"
- },
- "segmentationId": {
- "description": "Identification of the network segment to which the Cp instance connects to. See note 3 and note 4.\n",
- "type": "string"
- },
- "ipAddresses": {
- "description": "Addresses assigned to the CP instance. Each entry represents IP addresses assigned by fixed or dynamic IP address assignment per subnet. See note 1.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": ["type"],
- "oneOf": [{
- "required": ["addresses"]
- }, {
- "required": ["addressRange"]
- }],
- "properties": {
- "type": {
- "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
- "type": "string",
- "enum": ["IPV4", "IPV6"]
- },
- "addresses": {
- "description": "Fixed addresses assigned (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
- "type": "array",
- "items": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- },
- "isDynamic": {
- "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
- "type": "boolean"
- },
- "addressRange": {
- "description": "An IP address range used, e.g., in case of egress connections. Exactly one of \"addresses\" or \"addressRange\" shall be present. See note 2.\n",
- "type": "object",
- "required": ["minAddress", "maxAddress"],
- "properties": {
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- },
- "subnetId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- }
- },
- "type": {
- "description": "The type of the IP addresses\n",
- "type": "string",
- "enum": ["PV4", "PV6"]
- },
- "addresses": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "isDynamic": {
- "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
- "type": "boolean"
- },
- "addressRange": {
- "description": "An IP address range used, e.g. in case of egress connections. See note.\n",
- "type": "object",
- "required": ["minAddress", "maxAddress"],
- "properties": {
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- },
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "subnetId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- },
- "virtualCpAddress": {
- "description": "This type represents information about a network address that has been assigned to a virtual CP.\n",
- "type": "object",
- "required": ["type"],
- "properties": {
- "type": {
- "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
- "type": "string",
- "enum": ["IPV4", "IPV6"]
- },
- "loadBalancerIp": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- }
- }
- }
- },
- "vduId": {
- "description": "Reference to the VDU(s) which implement the service accessible via the virtual CP instance. See note.\n",
- "type": "array",
- "items": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- }
- },
- "additionalServiceInfo": {
- "description": "Additional service identification information of the virtual CP instance.\n",
- "type": "array",
- "items": {
- "description": "This type represents the additional service information of the virtual CP instance used to expose properties of the virtual CP to NFV-MANO.\nNOTE: This attribute shall only be present if additional information is needed to identify the service termination within the VNF, such as for example a URL path information in an HTTP request required to allow a single virtual CP IP address to be used for several HTTP based services that use the same port number.",
- "type": "object",
- "required": ["portInfo"],
- "properties": {
- "portInfo": {
- "description": "Service port numbers exposed by the virtual CP instance.\n",
- "type": "array",
- "items": {
- "description": "This type represents the information related to the service identifying port properties exposed by the virtual CP instance.",
- "type": "object",
- "required": ["name", "protocol", "port", "isPortConfigurable"],
- "properties": {
- "name": {
- "description": "The name of the port exposed by the virtual CP instance.\n",
- "type": "string"
- },
- "protocol": {
- "description": "The L4 protocol for this port exposed by the virtual CP instance. Permitted values:\n - TCP\n - UDP\n - SCTP\n",
- "type": "string",
- "enum": ["TCP", "UDP", "SCTP"]
- },
- "port": {
- "description": "The L4 port number exposed by the virtual CP instance.\n",
- "type": "integer"
- },
- "isPortConfigurable": {
- "description": "Specifies whether the port attribute value is allowed to be configurable.\n",
- "type": "boolean"
- }
- }
- }
- },
- "serviceInfo": {
- "description": "Service matching information exposed by the virtual CP instance. See note.\n",
- "type": "array",
- "items": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- }
- }
- },
- "metadata": {
- "description": "Metadata about this virtual CP instance.\n",
- "type": "array",
- "items": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- }
+ }
+ }
+ }
+ }
+ },
+ "vduId": {
+ "description": "Reference to the VDU(s) which implement the service accessible via the virtual CP instance. See note.\n",
+ "type": "array",
+ "items": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
+ "type": "string"
+ }
+ },
+ "additionalServiceInfo": {
+ "description": "Additional service identification information of the virtual CP instance.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the additional service information of the virtual CP instance used to expose properties of the virtual CP to NFV-MANO.\nNOTE: This attribute shall only be present if additional information is needed to identify the service termination within the VNF, such as for example a URL path information in an HTTP request required to allow a single virtual CP IP address to be used for several HTTP based services that use the same port number.",
+ "type": "object",
+ "required": [
+ "portInfo"
+ ],
+ "properties": {
+ "portInfo": {
+ "description": "Service port numbers exposed by the virtual CP instance.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the information related to the service identifying port properties exposed by the virtual CP instance.",
+ "type": "object",
+ "required": [
+ "name",
+ "protocol",
+ "port",
+ "isPortConfigurable"
+ ],
+ "properties": {
+ "name": {
+ "description": "The name of the port exposed by the virtual CP instance.\n",
+ "type": "string"
+ },
+ "protocol": {
+ "description": "The L4 protocol for this port exposed by the virtual CP instance.\n Permitted values:\n - TCP\n - UDP\n - SCTP\n",
+ "type": "string",
+ "enum": [
+ "TCP",
+ "UDP",
+ "SCTP"
+ ]
+ },
+ "port": {
+ "description": "The L4 port number exposed by the virtual CP instance.\n",
+ "type": "integer"
+ },
+ "isPortConfigurable": {
+ "description": "Specifies whether the port attribute value is allowed to be configurable.\n",
+ "type": "boolean"
+ }
}
+ }
},
- "extVirtualLinkInfo": {
- "description": "Information about the external VLs the VNF instance is connected to.\n",
- "type": "array",
- "items": {
- "description": "This type represents information about an VNF external VL.",
- "type": "object",
- "required": ["id", "resourceHandle", "currentVnfExtCpData"],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceHandle": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes instance the vimLevelResourceType is the type of resource, as would correspond to the kind field if the resource is declared in its own Kubernetes manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the claimName field in the Kubernetes manifest, or a compound name built by Kubernetes if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the metadata.name field in Kubernetes manifest. \n",
- "type": "object",
- "required": ["resourceId"],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
- "type": "string"
- },
- "vimLevelAdditionalResourceInfo": {
- "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
- "type": "object",
- "properties": {
- "hostName": {
- "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "persistentVolume": {
- "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "containerNamespace": {
- "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
- "type": "string"
- }
- }
- },
- "extLinkPorts": {
- "description": "Link ports of this VL.\n",
- "type": "array",
- "items": {
- "description": "This type represents information about a link port of an external VL, i.e. a port providing connectivity for the VNF to an NS VL. NOTE 1: The use cases UC#4 and UC#5 in Annex A.4 of ETSI GS NFV-IFA 007 provide examples for such a configuration. NOTE 2: The value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\" attribute.\n",
- "type": "object",
- "required": ["id", "resourceHandle"],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceHandle": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes instance the vimLevelResourceType is the type of resource, as would correspond to the kind field if the resource is declared in its own Kubernetes manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the claimName field in the Kubernetes manifest, or a compound name built by Kubernetes if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the metadata.name field in Kubernetes manifest. \n",
- "type": "object",
- "required": ["resourceId"],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
- "type": "string"
- },
- "vimLevelAdditionalResourceInfo": {
- "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
- "type": "object",
- "properties": {
- "hostName": {
- "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "persistentVolume": {
- "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "containerNamespace": {
- "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
- "type": "string"
- }
- }
- },
- "cpInstanceId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "secondaryCpInstanceId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "trunkResourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- }
- },
- "extNetAttDefResource": {
- "description": "Network attachment definition resources that provide the specification of the interface to attach connection points to this VL.\n",
- "type": "array",
- "items": {
- "description": "This type represents the information related to a network attachment definition resource that provides the specification of the interface used to connect one or multiple connection points to a secondary container cluster network\n",
- "type": "object",
- "required": ["netAttDefResourceInfoId", "netAttDefResource"],
- "properties": {
- "netAttDefResourceInfoId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "netAttDefResource": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes instance the vimLevelResourceType is the type of resource, as would correspond to the kind field if the resource is declared in its own Kubernetes manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the claimName field in the Kubernetes manifest, or a compound name built by Kubernetes if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the metadata.name field in Kubernetes manifest. \n",
- "type": "object",
- "required": ["resourceId"],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
- "type": "string"
- },
- "vimLevelAdditionalResourceInfo": {
- "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
- "type": "object",
- "properties": {
- "hostName": {
- "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "persistentVolume": {
- "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "containerNamespace": {
- "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
- "type": "string"
- }
- }
- },
- "associatedExtCpId": {
- "description": "Identifier of the external CP of the VNF associated to this network attachment definition resource. Shall be present when the network attachment definition resource is used for external connectivity by the VNF\n",
- "type": "array",
- "items": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- }
- },
- "associatedVnfcCpId": {
- "description": "Identifier of the VNFC CP of the VNF associated to this network attachment definition resource. May be present when the network attachment definition resource is used for internal connectivity by the VNF.\n",
- "type": "array",
- "items": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- }
- }
- }
- }
- },
- "currentVnfExtCpData": {
- "description": "This type represents configuration information for external CPs created from a CPD.\nNOTE 1: In case this identifier refers to a CPD with trunking enabled, the external CP instances created from this CPD will represent ports in a trunk. NOTE 2: The map entry value shall be set to \"null\" in order to delete a \"VnfExtCpConfig\" entry identified by a particular key value from the map, i.e. for the disconnection of an existing external CP instance addressed by cpInstanceId in the deleted map entry from a particular external virtual link, and deletion of that instance in case it represents a subport. Deleting the last key from the map removes the affected instance of the \"VnfExtCpData\" structure from its parent data structure. NOTE 3: Within one VNF instance, all VNFC instances created from a particular VDU have the same external connectivity. Thus, given a particular value of the \"cpdId' attribute, there shall be one \"cpConfig\" entry for each VNFC instance that has been or can be created from a VDU which includes a CPD identified by the \"cpdId\" attribute. If the cpConfig represents a subport in a trunk, all \"cpConfig\" entries in this list shall have the same segmentationId, which means they are connected to the same set of external VLs via the trunk. NOTE 4: If, as defined by the input parameters of a \"ChangeVnfFlavour\", \"ChangeExtVnfConnectivity\" or \"ChangeCurrentVnfPkg\" operation, a cpConfig map entry identified by a particular map key value is moved into another \"ExtVirtualLinkData\" or \"VnfExtCpData\" structure, this particular cpConfig map entry may be used by an external CP instance different than the one that has used it before the operation, or by no external CP instance at all. Renaming a CPD identifier during the \"changeCurrentVnfPkg\" operation does not count as moving the related \"cpConfig\" map entries to a new \"extCpData\" structure.\n",
- "type": "object",
- "required": ["cpdId"],
- "properties": {
- "cpdId": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "cpConfig": {
- "description": "Map of instance data that need to be configured on the CP instances created from the respective CPD. The key of the map which identifies the individual VnfExtCpConfig entries is of type \"IdentifierInVnf\" and is managed by the API consumer. The entries shall be applied by the VNFM according to the rules of JSON Merge Patch (see IETF RFC 7396 [11]). See notes 2, 3 and 4.\n",
- "type": "object",
- "additionalProperties": {
- "description": "This type represents an externally provided link port, or a network attachment definition resource of secondary container cluster network, or network address information per instance of a VNF external connection point. In the case of VM-based deployment of the VNFC exposing the external CP: In case a link port is provided, the NFVO shall use that link port when connecting the VNF external CP to the external VL. In case a link port is not provided, the NFVO or VNFM shall create a link port on the external VL, and use that link port to connect the VNF external CP to the external VL. In the case of container-based deployment of the VNFC exposing the external CP, the NFVO and VNFM shall use the network attachment definition resource of secondary container cluster network when connecting the CP to the external VL.\nNOTE 1: The following conditions apply to the attributes \"linkPortId\" and \"cpProtocolData\" for an external CP instance connected or to be connected to a virtual network not\n categorized as secondary container cluster network:\n - At least one of the \"linkPortId\" and \"cpProtocolData\" attributes shall be present for\n an external CP instance representing a subport that is to be created, or an external CP instance\n that is to be created by creating the corresponding VNFC or VNF instance during the current or\n a subsequent LCM operation, or for an existing external CP instance that is to be re-configured\n or added to a particular external virtual link.\n - If the \"cpProtocolData\" attribute is absent, the \"linkPortId\" attribute shall be provided\n referencing a pre-created link port with pre-configured address information.\n - If both \"cpProtocolData\" and \"linkportId\" are provided, the API consumer shall ensure that\n the cpProtocolData can be used with the pre-created link port referenced by \"linkPortId\".\nNOTE 2: In case the NFVO manages its own identifier space, the NFVO may remap this identifier when communicating with the VNFM. If the NFVO knows that there can be an identifier collision when communicating with the VNFM by using the identifier from the OSS/BSS, the NFVO shall remap it. NOTE 3: The following conditions apply to the attributes netAttDefResourceId and cpProtocolData for an external CP instance connected or to be connected to a secondary container cluster network; The \"netAttDefResourceId\" and \"cpProtocolData\" attributes shall both be absent for the deletion of an existing external CP instance addressed by \"cpInstanceId\". At least one of these attributes shall be present for a to-be-created external CP instance or an existing external CP instance. NOTE 4: Cardinality greater than 1 is only applicable for specific cases where more than one network attachment definition resource is needed to fulfil the connectivity requirements of the external CP, e.g. to build a link redundant mated pair in SR-IOV cases. When more than one \"netAttDefResourceId\" is indicated, all shall belong to the same namespace as defined by the corresponding \"netAttDefResourceNamespace\" attribute in the \"NetAttDefResourceData\". NOTE 5: Either \"linkPortId\" or \"netAttDefResourceId\" may be included, but not both.\n",
- "type": "object",
- "oneOf": [{
- "required": ["linkPortId"]
- }, {
- "required": ["cpProtocolData"]
- }],
- "properties": {
- "parentCpConfigId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "linkPortId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "createExtLinkPort": {
- "description": "Indicates the need to create a dedicated link port for the external CP. If set to True, a link port is created. If set to False, no link port is created. This attribute is only applicable for external CP instances without a floating IP address that expose a VIP CP instance for which a dedicated IP address is allocated. It shall be present in that case and shall be absent otherwise.\n",
- "type": "boolean"
- },
- "cpProtocolData": {
- "description": "Parameters for configuring the network protocols on the link port that connects the CP to a VL. See notes 1 and 3.\n",
- "type": "array",
- "items": {
- "description": "This type represents network protocol data.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the present document in a backwards-compatible way. In the current version of the present document, only IP over Ethernet is supported.\n",
- "type": "object",
- "required": ["layerProtocol"],
- "properties": {
- "layerProtocol": {
- "description": "Identifier of layer(s) and protocol(s). Permitted values: - IP_OVER_ETHERNET - IP_FOR_VIRTUAL_CP See note.\n",
- "type": "string",
- "enum": ["IP_OVER_ETHERNET", "IP_FOR_VIRTUAL_CP"]
- },
- "ipOverEthernet": {
- "description": "This type represents network address data for IP over Ethernet. NOTE 1: At least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2: Exactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present. NOTE 3: If the CP instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4: Depending on the NFVI networking infrastructure, the \"segmentationId\" may indicate the actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header of the packets or it may be an identifier used between the application and the NFVI networking infrastructure to identify the network sub-interface of the trunk port in question. In the latter case the NFVI infrastructure will map this local \"segmentationId\" to whatever \"segmentationId\" is actually used by the NFVI's transport technology.\n",
- "type": "object",
- "anyOf": [{
- "required": ["ipAddresses"]
- }, {
- "required": ["macAddress"]
- }],
- "properties": {
- "macAddress": {
- "description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
- "type": "string",
- "format": "MAC"
- },
- "segmentationType": {
- "description": "Specifies the encapsulation type for the traffics coming in and out of the trunk subport. Permitted values are: - VLAN: The subport uses VLAN as encapsulation type. - INHERIT: The subport gets its segmentation type from the network it is connected to. This attribute may be present for CP instances that represent subports in a trunk and shall be absent otherwise. If this attribute is not present for a subport CP instance, default value VLAN shall be used.\n",
- "type": "string",
- "enum": ["VLAN", "INHERIT"]
- },
- "segmentationId": {
- "description": "Identification of the network segment to which the CP instance connects to. See note 3 and note 4.\n",
- "type": "string"
- },
- "ipAddresses": {
- "description": "List of IP addresses to assign to the CP instance. Each entry represents IP address data for fixed or dynamic IP address assignment per subnet. If this attribute is not present, no IP address shall be assigned. See note 1.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": ["type"],
- "oneOf": [{
- "required": ["fixedAddresses"]
- }, {
- "required": ["numDynamicAddresses"]
- }, {
- "required": ["addressRange"]
- }],
- "properties": {
- "type": {
- "description": "The type of the IP addresses. Permitted values: - IPV4\n - IPV6\n",
- "type": "string",
- "enum": ["IPV4", "IPV6"]
- },
- "fixedAddresses": {
- "description": "Fixed addresses to assign (from the subnet defined by \"subnetId\" if provided). Exactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present.\n",
- "type": "array",
- "items": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- },
- "numDynamicAddresses": {
- "description": "Number of dynamic addresses to assign (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
- "type": "integer"
- },
- "addressRange": {
- "description": "An IP address range to be used, e.g. in case of egress connections. In case this attribute is present, IP addresses from the range will be used.\n",
- "type": "object",
- "required": ["minAddress", "maxAddress"],
- "properties": {
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- },
- "subnetId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- }
- }
- }
- },
- "virtualCpAddress": {
- "description": "This type represents network address data for a virtual CP. It shall comply with the provisions defined in table 6.5.3.12a-1.\n",
- "type": "object",
- "required": ["type"],
- "properties": {
- "type": {
- "description": "Identifier of layer(s) and protocol(s). Permitted values: IP_OVER_ETHERNET.\n",
- "type": "string",
- "enum": ["IPV4", "IPV6"]
- },
- "loadBalancerIp": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- }
- }
- }
- },
- "netAttDefResourceId": {
- "description": "Identifier of the \"NetAttDefResourceData\" structure that provides the specification of the interface to attach the external CP to a secondary container cluster network. It is only applicable if the external CP is connected or to be connected to a secondary container cluster network. It shall not be present if the external CP is related to a virtual network not categorized as secondary container cluster network. See notes 3, 4 and 5.\n",
- "type": "array",
- "items": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- }
- }
- }
- }
- }
- }
- }
- }
- }
+ "serviceInfo": {
+ "description": "Service matching information exposed by the virtual CP instance. See note.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ }
+ }
+ },
+ "metadata": {
+ "description": "Metadata about this virtual CP instance.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ }
+ }
+ },
+ "extVirtualLinkInfo": {
+ "description": "Information about the external VLs the VNF instance is connected to.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents information about an VNF external VL.",
+ "type": "object",
+ "required": [
+ "id",
+ "resourceHandle",
+ "currentVnfExtCpData"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceHandle": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would correspond to the ‘kind’ field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the ‘claimName’ field in the Kubernetes® manifest, or a compound name built by Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the ‘metadata.name’ field in Kubernetes® manifest. \n",
+ "type": "object",
+ "required": [
+ "resourceId"
+ ],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceProviderId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "type": "string"
+ },
+ "vimLevelAdditionalResourceInfo": {
+ "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
+ "type": "object",
+ "properties": {
+ "hostName": {
+ "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "persistentVolume": {
+ "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ },
+ "containerNamespace": {
+ "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise. \n",
+ "type": "string"
+ }
+ }
+ },
+ "extLinkPorts": {
+ "description": "Link ports of this VL.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents information about a link port of an external VL, i.e. a port providing connectivity for the VNF to an NS VL. NOTE 1: The use cases UC#4 and UC#5 in Annex A.4 of ETSI GS NFV-IFA 007 provide examples for such a configuration. NOTE 2: The value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\" attribute.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "resourceHandle"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
},
- "extManagedVirtualLinkInfo": {
- "description": "Information about the externally-managed internal VLs of the VNF instance. See note 4 and note 5.\n",
- "type": "array",
- "items": {
- "description": "This type provides information about an externally-managed internal virtual link for VNFs\n",
- "type": "object",
- "required": ["id", "vnfVirtualLinkDescId", "networkResource"],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfVirtualLinkDescId": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "networkResource": {
- "description": "Reference to the VirtualNetwork resource or multi-site connectivity service providing this VL.\n",
- "type": "array",
- "items": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes instance the vimLevelResourceType is the type of resource, as would correspond to the kind field if the resource is declared in its own Kubernetes manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the claimName field in the Kubernetes manifest, or a compound name built by Kubernetes if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the metadata.name field in Kubernetes manifest. \n",
- "type": "object",
- "required": ["resourceId"],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
- "type": "string"
- },
- "vimLevelAdditionalResourceInfo": {
- "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
- "type": "object",
- "properties": {
- "hostName": {
- "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "persistentVolume": {
- "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "containerNamespace": {
- "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
- "type": "string"
- }
- }
- }
- },
- "vnfLinkPorts": {
- "description": "Link ports of this VL.\n",
- "type": "array",
- "items": {
- "type": "object",
- "description": "This type represents a link port of an internal VL of a VNF. It shall comply with the provisions defined in table 6.5.3.64-1.\nNOTE 1: Either cpInstanceId with cpInstanceType set to \"EXT_CP\" or any combination of cpInstanceId with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId (i.e. one or both of them) shall be present for a VnfLinkPortInfo. In case both cpInstanceId with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId are present, the two different CP instances share the linkport.\n",
- "required": ["id", "resourceHandle"],
- "properties": {
- "id": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "resourceHandle": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes instance the vimLevelResourceType is the type of resource, as would correspond to the kind field if the resource is declared in its own Kubernetes manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the claimName field in the Kubernetes manifest, or a compound name built by Kubernetes if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the metadata.name field in Kubernetes manifest. \n",
- "type": "object",
- "required": ["resourceId"],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
- "type": "string"
- },
- "vimLevelAdditionalResourceInfo": {
- "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
- "type": "object",
- "properties": {
- "hostName": {
- "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "persistentVolume": {
- "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "containerNamespace": {
- "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
- "type": "string"
- }
- }
- },
- "cpInstanceId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "cpInstanceType": {
- "description": "Type of the CP instance that is identified by cpInstanceId. Shall be present if \"cpInstanceId\" is present, and shall be absent otherwise. Permitted values: * VNFC_CP: The link port is connected to a VNFC CP * EXT_CP: The link port is associated to an external CP. See note 1.\n",
- "type": "string",
- "enum": ["VNFC_CP", "EXT_CP"]
- },
- "vipCpInstanceId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "trunkResourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- }
- },
- "vnfNetAttDefResource": {
- "description": "This type represents the information related to a network attachment definition resource that provides the specification of the interface used to connect one or multiple connection points to a secondary container cluster network\n",
- "type": "object",
- "required": ["netAttDefResourceInfoId", "netAttDefResource"],
- "properties": {
- "netAttDefResourceInfoId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "netAttDefResource": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes instance the vimLevelResourceType is the type of resource, as would correspond to the kind field if the resource is declared in its own Kubernetes manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the claimName field in the Kubernetes manifest, or a compound name built by Kubernetes if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the metadata.name field in Kubernetes manifest. \n",
- "type": "object",
- "required": ["resourceId"],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
- "type": "string"
- },
- "vimLevelAdditionalResourceInfo": {
- "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
- "type": "object",
- "properties": {
- "hostName": {
- "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "persistentVolume": {
- "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "containerNamespace": {
- "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
- "type": "string"
- }
- }
- },
- "associatedExtCpId": {
- "description": "Identifier of the external CP of the VNF associated to this network attachment definition resource. Shall be present when the network attachment definition resource is used for external connectivity by the VNF\n",
- "type": "array",
- "items": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- }
- },
- "associatedVnfcCpId": {
- "description": "Identifier of the VNFC CP of the VNF associated to this network attachment definition resource. May be present when the network attachment definition resource is used for internal connectivity by the VNF.\n",
- "type": "array",
- "items": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- }
- }
- }
- },
- "extManagedMultisiteVirtualLinkId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- }
+ "resourceHandle": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would correspond to the ‘kind’ field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the ‘claimName’ field in the Kubernetes® manifest, or a compound name built by Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the ‘metadata.name’ field in Kubernetes® manifest. \n",
+ "type": "object",
+ "required": [
+ "resourceId"
+ ],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceProviderId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "type": "string"
+ },
+ "vimLevelAdditionalResourceInfo": {
+ "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
+ "type": "object",
+ "properties": {
+ "hostName": {
+ "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "persistentVolume": {
+ "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
}
+ }
+ },
+ "containerNamespace": {
+ "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise. \n",
+ "type": "string"
}
+ }
},
- "monitoringParameters": {
- "description": "Performance metrics tracked by the VNFM (e.g. for auto-scaling purposes) as identified by the VNF provider in the VNFD.\n",
- "type": "array",
- "items": {
- "description": "This type represents a monitoring parameter that is tracked by the VNFM, for example, for auto-scaling purposes. It shall comply with the provisions defined in Table 6.5.3.69-1.\n",
- "type": "object",
- "required": ["id", "performanceMetric"],
- "properties": {
- "id": {
- "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "name": {
- "description": "Human readable name of the monitoring parameter, as defined in the VNFD.\n",
- "type": "string"
- },
- "performanceMetric": {
- "description": "Performance metric that is monitored. This attribute shall contain the related \"Measurement Name\" value as defined in clause 7.2 of ETSI GS NFV-IFA 027.\n",
- "type": "string"
- }
+ "cpInstanceId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "secondaryCpInstanceId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "trunkResourceId": {
+ "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "extNetAttDefResource": {
+ "description": "Network attachment definition resources that provide the specification of the interface to attach connection points to this VL.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the information related to a network attachment definition resource that provides the specification of the interface used to connect one or multiple connection points to a secondary container cluster network\n",
+ "type": "object",
+ "required": [
+ "netAttDefResourceInfoId",
+ "netAttDefResource"
+ ],
+ "properties": {
+ "netAttDefResourceInfoId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "netAttDefResource": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would correspond to the ‘kind’ field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the ‘claimName’ field in the Kubernetes® manifest, or a compound name built by Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the ‘metadata.name’ field in Kubernetes® manifest. \n",
+ "type": "object",
+ "required": [
+ "resourceId"
+ ],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceProviderId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "type": "string"
+ },
+ "vimLevelAdditionalResourceInfo": {
+ "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
+ "type": "object",
+ "properties": {
+ "hostName": {
+ "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "persistentVolume": {
+ "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
}
+ }
+ },
+ "containerNamespace": {
+ "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise. \n",
+ "type": "string"
}
+ }
},
- "localizationLanguage": {
- "description": "Information about localization language of the VNF (includes e.g. strings in the VNFD). The localization languages supported by a VNF can be declared in the VNFD, and localization language selection can take place at instantiation time. The value shall comply with the format defined in IETF RFC 5646.\n",
+ "associatedExtCpId": {
+ "description": "Identifier of the external CP of the VNF associated to this network attachment definition resource. Shall be present when the network attachment definition resource is used for external connectivity by the VNF\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
"type": "string"
+ }
},
- "vnfcResourceInfo": {
- "description": "Information about the virtualised compute and storage resources used by the VNFCs of the VNF instance.\n",
- "type": "array",
- "items": {
- "description": "This type represents the information on virtualised compute and storage resources used by a VNFC in a VNF instance. This feature addresses the following capabilities: NFV Architecture support for VNFs which follow cloud-native design principles. Enhance NFV-MANO capabilities to support container technologies. Enhance NFV-MANO capabilities for container management and orchestration. Enhance information model for containerized VNFs both using bare metal or nested virtualization technologies.\nNOTE 1: ETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on TOSCA specifications. NOTE 2: A VNFC CP is \"connected to\" an external CP if the VNFC CP is connected to an internal VL that exposes an external CP. A VNFC CP is \"exposed as\" an external CP if it is connected directly to an external VL. NOTE 3: The information can be omitted because it is already available as part of the external CP information. NOTE 4: Cardinality greater than 1 is only applicable for specific cases where more than one network attachment definition resource is needed to fulfil the connectivity requirements of the internal CP, e.g. to build a link redundant mated pair in SR-IOV cases. NOTE 5: When more than one \"netAttDefResourceId\" is indicated, all shall belong to the same namespace.\n",
+ "associatedVnfcCpId": {
+ "description": "Identifier of the VNFC CP of the VNF associated to this network attachment definition resource. May be present when the network attachment definition resource is used for internal connectivity by the VNF.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ }
+ }
+ }
+ }
+ },
+ "currentVnfExtCpData": {
+ "description": "This type represents configuration information for external CPs created from a CPD.\nNOTE 1: In case this identifier refers to a CPD with trunking enabled, the external CP instances created from this CPD will represent ports in a trunk. NOTE 2: The map entry value shall be set to \"null\" in order to delete a \"VnfExtCpConfig\" entry identified by a particular key value from the map, i.e. for the disconnection of an existing external CP instance addressed by cpInstanceId in the deleted map entry from a particular external virtual link, and deletion of that instance in case it represents a subport. Deleting the last key from the map removes the affected instance of the \"VnfExtCpData\" structure from its parent data structure. NOTE 3: Within one VNF instance, all VNFC instances created from a particular VDU have the same external connectivity. Thus, given a particular value of the \"cpdId' attribute, there shall be one \"cpConfig\" entry for each VNFC instance that has been or can be created from a VDU which includes a CPD identified by the \"cpdId\" attribute. If the cpConfig represents a subport in a trunk, all \"cpConfig\" entries in this list shall have the same segmentationId, which means they are connected to the same set of external VLs via the trunk. NOTE 4: If, as defined by the input parameters of a \"ChangeVnfFlavour\", \"ChangeExtVnfConnectivity\" or \"ChangeCurrentVnfPkg\" operation, a cpConfig map entry identified by a particular map key value is moved into another \"ExtVirtualLinkData\" or \"VnfExtCpData\" structure, this particular cpConfig map entry may be used by an external CP instance different than the one that has used it before the operation, or by no external CP instance at all. Renaming a CPD identifier during the \"changeCurrentVnfPkg\" operation does not count as moving the related \"cpConfig\" map entries to a new \"extCpData\" structure.\n",
+ "type": "object",
+ "required": [
+ "cpdId"
+ ],
+ "properties": {
+ "cpdId": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
+ "type": "string"
+ },
+ "cpConfig": {
+ "description": "Map of instance data that need to be configured on the CP instances created from the respective CPD. The key of the map which identifies the individual VnfExtCpConfig entries is of type \"IdentifierInVnf\" and is managed by the API consumer. The entries shall be applied by the VNFM according to the rules of JSON Merge Patch (see IETF RFC 7396 [11]). See notes 2, 3 and 4.\n",
+ "type": "object",
+ "additionalProperties": {
+ "description": "This type represents an externally provided link port, or a network attachment definition resource of secondary container cluster network, or network address information per instance of a VNF external connection point. In the case of VM-based deployment of the VNFC exposing the external CP: In case a link port is provided, the NFVO shall use that link port when connecting the VNF external CP to the external VL. • In case a link port is not provided, the NFVO or VNFM shall create a link port on the external VL, and use that link port to connect the VNF external CP to the external VL. In the case of container-based deployment of the VNFC exposing the external CP, the NFVO and VNFM shall use the network attachment definition resource of secondary container cluster network when connecting the CP to the external VL.\nNOTE 1: The following conditions apply to the attributes \"linkPortId\" and \"cpProtocolData\"\n for an external CP instance connected or to be connected to a virtual network not\n categorized as secondary container cluster network:\n - At least one of the \"linkPortId\" and \"cpProtocolData\" attributes shall be present for\n an external CP instance representing a subport that is to be created, or an external CP instance\n that is to be created by creating the corresponding VNFC or VNF instance during the current or\n a subsequent LCM operation, or for an existing external CP instance that is to be re-configured\n or added to a particular external virtual link.\n - If the \"cpProtocolData\" attribute is absent, the \"linkPortId\" attribute shall be provided\n referencing a pre-created link port with pre-configured address information.\n - If both \"cpProtocolData\" and \"linkportId\" are provided, the API consumer shall ensure that\n the cpProtocolData can be used with the pre-created link port referenced by \"linkPortId\".\nNOTE 2: In case the NFVO manages its own identifier space, the NFVO may remap this identifier\n when communicating with the VNFM. If the NFVO knows that there can be an identifier collision\n when communicating with the VNFM by using the identifier from the OSS/BSS, the NFVO shall remap it.\nNOTE 3: The following conditions apply to the attributes \"netAttDefResourceId\" and \"cpProtocolData\" for an external CP\n instance connected or to be connected to a secondary container cluster network:\n − Void.\n − At least one of these attributes shall be present for a to-be-created external CP instance or an existing\n external CP instance.\nNOTE 4: Cardinality greater than 1 is only applicable for specific cases where more than one network\n attachment definition resource is needed to fulfil the connectivity requirements of the external CP,\n e.g. to build a link redundant mated pair in SR-IOV cases. When more than one \"netAttDefResourceId\"\n is indicated, all shall belong to the same namespace as defined by the corresponding \n \"containerNamespace\" attribute in the \"resourceHandle\" attribute in the \"NetAttDefResourceData\".\nNOTE 5: Either \"linkPortId\" or \"netAttDefResourceId\" may be included, but not both.\n",
+ "type": "object",
+ "oneOf": [
+ {
+ "required": [
+ "linkPortId"
+ ]
+ },
+ {
+ "required": [
+ "cpProtocolData"
+ ]
+ }
+ ],
+ "properties": {
+ "parentCpConfigId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "linkPortId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "createExtLinkPort": {
+ "description": "Indicates the need to create a dedicated link port for the external CP. If set to True, a link port is created. If set to False, no link port is created. This attribute is only applicable for external CP instances without a floating IP address that expose a VIP CP instance for which a dedicated IP address is allocated. It shall be present in that case and shall be absent otherwise.\n",
+ "type": "boolean"
+ },
+ "cpProtocolData": {
+ "description": "Parameters for configuring the network protocols on the link port that connects the CP to a VL. See notes 1 and 3.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents network protocol data.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the present document in a backwards-compatible way. In the current version of the present document, only IP over Ethernet is supported.\n",
"type": "object",
- "required": ["id", "vduId", "computeResource"],
+ "required": [
+ "layerProtocol"
+ ],
"properties": {
- "id": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vduId": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "computeResource": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes instance the vimLevelResourceType is the type of resource, as would correspond to the kind field if the resource is declared in its own Kubernetes manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the claimName field in the Kubernetes manifest, or a compound name built by Kubernetes if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the metadata.name field in Kubernetes manifest. \n",
- "type": "object",
- "required": ["resourceId"],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
- "type": "string"
- },
- "vimLevelAdditionalResourceInfo": {
- "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
- "type": "object",
- "properties": {
- "hostName": {
- "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "persistentVolume": {
- "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "containerNamespace": {
- "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
- "type": "string"
- }
- }
- },
- "storageResourceIds": {
- "description": "References to the VirtualStorage resources or references to Storage MCIOs. The value refers to a VirtualStorageResourceInfo item in the VnfInstance.\n",
- "type": "array",
- "items": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- }
- },
- "reservationId": {
- "description": "An identifier with the intention of being globally unique.\n",
+ "layerProtocol": {
+ "description": "Identifier of layer(s) and protocol(s). Permitted values: - IP_OVER_ETHERNET - IP_FOR_VIRTUAL_CP See note.\n",
+ "type": "string",
+ "enum": [
+ "IP_OVER_ETHERNET",
+ "IP_FOR_VIRTUAL_CP"
+ ]
+ },
+ "ipOverEthernet": {
+ "description": "This type represents network address data for IP over Ethernet. NOTE 1: At least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2: Exactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present. NOTE 3: If the CP instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4: Depending on the NFVI networking infrastructure, the \"segmentationId\" may indicate the actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header of the packets or it may be an identifier used between the application and the NFVI networking infrastructure to identify the network sub-interface of the trunk port in question. In the latter case the NFVI infrastructure will map this local \"segmentationId\" to whatever \"segmentationId\" is actually used by the NFVI's transport technology.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "required": [
+ "ipAddresses"
+ ]
+ },
+ {
+ "required": [
+ "macAddress"
+ ]
+ }
+ ],
+ "properties": {
+ "macAddress": {
+ "description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
+ "type": "string",
+ "format": "MAC"
+ },
+ "segmentationType": {
+ "description": "Specifies the encapsulation type for the traffics coming in and out of the trunk subport. Permitted values are: - VLAN: The subport uses VLAN as encapsulation type. - INHERIT: The subport gets its segmentation type from the network it is connected to. This attribute may be present for CP instances that represent subports in a trunk and shall be absent otherwise. If this attribute is not present for a subport CP instance, default value VLAN shall be used.\n",
+ "type": "string",
+ "enum": [
+ "VLAN",
+ "INHERIT"
+ ]
+ },
+ "segmentationId": {
+ "description": "Identification of the network segment to which the CP instance connects to. See note 3 and note 4.\n",
"type": "string"
- },
- "vnfcCpInfo": {
- "description": "CPs of the VNFC instance. Shall be present when that particular CP of the VNFC instance is exposed as an external CP of the VNF instance or is connected to an external CP of the VNF instance.See note 2. May be present otherwise.\n",
+ },
+ "ipAddresses": {
+ "description": "List of IP addresses to assign to the CP instance. Each entry represents IP address data for fixed or dynamic IP address assignment per subnet. If this attribute is not present, no IP address shall be assigned. See note 1.\n",
"type": "array",
"items": {
- "type": "object",
- "required": ["id", "cpdId"],
- "properties": {
- "id": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "cpdId": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "vnfExtCpId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "cpProtocolInfo": {
- "description": "Network protocol information for this CP. May be omitted if the VNFC CP is exposed as an external CP. See note 3.\n",
- "type": "array",
- "items": {
- "description": "This type describes the protocol layer(s) that a CP or SAP uses together with protocol-related information, like addresses. It shall comply with the provisions defined in Table 6.5.3.58-1. NOTE: This attribute allows to signal the addition of further types of layer and protocol in future versions of the present document in a backwards-compatible way. In the current version of the present document, only IP over Ethernet is supported.\n",
- "type": "object",
- "required": ["layerProtocol", "ipOverEthernet"],
- "properties": {
- "layerProtocol": {
- "description": "The identifier of layer(s) and protocol(s) associated to the network address information. Permitted values: - IP_OVER_ETHERNET\n - IP_FOR_VIRTUAL_CP\nSee note.\n",
- "type": "string",
- "enum": ["IP_OVER_ETHERNET", "IP_FOR_VIRTUAL_CP"]
- },
- "ipOverEthernet": {
- "description": "This type represents information about a network address that has been assigned.\nNOTE 1: At least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2: Exactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3: If the Cp instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4: Depending on the NFVI networking infrastructure, the \"segmentationId\" may indicate the actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header of the packets or it may be an identifier used between the application and the NFVI networking infrastructure to identify the network sub-interface of the trunk port in question. In the latter case the NFVI infrastructure will map this local \"segmentationId\" to whatever \"segmentationId\" is actually used by the NFVI's transport technology.\n",
- "type": "object",
- "anyOf": [{
- "required": ["macAddress"]
- }, {
- "required": ["ipAddresses"]
- }],
- "properties": {
- "macAddress": {
- "description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
- "type": "string",
- "format": "MAC"
- },
- "segmentationId": {
- "description": "Identification of the network segment to which the Cp instance connects to. See note 3 and note 4.\n",
- "type": "string"
- },
- "ipAddresses": {
- "description": "Addresses assigned to the CP instance. Each entry represents IP addresses assigned by fixed or dynamic IP address assignment per subnet. See note 1.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": ["type"],
- "oneOf": [{
- "required": ["addresses"]
- }, {
- "required": ["addressRange"]
- }],
- "properties": {
- "type": {
- "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
- "type": "string",
- "enum": ["IPV4", "IPV6"]
- },
- "addresses": {
- "description": "Fixed addresses assigned (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
- "type": "array",
- "items": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- },
- "isDynamic": {
- "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
- "type": "boolean"
- },
- "addressRange": {
- "description": "An IP address range used, e.g., in case of egress connections. Exactly one of \"addresses\" or \"addressRange\" shall be present. See note 2.\n",
- "type": "object",
- "required": ["minAddress", "maxAddress"],
- "properties": {
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- },
- "subnetId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- }
- },
- "type": {
- "description": "The type of the IP addresses\n",
- "type": "string",
- "enum": ["PV4", "PV6"]
- },
- "addresses": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "isDynamic": {
- "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
- "type": "boolean"
- },
- "addressRange": {
- "description": "An IP address range used, e.g. in case of egress connections. See note.\n",
- "type": "object",
- "required": ["minAddress", "maxAddress"],
- "properties": {
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- },
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "subnetId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- },
- "virtualCpAddress": {
- "description": "This type represents information about a network address that has been assigned to a virtual CP.\n",
- "type": "object",
- "required": ["type"],
- "properties": {
- "type": {
- "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
- "type": "string",
- "enum": ["IPV4", "IPV6"]
- },
- "loadBalancerIp": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- }
- }
- }
- },
- "parentCpId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "vnfLinkPortId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "netAttDefResourceId": {
- "description": "Identifier of the \"NetAttDefResourceInfo\" structure that provides the specification of the interface to attach the connection point to a secondary container cluster network. See notes 4 and 5. It shall be present if the internal CP is associated to a VNFC realized by one or a set of OS containers and is connected to a secondary container cluster network. It shall not be present otherwise.\n",
- "type": "array",
- "items": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- }
- },
- "metadata": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- }
- },
- "metadata": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- }
- },
- "vnfVirtualLinkResourceInfo": {
- "description": "Information about the virtualised network resources used by the VLs of the VNF instance. See note 5.\n",
- "type": "array",
- "items": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by an internal VL instance in a VNF instance.\n",
- "type": "object",
- "required": ["id", "vnfVirtualLinkDescId", "networkResource"],
- "properties": {
- "id": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfVirtualLinkDescId": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "networkResource": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes instance the vimLevelResourceType is the type of resource, as would correspond to the kind field if the resource is declared in its own Kubernetes manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the claimName field in the Kubernetes manifest, or a compound name built by Kubernetes if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the metadata.name field in Kubernetes manifest. \n",
- "type": "object",
- "required": ["resourceId"],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
+ "type": "object",
+ "required": [
+ "type"
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "fixedAddresses"
+ ]
},
- "vimLevelResourceType": {
- "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
- "type": "string"
+ {
+ "required": [
+ "numDynamicAddresses"
+ ]
},
- "vimLevelAdditionalResourceInfo": {
- "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
- "type": "object",
- "properties": {
- "hostName": {
- "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "persistentVolume": {
- "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "containerNamespace": {
- "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
- "type": "string"
+ {
+ "required": [
+ "addressRange"
+ ]
}
- }
- },
- "reservationId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfLinkPorts": {
- "description": "Links ports of this VL. Shall be present when the linkPort is used for external connectivity by the VNF (refer to VnfLinkPortInfo). May be present otherwise.\n",
- "type": "array",
- "items": {
- "type": "object",
- "description": "This type represents a link port of an internal VL of a VNF. It shall comply with the provisions defined in table 6.5.3.64-1.\nNOTE 1: Either cpInstanceId with cpInstanceType set to \"EXT_CP\" or any combination of cpInstanceId with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId (i.e. one or both of them) shall be present for a VnfLinkPortInfo. In case both cpInstanceId with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId are present, the two different CP instances share the linkport.\n",
- "required": ["id", "resourceHandle"],
- "properties": {
- "id": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "resourceHandle": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes instance the vimLevelResourceType is the type of resource, as would correspond to the kind field if the resource is declared in its own Kubernetes manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the claimName field in the Kubernetes manifest, or a compound name built by Kubernetes if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the metadata.name field in Kubernetes manifest. \n",
- "type": "object",
- "required": ["resourceId"],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
- "type": "string"
- },
- "vimLevelAdditionalResourceInfo": {
- "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
- "type": "object",
- "properties": {
- "hostName": {
- "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "persistentVolume": {
- "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "containerNamespace": {
- "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
- "type": "string"
- }
- }
- },
- "cpInstanceId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "cpInstanceType": {
- "description": "Type of the CP instance that is identified by cpInstanceId. Shall be present if \"cpInstanceId\" is present, and shall be absent otherwise. Permitted values: * VNFC_CP: The link port is connected to a VNFC CP * EXT_CP: The link port is associated to an external CP. See note 1.\n",
- "type": "string",
- "enum": ["VNFC_CP", "EXT_CP"]
- },
- "vipCpInstanceId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "trunkResourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- }
- },
- "metadata": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- }
- },
- "virtualStorageResourceInfo": {
- "description": "Information on the virtualised storage resource(s) used as storage for the VNF instance.\n",
- "type": "array",
- "items": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance.\n",
- "type": "object",
- "required": ["id", "virtualStorageDescId", "storageResource"],
- "properties": {
- "id": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "virtualStorageDescId": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "storageResource": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes instance the vimLevelResourceType is the type of resource, as would correspond to the kind field if the resource is declared in its own Kubernetes manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the claimName field in the Kubernetes manifest, or a compound name built by Kubernetes if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the metadata.name field in Kubernetes manifest. \n",
- "type": "object",
- "required": ["resourceId"],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
+ ],
+ "properties": {
+ "type": {
+ "description": "The type of the IP addresses. Permitted values:\n - IPV4\n - IPV6\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
},
- "resourceId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
+ "fixedAddresses": {
+ "description": "Fixed addresses to assign (from the subnet defined by \"subnetId\" if provided). Exactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present.\n",
+ "type": "array",
+ "items": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ }
},
- "vimLevelResourceType": {
- "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
- "type": "string"
+ "numDynamicAddresses": {
+ "description": "Number of dynamic addresses to assign (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
+ "type": "integer"
},
- "vimLevelAdditionalResourceInfo": {
- "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
- "type": "object",
- "properties": {
- "hostName": {
- "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "persistentVolume": {
- "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
+ "addressRange": {
+ "description": "An IP address range to be used, e.g. in case of egress connections. In case this attribute is present, IP addresses from the range will be used.\n",
+ "type": "object",
+ "required": [
+ "minAddress",
+ "maxAddress"
+ ],
+ "properties": {
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
}
+ }
},
- "containerNamespace": {
- "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
- "type": "string"
+ "subnetId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
}
+ }
}
- },
- "reservationId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "metadata": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
+ }
}
- }
- }
- },
- "mcioInfo": {
- "description": "Information on the MCIO(s) representing VNFC instance(s) realized by one or a set of OS containers and created from the same VDU for the VNF instance.\n",
- "type": "array",
- "items": {
- "description": "This type provides information about an MCIO representing the set of VNFC instances realized by one or a set of OS containers which have been created based on the same VDU.\nNOTE 1 The type of MCIO as specified in the declarative descriptor of the MCIO, and that can be read from the CISM. EXAMPLE: In case of MCIOs managed by Kubernetes, the type of MCIO corresponds to the kind property of the declarative descriptor. NOTE 2 If the attribute additionalInfo is present, it may contain runtime information on the actual and desired state of the MCIO(s). NOTE 3 When the container infrastructure service is a Kubernetes instance, the mcioId is the combined values from the kind and name fields of the Kubernetes resource object, separated by a slash. Example: \"Deployment/abcd\". NOTE 4 When the container infrastructure service is a Kubernetes instance, the mcioName is the name field of the resource object.",
- "type": "object",
- "required": ["mcioId", "mcioName", "mcioNamespace", "vduId", "cismId", "mcioType", "desiredInstances", "availableInstances"],
- "properties": {
- "mcioId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "mcioName": {
- "description": "Human readable name of this MCIO. See note 4.\n",
- "type": "string"
- },
- "mcioNamespace": {
- "description": "Namespace of this MCIO.\n",
- "type": "string"
- },
- "vduId": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "cismId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "mcioType": {
- "description": "The type of MCIO. Specific values, their semantics and associated MCIO types are defined in clause 6.5.4.13. Additional values are also permitted. See note 1.\n",
- "type": "string"
- },
- "desiredInstances": {
- "description": "Number of desired MCIO instances.\n",
- "type": "integer"
- },
- "availableInstances": {
- "description": "Number of available MCIO instances\n",
- "type": "integer"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
+ },
+ "virtualCpAddress": {
+ "description": "This type represents network address data for a virtual CP. It shall comply with the provisions defined in table 6.5.3.12a-1.\nNOTE 1: If the container cluster is set up to be able to configure an external load balancer this address will be\n used, otherwise it will be ignored by the CISM.\nNOTE 2: In case the cluster can configure an external load balancer but no loadBalancerIp is provided the\n container cluster will assign an IP address.\nNOTE 3: The attribute is only relevant if the virtual CP is instantiated in a cluster that supports configuration of IP\n address pools for virtual CPs. Otherwise it shall be ignored. MetalLB is an example of a solution for\n Kubernetes® that supports configuration of address pools for load balancer services.\nNOTE 4: The loadBalancerIp and the addressPoolName attributes shall not be present at the same time.\n",
+ "type": "object",
+ "required": [
+ "type"
+ ],
+ "properties": {
+ "type": {
+ "description": "Identifier of layer(s) and protocol(s). Permitted values: IP_OVER_ETHERNET.\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
+ },
+ "loadBalancerIp": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which the container cluster will assign an IP address to the virtual CP. See notes 3 and 4.\n",
+ "type": "array",
+ "items": {
+ "type": "string"
+ }
+ }
}
+ }
}
+ }
+ },
+ "netAttDefResourceId": {
+ "description": "Identifier of the \"NetAttDefResourceData\" structure that provides the specification of the interface to attach the external CP to a secondary container cluster network. It is only applicable if the external CP is connected or to be connected to a secondary container cluster network. It shall not be present if the external CP is related to a virtual network not categorized as secondary container cluster network. See notes 3, 4 and 5.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ }
}
+ }
}
+ }
}
- },
- "metadata": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- },
- "extensions": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
+ }
}
- }
- }
- },
- "pnfInfo": {
- "description": "Information on the PNF(s) that are part of the NS instance.\n",
- "type": "array",
- "items": {
- "description": "This type represents the information about a PNF that is part of an NS instance. It shall comply with the provisions defined in Table 6.5.3.13-1.\n",
- "type": "object",
- "required": ["pnfId", "pnfdId", "pnfdInfoId", "pnfProfileId"],
- "properties": {
- "pnfId": {
+ }
+ },
+ "extManagedVirtualLinkInfo": {
+ "description": "Information about the externally-managed internal VLs of the VNF instance. See note 4 and note 5.\n",
+ "type": "array",
+ "items": {
+ "description": "This type provides information about an externally-managed internal virtual link for VNFs\n",
+ "type": "object",
+ "required": [
+ "id",
+ "vnfVirtualLinkDescId",
+ "networkResource"
+ ],
+ "properties": {
+ "id": {
"description": "An identifier with the intention of being globally unique.\n",
"type": "string"
- },
- "pnfName": {
- "description": "Name of the PNF.\n",
- "type": "string"
- },
- "pnfdId": {
+ },
+ "vnfdId": {
"description": "An identifier with the intention of being globally unique.\n",
"type": "string"
- },
- "versionDependency": {
- "description": "Describes version dependencies currently valid for the PNF. Identifies versions of descriptors of other constituents in the NSD upon which the PNF depends. The dependencies may be described for the PNFD referenced in this PnfInfo with pnfdId and for PNFDs with the same PnfdExtInvariantId. There shall not be more than one versionDependency present with the same dependentConstituentId.\n",
+ },
+ "vnfVirtualLinkDescId": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
+ "type": "string"
+ },
+ "networkResource": {
+ "description": "Reference to the VirtualNetwork resource or multi-site connectivity service providing this VL.\n",
"type": "array",
"items": {
- "description": "This type represents the information related to all dependencies that an NSD constituent has on the versions of other NSD constituents. It shall comply with the provisions defined in table 6.5.3.112-1.\n",
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would correspond to the ‘kind’ field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the ‘claimName’ field in the Kubernetes® manifest, or a compound name built by Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the ‘metadata.name’ field in Kubernetes® manifest. \n",
+ "type": "object",
+ "required": [
+ "resourceId"
+ ],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceProviderId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "type": "string"
+ },
+ "vimLevelAdditionalResourceInfo": {
+ "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
+ "type": "object",
+ "properties": {
+ "hostName": {
+ "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "persistentVolume": {
+ "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ },
+ "containerNamespace": {
+ "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise. \n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "vnfLinkPorts": {
+ "description": "Link ports of this VL.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "description": "This type represents a link port of an internal VL of a VNF. It shall comply with the provisions defined in table 6.5.3.64-1.\nNOTE 1: Either cpInstanceId with cpInstanceType set to \"EXT_CP\" or any combination of cpInstanceId with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId (i.e. one or both of them) shall be present for a VnfLinkPortInfo. In case both cpInstanceId with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId are present, the two different CP instances share the linkport.\n",
+ "required": [
+ "id",
+ "resourceHandle"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "resourceHandle": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would correspond to the ‘kind’ field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the ‘claimName’ field in the Kubernetes® manifest, or a compound name built by Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the ‘metadata.name’ field in Kubernetes® manifest. \n",
+ "type": "object",
+ "required": [
+ "resourceId"
+ ],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceProviderId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "type": "string"
+ },
+ "vimLevelAdditionalResourceInfo": {
+ "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
+ "type": "object",
+ "properties": {
+ "hostName": {
+ "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "persistentVolume": {
+ "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ },
+ "containerNamespace": {
+ "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise. \n",
+ "type": "string"
+ }
+ }
+ },
+ "cpInstanceId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "cpInstanceType": {
+ "description": "Type of the CP instance that is identified by cpInstanceId. Shall be present if \"cpInstanceId\" is present, and shall be absent otherwise. Permitted values: * VNFC_CP: The link port is connected to a VNFC CP * EXT_CP: The link port is associated to an external CP. See note 1.\n",
+ "type": "string",
+ "enum": [
+ "VNFC_CP",
+ "EXT_CP"
+ ]
+ },
+ "vipCpInstanceId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "trunkResourceId": {
+ "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "vnfNetAttDefResource": {
+ "description": "This type represents the information related to a network attachment definition resource that provides the specification of the interface used to connect one or multiple connection points to a secondary container cluster network\n",
+ "type": "object",
+ "required": [
+ "netAttDefResourceInfoId",
+ "netAttDefResource"
+ ],
+ "properties": {
+ "netAttDefResourceInfoId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "netAttDefResource": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would correspond to the ‘kind’ field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the ‘claimName’ field in the Kubernetes® manifest, or a compound name built by Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the ‘metadata.name’ field in Kubernetes® manifest. \n",
"type": "object",
- "required": ["dependentConstituentId"],
+ "required": [
+ "resourceId"
+ ],
"properties": {
- "dependentConstituentId": {
- "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceProviderId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "type": "string"
+ },
+ "vimLevelAdditionalResourceInfo": {
+ "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
+ "type": "object",
+ "properties": {
+ "hostName": {
+ "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note. \n",
"type": "string"
- },
- "versionDependencyStatement": {
- "description": "Identifies one or multiple versions of an NSD constituents upon which the dependent constituent identified by dependentConstituentId has a dependency. Cardinality 0 is used to remove an existing version dependency in a profile.\n",
- "type": "array",
- "items": {
- "description": "This type represents the information related to one or more VNF, NS or PNF descriptor identifiers which describe one single dependency. When more than one descriptor is indicated, they correspond to different versions of the same VNF, NS or PNF and they represent alternatives to fulfil the dependency. It shall comply with the provisions defined in table 6.5.3.113-1.\n",
- "type": "object",
- "required": ["descriptorId"],
- "properties": {
- "descriptorId": {
- "description": "Identifies a VNFD, NSD or PNFD upon which the entity using this information element depends. When more than one descriptor is indicated, they shall correspond to versions of the same VNF, NS or PNF and they represent. alternatives, i.e. the presence of one of them fulfills the dependency.",
- "type": "array",
- "items": {
- "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- }
- }
+ },
+ "persistentVolume": {
+ "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
}
+ },
+ "containerNamespace": {
+ "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise. \n",
+ "type": "string"
+ }
}
+ },
+ "associatedExtCpId": {
+ "description": "Identifier of the external CP of the VNF associated to this network attachment definition resource. Shall be present when the network attachment definition resource is used for external connectivity by the VNF\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ }
+ },
+ "associatedVnfcCpId": {
+ "description": "Identifier of the VNFC CP of the VNF associated to this network attachment definition resource. May be present when the network attachment definition resource is used for internal connectivity by the VNF.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ }
+ }
}
- },
- "pnfdInfoId": {
+ },
+ "extManagedMultisiteVirtualLinkId": {
"description": "An identifier with the intention of being globally unique.\n",
"type": "string"
- },
- "pnfProfileId": {
+ }
+ }
+ }
+ },
+ "monitoringParameters": {
+ "description": "Performance metrics tracked by the VNFM (e.g. for auto-scaling purposes) as identified by the VNF provider in the VNFD.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents a monitoring parameter that is tracked by the VNFM, for example, for auto-scaling purposes. It shall comply with the provisions defined in Table 6.5.3.69-1.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "performanceMetric"
+ ],
+ "properties": {
+ "id": {
"description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
"type": "string"
- },
- "cpInfo": {
- "description": "This type represents the information about the external CP of the PNF. It shall comply with the provisions defined in Table 6.5.3.17-1.\n",
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "name": {
+ "description": "Human readable name of the monitoring parameter, as defined in the VNFD.\n",
+ "type": "string"
+ },
+ "performanceMetric": {
+ "description": "Performance metric that is monitored. This attribute shall contain the related \"Measurement Name\" value as defined in clause 7.2 of ETSI GS NFV-IFA 027.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "localizationLanguage": {
+ "description": "Information about localization language of the VNF (includes e.g. strings in the VNFD). The localization languages supported by a VNF can be declared in the VNFD, and localization language selection can take place at instantiation time. The value shall comply with the format defined in IETF RFC 5646.\n",
+ "type": "string"
+ },
+ "vnfcResourceInfo": {
+ "description": "Information about the virtualised compute and storage resources used by the VNFCs of the VNF instance.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the information on virtualised compute and storage resources used by a VNFC in a VNF instance. This feature addresses the following capabilities: • NFV Architecture support for VNFs which follow “cloud-native” design principles. • Enhance NFV-MANO capabilities to support container technologies. • Enhance NFV-MANO capabilities for container management and orchestration. • Enhance information model for containerized VNFs both using bare metal or nested virtualization technologies.\nNOTE 1: ETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on TOSCA specifications. NOTE 2: A VNFC CP is \"connected to\" an external CP if the VNFC CP is connected to an internal VL that exposes an external CP. A VNFC CP is \"exposed as\" an external CP if it is connected directly to an external VL. NOTE 3: The information can be omitted because it is already available as part of the external CP information. NOTE 4: Cardinality greater than 1 is only applicable for specific cases where more than one network attachment definition resource is needed to fulfil the connectivity requirements of the internal CP, e.g. to build a link redundant mated pair in SR-IOV cases. NOTE 5: When more than one \"netAttDefResourceId\" is indicated, all shall belong to the same namespace.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "vduId",
+ "computeResource"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vduId": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
+ "type": "string"
+ },
+ "computeResource": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would correspond to the ‘kind’ field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the ‘claimName’ field in the Kubernetes® manifest, or a compound name built by Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the ‘metadata.name’ field in Kubernetes® manifest. \n",
"type": "object",
- "required": ["cpInstanceId", "cpdId"],
+ "required": [
+ "resourceId"
+ ],
"properties": {
- "cpInstanceId": {
- "description": "An Identifier that is unique within respect to a PNF. Representation: string of variable length.\n",
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceProviderId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "type": "string"
+ },
+ "vimLevelAdditionalResourceInfo": {
+ "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
+ "type": "object",
+ "properties": {
+ "hostName": {
+ "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note. \n",
"type": "string"
+ },
+ "persistentVolume": {
+ "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ },
+ "containerNamespace": {
+ "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise. \n",
+ "type": "string"
+ }
+ }
+ },
+ "storageResourceIds": {
+ "description": "References to the VirtualStorage resources or references to Storage MCIOs. The value refers to a VirtualStorageResourceInfo item in the VnfInstance.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ }
+ },
+ "reservationId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfcCpInfo": {
+ "description": "CPs of the VNFC instance. Shall be present when that particular CP of the VNFC instance is exposed as an external CP of the VNF instance or is connected to an external CP of the VNF instance.See note 2. May be present otherwise.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": [
+ "id",
+ "cpdId"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
},
"cpdId": {
- "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
- "type": "string"
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
+ "type": "string"
},
- "cpProtocolData": {
- "description": "Parameters for configuring the network protocols on the CP.\n",
- "type": "array",
- "items": {
- "description": "This type represents network protocol data.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the present document in a backwards-compatible way. In the current version of the present document, only IP over Ethernet is supported.\n",
+ "vnfExtCpId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "cpProtocolInfo": {
+ "description": "Network protocol information for this CP. May be omitted if the VNFC CP is exposed as an external CP. See note 3.\n",
+ "type": "array",
+ "items": {
+ "description": "This type describes the protocol layer(s) that a CP or SAP uses together with protocol-related information, like addresses. It shall comply with the provisions defined in Table 6.5.3.58-1. NOTE: This attribute allows to signal the addition of further types of layer and protocol in future versions of the present document in a backwards-compatible way. In the current version of the present document, only IP over Ethernet is supported.\n",
+ "type": "object",
+ "required": [
+ "layerProtocol",
+ "ipOverEthernet"
+ ],
+ "properties": {
+ "layerProtocol": {
+ "description": "The identifier of layer(s) and protocol(s) associated to the network address information. Permitted values:\n - IP_OVER_ETHERNET\n - IP_FOR_VIRTUAL_CP\nSee note.\n",
+ "type": "string",
+ "enum": [
+ "IP_OVER_ETHERNET",
+ "IP_FOR_VIRTUAL_CP"
+ ]
+ },
+ "ipOverEthernet": {
+ "description": "This type represents information about a network address that has been assigned.\nNOTE 1: At least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2: Exactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3: If the Cp instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4: Depending on the NFVI networking infrastructure, the \"segmentationId\" may indicate the actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header of the packets or it may be an identifier used between the application and the NFVI networking infrastructure to identify the network sub-interface of the trunk port in question. In the latter case the NFVI infrastructure will map this local \"segmentationId\" to whatever \"segmentationId\" is actually used by the NFVI's transport technology.\n",
"type": "object",
- "required": ["layerProtocol"],
+ "anyOf": [
+ {
+ "required": [
+ "macAddress"
+ ]
+ },
+ {
+ "required": [
+ "ipAddresses"
+ ]
+ }
+ ],
"properties": {
- "layerProtocol": {
- "description": "Identifier of layer(s) and protocol(s). Permitted values: - IP_OVER_ETHERNET - IP_FOR_VIRTUAL_CP See note.\n",
- "type": "string",
- "enum": ["IP_OVER_ETHERNET", "IP_FOR_VIRTUAL_CP"]
- },
- "ipOverEthernet": {
- "description": "This type represents network address data for IP over Ethernet. NOTE 1: At least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2: Exactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present. NOTE 3: If the CP instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4: Depending on the NFVI networking infrastructure, the \"segmentationId\" may indicate the actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header of the packets or it may be an identifier used between the application and the NFVI networking infrastructure to identify the network sub-interface of the trunk port in question. In the latter case the NFVI infrastructure will map this local \"segmentationId\" to whatever \"segmentationId\" is actually used by the NFVI's transport technology.\n",
- "type": "object",
- "anyOf": [{
- "required": ["ipAddresses"]
- }, {
- "required": ["macAddress"]
- }],
- "properties": {
- "macAddress": {
- "description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
- "type": "string",
- "format": "MAC"
- },
- "segmentationType": {
- "description": "Specifies the encapsulation type for the traffics coming in and out of the trunk subport. Permitted values are: - VLAN: The subport uses VLAN as encapsulation type. - INHERIT: The subport gets its segmentation type from the network it is connected to. This attribute may be present for CP instances that represent subports in a trunk and shall be absent otherwise. If this attribute is not present for a subport CP instance, default value VLAN shall be used.\n",
- "type": "string",
- "enum": ["VLAN", "INHERIT"]
- },
- "segmentationId": {
- "description": "Identification of the network segment to which the CP instance connects to. See note 3 and note 4.\n",
- "type": "string"
- },
- "ipAddresses": {
- "description": "List of IP addresses to assign to the CP instance. Each entry represents IP address data for fixed or dynamic IP address assignment per subnet. If this attribute is not present, no IP address shall be assigned. See note 1.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": ["type"],
- "oneOf": [{
- "required": ["fixedAddresses"]
- }, {
- "required": ["numDynamicAddresses"]
- }, {
- "required": ["addressRange"]
- }],
- "properties": {
- "type": {
- "description": "The type of the IP addresses. Permitted values: - IPV4\n - IPV6\n",
- "type": "string",
- "enum": ["IPV4", "IPV6"]
- },
- "fixedAddresses": {
- "description": "Fixed addresses to assign (from the subnet defined by \"subnetId\" if provided). Exactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present.\n",
- "type": "array",
- "items": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- },
- "numDynamicAddresses": {
- "description": "Number of dynamic addresses to assign (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
- "type": "integer"
- },
- "addressRange": {
- "description": "An IP address range to be used, e.g. in case of egress connections. In case this attribute is present, IP addresses from the range will be used.\n",
- "type": "object",
- "required": ["minAddress", "maxAddress"],
- "properties": {
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- },
- "subnetId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- }
- }
+ "macAddress": {
+ "description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
+ "type": "string",
+ "format": "MAC"
+ },
+ "segmentationId": {
+ "description": "Identification of the network segment to which the Cp instance connects to. See note 3 and note 4.\n",
+ "type": "string"
+ },
+ "ipAddresses": {
+ "description": "Addresses assigned to the CP instance. Each entry represents IP addresses assigned by fixed or dynamic IP address assignment per subnet. See note 1.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": [
+ "type"
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "addresses"
+ ]
+ },
+ {
+ "required": [
+ "addressRange"
+ ]
}
- },
- "virtualCpAddress": {
- "description": "This type represents network address data for a virtual CP. It shall comply with the provisions defined in table 6.5.3.12a-1.\n",
- "type": "object",
- "required": ["type"],
- "properties": {
- "type": {
- "description": "Identifier of layer(s) and protocol(s). Permitted values: IP_OVER_ETHERNET.\n",
- "type": "string",
- "enum": ["IPV4", "IPV6"]
+ ],
+ "properties": {
+ "type": {
+ "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
+ },
+ "addresses": {
+ "description": "Fixed addresses assigned (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
+ "type": "array",
+ "items": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ }
+ },
+ "isDynamic": {
+ "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
+ "type": "boolean"
+ },
+ "addressRange": {
+ "description": "An IP address range used, e.g., in case of egress connections. Exactly one of \"addresses\" or \"addressRange\" shall be present. See note 2.\n",
+ "type": "object",
+ "required": [
+ "minAddress",
+ "maxAddress"
+ ],
+ "properties": {
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
},
- "loadBalancerIp": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
}
+ }
+ },
+ "subnetId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
}
+ }
+ }
+ },
+ "type": {
+ "description": "The type of the IP addresses\n",
+ "type": "string",
+ "enum": [
+ "PV4",
+ "PV6"
+ ]
+ },
+ "addresses": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "isDynamic": {
+ "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
+ "type": "boolean"
+ },
+ "addressRange": {
+ "description": "An IP address range used, e.g. in case of egress connections. See note.\n",
+ "type": "object",
+ "required": [
+ "minAddress",
+ "maxAddress"
+ ],
+ "properties": {
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ }
}
+ },
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "subnetId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ }
+ }
+ },
+ "virtualCpAddress": {
+ "description": "This type represents information about a network address that has been assigned to a virtual CP.\n",
+ "type": "object",
+ "required": [
+ "type"
+ ],
+ "properties": {
+ "type": {
+ "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
+ },
+ "loadBalancerIp": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.",
+ "type": "string"
+ }
}
+ }
}
+ }
+ },
+ "parentCpId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "vnfLinkPortId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "netAttDefResourceId": {
+ "description": "Identifier of the \"NetAttDefResourceInfo\" structure that provides the specification of the interface to attach the connection point to a secondary container cluster network. See notes 4 and 5. It shall be present if the internal CP is associated to a VNFC realized by one or a set of OS containers and is connected to a secondary container cluster network. It shall not be present otherwise.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ }
+ },
+ "metadata": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
}
+ }
}
+ },
+ "metadata": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
}
- }
- }
- },
- "virtualLinkInfo": {
- "description": "Information on the VL(s) of the NS instance. This attribute shall be present if the nsState attribute value is INSTANTIATED and if the NS instance has specified connectivity.\n",
- "type": "array",
- "items": {
- "description": "This type specifies the information about an NS VL instance. It shall comply with the provisions defined in Table 6.5.3.53-1.\nNOTE: As an NS can include NFs deployed in NFVI PoPs under the control of several different VIMs, therefore deploying an NS VL can involve several VIMs, each allocating different virtualised network resources, as well as WIMs handling the connectivity in between the NFVI-PoPs in the form of multi-site connectivity services. When this NsVirtualLink is provided as an ExtVirtualLink as input of a VNF LCM operation, the id of the ExtVirtualLink shall be the same as the corresponding NsVirtualLink.\n",
- "type": "object",
- "required": ["id", "nsVirtualLinkDescId", "nsVirtualLinkProfileId"],
- "properties": {
- "id": {
- "description": "An identifier that is unique with respect to a NS. Representation: string of variable length.\n",
+ }
+ },
+ "vnfVirtualLinkResourceInfo": {
+ "description": "Information about the virtualised network resources used by the VLs of the VNF instance. See note 5.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by an internal VL instance in a VNF instance.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "vnfVirtualLinkDescId",
+ "networkResource"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
"type": "string"
- },
- "nsVirtualLinkDescId": {
- "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
"type": "string"
- },
- "nsVirtualLinkProfileId": {
- "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
+ },
+ "vnfVirtualLinkDescId": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
"type": "string"
- },
- "resourceHandle": {
- "description": "Identifier(s) of the virtualised network resource(s) and/or multi-site connectivity service(s) realizing the VL instance. See note.\n",
- "type": "array",
- "items": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes instance the vimLevelResourceType is the type of resource, as would correspond to the kind field if the resource is declared in its own Kubernetes manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the claimName field in the Kubernetes manifest, or a compound name built by Kubernetes if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the metadata.name field in Kubernetes manifest. \n",
+ },
+ "networkResource": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would correspond to the ‘kind’ field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the ‘claimName’ field in the Kubernetes® manifest, or a compound name built by Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the ‘metadata.name’ field in Kubernetes® manifest. \n",
+ "type": "object",
+ "required": [
+ "resourceId"
+ ],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceProviderId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "type": "string"
+ },
+ "vimLevelAdditionalResourceInfo": {
+ "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
"type": "object",
- "required": ["resourceId"],
"properties": {
+ "hostName": {
+ "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "persistentVolume": {
+ "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ },
+ "containerNamespace": {
+ "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise. \n",
+ "type": "string"
+ }
+ }
+ },
+ "reservationId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfLinkPorts": {
+ "description": "Links ports of this VL. Shall be present when the linkPort is used for external connectivity by the VNF (refer to VnfLinkPortInfo). May be present otherwise.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "description": "This type represents a link port of an internal VL of a VNF. It shall comply with the provisions defined in table 6.5.3.64-1.\nNOTE 1: Either cpInstanceId with cpInstanceType set to \"EXT_CP\" or any combination of cpInstanceId with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId (i.e. one or both of them) shall be present for a VnfLinkPortInfo. In case both cpInstanceId with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId are present, the two different CP instances share the linkport.\n",
+ "required": [
+ "id",
+ "resourceHandle"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "resourceHandle": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would correspond to the ‘kind’ field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the ‘claimName’ field in the Kubernetes® manifest, or a compound name built by Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the ‘metadata.name’ field in Kubernetes® manifest. \n",
+ "type": "object",
+ "required": [
+ "resourceId"
+ ],
+ "properties": {
"vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
},
"resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
},
"resourceId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
},
"vimLevelResourceType": {
- "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
- "type": "string"
+ "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "type": "string"
},
"vimLevelAdditionalResourceInfo": {
- "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
- "type": "object",
- "properties": {
- "hostName": {
- "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "persistentVolume": {
- "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
+ "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
+ "type": "object",
+ "properties": {
+ "hostName": {
+ "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "persistentVolume": {
+ "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
}
+ }
},
"containerNamespace": {
- "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
- "type": "string"
+ "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise. \n",
+ "type": "string"
}
+ }
+ },
+ "cpInstanceId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "cpInstanceType": {
+ "description": "Type of the CP instance that is identified by cpInstanceId. Shall be present if \"cpInstanceId\" is present, and shall be absent otherwise. Permitted values: * VNFC_CP: The link port is connected to a VNFC CP * EXT_CP: The link port is associated to an external CP. See note 1.\n",
+ "type": "string",
+ "enum": [
+ "VNFC_CP",
+ "EXT_CP"
+ ]
+ },
+ "vipCpInstanceId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "trunkResourceId": {
+ "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
}
+ }
}
- },
- "linkPort": {
- "description": "Link ports of the VL instance. Cardinality of zero indicates that no port has yet been created for the VL instance.\n",
- "type": "array",
- "items": {
- "description": "This type represents information about a link port of a VL instance. It shall comply with the provisions defined in Table 6.5.3.55-1. NOTE: When the NsVirtualLink, from which the present NsLinkPort is part of, is provided as an ExtVirtualLink as input of a VNF LCM operation, the id of the ExtLinkPort shall be the same as the corresponding NsLinkPort.\n",
+ },
+ "metadata": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ }
+ },
+ "virtualStorageResourceInfo": {
+ "description": "Information on the virtualised storage resource(s) used as storage for the VNF instance.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "virtualStorageDescId",
+ "storageResource"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "virtualStorageDescId": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "storageResource": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would correspond to the ‘kind’ field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the ‘claimName’ field in the Kubernetes® manifest, or a compound name built by Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the ‘metadata.name’ field in Kubernetes® manifest. \n",
+ "type": "object",
+ "required": [
+ "resourceId"
+ ],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceProviderId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "type": "string"
+ },
+ "vimLevelAdditionalResourceInfo": {
+ "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
"type": "object",
- "required": ["id", "resourceHandle"],
"properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceHandle": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes instance the vimLevelResourceType is the type of resource, as would correspond to the kind field if the resource is declared in its own Kubernetes manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the claimName field in the Kubernetes manifest, or a compound name built by Kubernetes if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the metadata.name field in Kubernetes manifest. \n",
- "type": "object",
- "required": ["resourceId"],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
- "type": "string"
- },
- "vimLevelAdditionalResourceInfo": {
- "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
- "type": "object",
- "properties": {
- "hostName": {
- "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "persistentVolume": {
- "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "containerNamespace": {
- "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
- "type": "string"
- }
- }
- },
- "nsCpHandle": {
- "description": "This type represents an identifier of the CP or SAP instance. It shall comply with the provisions defined in Table 6.5.3.56-1. NOTE 1: For the VNF external CP instance, both vnfInstanceId and vnfExtCpInstanceId shall be present as a pair. NOTE 2: For the PNF external CP instance, both pnfInfoId and PnfExtCpInstanceId shall be present as a pair. NOTE 3: For the SAP instance, both nsInstanceId and nsSapInstanceId shall be present as a pair. NOTE 4: One pair of identifiers (VNF external CP, PNF external CP or SAP) shall be present.\n",
- "type": "object",
- "oneOf": [{
- "required": ["vnfInstanceId", "vnfExtCpInstanceId"]
- }, {
- "required": ["pnfInfoId", "pnfExtCpInstanceId"]
- }, {
- "required": ["nsInstanceId", "nsSapInstanceId"]
- }],
- "properties": {
- "vnfInstanceId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfExtCpInstanceId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "pnfInfoId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "pnfExtCpInstanceId": {
- "description": "An Identifier that is unique within respect to a PNF. Representation: string of variable length.\n",
- "type": "string"
- },
- "nsInstanceId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "nsSapInstanceId": {
- "description": "An identifier that is unique with respect to a NS. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- }
+ "hostName": {
+ "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "persistentVolume": {
+ "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
}
+ },
+ "containerNamespace": {
+ "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise. \n",
+ "type": "string"
+ }
}
+ },
+ "reservationId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "metadata": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ }
+ },
+ "mcioInfo": {
+ "description": "Information on the MCIO(s) representing VNFC instance(s) realized by one or a set of OS containers and created from the same VDU for the VNF instance.\n",
+ "type": "array",
+ "items": {
+ "description": "This type provides information about an MCIO representing the set of VNFC instances realized by one or a set of OS containers which have been created based on the same VDU.\nNOTE 1 The type of MCIO as specified in the declarative descriptor of the MCIO, and that can be read from the CISM. EXAMPLE: In case of MCIOs managed by Kubernetes, the type of MCIO corresponds to the “kind” property of the declarative descriptor. NOTE 2 If the attribute additionalInfo is present, it may contain runtime information on the actual and desired state of the MCIO(s). NOTE 3 When the container infrastructure service is a Kubernetes® instance, the mcioId is the combined values from the kind and name fields of the Kubernetes® resource object, separated by a slash. Example: \"Deployment/abcd\". NOTE 4 When the container infrastructure service is a Kubernetes® instance, the mcioName is the name field of the resource object.",
+ "type": "object",
+ "required": [
+ "mcioId",
+ "mcioName",
+ "mcioNamespace",
+ "vduId",
+ "cismId",
+ "mcioType",
+ "desiredInstances",
+ "availableInstances"
+ ],
+ "properties": {
+ "mcioId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "mcioName": {
+ "description": "Human readable name of this MCIO. See note 4. \n",
+ "type": "string"
+ },
+ "mcioNamespace": {
+ "description": "Namespace of this MCIO.\n",
+ "type": "string"
+ },
+ "vduId": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
+ "type": "string"
+ },
+ "cismId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "mcioType": {
+ "description": "The type of MCIO. Specific values, their semantics and associated MCIO types are defined in clause 6.5.4.13. Additional values are also permitted. See note 1.\n",
+ "type": "string"
+ },
+ "desiredInstances": {
+ "description": "Number of desired MCIO instances.\n",
+ "type": "integer"
+ },
+ "availableInstances": {
+ "description": "Number of available MCIO instances\n",
+ "type": "integer"
+ },
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
}
+ }
}
+ }
+ },
+ "metadata": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ },
+ "extensions": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
}
- },
- "vnffgInfo": {
- "description": "Information on the VNFFG(s) of the NS instance.\n",
- "type": "array",
- "items": {
- "description": "Information on the VNFFG(s) of the NS instance. NOTE: It indicates an exhaustive list of all the CP instances and SAP instances of the VNFFG.\n",
+ }
+ }
+ },
+ "pnfInfo": {
+ "description": "Information on the PNF(s) that are part of the NS instance.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the information about a PNF that is part of an NS instance. It shall comply with the provisions defined in Table 6.5.3.13-1.\n",
+ "type": "object",
+ "required": [
+ "pnfId",
+ "pnfdId",
+ "pnfdInfoId",
+ "pnfProfileId"
+ ],
+ "properties": {
+ "pnfId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "pnfName": {
+ "description": "Name of the PNF.\n",
+ "type": "string"
+ },
+ "pnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "versionDependency": {
+ "description": "Describes version dependencies currently valid for the PNF. Identifies versions of descriptors of other constituents in the NSD upon which the PNF depends. The dependencies may be described for the PNFD referenced in this PnfInfo with pnfdId and for PNFDs with the same \"pnfdExtInvariantId\". There shall not be more than one versionDependency present with the same dependentConstituentId.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the information related to all dependencies that an NSD constituent has on the versions of other NSD constituents. It shall comply with the provisions defined in table 6.5.3.112-1.\n",
"type": "object",
- "required": ["id", "vnffgdId", "vnfInstanceId", "pnfInfoId"],
+ "required": [
+ "dependentConstituentId"
+ ],
"properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnffgdId": {
- "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
- "type": "string"
- },
- "vnfInstanceId": {
- "description": "Identifier(s) of the constituent VNF instance(s) of this VNFFG instance.\n",
- "type": "array",
- "items": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- }
- },
- "pnfdInfoId": {
- "description": "Identifier(s) of the constituent PNF instance(s) of this VNFFG instance.\n",
- "type": "array",
- "items": {
- "description": "An identifier with the intention of being globally unique.\n",
+ "dependentConstituentId": {
+ "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "versionDependencyStatement": {
+ "description": "Identifies one or multiple versions of an NSD constituents upon which the dependent constituent identified by dependentConstituentId has a dependency. Cardinality 0 is used to remove an existing version dependency in a profile.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the information related to one or more VNF, NS or PNF descriptor identifiers which describe one single dependency. When more than one descriptor is indicated, they correspond to different versions of the same VNF, NS or PNF and they represent alternatives to fulfil the dependency. It shall comply with the provisions defined in table 6.5.3.113-1.\n",
+ "type": "object",
+ "required": [
+ "descriptorId"
+ ],
+ "properties": {
+ "descriptorId": {
+ "description": "Identifies a VNFD, NSD or PNFD upon which the entity using this data type depends. When more than one descriptor is indicated, they shall correspond to versions of the same VNF, NS or PNF and they represent alternatives, i.e. the presence of one of them fulfills the dependency.",
+ "type": "array",
+ "items": {
+ "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
"type": "string"
+ }
}
- },
- "nsVirtualLinkInfoId": {
- "description": "Identifier(s) of the constituent VL instance(s) of this VNFFG instance.\n",
- "type": "array",
- "items": {
- "description": "An identifier that is unique with respect to a NS. Representation: string of variable length.\n",
+ }
+ }
+ }
+ }
+ }
+ },
+ "pnfdInfoId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "pnfProfileId": {
+ "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "cpInfo": {
+ "description": "This type represents the information about the external CP of the PNF. It shall comply with the provisions defined in Table 6.5.3.17-1.\n",
+ "type": "object",
+ "required": [
+ "cpInstanceId",
+ "cpdId"
+ ],
+ "properties": {
+ "cpInstanceId": {
+ "description": "An Identifier that is unique within respect to a PNF. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "cpdId": {
+ "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "cpProtocolData": {
+ "description": "Parameters for configuring the network protocols on the CP.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents network protocol data.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the present document in a backwards-compatible way. In the current version of the present document, only IP over Ethernet is supported.\n",
+ "type": "object",
+ "required": [
+ "layerProtocol"
+ ],
+ "properties": {
+ "layerProtocol": {
+ "description": "Identifier of layer(s) and protocol(s). Permitted values: - IP_OVER_ETHERNET - IP_FOR_VIRTUAL_CP See note.\n",
+ "type": "string",
+ "enum": [
+ "IP_OVER_ETHERNET",
+ "IP_FOR_VIRTUAL_CP"
+ ]
+ },
+ "ipOverEthernet": {
+ "description": "This type represents network address data for IP over Ethernet. NOTE 1: At least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2: Exactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present. NOTE 3: If the CP instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4: Depending on the NFVI networking infrastructure, the \"segmentationId\" may indicate the actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header of the packets or it may be an identifier used between the application and the NFVI networking infrastructure to identify the network sub-interface of the trunk port in question. In the latter case the NFVI infrastructure will map this local \"segmentationId\" to whatever \"segmentationId\" is actually used by the NFVI's transport technology.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "required": [
+ "ipAddresses"
+ ]
+ },
+ {
+ "required": [
+ "macAddress"
+ ]
+ }
+ ],
+ "properties": {
+ "macAddress": {
+ "description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
+ "type": "string",
+ "format": "MAC"
+ },
+ "segmentationType": {
+ "description": "Specifies the encapsulation type for the traffics coming in and out of the trunk subport. Permitted values are: - VLAN: The subport uses VLAN as encapsulation type. - INHERIT: The subport gets its segmentation type from the network it is connected to. This attribute may be present for CP instances that represent subports in a trunk and shall be absent otherwise. If this attribute is not present for a subport CP instance, default value VLAN shall be used.\n",
+ "type": "string",
+ "enum": [
+ "VLAN",
+ "INHERIT"
+ ]
+ },
+ "segmentationId": {
+ "description": "Identification of the network segment to which the CP instance connects to. See note 3 and note 4.\n",
"type": "string"
+ },
+ "ipAddresses": {
+ "description": "List of IP addresses to assign to the CP instance. Each entry represents IP address data for fixed or dynamic IP address assignment per subnet. If this attribute is not present, no IP address shall be assigned. See note 1.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": [
+ "type"
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "fixedAddresses"
+ ]
+ },
+ {
+ "required": [
+ "numDynamicAddresses"
+ ]
+ },
+ {
+ "required": [
+ "addressRange"
+ ]
+ }
+ ],
+ "properties": {
+ "type": {
+ "description": "The type of the IP addresses. Permitted values:\n - IPV4\n - IPV6\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
+ },
+ "fixedAddresses": {
+ "description": "Fixed addresses to assign (from the subnet defined by \"subnetId\" if provided). Exactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present.\n",
+ "type": "array",
+ "items": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ }
+ },
+ "numDynamicAddresses": {
+ "description": "Number of dynamic addresses to assign (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
+ "type": "integer"
+ },
+ "addressRange": {
+ "description": "An IP address range to be used, e.g. in case of egress connections. In case this attribute is present, IP addresses from the range will be used.\n",
+ "type": "object",
+ "required": [
+ "minAddress",
+ "maxAddress"
+ ],
+ "properties": {
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ }
+ }
+ },
+ "subnetId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ }
+ }
+ }
+ }
}
- },
- "nsCpHandle": {
- "description": "This type represents an identifier of the CP or SAP instance. It shall comply with the provisions defined in Table 6.5.3.56-1. NOTE 1: For the VNF external CP instance, both vnfInstanceId and vnfExtCpInstanceId shall be present as a pair. NOTE 2: For the PNF external CP instance, both pnfInfoId and PnfExtCpInstanceId shall be present as a pair. NOTE 3: For the SAP instance, both nsInstanceId and nsSapInstanceId shall be present as a pair. NOTE 4: One pair of identifiers (VNF external CP, PNF external CP or SAP) shall be present.\n",
+ },
+ "virtualCpAddress": {
+ "description": "This type represents network address data for a virtual CP. It shall comply with the provisions defined in table 6.5.3.12a-1.\nNOTE 1: If the container cluster is set up to be able to configure an external load balancer this address will be\n used, otherwise it will be ignored by the CISM.\nNOTE 2: In case the cluster can configure an external load balancer but no loadBalancerIp is provided the\n container cluster will assign an IP address.\nNOTE 3: The attribute is only relevant if the virtual CP is instantiated in a cluster that supports configuration of IP\n address pools for virtual CPs. Otherwise it shall be ignored. MetalLB is an example of a solution for\n Kubernetes® that supports configuration of address pools for load balancer services.\nNOTE 4: The loadBalancerIp and the addressPoolName attributes shall not be present at the same time.\n",
"type": "object",
- "oneOf": [{
- "required": ["vnfInstanceId", "vnfExtCpInstanceId"]
- }, {
- "required": ["pnfInfoId", "pnfExtCpInstanceId"]
- }, {
- "required": ["nsInstanceId", "nsSapInstanceId"]
- }],
+ "required": [
+ "type"
+ ],
"properties": {
- "vnfInstanceId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfExtCpInstanceId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "pnfInfoId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "pnfExtCpInstanceId": {
- "description": "An Identifier that is unique within respect to a PNF. Representation: string of variable length.\n",
- "type": "string"
- },
- "nsInstanceId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "nsSapInstanceId": {
- "description": "An identifier that is unique with respect to a NS. Representation: string of variable length.\n",
- "type": "string"
+ "type": {
+ "description": "Identifier of layer(s) and protocol(s). Permitted values: IP_OVER_ETHERNET.\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
+ },
+ "loadBalancerIp": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which the container cluster will assign an IP address to the virtual CP. See notes 3 and 4.\n",
+ "type": "array",
+ "items": {
+ "type": "string"
}
+ }
}
+ }
}
+ }
}
+ }
}
- },
- "sapInfo": {
- "description": "Information on the SAP(s) of the NS instance.\n",
- "type": "array",
- "items": {
- "description": "This type represents an SAP instance. It shall comply with the provisions defined in Table 6.5.3.67-1.\n",
+ }
+ }
+ },
+ "virtualLinkInfo": {
+ "description": "Information on the VL(s) of the NS instance. This attribute shall be present if the nsState attribute value is INSTANTIATED and if the NS instance has specified connectivity.\n",
+ "type": "array",
+ "items": {
+ "description": "This type specifies the information about an NS VL instance. It shall comply with the provisions defined in Table 6.5.3.53-1.\nNOTE: As an NS can include NFs deployed in NFVI PoPs under the control of several different VIMs, therefore deploying an NS VL can involve several VIMs, each allocating different virtualised network resources, as well as WIMs handling the connectivity in between the NFVI-PoPs in the form of multi-site connectivity services. When this NsVirtualLink is provided as an ExtVirtualLink as input of a VNF LCM operation, the id of the ExtVirtualLink shall be the same as the corresponding NsVirtualLink.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "nsVirtualLinkDescId",
+ "nsVirtualLinkProfileId"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier that is unique with respect to a NS. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "nsVirtualLinkDescId": {
+ "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "nsVirtualLinkProfileId": {
+ "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "resourceHandle": {
+ "description": "Identifier(s) of the virtualised network resource(s) and/or multi-site connectivity service(s) realizing the VL instance. See note.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would correspond to the ‘kind’ field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the ‘claimName’ field in the Kubernetes® manifest, or a compound name built by Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the ‘metadata.name’ field in Kubernetes® manifest. \n",
"type": "object",
- "required": ["id", "sapdId", "sapName", "sapProtocolInfo"],
+ "required": [
+ "resourceId"
+ ],
"properties": {
- "id": {
- "description": "An identifier that is unique with respect to a NS. Representation: string of variable length.\n",
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceProviderId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "type": "string"
+ },
+ "vimLevelAdditionalResourceInfo": {
+ "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
+ "type": "object",
+ "properties": {
+ "hostName": {
+ "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note. \n",
"type": "string"
- },
- "sapdId": {
- "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
+ },
+ "persistentVolume": {
+ "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note. \n",
"type": "string"
- },
- "sapName": {
- "description": "Human readable name for the SAP instance.\n",
+ },
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ },
+ "containerNamespace": {
+ "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise. \n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "linkPort": {
+ "description": "Link ports of the VL instance. Cardinality of zero indicates that no port has yet been created for the VL instance.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents information about a link port of a VL instance. It shall comply with the provisions defined in Table 6.5.3.55-1. NOTE: When the NsVirtualLink, from which the present NsLinkPort is part of, is provided as an ExtVirtualLink as input of a VNF LCM operation, the id of the ExtLinkPort shall be the same as the corresponding NsLinkPort.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "resourceHandle"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceHandle": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would correspond to the ‘kind’ field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the ‘claimName’ field in the Kubernetes® manifest, or a compound name built by Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the ‘metadata.name’ field in Kubernetes® manifest. \n",
+ "type": "object",
+ "required": [
+ "resourceId"
+ ],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
"type": "string"
- },
- "description": {
- "description": "Human readable description for the SAP instance.\n",
+ },
+ "resourceProviderId": {
+ "description": "An identifier with the intention of being globally unique.\n",
"type": "string"
- },
- "sapProtocolInfo": {
- "description": "Network protocol information for this SAP.\n",
- "type": "array",
- "items": {
- "description": "This type describes the protocol layer(s) that a CP or SAP uses together with protocol-related information, like addresses. It shall comply with the provisions defined in Table 6.5.3.58-1. NOTE: This attribute allows to signal the addition of further types of layer and protocol in future versions of the present document in a backwards-compatible way. In the current version of the present document, only IP over Ethernet is supported.\n",
- "type": "object",
- "required": ["layerProtocol", "ipOverEthernet"],
- "properties": {
- "layerProtocol": {
- "description": "The identifier of layer(s) and protocol(s) associated to the network address information. Permitted values: - IP_OVER_ETHERNET\n - IP_FOR_VIRTUAL_CP\nSee note.\n",
- "type": "string",
- "enum": ["IP_OVER_ETHERNET", "IP_FOR_VIRTUAL_CP"]
- },
- "ipOverEthernet": {
- "description": "This type represents information about a network address that has been assigned.\nNOTE 1: At least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2: Exactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3: If the Cp instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4: Depending on the NFVI networking infrastructure, the \"segmentationId\" may indicate the actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header of the packets or it may be an identifier used between the application and the NFVI networking infrastructure to identify the network sub-interface of the trunk port in question. In the latter case the NFVI infrastructure will map this local \"segmentationId\" to whatever \"segmentationId\" is actually used by the NFVI's transport technology.\n",
- "type": "object",
- "anyOf": [{
- "required": ["macAddress"]
- }, {
- "required": ["ipAddresses"]
- }],
- "properties": {
- "macAddress": {
- "description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
- "type": "string",
- "format": "MAC"
- },
- "segmentationId": {
- "description": "Identification of the network segment to which the Cp instance connects to. See note 3 and note 4.\n",
- "type": "string"
- },
- "ipAddresses": {
- "description": "Addresses assigned to the CP instance. Each entry represents IP addresses assigned by fixed or dynamic IP address assignment per subnet. See note 1.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": ["type"],
- "oneOf": [{
- "required": ["addresses"]
- }, {
- "required": ["addressRange"]
- }],
- "properties": {
- "type": {
- "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
- "type": "string",
- "enum": ["IPV4", "IPV6"]
- },
- "addresses": {
- "description": "Fixed addresses assigned (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
- "type": "array",
- "items": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- },
- "isDynamic": {
- "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
- "type": "boolean"
- },
- "addressRange": {
- "description": "An IP address range used, e.g., in case of egress connections. Exactly one of \"addresses\" or \"addressRange\" shall be present. See note 2.\n",
- "type": "object",
- "required": ["minAddress", "maxAddress"],
- "properties": {
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- },
- "subnetId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- }
- },
- "type": {
- "description": "The type of the IP addresses\n",
- "type": "string",
- "enum": ["PV4", "PV6"]
- },
- "addresses": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "isDynamic": {
- "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
- "type": "boolean"
- },
- "addressRange": {
- "description": "An IP address range used, e.g. in case of egress connections. See note.\n",
- "type": "object",
- "required": ["minAddress", "maxAddress"],
- "properties": {
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- },
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "subnetId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- },
- "virtualCpAddress": {
- "description": "This type represents information about a network address that has been assigned to a virtual CP.\n",
- "type": "object",
- "required": ["type"],
- "properties": {
- "type": {
- "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
- "type": "string",
- "enum": ["IPV4", "IPV6"]
- },
- "loadBalancerIp": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- }
- }
+ },
+ "resourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "type": "string"
+ },
+ "vimLevelAdditionalResourceInfo": {
+ "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
+ "type": "object",
+ "properties": {
+ "hostName": {
+ "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "persistentVolume": {
+ "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
}
+ },
+ "containerNamespace": {
+ "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise. \n",
+ "type": "string"
+ }
+ }
+ },
+ "nsCpHandle": {
+ "description": "This type represents an identifier of the CP or SAP instance. It shall comply with the provisions defined in Table 6.5.3.56-1. NOTE 1: For the VNF external CP instance, both vnfInstanceId and vnfExtCpInstanceId shall be present as a pair. NOTE 2: For the PNF external CP instance, both pnfInfoId and PnfExtCpInstanceId shall be present as a pair. NOTE 3: For the SAP instance, both nsInstanceId and nsSapInstanceId shall be present as a pair. NOTE 4: One pair of identifiers (VNF external CP, PNF external CP or SAP) shall be present.\n",
+ "type": "object",
+ "oneOf": [
+ {
+ "required": [
+ "vnfInstanceId",
+ "vnfExtCpInstanceId"
+ ]
+ },
+ {
+ "required": [
+ "pnfInfoId",
+ "pnfExtCpInstanceId"
+ ]
+ },
+ {
+ "required": [
+ "nsInstanceId",
+ "nsSapInstanceId"
+ ]
+ }
+ ],
+ "properties": {
+ "vnfInstanceId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfExtCpInstanceId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "pnfInfoId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "pnfExtCpInstanceId": {
+ "description": "An Identifier that is unique within respect to a PNF. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "nsInstanceId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "nsSapInstanceId": {
+ "description": "An identifier that is unique with respect to a NS. Representation: string of variable length.\n",
+ "type": "string"
+ }
}
+ }
}
+ }
}
- },
- "nestedNsInstanceId": {
- "description": "Identifier of the nested NS(s) of the NS instance.\n",
- "type": "array",
- "items": {
+ }
+ }
+ },
+ "vnffgInfo": {
+ "description": "Information on the VNFFG(s) of the NS instance.\n",
+ "type": "array",
+ "items": {
+ "description": "Information on the VNFFG(s) of the NS instance. NOTE: It indicates an exhaustive list of all the CP instances and SAP instances of the VNFFG.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "vnffgdId",
+ "vnfInstanceId",
+ "pnfInfoId"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnffgdId": {
+ "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vnfInstanceId": {
+ "description": "Identifier(s) of the constituent VNF instance(s) of this VNFFG instance.\n",
+ "type": "array",
+ "items": {
"description": "An identifier with the intention of being globally unique.\n",
"type": "string"
- }
- },
- "vnfSnapshotInfoIds": {
- "description": "Identifier of information on VNF snapshots of VNF instances that are part of this NS instance.\n",
- "type": "array",
- "items": {
+ }
+ },
+ "pnfdInfoId": {
+ "description": "Identifier(s) of the constituent PNF instance(s) of this VNFFG instance.\n",
+ "type": "array",
+ "items": {
"description": "An identifier with the intention of being globally unique.\n",
"type": "string"
+ }
+ },
+ "nsVirtualLinkInfoId": {
+ "description": "Identifier(s) of the constituent VL instance(s) of this VNFFG instance.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier that is unique with respect to a NS. Representation: string of variable length.\n",
+ "type": "string"
+ }
+ },
+ "nsCpHandle": {
+ "description": "This type represents an identifier of the CP or SAP instance. It shall comply with the provisions defined in Table 6.5.3.56-1. NOTE 1: For the VNF external CP instance, both vnfInstanceId and vnfExtCpInstanceId shall be present as a pair. NOTE 2: For the PNF external CP instance, both pnfInfoId and PnfExtCpInstanceId shall be present as a pair. NOTE 3: For the SAP instance, both nsInstanceId and nsSapInstanceId shall be present as a pair. NOTE 4: One pair of identifiers (VNF external CP, PNF external CP or SAP) shall be present.\n",
+ "type": "object",
+ "oneOf": [
+ {
+ "required": [
+ "vnfInstanceId",
+ "vnfExtCpInstanceId"
+ ]
+ },
+ {
+ "required": [
+ "pnfInfoId",
+ "pnfExtCpInstanceId"
+ ]
+ },
+ {
+ "required": [
+ "nsInstanceId",
+ "nsSapInstanceId"
+ ]
+ }
+ ],
+ "properties": {
+ "vnfInstanceId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfExtCpInstanceId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "pnfInfoId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "pnfExtCpInstanceId": {
+ "description": "An Identifier that is unique within respect to a PNF. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "nsInstanceId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "nsSapInstanceId": {
+ "description": "An identifier that is unique with respect to a NS. Representation: string of variable length.\n",
+ "type": "string"
+ }
+ }
}
- },
- "nsState": {
- "description": "The state of the NS instance. Permitted values: NOT_INSTANTIATED: The NS instance is terminated or not instantiated. INSTANTIATED: The NS instance is instantiated.\n",
- "type": "string",
- "enum": ["NOT_INSTANTIATED", "INSTANTIATED"]
- },
- "monitoringParameter": {
- "description": "Performance metrics tracked by the NFVO (e.g. for auto-scaling purposes) as identified by the NS designer in the NSD.\n",
- "type": "array",
- "items": {
- "description": "This type represents a monitoring parameter that is tracked by the NFVO, for example, for auto-scaling purposes. It shall comply with the provisions defined in Table 6.5.3.68-1.\n",
+ }
+ }
+ },
+ "sapInfo": {
+ "description": "Information on the SAP(s) of the NS instance.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents an SAP instance. It shall comply with the provisions defined in Table 6.5.3.67-1.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "sapdId",
+ "sapName",
+ "sapProtocolInfo"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier that is unique with respect to a NS. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "sapdId": {
+ "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "sapName": {
+ "description": "Human readable name for the SAP instance.\n",
+ "type": "string"
+ },
+ "description": {
+ "description": "Human readable description for the SAP instance.\n",
+ "type": "string"
+ },
+ "sapProtocolInfo": {
+ "description": "Network protocol information for this SAP.\n",
+ "type": "array",
+ "items": {
+ "description": "This type describes the protocol layer(s) that a CP or SAP uses together with protocol-related information, like addresses. It shall comply with the provisions defined in Table 6.5.3.58-1. NOTE: This attribute allows to signal the addition of further types of layer and protocol in future versions of the present document in a backwards-compatible way. In the current version of the present document, only IP over Ethernet is supported.\n",
"type": "object",
- "required": ["id", "performanceMetric"],
+ "required": [
+ "layerProtocol",
+ "ipOverEthernet"
+ ],
"properties": {
- "id": {
- "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
- "type": "string"
- },
- "name": {
- "description": "Human readable name of the monitoring parameter, as defined in the NSD.\n",
+ "layerProtocol": {
+ "description": "The identifier of layer(s) and protocol(s) associated to the network address information. Permitted values:\n - IP_OVER_ETHERNET\n - IP_FOR_VIRTUAL_CP\nSee note.\n",
+ "type": "string",
+ "enum": [
+ "IP_OVER_ETHERNET",
+ "IP_FOR_VIRTUAL_CP"
+ ]
+ },
+ "ipOverEthernet": {
+ "description": "This type represents information about a network address that has been assigned.\nNOTE 1: At least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2: Exactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3: If the Cp instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4: Depending on the NFVI networking infrastructure, the \"segmentationId\" may indicate the actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header of the packets or it may be an identifier used between the application and the NFVI networking infrastructure to identify the network sub-interface of the trunk port in question. In the latter case the NFVI infrastructure will map this local \"segmentationId\" to whatever \"segmentationId\" is actually used by the NFVI's transport technology.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "required": [
+ "macAddress"
+ ]
+ },
+ {
+ "required": [
+ "ipAddresses"
+ ]
+ }
+ ],
+ "properties": {
+ "macAddress": {
+ "description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
+ "type": "string",
+ "format": "MAC"
+ },
+ "segmentationId": {
+ "description": "Identification of the network segment to which the Cp instance connects to. See note 3 and note 4.\n",
"type": "string"
- },
- "performanceMetric": {
- "description": "Performance metric that is monitored. This attribute shall contain the related \"Measurement Name\" value as defined in clause 7.2 of ETSI GS NFV-IFA 027.\n",
+ },
+ "ipAddresses": {
+ "description": "Addresses assigned to the CP instance. Each entry represents IP addresses assigned by fixed or dynamic IP address assignment per subnet. See note 1.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": [
+ "type"
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "addresses"
+ ]
+ },
+ {
+ "required": [
+ "addressRange"
+ ]
+ }
+ ],
+ "properties": {
+ "type": {
+ "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
+ },
+ "addresses": {
+ "description": "Fixed addresses assigned (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
+ "type": "array",
+ "items": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ }
+ },
+ "isDynamic": {
+ "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
+ "type": "boolean"
+ },
+ "addressRange": {
+ "description": "An IP address range used, e.g., in case of egress connections. Exactly one of \"addresses\" or \"addressRange\" shall be present. See note 2.\n",
+ "type": "object",
+ "required": [
+ "minAddress",
+ "maxAddress"
+ ],
+ "properties": {
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ }
+ }
+ },
+ "subnetId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "type": {
+ "description": "The type of the IP addresses\n",
+ "type": "string",
+ "enum": [
+ "PV4",
+ "PV6"
+ ]
+ },
+ "addresses": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "isDynamic": {
+ "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
+ "type": "boolean"
+ },
+ "addressRange": {
+ "description": "An IP address range used, e.g. in case of egress connections. See note.\n",
+ "type": "object",
+ "required": [
+ "minAddress",
+ "maxAddress"
+ ],
+ "properties": {
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ }
+ }
+ },
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "subnetId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
"type": "string"
+ }
}
- }
- }
- },
- "nsScaleStatus": {
- "description": "Status of each NS scaling aspect declared in the applicable DF, how \"big\" the NS instance has been scaled w.r.t. that aspect. This attribute shall be present if the nsState attribute value is INSTANTIATED.\n",
- "type": "array",
- "items": {
- "description": "This type represents the target NS Scale level for each NS scaling aspect of the current deployment flavor.\n",
- "type": "object",
- "required": ["nsScalingAspectId", "nsScaleLevelId"],
- "properties": {
- "nsScalingAspectId": {
- "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
- "type": "string"
- },
- "nsScaleLevelId": {
- "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
+ },
+ "virtualCpAddress": {
+ "description": "This type represents information about a network address that has been assigned to a virtual CP.\n",
+ "type": "object",
+ "required": [
+ "type"
+ ],
+ "properties": {
+ "type": {
+ "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
+ },
+ "loadBalancerIp": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.",
"type": "string"
+ }
}
+ }
}
+ }
+ }
+ }
+ }
+ },
+ "nestedNsInstanceId": {
+ "description": "Identifier of the nested NS(s) of the NS instance.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ },
+ "vnfSnapshotInfoIds": {
+ "description": "Identifier of information on VNF snapshots of VNF instances that are part of this NS instance.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ },
+ "nsState": {
+ "description": "The state of the NS instance. Permitted values: NOT_INSTANTIATED: The NS instance is terminated or not instantiated. INSTANTIATED: The NS instance is instantiated.\n",
+ "type": "string",
+ "enum": [
+ "NOT_INSTANTIATED",
+ "INSTANTIATED"
+ ]
+ },
+ "monitoringParameter": {
+ "description": "Performance metrics tracked by the NFVO (e.g. for auto-scaling purposes) as identified by the NS designer in the NSD.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents a monitoring parameter that is tracked by the NFVO, for example, for auto-scaling purposes. It shall comply with the provisions defined in Table 6.5.3.68-1.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "performanceMetric"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "name": {
+ "description": "Human readable name of the monitoring parameter, as defined in the NSD.\n",
+ "type": "string"
+ },
+ "performanceMetric": {
+ "description": "Performance metric that is monitored. This attribute shall contain the related \"Measurement Name\" value as defined in clause 7.2 of ETSI GS NFV-IFA 027.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "nsScaleStatus": {
+ "description": "Status of each NS scaling aspect declared in the applicable DF, how \"big\" the NS instance has been scaled w.r.t. that aspect. This attribute shall be present if the nsState attribute value is INSTANTIATED.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the target NS Scale level for each NS scaling aspect of the current deployment flavor.\n",
+ "type": "object",
+ "required": [
+ "nsScalingAspectId",
+ "nsScaleLevelId"
+ ],
+ "properties": {
+ "nsScalingAspectId": {
+ "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "nsScaleLevelId": {
+ "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "additionalAffinityOrAntiAffinityRule": {
+ "description": "Information on the additional affinity or anti-affinity rule from NS instantiation operation. Shall not conflict with rules already specified in the NSD.\n",
+ "type": "array",
+ "items": {
+ "description": "This type describes the additional affinity or anti-affinity rule applicable between the VNF instances to be instantiated in the NS instantiation operation request or between the VNF instances to be instantiated in the NS instantiation operation request and the existing VNF instances..\n",
+ "type": "object",
+ "required": [
+ "affinityOrAntiAffiinty",
+ "scope"
+ ],
+ "properties": {
+ "vnfdId": {
+ "description": "Reference to a VNFD. When the VNFD which is not used to instantiate VNF, it presents all VNF instances of this type as the subjects of the affinity or anti-affinity rule. The VNF instance which the VNFD presents is not necessary as a part of the NS to be instantiated.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ },
+ "vnfProfileId": {
+ "description": "Reference to a vnfProfile defined in the NSD. At least one VnfProfile which is used to instantiate VNF for the NS to be instantiated as the subject of the affinity or anti-affinity rule shall be present. When the VnfProfile which is not used to instantiate VNF, it presents all VNF instances of this type as the subjects of the affinity or anti-affinity rule. The VNF instance which the VnfProfile presents is not necessary as a part of the NS to be instantiated.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
+ "type": "string"
+ }
+ },
+ "vnfInstanceId": {
+ "description": "Reference to the existing VNF instance as the subject of the affinity or anti-affinity rule. The existing VNF instance is not necessary as a part of the NS to be instantiated.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ },
+ "affinityOrAntiAffiinty": {
+ "description": "The type of the constraint. Permitted values: AFFINITY ANTI_AFFINITY.\n",
+ "type": "string",
+ "enum": [
+ "AFFINITY",
+ "ANTI_AFFINITY"
+ ]
+ },
+ "scope": {
+ "description": "Specifies the scope of the rule where the placement constraint applies. Permitted values: NFVI_POP ZONE ZONE_GROUP NFVI_NODE.\n",
+ "type": "string",
+ "enum": [
+ "NFVI_POP",
+ "ZONE",
+ "ZONE_GROUP",
+ "NFVI_NODE"
+ ]
+ }
+ }
+ }
+ },
+ "wanConnectionInfo": {
+ "description": "Information about WAN related connectivity enabling multi-site VLs.\n",
+ "type": "array",
+ "items": {
+ "description": "This type provides information about the connectivity to the WAN of network resources realizing a VL, e.g.,\nwhen the VL is deployed on several sites across a WAN. It shall comply with the provisions defined in table 6.5.3.90-1.\nNOTE: Either a \"nsVirtualLinkInfoId\" or a \"vnfVirtualLinkResourceInfoId\" shall be provided, but not both.\n",
+ "type": "object",
+ "required": [
+ "wanConnectionInfoId"
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "nsVirtualLinkInfoId"
+ ]
+ },
+ {
+ "required": [
+ "vnfVirtualLinkResourceInfoId"
+ ]
}
- },
- "additionalAffinityOrAntiAffinityRule": {
- "description": "Information on the additional affinity or anti-affinity rule from NS instantiation operation. Shall not conflict with rules already specified in the NSD.\n",
- "type": "array",
- "items": {
- "description": "This type describes the additional affinity or anti-affinity rule applicable between the VNF instances to be instantiated in the NS instantiation operation request or between the VNF instances to be instantiated in the NS instantiation operation request and the existing VNF instances..\n",
- "type": "object",
- "required": ["affinityOrAntiAffiinty", "scope"],
- "properties": {
- "vnfdId": {
- "description": "Reference to a VNFD. When the VNFD which is not used to instantiate VNF, it presents all VNF instances of this type as the subjects of the affinity or anti-affinity rule. The VNF instance which the VNFD presents is not necessary as a part of the NS to be instantiated.\n",
- "type": "array",
- "items": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- }
+ ],
+ "properties": {
+ "wanConnectionInfoId": {
+ "description": "An identifier that is unique with respect to a NS. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "nsVirtualLinkInfoId": {
+ "description": "An identifier that is unique with respect to a NS. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vnfVirtualLinkResourceInfoId": {
+ "description": "An identifier that is unique with respect to a NS. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "protocolInfo": {
+ "description": "This type provides protocol specific information about the connectivity to the WAN of network resources realizing\na VL, e.g., when the VL is deployed on several sites and across a WAN, and the related multi-site connectivity\nservice (MSCS) enabling the connectivity through the WAN. This type supports providing information about both\npre-provisioned WAN connectivity realized by external entities to NFV-MANO but parts of such connectivity is known\nto the NFVO, as well as information about MSCS created under NFV-MANO responsibility (i.e., connectivity is realized\nwhen NFVO communicates with the WIM). It shall comply with the provisions defined in table 6.5.3.91-1.\n",
+ "type": "object",
+ "properties": {
+ "mscsInfo": {
+ "description": "This type provides information about an already provisioned multi-site connectivity service (MSCS) deployed across a WAN. It shall comply with the provisions defined in Table 6.5.3.82-1.\n",
+ "type": "object",
+ "required": [
+ "mscsId",
+ "mscsType"
+ ],
+ "properties": {
+ "mscsId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
},
- "vnfProfileId": {
- "description": "Reference to a vnfProfile defined in the NSD. At least one VnfProfile which is used to instantiate VNF for the NS to be instantiated as the subject of the affinity or anti-affinity rule shall be present. When the VnfProfile which is not used to instantiate VNF, it presents all VNF instances of this type as the subjects of the affinity or anti-affinity rule. The VNF instance which the VnfProfile presents is not necessary as a part of the NS to be instantiated.\n",
- "type": "array",
- "items": {
- "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
- "type": "string"
+ "mscsName": {
+ "description": "Human readable name of the MSCS.\n",
+ "type": "string"
+ },
+ "mscsDescription": {
+ "description": "Human readable description of the MSCS.\n",
+ "type": "string"
+ },
+ "mscsType": {
+ "description": "The type of connectivity that is provided to the virtualized networks in the NFVI-PoP and characterizes the connectivity service across the WAN. Permitted values: - L2 - L3\n",
+ "type": "string",
+ "enum": [
+ "L2VPN",
+ "L3VPN"
+ ]
+ },
+ "mscsLayerProtocol": {
+ "description": "Type of underlying connectivity service and protocol associated to the MSCS. Permitted values are as listed below and restricted by the type of MSCS: - EVPN_BGP_MPLS: as specified in IETF RFC 7432. Only applicable for mscsType=\"L2\". - EVPN_VPWS: as specified in IETF RFC 8214. Only applicable for mscsType=\"L2\". - VPLS_BGP: as specified in IETF RFC 4761 and IETF RFC 6624. Only applicable for mscsType=\"L2\". - VPLS_LDP_L2TP: as specified in IETF RFC 4762. Only applicable for mscsType=\"L2\". - VPWS_LDP_L2TP: as specified in IETF RFC 6074. Only applicable for mscsType=\"L2\". - BGP_IP_VPN: BGP/MPLS based IP VPN as specified in IETF RFC 4364. Only applicable for mscsType=\"L3\".\n",
+ "type": "string",
+ "enum": [
+ "EVPN_BGP_MPLS",
+ "EVPN_VPWS",
+ "VPLS_BGP",
+ "VPLS_LDP",
+ "VPWS",
+ "BGP_IP_VPN"
+ ]
+ },
+ "siteAccessProtectionSchemes": {
+ "description": "Information to determine the proper MSCS endpoints configuration to fulfil certain resiliency/protection requirements, e.g., by considering certain availability and redundancy of connectivity service endpoints in between NFVI-PoP and WAN.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "properties": {
+ "locationConstraints": {
+ "description": "This type represents location constraints for a VNF to be instantiated. The location constraints can be represented as follows: • as a country code • as a civic address combined with a country code • as an area, conditionally combined with a country code\nNOTE: If both \"countryCode\" and \"area\" are present, no conflicts should exist between the values of these two attributes. In case of conflicts, the API producer (i.e. the NFVO) shall disregard parts of the geographic area signalled by \"area\" that are outside the boundaries of the country signalled by \"countryCode\". If \"countryCode\" is absent, it is solely the \"area\" attribute that defines the location constraint.\n",
+ "type": "object",
+ "properties": {
+ "countryCode": {
+ "description": "The two-letter ISO 3166 country code in capital letters. Shall be present in case the \"area\" attribute is absent. May be absent if the \"area\" attribute is present (see note).\n",
+ "type": "string"
+ },
+ "civicAddressElement": {
+ "description": "Zero or more elements comprising the civic address. Shall be absent if the \"area\" attribute is present.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": [
+ "caType",
+ "caValue"
+ ],
+ "properties": {
+ "caType": {
+ "description": "Describe the content type of caValue. The value of caType shall comply with Section 3.4 of IETF RFC 4776 [13].\n",
+ "type": "integer"
+ },
+ "caValue": {
+ "description": "Content of civic address element corresponding to the caType. The format caValue shall comply with Section 3.4 of IETF RFC 4776 [13].\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "area": {
+ "description": "Geographic area. Shall be absent if the \"civicAddressElement\" attribute is present. The content of this attribute shall follow the provisions for the \"Polygon\" geometry object as defined in IETF RFC 7946, for which the \"type\" member shall be set to the value \"Polygon\". See note.\n",
+ "type": "object"
+ }
+ }
+ },
+ "protectionScheme": {
+ "description": "Defines the protection scheme. Permitted values: - UNPROTECTED: to indicate no protection. - ONE_TO_ONE: to indicate an active-passive access protection. - ONE_PLUS_ONE: to indicate an active-active access protection. - ONE_TO_N: to indicate an N active to 1 passive access protection.\n",
+ "type": "string",
+ "enum": [
+ "UNPROTECTED",
+ "ONE_TO_ONE",
+ "ONE_PLUS_ONE",
+ "ONE_TO_N"
+ ]
+ }
}
+ }
},
- "vnfInstanceId": {
- "description": "Reference to the existing VNF instance as the subject of the affinity or anti-affinity rule. The existing VNF instance is not necessary as a part of the NS to be instantiated.\n",
- "type": "array",
- "items": {
+ "mtuMscs": {
+ "description": "Maximum Transmission Unit (MTU) that can be forwarded over the MSCS (in bytes). Default value is \"1500\" (bytes).\n",
+ "type": "number"
+ },
+ "mscsEndpoints": {
+ "description": "Information about the MSCS endpoints of the MSCS.\n",
+ "type": "array",
+ "items": {
+ "description": "This type provides encapsulates information about an MSCS endpoint of the MSCS. It shall comply with the provisions defined in table 6.5.3.83-1.\n",
+ "type": "object",
+ "required": [
+ "mscsEndpointId",
+ "directionality",
+ "connectivityServiceEndpoinId"
+ ],
+ "properties": {
+ "mscsEndpointId": {
"description": "An identifier with the intention of being globally unique.\n",
"type": "string"
+ },
+ "directionality": {
+ "description": "Directionality of the data traffic in the context of the terminating MSCS endpoint from WAN’s perspective. Permitted values: - INBOUND: to indicate into the WAN. - OUTBOUND: to indicate from the WAN. - BOTH: to indicate bidirectional data traffic to/from the WAN.\n",
+ "type": "string",
+ "enum": [
+ "INBOUND",
+ "OUTBOUND",
+ "BOTH"
+ ]
+ },
+ "connectivityServiceEndpoinId": {
+ "description": "References the connectivity service endpoint configuration information applicable to support the MSCS endpoint. More than one connectivity service endpoint can be referred when endpoints are in LAG mode.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ }
}
- },
- "affinityOrAntiAffiinty": {
- "description": "The type of the constraint. Permitted values: AFFINITY ANTI_AFFINITY.\n",
- "type": "string",
- "enum": ["AFFINITY", "ANTI_AFFINITY"]
- },
- "scope": {
- "description": "Specifies the scope of the rule where the placement constraint applies. Permitted values: NFVI_POP ZONE ZONE_GROUP NFVI_NODE.\n",
- "type": "string",
- "enum": ["NFVI_POP", "ZONE", "ZONE_GROUP", "NFVI_NODE"]
+ }
}
- }
- }
- },
- "wanConnectionInfo": {
- "description": "Information about WAN related connectivity enabling multi-site VLs.\n",
- "type": "array",
- "items": {
- "description": "This type provides information about the connectivity to the WAN of network resources realizing a VL, e.g.,\nwhen the VL is deployed on several sites across a WAN. It shall comply with the provisions defined in table 6.5.3.90-1.\nNOTE: Either a \"nsVirtualLinkInfoId\" or a \"vnfVirtualLinkResourceInfoId\" shall be provided, but not both.\n",
- "type": "object",
- "required": ["wanConnectionInfoId"],
- "oneOf": [{
- "required": ["nsVirtualLinkInfoId"]
- }, {
- "required": ["vnfVirtualLinkResourceInfoId"]
- }],
- "properties": {
- "wanConnectionInfoId": {
- "description": "An identifier that is unique with respect to a NS. Representation: string of variable length.\n",
- "type": "string"
- },
- "nsVirtualLinkInfoId": {
- "description": "An identifier that is unique with respect to a NS. Representation: string of variable length.\n",
+ }
+ },
+ "connectivityServiceEndpoints": {
+ "description": "Configuration information about the network resources in the NFVI-PoP and their connectivity to the WAN.\n",
+ "type": "array",
+ "items": {
+ "description": "This type provides configuration data for the NFVI-PoP network gateway providing connectivity service endpoints. The connectivity service endpoints are used as endpoints by an MSCS. It shall comply with the provisions defined in Table 6.5.3.84-1.\n",
+ "type": "object",
+ "required": [
+ "connectivityServiceEndpointId",
+ "vimId"
+ ],
+ "properties": {
+ "connectivityServiceEndpointId": {
+ "description": "An identifier with the intention of being globally unique.\n",
"type": "string"
- },
- "vnfVirtualLinkResourceInfoId": {
- "description": "An identifier that is unique with respect to a NS. Representation: string of variable length.\n",
+ },
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
"type": "string"
- },
- "protocolInfo": {
- "description": "This type provides protocol specific information about the connectivity to the WAN of network resources realizing\na VL, e.g., when the VL is deployed on several sites and across a WAN, and the related multi-site connectivity\nservice (MSCS) enabling the connectivity through the WAN. This type supports providing information about both\npre-provisioned WAN connectivity realized by external entities to NFV-MANO but parts of such connectivity is known\nto the NFVO, as well as information about MSCS created under NFV-MANO responsibility (i.e., connectivity is realized\nwhen NFVO communicates with the WIM). It shall comply with the provisions defined in table 6.5.3.91-1.\n",
+ },
+ "siteToWanLayer2ProtocolData": {
+ "description": "This type provides information about Layer 2 protocol specific information for the configuration of the NFVI-PoP network gateway to enable the stitching of the intra-site VN to the MSCS over the WAN. It shall comply with the provisions defined in Table 6.5.3.85-1. NOTE: Either \"networkResources\" or \"vnSegmentsIds\" shall be provided, but not both.\n",
"type": "object",
+ "required": [
+ "layer2ConnectionInfo"
+ ],
"properties": {
- "mscsInfo": {
- "description": "This type provides information about an already provisioned multi-site connectivity service (MSCS) deployed across a WAN. It shall comply with the provisions defined in Table 6.5.3.82-1.\n",
+ "layer2ConnectionInfo": {
+ "description": "Layer 2 protocol parameters of the connectivity service endpoint (CSE).\n",
+ "type": "object",
+ "required": [
+ "connectionType",
+ "interfaceType",
+ "interfaceTagging",
+ "encapsulationType"
+ ],
+ "properties": {
+ "connectionType": {
+ "description": "The type of connection to be established on the connectivity service point. Permitted values: - CSE: defined by the characteristics of the existing referred connectivity service point. - AGGREGATE_CSE: create an aggregation of the connectivity service endpoints.\n",
+ "type": "string",
+ "enum": [
+ "CSE",
+ "AGGREGATE_CSE"
+ ]
+ },
+ "interfaceType": {
+ "description": "To indicate whether to create logical interfaces on the referred connectivity service endpoint or new aggregated connectivity service endpoint. Permitted values: - PARENT: use the mapped interface to the connectivity service endpoint as is, i.e., do not create logical interfaces. - LOGICAL: create logical interfaces.\n",
+ "type": "string",
+ "enum": [
+ "PARENT",
+ "LOGICAL"
+ ]
+ },
+ "interfaceTagging": {
+ "description": "The type of frames to forward on the connectivity service point. Permitted values: - UNTAGGED: an interface where frames are not tagged. - TAGGED: an interface configured to forward tagged frames (i.e., enabled for VLAN tagging).\n",
+ "type": "string",
+ "enum": [
+ "UNTAGGED",
+ "TAGGED"
+ ]
+ },
+ "encapsulationType": {
+ "description": "The type of encapsulation. If the interfaceTagging=\"TAGGED\", either \"VLAN\" or \"VXLAN\" shall be set. Permitted values: - ETH: generic Ethernet encapsulation. - VLAN: encapsulation based on VLAN. - VXLAN: encapsulation based on VXLAN.\n",
+ "type": "string",
+ "enum": [
+ "ETH",
+ "VLAN",
+ "VXLAN"
+ ]
+ },
+ "vlanTaggingType": {
+ "description": "Type of encapsulation method for VLAN tagging. Shall be present if interfaceTagging=\"TAGGED\" and encapsulationType=\"VLAN\". Permitted values: - DOT1Q: used when packets on the CSE are encapsulated with one or a set of customer VLAN identifiers. - QINQ: used when packets on the CSE are encapsulated with multiple customer VLAN identifiers and a single\n service VLAN identifier.\n- QINANY: used when packets on the CSE have no specific customer VLAN and a service VLAN identifier is used.\n",
+ "type": "string",
+ "enum": [
+ "DOT1Q",
+ "QINQ",
+ "QINANY"
+ ]
+ },
+ "wanSegmentIds": {
+ "description": "Segment identifiers to pass on the tagged interface. Shall be present if encapsulationType=\"VLAN\" or “VXLAN\".\n",
"type": "object",
- "required": ["mscsId", "mscsType"],
+ "required": [
+ "wanSegmentIdValue"
+ ],
"properties": {
- "mscsId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "mscsName": {
- "description": "Human readable name of the MSCS.\n",
- "type": "string"
- },
- "mscsDescription": {
- "description": "Human readable description of the MSCS.\n",
- "type": "string"
- },
- "mscsType": {
- "description": "The type of connectivity that is provided to the virtualized networks in the NFVI-PoP and characterizes the connectivity service across the WAN. Permitted values: - L2 - L3\n",
- "type": "string",
- "enum": ["L2VPN", "L3VPN"]
- },
- "mscsLayerProtocol": {
- "description": "Type of underlying connectivity service and protocol associated to the MSCS. Permitted values are as listed below and restricted by the type of MSCS: - EVPN_BGP_MPLS: as specified in IETF RFC 7432. Only applicable for mscsType=\"L2\". - EVPN_VPWS: as specified in IETF RFC 8214. Only applicable for mscsType=\"L2\". - VPLS_BGP: as specified in IETF RFC 4761 and IETF RFC 6624. Only applicable for mscsType=\"L2\". - VPLS_LDP_L2TP: as specified in IETF RFC 4762. Only applicable for mscsType=\"L2\". - VPWS_LDP_L2TP: as specified in IETF RFC 6074. Only applicable for mscsType=\"L2\". - BGP_IP_VPN: BGP/MPLS based IP VPN as specified in IETF RFC 4364. Only applicable for mscsType=\"L3\".\n",
- "type": "string",
- "enum": ["EVPN_BGP_MPLS", "EVPN_VPWS", "VPLS_BGP", "VPLS_LDP", "VPWS", "BGP_IP_VPN"]
- },
- "siteAccessProtectionSchemes": {
- "description": "Information to determine the proper MSCS endpoints configuration to fulfil certain resiliency/protection requirements, e.g., by considering certain availability and redundancy of connectivity service endpoints in between NFVI-PoP and WAN.\n",
- "type": "array",
- "items": {
- "type": "object",
- "properties": {
- "locationConstraints": {
- "description": "This type represents location constraints for a VNF to be instantiated. The location constraints can be represented as follows: as a country code as a civic address combined with a country code as an area, conditionally combined with a country code\nNOTE: If both \"countryCode\" and \"area\" are present, no conflicts should exist between the values of these two attributes. In case of conflicts, the API producer (i.e. the NFVO) shall disregard parts of the geographic area signalled by \"area\" that are outside the boundaries of the country signalled by \"countryCode\". If \"countryCode\" is absent, it is solely the \"area\" attribute that defines the location constraint.\n",
- "type": "object",
- "properties": {
- "countryCode": {
- "description": "The two-letter ISO 3166 country code in capital letters. Shall be present in case the \"area\" attribute is absent. May be absent if the \"area\" attribute is present (see note).\n",
- "type": "string"
- },
- "civicAddressElement": {
- "description": "Zero or more elements comprising the civic address. Shall be absent if the \"area\" attribute is present.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": ["caType", "caValue"],
- "properties": {
- "caType": {
- "description": "Describe the content type of caValue. The value of caType shall comply with Section 3.4 of IETF RFC 4776 [13].\n",
- "type": "integer"
- },
- "caValue": {
- "description": "Content of civic address element corresponding to the caType. The format caValue shall comply with Section 3.4 of IETF RFC 4776 [13].\n",
- "type": "string"
- }
- }
- }
- },
- "area": {
- "description": "Geographic area. Shall be absent if the \"civicAddressElement\" attribute is present. The content of this attribute shall follow the provisions for the \"Polygon\" geometry object as defined in IETF RFC 7946, for which the \"type\" member shall be set to the value \"Polygon\". See note.\n",
- "type": "object"
- }
- }
- },
- "protectionScheme": {
- "description": "Defines the protection scheme. Permitted values: - UNPROTECTED: to indicate no protection. - ONE_TO_ONE: to indicate an active-passive access protection. - ONE_PLUS_ONE: to indicate an active-active access protection. - ONE_TO_N: to indicate an N active to 1 passive access protection.\n",
- "type": "string",
- "enum": ["UNPROTECTED", "ONE_TO_ONE", "ONE_PLUS_ONE", "ONE_TO_N"]
- }
- }
- }
- },
- "mtuMscs": {
- "description": "Maximum Transmission Unit (MTU) that can be forwarded over the MSCS (in bytes). Default value is \"1500\" (bytes).\n",
- "type": "number"
- },
- "mscsEndpoints": {
- "description": "Information about the MSCS endpoints of the MSCS.\n",
- "type": "array",
- "items": {
- "description": "This type provides encapsulates information about an MSCS endpoint of the MSCS. It shall comply with the provisions defined in table 6.5.3.83-1.\n",
- "type": "object",
- "required": ["mscsEndpointId", "directionality", "connectivityServiceEndpoinId"],
- "properties": {
- "mscsEndpointId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "directionality": {
- "description": "Directionality of the data traffic in the context of the terminating MSCS endpoint from WANs perspective. Permitted values: - INBOUND: to indicate into the WAN. - OUTBOUND: to indicate from the WAN. - BOTH: to indicate bidirectional data traffic to/from the WAN.\n",
- "type": "string",
- "enum": ["INBOUND", "OUTBOUND", "BOTH"]
- },
- "connectivityServiceEndpoinId": {
- "description": "References the connectivity service endpoint configuration information applicable to support the MSCS endpoint. More than one connectivity service endpoint can be referred when endpoints are in LAG mode.\n",
- "type": "array",
- "items": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- }
- }
- }
- }
+ "wanSegmentIdValue": {
+ "description": "Identifier of the network segment (e.g., VLAN id or VNI).\n",
+ "type": "string"
+ },
+ "wanSegmentIdUpperRange": {
+ "description": "Identifier of the upper range network segment, in case the \"wanSegmentIds\" is used to define a range.\n",
+ "type": "string"
+ }
+ }
+ },
+ "vxlanConfig": {
+ "description": "Additional configuration needed when using VXLAN encapsulation. Shall be present if interfaceTagging=\"TAGGED\" and encapsulationType=\"VXLAN\".\n",
+ "type": "object",
+ "required": [
+ "peerMode"
+ ],
+ "properties": {
+ "peerMode": {
+ "description": "Type of VXLAN access mode. Default value is \"STATIC\".\nPermitted values: - STATIC - BGP_EVPN\n",
+ "type": "string",
+ "enum": [
+ "STATIC",
+ "BGP_EVPN"
+ ]
+ },
+ "peers": {
+ "description": "List of IP addresses of VTEP peers when using static mode.\n",
+ "type": "array",
+ "items": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
}
+ }
}
- },
- "connectivityServiceEndpoints": {
- "description": "Configuration information about the network resources in the NFVI-PoP and their connectivity to the WAN.\n",
+ },
+ "lagInterfaceData": {
+ "description": "Information for setting up a LAG interface aggregating multiple connectivity service endpoints.\n",
+ "type": "object",
+ "required": [
+ "aggregatedEndpoints",
+ "lacpActivation",
+ "lacpConfig"
+ ],
+ "properties": {
+ "aggregatedEndpoints": {
+ "description": "List of the connectivity service endpoints that are to be aggregated. Shall be present if connectionType=\"AGGREGATE_CSE\". In case of aggregating connectivity service endpoints, only one SiteToWanLayer2ProtocolData shall be provided for the whole set of aggregated endpoints.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ },
+ "lacpActivation": {
+ "description": "Indicates whether to activate LACP on the interface. If \"TRUE\", the LACP is to be activated, or \"FALSE\" otherwise. Default value is \"FALSE\".\n",
+ "type": "boolean"
+ },
+ "lacpConfig": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ },
+ "layer2ControlProtocol": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ },
+ "mtuL2": {
+ "description": "Maximum Transmission Unit (MTU) that can be forwarded at layer 2 (in bytes). Default value is \"1500\" (bytes).\n",
+ "type": "number"
+ },
+ "virtualRoutingAndForwarding": {
+ "description": "Configuration related to the L2 virtual routing and forwarding (MAC-VRF).\n",
+ "type": "object",
+ "required": [
+ "macVrfName"
+ ],
+ "properties": {
+ "macVrfName": {
+ "description": "Name (or identifier) of the MAC-VRF instance.\n",
+ "type": "string"
+ }
+ }
+ },
+ "forwardingConfig": {
+ "description": "Information related to the forwarding of the VN in the NFVI-PoP to the connectivity service endpoint, if information about the VN to \"stitch\" is already known. . by the OSS/BSS. Shall not be provided otherwise, in which case the NFVO will infer the forwarding configuration based on the NS VL, or external VL, or externally-managed VL provisioning.\n",
+ "type": "object",
+ "oneOf": [
+ {
+ "required": [
+ "networkResources"
+ ]
+ },
+ {
+ "required": [
+ "vnSegmentIds"
+ ]
+ }
+ ],
+ "properties": {
+ "networkResources": {
+ "description": "Reference to the VN resource to be forwarded into/from the MSCS. See note.\n",
"type": "array",
"items": {
- "description": "This type provides configuration data for the NFVI-PoP network gateway providing connectivity service endpoints. The connectivity service endpoints are used as endpoints by an MSCS. It shall comply with the provisions defined in Table 6.5.3.84-1.\n",
- "type": "object",
- "required": ["connectivityServiceEndpointId", "vimId"],
- "properties": {
- "connectivityServiceEndpointId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would correspond to the ‘kind’ field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the ‘claimName’ field in the Kubernetes® manifest, or a compound name built by Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the ‘metadata.name’ field in Kubernetes® manifest. \n",
+ "type": "object",
+ "required": [
+ "resourceId"
+ ],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceProviderId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "type": "string"
+ },
+ "vimLevelAdditionalResourceInfo": {
+ "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
+ "type": "object",
+ "properties": {
+ "hostName": {
+ "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
},
- "siteToWanLayer2ProtocolData": {
- "description": "This type provides information about Layer 2 protocol specific information for the configuration of the NFVI-PoP network gateway to enable the stitching of the intra-site VN to the MSCS over the WAN. It shall comply with the provisions defined in Table 6.5.3.85-1. NOTE: Either \"networkResources\" or \"vnSegmentsIds\" shall be provided, but not both.\n",
- "type": "object",
- "required": ["layer2ConnectionInfo"],
- "properties": {
- "layer2ConnectionInfo": {
- "description": "Layer 2 protocol parameters of the connectivity service endpoint (CSE).\n",
- "type": "object",
- "required": ["connectionType", "interfaceType", "interfaceTagging", "encapsulationType"],
- "properties": {
- "connectionType": {
- "description": "The type of connection to be established on the connectivity service point. Permitted values: - CSE: defined by the characteristics of the existing referred connectivity service point. - AGGREGATE_CSE: create an aggregation of the connectivity service endpoints.\n",
- "type": "string",
- "enum": ["CSE", "AGGREGATE_CSE"]
- },
- "interfaceType": {
- "description": "To indicate whether to create logical interfaces on the referred connectivity service endpoint or new aggregated connectivity service endpoint. Permitted values: - PARENT: use the mapped interface to the connectivity service endpoint as is, i.e., do not create logical interfaces. - LOGICAL: create logical interfaces.\n",
- "type": "string",
- "enum": ["PARENT", "LOGICAL"]
- },
- "interfaceTagging": {
- "description": "The type of frames to forward on the connectivity service point. Permitted values: - UNTAGGED: an interface where frames are not tagged. - TAGGED: an interface configured to forward tagged frames (i.e., enabled for VLAN tagging).\n",
- "type": "string",
- "enum": ["UNTAGGED", "TAGGED"]
- },
- "encapsulationType": {
- "description": "The type of encapsulation. If the interfaceTagging=\"TAGGED\", either \"VLAN\" or \"VXLAN\" shall be set. Permitted values: - ETH: generic Ethernet encapsulation. - VLAN: encapsulation based on VLAN. - VXLAN: encapsulation based on VXLAN.\n",
- "type": "string",
- "enum": ["ETH", "VLAN", "VXLAN"]
- },
- "vlanTaggingType": {
- "description": "Type of encapsulation method for VLAN tagging. Shall be present if interfaceTagging=\"TAGGED\" and encapsulationType=\"VLAN\". Permitted values: - DOT1Q: used when packets on the CSE are encapsulated with one or a set of customer VLAN identifiers. - QINQ: used when packets on the CSE are encapsulated with multiple customer VLAN identifiers and a single service VLAN identifier.\n- QINANY: used when packets on the CSE have no specific customer VLAN and a service VLAN identifier is used.\n",
- "type": "string",
- "enum": ["DOT1Q", "QINQ", "QINANY"]
- },
- "wanSegmentIds": {
- "description": "Segment identifiers to pass on the tagged interface. Shall be present if encapsulationType=\"VLAN\" or VXLAN\".\n",
- "type": "object",
- "required": ["wanSegmentIdValue"],
- "properties": {
- "wanSegmentIdValue": {
- "description": "Identifier of the network segment (e.g., VLAN id or VNI).\n",
- "type": "string"
- },
- "wanSegmentIdUpperRange": {
- "description": "Identifier of the upper range network segment, in case the \"wanSegmentIds\" is used to define a range.\n",
- "type": "string"
- }
- }
- },
- "vxlanConfig": {
- "description": "Additional configuration needed when using VXLAN encapsulation. Shall be present if interfaceTagging=\"TAGGED\" and encapsulationType=\"VXLAN\".\n",
- "type": "object",
- "required": ["peerMode"],
- "properties": {
- "peerMode": {
- "description": "Type of VXLAN access mode. Default value is \"STATIC\".\nPermitted values: - STATIC - BGP_EVPN\n",
- "type": "string",
- "enum": ["STATIC", "BGP_EVPN"]
- },
- "peers": {
- "description": "List of IP addresses of VTEP peers when using static mode.\n",
- "type": "array",
- "items": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- }
- },
- "lagInterfaceData": {
- "description": "Information for setting up a LAG interface aggregating multiple connectivity service endpoints.\n",
- "type": "object",
- "required": ["aggregatedEndpoints", "lacpActivation", "lacpConfig"],
- "properties": {
- "aggregatedEndpoints": {
- "description": "List of the connectivity service endpoints that are to be aggregated. Shall be present if connectionType=\"AGGREGATE_CSE\". In case of aggregating connectivity service endpoints, only one SiteToWanLayer2ProtocolData shall be provided for the whole set of aggregated endpoints.\n",
- "type": "array",
- "items": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- }
- },
- "lacpActivation": {
- "description": "Indicates whether to activate LACP on the interface. If \"TRUE\", the LACP is to be activated, or \"FALSE\" otherwise. Default value is \"FALSE\".\n",
- "type": "boolean"
- },
- "lacpConfig": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "layer2ControlProtocol": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "mtuL2": {
- "description": "Maximum Transmission Unit (MTU) that can be forwarded at layer 2 (in bytes). Default value is \"1500\" (bytes).\n",
- "type": "number"
- },
- "virtualRoutingAndForwarding": {
- "description": "Configuration related to the L2 virtual routing and forwarding (MAC-VRF).\n",
- "type": "object",
- "required": ["macVrfName"],
- "properties": {
- "macVrfName": {
- "description": "Name (or identifier) of the MAC-VRF instance.\n",
- "type": "string"
- }
- }
- },
- "forwardingConfig": {
- "description": "Information related to the forwarding of the VN in the NFVI-PoP to the connectivity service endpoint, if information about the VN to \"stitch\" is already known. . by the OSS/BSS. Shall not be provided otherwise, in which case the NFVO will infer the forwarding configuration based on the NS VL, or external VL, or externally-managed VL provisioning.\n",
- "type": "object",
- "oneOf": [{
- "required": ["networkResources"]
- }, {
- "required": ["vnSegmentIds"]
- }],
- "properties": {
- "networkResources": {
- "description": "Reference to the VN resource to be forwarded into/from the MSCS. See note.\n",
- "type": "array",
- "items": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes instance the vimLevelResourceType is the type of resource, as would correspond to the kind field if the resource is declared in its own Kubernetes manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the claimName field in the Kubernetes manifest, or a compound name built by Kubernetes if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the metadata.name field in Kubernetes manifest. \n",
- "type": "object",
- "required": ["resourceId"],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
- "type": "string"
- },
- "vimLevelAdditionalResourceInfo": {
- "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
- "type": "object",
- "properties": {
- "hostName": {
- "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "persistentVolume": {
- "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "containerNamespace": {
- "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
- "type": "string"
- }
- }
- }
- },
- "vnSegmentIds": {
- "description": "Identifiers of the network segments of the VN resources to be forwarded into/from the MSCS.\n",
- "type": "object",
- "required": ["vnSegmentIdValue"],
- "properties": {
- "vnSegmentIdValue": {
- "description": "Identifier of the network segment.\n",
- "type": "string"
- },
- "vnSegmentIdUpperRange": {
- "description": "Identifier of the upper range network segment, in case the \"vnSegmentIds\" is used to define a range.\n",
- "type": "string"
- }
- }
- }
- }
- }
- }
+ "persistentVolume": {
+ "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
},
- "siteToWanLayer3ProtocolData": {
- "description": "This type provides information about Layer 3 protocol specific information for the stitching of the intra-site VN to the multi-site connectivity service over the WAN. It shall comply with the provisions defined in Table 6.5.3.86-1.\n",
- "type": "object",
- "required": ["routingInfo"],
- "properties": {
- "logicalInterfaceIpAddress": {
- "description": "IP addressing information associated to a logical interface. Shall be present if the \"interfaceType\" of the SiteToWanLayer2ProtocolData is equal to \"LOGICAL\".\n",
- "type": "object",
- "required": ["ipAddress", "associatedSegmentId"],
- "properties": {
- "ipAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "associatedSegmentId": {
- "description": "The associated segment identifier that has triggered the creation of the logical interface. The value shall be one of the values listed in the \"wanSegmentIds\" of the \"siteToWanLayer2ProtocolData\".\n",
- "type": "string"
- }
- }
- },
- "routingInfo": {
- "description": "The routing information that is activated on the connectivity service endpoint. More than one \"routingInfo\" is allowed to enable stacking different routing protocols (e.g., one routing protocol for IPv4 and another one for IPv6).\n",
- "type": "object",
- "required": ["routingProtocol", "routingAddressFamily"],
- "properties": {
- "routingProtocol": {
- "description": "The routing protocol that is activated on the connectivity service endpoint. Permitted values: - BGP: used for dynamic routing BGPv4. - RIP: used for dynamic routing RIPv2. - OSPF: used for dynamic routing (OSPF version 2 for IPv4; and OSPF version 3 for IPv6). - STATIC: used for static routing. - DIRECT: used when the NFVI-PoP network is directly connected to the WAN provider network. - VRRP: used when the NFVI-PoP network is directly connected to the WAN provider network with virtual router redundancy protocol support (VRRP).\n",
- "type": "string",
- "enum": ["BGP", "RIP", "OSPF", "STATIC", "DIRECT", "VRRP"]
- },
- "staticRouting": {
- "description": "Defines a static route. It shall only be present if the routingProtocol=\"STATIC\".\n",
- "type": "object",
- "required": ["ipVersion", "ipPrefix", "prefixSize", "nextHop"],
- "properties": {
- "ipVersion": {
- "description": "The IP version applicable to the routing entry. Permitted values: - IPV4 - IPV6\n",
- "type": "string",
- "enum": ["IPV4", "IPV6"]
- },
- "ipPrefix": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "prefixSize": {
- "description": "The IP prefix size.\n",
- "type": "number"
- },
- "nextHop": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- },
- "routingAddressFamily": {
- "description": "The IP version applicable to the dynamic routing protocol. Shall be present for dynamic routing protocols. Permitted values: - IPV4 - IPV6\n",
- "type": "string",
- "enum": ["IPV4", "IPv6"]
- },
- "ospfRouting": {
- "description": "Defines parameters for OSPF routing. It shall only be present if the routingProtocol=\"OSPF\".\n",
- "type": "object",
- "required": ["areaId"],
- "properties": {
- "areaId": {
- "description": "The routing area identifier, e.g., a number or an IP address.\n",
- "type": "string"
- }
- }
- },
- "bgpRouting": {
- "description": "Defines parameters for BGP routing. It shall only be present if the routingProtocol=\"BGP\".\n",
- "type": "object",
- "required": ["bgpAs"],
- "properties": {
- "bgpAs": {
- "description": "The Autonomous System (AS) identification applicable to the BGP routing info entry.\n",
- "type": "object"
- },
- "bgpNeighbour": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "bgpAdditionalParam": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "routeMapsDistribution": {
- "description": "Maps of routes that are permitted or denied for redistribution.\n",
- "type": "object",
- "required": ["policy", "sequence", "matchAndSetRule"],
- "properties": {
- "policy": {
- "description": "The policy to apply to the route distribution.\nPermitted values: - PERMIT - DENY\n",
- "type": "string",
- "enum": ["PERMIT", "DENY"]
- },
- "sequence": {
- "description": "Sequence or index number assigned to the route-map.\n",
- "type": "number"
- },
- "matchAndSetRule": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- }
- }
- },
- "mtuL3": {
- "description": "Maximum Transmission Unit (MTU) that can be forwarded at layer 3 (in bytes). Default value is \"1500\" (bytes).\n",
- "type": "number"
- },
- "virtualRoutingAndForwarding": {
- "description": "Configuration related to the virtual routing and forwarding (VRF).\n",
- "type": "object",
- "required": ["vrfName"],
- "properties": {
- "vrfName": {
- "description": "Name (or identifier) of the VRF instance.\n",
- "type": "string"
- }
- }
- },
- "bfdConfig": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
}
+ }
+ },
+ "containerNamespace": {
+ "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise. \n",
+ "type": "string"
}
+ }
+ }
+ },
+ "vnSegmentIds": {
+ "description": "Identifiers of the network segments of the VN resources to be forwarded into/from the MSCS.\n",
+ "type": "object",
+ "required": [
+ "vnSegmentIdValue"
+ ],
+ "properties": {
+ "vnSegmentIdValue": {
+ "description": "Identifier of the network segment.\n",
+ "type": "string"
+ },
+ "vnSegmentIdUpperRange": {
+ "description": "Identifier of the upper range network segment, in case the \"vnSegmentIds\" is used to define a range.\n",
+ "type": "string"
+ }
}
+ }
}
+ }
}
- }
- }
- }
- },
- "_links": {
- "type": "object",
- "description": "Links to resources related to this resource.",
- "required": ["self"],
- "properties": {
- "self": {
- "description": "This type represents a link to a resource.\n",
- "type": "object",
- "required": ["href"],
- "properties": {
- "href": {
- "description": "URI of a resource referenced from a notification. Should be an absolute URI (i.e. a URI that contains {apiRoot}), however, may be a relative URI (i.e. a URI where the {apiRoot} part is omitted) if the {apiRoot} information is not available.\n",
- "type": "string",
- "format": "url"
- }
- }
- },
- "nestedNsInstances": {
- "description": "Links to resources related to this notification.\n",
- "type": "array",
- "items": {
- "description": "This type represents a link to a resource.\n",
+ },
+ "siteToWanLayer3ProtocolData": {
+ "description": "This type provides information about Layer 3 protocol specific information for the stitching of the intra-site VN to the multi-site connectivity service over the WAN. It shall comply with the provisions defined in Table 6.5.3.86-1.\n",
"type": "object",
- "required": ["href"],
+ "required": [
+ "routingInfo"
+ ],
"properties": {
- "href": {
- "description": "URI of a resource referenced from a notification. Should be an absolute URI (i.e. a URI that contains {apiRoot}), however, may be a relative URI (i.e. a URI where the {apiRoot} part is omitted) if the {apiRoot} information is not available.\n",
+ "logicalInterfaceIpAddress": {
+ "description": "IP addressing information associated to a logical interface. Shall be present if the \"interfaceType\" of the SiteToWanLayer2ProtocolData is equal to \"LOGICAL\".\n",
+ "type": "object",
+ "required": [
+ "ipAddress",
+ "associatedSegmentId"
+ ],
+ "properties": {
+ "ipAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
- "format": "url"
+ "format": "IP"
+ },
+ "associatedSegmentId": {
+ "description": "The associated segment identifier that has triggered the creation of the logical interface. The value shall be one of the values listed in the \"wanSegmentIds\" of the \"siteToWanLayer2ProtocolData\".\n",
+ "type": "string"
+ }
}
- }
- }
- },
- "vnfSnapshotInfos": {
- "description": "Links to the VNF snapshots associated to VNF instances which are part of this NS instance.\n",
- "type": "array",
- "items": {
- "description": "This type represents a link to a resource.\n",
- "type": "object",
- "required": ["href"],
- "properties": {
- "href": {
- "description": "URI of a resource referenced from a notification. Should be an absolute URI (i.e. a URI that contains {apiRoot}), however, may be a relative URI (i.e. a URI where the {apiRoot} part is omitted) if the {apiRoot} information is not available.\n",
+ },
+ "routingInfo": {
+ "description": "The routing information that is activated on the connectivity service endpoint. More than one \"routingInfo\" is allowed to enable stacking different routing protocols (e.g., one routing protocol for IPv4 and another one for IPv6).\n",
+ "type": "object",
+ "required": [
+ "routingProtocol",
+ "routingAddressFamily"
+ ],
+ "properties": {
+ "routingProtocol": {
+ "description": "The routing protocol that is activated on the connectivity service endpoint. Permitted values: - BGP: used for dynamic routing BGPv4. - RIP: used for dynamic routing RIPv2. - OSPF: used for dynamic routing (OSPF version 2 for IPv4; and OSPF version 3 for IPv6). - STATIC: used for static routing. - DIRECT: used when the NFVI-PoP network is directly connected to the WAN provider network. - VRRP: used when the NFVI-PoP network is directly connected to the WAN provider network with virtual\n router redundancy protocol support (VRRP).\n",
"type": "string",
- "format": "url"
+ "enum": [
+ "BGP",
+ "RIP",
+ "OSPF",
+ "STATIC",
+ "DIRECT",
+ "VRRP"
+ ]
+ },
+ "staticRouting": {
+ "description": "Defines a static route. It shall only be present if the routingProtocol=\"STATIC\".\n",
+ "type": "object",
+ "required": [
+ "ipVersion",
+ "ipPrefix",
+ "prefixSize",
+ "nextHop"
+ ],
+ "properties": {
+ "ipVersion": {
+ "description": "The IP version applicable to the routing entry. Permitted values: - IPV4 - IPV6\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
+ },
+ "ipPrefix": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "prefixSize": {
+ "description": "The IP prefix size.\n",
+ "type": "number"
+ },
+ "nextHop": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ }
+ }
+ },
+ "routingAddressFamily": {
+ "description": "The IP version applicable to the dynamic routing protocol. Shall be present for dynamic routing protocols. Permitted values: - IPV4 - IPV6\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPv6"
+ ]
+ },
+ "ospfRouting": {
+ "description": "Defines parameters for OSPF routing. It shall only be present if the routingProtocol=\"OSPF\".\n",
+ "type": "object",
+ "required": [
+ "areaId"
+ ],
+ "properties": {
+ "areaId": {
+ "description": "The routing area identifier, e.g., a number or an IP address.\n",
+ "type": "string"
+ }
+ }
+ },
+ "bgpRouting": {
+ "description": "Defines parameters for BGP routing. It shall only be present if the routingProtocol=\"BGP\".\n",
+ "type": "object",
+ "required": [
+ "bgpAs"
+ ],
+ "properties": {
+ "bgpAs": {
+ "description": "The Autonomous System (AS) identification applicable to the BGP routing info entry.\n",
+ "type": "object"
+ },
+ "bgpNeighbour": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "bgpAdditionalParam": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ },
+ "routeMapsDistribution": {
+ "description": "Maps of routes that are permitted or denied for redistribution.\n",
+ "type": "object",
+ "required": [
+ "policy",
+ "sequence",
+ "matchAndSetRule"
+ ],
+ "properties": {
+ "policy": {
+ "description": "The policy to apply to the route distribution.\nPermitted values: - PERMIT - DENY\n",
+ "type": "string",
+ "enum": [
+ "PERMIT",
+ "DENY"
+ ]
+ },
+ "sequence": {
+ "description": "Sequence or index number assigned to the route-map.\n",
+ "type": "number"
+ },
+ "matchAndSetRule": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ }
}
+ },
+ "mtuL3": {
+ "description": "Maximum Transmission Unit (MTU) that can be forwarded at layer 3 (in bytes). Default value is \"1500\" (bytes).\n",
+ "type": "number"
+ },
+ "virtualRoutingAndForwarding": {
+ "description": "Configuration related to the virtual routing and forwarding (VRF).\n",
+ "type": "object",
+ "required": [
+ "vrfName"
+ ],
+ "properties": {
+ "vrfName": {
+ "description": "Name (or identifier) of the VRF instance.\n",
+ "type": "string"
+ }
+ }
+ },
+ "bfdConfig": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
}
+ }
}
- },
- "instantiate": {
- "description": "This type represents a link to a resource.\n",
- "type": "object",
- "required": ["href"],
- "properties": {
- "href": {
- "description": "URI of a resource referenced from a notification. Should be an absolute URI (i.e. a URI that contains {apiRoot}), however, may be a relative URI (i.e. a URI where the {apiRoot} part is omitted) if the {apiRoot} information is not available.\n",
- "type": "string",
- "format": "url"
- }
- }
- },
- "terminate": {
- "description": "This type represents a link to a resource.\n",
- "type": "object",
- "required": ["href"],
- "properties": {
- "href": {
- "description": "URI of a resource referenced from a notification. Should be an absolute URI (i.e. a URI that contains {apiRoot}), however, may be a relative URI (i.e. a URI where the {apiRoot} part is omitted) if the {apiRoot} information is not available.\n",
- "type": "string",
- "format": "url"
- }
- }
- },
- "update": {
- "description": "This type represents a link to a resource.\n",
- "type": "object",
- "required": ["href"],
- "properties": {
- "href": {
- "description": "URI of a resource referenced from a notification. Should be an absolute URI (i.e. a URI that contains {apiRoot}), however, may be a relative URI (i.e. a URI where the {apiRoot} part is omitted) if the {apiRoot} information is not available.\n",
- "type": "string",
- "format": "url"
- }
- }
- },
- "scale": {
- "description": "This type represents a link to a resource.\n",
- "type": "object",
- "required": ["href"],
- "properties": {
- "href": {
- "description": "URI of a resource referenced from a notification. Should be an absolute URI (i.e. a URI that contains {apiRoot}), however, may be a relative URI (i.e. a URI where the {apiRoot} part is omitted) if the {apiRoot} information is not available.\n",
- "type": "string",
- "format": "url"
- }
- }
- },
- "heal": {
- "description": "This type represents a link to a resource.\n",
- "type": "object",
- "required": ["href"],
- "properties": {
- "href": {
- "description": "URI of a resource referenced from a notification. Should be an absolute URI (i.e. a URI that contains {apiRoot}), however, may be a relative URI (i.e. a URI where the {apiRoot} part is omitted) if the {apiRoot} information is not available.\n",
- "type": "string",
- "format": "url"
- }
- }
+ }
+ }
+ }
+ }
+ }
+ }
+ },
+ "_links": {
+ "type": "object",
+ "description": "Links to resources related to this resource.",
+ "required": [
+ "self"
+ ],
+ "properties": {
+ "self": {
+ "description": "This type represents a link to a resource.\n",
+ "type": "object",
+ "required": [
+ "href"
+ ],
+ "properties": {
+ "href": {
+ "description": "URI of a resource referenced from a notification. Should be an absolute URI (i.e. a URI that contains {apiRoot}), however, may be a relative URI (i.e. a URI where the {apiRoot} part is omitted) if the {apiRoot} information is not available.\n",
+ "type": "string",
+ "format": "url"
+ }
+ }
+ },
+ "nestedNsInstances": {
+ "description": "Links to resources related to this notification.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents a link to a resource.\n",
+ "type": "object",
+ "required": [
+ "href"
+ ],
+ "properties": {
+ "href": {
+ "description": "URI of a resource referenced from a notification. Should be an absolute URI (i.e. a URI that contains {apiRoot}), however, may be a relative URI (i.e. a URI where the {apiRoot} part is omitted) if the {apiRoot} information is not available.\n",
+ "type": "string",
+ "format": "url"
+ }
+ }
+ }
+ },
+ "vnfSnapshotInfos": {
+ "description": "Links to the VNF snapshots associated to VNF instances which are part of this NS instance.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents a link to a resource.\n",
+ "type": "object",
+ "required": [
+ "href"
+ ],
+ "properties": {
+ "href": {
+ "description": "URI of a resource referenced from a notification. Should be an absolute URI (i.e. a URI that contains {apiRoot}), however, may be a relative URI (i.e. a URI where the {apiRoot} part is omitted) if the {apiRoot} information is not available.\n",
+ "type": "string",
+ "format": "url"
}
+ }
+ }
+ },
+ "instantiate": {
+ "description": "This type represents a link to a resource.\n",
+ "type": "object",
+ "required": [
+ "href"
+ ],
+ "properties": {
+ "href": {
+ "description": "URI of a resource referenced from a notification. Should be an absolute URI (i.e. a URI that contains {apiRoot}), however, may be a relative URI (i.e. a URI where the {apiRoot} part is omitted) if the {apiRoot} information is not available.\n",
+ "type": "string",
+ "format": "url"
+ }
+ }
+ },
+ "terminate": {
+ "description": "This type represents a link to a resource.\n",
+ "type": "object",
+ "required": [
+ "href"
+ ],
+ "properties": {
+ "href": {
+ "description": "URI of a resource referenced from a notification. Should be an absolute URI (i.e. a URI that contains {apiRoot}), however, may be a relative URI (i.e. a URI where the {apiRoot} part is omitted) if the {apiRoot} information is not available.\n",
+ "type": "string",
+ "format": "url"
+ }
+ }
+ },
+ "update": {
+ "description": "This type represents a link to a resource.\n",
+ "type": "object",
+ "required": [
+ "href"
+ ],
+ "properties": {
+ "href": {
+ "description": "URI of a resource referenced from a notification. Should be an absolute URI (i.e. a URI that contains {apiRoot}), however, may be a relative URI (i.e. a URI where the {apiRoot} part is omitted) if the {apiRoot} information is not available.\n",
+ "type": "string",
+ "format": "url"
+ }
+ }
+ },
+ "scale": {
+ "description": "This type represents a link to a resource.\n",
+ "type": "object",
+ "required": [
+ "href"
+ ],
+ "properties": {
+ "href": {
+ "description": "URI of a resource referenced from a notification. Should be an absolute URI (i.e. a URI that contains {apiRoot}), however, may be a relative URI (i.e. a URI where the {apiRoot} part is omitted) if the {apiRoot} information is not available.\n",
+ "type": "string",
+ "format": "url"
+ }
+ }
+ },
+ "heal": {
+ "description": "This type represents a link to a resource.\n",
+ "type": "object",
+ "required": [
+ "href"
+ ],
+ "properties": {
+ "href": {
+ "description": "URI of a resource referenced from a notification. Should be an absolute URI (i.e. a URI that contains {apiRoot}), however, may be a relative URI (i.e. a URI where the {apiRoot} part is omitted) if the {apiRoot} information is not available.\n",
+ "type": "string",
+ "format": "url"
+ }
}
+ }
}
+ }
}
-}
\ No newline at end of file
+ }
\ No newline at end of file
diff --git a/SOL005/NSLifecycleManagement-API/schemas/NsInstances.schema.json b/SOL005/NSLifecycleManagement-API/schemas/NsInstances.schema.json
index 93b66e55058e206dbdc04174d89ce257554a48d8..02cd47bc19ee18fcf3aa911e883ff986250136e1 100644
--- a/SOL005/NSLifecycleManagement-API/schemas/NsInstances.schema.json
+++ b/SOL005/NSLifecycleManagement-API/schemas/NsInstances.schema.json
@@ -1,3444 +1,4138 @@
{
"type": "array",
"items": {
- "description": "This type represents a response for Query NS operation. It shall comply with the provisions defined in Table 6.5.2.10-1.\nNOTE 1: Void. \"vnfInstance\" attribute or one \"nestedNsInstanceId\" attribute shall be present.\nNOTE 2: The priority attribute of the NS instance is configured in the NSD in the NsDf structure. The mapping from application-specific priority values to a value in the NsDf is under OSS/BSS responsibility.\n The \"zero\" value expresses the highest priority and the fact that the NS instance based on this DF cannot be\n pre-empted during resource allocation.\nNOTE 3: Examples for the usage of priority include conflict resolution in case of resource shortage\n",
- "type": "object",
- "required": ["id", "nsInstanceName", "nsInstanceDescription", "nsdId", "nsdInfoId", "nsState", "_links"],
- "properties": {
- "id": {
+ "description": "This type represents a response for Query NS operation. It shall comply with the provisions defined in Table 6.5.2.10-1.\nNOTE 1: Void.\n \"vnfInstance\" attribute or one \"nestedNsInstanceId\" attribute shall be present.\nNOTE 2: The “priority” attribute of the NS instance is configured in the NSD in the NsDf structure.\n The mapping from application-specific priority values to a value in the NsDf is under OSS/BSS responsibility.\n The \"zero\" value expresses the highest priority and the fact that the NS instance based on this DF cannot be\n pre-empted during resource allocation.\nNOTE 3: Examples for the usage of priority include conflict resolution in case of resource shortage\n",
+ "type": "object",
+ "required": [
+ "id",
+ "nsInstanceName",
+ "nsInstanceDescription",
+ "nsdId",
+ "nsdInfoId",
+ "nsState",
+ "_links"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "nsInstanceName": {
+ "description": "Human readable name of the NS instance.\n",
+ "type": "string"
+ },
+ "nsInstanceDescription": {
+ "description": "Human readable description of the NS instance.\n",
+ "type": "string"
+ },
+ "nsdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "versionDependency": {
+ "description": "Describes version dependencies currently valid for the nested NS instance. Identifies versions of descriptors of other constituents in the NSD upon which the nested NS depends. The dependencies may be described for the NSD referenced in this NsInfo with nsdId and for NSDs with the same \"nsdExtInvariantId\". There shall not be more than one versionDependency present with the same dependentConstituentId. It may be present for the NsInfo of a nested NS. It shall not be present otherwise.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the information related to all dependencies that an NSD constituent has on the versions of other NSD constituents. It shall comply with the provisions defined in table 6.5.3.112-1.\n",
+ "type": "object",
+ "required": [
+ "dependentConstituentId"
+ ],
+ "properties": {
+ "dependentConstituentId": {
+ "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "versionDependencyStatement": {
+ "description": "Identifies one or multiple versions of an NSD constituents upon which the dependent constituent identified by dependentConstituentId has a dependency. Cardinality 0 is used to remove an existing version dependency in a profile.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the information related to one or more VNF, NS or PNF descriptor identifiers which describe one single dependency. When more than one descriptor is indicated, they correspond to different versions of the same VNF, NS or PNF and they represent alternatives to fulfil the dependency. It shall comply with the provisions defined in table 6.5.3.113-1.\n",
+ "type": "object",
+ "required": [
+ "descriptorId"
+ ],
+ "properties": {
+ "descriptorId": {
+ "description": "Identifies a VNFD, NSD or PNFD upon which the entity using this data type depends. When more than one descriptor is indicated, they shall correspond to versions of the same VNF, NS or PNF and they represent alternatives, i.e. the presence of one of them fulfills the dependency.",
+ "type": "array",
+ "items": {
+ "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
+ "type": "string"
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ },
+ "nsdInfoId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "flavourId": {
+ "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "priority": {
+ "description": "A number as defined in IETF RFC 8259.\n",
+ "type": "number"
+ },
+ "vnfInstance": {
+ "description": "Information on constituent VNF(s) of the NS instance.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents a VNF instance. It shall comply with the provisions defined in table 6.5.3.57-1.\nNOTE: Clause B.3.2 of ETSI GS NFV-SOL 003 provides examples illustrating the relationship among the \n different run-time data types (CP, VL and link ports) used to represent the connectivity \n of a VNF.\n\nNOTE 1: Modifying the value of this attribute shall not be performed when conflicts exist between the \n previous and the newly referred VNF package, i.e. when the new VNFD is changed with respect to \n the previous VNFD in other aspects than merely referencing to other VNF software images. \n In order to avoid misalignment of the VnfInstance with the current VNF's on-boarded VNF Package, \n the values of attributes in the VnfInstance that have corresponding attributes in the VNFD shall \n be kept in sync with the values in the VNFD.\nNOTE 2: ETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on TOSCA specifications. NOTE 3: VNF configurable properties are sometimes also referred to as configuration parameters applicable \n to a VNF. Some of these are set prior to instantiation and cannot be modified if the VNF is instantiated, \n some are set prior to instantiation (are part of initial configuration) and can be modified later, \n and others can be set only after instantiation. The applicability of certain configuration may depend \n on the VNF and the required operation of the VNF at a certain point in time.\nNOTE 4: It is possible to have several ExtManagedVirtualLinkInfo for the same VNF internal VL in case of a \n multi-site VNF spanning several VIMs. The set of ExtManagedVirtualLinkInfo corresponding to the same \n VNF internal VL shall indicate so by referencing to the same VnfVirtualLinkDesc and externally-managed \n multi-site VL instance (refer to clause 6.5.3.59).\nNOTE 5: Even though externally-managed internal VLs are also used for VNF-internal connectivity, they shall not \n be listed in the \"vnfVirtualLinkResourceInfo\" attribute as this would be redundant.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "vnfdId",
+ "vnfProvider",
+ "vnfProductName",
+ "vnfSoftwareVersion",
+ "vnfdVersion",
+ "vnfPkgId",
+ "instantiationState"
+ ],
+ "properties": {
+ "id": {
"description": "An identifier with the intention of being globally unique.\n",
"type": "string"
- },
- "nsInstanceName": {
- "description": "Human readable name of the NS instance.\n",
+ },
+ "vnfInstanceName": {
+ "description": "Name of the VNF instance. Modifications to this attribute can be requested using the \"ModifyVnfInfoData\" structure.\n",
"type": "string"
- },
- "nsInstanceDescription": {
- "description": "Human readable description of the NS instance.\n",
+ },
+ "vnfInstanceDescription": {
+ "description": "Human-readable description of the VNF instance. Modifications to this attribute can be requested using the \"ModifyVnfInfoData\" structure.\n",
"type": "string"
- },
- "nsdId": {
+ },
+ "vnfdId": {
"description": "An identifier with the intention of being globally unique.\n",
"type": "string"
- },
- "versionDependency": {
- "description": "Describes version dependencies currently valid for the nested NS instance. Identifies versions of descriptors of other constituents in the NSD upon which the nested NS depends. The dependencies may be described for the NSD referenced in this NsInfo with nsdId and for NSDs with the same NsdExtInvariantId. There shall not be more than one versionDependency present with the same dependentConstituentId. It may be present for the NsInfo of a nested NS. It shall not be present otherwise.\n",
+ },
+ "vnfProvider": {
+ "description": "Provider of the VNF and the VNFD. The value is copied from the VNFD.\n",
+ "type": "string"
+ },
+ "vnfProductName": {
+ "description": "Name to identify the VNF Product. The value is copied from the VNFD.\n",
+ "type": "string"
+ },
+ "vnfSoftwareVersion": {
+ "description": "A Version. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vnfdVersion": {
+ "description": "A Version. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "versionDependency": {
+ "description": "Describes version dependencies currently valid for the VNF instance. Identifies versions of descriptors of other constituents in the NSD upon which the VNF depends. The dependencies may be described for the VNFD referenced in this VnfInfo with \"vnfdId\" and for VNFDs with the same \"vnfdExtInvariantId\". There shall not be more than one \"versionDependency\" present with the same dependentConstituentId.\n",
"type": "array",
"items": {
- "description": "This type represents the information related to all dependencies that an NSD constituent has on the versions of other NSD constituents. It shall comply with the provisions defined in table 6.5.3.112-1.\n",
- "type": "object",
- "required": ["dependentConstituentId"],
- "properties": {
- "dependentConstituentId": {
- "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
- "type": "string"
- },
- "versionDependencyStatement": {
- "description": "Identifies one or multiple versions of an NSD constituents upon which the dependent constituent identified by dependentConstituentId has a dependency. Cardinality 0 is used to remove an existing version dependency in a profile.\n",
+ "description": "This type represents the information related to all dependencies that an NSD constituent has on the versions of other NSD constituents. It shall comply with the provisions defined in table 6.5.3.112-1.\n",
+ "type": "object",
+ "required": [
+ "dependentConstituentId"
+ ],
+ "properties": {
+ "dependentConstituentId": {
+ "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "versionDependencyStatement": {
+ "description": "Identifies one or multiple versions of an NSD constituents upon which the dependent constituent identified by dependentConstituentId has a dependency. Cardinality 0 is used to remove an existing version dependency in a profile.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the information related to one or more VNF, NS or PNF descriptor identifiers which describe one single dependency. When more than one descriptor is indicated, they correspond to different versions of the same VNF, NS or PNF and they represent alternatives to fulfil the dependency. It shall comply with the provisions defined in table 6.5.3.113-1.\n",
+ "type": "object",
+ "required": [
+ "descriptorId"
+ ],
+ "properties": {
+ "descriptorId": {
+ "description": "Identifies a VNFD, NSD or PNFD upon which the entity using this data type depends. When more than one descriptor is indicated, they shall correspond to versions of the same VNF, NS or PNF and they represent alternatives, i.e. the presence of one of them fulfills the dependency.",
"type": "array",
"items": {
- "description": "This type represents the information related to one or more VNF, NS or PNF descriptor identifiers which describe one single dependency. When more than one descriptor is indicated, they correspond to different versions of the same VNF, NS or PNF and they represent alternatives to fulfil the dependency. It shall comply with the provisions defined in table 6.5.3.113-1.\n",
- "type": "object",
- "required": ["descriptorId"],
- "properties": {
- "descriptorId": {
- "description": "Identifies a VNFD, NSD or PNFD upon which the entity using this information element depends. When more than one descriptor is indicated, they shall correspond to versions of the same VNF, NS or PNF and they represent. alternatives, i.e. the presence of one of them fulfills the dependency.",
- "type": "array",
- "items": {
- "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- }
+ "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
+ "type": "string"
}
+ }
}
+ }
}
+ }
}
- },
- "nsdInfoId": {
+ },
+ "vnfPkgId": {
"description": "An identifier with the intention of being globally unique.\n",
"type": "string"
- },
- "flavourId": {
- "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
+ },
+ "vnfConfigurableProperties": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ },
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
"type": "string"
- },
- "priority": {
- "description": "A number as defined in IETF RFC 8259.\n",
- "type": "number"
- },
- "vnfInstance": {
- "description": "Information on constituent VNF(s) of the NS instance.\n",
- "type": "array",
- "items": {
- "description": "This type represents a VNF instance. It shall comply with the provisions defined in table 6.5.3.57-1.\nNOTE: Clause B.3.2 of ETSI GS NFV-SOL 003 provides examples illustrating the relationship among the different run-time information elements (CP, VL and link ports) used to represent the connectivity \n of a VNF.\n\nNOTE 1: 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 changed with respect to \n the previous VNFD in other aspects than merely referencing to other VNF software images. \n In order to avoid misalignment of the VnfInstance with the current VNF's on-boarded VNF Package, \n the values of attributes in the VnfInstance that have corresponding attributes in the VNFD shall \n be kept in sync with the values in the VNFD.\nNOTE 2: ETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on TOSCA specifications. NOTE 3: VNF configurable properties are sometimes also referred to as configuration parameters applicable to a VNF. Some of these are set prior to instantiation and cannot be modified if the VNF is instantiated, \n some are set prior to instantiation (are part of initial configuration) and can be modified later, \n and others can be set only after instantiation. The applicability of certain configuration may depend \n on the VNF and the required operation of the VNF at a certain point in time.\nNOTE 4: It is possible to have several ExtManagedVirtualLinkInfo for the same VNF internal VL in case of a multi-site VNF spanning several VIMs. The set of ExtManagedVirtualLinkInfo corresponding to the same \n VNF internal VL shall indicate so by referencing to the same VnfVirtualLinkDesc and externally-managed \n multi-site VL instance (refer to clause 6.5.3.59).\nNOTE 5: Even though externally-managed internal VLs are also used for VNF-internal connectivity, they shall not be listed in the \"vnfVirtualLinkResourceInfo\" attribute as this would be redundant.\n",
- "type": "object",
- "required": ["id", "vnfdId", "vnfProvider", "vnfProductName", "vnfSoftwareVersion", "vnfdVersion", "vnfPkgId", "instantiationState"],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
+ },
+ "instantiationState": {
+ "description": "The instantiation state of the VNF.\nPermitted values: - NOT_INSTANTIATED: The VNF instance is terminated or not instantiated. - INSTANTIATED: The VNF instance is instantiated.\n",
+ "type": "string",
+ "enum": [
+ "NOT_INSTANTIATED",
+ "INSTANTIATED"
+ ]
+ },
+ "instantiatedVnfInfo": {
+ "description": "Information specific to an instantiated VNF instance. This attribute shall be present if the instantiateState attribute value is INSTANTIATED.\n",
+ "type": "object",
+ "required": [
+ "flavourId",
+ "vnfState",
+ "extCpInfo"
+ ],
+ "properties": {
+ "flavourId": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
+ "type": "string"
+ },
+ "vnfState": {
+ "type": "string",
+ "enum": [
+ "STARTED",
+ "STOPPED"
+ ]
+ },
+ "scaleStatus": {
+ "description": "Scale status of the VNF, one entry per aspect. Represents for every scaling aspect how \"big\" the VNF has been scaled w.r.t. that aspect.\n",
+ "type": "array",
+ "items": {
+ "required": [
+ "aspectId",
+ "scaleLevel"
+ ],
+ "type": "object",
+ "properties": {
+ "aspectId": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
+ "type": "string"
},
- "vnfInstanceName": {
- "description": "Name of the VNF instance. Modifications to this attribute can be requested using the \"ModifyVnfInfoData\" structure.\n",
- "type": "string"
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
},
- "vnfInstanceDescription": {
- "description": "Human-readable description of the VNF instance. Modifications to this attribute can be requested using the \"ModifyVnfInfoData\" structure.\n",
- "type": "string"
+ "scaleLevel": {
+ "description": "Indicates the scale level. The minimum value shall be 0 and the maximum value shall be <= maxScaleLevel as described in the VNFD.\n",
+ "type": "integer"
+ }
+ }
+ }
+ },
+ "maxScaleLevels": {
+ "description": "Maximum allowed scale levels of the VNF, one entry per aspect. This attribute shall be present if the VNF supports scaling.\n",
+ "type": "array",
+ "items": {
+ "required": [
+ "aspectId",
+ "scaleLevel"
+ ],
+ "type": "object",
+ "properties": {
+ "aspectId": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
+ "type": "string"
},
"vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
},
- "vnfProvider": {
- "description": "Provider of the VNF and the VNFD. The value is copied from the VNFD.\n",
- "type": "string"
+ "scaleLevel": {
+ "description": "Indicates the scale level. The minimum value shall be 0 and the maximum value shall be <= maxScaleLevel as described in the VNFD.\n",
+ "type": "integer"
+ }
+ }
+ }
+ },
+ "extCpInfo": {
+ "description": "Information about the external CPs exposed by the VNF instance. When trunking is enabled, the list of entries includes both, external CPs corresponding to parent ports of a trunk, and external CPs associated to sub-ports of a trunk.\n",
+ "type": "array",
+ "minItems": 1,
+ "items": {
+ "description": "This type represents information about an external CP of a VNF. It shall comply with the provisions defined in Table 6.5.3.70-1. NOTE 1: The attributes attributes \"associatedVnfcCpId\", \"associatedVipCpId\", \"associatedVirtualCpId\" and \"associatedVnfVirtualLinkId\" are mutually exclusive. Exactly one shall be present. NOTE 2: An external CP instance is not associated to a link port in the cases indicated for the “extLinkPorts” attribute in clause 6.5.3.26. NOTE 3: Cardinality greater than 1 is only applicable for specific cases where more than one network attachment definition resource is needed to fulfil the connectivity requirements of the external CP, e.g. to build a link redundant mated pair in SR-IOV cases. NOTE 4: When more than one \"netAttDefResourceId\" is indicated, all shall belong to the same namespace.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "cpdId",
+ "cpProtocolInfo"
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "associatedVnfcCpId"
+ ]
},
- "vnfProductName": {
- "description": "Name to identify the VNF Product. The value is copied from the VNFD.\n",
- "type": "string"
+ {
+ "required": [
+ "associatedVipCpId"
+ ]
},
- "vnfSoftwareVersion": {
- "description": "A Version. Representation: string of variable length.\n",
- "type": "string"
+ {
+ "required": [
+ "associatedVirtualCpId"
+ ]
},
- "vnfdVersion": {
- "description": "A Version. Representation: string of variable length.\n",
- "type": "string"
+ {
+ "required": [
+ "associatedVnfVirtualLinkId"
+ ]
+ }
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
},
- "versionDependency": {
- "description": "Describes version dependencies currently valid for the VNF instance. Identifies versions of descriptors of other constituents in the NSD upon which the VNF depends. The dependencies may be described for the VNFD referenced in this VnfInfo with vnfdId and for VNFDs with the same VnfdExtInvariantId. There shall not be more than one versionDependency present with the same dependentConstituentId.\n",
- "type": "array",
- "items": {
- "description": "This type represents the information related to all dependencies that an NSD constituent has on the versions of other NSD constituents. It shall comply with the provisions defined in table 6.5.3.112-1.\n",
+ "cpdId": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
+ "type": "string"
+ },
+ "cpConfigId": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "cpProtocolInfo": {
+ "description": "Network protocol information for this CP.\n",
+ "type": "array",
+ "minItems": 1,
+ "items": {
+ "description": "This type describes the protocol layer(s) that a CP or SAP uses together with protocol-related information, like addresses. It shall comply with the provisions defined in Table 6.5.3.58-1. NOTE: This attribute allows to signal the addition of further types of layer and protocol in future versions of the present document in a backwards-compatible way. In the current version of the present document, only IP over Ethernet is supported.\n",
+ "type": "object",
+ "required": [
+ "layerProtocol",
+ "ipOverEthernet"
+ ],
+ "properties": {
+ "layerProtocol": {
+ "description": "The identifier of layer(s) and protocol(s) associated to the network address information. Permitted values:\n - IP_OVER_ETHERNET\n - IP_FOR_VIRTUAL_CP\nSee note.\n",
+ "type": "string",
+ "enum": [
+ "IP_OVER_ETHERNET",
+ "IP_FOR_VIRTUAL_CP"
+ ]
+ },
+ "ipOverEthernet": {
+ "description": "This type represents information about a network address that has been assigned.\nNOTE 1: At least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2: Exactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3: If the Cp instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4: Depending on the NFVI networking infrastructure, the \"segmentationId\" may indicate the actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header of the packets or it may be an identifier used between the application and the NFVI networking infrastructure to identify the network sub-interface of the trunk port in question. In the latter case the NFVI infrastructure will map this local \"segmentationId\" to whatever \"segmentationId\" is actually used by the NFVI's transport technology.\n",
"type": "object",
- "required": ["dependentConstituentId"],
+ "anyOf": [
+ {
+ "required": [
+ "macAddress"
+ ]
+ },
+ {
+ "required": [
+ "ipAddresses"
+ ]
+ }
+ ],
"properties": {
- "dependentConstituentId": {
- "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
- "type": "string"
- },
- "versionDependencyStatement": {
- "description": "Identifies one or multiple versions of an NSD constituents upon which the dependent constituent identified by dependentConstituentId has a dependency. Cardinality 0 is used to remove an existing version dependency in a profile.\n",
- "type": "array",
- "items": {
- "description": "This type represents the information related to one or more VNF, NS or PNF descriptor identifiers which describe one single dependency. When more than one descriptor is indicated, they correspond to different versions of the same VNF, NS or PNF and they represent alternatives to fulfil the dependency. It shall comply with the provisions defined in table 6.5.3.113-1.\n",
- "type": "object",
- "required": ["descriptorId"],
- "properties": {
- "descriptorId": {
- "description": "Identifies a VNFD, NSD or PNFD upon which the entity using this information element depends. When more than one descriptor is indicated, they shall correspond to versions of the same VNF, NS or PNF and they represent. alternatives, i.e. the presence of one of them fulfills the dependency.",
- "type": "array",
- "items": {
- "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
- "type": "string"
- }
- }
+ "macAddress": {
+ "description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
+ "type": "string",
+ "format": "MAC"
+ },
+ "segmentationId": {
+ "description": "Identification of the network segment to which the Cp instance connects to. See note 3 and note 4.\n",
+ "type": "string"
+ },
+ "ipAddresses": {
+ "description": "Addresses assigned to the CP instance. Each entry represents IP addresses assigned by fixed or dynamic IP address assignment per subnet. See note 1.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": [
+ "type"
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "addresses"
+ ]
+ },
+ {
+ "required": [
+ "addressRange"
+ ]
+ }
+ ],
+ "properties": {
+ "type": {
+ "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
+ },
+ "addresses": {
+ "description": "Fixed addresses assigned (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
+ "type": "array",
+ "items": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ }
+ },
+ "isDynamic": {
+ "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
+ "type": "boolean"
+ },
+ "addressRange": {
+ "description": "An IP address range used, e.g., in case of egress connections. Exactly one of \"addresses\" or \"addressRange\" shall be present. See note 2.\n",
+ "type": "object",
+ "required": [
+ "minAddress",
+ "maxAddress"
+ ],
+ "properties": {
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
}
+ }
+ },
+ "subnetId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
}
+ }
+ }
+ },
+ "type": {
+ "description": "The type of the IP addresses\n",
+ "type": "string",
+ "enum": [
+ "PV4",
+ "PV6"
+ ]
+ },
+ "addresses": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "isDynamic": {
+ "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
+ "type": "boolean"
+ },
+ "addressRange": {
+ "description": "An IP address range used, e.g. in case of egress connections. See note.\n",
+ "type": "object",
+ "required": [
+ "minAddress",
+ "maxAddress"
+ ],
+ "properties": {
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ }
}
+ },
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "subnetId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ }
+ }
+ },
+ "virtualCpAddress": {
+ "description": "This type represents information about a network address that has been assigned to a virtual CP.\n",
+ "type": "object",
+ "required": [
+ "type"
+ ],
+ "properties": {
+ "type": {
+ "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
+ },
+ "loadBalancerIp": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.",
+ "type": "string"
+ }
}
+ }
}
+ }
+ },
+ "extLinkPortId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
},
- "vnfPkgId": {
- "description": "An identifier with the intention of being globally unique.\n",
+ "netAttDefResourceId": {
+ "description": "Identifier of the \"NetAttDefResourceInfo\" structure that provides the specification of the interface to attach the connection point to a secondary container cluster network. See notes 3 and 4.\nIt shall be present if the external CP is associated to a VNFC realized by one or a set of OS containers and is connected to a secondary container cluster network. It shall not be present otherwise.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
"type": "string"
+ }
},
- "vnfConfigurableProperties": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
+ "metadata": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
},
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
+ "associatedVnfcCpId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "associatedVipCpId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
},
- "instantiationState": {
- "description": "The instantiation state of the VNF.\nPermitted values: - NOT_INSTANTIATED: The VNF instance is terminated or not instantiated. - INSTANTIATED: The VNF instance is instantiated.\n",
- "type": "string",
- "enum": ["NOT_INSTANTIATED", "INSTANTIATED"]
+ "associatedVirtualCpId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
},
- "instantiatedVnfInfo": {
- "description": "Information specific to an instantiated VNF instance. This attribute shall be present if the instantiateState attribute value is INSTANTIATED.\n",
+ "associatedVnfVirtualLinkId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "vipCpInfo": {
+ "description": "VIP CPs that are part of the VNF instance. Shall be present when that particular VIP CP of the VNFC instance is associated to an external CP of the VNF instance. May be present otherwise.\n",
+ "type": "array",
+ "items": {
+ "description": "This type provides information related to virtual IP (VIP) CP. It shall comply with the provisions defined in table 6.5.3.97 1. NOTE: It is possible that there is no associated VnfcCp because the VIP CP is available but not associated yet.\n",
+ "type": "object",
+ "required": [
+ "cpInstanceId",
+ "cpdId"
+ ],
+ "properties": {
+ "cpInstanceId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "cpdId": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfExtCpId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "cpProtocolInfo": {
+ "description": "Protocol information for this CP. There shall be one cpProtocolInfo for layer 3. There may be one cpProtocolInfo for layer 2.\n",
+ "type": "array",
+ "items": {
+ "description": "This type describes the protocol layer(s) that a CP or SAP uses together with protocol-related information, like addresses. It shall comply with the provisions defined in Table 6.5.3.58-1. NOTE: This attribute allows to signal the addition of further types of layer and protocol in future versions of the present document in a backwards-compatible way. In the current version of the present document, only IP over Ethernet is supported.\n",
"type": "object",
- "required": ["flavourId", "vnfState", "extCpInfo"],
+ "required": [
+ "layerProtocol",
+ "ipOverEthernet"
+ ],
"properties": {
- "flavourId": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "vnfState": {
+ "layerProtocol": {
+ "description": "The identifier of layer(s) and protocol(s) associated to the network address information. Permitted values:\n - IP_OVER_ETHERNET\n - IP_FOR_VIRTUAL_CP\nSee note.\n",
+ "type": "string",
+ "enum": [
+ "IP_OVER_ETHERNET",
+ "IP_FOR_VIRTUAL_CP"
+ ]
+ },
+ "ipOverEthernet": {
+ "description": "This type represents information about a network address that has been assigned.\nNOTE 1: At least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2: Exactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3: If the Cp instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4: Depending on the NFVI networking infrastructure, the \"segmentationId\" may indicate the actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header of the packets or it may be an identifier used between the application and the NFVI networking infrastructure to identify the network sub-interface of the trunk port in question. In the latter case the NFVI infrastructure will map this local \"segmentationId\" to whatever \"segmentationId\" is actually used by the NFVI's transport technology.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "required": [
+ "macAddress"
+ ]
+ },
+ {
+ "required": [
+ "ipAddresses"
+ ]
+ }
+ ],
+ "properties": {
+ "macAddress": {
+ "description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
"type": "string",
- "enum": ["STARTED", "STOPPED"]
- },
- "scaleStatus": {
- "description": "Scale status of the VNF, one entry per aspect. Represents for every scaling aspect how \"big\" the VNF has been scaled w.r.t. that aspect.\n",
+ "format": "MAC"
+ },
+ "segmentationId": {
+ "description": "Identification of the network segment to which the Cp instance connects to. See note 3 and note 4.\n",
+ "type": "string"
+ },
+ "ipAddresses": {
+ "description": "Addresses assigned to the CP instance. Each entry represents IP addresses assigned by fixed or dynamic IP address assignment per subnet. See note 1.\n",
"type": "array",
"items": {
- "required": ["aspectId", "scaleLevel"],
- "type": "object",
- "properties": {
- "aspectId": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "scaleLevel": {
- "description": "Indicates the scale level. The minimum value shall be 0 and the maximum value shall be <= maxScaleLevel as described in the VNFD.\n",
- "type": "integer"
- }
+ "type": "object",
+ "required": [
+ "type"
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "addresses"
+ ]
+ },
+ {
+ "required": [
+ "addressRange"
+ ]
}
- }
- },
- "maxScaleLevels": {
- "description": "Maximum allowed scale levels of the VNF, one entry per aspect. This attribute shall be present if the VNF supports scaling.\n",
- "type": "array",
- "items": {
- "required": ["aspectId", "scaleLevel"],
- "type": "object",
- "properties": {
- "aspectId": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
+ ],
+ "properties": {
+ "type": {
+ "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
+ },
+ "addresses": {
+ "description": "Fixed addresses assigned (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
+ "type": "array",
+ "items": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ }
+ },
+ "isDynamic": {
+ "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
+ "type": "boolean"
+ },
+ "addressRange": {
+ "description": "An IP address range used, e.g., in case of egress connections. Exactly one of \"addresses\" or \"addressRange\" shall be present. See note 2.\n",
+ "type": "object",
+ "required": [
+ "minAddress",
+ "maxAddress"
+ ],
+ "properties": {
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
},
- "scaleLevel": {
- "description": "Indicates the scale level. The minimum value shall be 0 and the maximum value shall be <= maxScaleLevel as described in the VNFD.\n",
- "type": "integer"
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
}
+ }
+ },
+ "subnetId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
}
+ }
+ }
+ },
+ "type": {
+ "description": "The type of the IP addresses\n",
+ "type": "string",
+ "enum": [
+ "PV4",
+ "PV6"
+ ]
+ },
+ "addresses": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "isDynamic": {
+ "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
+ "type": "boolean"
+ },
+ "addressRange": {
+ "description": "An IP address range used, e.g. in case of egress connections. See note.\n",
+ "type": "object",
+ "required": [
+ "minAddress",
+ "maxAddress"
+ ],
+ "properties": {
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ }
}
+ },
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "subnetId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ }
+ }
+ },
+ "virtualCpAddress": {
+ "description": "This type represents information about a network address that has been assigned to a virtual CP.\n",
+ "type": "object",
+ "required": [
+ "type"
+ ],
+ "properties": {
+ "type": {
+ "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
+ },
+ "loadBalancerIp": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.",
+ "type": "string"
+ }
+ }
+ }
+ }
+ }
+ },
+ "associatedVnfcCpIds": {
+ "description": "Identifiers of the VnfcCps that share the virtual IP addresse allocated to the VIP CP instance. See note.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ }
+ },
+ "vnfLinkPortId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "metadata": {
+ "description": "Allows the OSS/BSS to provide additional parameter(s) to the termination process at the NS level.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ }
+ }
+ },
+ "virtualCpInfo": {
+ "description": "virtual CPs that are part of the VNF instance. Shall be present when a particular virtual CP is associated to an external CP of the VNF instance. May be present otherwise.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the information related to a virtual CP instance of a VNF. NOTE: A consumer of the VNF LCM interface can learn the actual VNFC instances implementing the service accessible via the virtual CP instance by querying the \"vnfcResourceInfo\" from the \"InstantiatedVnfInfo\" and filtering by corresponding \"vduId\" values.",
+ "type": "object",
+ "required": [
+ "cpInstanceId",
+ "cpdId",
+ "resourceHandle",
+ "vduId"
+ ],
+ "properties": {
+ "cpInstanceId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "cpdId": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
+ "type": "string"
+ },
+ "resourceHandle": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would correspond to the ‘kind’ field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the ‘claimName’ field in the Kubernetes® manifest, or a compound name built by Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the ‘metadata.name’ field in Kubernetes® manifest. \n",
+ "type": "object",
+ "required": [
+ "resourceId"
+ ],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceProviderId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "type": "string"
+ },
+ "vimLevelAdditionalResourceInfo": {
+ "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
+ "type": "object",
+ "properties": {
+ "hostName": {
+ "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
},
- "extCpInfo": {
- "description": "Information about the external CPs exposed by the VNF instance. When trunking is enabled, the list of entries includes both, external CPs corresponding to parent ports of a trunk, and external CPs associated to sub-ports of a trunk.\n",
+ "persistentVolume": {
+ "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ },
+ "containerNamespace": {
+ "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise. \n",
+ "type": "string"
+ }
+ }
+ },
+ "vnfExtCpId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "cpProtocolInfo": {
+ "description": "Protocol information for this CP. There shall be one cpProtocolInfo for each layer protocol supported.\n",
+ "type": "array",
+ "items": {
+ "description": "This type describes the protocol layer(s) that a CP or SAP uses together with protocol-related information, like addresses. It shall comply with the provisions defined in Table 6.5.3.58-1. NOTE: This attribute allows to signal the addition of further types of layer and protocol in future versions of the present document in a backwards-compatible way. In the current version of the present document, only IP over Ethernet is supported.\n",
+ "type": "object",
+ "required": [
+ "layerProtocol",
+ "ipOverEthernet"
+ ],
+ "properties": {
+ "layerProtocol": {
+ "description": "The identifier of layer(s) and protocol(s) associated to the network address information. Permitted values:\n - IP_OVER_ETHERNET\n - IP_FOR_VIRTUAL_CP\nSee note.\n",
+ "type": "string",
+ "enum": [
+ "IP_OVER_ETHERNET",
+ "IP_FOR_VIRTUAL_CP"
+ ]
+ },
+ "ipOverEthernet": {
+ "description": "This type represents information about a network address that has been assigned.\nNOTE 1: At least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2: Exactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3: If the Cp instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4: Depending on the NFVI networking infrastructure, the \"segmentationId\" may indicate the actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header of the packets or it may be an identifier used between the application and the NFVI networking infrastructure to identify the network sub-interface of the trunk port in question. In the latter case the NFVI infrastructure will map this local \"segmentationId\" to whatever \"segmentationId\" is actually used by the NFVI's transport technology.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "required": [
+ "macAddress"
+ ]
+ },
+ {
+ "required": [
+ "ipAddresses"
+ ]
+ }
+ ],
+ "properties": {
+ "macAddress": {
+ "description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
+ "type": "string",
+ "format": "MAC"
+ },
+ "segmentationId": {
+ "description": "Identification of the network segment to which the Cp instance connects to. See note 3 and note 4.\n",
+ "type": "string"
+ },
+ "ipAddresses": {
+ "description": "Addresses assigned to the CP instance. Each entry represents IP addresses assigned by fixed or dynamic IP address assignment per subnet. See note 1.\n",
"type": "array",
- "minItems": 1,
"items": {
- "description": "This type represents information about an external CP of a VNF. It shall comply with the provisions defined in Table 6.5.3.70-1. NOTE 1: The attributes attributes \"associatedVnfcCpId\", \"associatedVipCpId\", \"associatedVirtualCpId\" and \"associatedVnfVirtualLinkId\" are mutually exclusive. Exactly one shall be present. NOTE 2: An external CP instance is not associated to a link port in the cases indicated for the extLinkPorts attribute in clause 6.5.3.26. NOTE 3: Cardinality greater than 1 is only applicable for specific cases where more than one network attachment definition resource is needed to fulfil the connectivity requirements of the external CP, e.g. to build a link redundant mated pair in SR-IOV cases. NOTE 4: When more than one \"netAttDefResourceId\" is indicated, all shall belong to the same namespace.\n",
- "type": "object",
- "required": ["id", "cpdId", "cpProtocolInfo"],
- "oneOf": [{
- "required": ["associatedVnfcCpId"]
- }, {
- "required": ["associatedVipCpId"]
- }, {
- "required": ["associatedVirtualCpId"]
- }, {
- "required": ["associatedVnfVirtualLinkId"]
- }],
- "properties": {
- "id": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "cpdId": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "cpConfigId": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "cpProtocolInfo": {
- "description": "Network protocol information for this CP.\n",
- "type": "array",
- "minItems": 1,
- "items": {
- "description": "This type describes the protocol layer(s) that a CP or SAP uses together with protocol-related information, like addresses. It shall comply with the provisions defined in Table 6.5.3.58-1. NOTE: This attribute allows to signal the addition of further types of layer and protocol in future versions of the present document in a backwards-compatible way. In the current version of the present document, only IP over Ethernet is supported.\n",
- "type": "object",
- "required": ["layerProtocol", "ipOverEthernet"],
- "properties": {
- "layerProtocol": {
- "description": "The identifier of layer(s) and protocol(s) associated to the network address information. Permitted values: - IP_OVER_ETHERNET\n - IP_FOR_VIRTUAL_CP\nSee note.\n",
- "type": "string",
- "enum": ["IP_OVER_ETHERNET", "IP_FOR_VIRTUAL_CP"]
- },
- "ipOverEthernet": {
- "description": "This type represents information about a network address that has been assigned.\nNOTE 1: At least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2: Exactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3: If the Cp instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4: Depending on the NFVI networking infrastructure, the \"segmentationId\" may indicate the actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header of the packets or it may be an identifier used between the application and the NFVI networking infrastructure to identify the network sub-interface of the trunk port in question. In the latter case the NFVI infrastructure will map this local \"segmentationId\" to whatever \"segmentationId\" is actually used by the NFVI's transport technology.\n",
- "type": "object",
- "anyOf": [{
- "required": ["macAddress"]
- }, {
- "required": ["ipAddresses"]
- }],
- "properties": {
- "macAddress": {
- "description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
- "type": "string",
- "format": "MAC"
- },
- "segmentationId": {
- "description": "Identification of the network segment to which the Cp instance connects to. See note 3 and note 4.\n",
- "type": "string"
- },
- "ipAddresses": {
- "description": "Addresses assigned to the CP instance. Each entry represents IP addresses assigned by fixed or dynamic IP address assignment per subnet. See note 1.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": ["type"],
- "oneOf": [{
- "required": ["addresses"]
- }, {
- "required": ["addressRange"]
- }],
- "properties": {
- "type": {
- "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
- "type": "string",
- "enum": ["IPV4", "IPV6"]
- },
- "addresses": {
- "description": "Fixed addresses assigned (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
- "type": "array",
- "items": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- },
- "isDynamic": {
- "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
- "type": "boolean"
- },
- "addressRange": {
- "description": "An IP address range used, e.g., in case of egress connections. Exactly one of \"addresses\" or \"addressRange\" shall be present. See note 2.\n",
- "type": "object",
- "required": ["minAddress", "maxAddress"],
- "properties": {
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- },
- "subnetId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- }
- },
- "type": {
- "description": "The type of the IP addresses\n",
- "type": "string",
- "enum": ["PV4", "PV6"]
- },
- "addresses": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "isDynamic": {
- "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
- "type": "boolean"
- },
- "addressRange": {
- "description": "An IP address range used, e.g. in case of egress connections. See note.\n",
- "type": "object",
- "required": ["minAddress", "maxAddress"],
- "properties": {
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- },
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "subnetId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- },
- "virtualCpAddress": {
- "description": "This type represents information about a network address that has been assigned to a virtual CP.\n",
- "type": "object",
- "required": ["type"],
- "properties": {
- "type": {
- "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
- "type": "string",
- "enum": ["IPV4", "IPV6"]
- },
- "loadBalancerIp": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- }
- }
- }
- },
- "extLinkPortId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "netAttDefResourceId": {
- "description": "Identifier of the \"NetAttDefResourceInfo\" structure that provides the specification of the interface to attach the connection point to a secondary container cluster network. See notes 3 and 4.\nIt shall be present if the external CP is associated to a VNFC realized by one or a set of OS containers and is connected to a secondary container cluster network. It shall not be present otherwise.\n",
- "type": "array",
- "items": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- }
- },
- "metadata": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- },
- "associatedVnfcCpId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "associatedVipCpId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "associatedVirtualCpId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
+ "type": "object",
+ "required": [
+ "type"
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "addresses"
+ ]
+ },
+ {
+ "required": [
+ "addressRange"
+ ]
+ }
+ ],
+ "properties": {
+ "type": {
+ "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
+ },
+ "addresses": {
+ "description": "Fixed addresses assigned (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
+ "type": "array",
+ "items": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ }
+ },
+ "isDynamic": {
+ "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
+ "type": "boolean"
+ },
+ "addressRange": {
+ "description": "An IP address range used, e.g., in case of egress connections. Exactly one of \"addresses\" or \"addressRange\" shall be present. See note 2.\n",
+ "type": "object",
+ "required": [
+ "minAddress",
+ "maxAddress"
+ ],
+ "properties": {
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
},
- "associatedVnfVirtualLinkId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
}
+ }
+ },
+ "subnetId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
}
+ }
}
- },
- "vipCpInfo": {
- "description": "VIP CPs that are part of the VNF instance. Shall be present when that particular VIP CP of the VNFC instance is associated to an external CP of the VNF instance. May be present otherwise.\n",
- "type": "array",
- "items": {
- "description": "This type provides information related to virtual IP (VIP) CP. It shall comply with the provisions defined in table 6.5.3.97 1. NOTE: It is possible that there is no associated VnfcCp because the VIP CP is available but not associated yet.\n",
- "type": "object",
- "required": ["cpInstanceId", "cpdId"],
- "properties": {
- "cpInstanceId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "cpdId": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfExtCpId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "cpProtocolInfo": {
- "description": "Protocol information for this CP. There shall be one cpProtocolInfo for layer 3. There may be one cpProtocolInfo for layer 2.\n",
- "type": "array",
- "items": {
- "description": "This type describes the protocol layer(s) that a CP or SAP uses together with protocol-related information, like addresses. It shall comply with the provisions defined in Table 6.5.3.58-1. NOTE: This attribute allows to signal the addition of further types of layer and protocol in future versions of the present document in a backwards-compatible way. In the current version of the present document, only IP over Ethernet is supported.\n",
- "type": "object",
- "required": ["layerProtocol", "ipOverEthernet"],
- "properties": {
- "layerProtocol": {
- "description": "The identifier of layer(s) and protocol(s) associated to the network address information. Permitted values: - IP_OVER_ETHERNET\n - IP_FOR_VIRTUAL_CP\nSee note.\n",
- "type": "string",
- "enum": ["IP_OVER_ETHERNET", "IP_FOR_VIRTUAL_CP"]
- },
- "ipOverEthernet": {
- "description": "This type represents information about a network address that has been assigned.\nNOTE 1: At least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2: Exactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3: If the Cp instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4: Depending on the NFVI networking infrastructure, the \"segmentationId\" may indicate the actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header of the packets or it may be an identifier used between the application and the NFVI networking infrastructure to identify the network sub-interface of the trunk port in question. In the latter case the NFVI infrastructure will map this local \"segmentationId\" to whatever \"segmentationId\" is actually used by the NFVI's transport technology.\n",
- "type": "object",
- "anyOf": [{
- "required": ["macAddress"]
- }, {
- "required": ["ipAddresses"]
- }],
- "properties": {
- "macAddress": {
- "description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
- "type": "string",
- "format": "MAC"
- },
- "segmentationId": {
- "description": "Identification of the network segment to which the Cp instance connects to. See note 3 and note 4.\n",
- "type": "string"
- },
- "ipAddresses": {
- "description": "Addresses assigned to the CP instance. Each entry represents IP addresses assigned by fixed or dynamic IP address assignment per subnet. See note 1.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": ["type"],
- "oneOf": [{
- "required": ["addresses"]
- }, {
- "required": ["addressRange"]
- }],
- "properties": {
- "type": {
- "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
- "type": "string",
- "enum": ["IPV4", "IPV6"]
- },
- "addresses": {
- "description": "Fixed addresses assigned (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
- "type": "array",
- "items": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- },
- "isDynamic": {
- "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
- "type": "boolean"
- },
- "addressRange": {
- "description": "An IP address range used, e.g., in case of egress connections. Exactly one of \"addresses\" or \"addressRange\" shall be present. See note 2.\n",
- "type": "object",
- "required": ["minAddress", "maxAddress"],
- "properties": {
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- },
- "subnetId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- }
- },
- "type": {
- "description": "The type of the IP addresses\n",
- "type": "string",
- "enum": ["PV4", "PV6"]
- },
- "addresses": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "isDynamic": {
- "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
- "type": "boolean"
- },
- "addressRange": {
- "description": "An IP address range used, e.g. in case of egress connections. See note.\n",
- "type": "object",
- "required": ["minAddress", "maxAddress"],
- "properties": {
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- },
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "subnetId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- },
- "virtualCpAddress": {
- "description": "This type represents information about a network address that has been assigned to a virtual CP.\n",
- "type": "object",
- "required": ["type"],
- "properties": {
- "type": {
- "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
- "type": "string",
- "enum": ["IPV4", "IPV6"]
- },
- "loadBalancerIp": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- }
- }
- }
- },
- "associatedVnfcCpIds": {
- "description": "Identifiers of the VnfcCps that share the virtual IP addresse allocated to the VIP CP instance. See note.\n",
- "type": "array",
- "items": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- }
- },
- "vnfLinkPortId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "metadata": {
- "description": "Allows the OSS/BSS to provide additional parameter(s) to the termination process at the NS level.\n",
- "type": "array",
- "items": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- }
- }
- },
- "virtualCpInfo": {
- "description": "virtual CPs that are part of the VNF instance. Shall be present when a particular virtual CP is associated to an external CP of the VNF instance. May be present otherwise.\n",
- "type": "array",
- "items": {
- "description": "This type represents the information related to a virtual CP instance of a VNF. NOTE: A consumer of the VNF LCM interface can learn the actual VNFC instances implementing the service accessible via the virtual CP instance by querying the \"vnfcResourceInfo\" from the \"InstantiatedVnfInfo\" and filtering by corresponding \"vduId\" values.",
- "type": "object",
- "required": ["cpInstanceId", "cpdId", "resourceHandle", "vduId"],
- "properties": {
- "cpInstanceId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "cpdId": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "resourceHandle": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes instance the vimLevelResourceType is the type of resource, as would correspond to the kind field if the resource is declared in its own Kubernetes manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the claimName field in the Kubernetes manifest, or a compound name built by Kubernetes if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the metadata.name field in Kubernetes manifest. \n",
- "type": "object",
- "required": ["resourceId"],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
- "type": "string"
- },
- "vimLevelAdditionalResourceInfo": {
- "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
- "type": "object",
- "properties": {
- "hostName": {
- "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "persistentVolume": {
- "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "containerNamespace": {
- "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
- "type": "string"
- }
- }
- },
- "vnfExtCpId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "cpProtocolInfo": {
- "description": "Protocol information for this CP. There shall be one cpProtocolInfo for each layer protocol supported.\n",
- "type": "array",
- "items": {
- "description": "This type describes the protocol layer(s) that a CP or SAP uses together with protocol-related information, like addresses. It shall comply with the provisions defined in Table 6.5.3.58-1. NOTE: This attribute allows to signal the addition of further types of layer and protocol in future versions of the present document in a backwards-compatible way. In the current version of the present document, only IP over Ethernet is supported.\n",
- "type": "object",
- "required": ["layerProtocol", "ipOverEthernet"],
- "properties": {
- "layerProtocol": {
- "description": "The identifier of layer(s) and protocol(s) associated to the network address information. Permitted values: - IP_OVER_ETHERNET\n - IP_FOR_VIRTUAL_CP\nSee note.\n",
- "type": "string",
- "enum": ["IP_OVER_ETHERNET", "IP_FOR_VIRTUAL_CP"]
- },
- "ipOverEthernet": {
- "description": "This type represents information about a network address that has been assigned.\nNOTE 1: At least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2: Exactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3: If the Cp instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4: Depending on the NFVI networking infrastructure, the \"segmentationId\" may indicate the actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header of the packets or it may be an identifier used between the application and the NFVI networking infrastructure to identify the network sub-interface of the trunk port in question. In the latter case the NFVI infrastructure will map this local \"segmentationId\" to whatever \"segmentationId\" is actually used by the NFVI's transport technology.\n",
- "type": "object",
- "anyOf": [{
- "required": ["macAddress"]
- }, {
- "required": ["ipAddresses"]
- }],
- "properties": {
- "macAddress": {
- "description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
- "type": "string",
- "format": "MAC"
- },
- "segmentationId": {
- "description": "Identification of the network segment to which the Cp instance connects to. See note 3 and note 4.\n",
- "type": "string"
- },
- "ipAddresses": {
- "description": "Addresses assigned to the CP instance. Each entry represents IP addresses assigned by fixed or dynamic IP address assignment per subnet. See note 1.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": ["type"],
- "oneOf": [{
- "required": ["addresses"]
- }, {
- "required": ["addressRange"]
- }],
- "properties": {
- "type": {
- "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
- "type": "string",
- "enum": ["IPV4", "IPV6"]
- },
- "addresses": {
- "description": "Fixed addresses assigned (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
- "type": "array",
- "items": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- },
- "isDynamic": {
- "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
- "type": "boolean"
- },
- "addressRange": {
- "description": "An IP address range used, e.g., in case of egress connections. Exactly one of \"addresses\" or \"addressRange\" shall be present. See note 2.\n",
- "type": "object",
- "required": ["minAddress", "maxAddress"],
- "properties": {
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- },
- "subnetId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- }
- },
- "type": {
- "description": "The type of the IP addresses\n",
- "type": "string",
- "enum": ["PV4", "PV6"]
- },
- "addresses": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "isDynamic": {
- "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
- "type": "boolean"
- },
- "addressRange": {
- "description": "An IP address range used, e.g. in case of egress connections. See note.\n",
- "type": "object",
- "required": ["minAddress", "maxAddress"],
- "properties": {
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- },
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "subnetId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- },
- "virtualCpAddress": {
- "description": "This type represents information about a network address that has been assigned to a virtual CP.\n",
- "type": "object",
- "required": ["type"],
- "properties": {
- "type": {
- "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
- "type": "string",
- "enum": ["IPV4", "IPV6"]
- },
- "loadBalancerIp": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- }
- }
- }
- },
- "vduId": {
- "description": "Reference to the VDU(s) which implement the service accessible via the virtual CP instance. See note.\n",
- "type": "array",
- "items": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- }
- },
- "additionalServiceInfo": {
- "description": "Additional service identification information of the virtual CP instance.\n",
- "type": "array",
- "items": {
- "description": "This type represents the additional service information of the virtual CP instance used to expose properties of the virtual CP to NFV-MANO.\nNOTE: This attribute shall only be present if additional information is needed to identify the service termination within the VNF, such as for example a URL path information in an HTTP request required to allow a single virtual CP IP address to be used for several HTTP based services that use the same port number.",
- "type": "object",
- "required": ["portInfo"],
- "properties": {
- "portInfo": {
- "description": "Service port numbers exposed by the virtual CP instance.\n",
- "type": "array",
- "items": {
- "description": "This type represents the information related to the service identifying port properties exposed by the virtual CP instance.",
- "type": "object",
- "required": ["name", "protocol", "port", "isPortConfigurable"],
- "properties": {
- "name": {
- "description": "The name of the port exposed by the virtual CP instance.\n",
- "type": "string"
- },
- "protocol": {
- "description": "The L4 protocol for this port exposed by the virtual CP instance. Permitted values:\n - TCP\n - UDP\n - SCTP\n",
- "type": "string",
- "enum": ["TCP", "UDP", "SCTP"]
- },
- "port": {
- "description": "The L4 port number exposed by the virtual CP instance.\n",
- "type": "integer"
- },
- "isPortConfigurable": {
- "description": "Specifies whether the port attribute value is allowed to be configurable.\n",
- "type": "boolean"
- }
- }
- }
- },
- "serviceInfo": {
- "description": "Service matching information exposed by the virtual CP instance. See note.\n",
- "type": "array",
- "items": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- }
- }
- },
- "metadata": {
- "description": "Metadata about this virtual CP instance.\n",
- "type": "array",
- "items": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- }
- }
- },
- "extVirtualLinkInfo": {
- "description": "Information about the external VLs the VNF instance is connected to.\n",
- "type": "array",
- "items": {
- "description": "This type represents information about an VNF external VL.",
- "type": "object",
- "required": ["id", "resourceHandle", "currentVnfExtCpData"],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceHandle": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes instance the vimLevelResourceType is the type of resource, as would correspond to the kind field if the resource is declared in its own Kubernetes manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the claimName field in the Kubernetes manifest, or a compound name built by Kubernetes if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the metadata.name field in Kubernetes manifest. \n",
- "type": "object",
- "required": ["resourceId"],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
- "type": "string"
- },
- "vimLevelAdditionalResourceInfo": {
- "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
- "type": "object",
- "properties": {
- "hostName": {
- "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "persistentVolume": {
- "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "containerNamespace": {
- "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
- "type": "string"
- }
- }
- },
- "extLinkPorts": {
- "description": "Link ports of this VL.\n",
- "type": "array",
- "items": {
- "description": "This type represents information about a link port of an external VL, i.e. a port providing connectivity for the VNF to an NS VL. NOTE 1: The use cases UC#4 and UC#5 in Annex A.4 of ETSI GS NFV-IFA 007 provide examples for such a configuration. NOTE 2: The value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\" attribute.\n",
- "type": "object",
- "required": ["id", "resourceHandle"],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceHandle": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes instance the vimLevelResourceType is the type of resource, as would correspond to the kind field if the resource is declared in its own Kubernetes manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the claimName field in the Kubernetes manifest, or a compound name built by Kubernetes if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the metadata.name field in Kubernetes manifest. \n",
- "type": "object",
- "required": ["resourceId"],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
- "type": "string"
- },
- "vimLevelAdditionalResourceInfo": {
- "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
- "type": "object",
- "properties": {
- "hostName": {
- "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "persistentVolume": {
- "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "containerNamespace": {
- "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
- "type": "string"
- }
- }
- },
- "cpInstanceId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "secondaryCpInstanceId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "trunkResourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- }
- },
- "extNetAttDefResource": {
- "description": "Network attachment definition resources that provide the specification of the interface to attach connection points to this VL.\n",
- "type": "array",
- "items": {
- "description": "This type represents the information related to a network attachment definition resource that provides the specification of the interface used to connect one or multiple connection points to a secondary container cluster network\n",
- "type": "object",
- "required": ["netAttDefResourceInfoId", "netAttDefResource"],
- "properties": {
- "netAttDefResourceInfoId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "netAttDefResource": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes instance the vimLevelResourceType is the type of resource, as would correspond to the kind field if the resource is declared in its own Kubernetes manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the claimName field in the Kubernetes manifest, or a compound name built by Kubernetes if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the metadata.name field in Kubernetes manifest. \n",
- "type": "object",
- "required": ["resourceId"],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
- "type": "string"
- },
- "vimLevelAdditionalResourceInfo": {
- "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
- "type": "object",
- "properties": {
- "hostName": {
- "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "persistentVolume": {
- "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "containerNamespace": {
- "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
- "type": "string"
- }
- }
- },
- "associatedExtCpId": {
- "description": "Identifier of the external CP of the VNF associated to this network attachment definition resource. Shall be present when the network attachment definition resource is used for external connectivity by the VNF\n",
- "type": "array",
- "items": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- }
- },
- "associatedVnfcCpId": {
- "description": "Identifier of the VNFC CP of the VNF associated to this network attachment definition resource. May be present when the network attachment definition resource is used for internal connectivity by the VNF.\n",
- "type": "array",
- "items": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- }
- }
- }
- }
- },
- "currentVnfExtCpData": {
- "description": "This type represents configuration information for external CPs created from a CPD.\nNOTE 1: In case this identifier refers to a CPD with trunking enabled, the external CP instances created from this CPD will represent ports in a trunk. NOTE 2: The map entry value shall be set to \"null\" in order to delete a \"VnfExtCpConfig\" entry identified by a particular key value from the map, i.e. for the disconnection of an existing external CP instance addressed by cpInstanceId in the deleted map entry from a particular external virtual link, and deletion of that instance in case it represents a subport. Deleting the last key from the map removes the affected instance of the \"VnfExtCpData\" structure from its parent data structure. NOTE 3: Within one VNF instance, all VNFC instances created from a particular VDU have the same external connectivity. Thus, given a particular value of the \"cpdId' attribute, there shall be one \"cpConfig\" entry for each VNFC instance that has been or can be created from a VDU which includes a CPD identified by the \"cpdId\" attribute. If the cpConfig represents a subport in a trunk, all \"cpConfig\" entries in this list shall have the same segmentationId, which means they are connected to the same set of external VLs via the trunk. NOTE 4: If, as defined by the input parameters of a \"ChangeVnfFlavour\", \"ChangeExtVnfConnectivity\" or \"ChangeCurrentVnfPkg\" operation, a cpConfig map entry identified by a particular map key value is moved into another \"ExtVirtualLinkData\" or \"VnfExtCpData\" structure, this particular cpConfig map entry may be used by an external CP instance different than the one that has used it before the operation, or by no external CP instance at all. Renaming a CPD identifier during the \"changeCurrentVnfPkg\" operation does not count as moving the related \"cpConfig\" map entries to a new \"extCpData\" structure.\n",
- "type": "object",
- "required": ["cpdId"],
- "properties": {
- "cpdId": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "cpConfig": {
- "description": "Map of instance data that need to be configured on the CP instances created from the respective CPD. The key of the map which identifies the individual VnfExtCpConfig entries is of type \"IdentifierInVnf\" and is managed by the API consumer. The entries shall be applied by the VNFM according to the rules of JSON Merge Patch (see IETF RFC 7396 [11]). See notes 2, 3 and 4.\n",
- "type": "object",
- "additionalProperties": {
- "description": "This type represents an externally provided link port, or a network attachment definition resource of secondary container cluster network, or network address information per instance of a VNF external connection point. In the case of VM-based deployment of the VNFC exposing the external CP: In case a link port is provided, the NFVO shall use that link port when connecting the VNF external CP to the external VL. In case a link port is not provided, the NFVO or VNFM shall create a link port on the external VL, and use that link port to connect the VNF external CP to the external VL. In the case of container-based deployment of the VNFC exposing the external CP, the NFVO and VNFM shall use the network attachment definition resource of secondary container cluster network when connecting the CP to the external VL.\nNOTE 1: The following conditions apply to the attributes \"linkPortId\" and \"cpProtocolData\" for an external CP instance connected or to be connected to a virtual network not\n categorized as secondary container cluster network:\n - At least one of the \"linkPortId\" and \"cpProtocolData\" attributes shall be present for\n an external CP instance representing a subport that is to be created, or an external CP instance\n that is to be created by creating the corresponding VNFC or VNF instance during the current or\n a subsequent LCM operation, or for an existing external CP instance that is to be re-configured\n or added to a particular external virtual link.\n - If the \"cpProtocolData\" attribute is absent, the \"linkPortId\" attribute shall be provided\n referencing a pre-created link port with pre-configured address information.\n - If both \"cpProtocolData\" and \"linkportId\" are provided, the API consumer shall ensure that\n the cpProtocolData can be used with the pre-created link port referenced by \"linkPortId\".\nNOTE 2: In case the NFVO manages its own identifier space, the NFVO may remap this identifier when communicating with the VNFM. If the NFVO knows that there can be an identifier collision when communicating with the VNFM by using the identifier from the OSS/BSS, the NFVO shall remap it. NOTE 3: The following conditions apply to the attributes netAttDefResourceId and cpProtocolData for an external CP instance connected or to be connected to a secondary container cluster network; The \"netAttDefResourceId\" and \"cpProtocolData\" attributes shall both be absent for the deletion of an existing external CP instance addressed by \"cpInstanceId\". At least one of these attributes shall be present for a to-be-created external CP instance or an existing external CP instance. NOTE 4: Cardinality greater than 1 is only applicable for specific cases where more than one network attachment definition resource is needed to fulfil the connectivity requirements of the external CP, e.g. to build a link redundant mated pair in SR-IOV cases. When more than one \"netAttDefResourceId\" is indicated, all shall belong to the same namespace as defined by the corresponding \"netAttDefResourceNamespace\" attribute in the \"NetAttDefResourceData\". NOTE 5: Either \"linkPortId\" or \"netAttDefResourceId\" may be included, but not both.\n",
- "type": "object",
- "oneOf": [{
- "required": ["linkPortId"]
- }, {
- "required": ["cpProtocolData"]
- }],
- "properties": {
- "parentCpConfigId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "linkPortId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "createExtLinkPort": {
- "description": "Indicates the need to create a dedicated link port for the external CP. If set to True, a link port is created. If set to False, no link port is created. This attribute is only applicable for external CP instances without a floating IP address that expose a VIP CP instance for which a dedicated IP address is allocated. It shall be present in that case and shall be absent otherwise.\n",
- "type": "boolean"
- },
- "cpProtocolData": {
- "description": "Parameters for configuring the network protocols on the link port that connects the CP to a VL. See notes 1 and 3.\n",
- "type": "array",
- "items": {
- "description": "This type represents network protocol data.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the present document in a backwards-compatible way. In the current version of the present document, only IP over Ethernet is supported.\n",
- "type": "object",
- "required": ["layerProtocol"],
- "properties": {
- "layerProtocol": {
- "description": "Identifier of layer(s) and protocol(s). Permitted values: - IP_OVER_ETHERNET - IP_FOR_VIRTUAL_CP See note.\n",
- "type": "string",
- "enum": ["IP_OVER_ETHERNET", "IP_FOR_VIRTUAL_CP"]
- },
- "ipOverEthernet": {
- "description": "This type represents network address data for IP over Ethernet. NOTE 1: At least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2: Exactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present. NOTE 3: If the CP instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4: Depending on the NFVI networking infrastructure, the \"segmentationId\" may indicate the actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header of the packets or it may be an identifier used between the application and the NFVI networking infrastructure to identify the network sub-interface of the trunk port in question. In the latter case the NFVI infrastructure will map this local \"segmentationId\" to whatever \"segmentationId\" is actually used by the NFVI's transport technology.\n",
- "type": "object",
- "anyOf": [{
- "required": ["ipAddresses"]
- }, {
- "required": ["macAddress"]
- }],
- "properties": {
- "macAddress": {
- "description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
- "type": "string",
- "format": "MAC"
- },
- "segmentationType": {
- "description": "Specifies the encapsulation type for the traffics coming in and out of the trunk subport. Permitted values are: - VLAN: The subport uses VLAN as encapsulation type. - INHERIT: The subport gets its segmentation type from the network it is connected to. This attribute may be present for CP instances that represent subports in a trunk and shall be absent otherwise. If this attribute is not present for a subport CP instance, default value VLAN shall be used.\n",
- "type": "string",
- "enum": ["VLAN", "INHERIT"]
- },
- "segmentationId": {
- "description": "Identification of the network segment to which the CP instance connects to. See note 3 and note 4.\n",
- "type": "string"
- },
- "ipAddresses": {
- "description": "List of IP addresses to assign to the CP instance. Each entry represents IP address data for fixed or dynamic IP address assignment per subnet. If this attribute is not present, no IP address shall be assigned. See note 1.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": ["type"],
- "oneOf": [{
- "required": ["fixedAddresses"]
- }, {
- "required": ["numDynamicAddresses"]
- }, {
- "required": ["addressRange"]
- }],
- "properties": {
- "type": {
- "description": "The type of the IP addresses. Permitted values: - IPV4\n - IPV6\n",
- "type": "string",
- "enum": ["IPV4", "IPV6"]
- },
- "fixedAddresses": {
- "description": "Fixed addresses to assign (from the subnet defined by \"subnetId\" if provided). Exactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present.\n",
- "type": "array",
- "items": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- },
- "numDynamicAddresses": {
- "description": "Number of dynamic addresses to assign (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
- "type": "integer"
- },
- "addressRange": {
- "description": "An IP address range to be used, e.g. in case of egress connections. In case this attribute is present, IP addresses from the range will be used.\n",
- "type": "object",
- "required": ["minAddress", "maxAddress"],
- "properties": {
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- },
- "subnetId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- }
- }
- }
- },
- "virtualCpAddress": {
- "description": "This type represents network address data for a virtual CP. It shall comply with the provisions defined in table 6.5.3.12a-1.\n",
- "type": "object",
- "required": ["type"],
- "properties": {
- "type": {
- "description": "Identifier of layer(s) and protocol(s). Permitted values: IP_OVER_ETHERNET.\n",
- "type": "string",
- "enum": ["IPV4", "IPV6"]
- },
- "loadBalancerIp": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- }
- }
- }
- },
- "netAttDefResourceId": {
- "description": "Identifier of the \"NetAttDefResourceData\" structure that provides the specification of the interface to attach the external CP to a secondary container cluster network. It is only applicable if the external CP is connected or to be connected to a secondary container cluster network. It shall not be present if the external CP is related to a virtual network not categorized as secondary container cluster network. See notes 3, 4 and 5.\n",
- "type": "array",
- "items": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- }
- }
- }
- }
- }
- }
- }
- }
- }
- },
- "extManagedVirtualLinkInfo": {
- "description": "Information about the externally-managed internal VLs of the VNF instance. See note 4 and note 5.\n",
- "type": "array",
- "items": {
- "description": "This type provides information about an externally-managed internal virtual link for VNFs\n",
- "type": "object",
- "required": ["id", "vnfVirtualLinkDescId", "networkResource"],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfVirtualLinkDescId": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "networkResource": {
- "description": "Reference to the VirtualNetwork resource or multi-site connectivity service providing this VL.\n",
- "type": "array",
- "items": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes instance the vimLevelResourceType is the type of resource, as would correspond to the kind field if the resource is declared in its own Kubernetes manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the claimName field in the Kubernetes manifest, or a compound name built by Kubernetes if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the metadata.name field in Kubernetes manifest. \n",
- "type": "object",
- "required": ["resourceId"],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
- "type": "string"
- },
- "vimLevelAdditionalResourceInfo": {
- "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
- "type": "object",
- "properties": {
- "hostName": {
- "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "persistentVolume": {
- "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "containerNamespace": {
- "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
- "type": "string"
- }
- }
- }
- },
- "vnfLinkPorts": {
- "description": "Link ports of this VL.\n",
- "type": "array",
- "items": {
- "type": "object",
- "description": "This type represents a link port of an internal VL of a VNF. It shall comply with the provisions defined in table 6.5.3.64-1.\nNOTE 1: Either cpInstanceId with cpInstanceType set to \"EXT_CP\" or any combination of cpInstanceId with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId (i.e. one or both of them) shall be present for a VnfLinkPortInfo. In case both cpInstanceId with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId are present, the two different CP instances share the linkport.\n",
- "required": ["id", "resourceHandle"],
- "properties": {
- "id": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "resourceHandle": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes instance the vimLevelResourceType is the type of resource, as would correspond to the kind field if the resource is declared in its own Kubernetes manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the claimName field in the Kubernetes manifest, or a compound name built by Kubernetes if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the metadata.name field in Kubernetes manifest. \n",
- "type": "object",
- "required": ["resourceId"],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
- "type": "string"
- },
- "vimLevelAdditionalResourceInfo": {
- "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
- "type": "object",
- "properties": {
- "hostName": {
- "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "persistentVolume": {
- "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "containerNamespace": {
- "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
- "type": "string"
- }
- }
- },
- "cpInstanceId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "cpInstanceType": {
- "description": "Type of the CP instance that is identified by cpInstanceId. Shall be present if \"cpInstanceId\" is present, and shall be absent otherwise. Permitted values: * VNFC_CP: The link port is connected to a VNFC CP * EXT_CP: The link port is associated to an external CP. See note 1.\n",
- "type": "string",
- "enum": ["VNFC_CP", "EXT_CP"]
- },
- "vipCpInstanceId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "trunkResourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- }
- },
- "vnfNetAttDefResource": {
- "description": "This type represents the information related to a network attachment definition resource that provides the specification of the interface used to connect one or multiple connection points to a secondary container cluster network\n",
- "type": "object",
- "required": ["netAttDefResourceInfoId", "netAttDefResource"],
- "properties": {
- "netAttDefResourceInfoId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "netAttDefResource": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes instance the vimLevelResourceType is the type of resource, as would correspond to the kind field if the resource is declared in its own Kubernetes manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the claimName field in the Kubernetes manifest, or a compound name built by Kubernetes if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the metadata.name field in Kubernetes manifest. \n",
- "type": "object",
- "required": ["resourceId"],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
- "type": "string"
- },
- "vimLevelAdditionalResourceInfo": {
- "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
- "type": "object",
- "properties": {
- "hostName": {
- "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "persistentVolume": {
- "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "containerNamespace": {
- "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
- "type": "string"
- }
- }
- },
- "associatedExtCpId": {
- "description": "Identifier of the external CP of the VNF associated to this network attachment definition resource. Shall be present when the network attachment definition resource is used for external connectivity by the VNF\n",
- "type": "array",
- "items": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- }
- },
- "associatedVnfcCpId": {
- "description": "Identifier of the VNFC CP of the VNF associated to this network attachment definition resource. May be present when the network attachment definition resource is used for internal connectivity by the VNF.\n",
- "type": "array",
- "items": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- }
- }
- }
- },
- "extManagedMultisiteVirtualLinkId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- }
- }
- }
- },
- "monitoringParameters": {
- "description": "Performance metrics tracked by the VNFM (e.g. for auto-scaling purposes) as identified by the VNF provider in the VNFD.\n",
- "type": "array",
- "items": {
- "description": "This type represents a monitoring parameter that is tracked by the VNFM, for example, for auto-scaling purposes. It shall comply with the provisions defined in Table 6.5.3.69-1.\n",
- "type": "object",
- "required": ["id", "performanceMetric"],
- "properties": {
- "id": {
- "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "name": {
- "description": "Human readable name of the monitoring parameter, as defined in the VNFD.\n",
- "type": "string"
- },
- "performanceMetric": {
- "description": "Performance metric that is monitored. This attribute shall contain the related \"Measurement Name\" value as defined in clause 7.2 of ETSI GS NFV-IFA 027.\n",
- "type": "string"
- }
- }
+ },
+ "type": {
+ "description": "The type of the IP addresses\n",
+ "type": "string",
+ "enum": [
+ "PV4",
+ "PV6"
+ ]
+ },
+ "addresses": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "isDynamic": {
+ "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
+ "type": "boolean"
+ },
+ "addressRange": {
+ "description": "An IP address range used, e.g. in case of egress connections. See note.\n",
+ "type": "object",
+ "required": [
+ "minAddress",
+ "maxAddress"
+ ],
+ "properties": {
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ }
}
- },
- "localizationLanguage": {
- "description": "Information about localization language of the VNF (includes e.g. strings in the VNFD). The localization languages supported by a VNF can be declared in the VNFD, and localization language selection can take place at instantiation time. The value shall comply with the format defined in IETF RFC 5646.\n",
+ },
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "subnetId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
"type": "string"
- },
- "vnfcResourceInfo": {
- "description": "Information about the virtualised compute and storage resources used by the VNFCs of the VNF instance.\n",
- "type": "array",
- "items": {
- "description": "This type represents the information on virtualised compute and storage resources used by a VNFC in a VNF instance. This feature addresses the following capabilities: NFV Architecture support for VNFs which follow cloud-native design principles. Enhance NFV-MANO capabilities to support container technologies. Enhance NFV-MANO capabilities for container management and orchestration. Enhance information model for containerized VNFs both using bare metal or nested virtualization technologies.\nNOTE 1: ETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on TOSCA specifications. NOTE 2: A VNFC CP is \"connected to\" an external CP if the VNFC CP is connected to an internal VL that exposes an external CP. A VNFC CP is \"exposed as\" an external CP if it is connected directly to an external VL. NOTE 3: The information can be omitted because it is already available as part of the external CP information. NOTE 4: Cardinality greater than 1 is only applicable for specific cases where more than one network attachment definition resource is needed to fulfil the connectivity requirements of the internal CP, e.g. to build a link redundant mated pair in SR-IOV cases. NOTE 5: When more than one \"netAttDefResourceId\" is indicated, all shall belong to the same namespace.\n",
- "type": "object",
- "required": ["id", "vduId", "computeResource"],
- "properties": {
- "id": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vduId": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "computeResource": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes instance the vimLevelResourceType is the type of resource, as would correspond to the kind field if the resource is declared in its own Kubernetes manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the claimName field in the Kubernetes manifest, or a compound name built by Kubernetes if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the metadata.name field in Kubernetes manifest. \n",
- "type": "object",
- "required": ["resourceId"],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
- "type": "string"
- },
- "vimLevelAdditionalResourceInfo": {
- "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
- "type": "object",
- "properties": {
- "hostName": {
- "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "persistentVolume": {
- "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "containerNamespace": {
- "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
- "type": "string"
- }
- }
- },
- "storageResourceIds": {
- "description": "References to the VirtualStorage resources or references to Storage MCIOs. The value refers to a VirtualStorageResourceInfo item in the VnfInstance.\n",
- "type": "array",
- "items": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- }
- },
- "reservationId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfcCpInfo": {
- "description": "CPs of the VNFC instance. Shall be present when that particular CP of the VNFC instance is exposed as an external CP of the VNF instance or is connected to an external CP of the VNF instance.See note 2. May be present otherwise.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": ["id", "cpdId"],
- "properties": {
- "id": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "cpdId": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "vnfExtCpId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "cpProtocolInfo": {
- "description": "Network protocol information for this CP. May be omitted if the VNFC CP is exposed as an external CP. See note 3.\n",
- "type": "array",
- "items": {
- "description": "This type describes the protocol layer(s) that a CP or SAP uses together with protocol-related information, like addresses. It shall comply with the provisions defined in Table 6.5.3.58-1. NOTE: This attribute allows to signal the addition of further types of layer and protocol in future versions of the present document in a backwards-compatible way. In the current version of the present document, only IP over Ethernet is supported.\n",
- "type": "object",
- "required": ["layerProtocol", "ipOverEthernet"],
- "properties": {
- "layerProtocol": {
- "description": "The identifier of layer(s) and protocol(s) associated to the network address information. Permitted values: - IP_OVER_ETHERNET\n - IP_FOR_VIRTUAL_CP\nSee note.\n",
- "type": "string",
- "enum": ["IP_OVER_ETHERNET", "IP_FOR_VIRTUAL_CP"]
- },
- "ipOverEthernet": {
- "description": "This type represents information about a network address that has been assigned.\nNOTE 1: At least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2: Exactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3: If the Cp instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4: Depending on the NFVI networking infrastructure, the \"segmentationId\" may indicate the actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header of the packets or it may be an identifier used between the application and the NFVI networking infrastructure to identify the network sub-interface of the trunk port in question. In the latter case the NFVI infrastructure will map this local \"segmentationId\" to whatever \"segmentationId\" is actually used by the NFVI's transport technology.\n",
- "type": "object",
- "anyOf": [{
- "required": ["macAddress"]
- }, {
- "required": ["ipAddresses"]
- }],
- "properties": {
- "macAddress": {
- "description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
- "type": "string",
- "format": "MAC"
- },
- "segmentationId": {
- "description": "Identification of the network segment to which the Cp instance connects to. See note 3 and note 4.\n",
- "type": "string"
- },
- "ipAddresses": {
- "description": "Addresses assigned to the CP instance. Each entry represents IP addresses assigned by fixed or dynamic IP address assignment per subnet. See note 1.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": ["type"],
- "oneOf": [{
- "required": ["addresses"]
- }, {
- "required": ["addressRange"]
- }],
- "properties": {
- "type": {
- "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
- "type": "string",
- "enum": ["IPV4", "IPV6"]
- },
- "addresses": {
- "description": "Fixed addresses assigned (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
- "type": "array",
- "items": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- },
- "isDynamic": {
- "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
- "type": "boolean"
- },
- "addressRange": {
- "description": "An IP address range used, e.g., in case of egress connections. Exactly one of \"addresses\" or \"addressRange\" shall be present. See note 2.\n",
- "type": "object",
- "required": ["minAddress", "maxAddress"],
- "properties": {
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- },
- "subnetId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- }
- },
- "type": {
- "description": "The type of the IP addresses\n",
- "type": "string",
- "enum": ["PV4", "PV6"]
- },
- "addresses": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "isDynamic": {
- "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
- "type": "boolean"
- },
- "addressRange": {
- "description": "An IP address range used, e.g. in case of egress connections. See note.\n",
- "type": "object",
- "required": ["minAddress", "maxAddress"],
- "properties": {
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- },
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "subnetId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- },
- "virtualCpAddress": {
- "description": "This type represents information about a network address that has been assigned to a virtual CP.\n",
- "type": "object",
- "required": ["type"],
- "properties": {
- "type": {
- "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
- "type": "string",
- "enum": ["IPV4", "IPV6"]
- },
- "loadBalancerIp": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- }
- }
- }
- },
- "parentCpId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "vnfLinkPortId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "netAttDefResourceId": {
- "description": "Identifier of the \"NetAttDefResourceInfo\" structure that provides the specification of the interface to attach the connection point to a secondary container cluster network. See notes 4 and 5. It shall be present if the internal CP is associated to a VNFC realized by one or a set of OS containers and is connected to a secondary container cluster network. It shall not be present otherwise.\n",
- "type": "array",
- "items": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- }
- },
- "metadata": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- }
- },
- "metadata": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- }
- },
- "vnfVirtualLinkResourceInfo": {
- "description": "Information about the virtualised network resources used by the VLs of the VNF instance. See note 5.\n",
- "type": "array",
- "items": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by an internal VL instance in a VNF instance.\n",
- "type": "object",
- "required": ["id", "vnfVirtualLinkDescId", "networkResource"],
- "properties": {
- "id": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfVirtualLinkDescId": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "networkResource": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes instance the vimLevelResourceType is the type of resource, as would correspond to the kind field if the resource is declared in its own Kubernetes manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the claimName field in the Kubernetes manifest, or a compound name built by Kubernetes if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the metadata.name field in Kubernetes manifest. \n",
- "type": "object",
- "required": ["resourceId"],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
- "type": "string"
- },
- "vimLevelAdditionalResourceInfo": {
- "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
- "type": "object",
- "properties": {
- "hostName": {
- "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "persistentVolume": {
- "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "containerNamespace": {
- "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
- "type": "string"
- }
- }
- },
- "reservationId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfLinkPorts": {
- "description": "Links ports of this VL. Shall be present when the linkPort is used for external connectivity by the VNF (refer to VnfLinkPortInfo). May be present otherwise.\n",
- "type": "array",
- "items": {
- "type": "object",
- "description": "This type represents a link port of an internal VL of a VNF. It shall comply with the provisions defined in table 6.5.3.64-1.\nNOTE 1: Either cpInstanceId with cpInstanceType set to \"EXT_CP\" or any combination of cpInstanceId with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId (i.e. one or both of them) shall be present for a VnfLinkPortInfo. In case both cpInstanceId with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId are present, the two different CP instances share the linkport.\n",
- "required": ["id", "resourceHandle"],
- "properties": {
- "id": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "resourceHandle": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes instance the vimLevelResourceType is the type of resource, as would correspond to the kind field if the resource is declared in its own Kubernetes manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the claimName field in the Kubernetes manifest, or a compound name built by Kubernetes if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the metadata.name field in Kubernetes manifest. \n",
- "type": "object",
- "required": ["resourceId"],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
- "type": "string"
- },
- "vimLevelAdditionalResourceInfo": {
- "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
- "type": "object",
- "properties": {
- "hostName": {
- "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "persistentVolume": {
- "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "containerNamespace": {
- "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
- "type": "string"
- }
- }
- },
- "cpInstanceId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "cpInstanceType": {
- "description": "Type of the CP instance that is identified by cpInstanceId. Shall be present if \"cpInstanceId\" is present, and shall be absent otherwise. Permitted values: * VNFC_CP: The link port is connected to a VNFC CP * EXT_CP: The link port is associated to an external CP. See note 1.\n",
- "type": "string",
- "enum": ["VNFC_CP", "EXT_CP"]
- },
- "vipCpInstanceId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "trunkResourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- }
- },
- "metadata": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- }
- },
- "virtualStorageResourceInfo": {
- "description": "Information on the virtualised storage resource(s) used as storage for the VNF instance.\n",
- "type": "array",
- "items": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance.\n",
- "type": "object",
- "required": ["id", "virtualStorageDescId", "storageResource"],
- "properties": {
- "id": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "virtualStorageDescId": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "storageResource": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes instance the vimLevelResourceType is the type of resource, as would correspond to the kind field if the resource is declared in its own Kubernetes manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the claimName field in the Kubernetes manifest, or a compound name built by Kubernetes if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the metadata.name field in Kubernetes manifest. \n",
- "type": "object",
- "required": ["resourceId"],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
- "type": "string"
- },
- "vimLevelAdditionalResourceInfo": {
- "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
- "type": "object",
- "properties": {
- "hostName": {
- "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "persistentVolume": {
- "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "containerNamespace": {
- "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
- "type": "string"
- }
- }
- },
- "reservationId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "metadata": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- }
- },
- "mcioInfo": {
- "description": "Information on the MCIO(s) representing VNFC instance(s) realized by one or a set of OS containers and created from the same VDU for the VNF instance.\n",
- "type": "array",
- "items": {
- "description": "This type provides information about an MCIO representing the set of VNFC instances realized by one or a set of OS containers which have been created based on the same VDU.\nNOTE 1 The type of MCIO as specified in the declarative descriptor of the MCIO, and that can be read from the CISM. EXAMPLE: In case of MCIOs managed by Kubernetes, the type of MCIO corresponds to the kind property of the declarative descriptor. NOTE 2 If the attribute additionalInfo is present, it may contain runtime information on the actual and desired state of the MCIO(s). NOTE 3 When the container infrastructure service is a Kubernetes instance, the mcioId is the combined values from the kind and name fields of the Kubernetes resource object, separated by a slash. Example: \"Deployment/abcd\". NOTE 4 When the container infrastructure service is a Kubernetes instance, the mcioName is the name field of the resource object.",
- "type": "object",
- "required": ["mcioId", "mcioName", "mcioNamespace", "vduId", "cismId", "mcioType", "desiredInstances", "availableInstances"],
- "properties": {
- "mcioId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "mcioName": {
- "description": "Human readable name of this MCIO. See note 4.\n",
- "type": "string"
- },
- "mcioNamespace": {
- "description": "Namespace of this MCIO.\n",
- "type": "string"
- },
- "vduId": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "cismId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "mcioType": {
- "description": "The type of MCIO. Specific values, their semantics and associated MCIO types are defined in clause 6.5.4.13. Additional values are also permitted. See note 1.\n",
- "type": "string"
- },
- "desiredInstances": {
- "description": "Number of desired MCIO instances.\n",
- "type": "integer"
- },
- "availableInstances": {
- "description": "Number of available MCIO instances\n",
- "type": "integer"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
+ }
+ }
+ },
+ "virtualCpAddress": {
+ "description": "This type represents information about a network address that has been assigned to a virtual CP.\n",
+ "type": "object",
+ "required": [
+ "type"
+ ],
+ "properties": {
+ "type": {
+ "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
+ },
+ "loadBalancerIp": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.",
+ "type": "string"
+ }
+ }
+ }
+ }
+ }
+ },
+ "vduId": {
+ "description": "Reference to the VDU(s) which implement the service accessible via the virtual CP instance. See note.\n",
+ "type": "array",
+ "items": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
+ "type": "string"
+ }
+ },
+ "additionalServiceInfo": {
+ "description": "Additional service identification information of the virtual CP instance.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the additional service information of the virtual CP instance used to expose properties of the virtual CP to NFV-MANO.\nNOTE: This attribute shall only be present if additional information is needed to identify the service termination within the VNF, such as for example a URL path information in an HTTP request required to allow a single virtual CP IP address to be used for several HTTP based services that use the same port number.",
+ "type": "object",
+ "required": [
+ "portInfo"
+ ],
+ "properties": {
+ "portInfo": {
+ "description": "Service port numbers exposed by the virtual CP instance.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the information related to the service identifying port properties exposed by the virtual CP instance.",
+ "type": "object",
+ "required": [
+ "name",
+ "protocol",
+ "port",
+ "isPortConfigurable"
+ ],
+ "properties": {
+ "name": {
+ "description": "The name of the port exposed by the virtual CP instance.\n",
+ "type": "string"
+ },
+ "protocol": {
+ "description": "The L4 protocol for this port exposed by the virtual CP instance.\n Permitted values:\n - TCP\n - UDP\n - SCTP\n",
+ "type": "string",
+ "enum": [
+ "TCP",
+ "UDP",
+ "SCTP"
+ ]
+ },
+ "port": {
+ "description": "The L4 port number exposed by the virtual CP instance.\n",
+ "type": "integer"
+ },
+ "isPortConfigurable": {
+ "description": "Specifies whether the port attribute value is allowed to be configurable.\n",
+ "type": "boolean"
}
+ }
+ }
+ },
+ "serviceInfo": {
+ "description": "Service matching information exposed by the virtual CP instance. See note.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
}
+ }
}
+ }
},
"metadata": {
+ "description": "Metadata about this virtual CP instance.\n",
+ "type": "array",
+ "items": {
"description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
"type": "object"
- },
- "extensions": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
+ }
}
+ }
}
- }
- },
- "pnfInfo": {
- "description": "Information on the PNF(s) that are part of the NS instance.\n",
- "type": "array",
- "items": {
- "description": "This type represents the information about a PNF that is part of an NS instance. It shall comply with the provisions defined in Table 6.5.3.13-1.\n",
- "type": "object",
- "required": ["pnfId", "pnfdId", "pnfdInfoId", "pnfProfileId"],
- "properties": {
- "pnfId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
+ },
+ "extVirtualLinkInfo": {
+ "description": "Information about the external VLs the VNF instance is connected to.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents information about an VNF external VL.",
+ "type": "object",
+ "required": [
+ "id",
+ "resourceHandle",
+ "currentVnfExtCpData"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
},
- "pnfName": {
- "description": "Name of the PNF.\n",
- "type": "string"
+ "resourceHandle": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would correspond to the ‘kind’ field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the ‘claimName’ field in the Kubernetes® manifest, or a compound name built by Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the ‘metadata.name’ field in Kubernetes® manifest. \n",
+ "type": "object",
+ "required": [
+ "resourceId"
+ ],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceProviderId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "type": "string"
+ },
+ "vimLevelAdditionalResourceInfo": {
+ "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
+ "type": "object",
+ "properties": {
+ "hostName": {
+ "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "persistentVolume": {
+ "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ },
+ "containerNamespace": {
+ "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise. \n",
+ "type": "string"
+ }
+ }
},
- "pnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
+ "extLinkPorts": {
+ "description": "Link ports of this VL.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents information about a link port of an external VL, i.e. a port providing connectivity for the VNF to an NS VL. NOTE 1: The use cases UC#4 and UC#5 in Annex A.4 of ETSI GS NFV-IFA 007 provide examples for such a configuration. NOTE 2: The value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\" attribute.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "resourceHandle"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceHandle": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would correspond to the ‘kind’ field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the ‘claimName’ field in the Kubernetes® manifest, or a compound name built by Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the ‘metadata.name’ field in Kubernetes® manifest. \n",
+ "type": "object",
+ "required": [
+ "resourceId"
+ ],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceProviderId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "type": "string"
+ },
+ "vimLevelAdditionalResourceInfo": {
+ "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
+ "type": "object",
+ "properties": {
+ "hostName": {
+ "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "persistentVolume": {
+ "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ },
+ "containerNamespace": {
+ "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise. \n",
+ "type": "string"
+ }
+ }
+ },
+ "cpInstanceId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "secondaryCpInstanceId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "trunkResourceId": {
+ "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ }
+ }
+ }
},
- "versionDependency": {
- "description": "Describes version dependencies currently valid for the PNF. Identifies versions of descriptors of other constituents in the NSD upon which the PNF depends. The dependencies may be described for the PNFD referenced in this PnfInfo with pnfdId and for PNFDs with the same PnfdExtInvariantId. There shall not be more than one versionDependency present with the same dependentConstituentId.\n",
- "type": "array",
- "items": {
- "description": "This type represents the information related to all dependencies that an NSD constituent has on the versions of other NSD constituents. It shall comply with the provisions defined in table 6.5.3.112-1.\n",
+ "extNetAttDefResource": {
+ "description": "Network attachment definition resources that provide the specification of the interface to attach connection points to this VL.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the information related to a network attachment definition resource that provides the specification of the interface used to connect one or multiple connection points to a secondary container cluster network\n",
+ "type": "object",
+ "required": [
+ "netAttDefResourceInfoId",
+ "netAttDefResource"
+ ],
+ "properties": {
+ "netAttDefResourceInfoId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "netAttDefResource": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would correspond to the ‘kind’ field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the ‘claimName’ field in the Kubernetes® manifest, or a compound name built by Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the ‘metadata.name’ field in Kubernetes® manifest. \n",
"type": "object",
- "required": ["dependentConstituentId"],
+ "required": [
+ "resourceId"
+ ],
"properties": {
- "dependentConstituentId": {
- "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceProviderId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "type": "string"
+ },
+ "vimLevelAdditionalResourceInfo": {
+ "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
+ "type": "object",
+ "properties": {
+ "hostName": {
+ "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note. \n",
"type": "string"
- },
- "versionDependencyStatement": {
- "description": "Identifies one or multiple versions of an NSD constituents upon which the dependent constituent identified by dependentConstituentId has a dependency. Cardinality 0 is used to remove an existing version dependency in a profile.\n",
- "type": "array",
- "items": {
- "description": "This type represents the information related to one or more VNF, NS or PNF descriptor identifiers which describe one single dependency. When more than one descriptor is indicated, they correspond to different versions of the same VNF, NS or PNF and they represent alternatives to fulfil the dependency. It shall comply with the provisions defined in table 6.5.3.113-1.\n",
- "type": "object",
- "required": ["descriptorId"],
- "properties": {
- "descriptorId": {
- "description": "Identifies a VNFD, NSD or PNFD upon which the entity using this information element depends. When more than one descriptor is indicated, they shall correspond to versions of the same VNF, NS or PNF and they represent. alternatives, i.e. the presence of one of them fulfills the dependency.",
- "type": "array",
- "items": {
- "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- }
- }
+ },
+ "persistentVolume": {
+ "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
}
+ },
+ "containerNamespace": {
+ "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise. \n",
+ "type": "string"
+ }
+ }
+ },
+ "associatedExtCpId": {
+ "description": "Identifier of the external CP of the VNF associated to this network attachment definition resource. Shall be present when the network attachment definition resource is used for external connectivity by the VNF\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
}
+ },
+ "associatedVnfcCpId": {
+ "description": "Identifier of the VNFC CP of the VNF associated to this network attachment definition resource. May be present when the network attachment definition resource is used for internal connectivity by the VNF.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ }
+ }
}
+ }
},
- "pnfdInfoId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "pnfProfileId": {
- "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
- "type": "string"
- },
- "cpInfo": {
- "description": "This type represents the information about the external CP of the PNF. It shall comply with the provisions defined in Table 6.5.3.17-1.\n",
- "type": "object",
- "required": ["cpInstanceId", "cpdId"],
- "properties": {
- "cpInstanceId": {
- "description": "An Identifier that is unique within respect to a PNF. Representation: string of variable length.\n",
+ "currentVnfExtCpData": {
+ "description": "This type represents configuration information for external CPs created from a CPD.\nNOTE 1: In case this identifier refers to a CPD with trunking enabled, the external CP instances created from this CPD will represent ports in a trunk. NOTE 2: The map entry value shall be set to \"null\" in order to delete a \"VnfExtCpConfig\" entry identified by a particular key value from the map, i.e. for the disconnection of an existing external CP instance addressed by cpInstanceId in the deleted map entry from a particular external virtual link, and deletion of that instance in case it represents a subport. Deleting the last key from the map removes the affected instance of the \"VnfExtCpData\" structure from its parent data structure. NOTE 3: Within one VNF instance, all VNFC instances created from a particular VDU have the same external connectivity. Thus, given a particular value of the \"cpdId' attribute, there shall be one \"cpConfig\" entry for each VNFC instance that has been or can be created from a VDU which includes a CPD identified by the \"cpdId\" attribute. If the cpConfig represents a subport in a trunk, all \"cpConfig\" entries in this list shall have the same segmentationId, which means they are connected to the same set of external VLs via the trunk. NOTE 4: If, as defined by the input parameters of a \"ChangeVnfFlavour\", \"ChangeExtVnfConnectivity\" or \"ChangeCurrentVnfPkg\" operation, a cpConfig map entry identified by a particular map key value is moved into another \"ExtVirtualLinkData\" or \"VnfExtCpData\" structure, this particular cpConfig map entry may be used by an external CP instance different than the one that has used it before the operation, or by no external CP instance at all. Renaming a CPD identifier during the \"changeCurrentVnfPkg\" operation does not count as moving the related \"cpConfig\" map entries to a new \"extCpData\" structure.\n",
+ "type": "object",
+ "required": [
+ "cpdId"
+ ],
+ "properties": {
+ "cpdId": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
+ "type": "string"
+ },
+ "cpConfig": {
+ "description": "Map of instance data that need to be configured on the CP instances created from the respective CPD. The key of the map which identifies the individual VnfExtCpConfig entries is of type \"IdentifierInVnf\" and is managed by the API consumer. The entries shall be applied by the VNFM according to the rules of JSON Merge Patch (see IETF RFC 7396 [11]). See notes 2, 3 and 4.\n",
+ "type": "object",
+ "additionalProperties": {
+ "description": "This type represents an externally provided link port, or a network attachment definition resource of secondary container cluster network, or network address information per instance of a VNF external connection point. In the case of VM-based deployment of the VNFC exposing the external CP: In case a link port is provided, the NFVO shall use that link port when connecting the VNF external CP to the external VL. • In case a link port is not provided, the NFVO or VNFM shall create a link port on the external VL, and use that link port to connect the VNF external CP to the external VL. In the case of container-based deployment of the VNFC exposing the external CP, the NFVO and VNFM shall use the network attachment definition resource of secondary container cluster network when connecting the CP to the external VL.\nNOTE 1: The following conditions apply to the attributes \"linkPortId\" and \"cpProtocolData\"\n for an external CP instance connected or to be connected to a virtual network not\n categorized as secondary container cluster network:\n - At least one of the \"linkPortId\" and \"cpProtocolData\" attributes shall be present for\n an external CP instance representing a subport that is to be created, or an external CP instance\n that is to be created by creating the corresponding VNFC or VNF instance during the current or\n a subsequent LCM operation, or for an existing external CP instance that is to be re-configured\n or added to a particular external virtual link.\n - If the \"cpProtocolData\" attribute is absent, the \"linkPortId\" attribute shall be provided\n referencing a pre-created link port with pre-configured address information.\n - If both \"cpProtocolData\" and \"linkportId\" are provided, the API consumer shall ensure that\n the cpProtocolData can be used with the pre-created link port referenced by \"linkPortId\".\nNOTE 2: In case the NFVO manages its own identifier space, the NFVO may remap this identifier\n when communicating with the VNFM. If the NFVO knows that there can be an identifier collision\n when communicating with the VNFM by using the identifier from the OSS/BSS, the NFVO shall remap it.\nNOTE 3: The following conditions apply to the attributes \"netAttDefResourceId\" and \"cpProtocolData\" for an external CP\n instance connected or to be connected to a secondary container cluster network:\n − Void.\n − At least one of these attributes shall be present for a to-be-created external CP instance or an existing\n external CP instance.\nNOTE 4: Cardinality greater than 1 is only applicable for specific cases where more than one network\n attachment definition resource is needed to fulfil the connectivity requirements of the external CP,\n e.g. to build a link redundant mated pair in SR-IOV cases. When more than one \"netAttDefResourceId\"\n is indicated, all shall belong to the same namespace as defined by the corresponding \n \"containerNamespace\" attribute in the \"resourceHandle\" attribute in the \"NetAttDefResourceData\".\nNOTE 5: Either \"linkPortId\" or \"netAttDefResourceId\" may be included, but not both.\n",
+ "type": "object",
+ "oneOf": [
+ {
+ "required": [
+ "linkPortId"
+ ]
+ },
+ {
+ "required": [
+ "cpProtocolData"
+ ]
+ }
+ ],
+ "properties": {
+ "parentCpConfigId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
"type": "string"
- },
- "cpdId": {
- "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
+ },
+ "linkPortId": {
+ "description": "An identifier with the intention of being globally unique.\n",
"type": "string"
- },
- "cpProtocolData": {
- "description": "Parameters for configuring the network protocols on the CP.\n",
+ },
+ "createExtLinkPort": {
+ "description": "Indicates the need to create a dedicated link port for the external CP. If set to True, a link port is created. If set to False, no link port is created. This attribute is only applicable for external CP instances without a floating IP address that expose a VIP CP instance for which a dedicated IP address is allocated. It shall be present in that case and shall be absent otherwise.\n",
+ "type": "boolean"
+ },
+ "cpProtocolData": {
+ "description": "Parameters for configuring the network protocols on the link port that connects the CP to a VL. See notes 1 and 3.\n",
"type": "array",
"items": {
- "description": "This type represents network protocol data.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the present document in a backwards-compatible way. In the current version of the present document, only IP over Ethernet is supported.\n",
- "type": "object",
- "required": ["layerProtocol"],
- "properties": {
- "layerProtocol": {
- "description": "Identifier of layer(s) and protocol(s). Permitted values: - IP_OVER_ETHERNET - IP_FOR_VIRTUAL_CP See note.\n",
- "type": "string",
- "enum": ["IP_OVER_ETHERNET", "IP_FOR_VIRTUAL_CP"]
+ "description": "This type represents network protocol data.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the present document in a backwards-compatible way. In the current version of the present document, only IP over Ethernet is supported.\n",
+ "type": "object",
+ "required": [
+ "layerProtocol"
+ ],
+ "properties": {
+ "layerProtocol": {
+ "description": "Identifier of layer(s) and protocol(s). Permitted values: - IP_OVER_ETHERNET - IP_FOR_VIRTUAL_CP See note.\n",
+ "type": "string",
+ "enum": [
+ "IP_OVER_ETHERNET",
+ "IP_FOR_VIRTUAL_CP"
+ ]
+ },
+ "ipOverEthernet": {
+ "description": "This type represents network address data for IP over Ethernet. NOTE 1: At least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2: Exactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present. NOTE 3: If the CP instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4: Depending on the NFVI networking infrastructure, the \"segmentationId\" may indicate the actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header of the packets or it may be an identifier used between the application and the NFVI networking infrastructure to identify the network sub-interface of the trunk port in question. In the latter case the NFVI infrastructure will map this local \"segmentationId\" to whatever \"segmentationId\" is actually used by the NFVI's transport technology.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "required": [
+ "ipAddresses"
+ ]
},
- "ipOverEthernet": {
- "description": "This type represents network address data for IP over Ethernet. NOTE 1: At least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2: Exactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present. NOTE 3: If the CP instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4: Depending on the NFVI networking infrastructure, the \"segmentationId\" may indicate the actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header of the packets or it may be an identifier used between the application and the NFVI networking infrastructure to identify the network sub-interface of the trunk port in question. In the latter case the NFVI infrastructure will map this local \"segmentationId\" to whatever \"segmentationId\" is actually used by the NFVI's transport technology.\n",
- "type": "object",
- "anyOf": [{
- "required": ["ipAddresses"]
- }, {
- "required": ["macAddress"]
- }],
- "properties": {
- "macAddress": {
- "description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
- "type": "string",
- "format": "MAC"
- },
- "segmentationType": {
- "description": "Specifies the encapsulation type for the traffics coming in and out of the trunk subport. Permitted values are: - VLAN: The subport uses VLAN as encapsulation type. - INHERIT: The subport gets its segmentation type from the network it is connected to. This attribute may be present for CP instances that represent subports in a trunk and shall be absent otherwise. If this attribute is not present for a subport CP instance, default value VLAN shall be used.\n",
- "type": "string",
- "enum": ["VLAN", "INHERIT"]
- },
- "segmentationId": {
- "description": "Identification of the network segment to which the CP instance connects to. See note 3 and note 4.\n",
- "type": "string"
- },
- "ipAddresses": {
- "description": "List of IP addresses to assign to the CP instance. Each entry represents IP address data for fixed or dynamic IP address assignment per subnet. If this attribute is not present, no IP address shall be assigned. See note 1.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": ["type"],
- "oneOf": [{
- "required": ["fixedAddresses"]
- }, {
- "required": ["numDynamicAddresses"]
- }, {
- "required": ["addressRange"]
- }],
- "properties": {
- "type": {
- "description": "The type of the IP addresses. Permitted values: - IPV4\n - IPV6\n",
- "type": "string",
- "enum": ["IPV4", "IPV6"]
- },
- "fixedAddresses": {
- "description": "Fixed addresses to assign (from the subnet defined by \"subnetId\" if provided). Exactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present.\n",
- "type": "array",
- "items": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- },
- "numDynamicAddresses": {
- "description": "Number of dynamic addresses to assign (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
- "type": "integer"
- },
- "addressRange": {
- "description": "An IP address range to be used, e.g. in case of egress connections. In case this attribute is present, IP addresses from the range will be used.\n",
- "type": "object",
- "required": ["minAddress", "maxAddress"],
- "properties": {
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- },
- "subnetId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- }
- }
- }
+ {
+ "required": [
+ "macAddress"
+ ]
+ }
+ ],
+ "properties": {
+ "macAddress": {
+ "description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
+ "type": "string",
+ "format": "MAC"
+ },
+ "segmentationType": {
+ "description": "Specifies the encapsulation type for the traffics coming in and out of the trunk subport. Permitted values are: - VLAN: The subport uses VLAN as encapsulation type. - INHERIT: The subport gets its segmentation type from the network it is connected to. This attribute may be present for CP instances that represent subports in a trunk and shall be absent otherwise. If this attribute is not present for a subport CP instance, default value VLAN shall be used.\n",
+ "type": "string",
+ "enum": [
+ "VLAN",
+ "INHERIT"
+ ]
},
- "virtualCpAddress": {
- "description": "This type represents network address data for a virtual CP. It shall comply with the provisions defined in table 6.5.3.12a-1.\n",
+ "segmentationId": {
+ "description": "Identification of the network segment to which the CP instance connects to. See note 3 and note 4.\n",
+ "type": "string"
+ },
+ "ipAddresses": {
+ "description": "List of IP addresses to assign to the CP instance. Each entry represents IP address data for fixed or dynamic IP address assignment per subnet. If this attribute is not present, no IP address shall be assigned. See note 1.\n",
+ "type": "array",
+ "items": {
"type": "object",
- "required": ["type"],
+ "required": [
+ "type"
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "fixedAddresses"
+ ]
+ },
+ {
+ "required": [
+ "numDynamicAddresses"
+ ]
+ },
+ {
+ "required": [
+ "addressRange"
+ ]
+ }
+ ],
"properties": {
- "type": {
- "description": "Identifier of layer(s) and protocol(s). Permitted values: IP_OVER_ETHERNET.\n",
+ "type": {
+ "description": "The type of the IP addresses. Permitted values:\n - IPV4\n - IPV6\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
+ },
+ "fixedAddresses": {
+ "description": "Fixed addresses to assign (from the subnet defined by \"subnetId\" if provided). Exactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present.\n",
+ "type": "array",
+ "items": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ }
+ },
+ "numDynamicAddresses": {
+ "description": "Number of dynamic addresses to assign (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
+ "type": "integer"
+ },
+ "addressRange": {
+ "description": "An IP address range to be used, e.g. in case of egress connections. In case this attribute is present, IP addresses from the range will be used.\n",
+ "type": "object",
+ "required": [
+ "minAddress",
+ "maxAddress"
+ ],
+ "properties": {
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
- "enum": ["IPV4", "IPV6"]
- },
- "loadBalancerIp": {
+ "format": "IP"
+ },
+ "maxAddress": {
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
+ }
}
+ },
+ "subnetId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ }
}
+ }
+ }
+ }
+ },
+ "virtualCpAddress": {
+ "description": "This type represents network address data for a virtual CP. It shall comply with the provisions defined in table 6.5.3.12a-1.\nNOTE 1: If the container cluster is set up to be able to configure an external load balancer this address will be\n used, otherwise it will be ignored by the CISM.\nNOTE 2: In case the cluster can configure an external load balancer but no loadBalancerIp is provided the\n container cluster will assign an IP address.\nNOTE 3: The attribute is only relevant if the virtual CP is instantiated in a cluster that supports configuration of IP\n address pools for virtual CPs. Otherwise it shall be ignored. MetalLB is an example of a solution for\n Kubernetes® that supports configuration of address pools for load balancer services.\nNOTE 4: The loadBalancerIp and the addressPoolName attributes shall not be present at the same time.\n",
+ "type": "object",
+ "required": [
+ "type"
+ ],
+ "properties": {
+ "type": {
+ "description": "Identifier of layer(s) and protocol(s). Permitted values: IP_OVER_ETHERNET.\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
+ },
+ "loadBalancerIp": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which the container cluster will assign an IP address to the virtual CP. See notes 3 and 4.\n",
+ "type": "array",
+ "items": {
+ "type": "string"
+ }
}
+ }
}
+ }
+ }
+ },
+ "netAttDefResourceId": {
+ "description": "Identifier of the \"NetAttDefResourceData\" structure that provides the specification of the interface to attach the external CP to a secondary container cluster network. It is only applicable if the external CP is connected or to be connected to a secondary container cluster network. It shall not be present if the external CP is related to a virtual network not categorized as secondary container cluster network. See notes 3, 4 and 5.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
}
+ }
}
+ }
}
+ }
}
+ }
}
- }
- },
- "virtualLinkInfo": {
- "description": "Information on the VL(s) of the NS instance. This attribute shall be present if the nsState attribute value is INSTANTIATED and if the NS instance has specified connectivity.\n",
- "type": "array",
- "items": {
- "description": "This type specifies the information about an NS VL instance. It shall comply with the provisions defined in Table 6.5.3.53-1.\nNOTE: As an NS can include NFs deployed in NFVI PoPs under the control of several different VIMs, therefore deploying an NS VL can involve several VIMs, each allocating different virtualised network resources, as well as WIMs handling the connectivity in between the NFVI-PoPs in the form of multi-site connectivity services. When this NsVirtualLink is provided as an ExtVirtualLink as input of a VNF LCM operation, the id of the ExtVirtualLink shall be the same as the corresponding NsVirtualLink.\n",
- "type": "object",
- "required": ["id", "nsVirtualLinkDescId", "nsVirtualLinkProfileId"],
- "properties": {
+ },
+ "extManagedVirtualLinkInfo": {
+ "description": "Information about the externally-managed internal VLs of the VNF instance. See note 4 and note 5.\n",
+ "type": "array",
+ "items": {
+ "description": "This type provides information about an externally-managed internal virtual link for VNFs\n",
+ "type": "object",
+ "required": [
+ "id",
+ "vnfVirtualLinkDescId",
+ "networkResource"
+ ],
+ "properties": {
"id": {
- "description": "An identifier that is unique with respect to a NS. Representation: string of variable length.\n",
- "type": "string"
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
},
- "nsVirtualLinkDescId": {
- "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
- "type": "string"
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
},
- "nsVirtualLinkProfileId": {
- "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
- "type": "string"
+ "vnfVirtualLinkDescId": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
+ "type": "string"
},
- "resourceHandle": {
- "description": "Identifier(s) of the virtualised network resource(s) and/or multi-site connectivity service(s) realizing the VL instance. See note.\n",
- "type": "array",
- "items": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes instance the vimLevelResourceType is the type of resource, as would correspond to the kind field if the resource is declared in its own Kubernetes manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the claimName field in the Kubernetes manifest, or a compound name built by Kubernetes if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the metadata.name field in Kubernetes manifest. \n",
+ "networkResource": {
+ "description": "Reference to the VirtualNetwork resource or multi-site connectivity service providing this VL.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would correspond to the ‘kind’ field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the ‘claimName’ field in the Kubernetes® manifest, or a compound name built by Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the ‘metadata.name’ field in Kubernetes® manifest. \n",
+ "type": "object",
+ "required": [
+ "resourceId"
+ ],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceProviderId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "type": "string"
+ },
+ "vimLevelAdditionalResourceInfo": {
+ "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
"type": "object",
- "required": ["resourceId"],
"properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "hostName": {
+ "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "persistentVolume": {
+ "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ },
+ "containerNamespace": {
+ "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise. \n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "vnfLinkPorts": {
+ "description": "Link ports of this VL.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "description": "This type represents a link port of an internal VL of a VNF. It shall comply with the provisions defined in table 6.5.3.64-1.\nNOTE 1: Either cpInstanceId with cpInstanceType set to \"EXT_CP\" or any combination of cpInstanceId with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId (i.e. one or both of them) shall be present for a VnfLinkPortInfo. In case both cpInstanceId with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId are present, the two different CP instances share the linkport.\n",
+ "required": [
+ "id",
+ "resourceHandle"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "resourceHandle": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would correspond to the ‘kind’ field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the ‘claimName’ field in the Kubernetes® manifest, or a compound name built by Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the ‘metadata.name’ field in Kubernetes® manifest. \n",
+ "type": "object",
+ "required": [
+ "resourceId"
+ ],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceProviderId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "type": "string"
+ },
+ "vimLevelAdditionalResourceInfo": {
+ "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
+ "type": "object",
+ "properties": {
+ "hostName": {
+ "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note. \n",
"type": "string"
- },
- "vimLevelResourceType": {
- "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ },
+ "persistentVolume": {
+ "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note. \n",
"type": "string"
+ },
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ },
+ "containerNamespace": {
+ "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise. \n",
+ "type": "string"
+ }
+ }
+ },
+ "cpInstanceId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "cpInstanceType": {
+ "description": "Type of the CP instance that is identified by cpInstanceId. Shall be present if \"cpInstanceId\" is present, and shall be absent otherwise. Permitted values: * VNFC_CP: The link port is connected to a VNFC CP * EXT_CP: The link port is associated to an external CP. See note 1.\n",
+ "type": "string",
+ "enum": [
+ "VNFC_CP",
+ "EXT_CP"
+ ]
+ },
+ "vipCpInstanceId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "trunkResourceId": {
+ "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "vnfNetAttDefResource": {
+ "description": "This type represents the information related to a network attachment definition resource that provides the specification of the interface used to connect one or multiple connection points to a secondary container cluster network\n",
+ "type": "object",
+ "required": [
+ "netAttDefResourceInfoId",
+ "netAttDefResource"
+ ],
+ "properties": {
+ "netAttDefResourceInfoId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "netAttDefResource": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would correspond to the ‘kind’ field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the ‘claimName’ field in the Kubernetes® manifest, or a compound name built by Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the ‘metadata.name’ field in Kubernetes® manifest. \n",
+ "type": "object",
+ "required": [
+ "resourceId"
+ ],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceProviderId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "type": "string"
+ },
+ "vimLevelAdditionalResourceInfo": {
+ "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
+ "type": "object",
+ "properties": {
+ "hostName": {
+ "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
},
- "vimLevelAdditionalResourceInfo": {
- "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
- "type": "object",
- "properties": {
- "hostName": {
- "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "persistentVolume": {
- "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
+ "persistentVolume": {
+ "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
},
- "containerNamespace": {
- "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
- "type": "string"
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
}
+ }
+ },
+ "containerNamespace": {
+ "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise. \n",
+ "type": "string"
}
+ }
+ },
+ "associatedExtCpId": {
+ "description": "Identifier of the external CP of the VNF associated to this network attachment definition resource. Shall be present when the network attachment definition resource is used for external connectivity by the VNF\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ }
+ },
+ "associatedVnfcCpId": {
+ "description": "Identifier of the VNFC CP of the VNF associated to this network attachment definition resource. May be present when the network attachment definition resource is used for internal connectivity by the VNF.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ }
}
+ }
},
- "linkPort": {
- "description": "Link ports of the VL instance. Cardinality of zero indicates that no port has yet been created for the VL instance.\n",
- "type": "array",
- "items": {
- "description": "This type represents information about a link port of a VL instance. It shall comply with the provisions defined in Table 6.5.3.55-1. NOTE: When the NsVirtualLink, from which the present NsLinkPort is part of, is provided as an ExtVirtualLink as input of a VNF LCM operation, the id of the ExtLinkPort shall be the same as the corresponding NsLinkPort.\n",
- "type": "object",
- "required": ["id", "resourceHandle"],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
+ "extManagedMultisiteVirtualLinkId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "monitoringParameters": {
+ "description": "Performance metrics tracked by the VNFM (e.g. for auto-scaling purposes) as identified by the VNF provider in the VNFD.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents a monitoring parameter that is tracked by the VNFM, for example, for auto-scaling purposes. It shall comply with the provisions defined in Table 6.5.3.69-1.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "performanceMetric"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "name": {
+ "description": "Human readable name of the monitoring parameter, as defined in the VNFD.\n",
+ "type": "string"
+ },
+ "performanceMetric": {
+ "description": "Performance metric that is monitored. This attribute shall contain the related \"Measurement Name\" value as defined in clause 7.2 of ETSI GS NFV-IFA 027.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "localizationLanguage": {
+ "description": "Information about localization language of the VNF (includes e.g. strings in the VNFD). The localization languages supported by a VNF can be declared in the VNFD, and localization language selection can take place at instantiation time. The value shall comply with the format defined in IETF RFC 5646.\n",
+ "type": "string"
+ },
+ "vnfcResourceInfo": {
+ "description": "Information about the virtualised compute and storage resources used by the VNFCs of the VNF instance.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the information on virtualised compute and storage resources used by a VNFC in a VNF instance. This feature addresses the following capabilities: • NFV Architecture support for VNFs which follow “cloud-native” design principles. • Enhance NFV-MANO capabilities to support container technologies. • Enhance NFV-MANO capabilities for container management and orchestration. • Enhance information model for containerized VNFs both using bare metal or nested virtualization technologies.\nNOTE 1: ETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on TOSCA specifications. NOTE 2: A VNFC CP is \"connected to\" an external CP if the VNFC CP is connected to an internal VL that exposes an external CP. A VNFC CP is \"exposed as\" an external CP if it is connected directly to an external VL. NOTE 3: The information can be omitted because it is already available as part of the external CP information. NOTE 4: Cardinality greater than 1 is only applicable for specific cases where more than one network attachment definition resource is needed to fulfil the connectivity requirements of the internal CP, e.g. to build a link redundant mated pair in SR-IOV cases. NOTE 5: When more than one \"netAttDefResourceId\" is indicated, all shall belong to the same namespace.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "vduId",
+ "computeResource"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vduId": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
+ "type": "string"
+ },
+ "computeResource": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would correspond to the ‘kind’ field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the ‘claimName’ field in the Kubernetes® manifest, or a compound name built by Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the ‘metadata.name’ field in Kubernetes® manifest. \n",
+ "type": "object",
+ "required": [
+ "resourceId"
+ ],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceProviderId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "type": "string"
+ },
+ "vimLevelAdditionalResourceInfo": {
+ "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
+ "type": "object",
+ "properties": {
+ "hostName": {
+ "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "persistentVolume": {
+ "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ },
+ "containerNamespace": {
+ "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise. \n",
+ "type": "string"
+ }
+ }
+ },
+ "storageResourceIds": {
+ "description": "References to the VirtualStorage resources or references to Storage MCIOs. The value refers to a VirtualStorageResourceInfo item in the VnfInstance.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ }
+ },
+ "reservationId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfcCpInfo": {
+ "description": "CPs of the VNFC instance. Shall be present when that particular CP of the VNFC instance is exposed as an external CP of the VNF instance or is connected to an external CP of the VNF instance.See note 2. May be present otherwise.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": [
+ "id",
+ "cpdId"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "cpdId": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
+ "type": "string"
+ },
+ "vnfExtCpId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "cpProtocolInfo": {
+ "description": "Network protocol information for this CP. May be omitted if the VNFC CP is exposed as an external CP. See note 3.\n",
+ "type": "array",
+ "items": {
+ "description": "This type describes the protocol layer(s) that a CP or SAP uses together with protocol-related information, like addresses. It shall comply with the provisions defined in Table 6.5.3.58-1. NOTE: This attribute allows to signal the addition of further types of layer and protocol in future versions of the present document in a backwards-compatible way. In the current version of the present document, only IP over Ethernet is supported.\n",
+ "type": "object",
+ "required": [
+ "layerProtocol",
+ "ipOverEthernet"
+ ],
+ "properties": {
+ "layerProtocol": {
+ "description": "The identifier of layer(s) and protocol(s) associated to the network address information. Permitted values:\n - IP_OVER_ETHERNET\n - IP_FOR_VIRTUAL_CP\nSee note.\n",
+ "type": "string",
+ "enum": [
+ "IP_OVER_ETHERNET",
+ "IP_FOR_VIRTUAL_CP"
+ ]
},
- "resourceHandle": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes instance the vimLevelResourceType is the type of resource, as would correspond to the kind field if the resource is declared in its own Kubernetes manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the claimName field in the Kubernetes manifest, or a compound name built by Kubernetes if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the metadata.name field in Kubernetes manifest. \n",
- "type": "object",
- "required": ["resourceId"],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
- "type": "string"
- },
- "vimLevelAdditionalResourceInfo": {
- "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
+ "ipOverEthernet": {
+ "description": "This type represents information about a network address that has been assigned.\nNOTE 1: At least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2: Exactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3: If the Cp instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4: Depending on the NFVI networking infrastructure, the \"segmentationId\" may indicate the actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header of the packets or it may be an identifier used between the application and the NFVI networking infrastructure to identify the network sub-interface of the trunk port in question. In the latter case the NFVI infrastructure will map this local \"segmentationId\" to whatever \"segmentationId\" is actually used by the NFVI's transport technology.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "required": [
+ "macAddress"
+ ]
+ },
+ {
+ "required": [
+ "ipAddresses"
+ ]
+ }
+ ],
+ "properties": {
+ "macAddress": {
+ "description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
+ "type": "string",
+ "format": "MAC"
+ },
+ "segmentationId": {
+ "description": "Identification of the network segment to which the Cp instance connects to. See note 3 and note 4.\n",
+ "type": "string"
+ },
+ "ipAddresses": {
+ "description": "Addresses assigned to the CP instance. Each entry represents IP addresses assigned by fixed or dynamic IP address assignment per subnet. See note 1.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": [
+ "type"
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "addresses"
+ ]
+ },
+ {
+ "required": [
+ "addressRange"
+ ]
+ }
+ ],
+ "properties": {
+ "type": {
+ "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
+ },
+ "addresses": {
+ "description": "Fixed addresses assigned (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
+ "type": "array",
+ "items": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ }
+ },
+ "isDynamic": {
+ "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
+ "type": "boolean"
+ },
+ "addressRange": {
+ "description": "An IP address range used, e.g., in case of egress connections. Exactly one of \"addresses\" or \"addressRange\" shall be present. See note 2.\n",
"type": "object",
+ "required": [
+ "minAddress",
+ "maxAddress"
+ ],
"properties": {
- "hostName": {
- "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "persistentVolume": {
- "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ }
}
- },
- "containerNamespace": {
- "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
+ },
+ "subnetId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
"type": "string"
+ }
}
- }
- },
- "nsCpHandle": {
- "description": "This type represents an identifier of the CP or SAP instance. It shall comply with the provisions defined in Table 6.5.3.56-1. NOTE 1: For the VNF external CP instance, both vnfInstanceId and vnfExtCpInstanceId shall be present as a pair. NOTE 2: For the PNF external CP instance, both pnfInfoId and PnfExtCpInstanceId shall be present as a pair. NOTE 3: For the SAP instance, both nsInstanceId and nsSapInstanceId shall be present as a pair. NOTE 4: One pair of identifiers (VNF external CP, PNF external CP or SAP) shall be present.\n",
- "type": "object",
- "oneOf": [{
- "required": ["vnfInstanceId", "vnfExtCpInstanceId"]
- }, {
- "required": ["pnfInfoId", "pnfExtCpInstanceId"]
- }, {
- "required": ["nsInstanceId", "nsSapInstanceId"]
- }],
- "properties": {
- "vnfInstanceId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfExtCpInstanceId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "pnfInfoId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "pnfExtCpInstanceId": {
- "description": "An Identifier that is unique within respect to a PNF. Representation: string of variable length.\n",
- "type": "string"
- },
- "nsInstanceId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
+ }
+ },
+ "type": {
+ "description": "The type of the IP addresses\n",
+ "type": "string",
+ "enum": [
+ "PV4",
+ "PV6"
+ ]
+ },
+ "addresses": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "isDynamic": {
+ "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
+ "type": "boolean"
+ },
+ "addressRange": {
+ "description": "An IP address range used, e.g. in case of egress connections. See note.\n",
+ "type": "object",
+ "required": [
+ "minAddress",
+ "maxAddress"
+ ],
+ "properties": {
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
},
- "nsSapInstanceId": {
- "description": "An identifier that is unique with respect to a NS. Representation: string of variable length.\n",
- "type": "string"
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
}
+ }
+ },
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "subnetId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ }
+ }
+ },
+ "virtualCpAddress": {
+ "description": "This type represents information about a network address that has been assigned to a virtual CP.\n",
+ "type": "object",
+ "required": [
+ "type"
+ ],
+ "properties": {
+ "type": {
+ "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
+ },
+ "loadBalancerIp": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.",
+ "type": "string"
}
+ }
}
+ }
}
- }
- }
- }
- }
- },
- "vnffgInfo": {
- "description": "Information on the VNFFG(s) of the NS instance.\n",
- "type": "array",
- "items": {
- "description": "Information on the VNFFG(s) of the NS instance. NOTE: It indicates an exhaustive list of all the CP instances and SAP instances of the VNFFG.\n",
- "type": "object",
- "required": ["id", "vnffgdId", "vnfInstanceId", "pnfInfoId"],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnffgdId": {
- "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
- "type": "string"
- },
- "vnfInstanceId": {
- "description": "Identifier(s) of the constituent VNF instance(s) of this VNFFG instance.\n",
- "type": "array",
- "items": {
- "description": "An identifier with the intention of being globally unique.\n",
+ },
+ "parentCpId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
"type": "string"
- }
- },
- "pnfdInfoId": {
- "description": "Identifier(s) of the constituent PNF instance(s) of this VNFFG instance.\n",
- "type": "array",
- "items": {
- "description": "An identifier with the intention of being globally unique.\n",
+ },
+ "vnfLinkPortId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
"type": "string"
+ },
+ "netAttDefResourceId": {
+ "description": "Identifier of the \"NetAttDefResourceInfo\" structure that provides the specification of the interface to attach the connection point to a secondary container cluster network. See notes 4 and 5. It shall be present if the internal CP is associated to a VNFC realized by one or a set of OS containers and is connected to a secondary container cluster network. It shall not be present otherwise.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ }
+ },
+ "metadata": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
}
+ }
},
- "nsVirtualLinkInfoId": {
- "description": "Identifier(s) of the constituent VL instance(s) of this VNFFG instance.\n",
- "type": "array",
- "items": {
- "description": "An identifier that is unique with respect to a NS. Representation: string of variable length.\n",
- "type": "string"
+ "metadata": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ }
+ },
+ "vnfVirtualLinkResourceInfo": {
+ "description": "Information about the virtualised network resources used by the VLs of the VNF instance. See note 5.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by an internal VL instance in a VNF instance.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "vnfVirtualLinkDescId",
+ "networkResource"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfVirtualLinkDescId": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
+ "type": "string"
+ },
+ "networkResource": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would correspond to the ‘kind’ field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the ‘claimName’ field in the Kubernetes® manifest, or a compound name built by Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the ‘metadata.name’ field in Kubernetes® manifest. \n",
+ "type": "object",
+ "required": [
+ "resourceId"
+ ],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceProviderId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "type": "string"
+ },
+ "vimLevelAdditionalResourceInfo": {
+ "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
+ "type": "object",
+ "properties": {
+ "hostName": {
+ "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "persistentVolume": {
+ "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ },
+ "containerNamespace": {
+ "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise. \n",
+ "type": "string"
}
+ }
+ },
+ "reservationId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
},
- "nsCpHandle": {
- "description": "This type represents an identifier of the CP or SAP instance. It shall comply with the provisions defined in Table 6.5.3.56-1. NOTE 1: For the VNF external CP instance, both vnfInstanceId and vnfExtCpInstanceId shall be present as a pair. NOTE 2: For the PNF external CP instance, both pnfInfoId and PnfExtCpInstanceId shall be present as a pair. NOTE 3: For the SAP instance, both nsInstanceId and nsSapInstanceId shall be present as a pair. NOTE 4: One pair of identifiers (VNF external CP, PNF external CP or SAP) shall be present.\n",
+ "vnfLinkPorts": {
+ "description": "Links ports of this VL. Shall be present when the linkPort is used for external connectivity by the VNF (refer to VnfLinkPortInfo). May be present otherwise.\n",
+ "type": "array",
+ "items": {
"type": "object",
- "oneOf": [{
- "required": ["vnfInstanceId", "vnfExtCpInstanceId"]
- }, {
- "required": ["pnfInfoId", "pnfExtCpInstanceId"]
- }, {
- "required": ["nsInstanceId", "nsSapInstanceId"]
- }],
+ "description": "This type represents a link port of an internal VL of a VNF. It shall comply with the provisions defined in table 6.5.3.64-1.\nNOTE 1: Either cpInstanceId with cpInstanceType set to \"EXT_CP\" or any combination of cpInstanceId with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId (i.e. one or both of them) shall be present for a VnfLinkPortInfo. In case both cpInstanceId with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId are present, the two different CP instances share the linkport.\n",
+ "required": [
+ "id",
+ "resourceHandle"
+ ],
"properties": {
- "vnfInstanceId": {
+ "id": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "resourceHandle": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would correspond to the ‘kind’ field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the ‘claimName’ field in the Kubernetes® manifest, or a compound name built by Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the ‘metadata.name’ field in Kubernetes® manifest. \n",
+ "type": "object",
+ "required": [
+ "resourceId"
+ ],
+ "properties": {
+ "vimId": {
"description": "An identifier with the intention of being globally unique.\n",
"type": "string"
- },
- "vnfExtCpInstanceId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "pnfInfoId": {
+ },
+ "resourceProviderId": {
"description": "An identifier with the intention of being globally unique.\n",
"type": "string"
- },
- "pnfExtCpInstanceId": {
- "description": "An Identifier that is unique within respect to a PNF. Representation: string of variable length.\n",
+ },
+ "resourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
"type": "string"
- },
- "nsInstanceId": {
- "description": "An identifier with the intention of being globally unique.\n",
+ },
+ "vimLevelResourceType": {
+ "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
"type": "string"
- },
- "nsSapInstanceId": {
- "description": "An identifier that is unique with respect to a NS. Representation: string of variable length.\n",
+ },
+ "vimLevelAdditionalResourceInfo": {
+ "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
+ "type": "object",
+ "properties": {
+ "hostName": {
+ "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "persistentVolume": {
+ "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ },
+ "containerNamespace": {
+ "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise. \n",
"type": "string"
+ }
}
+ },
+ "cpInstanceId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "cpInstanceType": {
+ "description": "Type of the CP instance that is identified by cpInstanceId. Shall be present if \"cpInstanceId\" is present, and shall be absent otherwise. Permitted values: * VNFC_CP: The link port is connected to a VNFC CP * EXT_CP: The link port is associated to an external CP. See note 1.\n",
+ "type": "string",
+ "enum": [
+ "VNFC_CP",
+ "EXT_CP"
+ ]
+ },
+ "vipCpInstanceId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "trunkResourceId": {
+ "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ }
}
+ }
+ },
+ "metadata": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
}
+ }
}
- }
- },
- "sapInfo": {
- "description": "Information on the SAP(s) of the NS instance.\n",
- "type": "array",
- "items": {
- "description": "This type represents an SAP instance. It shall comply with the provisions defined in Table 6.5.3.67-1.\n",
- "type": "object",
- "required": ["id", "sapdId", "sapName", "sapProtocolInfo"],
- "properties": {
+ },
+ "virtualStorageResourceInfo": {
+ "description": "Information on the virtualised storage resource(s) used as storage for the VNF instance.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "virtualStorageDescId",
+ "storageResource"
+ ],
+ "properties": {
"id": {
- "description": "An identifier that is unique with respect to a NS. Representation: string of variable length.\n",
- "type": "string"
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
},
- "sapdId": {
- "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
- "type": "string"
+ "virtualStorageDescId": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
+ "type": "string"
},
- "sapName": {
- "description": "Human readable name for the SAP instance.\n",
- "type": "string"
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
},
- "description": {
- "description": "Human readable description for the SAP instance.\n",
- "type": "string"
+ "storageResource": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would correspond to the ‘kind’ field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the ‘claimName’ field in the Kubernetes® manifest, or a compound name built by Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the ‘metadata.name’ field in Kubernetes® manifest. \n",
+ "type": "object",
+ "required": [
+ "resourceId"
+ ],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceProviderId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "type": "string"
+ },
+ "vimLevelAdditionalResourceInfo": {
+ "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
+ "type": "object",
+ "properties": {
+ "hostName": {
+ "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "persistentVolume": {
+ "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ },
+ "containerNamespace": {
+ "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise. \n",
+ "type": "string"
+ }
+ }
+ },
+ "reservationId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "metadata": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ }
+ },
+ "mcioInfo": {
+ "description": "Information on the MCIO(s) representing VNFC instance(s) realized by one or a set of OS containers and created from the same VDU for the VNF instance.\n",
+ "type": "array",
+ "items": {
+ "description": "This type provides information about an MCIO representing the set of VNFC instances realized by one or a set of OS containers which have been created based on the same VDU.\nNOTE 1 The type of MCIO as specified in the declarative descriptor of the MCIO, and that can be read from the CISM. EXAMPLE: In case of MCIOs managed by Kubernetes, the type of MCIO corresponds to the “kind” property of the declarative descriptor. NOTE 2 If the attribute additionalInfo is present, it may contain runtime information on the actual and desired state of the MCIO(s). NOTE 3 When the container infrastructure service is a Kubernetes® instance, the mcioId is the combined values from the kind and name fields of the Kubernetes® resource object, separated by a slash. Example: \"Deployment/abcd\". NOTE 4 When the container infrastructure service is a Kubernetes® instance, the mcioName is the name field of the resource object.",
+ "type": "object",
+ "required": [
+ "mcioId",
+ "mcioName",
+ "mcioNamespace",
+ "vduId",
+ "cismId",
+ "mcioType",
+ "desiredInstances",
+ "availableInstances"
+ ],
+ "properties": {
+ "mcioId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "mcioName": {
+ "description": "Human readable name of this MCIO. See note 4. \n",
+ "type": "string"
+ },
+ "mcioNamespace": {
+ "description": "Namespace of this MCIO.\n",
+ "type": "string"
+ },
+ "vduId": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
+ "type": "string"
+ },
+ "cismId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "mcioType": {
+ "description": "The type of MCIO. Specific values, their semantics and associated MCIO types are defined in clause 6.5.4.13. Additional values are also permitted. See note 1.\n",
+ "type": "string"
+ },
+ "desiredInstances": {
+ "description": "Number of desired MCIO instances.\n",
+ "type": "integer"
},
- "sapProtocolInfo": {
- "description": "Network protocol information for this SAP.\n",
+ "availableInstances": {
+ "description": "Number of available MCIO instances\n",
+ "type": "integer"
+ },
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ }
+ }
+ }
+ },
+ "metadata": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ },
+ "extensions": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ }
+ },
+ "pnfInfo": {
+ "description": "Information on the PNF(s) that are part of the NS instance.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the information about a PNF that is part of an NS instance. It shall comply with the provisions defined in Table 6.5.3.13-1.\n",
+ "type": "object",
+ "required": [
+ "pnfId",
+ "pnfdId",
+ "pnfdInfoId",
+ "pnfProfileId"
+ ],
+ "properties": {
+ "pnfId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "pnfName": {
+ "description": "Name of the PNF.\n",
+ "type": "string"
+ },
+ "pnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "versionDependency": {
+ "description": "Describes version dependencies currently valid for the PNF. Identifies versions of descriptors of other constituents in the NSD upon which the PNF depends. The dependencies may be described for the PNFD referenced in this PnfInfo with pnfdId and for PNFDs with the same \"pnfdExtInvariantId\". There shall not be more than one versionDependency present with the same dependentConstituentId.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the information related to all dependencies that an NSD constituent has on the versions of other NSD constituents. It shall comply with the provisions defined in table 6.5.3.112-1.\n",
+ "type": "object",
+ "required": [
+ "dependentConstituentId"
+ ],
+ "properties": {
+ "dependentConstituentId": {
+ "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "versionDependencyStatement": {
+ "description": "Identifies one or multiple versions of an NSD constituents upon which the dependent constituent identified by dependentConstituentId has a dependency. Cardinality 0 is used to remove an existing version dependency in a profile.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the information related to one or more VNF, NS or PNF descriptor identifiers which describe one single dependency. When more than one descriptor is indicated, they correspond to different versions of the same VNF, NS or PNF and they represent alternatives to fulfil the dependency. It shall comply with the provisions defined in table 6.5.3.113-1.\n",
+ "type": "object",
+ "required": [
+ "descriptorId"
+ ],
+ "properties": {
+ "descriptorId": {
+ "description": "Identifies a VNFD, NSD or PNFD upon which the entity using this data type depends. When more than one descriptor is indicated, they shall correspond to versions of the same VNF, NS or PNF and they represent alternatives, i.e. the presence of one of them fulfills the dependency.",
"type": "array",
"items": {
- "description": "This type describes the protocol layer(s) that a CP or SAP uses together with protocol-related information, like addresses. It shall comply with the provisions defined in Table 6.5.3.58-1. NOTE: This attribute allows to signal the addition of further types of layer and protocol in future versions of the present document in a backwards-compatible way. In the current version of the present document, only IP over Ethernet is supported.\n",
+ "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
+ "type": "string"
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ },
+ "pnfdInfoId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "pnfProfileId": {
+ "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "cpInfo": {
+ "description": "This type represents the information about the external CP of the PNF. It shall comply with the provisions defined in Table 6.5.3.17-1.\n",
+ "type": "object",
+ "required": [
+ "cpInstanceId",
+ "cpdId"
+ ],
+ "properties": {
+ "cpInstanceId": {
+ "description": "An Identifier that is unique within respect to a PNF. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "cpdId": {
+ "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "cpProtocolData": {
+ "description": "Parameters for configuring the network protocols on the CP.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents network protocol data.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the present document in a backwards-compatible way. In the current version of the present document, only IP over Ethernet is supported.\n",
+ "type": "object",
+ "required": [
+ "layerProtocol"
+ ],
+ "properties": {
+ "layerProtocol": {
+ "description": "Identifier of layer(s) and protocol(s). Permitted values: - IP_OVER_ETHERNET - IP_FOR_VIRTUAL_CP See note.\n",
+ "type": "string",
+ "enum": [
+ "IP_OVER_ETHERNET",
+ "IP_FOR_VIRTUAL_CP"
+ ]
+ },
+ "ipOverEthernet": {
+ "description": "This type represents network address data for IP over Ethernet. NOTE 1: At least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2: Exactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present. NOTE 3: If the CP instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4: Depending on the NFVI networking infrastructure, the \"segmentationId\" may indicate the actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header of the packets or it may be an identifier used between the application and the NFVI networking infrastructure to identify the network sub-interface of the trunk port in question. In the latter case the NFVI infrastructure will map this local \"segmentationId\" to whatever \"segmentationId\" is actually used by the NFVI's transport technology.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "required": [
+ "ipAddresses"
+ ]
+ },
+ {
+ "required": [
+ "macAddress"
+ ]
+ }
+ ],
+ "properties": {
+ "macAddress": {
+ "description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
+ "type": "string",
+ "format": "MAC"
+ },
+ "segmentationType": {
+ "description": "Specifies the encapsulation type for the traffics coming in and out of the trunk subport. Permitted values are: - VLAN: The subport uses VLAN as encapsulation type. - INHERIT: The subport gets its segmentation type from the network it is connected to. This attribute may be present for CP instances that represent subports in a trunk and shall be absent otherwise. If this attribute is not present for a subport CP instance, default value VLAN shall be used.\n",
+ "type": "string",
+ "enum": [
+ "VLAN",
+ "INHERIT"
+ ]
+ },
+ "segmentationId": {
+ "description": "Identification of the network segment to which the CP instance connects to. See note 3 and note 4.\n",
+ "type": "string"
+ },
+ "ipAddresses": {
+ "description": "List of IP addresses to assign to the CP instance. Each entry represents IP address data for fixed or dynamic IP address assignment per subnet. If this attribute is not present, no IP address shall be assigned. See note 1.\n",
+ "type": "array",
+ "items": {
"type": "object",
- "required": ["layerProtocol", "ipOverEthernet"],
+ "required": [
+ "type"
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "fixedAddresses"
+ ]
+ },
+ {
+ "required": [
+ "numDynamicAddresses"
+ ]
+ },
+ {
+ "required": [
+ "addressRange"
+ ]
+ }
+ ],
"properties": {
- "layerProtocol": {
- "description": "The identifier of layer(s) and protocol(s) associated to the network address information. Permitted values: - IP_OVER_ETHERNET\n - IP_FOR_VIRTUAL_CP\nSee note.\n",
+ "type": {
+ "description": "The type of the IP addresses. Permitted values:\n - IPV4\n - IPV6\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
+ },
+ "fixedAddresses": {
+ "description": "Fixed addresses to assign (from the subnet defined by \"subnetId\" if provided). Exactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present.\n",
+ "type": "array",
+ "items": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ }
+ },
+ "numDynamicAddresses": {
+ "description": "Number of dynamic addresses to assign (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
+ "type": "integer"
+ },
+ "addressRange": {
+ "description": "An IP address range to be used, e.g. in case of egress connections. In case this attribute is present, IP addresses from the range will be used.\n",
+ "type": "object",
+ "required": [
+ "minAddress",
+ "maxAddress"
+ ],
+ "properties": {
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
- "enum": ["IP_OVER_ETHERNET", "IP_FOR_VIRTUAL_CP"]
- },
- "ipOverEthernet": {
- "description": "This type represents information about a network address that has been assigned.\nNOTE 1: At least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2: Exactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3: If the Cp instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4: Depending on the NFVI networking infrastructure, the \"segmentationId\" may indicate the actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header of the packets or it may be an identifier used between the application and the NFVI networking infrastructure to identify the network sub-interface of the trunk port in question. In the latter case the NFVI infrastructure will map this local \"segmentationId\" to whatever \"segmentationId\" is actually used by the NFVI's transport technology.\n",
- "type": "object",
- "anyOf": [{
- "required": ["macAddress"]
- }, {
- "required": ["ipAddresses"]
- }],
- "properties": {
- "macAddress": {
- "description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
- "type": "string",
- "format": "MAC"
- },
- "segmentationId": {
- "description": "Identification of the network segment to which the Cp instance connects to. See note 3 and note 4.\n",
- "type": "string"
- },
- "ipAddresses": {
- "description": "Addresses assigned to the CP instance. Each entry represents IP addresses assigned by fixed or dynamic IP address assignment per subnet. See note 1.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": ["type"],
- "oneOf": [{
- "required": ["addresses"]
- }, {
- "required": ["addressRange"]
- }],
- "properties": {
- "type": {
- "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
- "type": "string",
- "enum": ["IPV4", "IPV6"]
- },
- "addresses": {
- "description": "Fixed addresses assigned (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
- "type": "array",
- "items": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- },
- "isDynamic": {
- "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
- "type": "boolean"
- },
- "addressRange": {
- "description": "An IP address range used, e.g., in case of egress connections. Exactly one of \"addresses\" or \"addressRange\" shall be present. See note 2.\n",
- "type": "object",
- "required": ["minAddress", "maxAddress"],
- "properties": {
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- },
- "subnetId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- }
- },
- "type": {
- "description": "The type of the IP addresses\n",
- "type": "string",
- "enum": ["PV4", "PV6"]
- },
- "addresses": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "isDynamic": {
- "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
- "type": "boolean"
- },
- "addressRange": {
- "description": "An IP address range used, e.g. in case of egress connections. See note.\n",
- "type": "object",
- "required": ["minAddress", "maxAddress"],
- "properties": {
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- },
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "subnetId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- },
- "virtualCpAddress": {
- "description": "This type represents information about a network address that has been assigned to a virtual CP.\n",
- "type": "object",
- "required": ["type"],
- "properties": {
- "type": {
- "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
- "type": "string",
- "enum": ["IPV4", "IPV6"]
- },
- "loadBalancerIp": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
+ "format": "IP"
+ },
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ }
}
+ },
+ "subnetId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ }
}
+ }
+ }
+ }
+ },
+ "virtualCpAddress": {
+ "description": "This type represents network address data for a virtual CP. It shall comply with the provisions defined in table 6.5.3.12a-1.\nNOTE 1: If the container cluster is set up to be able to configure an external load balancer this address will be\n used, otherwise it will be ignored by the CISM.\nNOTE 2: In case the cluster can configure an external load balancer but no loadBalancerIp is provided the\n container cluster will assign an IP address.\nNOTE 3: The attribute is only relevant if the virtual CP is instantiated in a cluster that supports configuration of IP\n address pools for virtual CPs. Otherwise it shall be ignored. MetalLB is an example of a solution for\n Kubernetes® that supports configuration of address pools for load balancer services.\nNOTE 4: The loadBalancerIp and the addressPoolName attributes shall not be present at the same time.\n",
+ "type": "object",
+ "required": [
+ "type"
+ ],
+ "properties": {
+ "type": {
+ "description": "Identifier of layer(s) and protocol(s). Permitted values: IP_OVER_ETHERNET.\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
+ },
+ "loadBalancerIp": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which the container cluster will assign an IP address to the virtual CP. See notes 3 and 4.\n",
+ "type": "array",
+ "items": {
+ "type": "string"
+ }
}
+ }
}
+ }
}
+ }
}
- },
- "nestedNsInstanceId": {
- "description": "Identifier of the nested NS(s) of the NS instance.\n",
+ }
+ }
+ }
+ },
+ "virtualLinkInfo": {
+ "description": "Information on the VL(s) of the NS instance. This attribute shall be present if the nsState attribute value is INSTANTIATED and if the NS instance has specified connectivity.\n",
+ "type": "array",
+ "items": {
+ "description": "This type specifies the information about an NS VL instance. It shall comply with the provisions defined in Table 6.5.3.53-1.\nNOTE: As an NS can include NFs deployed in NFVI PoPs under the control of several different VIMs, therefore deploying an NS VL can involve several VIMs, each allocating different virtualised network resources, as well as WIMs handling the connectivity in between the NFVI-PoPs in the form of multi-site connectivity services. When this NsVirtualLink is provided as an ExtVirtualLink as input of a VNF LCM operation, the id of the ExtVirtualLink shall be the same as the corresponding NsVirtualLink.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "nsVirtualLinkDescId",
+ "nsVirtualLinkProfileId"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier that is unique with respect to a NS. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "nsVirtualLinkDescId": {
+ "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "nsVirtualLinkProfileId": {
+ "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "resourceHandle": {
+ "description": "Identifier(s) of the virtualised network resource(s) and/or multi-site connectivity service(s) realizing the VL instance. See note.\n",
"type": "array",
"items": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would correspond to the ‘kind’ field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the ‘claimName’ field in the Kubernetes® manifest, or a compound name built by Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the ‘metadata.name’ field in Kubernetes® manifest. \n",
+ "type": "object",
+ "required": [
+ "resourceId"
+ ],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceProviderId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "type": "string"
+ },
+ "vimLevelAdditionalResourceInfo": {
+ "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
+ "type": "object",
+ "properties": {
+ "hostName": {
+ "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "persistentVolume": {
+ "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ },
+ "containerNamespace": {
+ "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise. \n",
+ "type": "string"
+ }
+ }
}
- },
- "vnfSnapshotInfoIds": {
- "description": "Identifier of information on VNF snapshots of VNF instances that are part of this NS instance.\n",
+ },
+ "linkPort": {
+ "description": "Link ports of the VL instance. Cardinality of zero indicates that no port has yet been created for the VL instance.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents information about a link port of a VL instance. It shall comply with the provisions defined in Table 6.5.3.55-1. NOTE: When the NsVirtualLink, from which the present NsLinkPort is part of, is provided as an ExtVirtualLink as input of a VNF LCM operation, the id of the ExtLinkPort shall be the same as the corresponding NsLinkPort.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "resourceHandle"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceHandle": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would correspond to the ‘kind’ field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the ‘claimName’ field in the Kubernetes® manifest, or a compound name built by Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the ‘metadata.name’ field in Kubernetes® manifest. \n",
+ "type": "object",
+ "required": [
+ "resourceId"
+ ],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceProviderId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "type": "string"
+ },
+ "vimLevelAdditionalResourceInfo": {
+ "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
+ "type": "object",
+ "properties": {
+ "hostName": {
+ "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "persistentVolume": {
+ "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ },
+ "containerNamespace": {
+ "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise. \n",
+ "type": "string"
+ }
+ }
+ },
+ "nsCpHandle": {
+ "description": "This type represents an identifier of the CP or SAP instance. It shall comply with the provisions defined in Table 6.5.3.56-1. NOTE 1: For the VNF external CP instance, both vnfInstanceId and vnfExtCpInstanceId shall be present as a pair. NOTE 2: For the PNF external CP instance, both pnfInfoId and PnfExtCpInstanceId shall be present as a pair. NOTE 3: For the SAP instance, both nsInstanceId and nsSapInstanceId shall be present as a pair. NOTE 4: One pair of identifiers (VNF external CP, PNF external CP or SAP) shall be present.\n",
+ "type": "object",
+ "oneOf": [
+ {
+ "required": [
+ "vnfInstanceId",
+ "vnfExtCpInstanceId"
+ ]
+ },
+ {
+ "required": [
+ "pnfInfoId",
+ "pnfExtCpInstanceId"
+ ]
+ },
+ {
+ "required": [
+ "nsInstanceId",
+ "nsSapInstanceId"
+ ]
+ }
+ ],
+ "properties": {
+ "vnfInstanceId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfExtCpInstanceId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "pnfInfoId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "pnfExtCpInstanceId": {
+ "description": "An Identifier that is unique within respect to a PNF. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "nsInstanceId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "nsSapInstanceId": {
+ "description": "An identifier that is unique with respect to a NS. Representation: string of variable length.\n",
+ "type": "string"
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ },
+ "vnffgInfo": {
+ "description": "Information on the VNFFG(s) of the NS instance.\n",
+ "type": "array",
+ "items": {
+ "description": "Information on the VNFFG(s) of the NS instance. NOTE: It indicates an exhaustive list of all the CP instances and SAP instances of the VNFFG.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "vnffgdId",
+ "vnfInstanceId",
+ "pnfInfoId"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnffgdId": {
+ "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vnfInstanceId": {
+ "description": "Identifier(s) of the constituent VNF instance(s) of this VNFFG instance.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ },
+ "pnfdInfoId": {
+ "description": "Identifier(s) of the constituent PNF instance(s) of this VNFFG instance.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ },
+ "nsVirtualLinkInfoId": {
+ "description": "Identifier(s) of the constituent VL instance(s) of this VNFFG instance.\n",
"type": "array",
"items": {
+ "description": "An identifier that is unique with respect to a NS. Representation: string of variable length.\n",
+ "type": "string"
+ }
+ },
+ "nsCpHandle": {
+ "description": "This type represents an identifier of the CP or SAP instance. It shall comply with the provisions defined in Table 6.5.3.56-1. NOTE 1: For the VNF external CP instance, both vnfInstanceId and vnfExtCpInstanceId shall be present as a pair. NOTE 2: For the PNF external CP instance, both pnfInfoId and PnfExtCpInstanceId shall be present as a pair. NOTE 3: For the SAP instance, both nsInstanceId and nsSapInstanceId shall be present as a pair. NOTE 4: One pair of identifiers (VNF external CP, PNF external CP or SAP) shall be present.\n",
+ "type": "object",
+ "oneOf": [
+ {
+ "required": [
+ "vnfInstanceId",
+ "vnfExtCpInstanceId"
+ ]
+ },
+ {
+ "required": [
+ "pnfInfoId",
+ "pnfExtCpInstanceId"
+ ]
+ },
+ {
+ "required": [
+ "nsInstanceId",
+ "nsSapInstanceId"
+ ]
+ }
+ ],
+ "properties": {
+ "vnfInstanceId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfExtCpInstanceId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "pnfInfoId": {
"description": "An identifier with the intention of being globally unique.\n",
"type": "string"
+ },
+ "pnfExtCpInstanceId": {
+ "description": "An Identifier that is unique within respect to a PNF. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "nsInstanceId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "nsSapInstanceId": {
+ "description": "An identifier that is unique with respect to a NS. Representation: string of variable length.\n",
+ "type": "string"
+ }
}
- },
- "nsState": {
- "description": "The state of the NS instance. Permitted values: NOT_INSTANTIATED: The NS instance is terminated or not instantiated. INSTANTIATED: The NS instance is instantiated.\n",
- "type": "string",
- "enum": ["NOT_INSTANTIATED", "INSTANTIATED"]
- },
- "monitoringParameter": {
- "description": "Performance metrics tracked by the NFVO (e.g. for auto-scaling purposes) as identified by the NS designer in the NSD.\n",
+ }
+ }
+ }
+ },
+ "sapInfo": {
+ "description": "Information on the SAP(s) of the NS instance.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents an SAP instance. It shall comply with the provisions defined in Table 6.5.3.67-1.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "sapdId",
+ "sapName",
+ "sapProtocolInfo"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier that is unique with respect to a NS. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "sapdId": {
+ "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "sapName": {
+ "description": "Human readable name for the SAP instance.\n",
+ "type": "string"
+ },
+ "description": {
+ "description": "Human readable description for the SAP instance.\n",
+ "type": "string"
+ },
+ "sapProtocolInfo": {
+ "description": "Network protocol information for this SAP.\n",
"type": "array",
"items": {
- "description": "This type represents a monitoring parameter that is tracked by the NFVO, for example, for auto-scaling purposes. It shall comply with the provisions defined in Table 6.5.3.68-1.\n",
- "type": "object",
- "required": ["id", "performanceMetric"],
- "properties": {
- "id": {
- "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
- "type": "string"
+ "description": "This type describes the protocol layer(s) that a CP or SAP uses together with protocol-related information, like addresses. It shall comply with the provisions defined in Table 6.5.3.58-1. NOTE: This attribute allows to signal the addition of further types of layer and protocol in future versions of the present document in a backwards-compatible way. In the current version of the present document, only IP over Ethernet is supported.\n",
+ "type": "object",
+ "required": [
+ "layerProtocol",
+ "ipOverEthernet"
+ ],
+ "properties": {
+ "layerProtocol": {
+ "description": "The identifier of layer(s) and protocol(s) associated to the network address information. Permitted values:\n - IP_OVER_ETHERNET\n - IP_FOR_VIRTUAL_CP\nSee note.\n",
+ "type": "string",
+ "enum": [
+ "IP_OVER_ETHERNET",
+ "IP_FOR_VIRTUAL_CP"
+ ]
+ },
+ "ipOverEthernet": {
+ "description": "This type represents information about a network address that has been assigned.\nNOTE 1: At least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2: Exactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3: If the Cp instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4: Depending on the NFVI networking infrastructure, the \"segmentationId\" may indicate the actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header of the packets or it may be an identifier used between the application and the NFVI networking infrastructure to identify the network sub-interface of the trunk port in question. In the latter case the NFVI infrastructure will map this local \"segmentationId\" to whatever \"segmentationId\" is actually used by the NFVI's transport technology.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "required": [
+ "macAddress"
+ ]
+ },
+ {
+ "required": [
+ "ipAddresses"
+ ]
+ }
+ ],
+ "properties": {
+ "macAddress": {
+ "description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
+ "type": "string",
+ "format": "MAC"
+ },
+ "segmentationId": {
+ "description": "Identification of the network segment to which the Cp instance connects to. See note 3 and note 4.\n",
+ "type": "string"
+ },
+ "ipAddresses": {
+ "description": "Addresses assigned to the CP instance. Each entry represents IP addresses assigned by fixed or dynamic IP address assignment per subnet. See note 1.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": [
+ "type"
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "addresses"
+ ]
+ },
+ {
+ "required": [
+ "addressRange"
+ ]
+ }
+ ],
+ "properties": {
+ "type": {
+ "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
+ },
+ "addresses": {
+ "description": "Fixed addresses assigned (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
+ "type": "array",
+ "items": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ }
+ },
+ "isDynamic": {
+ "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
+ "type": "boolean"
+ },
+ "addressRange": {
+ "description": "An IP address range used, e.g., in case of egress connections. Exactly one of \"addresses\" or \"addressRange\" shall be present. See note 2.\n",
+ "type": "object",
+ "required": [
+ "minAddress",
+ "maxAddress"
+ ],
+ "properties": {
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ }
+ }
+ },
+ "subnetId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ }
+ }
+ }
},
- "name": {
- "description": "Human readable name of the monitoring parameter, as defined in the NSD.\n",
- "type": "string"
+ "type": {
+ "description": "The type of the IP addresses\n",
+ "type": "string",
+ "enum": [
+ "PV4",
+ "PV6"
+ ]
},
- "performanceMetric": {
- "description": "Performance metric that is monitored. This attribute shall contain the related \"Measurement Name\" value as defined in clause 7.2 of ETSI GS NFV-IFA 027.\n",
- "type": "string"
+ "addresses": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "isDynamic": {
+ "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
+ "type": "boolean"
+ },
+ "addressRange": {
+ "description": "An IP address range used, e.g. in case of egress connections. See note.\n",
+ "type": "object",
+ "required": [
+ "minAddress",
+ "maxAddress"
+ ],
+ "properties": {
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ }
+ }
+ },
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "subnetId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ }
+ }
+ },
+ "virtualCpAddress": {
+ "description": "This type represents information about a network address that has been assigned to a virtual CP.\n",
+ "type": "object",
+ "required": [
+ "type"
+ ],
+ "properties": {
+ "type": {
+ "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
+ },
+ "loadBalancerIp": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.",
+ "type": "string"
}
+ }
}
+ }
}
- },
- "nsScaleStatus": {
- "description": "Status of each NS scaling aspect declared in the applicable DF, how \"big\" the NS instance has been scaled w.r.t. that aspect. This attribute shall be present if the nsState attribute value is INSTANTIATED.\n",
+ }
+ }
+ }
+ },
+ "nestedNsInstanceId": {
+ "description": "Identifier of the nested NS(s) of the NS instance.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ },
+ "vnfSnapshotInfoIds": {
+ "description": "Identifier of information on VNF snapshots of VNF instances that are part of this NS instance.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ },
+ "nsState": {
+ "description": "The state of the NS instance. Permitted values: NOT_INSTANTIATED: The NS instance is terminated or not instantiated. INSTANTIATED: The NS instance is instantiated.\n",
+ "type": "string",
+ "enum": [
+ "NOT_INSTANTIATED",
+ "INSTANTIATED"
+ ]
+ },
+ "monitoringParameter": {
+ "description": "Performance metrics tracked by the NFVO (e.g. for auto-scaling purposes) as identified by the NS designer in the NSD.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents a monitoring parameter that is tracked by the NFVO, for example, for auto-scaling purposes. It shall comply with the provisions defined in Table 6.5.3.68-1.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "performanceMetric"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "name": {
+ "description": "Human readable name of the monitoring parameter, as defined in the NSD.\n",
+ "type": "string"
+ },
+ "performanceMetric": {
+ "description": "Performance metric that is monitored. This attribute shall contain the related \"Measurement Name\" value as defined in clause 7.2 of ETSI GS NFV-IFA 027.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "nsScaleStatus": {
+ "description": "Status of each NS scaling aspect declared in the applicable DF, how \"big\" the NS instance has been scaled w.r.t. that aspect. This attribute shall be present if the nsState attribute value is INSTANTIATED.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the target NS Scale level for each NS scaling aspect of the current deployment flavor.\n",
+ "type": "object",
+ "required": [
+ "nsScalingAspectId",
+ "nsScaleLevelId"
+ ],
+ "properties": {
+ "nsScalingAspectId": {
+ "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "nsScaleLevelId": {
+ "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "additionalAffinityOrAntiAffinityRule": {
+ "description": "Information on the additional affinity or anti-affinity rule from NS instantiation operation. Shall not conflict with rules already specified in the NSD.\n",
+ "type": "array",
+ "items": {
+ "description": "This type describes the additional affinity or anti-affinity rule applicable between the VNF instances to be instantiated in the NS instantiation operation request or between the VNF instances to be instantiated in the NS instantiation operation request and the existing VNF instances..\n",
+ "type": "object",
+ "required": [
+ "affinityOrAntiAffiinty",
+ "scope"
+ ],
+ "properties": {
+ "vnfdId": {
+ "description": "Reference to a VNFD. When the VNFD which is not used to instantiate VNF, it presents all VNF instances of this type as the subjects of the affinity or anti-affinity rule. The VNF instance which the VNFD presents is not necessary as a part of the NS to be instantiated.\n",
"type": "array",
"items": {
- "description": "This type represents the target NS Scale level for each NS scaling aspect of the current deployment flavor.\n",
- "type": "object",
- "required": ["nsScalingAspectId", "nsScaleLevelId"],
- "properties": {
- "nsScalingAspectId": {
- "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
- "type": "string"
- },
- "nsScaleLevelId": {
- "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
- "type": "string"
- }
- }
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
}
- },
- "additionalAffinityOrAntiAffinityRule": {
- "description": "Information on the additional affinity or anti-affinity rule from NS instantiation operation. Shall not conflict with rules already specified in the NSD.\n",
+ },
+ "vnfProfileId": {
+ "description": "Reference to a vnfProfile defined in the NSD. At least one VnfProfile which is used to instantiate VNF for the NS to be instantiated as the subject of the affinity or anti-affinity rule shall be present. When the VnfProfile which is not used to instantiate VNF, it presents all VNF instances of this type as the subjects of the affinity or anti-affinity rule. The VNF instance which the VnfProfile presents is not necessary as a part of the NS to be instantiated.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
+ "type": "string"
+ }
+ },
+ "vnfInstanceId": {
+ "description": "Reference to the existing VNF instance as the subject of the affinity or anti-affinity rule. The existing VNF instance is not necessary as a part of the NS to be instantiated.\n",
"type": "array",
"items": {
- "description": "This type describes the additional affinity or anti-affinity rule applicable between the VNF instances to be instantiated in the NS instantiation operation request or between the VNF instances to be instantiated in the NS instantiation operation request and the existing VNF instances..\n",
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ },
+ "affinityOrAntiAffiinty": {
+ "description": "The type of the constraint. Permitted values: AFFINITY ANTI_AFFINITY.\n",
+ "type": "string",
+ "enum": [
+ "AFFINITY",
+ "ANTI_AFFINITY"
+ ]
+ },
+ "scope": {
+ "description": "Specifies the scope of the rule where the placement constraint applies. Permitted values: NFVI_POP ZONE ZONE_GROUP NFVI_NODE.\n",
+ "type": "string",
+ "enum": [
+ "NFVI_POP",
+ "ZONE",
+ "ZONE_GROUP",
+ "NFVI_NODE"
+ ]
+ }
+ }
+ }
+ },
+ "wanConnectionInfo": {
+ "description": "Information about WAN related connectivity enabling multi-site VLs.\n",
+ "type": "array",
+ "items": {
+ "description": "This type provides information about the connectivity to the WAN of network resources realizing a VL, e.g.,\nwhen the VL is deployed on several sites across a WAN. It shall comply with the provisions defined in table 6.5.3.90-1.\nNOTE: Either a \"nsVirtualLinkInfoId\" or a \"vnfVirtualLinkResourceInfoId\" shall be provided, but not both.\n",
+ "type": "object",
+ "required": [
+ "wanConnectionInfoId"
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "nsVirtualLinkInfoId"
+ ]
+ },
+ {
+ "required": [
+ "vnfVirtualLinkResourceInfoId"
+ ]
+ }
+ ],
+ "properties": {
+ "wanConnectionInfoId": {
+ "description": "An identifier that is unique with respect to a NS. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "nsVirtualLinkInfoId": {
+ "description": "An identifier that is unique with respect to a NS. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vnfVirtualLinkResourceInfoId": {
+ "description": "An identifier that is unique with respect to a NS. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "protocolInfo": {
+ "description": "This type provides protocol specific information about the connectivity to the WAN of network resources realizing\na VL, e.g., when the VL is deployed on several sites and across a WAN, and the related multi-site connectivity\nservice (MSCS) enabling the connectivity through the WAN. This type supports providing information about both\npre-provisioned WAN connectivity realized by external entities to NFV-MANO but parts of such connectivity is known\nto the NFVO, as well as information about MSCS created under NFV-MANO responsibility (i.e., connectivity is realized\nwhen NFVO communicates with the WIM). It shall comply with the provisions defined in table 6.5.3.91-1.\n",
+ "type": "object",
+ "properties": {
+ "mscsInfo": {
+ "description": "This type provides information about an already provisioned multi-site connectivity service (MSCS) deployed across a WAN. It shall comply with the provisions defined in Table 6.5.3.82-1.\n",
"type": "object",
- "required": ["affinityOrAntiAffiinty", "scope"],
+ "required": [
+ "mscsId",
+ "mscsType"
+ ],
"properties": {
- "vnfdId": {
- "description": "Reference to a VNFD. When the VNFD which is not used to instantiate VNF, it presents all VNF instances of this type as the subjects of the affinity or anti-affinity rule. The VNF instance which the VNFD presents is not necessary as a part of the NS to be instantiated.\n",
- "type": "array",
- "items": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- }
- },
- "vnfProfileId": {
- "description": "Reference to a vnfProfile defined in the NSD. At least one VnfProfile which is used to instantiate VNF for the NS to be instantiated as the subject of the affinity or anti-affinity rule shall be present. When the VnfProfile which is not used to instantiate VNF, it presents all VNF instances of this type as the subjects of the affinity or anti-affinity rule. The VNF instance which the VnfProfile presents is not necessary as a part of the NS to be instantiated.\n",
- "type": "array",
- "items": {
- "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
- "type": "string"
+ "mscsId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "mscsName": {
+ "description": "Human readable name of the MSCS.\n",
+ "type": "string"
+ },
+ "mscsDescription": {
+ "description": "Human readable description of the MSCS.\n",
+ "type": "string"
+ },
+ "mscsType": {
+ "description": "The type of connectivity that is provided to the virtualized networks in the NFVI-PoP and characterizes the connectivity service across the WAN. Permitted values: - L2 - L3\n",
+ "type": "string",
+ "enum": [
+ "L2VPN",
+ "L3VPN"
+ ]
+ },
+ "mscsLayerProtocol": {
+ "description": "Type of underlying connectivity service and protocol associated to the MSCS. Permitted values are as listed below and restricted by the type of MSCS: - EVPN_BGP_MPLS: as specified in IETF RFC 7432. Only applicable for mscsType=\"L2\". - EVPN_VPWS: as specified in IETF RFC 8214. Only applicable for mscsType=\"L2\". - VPLS_BGP: as specified in IETF RFC 4761 and IETF RFC 6624. Only applicable for mscsType=\"L2\". - VPLS_LDP_L2TP: as specified in IETF RFC 4762. Only applicable for mscsType=\"L2\". - VPWS_LDP_L2TP: as specified in IETF RFC 6074. Only applicable for mscsType=\"L2\". - BGP_IP_VPN: BGP/MPLS based IP VPN as specified in IETF RFC 4364. Only applicable for mscsType=\"L3\".\n",
+ "type": "string",
+ "enum": [
+ "EVPN_BGP_MPLS",
+ "EVPN_VPWS",
+ "VPLS_BGP",
+ "VPLS_LDP",
+ "VPWS",
+ "BGP_IP_VPN"
+ ]
+ },
+ "siteAccessProtectionSchemes": {
+ "description": "Information to determine the proper MSCS endpoints configuration to fulfil certain resiliency/protection requirements, e.g., by considering certain availability and redundancy of connectivity service endpoints in between NFVI-PoP and WAN.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "properties": {
+ "locationConstraints": {
+ "description": "This type represents location constraints for a VNF to be instantiated. The location constraints can be represented as follows: • as a country code • as a civic address combined with a country code • as an area, conditionally combined with a country code\nNOTE: If both \"countryCode\" and \"area\" are present, no conflicts should exist between the values of these two attributes. In case of conflicts, the API producer (i.e. the NFVO) shall disregard parts of the geographic area signalled by \"area\" that are outside the boundaries of the country signalled by \"countryCode\". If \"countryCode\" is absent, it is solely the \"area\" attribute that defines the location constraint.\n",
+ "type": "object",
+ "properties": {
+ "countryCode": {
+ "description": "The two-letter ISO 3166 country code in capital letters. Shall be present in case the \"area\" attribute is absent. May be absent if the \"area\" attribute is present (see note).\n",
+ "type": "string"
+ },
+ "civicAddressElement": {
+ "description": "Zero or more elements comprising the civic address. Shall be absent if the \"area\" attribute is present.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": [
+ "caType",
+ "caValue"
+ ],
+ "properties": {
+ "caType": {
+ "description": "Describe the content type of caValue. The value of caType shall comply with Section 3.4 of IETF RFC 4776 [13].\n",
+ "type": "integer"
+ },
+ "caValue": {
+ "description": "Content of civic address element corresponding to the caType. The format caValue shall comply with Section 3.4 of IETF RFC 4776 [13].\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "area": {
+ "description": "Geographic area. Shall be absent if the \"civicAddressElement\" attribute is present. The content of this attribute shall follow the provisions for the \"Polygon\" geometry object as defined in IETF RFC 7946, for which the \"type\" member shall be set to the value \"Polygon\". See note.\n",
+ "type": "object"
+ }
+ }
+ },
+ "protectionScheme": {
+ "description": "Defines the protection scheme. Permitted values: - UNPROTECTED: to indicate no protection. - ONE_TO_ONE: to indicate an active-passive access protection. - ONE_PLUS_ONE: to indicate an active-active access protection. - ONE_TO_N: to indicate an N active to 1 passive access protection.\n",
+ "type": "string",
+ "enum": [
+ "UNPROTECTED",
+ "ONE_TO_ONE",
+ "ONE_PLUS_ONE",
+ "ONE_TO_N"
+ ]
}
- },
- "vnfInstanceId": {
- "description": "Reference to the existing VNF instance as the subject of the affinity or anti-affinity rule. The existing VNF instance is not necessary as a part of the NS to be instantiated.\n",
- "type": "array",
- "items": {
+ }
+ }
+ },
+ "mtuMscs": {
+ "description": "Maximum Transmission Unit (MTU) that can be forwarded over the MSCS (in bytes). Default value is \"1500\" (bytes).\n",
+ "type": "number"
+ },
+ "mscsEndpoints": {
+ "description": "Information about the MSCS endpoints of the MSCS.\n",
+ "type": "array",
+ "items": {
+ "description": "This type provides encapsulates information about an MSCS endpoint of the MSCS. It shall comply with the provisions defined in table 6.5.3.83-1.\n",
+ "type": "object",
+ "required": [
+ "mscsEndpointId",
+ "directionality",
+ "connectivityServiceEndpoinId"
+ ],
+ "properties": {
+ "mscsEndpointId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "directionality": {
+ "description": "Directionality of the data traffic in the context of the terminating MSCS endpoint from WAN’s perspective. Permitted values: - INBOUND: to indicate into the WAN. - OUTBOUND: to indicate from the WAN. - BOTH: to indicate bidirectional data traffic to/from the WAN.\n",
+ "type": "string",
+ "enum": [
+ "INBOUND",
+ "OUTBOUND",
+ "BOTH"
+ ]
+ },
+ "connectivityServiceEndpoinId": {
+ "description": "References the connectivity service endpoint configuration information applicable to support the MSCS endpoint. More than one connectivity service endpoint can be referred when endpoints are in LAG mode.\n",
+ "type": "array",
+ "items": {
"description": "An identifier with the intention of being globally unique.\n",
"type": "string"
+ }
}
- },
- "affinityOrAntiAffiinty": {
- "description": "The type of the constraint. Permitted values: AFFINITY ANTI_AFFINITY.\n",
- "type": "string",
- "enum": ["AFFINITY", "ANTI_AFFINITY"]
- },
- "scope": {
- "description": "Specifies the scope of the rule where the placement constraint applies. Permitted values: NFVI_POP ZONE ZONE_GROUP NFVI_NODE.\n",
- "type": "string",
- "enum": ["NFVI_POP", "ZONE", "ZONE_GROUP", "NFVI_NODE"]
+ }
}
+ }
}
- }
- },
- "wanConnectionInfo": {
- "description": "Information about WAN related connectivity enabling multi-site VLs.\n",
- "type": "array",
- "items": {
- "description": "This type provides information about the connectivity to the WAN of network resources realizing a VL, e.g.,\nwhen the VL is deployed on several sites across a WAN. It shall comply with the provisions defined in table 6.5.3.90-1.\nNOTE: Either a \"nsVirtualLinkInfoId\" or a \"vnfVirtualLinkResourceInfoId\" shall be provided, but not both.\n",
- "type": "object",
- "required": ["wanConnectionInfoId"],
- "oneOf": [{
- "required": ["nsVirtualLinkInfoId"]
- }, {
- "required": ["vnfVirtualLinkResourceInfoId"]
- }],
- "properties": {
- "wanConnectionInfoId": {
- "description": "An identifier that is unique with respect to a NS. Representation: string of variable length.\n",
- "type": "string"
- },
- "nsVirtualLinkInfoId": {
- "description": "An identifier that is unique with respect to a NS. Representation: string of variable length.\n",
- "type": "string"
+ },
+ "connectivityServiceEndpoints": {
+ "description": "Configuration information about the network resources in the NFVI-PoP and their connectivity to the WAN.\n",
+ "type": "array",
+ "items": {
+ "description": "This type provides configuration data for the NFVI-PoP network gateway providing connectivity service endpoints. The connectivity service endpoints are used as endpoints by an MSCS. It shall comply with the provisions defined in Table 6.5.3.84-1.\n",
+ "type": "object",
+ "required": [
+ "connectivityServiceEndpointId",
+ "vimId"
+ ],
+ "properties": {
+ "connectivityServiceEndpointId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
},
- "vnfVirtualLinkResourceInfoId": {
- "description": "An identifier that is unique with respect to a NS. Representation: string of variable length.\n",
- "type": "string"
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
},
- "protocolInfo": {
- "description": "This type provides protocol specific information about the connectivity to the WAN of network resources realizing\na VL, e.g., when the VL is deployed on several sites and across a WAN, and the related multi-site connectivity\nservice (MSCS) enabling the connectivity through the WAN. This type supports providing information about both\npre-provisioned WAN connectivity realized by external entities to NFV-MANO but parts of such connectivity is known\nto the NFVO, as well as information about MSCS created under NFV-MANO responsibility (i.e., connectivity is realized\nwhen NFVO communicates with the WIM). It shall comply with the provisions defined in table 6.5.3.91-1.\n",
- "type": "object",
- "properties": {
- "mscsInfo": {
- "description": "This type provides information about an already provisioned multi-site connectivity service (MSCS) deployed across a WAN. It shall comply with the provisions defined in Table 6.5.3.82-1.\n",
+ "siteToWanLayer2ProtocolData": {
+ "description": "This type provides information about Layer 2 protocol specific information for the configuration of the NFVI-PoP network gateway to enable the stitching of the intra-site VN to the MSCS over the WAN. It shall comply with the provisions defined in Table 6.5.3.85-1. NOTE: Either \"networkResources\" or \"vnSegmentsIds\" shall be provided, but not both.\n",
+ "type": "object",
+ "required": [
+ "layer2ConnectionInfo"
+ ],
+ "properties": {
+ "layer2ConnectionInfo": {
+ "description": "Layer 2 protocol parameters of the connectivity service endpoint (CSE).\n",
+ "type": "object",
+ "required": [
+ "connectionType",
+ "interfaceType",
+ "interfaceTagging",
+ "encapsulationType"
+ ],
+ "properties": {
+ "connectionType": {
+ "description": "The type of connection to be established on the connectivity service point. Permitted values: - CSE: defined by the characteristics of the existing referred connectivity service point. - AGGREGATE_CSE: create an aggregation of the connectivity service endpoints.\n",
+ "type": "string",
+ "enum": [
+ "CSE",
+ "AGGREGATE_CSE"
+ ]
+ },
+ "interfaceType": {
+ "description": "To indicate whether to create logical interfaces on the referred connectivity service endpoint or new aggregated connectivity service endpoint. Permitted values: - PARENT: use the mapped interface to the connectivity service endpoint as is, i.e., do not create logical interfaces. - LOGICAL: create logical interfaces.\n",
+ "type": "string",
+ "enum": [
+ "PARENT",
+ "LOGICAL"
+ ]
+ },
+ "interfaceTagging": {
+ "description": "The type of frames to forward on the connectivity service point. Permitted values: - UNTAGGED: an interface where frames are not tagged. - TAGGED: an interface configured to forward tagged frames (i.e., enabled for VLAN tagging).\n",
+ "type": "string",
+ "enum": [
+ "UNTAGGED",
+ "TAGGED"
+ ]
+ },
+ "encapsulationType": {
+ "description": "The type of encapsulation. If the interfaceTagging=\"TAGGED\", either \"VLAN\" or \"VXLAN\" shall be set. Permitted values: - ETH: generic Ethernet encapsulation. - VLAN: encapsulation based on VLAN. - VXLAN: encapsulation based on VXLAN.\n",
+ "type": "string",
+ "enum": [
+ "ETH",
+ "VLAN",
+ "VXLAN"
+ ]
+ },
+ "vlanTaggingType": {
+ "description": "Type of encapsulation method for VLAN tagging. Shall be present if interfaceTagging=\"TAGGED\" and encapsulationType=\"VLAN\". Permitted values: - DOT1Q: used when packets on the CSE are encapsulated with one or a set of customer VLAN identifiers. - QINQ: used when packets on the CSE are encapsulated with multiple customer VLAN identifiers and a single\n service VLAN identifier.\n- QINANY: used when packets on the CSE have no specific customer VLAN and a service VLAN identifier is used.\n",
+ "type": "string",
+ "enum": [
+ "DOT1Q",
+ "QINQ",
+ "QINANY"
+ ]
+ },
+ "wanSegmentIds": {
+ "description": "Segment identifiers to pass on the tagged interface. Shall be present if encapsulationType=\"VLAN\" or “VXLAN\".\n",
+ "type": "object",
+ "required": [
+ "wanSegmentIdValue"
+ ],
+ "properties": {
+ "wanSegmentIdValue": {
+ "description": "Identifier of the network segment (e.g., VLAN id or VNI).\n",
+ "type": "string"
+ },
+ "wanSegmentIdUpperRange": {
+ "description": "Identifier of the upper range network segment, in case the \"wanSegmentIds\" is used to define a range.\n",
+ "type": "string"
+ }
+ }
+ },
+ "vxlanConfig": {
+ "description": "Additional configuration needed when using VXLAN encapsulation. Shall be present if interfaceTagging=\"TAGGED\" and encapsulationType=\"VXLAN\".\n",
+ "type": "object",
+ "required": [
+ "peerMode"
+ ],
+ "properties": {
+ "peerMode": {
+ "description": "Type of VXLAN access mode. Default value is \"STATIC\".\nPermitted values: - STATIC - BGP_EVPN\n",
+ "type": "string",
+ "enum": [
+ "STATIC",
+ "BGP_EVPN"
+ ]
+ },
+ "peers": {
+ "description": "List of IP addresses of VTEP peers when using static mode.\n",
+ "type": "array",
+ "items": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ }
+ }
+ }
+ },
+ "lagInterfaceData": {
+ "description": "Information for setting up a LAG interface aggregating multiple connectivity service endpoints.\n",
+ "type": "object",
+ "required": [
+ "aggregatedEndpoints",
+ "lacpActivation",
+ "lacpConfig"
+ ],
+ "properties": {
+ "aggregatedEndpoints": {
+ "description": "List of the connectivity service endpoints that are to be aggregated. Shall be present if connectionType=\"AGGREGATE_CSE\". In case of aggregating connectivity service endpoints, only one SiteToWanLayer2ProtocolData shall be provided for the whole set of aggregated endpoints.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ },
+ "lacpActivation": {
+ "description": "Indicates whether to activate LACP on the interface. If \"TRUE\", the LACP is to be activated, or \"FALSE\" otherwise. Default value is \"FALSE\".\n",
+ "type": "boolean"
+ },
+ "lacpConfig": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ },
+ "layer2ControlProtocol": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ },
+ "mtuL2": {
+ "description": "Maximum Transmission Unit (MTU) that can be forwarded at layer 2 (in bytes). Default value is \"1500\" (bytes).\n",
+ "type": "number"
+ },
+ "virtualRoutingAndForwarding": {
+ "description": "Configuration related to the L2 virtual routing and forwarding (MAC-VRF).\n",
+ "type": "object",
+ "required": [
+ "macVrfName"
+ ],
+ "properties": {
+ "macVrfName": {
+ "description": "Name (or identifier) of the MAC-VRF instance.\n",
+ "type": "string"
+ }
+ }
+ },
+ "forwardingConfig": {
+ "description": "Information related to the forwarding of the VN in the NFVI-PoP to the connectivity service endpoint, if information about the VN to \"stitch\" is already known. . by the OSS/BSS. Shall not be provided otherwise, in which case the NFVO will infer the forwarding configuration based on the NS VL, or external VL, or externally-managed VL provisioning.\n",
+ "type": "object",
+ "oneOf": [
+ {
+ "required": [
+ "networkResources"
+ ]
+ },
+ {
+ "required": [
+ "vnSegmentIds"
+ ]
+ }
+ ],
+ "properties": {
+ "networkResources": {
+ "description": "Reference to the VN resource to be forwarded into/from the MSCS. See note.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would correspond to the ‘kind’ field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the ‘claimName’ field in the Kubernetes® manifest, or a compound name built by Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the ‘metadata.name’ field in Kubernetes® manifest. \n",
"type": "object",
- "required": ["mscsId", "mscsType"],
+ "required": [
+ "resourceId"
+ ],
"properties": {
- "mscsId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "mscsName": {
- "description": "Human readable name of the MSCS.\n",
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceProviderId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "type": "string"
+ },
+ "vimLevelAdditionalResourceInfo": {
+ "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
+ "type": "object",
+ "properties": {
+ "hostName": {
+ "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note. \n",
"type": "string"
- },
- "mscsDescription": {
- "description": "Human readable description of the MSCS.\n",
+ },
+ "persistentVolume": {
+ "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note. \n",
"type": "string"
- },
- "mscsType": {
- "description": "The type of connectivity that is provided to the virtualized networks in the NFVI-PoP and characterizes the connectivity service across the WAN. Permitted values: - L2 - L3\n",
- "type": "string",
- "enum": ["L2VPN", "L3VPN"]
- },
- "mscsLayerProtocol": {
- "description": "Type of underlying connectivity service and protocol associated to the MSCS. Permitted values are as listed below and restricted by the type of MSCS: - EVPN_BGP_MPLS: as specified in IETF RFC 7432. Only applicable for mscsType=\"L2\". - EVPN_VPWS: as specified in IETF RFC 8214. Only applicable for mscsType=\"L2\". - VPLS_BGP: as specified in IETF RFC 4761 and IETF RFC 6624. Only applicable for mscsType=\"L2\". - VPLS_LDP_L2TP: as specified in IETF RFC 4762. Only applicable for mscsType=\"L2\". - VPWS_LDP_L2TP: as specified in IETF RFC 6074. Only applicable for mscsType=\"L2\". - BGP_IP_VPN: BGP/MPLS based IP VPN as specified in IETF RFC 4364. Only applicable for mscsType=\"L3\".\n",
- "type": "string",
- "enum": ["EVPN_BGP_MPLS", "EVPN_VPWS", "VPLS_BGP", "VPLS_LDP", "VPWS", "BGP_IP_VPN"]
- },
- "siteAccessProtectionSchemes": {
- "description": "Information to determine the proper MSCS endpoints configuration to fulfil certain resiliency/protection requirements, e.g., by considering certain availability and redundancy of connectivity service endpoints in between NFVI-PoP and WAN.\n",
- "type": "array",
- "items": {
- "type": "object",
- "properties": {
- "locationConstraints": {
- "description": "This type represents location constraints for a VNF to be instantiated. The location constraints can be represented as follows: as a country code as a civic address combined with a country code as an area, conditionally combined with a country code\nNOTE: If both \"countryCode\" and \"area\" are present, no conflicts should exist between the values of these two attributes. In case of conflicts, the API producer (i.e. the NFVO) shall disregard parts of the geographic area signalled by \"area\" that are outside the boundaries of the country signalled by \"countryCode\". If \"countryCode\" is absent, it is solely the \"area\" attribute that defines the location constraint.\n",
- "type": "object",
- "properties": {
- "countryCode": {
- "description": "The two-letter ISO 3166 country code in capital letters. Shall be present in case the \"area\" attribute is absent. May be absent if the \"area\" attribute is present (see note).\n",
- "type": "string"
- },
- "civicAddressElement": {
- "description": "Zero or more elements comprising the civic address. Shall be absent if the \"area\" attribute is present.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": ["caType", "caValue"],
- "properties": {
- "caType": {
- "description": "Describe the content type of caValue. The value of caType shall comply with Section 3.4 of IETF RFC 4776 [13].\n",
- "type": "integer"
- },
- "caValue": {
- "description": "Content of civic address element corresponding to the caType. The format caValue shall comply with Section 3.4 of IETF RFC 4776 [13].\n",
- "type": "string"
- }
- }
- }
- },
- "area": {
- "description": "Geographic area. Shall be absent if the \"civicAddressElement\" attribute is present. The content of this attribute shall follow the provisions for the \"Polygon\" geometry object as defined in IETF RFC 7946, for which the \"type\" member shall be set to the value \"Polygon\". See note.\n",
- "type": "object"
- }
- }
- },
- "protectionScheme": {
- "description": "Defines the protection scheme. Permitted values: - UNPROTECTED: to indicate no protection. - ONE_TO_ONE: to indicate an active-passive access protection. - ONE_PLUS_ONE: to indicate an active-active access protection. - ONE_TO_N: to indicate an N active to 1 passive access protection.\n",
- "type": "string",
- "enum": ["UNPROTECTED", "ONE_TO_ONE", "ONE_PLUS_ONE", "ONE_TO_N"]
- }
- }
- }
- },
- "mtuMscs": {
- "description": "Maximum Transmission Unit (MTU) that can be forwarded over the MSCS (in bytes). Default value is \"1500\" (bytes).\n",
- "type": "number"
- },
- "mscsEndpoints": {
- "description": "Information about the MSCS endpoints of the MSCS.\n",
- "type": "array",
- "items": {
- "description": "This type provides encapsulates information about an MSCS endpoint of the MSCS. It shall comply with the provisions defined in table 6.5.3.83-1.\n",
- "type": "object",
- "required": ["mscsEndpointId", "directionality", "connectivityServiceEndpoinId"],
- "properties": {
- "mscsEndpointId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "directionality": {
- "description": "Directionality of the data traffic in the context of the terminating MSCS endpoint from WANs perspective. Permitted values: - INBOUND: to indicate into the WAN. - OUTBOUND: to indicate from the WAN. - BOTH: to indicate bidirectional data traffic to/from the WAN.\n",
- "type": "string",
- "enum": ["INBOUND", "OUTBOUND", "BOTH"]
- },
- "connectivityServiceEndpoinId": {
- "description": "References the connectivity service endpoint configuration information applicable to support the MSCS endpoint. More than one connectivity service endpoint can be referred when endpoints are in LAG mode.\n",
- "type": "array",
- "items": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- }
- }
- }
- }
+ },
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
}
+ },
+ "containerNamespace": {
+ "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise. \n",
+ "type": "string"
+ }
}
+ }
},
- "connectivityServiceEndpoints": {
- "description": "Configuration information about the network resources in the NFVI-PoP and their connectivity to the WAN.\n",
- "type": "array",
- "items": {
- "description": "This type provides configuration data for the NFVI-PoP network gateway providing connectivity service endpoints. The connectivity service endpoints are used as endpoints by an MSCS. It shall comply with the provisions defined in Table 6.5.3.84-1.\n",
- "type": "object",
- "required": ["connectivityServiceEndpointId", "vimId"],
- "properties": {
- "connectivityServiceEndpointId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "siteToWanLayer2ProtocolData": {
- "description": "This type provides information about Layer 2 protocol specific information for the configuration of the NFVI-PoP network gateway to enable the stitching of the intra-site VN to the MSCS over the WAN. It shall comply with the provisions defined in Table 6.5.3.85-1. NOTE: Either \"networkResources\" or \"vnSegmentsIds\" shall be provided, but not both.\n",
- "type": "object",
- "required": ["layer2ConnectionInfo"],
- "properties": {
- "layer2ConnectionInfo": {
- "description": "Layer 2 protocol parameters of the connectivity service endpoint (CSE).\n",
- "type": "object",
- "required": ["connectionType", "interfaceType", "interfaceTagging", "encapsulationType"],
- "properties": {
- "connectionType": {
- "description": "The type of connection to be established on the connectivity service point. Permitted values: - CSE: defined by the characteristics of the existing referred connectivity service point. - AGGREGATE_CSE: create an aggregation of the connectivity service endpoints.\n",
- "type": "string",
- "enum": ["CSE", "AGGREGATE_CSE"]
- },
- "interfaceType": {
- "description": "To indicate whether to create logical interfaces on the referred connectivity service endpoint or new aggregated connectivity service endpoint. Permitted values: - PARENT: use the mapped interface to the connectivity service endpoint as is, i.e., do not create logical interfaces. - LOGICAL: create logical interfaces.\n",
- "type": "string",
- "enum": ["PARENT", "LOGICAL"]
- },
- "interfaceTagging": {
- "description": "The type of frames to forward on the connectivity service point. Permitted values: - UNTAGGED: an interface where frames are not tagged. - TAGGED: an interface configured to forward tagged frames (i.e., enabled for VLAN tagging).\n",
- "type": "string",
- "enum": ["UNTAGGED", "TAGGED"]
- },
- "encapsulationType": {
- "description": "The type of encapsulation. If the interfaceTagging=\"TAGGED\", either \"VLAN\" or \"VXLAN\" shall be set. Permitted values: - ETH: generic Ethernet encapsulation. - VLAN: encapsulation based on VLAN. - VXLAN: encapsulation based on VXLAN.\n",
- "type": "string",
- "enum": ["ETH", "VLAN", "VXLAN"]
- },
- "vlanTaggingType": {
- "description": "Type of encapsulation method for VLAN tagging. Shall be present if interfaceTagging=\"TAGGED\" and encapsulationType=\"VLAN\". Permitted values: - DOT1Q: used when packets on the CSE are encapsulated with one or a set of customer VLAN identifiers. - QINQ: used when packets on the CSE are encapsulated with multiple customer VLAN identifiers and a single service VLAN identifier.\n- QINANY: used when packets on the CSE have no specific customer VLAN and a service VLAN identifier is used.\n",
- "type": "string",
- "enum": ["DOT1Q", "QINQ", "QINANY"]
- },
- "wanSegmentIds": {
- "description": "Segment identifiers to pass on the tagged interface. Shall be present if encapsulationType=\"VLAN\" or VXLAN\".\n",
- "type": "object",
- "required": ["wanSegmentIdValue"],
- "properties": {
- "wanSegmentIdValue": {
- "description": "Identifier of the network segment (e.g., VLAN id or VNI).\n",
- "type": "string"
- },
- "wanSegmentIdUpperRange": {
- "description": "Identifier of the upper range network segment, in case the \"wanSegmentIds\" is used to define a range.\n",
- "type": "string"
- }
- }
- },
- "vxlanConfig": {
- "description": "Additional configuration needed when using VXLAN encapsulation. Shall be present if interfaceTagging=\"TAGGED\" and encapsulationType=\"VXLAN\".\n",
- "type": "object",
- "required": ["peerMode"],
- "properties": {
- "peerMode": {
- "description": "Type of VXLAN access mode. Default value is \"STATIC\".\nPermitted values: - STATIC - BGP_EVPN\n",
- "type": "string",
- "enum": ["STATIC", "BGP_EVPN"]
- },
- "peers": {
- "description": "List of IP addresses of VTEP peers when using static mode.\n",
- "type": "array",
- "items": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- }
- },
- "lagInterfaceData": {
- "description": "Information for setting up a LAG interface aggregating multiple connectivity service endpoints.\n",
- "type": "object",
- "required": ["aggregatedEndpoints", "lacpActivation", "lacpConfig"],
- "properties": {
- "aggregatedEndpoints": {
- "description": "List of the connectivity service endpoints that are to be aggregated. Shall be present if connectionType=\"AGGREGATE_CSE\". In case of aggregating connectivity service endpoints, only one SiteToWanLayer2ProtocolData shall be provided for the whole set of aggregated endpoints.\n",
- "type": "array",
- "items": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- }
- },
- "lacpActivation": {
- "description": "Indicates whether to activate LACP on the interface. If \"TRUE\", the LACP is to be activated, or \"FALSE\" otherwise. Default value is \"FALSE\".\n",
- "type": "boolean"
- },
- "lacpConfig": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "layer2ControlProtocol": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "mtuL2": {
- "description": "Maximum Transmission Unit (MTU) that can be forwarded at layer 2 (in bytes). Default value is \"1500\" (bytes).\n",
- "type": "number"
- },
- "virtualRoutingAndForwarding": {
- "description": "Configuration related to the L2 virtual routing and forwarding (MAC-VRF).\n",
- "type": "object",
- "required": ["macVrfName"],
- "properties": {
- "macVrfName": {
- "description": "Name (or identifier) of the MAC-VRF instance.\n",
- "type": "string"
- }
- }
- },
- "forwardingConfig": {
- "description": "Information related to the forwarding of the VN in the NFVI-PoP to the connectivity service endpoint, if information about the VN to \"stitch\" is already known. . by the OSS/BSS. Shall not be provided otherwise, in which case the NFVO will infer the forwarding configuration based on the NS VL, or external VL, or externally-managed VL provisioning.\n",
- "type": "object",
- "oneOf": [{
- "required": ["networkResources"]
- }, {
- "required": ["vnSegmentIds"]
- }],
- "properties": {
- "networkResources": {
- "description": "Reference to the VN resource to be forwarded into/from the MSCS. See note.\n",
- "type": "array",
- "items": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes instance the vimLevelResourceType is the type of resource, as would correspond to the kind field if the resource is declared in its own Kubernetes manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the claimName field in the Kubernetes manifest, or a compound name built by Kubernetes if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the metadata.name field in Kubernetes manifest. \n",
- "type": "object",
- "required": ["resourceId"],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
- "type": "string"
- },
- "vimLevelAdditionalResourceInfo": {
- "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
- "type": "object",
- "properties": {
- "hostName": {
- "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "persistentVolume": {
- "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "containerNamespace": {
- "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
- "type": "string"
- }
- }
- }
- },
- "vnSegmentIds": {
- "description": "Identifiers of the network segments of the VN resources to be forwarded into/from the MSCS.\n",
- "type": "object",
- "required": ["vnSegmentIdValue"],
- "properties": {
- "vnSegmentIdValue": {
- "description": "Identifier of the network segment.\n",
- "type": "string"
- },
- "vnSegmentIdUpperRange": {
- "description": "Identifier of the upper range network segment, in case the \"vnSegmentIds\" is used to define a range.\n",
- "type": "string"
- }
- }
- }
- }
- }
- }
- },
- "siteToWanLayer3ProtocolData": {
- "description": "This type provides information about Layer 3 protocol specific information for the stitching of the intra-site VN to the multi-site connectivity service over the WAN. It shall comply with the provisions defined in Table 6.5.3.86-1.\n",
- "type": "object",
- "required": ["routingInfo"],
- "properties": {
- "logicalInterfaceIpAddress": {
- "description": "IP addressing information associated to a logical interface. Shall be present if the \"interfaceType\" of the SiteToWanLayer2ProtocolData is equal to \"LOGICAL\".\n",
- "type": "object",
- "required": ["ipAddress", "associatedSegmentId"],
- "properties": {
- "ipAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "associatedSegmentId": {
- "description": "The associated segment identifier that has triggered the creation of the logical interface. The value shall be one of the values listed in the \"wanSegmentIds\" of the \"siteToWanLayer2ProtocolData\".\n",
- "type": "string"
- }
- }
- },
- "routingInfo": {
- "description": "The routing information that is activated on the connectivity service endpoint. More than one \"routingInfo\" is allowed to enable stacking different routing protocols (e.g., one routing protocol for IPv4 and another one for IPv6).\n",
- "type": "object",
- "required": ["routingProtocol", "routingAddressFamily"],
- "properties": {
- "routingProtocol": {
- "description": "The routing protocol that is activated on the connectivity service endpoint. Permitted values: - BGP: used for dynamic routing BGPv4. - RIP: used for dynamic routing RIPv2. - OSPF: used for dynamic routing (OSPF version 2 for IPv4; and OSPF version 3 for IPv6). - STATIC: used for static routing. - DIRECT: used when the NFVI-PoP network is directly connected to the WAN provider network. - VRRP: used when the NFVI-PoP network is directly connected to the WAN provider network with virtual router redundancy protocol support (VRRP).\n",
- "type": "string",
- "enum": ["BGP", "RIP", "OSPF", "STATIC", "DIRECT", "VRRP"]
- },
- "staticRouting": {
- "description": "Defines a static route. It shall only be present if the routingProtocol=\"STATIC\".\n",
- "type": "object",
- "required": ["ipVersion", "ipPrefix", "prefixSize", "nextHop"],
- "properties": {
- "ipVersion": {
- "description": "The IP version applicable to the routing entry. Permitted values: - IPV4 - IPV6\n",
- "type": "string",
- "enum": ["IPV4", "IPV6"]
- },
- "ipPrefix": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "prefixSize": {
- "description": "The IP prefix size.\n",
- "type": "number"
- },
- "nextHop": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- },
- "routingAddressFamily": {
- "description": "The IP version applicable to the dynamic routing protocol. Shall be present for dynamic routing protocols. Permitted values: - IPV4 - IPV6\n",
- "type": "string",
- "enum": ["IPV4", "IPv6"]
- },
- "ospfRouting": {
- "description": "Defines parameters for OSPF routing. It shall only be present if the routingProtocol=\"OSPF\".\n",
- "type": "object",
- "required": ["areaId"],
- "properties": {
- "areaId": {
- "description": "The routing area identifier, e.g., a number or an IP address.\n",
- "type": "string"
- }
- }
- },
- "bgpRouting": {
- "description": "Defines parameters for BGP routing. It shall only be present if the routingProtocol=\"BGP\".\n",
- "type": "object",
- "required": ["bgpAs"],
- "properties": {
- "bgpAs": {
- "description": "The Autonomous System (AS) identification applicable to the BGP routing info entry.\n",
- "type": "object"
- },
- "bgpNeighbour": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "bgpAdditionalParam": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "routeMapsDistribution": {
- "description": "Maps of routes that are permitted or denied for redistribution.\n",
- "type": "object",
- "required": ["policy", "sequence", "matchAndSetRule"],
- "properties": {
- "policy": {
- "description": "The policy to apply to the route distribution.\nPermitted values: - PERMIT - DENY\n",
- "type": "string",
- "enum": ["PERMIT", "DENY"]
- },
- "sequence": {
- "description": "Sequence or index number assigned to the route-map.\n",
- "type": "number"
- },
- "matchAndSetRule": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- }
- }
- },
- "mtuL3": {
- "description": "Maximum Transmission Unit (MTU) that can be forwarded at layer 3 (in bytes). Default value is \"1500\" (bytes).\n",
- "type": "number"
- },
- "virtualRoutingAndForwarding": {
- "description": "Configuration related to the virtual routing and forwarding (VRF).\n",
- "type": "object",
- "required": ["vrfName"],
- "properties": {
- "vrfName": {
- "description": "Name (or identifier) of the VRF instance.\n",
- "type": "string"
- }
- }
- },
- "bfdConfig": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- }
- }
+ "vnSegmentIds": {
+ "description": "Identifiers of the network segments of the VN resources to be forwarded into/from the MSCS.\n",
+ "type": "object",
+ "required": [
+ "vnSegmentIdValue"
+ ],
+ "properties": {
+ "vnSegmentIdValue": {
+ "description": "Identifier of the network segment.\n",
+ "type": "string"
+ },
+ "vnSegmentIdUpperRange": {
+ "description": "Identifier of the upper range network segment, in case the \"vnSegmentIds\" is used to define a range.\n",
+ "type": "string"
+ }
+ }
+ }
+ }
+ }
+ }
+ },
+ "siteToWanLayer3ProtocolData": {
+ "description": "This type provides information about Layer 3 protocol specific information for the stitching of the intra-site VN to the multi-site connectivity service over the WAN. It shall comply with the provisions defined in Table 6.5.3.86-1.\n",
+ "type": "object",
+ "required": [
+ "routingInfo"
+ ],
+ "properties": {
+ "logicalInterfaceIpAddress": {
+ "description": "IP addressing information associated to a logical interface. Shall be present if the \"interfaceType\" of the SiteToWanLayer2ProtocolData is equal to \"LOGICAL\".\n",
+ "type": "object",
+ "required": [
+ "ipAddress",
+ "associatedSegmentId"
+ ],
+ "properties": {
+ "ipAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "associatedSegmentId": {
+ "description": "The associated segment identifier that has triggered the creation of the logical interface. The value shall be one of the values listed in the \"wanSegmentIds\" of the \"siteToWanLayer2ProtocolData\".\n",
+ "type": "string"
+ }
+ }
+ },
+ "routingInfo": {
+ "description": "The routing information that is activated on the connectivity service endpoint. More than one \"routingInfo\" is allowed to enable stacking different routing protocols (e.g., one routing protocol for IPv4 and another one for IPv6).\n",
+ "type": "object",
+ "required": [
+ "routingProtocol",
+ "routingAddressFamily"
+ ],
+ "properties": {
+ "routingProtocol": {
+ "description": "The routing protocol that is activated on the connectivity service endpoint. Permitted values: - BGP: used for dynamic routing BGPv4. - RIP: used for dynamic routing RIPv2. - OSPF: used for dynamic routing (OSPF version 2 for IPv4; and OSPF version 3 for IPv6). - STATIC: used for static routing. - DIRECT: used when the NFVI-PoP network is directly connected to the WAN provider network. - VRRP: used when the NFVI-PoP network is directly connected to the WAN provider network with virtual\n router redundancy protocol support (VRRP).\n",
+ "type": "string",
+ "enum": [
+ "BGP",
+ "RIP",
+ "OSPF",
+ "STATIC",
+ "DIRECT",
+ "VRRP"
+ ]
+ },
+ "staticRouting": {
+ "description": "Defines a static route. It shall only be present if the routingProtocol=\"STATIC\".\n",
+ "type": "object",
+ "required": [
+ "ipVersion",
+ "ipPrefix",
+ "prefixSize",
+ "nextHop"
+ ],
+ "properties": {
+ "ipVersion": {
+ "description": "The IP version applicable to the routing entry. Permitted values: - IPV4 - IPV6\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
+ },
+ "ipPrefix": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "prefixSize": {
+ "description": "The IP prefix size.\n",
+ "type": "number"
+ },
+ "nextHop": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ }
+ }
+ },
+ "routingAddressFamily": {
+ "description": "The IP version applicable to the dynamic routing protocol. Shall be present for dynamic routing protocols. Permitted values: - IPV4 - IPV6\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPv6"
+ ]
+ },
+ "ospfRouting": {
+ "description": "Defines parameters for OSPF routing. It shall only be present if the routingProtocol=\"OSPF\".\n",
+ "type": "object",
+ "required": [
+ "areaId"
+ ],
+ "properties": {
+ "areaId": {
+ "description": "The routing area identifier, e.g., a number or an IP address.\n",
+ "type": "string"
+ }
+ }
+ },
+ "bgpRouting": {
+ "description": "Defines parameters for BGP routing. It shall only be present if the routingProtocol=\"BGP\".\n",
+ "type": "object",
+ "required": [
+ "bgpAs"
+ ],
+ "properties": {
+ "bgpAs": {
+ "description": "The Autonomous System (AS) identification applicable to the BGP routing info entry.\n",
+ "type": "object"
+ },
+ "bgpNeighbour": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "bgpAdditionalParam": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ },
+ "routeMapsDistribution": {
+ "description": "Maps of routes that are permitted or denied for redistribution.\n",
+ "type": "object",
+ "required": [
+ "policy",
+ "sequence",
+ "matchAndSetRule"
+ ],
+ "properties": {
+ "policy": {
+ "description": "The policy to apply to the route distribution.\nPermitted values: - PERMIT - DENY\n",
+ "type": "string",
+ "enum": [
+ "PERMIT",
+ "DENY"
+ ]
+ },
+ "sequence": {
+ "description": "Sequence or index number assigned to the route-map.\n",
+ "type": "number"
+ },
+ "matchAndSetRule": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
}
+ }
+ }
+ }
+ },
+ "mtuL3": {
+ "description": "Maximum Transmission Unit (MTU) that can be forwarded at layer 3 (in bytes). Default value is \"1500\" (bytes).\n",
+ "type": "number"
+ },
+ "virtualRoutingAndForwarding": {
+ "description": "Configuration related to the virtual routing and forwarding (VRF).\n",
+ "type": "object",
+ "required": [
+ "vrfName"
+ ],
+ "properties": {
+ "vrfName": {
+ "description": "Name (or identifier) of the VRF instance.\n",
+ "type": "string"
}
+ }
+ },
+ "bfdConfig": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
}
+ }
}
+ }
}
+ }
+ }
+ }
+ }
+ }
+ },
+ "_links": {
+ "type": "object",
+ "description": "Links to resources related to this resource.",
+ "required": [
+ "self"
+ ],
+ "properties": {
+ "self": {
+ "description": "This type represents a link to a resource.\n",
+ "type": "object",
+ "required": [
+ "href"
+ ],
+ "properties": {
+ "href": {
+ "description": "URI of a resource referenced from a notification. Should be an absolute URI (i.e. a URI that contains {apiRoot}), however, may be a relative URI (i.e. a URI where the {apiRoot} part is omitted) if the {apiRoot} information is not available.\n",
+ "type": "string",
+ "format": "url"
}
+ }
},
- "_links": {
+ "nestedNsInstances": {
+ "description": "Links to resources related to this notification.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents a link to a resource.\n",
"type": "object",
- "description": "Links to resources related to this resource.",
- "required": ["self"],
+ "required": [
+ "href"
+ ],
"properties": {
- "self": {
- "description": "This type represents a link to a resource.\n",
- "type": "object",
- "required": ["href"],
- "properties": {
- "href": {
- "description": "URI of a resource referenced from a notification. Should be an absolute URI (i.e. a URI that contains {apiRoot}), however, may be a relative URI (i.e. a URI where the {apiRoot} part is omitted) if the {apiRoot} information is not available.\n",
- "type": "string",
- "format": "url"
- }
- }
- },
- "nestedNsInstances": {
- "description": "Links to resources related to this notification.\n",
- "type": "array",
- "items": {
- "description": "This type represents a link to a resource.\n",
- "type": "object",
- "required": ["href"],
- "properties": {
- "href": {
- "description": "URI of a resource referenced from a notification. Should be an absolute URI (i.e. a URI that contains {apiRoot}), however, may be a relative URI (i.e. a URI where the {apiRoot} part is omitted) if the {apiRoot} information is not available.\n",
- "type": "string",
- "format": "url"
- }
- }
- }
- },
- "vnfSnapshotInfos": {
- "description": "Links to the VNF snapshots associated to VNF instances which are part of this NS instance.\n",
- "type": "array",
- "items": {
- "description": "This type represents a link to a resource.\n",
- "type": "object",
- "required": ["href"],
- "properties": {
- "href": {
- "description": "URI of a resource referenced from a notification. Should be an absolute URI (i.e. a URI that contains {apiRoot}), however, may be a relative URI (i.e. a URI where the {apiRoot} part is omitted) if the {apiRoot} information is not available.\n",
- "type": "string",
- "format": "url"
- }
- }
- }
- },
- "instantiate": {
- "description": "This type represents a link to a resource.\n",
- "type": "object",
- "required": ["href"],
- "properties": {
- "href": {
- "description": "URI of a resource referenced from a notification. Should be an absolute URI (i.e. a URI that contains {apiRoot}), however, may be a relative URI (i.e. a URI where the {apiRoot} part is omitted) if the {apiRoot} information is not available.\n",
- "type": "string",
- "format": "url"
- }
- }
- },
- "terminate": {
- "description": "This type represents a link to a resource.\n",
- "type": "object",
- "required": ["href"],
- "properties": {
- "href": {
- "description": "URI of a resource referenced from a notification. Should be an absolute URI (i.e. a URI that contains {apiRoot}), however, may be a relative URI (i.e. a URI where the {apiRoot} part is omitted) if the {apiRoot} information is not available.\n",
- "type": "string",
- "format": "url"
- }
- }
- },
- "update": {
- "description": "This type represents a link to a resource.\n",
- "type": "object",
- "required": ["href"],
- "properties": {
- "href": {
- "description": "URI of a resource referenced from a notification. Should be an absolute URI (i.e. a URI that contains {apiRoot}), however, may be a relative URI (i.e. a URI where the {apiRoot} part is omitted) if the {apiRoot} information is not available.\n",
- "type": "string",
- "format": "url"
- }
- }
- },
- "scale": {
- "description": "This type represents a link to a resource.\n",
- "type": "object",
- "required": ["href"],
- "properties": {
- "href": {
- "description": "URI of a resource referenced from a notification. Should be an absolute URI (i.e. a URI that contains {apiRoot}), however, may be a relative URI (i.e. a URI where the {apiRoot} part is omitted) if the {apiRoot} information is not available.\n",
- "type": "string",
- "format": "url"
- }
- }
- },
- "heal": {
- "description": "This type represents a link to a resource.\n",
- "type": "object",
- "required": ["href"],
- "properties": {
- "href": {
- "description": "URI of a resource referenced from a notification. Should be an absolute URI (i.e. a URI that contains {apiRoot}), however, may be a relative URI (i.e. a URI where the {apiRoot} part is omitted) if the {apiRoot} information is not available.\n",
- "type": "string",
- "format": "url"
- }
- }
- }
+ "href": {
+ "description": "URI of a resource referenced from a notification. Should be an absolute URI (i.e. a URI that contains {apiRoot}), however, may be a relative URI (i.e. a URI where the {apiRoot} part is omitted) if the {apiRoot} information is not available.\n",
+ "type": "string",
+ "format": "url"
+ }
+ }
+ }
+ },
+ "vnfSnapshotInfos": {
+ "description": "Links to the VNF snapshots associated to VNF instances which are part of this NS instance.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents a link to a resource.\n",
+ "type": "object",
+ "required": [
+ "href"
+ ],
+ "properties": {
+ "href": {
+ "description": "URI of a resource referenced from a notification. Should be an absolute URI (i.e. a URI that contains {apiRoot}), however, may be a relative URI (i.e. a URI where the {apiRoot} part is omitted) if the {apiRoot} information is not available.\n",
+ "type": "string",
+ "format": "url"
+ }
+ }
+ }
+ },
+ "instantiate": {
+ "description": "This type represents a link to a resource.\n",
+ "type": "object",
+ "required": [
+ "href"
+ ],
+ "properties": {
+ "href": {
+ "description": "URI of a resource referenced from a notification. Should be an absolute URI (i.e. a URI that contains {apiRoot}), however, may be a relative URI (i.e. a URI where the {apiRoot} part is omitted) if the {apiRoot} information is not available.\n",
+ "type": "string",
+ "format": "url"
+ }
+ }
+ },
+ "terminate": {
+ "description": "This type represents a link to a resource.\n",
+ "type": "object",
+ "required": [
+ "href"
+ ],
+ "properties": {
+ "href": {
+ "description": "URI of a resource referenced from a notification. Should be an absolute URI (i.e. a URI that contains {apiRoot}), however, may be a relative URI (i.e. a URI where the {apiRoot} part is omitted) if the {apiRoot} information is not available.\n",
+ "type": "string",
+ "format": "url"
+ }
+ }
+ },
+ "update": {
+ "description": "This type represents a link to a resource.\n",
+ "type": "object",
+ "required": [
+ "href"
+ ],
+ "properties": {
+ "href": {
+ "description": "URI of a resource referenced from a notification. Should be an absolute URI (i.e. a URI that contains {apiRoot}), however, may be a relative URI (i.e. a URI where the {apiRoot} part is omitted) if the {apiRoot} information is not available.\n",
+ "type": "string",
+ "format": "url"
+ }
+ }
+ },
+ "scale": {
+ "description": "This type represents a link to a resource.\n",
+ "type": "object",
+ "required": [
+ "href"
+ ],
+ "properties": {
+ "href": {
+ "description": "URI of a resource referenced from a notification. Should be an absolute URI (i.e. a URI that contains {apiRoot}), however, may be a relative URI (i.e. a URI where the {apiRoot} part is omitted) if the {apiRoot} information is not available.\n",
+ "type": "string",
+ "format": "url"
+ }
+ }
+ },
+ "heal": {
+ "description": "This type represents a link to a resource.\n",
+ "type": "object",
+ "required": [
+ "href"
+ ],
+ "properties": {
+ "href": {
+ "description": "URI of a resource referenced from a notification. Should be an absolute URI (i.e. a URI that contains {apiRoot}), however, may be a relative URI (i.e. a URI where the {apiRoot} part is omitted) if the {apiRoot} information is not available.\n",
+ "type": "string",
+ "format": "url"
}
+ }
}
+ }
}
+ }
}
-}
\ No newline at end of file
+ }
\ No newline at end of file
diff --git a/SOL005/NSLifecycleManagement-API/schemas/NsLcmOperationOccurrenceNotification.schema.json b/SOL005/NSLifecycleManagement-API/schemas/NsLcmOperationOccurrenceNotification.schema.json
index f4420d9291c13fb30f3b029f63d8df22000f30d7..5fbda4394a976fe5f37690789553d53caa741ae8 100644
--- a/SOL005/NSLifecycleManagement-API/schemas/NsLcmOperationOccurrenceNotification.schema.json
+++ b/SOL005/NSLifecycleManagement-API/schemas/NsLcmOperationOccurrenceNotification.schema.json
@@ -1,1234 +1,1573 @@
{
"type": "object",
"description": "This type represents an NS lifecycle management operation occurrence notification, which informs the receiver of changes in the NS lifecycle caused by an NS LCM operation occurrence. The NS LCM operation occurrence may be triggered by the OSS/BSS or automatically triggered by the NFVO.",
- "required": ["id", "nsInstanceId", "nsLcmOpOccId", "operation", "notificationType", "subscriptionId", "timestamp", "notificationStatus", "operationState", "isAutomaticInvocation", "_links"],
+ "required": [
+ "id",
+ "nsInstanceId",
+ "nsLcmOpOccId",
+ "operation",
+ "notificationType",
+ "subscriptionId",
+ "timestamp",
+ "notificationStatus",
+ "operationState",
+ "isAutomaticInvocation",
+ "_links"
+ ],
"properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "nsInstanceId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "nsLcmOpOccId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "operation": {
- "description": "The enumeration NsLcmOpType represents those lifecycle operations that trigger a NS lifecycle management operation occurrence notification. Value | Description ------|------------ INSTANTIATE | Represents the \"Instantiate NS\" LCM operation. SCALE | Represents the \"Scale NS\" LCM operation. UPDATE | Represents the \"Update NS\" LCM operation. TERMINATE | Represents the \"Terminate NS\" LCM operation. HEAL | Represents the \"Heal NS\" LCM operation.\n",
- "type": "string",
- "enum": ["INSTANTIATE", "SCALE", "UPDATE", "TERMINATE", "HEAL"]
- },
- "notificationType": {
- "description": "Discriminator for the different notification types. Shall be set to \"NsLcmOperationOccurrenceNotification\" for this notification type.\n",
- "type": "string"
- },
- "subscriptionId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "timestamp": {
- "description": "Date-time stamp. Representation: String formatted according toas defined by the date-time production in IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "notificationStatus": {
- "description": "Indicates whether this notification reports about the start of a NS lifecycle operation or the result of a NS lifecycle operation. Permitted values: - START: Informs about the start of the NS LCM operation occurrence. - RESULT: Informs about the final or intermediate result of the NS LCM operation occurrence.\n",
- "type": "string",
- "enum": ["START", "RESULT"]
- },
- "operationState": {
- "description": "Value | Description ------|------------ PROCESSING | The NS LCM operation is currently in execution. COMPLETED | The NS LCM operation has been completed successfully. PARTIALLY_COMPLETED | The NS LCM operation has been partially completed with accepTable errors. FAILED_TEMP | The NS LCM operation has failed and execution has stopped, but the execution of the operation is not considered to be closed. FAILED | The NS LCM operation has failed and it cannot be retried or rolled back, as it is determined that such action will not succeed. OLLING_BACK | The NS LCM operation is currently being rolled back. ROLLED_BACK | The NS LCM operation has been successfully rolled back, i.e. The state of the NS prior to the original operation invocation has been restored as closely as possible.\n",
- "type": "string",
- "enum": ["PROCESSING", "COMPLETED", "PARTIALLY_COMPLETED", "FAILED_TEMP", "FAILED", "ROLLING_BACK", "ROLLED_BACK"]
- },
- "isAutomaticInvocation": {
- "description": "The Boolean is a data type having two values (TRUE and FALSE).\n",
- "type": "boolean"
- },
- "verbosity": {
- "description": "The enumeration LcmOpOccNotificationVerbosityType provides values to control the verbosity of LCM operation occurrence notifications. It shall comply with the provisions defined in table 6.5.4.11-1. * FULL: This signals a full notification which contains all change details. * SHORT: This signals a short notification which omits large-volume change details to reduce the size of data to be sent via the notification mechanism.\n",
- "type": "string",
- "enum": ["FULL", "SHORT"]
- },
- "affectedVnf": {
- "description": "Information about the VNF instances that were affected during the lifecycle operation. See note 1.\n",
- "type": "array",
- "items": {
- "description": "This type provides information about added, deleted and modified VNFs.\nNOTE: At least one of the attributes \"changedVnfInfo\", \"changedExtConnectivity\" or \"modificationsTriggeredByVnfPkgChange\" shall be present. Not more than one of \"changedVnfInfo\" and \"modificationsTriggeredByVnfPkgChange\" shall be present.\n",
- "type": "object",
- "required": ["vnfInstanceId", "vnfdId", "vnfProfileId", "vnfName", "changeType", "changeResult"],
- "anyOf": [{
- "required": ["changedExtConnectivity"]
- }, {
- "oneOf": [{
- "required": ["changedVnfInfo"]
- }, {
- "required": ["modificationsTriggeredByVnfPkgChange"]
- }]
- }],
- "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "nsInstanceId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "nsLcmOpOccId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "operation": {
+ "description": "The enumeration NsLcmOpType represents those lifecycle operations that trigger a NS lifecycle management operation occurrence notification. Value | Description ------|------------ INSTANTIATE | Represents the \"Instantiate NS\" LCM operation. SCALE | Represents the \"Scale NS\" LCM operation. UPDATE | Represents the \"Update NS\" LCM operation. TERMINATE | Represents the \"Terminate NS\" LCM operation. HEAL | Represents the \"Heal NS\" LCM operation.\n",
+ "type": "string",
+ "enum": [
+ "INSTANTIATE",
+ "SCALE",
+ "UPDATE",
+ "TERMINATE",
+ "HEAL"
+ ]
+ },
+ "notificationType": {
+ "description": "Discriminator for the different notification types. Shall be set to \"NsLcmOperationOccurrenceNotification\" for this notification type.\n",
+ "type": "string"
+ },
+ "subscriptionId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "timestamp": {
+ "description": "Date-time stamp. Representation: String formatted according toas defined by the date-time production in IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "notificationStatus": {
+ "description": "Indicates whether this notification reports about the start of a NS lifecycle operation or the result of a NS lifecycle operation. Permitted values: - START: Informs about the start of the NS LCM operation occurrence. - RESULT: Informs about the final or intermediate result of the NS LCM operation occurrence.\n",
+ "type": "string",
+ "enum": [
+ "START",
+ "RESULT"
+ ]
+ },
+ "operationState": {
+ "description": "Value | Description ------|------------ PROCESSING | The NS LCM operation is currently in execution. COMPLETED | The NS LCM operation has been completed successfully. PARTIALLY_COMPLETED | The NS LCM operation has been partially completed with accepTable errors. FAILED_TEMP | The NS LCM operation has failed and execution has stopped, but the execution of the operation is not considered to be closed. FAILED | The NS LCM operation has failed and it cannot be retried or rolled back, as it is determined that such action will not succeed. OLLING_BACK | The NS LCM operation is currently being rolled back. ROLLED_BACK | The NS LCM operation has been successfully rolled back, i.e. The state of the NS prior to the original operation invocation has been restored as closely as possible.\n",
+ "type": "string",
+ "enum": [
+ "PROCESSING",
+ "COMPLETED",
+ "PARTIALLY_COMPLETED",
+ "FAILED_TEMP",
+ "FAILED",
+ "ROLLING_BACK",
+ "ROLLED_BACK"
+ ]
+ },
+ "isAutomaticInvocation": {
+ "description": "The Boolean is a data type having two values (TRUE and FALSE).\n",
+ "type": "boolean"
+ },
+ "verbosity": {
+ "description": "The enumeration LcmOpOccNotificationVerbosityType provides values to control the verbosity of LCM operation occurrence notifications. It shall comply with the provisions defined in table 6.5.4.11-1. * FULL: This signals a full notification which contains all change details. * SHORT: This signals a short notification which omits large-volume change details to reduce the size of data to\n be sent via the notification mechanism.\n",
+ "type": "string",
+ "enum": [
+ "FULL",
+ "SHORT"
+ ]
+ },
+ "affectedVnf": {
+ "description": "Information about the VNF instances that were affected during the lifecycle operation. See note 1.\n",
+ "type": "array",
+ "items": {
+ "description": "This type provides information about added, deleted and modified VNFs.\nNOTE: At least one of the attributes \"changedVnfInfo\", \"changedExtConnectivity\" or \"modificationsTriggeredByVnfPkgChange\" shall be present. Not more than one of \"changedVnfInfo\" and \"modificationsTriggeredByVnfPkgChange\" shall be present.\n",
+ "type": "object",
+ "required": [
+ "vnfInstanceId",
+ "vnfdId",
+ "vnfProfileId",
+ "vnfName",
+ "changeType",
+ "changeResult"
+ ],
+ "anyOf": [
+ {
+ "required": [
+ "changedExtConnectivity"
+ ]
+ },
+ {
+ "oneOf": [
+ {
+ "required": [
+ "changedVnfInfo"
+ ]
+ },
+ {
+ "required": [
+ "modificationsTriggeredByVnfPkgChange"
+ ]
+ }
+ ]
+ }
+ ],
+ "properties": {
+ "vnfInstanceId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfProfileId": {
+ "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vnfName": {
+ "description": "Name of the VNF Instance.\n",
+ "type": "string"
+ },
+ "changeType": {
+ "description": "Signals the type of change Permitted values: - ADD - REMOVE - INSTANTIATE - TERMINATE - SCALE - CHANGE_FLAVOUR - HEAL - OPERATE - MODIFY_INFORMATION - CHANGE_EXTERNAL_VNF_CONNECTIVITY - CHANGE_VNFPKG\n",
+ "type": "string",
+ "enum": [
+ "ADD",
+ "REMOVE",
+ "INSTANTIATE",
+ "TERMINATE",
+ "SCALE",
+ "CHANGE_FLAVOUR",
+ "HEAL",
+ "OPERATE",
+ "MODIFY_INFORMATION",
+ "CHANGE_EXTERNAL_VNF_CONNECTIVITY",
+ "CHANGE_VNFPKG"
+ ]
+ },
+ "changeResult": {
+ "description": "Signals the result of change identified by the \"changeType\" attribute. Permitted values: - COMPLETED - ROLLED_BACK - FAILED\n",
+ "type": "string",
+ "enum": [
+ "COMPLETED",
+ "ROLLED_BACK",
+ "FAILED"
+ ]
+ },
+ "changedInfo": {
+ "description": "Information about the changed VNF instance information, including VNF configurable properties,if applicable. When the \"changedInfo\" attribute is present, either the \"changedVnfInfo\" attribute or the \"changedExtConnectivity\" attribute or both shall be present.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "required": [
+ "changedVnfInfo"
+ ]
+ },
+ {
+ "required": [
+ "changedVnfInfo"
+ ]
+ },
+ {
+ "required": [
+ "modificationsTriggeredByVnfPkgChange"
+ ]
+ }
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "changedVnfInfo"
+ ]
+ },
+ {
+ "required": [
+ "modificationsTriggeredByVnfPkgChange"
+ ]
+ }
+ ],
+ "properties": {
+ "changedVnfInfo": {
+ "description": "This type represents the information that is requested to be modified for a VNF instance. The information to be modified shall comply with the associated NSD. EXAMPLE. The vnfPkgId attribute value for a particular VNF instance can only be updated with a value that matches the identifier value of a VNF package whose vnfdId is present in the associated profile of the NSD.\n",
+ "type": "object",
+ "required": [
+ "vnfInstanceId"
+ ],
+ "properties": {
"vnfInstanceId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
},
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
+ "vnfInstanceName": {
+ "description": "New value of the \"vnfInstanceName\" attribute in \"VnfInstance\", or \"null\" to remove the attribute.\n",
+ "type": "string"
},
- "vnfProfileId": {
- "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
- "type": "string"
+ "vnfInstanceDescription": {
+ "description": "New value of the \"vnfInstanceDescription\" attribute in \"VnfInstance\", or \"null\" to remove the attribute.\n",
+ "type": "string"
},
- "vnfName": {
- "description": "Name of the VNF Instance.\n",
- "type": "string"
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
},
- "changeType": {
- "description": "Signals the type of change Permitted values: - ADD - REMOVE - INSTANTIATE - TERMINATE - SCALE - CHANGE_FLAVOUR - HEAL - OPERATE - MODIFY_INFORMATION - CHANGE_EXTERNAL_VNF_CONNECTIVITY - CHANGE_VNFPKG\n",
- "type": "string",
- "enum": ["ADD", "REMOVE", "INSTANTIATE", "TERMINATE", "SCALE", "CHANGE_FLAVOUR", "HEAL", "OPERATE", "MODIFY_INFORMATION", "CHANGE_EXTERNAL_VNF_CONNECTIVITY", "CHANGE_VNFPKG"]
+ "vnfConfigurableProperties": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
},
- "changeResult": {
- "description": "Signals the result of change identified by the \"changeType\" attribute. Permitted values: - COMPLETED - ROLLED_BACK - FAILED\n",
- "type": "string",
- "enum": ["COMPLETED", "ROLLED_BACK", "FAILED"]
+ "metadata": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
},
- "changedInfo": {
- "description": "Information about the changed VNF instance information, including VNF configurable properties,if applicable. When the \"changedInfo\" attribute is present, either the \"changedVnfInfo\" attribute or the \"changedExtConnectivity\" attribute or both shall be present.\n",
+ "extensions": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ },
+ "changedExtConnectivity": {
+ "description": "Information about changed external connectivity, if applicable. Only information about external VL instances that have been added or modified shall be provided. See note.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents information about an VNF external VL.",
+ "type": "object",
+ "required": [
+ "id",
+ "resourceHandle",
+ "currentVnfExtCpData"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceHandle": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would correspond to the ‘kind’ field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the ‘claimName’ field in the Kubernetes® manifest, or a compound name built by Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the ‘metadata.name’ field in Kubernetes® manifest. \n",
"type": "object",
- "anyOf": [{
- "required": ["changedVnfInfo"]
- }, {
- "required": ["changedVnfInfo"]
- }, {
- "required": ["modificationsTriggeredByVnfPkgChange"]
- }],
- "oneOf": [{
- "required": ["changedVnfInfo"]
- }, {
- "required": ["modificationsTriggeredByVnfPkgChange"]
- }],
+ "required": [
+ "resourceId"
+ ],
"properties": {
- "changedVnfInfo": {
- "description": "This type represents the information that is requested to be modified for a VNF instance. The information to be modified shall comply with the associated NSD. EXAMPLE. The vnfPkgId attribute value for a particular VNF instance can only be updated with a value that matches the identifier value of a VNF package whose vnfdId is present in the associated profile of the NSD.\n",
- "type": "object",
- "required": ["vnfInstanceId"],
- "properties": {
- "vnfInstanceId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfInstanceName": {
- "description": "New value of the \"vnfInstanceName\" attribute in \"VnfInstance\", or \"null\" to remove the attribute.\n",
- "type": "string"
- },
- "vnfInstanceDescription": {
- "description": "New value of the \"vnfInstanceDescription\" attribute in \"VnfInstance\", or \"null\" to remove the attribute.\n",
- "type": "string"
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceProviderId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "type": "string"
+ },
+ "vimLevelAdditionalResourceInfo": {
+ "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
+ "type": "object",
+ "properties": {
+ "hostName": {
+ "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "persistentVolume": {
+ "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ },
+ "containerNamespace": {
+ "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise. \n",
+ "type": "string"
+ }
+ }
+ },
+ "extLinkPorts": {
+ "description": "Link ports of this VL.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents information about a link port of an external VL, i.e. a port providing connectivity for the VNF to an NS VL. NOTE 1: The use cases UC#4 and UC#5 in Annex A.4 of ETSI GS NFV-IFA 007 provide examples for such a configuration. NOTE 2: The value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\" attribute.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "resourceHandle"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceHandle": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would correspond to the ‘kind’ field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the ‘claimName’ field in the Kubernetes® manifest, or a compound name built by Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the ‘metadata.name’ field in Kubernetes® manifest. \n",
+ "type": "object",
+ "required": [
+ "resourceId"
+ ],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceProviderId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "type": "string"
+ },
+ "vimLevelAdditionalResourceInfo": {
+ "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
+ "type": "object",
+ "properties": {
+ "hostName": {
+ "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
},
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
+ "persistentVolume": {
+ "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
},
- "vnfConfigurableProperties": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ },
+ "containerNamespace": {
+ "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise. \n",
+ "type": "string"
+ }
+ }
+ },
+ "cpInstanceId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "secondaryCpInstanceId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "trunkResourceId": {
+ "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "extNetAttDefResource": {
+ "description": "Network attachment definition resources that provide the specification of the interface to attach connection points to this VL.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the information related to a network attachment definition resource that provides the specification of the interface used to connect one or multiple connection points to a secondary container cluster network\n",
+ "type": "object",
+ "required": [
+ "netAttDefResourceInfoId",
+ "netAttDefResource"
+ ],
+ "properties": {
+ "netAttDefResourceInfoId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "netAttDefResource": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would correspond to the ‘kind’ field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the ‘claimName’ field in the Kubernetes® manifest, or a compound name built by Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the ‘metadata.name’ field in Kubernetes® manifest. \n",
+ "type": "object",
+ "required": [
+ "resourceId"
+ ],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceProviderId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "type": "string"
+ },
+ "vimLevelAdditionalResourceInfo": {
+ "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
+ "type": "object",
+ "properties": {
+ "hostName": {
+ "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
},
- "metadata": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
+ "persistentVolume": {
+ "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
},
- "extensions": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
}
+ }
+ },
+ "containerNamespace": {
+ "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise. \n",
+ "type": "string"
}
+ }
},
- "changedExtConnectivity": {
- "description": "Information about changed external connectivity, if applicable. Only information about external VL instances that have been added or modified shall be provided. See note.\n",
- "type": "array",
- "items": {
- "description": "This type represents information about an VNF external VL.",
+ "associatedExtCpId": {
+ "description": "Identifier of the external CP of the VNF associated to this network attachment definition resource. Shall be present when the network attachment definition resource is used for external connectivity by the VNF\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ }
+ },
+ "associatedVnfcCpId": {
+ "description": "Identifier of the VNFC CP of the VNF associated to this network attachment definition resource. May be present when the network attachment definition resource is used for internal connectivity by the VNF.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ }
+ }
+ }
+ }
+ },
+ "currentVnfExtCpData": {
+ "description": "This type represents configuration information for external CPs created from a CPD.\nNOTE 1: In case this identifier refers to a CPD with trunking enabled, the external CP instances created from this CPD will represent ports in a trunk. NOTE 2: The map entry value shall be set to \"null\" in order to delete a \"VnfExtCpConfig\" entry identified by a particular key value from the map, i.e. for the disconnection of an existing external CP instance addressed by cpInstanceId in the deleted map entry from a particular external virtual link, and deletion of that instance in case it represents a subport. Deleting the last key from the map removes the affected instance of the \"VnfExtCpData\" structure from its parent data structure. NOTE 3: Within one VNF instance, all VNFC instances created from a particular VDU have the same external connectivity. Thus, given a particular value of the \"cpdId' attribute, there shall be one \"cpConfig\" entry for each VNFC instance that has been or can be created from a VDU which includes a CPD identified by the \"cpdId\" attribute. If the cpConfig represents a subport in a trunk, all \"cpConfig\" entries in this list shall have the same segmentationId, which means they are connected to the same set of external VLs via the trunk. NOTE 4: If, as defined by the input parameters of a \"ChangeVnfFlavour\", \"ChangeExtVnfConnectivity\" or \"ChangeCurrentVnfPkg\" operation, a cpConfig map entry identified by a particular map key value is moved into another \"ExtVirtualLinkData\" or \"VnfExtCpData\" structure, this particular cpConfig map entry may be used by an external CP instance different than the one that has used it before the operation, or by no external CP instance at all. Renaming a CPD identifier during the \"changeCurrentVnfPkg\" operation does not count as moving the related \"cpConfig\" map entries to a new \"extCpData\" structure.\n",
+ "type": "object",
+ "required": [
+ "cpdId"
+ ],
+ "properties": {
+ "cpdId": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
+ "type": "string"
+ },
+ "cpConfig": {
+ "description": "Map of instance data that need to be configured on the CP instances created from the respective CPD. The key of the map which identifies the individual VnfExtCpConfig entries is of type \"IdentifierInVnf\" and is managed by the API consumer. The entries shall be applied by the VNFM according to the rules of JSON Merge Patch (see IETF RFC 7396 [11]). See notes 2, 3 and 4.\n",
+ "type": "object",
+ "additionalProperties": {
+ "description": "This type represents an externally provided link port, or a network attachment definition resource of secondary container cluster network, or network address information per instance of a VNF external connection point. In the case of VM-based deployment of the VNFC exposing the external CP: In case a link port is provided, the NFVO shall use that link port when connecting the VNF external CP to the external VL. • In case a link port is not provided, the NFVO or VNFM shall create a link port on the external VL, and use that link port to connect the VNF external CP to the external VL. In the case of container-based deployment of the VNFC exposing the external CP, the NFVO and VNFM shall use the network attachment definition resource of secondary container cluster network when connecting the CP to the external VL.\nNOTE 1: The following conditions apply to the attributes \"linkPortId\" and \"cpProtocolData\"\n for an external CP instance connected or to be connected to a virtual network not\n categorized as secondary container cluster network:\n - At least one of the \"linkPortId\" and \"cpProtocolData\" attributes shall be present for\n an external CP instance representing a subport that is to be created, or an external CP instance\n that is to be created by creating the corresponding VNFC or VNF instance during the current or\n a subsequent LCM operation, or for an existing external CP instance that is to be re-configured\n or added to a particular external virtual link.\n - If the \"cpProtocolData\" attribute is absent, the \"linkPortId\" attribute shall be provided\n referencing a pre-created link port with pre-configured address information.\n - If both \"cpProtocolData\" and \"linkportId\" are provided, the API consumer shall ensure that\n the cpProtocolData can be used with the pre-created link port referenced by \"linkPortId\".\nNOTE 2: In case the NFVO manages its own identifier space, the NFVO may remap this identifier\n when communicating with the VNFM. If the NFVO knows that there can be an identifier collision\n when communicating with the VNFM by using the identifier from the OSS/BSS, the NFVO shall remap it.\nNOTE 3: The following conditions apply to the attributes \"netAttDefResourceId\" and \"cpProtocolData\" for an external CP\n instance connected or to be connected to a secondary container cluster network:\n − Void.\n − At least one of these attributes shall be present for a to-be-created external CP instance or an existing\n external CP instance.\nNOTE 4: Cardinality greater than 1 is only applicable for specific cases where more than one network\n attachment definition resource is needed to fulfil the connectivity requirements of the external CP,\n e.g. to build a link redundant mated pair in SR-IOV cases. When more than one \"netAttDefResourceId\"\n is indicated, all shall belong to the same namespace as defined by the corresponding \n \"containerNamespace\" attribute in the \"resourceHandle\" attribute in the \"NetAttDefResourceData\".\nNOTE 5: Either \"linkPortId\" or \"netAttDefResourceId\" may be included, but not both.\n",
+ "type": "object",
+ "oneOf": [
+ {
+ "required": [
+ "linkPortId"
+ ]
+ },
+ {
+ "required": [
+ "cpProtocolData"
+ ]
+ }
+ ],
+ "properties": {
+ "parentCpConfigId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "linkPortId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "createExtLinkPort": {
+ "description": "Indicates the need to create a dedicated link port for the external CP. If set to True, a link port is created. If set to False, no link port is created. This attribute is only applicable for external CP instances without a floating IP address that expose a VIP CP instance for which a dedicated IP address is allocated. It shall be present in that case and shall be absent otherwise.\n",
+ "type": "boolean"
+ },
+ "cpProtocolData": {
+ "description": "Parameters for configuring the network protocols on the link port that connects the CP to a VL. See notes 1 and 3.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents network protocol data.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the present document in a backwards-compatible way. In the current version of the present document, only IP over Ethernet is supported.\n",
"type": "object",
- "required": ["id", "resourceHandle", "currentVnfExtCpData"],
+ "required": [
+ "layerProtocol"
+ ],
"properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
+ "layerProtocol": {
+ "description": "Identifier of layer(s) and protocol(s). Permitted values: - IP_OVER_ETHERNET - IP_FOR_VIRTUAL_CP See note.\n",
+ "type": "string",
+ "enum": [
+ "IP_OVER_ETHERNET",
+ "IP_FOR_VIRTUAL_CP"
+ ]
+ },
+ "ipOverEthernet": {
+ "description": "This type represents network address data for IP over Ethernet. NOTE 1: At least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2: Exactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present. NOTE 3: If the CP instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4: Depending on the NFVI networking infrastructure, the \"segmentationId\" may indicate the actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header of the packets or it may be an identifier used between the application and the NFVI networking infrastructure to identify the network sub-interface of the trunk port in question. In the latter case the NFVI infrastructure will map this local \"segmentationId\" to whatever \"segmentationId\" is actually used by the NFVI's transport technology.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "required": [
+ "ipAddresses"
+ ]
+ },
+ {
+ "required": [
+ "macAddress"
+ ]
+ }
+ ],
+ "properties": {
+ "macAddress": {
+ "description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
+ "type": "string",
+ "format": "MAC"
+ },
+ "segmentationType": {
+ "description": "Specifies the encapsulation type for the traffics coming in and out of the trunk subport. Permitted values are: - VLAN: The subport uses VLAN as encapsulation type. - INHERIT: The subport gets its segmentation type from the network it is connected to. This attribute may be present for CP instances that represent subports in a trunk and shall be absent otherwise. If this attribute is not present for a subport CP instance, default value VLAN shall be used.\n",
+ "type": "string",
+ "enum": [
+ "VLAN",
+ "INHERIT"
+ ]
+ },
+ "segmentationId": {
+ "description": "Identification of the network segment to which the CP instance connects to. See note 3 and note 4.\n",
"type": "string"
- },
- "resourceHandle": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes instance the vimLevelResourceType is the type of resource, as would correspond to the kind field if the resource is declared in its own Kubernetes manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the claimName field in the Kubernetes manifest, or a compound name built by Kubernetes if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the metadata.name field in Kubernetes manifest. \n",
- "type": "object",
- "required": ["resourceId"],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
+ },
+ "ipAddresses": {
+ "description": "List of IP addresses to assign to the CP instance. Each entry represents IP address data for fixed or dynamic IP address assignment per subnet. If this attribute is not present, no IP address shall be assigned. See note 1.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": [
+ "type"
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "fixedAddresses"
+ ]
},
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
+ {
+ "required": [
+ "numDynamicAddresses"
+ ]
},
- "resourceId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
+ {
+ "required": [
+ "addressRange"
+ ]
+ }
+ ],
+ "properties": {
+ "type": {
+ "description": "The type of the IP addresses. Permitted values:\n - IPV4\n - IPV6\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
},
- "vimLevelResourceType": {
- "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
- "type": "string"
+ "fixedAddresses": {
+ "description": "Fixed addresses to assign (from the subnet defined by \"subnetId\" if provided). Exactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present.\n",
+ "type": "array",
+ "items": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ }
},
- "vimLevelAdditionalResourceInfo": {
- "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
- "type": "object",
- "properties": {
- "hostName": {
- "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "persistentVolume": {
- "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
+ "numDynamicAddresses": {
+ "description": "Number of dynamic addresses to assign (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
+ "type": "integer"
},
- "containerNamespace": {
- "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
- "type": "string"
- }
- }
- },
- "extLinkPorts": {
- "description": "Link ports of this VL.\n",
- "type": "array",
- "items": {
- "description": "This type represents information about a link port of an external VL, i.e. a port providing connectivity for the VNF to an NS VL. NOTE 1: The use cases UC#4 and UC#5 in Annex A.4 of ETSI GS NFV-IFA 007 provide examples for such a configuration. NOTE 2: The value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\" attribute.\n",
- "type": "object",
- "required": ["id", "resourceHandle"],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceHandle": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes instance the vimLevelResourceType is the type of resource, as would correspond to the kind field if the resource is declared in its own Kubernetes manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the claimName field in the Kubernetes manifest, or a compound name built by Kubernetes if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the metadata.name field in Kubernetes manifest. \n",
- "type": "object",
- "required": ["resourceId"],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
- "type": "string"
- },
- "vimLevelAdditionalResourceInfo": {
- "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
- "type": "object",
- "properties": {
- "hostName": {
- "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "persistentVolume": {
- "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "containerNamespace": {
- "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
- "type": "string"
- }
- }
- },
- "cpInstanceId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
+ "addressRange": {
+ "description": "An IP address range to be used, e.g. in case of egress connections. In case this attribute is present, IP addresses from the range will be used.\n",
+ "type": "object",
+ "required": [
+ "minAddress",
+ "maxAddress"
+ ],
+ "properties": {
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
},
- "secondaryCpInstanceId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "trunkResourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
}
+ }
+ },
+ "subnetId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
}
+ }
}
- },
- "extNetAttDefResource": {
- "description": "Network attachment definition resources that provide the specification of the interface to attach connection points to this VL.\n",
+ }
+ }
+ },
+ "virtualCpAddress": {
+ "description": "This type represents network address data for a virtual CP. It shall comply with the provisions defined in table 6.5.3.12a-1.\nNOTE 1: If the container cluster is set up to be able to configure an external load balancer this address will be\n used, otherwise it will be ignored by the CISM.\nNOTE 2: In case the cluster can configure an external load balancer but no loadBalancerIp is provided the\n container cluster will assign an IP address.\nNOTE 3: The attribute is only relevant if the virtual CP is instantiated in a cluster that supports configuration of IP\n address pools for virtual CPs. Otherwise it shall be ignored. MetalLB is an example of a solution for\n Kubernetes® that supports configuration of address pools for load balancer services.\nNOTE 4: The loadBalancerIp and the addressPoolName attributes shall not be present at the same time.\n",
+ "type": "object",
+ "required": [
+ "type"
+ ],
+ "properties": {
+ "type": {
+ "description": "Identifier of layer(s) and protocol(s). Permitted values: IP_OVER_ETHERNET.\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
+ },
+ "loadBalancerIp": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which the container cluster will assign an IP address to the virtual CP. See notes 3 and 4.\n",
"type": "array",
"items": {
- "description": "This type represents the information related to a network attachment definition resource that provides the specification of the interface used to connect one or multiple connection points to a secondary container cluster network\n",
- "type": "object",
- "required": ["netAttDefResourceInfoId", "netAttDefResource"],
- "properties": {
- "netAttDefResourceInfoId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "netAttDefResource": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes instance the vimLevelResourceType is the type of resource, as would correspond to the kind field if the resource is declared in its own Kubernetes manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the claimName field in the Kubernetes manifest, or a compound name built by Kubernetes if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the metadata.name field in Kubernetes manifest. \n",
- "type": "object",
- "required": ["resourceId"],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
- "type": "string"
- },
- "vimLevelAdditionalResourceInfo": {
- "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
- "type": "object",
- "properties": {
- "hostName": {
- "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "persistentVolume": {
- "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "containerNamespace": {
- "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
- "type": "string"
- }
- }
- },
- "associatedExtCpId": {
- "description": "Identifier of the external CP of the VNF associated to this network attachment definition resource. Shall be present when the network attachment definition resource is used for external connectivity by the VNF\n",
- "type": "array",
- "items": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- }
- },
- "associatedVnfcCpId": {
- "description": "Identifier of the VNFC CP of the VNF associated to this network attachment definition resource. May be present when the network attachment definition resource is used for internal connectivity by the VNF.\n",
- "type": "array",
- "items": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- }
- }
- }
- }
- },
- "currentVnfExtCpData": {
- "description": "This type represents configuration information for external CPs created from a CPD.\nNOTE 1: In case this identifier refers to a CPD with trunking enabled, the external CP instances created from this CPD will represent ports in a trunk. NOTE 2: The map entry value shall be set to \"null\" in order to delete a \"VnfExtCpConfig\" entry identified by a particular key value from the map, i.e. for the disconnection of an existing external CP instance addressed by cpInstanceId in the deleted map entry from a particular external virtual link, and deletion of that instance in case it represents a subport. Deleting the last key from the map removes the affected instance of the \"VnfExtCpData\" structure from its parent data structure. NOTE 3: Within one VNF instance, all VNFC instances created from a particular VDU have the same external connectivity. Thus, given a particular value of the \"cpdId' attribute, there shall be one \"cpConfig\" entry for each VNFC instance that has been or can be created from a VDU which includes a CPD identified by the \"cpdId\" attribute. If the cpConfig represents a subport in a trunk, all \"cpConfig\" entries in this list shall have the same segmentationId, which means they are connected to the same set of external VLs via the trunk. NOTE 4: If, as defined by the input parameters of a \"ChangeVnfFlavour\", \"ChangeExtVnfConnectivity\" or \"ChangeCurrentVnfPkg\" operation, a cpConfig map entry identified by a particular map key value is moved into another \"ExtVirtualLinkData\" or \"VnfExtCpData\" structure, this particular cpConfig map entry may be used by an external CP instance different than the one that has used it before the operation, or by no external CP instance at all. Renaming a CPD identifier during the \"changeCurrentVnfPkg\" operation does not count as moving the related \"cpConfig\" map entries to a new \"extCpData\" structure.\n",
- "type": "object",
- "required": ["cpdId"],
- "properties": {
- "cpdId": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "cpConfig": {
- "description": "Map of instance data that need to be configured on the CP instances created from the respective CPD. The key of the map which identifies the individual VnfExtCpConfig entries is of type \"IdentifierInVnf\" and is managed by the API consumer. The entries shall be applied by the VNFM according to the rules of JSON Merge Patch (see IETF RFC 7396 [11]). See notes 2, 3 and 4.\n",
- "type": "object",
- "additionalProperties": {
- "description": "This type represents an externally provided link port, or a network attachment definition resource of secondary container cluster network, or network address information per instance of a VNF external connection point. In the case of VM-based deployment of the VNFC exposing the external CP: In case a link port is provided, the NFVO shall use that link port when connecting the VNF external CP to the external VL. In case a link port is not provided, the NFVO or VNFM shall create a link port on the external VL, and use that link port to connect the VNF external CP to the external VL. In the case of container-based deployment of the VNFC exposing the external CP, the NFVO and VNFM shall use the network attachment definition resource of secondary container cluster network when connecting the CP to the external VL.\nNOTE 1: The following conditions apply to the attributes \"linkPortId\" and \"cpProtocolData\" for an external CP instance connected or to be connected to a virtual network not\n categorized as secondary container cluster network:\n - At least one of the \"linkPortId\" and \"cpProtocolData\" attributes shall be present for\n an external CP instance representing a subport that is to be created, or an external CP instance\n that is to be created by creating the corresponding VNFC or VNF instance during the current or\n a subsequent LCM operation, or for an existing external CP instance that is to be re-configured\n or added to a particular external virtual link.\n - If the \"cpProtocolData\" attribute is absent, the \"linkPortId\" attribute shall be provided\n referencing a pre-created link port with pre-configured address information.\n - If both \"cpProtocolData\" and \"linkportId\" are provided, the API consumer shall ensure that\n the cpProtocolData can be used with the pre-created link port referenced by \"linkPortId\".\nNOTE 2: In case the NFVO manages its own identifier space, the NFVO may remap this identifier when communicating with the VNFM. If the NFVO knows that there can be an identifier collision when communicating with the VNFM by using the identifier from the OSS/BSS, the NFVO shall remap it. NOTE 3: The following conditions apply to the attributes netAttDefResourceId and cpProtocolData for an external CP instance connected or to be connected to a secondary container cluster network; The \"netAttDefResourceId\" and \"cpProtocolData\" attributes shall both be absent for the deletion of an existing external CP instance addressed by \"cpInstanceId\". At least one of these attributes shall be present for a to-be-created external CP instance or an existing external CP instance. NOTE 4: Cardinality greater than 1 is only applicable for specific cases where more than one network attachment definition resource is needed to fulfil the connectivity requirements of the external CP, e.g. to build a link redundant mated pair in SR-IOV cases. When more than one \"netAttDefResourceId\" is indicated, all shall belong to the same namespace as defined by the corresponding \"netAttDefResourceNamespace\" attribute in the \"NetAttDefResourceData\". NOTE 5: Either \"linkPortId\" or \"netAttDefResourceId\" may be included, but not both.\n",
- "type": "object",
- "oneOf": [{
- "required": ["linkPortId"]
- }, {
- "required": ["cpProtocolData"]
- }],
- "properties": {
- "parentCpConfigId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "linkPortId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "createExtLinkPort": {
- "description": "Indicates the need to create a dedicated link port for the external CP. If set to True, a link port is created. If set to False, no link port is created. This attribute is only applicable for external CP instances without a floating IP address that expose a VIP CP instance for which a dedicated IP address is allocated. It shall be present in that case and shall be absent otherwise.\n",
- "type": "boolean"
- },
- "cpProtocolData": {
- "description": "Parameters for configuring the network protocols on the link port that connects the CP to a VL. See notes 1 and 3.\n",
- "type": "array",
- "items": {
- "description": "This type represents network protocol data.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the present document in a backwards-compatible way. In the current version of the present document, only IP over Ethernet is supported.\n",
- "type": "object",
- "required": ["layerProtocol"],
- "properties": {
- "layerProtocol": {
- "description": "Identifier of layer(s) and protocol(s). Permitted values: - IP_OVER_ETHERNET - IP_FOR_VIRTUAL_CP See note.\n",
- "type": "string",
- "enum": ["IP_OVER_ETHERNET", "IP_FOR_VIRTUAL_CP"]
- },
- "ipOverEthernet": {
- "description": "This type represents network address data for IP over Ethernet. NOTE 1: At least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2: Exactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present. NOTE 3: If the CP instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4: Depending on the NFVI networking infrastructure, the \"segmentationId\" may indicate the actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header of the packets or it may be an identifier used between the application and the NFVI networking infrastructure to identify the network sub-interface of the trunk port in question. In the latter case the NFVI infrastructure will map this local \"segmentationId\" to whatever \"segmentationId\" is actually used by the NFVI's transport technology.\n",
- "type": "object",
- "anyOf": [{
- "required": ["ipAddresses"]
- }, {
- "required": ["macAddress"]
- }],
- "properties": {
- "macAddress": {
- "description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
- "type": "string",
- "format": "MAC"
- },
- "segmentationType": {
- "description": "Specifies the encapsulation type for the traffics coming in and out of the trunk subport. Permitted values are: - VLAN: The subport uses VLAN as encapsulation type. - INHERIT: The subport gets its segmentation type from the network it is connected to. This attribute may be present for CP instances that represent subports in a trunk and shall be absent otherwise. If this attribute is not present for a subport CP instance, default value VLAN shall be used.\n",
- "type": "string",
- "enum": ["VLAN", "INHERIT"]
- },
- "segmentationId": {
- "description": "Identification of the network segment to which the CP instance connects to. See note 3 and note 4.\n",
- "type": "string"
- },
- "ipAddresses": {
- "description": "List of IP addresses to assign to the CP instance. Each entry represents IP address data for fixed or dynamic IP address assignment per subnet. If this attribute is not present, no IP address shall be assigned. See note 1.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": ["type"],
- "oneOf": [{
- "required": ["fixedAddresses"]
- }, {
- "required": ["numDynamicAddresses"]
- }, {
- "required": ["addressRange"]
- }],
- "properties": {
- "type": {
- "description": "The type of the IP addresses. Permitted values: - IPV4\n - IPV6\n",
- "type": "string",
- "enum": ["IPV4", "IPV6"]
- },
- "fixedAddresses": {
- "description": "Fixed addresses to assign (from the subnet defined by \"subnetId\" if provided). Exactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present.\n",
- "type": "array",
- "items": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- },
- "numDynamicAddresses": {
- "description": "Number of dynamic addresses to assign (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
- "type": "integer"
- },
- "addressRange": {
- "description": "An IP address range to be used, e.g. in case of egress connections. In case this attribute is present, IP addresses from the range will be used.\n",
- "type": "object",
- "required": ["minAddress", "maxAddress"],
- "properties": {
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- },
- "subnetId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- }
- }
- }
- },
- "virtualCpAddress": {
- "description": "This type represents network address data for a virtual CP. It shall comply with the provisions defined in table 6.5.3.12a-1.\n",
- "type": "object",
- "required": ["type"],
- "properties": {
- "type": {
- "description": "Identifier of layer(s) and protocol(s). Permitted values: IP_OVER_ETHERNET.\n",
- "type": "string",
- "enum": ["IPV4", "IPV6"]
- },
- "loadBalancerIp": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- }
- }
- }
- },
- "netAttDefResourceId": {
- "description": "Identifier of the \"NetAttDefResourceData\" structure that provides the specification of the interface to attach the external CP to a secondary container cluster network. It is only applicable if the external CP is connected or to be connected to a secondary container cluster network. It shall not be present if the external CP is related to a virtual network not categorized as secondary container cluster network. See notes 3, 4 and 5.\n",
- "type": "array",
- "items": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- }
- }
- }
- }
- }
+ "type": "string"
}
+ }
}
+ }
}
+ }
+ },
+ "netAttDefResourceId": {
+ "description": "Identifier of the \"NetAttDefResourceData\" structure that provides the specification of the interface to attach the external CP to a secondary container cluster network. It is only applicable if the external CP is connected or to be connected to a secondary container cluster network. It shall not be present if the external CP is related to a virtual network not categorized as secondary container cluster network. See notes 3, 4 and 5.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ }
}
- },
- "modificationsTriggeredByVnfPkgChange": {
- "description": "This type represents attribute modifications that were performed by the VNFM on an \"Individual VNF instance\" resource when changing the current VNF package. The \"ModificationsTriggeredByVnfPkgChange\" data type shall comply with the provisions defined in table 6.5.3.79-1.\n",
- "type": "object",
- "properties": {
- "vnfConfigurableProperties": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- },
- "metadata": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- },
- "extensions": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfProvider": {
- "description": "If present, this attribute signals the new value of the \"vnfProvider\" attribute in \"VnfInstance\". If present, this attribute (which depends on the value of the \"vnfdId\" attribute) was modified implicitly during the related operation, and contains a copy of the value of the related attribute from the VNFD in the VNF Package identified by the \"vnfdId\" attribute.\n",
- "type": "string"
- },
- "vnfProductName": {
- "description": "If present, this attribute signals the new value of the \"vnfProductName\" attribute in \"VnfInstance\". If present, this attribute (which depends on the value of the \"vnfdId\" attribute) was modified implicitly during the related operation, and contains a copy of the value of the related attribute from the VNFD in the VNF Package identified by the \"vnfdId\" attribute.\n",
- "type": "string"
- },
- "vnfSoftwareVersion": {
- "description": "A Version. Representation: string of variable length.\n",
- "type": "string"
- },
- "vnfdVersion": {
- "description": "A Version. Representation: string of variable length.\n",
- "type": "string"
- }
- }
+ }
}
+ }
}
+ }
}
- }
- }
- },
- "affectedPnf": {
- "description": "Information about the PNF instances that were affected during the lifecycle operation. See note 1.\n",
- "type": "array",
- "items": {
- "description": "This type provides information about added, deleted and modified PNFs. It shall comply with the provisions in Table 6.5.3.3-1.\n",
- "type": "object",
- "required": ["pnfId", "pnfdId", "pnfProfileId", "cpInstanceId"],
- "properties": {
- "pnfId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
+ }
+ },
+ "modificationsTriggeredByVnfPkgChange": {
+ "description": "This type represents attribute modifications that were performed by the VNFM on an \"Individual VNF instance\" resource when changing the current VNF package. The \"ModificationsTriggeredByVnfPkgChange\" data type shall comply with the provisions defined in table 6.5.3.79-1.\n",
+ "type": "object",
+ "properties": {
+ "vnfConfigurableProperties": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
},
- "pnfdId": {
- "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
- "type": "string"
+ "metadata": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
},
- "pnfProfileId": {
- "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
- "type": "string"
+ "extensions": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
},
- "pnfName": {
- "description": "Name of the PNF.\n",
- "type": "string"
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
},
- "cpInstanceId": {
- "description": "Identifier of the CP in the scope of the PNF.\n",
- "type": "array",
- "items": {
- "description": "An Identifier that is unique within respect to a PNF. Representation: string of variable length.\n",
- "type": "string"
- }
+ "vnfProvider": {
+ "description": "If present, this attribute signals the new value of the \"vnfProvider\" attribute in \"VnfInstance\". If present, this attribute (which depends on the value of the \"vnfdId\" attribute) was modified implicitly during the related operation, and contains a copy of the value of the related attribute from the VNFD in the VNF Package identified by the \"vnfdId\" attribute.\n",
+ "type": "string"
},
- "changeType": {
- "description": "Signals the type of change. Permitted values: - ADD - REMOVE - MODIFY\n",
- "type": "string",
- "enum": ["ADD", "REMOVE", "MODIFY"]
+ "vnfProductName": {
+ "description": "If present, this attribute signals the new value of the \"vnfProductName\" attribute in \"VnfInstance\". If present, this attribute (which depends on the value of the \"vnfdId\" attribute) was modified implicitly during the related operation, and contains a copy of the value of the related attribute from the VNFD in the VNF Package identified by the \"vnfdId\" attribute.\n",
+ "type": "string"
},
- "changeResult": {
- "description": "Signals the result of change identified by the \"changeType\" attribute. Permitted values: - COMPLETED - ROLLED_BACK - FAILED\n",
- "type": "string",
- "enum": ["COMPLETED", "ROLLED_BACK", "FAILED"]
+ "vnfSoftwareVersion": {
+ "description": "A Version. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vnfdVersion": {
+ "description": "A Version. Representation: string of variable length.\n",
+ "type": "string"
}
+ }
}
+ }
+ }
+ }
+ }
+ },
+ "affectedPnf": {
+ "description": "Information about the PNF instances that were affected during the lifecycle operation. See note 1.\n",
+ "type": "array",
+ "items": {
+ "description": "This type provides information about added, deleted and modified PNFs. It shall comply with the provisions in Table 6.5.3.3-1.\n",
+ "type": "object",
+ "required": [
+ "pnfId",
+ "pnfdId",
+ "pnfProfileId",
+ "cpInstanceId"
+ ],
+ "properties": {
+ "pnfId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "pnfdId": {
+ "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "pnfProfileId": {
+ "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "pnfName": {
+ "description": "Name of the PNF.\n",
+ "type": "string"
+ },
+ "cpInstanceId": {
+ "description": "Identifier of the CP in the scope of the PNF.\n",
+ "type": "array",
+ "items": {
+ "description": "An Identifier that is unique within respect to a PNF. Representation: string of variable length.\n",
+ "type": "string"
+ }
+ },
+ "changeType": {
+ "description": "Signals the type of change. Permitted values: - ADD - REMOVE - MODIFY\n",
+ "type": "string",
+ "enum": [
+ "ADD",
+ "REMOVE",
+ "MODIFY"
+ ]
+ },
+ "changeResult": {
+ "description": "Signals the result of change identified by the \"changeType\" attribute. Permitted values: - COMPLETED - ROLLED_BACK - FAILED\n",
+ "type": "string",
+ "enum": [
+ "COMPLETED",
+ "ROLLED_BACK",
+ "FAILED"
+ ]
+ }
+ }
+ }
+ },
+ "affectedVl": {
+ "description": "Information about the VL instances that were affected during the lifecycle operation. See note 1.\n",
+ "type": "array",
+ "items": {
+ "description": "This type provides information about added, deleted, modified and temporary VLs. NOTE: The resource handles of the affected NS link ports can be found by dereferencing the identifiers in the \"linkPortIds\" attribute.\n",
+ "type": "object",
+ "required": [
+ "nsVirtualLinkInstanceId",
+ "nsVirtualLinkDescId",
+ "vlProfileId",
+ "changeType",
+ "changeResult"
+ ],
+ "properties": {
+ "nsVirtualLinkInstanceId": {
+ "description": "An identifier that is unique with respect to a NS. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "nsVirtualLinkDescId": {
+ "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vlProfileId": {
+ "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "changeType": {
+ "description": "Signals the type of change. Permitted values: * ADD * DELETE * MODIFY * ADD_LINK_PORT * REMOVE_LINK_PORT\n",
+ "type": "string",
+ "enum": [
+ "ADD",
+ "DELETE",
+ "MODIFY",
+ "ADD_LINK_PORT",
+ "REMOVE_LINK_PORT"
+ ]
+ },
+ "linkPortIds": {
+ "description": "Identifiers of the link ports of the affected VL related to the change. Each identifier references an \"NsLinkPortInfo\" structure.\nShall be set when changeType is equal to \"ADD_LINK_PORT\" or \"REMOVE_LINK_PORT\", and the related \"NsLinkPortInfo\" structures are present (case \"add\") or have been present (case \"remove\") in the \"NsVirtualLinkInfo\" structure that is represented by the \"virtualLink¬Info\" attribute in the \"NsInstance\" structure. See note.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier that is unique with respect to a NS. Representation: string of variable length.\n",
+ "type": "string"
+ }
+ },
+ "changeResult": {
+ "description": "Signals the result of change identified by the \"changeType\" attribute. Permitted values: * COMPLETED * ROLLED_BACK * FAILED\n",
+ "type": "string",
+ "enum": [
+ "COMPLETED",
+ "ROLLED_BACK",
+ "FAILED"
+ ]
}
- },
- "affectedVl": {
- "description": "Information about the VL instances that were affected during the lifecycle operation. See note 1.\n",
- "type": "array",
- "items": {
- "description": "This type provides information about added, deleted, modified and temporary VLs. NOTE: The resource handles of the affected NS link ports can be found by dereferencing the identifiers in the \"linkPortIds\" attribute.\n",
- "type": "object",
- "required": ["nsVirtualLinkInstanceId", "nsVirtualLinkDescId", "vlProfileId", "changeType", "changeResult"],
- "properties": {
- "nsVirtualLinkInstanceId": {
- "description": "An identifier that is unique with respect to a NS. Representation: string of variable length.\n",
+ }
+ }
+ },
+ "affectedVnffg": {
+ "description": "Information about the VNFFG instances that were affected during the lifecycle operation. See note 1. \n",
+ "type": "array",
+ "items": {
+ "description": "This type provides information about added, deleted and modified VNFFG instances. It shall comply with the provisions in Table 6.5.3.5-1.\n",
+ "type": "object",
+ "required": [
+ "vnffgInstanceId",
+ "vnffgdId"
+ ],
+ "properties": {
+ "vnffgInstanceId": {
+ "description": "An identifier that is unique with respect to a NS. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vnffgdId": {
+ "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "changeType": {
+ "description": "Signals the type of change. Permitted values: - ADD - DELETE - MODIFY\n",
+ "type": "string",
+ "enum": [
+ "ADD",
+ "DELETE",
+ "MODIFY"
+ ]
+ },
+ "changeResult": {
+ "description": "Signals the result of change identified by the \"changeType\" attribute. Permitted values: - COMPLETED - ROLLED_BACK - FAILED\n",
+ "type": "string",
+ "enum": [
+ "COMPLETED",
+ "ROLLED_BACK",
+ "FAILED"
+ ]
+ }
+ }
+ }
+ },
+ "affectedNs": {
+ "description": "Information about the SAP instances that were affected during the lifecycle operation.See note 1.\n",
+ "type": "array",
+ "items": {
+ "description": "This type provides information about added, deleted and modified nested NSs. It shall comply with the provisions in Table 6.5.3.6-1.\n",
+ "type": "object",
+ "required": [
+ "nsInstanceId",
+ "nsdId",
+ "changeType",
+ "changeResult"
+ ],
+ "properties": {
+ "nsInstanceId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "nsdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "changeType": {
+ "description": "Signals the type of lifecycle change. Permitted values: - ADD - REMOVE - INSTANTIATE - SCALE - UPDATE - HEAL - TERMINATE\n",
+ "type": "string",
+ "enum": [
+ "ADD",
+ "REMOVE",
+ "INSTANTIATE",
+ "SCALE",
+ "UPDATE",
+ "HEAL",
+ "TERMINATE"
+ ]
+ },
+ "changeResult": {
+ "description": "Signals the result of change identified by the \"changeType\" attribute. Permitted values: - COMPLETED - ROLLED_BACK - FAILED - PARTIALLY_COMPLETED\n",
+ "type": "string",
+ "enum": [
+ "COMPLETED",
+ "ROLLED_BACK",
+ "FAILED",
+ "PARTIALLY_COMPLETED"
+ ]
+ },
+ "changedInfo": {
+ "description": "Information about the changed NS instance information, if applicable.\n",
+ "type": "object",
+ "properties": {
+ "wanConnectionInfoModifications": {
+ "description": "Information about the modified WAN related connectivity information, if applicable.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents attribute modifications that were performed on WAN connection information. The attributes that can be included consist of those requested to be modified explicitly with the \"UpdateNsRequest\" data structure. It shall comply with the provisions defined in table 6.5.3.93-1.\n",
+ "type": "object",
+ "required": [
+ "wanConnectionInfoId"
+ ],
+ "properties": {
+ "wanConnectionInfoId": {
+ "description": "An identifier with the intention of being globally unique.\n",
"type": "string"
- },
- "nsVirtualLinkDescId": {
- "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
+ },
+ "mscsName": {
+ "description": "If present, this attribute signals modifications of the \"mscsName\" attribute in \"MscsInfo\" as defined in clause 6.5.3.82.\n",
"type": "string"
- },
- "vlProfileId": {
- "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
+ },
+ "mscsDescription": {
+ "description": "If present, this attribute signals modifications of the \"mscsDescription\" attribute in \"MscsInfo\" as defined in clause 6.5.3.82.\n",
"type": "string"
- },
- "changeType": {
- "description": "Signals the type of change. Permitted values: * ADD * DELETE * MODIFY * ADD_LINK_PORT * REMOVE_LINK_PORT\n",
- "type": "string",
- "enum": ["ADD", "DELETE", "MODIFY", "ADD_LINK_PORT", "REMOVE_LINK_PORT"]
- },
- "linkPortIds": {
- "description": "Identifiers of the link ports of the affected VL related to the change. Each identifier references an \"NsLinkPortInfo\" structure.\nShall be set when changeType is equal to \"ADD_LINK_PORT\" or \"REMOVE_LINK_PORT\", and the related \"NsLinkPortInfo\" structures are present (case \"add\") or have been present (case \"remove\") in the \"NsVirtualLinkInfo\" structure that is represented by the \"virtualLinkInfo\" attribute in the \"NsInstance\" structure. See note.\n",
+ },
+ "mscsEndpoints": {
+ "description": "If present, this attribute signals modifications of certain entries in the \"mscsEndpoints\" attribute array in \"MscsInfo\", as defined in clause 6.5.3.82.\n",
"type": "array",
"items": {
- "description": "An identifier that is unique with respect to a NS. Representation: string of variable length.\n",
- "type": "string"
+ "description": "This type provides encapsulates information about an MSCS endpoint of the MSCS. It shall comply with the provisions defined in table 6.5.3.83-1.\n",
+ "type": "object",
+ "required": [
+ "mscsEndpointId",
+ "directionality",
+ "connectivityServiceEndpoinId"
+ ],
+ "properties": {
+ "mscsEndpointId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "directionality": {
+ "description": "Directionality of the data traffic in the context of the terminating MSCS endpoint from WAN’s perspective. Permitted values: - INBOUND: to indicate into the WAN. - OUTBOUND: to indicate from the WAN. - BOTH: to indicate bidirectional data traffic to/from the WAN.\n",
+ "type": "string",
+ "enum": [
+ "INBOUND",
+ "OUTBOUND",
+ "BOTH"
+ ]
+ },
+ "connectivityServiceEndpoinId": {
+ "description": "References the connectivity service endpoint configuration information applicable to support the MSCS endpoint. More than one connectivity service endpoint can be referred when endpoints are in LAG mode.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ }
+ }
}
- },
- "changeResult": {
- "description": "Signals the result of change identified by the \"changeType\" attribute. Permitted values: * COMPLETED * ROLLED_BACK * FAILED\n",
- "type": "string",
- "enum": ["COMPLETED", "ROLLED_BACK", "FAILED"]
- }
- }
- }
- },
- "affectedVnffg": {
- "description": "Information about the VNFFG instances that were affected during the lifecycle operation. See note 1.\n",
- "type": "array",
- "items": {
- "description": "This type provides information about added, deleted and modified VNFFG instances. It shall comply with the provisions in Table 6.5.3.5-1.\n",
- "type": "object",
- "required": ["vnffgInstanceId", "vnffgdId"],
- "properties": {
- "vnffgInstanceId": {
- "description": "An identifier that is unique with respect to a NS. Representation: string of variable length.\n",
- "type": "string"
- },
- "vnffgdId": {
- "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
- "type": "string"
- },
- "changeType": {
- "description": "Signals the type of change. Permitted values: - ADD - DELETE - MODIFY\n",
- "type": "string",
- "enum": ["ADD", "DELETE", "MODIFY"]
- },
- "changeResult": {
- "description": "Signals the result of change identified by the \"changeType\" attribute. Permitted values: - COMPLETED - ROLLED_BACK - FAILED\n",
- "type": "string",
- "enum": ["COMPLETED", "ROLLED_BACK", "FAILED"]
- }
- }
- }
- },
- "affectedNs": {
- "description": "Information about the SAP instances that were affected during the lifecycle operation.See note 1.\n",
- "type": "array",
- "items": {
- "description": "This type provides information about added, deleted and modified nested NSs. It shall comply with the provisions in Table 6.5.3.6-1.\n",
- "type": "object",
- "required": ["nsInstanceId", "nsdId", "changeType", "changeResult"],
- "properties": {
- "nsInstanceId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "nsdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "changeType": {
- "description": "Signals the type of lifecycle change. Permitted values: - ADD - REMOVE - INSTANTIATE - SCALE - UPDATE - HEAL - TERMINATE\n",
- "type": "string",
- "enum": ["ADD", "REMOVE", "INSTANTIATE", "SCALE", "UPDATE", "HEAL", "TERMINATE"]
- },
- "changeResult": {
- "description": "Signals the result of change identified by the \"changeType\" attribute. Permitted values: - COMPLETED - ROLLED_BACK - FAILED - PARTIALLY_COMPLETED\n",
- "type": "string",
- "enum": ["COMPLETED", "ROLLED_BACK", "FAILED", "PARTIALLY_COMPLETED"]
- },
- "changedInfo": {
- "description": "Information about the changed NS instance information, if applicable.\n",
- "type": "object",
- "properties": {
- "wanConnectionInfoModifications": {
- "description": "Information about the modified WAN related connectivity information, if applicable.\n",
- "type": "array",
- "items": {
- "description": "This type represents attribute modifications that were performed on WAN connection information. The attributes that can be included consist of those requested to be modified explicitly with the \"UpdateNsRequest\" data structure. It shall comply with the provisions defined in table 6.5.3.93-1.\n",
- "type": "object",
- "required": ["wanConnectionInfoId"],
- "properties": {
- "wanConnectionInfoId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
+ },
+ "removeMscsEndpointIds": {
+ "description": "If present, this attribute signals the deletion of certain entries in the \"mscsEndpoints\" attribute array in \"MscsInfo\", as defined in clause 6.5.3.82.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ },
+ "connectivityServiceEndpoints": {
+ "description": "If present, this attribute signals modifications of certain entries in the \"connectivityServiceEndpoints\" attribute array in \"WanConnectionProtocolInfo\", as defined in clause 6.5.3.91.\n",
+ "type": "array",
+ "items": {
+ "description": "This type provides configuration data for the NFVI-PoP network gateway providing connectivity service endpoints. The connectivity service endpoints are used as endpoints by an MSCS. It shall comply with the provisions defined in Table 6.5.3.84-1.\n",
+ "type": "object",
+ "required": [
+ "connectivityServiceEndpointId",
+ "vimId"
+ ],
+ "properties": {
+ "connectivityServiceEndpointId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "siteToWanLayer2ProtocolData": {
+ "description": "This type provides information about Layer 2 protocol specific information for the configuration of the NFVI-PoP network gateway to enable the stitching of the intra-site VN to the MSCS over the WAN. It shall comply with the provisions defined in Table 6.5.3.85-1. NOTE: Either \"networkResources\" or \"vnSegmentsIds\" shall be provided, but not both.\n",
+ "type": "object",
+ "required": [
+ "layer2ConnectionInfo"
+ ],
+ "properties": {
+ "layer2ConnectionInfo": {
+ "description": "Layer 2 protocol parameters of the connectivity service endpoint (CSE).\n",
+ "type": "object",
+ "required": [
+ "connectionType",
+ "interfaceType",
+ "interfaceTagging",
+ "encapsulationType"
+ ],
+ "properties": {
+ "connectionType": {
+ "description": "The type of connection to be established on the connectivity service point. Permitted values: - CSE: defined by the characteristics of the existing referred connectivity service point. - AGGREGATE_CSE: create an aggregation of the connectivity service endpoints.\n",
+ "type": "string",
+ "enum": [
+ "CSE",
+ "AGGREGATE_CSE"
+ ]
+ },
+ "interfaceType": {
+ "description": "To indicate whether to create logical interfaces on the referred connectivity service endpoint or new aggregated connectivity service endpoint. Permitted values: - PARENT: use the mapped interface to the connectivity service endpoint as is, i.e., do not create logical interfaces. - LOGICAL: create logical interfaces.\n",
+ "type": "string",
+ "enum": [
+ "PARENT",
+ "LOGICAL"
+ ]
+ },
+ "interfaceTagging": {
+ "description": "The type of frames to forward on the connectivity service point. Permitted values: - UNTAGGED: an interface where frames are not tagged. - TAGGED: an interface configured to forward tagged frames (i.e., enabled for VLAN tagging).\n",
+ "type": "string",
+ "enum": [
+ "UNTAGGED",
+ "TAGGED"
+ ]
+ },
+ "encapsulationType": {
+ "description": "The type of encapsulation. If the interfaceTagging=\"TAGGED\", either \"VLAN\" or \"VXLAN\" shall be set. Permitted values: - ETH: generic Ethernet encapsulation. - VLAN: encapsulation based on VLAN. - VXLAN: encapsulation based on VXLAN.\n",
+ "type": "string",
+ "enum": [
+ "ETH",
+ "VLAN",
+ "VXLAN"
+ ]
+ },
+ "vlanTaggingType": {
+ "description": "Type of encapsulation method for VLAN tagging. Shall be present if interfaceTagging=\"TAGGED\" and encapsulationType=\"VLAN\". Permitted values: - DOT1Q: used when packets on the CSE are encapsulated with one or a set of customer VLAN identifiers. - QINQ: used when packets on the CSE are encapsulated with multiple customer VLAN identifiers and a single\n service VLAN identifier.\n- QINANY: used when packets on the CSE have no specific customer VLAN and a service VLAN identifier is used.\n",
+ "type": "string",
+ "enum": [
+ "DOT1Q",
+ "QINQ",
+ "QINANY"
+ ]
+ },
+ "wanSegmentIds": {
+ "description": "Segment identifiers to pass on the tagged interface. Shall be present if encapsulationType=\"VLAN\" or “VXLAN\".\n",
+ "type": "object",
+ "required": [
+ "wanSegmentIdValue"
+ ],
+ "properties": {
+ "wanSegmentIdValue": {
+ "description": "Identifier of the network segment (e.g., VLAN id or VNI).\n",
+ "type": "string"
},
- "mscsName": {
- "description": "If present, this attribute signals modifications of the \"mscsName\" attribute in \"MscsInfo\" as defined in clause 6.5.3.82.\n",
- "type": "string"
+ "wanSegmentIdUpperRange": {
+ "description": "Identifier of the upper range network segment, in case the \"wanSegmentIds\" is used to define a range.\n",
+ "type": "string"
+ }
+ }
+ },
+ "vxlanConfig": {
+ "description": "Additional configuration needed when using VXLAN encapsulation. Shall be present if interfaceTagging=\"TAGGED\" and encapsulationType=\"VXLAN\".\n",
+ "type": "object",
+ "required": [
+ "peerMode"
+ ],
+ "properties": {
+ "peerMode": {
+ "description": "Type of VXLAN access mode. Default value is \"STATIC\".\nPermitted values: - STATIC - BGP_EVPN\n",
+ "type": "string",
+ "enum": [
+ "STATIC",
+ "BGP_EVPN"
+ ]
},
- "mscsDescription": {
- "description": "If present, this attribute signals modifications of the \"mscsDescription\" attribute in \"MscsInfo\" as defined in clause 6.5.3.82.\n",
+ "peers": {
+ "description": "List of IP addresses of VTEP peers when using static mode.\n",
+ "type": "array",
+ "items": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ }
+ }
+ }
+ },
+ "lagInterfaceData": {
+ "description": "Information for setting up a LAG interface aggregating multiple connectivity service endpoints.\n",
+ "type": "object",
+ "required": [
+ "aggregatedEndpoints",
+ "lacpActivation",
+ "lacpConfig"
+ ],
+ "properties": {
+ "aggregatedEndpoints": {
+ "description": "List of the connectivity service endpoints that are to be aggregated. Shall be present if connectionType=\"AGGREGATE_CSE\". In case of aggregating connectivity service endpoints, only one SiteToWanLayer2ProtocolData shall be provided for the whole set of aggregated endpoints.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
"type": "string"
+ }
},
- "mscsEndpoints": {
- "description": "If present, this attribute signals modifications of certain entries in the \"mscsEndpoints\" attribute array in \"MscsInfo\", as defined in clause 6.5.3.82.\n",
- "type": "array",
- "items": {
- "description": "This type provides encapsulates information about an MSCS endpoint of the MSCS. It shall comply with the provisions defined in table 6.5.3.83-1.\n",
- "type": "object",
- "required": ["mscsEndpointId", "directionality", "connectivityServiceEndpoinId"],
- "properties": {
- "mscsEndpointId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "directionality": {
- "description": "Directionality of the data traffic in the context of the terminating MSCS endpoint from WANs perspective. Permitted values: - INBOUND: to indicate into the WAN. - OUTBOUND: to indicate from the WAN. - BOTH: to indicate bidirectional data traffic to/from the WAN.\n",
- "type": "string",
- "enum": ["INBOUND", "OUTBOUND", "BOTH"]
- },
- "connectivityServiceEndpoinId": {
- "description": "References the connectivity service endpoint configuration information applicable to support the MSCS endpoint. More than one connectivity service endpoint can be referred when endpoints are in LAG mode.\n",
- "type": "array",
- "items": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- }
- }
- }
- }
+ "lacpActivation": {
+ "description": "Indicates whether to activate LACP on the interface. If \"TRUE\", the LACP is to be activated, or \"FALSE\" otherwise. Default value is \"FALSE\".\n",
+ "type": "boolean"
},
- "removeMscsEndpointIds": {
- "description": "If present, this attribute signals the deletion of certain entries in the \"mscsEndpoints\" attribute array in \"MscsInfo\", as defined in clause 6.5.3.82.\n",
- "type": "array",
- "items": {
- "description": "An identifier with the intention of being globally unique.\n",
+ "lacpConfig": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ },
+ "layer2ControlProtocol": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ },
+ "mtuL2": {
+ "description": "Maximum Transmission Unit (MTU) that can be forwarded at layer 2 (in bytes). Default value is \"1500\" (bytes).\n",
+ "type": "number"
+ },
+ "virtualRoutingAndForwarding": {
+ "description": "Configuration related to the L2 virtual routing and forwarding (MAC-VRF).\n",
+ "type": "object",
+ "required": [
+ "macVrfName"
+ ],
+ "properties": {
+ "macVrfName": {
+ "description": "Name (or identifier) of the MAC-VRF instance.\n",
+ "type": "string"
+ }
+ }
+ },
+ "forwardingConfig": {
+ "description": "Information related to the forwarding of the VN in the NFVI-PoP to the connectivity service endpoint, if information about the VN to \"stitch\" is already known. . by the OSS/BSS. Shall not be provided otherwise, in which case the NFVO will infer the forwarding configuration based on the NS VL, or external VL, or externally-managed VL provisioning.\n",
+ "type": "object",
+ "oneOf": [
+ {
+ "required": [
+ "networkResources"
+ ]
+ },
+ {
+ "required": [
+ "vnSegmentIds"
+ ]
+ }
+ ],
+ "properties": {
+ "networkResources": {
+ "description": "Reference to the VN resource to be forwarded into/from the MSCS. See note.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would correspond to the ‘kind’ field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the ‘claimName’ field in the Kubernetes® manifest, or a compound name built by Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the ‘metadata.name’ field in Kubernetes® manifest. \n",
+ "type": "object",
+ "required": [
+ "resourceId"
+ ],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceProviderId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "type": "string"
+ },
+ "vimLevelAdditionalResourceInfo": {
+ "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
+ "type": "object",
+ "properties": {
+ "hostName": {
+ "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note. \n",
"type": "string"
+ },
+ "persistentVolume": {
+ "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
}
+ },
+ "containerNamespace": {
+ "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise. \n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "vnSegmentIds": {
+ "description": "Identifiers of the network segments of the VN resources to be forwarded into/from the MSCS.\n",
+ "type": "object",
+ "required": [
+ "vnSegmentIdValue"
+ ],
+ "properties": {
+ "vnSegmentIdValue": {
+ "description": "Identifier of the network segment.\n",
+ "type": "string"
},
- "connectivityServiceEndpoints": {
- "description": "If present, this attribute signals modifications of certain entries in the \"connectivityServiceEndpoints\" attribute array in \"WanConnectionProtocolInfo\", as defined in clause 6.5.3.91.\n",
- "type": "array",
- "items": {
- "description": "This type provides configuration data for the NFVI-PoP network gateway providing connectivity service endpoints. The connectivity service endpoints are used as endpoints by an MSCS. It shall comply with the provisions defined in Table 6.5.3.84-1.\n",
- "type": "object",
- "required": ["connectivityServiceEndpointId", "vimId"],
- "properties": {
- "connectivityServiceEndpointId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "siteToWanLayer2ProtocolData": {
- "description": "This type provides information about Layer 2 protocol specific information for the configuration of the NFVI-PoP network gateway to enable the stitching of the intra-site VN to the MSCS over the WAN. It shall comply with the provisions defined in Table 6.5.3.85-1. NOTE: Either \"networkResources\" or \"vnSegmentsIds\" shall be provided, but not both.\n",
- "type": "object",
- "required": ["layer2ConnectionInfo"],
- "properties": {
- "layer2ConnectionInfo": {
- "description": "Layer 2 protocol parameters of the connectivity service endpoint (CSE).\n",
- "type": "object",
- "required": ["connectionType", "interfaceType", "interfaceTagging", "encapsulationType"],
- "properties": {
- "connectionType": {
- "description": "The type of connection to be established on the connectivity service point. Permitted values: - CSE: defined by the characteristics of the existing referred connectivity service point. - AGGREGATE_CSE: create an aggregation of the connectivity service endpoints.\n",
- "type": "string",
- "enum": ["CSE", "AGGREGATE_CSE"]
- },
- "interfaceType": {
- "description": "To indicate whether to create logical interfaces on the referred connectivity service endpoint or new aggregated connectivity service endpoint. Permitted values: - PARENT: use the mapped interface to the connectivity service endpoint as is, i.e., do not create logical interfaces. - LOGICAL: create logical interfaces.\n",
- "type": "string",
- "enum": ["PARENT", "LOGICAL"]
- },
- "interfaceTagging": {
- "description": "The type of frames to forward on the connectivity service point. Permitted values: - UNTAGGED: an interface where frames are not tagged. - TAGGED: an interface configured to forward tagged frames (i.e., enabled for VLAN tagging).\n",
- "type": "string",
- "enum": ["UNTAGGED", "TAGGED"]
- },
- "encapsulationType": {
- "description": "The type of encapsulation. If the interfaceTagging=\"TAGGED\", either \"VLAN\" or \"VXLAN\" shall be set. Permitted values: - ETH: generic Ethernet encapsulation. - VLAN: encapsulation based on VLAN. - VXLAN: encapsulation based on VXLAN.\n",
- "type": "string",
- "enum": ["ETH", "VLAN", "VXLAN"]
- },
- "vlanTaggingType": {
- "description": "Type of encapsulation method for VLAN tagging. Shall be present if interfaceTagging=\"TAGGED\" and encapsulationType=\"VLAN\". Permitted values: - DOT1Q: used when packets on the CSE are encapsulated with one or a set of customer VLAN identifiers. - QINQ: used when packets on the CSE are encapsulated with multiple customer VLAN identifiers and a single service VLAN identifier.\n- QINANY: used when packets on the CSE have no specific customer VLAN and a service VLAN identifier is used.\n",
- "type": "string",
- "enum": ["DOT1Q", "QINQ", "QINANY"]
- },
- "wanSegmentIds": {
- "description": "Segment identifiers to pass on the tagged interface. Shall be present if encapsulationType=\"VLAN\" or VXLAN\".\n",
- "type": "object",
- "required": ["wanSegmentIdValue"],
- "properties": {
- "wanSegmentIdValue": {
- "description": "Identifier of the network segment (e.g., VLAN id or VNI).\n",
- "type": "string"
- },
- "wanSegmentIdUpperRange": {
- "description": "Identifier of the upper range network segment, in case the \"wanSegmentIds\" is used to define a range.\n",
- "type": "string"
- }
- }
- },
- "vxlanConfig": {
- "description": "Additional configuration needed when using VXLAN encapsulation. Shall be present if interfaceTagging=\"TAGGED\" and encapsulationType=\"VXLAN\".\n",
- "type": "object",
- "required": ["peerMode"],
- "properties": {
- "peerMode": {
- "description": "Type of VXLAN access mode. Default value is \"STATIC\".\nPermitted values: - STATIC - BGP_EVPN\n",
- "type": "string",
- "enum": ["STATIC", "BGP_EVPN"]
- },
- "peers": {
- "description": "List of IP addresses of VTEP peers when using static mode.\n",
- "type": "array",
- "items": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- }
- },
- "lagInterfaceData": {
- "description": "Information for setting up a LAG interface aggregating multiple connectivity service endpoints.\n",
- "type": "object",
- "required": ["aggregatedEndpoints", "lacpActivation", "lacpConfig"],
- "properties": {
- "aggregatedEndpoints": {
- "description": "List of the connectivity service endpoints that are to be aggregated. Shall be present if connectionType=\"AGGREGATE_CSE\". In case of aggregating connectivity service endpoints, only one SiteToWanLayer2ProtocolData shall be provided for the whole set of aggregated endpoints.\n",
- "type": "array",
- "items": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- }
- },
- "lacpActivation": {
- "description": "Indicates whether to activate LACP on the interface. If \"TRUE\", the LACP is to be activated, or \"FALSE\" otherwise. Default value is \"FALSE\".\n",
- "type": "boolean"
- },
- "lacpConfig": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "layer2ControlProtocol": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "mtuL2": {
- "description": "Maximum Transmission Unit (MTU) that can be forwarded at layer 2 (in bytes). Default value is \"1500\" (bytes).\n",
- "type": "number"
- },
- "virtualRoutingAndForwarding": {
- "description": "Configuration related to the L2 virtual routing and forwarding (MAC-VRF).\n",
- "type": "object",
- "required": ["macVrfName"],
- "properties": {
- "macVrfName": {
- "description": "Name (or identifier) of the MAC-VRF instance.\n",
- "type": "string"
- }
- }
- },
- "forwardingConfig": {
- "description": "Information related to the forwarding of the VN in the NFVI-PoP to the connectivity service endpoint, if information about the VN to \"stitch\" is already known. . by the OSS/BSS. Shall not be provided otherwise, in which case the NFVO will infer the forwarding configuration based on the NS VL, or external VL, or externally-managed VL provisioning.\n",
- "type": "object",
- "oneOf": [{
- "required": ["networkResources"]
- }, {
- "required": ["vnSegmentIds"]
- }],
- "properties": {
- "networkResources": {
- "description": "Reference to the VN resource to be forwarded into/from the MSCS. See note.\n",
- "type": "array",
- "items": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes instance the vimLevelResourceType is the type of resource, as would correspond to the kind field if the resource is declared in its own Kubernetes manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the claimName field in the Kubernetes manifest, or a compound name built by Kubernetes if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the metadata.name field in Kubernetes manifest. \n",
- "type": "object",
- "required": ["resourceId"],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
- "type": "string"
- },
- "vimLevelAdditionalResourceInfo": {
- "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
- "type": "object",
- "properties": {
- "hostName": {
- "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "persistentVolume": {
- "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "containerNamespace": {
- "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
- "type": "string"
- }
- }
- }
- },
- "vnSegmentIds": {
- "description": "Identifiers of the network segments of the VN resources to be forwarded into/from the MSCS.\n",
- "type": "object",
- "required": ["vnSegmentIdValue"],
- "properties": {
- "vnSegmentIdValue": {
- "description": "Identifier of the network segment.\n",
- "type": "string"
- },
- "vnSegmentIdUpperRange": {
- "description": "Identifier of the upper range network segment, in case the \"vnSegmentIds\" is used to define a range.\n",
- "type": "string"
- }
- }
- }
- }
- }
- }
- },
- "siteToWanLayer3ProtocolData": {
- "description": "This type provides information about Layer 3 protocol specific information for the stitching of the intra-site VN to the multi-site connectivity service over the WAN. It shall comply with the provisions defined in Table 6.5.3.86-1.\n",
- "type": "object",
- "required": ["routingInfo"],
- "properties": {
- "logicalInterfaceIpAddress": {
- "description": "IP addressing information associated to a logical interface. Shall be present if the \"interfaceType\" of the SiteToWanLayer2ProtocolData is equal to \"LOGICAL\".\n",
- "type": "object",
- "required": ["ipAddress", "associatedSegmentId"],
- "properties": {
- "ipAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "associatedSegmentId": {
- "description": "The associated segment identifier that has triggered the creation of the logical interface. The value shall be one of the values listed in the \"wanSegmentIds\" of the \"siteToWanLayer2ProtocolData\".\n",
- "type": "string"
- }
- }
- },
- "routingInfo": {
- "description": "The routing information that is activated on the connectivity service endpoint. More than one \"routingInfo\" is allowed to enable stacking different routing protocols (e.g., one routing protocol for IPv4 and another one for IPv6).\n",
- "type": "object",
- "required": ["routingProtocol", "routingAddressFamily"],
- "properties": {
- "routingProtocol": {
- "description": "The routing protocol that is activated on the connectivity service endpoint. Permitted values: - BGP: used for dynamic routing BGPv4. - RIP: used for dynamic routing RIPv2. - OSPF: used for dynamic routing (OSPF version 2 for IPv4; and OSPF version 3 for IPv6). - STATIC: used for static routing. - DIRECT: used when the NFVI-PoP network is directly connected to the WAN provider network. - VRRP: used when the NFVI-PoP network is directly connected to the WAN provider network with virtual router redundancy protocol support (VRRP).\n",
- "type": "string",
- "enum": ["BGP", "RIP", "OSPF", "STATIC", "DIRECT", "VRRP"]
- },
- "staticRouting": {
- "description": "Defines a static route. It shall only be present if the routingProtocol=\"STATIC\".\n",
- "type": "object",
- "required": ["ipVersion", "ipPrefix", "prefixSize", "nextHop"],
- "properties": {
- "ipVersion": {
- "description": "The IP version applicable to the routing entry. Permitted values: - IPV4 - IPV6\n",
- "type": "string",
- "enum": ["IPV4", "IPV6"]
- },
- "ipPrefix": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "prefixSize": {
- "description": "The IP prefix size.\n",
- "type": "number"
- },
- "nextHop": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- },
- "routingAddressFamily": {
- "description": "The IP version applicable to the dynamic routing protocol. Shall be present for dynamic routing protocols. Permitted values: - IPV4 - IPV6\n",
- "type": "string",
- "enum": ["IPV4", "IPv6"]
- },
- "ospfRouting": {
- "description": "Defines parameters for OSPF routing. It shall only be present if the routingProtocol=\"OSPF\".\n",
- "type": "object",
- "required": ["areaId"],
- "properties": {
- "areaId": {
- "description": "The routing area identifier, e.g., a number or an IP address.\n",
- "type": "string"
- }
- }
- },
- "bgpRouting": {
- "description": "Defines parameters for BGP routing. It shall only be present if the routingProtocol=\"BGP\".\n",
- "type": "object",
- "required": ["bgpAs"],
- "properties": {
- "bgpAs": {
- "description": "The Autonomous System (AS) identification applicable to the BGP routing info entry.\n",
- "type": "object"
- },
- "bgpNeighbour": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "bgpAdditionalParam": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "routeMapsDistribution": {
- "description": "Maps of routes that are permitted or denied for redistribution.\n",
- "type": "object",
- "required": ["policy", "sequence", "matchAndSetRule"],
- "properties": {
- "policy": {
- "description": "The policy to apply to the route distribution.\nPermitted values: - PERMIT - DENY\n",
- "type": "string",
- "enum": ["PERMIT", "DENY"]
- },
- "sequence": {
- "description": "Sequence or index number assigned to the route-map.\n",
- "type": "number"
- },
- "matchAndSetRule": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- }
- }
- },
- "mtuL3": {
- "description": "Maximum Transmission Unit (MTU) that can be forwarded at layer 3 (in bytes). Default value is \"1500\" (bytes).\n",
- "type": "number"
- },
- "virtualRoutingAndForwarding": {
- "description": "Configuration related to the virtual routing and forwarding (VRF).\n",
- "type": "object",
- "required": ["vrfName"],
- "properties": {
- "vrfName": {
- "description": "Name (or identifier) of the VRF instance.\n",
- "type": "string"
- }
- }
- },
- "bfdConfig": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- }
- }
- }
+ "vnSegmentIdUpperRange": {
+ "description": "Identifier of the upper range network segment, in case the \"vnSegmentIds\" is used to define a range.\n",
+ "type": "string"
+ }
+ }
+ }
+ }
+ }
+ }
+ },
+ "siteToWanLayer3ProtocolData": {
+ "description": "This type provides information about Layer 3 protocol specific information for the stitching of the intra-site VN to the multi-site connectivity service over the WAN. It shall comply with the provisions defined in Table 6.5.3.86-1.\n",
+ "type": "object",
+ "required": [
+ "routingInfo"
+ ],
+ "properties": {
+ "logicalInterfaceIpAddress": {
+ "description": "IP addressing information associated to a logical interface. Shall be present if the \"interfaceType\" of the SiteToWanLayer2ProtocolData is equal to \"LOGICAL\".\n",
+ "type": "object",
+ "required": [
+ "ipAddress",
+ "associatedSegmentId"
+ ],
+ "properties": {
+ "ipAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "associatedSegmentId": {
+ "description": "The associated segment identifier that has triggered the creation of the logical interface. The value shall be one of the values listed in the \"wanSegmentIds\" of the \"siteToWanLayer2ProtocolData\".\n",
+ "type": "string"
+ }
+ }
+ },
+ "routingInfo": {
+ "description": "The routing information that is activated on the connectivity service endpoint. More than one \"routingInfo\" is allowed to enable stacking different routing protocols (e.g., one routing protocol for IPv4 and another one for IPv6).\n",
+ "type": "object",
+ "required": [
+ "routingProtocol",
+ "routingAddressFamily"
+ ],
+ "properties": {
+ "routingProtocol": {
+ "description": "The routing protocol that is activated on the connectivity service endpoint. Permitted values: - BGP: used for dynamic routing BGPv4. - RIP: used for dynamic routing RIPv2. - OSPF: used for dynamic routing (OSPF version 2 for IPv4; and OSPF version 3 for IPv6). - STATIC: used for static routing. - DIRECT: used when the NFVI-PoP network is directly connected to the WAN provider network. - VRRP: used when the NFVI-PoP network is directly connected to the WAN provider network with virtual\n router redundancy protocol support (VRRP).\n",
+ "type": "string",
+ "enum": [
+ "BGP",
+ "RIP",
+ "OSPF",
+ "STATIC",
+ "DIRECT",
+ "VRRP"
+ ]
+ },
+ "staticRouting": {
+ "description": "Defines a static route. It shall only be present if the routingProtocol=\"STATIC\".\n",
+ "type": "object",
+ "required": [
+ "ipVersion",
+ "ipPrefix",
+ "prefixSize",
+ "nextHop"
+ ],
+ "properties": {
+ "ipVersion": {
+ "description": "The IP version applicable to the routing entry. Permitted values: - IPV4 - IPV6\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
},
- "removeConnectivityServiceEndpoints": {
- "description": "If present, this attribute signals the deletion of certain entries in the \"connectivityServiceEndpoints\" attribute array in \"WanConnectionProtocolInfo\", as defined in clause 6.5.3.91.\n",
- "type": "array",
- "items": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- }
+ "ipPrefix": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "prefixSize": {
+ "description": "The IP prefix size.\n",
+ "type": "number"
+ },
+ "nextHop": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ }
+ }
+ },
+ "routingAddressFamily": {
+ "description": "The IP version applicable to the dynamic routing protocol. Shall be present for dynamic routing protocols. Permitted values: - IPV4 - IPV6\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPv6"
+ ]
+ },
+ "ospfRouting": {
+ "description": "Defines parameters for OSPF routing. It shall only be present if the routingProtocol=\"OSPF\".\n",
+ "type": "object",
+ "required": [
+ "areaId"
+ ],
+ "properties": {
+ "areaId": {
+ "description": "The routing area identifier, e.g., a number or an IP address.\n",
+ "type": "string"
}
+ }
+ },
+ "bgpRouting": {
+ "description": "Defines parameters for BGP routing. It shall only be present if the routingProtocol=\"BGP\".\n",
+ "type": "object",
+ "required": [
+ "bgpAs"
+ ],
+ "properties": {
+ "bgpAs": {
+ "description": "The Autonomous System (AS) identification applicable to the BGP routing info entry.\n",
+ "type": "object"
+ },
+ "bgpNeighbour": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "bgpAdditionalParam": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ },
+ "routeMapsDistribution": {
+ "description": "Maps of routes that are permitted or denied for redistribution.\n",
+ "type": "object",
+ "required": [
+ "policy",
+ "sequence",
+ "matchAndSetRule"
+ ],
+ "properties": {
+ "policy": {
+ "description": "The policy to apply to the route distribution.\nPermitted values: - PERMIT - DENY\n",
+ "type": "string",
+ "enum": [
+ "PERMIT",
+ "DENY"
+ ]
+ },
+ "sequence": {
+ "description": "Sequence or index number assigned to the route-map.\n",
+ "type": "number"
+ },
+ "matchAndSetRule": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ }
+ }
+ },
+ "mtuL3": {
+ "description": "Maximum Transmission Unit (MTU) that can be forwarded at layer 3 (in bytes). Default value is \"1500\" (bytes).\n",
+ "type": "number"
+ },
+ "virtualRoutingAndForwarding": {
+ "description": "Configuration related to the virtual routing and forwarding (VRF).\n",
+ "type": "object",
+ "required": [
+ "vrfName"
+ ],
+ "properties": {
+ "vrfName": {
+ "description": "Name (or identifier) of the VRF instance.\n",
+ "type": "string"
}
+ }
+ },
+ "bfdConfig": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
}
+ }
}
+ }
}
+ },
+ "removeConnectivityServiceEndpoints": {
+ "description": "If present, this attribute signals the deletion of certain entries in the \"connectivityServiceEndpoints\" attribute array in \"WanConnectionProtocolInfo\", as defined in clause 6.5.3.91.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ }
}
+ }
}
+ }
}
- },
- "affectedSap": {
- "description": "Information about the SAP instances that were affected during the lifecycle operation. See note 1.\n",
- "type": "array",
- "items": {
- "description": "This type provides information about added, deleted and modified SAP of a NS. It shall comply with the provisions in Table 6.5.3.7-1.\n",
- "type": "object",
- "required": ["sapInstanceId", "sapdId"],
- "properties": {
- "sapInstanceId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "sapdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "sapName": {
- "description": "Human readable name for the SAP.\n",
- "type": "string"
- },
- "changeType": {
- "description": "Signals the type of lifecycle change. Permitted values: - ADD - REMOVE - MODIFY\n",
- "type": "string",
- "enum": ["ADD", "REMOVE", "MODIFY"]
- },
- "changeResult": {
- "description": "Signals the result of change identified by the \"changeType\" attribute. Permitted values: - COMPLETED - ROLLED_BACK - FAILED\n",
- "type": "string",
- "enum": ["COMPLETED", "ROLLED_BACK", "FAILED"]
- }
- }
+ }
+ }
+ },
+ "affectedSap": {
+ "description": "Information about the SAP instances that were affected during the lifecycle operation. See note 1.\n",
+ "type": "array",
+ "items": {
+ "description": "This type provides information about added, deleted and modified SAP of a NS. It shall comply with the provisions in Table 6.5.3.7-1.\n",
+ "type": "object",
+ "required": [
+ "sapInstanceId",
+ "sapdId"
+ ],
+ "properties": {
+ "sapInstanceId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "sapdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "sapName": {
+ "description": "Human readable name for the SAP.\n",
+ "type": "string"
+ },
+ "changeType": {
+ "description": "Signals the type of lifecycle change. Permitted values: - ADD - REMOVE - MODIFY\n",
+ "type": "string",
+ "enum": [
+ "ADD",
+ "REMOVE",
+ "MODIFY"
+ ]
+ },
+ "changeResult": {
+ "description": "Signals the result of change identified by the \"changeType\" attribute. Permitted values: - COMPLETED - ROLLED_BACK - FAILED\n",
+ "type": "string",
+ "enum": [
+ "COMPLETED",
+ "ROLLED_BACK",
+ "FAILED"
+ ]
}
- },
- "feasibilityCheckResult": {
- "description": "The enumeration FeasibilityCheckResultType defines the permitted values to represent the result of executing a feasibility check according to the options defined in clause 6.5.4.14. It shall comply with the provisions defined in table 6.5.4.15-1.\n",
+ }
+ }
+ },
+ "feasibilityCheckResult": {
+ "description": "The enumeration FeasibilityCheckResultType defines the permitted values to represent the result of executing a feasibility check according to the options defined in clause 6.5.4.14. It shall comply with the provisions defined in table 6.5.4.15-1.\n",
+ "type": "string",
+ "enum": [
+ "FEASIBILITY_CHECK_DONE",
+ "FEASIBILITY_CHECK_DONE_WITH_RESERVATION"
+ ]
+ },
+ "error": {
+ "description": "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 [19] is reproduced in this structure. Compared to the general framework defined in IETF RFC 7807 [19], the \"status\" and \"detail\" attributes are mandated to be included by the present document, to ensure that the response contains additional textual information about an error. IETF RFC 7807 [19] foresees extensibility of the \"ProblemDetails\" type. It is possible that particular APIs in the present document, or particular implementations, define extensions to define additional attributes that provide more information about the error. The description column only provides some explanation of the meaning to Facilitate understanding of the design. For a full description, see IETF RFC 7807 [19].\n",
+ "type": "object",
+ "required": [
+ "status",
+ "detail"
+ ],
+ "properties": {
+ "type": {
+ "description": "A URI reference according to IETF RFC 3986 [5] that identifies the problem type. It is encouraged that the URI provides human-readable documentation for the problem (e.g. using HTML) when dereferenced. When this member is not present, its value is assumed to be \"about:blank\".\n",
+ "type": "string",
+ "format": "URI"
+ },
+ "title": {
+ "description": "A short, human-readable summary of the problem type. It should not change from occurrence to occurrence of the problem, except for purposes of localization. If type is given and other than \"about:blank\", this attribute shall also be provided. A short, human-readable summary of the problem type. It SHOULD NOT change from occurrence to occurrence of the problem, except for purposes of localization (e.g., using proactive content negotiation; see [RFC7231], Section 3.4).\n",
+ "type": "string"
+ },
+ "status": {
+ "description": "The HTTP status code for this occurrence of the problem. The HTTP status code ([RFC7231], Section 6) generated by the origin server for this occurrence of the problem.\n",
+ "type": "integer"
+ },
+ "detail": {
+ "description": "A human-readable explanation specific to this occurrence of the problem.\n",
+ "type": "string"
+ },
+ "instance": {
+ "description": "A URI reference that identifies the specific occurrence of the problem. It may yield further information if dereferenced.\n",
"type": "string",
- "enum": ["FEASIBILITY_CHECK_DONE", "FEASIBILITY_CHECK_DONE_WITH_RESERVATION"]
- },
- "error": {
- "description": "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 [19] is reproduced in this structure. Compared to the general framework defined in IETF RFC 7807 [19], the \"status\" and \"detail\" attributes are mandated to be included by the present document, to ensure that the response contains additional textual information about an error. IETF RFC 7807 [19] foresees extensibility of the \"ProblemDetails\" type. It is possible that particular APIs in the present document, or particular implementations, define extensions to define additional attributes that provide more information about the error. The description column only provides some explanation of the meaning to Facilitate understanding of the design. For a full description, see IETF RFC 7807 [19].\n",
+ "format": "URI"
+ }
+ }
+ },
+ "_links": {
+ "type": "object",
+ "required": [
+ "nsInstance"
+ ],
+ "properties": {
+ "nsInstance": {
+ "description": "This type represents a link to a resource in a notification, using an absolute or relative URI.\n",
"type": "object",
- "required": ["status", "detail"],
+ "required": [
+ "href"
+ ],
"properties": {
- "type": {
- "description": "A URI reference according to IETF RFC 3986 [5] that identifies the problem type. It is encouraged that the URI provides human-readable documentation for the problem (e.g. using HTML) when dereferenced. When this member is not present, its value is assumed to be \"about:blank\".\n",
- "type": "string",
- "format": "URI"
- },
- "title": {
- "description": "A short, human-readable summary of the problem type. It should not change from occurrence to occurrence of the problem, except for purposes of localization. If type is given and other than \"about:blank\", this attribute shall also be provided. A short, human-readable summary of the problem type. It SHOULD NOT change from occurrence to occurrence of the problem, except for purposes of localization (e.g., using proactive content negotiation; see [RFC7231], Section 3.4).\n",
- "type": "string"
- },
- "status": {
- "description": "The HTTP status code for this occurrence of the problem. The HTTP status code ([RFC7231], Section 6) generated by the origin server for this occurrence of the problem.\n",
- "type": "integer"
- },
- "detail": {
- "description": "A human-readable explanation specific to this occurrence of the problem.\n",
- "type": "string"
- },
- "instance": {
- "description": "A URI reference that identifies the specific occurrence of the problem. It may yield further information if dereferenced.\n",
- "type": "string",
- "format": "URI"
- }
+ "href": {
+ "description": "URI of a resource referenced from a notification. Should be an absolute URI (i.e. a URI that contains {apiRoot}), however, may be a relative URI (i.e. a URI where the {apiRoot} part is omitted) if the {apiRoot} information is not available.\n",
+ "type": "string",
+ "format": "url"
+ }
}
- },
- "_links": {
+ },
+ "subscription": {
+ "description": "This type represents a link to a resource in a notification, using an absolute or relative URI.\n",
"type": "object",
- "required": ["nsInstance"],
+ "required": [
+ "href"
+ ],
"properties": {
- "nsInstance": {
- "description": "This type represents a link to a resource in a notification, using an absolute or relative URI.\n",
- "type": "object",
- "required": ["href"],
- "properties": {
- "href": {
- "description": "URI of a resource referenced from a notification. Should be an absolute URI (i.e. a URI that contains {apiRoot}), however, may be a relative URI (i.e. a URI where the {apiRoot} part is omitted) if the {apiRoot} information is not available.\n",
- "type": "string",
- "format": "url"
- }
- }
- },
- "subscription": {
- "description": "This type represents a link to a resource in a notification, using an absolute or relative URI.\n",
- "type": "object",
- "required": ["href"],
- "properties": {
- "href": {
- "description": "URI of a resource referenced from a notification. Should be an absolute URI (i.e. a URI that contains {apiRoot}), however, may be a relative URI (i.e. a URI where the {apiRoot} part is omitted) if the {apiRoot} information is not available.\n",
- "type": "string",
- "format": "url"
- }
- }
- },
- "nslcmOpOcc": {
- "description": "This type represents a link to a resource in a notification, using an absolute or relative URI.\n",
- "type": "object",
- "required": ["href"],
- "properties": {
- "href": {
- "description": "URI of a resource referenced from a notification. Should be an absolute URI (i.e. a URI that contains {apiRoot}), however, may be a relative URI (i.e. a URI where the {apiRoot} part is omitted) if the {apiRoot} information is not available.\n",
- "type": "string",
- "format": "url"
- }
- }
- }
+ "href": {
+ "description": "URI of a resource referenced from a notification. Should be an absolute URI (i.e. a URI that contains {apiRoot}), however, may be a relative URI (i.e. a URI where the {apiRoot} part is omitted) if the {apiRoot} information is not available.\n",
+ "type": "string",
+ "format": "url"
+ }
+ }
+ },
+ "nslcmOpOcc": {
+ "description": "This type represents a link to a resource in a notification, using an absolute or relative URI.\n",
+ "type": "object",
+ "required": [
+ "href"
+ ],
+ "properties": {
+ "href": {
+ "description": "URI of a resource referenced from a notification. Should be an absolute URI (i.e. a URI that contains {apiRoot}), however, may be a relative URI (i.e. a URI where the {apiRoot} part is omitted) if the {apiRoot} information is not available.\n",
+ "type": "string",
+ "format": "url"
+ }
}
+ }
}
+ }
}
-}
\ No newline at end of file
+ }
\ No newline at end of file
diff --git a/SOL005/NSLifecycleManagement-API/schemas/VnfSnapshotInfo.schema.json b/SOL005/NSLifecycleManagement-API/schemas/VnfSnapshotInfo.schema.json
index b10ddb60c02f5d91f8c8ad05d6eb4f7391bd0a9b..47277802a70af5fd188d2bec99209300d26c7885 100644
--- a/SOL005/NSLifecycleManagement-API/schemas/VnfSnapshotInfo.schema.json
+++ b/SOL005/NSLifecycleManagement-API/schemas/VnfSnapshotInfo.schema.json
@@ -1,2247 +1,2642 @@
{
"description": "This type represents an \"Individual VNF snapshot\" resource. The \"id\" attributed is used by the NFVO to index and\nidentify the VNF snapshots information resources that are accessible via the NFVO. The identifier is still\ngenerated by the VNFM and copied into the present \"VnfSnapshotInfo\" representing the \"Individual VNF snapshot\"\nresource hold by the NFVO.\n",
"type": "object",
- "required": ["id"],
+ "required": [
+ "id"
+ ],
"properties": {
- "id": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfSnapshotPkgId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfSnapshot": {
+ "description": "This type represents a VNF Snapshot. It shall comply with the provisions defined in table 6.5.2.18-1.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "vnfInstanceId",
+ "triggeredAt",
+ "createdAt",
+ "vnfdId",
+ "vnfInstance",
+ "vnfcSnapshots"
+ ],
+ "properties": {
+ "id": {
"description": "An identifier with the intention of being globally unique.\n",
"type": "string"
- },
- "vnfSnapshotPkgId": {
+ },
+ "vnfInstanceId": {
"description": "An identifier with the intention of being globally unique.\n",
"type": "string"
- },
- "vnfSnapshot": {
- "description": "This type represents a VNF Snapshot. It shall comply with the provisions defined in table 6.5.2.18-1.\n",
+ },
+ "creationStartedAt": {
+ "description": "Date-time stamp. Representation: String formatted according toas defined by the date-time production in IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "creationFinishedAt": {
+ "description": "Date-time stamp. Representation: String formatted according toas defined by the date-time production in IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfInstance": {
+ "description": "This type represents a VNF instance. It shall comply with the provisions defined in table 6.5.3.57-1.\nNOTE: Clause B.3.2 of ETSI GS NFV-SOL 003 provides examples illustrating the relationship among the \n different run-time data types (CP, VL and link ports) used to represent the connectivity \n of a VNF.\n\nNOTE 1: Modifying the value of this attribute shall not be performed when conflicts exist between the \n previous and the newly referred VNF package, i.e. when the new VNFD is changed with respect to \n the previous VNFD in other aspects than merely referencing to other VNF software images. \n In order to avoid misalignment of the VnfInstance with the current VNF's on-boarded VNF Package, \n the values of attributes in the VnfInstance that have corresponding attributes in the VNFD shall \n be kept in sync with the values in the VNFD.\nNOTE 2: ETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on TOSCA specifications. NOTE 3: VNF configurable properties are sometimes also referred to as configuration parameters applicable \n to a VNF. Some of these are set prior to instantiation and cannot be modified if the VNF is instantiated, \n some are set prior to instantiation (are part of initial configuration) and can be modified later, \n and others can be set only after instantiation. The applicability of certain configuration may depend \n on the VNF and the required operation of the VNF at a certain point in time.\nNOTE 4: It is possible to have several ExtManagedVirtualLinkInfo for the same VNF internal VL in case of a \n multi-site VNF spanning several VIMs. The set of ExtManagedVirtualLinkInfo corresponding to the same \n VNF internal VL shall indicate so by referencing to the same VnfVirtualLinkDesc and externally-managed \n multi-site VL instance (refer to clause 6.5.3.59).\nNOTE 5: Even though externally-managed internal VLs are also used for VNF-internal connectivity, they shall not \n be listed in the \"vnfVirtualLinkResourceInfo\" attribute as this would be redundant.\n",
"type": "object",
- "required": ["id", "vnfInstanceId", "triggeredAt", "createdAt", "vnfdId", "vnfInstance", "vnfcSnapshots"],
+ "required": [
+ "id",
+ "vnfdId",
+ "vnfProvider",
+ "vnfProductName",
+ "vnfSoftwareVersion",
+ "vnfdVersion",
+ "vnfPkgId",
+ "instantiationState"
+ ],
"properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfInstanceId": {
- "description": "An identifier with the intention of being globally unique.\n",
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfInstanceName": {
+ "description": "Name of the VNF instance. Modifications to this attribute can be requested using the \"ModifyVnfInfoData\" structure.\n",
+ "type": "string"
+ },
+ "vnfInstanceDescription": {
+ "description": "Human-readable description of the VNF instance. Modifications to this attribute can be requested using the \"ModifyVnfInfoData\" structure.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfProvider": {
+ "description": "Provider of the VNF and the VNFD. The value is copied from the VNFD.\n",
+ "type": "string"
+ },
+ "vnfProductName": {
+ "description": "Name to identify the VNF Product. The value is copied from the VNFD.\n",
+ "type": "string"
+ },
+ "vnfSoftwareVersion": {
+ "description": "A Version. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vnfdVersion": {
+ "description": "A Version. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "versionDependency": {
+ "description": "Describes version dependencies currently valid for the VNF instance. Identifies versions of descriptors of other constituents in the NSD upon which the VNF depends. The dependencies may be described for the VNFD referenced in this VnfInfo with \"vnfdId\" and for VNFDs with the same \"vnfdExtInvariantId\". There shall not be more than one \"versionDependency\" present with the same dependentConstituentId.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the information related to all dependencies that an NSD constituent has on the versions of other NSD constituents. It shall comply with the provisions defined in table 6.5.3.112-1.\n",
+ "type": "object",
+ "required": [
+ "dependentConstituentId"
+ ],
+ "properties": {
+ "dependentConstituentId": {
+ "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "versionDependencyStatement": {
+ "description": "Identifies one or multiple versions of an NSD constituents upon which the dependent constituent identified by dependentConstituentId has a dependency. Cardinality 0 is used to remove an existing version dependency in a profile.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the information related to one or more VNF, NS or PNF descriptor identifiers which describe one single dependency. When more than one descriptor is indicated, they correspond to different versions of the same VNF, NS or PNF and they represent alternatives to fulfil the dependency. It shall comply with the provisions defined in table 6.5.3.113-1.\n",
+ "type": "object",
+ "required": [
+ "descriptorId"
+ ],
+ "properties": {
+ "descriptorId": {
+ "description": "Identifies a VNFD, NSD or PNFD upon which the entity using this data type depends. When more than one descriptor is indicated, they shall correspond to versions of the same VNF, NS or PNF and they represent alternatives, i.e. the presence of one of them fulfills the dependency.",
+ "type": "array",
+ "items": {
+ "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
+ "type": "string"
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ },
+ "vnfPkgId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfConfigurableProperties": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ },
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "instantiationState": {
+ "description": "The instantiation state of the VNF.\nPermitted values: - NOT_INSTANTIATED: The VNF instance is terminated or not instantiated. - INSTANTIATED: The VNF instance is instantiated.\n",
+ "type": "string",
+ "enum": [
+ "NOT_INSTANTIATED",
+ "INSTANTIATED"
+ ]
+ },
+ "instantiatedVnfInfo": {
+ "description": "Information specific to an instantiated VNF instance. This attribute shall be present if the instantiateState attribute value is INSTANTIATED.\n",
+ "type": "object",
+ "required": [
+ "flavourId",
+ "vnfState",
+ "extCpInfo"
+ ],
+ "properties": {
+ "flavourId": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
"type": "string"
- },
- "creationStartedAt": {
- "description": "Date-time stamp. Representation: String formatted according toas defined by the date-time production in IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "creationFinishedAt": {
- "description": "Date-time stamp. Representation: String formatted according toas defined by the date-time production in IETF RFC 3339.\n",
+ },
+ "vnfState": {
"type": "string",
- "format": "date-time"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfInstance": {
- "description": "This type represents a VNF instance. It shall comply with the provisions defined in table 6.5.3.57-1.\nNOTE: Clause B.3.2 of ETSI GS NFV-SOL 003 provides examples illustrating the relationship among the different run-time information elements (CP, VL and link ports) used to represent the connectivity \n of a VNF.\n\nNOTE 1: 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 changed with respect to \n the previous VNFD in other aspects than merely referencing to other VNF software images. \n In order to avoid misalignment of the VnfInstance with the current VNF's on-boarded VNF Package, \n the values of attributes in the VnfInstance that have corresponding attributes in the VNFD shall \n be kept in sync with the values in the VNFD.\nNOTE 2: ETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on TOSCA specifications. NOTE 3: VNF configurable properties are sometimes also referred to as configuration parameters applicable to a VNF. Some of these are set prior to instantiation and cannot be modified if the VNF is instantiated, \n some are set prior to instantiation (are part of initial configuration) and can be modified later, \n and others can be set only after instantiation. The applicability of certain configuration may depend \n on the VNF and the required operation of the VNF at a certain point in time.\nNOTE 4: It is possible to have several ExtManagedVirtualLinkInfo for the same VNF internal VL in case of a multi-site VNF spanning several VIMs. The set of ExtManagedVirtualLinkInfo corresponding to the same \n VNF internal VL shall indicate so by referencing to the same VnfVirtualLinkDesc and externally-managed \n multi-site VL instance (refer to clause 6.5.3.59).\nNOTE 5: Even though externally-managed internal VLs are also used for VNF-internal connectivity, they shall not be listed in the \"vnfVirtualLinkResourceInfo\" attribute as this would be redundant.\n",
- "type": "object",
- "required": ["id", "vnfdId", "vnfProvider", "vnfProductName", "vnfSoftwareVersion", "vnfdVersion", "vnfPkgId", "instantiationState"],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
+ "enum": [
+ "STARTED",
+ "STOPPED"
+ ]
+ },
+ "scaleStatus": {
+ "description": "Scale status of the VNF, one entry per aspect. Represents for every scaling aspect how \"big\" the VNF has been scaled w.r.t. that aspect.\n",
+ "type": "array",
+ "items": {
+ "required": [
+ "aspectId",
+ "scaleLevel"
+ ],
+ "type": "object",
+ "properties": {
+ "aspectId": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
+ "type": "string"
},
- "vnfInstanceName": {
- "description": "Name of the VNF instance. Modifications to this attribute can be requested using the \"ModifyVnfInfoData\" structure.\n",
- "type": "string"
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
},
- "vnfInstanceDescription": {
- "description": "Human-readable description of the VNF instance. Modifications to this attribute can be requested using the \"ModifyVnfInfoData\" structure.\n",
- "type": "string"
+ "scaleLevel": {
+ "description": "Indicates the scale level. The minimum value shall be 0 and the maximum value shall be <= maxScaleLevel as described in the VNFD.\n",
+ "type": "integer"
+ }
+ }
+ }
+ },
+ "maxScaleLevels": {
+ "description": "Maximum allowed scale levels of the VNF, one entry per aspect. This attribute shall be present if the VNF supports scaling.\n",
+ "type": "array",
+ "items": {
+ "required": [
+ "aspectId",
+ "scaleLevel"
+ ],
+ "type": "object",
+ "properties": {
+ "aspectId": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
+ "type": "string"
},
"vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
},
- "vnfProvider": {
- "description": "Provider of the VNF and the VNFD. The value is copied from the VNFD.\n",
- "type": "string"
+ "scaleLevel": {
+ "description": "Indicates the scale level. The minimum value shall be 0 and the maximum value shall be <= maxScaleLevel as described in the VNFD.\n",
+ "type": "integer"
+ }
+ }
+ }
+ },
+ "extCpInfo": {
+ "description": "Information about the external CPs exposed by the VNF instance. When trunking is enabled, the list of entries includes both, external CPs corresponding to parent ports of a trunk, and external CPs associated to sub-ports of a trunk.\n",
+ "type": "array",
+ "minItems": 1,
+ "items": {
+ "description": "This type represents information about an external CP of a VNF. It shall comply with the provisions defined in Table 6.5.3.70-1. NOTE 1: The attributes attributes \"associatedVnfcCpId\", \"associatedVipCpId\", \"associatedVirtualCpId\" and \"associatedVnfVirtualLinkId\" are mutually exclusive. Exactly one shall be present. NOTE 2: An external CP instance is not associated to a link port in the cases indicated for the “extLinkPorts” attribute in clause 6.5.3.26. NOTE 3: Cardinality greater than 1 is only applicable for specific cases where more than one network attachment definition resource is needed to fulfil the connectivity requirements of the external CP, e.g. to build a link redundant mated pair in SR-IOV cases. NOTE 4: When more than one \"netAttDefResourceId\" is indicated, all shall belong to the same namespace.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "cpdId",
+ "cpProtocolInfo"
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "associatedVnfcCpId"
+ ]
},
- "vnfProductName": {
- "description": "Name to identify the VNF Product. The value is copied from the VNFD.\n",
- "type": "string"
+ {
+ "required": [
+ "associatedVipCpId"
+ ]
},
- "vnfSoftwareVersion": {
- "description": "A Version. Representation: string of variable length.\n",
- "type": "string"
+ {
+ "required": [
+ "associatedVirtualCpId"
+ ]
},
- "vnfdVersion": {
- "description": "A Version. Representation: string of variable length.\n",
- "type": "string"
+ {
+ "required": [
+ "associatedVnfVirtualLinkId"
+ ]
+ }
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
},
- "versionDependency": {
- "description": "Describes version dependencies currently valid for the VNF instance. Identifies versions of descriptors of other constituents in the NSD upon which the VNF depends. The dependencies may be described for the VNFD referenced in this VnfInfo with vnfdId and for VNFDs with the same VnfdExtInvariantId. There shall not be more than one versionDependency present with the same dependentConstituentId.\n",
- "type": "array",
- "items": {
- "description": "This type represents the information related to all dependencies that an NSD constituent has on the versions of other NSD constituents. It shall comply with the provisions defined in table 6.5.3.112-1.\n",
+ "cpdId": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
+ "type": "string"
+ },
+ "cpConfigId": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "cpProtocolInfo": {
+ "description": "Network protocol information for this CP.\n",
+ "type": "array",
+ "minItems": 1,
+ "items": {
+ "description": "This type describes the protocol layer(s) that a CP or SAP uses together with protocol-related information, like addresses. It shall comply with the provisions defined in Table 6.5.3.58-1. NOTE: This attribute allows to signal the addition of further types of layer and protocol in future versions of the present document in a backwards-compatible way. In the current version of the present document, only IP over Ethernet is supported.\n",
+ "type": "object",
+ "required": [
+ "layerProtocol",
+ "ipOverEthernet"
+ ],
+ "properties": {
+ "layerProtocol": {
+ "description": "The identifier of layer(s) and protocol(s) associated to the network address information. Permitted values:\n - IP_OVER_ETHERNET\n - IP_FOR_VIRTUAL_CP\nSee note.\n",
+ "type": "string",
+ "enum": [
+ "IP_OVER_ETHERNET",
+ "IP_FOR_VIRTUAL_CP"
+ ]
+ },
+ "ipOverEthernet": {
+ "description": "This type represents information about a network address that has been assigned.\nNOTE 1: At least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2: Exactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3: If the Cp instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4: Depending on the NFVI networking infrastructure, the \"segmentationId\" may indicate the actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header of the packets or it may be an identifier used between the application and the NFVI networking infrastructure to identify the network sub-interface of the trunk port in question. In the latter case the NFVI infrastructure will map this local \"segmentationId\" to whatever \"segmentationId\" is actually used by the NFVI's transport technology.\n",
"type": "object",
- "required": ["dependentConstituentId"],
+ "anyOf": [
+ {
+ "required": [
+ "macAddress"
+ ]
+ },
+ {
+ "required": [
+ "ipAddresses"
+ ]
+ }
+ ],
"properties": {
- "dependentConstituentId": {
- "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
- "type": "string"
- },
- "versionDependencyStatement": {
- "description": "Identifies one or multiple versions of an NSD constituents upon which the dependent constituent identified by dependentConstituentId has a dependency. Cardinality 0 is used to remove an existing version dependency in a profile.\n",
- "type": "array",
- "items": {
- "description": "This type represents the information related to one or more VNF, NS or PNF descriptor identifiers which describe one single dependency. When more than one descriptor is indicated, they correspond to different versions of the same VNF, NS or PNF and they represent alternatives to fulfil the dependency. It shall comply with the provisions defined in table 6.5.3.113-1.\n",
- "type": "object",
- "required": ["descriptorId"],
- "properties": {
- "descriptorId": {
- "description": "Identifies a VNFD, NSD or PNFD upon which the entity using this information element depends. When more than one descriptor is indicated, they shall correspond to versions of the same VNF, NS or PNF and they represent. alternatives, i.e. the presence of one of them fulfills the dependency.",
- "type": "array",
- "items": {
- "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
- "type": "string"
- }
- }
+ "macAddress": {
+ "description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
+ "type": "string",
+ "format": "MAC"
+ },
+ "segmentationId": {
+ "description": "Identification of the network segment to which the Cp instance connects to. See note 3 and note 4.\n",
+ "type": "string"
+ },
+ "ipAddresses": {
+ "description": "Addresses assigned to the CP instance. Each entry represents IP addresses assigned by fixed or dynamic IP address assignment per subnet. See note 1.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": [
+ "type"
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "addresses"
+ ]
+ },
+ {
+ "required": [
+ "addressRange"
+ ]
+ }
+ ],
+ "properties": {
+ "type": {
+ "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
+ },
+ "addresses": {
+ "description": "Fixed addresses assigned (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
+ "type": "array",
+ "items": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ }
+ },
+ "isDynamic": {
+ "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
+ "type": "boolean"
+ },
+ "addressRange": {
+ "description": "An IP address range used, e.g., in case of egress connections. Exactly one of \"addresses\" or \"addressRange\" shall be present. See note 2.\n",
+ "type": "object",
+ "required": [
+ "minAddress",
+ "maxAddress"
+ ],
+ "properties": {
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
}
+ }
+ },
+ "subnetId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
}
+ }
+ }
+ },
+ "type": {
+ "description": "The type of the IP addresses\n",
+ "type": "string",
+ "enum": [
+ "PV4",
+ "PV6"
+ ]
+ },
+ "addresses": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "isDynamic": {
+ "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
+ "type": "boolean"
+ },
+ "addressRange": {
+ "description": "An IP address range used, e.g. in case of egress connections. See note.\n",
+ "type": "object",
+ "required": [
+ "minAddress",
+ "maxAddress"
+ ],
+ "properties": {
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ }
}
+ },
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "subnetId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ }
+ }
+ },
+ "virtualCpAddress": {
+ "description": "This type represents information about a network address that has been assigned to a virtual CP.\n",
+ "type": "object",
+ "required": [
+ "type"
+ ],
+ "properties": {
+ "type": {
+ "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
+ },
+ "loadBalancerIp": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.",
+ "type": "string"
+ }
}
+ }
}
+ }
},
- "vnfPkgId": {
- "description": "An identifier with the intention of being globally unique.\n",
+ "extLinkPortId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "netAttDefResourceId": {
+ "description": "Identifier of the \"NetAttDefResourceInfo\" structure that provides the specification of the interface to attach the connection point to a secondary container cluster network. See notes 3 and 4.\nIt shall be present if the external CP is associated to a VNFC realized by one or a set of OS containers and is connected to a secondary container cluster network. It shall not be present otherwise.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
"type": "string"
+ }
},
- "vnfConfigurableProperties": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
+ "metadata": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
},
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
+ "associatedVnfcCpId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "associatedVipCpId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
},
- "instantiationState": {
- "description": "The instantiation state of the VNF.\nPermitted values: - NOT_INSTANTIATED: The VNF instance is terminated or not instantiated. - INSTANTIATED: The VNF instance is instantiated.\n",
- "type": "string",
- "enum": ["NOT_INSTANTIATED", "INSTANTIATED"]
+ "associatedVirtualCpId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
},
- "instantiatedVnfInfo": {
- "description": "Information specific to an instantiated VNF instance. This attribute shall be present if the instantiateState attribute value is INSTANTIATED.\n",
+ "associatedVnfVirtualLinkId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "vipCpInfo": {
+ "description": "VIP CPs that are part of the VNF instance. Shall be present when that particular VIP CP of the VNFC instance is associated to an external CP of the VNF instance. May be present otherwise.\n",
+ "type": "array",
+ "items": {
+ "description": "This type provides information related to virtual IP (VIP) CP. It shall comply with the provisions defined in table 6.5.3.97 1. NOTE: It is possible that there is no associated VnfcCp because the VIP CP is available but not associated yet.\n",
+ "type": "object",
+ "required": [
+ "cpInstanceId",
+ "cpdId"
+ ],
+ "properties": {
+ "cpInstanceId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "cpdId": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfExtCpId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "cpProtocolInfo": {
+ "description": "Protocol information for this CP. There shall be one cpProtocolInfo for layer 3. There may be one cpProtocolInfo for layer 2.\n",
+ "type": "array",
+ "items": {
+ "description": "This type describes the protocol layer(s) that a CP or SAP uses together with protocol-related information, like addresses. It shall comply with the provisions defined in Table 6.5.3.58-1. NOTE: This attribute allows to signal the addition of further types of layer and protocol in future versions of the present document in a backwards-compatible way. In the current version of the present document, only IP over Ethernet is supported.\n",
"type": "object",
- "required": ["flavourId", "vnfState", "extCpInfo"],
+ "required": [
+ "layerProtocol",
+ "ipOverEthernet"
+ ],
"properties": {
- "flavourId": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "vnfState": {
+ "layerProtocol": {
+ "description": "The identifier of layer(s) and protocol(s) associated to the network address information. Permitted values:\n - IP_OVER_ETHERNET\n - IP_FOR_VIRTUAL_CP\nSee note.\n",
+ "type": "string",
+ "enum": [
+ "IP_OVER_ETHERNET",
+ "IP_FOR_VIRTUAL_CP"
+ ]
+ },
+ "ipOverEthernet": {
+ "description": "This type represents information about a network address that has been assigned.\nNOTE 1: At least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2: Exactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3: If the Cp instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4: Depending on the NFVI networking infrastructure, the \"segmentationId\" may indicate the actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header of the packets or it may be an identifier used between the application and the NFVI networking infrastructure to identify the network sub-interface of the trunk port in question. In the latter case the NFVI infrastructure will map this local \"segmentationId\" to whatever \"segmentationId\" is actually used by the NFVI's transport technology.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "required": [
+ "macAddress"
+ ]
+ },
+ {
+ "required": [
+ "ipAddresses"
+ ]
+ }
+ ],
+ "properties": {
+ "macAddress": {
+ "description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
"type": "string",
- "enum": ["STARTED", "STOPPED"]
- },
- "scaleStatus": {
- "description": "Scale status of the VNF, one entry per aspect. Represents for every scaling aspect how \"big\" the VNF has been scaled w.r.t. that aspect.\n",
+ "format": "MAC"
+ },
+ "segmentationId": {
+ "description": "Identification of the network segment to which the Cp instance connects to. See note 3 and note 4.\n",
+ "type": "string"
+ },
+ "ipAddresses": {
+ "description": "Addresses assigned to the CP instance. Each entry represents IP addresses assigned by fixed or dynamic IP address assignment per subnet. See note 1.\n",
"type": "array",
"items": {
- "required": ["aspectId", "scaleLevel"],
- "type": "object",
- "properties": {
- "aspectId": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "scaleLevel": {
- "description": "Indicates the scale level. The minimum value shall be 0 and the maximum value shall be <= maxScaleLevel as described in the VNFD.\n",
- "type": "integer"
- }
+ "type": "object",
+ "required": [
+ "type"
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "addresses"
+ ]
+ },
+ {
+ "required": [
+ "addressRange"
+ ]
}
- }
- },
- "maxScaleLevels": {
- "description": "Maximum allowed scale levels of the VNF, one entry per aspect. This attribute shall be present if the VNF supports scaling.\n",
- "type": "array",
- "items": {
- "required": ["aspectId", "scaleLevel"],
- "type": "object",
- "properties": {
- "aspectId": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "scaleLevel": {
- "description": "Indicates the scale level. The minimum value shall be 0 and the maximum value shall be <= maxScaleLevel as described in the VNFD.\n",
- "type": "integer"
+ ],
+ "properties": {
+ "type": {
+ "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
+ },
+ "addresses": {
+ "description": "Fixed addresses assigned (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
+ "type": "array",
+ "items": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ }
+ },
+ "isDynamic": {
+ "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
+ "type": "boolean"
+ },
+ "addressRange": {
+ "description": "An IP address range used, e.g., in case of egress connections. Exactly one of \"addresses\" or \"addressRange\" shall be present. See note 2.\n",
+ "type": "object",
+ "required": [
+ "minAddress",
+ "maxAddress"
+ ],
+ "properties": {
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
}
+ }
+ },
+ "subnetId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
}
+ }
}
- },
- "extCpInfo": {
- "description": "Information about the external CPs exposed by the VNF instance. When trunking is enabled, the list of entries includes both, external CPs corresponding to parent ports of a trunk, and external CPs associated to sub-ports of a trunk.\n",
- "type": "array",
- "minItems": 1,
- "items": {
- "description": "This type represents information about an external CP of a VNF. It shall comply with the provisions defined in Table 6.5.3.70-1. NOTE 1: The attributes attributes \"associatedVnfcCpId\", \"associatedVipCpId\", \"associatedVirtualCpId\" and \"associatedVnfVirtualLinkId\" are mutually exclusive. Exactly one shall be present. NOTE 2: An external CP instance is not associated to a link port in the cases indicated for the extLinkPorts attribute in clause 6.5.3.26. NOTE 3: Cardinality greater than 1 is only applicable for specific cases where more than one network attachment definition resource is needed to fulfil the connectivity requirements of the external CP, e.g. to build a link redundant mated pair in SR-IOV cases. NOTE 4: When more than one \"netAttDefResourceId\" is indicated, all shall belong to the same namespace.\n",
- "type": "object",
- "required": ["id", "cpdId", "cpProtocolInfo"],
- "oneOf": [{
- "required": ["associatedVnfcCpId"]
- }, {
- "required": ["associatedVipCpId"]
- }, {
- "required": ["associatedVirtualCpId"]
- }, {
- "required": ["associatedVnfVirtualLinkId"]
- }],
- "properties": {
- "id": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "cpdId": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "cpConfigId": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "cpProtocolInfo": {
- "description": "Network protocol information for this CP.\n",
- "type": "array",
- "minItems": 1,
- "items": {
- "description": "This type describes the protocol layer(s) that a CP or SAP uses together with protocol-related information, like addresses. It shall comply with the provisions defined in Table 6.5.3.58-1. NOTE: This attribute allows to signal the addition of further types of layer and protocol in future versions of the present document in a backwards-compatible way. In the current version of the present document, only IP over Ethernet is supported.\n",
- "type": "object",
- "required": ["layerProtocol", "ipOverEthernet"],
- "properties": {
- "layerProtocol": {
- "description": "The identifier of layer(s) and protocol(s) associated to the network address information. Permitted values: - IP_OVER_ETHERNET\n - IP_FOR_VIRTUAL_CP\nSee note.\n",
- "type": "string",
- "enum": ["IP_OVER_ETHERNET", "IP_FOR_VIRTUAL_CP"]
- },
- "ipOverEthernet": {
- "description": "This type represents information about a network address that has been assigned.\nNOTE 1: At least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2: Exactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3: If the Cp instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4: Depending on the NFVI networking infrastructure, the \"segmentationId\" may indicate the actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header of the packets or it may be an identifier used between the application and the NFVI networking infrastructure to identify the network sub-interface of the trunk port in question. In the latter case the NFVI infrastructure will map this local \"segmentationId\" to whatever \"segmentationId\" is actually used by the NFVI's transport technology.\n",
- "type": "object",
- "anyOf": [{
- "required": ["macAddress"]
- }, {
- "required": ["ipAddresses"]
- }],
- "properties": {
- "macAddress": {
- "description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
- "type": "string",
- "format": "MAC"
- },
- "segmentationId": {
- "description": "Identification of the network segment to which the Cp instance connects to. See note 3 and note 4.\n",
- "type": "string"
- },
- "ipAddresses": {
- "description": "Addresses assigned to the CP instance. Each entry represents IP addresses assigned by fixed or dynamic IP address assignment per subnet. See note 1.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": ["type"],
- "oneOf": [{
- "required": ["addresses"]
- }, {
- "required": ["addressRange"]
- }],
- "properties": {
- "type": {
- "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
- "type": "string",
- "enum": ["IPV4", "IPV6"]
- },
- "addresses": {
- "description": "Fixed addresses assigned (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
- "type": "array",
- "items": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- },
- "isDynamic": {
- "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
- "type": "boolean"
- },
- "addressRange": {
- "description": "An IP address range used, e.g., in case of egress connections. Exactly one of \"addresses\" or \"addressRange\" shall be present. See note 2.\n",
- "type": "object",
- "required": ["minAddress", "maxAddress"],
- "properties": {
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- },
- "subnetId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- }
- },
- "type": {
- "description": "The type of the IP addresses\n",
- "type": "string",
- "enum": ["PV4", "PV6"]
- },
- "addresses": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "isDynamic": {
- "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
- "type": "boolean"
- },
- "addressRange": {
- "description": "An IP address range used, e.g. in case of egress connections. See note.\n",
- "type": "object",
- "required": ["minAddress", "maxAddress"],
- "properties": {
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- },
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "subnetId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- },
- "virtualCpAddress": {
- "description": "This type represents information about a network address that has been assigned to a virtual CP.\n",
- "type": "object",
- "required": ["type"],
- "properties": {
- "type": {
- "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
- "type": "string",
- "enum": ["IPV4", "IPV6"]
- },
- "loadBalancerIp": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- }
- }
- }
- },
- "extLinkPortId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "netAttDefResourceId": {
- "description": "Identifier of the \"NetAttDefResourceInfo\" structure that provides the specification of the interface to attach the connection point to a secondary container cluster network. See notes 3 and 4.\nIt shall be present if the external CP is associated to a VNFC realized by one or a set of OS containers and is connected to a secondary container cluster network. It shall not be present otherwise.\n",
- "type": "array",
- "items": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- }
- },
- "metadata": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- },
- "associatedVnfcCpId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "associatedVipCpId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "associatedVirtualCpId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "associatedVnfVirtualLinkId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- }
- }
+ },
+ "type": {
+ "description": "The type of the IP addresses\n",
+ "type": "string",
+ "enum": [
+ "PV4",
+ "PV6"
+ ]
+ },
+ "addresses": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "isDynamic": {
+ "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
+ "type": "boolean"
+ },
+ "addressRange": {
+ "description": "An IP address range used, e.g. in case of egress connections. See note.\n",
+ "type": "object",
+ "required": [
+ "minAddress",
+ "maxAddress"
+ ],
+ "properties": {
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ }
}
+ },
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "subnetId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ }
+ }
+ },
+ "virtualCpAddress": {
+ "description": "This type represents information about a network address that has been assigned to a virtual CP.\n",
+ "type": "object",
+ "required": [
+ "type"
+ ],
+ "properties": {
+ "type": {
+ "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
+ },
+ "loadBalancerIp": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.",
+ "type": "string"
+ }
+ }
+ }
+ }
+ }
+ },
+ "associatedVnfcCpIds": {
+ "description": "Identifiers of the VnfcCps that share the virtual IP addresse allocated to the VIP CP instance. See note.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ }
+ },
+ "vnfLinkPortId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "metadata": {
+ "description": "Allows the OSS/BSS to provide additional parameter(s) to the termination process at the NS level.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ }
+ }
+ },
+ "virtualCpInfo": {
+ "description": "virtual CPs that are part of the VNF instance. Shall be present when a particular virtual CP is associated to an external CP of the VNF instance. May be present otherwise.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the information related to a virtual CP instance of a VNF. NOTE: A consumer of the VNF LCM interface can learn the actual VNFC instances implementing the service accessible via the virtual CP instance by querying the \"vnfcResourceInfo\" from the \"InstantiatedVnfInfo\" and filtering by corresponding \"vduId\" values.",
+ "type": "object",
+ "required": [
+ "cpInstanceId",
+ "cpdId",
+ "resourceHandle",
+ "vduId"
+ ],
+ "properties": {
+ "cpInstanceId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "cpdId": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
+ "type": "string"
+ },
+ "resourceHandle": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would correspond to the ‘kind’ field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the ‘claimName’ field in the Kubernetes® manifest, or a compound name built by Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the ‘metadata.name’ field in Kubernetes® manifest. \n",
+ "type": "object",
+ "required": [
+ "resourceId"
+ ],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceProviderId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "type": "string"
+ },
+ "vimLevelAdditionalResourceInfo": {
+ "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
+ "type": "object",
+ "properties": {
+ "hostName": {
+ "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "persistentVolume": {
+ "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
},
- "vipCpInfo": {
- "description": "VIP CPs that are part of the VNF instance. Shall be present when that particular VIP CP of the VNFC instance is associated to an external CP of the VNF instance. May be present otherwise.\n",
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ },
+ "containerNamespace": {
+ "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise. \n",
+ "type": "string"
+ }
+ }
+ },
+ "vnfExtCpId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "cpProtocolInfo": {
+ "description": "Protocol information for this CP. There shall be one cpProtocolInfo for each layer protocol supported.\n",
+ "type": "array",
+ "items": {
+ "description": "This type describes the protocol layer(s) that a CP or SAP uses together with protocol-related information, like addresses. It shall comply with the provisions defined in Table 6.5.3.58-1. NOTE: This attribute allows to signal the addition of further types of layer and protocol in future versions of the present document in a backwards-compatible way. In the current version of the present document, only IP over Ethernet is supported.\n",
+ "type": "object",
+ "required": [
+ "layerProtocol",
+ "ipOverEthernet"
+ ],
+ "properties": {
+ "layerProtocol": {
+ "description": "The identifier of layer(s) and protocol(s) associated to the network address information. Permitted values:\n - IP_OVER_ETHERNET\n - IP_FOR_VIRTUAL_CP\nSee note.\n",
+ "type": "string",
+ "enum": [
+ "IP_OVER_ETHERNET",
+ "IP_FOR_VIRTUAL_CP"
+ ]
+ },
+ "ipOverEthernet": {
+ "description": "This type represents information about a network address that has been assigned.\nNOTE 1: At least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2: Exactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3: If the Cp instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4: Depending on the NFVI networking infrastructure, the \"segmentationId\" may indicate the actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header of the packets or it may be an identifier used between the application and the NFVI networking infrastructure to identify the network sub-interface of the trunk port in question. In the latter case the NFVI infrastructure will map this local \"segmentationId\" to whatever \"segmentationId\" is actually used by the NFVI's transport technology.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "required": [
+ "macAddress"
+ ]
+ },
+ {
+ "required": [
+ "ipAddresses"
+ ]
+ }
+ ],
+ "properties": {
+ "macAddress": {
+ "description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
+ "type": "string",
+ "format": "MAC"
+ },
+ "segmentationId": {
+ "description": "Identification of the network segment to which the Cp instance connects to. See note 3 and note 4.\n",
+ "type": "string"
+ },
+ "ipAddresses": {
+ "description": "Addresses assigned to the CP instance. Each entry represents IP addresses assigned by fixed or dynamic IP address assignment per subnet. See note 1.\n",
"type": "array",
"items": {
- "description": "This type provides information related to virtual IP (VIP) CP. It shall comply with the provisions defined in table 6.5.3.97 1. NOTE: It is possible that there is no associated VnfcCp because the VIP CP is available but not associated yet.\n",
- "type": "object",
- "required": ["cpInstanceId", "cpdId"],
- "properties": {
- "cpInstanceId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "cpdId": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfExtCpId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "cpProtocolInfo": {
- "description": "Protocol information for this CP. There shall be one cpProtocolInfo for layer 3. There may be one cpProtocolInfo for layer 2.\n",
- "type": "array",
- "items": {
- "description": "This type describes the protocol layer(s) that a CP or SAP uses together with protocol-related information, like addresses. It shall comply with the provisions defined in Table 6.5.3.58-1. NOTE: This attribute allows to signal the addition of further types of layer and protocol in future versions of the present document in a backwards-compatible way. In the current version of the present document, only IP over Ethernet is supported.\n",
- "type": "object",
- "required": ["layerProtocol", "ipOverEthernet"],
- "properties": {
- "layerProtocol": {
- "description": "The identifier of layer(s) and protocol(s) associated to the network address information. Permitted values: - IP_OVER_ETHERNET\n - IP_FOR_VIRTUAL_CP\nSee note.\n",
- "type": "string",
- "enum": ["IP_OVER_ETHERNET", "IP_FOR_VIRTUAL_CP"]
- },
- "ipOverEthernet": {
- "description": "This type represents information about a network address that has been assigned.\nNOTE 1: At least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2: Exactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3: If the Cp instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4: Depending on the NFVI networking infrastructure, the \"segmentationId\" may indicate the actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header of the packets or it may be an identifier used between the application and the NFVI networking infrastructure to identify the network sub-interface of the trunk port in question. In the latter case the NFVI infrastructure will map this local \"segmentationId\" to whatever \"segmentationId\" is actually used by the NFVI's transport technology.\n",
- "type": "object",
- "anyOf": [{
- "required": ["macAddress"]
- }, {
- "required": ["ipAddresses"]
- }],
- "properties": {
- "macAddress": {
- "description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
- "type": "string",
- "format": "MAC"
- },
- "segmentationId": {
- "description": "Identification of the network segment to which the Cp instance connects to. See note 3 and note 4.\n",
- "type": "string"
- },
- "ipAddresses": {
- "description": "Addresses assigned to the CP instance. Each entry represents IP addresses assigned by fixed or dynamic IP address assignment per subnet. See note 1.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": ["type"],
- "oneOf": [{
- "required": ["addresses"]
- }, {
- "required": ["addressRange"]
- }],
- "properties": {
- "type": {
- "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
- "type": "string",
- "enum": ["IPV4", "IPV6"]
- },
- "addresses": {
- "description": "Fixed addresses assigned (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
- "type": "array",
- "items": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- },
- "isDynamic": {
- "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
- "type": "boolean"
- },
- "addressRange": {
- "description": "An IP address range used, e.g., in case of egress connections. Exactly one of \"addresses\" or \"addressRange\" shall be present. See note 2.\n",
- "type": "object",
- "required": ["minAddress", "maxAddress"],
- "properties": {
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- },
- "subnetId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- }
- },
- "type": {
- "description": "The type of the IP addresses\n",
- "type": "string",
- "enum": ["PV4", "PV6"]
- },
- "addresses": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "isDynamic": {
- "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
- "type": "boolean"
- },
- "addressRange": {
- "description": "An IP address range used, e.g. in case of egress connections. See note.\n",
- "type": "object",
- "required": ["minAddress", "maxAddress"],
- "properties": {
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- },
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "subnetId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- },
- "virtualCpAddress": {
- "description": "This type represents information about a network address that has been assigned to a virtual CP.\n",
- "type": "object",
- "required": ["type"],
- "properties": {
- "type": {
- "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
- "type": "string",
- "enum": ["IPV4", "IPV6"]
- },
- "loadBalancerIp": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- }
- }
- }
- },
- "associatedVnfcCpIds": {
- "description": "Identifiers of the VnfcCps that share the virtual IP addresse allocated to the VIP CP instance. See note.\n",
- "type": "array",
- "items": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- }
- },
- "vnfLinkPortId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "metadata": {
- "description": "Allows the OSS/BSS to provide additional parameter(s) to the termination process at the NS level.\n",
- "type": "array",
- "items": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
+ "type": "object",
+ "required": [
+ "type"
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "addresses"
+ ]
+ },
+ {
+ "required": [
+ "addressRange"
+ ]
+ }
+ ],
+ "properties": {
+ "type": {
+ "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
+ },
+ "addresses": {
+ "description": "Fixed addresses assigned (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
+ "type": "array",
+ "items": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ }
+ },
+ "isDynamic": {
+ "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
+ "type": "boolean"
+ },
+ "addressRange": {
+ "description": "An IP address range used, e.g., in case of egress connections. Exactly one of \"addresses\" or \"addressRange\" shall be present. See note 2.\n",
+ "type": "object",
+ "required": [
+ "minAddress",
+ "maxAddress"
+ ],
+ "properties": {
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
}
+ }
+ },
+ "subnetId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
}
+ }
}
- },
- "virtualCpInfo": {
- "description": "virtual CPs that are part of the VNF instance. Shall be present when a particular virtual CP is associated to an external CP of the VNF instance. May be present otherwise.\n",
- "type": "array",
- "items": {
- "description": "This type represents the information related to a virtual CP instance of a VNF. NOTE: A consumer of the VNF LCM interface can learn the actual VNFC instances implementing the service accessible via the virtual CP instance by querying the \"vnfcResourceInfo\" from the \"InstantiatedVnfInfo\" and filtering by corresponding \"vduId\" values.",
- "type": "object",
- "required": ["cpInstanceId", "cpdId", "resourceHandle", "vduId"],
- "properties": {
- "cpInstanceId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "cpdId": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "resourceHandle": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes instance the vimLevelResourceType is the type of resource, as would correspond to the kind field if the resource is declared in its own Kubernetes manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the claimName field in the Kubernetes manifest, or a compound name built by Kubernetes if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the metadata.name field in Kubernetes manifest. \n",
- "type": "object",
- "required": ["resourceId"],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
- "type": "string"
- },
- "vimLevelAdditionalResourceInfo": {
- "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
- "type": "object",
- "properties": {
- "hostName": {
- "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "persistentVolume": {
- "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "containerNamespace": {
- "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
- "type": "string"
- }
- }
- },
- "vnfExtCpId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "cpProtocolInfo": {
- "description": "Protocol information for this CP. There shall be one cpProtocolInfo for each layer protocol supported.\n",
- "type": "array",
- "items": {
- "description": "This type describes the protocol layer(s) that a CP or SAP uses together with protocol-related information, like addresses. It shall comply with the provisions defined in Table 6.5.3.58-1. NOTE: This attribute allows to signal the addition of further types of layer and protocol in future versions of the present document in a backwards-compatible way. In the current version of the present document, only IP over Ethernet is supported.\n",
- "type": "object",
- "required": ["layerProtocol", "ipOverEthernet"],
- "properties": {
- "layerProtocol": {
- "description": "The identifier of layer(s) and protocol(s) associated to the network address information. Permitted values: - IP_OVER_ETHERNET\n - IP_FOR_VIRTUAL_CP\nSee note.\n",
- "type": "string",
- "enum": ["IP_OVER_ETHERNET", "IP_FOR_VIRTUAL_CP"]
- },
- "ipOverEthernet": {
- "description": "This type represents information about a network address that has been assigned.\nNOTE 1: At least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2: Exactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3: If the Cp instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4: Depending on the NFVI networking infrastructure, the \"segmentationId\" may indicate the actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header of the packets or it may be an identifier used between the application and the NFVI networking infrastructure to identify the network sub-interface of the trunk port in question. In the latter case the NFVI infrastructure will map this local \"segmentationId\" to whatever \"segmentationId\" is actually used by the NFVI's transport technology.\n",
- "type": "object",
- "anyOf": [{
- "required": ["macAddress"]
- }, {
- "required": ["ipAddresses"]
- }],
- "properties": {
- "macAddress": {
- "description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
- "type": "string",
- "format": "MAC"
- },
- "segmentationId": {
- "description": "Identification of the network segment to which the Cp instance connects to. See note 3 and note 4.\n",
- "type": "string"
- },
- "ipAddresses": {
- "description": "Addresses assigned to the CP instance. Each entry represents IP addresses assigned by fixed or dynamic IP address assignment per subnet. See note 1.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": ["type"],
- "oneOf": [{
- "required": ["addresses"]
- }, {
- "required": ["addressRange"]
- }],
- "properties": {
- "type": {
- "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
- "type": "string",
- "enum": ["IPV4", "IPV6"]
- },
- "addresses": {
- "description": "Fixed addresses assigned (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
- "type": "array",
- "items": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- },
- "isDynamic": {
- "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
- "type": "boolean"
- },
- "addressRange": {
- "description": "An IP address range used, e.g., in case of egress connections. Exactly one of \"addresses\" or \"addressRange\" shall be present. See note 2.\n",
- "type": "object",
- "required": ["minAddress", "maxAddress"],
- "properties": {
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- },
- "subnetId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- }
- },
- "type": {
- "description": "The type of the IP addresses\n",
- "type": "string",
- "enum": ["PV4", "PV6"]
- },
- "addresses": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "isDynamic": {
- "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
- "type": "boolean"
- },
- "addressRange": {
- "description": "An IP address range used, e.g. in case of egress connections. See note.\n",
- "type": "object",
- "required": ["minAddress", "maxAddress"],
- "properties": {
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- },
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "subnetId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- },
- "virtualCpAddress": {
- "description": "This type represents information about a network address that has been assigned to a virtual CP.\n",
- "type": "object",
- "required": ["type"],
- "properties": {
- "type": {
- "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
- "type": "string",
- "enum": ["IPV4", "IPV6"]
- },
- "loadBalancerIp": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- }
- }
- }
- },
- "vduId": {
- "description": "Reference to the VDU(s) which implement the service accessible via the virtual CP instance. See note.\n",
- "type": "array",
- "items": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- }
- },
- "additionalServiceInfo": {
- "description": "Additional service identification information of the virtual CP instance.\n",
- "type": "array",
- "items": {
- "description": "This type represents the additional service information of the virtual CP instance used to expose properties of the virtual CP to NFV-MANO.\nNOTE: This attribute shall only be present if additional information is needed to identify the service termination within the VNF, such as for example a URL path information in an HTTP request required to allow a single virtual CP IP address to be used for several HTTP based services that use the same port number.",
- "type": "object",
- "required": ["portInfo"],
- "properties": {
- "portInfo": {
- "description": "Service port numbers exposed by the virtual CP instance.\n",
- "type": "array",
- "items": {
- "description": "This type represents the information related to the service identifying port properties exposed by the virtual CP instance.",
- "type": "object",
- "required": ["name", "protocol", "port", "isPortConfigurable"],
- "properties": {
- "name": {
- "description": "The name of the port exposed by the virtual CP instance.\n",
- "type": "string"
- },
- "protocol": {
- "description": "The L4 protocol for this port exposed by the virtual CP instance. Permitted values:\n - TCP\n - UDP\n - SCTP\n",
- "type": "string",
- "enum": ["TCP", "UDP", "SCTP"]
- },
- "port": {
- "description": "The L4 port number exposed by the virtual CP instance.\n",
- "type": "integer"
- },
- "isPortConfigurable": {
- "description": "Specifies whether the port attribute value is allowed to be configurable.\n",
- "type": "boolean"
- }
- }
- }
- },
- "serviceInfo": {
- "description": "Service matching information exposed by the virtual CP instance. See note.\n",
- "type": "array",
- "items": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- }
- }
- },
- "metadata": {
- "description": "Metadata about this virtual CP instance.\n",
- "type": "array",
- "items": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- }
+ },
+ "type": {
+ "description": "The type of the IP addresses\n",
+ "type": "string",
+ "enum": [
+ "PV4",
+ "PV6"
+ ]
+ },
+ "addresses": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "isDynamic": {
+ "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
+ "type": "boolean"
+ },
+ "addressRange": {
+ "description": "An IP address range used, e.g. in case of egress connections. See note.\n",
+ "type": "object",
+ "required": [
+ "minAddress",
+ "maxAddress"
+ ],
+ "properties": {
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ }
}
+ },
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "subnetId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ }
+ }
+ },
+ "virtualCpAddress": {
+ "description": "This type represents information about a network address that has been assigned to a virtual CP.\n",
+ "type": "object",
+ "required": [
+ "type"
+ ],
+ "properties": {
+ "type": {
+ "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
+ },
+ "loadBalancerIp": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.",
+ "type": "string"
+ }
+ }
+ }
+ }
+ }
+ },
+ "vduId": {
+ "description": "Reference to the VDU(s) which implement the service accessible via the virtual CP instance. See note.\n",
+ "type": "array",
+ "items": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
+ "type": "string"
+ }
+ },
+ "additionalServiceInfo": {
+ "description": "Additional service identification information of the virtual CP instance.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the additional service information of the virtual CP instance used to expose properties of the virtual CP to NFV-MANO.\nNOTE: This attribute shall only be present if additional information is needed to identify the service termination within the VNF, such as for example a URL path information in an HTTP request required to allow a single virtual CP IP address to be used for several HTTP based services that use the same port number.",
+ "type": "object",
+ "required": [
+ "portInfo"
+ ],
+ "properties": {
+ "portInfo": {
+ "description": "Service port numbers exposed by the virtual CP instance.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the information related to the service identifying port properties exposed by the virtual CP instance.",
+ "type": "object",
+ "required": [
+ "name",
+ "protocol",
+ "port",
+ "isPortConfigurable"
+ ],
+ "properties": {
+ "name": {
+ "description": "The name of the port exposed by the virtual CP instance.\n",
+ "type": "string"
+ },
+ "protocol": {
+ "description": "The L4 protocol for this port exposed by the virtual CP instance.\n Permitted values:\n - TCP\n - UDP\n - SCTP\n",
+ "type": "string",
+ "enum": [
+ "TCP",
+ "UDP",
+ "SCTP"
+ ]
+ },
+ "port": {
+ "description": "The L4 port number exposed by the virtual CP instance.\n",
+ "type": "integer"
+ },
+ "isPortConfigurable": {
+ "description": "Specifies whether the port attribute value is allowed to be configurable.\n",
+ "type": "boolean"
+ }
+ }
+ }
+ },
+ "serviceInfo": {
+ "description": "Service matching information exposed by the virtual CP instance. See note.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ }
+ }
+ },
+ "metadata": {
+ "description": "Metadata about this virtual CP instance.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ }
+ }
+ },
+ "extVirtualLinkInfo": {
+ "description": "Information about the external VLs the VNF instance is connected to.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents information about an VNF external VL.",
+ "type": "object",
+ "required": [
+ "id",
+ "resourceHandle",
+ "currentVnfExtCpData"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceHandle": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would correspond to the ‘kind’ field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the ‘claimName’ field in the Kubernetes® manifest, or a compound name built by Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the ‘metadata.name’ field in Kubernetes® manifest. \n",
+ "type": "object",
+ "required": [
+ "resourceId"
+ ],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceProviderId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "type": "string"
+ },
+ "vimLevelAdditionalResourceInfo": {
+ "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
+ "type": "object",
+ "properties": {
+ "hostName": {
+ "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "persistentVolume": {
+ "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
},
- "extVirtualLinkInfo": {
- "description": "Information about the external VLs the VNF instance is connected to.\n",
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ },
+ "containerNamespace": {
+ "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise. \n",
+ "type": "string"
+ }
+ }
+ },
+ "extLinkPorts": {
+ "description": "Link ports of this VL.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents information about a link port of an external VL, i.e. a port providing connectivity for the VNF to an NS VL. NOTE 1: The use cases UC#4 and UC#5 in Annex A.4 of ETSI GS NFV-IFA 007 provide examples for such a configuration. NOTE 2: The value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\" attribute.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "resourceHandle"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceHandle": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would correspond to the ‘kind’ field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the ‘claimName’ field in the Kubernetes® manifest, or a compound name built by Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the ‘metadata.name’ field in Kubernetes® manifest. \n",
+ "type": "object",
+ "required": [
+ "resourceId"
+ ],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceProviderId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "type": "string"
+ },
+ "vimLevelAdditionalResourceInfo": {
+ "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
+ "type": "object",
+ "properties": {
+ "hostName": {
+ "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "persistentVolume": {
+ "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ },
+ "containerNamespace": {
+ "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise. \n",
+ "type": "string"
+ }
+ }
+ },
+ "cpInstanceId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "secondaryCpInstanceId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "trunkResourceId": {
+ "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "extNetAttDefResource": {
+ "description": "Network attachment definition resources that provide the specification of the interface to attach connection points to this VL.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the information related to a network attachment definition resource that provides the specification of the interface used to connect one or multiple connection points to a secondary container cluster network\n",
+ "type": "object",
+ "required": [
+ "netAttDefResourceInfoId",
+ "netAttDefResource"
+ ],
+ "properties": {
+ "netAttDefResourceInfoId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "netAttDefResource": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would correspond to the ‘kind’ field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the ‘claimName’ field in the Kubernetes® manifest, or a compound name built by Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the ‘metadata.name’ field in Kubernetes® manifest. \n",
+ "type": "object",
+ "required": [
+ "resourceId"
+ ],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceProviderId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "type": "string"
+ },
+ "vimLevelAdditionalResourceInfo": {
+ "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
+ "type": "object",
+ "properties": {
+ "hostName": {
+ "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "persistentVolume": {
+ "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ },
+ "containerNamespace": {
+ "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise. \n",
+ "type": "string"
+ }
+ }
+ },
+ "associatedExtCpId": {
+ "description": "Identifier of the external CP of the VNF associated to this network attachment definition resource. Shall be present when the network attachment definition resource is used for external connectivity by the VNF\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ }
+ },
+ "associatedVnfcCpId": {
+ "description": "Identifier of the VNFC CP of the VNF associated to this network attachment definition resource. May be present when the network attachment definition resource is used for internal connectivity by the VNF.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ }
+ }
+ }
+ }
+ },
+ "currentVnfExtCpData": {
+ "description": "This type represents configuration information for external CPs created from a CPD.\nNOTE 1: In case this identifier refers to a CPD with trunking enabled, the external CP instances created from this CPD will represent ports in a trunk. NOTE 2: The map entry value shall be set to \"null\" in order to delete a \"VnfExtCpConfig\" entry identified by a particular key value from the map, i.e. for the disconnection of an existing external CP instance addressed by cpInstanceId in the deleted map entry from a particular external virtual link, and deletion of that instance in case it represents a subport. Deleting the last key from the map removes the affected instance of the \"VnfExtCpData\" structure from its parent data structure. NOTE 3: Within one VNF instance, all VNFC instances created from a particular VDU have the same external connectivity. Thus, given a particular value of the \"cpdId' attribute, there shall be one \"cpConfig\" entry for each VNFC instance that has been or can be created from a VDU which includes a CPD identified by the \"cpdId\" attribute. If the cpConfig represents a subport in a trunk, all \"cpConfig\" entries in this list shall have the same segmentationId, which means they are connected to the same set of external VLs via the trunk. NOTE 4: If, as defined by the input parameters of a \"ChangeVnfFlavour\", \"ChangeExtVnfConnectivity\" or \"ChangeCurrentVnfPkg\" operation, a cpConfig map entry identified by a particular map key value is moved into another \"ExtVirtualLinkData\" or \"VnfExtCpData\" structure, this particular cpConfig map entry may be used by an external CP instance different than the one that has used it before the operation, or by no external CP instance at all. Renaming a CPD identifier during the \"changeCurrentVnfPkg\" operation does not count as moving the related \"cpConfig\" map entries to a new \"extCpData\" structure.\n",
+ "type": "object",
+ "required": [
+ "cpdId"
+ ],
+ "properties": {
+ "cpdId": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
+ "type": "string"
+ },
+ "cpConfig": {
+ "description": "Map of instance data that need to be configured on the CP instances created from the respective CPD. The key of the map which identifies the individual VnfExtCpConfig entries is of type \"IdentifierInVnf\" and is managed by the API consumer. The entries shall be applied by the VNFM according to the rules of JSON Merge Patch (see IETF RFC 7396 [11]). See notes 2, 3 and 4.\n",
+ "type": "object",
+ "additionalProperties": {
+ "description": "This type represents an externally provided link port, or a network attachment definition resource of secondary container cluster network, or network address information per instance of a VNF external connection point. In the case of VM-based deployment of the VNFC exposing the external CP: In case a link port is provided, the NFVO shall use that link port when connecting the VNF external CP to the external VL. • In case a link port is not provided, the NFVO or VNFM shall create a link port on the external VL, and use that link port to connect the VNF external CP to the external VL. In the case of container-based deployment of the VNFC exposing the external CP, the NFVO and VNFM shall use the network attachment definition resource of secondary container cluster network when connecting the CP to the external VL.\nNOTE 1: The following conditions apply to the attributes \"linkPortId\" and \"cpProtocolData\"\n for an external CP instance connected or to be connected to a virtual network not\n categorized as secondary container cluster network:\n - At least one of the \"linkPortId\" and \"cpProtocolData\" attributes shall be present for\n an external CP instance representing a subport that is to be created, or an external CP instance\n that is to be created by creating the corresponding VNFC or VNF instance during the current or\n a subsequent LCM operation, or for an existing external CP instance that is to be re-configured\n or added to a particular external virtual link.\n - If the \"cpProtocolData\" attribute is absent, the \"linkPortId\" attribute shall be provided\n referencing a pre-created link port with pre-configured address information.\n - If both \"cpProtocolData\" and \"linkportId\" are provided, the API consumer shall ensure that\n the cpProtocolData can be used with the pre-created link port referenced by \"linkPortId\".\nNOTE 2: In case the NFVO manages its own identifier space, the NFVO may remap this identifier\n when communicating with the VNFM. If the NFVO knows that there can be an identifier collision\n when communicating with the VNFM by using the identifier from the OSS/BSS, the NFVO shall remap it.\nNOTE 3: The following conditions apply to the attributes \"netAttDefResourceId\" and \"cpProtocolData\" for an external CP\n instance connected or to be connected to a secondary container cluster network:\n − Void.\n − At least one of these attributes shall be present for a to-be-created external CP instance or an existing\n external CP instance.\nNOTE 4: Cardinality greater than 1 is only applicable for specific cases where more than one network\n attachment definition resource is needed to fulfil the connectivity requirements of the external CP,\n e.g. to build a link redundant mated pair in SR-IOV cases. When more than one \"netAttDefResourceId\"\n is indicated, all shall belong to the same namespace as defined by the corresponding \n \"containerNamespace\" attribute in the \"resourceHandle\" attribute in the \"NetAttDefResourceData\".\nNOTE 5: Either \"linkPortId\" or \"netAttDefResourceId\" may be included, but not both.\n",
+ "type": "object",
+ "oneOf": [
+ {
+ "required": [
+ "linkPortId"
+ ]
+ },
+ {
+ "required": [
+ "cpProtocolData"
+ ]
+ }
+ ],
+ "properties": {
+ "parentCpConfigId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "linkPortId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "createExtLinkPort": {
+ "description": "Indicates the need to create a dedicated link port for the external CP. If set to True, a link port is created. If set to False, no link port is created. This attribute is only applicable for external CP instances without a floating IP address that expose a VIP CP instance for which a dedicated IP address is allocated. It shall be present in that case and shall be absent otherwise.\n",
+ "type": "boolean"
+ },
+ "cpProtocolData": {
+ "description": "Parameters for configuring the network protocols on the link port that connects the CP to a VL. See notes 1 and 3.\n",
"type": "array",
"items": {
- "description": "This type represents information about an VNF external VL.",
- "type": "object",
- "required": ["id", "resourceHandle", "currentVnfExtCpData"],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceHandle": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes instance the vimLevelResourceType is the type of resource, as would correspond to the kind field if the resource is declared in its own Kubernetes manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the claimName field in the Kubernetes manifest, or a compound name built by Kubernetes if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the metadata.name field in Kubernetes manifest. \n",
+ "description": "This type represents network protocol data.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the present document in a backwards-compatible way. In the current version of the present document, only IP over Ethernet is supported.\n",
+ "type": "object",
+ "required": [
+ "layerProtocol"
+ ],
+ "properties": {
+ "layerProtocol": {
+ "description": "Identifier of layer(s) and protocol(s). Permitted values: - IP_OVER_ETHERNET - IP_FOR_VIRTUAL_CP See note.\n",
+ "type": "string",
+ "enum": [
+ "IP_OVER_ETHERNET",
+ "IP_FOR_VIRTUAL_CP"
+ ]
+ },
+ "ipOverEthernet": {
+ "description": "This type represents network address data for IP over Ethernet. NOTE 1: At least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2: Exactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present. NOTE 3: If the CP instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4: Depending on the NFVI networking infrastructure, the \"segmentationId\" may indicate the actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header of the packets or it may be an identifier used between the application and the NFVI networking infrastructure to identify the network sub-interface of the trunk port in question. In the latter case the NFVI infrastructure will map this local \"segmentationId\" to whatever \"segmentationId\" is actually used by the NFVI's transport technology.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "required": [
+ "ipAddresses"
+ ]
+ },
+ {
+ "required": [
+ "macAddress"
+ ]
+ }
+ ],
+ "properties": {
+ "macAddress": {
+ "description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
+ "type": "string",
+ "format": "MAC"
+ },
+ "segmentationType": {
+ "description": "Specifies the encapsulation type for the traffics coming in and out of the trunk subport. Permitted values are: - VLAN: The subport uses VLAN as encapsulation type. - INHERIT: The subport gets its segmentation type from the network it is connected to. This attribute may be present for CP instances that represent subports in a trunk and shall be absent otherwise. If this attribute is not present for a subport CP instance, default value VLAN shall be used.\n",
+ "type": "string",
+ "enum": [
+ "VLAN",
+ "INHERIT"
+ ]
+ },
+ "segmentationId": {
+ "description": "Identification of the network segment to which the CP instance connects to. See note 3 and note 4.\n",
+ "type": "string"
+ },
+ "ipAddresses": {
+ "description": "List of IP addresses to assign to the CP instance. Each entry represents IP address data for fixed or dynamic IP address assignment per subnet. If this attribute is not present, no IP address shall be assigned. See note 1.\n",
+ "type": "array",
+ "items": {
"type": "object",
- "required": ["resourceId"],
+ "required": [
+ "type"
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "fixedAddresses"
+ ]
+ },
+ {
+ "required": [
+ "numDynamicAddresses"
+ ]
+ },
+ {
+ "required": [
+ "addressRange"
+ ]
+ }
+ ],
"properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
- "type": "string"
- },
- "vimLevelAdditionalResourceInfo": {
- "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
- "type": "object",
- "properties": {
- "hostName": {
- "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "persistentVolume": {
- "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "containerNamespace": {
- "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
- "type": "string"
- }
- }
- },
- "extLinkPorts": {
- "description": "Link ports of this VL.\n",
- "type": "array",
- "items": {
- "description": "This type represents information about a link port of an external VL, i.e. a port providing connectivity for the VNF to an NS VL. NOTE 1: The use cases UC#4 and UC#5 in Annex A.4 of ETSI GS NFV-IFA 007 provide examples for such a configuration. NOTE 2: The value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\" attribute.\n",
- "type": "object",
- "required": ["id", "resourceHandle"],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceHandle": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes instance the vimLevelResourceType is the type of resource, as would correspond to the kind field if the resource is declared in its own Kubernetes manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the claimName field in the Kubernetes manifest, or a compound name built by Kubernetes if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the metadata.name field in Kubernetes manifest. \n",
- "type": "object",
- "required": ["resourceId"],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
- "type": "string"
- },
- "vimLevelAdditionalResourceInfo": {
- "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
- "type": "object",
- "properties": {
- "hostName": {
- "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "persistentVolume": {
- "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "containerNamespace": {
- "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
- "type": "string"
- }
- }
- },
- "cpInstanceId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "secondaryCpInstanceId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "trunkResourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- }
+ "type": {
+ "description": "The type of the IP addresses. Permitted values:\n - IPV4\n - IPV6\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
+ },
+ "fixedAddresses": {
+ "description": "Fixed addresses to assign (from the subnet defined by \"subnetId\" if provided). Exactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present.\n",
+ "type": "array",
+ "items": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
}
- }
- },
- "extNetAttDefResource": {
- "description": "Network attachment definition resources that provide the specification of the interface to attach connection points to this VL.\n",
- "type": "array",
- "items": {
- "description": "This type represents the information related to a network attachment definition resource that provides the specification of the interface used to connect one or multiple connection points to a secondary container cluster network\n",
+ },
+ "numDynamicAddresses": {
+ "description": "Number of dynamic addresses to assign (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
+ "type": "integer"
+ },
+ "addressRange": {
+ "description": "An IP address range to be used, e.g. in case of egress connections. In case this attribute is present, IP addresses from the range will be used.\n",
"type": "object",
- "required": ["netAttDefResourceInfoId", "netAttDefResource"],
+ "required": [
+ "minAddress",
+ "maxAddress"
+ ],
"properties": {
- "netAttDefResourceInfoId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "netAttDefResource": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes instance the vimLevelResourceType is the type of resource, as would correspond to the kind field if the resource is declared in its own Kubernetes manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the claimName field in the Kubernetes manifest, or a compound name built by Kubernetes if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the metadata.name field in Kubernetes manifest. \n",
- "type": "object",
- "required": ["resourceId"],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
- "type": "string"
- },
- "vimLevelAdditionalResourceInfo": {
- "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
- "type": "object",
- "properties": {
- "hostName": {
- "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "persistentVolume": {
- "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "containerNamespace": {
- "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
- "type": "string"
- }
- }
- },
- "associatedExtCpId": {
- "description": "Identifier of the external CP of the VNF associated to this network attachment definition resource. Shall be present when the network attachment definition resource is used for external connectivity by the VNF\n",
- "type": "array",
- "items": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- }
- },
- "associatedVnfcCpId": {
- "description": "Identifier of the VNFC CP of the VNF associated to this network attachment definition resource. May be present when the network attachment definition resource is used for internal connectivity by the VNF.\n",
- "type": "array",
- "items": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- }
- }
- }
- }
- },
- "currentVnfExtCpData": {
- "description": "This type represents configuration information for external CPs created from a CPD.\nNOTE 1: In case this identifier refers to a CPD with trunking enabled, the external CP instances created from this CPD will represent ports in a trunk. NOTE 2: The map entry value shall be set to \"null\" in order to delete a \"VnfExtCpConfig\" entry identified by a particular key value from the map, i.e. for the disconnection of an existing external CP instance addressed by cpInstanceId in the deleted map entry from a particular external virtual link, and deletion of that instance in case it represents a subport. Deleting the last key from the map removes the affected instance of the \"VnfExtCpData\" structure from its parent data structure. NOTE 3: Within one VNF instance, all VNFC instances created from a particular VDU have the same external connectivity. Thus, given a particular value of the \"cpdId' attribute, there shall be one \"cpConfig\" entry for each VNFC instance that has been or can be created from a VDU which includes a CPD identified by the \"cpdId\" attribute. If the cpConfig represents a subport in a trunk, all \"cpConfig\" entries in this list shall have the same segmentationId, which means they are connected to the same set of external VLs via the trunk. NOTE 4: If, as defined by the input parameters of a \"ChangeVnfFlavour\", \"ChangeExtVnfConnectivity\" or \"ChangeCurrentVnfPkg\" operation, a cpConfig map entry identified by a particular map key value is moved into another \"ExtVirtualLinkData\" or \"VnfExtCpData\" structure, this particular cpConfig map entry may be used by an external CP instance different than the one that has used it before the operation, or by no external CP instance at all. Renaming a CPD identifier during the \"changeCurrentVnfPkg\" operation does not count as moving the related \"cpConfig\" map entries to a new \"extCpData\" structure.\n",
- "type": "object",
- "required": ["cpdId"],
- "properties": {
- "cpdId": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "cpConfig": {
- "description": "Map of instance data that need to be configured on the CP instances created from the respective CPD. The key of the map which identifies the individual VnfExtCpConfig entries is of type \"IdentifierInVnf\" and is managed by the API consumer. The entries shall be applied by the VNFM according to the rules of JSON Merge Patch (see IETF RFC 7396 [11]). See notes 2, 3 and 4.\n",
- "type": "object",
- "additionalProperties": {
- "description": "This type represents an externally provided link port, or a network attachment definition resource of secondary container cluster network, or network address information per instance of a VNF external connection point. In the case of VM-based deployment of the VNFC exposing the external CP: In case a link port is provided, the NFVO shall use that link port when connecting the VNF external CP to the external VL. In case a link port is not provided, the NFVO or VNFM shall create a link port on the external VL, and use that link port to connect the VNF external CP to the external VL. In the case of container-based deployment of the VNFC exposing the external CP, the NFVO and VNFM shall use the network attachment definition resource of secondary container cluster network when connecting the CP to the external VL.\nNOTE 1: The following conditions apply to the attributes \"linkPortId\" and \"cpProtocolData\" for an external CP instance connected or to be connected to a virtual network not\n categorized as secondary container cluster network:\n - At least one of the \"linkPortId\" and \"cpProtocolData\" attributes shall be present for\n an external CP instance representing a subport that is to be created, or an external CP instance\n that is to be created by creating the corresponding VNFC or VNF instance during the current or\n a subsequent LCM operation, or for an existing external CP instance that is to be re-configured\n or added to a particular external virtual link.\n - If the \"cpProtocolData\" attribute is absent, the \"linkPortId\" attribute shall be provided\n referencing a pre-created link port with pre-configured address information.\n - If both \"cpProtocolData\" and \"linkportId\" are provided, the API consumer shall ensure that\n the cpProtocolData can be used with the pre-created link port referenced by \"linkPortId\".\nNOTE 2: In case the NFVO manages its own identifier space, the NFVO may remap this identifier when communicating with the VNFM. If the NFVO knows that there can be an identifier collision when communicating with the VNFM by using the identifier from the OSS/BSS, the NFVO shall remap it. NOTE 3: The following conditions apply to the attributes netAttDefResourceId and cpProtocolData for an external CP instance connected or to be connected to a secondary container cluster network; The \"netAttDefResourceId\" and \"cpProtocolData\" attributes shall both be absent for the deletion of an existing external CP instance addressed by \"cpInstanceId\". At least one of these attributes shall be present for a to-be-created external CP instance or an existing external CP instance. NOTE 4: Cardinality greater than 1 is only applicable for specific cases where more than one network attachment definition resource is needed to fulfil the connectivity requirements of the external CP, e.g. to build a link redundant mated pair in SR-IOV cases. When more than one \"netAttDefResourceId\" is indicated, all shall belong to the same namespace as defined by the corresponding \"netAttDefResourceNamespace\" attribute in the \"NetAttDefResourceData\". NOTE 5: Either \"linkPortId\" or \"netAttDefResourceId\" may be included, but not both.\n",
- "type": "object",
- "oneOf": [{
- "required": ["linkPortId"]
- }, {
- "required": ["cpProtocolData"]
- }],
- "properties": {
- "parentCpConfigId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "linkPortId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "createExtLinkPort": {
- "description": "Indicates the need to create a dedicated link port for the external CP. If set to True, a link port is created. If set to False, no link port is created. This attribute is only applicable for external CP instances without a floating IP address that expose a VIP CP instance for which a dedicated IP address is allocated. It shall be present in that case and shall be absent otherwise.\n",
- "type": "boolean"
- },
- "cpProtocolData": {
- "description": "Parameters for configuring the network protocols on the link port that connects the CP to a VL. See notes 1 and 3.\n",
- "type": "array",
- "items": {
- "description": "This type represents network protocol data.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the present document in a backwards-compatible way. In the current version of the present document, only IP over Ethernet is supported.\n",
- "type": "object",
- "required": ["layerProtocol"],
- "properties": {
- "layerProtocol": {
- "description": "Identifier of layer(s) and protocol(s). Permitted values: - IP_OVER_ETHERNET - IP_FOR_VIRTUAL_CP See note.\n",
- "type": "string",
- "enum": ["IP_OVER_ETHERNET", "IP_FOR_VIRTUAL_CP"]
- },
- "ipOverEthernet": {
- "description": "This type represents network address data for IP over Ethernet. NOTE 1: At least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2: Exactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present. NOTE 3: If the CP instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4: Depending on the NFVI networking infrastructure, the \"segmentationId\" may indicate the actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header of the packets or it may be an identifier used between the application and the NFVI networking infrastructure to identify the network sub-interface of the trunk port in question. In the latter case the NFVI infrastructure will map this local \"segmentationId\" to whatever \"segmentationId\" is actually used by the NFVI's transport technology.\n",
- "type": "object",
- "anyOf": [{
- "required": ["ipAddresses"]
- }, {
- "required": ["macAddress"]
- }],
- "properties": {
- "macAddress": {
- "description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
- "type": "string",
- "format": "MAC"
- },
- "segmentationType": {
- "description": "Specifies the encapsulation type for the traffics coming in and out of the trunk subport. Permitted values are: - VLAN: The subport uses VLAN as encapsulation type. - INHERIT: The subport gets its segmentation type from the network it is connected to. This attribute may be present for CP instances that represent subports in a trunk and shall be absent otherwise. If this attribute is not present for a subport CP instance, default value VLAN shall be used.\n",
- "type": "string",
- "enum": ["VLAN", "INHERIT"]
- },
- "segmentationId": {
- "description": "Identification of the network segment to which the CP instance connects to. See note 3 and note 4.\n",
- "type": "string"
- },
- "ipAddresses": {
- "description": "List of IP addresses to assign to the CP instance. Each entry represents IP address data for fixed or dynamic IP address assignment per subnet. If this attribute is not present, no IP address shall be assigned. See note 1.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": ["type"],
- "oneOf": [{
- "required": ["fixedAddresses"]
- }, {
- "required": ["numDynamicAddresses"]
- }, {
- "required": ["addressRange"]
- }],
- "properties": {
- "type": {
- "description": "The type of the IP addresses. Permitted values: - IPV4\n - IPV6\n",
- "type": "string",
- "enum": ["IPV4", "IPV6"]
- },
- "fixedAddresses": {
- "description": "Fixed addresses to assign (from the subnet defined by \"subnetId\" if provided). Exactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present.\n",
- "type": "array",
- "items": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- },
- "numDynamicAddresses": {
- "description": "Number of dynamic addresses to assign (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
- "type": "integer"
- },
- "addressRange": {
- "description": "An IP address range to be used, e.g. in case of egress connections. In case this attribute is present, IP addresses from the range will be used.\n",
- "type": "object",
- "required": ["minAddress", "maxAddress"],
- "properties": {
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- },
- "subnetId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- }
- }
- }
- },
- "virtualCpAddress": {
- "description": "This type represents network address data for a virtual CP. It shall comply with the provisions defined in table 6.5.3.12a-1.\n",
- "type": "object",
- "required": ["type"],
- "properties": {
- "type": {
- "description": "Identifier of layer(s) and protocol(s). Permitted values: IP_OVER_ETHERNET.\n",
- "type": "string",
- "enum": ["IPV4", "IPV6"]
- },
- "loadBalancerIp": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- }
- }
- }
- },
- "netAttDefResourceId": {
- "description": "Identifier of the \"NetAttDefResourceData\" structure that provides the specification of the interface to attach the external CP to a secondary container cluster network. It is only applicable if the external CP is connected or to be connected to a secondary container cluster network. It shall not be present if the external CP is related to a virtual network not categorized as secondary container cluster network. See notes 3, 4 and 5.\n",
- "type": "array",
- "items": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- }
- }
- }
- }
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ }
}
+ },
+ "subnetId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ }
}
+ }
}
- }
- }
- },
- "extManagedVirtualLinkInfo": {
- "description": "Information about the externally-managed internal VLs of the VNF instance. See note 4 and note 5.\n",
- "type": "array",
- "items": {
- "description": "This type provides information about an externally-managed internal virtual link for VNFs\n",
- "type": "object",
- "required": ["id", "vnfVirtualLinkDescId", "networkResource"],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfVirtualLinkDescId": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "networkResource": {
- "description": "Reference to the VirtualNetwork resource or multi-site connectivity service providing this VL.\n",
- "type": "array",
- "items": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes instance the vimLevelResourceType is the type of resource, as would correspond to the kind field if the resource is declared in its own Kubernetes manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the claimName field in the Kubernetes manifest, or a compound name built by Kubernetes if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the metadata.name field in Kubernetes manifest. \n",
- "type": "object",
- "required": ["resourceId"],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
- "type": "string"
- },
- "vimLevelAdditionalResourceInfo": {
- "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
- "type": "object",
- "properties": {
- "hostName": {
- "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "persistentVolume": {
- "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "containerNamespace": {
- "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
- "type": "string"
- }
- }
- }
- },
- "vnfLinkPorts": {
- "description": "Link ports of this VL.\n",
- "type": "array",
- "items": {
- "type": "object",
- "description": "This type represents a link port of an internal VL of a VNF. It shall comply with the provisions defined in table 6.5.3.64-1.\nNOTE 1: Either cpInstanceId with cpInstanceType set to \"EXT_CP\" or any combination of cpInstanceId with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId (i.e. one or both of them) shall be present for a VnfLinkPortInfo. In case both cpInstanceId with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId are present, the two different CP instances share the linkport.\n",
- "required": ["id", "resourceHandle"],
- "properties": {
- "id": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "resourceHandle": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes instance the vimLevelResourceType is the type of resource, as would correspond to the kind field if the resource is declared in its own Kubernetes manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the claimName field in the Kubernetes manifest, or a compound name built by Kubernetes if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the metadata.name field in Kubernetes manifest. \n",
- "type": "object",
- "required": ["resourceId"],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
- "type": "string"
- },
- "vimLevelAdditionalResourceInfo": {
- "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
- "type": "object",
- "properties": {
- "hostName": {
- "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "persistentVolume": {
- "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "containerNamespace": {
- "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
- "type": "string"
- }
- }
- },
- "cpInstanceId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "cpInstanceType": {
- "description": "Type of the CP instance that is identified by cpInstanceId. Shall be present if \"cpInstanceId\" is present, and shall be absent otherwise. Permitted values: * VNFC_CP: The link port is connected to a VNFC CP * EXT_CP: The link port is associated to an external CP. See note 1.\n",
- "type": "string",
- "enum": ["VNFC_CP", "EXT_CP"]
- },
- "vipCpInstanceId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "trunkResourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- }
- },
- "vnfNetAttDefResource": {
- "description": "This type represents the information related to a network attachment definition resource that provides the specification of the interface used to connect one or multiple connection points to a secondary container cluster network\n",
- "type": "object",
- "required": ["netAttDefResourceInfoId", "netAttDefResource"],
- "properties": {
- "netAttDefResourceInfoId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "netAttDefResource": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes instance the vimLevelResourceType is the type of resource, as would correspond to the kind field if the resource is declared in its own Kubernetes manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the claimName field in the Kubernetes manifest, or a compound name built by Kubernetes if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the metadata.name field in Kubernetes manifest. \n",
- "type": "object",
- "required": ["resourceId"],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
- "type": "string"
- },
- "vimLevelAdditionalResourceInfo": {
- "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
- "type": "object",
- "properties": {
- "hostName": {
- "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "persistentVolume": {
- "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "containerNamespace": {
- "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
- "type": "string"
- }
- }
- },
- "associatedExtCpId": {
- "description": "Identifier of the external CP of the VNF associated to this network attachment definition resource. Shall be present when the network attachment definition resource is used for external connectivity by the VNF\n",
- "type": "array",
- "items": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- }
- },
- "associatedVnfcCpId": {
- "description": "Identifier of the VNFC CP of the VNF associated to this network attachment definition resource. May be present when the network attachment definition resource is used for internal connectivity by the VNF.\n",
- "type": "array",
- "items": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- }
- }
- }
- },
- "extManagedMultisiteVirtualLinkId": {
- "description": "An identifier with the intention of being globally unique.\n",
+ }
+ },
+ "virtualCpAddress": {
+ "description": "This type represents network address data for a virtual CP. It shall comply with the provisions defined in table 6.5.3.12a-1.\nNOTE 1: If the container cluster is set up to be able to configure an external load balancer this address will be\n used, otherwise it will be ignored by the CISM.\nNOTE 2: In case the cluster can configure an external load balancer but no loadBalancerIp is provided the\n container cluster will assign an IP address.\nNOTE 3: The attribute is only relevant if the virtual CP is instantiated in a cluster that supports configuration of IP\n address pools for virtual CPs. Otherwise it shall be ignored. MetalLB is an example of a solution for\n Kubernetes® that supports configuration of address pools for load balancer services.\nNOTE 4: The loadBalancerIp and the addressPoolName attributes shall not be present at the same time.\n",
+ "type": "object",
+ "required": [
+ "type"
+ ],
+ "properties": {
+ "type": {
+ "description": "Identifier of layer(s) and protocol(s). Permitted values: IP_OVER_ETHERNET.\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
+ },
+ "loadBalancerIp": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which the container cluster will assign an IP address to the virtual CP. See notes 3 and 4.\n",
+ "type": "array",
+ "items": {
"type": "string"
+ }
}
+ }
}
+ }
}
- },
- "monitoringParameters": {
- "description": "Performance metrics tracked by the VNFM (e.g. for auto-scaling purposes) as identified by the VNF provider in the VNFD.\n",
+ },
+ "netAttDefResourceId": {
+ "description": "Identifier of the \"NetAttDefResourceData\" structure that provides the specification of the interface to attach the external CP to a secondary container cluster network. It is only applicable if the external CP is connected or to be connected to a secondary container cluster network. It shall not be present if the external CP is related to a virtual network not categorized as secondary container cluster network. See notes 3, 4 and 5.\n",
"type": "array",
"items": {
- "description": "This type represents a monitoring parameter that is tracked by the VNFM, for example, for auto-scaling purposes. It shall comply with the provisions defined in Table 6.5.3.69-1.\n",
- "type": "object",
- "required": ["id", "performanceMetric"],
- "properties": {
- "id": {
- "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "name": {
- "description": "Human readable name of the monitoring parameter, as defined in the VNFD.\n",
- "type": "string"
- },
- "performanceMetric": {
- "description": "Performance metric that is monitored. This attribute shall contain the related \"Measurement Name\" value as defined in clause 7.2 of ETSI GS NFV-IFA 027.\n",
- "type": "string"
- }
- }
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
}
- },
- "localizationLanguage": {
- "description": "Information about localization language of the VNF (includes e.g. strings in the VNFD). The localization languages supported by a VNF can be declared in the VNFD, and localization language selection can take place at instantiation time. The value shall comply with the format defined in IETF RFC 5646.\n",
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ },
+ "extManagedVirtualLinkInfo": {
+ "description": "Information about the externally-managed internal VLs of the VNF instance. See note 4 and note 5.\n",
+ "type": "array",
+ "items": {
+ "description": "This type provides information about an externally-managed internal virtual link for VNFs\n",
+ "type": "object",
+ "required": [
+ "id",
+ "vnfVirtualLinkDescId",
+ "networkResource"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfVirtualLinkDescId": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
+ "type": "string"
+ },
+ "networkResource": {
+ "description": "Reference to the VirtualNetwork resource or multi-site connectivity service providing this VL.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would correspond to the ‘kind’ field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the ‘claimName’ field in the Kubernetes® manifest, or a compound name built by Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the ‘metadata.name’ field in Kubernetes® manifest. \n",
+ "type": "object",
+ "required": [
+ "resourceId"
+ ],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceProviderId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "type": "string"
+ },
+ "vimLevelAdditionalResourceInfo": {
+ "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
+ "type": "object",
+ "properties": {
+ "hostName": {
+ "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "persistentVolume": {
+ "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ },
+ "containerNamespace": {
+ "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise. \n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "vnfLinkPorts": {
+ "description": "Link ports of this VL.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "description": "This type represents a link port of an internal VL of a VNF. It shall comply with the provisions defined in table 6.5.3.64-1.\nNOTE 1: Either cpInstanceId with cpInstanceType set to \"EXT_CP\" or any combination of cpInstanceId with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId (i.e. one or both of them) shall be present for a VnfLinkPortInfo. In case both cpInstanceId with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId are present, the two different CP instances share the linkport.\n",
+ "required": [
+ "id",
+ "resourceHandle"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "resourceHandle": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would correspond to the ‘kind’ field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the ‘claimName’ field in the Kubernetes® manifest, or a compound name built by Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the ‘metadata.name’ field in Kubernetes® manifest. \n",
+ "type": "object",
+ "required": [
+ "resourceId"
+ ],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceProviderId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "type": "string"
+ },
+ "vimLevelAdditionalResourceInfo": {
+ "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
+ "type": "object",
+ "properties": {
+ "hostName": {
+ "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "persistentVolume": {
+ "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ },
+ "containerNamespace": {
+ "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise. \n",
"type": "string"
+ }
+ }
+ },
+ "cpInstanceId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "cpInstanceType": {
+ "description": "Type of the CP instance that is identified by cpInstanceId. Shall be present if \"cpInstanceId\" is present, and shall be absent otherwise. Permitted values: * VNFC_CP: The link port is connected to a VNFC CP * EXT_CP: The link port is associated to an external CP. See note 1.\n",
+ "type": "string",
+ "enum": [
+ "VNFC_CP",
+ "EXT_CP"
+ ]
+ },
+ "vipCpInstanceId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "trunkResourceId": {
+ "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "vnfNetAttDefResource": {
+ "description": "This type represents the information related to a network attachment definition resource that provides the specification of the interface used to connect one or multiple connection points to a secondary container cluster network\n",
+ "type": "object",
+ "required": [
+ "netAttDefResourceInfoId",
+ "netAttDefResource"
+ ],
+ "properties": {
+ "netAttDefResourceInfoId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "netAttDefResource": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would correspond to the ‘kind’ field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the ‘claimName’ field in the Kubernetes® manifest, or a compound name built by Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the ‘metadata.name’ field in Kubernetes® manifest. \n",
+ "type": "object",
+ "required": [
+ "resourceId"
+ ],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
},
- "vnfcResourceInfo": {
- "description": "Information about the virtualised compute and storage resources used by the VNFCs of the VNF instance.\n",
- "type": "array",
- "items": {
- "description": "This type represents the information on virtualised compute and storage resources used by a VNFC in a VNF instance. This feature addresses the following capabilities: NFV Architecture support for VNFs which follow cloud-native design principles. Enhance NFV-MANO capabilities to support container technologies. Enhance NFV-MANO capabilities for container management and orchestration. Enhance information model for containerized VNFs both using bare metal or nested virtualization technologies.\nNOTE 1: ETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on TOSCA specifications. NOTE 2: A VNFC CP is \"connected to\" an external CP if the VNFC CP is connected to an internal VL that exposes an external CP. A VNFC CP is \"exposed as\" an external CP if it is connected directly to an external VL. NOTE 3: The information can be omitted because it is already available as part of the external CP information. NOTE 4: Cardinality greater than 1 is only applicable for specific cases where more than one network attachment definition resource is needed to fulfil the connectivity requirements of the internal CP, e.g. to build a link redundant mated pair in SR-IOV cases. NOTE 5: When more than one \"netAttDefResourceId\" is indicated, all shall belong to the same namespace.\n",
- "type": "object",
- "required": ["id", "vduId", "computeResource"],
- "properties": {
- "id": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vduId": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "computeResource": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes instance the vimLevelResourceType is the type of resource, as would correspond to the kind field if the resource is declared in its own Kubernetes manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the claimName field in the Kubernetes manifest, or a compound name built by Kubernetes if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the metadata.name field in Kubernetes manifest. \n",
- "type": "object",
- "required": ["resourceId"],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
- "type": "string"
- },
- "vimLevelAdditionalResourceInfo": {
- "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
- "type": "object",
- "properties": {
- "hostName": {
- "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "persistentVolume": {
- "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "containerNamespace": {
- "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
- "type": "string"
- }
- }
- },
- "storageResourceIds": {
- "description": "References to the VirtualStorage resources or references to Storage MCIOs. The value refers to a VirtualStorageResourceInfo item in the VnfInstance.\n",
- "type": "array",
- "items": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- }
- },
- "reservationId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfcCpInfo": {
- "description": "CPs of the VNFC instance. Shall be present when that particular CP of the VNFC instance is exposed as an external CP of the VNF instance or is connected to an external CP of the VNF instance.See note 2. May be present otherwise.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": ["id", "cpdId"],
- "properties": {
- "id": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "cpdId": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "vnfExtCpId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "cpProtocolInfo": {
- "description": "Network protocol information for this CP. May be omitted if the VNFC CP is exposed as an external CP. See note 3.\n",
- "type": "array",
- "items": {
- "description": "This type describes the protocol layer(s) that a CP or SAP uses together with protocol-related information, like addresses. It shall comply with the provisions defined in Table 6.5.3.58-1. NOTE: This attribute allows to signal the addition of further types of layer and protocol in future versions of the present document in a backwards-compatible way. In the current version of the present document, only IP over Ethernet is supported.\n",
- "type": "object",
- "required": ["layerProtocol", "ipOverEthernet"],
- "properties": {
- "layerProtocol": {
- "description": "The identifier of layer(s) and protocol(s) associated to the network address information. Permitted values: - IP_OVER_ETHERNET\n - IP_FOR_VIRTUAL_CP\nSee note.\n",
- "type": "string",
- "enum": ["IP_OVER_ETHERNET", "IP_FOR_VIRTUAL_CP"]
- },
- "ipOverEthernet": {
- "description": "This type represents information about a network address that has been assigned.\nNOTE 1: At least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2: Exactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3: If the Cp instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4: Depending on the NFVI networking infrastructure, the \"segmentationId\" may indicate the actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header of the packets or it may be an identifier used between the application and the NFVI networking infrastructure to identify the network sub-interface of the trunk port in question. In the latter case the NFVI infrastructure will map this local \"segmentationId\" to whatever \"segmentationId\" is actually used by the NFVI's transport technology.\n",
- "type": "object",
- "anyOf": [{
- "required": ["macAddress"]
- }, {
- "required": ["ipAddresses"]
- }],
- "properties": {
- "macAddress": {
- "description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
- "type": "string",
- "format": "MAC"
- },
- "segmentationId": {
- "description": "Identification of the network segment to which the Cp instance connects to. See note 3 and note 4.\n",
- "type": "string"
- },
- "ipAddresses": {
- "description": "Addresses assigned to the CP instance. Each entry represents IP addresses assigned by fixed or dynamic IP address assignment per subnet. See note 1.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": ["type"],
- "oneOf": [{
- "required": ["addresses"]
- }, {
- "required": ["addressRange"]
- }],
- "properties": {
- "type": {
- "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
- "type": "string",
- "enum": ["IPV4", "IPV6"]
- },
- "addresses": {
- "description": "Fixed addresses assigned (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
- "type": "array",
- "items": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- },
- "isDynamic": {
- "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
- "type": "boolean"
- },
- "addressRange": {
- "description": "An IP address range used, e.g., in case of egress connections. Exactly one of \"addresses\" or \"addressRange\" shall be present. See note 2.\n",
- "type": "object",
- "required": ["minAddress", "maxAddress"],
- "properties": {
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- },
- "subnetId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- }
- },
- "type": {
- "description": "The type of the IP addresses\n",
- "type": "string",
- "enum": ["PV4", "PV6"]
- },
- "addresses": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "isDynamic": {
- "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
- "type": "boolean"
- },
- "addressRange": {
- "description": "An IP address range used, e.g. in case of egress connections. See note.\n",
- "type": "object",
- "required": ["minAddress", "maxAddress"],
- "properties": {
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- },
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "subnetId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- },
- "virtualCpAddress": {
- "description": "This type represents information about a network address that has been assigned to a virtual CP.\n",
- "type": "object",
- "required": ["type"],
- "properties": {
- "type": {
- "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
- "type": "string",
- "enum": ["IPV4", "IPV6"]
- },
- "loadBalancerIp": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- }
- }
- }
- },
- "parentCpId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "vnfLinkPortId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "netAttDefResourceId": {
- "description": "Identifier of the \"NetAttDefResourceInfo\" structure that provides the specification of the interface to attach the connection point to a secondary container cluster network. See notes 4 and 5. It shall be present if the internal CP is associated to a VNFC realized by one or a set of OS containers and is connected to a secondary container cluster network. It shall not be present otherwise.\n",
- "type": "array",
- "items": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- }
- },
- "metadata": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- }
- },
- "metadata": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
+ "resourceProviderId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "type": "string"
+ },
+ "vimLevelAdditionalResourceInfo": {
+ "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
+ "type": "object",
+ "properties": {
+ "hostName": {
+ "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "persistentVolume": {
+ "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
}
+ }
+ },
+ "containerNamespace": {
+ "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise. \n",
+ "type": "string"
+ }
+ }
+ },
+ "associatedExtCpId": {
+ "description": "Identifier of the external CP of the VNF associated to this network attachment definition resource. Shall be present when the network attachment definition resource is used for external connectivity by the VNF\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ }
+ },
+ "associatedVnfcCpId": {
+ "description": "Identifier of the VNFC CP of the VNF associated to this network attachment definition resource. May be present when the network attachment definition resource is used for internal connectivity by the VNF.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "extManagedMultisiteVirtualLinkId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "monitoringParameters": {
+ "description": "Performance metrics tracked by the VNFM (e.g. for auto-scaling purposes) as identified by the VNF provider in the VNFD.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents a monitoring parameter that is tracked by the VNFM, for example, for auto-scaling purposes. It shall comply with the provisions defined in Table 6.5.3.69-1.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "performanceMetric"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "name": {
+ "description": "Human readable name of the monitoring parameter, as defined in the VNFD.\n",
+ "type": "string"
+ },
+ "performanceMetric": {
+ "description": "Performance metric that is monitored. This attribute shall contain the related \"Measurement Name\" value as defined in clause 7.2 of ETSI GS NFV-IFA 027.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "localizationLanguage": {
+ "description": "Information about localization language of the VNF (includes e.g. strings in the VNFD). The localization languages supported by a VNF can be declared in the VNFD, and localization language selection can take place at instantiation time. The value shall comply with the format defined in IETF RFC 5646.\n",
+ "type": "string"
+ },
+ "vnfcResourceInfo": {
+ "description": "Information about the virtualised compute and storage resources used by the VNFCs of the VNF instance.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the information on virtualised compute and storage resources used by a VNFC in a VNF instance. This feature addresses the following capabilities: • NFV Architecture support for VNFs which follow “cloud-native” design principles. • Enhance NFV-MANO capabilities to support container technologies. • Enhance NFV-MANO capabilities for container management and orchestration. • Enhance information model for containerized VNFs both using bare metal or nested virtualization technologies.\nNOTE 1: ETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on TOSCA specifications. NOTE 2: A VNFC CP is \"connected to\" an external CP if the VNFC CP is connected to an internal VL that exposes an external CP. A VNFC CP is \"exposed as\" an external CP if it is connected directly to an external VL. NOTE 3: The information can be omitted because it is already available as part of the external CP information. NOTE 4: Cardinality greater than 1 is only applicable for specific cases where more than one network attachment definition resource is needed to fulfil the connectivity requirements of the internal CP, e.g. to build a link redundant mated pair in SR-IOV cases. NOTE 5: When more than one \"netAttDefResourceId\" is indicated, all shall belong to the same namespace.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "vduId",
+ "computeResource"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vduId": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
+ "type": "string"
+ },
+ "computeResource": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would correspond to the ‘kind’ field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the ‘claimName’ field in the Kubernetes® manifest, or a compound name built by Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the ‘metadata.name’ field in Kubernetes® manifest. \n",
+ "type": "object",
+ "required": [
+ "resourceId"
+ ],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceProviderId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "type": "string"
+ },
+ "vimLevelAdditionalResourceInfo": {
+ "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
+ "type": "object",
+ "properties": {
+ "hostName": {
+ "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
},
- "vnfVirtualLinkResourceInfo": {
- "description": "Information about the virtualised network resources used by the VLs of the VNF instance. See note 5.\n",
- "type": "array",
- "items": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by an internal VL instance in a VNF instance.\n",
- "type": "object",
- "required": ["id", "vnfVirtualLinkDescId", "networkResource"],
- "properties": {
- "id": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfVirtualLinkDescId": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "networkResource": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes instance the vimLevelResourceType is the type of resource, as would correspond to the kind field if the resource is declared in its own Kubernetes manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the claimName field in the Kubernetes manifest, or a compound name built by Kubernetes if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the metadata.name field in Kubernetes manifest. \n",
- "type": "object",
- "required": ["resourceId"],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
- "type": "string"
- },
- "vimLevelAdditionalResourceInfo": {
- "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
- "type": "object",
- "properties": {
- "hostName": {
- "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "persistentVolume": {
- "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "containerNamespace": {
- "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
- "type": "string"
- }
- }
- },
- "reservationId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfLinkPorts": {
- "description": "Links ports of this VL. Shall be present when the linkPort is used for external connectivity by the VNF (refer to VnfLinkPortInfo). May be present otherwise.\n",
+ "persistentVolume": {
+ "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ },
+ "containerNamespace": {
+ "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise. \n",
+ "type": "string"
+ }
+ }
+ },
+ "storageResourceIds": {
+ "description": "References to the VirtualStorage resources or references to Storage MCIOs. The value refers to a VirtualStorageResourceInfo item in the VnfInstance.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ }
+ },
+ "reservationId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfcCpInfo": {
+ "description": "CPs of the VNFC instance. Shall be present when that particular CP of the VNFC instance is exposed as an external CP of the VNF instance or is connected to an external CP of the VNF instance.See note 2. May be present otherwise.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": [
+ "id",
+ "cpdId"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "cpdId": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
+ "type": "string"
+ },
+ "vnfExtCpId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "cpProtocolInfo": {
+ "description": "Network protocol information for this CP. May be omitted if the VNFC CP is exposed as an external CP. See note 3.\n",
+ "type": "array",
+ "items": {
+ "description": "This type describes the protocol layer(s) that a CP or SAP uses together with protocol-related information, like addresses. It shall comply with the provisions defined in Table 6.5.3.58-1. NOTE: This attribute allows to signal the addition of further types of layer and protocol in future versions of the present document in a backwards-compatible way. In the current version of the present document, only IP over Ethernet is supported.\n",
+ "type": "object",
+ "required": [
+ "layerProtocol",
+ "ipOverEthernet"
+ ],
+ "properties": {
+ "layerProtocol": {
+ "description": "The identifier of layer(s) and protocol(s) associated to the network address information. Permitted values:\n - IP_OVER_ETHERNET\n - IP_FOR_VIRTUAL_CP\nSee note.\n",
+ "type": "string",
+ "enum": [
+ "IP_OVER_ETHERNET",
+ "IP_FOR_VIRTUAL_CP"
+ ]
+ },
+ "ipOverEthernet": {
+ "description": "This type represents information about a network address that has been assigned.\nNOTE 1: At least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2: Exactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3: If the Cp instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4: Depending on the NFVI networking infrastructure, the \"segmentationId\" may indicate the actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header of the packets or it may be an identifier used between the application and the NFVI networking infrastructure to identify the network sub-interface of the trunk port in question. In the latter case the NFVI infrastructure will map this local \"segmentationId\" to whatever \"segmentationId\" is actually used by the NFVI's transport technology.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "required": [
+ "macAddress"
+ ]
+ },
+ {
+ "required": [
+ "ipAddresses"
+ ]
+ }
+ ],
+ "properties": {
+ "macAddress": {
+ "description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
+ "type": "string",
+ "format": "MAC"
+ },
+ "segmentationId": {
+ "description": "Identification of the network segment to which the Cp instance connects to. See note 3 and note 4.\n",
+ "type": "string"
+ },
+ "ipAddresses": {
+ "description": "Addresses assigned to the CP instance. Each entry represents IP addresses assigned by fixed or dynamic IP address assignment per subnet. See note 1.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": [
+ "type"
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "addresses"
+ ]
+ },
+ {
+ "required": [
+ "addressRange"
+ ]
+ }
+ ],
+ "properties": {
+ "type": {
+ "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
+ },
+ "addresses": {
+ "description": "Fixed addresses assigned (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
"type": "array",
"items": {
- "type": "object",
- "description": "This type represents a link port of an internal VL of a VNF. It shall comply with the provisions defined in table 6.5.3.64-1.\nNOTE 1: Either cpInstanceId with cpInstanceType set to \"EXT_CP\" or any combination of cpInstanceId with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId (i.e. one or both of them) shall be present for a VnfLinkPortInfo. In case both cpInstanceId with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId are present, the two different CP instances share the linkport.\n",
- "required": ["id", "resourceHandle"],
- "properties": {
- "id": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "resourceHandle": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes instance the vimLevelResourceType is the type of resource, as would correspond to the kind field if the resource is declared in its own Kubernetes manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the claimName field in the Kubernetes manifest, or a compound name built by Kubernetes if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the metadata.name field in Kubernetes manifest. \n",
- "type": "object",
- "required": ["resourceId"],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
- "type": "string"
- },
- "vimLevelAdditionalResourceInfo": {
- "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
- "type": "object",
- "properties": {
- "hostName": {
- "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "persistentVolume": {
- "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "containerNamespace": {
- "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
- "type": "string"
- }
- }
- },
- "cpInstanceId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "cpInstanceType": {
- "description": "Type of the CP instance that is identified by cpInstanceId. Shall be present if \"cpInstanceId\" is present, and shall be absent otherwise. Permitted values: * VNFC_CP: The link port is connected to a VNFC CP * EXT_CP: The link port is associated to an external CP. See note 1.\n",
- "type": "string",
- "enum": ["VNFC_CP", "EXT_CP"]
- },
- "vipCpInstanceId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "trunkResourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- }
- }
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
}
- },
- "metadata": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- }
- },
- "virtualStorageResourceInfo": {
- "description": "Information on the virtualised storage resource(s) used as storage for the VNF instance.\n",
- "type": "array",
- "items": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance.\n",
- "type": "object",
- "required": ["id", "virtualStorageDescId", "storageResource"],
- "properties": {
- "id": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "virtualStorageDescId": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "storageResource": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes instance the vimLevelResourceType is the type of resource, as would correspond to the kind field if the resource is declared in its own Kubernetes manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the claimName field in the Kubernetes manifest, or a compound name built by Kubernetes if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the metadata.name field in Kubernetes manifest. \n",
+ },
+ "isDynamic": {
+ "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
+ "type": "boolean"
+ },
+ "addressRange": {
+ "description": "An IP address range used, e.g., in case of egress connections. Exactly one of \"addresses\" or \"addressRange\" shall be present. See note 2.\n",
"type": "object",
- "required": ["resourceId"],
+ "required": [
+ "minAddress",
+ "maxAddress"
+ ],
"properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
- "type": "string"
- },
- "vimLevelAdditionalResourceInfo": {
- "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
- "type": "object",
- "properties": {
- "hostName": {
- "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "persistentVolume": {
- "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "containerNamespace": {
- "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
- "type": "string"
- }
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ }
}
- },
- "reservationId": {
- "description": "An identifier with the intention of being globally unique.\n",
+ },
+ "subnetId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
"type": "string"
- },
- "metadata": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
+ }
}
- }
- }
- },
- "mcioInfo": {
- "description": "Information on the MCIO(s) representing VNFC instance(s) realized by one or a set of OS containers and created from the same VDU for the VNF instance.\n",
- "type": "array",
- "items": {
- "description": "This type provides information about an MCIO representing the set of VNFC instances realized by one or a set of OS containers which have been created based on the same VDU.\nNOTE 1 The type of MCIO as specified in the declarative descriptor of the MCIO, and that can be read from the CISM. EXAMPLE: In case of MCIOs managed by Kubernetes, the type of MCIO corresponds to the kind property of the declarative descriptor. NOTE 2 If the attribute additionalInfo is present, it may contain runtime information on the actual and desired state of the MCIO(s). NOTE 3 When the container infrastructure service is a Kubernetes instance, the mcioId is the combined values from the kind and name fields of the Kubernetes resource object, separated by a slash. Example: \"Deployment/abcd\". NOTE 4 When the container infrastructure service is a Kubernetes instance, the mcioName is the name field of the resource object.",
- "type": "object",
- "required": ["mcioId", "mcioName", "mcioNamespace", "vduId", "cismId", "mcioType", "desiredInstances", "availableInstances"],
- "properties": {
- "mcioId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "mcioName": {
- "description": "Human readable name of this MCIO. See note 4.\n",
- "type": "string"
- },
- "mcioNamespace": {
- "description": "Namespace of this MCIO.\n",
- "type": "string"
- },
- "vduId": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "cismId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "mcioType": {
- "description": "The type of MCIO. Specific values, their semantics and associated MCIO types are defined in clause 6.5.4.13. Additional values are also permitted. See note 1.\n",
- "type": "string"
- },
- "desiredInstances": {
- "description": "Number of desired MCIO instances.\n",
- "type": "integer"
- },
- "availableInstances": {
- "description": "Number of available MCIO instances\n",
- "type": "integer"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
+ }
+ },
+ "type": {
+ "description": "The type of the IP addresses\n",
+ "type": "string",
+ "enum": [
+ "PV4",
+ "PV6"
+ ]
+ },
+ "addresses": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "isDynamic": {
+ "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
+ "type": "boolean"
+ },
+ "addressRange": {
+ "description": "An IP address range used, e.g. in case of egress connections. See note.\n",
+ "type": "object",
+ "required": [
+ "minAddress",
+ "maxAddress"
+ ],
+ "properties": {
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
}
+ }
+ },
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "subnetId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
}
+ }
+ },
+ "virtualCpAddress": {
+ "description": "This type represents information about a network address that has been assigned to a virtual CP.\n",
+ "type": "object",
+ "required": [
+ "type"
+ ],
+ "properties": {
+ "type": {
+ "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
+ },
+ "loadBalancerIp": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.",
+ "type": "string"
+ }
+ }
}
+ }
+ }
+ },
+ "parentCpId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "vnfLinkPortId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "netAttDefResourceId": {
+ "description": "Identifier of the \"NetAttDefResourceInfo\" structure that provides the specification of the interface to attach the connection point to a secondary container cluster network. See notes 4 and 5. It shall be present if the internal CP is associated to a VNFC realized by one or a set of OS containers and is connected to a secondary container cluster network. It shall not be present otherwise.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
}
+ },
+ "metadata": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
}
+ }
},
"metadata": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- },
- "extensions": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
}
+ }
}
- },
- "vnfcSnapshots": {
- "description": "Information about VNFC Snapshots constituting this VNF Snapshot.\n",
+ },
+ "vnfVirtualLinkResourceInfo": {
+ "description": "Information about the virtualised network resources used by the VLs of the VNF instance. See note 5.\n",
"type": "array",
"items": {
- "description": "This type represents a VNFC Snapshot. It shall comply with the provisions defined in table 6.5.3.77-1. NOTE 1: The identifier of the compute snapshot resource is assigned during creation of a VNFC Snapshot being returned from the VIM as output data in the response message of the individual resource operations. This attribute shall only be present for a VNFC snapshot that has been newly created by the VNFM as a result of the \"Create VNF snapshot task\". NOTE 2: The identifier of the storage snapshot resource is assigned during creation of a VNFC snapshot being returned from the VIM as output data in the response message of the individual resource operations. This attribute shall only be present for a VNFC snapshot with an associated storage resource and that has been newly created by the VNFM as a result of the \"Create VNF snapshot task\".\n",
- "type": "object",
- "required": ["id", "vnfcInstanceId", "triggeredAt", "createdAt", "vnfcInfoId"],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by an internal VL instance in a VNF instance.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "vnfVirtualLinkDescId",
+ "networkResource"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfVirtualLinkDescId": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
+ "type": "string"
+ },
+ "networkResource": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would correspond to the ‘kind’ field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the ‘claimName’ field in the Kubernetes® manifest, or a compound name built by Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the ‘metadata.name’ field in Kubernetes® manifest. \n",
+ "type": "object",
+ "required": [
+ "resourceId"
+ ],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
},
- "vnfcInstanceId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
+ "resourceProviderId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
},
- "creationStartedAt": {
- "description": "Date-time stamp. Representation: String formatted according toas defined by the date-time production in IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
+ "resourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
},
- "creationFinishedAt": {
- "description": "Date-time stamp. Representation: String formatted according toas defined by the date-time production in IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
+ "vimLevelResourceType": {
+ "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "type": "string"
},
- "vnfcResourceInfoId": {
+ "vimLevelAdditionalResourceInfo": {
+ "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
+ "type": "object",
+ "properties": {
+ "hostName": {
+ "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "persistentVolume": {
+ "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ },
+ "containerNamespace": {
+ "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise. \n",
+ "type": "string"
+ }
+ }
+ },
+ "reservationId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfLinkPorts": {
+ "description": "Links ports of this VL. Shall be present when the linkPort is used for external connectivity by the VNF (refer to VnfLinkPortInfo). May be present otherwise.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "description": "This type represents a link port of an internal VL of a VNF. It shall comply with the provisions defined in table 6.5.3.64-1.\nNOTE 1: Either cpInstanceId with cpInstanceType set to \"EXT_CP\" or any combination of cpInstanceId with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId (i.e. one or both of them) shall be present for a VnfLinkPortInfo. In case both cpInstanceId with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId are present, the two different CP instances share the linkport.\n",
+ "required": [
+ "id",
+ "resourceHandle"
+ ],
+ "properties": {
+ "id": {
"description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
"type": "string"
- },
- "computeSnapshotResource": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes instance the vimLevelResourceType is the type of resource, as would correspond to the kind field if the resource is declared in its own Kubernetes manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the claimName field in the Kubernetes manifest, or a compound name built by Kubernetes if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the metadata.name field in Kubernetes manifest. \n",
+ },
+ "resourceHandle": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would correspond to the ‘kind’ field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the ‘claimName’ field in the Kubernetes® manifest, or a compound name built by Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the ‘metadata.name’ field in Kubernetes® manifest. \n",
"type": "object",
- "required": ["resourceId"],
+ "required": [
+ "resourceId"
+ ],
"properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceProviderId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "type": "string"
+ },
+ "vimLevelAdditionalResourceInfo": {
+ "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
+ "type": "object",
+ "properties": {
+ "hostName": {
+ "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note. \n",
"type": "string"
- },
- "vimLevelAdditionalResourceInfo": {
- "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
- "type": "object",
- "properties": {
- "hostName": {
- "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "persistentVolume": {
- "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "containerNamespace": {
- "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
+ },
+ "persistentVolume": {
+ "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note. \n",
"type": "string"
+ },
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
}
+ },
+ "containerNamespace": {
+ "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise. \n",
+ "type": "string"
+ }
}
+ },
+ "cpInstanceId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "cpInstanceType": {
+ "description": "Type of the CP instance that is identified by cpInstanceId. Shall be present if \"cpInstanceId\" is present, and shall be absent otherwise. Permitted values: * VNFC_CP: The link port is connected to a VNFC CP * EXT_CP: The link port is associated to an external CP. See note 1.\n",
+ "type": "string",
+ "enum": [
+ "VNFC_CP",
+ "EXT_CP"
+ ]
+ },
+ "vipCpInstanceId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "trunkResourceId": {
+ "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "metadata": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ }
+ },
+ "virtualStorageResourceInfo": {
+ "description": "Information on the virtualised storage resource(s) used as storage for the VNF instance.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "virtualStorageDescId",
+ "storageResource"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "virtualStorageDescId": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "storageResource": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would correspond to the ‘kind’ field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the ‘claimName’ field in the Kubernetes® manifest, or a compound name built by Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the ‘metadata.name’ field in Kubernetes® manifest. \n",
+ "type": "object",
+ "required": [
+ "resourceId"
+ ],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
},
- "storageSnapshotResources": {
- "description": "Reference to the \"VirtualStorageResourceInfo\" structure in the \"VnfInstance\" structure that represents the virtual storage resource. See note 2.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": ["storageResourceId"],
- "properties": {
- "storageResourceId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "storageSnapshotResources": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes instance the vimLevelResourceType is the type of resource, as would correspond to the kind field if the resource is declared in its own Kubernetes manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the claimName field in the Kubernetes manifest, or a compound name built by Kubernetes if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the metadata.name field in Kubernetes manifest. \n",
- "type": "object",
- "required": ["resourceId"],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
- "type": "string"
- },
- "vimLevelAdditionalResourceInfo": {
- "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
- "type": "object",
- "properties": {
- "hostName": {
- "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "persistentVolume": {
- "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "containerNamespace": {
- "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
- "type": "string"
- }
- }
- }
- }
+ "resourceProviderId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "type": "string"
+ },
+ "vimLevelAdditionalResourceInfo": {
+ "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
+ "type": "object",
+ "properties": {
+ "hostName": {
+ "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "persistentVolume": {
+ "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
}
+ }
},
- "userDefinedData": {
+ "containerNamespace": {
+ "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise. \n",
+ "type": "string"
+ }
+ }
+ },
+ "reservationId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "metadata": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ }
+ },
+ "mcioInfo": {
+ "description": "Information on the MCIO(s) representing VNFC instance(s) realized by one or a set of OS containers and created from the same VDU for the VNF instance.\n",
+ "type": "array",
+ "items": {
+ "description": "This type provides information about an MCIO representing the set of VNFC instances realized by one or a set of OS containers which have been created based on the same VDU.\nNOTE 1 The type of MCIO as specified in the declarative descriptor of the MCIO, and that can be read from the CISM. EXAMPLE: In case of MCIOs managed by Kubernetes, the type of MCIO corresponds to the “kind” property of the declarative descriptor. NOTE 2 If the attribute additionalInfo is present, it may contain runtime information on the actual and desired state of the MCIO(s). NOTE 3 When the container infrastructure service is a Kubernetes® instance, the mcioId is the combined values from the kind and name fields of the Kubernetes® resource object, separated by a slash. Example: \"Deployment/abcd\". NOTE 4 When the container infrastructure service is a Kubernetes® instance, the mcioName is the name field of the resource object.",
+ "type": "object",
+ "required": [
+ "mcioId",
+ "mcioName",
+ "mcioNamespace",
+ "vduId",
+ "cismId",
+ "mcioType",
+ "desiredInstances",
+ "availableInstances"
+ ],
+ "properties": {
+ "mcioId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "mcioName": {
+ "description": "Human readable name of this MCIO. See note 4. \n",
+ "type": "string"
+ },
+ "mcioNamespace": {
+ "description": "Namespace of this MCIO.\n",
+ "type": "string"
+ },
+ "vduId": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
+ "type": "string"
+ },
+ "cismId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "mcioType": {
+ "description": "The type of MCIO. Specific values, their semantics and associated MCIO types are defined in clause 6.5.4.13. Additional values are also permitted. See note 1.\n",
+ "type": "string"
+ },
+ "desiredInstances": {
+ "description": "Number of desired MCIO instances.\n",
+ "type": "integer"
+ },
+ "availableInstances": {
+ "description": "Number of available MCIO instances\n",
+ "type": "integer"
+ },
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ }
+ }
+ }
+ },
+ "metadata": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ },
+ "extensions": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ },
+ "vnfcSnapshots": {
+ "description": "Information about VNFC Snapshots constituting this VNF Snapshot.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents a VNFC Snapshot. It shall comply with the provisions defined in table 6.5.3.77-1. NOTE 1: The identifier of the compute snapshot resource is assigned during creation of a VNFC Snapshot being returned from the VIM as output data in the response message of the individual resource operations. This attribute shall only be present for a VNFC snapshot that has been newly created by the VNFM as a result of the \"Create VNF snapshot task\". NOTE 2: The identifier of the storage snapshot resource is assigned during creation of a VNFC snapshot being returned from the VIM as output data in the response message of the individual resource operations. This attribute shall only be present for a VNFC snapshot with an associated storage resource and that has been newly created by the VNFM as a result of the \"Create VNF snapshot task\".\n",
+ "type": "object",
+ "required": [
+ "id",
+ "vnfcInstanceId",
+ "triggeredAt",
+ "createdAt",
+ "vnfcInfoId"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfcInstanceId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "creationStartedAt": {
+ "description": "Date-time stamp. Representation: String formatted according toas defined by the date-time production in IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "creationFinishedAt": {
+ "description": "Date-time stamp. Representation: String formatted according toas defined by the date-time production in IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "vnfcResourceInfoId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "computeSnapshotResource": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would correspond to the ‘kind’ field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the ‘claimName’ field in the Kubernetes® manifest, or a compound name built by Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the ‘metadata.name’ field in Kubernetes® manifest. \n",
+ "type": "object",
+ "required": [
+ "resourceId"
+ ],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceProviderId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "type": "string"
+ },
+ "vimLevelAdditionalResourceInfo": {
+ "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
+ "type": "object",
+ "properties": {
+ "hostName": {
+ "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "persistentVolume": {
+ "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ },
+ "containerNamespace": {
+ "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise. \n",
+ "type": "string"
+ }
+ }
+ },
+ "storageSnapshotResources": {
+ "description": "Reference to the \"VirtualStorageResourceInfo\" structure in the \"VnfInstance\" structure that represents the virtual storage resource. See note 2.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": [
+ "storageResourceId"
+ ],
+ "properties": {
+ "storageResourceId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "storageSnapshotResources": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would correspond to the ‘kind’ field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the ‘claimName’ field in the Kubernetes® manifest, or a compound name built by Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the ‘metadata.name’ field in Kubernetes® manifest. \n",
+ "type": "object",
+ "required": [
+ "resourceId"
+ ],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceProviderId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "type": "string"
+ },
+ "vimLevelAdditionalResourceInfo": {
+ "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
+ "type": "object",
+ "properties": {
+ "hostName": {
+ "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "persistentVolume": {
+ "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "additionalInfo": {
"description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
"type": "object"
+ }
}
+ },
+ "containerNamespace": {
+ "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise. \n",
+ "type": "string"
+ }
}
+ }
}
+ }
},
"userDefinedData": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
}
+ }
}
- },
- "_links": {
- "description": "Links to resources related to this resource.\n",
+ },
+ "userDefinedData": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ },
+ "_links": {
+ "description": "Links to resources related to this resource.\n",
+ "type": "object",
+ "required": [
+ "self"
+ ],
+ "properties": {
+ "self": {
+ "description": "This type represents a link to a resource.\n",
"type": "object",
- "required": ["self"],
+ "required": [
+ "href"
+ ],
"properties": {
- "self": {
- "description": "This type represents a link to a resource.\n",
- "type": "object",
- "required": ["href"],
- "properties": {
- "href": {
- "description": "URI of a resource referenced from a notification. Should be an absolute URI (i.e. a URI that contains {apiRoot}), however, may be a relative URI (i.e. a URI where the {apiRoot} part is omitted) if the {apiRoot} information is not available.\n",
- "type": "string",
- "format": "url"
- }
- }
- }
+ "href": {
+ "description": "URI of a resource referenced from a notification. Should be an absolute URI (i.e. a URI that contains {apiRoot}), however, may be a relative URI (i.e. a URI where the {apiRoot} part is omitted) if the {apiRoot} information is not available.\n",
+ "type": "string",
+ "format": "url"
+ }
}
+ }
}
+ }
}
-}
\ No newline at end of file
+ }
\ No newline at end of file
diff --git a/SOL005/NSLifecycleManagement-API/schemas/VnfSnapshotsInfo.schema.json b/SOL005/NSLifecycleManagement-API/schemas/VnfSnapshotsInfo.schema.json
index 986e20101d2be0e26fba70fc7dd5ca389546ebcc..8042e3eb3e22b22f28c9c7d1ddfd1e74e8cafa97 100644
--- a/SOL005/NSLifecycleManagement-API/schemas/VnfSnapshotsInfo.schema.json
+++ b/SOL005/NSLifecycleManagement-API/schemas/VnfSnapshotsInfo.schema.json
@@ -1,2250 +1,2645 @@
{
"type": "array",
"items": {
- "description": "This type represents an \"Individual VNF snapshot\" resource. The \"id\" attributed is used by the NFVO to index and\nidentify the VNF snapshots information resources that are accessible via the NFVO. The identifier is still\ngenerated by the VNFM and copied into the present \"VnfSnapshotInfo\" representing the \"Individual VNF snapshot\"\nresource hold by the NFVO.\n",
- "type": "object",
- "required": ["id"],
- "properties": {
+ "description": "This type represents an \"Individual VNF snapshot\" resource. The \"id\" attributed is used by the NFVO to index and\nidentify the VNF snapshots information resources that are accessible via the NFVO. The identifier is still\ngenerated by the VNFM and copied into the present \"VnfSnapshotInfo\" representing the \"Individual VNF snapshot\"\nresource hold by the NFVO.\n",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfSnapshotPkgId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfSnapshot": {
+ "description": "This type represents a VNF Snapshot. It shall comply with the provisions defined in table 6.5.2.18-1.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "vnfInstanceId",
+ "triggeredAt",
+ "createdAt",
+ "vnfdId",
+ "vnfInstance",
+ "vnfcSnapshots"
+ ],
+ "properties": {
"id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
},
- "vnfSnapshotPkgId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
+ "vnfInstanceId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
},
- "vnfSnapshot": {
- "description": "This type represents a VNF Snapshot. It shall comply with the provisions defined in table 6.5.2.18-1.\n",
- "type": "object",
- "required": ["id", "vnfInstanceId", "triggeredAt", "createdAt", "vnfdId", "vnfInstance", "vnfcSnapshots"],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfInstanceId": {
- "description": "An identifier with the intention of being globally unique.\n",
+ "creationStartedAt": {
+ "description": "Date-time stamp. Representation: String formatted according toas defined by the date-time production in IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "creationFinishedAt": {
+ "description": "Date-time stamp. Representation: String formatted according toas defined by the date-time production in IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfInstance": {
+ "description": "This type represents a VNF instance. It shall comply with the provisions defined in table 6.5.3.57-1.\nNOTE: Clause B.3.2 of ETSI GS NFV-SOL 003 provides examples illustrating the relationship among the \n different run-time data types (CP, VL and link ports) used to represent the connectivity \n of a VNF.\n\nNOTE 1: Modifying the value of this attribute shall not be performed when conflicts exist between the \n previous and the newly referred VNF package, i.e. when the new VNFD is changed with respect to \n the previous VNFD in other aspects than merely referencing to other VNF software images. \n In order to avoid misalignment of the VnfInstance with the current VNF's on-boarded VNF Package, \n the values of attributes in the VnfInstance that have corresponding attributes in the VNFD shall \n be kept in sync with the values in the VNFD.\nNOTE 2: ETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on TOSCA specifications. NOTE 3: VNF configurable properties are sometimes also referred to as configuration parameters applicable \n to a VNF. Some of these are set prior to instantiation and cannot be modified if the VNF is instantiated, \n some are set prior to instantiation (are part of initial configuration) and can be modified later, \n and others can be set only after instantiation. The applicability of certain configuration may depend \n on the VNF and the required operation of the VNF at a certain point in time.\nNOTE 4: It is possible to have several ExtManagedVirtualLinkInfo for the same VNF internal VL in case of a \n multi-site VNF spanning several VIMs. The set of ExtManagedVirtualLinkInfo corresponding to the same \n VNF internal VL shall indicate so by referencing to the same VnfVirtualLinkDesc and externally-managed \n multi-site VL instance (refer to clause 6.5.3.59).\nNOTE 5: Even though externally-managed internal VLs are also used for VNF-internal connectivity, they shall not \n be listed in the \"vnfVirtualLinkResourceInfo\" attribute as this would be redundant.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "vnfdId",
+ "vnfProvider",
+ "vnfProductName",
+ "vnfSoftwareVersion",
+ "vnfdVersion",
+ "vnfPkgId",
+ "instantiationState"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfInstanceName": {
+ "description": "Name of the VNF instance. Modifications to this attribute can be requested using the \"ModifyVnfInfoData\" structure.\n",
+ "type": "string"
+ },
+ "vnfInstanceDescription": {
+ "description": "Human-readable description of the VNF instance. Modifications to this attribute can be requested using the \"ModifyVnfInfoData\" structure.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfProvider": {
+ "description": "Provider of the VNF and the VNFD. The value is copied from the VNFD.\n",
+ "type": "string"
+ },
+ "vnfProductName": {
+ "description": "Name to identify the VNF Product. The value is copied from the VNFD.\n",
+ "type": "string"
+ },
+ "vnfSoftwareVersion": {
+ "description": "A Version. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vnfdVersion": {
+ "description": "A Version. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "versionDependency": {
+ "description": "Describes version dependencies currently valid for the VNF instance. Identifies versions of descriptors of other constituents in the NSD upon which the VNF depends. The dependencies may be described for the VNFD referenced in this VnfInfo with \"vnfdId\" and for VNFDs with the same \"vnfdExtInvariantId\". There shall not be more than one \"versionDependency\" present with the same dependentConstituentId.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the information related to all dependencies that an NSD constituent has on the versions of other NSD constituents. It shall comply with the provisions defined in table 6.5.3.112-1.\n",
+ "type": "object",
+ "required": [
+ "dependentConstituentId"
+ ],
+ "properties": {
+ "dependentConstituentId": {
+ "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
"type": "string"
+ },
+ "versionDependencyStatement": {
+ "description": "Identifies one or multiple versions of an NSD constituents upon which the dependent constituent identified by dependentConstituentId has a dependency. Cardinality 0 is used to remove an existing version dependency in a profile.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the information related to one or more VNF, NS or PNF descriptor identifiers which describe one single dependency. When more than one descriptor is indicated, they correspond to different versions of the same VNF, NS or PNF and they represent alternatives to fulfil the dependency. It shall comply with the provisions defined in table 6.5.3.113-1.\n",
+ "type": "object",
+ "required": [
+ "descriptorId"
+ ],
+ "properties": {
+ "descriptorId": {
+ "description": "Identifies a VNFD, NSD or PNFD upon which the entity using this data type depends. When more than one descriptor is indicated, they shall correspond to versions of the same VNF, NS or PNF and they represent alternatives, i.e. the presence of one of them fulfills the dependency.",
+ "type": "array",
+ "items": {
+ "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
+ "type": "string"
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ },
+ "vnfPkgId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfConfigurableProperties": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ },
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "instantiationState": {
+ "description": "The instantiation state of the VNF.\nPermitted values: - NOT_INSTANTIATED: The VNF instance is terminated or not instantiated. - INSTANTIATED: The VNF instance is instantiated.\n",
+ "type": "string",
+ "enum": [
+ "NOT_INSTANTIATED",
+ "INSTANTIATED"
+ ]
+ },
+ "instantiatedVnfInfo": {
+ "description": "Information specific to an instantiated VNF instance. This attribute shall be present if the instantiateState attribute value is INSTANTIATED.\n",
+ "type": "object",
+ "required": [
+ "flavourId",
+ "vnfState",
+ "extCpInfo"
+ ],
+ "properties": {
+ "flavourId": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
+ "type": "string"
},
- "creationStartedAt": {
- "description": "Date-time stamp. Representation: String formatted according toas defined by the date-time production in IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
+ "vnfState": {
+ "type": "string",
+ "enum": [
+ "STARTED",
+ "STOPPED"
+ ]
},
- "creationFinishedAt": {
- "description": "Date-time stamp. Representation: String formatted according toas defined by the date-time production in IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
+ "scaleStatus": {
+ "description": "Scale status of the VNF, one entry per aspect. Represents for every scaling aspect how \"big\" the VNF has been scaled w.r.t. that aspect.\n",
+ "type": "array",
+ "items": {
+ "required": [
+ "aspectId",
+ "scaleLevel"
+ ],
+ "type": "object",
+ "properties": {
+ "aspectId": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "scaleLevel": {
+ "description": "Indicates the scale level. The minimum value shall be 0 and the maximum value shall be <= maxScaleLevel as described in the VNFD.\n",
+ "type": "integer"
+ }
+ }
+ }
},
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
+ "maxScaleLevels": {
+ "description": "Maximum allowed scale levels of the VNF, one entry per aspect. This attribute shall be present if the VNF supports scaling.\n",
+ "type": "array",
+ "items": {
+ "required": [
+ "aspectId",
+ "scaleLevel"
+ ],
+ "type": "object",
+ "properties": {
+ "aspectId": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "scaleLevel": {
+ "description": "Indicates the scale level. The minimum value shall be 0 and the maximum value shall be <= maxScaleLevel as described in the VNFD.\n",
+ "type": "integer"
+ }
+ }
+ }
},
- "vnfInstance": {
- "description": "This type represents a VNF instance. It shall comply with the provisions defined in table 6.5.3.57-1.\nNOTE: Clause B.3.2 of ETSI GS NFV-SOL 003 provides examples illustrating the relationship among the different run-time information elements (CP, VL and link ports) used to represent the connectivity \n of a VNF.\n\nNOTE 1: 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 changed with respect to \n the previous VNFD in other aspects than merely referencing to other VNF software images. \n In order to avoid misalignment of the VnfInstance with the current VNF's on-boarded VNF Package, \n the values of attributes in the VnfInstance that have corresponding attributes in the VNFD shall \n be kept in sync with the values in the VNFD.\nNOTE 2: ETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on TOSCA specifications. NOTE 3: VNF configurable properties are sometimes also referred to as configuration parameters applicable to a VNF. Some of these are set prior to instantiation and cannot be modified if the VNF is instantiated, \n some are set prior to instantiation (are part of initial configuration) and can be modified later, \n and others can be set only after instantiation. The applicability of certain configuration may depend \n on the VNF and the required operation of the VNF at a certain point in time.\nNOTE 4: It is possible to have several ExtManagedVirtualLinkInfo for the same VNF internal VL in case of a multi-site VNF spanning several VIMs. The set of ExtManagedVirtualLinkInfo corresponding to the same \n VNF internal VL shall indicate so by referencing to the same VnfVirtualLinkDesc and externally-managed \n multi-site VL instance (refer to clause 6.5.3.59).\nNOTE 5: Even though externally-managed internal VLs are also used for VNF-internal connectivity, they shall not be listed in the \"vnfVirtualLinkResourceInfo\" attribute as this would be redundant.\n",
+ "extCpInfo": {
+ "description": "Information about the external CPs exposed by the VNF instance. When trunking is enabled, the list of entries includes both, external CPs corresponding to parent ports of a trunk, and external CPs associated to sub-ports of a trunk.\n",
+ "type": "array",
+ "minItems": 1,
+ "items": {
+ "description": "This type represents information about an external CP of a VNF. It shall comply with the provisions defined in Table 6.5.3.70-1. NOTE 1: The attributes attributes \"associatedVnfcCpId\", \"associatedVipCpId\", \"associatedVirtualCpId\" and \"associatedVnfVirtualLinkId\" are mutually exclusive. Exactly one shall be present. NOTE 2: An external CP instance is not associated to a link port in the cases indicated for the “extLinkPorts” attribute in clause 6.5.3.26. NOTE 3: Cardinality greater than 1 is only applicable for specific cases where more than one network attachment definition resource is needed to fulfil the connectivity requirements of the external CP, e.g. to build a link redundant mated pair in SR-IOV cases. NOTE 4: When more than one \"netAttDefResourceId\" is indicated, all shall belong to the same namespace.\n",
"type": "object",
- "required": ["id", "vnfdId", "vnfProvider", "vnfProductName", "vnfSoftwareVersion", "vnfdVersion", "vnfPkgId", "instantiationState"],
+ "required": [
+ "id",
+ "cpdId",
+ "cpProtocolInfo"
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "associatedVnfcCpId"
+ ]
+ },
+ {
+ "required": [
+ "associatedVipCpId"
+ ]
+ },
+ {
+ "required": [
+ "associatedVirtualCpId"
+ ]
+ },
+ {
+ "required": [
+ "associatedVnfVirtualLinkId"
+ ]
+ }
+ ],
"properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfInstanceName": {
- "description": "Name of the VNF instance. Modifications to this attribute can be requested using the \"ModifyVnfInfoData\" structure.\n",
- "type": "string"
- },
- "vnfInstanceDescription": {
- "description": "Human-readable description of the VNF instance. Modifications to this attribute can be requested using the \"ModifyVnfInfoData\" structure.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfProvider": {
- "description": "Provider of the VNF and the VNFD. The value is copied from the VNFD.\n",
- "type": "string"
- },
- "vnfProductName": {
- "description": "Name to identify the VNF Product. The value is copied from the VNFD.\n",
- "type": "string"
- },
- "vnfSoftwareVersion": {
- "description": "A Version. Representation: string of variable length.\n",
- "type": "string"
- },
- "vnfdVersion": {
- "description": "A Version. Representation: string of variable length.\n",
- "type": "string"
- },
- "versionDependency": {
- "description": "Describes version dependencies currently valid for the VNF instance. Identifies versions of descriptors of other constituents in the NSD upon which the VNF depends. The dependencies may be described for the VNFD referenced in this VnfInfo with vnfdId and for VNFDs with the same VnfdExtInvariantId. There shall not be more than one versionDependency present with the same dependentConstituentId.\n",
- "type": "array",
- "items": {
- "description": "This type represents the information related to all dependencies that an NSD constituent has on the versions of other NSD constituents. It shall comply with the provisions defined in table 6.5.3.112-1.\n",
- "type": "object",
- "required": ["dependentConstituentId"],
- "properties": {
- "dependentConstituentId": {
- "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
+ "id": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "cpdId": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
+ "type": "string"
+ },
+ "cpConfigId": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "cpProtocolInfo": {
+ "description": "Network protocol information for this CP.\n",
+ "type": "array",
+ "minItems": 1,
+ "items": {
+ "description": "This type describes the protocol layer(s) that a CP or SAP uses together with protocol-related information, like addresses. It shall comply with the provisions defined in Table 6.5.3.58-1. NOTE: This attribute allows to signal the addition of further types of layer and protocol in future versions of the present document in a backwards-compatible way. In the current version of the present document, only IP over Ethernet is supported.\n",
+ "type": "object",
+ "required": [
+ "layerProtocol",
+ "ipOverEthernet"
+ ],
+ "properties": {
+ "layerProtocol": {
+ "description": "The identifier of layer(s) and protocol(s) associated to the network address information. Permitted values:\n - IP_OVER_ETHERNET\n - IP_FOR_VIRTUAL_CP\nSee note.\n",
+ "type": "string",
+ "enum": [
+ "IP_OVER_ETHERNET",
+ "IP_FOR_VIRTUAL_CP"
+ ]
+ },
+ "ipOverEthernet": {
+ "description": "This type represents information about a network address that has been assigned.\nNOTE 1: At least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2: Exactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3: If the Cp instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4: Depending on the NFVI networking infrastructure, the \"segmentationId\" may indicate the actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header of the packets or it may be an identifier used between the application and the NFVI networking infrastructure to identify the network sub-interface of the trunk port in question. In the latter case the NFVI infrastructure will map this local \"segmentationId\" to whatever \"segmentationId\" is actually used by the NFVI's transport technology.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "required": [
+ "macAddress"
+ ]
+ },
+ {
+ "required": [
+ "ipAddresses"
+ ]
+ }
+ ],
+ "properties": {
+ "macAddress": {
+ "description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
+ "type": "string",
+ "format": "MAC"
+ },
+ "segmentationId": {
+ "description": "Identification of the network segment to which the Cp instance connects to. See note 3 and note 4.\n",
+ "type": "string"
+ },
+ "ipAddresses": {
+ "description": "Addresses assigned to the CP instance. Each entry represents IP addresses assigned by fixed or dynamic IP address assignment per subnet. See note 1.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": [
+ "type"
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "addresses"
+ ]
+ },
+ {
+ "required": [
+ "addressRange"
+ ]
+ }
+ ],
+ "properties": {
+ "type": {
+ "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
+ },
+ "addresses": {
+ "description": "Fixed addresses assigned (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
+ "type": "array",
+ "items": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ }
+ },
+ "isDynamic": {
+ "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
+ "type": "boolean"
+ },
+ "addressRange": {
+ "description": "An IP address range used, e.g., in case of egress connections. Exactly one of \"addresses\" or \"addressRange\" shall be present. See note 2.\n",
+ "type": "object",
+ "required": [
+ "minAddress",
+ "maxAddress"
+ ],
+ "properties": {
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ }
+ }
+ },
+ "subnetId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
"type": "string"
+ }
+ }
+ }
+ },
+ "type": {
+ "description": "The type of the IP addresses\n",
+ "type": "string",
+ "enum": [
+ "PV4",
+ "PV6"
+ ]
+ },
+ "addresses": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "isDynamic": {
+ "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
+ "type": "boolean"
+ },
+ "addressRange": {
+ "description": "An IP address range used, e.g. in case of egress connections. See note.\n",
+ "type": "object",
+ "required": [
+ "minAddress",
+ "maxAddress"
+ ],
+ "properties": {
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
},
- "versionDependencyStatement": {
- "description": "Identifies one or multiple versions of an NSD constituents upon which the dependent constituent identified by dependentConstituentId has a dependency. Cardinality 0 is used to remove an existing version dependency in a profile.\n",
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ }
+ }
+ },
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "subnetId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ }
+ }
+ },
+ "virtualCpAddress": {
+ "description": "This type represents information about a network address that has been assigned to a virtual CP.\n",
+ "type": "object",
+ "required": [
+ "type"
+ ],
+ "properties": {
+ "type": {
+ "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
+ },
+ "loadBalancerIp": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.",
+ "type": "string"
+ }
+ }
+ }
+ }
+ }
+ },
+ "extLinkPortId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "netAttDefResourceId": {
+ "description": "Identifier of the \"NetAttDefResourceInfo\" structure that provides the specification of the interface to attach the connection point to a secondary container cluster network. See notes 3 and 4.\nIt shall be present if the external CP is associated to a VNFC realized by one or a set of OS containers and is connected to a secondary container cluster network. It shall not be present otherwise.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ }
+ },
+ "metadata": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ },
+ "associatedVnfcCpId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "associatedVipCpId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "associatedVirtualCpId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "associatedVnfVirtualLinkId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "vipCpInfo": {
+ "description": "VIP CPs that are part of the VNF instance. Shall be present when that particular VIP CP of the VNFC instance is associated to an external CP of the VNF instance. May be present otherwise.\n",
+ "type": "array",
+ "items": {
+ "description": "This type provides information related to virtual IP (VIP) CP. It shall comply with the provisions defined in table 6.5.3.97 1. NOTE: It is possible that there is no associated VnfcCp because the VIP CP is available but not associated yet.\n",
+ "type": "object",
+ "required": [
+ "cpInstanceId",
+ "cpdId"
+ ],
+ "properties": {
+ "cpInstanceId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "cpdId": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfExtCpId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "cpProtocolInfo": {
+ "description": "Protocol information for this CP. There shall be one cpProtocolInfo for layer 3. There may be one cpProtocolInfo for layer 2.\n",
+ "type": "array",
+ "items": {
+ "description": "This type describes the protocol layer(s) that a CP or SAP uses together with protocol-related information, like addresses. It shall comply with the provisions defined in Table 6.5.3.58-1. NOTE: This attribute allows to signal the addition of further types of layer and protocol in future versions of the present document in a backwards-compatible way. In the current version of the present document, only IP over Ethernet is supported.\n",
+ "type": "object",
+ "required": [
+ "layerProtocol",
+ "ipOverEthernet"
+ ],
+ "properties": {
+ "layerProtocol": {
+ "description": "The identifier of layer(s) and protocol(s) associated to the network address information. Permitted values:\n - IP_OVER_ETHERNET\n - IP_FOR_VIRTUAL_CP\nSee note.\n",
+ "type": "string",
+ "enum": [
+ "IP_OVER_ETHERNET",
+ "IP_FOR_VIRTUAL_CP"
+ ]
+ },
+ "ipOverEthernet": {
+ "description": "This type represents information about a network address that has been assigned.\nNOTE 1: At least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2: Exactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3: If the Cp instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4: Depending on the NFVI networking infrastructure, the \"segmentationId\" may indicate the actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header of the packets or it may be an identifier used between the application and the NFVI networking infrastructure to identify the network sub-interface of the trunk port in question. In the latter case the NFVI infrastructure will map this local \"segmentationId\" to whatever \"segmentationId\" is actually used by the NFVI's transport technology.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "required": [
+ "macAddress"
+ ]
+ },
+ {
+ "required": [
+ "ipAddresses"
+ ]
+ }
+ ],
+ "properties": {
+ "macAddress": {
+ "description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
+ "type": "string",
+ "format": "MAC"
+ },
+ "segmentationId": {
+ "description": "Identification of the network segment to which the Cp instance connects to. See note 3 and note 4.\n",
+ "type": "string"
+ },
+ "ipAddresses": {
+ "description": "Addresses assigned to the CP instance. Each entry represents IP addresses assigned by fixed or dynamic IP address assignment per subnet. See note 1.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": [
+ "type"
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "addresses"
+ ]
+ },
+ {
+ "required": [
+ "addressRange"
+ ]
+ }
+ ],
+ "properties": {
+ "type": {
+ "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
+ },
+ "addresses": {
+ "description": "Fixed addresses assigned (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
"type": "array",
"items": {
- "description": "This type represents the information related to one or more VNF, NS or PNF descriptor identifiers which describe one single dependency. When more than one descriptor is indicated, they correspond to different versions of the same VNF, NS or PNF and they represent alternatives to fulfil the dependency. It shall comply with the provisions defined in table 6.5.3.113-1.\n",
- "type": "object",
- "required": ["descriptorId"],
- "properties": {
- "descriptorId": {
- "description": "Identifies a VNFD, NSD or PNFD upon which the entity using this information element depends. When more than one descriptor is indicated, they shall correspond to versions of the same VNF, NS or PNF and they represent. alternatives, i.e. the presence of one of them fulfills the dependency.",
- "type": "array",
- "items": {
- "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- }
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ }
+ },
+ "isDynamic": {
+ "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
+ "type": "boolean"
+ },
+ "addressRange": {
+ "description": "An IP address range used, e.g., in case of egress connections. Exactly one of \"addresses\" or \"addressRange\" shall be present. See note 2.\n",
+ "type": "object",
+ "required": [
+ "minAddress",
+ "maxAddress"
+ ],
+ "properties": {
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ }
}
+ },
+ "subnetId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "type": {
+ "description": "The type of the IP addresses\n",
+ "type": "string",
+ "enum": [
+ "PV4",
+ "PV6"
+ ]
+ },
+ "addresses": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "isDynamic": {
+ "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
+ "type": "boolean"
+ },
+ "addressRange": {
+ "description": "An IP address range used, e.g. in case of egress connections. See note.\n",
+ "type": "object",
+ "required": [
+ "minAddress",
+ "maxAddress"
+ ],
+ "properties": {
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
}
+ }
+ },
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "subnetId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
}
+ }
+ },
+ "virtualCpAddress": {
+ "description": "This type represents information about a network address that has been assigned to a virtual CP.\n",
+ "type": "object",
+ "required": [
+ "type"
+ ],
+ "properties": {
+ "type": {
+ "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
+ },
+ "loadBalancerIp": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.",
+ "type": "string"
+ }
+ }
}
- },
- "vnfPkgId": {
+ }
+ }
+ },
+ "associatedVnfcCpIds": {
+ "description": "Identifiers of the VnfcCps that share the virtual IP addresse allocated to the VIP CP instance. See note.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ }
+ },
+ "vnfLinkPortId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "metadata": {
+ "description": "Allows the OSS/BSS to provide additional parameter(s) to the termination process at the NS level.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ }
+ }
+ },
+ "virtualCpInfo": {
+ "description": "virtual CPs that are part of the VNF instance. Shall be present when a particular virtual CP is associated to an external CP of the VNF instance. May be present otherwise.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the information related to a virtual CP instance of a VNF. NOTE: A consumer of the VNF LCM interface can learn the actual VNFC instances implementing the service accessible via the virtual CP instance by querying the \"vnfcResourceInfo\" from the \"InstantiatedVnfInfo\" and filtering by corresponding \"vduId\" values.",
+ "type": "object",
+ "required": [
+ "cpInstanceId",
+ "cpdId",
+ "resourceHandle",
+ "vduId"
+ ],
+ "properties": {
+ "cpInstanceId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "cpdId": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
+ "type": "string"
+ },
+ "resourceHandle": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would correspond to the ‘kind’ field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the ‘claimName’ field in the Kubernetes® manifest, or a compound name built by Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the ‘metadata.name’ field in Kubernetes® manifest. \n",
+ "type": "object",
+ "required": [
+ "resourceId"
+ ],
+ "properties": {
+ "vimId": {
"description": "An identifier with the intention of being globally unique.\n",
"type": "string"
- },
- "vnfConfigurableProperties": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- },
- "vimId": {
+ },
+ "resourceProviderId": {
"description": "An identifier with the intention of being globally unique.\n",
"type": "string"
- },
- "instantiationState": {
- "description": "The instantiation state of the VNF.\nPermitted values: - NOT_INSTANTIATED: The VNF instance is terminated or not instantiated. - INSTANTIATED: The VNF instance is instantiated.\n",
- "type": "string",
- "enum": ["NOT_INSTANTIATED", "INSTANTIATED"]
- },
- "instantiatedVnfInfo": {
- "description": "Information specific to an instantiated VNF instance. This attribute shall be present if the instantiateState attribute value is INSTANTIATED.\n",
+ },
+ "resourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "type": "string"
+ },
+ "vimLevelAdditionalResourceInfo": {
+ "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
"type": "object",
- "required": ["flavourId", "vnfState", "extCpInfo"],
"properties": {
- "flavourId": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
+ "hostName": {
+ "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "persistentVolume": {
+ "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ },
+ "containerNamespace": {
+ "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise. \n",
+ "type": "string"
+ }
+ }
+ },
+ "vnfExtCpId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "cpProtocolInfo": {
+ "description": "Protocol information for this CP. There shall be one cpProtocolInfo for each layer protocol supported.\n",
+ "type": "array",
+ "items": {
+ "description": "This type describes the protocol layer(s) that a CP or SAP uses together with protocol-related information, like addresses. It shall comply with the provisions defined in Table 6.5.3.58-1. NOTE: This attribute allows to signal the addition of further types of layer and protocol in future versions of the present document in a backwards-compatible way. In the current version of the present document, only IP over Ethernet is supported.\n",
+ "type": "object",
+ "required": [
+ "layerProtocol",
+ "ipOverEthernet"
+ ],
+ "properties": {
+ "layerProtocol": {
+ "description": "The identifier of layer(s) and protocol(s) associated to the network address information. Permitted values:\n - IP_OVER_ETHERNET\n - IP_FOR_VIRTUAL_CP\nSee note.\n",
+ "type": "string",
+ "enum": [
+ "IP_OVER_ETHERNET",
+ "IP_FOR_VIRTUAL_CP"
+ ]
+ },
+ "ipOverEthernet": {
+ "description": "This type represents information about a network address that has been assigned.\nNOTE 1: At least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2: Exactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3: If the Cp instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4: Depending on the NFVI networking infrastructure, the \"segmentationId\" may indicate the actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header of the packets or it may be an identifier used between the application and the NFVI networking infrastructure to identify the network sub-interface of the trunk port in question. In the latter case the NFVI infrastructure will map this local \"segmentationId\" to whatever \"segmentationId\" is actually used by the NFVI's transport technology.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "required": [
+ "macAddress"
+ ]
},
- "vnfState": {
- "type": "string",
- "enum": ["STARTED", "STOPPED"]
+ {
+ "required": [
+ "ipAddresses"
+ ]
+ }
+ ],
+ "properties": {
+ "macAddress": {
+ "description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
+ "type": "string",
+ "format": "MAC"
},
- "scaleStatus": {
- "description": "Scale status of the VNF, one entry per aspect. Represents for every scaling aspect how \"big\" the VNF has been scaled w.r.t. that aspect.\n",
- "type": "array",
- "items": {
- "required": ["aspectId", "scaleLevel"],
- "type": "object",
- "properties": {
- "aspectId": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "scaleLevel": {
- "description": "Indicates the scale level. The minimum value shall be 0 and the maximum value shall be <= maxScaleLevel as described in the VNFD.\n",
- "type": "integer"
- }
- }
- }
+ "segmentationId": {
+ "description": "Identification of the network segment to which the Cp instance connects to. See note 3 and note 4.\n",
+ "type": "string"
},
- "maxScaleLevels": {
- "description": "Maximum allowed scale levels of the VNF, one entry per aspect. This attribute shall be present if the VNF supports scaling.\n",
- "type": "array",
- "items": {
- "required": ["aspectId", "scaleLevel"],
- "type": "object",
- "properties": {
- "aspectId": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "scaleLevel": {
- "description": "Indicates the scale level. The minimum value shall be 0 and the maximum value shall be <= maxScaleLevel as described in the VNFD.\n",
- "type": "integer"
- }
+ "ipAddresses": {
+ "description": "Addresses assigned to the CP instance. Each entry represents IP addresses assigned by fixed or dynamic IP address assignment per subnet. See note 1.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": [
+ "type"
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "addresses"
+ ]
+ },
+ {
+ "required": [
+ "addressRange"
+ ]
+ }
+ ],
+ "properties": {
+ "type": {
+ "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
+ },
+ "addresses": {
+ "description": "Fixed addresses assigned (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
+ "type": "array",
+ "items": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
}
- }
- },
- "extCpInfo": {
- "description": "Information about the external CPs exposed by the VNF instance. When trunking is enabled, the list of entries includes both, external CPs corresponding to parent ports of a trunk, and external CPs associated to sub-ports of a trunk.\n",
- "type": "array",
- "minItems": 1,
- "items": {
- "description": "This type represents information about an external CP of a VNF. It shall comply with the provisions defined in Table 6.5.3.70-1. NOTE 1: The attributes attributes \"associatedVnfcCpId\", \"associatedVipCpId\", \"associatedVirtualCpId\" and \"associatedVnfVirtualLinkId\" are mutually exclusive. Exactly one shall be present. NOTE 2: An external CP instance is not associated to a link port in the cases indicated for the extLinkPorts attribute in clause 6.5.3.26. NOTE 3: Cardinality greater than 1 is only applicable for specific cases where more than one network attachment definition resource is needed to fulfil the connectivity requirements of the external CP, e.g. to build a link redundant mated pair in SR-IOV cases. NOTE 4: When more than one \"netAttDefResourceId\" is indicated, all shall belong to the same namespace.\n",
+ },
+ "isDynamic": {
+ "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
+ "type": "boolean"
+ },
+ "addressRange": {
+ "description": "An IP address range used, e.g., in case of egress connections. Exactly one of \"addresses\" or \"addressRange\" shall be present. See note 2.\n",
"type": "object",
- "required": ["id", "cpdId", "cpProtocolInfo"],
- "oneOf": [{
- "required": ["associatedVnfcCpId"]
- }, {
- "required": ["associatedVipCpId"]
- }, {
- "required": ["associatedVirtualCpId"]
- }, {
- "required": ["associatedVnfVirtualLinkId"]
- }],
+ "required": [
+ "minAddress",
+ "maxAddress"
+ ],
"properties": {
- "id": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "cpdId": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "cpConfigId": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "cpProtocolInfo": {
- "description": "Network protocol information for this CP.\n",
- "type": "array",
- "minItems": 1,
- "items": {
- "description": "This type describes the protocol layer(s) that a CP or SAP uses together with protocol-related information, like addresses. It shall comply with the provisions defined in Table 6.5.3.58-1. NOTE: This attribute allows to signal the addition of further types of layer and protocol in future versions of the present document in a backwards-compatible way. In the current version of the present document, only IP over Ethernet is supported.\n",
- "type": "object",
- "required": ["layerProtocol", "ipOverEthernet"],
- "properties": {
- "layerProtocol": {
- "description": "The identifier of layer(s) and protocol(s) associated to the network address information. Permitted values: - IP_OVER_ETHERNET\n - IP_FOR_VIRTUAL_CP\nSee note.\n",
- "type": "string",
- "enum": ["IP_OVER_ETHERNET", "IP_FOR_VIRTUAL_CP"]
- },
- "ipOverEthernet": {
- "description": "This type represents information about a network address that has been assigned.\nNOTE 1: At least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2: Exactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3: If the Cp instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4: Depending on the NFVI networking infrastructure, the \"segmentationId\" may indicate the actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header of the packets or it may be an identifier used between the application and the NFVI networking infrastructure to identify the network sub-interface of the trunk port in question. In the latter case the NFVI infrastructure will map this local \"segmentationId\" to whatever \"segmentationId\" is actually used by the NFVI's transport technology.\n",
- "type": "object",
- "anyOf": [{
- "required": ["macAddress"]
- }, {
- "required": ["ipAddresses"]
- }],
- "properties": {
- "macAddress": {
- "description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
- "type": "string",
- "format": "MAC"
- },
- "segmentationId": {
- "description": "Identification of the network segment to which the Cp instance connects to. See note 3 and note 4.\n",
- "type": "string"
- },
- "ipAddresses": {
- "description": "Addresses assigned to the CP instance. Each entry represents IP addresses assigned by fixed or dynamic IP address assignment per subnet. See note 1.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": ["type"],
- "oneOf": [{
- "required": ["addresses"]
- }, {
- "required": ["addressRange"]
- }],
- "properties": {
- "type": {
- "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
- "type": "string",
- "enum": ["IPV4", "IPV6"]
- },
- "addresses": {
- "description": "Fixed addresses assigned (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
- "type": "array",
- "items": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- },
- "isDynamic": {
- "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
- "type": "boolean"
- },
- "addressRange": {
- "description": "An IP address range used, e.g., in case of egress connections. Exactly one of \"addresses\" or \"addressRange\" shall be present. See note 2.\n",
- "type": "object",
- "required": ["minAddress", "maxAddress"],
- "properties": {
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- },
- "subnetId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- }
- },
- "type": {
- "description": "The type of the IP addresses\n",
- "type": "string",
- "enum": ["PV4", "PV6"]
- },
- "addresses": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "isDynamic": {
- "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
- "type": "boolean"
- },
- "addressRange": {
- "description": "An IP address range used, e.g. in case of egress connections. See note.\n",
- "type": "object",
- "required": ["minAddress", "maxAddress"],
- "properties": {
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- },
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "subnetId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- },
- "virtualCpAddress": {
- "description": "This type represents information about a network address that has been assigned to a virtual CP.\n",
- "type": "object",
- "required": ["type"],
- "properties": {
- "type": {
- "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
- "type": "string",
- "enum": ["IPV4", "IPV6"]
- },
- "loadBalancerIp": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- }
- }
- }
- },
- "extLinkPortId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "netAttDefResourceId": {
- "description": "Identifier of the \"NetAttDefResourceInfo\" structure that provides the specification of the interface to attach the connection point to a secondary container cluster network. See notes 3 and 4.\nIt shall be present if the external CP is associated to a VNFC realized by one or a set of OS containers and is connected to a secondary container cluster network. It shall not be present otherwise.\n",
- "type": "array",
- "items": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- }
- },
- "metadata": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- },
- "associatedVnfcCpId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "associatedVipCpId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "associatedVirtualCpId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "associatedVnfVirtualLinkId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- }
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ }
}
+ },
+ "subnetId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ }
}
+ }
},
- "vipCpInfo": {
- "description": "VIP CPs that are part of the VNF instance. Shall be present when that particular VIP CP of the VNFC instance is associated to an external CP of the VNF instance. May be present otherwise.\n",
- "type": "array",
- "items": {
- "description": "This type provides information related to virtual IP (VIP) CP. It shall comply with the provisions defined in table 6.5.3.97 1. NOTE: It is possible that there is no associated VnfcCp because the VIP CP is available but not associated yet.\n",
- "type": "object",
- "required": ["cpInstanceId", "cpdId"],
- "properties": {
- "cpInstanceId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "cpdId": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfExtCpId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "cpProtocolInfo": {
- "description": "Protocol information for this CP. There shall be one cpProtocolInfo for layer 3. There may be one cpProtocolInfo for layer 2.\n",
- "type": "array",
- "items": {
- "description": "This type describes the protocol layer(s) that a CP or SAP uses together with protocol-related information, like addresses. It shall comply with the provisions defined in Table 6.5.3.58-1. NOTE: This attribute allows to signal the addition of further types of layer and protocol in future versions of the present document in a backwards-compatible way. In the current version of the present document, only IP over Ethernet is supported.\n",
- "type": "object",
- "required": ["layerProtocol", "ipOverEthernet"],
- "properties": {
- "layerProtocol": {
- "description": "The identifier of layer(s) and protocol(s) associated to the network address information. Permitted values: - IP_OVER_ETHERNET\n - IP_FOR_VIRTUAL_CP\nSee note.\n",
- "type": "string",
- "enum": ["IP_OVER_ETHERNET", "IP_FOR_VIRTUAL_CP"]
- },
- "ipOverEthernet": {
- "description": "This type represents information about a network address that has been assigned.\nNOTE 1: At least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2: Exactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3: If the Cp instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4: Depending on the NFVI networking infrastructure, the \"segmentationId\" may indicate the actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header of the packets or it may be an identifier used between the application and the NFVI networking infrastructure to identify the network sub-interface of the trunk port in question. In the latter case the NFVI infrastructure will map this local \"segmentationId\" to whatever \"segmentationId\" is actually used by the NFVI's transport technology.\n",
- "type": "object",
- "anyOf": [{
- "required": ["macAddress"]
- }, {
- "required": ["ipAddresses"]
- }],
- "properties": {
- "macAddress": {
- "description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
- "type": "string",
- "format": "MAC"
- },
- "segmentationId": {
- "description": "Identification of the network segment to which the Cp instance connects to. See note 3 and note 4.\n",
- "type": "string"
- },
- "ipAddresses": {
- "description": "Addresses assigned to the CP instance. Each entry represents IP addresses assigned by fixed or dynamic IP address assignment per subnet. See note 1.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": ["type"],
- "oneOf": [{
- "required": ["addresses"]
- }, {
- "required": ["addressRange"]
- }],
- "properties": {
- "type": {
- "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
- "type": "string",
- "enum": ["IPV4", "IPV6"]
- },
- "addresses": {
- "description": "Fixed addresses assigned (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
- "type": "array",
- "items": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- },
- "isDynamic": {
- "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
- "type": "boolean"
- },
- "addressRange": {
- "description": "An IP address range used, e.g., in case of egress connections. Exactly one of \"addresses\" or \"addressRange\" shall be present. See note 2.\n",
- "type": "object",
- "required": ["minAddress", "maxAddress"],
- "properties": {
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- },
- "subnetId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- }
- },
- "type": {
- "description": "The type of the IP addresses\n",
- "type": "string",
- "enum": ["PV4", "PV6"]
- },
- "addresses": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "isDynamic": {
- "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
- "type": "boolean"
- },
- "addressRange": {
- "description": "An IP address range used, e.g. in case of egress connections. See note.\n",
- "type": "object",
- "required": ["minAddress", "maxAddress"],
- "properties": {
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- },
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "subnetId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- },
- "virtualCpAddress": {
- "description": "This type represents information about a network address that has been assigned to a virtual CP.\n",
- "type": "object",
- "required": ["type"],
- "properties": {
- "type": {
- "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
- "type": "string",
- "enum": ["IPV4", "IPV6"]
- },
- "loadBalancerIp": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- }
- }
- }
- },
- "associatedVnfcCpIds": {
- "description": "Identifiers of the VnfcCps that share the virtual IP addresse allocated to the VIP CP instance. See note.\n",
- "type": "array",
- "items": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- }
- },
- "vnfLinkPortId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "metadata": {
- "description": "Allows the OSS/BSS to provide additional parameter(s) to the termination process at the NS level.\n",
- "type": "array",
- "items": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- }
- }
+ "type": {
+ "description": "The type of the IP addresses\n",
+ "type": "string",
+ "enum": [
+ "PV4",
+ "PV6"
+ ]
},
- "virtualCpInfo": {
- "description": "virtual CPs that are part of the VNF instance. Shall be present when a particular virtual CP is associated to an external CP of the VNF instance. May be present otherwise.\n",
- "type": "array",
- "items": {
- "description": "This type represents the information related to a virtual CP instance of a VNF. NOTE: A consumer of the VNF LCM interface can learn the actual VNFC instances implementing the service accessible via the virtual CP instance by querying the \"vnfcResourceInfo\" from the \"InstantiatedVnfInfo\" and filtering by corresponding \"vduId\" values.",
- "type": "object",
- "required": ["cpInstanceId", "cpdId", "resourceHandle", "vduId"],
- "properties": {
- "cpInstanceId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "cpdId": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "resourceHandle": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes instance the vimLevelResourceType is the type of resource, as would correspond to the kind field if the resource is declared in its own Kubernetes manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the claimName field in the Kubernetes manifest, or a compound name built by Kubernetes if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the metadata.name field in Kubernetes manifest. \n",
- "type": "object",
- "required": ["resourceId"],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
- "type": "string"
- },
- "vimLevelAdditionalResourceInfo": {
- "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
- "type": "object",
- "properties": {
- "hostName": {
- "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "persistentVolume": {
- "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "containerNamespace": {
- "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
- "type": "string"
- }
- }
- },
- "vnfExtCpId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "cpProtocolInfo": {
- "description": "Protocol information for this CP. There shall be one cpProtocolInfo for each layer protocol supported.\n",
- "type": "array",
- "items": {
- "description": "This type describes the protocol layer(s) that a CP or SAP uses together with protocol-related information, like addresses. It shall comply with the provisions defined in Table 6.5.3.58-1. NOTE: This attribute allows to signal the addition of further types of layer and protocol in future versions of the present document in a backwards-compatible way. In the current version of the present document, only IP over Ethernet is supported.\n",
- "type": "object",
- "required": ["layerProtocol", "ipOverEthernet"],
- "properties": {
- "layerProtocol": {
- "description": "The identifier of layer(s) and protocol(s) associated to the network address information. Permitted values: - IP_OVER_ETHERNET\n - IP_FOR_VIRTUAL_CP\nSee note.\n",
- "type": "string",
- "enum": ["IP_OVER_ETHERNET", "IP_FOR_VIRTUAL_CP"]
- },
- "ipOverEthernet": {
- "description": "This type represents information about a network address that has been assigned.\nNOTE 1: At least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2: Exactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3: If the Cp instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4: Depending on the NFVI networking infrastructure, the \"segmentationId\" may indicate the actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header of the packets or it may be an identifier used between the application and the NFVI networking infrastructure to identify the network sub-interface of the trunk port in question. In the latter case the NFVI infrastructure will map this local \"segmentationId\" to whatever \"segmentationId\" is actually used by the NFVI's transport technology.\n",
- "type": "object",
- "anyOf": [{
- "required": ["macAddress"]
- }, {
- "required": ["ipAddresses"]
- }],
- "properties": {
- "macAddress": {
- "description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
- "type": "string",
- "format": "MAC"
- },
- "segmentationId": {
- "description": "Identification of the network segment to which the Cp instance connects to. See note 3 and note 4.\n",
- "type": "string"
- },
- "ipAddresses": {
- "description": "Addresses assigned to the CP instance. Each entry represents IP addresses assigned by fixed or dynamic IP address assignment per subnet. See note 1.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": ["type"],
- "oneOf": [{
- "required": ["addresses"]
- }, {
- "required": ["addressRange"]
- }],
- "properties": {
- "type": {
- "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
- "type": "string",
- "enum": ["IPV4", "IPV6"]
- },
- "addresses": {
- "description": "Fixed addresses assigned (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
- "type": "array",
- "items": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- },
- "isDynamic": {
- "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
- "type": "boolean"
- },
- "addressRange": {
- "description": "An IP address range used, e.g., in case of egress connections. Exactly one of \"addresses\" or \"addressRange\" shall be present. See note 2.\n",
- "type": "object",
- "required": ["minAddress", "maxAddress"],
- "properties": {
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- },
- "subnetId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- }
- },
- "type": {
- "description": "The type of the IP addresses\n",
- "type": "string",
- "enum": ["PV4", "PV6"]
- },
- "addresses": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "isDynamic": {
- "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
- "type": "boolean"
- },
- "addressRange": {
- "description": "An IP address range used, e.g. in case of egress connections. See note.\n",
- "type": "object",
- "required": ["minAddress", "maxAddress"],
- "properties": {
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- },
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "subnetId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- },
- "virtualCpAddress": {
- "description": "This type represents information about a network address that has been assigned to a virtual CP.\n",
- "type": "object",
- "required": ["type"],
- "properties": {
- "type": {
- "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
- "type": "string",
- "enum": ["IPV4", "IPV6"]
- },
- "loadBalancerIp": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- }
- }
- }
- },
- "vduId": {
- "description": "Reference to the VDU(s) which implement the service accessible via the virtual CP instance. See note.\n",
- "type": "array",
- "items": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- }
- },
- "additionalServiceInfo": {
- "description": "Additional service identification information of the virtual CP instance.\n",
- "type": "array",
- "items": {
- "description": "This type represents the additional service information of the virtual CP instance used to expose properties of the virtual CP to NFV-MANO.\nNOTE: This attribute shall only be present if additional information is needed to identify the service termination within the VNF, such as for example a URL path information in an HTTP request required to allow a single virtual CP IP address to be used for several HTTP based services that use the same port number.",
- "type": "object",
- "required": ["portInfo"],
- "properties": {
- "portInfo": {
- "description": "Service port numbers exposed by the virtual CP instance.\n",
- "type": "array",
- "items": {
- "description": "This type represents the information related to the service identifying port properties exposed by the virtual CP instance.",
- "type": "object",
- "required": ["name", "protocol", "port", "isPortConfigurable"],
- "properties": {
- "name": {
- "description": "The name of the port exposed by the virtual CP instance.\n",
- "type": "string"
- },
- "protocol": {
- "description": "The L4 protocol for this port exposed by the virtual CP instance. Permitted values:\n - TCP\n - UDP\n - SCTP\n",
- "type": "string",
- "enum": ["TCP", "UDP", "SCTP"]
- },
- "port": {
- "description": "The L4 port number exposed by the virtual CP instance.\n",
- "type": "integer"
- },
- "isPortConfigurable": {
- "description": "Specifies whether the port attribute value is allowed to be configurable.\n",
- "type": "boolean"
- }
- }
- }
- },
- "serviceInfo": {
- "description": "Service matching information exposed by the virtual CP instance. See note.\n",
- "type": "array",
- "items": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- }
- }
- },
- "metadata": {
- "description": "Metadata about this virtual CP instance.\n",
- "type": "array",
- "items": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- }
- }
+ "addresses": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
},
- "extVirtualLinkInfo": {
- "description": "Information about the external VLs the VNF instance is connected to.\n",
- "type": "array",
- "items": {
- "description": "This type represents information about an VNF external VL.",
- "type": "object",
- "required": ["id", "resourceHandle", "currentVnfExtCpData"],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceHandle": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes instance the vimLevelResourceType is the type of resource, as would correspond to the kind field if the resource is declared in its own Kubernetes manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the claimName field in the Kubernetes manifest, or a compound name built by Kubernetes if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the metadata.name field in Kubernetes manifest. \n",
- "type": "object",
- "required": ["resourceId"],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
- "type": "string"
- },
- "vimLevelAdditionalResourceInfo": {
- "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
- "type": "object",
- "properties": {
- "hostName": {
- "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "persistentVolume": {
- "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "containerNamespace": {
- "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
- "type": "string"
- }
- }
- },
- "extLinkPorts": {
- "description": "Link ports of this VL.\n",
- "type": "array",
- "items": {
- "description": "This type represents information about a link port of an external VL, i.e. a port providing connectivity for the VNF to an NS VL. NOTE 1: The use cases UC#4 and UC#5 in Annex A.4 of ETSI GS NFV-IFA 007 provide examples for such a configuration. NOTE 2: The value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\" attribute.\n",
- "type": "object",
- "required": ["id", "resourceHandle"],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceHandle": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes instance the vimLevelResourceType is the type of resource, as would correspond to the kind field if the resource is declared in its own Kubernetes manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the claimName field in the Kubernetes manifest, or a compound name built by Kubernetes if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the metadata.name field in Kubernetes manifest. \n",
- "type": "object",
- "required": ["resourceId"],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
- "type": "string"
- },
- "vimLevelAdditionalResourceInfo": {
- "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
- "type": "object",
- "properties": {
- "hostName": {
- "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "persistentVolume": {
- "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "containerNamespace": {
- "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
- "type": "string"
- }
- }
- },
- "cpInstanceId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "secondaryCpInstanceId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "trunkResourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- }
- },
- "extNetAttDefResource": {
- "description": "Network attachment definition resources that provide the specification of the interface to attach connection points to this VL.\n",
- "type": "array",
- "items": {
- "description": "This type represents the information related to a network attachment definition resource that provides the specification of the interface used to connect one or multiple connection points to a secondary container cluster network\n",
- "type": "object",
- "required": ["netAttDefResourceInfoId", "netAttDefResource"],
- "properties": {
- "netAttDefResourceInfoId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "netAttDefResource": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes instance the vimLevelResourceType is the type of resource, as would correspond to the kind field if the resource is declared in its own Kubernetes manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the claimName field in the Kubernetes manifest, or a compound name built by Kubernetes if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the metadata.name field in Kubernetes manifest. \n",
- "type": "object",
- "required": ["resourceId"],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
- "type": "string"
- },
- "vimLevelAdditionalResourceInfo": {
- "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
- "type": "object",
- "properties": {
- "hostName": {
- "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "persistentVolume": {
- "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "containerNamespace": {
- "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
- "type": "string"
- }
- }
- },
- "associatedExtCpId": {
- "description": "Identifier of the external CP of the VNF associated to this network attachment definition resource. Shall be present when the network attachment definition resource is used for external connectivity by the VNF\n",
- "type": "array",
- "items": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- }
- },
- "associatedVnfcCpId": {
- "description": "Identifier of the VNFC CP of the VNF associated to this network attachment definition resource. May be present when the network attachment definition resource is used for internal connectivity by the VNF.\n",
- "type": "array",
- "items": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- }
- }
- }
- }
- },
- "currentVnfExtCpData": {
- "description": "This type represents configuration information for external CPs created from a CPD.\nNOTE 1: In case this identifier refers to a CPD with trunking enabled, the external CP instances created from this CPD will represent ports in a trunk. NOTE 2: The map entry value shall be set to \"null\" in order to delete a \"VnfExtCpConfig\" entry identified by a particular key value from the map, i.e. for the disconnection of an existing external CP instance addressed by cpInstanceId in the deleted map entry from a particular external virtual link, and deletion of that instance in case it represents a subport. Deleting the last key from the map removes the affected instance of the \"VnfExtCpData\" structure from its parent data structure. NOTE 3: Within one VNF instance, all VNFC instances created from a particular VDU have the same external connectivity. Thus, given a particular value of the \"cpdId' attribute, there shall be one \"cpConfig\" entry for each VNFC instance that has been or can be created from a VDU which includes a CPD identified by the \"cpdId\" attribute. If the cpConfig represents a subport in a trunk, all \"cpConfig\" entries in this list shall have the same segmentationId, which means they are connected to the same set of external VLs via the trunk. NOTE 4: If, as defined by the input parameters of a \"ChangeVnfFlavour\", \"ChangeExtVnfConnectivity\" or \"ChangeCurrentVnfPkg\" operation, a cpConfig map entry identified by a particular map key value is moved into another \"ExtVirtualLinkData\" or \"VnfExtCpData\" structure, this particular cpConfig map entry may be used by an external CP instance different than the one that has used it before the operation, or by no external CP instance at all. Renaming a CPD identifier during the \"changeCurrentVnfPkg\" operation does not count as moving the related \"cpConfig\" map entries to a new \"extCpData\" structure.\n",
- "type": "object",
- "required": ["cpdId"],
- "properties": {
- "cpdId": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "cpConfig": {
- "description": "Map of instance data that need to be configured on the CP instances created from the respective CPD. The key of the map which identifies the individual VnfExtCpConfig entries is of type \"IdentifierInVnf\" and is managed by the API consumer. The entries shall be applied by the VNFM according to the rules of JSON Merge Patch (see IETF RFC 7396 [11]). See notes 2, 3 and 4.\n",
- "type": "object",
- "additionalProperties": {
- "description": "This type represents an externally provided link port, or a network attachment definition resource of secondary container cluster network, or network address information per instance of a VNF external connection point. In the case of VM-based deployment of the VNFC exposing the external CP: In case a link port is provided, the NFVO shall use that link port when connecting the VNF external CP to the external VL. In case a link port is not provided, the NFVO or VNFM shall create a link port on the external VL, and use that link port to connect the VNF external CP to the external VL. In the case of container-based deployment of the VNFC exposing the external CP, the NFVO and VNFM shall use the network attachment definition resource of secondary container cluster network when connecting the CP to the external VL.\nNOTE 1: The following conditions apply to the attributes \"linkPortId\" and \"cpProtocolData\" for an external CP instance connected or to be connected to a virtual network not\n categorized as secondary container cluster network:\n - At least one of the \"linkPortId\" and \"cpProtocolData\" attributes shall be present for\n an external CP instance representing a subport that is to be created, or an external CP instance\n that is to be created by creating the corresponding VNFC or VNF instance during the current or\n a subsequent LCM operation, or for an existing external CP instance that is to be re-configured\n or added to a particular external virtual link.\n - If the \"cpProtocolData\" attribute is absent, the \"linkPortId\" attribute shall be provided\n referencing a pre-created link port with pre-configured address information.\n - If both \"cpProtocolData\" and \"linkportId\" are provided, the API consumer shall ensure that\n the cpProtocolData can be used with the pre-created link port referenced by \"linkPortId\".\nNOTE 2: In case the NFVO manages its own identifier space, the NFVO may remap this identifier when communicating with the VNFM. If the NFVO knows that there can be an identifier collision when communicating with the VNFM by using the identifier from the OSS/BSS, the NFVO shall remap it. NOTE 3: The following conditions apply to the attributes netAttDefResourceId and cpProtocolData for an external CP instance connected or to be connected to a secondary container cluster network; The \"netAttDefResourceId\" and \"cpProtocolData\" attributes shall both be absent for the deletion of an existing external CP instance addressed by \"cpInstanceId\". At least one of these attributes shall be present for a to-be-created external CP instance or an existing external CP instance. NOTE 4: Cardinality greater than 1 is only applicable for specific cases where more than one network attachment definition resource is needed to fulfil the connectivity requirements of the external CP, e.g. to build a link redundant mated pair in SR-IOV cases. When more than one \"netAttDefResourceId\" is indicated, all shall belong to the same namespace as defined by the corresponding \"netAttDefResourceNamespace\" attribute in the \"NetAttDefResourceData\". NOTE 5: Either \"linkPortId\" or \"netAttDefResourceId\" may be included, but not both.\n",
- "type": "object",
- "oneOf": [{
- "required": ["linkPortId"]
- }, {
- "required": ["cpProtocolData"]
- }],
- "properties": {
- "parentCpConfigId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "linkPortId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "createExtLinkPort": {
- "description": "Indicates the need to create a dedicated link port for the external CP. If set to True, a link port is created. If set to False, no link port is created. This attribute is only applicable for external CP instances without a floating IP address that expose a VIP CP instance for which a dedicated IP address is allocated. It shall be present in that case and shall be absent otherwise.\n",
- "type": "boolean"
- },
- "cpProtocolData": {
- "description": "Parameters for configuring the network protocols on the link port that connects the CP to a VL. See notes 1 and 3.\n",
- "type": "array",
- "items": {
- "description": "This type represents network protocol data.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the present document in a backwards-compatible way. In the current version of the present document, only IP over Ethernet is supported.\n",
- "type": "object",
- "required": ["layerProtocol"],
- "properties": {
- "layerProtocol": {
- "description": "Identifier of layer(s) and protocol(s). Permitted values: - IP_OVER_ETHERNET - IP_FOR_VIRTUAL_CP See note.\n",
- "type": "string",
- "enum": ["IP_OVER_ETHERNET", "IP_FOR_VIRTUAL_CP"]
- },
- "ipOverEthernet": {
- "description": "This type represents network address data for IP over Ethernet. NOTE 1: At least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2: Exactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present. NOTE 3: If the CP instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4: Depending on the NFVI networking infrastructure, the \"segmentationId\" may indicate the actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header of the packets or it may be an identifier used between the application and the NFVI networking infrastructure to identify the network sub-interface of the trunk port in question. In the latter case the NFVI infrastructure will map this local \"segmentationId\" to whatever \"segmentationId\" is actually used by the NFVI's transport technology.\n",
- "type": "object",
- "anyOf": [{
- "required": ["ipAddresses"]
- }, {
- "required": ["macAddress"]
- }],
- "properties": {
- "macAddress": {
- "description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
- "type": "string",
- "format": "MAC"
- },
- "segmentationType": {
- "description": "Specifies the encapsulation type for the traffics coming in and out of the trunk subport. Permitted values are: - VLAN: The subport uses VLAN as encapsulation type. - INHERIT: The subport gets its segmentation type from the network it is connected to. This attribute may be present for CP instances that represent subports in a trunk and shall be absent otherwise. If this attribute is not present for a subport CP instance, default value VLAN shall be used.\n",
- "type": "string",
- "enum": ["VLAN", "INHERIT"]
- },
- "segmentationId": {
- "description": "Identification of the network segment to which the CP instance connects to. See note 3 and note 4.\n",
- "type": "string"
- },
- "ipAddresses": {
- "description": "List of IP addresses to assign to the CP instance. Each entry represents IP address data for fixed or dynamic IP address assignment per subnet. If this attribute is not present, no IP address shall be assigned. See note 1.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": ["type"],
- "oneOf": [{
- "required": ["fixedAddresses"]
- }, {
- "required": ["numDynamicAddresses"]
- }, {
- "required": ["addressRange"]
- }],
- "properties": {
- "type": {
- "description": "The type of the IP addresses. Permitted values: - IPV4\n - IPV6\n",
- "type": "string",
- "enum": ["IPV4", "IPV6"]
- },
- "fixedAddresses": {
- "description": "Fixed addresses to assign (from the subnet defined by \"subnetId\" if provided). Exactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present.\n",
- "type": "array",
- "items": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- },
- "numDynamicAddresses": {
- "description": "Number of dynamic addresses to assign (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
- "type": "integer"
- },
- "addressRange": {
- "description": "An IP address range to be used, e.g. in case of egress connections. In case this attribute is present, IP addresses from the range will be used.\n",
- "type": "object",
- "required": ["minAddress", "maxAddress"],
- "properties": {
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- },
- "subnetId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- }
- }
- }
- },
- "virtualCpAddress": {
- "description": "This type represents network address data for a virtual CP. It shall comply with the provisions defined in table 6.5.3.12a-1.\n",
- "type": "object",
- "required": ["type"],
- "properties": {
- "type": {
- "description": "Identifier of layer(s) and protocol(s). Permitted values: IP_OVER_ETHERNET.\n",
- "type": "string",
- "enum": ["IPV4", "IPV6"]
- },
- "loadBalancerIp": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- }
- }
- }
- },
- "netAttDefResourceId": {
- "description": "Identifier of the \"NetAttDefResourceData\" structure that provides the specification of the interface to attach the external CP to a secondary container cluster network. It is only applicable if the external CP is connected or to be connected to a secondary container cluster network. It shall not be present if the external CP is related to a virtual network not categorized as secondary container cluster network. See notes 3, 4 and 5.\n",
- "type": "array",
- "items": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- }
- }
- }
- }
- }
- }
- }
- }
- }
+ "isDynamic": {
+ "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
+ "type": "boolean"
},
- "extManagedVirtualLinkInfo": {
- "description": "Information about the externally-managed internal VLs of the VNF instance. See note 4 and note 5.\n",
- "type": "array",
- "items": {
- "description": "This type provides information about an externally-managed internal virtual link for VNFs\n",
- "type": "object",
- "required": ["id", "vnfVirtualLinkDescId", "networkResource"],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfVirtualLinkDescId": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "networkResource": {
- "description": "Reference to the VirtualNetwork resource or multi-site connectivity service providing this VL.\n",
- "type": "array",
- "items": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes instance the vimLevelResourceType is the type of resource, as would correspond to the kind field if the resource is declared in its own Kubernetes manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the claimName field in the Kubernetes manifest, or a compound name built by Kubernetes if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the metadata.name field in Kubernetes manifest. \n",
- "type": "object",
- "required": ["resourceId"],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
- "type": "string"
- },
- "vimLevelAdditionalResourceInfo": {
- "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
- "type": "object",
- "properties": {
- "hostName": {
- "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "persistentVolume": {
- "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "containerNamespace": {
- "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
- "type": "string"
- }
- }
- }
- },
- "vnfLinkPorts": {
- "description": "Link ports of this VL.\n",
- "type": "array",
- "items": {
- "type": "object",
- "description": "This type represents a link port of an internal VL of a VNF. It shall comply with the provisions defined in table 6.5.3.64-1.\nNOTE 1: Either cpInstanceId with cpInstanceType set to \"EXT_CP\" or any combination of cpInstanceId with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId (i.e. one or both of them) shall be present for a VnfLinkPortInfo. In case both cpInstanceId with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId are present, the two different CP instances share the linkport.\n",
- "required": ["id", "resourceHandle"],
- "properties": {
- "id": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "resourceHandle": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes instance the vimLevelResourceType is the type of resource, as would correspond to the kind field if the resource is declared in its own Kubernetes manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the claimName field in the Kubernetes manifest, or a compound name built by Kubernetes if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the metadata.name field in Kubernetes manifest. \n",
- "type": "object",
- "required": ["resourceId"],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
- "type": "string"
- },
- "vimLevelAdditionalResourceInfo": {
- "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
- "type": "object",
- "properties": {
- "hostName": {
- "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "persistentVolume": {
- "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "containerNamespace": {
- "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
- "type": "string"
- }
- }
- },
- "cpInstanceId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "cpInstanceType": {
- "description": "Type of the CP instance that is identified by cpInstanceId. Shall be present if \"cpInstanceId\" is present, and shall be absent otherwise. Permitted values: * VNFC_CP: The link port is connected to a VNFC CP * EXT_CP: The link port is associated to an external CP. See note 1.\n",
- "type": "string",
- "enum": ["VNFC_CP", "EXT_CP"]
- },
- "vipCpInstanceId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "trunkResourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- }
- },
- "vnfNetAttDefResource": {
- "description": "This type represents the information related to a network attachment definition resource that provides the specification of the interface used to connect one or multiple connection points to a secondary container cluster network\n",
- "type": "object",
- "required": ["netAttDefResourceInfoId", "netAttDefResource"],
- "properties": {
- "netAttDefResourceInfoId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "netAttDefResource": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes instance the vimLevelResourceType is the type of resource, as would correspond to the kind field if the resource is declared in its own Kubernetes manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the claimName field in the Kubernetes manifest, or a compound name built by Kubernetes if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the metadata.name field in Kubernetes manifest. \n",
- "type": "object",
- "required": ["resourceId"],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
- "type": "string"
- },
- "vimLevelAdditionalResourceInfo": {
- "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
- "type": "object",
- "properties": {
- "hostName": {
- "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "persistentVolume": {
- "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "containerNamespace": {
- "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
- "type": "string"
- }
- }
- },
- "associatedExtCpId": {
- "description": "Identifier of the external CP of the VNF associated to this network attachment definition resource. Shall be present when the network attachment definition resource is used for external connectivity by the VNF\n",
- "type": "array",
- "items": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- }
- },
- "associatedVnfcCpId": {
- "description": "Identifier of the VNFC CP of the VNF associated to this network attachment definition resource. May be present when the network attachment definition resource is used for internal connectivity by the VNF.\n",
- "type": "array",
- "items": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- }
- }
- }
- },
- "extManagedMultisiteVirtualLinkId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- }
- }
+ "addressRange": {
+ "description": "An IP address range used, e.g. in case of egress connections. See note.\n",
+ "type": "object",
+ "required": [
+ "minAddress",
+ "maxAddress"
+ ],
+ "properties": {
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
}
+ }
},
- "monitoringParameters": {
- "description": "Performance metrics tracked by the VNFM (e.g. for auto-scaling purposes) as identified by the VNF provider in the VNFD.\n",
- "type": "array",
- "items": {
- "description": "This type represents a monitoring parameter that is tracked by the VNFM, for example, for auto-scaling purposes. It shall comply with the provisions defined in Table 6.5.3.69-1.\n",
- "type": "object",
- "required": ["id", "performanceMetric"],
- "properties": {
- "id": {
- "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "name": {
- "description": "Human readable name of the monitoring parameter, as defined in the VNFD.\n",
- "type": "string"
- },
- "performanceMetric": {
- "description": "Performance metric that is monitored. This attribute shall contain the related \"Measurement Name\" value as defined in clause 7.2 of ETSI GS NFV-IFA 027.\n",
- "type": "string"
- }
- }
- }
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
},
- "localizationLanguage": {
- "description": "Information about localization language of the VNF (includes e.g. strings in the VNFD). The localization languages supported by a VNF can be declared in the VNFD, and localization language selection can take place at instantiation time. The value shall comply with the format defined in IETF RFC 5646.\n",
+ "subnetId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ }
+ }
+ },
+ "virtualCpAddress": {
+ "description": "This type represents information about a network address that has been assigned to a virtual CP.\n",
+ "type": "object",
+ "required": [
+ "type"
+ ],
+ "properties": {
+ "type": {
+ "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
+ },
+ "loadBalancerIp": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.",
+ "type": "string"
+ }
+ }
+ }
+ }
+ }
+ },
+ "vduId": {
+ "description": "Reference to the VDU(s) which implement the service accessible via the virtual CP instance. See note.\n",
+ "type": "array",
+ "items": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
+ "type": "string"
+ }
+ },
+ "additionalServiceInfo": {
+ "description": "Additional service identification information of the virtual CP instance.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the additional service information of the virtual CP instance used to expose properties of the virtual CP to NFV-MANO.\nNOTE: This attribute shall only be present if additional information is needed to identify the service termination within the VNF, such as for example a URL path information in an HTTP request required to allow a single virtual CP IP address to be used for several HTTP based services that use the same port number.",
+ "type": "object",
+ "required": [
+ "portInfo"
+ ],
+ "properties": {
+ "portInfo": {
+ "description": "Service port numbers exposed by the virtual CP instance.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the information related to the service identifying port properties exposed by the virtual CP instance.",
+ "type": "object",
+ "required": [
+ "name",
+ "protocol",
+ "port",
+ "isPortConfigurable"
+ ],
+ "properties": {
+ "name": {
+ "description": "The name of the port exposed by the virtual CP instance.\n",
"type": "string"
+ },
+ "protocol": {
+ "description": "The L4 protocol for this port exposed by the virtual CP instance.\n Permitted values:\n - TCP\n - UDP\n - SCTP\n",
+ "type": "string",
+ "enum": [
+ "TCP",
+ "UDP",
+ "SCTP"
+ ]
+ },
+ "port": {
+ "description": "The L4 port number exposed by the virtual CP instance.\n",
+ "type": "integer"
+ },
+ "isPortConfigurable": {
+ "description": "Specifies whether the port attribute value is allowed to be configurable.\n",
+ "type": "boolean"
+ }
+ }
+ }
+ },
+ "serviceInfo": {
+ "description": "Service matching information exposed by the virtual CP instance. See note.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ }
+ }
+ },
+ "metadata": {
+ "description": "Metadata about this virtual CP instance.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ }
+ }
+ },
+ "extVirtualLinkInfo": {
+ "description": "Information about the external VLs the VNF instance is connected to.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents information about an VNF external VL.",
+ "type": "object",
+ "required": [
+ "id",
+ "resourceHandle",
+ "currentVnfExtCpData"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceHandle": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would correspond to the ‘kind’ field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the ‘claimName’ field in the Kubernetes® manifest, or a compound name built by Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the ‘metadata.name’ field in Kubernetes® manifest. \n",
+ "type": "object",
+ "required": [
+ "resourceId"
+ ],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceProviderId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "type": "string"
+ },
+ "vimLevelAdditionalResourceInfo": {
+ "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
+ "type": "object",
+ "properties": {
+ "hostName": {
+ "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "persistentVolume": {
+ "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ },
+ "containerNamespace": {
+ "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise. \n",
+ "type": "string"
+ }
+ }
+ },
+ "extLinkPorts": {
+ "description": "Link ports of this VL.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents information about a link port of an external VL, i.e. a port providing connectivity for the VNF to an NS VL. NOTE 1: The use cases UC#4 and UC#5 in Annex A.4 of ETSI GS NFV-IFA 007 provide examples for such a configuration. NOTE 2: The value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\" attribute.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "resourceHandle"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceHandle": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would correspond to the ‘kind’ field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the ‘claimName’ field in the Kubernetes® manifest, or a compound name built by Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the ‘metadata.name’ field in Kubernetes® manifest. \n",
+ "type": "object",
+ "required": [
+ "resourceId"
+ ],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
},
- "vnfcResourceInfo": {
- "description": "Information about the virtualised compute and storage resources used by the VNFCs of the VNF instance.\n",
- "type": "array",
- "items": {
- "description": "This type represents the information on virtualised compute and storage resources used by a VNFC in a VNF instance. This feature addresses the following capabilities: NFV Architecture support for VNFs which follow cloud-native design principles. Enhance NFV-MANO capabilities to support container technologies. Enhance NFV-MANO capabilities for container management and orchestration. Enhance information model for containerized VNFs both using bare metal or nested virtualization technologies.\nNOTE 1: ETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on TOSCA specifications. NOTE 2: A VNFC CP is \"connected to\" an external CP if the VNFC CP is connected to an internal VL that exposes an external CP. A VNFC CP is \"exposed as\" an external CP if it is connected directly to an external VL. NOTE 3: The information can be omitted because it is already available as part of the external CP information. NOTE 4: Cardinality greater than 1 is only applicable for specific cases where more than one network attachment definition resource is needed to fulfil the connectivity requirements of the internal CP, e.g. to build a link redundant mated pair in SR-IOV cases. NOTE 5: When more than one \"netAttDefResourceId\" is indicated, all shall belong to the same namespace.\n",
- "type": "object",
- "required": ["id", "vduId", "computeResource"],
- "properties": {
- "id": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vduId": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "computeResource": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes instance the vimLevelResourceType is the type of resource, as would correspond to the kind field if the resource is declared in its own Kubernetes manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the claimName field in the Kubernetes manifest, or a compound name built by Kubernetes if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the metadata.name field in Kubernetes manifest. \n",
- "type": "object",
- "required": ["resourceId"],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
- "type": "string"
- },
- "vimLevelAdditionalResourceInfo": {
- "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
- "type": "object",
- "properties": {
- "hostName": {
- "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "persistentVolume": {
- "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "containerNamespace": {
- "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
- "type": "string"
- }
- }
- },
- "storageResourceIds": {
- "description": "References to the VirtualStorage resources or references to Storage MCIOs. The value refers to a VirtualStorageResourceInfo item in the VnfInstance.\n",
- "type": "array",
- "items": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- }
- },
- "reservationId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfcCpInfo": {
- "description": "CPs of the VNFC instance. Shall be present when that particular CP of the VNFC instance is exposed as an external CP of the VNF instance or is connected to an external CP of the VNF instance.See note 2. May be present otherwise.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": ["id", "cpdId"],
- "properties": {
- "id": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "cpdId": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "vnfExtCpId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "cpProtocolInfo": {
- "description": "Network protocol information for this CP. May be omitted if the VNFC CP is exposed as an external CP. See note 3.\n",
- "type": "array",
- "items": {
- "description": "This type describes the protocol layer(s) that a CP or SAP uses together with protocol-related information, like addresses. It shall comply with the provisions defined in Table 6.5.3.58-1. NOTE: This attribute allows to signal the addition of further types of layer and protocol in future versions of the present document in a backwards-compatible way. In the current version of the present document, only IP over Ethernet is supported.\n",
- "type": "object",
- "required": ["layerProtocol", "ipOverEthernet"],
- "properties": {
- "layerProtocol": {
- "description": "The identifier of layer(s) and protocol(s) associated to the network address information. Permitted values: - IP_OVER_ETHERNET\n - IP_FOR_VIRTUAL_CP\nSee note.\n",
- "type": "string",
- "enum": ["IP_OVER_ETHERNET", "IP_FOR_VIRTUAL_CP"]
- },
- "ipOverEthernet": {
- "description": "This type represents information about a network address that has been assigned.\nNOTE 1: At least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2: Exactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3: If the Cp instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4: Depending on the NFVI networking infrastructure, the \"segmentationId\" may indicate the actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header of the packets or it may be an identifier used between the application and the NFVI networking infrastructure to identify the network sub-interface of the trunk port in question. In the latter case the NFVI infrastructure will map this local \"segmentationId\" to whatever \"segmentationId\" is actually used by the NFVI's transport technology.\n",
- "type": "object",
- "anyOf": [{
- "required": ["macAddress"]
- }, {
- "required": ["ipAddresses"]
- }],
- "properties": {
- "macAddress": {
- "description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
- "type": "string",
- "format": "MAC"
- },
- "segmentationId": {
- "description": "Identification of the network segment to which the Cp instance connects to. See note 3 and note 4.\n",
- "type": "string"
- },
- "ipAddresses": {
- "description": "Addresses assigned to the CP instance. Each entry represents IP addresses assigned by fixed or dynamic IP address assignment per subnet. See note 1.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": ["type"],
- "oneOf": [{
- "required": ["addresses"]
- }, {
- "required": ["addressRange"]
- }],
- "properties": {
- "type": {
- "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
- "type": "string",
- "enum": ["IPV4", "IPV6"]
- },
- "addresses": {
- "description": "Fixed addresses assigned (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
- "type": "array",
- "items": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- },
- "isDynamic": {
- "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
- "type": "boolean"
- },
- "addressRange": {
- "description": "An IP address range used, e.g., in case of egress connections. Exactly one of \"addresses\" or \"addressRange\" shall be present. See note 2.\n",
- "type": "object",
- "required": ["minAddress", "maxAddress"],
- "properties": {
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- },
- "subnetId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- }
- },
- "type": {
- "description": "The type of the IP addresses\n",
- "type": "string",
- "enum": ["PV4", "PV6"]
- },
- "addresses": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "isDynamic": {
- "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
- "type": "boolean"
- },
- "addressRange": {
- "description": "An IP address range used, e.g. in case of egress connections. See note.\n",
- "type": "object",
- "required": ["minAddress", "maxAddress"],
- "properties": {
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- },
- "minAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "maxAddress": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- },
- "subnetId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- },
- "virtualCpAddress": {
- "description": "This type represents information about a network address that has been assigned to a virtual CP.\n",
- "type": "object",
- "required": ["type"],
- "properties": {
- "type": {
- "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
- "type": "string",
- "enum": ["IPV4", "IPV6"]
- },
- "loadBalancerIp": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
- "type": "string",
- "format": "IP"
- }
- }
- }
- }
- }
- },
- "parentCpId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "vnfLinkPortId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "netAttDefResourceId": {
- "description": "Identifier of the \"NetAttDefResourceInfo\" structure that provides the specification of the interface to attach the connection point to a secondary container cluster network. See notes 4 and 5. It shall be present if the internal CP is associated to a VNFC realized by one or a set of OS containers and is connected to a secondary container cluster network. It shall not be present otherwise.\n",
- "type": "array",
- "items": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- }
- },
- "metadata": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- }
- },
- "metadata": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
+ "resourceProviderId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "type": "string"
+ },
+ "vimLevelAdditionalResourceInfo": {
+ "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
+ "type": "object",
+ "properties": {
+ "hostName": {
+ "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "persistentVolume": {
+ "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
}
+ }
},
- "vnfVirtualLinkResourceInfo": {
- "description": "Information about the virtualised network resources used by the VLs of the VNF instance. See note 5.\n",
- "type": "array",
- "items": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by an internal VL instance in a VNF instance.\n",
- "type": "object",
- "required": ["id", "vnfVirtualLinkDescId", "networkResource"],
- "properties": {
- "id": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfVirtualLinkDescId": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "networkResource": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes instance the vimLevelResourceType is the type of resource, as would correspond to the kind field if the resource is declared in its own Kubernetes manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the claimName field in the Kubernetes manifest, or a compound name built by Kubernetes if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the metadata.name field in Kubernetes manifest. \n",
- "type": "object",
- "required": ["resourceId"],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
- "type": "string"
- },
- "vimLevelAdditionalResourceInfo": {
- "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
- "type": "object",
- "properties": {
- "hostName": {
- "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "persistentVolume": {
- "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "containerNamespace": {
- "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
- "type": "string"
- }
- }
- },
- "reservationId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfLinkPorts": {
- "description": "Links ports of this VL. Shall be present when the linkPort is used for external connectivity by the VNF (refer to VnfLinkPortInfo). May be present otherwise.\n",
- "type": "array",
- "items": {
- "type": "object",
- "description": "This type represents a link port of an internal VL of a VNF. It shall comply with the provisions defined in table 6.5.3.64-1.\nNOTE 1: Either cpInstanceId with cpInstanceType set to \"EXT_CP\" or any combination of cpInstanceId with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId (i.e. one or both of them) shall be present for a VnfLinkPortInfo. In case both cpInstanceId with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId are present, the two different CP instances share the linkport.\n",
- "required": ["id", "resourceHandle"],
- "properties": {
- "id": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "resourceHandle": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes instance the vimLevelResourceType is the type of resource, as would correspond to the kind field if the resource is declared in its own Kubernetes manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the claimName field in the Kubernetes manifest, or a compound name built by Kubernetes if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the metadata.name field in Kubernetes manifest. \n",
- "type": "object",
- "required": ["resourceId"],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
- "type": "string"
- },
- "vimLevelAdditionalResourceInfo": {
- "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
- "type": "object",
- "properties": {
- "hostName": {
- "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "persistentVolume": {
- "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "containerNamespace": {
- "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
- "type": "string"
- }
- }
- },
- "cpInstanceId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "cpInstanceType": {
- "description": "Type of the CP instance that is identified by cpInstanceId. Shall be present if \"cpInstanceId\" is present, and shall be absent otherwise. Permitted values: * VNFC_CP: The link port is connected to a VNFC CP * EXT_CP: The link port is associated to an external CP. See note 1.\n",
- "type": "string",
- "enum": ["VNFC_CP", "EXT_CP"]
- },
- "vipCpInstanceId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "trunkResourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- }
- },
- "metadata": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
+ "containerNamespace": {
+ "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise. \n",
+ "type": "string"
+ }
+ }
+ },
+ "cpInstanceId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "secondaryCpInstanceId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "trunkResourceId": {
+ "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "extNetAttDefResource": {
+ "description": "Network attachment definition resources that provide the specification of the interface to attach connection points to this VL.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the information related to a network attachment definition resource that provides the specification of the interface used to connect one or multiple connection points to a secondary container cluster network\n",
+ "type": "object",
+ "required": [
+ "netAttDefResourceInfoId",
+ "netAttDefResource"
+ ],
+ "properties": {
+ "netAttDefResourceInfoId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "netAttDefResource": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would correspond to the ‘kind’ field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the ‘claimName’ field in the Kubernetes® manifest, or a compound name built by Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the ‘metadata.name’ field in Kubernetes® manifest. \n",
+ "type": "object",
+ "required": [
+ "resourceId"
+ ],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceProviderId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "type": "string"
+ },
+ "vimLevelAdditionalResourceInfo": {
+ "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
+ "type": "object",
+ "properties": {
+ "hostName": {
+ "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "persistentVolume": {
+ "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
}
+ }
+ },
+ "containerNamespace": {
+ "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise. \n",
+ "type": "string"
+ }
+ }
+ },
+ "associatedExtCpId": {
+ "description": "Identifier of the external CP of the VNF associated to this network attachment definition resource. Shall be present when the network attachment definition resource is used for external connectivity by the VNF\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ }
+ },
+ "associatedVnfcCpId": {
+ "description": "Identifier of the VNFC CP of the VNF associated to this network attachment definition resource. May be present when the network attachment definition resource is used for internal connectivity by the VNF.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ }
+ }
+ }
+ }
+ },
+ "currentVnfExtCpData": {
+ "description": "This type represents configuration information for external CPs created from a CPD.\nNOTE 1: In case this identifier refers to a CPD with trunking enabled, the external CP instances created from this CPD will represent ports in a trunk. NOTE 2: The map entry value shall be set to \"null\" in order to delete a \"VnfExtCpConfig\" entry identified by a particular key value from the map, i.e. for the disconnection of an existing external CP instance addressed by cpInstanceId in the deleted map entry from a particular external virtual link, and deletion of that instance in case it represents a subport. Deleting the last key from the map removes the affected instance of the \"VnfExtCpData\" structure from its parent data structure. NOTE 3: Within one VNF instance, all VNFC instances created from a particular VDU have the same external connectivity. Thus, given a particular value of the \"cpdId' attribute, there shall be one \"cpConfig\" entry for each VNFC instance that has been or can be created from a VDU which includes a CPD identified by the \"cpdId\" attribute. If the cpConfig represents a subport in a trunk, all \"cpConfig\" entries in this list shall have the same segmentationId, which means they are connected to the same set of external VLs via the trunk. NOTE 4: If, as defined by the input parameters of a \"ChangeVnfFlavour\", \"ChangeExtVnfConnectivity\" or \"ChangeCurrentVnfPkg\" operation, a cpConfig map entry identified by a particular map key value is moved into another \"ExtVirtualLinkData\" or \"VnfExtCpData\" structure, this particular cpConfig map entry may be used by an external CP instance different than the one that has used it before the operation, or by no external CP instance at all. Renaming a CPD identifier during the \"changeCurrentVnfPkg\" operation does not count as moving the related \"cpConfig\" map entries to a new \"extCpData\" structure.\n",
+ "type": "object",
+ "required": [
+ "cpdId"
+ ],
+ "properties": {
+ "cpdId": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
+ "type": "string"
+ },
+ "cpConfig": {
+ "description": "Map of instance data that need to be configured on the CP instances created from the respective CPD. The key of the map which identifies the individual VnfExtCpConfig entries is of type \"IdentifierInVnf\" and is managed by the API consumer. The entries shall be applied by the VNFM according to the rules of JSON Merge Patch (see IETF RFC 7396 [11]). See notes 2, 3 and 4.\n",
+ "type": "object",
+ "additionalProperties": {
+ "description": "This type represents an externally provided link port, or a network attachment definition resource of secondary container cluster network, or network address information per instance of a VNF external connection point. In the case of VM-based deployment of the VNFC exposing the external CP: In case a link port is provided, the NFVO shall use that link port when connecting the VNF external CP to the external VL. • In case a link port is not provided, the NFVO or VNFM shall create a link port on the external VL, and use that link port to connect the VNF external CP to the external VL. In the case of container-based deployment of the VNFC exposing the external CP, the NFVO and VNFM shall use the network attachment definition resource of secondary container cluster network when connecting the CP to the external VL.\nNOTE 1: The following conditions apply to the attributes \"linkPortId\" and \"cpProtocolData\"\n for an external CP instance connected or to be connected to a virtual network not\n categorized as secondary container cluster network:\n - At least one of the \"linkPortId\" and \"cpProtocolData\" attributes shall be present for\n an external CP instance representing a subport that is to be created, or an external CP instance\n that is to be created by creating the corresponding VNFC or VNF instance during the current or\n a subsequent LCM operation, or for an existing external CP instance that is to be re-configured\n or added to a particular external virtual link.\n - If the \"cpProtocolData\" attribute is absent, the \"linkPortId\" attribute shall be provided\n referencing a pre-created link port with pre-configured address information.\n - If both \"cpProtocolData\" and \"linkportId\" are provided, the API consumer shall ensure that\n the cpProtocolData can be used with the pre-created link port referenced by \"linkPortId\".\nNOTE 2: In case the NFVO manages its own identifier space, the NFVO may remap this identifier\n when communicating with the VNFM. If the NFVO knows that there can be an identifier collision\n when communicating with the VNFM by using the identifier from the OSS/BSS, the NFVO shall remap it.\nNOTE 3: The following conditions apply to the attributes \"netAttDefResourceId\" and \"cpProtocolData\" for an external CP\n instance connected or to be connected to a secondary container cluster network:\n − Void.\n − At least one of these attributes shall be present for a to-be-created external CP instance or an existing\n external CP instance.\nNOTE 4: Cardinality greater than 1 is only applicable for specific cases where more than one network\n attachment definition resource is needed to fulfil the connectivity requirements of the external CP,\n e.g. to build a link redundant mated pair in SR-IOV cases. When more than one \"netAttDefResourceId\"\n is indicated, all shall belong to the same namespace as defined by the corresponding \n \"containerNamespace\" attribute in the \"resourceHandle\" attribute in the \"NetAttDefResourceData\".\nNOTE 5: Either \"linkPortId\" or \"netAttDefResourceId\" may be included, but not both.\n",
+ "type": "object",
+ "oneOf": [
+ {
+ "required": [
+ "linkPortId"
+ ]
+ },
+ {
+ "required": [
+ "cpProtocolData"
+ ]
+ }
+ ],
+ "properties": {
+ "parentCpConfigId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
},
- "virtualStorageResourceInfo": {
- "description": "Information on the virtualised storage resource(s) used as storage for the VNF instance.\n",
- "type": "array",
- "items": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance.\n",
+ "linkPortId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "createExtLinkPort": {
+ "description": "Indicates the need to create a dedicated link port for the external CP. If set to True, a link port is created. If set to False, no link port is created. This attribute is only applicable for external CP instances without a floating IP address that expose a VIP CP instance for which a dedicated IP address is allocated. It shall be present in that case and shall be absent otherwise.\n",
+ "type": "boolean"
+ },
+ "cpProtocolData": {
+ "description": "Parameters for configuring the network protocols on the link port that connects the CP to a VL. See notes 1 and 3.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents network protocol data.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the present document in a backwards-compatible way. In the current version of the present document, only IP over Ethernet is supported.\n",
+ "type": "object",
+ "required": [
+ "layerProtocol"
+ ],
+ "properties": {
+ "layerProtocol": {
+ "description": "Identifier of layer(s) and protocol(s). Permitted values: - IP_OVER_ETHERNET - IP_FOR_VIRTUAL_CP See note.\n",
+ "type": "string",
+ "enum": [
+ "IP_OVER_ETHERNET",
+ "IP_FOR_VIRTUAL_CP"
+ ]
+ },
+ "ipOverEthernet": {
+ "description": "This type represents network address data for IP over Ethernet. NOTE 1: At least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2: Exactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present. NOTE 3: If the CP instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4: Depending on the NFVI networking infrastructure, the \"segmentationId\" may indicate the actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header of the packets or it may be an identifier used between the application and the NFVI networking infrastructure to identify the network sub-interface of the trunk port in question. In the latter case the NFVI infrastructure will map this local \"segmentationId\" to whatever \"segmentationId\" is actually used by the NFVI's transport technology.\n",
"type": "object",
- "required": ["id", "virtualStorageDescId", "storageResource"],
+ "anyOf": [
+ {
+ "required": [
+ "ipAddresses"
+ ]
+ },
+ {
+ "required": [
+ "macAddress"
+ ]
+ }
+ ],
"properties": {
- "id": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "virtualStorageDescId": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "storageResource": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes instance the vimLevelResourceType is the type of resource, as would correspond to the kind field if the resource is declared in its own Kubernetes manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the claimName field in the Kubernetes manifest, or a compound name built by Kubernetes if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the metadata.name field in Kubernetes manifest. \n",
- "type": "object",
- "required": ["resourceId"],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
- "type": "string"
- },
- "vimLevelAdditionalResourceInfo": {
- "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
- "type": "object",
- "properties": {
- "hostName": {
- "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "persistentVolume": {
- "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
+ "macAddress": {
+ "description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
+ "type": "string",
+ "format": "MAC"
+ },
+ "segmentationType": {
+ "description": "Specifies the encapsulation type for the traffics coming in and out of the trunk subport. Permitted values are: - VLAN: The subport uses VLAN as encapsulation type. - INHERIT: The subport gets its segmentation type from the network it is connected to. This attribute may be present for CP instances that represent subports in a trunk and shall be absent otherwise. If this attribute is not present for a subport CP instance, default value VLAN shall be used.\n",
+ "type": "string",
+ "enum": [
+ "VLAN",
+ "INHERIT"
+ ]
+ },
+ "segmentationId": {
+ "description": "Identification of the network segment to which the CP instance connects to. See note 3 and note 4.\n",
+ "type": "string"
+ },
+ "ipAddresses": {
+ "description": "List of IP addresses to assign to the CP instance. Each entry represents IP address data for fixed or dynamic IP address assignment per subnet. If this attribute is not present, no IP address shall be assigned. See note 1.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": [
+ "type"
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "fixedAddresses"
+ ]
+ },
+ {
+ "required": [
+ "numDynamicAddresses"
+ ]
+ },
+ {
+ "required": [
+ "addressRange"
+ ]
+ }
+ ],
+ "properties": {
+ "type": {
+ "description": "The type of the IP addresses. Permitted values:\n - IPV4\n - IPV6\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
+ },
+ "fixedAddresses": {
+ "description": "Fixed addresses to assign (from the subnet defined by \"subnetId\" if provided). Exactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present.\n",
+ "type": "array",
+ "items": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ }
+ },
+ "numDynamicAddresses": {
+ "description": "Number of dynamic addresses to assign (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
+ "type": "integer"
+ },
+ "addressRange": {
+ "description": "An IP address range to be used, e.g. in case of egress connections. In case this attribute is present, IP addresses from the range will be used.\n",
+ "type": "object",
+ "required": [
+ "minAddress",
+ "maxAddress"
+ ],
+ "properties": {
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
},
- "containerNamespace": {
- "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
- "type": "string"
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
}
+ }
+ },
+ "subnetId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
}
- },
- "reservationId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "metadata": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
+ }
}
+ }
}
- }
- },
- "mcioInfo": {
- "description": "Information on the MCIO(s) representing VNFC instance(s) realized by one or a set of OS containers and created from the same VDU for the VNF instance.\n",
- "type": "array",
- "items": {
- "description": "This type provides information about an MCIO representing the set of VNFC instances realized by one or a set of OS containers which have been created based on the same VDU.\nNOTE 1 The type of MCIO as specified in the declarative descriptor of the MCIO, and that can be read from the CISM. EXAMPLE: In case of MCIOs managed by Kubernetes, the type of MCIO corresponds to the kind property of the declarative descriptor. NOTE 2 If the attribute additionalInfo is present, it may contain runtime information on the actual and desired state of the MCIO(s). NOTE 3 When the container infrastructure service is a Kubernetes instance, the mcioId is the combined values from the kind and name fields of the Kubernetes resource object, separated by a slash. Example: \"Deployment/abcd\". NOTE 4 When the container infrastructure service is a Kubernetes instance, the mcioName is the name field of the resource object.",
+ },
+ "virtualCpAddress": {
+ "description": "This type represents network address data for a virtual CP. It shall comply with the provisions defined in table 6.5.3.12a-1.\nNOTE 1: If the container cluster is set up to be able to configure an external load balancer this address will be\n used, otherwise it will be ignored by the CISM.\nNOTE 2: In case the cluster can configure an external load balancer but no loadBalancerIp is provided the\n container cluster will assign an IP address.\nNOTE 3: The attribute is only relevant if the virtual CP is instantiated in a cluster that supports configuration of IP\n address pools for virtual CPs. Otherwise it shall be ignored. MetalLB is an example of a solution for\n Kubernetes® that supports configuration of address pools for load balancer services.\nNOTE 4: The loadBalancerIp and the addressPoolName attributes shall not be present at the same time.\n",
"type": "object",
- "required": ["mcioId", "mcioName", "mcioNamespace", "vduId", "cismId", "mcioType", "desiredInstances", "availableInstances"],
+ "required": [
+ "type"
+ ],
"properties": {
- "mcioId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "mcioName": {
- "description": "Human readable name of this MCIO. See note 4.\n",
- "type": "string"
- },
- "mcioNamespace": {
- "description": "Namespace of this MCIO.\n",
- "type": "string"
- },
- "vduId": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "cismId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "mcioType": {
- "description": "The type of MCIO. Specific values, their semantics and associated MCIO types are defined in clause 6.5.4.13. Additional values are also permitted. See note 1.\n",
- "type": "string"
- },
- "desiredInstances": {
- "description": "Number of desired MCIO instances.\n",
- "type": "integer"
- },
- "availableInstances": {
- "description": "Number of available MCIO instances\n",
- "type": "integer"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
+ "type": {
+ "description": "Identifier of layer(s) and protocol(s). Permitted values: IP_OVER_ETHERNET.\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
+ },
+ "loadBalancerIp": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which the container cluster will assign an IP address to the virtual CP. See notes 3 and 4.\n",
+ "type": "array",
+ "items": {
+ "type": "string"
}
+ }
}
+ }
}
+ }
+ },
+ "netAttDefResourceId": {
+ "description": "Identifier of the \"NetAttDefResourceData\" structure that provides the specification of the interface to attach the external CP to a secondary container cluster network. It is only applicable if the external CP is connected or to be connected to a secondary container cluster network. It shall not be present if the external CP is related to a virtual network not categorized as secondary container cluster network. See notes 3, 4 and 5.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ }
}
+ }
}
- },
- "metadata": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- },
- "extensions": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
+ }
}
+ }
}
+ }
},
- "vnfcSnapshots": {
- "description": "Information about VNFC Snapshots constituting this VNF Snapshot.\n",
- "type": "array",
- "items": {
- "description": "This type represents a VNFC Snapshot. It shall comply with the provisions defined in table 6.5.3.77-1. NOTE 1: The identifier of the compute snapshot resource is assigned during creation of a VNFC Snapshot being returned from the VIM as output data in the response message of the individual resource operations. This attribute shall only be present for a VNFC snapshot that has been newly created by the VNFM as a result of the \"Create VNF snapshot task\". NOTE 2: The identifier of the storage snapshot resource is assigned during creation of a VNFC snapshot being returned from the VIM as output data in the response message of the individual resource operations. This attribute shall only be present for a VNFC snapshot with an associated storage resource and that has been newly created by the VNFM as a result of the \"Create VNF snapshot task\".\n",
+ "extManagedVirtualLinkInfo": {
+ "description": "Information about the externally-managed internal VLs of the VNF instance. See note 4 and note 5.\n",
+ "type": "array",
+ "items": {
+ "description": "This type provides information about an externally-managed internal virtual link for VNFs\n",
+ "type": "object",
+ "required": [
+ "id",
+ "vnfVirtualLinkDescId",
+ "networkResource"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfVirtualLinkDescId": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
+ "type": "string"
+ },
+ "networkResource": {
+ "description": "Reference to the VirtualNetwork resource or multi-site connectivity service providing this VL.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would correspond to the ‘kind’ field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the ‘claimName’ field in the Kubernetes® manifest, or a compound name built by Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the ‘metadata.name’ field in Kubernetes® manifest. \n",
+ "type": "object",
+ "required": [
+ "resourceId"
+ ],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceProviderId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "type": "string"
+ },
+ "vimLevelAdditionalResourceInfo": {
+ "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
+ "type": "object",
+ "properties": {
+ "hostName": {
+ "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "persistentVolume": {
+ "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ },
+ "containerNamespace": {
+ "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise. \n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "vnfLinkPorts": {
+ "description": "Link ports of this VL.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "description": "This type represents a link port of an internal VL of a VNF. It shall comply with the provisions defined in table 6.5.3.64-1.\nNOTE 1: Either cpInstanceId with cpInstanceType set to \"EXT_CP\" or any combination of cpInstanceId with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId (i.e. one or both of them) shall be present for a VnfLinkPortInfo. In case both cpInstanceId with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId are present, the two different CP instances share the linkport.\n",
+ "required": [
+ "id",
+ "resourceHandle"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "resourceHandle": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would correspond to the ‘kind’ field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the ‘claimName’ field in the Kubernetes® manifest, or a compound name built by Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the ‘metadata.name’ field in Kubernetes® manifest. \n",
+ "type": "object",
+ "required": [
+ "resourceId"
+ ],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceProviderId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "type": "string"
+ },
+ "vimLevelAdditionalResourceInfo": {
+ "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
+ "type": "object",
+ "properties": {
+ "hostName": {
+ "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "persistentVolume": {
+ "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ },
+ "containerNamespace": {
+ "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise. \n",
+ "type": "string"
+ }
+ }
+ },
+ "cpInstanceId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "cpInstanceType": {
+ "description": "Type of the CP instance that is identified by cpInstanceId. Shall be present if \"cpInstanceId\" is present, and shall be absent otherwise. Permitted values: * VNFC_CP: The link port is connected to a VNFC CP * EXT_CP: The link port is associated to an external CP. See note 1.\n",
+ "type": "string",
+ "enum": [
+ "VNFC_CP",
+ "EXT_CP"
+ ]
+ },
+ "vipCpInstanceId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "trunkResourceId": {
+ "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "vnfNetAttDefResource": {
+ "description": "This type represents the information related to a network attachment definition resource that provides the specification of the interface used to connect one or multiple connection points to a secondary container cluster network\n",
"type": "object",
- "required": ["id", "vnfcInstanceId", "triggeredAt", "createdAt", "vnfcInfoId"],
+ "required": [
+ "netAttDefResourceInfoId",
+ "netAttDefResource"
+ ],
"properties": {
- "id": {
+ "netAttDefResourceInfoId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "netAttDefResource": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would correspond to the ‘kind’ field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the ‘claimName’ field in the Kubernetes® manifest, or a compound name built by Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the ‘metadata.name’ field in Kubernetes® manifest. \n",
+ "type": "object",
+ "required": [
+ "resourceId"
+ ],
+ "properties": {
+ "vimId": {
"description": "An identifier with the intention of being globally unique.\n",
"type": "string"
- },
- "vnfcInstanceId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ },
+ "resourceProviderId": {
+ "description": "An identifier with the intention of being globally unique.\n",
"type": "string"
+ },
+ "resourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "type": "string"
+ },
+ "vimLevelAdditionalResourceInfo": {
+ "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
+ "type": "object",
+ "properties": {
+ "hostName": {
+ "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "persistentVolume": {
+ "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ },
+ "containerNamespace": {
+ "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise. \n",
+ "type": "string"
+ }
+ }
+ },
+ "associatedExtCpId": {
+ "description": "Identifier of the external CP of the VNF associated to this network attachment definition resource. Shall be present when the network attachment definition resource is used for external connectivity by the VNF\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ }
+ },
+ "associatedVnfcCpId": {
+ "description": "Identifier of the VNFC CP of the VNF associated to this network attachment definition resource. May be present when the network attachment definition resource is used for internal connectivity by the VNF.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "extManagedMultisiteVirtualLinkId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "monitoringParameters": {
+ "description": "Performance metrics tracked by the VNFM (e.g. for auto-scaling purposes) as identified by the VNF provider in the VNFD.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents a monitoring parameter that is tracked by the VNFM, for example, for auto-scaling purposes. It shall comply with the provisions defined in Table 6.5.3.69-1.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "performanceMetric"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier that is unique within a NS descriptor. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "name": {
+ "description": "Human readable name of the monitoring parameter, as defined in the VNFD.\n",
+ "type": "string"
+ },
+ "performanceMetric": {
+ "description": "Performance metric that is monitored. This attribute shall contain the related \"Measurement Name\" value as defined in clause 7.2 of ETSI GS NFV-IFA 027.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "localizationLanguage": {
+ "description": "Information about localization language of the VNF (includes e.g. strings in the VNFD). The localization languages supported by a VNF can be declared in the VNFD, and localization language selection can take place at instantiation time. The value shall comply with the format defined in IETF RFC 5646.\n",
+ "type": "string"
+ },
+ "vnfcResourceInfo": {
+ "description": "Information about the virtualised compute and storage resources used by the VNFCs of the VNF instance.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the information on virtualised compute and storage resources used by a VNFC in a VNF instance. This feature addresses the following capabilities: • NFV Architecture support for VNFs which follow “cloud-native” design principles. • Enhance NFV-MANO capabilities to support container technologies. • Enhance NFV-MANO capabilities for container management and orchestration. • Enhance information model for containerized VNFs both using bare metal or nested virtualization technologies.\nNOTE 1: ETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on TOSCA specifications. NOTE 2: A VNFC CP is \"connected to\" an external CP if the VNFC CP is connected to an internal VL that exposes an external CP. A VNFC CP is \"exposed as\" an external CP if it is connected directly to an external VL. NOTE 3: The information can be omitted because it is already available as part of the external CP information. NOTE 4: Cardinality greater than 1 is only applicable for specific cases where more than one network attachment definition resource is needed to fulfil the connectivity requirements of the internal CP, e.g. to build a link redundant mated pair in SR-IOV cases. NOTE 5: When more than one \"netAttDefResourceId\" is indicated, all shall belong to the same namespace.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "vduId",
+ "computeResource"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vduId": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
+ "type": "string"
+ },
+ "computeResource": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would correspond to the ‘kind’ field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the ‘claimName’ field in the Kubernetes® manifest, or a compound name built by Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the ‘metadata.name’ field in Kubernetes® manifest. \n",
+ "type": "object",
+ "required": [
+ "resourceId"
+ ],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceProviderId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "type": "string"
+ },
+ "vimLevelAdditionalResourceInfo": {
+ "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
+ "type": "object",
+ "properties": {
+ "hostName": {
+ "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "persistentVolume": {
+ "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ },
+ "containerNamespace": {
+ "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise. \n",
+ "type": "string"
+ }
+ }
+ },
+ "storageResourceIds": {
+ "description": "References to the VirtualStorage resources or references to Storage MCIOs. The value refers to a VirtualStorageResourceInfo item in the VnfInstance.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ }
+ },
+ "reservationId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfcCpInfo": {
+ "description": "CPs of the VNFC instance. Shall be present when that particular CP of the VNFC instance is exposed as an external CP of the VNF instance or is connected to an external CP of the VNF instance.See note 2. May be present otherwise.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": [
+ "id",
+ "cpdId"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
},
- "creationStartedAt": {
- "description": "Date-time stamp. Representation: String formatted according toas defined by the date-time production in IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "creationFinishedAt": {
- "description": "Date-time stamp. Representation: String formatted according toas defined by the date-time production in IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
+ "cpdId": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
+ "type": "string"
},
- "vnfcResourceInfoId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
+ "vnfExtCpId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
},
- "computeSnapshotResource": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes instance the vimLevelResourceType is the type of resource, as would correspond to the kind field if the resource is declared in its own Kubernetes manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the claimName field in the Kubernetes manifest, or a compound name built by Kubernetes if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the metadata.name field in Kubernetes manifest. \n",
+ "cpProtocolInfo": {
+ "description": "Network protocol information for this CP. May be omitted if the VNFC CP is exposed as an external CP. See note 3.\n",
+ "type": "array",
+ "items": {
+ "description": "This type describes the protocol layer(s) that a CP or SAP uses together with protocol-related information, like addresses. It shall comply with the provisions defined in Table 6.5.3.58-1. NOTE: This attribute allows to signal the addition of further types of layer and protocol in future versions of the present document in a backwards-compatible way. In the current version of the present document, only IP over Ethernet is supported.\n",
"type": "object",
- "required": ["resourceId"],
+ "required": [
+ "layerProtocol",
+ "ipOverEthernet"
+ ],
"properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "layerProtocol": {
+ "description": "The identifier of layer(s) and protocol(s) associated to the network address information. Permitted values:\n - IP_OVER_ETHERNET\n - IP_FOR_VIRTUAL_CP\nSee note.\n",
+ "type": "string",
+ "enum": [
+ "IP_OVER_ETHERNET",
+ "IP_FOR_VIRTUAL_CP"
+ ]
+ },
+ "ipOverEthernet": {
+ "description": "This type represents information about a network address that has been assigned.\nNOTE 1: At least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2: Exactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3: If the Cp instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4: Depending on the NFVI networking infrastructure, the \"segmentationId\" may indicate the actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header of the packets or it may be an identifier used between the application and the NFVI networking infrastructure to identify the network sub-interface of the trunk port in question. In the latter case the NFVI infrastructure will map this local \"segmentationId\" to whatever \"segmentationId\" is actually used by the NFVI's transport technology.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "required": [
+ "macAddress"
+ ]
+ },
+ {
+ "required": [
+ "ipAddresses"
+ ]
+ }
+ ],
+ "properties": {
+ "macAddress": {
+ "description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
+ "type": "string",
+ "format": "MAC"
+ },
+ "segmentationId": {
+ "description": "Identification of the network segment to which the Cp instance connects to. See note 3 and note 4.\n",
"type": "string"
- },
- "vimLevelAdditionalResourceInfo": {
- "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
- "type": "object",
- "properties": {
- "hostName": {
- "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "persistentVolume": {
- "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
+ },
+ "ipAddresses": {
+ "description": "Addresses assigned to the CP instance. Each entry represents IP addresses assigned by fixed or dynamic IP address assignment per subnet. See note 1.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": [
+ "type"
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "addresses"
+ ]
+ },
+ {
+ "required": [
+ "addressRange"
+ ]
+ }
+ ],
+ "properties": {
+ "type": {
+ "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
+ },
+ "addresses": {
+ "description": "Fixed addresses assigned (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
+ "type": "array",
+ "items": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ }
+ },
+ "isDynamic": {
+ "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
+ "type": "boolean"
+ },
+ "addressRange": {
+ "description": "An IP address range used, e.g., in case of egress connections. Exactly one of \"addresses\" or \"addressRange\" shall be present. See note 2.\n",
+ "type": "object",
+ "required": [
+ "minAddress",
+ "maxAddress"
+ ],
+ "properties": {
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ }
+ }
},
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
+ "subnetId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
}
+ }
}
- },
- "containerNamespace": {
- "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
+ },
+ "type": {
+ "description": "The type of the IP addresses\n",
+ "type": "string",
+ "enum": [
+ "PV4",
+ "PV6"
+ ]
+ },
+ "addresses": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "isDynamic": {
+ "description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
+ "type": "boolean"
+ },
+ "addressRange": {
+ "description": "An IP address range used, e.g. in case of egress connections. See note.\n",
+ "type": "object",
+ "required": [
+ "minAddress",
+ "maxAddress"
+ ],
+ "properties": {
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ }
+ }
+ },
+ "minAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "maxAddress": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "subnetId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
"type": "string"
+ }
}
- }
- },
- "storageSnapshotResources": {
- "description": "Reference to the \"VirtualStorageResourceInfo\" structure in the \"VnfInstance\" structure that represents the virtual storage resource. See note 2.\n",
- "type": "array",
- "items": {
+ },
+ "virtualCpAddress": {
+ "description": "This type represents information about a network address that has been assigned to a virtual CP.\n",
"type": "object",
- "required": ["storageResourceId"],
+ "required": [
+ "type"
+ ],
"properties": {
- "storageResourceId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "storageSnapshotResources": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes instance the vimLevelResourceType is the type of resource, as would correspond to the kind field if the resource is declared in its own Kubernetes manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the claimName field in the Kubernetes manifest, or a compound name built by Kubernetes if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the metadata.name field in Kubernetes manifest. \n",
- "type": "object",
- "required": ["resourceId"],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceId": {
- "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
- "type": "string"
- },
- "vimLevelAdditionalResourceInfo": {
- "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
- "type": "object",
- "properties": {
- "hostName": {
- "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "persistentVolume": {
- "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
- "type": "string"
- },
- "additionalInfo": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- },
- "containerNamespace": {
- "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
- "type": "string"
- }
- }
- }
+ "type": {
+ "description": "The type of the IP addresses. Permitted values: - IPV4 - IPV6\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
+ },
+ "loadBalancerIp": {
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
+ "type": "string",
+ "format": "IP"
+ },
+ "addressPoolName": {
+ "description": "Name of an address pool from which an IP address is assigned to the virtual CP.",
+ "type": "string"
+ }
+ }
+ }
+ }
+ }
+ },
+ "parentCpId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "vnfLinkPortId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "netAttDefResourceId": {
+ "description": "Identifier of the \"NetAttDefResourceInfo\" structure that provides the specification of the interface to attach the connection point to a secondary container cluster network. See notes 4 and 5. It shall be present if the internal CP is associated to a VNFC realized by one or a set of OS containers and is connected to a secondary container cluster network. It shall not be present otherwise.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ }
+ },
+ "metadata": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ }
+ },
+ "metadata": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ }
+ },
+ "vnfVirtualLinkResourceInfo": {
+ "description": "Information about the virtualised network resources used by the VLs of the VNF instance. See note 5.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by an internal VL instance in a VNF instance.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "vnfVirtualLinkDescId",
+ "networkResource"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfVirtualLinkDescId": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
+ "type": "string"
+ },
+ "networkResource": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would correspond to the ‘kind’ field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the ‘claimName’ field in the Kubernetes® manifest, or a compound name built by Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the ‘metadata.name’ field in Kubernetes® manifest. \n",
+ "type": "object",
+ "required": [
+ "resourceId"
+ ],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceProviderId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "type": "string"
+ },
+ "vimLevelAdditionalResourceInfo": {
+ "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
+ "type": "object",
+ "properties": {
+ "hostName": {
+ "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "persistentVolume": {
+ "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ },
+ "containerNamespace": {
+ "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise. \n",
+ "type": "string"
+ }
+ }
+ },
+ "reservationId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfLinkPorts": {
+ "description": "Links ports of this VL. Shall be present when the linkPort is used for external connectivity by the VNF (refer to VnfLinkPortInfo). May be present otherwise.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "description": "This type represents a link port of an internal VL of a VNF. It shall comply with the provisions defined in table 6.5.3.64-1.\nNOTE 1: Either cpInstanceId with cpInstanceType set to \"EXT_CP\" or any combination of cpInstanceId with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId (i.e. one or both of them) shall be present for a VnfLinkPortInfo. In case both cpInstanceId with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId are present, the two different CP instances share the linkport.\n",
+ "required": [
+ "id",
+ "resourceHandle"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "resourceHandle": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would correspond to the ‘kind’ field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the ‘claimName’ field in the Kubernetes® manifest, or a compound name built by Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the ‘metadata.name’ field in Kubernetes® manifest. \n",
+ "type": "object",
+ "required": [
+ "resourceId"
+ ],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceProviderId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "type": "string"
+ },
+ "vimLevelAdditionalResourceInfo": {
+ "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
+ "type": "object",
+ "properties": {
+ "hostName": {
+ "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "persistentVolume": {
+ "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
}
+ }
+ },
+ "containerNamespace": {
+ "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise. \n",
+ "type": "string"
}
+ }
+ },
+ "cpInstanceId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "cpInstanceType": {
+ "description": "Type of the CP instance that is identified by cpInstanceId. Shall be present if \"cpInstanceId\" is present, and shall be absent otherwise. Permitted values: * VNFC_CP: The link port is connected to a VNFC CP * EXT_CP: The link port is associated to an external CP. See note 1.\n",
+ "type": "string",
+ "enum": [
+ "VNFC_CP",
+ "EXT_CP"
+ ]
},
- "userDefinedData": {
+ "vipCpInstanceId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "trunkResourceId": {
+ "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "metadata": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ }
+ },
+ "virtualStorageResourceInfo": {
+ "description": "Information on the virtualised storage resource(s) used as storage for the VNF instance.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "virtualStorageDescId",
+ "storageResource"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "virtualStorageDescId": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "storageResource": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would correspond to the ‘kind’ field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the ‘claimName’ field in the Kubernetes® manifest, or a compound name built by Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the ‘metadata.name’ field in Kubernetes® manifest. \n",
+ "type": "object",
+ "required": [
+ "resourceId"
+ ],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceProviderId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "type": "string"
+ },
+ "vimLevelAdditionalResourceInfo": {
+ "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
+ "type": "object",
+ "properties": {
+ "hostName": {
+ "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "persistentVolume": {
+ "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "additionalInfo": {
"description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
"type": "object"
+ }
}
+ },
+ "containerNamespace": {
+ "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise. \n",
+ "type": "string"
+ }
}
+ },
+ "reservationId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "metadata": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
}
+ }
},
- "userDefinedData": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
+ "mcioInfo": {
+ "description": "Information on the MCIO(s) representing VNFC instance(s) realized by one or a set of OS containers and created from the same VDU for the VNF instance.\n",
+ "type": "array",
+ "items": {
+ "description": "This type provides information about an MCIO representing the set of VNFC instances realized by one or a set of OS containers which have been created based on the same VDU.\nNOTE 1 The type of MCIO as specified in the declarative descriptor of the MCIO, and that can be read from the CISM. EXAMPLE: In case of MCIOs managed by Kubernetes, the type of MCIO corresponds to the “kind” property of the declarative descriptor. NOTE 2 If the attribute additionalInfo is present, it may contain runtime information on the actual and desired state of the MCIO(s). NOTE 3 When the container infrastructure service is a Kubernetes® instance, the mcioId is the combined values from the kind and name fields of the Kubernetes® resource object, separated by a slash. Example: \"Deployment/abcd\". NOTE 4 When the container infrastructure service is a Kubernetes® instance, the mcioName is the name field of the resource object.",
+ "type": "object",
+ "required": [
+ "mcioId",
+ "mcioName",
+ "mcioNamespace",
+ "vduId",
+ "cismId",
+ "mcioType",
+ "desiredInstances",
+ "availableInstances"
+ ],
+ "properties": {
+ "mcioId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "mcioName": {
+ "description": "Human readable name of this MCIO. See note 4. \n",
+ "type": "string"
+ },
+ "mcioNamespace": {
+ "description": "Namespace of this MCIO.\n",
+ "type": "string"
+ },
+ "vduId": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
+ "type": "string"
+ },
+ "cismId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "mcioType": {
+ "description": "The type of MCIO. Specific values, their semantics and associated MCIO types are defined in clause 6.5.4.13. Additional values are also permitted. See note 1.\n",
+ "type": "string"
+ },
+ "desiredInstances": {
+ "description": "Number of desired MCIO instances.\n",
+ "type": "integer"
+ },
+ "availableInstances": {
+ "description": "Number of available MCIO instances\n",
+ "type": "integer"
+ },
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ }
}
+ }
+ },
+ "metadata": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ },
+ "extensions": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
}
+ }
},
- "_links": {
- "description": "Links to resources related to this resource.\n",
+ "vnfcSnapshots": {
+ "description": "Information about VNFC Snapshots constituting this VNF Snapshot.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents a VNFC Snapshot. It shall comply with the provisions defined in table 6.5.3.77-1. NOTE 1: The identifier of the compute snapshot resource is assigned during creation of a VNFC Snapshot being returned from the VIM as output data in the response message of the individual resource operations. This attribute shall only be present for a VNFC snapshot that has been newly created by the VNFM as a result of the \"Create VNF snapshot task\". NOTE 2: The identifier of the storage snapshot resource is assigned during creation of a VNFC snapshot being returned from the VIM as output data in the response message of the individual resource operations. This attribute shall only be present for a VNFC snapshot with an associated storage resource and that has been newly created by the VNFM as a result of the \"Create VNF snapshot task\".\n",
"type": "object",
- "required": ["self"],
+ "required": [
+ "id",
+ "vnfcInstanceId",
+ "triggeredAt",
+ "createdAt",
+ "vnfcInfoId"
+ ],
"properties": {
- "self": {
- "description": "This type represents a link to a resource.\n",
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfcInstanceId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "creationStartedAt": {
+ "description": "Date-time stamp. Representation: String formatted according toas defined by the date-time production in IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "creationFinishedAt": {
+ "description": "Date-time stamp. Representation: String formatted according toas defined by the date-time production in IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "vnfcResourceInfoId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "computeSnapshotResource": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would correspond to the ‘kind’ field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the ‘claimName’ field in the Kubernetes® manifest, or a compound name built by Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the ‘metadata.name’ field in Kubernetes® manifest. \n",
+ "type": "object",
+ "required": [
+ "resourceId"
+ ],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceProviderId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "type": "string"
+ },
+ "vimLevelAdditionalResourceInfo": {
+ "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
"type": "object",
- "required": ["href"],
"properties": {
- "href": {
- "description": "URI of a resource referenced from a notification. Should be an absolute URI (i.e. a URI that contains {apiRoot}), however, may be a relative URI (i.e. a URI where the {apiRoot} part is omitted) if the {apiRoot} information is not available.\n",
- "type": "string",
- "format": "url"
+ "hostName": {
+ "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "persistentVolume": {
+ "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ },
+ "containerNamespace": {
+ "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise. \n",
+ "type": "string"
+ }
+ }
+ },
+ "storageSnapshotResources": {
+ "description": "Reference to the \"VirtualStorageResourceInfo\" structure in the \"VnfInstance\" structure that represents the virtual storage resource. See note 2.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": [
+ "storageResourceId"
+ ],
+ "properties": {
+ "storageResourceId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "storageSnapshotResources": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance or by an NS instance. Information about the resource is available from the VIM.\nNOTE 1:\tThe value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the CISM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. When the container infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would correspond to the ‘kind’ field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition. NOTE 2:\tWhen the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the following way: * For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide per resource type. * For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, i.e. the value of the ‘claimName’ field in the Kubernetes® manifest, or a compound name built by Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own manifest. * For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of the ‘metadata.name’ field in Kubernetes® manifest. \n",
+ "type": "object",
+ "required": [
+ "resourceId"
+ ],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceProviderId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Additional resource information which is specific to this resource and its type, and which is available from the VIM or the CISM or the resource provider. See note 1.\n",
+ "type": "string"
+ },
+ "vimLevelAdditionalResourceInfo": {
+ "description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider. NOTE:\tAt least one attribute shall be present. \n",
+ "type": "object",
+ "properties": {
+ "hostName": {
+ "description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "persistentVolume": {
+ "description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note. \n",
+ "type": "string"
+ },
+ "additionalInfo": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ },
+ "containerNamespace": {
+ "description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise. \n",
+ "type": "string"
}
+ }
}
+ }
}
+ },
+ "userDefinedData": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ }
+ },
+ "userDefinedData": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ }
+ }
+ },
+ "_links": {
+ "description": "Links to resources related to this resource.\n",
+ "type": "object",
+ "required": [
+ "self"
+ ],
+ "properties": {
+ "self": {
+ "description": "This type represents a link to a resource.\n",
+ "type": "object",
+ "required": [
+ "href"
+ ],
+ "properties": {
+ "href": {
+ "description": "URI of a resource referenced from a notification. Should be an absolute URI (i.e. a URI that contains {apiRoot}), however, may be a relative URI (i.e. a URI where the {apiRoot} part is omitted) if the {apiRoot} information is not available.\n",
+ "type": "string",
+ "format": "url"
}
+ }
}
+ }
}
+ }
}
-}
\ No newline at end of file
+ }
\ No newline at end of file
diff --git a/SOL005/NSPerformanceManagement-API/ApiVersion.robot b/SOL005/NSPerformanceManagement-API/ApiVersion.robot
index ab7fd566544c93d15da50d2580044deafaca2bb9..d106728c227b25fda98cba01186d64ca35e66c33 100644
--- a/SOL005/NSPerformanceManagement-API/ApiVersion.robot
+++ b/SOL005/NSPerformanceManagement-API/ApiVersion.robot
@@ -13,7 +13,7 @@ POST API Version - Method not implemented
... Test title: POST API version - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -25,7 +25,7 @@ GET API Version
... Test title: GET API Version
... Test objective: The objective is to test that GET method successfully return ApiVersionInformation
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -38,7 +38,7 @@ PUT API Version - Method not implemented
... Test title: PUT API Version - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -50,7 +50,7 @@ PATCH API Version - Method not implemented
... Test title: PATCH API Version - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -62,7 +62,7 @@ DELETE API Version - Method not implemented
... Test title: DELETE API Version - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -74,7 +74,7 @@ POST API Version with apiMajorVerion - Method not implemented
... Test title: POST API version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -86,7 +86,7 @@ GET API Version with apiMajorVerion
... Test title: GET API Version with apiMajorVerion
... Test objective: The objective is to test that GET method successfully return ApiVersionInformation
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -99,7 +99,7 @@ PUT API Version with apiMajorVerion - Method not implemented
... Test title: PUT API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -111,7 +111,7 @@ PATCH API Version with apiMajorVerion - Method not implemented
... Test title: PATCH API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -123,7 +123,7 @@ DELETE API Version with apiMajorVerion - Method not implemented
... Test title: DELETE API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/NSPerformanceManagement-API/IndividualPmJob.robot b/SOL005/NSPerformanceManagement-API/IndividualPmJob.robot
index 5cdc8137874297cfc9344b745ced13d7386330a4..95c3605c602610606e5f388f7b2a087bb51c09f3 100644
--- a/SOL005/NSPerformanceManagement-API/IndividualPmJob.robot
+++ b/SOL005/NSPerformanceManagement-API/IndividualPmJob.robot
@@ -16,7 +16,7 @@ GET individual NS Performance Job
... Test title: Get individual NS Performance Job
... Test objective: The objective is to test the retrieval of an individual NS Performance monitoring job and perform a JSON schema and content validation of the collected job data structure
... Pre-conditions: A NS instance is instantiated. One or more NS Performance jobs are set in the NFVO.
- ... Reference: Clause 7.4.3.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 7.4.3.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -30,7 +30,7 @@ GET individual NS Performance Job with invalid resource identifier
... Test title: Get individual NS Performance Job with invalid resource identifier
... Test objective: The objective is to test that the retrieval of an individual NS Performance monitoring job fails when using an invalid resource identifier, and perform the JSON schema validation of the failed operation HTTP response
... Pre-conditions: A NS instance is instantiated. One or more NS Performance jobs are set in the NFVO.
- ... Reference: Clause 7.4.3.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 7.4.3.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -43,7 +43,7 @@ DELETE Individual NS Performance Job with invalid resource identifier
... Test title: Delete individual NS Performance Job with invalid resource identifier
... Test objective: The objective is to test that the deletion of an individual NS Performance monitoring job fails when using an invalid resource identifier
... Pre-conditions: A NS instance is instantiated. One or more NS Performance jobs are set in the NFVO.
- ... Reference: Clause 7.4.3.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 7.4.3.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -55,7 +55,7 @@ POST Individual NS Performance Job - Method not implemented
... Test title: POST Individual NS Performance Job - method not implemented
... Test objective: The objective is to test that POST method is not allowed to create a new NS Performance Monitoring Job
... Pre-conditions: none
- ... Reference: Clause 7.4.3.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 7.4.3.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -67,7 +67,7 @@ PUT Individual NS Performance Job - Method not implemented
... Test title: PUT Individual NS Performance Job - method not implemented
... Test objective: The objective is to test that PUT method is not allowed to update an existing NS Performance Monitoring Job
... Pre-conditions: none
- ... Reference: Clause 7.4.3.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 7.4.3.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -79,7 +79,7 @@ PATCH Individual NS Performance Job
... Test title: PATCH Individual NS Performance Job
... Test objective: The objective is to test that PATCH method modify an existing new NS Performance Monitoring Job
... Pre-conditions: A NS instance is instantiated. One or more NS performance jobs are set in the NFVO.
- ... Reference: Clause 6.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 6.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: Resource modified
@@ -92,7 +92,7 @@ DELETE Individual NS Performance Job
... Test title: Delete Individual NS Performance Job
... Test objective: The objective is to test the deletion of an individual NS Performance monitoring job
... Pre-conditions: A NS instance is instantiated. One or more NS Performance jobs are set in the NFVO.
- ... Reference: Clause 7.4.3.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 7.4.3.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: The NS Performance Job is no more available in the NFVO
@@ -105,23 +105,36 @@ PATCH Individual NS Performance Job - Precondition failed
... Test title: PATCH Individual NS Performance Job - Precondition failed
... Test objective: The objective is to attempt to Modify an individual NS Performance job fails, where the precondition was not met
... Pre-conditions: The related job already exist
- ... Reference: Clause 7.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 7.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: The resource is not modified
Send Patch request for individual NS Performance Job - Etag mismatch
Check HTTP Response Status Code Is 412
Check HTTP Response Body Json Schema Is ProblemDetails
+
+PATCH Individual NS Performance Job - Precondition failed HTTP Conditional Request Not Supported
+ [Documentation] Test ID: 5.3.4.2.8b
+ ... Test title: PATCH Individual NS Performance Job - Precondition failed HTTP Conditional Request Not Supported
+ ... Test objective: The objective is to attempt to Modify an individual NS Performance job fails, where the API Producer does not support "Last-Modified" and "ETag" HTTP Headers
+ ... Pre-conditions: The related job already exist
+ ... Reference: Clause 7.4.3.3.4, 4.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
+ ... Config ID: Config_prod_NFVO
+ ... Applicability: API Producer does not support "Last-Modified" and "ETag" HTTP Headers
+ ... Post-Conditions: The resource is not modified
+ Send Patch request for individual NS Performance Job - HTTP Conditional Request not supported
+ Check HTTP Response Status Code Is 412
+ Check HTTP Response Body Json Schema Is ProblemDetails
-PATCH Individual NS Performance Job - Unprocessable Entity
+PATCH Individual NS Performance Job - Unprocessable Content
[Documentation] Test ID: 5.3.4.2.9
- ... Test title: PATCH Individual NS Performance Job - Unprocessable Entity
+ ... Test title: PATCH Individual NS Performance Job - Unprocessable Content
... Test objective: The objective is to test that PATCH method cannot modify an exsisting individual PM job resource when a request contains syntactically correct data but the data cannot be processed.
... Pre-conditions: A NS instance is instantiated. One or more NS performance jobs are set in the NFVO.
- ... Reference: Clause 7.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 7.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
- Send Patch request for individual NS Performance Job with unprocessable entity
+ Send Patch request for individual NS Performance Job with unprocessable content
Check HTTP Response Status Code Is 422
Check HTTP Response Body Json Schema Is ProblemDetails
diff --git a/SOL005/NSPerformanceManagement-API/IndividualReport.robot b/SOL005/NSPerformanceManagement-API/IndividualReport.robot
index 3b8d7ae460628a6ec4ca367438f6d39b60e37ff6..f848fdbc5d157b8443a1ea61c711eb2e54d32de2 100644
--- a/SOL005/NSPerformanceManagement-API/IndividualReport.robot
+++ b/SOL005/NSPerformanceManagement-API/IndividualReport.robot
@@ -11,7 +11,7 @@ Get Individual Performance Report
... Test title: Get Individual Performance Report
... Test objective: The objective is to test the retrieval of an individual NS performance report associated to a monitoring job and perform a JSON schema validation of the collected report data structure
... Pre-conditions: A NS instance is instantiated. One or more NS performance reports are set for a monitoring job in the NFVO.
- ... Reference: Clause 7.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 7.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -24,7 +24,7 @@ Get Individual Performance Report with invalid resource endpoint
... Test title: Get Individual Performance Report with invalid resource endpoint
... Test objective: The objective is to test that the retrieval of an individual NS performance report associated to a monitoring job fails when using an invalid resource endpoint
... Pre-conditions: A NS instance is instantiated. One or more NS performance reports are set for a monitoring job in the NFVO.
- ... Reference: Clause 7.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 7.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -37,7 +37,7 @@ POST Individual Performance Report - Method not implemented
... Test title: POST Individual Performance Report - Method not implemented
... Test objective: The objective is to test that POST method is not allowed to create a new NS performance report within a monitoring job
... Pre-conditions: none
- ... Reference: Clause 7.4.4.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 7.4.4.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -49,7 +49,7 @@ PUT Individual Performance Report - Method not implemented
... Test title: PUT Individual Performance Report - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to update an existing NS performance report within a monitoring job
... Pre-conditions: none
- ... Reference: Clause 7.4.4.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 7.4.4.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -61,7 +61,7 @@ PATCH Individual Performance Report - Method not implemented
... Test title: PATCH Individual Performance Report - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to modify an existing NS performance report within a monitoring job
... Pre-conditions: none
- ... Reference: Clause 7.4.4.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 7.4.4.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -73,7 +73,7 @@ DELETE Individual Performance Report - Method not implemented
... Test title: DELETE Individual Performance Report - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to delete an existing NS performance report within a monitoring job
... Pre-conditions: none
- ... Reference: Clause 7.4.4.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 7.4.4.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/NSPerformanceManagement-API/IndividualThreshold.robot b/SOL005/NSPerformanceManagement-API/IndividualThreshold.robot
index 6cef2d8ab09405adba56994cc6021869b92b854e..8fc83339db3418689faf1c37e3eff3a3e811462d 100644
--- a/SOL005/NSPerformanceManagement-API/IndividualThreshold.robot
+++ b/SOL005/NSPerformanceManagement-API/IndividualThreshold.robot
@@ -18,7 +18,7 @@ GET Individual Threshold
... Test title: GET Individual Threshold
... Test objective: The objective is to test the retrieval of an individual NS performance threshold and perform a JSON schema and content validation of the collected threshold data structure
... Pre-conditions: A NS instance is instantiated. One or more NS performance thresholds are set in the NFVO.
- ... Reference: Clause 7.4.6.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 7.4.6.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -32,7 +32,7 @@ GET Individual Threshold with invalid resource identifier
... Test title: GET Individual Threshold with invalid resource identifier
... Test objective: The objective is to test that the retrieval of an individual NS performance threshold fails when using an invalid resource identifier
... Pre-conditions: A NS instance is instantiated. One or more NS performance jobs are set in the NFVO.
- ... Reference: Clause 7.4.6.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 7.4.6.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -45,7 +45,7 @@ DELETE Individual Threshold with invalid resource identifier
... Test title: DELETE Individual Threshold with invalid resource identifier
... Test objective: The objective is to test the deletion of an individual NS performance threshold
... Pre-conditions: A NS instance is instantiated. One or more NS performance thresholds are set in the NFVO.
- ... Reference: Clause 7.4.6.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 7.4.6.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -57,7 +57,7 @@ POST Individual Threshold - Method not implemented
... Test title: POST Individual Threshold - Method not implemented
... Test objective: The objective is to test that POST method is not allowed to create a new NS performance Threshold
... Pre-conditions: A NS instance is instantiated
- ... Reference: Clause 7.4.6.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 7.4.6.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -69,7 +69,7 @@ PUT Individual Threshold - Method not implemented
... Test title: PUT Individual Threshold - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to update an existing NS performance threshold
... Pre-conditions: A NS instance is instantiated. One or more NS performance thresholds are set in the NFVO.
- ... Reference: Clause 7.4.6.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 7.4.6.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -81,7 +81,7 @@ PATCH Individual Threshold
... Test title: PATCH Individual Threshold
... Test objective: The objective is to test that PATCH method modify an existing NS performance threshold
... Pre-conditions: A NS instance is instantiated. One or more NS performance thresholds are set in the NFVO.
- ... Reference: Clause 7.4.6.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 7.4.6.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: The NS performance Threshold is modified by the operation
@@ -95,7 +95,7 @@ DELETE Individual Threshold
... Test title: DELETE Individual Threshold
... Test objective: The objective is to test the deletion of an individual NS performance threshold
... Pre-conditions: A NS instance is instantiated. One or more NS performance thresholds are set in the NFVO.
- ... Reference: Clause 7.4.6.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 7.4.6.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: The NS performance Threshold is not available anymore in the NFVO
@@ -108,7 +108,7 @@ PATCH Individual Threshold - Precondition failed
... Test title: PATCH Individual Threshold - Precondition failed
... Test objective: The objective is to attempt to Modify an individual NS Performance threshold fails, where the precondition was not met
... Pre-conditions: A NS instance is instantiated. One or more NS performance thresholds are set in the NFVO.
- ... Reference: Clause 7.4.6.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 7.4.6.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: The NS performance Threshold is not modified by the operation
@@ -116,17 +116,31 @@ PATCH Individual Threshold - Precondition failed
Check HTTP Response Status Code Is 412
Check HTTP Response Body Json Schema Is ProblemDetails
Check Postcondition NS performance Threshold is Unmodified (Implicit)
+
+PATCH Individual Threshold - Precondition failed HTTP Conditional Request Not Supported
+ [Documentation] Test ID: 5.3.4.5.8b
+ ... Test title: PATCH Individual Threshold - Precondition failed HTTP Conditional Request Not Supported
+ ... Test objective: The objective is to attempt to Modify an individual NS Performance threshold fails, where the API Producer does not support "Last-Modified" and "ETag" HTTP Headers
+ ... Pre-conditions: A NS instance is instantiated. One or more NS performance thresholds are set in the NFVO.
+ ... Reference: Clause 7.4.6.3.4, 4.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
+ ... Config ID: Config_prod_NFVO
+ ... Applicability: API Producer does not support "Last-Modified" and "ETag" HTTP Headers
+ ... Post-Conditions: The NS performance Threshold is not modified by the operation
+ Send Patch request for individual NS performance Threshold - HTTP Conditional Request not supported
+ Check HTTP Response Status Code Is 412
+ Check HTTP Response Body Json Schema Is ProblemDetails
+ Check Postcondition NS performance Threshold is Unmodified (Implicit)
-PATCH Individual Threshold - Unprocessable Entity
+PATCH Individual Threshold - Unprocessable Content
[Documentation] Test ID: 5.3.4.2.9
- ... Test title: PATCH Individual NS Performance Job - Unprocessable Entity
+ ... Test title: PATCH Individual NS Performance Job - Unprocessable Content
... Test objective: The objective is to test that PATCH method cannot modify an exsisting individual PM job resource when a request contains syntactically correct data but the data cannot be processed.
... Pre-conditions: A NS instance is instantiated. One or more NS performance jobs are set in the NFVO.
- ... Reference: Clause 7.4.6.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 7.4.6.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: The NS performance Threshold is not modified by the operation
- Send Patch request for Individual Threshold with unprocessable entity
+ Send Patch request for Individual Threshold with unprocessable content
Check HTTP Response Status Code Is 422
Check HTTP Response Body Json Schema Is ProblemDetails
- Check Postcondition NS performance Threshold is Unmodified (Implicit)
\ No newline at end of file
+ Check Postcondition NS performance Threshold is Unmodified (Implicit)
diff --git a/SOL005/NSPerformanceManagement-API/NSPerformanceManagementKeywords.robot b/SOL005/NSPerformanceManagement-API/NSPerformanceManagementKeywords.robot
index 15bd31168def8ee935e6ffe258e9f40b4f234413..515ed39350367af5d762d18e8fa5aab760c21151 100644
--- a/SOL005/NSPerformanceManagement-API/NSPerformanceManagementKeywords.robot
+++ b/SOL005/NSPerformanceManagement-API/NSPerformanceManagementKeywords.robot
@@ -106,7 +106,7 @@ Send Post Request Create new NS Performance Monitoring Job
Clear Requests ${callback_endpoint}
-Send POST request for NS Performance Monitoring Job with unprocessable entity
+Send POST request for NS Performance Monitoring Job with unprocessable content
Log trying to create a new NS PM Job
Set Headers {"Accept": "${ACCEPT_JSON}"}
Set Headers {"Content-Type": "${CONTENT_TYPE_JSON}"}
@@ -293,8 +293,27 @@ Send Patch request for individual NS Performance Job - Etag mismatch
Verify Mock Expectation ${notification_request}
Clear Requests ${callback_endpoint}
+Send Patch request for individual NS Performance Job - HTTP Conditional Request not supported
+ Pass Execution If ${PRODUCER_SUPPORT_COND_REQ} == 1 NVFO allows conditional requests, skipping test
+ Log Trying to perform a PATCH
+ Set Headers {"Accept": "${ACCEPT_JSON}"}
+ Set Headers {"Content-Type": "${CONTENT_TYPE_PATCH}"}
+ Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"${AUTHORIZATION_HEADER}":"${AUTHORIZATION_TOKEN}"}
+ ${template}= Get File jsons/PmJobModifications.json
+ ${body}= Format String ${template} callbackUri=${callback_uri} callbackEndpoint=${callback_endpoint} callbackPort=${callback_port}
+ Log Creating mock request and response to handle GET operation on notification endpoint
+ &{notification_request}= Create Mock Request Matcher GET ${callback_endpoint}
+ &{notification_response}= Create Mock Response status_code=204
+ Log Issue the request
+ Create Mock Expectation ${notification_request} ${notification_response}
+ PATCH ${apiRoot}/${apiName}/${apiMajorVersion}/pm_jobs/${pmJobId} ${body}
+ ${output}= Output response
+ Set Suite Variable ${response} ${output}
+ Log Verify producer tested the notification endpoint
+ Verify Mock Expectation ${notification_request}
+ Clear Requests ${callback_endpoint}
-Send Patch request for individual NS Performance Job with unprocessable entity
+Send Patch request for individual NS Performance Job with unprocessable content
Set Headers {"Accept":"${ACCEPT_JSON}"}
Set Headers {"Content-Type": "${CONTENT_TYPE_PATCH}"}
Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"${AUTHORIZATION_HEADER}":"${AUTHORIZATION_TOKEN}"}
@@ -433,7 +452,7 @@ Send Post Request Create new Performance Threshold
Verify Mock Expectation ${notification_request}
Clear Requests ${callback_endpoint}
-Send POST request for Performance threshold with unprocessable entity
+Send POST request for Performance threshold with unprocessable content
Log Creating a new Threshold
Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"${AUTHORIZATION_HEADER}":"${AUTHORIZATION_TOKEN}"}
Set Headers {"Accept": "${ACCEPT_JSON}"}
@@ -579,8 +598,28 @@ Send Patch request for individual NS performance Threshold - Etag mismatch
Log Verify producer tested the notification endpoint
Verify Mock Expectation ${notification_request}
Clear Requests ${callback_endpoint}
+
+Send Patch request for individual NS performance Threshold - HTTP Conditional Request not supported
+ Pass Execution If ${PRODUCER_SUPPORT_COND_REQ} == 1 NVFO allows conditional requests, skipping test
+ Log Trying to PUT threshold
+ Set Headers {"Accept": "${ACCEPT_JSON}"}
+ Set Headers {"Content-Type": "${CONTENT_TYPE_PATCH}"}
+ Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"${AUTHORIZATION_HEADER}":"${AUTHORIZATION_TOKEN}"}
+ ${template}= Get File jsons/ThresholdModifications.json
+ ${body}= Format String ${template} callbackUri=${callback_uri} callbackEndpoint=${callback_endpoint} callbackPort=${callback_port}
+ Log Creating mock request and response to handle GET operation on notification endpoint
+ &{notification_request}= Create Mock Request Matcher GET ${callback_endpoint}
+ &{notification_response}= Create Mock Response status_code=204
+ Log Issue the request
+ Create Mock Expectation ${notification_request} ${notification_response}
+ PATCH ${apiRoot}/${apiName}/${apiMajorVersion}/thresholds/${thresholdId} ${body}
+ ${output}= Output response
+ Set Suite Variable ${response} ${output}
+ Log Verify producer tested the notification endpoint
+ Verify Mock Expectation ${notification_request}
+ Clear Requests ${callback_endpoint}
-Send Patch request for Individual Threshold with unprocessable entity
+Send Patch request for Individual Threshold with unprocessable content
Set Headers {"Accept":"${ACCEPT_JSON}"}
Set Headers {"Content-Type": "${CONTENT_TYPE_PATCH}"}
Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"${AUTHORIZATION_HEADER}":"${AUTHORIZATION_TOKEN}"}
@@ -647,4 +686,4 @@ Check Notification Endpoint
Check HTTP Response Header Contains Location
${linkURL}= Get Value From Json ${response['headers']} $..Link
- Should Not Be Empty ${linkURL}
\ No newline at end of file
+ Should Not Be Empty ${linkURL}
diff --git a/SOL005/NSPerformanceManagement-API/NotificationEndpoint.robot b/SOL005/NSPerformanceManagement-API/NotificationEndpoint.robot
index 7bc788615474002d9acfe0a05b119c0255d29987..a4519edea9e086b25953081c48c2a76232790ef0 100644
--- a/SOL005/NSPerformanceManagement-API/NotificationEndpoint.robot
+++ b/SOL005/NSPerformanceManagement-API/NotificationEndpoint.robot
@@ -13,7 +13,7 @@ NS Performance Information Availability Notification
... Test title: NS Performance Information Availability Notification
... Test objective: The objective is to test that NS Performance Information Availability Notification is delivered with success to the notification consumer
... Pre-conditions: A NS performance job is created, and information availability notifications is available in the NFVO.
- ... Reference: Clause 7.4.9.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 7.4.9.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
@@ -25,7 +25,7 @@ NS Threshold Crossed Notification
... Test title: NS Threshold Crossed Notification
... Test objective: The objective is to test that NS Threshold Crossed Notification is delivered with success to the notification consumer
... Pre-conditions: A NS performance job is created, and threshold crossed notifications is available in the NFVO.
- ... Reference: Clause 7.4.9.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 7.4.9.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/NSPerformanceManagement-API/Notifications.robot b/SOL005/NSPerformanceManagement-API/Notifications.robot
index b88feb22e739460c64445f9ea09115d2d3be2350..5874b6f2fabd3885e2de4038b70a8a5d3ca25424 100644
--- a/SOL005/NSPerformanceManagement-API/Notifications.robot
+++ b/SOL005/NSPerformanceManagement-API/Notifications.robot
@@ -16,7 +16,7 @@ NS Performance Information Availability Notification
... Test title: NS Performance Information Availability Notification
... Test objective: The objective is to test the dispatch of NS Performance Information Availability Notification when new NS performance information is available in the NFVO, and perform a JSON schema and content validation of the delivered notification. The action that triggers the notification under test is an explicit test step, but it is not performed by the test system.
... Pre-conditions: A NS performance job is created, and a subscription for information availability notifications is available in the NFVO.
- ... Reference: Clause 7.4.9.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 7.4.9.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -29,7 +29,7 @@ NS Threshold Crossed Notification
... Test title: NS Threshold Crossed Notification
... Test objective: The objective is to test the dispatch of NS Threshold Crossed Notification when a previously set NS performance metric threshold is crossed, and perform a JSON schema and content validation of the delivered notification. The action that triggers the notification under test is an explicit test step, but it is not performed by the test system.
... Pre-conditions: A NS performance job is created, and a threshold subscription is available in the NFVO.
- ... Reference: Clause 7.4.9.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 7.4.9.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/NSPerformanceManagement-API/PMJobs.robot b/SOL005/NSPerformanceManagement-API/PMJobs.robot
index 1525374ec72e212672590eaf8e998bb04428cea2..2593818b4b8e3cdbedb023f3ddc9ee83a679e759 100644
--- a/SOL005/NSPerformanceManagement-API/PMJobs.robot
+++ b/SOL005/NSPerformanceManagement-API/PMJobs.robot
@@ -17,7 +17,7 @@ GET all NS Performance Monitoring Jobs
... Test title: GET all NS Performance Monitoring Jobs
... Test objective: The objective is to test the retrieval of all the available NS performance monitoring jobs and perform a JSON schema and content validation of the collected jobs data structure
... Pre-conditions: A NS instance is instantiated. One or more NS performance jobs are set in the NFVO.
- ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -31,7 +31,7 @@ GET NS Performance Monitoring Jobs with attribute-based filter
... Test title: GET all NS Performance Monitoring Jobs with attribute-based filter
... Test objective: The objective is to test the retrieval of NS performance monitoring jobs using attribute-based filter, perform a JSON schema validation of the collected jobs data structure, and verify that the retrieved information matches the issued attribute-based filter
... Pre-conditions: A NS instance is instantiated. One or more NS performance jobs are set in the NFVO.
- ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -45,7 +45,7 @@ GET all NS Performance Monitoring Jobs with "all_fields" attribute selector
... Test title: GET all NS Performance Monitoring Jobs with "all_fields" attribute selector
... Test objective: The objective is to test the retrieval of all NS performance monitoring jobs "all_fields" attribute selector, perform a JSON schema validation of the collected jobs data structure, and verify that the retrieved information matches the issued "all_fileds" selector
... Pre-conditions: A NS instance is instantiated. One or more NS performance jobs are set in the NFVO.
- ... Reference: Clause 4.3.3.2.1, 7.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 4.3.3.2.1, 7.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -59,7 +59,7 @@ GET all NS Performance Monitoring Jobs with "exclude_default" attribute selector
... Test title: GET all NS Performance Monitoring Jobs with "exclude_default" attribute selector
... Test objective: The objective is to test the retrieval of all NS performance monitoring jobs "exclude_default" attribute selector, perform a JSON schema validation of the collected jobs data structure, and verify that the retrieved information matches the issued "exclude_default" selector
... Pre-conditions: A NS instance is instantiated. One or more NS performance jobs are set in the NFVO.
- ... Reference: Clause 4.3.3.2.1, 7.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 4.3.3.2.1, 7.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -73,7 +73,7 @@ GET all NS Performance Monitoring Jobs with "fields" attribute selector
... Test title: GET all NS Performance Monitoring Jobs with "fields" attribute selector
... Test objective: The objective is to test the retrieval of all NS performance monitoring jobs "fields" attribute selector, perform a JSON schema validation of the collected jobs data structure, and verify that the retrieved information matches the issued "include" selector
... Pre-conditions: A NS instance is instantiated. One or more NS performance jobs are set in the NFVO.
- ... Reference: Clause 4.3.3.2.1, 7.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 4.3.3.2.1, 7.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO supports the use of "include" attribute selector
... Post-Conditions: none
@@ -87,7 +87,7 @@ GET all NS Performance Monitoring Jobs with "exclude" attribute selector
... Test title: GET all NS Performance Monitoring Jobs with exclude_fields attribute selector
... Test objective: The objective is to test the retrieval of all NS performance monitoring jobs "exclude" attribute selector, perform a JSON schema validation of the collected jobs data structure, and verify that the retrieved information matches the issued "exclude" selector
... Pre-conditions: A NS instance is instantiated. One or more NS performance jobs are set in the NFVO.
- ... Reference: Clause 4.3.3.2.1, 7.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 4.3.3.2.1, 7.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO supports the use of "exclude" attribute selector
... Post-Conditions: none
@@ -101,7 +101,7 @@ GET NS Performance Monitoring Jobs with invalid attribute-based filter
... Test title: GET NS Performance Monitoring Jobs with invalid attribute-based filter
... Test objective: The objective is to test that the retrieval of NS performance monitoring jobs fails when using invalid attribute-based filter, and perform the JSON schema validation of the failed operation HTTP response
... Pre-conditions: A NS instance is instantiated. One or more NS performance jobs are set in the NFVO.
- ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -114,7 +114,7 @@ GET NS Performance Monitoring Jobs with invalid resource endpoint
... Test title: GET NS Performance Monitoring Jobs with invalid resource endpoint
... Test objective: The objective is to test that the retrieval of NS performance monitoring jobs fails when using invalid resource endpoint
... Pre-conditions: A NS instance is instantiated. One or more NS performance jobs are set in the NFVO.
- ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -127,7 +127,7 @@ Create new NS Performance Monitoring Job
... Test title: Create a new NS Performance Monitoring Job
... Test objective: The objective is to test the creation of a new NS performance monitoring job and perform the JSON schema validation of the returned job data structure
... Pre-conditions: A NS instance is instantiated. One or more NS performance jobs are set in the NFVO.
- ... Reference: Clause 7.4.2.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 7.4.2.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: The NS Performance Job is successfully created on the NFVO
@@ -141,7 +141,7 @@ PUT all NS Performance Monitoring Jobs - Method not implemented
... Test title: PUT all NS Performance Monitoring Jobs - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to modify NS Performance Monitoring Jobs
... Pre-conditions: A NS instance is instantiated. One or more NS performance jobs are set in the NFVO.
- ... Reference: Clause 7.4.2.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 7.4.2.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -153,7 +153,7 @@ PATCH all NS Performance Monitoring Jobs - Method not implemented
... Test title: PATCH all NS Performance Monitoring Jobs - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update NS Performance Monitoring Jobs
... Pre-conditions: A NS instance is instantiated. One or more NS performance jobs are set in the NFVO.
- ... Reference: Clause 7.4.2.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 7.4.2.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -165,7 +165,7 @@ DELETE all NS Performance Monitoring Jobs - Method not implemented
... Test title: DELETE all NS Performance Monitoring Jobs - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to delete NS Performance Monitoring Jobs
... Pre-conditions: A NS instance is instantiated. One or more NS performance jobs are set in the NFVO.
- ... Reference: Clause 7.4.2.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 7.4.2.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -177,7 +177,7 @@ GET all NS Performance Monitoring Jobs as Paged Response
... Test title: GET all NS Performance Monitoring Jobs as Paged Response
... Test objective: The objective is to test the retrieval of all the available NS performance monitoring jobs as paged response.
... Pre-conditions: A NS instance is instantiated. One or more NS performance jobs are set in the NFVO.
- ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -190,7 +190,7 @@ GET NS Performance Monitoring Jobs - Bad Request Response too Big
... Test title: GET NS Performance Monitoring Jobs - Bad Request Response too Big
... Test objective: The objective is to test that the retrieval of NS performance monitoring jobs fails because reponse is too big, and perform the JSON schema validation of the failed operation HTTP response
... Pre-conditions: A NS instance is instantiated. One or more NS performance jobs are set in the NFVO.
- ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -203,7 +203,7 @@ GET all NS Performance Monitoring Jobs with "fields" and "exclude_default" attri
... Test title: GET all NS Performance Monitoring Jobs with "fields" and "exclude_default" attribute selector
... Test objective: The objective is to test the retrieval of all NS performance monitoring jobs "fields" and "exclude_default" attribute selector, perform a JSON schema validation of the collected jobs data structure, and verify that the retrieved information matches the issued selector
... Pre-conditions: A NS instance is instantiated. One or more NS performance jobs are set in the NFVO.
- ... Reference: Clause 4.3.3.2.1, 7.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 4.3.3.2.1, 7.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO supports the use of "include" attribute selector
... Post-Conditions: none
@@ -212,15 +212,15 @@ GET all NS Performance Monitoring Jobs with "fields" and "exclude_default" attri
Check HTTP Response Body Json Schema Is PmJobs
Check HTTP Response Body PmJobs Matches the requested selector
-POST new NS Performance Monitoring Job - Unprocessable Entity
+POST new NS Performance Monitoring Job - Unprocessable Content
[Documentation] Test ID: 5.3.4.1.16
- ... Test title: POST new NS Performance Monitoring Job - Unprocessable Entity
+ ... Test title: POST new NS Performance Monitoring Job - Unprocessable Content
... Test objective: The objective is to test the creation of a new NS performance monitoring job fails when a request contains syntactically correct data but the data cannot be processed.
... Pre-conditions: A NS instance is instantiated. One or more NS performance jobs are set in the NFVO.
- ... Reference: clause 7.4.2.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: clause 7.4.2.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
- Send POST request for NS Performance Monitoring Job with unprocessable entity
+ Send POST request for NS Performance Monitoring Job with unprocessable content
Check HTTP Response Status Code Is 422
- Check HTTP Response Body Json Schema Is ProblemDetails
\ No newline at end of file
+ Check HTTP Response Body Json Schema Is ProblemDetails
diff --git a/SOL005/NSPerformanceManagement-API/Thresholds.robot b/SOL005/NSPerformanceManagement-API/Thresholds.robot
index 832c4e5c3cd0a8d0762cb8a5407bae1158be5c4e..f2f8a5cad858b71bb6b34307e2e2d0727fef997d 100644
--- a/SOL005/NSPerformanceManagement-API/Thresholds.robot
+++ b/SOL005/NSPerformanceManagement-API/Thresholds.robot
@@ -18,7 +18,7 @@ GET All Performance Thresholds
... Test title: GET All Performance Thresholds
... Test objective: The objective is to test the retrieval of all the available NS performance thresholds and perform a JSON schema validation of the collected thresholds data structure
... Pre-conditions: A NS instance is instantiated. One or more NS performance thresholds are set in the NFVO.
- ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -31,7 +31,7 @@ GET Performance Thresholds with attribute-based filter
... Test title: GET Performance Thresholds with attribute-based filter
... Test objective: The objective is to test the retrieval of all the available NS performance thresholds when using attribute-based filters, perform a JSON schema validation of the collected thresholds data structure, and verify that the retrieved information matches the issued attribute-based filter
... Pre-conditions: A NS instance is instantiated. One or more NS performance thresholds are set in the NFVO.
- ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -45,7 +45,7 @@ GET Performance Thresholds with invalid attribute-based filter
... Test title: GET Performance Thresholds with invalid attribute-based filter
... Test objective: The objective is to test that the retrieval of NS performance thresholds fails when using invalid attribute-based filter, and perform the JSON schema validation of the failed operation HTTP response
... Pre-conditions: A NS instance is instantiated. One or more NS performance thresholds are set in the NFVO.
- ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -58,7 +58,7 @@ GET Performance Thresholds with invalid resource endpoint
... Test title: GET Performance Thresholds with invalid resource endpoint
... Test objective: The objective is to test that the retrieval of NS performance thresholds fails when using invalid resource endpoint, and perform the JSON schema validation of the failed operation HTTP response
... Pre-conditions: A NS instance is instantiated. One or more NS performance thresholds are set in the NFVO.
- ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -71,7 +71,7 @@ Create new Performance Threshold
... Test title: Create new Performance Threshold
... Test objective: The objective is to test the creation of a new NS performance threshold and perform the JSON schema validation of the returned threshold data structure
... Pre-conditions: A NS instance is instantiated.
- ... Reference: Clause 7.4.5.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 7.4.5.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: The NS performance Threshold is successfully created on the NFVO
@@ -86,7 +86,7 @@ PUT Performance Thresholds - Method not implemented
... Test title: PUT Performance Thresholds - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to modify NS performance Thresholds
... Pre-conditions: A NS instance is instantiated. One or more NS performance thresholds are set in the NFVO.
- ... Reference: Clause 7.4.5.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 7.4.5.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -98,7 +98,7 @@ PATCH Performance Thresholds - Method not implemented
... Test title: PATCH Performance Thresholds - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to modify NS performance Thresholds
... Pre-conditions: A NS instance is instantiated. One or more NS performance thresholds are set in the NFVO.
- ... Reference: Clause 7.4.5.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 7.4.5.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -110,7 +110,7 @@ DELETE Performance Thresholds - Method not implemented
... Test title: DELETE Performance Thresholds - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to update NS performance Thresholds
... Pre-conditions: A NS instance is instantiated. One or more NS performance thresholds are set in the NFVO.
- ... Reference: Clause 7.4.5.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 7.4.5.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -122,7 +122,7 @@ GET All Performance Thresholds as Paged Response
... Test title: GET All Performance Thresholds as Paged Response
... Test objective: The objective is to test the retrieval of all the available NS performance thresholds as paged response.
... Pre-conditions: A NS instance is instantiated. One or more NS performance thresholds are set in the NFVO.
- ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -135,7 +135,7 @@ GET Performance Thresholds - Bad Request Response too Big
... Test title: GET Performance Thresholds - Bad Request Response too Big
... Test objective: The objective is to test that the retrieval of NS performance thresholds fails because reponse is too big, and perform the JSON schema validation of the failed operation HTTP response
... Pre-conditions: A NS instance is instantiated. One or more NS performance thresholds are set in the NFVO.
- ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -143,16 +143,16 @@ GET Performance Thresholds - Bad Request Response too Big
Check HTTP Response Status Code Is 400
Check HTTP Response Body Json Schema Is ProblemDetails
-POST new Performance Threshold - Unprocessable Entity
+POST new Performance Threshold - Unprocessable Content
[Documentation] Test ID: 5.3.4.4.11
- ... Test title: POST new Performance Threshold - Unprocessable Entity
+ ... Test title: POST new Performance Threshold - Unprocessable Content
... Test objective: The objective is to test the creation of a new NS performance threshold fails when a request contains syntactically correct data but the data cannot be processed.
... Pre-conditions: A NS instance is instantiated.
- ... Reference: clause 7.4.5.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: clause 7.4.5.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
- Send POST request for Performance threshold with unprocessable entity
+ Send POST request for Performance threshold with unprocessable content
Check HTTP Response Status Code Is 422
Check HTTP Response Body Json Schema Is ProblemDetails
-
\ No newline at end of file
+
diff --git a/SOL005/NSPerformanceManagement-API/environment/variables.txt b/SOL005/NSPerformanceManagement-API/environment/variables.txt
index 33dcf94305e1563b9d59756921fd9b7775b88710..c0bb21017be0a7f7e6a977c1cca614d14a846f6a 100644
--- a/SOL005/NSPerformanceManagement-API/environment/variables.txt
+++ b/SOL005/NSPerformanceManagement-API/environment/variables.txt
@@ -75,4 +75,6 @@ ${FILTER_OK_Threshold} objectInstanceId=1f50d68b-82e8-4deb-bd40-c934d4d1ac0
${FILTER_KO} criterias=erroneousFilter
${SEPERATOR} =
-${callbackResp} 127.0.0.1
\ No newline at end of file
+${callbackResp} 127.0.0.1
+
+${PRODUCER_SUPPORT_COND_REQ} 1
\ No newline at end of file
diff --git a/SOL005/VNFPackageManagement-API/AccessConfigurationForExternalArtifacts.robot b/SOL005/VNFPackageManagement-API/AccessConfigurationForExternalArtifacts.robot
index 9d8a6e0800421ec86188206bb7b7c8ba980dc1b2..b50411050323da29347c797c4b874b9d68f73639 100644
--- a/SOL005/VNFPackageManagement-API/AccessConfigurationForExternalArtifacts.robot
+++ b/SOL005/VNFPackageManagement-API/AccessConfigurationForExternalArtifacts.robot
@@ -7,11 +7,11 @@ Library REST ${NFVO_SCHEMA}://${NFVO_HOST}:${NFVO_PORT} ssl_veri
*** Test Cases ***
Get Access configuration for external artifacts
- [Documentation] Test ID: 5.3.5.10.1
+ [Documentation] Test ID: 5.3.5.11.1
... Test title: Get Access configuration for external artifacts
... Test objective: The objective is to test the GET method reads the access configuration information that is used by the NFVO to get the content of external VNF package artifacts and perform a JSON schema and content validation of the collected data structure
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.4a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.4a.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -20,11 +20,11 @@ Get Access configuration for external artifacts
Check HTTP Response Body Json Schema Is ExternalArtifactsAccessConfig
Get Access configuration for external artifacts - Not Found
- [Documentation] Test ID: 5.3.5.10.2
+ [Documentation] Test ID: 5.3.5.11.2
... Test title: Get Access configuration for external artifacts - Not Found
... Test objective: The objective is to test that the retrieval of access configuration information that is used by the NFVO to get the content of external VNF package artifacts fails because resource is not present.
... Pre-conditions: none
- ... Reference: Clause 9.4.4a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.4a.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -33,11 +33,11 @@ Get Access configuration for external artifacts - Not Found
Check HTTP Response Body Json Schema Is ProblemDetails
PUT Access configuration for external artifacts
- [Documentation] Test ID: 5.3.5.10.3
+ [Documentation] Test ID: 5.3.5.11.3
... Test title: Access configuration for external artifacts
... Test objective: The objective is to test that PUT method provides the access configuration information for the NFVO to download the content of external VNF package artifacts.
... Pre-conditions: the individual VNF package resource shall have been created, and the value of "onboardingState" attribute shall equal to "CREATED" or "ERROR"
- ... Reference: Clause 9.4.4a.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.4a.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -47,11 +47,11 @@ PUT Access configuration for external artifacts
Check HTTP Response Body Json Schema Is ExternalArtifactsAccessConfig
PUT Access configuration for external artifacts - Downloading
- [Documentation] Test ID: 5.3.5.10.4
+ [Documentation] Test ID: 5.3.5.11.4
... Test title: Access configuration for external artifacts - Downloading
... Test objective: The objective is to test that VNF package has been uploaded successfully previously, to indicate that the access configuration information has been stored successfully by the NFVO and the NFVO now starts downloading external artifacts.
... Pre-conditions: the individual VNF package resource shall have been created, and the value of "onboardingState" attribute shall equal to "CREATED" or "ERROR"
- ... Reference: Clause 9.4.4a.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.4a.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -60,11 +60,11 @@ PUT Access configuration for external artifacts - Downloading
Check HTTP Response Status Code Is 202
PUT Access configuration for external artifacts - Conflict
- [Documentation] Test ID: 5.3.5.10.5
+ [Documentation] Test ID: 5.3.5.11.5
... Test title: Access configuration for external artifacts
... Test objective: The objective is to test that PUT method provides the access configuration information for the NFVO to download the content of external VNF package artifacts.
... Pre-conditions: the individual VNF package resource shall have been created, and the value of "onboardingState" attribute is neither "CREATED" nor "ERROR"
- ... Reference: Clause 9.4.4a.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.4a.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -73,11 +73,11 @@ PUT Access configuration for external artifacts - Conflict
Check HTTP Response Body Json Schema Is ProblemDetails
POST Access configuration for external artifacts - Method not implemented
- [Documentation] Test ID: 5.3.5.10.6
+ [Documentation] Test ID: 5.3.5.11.6
... Test title: POST Access configuration for external artifacts - Method not implemented
... Test objective: The objective is to test that POST method is not allowed to create access configuration for external artifacts
... Pre-conditions: none
- ... Reference: Clause 9.4.4a.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.4a.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -85,11 +85,11 @@ POST Access configuration for external artifacts - Method not implemented
Check HTTP Response Status Code Is 405
PATCH Access configuration for external artifacts - Method not implemented
- [Documentation] Test ID: 5.3.5.10.7
+ [Documentation] Test ID: 5.3.5.11.7
... Test title: PATCH Access configuration for external artifacts - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update access configuration for external artifacts
... Pre-conditions: none
- ... Reference: Clause 9.4.4a.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.4a.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -97,11 +97,11 @@ PATCH Access configuration for external artifacts - Method not implemented
Check HTTP Response Status Code Is 405
DELETE Access configuration for external artifacts - Method not implemented
- [Documentation] Test ID: 5.3.5.10.8
+ [Documentation] Test ID: 5.3.5.11.8
... Test title: DELETE Access configuration for external artifacts - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to delete access configuration for external artifacts
... Pre-conditions: none
- ... Reference: Clause 9.4.4a.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.4a.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/VNFPackageManagement-API/ApiVersion.robot b/SOL005/VNFPackageManagement-API/ApiVersion.robot
index 792731e76973ad88384b4baa3891e834d09c5a79..27b49119c8e0aa0a65db77f72f68c2f6c802a1cf 100644
--- a/SOL005/VNFPackageManagement-API/ApiVersion.robot
+++ b/SOL005/VNFPackageManagement-API/ApiVersion.robot
@@ -12,7 +12,7 @@ POST API Version - Method not implemented
... Test title: POST API version - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -24,7 +24,7 @@ GET API Version
... Test title: GET API Version
... Test objective: The objective is to test that GET method successfully return ApiVersionInformation
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -37,7 +37,7 @@ PUT API Version - Method not implemented
... Test title: PUT API Version - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -49,7 +49,7 @@ PATCH API Version - Method not implemented
... Test title: PATCH API Version - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -61,7 +61,7 @@ DELETE API Version - Method not implemented
... Test title: DELETE API Version - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -73,7 +73,7 @@ POST API Version with apiMajorVerion - Method not implemented
... Test title: POST API version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -85,7 +85,7 @@ GET API Version with apiMajorVerion
... Test title: GET API Version with apiMajorVerion
... Test objective: The objective is to test that GET method successfully return ApiVersionInformation
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -98,7 +98,7 @@ PUT API Version with apiMajorVerion - Method not implemented
... Test title: PUT API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -110,7 +110,7 @@ PATCH API Version with apiMajorVerion - Method not implemented
... Test title: PATCH API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -122,7 +122,7 @@ DELETE API Version with apiMajorVerion - Method not implemented
... Test title: DELETE API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/VNFPackageManagement-API/IndividualSubscription.robot b/SOL005/VNFPackageManagement-API/IndividualSubscription.robot
index b6e959c2100e611a22982df0de751fddaf033f51..99801802810cb7907ff8c3c22e2e492c40a3ef12 100644
--- a/SOL005/VNFPackageManagement-API/IndividualSubscription.robot
+++ b/SOL005/VNFPackageManagement-API/IndividualSubscription.robot
@@ -12,7 +12,7 @@ GET Individual VNF Package Subscription
... Test title: GET Individual VNF Package Subscription
... Test objective: The objective is to test the retrieval of individual VNF package subscription and perform a JSON schema and content validation of the returned subscription data structure
... Pre-conditions: At least one VNF package subscription is available in the NFVO.
- ... Reference: Clause 9.4.9.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.9.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -27,7 +27,7 @@ GET Individual VNF Package Subscription with invalid resource identifier
... Test title: GET Individual VNF Package Subscription with invalid resource identifier
... Test objective: The objective is to test that the retrieval of an individual VNF package subscription fails when using an invalid resource identifier
... Pre-conditions: At least one VNF package subscription is available in the NFVO.
- ... Reference: Clause 9.4.9.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.9.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -40,7 +40,7 @@ DELETE Individual VNF Package Subscription with invalid resource identifier
... Test title: DELETE Individual VNF Package Subscription with invalid resource identifier
... Test objective: The objective is to test that the deletion of an individual VNF package subscription fails when using an invalid resource identifier
... Pre-conditions: At least one VNF package subscription is available in the NFVO.
- ... Reference: Clause 9.4.9.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.9.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -52,7 +52,7 @@ POST Individual VNF Package Subscription - Method not implemented
... Test title: POST Individual VNF Package Subscription - Method not implemented
... Test objective: The objective is to test that POST method is not allowed to create a new VNF Package Subscription
... Pre-conditions: none
- ... Reference: Clause 9.4.9.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.9.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -64,7 +64,7 @@ PUT Individual VNF Package Subscription - Method not implemented
... Test title: PUT Individual VNF Package Subscription - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to update an existing VNF Package subscription
... Pre-conditions: At least one VNF package subscription is available in the NFVO.
- ... Reference: Clause 9.4.9.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.9.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -76,7 +76,7 @@ PATCH Individual VNF Package Subscription - Method not implemented
... Test title: PATCH Individual VNF Package Subscription - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to modify an existing VNF Package subscription
... Pre-conditions: At least one VNF package subscription is available in the NFVO.
- ... Reference: Clause 9.4.9.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.9.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -88,7 +88,7 @@ DELETE Individual VNF Package Subscription
... Test title: DELETE Individual VNF Package Subscription
... Test objective: The objective is to test the deletion of an individual VNF package subscription
... Pre-conditions: At least one VNF package subscription is available in the NFVO.
- ... Reference: Clause 9.4.9.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.9.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: The VNF Package Subscription is not available anymore in the NFVO
diff --git a/SOL005/VNFPackageManagement-API/IndividualVNFPackage.robot b/SOL005/VNFPackageManagement-API/IndividualVNFPackage.robot
index ef2d378624eca5953c22f0915c9c1b8ed3931693..ad4c51d02de4c2dbe8c644f95c7e1c4458c69bc4 100644
--- a/SOL005/VNFPackageManagement-API/IndividualVNFPackage.robot
+++ b/SOL005/VNFPackageManagement-API/IndividualVNFPackage.robot
@@ -11,7 +11,7 @@ GET Individual VNF Package
... Test title: GET Individual VNF Package
... Test objective: The objective is to test the retrieval of an individual VNF package information perform a JSON schema validation of the collected data structure
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.3.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.3.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -26,7 +26,7 @@ GET Individual VNF Package with invalid resource identifier
... Test title: GET Individual VNF Package with invalid resource identifier
... Test objective: The objective is to test that the retrieval of an individual VNF package fails when using an invalid resource identifier
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.3.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.3.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -39,7 +39,7 @@ POST Individual VNF Package - Method not implemented
... Test title: POST Individual VNF Package - Method not implemented
... Test objective: The objective is to test that POST method is not allowed to create new VNF Package
... Pre-conditions: none
- ... Reference: Clause 9.4.3.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.3.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -51,7 +51,7 @@ PUT Individual VNF Package - Method not implemented
... Test title: PUT Individual VNF Package - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to modify a VNF Package
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.3.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.3.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -63,7 +63,7 @@ Disable Individual VNF Package
... Test title: Disable Individual VNF Package
... Test objective: The objective is to test the disabling of an individual VNF Package and perform a JSON schema and content validation of the collected data structure
... Pre-conditions: One or more VNF Packages are onboarded in the NFVO in ENABLED operational state.
- ... Reference: Clause 9.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: The VNF Package is in operational state DISABLED
@@ -77,7 +77,7 @@ Disable Individual VNF Package with conflict due to operational state DISABLED
... Test title: Disable Individual VNF Package with conflict due to operational state DISABLED
... Test objective: The objective is to test that disabling an individual VNF Package that is already in DISABLED operational state fails and perform a JSON schema validation of the failed operation HTTP response
... Pre-conditions: One or more VNF Packages are onboarded in the NFVO in DISABLED operational state (Test ID 5.3.5.2.5).
- ... Reference: Clause 9.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -90,7 +90,7 @@ Enable Individual VNF Package
... Test title: Enable Individual VNF Package
... Test objective: The objective is to test the enabling of an individual VNF Package and perform a JSON schema and content validation of the collected data structure
... Pre-conditions: One or more VNF Packages are onboarded in the NFVO in DISABLED operational state (Test ID 5.3.5.2.5).
- ... Reference: Clause 9.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: The VNF Package is in operational state ENABLED
@@ -104,7 +104,7 @@ Enable Individual VNF Package with conflict due to operational state ENABLED
... Test title: Enable Individual VNF Package with conflict due to operational state ENABLED
... Test objective: The objective is to test that enabling an individual VNF Package that is already in ENABLED operational state fails and perform a JSON schema validation of the failed operation HTTP response
... Pre-conditions: One or more VNF Packages are onboarded in the NFVO in ENABLED operational state (Test ID 5.3.5.2.7).
- ... Reference: Clause 9.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -117,7 +117,7 @@ DELETE Individual VNF Package
... Test title: DELETE Individual VNF Package
... Test objective: The objective is to test the deletion of an individual VNF Package
... Pre-conditions: One or more VNF packages are onboarded in the NFVO in DISABLED operational state
- ... Reference: Clause 9.4.3.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.3.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: The VNF Package is not available anymore in the NFVO
@@ -130,7 +130,7 @@ DELETE Individual VNF Package in operational state ENABLED
... Test title: DELETE Individual VNF Package in operational state ENABLED
... Test objective: The objective is to test that the deletion of an individual VNF Package in operational state ENABLED fails. The test also performs a JSON schema validation of the failed operation HTTP response.
... Pre-conditions: One or more VNF Package are onboarded in the NFVO in ENABLED operational state (Test ID 5.3.1.2.7).
- ... Reference: Clause 9.4.3.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.3.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: The VNF Package is not deleted by the failed operation.
@@ -144,7 +144,7 @@ DELETE Individual VNF Package used for instantiated VNF instances
... Test title: DELETE Individual VNF Package used for instantiated VNF instances
... Test objective: The objective is to test that the deletion of an individual VNF Package that is used in instantiated VNF instances fails. The test also performs a JSON schema validation of the failed operation HTTP response.
... Pre-conditions: One or more VNF instances are instantiated based on the concerned VNF package.
- ... Reference: Clause 9.4.3.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.3.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: The VNF Package is not deleted by the failed operation.
diff --git a/SOL005/VNFPackageManagement-API/IndividualVNFPackageArtifacts.robot b/SOL005/VNFPackageManagement-API/IndividualVNFPackageArtifacts.robot
index f933d346d7c490ef01a50e70cd82ffb57ab802bb..6e44e2489fde9a4b9b28db79a6686ff16f9d62d1 100644
--- a/SOL005/VNFPackageManagement-API/IndividualVNFPackageArtifacts.robot
+++ b/SOL005/VNFPackageManagement-API/IndividualVNFPackageArtifacts.robot
@@ -11,7 +11,7 @@ GET Individual VNF Package Artifact
... Test title: GET Individual VNF Package Artifact
... Test objective: The objective is to test the retrieval of an individual VNF package artifact
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.7.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.7.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -23,7 +23,7 @@ GET Individual VNF Package Artifact in octet stream format
... Test title: GET Individual VNF Package Artifact in octet stream format
... Test objective: The objective is to test the retrieval of an individual VNF package artifact when the NFVO cannot determine the artifact content type. The test performs a validation that the returned artifcat in is octet-stream format
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.7.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.7.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO cannot determine the content type of the artifact
... Post-Conditions: none
@@ -36,7 +36,7 @@ GET Individual VNF Package Artifact with Range Request and NFVO supporting Range
... Test title: GET Individual VNF Package Artifact with Range Request and NFVO supporting Range Requests
... Test objective: The objective is to test the retrieval of an individual VNF package artifact when using a range request to return single range of bytes from the file, with the NFVO supporting it. The test also perform a validation that returned content matches the issued range
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.7.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.7.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO supports range requests to return single range of bytes from the VNF package artifact
... Post-Conditions: none
@@ -50,7 +50,7 @@ GET Individual VNF Package Artifact with Range Request and NFVO not supporting R
... Test title: GET Individual VNF Package Artifact with Range Request and NFVO not supporting Range Requests
... Test objective: The objective is to test that the retrieval of an individual VNF package artifact, when using a range request to return single range of bytes from the file and the NFVO not supporting it, returns the full VNF Package artifact.
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.7.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.7.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO does not support range requests to return single range of bytes from the VNF package artifact
... Post-Conditions: none
@@ -62,7 +62,7 @@ GET Individual VNF Package Artifact with invalid Range Request
... Test title: GET Individual VNF Package Artifact with invalid Range Request
... Test objective: The objective is to test that the retrieval of an individual VNF package artifact fails when using a range request that does not match any available byte range in the file.
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.7.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.7.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO supports range requests to return single range of bytes from the VNF package artifact
... Post-Conditions: none
@@ -74,7 +74,7 @@ GET Individual VNF Package Artifact with invalid resource identifier
... Test title: GET Individual VNF Package Artifact with invalid resource identifier
... Test objective: The objective is to test that the retrieval of an individual VNF package artifact fails when using an invalid resource identifier
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.7.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.7.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -87,7 +87,7 @@ GET Individual VNF Package Artifact with conflict due to onboarding state
... Test title: GET Individual VNF Package Artifact with conflict due to onboarding state
... Test objective: The objective is to test that the retrieval of an individual VNF package artifact fails due to a conflict when the VNF Package is not in onboarding state ONBOARDED in the NFVO. The test also performs a validation of the JSON schema validation of the failed operation HTTP response
... Pre-conditions: The onboarding state of the VNF package for which the content is requested is different from ONBOARDED.
- ... Reference: Clause 9.4.7.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.7.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -100,7 +100,7 @@ POST Individual VNF Package Artifact - Method not implemented
... Test title: POST Individual VNF Package Artifact - Method not implemented
... Test objective: The objective is to test that POST method is not allowed to create new VNF Package artifact
... Pre-conditions: none
- ... Reference: Clause 9.4.7.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.7.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -112,7 +112,7 @@ PUT Individual VNF Package Artifact - Method not implemented
... Test title: PUT Individual VNF Package Artifact - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to modify a VNF Package artifact
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.7.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.7.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -124,7 +124,7 @@ PATCH Individual VNF Package Artifact - Method not implemented
... Test title: PATCH Individual VNF Package Artifact - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update a VNF Package artifact
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.7.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.7.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -136,7 +136,7 @@ DELETE Individual VNF Package Artifact - Method not implemented
... Test title: DELETE Individual VNF Package Artifact - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to delete a VNF Package artifact
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.7.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.7.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/VNFPackageManagement-API/ManifestInIndividualVNFPackage.robot b/SOL005/VNFPackageManagement-API/ManifestInIndividualVNFPackage.robot
index 2f08a9855f7e96e26d400ac49db23d3228d2c1eb..c77ce8c5e85994137408d13b3aa98945ff14c06a 100644
--- a/SOL005/VNFPackageManagement-API/ManifestInIndividualVNFPackage.robot
+++ b/SOL005/VNFPackageManagement-API/ManifestInIndividualVNFPackage.robot
@@ -7,11 +7,11 @@ Library REST ${NFVO_SCHEMA}://${NFVO_HOST}:${NFVO_PORT} ssl_veri
*** Test Cases ***
Get Manifest in Individual VNF Package
- [Documentation] Test ID: 5.3.5.11.1
+ [Documentation] Test ID: 5.3.5.12.1
... Test title: Get Manifest in Individual VNF Package
... Test objective: The objective is to test that content of manifest within a NVF Package is read successfully.
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.4b.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.4b.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -20,11 +20,11 @@ Get Manifest in Individual VNF Package
Check HTTP Response Header Content-Type Is text/plain
Get Manifest in Individual VNF Package with security information
- [Documentation] Test ID: 5.3.5.11.2
+ [Documentation] Test ID: 5.3.5.12.2
... Test title: Get Manifest in Individual VNF Package with security information
... Test objective: The objective is to test the retrieval of the Manifest in individual VNF package shall include in the ZIP archive the security information when requested with "include_signature" parameter, and perform a validation that returned content is in zip format
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.4b.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.4b.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -33,11 +33,11 @@ Get Manifest in Individual VNF Package with security information
Check HTTP Response Header Content-Type Is application/zip
Get Manifest in Individual VNF Package - Not Acceptable
- [Documentation] Test ID: 5.3.5.11.3
+ [Documentation] Test ID: 5.3.5.12.3
... Test title: Get Manifest in Individual VNF Package - Not Acceptable
... Test objective: The objective is to test that the "Accept" header is not compatible with Content type "application/zip" but "incude_signature" is provided.\
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.4b.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.4b.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -46,11 +46,11 @@ Get Manifest in Individual VNF Package - Not Acceptable
Check HTTP Response Body Json Schema Is ProblemDetails
Get Manifest in Individual VNF Package - Conflict
- [Documentation] Test ID: 5.3.5.11.4
+ [Documentation] Test ID: 5.3.5.12.4
... Test title: Get Manifest in Individual VNF Package - Conflict
... Test objective: The objective is to test that the operation cannot be executed currently, due to a conflict with the state of the resource.
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.4b.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.4b.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -59,11 +59,11 @@ Get Manifest in Individual VNF Package - Conflict
Check HTTP Response Body Json Schema Is ProblemDetails
POST Manifest in Individual VNF Package - Method not implemented
- [Documentation] Test ID: 5.3.5.11.5
+ [Documentation] Test ID: 5.3.5.12.5
... Test title: POST Manifest in Individual VNF Package - Method not implemented
... Test objective: The objective is to test that POST method is not allowed to create new Manifest
... Pre-conditions: none
- ... Reference: Clause 9.4.4b.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.4b.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -71,11 +71,11 @@ POST Manifest in Individual VNF Package - Method not implemented
Check HTTP Response Status Code Is 405
PUT Manifest in Individual VNF Package - Method not implemented
- [Documentation] Test ID: 5.3.5.11.6
+ [Documentation] Test ID: 5.3.5.12.6
... Test title: PUT Manifest in Individual VNF Package - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to modify a Manifest
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.4b.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.4b.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -83,11 +83,11 @@ PUT Manifest in Individual VNF Package - Method not implemented
Check HTTP Response Status Code Is 405
PATCH Manifest in Individual VNF Package - Method not implemented
- [Documentation] Test ID: 5.3.5.11.7
+ [Documentation] Test ID: 5.3.5.12.7
... Test title: PATCH Manifest in Individual VNF Package - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update a Manifest
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.4b.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.4b.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -95,11 +95,11 @@ PATCH Manifest in Individual VNF Package - Method not implemented
Check HTTP Response Status Code Is 405
DELETE Manifest in Individual VNF Package - Method not implemented
- [Documentation] Test ID: 5.3.5.11.8
+ [Documentation] Test ID: 5.3.5.12.8
... Test title: DELETE Manifest in Individual VNF Package - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to delete a Manifest
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.4b.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.4b.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/VNFPackageManagement-API/NotificationEndpoint.robot b/SOL005/VNFPackageManagement-API/NotificationEndpoint.robot
index 151a3b510ca1475f530e23384957344f1e55d21a..e2c33abb1dbb915144d5b8e24832d9a8999700dc 100644
--- a/SOL005/VNFPackageManagement-API/NotificationEndpoint.robot
+++ b/SOL005/VNFPackageManagement-API/NotificationEndpoint.robot
@@ -14,7 +14,7 @@ VNF Package Onboarding Notification
... Test title: VNF Package Onboarding Notification
... Test objective: The objective is to test that VNF Package Onboarding Notification is delivered with success to the notification consumer
... Pre-conditions: A VNF package subscription for onboarding notifications is available in the NFVO.
- ... Reference: Clause 9.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
@@ -26,7 +26,7 @@ VNF Package Change Notification
... Test title: VNF Package Change Notification
... Test objective: The objective is to test that VNF Package Change Notification is delivered with success to the notification consumer
... Pre-conditions: A VNF package subscription for change notifications is available in the NFVO.
- ... Reference: Clause 9.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/VNFPackageManagement-API/Notifications.robot b/SOL005/VNFPackageManagement-API/Notifications.robot
index 9f0cede4615ae2d1f5abe1219ee42abd61501467..4c5ac65280a768c07bcbd88709f13b1c14312e6f 100644
--- a/SOL005/VNFPackageManagement-API/Notifications.robot
+++ b/SOL005/VNFPackageManagement-API/Notifications.robot
@@ -16,7 +16,7 @@ VNF Package Onboarding Notification
... Test title: VNF Package Onboarding Notification
... Test objective: The objective is to test the dispatch of VNF Package Onboarding notification when the VNF package onboarding operation is successfully completed, and perform a JSON schema and content validation of the delivered notification. The action that triggers the notification under test is an explicit test step, but it is not performed by the test system.
... Pre-conditions: A VNF package subscription for onboarding notifications is available in the NFVO.
- ... Reference: Clause 9.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -29,7 +29,7 @@ VNF Package Operational State Change Notification
... Test title: VNF Package Operational State Change Notification
... Test objective: The objective is to test the dispatch of VNF Package Change notification when the VNF package operational state is modified, and perform a JSON schema and content validation of the delivered notification. The action that triggers the notification under test is an explicit test step, but it is not performed by the test system.
... Pre-conditions: A VNF package subscription for change notifications is available in the NFVO.
- ... Reference: Clause 9.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -43,7 +43,7 @@ VNF Package Deletion Notification
... Test title: VNF Package Deletion Notification
... Test objective: The objective is to test the dispatch of VNF Package Change notification when the VNF package is deleted on the NFVO, and perform a JSON schema and content validation of the delivered notification. The action that triggers the notification under test is an explicit test step, but it is not performed by the test system.
... Pre-conditions: A VNF package subscription for change notifications is available in the NFVO.
- ... Reference: Clause 9.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/VNFPackageManagement-API/Subscriptions.robot b/SOL005/VNFPackageManagement-API/Subscriptions.robot
index 8bed781d057c7dbcb3e44511f7ebc8ba69714aa5..0602f8b8274184f9c5da9b4bea755a046b8419a9 100644
--- a/SOL005/VNFPackageManagement-API/Subscriptions.robot
+++ b/SOL005/VNFPackageManagement-API/Subscriptions.robot
@@ -16,7 +16,7 @@ Get All VNF Package Subscriptions
... Test title: GET all VNF Package Subscriptions
... Test objective: The objective is to test the retrieval of all VNF package subscriptions and perform a JSON schema validation of the returned subscriptions data structure
... Pre-conditions: At least one VNF package subscription is available in the NFVO.
- ... Reference: Clause 9.4.8.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.8.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -29,7 +29,7 @@ Get VNF Package Subscriptions with attribute-based filter
... Test title: Get VNF Package Subscriptions with attribute-based filter
... Test objective: The objective is to test the retrieval of VNF package subscriptions using attribute-based filter, perform a JSON schema validation of the collected data structure, and verify that the retrieved information matches the issued attribute-based filters
... Pre-conditions: At least one VNF package subscription is available in the NFVO.
- ... Reference: Clause 9.4.8.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.8.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -43,7 +43,7 @@ Get VNF Package Subscriptions with invalid attribute-based filter
... Test title: Get VNF Package Subscriptions with attribute-based filters
... Test objective: The objective is to test that the retrieval of VNF package subscriptions fails when using invalid attribute-based filters, and perform the JSON schema validation of the failed operation HTTP response.
... Pre-conditions: At least one VNF package subscription is available in the NFVO.
- ... Reference: Clause 9.4.8.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.8.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -56,7 +56,7 @@ GET VNF Package Subscription with invalid resource endpoint
... Test title: GET VNF Package Subscription with invalid resource endpoint
... Test objective: The objective is to test that the retrieval of all VNF package subscriptions fails when using invalid resource endpoint.
... Pre-conditions: At least one VNF package subscription is available in the NFVO.
- ... Reference: Clause 9.4.8.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.8.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -69,7 +69,7 @@ Create new VNF Package subscription
... Test title: Create new VNF Package subscription
... Test objective: The objective is to test the creation of a new VNF package subscription and perform a JSON schema and content validation of the returned subscription data structure
... Pre-conditions: none
- ... Reference: Clause 9.4.8.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.8.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: The VNF package subscription is successfully set and it matches the issued subscription
@@ -85,7 +85,7 @@ Create duplicated VNF Package subscription with NFVO not creating duplicated sub
... Test title: Create duplicated VNF Package subscription with NFVO not creating duplicated subscriptions
... Test objective: The objective is to test the attempt of a creation of a duplicated VNF package subscription and check that no new subscription is created by the NFVO and a link to the original subscription is returned
... Pre-conditions: At least one VNF package subscription is available in the NFVO.
- ... Reference: Clause 9.4.8.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.8.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO does not support the creation of duplicated subscriptions
... Post-Conditions: The existing VNF package subscription returned is available in the NFVO
@@ -101,7 +101,7 @@ Create duplicated VNF Package subscription with NFVO creating duplicated subscri
... Test title: Create duplicated VNF Package subscription with NFVO creating duplicated subscriptions
... Test objective: The objective is to test the creation of a duplicated VNF package subscription and perform a JSON schema and content validation of the returned duplicated subscription data structure
... Pre-conditions: At least one VNF package subscription is available in the NFVO.
- ... Reference: Clause 9.4.8.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.8.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO supports the creation of duplicated subscriptions
... Post-Conditions: The duplicated VNF package subscription is successfully set and it matches the issued subscription
@@ -116,7 +116,7 @@ PUT VNF Package Subscriptions - Method not implemented
... Test title: PUT VNF Package Subscriptions - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to modify VNF package subscriptions
... Pre-conditions: At least one VNF package subscription is available in the NFVO.
- ... Reference: Clause 9.4.8.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.8.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -128,7 +128,7 @@ PATCH VNF Package Subscriptions - Method not implemented
... Test title: PATCH VNF Package Subscriptions - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update VNF package subscriptions
... Pre-conditions: At least one VNF package subscription is available in the NFVO.
- ... Reference: Clause 9.4.8.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.8.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -151,7 +151,7 @@ Get All VNF Package Subscriptions as Paged Response
... Test title: GET all VNF Package Subscriptions as Paged Response
... Test objective: The objective is to test the retrieval of all VNF package subscriptions as paged response.
... Pre-conditions: At least one VNF package subscription is available in the NFVO.
- ... Reference: Clause 9.4.8.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.8.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -164,7 +164,7 @@ Get VNF Package Subscriptions - Bad Request Response too Big
... Test title: Get VNF Package Subscriptions - Bad Request Response too Big
... Test objective: The objective is to test that the retrieval of VNF package subscriptions fails because response is too big, and perform the JSON schema validation of the failed operation HTTP response.
... Pre-conditions: At least one VNF package subscription is available in the NFVO.
- ... Reference: Clause 9.4.8.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.8.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/VNFPackageManagement-API/VNFDInIndividualVNFPackage.robot b/SOL005/VNFPackageManagement-API/VNFDInIndividualVNFPackage.robot
index 9a0db3c6a450bb612023d268ca391032022d6d4d..2b0f2f40fe34d45b74717579f1895f4f81e5270b 100644
--- a/SOL005/VNFPackageManagement-API/VNFDInIndividualVNFPackage.robot
+++ b/SOL005/VNFPackageManagement-API/VNFDInIndividualVNFPackage.robot
@@ -22,7 +22,7 @@ Get VNFD in Individual VNF Package in Zip Format
... Test title: Get VNFD in Individual VNF Package in Zip Format
... Test objective: The objective is to test the retrieval of the VNFD in zip format for an individual VNF package and perform a validation that returned content is in zip format
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -68,7 +68,7 @@ Get VNFD in Individual VNF Package with invalid resource identifier
... Test title: Get VNFD in Individual VNF Package with invalid resource identifier
... Test objective: The objective is to test that the retrieval of the VNFD for an individual VNF Package fails when using an invalid resource identifier
... Pre-conditions: none
- ... Reference: Clause 9.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -81,7 +81,7 @@ Get VNFD in Individual VNF Package with conflict due to onboarding state
... Test title: Get VNFD in Individual VNF Package with conflict due to onboarding state
... Test objective: The objective is to test that the retrieval of the VNFD for an individual VNF Package fails due to a conflict when the VNF Package is not in onboarding state ONBOARDED in the NFVO. The test also performs a validation of the JSON schema validation of the failed operation HTTP response
... Pre-conditions: The onboarding state of the VNF package for which the VNFD is requested is different from ONBOARDED.
- ... Reference: Clause 9.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -94,7 +94,7 @@ POST VNFD in Individual VNF Package - Method not implemented
... Test title: POST VNFD in Individual VNF Package - Method not implemented
... Test objective: The objective is to test that POST method is not allowed to create new VNFD
... Pre-conditions: none
- ... Reference: Clause 9.4.4.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.4.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -106,7 +106,7 @@ PUT VNFD in Individual VNF Package - Method not implemented
... Test title: PUT VNFD in Individual VNF Package - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to modify a VNFD
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.4.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.4.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -118,7 +118,7 @@ PATCH VNFD in Individual VNF Package - Method not implemented
... Test title: PATCH VNFD in Individual VNF Package - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update a VNFD
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.4.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.4.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -130,7 +130,7 @@ DELETE VNFD in Individual VNF Package - Method not implemented
... Test title: DELETE VNFD in Individual VNF Package - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to delete a VNFD
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.4.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.4.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -142,7 +142,7 @@ Get VNFD in Individual VNF Package with security information
... Test title: Get VNFD in Individual VNF Package with security information
... Test objective: The objective is to test the retrieval of the VNFD in zip format for an individual VNF package shall include in the ZIP archive the security information when requested with "include_signature" parameter, and perform a validation that returned content is in zip format
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/VNFPackageManagement-API/VNFPackageArtifacts.robot b/SOL005/VNFPackageManagement-API/VNFPackageArtifacts.robot
index 21c99fd66540b14f7e827e2357c46905aa187d79..d0e465324f33c386544690bf0e32ec3fe7ef4967 100644
--- a/SOL005/VNFPackageManagement-API/VNFPackageArtifacts.robot
+++ b/SOL005/VNFPackageManagement-API/VNFPackageArtifacts.robot
@@ -8,11 +8,11 @@ Library REST ${NFVO_SCHEMA}://${NFVO_HOST}:${NFVO_PORT} ssl_veri
*** Test Cases ***
Get VNF Package Artifact
- [Documentation] Test ID: 5.3.5.12.1
+ [Documentation] Test ID: 5.3.5.13.1
... Test title: Get VNF Package Artifact
... Test objective: The objective is to test that the GET request read the whole content of the archive containing the artifact files successfully, and perform a validation that returned content is in Zip format
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.5a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.5a.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -21,11 +21,11 @@ Get VNF Package Artifact
Check HTTP Response Header Content-Type Is application/zip
Get VNF Package Artifact with "exclude_all_mano_artifacts" parameter
- [Documentation] Test ID: 5.3.5.12.2
+ [Documentation] Test ID: 5.3.5.13.2
... Test title: Get VNF Package Artifact with "exclude_all_mano_artifacts" parameter
... Test objective: The objective is to test that the GET request read the whole content of the archive containing the artifact files successfully and it doesnot contain additional MANO artifacts when requested with "exclude_all_mano_artifacts" parameter
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.5a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.5a.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -34,11 +34,11 @@ Get VNF Package Artifact with "exclude_all_mano_artifacts" parameter
Check HTTP Response Header Content-Type Is application/zip
Get VNF Package Artifact with "exclude_all_non_mano_artifacts" parameter
- [Documentation] Test ID: 5.3.5.12.3
+ [Documentation] Test ID: 5.3.5.13.3
... Test title: Get VNF Package Artifact with "exclude_all_non_mano_artifacts" parameter
... Test objective: The objective is to test that the GET request read the whole content of the archive containing the artifact files successfully and it doesnot contain non-MANO Artifacts when requested with "exclude_all_non_mano_artifacts" parameter
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.5a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.5a.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -47,11 +47,11 @@ Get VNF Package Artifact with "exclude_all_non_mano_artifacts" parameter
Check HTTP Response Header Content-Type Is application/zip
Get VNF Package Artifact with "select_non_mano_artifact_sets" parameter
- [Documentation] Test ID: 5.3.5.12.4
+ [Documentation] Test ID: 5.3.5.13.4
... Test title: Get VNF Package Artifact with "select_non_mano_artifact_sets" parameter
... Test objective: The objective is to test that the GET request read the whole content of the archive containing the artifact files successfully and also contain non_MANO artifacts set when requested with "select_non_mano_artifact_sets" parameter
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.5a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.5a.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -60,11 +60,11 @@ Get VNF Package Artifact with "select_non_mano_artifact_sets" parameter
Check HTTP Response Header Content-Type Is application/zip
Get VNF Package Artifact with "include_signatures" parameter
- [Documentation] Test ID: 5.3.5.12.5
+ [Documentation] Test ID: 5.3.5.13.5
... Test title: Get VNF Package Artifact with "include_signatures" parameter
... Test objective: The objective is to test that the GET request read the whole content of the archive containing the artifact files successfully and also contain security certificates when requested with "include_signature" parameter, and perform a validation that returned content is in Zip format
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.5a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.5a.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -73,11 +73,11 @@ Get VNF Package Artifact with "include_signatures" parameter
Check HTTP Response Header Content-Type Is application/zip
Get VNF Package Artifact with Range Request and NFVO supporting Range Requests
- [Documentation] Test ID: 5.3.5.12.6
+ [Documentation] Test ID: 5.3.5.13.6
... Test title: Get VNF Package Artifact with Range Request and NFVO supporting Range Requests
... Test objective: The objective is to test the GET request read the whole content of the archive containing the artifact files successfully when using a range request to return single range of bytes from the file, with the NFVO supporting it. The test also perform a validation that returned content matches the issued range
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.5a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.5a.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO supports range requests to return single range of bytes from the VNF package artifact
... Post-Conditions: none
@@ -87,11 +87,11 @@ Get VNF Package Artifact with Range Request and NFVO supporting Range Requests
Check HTTP Response Header Content-Length Is Present and Matches the requested range length
Get VNF Package Artifact with invalid URI parameters "exclude_all_non_mano_artifacts", "select_non_mano_artifact_sets"
- [Documentation] Test ID: 5.3.5.12.7
+ [Documentation] Test ID: 5.3.5.13.7
... Test title: Get VNF Package Artifact with invalid URI parameters "exclude_all_non_mano_artifacts", "select_non_mano_artifact_sets"
... Test objective: The objective is to test that the GET request to read the whole content of the archive containing the artifact files fails when both "exclude_all_non_mano_artifacts" and "select_non_mano_artifact_sets" are present in request
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.5a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.5a.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -100,11 +100,11 @@ Get VNF Package Artifact with invalid URI parameters "exclude_all_non_mano_artif
Check HTTP Response Body Json Schema Is ProblemDetails
Get VNF Package Artifact with invalid URI parameters "exclude_all_non_mano_artifacts", "exclude_all_mano_artifacts"
- [Documentation] Test ID: 5.3.5.12.8
+ [Documentation] Test ID: 5.3.5.13.8
... Test title: Get VNF Package Artifact with invalid URI parameters "exclude_all_non_mano_artifacts", "exclude_all_mano_artifactss"
... Test objective: The objective is to test that the GET request to read the whole content of the archive containing the artifact files fails when both "exclude_all_non_mano_artifacts" and "exclude_all_mano_artifacts" are present in request
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.5a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.5a.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -113,11 +113,11 @@ Get VNF Package Artifact with invalid URI parameters "exclude_all_non_mano_artif
Check HTTP Response Body Json Schema Is ProblemDetails
Get VNF Package Artifact with invalid URI parameters undifend select_non_mano_artifact_sets
- [Documentation] Test ID: 5.3.5.12.9
+ [Documentation] Test ID: 5.3.5.13.9
... Test title: Get VNF Package Artifact with invalid URI parameters undefined select_non_mano_artifact_sets
... Test objective: The objective is to test that the GET request to read the whole content of the archive containing the artifact files fails when one or more value provided in "select_non_mano_artifact_sets" are not provided in Manifest.
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.5a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.5a.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -126,11 +126,11 @@ Get VNF Package Artifact with invalid URI parameters undifend select_non_mano_ar
Check HTTP Response Body Json Schema Is ProblemDetails
Get VNF Package Artifact with conflict due to onboarding state
- [Documentation] Test ID: 5.3.5.12.10
+ [Documentation] Test ID: 5.3.5.13.10
... Test title: Get VNF Package Artifact with conflict due to onboarding state
... Test objective: The objective is to test that the GET request to read the whole content of the archive containing the artifact files fails due to a conflict when the VNF Package is not in onboarding state ONBOARDED in the NFVO. The test also performs a validation of the JSON schema validation of the failed operation HTTP response
... Pre-conditions: The onboarding state of the VNF package for which the content is requested is different from ONBOARDED.
- ... Reference: Clause 9.4.5a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.5a.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -139,11 +139,11 @@ Get VNF Package Artifact with conflict due to onboarding state
Check HTTP Response Body Json Schema Is ProblemDetails
GET VNF Package Artifact with invalid Range Request
- [Documentation] Test ID: 5.3.5.12.11
+ [Documentation] Test ID: 5.3.5.13.11
... Test title: GET VNF Package Artifact with invalid Range Request
... Test objective: The objective is to test that the GET request to read the whole content of the archive containing the artifact files fails when using a range request that does not match any available byte range in the file.
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.5a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.5a.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO supports range requests to return single range of bytes from the VNF package artifact
... Post-Conditions: none
@@ -152,11 +152,11 @@ GET VNF Package Artifact with invalid Range Request
Check HTTP Response Body Json Schema Is ProblemDetails
POST VNF Package Artifact - Method not implemented
- [Documentation] Test ID: 5.3.5.12.12
+ [Documentation] Test ID: 5.3.5.13.12
... Test title: POST VNF Package Artifact - Method not implemented
... Test objective: The objective is to test that POST method is not allowed to create new VNF Package artifact
... Pre-conditions: none
- ... Reference: Clause 9.4.5a.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.5a.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -164,11 +164,11 @@ POST VNF Package Artifact - Method not implemented
Check HTTP Response Status Code Is 405
PUT VNF Package Artifact - Method not implemented
- [Documentation] Test ID: 5.3.5.12.13
+ [Documentation] Test ID: 5.3.5.13.13
... Test title: PUT VNF Package Artifact - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to modify a VNF Package artifact
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.5a.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.5a.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -176,11 +176,11 @@ PUT VNF Package Artifact - Method not implemented
Check HTTP Response Status Code Is 405
PATCH VNF Package Artifact - Method not implemented
- [Documentation] Test ID: 5.3.5.12.14
+ [Documentation] Test ID: 5.3.5.13.14
... Test title: PATCH VNF Package Artifact - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update a VNF Package artifact
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.5a.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.5a.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -188,11 +188,11 @@ PATCH VNF Package Artifact - Method not implemented
Check HTTP Response Status Code Is 405
DELETE VNF Package Artifact - Method not implemented
- [Documentation] Test ID: 5.3.5.12.15
+ [Documentation] Test ID: 5.3.5.13.15
... Test title: DELETE VNF Package Artifact - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to delete a VNF Package artifact
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.6.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.6.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -200,11 +200,11 @@ DELETE VNF Package Artifact - Method not implemented
Check HTTP Response Status Code Is 405
Get VNF Package Artifact with "include_external_artifacts" parameter
- [Documentation] Test ID: 5.3.5.12.16
+ [Documentation] Test ID: 5.3.5.13.16
... Test title: Get VNF Package Artifact with "include_external_artifacts" parameter
... Test objective: The objective is to test that GET request reads the whole content of the archive containing the external artifacts successfully when requested with "include_external_artifacts" parameter
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.5a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.5a.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/VNFPackageManagement-API/VNFPackageContent.robot b/SOL005/VNFPackageManagement-API/VNFPackageContent.robot
index 20138c9d2d2bb63043f041f5a685103852c623e0..8f5bfa0153265fd73c3f04a352955e5979cdd3bb 100644
--- a/SOL005/VNFPackageManagement-API/VNFPackageContent.robot
+++ b/SOL005/VNFPackageManagement-API/VNFPackageContent.robot
@@ -12,7 +12,7 @@ GET Individual VNF Package Content
... Test title: GET Individual VNF Package Content
... Test objective: The objective is to test the retrieval of an individual VNF package content and perform a validation that returned content is in zip format
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -25,7 +25,7 @@ GET Individual VNF Package Content with Range Request and NFVO supporting Range
... Test title: GET Individual VNF Package Content with Range Request and NFVO supporting Range Requests
... Test objective: The objective is to test the retrieval of an individual VNF package content when using a range request to return single range of bytes from the file, with the NFVO supporting it. The test also perform a validation that returned content matches the issued range
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO supports range requests to return single range of bytes from the VNF package file
... Post-Conditions: none
@@ -40,7 +40,7 @@ GET Individual VNF Package Content with Range Request and NFVO not supporting Ra
... Test title: GET Individual VNF Package Content with Range Request and NFVO not supporting Range Requests
... Test objective: The objective is to test that the retrieval of an individual VNF package content, when using a range request to return single range of bytes from the file and the NFVO not supporting it, returns the full VNF Package file.
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO does not support range requests to return single range of bytes from the VNF package file
... Post-Conditions: none
@@ -53,7 +53,7 @@ GET Individual VNF Package Content with invalid Range Request
... Test title: GET Individual VNF Package Content with invalid Range Request
... Test objective: The objective is to test that the retrieval of an individual VNF package content fails when using a range request that does not match any available byte range in the file.
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO supports range requests to return single range of bytes from the VNF package file
... Post-Conditions: none
@@ -65,7 +65,7 @@ GET Individual VNF Package Content with invalid resource identifier
... Test title: GET Individual VNF Package Content with invalid resource identifier
... Test objective: The objective is to test that the retrieval of an individual VNF package content fails when using an invalid resource identifier
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -78,7 +78,7 @@ GET Individual VNF Package Content with conflict due to onboarding state
... Test title: GET Individual VNF Package Content with conflict due to onboarding state
... Test objective: The objective is to test that the retrieval of an individual VNF package content fails due to a conflict when the VNF Package is not in onboarding state ONBOARDED in the NFVO. The test also performs a validation of the JSON schema validation of the failed operation HTTP response
... Pre-conditions: The onboarding state of the VNF package for which the content is requested is different from ONBOARDED.
- ... Reference: Clause 9.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -91,7 +91,7 @@ POST Individual VNF Package Content - Method not implemented
... Test title: POST Individual VNF Package Content - Method not implemented
... Test objective: The objective is to test that POST method is not allowed to create new VNF Package content
... Pre-conditions: none
- ... Reference: Clause 9.4.5.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.5.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -103,7 +103,7 @@ Upload VNF Package Content
... Test title: Upload VNF Package Content
... Test objective: The objective is to test the upload of a VNF Package Content in Zip format.
... Pre-conditions: One or more VNF Packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.5.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.5.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: The VNF Package content is successfully uploaded and available in the NFVO
@@ -116,7 +116,7 @@ Upload VNF Package Content with conflict due to onboarding state
... Test title: Upload VNF Package Content with conflict due to onboarding state
... Test objective: The objective is to test that the upload of the VNF Package Content fails due to a conflict when the VNF Package is not in onboarding state CREATED in the NFVO. The test also performs a validation of the JSON schema validation of the failed operation HTTP response
... Pre-conditions: The onboarding state of the VNF Package for which the content is requested is different from CREATED.
- ... Reference: Clause 9.4.5.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.5.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -129,7 +129,7 @@ PATCH Individual VNF Package Content - Method not implemented
... Test title: PATCH Individual VNF Package Content - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update a VNF Package content
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.5.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.5.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -141,7 +141,7 @@ DELETE Individual VNF Package Content - Method not implemented
... Test title: DELETE Individual VNF Package Content - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to delete a VNF Package content
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.5.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.5.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/VNFPackageManagement-API/VNFPackageContentViaURI.robot b/SOL005/VNFPackageManagement-API/VNFPackageContentViaURI.robot
index fd930246af8183a5675f3f33f5981b8eced196bd..8917321b9b84ce0886f5a3a56b3390f97ba32a7d 100644
--- a/SOL005/VNFPackageManagement-API/VNFPackageContentViaURI.robot
+++ b/SOL005/VNFPackageManagement-API/VNFPackageContentViaURI.robot
@@ -12,7 +12,7 @@ Upload VNF Package Content from URI
... Test title: Upload VNF Package Content from URI
... Test objective: The objective is to test the upload of a VNF Package Content from URI.
... Pre-conditions: One or more VNF Packages are in onboarding state CREATED in the NFVO.
- ... Reference: Clause 9.4.6.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.6.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -25,7 +25,7 @@ Upload VNF Package Content from URI with conflict due to onboarding state
... Test title: Upload VNF Package Content from URI with conflict due to onboarding state
... Test objective: The objective is to test that the upload of the VNF Package Content from URI fails due to a conflict when the VNF Package is not in onboarding state CREATED in the NFVO. The test also performs a validation of the JSON schema validation of the failed operation HTTP response
... Pre-conditions: The onboarding state of the VNF Package for which the content is requested is different from CREATED.
- ... Reference: Clause 9.4.6.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.6.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -38,7 +38,7 @@ GET Individual VNF Package Content from URI - Method not implemented
... Test title: GET Individual VNF Package Content from URI - Method not implemented
... Test objective: The objective is to test that GET method is not allowed to retrieve a VNF Package content from URI
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.6.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.6.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -50,7 +50,7 @@ PUT Individual VNF Package Content from URI - Method not implemented
... Test title: PUT Individual VNF Package Content from URI - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to modify a VNF Package content from URI
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.6.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.6.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -62,7 +62,7 @@ PATCH Individual VNF Package Content from URI - Method not implemented
... Test title: PATCH Individual VNF Package Content - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update a VNF Package content from URI
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.6.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.6.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -74,7 +74,7 @@ DELETE Individual VNF Package Content from URI - Method not implemented
... Test title: DELETE Individual VNF Package Content - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to delete a VNF Package content from URI
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.6.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.6.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/VNFPackageManagement-API/VNFPackages.robot b/SOL005/VNFPackageManagement-API/VNFPackages.robot
index ad935d8e9dfcc5dbcc4a914d6a90cd7d0ddd814a..681b365f6c0899b603733f66f2551975699690e7 100644
--- a/SOL005/VNFPackageManagement-API/VNFPackages.robot
+++ b/SOL005/VNFPackageManagement-API/VNFPackages.robot
@@ -11,7 +11,7 @@ GET all VNF Packages
... Test title: GET all VNF Packages
... Test objective: The objective is to test the retrieval of all the available VNF packages information and perform a JSON schema and content validation of the collected data structure
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -28,7 +28,7 @@ GET VNF Packages with attribute-based filter
... Test title: GET VNF Packages with attribute-based filter
... Test objective: The objective is to test the retrieval of VNF packages using attribute-based filter, perform a JSON schema validation of the collected jobs data structure, and verify that the retrieved information matches the issued attribute-based filter
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -42,7 +42,7 @@ GET VNF Packages with invalid attribute-based filter
... Test title: GET VNF Packages with invalid attribute-based filter
... Test objective: The objective is to test that the retrieval of VNF packages fails when using invalid attribute-based filter, and perform the JSON schema validation of the failed operation HTTP response
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -55,7 +55,7 @@ Get all VNF Packages with malformed authorization token
... Test title: Get all VNF Packages Information with malformed authorization token
... Test objective: The objective is to test that the retrieval of VNF Packages fails when using malformed authorization token
... Pre-conditions: One or more VNF Packages are onboarded in the NFVO.
- ... Reference: Clause 4.5.3.3, 9.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 4.5.3.3, 9.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO requires the usage of access tokens for authorizing the API requests.
... Post-Conditions: none
@@ -67,7 +67,7 @@ Get all VNF Packages without authorization token
... Test title: Get all VNF Packages without authorization token
... Test objective: The objective is to test that the retrieval of VNF Packages fails when omitting the authorization token
... Pre-conditions: One or more VNF Packages are onboarded in the NFVO.
- ... Reference: Clause 4.5.3.3, 9.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 4.5.3.3, 9.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO requires the usage of access tokens for authorizing the API requests.
... Post-Conditions: none
@@ -79,7 +79,7 @@ GET VNF Packages with "all_fields" attribute selector
... Test title: GET VNF Packages with "all_fields" attribute selector
... Test objective: The objective is to test the retrieval of VNF packages with "all_fields" attribute selector, perform a JSON schema validation of the collected data structure, and verify that the retrieved information matches the issued "all_fileds" selector
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 4.3.3.2.1, 9.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 4.3.3.2.1, 9.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -93,7 +93,7 @@ GET VNF Packages with "exclude_default" attribute selector
... Test title: GET VNF Packages with exclude_default attribute selector
... Test objective: The objective is to test the retrieval of VNF packages with "exclude_default" attribute selector, perform a JSON schema validation of the collected data structure, and verify that the retrieved information matches the issued "exclude_default" selector
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 4.3.3.2.1, 9.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 4.3.3.2.1, 9.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -107,7 +107,7 @@ GET VNF Packages with "fields" attribute selector
... Test title: GET VNF Packages with fields attribute selector
... Test objective: The objective is to test the retrieval of VNF packages with "fields" attribute selector, perform a JSON schema validation of the collected data structure, and verify that the retrieved information matches the issued "fields" selector
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 4.3.3.2.1, 9.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 4.3.3.2.1, 9.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The VNFM supports the use of fields attribute selector
... Post-Conditions: none
@@ -121,7 +121,7 @@ GET VNF Packages with "exclude_fields" attribute selector
... Test title: GET VNF Packages with exclude_fields attribute selector
... Test objective: The objective is to test the retrieval of VNF packages with "exclude_fields" attribute selector, perform a JSON schema validation of the collected data structure, and verify that the retrieved information matches the issued "exclude_fields" selector
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 4.3.3.2.1, 9.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 4.3.3.2.1, 9.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The VNFM supports the use of exclude_fields attribute selector
... Post-Conditions: none
@@ -135,7 +135,7 @@ GET all VNF Packages with invalid resource endpoint
... Test title: GET VNF Packages with invalid resource endpoint
... Test objective: The objective is to test that the retrieval of VNF packages fails when using invalid resource endpoint
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -148,7 +148,7 @@ Create new VNF Package Resource
... Test title: Create new VNF Package Resource
... Test objective: The objective is to test the creation of a new VNF Package Resource and perform the JSON schema validation of the returned structure
... Pre-conditions: none
- ... Reference: Clause 9.4.2.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.2.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: The VNF Package Resource is successfully created on the NFVO
@@ -164,7 +164,7 @@ PUT all VNF Packages - Method not implemented
... Test title: PUT all VNF Packages - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to modify existing VNF Packages
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.2.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.2.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -176,7 +176,7 @@ PATCH all VNF Packages - Method not implemented
... Test title: PATCH all VNF Packages - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update existing VNF Packages
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.2.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.2.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -188,7 +188,7 @@ DELETE all VNF Packages - Method not implemented
... Test title: DELETE all VNF Packages - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to delete existing VNF Packages
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.2.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.2.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -200,7 +200,7 @@ GET all VNF Packages as Paged Response
... Test title: GET all VNF Packages as Paged Response
... Test objective: The objective is to test the retrieval of all the available VNF packages information as paged response.
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -213,7 +213,7 @@ GET VNF Packages - Bad Request Response too Big
... Test title: GET VNF Packages - Bad Request Response too Big
... Test objective: The objective is to test that the retrieval of VNF packages fails because response is too big, and perform the JSON schema validation of the failed operation HTTP response
... Pre-conditions: One or more VNF packages are onboarded in the NFVO.
- ... Reference: Clause 9.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 9.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/VNFPackageManagement-API/schemas/ExternalArtifactsAccessConfig.json b/SOL005/VNFPackageManagement-API/schemas/ExternalArtifactsAccessConfig.json
index a9b43cf0b5f30a71da75df73f1f02989c2671064..2603cca3060b90864da1a36a50c7842ad1e02c56 100644
--- a/SOL005/VNFPackageManagement-API/schemas/ExternalArtifactsAccessConfig.json
+++ b/SOL005/VNFPackageManagement-API/schemas/ExternalArtifactsAccessConfig.json
@@ -1,65 +1,56 @@
{
- "description": "This type represents the access configuration information for downloading external VNF package artifacts. The NFVO can obtain the external VNF package artifact file through the information provided in this structure, together with information provided in the manifest / VNFD. The data structure shall comply with the provisions defined in Table 9.5.2.10-1. If the data structure is part of a response body, security-sensitive attributes shall be excluded as specified in Table 9.5.2.10-1.\n",
- "type": "object",
- "properties": {
- "artifact": {
- "description": "Access configuration information for an external artefact.\n",
- "type": "object",
- "required": [
- "artifactUri"
- ],
- "properties": {
- "artifactUri": {
- "description": "String formatted according to IETF RFC 3986.\n",
- "type": "string",
- "format": "uri"
- },
- "overrideUri": {
- "description": "String formatted according to IETF RFC 3986.\n",
- "type": "string",
- "format": "uri"
- },
- "authType": {
- "description": "Defines the type of authentication / authorization for downloading the VNF package. Permitted values: - BASIC: Only the \"username\" and \"password\" attributes shall be present. - OAUTH2_CLIENT_CREDENTIAL S: Only the \"paramsOauth2ClientCredentials\" attribute shall be present. This attribute shall not be present if no credentials are provided for the artifact.\n",
- "type": "string",
- "enum": [
- "BASIC",
- "OAUTH2_CLIENT_CREDENTIALS"
- ]
- },
- "username": {
- "description": "User name to be used for authentication.\n",
- "type": "string"
- },
- "password": {
- "description": "Password to be used for authentication. Shall not be present in response bodies.\n",
- "type": "string"
- },
- "paramsOauth2ClientCredentials": {
- "description": "Parameters for authentication/authorization using OAUTH2_CLIENT_CREDENTIALS.\n",
- "type": "object",
- "required": [
- "clientId",
- "clientPassword",
- "tokenEndpoint"
- ],
- "properties": {
- "clientId": {
- "description": "Client identifier to be used in the access token request of the OAuth 2.0 client credentials grant type.\n",
- "type": "string"
- },
- "clientPassword": {
- "description": "Client password to be used in the access token request of the OAuth 2.0 client credentials grant type. Shall not be present in response bodies.\n",
- "type": "string"
- },
- "tokenEndpoint": {
- "description": "String formatted according to IETF RFC 3986.\n",
- "type": "string",
- "format": "uri"
- }
+ "description": "This type represents the access configuration information for downloading external VNF package artifacts. The NFVO can obtain the external VNF package artifact file through the information provided in this structure, together with information provided in the manifest / VNFD. The data structure shall comply with the provisions defined in Table 9.5.2.10-1. If the data structure is part of a response body, security-sensitive attributes shall be excluded as specified in Table 9.5.2.10-1.\n",
+ "type": "object",
+ "properties": {
+ "artifact": {
+ "description": "Access configuration information for an external artifact.\n",
+ "type": "object",
+ "required": [
+ "artifactUri"
+ ],
+ "properties": {
+ "artifactUri": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string",
+ "format": "uri"
+ },
+ "overrideUri": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string",
+ "format": "uri"
+ },
+ "authType": {
+ "description": "Defines the type of authentication / authorization for downloading the VNF package. Permitted values: - OAUTH2_CLIENT_CREDENTIALS: Only the \"paramsOauth2ClientCredentials\" attribute shall be present. This attribute shall not be present if no credentials are provided for the artifact.\n",
+ "type": "string",
+ "enum": [
+ "OAUTH2_CLIENT_CREDENTIALS"
+ ]
+ },
+ "paramsOauth2ClientCredentials": {
+ "description": "Parameters for authentication/authorization using OAUTH2_CLIENT_CREDENTIALS.\n",
+ "type": "object",
+ "required": [
+ "clientId",
+ "clientPassword",
+ "tokenEndpoint"
+ ],
+ "properties": {
+ "clientId": {
+ "description": "Client identifier to be used in the access token request of the OAuth 2.0 client credentials grant type.\n",
+ "type": "string"
+ },
+ "clientPassword": {
+ "description": "Client password to be used in the access token request of the OAuth 2.0 client credentials grant type. Shall not be present in response bodies.\n",
+ "type": "string"
+ },
+ "tokenEndpoint": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string",
+ "format": "uri"
}
}
}
}
}
- }
\ No newline at end of file
+ }
+}
\ No newline at end of file
diff --git a/SOL005/VNFPackageManagement-API/schemas/vnfPkgInfo.schema.json b/SOL005/VNFPackageManagement-API/schemas/vnfPkgInfo.schema.json
index fee9780add425e18f3b4567b0c5cf8c4952d0be1..967b1dc4654eff4f16ddf49b47924735d7ef6629 100644
--- a/SOL005/VNFPackageManagement-API/schemas/vnfPkgInfo.schema.json
+++ b/SOL005/VNFPackageManagement-API/schemas/vnfPkgInfo.schema.json
@@ -1,302 +1,385 @@
{
"description": "This type represents the information of a VNF package. It shall comply with the provisions defined in table 9.5.2.5-1.\nNOTE 1:\tIf the value of the onboardingState attribute is not equal to \"ONBOARDED\", the value of the operationalState attribute shall be equal to \"DISABLED\". NOTE 2:\tIf the value of the onboardingState attribute is not equal to \"ONBOARDED\", the value of the usageState attribute shall be equal to \"NOT_IN_USE\". NOTE 3:\tState changes of a VNF package are illustrated in clause B.2. NOTE 4:\tETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on TOSCA specifications.\n",
"type": "object",
- "required": ["id", "onboardingState", "operationalState", "usageState", "vnfmInfo", "_links"],
+ "required": [
+ "id",
+ "onboardingState",
+ "operationalState",
+ "usageState",
+ "_links"
+ ],
"properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfdExtInvariantId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfProvider": {
+ "description": "Provider of the VNF package and the VNFD. This information is copied from the VNFD. It shall be present after the VNF package content has been on-boarded and absent otherwise.\n",
+ "type": "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.\n",
+ "type": "string"
+ },
+ "vnfSoftwareVersion": {
+ "description": "A Version. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vnfdVersion": {
+ "description": "A Version. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "compatibleSpecificationVersions": {
+ "description": "A Version. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "checksum": {
+ "description": "This type represents the checksum of a VNF package or an artifact file.\n",
+ "required": [
+ "algorithm",
+ "hash"
+ ],
+ "type": "object",
+ "properties": {
+ "algorithm": {
+ "description": "Name of the algorithm used to generate the checksum, as defined in ETSI GS NFV-SOL 004 [5]. For example, SHA-256, SHA-512.\n",
"type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
+ },
+ "hash": {
+ "description": "The hexadecimal value of the checksum.\n",
"type": "string"
- },
- "vnfdExtInvariantId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfProvider": {
- "description": "Provider of the VNF package and the VNFD. This information is copied from the VNFD. It shall be present after the VNF package content has been on-boarded and absent otherwise.\n",
- "type": "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.\n",
- "type": "string"
- },
- "vnfSoftwareVersion": {
- "description": "A Version. Representation: string of variable length.\n",
- "type": "string"
- },
- "vnfdVersion": {
- "description": "A Version. Representation: string of variable length.\n",
- "type": "string"
- },
- "compatibleSpecificationVersions": {
- "description": "A Version. Representation: string of variable length.\n",
- "type": "string"
- },
- "checksum": {
- "description": "This type represents the checksum of a VNF package or an artifact file.\n",
- "required": ["algorithm", "hash"],
- "type": "object",
- "properties": {
+ }
+ }
+ },
+ "packageSecurityOption": {
+ "description": "Signals the security option used by the package as defined in clause 5.1 of ETSI GS NFV-SOL 004. It shall be present after the VNF package content has been on-boarded and absent otherwise. Valid values: - OPTION_1 - OPTION_2\n",
+ "type": "string",
+ "enum": [
+ "OPTION_1",
+ "OPTION_2"
+ ]
+ },
+ "signingCertificate": {
+ "description": "The singleton signing certificate if it is included as a file in the VNF package.\n",
+ "type": "string"
+ },
+ "softwareImages": {
+ "description": "Information about VNF package artifacts that are software images. This attribute shall not be present before the VNF package content is on-boarded. Otherwise, this attribute shall be present unless it has been requested to be excluded per attribute selector.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents an artifact contained in or external to a VNF package which represents a software image. NOTE 1:\tThe list of permitted values was taken from \"Container formats\" in OpenStack®: \"Disk and container formats for images\". NOTE 2:\tThe list of permitted values was adapted from \"Disk formats\" in OpenStack®: \"Disk and container formats for images\".\n",
+ "required": [
+ "id",
+ "name",
+ "provider",
+ "version",
+ "checksum",
+ "isEncrypted",
+ "containerFormat",
+ "diskFormat",
+ "createdAt",
+ "minDisk",
+ "minRam",
+ "size",
+ "imagePath"
+ ],
+ "type": "object",
+ "properties": {
+ "id": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
+ "type": "string"
+ },
+ "name": {
+ "description": "Name of the software image.\n",
+ "type": "string"
+ },
+ "provider": {
+ "description": "Provider of the software image.\n",
+ "type": "string"
+ },
+ "version": {
+ "description": "A Version. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "checksum": {
+ "description": "This type represents the checksum of a VNF package or an artifact file.\n",
+ "required": [
+ "algorithm",
+ "hash"
+ ],
+ "type": "object",
+ "properties": {
"algorithm": {
- "description": "Name of the algorithm used to generate the checksum, as defined in ETSI GS NFV-SOL 004 [5]. For example, SHA-256, SHA-512.\n",
- "type": "string"
+ "description": "Name of the algorithm used to generate the checksum, as defined in ETSI GS NFV-SOL 004 [5]. For example, SHA-256, SHA-512.\n",
+ "type": "string"
},
"hash": {
- "description": "The hexadecimal value of the checksum.\n",
- "type": "string"
+ "description": "The hexadecimal value of the checksum.\n",
+ "type": "string"
}
+ }
+ },
+ "isEncrypted": {
+ "description": "Reflects whether the image is encrypted (true) or not (false).\n",
+ "type": "boolean"
+ },
+ "containerFormat": {
+ "description": "Container format indicates whether the software image is in a file format that also contains meta-data about the actual software. Permitted values: - AKI: a kernel image format - AMI: a machine image format - ARI: a ram disk image format - BARE: the image does not have a container or meta-data envelope - DOCKER: docker container format - OVA: OVF package in a tar file - OVF: OVF container format\nSee note 1.\n",
+ "type": "string",
+ "enum": [
+ "AKI",
+ "AMI",
+ "ARI",
+ "BARE",
+ "DOCKER",
+ "OVA",
+ "OVF"
+ ]
+ },
+ "diskFormat": {
+ "description": "Disk format of a software image is the format of the underlying disk image. Permitted values: - AKI: a kernel image format - AMI: a machine image format - ARI: a ramdisk image format - ISO: an archive format for the data contents of an optical disc, such as CD-ROM - QCOW2: a common disk image format, which can expand dynamically and supports copy on write - RAW: an unstructured disk image format - VDI: a common disk image format - VHD: a common disk image format - VHDX: enhanced version of VHD format - VMDK: a common disk image format\nSee note 2.\n",
+ "type": "string",
+ "enum": [
+ "AKI",
+ "AMI",
+ "ARI",
+ "ISO",
+ "QCOW2",
+ "RAW",
+ "VDI",
+ "VHD",
+ "VHDX",
+ "VMDK"
+ ]
+ },
+ "createdAt": {
+ "description": "Date-time stamp. Representation: String formatted according toas defined by the date-time production in IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "minDisk": {
+ "description": "The minimal disk for this software image in bytes.\n",
+ "type": "integer",
+ "minimum": 0
+ },
+ "minRam": {
+ "description": "The minimal RAM for this software image in bytes.\n",
+ "type": "integer",
+ "minimum": 0
+ },
+ "size": {
+ "description": "Size of this software image in bytes.\n",
+ "type": "integer",
+ "minimum": 0
+ },
+ "userMetadata": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ },
+ "imagePath": {
+ "description": "Path, which identifies the image artifact and also allows to access a copy of the image artifact. For a software image 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 \"/\".\nEXAMPLE:\tfoo/bar/m%40ster.vhd\nFor an external software image represented as a URI in the VNF descriptor, this attribute shall be present if the image artifact has been downloaded by the NFVO and shall be absent otherwise. If present, it shall contain the artifactPath under which the image artifact can be obtained using the \"Individual artifact in a VNF package\" resource defined in clause 9.4.7. 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 image artifacts included in the package.\n",
+ "type": "string"
+ },
+ "imageUri": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string",
+ "format": "uri"
}
- },
- "packageSecurityOption": {
- "description": "Signals the security option used by the package as defined in clause 5.1 of ETSI GS NFV-SOL 004. It shall be present after the VNF package content has been on-boarded and absent otherwise. Valid values: - OPTION_1 - OPTION_2\n",
- "type": "string",
- "enum": ["OPTION_1", "OPTION_2"]
- },
- "signingCertificate": {
- "description": "The singleton signing certificate if it is included as a file in the VNF package.\n",
- "type": "string"
- },
- "softwareImages": {
- "description": "Information about VNF package artifacts that are software images. This attribute shall not be present before the VNF package content is on-boarded. Otherwise, this attribute shall be present unless it has been requested to be excluded per attribute selector.\n",
- "type": "array",
- "items": {
- "description": "This type represents an artifact contained in or external to a VNF package which represents a software image. NOTE 1:\tThe list of permitted values was taken from \"Container formats\" in OpenStack: \"Disk and container formats for images\". NOTE 2:\tThe list of permitted values was adapted from \"Disk formats\" in OpenStack: \"Disk and container formats for images\".\n",
- "required": ["id", "name", "provider", "version", "checksum", "isEncrypted", "containerFormat", "diskFormat", "createdAt", "minDisk", "minRam", "size", "imagePath"],
- "type": "object",
- "properties": {
- "id": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "name": {
- "description": "Name of the software image.\n",
- "type": "string"
- },
- "provider": {
- "description": "Provider of the software image.\n",
- "type": "string"
- },
- "version": {
- "description": "A Version. Representation: string of variable length.\n",
- "type": "string"
- },
- "checksum": {
- "description": "This type represents the checksum of a VNF package or an artifact file.\n",
- "required": ["algorithm", "hash"],
- "type": "object",
- "properties": {
- "algorithm": {
- "description": "Name of the algorithm used to generate the checksum, as defined in ETSI GS NFV-SOL 004 [5]. For example, SHA-256, SHA-512.\n",
- "type": "string"
- },
- "hash": {
- "description": "The hexadecimal value of the checksum.\n",
- "type": "string"
- }
- }
- },
- "isEncrypted": {
- "description": "Reflects whether the image is encrypted (true) or not (false).\n",
- "type": "boolean"
- },
- "containerFormat": {
- "description": "Container format indicates whether the software image is in a file format that also contains meta-data about the actual software. Permitted values: - AKI: a kernel image format - AMI: a machine image format - ARI: a ram disk image format - BARE: the image does not have a container or meta-data envelope - DOCKER: docker container format - OVA: OVF package in a tar file - OVF: OVF container format\nSee note 1.\n",
- "type": "string",
- "enum": ["AKI", "AMI", "ARI", "BARE", "DOCKER", "OVA", "OVF"]
- },
- "diskFormat": {
- "description": "Disk format of a software image is the format of the underlying disk image. Permitted values: - AKI: a kernel image format - AMI: a machine image format - ARI: a ramdisk image format - ISO: an archive format for the data contents of an optical disc, such as CD-ROM - QCOW2: a common disk image format, which can expand dynamically and supports copy on write - RAW: an unstructured disk image format - VDI: a common disk image format - VHD: a common disk image format - VHDX: enhanced version of VHD format - VMDK: a common disk image format\nSee note 2.\n",
- "type": "string",
- "enum": ["AKI", "AMI", "ARI", "ISO", "QCOW2", "RAW", "VDI", "VHD", "VHDX", "VMDK"]
- },
- "createdAt": {
- "description": "Date-time stamp. Representation: String formatted according toas defined by the date-time production in IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "minDisk": {
- "description": "The minimal disk for this software image in bytes.\n",
- "type": "integer",
- "minimum": 0
- },
- "minRam": {
- "description": "The minimal RAM for this software image in bytes.\n",
- "type": "integer",
- "minimum": 0
- },
- "size": {
- "description": "Size of this software image in bytes.\n",
- "type": "integer",
- "minimum": 0
- },
- "userMetadata": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- },
- "imagePath": {
- "description": "Path, which identifies the image artifact and also allows to access a copy of the image artifact. For a software image 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 \"/\".\nEXAMPLE:\tfoo/bar/m%40ster.vhd\nFor an external software image represented as a URI in the VNF descriptor, this attribute shall be present if the image artifact has been downloaded by the NFVO and shall be absent otherwise. If present, it shall contain the artifactPath under which the image artifact can be obtained using the \"Individual artifact in a VNF package\" resource defined in clause 9.4.7. 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 image artifacts included in the package.\n",
- "type": "string"
- },
- "imageUri": {
- "description": "String formatted according to IETF RFC 3986.\n",
- "type": "string",
- "format": "uri"
- }
- }
- }
- },
- "additionalArtifacts": {
- "description": "Information about VNF package artifacts contained in the VNF package that are not software images. 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.\n",
- "type": "array",
- "items": {
- "description": "This type represents an artifact other than a software image which is contained in or external to a VNF package. It shall comply with provisions defined in Table 9.5.3.3-1.\n",
- "required": ["isEncrypted", "checksum"],
- "type": "object",
- "properties": {
- "artifactPath": {
- "description": "A string as defined in IETF RFC 8259.\n",
- "type": "string"
- },
- "artifactURI": {
- "description": "String formatted according to IETF RFC 3986.\n",
- "type": "string",
- "format": "uri"
- },
- "checksum": {
- "description": "This type represents the checksum of a VNF package or an artifact file.\n",
- "required": ["algorithm", "hash"],
- "type": "object",
- "properties": {
- "algorithm": {
- "description": "Name of the algorithm used to generate the checksum, as defined in ETSI GS NFV-SOL 004 [5]. For example, SHA-256, SHA-512.\n",
- "type": "string"
- },
- "hash": {
- "description": "The hexadecimal value of the checksum.\n",
- "type": "string"
- }
- }
- },
- "isEncrypted": {
- "description": "Reflects whether the artifact is encrypted (true) or not (false).\n",
- "type": "boolean"
- },
- "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 [5]. Shall be provided if the artifact is a non-MANO artifact, and shall be omitted otherwise.\n",
- "type": "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\n",
- "type": "string",
- "enum": ["HISTORY", "TESTING", "LICENSE"]
- },
- "metadata": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
+ }
+ }
+ },
+ "additionalArtifacts": {
+ "description": "Information about VNF package artifacts contained in the VNF package that are not software images. 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.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents an artifact other than a software image which is contained in or external to a VNF package. It shall comply with provisions defined in Table 9.5.3.3-1.\nNOTE: The attribute name \"artifactURI\" does not comply with the naming convention defined in clause 4.3 of ETSI GS NFV-SOL 015. This is to maintain the backward compatibility.\n",
+ "required": [
+ "isEncrypted",
+ "checksum"
+ ],
+ "type": "object",
+ "properties": {
+ "artifactPath": {
+ "description": "A string as defined in IETF RFC 8259.\n",
+ "type": "string"
+ },
+ "artifactURI": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string",
+ "format": "uri"
+ },
+ "checksum": {
+ "description": "This type represents the checksum of a VNF package or an artifact file.\n",
+ "required": [
+ "algorithm",
+ "hash"
+ ],
+ "type": "object",
+ "properties": {
+ "algorithm": {
+ "description": "Name of the algorithm used to generate the checksum, as defined in ETSI GS NFV-SOL 004 [5]. For example, SHA-256, SHA-512.\n",
+ "type": "string"
+ },
+ "hash": {
+ "description": "The hexadecimal value of the checksum.\n",
+ "type": "string"
}
+ }
+ },
+ "isEncrypted": {
+ "description": "Reflects whether the artifact is encrypted (true) or not (false).\n",
+ "type": "boolean"
+ },
+ "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 [5]. Shall be provided if the artifact is a non-MANO artifact, and shall be omitted otherwise.\n",
+ "type": "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\n",
+ "type": "string",
+ "enum": [
+ "HISTORY",
+ "TESTING",
+ "LICENSE"
+ ]
+ },
+ "metadata": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
}
- },
- "onboardingState": {
- "description": "The enumeration PackageOnboardingStateType shall comply with the provisions defined in Table 9.5.4.3-1. Permitted values: - CREATED: The 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 is successfully on-boarded. - ERROR: There was an error during upload of the VNF package content or external artifacts, or during VNF package processing.\n",
- "type": "string",
- "enum": ["CREATED", "UPLOADING", "PROCESSING", "ONBOARDED", "ERROR"]
- },
- "operationalState": {
+ }
+ }
+ },
+ "onboardingState": {
+ "description": "The enumeration PackageOnboardingStateType shall comply with the provisions defined in Table 9.5.4.3-1. Permitted values: - CREATED: The 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 is successfully on-boarded. - ERROR: There was an error during upload of the VNF package content or external artifacts, or during VNF package processing.\n",
+ "type": "string",
+ "enum": [
+ "CREATED",
+ "UPLOADING",
+ "PROCESSING",
+ "ONBOARDED",
+ "ERROR"
+ ]
+ },
+ "operationalState": {
+ "type": "string",
+ "description": "\"The enumeration PackageOperationalStateType shall comply with the provisions defined in Table 9.5.4.4-1.\" Acceptable values are: - 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\n (unless and until the VNF package is re-enabled).\n",
+ "enum": [
+ "ENABLED",
+ "DISABLED"
+ ]
+ },
+ "usageState": {
+ "type": "string",
+ "description": "\"The enumeration PackageUsageStateType shall comply with the provisions. Acceptable values are: - IN_USE: \"Individual VNF instance\" resources created from this VNF package exist. - NOT_IN_USE: No \"individual VNF instance\" resource created from this VNF package exists.\n",
+ "enum": [
+ "IN_USE",
+ "NOT_IN_USE"
+ ]
+ },
+ "vnfmInfo": {
+ "description": "Specifies VNFMs compatible with the VNF. This information is copied from the VNFD of the on-boarded VNF package. See note 4. It shall be present after the VNF package content has been on-boarded and absent otherwise.\n",
+ "type": "array",
+ "items": {
+ "type": "string"
+ }
+ },
+ "userDefinedData": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ },
+ "onboardingFailureDetails": {
+ "description": "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 [19] is reproduced in this structure. Compared to the general framework defined in IETF RFC 7807 [19], the \"status\" and \"detail\" attributes are mandated to be included by the present document, to ensure that the response contains additional textual information about an error. IETF RFC 7807 [19] foresees extensibility of the \"ProblemDetails\" type. It is possible that particular APIs in the present document, or particular implementations, define extensions to define additional attributes that provide more information about the error. The description column only provides some explanation of the meaning to Facilitate understanding of the design. For a full description, see IETF RFC 7807 [19].\n",
+ "type": "object",
+ "required": [
+ "status",
+ "detail"
+ ],
+ "properties": {
+ "type": {
+ "description": "A URI reference according to IETF RFC 3986 [5] that identifies the problem type. It is encouraged that the URI provides human-readable documentation for the problem (e.g. using HTML) when dereferenced. When this member is not present, its value is assumed to be \"about:blank\".\n",
"type": "string",
- "description": "\"The enumeration PackageOperationalStateType shall comply with the provisions defined in Table 9.5.4.4-1.\" Acceptable values are: - 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).\n",
- "enum": ["ENABLED", "DISABLED"]
- },
- "usageState": {
+ "format": "URI"
+ },
+ "title": {
+ "description": "A short, human-readable summary of the problem type. It should not change from occurrence to occurrence of the problem, except for purposes of localization. If type is given and other than \"about:blank\", this attribute shall also be provided. A short, human-readable summary of the problem type. It SHOULD NOT change from occurrence to occurrence of the problem, except for purposes of localization (e.g., using proactive content negotiation; see [RFC7231], Section 3.4).\n",
+ "type": "string"
+ },
+ "status": {
+ "description": "The HTTP status code for this occurrence of the problem. The HTTP status code ([RFC7231], Section 6) generated by the origin server for this occurrence of the problem.\n",
+ "type": "integer"
+ },
+ "detail": {
+ "description": "A human-readable explanation specific to this occurrence of the problem.\n",
+ "type": "string"
+ },
+ "instance": {
+ "description": "A URI reference that identifies the specific occurrence of the problem. It may yield further information if dereferenced.\n",
"type": "string",
- "description": "\"The enumeration PackageUsageStateType shall comply with the provisions. Acceptable values are: - IN_USE: \"Individual VNF instance\" resources created from this VNF package exist. - NOT_IN_USE: No \"individual VNF instance\" resource created from this VNF package exists.\n",
- "enum": ["IN_USE", "NOT_IN_USE"]
- },
- "vnfmInfo": {
- "description": "Specifies VNFMs compatible with the VNF. This information is copied from the VNFD. See note 4.\n",
- "type": "array",
- "items": {
- "type": "string"
+ "format": "URI"
+ }
+ }
+ },
+ "_links": {
+ "type": "object",
+ "description": "Links to resources related to this resource.\n",
+ "required": [
+ "self",
+ "packageContent",
+ "vnfd"
+ ],
+ "properties": {
+ "self": {
+ "description": "This type represents a link to a resource.\n",
+ "type": "object",
+ "required": [
+ "href"
+ ],
+ "properties": {
+ "href": {
+ "description": "URI of a resource referenced from a notification. Should be an absolute URI (i.e. a URI that contains {apiRoot}), however, may be a relative URI (i.e. a URI where the {apiRoot} part is omitted) if the {apiRoot} information is not available.\n",
+ "type": "string",
+ "format": "url"
+ }
}
- },
- "userDefinedData": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- },
- "onboardingFailureDetails": {
- "description": "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 [19] is reproduced in this structure. Compared to the general framework defined in IETF RFC 7807 [19], the \"status\" and \"detail\" attributes are mandated to be included by the present document, to ensure that the response contains additional textual information about an error. IETF RFC 7807 [19] foresees extensibility of the \"ProblemDetails\" type. It is possible that particular APIs in the present document, or particular implementations, define extensions to define additional attributes that provide more information about the error. The description column only provides some explanation of the meaning to Facilitate understanding of the design. For a full description, see IETF RFC 7807 [19].\n",
+ },
+ "vnfd": {
+ "description": "This type represents a link to a resource.\n",
"type": "object",
- "required": ["status", "detail"],
+ "required": [
+ "href"
+ ],
"properties": {
- "type": {
- "description": "A URI reference according to IETF RFC 3986 [5] that identifies the problem type. It is encouraged that the URI provides human-readable documentation for the problem (e.g. using HTML) when dereferenced. When this member is not present, its value is assumed to be \"about:blank\".\n",
- "type": "string",
- "format": "URI"
- },
- "title": {
- "description": "A short, human-readable summary of the problem type. It should not change from occurrence to occurrence of the problem, except for purposes of localization. If type is given and other than \"about:blank\", this attribute shall also be provided. A short, human-readable summary of the problem type. It SHOULD NOT change from occurrence to occurrence of the problem, except for purposes of localization (e.g., using proactive content negotiation; see [RFC7231], Section 3.4).\n",
- "type": "string"
- },
- "status": {
- "description": "The HTTP status code for this occurrence of the problem. The HTTP status code ([RFC7231], Section 6) generated by the origin server for this occurrence of the problem.\n",
- "type": "integer"
- },
- "detail": {
- "description": "A human-readable explanation specific to this occurrence of the problem.\n",
- "type": "string"
- },
- "instance": {
- "description": "A URI reference that identifies the specific occurrence of the problem. It may yield further information if dereferenced.\n",
- "type": "string",
- "format": "URI"
- }
+ "href": {
+ "description": "URI of a resource referenced from a notification. Should be an absolute URI (i.e. a URI that contains {apiRoot}), however, may be a relative URI (i.e. a URI where the {apiRoot} part is omitted) if the {apiRoot} information is not available.\n",
+ "type": "string",
+ "format": "url"
+ }
}
- },
- "_links": {
+ },
+ "packageContent": {
+ "description": "This type represents a link to a resource.\n",
"type": "object",
- "description": "Links to resources related to this resource.\n",
- "required": ["self", "packageContent", "vnfd"],
+ "required": [
+ "href"
+ ],
"properties": {
- "self": {
- "description": "This type represents a link to a resource.\n",
- "type": "object",
- "required": ["href"],
- "properties": {
- "href": {
- "description": "URI of a resource referenced from a notification. Should be an absolute URI (i.e. a URI that contains {apiRoot}), however, may be a relative URI (i.e. a URI where the {apiRoot} part is omitted) if the {apiRoot} information is not available.\n",
- "type": "string",
- "format": "url"
- }
- }
- },
- "vnfd": {
- "description": "This type represents a link to a resource.\n",
- "type": "object",
- "required": ["href"],
- "properties": {
- "href": {
- "description": "URI of a resource referenced from a notification. Should be an absolute URI (i.e. a URI that contains {apiRoot}), however, may be a relative URI (i.e. a URI where the {apiRoot} part is omitted) if the {apiRoot} information is not available.\n",
- "type": "string",
- "format": "url"
- }
- }
- },
- "packageContent": {
- "description": "This type represents a link to a resource.\n",
- "type": "object",
- "required": ["href"],
- "properties": {
- "href": {
- "description": "URI of a resource referenced from a notification. Should be an absolute URI (i.e. a URI that contains {apiRoot}), however, may be a relative URI (i.e. a URI where the {apiRoot} part is omitted) if the {apiRoot} information is not available.\n",
- "type": "string",
- "format": "url"
- }
- }
- }
+ "href": {
+ "description": "URI of a resource referenced from a notification. Should be an absolute URI (i.e. a URI that contains {apiRoot}), however, may be a relative URI (i.e. a URI where the {apiRoot} part is omitted) if the {apiRoot} information is not available.\n",
+ "type": "string",
+ "format": "url"
+ }
}
+ }
}
+ }
}
-}
\ No newline at end of file
+ }
\ No newline at end of file
diff --git a/SOL005/VNFPackageManagement-API/schemas/vnfPkgsInfo.schema.json b/SOL005/VNFPackageManagement-API/schemas/vnfPkgsInfo.schema.json
index c9e165f061c64b5a03b59d5a6a7b3237e4dc6668..131c158bd23f8625cf387d390b8ee639684da897 100644
--- a/SOL005/VNFPackageManagement-API/schemas/vnfPkgsInfo.schema.json
+++ b/SOL005/VNFPackageManagement-API/schemas/vnfPkgsInfo.schema.json
@@ -1,305 +1,388 @@
{
"type": "array",
"items": {
- "description": "This type represents the information of a VNF package. It shall comply with the provisions defined in table 9.5.2.5-1.\nNOTE 1:\tIf the value of the onboardingState attribute is not equal to \"ONBOARDED\", the value of the operationalState attribute shall be equal to \"DISABLED\". NOTE 2:\tIf the value of the onboardingState attribute is not equal to \"ONBOARDED\", the value of the usageState attribute shall be equal to \"NOT_IN_USE\". NOTE 3:\tState changes of a VNF package are illustrated in clause B.2. NOTE 4:\tETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on TOSCA specifications.\n",
- "type": "object",
- "required": ["id", "onboardingState", "operationalState", "usageState", "vnfmInfo", "_links"],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfdExtInvariantId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfProvider": {
- "description": "Provider of the VNF package and the VNFD. This information is copied from the VNFD. It shall be present after the VNF package content has been on-boarded and absent otherwise.\n",
- "type": "string"
+ "description": "This type represents the information of a VNF package. It shall comply with the provisions defined in table 9.5.2.5-1.\nNOTE 1:\tIf the value of the onboardingState attribute is not equal to \"ONBOARDED\", the value of the operationalState attribute shall be equal to \"DISABLED\". NOTE 2:\tIf the value of the onboardingState attribute is not equal to \"ONBOARDED\", the value of the usageState attribute shall be equal to \"NOT_IN_USE\". NOTE 3:\tState changes of a VNF package are illustrated in clause B.2. NOTE 4:\tETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on TOSCA specifications.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "onboardingState",
+ "operationalState",
+ "usageState",
+ "_links"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfdExtInvariantId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfProvider": {
+ "description": "Provider of the VNF package and the VNFD. This information is copied from the VNFD. It shall be present after the VNF package content has been on-boarded and absent otherwise.\n",
+ "type": "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.\n",
+ "type": "string"
+ },
+ "vnfSoftwareVersion": {
+ "description": "A Version. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "vnfdVersion": {
+ "description": "A Version. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "compatibleSpecificationVersions": {
+ "description": "A Version. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "checksum": {
+ "description": "This type represents the checksum of a VNF package or an artifact file.\n",
+ "required": [
+ "algorithm",
+ "hash"
+ ],
+ "type": "object",
+ "properties": {
+ "algorithm": {
+ "description": "Name of the algorithm used to generate the checksum, as defined in ETSI GS NFV-SOL 004 [5]. For example, SHA-256, SHA-512.\n",
+ "type": "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.\n",
+ "hash": {
+ "description": "The hexadecimal value of the checksum.\n",
+ "type": "string"
+ }
+ }
+ },
+ "packageSecurityOption": {
+ "description": "Signals the security option used by the package as defined in clause 5.1 of ETSI GS NFV-SOL 004. It shall be present after the VNF package content has been on-boarded and absent otherwise. Valid values: - OPTION_1 - OPTION_2\n",
+ "type": "string",
+ "enum": [
+ "OPTION_1",
+ "OPTION_2"
+ ]
+ },
+ "signingCertificate": {
+ "description": "The singleton signing certificate if it is included as a file in the VNF package.\n",
+ "type": "string"
+ },
+ "softwareImages": {
+ "description": "Information about VNF package artifacts that are software images. This attribute shall not be present before the VNF package content is on-boarded. Otherwise, this attribute shall be present unless it has been requested to be excluded per attribute selector.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents an artifact contained in or external to a VNF package which represents a software image. NOTE 1:\tThe list of permitted values was taken from \"Container formats\" in OpenStack®: \"Disk and container formats for images\". NOTE 2:\tThe list of permitted values was adapted from \"Disk formats\" in OpenStack®: \"Disk and container formats for images\".\n",
+ "required": [
+ "id",
+ "name",
+ "provider",
+ "version",
+ "checksum",
+ "isEncrypted",
+ "containerFormat",
+ "diskFormat",
+ "createdAt",
+ "minDisk",
+ "minRam",
+ "size",
+ "imagePath"
+ ],
+ "type": "object",
+ "properties": {
+ "id": {
+ "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
"type": "string"
- },
- "vnfSoftwareVersion": {
- "description": "A Version. Representation: string of variable length.\n",
+ },
+ "name": {
+ "description": "Name of the software image.\n",
"type": "string"
- },
- "vnfdVersion": {
- "description": "A Version. Representation: string of variable length.\n",
+ },
+ "provider": {
+ "description": "Provider of the software image.\n",
"type": "string"
- },
- "compatibleSpecificationVersions": {
+ },
+ "version": {
"description": "A Version. Representation: string of variable length.\n",
"type": "string"
- },
- "checksum": {
+ },
+ "checksum": {
"description": "This type represents the checksum of a VNF package or an artifact file.\n",
- "required": ["algorithm", "hash"],
+ "required": [
+ "algorithm",
+ "hash"
+ ],
"type": "object",
"properties": {
- "algorithm": {
- "description": "Name of the algorithm used to generate the checksum, as defined in ETSI GS NFV-SOL 004 [5]. For example, SHA-256, SHA-512.\n",
- "type": "string"
- },
- "hash": {
- "description": "The hexadecimal value of the checksum.\n",
- "type": "string"
- }
+ "algorithm": {
+ "description": "Name of the algorithm used to generate the checksum, as defined in ETSI GS NFV-SOL 004 [5]. For example, SHA-256, SHA-512.\n",
+ "type": "string"
+ },
+ "hash": {
+ "description": "The hexadecimal value of the checksum.\n",
+ "type": "string"
+ }
}
- },
- "packageSecurityOption": {
- "description": "Signals the security option used by the package as defined in clause 5.1 of ETSI GS NFV-SOL 004. It shall be present after the VNF package content has been on-boarded and absent otherwise. Valid values: - OPTION_1 - OPTION_2\n",
+ },
+ "isEncrypted": {
+ "description": "Reflects whether the image is encrypted (true) or not (false).\n",
+ "type": "boolean"
+ },
+ "containerFormat": {
+ "description": "Container format indicates whether the software image is in a file format that also contains meta-data about the actual software. Permitted values: - AKI: a kernel image format - AMI: a machine image format - ARI: a ram disk image format - BARE: the image does not have a container or meta-data envelope - DOCKER: docker container format - OVA: OVF package in a tar file - OVF: OVF container format\nSee note 1.\n",
"type": "string",
- "enum": ["OPTION_1", "OPTION_2"]
- },
- "signingCertificate": {
- "description": "The singleton signing certificate if it is included as a file in the VNF package.\n",
- "type": "string"
- },
- "softwareImages": {
- "description": "Information about VNF package artifacts that are software images. This attribute shall not be present before the VNF package content is on-boarded. Otherwise, this attribute shall be present unless it has been requested to be excluded per attribute selector.\n",
- "type": "array",
- "items": {
- "description": "This type represents an artifact contained in or external to a VNF package which represents a software image. NOTE 1:\tThe list of permitted values was taken from \"Container formats\" in OpenStack: \"Disk and container formats for images\". NOTE 2:\tThe list of permitted values was adapted from \"Disk formats\" in OpenStack: \"Disk and container formats for images\".\n",
- "required": ["id", "name", "provider", "version", "checksum", "isEncrypted", "containerFormat", "diskFormat", "createdAt", "minDisk", "minRam", "size", "imagePath"],
- "type": "object",
- "properties": {
- "id": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "name": {
- "description": "Name of the software image.\n",
- "type": "string"
- },
- "provider": {
- "description": "Provider of the software image.\n",
- "type": "string"
- },
- "version": {
- "description": "A Version. Representation: string of variable length.\n",
- "type": "string"
- },
- "checksum": {
- "description": "This type represents the checksum of a VNF package or an artifact file.\n",
- "required": ["algorithm", "hash"],
- "type": "object",
- "properties": {
- "algorithm": {
- "description": "Name of the algorithm used to generate the checksum, as defined in ETSI GS NFV-SOL 004 [5]. For example, SHA-256, SHA-512.\n",
- "type": "string"
- },
- "hash": {
- "description": "The hexadecimal value of the checksum.\n",
- "type": "string"
- }
- }
- },
- "isEncrypted": {
- "description": "Reflects whether the image is encrypted (true) or not (false).\n",
- "type": "boolean"
- },
- "containerFormat": {
- "description": "Container format indicates whether the software image is in a file format that also contains meta-data about the actual software. Permitted values: - AKI: a kernel image format - AMI: a machine image format - ARI: a ram disk image format - BARE: the image does not have a container or meta-data envelope - DOCKER: docker container format - OVA: OVF package in a tar file - OVF: OVF container format\nSee note 1.\n",
- "type": "string",
- "enum": ["AKI", "AMI", "ARI", "BARE", "DOCKER", "OVA", "OVF"]
- },
- "diskFormat": {
- "description": "Disk format of a software image is the format of the underlying disk image. Permitted values: - AKI: a kernel image format - AMI: a machine image format - ARI: a ramdisk image format - ISO: an archive format for the data contents of an optical disc, such as CD-ROM - QCOW2: a common disk image format, which can expand dynamically and supports copy on write - RAW: an unstructured disk image format - VDI: a common disk image format - VHD: a common disk image format - VHDX: enhanced version of VHD format - VMDK: a common disk image format\nSee note 2.\n",
- "type": "string",
- "enum": ["AKI", "AMI", "ARI", "ISO", "QCOW2", "RAW", "VDI", "VHD", "VHDX", "VMDK"]
- },
- "createdAt": {
- "description": "Date-time stamp. Representation: String formatted according toas defined by the date-time production in IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "minDisk": {
- "description": "The minimal disk for this software image in bytes.\n",
- "type": "integer",
- "minimum": 0
- },
- "minRam": {
- "description": "The minimal RAM for this software image in bytes.\n",
- "type": "integer",
- "minimum": 0
- },
- "size": {
- "description": "Size of this software image in bytes.\n",
- "type": "integer",
- "minimum": 0
- },
- "userMetadata": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- },
- "imagePath": {
- "description": "Path, which identifies the image artifact and also allows to access a copy of the image artifact. For a software image 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 \"/\".\nEXAMPLE:\tfoo/bar/m%40ster.vhd\nFor an external software image represented as a URI in the VNF descriptor, this attribute shall be present if the image artifact has been downloaded by the NFVO and shall be absent otherwise. If present, it shall contain the artifactPath under which the image artifact can be obtained using the \"Individual artifact in a VNF package\" resource defined in clause 9.4.7. 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 image artifacts included in the package.\n",
- "type": "string"
- },
- "imageUri": {
- "description": "String formatted according to IETF RFC 3986.\n",
- "type": "string",
- "format": "uri"
- }
- }
- }
- },
- "additionalArtifacts": {
- "description": "Information about VNF package artifacts contained in the VNF package that are not software images. 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.\n",
- "type": "array",
- "items": {
- "description": "This type represents an artifact other than a software image which is contained in or external to a VNF package. It shall comply with provisions defined in Table 9.5.3.3-1.\n",
- "required": ["isEncrypted", "checksum"],
- "type": "object",
- "properties": {
- "artifactPath": {
- "description": "A string as defined in IETF RFC 8259.\n",
- "type": "string"
- },
- "artifactURI": {
- "description": "String formatted according to IETF RFC 3986.\n",
- "type": "string",
- "format": "uri"
- },
- "checksum": {
- "description": "This type represents the checksum of a VNF package or an artifact file.\n",
- "required": ["algorithm", "hash"],
- "type": "object",
- "properties": {
- "algorithm": {
- "description": "Name of the algorithm used to generate the checksum, as defined in ETSI GS NFV-SOL 004 [5]. For example, SHA-256, SHA-512.\n",
- "type": "string"
- },
- "hash": {
- "description": "The hexadecimal value of the checksum.\n",
- "type": "string"
- }
- }
- },
- "isEncrypted": {
- "description": "Reflects whether the artifact is encrypted (true) or not (false).\n",
- "type": "boolean"
- },
- "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 [5]. Shall be provided if the artifact is a non-MANO artifact, and shall be omitted otherwise.\n",
- "type": "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\n",
- "type": "string",
- "enum": ["HISTORY", "TESTING", "LICENSE"]
- },
- "metadata": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
- "type": "object"
- }
- }
- }
- },
- "onboardingState": {
- "description": "The enumeration PackageOnboardingStateType shall comply with the provisions defined in Table 9.5.4.3-1. Permitted values: - CREATED: The 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 is successfully on-boarded. - ERROR: There was an error during upload of the VNF package content or external artifacts, or during VNF package processing.\n",
+ "enum": [
+ "AKI",
+ "AMI",
+ "ARI",
+ "BARE",
+ "DOCKER",
+ "OVA",
+ "OVF"
+ ]
+ },
+ "diskFormat": {
+ "description": "Disk format of a software image is the format of the underlying disk image. Permitted values: - AKI: a kernel image format - AMI: a machine image format - ARI: a ramdisk image format - ISO: an archive format for the data contents of an optical disc, such as CD-ROM - QCOW2: a common disk image format, which can expand dynamically and supports copy on write - RAW: an unstructured disk image format - VDI: a common disk image format - VHD: a common disk image format - VHDX: enhanced version of VHD format - VMDK: a common disk image format\nSee note 2.\n",
"type": "string",
- "enum": ["CREATED", "UPLOADING", "PROCESSING", "ONBOARDED", "ERROR"]
- },
- "operationalState": {
+ "enum": [
+ "AKI",
+ "AMI",
+ "ARI",
+ "ISO",
+ "QCOW2",
+ "RAW",
+ "VDI",
+ "VHD",
+ "VHDX",
+ "VMDK"
+ ]
+ },
+ "createdAt": {
+ "description": "Date-time stamp. Representation: String formatted according toas defined by the date-time production in IETF RFC 3339.\n",
"type": "string",
- "description": "\"The enumeration PackageOperationalStateType shall comply with the provisions defined in Table 9.5.4.4-1.\" Acceptable values are: - 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).\n",
- "enum": ["ENABLED", "DISABLED"]
- },
- "usageState": {
+ "format": "date-time"
+ },
+ "minDisk": {
+ "description": "The minimal disk for this software image in bytes.\n",
+ "type": "integer",
+ "minimum": 0
+ },
+ "minRam": {
+ "description": "The minimal RAM for this software image in bytes.\n",
+ "type": "integer",
+ "minimum": 0
+ },
+ "size": {
+ "description": "Size of this software image in bytes.\n",
+ "type": "integer",
+ "minimum": 0
+ },
+ "userMetadata": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ },
+ "imagePath": {
+ "description": "Path, which identifies the image artifact and also allows to access a copy of the image artifact. For a software image 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 \"/\".\nEXAMPLE:\tfoo/bar/m%40ster.vhd\nFor an external software image represented as a URI in the VNF descriptor, this attribute shall be present if the image artifact has been downloaded by the NFVO and shall be absent otherwise. If present, it shall contain the artifactPath under which the image artifact can be obtained using the \"Individual artifact in a VNF package\" resource defined in clause 9.4.7. 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 image artifacts included in the package.\n",
+ "type": "string"
+ },
+ "imageUri": {
+ "description": "String formatted according to IETF RFC 3986.\n",
"type": "string",
- "description": "\"The enumeration PackageUsageStateType shall comply with the provisions. Acceptable values are: - IN_USE: \"Individual VNF instance\" resources created from this VNF package exist. - NOT_IN_USE: No \"individual VNF instance\" resource created from this VNF package exists.\n",
- "enum": ["IN_USE", "NOT_IN_USE"]
- },
- "vnfmInfo": {
- "description": "Specifies VNFMs compatible with the VNF. This information is copied from the VNFD. See note 4.\n",
- "type": "array",
- "items": {
+ "format": "uri"
+ }
+ }
+ }
+ },
+ "additionalArtifacts": {
+ "description": "Information about VNF package artifacts contained in the VNF package that are not software images. 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.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents an artifact other than a software image which is contained in or external to a VNF package. It shall comply with provisions defined in Table 9.5.3.3-1.\nNOTE: The attribute name \"artifactURI\" does not comply with the naming convention defined in clause 4.3 of ETSI GS NFV-SOL 015. This is to maintain the backward compatibility.\n",
+ "required": [
+ "isEncrypted",
+ "checksum"
+ ],
+ "type": "object",
+ "properties": {
+ "artifactPath": {
+ "description": "A string as defined in IETF RFC 8259.\n",
+ "type": "string"
+ },
+ "artifactURI": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string",
+ "format": "uri"
+ },
+ "checksum": {
+ "description": "This type represents the checksum of a VNF package or an artifact file.\n",
+ "required": [
+ "algorithm",
+ "hash"
+ ],
+ "type": "object",
+ "properties": {
+ "algorithm": {
+ "description": "Name of the algorithm used to generate the checksum, as defined in ETSI GS NFV-SOL 004 [5]. For example, SHA-256, SHA-512.\n",
"type": "string"
+ },
+ "hash": {
+ "description": "The hexadecimal value of the checksum.\n",
+ "type": "string"
+ }
}
- },
- "userDefinedData": {
+ },
+ "isEncrypted": {
+ "description": "Reflects whether the artifact is encrypted (true) or not (false).\n",
+ "type": "boolean"
+ },
+ "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 [5]. Shall be provided if the artifact is a non-MANO artifact, and shall be omitted otherwise.\n",
+ "type": "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\n",
+ "type": "string",
+ "enum": [
+ "HISTORY",
+ "TESTING",
+ "LICENSE"
+ ]
+ },
+ "metadata": {
"description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
"type": "object"
+ }
+ }
+ }
+ },
+ "onboardingState": {
+ "description": "The enumeration PackageOnboardingStateType shall comply with the provisions defined in Table 9.5.4.3-1. Permitted values: - CREATED: The 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 is successfully on-boarded. - ERROR: There was an error during upload of the VNF package content or external artifacts, or during VNF package processing.\n",
+ "type": "string",
+ "enum": [
+ "CREATED",
+ "UPLOADING",
+ "PROCESSING",
+ "ONBOARDED",
+ "ERROR"
+ ]
+ },
+ "operationalState": {
+ "type": "string",
+ "description": "\"The enumeration PackageOperationalStateType shall comply with the provisions defined in Table 9.5.4.4-1.\" Acceptable values are: - 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\n (unless and until the VNF package is re-enabled).\n",
+ "enum": [
+ "ENABLED",
+ "DISABLED"
+ ]
+ },
+ "usageState": {
+ "type": "string",
+ "description": "\"The enumeration PackageUsageStateType shall comply with the provisions. Acceptable values are: - IN_USE: \"Individual VNF instance\" resources created from this VNF package exist. - NOT_IN_USE: No \"individual VNF instance\" resource created from this VNF package exists.\n",
+ "enum": [
+ "IN_USE",
+ "NOT_IN_USE"
+ ]
+ },
+ "vnfmInfo": {
+ "description": "Specifies VNFMs compatible with the VNF. This information is copied from the VNFD of the on-boarded VNF package. See note 4. It shall be present after the VNF package content has been on-boarded and absent otherwise.\n",
+ "type": "array",
+ "items": {
+ "type": "string"
+ }
+ },
+ "userDefinedData": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "type": "object"
+ },
+ "onboardingFailureDetails": {
+ "description": "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 [19] is reproduced in this structure. Compared to the general framework defined in IETF RFC 7807 [19], the \"status\" and \"detail\" attributes are mandated to be included by the present document, to ensure that the response contains additional textual information about an error. IETF RFC 7807 [19] foresees extensibility of the \"ProblemDetails\" type. It is possible that particular APIs in the present document, or particular implementations, define extensions to define additional attributes that provide more information about the error. The description column only provides some explanation of the meaning to Facilitate understanding of the design. For a full description, see IETF RFC 7807 [19].\n",
+ "type": "object",
+ "required": [
+ "status",
+ "detail"
+ ],
+ "properties": {
+ "type": {
+ "description": "A URI reference according to IETF RFC 3986 [5] that identifies the problem type. It is encouraged that the URI provides human-readable documentation for the problem (e.g. using HTML) when dereferenced. When this member is not present, its value is assumed to be \"about:blank\".\n",
+ "type": "string",
+ "format": "URI"
},
- "onboardingFailureDetails": {
- "description": "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 [19] is reproduced in this structure. Compared to the general framework defined in IETF RFC 7807 [19], the \"status\" and \"detail\" attributes are mandated to be included by the present document, to ensure that the response contains additional textual information about an error. IETF RFC 7807 [19] foresees extensibility of the \"ProblemDetails\" type. It is possible that particular APIs in the present document, or particular implementations, define extensions to define additional attributes that provide more information about the error. The description column only provides some explanation of the meaning to Facilitate understanding of the design. For a full description, see IETF RFC 7807 [19].\n",
- "type": "object",
- "required": ["status", "detail"],
- "properties": {
- "type": {
- "description": "A URI reference according to IETF RFC 3986 [5] that identifies the problem type. It is encouraged that the URI provides human-readable documentation for the problem (e.g. using HTML) when dereferenced. When this member is not present, its value is assumed to be \"about:blank\".\n",
- "type": "string",
- "format": "URI"
- },
- "title": {
- "description": "A short, human-readable summary of the problem type. It should not change from occurrence to occurrence of the problem, except for purposes of localization. If type is given and other than \"about:blank\", this attribute shall also be provided. A short, human-readable summary of the problem type. It SHOULD NOT change from occurrence to occurrence of the problem, except for purposes of localization (e.g., using proactive content negotiation; see [RFC7231], Section 3.4).\n",
- "type": "string"
- },
- "status": {
- "description": "The HTTP status code for this occurrence of the problem. The HTTP status code ([RFC7231], Section 6) generated by the origin server for this occurrence of the problem.\n",
- "type": "integer"
- },
- "detail": {
- "description": "A human-readable explanation specific to this occurrence of the problem.\n",
- "type": "string"
- },
- "instance": {
- "description": "A URI reference that identifies the specific occurrence of the problem. It may yield further information if dereferenced.\n",
- "type": "string",
- "format": "URI"
- }
+ "title": {
+ "description": "A short, human-readable summary of the problem type. It should not change from occurrence to occurrence of the problem, except for purposes of localization. If type is given and other than \"about:blank\", this attribute shall also be provided. A short, human-readable summary of the problem type. It SHOULD NOT change from occurrence to occurrence of the problem, except for purposes of localization (e.g., using proactive content negotiation; see [RFC7231], Section 3.4).\n",
+ "type": "string"
+ },
+ "status": {
+ "description": "The HTTP status code for this occurrence of the problem. The HTTP status code ([RFC7231], Section 6) generated by the origin server for this occurrence of the problem.\n",
+ "type": "integer"
+ },
+ "detail": {
+ "description": "A human-readable explanation specific to this occurrence of the problem.\n",
+ "type": "string"
+ },
+ "instance": {
+ "description": "A URI reference that identifies the specific occurrence of the problem. It may yield further information if dereferenced.\n",
+ "type": "string",
+ "format": "URI"
+ }
+ }
+ },
+ "_links": {
+ "type": "object",
+ "description": "Links to resources related to this resource.\n",
+ "required": [
+ "self",
+ "packageContent",
+ "vnfd"
+ ],
+ "properties": {
+ "self": {
+ "description": "This type represents a link to a resource.\n",
+ "type": "object",
+ "required": [
+ "href"
+ ],
+ "properties": {
+ "href": {
+ "description": "URI of a resource referenced from a notification. Should be an absolute URI (i.e. a URI that contains {apiRoot}), however, may be a relative URI (i.e. a URI where the {apiRoot} part is omitted) if the {apiRoot} information is not available.\n",
+ "type": "string",
+ "format": "url"
}
+ }
},
- "_links": {
- "type": "object",
- "description": "Links to resources related to this resource.\n",
- "required": ["self", "packageContent", "vnfd"],
- "properties": {
- "self": {
- "description": "This type represents a link to a resource.\n",
- "type": "object",
- "required": ["href"],
- "properties": {
- "href": {
- "description": "URI of a resource referenced from a notification. Should be an absolute URI (i.e. a URI that contains {apiRoot}), however, may be a relative URI (i.e. a URI where the {apiRoot} part is omitted) if the {apiRoot} information is not available.\n",
- "type": "string",
- "format": "url"
- }
- }
- },
- "vnfd": {
- "description": "This type represents a link to a resource.\n",
- "type": "object",
- "required": ["href"],
- "properties": {
- "href": {
- "description": "URI of a resource referenced from a notification. Should be an absolute URI (i.e. a URI that contains {apiRoot}), however, may be a relative URI (i.e. a URI where the {apiRoot} part is omitted) if the {apiRoot} information is not available.\n",
- "type": "string",
- "format": "url"
- }
- }
- },
- "packageContent": {
- "description": "This type represents a link to a resource.\n",
- "type": "object",
- "required": ["href"],
- "properties": {
- "href": {
- "description": "URI of a resource referenced from a notification. Should be an absolute URI (i.e. a URI that contains {apiRoot}), however, may be a relative URI (i.e. a URI where the {apiRoot} part is omitted) if the {apiRoot} information is not available.\n",
- "type": "string",
- "format": "url"
- }
- }
- }
+ "vnfd": {
+ "description": "This type represents a link to a resource.\n",
+ "type": "object",
+ "required": [
+ "href"
+ ],
+ "properties": {
+ "href": {
+ "description": "URI of a resource referenced from a notification. Should be an absolute URI (i.e. a URI that contains {apiRoot}), however, may be a relative URI (i.e. a URI where the {apiRoot} part is omitted) if the {apiRoot} information is not available.\n",
+ "type": "string",
+ "format": "url"
+ }
+ }
+ },
+ "packageContent": {
+ "description": "This type represents a link to a resource.\n",
+ "type": "object",
+ "required": [
+ "href"
+ ],
+ "properties": {
+ "href": {
+ "description": "URI of a resource referenced from a notification. Should be an absolute URI (i.e. a URI that contains {apiRoot}), however, may be a relative URI (i.e. a URI where the {apiRoot} part is omitted) if the {apiRoot} information is not available.\n",
+ "type": "string",
+ "format": "url"
}
+ }
}
+ }
}
+ }
}
-}
\ No newline at end of file
+ }
\ No newline at end of file
diff --git a/SOL005/VNFSnapshotPackageManagement-API/AccessConfigurationForExternalArtifacts.robot b/SOL005/VNFSnapshotPackageManagement-API/AccessConfigurationForExternalArtifacts.robot
index ae16fc6ce482514b9af7efa5e932c98dac933b6e..4b470a4097e26e1738fd5be08e246d2b0b567a33 100644
--- a/SOL005/VNFSnapshotPackageManagement-API/AccessConfigurationForExternalArtifacts.robot
+++ b/SOL005/VNFSnapshotPackageManagement-API/AccessConfigurationForExternalArtifacts.robot
@@ -7,7 +7,7 @@ POST Access Configuration for External Artifacts - Method not implemented
... Test title: POST Access Configuration for External Artifacts - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: Individual VNF Snapshot Package resource have been created.
- ... Reference: Clause 11.4.9.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.9.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -19,7 +19,7 @@ GET Access Configuration for External Artifacts
... Test title: GET Access Configuration for External Artifacts
... Test objective: The objective is to test that GET method reads the access configuration information that is used by the NFVO to get the content of external VNF snapshot package artifacts.
... Pre-conditions: Individual VNF Snapshot Package resource have been created.
- ... Reference: Clause 11.4.9.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.9.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -32,7 +32,7 @@ PUT Access Configuration for External Artifacts
... Test title: PUT Access Configuration for External Artifacts
... Test objective: The objective is to test that PUT method provides the access configuration information for the NFVO to download the content of external VNF package artifacts.
... Pre-conditions: Individual VNF Snapshot Package resource have been created.
- ... Reference: Clause 11.4.9.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.9.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -45,7 +45,7 @@ PUT Access Configuration for External Artifacts - Conflict
... Test title: PUT Access Configuration for External Artifacts - Conflict
... Test objective: The objective is to test that PUT method cannot provide the access configuration information to the NFVO when the VNF Snapshot Package resource is not in CREATED or ERROR state.
... Pre-conditions: Individual VNF Snapshot Package resource have been created.
- ... Reference: Clause 11.4.9.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.9.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The "state" attribute of the "Individual VNF snapshot package" resources contains a value different from "CREATED" or "ERROR".
... Post-Conditions: none
@@ -58,7 +58,7 @@ PATCH Access Configuration for External Artifacts - Method Not implemented
... Test title: PATCH Access Configuration for External Artifacts - Method Not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 11.4.8.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.8.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -70,7 +70,7 @@ DELETE Access Configuration for External Artifacts - Method Not implemented
... Test title: DELETE Access Configuration for External Artifacts - Method Not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 11.4.8.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.8.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/VNFSnapshotPackageManagement-API/ApiVersion.robot b/SOL005/VNFSnapshotPackageManagement-API/ApiVersion.robot
index 8f7d9b223163e1e881309cb01913115536248baf..6900c202c5de3c6e80cd6bf1533124860edbb016 100644
--- a/SOL005/VNFSnapshotPackageManagement-API/ApiVersion.robot
+++ b/SOL005/VNFSnapshotPackageManagement-API/ApiVersion.robot
@@ -7,7 +7,7 @@ POST API Version - Method not implemented
... Test title: POST API version - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -19,7 +19,7 @@ GET API Version
... Test title: GET API Version
... Test objective: The objective is to test that GET method successfully return ApiVersionInformation
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -32,7 +32,7 @@ PUT API Version - Method not implemented
... Test title: PUT API Version - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -44,7 +44,7 @@ PATCH API Version - Method not implemented
... Test title: PATCH API Version - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -56,7 +56,7 @@ DELETE API Version - Method not implemented
... Test title: DELETE API Version - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -68,7 +68,7 @@ POST API Version with apiMajorVerion - Method not implemented
... Test title: POST API version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -80,7 +80,7 @@ GET API Version with apiMajorVerion
... Test title: GET API Version with apiMajorVerion
... Test objective: The objective is to test that GET method successfully return ApiVersionInformation
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -93,7 +93,7 @@ PUT API Version with apiMajorVerion - Method not implemented
... Test title: PUT API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -105,7 +105,7 @@ PATCH API Version with apiMajorVerion - Method not implemented
... Test title: PATCH API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -117,7 +117,7 @@ DELETE API Version with apiMajorVerion - Method not implemented
... Test title: DELETE API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/VNFSnapshotPackageManagement-API/BuildVNFSnapshotPackageContentTask.robot b/SOL005/VNFSnapshotPackageManagement-API/BuildVNFSnapshotPackageContentTask.robot
index 1adf0ed4bc91c87a5207dcded24f9308a3d74e5c..f9b9cc1d0fffd2bdfe9eda7b482ad522cede19d9 100644
--- a/SOL005/VNFSnapshotPackageManagement-API/BuildVNFSnapshotPackageContentTask.robot
+++ b/SOL005/VNFSnapshotPackageManagement-API/BuildVNFSnapshotPackageContentTask.robot
@@ -7,7 +7,7 @@ POST Build VNF Snapshot Package Content Task
... Test title: POST Build VNF Snapshot Package Content Task
... Test objective: The objective is to test that POST method provides the information for the NFVO to start building the content of a VNF snapshot package.
... Pre-conditions: none
- ... Reference: Clause 11.4.6.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.6.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -19,7 +19,7 @@ POST Build VNF Snapshot Package Content Task - Conflict
... Test title: POST Build VNF Snapshot Package Content Task - Conflict
... Test objective: The objective is to test that a correct error code is returned when the POST method tries to intiate building of VNF Snapshot Package and the state of the VNF snapshot package resource is other than "CREATED".
... Pre-conditions: none
- ... Reference: Clause 11.4.6.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.6.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The state of the VNF snapshot package resource is other than "CREATED".
... Post-Conditions: none
@@ -32,7 +32,7 @@ GET Build VNF Snapshot Package Content Task - Method Not implemented
... Test title: GET Build VNF Snapshot Package Content Task - Method Not implemented
... Test objective: The objective is to test that GET method is not implemented
... Pre-conditions: none
- ... Reference: Clause 11.4.6.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.6.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -44,7 +44,7 @@ PUT Build VNF Snapshot Package Content Task - Method Not implemented
... Test title: PUT Build VNF Snapshot Package Content Task - Method Not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 11.4.6.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.6.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -56,7 +56,7 @@ PATCH Build VNF Snapshot Package Content Task - Method Not implemented
... Test title: PATCH Build VNF Snapshot Package Content Task - Method Not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 11.4.6.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.6.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -68,7 +68,7 @@ DELETE Build VNF Snapshot Package Content Task - Method Not implemented
... Test title: DELETE Build VNF Snapshot Package Content Task - Method Not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 11.4.6.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.6.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/VNFSnapshotPackageManagement-API/CancelVNFSnapshotPackageOperationTask.robot b/SOL005/VNFSnapshotPackageManagement-API/CancelVNFSnapshotPackageOperationTask.robot
index a37504eb2975bfef2d2cc6fc9141a46c4d71b5db..68b074140a80f7ef2697616e468b050873ccc977 100644
--- a/SOL005/VNFSnapshotPackageManagement-API/CancelVNFSnapshotPackageOperationTask.robot
+++ b/SOL005/VNFSnapshotPackageManagement-API/CancelVNFSnapshotPackageOperationTask.robot
@@ -7,7 +7,7 @@ POST Cancel VNF Snapshot Package Content Task
... Test title: POST Cancel VNF Snapshot Package Content Task
... Test objective: The objective is to test that POST method provides the information for the NFVO to cancel the ongoing operation related to the content of a VNF snapshot package.
... Pre-conditions: none
- ... Reference: Clause 11.4.8.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.8.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -19,7 +19,7 @@ POST Cancel VNF Snapshot Package Content Task - Conflict
... Test title: POST Cancel VNF Snapshot Package Content Task - Conflict
... Test objective: The objective is to test that a correct error code is returned when the POST method tries to cancel a VNF Snapshot Package task and the state of the VNF snapshot package resource is other than "UPLOADING", "BUILDING", "PROCESSING" or "EXTRACTING".
... Pre-conditions: none
- ... Reference: Clause 11.4.8.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.8.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The state of the VNF snapshot package resource is other than "UPLOADING", "BUILDING", "PROCESSING" or "EXTRACTING".
... Post-Conditions: none
@@ -32,7 +32,7 @@ GET Cancel VNF Snapshot Package Content Task - Method Not implemented
... Test title: GET Cancel VNF Snapshot Package Content Task - Method Not implemented
... Test objective: The objective is to test that GET method is not implemented
... Pre-conditions: none
- ... Reference: Clause 11.4.8.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.8.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -44,7 +44,7 @@ PUT Cancel VNF Snapshot Package Content Task - Method Not implemented
... Test title: PUT Cancel VNF Snapshot Package Content Task - Method Not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 11.4.8.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.8.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -56,7 +56,7 @@ PATCH Cancel VNF Snapshot Package Content Task - Method Not implemented
... Test title: PATCH Cancel VNF Snapshot Package Content Task - Method Not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 11.4.8.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.8.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -68,7 +68,7 @@ DELETE Cancel VNF Snapshot Package Content Task - Method Not implemented
... Test title: DELETE Cancel VNF Snapshot Package Content Task - Method Not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 11.4.8.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.8.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/VNFSnapshotPackageManagement-API/ExtractVNFSnapshotPackageContentTask.robot b/SOL005/VNFSnapshotPackageManagement-API/ExtractVNFSnapshotPackageContentTask.robot
index dec6b8c119898f137a1a955fd1a40a0b5e7030ed..79984eac5217aef78aed55d790dbcb52f3f36678 100644
--- a/SOL005/VNFSnapshotPackageManagement-API/ExtractVNFSnapshotPackageContentTask.robot
+++ b/SOL005/VNFSnapshotPackageManagement-API/ExtractVNFSnapshotPackageContentTask.robot
@@ -7,7 +7,7 @@ POST Extract VNF Snapshot Package Content Task
... Test title: POST Extract VNF Snapshot Package Content Task
... Test objective: The objective is to test that POST method provides the information for the NFVO to start extracting the content of a VNF snapshot package.
... Pre-conditions: none
- ... Reference: Clause 11.4.7.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.7.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -19,7 +19,7 @@ POST Extract VNF Snapshot Package Content Task - Conflict State
... Test title: POST Extract VNF Snapshot Package Content Task - Conflict
... Test objective: The objective is to test that a correct error code is returned when the POST method tries to intiate extraction of VNF Snapshot Package and the state of the VNF snapshot package resource is other than "AVAILABLE".
... Pre-conditions: none
- ... Reference: Clause 11.4.7.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.7.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The state of the VNF snapshot package resource is other than "AVAILABLE".
... Post-Conditions: none
@@ -32,7 +32,7 @@ POST Extract VNF Snapshot Package Content Task - Invalid VnfInstanceId
... Test title: POST Extract VNF Snapshot Package Content Task - Conflict
... Test objective: The objective is to test that a correct error code is returned when the POST method tries to intiate extraction of VNF Snapshot Package using an invalid VnfInstanceId in the request body.
... Pre-conditions: none
- ... Reference: Clause 11.4.7.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.7.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The state of the VNF snapshot package resource is other than "CREATED".
... Post-Conditions: none
@@ -45,7 +45,7 @@ GET Extract VNF Snapshot Package Content Task - Method Not implemented
... Test title: GET Extract VNF Snapshot Package Content Task - Method Not implemented
... Test objective: The objective is to test that GET method is not implemented
... Pre-conditions: none
- ... Reference: Clause 11.4.7.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.7.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -57,7 +57,7 @@ PUT Extract VNF Snapshot Package Content Task - Method Not implemented
... Test title: PUT Extract VNF Snapshot Package Content Task - Method Not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 11.4.7.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.7.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -69,7 +69,7 @@ PATCH Extract VNF Snapshot Package Content Task - Method Not implemented
... Test title: PATCH Extract VNF Snapshot Package Content Task - Method Not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 11.4.7.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.7.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -81,7 +81,7 @@ DELETE Extract VNF Snapshot Package Content Task - Method Not implemented
... Test title: DELETE Extract VNF Snapshot Package Content Task - Method Not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 11.4.7.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.7.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/VNFSnapshotPackageManagement-API/IndividualVNFSnapshotPackage.robot b/SOL005/VNFSnapshotPackageManagement-API/IndividualVNFSnapshotPackage.robot
index 9361a41e4062a1ce7be5692a0e7162f1ed0e2f5e..83570a23e7d854ae834acdfc6db09232fee7badf 100644
--- a/SOL005/VNFSnapshotPackageManagement-API/IndividualVNFSnapshotPackage.robot
+++ b/SOL005/VNFSnapshotPackageManagement-API/IndividualVNFSnapshotPackage.robot
@@ -7,7 +7,7 @@ POST Individual VNF Snapshot Package - Method not implemented
... Test title: POST Individual VNF Snapshot Package - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 11.4.3.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.3.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -19,7 +19,7 @@ GET Information about an individual VNF Snapshot Package - SUCCESSFUL
... Test title: GET Information about an individual VNF Snapshot Package - SUCCESSFUL
... Test objective: The objective is to create a new VNF Snapshot Package resource
... Pre-conditions: none
- ... Reference: Clause 11.4.3.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.3.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -32,7 +32,7 @@ GET Information about an individual VNF Snapshot Package - NOT FOUND
... Test title: GET Information about an individual VNF Snapshot Package - NOT FOUND
... Test objective: The objective is to test that the retrieval of individual VNF Snapshot Package fails when using an invalid resource identifier.
... Pre-conditions: At least one individual VNF Snapshot Package is available in the NFV-MANO.
- ... Reference: Clause 11.4.3.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.3.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -45,7 +45,7 @@ PUT Individual VNF Snapshot Package - Method not implemented
... Test title: PUT Individual VNF Snapshot Package - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 11.4.3.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.3.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: VNF Snapshot Package not modified
@@ -57,7 +57,7 @@ PATCH Individual VNF Snapshot Package - Modified
... Test title: PATCH Individual VNF Snapshot Package - Modified
... Test objective: The objective is to test that PATCH method updates the information of a VNF Snapshot package
... Pre-conditions: none
- ... Reference: Clause 11.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -70,7 +70,7 @@ PATCH Individual VNF Snapshot Package - Conflict
... Test title: PATCH Individual VNF Snapshot Package - Conflict
... Test objective: The objective is to test that PATCH method does not update the information of a VNF Snapshot package when the state of the VNF snapshot package resource is in a state other than CREATED, ERROR_EXTRACTING or AVAILABLE.
... Pre-conditions: none
- ... Reference: Clause 11.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The state of the VNF snapshot package resource is in a state other than CREATED, ERROR_EXTRACTING or AVAILABLE.
... Post-Conditions: none
@@ -83,7 +83,7 @@ DELETE Individual VNF Snapshot Package
... Test title: DELETE Individual VNF Snapshot Package
... Test objective: The objective is to test that DELETE method deletes an individual VNF Snapshot Package resource
... Pre-conditions: none
- ... Reference: Clause 11.4.3.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.3.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: VNF Snapshot Package deleted
@@ -95,7 +95,7 @@ DELETE Individual VNF Snapshot Package - Conflict
... Test title: DELETE Individual VNF Snapshot Package - Method Not im
... Test objective: The objective is to test that DELETE method does not delete a VNF Snapshot package when the state of the VNF snapshot package resource is in a state other than CREATED, ERROR or AVAILABLE.
... Pre-conditions: none
- ... Reference: Clause 11.4.3.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.3.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The state of the VNF snapshot package resource is in a state other than CREATED, ERROR or AVAILABLE.
... Post-Conditions: VNF Snapshot Package not deleted
diff --git a/SOL005/VNFSnapshotPackageManagement-API/IndividualVNFSnapshotPackageArtifact.robot b/SOL005/VNFSnapshotPackageManagement-API/IndividualVNFSnapshotPackageArtifact.robot
index 0b58125d004592184ec6b20a9728d2564bc5e866..0aeb295ccf889e0f7cd7dabecb8fbeb8feac8d30 100644
--- a/SOL005/VNFSnapshotPackageManagement-API/IndividualVNFSnapshotPackageArtifact.robot
+++ b/SOL005/VNFSnapshotPackageManagement-API/IndividualVNFSnapshotPackageArtifact.robot
@@ -7,7 +7,7 @@ POST Individual VNF Snapshot Package Artifact - Method not implemented
... Test title: POST Individual VNF Snapshot Package Artifact - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 11.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -19,7 +19,7 @@ GET Individual VNF Snapshot Package Artifact - Complete File
... Test title: GET Information about an individual VNF Snapshot Package - Complete File
... Test objective: The objective is to fetch the whole content of a VNF snapshot package using GET method.
... Pre-conditions: none
- ... Reference: Clause 11.4.10.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.10.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -32,7 +32,7 @@ GET Individual VNF Snapshot Package Artifact - Partial Content
... Test title: GET Individual VNF Snapshot Package Artifact - Partial Content
... Test objective: The objective is to fetch partial content of a VNF snapshot package by sending a range request using GET method.
... Pre-conditions: none
- ... Reference: Clause 11.4.10.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.10.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: NFVO supports range requests
... Post-Conditions: none
@@ -47,7 +47,7 @@ GET Individual VNF Snapshot Package Artifact - Range Request Not Supported
... Test title: GET Information about an individual VNF Snapshot Package - Range Request Not Supported
... Test objective: The objective is to test that the whole content of a VNF snapshot package is delivered even with a range request when NFVO does not support range requests.
... Pre-conditions: none
- ... Reference: Clause 11.4.10.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.10.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: NFVO does not support range requests
... Post-Conditions: none
@@ -60,7 +60,7 @@ GET Individual VNF Snapshot Package Artifact - Range Not Satisfiable
... Test title: GET Information about an individual VNF Snapshot Package - Range Not Satisfiable
... Test objective: The objective is to test that an error is returned when the byte range passed in the "Range" header does not match any available byte range in the VNF snapshot package file.
... Pre-conditions: none
- ... Reference: Clause 11.4.10.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.10.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: NFVO supports range requests
... Post-Conditions: none
@@ -72,7 +72,7 @@ GET Individual VNF Snapshot Package Artifact - Conflict
... Test title: GET Information about an individual VNF Snapshot Package - Conflict
... Test objective: The objective is to test that an error is returned when the "state" of the VNF snapshot package has a value different from "AVAILABLE".
... Pre-conditions: none
- ... Reference: Clause 11.4.10.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.10.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The "state" of the VNF snapshot package has a value different from "AVAILABLE".
... Post-Conditions: none
@@ -85,7 +85,7 @@ GET Individual VNF Snapshot Package Artifact - External Artifact
... Test title: GET Information about an individual VNF Snapshot Package - External Artifact
... Test objective: The objective is to test that correct response code is returned the referred "Individual VNF Snapshot package artifact" is external to the main VNF snapshot package file created from a build process.
... Pre-conditions: none
- ... Reference: Clause 11.4.10.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.10.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The "Individual VNF Snapshot package artifact" is external to the main VNF snapshot package file created from a build process.
... Post-Conditions: none
@@ -98,7 +98,7 @@ PUT Individual VNF Snapshot Package Artifact - Method not implemented
... Test title: PUT Individual VNF Snapshot Package Artifact - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 11.4.10.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.10.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: VNF Snapshot Package not modified
@@ -110,7 +110,7 @@ PATCH Individual VNF Snapshot Package Artifact - Method Not implemented
... Test title: PATCH Individual VNF Snapshot Package Artifact
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 11.4.10.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.10.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -122,7 +122,7 @@ DELETE Individual VNF Snapshot Package Artifact - Method Not implemented
... Test title: DELETE Individual VNF Snapshot Package Artifact - Method Not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 11.4.10.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.10.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/VNFSnapshotPackageManagement-API/UploadVNFSnapshotPackageFromUriTask.robot b/SOL005/VNFSnapshotPackageManagement-API/UploadVNFSnapshotPackageFromUriTask.robot
index d9f9f145b177f99db31576cf4cd8ee4598270072..ee2ec096de0c781f60e1ce9a08e60925221aab92 100644
--- a/SOL005/VNFSnapshotPackageManagement-API/UploadVNFSnapshotPackageFromUriTask.robot
+++ b/SOL005/VNFSnapshotPackageManagement-API/UploadVNFSnapshotPackageFromUriTask.robot
@@ -7,7 +7,7 @@ POST Upload VNF Snapshot Package Content from URI
... Test title: POST Upload VNF Snapshot Package Content from URI
... Test objective: The objective is to test that POST method provides the information for the NFVO to get the content of a VNF snapshot package.
... Pre-conditions: none
- ... Reference: Clause 11.4.5.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.5.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -19,7 +19,7 @@ POST Upload VNF Snapshot Package Content from URI - Conflict
... Test title: POST Upload VNF Snapshot Package Content from URI - Conflict
... Test objective: The objective is to test that a correct error code is returned when the POST method tries to intiate upload VNF Snapshot Package from URI task and the state of the VNF snapshot package resource is other than "CREATED" or "ERROR".
... Pre-conditions: none
- ... Reference: Clause 11.4.5.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.5.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The state of the VNF snapshot package resource is other than "CREATED" or "ERROR".
... Post-Conditions: none
@@ -32,7 +32,7 @@ GET Upload VNF Snapshot Package Content from URI - Method Not implemented
... Test title: GET Upload VNF Snapshot Package Content from URI - Method Not implemented
... Test objective: The objective is to test that GET method is not implemented
... Pre-conditions: none
- ... Reference: Clause 11.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -44,7 +44,7 @@ PUT Upload VNF Snapshot Package Content from URI - Method Not implemented
... Test title: PUT Upload VNF Snapshot Package Content from URI - Method Not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 11.4.5.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.5.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -56,7 +56,7 @@ PATCH Upload VNF Snapshot Package Content from URI - Method Not implemented
... Test title: PATCH Upload VNF Snapshot Package Content from URI - Method Not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 11.4.5.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.5.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -68,7 +68,7 @@ DELETE Upload VNF Snapshot Package Content from URI - Method Not implemented
... Test title: DELETE Upload VNF Snapshot Package Content from URI - Method Not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 11.4.5.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.5.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/VNFSnapshotPackageManagement-API/VNFSnapshotPackageContent.robot b/SOL005/VNFSnapshotPackageManagement-API/VNFSnapshotPackageContent.robot
index 8f9a42c9d54cacdb80ecb0eedc72e0c1f8f84d75..5198074c868f31887a086f2f390f923acc862c3c 100644
--- a/SOL005/VNFSnapshotPackageManagement-API/VNFSnapshotPackageContent.robot
+++ b/SOL005/VNFSnapshotPackageManagement-API/VNFSnapshotPackageContent.robot
@@ -7,7 +7,7 @@ POST VNF Snapshot Package Content - Method not implemented
... Test title: POST VNF Snapshot Package Content - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 11.4.4.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.4.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -19,7 +19,7 @@ GET VNF Snapshot Package Content - Complete File
... Test title: GET Information about an individual VNF Snapshot Package - Complete File
... Test objective: The objective is to fetch the whole content of a VNF snapshot package using GET method.
... Pre-conditions: none
- ... Reference: Clause 11.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -32,7 +32,7 @@ GET VNF Snapshot Package Content - Partial Content
... Test title: GET VNF Snapshot Package Content - Partial Content
... Test objective: The objective is to fetch partial content of a VNF snapshot package by sending a range request using GET method.
... Pre-conditions: none
- ... Reference: Clause 11.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: NFVO supports range requests
... Post-Conditions: none
@@ -47,7 +47,7 @@ GET VNF Snapshot Package Content - Range Request Not Supported
... Test title: GET Information about an individual VNF Snapshot Package - Range Request Not Supported
... Test objective: The objective is to test that the whole content of a VNF snapshot package is delivered even with a range request when NFVO does not support range requests.
... Pre-conditions: none
- ... Reference: Clause 11.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: NFVO does not support range requests
... Post-Conditions: none
@@ -60,7 +60,7 @@ GET VNF Snapshot Package Content - Range Not Satisfiable
... Test title: GET Information about an individual VNF Snapshot Package - Range Not Satisfiable
... Test objective: The objective is to test that an error is returned when the byte range passed in the "Range" header does not match any available byte range in the VNF snapshot package file.
... Pre-conditions: none
- ... Reference: Clause 11.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: NFVO supports range requests
... Post-Conditions: none
@@ -72,7 +72,7 @@ GET VNF Snapshot Package Content - Conflict
... Test title: GET Information about an individual VNF Snapshot Package - Conflict
... Test objective: The objective is to test that an error is returned when the "state" of the VNF snapshot package has a value different from "AVAILABLE".
... Pre-conditions: none
- ... Reference: Clause 11.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The "state" of the VNF snapshot package has a value different from "AVAILABLE".
... Post-Conditions: none
@@ -85,7 +85,7 @@ PUT VNF Snapshot Package Content
... Test title: PUT VNF Snapshot Package Content
... Test objective: The objective is to test that PUT method uploads the content of VNF Snapshot Package.
... Pre-conditions: none
- ... Reference: Clause 11.4.4.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.4.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -97,7 +97,7 @@ PUT VNF Snapshot Package Content - Conflict
... Test title: PUT VNF Snapshot Package Content
... Test objective: The objective is to test that PUT method cannot upload the content of VNF Package when the state of the VNF snapshot package resource is other than "CREATED" or "ERROR"..
... Pre-conditions: none
- ... Reference: Clause 11.4.4.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.4.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: the state of the VNF snapshot package resource is other than "CREATED" or "ERROR".
... Post-Conditions: none
@@ -110,7 +110,7 @@ PATCH VNF Snapshot Package Content - Method Not implemented
... Test title: PATCH VNF Snapshot Package Content
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 11.4.4.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.4.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -122,7 +122,7 @@ DELETE VNF Snapshot Package Content - Method Not implemented
... Test title: DELETE VNF Snapshot Package Content - Method Not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 11.4.4.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.4.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/VNFSnapshotPackageManagement-API/VNFSnapshotPackages.robot b/SOL005/VNFSnapshotPackageManagement-API/VNFSnapshotPackages.robot
index 50323c3701b9dd8f65bdbef869525b6dd25f4a0f..16cc89da668ff3951419ccc8e263c54bb10238a7 100644
--- a/SOL005/VNFSnapshotPackageManagement-API/VNFSnapshotPackages.robot
+++ b/SOL005/VNFSnapshotPackageManagement-API/VNFSnapshotPackages.robot
@@ -7,7 +7,7 @@ POST Create a VNF Snapshot Package
... Test title: POST Create a VNF Snapshot Package
... Test objective: The objective is to test that POST method creates a VNF Snapshot Package
... Pre-conditions: none
- ... Reference: Clause 11.4.2.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.2.3.1 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -20,7 +20,7 @@ GET information about multiple VNF Snapshot Packages
... Test title: GET information about multiple VNF Snapshot Packages
... Test objective: The objective is to get information about multiples VNF Snapshot Packages
... Pre-conditions: none
- ... Reference: Clause 11.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -33,7 +33,7 @@ GET information about multiple VNF Snapshot Packages Bad Request Invalid attribu
... Test title: GET information about multiple VNF Snapshot Packages Bad Request Invalid attribute-based filtering parameters
... Test objective: The objective is to get information about multiples VNF Snapshot Packages with Invalid attribute-based filtering parameters
... Pre-conditions: none
- ... Reference: Clause 11.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -46,7 +46,7 @@ GET information about multiple VNF Snapshot Packages Bad Request Invalid attribu
... Test title: GET information about multiple VNF Snapshot Packages Bad Request Invalid attribute selector
... Test objective: The objective is to get information about multiples VNF Snapshot Packages with Invalid attribute-based filtering parameters
... Pre-conditions: none
- ... Reference: Clause 11.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -59,7 +59,7 @@ GET information about multiple VNF Snapshot Packages with "all_fields" attribute
... Test title: GET information about multiple VNF Snapshot Packages with "all_fields" attribute selector
... Test objective: The objective is to query information about multiple VNF Snapshot Packages
... Pre-conditions: none
- ... Reference: Clause 11.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -72,7 +72,7 @@ GET information about multiple VNF Snapshot Packages with "exclude_default" attr
... Test title: GET information about multiple VNF Snapshot Packages with "exclude_default" attribute selector
... Test objective: The objective is to query information about multiple VNF Snapshot Packages
... Pre-conditions: none
- ... Reference: Clause 11.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -85,7 +85,7 @@ GET information about multiple VNF Snapshot Packages with "fields" attribute sel
... Test title: GET information about multiple VNF Snapshot Packages with "fields" attribute selector
... Test objective: The objective is to query information about multiple VNF Snapshot Packages
... Pre-conditions: none
- ... Reference: Clause 11.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -98,7 +98,7 @@ GET information about multiple VNF Snapshot Packages with "exclude_default" and
... Test title: GET information about multiple VNF Snapshot Packages with "exclude_default" and "fields" attribute selector
... Test objective: The objective is to query information about multiple VNF Snapshot Packages
... Pre-conditions: none
- ... Reference: Clause 11.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -111,7 +111,7 @@ GET information about multiple VNF Snapshot Packages with "exclude_fields" attri
... Test title: GET information about multiple VNF Snapshot Packages with "exclude_fields" attribute selector
... Test objective: The objective is to query information about multiple VNF Snapshot Packages
... Pre-conditions: none
- ... Reference: Clause 11.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -124,7 +124,7 @@ GET VNF Snapshot Packages - Bad Request Response too Big
... Test title: GET VNF Snapshot Packages - Bad Request Response too Big
... Test objective: The objective is test that the retrieval of existing VNF Snapshot Packages list fails because response is too big, and perform the JSON schema validation of the failed operation HTTP response.
... Pre-conditions: none
- ... Reference: Clause 11.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: NFVO does not support paged response.
... Post-Conditions: none
@@ -137,7 +137,7 @@ GET VNF Snapshot Packages as Paged Response
... Test title: GET VNF Snapshot Packages as Paged Response
... Test objective: The objective is to test that GET method retrieves the list of existing VNF Snapshot Packages as paged response.
... Pre-conditions: none
- ... Reference: Clause 11.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: NFVO supports paged response.
... Post-Conditions: none
@@ -150,7 +150,7 @@ PUT VNF Snapshot Packages - Method not implemented
... Test title: PUT VNF Snapshot Packages - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 11.4.2.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.2.3.3 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -162,7 +162,7 @@ PATCH VNF Snapshot Packages - Method not implemented
... Test title: PATCH VNF Snapshot Packages - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 11.4.2.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.2.3.4 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -174,7 +174,7 @@ DELETE VNF Snapshot Packages - Method not implemented
... Test title: DELETE VNF Snapshot Packages - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 11.4.2.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.2.3.5 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: VNF snapshot package is not deleted
@@ -186,7 +186,7 @@ GET information about multiple VNF Snapshot Packages with Filter
... Test title: GET information about multiple VNF Snapshot Packages with Filter
... Test objective: The objective is to get information about multiples VNF Snapshot Packages using filter
... Pre-conditions: none
- ... Reference: Clause 11.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
+ ... Reference: Clause 11.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/VNFSnapshotPackageManagement-API/schemas/VnfSnapshotPkgExtArtifactsAccessConfig.schema.json b/SOL005/VNFSnapshotPackageManagement-API/schemas/VnfSnapshotPkgExtArtifactsAccessConfig.schema.json
index f6252a50874252521e3d793e45ea3b0f991a77eb..7e1e64b2bcfa63bad1a19416056be1b856a900a9 100644
--- a/SOL005/VNFSnapshotPackageManagement-API/schemas/VnfSnapshotPkgExtArtifactsAccessConfig.schema.json
+++ b/SOL005/VNFSnapshotPackageManagement-API/schemas/VnfSnapshotPkgExtArtifactsAccessConfig.schema.json
@@ -1,68 +1,59 @@
{
- "description": "This type represents the access configuration information for downloading external VNF snapshot package artifacts. The NFVO can obtain the external VNF snapshot package artifact file through the information provided in this structure, together with information provided in the manifest. The data structure shall comply with the provisions defined in Table 11.5.2.9-1. If the data structure is part of a response body, security-sensitive attributes shall be excluded as specified in Table 11.5.2.9-1.\n",
- "type": "object",
- "properties": {
- "artifact": {
- "description": "Access configuration information for an external artifact.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": [
- "artifactUri"
- ],
- "properties": {
- "artifactUri": {
- "description": "String formatted according to IETF RFC 3986.\n",
- "type": "string",
- "format": "uri"
- },
- "overrideUri": {
- "description": "String formatted according to IETF RFC 3986.\n",
- "type": "string",
- "format": "uri"
- },
- "authType": {
- "description": "Defines the type of authentication / authorization for downloading the VNF package.\nPermitted values: - BASIC: Only the \"username\" and \"password\" attributes shall be present. - OAUTH2_CLIENT_CREDENTIALS: Only the \"paramsOauth2ClientCredentials\" attribute shall be present.\nThis attribute shall not be present if no credentials are provided for the artifact.\n",
- "type": "string",
- "enum": [
- "BASIC",
- "OAUTH2_CLIENT_CREDENTIALS"
- ]
- },
- "username": {
- "description": "Username to be used for authentication.\n",
- "type": "string"
- },
- "password": {
- "description": "Password to be used for authentication. Shall not be present in response bodies.\n",
- "type": "string"
- },
- "paramsOauth2ClientCredentials": {
- "description": "Parameters for authentication/authorization using OAUTH2_CLIENT_CREDENTIALS.\n",
- "type": "object",
- "required": [
- "clientId",
- "clientPassword",
- "tokenEndpoint"
- ],
- "properties": {
- "clientId": {
- "description": "Client identifier to be used in the access token request of the OAuth 2.0 client credentials grant type.\n",
- "type": "string"
- },
- "clientPassword": {
- "description": "Client password to be used in the access token request of the OAuth 2.0 client credentials grant type. Shall not be present in response bodies.\n",
- "type": "string"
- },
- "tokenEndpoint": {
- "description": "String formatted according to IETF RFC 3986.\n",
- "type": "string",
- "format": "uri"
- }
- }
- }
- }
- }
- }
- }
+ "description": "This type represents the access configuration information for downloading external VNF snapshot package artifacts. The NFVO can obtain the external VNF snapshot package artifact file through the information provided in this structure, together with information provided in the manifest. The data structure shall comply with the provisions defined in Table 11.5.2.9-1. If the data structure is part of a response body, security-sensitive attributes shall be excluded as specified in Table 11.5.2.9-1.\n",
+ "properties": {
+ "artifact": {
+ "description": "Access configuration information for an external artifact.\n",
+ "items": {
+ "properties": {
+ "artifactUri": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "format": "uri",
+ "type": "string"
+ },
+ "authType": {
+ "description": "Defines the type of authentication / authorization for downloading the VNF package.\nPermitted values: - OAUTH2_CLIENT_CREDENTIALS: Only the \"paramsOauth2ClientCredentials\" attribute shall be present.\nThis attribute shall not be present if no credentials are provided for the artifact\n",
+ "enum": [
+ "OAUTH2_CLIENT_CREDENTIALS"
+ ],
+ "type": "string"
+ },
+ "overrideUri": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "format": "uri",
+ "type": "string"
+ },
+ "paramsOauth2ClientCredentials": {
+ "description": "Parameters for authentication/authorization using OAUTH2_CLIENT_CREDENTIALS.\n",
+ "properties": {
+ "clientId": {
+ "description": "Client identifier to be used in the access token request of the OAuth 2.0 client credentials grant type.\n",
+ "type": "string"
+ },
+ "clientPassword": {
+ "description": "Client password to be used in the access token request of the OAuth 2.0 client credentials grant type. Shall not be present in response bodies.\n",
+ "type": "string"
+ },
+ "tokenEndpoint": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "format": "uri",
+ "type": "string"
+ }
+ },
+ "required": [
+ "clientId",
+ "clientPassword",
+ "tokenEndpoint"
+ ],
+ "type": "object"
+ }
+ },
+ "required": [
+ "artifactUri"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "type": "object"
}
\ No newline at end of file
diff --git a/SOL009/NFVMANOFaultManagement-API/Alarms.robot b/SOL009/NFVMANOFaultManagement-API/Alarms.robot
index 2943ff2483474aa58c17289564b1d74cb3514c59..3d6d861e732255afbbad0569dfdab5cca36f3047 100644
--- a/SOL009/NFVMANOFaultManagement-API/Alarms.robot
+++ b/SOL009/NFVMANOFaultManagement-API/Alarms.robot
@@ -7,7 +7,7 @@ POST Alarms - Method not implemented
... Test title: POST Alarms - Method not implemented
... Test objective: The objective is to test that Post method is not allowed to create fault management alarms on NFV-MANO
... Pre-conditions: none
- ... Reference: clause 7.5.3.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 7.5.3.3.1 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -19,7 +19,7 @@ Get information about multiple alarms
... Test title: Get information about multiple alarms
... Test objective: The objective is to retrieve information about the alarm list and perform a JSON schema of the returned alarms data structure
... Pre-conditions: none
- ... Reference: clause 7.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 7.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -32,7 +32,7 @@ Get information about multiple alarms with filter
... Test title: Get information about multiple alarms with filter
... Test objective: The objective is to retrieve information about the alarm list and perform a JSON schema validation of the returned alarms data structure, and verify that the retrieved information matches the issued attribute-based filters
... Pre-conditions: none
- ... Reference: clause 7.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 7.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -45,7 +45,7 @@ Get information about multiple alarms with invalid attribute-based filtering par
... Test title: Get information about multiple alarms with invalid attribute-based filtering parameters
... Test objective: The objective is to try to retrieve information about the alarm list with invalid filters and perform a JSON schema validation of the returned problem details data structure
... Pre-conditions: none
- ... Reference: clause 7.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 7.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -58,7 +58,7 @@ Get information about multiple alarms as a Paged Response
... Test title: Get information about multiple alarms as a Paged Response
... Test objective: The objective is to retrieve information about the alarm list as a Paged Response.
... Pre-conditions: none
- ... Reference: Clause 7.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: Clause 7.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -71,7 +71,7 @@ Get information about multiple alarms - Bad Request Response too Big
... Test title: Get information about multiple alarms - Bad Request Response too Big
... Test objective: The objective is to try to retrieve information about the alarm list because response is too big and perform a JSON schema validation of the returned problem details data structure
... Pre-conditions: none
- ... Reference: Clause 7.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: Clause 7.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -84,7 +84,7 @@ GET information about alarms with attribute-based filter "id"
... Test title: GET information about alarms with attribute-based filter "id"
... Test objective: The objective is to retrieve information about the alarm list with alarm filter "id"
... Pre-conditions: none
- ... Reference: Clause 7.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: Clause 7.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -98,7 +98,7 @@ GET information about multiple alarms with attribute-based filter "managedObject
... Test title: GET information about multiple alarms with attribute-based filter "managedObjectId"
... Test objective: The objective is to retrieve information about the alarm list with attribute filter "managedObjectId"
... Pre-conditions: none
- ... Reference: Clause 7.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: Clause 7.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -112,7 +112,7 @@ GET information about multiple alarms with attribute-based filter "eventType"
... Test title: GET information about multiple alarms with attribute-based filter "eventType"
... Test objective: The objective is to retrieve information about the alarm list with attribute filter "eventType"
... Pre-conditions: none
- ... Reference: Clause 7.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: Clause 7.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -126,7 +126,7 @@ GET information about multiple alarms with attribute-based filter "perceivedSeve
... Test title: GET information about multiple alarms with attribute-based filter "perceivedSeverity"
... Test objective: The objective is to retrieve information about the alarm list with attribute filter "perceivedSeverity"
... Pre-conditions: none
- ... Reference: Clause 7.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: Clause 7.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -140,7 +140,7 @@ GET information about multiple alarms with attribute-based filter "probableCause
... Test title: GET information about multiple alarms with attribute-based filter "probableCause"
... Test objective: The objective is to retrieve information about the alarm list with attribute filter "probableCause"
... Pre-conditions: none
- ... Reference: Clause 7.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: Clause 7.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -154,7 +154,7 @@ Get information about multiple alarms with malformed authorization token
... Test title: Get information about multiple alarms with malformed authorization token
... Test objective: The objective is to test that the retrieval of information about the alarm list fails when using malformed authorization token
... Pre-conditions: none
- ... Reference: clause 7.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 7.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: The NFV-MANO entity requires the usage of access tokens for authorizing the API requests.
... Post-Conditions: none
@@ -166,7 +166,7 @@ Get information about multiple alarms without authorization token
... Test title: Get information about multiple alarms without authorization token
... Test objective: The objective is to test that the retrieval of information about the alarm list fails when omitting the authorization token
... Pre-conditions: none
- ... Reference: clause 7.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 7.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: The NFV-MANO entity requires the usage of access tokens for authorizing the API requests.
... Post-Conditions: none
@@ -178,7 +178,7 @@ GET information about multiple alarms with expired or revoked authorization toke
... Test title: GET information about multiple alarms with expired or revoked authorization token
... Test objective: The objective is to test that the retrieval of information about the alarm list fails when using expired or revoked authorization token
... Pre-conditions: One or more Network Service Descriptors are onboarded in the NFVO
- ... Reference: clause 7.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 7.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: The NFV-MANO entity requires the usage of access tokens for authorizing the API requests.
... Post-Conditions: none
@@ -190,7 +190,7 @@ PUT Alarms - Method not implemented
... Test title: PUT Alarms - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to modify fault management alarms on NFV-MANO.
... Pre-conditions: none
- ... Reference: clause 7.5.3.3.3 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 7.5.3.3.3 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -202,7 +202,7 @@ PATCH Alarms - Method not implemented
... Test title: PATCH Alarms - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to modify fault management alarms on NFV-MANO.
... Pre-conditions: none
- ... Reference: clause 7.5.3.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 7.5.3.3.4 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -214,7 +214,7 @@ DELETE Alarms - Method not implemented
... Test title: POST Alarms - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed for fault management alarms on NFV-MANO
... Pre-conditions: none
- ... Reference: clause 7.5.3.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 7.5.3.3.5 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL009/NFVMANOFaultManagement-API/ApiVersion.robot b/SOL009/NFVMANOFaultManagement-API/ApiVersion.robot
index ad92531537f1559036a25897cf9532e5351a4904..0d18aead99dfc61ac1b950b2b558e37c699ff478 100644
--- a/SOL009/NFVMANOFaultManagement-API/ApiVersion.robot
+++ b/SOL009/NFVMANOFaultManagement-API/ApiVersion.robot
@@ -7,7 +7,7 @@ POST API Version - Method not implemented
... Test title: POST API version - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -19,7 +19,7 @@ GET API Version
... Test title: GET API Version
... Test objective: The objective is to test that GET method successfully return ApiVersionInformation
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -32,7 +32,7 @@ PUT API Version - Method not implemented
... Test title: PUT API Version - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -44,7 +44,7 @@ PATCH API Version - Method not implemented
... Test title: PATCH API Version - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -56,7 +56,7 @@ DELETE API Version - Method not implemented
... Test title: DELETE API Version - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -68,7 +68,7 @@ POST API Version with apiMajorVerion - Method not implemented
... Test title: POST API version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -80,7 +80,7 @@ GET API Version with apiMajorVerion
... Test title: GET API Version with apiMajorVerion
... Test objective: The objective is to test that GET method successfully return ApiVersionInformation
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -93,7 +93,7 @@ PUT API Version with apiMajorVerion - Method not implemented
... Test title: PUT API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -105,7 +105,7 @@ PATCH API Version with apiMajorVerion - Method not implemented
... Test title: PATCH API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -117,7 +117,7 @@ DELETE API Version with apiMajorVerion - Method not implemented
... Test title: DELETE API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL009/NFVMANOFaultManagement-API/IndividualAlarm.robot b/SOL009/NFVMANOFaultManagement-API/IndividualAlarm.robot
index 9a09ca222f25efe64a66569a8d3928e7eecad121..9b1d6e2b1f408dd7cae49444660f235df07d8cb1 100644
--- a/SOL009/NFVMANOFaultManagement-API/IndividualAlarm.robot
+++ b/SOL009/NFVMANOFaultManagement-API/IndividualAlarm.robot
@@ -7,7 +7,7 @@ POST Individual Alarm - Method not implemented
... Test title: POST Individual Alarm - Method not implemented
... Test objective: The objective is to test that Post method is not allowed to create fault management individual alarm on NFV-MANO
... Pre-conditions: none
- ... Reference: clause 7.5.4.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 7.5.4.3.1 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -19,7 +19,7 @@ Get information about an fault management individual alarm
... Test title: Get information about an fault management individual alarm
... Test objective: The objective is to retrieve information about an individual alarm and perform a JSON schema and content validation of the returned alarm data structure
... Pre-conditions: The related alarm exists
- ... Reference: clause 7.5.4.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 7.5.4.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -32,7 +32,7 @@ Get information about an fault management individual alarm - Not Found
... Test title: Get information about an fault management individual alarm
... Test objective: The objective is to test the retrieval of information about an individual alarm fails when the resource is not present.
... Pre-conditions: none
- ... Reference: clause 7.5.4.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 7.5.4.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -45,7 +45,7 @@ PUT Individual Alarm - Method not implemented
... Test title: PUT Individual Alarm - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to for fault management individual alarm on NFV-MANO
... Pre-conditions: none
- ... Reference: clause 7.5.4.3.3 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 7.5.4.3.3 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -57,7 +57,7 @@ PATCH Fault Management Individual Alarm
... Test title: PATCH Fault Management Individual Alarm
... Test objective: The objective is to Modify an individual alarm resource, and perform a JSON schema validation of the returned alarm data structure.
... Pre-conditions: The related alarm exists
- ... Reference: clause 7.5.4.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 7.5.4.3.4 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: Alarm is modified.
@@ -70,7 +70,7 @@ Modify an individual alarm resource - Precondition failed
... Test title: Modify an individual alarm resource - Precondition failed
... Test objective: The objective is to test that an individual alarm resource cannot be modified if the alarm is already in the state that is requested to be set, and perform a JSON schema validation of the returned data structure.
... Pre-conditions: The related alarm exists
- ... Reference: clause 7.5.4.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 7.5.4.3.4 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: Alarm is not modified.
@@ -84,7 +84,7 @@ Modify an individual alarm resource - Conflict
... Test title: Modify an individual alarm resource - Conflict
... Test objective: The objective is to test that an individual alarm resource cannot be modified if the resource was modified by another entity , and perform a JSON schema validation of the returned data structure.
... Pre-conditions: The related alarm exists
- ... Reference: clause 7.5.4.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 7.5.4.3.4 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: Alarm is not modified.
@@ -98,7 +98,7 @@ DELETE Individual Alarm - Method not implemented
... Test title: DELETE Individual Alarm - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to delete fault management individual alarm on NFV-MANO.
... Pre-conditions: none
- ... Reference: clause 7.5.4.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 7.5.4.3.5 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL009/NFVMANOFaultManagement-API/IndividualSubscription.robot b/SOL009/NFVMANOFaultManagement-API/IndividualSubscription.robot
index 7fd7c312a80a19cfe345893433e239366c27e36f..36bbf07f9c9d66b3a38ad73f2c8fc84a88bc669b 100644
--- a/SOL009/NFVMANOFaultManagement-API/IndividualSubscription.robot
+++ b/SOL009/NFVMANOFaultManagement-API/IndividualSubscription.robot
@@ -7,7 +7,7 @@ Post Individual Subscription - Method not implemented
... Test title: Post Individual Subscription - Method not implemented
... Test objective: The objective is to test that POST method is not allowed for fault management subscription on NFV-MANO
... Pre-conditions: none
- ... Reference: clause 7.5.6.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 7.5.6.3.1 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -19,7 +19,7 @@ Get Information about an individual subscription
... Test title: Get Information about an individual subscription
... Test objective: The objective is to read an individual subscription from NFV-MANO alarms subscribed by the client and perform a JSON schema and content validation of the returned fault management individual subscription data structure
... Pre-conditions: The subscription with the given id exists
- ... Reference: clause 7.5.6.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 7.5.6.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -32,7 +32,7 @@ Get Information about an individual subscription - Not Found
... Test title: Get Information about an individual subscription - Not Found
... Test objective: The objective is to test the retrieval of individual subscription from NFV-MANO alarms fails when the resource is not present.
... Pre-conditions: none
- ... Reference: clause 7.5.6.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 7.5.6.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -44,7 +44,7 @@ PUT an individual subscription - Method not implemented
... Test title:PUT an individual subscription - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed for fault management individual subscription on VNF
... Pre-conditions: none
- ... Reference: clause 7.5.6.3.3 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 7.5.6.3.3 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -56,7 +56,7 @@ PATCH an individual subscription - Method not implemented
... Test title:PATCH an individual subscription - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed for fault management individual subscription on VNF
... Pre-conditions: none
- ... Reference: clause 7.5.6.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 7.5.6.3.4 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -68,7 +68,7 @@ DELETE an individual subscription
... Test title:DELETE an individual subscription
... Test objective: The objective is to test that DELETE method removes individual subscription on VNF
... Pre-conditions: The Subsbcription already exists
- ... Reference: clause 7.5.6.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 7.5.6.3.5 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: subscription is deleted
diff --git a/SOL009/NFVMANOFaultManagement-API/NotificationEndpoint.robot b/SOL009/NFVMANOFaultManagement-API/NotificationEndpoint.robot
index 808192e9d94d92a8e7f46c6dc15a3c3fa0750856..0f54308886d2679aa1b64c025edd48cc5ba31158 100644
--- a/SOL009/NFVMANOFaultManagement-API/NotificationEndpoint.robot
+++ b/SOL009/NFVMANOFaultManagement-API/NotificationEndpoint.robot
@@ -8,7 +8,7 @@ Alarm Notification
... Test title: Alarm Notification
... Test objective: The objective is to test that Alarm Notification is delivered with success to the notification consumer.
... Pre-conditions: A subscription for alarm notification is available in the NFV-MANO.
- ... Reference: clause 7.5.7.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 7.5.7.3.1 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
@@ -20,7 +20,7 @@ Alarm Cleared Notification
... Test title: Alarm Cleared Notification
... Test objective: The objective is to test that Alarm Cleared Notification is delivered with success to the notification consumer.
... Pre-conditions: A subscription for alarm cleared notification is available in the NFV-MANO.
- ... Reference: clause 7.5.7.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 7.5.7.3.1 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
@@ -32,7 +32,7 @@ Alarm List Rebuilt Notification
... Test title: Alarm List Rebuilt Notification
... Test objective: The objective is to test that Alarm List Rebuilt Notification is delivered with success to the notification consumer.
... Pre-conditions: A subscription for alarm list rebuilt notification is available in the NFV-MANO.
- ... Reference: clause 7.5.7.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 7.5.7.3.1 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
diff --git a/SOL009/NFVMANOFaultManagement-API/Notifications.robot b/SOL009/NFVMANOFaultManagement-API/Notifications.robot
index b482d9983ce3ba29af4f66b4f45b64243c9cb04d..61b3e367c4280c566df66319e372171b2bb5a31f 100644
--- a/SOL009/NFVMANOFaultManagement-API/Notifications.robot
+++ b/SOL009/NFVMANOFaultManagement-API/Notifications.robot
@@ -10,7 +10,7 @@ NFV-MANO Fault Alarm Notification
... Test title: NFV-MANO Fault Alarm Notification
... Test objective: The objective is to test the dispatch of NFV-MANO Fault Alarm Notification when a resource within an NFV-MANO instance fails, and perform a JSON schema and content validation of the delivered notification. The action that triggers the notification under test is an explicit test step, but it is not performed by the test system.
... Pre-conditions: A NFV-MANO instance is instantiated, and a subscription for fault alarm notifications is available.
- ... Reference: clause 7.5.7.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 7.5.7.3.1 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -23,7 +23,7 @@ NFV-MANO Fault Alarm Cleared Notification
... Test title: NFV-MANO Fault Alarm Cleared Notification
... Test objective: The objective is to test the dispatch of NFV-MANO Fault Alarm Cleared Notification when a faulty resource within an NFV-MANO instance is cleared, and perform a JSON schema and content validation of the delivered notification. The action that triggers the notification under test is an explicit test step, but it is not performed by the test system.
... Pre-conditions: A NFV-MANO instance is instantiated, a virtualised resource is in faulty state, and a subscription for fault alarm cleared notifications is available.
- ... Reference: clause 7.5.7.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 7.5.7.3.1 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -36,7 +36,7 @@ NFV-MANO Fault Alarm List Rebuilt Notification
... Test title: NFV-MANO Fault Alarm List Rebuilt Notification
... Test objective: The objective is to test the dispatch of NFV-MANO Fault Alarm List Rebuilt Notification when the NFV-MANO decides to rebuild the list of its NFV-MANO alarms, e.g. due to a corruption in the alarm storage, and perform a JSON schema and content validation of the delivered notification. The action that triggers the notification under test is an explicit test step, but it is not performed by the test system.
... Pre-conditions: A NFV-MANO instance is instantiated, one or more virtualised resource are in faulty state, and a subscription for fault alarm list rebuilt notifications is available.
- ... Reference: clause 7.5.7.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 7.5.7.3.1 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL009/NFVMANOFaultManagement-API/Subscriptions.robot b/SOL009/NFVMANOFaultManagement-API/Subscriptions.robot
index b46e5fcab1141b38570c841b0650c880e3da545c..7b747f50a15f38add375455705ef88a4cdda1fbc 100644
--- a/SOL009/NFVMANOFaultManagement-API/Subscriptions.robot
+++ b/SOL009/NFVMANOFaultManagement-API/Subscriptions.robot
@@ -7,7 +7,7 @@ POST Create a new Fault Management alarm subscription
... Test title: POST Create a new fault management alarm subscription
... Test objective: The objective is to create a new fault management alarm subscription and perform a JSON schema validation of the returned fault management alarms subscription data structure
... Pre-conditions: No subscription with the same filter and callbackUri exists
- ... Reference: clause 7.5.5.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 7.5.5.3.1 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: subscription is created
@@ -22,7 +22,7 @@ POST Create a new alarm subscription - DUPLICATION
... Test title: POST Create a new alarm subscription - DUPLICATION
... Test objective: The objective is to create a new subscription with the NFV-MANO allowing duplication and perform a JSON schema validation of the returned fault management alarms subscription data structure.
... Pre-conditions: subscription with the same filter and callbackUri exists
- ... Reference: clause 7.5.5.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 7.5.5.3.1 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: the NFV-MANO allows creating a subscription resource if another subscription resource with the same filter and callbackUri already exists
... Post-Conditions: duplicated subscription is created
@@ -37,7 +37,7 @@ POST Create a new alarm subscription - NO DUPLICATION
... Test title: POST Create a new alarm subscription - NO DUPLICATION
... Test objective: The objective is to create a new subscription with the NFV-MANO not allowing duplication and perform a JSON schema validation of the returned fault management alarms subscription data structure.
... Pre-conditions: subscription with the same filter and callbackUri exists
- ... Reference: clause 7.5.5.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 7.5.5.3.1 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: the NFV-MANO does not allow to create a duplicate subscription resource
... Post-Conditions: duplicated subscription is not created
@@ -52,7 +52,7 @@ Retrieve a list of alarm subscriptions
... Test title: Retrieve a list of alarm subscriptions
... Test objective: The objective is to retrieve the list of active subscriptions and perform a JSON schema validation of the returned fault management alarms subscription data structure.
... Pre-conditions: none
- ... Reference: clause 7.5.5.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 7.5.5.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: noe
@@ -65,7 +65,7 @@ Retrieve a list of alarm subscriptions with filter
... Test title: Retrieve a list of alarm subscriptions with filter
... Test objective: The objective is to retrieve the list of active subscriptions with filter and perform a JSON schema validation of the returned fault management alarms subscription data structure.
... Pre-conditions: none
- ... Reference: clause 7.5.5.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 7.5.5.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -78,7 +78,7 @@ Get information about multiple alarms as a Paged Response
... Test title: Get information about multiple alarms as a Paged Response
... Test objective: The objective is to retrieve information about active list subscriptions as a Paged Response
... Pre-conditions: none
- ... Reference: Clause 7.5.5.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: Clause 7.5.5.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -91,7 +91,7 @@ GET subscriptions - Bad Request Invalid attribute-based filtering parameters
... Test title: GET subscriptions - Bad Request Invalid attribute-based filtering parameters
... Test objective: The objective is to retrieve the list of active subscriptions with Invalid attribute-based filtering parameters and perform a JSON schema validation of the returned problem details data structure.
... Pre-conditions: none
- ... Reference: clause 7.5.5.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 7.5.5.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -104,7 +104,7 @@ Get information about multiple alarms - Bad Request Response too Big
... Test title: Get information about multiple alarms - Bad Request Response too Big
... Test objective: The objective is to try to retrieve information about active list subscription to check that response is too big and perform a JSON schema validation of the returned problem details data structure
... Pre-conditions: none
- ... Reference: Clause clause 7.5.5.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: Clause clause 7.5.5.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -117,7 +117,7 @@ GET Subscription with attribute-based filter "id"
... Test title: GET Subscription with attribute-based filter "id"
... Test objective: The objective is to retrieve the list of active subscriptions with filter "id"
... Pre-conditions: none
- ... Reference: Clause 7.5.5.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: Clause 7.5.5.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -131,7 +131,7 @@ Get subscriptions with filter "filter.notificationTypes"
... Test title: GET Subscription with attribute-based filter "filter.notificationTypes"
... Test objective: The objective is to retrieve the list of active subscriptions with filter "filter.notificationTypes"
... Pre-conditions: none
- ... Reference: Clause 7.5.5.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: Clause 7.5.5.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -145,7 +145,7 @@ Get subscriptions with filter "filter.perceivedSeverities"
... Test title: GET Subscription with attribute-based filter "filter.perceivedSeverities"
... Test objective: The objective is to retrieve the list of active subscriptions with filter "filter.perceivedSeverities"
... Pre-conditions: none
- ... Reference: Clause 7.5.5.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: Clause 7.5.5.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -159,7 +159,7 @@ Get subscriptions with filter "filter.eventTypes"
... Test title: GET Subscription with attribute-based filter "filter.eventTypes"
... Test objective: The objective is to retrieve the list of active subscriptions with filter "filter.eventTypes"
... Pre-conditions: none
- ... Reference: Clause 7.5.5.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: Clause 7.5.5.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -173,7 +173,7 @@ Get subscriptions with filter "filter.probableCauses"
... Test title: GET Subscription with attribute-based filter "filter.probableCauses"
... Test objective: The objective is to retrieve the list of active subscriptions with filter "filter.probableCauses"
... Pre-conditions: none
- ... Reference: Clause 7.5.5.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: Clause 7.5.5.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -187,7 +187,7 @@ PUT subscriptions - Method not implemented
... Test title:PUT subscriptions - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to for fault management subscriptions on VNF
... Pre-conditions: none
- ... RReference: clause 7.5.5.3.3 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... RReference: clause 7.5.5.3.3 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -199,7 +199,7 @@ PATCH subscriptions - Method not implemented
... Test title: PATCH subscriptions - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to for fault management subscriptions on VNF
... Pre-conditions: none
- ... Reference: clause 7.5.5.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 7.5.5.3.4 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -211,19 +211,19 @@ DELETE subscriptions - Method not implemented
... Test title: DELETE subscriptions - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to for fault management subscriptions on VNF
... Pre-conditions: none
- ... Reference: clause 7.5.5.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 7.5.5.3.5 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
DELETE Subscriptions
Check HTTP Response Status Code Is 405
-POST Create a new Fault Management alarm subscription - Unprocessable entity
+POST Create a new Fault Management alarm subscription - Unprocessable content
[Documentation] Test ID:8.3.3.3.17
- ... Test title: POST Create a new fault management alarm subscription - Unprocessable entity
+ ... Test title: POST Create a new fault management alarm subscription - Unprocessable content
... Test objective: The objective is to test that a new fault management alarm subscription is not created if the notification endpoint is unreachable by the NFV-MANO.
... Pre-conditions: No subscription with the same filter and callbackUri exists.
- ... Reference: clause 7.5.5.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 7.5.5.3.1 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: Notification endpoint is unreachable by the NFV-MANO.
... Post-Conditions: none
diff --git a/SOL009/NFVMANOLogManagement-API/ApiVersion.robot b/SOL009/NFVMANOLogManagement-API/ApiVersion.robot
index efd72ad08dc7018bb870cde88651e1e73bf5e6e5..2b94ded483a2d894144b694d3f56f1b8e1eb2b8e 100644
--- a/SOL009/NFVMANOLogManagement-API/ApiVersion.robot
+++ b/SOL009/NFVMANOLogManagement-API/ApiVersion.robot
@@ -7,7 +7,7 @@ POST API Version - Method not implemented
... Test title: POST API version - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -19,7 +19,7 @@ GET API Version
... Test title: GET API Version
... Test objective: The objective is to test that GET method successfully return ApiVersionInformation
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -32,7 +32,7 @@ PUT API Version - Method not implemented
... Test title: PUT API Version - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -44,7 +44,7 @@ PATCH API Version - Method not implemented
... Test title: PATCH API Version - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -56,7 +56,7 @@ DELETE API Version - Method not implemented
... Test title: DELETE API Version - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -68,7 +68,7 @@ POST API Version with apiMajorVerion - Method not implemented
... Test title: POST API version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -80,7 +80,7 @@ GET API Version with apiMajorVerion
... Test title: GET API Version with apiMajorVerion
... Test objective: The objective is to test that GET method successfully return ApiVersionInformation
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -93,7 +93,7 @@ PUT API Version with apiMajorVerion - Method not implemented
... Test title: PUT API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -105,7 +105,7 @@ PATCH API Version with apiMajorVerion - Method not implemented
... Test title: PATCH API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -117,7 +117,7 @@ DELETE API Version with apiMajorVerion - Method not implemented
... Test title: DELETE API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL009/NFVMANOLogManagement-API/CompileLogTask.robot b/SOL009/NFVMANOLogManagement-API/CompileLogTask.robot
index 8b0f24d294d7fd2a57155b1a0e4c4b00b9056d0c..e3f6b68b66f4a184590e35b979e3b85ac66879e1 100644
--- a/SOL009/NFVMANOLogManagement-API/CompileLogTask.robot
+++ b/SOL009/NFVMANOLogManagement-API/CompileLogTask.robot
@@ -8,7 +8,7 @@ Request to compile the logged data into a file - Synchronous mode
... Test title: Request to compile the logged data into a file - Synchronous mode
... Test objective: The objective is to request to compile the logged data into a file in synchronous mode and perform a JSON schema validation on the returned log report data structure
... Pre-conditions: logging job is available
- ... Reference: clause 8.5.6.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.6.3.1 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: The NFV-MANO can decide immediately what to respond to a compile request
... Post-Conditions: none
@@ -22,7 +22,7 @@ Request to compile the logged data into a file - Asynchronous mode
... Test title: Request to compile the logged data into a file - Asynchronous mode
... Test objective: The objective is to request to compile the logged data into a file in asynchronous mode
... Pre-conditions: logging job is available
- ... Reference: clause 8.5.6.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.6.3.1 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: The NFV-MANO can not decide immediately what to respond to a compile request
... Post-Conditions: log report is available to the API consumer
@@ -36,7 +36,7 @@ Request to compile the logged data into a file - Already Processing
... Test title: Request to compile the logged data into a file - Already Processing
... Test objective: The objective is to request to compile the logged data into a file when a log data compilation and report creation is already ongoing, or a log report has just been created, for the specified logging job at the time of processing the request
... Pre-conditions: none
- ... Reference: clause 8.5.6.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.6.3.1 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -44,12 +44,12 @@ Request to compile the logged data into a file - Already Processing
Check HTTP Response Status Code Is 303
Check HTTP Response Header Contains Location
-Request to compile the logged data into a file with unprocessable entity
+Request to compile the logged data into a file with unprocessable content
[Documentation] Test ID: 8.3.4.4.4
- ... Test title: Request to compile the logged data into a file with unprocessable entity
+ ... Test title: Request to compile the logged data into a file with unprocessable content
... Test objective: The objective is to test that the rrequest to compile the logged data into a file fails when error in request body.
... Pre-conditions: none
- ... Reference: clause 8.5.6.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.6.3.1 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -62,7 +62,7 @@ GET Compiled Log Data - Method not implemented
... Test title: GET Compiled Log Data - Method not implemented
... Test objective: The objective is to test that GET method is not allowed to retrieve compiled log data.
... Pre-conditions: none
- ... Reference: clause 8.5.6.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.6.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -74,7 +74,7 @@ PUT Compiled Log Data - Method not implemented
... Test title: PUT Compiled Log Data - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to update compiled log data.
... Pre-conditions: none
- ... Reference: clause 8.5.6.3.3 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.6.3.3 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -86,7 +86,7 @@ PATCH Compiled Log Data - Method not implemented
... Test title: PATCH Compiled Log Data - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update compiled log data.
... Pre-conditions: none
- ... Reference: clause 8.5.6.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.6.3.4 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -98,10 +98,10 @@ DELETE Compiled Log Data - Method not implemented
... Test title: DELETE Compiled Log Data - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to update compiled log data.
... Pre-conditions: none
- ... Reference: clause 8.5.6.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.6.3.5 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
Send DELETE Compiled Log Data
Check HTTP Response Status Code Is 405
-
\ No newline at end of file
+
diff --git a/SOL009/NFVMANOLogManagement-API/IndividualLoggingJob.robot b/SOL009/NFVMANOLogManagement-API/IndividualLoggingJob.robot
index 16a366f691dc889ff2193f80edfb1e37527b49c1..be2e6bf2de134b910a4fb0c167ae95ff8592dd4b 100644
--- a/SOL009/NFVMANOLogManagement-API/IndividualLoggingJob.robot
+++ b/SOL009/NFVMANOLogManagement-API/IndividualLoggingJob.robot
@@ -7,7 +7,7 @@ POST Individual Logging Job - Method not implemented
... Test title: POST Individual Logging Job - method not implemented
... Test objective: The objective is to test that POST method is not allowed to create an Indiviual Logging
... Pre-conditions: none
- ... Reference: clause 8.5.4.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.4.3.1 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -19,7 +19,7 @@ GET individual Logging Job
... Test title: Get individual Logging Job
... Test objective: The objective is to test the retrieval of an individual logging job and perform a JSON schema validation of the collected job data structure
... Pre-conditions: Logging Job is already created.
- ... Reference: clause 8.5.4.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.4.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -33,7 +33,7 @@ GET individual Logging Job with invalid resource identifier
... Test title: Get individual Logging Job with invalid resource identifier
... Test objective: The objective is to test that the retrieval of an individual logging job fails when using an invalid resource identifier, and perform the JSON schema validation of the failed operation HTTP response
... Pre-conditions: Logging Job is already created.
- ... Reference: clause 8.5.4.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.4.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -46,7 +46,7 @@ PUT Individual Logging Job - Method not implemented
... Test title: PUT Individual Logging Job - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to update an existing Logging Job
... Pre-conditions: none
- ... Reference: clause 8.5.4.3.3 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.4.3.3 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -58,7 +58,7 @@ PATCH Individual Logging Job - Method not implemented
... Test title: PATCH Individual Logging Job - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to modify an existing new Logging Job
... Pre-conditions: none
- ... Reference: clause 6.5.4.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 6.5.4.3.4 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -70,7 +70,7 @@ DELETE Individual Logging Job
... Test title: DELETE Individual Logging Job
... Test objective: The objective is to test the deletion of an individual logging job
... Pre-conditions: Logging Job is already created.
- ... Reference: clause 8.5.4.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.4.3.5 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: The Logging Job is no more available.
@@ -83,7 +83,7 @@ DELETE Individual Logging Job with invalid resource identifier
... Test title: DELETE Individual Logging Job with invalid resource identifier
... Test objective: The objective is to test that the deletion of an individual logging job fails when using an invalid resource identifier
... Pre-conditions: Logging Job is already created.
- ... Reference: clause 8.5.4.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.4.3.5 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL009/NFVMANOLogManagement-API/IndividualReport.robot b/SOL009/NFVMANOLogManagement-API/IndividualReport.robot
index c710c34baca85acc4ee4ea97ac1b88c1ec75f38b..d0a31fdbb765d931b13ef7ad58ed7d0a143b6127 100644
--- a/SOL009/NFVMANOLogManagement-API/IndividualReport.robot
+++ b/SOL009/NFVMANOLogManagement-API/IndividualReport.robot
@@ -7,7 +7,7 @@ POST Individual Log Report - Method not implemented
... Test title: POST Individual Log Report - Method not implemented
... Test objective: The objective is to test that POST method is not allowed to create a new log report.
... Pre-conditions: none
- ... Reference: clause 8.5.5.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.5.3.1 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -19,7 +19,7 @@ Get Individual Log Report
... Test title: Get Individual Log Report
... Test objective: The objective is to test the retrieval of an individual log report and perform a JSON schema validation of the collected report data structure
... Pre-conditions: One or more log reports are set.
- ... Reference: clause 8.5.5.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.5.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -32,7 +32,7 @@ Get Individual Log Report (asynchronous)
... Test title: Get Individual Log Report (asynchronous)
... Test objective: The objective is to test the retrieval of an individual log report is ongoing and no log report is available yet.
... Pre-conditions: One or more log reports are set.
- ... Reference: clause 8.5.5.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.5.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -44,7 +44,7 @@ Get Individual Log Report with invalid resource endpoint
... Test title: Get Individual Log Report with invalid resource endpoint
... Test objective: The objective is to test that the retrieval of an individual log report fails when using an invalid resource endpoint.
... Pre-conditions: One or more log reports are set.
- ... Reference: clause 8.5.5.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.5.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -57,7 +57,7 @@ PUT Individual Log Report - Method not implemented
... Test title: PUT Individual Log Report - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to update an existing log report.
... Pre-conditions: none
- ... Reference: clause 8.5.5.3.3 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.5.3.3 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -69,7 +69,7 @@ PATCH Individual Log Report - Method not implemented
... Test title: PATCH Individual Log Report - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to modify an existinglog report.
... Pre-conditions: none
- ... Reference: clause 8.5.5.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.5.3.4 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -81,7 +81,7 @@ DELETE Individual Log Report - Method not implemented
... Test title: DELETE Individual Log Report - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to delete an existing log report.
... Pre-conditions: none
- ... Reference: clause 8.5.5.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.5.3.5 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL009/NFVMANOLogManagement-API/IndividualSubscription.robot b/SOL009/NFVMANOLogManagement-API/IndividualSubscription.robot
index c3a842ac87a5df006d31bb6a38515061f9330f59..d7376efcfc33cff8e1d5d780c20d72b8b838117b 100644
--- a/SOL009/NFVMANOLogManagement-API/IndividualSubscription.robot
+++ b/SOL009/NFVMANOLogManagement-API/IndividualSubscription.robot
@@ -7,7 +7,7 @@ GET Individual Subscription
... Test title: GET Individual Subscription
... Test objective: The objective is to test the retrieval of individual subscription and perform a JSON schema validation of the returned subscription data structure
... Pre-conditions: At least one subscription is available in the NFV-MANO.
- ... Reference: clause 8.5.8.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.8.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -21,7 +21,7 @@ GET Individual Subscription - invalid resource identifier
... Test title: GET Individual Subscription - invalid resource identifier
... Test objective: The objective is to test that the retrieval of an individual subscription fails when using an invalid resource identifier
... Pre-conditions: At least one subscription is available in the NFV-MANO.
- ... Reference: clause 8.5.8.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.8.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -34,7 +34,7 @@ DELETE Individual Subscription
... Test title: DELETE Individual Subscription
... Test objective: The objective is to test the deletion of an individual subscription
... Pre-conditions: At least one subscription is available in the NFV-MANO.
- ... Reference: clause 8.5.8.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.8.3.5 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: The is not available anymore in the NFV-MANO
@@ -47,7 +47,7 @@ DELETE Individual Subscription - invalid resource identifier
... Test title: DELETE Individual Subscription - invalid resource identifier
... Test objective: The objective is to test that the deletion of an individual subscription fails when using an invalid resource identifier
... Pre-conditions: At least one subscription is available in the NFV-MANO.
- ... Reference: clause 8.5.8.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.8.3.5 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -59,7 +59,7 @@ POST Individual Subscription - Method not implemented
... Test title: POST Individual Subscription - Method not implemented
... Test objective: The objective is to test that POST method is not allowed to create a new Subscription
... Pre-conditions: none
- ... Reference: clause 8.5.8.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.8.3.1 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -71,7 +71,7 @@ PUT Individual Subscription - Method not implemented
... Test title: PUT Individual Subscription - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to update an existing subscription
... Pre-conditions: none
- ... Reference: clause 8.5.8.3.3 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.8.3.3 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -83,7 +83,7 @@ PATCH Individual Subscription - Method not implemented
... Test title: PATCH Individual Subscription - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to modify an existing subscription
... Pre-conditions: none
- ... Reference: clause 8.5.8.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.8.3.4 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL009/NFVMANOLogManagement-API/LoggingJobs.robot b/SOL009/NFVMANOLogManagement-API/LoggingJobs.robot
index eafc5be21c4a4e668ba9eec07f25d53c04c4f9d3..1fa21ae2f06bc92697123a22c3224290501a7e71 100644
--- a/SOL009/NFVMANOLogManagement-API/LoggingJobs.robot
+++ b/SOL009/NFVMANOLogManagement-API/LoggingJobs.robot
@@ -7,7 +7,7 @@ POST Create a new logging job
... Test title: POST Create a new logging job
... Test objective: The objective is to create a new logging job, and perform the JSON schema validation of the operation HTTP response.
... Pre-conditions: none
- ... Reference: clause 8.5.3.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.3.3.1 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: logging job created
@@ -22,7 +22,7 @@ GET information about logging jobs
... Test title: GET information logging jobs
... Test objective: The objective is to retrieve information about logging jobs, and perform the JSON schema validation of the operation HTTP response.
... Pre-conditions: At least one logging job is created.
- ... Reference: clause 8.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -35,7 +35,7 @@ GET Logging jobs - invalid attribute-based filter
... Test title: GET Logging jobs - invalid attribute-based filter
... Test objective: The objective is to test that the retrieval of logging jobs fails when using invalid attribute-based filter, and perform the JSON schema validation of the failed operation HTTP response.
... Pre-conditions: At least one logging job is created.
- ... Reference: clause 8.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -48,7 +48,7 @@ GET Logging jobs - invalid attribute selector
... Test title: GET Logging jobs - invalid attribute selector
... Test objective: The objective is to test that the retrieval of logging jobs fails when using invalid attribute selector, and perform the JSON schema validation of the failed operation HTTP response.
... Pre-conditions: At least one logging job is created.
- ... Reference: clause 8.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -61,7 +61,7 @@ GET Logging jobs - Bad Request Response too Big
... Test title: GET Logging jobs - Bad Request Response too Big
... Test objective: The objective is to test that the retrieval of Logging job fails when response is too big, and perform the JSON schema validation of the failed operation HTTP response.
... Pre-conditions: At least one logging job is created.
- ... Reference: clause 8.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -74,7 +74,7 @@ GET information about logging jobs with attribute-based filter
... Test title: GET information about logging jobs with attribute-based filter
... Test objective: The objective is to retrieve information about the logging jobs with attribute filters, and perform the JSON schema validation of the failed operation HTTP response.
... Pre-conditions: At least one logging job is created.
- ... Reference: clause 8.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -87,7 +87,7 @@ GET information about logging jobs with "all_fields" attribute selector
... Test title: GET information about logging jobs with "all_fields" attribute selector
... Test objective: The objective is to retrieve information about logging jobs with "all_fields" attribute selector, and perform the JSON schema validation of the failed operation HTTP response.
... Pre-conditions: At least one logging job is created.
- ... Reference: clause 8.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -100,7 +100,7 @@ GET information about Logging Jobs with "exclude_default" attribute selector
... Test title: GET information about Logging Jobs with "exclude_default" attribute selector
... Test objective: The objective is to retrieve information about logging jobs with "exclude_default" attribute selector, and perform the JSON schema validation of the failed operation HTTP response.
... Pre-conditions: At least one logging job is created.
- ... Reference: clause 8.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -113,7 +113,7 @@ GET information about Logging Jobs with "fields" attribute selector
... Test title: GET information about Logging Jobs with fields attribute selector
... Test objective: The objective is to retrieve information about Logging Jobs with fields attribute selector, and perform the JSON schema validation of the failed operation HTTP response.
... Pre-conditions: At least one logging job is created.
- ... Reference: clause 8.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -126,7 +126,7 @@ GET information about Logging Jobs with "exclude_fields" attribute selector
... Test title: GET information about Logging Jobs with "exclude_fields" attribute selector
... Test objective: The objective is to retrieve information about the Logging Jobs with "exclude_fields" attribute selector, and perform the JSON schema validation of the failed operation HTTP response.
... Pre-conditions: At least one logging job is created.
- ... Reference: clause 8.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -139,7 +139,7 @@ GET information about Logging Jobs with "fields" and "exclude_default" attribute
... Test title: GET information about Logging Jobs with fields and exclude_default attribute selector
... Test objective: The objective is to retrieve information about Logging Jobs with fields and exclude_default attribute selector, and perform the JSON schema validation of the failed operation HTTP response.
... Pre-conditions: At least one logging job is created.
- ... Reference: clause 8.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -152,7 +152,7 @@ GET information about Logging Jobs with Paged Response
... Test title: GET information about Logging Jobs with Paged Response
... Test objective: The objective is to query information about Logging Jobs to get Paged Response.
... Pre-conditions: At least one logging job is created.
- ... Reference: clause 8.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -165,7 +165,7 @@ GET information about Logging Jobs with malformed authorization token
... Test title: GET information about Logging Jobs with malformed authorization token
... Test objective: The objective is to test that the retrieval of information about Logging Jobs fails when using malformed authorization token.
... Pre-conditions: none
- ... Reference: clause 8.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: The Peer Entity requires the usage of access tokens for authorizing the API requests.
... Post-Conditions: none
@@ -177,7 +177,7 @@ GET information about Logging Jobs without authorization token
... Test title: GET information about Logging Jobs without authorization token
... Test objective: The objective is to test that the retrieval of information about Logging Jobs fails when omitting the authorization token.
... Pre-conditions: none
- ... Reference: clause 8.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: The Peer Entity requires the usage of access tokens for authorizing the API requests.
... Post-Conditions: none
@@ -189,7 +189,7 @@ GET information about Logging Jobs with expired or revoked authorization token
... Test title: GET information about Logging Jobs with expired or revoked authorization token
... Test objective: The objective is to test that the retrieval of information about Logging Jobs fails when using expired or revoked authorization token.
... Pre-conditions: none
- ... Reference: clause 8.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: The Peer Entity requires the usage of access tokens for authorizing the API requests.
... Post-Conditions: none
@@ -201,7 +201,7 @@ PUT Logging Jobs - Method not implemented
... Test title: PUT Logging Jobs - Method not implemented
... Test objective: The objective is to test that the method is not implemented
... Pre-conditions: none
- ... Reference: clause 8.5.3.3.3 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.3.3.3 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -213,7 +213,7 @@ PATCH Logging Jobs - Method not implemented
... Test title: PATCH Logging Jobs - Method not implemented
... Test objective: The objective is to test that the method is not implemented
... Pre-conditions: none
- ... Reference: clause 8.5.3.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.3.3.4 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -225,7 +225,7 @@ DELETE Logging Jobs - Method not implemented
... Test title: DELETE Logging Jobs - Method not implemented
... Test objective: The objective is to test that the method is not implemented
... Pre-conditions: none
- ... Reference: clause 8.5.3.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.3.3.5 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL009/NFVMANOLogManagement-API/NotificationEndpoint.robot b/SOL009/NFVMANOLogManagement-API/NotificationEndpoint.robot
index 67181a745c35f8a63cf9c03e218d078d18938e23..0bd1b3550e74800f34afef69ace45d33f2a38be4 100644
--- a/SOL009/NFVMANOLogManagement-API/NotificationEndpoint.robot
+++ b/SOL009/NFVMANOLogManagement-API/NotificationEndpoint.robot
@@ -8,7 +8,7 @@ Log Report Available Notification
... Test title: Log Report Available Notification
... Test objective: The objective is to test that Log Report Available Notification is delivered with success to the notification consumer.
... Pre-conditions: A subscription for log report available notification is available in the NFV-MANO.
- ... Reference: clause 8.5.9.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.9.3.1 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
diff --git a/SOL009/NFVMANOLogManagement-API/Notifications.robot b/SOL009/NFVMANOLogManagement-API/Notifications.robot
index 4f797cd6be3a3f52fb8a409f16ab5ff39b0990f1..da28ed2d23e2a836f11c5dfa809e9f94b2b6decf 100644
--- a/SOL009/NFVMANOLogManagement-API/Notifications.robot
+++ b/SOL009/NFVMANOLogManagement-API/Notifications.robot
@@ -9,7 +9,7 @@ Log Report Avaliable Notification
... Test title: Log Report Avaliable Notification
... Test objective: The objective is to test the dispatch of Log Report Avaliable Notification when new log report is available in the NFV-MANO, and perform a JSON schema and content validation of the delivered notification. The action that triggers the notification under test is an explicit test step, but it is not performed by the test system.
... Pre-conditions: none
- ... Reference: clause 8.5.9.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.9.3.1 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL009/NFVMANOLogManagement-API/Subscriptions.robot b/SOL009/NFVMANOLogManagement-API/Subscriptions.robot
index a513bf9b9baa2e2bbd039621e0971c5f651b2f50..c1087430c20f3535f382199700d65266af43769b 100644
--- a/SOL009/NFVMANOLogManagement-API/Subscriptions.robot
+++ b/SOL009/NFVMANOLogManagement-API/Subscriptions.robot
@@ -9,7 +9,7 @@ GET all Subscriptions
... Test title: GET all Subscriptions
... Test objective: The objective is to test the retrieval list of active subscriptions list to log management notifications and perform a JSON schema validation of the returned subscriptions data structure
... Pre-conditions: At least one subscription is available in the NFV-MANO.
- ... Reference: clause 8.5.7.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.7.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -22,7 +22,7 @@ GET Subscriptions with attribute-based filter
... Test title: GET Subscriptions with attribute-based filter
... Test objective: The objective is to test the retrieval of active subscriptions list to log management notifications using attribute-based filter, perform a JSON schema validation of the collected indicators data structure, and verify that the retrieved information matches the issued attribute-based filters
... Pre-conditions: At least one subscription is available in the NFV-MANO.
- ... Reference: clause 8.5.7.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.7.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -35,7 +35,7 @@ GET Subscriptions with Paged Response
... Test title: GET Subscriptions with Paged Response
... Test objective: The objective is to query information of active subscriptions list to log management notifications to get Paged Response.
... Pre-conditions: At least one subscription is available in the NFV-MANO.
- ... Reference: clause 8.5.7.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.7.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -48,7 +48,7 @@ GET Subscriptions - invalid attribute-based filter
... Test title: GET Subscriptions - invalid attribute-based filter
... Test objective: The objective is to test that the retrieval of active subscriptions list to log management notifications fails when using invalid attribute-based filters, and perform the JSON schema validation of the failed operation HTTP response.
... Pre-conditions: At least one subscription is available in the NFV-MANO.
- ... Reference: clause 8.5.7.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.7.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -61,7 +61,7 @@ GET Subscriptions - Bad Request Response too Big
... Test title: GET Subscriptions - Bad Request Response too Big
... Test objective: The objective is to test that the retrieval of active subscriptions list to log management notifications fails when response is too big, and perform the JSON schema validation of the failed operation HTTP response.
... Pre-conditions: At least one subscription is available in the NFV-MANO.
- ... Reference: clause 8.5.7.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.7.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -74,7 +74,7 @@ GET Subscriptions - invalid resource endpoint
... Test title: GET Subscriptions - invalid resource endpoint
... Test objective: The objective is to test that the retrieval of active subscriptions list to log management notifications fails when using invalid resource endpoint.
... Pre-conditions: At least one subscription is available in the NFV-MANO.
- ... Reference: clause 8.5.7.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.7.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -87,7 +87,7 @@ GET Subscription with attribute-based filter "id"
... Test title: GET Subscription with attribute-based filter "id"
... Test objective: The objective is to retrieve the list of active subscriptions with filter "id"
... Pre-conditions: none
- ... Reference: clause 8.5.7.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.7.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -101,7 +101,7 @@ Get subscriptions with filter "filter.notificationTypes"
... Test title: GET Subscription with attribute-based filter "filter.notificationTypes"
... Test objective: The objective is to retrieve the list of active subscriptions with filter "filter.notificationTypes"
... Pre-conditions: none
- ... Reference: clause 8.5.7.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.7.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -115,7 +115,7 @@ POST Create new Subscription
... Test title: POST Create new Subscription
... Test objective: The objective is to test the creation of a new subscription to log management notification and perform a JSON schema and content validation of the returned subscription data structure
... Pre-conditions: none
- ... Reference: clause 8.5.7.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.7.3.1 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: The subscription is successfully set and it matches the issued subscription
@@ -131,7 +131,7 @@ POST Create request for duplicated Subscription not creating duplicated subscrip
... Test title: POST Create request for duplicated Subscription not creating duplicated subscriptions
... Test objective: The objective is to test the attempt of a creation of a duplicated subscription failed and check that no new subscription is created and a link to the original subscription is returned
... Pre-conditions: At least one subscription is available in the NFV-MANO.
- ... Reference: clause 8.5.7.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.7.3.1 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: The NFV-MANO does not support the creation of duplicated subscriptions
... Post-Conditions: The existing Subscription returned is available in the NFV-MANO
@@ -147,7 +147,7 @@ POST Create request for duplicated Subscription creating duplicated subscription
... Test title: POST Create request for duplicated Subscription creating duplicated subscriptions
... Test objective: The objective is to test the creation of a duplicated subscription and perform a JSON schema and content validation of the returned duplicated subscription data structure
... Pre-conditions: At least one subscription is available in the NFV-MANO.
- ... Reference: clause 8.5.7.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.7.3.1 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: The NFV-MANO supports the creation of duplicated subscriptions
... Post-Conditions: The duplicated subscription is successfully set and it matches the issued subscription
@@ -162,7 +162,7 @@ PUT Subscriptions - Method not implemented
... Test title: PUT Subscriptions - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to modify subscriptions
... Pre-conditions: none
- ... Reference: clause 8.5.7.3.3 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.7.3.3 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -174,7 +174,7 @@ PATCH Subscriptions - Method not implemented
... Test title: PATCH Subscriptions - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update subscriptions
... Pre-conditions: none
- ... Reference: clause 8.5.7.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.7.3.4 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -186,19 +186,19 @@ DELETE Subscriptions - Method not implemented
... Test title: DELETE Subscriptions - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to delete subscriptions
... Pre-conditions: none
- ... Reference: clause 8.5.7.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.7.3.5 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
Send Delete Request for Subscriptions
Check HTTP Response Status Code Is 405
-POST Create new Subscription - Unprocessable entity
+POST Create new Subscription - Unprocessable content
[Documentation] Test ID: 8.3.4.5.15
- ... Test title: POST Create new Subscription - Unprocessable entity
+ ... Test title: POST Create new Subscription - Unprocessable content
... Test objective: The objective is to test that a new log management subscription is not created if the notification endpoint is unreachable by the NFV-MANO.
... Pre-conditions: none
- ... Reference: clause 8.5.7.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 8.5.7.3.1 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: Notification endpoint is unreachable by the NFV-MANO.
... Post-Conditions: none
diff --git a/SOL009/NFVMANOLogManagement-API/schemas/LoggingJob.schema.json b/SOL009/NFVMANOLogManagement-API/schemas/LoggingJob.schema.json
index 5521b76ab9008222b398718d22e11e4439e79d8b..e4b1959980ff9f5e0e23dd4fc252015e700a7c54 100644
--- a/SOL009/NFVMANOLogManagement-API/schemas/LoggingJob.schema.json
+++ b/SOL009/NFVMANOLogManagement-API/schemas/LoggingJob.schema.json
@@ -1,7 +1,13 @@
{
"description": "This type represents a logging job. It shall comply with the provisions defined in table 8.6.2.6-1.",
"type": "object",
- "required": ["id", "objectInstanceIds", "jobCriteria", "jobConfig", "_links"],
+ "required": [
+ "id",
+ "objectInstanceIds",
+ "jobCriteria",
+ "jobConfig",
+ "_links"
+ ],
"properties": {
"id": {
"description": "An identifier with the intention of being globally unique.\n",
@@ -11,7 +17,7 @@
"description": "Identifiers of the object instance for which logging information is collected. This attribute shall contain the identifier of the instance of the object that is logged according to their type.",
"type": "array",
"items": {
- "description": "This type represents the identifier to reference a managed object of a particular type. \n",
+ "description": "This type represents the identifier to reference a managed object of a particular type.\n",
"type": "object",
"properties": {
"type": {
@@ -34,28 +40,43 @@
"type": "string"
}
},
- "required": ["type", "objectId"]
+ "required": [
+ "type",
+ "objectId"
+ ]
}
},
"jobCriteria": {
"description": "This type represents collection criteria for logging jobs. * NOTE:\tThe value of the loggingType has dependency on the object that is requested to be logged\n (refer to the CreateLoggingJobRequest): a) the logging of messages is only applicable to\n ManoServiceInterface and ConsumedManoInterface objects.",
"type": "object",
- "required": ["loggingType"],
+ "required": [
+ "loggingType"
+ ],
"properties": {
"loggingType": {
- "description": "Type of logging. This defines the types of logged information to collect.\nPermitted values: - MESSAGES: logged NFV-MANO service interface messages. - SERVICES: logged messages about processes pertaining to NFV-MANO services. - SYSTEM: logged messages about the NFV-MANO functional entityΓÇÖs system enabled by the provider.\nSee note.",
+ "description": "Type of logging. This defines the types of logged information to collect.\nPermitted values: - MESSAGES: logged NFV-MANO service interface messages. - SERVICES: logged messages about processes pertaining to NFV-MANO services. - SYSTEM: logged messages about the NFV-MANO functional entity’s system enabled by the provider.\nSee note.",
"type": "string",
- "enum": ["MESSAGES", "SERVICES", "SYSTEM"]
+ "enum": [
+ "MESSAGES",
+ "SERVICES",
+ "SYSTEM"
+ ]
},
"messagesLogDetail": {
"description": "This type represents criteria for logging jobs to collect logged messages on NFV-MANO service interfaces. * NOTE:\tIf a matching pattern is present, at least one of the \"srcIpAddress\", \"dstIpAddress\", \"requestMethod\",\n \"requestUriPattern\" or \"responseCodes\" shall be provided.",
"type": "object",
- "required": ["direction"],
+ "required": [
+ "direction"
+ ],
"properties": {
"direction": {
"description": "The direction of the interface messages to match.\nPermitted values: - IN: input messages into the interface. - OUT: output messages from the interface. - ALL: both input and output messages into/from the interface.",
"type": "string",
- "enum": ["IN", "OUT", "ALL"]
+ "enum": [
+ "IN",
+ "OUT",
+ "ALL"
+ ]
},
"matchingPatterns": {
"description": "Patterns to be matched in the interface message. If provided, only messages that match all the values provided in the sub-attributes shall be logged. An API consumer can provide more than one \"matchingPattern\" if combinations of patterns are to be considered to match diverse sets of interface messages. See note.",
@@ -64,19 +85,29 @@
"type": "object",
"anyOf": [
{
- "required": ["srcIpAddress"]
+ "required": [
+ "srcIpAddress"
+ ]
},
{
- "required": ["dstIpAddress"]
+ "required": [
+ "dstIpAddress"
+ ]
},
{
- "required": ["requestMethod"]
+ "required": [
+ "requestMethod"
+ ]
},
{
- "required": ["requestUriPattern"]
+ "required": [
+ "requestUriPattern"
+ ]
},
{
- "required": ["responseCodes"]
+ "required": [
+ "responseCodes"
+ ]
}
],
"properties": {
@@ -86,11 +117,11 @@
"format": "IP"
},
"requestMethod": {
- "description": "HTTP request method to be matched. To match, the HTTP request method of the message shall be the same as the value of this attribute. Valid values are specified in IETF RFC 7231. The API producer shall support this attribute.",
+ "description": "HTTP request method to be matched. To match, the HTTP request method of the message shall be the same as the value of this attribute. Valid values are specified in IETF RFC 9110 and IETF RFC 5789. The API producer shall support this attribute.",
"type": "string"
},
"requestUriPattern": {
- "description": "Substring to be matched in the request URI. To match, the request URI shall include the value of\n this attribute as a substring. This is typically used to match messages which associate to RESTful\n resources, or to a specific API (e.g., by using the \"apiName\" of the API). The API producer shall\n support this attribute.",
+ "description": "Substring to be matched in the request URI. To match, the request URI shall include the value of\n this attribute as a substring. This is typically used to match messages which associate to RESTful\n resources, or to a specific API (e.g., by using the \"apiName\" of the API). The API producer shall\n support this attribute.",
"type": "string"
},
"dstIpAddress": {
@@ -135,7 +166,10 @@
"systemLogDetail": {
"description": "This type represents criteria for logging jobs to collect logged system events of the NFV-MANO functional entity. * NOTE:\tThe set of properties and values for this attribute are assumed to be known to the consumer\n by means defined outside of the present document.",
"type": "object",
- "required": ["systemLogs", "severityLevel"],
+ "required": [
+ "systemLogs",
+ "severityLevel"
+ ],
"properties": {
"systemLogs": {
"description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of keyvalue pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 8259. In the following example, a list of key-value pairs with four keys (\"aString\", \"aNumber\", \"anArray\" and \"anObject\") is provided to illustrate that the values associated with different keys can be of different type.\n",
@@ -156,7 +190,10 @@
"jobConfig": {
"description": "This type represents configuration data for a logging job. It shall comply with the provisions defined in table 8.6.3.6-1. NOTE: The present document version does not specify the support for \"log compilation and reporting based on events\" as specified in clause 6.6.2.2 of ETSI GS NFV-IFA 031.\n* NOTE 1:\tThe minimumReportingPeriod is used to throttle possible flooding of reports by providing a lower\n limit on the gap between two log availability notification to be emitted by the same logging job.\n NOTE 2:\tMore than one logCompilingCondition is possible to provide a combination of different conditions\n for the compilation. This covers use cases when the compilation of the log can be based on, e.g.\n a timer value and a size value, whichever first condition is met first. For instance, compile a\n log every 3 600 seconds, or whenever during the 3 600 seconds period the log grows in\n size to 1 000 000 bytes.\n NOTE 3:\tThe value is indicative, as the actual size of the compiled log files might not match the provided\n compileBySizeValue due to possible deviations in the tracking of the size of the log data by the\n API producer, and the size of individual logged data entries when these are collected.",
"type": "object",
- "required": ["reportingCondition", "securityConf"],
+ "required": [
+ "reportingCondition",
+ "securityConf"
+ ],
"properties": {
"startTime": {
"description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
@@ -170,12 +207,17 @@
},
"reportingCondition": {
"description": "Specifies the condition under which the producer will report to the consumer about the compiled log data.",
- "required": ["reportingType"],
+ "required": [
+ "reportingType"
+ ],
"properties": {
"reportingType": {
"description": "Specifies the type of reporting condition. Permitted values: - REPORTING_ON_COMPILATION: the producer shall notify the consumer once the compilation of the\n collected logging data into a file is completed and a new log report is available.\n- NO_REPORTING: no reporting is requested (the consumer can query the logging jobs to know about the\n availability of new log reports).",
"type": "string",
- "enum": ["REPORTING_ON_COMPILATION", "NO_REPORTING"]
+ "enum": [
+ "REPORTING_ON_COMPILATION",
+ "NO_REPORTING"
+ ]
},
"minimumReportingPeriod": {
"description": "Specifies the minimum periodicity at which the producer will report to the consumer about the collected log information, in seconds. See note 1.",
@@ -200,7 +242,10 @@
"properties": {
"logFileEncryption": {
"description": "Information about the encryption of the compiled log files. Shall be present if the log file is requested to be encrypted.",
- "required": ["encryptionCertificate", "cipherAlgorithm"],
+ "required": [
+ "encryptionCertificate",
+ "cipherAlgorithm"
+ ],
"type": "object",
"properties": {
"encryptionCertificate": {
@@ -240,7 +285,10 @@
"type": "array",
"items": {
"type": "object",
- "required": ["logReportId", "logReportLoc"],
+ "required": [
+ "logReportId",
+ "logReportLoc"
+ ],
"properties": {
"logReportId": {
"description": "An identifier with the intention of being globally unique.\n",
@@ -249,7 +297,9 @@
"logReportLoc": {
"description": "This type represents a link to a resource using an absolute URI.\n",
"type": "object",
- "required": ["href"],
+ "required": [
+ "href"
+ ],
"properties": {
"href": {
"description": "String formatted according to IETF RFC 3986.\n",
@@ -263,12 +313,16 @@
"_links": {
"description": "Links for this resource.",
"type": "object",
- "required": ["self"],
+ "required": [
+ "self"
+ ],
"properties": {
"self": {
"description": "This type represents a link to a resource using an absolute URI.\n",
"type": "object",
- "required": ["href"],
+ "required": [
+ "href"
+ ],
"properties": {
"href": {
"description": "String formatted according to IETF RFC 3986.\n",
@@ -282,7 +336,9 @@
"items": {
"description": "This type represents a link to a resource using an absolute URI.\n",
"type": "object",
- "required": ["href"],
+ "required": [
+ "href"
+ ],
"properties": {
"href": {
"description": "String formatted according to IETF RFC 3986.\n",
@@ -294,4 +350,4 @@
}
}
}
-}
+}
\ No newline at end of file
diff --git a/SOL009/NFVMANOLogManagement-API/schemas/LoggingJobs.schema.json b/SOL009/NFVMANOLogManagement-API/schemas/LoggingJobs.schema.json
index 86390e42be27dd351b012751e81b73d6337b82ba..646af5d9dc9cb59d60598fb20ef58375187fb375 100644
--- a/SOL009/NFVMANOLogManagement-API/schemas/LoggingJobs.schema.json
+++ b/SOL009/NFVMANOLogManagement-API/schemas/LoggingJobs.schema.json
@@ -19,7 +19,7 @@
"description": "Identifiers of the object instance for which logging information is collected. This attribute shall contain the identifier of the instance of the object that is logged according to their type.",
"type": "array",
"items": {
- "description": "This type represents the identifier to reference a managed object of a particular type. \n",
+ "description": "This type represents the identifier to reference a managed object of a particular type.\n",
"type": "object",
"properties": {
"type": {
@@ -42,28 +42,43 @@
"type": "string"
}
},
- "required": ["type", "objectId"]
+ "required": [
+ "type",
+ "objectId"
+ ]
}
},
"jobCriteria": {
"description": "This type represents collection criteria for logging jobs. * NOTE:\tThe value of the loggingType has dependency on the object that is requested to be logged\n (refer to the CreateLoggingJobRequest): a) the logging of messages is only applicable to\n ManoServiceInterface and ConsumedManoInterface objects.",
"type": "object",
- "required": ["loggingType"],
+ "required": [
+ "loggingType"
+ ],
"properties": {
"loggingType": {
- "description": "Type of logging. This defines the types of logged information to collect.\nPermitted values: - MESSAGES: logged NFV-MANO service interface messages. - SERVICES: logged messages about processes pertaining to NFV-MANO services. - SYSTEM: logged messages about the NFV-MANO functional entityΓÇÖs system enabled by the provider.\nSee note.",
+ "description": "Type of logging. This defines the types of logged information to collect.\nPermitted values: - MESSAGES: logged NFV-MANO service interface messages. - SERVICES: logged messages about processes pertaining to NFV-MANO services. - SYSTEM: logged messages about the NFV-MANO functional entity’s system enabled by the provider.\nSee note.",
"type": "string",
- "enum": ["MESSAGES", "SERVICES", "SYSTEM"]
+ "enum": [
+ "MESSAGES",
+ "SERVICES",
+ "SYSTEM"
+ ]
},
"messagesLogDetail": {
"description": "This type represents criteria for logging jobs to collect logged messages on NFV-MANO service interfaces. * NOTE:\tIf a matching pattern is present, at least one of the \"srcIpAddress\", \"dstIpAddress\", \"requestMethod\",\n \"requestUriPattern\" or \"responseCodes\" shall be provided.",
"type": "object",
- "required": ["direction"],
+ "required": [
+ "direction"
+ ],
"properties": {
"direction": {
"description": "The direction of the interface messages to match.\nPermitted values: - IN: input messages into the interface. - OUT: output messages from the interface. - ALL: both input and output messages into/from the interface.",
"type": "string",
- "enum": ["IN", "OUT", "ALL"]
+ "enum": [
+ "IN",
+ "OUT",
+ "ALL"
+ ]
},
"matchingPatterns": {
"description": "Patterns to be matched in the interface message. If provided, only messages that match all the values provided in the sub-attributes shall be logged. An API consumer can provide more than one \"matchingPattern\" if combinations of patterns are to be considered to match diverse sets of interface messages. See note.",
@@ -72,19 +87,29 @@
"type": "object",
"anyOf": [
{
- "required": ["srcIpAddress"]
+ "required": [
+ "srcIpAddress"
+ ]
},
{
- "required": ["dstIpAddress"]
+ "required": [
+ "dstIpAddress"
+ ]
},
{
- "required": ["requestMethod"]
+ "required": [
+ "requestMethod"
+ ]
},
{
- "required": ["requestUriPattern"]
+ "required": [
+ "requestUriPattern"
+ ]
},
{
- "required": ["responseCodes"]
+ "required": [
+ "responseCodes"
+ ]
}
],
"properties": {
@@ -94,11 +119,11 @@
"format": "IP"
},
"requestMethod": {
- "description": "HTTP request method to be matched. To match, the HTTP request method of the message shall be the same as the value of this attribute. Valid values are specified in IETF RFC 7231. The API producer shall support this attribute.",
+ "description": "HTTP request method to be matched. To match, the HTTP request method of the message shall be the same as the value of this attribute. Valid values are specified in IETF RFC 9110 and IETF RFC 5789. The API producer shall support this attribute.",
"type": "string"
},
"requestUriPattern": {
- "description": "Substring to be matched in the request URI. To match, the request URI shall include the value of\n this attribute as a substring. This is typically used to match messages which associate to RESTful\n resources, or to a specific API (e.g., by using the \"apiName\" of the API). The API producer shall\n support this attribute.",
+ "description": "Substring to be matched in the request URI. To match, the request URI shall include the value of\n this attribute as a substring. This is typically used to match messages which associate to RESTful\n resources, or to a specific API (e.g., by using the \"apiName\" of the API). The API producer shall\n support this attribute.",
"type": "string"
},
"dstIpAddress": {
@@ -143,7 +168,10 @@
"systemLogDetail": {
"description": "This type represents criteria for logging jobs to collect logged system events of the NFV-MANO functional entity. * NOTE:\tThe set of properties and values for this attribute are assumed to be known to the consumer\n by means defined outside of the present document.",
"type": "object",
- "required": ["systemLogs", "severityLevel"],
+ "required": [
+ "systemLogs",
+ "severityLevel"
+ ],
"properties": {
"systemLogs": {
"description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of keyvalue pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 8259. In the following example, a list of key-value pairs with four keys (\"aString\", \"aNumber\", \"anArray\" and \"anObject\") is provided to illustrate that the values associated with different keys can be of different type.\n",
@@ -164,7 +192,10 @@
"jobConfig": {
"description": "This type represents configuration data for a logging job. It shall comply with the provisions defined in table 8.6.3.6-1. NOTE: The present document version does not specify the support for \"log compilation and reporting based on events\" as specified in clause 6.6.2.2 of ETSI GS NFV-IFA 031.\n* NOTE 1:\tThe minimumReportingPeriod is used to throttle possible flooding of reports by providing a lower\n limit on the gap between two log availability notification to be emitted by the same logging job.\n NOTE 2:\tMore than one logCompilingCondition is possible to provide a combination of different conditions\n for the compilation. This covers use cases when the compilation of the log can be based on, e.g.\n a timer value and a size value, whichever first condition is met first. For instance, compile a\n log every 3 600 seconds, or whenever during the 3 600 seconds period the log grows in\n size to 1 000 000 bytes.\n NOTE 3:\tThe value is indicative, as the actual size of the compiled log files might not match the provided\n compileBySizeValue due to possible deviations in the tracking of the size of the log data by the\n API producer, and the size of individual logged data entries when these are collected.",
"type": "object",
- "required": ["reportingCondition", "securityConf"],
+ "required": [
+ "reportingCondition",
+ "securityConf"
+ ],
"properties": {
"startTime": {
"description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
@@ -178,12 +209,17 @@
},
"reportingCondition": {
"description": "Specifies the condition under which the producer will report to the consumer about the compiled log data.",
- "required": ["reportingType"],
+ "required": [
+ "reportingType"
+ ],
"properties": {
"reportingType": {
"description": "Specifies the type of reporting condition. Permitted values: - REPORTING_ON_COMPILATION: the producer shall notify the consumer once the compilation of the\n collected logging data into a file is completed and a new log report is available.\n- NO_REPORTING: no reporting is requested (the consumer can query the logging jobs to know about the\n availability of new log reports).",
"type": "string",
- "enum": ["REPORTING_ON_COMPILATION", "NO_REPORTING"]
+ "enum": [
+ "REPORTING_ON_COMPILATION",
+ "NO_REPORTING"
+ ]
},
"minimumReportingPeriod": {
"description": "Specifies the minimum periodicity at which the producer will report to the consumer about the collected log information, in seconds. See note 1.",
@@ -208,7 +244,10 @@
"properties": {
"logFileEncryption": {
"description": "Information about the encryption of the compiled log files. Shall be present if the log file is requested to be encrypted.",
- "required": ["encryptionCertificate", "cipherAlgorithm"],
+ "required": [
+ "encryptionCertificate",
+ "cipherAlgorithm"
+ ],
"type": "object",
"properties": {
"encryptionCertificate": {
@@ -248,7 +287,10 @@
"type": "array",
"items": {
"type": "object",
- "required": ["logReportId", "logReportLoc"],
+ "required": [
+ "logReportId",
+ "logReportLoc"
+ ],
"properties": {
"logReportId": {
"description": "An identifier with the intention of being globally unique.\n",
@@ -257,7 +299,9 @@
"logReportLoc": {
"description": "This type represents a link to a resource using an absolute URI.\n",
"type": "object",
- "required": ["href"],
+ "required": [
+ "href"
+ ],
"properties": {
"href": {
"description": "String formatted according to IETF RFC 3986.\n",
@@ -271,12 +315,16 @@
"_links": {
"description": "Links for this resource.",
"type": "object",
- "required": ["self"],
+ "required": [
+ "self"
+ ],
"properties": {
"self": {
"description": "This type represents a link to a resource using an absolute URI.\n",
"type": "object",
- "required": ["href"],
+ "required": [
+ "href"
+ ],
"properties": {
"href": {
"description": "String formatted according to IETF RFC 3986.\n",
@@ -290,7 +338,9 @@
"items": {
"description": "This type represents a link to a resource using an absolute URI.\n",
"type": "object",
- "required": ["href"],
+ "required": [
+ "href"
+ ],
"properties": {
"href": {
"description": "String formatted according to IETF RFC 3986.\n",
diff --git a/SOL009/NFVMANOPerformanceManagement-API/ApiVersion.robot b/SOL009/NFVMANOPerformanceManagement-API/ApiVersion.robot
index f3543a290f41734b7b99a3fbe52f388aa214c5e7..5a45404568f9233c6e929f0ab0a592410b4ba6d8 100644
--- a/SOL009/NFVMANOPerformanceManagement-API/ApiVersion.robot
+++ b/SOL009/NFVMANOPerformanceManagement-API/ApiVersion.robot
@@ -7,7 +7,7 @@ POST API Version - Method not implemented
... Test title: POST API version - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.1 v3.5.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -19,7 +19,7 @@ GET API Version
... Test title: GET API Version
... Test objective: The objective is to test that GET method successfully return ApiVersionInformation
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.1 v3.5.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -32,7 +32,7 @@ PUT API Version - Method not implemented
... Test title: PUT API Version - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.1 v3.5.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -44,7 +44,7 @@ PATCH API Version - Method not implemented
... Test title: PATCH API Version - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.1 v3.5.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -56,7 +56,7 @@ DELETE API Version - Method not implemented
... Test title: DELETE API Version - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1 v3.5.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -68,7 +68,7 @@ POST API Version with apiMajorVerion - Method not implemented
... Test title: POST API version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.1 v3.5.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -80,7 +80,7 @@ GET API Version with apiMajorVerion
... Test title: GET API Version with apiMajorVerion
... Test objective: The objective is to test that GET method successfully return ApiVersionInformation
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.1 v3.5.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -93,7 +93,7 @@ PUT API Version with apiMajorVerion - Method not implemented
... Test title: PUT API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.1 v3.5.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -105,7 +105,7 @@ PATCH API Version with apiMajorVerion - Method not implemented
... Test title: PATCH API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.1 v3.5.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -117,7 +117,7 @@ DELETE API Version with apiMajorVerion - Method not implemented
... Test title: DELETE API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1 v3.5.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL009/NFVMANOPerformanceManagement-API/IndividualPmJob.robot b/SOL009/NFVMANOPerformanceManagement-API/IndividualPmJob.robot
index 056cc8ccc22cbfce535aaafee2c5d1c9aefe5de8..2ea7304ff2c960c5b527dbf4251d11d46aa8fec1 100644
--- a/SOL009/NFVMANOPerformanceManagement-API/IndividualPmJob.robot
+++ b/SOL009/NFVMANOPerformanceManagement-API/IndividualPmJob.robot
@@ -7,7 +7,7 @@ POST Individual NFV-MANO Performance Job - Method not implemented
... Test title: POST Individual NFV-MANO Performance Job - method not implemented
... Test objective: The objective is to test that POST method is not allowed to create a new NFV-MANO Performance Monitoring Job
... Pre-conditions: none
- ... Reference: clause 6.5.4.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 6.5.4.3.1 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -19,7 +19,7 @@ GET individual NFV-MANO Performance Job
... Test title: Get individual NFV-MANO Performance Job
... Test objective: The objective is to test the retrieval of an individual performance monitoring job and perform a JSON schema validation of the collected job data structure
... Pre-conditions: A NFV-MANO instance is instantiated.
- ... Reference: clause 6.5.4.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 6.5.4.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -33,7 +33,7 @@ GET individual NFV-MANO Performance Job with invalid resource identifier
... Test title: Get individual NFV-MANO Performance Job with invalid resource identifier
... Test objective: The objective is to test that the retrieval of an individual performance monitoring job fails when using an invalid resource identifier, and perform the JSON schema validation of the failed operation HTTP response
... Pre-conditions: A NFV-MANO instance is instantiated. One or more NFV-MANO performance jobs are set in the NFV-MANO.
- ... Reference: clause 6.5.4.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 6.5.4.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -46,7 +46,7 @@ PUT Individual NFV-MANO Performance Job - Method not implemented
... Test title: PUT Individual NFV-MANO Performance Job - method not implemented
... Test objective: The objective is to test that PUT method is not allowed to update an existing NFV-MANO Performance Monitoring Job
... Pre-conditions: none
- ... Reference: clause 6.5.4.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 6.5.4.3.4 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -58,7 +58,7 @@ PATCH Individual NFV-MANO Performance Job
... Test title: PATCH Individual NFV-MANO Performance Job
... Test objective: The objective is to test that PATCH method modify an existing individual NFV-MANO Performance Monitoring Job
... Pre-conditions: A NFV-MANO instance is instantiated. One or more NFV-MANO performance jobs are set in the NFV-MANO.
- ... Reference: clause 6.5.4.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 6.5.4.3.4 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: PM Job resource is modified.
@@ -71,7 +71,7 @@ DELETE Individual NFV-MANO Performance Job
... Test title: Delete Individual NFV-MANO Performance Job
... Test objective: The objective is to test the deletion of an individual performance monitoring job
... Pre-conditions: A NFV-MANO instance is instantiated. One or more NFV-MANO performance jobs are set in the NFV-MANO.
- ... Reference: clause 6.5.4.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 6.5.4.3.5 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: The NFV-MANO Performance Job is no more available.
@@ -84,7 +84,7 @@ DELETE Individual NFV-MANO Performance Job with invalid resource identifier
... Test title: Delete individual NFV-MANO Performance Job with invalid resource identifier
... Test objective: The objective is to test that the deletion of an individual NFV-MANO performance monitoring job fails when using an invalid resource identifier
... Pre-conditions: A NFV-MANO instance is instantiated. One or more NFV-MANO performance jobs are set in the NFV-MANO.
- ... Reference: clause 6.5.4.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 6.5.4.3.5 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -96,7 +96,7 @@ PATCH Individual NFV-MANO Performance Job - Precondition failed
... Test title: PATCH Individual NFV-MANO Performance Job - Precondition failed
... Test objective: The objective is to test that the PATCH method cannot modify an individual NFV-MANO Performance job where the precondition was not met.
... Pre-conditions: A NFV-MANO instance is instantiated. One or more NFV-MANO performance jobs are set in the NFV-MANO.
- ... Reference: clause 6.5.4.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 6.5.4.3.4 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: PM Job resource is not modified.
@@ -104,15 +104,15 @@ PATCH Individual NFV-MANO Performance Job - Precondition failed
Check HTTP Response Status Code Is 412
Check HTTP Response Body Json Schema Is ProblemDetails
-PATCH Individual NFV-MANO Performance Job - Unprocessable entity
+PATCH Individual NFV-MANO Performance Job - Unprocessable content
[Documentation] Test ID: 8.3.2.2.9
- ... Test title: PATCH Individual NFV-MANO Performance Job - Unprocessable entity
+ ... Test title: PATCH Individual NFV-MANO Performance Job - Unprocessable content
... Test objective: The objective is to test that PATCH method cannot modify an exsisting individual PM job resource when a request contains syntactically correct data but the data cannot be processed.
... Pre-conditions: A NFV-MANO instance is instantiated. One or more NFV-MANO performance jobs are set in the NFV-MANO.
- ... Reference: clause 6.5.4.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 6.5.4.3.4 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: PM Job resource is not modified.
- Send Patch request for individual NFV_MANO Performance Job with unprocessable entity
+ Send Patch request for individual NFV_MANO Performance Job with unprocessable content
Check HTTP Response Status Code Is 422
Check HTTP Response Body Json Schema Is ProblemDetails
diff --git a/SOL009/NFVMANOPerformanceManagement-API/IndividualReport.robot b/SOL009/NFVMANOPerformanceManagement-API/IndividualReport.robot
index b122db873e1cabc4aca6b9a1b89bb0427c52bd28..90b0a7df98fe34c75027723d54621b8d0340870f 100644
--- a/SOL009/NFVMANOPerformanceManagement-API/IndividualReport.robot
+++ b/SOL009/NFVMANOPerformanceManagement-API/IndividualReport.robot
@@ -7,7 +7,7 @@ POST Individual Performance Report - Method not implemented
... Test title: POST Individual Performance Report - Method not implemented
... Test objective: The objective is to test that POST method is not allowed to create a new NFV-MANO performance report within a monitoring job.
... Pre-conditions: none
- ... Reference: clause 6.5.5.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 6.5.5.3.1 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -19,7 +19,7 @@ Get Individual Performance Report
... Test title: Get Individual Performance Report
... Test objective: The objective is to test the retrieval of an individual performance report associated to a monitoring job and perform a JSON schema validation of the collected report data structure
... Pre-conditions: A NFV-MANO instance is instantiated. One or more NFV-MANO performance reports are set for a monitoring job.
- ... Reference: clause 6.5.5.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 6.5.5.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -32,7 +32,7 @@ Get Individual Performance Report with invalid resource endpoint
... Test title: Get Individual Performance Report with invalid resource endpoint
... Test objective: The objective is to test that the retrieval of an individual NFV-MANO performance report associated to a monitoring job fails when using an invalid resource endpoint.
... Pre-conditions: A NFV-MANO instance is instantiated. One or more NFV-MANO performance reports are set for a monitoring job.
- ... Reference: clause 6.5.5.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 6.5.5.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -44,7 +44,7 @@ PUT Individual Performance Report - Method not implemented
... Test title: PUT Individual Performance Report - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to update an existing NFV-MANO performance report within a monitoring job.
... Pre-conditions: none
- ... Reference: clause 6.5.5.3.3 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 6.5.5.3.3 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -56,7 +56,7 @@ PATCH Individual Performance Report - Method not implemented
... Test title: PATCH Individual Performance Report - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to modify an existing NFV-MANO performance report within a monitoring job.
... Pre-conditions: none
- ... Reference: clause 6.5.5.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 6.5.5.3.4 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -68,7 +68,7 @@ DELETE Individual Performance Report - Method not implemented
... Test title: DELETE Individual Performance Report - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to delete an existing NFV-MANO performance report within a monitoring job
... Pre-conditions: none
- ... Reference: clause 6.5.5.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 6.5.5.3.5 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANOM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL009/NFVMANOPerformanceManagement-API/IndividualThreshold.robot b/SOL009/NFVMANOPerformanceManagement-API/IndividualThreshold.robot
index 83da2ff4e309b3e8ce4967d5b6c1410b86270b0d..30d70c9f116045638aec847e5e7d8430076c20e9 100644
--- a/SOL009/NFVMANOPerformanceManagement-API/IndividualThreshold.robot
+++ b/SOL009/NFVMANOPerformanceManagement-API/IndividualThreshold.robot
@@ -7,7 +7,7 @@ POST Individual Threshold - Method not implemented
... Test title: POST Individual Threshold - Method not implemented
... Test objective: The objective is to test that POST method is not allowed to create a new Performance Threshold
... Pre-conditions: none
- ... Reference: clause 6.5.7.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 6.5.7.3.1 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -19,7 +19,7 @@ GET Individual Threshold
... Test title: GET Individual Threshold
... Test objective: The objective is to test the retrieval of an individual NFV-MANO performance threshold and perform a JSON schema and content validation of the collected threshold data structure
... Pre-conditions: A NFV-MANO instance is instantiated. One or more performance thresholds are set.
- ... Reference: clause 6.5.7.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 6.5.7.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -33,7 +33,7 @@ GET Individual Threshold with invalid resource identifier
... Test title: GET Individual Threshold with invalid resource identifier
... Test objective: The objective is to test that the retrieval of an individual performance threshold fails when using an invalid resource identifier
... Pre-conditions: A NFV-MANO instance is instantiated. One or more performance jobs are set.
- ... Reference: clause 6.5.7.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 6.5.7.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -45,7 +45,7 @@ PUT Individual Threshold - Method not implemented
... Test title: PUT Individual Threshold - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to update an existing Performance threshold
... Pre-conditions: none
- ... Reference: clause 6.5.7.3.3 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 6.5.7.3.3 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -57,7 +57,7 @@ PATCH Individual Threshold
... Test title: PATCH Individual Threshold
... Test objective: The objective is to test that PATCH method modify an existing NFV_MANO performance threshold.
... Pre-conditions: A NFV-MANO instance is instantiated. One or more performance thresholds are set.
- ... Reference: clause 6.5.7.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 6.5.7.3.4 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: Threshold resource is modified.
@@ -70,7 +70,7 @@ DELETE Individual Threshold
... Test title: DELETE Individual Threshold
... Test objective: The objective is to test the deletion of an individual performance threshold
... Pre-conditions: A NFV-MANO instance is instantiated. One or more performance thresholds are set.
- ... Reference: clause 6.5.7.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 6.5.7.3.5 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: The Performance Threshold is not available anymore in the NFV-MANO
@@ -83,7 +83,7 @@ DELETE Individual Threshold with invalid resource identifier
... Test title: DELETE Individual Threshold with invalid resource identifier
... Test objective: The objective is to test the deletion of an individual performance threshold
... Pre-conditions: A NFV-MANO instance is instantiated. One or more performance thresholds are set.
- ... Reference: clause 6.5.7.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 6.5.7.3.5 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -95,7 +95,7 @@ PATCH Individual Threshold - Precondition failed
... Test title: PATCH Individual Threshold - Precondition failed
... Test objective: The objective is to test that the PATCH method cannot modify an individual NFV-MANO threshold where the precondition was not met.
... Pre-conditions: A NFV-MANO instance is instantiated. One or more performance thresholds are set.
- ... Reference: clause 6.5.7.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 6.5.7.3.4 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: Threshold resource is not modified.
@@ -103,15 +103,15 @@ PATCH Individual Threshold - Precondition failed
Check HTTP Response Status Code Is 412
Check HTTP Response Body Json Schema Is ProblemDetails
-PATCH Individual Threshold - Unprocessable entity
+PATCH Individual Threshold - Unprocessable content
[Documentation] Test ID: 8.3.2.5.9
- ... Test title: PATCH Individual Threshold - Unprocessable entity
+ ... Test title: PATCH Individual Threshold - Unprocessable content
... Test objective: The objective is to test that PATCH method cannot modify an exsisting individual threshold resource when a request contains syntactically correct data but the data cannot be processed.
... Pre-conditions: A NFV-MANO instance is instantiated. One or more performance thresholds are set.
- ... Reference: clause 6.5.7.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 6.5.7.3.4 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: Threshold resource is not modified.
- Send Patch request for individual Performance Threshold with unprocessable entity
+ Send Patch request for individual Performance Threshold with unprocessable content
Check HTTP Response Status Code Is 422
Check HTTP Response Body Json Schema Is ProblemDetails
diff --git a/SOL009/NFVMANOPerformanceManagement-API/NFVMANOPMKeywords.robot b/SOL009/NFVMANOPerformanceManagement-API/NFVMANOPMKeywords.robot
index 41dcec46bc9b6716fe3f58c6f5abe48c03858d84..e44605fb8dd6866dc3f0f9510c2c10d64d1e6396 100644
--- a/SOL009/NFVMANOPerformanceManagement-API/NFVMANOPMKeywords.robot
+++ b/SOL009/NFVMANOPerformanceManagement-API/NFVMANOPMKeywords.robot
@@ -293,7 +293,7 @@ Send Patch request for individual NFV-MANO Performance Job - Etag mismatch
${output}= Output response
Set Suite Variable ${response} ${output}
-Send Patch request for individual NFV_MANO Performance Job with unprocessable entity
+Send Patch request for individual NFV_MANO Performance Job with unprocessable content
Set Headers {"Accept":"${ACCEPT_JSON}"}
Set Headers {"Content-Type": "${CONTENT_TYPE_PATCH}"}
Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"${AUTHORIZATION_HEADER}":"${AUTHORIZATION_TOKEN}"}
@@ -479,7 +479,7 @@ Send Patch request for individual Performance Threshold - Etag mismatch
${output}= Output response
Set Suite Variable @{response} ${output}
-Send Patch request for individual Performance Threshold with unprocessable entity
+Send Patch request for individual Performance Threshold with unprocessable content
Log Trying to PUT threshold
Set Headers {"Accept": "${ACCEPT_JSON}"}
Set Headers {"Content-Type": "${CONTENT_TYPE_PATCH}"}
diff --git a/SOL009/NFVMANOPerformanceManagement-API/NotificationEndpoint.robot b/SOL009/NFVMANOPerformanceManagement-API/NotificationEndpoint.robot
index 09835042d5b4fa1d7f74b1677c4fb2e8b93e023c..ef00f429d3bec712d8c7babe8d3cf8b1fa73824d 100644
--- a/SOL009/NFVMANOPerformanceManagement-API/NotificationEndpoint.robot
+++ b/SOL009/NFVMANOPerformanceManagement-API/NotificationEndpoint.robot
@@ -8,7 +8,7 @@ Performance Information Available Notification
... Test title: Performance Information Available Notification
... Test objective: The objective is to test that Performance Available Notification is delivered with success to the notification consumer
... Pre-conditions: A subscription for performance available notification is available in the NFV-MANO.
- ... Reference: clause 6.5.10.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 6.5.10.3.1 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
@@ -21,7 +21,7 @@ Threshold Crossed Notification
... Test title: Threshold Crossed Notification
... Test objective: The objective is to test that Threshold Crossed Notification is delivered with success to the notification consumer
... Pre-conditions: A subscription for threshold crosssed notification is available in the NFV-MANO.
- ... Reference: clause 6.5.10.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 6.5.10.3.1 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
diff --git a/SOL009/NFVMANOPerformanceManagement-API/Notifications.robot b/SOL009/NFVMANOPerformanceManagement-API/Notifications.robot
index 98211c3f3120e7e0759501bb4c9b599ac95ce50e..8fb3977a0a9a9e64b8757005c7ba66a22c62bd65 100644
--- a/SOL009/NFVMANOPerformanceManagement-API/Notifications.robot
+++ b/SOL009/NFVMANOPerformanceManagement-API/Notifications.robot
@@ -9,7 +9,7 @@ Performance Information Availability Notification
... Test title: Performance Information Availability Notification
... Test objective: The objective is to test the dispatch of Performance Information Availability Notification when new performance information is available in the NFV-MANO, and perform a JSON schema and content validation of the delivered notification. The action that triggers the notification under test is an explicit test step, but it is not performed by the test system.
... Pre-conditions: A performance job is created, and a subscription for information availability notifications is available in the NFV-MANO.
- ... Reference: clause 6.5.10.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 6.5.10.3.1 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -22,7 +22,7 @@ Threshold Crossed Notification
... Test title: Threshold Crossed Notification
... Test objective: The objective is to test the dispatch of Threshold Crossed Notification when a previously set performance metric threshold is crossed, and perform a JSON schema and content validation of the delivered notification. The action that triggers the notification under test is an explicit test step, but it is not performed by the test system.
... Pre-conditions: A performance job is created, and a threshold subscription is available in the NFV-MANO.
- ... Reference: clause 6.5.10.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 6.5.10.3.1 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL009/NFVMANOPerformanceManagement-API/PMJobs.robot b/SOL009/NFVMANOPerformanceManagement-API/PMJobs.robot
index ebb291870f395d156e6abcb8433fa3eff37f8c2d..1f8f764117820866033e7152323fdce3eb7f7b3c 100644
--- a/SOL009/NFVMANOPerformanceManagement-API/PMJobs.robot
+++ b/SOL009/NFVMANOPerformanceManagement-API/PMJobs.robot
@@ -7,7 +7,7 @@ POST Create new NFV-MANO Performance Monitoring Job
... Test title: POST Create a new NFV-MANO Performance Monitoring Job
... Test objective: The objective is to test the creation of a new NFV-MANO performance monitoring job and perform the JSON schema validation of the returned job data structure
... Pre-conditions: A NFV-MANO instance is instantiated. One or more NFV-MANO performance jobs are set in the NFV-MANO.
- ... Reference: clause 6.5.3.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 6.5.3.3.1 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: The NFV-MANO Performance Job is successfully created on the NFV-MANO
@@ -21,7 +21,7 @@ GET all NFV-MANO Performance Monitoring Jobs
... Test title: GET all NFV-MANO Performance Monitoring Jobs
... Test objective: The objective is to test the retrieval of all the available NFV-MANO performance monitoring jobs and perform a JSON schema validation
... Pre-conditions: A NFV-MANO instance is instantiated. One or more NFV-MANO performance jobs are set in the NFV-MANO.
- ... Reference: clause 6.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 6.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -34,7 +34,7 @@ GET NFV-MANO Performance Monitoring Jobs with attribute-based filter
... Test title: GET all NFV-MANO Performance Monitoring Jobs with attribute-based filter
... Test objective: The objective is to test the retrieval of NFV-MANO performance monitoring jobs using attribute-based filter, perform a JSON schema validation of the collected jobs data structure
... Pre-conditions: A NFV-MANO instance is instantiated. One or more NFV-MANO performance jobs are set in the NFV-MANO.
- ... Reference: clause 6.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 6.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -47,7 +47,7 @@ GET all NFV-MANO Performance Monitoring Jobs with all_fields attribute selector
... Test title: GET all NFV-MANO Performance Monitoring Jobs with all_fields attribute selector
... Test objective: The objective is to test the retrieval of all NFV-MANO performance monitoring jobs all_fields attribute selector, perform a JSON schema validation of the collected jobs data structure
... Pre-conditions: A NFV-MANO instance is instantiated. One or more NFV-MANO performance jobs are set in the NFV-MANO.
- ... Reference: clause 6.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 6.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -60,7 +60,7 @@ GET all NFV-MANO Performance Monitoring Jobs with exclude_default attribute sele
... Test title: GET all NFV-MANO Performance Monitoring Jobs with exclude_default attribute selector
... Test objective: The objective is to test the retrieval of all NFV-MANO performance monitoring jobs exclude_default attribute selector, perform a JSON schema validation of the collected jobs data structure
... Pre-conditions: A NFV-MANO instance is instantiated. One or more NFV-MANO performance jobs are set in the NFV-MANO.
- ... Reference: clause 6.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 6.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -73,7 +73,7 @@ GET all NFV-MANO Performance Monitoring Jobs with fields attribute selector
... Test title: GET all NFV-MANO Performance Monitoring Jobs with fields attribute selector
... Test objective: The objective is to test the retrieval of all NFV-MANO performance monitoring jobs fields attribute selector, perform a JSON schema validation of the collected jobs data structure
... Pre-conditions: A NFV-MANO instance is instantiated. One or more NFV-MANO performance jobs are set in the NFV-MANO.
- ... Reference: clause 6.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 6.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: The NFV-MANO supports the use of fields attribute selector
... Post-Conditions: none
@@ -86,7 +86,7 @@ GET all NFV-MANO Performance Monitoring Jobs with exclude_fields attribute selec
... Test title: GET all NFV-MANO Performance Monitoring Jobs with exclude_fields attribute selector
... Test objective: The objective is to test the retrieval of all NFV-MANO performance monitoring jobs exclude_fields attribute selector, perform a JSON schema validation of the collected jobs data structure
... Pre-conditions: A NFV-MANO instance is instantiated. One or more NFV-MANO performance jobs are set in the NFV-MANO.
- ... Reference: clause 6.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 6.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: The NFV-MANO supports the use of exclude_fields attribute selector
... Post-Conditions: none
@@ -99,7 +99,7 @@ GET NFV-MANO Performance Monitoring Jobs with invalid attribute-based filter
... Test title: GET NFV-MANO Performance Monitoring Jobs with invalid attribute-based filter
... Test objective: The objective is to test that the retrieval of NFV-MANO performance monitoring jobs fails when using invalid attribute-based filter, and perform the JSON schema validation of the failed operation HTTP response
... Pre-conditions: A NFV-MANO instance is instantiated. One or more NFV-MANO performance jobs are set in the NFV-MANO.
- ... Reference: clause 6.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 6.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -112,7 +112,7 @@ GET NFV-MANO Performance Monitoring Jobs with invalid attribute selector
... Test title: GET NFV-MANO Performance Monitoring Jobs with invalid resource endpoint
... Test objective: The objective is to test that the retrieval of NFV-MANO performance monitoring jobs fails with invalid attribute selector
... Pre-conditions: A NFV-MANO instance is instantiated. One or more NFV-MANO performance jobs are set in the NFV-MANO.
- ... Reference: clause 6.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 6.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -125,7 +125,7 @@ GET information about multiple Performance Monitoring Jobs to get Paged Response
... Test title: GET information about multiple Performance Monitoring Jobs to get Paged Response
... Test objective: The objective is to retrieve information about the performance monitoring jobs to get paged response
... Pre-conditions: none
- ... Reference: clause 6.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 6.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -138,7 +138,7 @@ GET information about multiple Performance Monitoring Jobs for Bad Request Respo
... Test title: GET information about multiple Performance Monitoring Jobs for Bad Request Response too big
... Test objective: The objective is to test that GET method fail retrieving status information about performance monitoring jobs when Response is too big, and perform the JSON schema validation of the failed operation HTTP response
... Pre-conditions: none
- ... Reference: clause 6.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 6.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -151,7 +151,7 @@ GET information about multiple Performance Monitoring Jobs with "fields" and "ex
... Test title: GET all NFV-MANO Performance Monitoring Jobs with "fields" and "exclude_default" attribute selector
... Test objective: The objective is to retrieve all performance monitoring jobs with fields and exclude default attribute selector, and perform the JSON schema validation of the HTTP response.
... Pre-conditions: none
- ... Reference: clause 5.5.8.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.8.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -164,7 +164,7 @@ Get information about multiple Performance Monitoring Jobs with malformed author
... Test title: Get information about multiple Performance Monitoring Jobs with malformed authorization token
... Test objective: The objective is to test that the retrieval of information about Performance Monitoring Jobs fails when using malformed authorization token
... Pre-conditions: none
- ... Reference: clause 6.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 6.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: The NFV-MANO entity requires the usage of access tokens for authorizing the API requests.
... Post-Conditions: none
@@ -176,7 +176,7 @@ Get information about multiple Performance Monitoring Jobs without authorization
... Test title: Get information about multiple Performance Monitoring Jobs without authorization token
... Test objective: The objective is to test that the retrieval of information about Performance Monitoring Jobs fails when omitting the authorization token
... Pre-conditions: none
- ... Reference: clause 6.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 6.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: The NFV-MANO entity requires the usage of access tokens for authorizing the API requests.
... Post-Conditions: none
@@ -188,7 +188,7 @@ GET information about multiple Performance Monitoring Jobs with expired or revok
... Test title: GET information about multiple Performance Monitoring Jobs with expired or revoked authorization token
... Test objective: The objective is to test that the retrieval of information about Performance Monitoring Jobs fails when using expired or revoked authorization token
... Pre-conditions: One or more Network Service Descriptors are onboarded in the NFVO
- ... Reference: clause 6.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 6.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: The NFV-MANO entity requires the usage of access tokens for authorizing the API requests.
... Post-Conditions: none
@@ -200,7 +200,7 @@ PUT all NFV-MANO Performance Monitoring Jobs - Method not implemented
... Test title: PUT all NFV-MANO Performance Monitoring Jobs - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to modify NFV-MANO Performance Monitoring Jobs
... Pre-conditions: none
- ... Reference: clause 6.5.3.3.3 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 6.5.3.3.3 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -212,7 +212,7 @@ PATCH all NFV-MANO Performance Monitoring Jobs - (Method not implemented)
... Test title: PATCH all NFV-MANO Performance Monitoring Jobs - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update NFV-MANO Performance Monitoring Jobs
... Pre-conditions: none
- ... Reference: clause 6.5.3.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 6.5.3.3.4 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -224,7 +224,7 @@ DELETE all NFV-MANO Performance Monitoring Jobs - Method not implemented
... Test title: DELETE all NFV-MANO Performance Monitoring Jobs - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to update NFV-MANO Performance Monitoring Jobs
... Pre-conditions: none
- ... Reference: clause 6.5.3.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 6.5.3.3.5 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -236,7 +236,7 @@ POST Create new NFV-MANO Performance Monitoring Job - Unreachable Notification E
... Test title: POST Create a new NFV-MANO Performance Monitoring Job
... Test objective: The objective is to test that a new NFV_MANO Performance Monitoring Job is not created if the notification endpoint is unreachable by the NFV-MANO.
... Pre-conditions: A NFV-MANO instance is instantiated. One or more NFV-MANO performance jobs are set in the NFV-MANO.
- ... Reference: clause 6.5.3.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 6.5.3.3.1 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: Notification endpoint is unreachable by the NFV-MANO.
... Post-Conditions: none
diff --git a/SOL009/NFVMANOPerformanceManagement-API/Thresholds.robot b/SOL009/NFVMANOPerformanceManagement-API/Thresholds.robot
index d0b07cb04ffb885bc8272afa344e7ea1529d1666..b5777f265eb152d227c830b2f50764caf23614c8 100644
--- a/SOL009/NFVMANOPerformanceManagement-API/Thresholds.robot
+++ b/SOL009/NFVMANOPerformanceManagement-API/Thresholds.robot
@@ -7,7 +7,7 @@ POST Create new Performance Threshold
... Test title: POST Create new Performance Threshold
... Test objective: The objective is to test the creation of a new NFV-MANO performance threshold and perform the JSON schema validation of the returned threshold data structure.
... Pre-conditions: A NFV-MANO instance is instantiated.
- ... Reference: clause 6.5.6.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 6.5.6.3.1 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: The NFV-MANO Performance Threshold is successfully created on the NFV-MANO
@@ -22,7 +22,7 @@ GET All Performance Thresholds
... Test title: GET All Performance Thresholds
... Test objective: The objective is to test the retrieval of all the available NFV-MANO performance thresholds and perform a JSON schema validation of the collected thresholds data structure.
... Pre-conditions: A NFV-MANO instance is instantiated. One or more NFV-MANO performance thresholds are set.
- ... Reference: clause 6.5.6.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 6.5.6.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -35,7 +35,7 @@ GET Performance Thresholds with attribute-based filter
... Test title: GET Performance Thresholds with attribute-based filter
... Test objective: The objective is to test the retrieval of all the available NFV-MANO performance thresholds when using attribute-based filters, perform a JSON schema validation of the collected thresholds data structure, and verify that the retrieved information matches the issued attribute-based filter
... Pre-conditions: A NFV-MANO instance is instantiated. One or more NFV-MANO performance thresholds are set in the NFV-MANO.
- ... Reference: clause 6.5.6.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 6.5.6.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -49,7 +49,7 @@ GET Performance Threshold with Paged Response
... Test title: GET Performance Threshold with Paged Response
... Test objective: The objective is to query information about NFV-MANO Performance Thresholds to get Paged Response.
... Pre-conditions: A NFV-MANO instance is instantiated. One or more NFV-MANO performance thresholds are set.
- ... Reference: clause 6.5.6.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 6.5.6.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -62,7 +62,7 @@ GET Performance Thresholds - Invalid attribute-based filter
... Test title: GET Performance Thresholds - Invalid attribute-based filter
... Test objective: The objective is to test that the retrieval of NFV-MANO performance thresholds fails when using invalid attribute-based filter, and perform the JSON schema validation of the failed operation HTTP response.
... Pre-conditions: A NFV-MANO instance is instantiated. One or more NFV-MANO performance thresholds are set.
- ... Reference: clause 6.5.6.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 6.5.6.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -75,7 +75,7 @@ GET Performance Threshold - Bad Request Response too Big
... Test title: GET Performance Threshold - Bad Request Response too Big
... Test objective: The objective is to test that the retrieval of NFV-MANO performance thresholds fails when response is too big, and perform the JSON schema validation of the failed operation HTTP response.
... Pre-conditions: A NFV-MANO instance is instantiated. One or more NFV-MANO performance thresholds are set.
- ... Reference: clause 6.5.6.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 6.5.6.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -88,7 +88,7 @@ PUT Performance Thresholds - Method not implemented
... Test title: PUT Performance Thresholds - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to modify NFV-MANO Performance Thresholds
... Pre-conditions: none
- ... Reference: clause 6.5.6.3.3 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 6.5.6.3.3 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -100,7 +100,7 @@ PATCH Performance Thresholds - Method not implemented
... Test title: PATCH Performance Thresholds - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to modify NFV-MANO Performance Thresholds
... Pre-conditions: none
- ... Reference: clause 6.5.6.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 6.5.6.3.4 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -112,20 +112,20 @@ DELETE Performance Thresholds - Method not implemented
... Test title: DELETE Performance Thresholds - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to update NFV-MANO Performance Thresholds
... Pre-conditions: none
- ... Reference: clause 6.5.6.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 6.5.6.3.5 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
Send DELETE Request for all Performance Thresholds
Check HTTP Response Status Code Is 405
-POST Create new Performance Threshold - Unprocessable entity
+POST Create new Performance Threshold - Unprocessable content
[Documentation] Test ID: 8.3.2.4.10
- ... Test title: POST Create new Performance Threshold - Unprocessable Entity
+ ... Test title: POST Create new Performance Threshold - Unprocessable Content
... Test objective: The objective is to test the creation of a new NFV-MANO performance threshold and perform the JSON schema validation of the returned threshold data structure.
... Test objective: The objective is to test that a new NFV-MANO performance threshold is not created if the notification endpoint is unreachable by the NFV-MANO.
... Pre-conditions: A NFV-MANO instance is instantiated.
- ... Reference: clause 6.5.6.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 6.5.6.3.1 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: Notification endpoint is unreachable by the NFV-MANO.
... Post-Conditions: none
diff --git a/SOL009/NFVManoConfigurationAndInformationManagement-API/ApiVersion.robot b/SOL009/NFVManoConfigurationAndInformationManagement-API/ApiVersion.robot
index 52d5e7b5e8eb74becd81c1de15bc85dbe3eb6bec..e287ed1feb770fc799b1d1fb3f72fdbb47f2a32c 100644
--- a/SOL009/NFVManoConfigurationAndInformationManagement-API/ApiVersion.robot
+++ b/SOL009/NFVManoConfigurationAndInformationManagement-API/ApiVersion.robot
@@ -11,7 +11,7 @@ POST API Version - Method not implemented
... Test title: POST API version - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -23,7 +23,7 @@ GET API Version
... Test title: GET API Version
... Test objective: The objective is to test that GET method successfully return ApiVersionInformation
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -36,7 +36,7 @@ PUT API Version - Method not implemented
... Test title: PUT API Version - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -48,7 +48,7 @@ PATCH API Version - Method not implemented
... Test title: PATCH API Version - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -60,7 +60,7 @@ DELETE API Version - Method not implemented
... Test title: DELETE API Version - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -72,7 +72,7 @@ POST API Version with apiMajorVerion - Method not implemented
... Test title: POST API version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -84,7 +84,7 @@ GET API Version with apiMajorVerion
... Test title: GET API Version with apiMajorVerion
... Test objective: The objective is to test that GET method successfully return ApiVersionInformation
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -97,7 +97,7 @@ PUT API Version with apiMajorVerion - Method not implemented
... Test title: PUT API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -109,7 +109,7 @@ PATCH API Version with apiMajorVerion - Method not implemented
... Test title: PATCH API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -121,7 +121,7 @@ DELETE API Version with apiMajorVerion - Method not implemented
... Test title: DELETE API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL009/NFVManoConfigurationAndInformationManagement-API/ChangeInterfaceStateTask.robot b/SOL009/NFVManoConfigurationAndInformationManagement-API/ChangeInterfaceStateTask.robot
index a094501817201c50f33dcfb26a08c03f45565897..2d4a64d775a6568680b32f4cad71a8d0d4ed16a8 100644
--- a/SOL009/NFVManoConfigurationAndInformationManagement-API/ChangeInterfaceStateTask.robot
+++ b/SOL009/NFVManoConfigurationAndInformationManagement-API/ChangeInterfaceStateTask.robot
@@ -13,7 +13,7 @@ POST Change interface state task
... Test title: POST Change interface state task
... Test objective: The objective is send put request to change the state of the NFV-MANO service interface produced by the NFV-MANO functional entity
... Pre-conditions: none
- ... Reference: clause 5.5.12.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.12.3.1 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: interface status changed
@@ -27,7 +27,7 @@ POST Change interface state task - Conflict
... Test title: POST Change interface state task - Conflict
... Test objective: The objective is to test that request to cchange the state of the NFV-MANO service interface produced by the NFV-MANO functional entity failed due to a conflict with the state of the NFV-MANO entity resource and perform the JSON schema validation of the failed operation HTTP response.
... Pre-conditions: none
- ... Reference: clause 5.5.12.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.12.3.1 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -40,7 +40,7 @@ GET Change interface state task - Method not implemented
... Test title: GET Change interface state task - Method not implemented
... Test objective: The objective is to test that GET method is not allowed to retrieve the changed state of the NFV-MANO functional entity application.
... Pre-conditions: none
- ... Reference: clause 5.5.12.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.12.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -52,7 +52,7 @@ PUT Change interface state task - Conflict - Method not implemented
... Test title: PUT Change interface state task - Conflict - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to update the changed state of the NFV-MANO functional entity application.
... Pre-conditions: none
- ... Reference: clause 5.5.12.3.3 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.12.3.3 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -64,7 +64,7 @@ PATCH Change interface state task - Conflict - Method not implemented
... Test title: PATCH Change interface state task - Conflict - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update the changed state of the NFV-MANO functional entity application.
... Pre-conditions: none
- ... Reference: clause 5.5.12.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.12.3.4 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -76,7 +76,7 @@ DELETE Change interface state task - Conflict - Method not implemented
... Test title: DELETE Change interface state task - Conflict - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to delete the changed state of the NFV-MANO functional entity application.
... Pre-conditions: none
- ... Reference: clause 5.5.12.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.12.3.5 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL009/NFVManoConfigurationAndInformationManagement-API/ChangeNFVMANOEntityStateTask.robot b/SOL009/NFVManoConfigurationAndInformationManagement-API/ChangeNFVMANOEntityStateTask.robot
index 30f968022f43ab20478ed280b8ed99fdc59e422d..23655cdcc7b4784872be30853b21dc4ee3868be2 100644
--- a/SOL009/NFVManoConfigurationAndInformationManagement-API/ChangeNFVMANOEntityStateTask.robot
+++ b/SOL009/NFVManoConfigurationAndInformationManagement-API/ChangeNFVMANOEntityStateTask.robot
@@ -12,7 +12,7 @@ POST NFV-MANO functional entity application state change
... Test title: POST NFV-MANO functional entity application state change
... Test objective: The objective is to request state change of the NFV-MANO functional entity application.
... Pre-conditions: none
- ... Reference: clause 5.5.7.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.7.3.1 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: entity status changed
@@ -26,7 +26,7 @@ POST NFV-MANO functional entity application state change - Conflict
... Test title: POST NFV-MANO functional entity application state change - Conflict
... Test objective: The objective is to test that request to change the state of the NFV-MANO functional entity application fails due to a conflict with the state of the NFV-MANO entity resource and perform the JSON schema validation of the failed operation HTTP response.
... Pre-conditions: none
- ... Reference: clause 5.5.7.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.7.3.1 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -39,7 +39,7 @@ GET NFV-MANO functional entity application state change - Method not implemented
... Test title: GET NFV-MANO functional entity application state change - Method not implemented
... Test objective: The objective is to test that GET method is not allowed to retrieve the changed state of the NFV-MANO functional entity application.
... Pre-conditions: none
- ... Reference: clause 5.5.7.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.7.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -51,7 +51,7 @@ PUT NFV-MANO functional entity application state change - Method not implemented
... Test title: PUT NFV-MANO functional entity application state change - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to update the changed state of the NFV-MANO functional entity application.
... Pre-conditions: none
- ... Reference: clause 5.5.7.3.3 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.7.3.3 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -63,7 +63,7 @@ PATCH NFV-MANO functional entity application state change - Method not implement
... Test title: PATCH NFV-MANO functional entity application state change - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update the changed state of the NFV-MANO functional entity application.
... Pre-conditions: none
- ... Reference: clause 5.5.7.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.7.3.4 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -75,7 +75,7 @@ DELETE NFV-MANO functional entity application state change - Method not implemen
... Test title: DELETE NFV-MANO functional entity application state change - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to delete the changed state of the NFV-MANO functional entity application.
... Pre-conditions: none
- ... Reference: clause 5.5.7.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.7.3.5 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL009/NFVManoConfigurationAndInformationManagement-API/ChangeStateOperationOccurrences.robot b/SOL009/NFVManoConfigurationAndInformationManagement-API/ChangeStateOperationOccurrences.robot
index 3b3086b040c313773db3db74ce1aabce143f7937..bb0c97c0097b529ad3c24b3ed02e35b3607029a6 100644
--- a/SOL009/NFVManoConfigurationAndInformationManagement-API/ChangeStateOperationOccurrences.robot
+++ b/SOL009/NFVManoConfigurationAndInformationManagement-API/ChangeStateOperationOccurrences.robot
@@ -13,7 +13,7 @@ POST Change State Operation Occurrences - Method not implemented
... Test title: POST Change State Operation Occurrences - Method not implemented
... Test objective: The objective is to test that POST method is not implemeted.
... Pre-conditions: none
- ... Reference: clause 5.5.8.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.8.3.1 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -25,7 +25,7 @@ GET Change State Operation Occurrences
... Test title: GET Change State Operation Occurrences
... Test objective: The objective is to query status information about multiple change state operation occurrences, and perform the JSON schema validation of the HTTP response.
... Pre-conditions: none
- ... Reference: clause 5.5.8.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.8.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -38,7 +38,7 @@ GET Change State Operation Occurrences - invalid attribute-based filter
... Test title: GET Change State Operation Occurrences - invalid attribute-based filter
... Test objective: The objective is to test that the retrieval of Change State Operation Occurrences fails when using invalid attribute-based filter, and perform the JSON schema validation of the failed operation HTTP response.
... Pre-conditions: none
- ... Reference: clause 5.5.8.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.8.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -51,7 +51,7 @@ GET Change State Operation Occurrences - invalid attribute selector
... Test title: GET Change State Operation Occurrences - invalid attribute selector
... Test objective: The objective is to test that the retrieval of Change State Operation Occurrences fails when using invalid attribute selector, and perform the JSON schema validation of the failed operation HTTP response.
... Pre-conditions: none
- ... Reference: clause 5.5.8.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.8.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -64,7 +64,7 @@ GET Change State Operation Occurrences - Bad Request Response too Big
... Test title: GET Change State Operation Occurrences - Bad Request Response too Big
... Test objective: The objective is to test that the retrieval of Change State Operation Occurrences fails when response is too big, and perform the JSON schema validation of the failed operation HTTP response.
... Pre-conditions: none
- ... Reference: clause 5.5.8.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.8.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -77,7 +77,7 @@ GET Change State Operation Occurrences with attribute-based filter
... Test title: GET Change State Operation Occurrences with attribute-based filter
... Test objective: The objective is to query status information about multiple change state operation occurrences with attribute filters, and perform the JSON schema validation of the HTTP response.
... Pre-conditions: none
- ... Reference: clause 5.5.8.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.8.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -90,7 +90,7 @@ GET Change State Operation Occurrences with "all_fields" attribute selector
... Test title: GET Change State Operation Occurrences with "all_fields" attribute selector
... Test objective: The objective is to retrieve Change State Operation Occurrences with "all_fields" attribute selector, and perform the JSON schema validation of the HTTP response.
... Pre-conditions: none
- ... Reference: clause 5.5.8.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.8.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -103,7 +103,7 @@ GET Change State Operation Occurrences with "exclude_default" attribute selector
... Test title: GET Change State Operation Occurrence with "exclude_default" attribute selector
... Test objective: The objective is to retrieve Change State Operation Occurrence with "exclude_default" attribute selector, and perform the JSON schema validation of the HTTP response.
... Pre-conditions: none
- ... Reference: clause 5.5.8.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.8.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -116,7 +116,7 @@ GET Change State Operation Occurrences with "fields" attribute selector
... Test title: GET Change State Operation Occurrences with "fields" attribute selector
... Test objective: The objective is to retrieve Change State Operation Occurrences with fields attribute selector, and perform the JSON schema validation of the HTTP response.
... Pre-conditions: none
- ... Reference: clause 5.5.8.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.8.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -129,7 +129,7 @@ GET Change State Operation Occurrences with "exclude_fields" attribute selector
... Test title: GET Change State Operation Occurrences with "exclude_fields" attribute selector
... Test objective: The objective is to retrieve Change State Operation Occurrences with "exclude_fields" attribute selector, and perform the JSON schema validation of the HTTP response.
... Pre-conditions: none
- ... Reference: clause 5.5.8.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.8.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -142,7 +142,7 @@ GET Change State Operation Occurrences with Paged Response
... Test title: GET Change State Operation Occurrence with Paged Response
... Test objective: The objective is to query Change State Operation Occurrence to get Paged Response.
... Pre-conditions: none
- ... Reference: clause 5.5.8.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.8.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -155,7 +155,7 @@ GET Change State Operation Occurrences with "fields" and "exclude_default" attri
... Test title: GET Change State Operation Occurrences with "fields" and "exclude_default" attribute selector
... Test objective: The objective is to retrieve Change State Operation Occurrences with fields and exclude default attribute selector, and perform the JSON schema validation of the HTTP response.
... Pre-conditions: none
- ... Reference: clause 5.5.8.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.8.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -168,7 +168,7 @@ PUT Change State Operation Occurrences - Method not implemented
... Test title: PUT Change State Operation Occurrences - Method not implemented
... Test objective: The objective is to test that PUT method is not implemeted.
... Pre-conditions: none
- ... Reference: clause 5.5.8.3.3 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.8.3.3 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -180,7 +180,7 @@ PATCH Change State Operation Occurrences - Method not implemented
... Test title: PATCH Change State Operation Occurrences - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemeted.
... Pre-conditions: none
- ... Reference: clause 5.5.8.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.8.3.4 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -192,7 +192,7 @@ DELETE Change State Operation Occurrences - Method not implemented
... Test title: DELETE Change State Operation Occurrences - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemeted.
... Pre-conditions: none
- ... Reference: clause 5.5.8.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.8.3.5 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL009/NFVManoConfigurationAndInformationManagement-API/IndividualNFVMANOServiceInterface.robot b/SOL009/NFVManoConfigurationAndInformationManagement-API/IndividualNFVMANOServiceInterface.robot
index 56c50789c9b59d3650280a7681f7baa8ecdb98a9..bd06a94f91d5d79abbf4000aae3c630f7adbb1b2 100644
--- a/SOL009/NFVManoConfigurationAndInformationManagement-API/IndividualNFVMANOServiceInterface.robot
+++ b/SOL009/NFVManoConfigurationAndInformationManagement-API/IndividualNFVMANOServiceInterface.robot
@@ -13,7 +13,7 @@ POST Individual NFV-MANO Service Interface - Method not implemented
... Test title: POST Individual NFV-MANO Service Interface - Method not implemented
... Test objective: The objective is to test that POST method is not implemeted.
... Pre-conditions: none
- ... Reference: clause 5.5.11.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.11.3.1 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -25,7 +25,7 @@ GET Individual NFV-MANO Service Interface
... Test title: GET Individual NFV-MANO Service Interface
... Test objective: The objective is to query status information about an NFV-MANO service interface of the producer NFV-MANO functional entity by reading an "Individual NFV-MANO service interface" resource, and perform the JSON schema validation of the HTTP response.
... Pre-conditions: none
- ... Reference: clause 5.5.11.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.11.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -38,7 +38,7 @@ GET Individual NFV-MANO Service Interface - Not Found
... Test title: GET Individual NFV-MANO Service Interface - Not Found
... Test objective: The objective is to test the retrieval of information about an NFV-MANO service interface of the producer NFV-MANO functional entity by reading an "Individual NFV-MANO service interface" resource fails when the resource is not present.
... Pre-conditions: none
- ... Reference: clause 5.5.11.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.11.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -51,7 +51,7 @@ PUT Individual NFV-MANO Service Interface - Method not implemented
... Test title: PUT Individual NFV-MANO Service Interface - Method not implemented
... Test objective: The objective is to test that PUT method is not implemeted.
... Pre-conditions: none
- ... Reference: clause 5.5.11.3.3 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.11.3.3 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -63,7 +63,7 @@ PATCH Individual NFV-MANO Service Interface
... Test title: PATCH Individual NFV-MANO Service Interface
... Test objective: This method modifies the Individual NFV-MANO Service Interface resource, and perform the JSON schema validation of the HTTP response.
... Pre-conditions: Individual NFV-MANO Service Interface resource is already created.
- ... Reference: clause 5.5.11.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.11.3.4 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: The Individual NFV-MANO Service Interface is modified by the operation
@@ -76,7 +76,7 @@ PATCH Individual NFV-MANO Service Interface - Conflict
... Test title: PATCH Individual NFV-MANO Service Interface - Conflict
... Test objective: The objective is to test that the modification of the Individual NFV-MANO Service Interface resource failed due to a conflict with the state of the Individual NFV-MANO Service Interface resource and perform the JSON schema validation of the failed operation HTTP response.
... Pre-conditions: Individual NFV-MANO Service Interface resource is already created.
- ... Reference: clause 5.5.11.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.11.3.4 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: The Individual NFV-MANO Service Interface is not modified by the operation
@@ -89,7 +89,7 @@ PATCH Individual NFV-MANO Service Interface - PreCondition Failed
... Test title: PATCH Individual NFV-MANO Service Interface - PreCondition Failed
... Test objective: The objective is to test that the modification of the Individual NFV-MANO Service Interface resource failed because precondition given in an HTTP request header is not fulfilled and perform the JSON schema validation of the failed operation HTTP response.
... Pre-conditions: Individual NFV-MANO Service Interface resource is already created.
- ... Reference: clause 5.5.11.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.11.3.4 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: The Individual NFV-MANO Service Interface is not modified by the operation
@@ -102,7 +102,7 @@ DELETE Individual NFV-MANO Service Interface - Method not implemented
... Test title: DELETE Individual NFV-MANO Service Interface - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemeted.
... Pre-conditions: none
- ... Reference: clause 5.5.11.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.11.3.5 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL009/NFVManoConfigurationAndInformationManagement-API/IndividualPeerEntity.robot b/SOL009/NFVManoConfigurationAndInformationManagement-API/IndividualPeerEntity.robot
index b084730e74e414b7cc9e939d2b82f6fabf7c6208..1e4bb41f4897835639183d6e5509d8e9ea269e01 100644
--- a/SOL009/NFVManoConfigurationAndInformationManagement-API/IndividualPeerEntity.robot
+++ b/SOL009/NFVManoConfigurationAndInformationManagement-API/IndividualPeerEntity.robot
@@ -13,7 +13,7 @@ POST Individual Peer Entity - Method not implemented
... Test title: POST Individual Peer Entity - Method not implemented
... Test objective: The objective is to test that POST method is not implemeted.
... Pre-conditions: none
- ... Reference: clause 5.5.14.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.14.3.1 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -25,7 +25,7 @@ GET Individual Peer Entity
... Test title: GET Individual Peer Entity
... Test objective: The objective is to retrieves information and configuration hold in the producer NFV-MANO functional entity with regards to a peer entity by reading an individual peer entity resource
... Pre-conditions: none
- ... Reference: clause 5.5.14.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.14.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -38,7 +38,7 @@ GET Individual Peer Entity - Not Found
... Test title: GET Individual Peer Entity - Not Found
... Test objective: The objective is to test the retrieval of information and configuration hold in the producer NFV-MANO functional entity with regards to a peer entity by reading an individual peer entity resource fails when the resource is not present.
... Pre-conditions: none
- ... Reference: clause 5.5.14.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.14.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -50,7 +50,7 @@ PUT Individual Peer Entity - Method not implemented
... Test title: PUT Individual Peer Entity - Method not implemented
... Test objective: The objective is to test that PUT method is not implemeted.
... Pre-conditions: none
- ... Reference: clause 5.5.14.3.3 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.14.3.3 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -62,20 +62,20 @@ PATCH Individual Peer Entity
... Test title: PATCH Individual Peer Entity
... Test objective: This method modifies configuration and information of the producer NFV-MANO functional entity with regards to a peer functional entity by updating the corresponding "Individual peer entity" resource.
... Pre-conditions: At least one Peer Entity resource is created
- ... Reference: clause 5.5.14.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.14.3.4 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: Peer Entity Resource is modified by the operation
Send Patch request for Individual Peer Entity
Check HTTP Response Status Code Is 200
- Check HTTP Response Body Json Schema Is ManoServiceInterfaceModifications
+ Check HTTP Response Body Json Schema Is PeerEntityConfigModifications
PATCH Individual Peer Entity - Conflict
[Documentation] Test ID: 8.3.1.9.6
... Test title: PATCH Individual Peer Entity - Conflict
... Test objective: The objective is to test that the modification of configuration and information of the producer NFV-MANO functional entity with regards to a peer functional entity by updating the corresponding "Individual peer entity" resource failed due to a conflict with the state of the Individual Peer Entity resource and perform the JSON schema validation of the failed operation HTTP response.
... Pre-conditions: At least one Peer Entity resource is created
- ... Reference: clause 5.5.14.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.14.3.4 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: Peer Entity Resource is not modified by the operation
@@ -88,7 +88,7 @@ PATCH Individual Peer Entity - PreCondition Failed
... Test title: PATCH Individual Peer Entity - PreCondition Failed
... Test objective: The objective is to test that the modification of the Individual Peer Entity resource failed because precondition given in an HTTP request header is not fulfilled and perform the JSON schema validation of the failed operation HTTP response.
... Pre-conditions: At least one Peer Entity resource is created
- ... Reference: clause 5.5.14.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.14.3.4 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: Peer Entity Resource is not modified by the operation
@@ -101,7 +101,7 @@ DELETE Individual Peer Entity - Method not implemented
... Test title: DELETE Individual Peer Entity - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemeted.
... Pre-conditions: none
- ... Reference: clause 5.5.14.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.14.3.5 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL009/NFVManoConfigurationAndInformationManagement-API/IndividualStateChangeOperationOccurrence.robot b/SOL009/NFVManoConfigurationAndInformationManagement-API/IndividualStateChangeOperationOccurrence.robot
index a60ab0d9eaf6bde2a3099509b1bffd0f2926a6c6..9939a17006928baa1fb72057caef3103e61aa781 100644
--- a/SOL009/NFVManoConfigurationAndInformationManagement-API/IndividualStateChangeOperationOccurrence.robot
+++ b/SOL009/NFVManoConfigurationAndInformationManagement-API/IndividualStateChangeOperationOccurrence.robot
@@ -13,7 +13,7 @@ POST Individual Change State Operation Occurrence - Method not implemented
... Test title: POST Individual Change State Operation Occurrence - Method not implemented
... Test objective: The objective is to test that POST method is not implemeted.
... Pre-conditions: none
- ... Reference: clause 5.5.9.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.9.3.1 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -25,7 +25,7 @@ GET Individual Change State Operation Occurrence
... Test title: GET Individual Change State Operation Occurrence
... Test objective: The objective is to query status information about Individual change state operation occurrence.
... Pre-conditions: none
- ... Reference: clause 5.5.9.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.9.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -38,7 +38,7 @@ GET Individual Change State Operation Occurrence - Not Found
... Test title: GET Individual Change State Operation Occurrence - Not Found
... Test objective: The objective is to test the retrieval of information about individual change state operation occurence fails when the resource is not present.
... Pre-conditions: none
- ... Reference: clause 5.5.9.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.9.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -50,7 +50,7 @@ PUT Individual Change State Operation Occurrence - Method not implemented
... Test title: PUT Individual Change State Operation Occurrence - Method not implemented
... Test objective: The objective is to test that PUT method is not implemeted.
... Pre-conditions: none
- ... Reference: clause 5.5.9.3.3 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.9.3.3 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -62,7 +62,7 @@ PATCH Individual Change State Operation Occurrence - Method not implemented
... Test title: PATCH Individual Change State Operation Occurrence - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemeted.
... Pre-conditions: none
- ... Reference: clause 5.5.9.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.9.3.4 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -74,7 +74,7 @@ DELETE Individual Change State Operation Occurrence - Method not implemented
... Test title: DELETE Individual Change State Operation Occurrence - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemeted.
... Pre-conditions: none
- ... Reference: clause 5.5.9.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.9.3.5 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL009/NFVManoConfigurationAndInformationManagement-API/IndividualSubscription.robot b/SOL009/NFVManoConfigurationAndInformationManagement-API/IndividualSubscription.robot
index f406fad84bf4c81ee0dfa66f4f241a3775172973..d2b46bdd3d9c328a90164176f8f3b01e39496b76 100644
--- a/SOL009/NFVManoConfigurationAndInformationManagement-API/IndividualSubscription.robot
+++ b/SOL009/NFVManoConfigurationAndInformationManagement-API/IndividualSubscription.robot
@@ -12,7 +12,7 @@ GET Individual Subscription
... Test title: GET Individual Subscription
... Test objective: The objective is to test the retrieval of individual subscription and perform a JSON schema and content validation of the returned subscription data structure
... Pre-conditions: At least one subscription is available in the NFV-MANO.
- ... Reference: clause 5.5.5.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.5.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -26,7 +26,7 @@ GET Individual Subscription - invalid resource identifier
... Test title: GET Individual Subscription - invalid resource identifier
... Test objective: The objective is to test that the retrieval of an individual subscription fails when using an invalid resource identifier
... Pre-conditions: At least one subscription is available in the NFV-MANO.
- ... Reference: clause 5.5.5.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.5.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -38,7 +38,7 @@ DELETE Individual Subscription
... Test title: DELETE Individual Subscription
... Test objective: The objective is to test the deletion of an individual subscription
... Pre-conditions: At least one subscription is available in the NFV-MANO.
- ... Reference: clause 5.5.5.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.5.3.5 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: The resource is not available anymore in the NFV-MANO
@@ -51,7 +51,7 @@ DELETE Individual Subscription - invalid resource identifier
... Test title: DELETE Individual Subscription - invalid resource identifier
... Test objective: The objective is to test that the deletion of an individual subscription fails when using an invalid resource identifier
... Pre-conditions: At least one subscription is available in the NFV-MANO.
- ... Reference: clause 5.5.5.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.5.3.5 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -63,7 +63,7 @@ POST Individual Subscription - Method not implemented
... Test title: POST Individual Subscription - Method not implemented
... Test objective: The objective is to test that POST method is not allowed to create a new Subscription
... Pre-conditions: none
- ... Reference: clause 5.5.5.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.5.3.1 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -75,7 +75,7 @@ PUT Individual Subscription - Method not implemented
... Test title: PUT Individual Subscription - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to update an existing subscription
... Pre-conditions: none
- ... Reference: clause 5.5.5.3.3 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.5.3.3 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -87,7 +87,7 @@ PATCH Individual Subscription - Method not implemented
... Test title: PATCH Individual Subscription - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to modify an existing subscription
... Pre-conditions: none
- ... Reference: clause 5.5.5.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.5.3.4 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL009/NFVManoConfigurationAndInformationManagement-API/NFVMANOEntity.robot b/SOL009/NFVManoConfigurationAndInformationManagement-API/NFVMANOEntity.robot
index 832156bdf9c4d40ec39509fdffcf086ac7315d0e..05fe34388ca070cf589850d3d919e7c434dc6ad0 100644
--- a/SOL009/NFVManoConfigurationAndInformationManagement-API/NFVMANOEntity.robot
+++ b/SOL009/NFVManoConfigurationAndInformationManagement-API/NFVMANOEntity.robot
@@ -13,7 +13,7 @@ POST NFV-MANO entity - Method not implemented
... Test title: POST NFV-MANO entity - Method not implemented
... Test objective: The objective is to test that POST method is not allowed to create an NFV-MANO Entity.
... Pre-conditions: none
- ... Reference: clause 5.5.3.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.3.3.1 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -25,7 +25,7 @@ GET NFV-MANO entity
... Test title: Get NFV-MANO entity
... Test objective: The objective is to test the retrieval of information about an NFV-MANO functional entity by reading the NFV-MANO entity resource and perform a JSON schema and content validation of the collected job data structure.
... Pre-conditions: none
- ... Reference: clause 5.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -38,7 +38,7 @@ GET NFV-MANO entity - Not Found
... Test title: Get NFV-MANO entity - Not Found
... Test objective: The objective is to test the retrieval of information about an NFV-MANO functional entity by reading the NFV-MANO entity resource fails when the resource is not present.
... Pre-conditions: none
- ... Reference: clause 5.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -50,7 +50,7 @@ PUT NFV-MANO entity - Method not implemented
... Test title: PUT NFV-MANO entity - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to update an NFV-MANO Entity.
... Pre-conditions: none
- ... Reference: clause 5.5.3.3.3 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.3.3.3 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -62,7 +62,7 @@ PATCH NFV-MANO entity
... Test title: PATCH NFV-MANO entity
... Test objective: The objective is to test that PATCH method modifies the NFV-MANO entity resource and perform a JSON schema and content validation of the modified response.
... Pre-conditions: NFV-MANO entity resource is already created.
- ... Reference: clause 5.5.3.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.3.3.4 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: The NFV-MANO entity is modified by the operation
@@ -75,7 +75,7 @@ PATCH NFV-MANO entity - Conflict
... Test title: PATCH NFV-MANO entity - Conflict
... Test objective: The objective is to test that the modification of the NFV-MANO entity resource failed due to a conflict with the state of the NFV-MANO entity resource and perform the JSON schema validation of the failed operation HTTP response.
... Pre-conditions: NFV-MANO entity resource is already created.
- ... Reference: clause 5.5.3.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.3.3.4 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: The NFV-MANO entity is not modified by the operation
@@ -88,7 +88,7 @@ PATCH NFV-MANO entity - PreCondition Failed
... Test title: PATCH NFV-MANO entity - PreCondition Failed
... Test objective: The objective is to test that the modification of the NFV-MANO entity resource failed because precondition given in an HTTP request header is not fulfilled and perform the JSON schema validation of the failed operation HTTP response.
... Pre-conditions: NFV-MANO entity resource is already created.
- ... Reference: clause 5.5.3.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.3.3.4 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: The NFV-MANO entity is not modified by the operation
@@ -101,7 +101,7 @@ DELETE NFV-MANO entity - Method not implemented
... Test title: DELETE NFV-MANO entity - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to delete an NFV-MANO Entity.
... Pre-conditions: none
- ... Reference: clause 5.5.3.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.3.3.5 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL009/NFVManoConfigurationAndInformationManagement-API/NFVMANOServiceInterfaces.robot b/SOL009/NFVManoConfigurationAndInformationManagement-API/NFVMANOServiceInterfaces.robot
index bd7c62ae2546399fb8ce2aab1d6966b82ceb2dcb..9f4f28d151d28ca1e1faed3e5905cadde1bc4ccf 100644
--- a/SOL009/NFVManoConfigurationAndInformationManagement-API/NFVMANOServiceInterfaces.robot
+++ b/SOL009/NFVManoConfigurationAndInformationManagement-API/NFVMANOServiceInterfaces.robot
@@ -13,7 +13,7 @@ POST NFV-MANO Service Interfaces - Method not implemented
... Test title: POST NFV-MANO Service Interfaces - Method not implemented
... Test objective: The objective is to test that POST method is not implemeted.
... Pre-conditions: none
- ... Reference: clause 5.5.10.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.10.3.1 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -25,7 +25,7 @@ GET NFV-MANO Service Interfaces
... Test title: GET NFV-MANO Service Interfaces
... Test objective: The objective is to query status information about multiple NFV-MANO service interfaces of the NFV-MANO functional entity, and perform the JSON schema validation of the HTTP response.
... Pre-conditions: none
- ... Reference: clause 5.5.10.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.10.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -38,7 +38,7 @@ GET NFV-MANO Service Interfaces - invalid attribute-based filter
... Test title: GET NFV-MANO Service Interfaces - invalid attribute-based filter
... Test objective: The objective is to test that the retrieval of NFV-MANO Service Interfaces fails when using invalid attribute-based filter, and perform the JSON schema validation of the failed operation HTTP response.
... Pre-conditions: none
- ... Reference: clause 5.5.10.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.10.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -51,7 +51,7 @@ GET NFV-MANO Service Interfaces - invalid attribute selector
... Test title: GET NFV-MANO Service Interfaces - invalid attribute selector
... Test objective: The objective is to test that the retrieval of NFV-MANO Service Interfaces fails when using invalid attribute selector, and perform the JSON schema validation of the failed operation HTTP response.
... Pre-conditions: none
- ... Reference: clause 5.5.10.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.10.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -64,7 +64,7 @@ GET NFV-MANO Service Interfaces - Bad Request Response too Big
... Test title: GET NFV-MANO Service Interfaces - Bad Request Response too Big
... Test objective: The objective is to test that the retrieval of NFV-MANO Service Interfaces fails when response is too big, and perform the JSON schema validation of the failed operation HTTP response.
... Pre-conditions: none
- ... Reference: clause 5.5.10.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.10.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -77,7 +77,7 @@ GET NFV-MANO Service Interfaces with attribute-based filter
... Test title: GET NFV-MANO Service Interfaces with attribute-based filter
... Test objective: The objective is to query status information about multiple NFV-MANO service interfaces of the NFV-MANO functional entities with attribute filters, and perform the JSON schema validation of the HTTP response.
... Pre-conditions: none
- ... Reference: clause 5.5.10.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.10.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -90,7 +90,7 @@ GET NFV-MANO Service Interfaces with "all_fields" attribute selector
... Test title: GET NFV-MANO Service Interface with "all_fields" attribute selector
... Test objective: The objective is to retrieve NFV-MANO Service Interfaces with "all_fields" attribute selector, and perform the JSON schema validation of the HTTP response.
... Pre-conditions: none
- ... Reference: clause 5.5.10.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.10.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -103,7 +103,7 @@ GET NFV-MANO Service Interfaces with "exclude_default" attribute selector
... Test title: GET NFV-MANO Service Interfaces with "exclude_default" attribute selector
... Test objective: The objective is to retrieve NFV-MANO Service Interfaces with "exclude_default" attribute selector, and perform the JSON schema validation of the HTTP response.
... Pre-conditions: none
- ... Reference: clause 5.5.10.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.10.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -116,7 +116,7 @@ GET NFV-MANO Service Interfaces with "fields" attribute selector
... Test title: GET NFV-MANO Service Interfaces with "fields" attribute selector
... Test objective: The objective is to retrieve NFV-MANO Service Interfaces with fields attribute selector, and perform the JSON schema validation of the HTTP response.
... Pre-conditions: none
- ... Reference: clause 5.5.10.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.10.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -129,7 +129,7 @@ GET NFV-MANO Service Interfaces with "exclude_fields" attribute selector
... Test title: GET NFV-MANO Service Interfaces with "exclude_fields" attribute selector
... Test objective: The objective is to retrieve NFV-MANO Service Interfaces with "exclude_fields" attribute selector, and perform the JSON schema validation of the HTTP response.
... Pre-conditions: none
- ... Reference: clause 5.5.10.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.10.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -142,7 +142,7 @@ GET NFV-MANO Service Interfaces with "exclude_default" and "fields" attribute se
... Test title: GET NFV-MANO Service Interfaces with "exclude_default" and "fields" attribute selector
... Test objective: The objective is to retrieve NFV-MANO Service Interfaces with "exclude_default" and "fields" attribute selector, and perform the JSON schema validation of the HTTP response.
... Pre-conditions: none
- ... Reference: clause 5.5.10.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.10.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -155,7 +155,7 @@ GET NFV-MANO Service Interfaces with Paged Response
... Test title: GET NFV-MANO Service Interfaces with Paged Response
... Test objective: The objective is to query NFV-MANO Service Interface to get Paged Response.
... Pre-conditions: none
- ... Reference: clause 5.5.10.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.10.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -168,7 +168,7 @@ PUT NFV-MANO Service Interfaces - Method not implemented
... Test title: PUT NFV-MANO Service Interfaces - Method not implemented
... Test objective: The objective is to test that PUT method is not implemeted.
... Pre-conditions: none
- ... Reference: clause 5.5.10.3.3 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.10.3.3 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -180,7 +180,7 @@ PATCH NFV-MANO Service Interfaces - Method not implemented
... Test title: PATCH NFV-MANO Service Interfaces - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemeted.
... Pre-conditions: none
- ... Reference: clause 5.5.10.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.10.3.4 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -192,7 +192,7 @@ DELETE NFV-MANO Service Interfaces - Method not implemented
... Test title: DELETE NFV-MANO Service Interfaces - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemeted.
... Pre-conditions: none
- ... Reference: clause 5.5.10.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.10.3.5 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL009/NFVManoConfigurationAndInformationManagement-API/NotificationEndpoint.robot b/SOL009/NFVManoConfigurationAndInformationManagement-API/NotificationEndpoint.robot
index b51c7d3964ee3b7fa94d9811c375a2f49996c762..f12d35bf0ce286c13c1d412f1d734e314068adaf 100644
--- a/SOL009/NFVManoConfigurationAndInformationManagement-API/NotificationEndpoint.robot
+++ b/SOL009/NFVManoConfigurationAndInformationManagement-API/NotificationEndpoint.robot
@@ -13,7 +13,7 @@ Information Changed Notification
... Test title: Information Changed Notification
... Test objective: The objective is to test that Information Changed Notification is delivered with success to the notification consumer
... Pre-conditions: A subscription for information availability notification is available in the NFV-MANO.
- ... Reference: clause 5.5.6.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.6.3.1 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
@@ -25,7 +25,7 @@ Change State Notification
... Test title: Change State Notification
... Test objective: The objective is to test that Change State Notification is delivered with success to the notification consumer
... Pre-conditions: A subscription for change state notification is available in the NFV-MANO.
- ... Reference: clause 5.5.6.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.6.3.1 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
diff --git a/SOL009/NFVManoConfigurationAndInformationManagement-API/Notifications.robot b/SOL009/NFVManoConfigurationAndInformationManagement-API/Notifications.robot
index 592bf0c284438941ab0047808014c6b8a5f7550e..60541f73463663ff3249122511ebec4d2c565bd3 100644
--- a/SOL009/NFVManoConfigurationAndInformationManagement-API/Notifications.robot
+++ b/SOL009/NFVManoConfigurationAndInformationManagement-API/Notifications.robot
@@ -16,7 +16,7 @@ Information Changed Notification
... Test title: Information Changed Notification
... Test objective: The objective is to test the dispatch of Information Changed Notification when configuration or information is changed in the NFV-MANO, and perform a JSON schema and content validation of the delivered notification. The action that triggers the notification under test is an explicit test step, but it is not performed by the test system.
... Pre-conditions: A subscription for information availability notifications is available in the NFV-MANO.
- ... Reference: clause 5.5.6.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.6.3.1 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -29,7 +29,7 @@ Change State Notification
... Test title: Change State Notification
... Test objective: The objective is to test the dispatch of Change State Notification when state changes of the NFV-MANO functional entity and its managed objects, and perform a JSON schema and content validation of the delivered notification. The action that triggers the notification under test is an explicit test step, but it is not performed by the test system.
... Pre-conditions: A performance job is created, and a state change subscription is available in the NFV-MANO.
- ... Reference: clause 5.5.6.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.6.3.1 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANOz
... Applicability: none
... Post-Conditions: none
diff --git a/SOL009/NFVManoConfigurationAndInformationManagement-API/PeerEntities.robot b/SOL009/NFVManoConfigurationAndInformationManagement-API/PeerEntities.robot
index 2a62dccfc85ca2e2199ac4a5bb07ac648b22f4c6..d8f9a0f6a0ed7af3fa0f2f4d06405ebe42ba8e37 100644
--- a/SOL009/NFVManoConfigurationAndInformationManagement-API/PeerEntities.robot
+++ b/SOL009/NFVManoConfigurationAndInformationManagement-API/PeerEntities.robot
@@ -13,7 +13,7 @@ POST Peer Entity
... Test title: POST Peer Entity
... Test objective: The objective is to creates in the producer NFV-MANO functional entity a new peer entity resource which contains configuration and information with regards to the peer functional entity and perform the JSON schema validation of the returned job data structure.
... Pre-conditions: none
- ... Reference: clause 5.5.13.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.13.3.1 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: Peer Entity is created
@@ -28,7 +28,7 @@ GET Peer Entities
... Test title: GET Peer Entities
... Test objective: The objective is to query information and configuration in the producer NFV-MANO functional entity with regards to multiple peer entities, and perform the JSON schema validation of the returned job data structure.
... Pre-conditions: At least one Peer Entity is already created.
- ... Reference: clause 5.5.13.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.13.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -41,7 +41,7 @@ GET Peer Entities - invalid attribute-based filter
... Test title: GET Peer Entities - invalid attribute-based filter
... Test objective: The objective is to test that the retrieval of information and configuration in the producer NFV-MANO functional entity with regards to multiple peer entities fails when using invalid attribute-based filter, and perform the JSON schema validation of the failed operation HTTP response.
... Pre-conditions: At least one Peer Entity is already created.
- ... Reference: clause 5.5.13.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.13.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -54,7 +54,7 @@ GET Peer Entities - invalid attribute selector
... Test title: GET Peer Entities - invalid attribute selector
... Test objective: The objective is to test that the retrieval of information and configuration in the producer NFV-MANO functional entity with regards to multiple peer entities fails when using invalid attribute selector, and perform the JSON schema validation of the failed operation HTTP response.
... Pre-conditions: At least one Peer Entity is already created.
- ... Reference: clause 5.5.13.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.13.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -67,7 +67,7 @@ GET Peer Entities - Bad Request Response too Big
... Test title: GET Peer Entities - Bad Request Response too Big
... Test objective: The objective is to test that the retrieval of information and configuration in the producer NFV-MANO functional entity with regards to multiple peer entities fails when response is too big, and perform the JSON schema validation of the failed operation HTTP response.
... Pre-conditions: At least one Peer Entity is already created.
- ... Reference: clause 5.5.13.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.13.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -80,7 +80,7 @@ GET Peer Entities with attribute-based filter
... Test title: GET Peer Entities with attribute-based filter
... Test objective: The objective is to query information and configuration in the producer NFV-MANO functional entity with regards to multiple peer entities with attribute filters, and perform the JSON schema validation of the returned job data structure.
... Pre-conditions: At least one Peer Entity is already created.
- ... Reference: clause 5.5.13.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.13.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -93,7 +93,7 @@ GET Peer Entities with "all_fields" attribute selector
... Test title: GET Peer Entities with "all_fields" attribute selector
... Test objective: The objective is to retrieve information and configuration in the producer NFV-MANO functional entity with regards to multiple peer entities with "all_fields" attribute selector, and perform the JSON schema validation of the returned job data structure.
... Pre-conditions: At least one Peer Entity is already created.
- ... Reference: clause 5.5.13.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.13.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -106,7 +106,7 @@ GET Peer Entities with "exclude_default" attribute selector
... Test title: GET Peer Entities with "exclude_default" attribute selector
... Test objective: The objective is to retrieve information and configuration in the producer NFV-MANO functional entity with regards to multiple peer entities with "exclude_default" attribute selector, and perform the JSON schema validation of the returned job data structure.
... Pre-conditions: At least one Peer Entity is already created.
- ... Reference: clause 5.5.13.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.13.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -119,7 +119,7 @@ GET Peer Entities with "fields" attribute selector
... Test title: GET Peer Entities with "fields" attribute selector
... Test objective: The objective is to retrieve information and configuration in the producer NFV-MANO functional entity with regards to multiple peer entities with fields attribute selector, and perform the JSON schema validation of the returned job data structure.
... Pre-conditions: At least one Peer Entity is already created.
- ... Reference: clause 5.5.13.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.13.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -132,7 +132,7 @@ GET Peer Entities with "exclude_fields" attribute selector
... Test title: GET Peer Entities with "exclude_fields" attribute selector
... Test objective: The objective is to retrieve information and configuration in the producer NFV-MANO functional entity with regards to multiple peer entities with "exclude_fields" attribute selector, and perform the JSON schema validation of the returned job data structure.
... Pre-conditions: At least one Peer Entity is already created.
- ... Reference: clause 5.5.13.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.13.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -145,7 +145,7 @@ GET Peer Entities with "exclude_default" and "fields" attribute selector
... Test title: GET Peer Entities with "exclude_default" and "fields" attribute selector
... Test objective: The objective is to retrieve information and configuration in the producer NFV-MANO functional entity with regards to multiple peer entities with "exclude_default" and "fields" attribute selector, and perform the JSON schema validation of the returned job data structure.
... Pre-conditions: At least one Peer Entity is already created.
- ... Reference: clause 5.5.13.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.13.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -158,7 +158,7 @@ GET Peer Entity with Paged Response
... Test title: GET Peer Entity with Paged Response
... Test objective: The objective is to query information and configuration in the producer NFV-MANO functional entity with regards to multiple peer entities to get Paged Response.
... Pre-conditions: At least one Peer Entity is already created.
- ... Reference: clause 5.5.13.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.13.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -171,7 +171,7 @@ Get Peer Entity with malformed authorization token
... Test title: Get Peer Entity with malformed authorization token
... Test objective: The objective is to test that the retrieval of information and configuration in the producer NFV-MANO functional entity with regards to multiple peer entities fails when using malformed authorization token.
... Pre-conditions: none
- ... Reference: clause 5.5.13.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.13.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: The Peer Entity requires the usage of access tokens for authorizing the API requests.
... Post-Conditions: none
@@ -183,7 +183,7 @@ Get Peer Entity without authorization token
... Test title: Get Peer Entity without authorization token
... Test objective: The objective is to test that the retrieval of information and configuration in the producer NFV-MANO functional entity with regards to multiple peer entities fails when omitting the authorization token.
... Pre-conditions: none
- ... Reference: clause 5.5.13.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.13.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: The Peer Entity requires the usage of access tokens for authorizing the API requests.
... Post-Conditions: none
@@ -195,7 +195,7 @@ GET information about multiple alarms with expired or revoked authorization toke
... Test title: GET information about multiple alarms with expired or revoked authorization token
... Test objective: The objective is to test that the retrieval of information and configuration in the producer NFV-MANO functional entity with regards to multiple peer entities fails when using expired or revoked authorization token.
... Pre-conditions: none
- ... Reference: clause 5.5.13.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.13.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: The Peer Entity requires the usage of access tokens for authorizing the API requests.
... Post-Conditions: none
@@ -207,7 +207,7 @@ PUT Peer Entities - Method not implemented
... Test title: PUT Peer Entities - Method not implemented
... Test objective: The objective is to test that PUT method is not implemeted.
... Pre-conditions: none
- ... Reference: clause 5.5.13.3.3 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.13.3.3 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -219,7 +219,7 @@ PATCH Peer Entities - Method not implemented
... Test title: PATCH Peer Entities - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemeted.
... Pre-conditions: none
- ... Reference: clause 5.5.13.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.13.3.4 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -231,7 +231,7 @@ DELETE Peer Entities - Method not implemented
... Test title: DELETE Peer Entities - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemeted.
... Pre-conditions: none
- ... Reference: clause 5.5.13.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.13.3.5 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL009/NFVManoConfigurationAndInformationManagement-API/Subscriptions.robot b/SOL009/NFVManoConfigurationAndInformationManagement-API/Subscriptions.robot
index 2d890a6dfd7c8efb5f3017e4ac36a47ac620dd54..dc69dd1f4b9d820af93658269d2ce684a2c8b652 100644
--- a/SOL009/NFVManoConfigurationAndInformationManagement-API/Subscriptions.robot
+++ b/SOL009/NFVManoConfigurationAndInformationManagement-API/Subscriptions.robot
@@ -16,7 +16,7 @@ GET all Subscriptions
... Test title: GET all Subscriptions
... Test objective: The objective is to test the retrieval list of active subscriptions of API consumer and perform a JSON schema validation of the returned subscriptions data structure.
... Pre-conditions: At least one subscription is available in the NFV-MANO.
- ... Reference: clause 5.5.4.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.4.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -29,7 +29,7 @@ GET Subscriptions with attribute-based filter
... Test title: GET Subscriptions with attribute-based filter
... Test objective: The objective is to test the retrieval of active subscriptions list of API consumer using attribute-based filter and perform a JSON schema validation of the collected indicators data structure.
... Pre-conditions: At least one subscription is available in the NFV-MANO.
- ... Reference: clause 5.5.4.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.4.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -42,7 +42,7 @@ GET Subscriptions with Paged Response
... Test title: GET Subscriptions with Paged Response
... Test objective: The objective is to query information of active subscriptions list to of API consumer to get Paged Response.
... Pre-conditions: At least one subscription is available in the NFV-MANO.
- ... Reference: clause 5.5.4.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.4.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability:
... Post-Conditions:
@@ -55,7 +55,7 @@ GET Subscriptions - invalid attribute-based filter
... Test title: GET Subscriptions - invalid attribute-based filter
... Test objective: The objective is to test that the retrieval of active subscriptions list of API consumer fails when using invalid attribute-based filters, and perform the JSON schema validation of the failed operation HTTP response.
... Pre-conditions: At least one subscription is available in the NFV-MANO.
- ... Reference: clause 5.5.4.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.4.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -69,7 +69,7 @@ GET Subscriptions - Bad Request Response too Big
... Test title: GET Subscriptions - Bad Request Response too Big
... Test objective: The objective is to test that the retrieval of active subscriptions list of API consumer fails when response is too big, and perform the JSON schema validation of the failed operation HTTP response.
... Pre-conditions: At least one subscription is available in the NFV-MANO.
- ... Reference: clause 5.5.4.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.4.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -82,7 +82,7 @@ GET Subscriptions - invalid resource endpoint
... Test title: GET Subscriptions - invalid resource endpoint
... Test objective: The objective is to test that the retrieval of active subscriptions list of API consumer fails when using invalid resource endpoint.
... Pre-conditions: At least one subscription is available in the NFV-MANO.
- ... Reference: clause 5.5.4.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.4.3.2 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -94,7 +94,7 @@ POST Create new Subscription
... Test title: Create new Subscription
... Test objective: The objective is to test the creation of a new subscription and perform a JSON schema and content validation of the returned subscription data structure
... Pre-conditions: none
- ... Reference: clause 5.5.4.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.4.3.1 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: The subscription is successfully set and it matches the issued subscription
@@ -111,7 +111,7 @@ POST Create request for duplicated Subscription not creating duplicated subscrip
... Test title: Create request for duplicated Subscription not creating duplicated subscriptions
... Test objective: The objective is to test the attempt of a creation of a duplicated subscription failed and check that no new subscription is created and a link to the original subscription is returned
... Pre-conditions: At least one subscription is available in the NFV-MANO.
- ... Reference: clause 5.5.4.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.4.3.1 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: The NFV-MANO does not support the creation of duplicated subscriptions
... Post-Conditions: The existing Subscription returned is available in the NFV-MANO
@@ -127,7 +127,7 @@ POST Create request for duplicated Subscription creating duplicated subscription
... Test title: Create request for duplicated Subscription creating duplicated subscriptions
... Test objective: The objective is to test the creation of a duplicated subscription and perform a JSON schema and content validation of the returned duplicated subscription data structure
... Pre-conditions: At least one subscription is available in the NFV-MANO.
- ... Reference: clause 5.5.4.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.4.3.1 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: The NFV-MANO supports the creation of duplicated subscriptions
... Post-Conditions: The duplicated subscription is successfully set and it matches the issued subscription
@@ -142,7 +142,7 @@ PUT Subscriptions - Method not implemented
... Test title: PUT Subscriptions - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to modify subscriptions
... Pre-conditions: none
- ... Reference: clause 5.5.4.3.3 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.4.3.3 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -154,7 +154,7 @@ PATCH Subscriptions - Method not implemented
... Test title: PATCH Subscriptions - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to update subscriptions
... Pre-conditions: none
- ... Reference: clause 5.5.4.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.4.3.4 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -166,19 +166,19 @@ DELETE Subscriptions - Method not implemented
... Test title: DELETE Subscriptions - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to delete subscriptions
... Pre-conditions: none
- ... Reference: clause 5.5.4.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.4.3.5 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
Send Delete Request for Subscriptions
Check HTTP Response Status Code Is 405
-POST Create a new subscription - Unprocessable Entity
+POST Create a new subscription - Unprocessable Content
[Documentation] Test ID: 8.3.1.10.13
- ... Test title: POST Create a new Subscription - Unprocessable Entity
+ ... Test title: POST Create a new Subscription - Unprocessable Content
... Test objective: The objective is to test that a new subscription is not created if the notification endpoint is unreachable by the NFV-MANO.
... Pre-conditions: none
- ... Reference: clause 5.5.4.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
+ ... Reference: clause 5.5.4.3.1 - ETSI GS NFV-SOL 009 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: Notification endpoint is unreachable by the NFV-MANO
... Post-Conditions: none
diff --git a/SOL009/NFVManoConfigurationAndInformationManagement-API/schemas/ManoEntity.schema.json b/SOL009/NFVManoConfigurationAndInformationManagement-API/schemas/ManoEntity.schema.json
index 4e9bd8cbb5a1feab54d70de7bf4ff04f55d7a9d1..233330f759a633f7a253cbcfd96815129b0c6e09 100644
--- a/SOL009/NFVManoConfigurationAndInformationManagement-API/schemas/ManoEntity.schema.json
+++ b/SOL009/NFVManoConfigurationAndInformationManagement-API/schemas/ManoEntity.schema.json
@@ -1,16 +1,34 @@
{
- "description": "This type represents an NFV-MANO functional entity. * NOTE 1:\tIt shall be present when \"type\" attribute is \"NFVO\", and it shall be absent in any other case. * NOTE 2:\tIt shall be present when \"type\" attribute is \"VNFM\", and it shall be absent in any other case. * NOTE 3:\tIt shall be present when \"type\" attribute is \"VIM\", and it shall be absent in any other case. * NOTE 4:\tThe information about the NFV-MANO services offered by a specific type of NFV-MANO functional\n entity is specified by the manoServices attribute.\n* NOTE 5:\tIt is optional for the API producer to support the \"manoEntityComponents\" attribute. * NOTE 6:\tIt shall be present when \"type\" attribute is \"WIM\", and it shall be absent in any other case. * NOTE 7:\tIt shall be present when \"type\" attribute is \"CISM\", and it shall be absent in any other case. \n",
+ "description": "This type represents an NFV-MANO functional entity. * NOTE 1:\tIt shall be present when \"type\" attribute is \"NFVO\", and it shall be absent in any other case. * NOTE 2:\tIt shall be present when \"type\" attribute is \"VNFM\", and it shall be absent in any other case. * NOTE 3:\tIt shall be present when \"type\" attribute is \"VIM\", and it shall be absent in any other case. * NOTE 4:\tThe information about the NFV-MANO services offered by a specific type of NFV-MANO functional\n entity is specified by the manoServices attribute.\n* NOTE 5:\tIt is optional for the API producer to support the \"manoEntityComponents\" attribute. * NOTE 6:\tIt shall be present when \"type\" attribute is \"WIM\", and it shall be absent in any other case. * NOTE 7:\tIt shall be present when \"type\" attribute is \"CISM\", and it shall be absent in any other case. * NOTE 8:\tIt shall be present when \"type\" attribute is \"CIR\", and it shall be absent in any other case. * NOTE 9:\tIt shall be present when \"type\" attribute is \"CCM\", and it shall be absent in any other case. \n",
"type": "object",
- "required": ["id", "type", "name", "description", "provider", "softwareVersion", "manoConfigurableParams", "manoApplicationState", "_links"],
+ "required": [
+ "id",
+ "type",
+ "name",
+ "description",
+ "provider",
+ "softwareVersion",
+ "manoConfigurableParams",
+ "manoApplicationState",
+ "_links"
+ ],
"properties": {
"id": {
"description": "An identifier with the intention of being globally unique.\n",
"type": "string"
},
"type": {
- "description": "The enumeration ManoEntityEnumType defines the permitted values to represent NFV-MANO functional entities. It shall comply with the provisions :\n - NFVO\tThe NFV-MANO functional entity is an NFVO.\n - VNFM\tThe NFV-MANO functional entity is a VNFM.\n - VIM\t The NFV-MANO functional entity is a VIM.\n - WIM The NFV-MANO functional entity is a WIM.\n - CISM The NFV-MANO functional entity is a CISM. \n",
+ "description": "The enumeration ManoEntityEnumType defines the permitted values to represent NFV-MANO functional entities. It shall comply with the provisions :\n - NFVO\tThe NFV-MANO functional entity is an NFVO.\n - VNFM\tThe NFV-MANO functional entity is a VNFM.\n - VIM\t The NFV-MANO functional entity is a VIM.\n - WIM The NFV-MANO functional entity is a WIM.\n - CISM The NFV-MANO functional entity is a CISM. \n - CIR The NFV-MANO functional entity is a CIR.\n - CCM The NFV-MANO functional entity is a CCM.\n",
"type": "string",
- "enum": ["NFVO", "VNFM", "VIM", "WIM", "CISM"]
+ "enum": [
+ "NFVO",
+ "VNFM",
+ "VIM",
+ "WIM",
+ "CISM",
+ "CIR",
+ "CCM"
+ ]
},
"name": {
"description": "Human-readable name of the NFV-MANO functional entity.\nThis attribute can be modified with the PATCH method.\n",
@@ -38,7 +56,9 @@
"items": {
"description": "This type represents information of a deployed component realizing part of an NFV-MANO functional entity. It is optional for the API producer to support this type.\n",
"type": "object",
- "required": ["id"],
+ "required": [
+ "id"
+ ],
"properties": {
"id": {
"description": "An identifier that is unique for the respective type within a NFV-MANO functional entity, but that need not be globally unique. Representation: string of variable length..\n",
@@ -61,7 +81,13 @@
"items": {
"description": "This type represents information about an NFV-MANO service provided by the NFV-MANO functional entity. * NOTE:\tA cardinality greater than one supports having different interface versions or api Endpoints\n to be used for accessing the same instance of an NFV-MANO service.\n",
"type": "object",
- "required": ["id", "name", "description", "manoServiceInterfaceIds", "_links"],
+ "required": [
+ "id",
+ "name",
+ "description",
+ "manoServiceInterfaceIds",
+ "_links"
+ ],
"properties": {
"id": {
"description": "An identifier that is unique for the respective type within a NFV-MANO functional entity, but that need not be globally unique. Representation: string of variable length..\n",
@@ -94,7 +120,9 @@
"items": {
"description": "This type represents a link to a resource using an absolute URI.\n",
"type": "object",
- "required": ["href"],
+ "required": [
+ "href"
+ ],
"properties": {
"href": {
"description": "String formatted according to IETF RFC 3986.\n",
@@ -105,7 +133,9 @@
"minItems": 1
}
},
- "required": ["manoServiceInterfaces"]
+ "required": [
+ "manoServiceInterfaces"
+ ]
}
}
}
@@ -114,31 +144,51 @@
"description": "ManoConfigurableParams\n"
},
"manoApplicationState": {
- "description": "Information and current values of the NFV-MANO functional entitys application state.\n",
+ "description": "Information and current values of the NFV-MANO functional entity’s application state.\n",
"type": "object",
- "required": ["operationalState", "administrativeState", "usageState"],
+ "required": [
+ "operationalState",
+ "administrativeState",
+ "usageState"
+ ],
"properties": {
"operationalState": {
"description": "The enumeration OperationalStateEnumType defines values representing the operational state of an NFV-MANO functional application type of managed entity. The OperationalStateEnumType shall comply with the provisions:\n - STARTED\tThe managed entity is operational.\n - STOPPED\tThe managed entity is not operational.\n - STOPPING\tThe managed entity is in the transition to stop.\n - STARTING\tThe managed entity is in the transition to start and become operational.\n - RESTARTING\tThe managed entity is in the transition to stop and start again.\n",
"type": "string",
- "enum": ["STARTED", "STOPPED", "STOPPING", "STARTING", "RESTARTING"]
+ "enum": [
+ "STARTED",
+ "STOPPED",
+ "STOPPING",
+ "STARTING",
+ "RESTARTING"
+ ]
},
"administrativeState": {
"description": "The enumeration AdministrativeStateEnumType defines values representing the administrative state of a managed entity. The AdministrativeStateEnumType shall comply with the provisions:\n - LOCKED\tThe managed entity is administratively prohibited to be used.\n - UNLOCKED\tThe managed entity is administratively allowed to be used.\n - LOCKING\tThe managed entity is in the transition to be locked.\n",
"type": "string",
- "enum": ["LOCKED", "UNLOCKED", "LOCKING"]
+ "enum": [
+ "LOCKED",
+ "UNLOCKED",
+ "LOCKING"
+ ]
},
"usageState": {
"description": "The enumeration UsageStateEnumType defines values representing the usage state of a managed entity. The UsageStateEnumType shall comply with the provisions:\n - IN_USE\tThe managed entity is currently being used.\n - NOT_IN_USE\tThe managed entity is currently not being used.\n",
"type": "string",
- "enum": ["IN_USE", "NOT_IN_USE"]
+ "enum": [
+ "IN_USE",
+ "NOT_IN_USE"
+ ]
}
}
},
"nfvoSpecificInfo": {
"description": "This type represents information attributes specific to an NFVO entity, and that can be relevant to more than one NFV-MANO service offered by an NFVO entity. * NOTE 1:\tThe information to be provided in this attribute shall relate to the specification and version\n of the specification. For instance, \"ETSI GS NFV-SOL 001 (V2.5.1)\".\n NOTE 2:\tIf this attribute is not present, the value of this parameter is undefined.\n",
"type": "object",
- "required": ["supportedVnfdFormats", "supportedNsdFormats"],
+ "required": [
+ "supportedVnfdFormats",
+ "supportedNsdFormats"
+ ],
"properties": {
"maxOnboardedNsdNum": {
"description": "Maximum number of NSDs that can be on-boarded on the NFVO. See note 2.\n",
@@ -155,14 +205,20 @@
"vnfdFormat": {
"description": "Name of the VNFD format.\nPermitted values:\n - TOSCA: The VNFD follows TOSCA definition, according to ETSI\n GS NFV-SOL 001 standard.\n - YANG: The VNFD follows YANG definition according to ETSI\n GS NFV-SOL 006 standard.\n",
"type": "string",
- "enum": ["TOSCA", "YANG"]
+ "enum": [
+ "TOSCA",
+ "YANG"
+ ]
},
"standardVersion": {
"description": "A version.\n",
"type": "string"
}
},
- "required": ["vnfdFormat", "standardVersion"]
+ "required": [
+ "vnfdFormat",
+ "standardVersion"
+ ]
},
"supportedNsdFormats": {
"description": "Supported NSD data formats.\n",
@@ -171,26 +227,40 @@
"nsdFormat": {
"description": "Name of the NSD format.\nPermitted values:\n - TOSCA: The VNFD follows TOSCA definition, according to ETSI\n GS NFV-SOL 001 standard.\n - YANG: The VNFD follows YANG definition according to ETSI\n GS NFV-SOL 006 standard.\n",
"type": "string",
- "enum": ["TOSCA", "YANG"]
+ "enum": [
+ "TOSCA",
+ "YANG"
+ ]
},
"standardVersion": {
"description": "A version.\n",
"type": "string"
}
},
- "required": ["nsdFormat", "standardVersion"]
+ "required": [
+ "nsdFormat",
+ "standardVersion"
+ ]
}
}
},
"vnfmSpecificInfo": {
"description": "This type represents information attributes specific to a VNFM entity, and that can be relevant to more than one NFV-MANO service offered by a VNFM entity. * NOTE:\tThe information to be provided in this attribute shall relate to the specification and version\n of the specification. For instance, \"ETSI GS NFV-SOL 001 (V2.5.1)\".\n",
"type": "object",
- "required": ["resoruceMgmtModeSupport", "managedVnfInstanceInfos", "supportedVnfdFormats"],
+ "required": [
+ "resoruceMgmtModeSupport",
+ "managedVnfInstanceInfos",
+ "supportedVnfdFormats"
+ ],
"properties": {
"resoruceMgmtModeSupport": {
"description": "The supported resource management modes of the VNFM.\nPermitted values:\n - DIRECT: The VNFM supports direct mode only.\n - INDIRECT: The VNFM supports indirect mode only.\n - BOTH: The VNFM supports both direct and indirect mode.\n",
"type": "string",
- "enum": ["DIRECT", "INDIRECT", "BOTH"]
+ "enum": [
+ "DIRECT",
+ "INDIRECT",
+ "BOTH"
+ ]
},
"managedVnfInstanceInfos": {
"description": "The kinds of VNF instances that can be managed, e.g. to determine the compatibility of a VNF with certain VNFM according to the vnfmInfo attribute in the VNFD (see table 7.1.2.2-1 in ETSI GS NFV-IFA 011).\n",
@@ -209,14 +279,20 @@
"vnfdFormat": {
"description": "Name of the VNFD format.\nPermitted values:\n - TOSCA: The VNFD follows TOSCA definition, according to ETSI\n GS NFV-SOL 001 standard.\n - YANG: The VNFD follows YANG definition according to ETSI\n GS NFV-SOL 006 standard.\n",
"type": "string",
- "enum": ["TOSCA", "YANG"]
+ "enum": [
+ "TOSCA",
+ "YANG"
+ ]
},
"standardVersion": {
"description": "A version.\n",
"type": "string"
}
},
- "required": ["vnfdFormat", "standardVersion"]
+ "required": [
+ "vnfdFormat",
+ "standardVersion"
+ ]
},
"minItems": 1
}
@@ -225,7 +301,12 @@
"vimSpecificInfo": {
"description": "This type represents information attributes specific to a VIM entity, and that can be relevant to more than one NFV MANO service offered by a VIM entity. It shall comply with the provisions defined in table 5.6.3.6-1. The present document version does not specify the support for \"maximum number of virtualised resources (attribute \"maxVirtualResourceNum\")\" as specified in clause 7.2.9.2 of ETSI GS NFV IFA 031 [1].\nNOTE:\tRecommendations on appropriate algorithms and key lengths are given e.g., in NIST Special Publication 800-57 Part 3 Revision 1 [i.26] or in documents related to local legislation.\n",
"type": "object",
- "required": ["imageContainerFormats", "imageDiskFormats", "imageSignatureVerification", "imageDigestAlgorithms"],
+ "required": [
+ "imageContainerFormats",
+ "imageDiskFormats",
+ "imageSignatureVerification",
+ "imageDigestAlgorithms"
+ ],
"properties": {
"imageContainerFormats": {
"description": "List of supported image container formats. Container format indicates whether a software image is in a file that also contains metadata about the actual software. Valid values are all values for \"container_format\" as defined in ETSI GS NFV-SOL 001 [16] and all values for \"container-format\" as defined in ETSI GS NFV-SOL 006 [i.17].\n",
@@ -244,7 +325,9 @@
"imageSignatureVerification": {
"description": "Information about the supported mechanisms, algorithms, and protocols for verifying the signature of software images.\n",
"type": "object",
- "required": ["signatureVerificationAlgorithms"],
+ "required": [
+ "signatureVerificationAlgorithms"
+ ],
"properties": {
"additionalVerificationCapabilities": {
"description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of keyvalue pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 8259. In the following example, a list of key-value pairs with four keys (\"aString\", \"aNumber\", \"anArray\" and \"anObject\") is provided to illustrate that the values associated with different keys can be of different type.\n",
@@ -255,14 +338,17 @@
"type": "array",
"items": {
"type": "object",
- "required": ["algorithm", "keyLengths"],
+ "required": [
+ "algorithm",
+ "keyLengths"
+ ],
"properties": {
"algorithm": {
"description": "The name of the algorithm. Permitted values are: \"RSA\", \"DSA\", \"ECDSA\".\n",
"type": "string"
},
"keyLengths": {
- "description": "List of supported key lengths of the algorithm. The key length indicates the number of bits, such as 256, 512, etc. See note.\n",
+ "description": "List of supported key lengths of the algorithm. The key length indicates the number of bits, such as “256”, “512”, etc. See note.\n",
"type": "array",
"items": {
"type": "string"
@@ -282,14 +368,17 @@
"type": "array",
"items": {
"type": "object",
- "required": ["algorithm", "keyLengths"],
+ "required": [
+ "algorithm",
+ "keyLengths"
+ ],
"properties": {
"algorithm": {
- "description": "The name of the algorithm. Permitted values are: SHA2,SHA3.\n",
+ "description": "The name of the algorithm. Permitted values are: “SHA2“,“SHA3“.\n",
"type": "string"
},
"keyLengths": {
- "description": "List of supported key lengths of the algorithm. The key length indicates the number of bits, such as 256, 512, etc. See note.\n",
+ "description": "List of supported key lengths of the algorithm. The key length indicates the number of bits, such as “256”, “512”, etc. See note.\n",
"type": "array",
"items": {
"type": "string"
@@ -303,12 +392,18 @@
"wimSpecificInfo": {
"description": "This type represents information attributes specific to a WIM entity, and that can be relevant to more than one NFV MANO service offered by a WIM entity.\n",
"type": "object",
- "required": ["maxMscsNums", "maxMsncNum", "mscsLayerProtocolSupport"],
+ "required": [
+ "maxMscsNums",
+ "maxMsncNum",
+ "mscsLayerProtocolSupport"
+ ],
"properties": {
"maxMscsNums": {
"description": "Maximum number of MSCS that the WIM can manage.\n",
"type": "object",
- "required": ["numMscs"],
+ "required": [
+ "numMscs"
+ ],
"properties": {
"numMscs": {
"description": "Maximum number of MSCS.\n",
@@ -323,7 +418,9 @@
"maxMsncNum": {
"description": "Maximum number of MSNC that the WIM can manage\n",
"type": "object",
- "required": ["numMsnc"],
+ "required": [
+ "numMsnc"
+ ],
"properties": {
"numMsnc": {
"description": "Maximum number of MSNC..\n",
@@ -336,26 +433,153 @@
}
},
"mscsLayerProtocolSupport": {
- "description": "List of protocols of particular layers used to realize an MSCS that are supported by the WIM.\nPermitted values: - EVPN_BGP_MPLS: L2 MSCS realized by BGP MPLS-based Ethernet VPN (EVPN) as specified in IETF RFC 7432.\n - EVPN_VPWS: L2 MSCS realized by EVPN Virtual Private Wire Service (VPWS) as specified in IETF RFC 8214.\n - VPLS_BGP: L2 MSCS realized by Virtual Private LAN Service (VPLS) using BGP as specified\n in IETF RFC 4761 and IETF RFC.\n - VPLS_LDP_L2TP: L2 MSCS realized by VPLS using Label Distribution Protocol (LDP) Layer 2\n Tunnelling Protocol (L2TP) as specified in IETF RFC 4762 and IETF RFC 6074.\n - VPWS_LDP_L2TP: L2 MSCS realized by VPWS using LDP L2TP as specified in IETF RFC 6074.\n - BGP_IP_VPN: L3 MSCS realized by BGP/MPLS based IP VPN as specified in IETF RFC 4364.\n",
+ "description": "List of protocols of particular layers used to realize an MSCS that are supported by the WIM.\nPermitted values:\n - EVPN_BGP_MPLS: L2 MSCS realized by BGP MPLS-based Ethernet VPN (EVPN) as specified in IETF RFC 7432.\n - EVPN_VPWS: L2 MSCS realized by EVPN Virtual Private Wire Service (VPWS) as specified in IETF RFC 8214.\n - VPLS_BGP: L2 MSCS realized by Virtual Private LAN Service (VPLS) using BGP as specified\n in IETF RFC 4761 and IETF RFC.\n - VPLS_LDP_L2TP: L2 MSCS realized by VPLS using Label Distribution Protocol (LDP) Layer 2\n Tunnelling Protocol (L2TP) as specified in IETF RFC 4762 and IETF RFC 6074.\n - VPWS_LDP_L2TP: L2 MSCS realized by VPWS using LDP L2TP as specified in IETF RFC 6074.\n - BGP_IP_VPN: L3 MSCS realized by BGP/MPLS based IP VPN as specified in IETF RFC 4364.\n",
"type": "string",
- "enum": ["EVPN_BGP_MPLS", "EVPN_VPWS", "VPLS_BGP", "VPLS_LDP_L2TP", "VPWS_LDP_L2TP", "BGP_IP_VPN"]
+ "enum": [
+ "EVPN_BGP_MPLS",
+ "EVPN_VPWS",
+ "VPLS_BGP",
+ "VPLS_LDP_L2TP",
+ "VPWS_LDP_L2TP",
+ "BGP_IP_VPN"
+ ]
}
}
},
"cismSpecificInfo": {
"description": "This type represents information attributes specific to a CISM entity, and that can be relevant to more than one NFV-MANO service offered by a CISM entity. It shall comply with the provisions defined in table 5.6.3.14-1. NOTE:\tNo attributes are specified in the present document version. The definition of attributes is left for future specification. \n",
- "type": "object"
+ "type": "object",
+ "properties": {
+ "none": {
+ "type": "object"
+ }
+ }
+ },
+ "cirSpecificInfo": {
+ "description": "This type represents information attributes specific to a CIR entity, and that can be relevant to more than one NFV- MANO service offered by a CIR entity. It shall comply with the provisions defined in table 5.6.3.15-1. NOTE: Recommendations on appropriate algorithms and key lengths are given e.g. in NIST Special Publication 800-57 \n Part 3 Revision 1 or in documents related to local legislation.\n",
+ "type": "object",
+ "required": [
+ "osContainerImageFormats",
+ "imageSignatureVerification",
+ "imageDigestAlgorithms"
+ ],
+ "properties": {
+ "osContainerImageFormats": {
+ "description": "List of supported OS container image formats. Valid values are all values for \"container_format\" as defined in ETSI GS NFV-SOL 001 and all values for \"container-format\" as defined in ETSI GS NFV-SOL 006.\n",
+ "type": "array",
+ "minItems": 1,
+ "items": {
+ "type": "string"
+ }
+ },
+ "imageSignatureVerification": {
+ "description": "Information about the supported mechanisms, algorithms, and protocols for verifying the of software images.\n",
+ "type": "object",
+ "required": [
+ "signatureVerificationAlgorithms"
+ ],
+ "properties": {
+ "signatureVerificationAlgorithms": {
+ "description": "List of algorithms for verifying the signature of software images that are supported by the CIR.\n",
+ "type": "array",
+ "items": {
+ "description": "List of algorithms for verifying the signature of software images that are supported by the CIR.\n",
+ "type": "object",
+ "required": [
+ "algorithm",
+ "keyLengths"
+ ],
+ "properties": {
+ "algorithm": {
+ "description": "The name of the algorithm. Permitted values are: \"RSA\", \"DSA\", \"ECDSA\".\n",
+ "type": "string"
+ },
+ "keyLengths": {
+ "description": "List of supported key lengths of the algorithm. The key length indicates the number of bits, such as \"256\", \"512\", etc. See note\n",
+ "type": "array",
+ "minItems": 1,
+ "items": {
+ "type": "string"
+ }
+ },
+ "additionalAlgParams": {
+ "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of keyvalue pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 8259. In the following example, a list of key-value pairs with four keys (\"aString\", \"aNumber\", \"anArray\" and \"anObject\") is provided to illustrate that the values associated with different keys can be of different type.\n",
+ "type": "object"
+ }
+ }
+ }
+ }
+ }
+ },
+ "imageDigestAlgorithms": {
+ "type": "array",
+ "items": {
+ "description": "List of supported digest algorithms that can be used for digital signatures.\n",
+ "type": "object",
+ "required": [
+ "algorithm",
+ "keyLengths"
+ ],
+ "properties": {
+ "algorithm": {
+ "description": "The name of the algorithm. Permitted values are: \"SHA2\", \"SHA3\".\n",
+ "type": "string",
+ "enum": [
+ "SHA2",
+ "SHA3"
+ ]
+ },
+ "keyLengths": {
+ "description": "List of supported key lengths of the algorithm. The key length indicates the number of bits, such as \"256\", \"512\", etc. See note.\n",
+ "type": "array",
+ "items": {
+ "type": "string"
+ }
+ }
+ }
+ }
+ }
+ }
+ },
+ "ccmSpecificInfo": {
+ "description": "The supported cluster resource management modes. Available modes include: virtual and bare-metal resources, and for both types, on-demand (i.e., CCM requests to corresponding infrastructure managers to build necessary pools of resources) or pooled (i.e., CCM manages resources from pre-allocated resource pools). Multiple values can be specified. See note. Permitted values: - VIRTUAL-ON-DEMAND: virtual resourceson demand. - VIRTUAL-POOLED: virtual resources from a pre-allocated resource pool. - BARE-METAL-ON-DEMAND: bare-metal resources on demand. - BARE-METAL-POOLED: bare-metal resources from a pre-allocated resource pool.\nNOTE: Hybrid CIS clusters include both physical and virtual CIS cluster nodes and can be supported by a\n combination of relevant \"clusterResourceMgmtModes\".\n",
+ "type": "object",
+ "required": [
+ "clusterResourceMgmtModes"
+ ],
+ "properties": {
+ "clusterResourceMgmtModes": {
+ "type": "array",
+ "minItems": 1,
+ "items": {
+ "type": "string",
+ "enum": [
+ "VIRTUAL-ON-DEMAND",
+ "VIRTUAL-POOLED",
+ "BARE-METAL-ON-DEMAND",
+ "BARE-METAL-POOLED"
+ ]
+ }
+ }
}
},
"_links": {
"description": "Links to resources related to this resource.\n",
"type": "object",
- "required": ["self", "manoServiceInterfaces", "peerEntities", "changeState", "changeStateOpOccs"],
+ "required": [
+ "self",
+ "manoServiceInterfaces",
+ "peerEntities",
+ "changeState",
+ "changeStateOpOccs"
+ ],
"properties": {
"self": {
"description": "This type represents a link to a resource using an absolute URI.\n",
"type": "object",
- "required": ["href"],
+ "required": [
+ "href"
+ ],
"properties": {
"href": {
"description": "String formatted according to IETF RFC 3986.\n",
@@ -366,7 +590,9 @@
"manoServiceInterfaces": {
"description": "This type represents a link to a resource using an absolute URI.\n",
"type": "object",
- "required": ["href"],
+ "required": [
+ "href"
+ ],
"properties": {
"href": {
"description": "String formatted according to IETF RFC 3986.\n",
@@ -377,7 +603,9 @@
"peerEntities": {
"description": "This type represents a link to a resource using an absolute URI.\n",
"type": "object",
- "required": ["href"],
+ "required": [
+ "href"
+ ],
"properties": {
"href": {
"description": "String formatted according to IETF RFC 3986.\n",
@@ -388,7 +616,9 @@
"changeState": {
"description": "This type represents a link to a resource using an absolute URI.\n",
"type": "object",
- "required": ["href"],
+ "required": [
+ "href"
+ ],
"properties": {
"href": {
"description": "String formatted according to IETF RFC 3986.\n",
@@ -399,7 +629,9 @@
"changeStateOpOccs": {
"description": "This type represents a link to a resource using an absolute URI.\n",
"type": "object",
- "required": ["href"],
+ "required": [
+ "href"
+ ],
"properties": {
"href": {
"description": "String formatted according to IETF RFC 3986.\n",
diff --git a/SOL009/NFVManoConfigurationAndInformationManagement-API/schemas/ManoServiceInterface.schema.json b/SOL009/NFVManoConfigurationAndInformationManagement-API/schemas/ManoServiceInterface.schema.json
index 94ea568214b39f3be8f2b4580ca54129ecff6214..3f879bdc5822c09d50e6af0e6219379c2a9b1f7b 100644
--- a/SOL009/NFVManoConfigurationAndInformationManagement-API/schemas/ManoServiceInterface.schema.json
+++ b/SOL009/NFVManoConfigurationAndInformationManagement-API/schemas/ManoServiceInterface.schema.json
@@ -1,5 +1,5 @@
{
- "description": "This type represents an individual NFV-MANO service interface produced by an NFV-MANO functional entity. * NOTE 1:\tThe information to be provided in this attribute shall relate to the specification and\n version of the specification. For instance, \"ETSI GS NFV-SOL 003 (V2.4.1)\".\n* NOTE 2:\tIf this attribute is not present, the value of this parameter is undefined. Overload is\n handled by the error handling schemes defined by the applicable API specification.\n* NOTE 3:\tDue to the security sensitive information associated to the attribute, based on access\n control policies, the API consumer might have read only, write only, read/write, or no access\n at all to the attribute's value. In case the API consumer is not allowed to read the value of\n the security sensitive attribute, the attribute shall be omitted when the information is to be\n provided in a response message, and shall be provided otherwise. In case the API consumer is\n not allowed to modify the value of the security sensitive attribute, and the modification request\n includes new attribute values, the whole modification request shall be rejected, and proper\n error information returned.\n",
+ "description": "This type represents an individual NFV-MANO service interface produced by an NFV-MANO functional entity. * NOTE 1:\tThe information to be provided in this attribute shall relate to the specification and\n version of the specification. For instance, \"ETSI GS NFV-SOL 003 (V2.4.1)\".\n* NOTE 2:\tIf this attribute is not present, the value of this parameter is undefined. Overload is\n handled by the error handling schemes defined by the applicable API specification.\n* NOTE 3:\tDue to the security sensitive information associated to the attribute, based on access\n control policies, the API consumer might have read only, write only, read/write, or no access\n at all to the attribute's value. In case the API consumer is not allowed to read the value of\n the security sensitive attribute, the attribute shall be omitted when the information is to be\n provided in a response message, and shall be provided otherwise. In case the API consumer is\n not allowed to modify the value of the security sensitive attribute, and the modification request\n includes new attribute values, the whole modification request shall be rejected, and proper\n error information returned.\n",
"type": "object",
"required": [
"id",
@@ -22,7 +22,7 @@
"type": "string"
},
"type": {
- "description": "Type of the NFV-MANO service interface produced by the NFV-MANO functional entity. Valid values are defined in clause 5.6.4.3.\n",
+ "description": "Type of the NFV-MANO service interface produced by the NFV-MANO functional entity. Valid values are defined in clause 5.6.4.3.\n",
"type": "string"
},
"standardVersion": {
@@ -46,11 +46,11 @@
"type": "string"
},
"apiName": {
- "description": "Indicates the interface name in an abbreviated form. Shall be present for ETSI NFV specified RESTful NFV-MANO APIs. The {apiName} of each interface is defined in the standard the interface is compliant to (see also clause 4.1 of ETSI GS NFV-SOL 013). May be present otherwise.\n",
+ "description": "Indicates the interface name in an abbreviated form. Shall be present for ETSI NFV specified RESTful NFV-MANO APIs. The {apiName} of each interface is defined in the standard the interface is compliant to (see also clause 4.1 of ETSI GS NFV-SOL 013). May be present otherwise.\n",
"type": "string"
},
"apiMajorVersion": {
- "description": "Indicates the current major version of the API. Shall be present for ETSI NFV specified RESTful NFV-MANO APIs. The major version is defined in the standard the interface is compliant to (see also clause 4.1 of ETSI GS NFV-SOL 013). May be present otherwise.\n",
+ "description": "Indicates the current major version of the API. Shall be present for ETSI NFV specified RESTful NFV-MANO APIs. The major version is defined in the standard the interface is compliant to (see also clause 4.1 of ETSI GS NFV-SOL 013). May be present otherwise.\n",
"type": "string"
},
"apiUri": {
@@ -91,7 +91,7 @@
"description": "State of the NFV-MANO service interface.\n",
"properties": {
"operationalState": {
- "description": "The enumeration InterfaceOperationalStateEnumType defines values representing the operational state of an NFV-MANO service interface type of managed entity. The InterfaceOperationalStateEnumType shall comply with the provisions :\n - STARTED\tThe managed entity is operational.\n - STOPPED\tThe managed entity is not operational.\n - STOPPING\tThe managed entity is in the transition to stop.\n - STARTING\tThe managed entity is in the transition to start and become operational.\n",
+ "description": "The enumeration InterfaceOperationalStateEnumType defines values representing the operational state of an NFV-MANO service interface type of managed entity. The InterfaceOperationalStateEnumType shall comply with the provisions :\n - STARTED\tThe managed entity is operational.\n - STOPPED\tThe managed entity is not operational.\n - STOPPING\tThe managed entity is in the transition to stop.\n - STARTING\tThe managed entity is in the transition to start and become operational.\n",
"type": "string",
"enum": [
"STARTED",
@@ -110,7 +110,7 @@
]
},
"usageState": {
- "description": "The enumeration UsageStateEnumType defines values representing the usage state of a managed entity. The UsageStateEnumType shall comply with the provisions:\n - IN_USE\tThe managed entity is currently being used.\n - NOT_IN_USE\tThe managed entity is currently not being used.\n",
+ "description": "The enumeration UsageStateEnumType defines values representing the usage state of a managed entity. The UsageStateEnumType shall comply with the provisions:\n - IN_USE\tThe managed entity is currently being used.\n - NOT_IN_USE\tThe managed entity is currently not being used.\n",
"type": "string",
"enum": [
"IN_USE",
@@ -125,7 +125,7 @@
]
},
"securityInfo": {
- "description": "This type represents security related information of an NFV-MANO service interface produced by an NFV-MANO functional entity. * NOTE:\tProvided configuration of the OAuth 2.0 authorization server information and configuration\n shall be supported, and dynamic configuration may be supported.\n",
+ "description": "This type represents security related information of an NFV-MANO service interface produced by an NFV-MANO functional entity. * NOTE:\tProvided configuration of the OAuth 2.0 authorization server information and configuration\n shall be supported, and dynamic configuration may be supported.\n",
"type": "object",
"required": [
"authType",
@@ -133,12 +133,13 @@
],
"properties": {
"authType": {
- "description": "Type of API request authorization to be used by the API producer.\nThe support of authorization methods for the API producer is specified in clause 8.3.6 of ETSI GS NFV-SOL 013.\nPermitted values:\n - TLS_TUNNEL: Using TLS tunnel, as defined by TLS 1.2 in IETF RFC 5246.\n - OAUTH2: Using access token, as defined by the OAuth 2.0 specification \n in IETF RFC 6749. \n",
+ "description": "Type of API request authorization to be used by the API producer.\nThe support of authorization methods for the API producer is specified in clause 8.3.6 of ETSI GS NFV-SOL 013.\nPermitted values:\n - TLS_TUNNEL: Using TLS tunnel, as defined by TLS 1.2 in IETF RFC 5246.\n - TLS_TUNNEL_13: Using TLS tunnel, as defined by TLS 1.3 in IETF RFC 8446.\n - OAUTH2: Using access token, as defined by the OAuth 2.0 specification\n in IETF RFC 6749.\n",
"type": "array",
"items": {
"type": "string",
"enum": [
"TLS_TUNNEL",
+ "TLS_TUNNEL_13",
"OAUTH2"
]
},
@@ -153,7 +154,7 @@
],
"properties": {
"dynamicDiscovery": {
- "description": "Configuration data used when performing dynamic discovery of the authorization server identifier. See note.\n",
+ "description": "Configuration data used when performing dynamic discovery of the authorization server identifier. See note.\n",
"type": "object",
"required": [
"webFingerHost"
@@ -189,11 +190,11 @@
}
},
"tlsTunnelInfo": {
- "description": "Information and configuration related to the use of TLS tunnel. Shall be present if authType contains \"TLS_TUNNEL\".\n",
+ "description": "Information and configuration related to the use of TLS tunnel. Shall be present if authType contains \"TLS_TUNNEL\".\n",
"type": "object",
"properties": {
"tlsTunnelCipherSuites": {
- "description": "List of cipher suites that shall be declared as supported by the API producer when performing the SSL or TLS negotiation with the API client. Valid values of cipher suites are defined in IETF RFC 8447.\n",
+ "description": "List of cipher suites that shall be declared as supported by the API producer when performing the SSL or TLS negotiation with the API client. Valid values of cipher suites are defined in IETF RFC 8447.\n",
"type": "array",
"items": {
"type": "string"
diff --git a/SOL009/NFVManoConfigurationAndInformationManagement-API/schemas/ManoServiceInterfaceModifications.schema.json b/SOL009/NFVManoConfigurationAndInformationManagement-API/schemas/ManoServiceInterfaceModifications.schema.json
index 26199703f9c3a5cef261431b73822c2aeffb2ece..317cbae83ef623de9180cfc2948a7a6593c825cb 100644
--- a/SOL009/NFVManoConfigurationAndInformationManagement-API/schemas/ManoServiceInterfaceModifications.schema.json
+++ b/SOL009/NFVManoConfigurationAndInformationManagement-API/schemas/ManoServiceInterfaceModifications.schema.json
@@ -1,9 +1,9 @@
{
- "description": "This type represents attribute modifications that were performed on an Individual NFV-MANO service interface\" resource. The attributes that can be included consist of those requested to be modified explicitly in the \"ManoServiceInterfaceModificationRequest\" data structure. If applicable, additional attributes of the \"ManoServiceInterface\" data structure that were modified implicitly shall also be provided. * NOTE:\tDue to the security sensitive information associated to the attribute, based on access control\n policies, the API consumer might have read only, write only, read/write, or no access at all\n to the attribute's value. In case the API consumer is not allowed to read the value of the security\n sensitive attribute, the attribute shall be omitted when the information is to be provided\n in a response message.\n",
+ "description": "This type represents attribute modifications that were performed on an Individual NFV-MANO service interface\" resource. The attributes that can be included consist of those requested to be modified explicitly in the \"ManoServiceInterfaceModificationRequest\" data structure. If applicable, additional attributes of the \"ManoServiceInterface\" data structure that were modified implicitly shall also be provided. * NOTE:\tDue to the security sensitive information associated to the attribute, based on access control\n policies, the API consumer might have read only, write only, read/write, or no access at all\n to the attribute's value. In case the API consumer is not allowed to read the value of the security\n sensitive attribute, the attribute shall be omitted when the information is to be provided\n in a response message.\n",
"type": "object",
"properties": {
"name": {
- "description": "If present, this attribute signals modifications of the \"name\" attribute in \"ManoServiceInterface\", as defined in clause 5.6.2.11.\n",
+ "description": "If present, this attribute signals modifications of the \"name\" attribute in \"ManoServiceInterface\", as defined in clause 5.6.2.11.\n",
"type": "string"
},
"apiRoot": {
@@ -15,7 +15,7 @@
"type": "string"
},
"securityInfo": {
- "description": "This type represents security related information of an NFV-MANO service interface produced by an NFV-MANO functional entity. * NOTE:\tProvided configuration of the OAuth 2.0 authorization server information and configuration\n shall be supported, and dynamic configuration may be supported.\n",
+ "description": "This type represents security related information of an NFV-MANO service interface produced by an NFV-MANO functional entity. * NOTE:\tProvided configuration of the OAuth 2.0 authorization server information and configuration\n shall be supported, and dynamic configuration may be supported.\n",
"type": "object",
"required": [
"authType",
@@ -23,12 +23,13 @@
],
"properties": {
"authType": {
- "description": "Type of API request authorization to be used by the API producer.\nThe support of authorization methods for the API producer is specified in clause 8.3.6 of ETSI GS NFV-SOL 013.\nPermitted values:\n - TLS_TUNNEL: Using TLS tunnel, as defined by TLS 1.2 in IETF RFC 5246.\n - OAUTH2: Using access token, as defined by the OAuth 2.0 specification \n in IETF RFC 6749. \n",
+ "description": "Type of API request authorization to be used by the API producer.\nThe support of authorization methods for the API producer is specified in clause 8.3.6 of ETSI GS NFV-SOL 013.\nPermitted values:\n - TLS_TUNNEL: Using TLS tunnel, as defined by TLS 1.2 in IETF RFC 5246.\n - TLS_TUNNEL_13: Using TLS tunnel, as defined by TLS 1.3 in IETF RFC 8446.\n - OAUTH2: Using access token, as defined by the OAuth 2.0 specification\n in IETF RFC 6749.\n",
"type": "array",
"items": {
"type": "string",
"enum": [
"TLS_TUNNEL",
+ "TLS_TUNNEL_13",
"OAUTH2"
]
},
@@ -43,7 +44,7 @@
],
"properties": {
"dynamicDiscovery": {
- "description": "Configuration data used when performing dynamic discovery of the authorization server identifier. See note.\n",
+ "description": "Configuration data used when performing dynamic discovery of the authorization server identifier. See note.\n",
"type": "object",
"required": [
"webFingerHost"
@@ -79,11 +80,11 @@
}
},
"tlsTunnelInfo": {
- "description": "Information and configuration related to the use of TLS tunnel. Shall be present if authType contains \"TLS_TUNNEL\".\n",
+ "description": "Information and configuration related to the use of TLS tunnel. Shall be present if authType contains \"TLS_TUNNEL\".\n",
"type": "object",
"properties": {
"tlsTunnelCipherSuites": {
- "description": "List of cipher suites that shall be declared as supported by the API producer when performing the SSL or TLS negotiation with the API client. Valid values of cipher suites are defined in IETF RFC 8447.\n",
+ "description": "List of cipher suites that shall be declared as supported by the API producer when performing the SSL or TLS negotiation with the API client. Valid values of cipher suites are defined in IETF RFC 8447.\n",
"type": "array",
"items": {
"type": "string"
diff --git a/SOL009/NFVManoConfigurationAndInformationManagement-API/schemas/ManoServiceInterfaces.schema.json b/SOL009/NFVManoConfigurationAndInformationManagement-API/schemas/ManoServiceInterfaces.schema.json
index 8b6194d71ecbe2ac60e623fe027d1bb9d62dc577..14a4ea0d7f58a550c94af06a33113e784883d79c 100644
--- a/SOL009/NFVManoConfigurationAndInformationManagement-API/schemas/ManoServiceInterfaces.schema.json
+++ b/SOL009/NFVManoConfigurationAndInformationManagement-API/schemas/ManoServiceInterfaces.schema.json
@@ -1,7 +1,7 @@
{
- "type": "array",
+ "type": "array",
"items": {
- "description": "This type represents an individual NFV-MANO service interface produced by an NFV-MANO functional entity. * NOTE 1:\tThe information to be provided in this attribute shall relate to the specification and\n version of the specification. For instance, \"ETSI GS NFV-SOL 003 (V2.4.1)\".\n* NOTE 2:\tIf this attribute is not present, the value of this parameter is undefined. Overload is\n handled by the error handling schemes defined by the applicable API specification.\n* NOTE 3:\tDue to the security sensitive information associated to the attribute, based on access\n control policies, the API consumer might have read only, write only, read/write, or no access\n at all to the attribute's value. In case the API consumer is not allowed to read the value of\n the security sensitive attribute, the attribute shall be omitted when the information is to be\n provided in a response message, and shall be provided otherwise. In case the API consumer is\n not allowed to modify the value of the security sensitive attribute, and the modification request\n includes new attribute values, the whole modification request shall be rejected, and proper\n error information returned.\n",
+ "description": "This type represents an individual NFV-MANO service interface produced by an NFV-MANO functional entity. * NOTE 1:\tThe information to be provided in this attribute shall relate to the specification and\n version of the specification. For instance, \"ETSI GS NFV-SOL 003 (V2.4.1)\".\n* NOTE 2:\tIf this attribute is not present, the value of this parameter is undefined. Overload is\n handled by the error handling schemes defined by the applicable API specification.\n* NOTE 3:\tDue to the security sensitive information associated to the attribute, based on access\n control policies, the API consumer might have read only, write only, read/write, or no access\n at all to the attribute's value. In case the API consumer is not allowed to read the value of\n the security sensitive attribute, the attribute shall be omitted when the information is to be\n provided in a response message, and shall be provided otherwise. In case the API consumer is\n not allowed to modify the value of the security sensitive attribute, and the modification request\n includes new attribute values, the whole modification request shall be rejected, and proper\n error information returned.\n",
"type": "object",
"required": [
"id",
@@ -24,7 +24,7 @@
"type": "string"
},
"type": {
- "description": "Type of the NFV-MANO service interface produced by the NFV-MANO functional entity. Valid values are defined in clause 5.6.4.3.\n",
+ "description": "Type of the NFV-MANO service interface produced by the NFV-MANO functional entity. Valid values are defined in clause 5.6.4.3.\n",
"type": "string"
},
"standardVersion": {
@@ -48,11 +48,11 @@
"type": "string"
},
"apiName": {
- "description": "Indicates the interface name in an abbreviated form. Shall be present for ETSI NFV specified RESTful NFV-MANO APIs. The {apiName} of each interface is defined in the standard the interface is compliant to (see also clause 4.1 of ETSI GS NFV-SOL 013). May be present otherwise.\n",
+ "description": "Indicates the interface name in an abbreviated form. Shall be present for ETSI NFV specified RESTful NFV-MANO APIs. The {apiName} of each interface is defined in the standard the interface is compliant to (see also clause 4.1 of ETSI GS NFV-SOL 013). May be present otherwise.\n",
"type": "string"
},
"apiMajorVersion": {
- "description": "Indicates the current major version of the API. Shall be present for ETSI NFV specified RESTful NFV-MANO APIs. The major version is defined in the standard the interface is compliant to (see also clause 4.1 of ETSI GS NFV-SOL 013). May be present otherwise.\n",
+ "description": "Indicates the current major version of the API. Shall be present for ETSI NFV specified RESTful NFV-MANO APIs. The major version is defined in the standard the interface is compliant to (see also clause 4.1 of ETSI GS NFV-SOL 013). May be present otherwise.\n",
"type": "string"
},
"apiUri": {
@@ -93,7 +93,7 @@
"description": "State of the NFV-MANO service interface.\n",
"properties": {
"operationalState": {
- "description": "The enumeration InterfaceOperationalStateEnumType defines values representing the operational state of an NFV-MANO service interface type of managed entity. The InterfaceOperationalStateEnumType shall comply with the provisions :\n - STARTED\tThe managed entity is operational.\n - STOPPED\tThe managed entity is not operational.\n - STOPPING\tThe managed entity is in the transition to stop.\n - STARTING\tThe managed entity is in the transition to start and become operational.\n",
+ "description": "The enumeration InterfaceOperationalStateEnumType defines values representing the operational state of an NFV-MANO service interface type of managed entity. The InterfaceOperationalStateEnumType shall comply with the provisions :\n - STARTED\tThe managed entity is operational.\n - STOPPED\tThe managed entity is not operational.\n - STOPPING\tThe managed entity is in the transition to stop.\n - STARTING\tThe managed entity is in the transition to start and become operational.\n",
"type": "string",
"enum": [
"STARTED",
@@ -112,7 +112,7 @@
]
},
"usageState": {
- "description": "The enumeration UsageStateEnumType defines values representing the usage state of a managed entity. The UsageStateEnumType shall comply with the provisions:\n - IN_USE\tThe managed entity is currently being used.\n - NOT_IN_USE\tThe managed entity is currently not being used.\n",
+ "description": "The enumeration UsageStateEnumType defines values representing the usage state of a managed entity. The UsageStateEnumType shall comply with the provisions:\n - IN_USE\tThe managed entity is currently being used.\n - NOT_IN_USE\tThe managed entity is currently not being used.\n",
"type": "string",
"enum": [
"IN_USE",
@@ -127,7 +127,7 @@
]
},
"securityInfo": {
- "description": "This type represents security related information of an NFV-MANO service interface produced by an NFV-MANO functional entity. * NOTE:\tProvided configuration of the OAuth 2.0 authorization server information and configuration\n shall be supported, and dynamic configuration may be supported.\n",
+ "description": "This type represents security related information of an NFV-MANO service interface produced by an NFV-MANO functional entity. * NOTE:\tProvided configuration of the OAuth 2.0 authorization server information and configuration\n shall be supported, and dynamic configuration may be supported.\n",
"type": "object",
"required": [
"authType",
@@ -135,12 +135,13 @@
],
"properties": {
"authType": {
- "description": "Type of API request authorization to be used by the API producer.\nThe support of authorization methods for the API producer is specified in clause 8.3.6 of ETSI GS NFV-SOL 013.\nPermitted values:\n - TLS_TUNNEL: Using TLS tunnel, as defined by TLS 1.2 in IETF RFC 5246.\n - OAUTH2: Using access token, as defined by the OAuth 2.0 specification \n in IETF RFC 6749. \n",
+ "description": "Type of API request authorization to be used by the API producer.\nThe support of authorization methods for the API producer is specified in clause 8.3.6 of ETSI GS NFV-SOL 013.\nPermitted values:\n - TLS_TUNNEL: Using TLS tunnel, as defined by TLS 1.2 in IETF RFC 5246.\n - TLS_TUNNEL_13: Using TLS tunnel, as defined by TLS 1.3 in IETF RFC 8446.\n - OAUTH2: Using access token, as defined by the OAuth 2.0 specification\n in IETF RFC 6749.\n",
"type": "array",
"items": {
"type": "string",
"enum": [
"TLS_TUNNEL",
+ "TLS_TUNNEL_13",
"OAUTH2"
]
},
@@ -155,7 +156,7 @@
],
"properties": {
"dynamicDiscovery": {
- "description": "Configuration data used when performing dynamic discovery of the authorization server identifier. See note.\n",
+ "description": "Configuration data used when performing dynamic discovery of the authorization server identifier. See note.\n",
"type": "object",
"required": [
"webFingerHost"
@@ -191,11 +192,11 @@
}
},
"tlsTunnelInfo": {
- "description": "Information and configuration related to the use of TLS tunnel. Shall be present if authType contains \"TLS_TUNNEL\".\n",
+ "description": "Information and configuration related to the use of TLS tunnel. Shall be present if authType contains \"TLS_TUNNEL\".\n",
"type": "object",
"properties": {
"tlsTunnelCipherSuites": {
- "description": "List of cipher suites that shall be declared as supported by the API producer when performing the SSL or TLS negotiation with the API client. Valid values of cipher suites are defined in IETF RFC 8447.\n",
+ "description": "List of cipher suites that shall be declared as supported by the API producer when performing the SSL or TLS negotiation with the API client. Valid values of cipher suites are defined in IETF RFC 8447.\n",
"type": "array",
"items": {
"type": "string"
diff --git a/SOL009/NFVManoConfigurationAndInformationManagement-API/schemas/PeerEntities.schema.json b/SOL009/NFVManoConfigurationAndInformationManagement-API/schemas/PeerEntities.schema.json
index 34582033f9db04cb526d2bf418b2c204f3d76c80..12b4645badc2b495f13adc9be5b4256cef34aa39 100644
--- a/SOL009/NFVManoConfigurationAndInformationManagement-API/schemas/PeerEntities.schema.json
+++ b/SOL009/NFVManoConfigurationAndInformationManagement-API/schemas/PeerEntities.schema.json
@@ -1,166 +1,230 @@
{
"type": "array",
"items": {
- "description": "This type represents an individual peer entity. * NOTE 1:\tThe value of the \"peerEntityId\" attribute is the same as the value of the \"id\" attribute in the\n \"ManoEntity\" of the corresponding NFV-MANO functional entity that acts as peer entity, and shall\n follow the uniqueness requirements set out in clause 5.6.2.2 for the \"id\" attribute.\n* NOTE 2:\tETSI GS NFV-IFA 031 [1] defines an additional attribute named \"apiDiscoveryEndpoint\" in the\n PeerManoEntity. The modelling of this attribute is not specified in the present document version.\n",
- "type": "object",
- "required": ["id", "peerEntityId", "name", "type", "peerEntityState"],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
+ "description": "This type represents an individual peer entity. * NOTE 1:\tThe value of the \"peerEntityId\" attribute is the same as the value of the \"id\" attribute in the\n \"ManoEntity\" of the corresponding NFV-MANO functional entity that acts as peer entity, and shall\n follow the uniqueness requirements set out in clause 5.6.2.2 for the \"id\" attribute.\n* NOTE 2: With this information, the NFVO has available information about the set of VIMs and associated VIM\n connection information that have been configured into the VNFM.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "peerEntityId",
+ "name",
+ "type",
+ "peerEntityState"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "peerEntityId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "name": {
+ "description": "Human-readable name of the peer functional entity.\nThis attribute can be modified with the PATCH method.\n",
+ "type": "string"
+ },
+ "type": {
+ "description": "The enumeration PeerEntityEnumType defines the permitted values to represent peer functional entities. it shall complains with the provisions : - NFVO\tThe peer functional entity is an NFVO. - VNFM\tThe peer functional entity is a VNFM. - VIM\t The peer functional entity is a VIM. - WIM\t The peer functional entity is a WIM. - CISM The peer functional entity is a CISM. - CIR The NFV-MANO functional entity is a CIR. - CCM The NFV-MANO functional entity is a CCM. - EM\t The peer functional entity is an EM. - OSS\t The peer functional entity is an OSS/BSS.\n",
+ "type": "string",
+ "enum": [
+ "NFVO",
+ "VNFM",
+ "VIM",
+ "WIM",
+ "CISM",
+ "CIR",
+ "CCM",
+ "EM",
+ "OSS"
+ ]
+ },
+ "description": {
+ "description": "Human-readable description of the peer functional entity.\nThis attribute can be modified with the PATCH method.\n",
+ "type": "string"
+ },
+ "consumedManoInterfaces": {
+ "description": "Information of the interface consumed by the NFV-MANO functional entity from the peer functional entity.\nThis attribute can be modified with the PATCH method.\nThe keys of the map, each of which identifies information about a particular consumed NFV-MANO interface, are managed by the API consumer and referenced from other data structures via the \"consumedManoInterfaceIds\" attribute.\n",
+ "type": "object"
+ },
+ "vimConnectionInfos": {
+ "description": "Map of VIM connection information. The VimConnectionInfo is specified in clause 4.4.1.6 of ETSI GS NFV-SOL 003. This attribute can be modified with the PATCH method. May be present only if the \"type\" attribute in the \"PeerEntity” is either a \"VIM\", a \"CISM\" or a \"CIR\", and the NFV-MANO entity being configured is a \"VNFM\" or \"NFVO\" as indicated by the \"type\" attribute in the \"ManoEntity\". In case it is present, the value of the \"vimId\" in the \"VimConnectionInfo\" shall be equal to the value of \"peerEntityId\". In addition, the content of \"interfaceInfo\", \"accessInfo” and \"extra\" (if applicable) of the “VimConnectionInfo\" shall be provided by means in scope of the present document.\n",
+ "type": "array",
+ "items": {
+ "type": "object"
+ }
+ },
+ "vnfmConfiguredVimConnectionInfoIds": {
+ "description": "List of VIM connection information identifiers that identify the set of VIMs and associated VIM connection information that have been configured into the VNFM whose identifier is equal to the “peerEntityId“. See note 2. Only applicable if the \"type” attribute in the \"ManoEntity\" is \"NFVO\" and the \"type” attribute in the \"PeerEntity\" is a \"VNFM\".\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "additionalProperties": {
+ "description": "This type represents an interface consumed by the producer NFV MANO functional entity from another peer functional entity. * NOTE 1:\tThe information to be provided in this attribute shall relate to the specification and its version.\n For instance, \"ETSI GS NFV-SOL 003 (V2.4.1)\".\n* NOTE 2:\tDue to the security sensitive information associated to the attribute, based on access control\n policies, the API consumer might have read only, write only, read/write, or no access at all to\n the attribute's value. In case the API consumer is not allowed to read the value of the security\n sensitive attribute, the attribute shall be omitted when the information is to be provided in a\n response message, and shall be provided otherwise. In case the API consumer is not allowed to\n modify the value of the security sensitive attribute, and the modification request includes new\n attribute values, the whole modification request shall be rejected, and proper error information returned.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "name",
+ "type",
+ "standardVersion",
+ "apiVersion",
+ "apiEndpoint"
+ ],
+ "properties": {
+ "name": {
+ "description": "Human-readable name of the NFV-MANO interface.\n",
"type": "string"
- },
- "peerEntityId": {
- "description": "An identifier with the intention of being globally unique.\n",
+ },
+ "type": {
+ "description": "Type of the NFV-MANO service interface consumed by the NFV-MANO functional entity. Valid values are defined in clause 5.6.4.3.\n",
"type": "string"
- },
- "name": {
- "description": "Human-readable name of the peer functional entity.\nThis attribute can be modified with the PATCH method.\n",
+ },
+ "standardVersion": {
+ "description": "A version.\n",
"type": "string"
- },
- "type": {
- "description": "The enumeration PeerEntityEnumType defines the permitted values to represent peer functional entities. it shall complains with the provisions : - NFVO\tThe peer functional entity is an NFVO. - VNFM\tThe peer functional entity is a VNFM. - VIM\t The peer functional entity is a VIM. - WIM\t The peer functional entity is a WIM. - CISM The peer functional entity is a CISM. - EM\t The peer functional entity is an EM. - OSS\t The peer functional entity is an OSS/BSS.\n",
- "type": "string",
- "enum": ["NFVO", "VNFM", "VIM", "WIM", "CISM", "EM", "OSS"]
- },
- "description": {
- "description": "Human-readable description of the peer functional entity.\nThis attribute can be modified with the PATCH method.\n",
+ },
+ "apiVersion": {
+ "description": "A version.\n",
"type": "string"
- },
- "consumedManoInterfaces": {
- "description": "Information of the interface consumed by the NFV-MANO functional entity from the peer functional entity.\nThis attribute can be modified with the PATCH method.\nThe keys of the map, each of which identifies information about a particular consumed NFV-MANO interface, are managed by the API consumer and referenced from other data structures via the \"consumedManoInterfaceIds\" attribute.\n",
+ },
+ "apiEndpoint": {
+ "description": "Consumable API endpoint of the interface. It provides the information relevant about the protocol, host and port, and path where the interface API can be accessed.\n",
"type": "object",
- "additionalProperties": {
- "description": "This type represents an interface consumed by the producer NFV MANO functional entity from another peer functional entity. * NOTE 1:\tThe information to be provided in this attribute shall relate to the specification and its version.\n For instance, \"ETSI GS NFV-SOL 003 (V2.4.1)\".\n* NOTE 2:\tDue to the security sensitive information associated to the attribute, based on access control\n policies, the API consumer might have read only, write only, read/write, or no access at all to\n the attribute's value. In case the API consumer is not allowed to read the value of the security\n sensitive attribute, the attribute shall be omitted when the information is to be provided in a\n response message, and shall be provided otherwise. In case the API consumer is not allowed to\n modify the value of the security sensitive attribute, and the modification request includes new\n attribute values, the whole modification request shall be rejected, and proper error information returned.\n",
+ "properties": {
+ "apiRoot": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ },
+ "apiName": {
+ "description": "Indicates the interface name in an abbreviated form. Shall be present for ETSI NFV specified RESTful NFV-MANO APIs. The {apiName} of each interface is defined in the standard the interface is compliant to (see also clause 4.1 of ETSI GS NFV-SOL 013). May be present otherwise.\n",
+ "type": "string"
+ },
+ "apiMajorVersion": {
+ "description": "Indicates the current major version of the API. Shall be present for ETSI NFV specified RESTful NFV-MANO APIs. The major version is defined in the standard the interface is compliant to (see also clause 4.1 of ETSI GS NFV-SOL 013). May be present otherwise.\n",
+ "type": "string"
+ },
+ "apiUri": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ }
+ },
+ "required": [
+ "apiUri"
+ ]
+ },
+ "securityInfo": {
+ "description": "This type represents security related information for accessing an NFV-MANO service interface produced by an NFV-MANO functional entity. * NOTE:\tProvided configuration of the OAuth 2.0 authorization server information and configuration\n shall be supported, and dynamic configuration may be supported.\n",
+ "type": "object",
+ "required": [
+ "authType",
+ "oauthServerInfo"
+ ],
+ "properties": {
+ "authType": {
+ "description": "Type of API request authorization to be used by the API consumer accessing the API.\nThe support of authorization methods for the API consumer is specified in clause 8.3.6 of ETSI GS NFV-SOL 013.\nPermitted values: - TLS_TUNNEL: Using TLS tunnel, as defined by TLS 1.2 in IETF RFC 5246. - TLS_TUNNEL_13: Using TLS tunnel, as defined by TLS 1.3 in IETF RFC 8446. - OAUTH2: Using access token, as defined by the OAuth 2.0 specification in IETF RFC 6749.\n",
+ "type": "array",
+ "items": {
+ "type": "string",
+ "enum": [
+ "TLS_TUNNEL",
+ "TLS_TUNNEL_13",
+ "OAUTH2"
+ ]
+ },
+ "minItems": 1
+ },
+ "oauthServerInfo": {
+ "description": "OAuth 2.0 authorization server information and configuration.\n",
+ "type": "object",
+ "properties": {
+ "dynamicDiscovery": {
+ "description": "Configuration data used when performing dynamic discovery of the authorization server identifier. See note.\n",
+ "type": "object",
+ "required": [
+ "webFingerHost"
+ ],
+ "properties": {
+ "webFingerHost": {
+ "description": "Server where the WebFinger service is hosted. When used, the request to the WebFinger resource shall conform as specified in clause 5.1.3 of ETSI GS NFV-SEC 022.\n",
+ "type": "string",
+ "format": "uri"
+ }
+ }
+ },
+ "providedConfiguration": {
+ "description": "Configuration data used to setup the authorization server identifier. See note.\n",
+ "type": "object",
+ "required": [
+ "authServerId"
+ ],
+ "properties": {
+ "authServerId": {
+ "description": "Authorization server identifier as defined in ETSI GS NFV-SEC 022.\n",
+ "type": "string",
+ "format": "uri"
+ }
+ }
+ },
+ "tlsCipherSuites": {
+ "description": "List of cipher suites that shall be declared as supported by the API consumer when performing the SSL or TLS negotiation with the authorization server. Valid values of cipher suites are defined in IETF RFC 8447.\n",
+ "type": "array",
+ "items": {
+ "type": "string",
+ "minItems": 1
+ }
+ }
+ }
+ },
+ "tlsTunnelInfo": {
+ "description": "Information and configuration related to the use of TLS tunnel. Shall be present if authType contains \"TLS_TUNNEL\".\n",
"type": "object",
- "required": ["id", "name", "type", "standardVersion", "apiVersion", "apiEndpoint"],
"properties": {
- "name": {
- "description": "Human-readable name of the NFV-MANO interface.\n",
- "type": "string"
- },
- "type": {
- "description": "Type of the NFV-MANO service interface consumed by the NFV-MANO functional entity. Valid values are defined in clause 5.6.4.3.\n",
- "type": "string"
- },
- "standardVersion": {
- "description": "A version.\n",
- "type": "string"
- },
- "apiVersion": {
- "description": "A version.\n",
- "type": "string"
- },
- "apiEndpoint": {
- "description": "Consumable API endpoint of the interface. It provides the information relevant about the protocol, host and port, and path where the interface API can be accessed.\n",
- "type": "object",
- "properties": {
- "apiRoot": {
- "description": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- },
- "apiName": {
- "description": "Indicates the interface name in an abbreviated form. Shall be present for ETSI NFV specified RESTful NFV-MANO APIs. The {apiName} of each interface is defined in the standard the interface is compliant to (see also clause 4.1 of ETSI GS NFV-SOL 013). May be present otherwise.\n",
- "type": "string"
- },
- "apiMajorVersion": {
- "description": "Indicates the current major version of the API. Shall be present for ETSI NFV specified RESTful NFV-MANO APIs. The major version is defined in the standard the interface is compliant to (see also clause 4.1 of ETSI GS NFV-SOL 013). May be present otherwise.\n",
- "type": "string"
- },
- "apiUri": {
- "description": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- }
- },
- "required": ["apiUri"]
- },
- "securityInfo": {
- "description": "This type represents security related information for accessing an NFV-MANO service interface produced by an NFV-MANO functional entity. * NOTE:\tProvided configuration of the OAuth 2.0 authorization server information and configuration\n shall be supported, and dynamic configuration may be supported.\n",
- "type": "object",
- "required": ["authType", "oauthServerInfo"],
- "properties": {
- "authType": {
- "description": "Type of API request authorization to be used by the API consumer accessing the API.\nThe support of authorization methods for the API consumer is specified in clause 8.3.6 of ETSI GS NFV-SOL 013.\nPermitted values: - TLS_TUNNEL: Using TLS tunnel, as defined by TLS 1.2 in IETF RFC 5246. - OAUTH2: Using access token, as defined by the OAuth 2.0 specification in IETF RFC 6749.\n",
- "type": "array",
- "items": {
- "type": "string",
- "enum": ["TLS_TUNNEL", "OAUTH2"]
- },
- "minItems": 1
- },
- "oauthServerInfo": {
- "description": "OAuth 2.0 authorization server information and configuration.\n",
- "type": "object",
- "properties": {
- "dynamicDiscovery": {
- "description": "Configuration data used when performing dynamic discovery of the authorization server identifier. See note.\n",
- "type": "object",
- "required": ["webFingerHost"],
- "properties": {
- "webFingerHost": {
- "description": "Server where the WebFinger service is hosted. When used, the request to the WebFinger resource shall conform as specified in clause 5.1.3 of ETSI GS NFV-SEC 022.\n",
- "type": "string",
- "format": "uri"
- }
- }
- },
- "providedConfiguration": {
- "description": "Configuration data used to setup the authorization server identifier. See note.\n",
- "type": "object",
- "required": ["authServerId"],
- "properties": {
- "authServerId": {
- "description": "Authorization server identifier as defined in ETSI GS NFV-SEC 022.\n",
- "type": "string",
- "format": "uri"
- }
- }
- },
- "tlsCipherSuites": {
- "description": "List of cipher suites that shall be declared as supported by the API consumer when performing the SSL or TLS negotiation with the authorization server. Valid values of cipher suites are defined in IETF RFC 8447.\n",
- "type": "array",
- "items": {
- "type": "string",
- "minItems": 1
- }
- }
- }
- },
- "tlsTunnelInfo": {
- "description": "Information and configuration related to the use of TLS tunnel. Shall be present if authType contains \"TLS_TUNNEL\".\n",
- "type": "object",
- "properties": {
- "tlsTunnelCipherSuites": {
- "description": "List of cipher suites that shall be declared as supported by the API consumer when performing the SSL or TLS negotiation with the API producer. Valid values of cipher suites are defined in IETF RFC 8447.\n",
- "type": "array",
- "items": {
- "type": "string",
- "minItems": 1
- }
- }
- }
- }
- }
+ "tlsTunnelCipherSuites": {
+ "description": "List of cipher suites that shall be declared as supported by the API consumer when performing the SSL or TLS negotiation with the API producer. Valid values of cipher suites are defined in IETF RFC 8447.\n",
+ "type": "array",
+ "items": {
+ "type": "string",
+ "minItems": 1
}
+ }
}
+ }
}
+ }
+ }
+ }
+ },
+ "peerEntityState": {
+ "description": "State of the peer functional entity as provided by the API consumer when creating the resource or when updating it with the PATCH method.\n",
+ "type": "object",
+ "properties": {
+ "operationalState": {
+ "description": "The enumeration OperationalStateEnumType defines values representing the operational state of an NFV-MANO functional application type of managed entity. The OperationalStateEnumType shall comply with the provisions:\n - STARTED\tThe managed entity is operational.\n - STOPPED\tThe managed entity is not operational.\n - STOPPING\tThe managed entity is in the transition to stop.\n - STARTING\tThe managed entity is in the transition to start and become operational.\n - RESTARTING\tThe managed entity is in the transition to stop and start again.\n",
+ "type": "string",
+ "enum": [
+ "STARTED",
+ "STOPPED",
+ "STOPPING",
+ "STARTING",
+ "RESTARTING"
+ ]
},
- "peerEntityState": {
- "description": "State of the peer functional entity as provided by the API consumer when creating the resource or when updating it with the PATCH method.\n",
- "type": "object",
- "properties": {
- "operationalState": {
- "description": "The enumeration OperationalStateEnumType defines values representing the operational state of an NFV-MANO functional application type of managed entity. The OperationalStateEnumType shall comply with the provisions:\n - STARTED\tThe managed entity is operational.\n - STOPPED\tThe managed entity is not operational.\n - STOPPING\tThe managed entity is in the transition to stop.\n - STARTING\tThe managed entity is in the transition to start and become operational.\n - RESTARTING\tThe managed entity is in the transition to stop and start again.\n",
- "type": "string",
- "enum": ["STARTED", "STOPPED", "STOPPING", "STARTING", "RESTARTING"]
- },
- "administrativeState": {
- "description": "The enumeration AdministrativeStateEnumType defines values representing the administrative state of a managed entity. The AdministrativeStateEnumType shall comply with the provisions:\n - LOCKED\tThe managed entity is administratively prohibited to be used.\n - UNLOCKED\tThe managed entity is administratively allowed to be used.\n - LOCKING\tThe managed entity is in the transition to be locked.\n",
- "type": "string",
- "enum": ["LOCKED", "UNLOCKED", "LOCKING"]
- }
- },
- "required": ["operationalState", "administrativeState"]
+ "administrativeState": {
+ "description": "The enumeration AdministrativeStateEnumType defines values representing the administrative state of a managed entity. The AdministrativeStateEnumType shall comply with the provisions:\n - LOCKED\tThe managed entity is administratively prohibited to be used.\n - UNLOCKED\tThe managed entity is administratively allowed to be used.\n - LOCKING\tThe managed entity is in the transition to be locked.\n",
+ "type": "string",
+ "enum": [
+ "LOCKED",
+ "UNLOCKED",
+ "LOCKING"
+ ]
}
+ },
+ "required": [
+ "operationalState",
+ "administrativeState"
+ ]
}
+ }
}
-}
\ No newline at end of file
+ }
\ No newline at end of file
diff --git a/SOL009/NFVManoConfigurationAndInformationManagement-API/schemas/PeerEntity.schema.json b/SOL009/NFVManoConfigurationAndInformationManagement-API/schemas/PeerEntity.schema.json
index c7b3a60d1f62eb532bf364575361d781187a4f65..24ae5429928335e9c638299afc1cccb078df34fb 100644
--- a/SOL009/NFVManoConfigurationAndInformationManagement-API/schemas/PeerEntity.schema.json
+++ b/SOL009/NFVManoConfigurationAndInformationManagement-API/schemas/PeerEntity.schema.json
@@ -1,7 +1,13 @@
{
- "description": "This type represents an individual peer entity. * NOTE 1:\tThe value of the \"peerEntityId\" attribute is the same as the value of the \"id\" attribute in the\n \"ManoEntity\" of the corresponding NFV-MANO functional entity that acts as peer entity, and shall\n follow the uniqueness requirements set out in clause 5.6.2.2 for the \"id\" attribute.\n* NOTE 2:\tETSI GS NFV-IFA 031 [1] defines an additional attribute named \"apiDiscoveryEndpoint\" in the\n PeerManoEntity. The modelling of this attribute is not specified in the present document version.\n",
+ "description": "This type represents an individual peer entity. * NOTE 1:\tThe value of the \"peerEntityId\" attribute is the same as the value of the \"id\" attribute in the\n \"ManoEntity\" of the corresponding NFV-MANO functional entity that acts as peer entity, and shall\n follow the uniqueness requirements set out in clause 5.6.2.2 for the \"id\" attribute.\n* NOTE 2: With this information, the NFVO has available information about the set of VIMs and associated VIM\n connection information that have been configured into the VNFM.\n",
"type": "object",
- "required": ["id", "peerEntityId", "name", "type", "peerEntityState"],
+ "required": [
+ "id",
+ "peerEntityId",
+ "name",
+ "type",
+ "peerEntityState"
+ ],
"properties": {
"id": {
"description": "An identifier with the intention of being globally unique.\n",
@@ -16,9 +22,19 @@
"type": "string"
},
"type": {
- "description": "The enumeration PeerEntityEnumType defines the permitted values to represent peer functional entities. it shall complains with the provisions : - NFVO\tThe peer functional entity is an NFVO. - VNFM\tThe peer functional entity is a VNFM. - VIM\t The peer functional entity is a VIM. - WIM\t The peer functional entity is a WIM. - CISM The peer functional entity is a CISM. - EM\t The peer functional entity is an EM. - OSS\t The peer functional entity is an OSS/BSS.\n",
+ "description": "The enumeration PeerEntityEnumType defines the permitted values to represent peer functional entities. it shall complains with the provisions : - NFVO\tThe peer functional entity is an NFVO. - VNFM\tThe peer functional entity is a VNFM. - VIM\t The peer functional entity is a VIM. - WIM\t The peer functional entity is a WIM. - CISM The peer functional entity is a CISM. - CIR The NFV-MANO functional entity is a CIR. - CCM The NFV-MANO functional entity is a CCM. - EM\t The peer functional entity is an EM. - OSS\t The peer functional entity is an OSS/BSS.\n",
"type": "string",
- "enum": ["NFVO", "VNFM", "VIM", "WIM", "CISM", "EM", "OSS"]
+ "enum": [
+ "NFVO",
+ "VNFM",
+ "VIM",
+ "WIM",
+ "CISM",
+ "CIR",
+ "CCM",
+ "EM",
+ "OSS"
+ ]
},
"description": {
"description": "Human-readable description of the peer functional entity.\nThis attribute can be modified with the PATCH method.\n",
@@ -26,11 +42,33 @@
},
"consumedManoInterfaces": {
"description": "Information of the interface consumed by the NFV-MANO functional entity from the peer functional entity.\nThis attribute can be modified with the PATCH method.\nThe keys of the map, each of which identifies information about a particular consumed NFV-MANO interface, are managed by the API consumer and referenced from other data structures via the \"consumedManoInterfaceIds\" attribute.\n",
- "type": "object",
+ "type": "object"
+ },
+ "vimConnectionInfos": {
+ "description": "Map of VIM connection information. The VimConnectionInfo is specified in clause 4.4.1.6 of ETSI GS NFV-SOL 003. This attribute can be modified with the PATCH method. May be present only if the \"type\" attribute in the \"PeerEntity” is either a \"VIM\", a \"CISM\" or a \"CIR\", and the NFV-MANO entity being configured is a \"VNFM\" or \"NFVO\" as indicated by the \"type\" attribute in the \"ManoEntity\". In case it is present, the value of the \"vimId\" in the \"VimConnectionInfo\" shall be equal to the value of \"peerEntityId\". In addition, the content of \"interfaceInfo\", \"accessInfo” and \"extra\" (if applicable) of the “VimConnectionInfo\" shall be provided by means in scope of the present document.\n",
+ "type": "array",
+ "items": {
+ "type": "object"
+ }
+ },
+ "vnfmConfiguredVimConnectionInfoIds": {
+ "description": "List of VIM connection information identifiers that identify the set of VIMs and associated VIM connection information that have been configured into the VNFM whose identifier is equal to the “peerEntityId“. See note 2. Only applicable if the \"type” attribute in the \"ManoEntity\" is \"NFVO\" and the \"type” attribute in the \"PeerEntity\" is a \"VNFM\".\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
"additionalProperties": {
"description": "This type represents an interface consumed by the producer NFV MANO functional entity from another peer functional entity. * NOTE 1:\tThe information to be provided in this attribute shall relate to the specification and its version.\n For instance, \"ETSI GS NFV-SOL 003 (V2.4.1)\".\n* NOTE 2:\tDue to the security sensitive information associated to the attribute, based on access control\n policies, the API consumer might have read only, write only, read/write, or no access at all to\n the attribute's value. In case the API consumer is not allowed to read the value of the security\n sensitive attribute, the attribute shall be omitted when the information is to be provided in a\n response message, and shall be provided otherwise. In case the API consumer is not allowed to\n modify the value of the security sensitive attribute, and the modification request includes new\n attribute values, the whole modification request shall be rejected, and proper error information returned.\n",
"type": "object",
- "required": ["id", "name", "type", "standardVersion", "apiVersion", "apiEndpoint"],
+ "required": [
+ "id",
+ "name",
+ "type",
+ "standardVersion",
+ "apiVersion",
+ "apiEndpoint"
+ ],
"properties": {
"name": {
"description": "Human-readable name of the NFV-MANO interface.\n",
@@ -69,19 +107,28 @@
"type": "string"
}
},
- "required": ["apiUri"]
+ "required": [
+ "apiUri"
+ ]
},
"securityInfo": {
"description": "This type represents security related information for accessing an NFV-MANO service interface produced by an NFV-MANO functional entity. * NOTE:\tProvided configuration of the OAuth 2.0 authorization server information and configuration\n shall be supported, and dynamic configuration may be supported.\n",
"type": "object",
- "required": ["authType", "oauthServerInfo"],
+ "required": [
+ "authType",
+ "oauthServerInfo"
+ ],
"properties": {
"authType": {
- "description": "Type of API request authorization to be used by the API consumer accessing the API.\nThe support of authorization methods for the API consumer is specified in clause 8.3.6 of ETSI GS NFV-SOL 013.\nPermitted values: - TLS_TUNNEL: Using TLS tunnel, as defined by TLS 1.2 in IETF RFC 5246. - OAUTH2: Using access token, as defined by the OAuth 2.0 specification in IETF RFC 6749.\n",
+ "description": "Type of API request authorization to be used by the API consumer accessing the API.\nThe support of authorization methods for the API consumer is specified in clause 8.3.6 of ETSI GS NFV-SOL 013.\nPermitted values: - TLS_TUNNEL: Using TLS tunnel, as defined by TLS 1.2 in IETF RFC 5246. - TLS_TUNNEL_13: Using TLS tunnel, as defined by TLS 1.3 in IETF RFC 8446. - OAUTH2: Using access token, as defined by the OAuth 2.0 specification in IETF RFC 6749.\n",
"type": "array",
"items": {
"type": "string",
- "enum": ["TLS_TUNNEL", "OAUTH2"]
+ "enum": [
+ "TLS_TUNNEL",
+ "TLS_TUNNEL_13",
+ "OAUTH2"
+ ]
},
"minItems": 1
},
@@ -92,7 +139,9 @@
"dynamicDiscovery": {
"description": "Configuration data used when performing dynamic discovery of the authorization server identifier. See note.\n",
"type": "object",
- "required": ["webFingerHost"],
+ "required": [
+ "webFingerHost"
+ ],
"properties": {
"webFingerHost": {
"description": "Server where the WebFinger service is hosted. When used, the request to the WebFinger resource shall conform as specified in clause 5.1.3 of ETSI GS NFV-SEC 022.\n",
@@ -104,7 +153,9 @@
"providedConfiguration": {
"description": "Configuration data used to setup the authorization server identifier. See note.\n",
"type": "object",
- "required": ["authServerId"],
+ "required": [
+ "authServerId"
+ ],
"properties": {
"authServerId": {
"description": "Authorization server identifier as defined in ETSI GS NFV-SEC 022.\n",
@@ -149,15 +200,28 @@
"operationalState": {
"description": "The enumeration OperationalStateEnumType defines values representing the operational state of an NFV-MANO functional application type of managed entity. The OperationalStateEnumType shall comply with the provisions:\n - STARTED\tThe managed entity is operational.\n - STOPPED\tThe managed entity is not operational.\n - STOPPING\tThe managed entity is in the transition to stop.\n - STARTING\tThe managed entity is in the transition to start and become operational.\n - RESTARTING\tThe managed entity is in the transition to stop and start again.\n",
"type": "string",
- "enum": ["STARTED", "STOPPED", "STOPPING", "STARTING", "RESTARTING"]
+ "enum": [
+ "STARTED",
+ "STOPPED",
+ "STOPPING",
+ "STARTING",
+ "RESTARTING"
+ ]
},
"administrativeState": {
"description": "The enumeration AdministrativeStateEnumType defines values representing the administrative state of a managed entity. The AdministrativeStateEnumType shall comply with the provisions:\n - LOCKED\tThe managed entity is administratively prohibited to be used.\n - UNLOCKED\tThe managed entity is administratively allowed to be used.\n - LOCKING\tThe managed entity is in the transition to be locked.\n",
"type": "string",
- "enum": ["LOCKED", "UNLOCKED", "LOCKING"]
+ "enum": [
+ "LOCKED",
+ "UNLOCKED",
+ "LOCKING"
+ ]
}
},
- "required": ["operationalState", "administrativeState"]
+ "required": [
+ "operationalState",
+ "administrativeState"
+ ]
}
}
}
\ No newline at end of file
diff --git a/SOL009/NFVManoConfigurationAndInformationManagement-API/schemas/PeerEntityConfigModifications.schema.json b/SOL009/NFVManoConfigurationAndInformationManagement-API/schemas/PeerEntityConfigModifications.schema.json
new file mode 100644
index 0000000000000000000000000000000000000000..3dc2ad392a247cac347451414c2e845a63d414dc
--- /dev/null
+++ b/SOL009/NFVManoConfigurationAndInformationManagement-API/schemas/PeerEntityConfigModifications.schema.json
@@ -0,0 +1,179 @@
+{
+ "description": "This type represents attribute modifications that were performed on an \"Individual peer entity\" resource. The attributes that can be included consist of those requested to be modified explicitly in the \"PeerEntityConfigModificationRequest\" data structure. If applicable, additional attributes of the \"PeerEntity\" data structure that were modified implicitly shall also be provided. * NOTE:\tDue to the security sensitive information contained within the attribute (refer to \"securityInfo\"\n within the \"ConsumedManoInterfaceInfo\" \" and \"accessInfo\" within the \"VimConnectionInfo\"), based \n on access control policies, the API consumer might have read only, write only, read/write, or no\n access at all to the attribute's value. In case the API consumer is not allowed to read the value \n of the security sensitive attribute, the attribute shall be omitted when the information is to be\n provided in a response message.\n",
+ "type": "object",
+ "properties": {
+ "name": {
+ "description": "If present, this attribute signals modifications of the \"name\" attribute in \"PeerEntity\", as defined in clause 5.6.2.15.\n",
+ "type": "string"
+ },
+ "description": {
+ "description": "If present, this attribute signals modifications of the \"description\" attribute in \"PeerEntity\", as defined in clause 5.6.2.15.\n",
+ "type": "string"
+ },
+ "consumedManoInterfaces": {
+ "description": "If present, this attribute signals modifications of the \"consumedManoInterfaces\" attribute in \"PeerEntity\", as defined in clause 5.6.2.15. See note.\n",
+ "type": "object"
+ },
+ "vimConnectionInfos": {
+ "description": "If present, this attribute signals modifications of the \"vimConnectionInfos\" attribute in \"PeerEntity\", as defined in clause 5.6.2.15. See note.\n",
+ "type": "array",
+ "items": {
+ "type": "object"
+ },
+ "additionalProperties": {
+ "description": "This type represents an interface consumed by the producer NFV MANO functional entity from another peer functional entity. * NOTE 1:\tThe information to be provided in this attribute shall relate to the specification and its version.\n For instance, \"ETSI GS NFV-SOL 003 (V2.4.1)\".\n* NOTE 2:\tDue to the security sensitive information associated to the attribute, based on access control\n policies, the API consumer might have read only, write only, read/write, or no access at all to\n the attribute's value. In case the API consumer is not allowed to read the value of the security\n sensitive attribute, the attribute shall be omitted when the information is to be provided in a\n response message, and shall be provided otherwise. In case the API consumer is not allowed to\n modify the value of the security sensitive attribute, and the modification request includes new\n attribute values, the whole modification request shall be rejected, and proper error information returned.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "name",
+ "type",
+ "standardVersion",
+ "apiVersion",
+ "apiEndpoint"
+ ],
+ "properties": {
+ "name": {
+ "description": "Human-readable name of the NFV-MANO interface.\n",
+ "type": "string"
+ },
+ "type": {
+ "description": "Type of the NFV-MANO service interface consumed by the NFV-MANO functional entity. Valid values are defined in clause 5.6.4.3.\n",
+ "type": "string"
+ },
+ "standardVersion": {
+ "description": "A version.\n",
+ "type": "string"
+ },
+ "apiVersion": {
+ "description": "A version.\n",
+ "type": "string"
+ },
+ "apiEndpoint": {
+ "description": "Consumable API endpoint of the interface. It provides the information relevant about the protocol, host and port, and path where the interface API can be accessed.\n",
+ "type": "object",
+ "properties": {
+ "apiRoot": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ },
+ "apiName": {
+ "description": "Indicates the interface name in an abbreviated form. Shall be present for ETSI NFV specified RESTful NFV-MANO APIs. The {apiName} of each interface is defined in the standard the interface is compliant to (see also clause 4.1 of ETSI GS NFV-SOL 013). May be present otherwise.\n",
+ "type": "string"
+ },
+ "apiMajorVersion": {
+ "description": "Indicates the current major version of the API. Shall be present for ETSI NFV specified RESTful NFV-MANO APIs. The major version is defined in the standard the interface is compliant to (see also clause 4.1 of ETSI GS NFV-SOL 013). May be present otherwise.\n",
+ "type": "string"
+ },
+ "apiUri": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ }
+ },
+ "required": [
+ "apiUri"
+ ]
+ },
+ "securityInfo": {
+ "description": "This type represents security related information for accessing an NFV-MANO service interface produced by an NFV-MANO functional entity. * NOTE:\tProvided configuration of the OAuth 2.0 authorization server information and configuration\n shall be supported, and dynamic configuration may be supported.\n",
+ "type": "object",
+ "required": [
+ "authType",
+ "oauthServerInfo"
+ ],
+ "properties": {
+ "authType": {
+ "description": "Type of API request authorization to be used by the API consumer accessing the API.\nThe support of authorization methods for the API consumer is specified in clause 8.3.6 of ETSI GS NFV-SOL 013.\nPermitted values: - TLS_TUNNEL: Using TLS tunnel, as defined by TLS 1.2 in IETF RFC 5246. - TLS_TUNNEL_13: Using TLS tunnel, as defined by TLS 1.3 in IETF RFC 8446. - OAUTH2: Using access token, as defined by the OAuth 2.0 specification in IETF RFC 6749.\n",
+ "type": "array",
+ "items": {
+ "type": "string",
+ "enum": [
+ "TLS_TUNNEL",
+ "TLS_TUNNEL_13",
+ "OAUTH2"
+ ]
+ },
+ "minItems": 1
+ },
+ "oauthServerInfo": {
+ "description": "OAuth 2.0 authorization server information and configuration.\n",
+ "type": "object",
+ "properties": {
+ "dynamicDiscovery": {
+ "description": "Configuration data used when performing dynamic discovery of the authorization server identifier. See note.\n",
+ "type": "object",
+ "required": [
+ "webFingerHost"
+ ],
+ "properties": {
+ "webFingerHost": {
+ "description": "Server where the WebFinger service is hosted. When used, the request to the WebFinger resource shall conform as specified in clause 5.1.3 of ETSI GS NFV-SEC 022.\n",
+ "type": "string",
+ "format": "uri"
+ }
+ }
+ },
+ "providedConfiguration": {
+ "description": "Configuration data used to setup the authorization server identifier. See note.\n",
+ "type": "object",
+ "required": [
+ "authServerId"
+ ],
+ "properties": {
+ "authServerId": {
+ "description": "Authorization server identifier as defined in ETSI GS NFV-SEC 022.\n",
+ "type": "string",
+ "format": "uri"
+ }
+ }
+ },
+ "tlsCipherSuites": {
+ "description": "List of cipher suites that shall be declared as supported by the API consumer when performing the SSL or TLS negotiation with the authorization server. Valid values of cipher suites are defined in IETF RFC 8447.\n",
+ "type": "array",
+ "items": {
+ "type": "string",
+ "minItems": 1
+ }
+ }
+ }
+ },
+ "tlsTunnelInfo": {
+ "description": "Information and configuration related to the use of TLS tunnel. Shall be present if authType contains \"TLS_TUNNEL\".\n",
+ "type": "object",
+ "properties": {
+ "tlsTunnelCipherSuites": {
+ "description": "List of cipher suites that shall be declared as supported by the API consumer when performing the SSL or TLS negotiation with the API producer. Valid values of cipher suites are defined in IETF RFC 8447.\n",
+ "type": "array",
+ "items": {
+ "type": "string",
+ "minItems": 1
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ },
+ "operationalState": {
+ "description": "The enumeration OperationalStateEnumType defines values representing the operational state of an NFV-MANO functional application type of managed entity. The OperationalStateEnumType shall comply with the provisions:\n - STARTED\tThe managed entity is operational.\n - STOPPED\tThe managed entity is not operational.\n - STOPPING\tThe managed entity is in the transition to stop.\n - STARTING\tThe managed entity is in the transition to start and become operational.\n - RESTARTING\tThe managed entity is in the transition to stop and start again.\n",
+ "type": "string",
+ "enum": [
+ "STARTED",
+ "STOPPED",
+ "STOPPING",
+ "STARTING",
+ "RESTARTING"
+ ]
+ },
+ "administrativeState": {
+ "description": "The enumeration AdministrativeStateEnumType defines values representing the administrative state of a managed entity. The AdministrativeStateEnumType shall comply with the provisions:\n - LOCKED\tThe managed entity is administratively prohibited to be used.\n - UNLOCKED\tThe managed entity is administratively allowed to be used.\n - LOCKING\tThe managed entity is in the transition to be locked.\n",
+ "type": "string",
+ "enum": [
+ "LOCKED",
+ "UNLOCKED",
+ "LOCKING"
+ ]
+ }
+ }
+}
\ No newline at end of file
diff --git a/SOL011/NSInstanceUsageNotification-API/ApiVersion.robot b/SOL011/NSInstanceUsageNotification-API/ApiVersion.robot
index 55953557c2defc94f5616e5cd92350159b970b24..aab84ef8fc008ef7f44a0b5f59d8d9ee3e6c8901 100644
--- a/SOL011/NSInstanceUsageNotification-API/ApiVersion.robot
+++ b/SOL011/NSInstanceUsageNotification-API/ApiVersion.robot
@@ -13,7 +13,7 @@ POST API Version - Method not implemented
... Test title: POST API version - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v3.3.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -25,7 +25,7 @@ GET API Version
... Test title: GET API Version
... Test objective: The objective is to test that GET method successfully return ApiVersionInformation
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v3.3.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -38,7 +38,7 @@ PUT API Version - Method not implemented
... Test title: PUT API Version - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v3.3.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -50,7 +50,7 @@ PATCH API Version - Method not implemented
... Test title: PATCH API Version - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v3.3.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -62,7 +62,7 @@ DELETE API Version - Method not implemented
... Test title: DELETE API Version - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v3.3.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -74,7 +74,7 @@ POST API Version with apiMajorVerion - Method not implemented
... Test title: POST API version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v3.3.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -86,7 +86,7 @@ GET API Version with apiMajorVerion
... Test title: GET API Version with apiMajorVerion
... Test objective: The objective is to test that GET method successfully return ApiVersionInformation
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v3.3.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -99,7 +99,7 @@ PUT API Version with apiMajorVerion - Method not implemented
... Test title: PUT API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v3.3.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -111,7 +111,7 @@ PATCH API Version with apiMajorVerion - Method not implemented
... Test title: PATCH API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v3.3.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -123,7 +123,7 @@ DELETE API Version with apiMajorVerion - Method not implemented
... Test title: DELETE API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v3.3.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL011/NSInstanceUsageNotification-API/IndividualSubscription.robot b/SOL011/NSInstanceUsageNotification-API/IndividualSubscription.robot
index 321078c10ee886a8be99fe0f70182d98941fe07a..5f11fda6ff81b636f1a4e101f4e154c067c8361e 100644
--- a/SOL011/NSInstanceUsageNotification-API/IndividualSubscription.robot
+++ b/SOL011/NSInstanceUsageNotification-API/IndividualSubscription.robot
@@ -12,7 +12,7 @@ POST Individual Subscription - Method not implemented
... Test title: POST Individual Subscription - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 8.5.4.3.1 - ETSI GS NFV-SOL 011 [8] v3.3.1
+ ... Reference: Clause 8.5.4.3.1 - ETSI GS NFV-SOL 011 [8] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -24,7 +24,7 @@ GET Information about an individual subscription - Successful
... Test title: GET Information about an individual subscription - Successful
... Test objective: The objective is to test the retrieval of NS instance usage notification subscription and perform a JSON schema validation of the returned subscription data structure
... Pre-conditions: An NS instance is instantiated. At least one NS instance usage notification subscription is available in the NFVO.
- ... Reference: Clause 8.5.4.3.2 - ETSI GS NFV-SOL 011 [8] v3.3.1
+ ... Reference: Clause 8.5.4.3.2 - ETSI GS NFV-SOL 011 [8] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -37,7 +37,7 @@ PUT an individual subscription - Method not implemented
... Test title: PUT an individual subscription - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 8.5.4.3.3 - ETSI GS NFV-SOL 011 [8] v3.3.1
+ ... Reference: Clause 8.5.4.3.3 - ETSI GS NFV-SOL 011 [8] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -49,7 +49,7 @@ PATCH an individual subscription - Method not implemented
... Test title: PATCH an individual subscription - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 8.5.4.3.4 - ETSI GS NFV-SOL 011 [8] v3.3.1
+ ... Reference: Clause 8.5.4.3.4 - ETSI GS NFV-SOL 011 [8] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -61,7 +61,7 @@ DELETE an individual subscription
... Test title: DELETE an individual subscription
... Test objective: The objective is to test that DELETE method deletes an individual subscription
... Pre-conditions: At least one instance usage notification subscription is available in the NFVO
- ... Reference: Clause 8.5.4.3.5 - ETSI GS NFV-SOL 011 [8] v3.3.1
+ ... Reference: Clause 8.5.4.3.5 - ETSI GS NFV-SOL 011 [8] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: The NS instance usage notification subscription is not available anymore on NFVO
@@ -74,7 +74,7 @@ GET Information about an individual subscription - NOT FOUND
... Test title: GET Information about an individual subscription - NOT FOUND
... Test objective: The objective is to test that the retrieval of individual NS instance usage notification subscription fails when using an invalid resource identifier.
... Pre-conditions: An NS instance is instantiated. At least one NS instance usage notification subscription is available in the NFVO.
- ... Reference: Clause 8.5.4.3.2 - ETSI GS NFV-SOL 011 [8] v3.3.1
+ ... Reference: Clause 8.5.4.3.2 - ETSI GS NFV-SOL 011 [8] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL011/NSInstanceUsageNotification-API/NotificationEndpoint.robot b/SOL011/NSInstanceUsageNotification-API/NotificationEndpoint.robot
index 2eb57060ffe43db76c938ca47b143062db89b9a7..28bb3cce7ed3cb7410dff67a258d577f796ba160 100644
--- a/SOL011/NSInstanceUsageNotification-API/NotificationEndpoint.robot
+++ b/SOL011/NSInstanceUsageNotification-API/NotificationEndpoint.robot
@@ -13,7 +13,7 @@ NS Instance Usage Notification
... Test title: NS Instance Usage Notification
... Test objective: The objective is to test that NS Instance Usage Notification is delivered with success to the notification consumer
... Pre-conditions: A subscription for instance usage notification is available in the NFVO.
- ... Reference: Clause 8.5.5.3.1 - ETSI GS NFV-SOL 011 [8] v3.3.1
+ ... Reference: Clause 8.5.5.3.1 - ETSI GS NFV-SOL 011 [8] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
diff --git a/SOL011/NSInstanceUsageNotification-API/Notifications.robot b/SOL011/NSInstanceUsageNotification-API/Notifications.robot
index 0d033484701586cdcccf0f827118fc6da8791b9e..a299608dc1d8e979aac52e31decd378cdc760d77 100644
--- a/SOL011/NSInstanceUsageNotification-API/Notifications.robot
+++ b/SOL011/NSInstanceUsageNotification-API/Notifications.robot
@@ -13,7 +13,7 @@ NS Instance Usage START Notification
... Test title: NS Instance Usage START Notification
... Test objective: The objective is to test the dispatch of NS Instance Usage Start Notification when the usage of an NS instance is started, and perform a JSON schema and content validation of the delivered notification. The action that triggers the notification under test is an explicit test step, but it is not performed by the test system.
... Pre-conditions: A subscription for NS instance usage notification is available in the NFVO.
- ... Reference: Clause 8.5.5.3.1 - ETSI GS NFV-SOL 011 [8] v3.3.1
+ ... Reference: Clause 8.5.5.3.1 - ETSI GS NFV-SOL 011 [8] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -27,7 +27,7 @@ NS Instance Usage END Notification
... Test title: NS Instance Usage END Notification
... Test objective: The objective is to test the dispatch of NS Instance Usage End Notification when the usage of an NS instance is ended, and perform a JSON schema and content validation of the delivered notification. The action that triggers the notification under test is an explicit test step, but it is not performed by the test system.
... Pre-conditions: A subscription for NS instance usage notification is available in the NFVO.
- ... Reference: Clause 8.5.5.3.1 - ETSI GS NFV-SOL 011 [8] v3.3.1
+ ... Reference: Clause 8.5.5.3.1 - ETSI GS NFV-SOL 011 [8] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL011/NSInstanceUsageNotification-API/Subscriptions.robot b/SOL011/NSInstanceUsageNotification-API/Subscriptions.robot
index 7ad64adf52138c9e40164380816a2912377803c4..36d4389e644dd762f311ea4764e7b43d8eb07e91 100644
--- a/SOL011/NSInstanceUsageNotification-API/Subscriptions.robot
+++ b/SOL011/NSInstanceUsageNotification-API/Subscriptions.robot
@@ -12,7 +12,7 @@ POST Create a new subscription
... Test title: POST Create a new subscription
... Test objective: The objective is to test that POST method creates a subscription
... Pre-conditions: none
- ... Reference: Clause 8.5.3.3.1 - ETSI GS NFV-SOL 011 [8] v3.3.1
+ ... Reference: Clause 8.5.3.3.1 - ETSI GS NFV-SOL 011 [8] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: Subscription is created in the NFVO
@@ -28,7 +28,7 @@ POST Create a new Subscription - DUPLICATION
... Test title: POST Create a new subscription - DUPLICATION
... Test objective: The objective is to test that POST method creates a duplicate subscription
... Pre-conditions: A subscription shall already exist
- ... Reference: Clause 8.5.3.3.1 - ETSI GS NFV-SOL 011 [8] v3.3.1
+ ... Reference: Clause 8.5.3.3.1 - ETSI GS NFV-SOL 011 [8] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: Duplication supported by NFVO-C
... Post-Conditions: Duplicate subscription is created in the NFVO
@@ -44,7 +44,7 @@ POST Create a new Subscription - NO-DUPLICATION
... Test title: POST Create a new subscription - NO-DUPLICATION
... Test objective: The objective is to test that POST method cannot create a duplicate subscription
... Pre-conditions: A subscription shall already exist
- ... Reference: Clause 8.5.3.3.1 - ETSI GS NFV-SOL 011 [8] v3.3.1
+ ... Reference: Clause 8.5.3.3.1 - ETSI GS NFV-SOL 011 [8] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: Duplication NOT supported by NFVO-C
... Post-Conditions: Duplicate subscription is not created in the NFVO
@@ -58,7 +58,7 @@ GET Subscriptions
... Test title: GET Subscriptions
... Test objective: The objective is to test that GET method retrieves the list of existing subscriptions
... Pre-conditions: none
- ... Reference: Clause 8.5.3.3.2 - ETSI GS NFV-SOL 011 [8] v3.3.1
+ ... Reference: Clause 8.5.3.3.2 - ETSI GS NFV-SOL 011 [8] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -71,7 +71,7 @@ GET Subscription - Filter
... Test title: GET Subscription - Filter
... Test objective: The objective is GET the list of active subscriptions using a filter
... Pre-conditions: none
- ... Reference: Clause 8.5.3.3.2 - ETSI GS NFV-SOL 011 [8] v3.3.1
+ ... Reference: Clause 8.5.3.3.2 - ETSI GS NFV-SOL 011 [8] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -84,7 +84,7 @@ GET subscriptions - Bad Request Invalid attribute-based filtering parameters
... Test title: GET subscriptions - Bad Request Invalid attribute-based filtering parameters
... Test objective: The objective is GET the list of active subscriptions using an invalid filter
... Pre-conditions: none
- ... Reference: Clause 8.5.3.3.2 - ETSI GS NFV-SOL 011 [8] v3.3.1
+ ... Reference: Clause 8.5.3.3.2 - ETSI GS NFV-SOL 011 [8] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -97,7 +97,7 @@ GET subscriptions - Bad Request Response too Big
... Test title: GET subscriptions - Bad Request Response too Big
... Test objective: The objective is test that the retrieval of active subscriptions list fails because response is too big, and perform the JSON schema validation of the failed operation HTTP response.
... Pre-conditions: none
- ... Reference: Clause 8.5.3.3.2 - ETSI GS NFV-SOL 011 [8] v3.3.1
+ ... Reference: Clause 8.5.3.3.2 - ETSI GS NFV-SOL 011 [8] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -110,7 +110,7 @@ GET subscriptions with "all_fields" attribute selector
... Test title: GET subscriptions with "all_fields" attribute selector
... Test objective: The objective is to retrieve the list of active subscriptions with "all_fields" attribute selector
... Pre-conditions: none
- ... Reference: Clause 8.5.3.3.2 - ETSI GS NFV-SOL 011 [8] v3.3.1
+ ... Reference: Clause 8.5.3.3.2 - ETSI GS NFV-SOL 011 [8] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -123,7 +123,7 @@ GET subscriptions with "exclude_default" attribute selector
... Test title: GET subscriptions with "exclude_default" attribute selector
... Test objective: The objective is to retrieve the list of active subscriptions with "exclude_default"s attribute selector
... Pre-conditions: none
- ... Reference: Clause 8.5.3.3.2 - ETSI GS NFV-SOL 011 [8] v3.3.1
+ ... Reference: Clause 8.5.3.3.2 - ETSI GS NFV-SOL 011 [8] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -136,7 +136,7 @@ GET subscriptions with "fields" attribute selector
... Test title: GET subscriptions with "fields" attribute selector
... Test objective: The objective is to retrieve the list of active subscriptions with "fields" attribute selector
... Pre-conditions: none
- ... Reference: Clause 8.5.3.3.2 - ETSI GS NFV-SOL 011 [8] v3.3.1
+ ... Reference: Clause 8.5.3.3.2 - ETSI GS NFV-SOL 011 [8] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -149,7 +149,7 @@ GET subscriptions with "exclude_fields" attribute selector
... Test title: GET subscriptions with "exclude_fields" attribute selector
... Test objective: The objective is to retrieve the list of active subscriptions with "exclude_fields" attribute selector
... Pre-conditions: none
- ... Reference: Clause 8.5.3.3.2 - ETSI GS NFV-SOL 011 [8] v3.3.1
+ ... Reference: Clause 8.5.3.3.2 - ETSI GS NFV-SOL 011 [8] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -162,7 +162,7 @@ GET Subscriptions as Paged Response
... Test title: GET Subscriptions as Paged Response
... Test objective: The objective is to test that GET method retrieve the list of existing subscriptions as paged response.
... Pre-conditions: none
- ... Reference: Clause 8.5.3.3.2 - ETSI GS NFV-SOL 011 [8] v3.3.1
+ ... Reference: Clause 8.5.3.3.2 - ETSI GS NFV-SOL 011 [8] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -175,7 +175,7 @@ PUT subscriptions - Method not implemented
... Test title: PUT subscriptions - Method not implemented
... Test objective: The objective is to test that PUT method cannot modify a NS instance usage subscription
... Pre-conditions: none
- ... Reference: Clause 8.5.3.3.3 - ETSI GS NFV-SOL 011 [8] v3.3.1
+ ... Reference: Clause 8.5.3.3.3 - ETSI GS NFV-SOL 011 [8] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -187,7 +187,7 @@ PATCH subscriptions - Method not implemented
... Test title: PATCH subscriptions - Method not implemented
... Test objective: The objective is to test that PUT method cannot modify a NS instance usage subscription
... Pre-conditions: none
- ... Reference: Clause 8.5.3.3.4 - ETSI GS NFV-SOL 011 [8] v3.3.1
+ ... Reference: Clause 8.5.3.3.4 - ETSI GS NFV-SOL 011 [8] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -199,7 +199,7 @@ DELETE subscriptions - Method not implemented
... Test title: DELETE subscriptions - Method not implemented
... Test objective: The objective is to test that DELETE method cannot delete a NS instance usage subscription
... Pre-conditions: none
- ... Reference: Clause 8.5.3.3.5 - ETSI GS NFV-SOL 011 [8] v3.3.1
+ ... Reference: Clause 8.5.3.3.5 - ETSI GS NFV-SOL 011 [8] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: Subscriptions are not deleted
@@ -212,7 +212,7 @@ GET subscriptions with "exclude_default" and "fields" attribute selector
... Test title: GET subscriptions with "exclude_default" and "fields" attribute selector
... Test objective: The objective is to retrieve the list of active subscriptions with "exclude_default" and "fields" attribute selector
... Pre-conditions:
- ... Reference: Clause 8.5.3.3.2 - ETSI GS NFV-SOL 011 [8] v3.3.1
+ ... Reference: Clause 8.5.3.3.2 - ETSI GS NFV-SOL 011 [8] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL011/NSLifecycleOperationGranting-API/ApiVersion.robot b/SOL011/NSLifecycleOperationGranting-API/ApiVersion.robot
index aedb3eec5ca811084a3852e7d02aaa2bcb170220..6d2eb96b1fa49a8e869db0e42d95cdab61cb4792 100644
--- a/SOL011/NSLifecycleOperationGranting-API/ApiVersion.robot
+++ b/SOL011/NSLifecycleOperationGranting-API/ApiVersion.robot
@@ -13,7 +13,7 @@ POST API Version - Method not implemented
... Test title: POST API version - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v3.3.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -25,7 +25,7 @@ GET API Version
... Test title: GET API Version
... Test objective: The objective is to test that GET method successfully return ApiVersionInformation
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v3.3.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -38,7 +38,7 @@ PUT API Version - Method not implemented
... Test title: PUT API Version - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v3.3.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -50,7 +50,7 @@ PATCH API Version - Method not implemented
... Test title: PATCH API Version - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v3.3.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -62,7 +62,7 @@ DELETE API Version - Method not implemented
... Test title: DELETE API Version - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v3.3.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -74,7 +74,7 @@ POST API Version with apiMajorVerion - Method not implemented
... Test title: POST API version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that POST method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v3.3.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -86,7 +86,7 @@ GET API Version with apiMajorVerion
... Test title: GET API Version with apiMajorVerion
... Test objective: The objective is to test that GET method successfully return ApiVersionInformation
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v3.3.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -99,7 +99,7 @@ PUT API Version with apiMajorVerion - Method not implemented
... Test title: PUT API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v3.3.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -111,7 +111,7 @@ PATCH API Version with apiMajorVerion - Method not implemented
... Test title: PATCH API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v3.3.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -123,7 +123,7 @@ DELETE API Version with apiMajorVerion - Method not implemented
... Test title: DELETE API Version with apiMajorVerion - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v3.3.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL011/NSLifecycleOperationGranting-API/Grants.robot b/SOL011/NSLifecycleOperationGranting-API/Grants.robot
index 61e4353b8824617d833a35899325ee40ae3c67b6..ff8921e307e5ef39f8897ccc20d7cc3ba21e457f 100644
--- a/SOL011/NSLifecycleOperationGranting-API/Grants.robot
+++ b/SOL011/NSLifecycleOperationGranting-API/Grants.robot
@@ -12,7 +12,7 @@ Requests a grant for a particular NS lifecycle operation
... Test title: Requests a grant for a particular NS lifecycle operation
... Test objective: The objective is to request a grant for a particular NS lifecycle operation and perform a JSON schema validation on the returned grant data structure
... Pre-conditions:
- ... Reference: Clause 7.5.3.3.1 - ETSI GS NFV-SOL 011 [8] v3.3.1
+ ... Reference: Clause 7.5.3.3.1 - ETSI GS NFV-SOL 011 [8] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO can decide immediately what to respond to a grant request
... Post-Conditions: The grant information is available to the NFVO.
@@ -27,7 +27,7 @@ Requests a grant for a particular NS lifecycle operation - Forbidden
... Test title: Requests a grant for a particular NS lifecycle operation - Forbidden
... Test objective: The objective is to request a grant for a particular NS lifecycle operation and the grant is rejected
... Pre-conditions: none
- ... Reference: Clause 7.5.3.3.1 - ETSI GS NFV-SOL 011 [8] v3.3.1
+ ... Reference: Clause 7.5.3.3.1 - ETSI GS NFV-SOL 011 [8] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -40,7 +40,7 @@ GET Grants - Method not implemented
... Test title: GET Grants - Method not implemented
... Test objective: The objective is to test that GET method is not allowed for Lifecycle operation granting
... Pre-conditions: none
- ... Reference: Clause 7.5.3.3.2 - ETSI GS NFV-SOL 011 [8] v3.3.1
+ ... Reference: Clause 7.5.3.3.2 - ETSI GS NFV-SOL 011 [8] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -52,7 +52,7 @@ PUT Grants - Method not implemented
... Test title: PUT Grants - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed for Lifecycle operation granting
... Pre-conditions: none
- ... Reference: Clause 7.5.3.3.3 - ETSI GS NFV-SOL 011 [8] v3.3.1
+ ... Reference: Clause 7.5.3.3.3 - ETSI GS NFV-SOL 011 [8] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -64,7 +64,7 @@ PATCH Grants - Method not implemented
... Test title: PATCH Grants - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed for Lifecycle operation granting
... Pre-conditions: none
- ... Reference: Clause 7.5.3.3.4 - ETSI GS NFV-SOL 011 [8] v3.3.1
+ ... Reference: Clause 7.5.3.3.4 - ETSI GS NFV-SOL 011 [8] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -76,7 +76,7 @@ DELETE Grants - Method not implemented
... Test title: DELETE Grants - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed for Lifecycle operation granting
... Pre-conditions: none
- ... Reference: Clause 7.5.3.3.5 - ETSI GS NFV-SOL 011 [8] v3.3.1
+ ... Reference: Clause 7.5.3.3.5 - ETSI GS NFV-SOL 011 [8] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: Resources are not deleted
diff --git a/SOL011/NSLifecycleOperationGranting-API/IndividualGrant.robot b/SOL011/NSLifecycleOperationGranting-API/IndividualGrant.robot
index dcc0f47957b52fd432595cb9eb49d18ed91cf6cf..0bad5cd0dc39257ea2c7c8c0fef86b3662dc087d 100644
--- a/SOL011/NSLifecycleOperationGranting-API/IndividualGrant.robot
+++ b/SOL011/NSLifecycleOperationGranting-API/IndividualGrant.robot
@@ -15,7 +15,7 @@ POST Individual Grant - Method not implemented
... Test title: POST Individual Grant - Method not implemented
... Test objective: The objective is to test that POST method is not allowed for Lifecycle operation granting
... Pre-conditions: none
- ... Reference: Clause 7.5.4.3.1 - ETSI GS NFV-SOL 011 [8] v3.3.1
+ ... Reference: Clause 7.5.4.3.1 - ETSI GS NFV-SOL 011 [8] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -27,7 +27,7 @@ GET an individual grant - Successful
... Test title: GET an individual grant - Successful
... Test objective: The objective is to retrieve a grant for a particular NS Lifecycle Operation.
... Pre-conditions: The grant information is available to the NFVO
- ... Reference: Clause 7.5.4.3.2 - ETSI GS NFV-SOL 011 [8] v3.3.1
+ ... Reference: Clause 7.5.4.3.2 - ETSI GS NFV-SOL 011 [8] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -40,7 +40,7 @@ PUT an individual grant - Method not implemented
... Test title: PUT an individual grant - Method not implemented
... Test objective: The objective is to test that PUT method is not allowed to for Lifecycle operation granting
... Pre-conditions: none
- ... Reference: Clause 7.5.4.3.3 - ETSI GS NFV-SOL 011 [8] v3.3.1
+ ... Reference: Clause 7.5.4.3.3 - ETSI GS NFV-SOL 011 [8] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -52,7 +52,7 @@ PATCH an individual grant - Method not implemented
... Test title: PATCH an individual grant - Method not implemented
... Test objective: The objective is to test that PATCH method is not allowed to for Lifecycle operation granting
... Pre-conditions: none
- ... Reference: Clause 7.5.4.3.4 - ETSI GS NFV-SOL 011 [8] v3.3.1
+ ... Reference: Clause 7.5.4.3.4 - ETSI GS NFV-SOL 011 [8] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -64,7 +64,7 @@ DELETE an individual grant - Method not implemented
... Test title: DELETE an individual grant - Method not implemented
... Test objective: The objective is to test that DELETE method is not allowed to for Lifecycle operation granting
... Pre-conditions: none
- ... Reference: Clause 7.5.4.3.5 - ETSI GS NFV-SOL 011 [8] v3.3.1
+ ... Reference: Clause 7.5.4.3.5 - ETSI GS NFV-SOL 011 [8] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -76,7 +76,7 @@ GET an individual grant - NOT FOUND
... Test title: GET an individual grant - NOT FOUND
... Test objective: The objective is to test that the retrieval of individual grant for a particular Lifecycle operation fails when using an invalid resource identifier
... Pre-conditions: The grant information is available to the NFVO
- ... Reference: Clause 7.5.4.3.2 - ETSI GS NFV-SOL 011 [8] v3.3.1
+ ... Reference: Clause 7.5.4.3.2 - ETSI GS NFV-SOL 011 [8] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: Invalid resource identifier is used
... Post-Conditions: none
diff --git a/SOL011/README.md b/SOL011/README.md
index dc212cbbcdb76a61c13aaecb3286a95fd1629d31..bdd8bde54470ff210d661c793642389ae0d16c97 100644
--- a/SOL011/README.md
+++ b/SOL011/README.md
@@ -2,7 +2,7 @@
This folder includes the NFV API conformance test descriptions for NFV SOL011 APIs.
-The reference spec version is v3.3.1: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/011/03.03.01_60/gs_NFV-SOL011v030301p.pdf
+The reference spec version is v4.4.1: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/011/04.04.01_60/gs_NFV-SOL011v040401p.pdf
## Applicable Tests
In addition to the SOL011 tests included in this folder for NS Instance Usage Notification API and NS Lifecycle Operation Granting API, the SOL011 tests make use of applicable SOL005 tests.
diff --git a/SOL012/PolicyManagement-API/ApiVersion.robot b/SOL012/PolicyManagement-API/ApiVersion.robot
index ac2a5df81d215ac8d85567e4bafdf94d0cc3e02d..e14f6382b31b702fc99822a35e40e529613791eb 100644
--- a/SOL012/PolicyManagement-API/ApiVersion.robot
+++ b/SOL012/PolicyManagement-API/ApiVersion.robot
@@ -9,7 +9,7 @@ POST API Version - Method not implemented
... Test title: POST API version - Method not implemented
... Test objective: The objective is to test that POST method is not implemented for this resource.
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v3.3.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -21,7 +21,7 @@ GET API Version
... Test title: GET API Version
... Test objective: The objective is to test that GET method successfully returns ApiVersionInformation.
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v3.3.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -34,7 +34,7 @@ PUT API Version - Method not implemented
... Test title: PUT API Version - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented for this resource.
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v3.3.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -46,7 +46,7 @@ PATCH API Version - Method not implemented
... Test title: PATCH API Version - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v3.3.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -58,7 +58,7 @@ DELETE API Version - Method not implemented
... Test title: DELETE API Version - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented for this resource.
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v3.3.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -70,7 +70,7 @@ POST API Version with apiMajorVersion - Method not implemented
... Test title: POST API version with apiMajorVersion - Method not implemented
... Test objective: The objective is to test that POST method is not implemented.
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v3.3.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -82,7 +82,7 @@ GET API Version with apiMajorVersion
... Test title: GET API Version with apiMajorVersion
... Test objective: The objective is to test that GET method successfully returns ApiVersionInformation.
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v3.3.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -95,7 +95,7 @@ PUT API Version with apiMajorVersion - Method not implemented
... Test title: PUT API Version with apiMajorVersion - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented.
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v3.3.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -107,7 +107,7 @@ PATCH API Version with apiMajorVersion - Method not implemented
... Test title: PATCH API Version with apiMajorVersion - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented.
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v3.3.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -119,7 +119,7 @@ DELETE API Version with apiMajorVersion - Method not implemented
... Test title: DELETE API Version with apiMajorVersion - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented.
... Pre-conditions: none
- ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v3.3.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL012/PolicyManagement-API/IndividualPolicy.robot b/SOL012/PolicyManagement-API/IndividualPolicy.robot
index 7deca87f045eed83d7dac7011b1fefc8136c61a1..b6d5f1e3f4818e3a78fd943c1660603cdaacd0f1 100644
--- a/SOL012/PolicyManagement-API/IndividualPolicy.robot
+++ b/SOL012/PolicyManagement-API/IndividualPolicy.robot
@@ -8,7 +8,7 @@ POST Individual Policy - Method not implemented
... Test title: POST Individual Policy - Method not implemented
... Test objective: The objective is to test that POST method is not implemented.
... Pre-conditions: none
- ... Reference: Clause 5.5.4.3.1 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.4.3.1 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -20,7 +20,7 @@ GET Information about an individual policy - Successful
... Test title: GET Information about an individual policy - Successful
... Test objective: The objective is to test the retrieval of Individual Policy and perform a JSON schema validation of the returned Policy data structure.
... Pre-conditions: At least one policy is available in the NFV-MANO.
- ... Reference: Clause 5.5.4.3.2 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.4.3.2 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -33,7 +33,7 @@ GET Information about an individual policy - NOT FOUND
... Test title: GET Information about an individual policy - NOT FOUND
... Test objective: The objective is to test that the retrieval of individual policy fails when using an invalid resource identifier.
... Pre-conditions: At least one individual policy is available in the NFV-MANO.
- ... Reference: Clause 5.5.8.3.2 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.8.3.2 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -46,7 +46,7 @@ PUT an individual policy - Method not implemented
... Test title: PUT an individual policy - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented.
... Pre-conditions: none
- ... Reference: Clause 5.5.4.3.3 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.4.3.3 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -58,7 +58,7 @@ PATCH an individual policy - Successful
... Test title: PATCH an individual policy - Successful
... Test objective: The objective is to test that an individual policy is modified successfully when there is no conflict using PATCH method.
... Pre-conditions: There should not exist a conflict as described in Reference.
- ... Reference: Clause 5.5.4.3.4 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.4.3.4 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -71,7 +71,7 @@ PATCH an individual policy - Conflict
... Test title: PATCH an individual policy - Conflict
... Test objective: The objective is to test that an individual policy is not modified when there is a conflict using PATCH method.
... Pre-conditions: There exists a conflict as described in Reference.
- ... Reference: Clause 5.5.4.3.4 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.4.3.4 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -85,7 +85,7 @@ DELETE an individual policy - Successful
... Test title: DELETE an individual policy - Successful
... Test objective: The objective is to test that DELETE method deletes a deactivated individual policy.
... Pre-conditions: The activation status of individual policy to be deleted is not set to ACTIVATED.
- ... Reference: Clause 5.5.8.3.5 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.8.3.5 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: The individual policy is not available anymore in the NFV-MANO.
@@ -98,7 +98,7 @@ DELETE an individual policy - CONFLICT
... Test title: DELETE an individual policy - CONFLICT
... Test objective: The objective is to test that DELETE method does not delete an activated individual policy.
... Pre-conditions: The activation status of individual policy to be deleted is set to ACTIVATED.
- ... Reference: Clause 5.5.8.3.5 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.8.3.5 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: The individual policy is not deleted.
diff --git a/SOL012/PolicyManagement-API/IndividualSubscription.robot b/SOL012/PolicyManagement-API/IndividualSubscription.robot
index e7e3da0f7d6943df3b0dc1d72b7a9cbdc5dbf08c..82755dae1e90db8527376abe4d982af6942b3381 100644
--- a/SOL012/PolicyManagement-API/IndividualSubscription.robot
+++ b/SOL012/PolicyManagement-API/IndividualSubscription.robot
@@ -8,7 +8,7 @@ POST Individual Subscription - Method not implemented
... Test title: POST Individual Subscription - Method not implemented
... Test objective: The objective is to test that POST method is not implemented for this resource.
... Pre-conditions: none
- ... Reference: Clause 5.5.8.3.1 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.8.3.1 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -20,7 +20,7 @@ GET Information about an individual subscription - Successful
... Test title: GET Information about an individual subscription - Successful
... Test objective: The objective is to test the retrieval of Policy Management subscription and perform a JSON schema validation of the returned PolicySubscription data structure
... Pre-conditions: At least one policy management subscription is available in the NFV-MANO.
- ... Reference: Clause 5.5.8.3.2 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.8.3.2 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -33,7 +33,7 @@ GET Information about an individual subscription - NOT FOUND
... Test title: GET Information about an individual subscription - NOT FOUND
... Test objective: The objective is to test that the retrieval of individual Policy Management subscription fails when using an invalid resource identifier.
... Pre-conditions: At least one Policy Management subscription is available in the NFV-MANO.
- ... Reference: Clause 5.5.8.3.2 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.8.3.2 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -46,7 +46,7 @@ PUT an individual subscription - Method not implemented
... Test title: PUT an individual subscription - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented for this resource.
... Pre-conditions: none
- ... Reference: Clause 5.5.8.3.3 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.8.3.3 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -58,7 +58,7 @@ PATCH an individual subscription - Method not implemented
... Test title: PATCH an individual subscription - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented for this resource.
... Pre-conditions: none
- ... Reference: Clause 5.5.8.3.4 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.8.3.4 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -70,7 +70,7 @@ DELETE an individual subscription
... Test title: DELETE an individual subscription
... Test objective: The objective is to test that DELETE method deletes an individual subscription
... Pre-conditions: At least one policy management subscription is available in the NFV-MANO.
- ... Reference: Clause 5.5.8.3.5 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.8.3.5 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: The Policy Management subscription is no longer available in the NFV-MANO.
diff --git a/SOL012/PolicyManagement-API/NotificationEndpoint.robot b/SOL012/PolicyManagement-API/NotificationEndpoint.robot
index 80097e51a2fd627dcca6fad9b569f58ad0bf35e0..48089c6547c208a4345a3c64ae31c85aa3a39242 100644
--- a/SOL012/PolicyManagement-API/NotificationEndpoint.robot
+++ b/SOL012/PolicyManagement-API/NotificationEndpoint.robot
@@ -9,7 +9,7 @@ Policy Change Notification
... Test title: Policy Change Notification
... Test objective: The objective is to test that Policy Change Notification is delivered with success to the notification consumer.
... Pre-conditions: A subscription for policy change notification is available in the NFV-MANO.
- ... Reference: Clause 5.5.9.3.1 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.9.3.1 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
@@ -21,7 +21,7 @@ Policy Conflict Notification
... Test title: Policy Conflict Notification
... Test objective: The objective is to test that Policy Conflict Notification is delivered with success to the notification consumer.
... Pre-conditions: A subscription for policy conflict notification is available in the NFV-MANO.
- ... Reference: Clause 5.5.9.3.1 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.9.3.1 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
@@ -33,7 +33,7 @@ Test the Notification Endpoint - Successful
... Test title: Test the Notification Endpoint - Successful
... Test objective: The objective is to test the Notification Endpoint provided by the notification consumer.
... Pre-conditions: A notification endpoint is provided by the API consumer upon subscription.
- ... Reference: Clause 5.5.9.3.2 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.9.3.2 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
@@ -45,7 +45,7 @@ Test the Notification Endpoint - UNREACHABLE
... Test title: Test the Notification Endpoint - UNREACHABLE
... Test objective: The objective is to test the Notification Endpoint provided by the notification consumer.
... Pre-conditions: A notification endpoint is provided by the API consumer upon subscription.
- ... Reference: Clause 5.5.7.3.1 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.7.3.1 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: The notification endpoint is unreachable by the API producer.
... Post-Conditions: none
@@ -58,7 +58,7 @@ PUT Notification endpoint - Method Not Implemented
... Test title: PUT Notification endpoint - Method Not Implemented
... Test objective: The objective is to test the PUT method for Notification Endpoint provided by the consumer is not implemented.
... Pre-conditions: A notification endpoint is provided by the API consumer upon subscription.
- ... Reference: Clause 5.5.9.3.3 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.9.3.3 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
@@ -70,7 +70,7 @@ PATCH Notification endpoint - Method Not Implemented
... Test title: PATCH Notification endpoint - Method Not Implemented
... Test objective: The objective is to test the PATCH method for Notification Endpoint provided by the consumer is not implemented.
... Pre-conditions: A notification endpoint is provided by the API consumer upon subscription.
- ... Reference: Clause 5.5.9.3.4 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.9.3.4 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
@@ -82,7 +82,7 @@ DELETE Notification endpoint - Method Not Implemented
... Test title: DELETE Notification endpoint - Method Not Implemented
... Test objective: The objective is to test the DELETE method for Notification Endpoint provided by the consumer is not implemented.
... Pre-conditions: A notification endpoint is provided by the API consumer upon subscription.
- ... Reference: Clause 5.5.9.3.5 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.9.3.5 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
diff --git a/SOL012/PolicyManagement-API/Notifications.robot b/SOL012/PolicyManagement-API/Notifications.robot
index 2e0efb08ffaa0c2b27c37ba3060bfe6ec6084ccd..0ef06146979b0e4ad47c0d4a90792e9362cb2cae 100644
--- a/SOL012/PolicyManagement-API/Notifications.robot
+++ b/SOL012/PolicyManagement-API/Notifications.robot
@@ -13,7 +13,7 @@ Policy Change Notification
... Test title: Policy Change Notification
... Test objective: The objective is to test the dispatch of Policy Change Notification when the policy is changed, and perform a JSON schema and content validation of the delivered notification. The action that triggers the notification under test is an explicit test step, but it is not performed by the test system.
... Pre-conditions: A subscription for policy change notification is available in the NFV-MANO.
- ... Reference: Clause 5.5.9.3.1 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.9.3.1 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -26,7 +26,7 @@ Policy Conflict Notification
... Test title: Policy Conflict Notification
... Test objective: The objective is to test the dispatch of Policy Conflict Notification when a conflict in policy is detected, and perform a JSON schema and content validation of the delivered notification. The action that triggers the notification under test is an explicit test step, but it is not performed by the test system.
... Pre-conditions: A subscription for policy conflict notification is available in the NFV-MANO.
- ... Reference: Clause 5.5.9.3.1 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.9.3.1 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL012/PolicyManagement-API/ParticularVersionOfAnIndividualPolicy.robot b/SOL012/PolicyManagement-API/ParticularVersionOfAnIndividualPolicy.robot
index 5c97dad14b7b335a86f44e7410385f8c4671c934..464523ad8044b5433f62dc4ad8a182f5bc55e490 100644
--- a/SOL012/PolicyManagement-API/ParticularVersionOfAnIndividualPolicy.robot
+++ b/SOL012/PolicyManagement-API/ParticularVersionOfAnIndividualPolicy.robot
@@ -8,7 +8,7 @@ POST Particular Version of an Individual Policy - Method not implemented
... Test title: POST Particular Version of an Individual Policy - Method not implemented
... Test objective: The objective is to test that POST method is not implemented for this resource.
... Pre-conditions: none
- ... Reference: Clause 5.5.6.3.1 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.6.3.1 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -20,7 +20,7 @@ GET Information about a Particular Version of an Individual Policy - Successful
... Test title: GET Information about a Particular Version of an Individual Policy - Successful
... Test objective: The objective is to test that GET method fetches the content of a particular version of an individual policy.
... Pre-conditions: Individual policy is available in the NFV-MANO. Policy contents are provided in the json/PolicyContent folder.
- ... Reference: Clause 5.5.6.3.2 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.6.3.2 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: The policy content type is either JSON, YAML or ZIP.
... Post-Conditions: none
@@ -33,7 +33,7 @@ GET Information about a Particular Version of an Individual Policy - NOT FOUND
... Test title: GET Information about a Particular Version of an Individual Policy - NOT FOUND
... Test objective: The objective is to test that the information about a particular version of an individual policy fails when using an invalid resource identifier.
... Pre-conditions: none
- ... Reference: Clause 5.5.6.3.2 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.6.3.2 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -46,7 +46,7 @@ PUT Particular Version of an individual policy - Successful
... Test title: PUT Particular Version of an individual policy - Successful
... Test objective: The objective is to test that the PUT method transfers the content of a particular version of an individual policy.
... Pre-conditions: none
- ... Reference: Clause 5.5.6.3.3 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.6.3.3 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: The policy content type is either JSON, YAML or ZIP.
... Post-Conditions: none
@@ -58,7 +58,7 @@ PUT Particular Version of an individual policy - CONFLICT
... Test title: PUT Particular Version of an individual policy - CONFLICT
... Test objective: The objective is to test that the PUT method does not transfer the content of a particular version in case of a conflict.
... Pre-conditions: The particular version has already been transferred to the API producer.
- ... Reference: Clause 5.5.6.3.3 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.6.3.3 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: The policy content type is either JSON, YAML or ZIP.
... Post-Conditions: none
@@ -71,7 +71,7 @@ PATCH Particular Version of an individual policy - Method not implemented
... Test title: PATCH Particular Version of an individual policy - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented for this resource.
... Pre-conditions: none
- ... Reference: Clause 5.5.6.3.4 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.6.3.4 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -83,7 +83,7 @@ DELETE Particular Version of an individual policy - Successful
... Test title: DELETE Particular Version of an individual policy - Successful
... Test objective: The objective is to test that the DELETE method deletes a particular version of an individual policy.
... Pre-conditions: none
- ... Reference: Clause 5.5.6.3.5 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.6.3.5 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -95,7 +95,7 @@ DELETE Particular Version of an individual policy - CONFLICT
... Test title: DELETE Particular Version of an individual policy - CONFLICT
... Test objective: The objective is to test that the DELETE method does not delete a particular version of an individual policy in case of a conflict.
... Pre-conditions: The requested version of the individual policy is the selected version.
- ... Reference: Clause 5.5.6.3.5 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.6.3.5 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL012/PolicyManagement-API/Policies.robot b/SOL012/PolicyManagement-API/Policies.robot
index 6e76d17b4744933937710a74116e4f113e1c968a..18c4837b501b82a952efc1ceabb9a9a3b90151b0 100644
--- a/SOL012/PolicyManagement-API/Policies.robot
+++ b/SOL012/PolicyManagement-API/Policies.robot
@@ -8,7 +8,7 @@ POST Create a new Policy
... Test title: POST Create a new Policy
... Test objective: The objective is to test that POST method creates a policy.
... Pre-conditions: none
- ... Reference: Clause 5.5.3.3.1 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.3.3.1 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: Policy is created.
@@ -22,7 +22,7 @@ GET Policies
... Test title: GET Policies
... Test objective: The objective is to test that GET method retrieves the list of existing policies.
... Pre-conditions: none
- ... Reference: Clause 5.5.3.3.2 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.3.3.2 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -35,7 +35,7 @@ GET Policies - Filter
... Test title: GET Policies - Filter
... Test objective: The objective is to GET the list of existing policies using a filter.
... Pre-conditions: none
- ... Reference: Clause 5.5.3.3.2 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.3.3.2 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -48,7 +48,7 @@ GET Policies - Bad Request Invalid attribute-based filtering parameters
... Test title: GET Policies - Bad Request Invalid attribute-based filtering parameters
... Test objective: The objective is to GET the list of existing policies using an invalid filter.
... Pre-conditions: none
- ... Reference: Clause 5.5.3.3.2 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.3.3.2 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -61,7 +61,7 @@ GET Policies - Bad Request Response too Big
... Test title: GET Policies - Bad Request Response too Big
... Test objective: The objective is test that the retrieval of existing policies list fails because response is too big, and perform the JSON schema validation of the failed operation HTTP response.
... Pre-conditions: none
- ... Reference: Clause 5.5.3.3.2 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.3.3.2 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: NFV-MANO does not support paged response.
... Post-Conditions: none
@@ -74,7 +74,7 @@ GET Policies with "all_fields" attribute selector
... Test title: GET Policies with "all_fields" attribute selector
... Test objective: The objective is to retrieve the list of existing policies with "all_fields" attribute selector.
... Pre-conditions: none
- ... Reference: Clause 5.5.3.3.2 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.3.3.2 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -87,7 +87,7 @@ GET Policies with "exclude_default" attribute selector
... Test title: GET policies with "exclude_default" attribute selector
... Test objective: The objective is to retrieve the list of existing policies with "exclude_default"s attribute selector.
... Pre-conditions: none
- ... Reference: Clause 5.5.3.3.2 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.3.3.2 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -100,7 +100,7 @@ GET Policies with "fields" attribute selector
... Test title: GET Policies with "fields" attribute selector
... Test objective: The objective is to retrieve the list of existing policies with "fields" attribute selector.
... Pre-conditions: none
- ... Reference: Clause 5.5.3.3.2 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.3.3.2 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -113,7 +113,7 @@ GET Policies with "exclude_fields" attribute selector
... Test title: GET Policies with "exclude_fields" attribute selector
... Test objective: The objective is to retrieve the list of existing policies with "exclude_fields" attribute selector.
... Pre-conditions: none
- ... Reference: Clause 5.5.3.3.2 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.3.3.2 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -126,7 +126,7 @@ GET Policies with "exclude_default" and "fields" attribute selector
... Test title: GET Policies with "exclude_default" and "fields" attribute selector
... Test objective: The objective is to retrieve the list of existing policies with "exclude_default" and "fields" attribute selector
... Pre-conditions:
- ... Reference: Clause 5.5.3.3.2 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.3.3.2 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -139,7 +139,7 @@ GET Policies as Paged Response
... Test title: GET Policies as Paged Response
... Test objective: The objective is to test that GET method retrieves the list of existing policies as paged response.
... Pre-conditions: none
- ... Reference: Clause 5.5.3.3.2 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.3.3.2 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: NFV-MANO supports paged response.
... Post-Conditions: none
@@ -152,7 +152,7 @@ PUT Policies - Method not implemented
... Test title: PUT Policies - Method not implemented
... Test objective: The objective is to test that PUT method cannot modify policies.
... Pre-conditions: none
- ... Reference: Clause 5.5.3.3.3 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.3.3.3 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -164,7 +164,7 @@ PATCH Policies - Method not implemented
... Test title: PATCH Policies - Method not implemented
... Test objective: The objective is to test that PATCH method cannot modify policies.
... Pre-conditions: none
- ... Reference: Clause 5.5.3.3.4 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.3.3.4 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -176,7 +176,7 @@ DELETE Policies - Method not implemented
... Test title: DELETE Policies - Method not implemented
... Test objective: The objective is to test that DELETE method cannot delete policies.
... Pre-conditions: none
- ... Reference: Clause 5.5.3.3.5 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.3.3.5 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: Policies are not deleted
diff --git a/SOL012/PolicyManagement-API/SelectedVersionOfAnIndividualPolicy.robot b/SOL012/PolicyManagement-API/SelectedVersionOfAnIndividualPolicy.robot
index 8a3c163ab3f2b7d2a5c2e7c031f18043ab25c215..7394c56d416a304297ade3f04865634bc5384544 100644
--- a/SOL012/PolicyManagement-API/SelectedVersionOfAnIndividualPolicy.robot
+++ b/SOL012/PolicyManagement-API/SelectedVersionOfAnIndividualPolicy.robot
@@ -8,7 +8,7 @@ POST Selected Version of an Individual Policy - Method not implemented
... Test title: POST Selected Version of an Individual Policy - Method not implemented
... Test objective: The objective is to test that POST method is not implemented for this resource.
... Pre-conditions: none
- ... Reference: Clause 5.5.5.3.1 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.5.3.1 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -20,7 +20,7 @@ GET Information about the Selected Version of an Individual Policy - Successful
... Test title: GET Information about the Selected Version of an Individual Policy - Successful
... Test objective: The objective is to test The GET method fetches contents of the selected version of an individual policy and check that the HTTP Content-Type header is set according to the type of content.
... Pre-conditions: Individual policy is available in the NFV-MANO. Policy contents are provided in the json/PolicyContent folder.
- ... Reference: Clause 5.5.5.3.2 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.5.3.2 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: The policy content type is either JSON, YAML or ZIP.
... Post-Conditions: none
@@ -33,7 +33,7 @@ GET Information about the Selected Version of an Individual Policy - NOT FOUND
... Test title: GET Information about the Selected Version of an Individual Policy - NOT FOUND
... Test objective: The objective is to test that the information about the selected version of an individual policy fails when using an invalid resource identifier.
... Pre-conditions: The API producer did not find the current representation for the target resource.
- ... Reference: Clause 5.5.5.3.2 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.5.3.2 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -46,7 +46,7 @@ GET Information about the Selected Version of an Individual Policy - CREATED STA
... Test title: GET Information about the Selected Version of an Individual Policy - NOT FOUND
... Test objective: The objective is to test that the information about the selected version of an individual policy is not retrieved when it is in CREATED state.
... Pre-conditions: none
- ... Reference: Clause 5.5.5.3.2 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.5.3.2 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -59,7 +59,7 @@ PUT Selected Version of an individual policy - Method not implemented
... Test title: PUT Selected Version of an individual policy - Method not implemented
... Test objective: The objective is to test that PUT method is not implemented for this resource.
... Pre-conditions: none
- ... Reference: Clause 5.5.5.3.3 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.5.3.3 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -71,7 +71,7 @@ PATCH Selected Version of an individual policy - Method not implemented
... Test title: PATCH Selected Version of an individual policy - Method not implemented
... Test objective: The objective is to test that PATCH method is not implemented for this resource.
... Pre-conditions: none
- ... Reference: Clause 5.5.5.3.4 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.5.3.4 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -83,7 +83,7 @@ DELETE Selected Version of an individual policy - Method not implemented
... Test title: DELETE Selected Version of an individual policy - Method not implemented
... Test objective: The objective is to test that DELETE method is not implemented for this resource.
... Pre-conditions: none
- ... Reference: Clause 5.5.5.3.5 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.5.3.5 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL012/PolicyManagement-API/Subscriptions.robot b/SOL012/PolicyManagement-API/Subscriptions.robot
index f0267cc12b1fef4ef67c31648e906ce9c06fef1c..e45cfdf8ee4354921adcb4d657e07df7994a7c12 100644
--- a/SOL012/PolicyManagement-API/Subscriptions.robot
+++ b/SOL012/PolicyManagement-API/Subscriptions.robot
@@ -11,7 +11,7 @@ POST Create a new subscription
... Test title: POST Create a new subscription
... Test objective: The objective is to test that POST method creates a subscription.
... Pre-conditions: none
- ... Reference: Clause 5.5.7.3.1 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.7.3.1 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: Policy subscription is created.
@@ -26,7 +26,7 @@ POST Create a new Subscription - DUPLICATION NOT ALLOWED
... Test title: POST Create a new subscription - DUPLICATION NOT ALLOWED
... Test objective: The objective is to test that POST method cannot create a duplicate subscription.
... Pre-conditions: A subscription shall already exist.
- ... Reference: Clause 5.5.7.3.1 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.7.3.1 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: Duplication is not supported by NFVMANO.
... Post-Conditions: Individual subscription resource returned in the location header is available.
@@ -35,12 +35,12 @@ POST Create a new Subscription - DUPLICATION NOT ALLOWED
Check HTTP Response Header Contains Location
Check Postcondition Individual Subscription Resource Returned in Location Header Is Available
-POST Create a new Subscription - UNPROCESSABLE ENTITY
+POST Create a new Subscription - UNPROCESSABLE CONTENT
[Documentation] Test ID: 10.3.1.6.3
- ... Test title: POST Create a new Subscription - UNPROCESSABLE ENTITY
+ ... Test title: POST Create a new Subscription - UNPROCESSABLE CONTENT
... Test objective: The objective is to test that correct error code is generated when data in the request body cannot be processed.
... Pre-conditions: none
- ... Reference: Clause 5.5.7.3.1 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.7.3.1 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: Callback URI is not reachable by the API producer.
... Post-Conditions: none
@@ -53,7 +53,7 @@ GET Subscriptions
... Test title: GET Subscriptions
... Test objective: The objective is to test that GET method retrieves the list of existing subscriptions.
... Pre-conditions: none
- ... Reference: Clause 5.5.7.3.2 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.7.3.2 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -66,7 +66,7 @@ GET Subscription - Filter
... Test title: GET Subscription - Filter
... Test objective: The objective is to GET the list of active subscriptions using a filter.
... Pre-conditions: none
- ... Reference: Clause 5.5.7.3.2 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.7.3.2 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -79,7 +79,7 @@ GET subscriptions - Bad Request Invalid attribute-based filtering parameters
... Test title: GET subscriptions - Bad Request Invalid attribute-based filtering parameters
... Test objective: The objective is to GET the list of active subscriptions using an invalid filter.
... Pre-conditions: none
- ... Reference: Clause 5.5.7.3.2 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.7.3.2 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -92,7 +92,7 @@ GET subscriptions - Bad Request Response too Big
... Test title: GET subscriptions - Bad Request Response too Big
... Test objective: The objective is test that the retrieval of active subscriptions list fails because response is too big, and perform the JSON schema validation of the failed operation HTTP response.
... Pre-conditions: none
- ... Reference: Clause 5.5.7.3.2 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.7.3.2 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: NFV-MANO does not support paged response.
... Post-Conditions: none
@@ -105,7 +105,7 @@ GET subscriptions with "all_fields" attribute selector
... Test title: GET subscriptions with "all_fields" attribute selector
... Test objective: The objective is to retrieve the list of active subscriptions with "all_fields" attribute selector
... Pre-conditions: none
- ... Reference: Clause 5.5.7.3.2 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.7.3.2 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -118,7 +118,7 @@ GET subscriptions with "exclude_default" attribute selector
... Test title: GET subscriptions with "exclude_default" attribute selector
... Test objective: The objective is to retrieve the list of active subscriptions with "exclude_default"s attribute selector
... Pre-conditions: none
- ... Reference: Clause 5.5.7.3.2 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.7.3.2 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -131,7 +131,7 @@ GET subscriptions with "fields" attribute selector
... Test title: GET subscriptions with "fields" attribute selector
... Test objective: The objective is to retrieve the list of active subscriptions with "fields" attribute selector
... Pre-conditions: none
- ... Reference: Clause 5.5.7.3.2 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.7.3.2 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -144,7 +144,7 @@ GET subscriptions with "exclude_fields" attribute selector
... Test title: GET subscriptions with "exclude_fields" attribute selector
... Test objective: The objective is to retrieve the list of active subscriptions with "exclude_fields" attribute selector
... Pre-conditions: none
- ... Reference: Clause 5.5.7.3.2 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.7.3.2 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -157,7 +157,7 @@ GET Subscriptions as Paged Response
... Test title: GET Subscriptions as Paged Response
... Test objective: The objective is to test that GET method retrieves the list of existing subscriptions as paged response.
... Pre-conditions: none
- ... Reference: Clause 5.5.7.3.2 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.7.3.2 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: NFV-MANO supports paged response.
... Post-Conditions: none
@@ -170,7 +170,7 @@ GET subscriptions with "exclude_default" and "fields" attribute selector
... Test title: GET subscriptions with "exclude_default" and "fields" attribute selector
... Test objective: The objective is to retrieve the list of active subscriptions with "exclude_default" and "fields" attribute selector
... Pre-conditions:
- ... Reference: Clause 5.5.7.3.2 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.7.3.2 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -183,7 +183,7 @@ PUT subscriptions - Method not implemented
... Test title: PUT subscriptions - Method not implemented
... Test objective: The objective is to test that PUT method cannot modify a policy management subscription.
... Pre-conditions: none
- ... Reference: Clause 5.5.7.3.3 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.7.3.3 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -195,7 +195,7 @@ PATCH subscriptions - Method not implemented
... Test title: PATCH subscriptions - Method not implemented
... Test objective: The objective is to test that PATCH method cannot modify a policy management subscription.
... Pre-conditions: none
- ... Reference: Clause 5.5.7.3.4 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.7.3.4 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -207,10 +207,10 @@ DELETE subscriptions - Method not implemented
... Test title: DELETE subscriptions - Method not implemented
... Test objective: The objective is to test that DELETE method cannot delete a policy management subscription.
... Pre-conditions: none
- ... Reference: Clause 5.5.7.3.5 - ETSI GS NFV-SOL 012 [7] v3.4.1
+ ... Reference: Clause 5.5.7.3.5 - ETSI GS NFV-SOL 012 [7] v4.4.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: Subscriptions are not deleted
DELETE subscriptions
Check HTTP Response Status Code Is 405
- Check Postcondition Subscriptions Exist
\ No newline at end of file
+ Check Postcondition Subscriptions Exist
diff --git a/SOL012/PolicyManagement-API/schemas/Policies.schema.json b/SOL012/PolicyManagement-API/schemas/Policies.schema.json
index 3e095ed9ba92228fb2f4c4b59ccf497c9b465fb9..24d3af078f2ad43dfbfba1821eb3fa820e1b43e9 100644
--- a/SOL012/PolicyManagement-API/schemas/Policies.schema.json
+++ b/SOL012/PolicyManagement-API/schemas/Policies.schema.json
@@ -1,121 +1,121 @@
-{ "type": "array",
- "items":
- {
- "description": "This type represents an individual policy. It shall comply with the provisions defined in table 5.6.2.3-1.",
- "type": "object",
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "designer": {
- "description": "Human readable name of the designer of the policy.\n",
- "type": "string"
- },
- "name": {
- "description": "Human readable name of the policy.\n",
- "type": "string"
- },
- "pfId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "versions": {
- "description": "Versions of the policy. Shall be present if at least one version of the policy has been transferred.\n",
- "type": "array",
- "items": {
- "description": "A version.\n",
- "type": "string"
- }
- },
- "selectedVersion": {
- "description": "A version.\n",
- "type": "string"
- },
- "activationStatus": {
- "description": "The enumeration ActivationStatus shall comply with the provisions defined in table 5.6.4.3-1. It indicates the activation status of a policy.\n",
- "type": "string",
- "enum": [
- "ACTIVATED",
- "DEACTIVATED"
- ]
- },
- "transferStatus": {
- "description": "The enumeration TransferStatus shall comply with the provisions defined in table 5.6.4.4-1. It indicates the transfer status of a policy\n",
- "type": "string",
- "enum": [
- "CREATED",
- "TRANSFERRED"
- ]
- },
- "associations": {
- "description": "Identifiers of the entities that the PF manages and to which the policy associates to. Shall be absent when the association feature is not applicable for the PF. The associations refer to identifiers of entities that the PF manages. E.g., if the PF is a VNFM, the policy can associate to VNF instances; if the PF is NFVO, the policy can associate to an NS instances. How the PF determines the scope of applicability of the policy when this attribute is absent is outside the scope of the present document.\n",
- "type": "array",
- "items": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- }
- },
- "_links": {
- "description": "Links for this resource\n",
- "type": "object",
- "properties": {
- "self": {
- "description": "This type represents a link to a resource using an absolute URI.\n",
- "type": "object",
- "required": [
- "href"
- ],
- "properties": {
- "href": {
- "description": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- }
- }
- },
- "selected": {
- "description": "This type represents a link to a resource using an absolute URI.\n",
- "type": "object",
- "required": [
- "href"
- ],
- "properties": {
- "href": {
- "description": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- }
- }
- },
- "versions": {
- "description": "URIs of all the transferred versions of this policy, if exists.\n",
- "type": "array",
- "items": {
- "description": "This type represents a link to a resource using an absolute URI.\n",
- "type": "object",
- "required": [
- "href"
- ],
- "properties": {
- "href": {
- "description": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- }
- }
- }
- }
- },
- "required": [
- "self"
- ]
- }
- },
- "required": [
- "id",
- "designer",
- "name",
- "activationStatus",
- "transferStatus",
- "_links"
- ]
- }
+{
+ "type": "array",
+ "items": {
+ "description": "This type represents an individual policy. It shall comply with the provisions defined in table 5.6.2.3-1.",
+ "type": "object",
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "designer": {
+ "description": "Human readable name of the designer of the policy.\n",
+ "type": "string"
+ },
+ "name": {
+ "description": "Human readable name of the policy.\n",
+ "type": "string"
+ },
+ "pfId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "versions": {
+ "description": "Versions of the policy. Shall be present if at least one version of the policy has been transferred. Its value shall be the same as the version present in the actual policy content as defined by the \"policyVersion\" attribute in the \"Policy\" information element specified in clause 5.2 of ETSI GS NFV-IFA 048 [ref-ifa048].\n",
+ "type": "array",
+ "items": {
+ "description": "A version.\n",
+ "type": "string"
+ }
+ },
+ "selectedVersion": {
+ "description": "A version.\n",
+ "type": "string"
+ },
+ "activationStatus": {
+ "description": "The enumeration ActivationStatus shall comply with the provisions defined in table 5.6.4.3-1. It indicates the activation status of a policy.\n",
+ "type": "string",
+ "enum": [
+ "ACTIVATED",
+ "DEACTIVATED"
+ ]
+ },
+ "transferStatus": {
+ "description": "The enumeration TransferStatus shall comply with the provisions defined in table 5.6.4.4-1. It indicates the transfer status of a policy\n",
+ "type": "string",
+ "enum": [
+ "CREATED",
+ "TRANSFERRED"
+ ]
+ },
+ "associations": {
+ "description": "Identifiers of the entities that the PF manages and to which the policy associates to. Shall be absent when the association feature is not applicable for the PF, i.e., the target information in the policy content defined by the \"targetType\" attribute of the \"Policy\" information element specified in clause 5.2 of ETSI GS NFV-IFA 048 [ref-ifa048] is equal to \"COMMON\". An initial set of associations applicable to a policy to be set by the API producer may either be provided by the \"associations\" attribute in the \"CreatePolicyRequest\" or by the actual policy content via the \"targetObjectId\" attribute of the \"Policy” information element specified in clause 5.2 of ETSI GS NFV-IFA 048 [ref-ifa048]. Values of the \"associations\" attribute can be further modified with the PATCH method. See note 2 and note 3.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ },
+ "_links": {
+ "description": "Links for this resource\n",
+ "type": "object",
+ "properties": {
+ "self": {
+ "description": "This type represents a link to a resource using an absolute URI.\n",
+ "type": "object",
+ "required": [
+ "href"
+ ],
+ "properties": {
+ "href": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ }
+ }
+ },
+ "selected": {
+ "description": "This type represents a link to a resource using an absolute URI.\n",
+ "type": "object",
+ "required": [
+ "href"
+ ],
+ "properties": {
+ "href": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ }
+ }
+ },
+ "versions": {
+ "description": "URIs of all the transferred versions of this policy, if exists.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents a link to a resource using an absolute URI.\n",
+ "type": "object",
+ "required": [
+ "href"
+ ],
+ "properties": {
+ "href": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ }
+ }
+ }
+ }
+ },
+ "required": [
+ "self"
+ ]
+ }
+ },
+ "required": [
+ "id",
+ "designer",
+ "name",
+ "activationStatus",
+ "transferStatus",
+ "_links"
+ ]
+ }
}
\ No newline at end of file
diff --git a/SOL012/PolicyManagement-API/schemas/Policy.schema.json b/SOL012/PolicyManagement-API/schemas/Policy.schema.json
index fdcdea95a697b56140ec9aa1fa9aedda5a9296b6..c0429a23d210a555ef7478618c43f02581ff0cc4 100644
--- a/SOL012/PolicyManagement-API/schemas/Policy.schema.json
+++ b/SOL012/PolicyManagement-API/schemas/Policy.schema.json
@@ -1,118 +1,118 @@
{
- "description": "This type represents an individual policy. It shall comply with the provisions defined in table 5.6.2.3-1.",
- "type": "object",
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "designer": {
- "description": "Human readable name of the designer of the policy.\n",
- "type": "string"
- },
- "name": {
- "description": "Human readable name of the policy.\n",
- "type": "string"
- },
- "pfId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "versions": {
- "description": "Versions of the policy. Shall be present if at least one version of the policy has been transferred.\n",
- "type": "array",
- "items": {
- "description": "A version.\n",
- "type": "string"
- }
- },
- "selectedVersion": {
- "description": "A version.\n",
- "type": "string"
- },
- "activationStatus": {
- "description": "The enumeration ActivationStatus shall comply with the provisions defined in table 5.6.4.3-1. It indicates the activation status of a policy.\n",
- "type": "string",
- "enum": [
- "ACTIVATED",
- "DEACTIVATED"
- ]
- },
- "transferStatus": {
- "description": "The enumeration TransferStatus shall comply with the provisions defined in table 5.6.4.4-1. It indicates the transfer status of a policy\n",
- "type": "string",
- "enum": [
- "CREATED",
- "TRANSFERRED"
- ]
- },
- "associations": {
- "description": "Identifiers of the entities that the PF manages and to which the policy associates to. Shall be absent when the association feature is not applicable for the PF. The associations refer to identifiers of entities that the PF manages. E.g., if the PF is a VNFM, the policy can associate to VNF instances; if the PF is NFVO, the policy can associate to an NS instances. How the PF determines the scope of applicability of the policy when this attribute is absent is outside the scope of the present document.\n",
- "type": "array",
- "items": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- }
- },
- "_links": {
- "description": "Links for this resource\n",
- "type": "object",
- "properties": {
- "self": {
- "description": "This type represents a link to a resource using an absolute URI.\n",
- "type": "object",
- "required": [
- "href"
- ],
- "properties": {
- "href": {
- "description": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- }
- }
- },
- "selected": {
- "description": "This type represents a link to a resource using an absolute URI.\n",
- "type": "object",
- "required": [
- "href"
- ],
- "properties": {
- "href": {
- "description": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- }
- }
- },
- "versions": {
- "description": "URIs of all the transferred versions of this policy, if exists.\n",
- "type": "array",
- "items": {
- "description": "This type represents a link to a resource using an absolute URI.\n",
- "type": "object",
- "required": [
- "href"
- ],
- "properties": {
- "href": {
- "description": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- }
- }
- }
- }
- },
- "required": [
- "self"
- ]
- }
- },
- "required": [
- "id",
- "designer",
- "name",
- "activationStatus",
- "transferStatus",
- "_links"
- ]
+ "description": "This type represents an individual policy. It shall comply with the provisions defined in table 5.6.2.3-1.",
+ "type": "object",
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "designer": {
+ "description": "Human readable name of the designer of the policy.\n",
+ "type": "string"
+ },
+ "name": {
+ "description": "Human readable name of the policy.\n",
+ "type": "string"
+ },
+ "pfId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "versions": {
+ "description": "Versions of the policy. Shall be present if at least one version of the policy has been transferred. Its value shall be the same as the version present in the actual policy content as defined by the \"policyVersion\" attribute in the \"Policy\" information element specified in clause 5.2 of ETSI GS NFV-IFA 048 [ref-ifa048].\n",
+ "type": "array",
+ "items": {
+ "description": "A version.\n",
+ "type": "string"
+ }
+ },
+ "selectedVersion": {
+ "description": "A version.\n",
+ "type": "string"
+ },
+ "activationStatus": {
+ "description": "The enumeration ActivationStatus shall comply with the provisions defined in table 5.6.4.3-1. It indicates the activation status of a policy.\n",
+ "type": "string",
+ "enum": [
+ "ACTIVATED",
+ "DEACTIVATED"
+ ]
+ },
+ "transferStatus": {
+ "description": "The enumeration TransferStatus shall comply with the provisions defined in table 5.6.4.4-1. It indicates the transfer status of a policy\n",
+ "type": "string",
+ "enum": [
+ "CREATED",
+ "TRANSFERRED"
+ ]
+ },
+ "associations": {
+ "description": "Identifiers of the entities that the PF manages and to which the policy associates to. Shall be absent when the association feature is not applicable for the PF, i.e., the target information in the policy content defined by the \"targetType\" attribute of the \"Policy\" information element specified in clause 5.2 of ETSI GS NFV-IFA 048 [ref-ifa048] is equal to \"COMMON\". An initial set of associations applicable to a policy to be set by the API producer may either be provided by the \"associations\" attribute in the \"CreatePolicyRequest\" or by the actual policy content via the \"targetObjectId\" attribute of the \"Policy” information element specified in clause 5.2 of ETSI GS NFV-IFA 048 [ref-ifa048]. Values of the \"associations\" attribute can be further modified with the PATCH method. See note 2 and note 3.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ },
+ "_links": {
+ "description": "Links for this resource\n",
+ "type": "object",
+ "properties": {
+ "self": {
+ "description": "This type represents a link to a resource using an absolute URI.\n",
+ "type": "object",
+ "required": [
+ "href"
+ ],
+ "properties": {
+ "href": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ }
+ }
+ },
+ "selected": {
+ "description": "This type represents a link to a resource using an absolute URI.\n",
+ "type": "object",
+ "required": [
+ "href"
+ ],
+ "properties": {
+ "href": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ }
+ }
+ },
+ "versions": {
+ "description": "URIs of all the transferred versions of this policy, if exists.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents a link to a resource using an absolute URI.\n",
+ "type": "object",
+ "required": [
+ "href"
+ ],
+ "properties": {
+ "href": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ }
+ }
+ }
+ }
+ },
+ "required": [
+ "self"
+ ]
+ }
+ },
+ "required": [
+ "id",
+ "designer",
+ "name",
+ "activationStatus",
+ "transferStatus",
+ "_links"
+ ]
}
\ No newline at end of file
diff --git a/SOL012/README.md b/SOL012/README.md
index 5c51a4086562685c490ecf95a45f099391c63ac2..ed88a64a59cdb55cdee07a7dc2d08c0247005448 100644
--- a/SOL012/README.md
+++ b/SOL012/README.md
@@ -2,5 +2,5 @@
This folder includes the NFV API conformance test descriptions for NFV SOL012 APIs.
-The reference spec version is v3.3.1: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/012/03.04.01_60/gs_NFV-SOL012v030401p.pdf
+The reference spec version is v4.4.1: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/012/04.04.01_60/gs_NFV-SOL012v040401p.pdf
diff --git a/indexes/sol_002_index.csv b/indexes/sol_002_index.csv
index e4673a0c1bb78b07b967c6df5e4c071bb387d9a2..e51dbb0aff51c1e22b319447817d93f3610da7c0 100644
--- a/indexes/sol_002_index.csv
+++ b/indexes/sol_002_index.csv
@@ -8,7 +8,7 @@
6.3.2.3,Individual VNF Indicator Resource Endpoit,IndividualVNFindicator.robot
6.3.2.4,Subscriptions Resource Endpoint,Subscriptions.robot
6.3.2.5,Individual Subscription Resource Endpoint,IndividualSubscription.robot
-6.3.2.6,Notifications,../VNFIndicatorNotification-API/Notifications.robot
+6.3.2.6,Notifications,Notifications.robot
6.3.2.7,API Version Resource Endpoint,ApiVersion.robot
6.3.2.8,Notification Endpoint,NotificationEndpoint.robot
6.3.3,VNF Performance Management Interface,VNFPerformanceManagement-API
@@ -16,8 +16,10 @@
6.3.3.2,Individual PM Job Resource Endpoint,IndividualPmJob.robot
6.3.3.3,Individual Performance Report Resource Endpoint,IndividualReport.robot
6.3.3.4,Thresholds Resource Endpoint,Thresholds.robot
-6.3.3.5,Individual Threshold Resource Endpoint,IndividualThreshold.robot
-6.3.3.8,Notification,../VNFPerformanceManagementNotification-API/Notifications.robot
+6.3.3.5,Individual Threshold Resource Endpoint,IndividualThreshold.robot
+6.3.3.6,Void,Void
+6.3.3.7,Void,Void
+6.3.3.8,Notification,Notifications.robot
6.3.3.9,API Version Resource Endpoint,ApiVersion.robot
6.3.3.10,Notification Endpoint,NotificationEndpoint.robot
6.3.4,VNF Fault Management interface,VNFFaultManagement-API
@@ -51,8 +53,13 @@
6.3.5.19,Notifications,Notifications.robot
6.3.5.20,API Version Resource Endpoint,ApiVersion.robot
6.3.5.21,Notification Endpoint,NotificationEndpoint.robot
+6.3.5.22,Change current VNF package,ChangeCurrentVNFPackageTask.robot
+6.3.5.23,Create VNF Snapshot Task,CreateVNFSnapshotTask.robot
+6.3.5.24,Revert to VNF Snapshot Task,RevertToVNFSnapshotTask.robot
+6.3.5.25,VNF Snapshots,VNFSnapshots.robot
+6.3.5.26,Individual VNF Snapshot,IndividualVNFSnapshot.robot
6.3.6,VNF LCM Coordination Interface,VNFLCMCoordination-API
6.3.6.1,API Version Resource Endpoint,ApiVersion.robot
6.3.6.2,Coordinations,Coordinations.robot
6.3.6.3,Individual Coordination Action,IndividualCoordinationAction.robot
-6.3.6.4,Cancel Coordination Action Task,CancelCoordinationActionTask.robot
\ No newline at end of file
+6.3.6.4,Cancel Coordination Action Task,CancelCoordinationActionTask.robot
diff --git a/indexes/sol_003_index.csv b/indexes/sol_003_index.csv
index 4605666906005e8352b03843c788e2ce4112114c..c7f408b74c37f2d610e24aff08f252ad1e9ac8ac 100644
--- a/indexes/sol_003_index.csv
+++ b/indexes/sol_003_index.csv
@@ -1,93 +1,101 @@
-7,Or-Vnfm Reference Point, SOL003
-7.3.1,VNF Lifecycle Management Interface, VNFLifecycleManagement-API
-7.3.1.1,VnfInstances, VNFInstances.robot
-7.3.1.2,Individual VNFInstance, IndividualVNFInstance.robot
-7.3.1.3,Instantiate a VNF, InstantiateVNFTask.robot
-7.3.1.4,Scale a vnfInstance, ScaleVNFTask.robot
-7.3.1.5,Scale a vnfInstance to level, ScaleVNFToLevelTask.robot
-7.3.1.6,Change deployment flavour of a vnfInstance,ChangeVNFFlavourTask.robot
-7.3.1.7,Terminate a vnfInstance,TerminateVNFTask.robot
-7.3.1.8,Heal a vnfInstance, HealVNFTask.robot
-7.3.1.9,Operate a vnfInstance, OperateVNFTask.robot
-7.3.1.10,Change external VNF connectivity, ChangeExternalVNFConnectivityTask.robot
-7.3.1.11,VNF LCM Operation occurrences, VnfLcmOperationOccurences.robot
-7.3.1.12,Individual VNF LCM Operation occurrence, IndividualVnfLcmOperationOccurence.robot
-7.3.1.13,Retry operation task, RetryOperationTask.robot
-7.3.1.14,Rollback operation task, RollbackOperationTask.robot
-7.3.1.15,Fail operation task, FailOperationTask.robot
-7.3.1.16,Cancel operation task, CancelOperationTask.robot
-7.3.1.17,Subscriptions, Subscriptions.robot
-7.3.1.18,Individual Subscription, IndividualSubscription.robot
-7.3.1.19,Cancel VNF LCM Operation, CancelOperationWorkflow.robot
-7.3.1.20,Change external connectivity of VNF Workflow, ChangeExternalVNFConnectivityWorkflow.robot
-7.3.1.21,Change VNF Flavour Workflow, ChangeVNFFlavourWorkflow.robot
-7.3.1.22,Create VNF Instance Resource,CreateVNFWorkflow.robot
-7.3.1.23,Delete VNF Instance Resource, DeleteVNFWorkflow.robot
-7.3.1.24,Fail a VNF LCM Operation Workflow,FailOperationWorkflow.robot
-7.3.1.25,Heal a VNF Instance,HealVNFWorkflow.robot
-7.3.1.26,VNF Instantiation,InstantiateVNFTaskWorkflow.robot
-7.3.1.27,Modify info of a VNF Instance, ModifyVNFInformationWorkflow.robot
-7.3.1.28,Operate a VNF Instance,OperateVNFWorkflow.robot
-7.3.1.29,Retry VNF LCM Operation, RetryOperationWorkflow.robot
-7.3.1.30,Rollback VNF LCM Operation, RollBackOperationWorkflow.robot
-7.3.1.31,VNF Instance Scale To Level, ScaleVNFToLevelWorkflow.robot
-7.3.1.32,VNF Instance Scale Out, ScaleVNFWorkflow.robot
-7.3.1.33,Terminate a VNF Instance, TerminateVNFWorkflow.robot
-7.3.1.34,Notifications, Notifications.robot
-7.3.1.35,API Version Resource Endpoint, ApiVersion.robot
-7.3.1.36,Notification Endpoint,NotificationEndpoint.robot
-7.3.2,VNF Lifecycle Operation Granting Interface, VNFLifecycleOperationGranting-API
-7.3.2.1,Grants, Grants.robot
-7.3.2.2,Individual Grant, IndividualGrant.robot
-7.3.2.3,API Version Resource Endpoint, ApiVersion.robot
-7.3.3,VNF Package Management Interface, VNFPackageManagement-API
-7.3.3.1,VNF Packages Resource Endpoint, VNFPackages.robot
-7.3.3.2,Individual VNF Package Resource Endpoint, IndividualVNFPackage.robot
-7.3.3.3,VNF Package Content Resource Endpoint, VNFPackageContent.robot
-7.3.3.4,VNFD In Individual VNF Package Resource Endpoint, VNFDInIndividualVNFPackage.robot
-7.3.3.5,Individual VNF Package Artifact Resource Endpoint, VNFPackageArtifacts.robot
-7.3.3.6,Subscriptions Resource Endpoint, Subscriptions.robot
-7.3.3.7,Individual Subscription Resource Endpoint, IndividualSubscription.robot
-7.3.3.8,Notifications, Notifications.robot
-7.3.3.9,API Version Resource Endpoint, ApiVersion.robot
-7.3.3.10,Manifest In Individual VNF Package Endpoint,ManifestInIndividualVNFPackage.robot
-7.3.3.11,VNF Package Artifacts Endpoint,VNFPackageArtifacts.robot
-7.3.3.12,Notification Endpoint,NotificationEndpoint.robot
-7.3.4,VNF Performance Management Interface, VNFPerformanceManagement-API
-7.3.4.1,PM Jobs Resource Endpoint, PMJobs.robot
-7.3.4.2,Individual Pm Job Resource Endpoint, IndividualPmJob.robot
-7.3.4.3,Individual Performance Report Resource Endpoint, IndividualReport.robot
-7.3.4.4,Thresholds Resource Endpoint, Thresholds.robot
-7.3.4.5,Individual Threshold Resource Endpoint, IndividualThreshold.robot
-7.3.4.8,Notifications,Notifications.robot
-7.3.4.9,API Version Resource Endpoint, ApiVersion.robot
-7.3.4.10,Notification Endpoint,NotificationEndpoint.robot
-7.3.5,VNF Fault Management interface, VNFFaultManagement-API
-7.3.5.1,Alarms, Alarms.robot
-7.3.5.2,Individual Alarm, IndividualAlarm.robot
-7.3.5.3,Subscriptions, Subscriptions.robot
-7.3.5.4,Individual Subscription, IndividualSubscription.robot
-7.3.5.5,Notifications, ../VNFFaultManagementNotification-API/Notifications.robot
-7.3.5.6,API Version Resource Endpoint, ApiVersion.robot
-7.3.5.7,Notification Endpoint,NotificationEndpoint.robot
-7.3.6,VNF Indicator Interface, VNFIndicator-API
-7.3.6.1,VNF Indicators Resource Endpoint, VNFIndicators.robot
-7.3.6.2,VNF Indicators Related to a VNF Instance Resource Endpoint, VnfIndicatorsInVnfInstanceId.robot
-7.3.6.3,Individual VNF Indicator Resource Endpoint, IndividualVNFindicator.robot
-7.3.6.4,Subscriptions Resource Endpoint, Subscriptions.robot
-7.3.6.5,Individual Subscription Resource Endpoint, IndividualSubscription.robot
-7.3.6.6,Notifications, Notifications.robot
-7.3.6.7,API Version Resource Endpoint, ApiVersion.robot
-7.3.6.8,Notification Endpoint,NotificationEndpoint.robot
-7.3.7,Virtualised Resources Quota Available Notification interface, VirtualisedResourcesQuotaAvailableNotification-API
-7.3.7.1,Subscriptions, Subscriptions.robot
-7.3.7.2,Individual Subscription, IndividualSubscription.robot
-7.3.7.3,API Version Resource Endpoint, ApiVersion.robot
-7.3.7.4,Notification Endpoint,NotificationEndpoint.robot
-7.3.7.5,Notifications,Notifications.robot
-7.3.8,VNF Snapshot Package Management Interface, VNFSnapshotPackageManagement-API
-7.3.8.1,API Version Resource Endpoint, ApiVersion.robot
-7.3.8.2,VNF Snapshot Packages Endpoint,VNFSnapshotPackages.robot
-7.3.8.3,Individual VNF Snapshot Package Endpoint,IndividualVNFSnapshotPackage.robot
-7.3.8.4,VNF Snapshot Package Content Endpoint,VNFSnapshotPackageContent.robot
-7.3.8.5,Individual VNF Snapshot Package Artifact Endpoint,IndividualVNFSnapshotPackageArtifact.robot
+7,Or-Vnfm Reference Point, SOL003
+7.3.1,VNF Lifecycle Management Interface, VNFLifecycleManagement-API
+7.3.1.1,VnfInstances, VNFInstances.robot
+7.3.1.2,Individual VNFInstance, IndividualVNFInstance.robot
+7.3.1.3,Instantiate a VNF, InstantiateVNFTask.robot
+7.3.1.4,Scale a vnfInstance, ScaleVNFTask.robot
+7.3.1.5,Scale a vnfInstance to level, ScaleVNFToLevelTask.robot
+7.3.1.6,Change deployment flavour of a vnfInstance,ChangeVNFFlavourTask.robot
+7.3.1.7,Terminate a vnfInstance,TerminateVNFTask.robot
+7.3.1.8,Heal a vnfInstance, HealVNFTask.robot
+7.3.1.9,Operate a vnfInstance, OperateVNFTask.robot
+7.3.1.10,Change external VNF connectivity, ChangeExternalVNFConnectivityTask.robot
+7.3.1.11,VNF LCM Operation occurrences, VnfLcmOperationOccurences.robot
+7.3.1.12,Individual VNF LCM Operation occurrence, IndividualVnfLcmOperationOccurence.robot
+7.3.1.13,Retry operation task, RetryOperationTask.robot
+7.3.1.14,Rollback operation task, RollbackOperationTask.robot
+7.3.1.15,Fail operation task, FailOperationTask.robot
+7.3.1.16,Cancel operation task, CancelOperationTask.robot
+7.3.1.17,Subscriptions, Subscriptions.robot
+7.3.1.18,Individual Subscription, IndividualSubscription.robot
+7.3.1.19,Cancel VNF LCM Operation, CancelOperationWorkflow.robot
+7.3.1.20,Change external connectivity of VNF Workflow, ChangeExternalVNFConnectivityWorkflow.robot
+7.3.1.21,Change VNF Flavour Workflow, ChangeVNFFlavourWorkflow.robot
+7.3.1.22,Create VNF Instance Resource,CreateVNFWorkflow.robot
+7.3.1.23,Delete VNF Instance Resource, DeleteVNFWorkflow.robot
+7.3.1.24,Fail a VNF LCM Operation Workflow,FailOperationWorkflow.robot
+7.3.1.25,Heal a VNF Instance,HealVNFWorkflow.robot
+7.3.1.26,VNF Instantiation,InstantiateVNFTaskWorkflow.robot
+7.3.1.27,Modify info of a VNF Instance, ModifyVNFInformationWorkflow.robot
+7.3.1.28,Operate a VNF Instance,OperateVNFWorkflow.robot
+7.3.1.29,Retry VNF LCM Operation, RetryOperationWorkflow.robot
+7.3.1.30,Rollback VNF LCM Operation, RollBackOperationWorkflow.robot
+7.3.1.31,VNF Instance Scale To Level, ScaleVNFToLevelWorkflow.robot
+7.3.1.32,VNF Instance Scale Out, ScaleVNFWorkflow.robot
+7.3.1.33,Terminate a VNF Instance, TerminateVNFWorkflow.robot
+7.3.1.34,Notifications, Notifications.robot
+7.3.1.35,API Version Resource Endpoint, ApiVersion.robot
+7.3.1.36,Notification Endpoint,NotificationEndpoint.robot
+7.3.1.37,Change current VNF package,ChangeCurrentVNFPackageTask.robot
+7.3.1.38,Create VNF Snapshot Task,CreateVNFSnapshotTask.robot
+7.3.1.39,Revert to VNF Snapshot Task,RevertToVNFSnapshotTask.robot
+7.3.1.40,VNF Snapshots,VNFSnapshots.robot
+7.3.1.41,Individual VNF Snapshot,IndividualVNFSnapshot.robot
+7.3.1.42,VNF state snapshot,VNFStateSnapshot.robot
+7.3.2,VNF Lifecycle Operation Granting Interface, VNFLifecycleOperationGranting-API
+7.3.2.1,Grants, Grants.robot
+7.3.2.2,Individual Grant, IndividualGrant.robot
+7.3.2.3,API Version Resource Endpoint, ApiVersion.robot
+7.3.3,VNF Package Management Interface, VNFPackageManagement-API
+7.3.3.1,VNF Packages Resource Endpoint, VNFPackages.robot
+7.3.3.2,Individual VNF Package Resource Endpoint, IndividualVNFPackage.robot
+7.3.3.3,VNF Package Content Resource Endpoint, VNFPackageContent.robot
+7.3.3.4,VNFD In Individual VNF Package Resource Endpoint, VNFDInIndividualVNFPackage.robot
+7.3.3.5,Individual VNF Package Artifact Resource Endpoint, VNFPackageArtifacts.robot
+7.3.3.6,Subscriptions Resource Endpoint, Subscriptions.robot
+7.3.3.7,Individual Subscription Resource Endpoint, IndividualSubscription.robot
+7.3.3.8,Notifications, Notifications.robot
+7.3.3.9,API Version Resource Endpoint, ApiVersion.robot
+7.3.3.10,Manifest In Individual VNF Package Endpoint,ManifestInIndividualVNFPackage.robot
+7.3.3.11,VNF Package Artifacts Endpoint,VNFPackageArtifacts.robot
+7.3.3.12,Notification Endpoint,NotificationEndpoint.robot
+7.3.4,VNF Performance Management Interface, VNFPerformanceManagement-API
+7.3.4.1,PM Jobs Resource Endpoint, PMJobs.robot
+7.3.4.2,Individual Pm Job Resource Endpoint, IndividualPmJob.robot
+7.3.4.3,Individual Performance Report Resource Endpoint, IndividualReport.robot
+7.3.4.4,Thresholds Resource Endpoint, Thresholds.robot
+7.3.4.5,Individual Threshold Resource Endpoint, IndividualThreshold.robot
+7.3.4.6,Void,Void
+7.3.4.7,Void,Void
+7.3.4.8,Notifications,Notifications.robot
+7.3.4.9,API Version Resource Endpoint, ApiVersion.robot
+7.3.4.10,Notification Endpoint,NotificationEndpoint.robot
+7.3.5,VNF Fault Management interface, VNFFaultManagement-API
+7.3.5.1,Alarms, Alarms.robot
+7.3.5.2,Individual Alarm, IndividualAlarm.robot
+7.3.5.3,Subscriptions, Subscriptions.robot
+7.3.5.4,Individual Subscription, IndividualSubscription.robot
+7.3.5.5,Notifications,Notifications.robot
+7.3.5.6,API Version Resource Endpoint, ApiVersion.robot
+7.3.5.7,Notification Endpoint,NotificationEndpoint.robot
+7.3.6,VNF Indicator Interface, VNFIndicator-API
+7.3.6.1,VNF Indicators Resource Endpoint, VNFIndicators.robot
+7.3.6.2,VNF Indicators Related to a VNF Instance Resource Endpoint, VnfIndicatorsInVnfInstanceId.robot
+7.3.6.3,Individual VNF Indicator Resource Endpoint, IndividualVNFindicator.robot
+7.3.6.4,Subscriptions Resource Endpoint, Subscriptions.robot
+7.3.6.5,Individual Subscription Resource Endpoint, IndividualSubscription.robot
+7.3.6.6,Notifications, Notifications.robot
+7.3.6.7,API Version Resource Endpoint, ApiVersion.robot
+7.3.6.8,Notification Endpoint,NotificationEndpoint.robot
+7.3.7,Virtualised Resources Quota Available Notification interface, VirtualisedResourcesQuotaAvailableNotification-API
+7.3.7.1,Subscriptions, Subscriptions.robot
+7.3.7.2,Individual Subscription, IndividualSubscription.robot
+7.3.7.3,API Version Resource Endpoint, ApiVersion.robot
+7.3.7.4,Notification Endpoint,NotificationEndpoint.robot
+7.3.7.5,Notifications,Notifications.robot
+7.3.8,VNF Snapshot Package Management Interface, VNFSnapshotPackageManagement-API
+7.3.8.1,API Version Resource Endpoint, ApiVersion.robot
+7.3.8.2,VNF Snapshot Packages Endpoint,VNFSnapshotPackages.robot
+7.3.8.3,Individual VNF Snapshot Package Endpoint,IndividualVNFSnapshotPackage.robot
+7.3.8.4,VNF Snapshot Package Content Endpoint,VNFSnapshotPackageContent.robot
+7.3.8.5,Individual VNF Snapshot Package Artifact Endpoint,IndividualVNFSnapshotPackageArtifact.robot
diff --git a/indexes/sol_005_index.csv b/indexes/sol_005_index.csv
index 5bf0ff7ccc28edbac878c7972ff89d1bed26745a..936db8c95f1cc6b74575ee432a03fe51a9033ca9 100644
--- a/indexes/sol_005_index.csv
+++ b/indexes/sol_005_index.csv
@@ -15,6 +15,8 @@
5.3.1.13,PNFD Resource Endpoint, PNFD.robot
5.3.1.14,PNFD Archive Manifest Resource Endpoint, PNFDArchiveManifest.robot
5.3.1.15,Notification Endpoint,NotificationEndpoint.robot
+5.3.1.16,Individual NSD Archive Artifact Resource Endpoint,IndividualNSDArchiveArtifact.robot
+5.3.1.17,Individual PNFD Archive Artifact Resource Endpoint,IndividualPNFDArchiveArtifact.robot
5.3.2,NS Lifecycle Management interface, NSLifecycleManagement-API
5.3.2.1,NsInstances, NSInstances.robot
5.3.2.2,Individual NSInstance, IndividualNSInstance.robot
@@ -42,6 +44,8 @@
5.3.2.24, Update Flow of NS lifecycle management operations, UpdateNSTaskWorkflow.robot
5.3.2.25,API Version Resource Endpoint, ApiVersion.robot
5.3.2.26,Notification Endpoint,NotificationEndpoint.robot
+5.3.2.27,VNF Snapshots, VNFSnapshots.robot
+5.3.2.28,Individual VNF Snapshot, IndividualVNFSnapshot.robot
5.3.3,NS Fault Management interface, NSFaultManagement-API
5.3.3.1,Alarms, Alarms.robot
5.3.3.2,Individual Alarm, IndividualAlarm.robot
@@ -56,6 +60,8 @@
5.3.4.3,Individual Performance Report Resource Endpoint, IndividualReport.robot
5.3.4.4,Thresholds Resource Endpoint, Thresholds.robot
5.3.4.5,Individual Threshold Resource Endpoint, IndividualThreshold.robot
+5.3.4.6,Void,Void
+5.3.4.7,Void,Void
5.3.4.8,Notifications, Notifications.robot
5.3.4.9,API Version Resource Endpoint, ApiVersion.robot
5.3.4.10,Notification Endpoint,NotificationEndpoint.robot
@@ -71,7 +77,7 @@
5.3.5.9,Notifications, Notifications.robot
5.3.5.10,API Version Resource Endpoint, ApiVersion.robot
5.3.5.11,Manifest In Individual VNF Package Endpoint,ManifestInIndividualVNFPackage.robot
-5.3.5.11,VNF Package Artifacts Endpoint,VNFPackageArtifacts.robot
+5.3.5.12,VNF Package Artifacts Endpoint,VNFPackageArtifacts.robot
5.3.5.13,Notification Endpoint,NotificationEndpoint.robot
5.3.6,NFVI Capacity Information Interface, NFVICapacityInformation-API
5.3.6.1,API Version Resource Endpoint, ApiVersion.robot
diff --git a/requirements.txt b/requirements.txt
index 4f00299b7ec3c17280e3269345fe687d2d7815e7..a5adb34575a5a81a184fb415507b75b258201ca0 100644
--- a/requirements.txt
+++ b/requirements.txt
@@ -2,7 +2,7 @@
# pip -r requirements.txt
git+https://github.com/etsi-cti-admin/RESTinstance
-robotframework==3.1
+robotframework==3.2
#RESTinstance==1.0.0rc4
robotframework-dependencylibrary==1.0.0.post1
robotframework-jsonlibrary==0.3