diff --git a/README.md b/README.md
index 13b9fa550ff77db89e7e6be36b71cbaa4fa17adb..e15262e3ed2402571e40ce9ff0464fb001a15918 100644
--- a/README.md
+++ b/README.md
@@ -14,15 +14,23 @@ More information and download is available at [DGS/NFV-TST010ed431]().
The NFV API Conformance test specification is available in the following versions:
-| TST010 Version | SOL Specifications | API Conformance Tests |
-|----------------|-------------------------------------------------------------------------------------------|----------------------------------------------------------------|
-| v2.4.1 | SOL002 SOL003 SOL005 v2.4.1 | [v2.4.1](https://forge.etsi.org/rep/nfv/api-tests/tree/2.4.1/) |
-| v2.6.1 | SOL002 SOL003 SOL005 v2.6.1 | [v2.6.1](https://forge.etsi.org/rep/nfv/api-tests/tree/2.6.1/) |
-| v2.7.1 | SOL002 SOL003 SOL005 v2.7.1 | [v2.7.1](https://forge.etsi.org/rep/nfv/api-tests/tree/2.7.1/) |
-| v3.3.1 | SOL002 SOL003 SOL005 v3.3.1
SOL009 SOL011 v3.3.1
SOL012 v3.4.1 | [v3.3.1](https://forge.etsi.org/rep/nfv/api-tests/tree/3.3.1/) |
-| v3.5.1 | SOL002 SOL003 SOL005 v3.5.1
SOL009 v3.5.1
SOL011 v3.3.1
SOL012 v3.4.1 | [v3.5.1](https://forge.etsi.org/rep/nfv/api-tests/tree/3.5.1/) |
-| v3.6.1 | SOL002 SOL003 SOL005 v3.6.1
SOL009 v3.6.1
SOL011 v3.3.1
SOL012 v3.4.1 | [v3.6.1](https://forge.etsi.org/rep/nfv/api-tests/tree/3.6.1/) |
-| v4.3.1 | SOL002 SOL003 SOL005 v4.3.1
SOL009 v4.3.1
SOL011 v3.3.1
SOL012 v3.4.1 | [v3.6.1](https://forge.etsi.org/rep/nfv/api-tests/tree/4.3.1/) |
+| TST010 Version | SOL Specifications | API Conformance Tests |
+|----------------------|-----------------------------------------------------------------------------------------|-----------------------------------------------------------|
+| v2.4.1 | SOL002 SOL003 SOL005 v2.4.1 | [v2.4.1](https://forge.etsi.org/rep/nfv/api-tests/tree/2.4.1/) |
+| v2.4.1-maintenance | SOL002 SOL003 SOL005 v2.4.1 | [v2.4.1-fix-plu](https://forge.etsi.org/rep/nfv/api-tests/tree/2.4.1-fix-plu/) |
+| v2.6.1 | SOL002 SOL003 SOL005 v2.6.1 | [v2.6.1](https://forge.etsi.org/rep/nfv/api-tests/tree/2.6.1/) |
+| v2.6.1-maintenance | SOL002 SOL003 SOL005 v2.6.1 | [v2.6.1-fix-plu](https://forge.etsi.org/rep/nfv/api-tests/tree/2.6.1-fix-plu/) |
+| v2.7.1 | SOL002 SOL003 SOL005 v2.7.1 | [v2.7.1](https://forge.etsi.org/rep/nfv/api-tests/tree/2.7.1/) |
+| v2.7.1-maintenance | SOL002 SOL003 SOL005 v2.7.1 | [v2.7.1-fix-plu](https://forge.etsi.org/rep/nfv/api-tests/tree/2.7.1-fix-plu/)
+| v2.8.1 | SOL002 SOL003 SOL005 v2.8.1 | [v2.8.1](https://forge.etsi.org/rep/nfv/api-tests/tree/2.8.1/) |
+| v2.8.1-maintenance | SOL002 SOL003 SOL005 v2.8.1 | [v2.8.1-fix-plu](https://forge.etsi.org/rep/nfv/api-tests/tree/2.8.1-fix-plu/)|
+| v3.3.1 | SOL002 SOL003 SOL005 v3.3.1
SOL009 SOL011 v3.3.1
SOL012 v3.4.1 | [v3.3.1](https://forge.etsi.org/rep/nfv/api-tests/tree/3.3.1/) |
+| v3.3.1-maintenance | SOL002 SOL003 SOL005 v3.3.1
SOL009 SOL011 v3.3.1
SOL012 v3.4.1 | [v3.3.1-fix-plu](https://forge.etsi.org/rep/nfv/api-tests/tree/3.3.1-fix-plu/) |
+| v3.5.1 | SOL002 SOL003 SOL005 v3.5.1
SOL009 v3.5.1
SOL011 v3.3.1
SOL012 v3.4.1 | [v3.5.1](https://forge.etsi.org/rep/nfv/api-tests/tree/3.5.1/) |
+| v3.5.1-maintenance | SOL002 SOL003 SOL005 v3.5.1
SOL009 v3.5.1
SOL011 v3.3.1
SOL012 v3.4.1 | [v3.5.1-fix-plu](https://forge.etsi.org/rep/nfv/api-tests/tree/3.5.1-fix-plu/) |
+| v3.6.1 | SOL002 SOL003 SOL005 v3.6.1
SOL009 v3.6.1
SOL011 v3.3.1
SOL012 v3.4.1 | [v3.6.1](https://forge.etsi.org/rep/nfv/api-tests/tree/3.6.1/) |
+| 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
(under development) |
## Test Specification Overview
diff --git a/SOL002/README.md b/SOL002/README.md
index ec4924faa93a02f060c79780cdf9799084b84bbe..4a4d6a18fa680be9bfe5dcf2bfc7897963e0cdb1 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 v3.5.1: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/002/03.06.01_60/gs_NFV-SOL002v030601p.pdf
+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
diff --git a/SOL002/VNFConfiguration-API/ApiVersion.robot b/SOL002/VNFConfiguration-API/ApiVersion.robot
index 03f15c0ecd57832db743cc94910d5d71ea68268b..601b261d26c567853b54e6b9ad992fbf083fe3fa 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] v3.5.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.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 afcd2d2289ff9be1bdb3acba3ce38517ee2edbb6..df2794519a13bd8c6285c6858699bdcae205908b 100644
--- a/SOL002/VNFConfiguration-API/Configuration.robot
+++ b/SOL002/VNFConfiguration-API/Configuration.robot
@@ -4,6 +4,7 @@ Library REST ${EM-VNF_SCHEMA}://${EM-VNF_HOST}:${EM-VNF_PORT} ssl_verif
Library JSONLibrary
Library JSONSchemaLibrary schemas/
Library OperatingSystem
+Library String
Library DependencyLibrary
*** Test Cases ***
@@ -12,13 +13,13 @@ 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] v3.6.1
+ ... Reference: Clause 9.4.2.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.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
Send VNF configuration
Check HTTP Response Status Code Is 200
- Check HTTP Response Header Contains ETag
+ Check HTTP Response Header Contains ETag and Last-Modified
Check HTTP Response Body Json Schema Is vnfConfigModifications
Check Postcondition VNF Is Configured
@@ -28,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] v3.6.1
+ ... Reference: Clause 9.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -42,13 +43,13 @@ 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] v3.6.1
+ ... Reference: Clause 9.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation of HTTP Etag opaque identifiers
... Post-Conditions: none
Get VNF configuration
Check HTTP Response Status Code Is 200
- Check HTTP Response Header Contains ETag
+ Check HTTP Response Header Contains ETag and Last-Modified
Check HTTP Response Body Json Schema Is vnfConfiguration
Set new VNF Configuration - HTTP Etag precondition unsuccessful
@@ -57,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] v3.6.1
+ ... Reference: Clause 9.4.2.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.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
@@ -71,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] v3.6.1
+ ... Reference: Clause 9.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -83,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] v3.6.1
+ ... Reference: Clause 9.4.2.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -95,13 +96,44 @@ 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] v3.6.1
+ ... Reference: Clause 9.4.2.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
Send DELETE Request for VNF Configuration
Check HTTP Response Status Code Is 405
+
+Set new VNF Configuration With Attribute vnfConfigurationData
+ [Documentation] Test ID: 6.3.1.1.8
+ ... 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
+ ... 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
+ Send VNF configuration with vnfConfigurationData
+ Check HTTP Response Status Code Is 200
+ Check HTTP Response Header Contains ETag and Last-Modified
+ Check HTTP Response Body Json Schema Is vnfConfigModifications
+ Check Postcondition VNF Is Configured
+Set new VNF Configuration With Attribute vnfcConfigurationData
+ [Documentation] Test ID: 6.3.1.1.9
+ ... 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
+ ... 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
+ Send VNF configuration with vnfcConfigurationData
+ Check HTTP Response Status Code Is 200
+ Check HTTP Response Header Contains ETag and Last-Modified
+ Check HTTP Response Body Json Schema Is vnfConfigModifications
+ Check Postcondition VNF Is Configured
+
+
*** Keywords ***
Get VNF configuration
Log Query VNF The GET method queries information about a configuration.
@@ -128,11 +160,12 @@ Check HTTP Response Status Code Is
Should Be Equal As Strings ${response['status']} ${expected_status}
Log Status code validated
-Check HTTP Response Header Contains
- [Arguments] ${CONTENT_TYPE}
+Check HTTP Response Header Contains ETag and Last-Modified
+ Pass Execution If ${HEADER_TEST_SUPPORTED} == 0 Headers testing not supported. Skipping the Test.
Log ${response['headers']}
- Should Contain ${response['headers']} ${CONTENT_TYPE}
- Log Header is present
+ Should Contain ${response['headers']} Etag
+ Should Contain ${response['headers']} Last-Modified
+ Log Etag and Last-Modified Headers are present
Check HTTP Response Body Json Schema Is
[Arguments] ${input}
@@ -187,4 +220,31 @@ Send DELETE Request for VNF Configuration
Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"${AUTHORIZATION_HEADER}":"${AUTHORIZATION_TOKEN}"}
Delete ${apiRoot}/${apiName}/${apiMajorVersion}/configuration
${output}= Output response
- Set Suite Variable ${response} ${output}
\ No newline at end of file
+ Set Suite Variable ${response} ${output}
+
+Send VNF configuration with vnfConfigurationData
+ log Trying to perform a PATCH. This method modifies the configuration when attribute is vnfConfigurationData
+ Set Headers {"Accept":"${ACCEPT}"}
+ Set Headers {"Content-Type": "${CONTENT_TYPE}"}
+ Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"${AUTHORIZATION_HEADER}":"${AUTHORIZATION_TOKEN}"}
+ ${template}= Get File jsons/vnfConfigModificationsWithVnfConfigurationData.json
+ ${body}= Format String ${template} cpId=${cpId} cpdId=${cpdId}
+ Patch ${apiRoot}/${apiName}/${apiMajorVersion}/configuration ${body}
+ ${output}= Output response
+ Set Suite Variable ${response} ${output}
+
+Send VNF configuration with vnfcConfigurationData
+ log Trying to perform a PATCH. This method modifies the configuration when attribute is vnfcConfigurationData
+ Set Headers {"Accept":"${ACCEPT}"}
+ Set Headers {"Content-Type": "${CONTENT_TYPE}"}
+ Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"${AUTHORIZATION_HEADER}":"${AUTHORIZATION_TOKEN}"}
+ ${template}= Get File jsons/vnfConfigModificationsWithvnfcConfigurationData.json
+ ${body}= Format String ${template} vnfcInstanceId=${vnfcInstanceId} cpId=${cpId} cpdId=${cpdId}
+ Patch ${apiRoot}/${apiName}/${apiMajorVersion}/configuration ${body}
+ ${output}= Output response
+ Set Suite Variable ${response} ${output}
+Check HTTP Response Header Contains
+ [Arguments] ${CONTENT_TYPE}
+ Log ${response['headers']}
+ Should Contain ${response['headers']} ${CONTENT_TYPE}
+ Log Header is present
\ No newline at end of file
diff --git a/SOL002/VNFConfiguration-API/environment/variables.txt b/SOL002/VNFConfiguration-API/environment/variables.txt
index 46ba91d8df1967e6d6bc0caeb67b7d4d3c7e674f..2e7355081c23089053107fbe10736eac284cbe2a 100644
--- a/SOL002/VNFConfiguration-API/environment/variables.txt
+++ b/SOL002/VNFConfiguration-API/environment/variables.txt
@@ -13,8 +13,14 @@ ${AUTHORIZATION_TOKEN} Bearer 0b79bab50daca910b000d4f1a2b675d604257e42
${CONTENT_TYPE} application/json
+${HEADER_TEST_SUPPORTED} 0
+
${apiRoot} /
${apiName} vnfconfig
${apiMajorVersion} v1
${etag} enter-etag-value-for-testing-mismatch-condition
+
+${cpId}
+${cpdId}
+${vnfcInstanceId}
diff --git a/SOL002/VNFConfiguration-API/jsons/vnfConfigModifications.json b/SOL002/VNFConfiguration-API/jsons/vnfConfigModifications.json
index 5a14e63b86bdbc474fa969b54373f23285ed7e16..16f8c15d54cb83ec0993d537872f7dfd3283deff 100644
--- a/SOL002/VNFConfiguration-API/jsons/vnfConfigModifications.json
+++ b/SOL002/VNFConfiguration-API/jsons/vnfConfigModifications.json
@@ -14,7 +14,6 @@
}
]
},
- "dhcpServer": "string",
"vnfSpecificData": {}
},
"vnfcConfigurationData": [
diff --git a/SOL002/VNFConfiguration-API/jsons/vnfConfigModificationsWithVnfConfigurationData.json b/SOL002/VNFConfiguration-API/jsons/vnfConfigModificationsWithVnfConfigurationData.json
new file mode 100644
index 0000000000000000000000000000000000000000..65d0a6695c916f5780942fc8b4cd6fd35627a30f
--- /dev/null
+++ b/SOL002/VNFConfiguration-API/jsons/vnfConfigModificationsWithVnfConfigurationData.json
@@ -0,0 +1,19 @@
+{{
+ "vnfConfigurationData": {
+ "extCpConfig": {
+ "cpId": "{cpId}",
+ "cpdId": "{cpdId}",
+ "addresses": [
+ {
+ "address": {
+ "macAddress": "string",
+ "ipAddress": "string"
+ },
+ "useDynamicAddress": true,
+ "port": 0
+ }
+ ]
+ },
+ "vnfSpecificData": {}
+ }
+}}
\ No newline at end of file
diff --git a/SOL002/VNFConfiguration-API/jsons/vnfConfigModificationsWithvnfcConfigurationData.json b/SOL002/VNFConfiguration-API/jsons/vnfConfigModificationsWithvnfcConfigurationData.json
new file mode 100644
index 0000000000000000000000000000000000000000..dbbeb16ea50e8e479d670b6566826ca0851df5a5
--- /dev/null
+++ b/SOL002/VNFConfiguration-API/jsons/vnfConfigModificationsWithvnfcConfigurationData.json
@@ -0,0 +1,26 @@
+{{
+ "vnfcConfigurationData": [
+ {
+ "vnfcInstanceId": "{vnfcInstanceId}",
+ "intCpConfig": [
+ {
+ "cpId": "{cpId}",
+ "cpdId": "{cpdId}",
+ "addresses": [
+ {
+ "address": {
+ "macAddress": "string",
+ "ipAddress": "string"
+ },
+ "useDynamicAddress": true,
+ "port": 0
+ }
+ ]
+ }
+ ],
+ "dhcpServer": "string",
+ "vnfcSpecificData": {}
+ }
+ ],
+ "vnfcConfigurationDataDeleteIds": []
+}}
\ No newline at end of file
diff --git a/SOL002/VNFConfiguration-API/schemas/vnfConfigModifications.schema.json b/SOL002/VNFConfiguration-API/schemas/vnfConfigModifications.schema.json
index e69ca505e252ae4b92077f0ee6a0ad0970939f1f..01f6087b6a3ef0f8551d13d2bb7348f6a1826f86 100644
--- a/SOL002/VNFConfiguration-API/schemas/vnfConfigModifications.schema.json
+++ b/SOL002/VNFConfiguration-API/schemas/vnfConfigModifications.schema.json
@@ -15,7 +15,7 @@
],
"properties": {
"vnfConfigurationData": {
- "description": "This type represents configuration parameters of a VNF instance.\n",
+ "description": "This type represents configuration parameters of a VNF instance. * NOTE:\tETSI GS NFV-SOL 001 specifies the structure and format of\n the VNFD based on TOSCA specifications.\n",
"type": "object",
"properties": {
"extCpConfig": {
@@ -99,11 +99,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"
- },
"vnfSpecificData": {
"description": "This 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"
@@ -111,10 +106,10 @@
}
},
"vnfcConfigurationData": {
- "description": "Modifications to configuration data for certain VNFC instances. See NOTE 1 and NOTE 2. If present, the modifications of the \"vnfcConfigurationData\" attribute shall follow these provisions:\n Modifying an attribute that is an array of objects of type \"VnfcConfigurationData\".\n Assumptions:\n 1) \"oldList\" is the \"VnfcConfigurationData\" array to be modified and \"newList\"\n is the \"VnfcConfigurationData\" array that contains the changes.\n 2) \"oldEntry\" is an entry in \"oldList\" and \"newEntry\" is an entry in \"newList\".\n 3) A \"newEntry\" has a \"corresponding entry\" if there exists an \"oldEntry\" that\n has the same content of the \"vnfcInstanceId\" attribute as the \"newEntry\";\n a \"newEntry\" has no corresponding entry if no such \"oldEntry\" exists.\n 4) In any array of \"VnfcConfigurationData\" structures, the content of \"vnfcInstanceId\"\n is unique (i.e. there shall be no two entries with the same content of \"vnfcInstanceId\").\n Provisions:\n 1) For each \"newEntry\" in \"newList\" that has no corresponding entry in \"oldList\",\n the \"oldList\" array shall be modified by adding that \"newEntry\".\n\n 2) For each \"newEntry\" in \"newList\" that has a corresponding \"oldEntry\" in \"oldList\",\n the value of \"oldEntry\" shall be updated with the value of \"newEntry\" according to\n the rules of JSON Merge PATCH (see IETF RFC 7396 ).\n",
+ "description": "Modifications to configuration data for certain VNFC instances. See NOTE 1 and NOTE 2. If present, the modifications of the \"vnfcConfigurationData\" attribute shall follow these provisions:\n Modifying an attribute that is an array of objects of type \"VnfcConfigurationData\".\n Assumptions:\n 1) \"oldList\" is the \"VnfcConfigurationData\" array to be modified and \"newList\"\n is the \"VnfcConfigurationData\" array that contains the changes.\n 2) \"oldEntry\" is an entry in \"oldList\" and \"newEntry\" is an entry in \"newList\".\n 3) A \"newEntry\" has a \"corresponding entry\" if there exists an \"oldEntry\" that\n has the same content of the \"vnfcInstanceId\" attribute as the \"newEntry\";\n a \"newEntry\" has no corresponding entry if no such \"oldEntry\" exists.\n 4) In any array of \"VnfcConfigurationData\" structures, the content of \"vnfcInstanceId\"\n is unique (i.e. there shall be no two entries with the same content of \"vnfcInstanceId\").\n Provisions:\n 1) For each \"newEntry\" in \"newList\" that has no corresponding entry in \"oldList\",\n the \"oldList\" array shall be modified by adding that \"newEntry\".\n\n 2) For each \"newEntry\" in \"newList\" that has a corresponding \"oldEntry\" in \"oldList\",\n the value of \"oldEntry\" shall be updated with the value of \"newEntry\" according to\n the rules of JSON Merge PATCH (see IETF RFC 7396 ).\n",
"type": "array",
"items": {
- "description": "This type represents configuration parameters of a VNFC instance.\n",
+ "description": "This type represents configuration parameters of a VNFC instance. * NOTE:\tETSI GS NFV-SOL 001 specifies the structure and format\n of the VNFD based on TOSCA specifications.\n",
"type": "object",
"required": [
"vnfcInstanceId"
diff --git a/SOL002/VNFConfiguration-API/schemas/vnfConfiguration.schema.json b/SOL002/VNFConfiguration-API/schemas/vnfConfiguration.schema.json
index 1156069c2a77f485b8cff43ce6826283c414aa8b..c28f9c65ee72d004a5a7d0824181b1e377184023 100644
--- a/SOL002/VNFConfiguration-API/schemas/vnfConfiguration.schema.json
+++ b/SOL002/VNFConfiguration-API/schemas/vnfConfiguration.schema.json
@@ -6,69 +6,92 @@
],
"properties": {
"vnfConfigurationData": {
- "description": "This type represents configuration parameters of a VNF instance.\n",
+ "description": "This type represents configuration parameters of a VNF instance. * NOTE:\tETSI GS NFV-SOL 001 specifies the structure and format of\n the VNFD based on TOSCA specifications.\n",
"type": "object",
"properties": {
"extCpConfig": {
- "description": "This type represents configuration parameters of a CP instance.\n",
- "type": "object",
- "required": [
- "cpId",
- "cpdId",
- "addresses"
- ],
- "properties": {
- "cpId": {
- "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 VNF descriptor.\n",
- "type": "string"
- },
- "addresses": {
- "description": "Network address and port assigned to the CP.\n",
- "type": "array",
- "items": {
- "description": "This type represents configuration parameters of a CP instance address. * NOTE 1: Either \"address\" or \"useDynamicAddress\" shall be present.\n * NOTE 2: At least one of \"macAddress\" and \"ipAddress\" shall be present.\n",
- "type": "object",
- "properties": {
- "address": {
- "description": "Network address that has been configured on the CP. See NOTE 1.\n",
- "type": "object",
- "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"
- },
- "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"
+ "description": "Configuration parameters for the external CPs of the VNF instance.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents configuration parameters of a CP instance.\n",
+ "type": "object",
+ "required": [
+ "cpId",
+ "cpdId",
+ "addresses"
+ ],
+ "properties": {
+ "cpId": {
+ "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 VNF descriptor.\n",
+ "type": "string"
+ },
+ "addresses": {
+ "description": "Network address and port assigned to the CP.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents configuration parameters of a CP instance address.\n * NOTE 1: Either \"address\" or \"useDynamicAddress\" shall be present.\n * NOTE 2: At least one of \"macAddress\" and \"ipAddress\" shall be present.\n",
+ "type": "object",
+ "oneOf": [
+ {
+ "required": [
+ "address"
+ ]
+ },
+ {
+ "required": [
+ "useDynamicAddress"
+ ]
+ }
+ ],
+ "anyOf": [
+ {
+ "required": [
+ "macAddress"
+ ]
+ },
+ {
+ "required": [
+ "ipAddress"
+ ]
+ }
+ ],
+ "properties": {
+ "address": {
+ "description": "Network address that has been configured on the CP. See NOTE 1.\n",
+ "type": "object",
+ "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"
+ },
+ "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"
+ }
}
+ },
+ "useDynamicAddress": {
+ "description": "Set to true if an address shall be assigned dynamically. Otherwise set to false. The default value shall be false. See NOTE 1.\n",
+ "type": "boolean"
+ },
+ "port": {
+ "description": "The port assigned to the CP instance (e.g. IP port number, Ethernet port number, etc.).\n",
+ "type": "integer"
}
- },
- "useDynamicAddress": {
- "description": "Set to true if an address shall be assigned dynamically. Otherwise set to false. The default value shall be false. See NOTE 1.\n",
- "type": "boolean"
- },
- "port": {
- "description": "The port assigned to the CP instance (e.g. IP port number, Ethernet port number, etc.).\n",
- "type": "integer"
}
}
}
}
}
},
- "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"
- },
"vnfSpecificData": {
- "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "description": "This 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"
}
}
@@ -77,7 +100,7 @@
"description": "Configuration parameters of the VNFC instances.\n",
"type": "array",
"items": {
- "description": "This type represents configuration parameters of a VNFC instance.\n",
+ "description": "This type represents configuration parameters of a VNFC instance. * NOTE:\tETSI GS NFV-SOL 001 specifies the structure and format\n of the VNFD based on TOSCA specifications.\n",
"type": "object",
"required": [
"vnfcInstanceId"
@@ -111,8 +134,32 @@
"description": "Network address and port assigned to the CP.\n",
"type": "array",
"items": {
- "description": "This type represents configuration parameters of a CP instance address. * NOTE 1: Either \"address\" or \"useDynamicAddress\" shall be present.\n * NOTE 2: At least one of \"macAddress\" and \"ipAddress\" shall be present.\n",
+ "description": "This type represents configuration parameters of a CP instance address.\n * NOTE 1: Either \"address\" or \"useDynamicAddress\" shall be present.\n * NOTE 2: At least one of \"macAddress\" and \"ipAddress\" shall be present.\n",
"type": "object",
+ "oneOf": [
+ {
+ "required": [
+ "address"
+ ]
+ },
+ {
+ "required": [
+ "useDynamicAddress"
+ ]
+ }
+ ],
+ "anyOf": [
+ {
+ "required": [
+ "macAddress"
+ ]
+ },
+ {
+ "required": [
+ "ipAddress"
+ ]
+ }
+ ],
"properties": {
"address": {
"description": "Network address that has been configured on the CP. See NOTE 1.\n",
@@ -124,7 +171,7 @@
"format": "MAC"
},
"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",
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
}
@@ -144,17 +191,337 @@
}
}
},
- "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 key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
+ "description": "This 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"
}
}
}
}
}
-}
\ No newline at end of file
+},
+"VnfConfigurationData": {
+ "description": "This type represents configuration parameters of a VNF instance. * NOTE:\tETSI GS NFV-SOL 001 specifies the structure and format of\n the VNFD based on TOSCA specifications.\n",
+ "type": "object",
+ "properties": {
+ "extCpConfig": {
+ "description": "Configuration parameters for the external CPs of the VNF instance.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents configuration parameters of a CP instance.\n",
+ "type": "object",
+ "required": [
+ "cpId",
+ "cpdId",
+ "addresses"
+ ],
+ "properties": {
+ "cpId": {
+ "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 VNF descriptor.\n",
+ "type": "string"
+ },
+ "addresses": {
+ "description": "Network address and port assigned to the CP.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents configuration parameters of a CP instance address.\n * NOTE 1: Either \"address\" or \"useDynamicAddress\" shall be present.\n * NOTE 2: At least one of \"macAddress\" and \"ipAddress\" shall be present.\n",
+ "type": "object",
+ "oneOf": [
+ {
+ "required": [
+ "address"
+ ]
+ },
+ {
+ "required": [
+ "useDynamicAddress"
+ ]
+ }
+ ],
+ "anyOf": [
+ {
+ "required": [
+ "macAddress"
+ ]
+ },
+ {
+ "required": [
+ "ipAddress"
+ ]
+ }
+ ],
+ "properties": {
+ "address": {
+ "description": "Network address that has been configured on the CP. See NOTE 1.\n",
+ "type": "object",
+ "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"
+ },
+ "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"
+ }
+ }
+ },
+ "useDynamicAddress": {
+ "description": "Set to true if an address shall be assigned dynamically. Otherwise set to false. The default value shall be false. See NOTE 1.\n",
+ "type": "boolean"
+ },
+ "port": {
+ "description": "The port assigned to the CP instance (e.g. IP port number, Ethernet port number, etc.).\n",
+ "type": "integer"
+ }
+ }
+ }
+ }
+ }
+ }
+ },
+ "vnfSpecificData": {
+ "description": "This 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"
+ }
+ }
+},
+"VnfcConfigurationData": {
+ "description": "This type represents configuration parameters of a VNFC instance. * NOTE:\tETSI GS NFV-SOL 001 specifies the structure and format\n of the VNFD based on TOSCA specifications.\n",
+ "type": "object",
+ "required": [
+ "vnfcInstanceId"
+ ],
+ "properties": {
+ "vnfcInstanceId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "intCpConfig": {
+ "description": "Configuration parameters for the internal CPs of the VNFC instance.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents configuration parameters of a CP instance.\n",
+ "type": "object",
+ "required": [
+ "cpId",
+ "cpdId",
+ "addresses"
+ ],
+ "properties": {
+ "cpId": {
+ "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 VNF descriptor.\n",
+ "type": "string"
+ },
+ "addresses": {
+ "description": "Network address and port assigned to the CP.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents configuration parameters of a CP instance address.\n * NOTE 1: Either \"address\" or \"useDynamicAddress\" shall be present.\n * NOTE 2: At least one of \"macAddress\" and \"ipAddress\" shall be present.\n",
+ "type": "object",
+ "oneOf": [
+ {
+ "required": [
+ "address"
+ ]
+ },
+ {
+ "required": [
+ "useDynamicAddress"
+ ]
+ }
+ ],
+ "anyOf": [
+ {
+ "required": [
+ "macAddress"
+ ]
+ },
+ {
+ "required": [
+ "ipAddress"
+ ]
+ }
+ ],
+ "properties": {
+ "address": {
+ "description": "Network address that has been configured on the CP. See NOTE 1.\n",
+ "type": "object",
+ "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"
+ },
+ "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"
+ }
+ }
+ },
+ "useDynamicAddress": {
+ "description": "Set to true if an address shall be assigned dynamically. Otherwise set to false. The default value shall be false. See NOTE 1.\n",
+ "type": "boolean"
+ },
+ "port": {
+ "description": "The port assigned to the CP instance (e.g. IP port number, Ethernet port number, etc.).\n",
+ "type": "integer"
+ }
+ }
+ }
+ }
+ }
+ }
+ },
+ "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"
+ }
+ }
+},
+"CpConfiguration": {
+ "description": "This type represents configuration parameters of a CP instance.\n",
+ "type": "object",
+ "required": [
+ "cpId",
+ "cpdId",
+ "addresses"
+ ],
+ "properties": {
+ "cpId": {
+ "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 VNF descriptor.\n",
+ "type": "string"
+ },
+ "addresses": {
+ "description": "Network address and port assigned to the CP.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents configuration parameters of a CP instance address.\n * NOTE 1: Either \"address\" or \"useDynamicAddress\" shall be present.\n * NOTE 2: At least one of \"macAddress\" and \"ipAddress\" shall be present.\n",
+ "type": "object",
+ "oneOf": [
+ {
+ "required": [
+ "address"
+ ]
+ },
+ {
+ "required": [
+ "useDynamicAddress"
+ ]
+ }
+ ],
+ "anyOf": [
+ {
+ "required": [
+ "macAddress"
+ ]
+ },
+ {
+ "required": [
+ "ipAddress"
+ ]
+ }
+ ],
+ "properties": {
+ "address": {
+ "description": "Network address that has been configured on the CP. See NOTE 1.\n",
+ "type": "object",
+ "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"
+ },
+ "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"
+ }
+ }
+ },
+ "useDynamicAddress": {
+ "description": "Set to true if an address shall be assigned dynamically. Otherwise set to false. The default value shall be false. See NOTE 1.\n",
+ "type": "boolean"
+ },
+ "port": {
+ "description": "The port assigned to the CP instance (e.g. IP port number, Ethernet port number, etc.).\n",
+ "type": "integer"
+ }
+ }
+ }
+ }
+ }
+},
+"CpAddress": {
+ "description": "This type represents configuration parameters of a CP instance address.\n * NOTE 1: Either \"address\" or \"useDynamicAddress\" shall be present.\n * NOTE 2: At least one of \"macAddress\" and \"ipAddress\" shall be present.\n",
+ "type": "object",
+ "oneOf": [
+ {
+ "required": [
+ "address"
+ ]
+ },
+ {
+ "required": [
+ "useDynamicAddress"
+ ]
+ }
+ ],
+ "anyOf": [
+ {
+ "required": [
+ "macAddress"
+ ]
+ },
+ {
+ "required": [
+ "ipAddress"
+ ]
+ }
+ ],
+ "properties": {
+ "address": {
+ "description": "Network address that has been configured on the CP. See NOTE 1.\n",
+ "type": "object",
+ "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"
+ },
+ "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"
+ }
+ }
+ },
+ "useDynamicAddress": {
+ "description": "Set to true if an address shall be assigned dynamically. Otherwise set to false. The default value shall be false. See NOTE 1.\n",
+ "type": "boolean"
+ },
+ "port": {
+ "description": "The port assigned to the CP instance (e.g. IP port number, Ethernet port number, etc.).\n",
+ "type": "integer"
+ }
+ }
+}
diff --git a/SOL002/VNFFaultManagement-API/Alarms.robot b/SOL002/VNFFaultManagement-API/Alarms.robot
index 5becb1c2d32a02b0732128f0af0c8a1ce8d2e958..806b40f8691d36b8712137455e6160493cc866b3 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] v3.6.1
+ ... Reference: Clause 7.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.2.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.2.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.2.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.2.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.2.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.2.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.2.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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 1a44e71cbcb5b56fcc9847ddeff6feddfbf7db5c..630a5705ec97ef3567adc542e8daa7dc673c9e86 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] v3.5.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.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 3b3d3cf8ac52373420e4dcf0f307f7a09c7302be..66bbc3465bdac0a97f0908beca234d227b75fd90 100644
--- a/SOL002/VNFFaultManagement-API/EscalatePerceivedSeverityTask.robot
+++ b/SOL002/VNFFaultManagement-API/EscalatePerceivedSeverityTask.robot
@@ -2,6 +2,8 @@
Resource environment/variables.txt
Library REST ${VNFM_SCHEMA}://${VNFM_HOST}:${VNFM_PORT} ssl_verify=false
Library JSONSchemaLibrary
+Library OperatingSystem
+Library String
Suite Setup Check resource existence
*** Test Cases ***
@@ -10,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] v3.6.1
+ ... Reference: Clause 7.4.4.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -22,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] v3.6.1
+ ... Reference: Clause 7.4.4.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -34,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] v3.6.1
+ ... Reference: Clause 7.4.4.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -46,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] v3.6.1
+ ... Reference: Clause 7.4.4.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -58,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] v3.6.1
+ ... Reference: Clause 7.4.4.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -77,9 +79,12 @@ POST escalate severity
Set Headers {"Accept":"${ACCEPT}"}
Set Headers {"Content-Type": "${CONTENT_TYPE}"}
Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"${AUTHORIZATION_HEADER}":"${AUTHORIZATION_TOKEN}"}
- Post ${apiRoot}/${apiName}/${apiMajorVersion}/alarms/${alarmId}/escalate ${PerceivedSeverity}
+ ${template}= Get File jsons/EscalatePerceivedSeverity.json
+ ${body}= Format String ${template} perceivedSeverity=${PerceivedSeverity}
+ Post ${apiRoot}/${apiName}/${apiMajorVersion}/alarms/${alarmId}/escalate ${body}
${outputResponse}= Output response
Set Global Variable ${response} ${outputResponse}
+
GET escalate severity
log Trying to perform a GET. This method should not be implemented
Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"${AUTHORIZATION_HEADER}":"${AUTHORIZATION_TOKEN}"}
diff --git a/SOL002/VNFFaultManagement-API/IndividualAlarm.robot b/SOL002/VNFFaultManagement-API/IndividualAlarm.robot
index bb549e1e37129ec1272615aaf65b9f4351e30006..07c739c29d5474c2efe384509d7870390389f0b0 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] v3.6.1
+ ... Reference: Clause 7.4.3.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -27,12 +27,13 @@ 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] v3.6.1
+ ... Reference: Clause 7.4.3.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
GET Alarm Task
Check HTTP Response Status Code Is 200
+ Check HTTP Response Header Contains ETag and Last-Modified
Check HTTP Response Body Json Schema Is alarm
PUT Individual Alarm - Method not implemented
@@ -40,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] v3.6.1
+ ... Reference: Clause 7.4.3.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -52,12 +53,13 @@ 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] v3.6.1
+ ... Reference: Clause 7.4.3.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
PATCH Alarm Task
Check HTTP Response Status Code Is 200
+ Check HTTP Response Header Contains ETag and Last-Modified
Check HTTP Response Body Json Schema Is alarmModifications
PATCH Individual Alarm - Precondition failed
@@ -65,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] v3.6.1
+ ... Reference: Clause 7.4.3.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: The alarm resource is not modified
@@ -79,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] v3.6.1
+ ... Reference: Clause 7.4.3.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: The alarm resource is not modified
@@ -93,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] v3.6.1
+ ... Reference: Clause 7.4.3.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -105,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] v3.6.1
+ ... Reference: Clause 7.4.3.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -168,6 +170,13 @@ GET Alarm Task
Set Suite Variable &{original_etag} ${etag}
${outputResponse}= Output response
Set Global Variable ${response} ${outputResponse}
+
+Check HTTP Response Header Contains ETag and Last-Modified
+ Pass Execution If ${HEADER_TEST_SUPPORTED} == 0 Headers testing not supported. Skipping the Test.
+ Log ${response['headers']}
+ Should Contain ${response['headers']} Etag
+ Should Contain ${response['headers']} Last-Modified
+ Log Etag and Last-Modified Headers are present
GET Alarm Task with filter
Log Query VNF The GET method queries information about individual alarm with filters.
Set Headers {"Accept":"${ACCEPT}"}
@@ -202,3 +211,8 @@ Check Postcondition VNF individual alarm Unmodified (Implicit)
GET Alarm Task
Should Be Equal As Strings ${origResponse['body']['callbackUri']} ${response['body']['callbackUri']}
+Check HTTP Response Header Contains
+ [Arguments] ${CONTENT_TYPE}
+ Should Contain ${response['headers']} ${CONTENT_TYPE}
+ Log Header is present
+
diff --git a/SOL002/VNFFaultManagement-API/IndividualSubscription.robot b/SOL002/VNFFaultManagement-API/IndividualSubscription.robot
index a5a755b4e99fd23f52388228603019d0d12fae7c..52438e58acaf8fc90e7183e69a356c2c21c368c1 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] v3.6.1
+ ... Reference: Clause 7.4.6.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.6.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.6.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.6.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.6.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.6.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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 c6991d698e8c06043668f6497c2d42b70dcea7cc..7432ceebe2cb54c16a4531ad5d7916ac0ac180e5 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] v3.6.1
+ ... Reference: Clause 7.4.7.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.7.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.7.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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 688643ef15386c209467b5e8ba85ae26af75d9a9..7f2da3b2cac8d56f095896ff8d41bad642ee5043 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] v3.6.1
+ ... Reference: Clause 7.4.7.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.7.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.7.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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 7d47f126fc61b422555c5aebb31c2589a8768990..bfee46e5c62923bf6501d3d90e38af1498ecc8b3 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] v3.6.1
+ ... Reference: Clause 7.4.5.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.5.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.5.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.5.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.5.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -291,7 +291,7 @@ POST Create a new Subscription - Unprocessable Entity
... 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.
... re-conditions: none
- ... Reference: Clause 7.4.5.3.1 - ETSI GS NFV-SOL 002 [2] v3.6.1
+ ... Reference: Clause 7.4.5.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL002/VNFFaultManagement-API/environment/variables.txt b/SOL002/VNFFaultManagement-API/environment/variables.txt
index ce47ccabbd7228a50f97614a64fea45890ddef78..7641e281857ab2a1a011c535db87530d3cc3f9b6 100644
--- a/SOL002/VNFFaultManagement-API/environment/variables.txt
+++ b/SOL002/VNFFaultManagement-API/environment/variables.txt
@@ -15,6 +15,8 @@ ${apiName} vnffm
${apiMajorVersion} v1
${CONTENT_TYPE} application/json
+${HEADER_TEST_SUPPORTED} 0
+
${origResponse}= httpresponse
${VNFM_ALLOWS_DUPLICATE_SUBS} 0
diff --git a/SOL002/VNFFaultManagement-API/jsons/EscalatePerceivedSeverity.json b/SOL002/VNFFaultManagement-API/jsons/EscalatePerceivedSeverity.json
new file mode 100644
index 0000000000000000000000000000000000000000..8a8f5a6a878b716450d88607594209b8e364a834
--- /dev/null
+++ b/SOL002/VNFFaultManagement-API/jsons/EscalatePerceivedSeverity.json
@@ -0,0 +1,3 @@
+{{
+ "proposedPerceivedSeverity": "{perceivedSeverity}"
+}}
\ No newline at end of file
diff --git a/SOL002/VNFFaultManagement-API/schemas/FmSubscription.schema.json b/SOL002/VNFFaultManagement-API/schemas/FmSubscription.schema.json
index d691e415c7711efda628223032a7d084eff4dbed..e6fc6b8aeb8ad0696cbd4ce3bf10e001c6d554c4 100644
--- a/SOL002/VNFFaultManagement-API/schemas/FmSubscription.schema.json
+++ b/SOL002/VNFFaultManagement-API/schemas/FmSubscription.schema.json
@@ -1,5 +1,5 @@
{
- "description": "This type represents a subscription related to notifications related to the availability of the virtualised resources quotas.\n",
+ "description": "This type represents a subscription related to notifications about VNF faults.\n",
"type": "object",
"required": [
"id",
@@ -12,29 +12,141 @@
"type": "string"
},
"filter": {
- "description": "This type represents a subscription filter related to notifications about the availability of the virtualised resources quotas. At a particular nesting level in the filter structure, the following applies: All attributes shall match in order for the filter to match (logical \"and\" between different filter attributes). If an attribute is an array, the attribute shall match if at least one of the values in the array matches (logical \"or\" between the values of one filter attribute).\n",
+ "description": "This type represents a subscription filter related to notifications about VNF faults.\nAt a particular nesting level in the filter structure, the following applies: All attributes shall match in order for the filter to match (logical \"and\" between different filter attributes). If an attribute is an array, the attribute shall match if at least one of the values in the array matches (logical \"or\" between the values of one filter attribute).\nNOTE:\tThe permitted values of the \"notificationTypes\" attribute are spelled exactly as the names \n of the notification types to facilitate automated code generation systems.\n",
"type": "object",
"properties": {
- "vimIds": {
- "description": "Match VIMs that were created the quota for a consumer of the virtualised resources. This attribute shall only be supported when VNF-related Resource Management in direct mode is applicable.\n",
- "type": "array",
- "items": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
+ "vnfInstanceSubscriptionFilter": {
+ "description": "This type represents subscription filter criteria to match VNF instances. * NOTE 1:\tThe attributes \"vnfdIds\" and \"vnfProductsFromProviders\" are alternatives to reference to VNF instances\n that are based on certain VNFDs in a filter. They should not be used both in the same filter instance,\n but one alternative should be chosen.\n NOTE 2:\tThe attributes \"vnfInstanceIds\" and \"vnfInstanceNames\" are alternatives to reference to particular VNF\n instances in a filter. They should not be used both in the same filter instance, but one alternative\n should be chosen.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "oneOf": [
+ {
+ "required": [
+ "vnfdId"
+ ]
+ },
+ {
+ "required": [
+ "vnfProductsFromProviders"
+ ]
+ }
+ ]
+ },
+ {
+ "oneOf": [
+ {
+ "required": [
+ "vnfInstanceIds"
+ ]
+ },
+ {
+ "required": [
+ "vnfInstanceNames"
+ ]
+ }
+ ]
+ }
+ ],
+ "properties": {
+ "vnfdIds": {
+ "description": "If present, match VNF instances that were created based on a VNFD identified by one of the vnfdId values listed in this attribute. See note 1.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ },
+ "vnfProductsFromProviders": {
+ "description": "If present, match VNF instances that belong to VNF products from certain providers. See note 1.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": [
+ "vnfProvider"
+ ],
+ "properties": {
+ "vnfProvider": {
+ "description": "Name of the VNF provider to match.\n",
+ "type": "string"
+ },
+ "vnfProducts": {
+ "description": "If present, match VNF instances that belong to VNF products with certain product names, from one particular provider.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": [
+ "vnfProductName"
+ ],
+ "properties": {
+ "vnfProductName": {
+ "description": "Name of the VNF product to match.\n",
+ "type": "string"
+ },
+ "versions": {
+ "description": "If present, match VNF instances that belong to VNF products with certain versions and a certain product name, from one particular provider.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": [
+ "vnfSoftwareVersion"
+ ],
+ "properties": {
+ "vnfSoftwareVersion": {
+ "description": "A version.\n",
+ "type": "string"
+ },
+ "vnfdVersions": {
+ "description": "If present, match VNF instances that belong to VNF products with certain VNFD versions, a certain software version and a certain product name, from one particular provider.\n",
+ "type": "array",
+ "items": {
+ "description": "A version.\n",
+ "type": "string"
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ },
+ "vnfInstanceIds": {
+ "description": "If present, match VNF instances with an instance identifier listed in this attribute. See note 2.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ },
+ "vnfInstanceNames": {
+ "description": "If present, match VNF instances with a VNF Instance Name listed in this attribute. See note 2.\n",
+ "type": "array",
+ "items": {
+ "type": "string"
+ }
+ }
}
},
- "resourceProviderIds": {
- "description": "Match the entities responsible for the management of the virtualised resources that were allocated by the NFVO. This attribute shall only be supported when VNF-related Resource Management in indirect mode is applicable. The identification scheme is outside the scope of the present document.\n",
+ "notificationTypes": {
+ "description": "Match particular notification types. \nPermitted values: -\tAlarmNotification -\tAlarmClearedNotification -\tAlarmListRebuiltNotification See note.\n",
"type": "array",
"items": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
+ "type": "string",
+ "enum": [
+ "AlarmNotification",
+ "AlarmClearedNotification",
+ "AlarmListRebuiltNotification"
+ ]
}
},
- "resourceTypes": {
- "description": "Match particular resource types.\n",
+ "faultyResourceTypes": {
+ "description": "Match VNF alarms with a faulty resource type listed in this attribute.\n",
"type": "array",
"items": {
+ "description": "The enumeration FaultyResourceType represents those types of faulty resource.\n",
"type": "string",
"enum": [
"COMPUTE",
@@ -43,11 +155,41 @@
]
}
},
- "resourceGroupIds": {
- "description": "Match the \"infrastructure resource groups\" that are logical groupings of the virtualised resources assigned to a tenant within an infrastructure Domain.\n",
+ "perceivedSeverities": {
+ "description": "Match VNF alarms with a perceived severity listed in this attribute.\n",
+ "type": "array",
+ "items": {
+ "description": "Indicates the relative level of urgency for operator attention. * CRITICAL: The Critical severity level indicates that a service\n affecting condition has occurred and an immediate corrective action\n is required. Such a severity can be reported, for example, when a\n managed object becomes totally out of service and its capability needs\n to be restored (ITU-T Recommendation X.733).\n* MAJOR: The Major severity level indicates that a service affecting\n condition has developed and an urgent corrective action is required.\n Such a severity can be reported, for example, when there is a severe\n degradation in the capability of the managed object and its full\n capability needs to be restored (ITU-T Recommendation X.733).\n* MINOR: The Minor severity level indicates the existence of a\n non-service affecting fault condition and that corrective action\n should be taken in order to prevent a more serious (for example,\n service affecting) fault. Such a severity can be reported, for\n example, when the detected alarm condition is not currently degrading\n the capacity of the managed object (ITU-T Recommendation X.733).\n* WARNING: The Warning severity level indicates the detection of a\n potential or impending service affecting fault, before any significant\n effects have been felt. Action should be taken to further diagnose (if\n necessary) and correct the problem in order to prevent it from\n becoming a more serious service affecting fault (ITU-T Recommendation\n X.733).\n* INDETERMINATE: The Indeterminate severity level indicates that the\n severity level cannot be determined (ITU-T Recommendation X.733).\n* CLEARED: The Cleared severity level indicates the clearing of one or\n more previously reported alarms. This alarm clears all alarms for this\n managed object that have the same Alarm type, Probable cause and\n Specific problems (if given) (ITU-T Recommendation X.733).\n",
+ "type": "string",
+ "enum": [
+ "CRITICAL",
+ "MAJOR",
+ "MINOR",
+ "WARNING",
+ "INDETERMINATE",
+ "CLEARED"
+ ]
+ }
+ },
+ "eventTypes": {
+ "description": "Match VNF alarms with an event type listed in this attribute.\n",
+ "type": "array",
+ "items": {
+ "description": "The enumeration EventType represents those types of events that trigger an alarm. * COMMUNICATIONS_ALARM: An alarm of this type is associated with the\n procedure and/or process required conveying information from one point\n to another (ITU-T Recommendation X.733).\n* PROCESSING_ERROR_ALARM: An alarm of this type is associated with a\n software or processing fault (ITU-T Recommendation X.733).\n* ENVIRONMENTAL_ALARM: An alarm of this type is associated with a\n condition related to an enclosure in which the equipment resides\n (ITU-T Recommendation X.733).\n* QOS_ALARM: An alarm of this type is associated with degradation in the\n quality of a service (ITU-T Recommendation X.733).\n* EQUIPMENT_ALARM: An alarm of this type is associated with an equipment\n fault (ITU-T Recommendation X.733).\n",
+ "type": "string",
+ "enum": [
+ "COMMUNICATIONS_ALARM",
+ "PROCESSING_ERROR_ALARM",
+ "ENVIRONMENTAL_ALARM",
+ "QOS_ALARM",
+ "EQUIPMENT_ALARM"
+ ]
+ }
+ },
+ "probableCauses": {
+ "description": "Match VNF alarms with a probable cause listed in this attribute.\n",
"type": "array",
"items": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
"type": "string"
}
}
@@ -58,23 +200,22 @@
"type": "string"
},
"_links": {
- "description": "Links for this resource\n",
+ "description": "Links for this resource.\n",
"type": "object",
"required": [
"self"
],
"properties": {
"self": {
- "description": "This type represents a link to a resource.\n",
+ "description": "This type represents a link to a resource using an absolute URI.\n",
"type": "object",
"required": [
"href"
],
"properties": {
"href": {
- "description": "URI of the referenced resource.\n",
- "type": "string",
- "format": "url"
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
}
}
}
diff --git a/SOL002/VNFFaultManagement-API/schemas/FmSubscriptions.schema.json b/SOL002/VNFFaultManagement-API/schemas/FmSubscriptions.schema.json
index 6394f38119da95caa764e09e3af7f34c66d734ba..d61b2a28af75051da15e4f9ac5bda6ab5c071675 100644
--- a/SOL002/VNFFaultManagement-API/schemas/FmSubscriptions.schema.json
+++ b/SOL002/VNFFaultManagement-API/schemas/FmSubscriptions.schema.json
@@ -1,7 +1,7 @@
{
"type": "array",
- "items": {
- "description": "This type represents a subscription related to notifications related to the availability of the virtualised resources quotas.\n",
+ "items": {
+ "description": "This type represents a subscription related to notifications about VNF faults.\n",
"type": "object",
"required": [
"id",
@@ -14,29 +14,141 @@
"type": "string"
},
"filter": {
- "description": "This type represents a subscription filter related to notifications about the availability of the virtualised resources quotas. At a particular nesting level in the filter structure, the following applies: All attributes shall match in order for the filter to match (logical \"and\" between different filter attributes). If an attribute is an array, the attribute shall match if at least one of the values in the array matches (logical \"or\" between the values of one filter attribute).\n",
+ "description": "This type represents a subscription filter related to notifications about VNF faults.\nAt a particular nesting level in the filter structure, the following applies: All attributes shall match in order for the filter to match (logical \"and\" between different filter attributes). If an attribute is an array, the attribute shall match if at least one of the values in the array matches (logical \"or\" between the values of one filter attribute).\nNOTE:\tThe permitted values of the \"notificationTypes\" attribute are spelled exactly as the names \n of the notification types to facilitate automated code generation systems.\n",
"type": "object",
"properties": {
- "vimIds": {
- "description": "Match VIMs that were created the quota for a consumer of the virtualised resources. This attribute shall only be supported when VNF-related Resource Management in direct mode is applicable.\n",
- "type": "array",
- "items": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
+ "vnfInstanceSubscriptionFilter": {
+ "description": "This type represents subscription filter criteria to match VNF instances. * NOTE 1:\tThe attributes \"vnfdIds\" and \"vnfProductsFromProviders\" are alternatives to reference to VNF instances\n that are based on certain VNFDs in a filter. They should not be used both in the same filter instance,\n but one alternative should be chosen.\n NOTE 2:\tThe attributes \"vnfInstanceIds\" and \"vnfInstanceNames\" are alternatives to reference to particular VNF\n instances in a filter. They should not be used both in the same filter instance, but one alternative\n should be chosen.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "oneOf": [
+ {
+ "required": [
+ "vnfdId"
+ ]
+ },
+ {
+ "required": [
+ "vnfProductsFromProviders"
+ ]
+ }
+ ]
+ },
+ {
+ "oneOf": [
+ {
+ "required": [
+ "vnfInstanceIds"
+ ]
+ },
+ {
+ "required": [
+ "vnfInstanceNames"
+ ]
+ }
+ ]
+ }
+ ],
+ "properties": {
+ "vnfdIds": {
+ "description": "If present, match VNF instances that were created based on a VNFD identified by one of the vnfdId values listed in this attribute. See note 1.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ },
+ "vnfProductsFromProviders": {
+ "description": "If present, match VNF instances that belong to VNF products from certain providers. See note 1.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": [
+ "vnfProvider"
+ ],
+ "properties": {
+ "vnfProvider": {
+ "description": "Name of the VNF provider to match.\n",
+ "type": "string"
+ },
+ "vnfProducts": {
+ "description": "If present, match VNF instances that belong to VNF products with certain product names, from one particular provider.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": [
+ "vnfProductName"
+ ],
+ "properties": {
+ "vnfProductName": {
+ "description": "Name of the VNF product to match.\n",
+ "type": "string"
+ },
+ "versions": {
+ "description": "If present, match VNF instances that belong to VNF products with certain versions and a certain product name, from one particular provider.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": [
+ "vnfSoftwareVersion"
+ ],
+ "properties": {
+ "vnfSoftwareVersion": {
+ "description": "A version.\n",
+ "type": "string"
+ },
+ "vnfdVersions": {
+ "description": "If present, match VNF instances that belong to VNF products with certain VNFD versions, a certain software version and a certain product name, from one particular provider.\n",
+ "type": "array",
+ "items": {
+ "description": "A version.\n",
+ "type": "string"
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ },
+ "vnfInstanceIds": {
+ "description": "If present, match VNF instances with an instance identifier listed in this attribute. See note 2.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ },
+ "vnfInstanceNames": {
+ "description": "If present, match VNF instances with a VNF Instance Name listed in this attribute. See note 2.\n",
+ "type": "array",
+ "items": {
+ "type": "string"
+ }
+ }
}
},
- "resourceProviderIds": {
- "description": "Match the entities responsible for the management of the virtualised resources that were allocated by the NFVO. This attribute shall only be supported when VNF-related Resource Management in indirect mode is applicable. The identification scheme is outside the scope of the present document.\n",
+ "notificationTypes": {
+ "description": "Match particular notification types. \nPermitted values: -\tAlarmNotification -\tAlarmClearedNotification -\tAlarmListRebuiltNotification See note.\n",
"type": "array",
"items": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
+ "type": "string",
+ "enum": [
+ "AlarmNotification",
+ "AlarmClearedNotification",
+ "AlarmListRebuiltNotification"
+ ]
}
},
- "resourceTypes": {
- "description": "Match particular resource types.\n",
+ "faultyResourceTypes": {
+ "description": "Match VNF alarms with a faulty resource type listed in this attribute.\n",
"type": "array",
"items": {
+ "description": "The enumeration FaultyResourceType represents those types of faulty resource.\n",
"type": "string",
"enum": [
"COMPUTE",
@@ -45,11 +157,41 @@
]
}
},
- "resourceGroupIds": {
- "description": "Match the \"infrastructure resource groups\" that are logical groupings of the virtualised resources assigned to a tenant within an infrastructure Domain.\n",
+ "perceivedSeverities": {
+ "description": "Match VNF alarms with a perceived severity listed in this attribute.\n",
+ "type": "array",
+ "items": {
+ "description": "Indicates the relative level of urgency for operator attention. * CRITICAL: The Critical severity level indicates that a service\n affecting condition has occurred and an immediate corrective action\n is required. Such a severity can be reported, for example, when a\n managed object becomes totally out of service and its capability needs\n to be restored (ITU-T Recommendation X.733).\n* MAJOR: The Major severity level indicates that a service affecting\n condition has developed and an urgent corrective action is required.\n Such a severity can be reported, for example, when there is a severe\n degradation in the capability of the managed object and its full\n capability needs to be restored (ITU-T Recommendation X.733).\n* MINOR: The Minor severity level indicates the existence of a\n non-service affecting fault condition and that corrective action\n should be taken in order to prevent a more serious (for example,\n service affecting) fault. Such a severity can be reported, for\n example, when the detected alarm condition is not currently degrading\n the capacity of the managed object (ITU-T Recommendation X.733).\n* WARNING: The Warning severity level indicates the detection of a\n potential or impending service affecting fault, before any significant\n effects have been felt. Action should be taken to further diagnose (if\n necessary) and correct the problem in order to prevent it from\n becoming a more serious service affecting fault (ITU-T Recommendation\n X.733).\n* INDETERMINATE: The Indeterminate severity level indicates that the\n severity level cannot be determined (ITU-T Recommendation X.733).\n* CLEARED: The Cleared severity level indicates the clearing of one or\n more previously reported alarms. This alarm clears all alarms for this\n managed object that have the same Alarm type, Probable cause and\n Specific problems (if given) (ITU-T Recommendation X.733).\n",
+ "type": "string",
+ "enum": [
+ "CRITICAL",
+ "MAJOR",
+ "MINOR",
+ "WARNING",
+ "INDETERMINATE",
+ "CLEARED"
+ ]
+ }
+ },
+ "eventTypes": {
+ "description": "Match VNF alarms with an event type listed in this attribute.\n",
+ "type": "array",
+ "items": {
+ "description": "The enumeration EventType represents those types of events that trigger an alarm. * COMMUNICATIONS_ALARM: An alarm of this type is associated with the\n procedure and/or process required conveying information from one point\n to another (ITU-T Recommendation X.733).\n* PROCESSING_ERROR_ALARM: An alarm of this type is associated with a\n software or processing fault (ITU-T Recommendation X.733).\n* ENVIRONMENTAL_ALARM: An alarm of this type is associated with a\n condition related to an enclosure in which the equipment resides\n (ITU-T Recommendation X.733).\n* QOS_ALARM: An alarm of this type is associated with degradation in the\n quality of a service (ITU-T Recommendation X.733).\n* EQUIPMENT_ALARM: An alarm of this type is associated with an equipment\n fault (ITU-T Recommendation X.733).\n",
+ "type": "string",
+ "enum": [
+ "COMMUNICATIONS_ALARM",
+ "PROCESSING_ERROR_ALARM",
+ "ENVIRONMENTAL_ALARM",
+ "QOS_ALARM",
+ "EQUIPMENT_ALARM"
+ ]
+ }
+ },
+ "probableCauses": {
+ "description": "Match VNF alarms with a probable cause listed in this attribute.\n",
"type": "array",
"items": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
"type": "string"
}
}
@@ -60,23 +202,22 @@
"type": "string"
},
"_links": {
- "description": "Links for this resource\n",
+ "description": "Links for this resource.\n",
"type": "object",
"required": [
"self"
],
"properties": {
"self": {
- "description": "This type represents a link to a resource.\n",
+ "description": "This type represents a link to a resource using an absolute URI.\n",
"type": "object",
"required": [
"href"
],
"properties": {
"href": {
- "description": "URI of the referenced resource.\n",
- "type": "string",
- "format": "url"
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
}
}
}
diff --git a/SOL002/VNFFaultManagement-API/schemas/alarm.schema.json b/SOL002/VNFFaultManagement-API/schemas/alarm.schema.json
index 49166a3b78a7485ecff32da358d292bb85549d28..44aea28bc11d24f4469aec51e873290023462883 100644
--- a/SOL002/VNFFaultManagement-API/schemas/alarm.schema.json
+++ b/SOL002/VNFFaultManagement-API/schemas/alarm.schema.json
@@ -1,5 +1,5 @@
{
- "description": "The alarm data type encapsulates information about an alarm. It shall comply with the provisions defined in table 7.5.2.4-1.\nIf the attribute \"faultType\" has the value \"NFVI_OAM_VIRTUALISED_RESOURCE_STATE_CHANGE\", the following provisions apply for the values of the attribute \"faultDetails\" related to changes in the state of virtualised resources:\n - One of the entries in the array shall provide information about the anticipated time of maintenance in the\n following format: \"anticipatedTime=$time\", wherein \"$time\" shall be formatted as a \"DateTime\", as specified\n in ETSI GS NFV-SOL 013 [6].\n - One of the entries in the array shall provide identification information about the affinity/anti-affinity group\n defined in the VNFD that is associated to the affected virtualised resource indicated by \"rootCauseFaultyResource\" \n in the following format: \"affinityOrAntiAffinityGroupId=$group\", wherein \"$group\" shall be equal to the \n \"affinityOrAntiAffinityGroupId\" value in the corresponding \"VduProfile\" (for a VNFC/COMPUTE affected resource) \n or \"VirtualLinkProfile\" for a VL/NETWORK affected resource) in the VNFD, which is mapped by the VNFM to the \n virtualised resource group identifier in the virtualised resource change notification received by the VNFM from \n the VIM.\n\nNOTE 1: For an alarm about upcoming impact due to NFVI operation and maintenance (i.e. the attribute \"faultType\" \n has the value \"NFVI_OAM_VIRTUALISED_RESOURCE_STATE_CHANGE\"), the attribute \"rootCauseFaultyResource\" \n indicates a resource to be impacted. Further information on the upcoming impact (e.g. group of impacted \n resources, time of impact) is provided in the attribute \"faultDetails\".\nNOTE 2: When alarms are due to upcoming NFVI operation and maintenance (i.e. the attribute \"faultType\" has the\n value \"NFVI_OAM_VIRTUALISED_RESOURCE_STATE_CHANGE\"), the attribute \"faultDetails\" shall include information \n about the anticipated time of the maintenance. See provisions under the present table.\n",
+ "description": "The alarm data type encapsulates information about an alarm.\nIf the attribute \"faultType\" has the value \"NFVI_OAM_VIRTUALISED_RESOURCE_STATE_CHANGE\", the following provisions apply for the values of the attribute \"faultDetails\" related to changes in the state of virtualised resources:\n - One of the entries in the array shall provide information about the anticipated time of maintenance in the\n following format: \"anticipatedTime=$time\", wherein \"$time\" shall be formatted as a \"DateTime\", as specified\n in ETSI GS NFV-SOL 013 [6].\n - One of the entries in the array shall provide identification information about the affinity/anti-affinity group\n defined in the VNFD that is associated to the affected virtualised resource indicated by \"rootCauseFaultyResource\" \n in the following format: \"affinityOrAntiAffinityGroupId=$group\", wherein \"$group\" shall be equal to the \n \"affinityOrAntiAffinityGroupId\" value in the corresponding \"VduProfile\" (for a VNFC/COMPUTE affected resource) \n or \"VirtualLinkProfile\" for a VL/NETWORK affected resource) in the VNFD, which is mapped by the VNFM to the \n virtualised resource group identifier in the virtualised resource change notification received by the VNFM from \n the VIM.\n\nNOTE 1: For an alarm about upcoming impact due to NFVI operation and maintenance (i.e. the attribute \"faultType\" \n has the value \"NFVI_OAM_VIRTUALISED_RESOURCE_STATE_CHANGE\"), the attribute \"rootCauseFaultyResource\" \n indicates a resource to be impacted. Further information on the upcoming impact (e.g. group of impacted \n resources, time of impact) is provided in the attribute \"faultDetails\".\nNOTE 2: When alarms are due to upcoming NFVI operation and maintenance (i.e. the attribute \"faultType\" has the\n value \"NFVI_OAM_VIRTUALISED_RESOURCE_STATE_CHANGE\"), the attribute \"faultDetails\" shall include information \n about the anticipated time of the maintenance. See provisions under the present table.\n",
"type": "object",
"required": [
"id",
@@ -43,7 +43,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",
+ "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",
"properties": {
"vimConnectionId": {
"description": "An identifier with the intention of being globally unique.\n",
@@ -54,11 +54,33 @@
"type": "string"
},
"resourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
"type": "string"
},
"vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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"
}
}
@@ -135,7 +157,7 @@
"type": "string"
},
"probableCause": {
- "description": "Information about the probable cause of the fault. If the attribute \"faultType\" has the value “NFVI_OAM_VIRTUALISED_RESOURCE_STATE_CHANGEâ€, the permitted values are: \n - \"NFVI_COMPONENT_MAINTENANCE\": Maintenance of NFVI components, e.g. physical maintenance/repair, \n hypervisor software updates, etc.\n - \"NFVI_COMPONENT_EVACUATION\": Evacuation of physical hosts.\n - \"NFVI_COMPONENT_OPTIMIZATION\": Operation and management of NFVI resources, e.g. to support energy\n efficiency or resource usage optimization.\n",
+ "description": "Information about the probable cause of the fault. If the attribute \"faultType\" has the value ΓÇ£NFVI_OAM_VIRTUALISED_RESOURCE_STATE_CHANGEΓÇ¥, the permitted values are: \n - \"NFVI_COMPONENT_MAINTENANCE\": Maintenance of NFVI components, e.g. physical maintenance/repair, \n hypervisor software updates, etc.\n - \"NFVI_COMPONENT_EVACUATION\": Evacuation of physical hosts.\n - \"NFVI_COMPONENT_OPTIMIZATION\": Operation and management of NFVI resources, e.g. to support energy\n efficiency or resource usage optimization.\n",
"type": "string"
},
"isRootCause": {
diff --git a/SOL002/VNFFaultManagement-API/schemas/alarmClearedNotification.schema.json b/SOL002/VNFFaultManagement-API/schemas/alarmClearedNotification.schema.json
index 08131723d82361c2b27ba85b4ad5e7bc1077da2f..e71ffd497ad78e067bacb8aa733928d1bb772340 100644
--- a/SOL002/VNFFaultManagement-API/schemas/alarmClearedNotification.schema.json
+++ b/SOL002/VNFFaultManagement-API/schemas/alarmClearedNotification.schema.json
@@ -27,7 +27,7 @@
"type": "string"
},
"timeStamp": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
"type": "string",
"format": "date-time"
},
@@ -36,7 +36,9 @@
"type": "string"
},
"alarmClearedTime": {
- "description": "The time stamp indicating when the alarm was cleared.\n"
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
},
"_links": {
"description": "Links to resources related to this notification.\n",
@@ -47,30 +49,28 @@
],
"properties": {
"subscription": {
- "description": "This type represents a link to a resource.\n",
+ "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 the referenced resource.\n",
- "type": "string",
- "format": "url"
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
}
}
},
"alarm": {
- "description": "This type represents a link to a resource.\n",
+ "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 the referenced resource.\n",
- "type": "string",
- "format": "url"
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
}
}
}
diff --git a/SOL002/VNFFaultManagement-API/schemas/alarmListRebuiltNotification.schema.json b/SOL002/VNFFaultManagement-API/schemas/alarmListRebuiltNotification.schema.json
index bfe018df8f3dec0fc2526d02254fa13486ea68b9..d13d292b86f9afd2022d0f274f291e8a292912fc 100644
--- a/SOL002/VNFFaultManagement-API/schemas/alarmListRebuiltNotification.schema.json
+++ b/SOL002/VNFFaultManagement-API/schemas/alarmListRebuiltNotification.schema.json
@@ -1,5 +1,5 @@
{
- "description": "This type represents a notification that the alarm list has been rebuilt, e.g. if the VNFM detects its storage holding the alarm list is corrupted. The notification shall be triggered by the VNFM when the alarm list has been rebuilt.\n",
+ "description": "This type represents a notification that the alarm list has been rebuilt, e.g. if the VNFM detects its storage holding the alarm list is corrupted. The notification shall be triggered by the VNFM when the alarm list has been rebuilt, e.g. because the VNFM has detected that its storage holding the alarm list was corrupted.\n",
"type": "object",
"required": [
"id",
@@ -25,7 +25,7 @@
"type": "string"
},
"timeStamp": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
"type": "string",
"format": "date-time"
},
@@ -38,30 +38,28 @@
],
"properties": {
"subscription": {
- "description": "This type represents a link to a resource.\n",
+ "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 the referenced resource.\n",
- "type": "string",
- "format": "url"
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
}
}
},
"alarms": {
- "description": "This type represents a link to a resource.\n",
+ "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 the referenced resource.\n",
- "type": "string",
- "format": "url"
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
}
}
}
diff --git a/SOL002/VNFFaultManagement-API/schemas/alarmModifications.schema.json b/SOL002/VNFFaultManagement-API/schemas/alarmModifications.schema.json
index 460ad06565d3e2bd8ee356b8448f14202150b7cf..4e98ff4de27d165e11d2212645f6eccb052d6277 100644
--- a/SOL002/VNFFaultManagement-API/schemas/alarmModifications.schema.json
+++ b/SOL002/VNFFaultManagement-API/schemas/alarmModifications.schema.json
@@ -6,10 +6,11 @@
],
"properties": {
"ackState": {
- "description": "New value of the \"ackState\" attribute in \"Alarm\". Permitted values: * ACKNOWLEDGED\n",
+ "description": "New value of the \"ackState\" attribute in \"Alarm\". Permitted values: * ACKNOWLEDGED * UNACKNOWLEDGED\n",
"type": "string",
"enum": [
- "ACKNOWLEDGED"
+ "ACKNOWLEDGED",
+ "UNACKNOWLEDGED"
]
}
}
diff --git a/SOL002/VNFFaultManagement-API/schemas/alarmNotification.schema.json b/SOL002/VNFFaultManagement-API/schemas/alarmNotification.schema.json
index bca2fc85657c28c9914c131ea0abf5ea8bd997b6..aba8ecf662d0995545d70cddccd165761f8e2ad4 100644
--- a/SOL002/VNFFaultManagement-API/schemas/alarmNotification.schema.json
+++ b/SOL002/VNFFaultManagement-API/schemas/alarmNotification.schema.json
@@ -1,244 +1,274 @@
{
- "description": "This type represents an alarm notification about VNF faults. This notification shall be triggered by the VNFM when: * An alarm has been created. * An alarm has been updated, e.g. if the severity of the alarm has changed.\n",
- "type": "object",
- "required": [
- "id",
- "notificationType",
- "subscriptionId",
- "timeStamp",
- "alarm",
- "_links"
- ],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "notificationType": {
- "description": "Discriminator for the different notification types. Shall be set to \"AlarmNotification\" for this notification type.\n",
- "type": "string",
- "enum": [
- "AlarmNotification"
- ]
- },
- "subscriptionId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "timeStamp": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "alarm": {
- "description": "The alarm data type encapsulates information about an alarm.\n",
- "type": "object",
- "required": [
- "id",
- "managedObjectId",
- "rootCauseFaultyResource",
- "alarmRaisedTime",
- "ackState",
- "perceivedSeverity",
- "eventTime",
- "eventType",
- "probableCause",
- "isRootCause",
- "_links"
- ],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "managedObjectId": {
- "description": "An identifier with the intention of being globally unique.\n",
+ "description": "This type represents an alarm notification about VNF faults. This notification shall be triggered by the VNFM when: * An alarm has been created. * An alarm has been updated, e.g. if the severity of the alarm has\n changed.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "notificationType",
+ "subscriptionId",
+ "timeStamp",
+ "alarm",
+ "_links"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "notificationType": {
+ "description": "Discriminator for the different notification types. Shall be set to \"AlarmNotification\" for this notification type.\n",
+ "type": "string",
+ "enum": [
+ "AlarmNotification"
+ ]
+ },
+ "subscriptionId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "timeStamp": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "alarm": {
+ "description": "The alarm data type encapsulates information about an alarm.\nIf the attribute \"faultType\" has the value \"NFVI_OAM_VIRTUALISED_RESOURCE_STATE_CHANGE\", the following provisions apply for the values of the attribute \"faultDetails\" related to changes in the state of virtualised resources:\n - One of the entries in the array shall provide information about the anticipated time of maintenance in the\n following format: \"anticipatedTime=$time\", wherein \"$time\" shall be formatted as a \"DateTime\", as specified\n in ETSI GS NFV-SOL 013 [6].\n - One of the entries in the array shall provide identification information about the affinity/anti-affinity group\n defined in the VNFD that is associated to the affected virtualised resource indicated by \"rootCauseFaultyResource\" \n in the following format: \"affinityOrAntiAffinityGroupId=$group\", wherein \"$group\" shall be equal to the \n \"affinityOrAntiAffinityGroupId\" value in the corresponding \"VduProfile\" (for a VNFC/COMPUTE affected resource) \n or \"VirtualLinkProfile\" for a VL/NETWORK affected resource) in the VNFD, which is mapped by the VNFM to the \n virtualised resource group identifier in the virtualised resource change notification received by the VNFM from \n the VIM.\n\nNOTE 1: For an alarm about upcoming impact due to NFVI operation and maintenance (i.e. the attribute \"faultType\" \n has the value \"NFVI_OAM_VIRTUALISED_RESOURCE_STATE_CHANGE\"), the attribute \"rootCauseFaultyResource\" \n indicates a resource to be impacted. Further information on the upcoming impact (e.g. group of impacted \n resources, time of impact) is provided in the attribute \"faultDetails\".\nNOTE 2: When alarms are due to upcoming NFVI operation and maintenance (i.e. the attribute \"faultType\" has the\n value \"NFVI_OAM_VIRTUALISED_RESOURCE_STATE_CHANGE\"), the attribute \"faultDetails\" shall include information \n about the anticipated time of the maintenance. See provisions under the present table.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "managedObjectId",
+ "alarmRaisedTime",
+ "ackState",
+ "perceivedSeverity",
+ "eventTime",
+ "eventType",
+ "probableCause",
+ "isRootCause",
+ "_links"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "managedObjectId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfcInstanceIds": {
+ "description": "Identifiers of the affected VNFC instances. Each identifier references the \"id\" attribute in a \"VnfcInfo\" structure. Shall be present if the alarm affects at least one VNFC instance.\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"
- },
- "rootCauseFaultyResource": {
- "description": "This type represents the faulty virtual resources that have a negative impact on a VNF.\n",
- "type": "object",
- "required": [
- "faultyResource",
- "faultyResourceType"
- ],
- "properties": {
- "faultyResource": {
- "required": [
- "vimConnectionId",
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Type of the resource in the scope of the VIM or the resource provider.\n",
- "type": "string"
+ }
+ },
+ "rootCauseFaultyResource": {
+ "description": "This type represents the faulty virtual resources that have a negative impact on a VNF.\n",
+ "type": "object",
+ "required": [
+ "faultyResource",
+ "faultyResourceType"
+ ],
+ "properties": {
+ "faultyResource": {
+ "required": [
+ "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",
+ "properties": {
+ "vimConnectionId": {
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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 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"
+ }
}
+ },
+ "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"
}
- },
- "faultyResourceType": {
- "description": "The enumeration FaultyResourceType represents those types of faulty resource.\n",
- "type": "string",
- "enum": [
- "COMPUTE",
- "STORAGE",
- "NETWORK"
- ]
}
+ },
+ "faultyResourceType": {
+ "description": "The enumeration FaultyResourceType represents those types of faulty resource.\n",
+ "type": "string",
+ "enum": [
+ "COMPUTE",
+ "STORAGE",
+ "NETWORK"
+ ]
}
- },
- "alarmRaisedTime": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "alarmChangedTime": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "alarmClearedTime": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "ackState": {
- "description": "Acknowledgement state of the alarm. Permitted values: * UNACKNOWLEDGED * ACKNOWLEDGED.\n",
- "type": "string",
- "enum": [
- "UNACKNOWLEDGED",
- "ACKNOWLEDGED"
- ]
- },
- "perceivedSeverity": {
- "description": "Indicates the relative level of urgency for operator attention. * CRITICAL: The Critical severity level indicates that a service affecting condition has occurred and an immediate corrective action\n is required. Such a severity can be reported, for example, when a\n managed object becomes totally out of service and its capability needs\n to be restored (ITU-T Recommendation X.733).\n* MAJOR: The Major severity level indicates that a service affecting condition has developed and an urgent corrective action is required.\n Such a severity can be reported, for example, when there is a severe\n degradation in the capability of the managed object and its full\n capability needs to be restored (ITU-T Recommendation X.733).\n* MINOR: The Minor severity level indicates the existence of a non-service affecting fault condition and that corrective action\n should be taken in order to prevent a more serious (for example,\n service affecting) fault. Such a severity can be reported, for\n example, when the detected alarm condition is not currently degrading\n the capacity of the managed object (ITU-T Recommendation X.733).\n* WARNING: The Warning severity level indicates the detection of a potential or impending service affecting fault, before any significant\n effects have been felt. Action should be taken to further diagnose (if\n necessary) and correct the problem in order to prevent it from\n becoming a more serious service affecting fault (ITU-T Recommendation\n X.733).\n* INDETERMINATE: The Indeterminate severity level indicates that the severity level cannot be determined (ITU-T Recommendation X.733).\n* CLEARED: The Cleared severity level indicates the clearing of one or more previously reported alarms. This alarm clears all alarms for this\n managed object that have the same Alarm type, Probable cause and\n Specific problems (if given) (ITU-T Recommendation X.733).\n",
- "type": "string",
- "enum": [
- "CRITICAL",
- "MAJOR",
- "MINOR",
- "WARNING",
- "INDETERMINATE",
- "CLEARED"
- ]
- },
- "eventTime": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "eventType": {
- "description": "The enumeration EventType represents those types of events that trigger an alarm. * COMMUNICATIONS_ALARM: An alarm of this type is associated with the procedure and/or process required conveying information from one point\n to another (ITU-T Recommendation X.733).\n* PROCESSING_ERROR_ALARM: An alarm of this type is associated with a software or processing fault (ITU-T Recommendation X.733).\n* ENVIRONMENTAL_ALARM: An alarm of this type is associated with a condition related to an enclosure in which the equipment resides\n (ITU-T Recommendation X.733).\n* QOS_ALARM: An alarm of this type is associated with degradation in the quality of a service (ITU-T Recommendation X.733).\n* EQUIPMENT_ALARM: An alarm of this type is associated with an equipment fault (ITU-T Recommendation X.733).\n",
- "type": "string",
- "enum": [
- "COMMUNICATIONS_ALARM",
- "PROCESSING_ERROR_ALARM",
- "ENVIRONMENTAL_ALARM",
- "QOS_ALARM",
- "EQUIPMENT_ALARM"
- ]
- },
- "faultType": {
- "description": "Additional information to clarify the type of the fault.\n",
+ }
+ },
+ "alarmRaisedTime": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "alarmChangedTime": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "alarmClearedTime": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "alarmAcknowledgedTime": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "ackState": {
+ "description": "Acknowledgement state of the alarm. Permitted values: * UNACKNOWLEDGED * ACKNOWLEDGED.\n",
+ "type": "string",
+ "enum": [
+ "UNACKNOWLEDGED",
+ "ACKNOWLEDGED"
+ ]
+ },
+ "perceivedSeverity": {
+ "description": "Indicates the relative level of urgency for operator attention. * CRITICAL: The Critical severity level indicates that a service\n affecting condition has occurred and an immediate corrective action\n is required. Such a severity can be reported, for example, when a\n managed object becomes totally out of service and its capability needs\n to be restored (ITU-T Recommendation X.733).\n* MAJOR: The Major severity level indicates that a service affecting\n condition has developed and an urgent corrective action is required.\n Such a severity can be reported, for example, when there is a severe\n degradation in the capability of the managed object and its full\n capability needs to be restored (ITU-T Recommendation X.733).\n* MINOR: The Minor severity level indicates the existence of a\n non-service affecting fault condition and that corrective action\n should be taken in order to prevent a more serious (for example,\n service affecting) fault. Such a severity can be reported, for\n example, when the detected alarm condition is not currently degrading\n the capacity of the managed object (ITU-T Recommendation X.733).\n* WARNING: The Warning severity level indicates the detection of a\n potential or impending service affecting fault, before any significant\n effects have been felt. Action should be taken to further diagnose (if\n necessary) and correct the problem in order to prevent it from\n becoming a more serious service affecting fault (ITU-T Recommendation\n X.733).\n* INDETERMINATE: The Indeterminate severity level indicates that the\n severity level cannot be determined (ITU-T Recommendation X.733).\n* CLEARED: The Cleared severity level indicates the clearing of one or\n more previously reported alarms. This alarm clears all alarms for this\n managed object that have the same Alarm type, Probable cause and\n Specific problems (if given) (ITU-T Recommendation X.733).\n",
+ "type": "string",
+ "enum": [
+ "CRITICAL",
+ "MAJOR",
+ "MINOR",
+ "WARNING",
+ "INDETERMINATE",
+ "CLEARED"
+ ]
+ },
+ "eventTime": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "eventType": {
+ "description": "The enumeration EventType represents those types of events that trigger an alarm. * COMMUNICATIONS_ALARM: An alarm of this type is associated with the\n procedure and/or process required conveying information from one point\n to another (ITU-T Recommendation X.733).\n* PROCESSING_ERROR_ALARM: An alarm of this type is associated with a\n software or processing fault (ITU-T Recommendation X.733).\n* ENVIRONMENTAL_ALARM: An alarm of this type is associated with a\n condition related to an enclosure in which the equipment resides\n (ITU-T Recommendation X.733).\n* QOS_ALARM: An alarm of this type is associated with degradation in the\n quality of a service (ITU-T Recommendation X.733).\n* EQUIPMENT_ALARM: An alarm of this type is associated with an equipment\n fault (ITU-T Recommendation X.733).\n",
+ "type": "string",
+ "enum": [
+ "COMMUNICATIONS_ALARM",
+ "PROCESSING_ERROR_ALARM",
+ "ENVIRONMENTAL_ALARM",
+ "QOS_ALARM",
+ "EQUIPMENT_ALARM"
+ ]
+ },
+ "faultType": {
+ "description": "Additional information to clarify the type of the fault. If the alarm is related to changes in the state of virtualised resources due to NFVI operation and maintenance, this attribute shall be set to \"NFVI_OAM_VIRTUALISED_RESOURCE_STATE _CHANGE\".\n",
+ "type": "string"
+ },
+ "probableCause": {
+ "description": "Information about the probable cause of the fault. If the attribute \"faultType\" has the value ΓÇ£NFVI_OAM_VIRTUALISED_RESOURCE_STATE_CHANGEΓÇ¥, the permitted values are: \n - \"NFVI_COMPONENT_MAINTENANCE\": Maintenance of NFVI components, e.g. physical maintenance/repair, \n hypervisor software updates, etc.\n - \"NFVI_COMPONENT_EVACUATION\": Evacuation of physical hosts.\n - \"NFVI_COMPONENT_OPTIMIZATION\": Operation and management of NFVI resources, e.g. to support energy\n efficiency or resource usage optimization.\n",
+ "type": "string"
+ },
+ "isRootCause": {
+ "description": "The Boolean is a data type having two values (true and false).\n",
+ "type": "boolean"
+ },
+ "correlatedAlarmIds": {
+ "description": "List of identifiers of other alarms correlated to this fault.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
"type": "string"
- },
- "probableCause": {
- "description": "Information about the probable cause of the fault.\n",
+ }
+ },
+ "faultDetails": {
+ "description": "Provides additional information about the fault. See notes 1 and 2.\n",
+ "type": "array",
+ "items": {
"type": "string"
- },
- "isRootCause": {
- "description": "Attribute indicating if this fault is the root for other correlated alarms. If TRUE, then the alarms listed in the attribute CorrelatedAlarmId are caused by this fault.\n",
- "type": "boolean"
- },
- "correlatedAlarmIds": {
- "description": "List of identifiers of other alarms correlated to this fault.\n",
- "type": "array",
- "items": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- }
- },
- "faultDetails": {
- "description": "Provides additional information about the fault.\n",
- "type": "array",
- "items": {
- "type": "string"
- }
- },
- "_links": {
- "description": "Links for 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 the referenced resource.\n",
- "type": "string",
- "format": "url"
- }
+ }
+ },
+ "_links": {
+ "description": "Links for this resource.\n",
+ "type": "object",
+ "required": [
+ "self"
+ ],
+ "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"
}
- },
- "objectInstance": {
- "description": "This type represents a link to a resource.\n",
- "type": "object",
- "required": [
- "href"
- ],
- "properties": {
- "href": {
- "description": "URI of the referenced resource.\n",
- "type": "string",
- "format": "url"
- }
+ }
+ },
+ "objectInstance": {
+ "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"
}
}
}
}
}
- },
- "_links": {
- "description": "Links to resources related to this notification.\n",
- "type": "object",
- "required": [
- "subscription"
- ],
- "properties": {
- "subscription": {
- "description": "This type represents a link to a resource.\n",
- "type": "object",
- "required": [
- "href"
- ],
- "properties": {
- "href": {
- "description": "URI of the referenced resource.\n",
- "type": "string",
- "format": "url"
- }
+ }
+ },
+ "_links": {
+ "description": "Links to resources related to this notification.\n",
+ "type": "object",
+ "required": [
+ "subscription"
+ ],
+ "properties": {
+ "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": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
}
}
}
}
}
- }
\ No newline at end of file
+ }
+}
\ No newline at end of file
diff --git a/SOL002/VNFFaultManagement-API/schemas/alarms.schema.json b/SOL002/VNFFaultManagement-API/schemas/alarms.schema.json
index 8eb6bf5974421f6ca0e3de398a69d8228d9d9727..632fefd6a84f13f0d8cc7a38c8ad836d8a045100 100644
--- a/SOL002/VNFFaultManagement-API/schemas/alarms.schema.json
+++ b/SOL002/VNFFaultManagement-API/schemas/alarms.schema.json
@@ -1,197 +1,216 @@
{
"type": "array",
"items": {
+ "description": "The alarm data type encapsulates information about an alarm.\nIf the attribute \"faultType\" has the value \"NFVI_OAM_VIRTUALISED_RESOURCE_STATE_CHANGE\", the following provisions apply for the values of the attribute \"faultDetails\" related to changes in the state of virtualised resources:\n - One of the entries in the array shall provide information about the anticipated time of maintenance in the\n following format: \"anticipatedTime=$time\", wherein \"$time\" shall be formatted as a \"DateTime\", as specified\n in ETSI GS NFV-SOL 013 [6].\n - One of the entries in the array shall provide identification information about the affinity/anti-affinity group\n defined in the VNFD that is associated to the affected virtualised resource indicated by \"rootCauseFaultyResource\" \n in the following format: \"affinityOrAntiAffinityGroupId=$group\", wherein \"$group\" shall be equal to the \n \"affinityOrAntiAffinityGroupId\" value in the corresponding \"VduProfile\" (for a VNFC/COMPUTE affected resource) \n or \"VirtualLinkProfile\" for a VL/NETWORK affected resource) in the VNFD, which is mapped by the VNFM to the \n virtualised resource group identifier in the virtualised resource change notification received by the VNFM from \n the VIM.\n\nNOTE 1: For an alarm about upcoming impact due to NFVI operation and maintenance (i.e. the attribute \"faultType\" \n has the value \"NFVI_OAM_VIRTUALISED_RESOURCE_STATE_CHANGE\"), the attribute \"rootCauseFaultyResource\" \n indicates a resource to be impacted. Further information on the upcoming impact (e.g. group of impacted \n resources, time of impact) is provided in the attribute \"faultDetails\".\nNOTE 2: When alarms are due to upcoming NFVI operation and maintenance (i.e. the attribute \"faultType\" has the\n value \"NFVI_OAM_VIRTUALISED_RESOURCE_STATE_CHANGE\"), the attribute \"faultDetails\" shall include information \n about the anticipated time of the maintenance. See provisions under the present table.\n",
"type": "object",
- "items": {
- "description": "The alarm data type encapsulates information about an alarm. It shall comply with the provisions defined in table 7.5.2.4-1.\nIf the attribute \"faultType\" has the value \"NFVI_OAM_VIRTUALISED_RESOURCE_STATE_CHANGE\", the following provisions apply for the values of the attribute \"faultDetails\" related to changes in the state of virtualised resources:\n - One of the entries in the array shall provide information about the anticipated time of maintenance in the\n following format: \"anticipatedTime=$time\", wherein \"$time\" shall be formatted as a \"DateTime\", as specified\n in ETSI GS NFV-SOL 013 [6].\n - One of the entries in the array shall provide identification information about the affinity/anti-affinity group\n defined in the VNFD that is associated to the affected virtualised resource indicated by \"rootCauseFaultyResource\" \n in the following format: \"affinityOrAntiAffinityGroupId=$group\", wherein \"$group\" shall be equal to the \n \"affinityOrAntiAffinityGroupId\" value in the corresponding \"VduProfile\" (for a VNFC/COMPUTE affected resource) \n or \"VirtualLinkProfile\" for a VL/NETWORK affected resource) in the VNFD, which is mapped by the VNFM to the \n virtualised resource group identifier in the virtualised resource change notification received by the VNFM from \n the VIM.\n\nNOTE 1: For an alarm about upcoming impact due to NFVI operation and maintenance (i.e. the attribute \"faultType\" \n has the value \"NFVI_OAM_VIRTUALISED_RESOURCE_STATE_CHANGE\"), the attribute \"rootCauseFaultyResource\" \n indicates a resource to be impacted. Further information on the upcoming impact (e.g. group of impacted \n resources, time of impact) is provided in the attribute \"faultDetails\".\nNOTE 2: When alarms are due to upcoming NFVI operation and maintenance (i.e. the attribute \"faultType\" has the\n value \"NFVI_OAM_VIRTUALISED_RESOURCE_STATE_CHANGE\"), the attribute \"faultDetails\" shall include information \n about the anticipated time of the maintenance. See provisions under the present table.\n",
- "type": "object",
- "required": [
- "id",
- "managedObjectId",
- "alarmRaisedTime",
- "ackState",
- "perceivedSeverity",
- "eventTime",
- "eventType",
- "probableCause",
- "isRootCause",
- "_links"
- ],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "managedObjectId": {
- "description": "An identifier with the intention of being globally unique.\n",
+ "required": [
+ "id",
+ "managedObjectId",
+ "alarmRaisedTime",
+ "ackState",
+ "perceivedSeverity",
+ "eventTime",
+ "eventType",
+ "probableCause",
+ "isRootCause",
+ "_links"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "managedObjectId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfcInstanceIds": {
+ "description": "Identifiers of the affected VNFC instances. Each identifier references the \"id\" attribute in a \"VnfcInfo\" structure. Shall be present if the alarm affects at least one VNFC instance.\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"
- },
- "vnfcInstanceIds": {
- "description": "Identifiers of the affected VNFC instances. Each identifier references the \"id\" attribute in a \"VnfcInfo\" structure. Shall be present if the alarm affects at least one VNFC instance.\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"
- }
- },
- "rootCauseFaultyResource": {
- "description": "This type represents the faulty virtual resources that have a negative impact on a VNF.\n",
- "type": "object",
- "required": [
- "faultyResource",
- "faultyResourceType"
- ],
- "properties": {
- "faultyResource": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
- "type": "string"
+ }
+ },
+ "rootCauseFaultyResource": {
+ "description": "This type represents the faulty virtual resources that have a negative impact on a VNF.\n",
+ "type": "object",
+ "required": [
+ "faultyResource",
+ "faultyResourceType"
+ ],
+ "properties": {
+ "faultyResource": {
+ "required": [
+ "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",
+ "properties": {
+ "vimConnectionId": {
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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 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"
+ }
}
+ },
+ "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"
}
- },
- "faultyResourceType": {
- "description": "The enumeration FaultyResourceType represents those types of faulty resource.\n",
- "type": "string",
- "enum": [
- "COMPUTE",
- "STORAGE",
- "NETWORK"
- ]
}
+ },
+ "faultyResourceType": {
+ "description": "The enumeration FaultyResourceType represents those types of faulty resource.\n",
+ "type": "string",
+ "enum": [
+ "COMPUTE",
+ "STORAGE",
+ "NETWORK"
+ ]
}
- },
- "alarmRaisedTime": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "alarmChangedTime": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "alarmClearedTime": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "alarmAcknowledgedTime": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "ackState": {
- "description": "Acknowledgement state of the alarm. Permitted values: * UNACKNOWLEDGED * ACKNOWLEDGED.\n",
- "type": "string",
- "enum": [
- "UNACKNOWLEDGED",
- "ACKNOWLEDGED"
- ]
- },
- "perceivedSeverity": {
- "description": "Indicates the relative level of urgency for operator attention. * CRITICAL: The Critical severity level indicates that a service\n affecting condition has occurred and an immediate corrective action\n is required. Such a severity can be reported, for example, when a\n managed object becomes totally out of service and its capability needs\n to be restored (ITU-T Recommendation X.733).\n* MAJOR: The Major severity level indicates that a service affecting\n condition has developed and an urgent corrective action is required.\n Such a severity can be reported, for example, when there is a severe\n degradation in the capability of the managed object and its full\n capability needs to be restored (ITU-T Recommendation X.733).\n* MINOR: The Minor severity level indicates the existence of a\n non-service affecting fault condition and that corrective action\n should be taken in order to prevent a more serious (for example,\n service affecting) fault. Such a severity can be reported, for\n example, when the detected alarm condition is not currently degrading\n the capacity of the managed object (ITU-T Recommendation X.733).\n* WARNING: The Warning severity level indicates the detection of a\n potential or impending service affecting fault, before any significant\n effects have been felt. Action should be taken to further diagnose (if\n necessary) and correct the problem in order to prevent it from\n becoming a more serious service affecting fault (ITU-T Recommendation\n X.733).\n* INDETERMINATE: The Indeterminate severity level indicates that the\n severity level cannot be determined (ITU-T Recommendation X.733).\n* CLEARED: The Cleared severity level indicates the clearing of one or\n more previously reported alarms. This alarm clears all alarms for this\n managed object that have the same Alarm type, Probable cause and\n Specific problems (if given) (ITU-T Recommendation X.733).\n",
- "type": "string",
- "enum": [
- "CRITICAL",
- "MAJOR",
- "MINOR",
- "WARNING",
- "INDETERMINATE",
- "CLEARED"
- ]
- },
- "eventTime": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "eventType": {
- "description": "The enumeration EventType represents those types of events that trigger an alarm. * COMMUNICATIONS_ALARM: An alarm of this type is associated with the\n procedure and/or process required conveying information from one point\n to another (ITU-T Recommendation X.733).\n* PROCESSING_ERROR_ALARM: An alarm of this type is associated with a\n software or processing fault (ITU-T Recommendation X.733).\n* ENVIRONMENTAL_ALARM: An alarm of this type is associated with a\n condition related to an enclosure in which the equipment resides\n (ITU-T Recommendation X.733).\n* QOS_ALARM: An alarm of this type is associated with degradation in the\n quality of a service (ITU-T Recommendation X.733).\n* EQUIPMENT_ALARM: An alarm of this type is associated with an equipment\n fault (ITU-T Recommendation X.733).\n",
- "type": "string",
- "enum": [
- "COMMUNICATIONS_ALARM",
- "PROCESSING_ERROR_ALARM",
- "ENVIRONMENTAL_ALARM",
- "QOS_ALARM",
- "EQUIPMENT_ALARM"
- ]
- },
- "faultType": {
- "description": "Additional information to clarify the type of the fault. If the alarm is related to changes in the state of virtualised resources due to NFVI operation and maintenance, this attribute shall be set to \"NFVI_OAM_VIRTUALISED_RESOURCE_STATE _CHANGE\".\n",
+ }
+ },
+ "alarmRaisedTime": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "alarmChangedTime": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "alarmClearedTime": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "alarmAcknowledgedTime": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "ackState": {
+ "description": "Acknowledgement state of the alarm. Permitted values: * UNACKNOWLEDGED * ACKNOWLEDGED.\n",
+ "type": "string",
+ "enum": [
+ "UNACKNOWLEDGED",
+ "ACKNOWLEDGED"
+ ]
+ },
+ "perceivedSeverity": {
+ "description": "Indicates the relative level of urgency for operator attention. * CRITICAL: The Critical severity level indicates that a service\n affecting condition has occurred and an immediate corrective action\n is required. Such a severity can be reported, for example, when a\n managed object becomes totally out of service and its capability needs\n to be restored (ITU-T Recommendation X.733).\n* MAJOR: The Major severity level indicates that a service affecting\n condition has developed and an urgent corrective action is required.\n Such a severity can be reported, for example, when there is a severe\n degradation in the capability of the managed object and its full\n capability needs to be restored (ITU-T Recommendation X.733).\n* MINOR: The Minor severity level indicates the existence of a\n non-service affecting fault condition and that corrective action\n should be taken in order to prevent a more serious (for example,\n service affecting) fault. Such a severity can be reported, for\n example, when the detected alarm condition is not currently degrading\n the capacity of the managed object (ITU-T Recommendation X.733).\n* WARNING: The Warning severity level indicates the detection of a\n potential or impending service affecting fault, before any significant\n effects have been felt. Action should be taken to further diagnose (if\n necessary) and correct the problem in order to prevent it from\n becoming a more serious service affecting fault (ITU-T Recommendation\n X.733).\n* INDETERMINATE: The Indeterminate severity level indicates that the\n severity level cannot be determined (ITU-T Recommendation X.733).\n* CLEARED: The Cleared severity level indicates the clearing of one or\n more previously reported alarms. This alarm clears all alarms for this\n managed object that have the same Alarm type, Probable cause and\n Specific problems (if given) (ITU-T Recommendation X.733).\n",
+ "type": "string",
+ "enum": [
+ "CRITICAL",
+ "MAJOR",
+ "MINOR",
+ "WARNING",
+ "INDETERMINATE",
+ "CLEARED"
+ ]
+ },
+ "eventTime": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "eventType": {
+ "description": "The enumeration EventType represents those types of events that trigger an alarm. * COMMUNICATIONS_ALARM: An alarm of this type is associated with the\n procedure and/or process required conveying information from one point\n to another (ITU-T Recommendation X.733).\n* PROCESSING_ERROR_ALARM: An alarm of this type is associated with a\n software or processing fault (ITU-T Recommendation X.733).\n* ENVIRONMENTAL_ALARM: An alarm of this type is associated with a\n condition related to an enclosure in which the equipment resides\n (ITU-T Recommendation X.733).\n* QOS_ALARM: An alarm of this type is associated with degradation in the\n quality of a service (ITU-T Recommendation X.733).\n* EQUIPMENT_ALARM: An alarm of this type is associated with an equipment\n fault (ITU-T Recommendation X.733).\n",
+ "type": "string",
+ "enum": [
+ "COMMUNICATIONS_ALARM",
+ "PROCESSING_ERROR_ALARM",
+ "ENVIRONMENTAL_ALARM",
+ "QOS_ALARM",
+ "EQUIPMENT_ALARM"
+ ]
+ },
+ "faultType": {
+ "description": "Additional information to clarify the type of the fault. If the alarm is related to changes in the state of virtualised resources due to NFVI operation and maintenance, this attribute shall be set to \"NFVI_OAM_VIRTUALISED_RESOURCE_STATE _CHANGE\".\n",
+ "type": "string"
+ },
+ "probableCause": {
+ "description": "Information about the probable cause of the fault. If the attribute \"faultType\" has the value ΓÇ£NFVI_OAM_VIRTUALISED_RESOURCE_STATE_CHANGEΓÇ¥, the permitted values are: \n - \"NFVI_COMPONENT_MAINTENANCE\": Maintenance of NFVI components, e.g. physical maintenance/repair, \n hypervisor software updates, etc.\n - \"NFVI_COMPONENT_EVACUATION\": Evacuation of physical hosts.\n - \"NFVI_COMPONENT_OPTIMIZATION\": Operation and management of NFVI resources, e.g. to support energy\n efficiency or resource usage optimization.\n",
+ "type": "string"
+ },
+ "isRootCause": {
+ "description": "The Boolean is a data type having two values (true and false).\n",
+ "type": "boolean"
+ },
+ "correlatedAlarmIds": {
+ "description": "List of identifiers of other alarms correlated to this fault.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
"type": "string"
- },
- "probableCause": {
- "description": "Information about the probable cause of the fault. If the attribute \"faultType\" has the value “NFVI_OAM_VIRTUALISED_RESOURCE_STATE_CHANGEâ€, the permitted values are: \n - \"NFVI_COMPONENT_MAINTENANCE\": Maintenance of NFVI components, e.g. physical maintenance/repair, \n hypervisor software updates, etc.\n - \"NFVI_COMPONENT_EVACUATION\": Evacuation of physical hosts.\n - \"NFVI_COMPONENT_OPTIMIZATION\": Operation and management of NFVI resources, e.g. to support energy\n efficiency or resource usage optimization.\n",
+ }
+ },
+ "faultDetails": {
+ "description": "Provides additional information about the fault. See notes 1 and 2.\n",
+ "type": "array",
+ "items": {
"type": "string"
- },
- "isRootCause": {
- "description": "The Boolean is a data type having two values (true and false).\n",
- "type": "boolean"
- },
- "correlatedAlarmIds": {
- "description": "List of identifiers of other alarms correlated to this fault.\n",
- "type": "array",
- "items": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- }
- },
- "faultDetails": {
- "description": "Provides additional information about the fault. See notes 1 and 2.\n",
- "type": "array",
- "items": {
- "type": "string"
- }
- },
- "_links": {
- "description": "Links for this resource.\n",
- "type": "object",
- "required": [
- "self"
- ],
- "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"
- }
+ }
+ },
+ "_links": {
+ "description": "Links for this resource.\n",
+ "type": "object",
+ "required": [
+ "self"
+ ],
+ "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"
}
- },
- "objectInstance": {
- "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"
- }
+ }
+ },
+ "objectInstance": {
+ "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"
}
}
}
diff --git a/SOL002/VNFFaultManagement-API/schemas/perceivedSeverityRequest.schema.json b/SOL002/VNFFaultManagement-API/schemas/perceivedSeverityRequest.schema.json
index ee370408ae331b493600571b782eaf0317d50e53..5ee777b0802e9764c23d1194e734cfaf2fcc0d4e 100644
--- a/SOL002/VNFFaultManagement-API/schemas/perceivedSeverityRequest.schema.json
+++ b/SOL002/VNFFaultManagement-API/schemas/perceivedSeverityRequest.schema.json
@@ -1,11 +1,21 @@
{
- "type": "string",
- "enum": [
- "CRITICAL",
- "MAJOR",
- "MINOR",
- "WARNING",
- "INDETERMINATE",
- "CLEARED"
- ]
+ "description": "This type represents the escalated value of the perceived severity for an alarm.\n",
+ "type": "object",
+ "required": [
+ "proposedPerceivedSeverity"
+ ],
+ "properties": {
+ "proposedPerceivedSeverity": {
+ "description": "Indicates the relative level of urgency for operator attention. * CRITICAL: The Critical severity level indicates that a service\n affecting condition has occurred and an immediate corrective action\n is required. Such a severity can be reported, for example, when a\n managed object becomes totally out of service and its capability needs\n to be restored (ITU-T Recommendation X.733).\n* MAJOR: The Major severity level indicates that a service affecting\n condition has developed and an urgent corrective action is required.\n Such a severity can be reported, for example, when there is a severe\n degradation in the capability of the managed object and its full\n capability needs to be restored (ITU-T Recommendation X.733).\n* MINOR: The Minor severity level indicates the existence of a\n non-service affecting fault condition and that corrective action\n should be taken in order to prevent a more serious (for example,\n service affecting) fault. Such a severity can be reported, for\n example, when the detected alarm condition is not currently degrading\n the capacity of the managed object (ITU-T Recommendation X.733).\n* WARNING: The Warning severity level indicates the detection of a\n potential or impending service affecting fault, before any significant\n effects have been felt. Action should be taken to further diagnose (if\n necessary) and correct the problem in order to prevent it from\n becoming a more serious service affecting fault (ITU-T Recommendation\n X.733).\n* INDETERMINATE: The Indeterminate severity level indicates that the\n severity level cannot be determined (ITU-T Recommendation X.733).\n* CLEARED: The Cleared severity level indicates the clearing of one or\n more previously reported alarms. This alarm clears all alarms for this\n managed object that have the same Alarm type, Probable cause and\n Specific problems (if given) (ITU-T Recommendation X.733).\n",
+ "type": "string",
+ "enum": [
+ "CRITICAL",
+ "MAJOR",
+ "MINOR",
+ "WARNING",
+ "INDETERMINATE",
+ "CLEARED"
+ ]
+ }
+ }
}
\ No newline at end of file
diff --git a/SOL002/VNFIndicator-API/ApiVersion.robot b/SOL002/VNFIndicator-API/ApiVersion.robot
index 96c76f6925aff257f6f2a186517df487d2745a9e..d3205fd50acfa8812aee3ae9685e95117874a0c9 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] v3.5.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.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 5b0fa826776dc297d9a41996bb36a57677283e94..4a1e6e24200a79e9772ebbcd440d9335f7b0b744 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] v3.6.1
+ ... Reference: Clause 8.4.6.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.6.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: clause 8.4.6.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: clause 8.4.6.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.6.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.6.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.6.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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 ad1f93f0e0bf1fe7a79abf7447c140106b3204be..e70906560f907e0672731a41b22e6ee9b2ba6001 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] v3.6.1
+ ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.4.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.4.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.4.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.3.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.4.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.4.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.4.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.3.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.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 4503243852c96839c75914de75f4ed8e27a43023..b85205047e30cf10ad65e5f34b1dff52cd9ff304 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] v3.6.1
+ ... Reference: Clause 8.4.7.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.7.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.7.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.7.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.7.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.7.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.7.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
diff --git a/SOL002/VNFIndicator-API/Subscriptions.robot b/SOL002/VNFIndicator-API/Subscriptions.robot
index c2c8c223b60ea71cdc9b9ee08c4a57af26fbff13..80b7bdbf3bc15222bf3a2a3cbd09dce57f00aee4 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] v3.6.1
+ ... Reference: Clause 8.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.5.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.5.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.5.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.5.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VE
... Applicability: The VNF supports the generation and maintenance of indicators
... Post-Conditions: none
@@ -146,7 +146,7 @@ POST Create a new Subscription - Unprocessable Entity
... 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.
... Pre-conditions: none
- ... Reference: Clause 8.4.5.3.1 - ETSI GS NFV-SOL 002 [2] v3.6.1
+ ... Reference: Clause 8.4.5.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -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] v3.6.1
+ ... Reference: Clause 8.4.5.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.5.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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
diff --git a/SOL002/VNFIndicator-API/VNFIndicators.robot b/SOL002/VNFIndicator-API/VNFIndicators.robot
index 4fca8145969f673a06793a5db63cf838b94d9426..219ecabc60f2f139bc0c5470c1dd501f53c18ce3 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] v3.6.1
+ ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 4.5.3.3, 8.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 4.5.3.3, 8.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 4.5.3.3, 8.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.2.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.2.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.2.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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 df82c7c00d7d6c31afe93c8836828c3ef37ccba2..f5779bbe236323071ebb46067553d539f329e651 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] v3.6.1
+ ... Reference: Clause 8.4.3.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.3.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.3.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.3.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.3.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.3.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.3.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.3.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.3.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.3.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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/schemas/VnfIndicatorSubscription.schema.json b/SOL002/VNFIndicator-API/schemas/VnfIndicatorSubscription.schema.json
index c0065726d71fa160a3770194ce3339552f1d655a..434a9a44eac3d574a9e03a295b3c51a2616ac3dc 100644
--- a/SOL002/VNFIndicator-API/schemas/VnfIndicatorSubscription.schema.json
+++ b/SOL002/VNFIndicator-API/schemas/VnfIndicatorSubscription.schema.json
@@ -12,14 +12,16 @@
"type": "string"
},
"filter": {
- "description": "This type represents a subscription filter for notifications related to VNF indicators. At a particular nesting level in the filter structure, the following applies: All attributes shall match in order for the filter to match (logical \"and\" between different filter attributes). If an attribute is an array, the attribute shall match if at least one of the values in the array matches (logical \"or\" between the values of one filter attribute).\n",
+ "description": "This type represents a subscription filter for notifications related to VNF indicators.\nAt a particular nesting level in the filter structure, the following applies: All attributes shall match in order for the filter to match (logical \"and\" between different filter attributes). If an attribute is an array, the attribute shall match if at least one of the values in the array matches (logical \"or\" between the values of one filter attribute).\nNOTE:\tThe permitted values of the \"notificationTypes\" attribute are spelled exactly as the names \n of the notification types to facilitate automated code generation systems.\n",
"type": "object",
"properties": {
"vnfInstanceSubscriptionFilter": {
- "description": "This type represents subscription filter criteria to match VNF instances.\n",
+ "description": "This type represents subscription filter criteria to match VNF instances. * NOTE 1:\tThe attributes \"vnfdIds\" and \"vnfProductsFromProviders\" are alternatives to reference to VNF instances\n that are based on certain VNFDs in a filter. They should not be used both in the same filter instance,\n but one alternative should be chosen.\n NOTE 2:\tThe attributes \"vnfInstanceIds\" and \"vnfInstanceNames\" are alternatives to reference to particular VNF\n instances in a filter. They should not be used both in the same filter instance, but one alternative\n should be chosen.\n",
"type": "object",
- "anyOf": [{
- "oneOf": [{
+ "anyOf": [
+ {
+ "oneOf": [
+ {
"required": [
"vnfdId"
]
@@ -32,7 +34,8 @@
]
},
{
- "oneOf": [{
+ "oneOf": [
+ {
"required": [
"vnfInstanceIds"
]
@@ -47,7 +50,7 @@
],
"properties": {
"vnfdIds": {
- "description": "If present, match VNF instances that were created based on a VNFD identified by one of the vnfdId values listed in this attribute. The attributes \"vnfdIds\" and \"vnfProductsFromProviders\" are alternatives to reference to VNF instances that are based on certain VNFDs in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n",
+ "description": "If present, match VNF instances that were created based on a VNFD identified by one of the vnfdId values listed in this attribute. See note 1.\n",
"type": "array",
"items": {
"description": "An identifier with the intention of being globally unique.\n",
@@ -55,7 +58,7 @@
}
},
"vnfProductsFromProviders": {
- "description": "If present, match VNF instances that belong to VNF products from certain providers. The attributes \"vnfdIds\" and \"vnfProductsFromProviders\" are alternatives to reference to VNF instances that are based on certain VNFDs in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n",
+ "description": "If present, match VNF instances that belong to VNF products from certain providers. See note 1.\n",
"type": "array",
"items": {
"type": "object",
@@ -111,7 +114,7 @@
}
},
"vnfInstanceIds": {
- "description": "If present, match VNF instances with an instance identifier listed in this attribute. The attributes \"vnfInstanceIds\" and \"vnfInstanceNames\" are alternatives to reference to particular VNF Instances in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n",
+ "description": "If present, match VNF instances with an instance identifier listed in this attribute. See note 2.\n",
"type": "array",
"items": {
"description": "An identifier with the intention of being globally unique.\n",
@@ -119,7 +122,7 @@
}
},
"vnfInstanceNames": {
- "description": "If present, match VNF instances with a VNF Instance Name listed in this attribute. The attributes \"vnfInstanceIds\" and \"vnfInstanceNames\" are alternatives to reference to particular VNF Instances in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n",
+ "description": "If present, match VNF instances with a VNF Instance Name listed in this attribute. See note 2.\n",
"type": "array",
"items": {
"type": "string"
@@ -128,7 +131,7 @@
}
},
"notificationTypes": {
- "description": "Match particular notification types. Permitted values: *\tVnfIndicatorValueChangeNotification *\tSupportedIndicatorsChangeNotification The permitted values of the \"notificationTypes\" attribute are spelled exactly as the names of the notification types to facilitate automated code generation systems.\n",
+ "description": "Match particular notification types. \nPermitted values: -\tVnfIndicatorValueChangeNotification -\tSupportedIndicatorsChangeNotification See note.\n",
"type": "string",
"enum": [
"VnfIndicatorValueChangeNotification",
@@ -173,4 +176,4 @@
}
}
}
-}s
\ No newline at end of file
+}
\ No newline at end of file
diff --git a/SOL002/VNFIndicator-API/schemas/VnfIndicatorSubscriptions.schema.json b/SOL002/VNFIndicator-API/schemas/VnfIndicatorSubscriptions.schema.json
index f495a62796412beda89d1b35adeb9633678a3588..1c074e6d017832503d55acda09459b5878fc8821 100644
--- a/SOL002/VNFIndicator-API/schemas/VnfIndicatorSubscriptions.schema.json
+++ b/SOL002/VNFIndicator-API/schemas/VnfIndicatorSubscriptions.schema.json
@@ -1,180 +1,182 @@
{
"type": "array",
- "items":
- {
- "description": "This type represents a subscription related to notifications about VNF indicator value changes.\n",
- "type": "object",
- "required": [
- "id",
- "callbackUri",
- "_links"
- ],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "filter": {
- "description": "This type represents a subscription filter for notifications related to VNF indicators. At a particular nesting level in the filter structure, the following applies: All attributes shall match in order for the filter to match (logical \"and\" between different filter attributes). If an attribute is an array, the attribute shall match if at least one of the values in the array matches (logical \"or\" between the values of one filter attribute).\n",
- "type": "object",
- "properties": {
- "vnfInstanceSubscriptionFilter": {
- "description": "This type represents subscription filter criteria to match VNF instances.\n",
- "type": "object",
- "anyOf": [{
- "oneOf": [{
- "required": [
- "vnfdId"
- ]
- },
- {
- "required": [
- "vnfProductsFromProviders"
- ]
- }
- ]
- },
- {
- "oneOf": [{
- "required": [
- "vnfInstanceIds"
- ]
- },
- {
- "required": [
- "vnfInstanceNames"
- ]
- }
- ]
- }
- ],
- "properties": {
- "vnfdIds": {
- "description": "If present, match VNF instances that were created based on a VNFD identified by one of the vnfdId values listed in this attribute. The attributes \"vnfdIds\" and \"vnfProductsFromProviders\" are alternatives to reference to VNF instances that are based on certain VNFDs in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n",
- "type": "array",
- "items": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- }
- },
- "vnfProductsFromProviders": {
- "description": "If present, match VNF instances that belong to VNF products from certain providers. The attributes \"vnfdIds\" and \"vnfProductsFromProviders\" are alternatives to reference to VNF instances that are based on certain VNFDs in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": [
- "vnfProvider"
- ],
- "properties": {
- "vnfProvider": {
- "description": "Name of the VNF provider to match.\n",
- "type": "string"
- },
- "vnfProducts": {
- "description": "If present, match VNF instances that belong to VNF products with certain product names, from one particular provider.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": [
- "vnfProductName"
- ],
- "properties": {
- "vnfProductName": {
- "description": "Name of the VNF product to match.\n",
- "type": "string"
- },
- "versions": {
- "description": "If present, match VNF instances that belong to VNF products with certain versions and a certain product name, from one particular provider.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": [
- "vnfSoftwareVersion"
- ],
- "properties": {
- "vnfSoftwareVersion": {
- "description": "A version.\n",
- "type": "string"
- },
- "vnfdVersions": {
- "description": "If present, match VNF instances that belong to VNF products with certain VNFD versions, a certain software version and a certain product name, from one particular provider.\n",
- "type": "array",
- "items": {
- "description": "A version.\n",
- "type": "string"
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- },
- "vnfInstanceIds": {
- "description": "If present, match VNF instances with an instance identifier listed in this attribute. The attributes \"vnfInstanceIds\" and \"vnfInstanceNames\" are alternatives to reference to particular VNF Instances in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n",
- "type": "array",
- "items": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- }
- },
- "vnfInstanceNames": {
- "description": "If present, match VNF instances with a VNF Instance Name listed in this attribute. The attributes \"vnfInstanceIds\" and \"vnfInstanceNames\" are alternatives to reference to particular VNF Instances in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n",
- "type": "array",
- "items": {
- "type": "string"
- }
- }
- }
- },
- "notificationTypes": {
- "description": "Match particular notification types. Permitted values: *\tVnfIndicatorValueChangeNotification *\tSupportedIndicatorsChangeNotification The permitted values of the \"notificationTypes\" attribute are spelled exactly as the names of the notification types to facilitate automated code generation systems.\n",
- "type": "string",
- "enum": [
- "VnfIndicatorValueChangeNotification",
- "SupportedIndicatorsChangeNotification"
- ]
- },
- "indicatorIds": {
- "description": "Match particular VNF indicator identifiers.\n",
- "type": "array",
- "items": {
- "description": "An identifier that is unique within a VNF descriptor.\n",
- "type": "string"
- }
- }
- }
- },
- "callbackUri": {
- "description": "The URI of the endpoint to send the notification to.\n",
- "type": "string",
- "format": "url"
- },
- "_links": {
- "description": "Links for this resource.\n",
- "type": "object",
- "required": [
- "self"
- ],
- "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"
- }
- }
- }
- }
- }
- }
- }
+ "items": {
+ "description": "This type represents a subscription related to notifications about VNF indicator value changes.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "callbackUri",
+ "_links"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "filter": {
+ "description": "This type represents a subscription filter for notifications related to VNF indicators.\nAt a particular nesting level in the filter structure, the following applies: All attributes shall match in order for the filter to match (logical \"and\" between different filter attributes). If an attribute is an array, the attribute shall match if at least one of the values in the array matches (logical \"or\" between the values of one filter attribute).\nNOTE:\tThe permitted values of the \"notificationTypes\" attribute are spelled exactly as the names \n of the notification types to facilitate automated code generation systems.\n",
+ "type": "object",
+ "properties": {
+ "vnfInstanceSubscriptionFilter": {
+ "description": "This type represents subscription filter criteria to match VNF instances. * NOTE 1:\tThe attributes \"vnfdIds\" and \"vnfProductsFromProviders\" are alternatives to reference to VNF instances\n that are based on certain VNFDs in a filter. They should not be used both in the same filter instance,\n but one alternative should be chosen.\n NOTE 2:\tThe attributes \"vnfInstanceIds\" and \"vnfInstanceNames\" are alternatives to reference to particular VNF\n instances in a filter. They should not be used both in the same filter instance, but one alternative\n should be chosen.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "oneOf": [
+ {
+ "required": [
+ "vnfdId"
+ ]
+ },
+ {
+ "required": [
+ "vnfProductsFromProviders"
+ ]
+ }
+ ]
+ },
+ {
+ "oneOf": [
+ {
+ "required": [
+ "vnfInstanceIds"
+ ]
+ },
+ {
+ "required": [
+ "vnfInstanceNames"
+ ]
+ }
+ ]
+ }
+ ],
+ "properties": {
+ "vnfdIds": {
+ "description": "If present, match VNF instances that were created based on a VNFD identified by one of the vnfdId values listed in this attribute. See note 1.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ },
+ "vnfProductsFromProviders": {
+ "description": "If present, match VNF instances that belong to VNF products from certain providers. See note 1.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": [
+ "vnfProvider"
+ ],
+ "properties": {
+ "vnfProvider": {
+ "description": "Name of the VNF provider to match.\n",
+ "type": "string"
+ },
+ "vnfProducts": {
+ "description": "If present, match VNF instances that belong to VNF products with certain product names, from one particular provider.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": [
+ "vnfProductName"
+ ],
+ "properties": {
+ "vnfProductName": {
+ "description": "Name of the VNF product to match.\n",
+ "type": "string"
+ },
+ "versions": {
+ "description": "If present, match VNF instances that belong to VNF products with certain versions and a certain product name, from one particular provider.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": [
+ "vnfSoftwareVersion"
+ ],
+ "properties": {
+ "vnfSoftwareVersion": {
+ "description": "A version.\n",
+ "type": "string"
+ },
+ "vnfdVersions": {
+ "description": "If present, match VNF instances that belong to VNF products with certain VNFD versions, a certain software version and a certain product name, from one particular provider.\n",
+ "type": "array",
+ "items": {
+ "description": "A version.\n",
+ "type": "string"
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ },
+ "vnfInstanceIds": {
+ "description": "If present, match VNF instances with an instance identifier listed in this attribute. See note 2.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ },
+ "vnfInstanceNames": {
+ "description": "If present, match VNF instances with a VNF Instance Name listed in this attribute. See note 2.\n",
+ "type": "array",
+ "items": {
+ "type": "string"
+ }
+ }
+ }
+ },
+ "notificationTypes": {
+ "description": "Match particular notification types. \nPermitted values: -\tVnfIndicatorValueChangeNotification -\tSupportedIndicatorsChangeNotification See note.\n",
+ "type": "string",
+ "enum": [
+ "VnfIndicatorValueChangeNotification",
+ "SupportedIndicatorsChangeNotification"
+ ]
+ },
+ "indicatorIds": {
+ "description": "Match particular VNF indicator identifiers.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "callbackUri": {
+ "description": "The URI of the endpoint to send the notification to.\n",
+ "type": "string",
+ "format": "url"
+ },
+ "_links": {
+ "description": "Links for this resource.\n",
+ "type": "object",
+ "required": [
+ "self"
+ ],
+ "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"
+ }
+ }
+ }
+ }
+ }
+ }
+ }
}
\ No newline at end of file
diff --git a/SOL002/VNFIndicator-API/schemas/vnfIndicator.schema.json b/SOL002/VNFIndicator-API/schemas/vnfIndicator.schema.json
index 7d12d66566c0ad725987f4f449eb9360b538cef8..209ea76706900a67c15f57f6b9c68814cf3c8510 100644
--- a/SOL002/VNFIndicator-API/schemas/vnfIndicator.schema.json
+++ b/SOL002/VNFIndicator-API/schemas/vnfIndicator.schema.json
@@ -1,4 +1,5 @@
{
+ "description": "This type represents a VNF indicator value.\nNOTE:\tETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on TOSCA specifications.\n",
"type": "object",
"required": [
"id",
@@ -12,9 +13,11 @@
"type": "string"
},
"name": {
+ "description": "Human readable name of the indicator. Shall be present if defined in the VNFD.\n",
"type": "string"
},
"value": {
+ "description": "Provides the value of the indicator. The value format is defined in the VNFD. See note.\n",
"type": "object"
},
"vnfInstanceId": {
@@ -22,37 +25,36 @@
"type": "string"
},
"_links": {
- "description": "Links to resources related to this resource.\n",
+ "description": "Links for this resource.\n",
"type": "object",
"required": [
- "self"
+ "self",
+ "vnfInstance"
],
"properties": {
"self": {
- "description": "This type represents a link to a resource.\n",
+ "description": "This type represents a link to a resource using an absolute URI.\n",
"type": "object",
"required": [
"href"
],
"properties": {
"href": {
- "description": "URI of the referenced resource.\n",
- "type": "string",
- "format": "url"
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
}
}
},
"vnfInstance": {
- "description": "This type represents a link to a resource.\n",
+ "description": "This type represents a link to a resource using an absolute URI.\n",
"type": "object",
"required": [
"href"
],
"properties": {
"href": {
- "description": "URI of the referenced resource.\n",
- "type": "string",
- "format": "url"
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
}
}
}
diff --git a/SOL002/VNFIndicator-API/schemas/vnfIndicators.schema.json b/SOL002/VNFIndicator-API/schemas/vnfIndicators.schema.json
index 3f6a84d579cd12c66b2af8cef3c9110e67cc3540..686df172445674ed7cf24190bbb04525e8437909 100644
--- a/SOL002/VNFIndicator-API/schemas/vnfIndicators.schema.json
+++ b/SOL002/VNFIndicator-API/schemas/vnfIndicators.schema.json
@@ -1 +1,67 @@
-{ "type": "array", "items": { "type": "object", "required": [ "id", "value", "vnfInstanceId", "_links" ], "properties": { "id": { "description": "An identifier that is unique within a VNF descriptor.\n", "type": "string" }, "name": { "type": "string" }, "value": { "type": "object" }, "vnfInstanceId": { "description": "An identifier with the intention of being globally unique.\n", "type": "string" }, "_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 the referenced resource.\n", "type": "string", "format": "url" } } }, "vnfInstance": { "description": "This type represents a link to a resource.\n", "type": "object", "required": [ "href" ], "properties": { "href": { "description": "URI of the referenced resource.\n", "type": "string", "format": "url" } } } } } } }}
\ No newline at end of file
+{
+ "type": "array",
+ "items": {
+ "description": "This type represents a VNF indicator value.\nNOTE:\tETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on TOSCA specifications.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "value",
+ "vnfInstanceId",
+ "_links"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "name": {
+ "description": "Human readable name of the indicator. Shall be present if defined in the VNFD.\n",
+ "type": "string"
+ },
+ "value": {
+ "description": "Provides the value of the indicator. The value format is defined in the VNFD. See note.\n",
+ "type": "object"
+ },
+ "vnfInstanceId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "_links": {
+ "description": "Links for this resource.\n",
+ "type": "object",
+ "required": [
+ "self",
+ "vnfInstance"
+ ],
+ "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"
+ }
+ }
+ },
+ "vnfInstance": {
+ "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"
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+}
\ No newline at end of file
diff --git a/SOL002/VNFIndicatorNotification-API/Notifications.robot b/SOL002/VNFIndicatorNotification-API/Notifications.robot
index c186bf4123f25ddb1ada7c4625263013fa1a61d7..2a5b9f47f0a05947f8f654424b844195971d052c 100644
--- a/SOL002/VNFIndicatorNotification-API/Notifications.robot
+++ b/SOL002/VNFIndicatorNotification-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] v3.6.1
+ ... Reference: Clause 8.4.7.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.7.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VNF
... Applicability: none
... Post-Conditions: none
diff --git a/SOL002/VNFIndicatorNotification-API/schemas/VnfIndicatorValueChangeNotification.schema.json b/SOL002/VNFIndicatorNotification-API/schemas/VnfIndicatorValueChangeNotification.schema.json
index c91de218005531a44de41d1175810103c1dcf164..7a33be24bbb854eb93b673c0fd6f95a10d6f0109 100644
--- a/SOL002/VNFIndicatorNotification-API/schemas/VnfIndicatorValueChangeNotification.schema.json
+++ b/SOL002/VNFIndicatorNotification-API/schemas/VnfIndicatorValueChangeNotification.schema.json
@@ -1,7 +1,8 @@
{
- "description": "This type represents a VNF indicator value change notification.\n",
- "type": "object",
- "required": [
+ "VnfIndicatorValueChangeNotification": {
+ "description": "This type represents a VNF indicator value change notification. * NOTE:\tETSI GS NFV-SOL 001 specifies the structure and\n format of the VNFD based on TOSCA specifications.\n",
+ "type": "object",
+ "required": [
"id",
"notificationType",
"subscriptionId",
@@ -10,78 +11,166 @@
"value",
"vnfInstanceId",
"_links"
- ],
- "properties": {
+ ],
+ "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"
},
"notificationType": {
- "description": "Discriminator for the different notification types. Shall be set to \"VnfIndicatorValueChangeNotification\" for this notification type.\n",
- "type": "string"
+ "description": "Discriminator for the different notification types. Shall be set to \"VnfIndicatorValueChangeNotification\" for this notification type.\n",
+ "type": "string"
},
"subscriptionId": {
- "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"
},
"timeStamp": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
},
"vnfIndicatorId": {
- "description": "An identifier that is unique within a VNF descriptor.\n",
- "type": "string"
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
},
"name": {
- "description": "Human readable name of the VNF indicator. Shall be present if defined in the VNFD.\n",
- "type": "string"
+ "description": "Human readable name of the VNF indicator. Shall be present if defined in the VNFD.\n",
+ "type": "string"
},
"value": {
- "description": "Provides the value of the VNF indicator. The value format is defined in the VNFD. \n",
- "type": "object"
+ "description": "Provides the value of the VNF indicator. The value format is defined in the VNFD. See note.\n",
+ "type": "object"
},
"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"
},
"_links": {
- "description": "Links to resources related to this resource.\n",
+ "description": "Links to resources related to this resource.\n",
+ "type": "object",
+ "required": [
+ "vnfInstance",
+ "subscription"
+ ],
+ "properties": {
+ "vnfInstance": {
+ "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"
+ }
+ }
+ },
+ "subscription": {
+ "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"
+ }
+ }
+ }
+ }
+ }
+ }
+ },
+ "SupportedIndicatorsChangeNotification": {
+ "description": "This type represents a notification to inform the receiver that the set of indicators\nsupported by a VNF instance has changed.\n* NOTE:\tETSI GS NFV-SOL 001 specifies the structure and\n format of the VNFD based on TOSCA specifications.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "notificationType",
+ "subscriptionId",
+ "timeStamp",
+ "vnfInstanceId"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "notificationType": {
+ "description": "Discriminator for the different notification types. Shall be set to \"SupportedIndicatorsChangeNotification\"\nfor 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 to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "vnfInstanceId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "supportedIndicators": {
+ "description": "Set of VNF indicators supported by the VNF instance.\n",
+ "type": "array",
+ "items": {
"type": "object",
"required": [
- "vnfInstance",
- "subscription"
+ "vnfIndicatorId"
],
"properties": {
- "vnfInstance": {
- "description": "This type represents a link to a resource.\n",
- "type": "object",
- "required": [
- "href"
- ],
- "properties": {
- "href": {
- "description": "URI of the referenced resource.\n",
- "type": "string",
- "format": "url"
- }
- }
- },
- "subscription": {
- "description": "This type represents a link to a resource.\n",
- "type": "object",
- "required": [
- "href"
- ],
- "properties": {
- "href": {
- "description": "URI of the referenced resource.\n",
- "type": "string",
- "format": "url"
- }
- }
+ "vnfIndicatorId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "name": {
+ "description": "Human readable name of the VNF indicator. Shall be present if defined in the VNFD.\nSee note.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "_links": {
+ "description": "Links for this resource.\n",
+ "type": "object",
+ "required": [
+ "subscription"
+ ],
+ "properties": {
+ "vnfInstance": {
+ "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": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ }
+ }
+ },
+ "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": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
}
+ }
}
+ }
}
+ }
}
-}
\ No newline at end of file
+ }
\ No newline at end of file
diff --git a/SOL002/VNFLCMCoordination-API/ApiVersion.robot b/SOL002/VNFLCMCoordination-API/ApiVersion.robot
index 11d89668e2e460ccefea47feb778a69e324dc8cf..8c23db3fe641f20aee540463bb68a3a69c9c6a43 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] v3.5.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.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 8aea9be19015e1d4b4e94b5abbe0acd970713dcd..8f84fa1bd59ac08cdb3c914e103a183640bb1713 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] v3.6.1
+ ... Reference: Clause 10.4.4.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.4.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause Clause 10.4.4.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.4.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.4.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.4.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.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 fd8e6ccb86ff94e54f417e27b8ab08896790509e..8020da914796eaa61eb8f30517e0aa2843943fe2 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] v3.6.1
+ ... Reference: Clause 10.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.2.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.2.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.2.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.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 98ef18a02cb3ac9f7fac5bc13a0c8f396318df7c..871540dac54629527625c04dc0f9b6f4f264922c 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] v3.6.1
+ ... Reference: Clause 10.4.3.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.3.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.3.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.3.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.3.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.3.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.3.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Condition: none
diff --git a/SOL002/VNFLCMCoordination-API/schemas/LcmCoord.schema.json b/SOL002/VNFLCMCoordination-API/schemas/LcmCoord.schema.json
index fdadd65b75a5c0ba3b2036f5cf91b61a1abcc967..e685d25af5ed21c0a201fd0fd674865fadd7f0b8 100644
--- a/SOL002/VNFLCMCoordination-API/schemas/LcmCoord.schema.json
+++ b/SOL002/VNFLCMCoordination-API/schemas/LcmCoord.schema.json
@@ -1,148 +1,148 @@
{
- "description": "This type represents an LCM coordination result.\n",
- "type": "object",
- "required": [
- "id",
- "coordinationResult",
- "vnfInstanceId",
- "vnfLcmOpOccId",
- "lcmOperationType",
- "coordinationActionName",
- "_links"
- ],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "coordinationResult": {
- "description": "The enumeration LcmCoordResultType defines the permitted values to represent the result of executing an LCM coordination action. The coordination result also implies the action to be performed by the VNFM as the follow-up to this coordination. Value | Description ------|------------ CONTINUE | The related LCM operation shall be continued, staying in the state \"PROCESSING\". ABORT | The related LCM operation shall be aborted by transitioning into the state \"FAILED_TEMP\". CANCELLED | The coordination action has been cancelled upon request of the API consumer, i.e. the VNFM. The related LCM operation shall be aborted by transitioning into the state \"FAILED_TEMP\".\n",
- "type": "string",
- "enum": [
- "CONTINUE",
- "ABORT",
- "CANCELLED"
- ]
- },
- "vnfInstanceId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfLcmOpOccId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "lcmOperationType": {
- "description": "The enumeration LcmOperationForCoordType defines the permitted values to represent VNF lifecycle operation types in VNF LCM operation coordination actions. * INSTANTIATE: Represents the \"Instantiate VNF\" LCM operation. * SCALE: Represents the \"Scale VNF\" LCM operation. * SCALE_TO_LEVEL: Represents the \"Scale VNF to Level\" LCM operation. * CHANGE_FLAVOUR: Represents the \"Change VNF Flavour\" LCM operation. * TERMINATE: Represents the \"Terminate VNF\" LCM operation. * HEAL: Represents the \"Heal VNF\" LCM operation. * OPERATE: Represents the \"Operate VNF\" LCM operation. * CHANGE_EXT_CONN: Represents the \"Change external VNF connectivity\" LCM operation. * MODIFY_INFO: Represents the \"Modify VNF Information\" LCM operation. * CREATE_SNAPSHOT: Represents the \"Create VNF Snapshot\" LCM operation. * REVERT_TO_SNAPSHOT: Represents the \"Revert To VNF Snapshot\" LCM operation. * CHANGE_VNFPKG: Represents the \"Change current VNF package\" LCM operation.\n",
- "type": "string",
- "enum": [
- "INSTANTIATE",
- "SCALE",
- "SCALE_TO_LEVEL",
- "CHANGE_FLAVOUR",
- "TERMINATE",
- "HEAL",
- "OPERATE",
- "CHANGE_EXT_CONN",
- "MODIFY_INFO",
- "CREATE_SNAPSHOT",
- "REVERT_TO_SNAPSHOT",
- "CHANGE_VNFPKG"
- ]
- },
- "coordinationActionName": {
- "description": "Indicates the actual LCM coordination action. The coordination actions that a VNF supports are declared in the VNFD.\n",
- "type": "string"
- },
- "outputParams": {
- "description": "This 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"
- },
- "warnings": {
- "description": "Warning messages that were generated while the operation was executing.\n",
- "type": "string"
- },
- "error": {
- "description": "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 is reproduced inthis structure. Compared to the general framework defined in IETF RFC 7807, 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 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.\n",
- "type": "object",
- "required": [
- "status",
- "detail"
- ],
- "properties": {
- "type": {
- "description": "A URI reference according to IETF RFC 3986 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"
- }
+ "description": "This type represents an LCM coordination result.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "coordinationResult",
+ "vnfInstanceId",
+ "vnfLcmOpOccId",
+ "lcmOperationType",
+ "coordinationActionName",
+ "_links"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "coordinationResult": {
+ "description": "The enumeration LcmCoordResultType defines the permitted values to represent the result of executing an LCM coordination action. The coordination result also implies the action to be performed by the VNFM as the follow-up to this coordination. Value | Description ------|------------ CONTINUE | The related LCM operation shall be continued, staying in the state \"PROCESSING\". ABORT | The related LCM operation shall be aborted by transitioning into the state \"FAILED_TEMP\". CANCELLED | The coordination action has been cancelled upon request of the API consumer, i.e. the VNFM. The related LCM operation shall be aborted by transitioning into the state \"FAILED_TEMP\".\n",
+ "type": "string",
+ "enum": [
+ "CONTINUE",
+ "ABORT",
+ "CANCELLED"
+ ]
+ },
+ "vnfInstanceId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfLcmOpOccId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "lcmOperationType": {
+ "description": "The enumeration LcmOperationForCoordType defines the permitted values to represent VNF lifecycle operation types in VNF LCM operation coordination actions. * INSTANTIATE: Represents the \"Instantiate VNF\" LCM operation. * SCALE: Represents the \"Scale VNF\" LCM operation. * SCALE_TO_LEVEL: Represents the \"Scale VNF to Level\" LCM operation. * CHANGE_FLAVOUR: Represents the \"Change VNF Flavour\" LCM operation. * TERMINATE: Represents the \"Terminate VNF\" LCM operation. * HEAL: Represents the \"Heal VNF\" LCM operation. * OPERATE: Represents the \"Operate VNF\" LCM operation. * CHANGE_EXT_CONN: Represents the \"Change external VNF connectivity\" LCM operation. * MODIFY_INFO: Represents the \"Modify VNF Information\" LCM operation. * CREATE_SNAPSHOT: Represents the \"Create VNF Snapshot\" LCM operation. * REVERT_TO_SNAPSHOT: Represents the \"Revert To VNF Snapshot\" LCM operation. * CHANGE_VNFPKG: Represents the \"Change current VNF package\" LCM operation.\n",
+ "type": "string",
+ "enum": [
+ "INSTANTIATE",
+ "SCALE",
+ "SCALE_TO_LEVEL",
+ "CHANGE_FLAVOUR",
+ "TERMINATE",
+ "HEAL",
+ "OPERATE",
+ "CHANGE_EXT_CONN",
+ "MODIFY_INFO",
+ "CREATE_SNAPSHOT",
+ "REVERT_TO_SNAPSHOT",
+ "CHANGE_VNFPKG"
+ ]
+ },
+ "coordinationActionName": {
+ "description": "Indicates the actual LCM coordination action. The coordination actions that a VNF supports are declared in the VNFD.\n",
+ "type": "string"
+ },
+ "outputParams": {
+ "description": "This 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"
+ },
+ "warnings": {
+ "description": "Warning messages that were generated while the operation was executing.\n",
+ "type": "string"
+ },
+ "error": {
+ "description": "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 is reproduced inthis structure. Compared to the general framework defined in IETF RFC 7807, 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 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.\n",
+ "type": "object",
+ "required": [
+ "status",
+ "detail"
+ ],
+ "properties": {
+ "type": {
+ "description": "A URI reference according to IETF RFC 3986 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"
}
- },
- "_links": {
- "description": "Links to resources related to this resource.\n",
- "type": "object",
- "required": [
- "self",
- "vnfLcmOpOcc",
- "vnfInstance"
- ],
- "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"
- }
+ }
+ },
+ "_links": {
+ "description": "Links to resources related to this resource.\n",
+ "type": "object",
+ "required": [
+ "self",
+ "vnfLcmOpOcc",
+ "vnfInstance"
+ ],
+ "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"
}
- },
- "vnfLcmOpOcc": {
- "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"
- }
+ }
+ },
+ "vnfLcmOpOcc": {
+ "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"
}
- },
- "vnfInstance": {
- "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"
- }
+ }
+ },
+ "vnfInstance": {
+ "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"
}
}
}
}
}
- }
\ No newline at end of file
+ }
+}
\ No newline at end of file
diff --git a/SOL002/VNFLifecycleManagement-API/ApiVersion.robot b/SOL002/VNFLifecycleManagement-API/ApiVersion.robot
index 182df54f010bb2b1914d0de424c34fade2f530c7..0d713d4612c83e774205c352fafb885c07c35641 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] v3.5.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.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 61fba3f553cf57886ef544ba8839d5b8e07d8640..79f0e080b7d85beeff7ec00b7a8cc8900336e23e 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] v3.6.1
+ ... Reference: Clause 5.4.17.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.17.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.17.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.17.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.17.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.17.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.17.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.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 f30b3f11987b86dab35c6e9fb04587fed1f2e92d..f8e534e824eb86cd75214b1ec237293308582a00 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] v3.6.1
+ ... Reference: Clause 5.4.11a.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.11a.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.11a.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.11a.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.11a.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.11a.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.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 f57dce6577d28f492af2698834579780f835529e..7265d193c6c5d873e501b067383e9021b873bacf 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] v3.6.1
+ ... Reference: Clause 5.4.11.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.11.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.11.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.11.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.11.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.11.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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 ca5dd6bd1e9e8abac838b8656660225bb1ec6b37..9d6c8939506867771bb6d556a5fd6e65d1d6bd81 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] v3.6.1
+ ... Reference: Clause 5.4.7.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.7.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.7.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.7.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.7.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.7.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.7.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.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 273ae52862e86a41062a80b8e66d45c6ffa81a24..31d32e3f683f5bb0e32e43ababa746d0f5e31c18 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] v3.6.1
+ ... Reference: Clause 5.4.21.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.21.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.21.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VE
... Applicability: VNF instance is in NOT_INSTANTIATED state.
... Post-Conditions: none
@@ -52,7 +52,7 @@ POST Create VNF Snapshot Task - UNPROCESSIBLE ENTITY
... Test title: POST Create VNF Snapshot Task - UNPROCESSIBLE ENTITY
... 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] v3.6.1
+ ... Reference: Clause 5.4.21.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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
@@ -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] v3.6.1
+ ... Reference: Clause 5.4.21.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.21.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.21.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.21.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.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 8c58aefbdf8ce68a80c6400b0390bb75f231cc08..8fb44ad4662b0b59ce5223c44de5e37c6d47cd70 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] v3.6.1
+ ... Reference: Clause 5.4.16.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.16.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.16.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.16.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.16.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.16.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.16.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.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 fae1f502862db658680dc41baf0feea3b53dfcf8..a4b85291afa6e175490d295099fa589d184334da 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] v3.6.1
+ ... Reference: Clause 5.4.9.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.9.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.9.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.9.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.9.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.9.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.9.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.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 60c18199e0d0b531f86b53d55b010dd19b314f40..332d6a0a7c2d2de6b314211cbe8c0843e631c69f 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] v3.6.1
+ ... Reference: Clause 5.4.19.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.19.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.19.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.19.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.19.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.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 cdd3378acad754f800ff2b2edbbde1c6b8a35c20..de4f26c868de4e7234fbc3fc7ecd565b33aec3e4 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] v3.6.1
+ ... Reference: Clause 5.4.3.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -30,12 +30,13 @@ 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] v3.6.1
+ ... Reference: Clause 5.4.3.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
GET individual vnfInstance
Check HTTP Response Status Code Is 200
+ Check HTTP Response Header Contains ETag and Last-Modified
Check HTTP Response Body Json Schema Is vnfInstance
Check HTTP Response Body vnfInstance content against VNF Descriptor
@@ -44,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] v3.6.1
+ ... Reference: Clause 5.4.3.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: VNF instance not modified
@@ -56,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] v3.6.1
+ ... Reference: Clause 5.4.3.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: VNF instance modified
@@ -69,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] v3.6.1
+ ... Reference: Clause 5.4.3.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -82,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] v3.6.1
+ ... Reference: Clause 5.4.3.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -95,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] v3.6.1
+ ... Reference: Clause 5.4.3.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: VNF instance deleted
@@ -107,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] v3.6.1
+ ... Reference: Clause 5.4.3.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.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 0f97de0c9260434c6a88fb8202e3aa848074a2ef..5e737b0db488811bbb32abb157e027ec73bc14ec 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] v3.6.1
+ ... Reference: Clause 5.4.24.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.24.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.24.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.24.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.24.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.24.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.24.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.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 14bb9e6af532f0d20f650cffb76fce820976fa7b..63859ff736cf2d2be51ab9daec98815f60321ffb 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] v3.6.1
+ ... Reference: Clause 5.4.13.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.13.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.13.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.13.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.13.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.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 a4bc6b77e8061b14cfa9d61773cf710bacd71b64..694506c6f90c5dcadbabc204bb071aced634a749 100644
--- a/SOL002/VNFLifecycleManagement-API/InstantiateVNFTask.robot
+++ b/SOL002/VNFLifecycleManagement-API/InstantiateVNFTask.robot
@@ -15,20 +15,20 @@ 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] v3.6.1
+ ... Reference: Clause 5.4.4.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
POST instantiate individual vnfInstance
Check HTTP Response Status Code Is 202
Check Operation Occurrence Id
-
+
POST Instantiate a vnfInstance Conflict
[Documentation] Test ID: 6.3.5.3.2
... 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] v3.6.1
+ ... Reference: Clause 5.4.4.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.4.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.4.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.4.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -77,13 +77,39 @@ 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] v3.6.1
+ ... Reference: Clause 5.4.4.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
DELETE instantiate individual vnfInstance
Check HTTP Response Status Code Is 405
+POST Instantiate a vnfInstance with TaretScaleLevelId
+ [Documentation] Test ID: 6.3.5.3.7
+ ... 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
+ ... Config ID: Config_prod_VE
+ ... Applicability: none
+ ... Post-Conditions: none
+ POST instantiate individual vnfInstance with TargetScaleLevelId
+ Check HTTP Response Status Code Is 202
+ Check Operation Occurrence Id
+
+POST Instantiate individual vnfInstance with instantiationLevelId
+ [Documentation] Test ID: 6.3.5.3.8
+ ... 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
+ ... Config ID: Config_prod_VE
+ ... Applicability: none
+ ... Post-Conditions: none
+ POST instantiate individual vnfInstance with instantiationLevelId
+ Check HTTP Response Status Code Is 202
+ Check Operation Occurrence Id
+
*** Keywords ***
Check resource existence
Set Headers {"Accept":"${ACCEPT}"}
diff --git a/SOL002/VNFLifecycleManagement-API/NotificationEndpoint.robot b/SOL002/VNFLifecycleManagement-API/NotificationEndpoint.robot
index 7c0e2f45ec4dd55f7f2b206bd5ddf77ce5371cf9..7bdd35070b6a03e91966bce108e00674080db435 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] v3.6.1
+ ... Reference: Clause 5.4.20.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.20.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.20.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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 903ffe32eb5e5e3c34709d90b680ba03aab08a53..3ae386405c71240c1a7cba5582a76430380d49a5 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] v3.6.1
+ ... Reference: Clause 5.4.20.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.20.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.20.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.18.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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 9884938c7c6ed8e80d2829e74210fd3f374afc08..efe08bea36bf39080581f9262e605fb96f10886f 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] v3.6.1
+ ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.10.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.10.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.10.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.10.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.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 de935f8693543efb697f8b49c29ce942946fc1e9..9230870040cd35ace79e321d9f08765914b332ff 100644
--- a/SOL002/VNFLifecycleManagement-API/RetryOperationTask.robot
+++ b/SOL002/VNFLifecycleManagement-API/RetryOperationTask.robot
@@ -14,7 +14,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 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] v3.6.1
+ ... Reference: Clause 5.4.14.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.14.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.14.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.14.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.14.3 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.14.4 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.14.5 - ETSI GS NFV-SOL 002 [2] v4.3.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 ce0a03d1672eb533af3a2f87b8c2d34b14f5b1b2..73da877d38b60dd3947ddd922fdd7cfdc6f64e5f 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] v3.6.1
+ ... Reference: Clause 5.4.22.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.22.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.22.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.22.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.22.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.22.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.22.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.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 ee9edb681b7ff6401dc7eb43427857128851afeb..d2bb879ad4df51e9d38dd059d0d2a79709dfab82 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] v3.6.1
+ ... Reference: Clause 5.4.15.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.15.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.15.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.15.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.15.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.15.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.15.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.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 e3fb2019db1078e7d076d6ca61df4057db262119..683870071adee0b8789c223afe28b1c1fe082424 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] v3.6.1
+ ... Reference: Clause 5.4.5.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.5.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.5.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.5.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.5.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.5.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.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 fad982596807013906318eeb4991892f430d44be..5ec9c25575b5a2b2af5aca46ff55cb619af678b3 100644
--- a/SOL002/VNFLifecycleManagement-API/ScaleVNFToLevelTask.robot
+++ b/SOL002/VNFLifecycleManagement-API/ScaleVNFToLevelTask.robot
@@ -7,29 +7,30 @@ Library JSONLibrary
Library JSONSchemaLibrary schemas/
*** Test Cases ***
-POST Scale a vnfInstance to level
+POST Scale a vnfInstance to level with Attribute instantiationLevelId
[Documentation] Test ID: 6.3.5.5.1
- ... Test title: POST Scale a vnfInstance to level
+ ... 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] v3.6.1
+ ... Reference: Clause 5.4.6.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
- POST Scale vnfInstance to level
+ POST Scale vnfInstance to level with instantiationLevelId
Check HTTP Response Status Code Is 202
Check Operation Occurrence Id
+
POST Scale a vnfInstance to level Conflict (Not-Instantiated)
[Documentation] Test ID: 6.3.5.5.2
... 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] v3.6.1
+ ... Reference: Clause 5.4.6.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
- POST Scale vnfInstance to level
+ POST Scale vnfInstance to level with instantiationLevelId
Check HTTP Response Status Code Is 409
Check HTTP Response Body Json Schema Is ProblemDetails
@@ -38,11 +39,11 @@ 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] v3.6.1
+ ... Reference: Clause 5.4.6.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
- POST Scale vnfInstance to level
+ POST Scale vnfInstance to level with instantiationLevelId
Check HTTP Response Status Code Is 404
Check HTTP Response Body Json Schema Is ProblemDetails
@@ -51,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] v3.6.1
+ ... Reference: Clause 5.4.6.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -63,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] v3.6.1
+ ... Reference: Clause 5.4.6.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -75,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] v3.6.1
+ ... Reference: Clause 5.4.6.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -87,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] v3.6.1
+ ... Reference: Clause 5.4.6.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.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 390a3bcaf05db005452f2d6d75ddeb56d44b388a..2078763ebb4f838c69c069cbe1cec5b2c4f57624 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] v3.6.1
+ ... Reference: Clause 5.4.18.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.18.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.18.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.18.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.18.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.18.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.18.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.18.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.18.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.18.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.18.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.18.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.18.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: check that resources are not deleted
@@ -182,7 +182,7 @@ POST Create a new Subscription - Unprocessable Entity
... 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.
... re-conditions: none
- ... Reference: Clause 5.4.18.3.1 - ETSI GS NFV-SOL 002 [2] v3.6.1
+ ... Reference: Clause 5.4.18.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.18.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.18.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VE
... Applicability:
... Post-Conditions:
diff --git a/SOL002/VNFLifecycleManagement-API/TerminateVNFTask.robot b/SOL002/VNFLifecycleManagement-API/TerminateVNFTask.robot
index 552adc6f0675554a018726b43e13a4912ff5bdb3..a1187ba166aece8273f1396c48a1b7f5f929feeb 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] v3.6.1
+ ... Reference: Clause 5.4.8.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.8.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.8.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.8.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.8.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.8.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.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 75dc9dd97bb7ab1cd1f90da1a40c11852ff18289..4e7410f82dbb204e972489d9be695f922b2ddb30 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] v3.6.1
+ ... Reference: Clause 5.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.2.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.2.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.2.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
@@ -167,7 +167,7 @@ POST Create a new vnfInstance - UNPROCESSIBLE ENTITY
... Test title: POST Create a new vnfInstance - UNPROCESSIBLE ENTITY
... 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] v3.6.1
+ ... Reference: Clause 5.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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 39b62f0ddea7a2f6fab22afc62001817571e2aeb..c57ae45ad8b0b5f01812db4324c48dc7c609ee1f 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] v3.6.1
+ ... Reference: Clause 5.4.23.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.23.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.23.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.23.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: VNF instance not deleted
diff --git a/SOL002/VNFLifecycleManagement-API/VnfLcmOperationKeywords.robot b/SOL002/VNFLifecycleManagement-API/VnfLcmOperationKeywords.robot
index a3cb7f143b44ef80c5120b38c0f224a77cd438e1..00134fa763281edd4009ea3e50b42dd1ce222957 100644
--- a/SOL002/VNFLifecycleManagement-API/VnfLcmOperationKeywords.robot
+++ b/SOL002/VNFLifecycleManagement-API/VnfLcmOperationKeywords.robot
@@ -86,6 +86,13 @@ Check HTTP Response Header Contains
[Arguments] ${CONTENT_TYPE}
Should Contain ${response['headers']} ${CONTENT_TYPE}
Log Header is present
+
+Check HTTP Response Header Contains ETag and Last-Modified
+ Pass Execution If ${HEADER_TEST_SUPPORTED} == 0 Headers testing not supported. Skipping the Test.
+ Log ${response['headers']}
+ Should Contain ${response['headers']} ETag
+ Should Contain ${response['headers']} Last-Modified
+ Log ETag and Last-Modified header are present
POST Create a new vnfInstance
Log Create VNF instance by POST to ${apiRoot}/${apiName}/${apiMajorVersion}/vnf_instances
@@ -339,7 +346,7 @@ PATCH individual vnfInstance
Set Headers {"If-Match": "${original_etag}"}
Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"${AUTHORIZATION_HEADER}":"${AUTHORIZATION_TOKEN}"}
#Run Keyword If ${check_descriptors} == 1 Add VNF Descriptor Content to VNF Instance
- ${body}= Get File jsons/patchBodyRequest.json
+ ${body}= Get File jsons/VnfInfoModificationRequest.json
#${body}= Format String ${template} vnfdId=${descriptor_id}
Patch ${apiRoot}/${apiName}/${apiMajorVersion}/vnf_instances/${vnfInstanceId} ${body}
${outputResponse}= Output response
@@ -414,14 +421,13 @@ DELETE individual VNF Snapshot - CONFLICT
Patch ${apiRoot}/${apiName}/${apiMajorVersion}/vnf_snapshots/${vnfSnapshotInfoId_InUse}
${outputResponse}= Output response
Set Global Variable ${response} ${outputResponse}
-
-POST instantiate individual vnfInstance
+POST instantiate individual vnfInstance
Log Trying to Instantiate a vnf Instance
Set Headers {"Accept":"${ACCEPT}"}
Set Headers {"Content-Type": "${CONTENT_TYPE}"}
Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"${AUTHORIZATION_HEADER}":"${AUTHORIZATION_TOKEN}"}
${template}= Get File jsons/instantiateVnfRequest.json
- ${body}= Format String ${template} flavourId=${flavourId}
+ ${body}= Format String ${template} flavourId=${flavourId}
Post ${apiRoot}/${apiName}/${apiMajorVersion}/vnf_instances/${vnfInstanceId}/instantiate ${body}
${outputResponse}= Output response
Set Global Variable ${response} ${outputResponse}
@@ -522,16 +528,17 @@ DELETE Scale vnfInstance
${outputResponse}= Output response
Set Global Variable ${response} ${outputResponse}
-POST Scale vnfInstance to level
+POST Scale vnfInstance to level with instantiationLevelId
Log Trying to scale a vnf Instance to level
Set Headers {"Accept":"${ACCEPT}"}
Set Headers {"Content-Type": "${CONTENT_TYPE}"}
Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"${AUTHORIZATION_HEADER}":"${AUTHORIZATION_TOKEN}"}
- ${template}= Get File jsons/scaleVnfToLevelRequest.json
- ${body}= Format String ${template} newFlavourId=${newFlavourId}
+ ${template}= Get File jsons/scaleVnfToLevelRequestWithinstantiationLevelId.json
+ ${body}= Format String ${template} instantiationLevelId=${instantiationLevelId}
Post ${apiRoot}/${apiName}/${apiMajorVersion}/vnf_instances/${vnfInstanceId}/scale_to_level ${body}
${outputResponse}= Output response
Set Global Variable ${response} ${outputResponse}
+
GET Scale vnfInstance to level
log Trying to perform a GET. This method should not be implemented
Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"${AUTHORIZATION_HEADER}":"${AUTHORIZATION_TOKEN}"}
@@ -681,7 +688,8 @@ POST Change External VNF Connectivity
Set Headers {"Accept":"${ACCEPT}"}
Set Headers {"Content-Type": "${CONTENT_TYPE}"}
Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"${AUTHORIZATION_HEADER}":"${AUTHORIZATION_TOKEN}"}
- ${body}= Get File jsons/changeExtVnfConnectivityRequest.json
+ ${template}= Get File jsons/changeExtVnfConnectivityRequest.json
+ ${body}= Format String ${template} CPD_IDs=${CPD_IDs}
Post ${apiRoot}/${apiName}/${apiMajorVersion}/vnf_instances/${vnfInstanceId}/change_ext_conn ${body}
${outputResponse}= Output response
Set Global Variable ${response} ${outputResponse}
@@ -1626,3 +1634,25 @@ Match the VNF LCM Operation Occurence Response Attributes with Descriptors
List Should Contain Value ${VDU_IDs} ${response['body']['resourceChanges']['affectedVnfcs'][0]['vduId']}
List Should Contain value ${Storage_IDs} ${response['body']['resourceChanges']['affectedVirtualStorages'][0]['virtualStorageDescId']}
List Should Contain Value ${VirtualLink_IDs} ${response['body']['resourceChanges']['affectedVirtualLinks'][0]['vnfVirtualLinkDescId']}
+
+POST Instantiate individual vnfInstance with instantiationLevelId
+ Log Trying to Instantiate a vnf Instance with instantiationLevelId
+ Set Headers {"Accept":"${ACCEPT}"}
+ Set Headers {"Content-Type": "${CONTENT_TYPE}"}
+ Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"${AUTHORIZATION_HEADER}":"${AUTHORIZATION_TOKEN}"}
+ ${template}= Get File jsons/instantiateVnfRequestWithInstantiationLevelId.json
+ ${body}= Format String ${template} flavourId=${flavourId} instantiationLevelId=${instantiationLevelId}
+ Post ${apiRoot}/${apiName}/${apiMajorVersion}/vnf_instances/${vnfInstanceId}/instantiate ${body}
+ ${outputResponse}= Output response
+ Set Global Variable ${response} ${outputResponse}
+
+POST instantiate individual vnfInstance with targetScaleLevelId
+ Log Trying to Instantiate a vnf Instance with targetScaleLevelId
+ Set Headers {"Accept":"${ACCEPT}"}
+ Set Headers {"Content-Type": "${CONTENT_TYPE}"}
+ Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"${AUTHORIZATION_HEADER}":"${AUTHORIZATION_TOKEN}"}
+ ${template}= Get File jsons/instantiateVnfRequestWithTargetScaleLevelInfo.json
+ ${body}= Format String ${template} flavourId=${flavourId} scaleVnfRequestAspect=${scaleVnfRequestAspect}
+ Post ${apiRoot}/${apiName}/${apiMajorVersion}/vnf_instances/${vnfInstanceId}/instantiate ${body}
+ ${outputResponse}= Output response
+ Set Global Variable ${response} ${outputResponse}
\ No newline at end of file
diff --git a/SOL002/VNFLifecycleManagement-API/VnfLcmOperationOccurences.robot b/SOL002/VNFLifecycleManagement-API/VnfLcmOperationOccurences.robot
index 7948b8580b03b217f8d9c481f7e4067ba69d1fd5..18bb9b59c7580fcc2e437024739aed2194fe3460 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] v3.6.1
+ ... Reference: Clause 5.4.12.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.12.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.12.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.12.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VE
... Applicability: none
... Post-Conditions: none
diff --git a/SOL002/VNFLifecycleManagement-API/environment/variables.txt b/SOL002/VNFLifecycleManagement-API/environment/variables.txt
index efe6c5b3788f0f49c3b612d0b3ff1482bdc405f7..ea2072dc4447c89614a6c23a214595b018d32240 100644
--- a/SOL002/VNFLifecycleManagement-API/environment/variables.txt
+++ b/SOL002/VNFLifecycleManagement-API/environment/variables.txt
@@ -15,6 +15,9 @@ ${apiName} vnflcm
${apiMajorVersion} v2
${AUTH_USAGE} 1
+
+${HEADER_TEST_SUPPORTED} 0
+
${vnfInstanceId} 6fc3539c-e602-4afa-8e13-962fb5a7d81f
${vnfInstanceId_NoSnapshotTask} vnfInstanceIdForWhichSnapshotResourceDoesNotExist
${vnfInstanceId_NOT_INSTANTIATED} vnfResourceIsInNOT_INSTANTIATEDstate
@@ -63,6 +66,7 @@ ${flavourId} vnf flavour
${scaleVnfRequesttype} SCALE_OUT
${scaleVnfRequestAspect} Aspect
+${instantiationLevelId}
${newFlavourId} 5a7d81f-e602-4afa-8e13-962fb5a7d81f
@@ -94,6 +98,7 @@ ${VDU_IDs}
${Storage_IDs}
${internalCP_IDs}
${externalCP_IDs}
+${CPD_IDs}
${InstantiationLevel_IDs}
${Descriptor_ID}
diff --git a/SOL002/VNFLifecycleManagement-API/jsons/patchBodyRequest.json b/SOL002/VNFLifecycleManagement-API/jsons/VnfInfoModificationRequest.json
similarity index 100%
rename from SOL002/VNFLifecycleManagement-API/jsons/patchBodyRequest.json
rename to SOL002/VNFLifecycleManagement-API/jsons/VnfInfoModificationRequest.json
diff --git a/SOL002/VNFLifecycleManagement-API/jsons/changeExtVnfConnectivityRequest.json b/SOL002/VNFLifecycleManagement-API/jsons/changeExtVnfConnectivityRequest.json
index d9dd498d69010f6bd9fe14558e90ce8d09149048..03ba12d490fc084f10152645ff675e0fd3a4464c 100644
--- a/SOL002/VNFLifecycleManagement-API/jsons/changeExtVnfConnectivityRequest.json
+++ b/SOL002/VNFLifecycleManagement-API/jsons/changeExtVnfConnectivityRequest.json
@@ -1,11 +1,21 @@
-{
- "extVirtualLinks": [
- {
- "id": "",
- "vimConnectionId": "",
- "resourceProviderId": "",
- "resourceId": ""
- }
- ],
- "additionalParams": {}
-}
\ No newline at end of file
+{{
+ "extVirtualLinks": [
+ {
+ "id": "",
+ "vimConnectionId": "",
+ "resourceProviderId": "",
+ "resourceId": "",
+ "extCps": [
+ {
+ "cpdId": "{CPD_IDs}",
+ "cpConfig": [
+ {
+ "linkPortId": ""
+ }
+ ]
+ }
+ ]
+ }
+ ],
+ "additionalParams": {}
+}}
\ No newline at end of file
diff --git a/SOL002/VNFLifecycleManagement-API/jsons/instantiateVnfRequest.json b/SOL002/VNFLifecycleManagement-API/jsons/instantiateVnfRequest.json
index eaf4f76fc5cb2e65d0543749829c2501ccd43f54..a89dab190c604d1bd8f989c0f0abf1ea49f03316 100644
--- a/SOL002/VNFLifecycleManagement-API/jsons/instantiateVnfRequest.json
+++ b/SOL002/VNFLifecycleManagement-API/jsons/instantiateVnfRequest.json
@@ -1,4 +1,4 @@
{{
- "flavourId": "{flavourId}",
- "instantiationLevelId": ""
-}}
+ "flavourId": "{flavourId}"
+ }}
+
\ No newline at end of file
diff --git a/SOL002/VNFLifecycleManagement-API/jsons/instantiateVnfRequestWithInstantiationLevelId.json b/SOL002/VNFLifecycleManagement-API/jsons/instantiateVnfRequestWithInstantiationLevelId.json
new file mode 100644
index 0000000000000000000000000000000000000000..6bd23edf54c4394849a11343f8ff680793e2f52a
--- /dev/null
+++ b/SOL002/VNFLifecycleManagement-API/jsons/instantiateVnfRequestWithInstantiationLevelId.json
@@ -0,0 +1,4 @@
+{{
+ "flavourId": "{flavourId}",
+ "instantiationLevelId": "{instantiationLevelId}"
+}}
diff --git a/SOL002/VNFLifecycleManagement-API/jsons/instantiateVnfRequestWithTargetScaleLevelInfo.json b/SOL002/VNFLifecycleManagement-API/jsons/instantiateVnfRequestWithTargetScaleLevelInfo.json
new file mode 100644
index 0000000000000000000000000000000000000000..b94b5ed435c4046f945592890146185d727171fe
--- /dev/null
+++ b/SOL002/VNFLifecycleManagement-API/jsons/instantiateVnfRequestWithTargetScaleLevelInfo.json
@@ -0,0 +1,9 @@
+{{
+ "flavourId": "{flavourId}",
+ "targetScaleLevelInfo": [
+ {
+ "aspectId": "{scaleVnfRequestAspect}",
+ "scaleLevel": 2
+ }
+ ]
+ }}
\ No newline at end of file
diff --git a/SOL002/VNFLifecycleManagement-API/jsons/scaleVnfToLevelRequest.json b/SOL002/VNFLifecycleManagement-API/jsons/scaleVnfToLevelRequest.json
deleted file mode 100644
index 448dc4c275e80759dc2a3bb6b39821765f3f9a18..0000000000000000000000000000000000000000
--- a/SOL002/VNFLifecycleManagement-API/jsons/scaleVnfToLevelRequest.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{{
- "newFlavourId" : "{newFlavourId}"
-}}
\ No newline at end of file
diff --git a/SOL002/VNFLifecycleManagement-API/jsons/scaleVnfToLevelRequestWithinstantiationLevelId.json b/SOL002/VNFLifecycleManagement-API/jsons/scaleVnfToLevelRequestWithinstantiationLevelId.json
new file mode 100644
index 0000000000000000000000000000000000000000..b200d5844d081b63e9c11495e5a7844639495d33
--- /dev/null
+++ b/SOL002/VNFLifecycleManagement-API/jsons/scaleVnfToLevelRequestWithinstantiationLevelId.json
@@ -0,0 +1,4 @@
+{{
+ "instantiationLevelId": "{instantiationLevelId}",
+ "additionalParams": {}
+}}
\ No newline at end of file
diff --git a/SOL002/VNFLifecycleManagement-API/schemas/VnfIdentifierDeletionNotification.schema.json b/SOL002/VNFLifecycleManagement-API/schemas/VnfIdentifierDeletionNotification.schema.json
index 253ccce96b2de34faba43dd5093c2a3ab9e561ef..a1d381763111b2d19df6100eab546a9a51b4531b 100644
--- a/SOL002/VNFLifecycleManagement-API/schemas/VnfIdentifierDeletionNotification.schema.json
+++ b/SOL002/VNFLifecycleManagement-API/schemas/VnfIdentifierDeletionNotification.schema.json
@@ -1,87 +1,87 @@
{
- "description": "This type represents a VNF identifier deletion notification, which informs the receiver of the deletion of a new \"Individual VNF instance\" resource and the associated VNF instance identifier. This notification shall be triggered by the VNFM when it has deleted an \"Individual VNF instance\" resource and the associated VNF instance identifier.\n",
+ "description": "This type represents a VNF identifier deletion notification, which informs the receiver of the deletion of a new \"Individual VNF instance\" resource and the associated VNF instance identifier. This notification shall be triggered by the VNFM when it has deleted an \"Individual VNF instance\" resource and the associated VNF instance identifier.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "notificationType",
+ "subscriptionId",
+ "timeStamp",
+ "vnfInstanceId",
+ "_links"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "notificationType": {
+ "description": "Discriminator for the different notification types. Shall be set to \"VnfIdentifierDeletionNotification\" for this notification type.\n",
+ "type": "string",
+ "enum": [
+ "VnfIdentifierDeletionNotification"
+ ]
+ },
+ "subscriptionId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "timeStamp": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "vnfInstanceId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "_links": {
+ "description": "This type represents the links to resources that a notification can contain.\n",
"type": "object",
"required": [
- "id",
- "notificationType",
- "subscriptionId",
- "timeStamp",
- "vnfInstanceId",
- "_links"
+ "vnfInstance",
+ "subscription"
],
"properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "notificationType": {
- "description": "Discriminator for the different notification types. Shall be set to \"VnfIdentifierDeletionNotification\" for this notification type.\n",
- "type": "string",
- "enum": [
- "VnfIdentifierDeletionNotification"
- ]
- },
- "subscriptionId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "timeStamp": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
+ "vnfInstance": {
+ "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": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ }
+ }
},
- "vnfInstanceId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
+ "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": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ }
+ }
},
- "_links": {
- "description": "This type represents the links to resources that a notification can contain.\n",
+ "vnfLcmOpOcc": {
+ "description": "This type represents a link to a resource in a notification, using an absolute or relative URI.\n",
"type": "object",
"required": [
- "vnfInstance",
- "subscription"
+ "href"
],
"properties": {
- "vnfInstance": {
- "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": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- }
- }
- },
- "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": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- }
- }
- },
- "vnfLcmOpOcc": {
- "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": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- }
- }
+ "href": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
}
}
}
}
- }
\ No newline at end of file
+ }
+ }
+}
\ No newline at end of file
diff --git a/SOL002/VNFLifecycleManagement-API/schemas/VnfLcmOperationOccurrenceNotification.schema.json b/SOL002/VNFLifecycleManagement-API/schemas/VnfLcmOperationOccurrenceNotification.schema.json
index 8065ae213f600f571a603bc504efa81e5eb8764a..d5e28f6deb68735e6d86f2c21fa01121016d7f21 100644
--- a/SOL002/VNFLifecycleManagement-API/schemas/VnfLcmOperationOccurrenceNotification.schema.json
+++ b/SOL002/VNFLifecycleManagement-API/schemas/VnfLcmOperationOccurrenceNotification.schema.json
@@ -1,889 +1,1211 @@
{
- "description": "This type represents a VNF lifecycle management operation occurrence notification, which informs the receiver of changes in the VNF lifecycle caused by a VNF LCM operation occurrence. The support of the notification is mandatory. This notification shall be triggered by the VNFM when there is a change in the VNF lifecycle caused by a VNF LCM operation occurrence, including: * Instantiation of the VNF * Scaling of the VNF instance (including auto-scaling) * Healing of the VNF instance (including auto-healing) * Change of the state of the VNF instance (i.e. Operate VNF) * Change of the deployment flavour of the VNF instance * Change of the external connectivity of the VNF instance * Termination of the VNF instance * Modification of VNF instance information and/or VNF configurable\n properties through the \"PATCH\" method on the \"Individual VNF instance\"\n resource.\nIf this is the initial notification about the start of a VNF LCM operation occurrence, it is assumed that the notification is sent by the VNFM before any action (including sending the grant request) is taken as part of the LCM operation. Due to possible race conditions, the \"start\" notification, the grant request and the LCM operation acknowledgment can arrive in any order at the NFVO, and the NFVO shall be able to handle such a situation. If this is a notification about a final or intermediate result state of a VNF LCM operation occurrence, the notification shall be sent after all related actions of the LCM operation that led to this state have been executed. The new state shall be set in the \"Individual VNF LCM operation occurrence\" resource before the notification about the state change is sent. * NOTE 1:\tShall be present if the \"notificationStatus\" is set to \"RESULT\", the \"verbosity\" attribute is set\n to \"FULL\" and the operation has performed any resource modification. Shall be absent otherwise.\n This attribute contains information about the cumulative changes to virtualised resources that\n were performed so far by the VNF LCM operation occurrence and by any of the error handling\n procedures for that operation occurrence.\n NOTE 2:\tFor a particular affected VL, there shall be as many \"AffectedVirtualLink\" entries as needed\n for signalling the different types of changes, i.e. one per virtual link and change type.\n For instance, in the case of signaling affected VL instances involving the addition of a particular\n VL instance with links ports, one \"AffectedVirtualLink\" entry signals the addition of the VL by using\n the \"changeType\" attribute of \"AffectedVirtualLink\" structure equal to \"ADDED\", and another\n \"AffectedVirtualLink\" entry signals the addition of VNF link ports of the VL by using the\n \"changeType\" equal to \"LINK_PORT_ADDED\".\n",
+ "description": "This type represents a VNF lifecycle management operation occurrence notification, which informs the receiver of changes in the VNF lifecycle caused by a VNF LCM operation occurrence. The support of the notification is mandatory. This notification shall be triggered by the VNFM when there is a change in the VNF lifecycle caused by a VNF LCM operation occurrence, including: * Instantiation of the VNF * Scaling of the VNF instance (including auto-scaling) * Healing of the VNF instance (including auto-healing) * Change of the state of the VNF instance (i.e. Operate VNF) * Change of the deployment flavour of the VNF instance * Change of the external connectivity of the VNF instance * Termination of the VNF instance * Modification of VNF instance information and/or VNF configurable\n properties through the \"PATCH\" method on the \"Individual VNF instance\"\n resource.\nIf this is the initial notification about the start of a VNF LCM operation occurrence, it is assumed that the notification is sent by the VNFM before any action (including sending the grant request) is taken as part of the LCM operation. Due to possible race conditions, the \"start\" notification, the grant request and the LCM operation acknowledgment can arrive in any order at the NFVO, and the NFVO shall be able to handle such a situation. If this is a notification about a final or intermediate result state of a VNF LCM operation occurrence, the notification shall be sent after all related actions of the LCM operation that led to this state have been executed. The new state shall be set in the \"Individual VNF LCM operation occurrence\" resource before the notification about the state change is sent. * NOTE 1:\tShall be present if the \"notificationStatus\" is set to \"RESULT\", the \"verbosity\" attribute is set\n to \"FULL\" and the operation has performed any resource modification. Shall be absent otherwise.\n This attribute contains information about the cumulative changes to virtualised resources that\n were performed so far by the VNF LCM operation occurrence and by any of the error handling\n procedures for that operation occurrence.\n NOTE 2:\tFor a particular affected VL, there shall be as many \"AffectedVirtualLink\" entries as needed\n for signalling the different types of changes, i.e. one per virtual link and change type.\n For instance, in the case of signalling affected VL instances involving the addition of a particular\n VL instance with links ports, one \"AffectedVirtualLink\" entry signals the addition of the VL by using\n the \"changeType\" attribute of \"AffectedVirtualLink\" structure equal to \"ADDED\", and another\n \"AffectedVirtualLink\" entry signals the addition of VNF link ports of the VL by using the\n \"changeType\" equal to \"LINK_PORT_ADDED\".\n NOTE 3: Not more than one of changedInfo and modificationsTriggeredByVnfPkgChange shall be present.\n",
"type": "object",
"required": [
- "id",
- "notificationType",
- "subscriptionId",
- "timeStamp",
- "notificationStatus",
- "operationState",
- "vnfInstanceId",
- "operation",
- "isAutomaticInvocation",
- "vnfLcmOpOccId",
- "_links"
+ "id",
+ "notificationType",
+ "subscriptionId",
+ "timeStamp",
+ "notificationStatus",
+ "operationState",
+ "vnfInstanceId",
+ "operation",
+ "isAutomaticInvocation",
+ "vnfLcmOpOccId",
+ "_links"
],
"properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "notificationType": {
- "description": "Discriminator for the different notification types. Shall be set to \"VnfLcmOperationOccurrenceNotification\" for this notification type.\n",
- "type": "string",
- "enum": [
- "VnfLcmOperationOccurrenceNotification"
- ]
- },
- "subscriptionId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "timeStamp": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "notificationStatus": {
- "description": "Indicates whether this notification reports about the start of a lifecycle operation or the result of a lifecycle operation. Permitted values: * START: Informs about the start of the VNF LCM operation\n occurrence.\n* RESULT: Informs about the final or intermediate result of the VNF\n LCM operation occurrence.\n",
- "type": "string",
- "enum": [
- "START",
- "RESULT"
- ]
- },
- "operationState": {
- "description": "STARTING: The LCM operation is starting. PROCESSING: The LCM operation is currently in execution. COMPLETED: The LCM operation has been completed successfully. FAILED_TEMP: The LCM operation has failed and execution has stopped, but the execution of the operation is not considered to be closed. FAILED: The LCM operation has failed and it cannot be retried or rolled back, as it is determined that such action won't succeed. ROLLING_BACK: The LCM operation is currently being rolled back. ROLLED_BACK: The LCM operation has been successfully rolled back, i.e. The state of the VNF prior to the original operation invocation has been restored as closely as possible.\n",
- "type": "string",
- "enum": [
- "STARTING",
- "PROCESSING",
- "COMPLETED",
- "FAILED_TEMP",
- "FAILED",
- "ROLLING_BACK",
- "ROLLED_BACK"
- ]
- },
- "vnfInstanceId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "operation": {
- "description": "The enumeration LcmOpType defines the permitted values to represent VNF lifecycle operation types in VNF lifecycle management operation occurrence resources and VNF lifecycle management operation occurrence notifications. It shall comply with the provisions defined in table 5.5.4.5-1.\nValue | Description ------|------------ INSTANTIATE | Represents the \"Instantiate VNF\" LCM operation. SCALE | Represents the \"Scale VNF\" LCM operation. SCALE_TO_LEVEL | Represents the \"Scale VNF to Level\" LCM operation. CHANGE_FLAVOUR | Represents the \"Change VNF Flavour\" LCM operation. TERMINATE | Represents the \"Terminate VNF\" LCM operation. HEAL | Represents the \"Heal VNF\" LCM operation. OPERATE | Represents the \"Operate VNF\" LCM operation. CHANGE_EXT_CONN | Represents the \"Change external VNF connectivity\" LCM operation. MODIFY_INFO | Represents the \"Modify VNF Information\" LCM operation. CREATE_SNAPSHOT | Represents the \"Create VNF Snapshot\" LCM operation. REVERT_TO_SNAPSHOT | Represents the ΓÇ£Revert-To VNF Snapshot\" LCM operation. CHANGE_VNFPKG | Represents the \"Change current VNF package\" LCM operation.\n",
- "type": "string",
- "enum": [
- "INSTANTIATE",
- "SCALE",
- "SCALE_TO_LEVEL",
- "CHANGE_FLAVOUR",
- "TERMINATE",
- "HEAL",
- "OPERATE",
- "CHANGE_EXT_CONN",
- "MODIFY_INFO",
- "CREATE_SNAPSHOT",
- "REVERT_TO_SNAPSHOT",
- "CHANGE_VNFPKG"
- ]
- },
- "isAutomaticInvocation": {
- "description": "Set to true if this VNF LCM operation occurrence has been triggered by an automated procedure inside the VNFM (i.e. ScaleVnf / ScaleVnfToLevel triggered by auto-scale, or HealVnf triggered by auto-heal). Set to false otherwise.\n",
- "type": "boolean"
- },
- "verbosity": {
- "description": "The enumeration LcmOpOccNotificationVerbosityType provides values to control the verbosity of LCM operation occurrence notifications. * 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"
- ]
- },
- "vnfLcmOpOccId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "affectedVnfcs": {
- "description": "Information about VNFC 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 VNFCs.\n",
- "type": "object",
- "required": [
- "id",
- "vduId",
- "changeType",
- "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"
- },
- "vduId": {
- "description": "An identifier that is unique within a VNF descriptor.\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: * ADDED * REMOVED * MODIFIED * TEMPORARY For a temporary resource, an AffectedVnfc structure exists as long as the temporary resource exists.\n",
- "type": "string",
- "enum": [
- "ADDED",
- "REMOVED",
- "MODIFIED",
- "TEMPORARY"
- ]
- },
- "computeResource": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\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 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"
- },
- "affectedVnfcCpIds": {
- "description": "Identifiers of CP(s) of the VNFC instance that were affected by the change. Shall be present for those affected CPs of the VNFC instance that are associated to an external CP of the VNF instance. May be present for further affected CPs of the VNFC instance.\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"
- }
- },
- "addedStorageResourceIds": {
- "description": "References to VirtualStorage resources that have been added. Each value refers to a VirtualStorageResourceInfo item in the VnfInstance that was added to the VNFC. It shall be provided if at least one storage resource was added to the VNFC.\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"
- }
- },
- "removedStorageResourceIds": {
- "description": "References to VirtualStorage resources that have been removed. The value contains the identifier of a VirtualStorageResourceInfo item that has been removed from the VNFC, and might no longer exist in the VnfInstance. It shall be provided if at least one storage resource was removed from the VNFC.\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"
- }
- }
- }
- }
- },
- "affectedVirtualLinks": {
- "description": "Information about VL instances that were affected during the lifecycle operation. See note 1 and note 2.\n",
- "type": "array",
- "items": {
- "description": "This type provides information about added, deleted, modified and temporary VLs, and added or removed VNF link ports.\nNOTE:\tWhen signalling the addition (LINK_PORT_ADDED) or removal (LINK_PORT_REMOVED) of VNF link ports, \n the \"networkResource\" attribute refers to the affected virtual link instance, not the link port \n instance. The resource handles of the affected VNF link ports can be found by dereferencing the \n identifiers in the \"vnfLinkPortIds\" attribute.\n",
- "type": "object",
- "required": [
- "id",
- "vnfVirtualLinkDescId",
- "changeType",
- "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"
- },
- "vnfVirtualLinkDescId": {
- "description": "An identifier that is unique within a VNF descriptor.\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: * ADDED * REMOVED * MODIFIED * TEMPORARY * LINK_PORT_ADDED * LINK_PORT_REMOVED For a temporary resource, an AffectedVirtualLink structure exists as long as the temporary resource exists. When signalling the addition (LINK_PORT_ADDED) or removal (LINK_PORT_REMOVED) of VNF link ports, the \"networkResource\" attribute refers to the affected virtual link instance, not the link port instance. The resource handles of the affected VNF link ports can be found by dereferencing the identifiers in the \"vnfLinkPortIds\" attribute.\n",
- "type": "string",
- "enum": [
- "ADDED",
- "REMOVED",
- "MODIFIED",
- "TEMPORARY",
- "LINK_PORT_ADDED",
- "LINK_PORT_REMOVED"
- ]
- },
- "networkResource": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
- "type": "string"
- }
- }
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "notificationType": {
+ "description": "Discriminator for the different notification types. Shall be set to \"VnfLcmOperationOccurrenceNotification\" for this notification type.\n",
+ "type": "string",
+ "enum": [
+ "VnfLcmOperationOccurrenceNotification"
+ ]
+ },
+ "subscriptionId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "timeStamp": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "notificationStatus": {
+ "description": "Indicates whether this notification reports about the start of a lifecycle operation or the result of a lifecycle operation. Permitted values: * START: Informs about the start of the VNF LCM operation\n occurrence.\n* RESULT: Informs about the final or intermediate result of the VNF\n LCM operation occurrence.\n",
+ "type": "string",
+ "enum": [
+ "START",
+ "RESULT"
+ ]
+ },
+ "operationState": {
+ "description": "STARTING: The LCM operation is starting. PROCESSING: The LCM operation is currently in execution. COMPLETED: The LCM operation has been completed successfully. FAILED_TEMP: The LCM operation has failed and execution has stopped, but the execution of the operation is not considered to be closed. FAILED: The LCM operation has failed and it cannot be retried or rolled back, as it is determined that such action won't succeed. ROLLING_BACK: The LCM operation is currently being rolled back. ROLLED_BACK: The LCM operation has been successfully rolled back, i.e. The state of the VNF prior to the original operation invocation has been restored as closely as possible.\n",
+ "type": "string",
+ "enum": [
+ "STARTING",
+ "PROCESSING",
+ "COMPLETED",
+ "FAILED_TEMP",
+ "FAILED",
+ "ROLLING_BACK",
+ "ROLLED_BACK"
+ ]
+ },
+ "vnfInstanceId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "operation": {
+ "description": "The enumeration LcmOpType defines the permitted values to represent VNF lifecycle operation types in VNF lifecycle management operation occurrence resources and VNF lifecycle management operation occurrence notifications.\nValue | Description ------|------------ INSTANTIATE | Represents the \"Instantiate VNF\" LCM operation. SCALE | Represents the \"Scale VNF\" LCM operation. SCALE_TO_LEVEL | Represents the \"Scale VNF to Level\" LCM operation. CHANGE_FLAVOUR | Represents the \"Change VNF Flavour\" LCM operation. TERMINATE | Represents the \"Terminate VNF\" LCM operation. HEAL | Represents the \"Heal VNF\" LCM operation. OPERATE | Represents the \"Operate VNF\" LCM operation. CHANGE_EXT_CONN | Represents the \"Change external VNF connectivity\" LCM operation. MODIFY_INFO | Represents the \"Modify VNF Information\" LCM operation. CREATE_SNAPSHOT | Represents the \"Create VNF Snapshot\" LCM operation. REVERT_TO_SNAPSHOT | Represents the ΓÇ£Revert-To VNF Snapshot\" LCM operation. CHANGE_VNFPKG | Represents the \"Change current VNF package\" LCM operation.\n",
+ "type": "string",
+ "enum": [
+ "INSTANTIATE",
+ "SCALE",
+ "SCALE_TO_LEVEL",
+ "CHANGE_FLAVOUR",
+ "TERMINATE",
+ "HEAL",
+ "OPERATE",
+ "CHANGE_EXT_CONN",
+ "MODIFY_INFO",
+ "CREATE_SNAPSHOT",
+ "REVERT_TO_SNAPSHOT",
+ "CHANGE_VNFPKG"
+ ]
+ },
+ "isAutomaticInvocation": {
+ "description": "Set to true if this VNF LCM operation occurrence has been triggered by an automated procedure inside the VNFM (i.e. ScaleVnf / ScaleVnfToLevel triggered by auto-scale, or HealVnf triggered by auto-heal). Set to false otherwise.\n",
+ "type": "boolean"
+ },
+ "verbosity": {
+ "description": "The enumeration LcmOpOccNotificationVerbosityType provides values to control the verbosity of LCM operation occurrence notifications. * 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"
+ ]
+ },
+ "vnfLcmOpOccId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "affectedVnfcs": {
+ "description": "Information about VNFC 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 VNFCs.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "vduId",
+ "changeType",
+ "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"
+ },
+ "vduId": {
+ "description": "An identifier that is unique within a VNF descriptor.\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: * ADDED * REMOVED * MODIFIED * TEMPORARY For a temporary resource, an AffectedVnfc structure exists as long as the temporary resource exists.\n",
+ "type": "string",
+ "enum": [
+ "ADDED",
+ "REMOVED",
+ "MODIFIED",
+ "TEMPORARY"
+ ]
+ },
+ "computeResource": {
+ "required": [
+ "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",
+ "properties": {
+ "vimConnectionId": {
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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"
},
- "vnfLinkPortIds": {
- "description": "Identifiers of the link ports of the affected VL related to the change. Each identifier references a \"VnfLinkPortInfo\" structure.\nShall be set when changeType is equal to \"LINK_PORT_ADDED\" or \"LINK_PORT_REMOVED\", and the related \"VnfLinkPortInfo\" structures are present (case \"added\") or have been present (case \"removed\") in the \"VnfVirtualLinkResourceInfo\" or \"ExtManagedVirtualLinkInfo\" structures that are represented by the \"vnfVirtualLinkResourceInfo\" or \"extManagedVirtualLinkInfo\" attribute in the \"VnfInstance\" structure. See note.\n",
- "type": "array",
- "items": {
- "description": "An identifier that is unique within a VNF descriptor.\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"
},
- "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 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"
+ "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 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"
}
+ }
+ },
+ "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"
}
+ }
+ },
+ "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 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"
+ },
+ "affectedVnfcCpIds": {
+ "description": "Identifiers of CP(s) of the VNFC instance that were affected by the change. Shall be present for those affected CPs of the VNFC instance that are associated to an external CP of the VNF instance. May be present for further affected CPs of the VNFC instance.\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"
+ }
+ },
+ "addedStorageResourceIds": {
+ "description": "References to VirtualStorage resources that have been added. Each value refers to a VirtualStorageResourceInfo item in the VnfInstance that was added to the VNFC. It shall be provided if at least one storage resource was added to the VNFC.\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"
+ }
+ },
+ "removedStorageResourceIds": {
+ "description": "References to VirtualStorage resources that have been removed. The value contains the identifier of a VirtualStorageResourceInfo item that has been removed from the VNFC, and might no longer exist in the VnfInstance. It shall be provided if at least one storage resource was removed from the VNFC.\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"
+ }
}
- },
- "affectedExtLinkPorts": {
- "description": "Information about external VNF link ports that were affected during the lifecycle operation. See note 1.\n",
- "type": "array",
- "items": {
- "description": "This type provides information about added and deleted external link ports (link ports attached to external virtual links).\n",
- "type": "object",
- "required": [
- "id",
- "changeType",
- "extCpInstanceId",
- "resourceHandle"
- ],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "changeType": {
- "description": "Signals the type of change. Permitted values: -\tADDED -\tREMOVED\n",
- "type": "string",
- "enum": [
- "ADDED",
- "REMOVED"
- ]
+ }
+ }
+ },
+ "affectedVirtualLinks": {
+ "description": "Information about VL instances that were affected during the lifecycle operation. See note 1 and note 2.\n",
+ "type": "array",
+ "items": {
+ "description": "This type provides information about added, deleted, modified and temporary VLs, and added or removed VNF link ports.\nNOTE:\tWhen signalling the addition (LINK_PORT_ADDED) or removal (LINK_PORT_REMOVED) of VNF link ports, \n the \"networkResource\" attribute refers to the affected virtual link instance, not the link port \n instance. The resource handles of the affected VNF link ports can be found by dereferencing the \n identifiers in the \"vnfLinkPortIds\" attribute.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "vnfVirtualLinkDescId",
+ "changeType",
+ "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"
+ },
+ "vnfVirtualLinkDescId": {
+ "description": "An identifier that is unique within a VNF descriptor.\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: * ADDED * REMOVED * MODIFIED * TEMPORARY * LINK_PORT_ADDED * LINK_PORT_REMOVED For a temporary resource, an AffectedVirtualLink structure exists as long as the temporary resource exists. When signalling the addition (LINK_PORT_ADDED) or removal (LINK_PORT_REMOVED) of VNF link ports, the \"networkResource\" attribute refers to the affected virtual link instance, not the link port instance. The resource handles of the affected VNF link ports can be found by dereferencing the identifiers in the \"vnfLinkPortIds\" attribute.\n",
+ "type": "string",
+ "enum": [
+ "ADDED",
+ "REMOVED",
+ "MODIFIED",
+ "TEMPORARY",
+ "LINK_PORT_ADDED",
+ "LINK_PORT_REMOVED"
+ ]
+ },
+ "networkResource": {
+ "required": [
+ "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",
+ "properties": {
+ "vimConnectionId": {
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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"
},
- "extCpInstanceId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be 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"
},
- "resourceHandle": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\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 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"
}
+ }
+ },
+ "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"
}
+ }
+ },
+ "vnfLinkPortIds": {
+ "description": "Identifiers of the link ports of the affected VL related to the change. Each identifier references a \"VnfLinkPortInfo\" structure.\nShall be set when changeType is equal to \"LINK_PORT_ADDED\" or \"LINK_PORT_REMOVED\", and the related \"VnfLinkPortInfo\" structures are present (case \"added\") or have been present (case \"removed\") in the \"VnfVirtualLinkResourceInfo\" or \"ExtManagedVirtualLinkInfo\" structures that are represented by the \"vnfVirtualLinkResourceInfo\" or \"extManagedVirtualLinkInfo\" attribute in the \"VnfInstance\" structure. See note.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier that is unique within a VNF descriptor.\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 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"
}
- },
- "affectedVirtualStorages": {
- "description": "Information about virtualised storage 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 virtual storage resources.\n",
- "type": "object",
- "required": [
- "id",
- "virtualStorageDescId",
- "changeType",
- "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": "An identifier that is unique within a VNF descriptor.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
+ }
+ }
+ },
+ "affectedExtLinkPorts": {
+ "description": "Information about external VNF link ports that were affected during the lifecycle operation. See note 1.\n",
+ "type": "array",
+ "items": {
+ "description": "This type provides information about added and deleted external link ports (link ports attached to external virtual links).\n",
+ "type": "object",
+ "required": [
+ "id",
+ "changeType",
+ "extCpInstanceId",
+ "resourceHandle"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "changeType": {
+ "description": "Signals the type of change. Permitted values: -\tADDED - MODIFIED -\tREMOVED\n",
+ "type": "string",
+ "enum": [
+ "ADDED",
+ "MODIFIED",
+ "REMOVED"
+ ]
+ },
+ "extCpInstanceId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "resourceHandle": {
+ "required": [
+ "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",
+ "properties": {
+ "vimConnectionId": {
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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"
},
- "changeType": {
- "description": "Signals the type of change. Permitted values: * ADDED * REMOVED * MODIFIED * TEMPORARY For a temporary resource, an AffectedVirtualStorage structure exists as long as the temporary resource exists.\n",
- "type": "string",
- "enum": [
- "ADDED",
- "REMOVED",
- "MODIFIED",
- "TEMPORARY"
- ]
+ "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"
},
- "storageResource": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\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 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"
+ "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 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"
}
+ }
+ },
+ "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"
}
+ }
}
- },
- "changedInfo": {
- "description": "This type represents attribute modifications that were performed on an \"Individual VNF instance\" resource. The attributes that can be included consist of those requested to be modified explicitly in the \"VnfInfoModificationRequest\" data structure, and additional attributes of the \"VnfInstance\" data structure that were modified implicitly e.g. when modifying the referenced VNF package. * NOTE:\tIf present, this attribute (which depends on the value of the \"vnfdId\" attribute)\n was modified implicitly following a request to modify the \"vnfdId\" attribute, by\n copying the value of this attribute from the VNFD in the VNF Package identified\n by the \"vnfdId\" attribute.\n",
- "type": "object",
- "properties": {
- "vnfInstanceName": {
- "description": "If present, this attribute signals modifications of the \"vnfInstanceName\" attribute in \"VnfInstance\" as defined in clause 5.5.2.12..\n",
- "type": "string"
+ }
+ }
+ },
+ "affectedVirtualStorages": {
+ "description": "Information about virtualised storage 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 virtual storage resources.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "virtualStorageDescId",
+ "changeType",
+ "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": "An identifier that is unique within a VNF descriptor.\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: * ADDED * REMOVED * MODIFIED * TEMPORARY For a temporary resource, an AffectedVirtualStorage structure exists as long as the temporary resource exists.\n",
+ "type": "string",
+ "enum": [
+ "ADDED",
+ "REMOVED",
+ "MODIFIED",
+ "TEMPORARY"
+ ]
+ },
+ "storageResource": {
+ "required": [
+ "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",
+ "properties": {
+ "vimConnectionId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
},
- "vnfInstanceDescription": {
- "description": "If present, this attribute signals modifications of the \"vnfInstanceDescription\" attribute in \"VnfInstance\", as defined in clause 5.5.2.12..\n",
- "type": "string"
+ "resourceProviderId": {
+ "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 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"
+ "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.\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 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"
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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 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"
+ "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.\n* NOTE: At 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 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"
+ }
+ }
},
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\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"
+ }
+ }
+ },
+ "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 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"
+ }
+ }
+ }
+ },
+ "changedInfo": {
+ "description": "This type represents attribute modifications that were performed on an \"Individual VNF instance\" resource. The attributes that can be included consist of those requested to be modified explicitly in the \"VnfInfoModificationRequest\" data structure, and additional attributes of the \"VnfInstance\" data structure that were modified implicitly e.g. when modifying the referenced VNF package. * NOTE:\tIf present, this attribute (which depends on the value of the \"vnfdId\" attribute)\n was modified implicitly following a request to modify the \"vnfdId\" attribute, by\n copying the value of this attribute from the VNFD in the VNF Package identified\n by the \"vnfdId\" attribute.\n",
+ "type": "object",
+ "properties": {
+ "vnfInstanceName": {
+ "description": "If present, this attribute signals modifications of the \"vnfInstanceName\" attribute in \"VnfInstance\" as defined in clause 5.5.2.12..\n",
+ "type": "string"
+ },
+ "vnfInstanceDescription": {
+ "description": "If present, this attribute signals modifications of the \"vnfInstanceDescription\" attribute in \"VnfInstance\", as defined in clause 5.5.2.12..\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 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"
+ },
+ "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 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"
+ },
+ "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 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"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfProvider": {
+ "description": "If present, this attribute signals modifications of the \"vnfProvider\" attribute in \"VnfInstance\". See note.\n",
+ "type": "string"
+ },
+ "vnfProductName": {
+ "description": "If present, this attribute signals modifications of the \"vnfProductName\" attribute in \"VnfInstance\". See note.\n",
+ "type": "string"
+ },
+ "vnfSoftwareVersion": {
+ "description": "A version.\n",
+ "type": "string"
+ },
+ "vnfdVersion": {
+ "description": "A version.\n",
+ "type": "string"
+ },
+ "vnfcInfoModifications": {
+ "description": "If present, this attribute signals modifications of certain entries in the \"vnfcInfo\" attribute array in the \"instantiatedVnfInfo\" attribute of \"VnfInstance\", as defined in clause 5.5.2.12.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents modifications of an entry in an array of \"VnfcInfo\" objects. * NOTE:\tThe attribute \"id\" in this data type represents the same identifier as the attribute\n \"vnfcInstanceId\" in other related data types in the present document. For reasons of backward\n compatibility, this misalignment is not corrected.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "vnfcConfigurableProperties"
+ ],
+ "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"
},
- "vnfProvider": {
- "description": "If present, this attribute signals modifications of the \"vnfProvider\" attribute in \"VnfInstance\". See note.\n",
- "type": "string"
+ "vnfcConfigurableProperties": {
+ "description": "This 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"
+ }
+ }
+ }
+ }
+ }
+ },
+ "affectedVipCps": {
+ "description": "Information about virtual IP CP instances that were affected during the execution of the lifecycle management operation, if this notification represents the result of a lifecycle management operation occurrence. Shall be present if the \"notificationStatus\" is set to \"RESULT\", the \"verbosity\" attribute is set to \"FULL\" and the operation has made any changes to the Virtual IP CP instances of the VNF instance. Shall be absent otherwise. Only information about virtual IP CP instances that have been added, deleted or modified shall be provided.\n",
+ "type": "array",
+ "items": {
+ "description": "This type provides information about added, deleted and modified virtual IP CP instances.\n",
+ "type": "object",
+ "required": [
+ "cpInstanceId",
+ "cpdId",
+ "changeType"
+ ],
+ "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": "An identifier that is unique within a VNF descriptor.\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: -\tADDED -\tREMOVED -\tMODIFIED\n",
+ "type": "string",
+ "enum": [
+ "ADDED",
+ "REMOVED",
+ "MODIFIED"
+ ]
+ }
+ }
+ }
+ },
+ "affectedVirtualCps": {
+ "description": "Information about virtual CP instances that were affected during the execution of the lifecycle management operation, if this notification represents the result of a lifecycle management operation occurrence.\nShall be present if the \"notificationStatus\" is set to \"RESULT\", the \"verbosity\" attribute is set to \"FULL\" and the operation has made any changes to the virtual CP instances of the VNF instance. Shall be absent otherwise. Only information about virtual CP instances that have been added, deleted or modified shall be provided.\n",
+ "type": "array",
+ "items": {
+ "description": "This type provides information about added, deleted and modified virtual CP instances.\n",
+ "type": "object",
+ "required": [
+ "cpInstanceId",
+ "cpdId",
+ "changeType"
+ ],
+ "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": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "changeType": {
+ "description": "Signals the type of change.\nPermitted values:\n - ADDED\n - REMOVED\n - MODIFIED\n",
+ "type": "string",
+ "enum": [
+ "ADDED",
+ "REMOVED",
+ "MODIFIED"
+ ]
+ }
+ }
+ }
+ },
+ "changedExtConnectivity": {
+ "description": "Information about changed external connectivity, if this notification represents the result of a lifecycle operation occurrence. Shall be present if the \"notificationStatus\" is set to \"RESULT\" and the \"operation\" has made any change of the external connectivity of the VNF instance. Shall be absent otherwise.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents information about an external VL.\nNOTE:\tThis attribute reflects the current configuration information that has resulted from merging into this attribute \n the \"VnfExtCpData\" information which was passed as part of the \"ExtVirtualLinkData\" structure in the input of the \n most recent VNF LCM operation such as \"InstantiateVnfRequest\", \"ChangeExtVnfConnectivityRequest\", \"ChangeVnfFlavourRequest\" \n or \"ChangeCurrentVnfPkgRequest\", or in the Grant response. If applying such change results in an empty list of \n \"currentVnfExtCpData\" structure instances, the affected instance of \"ExtVirtualLinkInfo\" shall be removed from its \n parent data structure.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "resourceHandle",
+ "currentVnfExtCpData"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceHandle": {
+ "required": [
+ "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",
+ "properties": {
+ "vimConnectionId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
},
- "vnfProductName": {
- "description": "If present, this attribute signals modifications of the \"vnfProductName\" attribute in \"VnfInstance\". See note.\n",
- "type": "string"
+ "resourceProviderId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
},
- "vnfSoftwareVersion": {
- "description": "A version.\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.\n",
+ "type": "string"
},
- "vnfdVersion": {
- "description": "A version.\n",
- "type": "string"
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\n",
+ "type": "string"
},
- "vnfcInfoModifications": {
- "description": "If present, this attribute signals modifications of certain entries in the \"vnfcInfo\" attribute array in the \"instantiatedVnfInfo\" attribute of \"VnfInstance\", as defined in clause 5.5.2.12.\n",
- "type": "array",
- "items": {
- "description": "This type represents modifications of an entry in an array of \"VnfcInfo\" objects. * NOTE:\tThe attribute \"id\" in this data type represents the same identifier as the attribute\n \"vnfcInstanceId\" in other related data types in the present document. For reasons of backward\n compatibility, this misalignment is not corrected.\n",
- "type": "object",
- "required": [
- "id",
- "vnfcConfigurableProperties"
- ],
- "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"
- },
- "vnfcConfigurableProperties": {
- "description": "This 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"
- }
- }
+ "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.\n* NOTE: At 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 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"
}
+ }
+ },
+ "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"
}
- }
- },
- "affectedVipCps": {
- "description": "Information about virtual IP CP instances that were affected during the execution of the lifecycle management operation, if this notification represents the result of a lifecycle management operation occurrence. Shall be present if the \"notificationStatus\" is set to \"RESULT\", the \"verbosity\" attribute is set to \"FULL\" and the operation has made any changes to the VIP CP instances of the VNF instance. Shall be absent otherwise. Only information about VIP CP instances that have been added, deleted or modified shall be provided.\n",
- "type": "array",
- "items": {
- "description": "This type provides information about added, deleted and modified virtual IP CP instances.\n",
+ }
+ },
+ "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.\nNOTE 1:\tThe use cases UC#4 and UC#5 in clause A.4 of ETSI GS NFV-IFA 007 provide examples for such a configuration. NOTE 2:\tThe value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\" attribute.\n",
"type": "object",
"required": [
- "cpInstanceId",
- "cpdId",
- "changeType"
+ "id",
+ "resourceHandle"
],
"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": "An identifier that is unique within a VNF descriptor.\n",
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceHandle": {
+ "required": [
+ "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",
+ "properties": {
+ "vimConnectionId": {
+ "description": "An identifier with the intention of being globally unique.\n",
"type": "string"
- },
- "vnfdId": {
+ },
+ "resourceProviderId": {
"description": "An identifier with the intention of being globally unique.\n",
"type": "string"
- },
- "changeType": {
- "description": "Signals the type of change. Permitted values: -\tADDED -\tREMOVED -\tMODIFIED\n",
- "type": "string",
- "enum": [
- "ADDED",
- "REMOVED",
- "MODIFIED"
- ]
+ },
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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 the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "type": "string"
+ }
}
- }
- },
- "changedExtConnectivity": {
- "description": "Information about changed external connectivity, if this notification represents the result of a lifecycle operation occurrence. Shall be present if the \"notificationStatus\" is set to \"RESULT\" and the \"operation\" has made any change of the external connectivity of the VNF instance. Shall be absent otherwise.\n",
- "type": "array",
- "items": {
- "description": "This type represents information about an external VL. It shall comply with the provisions defined in table 5.5.3.2-1.\nNOTE:\tThis attribute reflects the current configuration information that has resulted from merging into this attribute \n the \"VnfExtCpData\" information which was passed as part of the \"ExtVirtualLinkData\" structure in the input of the \n most recent VNF LCM operation such as \"InstantiateVnfRequest\", \"ChangeExtVnfConnectivityRequest\", \"ChangeVnfFlavourRequest\" \n or \"ChangeCurrentVnfPkgRequest\", or in the Grant response. If applying such change results in an empty list of \n \"currentVnfExtCpData\" structure instances, the affected instance of \"ExtVirtualLinkInfo\" shall be removed from its \n parent data structure.\n",
+ }
+ },
+ "currentVnfExtCpData": {
+ "description": "Allows the API consumer to read the current CP configuration information for the connection of external CPs to the external virtual link. See note.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents configuration information for external CPs created. * NOTE 1: \tIn case this identifier refers to a CPD with trunking enabled, the external CP instances created\n from this CPD will represent ports in a trunk.\n* NOTE 2: \tWithin one VNF instance, all VNFC instances created from a particular VDU have the same external\n connectivity. Thus, given a particular value of the \"cpdId\" attribute, there shall be one\n \"cpConfig\" entry for each VNFC instance that has been or can be created from a VDU which includes\n a CPD identified by the \"cpdId\" attribute. If the cpConfig represents a subport in a trunk,\n all \"cpConfig\" entries in this list shall have the same segmentationId, which means they are\n connected to the same set of external VLs via the trunk.\n* NOTE 3: \tThe map entry value shall be set to \"null\" in order to delete a \"VnfExtCpConfig\" entry identified\n by a particular key value from the map, i.e. for the disconnection of an existing external\n CP instance addressed by cpInstanceId in the deleted map entry from a particular external\n virtual link, and deletion of that instance in case it represents a subport. Deleting the\n last key from the map removes the affected instance of the \"VnfExtCpData\" structure from\n its parent data structure.\n* NOTE 4: If, as defined by the input parameters of a \"ChangeVnfFlavour\", \"ChangeExtVnfConnectivity\" or\n \"ChangeCurrentVnfPkg\" operation, a cpConfig map entry identified by a particular map key value \n is moved into another \"ExtVirtualLinkData\" or \"VnfExtCpData\" structure, this particular cpConfig\n map entry may be used by an external CP instance different than the one that has used it before the\n operation, or by no external CP instance at all. Renaming a CPD identifier during the \"changeCurrentVnfPkg\"\n operation does not count as moving the related \"cpConfig\" map entries to a new \"extCpData\" structure.\n",
"type": "object",
"required": [
- "id",
- "resourceHandle",
- "currentVnfExtCpData"
+ "cpdId"
],
"properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceHandle": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
- "type": "string"
- }
+ "cpdId": {
+ "description": "An identifier that is unique within a VNF descriptor.\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 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",
+ "anyOf": [
+ {
+ "required": [
+ "linkPortId"
+ ]
+ },
+ {
+ "required": [
+ "cpProtocolData"
+ ]
+ },
+ {
+ "required": [
+ "netAttDefResourceId"
+ ]
}
- },
- "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. It shall comply with the provisions defined in table 5.5.3.9-1.\nNOTE 1:\tThe 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:\tThe value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\" attribute.\n",
+ ],
+ "type": "object",
+ "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 to the VNFM the need to create a dedicated link port for the external CP. If set to True, the VNFM shall create a link port. If set to False, the VNFM shall not create a link port. 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 2.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents network protocol data. * NOTE:\tThis attribute allows to signal the addition of further types of layer and protocol\n in future versions of the present document in a backwards-compatible way. In the current\n version of the present document, only IP over Ethernet is supported.\n",
"type": "object",
"required": [
- "id",
- "resourceHandle"
+ "layerProtocol"
],
"properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceHandle": {
+ "layerProtocol": {
+ "description": "Identifier of layer(s) and protocol(s). 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 network address data for IP over Ethernet. * NOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. * NOTE 2:\tExactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present. * NOTE 3:\tIf the CP instance represents a subport in a trunk, segmentationId shall be present.\n Otherwise it shall not be present.\n* NOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the actual\n network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header\n of the packets or it may be an identifier used between the application and the NFVI networking\n infrastructure to identify the network sub-interface of the trunk port in question. In the latter\n case the NFVI infrastructure will map this local segmentationId to whatever segmentationId is\n actually used by the NFVI's transport technology.\n",
+ "type": "object",
+ "anyOf": [
+ {
"required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
+ "macAddress"
+ ]
+ },
+ {
+ "required": [
+ "ipAddresses"
+ ]
+ }
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "fixedAddresses"
+ ]
+ },
+ {
+ "required": [
+ "numDynamicAddresses"
+ ]
+ },
+ {
+ "required": [
+ "ipAddressRange"
+ ]
+ }
+ ],
+ "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: -\tVLAN: the subport uses VLAN as encapsulation type. -\tINHERIT: the subport gets its segmentation type from the network itΓÇÖs 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"
+ ],
+ "properties": {
+ "type": {
+ "description": "The type of the IP addresses. Permitted values: IPV4, IPV6.\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
},
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
+ "fixedAddresses": {
+ "description": "Fixed addresses to assign (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"
+ }
},
- "resourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\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"
},
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\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.\n",
- "type": "string"
- }
- }
- }
- },
- "currentVnfExtCpData": {
- "description": "Allows the API consumer to read the current CP configuration information for the connection of external CPs to the external virtual link. See note.\n",
- "type": "array",
- "items": {
- "description": "This type represents configuration information for external CPs created. * NOTE 1: \tIn case this identifier refers to a CPD with trunking enabled, the external CP instances created\n from this CPD will represent ports in a trunk.\n* NOTE 2: \tWithin one VNF instance, all VNFC instances created from a particular VDU have the same external\n connectivity. Thus, given a particular value of the \"cpdId\" attribute, there shall be one\n \"cpConfig\" entry for each VNFC instance that has been or can be created from a VDU which includes\n a CPD identified by the \"cpdId\" attribute. If the cpConfig represents a subport in a trunk,\n all \"cpConfig\" entries in this list shall have the same segmentationId, which means they are\n connected to the same set of external VLs via the trunk.\n* NOTE 3: \tThe map entry value shall be set to \"null\" in order to delete a \"VnfExtCpConfig\" entry identified\n by a particular key value from the map, i.e. for the disconnection of an existing external\n CP instance addressed by cpInstanceId in the deleted map entry from a particular external\n virtual link, and deletion of that instance in case it represents a subport. Deleting the\n last key from the map removes the affected instance of the \"VnfExtCpData\" structure from\n its parent data structure.\n",
- "type": "object",
- "required": [
- "cpdId"
- ],
- "properties": {
- "cpdId": {
- "description": "An identifier that is unique within a VNF descriptor.\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 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). See note 2 and note 3.\n",
- "type": "object",
- "additionalProperties": {
- "description": "This type represents an externally provided link port or network address information per instance of an external connection point. In case a link port is provided, the VNFM shall use that link port when connecting the external CP to the external VL. In a link port is not provided, the VNFM shall create a link port on the external VL, and use that link port to connect the external CP to the external VL. * NOTE: The following conditions apply to the attributes \"linkPortId\" and \"cpProtocolData\":\n 1) Void.\n 2) At least one of the \"linkPortId\" and \"cpProtocolData\" attributes shall be present for an external\n CP instance representing a subport that is to be created, or an external CP instance that is to be\n created by creating the corresponding VNFC or VNF instance during the current or a subsequent LCM\n operation, or for an existing external CP instance that is to be re-configured or added to a\n 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\n a pre created link port, and the VNFM can use means outside the scope of the present document to obtain\n the pre-configured address information for the connection point from the resource representing\n the link port.\n 5) If both \"cpProtocolData\" and \"linkportId\" are provided, the API consumer shall ensure that the\n cpProtocolData can be used with the pre-created link port referenced by \"linkPortId\".\n",
- "anyOf": [{
- "required": [
- "linkPortId"
- ]
+ "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. 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"
},
- {
- "required": [
- "cpProtocolData"
- ]
- }
- ],
- "type": "object",
- "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 to the VNFM the need to create a dedicated link port for the external CP. If set to True, the VNFM shall create a link port. If set to False, the VNFM shall not create a link port. 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 note.\n",
- "type": "array",
- "items": {
- "description": "This type represents network protocol data. * NOTE:\tThis attribute allows to signal the addition of further types of layer and protocol\n in future versions of the present document in a backwards-compatible way. In the current\n 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). See note.\n",
- "type": "string",
- "enum": [
- "IP_OVER_ETHERNET"
- ]
- },
- "ipOverEthernet": {
- "description": "This type represents network address data for IP over Ethernet. * NOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. * NOTE 2:\tExactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present. * NOTE 3:\tIf the CP instance represents a subport in a trunk, segmentationId shall be present.\n Otherwise it shall not be present.\n* NOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the actual\n network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header\n of the packets or it may be an identifier used between the application and the NFVI networking\n infrastructure to identify the network sub-interface of the trunk port in question. In the latter\n case the NFVI infrastructure will map this local segmentationId to whatever segmentationId is\n actually used by the NFVIΓÇÖs transport technology.\n",
- "type": "object",
- "anyOf": [{
- "required": [
- "macAddress"
- ]
- },
- {
- "required": [
- "ipAddresses"
- ]
- }
- ],
- "oneOf": [{
- "required": [
- "fixedAddresses"
- ]
- },
- {
- "required": [
- "numDynamicAddresses"
- ]
- },
- {
- "required": [
- "ipAddressRange"
- ]
- }
- ],
- "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: -\tVLAN: the subport uses VLAN as encapsulation type. -\tINHERIT: the subport gets its segmentation type from the network itΓÇÖs 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"
- ],
- "properties": {
- "type": {
- "description": "The type of the IP addresses. Permitted values: IPV4, IPV6.\n",
- "type": "string",
- "enum": [
- "IPV4",
- "IPV6"
- ]
- },
- "fixedAddresses": {
- "description": "Fixed addresses to assign (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"
- }
- },
- "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. 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 other resource provider. It is expected to be unique within the VIM instance.\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.\n",
+ "type": "string"
}
+ }
}
+ }
}
+ },
+ "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",
+ "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"
+ }
+ }
+ }
}
+ }
+ },
+ "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 2, 3 and 4.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
}
+ }
}
+ }
}
- }
- },
- "modificationsTriggeredByVnfPkgChange": {
- "description": "This type represents attribute modifications that were performed on an \"Individual VNF instance\" resource when changing the current VNF package. The attributes that can be included consist of those requested to be modified explicitly in the \"ChangeCurrentVnfPkgRequest\" data structure, and additional attributes of the \"VnfInstance\" data structure that were modified implicitly during the operation. The \"ModificationsTriggeredByVnfPkgChange\" data type shall comply with the provisions defined in table 5.5.3.21-1.\nNOTE 1:\tThis attribute represents the delta (semantics as per IETF RFC 7396, JSON Merge Patch) between the value \n of the attribute at the start of the \"Change current VNF package\" operation and the value of the attribute \n at its completion.\nNOTE 2:\tIf present, this attribute (which depends on the value of the \"vnfdId\" attribute) was modified implicitly \n during the related operation and contains a copy of the value of the related attribute from the VNFD in the \n VNF Package identified by the \"vnfdId\" attribute.\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 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"
- },
- "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 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"
- },
- "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 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"
- },
- "vnfdId": {
+ }
+ },
+ "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 contains 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": {
+ "required": [
+ "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",
+ "properties": {
+ "vimConnectionId": {
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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 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 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"
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ },
+ "modificationsTriggeredByVnfPkgChange": {
+ "description": "This type represents attribute modifications that were performed on an \"Individual VNF instance\" resource when changing the current VNF package. The attributes that can be included consist of those requested to be modified explicitly in the \"ChangeCurrentVnfPkgRequest\" data structure, and additional attributes of the \"VnfInstance\" data structure that were modified implicitly during the operation.\nNOTE 1:\tThis attribute represents the delta (semantics as per IETF RFC 7396, JSON Merge Patch) between the value \n of the attribute at the start of the \"Change current VNF package\" operation and the value of the attribute \n at its completion.\nNOTE 2:\tIf present, this attribute (which depends on the value of the \"vnfdId\" attribute) was modified implicitly \n during the related operation and contains a copy of the value of the related attribute from the VNFD in the \n VNF Package identified by the \"vnfdId\" attribute.\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 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"
+ },
+ "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 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"
+ },
+ "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 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"
+ },
+ "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\". See note 2.\n",
+ "type": "string"
+ },
+ "vnfProductName": {
+ "description": "If present, this attribute signals the new value of the \"vnfProductName\" attribute in \"VnfInstance\". See note 2.\n",
+ "type": "string"
+ },
+ "vnfSoftwareVersion": {
+ "description": "A version.\n",
+ "type": "string"
+ },
+ "vnfdVersion": {
+ "description": "A version.\n",
+ "type": "string"
+ },
+ "vimConnectionInfo": {
+ "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-relate dparameters 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",
+ "type": "object",
+ "required": [
+ "vimType"
+ ],
+ "properties": {
+ "vimId": {
+ "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\". See note 2.\n",
- "type": "string"
+ "vimType": {
+ "description": "Discriminator for the different types of the VIM information. The value of this attribute determines the structure of the \"interfaceInfo\" and \"accessInfo\" attributes, based on the type of the VIM., CISM, CIR or MCIOP repository. The set of permitted values is expected to change over time as new types or versions of VIMs become available. The ETSI NFV registry of VIM-related information [i.3] provides access to information about VimConnectionInfo definitions for various VIM, CISM, CIR or MCIOP repository types. The structure of the registry is defined in annex C.\n",
+ "type": "string"
},
- "vnfProductName": {
- "description": "If present, this attribute signals the new value of the \"vnfProductName\" attribute in \"VnfInstance\". See note 2.\n",
- "type": "string"
+ "interfaceInfo": {
+ "description": "This 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"
},
- "vnfSoftwareVersion": {
- "description": "A version.\n",
- "type": "string"
+ "accessInfo": {
+ "description": "This 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"
},
- "vnfdVersion": {
- "description": "A version.\n",
- "type": "string"
+ "extra": {
+ "description": "This 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"
}
+ }
}
- },
- "error": {
- "description": "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 is reproduced inthis structure. Compared to the general framework defined in IETF RFC 7807, 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 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.\n",
+ }
+ }
+ },
+ "error": {
+ "description": "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 is reproduced inthis structure. Compared to the general framework defined in IETF RFC 7807, 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 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.\n",
+ "type": "object",
+ "required": [
+ "status",
+ "detail"
+ ],
+ "properties": {
+ "type": {
+ "description": "A URI reference according to IETF RFC 3986 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"
+ }
+ }
+ },
+ "_links": {
+ "description": "This type represents the links to resources that a notification can contain.\n",
+ "type": "object",
+ "required": [
+ "vnfInstance",
+ "subscription"
+ ],
+ "properties": {
+ "vnfInstance": {
+ "description": "This type represents a link to a resource in a notification, using an absolute or relative URI.\n",
"type": "object",
"required": [
- "status",
- "detail"
+ "href"
],
"properties": {
- "type": {
- "description": "A URI reference according to IETF RFC 3986 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": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ }
}
- },
- "_links": {
- "description": "This type represents the links to resources that a notification can contain.\n",
+ },
+ "subscription": {
+ "description": "This type represents a link to a resource in a notification, using an absolute or relative URI.\n",
"type": "object",
"required": [
- "vnfInstance",
- "subscription"
+ "href"
],
"properties": {
- "vnfInstance": {
- "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": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- }
- }
- },
- "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": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- }
- }
- },
- "vnfLcmOpOcc": {
- "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": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- }
- }
- }
+ "href": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ }
+ }
+ },
+ "vnfLcmOpOcc": {
+ "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": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ }
}
+ }
}
+ }
}
-}
\ No newline at end of file
+ }
\ No newline at end of file
diff --git a/SOL002/VNFLifecycleManagement-API/schemas/VnfSnapshotInfo.schema.json b/SOL002/VNFLifecycleManagement-API/schemas/VnfSnapshotInfo.schema.json
index 287543fd68efda580d938452d5d0814fff26dfb4..54f0bdc98d33894d9b43f2b45bb6806b835a8b53 100644
--- a/SOL002/VNFLifecycleManagement-API/schemas/VnfSnapshotInfo.schema.json
+++ b/SOL002/VNFLifecycleManagement-API/schemas/VnfSnapshotInfo.schema.json
@@ -1,1682 +1,2596 @@
{
- "description": "This type represents a VNF snapshot.\n",
+ "description": "This type represents an individual VNF snapshot resource.\n",
"type": "object",
"required": [
- "id",
- "vnfInstanceId",
- "triggeredAt",
- "vnfdId",
- "vnfInfo",
- "vnfcSnapshots"
+ "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.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "vnfInstanceId",
+ "creationStartedAt",
+ "vnfdId",
+ "vnfInstance",
+ "vnfcSnapshots"
+ ],
+ "properties": {
+ "id": {
"description": "An identifier with the intention of being globally unique.\n",
"type": "string"
- },
- "vnfInstanceId": {
+ },
+ "vnfInstanceId": {
"description": "An identifier with the intention of being globally unique.\n",
"type": "string"
- },
- "creationStartedAt": {
+ },
+ "creationStartedAt": {
"description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
"type": "string",
"format": "date-time"
- },
- "creationFinishedAt": {
+ },
+ "creationFinishedAt": {
"description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
"type": "string",
"format": "date-time"
- },
- "vnfdId": {
+ },
+ "vnfdId": {
"description": "An identifier with the intention of being globally unique.\n",
"type": "string"
- },
- "vnfInstance": {
+ },
+ "vnfInstance": {
"description": "This type represents a VNF instance. * NOTE 1:\tModifying the value of this attribute shall not be performed when conflicts exist\n between the previous and the newly referred VNF package, i.e. when the new VNFD is\n changed with respect to the previous VNFD in other aspects than merely referencing\n to other VNF software images. In order to avoid misalignment of the VnfInstance with\n the current VNF's on-boarded VNF package, the values of attributes in the VnfInstance\n that have corresponding attributes in the VNFD shall be kept in sync with the values in the VNFD.\n* NOTE 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\n applicable to a VNF. Some of these are set prior to instantiation and cannot be modified\n if the VNF is instantiated, some are set prior to instantiation (are part of initial configuration)\n and can be modified later, and others can be set only after instantiation.\n The applicability of certain configuration may depend on the VNF and the required operation of\n the VNF at a certain point in time.\n* NOTE 4:\tUpon creation of the VnfInstance structure, the VNFM shall create and initialize all child\n attributes of \"vnfConfigurableProperties\", \"metadata\" and \"extensions\" that were declared\n in the VNFD with a defined initial value. The defined initial values can be declared in the VNFD,\n and/or, in case of \"metadata\", obtained from the \"CreateVnfRequest\" structure. Child attributes of\n \"vnfConfigurableProperties\", \"metadata\" and \"extensions\" that have no defined initial value shall\n not be created, in order to be consistent with the semantics of the JSON Merge Patch method\n (see IETF RFC 7396) that interprets null values as deletion request.\n* NOTE 5:\tIt is possible to have several ExtManagedVirtualLinkInfo for the same VNF internal VL in case\n of a multi-site VNF spanning several VIMs. The set of ExtManagedVirtualLinkInfo corresponding\n to the same VNF internal VL shall indicate so by referencing to the same VnfVirtualLinkDesc\n and externally-managed multi-site VL instance (refer to clause 5.5.3.5).\n* NOTE 6:\tEven though externally-managed internal VLs are also used for VNF-internal connectivity,\n they shall not be listed in the \"vnfVirtualLinkResourceInfo\" attribute as this would be redundant.\n",
"type": "object",
"required": [
- "id",
- "vnfdId",
- "vnfProvider",
- "vnfProductName",
- "vnfSoftwareVersion",
- "vnfdVersion",
- "instantiationState",
- "_links"
+ "id",
+ "vnfdId",
+ "vnfProvider",
+ "vnfProductName",
+ "vnfSoftwareVersion",
+ "vnfdVersion",
+ "instantiationState",
+ "_links"
],
"properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfInstanceName": {
- "description": "Name of the VNF instance. This attribute can be modified with the PATCH method.\n",
- "type": "string"
- },
- "vnfInstanceDescription": {
- "description": "Human-readable description of the VNF instance. This attribute can be modified with the PATCH method.\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.\n",
- "type": "string"
- },
- "vnfdVersion": {
- "description": "A version.\n",
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfInstanceName": {
+ "description": "Name of the VNF instance. This attribute can be modified with the PATCH method.\n",
+ "type": "string"
+ },
+ "vnfInstanceDescription": {
+ "description": "Human-readable description of the VNF instance. This attribute can be modified with the PATCH method.\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.\n",
+ "type": "string"
+ },
+ "vnfdVersion": {
+ "description": "A version.\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 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"
+ },
+ "instantiationState": {
+ "description": "The instantiation state of the VNF.\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": "An identifier that is unique within a VNF descriptor.\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 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"
- },
- "instantiationState": {
- "description": "The instantiation state of the VNF.\n",
+ },
+ "vnfState": {
+ "description": "STARTED: The VNF instance is up and running. STOPPED: The VNF instance has been shut down.\n",
"type": "string",
"enum": [
- "NOT_INSTANTIATED",
- "INSTANTIATED"
+ "STARTED",
+ "STOPPED"
]
- },
- "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": "An identifier that is unique within a VNF descriptor.\n",
+ },
+ "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. This attribute shall be present if the VNF supports scaling. See clause B.2 for an explanation of VNF scaling.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the scale level of a VNF instance related to a scaling aspect.\n",
+ "type": "object",
+ "required": [
+ "aspectId",
+ "scaleLevel"
+ ],
+ "properties": {
+ "aspectId": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "scaleToLevel": {
+ "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": {
+ "description": "This type represents the scale level of a VNF instance related to a scaling aspect.\n",
+ "type": "object",
+ "required": [
+ "aspectId",
+ "scaleLevel"
+ ],
+ "properties": {
+ "aspectId": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "scaleToLevel": {
+ "description": "An identifier with the intention of being globally unique.\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.\nNOTE 1:\tThe attributes \"associatedVnfcCpId\", \"associatedVipCpId\", \"associatedVirtualCpId\" and \n \"associatedVnfVirtualLinkId\" are mutually exclusive. Exactly one shall be present.\nNOTE 2:\tAn external CP instance is not associated to a link port in the cases indicated for the \n ΓÇ£extLinkPortsΓÇ¥ attribute in clause 4.4.1.11.\nNOTE 3: 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 \n CP, e.g. to build a link redundant mated pair in SR-IOV cases.\nNOTE 4: When more than one netAttDefResourceId is indicated, all shall belong to the same namespace.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "cpdId",
+ "cpConfigId",
+ "cpProtocolInfo"
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "associatedVnfcCpId"
+ ]
+ },
+ {
+ "required": [
+ "associatedVipCpId"
+ ]
+ },
+ {
+ "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": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "cpConfigId": {
+ "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"
+ },
+ "cpProtocolInfo": {
+ "description": "Network protocol information for this CP.\n",
+ "type": "array",
+ "items": {
+ "description": "This type describes the protocol layer(s) that a CP uses together with protocol-related information, like addresses.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the \n present document in a backwards-compatible way. In the current version of the present document, only IP over \n Ethernet is supported.\n",
+ "type": "object",
+ "required": [
+ "layerProtocol"
+ ],
+ "properties": {
+ "layerProtocol": {
+ "description": "The identifier of layer(s) and protocol(s) associated to the network address information.\nPermitted 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:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, segmentationId shall be present. \n Otherwise it shall not be present.\nNOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the \n actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the \n transport header of the packets or it may be an identifier used between the application \n and the NFVI networking infrastructure to identify the network sub-interface of the trunk \n port in question. In the latter case the NFVI infrastructure will map this local segmentationId \n to whatever segmentationId is actually used by the NFVIΓÇÖs transport technology.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "required": [
+ "macAddress"
+ ]
+ },
+ {
+ "required": [
+ "ipAddresses"
+ ]
+ }
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "addresses"
+ ]
+ },
+ {
+ "required": [
+ "addressRange"
+ ]
+ }
+ ],
+ "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 notes 3 and 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"
+ ],
+ "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. 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.\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"
+ },
+ "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 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"
+ },
+ "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 within a VNF descriptor.\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"
+ },
+ "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. It 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 with the intention of being 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.\nMay be present otherwise.\n",
+ "type": "array",
+ "items": {
+ "description": "This type provides information related to virtual IP CP.\nNOTE 1:\tIt is possible that there is no associated VnfcCp because the virtual IP CP is available but not associated yet. NOTE 2: If only the value or the presence of this attribute is changed in the \"VipCpInfo\" structure by an LCM operation occurrence, this does not represent a change that requires including a related \"AffectedVipCp\" structure in the VNF LCM operation occurrence notifications or the \"VnfLcmOpOcc\" structure related to this LCM operation occurrence.\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": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
},
- "vnfState": {
- "description": "STARTED: The VNF instance is up and running. STOPPED: The VNF instance has been shut down.\n",
- "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"
},
- "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. This attribute shall be present if the VNF supports scaling. See clause B.2 for an explanation of VNF scaling.\n",
- "type": "array",
- "items": {
+ "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 uses together with protocol-related information, like addresses.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the \n present document in a backwards-compatible way. In the current version of the present document, only IP over \n Ethernet is supported.\n",
+ "type": "object",
+ "required": [
+ "layerProtocol"
+ ],
+ "properties": {
+ "layerProtocol": {
+ "description": "The identifier of layer(s) and protocol(s) associated to the network address information.\nPermitted 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:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, segmentationId shall be present. \n Otherwise it shall not be present.\nNOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the \n actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the \n transport header of the packets or it may be an identifier used between the application \n and the NFVI networking infrastructure to identify the network sub-interface of the trunk \n port in question. In the latter case the NFVI infrastructure will map this local segmentationId \n to whatever segmentationId is actually used by the NFVIΓÇÖs transport technology.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "required": [
+ "macAddress"
+ ]
+ },
+ {
+ "required": [
+ "ipAddresses"
+ ]
+ }
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "addresses"
+ ]
+ },
+ {
+ "required": [
+ "addressRange"
+ ]
+ }
+ ],
+ "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 notes 3 and 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"
+ ],
+ "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. 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.\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": [
- "aspectId",
- "scaleLevel"
+ "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 virtual IP 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": "This 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"
+ }
+ }
+ }
+ },
+ "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 provides information related to a virtual CP instance of a VNF.\nNOTE: A consumer of the VNF LCM interface can learn the actual VNFC instances implementing the service \n accessible via the virtual CP instance by querying the \"vnfcResourceInfo\" from the \"InstantiatedVnfInfo\" \n and filtering by corresponding \"vduIds\" values.\n",
+ "type": "object",
+ "required": [
+ "cpInstanceId",
+ "cpdId",
+ "resourceHandle",
+ "vduIds"
+ ],
+ "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": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "resourceHandle": {
+ "required": [
+ "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",
+ "properties": {
+ "vimConnectionId": {
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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 uses together with protocol-related information, like addresses.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the \n present document in a backwards-compatible way. In the current version of the present document, only IP over \n Ethernet is supported.\n",
+ "type": "object",
+ "required": [
+ "layerProtocol"
+ ],
+ "properties": {
+ "layerProtocol": {
+ "description": "The identifier of layer(s) and protocol(s) associated to the network address information.\nPermitted 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:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, segmentationId shall be present. \n Otherwise it shall not be present.\nNOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the \n actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the \n transport header of the packets or it may be an identifier used between the application \n and the NFVI networking infrastructure to identify the network sub-interface of the trunk \n port in question. In the latter case the NFVI infrastructure will map this local segmentationId \n to whatever segmentationId is actually used by the NFVIΓÇÖs transport technology.\n",
"type": "object",
+ "anyOf": [
+ {
+ "required": [
+ "macAddress"
+ ]
+ },
+ {
+ "required": [
+ "ipAddresses"
+ ]
+ }
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "addresses"
+ ]
+ },
+ {
+ "required": [
+ "addressRange"
+ ]
+ }
+ ],
"properties": {
- "aspectId": {
- "description": "An identifier that is unique within a VNF descriptor.\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 notes 3 and 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"
+ ],
+ "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. 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.\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"
+ }
+ }
+ }
+ }
+ }
+ },
+ "vduIds": {
+ "description": "Reference to the VDU(s) which implement the service accessible via the virtual CP instance. See note.\n",
+ "type": "array",
+ "minItems": 1,
+ "items": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ }
+ },
+ "additionalServiceInfo": {
+ "description": "Additional service identification information of the virtual CP instance.\n",
+ "type": "array",
+ "items": {
+ "description": "This type provides 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 \n termination within the VNF, such as for example a URL path information in an HTTP request required \n to allow a single virtual CP IP address to be used for several HTTP based services that use the \n same port number.\n",
+ "type": "object",
+ "required": [
+ "portInfo"
+ ],
+ "properties": {
+ "portInfo": {
+ "description": "Service port numbers exposed by the virtual CP instance.\n",
+ "minItems": 1,
+ "type": "array",
+ "items": {
+ "description": "This type describes the service identifying port properties exposed by the virtual CP instance.\n",
+ "type": "object",
+ "required": [
+ "name",
+ "port",
+ "portConfigurable"
+ ],
+ "properties": {
+ "name": {
+ "description": "The name of the port exposed by the virtual CP instance.\n",
+ "type": "string"
},
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
+ "protocol": {
+ "description": "The L4 protocol for this port exposed by the virtual CP instance.\nPermitted values: - TCP - UDP - SCTP\n",
+ "type": "string",
+ "enum": [
+ "TCP",
+ "UDP",
+ "SCTP"
+ ]
},
- "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"
+ "port": {
+ "description": "The L4 port number exposed by the virtual CP instance.\n",
+ "type": "integer"
+ },
+ "portConfigurable": {
+ "description": "The Boolean is a data type having two values (true and false).\n",
+ "type": "boolean"
}
+ }
+ }
+ },
+ "serviceInfo": {
+ "description": "This 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"
+ }
+ }
+ }
+ },
+ "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 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"
+ }
+ }
+ }
+ },
+ "extVirtualLinkInfo": {
+ "description": "Information about the external VLs the VNF instance is connected to.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents information about an external VL.\nNOTE:\tThis attribute reflects the current configuration information that has resulted from merging into this attribute \n the \"VnfExtCpData\" information which was passed as part of the \"ExtVirtualLinkData\" structure in the input of the \n most recent VNF LCM operation such as \"InstantiateVnfRequest\", \"ChangeExtVnfConnectivityRequest\", \"ChangeVnfFlavourRequest\" \n or \"ChangeCurrentVnfPkgRequest\", or in the Grant response. If applying such change results in an empty list of \n \"currentVnfExtCpData\" structure instances, the affected instance of \"ExtVirtualLinkInfo\" shall be removed from its \n parent data structure.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "resourceHandle",
+ "currentVnfExtCpData"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceHandle": {
+ "required": [
+ "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",
+ "properties": {
+ "vimConnectionId": {
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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 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"
}
+ }
+ },
+ "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"
}
+ }
},
- "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": {
+ "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.\nNOTE 1:\tThe use cases UC#4 and UC#5 in clause A.4 of ETSI GS NFV-IFA 007 provide examples for such a configuration. NOTE 2:\tThe 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": {
"required": [
- "aspectId",
- "scaleLevel"
+ "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",
"properties": {
- "aspectId": {
- "description": "An identifier that is unique within a VNF descriptor.\n",
+ "vimConnectionId": {
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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",
+ },
+ "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"
- },
- "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"
+ },
+ "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 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"
+ }
}
+ },
+ "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 the CISM or other resource provider. It is expected to be unique within the VIM instance.\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 5.5.3.17 1.\nNOTE 1:\tThe attributes \"associatedVnfcCpId\", \"associatedVipCpId\" and \"associatedVnfVirtualLinkId\" \n are mutually exclusive. Exactly one shall be present.\nNOTE 2:\tAn external CP instance is not associated to a link port in the cases indicated for the \n ΓÇ£extLinkPortsΓÇ¥ attribute in clause 4.4.1.11.\n",
+ "currentVnfExtCpData": {
+ "description": "Allows the API consumer to read the current CP configuration information for the connection of external CPs to the external virtual link. See note.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents configuration information for external CPs created. * NOTE 1: \tIn case this identifier refers to a CPD with trunking enabled, the external CP instances created\n from this CPD will represent ports in a trunk.\n* NOTE 2: \tWithin one VNF instance, all VNFC instances created from a particular VDU have the same external\n connectivity. Thus, given a particular value of the \"cpdId\" attribute, there shall be one\n \"cpConfig\" entry for each VNFC instance that has been or can be created from a VDU which includes\n a CPD identified by the \"cpdId\" attribute. If the cpConfig represents a subport in a trunk,\n all \"cpConfig\" entries in this list shall have the same segmentationId, which means they are\n connected to the same set of external VLs via the trunk.\n* NOTE 3: \tThe map entry value shall be set to \"null\" in order to delete a \"VnfExtCpConfig\" entry identified\n by a particular key value from the map, i.e. for the disconnection of an existing external\n CP instance addressed by cpInstanceId in the deleted map entry from a particular external\n virtual link, and deletion of that instance in case it represents a subport. Deleting the\n last key from the map removes the affected instance of the \"VnfExtCpData\" structure from\n its parent data structure.\n* NOTE 4: If, as defined by the input parameters of a \"ChangeVnfFlavour\", \"ChangeExtVnfConnectivity\" or\n \"ChangeCurrentVnfPkg\" operation, a cpConfig map entry identified by a particular map key value \n is moved into another \"ExtVirtualLinkData\" or \"VnfExtCpData\" structure, this particular cpConfig\n map entry may be used by an external CP instance different than the one that has used it before the\n operation, or by no external CP instance at all. Renaming a CPD identifier during the \"changeCurrentVnfPkg\"\n operation does not count as moving the related \"cpConfig\" map entries to a new \"extCpData\" structure.\n",
+ "type": "object",
+ "required": [
+ "cpdId"
+ ],
+ "properties": {
+ "cpdId": {
+ "description": "An identifier that is unique within a VNF descriptor.\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 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",
- "required": [
- "id",
- "cpdId",
- "cpConfigId",
- "cpProtocolInfo"
- ],
- "oneOf": [{
- "required": [
- "associatedVnfcCpId"
- ]
+ "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",
+ "anyOf": [
+ {
+ "required": [
+ "linkPortId"
+ ]
},
{
- "required": [
- "associatedVipCpId"
- ]
+ "required": [
+ "cpProtocolData"
+ ]
},
{
- "required": [
- "associatedVnfVirtualLinkId"
- ]
+ "required": [
+ "netAttDefResourceId"
+ ]
}
- ],
- "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 VNF descriptor.\n",
- "type": "string"
+ ],
+ "type": "object",
+ "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"
},
- "cpConfigId": {
- "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"
},
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
+ "createExtLinkPort": {
+ "description": "Indicates to the VNFM the need to create a dedicated link port for the external CP. If set to True, the VNFM shall create a link port. If set to False, the VNFM shall not create a link port. This attribute is only applicable for external CP instances without a floating IP address that expose a virtual IP 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"
},
- "cpProtocolInfo": {
- "description": "Network protocol information for this CP.\n",
- "type": "array",
- "items": {
- "description": "This type describes the protocol layer(s) that a CP uses together with protocol-related information, like addresses. It shall comply with the provisions defined in table 5.5.3.9b-1.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the \n present document in a backwards-compatible way. In the current version of the present document, only IP over \n Ethernet is supported.\n",
+ "cpProtocolData": {
+ "description": "Parameters for configuring the network protocols on the link port that connects the CP to a VL. See notes 1 and 2.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents network protocol data. * NOTE:\tThis attribute allows to signal the addition of further types of layer and protocol\n in future versions of the present document in a backwards-compatible way. In the current\n 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:\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 network address data for IP over Ethernet to assign to the external CP. * NOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. * NOTE 2:\tExactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present. * NOTE 3:\tIf the CP instance represents a subport in a trunk, segmentationId shall be present.\n Otherwise it shall not be present.\n* NOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the actual\n network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header\n of the packets or it may be an identifier used between the application and the NFVI networking\n infrastructure to identify the network sub-interface of the trunk port in question. In the latter\n case the NFVI infrastructure will map this local segmentationId to whatever segmentationId is\n actually used by the NFVI's transport technology.\n",
"type": "object",
- "required": [
- "layerProtocol"
+ "anyOf": [
+ {
+ "required": [
+ "macAddress"
+ ]
+ },
+ {
+ "required": [
+ "ipAddresses"
+ ]
+ }
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "fixedAddresses"
+ ]
+ },
+ {
+ "required": [
+ "numDynamicAddresses"
+ ]
+ },
+ {
+ "required": [
+ "ipAddressRange"
+ ]
+ }
],
"properties": {
- "layerProtocol": {
- "description": "The identifier of layer(s) and protocol(s) associated to the network address information.\nPermitted values: IP_OVER_ETHERNET See note.\n",
- "type": "string",
- "enum": [
- "IP_OVER_ETHERNET"
- ]
- },
- "ipOverEthernet": {
- "description": "This type represents information about a network address that has been assigned. It shall comply with the provisions defined in table 5.5.3.10-1.\nNOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, segmentationId shall be present. \n Otherwise it shall not be present.\nNOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the \n actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the \n transport header of the packets or it may be an identifier used between the application \n and the NFVI networking infrastructure to identify the network sub-interface of the trunk \n port in question. In the latter case the NFVI infrastructure will map this local segmentationId \n to whatever segmentationId is actually used by the NFVIΓÇÖs transport technology.\n",
- "type": "object",
- "anyOf": [{
- "required": [
- "macAddress"
- ]
- },
- {
- "required": [
- "ipAddresses"
- ]
- }
- ],
- "oneOf": [{
- "required": [
- "addresses"
- ]
- },
- {
- "required": [
- "addressRange"
- ]
- }
- ],
- "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 notes 3 and 4.\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"
+ },
+ "segmentationType": {
+ "description": "Specifies the encapsulation type for the traffics coming in and out of the trunk subport. Permitted values: -\tVLAN: the subport uses VLAN as encapsulation type. -\tINHERIT: the subport gets its segmentation type from the network itΓÇÖs 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"
+ ],
+ "properties": {
+ "type": {
+ "description": "The type of the IP addresses. Permitted values: IPV4, IPV6.\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
+ },
+ "fixedAddresses": {
+ "description": "Fixed addresses to assign (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"
+ }
+ },
+ "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. 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"
},
- "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"
- ],
- "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. 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 other resource provider. It is expected to be unique within the VIM instance.\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.\n",
+ "type": "string"
}
+ }
}
+ }
+ }
+ },
+ "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",
+ "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": {
+ "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 2, 3 and 4.\n",
+ "type": "array",
+ "items": {
"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 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"
- },
- "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"
- },
- "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.\nMay 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 5.5.3.28-1.\nNOTE:\tIt is possible that there is no associated VnfcCp because the VIP CP is available but not associated yet.\n",
- "type": "object",
+ "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 contains 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": {
"required": [
- "cpInstanceId",
- "cpdId"
+ "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",
"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": "An identifier that is unique within a VNF descriptor.\n",
+ "vimConnectionId": {
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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"
- },
- "vnfExtCpId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\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"
- },
- "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 uses together with protocol-related information, like addresses. It shall comply with the provisions defined in table 5.5.3.9b-1.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the \n present document in a backwards-compatible way. In the current version of the present document, only IP over \n Ethernet is supported.\n",
- "type": "object",
- "required": [
- "layerProtocol"
- ],
- "properties": {
- "layerProtocol": {
- "description": "The identifier of layer(s) and protocol(s) associated to the network address information.\nPermitted values: IP_OVER_ETHERNET See note.\n",
- "type": "string",
- "enum": [
- "IP_OVER_ETHERNET"
- ]
- },
- "ipOverEthernet": {
- "description": "This type represents information about a network address that has been assigned. It shall comply with the provisions defined in table 5.5.3.10-1.\nNOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, segmentationId shall be present. \n Otherwise it shall not be present.\nNOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the \n actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the \n transport header of the packets or it may be an identifier used between the application \n and the NFVI networking infrastructure to identify the network sub-interface of the trunk \n port in question. In the latter case the NFVI infrastructure will map this local segmentationId \n to whatever segmentationId is actually used by the NFVIΓÇÖs transport technology.\n",
- "type": "object",
- "anyOf": [{
- "required": [
- "macAddress"
- ]
- },
- {
- "required": [
- "ipAddresses"
- ]
- }
- ],
- "oneOf": [{
- "required": [
- "addresses"
- ]
- },
- {
- "required": [
- "addressRange"
- ]
- }
- ],
- "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 notes 3 and 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"
- ],
- "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. 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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "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": "Metadata about this VIP CP.\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 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"
- }
+ },
+ "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 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"
+ }
}
+ },
+ "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 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 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"
+ }
+ }
}
+ }
+ }
+ }
+ }
+ },
+ "extManagedVirtualLinkInfo": {
+ "description": "Information about the externally managed internal VLs of the VNF instance. See note 5 and note 6. 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 VNF internal VL shall indicate so by referencing to the same VnfVirtualLinkDesc and externally-managed multi-site VL instance (refer to clause 5.5.3.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": "array",
+ "items": {
+ "description": "This type provides information about an externally-managed virtual link.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "vnfVirtualLinkDescId",
+ "networkResource"
+ ],
+ "properties": {
+ "id": {
+ "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 external VL. It shall comply with the provisions defined in table 5.5.3.2-1.\nNOTE:\tThis attribute reflects the current configuration information that has resulted from merging into this attribute \n the \"VnfExtCpData\" information which was passed as part of the \"ExtVirtualLinkData\" structure in the input of the \n most recent VNF LCM operation such as \"InstantiateVnfRequest\", \"ChangeExtVnfConnectivityRequest\", \"ChangeVnfFlavourRequest\" \n or \"ChangeCurrentVnfPkgRequest\", or in the Grant response. If applying such change results in an empty list of \n \"currentVnfExtCpData\" structure instances, the affected instance of \"ExtVirtualLinkInfo\" shall be removed from its \n parent data structure.\n",
- "type": "object",
- "required": [
- "id",
- "resourceHandle",
- "currentVnfExtCpData"
- ],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceHandle": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\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. It shall comply with the provisions defined in table 5.5.3.9-1.\nNOTE 1:\tThe 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:\tThe 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": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\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.\n",
- "type": "string"
- }
- }
- }
- },
- "currentVnfExtCpData": {
- "description": "Allows the API consumer to read the current CP configuration information for the connection of external CPs to the external virtual link. See note.\n",
- "type": "array",
- "items": {
- "description": "This type represents configuration information for external CPs created. * NOTE 1: \tIn case this identifier refers to a CPD with trunking enabled, the external CP instances created\n from this CPD will represent ports in a trunk.\n* NOTE 2: \tWithin one VNF instance, all VNFC instances created from a particular VDU have the same external\n connectivity. Thus, given a particular value of the \"cpdId\" attribute, there shall be one\n \"cpConfig\" entry for each VNFC instance that has been or can be created from a VDU which includes\n a CPD identified by the \"cpdId\" attribute. If the cpConfig represents a subport in a trunk,\n all \"cpConfig\" entries in this list shall have the same segmentationId, which means they are\n connected to the same set of external VLs via the trunk.\n* NOTE 3: \tThe map entry value shall be set to \"null\" in order to delete a \"VnfExtCpConfig\" entry identified\n by a particular key value from the map, i.e. for the disconnection of an existing external\n CP instance addressed by cpInstanceId in the deleted map entry from a particular external\n virtual link, and deletion of that instance in case it represents a subport. Deleting the\n last key from the map removes the affected instance of the \"VnfExtCpData\" structure from\n its parent data structure.\n",
- "type": "object",
- "required": [
- "cpdId"
- ],
- "properties": {
- "cpdId": {
- "description": "An identifier that is unique within a VNF descriptor.\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 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). See note 2 and note 3.\n",
- "type": "object",
- "additionalProperties": {
- "description": "This type represents an externally provided link port or network address information per instance of an external connection point. In case a link port is provided, the VNFM shall use that link port when connecting the external CP to the external VL. In a link port is not provided, the VNFM shall create a link port on the external VL, and use that link port to connect the external CP to the external VL. * NOTE: The following conditions apply to the attributes \"linkPortId\" and \"cpProtocolData\":\n 1) Void.\n 2) At least one of the \"linkPortId\" and \"cpProtocolData\" attributes shall be present for an external\n CP instance representing a subport that is to be created, or an external CP instance that is to be\n created by creating the corresponding VNFC or VNF instance during the current or a subsequent LCM\n operation, or for an existing external CP instance that is to be re-configured or added to a\n 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\n a pre created link port, and the VNFM can use means outside the scope of the present document to obtain\n the pre-configured address information for the connection point from the resource representing\n the link port.\n 5) If both \"cpProtocolData\" and \"linkportId\" are provided, the API consumer shall ensure that the\n cpProtocolData can be used with the pre-created link port referenced by \"linkPortId\".\n",
- "anyOf": [{
- "required": [
- "linkPortId"
- ]
- },
- {
- "required": [
- "cpProtocolData"
- ]
- }
- ],
- "type": "object",
- "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 to the VNFM the need to create a dedicated link port for the external CP. If set to True, the VNFM shall create a link port. If set to False, the VNFM shall not create a link port. 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 note.\n",
- "type": "array",
- "items": {
- "description": "This type represents network protocol data. * NOTE:\tThis attribute allows to signal the addition of further types of layer and protocol\n in future versions of the present document in a backwards-compatible way. In the current\n 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). See note.\n",
- "type": "string",
- "enum": [
- "IP_OVER_ETHERNET"
- ]
- },
- "ipOverEthernet": {
- "description": "This type represents network address data for IP over Ethernet. * NOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. * NOTE 2:\tExactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present. * NOTE 3:\tIf the CP instance represents a subport in a trunk, segmentationId shall be present.\n Otherwise it shall not be present.\n* NOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the actual\n network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header\n of the packets or it may be an identifier used between the application and the NFVI networking\n infrastructure to identify the network sub-interface of the trunk port in question. In the latter\n case the NFVI infrastructure will map this local segmentationId to whatever segmentationId is\n actually used by the NFVIΓÇÖs transport technology.\n",
- "type": "object",
- "anyOf": [{
- "required": [
- "macAddress"
- ]
- },
- {
- "required": [
- "ipAddresses"
- ]
- }
- ],
- "oneOf": [{
- "required": [
- "fixedAddresses"
- ]
- },
- {
- "required": [
- "numDynamicAddresses"
- ]
- },
- {
- "required": [
- "ipAddressRange"
- ]
- }
- ],
- "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: -\tVLAN: the subport uses VLAN as encapsulation type. -\tINHERIT: the subport gets its segmentation type from the network itΓÇÖs 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"
- ],
- "properties": {
- "type": {
- "description": "The type of the IP addresses. Permitted values: IPV4, IPV6.\n",
- "type": "string",
- "enum": [
- "IPV4",
- "IPV6"
- ]
- },
- "fixedAddresses": {
- "description": "Fixed addresses to assign (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"
- }
- },
- "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. 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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
+ "vnfVirtualLinkDescId": {
+ "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"
+ },
+ "networkResource": {
+ "required": [
+ "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",
+ "properties": {
+ "vimConnectionId": {
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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 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"
}
+ }
+ },
+ "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"
}
+ }
},
- "extManagedVirtualLinkInfo": {
- "description": "Information about the externally managed internal VLs of the VNF instance. See note 5 and note 6. 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 VNF internal VL shall indicate so by referencing to the same VnfVirtualLinkDesc and externally-managed multi-site VL instance (refer to clause 5.5.3.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": "array",
- "items": {
- "type": "object",
+ "vnfLinkPorts": {
+ "description": "Link ports of this VL.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents a link port of an internal VL of a VNF.\nNOTE 1: Either cpInstanceId with cpInstanceType set to \"EXT_CP\" or any combination of cpInstanceId\n with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId (i.e. one or both of them) shall be \n present for a VnfLinkPortInfo. In case both cpInstanceId with cpInstanceType set to \"VNFC_CP\" \n and vipCpInstanceId are present, the two different CP instances share the linkport.\nNOTE 2: Annex A.4 of ETSI GS NFV-IFA 007 provides examples for configurations where both vipCpInstanceId\n and vnfcCpInstanceId are present (UC#5 and UC#5-b), only vnfcCpInstanceId is present (UC#2), or \n only vipCpInstanceId is present (UC6 and UC#6-b).\nNOTE 3: The value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\"\n attribute.\n",
+ "type": "object",
+ "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": {
"required": [
- "id",
- "vnfVirtualLinkDescId",
- "networkResource"
+ "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",
"properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfVirtualLinkDescId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "vimConnectionId": {
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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",
+ },
+ "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"
- },
- "networkResource": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
- "type": "string"
- }
- }
- },
- "vnfLinkPorts": {
- "description": "Link ports of this VL.\n",
- "type": "array",
- "items": {
- "description": "This type represents a link port of an internal VL of a VNF. It shall comply with the provisions defined in table 5.5.3.8 1.\nNOTE 1: Either cpInstanceId with cpInstanceType set to \"EXT_CP\" or any combination of cpInstanceId\n with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId (i.e. one or both of them) shall be \n present for a VnfLinkPortInfo. In case both cpInstanceId with cpInstanceType set to \"VNFC_CP\" \n and vipCpInstanceId are present, the two different CP instances share the linkport.\nNOTE 2: Annex A.4 of ETSI GS NFV-IFA 007 provides examples for configurations where both vipCpInstanceId\n and vnfcCpInstanceId are present (UC#5 and UC#5-b), only vnfcCpInstanceId is present (UC#2), or \n only vipCpInstanceId is present (UC6 and UC#6-b).\nNOTE 3: The value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\"\n attribute.\n",
- "type": "object",
- "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": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\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.\nPermitted values: - VNFC_CP: The link port is connected to a VNFC CP. -\tEXT_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.\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 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"
+ }
}
+ },
+ "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.\nPermitted values: - VNFC_CP: The link port is connected to a VNFC CP. -\tEXT_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 the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "type": "string"
+ }
}
+ }
},
- "monitoringParameters": {
- "description": "Active monitoring parameters.\n",
- "type": "array",
- "items": {
- "type": "object",
+ "vnfNetAttDefResource": {
+ "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 contains 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": {
"required": [
- "id",
- "performanceMetric"
+ "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",
"properties": {
- "id": {
- "description": "An identifier that is unique within a VNF descriptor.\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",
+ "vimConnectionId": {
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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"
- },
- "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",
+ },
+ "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 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"
+ }
}
+ },
+ "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 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 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"
}
+ }
}
+ }
+ }
+ }
+ }
+ },
+ "monitoringParameters": {
+ "description": "Active monitoring parameters.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": [
+ "id",
+ "performanceMetric"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier that is unique within a VNF descriptor.\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"
+ "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"
},
- "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. * NOTE 1:\tETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on TOSCA specifications. * NOTE 2:\tA VNFC CP is \"connected to\" an external CP if the VNFC CP is connected to an internal VL that\n exposes an external CP. A VNFC CP is \"exposed as\" an external CP if it is connected directly\n to an external VL.\n* NOTE 3:\tThe information can be omitted because it is already available as part of the external CP information.\n",
+ "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": "This type represents the information on virtualised compute and storage resources used by a VNFC in a VNF instance. Depending on the form of virtualisation container of the VNFC:\n - For a VNFC based on VM, a reference to the corresponding VirtualCompute shall be provided, and\n - For a VNFC based on OS container(s), a reference to the Compute MCIO shall be provided. Hence, exposure \n of information by the VNFM to the NFVO is at the MCIO level.\nIn addition, the references to the storage resources depend on the form of the VNFC:\n - For a VNFC based on VM, storage resource identifiers shall refer to VirtualStorage resources, and\n - For a VNFC based on OS container(s), storage resource identifiers shall refer to Storage MCIOs.\n\n\n* NOTE 1:\tETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on TOSCA specifications. * NOTE 2:\tA VNFC CP is \"connected to\" an external CP if the VNFC CP is connected to an internal VL that\n exposes an external CP. A VNFC CP is \"exposed as\" an external CP if it is connected directly\n to an external VL.\n* NOTE 3:\tThe information can be omitted because it is already available as part of the external CP information. * NOTE 4: If only the value or the presence of this attribute is changed in the \"VnfcResourceInfo\" structure by \n an LCM operation occurrence, this does not represent a change that requires including a related \"AffectedVnfc\"\n structure in the VNF LCM operation occurrence notifications or the \"VnfLcmOpOcc\" structure related to \n this LCM operation occurrence.\n* NOTE 5: 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 internal CP, e.g. to build \n a link redundant mated pair in SR-IOV cases.\n* NOTE 6: 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"
+ },
+ "vduId": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "computeResource": {
+ "required": [
+ "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",
+ "properties": {
+ "vimConnectionId": {
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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 MCIO(s). 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": "All the CPs of the VNFC instance.\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 VNF descriptor.\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. The information can be omitted because it is already available as part of the external CP information. See note 3.\n",
+ "type": "array",
+ "items": {
+ "description": "This type describes the protocol layer(s) that a CP uses together with protocol-related information, like addresses.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the \n present document in a backwards-compatible way. In the current version of the present document, only IP over \n Ethernet is supported.\n",
"type": "object",
"required": [
- "id",
- "vduId",
- "computeResource"
+ "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"
- },
- "vduId": {
- "description": "An identifier that is unique within a VNF descriptor.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "computeResource": {
+ "layerProtocol": {
+ "description": "The identifier of layer(s) and protocol(s) associated to the network address information.\nPermitted 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:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, segmentationId shall be present. \n Otherwise it shall not be present.\nNOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the \n actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the \n transport header of the packets or it may be an identifier used between the application \n and the NFVI networking infrastructure to identify the network sub-interface of the trunk \n port in question. In the latter case the NFVI infrastructure will map this local segmentationId \n to whatever segmentationId is actually used by the NFVIΓÇÖs transport technology.\n",
+ "type": "object",
+ "anyOf": [
+ {
"required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
+ "macAddress"
+ ]
+ },
+ {
+ "required": [
+ "ipAddresses"
+ ]
+ }
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "addresses"
+ ]
+ },
+ {
+ "required": [
+ "addressRange"
+ ]
+ }
+ ],
+ "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 notes 3 and 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"
+ ],
+ "properties": {
+ "type": {
+ "description": "The type of the IP addresses. Permitted values: IPV4, IPV6.\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
},
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
+ "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"
+ }
},
- "resourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\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"
},
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
- "type": "string"
+ "addressRange": {
+ "description": "An IP address range used, e.g. in case of egress connections. 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.\n",
+ "type": "string"
}
+ }
}
- },
- "storageResourceIds": {
- "description": "References to the VirtualStorage resources. 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": "All the CPs of the VNFC instance.\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 VNF descriptor.\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. The information can be omitted because it is already available as part of the external CP information. See note 3.\n",
- "type": "array",
- "items": {
- "description": "This type describes the protocol layer(s) that a CP uses together with protocol-related information, like addresses. It shall comply with the provisions defined in table 5.5.3.9b-1.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the \n present document in a backwards-compatible way. In the current version of the present document, only IP over \n Ethernet is supported.\n",
- "type": "object",
- "required": [
- "layerProtocol"
- ],
- "properties": {
- "layerProtocol": {
- "description": "The identifier of layer(s) and protocol(s) associated to the network address information.\nPermitted values: IP_OVER_ETHERNET See note.\n",
- "type": "string",
- "enum": [
- "IP_OVER_ETHERNET"
- ]
- },
- "ipOverEthernet": {
- "description": "This type represents information about a network address that has been assigned. It shall comply with the provisions defined in table 5.5.3.10-1.\nNOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, segmentationId shall be present. \n Otherwise it shall not be present.\nNOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the \n actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the \n transport header of the packets or it may be an identifier used between the application \n and the NFVI networking infrastructure to identify the network sub-interface of the trunk \n port in question. In the latter case the NFVI infrastructure will map this local segmentationId \n to whatever segmentationId is actually used by the NFVIΓÇÖs transport technology.\n",
- "type": "object",
- "anyOf": [{
- "required": [
- "macAddress"
- ]
- },
- {
- "required": [
- "ipAddresses"
- ]
- }
- ],
- "oneOf": [{
- "required": [
- "addresses"
- ]
- },
- {
- "required": [
- "addressRange"
- ]
- }
- ],
- "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 notes 3 and 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"
- ],
- "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. 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 other resource provider. It is expected to be unique within the VIM instance.\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"
- },
- "parentCpId": {
- "description": "This 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"
- },
- "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 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"
- }
- }
- }
- },
- "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 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"
+ }
}
- }
- }
- },
- "vnfVirtualLinkResourceInfo": {
- "description": "Information about the virtualised network resources used by the VLs of the VNF instance. See note 6. 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": "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",
- "vnfLinkPorts"
- ],
- "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"
- },
- "vnfVirtualLinkDescId": {
- "description": "An identifier that is unique within a VNF descriptor.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "networkResource": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\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": {
- "description": "This type represents a link port of an internal VL of a VNF. It shall comply with the provisions defined in table 5.5.3.8 1.\nNOTE 1: Either cpInstanceId with cpInstanceType set to \"EXT_CP\" or any combination of cpInstanceId\n with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId (i.e. one or both of them) shall be \n present for a VnfLinkPortInfo. In case both cpInstanceId with cpInstanceType set to \"VNFC_CP\" \n and vipCpInstanceId are present, the two different CP instances share the linkport.\nNOTE 2: Annex A.4 of ETSI GS NFV-IFA 007 provides examples for configurations where both vipCpInstanceId\n and vnfcCpInstanceId are present (UC#5 and UC#5-b), only vnfcCpInstanceId is present (UC#2), or \n only vipCpInstanceId is present (UC6 and UC#6-b).\nNOTE 3: The value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\"\n attribute.\n",
- "type": "object",
- "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": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\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.\nPermitted values: - VNFC_CP: The link port is connected to a VNFC CP. -\tEXT_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.\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 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"
+ },
+ "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"
+ }
}
+ }
}
+ }
+ },
+ "vnfLinkPortId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "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"
+ },
+ "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 5 and 6. 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 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 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"
}
- },
- "vnfVirtualStorageResourceInfo": {
- "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": "An identifier that is unique within a VNF descriptor.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "storageResource": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\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 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"
- }
- }
+ }
+ }
+ },
+ "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 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"
+ }
+ }
+ },
+ "vnfVirtualLinkResourceInfo": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by an internal VL instance in a VNF instance. NOTE: If only the value or the presence of this attribute is changed in the \"VnfVirtualLinkResourceInfo\" \n structure by an LCM operation occurrence, this does not represent a change that requires including a \n related \"AffectedVirtualLink\" structure in the VNF LCM operation occurrence notifications or the \n \"VnfLcmOpOcc\" structure related to this LCM operation occurrence.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "vnfVirtualLinkDescId",
+ "networkResource",
+ "vnfLinkPorts"
+ ],
+ "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"
+ },
+ "vnfVirtualLinkDescId": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "networkResource": {
+ "required": [
+ "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",
+ "properties": {
+ "vimConnectionId": {
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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 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"
+ }
}
- },
- "vnfcInfo": {
- "description": "Information about the VNFC instances.\n",
- "type": "array",
- "items": {
- "description": "This type represents the information about a VNFC instance that is part of a VNF instance. * NOTE:\tThis allows to represent the error condition that a VNFC instance has lost its resources.\n",
- "type": "object",
- "required": [
- "id",
- "vduId",
- "vnfcState"
- ],
- "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"
- },
- "vduId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\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"
+ },
+ "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": {
+ "description": "This type represents a link port of an internal VL of a VNF.\nNOTE 1: Either cpInstanceId with cpInstanceType set to \"EXT_CP\" or any combination of cpInstanceId\n with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId (i.e. one or both of them) shall be \n present for a VnfLinkPortInfo. In case both cpInstanceId with cpInstanceType set to \"VNFC_CP\" \n and vipCpInstanceId are present, the two different CP instances share the linkport.\nNOTE 2: Annex A.4 of ETSI GS NFV-IFA 007 provides examples for configurations where both vipCpInstanceId\n and vnfcCpInstanceId are present (UC#5 and UC#5-b), only vnfcCpInstanceId is present (UC#2), or \n only vipCpInstanceId is present (UC6 and UC#6-b).\nNOTE 3: The value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\"\n attribute.\n",
+ "type": "object",
+ "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": {
+ "required": [
+ "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",
+ "properties": {
+ "vimConnectionId": {
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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"
},
- "vnfcState": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be 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"
},
- "vnfcConfigurableProperties": {
- "description": "This 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"
+ "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 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"
}
+ }
+ },
+ "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.\nPermitted values: - VNFC_CP: The link port is connected to a VNFC CP. -\tEXT_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 the CISM or other resource provider. It is expected to be unique within the VIM instance.\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 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"
+ }
}
- },
- "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 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"
- },
- "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 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"
- },
- "_links": {
- "description": "Links to resources related to this resource.\n",
+ },
+ "virtualStorageResourceInfo":{
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance.\nNOTE: If only the value or the presence of this attribute is changed in the \"VirtualStorageResourceInfo\" structure by an LCM operation occurrence, this does not represent a change that requires including a related \"AffectedVirtualStorage\" structure in the VNF LCM operation occurrence notifications or the \"VnfLcmOpOcc\" structure related to this LCM operation occurrence.\n",
"type": "object",
"required": [
- "self"
+ "id",
+ "virtualStorageDescId",
+ "storageResource"
],
"properties": {
- "self": {
- "description": "This type represents a link to a resource using an absolute URI.\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"
+ },
+ "virtualStorageDescId": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "storageResource": {
+ "required": [
+ "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",
+ "properties": {
+ "vimConnectionId": {
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At least one attribute shall be present.\n",
"type": "object",
- "required": [
- "href"
- ],
"properties": {
- "href": {
- "description": "String formatted according to IETF RFC 3986.\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 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"
+ }
}
+ },
+ "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 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"
+ }
+ }
+ },
+ "vnfcInfo": {
+ "description": "Information about the VNFC instances.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the information about a VNFC instance that is part of a VNF instance. * NOTE:\tThis allows to represent the error condition that a VNFC instance has lost its resources.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "vduId",
+ "vnfcState"
+ ],
+ "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"
},
- "indicators": {
- "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"
- }
- }
+ "vduId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
},
- "instantiate": {
- "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"
- }
- }
+ "vnfcResourceInfoId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
},
- "terminate": {
- "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"
- }
- }
+ "vnfcState": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
},
- "scale": {
- "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"
- }
- }
+ "vnfcConfigurableProperties": {
+ "description": "This 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"
+ }
+ }
+ }
+ },
+ "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. Within the CISM, an MCIO controller monitors the actual state of an MCIO representing the set of VNFC instances realized by one or a set of OS containers and compare it to the desired state as specified in the respective declarative descriptor. It triggers actions toward the CIS to align the actual to the desired state. Monitoring the actual state includes monitoring the number of MCIO instances available at any specific point in time. In addition, an MCIO controller maintains properties and runtime information on the MCIO instances which have been created based on the same VDU. The McioInfo data structure provides the runtime information on the MCIOs obtained from the MCIO controller.\nNOTE: There are different types of MCIOs. The set of VNFC instances based on the same VDU is represented \n by one MCIO, e.g. of type Deployment. Each individual VNFC instance is represented by another type \n of MCIO, e.g. a POD.\n\nRuntime information of the set of OS containers realizing an individual VNFC instance is not part of the McioInfo data structure; such runtime information is provided in the ResourceHandle data structure referenced from the VnfcResourceInfo. The McioInfo does not provide runtime information of a constituent VNFC instance created based on a specific VDU.\nNOTE 1: The type of MCIO as specified in the declarative descriptor of the MCIO, and that can be read from \n the CISM. EXAMPLE: In case of MCIOs managed by Kubernetes®, the type of MCIO corresponds to the \n “kind” property of the declarative descriptor.\nNOTE 2: If the attribute additionalInfo is present, it may contain runtime information on the actual and \n desired state of the MCIO(s). \nNOTE 3: When the container infrastructure service is a Kubernetes® instance, the mcioId is the combined \n values from the kind and name fields of the Kubernetes resource object, separated by a slash. \n Example: \"Deployment/abcd\". \nNOTE 4: When the container infrastructure service is a Kubernetes® instance, the mcioName is the name \n field of the resource object. \n",
+ "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"
},
- "scaleToLevel": {
- "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"
- }
- }
+ "mcioName": {
+ "description": "Human readable name of this MCIO. See note 4.\n",
+ "type": "string"
},
- "changeFlavour": {
- "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"
- }
- }
+ "mcioNamespace": {
+ "description": "Namespace of this MCIO.\n",
+ "type": "string"
},
- "heal": {
- "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"
- }
- }
+ "vduId": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
},
- "operate": {
- "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"
- }
- }
+ "cismId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
},
- "changeExtConn": {
- "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"
- }
- }
+ "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"
+ ]
},
- "createSnapshot": {
- "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"
- }
- }
+ "desiredInstances": {
+ "description": "Number of desired MCIO instances.\n",
+ "type": "integer"
},
- "revertToSnapshot": {
- "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"
- }
- }
+ "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 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"
}
+ }
}
+ }
}
+ },
+ "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 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"
+ },
+ "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 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"
+ },
+ "_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 using an absolute URI.\n",
+ "type": "object",
+ "required": [
+ "href"
+ ],
+ "properties": {
+ "href": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ }
+ }
+ },
+ "indicators": {
+ "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"
+ }
+ }
+ },
+ "instantiate": {
+ "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"
+ }
+ }
+ },
+ "terminate": {
+ "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"
+ }
+ }
+ },
+ "scale": {
+ "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"
+ }
+ }
+ },
+ "scaleToLevel": {
+ "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"
+ }
+ }
+ },
+ "changeFlavour": {
+ "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"
+ }
+ }
+ },
+ "heal": {
+ "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"
+ }
+ }
+ },
+ "operate": {
+ "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"
+ }
+ }
+ },
+ "changeExtConn": {
+ "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"
+ }
+ }
+ },
+ "createSnapshot": {
+ "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"
+ }
+ }
+ },
+ "revertToSnapshot": {
+ "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"
+ }
+ }
+ },
+ "changeCurrentVnfPkg": {
+ "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"
+ }
+ }
+ }
+ }
+ }
}
- },
- "vnfcSnapshots": {
+ },
+ "vnfcSnapshots": {
"description": "Information about VNFC snapshots constituting this VNF snapshot.\n",
"type": "array",
"items": {
- "description": "This type represents a VNFC snapshot. * NOTE 1:\tThe identifier of the compute snapshot resource is assigned during creation of a VNFC\n snapshot being returned from the VIM as output data in the response message of the individual\n resource operations. This attribute shall only be present for a VNFC snapshot that has been\n newly created by the VNFM as a result of the \"Create VNF snapshot task\".\n NOTE 2:\tThe identifier of the storage snapshot resource is assigned during creation of a VNFC snapshot\n being returned from the VIM as output data in the response message of the individual resource\n operations. This attribute shall only be present for a VNFC snapshot with an associated storage\n resource and that has been newly created by the VNFM as a result of the \"Create VNF snapshot task\".\n",
- "type": "object",
- "required": [
+ "description": "This type represents a VNFC snapshot. * NOTE 1:\tThe identifier of the compute snapshot resource is assigned during creation of a VNFC\n snapshot being returned from the VIM as output data in the response message of the individual\n resource operations. This attribute shall only be present for a VNFC snapshot that has been\n newly created by the VNFM as a result of the \"Create VNF snapshot task\".\n NOTE 2:\tThe identifier of the storage snapshot resource is assigned during creation of a VNFC snapshot\n being returned from the VIM as output data in the response message of the individual resource\n operations. This attribute shall only be present for a VNFC snapshot with an associated storage\n 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",
+ "creationStartedAt",
+ "vnfcResourceInfoId"
+ ],
+ "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 to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "creationFinishedAt": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "vnfcResourceInfoId": {
+ "description": "This type represents the information about a VNFC instance that is part of a VNF instance. * NOTE:\tThis allows to represent the error condition that a VNFC instance has lost its resources.\n",
+ "type": "object",
+ "required": [
"id",
- "vnfcInstanceId",
- "creationStartedAt",
- "vnfcResourceInfoId"
- ],
- "properties": {
+ "vduId",
+ "vnfcState"
+ ],
+ "properties": {
"id": {
- "description": "An identifier with the intention of being globally unique.\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"
},
- "vnfcInstanceId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
+ "vduId": {
+ "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 to 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"
},
- "creationFinishedAt": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
+ "vnfcState": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
},
- "vnfcResourceInfoId": {
- "description": "This type represents the information about a VNFC instance that is part of a VNF instance. * NOTE:\tThis allows to represent the error condition that a VNFC instance has lost its resources.\n",
- "type": "object",
- "required": [
- "id",
- "vduId",
- "vnfcState"
- ],
- "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"
- },
- "vduId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\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"
- },
- "vnfcState": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "vnfcConfigurableProperties": {
- "description": "This 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"
- }
- }
+ "vnfcConfigurableProperties": {
+ "description": "This 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"
+ }
+ }
+ },
+ "computeSnapshotResource": {
+ "required": [
+ "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",
+ "properties": {
+ "vimConnectionId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
},
- "computeSnapshotResource": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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 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"
}
+ }
},
- "storageSnapshotResources": {
- "description": "Mapping of the storage resources associated to the VNFC with the storage snapshot resources.\n",
- "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"
+ "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": "Mapping of the storage resources associated to the VNFC with the storage snapshot resources.\n",
+ "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"
+ },
+ "storageSnapshotResource": {
+ "required": [
+ "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",
+ "properties": {
+ "vimConnectionId": {
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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"
},
- "storageSnapshotResource": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\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 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"
}
+ }
+ },
+ "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 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"
+ }
}
+ }
+ },
+ "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 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"
}
+ }
}
- },
- "userDefinedData": {
+ },
+ "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 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"
+ }
+ }
+ },
+ "_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 using an absolute URI.\n",
+ "type": "object",
+ "required": [
+ "href"
+ ],
+ "properties": {
+ "href": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ }
+ }
+ },
+ "takenFrom": {
+ "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"
+ }
+ }
+ }
}
+ }
}
-}
\ No newline at end of file
+ }
\ No newline at end of file
diff --git a/SOL002/VNFLifecycleManagement-API/schemas/VnfSnapshotsInfo.schema.json b/SOL002/VNFLifecycleManagement-API/schemas/VnfSnapshotsInfo.schema.json
index 46551a0b33eef8ab7c37b06c18e66b2a5abf6628..7511c2097bb84ae6df599920d0287193740ae6f1 100644
--- a/SOL002/VNFLifecycleManagement-API/schemas/VnfSnapshotsInfo.schema.json
+++ b/SOL002/VNFLifecycleManagement-API/schemas/VnfSnapshotsInfo.schema.json
@@ -1,561 +1,882 @@
{
- "type":"array",
- "items": {
- "description": "This type represents a VNF snapshot.\n",
- "type": "object",
- "required": [
- "id",
- "vnfInstanceId",
- "triggeredAt",
- "vnfdId",
- "vnfInfo",
- "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",
- "type": "string"
- },
- "creationStartedAt": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "creationFinishedAt": {
- "description": "Date-time stamp. Representation: String formatted according to 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. * NOTE 1:\tModifying the value of this attribute shall not be performed when conflicts exist\n between the previous and the newly referred VNF package, i.e. when the new VNFD is\n changed with respect to the previous VNFD in other aspects than merely referencing\n to other VNF software images. In order to avoid misalignment of the VnfInstance with\n the current VNF's on-boarded VNF package, the values of attributes in the VnfInstance\n that have corresponding attributes in the VNFD shall be kept in sync with the values in the VNFD.\n* NOTE 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\n applicable to a VNF. Some of these are set prior to instantiation and cannot be modified\n if the VNF is instantiated, some are set prior to instantiation (are part of initial configuration)\n and can be modified later, and others can be set only after instantiation.\n The applicability of certain configuration may depend on the VNF and the required operation of\n the VNF at a certain point in time.\n* NOTE 4:\tUpon creation of the VnfInstance structure, the VNFM shall create and initialize all child\n attributes of \"vnfConfigurableProperties\", \"metadata\" and \"extensions\" that were declared\n in the VNFD with a defined initial value. The defined initial values can be declared in the VNFD,\n and/or, in case of \"metadata\", obtained from the \"CreateVnfRequest\" structure. Child attributes of\n \"vnfConfigurableProperties\", \"metadata\" and \"extensions\" that have no defined initial value shall\n not be created, in order to be consistent with the semantics of the JSON Merge Patch method\n (see IETF RFC 7396) that interprets null values as deletion request.\n* NOTE 5:\tIt is possible to have several ExtManagedVirtualLinkInfo for the same VNF internal VL in case\n of a multi-site VNF spanning several VIMs. The set of ExtManagedVirtualLinkInfo corresponding\n to the same VNF internal VL shall indicate so by referencing to the same VnfVirtualLinkDesc\n and externally-managed multi-site VL instance (refer to clause 5.5.3.5).\n* NOTE 6:\tEven though externally-managed internal VLs are also used for VNF-internal connectivity,\n they shall not be listed in the \"vnfVirtualLinkResourceInfo\" attribute as this would be redundant.\n",
- "type": "object",
- "required": [
- "id",
- "vnfdId",
- "vnfProvider",
- "vnfProductName",
- "vnfSoftwareVersion",
- "vnfdVersion",
- "instantiationState",
- "_links"
- ],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfInstanceName": {
- "description": "Name of the VNF instance. This attribute can be modified with the PATCH method.\n",
- "type": "string"
- },
- "vnfInstanceDescription": {
- "description": "Human-readable description of the VNF instance. This attribute can be modified with the PATCH method.\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.\n",
- "type": "string"
- },
- "vnfdVersion": {
- "description": "A version.\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 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"
- },
- "instantiationState": {
- "description": "The instantiation state of the VNF.\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": "An identifier that is unique within a VNF descriptor.\n",
- "type": "string"
- },
- "vnfState": {
- "description": "STARTED: The VNF instance is up and running. STOPPED: The VNF instance has been shut down.\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. This attribute shall be present if the VNF supports scaling. See clause B.2 for an explanation of VNF scaling.\n",
- "type": "array",
- "items": {
- "required": [
- "aspectId",
- "scaleLevel"
- ],
+ "type": "array",
+ "items": {
+ "description": "This type represents an individual VNF snapshot resource.\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.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "vnfInstanceId",
+ "creationStartedAt",
+ "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",
+ "type": "string"
+ },
+ "creationStartedAt": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "creationFinishedAt": {
+ "description": "Date-time stamp. Representation: String formatted according to 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. * NOTE 1:\tModifying the value of this attribute shall not be performed when conflicts exist\n between the previous and the newly referred VNF package, i.e. when the new VNFD is\n changed with respect to the previous VNFD in other aspects than merely referencing\n to other VNF software images. In order to avoid misalignment of the VnfInstance with\n the current VNF's on-boarded VNF package, the values of attributes in the VnfInstance\n that have corresponding attributes in the VNFD shall be kept in sync with the values in the VNFD.\n* NOTE 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\n applicable to a VNF. Some of these are set prior to instantiation and cannot be modified\n if the VNF is instantiated, some are set prior to instantiation (are part of initial configuration)\n and can be modified later, and others can be set only after instantiation.\n The applicability of certain configuration may depend on the VNF and the required operation of\n the VNF at a certain point in time.\n* NOTE 4:\tUpon creation of the VnfInstance structure, the VNFM shall create and initialize all child\n attributes of \"vnfConfigurableProperties\", \"metadata\" and \"extensions\" that were declared\n in the VNFD with a defined initial value. The defined initial values can be declared in the VNFD,\n and/or, in case of \"metadata\", obtained from the \"CreateVnfRequest\" structure. Child attributes of\n \"vnfConfigurableProperties\", \"metadata\" and \"extensions\" that have no defined initial value shall\n not be created, in order to be consistent with the semantics of the JSON Merge Patch method\n (see IETF RFC 7396) that interprets null values as deletion request.\n* NOTE 5:\tIt is possible to have several ExtManagedVirtualLinkInfo for the same VNF internal VL in case\n of a multi-site VNF spanning several VIMs. The set of ExtManagedVirtualLinkInfo corresponding\n to the same VNF internal VL shall indicate so by referencing to the same VnfVirtualLinkDesc\n and externally-managed multi-site VL instance (refer to clause 5.5.3.5).\n* NOTE 6:\tEven though externally-managed internal VLs are also used for VNF-internal connectivity,\n they shall not be listed in the \"vnfVirtualLinkResourceInfo\" attribute as this would be redundant.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "vnfdId",
+ "vnfProvider",
+ "vnfProductName",
+ "vnfSoftwareVersion",
+ "vnfdVersion",
+ "instantiationState",
+ "_links"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfInstanceName": {
+ "description": "Name of the VNF instance. This attribute can be modified with the PATCH method.\n",
+ "type": "string"
+ },
+ "vnfInstanceDescription": {
+ "description": "Human-readable description of the VNF instance. This attribute can be modified with the PATCH method.\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.\n",
+ "type": "string"
+ },
+ "vnfdVersion": {
+ "description": "A version.\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 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"
+ },
+ "instantiationState": {
+ "description": "The instantiation state of the VNF.\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",
- "properties": {
- "aspectId": {
- "description": "An identifier that is unique within a VNF descriptor.\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"
- }
- }
- }
- },
- "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"
+ "flavourId",
+ "vnfState",
+ "extCpInfo"
],
- "type": "object",
"properties": {
- "aspectId": {
+ "flavourId": {
"description": "An identifier that is unique within a VNF descriptor.\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"
- }
- }
- }
- },
- "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 5.5.3.17 1.\nNOTE 1:\tThe attributes \"associatedVnfcCpId\", \"associatedVipCpId\" and \"associatedVnfVirtualLinkId\" \n are mutually exclusive. Exactly one shall be present.\nNOTE 2:\tAn external CP instance is not associated to a link port in the cases indicated for the \n ΓÇ£extLinkPortsΓÇ¥ attribute in clause 4.4.1.11.\n",
- "type": "object",
- "required": [
- "id",
- "cpdId",
- "cpConfigId",
- "cpProtocolInfo"
- ],
- "oneOf": [{
- "required": [
- "associatedVnfcCpId"
- ]
- },
- {
- "required": [
- "associatedVipCpId"
- ]
- },
- {
- "required": [
- "associatedVnfVirtualLinkId"
+ "vnfState": {
+ "description": "STARTED: The VNF instance is up and running. STOPPED: The VNF instance has been shut down.\n",
+ "type": "string",
+ "enum": [
+ "STARTED",
+ "STOPPED"
]
- }
- ],
- "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 VNF descriptor.\n",
- "type": "string"
},
- "cpConfigId": {
- "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"
+ "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. This attribute shall be present if the VNF supports scaling. See clause B.2 for an explanation of VNF scaling.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the scale level of a VNF instance related to a scaling aspect.\n",
+ "type": "object",
+ "required": [
+ "aspectId",
+ "scaleLevel"
+ ],
+ "properties": {
+ "aspectId": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "scaleToLevel": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ }
+ }
},
- "cpProtocolInfo": {
- "description": "Network protocol information for this CP.\n",
+ "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": {
- "description": "This type describes the protocol layer(s) that a CP uses together with protocol-related information, like addresses. It shall comply with the provisions defined in table 5.5.3.9b-1.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the \n present document in a backwards-compatible way. In the current version of the present document, only IP over \n Ethernet is supported.\n",
+ "description": "This type represents the scale level of a VNF instance related to a scaling aspect.\n",
"type": "object",
"required": [
- "layerProtocol"
+ "aspectId",
+ "scaleLevel"
],
"properties": {
- "layerProtocol": {
- "description": "The identifier of layer(s) and protocol(s) associated to the network address information.\nPermitted values: IP_OVER_ETHERNET See note.\n",
- "type": "string",
- "enum": [
- "IP_OVER_ETHERNET"
+ "aspectId": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "scaleToLevel": {
+ "description": "An identifier with the intention of being globally unique.\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.\nNOTE 1:\tThe attributes \"associatedVnfcCpId\", \"associatedVipCpId\", \"associatedVirtualCpId\" and \n \"associatedVnfVirtualLinkId\" are mutually exclusive. Exactly one shall be present.\nNOTE 2:\tAn external CP instance is not associated to a link port in the cases indicated for the \n ΓÇ£extLinkPortsΓÇ¥ attribute in clause 4.4.1.11.\nNOTE 3: 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 \n CP, e.g. to build a link redundant mated pair in SR-IOV cases.\nNOTE 4: When more than one netAttDefResourceId is indicated, all shall belong to the same namespace.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "cpdId",
+ "cpConfigId",
+ "cpProtocolInfo"
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "associatedVnfcCpId"
]
},
- "ipOverEthernet": {
- "description": "This type represents information about a network address that has been assigned. It shall comply with the provisions defined in table 5.5.3.10-1.\nNOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, segmentationId shall be present. \n Otherwise it shall not be present.\nNOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the \n actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the \n transport header of the packets or it may be an identifier used between the application \n and the NFVI networking infrastructure to identify the network sub-interface of the trunk \n port in question. In the latter case the NFVI infrastructure will map this local segmentationId \n to whatever segmentationId is actually used by the NFVIΓÇÖs transport technology.\n",
- "type": "object",
- "anyOf": [{
- "required": [
- "macAddress"
- ]
- },
- {
- "required": [
- "ipAddresses"
- ]
- }
- ],
- "oneOf": [{
- "required": [
- "addresses"
- ]
- },
- {
- "required": [
- "addressRange"
- ]
- }
- ],
- "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 notes 3 and 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": [
+ "associatedVipCpId"
+ ]
+ },
+ {
+ "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": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "cpConfigId": {
+ "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"
+ },
+ "cpProtocolInfo": {
+ "description": "Network protocol information for this CP.\n",
+ "type": "array",
+ "items": {
+ "description": "This type describes the protocol layer(s) that a CP uses together with protocol-related information, like addresses.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the \n present document in a backwards-compatible way. In the current version of the present document, only IP over \n Ethernet is supported.\n",
+ "type": "object",
+ "required": [
+ "layerProtocol"
+ ],
+ "properties": {
+ "layerProtocol": {
+ "description": "The identifier of layer(s) and protocol(s) associated to the network address information.\nPermitted 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:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, segmentationId shall be present. \n Otherwise it shall not be present.\nNOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the \n actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the \n transport header of the packets or it may be an identifier used between the application \n and the NFVI networking infrastructure to identify the network sub-interface of the trunk \n port in question. In the latter case the NFVI infrastructure will map this local segmentationId \n to whatever segmentationId is actually used by the NFVIΓÇÖs transport technology.\n",
"type": "object",
- "required": [
- "type"
+ "anyOf": [
+ {
+ "required": [
+ "macAddress"
+ ]
+ },
+ {
+ "required": [
+ "ipAddresses"
+ ]
+ }
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "addresses"
+ ]
+ },
+ {
+ "required": [
+ "addressRange"
+ ]
+ }
],
"properties": {
- "type": {
- "description": "The type of the IP addresses. Permitted values: IPV4, IPV6.\n",
+ "macAddress": {
+ "description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
"type": "string",
- "enum": [
- "IPV4",
- "IPV6"
- ]
+ "format": "MAC"
+ },
+ "segmentationId": {
+ "description": "Identification of the network segment to which the Cp instance connects to. See notes 3 and 4.\n",
+ "type": "string"
},
- "addresses": {
- "description": "Fixed addresses assigned (from the subnet defined by \"subnetId\" if provided). See note 2.\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": {
- "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In 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 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"
+ "type": "object",
+ "required": [
+ "type"
+ ],
+ "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. 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.\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"
+ },
+ "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 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"
+ },
+ "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 within a VNF descriptor.\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"
+ },
+ "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. It 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 with the intention of being 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.\nMay be present otherwise.\n",
+ "type": "array",
+ "items": {
+ "description": "This type provides information related to virtual IP CP.\nNOTE 1:\tIt is possible that there is no associated VnfcCp because the virtual IP CP is available but not associated yet. NOTE 2: If only the value or the presence of this attribute is changed in the \"VipCpInfo\" structure by an LCM operation occurrence, this does not represent a change that requires including a related \"AffectedVipCp\" structure in the VNF LCM operation occurrence notifications or the \"VnfLcmOpOcc\" structure related to this LCM operation occurrence.\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": "An identifier that is unique within a VNF descriptor.\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 uses together with protocol-related information, like addresses.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the \n present document in a backwards-compatible way. In the current version of the present document, only IP over \n Ethernet is supported.\n",
+ "type": "object",
+ "required": [
+ "layerProtocol"
+ ],
+ "properties": {
+ "layerProtocol": {
+ "description": "The identifier of layer(s) and protocol(s) associated to the network address information.\nPermitted 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:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, segmentationId shall be present. \n Otherwise it shall not be present.\nNOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the \n actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the \n transport header of the packets or it may be an identifier used between the application \n and the NFVI networking infrastructure to identify the network sub-interface of the trunk \n port in question. In the latter case the NFVI infrastructure will map this local segmentationId \n to whatever segmentationId is actually used by the NFVIΓÇÖs transport technology.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "required": [
+ "macAddress"
+ ]
+ },
+ {
+ "required": [
+ "ipAddresses"
+ ]
+ }
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "addresses"
+ ]
+ },
+ {
+ "required": [
+ "addressRange"
+ ]
+ }
+ ],
+ "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 notes 3 and 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"
+ ],
+ "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. 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.\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 virtual IP 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": "This 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"
+ }
+ }
+ }
+ },
+ "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 provides information related to a virtual CP instance of a VNF.\nNOTE: A consumer of the VNF LCM interface can learn the actual VNFC instances implementing the service \n accessible via the virtual CP instance by querying the \"vnfcResourceInfo\" from the \"InstantiatedVnfInfo\" \n and filtering by corresponding \"vduIds\" values.\n",
+ "type": "object",
+ "required": [
+ "cpInstanceId",
+ "cpdId",
+ "resourceHandle",
+ "vduIds"
+ ],
+ "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": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "resourceHandle": {
+ "required": [
+ "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",
+ "properties": {
+ "vimConnectionId": {
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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 uses together with protocol-related information, like addresses.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the \n present document in a backwards-compatible way. In the current version of the present document, only IP over \n Ethernet is supported.\n",
+ "type": "object",
+ "required": [
+ "layerProtocol"
+ ],
+ "properties": {
+ "layerProtocol": {
+ "description": "The identifier of layer(s) and protocol(s) associated to the network address information.\nPermitted 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:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, segmentationId shall be present. \n Otherwise it shall not be present.\nNOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the \n actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the \n transport header of the packets or it may be an identifier used between the application \n and the NFVI networking infrastructure to identify the network sub-interface of the trunk \n port in question. In the latter case the NFVI infrastructure will map this local segmentationId \n to whatever segmentationId is actually used by the NFVIΓÇÖs transport technology.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "required": [
+ "macAddress"
+ ]
+ },
+ {
+ "required": [
+ "ipAddresses"
+ ]
+ }
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "addresses"
+ ]
+ },
+ {
+ "required": [
+ "addressRange"
+ ]
+ }
+ ],
+ "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 notes 3 and 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"
+ ],
+ "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. 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.\n",
+ "type": "string"
+ }
}
}
- },
- "subnetId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
}
}
- }
- }
- }
- }
- }
- }
- },
- "extLinkPortId": {
- "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 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"
- },
- "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"
- },
- "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.\nMay 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 5.5.3.28-1.\nNOTE:\tIt 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": "An identifier that is unique within a VNF descriptor.\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 uses together with protocol-related information, like addresses. It shall comply with the provisions defined in table 5.5.3.9b-1.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the \n present document in a backwards-compatible way. In the current version of the present document, only IP over \n Ethernet is supported.\n",
- "type": "object",
- "required": [
- "layerProtocol"
- ],
- "properties": {
- "layerProtocol": {
- "description": "The identifier of layer(s) and protocol(s) associated to the network address information.\nPermitted values: IP_OVER_ETHERNET See note.\n",
- "type": "string",
- "enum": [
- "IP_OVER_ETHERNET"
- ]
- },
- "ipOverEthernet": {
- "description": "This type represents information about a network address that has been assigned. It shall comply with the provisions defined in table 5.5.3.10-1.\nNOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, segmentationId shall be present. \n Otherwise it shall not be present.\nNOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the \n actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the \n transport header of the packets or it may be an identifier used between the application \n and the NFVI networking infrastructure to identify the network sub-interface of the trunk \n port in question. In the latter case the NFVI infrastructure will map this local segmentationId \n to whatever segmentationId is actually used by the NFVIΓÇÖs transport technology.\n",
- "type": "object",
- "anyOf": [{
- "required": [
- "macAddress"
- ]
- },
- {
- "required": [
- "ipAddresses"
- ]
- }
- ],
- "oneOf": [{
- "required": [
- "addresses"
- ]
- },
- {
- "required": [
- "addressRange"
- ]
- }
- ],
- "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 notes 3 and 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": {
+ },
+ "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",
+ "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",
+ "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"
+ }
+ }
+ }
+ }
+ }
+ },
+ "vduIds": {
+ "description": "Reference to the VDU(s) which implement the service accessible via the virtual CP instance. See note.\n",
+ "type": "array",
+ "minItems": 1,
+ "items": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ }
+ },
+ "additionalServiceInfo": {
+ "description": "Additional service identification information of the virtual CP instance.\n",
+ "type": "array",
+ "items": {
+ "description": "This type provides 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 \n termination within the VNF, such as for example a URL path information in an HTTP request required \n to allow a single virtual CP IP address to be used for several HTTP based services that use the \n same port number.\n",
+ "type": "object",
+ "required": [
+ "portInfo"
+ ],
+ "properties": {
+ "portInfo": {
+ "description": "Service port numbers exposed by the virtual CP instance.\n",
+ "minItems": 1,
+ "type": "array",
+ "items": {
+ "description": "This type describes the service identifying port properties exposed by the virtual CP instance.\n",
+ "type": "object",
+ "required": [
+ "name",
+ "port",
+ "portConfigurable"
+ ],
+ "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.\nPermitted values: - TCP - UDP - SCTP\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 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"
- }
+ "enum": [
+ "TCP",
+ "UDP",
+ "SCTP"
+ ]
+ },
+ "port": {
+ "description": "The L4 port number exposed by the virtual CP instance.\n",
+ "type": "integer"
+ },
+ "portConfigurable": {
+ "description": "The Boolean is a data type having two values (true and false).\n",
+ "type": "boolean"
}
- },
- "subnetId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
}
}
+ },
+ "serviceInfo": {
+ "description": "This 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"
}
}
}
+ },
+ "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 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"
}
}
}
},
- "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": "Metadata about this VIP CP.\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 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"
- }
- }
- }
- }
- },
- "extVirtualLinkInfo": {
- "description": "Information about the external VLs the VNF instance is connected to.\n",
- "type": "array",
- "items": {
- "description": "This type represents information about an external VL. It shall comply with the provisions defined in table 5.5.3.2-1.\nNOTE:\tThis attribute reflects the current configuration information that has resulted from merging into this attribute \n the \"VnfExtCpData\" information which was passed as part of the \"ExtVirtualLinkData\" structure in the input of the \n most recent VNF LCM operation such as \"InstantiateVnfRequest\", \"ChangeExtVnfConnectivityRequest\", \"ChangeVnfFlavourRequest\" \n or \"ChangeCurrentVnfPkgRequest\", or in the Grant response. If applying such change results in an empty list of \n \"currentVnfExtCpData\" structure instances, the affected instance of \"ExtVirtualLinkInfo\" shall be removed from its \n parent data structure.\n",
- "type": "object",
- "required": [
- "id",
- "resourceHandle",
- "currentVnfExtCpData"
- ],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceHandle": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
- "type": "string"
- }
- }
- },
- "extLinkPorts": {
- "description": "Link ports of this VL.\n",
+ "extVirtualLinkInfo": {
+ "description": "Information about the external VLs the VNF instance is connected to.\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. It shall comply with the provisions defined in table 5.5.3.9-1.\nNOTE 1:\tThe 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:\tThe value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\" attribute.\n",
+ "description": "This type represents information about an external VL.\nNOTE:\tThis attribute reflects the current configuration information that has resulted from merging into this attribute \n the \"VnfExtCpData\" information which was passed as part of the \"ExtVirtualLinkData\" structure in the input of the \n most recent VNF LCM operation such as \"InstantiateVnfRequest\", \"ChangeExtVnfConnectivityRequest\", \"ChangeVnfFlavourRequest\" \n or \"ChangeCurrentVnfPkgRequest\", or in the Grant response. If applying such change results in an empty list of \n \"currentVnfExtCpData\" structure instances, the affected instance of \"ExtVirtualLinkInfo\" shall be removed from its \n parent data structure.\n",
"type": "object",
"required": [
"id",
- "resourceHandle"
+ "resourceHandle",
+ "currentVnfExtCpData"
],
"properties": {
"id": {
@@ -567,7 +888,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",
+ "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",
"properties": {
"vimConnectionId": {
"description": "An identifier with the intention of being globally unique.\n",
@@ -578,143 +899,293 @@
"type": "string"
},
"resourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
"type": "string"
},
"vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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.\n",
- "type": "string"
- }
- }
- }
- },
- "currentVnfExtCpData": {
- "description": "Allows the API consumer to read the current CP configuration information for the connection of external CPs to the external virtual link. See note.\n",
- "type": "array",
- "items": {
- "description": "This type represents configuration information for external CPs created. * NOTE 1: \tIn case this identifier refers to a CPD with trunking enabled, the external CP instances created\n from this CPD will represent ports in a trunk.\n* NOTE 2: \tWithin one VNF instance, all VNFC instances created from a particular VDU have the same external\n connectivity. Thus, given a particular value of the \"cpdId\" attribute, there shall be one\n \"cpConfig\" entry for each VNFC instance that has been or can be created from a VDU which includes\n a CPD identified by the \"cpdId\" attribute. If the cpConfig represents a subport in a trunk,\n all \"cpConfig\" entries in this list shall have the same segmentationId, which means they are\n connected to the same set of external VLs via the trunk.\n* NOTE 3: \tThe map entry value shall be set to \"null\" in order to delete a \"VnfExtCpConfig\" entry identified\n by a particular key value from the map, i.e. for the disconnection of an existing external\n CP instance addressed by cpInstanceId in the deleted map entry from a particular external\n virtual link, and deletion of that instance in case it represents a subport. Deleting the\n last key from the map removes the affected instance of the \"VnfExtCpData\" structure from\n its parent data structure.\n",
- "type": "object",
- "required": [
- "cpdId"
- ],
- "properties": {
- "cpdId": {
- "description": "An identifier that is unique within a VNF descriptor.\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 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). See note 2 and note 3.\n",
- "type": "object",
- "additionalProperties": {
- "description": "This type represents an externally provided link port or network address information per instance of an external connection point. In case a link port is provided, the VNFM shall use that link port when connecting the external CP to the external VL. In a link port is not provided, the VNFM shall create a link port on the external VL, and use that link port to connect the external CP to the external VL. * NOTE: The following conditions apply to the attributes \"linkPortId\" and \"cpProtocolData\":\n 1) Void.\n 2) At least one of the \"linkPortId\" and \"cpProtocolData\" attributes shall be present for an external\n CP instance representing a subport that is to be created, or an external CP instance that is to be\n created by creating the corresponding VNFC or VNF instance during the current or a subsequent LCM\n operation, or for an existing external CP instance that is to be re-configured or added to a\n 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\n a pre created link port, and the VNFM can use means outside the scope of the present document to obtain\n the pre-configured address information for the connection point from the resource representing\n the link port.\n 5) If both \"cpProtocolData\" and \"linkportId\" are provided, the API consumer shall ensure that the\n cpProtocolData can be used with the pre-created link port referenced by \"linkPortId\".\n",
- "anyOf": [{
- "required": [
- "linkPortId"
- ]
- },
- {
- "required": [
- "cpProtocolData"
- ]
- }
- ],
+ "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.\nNOTE 1:\tThe use cases UC#4 and UC#5 in clause A.4 of ETSI GS NFV-IFA 007 provide examples for such a configuration. NOTE 2:\tThe value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\" attribute.\n",
"type": "object",
+ "required": [
+ "id",
+ "resourceHandle"
+ ],
"properties": {
- "parentCpConfigId": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceHandle": {
+ "required": [
+ "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",
+ "properties": {
+ "vimConnectionId": {
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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"
},
- "linkPortId": {
- "description": "An identifier with the intention of being globally unique.\n",
+ "secondaryCpInstanceId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
"type": "string"
},
- "createExtLinkPort": {
- "description": "Indicates to the VNFM the need to create a dedicated link port for the external CP. If set to True, the VNFM shall create a link port. If set to False, the VNFM shall not create a link port. 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"
+ "trunkResourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "currentVnfExtCpData": {
+ "description": "Allows the API consumer to read the current CP configuration information for the connection of external CPs to the external virtual link. See note.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents configuration information for external CPs created. * NOTE 1: \tIn case this identifier refers to a CPD with trunking enabled, the external CP instances created\n from this CPD will represent ports in a trunk.\n* NOTE 2: \tWithin one VNF instance, all VNFC instances created from a particular VDU have the same external\n connectivity. Thus, given a particular value of the \"cpdId\" attribute, there shall be one\n \"cpConfig\" entry for each VNFC instance that has been or can be created from a VDU which includes\n a CPD identified by the \"cpdId\" attribute. If the cpConfig represents a subport in a trunk,\n all \"cpConfig\" entries in this list shall have the same segmentationId, which means they are\n connected to the same set of external VLs via the trunk.\n* NOTE 3: \tThe map entry value shall be set to \"null\" in order to delete a \"VnfExtCpConfig\" entry identified\n by a particular key value from the map, i.e. for the disconnection of an existing external\n CP instance addressed by cpInstanceId in the deleted map entry from a particular external\n virtual link, and deletion of that instance in case it represents a subport. Deleting the\n last key from the map removes the affected instance of the \"VnfExtCpData\" structure from\n its parent data structure.\n* NOTE 4: If, as defined by the input parameters of a \"ChangeVnfFlavour\", \"ChangeExtVnfConnectivity\" or\n \"ChangeCurrentVnfPkg\" operation, a cpConfig map entry identified by a particular map key value \n is moved into another \"ExtVirtualLinkData\" or \"VnfExtCpData\" structure, this particular cpConfig\n map entry may be used by an external CP instance different than the one that has used it before the\n operation, or by no external CP instance at all. Renaming a CPD identifier during the \"changeCurrentVnfPkg\"\n operation does not count as moving the related \"cpConfig\" map entries to a new \"extCpData\" structure.\n",
+ "type": "object",
+ "required": [
+ "cpdId"
+ ],
+ "properties": {
+ "cpdId": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
},
- "cpProtocolData": {
- "description": "Parameters for configuring the network protocols on the link port that connects the CP to a VL. See note.\n",
- "type": "array",
- "items": {
- "description": "This type represents network protocol data. * NOTE:\tThis attribute allows to signal the addition of further types of layer and protocol\n in future versions of the present document in a backwards-compatible way. In the current\n version of the present document, only IP over Ethernet is supported.\n",
- "type": "object",
- "required": [
- "layerProtocol"
+ "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 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",
+ "anyOf": [
+ {
+ "required": [
+ "linkPortId"
+ ]
+ },
+ {
+ "required": [
+ "cpProtocolData"
+ ]
+ },
+ {
+ "required": [
+ "netAttDefResourceId"
+ ]
+ }
],
+ "type": "object",
"properties": {
- "layerProtocol": {
- "description": "Identifier of layer(s) and protocol(s). See note.\n",
- "type": "string",
- "enum": [
- "IP_OVER_ETHERNET"
- ]
+ "parentCpConfigId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
},
- "ipOverEthernet": {
- "description": "This type represents network address data for IP over Ethernet. * NOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. * NOTE 2:\tExactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present. * NOTE 3:\tIf the CP instance represents a subport in a trunk, segmentationId shall be present.\n Otherwise it shall not be present.\n* NOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the actual\n network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header\n of the packets or it may be an identifier used between the application and the NFVI networking\n infrastructure to identify the network sub-interface of the trunk port in question. In the latter\n case the NFVI infrastructure will map this local segmentationId to whatever segmentationId is\n actually used by the NFVIΓÇÖs transport technology.\n",
- "type": "object",
- "anyOf": [{
- "required": [
- "macAddress"
- ]
- },
- {
- "required": [
- "ipAddresses"
- ]
- }
- ],
- "oneOf": [{
- "required": [
- "fixedAddresses"
- ]
- },
- {
- "required": [
- "numDynamicAddresses"
- ]
- },
- {
- "required": [
- "ipAddressRange"
- ]
- }
- ],
- "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: -\tVLAN: the subport uses VLAN as encapsulation type. -\tINHERIT: the subport gets its segmentation type from the network itΓÇÖs 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": {
+ "linkPortId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "createExtLinkPort": {
+ "description": "Indicates to the VNFM the need to create a dedicated link port for the external CP. If set to True, the VNFM shall create a link port. If set to False, the VNFM shall not create a link port. This attribute is only applicable for external CP instances without a floating IP address that expose a virtual IP 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 2.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents network protocol data. * NOTE:\tThis attribute allows to signal the addition of further types of layer and protocol\n in future versions of the present document in a backwards-compatible way. In the current\n 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:\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 network address data for IP over Ethernet to assign to the external CP. * NOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. * NOTE 2:\tExactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present. * NOTE 3:\tIf the CP instance represents a subport in a trunk, segmentationId shall be present.\n Otherwise it shall not be present.\n* NOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the actual\n network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header\n of the packets or it may be an identifier used between the application and the NFVI networking\n infrastructure to identify the network sub-interface of the trunk port in question. In the latter\n case the NFVI infrastructure will map this local segmentationId to whatever segmentationId is\n actually used by the NFVI's transport technology.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "required": [
+ "macAddress"
+ ]
+ },
+ {
+ "required": [
+ "ipAddresses"
+ ]
+ }
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "fixedAddresses"
+ ]
+ },
+ {
+ "required": [
+ "numDynamicAddresses"
+ ]
+ },
+ {
+ "required": [
+ "ipAddressRange"
+ ]
+ }
+ ],
+ "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: -\tVLAN: the subport uses VLAN as encapsulation type. -\tINHERIT: the subport gets its segmentation type from the network itΓÇÖs 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"
+ ],
+ "properties": {
+ "type": {
+ "description": "The type of the IP addresses. Permitted values: IPV4, IPV6.\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
+ },
+ "fixedAddresses": {
+ "description": "Fixed addresses to assign (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"
+ }
+ },
+ "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. 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.\n",
+ "type": "string"
+ }
+ }
+ }
+ }
+ }
+ },
+ "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",
"type": "object",
"required": [
"type"
@@ -728,129 +1199,144 @@
"IPV6"
]
},
- "fixedAddresses": {
- "description": "Fixed addresses to assign (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"
- }
- },
- "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. 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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
+ "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 2, 3 and 4.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\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 contains 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": {
+ "required": [
+ "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",
+ "properties": {
+ "vimConnectionId": {
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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 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"
+ }
}
+ },
+ "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 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 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"
+ }
}
}
}
}
}
}
- }
- }
- }
- },
- "extManagedVirtualLinkInfo": {
- "description": "Information about the externally managed internal VLs of the VNF instance. See note 5 and note 6. 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 VNF internal VL shall indicate so by referencing to the same VnfVirtualLinkDesc and externally-managed multi-site VL instance (refer to clause 5.5.3.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": "array",
- "items": {
- "type": "object",
- "required": [
- "id",
- "vnfVirtualLinkDescId",
- "networkResource"
- ],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfVirtualLinkDescId": {
- "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"
- },
- "networkResource": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
- "type": "string"
- }
- }
},
- "vnfLinkPorts": {
- "description": "Link ports of this VL.\n",
+ "extManagedVirtualLinkInfo": {
+ "description": "Information about the externally managed internal VLs of the VNF instance. See note 5 and note 6. 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 VNF internal VL shall indicate so by referencing to the same VnfVirtualLinkDesc and externally-managed multi-site VL instance (refer to clause 5.5.3.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": "array",
"items": {
- "description": "This type represents a link port of an internal VL of a VNF. It shall comply with the provisions defined in table 5.5.3.8 1.\nNOTE 1: Either cpInstanceId with cpInstanceType set to \"EXT_CP\" or any combination of cpInstanceId\n with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId (i.e. one or both of them) shall be \n present for a VnfLinkPortInfo. In case both cpInstanceId with cpInstanceType set to \"VNFC_CP\" \n and vipCpInstanceId are present, the two different CP instances share the linkport.\nNOTE 2: Annex A.4 of ETSI GS NFV-IFA 007 provides examples for configurations where both vipCpInstanceId\n and vnfcCpInstanceId are present (UC#5 and UC#5-b), only vnfcCpInstanceId is present (UC#2), or \n only vipCpInstanceId is present (UC6 and UC#6-b).\nNOTE 3: The value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\"\n attribute.\n",
+ "description": "This type provides information about an externally-managed virtual link.\n",
"type": "object",
"required": [
"id",
- "resourceHandle"
+ "vnfVirtualLinkDescId",
+ "networkResource"
],
"properties": {
"id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfVirtualLinkDescId": {
"description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
"type": "string"
},
- "resourceHandle": {
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "networkResource": {
"required": [
"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",
+ "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",
"properties": {
"vimConnectionId": {
"description": "An identifier with the intention of being globally unique.\n",
@@ -861,825 +1347,1253 @@
"type": "string"
},
"resourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
"type": "string"
},
"vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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",
+ "vnfLinkPorts": {
+ "description": "Link ports of this VL.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents a link port of an internal VL of a VNF.\nNOTE 1: Either cpInstanceId with cpInstanceType set to \"EXT_CP\" or any combination of cpInstanceId\n with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId (i.e. one or both of them) shall be \n present for a VnfLinkPortInfo. In case both cpInstanceId with cpInstanceType set to \"VNFC_CP\" \n and vipCpInstanceId are present, the two different CP instances share the linkport.\nNOTE 2: Annex A.4 of ETSI GS NFV-IFA 007 provides examples for configurations where both vipCpInstanceId\n and vnfcCpInstanceId are present (UC#5 and UC#5-b), only vnfcCpInstanceId is present (UC#2), or \n only vipCpInstanceId is present (UC6 and UC#6-b).\nNOTE 3: The value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\"\n attribute.\n",
+ "type": "object",
+ "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": {
+ "required": [
+ "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",
+ "properties": {
+ "vimConnectionId": {
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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.\nPermitted values: - VNFC_CP: The link port is connected to a VNFC CP. -\tEXT_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 the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "vnfNetAttDefResource": {
+ "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 contains 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": {
+ "required": [
+ "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",
+ "properties": {
+ "vimConnectionId": {
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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 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 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"
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ },
+ "monitoringParameters": {
+ "description": "Active monitoring parameters.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": [
+ "id",
+ "performanceMetric"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier that is unique within a VNF descriptor.\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.\nPermitted values: - VNFC_CP: The link port is connected to a VNFC CP. -\tEXT_CP: The link port is associated to an external CP. See note 1.\n",
- "type": "string",
- "enum": [
- "VNFC_CP",
- "EXT_CP"
- ]
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
},
- "vipCpInstanceId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "name": {
+ "description": "Human readable name of the monitoring parameter, as defined in the VNFD.\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.\n",
+ "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"
}
}
}
- }
- }
- }
- },
- "monitoringParameters": {
- "description": "Active monitoring parameters.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": [
- "id",
- "performanceMetric"
- ],
- "properties": {
- "id": {
- "description": "An identifier that is unique within a VNF descriptor.\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. * NOTE 1:\tETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on TOSCA specifications. * NOTE 2:\tA VNFC CP is \"connected to\" an external CP if the VNFC CP is connected to an internal VL that\n exposes an external CP. A VNFC CP is \"exposed as\" an external CP if it is connected directly\n to an external VL.\n* NOTE 3:\tThe information can be omitted because it is already available as part of the external CP information.\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"
- },
- "vduId": {
- "description": "An identifier that is unique within a VNF descriptor.\n",
- "type": "string"
},
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
+ "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"
},
- "computeResource": {
+ "vnfcResourceInfo": {
+ "description": "This type represents the information on virtualised compute and storage resources used by a VNFC in a VNF instance. Depending on the form of virtualisation container of the VNFC:\n - For a VNFC based on VM, a reference to the corresponding VirtualCompute shall be provided, and\n - For a VNFC based on OS container(s), a reference to the Compute MCIO shall be provided. Hence, exposure \n of information by the VNFM to the NFVO is at the MCIO level.\nIn addition, the references to the storage resources depend on the form of the VNFC:\n - For a VNFC based on VM, storage resource identifiers shall refer to VirtualStorage resources, and\n - For a VNFC based on OS container(s), storage resource identifiers shall refer to Storage MCIOs.\n\n\n* NOTE 1:\tETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on TOSCA specifications. * NOTE 2:\tA VNFC CP is \"connected to\" an external CP if the VNFC CP is connected to an internal VL that\n exposes an external CP. A VNFC CP is \"exposed as\" an external CP if it is connected directly\n to an external VL.\n* NOTE 3:\tThe information can be omitted because it is already available as part of the external CP information. * NOTE 4: If only the value or the presence of this attribute is changed in the \"VnfcResourceInfo\" structure by \n an LCM operation occurrence, this does not represent a change that requires including a related \"AffectedVnfc\"\n structure in the VNF LCM operation occurrence notifications or the \"VnfLcmOpOcc\" structure related to \n this LCM operation occurrence.\n* NOTE 5: 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 internal CP, e.g. to build \n a link redundant mated pair in SR-IOV cases.\n* NOTE 6: When more than one netAttDefResourceId is indicated, all shall belong to the same namespace.\n",
+ "type": "object",
"required": [
- "resourceId"
+ "id",
+ "vduId",
+ "computeResource"
],
- "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",
"properties": {
- "vimConnectionId": {
- "description": "An identifier with the intention of being globally unique.\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"
},
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
+ "vduId": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
"type": "string"
},
- "resourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
"type": "string"
},
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
- "type": "string"
- }
- }
- },
- "storageResourceIds": {
- "description": "References to the VirtualStorage resources. 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": "All the CPs of the VNFC instance.\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 VNF descriptor.\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. The information can be omitted because it is already available as part of the external CP information. See note 3.\n",
- "type": "array",
- "items": {
- "description": "This type describes the protocol layer(s) that a CP uses together with protocol-related information, like addresses. It shall comply with the provisions defined in table 5.5.3.9b-1.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the \n present document in a backwards-compatible way. In the current version of the present document, only IP over \n Ethernet is supported.\n",
+ "computeResource": {
+ "required": [
+ "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",
+ "properties": {
+ "vimConnectionId": {
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At least one attribute shall be present.\n",
"type": "object",
- "required": [
- "layerProtocol"
- ],
"properties": {
- "layerProtocol": {
- "description": "The identifier of layer(s) and protocol(s) associated to the network address information.\nPermitted values: IP_OVER_ETHERNET See note.\n",
- "type": "string",
- "enum": [
- "IP_OVER_ETHERNET"
- ]
+ "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"
},
- "ipOverEthernet": {
- "description": "This type represents information about a network address that has been assigned. It shall comply with the provisions defined in table 5.5.3.10-1.\nNOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, segmentationId shall be present. \n Otherwise it shall not be present.\nNOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the \n actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the \n transport header of the packets or it may be an identifier used between the application \n and the NFVI networking infrastructure to identify the network sub-interface of the trunk \n port in question. In the latter case the NFVI infrastructure will map this local segmentationId \n to whatever segmentationId is actually used by the NFVIΓÇÖs transport technology.\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 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"
+ }
+ }
+ },
+ "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 MCIO(s). 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": "All the CPs of the VNFC instance.\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 VNF descriptor.\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. The information can be omitted because it is already available as part of the external CP information. See note 3.\n",
+ "type": "array",
+ "items": {
+ "description": "This type describes the protocol layer(s) that a CP uses together with protocol-related information, like addresses.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the \n present document in a backwards-compatible way. In the current version of the present document, only IP over \n Ethernet is supported.\n",
"type": "object",
- "anyOf": [{
- "required": [
- "macAddress"
- ]
- },
- {
- "required": [
- "ipAddresses"
- ]
- }
- ],
- "oneOf": [{
- "required": [
- "addresses"
- ]
- },
- {
- "required": [
- "addressRange"
- ]
- }
+ "required": [
+ "layerProtocol"
],
"properties": {
- "macAddress": {
- "description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
+ "layerProtocol": {
+ "description": "The identifier of layer(s) and protocol(s) associated to the network address information.\nPermitted values:\n - IP_OVER_ETHERNET\n - IP_FOR_VIRTUAL_CP\nSee note.\n",
"type": "string",
- "format": "MAC"
- },
- "segmentationId": {
- "description": "Identification of the network segment to which the Cp instance connects to. See notes 3 and 4.\n",
- "type": "string"
+ "enum": [
+ "IP_OVER_ETHERNET",
+ "IP_FOR_VIRTUAL_CP"
+ ]
},
- "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"
- ],
- "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. See note 2.\n",
+ "ipOverEthernet": {
+ "description": "This type represents information about a network address that has been assigned.\nNOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, segmentationId shall be present. \n Otherwise it shall not be present.\nNOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the \n actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the \n transport header of the packets or it may be an identifier used between the application \n and the NFVI networking infrastructure to identify the network sub-interface of the trunk \n port in question. In the latter case the NFVI infrastructure will map this local segmentationId \n to whatever segmentationId is actually used by the NFVIΓÇÖs transport technology.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "required": [
+ "macAddress"
+ ]
+ },
+ {
+ "required": [
+ "ipAddresses"
+ ]
+ }
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "addresses"
+ ]
+ },
+ {
+ "required": [
+ "addressRange"
+ ]
+ }
+ ],
+ "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 notes 3 and 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": [
- "minAddress",
- "maxAddress"
+ "type"
],
"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": {
+ "description": "The type of the IP addresses. Permitted values: IPV4, IPV6.\n",
"type": "string",
- "format": "IP"
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
},
- "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"
+ "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. 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.\n",
+ "type": "string"
}
}
- },
- "subnetId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\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"
+ }
+ }
+ }
+ }
+ }
+ },
+ "vnfLinkPortId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "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"
+ },
+ "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 5 and 6. 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 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 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"
+ }
+ }
+ }
+ },
+ "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 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"
+ }
+ }
+ },
+ "vnfVirtualLinkResourceInfo": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by an internal VL instance in a VNF instance. NOTE: If only the value or the presence of this attribute is changed in the \"VnfVirtualLinkResourceInfo\" \n structure by an LCM operation occurrence, this does not represent a change that requires including a \n related \"AffectedVirtualLink\" structure in the VNF LCM operation occurrence notifications or the \n \"VnfLcmOpOcc\" structure related to this LCM operation occurrence.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "vnfVirtualLinkDescId",
+ "networkResource",
+ "vnfLinkPorts"
+ ],
+ "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"
+ },
+ "vnfVirtualLinkDescId": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "networkResource": {
+ "required": [
+ "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",
+ "properties": {
+ "vimConnectionId": {
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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": {
+ "description": "This type represents a link port of an internal VL of a VNF.\nNOTE 1: Either cpInstanceId with cpInstanceType set to \"EXT_CP\" or any combination of cpInstanceId\n with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId (i.e. one or both of them) shall be \n present for a VnfLinkPortInfo. In case both cpInstanceId with cpInstanceType set to \"VNFC_CP\" \n and vipCpInstanceId are present, the two different CP instances share the linkport.\nNOTE 2: Annex A.4 of ETSI GS NFV-IFA 007 provides examples for configurations where both vipCpInstanceId\n and vnfcCpInstanceId are present (UC#5 and UC#5-b), only vnfcCpInstanceId is present (UC#2), or \n only vipCpInstanceId is present (UC6 and UC#6-b).\nNOTE 3: The value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\"\n attribute.\n",
+ "type": "object",
+ "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": {
+ "required": [
+ "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",
+ "properties": {
+ "vimConnectionId": {
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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 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"
+ }
}
+ },
+ "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.\nPermitted values: - VNFC_CP: The link port is connected to a VNFC CP. -\tEXT_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 the CISM or other resource provider. It is expected to be unique within the VIM instance.\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 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"
+ }
+ }
+ },
+ "virtualStorageResourceInfo": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance.\nNOTE: If only the value or the presence of this attribute is changed in the \"VirtualStorageResourceInfo\" structure by an LCM operation occurrence, this does not represent a change that requires including a related \"AffectedVirtualStorage\" structure in the VNF LCM operation occurrence notifications or the \"VnfLcmOpOcc\" structure related to this LCM operation occurrence.\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": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "storageResource": {
+ "required": [
+ "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",
+ "properties": {
+ "vimConnectionId": {
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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 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"
+ }
}
+ },
+ "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 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"
+ }
+ }
+ },
+ "vnfcInfo": {
+ "description": "Information about the VNFC instances.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the information about a VNFC instance that is part of a VNF instance. * NOTE:\tThis allows to represent the error condition that a VNFC instance has lost its resources.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "vduId",
+ "vnfcState"
+ ],
+ "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"
},
- "vnfLinkPortId": {
+ "vduId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\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"
+ },
+ "vnfcState": {
"description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
"type": "string"
},
- "parentCpId": {
+ "vnfcConfigurableProperties": {
"description": "This 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"
+ }
+ }
+ }
+ },
+ "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. Within the CISM, an MCIO controller monitors the actual state of an MCIO representing the set of VNFC instances realized by one or a set of OS containers and compare it to the desired state as specified in the respective declarative descriptor. It triggers actions toward the CIS to align the actual to the desired state. Monitoring the actual state includes monitoring the number of MCIO instances available at any specific point in time. In addition, an MCIO controller maintains properties and runtime information on the MCIO instances which have been created based on the same VDU. The McioInfo data structure provides the runtime information on the MCIOs obtained from the MCIO controller.\nNOTE: There are different types of MCIOs. The set of VNFC instances based on the same VDU is represented \n by one MCIO, e.g. of type Deployment. Each individual VNFC instance is represented by another type \n of MCIO, e.g. a POD.\n\nRuntime information of the set of OS containers realizing an individual VNFC instance is not part of the McioInfo data structure; such runtime information is provided in the ResourceHandle data structure referenced from the VnfcResourceInfo. The McioInfo does not provide runtime information of a constituent VNFC instance created based on a specific VDU.\nNOTE 1: The type of MCIO as specified in the declarative descriptor of the MCIO, and that can be read from \n the CISM. EXAMPLE: In case of MCIOs managed by Kubernetes®, the type of MCIO corresponds to the \n “kind” property of the declarative descriptor.\nNOTE 2: If the attribute additionalInfo is present, it may contain runtime information on the actual and \n desired state of the MCIO(s). \nNOTE 3: When the container infrastructure service is a Kubernetes® instance, the mcioId is the combined \n values from the kind and name fields of the Kubernetes resource object, separated by a slash. \n Example: \"Deployment/abcd\". \nNOTE 4: When the container infrastructure service is a Kubernetes® instance, the mcioName is the name \n field of the resource object. \n",
+ "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"
},
- "metadata": {
+ "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": "An identifier that is unique within a VNF descriptor.\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 5.5.4.9. Additional values are also permitted. See note 1.\n",
+ "type": "string",
+ "enum": [
+ "Deployment",
+ "Statefulset"
+ ]
+ },
+ "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 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"
}
}
}
- },
- "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 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"
}
}
- }
- },
- "vnfVirtualLinkResourceInfo": {
- "description": "Information about the virtualised network resources used by the VLs of the VNF instance. See note 6. 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": "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",
+ },
+ "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 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"
+ },
+ "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 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"
+ },
+ "_links": {
+ "description": "Links to resources related to this resource.\n",
"type": "object",
"required": [
- "id",
- "vnfVirtualLinkDescId",
- "networkResource",
- "vnfLinkPorts"
+ "self"
],
"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"
+ "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"
+ }
+ }
},
- "vnfVirtualLinkDescId": {
- "description": "An identifier that is unique within a VNF descriptor.\n",
- "type": "string"
+ "indicators": {
+ "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"
+ }
+ }
},
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
+ "instantiate": {
+ "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"
+ }
+ }
+ },
+ "terminate": {
+ "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"
+ }
+ }
},
- "networkResource": {
+ "scale": {
+ "description": "This type represents a link to a resource using an absolute URI.\n",
+ "type": "object",
"required": [
- "resourceId"
+ "href"
],
+ "properties": {
+ "href": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ }
+ }
+ },
+ "scaleToLevel": {
+ "description": "This type represents a link to a resource using an absolute URI.\n",
"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",
+ "required": [
+ "href"
+ ],
"properties": {
- "vimConnectionId": {
- "description": "An identifier with the intention of being globally unique.\n",
+ "href": {
+ "description": "String formatted according to IETF RFC 3986.\n",
"type": "string"
- },
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
+ }
+ }
+ },
+ "changeFlavour": {
+ "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"
- },
- "resourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ }
+ }
+ },
+ "heal": {
+ "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"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
+ }
+ }
+ },
+ "operate": {
+ "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"
+ }
+ }
+ },
+ "changeExtConn": {
+ "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"
+ }
+ }
+ },
+ "createSnapshot": {
+ "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"
+ }
+ }
+ },
+ "revertToSnapshot": {
+ "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"
+ }
+ }
+ },
+ "changeCurrentVnfPkg": {
+ "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"
}
}
- },
- "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": {
- "description": "This type represents a link port of an internal VL of a VNF. It shall comply with the provisions defined in table 5.5.3.8 1.\nNOTE 1: Either cpInstanceId with cpInstanceType set to \"EXT_CP\" or any combination of cpInstanceId\n with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId (i.e. one or both of them) shall be \n present for a VnfLinkPortInfo. In case both cpInstanceId with cpInstanceType set to \"VNFC_CP\" \n and vipCpInstanceId are present, the two different CP instances share the linkport.\nNOTE 2: Annex A.4 of ETSI GS NFV-IFA 007 provides examples for configurations where both vipCpInstanceId\n and vnfcCpInstanceId are present (UC#5 and UC#5-b), only vnfcCpInstanceId is present (UC#2), or \n only vipCpInstanceId is present (UC6 and UC#6-b).\nNOTE 3: The value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\"\n attribute.\n",
- "type": "object",
+ }
+ }
+ }
+ }
+ },
+ "vnfcSnapshots": {
+ "description": "Information about VNFC snapshots constituting this VNF snapshot.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents a VNFC snapshot. * NOTE 1:\tThe identifier of the compute snapshot resource is assigned during creation of a VNFC\n snapshot being returned from the VIM as output data in the response message of the individual\n resource operations. This attribute shall only be present for a VNFC snapshot that has been\n newly created by the VNFM as a result of the \"Create VNF snapshot task\".\n NOTE 2:\tThe identifier of the storage snapshot resource is assigned during creation of a VNFC snapshot\n being returned from the VIM as output data in the response message of the individual resource\n operations. This attribute shall only be present for a VNFC snapshot with an associated storage\n 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",
+ "creationStartedAt",
+ "vnfcResourceInfoId"
+ ],
+ "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 to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "creationFinishedAt": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "vnfcResourceInfoId": {
+ "description": "This type represents the information about a VNFC instance that is part of a VNF instance. * NOTE:\tThis allows to represent the error condition that a VNFC instance has lost its resources.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "vduId",
+ "vnfcState"
+ ],
+ "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"
+ },
+ "vduId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\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"
+ },
+ "vnfcState": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "vnfcConfigurableProperties": {
+ "description": "This 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"
+ }
+ }
+ },
+ "computeSnapshotResource": {
+ "required": [
+ "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",
+ "properties": {
+ "vimConnectionId": {
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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": "Mapping of the storage resources associated to the VNFC with the storage snapshot resources.\n",
+ "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"
+ },
+ "storageSnapshotResource": {
"required": [
- "id",
- "resourceHandle"
+ "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",
"properties": {
- "id": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "vimConnectionId": {
+ "description": "An identifier with the intention of being globally unique.\n",
"type": "string"
},
- "resourceHandle": {
- "required": [
- "resourceId"
- ],
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At least one attribute shall be present.\n",
"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",
"properties": {
- "vimConnectionId": {
- "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",
+ "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"
},
- "resourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\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"
},
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\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 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"
}
}
},
- "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.\nPermitted values: - VNFC_CP: The link port is connected to a VNFC CP. -\tEXT_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.\n",
+ "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"
}
}
}
- },
- "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 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"
- }
- }
- }
- },
- "vnfVirtualStorageResourceInfo": {
- "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": "An identifier that is unique within a VNF descriptor.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "storageResource": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\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 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"
- }
- }
- }
- },
- "vnfcInfo": {
- "description": "Information about the VNFC instances.\n",
- "type": "array",
- "items": {
- "description": "This type represents the information about a VNFC instance that is part of a VNF instance. * NOTE:\tThis allows to represent the error condition that a VNFC instance has lost its resources.\n",
- "type": "object",
- "required": [
- "id",
- "vduId",
- "vnfcState"
- ],
- "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"
- },
- "vduId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\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"
- },
- "vnfcState": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "vnfcConfigurableProperties": {
- "description": "This 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"
}
+ },
+ "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 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"
}
}
}
- }
- },
- "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 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"
- },
- "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 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"
- },
- "_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 using an absolute URI.\n",
- "type": "object",
- "required": [
- "href"
- ],
- "properties": {
- "href": {
- "description": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- }
- }
- },
- "indicators": {
- "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"
- }
- }
- },
- "instantiate": {
- "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"
- }
- }
- },
- "terminate": {
- "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"
- }
- }
- },
- "scale": {
- "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"
- }
- }
- },
- "scaleToLevel": {
- "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"
- }
- }
- },
- "changeFlavour": {
- "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"
- }
- }
- },
- "heal": {
- "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"
- }
- }
- },
- "operate": {
- "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"
- }
- }
- },
- "changeExtConn": {
- "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"
- }
- }
- },
- "createSnapshot": {
- "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"
- }
- }
- },
- "revertToSnapshot": {
- "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"
- }
- }
- }
+ },
+ "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 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"
}
}
- }
- },
- "vnfcSnapshots": {
- "description": "Information about VNFC snapshots constituting this VNF snapshot.\n",
- "type": "array",
- "items": {
- "description": "This type represents a VNFC snapshot. * NOTE 1:\tThe identifier of the compute snapshot resource is assigned during creation of a VNFC\n snapshot being returned from the VIM as output data in the response message of the individual\n resource operations. This attribute shall only be present for a VNFC snapshot that has been\n newly created by the VNFM as a result of the \"Create VNF snapshot task\".\n NOTE 2:\tThe identifier of the storage snapshot resource is assigned during creation of a VNFC snapshot\n being returned from the VIM as output data in the response message of the individual resource\n operations. This attribute shall only be present for a VNFC snapshot with an associated storage\n resource and that has been newly created by the VNFM as a result of the \"Create VNF snapshot task\".\n",
+ },
+ "_links": {
+ "description": "Links to resources related to this resource.\n",
"type": "object",
"required": [
- "id",
- "vnfcInstanceId",
- "creationStartedAt",
- "vnfcResourceInfoId"
+ "self"
],
"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 to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "creationFinishedAt": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "vnfcResourceInfoId": {
- "description": "This type represents the information about a VNFC instance that is part of a VNF instance. * NOTE:\tThis allows to represent the error condition that a VNFC instance has lost its resources.\n",
+ "self": {
+ "description": "This type represents a link to a resource using an absolute URI.\n",
"type": "object",
"required": [
- "id",
- "vduId",
- "vnfcState"
- ],
- "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"
- },
- "vduId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\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"
- },
- "vnfcState": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "vnfcConfigurableProperties": {
- "description": "This 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"
- }
- }
- },
- "computeSnapshotResource": {
- "required": [
- "resourceId"
+ "href"
],
- "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",
"properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
+ "href": {
+ "description": "String formatted according to IETF RFC 3986.\n",
"type": "string"
}
}
},
- "storageSnapshotResources": {
- "description": "Mapping of the storage resources associated to the VNFC with the storage snapshot resources.\n",
+ "takenFrom": {
+ "description": "This type represents a link to a resource using an absolute URI.\n",
"type": "object",
"required": [
- "storageResourceId"
+ "href"
],
"properties": {
- "storageResourceId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "href": {
+ "description": "String formatted according to IETF RFC 3986.\n",
"type": "string"
- },
- "storageSnapshotResource": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\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 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"
}
}
}
- },
- "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 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"
}
}
- }
}
\ No newline at end of file
diff --git a/SOL002/VNFLifecycleManagement-API/schemas/subscription.schema.json b/SOL002/VNFLifecycleManagement-API/schemas/subscription.schema.json
index c86be18a0cd5dfb678cbf90df540243272f97782..bd91d402b116c5be910e4ca8871c98e6a41f7025 100644
--- a/SOL002/VNFLifecycleManagement-API/schemas/subscription.schema.json
+++ b/SOL002/VNFLifecycleManagement-API/schemas/subscription.schema.json
@@ -13,14 +13,16 @@
"type": "string"
},
"filter": {
- "description": "This type represents a subscription filter related to notifications about VNF lifecycle changes. At a particular nesting level in the filter structure, the following applies: All attributes shall match in order for the filter to match (logical \"and\" between different filter attributes). If an attribute is an array, the attribute shall match if at least one of the values in the array matches (logical \"or\" between the values of one filter attribute).\n",
+ "description": "This type represents a subscription filter related to notifications about VNF lifecycle changes.\nAt a particular nesting level in the filter structure, the following applies: All attributes shall match in order for the filter to match (logical \"and\" between different filter attributes). If an attribute is an array, the attribute shall match if at least one of the values in the array matches (logical \"or\" between the values of one filter attribute).\nNOTE:\tThe permitted values of the \"notificationTypes\" attribute are spelled exactly as the names of \n the notification types to facilitate automated code generation systems.\n",
"type": "object",
"properties": {
"vnfInstanceSubscriptionFilter": {
- "description": "This type represents subscription filter criteria to match VNF instances.\n",
+ "description": "This type represents subscription filter criteria to match VNF instances. * NOTE 1:\tThe attributes \"vnfdIds\" and \"vnfProductsFromProviders\" are alternatives to reference to VNF instances\n that are based on certain VNFDs in a filter. They should not be used both in the same filter instance,\n but one alternative should be chosen.\n NOTE 2:\tThe attributes \"vnfInstanceIds\" and \"vnfInstanceNames\" are alternatives to reference to particular VNF\n instances in a filter. They should not be used both in the same filter instance, but one alternative\n should be chosen.\n",
"type": "object",
- "anyOf": [{
- "oneOf": [{
+ "anyOf": [
+ {
+ "oneOf": [
+ {
"required": [
"vnfdId"
]
@@ -33,7 +35,8 @@
]
},
{
- "oneOf": [{
+ "oneOf": [
+ {
"required": [
"vnfInstanceIds"
]
@@ -48,7 +51,7 @@
],
"properties": {
"vnfdIds": {
- "description": "If present, match VNF instances that were created based on a VNFD identified by one of the vnfdId values listed in this attribute. The attributes \"vnfdIds\" and \"vnfProductsFromProviders\" are alternatives to reference to VNF instances that are based on certain VNFDs in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n",
+ "description": "If present, match VNF instances that were created based on a VNFD identified by one of the vnfdId values listed in this attribute. See note 1.\n",
"type": "array",
"items": {
"description": "An identifier with the intention of being globally unique.\n",
@@ -56,7 +59,7 @@
}
},
"vnfProductsFromProviders": {
- "description": "If present, match VNF instances that belong to VNF products from certain providers. The attributes \"vnfdIds\" and \"vnfProductsFromProviders\" are alternatives to reference to VNF instances that are based on certain VNFDs in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n",
+ "description": "If present, match VNF instances that belong to VNF products from certain providers. See note 1.\n",
"type": "array",
"items": {
"type": "object",
@@ -112,7 +115,7 @@
}
},
"vnfInstanceIds": {
- "description": "If present, match VNF instances with an instance identifier listed in this attribute. The attributes \"vnfInstanceIds\" and \"vnfInstanceNames\" are alternatives to reference to particular VNF Instances in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n",
+ "description": "If present, match VNF instances with an instance identifier listed in this attribute. See note 2.\n",
"type": "array",
"items": {
"description": "An identifier with the intention of being globally unique.\n",
@@ -120,7 +123,7 @@
}
},
"vnfInstanceNames": {
- "description": "If present, match VNF instances with a VNF Instance Name listed in this attribute. The attributes \"vnfInstanceIds\" and \"vnfInstanceNames\" are alternatives to reference to particular VNF Instances in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n",
+ "description": "If present, match VNF instances with a VNF Instance Name listed in this attribute. See note 2.\n",
"type": "array",
"items": {
"type": "string"
@@ -129,7 +132,7 @@
}
},
"notificationTypes": {
- "description": "Match particular notification types. Permitted values: * VnfLcmOperationOccurrenceNotification * VnfIdentifierCreationNotification * VnfIdentifierDeletionNotification The permitted values of the \"notificationTypes\" attribute are spelled exactly as the names of the notification types to facilitate automated code generation systems.\n",
+ "description": "Match particular notification types. \nPermitted values: -\tVnfLcmOperationOccurrenceNotification -\tVnfIdentifierCreationNotification -\tVnfIdentifierDeletionNotification See note.\n",
"type": "array",
"items": {
"type": "string",
@@ -144,7 +147,7 @@
"description": "Match particular VNF lifecycle operation types for the notification of type VnfLcmOperationOccurrenceNotification. May be present if the \"notificationTypes\" attribute contains the value \"VnfLcmOperationOccurrenceNotification\", and shall be absent otherwise.\n",
"type": "array",
"items": {
- "description": "Value | Description ------|------------ INSTANTIATE | Represents the \"Instantiate VNF\" LCM operation. SCALE | Represents the \"Scale VNF\" LCM operation. SCALE_TO_LEVEL | Represents the \"Scale VNF to Level\" LCM operation. CHANGE_FLAVOUR | Represents the \"Change VNF Flavour\" LCM operation. TERMINATE | Represents the \"Terminate VNF\" LCM operation. HEAL | Represents the \"Heal VNF\" LCM operation. OPERATE | Represents the \"Operate VNF\" LCM operation. CHANGE_EXT_CONN | Represents the \"Change external VNF connectivity\" LCM operation. MODIFY_INFO | Represents the \"Modify VNF Information\" LCM operation. CREATE_SNAPSHOT | Represents the \"Create VNF Snapshot\" LCM operation. REVERT_TO_SNAPSHOT | Represents the “Revert-To VNF Snapshot\" LCM operation. CHANGE_VNFPKG | Represents the \"Change current VNF package\" LCM operation.\n",
+ "description": "The enumeration LcmOpType defines the permitted values to represent VNF lifecycle operation types in VNF lifecycle management operation occurrence resources and VNF lifecycle management operation occurrence notifications.\nValue | Description ------|------------ INSTANTIATE | Represents the \"Instantiate VNF\" LCM operation. SCALE | Represents the \"Scale VNF\" LCM operation. SCALE_TO_LEVEL | Represents the \"Scale VNF to Level\" LCM operation. CHANGE_FLAVOUR | Represents the \"Change VNF Flavour\" LCM operation. TERMINATE | Represents the \"Terminate VNF\" LCM operation. HEAL | Represents the \"Heal VNF\" LCM operation. OPERATE | Represents the \"Operate VNF\" LCM operation. CHANGE_EXT_CONN | Represents the \"Change external VNF connectivity\" LCM operation. MODIFY_INFO | Represents the \"Modify VNF Information\" LCM operation. CREATE_SNAPSHOT | Represents the \"Create VNF Snapshot\" LCM operation. REVERT_TO_SNAPSHOT | Represents the ΓÇ£Revert-To VNF Snapshot\" LCM operation. CHANGE_VNFPKG | Represents the \"Change current VNF package\" LCM operation.\n",
"type": "string",
"enum": [
"INSTANTIATE",
@@ -186,7 +189,7 @@
"type": "string"
},
"verbosity": {
- "description": "The enumeration LcmOpOccNotificationVerbosityType provides values to control the verbosity of LCM operation occurrence notifications. * 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",
+ "description": "The enumeration LcmOpOccNotificationVerbosityType provides values to control the verbosity of LCM operation occurrence notifications. * 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",
diff --git a/SOL002/VNFLifecycleManagement-API/schemas/subscriptions.schema.json b/SOL002/VNFLifecycleManagement-API/schemas/subscriptions.schema.json
index 5b58184ce0a290447862c52fa53993e15e06b4b2..ece4d04cbdbeceadb06adcdd7141082e2752e9d9 100644
--- a/SOL002/VNFLifecycleManagement-API/schemas/subscriptions.schema.json
+++ b/SOL002/VNFLifecycleManagement-API/schemas/subscriptions.schema.json
@@ -1,108 +1,111 @@
{
- "type": "array",
- "items":
- {
- "description": "This type represents a subscription related to notifications about VNF lifecycle changes.\n",
- "type": "object",
- "required": [
- "id",
- "callbackUri",
- "verbosity",
- "_links"
- ],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "filter": {
- "description": "This type represents a subscription filter related to notifications about VNF lifecycle changes. At a particular nesting level in the filter structure, the following applies: All attributes shall match in order for the filter to match (logical \"and\" between different filter attributes). If an attribute is an array, the attribute shall match if at least one of the values in the array matches (logical \"or\" between the values of one filter attribute).\n",
- "type": "object",
- "properties": {
- "vnfInstanceSubscriptionFilter": {
- "description": "This type represents subscription filter criteria to match VNF instances.\n",
- "type": "object",
- "anyOf": [{
- "oneOf": [{
- "required": [
- "vnfdId"
- ]
- },
- {
- "required": [
- "vnfProductsFromProviders"
- ]
+ "type": "array",
+ "items": {
+ "description": "This type represents a subscription related to notifications about VNF lifecycle changes.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "callbackUri",
+ "verbosity",
+ "_links"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "filter": {
+ "description": "This type represents a subscription filter related to notifications about VNF lifecycle changes.\nAt a particular nesting level in the filter structure, the following applies: All attributes shall match in order for the filter to match (logical \"and\" between different filter attributes). If an attribute is an array, the attribute shall match if at least one of the values in the array matches (logical \"or\" between the values of one filter attribute).\nNOTE:\tThe permitted values of the \"notificationTypes\" attribute are spelled exactly as the names of \n the notification types to facilitate automated code generation systems.\n",
+ "type": "object",
+ "properties": {
+ "vnfInstanceSubscriptionFilter": {
+ "description": "This type represents subscription filter criteria to match VNF instances. * NOTE 1:\tThe attributes \"vnfdIds\" and \"vnfProductsFromProviders\" are alternatives to reference to VNF instances\n that are based on certain VNFDs in a filter. They should not be used both in the same filter instance,\n but one alternative should be chosen.\n NOTE 2:\tThe attributes \"vnfInstanceIds\" and \"vnfInstanceNames\" are alternatives to reference to particular VNF\n instances in a filter. They should not be used both in the same filter instance, but one alternative\n should be chosen.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "oneOf": [
+ {
+ "required": [
+ "vnfdId"
+ ]
+ },
+ {
+ "required": [
+ "vnfProductsFromProviders"
+ ]
+ }
+ ]
+ },
+ {
+ "oneOf": [
+ {
+ "required": [
+ "vnfInstanceIds"
+ ]
+ },
+ {
+ "required": [
+ "vnfInstanceNames"
+ ]
+ }
+ ]
+ }
+ ],
+ "properties": {
+ "vnfdIds": {
+ "description": "If present, match VNF instances that were created based on a VNFD identified by one of the vnfdId values listed in this attribute. See note 1.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
}
- ]
- },
- {
- "oneOf": [{
- "required": [
- "vnfInstanceIds"
- ]
- },
- {
+ },
+ "vnfProductsFromProviders": {
+ "description": "If present, match VNF instances that belong to VNF products from certain providers. See note 1.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
"required": [
- "vnfInstanceNames"
- ]
- }
- ]
- }
- ],
- "properties": {
- "vnfdIds": {
- "description": "If present, match VNF instances that were created based on a VNFD identified by one of the vnfdId values listed in this attribute. The attributes \"vnfdIds\" and \"vnfProductsFromProviders\" are alternatives to reference to VNF instances that are based on certain VNFDs in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n",
- "type": "array",
- "items": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- }
- },
- "vnfProductsFromProviders": {
- "description": "If present, match VNF instances that belong to VNF products from certain providers. The attributes \"vnfdIds\" and \"vnfProductsFromProviders\" are alternatives to reference to VNF instances that are based on certain VNFDs in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": [
- "vnfProvider"
- ],
- "properties": {
- "vnfProvider": {
- "description": "Name of the VNF provider to match.\n",
- "type": "string"
- },
- "vnfProducts": {
- "description": "If present, match VNF instances that belong to VNF products with certain product names, from one particular provider.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": [
- "vnfProductName"
- ],
- "properties": {
- "vnfProductName": {
- "description": "Name of the VNF product to match.\n",
- "type": "string"
- },
- "versions": {
- "description": "If present, match VNF instances that belong to VNF products with certain versions and a certain product name, from one particular provider.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": [
- "vnfSoftwareVersion"
- ],
- "properties": {
- "vnfSoftwareVersion": {
- "description": "A version.\n",
- "type": "string"
- },
- "vnfdVersions": {
- "description": "If present, match VNF instances that belong to VNF products with certain VNFD versions, a certain software version and a certain product name, from one particular provider.\n",
- "type": "array",
- "items": {
+ "vnfProvider"
+ ],
+ "properties": {
+ "vnfProvider": {
+ "description": "Name of the VNF provider to match.\n",
+ "type": "string"
+ },
+ "vnfProducts": {
+ "description": "If present, match VNF instances that belong to VNF products with certain product names, from one particular provider.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": [
+ "vnfProductName"
+ ],
+ "properties": {
+ "vnfProductName": {
+ "description": "Name of the VNF product to match.\n",
+ "type": "string"
+ },
+ "versions": {
+ "description": "If present, match VNF instances that belong to VNF products with certain versions and a certain product name, from one particular provider.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": [
+ "vnfSoftwareVersion"
+ ],
+ "properties": {
+ "vnfSoftwareVersion": {
"description": "A version.\n",
"type": "string"
+ },
+ "vnfdVersions": {
+ "description": "If present, match VNF instances that belong to VNF products with certain VNFD versions, a certain software version and a certain product name, from one particular provider.\n",
+ "type": "array",
+ "items": {
+ "description": "A version.\n",
+ "type": "string"
+ }
}
}
}
@@ -112,112 +115,111 @@
}
}
}
- }
- },
- "vnfInstanceIds": {
- "description": "If present, match VNF instances with an instance identifier listed in this attribute. The attributes \"vnfInstanceIds\" and \"vnfInstanceNames\" are alternatives to reference to particular VNF Instances in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n",
- "type": "array",
- "items": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- }
- },
- "vnfInstanceNames": {
- "description": "If present, match VNF instances with a VNF Instance Name listed in this attribute. The attributes \"vnfInstanceIds\" and \"vnfInstanceNames\" are alternatives to reference to particular VNF Instances in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n",
- "type": "array",
- "items": {
- "type": "string"
+ },
+ "vnfInstanceIds": {
+ "description": "If present, match VNF instances with an instance identifier listed in this attribute. See note 2.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ },
+ "vnfInstanceNames": {
+ "description": "If present, match VNF instances with a VNF Instance Name listed in this attribute. See note 2.\n",
+ "type": "array",
+ "items": {
+ "type": "string"
+ }
}
}
- }
- },
- "notificationTypes": {
- "description": "Match particular notification types. Permitted values: * VnfLcmOperationOccurrenceNotification * VnfIdentifierCreationNotification * VnfIdentifierDeletionNotification The permitted values of the \"notificationTypes\" attribute are spelled exactly as the names of the notification types to facilitate automated code generation systems.\n",
- "type": "array",
- "items": {
- "type": "string",
- "enum": [
- "VnfLcmOperationOccurrenceNotification",
- "VnfIdentifierCreationNotification",
- "VnfIdentifierDeletionNotification"
- ]
- }
- },
- "operationTypes": {
- "description": "Match particular VNF lifecycle operation types for the notification of type VnfLcmOperationOccurrenceNotification. May be present if the \"notificationTypes\" attribute contains the value \"VnfLcmOperationOccurrenceNotification\", and shall be absent otherwise.\n",
- "type": "array",
- "items": {
- "description": "Value | Description ------|------------ INSTANTIATE | Represents the \"Instantiate VNF\" LCM operation. SCALE | Represents the \"Scale VNF\" LCM operation. SCALE_TO_LEVEL | Represents the \"Scale VNF to Level\" LCM operation. CHANGE_FLAVOUR | Represents the \"Change VNF Flavour\" LCM operation. TERMINATE | Represents the \"Terminate VNF\" LCM operation. HEAL | Represents the \"Heal VNF\" LCM operation. OPERATE | Represents the \"Operate VNF\" LCM operation. CHANGE_EXT_CONN | Represents the \"Change external VNF connectivity\" LCM operation. MODIFY_INFO | Represents the \"Modify VNF Information\" LCM operation. CREATE_SNAPSHOT | Represents the \"Create VNF Snapshot\" LCM operation. REVERT_TO_SNAPSHOT | Represents the “Revert-To VNF Snapshot\" LCM operation. CHANGE_VNFPKG | Represents the \"Change current VNF package\" LCM operation.\n",
- "type": "string",
- "enum": [
- "INSTANTIATE",
- "SCALE",
- "SCALE_TO_LEVEL",
- "CHANGE_FLAVOUR",
- "TERMINATE",
- "HEAL",
- "OPERATE",
- "CHANGE_EXT_CONN",
- "MODIFY_INFO",
- "CREATE_SNAPSHOT",
- "REVERT_TO_SNAPSHOT",
- "CHANGE_VNFPKG"
- ]
- }
- },
- "operationStates": {
- "description": "Match particular LCM operation state values as reported in notifications of type VnfLcmOperationOccurrenceNotification. May be present if the \"notificationTypes\" attribute contains the value \"VnfLcmOperationOccurrenceNotification\", and shall be absent otherwise.\n",
- "type": "array",
- "items": {
- "description": "STARTING: The LCM operation is starting. PROCESSING: The LCM operation is currently in execution. COMPLETED: The LCM operation has been completed successfully. FAILED_TEMP: The LCM operation has failed and execution has stopped, but the execution of the operation is not considered to be closed. FAILED: The LCM operation has failed and it cannot be retried or rolled back, as it is determined that such action won't succeed. ROLLING_BACK: The LCM operation is currently being rolled back. ROLLED_BACK: The LCM operation has been successfully rolled back, i.e. The state of the VNF prior to the original operation invocation has been restored as closely as possible.\n",
- "type": "string",
- "enum": [
- "STARTING",
- "PROCESSING",
- "COMPLETED",
- "FAILED_TEMP",
- "FAILED",
- "ROLLING_BACK",
- "ROLLED_BACK"
- ]
+ },
+ "notificationTypes": {
+ "description": "Match particular notification types. \nPermitted values: -\tVnfLcmOperationOccurrenceNotification -\tVnfIdentifierCreationNotification -\tVnfIdentifierDeletionNotification See note.\n",
+ "type": "array",
+ "items": {
+ "type": "string",
+ "enum": [
+ "VnfLcmOperationOccurrenceNotification",
+ "VnfIdentifierCreationNotification",
+ "VnfIdentifierDeletionNotification"
+ ]
+ }
+ },
+ "operationTypes": {
+ "description": "Match particular VNF lifecycle operation types for the notification of type VnfLcmOperationOccurrenceNotification. May be present if the \"notificationTypes\" attribute contains the value \"VnfLcmOperationOccurrenceNotification\", and shall be absent otherwise.\n",
+ "type": "array",
+ "items": {
+ "description": "The enumeration LcmOpType defines the permitted values to represent VNF lifecycle operation types in VNF lifecycle management operation occurrence resources and VNF lifecycle management operation occurrence notifications.\nValue | Description ------|------------ INSTANTIATE | Represents the \"Instantiate VNF\" LCM operation. SCALE | Represents the \"Scale VNF\" LCM operation. SCALE_TO_LEVEL | Represents the \"Scale VNF to Level\" LCM operation. CHANGE_FLAVOUR | Represents the \"Change VNF Flavour\" LCM operation. TERMINATE | Represents the \"Terminate VNF\" LCM operation. HEAL | Represents the \"Heal VNF\" LCM operation. OPERATE | Represents the \"Operate VNF\" LCM operation. CHANGE_EXT_CONN | Represents the \"Change external VNF connectivity\" LCM operation. MODIFY_INFO | Represents the \"Modify VNF Information\" LCM operation. CREATE_SNAPSHOT | Represents the \"Create VNF Snapshot\" LCM operation. REVERT_TO_SNAPSHOT | Represents the ΓÇ£Revert-To VNF Snapshot\" LCM operation. CHANGE_VNFPKG | Represents the \"Change current VNF package\" LCM operation.\n",
+ "type": "string",
+ "enum": [
+ "INSTANTIATE",
+ "SCALE",
+ "SCALE_TO_LEVEL",
+ "CHANGE_FLAVOUR",
+ "TERMINATE",
+ "HEAL",
+ "OPERATE",
+ "CHANGE_EXT_CONN",
+ "MODIFY_INFO",
+ "CREATE_SNAPSHOT",
+ "REVERT_TO_SNAPSHOT",
+ "CHANGE_VNFPKG"
+ ]
+ }
+ },
+ "operationStates": {
+ "description": "Match particular LCM operation state values as reported in notifications of type VnfLcmOperationOccurrenceNotification. May be present if the \"notificationTypes\" attribute contains the value \"VnfLcmOperationOccurrenceNotification\", and shall be absent otherwise.\n",
+ "type": "array",
+ "items": {
+ "description": "STARTING: The LCM operation is starting. PROCESSING: The LCM operation is currently in execution. COMPLETED: The LCM operation has been completed successfully. FAILED_TEMP: The LCM operation has failed and execution has stopped, but the execution of the operation is not considered to be closed. FAILED: The LCM operation has failed and it cannot be retried or rolled back, as it is determined that such action won't succeed. ROLLING_BACK: The LCM operation is currently being rolled back. ROLLED_BACK: The LCM operation has been successfully rolled back, i.e. The state of the VNF prior to the original operation invocation has been restored as closely as possible.\n",
+ "type": "string",
+ "enum": [
+ "STARTING",
+ "PROCESSING",
+ "COMPLETED",
+ "FAILED_TEMP",
+ "FAILED",
+ "ROLLING_BACK",
+ "ROLLED_BACK"
+ ]
+ }
}
}
- }
- },
- "callbackUri": {
- "description": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- },
- "verbosity": {
- "description": "The enumeration LcmOpOccNotificationVerbosityType provides values to control the verbosity of LCM operation occurrence notifications. * 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"
- ]
- },
- "_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 using an absolute URI.\n",
- "type": "object",
- "required": [
- "href"
- ],
- "properties": {
- "href": {
- "description": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
+ },
+ "callbackUri": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ },
+ "verbosity": {
+ "description": "The enumeration LcmOpOccNotificationVerbosityType provides values to control the verbosity of LCM operation occurrence notifications. * 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"
+ ]
+ },
+ "_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 using an absolute URI.\n",
+ "type": "object",
+ "required": [
+ "href"
+ ],
+ "properties": {
+ "href": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ }
}
}
}
}
}
}
- }
}
\ No newline at end of file
diff --git a/SOL002/VNFLifecycleManagement-API/schemas/vnfInstance.schema.json b/SOL002/VNFLifecycleManagement-API/schemas/vnfInstance.schema.json
index 6d3dff1791c9dc2046cffb5ea89af80817e36686..eb86a9bb6e234d4814a22a061cb85bd69ae01fdd 100644
--- a/SOL002/VNFLifecycleManagement-API/schemas/vnfInstance.schema.json
+++ b/SOL002/VNFLifecycleManagement-API/schemas/vnfInstance.schema.json
@@ -81,23 +81,24 @@
"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. This attribute shall be present if the VNF supports scaling. See clause B.2 for an explanation of VNF scaling.\n",
"type": "array",
"items": {
+ "description": "This type represents the scale level of a VNF instance related to a scaling aspect.\n",
+ "type": "object",
"required": [
"aspectId",
"scaleLevel"
],
- "type": "object",
"properties": {
"aspectId": {
"description": "An identifier that is unique within a VNF descriptor.\n",
"type": "string"
},
"vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
+ "description": "An identifier that is unique within a VNF descriptor.\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"
+ "scaleToLevel": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
}
}
}
@@ -106,23 +107,24 @@
"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": {
+ "description": "This type represents the scale level of a VNF instance related to a scaling aspect.\n",
+ "type": "object",
"required": [
"aspectId",
"scaleLevel"
],
- "type": "object",
"properties": {
"aspectId": {
"description": "An identifier that is unique within a VNF descriptor.\n",
"type": "string"
},
"vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
+ "description": "An identifier that is unique within a VNF descriptor.\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"
+ "scaleToLevel": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
}
}
}
@@ -132,7 +134,7 @@
"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 5.5.3.17 1.\nNOTE 1:\tThe attributes \"associatedVnfcCpId\", \"associatedVipCpId\" and \"associatedVnfVirtualLinkId\" \n are mutually exclusive. Exactly one shall be present.\nNOTE 2:\tAn external CP instance is not associated to a link port in the cases indicated for the \n “extLinkPorts†attribute in clause 4.4.1.11.\n",
+ "description": "This type represents information about an external CP of a VNF.\nNOTE 1:\tThe attributes \"associatedVnfcCpId\", \"associatedVipCpId\", \"associatedVirtualCpId\" and \n \"associatedVnfVirtualLinkId\" are mutually exclusive. Exactly one shall be present.\nNOTE 2:\tAn external CP instance is not associated to a link port in the cases indicated for the \n ΓÇ£extLinkPortsΓÇ¥ attribute in clause 4.4.1.11.\nNOTE 3: 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 \n CP, e.g. to build a link redundant mated pair in SR-IOV cases.\nNOTE 4: When more than one netAttDefResourceId is indicated, all shall belong to the same namespace.\n",
"type": "object",
"required": [
"id",
@@ -178,21 +180,22 @@
"description": "Network protocol information for this CP.\n",
"type": "array",
"items": {
- "description": "This type describes the protocol layer(s) that a CP uses together with protocol-related information, like addresses. It shall comply with the provisions defined in table 5.5.3.9b-1.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the \n present document in a backwards-compatible way. In the current version of the present document, only IP over \n Ethernet is supported.\n",
+ "description": "This type describes the protocol layer(s) that a CP uses together with protocol-related information, like addresses.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the \n present document in a backwards-compatible way. In the current version of the present document, only IP over \n Ethernet is supported.\n",
"type": "object",
"required": [
"layerProtocol"
],
"properties": {
"layerProtocol": {
- "description": "The identifier of layer(s) and protocol(s) associated to the network address information.\nPermitted values: IP_OVER_ETHERNET See note.\n",
+ "description": "The identifier of layer(s) and protocol(s) associated to the network address information.\nPermitted values:\n - IP_OVER_ETHERNET\n - IP_FOR_VIRTUAL_CP\nSee note.\n",
"type": "string",
"enum": [
- "IP_OVER_ETHERNET"
+ "IP_OVER_ETHERNET",
+ "IP_FOR_VIRTUAL_CP"
]
},
"ipOverEthernet": {
- "description": "This type represents information about a network address that has been assigned. It shall comply with the provisions defined in table 5.5.3.10-1.\nNOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, segmentationId shall be present. \n Otherwise it shall not be present.\nNOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the \n actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the \n transport header of the packets or it may be an identifier used between the application \n and the NFVI networking infrastructure to identify the network sub-interface of the trunk \n port in question. In the latter case the NFVI infrastructure will map this local segmentationId \n to whatever segmentationId is actually used by the NFVI’s transport technology.\n",
+ "description": "This type represents information about a network address that has been assigned.\nNOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, segmentationId shall be present. \n Otherwise it shall not be present.\nNOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the \n actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the \n transport header of the packets or it may be an identifier used between the application \n and the NFVI networking infrastructure to identify the network sub-interface of the trunk \n port in question. In the latter case the NFVI infrastructure will map this local segmentationId \n to whatever segmentationId is actually used by the NFVIΓÇÖs transport technology.\n",
"type": "object",
"anyOf": [
{
@@ -279,13 +282,35 @@
}
},
"subnetId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\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"
+ }
+ }
}
}
}
@@ -306,9 +331,21 @@
"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 within a VNF descriptor.\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"
+ },
+ "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. It 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 with the intention of being globally unique.\n",
+ "type": "string"
+ }
}
}
}
@@ -317,7 +354,7 @@
"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.\nMay 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 5.5.3.28-1.\nNOTE 1:\tIt is possible that there is no associated VnfcCp because the VIP CP is available but not associated yet. NOTE 2: If only the value or the presence of this attribute is changed in the \"VipCpInfo\" structure by an LCM operation occurrence, this does not represent a change that requires including a related \"AffectedVipCp\" structure in the VNF LCM operation occurrence notifications or the \"VnfLcmOpOcc\" structure related to this LCM operation occurrence.\n",
+ "description": "This type provides information related to virtual IP CP.\nNOTE 1:\tIt is possible that there is no associated VnfcCp because the virtual IP CP is available but not associated yet. NOTE 2: If only the value or the presence of this attribute is changed in the \"VipCpInfo\" structure by an LCM operation occurrence, this does not represent a change that requires including a related \"AffectedVipCp\" structure in the VNF LCM operation occurrence notifications or the \"VnfLcmOpOcc\" structure related to this LCM operation occurrence.\n",
"type": "object",
"required": [
"cpInstanceId",
@@ -344,21 +381,22 @@
"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 uses together with protocol-related information, like addresses. It shall comply with the provisions defined in table 5.5.3.9b-1.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the \n present document in a backwards-compatible way. In the current version of the present document, only IP over \n Ethernet is supported.\n",
+ "description": "This type describes the protocol layer(s) that a CP uses together with protocol-related information, like addresses.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the \n present document in a backwards-compatible way. In the current version of the present document, only IP over \n Ethernet is supported.\n",
"type": "object",
"required": [
"layerProtocol"
],
"properties": {
"layerProtocol": {
- "description": "The identifier of layer(s) and protocol(s) associated to the network address information.\nPermitted values: IP_OVER_ETHERNET See note.\n",
+ "description": "The identifier of layer(s) and protocol(s) associated to the network address information.\nPermitted values:\n - IP_OVER_ETHERNET\n - IP_FOR_VIRTUAL_CP\nSee note.\n",
"type": "string",
"enum": [
- "IP_OVER_ETHERNET"
+ "IP_OVER_ETHERNET",
+ "IP_FOR_VIRTUAL_CP"
]
},
"ipOverEthernet": {
- "description": "This type represents information about a network address that has been assigned. It shall comply with the provisions defined in table 5.5.3.10-1.\nNOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, segmentationId shall be present. \n Otherwise it shall not be present.\nNOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the \n actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the \n transport header of the packets or it may be an identifier used between the application \n and the NFVI networking infrastructure to identify the network sub-interface of the trunk \n port in question. In the latter case the NFVI infrastructure will map this local segmentationId \n to whatever segmentationId is actually used by the NFVI’s transport technology.\n",
+ "description": "This type represents information about a network address that has been assigned.\nNOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, segmentationId shall be present. \n Otherwise it shall not be present.\nNOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the \n actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the \n transport header of the packets or it may be an identifier used between the application \n and the NFVI networking infrastructure to identify the network sub-interface of the trunk \n port in question. In the latter case the NFVI infrastructure will map this local segmentationId \n to whatever segmentationId is actually used by the NFVIΓÇÖs transport technology.\n",
"type": "object",
"anyOf": [
{
@@ -445,19 +483,41 @@
}
},
"subnetId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\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 1.\n",
+ "description": "Identifiers of the VnfcCps that share the virtual IP addresse allocated to the virtual IP 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",
@@ -469,30 +529,31 @@
"type": "string"
},
"metadata": {
- "description": "Metadata about this VIP CP.\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 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"
- }
+ "description": "This 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"
}
}
}
},
- "extVirtualLinkInfo": {
- "description": "Information about the external VLs the VNF instance is connected to.\n",
+ "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 information about an external VL. It shall comply with the provisions defined in table 5.5.3.2-1.\nNOTE:\tThis attribute reflects the current configuration information that has resulted from merging into this attribute \n the \"VnfExtCpData\" information which was passed as part of the \"ExtVirtualLinkData\" structure in the input of the \n most recent VNF LCM operation such as \"InstantiateVnfRequest\", \"ChangeExtVnfConnectivityRequest\", \"ChangeVnfFlavourRequest\" \n or \"ChangeCurrentVnfPkgRequest\", or in the Grant response. If applying such change results in an empty list of \n \"currentVnfExtCpData\" structure instances, the affected instance of \"ExtVirtualLinkInfo\" shall be removed from its \n parent data structure.\n",
+ "description": "This type provides information related to a virtual CP instance of a VNF.\nNOTE: A consumer of the VNF LCM interface can learn the actual VNFC instances implementing the service \n accessible via the virtual CP instance by querying the \"vnfcResourceInfo\" from the \"InstantiatedVnfInfo\" \n and filtering by corresponding \"vduIds\" values.\n",
"type": "object",
"required": [
- "id",
+ "cpInstanceId",
+ "cpdId",
"resourceHandle",
- "currentVnfExtCpData"
+ "vduIds"
],
"properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
+ "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": "An identifier that is unique within a VNF descriptor.\n",
"type": "string"
},
"resourceHandle": {
@@ -500,7 +561,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",
+ "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",
"properties": {
"vimConnectionId": {
"description": "An identifier with the intention of being globally unique.\n",
@@ -511,134 +572,460 @@
"type": "string"
},
"resourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
"type": "string"
},
"vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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",
+ "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 represents information about a link port of an external VL, i.e. a port providing connectivity for the VNF to an NS VL. It shall comply with the provisions defined in table 5.5.3.9-1.\nNOTE 1:\tThe use cases UC#4 and UC#5 in clause A.4 of ETSI GS NFV-IFA 007 provide examples for such a configuration. NOTE 2:\tThe value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\" attribute.\n",
+ "description": "This type describes the protocol layer(s) that a CP uses together with protocol-related information, like addresses.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the \n present document in a backwards-compatible way. In the current version of the present document, only IP over \n Ethernet is supported.\n",
"type": "object",
"required": [
- "id",
- "resourceHandle"
+ "layerProtocol"
],
"properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
+ "layerProtocol": {
+ "description": "The identifier of layer(s) and protocol(s) associated to the network address information.\nPermitted values:\n - IP_OVER_ETHERNET\n - IP_FOR_VIRTUAL_CP\nSee note.\n",
+ "type": "string",
+ "enum": [
+ "IP_OVER_ETHERNET",
+ "IP_FOR_VIRTUAL_CP"
+ ]
},
- "resourceHandle": {
- "required": [
- "resourceId"
- ],
+ "ipOverEthernet": {
+ "description": "This type represents information about a network address that has been assigned.\nNOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, segmentationId shall be present. \n Otherwise it shall not be present.\nNOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the \n actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the \n transport header of the packets or it may be an identifier used between the application \n and the NFVI networking infrastructure to identify the network sub-interface of the trunk \n port in question. In the latter case the NFVI infrastructure will map this local segmentationId \n to whatever segmentationId is actually used by the NFVIΓÇÖs transport technology.\n",
"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",
- "properties": {
- "vimConnectionId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
+ "anyOf": [
+ {
+ "required": [
+ "macAddress"
+ ]
},
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
+ {
+ "required": [
+ "ipAddresses"
+ ]
+ }
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "addresses"
+ ]
},
- "resourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
+ {
+ "required": [
+ "addressRange"
+ ]
+ }
+ ],
+ "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"
},
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
+ "segmentationId": {
+ "description": "Identification of the network segment to which the Cp instance connects to. See notes 3 and 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"
+ ],
+ "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. 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.\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.\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"
+ }
+ }
}
}
}
},
- "currentVnfExtCpData": {
- "description": "Allows the API consumer to read the current CP configuration information for the connection of external CPs to the external virtual link. See note.\n",
+ "vduIds": {
+ "description": "Reference to the VDU(s) which implement the service accessible via the virtual CP instance. See note.\n",
+ "type": "array",
+ "minItems": 1,
+ "items": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ }
+ },
+ "additionalServiceInfo": {
+ "description": "Additional service identification information of the virtual CP instance.\n",
"type": "array",
"items": {
- "description": "This type represents configuration information for external CPs created. * NOTE 1: \tIn case this identifier refers to a CPD with trunking enabled, the external CP instances created\n from this CPD will represent ports in a trunk.\n* NOTE 2: \tWithin one VNF instance, all VNFC instances created from a particular VDU have the same external\n connectivity. Thus, given a particular value of the \"cpdId\" attribute, there shall be one\n \"cpConfig\" entry for each VNFC instance that has been or can be created from a VDU which includes\n a CPD identified by the \"cpdId\" attribute. If the cpConfig represents a subport in a trunk,\n all \"cpConfig\" entries in this list shall have the same segmentationId, which means they are\n connected to the same set of external VLs via the trunk.\n* NOTE 3: \tThe map entry value shall be set to \"null\" in order to delete a \"VnfExtCpConfig\" entry identified\n by a particular key value from the map, i.e. for the disconnection of an existing external\n CP instance addressed by cpInstanceId in the deleted map entry from a particular external\n virtual link, and deletion of that instance in case it represents a subport. Deleting the\n last key from the map removes the affected instance of the \"VnfExtCpData\" structure from\n its parent data structure.\n* NOTE 4: If, as defined by the input parameters of a \"ChangeVnfFlavour\", \"ChangeExtVnfConnectivity\" or \n \"ChangeCurrentVnfPkg\" operation or as part of the Grant response for any of these operations, a \n cpConfig map entry identified by a particular map key value is moved into another \"ExtVirtualLinkData\"\n or \"VnfExtCpData\" structure, this particular cpConfig map entry may be used by an external CP instance\n different than the one that has used it before the operation, or by no external CP instance at all.\n Renaming a CPD identifier during the \"changeCurrentVnfPkg\" operation does not count as moving the\n related \"cpConfig\" map entries to a new \"extCpData\" structure.\n",
+ "description": "This type provides 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 \n termination within the VNF, such as for example a URL path information in an HTTP request required \n to allow a single virtual CP IP address to be used for several HTTP based services that use the \n same port number.\n",
"type": "object",
"required": [
- "cpdId"
+ "portInfo"
],
"properties": {
- "cpdId": {
- "description": "An identifier that is unique within a VNF descriptor.\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). See notes 2, 3 and 4.\n",
- "type": "object",
- "additionalProperties": {
- "description": "This type represents an externally provided link port or network address information per instance of an external connection point. In case a link port is provided, the VNFM shall use that link port when connecting the external CP to the external VL. In a link port is not provided, the VNFM shall create a link port on the external VL, and use that link port to connect the external CP to the external VL. * NOTE: The following conditions apply to the attributes \"linkPortId\" and \"cpProtocolData\":\n 1) Void.\n 2) At least one of the \"linkPortId\" and \"cpProtocolData\" attributes shall be present for an external\n CP instance representing a subport that is to be created, or an external CP instance that is to be\n created by creating the corresponding VNFC or VNF instance during the current or a subsequent LCM\n operation, or for an existing external CP instance that is to be re-configured or added to a\n 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\n a pre created link port, and the VNFM can use means outside the scope of the present document to obtain\n the pre-configured address information for the connection point from the resource representing\n the link port.\n 5) If both \"cpProtocolData\" and \"linkportId\" are provided, the API consumer shall ensure that the\n cpProtocolData can be used with the pre-created link port referenced by \"linkPortId\".\n",
- "anyOf": [
- {
- "required": [
- "linkPortId"
- ]
- },
- {
- "required": [
- "cpProtocolData"
- ]
- }
- ],
+ "portInfo": {
+ "description": "Service port numbers exposed by the virtual CP instance.\n",
+ "minItems": 1,
+ "type": "array",
+ "items": {
+ "description": "This type describes the service identifying port properties exposed by the virtual CP instance.\n",
"type": "object",
+ "required": [
+ "name",
+ "port",
+ "portConfigurable"
+ ],
"properties": {
- "parentCpConfigId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "name": {
+ "description": "The name of the port exposed by the virtual CP instance.\n",
"type": "string"
},
- "linkPortId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
+ "protocol": {
+ "description": "The L4 protocol for this port exposed by the virtual CP instance.\nPermitted values: - TCP - UDP - SCTP\n",
+ "type": "string",
+ "enum": [
+ "TCP",
+ "UDP",
+ "SCTP"
+ ]
},
- "createExtLinkPort": {
- "description": "Indicates to the VNFM the need to create a dedicated link port for the external CP. If set to True, the VNFM shall create a link port. If set to False, the VNFM shall not create a link port. 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"
+ "port": {
+ "description": "The L4 port number exposed by the virtual CP instance.\n",
+ "type": "integer"
},
- "cpProtocolData": {
- "description": "Parameters for configuring the network protocols on the link port that connects the CP to a VL. See note.\n",
- "type": "array",
- "items": {
- "description": "This type represents network protocol data. * NOTE:\tThis attribute allows to signal the addition of further types of layer and protocol\n in future versions of the present document in a backwards-compatible way. In the current\n 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). See note.\n",
- "type": "string",
+ "portConfigurable": {
+ "description": "The Boolean is a data type having two values (true and false).\n",
+ "type": "boolean"
+ }
+ }
+ }
+ },
+ "serviceInfo": {
+ "description": "This 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"
+ }
+ }
+ }
+ },
+ "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 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"
+ }
+ }
+ }
+ },
+ "extVirtualLinkInfo": {
+ "description": "Information about the external VLs the VNF instance is connected to.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents information about an external VL.\nNOTE:\tThis attribute reflects the current configuration information that has resulted from merging into this attribute \n the \"VnfExtCpData\" information which was passed as part of the \"ExtVirtualLinkData\" structure in the input of the \n most recent VNF LCM operation such as \"InstantiateVnfRequest\", \"ChangeExtVnfConnectivityRequest\", \"ChangeVnfFlavourRequest\" \n or \"ChangeCurrentVnfPkgRequest\", or in the Grant response. If applying such change results in an empty list of \n \"currentVnfExtCpData\" structure instances, the affected instance of \"ExtVirtualLinkInfo\" shall be removed from its \n parent data structure.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "resourceHandle",
+ "currentVnfExtCpData"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceHandle": {
+ "required": [
+ "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",
+ "properties": {
+ "vimConnectionId": {
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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.\nNOTE 1:\tThe use cases UC#4 and UC#5 in clause A.4 of ETSI GS NFV-IFA 007 provide examples for such a configuration. NOTE 2:\tThe 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": {
+ "required": [
+ "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",
+ "properties": {
+ "vimConnectionId": {
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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 the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "currentVnfExtCpData": {
+ "description": "Allows the API consumer to read the current CP configuration information for the connection of external CPs to the external virtual link. See note.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents configuration information for external CPs created. * NOTE 1: \tIn case this identifier refers to a CPD with trunking enabled, the external CP instances created\n from this CPD will represent ports in a trunk.\n* NOTE 2: \tWithin one VNF instance, all VNFC instances created from a particular VDU have the same external\n connectivity. Thus, given a particular value of the \"cpdId\" attribute, there shall be one\n \"cpConfig\" entry for each VNFC instance that has been or can be created from a VDU which includes\n a CPD identified by the \"cpdId\" attribute. If the cpConfig represents a subport in a trunk,\n all \"cpConfig\" entries in this list shall have the same segmentationId, which means they are\n connected to the same set of external VLs via the trunk.\n* NOTE 3: \tThe map entry value shall be set to \"null\" in order to delete a \"VnfExtCpConfig\" entry identified\n by a particular key value from the map, i.e. for the disconnection of an existing external\n CP instance addressed by cpInstanceId in the deleted map entry from a particular external\n virtual link, and deletion of that instance in case it represents a subport. Deleting the\n last key from the map removes the affected instance of the \"VnfExtCpData\" structure from\n its parent data structure.\n* NOTE 4: If, as defined by the input parameters of a \"ChangeVnfFlavour\", \"ChangeExtVnfConnectivity\" or\n \"ChangeCurrentVnfPkg\" operation, a cpConfig map entry identified by a particular map key value \n is moved into another \"ExtVirtualLinkData\" or \"VnfExtCpData\" structure, this particular cpConfig\n map entry may be used by an external CP instance different than the one that has used it before the\n operation, or by no external CP instance at all. Renaming a CPD identifier during the \"changeCurrentVnfPkg\"\n operation does not count as moving the related \"cpConfig\" map entries to a new \"extCpData\" structure.\n",
+ "type": "object",
+ "required": [
+ "cpdId"
+ ],
+ "properties": {
+ "cpdId": {
+ "description": "An identifier that is unique within a VNF descriptor.\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 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",
+ "anyOf": [
+ {
+ "required": [
+ "linkPortId"
+ ]
+ },
+ {
+ "required": [
+ "cpProtocolData"
+ ]
+ },
+ {
+ "required": [
+ "netAttDefResourceId"
+ ]
+ }
+ ],
+ "type": "object",
+ "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 to the VNFM the need to create a dedicated link port for the external CP. If set to True, the VNFM shall create a link port. If set to False, the VNFM shall not create a link port. This attribute is only applicable for external CP instances without a floating IP address that expose a virtual IP 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 2.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents network protocol data. * NOTE:\tThis attribute allows to signal the addition of further types of layer and protocol\n in future versions of the present document in a backwards-compatible way. In the current\n 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:\n - IP_OVER_ETHERNET.\n - IP_FOR_VIRTUAL_CP\nSee note\n",
+ "type": "string",
"enum": [
- "IP_OVER_ETHERNET"
+ "IP_OVER_ETHERNET",
+ "IP_FOR_VIRTUAL_CP"
]
},
"ipOverEthernet": {
- "description": "This type represents network address data for IP over Ethernet. * NOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. * NOTE 2:\tExactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present. * NOTE 3:\tIf the CP instance represents a subport in a trunk, segmentationId shall be present.\n Otherwise it shall not be present.\n* NOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the actual\n network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header\n of the packets or it may be an identifier used between the application and the NFVI networking\n infrastructure to identify the network sub-interface of the trunk port in question. In the latter\n case the NFVI infrastructure will map this local segmentationId to whatever segmentationId is\n actually used by the NFVI’s transport technology.\n",
+ "description": "This type represents network address data for IP over Ethernet to assign to the external CP. * NOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. * NOTE 2:\tExactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present. * NOTE 3:\tIf the CP instance represents a subport in a trunk, segmentationId shall be present.\n Otherwise it shall not be present.\n* NOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the actual\n network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header\n of the packets or it may be an identifier used between the application and the NFVI networking\n infrastructure to identify the network sub-interface of the trunk port in question. In the latter\n case the NFVI infrastructure will map this local segmentationId to whatever segmentationId is\n actually used by the NFVI's transport technology.\n",
"type": "object",
"anyOf": [
{
@@ -676,7 +1063,7 @@
"format": "MAC"
},
"segmentationType": {
- "description": "Specifies the encapsulation type for the traffics coming in and out of the trunk subport. Permitted values: -\tVLAN: the subport uses VLAN as encapsulation type. -\tINHERIT: the subport gets its segmentation type from the network it’s 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",
+ "description": "Specifies the encapsulation type for the traffics coming in and out of the trunk subport. Permitted values: -\tVLAN: the subport uses VLAN as encapsulation type. -\tINHERIT: the subport gets its segmentation type from the network itΓÇÖs 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",
@@ -738,19 +1125,130 @@
}
},
"subnetId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
"type": "string"
}
}
}
}
}
+ },
+ "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",
+ "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"
+ }
+ }
}
}
}
+ },
+ "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 2, 3 and 4.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\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 contains 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": {
+ "required": [
+ "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",
+ "properties": {
+ "vimConnectionId": {
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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 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"
+ }
}
+ },
+ "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 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 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"
+ }
}
}
}
@@ -762,6 +1260,7 @@
"description": "Information about the externally managed internal VLs of the VNF instance. See note 5 and note 6. 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 VNF internal VL shall indicate so by referencing to the same VnfVirtualLinkDesc and externally-managed multi-site VL instance (refer to clause 5.5.3.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": "array",
"items": {
+ "description": "This type provides information about an externally-managed virtual link.\n",
"type": "object",
"required": [
"id",
@@ -786,7 +1285,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",
+ "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",
"properties": {
"vimConnectionId": {
"description": "An identifier with the intention of being globally unique.\n",
@@ -797,11 +1296,33 @@
"type": "string"
},
"resourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
"type": "string"
},
"vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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"
}
}
@@ -810,7 +1331,7 @@
"description": "Link ports of this VL.\n",
"type": "array",
"items": {
- "description": "This type represents a link port of an internal VL of a VNF. It shall comply with the provisions defined in table 5.5.3.8 1.\nNOTE 1: Either cpInstanceId with cpInstanceType set to \"EXT_CP\" or any combination of cpInstanceId\n with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId (i.e. one or both of them) shall be \n present for a VnfLinkPortInfo. In case both cpInstanceId with cpInstanceType set to \"VNFC_CP\" \n and vipCpInstanceId are present, the two different CP instances share the linkport.\nNOTE 2: Annex A.4 of ETSI GS NFV-IFA 007 provides examples for configurations where both vipCpInstanceId\n and vnfcCpInstanceId are present (UC#5 and UC#5-b), only vnfcCpInstanceId is present (UC#2), or \n only vipCpInstanceId is present (UC6 and UC#6-b).\nNOTE 3: The value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\"\n attribute.\n",
+ "description": "This type represents a link port of an internal VL of a VNF.\nNOTE 1: Either cpInstanceId with cpInstanceType set to \"EXT_CP\" or any combination of cpInstanceId\n with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId (i.e. one or both of them) shall be \n present for a VnfLinkPortInfo. In case both cpInstanceId with cpInstanceType set to \"VNFC_CP\" \n and vipCpInstanceId are present, the two different CP instances share the linkport.\nNOTE 2: Annex A.4 of ETSI GS NFV-IFA 007 provides examples for configurations where both vipCpInstanceId\n and vnfcCpInstanceId are present (UC#5 and UC#5-b), only vnfcCpInstanceId is present (UC#2), or \n only vipCpInstanceId is present (UC6 and UC#6-b).\nNOTE 3: The value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\"\n attribute.\n",
"type": "object",
"required": [
"id",
@@ -826,7 +1347,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",
+ "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",
"properties": {
"vimConnectionId": {
"description": "An identifier with the intention of being globally unique.\n",
@@ -837,11 +1358,33 @@
"type": "string"
},
"resourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
"type": "string"
},
"vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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"
}
}
@@ -863,20 +1406,101 @@
"type": "string"
},
"trunkResourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
"type": "string"
}
}
}
- }
- }
- }
- },
- "monitoringParameters": {
- "description": "Active monitoring parameters.\n",
- "type": "array",
- "items": {
- "type": "object",
+ },
+ "vnfNetAttDefResource": {
+ "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 contains 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": {
+ "required": [
+ "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",
+ "properties": {
+ "vimConnectionId": {
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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 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 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"
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ },
+ "monitoringParameters": {
+ "description": "Active monitoring parameters.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
"required": [
"id",
"performanceMetric"
@@ -906,439 +1530,606 @@
"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. * NOTE 1:\tETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on TOSCA specifications. * NOTE 2:\tA VNFC CP is \"connected to\" an external CP if the VNFC CP is connected to an internal VL that\n exposes an external CP. A VNFC CP is \"exposed as\" an external CP if it is connected directly\n to an external VL.\n* NOTE 3:\tThe information can be omitted because it is already available as part of the external CP information. * NOTE 4: If only the value or the presence of this attribute is changed in the \"VnfcResourceInfo\" structure by \n an LCM operation occurrence, this does not represent a change that requires including a related \"AffectedVnfc\"\n structure in the VNF LCM operation occurrence notifications or the \"VnfLcmOpOcc\" structure related to \n this LCM operation occurrence.\n",
- "type": "object",
- "required": [
- "id",
- "vduId",
- "computeResource"
- ],
- "properties": {
- "id": {
+ "description": "This type represents the information on virtualised compute and storage resources used by a VNFC in a VNF instance. Depending on the form of virtualisation container of the VNFC:\n - For a VNFC based on VM, a reference to the corresponding VirtualCompute shall be provided, and\n - For a VNFC based on OS container(s), a reference to the Compute MCIO shall be provided. Hence, exposure \n of information by the VNFM to the NFVO is at the MCIO level.\nIn addition, the references to the storage resources depend on the form of the VNFC:\n - For a VNFC based on VM, storage resource identifiers shall refer to VirtualStorage resources, and\n - For a VNFC based on OS container(s), storage resource identifiers shall refer to Storage MCIOs.\n\n\n* NOTE 1:\tETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on TOSCA specifications. * NOTE 2:\tA VNFC CP is \"connected to\" an external CP if the VNFC CP is connected to an internal VL that\n exposes an external CP. A VNFC CP is \"exposed as\" an external CP if it is connected directly\n to an external VL.\n* NOTE 3:\tThe information can be omitted because it is already available as part of the external CP information. * NOTE 4: If only the value or the presence of this attribute is changed in the \"VnfcResourceInfo\" structure by \n an LCM operation occurrence, this does not represent a change that requires including a related \"AffectedVnfc\"\n structure in the VNF LCM operation occurrence notifications or the \"VnfLcmOpOcc\" structure related to \n this LCM operation occurrence.\n* NOTE 5: 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 internal CP, e.g. to build \n a link redundant mated pair in SR-IOV cases.\n* NOTE 6: 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"
+ },
+ "vduId": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "computeResource": {
+ "required": [
+ "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",
+ "properties": {
+ "vimConnectionId": {
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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 MCIO(s). 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"
- },
- "vduId": {
- "description": "An identifier that is unique within a VNF descriptor.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "computeResource": {
+ }
+ },
+ "reservationId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfcCpInfo": {
+ "description": "All the CPs of the VNFC instance.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
"required": [
- "resourceId"
+ "id",
+ "cpdId"
],
- "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",
"properties": {
- "vimConnectionId": {
- "description": "An identifier with the intention of being globally unique.\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"
},
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
+ "cpdId": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
"type": "string"
},
- "resourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\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"
},
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
- "type": "string"
- }
- }
- },
- "storageResourceIds": {
- "description": "References to the VirtualStorage resources. 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": "All the CPs of the VNFC instance.\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 VNF descriptor.\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. The information can be omitted because it is already available as part of the external CP information. See note 3.\n",
- "type": "array",
- "items": {
- "description": "This type describes the protocol layer(s) that a CP uses together with protocol-related information, like addresses. It shall comply with the provisions defined in table 5.5.3.9b-1.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the \n present document in a backwards-compatible way. In the current version of the present document, only IP over \n Ethernet is supported.\n",
- "type": "object",
- "required": [
- "layerProtocol"
- ],
- "properties": {
- "layerProtocol": {
- "description": "The identifier of layer(s) and protocol(s) associated to the network address information.\nPermitted values: IP_OVER_ETHERNET See note.\n",
- "type": "string",
- "enum": [
- "IP_OVER_ETHERNET"
- ]
- },
- "ipOverEthernet": {
- "description": "This type represents information about a network address that has been assigned. It shall comply with the provisions defined in table 5.5.3.10-1.\nNOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, segmentationId shall be present. \n Otherwise it shall not be present.\nNOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the \n actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the \n transport header of the packets or it may be an identifier used between the application \n and the NFVI networking infrastructure to identify the network sub-interface of the trunk \n port in question. In the latter case the NFVI infrastructure will map this local segmentationId \n to whatever segmentationId is actually used by the NFVI’s transport technology.\n",
- "type": "object",
- "anyOf": [
- {
- "required": [
- "macAddress"
- ]
- },
- {
- "required": [
- "ipAddresses"
- ]
- }
- ],
- "oneOf": [
- {
- "required": [
- "addresses"
- ]
- },
- {
+ "cpProtocolInfo": {
+ "description": "Network protocol information for this CP. May be omitted if the VNFC CP is exposed as an external CP. The information can be omitted because it is already available as part of the external CP information. See note 3.\n",
+ "type": "array",
+ "items": {
+ "description": "This type describes the protocol layer(s) that a CP uses together with protocol-related information, like addresses.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the \n present document in a backwards-compatible way. In the current version of the present document, only IP over \n Ethernet is supported.\n",
+ "type": "object",
+ "required": [
+ "layerProtocol"
+ ],
+ "properties": {
+ "layerProtocol": {
+ "description": "The identifier of layer(s) and protocol(s) associated to the network address information.\nPermitted 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:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, segmentationId shall be present. \n Otherwise it shall not be present.\nNOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the \n actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the \n transport header of the packets or it may be an identifier used between the application \n and the NFVI networking infrastructure to identify the network sub-interface of the trunk \n port in question. In the latter case the NFVI infrastructure will map this local segmentationId \n to whatever segmentationId is actually used by the NFVIΓÇÖs transport technology.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "required": [
+ "macAddress"
+ ]
+ },
+ {
+ "required": [
+ "ipAddresses"
+ ]
+ }
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "addresses"
+ ]
+ },
+ {
+ "required": [
+ "addressRange"
+ ]
+ }
+ ],
+ "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 notes 3 and 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": [
- "addressRange"
- ]
- }
- ],
- "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 notes 3 and 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"
- ],
- "properties": {
- "type": {
- "description": "The type of the IP addresses. Permitted values: IPV4, IPV6.\n",
+ "type"
+ ],
+ "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",
- "enum": [
- "IPV4",
- "IPV6"
- ]
- },
- "addresses": {
- "description": "Fixed addresses assigned (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
- "type": "array",
- "items": {
+ "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 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"
}
- },
- "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 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 other resource provider. It is expected to be unique within the VIM instance.\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.\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"
+ }
+ }
}
}
- },
- "vnfLinkPortId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be 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"
+ },
+ "parentCpId": {
+ "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 5 and 6. 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 with the intention of being globally unique.\n",
"type": "string"
- },
- "parentCpId": {
- "description": "This 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"
- },
- "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 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"
}
+ },
+ "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 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"
}
}
- },
- "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 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"
}
+ },
+ "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 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"
}
}
},
"vnfVirtualLinkResourceInfo": {
- "description": "Information about the virtualised network resources used by the VLs of the VNF instance. See note 6. 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": "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. NOTE: If only the value or the presence of this attribute is changed in the \"VnfVirtualLinkResourceInfo\" \n structure by an LCM operation occurrence, this does not represent a change that requires including a \n related \"AffectedVirtualLink\" structure in the VNF LCM operation occurrence notifications or the \n \"VnfLcmOpOcc\" structure related to this LCM operation occurrence.\n",
- "type": "object",
- "required": [
- "id",
- "vnfVirtualLinkDescId",
- "networkResource",
- "vnfLinkPorts"
- ],
- "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"
- },
- "vnfVirtualLinkDescId": {
- "description": "An identifier that is unique within a VNF descriptor.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "networkResource": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by an internal VL instance in a VNF instance. NOTE: If only the value or the presence of this attribute is changed in the \"VnfVirtualLinkResourceInfo\" \n structure by an LCM operation occurrence, this does not represent a change that requires including a \n related \"AffectedVirtualLink\" structure in the VNF LCM operation occurrence notifications or the \n \"VnfLcmOpOcc\" structure related to this LCM operation occurrence.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "vnfVirtualLinkDescId",
+ "networkResource",
+ "vnfLinkPorts"
+ ],
+ "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"
+ },
+ "vnfVirtualLinkDescId": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "networkResource": {
+ "required": [
+ "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",
+ "properties": {
+ "vimConnectionId": {
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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": {
+ "description": "This type represents a link port of an internal VL of a VNF.\nNOTE 1: Either cpInstanceId with cpInstanceType set to \"EXT_CP\" or any combination of cpInstanceId\n with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId (i.e. one or both of them) shall be \n present for a VnfLinkPortInfo. In case both cpInstanceId with cpInstanceType set to \"VNFC_CP\" \n and vipCpInstanceId are present, the two different CP instances share the linkport.\nNOTE 2: Annex A.4 of ETSI GS NFV-IFA 007 provides examples for configurations where both vipCpInstanceId\n and vnfcCpInstanceId are present (UC#5 and UC#5-b), only vnfcCpInstanceId is present (UC#2), or \n only vipCpInstanceId is present (UC6 and UC#6-b).\nNOTE 3: The value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\"\n attribute.\n",
+ "type": "object",
"required": [
- "resourceId"
+ "id",
+ "resourceHandle"
],
- "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",
"properties": {
- "vimConnectionId": {
- "description": "An identifier with the intention of being globally unique.\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"
},
- "resourceProviderId": {
- "description": "An identifier with the intention of being globally unique.\n",
+ "resourceHandle": {
+ "required": [
+ "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",
+ "properties": {
+ "vimConnectionId": {
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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"
},
- "resourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "cpInstanceType": {
+ "description": "Type of the CP instance that is identified by cpInstanceId. Shall be present if \"cpInstanceId\" is present and shall be absent otherwise.\nPermitted values: - VNFC_CP: The link port is connected to a VNFC CP. -\tEXT_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"
},
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
+ "trunkResourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\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": {
- "description": "This type represents a link port of an internal VL of a VNF. It shall comply with the provisions defined in table 5.5.3.8 1.\nNOTE 1: Either cpInstanceId with cpInstanceType set to \"EXT_CP\" or any combination of cpInstanceId\n with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId (i.e. one or both of them) shall be \n present for a VnfLinkPortInfo. In case both cpInstanceId with cpInstanceType set to \"VNFC_CP\" \n and vipCpInstanceId are present, the two different CP instances share the linkport.\nNOTE 2: Annex A.4 of ETSI GS NFV-IFA 007 provides examples for configurations where both vipCpInstanceId\n and vnfcCpInstanceId are present (UC#5 and UC#5-b), only vnfcCpInstanceId is present (UC#2), or \n only vipCpInstanceId is present (UC6 and UC#6-b).\nNOTE 3: The value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\"\n attribute.\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 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"
+ }
+ }
+ },
+ "virtualStorageResourceInfo":{
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance.\nNOTE: If only the value or the presence of this attribute is changed in the \"VirtualStorageResourceInfo\" structure by an LCM operation occurrence, this does not represent a change that requires including a related \"AffectedVirtualStorage\" structure in the VNF LCM operation occurrence notifications or the \"VnfLcmOpOcc\" structure related to this LCM operation occurrence.\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": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "storageResource": {
+ "required": [
+ "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",
+ "properties": {
+ "vimConnectionId": {
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At least one attribute shall be present.\n",
"type": "object",
- "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": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\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",
+ "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"
},
- "cpInstanceType": {
- "description": "Type of the CP instance that is identified by cpInstanceId. Shall be present if \"cpInstanceId\" is present and shall be absent otherwise.\nPermitted values: - VNFC_CP: The link port is connected to a VNFC CP. -\tEXT_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",
+ "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"
},
- "trunkResourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\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 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"
}
}
+ },
+ "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"
}
- },
- "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 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"
}
+ },
+ "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 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"
}
}
},
- "virtualStorageResourceInfo": {
- "description": "Information on the virtualised storage resource(s) used as storage for the VNF instance.\n",
+ "vnfcInfo": {
+ "description": "Information about the VNFC instances.\n",
"type": "array",
"items": {
- "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance.\nNOTE: If only the value or the presence of this attribute is changed in the \"VirtualStorageResourceInfo\" structure by an LCM operation occurrence, this does not represent a change that requires including a related \"AffectedVirtualStorage\" structure in the VNF LCM operation occurrence notifications or the \"VnfLcmOpOcc\" structure related to this LCM operation occurrence.\n",
+ "description": "This type represents the information about a VNFC instance that is part of a VNF instance. * NOTE:\tThis allows to represent the error condition that a VNFC instance has lost its resources.\n",
"type": "object",
"required": [
"id",
- "virtualStorageDescId",
- "storageResource"
+ "vduId",
+ "vnfcState"
],
"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": "An identifier that is unique within a VNF descriptor.\n",
+ "vduId": {
+ "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",
+ "vnfcResourceInfoId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
"type": "string"
},
- "storageResource": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
- "type": "string"
- }
- }
- },
- "reservationId": {
- "description": "An identifier with the intention of being globally unique.\n",
+ "vnfcState": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
"type": "string"
},
- "metadata": {
+ "vnfcConfigurableProperties": {
"description": "This 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"
}
}
}
},
- "vnfcInfo": {
- "description": "Information about the VNFC instances.\n",
+ "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 represents the information about a VNFC instance that is part of a VNF instance. * NOTE:\tThis allows to represent the error condition that a VNFC instance has lost its resources.\n",
+ "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. Within the CISM, an MCIO controller monitors the actual state of an MCIO representing the set of VNFC instances realized by one or a set of OS containers and compare it to the desired state as specified in the respective declarative descriptor. It triggers actions toward the CIS to align the actual to the desired state. Monitoring the actual state includes monitoring the number of MCIO instances available at any specific point in time. In addition, an MCIO controller maintains properties and runtime information on the MCIO instances which have been created based on the same VDU. The McioInfo data structure provides the runtime information on the MCIOs obtained from the MCIO controller.\nNOTE: There are different types of MCIOs. The set of VNFC instances based on the same VDU is represented \n by one MCIO, e.g. of type Deployment. Each individual VNFC instance is represented by another type \n of MCIO, e.g. a POD.\n\nRuntime information of the set of OS containers realizing an individual VNFC instance is not part of the McioInfo data structure; such runtime information is provided in the ResourceHandle data structure referenced from the VnfcResourceInfo. The McioInfo does not provide runtime information of a constituent VNFC instance created based on a specific VDU.\nNOTE 1: The type of MCIO as specified in the declarative descriptor of the MCIO, and that can be read from \n the CISM. EXAMPLE: In case of MCIOs managed by Kubernetes®, the type of MCIO corresponds to the \n “kind” property of the declarative descriptor.\nNOTE 2: If the attribute additionalInfo is present, it may contain runtime information on the actual and \n desired state of the MCIO(s). \nNOTE 3: When the container infrastructure service is a Kubernetes® instance, the mcioId is the combined \n values from the kind and name fields of the Kubernetes resource object, separated by a slash. \n Example: \"Deployment/abcd\". \nNOTE 4: When the container infrastructure service is a Kubernetes® instance, the mcioName is the name \n field of the resource object. \n",
"type": "object",
"required": [
- "id",
+ "mcioId",
+ "mcioName",
+ "mcioNamespace",
"vduId",
- "vnfcState"
+ "cismId",
+ "mcioType",
+ "desiredInstances",
+ "availableInstances"
],
"properties": {
- "id": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "mcioId": {
+ "description": "An identifier with the intention of being globally unique.\n",
"type": "string"
},
- "vduId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "mcioName": {
+ "description": "Human readable name of this MCIO. See note 4.\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",
+ "mcioNamespace": {
+ "description": "Namespace of this MCIO.\n",
"type": "string"
},
- "vnfcState": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "vduId": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
"type": "string"
},
- "vnfcConfigurableProperties": {
+ "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 5.5.4.9. Additional values are also permitted. See note 1.\n",
+ "type": "string",
+ "enum": [
+ "Deployment",
+ "Statefulset"
+ ]
+ },
+ "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 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/VNFLifecycleManagement-API/schemas/vnfInstances.schema.json b/SOL002/VNFLifecycleManagement-API/schemas/vnfInstances.schema.json
index 01def0b9bfd37fddbc277b817dd9b1668a6b0acf..0b112657efa5cb4701761b670a6498321307ab72 100644
--- a/SOL002/VNFLifecycleManagement-API/schemas/vnfInstances.schema.json
+++ b/SOL002/VNFLifecycleManagement-API/schemas/vnfInstances.schema.json
@@ -2,1539 +2,2330 @@
"type": "array",
"items": {
"description": "This type represents a VNF instance. * NOTE 1:\tModifying the value of this attribute shall not be performed when conflicts exist\n between the previous and the newly referred VNF package, i.e. when the new VNFD is\n changed with respect to the previous VNFD in other aspects than merely referencing\n to other VNF software images. In order to avoid misalignment of the VnfInstance with\n the current VNF's on-boarded VNF package, the values of attributes in the VnfInstance\n that have corresponding attributes in the VNFD shall be kept in sync with the values in the VNFD.\n* NOTE 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\n applicable to a VNF. Some of these are set prior to instantiation and cannot be modified\n if the VNF is instantiated, some are set prior to instantiation (are part of initial configuration)\n and can be modified later, and others can be set only after instantiation.\n The applicability of certain configuration may depend on the VNF and the required operation of\n the VNF at a certain point in time.\n* NOTE 4:\tUpon creation of the VnfInstance structure, the VNFM shall create and initialize all child\n attributes of \"vnfConfigurableProperties\", \"metadata\" and \"extensions\" that were declared\n in the VNFD with a defined initial value. The defined initial values can be declared in the VNFD,\n and/or, in case of \"metadata\", obtained from the \"CreateVnfRequest\" structure. Child attributes of\n \"vnfConfigurableProperties\", \"metadata\" and \"extensions\" that have no defined initial value shall\n not be created, in order to be consistent with the semantics of the JSON Merge Patch method\n (see IETF RFC 7396) that interprets null values as deletion request.\n* NOTE 5:\tIt is possible to have several ExtManagedVirtualLinkInfo for the same VNF internal VL in case\n of a multi-site VNF spanning several VIMs. The set of ExtManagedVirtualLinkInfo corresponding\n to the same VNF internal VL shall indicate so by referencing to the same VnfVirtualLinkDesc\n and externally-managed multi-site VL instance (refer to clause 5.5.3.5).\n* NOTE 6:\tEven though externally-managed internal VLs are also used for VNF-internal connectivity,\n they shall not be listed in the \"vnfVirtualLinkResourceInfo\" attribute as this would be redundant.\n",
- "type": "object",
- "required": [
- "id",
- "vnfdId",
- "vnfProvider",
- "vnfProductName",
- "vnfSoftwareVersion",
- "vnfdVersion",
- "instantiationState",
- "_links"
- ],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfInstanceName": {
- "description": "Name of the VNF instance. This attribute can be modified with the PATCH method.\n",
- "type": "string"
- },
- "vnfInstanceDescription": {
- "description": "Human-readable description of the VNF instance. This attribute can be modified with the PATCH method.\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.\n",
- "type": "string"
- },
- "vnfdVersion": {
- "description": "A version.\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 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"
- },
- "instantiationState": {
- "description": "The instantiation state of the VNF.\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": "An identifier that is unique within a VNF descriptor.\n",
- "type": "string"
- },
- "vnfState": {
- "description": "STARTED: The VNF instance is up and running. STOPPED: The VNF instance has been shut down.\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. This attribute shall be present if the VNF supports scaling. See clause B.2 for an explanation of VNF scaling.\n",
- "type": "array",
- "items": {
- "required": [
- "aspectId",
- "scaleLevel"
- ],
- "type": "object",
- "properties": {
- "aspectId": {
- "description": "An identifier that is unique within a VNF descriptor.\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"
- }
- }
- }
- },
- "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": "An identifier that is unique within a VNF descriptor.\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"
- }
- }
- }
- },
- "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 5.5.3.17 1.\nNOTE 1:\tThe attributes \"associatedVnfcCpId\", \"associatedVipCpId\" and \"associatedVnfVirtualLinkId\" \n are mutually exclusive. Exactly one shall be present.\nNOTE 2:\tAn external CP instance is not associated to a link port in the cases indicated for the \n “extLinkPorts†attribute in clause 4.4.1.11.\n",
- "type": "object",
- "required": [
- "id",
- "cpdId",
- "cpConfigId",
- "cpProtocolInfo"
- ],
- "oneOf": [
- {
- "required": [
- "associatedVnfcCpId"
- ]
- },
- {
- "required": [
- "associatedVipCpId"
- ]
- },
- {
- "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": "An identifier that is unique within a VNF descriptor.\n",
- "type": "string"
- },
- "cpConfigId": {
- "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"
- },
- "cpProtocolInfo": {
- "description": "Network protocol information for this CP.\n",
- "type": "array",
- "items": {
- "description": "This type describes the protocol layer(s) that a CP uses together with protocol-related information, like addresses. It shall comply with the provisions defined in table 5.5.3.9b-1.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the \n present document in a backwards-compatible way. In the current version of the present document, only IP over \n Ethernet is supported.\n",
- "type": "object",
- "required": [
- "layerProtocol"
- ],
- "properties": {
- "layerProtocol": {
- "description": "The identifier of layer(s) and protocol(s) associated to the network address information.\nPermitted values: IP_OVER_ETHERNET See note.\n",
- "type": "string",
- "enum": [
- "IP_OVER_ETHERNET"
- ]
- },
- "ipOverEthernet": {
- "description": "This type represents information about a network address that has been assigned. It shall comply with the provisions defined in table 5.5.3.10-1.\nNOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, segmentationId shall be present. \n Otherwise it shall not be present.\nNOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the \n actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the \n transport header of the packets or it may be an identifier used between the application \n and the NFVI networking infrastructure to identify the network sub-interface of the trunk \n port in question. In the latter case the NFVI infrastructure will map this local segmentationId \n to whatever segmentationId is actually used by the NFVI’s transport technology.\n",
- "type": "object",
- "anyOf": [
- {
- "required": [
- "macAddress"
- ]
- },
- {
- "required": [
- "ipAddresses"
- ]
- }
- ],
- "oneOf": [
- {
- "required": [
- "addresses"
- ]
- },
- {
- "required": [
- "addressRange"
- ]
- }
- ],
- "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 notes 3 and 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"
- ],
- "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. 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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- }
- }
- }
- }
- }
- }
- }
- }
- },
- "extLinkPortId": {
- "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 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"
- },
- "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"
- },
- "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.\nMay 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 5.5.3.28-1.\nNOTE 1:\tIt is possible that there is no associated VnfcCp because the VIP CP is available but not associated yet. NOTE 2: If only the value or the presence of this attribute is changed in the \"VipCpInfo\" structure by an LCM operation occurrence, this does not represent a change that requires including a related \"AffectedVipCp\" structure in the VNF LCM operation occurrence notifications or the \"VnfLcmOpOcc\" structure related to this LCM operation occurrence.\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": "An identifier that is unique within a VNF descriptor.\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 uses together with protocol-related information, like addresses. It shall comply with the provisions defined in table 5.5.3.9b-1.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the \n present document in a backwards-compatible way. In the current version of the present document, only IP over \n Ethernet is supported.\n",
- "type": "object",
- "required": [
- "layerProtocol"
- ],
- "properties": {
- "layerProtocol": {
- "description": "The identifier of layer(s) and protocol(s) associated to the network address information.\nPermitted values: IP_OVER_ETHERNET See note.\n",
- "type": "string",
- "enum": [
- "IP_OVER_ETHERNET"
- ]
- },
- "ipOverEthernet": {
- "description": "This type represents information about a network address that has been assigned. It shall comply with the provisions defined in table 5.5.3.10-1.\nNOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, segmentationId shall be present. \n Otherwise it shall not be present.\nNOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the \n actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the \n transport header of the packets or it may be an identifier used between the application \n and the NFVI networking infrastructure to identify the network sub-interface of the trunk \n port in question. In the latter case the NFVI infrastructure will map this local segmentationId \n to whatever segmentationId is actually used by the NFVI’s transport technology.\n",
- "type": "object",
- "anyOf": [
- {
- "required": [
- "macAddress"
- ]
- },
- {
- "required": [
- "ipAddresses"
- ]
- }
- ],
- "oneOf": [
- {
- "required": [
- "addresses"
- ]
- },
- {
- "required": [
- "addressRange"
- ]
- }
- ],
- "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 notes 3 and 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"
- ],
- "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. 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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- }
- }
- }
- }
- }
- }
- }
- }
- },
- "associatedVnfcCpIds": {
- "description": "Identifiers of the VnfcCps that share the virtual IP addresse allocated to the VIP CP instance. See note 1.\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": "Metadata about this VIP CP.\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 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"
- }
- }
- }
- }
- },
- "extVirtualLinkInfo": {
- "description": "Information about the external VLs the VNF instance is connected to.\n",
- "type": "array",
- "items": {
- "description": "This type represents information about an external VL. It shall comply with the provisions defined in table 5.5.3.2-1.\nNOTE:\tThis attribute reflects the current configuration information that has resulted from merging into this attribute \n the \"VnfExtCpData\" information which was passed as part of the \"ExtVirtualLinkData\" structure in the input of the \n most recent VNF LCM operation such as \"InstantiateVnfRequest\", \"ChangeExtVnfConnectivityRequest\", \"ChangeVnfFlavourRequest\" \n or \"ChangeCurrentVnfPkgRequest\", or in the Grant response. If applying such change results in an empty list of \n \"currentVnfExtCpData\" structure instances, the affected instance of \"ExtVirtualLinkInfo\" shall be removed from its \n parent data structure.\n",
- "type": "object",
- "required": [
- "id",
- "resourceHandle",
- "currentVnfExtCpData"
- ],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceHandle": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\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. It shall comply with the provisions defined in table 5.5.3.9-1.\nNOTE 1:\tThe use cases UC#4 and UC#5 in clause A.4 of ETSI GS NFV-IFA 007 provide examples for such a configuration. NOTE 2:\tThe 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": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\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.\n",
- "type": "string"
- }
- }
- }
- },
- "currentVnfExtCpData": {
- "description": "Allows the API consumer to read the current CP configuration information for the connection of external CPs to the external virtual link. See note.\n",
- "type": "array",
- "items": {
- "description": "This type represents configuration information for external CPs created. * NOTE 1: \tIn case this identifier refers to a CPD with trunking enabled, the external CP instances created\n from this CPD will represent ports in a trunk.\n* NOTE 2: \tWithin one VNF instance, all VNFC instances created from a particular VDU have the same external\n connectivity. Thus, given a particular value of the \"cpdId\" attribute, there shall be one\n \"cpConfig\" entry for each VNFC instance that has been or can be created from a VDU which includes\n a CPD identified by the \"cpdId\" attribute. If the cpConfig represents a subport in a trunk,\n all \"cpConfig\" entries in this list shall have the same segmentationId, which means they are\n connected to the same set of external VLs via the trunk.\n* NOTE 3: \tThe map entry value shall be set to \"null\" in order to delete a \"VnfExtCpConfig\" entry identified\n by a particular key value from the map, i.e. for the disconnection of an existing external\n CP instance addressed by cpInstanceId in the deleted map entry from a particular external\n virtual link, and deletion of that instance in case it represents a subport. Deleting the\n last key from the map removes the affected instance of the \"VnfExtCpData\" structure from\n its parent data structure.\n* NOTE 4: If, as defined by the input parameters of a \"ChangeVnfFlavour\", \"ChangeExtVnfConnectivity\" or \n \"ChangeCurrentVnfPkg\" operation or as part of the Grant response for any of these operations, a \n cpConfig map entry identified by a particular map key value is moved into another \"ExtVirtualLinkData\"\n or \"VnfExtCpData\" structure, this particular cpConfig map entry may be used by an external CP instance\n different than the one that has used it before the operation, or by no external CP instance at all.\n Renaming a CPD identifier during the \"changeCurrentVnfPkg\" operation does not count as moving the\n related \"cpConfig\" map entries to a new \"extCpData\" structure.\n",
- "type": "object",
- "required": [
- "cpdId"
- ],
- "properties": {
- "cpdId": {
- "description": "An identifier that is unique within a VNF descriptor.\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). See notes 2, 3 and 4.\n",
- "type": "object",
- "additionalProperties": {
- "description": "This type represents an externally provided link port or network address information per instance of an external connection point. In case a link port is provided, the VNFM shall use that link port when connecting the external CP to the external VL. In a link port is not provided, the VNFM shall create a link port on the external VL, and use that link port to connect the external CP to the external VL. * NOTE: The following conditions apply to the attributes \"linkPortId\" and \"cpProtocolData\":\n 1) Void.\n 2) At least one of the \"linkPortId\" and \"cpProtocolData\" attributes shall be present for an external\n CP instance representing a subport that is to be created, or an external CP instance that is to be\n created by creating the corresponding VNFC or VNF instance during the current or a subsequent LCM\n operation, or for an existing external CP instance that is to be re-configured or added to a\n 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\n a pre created link port, and the VNFM can use means outside the scope of the present document to obtain\n the pre-configured address information for the connection point from the resource representing\n the link port.\n 5) If both \"cpProtocolData\" and \"linkportId\" are provided, the API consumer shall ensure that the\n cpProtocolData can be used with the pre-created link port referenced by \"linkPortId\".\n",
- "anyOf": [
- {
- "required": [
- "linkPortId"
- ]
- },
- {
- "required": [
- "cpProtocolData"
- ]
- }
- ],
- "type": "object",
- "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 to the VNFM the need to create a dedicated link port for the external CP. If set to True, the VNFM shall create a link port. If set to False, the VNFM shall not create a link port. 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 note.\n",
- "type": "array",
- "items": {
- "description": "This type represents network protocol data. * NOTE:\tThis attribute allows to signal the addition of further types of layer and protocol\n in future versions of the present document in a backwards-compatible way. In the current\n 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). See note.\n",
- "type": "string",
- "enum": [
- "IP_OVER_ETHERNET"
- ]
- },
- "ipOverEthernet": {
- "description": "This type represents network address data for IP over Ethernet. * NOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. * NOTE 2:\tExactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present. * NOTE 3:\tIf the CP instance represents a subport in a trunk, segmentationId shall be present.\n Otherwise it shall not be present.\n* NOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the actual\n network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header\n of the packets or it may be an identifier used between the application and the NFVI networking\n infrastructure to identify the network sub-interface of the trunk port in question. In the latter\n case the NFVI infrastructure will map this local segmentationId to whatever segmentationId is\n actually used by the NFVI’s transport technology.\n",
- "type": "object",
- "anyOf": [
- {
- "required": [
- "macAddress"
- ]
- },
- {
- "required": [
- "ipAddresses"
- ]
- }
- ],
- "oneOf": [
- {
- "required": [
- "fixedAddresses"
- ]
- },
- {
- "required": [
- "numDynamicAddresses"
- ]
- },
- {
- "required": [
- "ipAddressRange"
- ]
- }
- ],
- "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: -\tVLAN: the subport uses VLAN as encapsulation type. -\tINHERIT: the subport gets its segmentation type from the network it’s 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"
- ],
- "properties": {
- "type": {
- "description": "The type of the IP addresses. Permitted values: IPV4, IPV6.\n",
- "type": "string",
- "enum": [
- "IPV4",
- "IPV6"
- ]
- },
- "fixedAddresses": {
- "description": "Fixed addresses to assign (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"
- }
- },
- "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. 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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- },
- "extManagedVirtualLinkInfo": {
- "description": "Information about the externally managed internal VLs of the VNF instance. See note 5 and note 6. 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 VNF internal VL shall indicate so by referencing to the same VnfVirtualLinkDesc and externally-managed multi-site VL instance (refer to clause 5.5.3.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": "array",
- "items": {
- "type": "object",
- "required": [
- "id",
- "vnfVirtualLinkDescId",
- "networkResource"
- ],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfVirtualLinkDescId": {
- "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"
- },
- "networkResource": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
- "type": "string"
- }
- }
- },
- "vnfLinkPorts": {
- "description": "Link ports of this VL.\n",
- "type": "array",
- "items": {
- "description": "This type represents a link port of an internal VL of a VNF. It shall comply with the provisions defined in table 5.5.3.8 1.\nNOTE 1: Either cpInstanceId with cpInstanceType set to \"EXT_CP\" or any combination of cpInstanceId\n with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId (i.e. one or both of them) shall be \n present for a VnfLinkPortInfo. In case both cpInstanceId with cpInstanceType set to \"VNFC_CP\" \n and vipCpInstanceId are present, the two different CP instances share the linkport.\nNOTE 2: Annex A.4 of ETSI GS NFV-IFA 007 provides examples for configurations where both vipCpInstanceId\n and vnfcCpInstanceId are present (UC#5 and UC#5-b), only vnfcCpInstanceId is present (UC#2), or \n only vipCpInstanceId is present (UC6 and UC#6-b).\nNOTE 3: The value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\"\n attribute.\n",
- "type": "object",
- "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": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\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.\nPermitted values: - VNFC_CP: The link port is connected to a VNFC CP. -\tEXT_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.\n",
- "type": "string"
- }
- }
- }
- }
- }
- }
- },
- "monitoringParameters": {
- "description": "Active monitoring parameters.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": [
- "id",
- "performanceMetric"
- ],
- "properties": {
- "id": {
- "description": "An identifier that is unique within a VNF descriptor.\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. * NOTE 1:\tETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on TOSCA specifications. * NOTE 2:\tA VNFC CP is \"connected to\" an external CP if the VNFC CP is connected to an internal VL that\n exposes an external CP. A VNFC CP is \"exposed as\" an external CP if it is connected directly\n to an external VL.\n* NOTE 3:\tThe information can be omitted because it is already available as part of the external CP information. * NOTE 4: If only the value or the presence of this attribute is changed in the \"VnfcResourceInfo\" structure by \n an LCM operation occurrence, this does not represent a change that requires including a related \"AffectedVnfc\"\n structure in the VNF LCM operation occurrence notifications or the \"VnfLcmOpOcc\" structure related to \n this LCM operation occurrence.\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"
- },
- "vduId": {
- "description": "An identifier that is unique within a VNF descriptor.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "computeResource": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
- "type": "string"
- }
- }
- },
- "storageResourceIds": {
- "description": "References to the VirtualStorage resources. 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": "All the CPs of the VNFC instance.\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 VNF descriptor.\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. The information can be omitted because it is already available as part of the external CP information. See note 3.\n",
- "type": "array",
- "items": {
- "description": "This type describes the protocol layer(s) that a CP uses together with protocol-related information, like addresses. It shall comply with the provisions defined in table 5.5.3.9b-1.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the \n present document in a backwards-compatible way. In the current version of the present document, only IP over \n Ethernet is supported.\n",
- "type": "object",
- "required": [
- "layerProtocol"
- ],
- "properties": {
- "layerProtocol": {
- "description": "The identifier of layer(s) and protocol(s) associated to the network address information.\nPermitted values: IP_OVER_ETHERNET See note.\n",
- "type": "string",
- "enum": [
- "IP_OVER_ETHERNET"
- ]
- },
- "ipOverEthernet": {
- "description": "This type represents information about a network address that has been assigned. It shall comply with the provisions defined in table 5.5.3.10-1.\nNOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, segmentationId shall be present. \n Otherwise it shall not be present.\nNOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the \n actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the \n transport header of the packets or it may be an identifier used between the application \n and the NFVI networking infrastructure to identify the network sub-interface of the trunk \n port in question. In the latter case the NFVI infrastructure will map this local segmentationId \n to whatever segmentationId is actually used by the NFVI’s transport technology.\n",
- "type": "object",
- "anyOf": [
- {
- "required": [
- "macAddress"
- ]
- },
- {
- "required": [
- "ipAddresses"
- ]
- }
- ],
- "oneOf": [
- {
- "required": [
- "addresses"
- ]
- },
- {
- "required": [
- "addressRange"
- ]
- }
- ],
- "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 notes 3 and 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"
- ],
- "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. 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 other resource provider. It is expected to be unique within the VIM instance.\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"
- },
- "parentCpId": {
- "description": "This 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"
- },
- "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 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"
- }
- }
- }
- },
- "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 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"
- }
- }
- }
- },
- "vnfVirtualLinkResourceInfo": {
- "description": "Information about the virtualised network resources used by the VLs of the VNF instance. See note 6. 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": "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. NOTE: If only the value or the presence of this attribute is changed in the \"VnfVirtualLinkResourceInfo\" \n structure by an LCM operation occurrence, this does not represent a change that requires including a \n related \"AffectedVirtualLink\" structure in the VNF LCM operation occurrence notifications or the \n \"VnfLcmOpOcc\" structure related to this LCM operation occurrence.\n",
- "type": "object",
- "required": [
- "id",
- "vnfVirtualLinkDescId",
- "networkResource",
- "vnfLinkPorts"
- ],
- "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"
- },
- "vnfVirtualLinkDescId": {
- "description": "An identifier that is unique within a VNF descriptor.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "networkResource": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\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": {
- "description": "This type represents a link port of an internal VL of a VNF. It shall comply with the provisions defined in table 5.5.3.8 1.\nNOTE 1: Either cpInstanceId with cpInstanceType set to \"EXT_CP\" or any combination of cpInstanceId\n with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId (i.e. one or both of them) shall be \n present for a VnfLinkPortInfo. In case both cpInstanceId with cpInstanceType set to \"VNFC_CP\" \n and vipCpInstanceId are present, the two different CP instances share the linkport.\nNOTE 2: Annex A.4 of ETSI GS NFV-IFA 007 provides examples for configurations where both vipCpInstanceId\n and vnfcCpInstanceId are present (UC#5 and UC#5-b), only vnfcCpInstanceId is present (UC#2), or \n only vipCpInstanceId is present (UC6 and UC#6-b).\nNOTE 3: The value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\"\n attribute.\n",
- "type": "object",
- "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": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\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.\nPermitted values: - VNFC_CP: The link port is connected to a VNFC CP. -\tEXT_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.\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 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"
- }
- }
- }
- },
- "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.\nNOTE: If only the value or the presence of this attribute is changed in the \"VirtualStorageResourceInfo\" structure by an LCM operation occurrence, this does not represent a change that requires including a related \"AffectedVirtualStorage\" structure in the VNF LCM operation occurrence notifications or the \"VnfLcmOpOcc\" structure related to this LCM operation occurrence.\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": "An identifier that is unique within a VNF descriptor.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "storageResource": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\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 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"
- }
- }
- }
- },
- "vnfcInfo": {
- "description": "Information about the VNFC instances.\n",
- "type": "array",
- "items": {
- "description": "This type represents the information about a VNFC instance that is part of a VNF instance. * NOTE:\tThis allows to represent the error condition that a VNFC instance has lost its resources.\n",
- "type": "object",
- "required": [
- "id",
- "vduId",
- "vnfcState"
- ],
- "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"
- },
- "vduId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\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"
- },
- "vnfcState": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "vnfcConfigurableProperties": {
- "description": "This 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"
- }
- }
- }
- }
- }
- },
- "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 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"
- },
- "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 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"
- },
- "_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 using an absolute URI.\n",
- "type": "object",
- "required": [
- "href"
- ],
- "properties": {
- "href": {
- "description": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- }
- }
- },
- "indicators": {
- "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"
- }
- }
- },
- "instantiate": {
- "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"
- }
- }
- },
- "terminate": {
- "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"
- }
- }
- },
- "scale": {
- "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"
- }
- }
- },
- "scaleToLevel": {
- "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"
- }
- }
- },
- "changeFlavour": {
- "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"
- }
- }
- },
- "heal": {
- "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"
- }
- }
- },
- "operate": {
- "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"
- }
- }
- },
- "changeExtConn": {
- "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"
- }
- }
- },
- "createSnapshot": {
- "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"
- }
- }
- },
- "revertToSnapshot": {
- "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"
- }
- }
- },
- "changeCurrentVnfPkg": {
- "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"
- }
- }
- }
- }
- }
- }
- }
+ "type": "object",
+ "required": [
+ "id",
+ "vnfdId",
+ "vnfProvider",
+ "vnfProductName",
+ "vnfSoftwareVersion",
+ "vnfdVersion",
+ "instantiationState",
+ "_links"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfInstanceName": {
+ "description": "Name of the VNF instance. This attribute can be modified with the PATCH method.\n",
+ "type": "string"
+ },
+ "vnfInstanceDescription": {
+ "description": "Human-readable description of the VNF instance. This attribute can be modified with the PATCH method.\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.\n",
+ "type": "string"
+ },
+ "vnfdVersion": {
+ "description": "A version.\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 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"
+ },
+ "instantiationState": {
+ "description": "The instantiation state of the VNF.\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": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "vnfState": {
+ "description": "STARTED: The VNF instance is up and running. STOPPED: The VNF instance has been shut down.\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. This attribute shall be present if the VNF supports scaling. See clause B.2 for an explanation of VNF scaling.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the scale level of a VNF instance related to a scaling aspect.\n",
+ "type": "object",
+ "required": [
+ "aspectId",
+ "scaleLevel"
+ ],
+ "properties": {
+ "aspectId": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "scaleToLevel": {
+ "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": {
+ "description": "This type represents the scale level of a VNF instance related to a scaling aspect.\n",
+ "type": "object",
+ "required": [
+ "aspectId",
+ "scaleLevel"
+ ],
+ "properties": {
+ "aspectId": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "scaleToLevel": {
+ "description": "An identifier with the intention of being globally unique.\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.\nNOTE 1:\tThe attributes \"associatedVnfcCpId\", \"associatedVipCpId\", \"associatedVirtualCpId\" and \n \"associatedVnfVirtualLinkId\" are mutually exclusive. Exactly one shall be present.\nNOTE 2:\tAn external CP instance is not associated to a link port in the cases indicated for the \n ΓÇ£extLinkPortsΓÇ¥ attribute in clause 4.4.1.11.\nNOTE 3: 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 \n CP, e.g. to build a link redundant mated pair in SR-IOV cases.\nNOTE 4: When more than one netAttDefResourceId is indicated, all shall belong to the same namespace.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "cpdId",
+ "cpConfigId",
+ "cpProtocolInfo"
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "associatedVnfcCpId"
+ ]
+ },
+ {
+ "required": [
+ "associatedVipCpId"
+ ]
+ },
+ {
+ "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": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "cpConfigId": {
+ "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"
+ },
+ "cpProtocolInfo": {
+ "description": "Network protocol information for this CP.\n",
+ "type": "array",
+ "items": {
+ "description": "This type describes the protocol layer(s) that a CP uses together with protocol-related information, like addresses.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the \n present document in a backwards-compatible way. In the current version of the present document, only IP over \n Ethernet is supported.\n",
+ "type": "object",
+ "required": [
+ "layerProtocol"
+ ],
+ "properties": {
+ "layerProtocol": {
+ "description": "The identifier of layer(s) and protocol(s) associated to the network address information.\nPermitted 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:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, segmentationId shall be present. \n Otherwise it shall not be present.\nNOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the \n actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the \n transport header of the packets or it may be an identifier used between the application \n and the NFVI networking infrastructure to identify the network sub-interface of the trunk \n port in question. In the latter case the NFVI infrastructure will map this local segmentationId \n to whatever segmentationId is actually used by the NFVIΓÇÖs transport technology.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "required": [
+ "macAddress"
+ ]
+ },
+ {
+ "required": [
+ "ipAddresses"
+ ]
+ }
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "addresses"
+ ]
+ },
+ {
+ "required": [
+ "addressRange"
+ ]
+ }
+ ],
+ "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 notes 3 and 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"
+ ],
+ "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. 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.\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"
+ },
+ "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 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"
+ },
+ "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 within a VNF descriptor.\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"
+ },
+ "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. It 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 with the intention of being 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.\nMay be present otherwise.\n",
+ "type": "array",
+ "items": {
+ "description": "This type provides information related to virtual IP CP.\nNOTE 1:\tIt is possible that there is no associated VnfcCp because the virtual IP CP is available but not associated yet. NOTE 2: If only the value or the presence of this attribute is changed in the \"VipCpInfo\" structure by an LCM operation occurrence, this does not represent a change that requires including a related \"AffectedVipCp\" structure in the VNF LCM operation occurrence notifications or the \"VnfLcmOpOcc\" structure related to this LCM operation occurrence.\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": "An identifier that is unique within a VNF descriptor.\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 uses together with protocol-related information, like addresses.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the \n present document in a backwards-compatible way. In the current version of the present document, only IP over \n Ethernet is supported.\n",
+ "type": "object",
+ "required": [
+ "layerProtocol"
+ ],
+ "properties": {
+ "layerProtocol": {
+ "description": "The identifier of layer(s) and protocol(s) associated to the network address information.\nPermitted 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:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, segmentationId shall be present. \n Otherwise it shall not be present.\nNOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the \n actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the \n transport header of the packets or it may be an identifier used between the application \n and the NFVI networking infrastructure to identify the network sub-interface of the trunk \n port in question. In the latter case the NFVI infrastructure will map this local segmentationId \n to whatever segmentationId is actually used by the NFVIΓÇÖs transport technology.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "required": [
+ "macAddress"
+ ]
+ },
+ {
+ "required": [
+ "ipAddresses"
+ ]
+ }
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "addresses"
+ ]
+ },
+ {
+ "required": [
+ "addressRange"
+ ]
+ }
+ ],
+ "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 notes 3 and 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"
+ ],
+ "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. 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.\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 virtual IP 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": "This 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"
+ }
+ }
+ }
+ },
+ "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 provides information related to a virtual CP instance of a VNF.\nNOTE: A consumer of the VNF LCM interface can learn the actual VNFC instances implementing the service \n accessible via the virtual CP instance by querying the \"vnfcResourceInfo\" from the \"InstantiatedVnfInfo\" \n and filtering by corresponding \"vduIds\" values.\n",
+ "type": "object",
+ "required": [
+ "cpInstanceId",
+ "cpdId",
+ "resourceHandle",
+ "vduIds"
+ ],
+ "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": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "resourceHandle": {
+ "required": [
+ "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",
+ "properties": {
+ "vimConnectionId": {
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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 uses together with protocol-related information, like addresses.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the \n present document in a backwards-compatible way. In the current version of the present document, only IP over \n Ethernet is supported.\n",
+ "type": "object",
+ "required": [
+ "layerProtocol"
+ ],
+ "properties": {
+ "layerProtocol": {
+ "description": "The identifier of layer(s) and protocol(s) associated to the network address information.\nPermitted 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:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, segmentationId shall be present. \n Otherwise it shall not be present.\nNOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the \n actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the \n transport header of the packets or it may be an identifier used between the application \n and the NFVI networking infrastructure to identify the network sub-interface of the trunk \n port in question. In the latter case the NFVI infrastructure will map this local segmentationId \n to whatever segmentationId is actually used by the NFVIΓÇÖs transport technology.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "required": [
+ "macAddress"
+ ]
+ },
+ {
+ "required": [
+ "ipAddresses"
+ ]
+ }
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "addresses"
+ ]
+ },
+ {
+ "required": [
+ "addressRange"
+ ]
+ }
+ ],
+ "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 notes 3 and 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"
+ ],
+ "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. 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.\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"
+ }
+ }
+ }
+ }
+ }
+ },
+ "vduIds": {
+ "description": "Reference to the VDU(s) which implement the service accessible via the virtual CP instance. See note.\n",
+ "type": "array",
+ "minItems": 1,
+ "items": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ }
+ },
+ "additionalServiceInfo": {
+ "description": "Additional service identification information of the virtual CP instance.\n",
+ "type": "array",
+ "items": {
+ "description": "This type provides 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 \n termination within the VNF, such as for example a URL path information in an HTTP request required \n to allow a single virtual CP IP address to be used for several HTTP based services that use the \n same port number.\n",
+ "type": "object",
+ "required": [
+ "portInfo"
+ ],
+ "properties": {
+ "portInfo": {
+ "description": "Service port numbers exposed by the virtual CP instance.\n",
+ "minItems": 1,
+ "type": "array",
+ "items": {
+ "description": "This type describes the service identifying port properties exposed by the virtual CP instance.\n",
+ "type": "object",
+ "required": [
+ "name",
+ "port",
+ "portConfigurable"
+ ],
+ "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.\nPermitted values: - TCP - UDP - SCTP\n",
+ "type": "string",
+ "enum": [
+ "TCP",
+ "UDP",
+ "SCTP"
+ ]
+ },
+ "port": {
+ "description": "The L4 port number exposed by the virtual CP instance.\n",
+ "type": "integer"
+ },
+ "portConfigurable": {
+ "description": "The Boolean is a data type having two values (true and false).\n",
+ "type": "boolean"
+ }
+ }
+ }
+ },
+ "serviceInfo": {
+ "description": "This 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"
+ }
+ }
+ }
+ },
+ "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 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"
+ }
+ }
+ }
+ },
+ "extVirtualLinkInfo": {
+ "description": "Information about the external VLs the VNF instance is connected to.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents information about an external VL.\nNOTE:\tThis attribute reflects the current configuration information that has resulted from merging into this attribute \n the \"VnfExtCpData\" information which was passed as part of the \"ExtVirtualLinkData\" structure in the input of the \n most recent VNF LCM operation such as \"InstantiateVnfRequest\", \"ChangeExtVnfConnectivityRequest\", \"ChangeVnfFlavourRequest\" \n or \"ChangeCurrentVnfPkgRequest\", or in the Grant response. If applying such change results in an empty list of \n \"currentVnfExtCpData\" structure instances, the affected instance of \"ExtVirtualLinkInfo\" shall be removed from its \n parent data structure.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "resourceHandle",
+ "currentVnfExtCpData"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceHandle": {
+ "required": [
+ "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",
+ "properties": {
+ "vimConnectionId": {
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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.\nNOTE 1:\tThe use cases UC#4 and UC#5 in clause A.4 of ETSI GS NFV-IFA 007 provide examples for such a configuration. NOTE 2:\tThe 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": {
+ "required": [
+ "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",
+ "properties": {
+ "vimConnectionId": {
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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 the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "currentVnfExtCpData": {
+ "description": "Allows the API consumer to read the current CP configuration information for the connection of external CPs to the external virtual link. See note.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents configuration information for external CPs created. * NOTE 1: \tIn case this identifier refers to a CPD with trunking enabled, the external CP instances created\n from this CPD will represent ports in a trunk.\n* NOTE 2: \tWithin one VNF instance, all VNFC instances created from a particular VDU have the same external\n connectivity. Thus, given a particular value of the \"cpdId\" attribute, there shall be one\n \"cpConfig\" entry for each VNFC instance that has been or can be created from a VDU which includes\n a CPD identified by the \"cpdId\" attribute. If the cpConfig represents a subport in a trunk,\n all \"cpConfig\" entries in this list shall have the same segmentationId, which means they are\n connected to the same set of external VLs via the trunk.\n* NOTE 3: \tThe map entry value shall be set to \"null\" in order to delete a \"VnfExtCpConfig\" entry identified\n by a particular key value from the map, i.e. for the disconnection of an existing external\n CP instance addressed by cpInstanceId in the deleted map entry from a particular external\n virtual link, and deletion of that instance in case it represents a subport. Deleting the\n last key from the map removes the affected instance of the \"VnfExtCpData\" structure from\n its parent data structure.\n* NOTE 4: If, as defined by the input parameters of a \"ChangeVnfFlavour\", \"ChangeExtVnfConnectivity\" or\n \"ChangeCurrentVnfPkg\" operation, a cpConfig map entry identified by a particular map key value \n is moved into another \"ExtVirtualLinkData\" or \"VnfExtCpData\" structure, this particular cpConfig\n map entry may be used by an external CP instance different than the one that has used it before the\n operation, or by no external CP instance at all. Renaming a CPD identifier during the \"changeCurrentVnfPkg\"\n operation does not count as moving the related \"cpConfig\" map entries to a new \"extCpData\" structure.\n",
+ "type": "object",
+ "required": [
+ "cpdId"
+ ],
+ "properties": {
+ "cpdId": {
+ "description": "An identifier that is unique within a VNF descriptor.\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 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",
+ "anyOf": [
+ {
+ "required": [
+ "linkPortId"
+ ]
+ },
+ {
+ "required": [
+ "cpProtocolData"
+ ]
+ },
+ {
+ "required": [
+ "netAttDefResourceId"
+ ]
+ }
+ ],
+ "type": "object",
+ "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 to the VNFM the need to create a dedicated link port for the external CP. If set to True, the VNFM shall create a link port. If set to False, the VNFM shall not create a link port. This attribute is only applicable for external CP instances without a floating IP address that expose a virtual IP 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 2.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents network protocol data. * NOTE:\tThis attribute allows to signal the addition of further types of layer and protocol\n in future versions of the present document in a backwards-compatible way. In the current\n 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:\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 network address data for IP over Ethernet to assign to the external CP. * NOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. * NOTE 2:\tExactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present. * NOTE 3:\tIf the CP instance represents a subport in a trunk, segmentationId shall be present.\n Otherwise it shall not be present.\n* NOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the actual\n network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header\n of the packets or it may be an identifier used between the application and the NFVI networking\n infrastructure to identify the network sub-interface of the trunk port in question. In the latter\n case the NFVI infrastructure will map this local segmentationId to whatever segmentationId is\n actually used by the NFVI's transport technology.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "required": [
+ "macAddress"
+ ]
+ },
+ {
+ "required": [
+ "ipAddresses"
+ ]
+ }
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "fixedAddresses"
+ ]
+ },
+ {
+ "required": [
+ "numDynamicAddresses"
+ ]
+ },
+ {
+ "required": [
+ "ipAddressRange"
+ ]
+ }
+ ],
+ "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: -\tVLAN: the subport uses VLAN as encapsulation type. -\tINHERIT: the subport gets its segmentation type from the network itΓÇÖs 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"
+ ],
+ "properties": {
+ "type": {
+ "description": "The type of the IP addresses. Permitted values: IPV4, IPV6.\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
+ },
+ "fixedAddresses": {
+ "description": "Fixed addresses to assign (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"
+ }
+ },
+ "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. 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.\n",
+ "type": "string"
+ }
+ }
+ }
+ }
+ }
+ },
+ "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",
+ "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"
+ }
+ }
+ }
+ }
+ }
+ },
+ "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 2, 3 and 4.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\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 contains 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": {
+ "required": [
+ "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",
+ "properties": {
+ "vimConnectionId": {
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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 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 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"
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ },
+ "extManagedVirtualLinkInfo": {
+ "description": "Information about the externally managed internal VLs of the VNF instance. See note 5 and note 6. 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 VNF internal VL shall indicate so by referencing to the same VnfVirtualLinkDesc and externally-managed multi-site VL instance (refer to clause 5.5.3.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": "array",
+ "items": {
+ "description": "This type provides information about an externally-managed virtual link.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "vnfVirtualLinkDescId",
+ "networkResource"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfVirtualLinkDescId": {
+ "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"
+ },
+ "networkResource": {
+ "required": [
+ "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",
+ "properties": {
+ "vimConnectionId": {
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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": {
+ "description": "This type represents a link port of an internal VL of a VNF.\nNOTE 1: Either cpInstanceId with cpInstanceType set to \"EXT_CP\" or any combination of cpInstanceId\n with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId (i.e. one or both of them) shall be \n present for a VnfLinkPortInfo. In case both cpInstanceId with cpInstanceType set to \"VNFC_CP\" \n and vipCpInstanceId are present, the two different CP instances share the linkport.\nNOTE 2: Annex A.4 of ETSI GS NFV-IFA 007 provides examples for configurations where both vipCpInstanceId\n and vnfcCpInstanceId are present (UC#5 and UC#5-b), only vnfcCpInstanceId is present (UC#2), or \n only vipCpInstanceId is present (UC6 and UC#6-b).\nNOTE 3: The value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\"\n attribute.\n",
+ "type": "object",
+ "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": {
+ "required": [
+ "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",
+ "properties": {
+ "vimConnectionId": {
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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.\nPermitted values: - VNFC_CP: The link port is connected to a VNFC CP. -\tEXT_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 the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "vnfNetAttDefResource": {
+ "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 contains 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": {
+ "required": [
+ "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",
+ "properties": {
+ "vimConnectionId": {
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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 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 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"
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ },
+ "monitoringParameters": {
+ "description": "Active monitoring parameters.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": [
+ "id",
+ "performanceMetric"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier that is unique within a VNF descriptor.\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": "This type represents the information on virtualised compute and storage resources used by a VNFC in a VNF instance. Depending on the form of virtualisation container of the VNFC:\n - For a VNFC based on VM, a reference to the corresponding VirtualCompute shall be provided, and\n - For a VNFC based on OS container(s), a reference to the Compute MCIO shall be provided. Hence, exposure \n of information by the VNFM to the NFVO is at the MCIO level.\nIn addition, the references to the storage resources depend on the form of the VNFC:\n - For a VNFC based on VM, storage resource identifiers shall refer to VirtualStorage resources, and\n - For a VNFC based on OS container(s), storage resource identifiers shall refer to Storage MCIOs.\n\n\n* NOTE 1:\tETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on TOSCA specifications. * NOTE 2:\tA VNFC CP is \"connected to\" an external CP if the VNFC CP is connected to an internal VL that\n exposes an external CP. A VNFC CP is \"exposed as\" an external CP if it is connected directly\n to an external VL.\n* NOTE 3:\tThe information can be omitted because it is already available as part of the external CP information. * NOTE 4: If only the value or the presence of this attribute is changed in the \"VnfcResourceInfo\" structure by \n an LCM operation occurrence, this does not represent a change that requires including a related \"AffectedVnfc\"\n structure in the VNF LCM operation occurrence notifications or the \"VnfLcmOpOcc\" structure related to \n this LCM operation occurrence.\n* NOTE 5: 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 internal CP, e.g. to build \n a link redundant mated pair in SR-IOV cases.\n* NOTE 6: 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"
+ },
+ "vduId": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "computeResource": {
+ "required": [
+ "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",
+ "properties": {
+ "vimConnectionId": {
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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 MCIO(s). 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": "All the CPs of the VNFC instance.\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 VNF descriptor.\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. The information can be omitted because it is already available as part of the external CP information. See note 3.\n",
+ "type": "array",
+ "items": {
+ "description": "This type describes the protocol layer(s) that a CP uses together with protocol-related information, like addresses.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the \n present document in a backwards-compatible way. In the current version of the present document, only IP over \n Ethernet is supported.\n",
+ "type": "object",
+ "required": [
+ "layerProtocol"
+ ],
+ "properties": {
+ "layerProtocol": {
+ "description": "The identifier of layer(s) and protocol(s) associated to the network address information.\nPermitted 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:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, segmentationId shall be present. \n Otherwise it shall not be present.\nNOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the \n actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the \n transport header of the packets or it may be an identifier used between the application \n and the NFVI networking infrastructure to identify the network sub-interface of the trunk \n port in question. In the latter case the NFVI infrastructure will map this local segmentationId \n to whatever segmentationId is actually used by the NFVIΓÇÖs transport technology.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "required": [
+ "macAddress"
+ ]
+ },
+ {
+ "required": [
+ "ipAddresses"
+ ]
+ }
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "addresses"
+ ]
+ },
+ {
+ "required": [
+ "addressRange"
+ ]
+ }
+ ],
+ "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 notes 3 and 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"
+ ],
+ "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. 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.\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"
+ }
+ }
+ }
+ }
+ }
+ },
+ "vnfLinkPortId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "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"
+ },
+ "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 5 and 6. 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 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 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"
+ }
+ }
+ }
+ },
+ "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 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"
+ }
+ }
+ },
+ "vnfVirtualLinkResourceInfo": {
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by an internal VL instance in a VNF instance. NOTE: If only the value or the presence of this attribute is changed in the \"VnfVirtualLinkResourceInfo\" \n structure by an LCM operation occurrence, this does not represent a change that requires including a \n related \"AffectedVirtualLink\" structure in the VNF LCM operation occurrence notifications or the \n \"VnfLcmOpOcc\" structure related to this LCM operation occurrence.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "vnfVirtualLinkDescId",
+ "networkResource",
+ "vnfLinkPorts"
+ ],
+ "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"
+ },
+ "vnfVirtualLinkDescId": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "networkResource": {
+ "required": [
+ "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",
+ "properties": {
+ "vimConnectionId": {
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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": {
+ "description": "This type represents a link port of an internal VL of a VNF.\nNOTE 1: Either cpInstanceId with cpInstanceType set to \"EXT_CP\" or any combination of cpInstanceId\n with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId (i.e. one or both of them) shall be \n present for a VnfLinkPortInfo. In case both cpInstanceId with cpInstanceType set to \"VNFC_CP\" \n and vipCpInstanceId are present, the two different CP instances share the linkport.\nNOTE 2: Annex A.4 of ETSI GS NFV-IFA 007 provides examples for configurations where both vipCpInstanceId\n and vnfcCpInstanceId are present (UC#5 and UC#5-b), only vnfcCpInstanceId is present (UC#2), or \n only vipCpInstanceId is present (UC6 and UC#6-b).\nNOTE 3: The value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\"\n attribute.\n",
+ "type": "object",
+ "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": {
+ "required": [
+ "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",
+ "properties": {
+ "vimConnectionId": {
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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.\nPermitted values: - VNFC_CP: The link port is connected to a VNFC CP. -\tEXT_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 the CISM or other resource provider. It is expected to be unique within the VIM instance.\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 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"
+ }
+ }
+ },
+ "virtualStorageResourceInfo":{
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance.\nNOTE: If only the value or the presence of this attribute is changed in the \"VirtualStorageResourceInfo\" structure by an LCM operation occurrence, this does not represent a change that requires including a related \"AffectedVirtualStorage\" structure in the VNF LCM operation occurrence notifications or the \"VnfLcmOpOcc\" structure related to this LCM operation occurrence.\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": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "storageResource": {
+ "required": [
+ "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",
+ "properties": {
+ "vimConnectionId": {
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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 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"
+ }
+ }
+ },
+ "vnfcInfo": {
+ "description": "Information about the VNFC instances.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the information about a VNFC instance that is part of a VNF instance. * NOTE:\tThis allows to represent the error condition that a VNFC instance has lost its resources.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "vduId",
+ "vnfcState"
+ ],
+ "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"
+ },
+ "vduId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\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"
+ },
+ "vnfcState": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "vnfcConfigurableProperties": {
+ "description": "This 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"
+ }
+ }
+ }
+ },
+ "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. Within the CISM, an MCIO controller monitors the actual state of an MCIO representing the set of VNFC instances realized by one or a set of OS containers and compare it to the desired state as specified in the respective declarative descriptor. It triggers actions toward the CIS to align the actual to the desired state. Monitoring the actual state includes monitoring the number of MCIO instances available at any specific point in time. In addition, an MCIO controller maintains properties and runtime information on the MCIO instances which have been created based on the same VDU. The McioInfo data structure provides the runtime information on the MCIOs obtained from the MCIO controller.\nNOTE: There are different types of MCIOs. The set of VNFC instances based on the same VDU is represented \n by one MCIO, e.g. of type Deployment. Each individual VNFC instance is represented by another type \n of MCIO, e.g. a POD.\n\nRuntime information of the set of OS containers realizing an individual VNFC instance is not part of the McioInfo data structure; such runtime information is provided in the ResourceHandle data structure referenced from the VnfcResourceInfo. The McioInfo does not provide runtime information of a constituent VNFC instance created based on a specific VDU.\nNOTE 1: The type of MCIO as specified in the declarative descriptor of the MCIO, and that can be read from \n the CISM. EXAMPLE: In case of MCIOs managed by Kubernetes®, the type of MCIO corresponds to the \n “kind” property of the declarative descriptor.\nNOTE 2: If the attribute additionalInfo is present, it may contain runtime information on the actual and \n desired state of the MCIO(s). \nNOTE 3: When the container infrastructure service is a Kubernetes® instance, the mcioId is the combined \n values from the kind and name fields of the Kubernetes resource object, separated by a slash. \n Example: \"Deployment/abcd\". \nNOTE 4: When the container infrastructure service is a Kubernetes® instance, the mcioName is the name \n field of the resource object. \n",
+ "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": "An identifier that is unique within a VNF descriptor.\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 5.5.4.9. Additional values are also permitted. See note 1.\n",
+ "type": "string",
+ "enum": [
+ "Deployment",
+ "Statefulset"
+ ]
+ },
+ "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 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"
+ }
+ }
+ }
+ }
+ }
+ },
+ "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 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"
+ },
+ "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 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"
+ },
+ "_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 using an absolute URI.\n",
+ "type": "object",
+ "required": [
+ "href"
+ ],
+ "properties": {
+ "href": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ }
+ }
+ },
+ "indicators": {
+ "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"
+ }
+ }
+ },
+ "instantiate": {
+ "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"
+ }
+ }
+ },
+ "terminate": {
+ "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"
+ }
+ }
+ },
+ "scale": {
+ "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"
+ }
+ }
+ },
+ "scaleToLevel": {
+ "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"
+ }
+ }
+ },
+ "changeFlavour": {
+ "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"
+ }
+ }
+ },
+ "heal": {
+ "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"
+ }
+ }
+ },
+ "operate": {
+ "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"
+ }
+ }
+ },
+ "changeExtConn": {
+ "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"
+ }
+ }
+ },
+ "createSnapshot": {
+ "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"
+ }
+ }
+ },
+ "revertToSnapshot": {
+ "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"
+ }
+ }
+ },
+ "changeCurrentVnfPkg": {
+ "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"
+ }
+ }
+ }
+ }
+ }
+ }
+}
}
\ No newline at end of file
diff --git a/SOL002/VNFLifecycleManagement-API/schemas/vnfLcmOpOcc.schema.json b/SOL002/VNFLifecycleManagement-API/schemas/vnfLcmOpOcc.schema.json
index e107aa8d5d42398955e386d58374cf4723a8860b..a28e3312b7096d742102454fce9e831686809784 100644
--- a/SOL002/VNFLifecycleManagement-API/schemas/vnfLcmOpOcc.schema.json
+++ b/SOL002/VNFLifecycleManagement-API/schemas/vnfLcmOpOcc.schema.json
@@ -1,5 +1,5 @@
{
- "description": "This type represents a VNF lifecycle management operation occurrence. Shall be set to the value of the \"id\" attribute in the \"Grant\" representing the associated \"Individual Grant\", if such grant exists. * NOTE 1:\tThis allows the API consumer to obtain the information contained in the latest \"result\"\n notification if it has not received it due to an error or a wrongly configured subscription filter.\n* NOTE 2:\tNot more than one of changedInfo and modificationsTriggeredByVnfPkgChange shall be present. * NOTE 3:\tFor a particular affected VL, there shall be as many \"AffectedVirtualLink\" entries as needed\n for signalling the different types of changes, i.e. one per virtual link and change type.\n For instance, in the case of signaling affected VL instances involving the addition of a\n particular VL instance with links ports, one \"AffectedVirtualLink\" entry signals the addition\n of the VL by using the \"changeType\" attribute of \"AffectedVirtualLink\" structure equal to \"ADDED\",\n and another \"AffectedVirtualLink\" entry signals the addition of VNF link ports of the VL by using the\n \"changeType\" equal to \"LINK_PORT_ADDED\".\n* NOTE 4:\tA coordination action has timed out if the VNFM has not been able to read the\n \"Individual coordination action\" resource within a timeout interval after requesting the coordination\n to be started or to be cancelled. The length of the timeout interval is defined by means outside\n the scope of the present document.\n* NOTE 5: The list of rejected coordinations may be garbage collected if the LCM operation occurrence has\n reached a terminal state, i.e. one of \"COMPLETED\", \"FAILED\" and \"ROLLED_BACK\".\n",
+ "description": "This type represents a VNF lifecycle management operation occurrence. Shall be set to the value of the \"id\" attribute in the \"Grant\" representing the associated \"Individual Grant\", if such grant exists. * NOTE 1:\tThis allows the API consumer to obtain the information contained in the latest \"result\"\n notification if it has not received it due to an error or a wrongly configured subscription filter.\n* NOTE 2:\tNot more than one of changedInfo and modificationsTriggeredByVnfPkgChange shall be present. * NOTE 3:\tFor a particular affected VL, there shall be as many \"AffectedVirtualLink\" entries as needed\n for signalling the different types of changes, i.e. one per virtual link and change type.\n For instance, in the case of signalling affected VL instances involving the addition of a\n particular VL instance with links ports, one \"AffectedVirtualLink\" entry signals the addition\n of the VL by using the \"changeType\" attribute of \"AffectedVirtualLink\" structure equal to \"ADDED\",\n and another \"AffectedVirtualLink\" entry signals the addition of VNF link ports of the VL by using the\n \"changeType\" equal to \"LINK_PORT_ADDED\".\n* NOTE 4:\tA coordination action has timed out if the VNFM has not been able to read the\n \"Individual coordination action\" resource within a timeout interval after requesting the coordination\n to be started or to be cancelled. The length of the timeout interval is defined by means outside\n the scope of the present document.\n* NOTE 5: The list of rejected coordinations may be garbage collected if the LCM operation occurrence has\n reached a terminal state, i.e. one of \"COMPLETED\", \"FAILED\" and \"ROLLED_BACK\".\n",
"type": "object",
"oneOf": [
{
@@ -60,7 +60,7 @@
"type": "string"
},
"operation": {
- "description": "The enumeration LcmOpType defines the permitted values to represent VNF lifecycle operation types in VNF lifecycle management operation occurrence resources and VNF lifecycle management operation occurrence notifications. It shall comply with the provisions defined in table 5.5.4.5-1.\nValue | Description ------|------------ INSTANTIATE | Represents the \"Instantiate VNF\" LCM operation. SCALE | Represents the \"Scale VNF\" LCM operation. SCALE_TO_LEVEL | Represents the \"Scale VNF to Level\" LCM operation. CHANGE_FLAVOUR | Represents the \"Change VNF Flavour\" LCM operation. TERMINATE | Represents the \"Terminate VNF\" LCM operation. HEAL | Represents the \"Heal VNF\" LCM operation. OPERATE | Represents the \"Operate VNF\" LCM operation. CHANGE_EXT_CONN | Represents the \"Change external VNF connectivity\" LCM operation. MODIFY_INFO | Represents the \"Modify VNF Information\" LCM operation. CREATE_SNAPSHOT | Represents the \"Create VNF Snapshot\" LCM operation. REVERT_TO_SNAPSHOT | Represents the “Revert-To VNF Snapshot\" LCM operation. CHANGE_VNFPKG | Represents the \"Change current VNF package\" LCM operation.\n",
+ "description": "The enumeration LcmOpType defines the permitted values to represent VNF lifecycle operation types in VNF lifecycle management operation occurrence resources and VNF lifecycle management operation occurrence notifications.\nValue | Description ------|------------ INSTANTIATE | Represents the \"Instantiate VNF\" LCM operation. SCALE | Represents the \"Scale VNF\" LCM operation. SCALE_TO_LEVEL | Represents the \"Scale VNF to Level\" LCM operation. CHANGE_FLAVOUR | Represents the \"Change VNF Flavour\" LCM operation. TERMINATE | Represents the \"Terminate VNF\" LCM operation. HEAL | Represents the \"Heal VNF\" LCM operation. OPERATE | Represents the \"Operate VNF\" LCM operation. CHANGE_EXT_CONN | Represents the \"Change external VNF connectivity\" LCM operation. MODIFY_INFO | Represents the \"Modify VNF Information\" LCM operation. CREATE_SNAPSHOT | Represents the \"Create VNF Snapshot\" LCM operation. REVERT_TO_SNAPSHOT | Represents the ΓÇ£Revert-To VNF Snapshot\" LCM operation. CHANGE_VNFPKG | Represents the \"Change current VNF package\" LCM operation.\n",
"type": "string",
"enum": [
"INSTANTIATE",
@@ -173,7 +173,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",
+ "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",
"properties": {
"vimConnectionId": {
"description": "An identifier with the intention of being globally unique.\n",
@@ -184,11 +184,33 @@
"type": "string"
},
"resourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
"type": "string"
},
"vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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"
}
}
@@ -266,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",
+ "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",
"properties": {
"vimConnectionId": {
"description": "An identifier with the intention of being globally unique.\n",
@@ -277,11 +299,33 @@
"type": "string"
},
"resourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
"type": "string"
},
"vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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"
}
}
@@ -336,7 +380,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",
+ "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",
"properties": {
"vimConnectionId": {
"description": "An identifier with the intention of being globally unique.\n",
@@ -347,11 +391,33 @@
"type": "string"
},
"resourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
"type": "string"
},
"vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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"
}
}
@@ -399,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",
+ "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",
"properties": {
"vimConnectionId": {
"description": "An identifier with the intention of being globally unique.\n",
@@ -410,11 +476,33 @@
"type": "string"
},
"resourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
"type": "string"
},
"vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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"
}
}
@@ -536,7 +624,7 @@
"description": "Information about changed external connectivity, if applicable. See note 1.\n",
"type": "array",
"items": {
- "description": "This type represents information about an external VL. It shall comply with the provisions defined in table 5.5.3.2-1.\nNOTE:\tThis attribute reflects the current configuration information that has resulted from merging into this attribute \n the \"VnfExtCpData\" information which was passed as part of the \"ExtVirtualLinkData\" structure in the input of the \n most recent VNF LCM operation such as \"InstantiateVnfRequest\", \"ChangeExtVnfConnectivityRequest\", \"ChangeVnfFlavourRequest\" \n or \"ChangeCurrentVnfPkgRequest\", or in the Grant response. If applying such change results in an empty list of \n \"currentVnfExtCpData\" structure instances, the affected instance of \"ExtVirtualLinkInfo\" shall be removed from its \n parent data structure.\n",
+ "description": "This type represents information about an external VL.\nNOTE:\tThis attribute reflects the current configuration information that has resulted from merging into this attribute \n the \"VnfExtCpData\" information which was passed as part of the \"ExtVirtualLinkData\" structure in the input of the \n most recent VNF LCM operation such as \"InstantiateVnfRequest\", \"ChangeExtVnfConnectivityRequest\", \"ChangeVnfFlavourRequest\" \n or \"ChangeCurrentVnfPkgRequest\", or in the Grant response. If applying such change results in an empty list of \n \"currentVnfExtCpData\" structure instances, the affected instance of \"ExtVirtualLinkInfo\" shall be removed from its \n parent data structure.\n",
"type": "object",
"required": [
"id",
@@ -553,7 +641,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",
+ "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",
"properties": {
"vimConnectionId": {
"description": "An identifier with the intention of being globally unique.\n",
@@ -564,11 +652,33 @@
"type": "string"
},
"resourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
"type": "string"
},
"vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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"
}
}
@@ -577,7 +687,7 @@
"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. It shall comply with the provisions defined in table 5.5.3.9-1.\nNOTE 1:\tThe use cases UC#4 and UC#5 in clause A.4 of ETSI GS NFV-IFA 007 provide examples for such a configuration. NOTE 2:\tThe value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\" attribute.\n",
+ "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.\nNOTE 1:\tThe use cases UC#4 and UC#5 in clause A.4 of ETSI GS NFV-IFA 007 provide examples for such a configuration. NOTE 2:\tThe value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\" attribute.\n",
"type": "object",
"required": [
"id",
@@ -593,7 +703,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",
+ "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",
"properties": {
"vimConnectionId": {
"description": "An identifier with the intention of being globally unique.\n",
@@ -604,11 +714,33 @@
"type": "string"
},
"resourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
"type": "string"
},
"vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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"
}
}
@@ -622,7 +754,7 @@
"type": "string"
},
"trunkResourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
"type": "string"
}
}
@@ -632,7 +764,7 @@
"description": "Allows the API consumer to read the current CP configuration information for the connection of external CPs to the external virtual link. See note.\n",
"type": "array",
"items": {
- "description": "This type represents configuration information for external CPs created. * NOTE 1: \tIn case this identifier refers to a CPD with trunking enabled, the external CP instances created\n from this CPD will represent ports in a trunk.\n* NOTE 2: \tWithin one VNF instance, all VNFC instances created from a particular VDU have the same external\n connectivity. Thus, given a particular value of the \"cpdId\" attribute, there shall be one\n \"cpConfig\" entry for each VNFC instance that has been or can be created from a VDU which includes\n a CPD identified by the \"cpdId\" attribute. If the cpConfig represents a subport in a trunk,\n all \"cpConfig\" entries in this list shall have the same segmentationId, which means they are\n connected to the same set of external VLs via the trunk.\n* NOTE 3: \tThe map entry value shall be set to \"null\" in order to delete a \"VnfExtCpConfig\" entry identified\n by a particular key value from the map, i.e. for the disconnection of an existing external\n CP instance addressed by cpInstanceId in the deleted map entry from a particular external\n virtual link, and deletion of that instance in case it represents a subport. Deleting the\n last key from the map removes the affected instance of the \"VnfExtCpData\" structure from\n its parent data structure.\n* NOTE 4: If, as defined by the input parameters of a \"ChangeVnfFlavour\", \"ChangeExtVnfConnectivity\" or \n \"ChangeCurrentVnfPkg\" operation or as part of the Grant response for any of these operations, a \n cpConfig map entry identified by a particular map key value is moved into another \"ExtVirtualLinkData\"\n or \"VnfExtCpData\" structure, this particular cpConfig map entry may be used by an external CP instance\n different than the one that has used it before the operation, or by no external CP instance at all.\n Renaming a CPD identifier during the \"changeCurrentVnfPkg\" operation does not count as moving the\n related \"cpConfig\" map entries to a new \"extCpData\" structure.\n",
+ "description": "This type represents configuration information for external CPs created. * NOTE 1: \tIn case this identifier refers to a CPD with trunking enabled, the external CP instances created\n from this CPD will represent ports in a trunk.\n* NOTE 2: \tWithin one VNF instance, all VNFC instances created from a particular VDU have the same external\n connectivity. Thus, given a particular value of the \"cpdId\" attribute, there shall be one\n \"cpConfig\" entry for each VNFC instance that has been or can be created from a VDU which includes\n a CPD identified by the \"cpdId\" attribute. If the cpConfig represents a subport in a trunk,\n all \"cpConfig\" entries in this list shall have the same segmentationId, which means they are\n connected to the same set of external VLs via the trunk.\n* NOTE 3: \tThe map entry value shall be set to \"null\" in order to delete a \"VnfExtCpConfig\" entry identified\n by a particular key value from the map, i.e. for the disconnection of an existing external\n CP instance addressed by cpInstanceId in the deleted map entry from a particular external\n virtual link, and deletion of that instance in case it represents a subport. Deleting the\n last key from the map removes the affected instance of the \"VnfExtCpData\" structure from\n its parent data structure.\n* NOTE 4: If, as defined by the input parameters of a \"ChangeVnfFlavour\", \"ChangeExtVnfConnectivity\" or\n \"ChangeCurrentVnfPkg\" operation, a cpConfig map entry identified by a particular map key value \n is moved into another \"ExtVirtualLinkData\" or \"VnfExtCpData\" structure, this particular cpConfig\n map entry may be used by an external CP instance different than the one that has used it before the\n operation, or by no external CP instance at all. Renaming a CPD identifier during the \"changeCurrentVnfPkg\"\n operation does not count as moving the related \"cpConfig\" map entries to a new \"extCpData\" structure.\n",
"type": "object",
"required": [
"cpdId"
@@ -643,10 +775,10 @@
"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). See notes 2, 3 and 4.\n",
+ "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 network address information per instance of an external connection point. In case a link port is provided, the VNFM shall use that link port when connecting the external CP to the external VL. In a link port is not provided, the VNFM shall create a link port on the external VL, and use that link port to connect the external CP to the external VL. * NOTE: The following conditions apply to the attributes \"linkPortId\" and \"cpProtocolData\":\n 1) Void.\n 2) At least one of the \"linkPortId\" and \"cpProtocolData\" attributes shall be present for an external\n CP instance representing a subport that is to be created, or an external CP instance that is to be\n created by creating the corresponding VNFC or VNF instance during the current or a subsequent LCM\n operation, or for an existing external CP instance that is to be re-configured or added to a\n 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\n a pre created link port, and the VNFM can use means outside the scope of the present document to obtain\n the pre-configured address information for the connection point from the resource representing\n the link port.\n 5) If both \"cpProtocolData\" and \"linkportId\" are provided, the API consumer shall ensure that the\n cpProtocolData can be used with the pre-created link port referenced by \"linkPortId\".\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) 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",
"anyOf": [
{
"required": [
@@ -657,6 +789,11 @@
"required": [
"cpProtocolData"
]
+ },
+ {
+ "required": [
+ "netAttDefResourceId"
+ ]
}
],
"type": "object",
@@ -674,7 +811,7 @@
"type": "boolean"
},
"cpProtocolData": {
- "description": "Parameters for configuring the network protocols on the link port that connects the CP to a VL. See note.\n",
+ "description": "Parameters for configuring the network protocols on the link port that connects the CP to a VL. See notes 1 and 2.\n",
"type": "array",
"items": {
"description": "This type represents network protocol data. * NOTE:\tThis attribute allows to signal the addition of further types of layer and protocol\n in future versions of the present document in a backwards-compatible way. In the current\n version of the present document, only IP over Ethernet is supported.\n",
@@ -684,14 +821,15 @@
],
"properties": {
"layerProtocol": {
- "description": "Identifier of layer(s) and protocol(s). See note.\n",
+ "description": "Identifier of layer(s) and protocol(s). Permitted values:\n - IP_OVER_ETHERNET.\n - IP_FOR_VIRTUAL_CP\nSee note\n",
"type": "string",
"enum": [
- "IP_OVER_ETHERNET"
+ "IP_OVER_ETHERNET",
+ "IP_FOR_VIRTUAL_CP"
]
},
"ipOverEthernet": {
- "description": "This type represents network address data for IP over Ethernet. * NOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. * NOTE 2:\tExactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present. * NOTE 3:\tIf the CP instance represents a subport in a trunk, segmentationId shall be present.\n Otherwise it shall not be present.\n* NOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the actual\n network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header\n of the packets or it may be an identifier used between the application and the NFVI networking\n infrastructure to identify the network sub-interface of the trunk port in question. In the latter\n case the NFVI infrastructure will map this local segmentationId to whatever segmentationId is\n actually used by the NFVI’s transport technology.\n",
+ "description": "This type represents network address data for IP over Ethernet. * NOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. * NOTE 2:\tExactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present. * NOTE 3:\tIf the CP instance represents a subport in a trunk, segmentationId shall be present.\n Otherwise it shall not be present.\n* NOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the actual\n network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header\n of the packets or it may be an identifier used between the application and the NFVI networking\n infrastructure to identify the network sub-interface of the trunk port in question. In the latter\n case the NFVI infrastructure will map this local segmentationId to whatever segmentationId is\n actually used by the NFVI's transport technology.\n",
"type": "object",
"anyOf": [
{
@@ -729,7 +867,7 @@
"format": "MAC"
},
"segmentationType": {
- "description": "Specifies the encapsulation type for the traffics coming in and out of the trunk subport. Permitted values: -\tVLAN: the subport uses VLAN as encapsulation type. -\tINHERIT: the subport gets its segmentation type from the network it’s 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",
+ "description": "Specifies the encapsulation type for the traffics coming in and out of the trunk subport. Permitted values: -\tVLAN: the subport uses VLAN as encapsulation type. -\tINHERIT: the subport gets its segmentation type from the network itΓÇÖs 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",
@@ -791,19 +929,130 @@
}
},
"subnetId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
"type": "string"
}
}
}
}
}
+ },
+ "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",
+ "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"
+ }
+ }
}
}
}
+ },
+ "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 2, 3 and 4.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\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 contains 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": {
+ "required": [
+ "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",
+ "properties": {
+ "vimConnectionId": {
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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 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"
+ }
}
+ },
+ "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 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 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"
+ }
}
}
}
@@ -812,7 +1061,7 @@
}
},
"modificationsTriggeredByVnfPkgChange": {
- "description": "This type represents attribute modifications that were performed on an \"Individual VNF instance\" resource when changing the current VNF package. The attributes that can be included consist of those requested to be modified explicitly in the \"ChangeCurrentVnfPkgRequest\" data structure, and additional attributes of the \"VnfInstance\" data structure that were modified implicitly during the operation. The \"ModificationsTriggeredByVnfPkgChange\" data type shall comply with the provisions defined in table 5.5.3.21-1.\nNOTE 1:\tThis attribute represents the delta (semantics as per IETF RFC 7396, JSON Merge Patch) between the value \n of the attribute at the start of the \"Change current VNF package\" operation and the value of the attribute \n at its completion.\nNOTE 2:\tIf present, this attribute (which depends on the value of the \"vnfdId\" attribute) was modified implicitly \n during the related operation and contains a copy of the value of the related attribute from the VNFD in the \n VNF Package identified by the \"vnfdId\" attribute.\n",
+ "description": "This type represents attribute modifications that were performed on an \"Individual VNF instance\" resource when changing the current VNF package. The attributes that can be included consist of those requested to be modified explicitly in the \"ChangeCurrentVnfPkgRequest\" data structure, and additional attributes of the \"VnfInstance\" data structure that were modified implicitly during the operation.\nNOTE 1:\tThis attribute represents the delta (semantics as per IETF RFC 7396, JSON Merge Patch) between the value \n of the attribute at the start of the \"Change current VNF package\" operation and the value of the attribute \n at its completion.\nNOTE 2:\tIf present, this attribute (which depends on the value of the \"vnfdId\" attribute) was modified implicitly \n during the related operation and contains a copy of the value of the related attribute from the VNFD in the \n VNF Package identified by the \"vnfdId\" attribute.\n",
"type": "object",
"properties": {
"vnfConfigurableProperties": {
@@ -846,6 +1095,39 @@
"vnfdVersion": {
"description": "A version.\n",
"type": "string"
+ },
+ "vimConnectionInfo": {
+ "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-relate dparameters 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",
+ "type": "object",
+ "required": [
+ "vimType"
+ ],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vimType": {
+ "description": "Discriminator for the different types of the VIM information. The value of this attribute determines the structure of the \"interfaceInfo\" and \"accessInfo\" attributes, based on the type of the VIM., CISM, CIR or MCIOP repository. The set of permitted values is expected to change over time as new types or versions of VIMs become available. The ETSI NFV registry of VIM-related information [i.3] provides access to information about VimConnectionInfo definitions for various VIM, CISM, CIR or MCIOP repository types. The structure of the registry is defined in annex C.\n",
+ "type": "string"
+ },
+ "interfaceInfo": {
+ "description": "This 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"
+ },
+ "accessInfo": {
+ "description": "This 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"
+ },
+ "extra": {
+ "description": "This 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/VNFLifecycleManagement-API/schemas/vnfLcmOpOccs.schema.json b/SOL002/VNFLifecycleManagement-API/schemas/vnfLcmOpOccs.schema.json
index 841d6ae32fff889ccb913e4d4fe6406954f544e5..f573bc5d1195abc46e13e4850500a29d3bd51903 100644
--- a/SOL002/VNFLifecycleManagement-API/schemas/vnfLcmOpOccs.schema.json
+++ b/SOL002/VNFLifecycleManagement-API/schemas/vnfLcmOpOccs.schema.json
@@ -1,1067 +1,1349 @@
{
- "type": "array",
- "items": {
- "description": "This type represents a VNF lifecycle management operation occurrence. Shall be set to the value of the \"id\" attribute in the \"Grant\" representing the associated \"Individual Grant\", if such grant exists. * NOTE 1:\tThis allows the API consumer to obtain the information contained in the latest \"result\"\n notification if it has not received it due to an error or a wrongly configured subscription filter.\n* NOTE 2:\tNot more than one of changedInfo and modificationsTriggeredByVnfPkgChange shall be present. * NOTE 3:\tFor a particular affected VL, there shall be as many \"AffectedVirtualLink\" entries as needed\n for signalling the different types of changes, i.e. one per virtual link and change type.\n For instance, in the case of signaling affected VL instances involving the addition of a\n particular VL instance with links ports, one \"AffectedVirtualLink\" entry signals the addition\n of the VL by using the \"changeType\" attribute of \"AffectedVirtualLink\" structure equal to \"ADDED\",\n and another \"AffectedVirtualLink\" entry signals the addition of VNF link ports of the VL by using the\n \"changeType\" equal to \"LINK_PORT_ADDED\".\n* NOTE 4:\tA coordination action has timed out if the VNFM has not been able to read the\n \"Individual coordination action\" resource within a timeout interval after requesting the coordination\n to be started or to be cancelled. The length of the timeout interval is defined by means outside\n the scope of the present document.\n* NOTE 5: The list of rejected coordinations may be garbage collected if the LCM operation occurrence has\n reached a terminal state, i.e. one of \"COMPLETED\", \"FAILED\" and \"ROLLED_BACK\".\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents a VNF lifecycle management operation occurrence. Shall be set to the value of the \"id\" attribute in the \"Grant\" representing the associated \"Individual Grant\", if such grant exists. * NOTE 1:\tThis allows the API consumer to obtain the information contained in the latest \"result\"\n notification if it has not received it due to an error or a wrongly configured subscription filter.\n* NOTE 2:\tNot more than one of changedInfo and modificationsTriggeredByVnfPkgChange shall be present. * NOTE 3:\tFor a particular affected VL, there shall be as many \"AffectedVirtualLink\" entries as needed\n for signalling the different types of changes, i.e. one per virtual link and change type.\n For instance, in the case of signalling affected VL instances involving the addition of a\n particular VL instance with links ports, one \"AffectedVirtualLink\" entry signals the addition\n of the VL by using the \"changeType\" attribute of \"AffectedVirtualLink\" structure equal to \"ADDED\",\n and another \"AffectedVirtualLink\" entry signals the addition of VNF link ports of the VL by using the\n \"changeType\" equal to \"LINK_PORT_ADDED\".\n* NOTE 4:\tA coordination action has timed out if the VNFM has not been able to read the\n \"Individual coordination action\" resource within a timeout interval after requesting the coordination\n to be started or to be cancelled. The length of the timeout interval is defined by means outside\n the scope of the present document.\n* NOTE 5: The list of rejected coordinations may be garbage collected if the LCM operation occurrence has\n reached a terminal state, i.e. one of \"COMPLETED\", \"FAILED\" and \"ROLLED_BACK\".\n",
"type": "object",
"oneOf": [
- {
- "required": [
- "changedInfo"
- ]
- },
- {
- "required": [
- "modificationsTriggeredByVnfPkgChange"
- ]
- }
+ {
+ "required": [
+ "changedInfo"
+ ]
+ },
+ {
+ "required": [
+ "modificationsTriggeredByVnfPkgChange"
+ ]
+ }
],
"required": [
- "id",
- "operationState",
- "stateEnteredTime",
- "startTime",
- "vnfInstanceId",
- "operation",
- "isAutomaticInvocation",
- "isCancelPending"
+ "id",
+ "operationState",
+ "stateEnteredTime",
+ "startTime",
+ "vnfInstanceId",
+ "operation",
+ "isAutomaticInvocation",
+ "isCancelPending"
],
"properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "operationState": {
- "description": "STARTING: The LCM operation is starting. PROCESSING: The LCM operation is currently in execution. COMPLETED: The LCM operation has been completed successfully. FAILED_TEMP: The LCM operation has failed and execution has stopped, but the execution of the operation is not considered to be closed. FAILED: The LCM operation has failed and it cannot be retried or rolled back, as it is determined that such action won't succeed. ROLLING_BACK: The LCM operation is currently being rolled back. ROLLED_BACK: The LCM operation has been successfully rolled back, i.e. The state of the VNF prior to the original operation invocation has been restored as closely as possible.\n",
- "type": "string",
- "enum": [
- "STARTING",
- "PROCESSING",
- "COMPLETED",
- "FAILED_TEMP",
- "FAILED",
- "ROLLING_BACK",
- "ROLLED_BACK"
- ]
- },
- "stateEnteredTime": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "startTime": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "vnfInstanceId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "grantId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "operation": {
- "description": "The enumeration LcmOpType defines the permitted values to represent VNF lifecycle operation types in VNF lifecycle management operation occurrence resources and VNF lifecycle management operation occurrence notifications. It shall comply with the provisions defined in table 5.5.4.5-1.\nValue | Description ------|------------ INSTANTIATE | Represents the \"Instantiate VNF\" LCM operation. SCALE | Represents the \"Scale VNF\" LCM operation. SCALE_TO_LEVEL | Represents the \"Scale VNF to Level\" LCM operation. CHANGE_FLAVOUR | Represents the \"Change VNF Flavour\" LCM operation. TERMINATE | Represents the \"Terminate VNF\" LCM operation. HEAL | Represents the \"Heal VNF\" LCM operation. OPERATE | Represents the \"Operate VNF\" LCM operation. CHANGE_EXT_CONN | Represents the \"Change external VNF connectivity\" LCM operation. MODIFY_INFO | Represents the \"Modify VNF Information\" LCM operation. CREATE_SNAPSHOT | Represents the \"Create VNF Snapshot\" LCM operation. REVERT_TO_SNAPSHOT | Represents the “Revert-To VNF Snapshot\" LCM operation. CHANGE_VNFPKG | Represents the \"Change current VNF package\" LCM operation.\n",
- "type": "string",
- "enum": [
- "INSTANTIATE",
- "SCALE",
- "SCALE_TO_LEVEL",
- "CHANGE_FLAVOUR",
- "TERMINATE",
- "HEAL",
- "OPERATE",
- "CHANGE_EXT_CONN",
- "MODIFY_INFO",
- "CREATE_SNAPSHOT",
- "REVERT_TO_SNAPSHOT",
- "CHANGE_VNFPKG"
- ]
- },
- "isAutomaticInvocation": {
- "description": "The Boolean is a data type having two values (true and false).\n",
- "type": "boolean"
- },
- "operationParams": {
- "description": "Input parameters of the LCM operation. This attribute shall be formatted according to the request data type of the related LCM operation. In addition, the provisions in clause 5.7 shall apply. The following mapping between operationType and the data type of this attribute shall apply: * INSTANTIATE: InstantiateVnfRequest * SCALE: ScaleVnfRequest * SCALE_TO_LEVEL: ScaleVnfToLevelRequest * CHANGE_FLAVOUR: ChangeVnfFlavourRequest * OPERATE: OperateVnfRequest * HEAL: HealVnfRequest * CHANGE_EXT_CONN: ChangeExtVnfConnectivityRequest * TERMINATE: TerminateVnfRequest * MODIFY_INFO: VnfInfoModifications * CREATE_SNAPSHOT: CreateVnfSnapshotRequest * REVERT_TO_SNAPSHOT: RevertToVnfSnapshotRequest * CHANGE_VNFPKG: ChangeCurrentVnfPkgRequest\n",
- "type": "object"
- },
- "isCancelPending": {
- "description": "The Boolean is a data type having two values (true and false).\n",
- "type": "boolean"
- },
- "cancelMode": {
- "description": "Cancellation mode. GRACEFUL: If the VNF LCM operation occurrence is in \"PROCESSING\" or \"ROLLING_BACK\" state, the VNFM shall not start any new resource management operation and shall wait for the ongoing resource management operations in the underlying system, typically the VIM, to finish execution or to time out. After that, the VNFM shall put the operation occurrence into the FAILED_TEMP state. If the VNF LCM operation occurrence is in \"STARTING\" state, the VNFM shall not start any resource management operation and shall wait for the granting request to finish execution or time out. After that, the VNFM shall put the operation occurrence into the ROLLED_BACK state. FORCEFUL: If the VNF LCM operation occurrence is in \"PROCESSING\" or \"ROLLING_BACK\" state, the VNFM shall not start any new resource management operation, shall cancel the ongoing resource management operations in the underlying system, typically the VIM, and shall wait for the cancellation to finish or to time out. After that, the VNFM shall put the operation occurrence into the FAILED_TEMP state. If the VNF LCM operation occurrence is in \"STARTING\" state, the VNFM shall not start any resource management operation and put the operation occurrence into the ROLLED_BACK state.\n",
- "type": "string",
- "enum": [
- "GRACEFUL",
- "FORCEFUL"
- ]
- },
- "error": {
- "description": "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 is reproduced inthis structure. Compared to the general framework defined in IETF RFC 7807, 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 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.\n",
- "type": "object",
- "required": [
- "status",
- "detail"
- ],
- "properties": {
- "type": {
- "description": "A URI reference according to IETF RFC 3986 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",
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "operationState": {
+ "description": "STARTING: The LCM operation is starting. PROCESSING: The LCM operation is currently in execution. COMPLETED: The LCM operation has been completed successfully. FAILED_TEMP: The LCM operation has failed and execution has stopped, but the execution of the operation is not considered to be closed. FAILED: The LCM operation has failed and it cannot be retried or rolled back, as it is determined that such action won't succeed. ROLLING_BACK: The LCM operation is currently being rolled back. ROLLED_BACK: The LCM operation has been successfully rolled back, i.e. The state of the VNF prior to the original operation invocation has been restored as closely as possible.\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",
+ "enum": [
+ "STARTING",
+ "PROCESSING",
+ "COMPLETED",
+ "FAILED_TEMP",
+ "FAILED",
+ "ROLLING_BACK",
+ "ROLLED_BACK"
+ ]
+ },
+ "stateEnteredTime": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "startTime": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "vnfInstanceId": {
+ "description": "An identifier with the intention of being globally unique.\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",
+ },
+ "grantId": {
+ "description": "An identifier with the intention of being globally unique.\n",
"type": "string"
- },
- "instance": {
- "description": "A URI reference that identifies the specific occurrence of the problem. It may yield further information if dereferenced.\n",
+ },
+ "operation": {
+ "description": "The enumeration LcmOpType defines the permitted values to represent VNF lifecycle operation types in VNF lifecycle management operation occurrence resources and VNF lifecycle management operation occurrence notifications.\nValue | Description ------|------------ INSTANTIATE | Represents the \"Instantiate VNF\" LCM operation. SCALE | Represents the \"Scale VNF\" LCM operation. SCALE_TO_LEVEL | Represents the \"Scale VNF to Level\" LCM operation. CHANGE_FLAVOUR | Represents the \"Change VNF Flavour\" LCM operation. TERMINATE | Represents the \"Terminate VNF\" LCM operation. HEAL | Represents the \"Heal VNF\" LCM operation. OPERATE | Represents the \"Operate VNF\" LCM operation. CHANGE_EXT_CONN | Represents the \"Change external VNF connectivity\" LCM operation. MODIFY_INFO | Represents the \"Modify VNF Information\" LCM operation. CREATE_SNAPSHOT | Represents the \"Create VNF Snapshot\" LCM operation. REVERT_TO_SNAPSHOT | Represents the ΓÇ£Revert-To VNF Snapshot\" LCM operation. CHANGE_VNFPKG | Represents the \"Change current VNF package\" LCM operation.\n",
"type": "string",
- "format": "URI"
- }
- }
- },
- "resourceChanges": {
- "description": "This attribute contains information about the cumulative changes to virtualised resources that were performed so far by the LCM operation since its start, if applicable.\n",
- "type": "object",
- "properties": {
- "affectedVnfcs": {
- "description": "Information about VNFC 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 VNFCs.\n",
- "type": "object",
- "required": [
- "id",
- "vduId",
- "changeType",
- "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"
- },
- "vduId": {
- "description": "An identifier that is unique within a VNF descriptor.\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: * ADDED * REMOVED * MODIFIED * TEMPORARY For a temporary resource, an AffectedVnfc structure exists as long as the temporary resource exists.\n",
- "type": "string",
- "enum": [
- "ADDED",
- "REMOVED",
- "MODIFIED",
- "TEMPORARY"
- ]
- },
- "computeResource": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\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 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"
+ "enum": [
+ "INSTANTIATE",
+ "SCALE",
+ "SCALE_TO_LEVEL",
+ "CHANGE_FLAVOUR",
+ "TERMINATE",
+ "HEAL",
+ "OPERATE",
+ "CHANGE_EXT_CONN",
+ "MODIFY_INFO",
+ "CREATE_SNAPSHOT",
+ "REVERT_TO_SNAPSHOT",
+ "CHANGE_VNFPKG"
+ ]
+ },
+ "isAutomaticInvocation": {
+ "description": "The Boolean is a data type having two values (true and false).\n",
+ "type": "boolean"
+ },
+ "operationParams": {
+ "description": "Input parameters of the LCM operation. This attribute shall be formatted according to the request data type of the related LCM operation. In addition, the provisions in clause 5.7 shall apply. The following mapping between operationType and the data type of this attribute shall apply: * INSTANTIATE: InstantiateVnfRequest * SCALE: ScaleVnfRequest * SCALE_TO_LEVEL: ScaleVnfToLevelRequest * CHANGE_FLAVOUR: ChangeVnfFlavourRequest * OPERATE: OperateVnfRequest * HEAL: HealVnfRequest * CHANGE_EXT_CONN: ChangeExtVnfConnectivityRequest * TERMINATE: TerminateVnfRequest * MODIFY_INFO: VnfInfoModifications * CREATE_SNAPSHOT: CreateVnfSnapshotRequest * REVERT_TO_SNAPSHOT: RevertToVnfSnapshotRequest * CHANGE_VNFPKG: ChangeCurrentVnfPkgRequest\n",
+ "type": "object"
+ },
+ "isCancelPending": {
+ "description": "The Boolean is a data type having two values (true and false).\n",
+ "type": "boolean"
+ },
+ "cancelMode": {
+ "description": "Cancellation mode. GRACEFUL: If the VNF LCM operation occurrence is in \"PROCESSING\" or \"ROLLING_BACK\" state, the VNFM shall not start any new resource management operation and shall wait for the ongoing resource management operations in the underlying system, typically the VIM, to finish execution or to time out. After that, the VNFM shall put the operation occurrence into the FAILED_TEMP state. If the VNF LCM operation occurrence is in \"STARTING\" state, the VNFM shall not start any resource management operation and shall wait for the granting request to finish execution or time out. After that, the VNFM shall put the operation occurrence into the ROLLED_BACK state. FORCEFUL: If the VNF LCM operation occurrence is in \"PROCESSING\" or \"ROLLING_BACK\" state, the VNFM shall not start any new resource management operation, shall cancel the ongoing resource management operations in the underlying system, typically the VIM, and shall wait for the cancellation to finish or to time out. After that, the VNFM shall put the operation occurrence into the FAILED_TEMP state. If the VNF LCM operation occurrence is in \"STARTING\" state, the VNFM shall not start any resource management operation and put the operation occurrence into the ROLLED_BACK state.\n",
+ "type": "string",
+ "enum": [
+ "GRACEFUL",
+ "FORCEFUL"
+ ]
+ },
+ "error": {
+ "description": "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 is reproduced inthis structure. Compared to the general framework defined in IETF RFC 7807, 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 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.\n",
+ "type": "object",
+ "required": [
+ "status",
+ "detail"
+ ],
+ "properties": {
+ "type": {
+ "description": "A URI reference according to IETF RFC 3986 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"
},
- "affectedVnfcCpIds": {
- "description": "Identifiers of CP(s) of the VNFC instance that were affected by the change. Shall be present for those affected CPs of the VNFC instance that are associated to an external CP of the VNF instance. May be present for further affected CPs of the VNFC instance.\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",
+ "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"
- }
},
- "addedStorageResourceIds": {
- "description": "References to VirtualStorage resources that have been added. Each value refers to a VirtualStorageResourceInfo item in the VnfInstance that was added to the VNFC. It shall be provided if at least one storage resource was added to the VNFC.\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"
- }
+ "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"
},
- "removedStorageResourceIds": {
- "description": "References to VirtualStorage resources that have been removed. The value contains the identifier of a VirtualStorageResourceInfo item that has been removed from the VNFC, and might no longer exist in the VnfInstance. It shall be provided if at least one storage resource was removed from the VNFC.\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",
+ "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"
}
- }
}
- },
- "affectedVirtualLinks": {
- "description": "Information about VL instances that were affected during the lifecycle operation. See note 1 and note 3.\n",
- "type": "array",
- "items": {
- "description": "This type provides information about added, deleted, modified and temporary VLs, and added or removed VNF link ports.\nNOTE:\tWhen signalling the addition (LINK_PORT_ADDED) or removal (LINK_PORT_REMOVED) of VNF link ports, \n the \"networkResource\" attribute refers to the affected virtual link instance, not the link port \n instance. The resource handles of the affected VNF link ports can be found by dereferencing the \n identifiers in the \"vnfLinkPortIds\" attribute.\n",
- "type": "object",
- "required": [
- "id",
- "vnfVirtualLinkDescId",
- "changeType",
- "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"
- },
- "vnfVirtualLinkDescId": {
- "description": "An identifier that is unique within a VNF descriptor.\n",
- "type": "string"
+ },
+ "resourceChanges": {
+ "description": "This attribute contains information about the cumulative changes to virtualised resources that were performed so far by the LCM operation since its start, if applicable.\n",
+ "type": "object",
+ "properties": {
+ "affectedVnfcs": {
+ "description": "Information about VNFC 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 VNFCs.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "vduId",
+ "changeType",
+ "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"
+ },
+ "vduId": {
+ "description": "An identifier that is unique within a VNF descriptor.\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: * ADDED * REMOVED * MODIFIED * TEMPORARY For a temporary resource, an AffectedVnfc structure exists as long as the temporary resource exists.\n",
+ "type": "string",
+ "enum": [
+ "ADDED",
+ "REMOVED",
+ "MODIFIED",
+ "TEMPORARY"
+ ]
+ },
+ "computeResource": {
+ "required": [
+ "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",
+ "properties": {
+ "vimConnectionId": {
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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"
+ }
+ }
+ },
+ "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 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"
+ },
+ "affectedVnfcCpIds": {
+ "description": "Identifiers of CP(s) of the VNFC instance that were affected by the change. Shall be present for those affected CPs of the VNFC instance that are associated to an external CP of the VNF instance. May be present for further affected CPs of the VNFC instance.\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"
+ }
+ },
+ "addedStorageResourceIds": {
+ "description": "References to VirtualStorage resources that have been added. Each value refers to a VirtualStorageResourceInfo item in the VnfInstance that was added to the VNFC. It shall be provided if at least one storage resource was added to the VNFC.\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"
+ }
+ },
+ "removedStorageResourceIds": {
+ "description": "References to VirtualStorage resources that have been removed. The value contains the identifier of a VirtualStorageResourceInfo item that has been removed from the VNFC, and might no longer exist in the VnfInstance. It shall be provided if at least one storage resource was removed from the VNFC.\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"
+ }
+ }
+ }
+ }
},
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
+ "affectedVirtualLinks": {
+ "description": "Information about VL instances that were affected during the lifecycle operation. See note 1 and note 3.\n",
+ "type": "array",
+ "items": {
+ "description": "This type provides information about added, deleted, modified and temporary VLs, and added or removed VNF link ports.\nNOTE:\tWhen signalling the addition (LINK_PORT_ADDED) or removal (LINK_PORT_REMOVED) of VNF link ports, \n the \"networkResource\" attribute refers to the affected virtual link instance, not the link port \n instance. The resource handles of the affected VNF link ports can be found by dereferencing the \n identifiers in the \"vnfLinkPortIds\" attribute.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "vnfVirtualLinkDescId",
+ "changeType",
+ "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"
+ },
+ "vnfVirtualLinkDescId": {
+ "description": "An identifier that is unique within a VNF descriptor.\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: * ADDED * REMOVED * MODIFIED * TEMPORARY * LINK_PORT_ADDED * LINK_PORT_REMOVED For a temporary resource, an AffectedVirtualLink structure exists as long as the temporary resource exists. When signalling the addition (LINK_PORT_ADDED) or removal (LINK_PORT_REMOVED) of VNF link ports, the \"networkResource\" attribute refers to the affected virtual link instance, not the link port instance. The resource handles of the affected VNF link ports can be found by dereferencing the identifiers in the \"vnfLinkPortIds\" attribute.\n",
+ "type": "string",
+ "enum": [
+ "ADDED",
+ "REMOVED",
+ "MODIFIED",
+ "TEMPORARY",
+ "LINK_PORT_ADDED",
+ "LINK_PORT_REMOVED"
+ ]
+ },
+ "networkResource": {
+ "required": [
+ "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",
+ "properties": {
+ "vimConnectionId": {
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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"
+ }
+ }
+ },
+ "vnfLinkPortIds": {
+ "description": "Identifiers of the link ports of the affected VL related to the change. Each identifier references a \"VnfLinkPortInfo\" structure.\nShall be set when changeType is equal to \"LINK_PORT_ADDED\" or \"LINK_PORT_REMOVED\", and the related \"VnfLinkPortInfo\" structures are present (case \"added\") or have been present (case \"removed\") in the \"VnfVirtualLinkResourceInfo\" or \"ExtManagedVirtualLinkInfo\" structures that are represented by the \"vnfVirtualLinkResourceInfo\" or \"extManagedVirtualLinkInfo\" attribute in the \"VnfInstance\" structure. See note.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier that is unique within a VNF descriptor.\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 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"
+ }
+ }
+ }
},
- "changeType": {
- "description": "Signals the type of change. Permitted values: * ADDED * REMOVED * MODIFIED * TEMPORARY * LINK_PORT_ADDED * LINK_PORT_REMOVED For a temporary resource, an AffectedVirtualLink structure exists as long as the temporary resource exists. When signalling the addition (LINK_PORT_ADDED) or removal (LINK_PORT_REMOVED) of VNF link ports, the \"networkResource\" attribute refers to the affected virtual link instance, not the link port instance. The resource handles of the affected VNF link ports can be found by dereferencing the identifiers in the \"vnfLinkPortIds\" attribute.\n",
- "type": "string",
- "enum": [
- "ADDED",
- "REMOVED",
- "MODIFIED",
- "TEMPORARY",
- "LINK_PORT_ADDED",
- "LINK_PORT_REMOVED"
- ]
+ "affectedExtLinkPorts": {
+ "description": "Information about external VNF link ports that were affected during the lifecycle operation. See note 1.\n",
+ "type": "array",
+ "items": {
+ "description": "This type provides information about added and deleted external link ports (link ports attached to external virtual links).\n",
+ "type": "object",
+ "required": [
+ "id",
+ "changeType",
+ "extCpInstanceId",
+ "resourceHandle"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "changeType": {
+ "description": "Signals the type of change. Permitted values: -\tADDED - MODIFIED -\tREMOVED\n",
+ "type": "string",
+ "enum": [
+ "ADDED",
+ "MODIFIED",
+ "REMOVED"
+ ]
+ },
+ "extCpInstanceId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "resourceHandle": {
+ "required": [
+ "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",
+ "properties": {
+ "vimConnectionId": {
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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"
+ }
+ }
+ }
+ }
+ }
},
- "networkResource": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
- "type": "string"
+ "affectedVirtualStorages": {
+ "description": "Information about virtualised storage 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 virtual storage resources.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "virtualStorageDescId",
+ "changeType",
+ "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": "An identifier that is unique within a VNF descriptor.\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: * ADDED * REMOVED * MODIFIED * TEMPORARY For a temporary resource, an AffectedVirtualStorage structure exists as long as the temporary resource exists.\n",
+ "type": "string",
+ "enum": [
+ "ADDED",
+ "REMOVED",
+ "MODIFIED",
+ "TEMPORARY"
+ ]
+ },
+ "storageResource": {
+ "required": [
+ "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",
+ "properties": {
+ "vimConnectionId": {
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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"
+ }
+ }
+ },
+ "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 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"
+ }
+ }
}
- }
+ }
+ }
+ },
+ "changedInfo": {
+ "description": "This type represents attribute modifications that were performed on an \"Individual VNF instance\" resource. The attributes that can be included consist of those requested to be modified explicitly in the \"VnfInfoModificationRequest\" data structure, and additional attributes of the \"VnfInstance\" data structure that were modified implicitly e.g. when modifying the referenced VNF package. * NOTE:\tIf present, this attribute (which depends on the value of the \"vnfdId\" attribute)\n was modified implicitly following a request to modify the \"vnfdId\" attribute, by\n copying the value of this attribute from the VNFD in the VNF Package identified\n by the \"vnfdId\" attribute.\n",
+ "type": "object",
+ "properties": {
+ "vnfInstanceName": {
+ "description": "If present, this attribute signals modifications of the \"vnfInstanceName\" attribute in \"VnfInstance\" as defined in clause 5.5.2.12..\n",
+ "type": "string"
},
- "vnfLinkPortIds": {
- "description": "Identifiers of the link ports of the affected VL related to the change. Each identifier references a \"VnfLinkPortInfo\" structure.\nShall be set when changeType is equal to \"LINK_PORT_ADDED\" or \"LINK_PORT_REMOVED\", and the related \"VnfLinkPortInfo\" structures are present (case \"added\") or have been present (case \"removed\") in the \"VnfVirtualLinkResourceInfo\" or \"ExtManagedVirtualLinkInfo\" structures that are represented by the \"vnfVirtualLinkResourceInfo\" or \"extManagedVirtualLinkInfo\" attribute in the \"VnfInstance\" structure. See note.\n",
- "type": "array",
- "items": {
- "description": "An identifier that is unique within a VNF descriptor.\n",
+ "vnfInstanceDescription": {
+ "description": "If present, this attribute signals modifications of the \"vnfInstanceDescription\" attribute in \"VnfInstance\", as defined in clause 5.5.2.12..\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 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"
},
"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 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"
- }
- }
- }
- },
- "affectedExtLinkPorts": {
- "description": "Information about external VNF link ports that were affected during the lifecycle operation. See note 1.\n",
- "type": "array",
- "items": {
- "description": "This type provides information about added and deleted external link ports (link ports attached to external virtual links).\n",
- "type": "object",
- "required": [
- "id",
- "changeType",
- "extCpInstanceId",
- "resourceHandle"
- ],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
+ "description": "This 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"
},
- "changeType": {
- "description": "Signals the type of change. Permitted values: -\tADDED - MODIFIED -\tREMOVED\n",
- "type": "string",
- "enum": [
- "ADDED",
- "MODIFIED",
- "REMOVED"
- ]
+ "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 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"
},
- "extCpInstanceId": {
- "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"
},
- "resourceHandle": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
- "type": "string"
- }
- }
- }
- }
- }
- },
- "affectedVirtualStorages": {
- "description": "Information about virtualised storage 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 virtual storage resources.\n",
- "type": "object",
- "required": [
- "id",
- "virtualStorageDescId",
- "changeType",
- "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"
+ "vnfProvider": {
+ "description": "If present, this attribute signals modifications of the \"vnfProvider\" attribute in \"VnfInstance\". See note.\n",
+ "type": "string"
},
- "virtualStorageDescId": {
- "description": "An identifier that is unique within a VNF descriptor.\n",
- "type": "string"
+ "vnfProductName": {
+ "description": "If present, this attribute signals modifications of the \"vnfProductName\" attribute in \"VnfInstance\". See note.\n",
+ "type": "string"
},
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
+ "vnfSoftwareVersion": {
+ "description": "A version.\n",
+ "type": "string"
},
- "changeType": {
- "description": "Signals the type of change. Permitted values: * ADDED * REMOVED * MODIFIED * TEMPORARY For a temporary resource, an AffectedVirtualStorage structure exists as long as the temporary resource exists.\n",
- "type": "string",
- "enum": [
- "ADDED",
- "REMOVED",
- "MODIFIED",
- "TEMPORARY"
- ]
+ "vnfdVersion": {
+ "description": "A version.\n",
+ "type": "string"
},
- "storageResource": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
- "type": "string"
+ "vnfcInfoModifications": {
+ "description": "If present, this attribute signals modifications of certain entries in the \"vnfcInfo\" attribute array in the \"instantiatedVnfInfo\" attribute of \"VnfInstance\", as defined in clause 5.5.2.12.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents modifications of an entry in an array of \"VnfcInfo\" objects. * NOTE:\tThe attribute \"id\" in this data type represents the same identifier as the attribute\n \"vnfcInstanceId\" in other related data types in the present document. For reasons of backward\n compatibility, this misalignment is not corrected.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "vnfcConfigurableProperties"
+ ],
+ "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"
+ },
+ "vnfcConfigurableProperties": {
+ "description": "This 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"
+ }
+ }
}
- }
- },
- "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 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"
}
- }
}
- }
- }
- },
- "changedInfo": {
- "description": "This type represents attribute modifications that were performed on an \"Individual VNF instance\" resource. The attributes that can be included consist of those requested to be modified explicitly in the \"VnfInfoModificationRequest\" data structure, and additional attributes of the \"VnfInstance\" data structure that were modified implicitly e.g. when modifying the referenced VNF package. * NOTE:\tIf present, this attribute (which depends on the value of the \"vnfdId\" attribute)\n was modified implicitly following a request to modify the \"vnfdId\" attribute, by\n copying the value of this attribute from the VNFD in the VNF Package identified\n by the \"vnfdId\" attribute.\n",
- "type": "object",
- "properties": {
- "vnfInstanceName": {
- "description": "If present, this attribute signals modifications of the \"vnfInstanceName\" attribute in \"VnfInstance\" as defined in clause 5.5.2.12..\n",
- "type": "string"
- },
- "vnfInstanceDescription": {
- "description": "If present, this attribute signals modifications of the \"vnfInstanceDescription\" attribute in \"VnfInstance\", as defined in clause 5.5.2.12..\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 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"
- },
- "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 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"
- },
- "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 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"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfProvider": {
- "description": "If present, this attribute signals modifications of the \"vnfProvider\" attribute in \"VnfInstance\". See note.\n",
- "type": "string"
- },
- "vnfProductName": {
- "description": "If present, this attribute signals modifications of the \"vnfProductName\" attribute in \"VnfInstance\". See note.\n",
- "type": "string"
- },
- "vnfSoftwareVersion": {
- "description": "A version.\n",
- "type": "string"
- },
- "vnfdVersion": {
- "description": "A version.\n",
- "type": "string"
- },
- "vnfcInfoModifications": {
- "description": "If present, this attribute signals modifications of certain entries in the \"vnfcInfo\" attribute array in the \"instantiatedVnfInfo\" attribute of \"VnfInstance\", as defined in clause 5.5.2.12.\n",
+ },
+ "affectedVipCps": {
+ "description": "Information about virtual IP CP instances that were affected during the execution of the lifecycle management operation.\n",
"type": "array",
"items": {
- "description": "This type represents modifications of an entry in an array of \"VnfcInfo\" objects. * NOTE:\tThe attribute \"id\" in this data type represents the same identifier as the attribute\n \"vnfcInstanceId\" in other related data types in the present document. For reasons of backward\n compatibility, this misalignment is not corrected.\n",
- "type": "object",
- "required": [
- "id",
- "vnfcConfigurableProperties"
- ],
- "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"
- },
- "vnfcConfigurableProperties": {
- "description": "This 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"
- }
- }
- }
- }
- }
- },
- "affectedVipCps": {
- "description": "Information about virtual IP CP instances that were affected during the execution of the lifecycle management operation.\n",
- "type": "array",
- "items": {
- "description": "This type provides information about added, deleted and modified virtual IP CP instances.\n",
- "type": "object",
- "required": [
- "cpInstanceId",
- "cpdId",
- "changeType"
- ],
- "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": "An identifier that is unique within a VNF descriptor.\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: -\tADDED -\tREMOVED -\tMODIFIED\n",
- "type": "string",
- "enum": [
- "ADDED",
- "REMOVED",
- "MODIFIED"
- ]
- }
- }
- }
- },
- "changedExtConnectivity": {
- "description": "Information about changed external connectivity, if applicable. See note 1.\n",
- "type": "array",
- "items": {
- "description": "This type represents information about an external VL. It shall comply with the provisions defined in table 5.5.3.2-1.\nNOTE:\tThis attribute reflects the current configuration information that has resulted from merging into this attribute \n the \"VnfExtCpData\" information which was passed as part of the \"ExtVirtualLinkData\" structure in the input of the \n most recent VNF LCM operation such as \"InstantiateVnfRequest\", \"ChangeExtVnfConnectivityRequest\", \"ChangeVnfFlavourRequest\" \n or \"ChangeCurrentVnfPkgRequest\", or in the Grant response. If applying such change results in an empty list of \n \"currentVnfExtCpData\" structure instances, the affected instance of \"ExtVirtualLinkInfo\" shall be removed from its \n parent data structure.\n",
- "type": "object",
- "required": [
- "id",
- "resourceHandle",
- "currentVnfExtCpData"
- ],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceHandle": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\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. It shall comply with the provisions defined in table 5.5.3.9-1.\nNOTE 1:\tThe use cases UC#4 and UC#5 in clause A.4 of ETSI GS NFV-IFA 007 provide examples for such a configuration. NOTE 2:\tThe value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\" attribute.\n",
+ "description": "This type provides information about added, deleted and modified virtual IP CP instances.\n",
"type": "object",
"required": [
- "id",
- "resourceHandle"
+ "cpInstanceId",
+ "cpdId",
+ "changeType"
],
"properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceHandle": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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",
+ "cpInstanceId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
"type": "string"
- },
- "resourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ },
+ "cpdId": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
"type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
"type": "string"
- }
+ },
+ "changeType": {
+ "description": "Signals the type of change. Permitted values: -\tADDED -\tREMOVED -\tMODIFIED\n",
+ "type": "string",
+ "enum": [
+ "ADDED",
+ "REMOVED",
+ "MODIFIED"
+ ]
}
- },
- "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.\n",
- "type": "string"
- }
}
- }
- },
- "currentVnfExtCpData": {
- "description": "Allows the API consumer to read the current CP configuration information for the connection of external CPs to the external virtual link. See note.\n",
- "type": "array",
- "items": {
- "description": "This type represents configuration information for external CPs created. * NOTE 1: \tIn case this identifier refers to a CPD with trunking enabled, the external CP instances created\n from this CPD will represent ports in a trunk.\n* NOTE 2: \tWithin one VNF instance, all VNFC instances created from a particular VDU have the same external\n connectivity. Thus, given a particular value of the \"cpdId\" attribute, there shall be one\n \"cpConfig\" entry for each VNFC instance that has been or can be created from a VDU which includes\n a CPD identified by the \"cpdId\" attribute. If the cpConfig represents a subport in a trunk,\n all \"cpConfig\" entries in this list shall have the same segmentationId, which means they are\n connected to the same set of external VLs via the trunk.\n* NOTE 3: \tThe map entry value shall be set to \"null\" in order to delete a \"VnfExtCpConfig\" entry identified\n by a particular key value from the map, i.e. for the disconnection of an existing external\n CP instance addressed by cpInstanceId in the deleted map entry from a particular external\n virtual link, and deletion of that instance in case it represents a subport. Deleting the\n last key from the map removes the affected instance of the \"VnfExtCpData\" structure from\n its parent data structure.\n* NOTE 4: If, as defined by the input parameters of a \"ChangeVnfFlavour\", \"ChangeExtVnfConnectivity\" or \n \"ChangeCurrentVnfPkg\" operation or as part of the Grant response for any of these operations, a \n cpConfig map entry identified by a particular map key value is moved into another \"ExtVirtualLinkData\"\n or \"VnfExtCpData\" structure, this particular cpConfig map entry may be used by an external CP instance\n different than the one that has used it before the operation, or by no external CP instance at all.\n Renaming a CPD identifier during the \"changeCurrentVnfPkg\" operation does not count as moving the\n related \"cpConfig\" map entries to a new \"extCpData\" structure.\n",
+ }
+ },
+ "changedExtConnectivity": {
+ "description": "Information about changed external connectivity, if applicable. See note 1.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents information about an external VL.\nNOTE:\tThis attribute reflects the current configuration information that has resulted from merging into this attribute \n the \"VnfExtCpData\" information which was passed as part of the \"ExtVirtualLinkData\" structure in the input of the \n most recent VNF LCM operation such as \"InstantiateVnfRequest\", \"ChangeExtVnfConnectivityRequest\", \"ChangeVnfFlavourRequest\" \n or \"ChangeCurrentVnfPkgRequest\", or in the Grant response. If applying such change results in an empty list of \n \"currentVnfExtCpData\" structure instances, the affected instance of \"ExtVirtualLinkInfo\" shall be removed from its \n parent data structure.\n",
"type": "object",
"required": [
- "cpdId"
+ "id",
+ "resourceHandle",
+ "currentVnfExtCpData"
],
"properties": {
- "cpdId": {
- "description": "An identifier that is unique within a VNF descriptor.\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). See notes 2, 3 and 4.\n",
- "type": "object",
- "additionalProperties": {
- "description": "This type represents an externally provided link port or network address information per instance of an external connection point. In case a link port is provided, the VNFM shall use that link port when connecting the external CP to the external VL. In a link port is not provided, the VNFM shall create a link port on the external VL, and use that link port to connect the external CP to the external VL. * NOTE: The following conditions apply to the attributes \"linkPortId\" and \"cpProtocolData\":\n 1) Void.\n 2) At least one of the \"linkPortId\" and \"cpProtocolData\" attributes shall be present for an external\n CP instance representing a subport that is to be created, or an external CP instance that is to be\n created by creating the corresponding VNFC or VNF instance during the current or a subsequent LCM\n operation, or for an existing external CP instance that is to be re-configured or added to a\n 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\n a pre created link port, and the VNFM can use means outside the scope of the present document to obtain\n the pre-configured address information for the connection point from the resource representing\n the link port.\n 5) If both \"cpProtocolData\" and \"linkportId\" are provided, the API consumer shall ensure that the\n cpProtocolData can be used with the pre-created link port referenced by \"linkPortId\".\n",
- "anyOf": [
- {
- "required": [
- "linkPortId"
- ]
- },
- {
- "required": [
- "cpProtocolData"
- ]
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceHandle": {
+ "required": [
+ "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",
+ "properties": {
+ "vimConnectionId": {
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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": "object",
- "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 to the VNFM the need to create a dedicated link port for the external CP. If set to True, the VNFM shall create a link port. If set to False, the VNFM shall not create a link port. 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 note.\n",
- "type": "array",
- "items": {
- "description": "This type represents network protocol data. * NOTE:\tThis attribute allows to signal the addition of further types of layer and protocol\n in future versions of the present document in a backwards-compatible way. In the current\n version of the present document, only IP over Ethernet is supported.\n",
+ },
+ "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.\nNOTE 1:\tThe use cases UC#4 and UC#5 in clause A.4 of ETSI GS NFV-IFA 007 provide examples for such a configuration. NOTE 2:\tThe value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\" attribute.\n",
"type": "object",
"required": [
- "layerProtocol"
+ "id",
+ "resourceHandle"
],
"properties": {
- "layerProtocol": {
- "description": "Identifier of layer(s) and protocol(s). See note.\n",
- "type": "string",
- "enum": [
- "IP_OVER_ETHERNET"
- ]
- },
- "ipOverEthernet": {
- "description": "This type represents network address data for IP over Ethernet. * NOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. * NOTE 2:\tExactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present. * NOTE 3:\tIf the CP instance represents a subport in a trunk, segmentationId shall be present.\n Otherwise it shall not be present.\n* NOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the actual\n network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header\n of the packets or it may be an identifier used between the application and the NFVI networking\n infrastructure to identify the network sub-interface of the trunk port in question. In the latter\n case the NFVI infrastructure will map this local segmentationId to whatever segmentationId is\n actually used by the NFVI’s transport technology.\n",
- "type": "object",
- "anyOf": [
- {
- "required": [
- "macAddress"
- ]
- },
- {
- "required": [
- "ipAddresses"
- ]
- }
- ],
- "oneOf": [
- {
- "required": [
- "fixedAddresses"
- ]
- },
- {
- "required": [
- "numDynamicAddresses"
- ]
- },
- {
- "required": [
- "ipAddressRange"
- ]
- }
- ],
- "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: -\tVLAN: the subport uses VLAN as encapsulation type. -\tINHERIT: the subport gets its segmentation type from the network it’s 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",
+ "id": {
+ "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"
- ],
- "properties": {
- "type": {
- "description": "The type of the IP addresses. Permitted values: IPV4, IPV6.\n",
- "type": "string",
- "enum": [
- "IPV4",
- "IPV6"
- ]
+ },
+ "resourceHandle": {
+ "required": [
+ "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",
+ "properties": {
+ "vimConnectionId": {
+ "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.\n",
+ "type": "string"
},
- "fixedAddresses": {
- "description": "Fixed addresses to assign (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"
- }
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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 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"
+ }
+ }
},
- "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. 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"
+ "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 the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "currentVnfExtCpData": {
+ "description": "Allows the API consumer to read the current CP configuration information for the connection of external CPs to the external virtual link. See note.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents configuration information for external CPs created. * NOTE 1: \tIn case this identifier refers to a CPD with trunking enabled, the external CP instances created\n from this CPD will represent ports in a trunk.\n* NOTE 2: \tWithin one VNF instance, all VNFC instances created from a particular VDU have the same external\n connectivity. Thus, given a particular value of the \"cpdId\" attribute, there shall be one\n \"cpConfig\" entry for each VNFC instance that has been or can be created from a VDU which includes\n a CPD identified by the \"cpdId\" attribute. If the cpConfig represents a subport in a trunk,\n all \"cpConfig\" entries in this list shall have the same segmentationId, which means they are\n connected to the same set of external VLs via the trunk.\n* NOTE 3: \tThe map entry value shall be set to \"null\" in order to delete a \"VnfExtCpConfig\" entry identified\n by a particular key value from the map, i.e. for the disconnection of an existing external\n CP instance addressed by cpInstanceId in the deleted map entry from a particular external\n virtual link, and deletion of that instance in case it represents a subport. Deleting the\n last key from the map removes the affected instance of the \"VnfExtCpData\" structure from\n its parent data structure.\n* NOTE 4: If, as defined by the input parameters of a \"ChangeVnfFlavour\", \"ChangeExtVnfConnectivity\" or\n \"ChangeCurrentVnfPkg\" operation, a cpConfig map entry identified by a particular map key value \n is moved into another \"ExtVirtualLinkData\" or \"VnfExtCpData\" structure, this particular cpConfig\n map entry may be used by an external CP instance different than the one that has used it before the\n operation, or by no external CP instance at all. Renaming a CPD identifier during the \"changeCurrentVnfPkg\"\n operation does not count as moving the related \"cpConfig\" map entries to a new \"extCpData\" structure.\n",
+ "type": "object",
+ "required": [
+ "cpdId"
+ ],
+ "properties": {
+ "cpdId": {
+ "description": "An identifier that is unique within a VNF descriptor.\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 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",
+ "anyOf": [
+ {
+ "required": [
+ "linkPortId"
+ ]
+ },
+ {
+ "required": [
+ "cpProtocolData"
+ ]
+ },
+ {
+ "required": [
+ "netAttDefResourceId"
+ ]
+ }
+ ],
+ "type": "object",
+ "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 to the VNFM the need to create a dedicated link port for the external CP. If set to True, the VNFM shall create a link port. If set to False, the VNFM shall not create a link port. 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 2.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents network protocol data. * NOTE:\tThis attribute allows to signal the addition of further types of layer and protocol\n in future versions of the present document in a backwards-compatible way. In the current\n 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:\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 network address data for IP over Ethernet. * NOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. * NOTE 2:\tExactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present. * NOTE 3:\tIf the CP instance represents a subport in a trunk, segmentationId shall be present.\n Otherwise it shall not be present.\n* NOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the actual\n network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header\n of the packets or it may be an identifier used between the application and the NFVI networking\n infrastructure to identify the network sub-interface of the trunk port in question. In the latter\n case the NFVI infrastructure will map this local segmentationId to whatever segmentationId is\n actually used by the NFVI's transport technology.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "required": [
+ "macAddress"
+ ]
+ },
+ {
+ "required": [
+ "ipAddresses"
+ ]
+ }
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "fixedAddresses"
+ ]
+ },
+ {
+ "required": [
+ "numDynamicAddresses"
+ ]
+ },
+ {
+ "required": [
+ "ipAddressRange"
+ ]
+ }
+ ],
+ "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: -\tVLAN: the subport uses VLAN as encapsulation type. -\tINHERIT: the subport gets its segmentation type from the network itΓÇÖs 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"
+ ],
+ "properties": {
+ "type": {
+ "description": "The type of the IP addresses. Permitted values: IPV4, IPV6.\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
+ },
+ "fixedAddresses": {
+ "description": "Fixed addresses to assign (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"
+ }
+ },
+ "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. 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.\n",
+ "type": "string"
+ }
+ }
+ }
+ }
+ }
+ },
+ "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",
+ "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"
+ }
+ }
+ }
+ }
+ }
},
- "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"
+ "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 2, 3 and 4.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\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 contains 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": {
+ "required": [
+ "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",
+ "properties": {
+ "vimConnectionId": {
+ "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.\n",
+ "type": "string"
},
- "subnetId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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 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 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"
+ }
}
- }
}
- }
}
- }
}
- }
}
- }
- }
- }
- }
- },
- "modificationsTriggeredByVnfPkgChange": {
- "description": "This type represents attribute modifications that were performed on an \"Individual VNF instance\" resource when changing the current VNF package. The attributes that can be included consist of those requested to be modified explicitly in the \"ChangeCurrentVnfPkgRequest\" data structure, and additional attributes of the \"VnfInstance\" data structure that were modified implicitly during the operation. The \"ModificationsTriggeredByVnfPkgChange\" data type shall comply with the provisions defined in table 5.5.3.21-1.\nNOTE 1:\tThis attribute represents the delta (semantics as per IETF RFC 7396, JSON Merge Patch) between the value \n of the attribute at the start of the \"Change current VNF package\" operation and the value of the attribute \n at its completion.\nNOTE 2:\tIf present, this attribute (which depends on the value of the \"vnfdId\" attribute) was modified implicitly \n during the related operation and contains a copy of the value of the related attribute from the VNFD in the \n VNF Package identified by the \"vnfdId\" attribute.\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 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"
- },
- "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 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"
- },
- "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 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"
- },
- "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\". See note 2.\n",
- "type": "string"
- },
- "vnfProductName": {
- "description": "If present, this attribute signals the new value of the \"vnfProductName\" attribute in \"VnfInstance\". See note 2.\n",
- "type": "string"
- },
- "vnfSoftwareVersion": {
- "description": "A version.\n",
- "type": "string"
- },
- "vnfdVersion": {
- "description": "A version.\n",
- "type": "string"
- }
- }
- },
- "vnfSnapshotInfoId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "lcmCoordinations": {
- "description": "Information about LCM coordination actions (see clause 10) related to this LCM operation occurrence.\n",
- "type": "object",
- "required": [
- "id",
- "coordinationActionName",
- "startTime",
- "endpointType"
- ],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "coordinationActionName": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "coordinationResult": {
- "description": "The enumeration LcmCoordResultType defines the permitted values to represent the result of executing an LCM coordination action. The coordination result also implies the action to be performed by the VNFM as the follow-up to this coordination. Value | Description ------|------------ CONTINUE | The related LCM operation shall be continued, staying in the state \"PROCESSING\". ABORT | The related LCM operation shall be aborted by transitioning into the state \"FAILED_TEMP\". CANCELLED | The coordination action has been cancelled upon request of the API consumer, i.e. the VNFM. The related LCM operation shall be aborted by transitioning into the state \"FAILED_TEMP\".\n",
- "type": "string",
- "enum": [
- "CONTINUE",
- "ABORT",
- "CANCELLED"
- ]
- },
- "startTime": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "endTime": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "endpointType": {
- "description": "The endpoint type used by this coordination action. Valid values: - MGMT: coordination with other operation supporting management systems (e.g. EM) - VNF: coordination with the VNF instance\n",
- "type": "string",
- "enum": [
- "MGMT",
- "VNF"
- ]
- },
- "delay": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- }
- }
- },
- "rejectedLcmCoordinations": {
- "description": "Information about LCM coordination actions (see clause 10) that were rejected by 503 error which means they will be tried again after a delay. See note 5.\n",
- "type": "object",
- "required": [
- "coordinationActionName",
- "rejectionTime",
- "endpointType",
- "delay"
- ],
- "properties": {
- "coordinationActionName": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "rejectionTime": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "endpointType": {
- "description": "The endpoint type used by this coordination action. Valid values: - MGMT: coordination with other operation supporting management systems (e.g. EM) - VNF: coordination with the VNF instance\n",
- "type": "string",
- "enum": [
- "MGMT",
- "VNF"
- ]
- },
- "delay": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- }
- }
- },
- "warnings": {
- "description": "Warning messages that were generated while the operation was executing.\nIf the operation has included LCM coordination actions and these have resulted in warnings, such warnings should be added to this attribute.\n",
- "type": "array",
- "items": {
- "type": "string"
- }
- },
- "_links": {
- "description": "Links to resources related to this resource.\n",
- "type": "object",
- "required": [
- "self",
- "vnfInstance"
- ],
- "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"
- }
- }
- },
- "vnfInstance": {
- "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"
- }
- }
- },
- "grant": {
- "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"
- }
}
- },
- "cancel": {
- "description": "This type represents a link to a resource using an absolute URI.\n",
+ },
+ "modificationsTriggeredByVnfPkgChange": {
+ "description": "This type represents attribute modifications that were performed on an \"Individual VNF instance\" resource when changing the current VNF package. The attributes that can be included consist of those requested to be modified explicitly in the \"ChangeCurrentVnfPkgRequest\" data structure, and additional attributes of the \"VnfInstance\" data structure that were modified implicitly during the operation.\nNOTE 1:\tThis attribute represents the delta (semantics as per IETF RFC 7396, JSON Merge Patch) between the value \n of the attribute at the start of the \"Change current VNF package\" operation and the value of the attribute \n at its completion.\nNOTE 2:\tIf present, this attribute (which depends on the value of the \"vnfdId\" attribute) was modified implicitly \n during the related operation and contains a copy of the value of the related attribute from the VNFD in the \n VNF Package identified by the \"vnfdId\" attribute.\n",
"type": "object",
- "required": [
- "href"
- ],
"properties": {
- "href": {
- "description": "String formatted according to IETF RFC 3986.\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 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"
+ },
+ "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 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"
+ },
+ "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 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"
+ },
+ "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\". See note 2.\n",
+ "type": "string"
+ },
+ "vnfProductName": {
+ "description": "If present, this attribute signals the new value of the \"vnfProductName\" attribute in \"VnfInstance\". See note 2.\n",
+ "type": "string"
+ },
+ "vnfSoftwareVersion": {
+ "description": "A version.\n",
+ "type": "string"
+ },
+ "vnfdVersion": {
+ "description": "A version.\n",
+ "type": "string"
+ },
+ "vimConnectionInfo": {
+ "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-relate dparameters 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",
+ "type": "object",
+ "required": [
+ "vimType"
+ ],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vimType": {
+ "description": "Discriminator for the different types of the VIM information. The value of this attribute determines the structure of the \"interfaceInfo\" and \"accessInfo\" attributes, based on the type of the VIM., CISM, CIR or MCIOP repository. The set of permitted values is expected to change over time as new types or versions of VIMs become available. The ETSI NFV registry of VIM-related information [i.3] provides access to information about VimConnectionInfo definitions for various VIM, CISM, CIR or MCIOP repository types. The structure of the registry is defined in annex C.\n",
+ "type": "string"
+ },
+ "interfaceInfo": {
+ "description": "This 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"
+ },
+ "accessInfo": {
+ "description": "This 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"
+ },
+ "extra": {
+ "description": "This 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"
+ }
+ }
+ }
+ }
}
- },
- "retry": {
- "description": "This type represents a link to a resource using an absolute URI.\n",
+ },
+ "vnfSnapshotInfoId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "lcmCoordinations": {
+ "description": "Information about LCM coordination actions (see clause 10) related to this LCM operation occurrence.\n",
"type": "object",
"required": [
- "href"
+ "id",
+ "coordinationActionName",
+ "startTime",
+ "endpointType"
],
"properties": {
- "href": {
- "description": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- }
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "coordinationActionName": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "coordinationResult": {
+ "description": "The enumeration LcmCoordResultType defines the permitted values to represent the result of executing an LCM coordination action. The coordination result also implies the action to be performed by the VNFM as the follow-up to this coordination. Value | Description ------|------------ CONTINUE | The related LCM operation shall be continued, staying in the state \"PROCESSING\". ABORT | The related LCM operation shall be aborted by transitioning into the state \"FAILED_TEMP\". CANCELLED | The coordination action has been cancelled upon request of the API consumer, i.e. the VNFM. The related LCM operation shall be aborted by transitioning into the state \"FAILED_TEMP\".\n",
+ "type": "string",
+ "enum": [
+ "CONTINUE",
+ "ABORT",
+ "CANCELLED"
+ ]
+ },
+ "startTime": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "endTime": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "endpointType": {
+ "description": "The endpoint type used by this coordination action. Valid values: - MGMT: coordination with other operation supporting management systems (e.g. EM) - VNF: coordination with the VNF instance\n",
+ "type": "string",
+ "enum": [
+ "MGMT",
+ "VNF"
+ ]
+ },
+ "delay": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ }
}
- },
- "rollback": {
- "description": "This type represents a link to a resource using an absolute URI.\n",
+ },
+ "rejectedLcmCoordinations": {
+ "description": "Information about LCM coordination actions (see clause 10) that were rejected by 503 error which means they will be tried again after a delay. See note 5.\n",
"type": "object",
"required": [
- "href"
+ "coordinationActionName",
+ "rejectionTime",
+ "endpointType",
+ "delay"
],
"properties": {
- "href": {
- "description": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- }
+ "coordinationActionName": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "rejectionTime": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "endpointType": {
+ "description": "The endpoint type used by this coordination action. Valid values: - MGMT: coordination with other operation supporting management systems (e.g. EM) - VNF: coordination with the VNF instance\n",
+ "type": "string",
+ "enum": [
+ "MGMT",
+ "VNF"
+ ]
+ },
+ "delay": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ }
}
- },
- "fail": {
- "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",
+ },
+ "warnings": {
+ "description": "Warning messages that were generated while the operation was executing.\nIf the operation has included LCM coordination actions and these have resulted in warnings, such warnings should be added to this attribute.\n",
+ "type": "array",
+ "items": {
"type": "string"
- }
}
- },
- "vnfSnapshot": {
- "description": "This type represents a link to a resource using an absolute URI.\n",
+ },
+ "_links": {
+ "description": "Links to resources related to this resource.\n",
"type": "object",
"required": [
- "href"
+ "self",
+ "vnfInstance"
],
"properties": {
- "href": {
- "description": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- }
+ "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"
+ }
+ }
+ },
+ "vnfInstance": {
+ "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"
+ }
+ }
+ },
+ "grant": {
+ "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"
+ }
+ }
+ },
+ "cancel": {
+ "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"
+ }
+ }
+ },
+ "retry": {
+ "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"
+ }
+ }
+ },
+ "rollback": {
+ "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"
+ }
+ }
+ },
+ "fail": {
+ "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"
+ }
+ }
+ },
+ "vnfSnapshot": {
+ "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"
+ }
+ }
+ }
}
- }
}
- }
}
- }
+ }
}
\ No newline at end of file
diff --git a/SOL002/VNFPerformanceManagement-API/ApiVersion.robot b/SOL002/VNFPerformanceManagement-API/ApiVersion.robot
index 19cb6597b93d310da1209bfc73d2008ee8757e9f..359048058f864d71e7eb3f10eb3aee3b7272af92 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] v3.5.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.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 c76ccecc8ccdd37e09c86133b1aa0da20e86039d..4e73e9b703ddb1d2aa8ab85ea06d74fb7761d56b 100644
--- a/SOL002/VNFPerformanceManagement-API/IndividualPmJob.robot
+++ b/SOL002/VNFPerformanceManagement-API/IndividualPmJob.robot
@@ -13,12 +13,13 @@ 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] v3.6.1
+ ... Reference: Clause 6.4.3.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
GET individual VNF Performance Job
Check HTTP Response Status Code Is 200
+ Check HTTP Response Header Contains ETag and Last-Modified
Check HTTP Response Body Json Schema Is PmJob
Check HTTP Response Body Pm Job Identifier matches the requested Pm Job
@@ -27,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] v3.6.1
+ ... Reference: Clause 6.4.3.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -40,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] v3.6.1
+ ... Reference: Clause 6.4.3.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: The VNF Performance Job is no more available in the VNFM
@@ -53,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] v3.6.1
+ ... Reference: Clause 6.4.3.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -66,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] v3.6.1
+ ... Reference: Clause 6.4.3.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -78,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] v3.6.1
+ ... Reference: Clause 6.4.3.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -90,12 +91,13 @@ 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] v3.6.1
+ ... Reference: Clause 6.4.3.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
Send Patch request for individual VNF Performance Job
Check HTTP Response Status Code Is 200
+ Check HTTP Response Header Contains ETag and Last-Modified
Check HTTP Response Body Json Schema Is PMJobModifications
PATCH Individual VNF Performance Job - Precondition failed
@@ -103,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] v3.6.1
+ ... Reference: Clause 6.4.3.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: The VNF Performance Job is not modified by the operation
@@ -117,7 +119,7 @@ PATCH Individual VNF Performance Job - UNPROCESSIBLE ENTITY
... Test title: PATCH Individual VNF Performance Job - UNPROCESSIBLE ENTITY
... 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] v3.6.1
+ ... Reference: Clause 6.4.3.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: The VNFM cannot reach the Notification endpoint.
... Post-Conditions: none
@@ -235,3 +237,10 @@ Check HTTP Response Body Json Schema Is
Validate Json ${schema} ${response['body']}
Log Json Schema Validation OK
+Check HTTP Response Header Contains ETag and Last-Modified
+ Pass Execution If ${HEADER_TEST_SUPPORTED} == 0 Headers testing not supported. Skipping the Test.
+ Log ${response['headers']}
+ Should Contain ${response['headers']} Etag
+ Should Contain ${response['headers']} Last-Modified
+ Log Etag and Last-Modified Headers are present
+
diff --git a/SOL002/VNFPerformanceManagement-API/IndividualReport.robot b/SOL002/VNFPerformanceManagement-API/IndividualReport.robot
index 8ec2ab61ec568f5ea28665be3f1a552aeb6ceedf..716fdafd289e70905b93db8dbc012635e9e9050f 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] v3.6.1
+ ... Reference: Clause 6.4.4.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.4.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.4.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.4.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.4.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.4.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.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 ef2e945afd1b9b31331350418190641279d7527f..593d3eb05c17a3baec9f7485d75d0532aa18d57b 100644
--- a/SOL002/VNFPerformanceManagement-API/IndividualThreshold.robot
+++ b/SOL002/VNFPerformanceManagement-API/IndividualThreshold.robot
@@ -12,12 +12,13 @@ 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] v3.6.1
+ ... Reference: Clause 6.4.6.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
GET individual VNF Performance Threshold
Check HTTP Response Status Code Is 200
+ Check HTTP Response Header Contains ETag and Last-Modified
Check HTTP Response Body Json Schema Is Threshold
Check HTTP Response Body Threshold Identifier matches the requested Threshold
@@ -26,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] v3.6.1
+ ... Reference: Clause 6.4.6.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -39,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] v3.6.1
+ ... Reference: Clause 6.4.6.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: The VNF Performance Threshold is not available anymore in the VNFM
@@ -52,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] v3.6.1
+ ... Reference: Clause 6.4.6.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -65,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] v3.6.1
+ ... Reference: Clause 6.4.6.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: The VNF Performance Threshold is not created on the VNFM
@@ -77,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] v3.6.1
+ ... Reference: Clause 6.4.6.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -89,12 +90,13 @@ 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] v3.6.1
+ ... Reference: Clause 6.4.6.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: The VNF Performance Threshold is not modified by the operation
Send Patch request for individual VNF Performance Threshold
Check HTTP Response Status Code Is 200
+ Check HTTP Response Header Contains ETag and Last-Modified
Check HTTP Response Body Json Schema Is ThresholdModifications
PATCH Individual Threshold - Precondition failed
@@ -102,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] v3.6.1
+ ... Reference: Clause 6.4.6.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: The VNF Performance Job is not modified by the operation
@@ -116,7 +118,7 @@ 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 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] v3.6.1
+ ... Reference: Clause 6.4.6.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.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
@@ -234,4 +236,9 @@ Check HTTP Response Body Json Schema Is
Validate Json ${schema} ${response['body']}
Log Json Schema Validation OK
-
+Check HTTP Response Header Contains ETag and Last-Modified
+ Pass Execution If ${HEADER_TEST_SUPPORTED} == 0 Headers testing not supported. Skipping the Test.
+ Log ${response['headers']}
+ Should Contain ${response['headers']} Etag
+ Should Contain ${response['headers']} Last-Modified
+ Log Etag and Last-Modified Headers are present
diff --git a/SOL002/VNFPerformanceManagement-API/NotificationEndpoint.robot b/SOL002/VNFPerformanceManagement-API/NotificationEndpoint.robot
index 0c4226b666d099c6844c80f6a57bbbab6ebb17e3..c18e20f2c52dc62639adc33534825610cc65f373 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] v3.6.1
+ ... Reference: Clause 6.4.9.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.9.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
diff --git a/SOL002/VNFPerformanceManagement-API/PMJobs.robot b/SOL002/VNFPerformanceManagement-API/PMJobs.robot
index af2ce1fa4e597f94240383ddce98a632149f8c97..e1a52d741fa5d0c4a76a8858eb6412becfd20473 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] v3.6.1
+ ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 4.3.3.2.1, 6.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 4.3.3.2.1, 6.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 4.3.3.2.1, 6.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 4.3.3.2.1, 6.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.2.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.2.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.2.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 4.3.3.2.1, 6.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -210,7 +210,7 @@ POST Create new VNF Performance Monitoring Job - UNPROCESSIBLE ENTITY
... Test title: POST Create a new VNF Performance Monitoring Job - UNPROCESSIBLE ENTITY
... 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] v3.6.1
+ ... Reference: Clause 6.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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 0c5343f2d088a85de3e6bc1ccaacbef337eaf0f8..6fba18cd26767360867979ccf358dcc4f263fc96 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] v3.6.1
+ ... Reference: Clause 6.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.5.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.5.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.5.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.5.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.5.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -142,7 +142,7 @@ POST Create new Performance Threshold - UNPROCESSIBLE ENTITY
... Test title: POST Create new Performance Threshold
... 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] v3.6.1
+ ... Reference: Clause 6.4.5.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: The VNFM cannot reach the Notification endpoint.
... Post-Conditions: none
diff --git a/SOL002/VNFPerformanceManagement-API/environment/variables.txt b/SOL002/VNFPerformanceManagement-API/environment/variables.txt
index 0eedfd4a5e0a90732b356e41fc47d96d5c5e620c..927b59b9ba51b41e781bb8415b9b753db8eafd93 100644
--- a/SOL002/VNFPerformanceManagement-API/environment/variables.txt
+++ b/SOL002/VNFPerformanceManagement-API/environment/variables.txt
@@ -16,6 +16,8 @@ ${AUTHORIZATION_HEADER} Authorization
${AUTHORIZATION_TOKEN} Bearer 0b79bab50daca910b000d4f1a2b675d604257e42
${AUTH_USAGE} 1
+${HEADER_TEST_SUPPORTED} 0
+
${VNFM_CHECKS_NOTIF_ENDPOINT} 1
${callback_uri} http://localhost
${unreachable_callback_uri} http://not-reachable-uri
diff --git a/SOL002/VNFPerformanceManagement-API/schemas/PMJobModifications.json b/SOL002/VNFPerformanceManagement-API/schemas/PMJobModifications.json
index 7a09620564f077ebb19981dd44bb3d3df07aa67c..10a10761ddc321fb8500d785727f5ad4b8c20a0c 100644
--- a/SOL002/VNFPerformanceManagement-API/schemas/PMJobModifications.json
+++ b/SOL002/VNFPerformanceManagement-API/schemas/PMJobModifications.json
@@ -1,62 +1,75 @@
- {
- "description": "This type represents modifications to a PM job. It shall comply with the provisions defined in table 6.5.2.12-1.\n",
- "type": "object",
- "properties": {
- "callbackUri": {
- "description": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- },
- "authentication": {
- "type": "object",
- "required": [
- "authType"
- ],
- "properties": {
- "authType": {
- "description": "Defines the types of Authentication / Authorization which the API consumer is willing to accept when receiving a notification. Permitted values: * BASIC: In every HTTP request to the notification endpoint, use\n HTTP Basic authentication with the client credentials. \n* OAUTH2_CLIENT_CREDENTIALS: In every HTTP request to the\n notification endpoint, use an OAuth 2.0 Bearer token, obtained\n using the client credentials grant type.\n* TLS_CERT: Every HTTP request to the notification endpoint is sent\n over a mutually authenticated TLS session, i.e. not only the\n server is authenticated, but also the client is authenticated\n during the TLS tunnel setup.\n",
- "type": "array",
- "items": {
- "type": "string",
- "enum": [
- "BASIC",
- "OAUTH2_CLIENT_CREDENTIALS",
- "TLS_CERT"
- ]
- }
- },
- "paramsBasic": {
- "description": "Parameters for authentication/authorization using BASIC. Shall be present if authType is \"BASIC\" and the contained information has not been provisioned out of band. Shall be absent otherwise.\n",
- "type": "object",
- "properties": {
- "userName": {
- "description": "Username to be used in HTTP Basic authentication. Shall be present if it has not been provisioned out of band.\n",
- "type": "string"
- },
- "password": {
- "description": "Password to be used in HTTP Basic authentication. Shall be present if it has not been provisioned out of band.\n",
- "type": "string"
- }
+{
+ "description": "This type represents modifications to a PM job.\nNOTE:\tAt least one of the attributes defined in this type shall be present in request bodies.\n",
+ "type": "object",
+ "oneOf": [
+ {
+ "required": [
+ "callbackUri"
+ ]
+ },
+ {
+ "required": [
+ "authentication"
+ ]
+ }
+ ],
+ "properties": {
+ "callbackUri": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ },
+ "authentication": {
+ "description": "* NOTE: The clientId and clientPassword passed in a subscription shall not be the same as the clientId and\n clientPassword that are used to obtain authorization for API requests. Client credentials may differ between\n subscriptions. The value of clientPassword should be generated by a random process\n",
+ "type": "object",
+ "required": [
+ "authType"
+ ],
+ "properties": {
+ "authType": {
+ "description": "Defines the types of Authentication / Authorization which the API consumer is willing to accept when receiving a notification. Permitted values: * BASIC: In every HTTP request to the notification endpoint, use\n HTTP Basic authentication with the client credentials. \n* OAUTH2_CLIENT_CREDENTIALS: In every HTTP request to the\n notification endpoint, use an OAuth 2.0 Bearer token, obtained\n using the client credentials grant type.\n* TLS_CERT: Every HTTP request to the notification endpoint is sent\n over a mutually authenticated TLS session, i.e. not only the\n server is authenticated, but also the client is authenticated\n during the TLS tunnel setup.\n",
+ "type": "array",
+ "items": {
+ "type": "string",
+ "enum": [
+ "BASIC",
+ "OAUTH2_CLIENT_CREDENTIALS",
+ "TLS_CERT"
+ ]
+ }
+ },
+ "paramsBasic": {
+ "description": "Parameters for authentication/authorization using BASIC. Shall be present if authType is \"BASIC\" and the contained information has not been provisioned out of band. Shall be absent otherwise.\n",
+ "type": "object",
+ "properties": {
+ "userName": {
+ "description": "Username to be used in HTTP Basic authentication. Shall be present if it has not been provisioned out of band.\n",
+ "type": "string"
+ },
+ "password": {
+ "description": "Password to be used in HTTP Basic authentication. Shall be present if it has not been provisioned out of band.\n",
+ "type": "string"
}
- },
- "paramsOauth2ClientCredentials": {
- "description": "Parameters for authentication/authorization using OAUTH2_CLIENT_CREDENTIALS. Shall be present if authType is \"OAUTH2_CLIENT_CREDENTIALS\" and the contained information has not been provisioned out of band. Shall be absent otherwise.\n",
- "type": "object",
- "properties": {
- "clientId": {
- "description": "Client identifier to be used in the access token request of the OAuth 2.0 client credentials grant type. Shall be present if it has not been provisioned out of band. The clientId and clientPassword passed in a subscription shall not be the same as the clientId and clientPassword that are used to obtain authorization for API requests. Client credentials may differ between subscriptions. The value of clientPassword should be generated by a random process.\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 be present if it has not been provisioned out of band. The clientId and clientPassword passed in a subscription shall not be the same as the clientId and clientPassword that are used to obtain authorization for API requests. Client credentials may differ between subscriptions. The value of clientPassword should be generated by a random process.\n",
- "type": "string"
- },
- "tokenEndpoint": {
- "description": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- }
+ }
+ },
+ "paramsOauth2ClientCredentials": {
+ "description": "Parameters for authentication/authorization using OAUTH2_CLIENT_CREDENTIALS. Shall be present if authType is \"OAUTH2_CLIENT_CREDENTIALS\" and the contained information has not been provisioned out of band. Shall be absent otherwise.\n",
+ "type": "object",
+ "properties": {
+ "clientId": {
+ "description": "Client identifier to be used in the access token request of the OAuth 2.0 client credentials grant type. Shall be present if it has not been provisioned out of band. See note.\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 be present if it has not been provisioned out of band. See note.\n",
+ "type": "string"
+ },
+ "tokenEndpoint": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
}
}
}
}
}
- }
\ No newline at end of file
+ }
+}
\ No newline at end of file
diff --git a/SOL002/VNFPerformanceManagement-API/schemas/PerformanceReport.schema.json b/SOL002/VNFPerformanceManagement-API/schemas/PerformanceReport.schema.json
index c0a9c444eb6cf2ac6e2a8b8800cccc857683a336..f499d9f467798bcf824e6828160b8b313fd3458d 100644
--- a/SOL002/VNFPerformanceManagement-API/schemas/PerformanceReport.schema.json
+++ b/SOL002/VNFPerformanceManagement-API/schemas/PerformanceReport.schema.json
@@ -1 +1,66 @@
-{ "description": "This type defines the format of a performance report provided by the VNFM to the NFVO as a result of collecting performance information as part of a PM job.\n", "type": "object", "properties": { "entries": { "description": "List of performance information entries. Each performance report entry is for a given metric of a given object (i.e. VNF instance), but can include multiple collected values.\n", "type": "array", "items": { "type": "object", "required": [ "objectType", "objectInstanceId", "performanceMetric", "performanceValue" ], "properties": { "objectType": { "description": "Defines the object type for which performance information is reported (i.e. VNF type). The string value shall be set to the vnfdId of the VNF instance to which the performance information relates.\n", "type": "string" }, "objectInstanceId": { "description": "An identifier with the intention of being globally unique.\n", "type": "string" }, "performanceMetric": { "description": "Name of the metric collected.\n", "type": "string" }, "performanceValues": { "description": "List of performance values with associated timestamp.\n", "type": "array", "items": { "type": "object", "required": [ "timeStamp", "performanceValue" ], "properties": { "timeStamp": { "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n", "type": "string", "format": "date-time" }, "value": { "description": "Value of the metric collected. The type of the \"value\" attribute (i.e. scalar, structure (Object in JSON), or array (of scalars, arrays or structures / Objects)) is assumed to be defined in the external measurement specification (see ETSI GS NFV-IFA 027).\n", "type": "object" } } } } } } } }}
\ No newline at end of file
+{
+ "description": "This type defines the format of a performance report provided by the VNFM to the NFVO as a result of collecting performance information as part of a PM job.\nNOTE:\tThe sub-object allows to structure the measured object but is not to be confused with sub-counters which allow \n to structure the measurement value.\n\nEXAMPLE:\n Measured object: VnfInstanceXYZ\n Sub-object: VnfcInstance1\n Measurement: vCPU_utilization\n Sub-counters: vCPU utilization of each of the vCPUs of VnfcInstance1 (vCPU utilization.vCPU1, vCPU_utilization.vCPU2, etc.).\n",
+ "type": "object",
+ "required": [
+ "entries"
+ ],
+ "properties": {
+ "entries": {
+ "description": "List of performance information entries. Each performance report entry is for a given metric of a given object (i.e. VNF instance), but can include multiple collected values.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": [
+ "objectType",
+ "objectInstanceId",
+ "performanceMetric",
+ "performanceValue"
+ ],
+ "properties": {
+ "objectType": {
+ "description": "Type of the measured object. The applicable measured object type for a measurement is defined in clause 7.2 of ETSI GS NFV-IFA 027.\n",
+ "type": "string"
+ },
+ "objectInstanceId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "subObjectInstanceId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "performanceMetric": {
+ "description": "Name of the metric collected. This attribute shall contain the related \"Measurement Name\" value as defined in clause 7.2 of ETSI GS NFV-IFA 027.\n",
+ "type": "string"
+ },
+ "performanceValues": {
+ "description": "List of performance values with associated timestamp.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": [
+ "timeStamp",
+ "value"
+ ],
+ "properties": {
+ "timeStamp": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "value": {
+ "description": "Value of the metric collected. The type of this attribute shall correspond to the related \"Measurement Unit\" as defined in clause 7.2. of ETSI GS NFV-IFA 027.\n",
+ "type": "object"
+ },
+ "context": {
+ "description": "This 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"
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+}
\ No newline at end of file
diff --git a/SOL002/VNFPerformanceManagement-API/schemas/PmJob.schema.json b/SOL002/VNFPerformanceManagement-API/schemas/PmJob.schema.json
index 65121412dcdc18bd63c0b3ddf837a3da8073a8d7..2ababaaeadfb3f935aa5279aa53f74b7c601dbdf 100644
--- a/SOL002/VNFPerformanceManagement-API/schemas/PmJob.schema.json
+++ b/SOL002/VNFPerformanceManagement-API/schemas/PmJob.schema.json
@@ -1 +1,153 @@
-{ "description": "This type represents a PM job.\n", "type": "object", "required": [ "id", "objectInstanceIds", "criteria" ], "properties": { "id": { "description": "An identifier with the intention of being globally unique.\n", "type": "string" }, "objectInstanceIds": { "description": "Identifiers of the VNF instances for which performance information is collected.\n", "type": "array", "items": { "description": "An identifier with the intention of being globally unique.\n", "type": "string" } }, "criteria": { "description": "Criteria of the collection of performance information.\n", "type": "object", "required": [ "collectionPeriod", "reportingPeriod" ], "properties": { "performanceMetric": { "description": "This defines the types of performance metrics for the specified object instances, as specified in ETSI GS NFV-IFA 027). At least one of the two attributes (performance metric or group) shall be present.\n", "type": "array", "items": { "type": "string" } }, "performanceMetricGroup": { "description": "Group of performance metrics. A metric group is a pre-defined list of metrics, known to the producer that it can decompose to individual metrics. At least one of the two attributes (performance metric or group) shall be present.\n", "type": "array", "items": { "type": "string" } }, "collectionPeriod": { "description": "Specifies the periodicity at which the producer will collect performance information. The unit shall be seconds. At the end of each reportingPeriod, the producer will inform the consumer about availability of the performance data collected for each completed collection period during this reportingPeriod. The reportingPeriod should be equal to or a multiple of the collectionPeriod. In the latter case, the performance data for the collection periods within one reporting period are reported together.\n", "type": "integer" }, "reportingPeriod": { "description": "Specifies the periodicity at which the producer will report to the consumer. about performance information. The unit shall be seconds. At the end of each reportingPeriod, the producer will inform the consumer about availability of the performance data collected for each completed collection period during this reportingPeriod. The reportingPeriod should be equal to or a multiple of the collectionPeriod. In the latter case, the performance data for the collection periods within one reporting period are reported together.\n", "type": "integer" }, "reportingBoundary": { "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n", "type": "string", "format": "date-time" } } }, "reports": { "description": "Information about available reports collected by this PM job.\n", "type": "object", "required": [ "href", "readyTime", "_links" ], "properties": { "href": { "description": "The Uri where the report can be obtained.\n", "type": "string", "format": "url" }, "readyTime": { "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n", "type": "string", "format": "date-time" }, "expiryTime": { "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n", "type": "string", "format": "date-time" }, "fileSize": { "description": "The size of the report file in bytes, if known.\n", "type": "integer" }, "_links": { "description": "Links for 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 the referenced resource.\n", "type": "string", "format": "url" } } }, "objects": { "description": "Links to resources representing the VNF instances for which performance information is collected. Shall be present if the VNF instance information is accessible as a resource.\n", "type": "array", "items": { "description": "This type represents a link to a resource.\n", "type": "object", "required": [ "href" ], "properties": { "href": { "description": "URI of the referenced resource.\n", "type": "string", "format": "url" } } } } } } } } }}
\ No newline at end of file
+{
+ "description": "This type represents a PM job.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "objectType",
+ "objectInstanceIds",
+ "criteria",
+ "callbackUri",
+ "_links"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "objectType": {
+ "description": "Type of the measured object. The applicable measured object type for a measurement is defined in clause 7.2 of ETSI GS NFV-IFA 027.\n",
+ "type": "string"
+ },
+ "objectInstanceIds": {
+ "description": "Identifiers of the VNF instances for which performance information is collected.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ },
+ "subObjectInstanceIds": {
+ "description": "Identifiers of the sub-object instances of the measured object instance for which performance information is requested to be collected. May be present if a sub-object is defined in clause 6.2 of ETSI GS NFV-IFA 027 for the related measured object type. If this attribute is present, the cardinality of the \"objectInstanceIds\" attribute shall be 1. If this attribute is absent and a sub-object is defined in clause 6.2 of ETSI GS NFV IFA 027 for the related measured object type, measurements will be taken for all sub-object instances of the measured object instance.\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"
+ }
+ },
+ "criteria": {
+ "description": "This type represents collection criteria for PM jobs.\nNOTE 1:\tAt the end of each reportingPeriod, the API producer will inform the API consumer about availability of the \n performance data collected for each completed collection period during this reportingPeriod. \n The reportingPeriod should be equal to or a multiple of the collectionPeriod. In the latter case, the performance \n data for the collection periods within one reporting period are reported together.\nNOTE 2:\tIn particular when choosing short collection and reporting periods, the number of PM jobs that can be supported \n depends on the capability of the producing entity.\n",
+ "type": "object",
+ "required": [
+ "collectionPeriod",
+ "reportingPeriod"
+ ],
+ "properties": {
+ "performanceMetric": {
+ "description": "This defines the types of performance metrics for the specified object instances. Valid values are specified as \"Measurement Name\" values in clause 7.2 of ETSI GS NFV-IFA 027. At least one of the two attributes (performance metric or group) shall be present.\n",
+ "type": "array",
+ "items": {
+ "type": "string"
+ }
+ },
+ "performanceMetricGroup": {
+ "description": "Group of performance metrics. A metric group is a pre-defined list of metrics, known to the API producer that it can decompose to individual metrics. Valid values are specified as \"Measurement Group\" values in clause 7.2 of ETSI GS NFV-IFA 027. At least one of the two attributes (performance metric or group) shall be present.\n",
+ "type": "array",
+ "items": {
+ "type": "string"
+ }
+ },
+ "collectionPeriod": {
+ "description": "SSpecifies the periodicity at which the API producer will collect performance information. The unit shall be seconds. See notes 1 and 2.\n",
+ "type": "integer",
+ "minimum": 0,
+ "maximum": 1024
+ },
+ "reportingPeriod": {
+ "description": "Specifies the periodicity at which the API producer will report to the API consumer about performance information. The unit shall be seconds. See notes 1 and 2.\n",
+ "type": "integer",
+ "minimum": 0,
+ "maximum": 1024
+ },
+ "reportingBoundary": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ }
+ }
+ },
+ "callbackUri": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ },
+ "reports": {
+ "description": "Information about available reports collected by this PM job.\n",
+ "type": "object",
+ "required": [
+ "href",
+ "readyTime"
+ ],
+ "properties": {
+ "href": {
+ "description": "The URI where the report can be obtained.\n",
+ "type": "string",
+ "format": "url"
+ },
+ "readyTime": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "expiryTime": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "fileSize": {
+ "description": "The size of the report file in bytes, if known.\n",
+ "type": "integer",
+ "minimum": 0,
+ "maximum": 1024
+ }
+ }
+ },
+ "_links": {
+ "description": "Links for this resource.\n",
+ "type": "object",
+ "required": [
+ "self"
+ ],
+ "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"
+ }
+ }
+ },
+ "objects": {
+ "description": "Links to resources representing the measure object instances for which performance information is collected. Shall be present if the measured object instance information is accessible as a resource.\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"
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
\ No newline at end of file
diff --git a/SOL002/VNFPerformanceManagement-API/schemas/PmJobs.schema.json b/SOL002/VNFPerformanceManagement-API/schemas/PmJobs.schema.json
index 654acdcf1f41f72b24464e32472a944bbf422120..a623a448c959cb7f17b33a4a388e8eff18ee57f2 100644
--- a/SOL002/VNFPerformanceManagement-API/schemas/PmJobs.schema.json
+++ b/SOL002/VNFPerformanceManagement-API/schemas/PmJobs.schema.json
@@ -5,14 +5,21 @@
"type": "object",
"required": [
"id",
+ "objectType",
"objectInstanceIds",
- "criteria"
+ "criteria",
+ "callbackUri",
+ "_links"
],
"properties": {
"id": {
"description": "An identifier with the intention of being globally unique.\n",
"type": "string"
},
+ "objectType": {
+ "description": "Type of the measured object. The applicable measured object type for a measurement is defined in clause 7.2 of ETSI GS NFV-IFA 027.\n",
+ "type": "string"
+ },
"objectInstanceIds": {
"description": "Identifiers of the VNF instances for which performance information is collected.\n",
"type": "array",
@@ -21,8 +28,16 @@
"type": "string"
}
},
+ "subObjectInstanceIds": {
+ "description": "Identifiers of the sub-object instances of the measured object instance for which performance information is requested to be collected. May be present if a sub-object is defined in clause 6.2 of ETSI GS NFV-IFA 027 for the related measured object type. If this attribute is present, the cardinality of the \"objectInstanceIds\" attribute shall be 1. If this attribute is absent and a sub-object is defined in clause 6.2 of ETSI GS NFV IFA 027 for the related measured object type, measurements will be taken for all sub-object instances of the measured object instance.\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"
+ }
+ },
"criteria": {
- "description": "Criteria of the collection of performance information.\n",
+ "description": "This type represents collection criteria for PM jobs.\nNOTE 1:\tAt the end of each reportingPeriod, the API producer will inform the API consumer about availability of the \n performance data collected for each completed collection period during this reportingPeriod. \n The reportingPeriod should be equal to or a multiple of the collectionPeriod. In the latter case, the performance \n data for the collection periods within one reporting period are reported together.\nNOTE 2:\tIn particular when choosing short collection and reporting periods, the number of PM jobs that can be supported \n depends on the capability of the producing entity.\n",
"type": "object",
"required": [
"collectionPeriod",
@@ -30,99 +45,106 @@
],
"properties": {
"performanceMetric": {
- "description": "This defines the types of performance metrics for the specified object instances, as specified in ETSI GS NFV-IFA 027). At least one of the two attributes (performance metric or group) shall be present.\n",
+ "description": "This defines the types of performance metrics for the specified object instances. Valid values are specified as \"Measurement Name\" values in clause 7.2 of ETSI GS NFV-IFA 027. At least one of the two attributes (performance metric or group) shall be present.\n",
"type": "array",
"items": {
"type": "string"
}
},
"performanceMetricGroup": {
- "description": "Group of performance metrics. A metric group is a pre-defined list of metrics, known to the producer that it can decompose to individual metrics. At least one of the two attributes (performance metric or group) shall be present.\n",
+ "description": "Group of performance metrics. A metric group is a pre-defined list of metrics, known to the API producer that it can decompose to individual metrics. Valid values are specified as \"Measurement Group\" values in clause 7.2 of ETSI GS NFV-IFA 027. At least one of the two attributes (performance metric or group) shall be present.\n",
"type": "array",
"items": {
"type": "string"
}
},
"collectionPeriod": {
- "description": "Specifies the periodicity at which the producer will collect performance information. The unit shall be seconds. At the end of each reportingPeriod, the producer will inform the consumer about availability of the performance data collected for each completed collection period during this reportingPeriod. The reportingPeriod should be equal to or a multiple of the collectionPeriod. In the latter case, the performance data for the collection periods within one reporting period are reported together.\n",
- "type": "integer"
+ "description": "SSpecifies the periodicity at which the API producer will collect performance information. The unit shall be seconds. See notes 1 and 2.\n",
+ "type": "integer",
+ "minimum": 0,
+ "maximum": 1024
},
"reportingPeriod": {
- "description": "Specifies the periodicity at which the producer will report to the consumer. about performance information. The unit shall be seconds. At the end of each reportingPeriod, the producer will inform the consumer about availability of the performance data collected for each completed collection period during this reportingPeriod. The reportingPeriod should be equal to or a multiple of the collectionPeriod. In the latter case, the performance data for the collection periods within one reporting period are reported together.\n",
- "type": "integer"
+ "description": "Specifies the periodicity at which the API producer will report to the API consumer about performance information. The unit shall be seconds. See notes 1 and 2.\n",
+ "type": "integer",
+ "minimum": 0,
+ "maximum": 1024
},
"reportingBoundary": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
"type": "string",
"format": "date-time"
}
}
},
+ "callbackUri": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ },
"reports": {
"description": "Information about available reports collected by this PM job.\n",
"type": "object",
"required": [
"href",
- "readyTime",
- "_links"
+ "readyTime"
],
"properties": {
"href": {
- "description": "The Uri where the report can be obtained.\n",
+ "description": "The URI where the report can be obtained.\n",
"type": "string",
"format": "url"
},
"readyTime": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
"type": "string",
"format": "date-time"
},
"expiryTime": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
"type": "string",
"format": "date-time"
},
"fileSize": {
"description": "The size of the report file in bytes, if known.\n",
- "type": "integer"
- },
- "_links": {
- "description": "Links for this resource.\n",
+ "type": "integer",
+ "minimum": 0,
+ "maximum": 1024
+ }
+ }
+ },
+ "_links": {
+ "description": "Links for this resource.\n",
+ "type": "object",
+ "required": [
+ "self"
+ ],
+ "properties": {
+ "self": {
+ "description": "This type represents a link to a resource using an absolute URI.\n",
"type": "object",
"required": [
- "self"
+ "href"
],
"properties": {
- "self": {
- "description": "This type represents a link to a resource.\n",
- "type": "object",
- "required": [
- "href"
- ],
- "properties": {
- "href": {
- "description": "URI of the referenced resource.\n",
- "type": "string",
- "format": "url"
- }
- }
- },
- "objects": {
- "description": "Links to resources representing the VNF instances for which performance information is collected. Shall be present if the VNF instance information is accessible as a resource.\n",
- "type": "array",
- "items": {
- "description": "This type represents a link to a resource.\n",
- "type": "object",
- "required": [
- "href"
- ],
- "properties": {
- "href": {
- "description": "URI of the referenced resource.\n",
- "type": "string",
- "format": "url"
- }
- }
+ "href": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ }
+ }
+ },
+ "objects": {
+ "description": "Links to resources representing the measure object instances for which performance information is collected. Shall be present if the measured object instance information is accessible as a resource.\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"
}
}
}
diff --git a/SOL002/VNFPerformanceManagement-API/schemas/ProblemDetails.schema.json b/SOL002/VNFPerformanceManagement-API/schemas/ProblemDetails.schema.json
index 2af3ef9b3f8c0e1dc6bfa39a818ba45e63ca223c..a4c007a5c1501eaf4ae57b5973cda6ef1d4bbea5 100644
--- a/SOL002/VNFPerformanceManagement-API/schemas/ProblemDetails.schema.json
+++ b/SOL002/VNFPerformanceManagement-API/schemas/ProblemDetails.schema.json
@@ -1 +1,32 @@
-{ "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
+{
+ "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/SOL002/VNFPerformanceManagement-API/schemas/Subscriptions.schema.json b/SOL002/VNFPerformanceManagement-API/schemas/Subscriptions.schema.json
index fefb142da9f905120ff32246f73e6b88062978d5..ebc48dfd18579ce3821eb9ad1713559b9f9bea19 100644
--- a/SOL002/VNFPerformanceManagement-API/schemas/Subscriptions.schema.json
+++ b/SOL002/VNFPerformanceManagement-API/schemas/Subscriptions.schema.json
@@ -1 +1,145 @@
-{ "type": "array", "items": { "description": "This type represents a subscription.\n", "type": "object", "required": [ "id", "callbackUri", "_links" ], "properties": { "id": { "description": "An identifier with the intention of being globally unique.\n", "type": "string" }, "filter": { "description": "This type represents a filter that can be used to subscribe for notifications related to performance management events.\n", "type": "object", "properties": { "vnfInstanceSubscriptionFilter": { "description": "This type represents subscription filter criteria to match VNF instances.\n", "type": "object", "properties": { "vnfdIds": { "description": "If present, match VNF instances that were created based on a VNFD identified by one of the vnfdId values listed in this attribute. The attributes \"vnfdIds\" and \"vnfProductsFromProviders\" are alternatives to reference to VNF instances that are based on certain VNFDs in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n", "type": "array", "items": { "description": "An identifier with the intention of being globally unique.\n", "type": "string" } }, "vnfProductsFromProviders": { "description": "If present, match VNF instances that belong to VNF products from certain providers. The attributes \"vnfdIds\" and \"vnfProductsFromProviders\" are alternatives to reference to VNF instances that are based on certain VNFDs in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n", "type": "array", "items": { "type": "object", "required": [ "vnfProvider" ], "properties": { "vnfProvider": { "description": "Name of the VNF provider to match.\n", "type": "string" }, "vnfProducts": { "description": "If present, match VNF instances that belong to VNF products with certain product names, from one particular provider.\n", "type": "array", "items": { "type": "object", "required": [ "vnfProductName" ], "properties": { "vnfProductName": { "description": "Name of the VNF product to match.\n", "type": "string" }, "versions": { "description": "If present, match VNF instances that belong to VNF products with certain versions and a certain product name, from one particular provider.\n", "type": "array", "items": { "type": "object", "required": [ "vnfSoftwareVersion" ], "properties": { "vnfSoftwareVersion": { "description": "A version.\n", "type": "string" }, "vnfdVersions": { "description": "If present, match VNF instances that belong to VNF products with certain VNFD versions, a certain software version and a certain product name, from one particular provider.\n", "type": "array", "items": { "description": "A version.\n", "type": "string" } } } } } } } } } } }, "vnfInstanceIds": { "description": "If present, match VNF instances with an instance identifier listed in this attribute. The attributes \"vnfInstanceIds\" and \"vnfInstanceNames\" are alternatives to reference to particular VNF Instances in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n", "type": "array", "items": { "description": "An identifier with the intention of being globally unique.\n", "type": "string" } }, "vnfInstanceNames": { "description": "If present, match VNF instances with a VNF Instance Name listed in this attribute. The attributes \"vnfInstanceIds\" and \"vnfInstanceNames\" are alternatives to reference to particular VNF Instances in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n", "type": "array", "items": { "type": "string" } } } }, "notificationTypes": { "description": "Match particular notification types. Permitted values: * ThresholdCrossedNotification * PerformanceInformationAvailableNotification The permitted values of the \"notificationTypes\" attribute are spelled exactly as the names of the notification types to facilitate automated code generation systems.\n", "type": "string", "enum": [ "ThresholdCrossedNotification", "PerformanceInformationAvailableNotification" ] } } }, "callbackUri": { "description": "The URI of the endpoint to send the notification to.\n", "type": "string", "format": "url" }, "_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 the referenced resource.\n", "type": "string", "format": "url" } } } } } } }}
\ No newline at end of file
+{
+ "type": "array",
+ "items": {
+ "description": "This type represents a subscription.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "callbackUri",
+ "_links"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "filter": {
+ "description": "This type represents a filter that can be used to subscribe for notifications related to performance management events.\n",
+ "type": "object",
+ "properties": {
+ "vnfInstanceSubscriptionFilter": {
+ "description": "This type represents subscription filter criteria to match VNF instances.\n",
+ "type": "object",
+ "properties": {
+ "vnfdIds": {
+ "description": "If present, match VNF instances that were created based on a VNFD identified by one of the vnfdId values listed in this attribute. The attributes \"vnfdIds\" and \"vnfProductsFromProviders\" are alternatives to reference to VNF instances that are based on certain VNFDs in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ },
+ "vnfProductsFromProviders": {
+ "description": "If present, match VNF instances that belong to VNF products from certain providers. The attributes \"vnfdIds\" and \"vnfProductsFromProviders\" are alternatives to reference to VNF instances that are based on certain VNFDs in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": [
+ "vnfProvider"
+ ],
+ "properties": {
+ "vnfProvider": {
+ "description": "Name of the VNF provider to match.\n",
+ "type": "string"
+ },
+ "vnfProducts": {
+ "description": "If present, match VNF instances that belong to VNF products with certain product names, from one particular provider.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": [
+ "vnfProductName"
+ ],
+ "properties": {
+ "vnfProductName": {
+ "description": "Name of the VNF product to match.\n",
+ "type": "string"
+ },
+ "versions": {
+ "description": "If present, match VNF instances that belong to VNF products with certain versions and a certain product name, from one particular provider.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": [
+ "vnfSoftwareVersion"
+ ],
+ "properties": {
+ "vnfSoftwareVersion": {
+ "description": "A version.\n",
+ "type": "string"
+ },
+ "vnfdVersions": {
+ "description": "If present, match VNF instances that belong to VNF products with certain VNFD versions, a certain software version and a certain product name, from one particular provider.\n",
+ "type": "array",
+ "items": {
+ "description": "A version.\n",
+ "type": "string"
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ },
+ "vnfInstanceIds": {
+ "description": "If present, match VNF instances with an instance identifier listed in this attribute. The attributes \"vnfInstanceIds\" and \"vnfInstanceNames\" are alternatives to reference to particular VNF Instances in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ },
+ "vnfInstanceNames": {
+ "description": "If present, match VNF instances with a VNF Instance Name listed in this attribute. The attributes \"vnfInstanceIds\" and \"vnfInstanceNames\" are alternatives to reference to particular VNF Instances in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n",
+ "type": "array",
+ "items": {
+ "type": "string"
+ }
+ }
+ }
+ },
+ "notificationTypes": {
+ "description": "Match particular notification types. Permitted values: * ThresholdCrossedNotification * PerformanceInformationAvailableNotification The permitted values of the \"notificationTypes\" attribute are spelled exactly as the names of the notification types to facilitate automated code generation systems.\n",
+ "type": "string",
+ "enum": [
+ "ThresholdCrossedNotification",
+ "PerformanceInformationAvailableNotification"
+ ]
+ }
+ }
+ },
+ "callbackUri": {
+ "description": "The URI of the endpoint to send the notification to.\n",
+ "type": "string",
+ "format": "url"
+ },
+ "_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 the referenced resource.\n",
+ "type": "string",
+ "format": "url"
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+}
\ No newline at end of file
diff --git a/SOL002/VNFPerformanceManagement-API/schemas/Threshold.schema.json b/SOL002/VNFPerformanceManagement-API/schemas/Threshold.schema.json
index 938d1991966625c219944ac645f0f2940614846d..53ec1c1b475e8b161cb4a8d7103e81e210913c53 100644
--- a/SOL002/VNFPerformanceManagement-API/schemas/Threshold.schema.json
+++ b/SOL002/VNFPerformanceManagement-API/schemas/Threshold.schema.json
@@ -31,7 +31,7 @@
}
},
"criteria": {
- "description": "This type represents criteria that define a threshold.\n",
+ "description": "This type represents criteria that define a threshold.\nNOTE 1:\tIn the present document, simple thresholds are defined. The definition of additional threshold types is left for \n future specification.\nNOTE 2:\tThe hysteresis is defined to prevent storms of threshold crossing notifications. When processing a request to create \n a threshold, implementations should enforce a suitable minimum value for this attribute (e.g. override the value or \n reject the request). \n",
"type": "object",
"required": [
"performanceMetric",
@@ -43,7 +43,7 @@
"type": "string"
},
"thresholdType": {
- "description": "Type of threshold. This attribute determines which other attributes are present in the data structure. Permitted values: * SIMPLE: Single-valued static threshold In the present document, simple thresholds are defined. The definition of additional threshold types is left for future specification.\n",
+ "description": "Type of threshold. This attribute determines which other attributes are present in the data structure.\nPermitted values: -\tSIMPLE: Single-valued static threshold. See note 1.\n",
"type": "string",
"enum": [
"SIMPLE"
@@ -63,7 +63,7 @@
"format": "float"
},
"hysteresis": {
- "description": "The hysteresis of the threshold. Shall be represented as a non-negative floating point number. A notification with crossing direction \"UP\" will be generated if the measured value reaches or exceeds \"thresholdValue\" + \"hysteresis\". A notification with crossing direction \"DOWN\" will be generated if the measured value reaches or undercuts \"thresholdValue\" - \"hysteresis\". The hysteresis is defined to prevent storms of threshold crossing notifications. When processing a request to create a threshold, implementations should enforce a suitable minimum value for this attribute (e.g. override the value or reject the request).\n",
+ "description": "The hysteresis of the threshold. Shall be represented as a non-negative floating point number.\nA notification with crossing direction \"UP\" will be generated if the measured value reaches or exceeds \"thresholdValue\" + \"hysteresis\". A notification with crossing direction \"DOWN\" will be generated if the measured value reaches or undercuts \"thresholdValue\" - \"hysteresis\". See note 2.\n",
"type": "number",
"minimum": 0,
"maximum": 1024,
diff --git a/SOL002/VNFPerformanceManagement-API/schemas/ThresholdModifications.json b/SOL002/VNFPerformanceManagement-API/schemas/ThresholdModifications.json
index 995cee3517b75439118025ed7746ffd7027989e3..14053751fed164339350ed1a26a71b05e7d41c1c 100644
--- a/SOL002/VNFPerformanceManagement-API/schemas/ThresholdModifications.json
+++ b/SOL002/VNFPerformanceManagement-API/schemas/ThresholdModifications.json
@@ -1,62 +1,75 @@
- {
- "description": "This type represents modifications to a threshold. It shall comply with the provisions defined in table 6.5.2.11-1.\n",
- "type": "object",
- "properties": {
- "callbackUri": {
- "description": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- },
- "authentication": {
- "type": "object",
- "required": [
- "authType"
- ],
- "properties": {
- "authType": {
- "description": "Defines the types of Authentication / Authorization which the API consumer is willing to accept when receiving a notification. Permitted values: * BASIC: In every HTTP request to the notification endpoint, use\n HTTP Basic authentication with the client credentials. \n* OAUTH2_CLIENT_CREDENTIALS: In every HTTP request to the\n notification endpoint, use an OAuth 2.0 Bearer token, obtained\n using the client credentials grant type.\n* TLS_CERT: Every HTTP request to the notification endpoint is sent\n over a mutually authenticated TLS session, i.e. not only the\n server is authenticated, but also the client is authenticated\n during the TLS tunnel setup.\n",
- "type": "array",
- "items": {
- "type": "string",
- "enum": [
- "BASIC",
- "OAUTH2_CLIENT_CREDENTIALS",
- "TLS_CERT"
- ]
- }
- },
- "paramsBasic": {
- "description": "Parameters for authentication/authorization using BASIC. Shall be present if authType is \"BASIC\" and the contained information has not been provisioned out of band. Shall be absent otherwise.\n",
- "type": "object",
- "properties": {
- "userName": {
- "description": "Username to be used in HTTP Basic authentication. Shall be present if it has not been provisioned out of band.\n",
- "type": "string"
- },
- "password": {
- "description": "Password to be used in HTTP Basic authentication. Shall be present if it has not been provisioned out of band.\n",
- "type": "string"
- }
+{
+ "description": "This type represents modifications to a threshold.\nNOTE:\tAt least one of the attributes defined in this type shall be present in request bodies.\n",
+ "type": "object",
+ "oneOf": [
+ {
+ "required": [
+ "callbackUri"
+ ]
+ },
+ {
+ "required": [
+ "authentication"
+ ]
+ }
+ ],
+ "properties": {
+ "callbackUri": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ },
+ "authentication": {
+ "description": "* NOTE: The clientId and clientPassword passed in a subscription shall not be the same as the clientId and\n clientPassword that are used to obtain authorization for API requests. Client credentials may differ between\n subscriptions. The value of clientPassword should be generated by a random process\n",
+ "type": "object",
+ "required": [
+ "authType"
+ ],
+ "properties": {
+ "authType": {
+ "description": "Defines the types of Authentication / Authorization which the API consumer is willing to accept when receiving a notification. Permitted values: * BASIC: In every HTTP request to the notification endpoint, use\n HTTP Basic authentication with the client credentials. \n* OAUTH2_CLIENT_CREDENTIALS: In every HTTP request to the\n notification endpoint, use an OAuth 2.0 Bearer token, obtained\n using the client credentials grant type.\n* TLS_CERT: Every HTTP request to the notification endpoint is sent\n over a mutually authenticated TLS session, i.e. not only the\n server is authenticated, but also the client is authenticated\n during the TLS tunnel setup.\n",
+ "type": "array",
+ "items": {
+ "type": "string",
+ "enum": [
+ "BASIC",
+ "OAUTH2_CLIENT_CREDENTIALS",
+ "TLS_CERT"
+ ]
+ }
+ },
+ "paramsBasic": {
+ "description": "Parameters for authentication/authorization using BASIC. Shall be present if authType is \"BASIC\" and the contained information has not been provisioned out of band. Shall be absent otherwise.\n",
+ "type": "object",
+ "properties": {
+ "userName": {
+ "description": "Username to be used in HTTP Basic authentication. Shall be present if it has not been provisioned out of band.\n",
+ "type": "string"
+ },
+ "password": {
+ "description": "Password to be used in HTTP Basic authentication. Shall be present if it has not been provisioned out of band.\n",
+ "type": "string"
}
- },
- "paramsOauth2ClientCredentials": {
- "description": "Parameters for authentication/authorization using OAUTH2_CLIENT_CREDENTIALS. Shall be present if authType is \"OAUTH2_CLIENT_CREDENTIALS\" and the contained information has not been provisioned out of band. Shall be absent otherwise.\n",
- "type": "object",
- "properties": {
- "clientId": {
- "description": "Client identifier to be used in the access token request of the OAuth 2.0 client credentials grant type. Shall be present if it has not been provisioned out of band. The clientId and clientPassword passed in a subscription shall not be the same as the clientId and clientPassword that are used to obtain authorization for API requests. Client credentials may differ between subscriptions. The value of clientPassword should be generated by a random process.\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 be present if it has not been provisioned out of band. The clientId and clientPassword passed in a subscription shall not be the same as the clientId and clientPassword that are used to obtain authorization for API requests. Client credentials may differ between subscriptions. The value of clientPassword should be generated by a random process.\n",
- "type": "string"
- },
- "tokenEndpoint": {
- "description": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- }
+ }
+ },
+ "paramsOauth2ClientCredentials": {
+ "description": "Parameters for authentication/authorization using OAUTH2_CLIENT_CREDENTIALS. Shall be present if authType is \"OAUTH2_CLIENT_CREDENTIALS\" and the contained information has not been provisioned out of band. Shall be absent otherwise.\n",
+ "type": "object",
+ "properties": {
+ "clientId": {
+ "description": "Client identifier to be used in the access token request of the OAuth 2.0 client credentials grant type. Shall be present if it has not been provisioned out of band. See note.\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 be present if it has not been provisioned out of band. See note.\n",
+ "type": "string"
+ },
+ "tokenEndpoint": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
}
}
}
}
}
- }
\ No newline at end of file
+ }
+}
\ No newline at end of file
diff --git a/SOL002/VNFPerformanceManagement-API/schemas/Thresholds.schema.json b/SOL002/VNFPerformanceManagement-API/schemas/Thresholds.schema.json
index 74bddb4bc413c11914ac716a58d32ccf1495b41c..1317135dd988c8c70052ecc013718f8ebbaf41e1 100644
--- a/SOL002/VNFPerformanceManagement-API/schemas/Thresholds.schema.json
+++ b/SOL002/VNFPerformanceManagement-API/schemas/Thresholds.schema.json
@@ -1,120 +1,119 @@
{
- "type": "array",
- "items":
- {
- "description": "This type represents a threshold.\n",
- "type": "object",
- "required": [
- "id",
- "objectType",
- "objectInstanceId",
- "criteria",
- "callbackUri",
- "_links"
- ],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "objectType": {
- "description": "Type of the measured object. The applicable measured object type for a measurement is defined in clause 7.2 of ETSI GS NFV-IFA 027.\n",
- "type": "string"
- },
- "objectInstanceId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "subObjectInstanceIds": {
- "description": "Identifiers of the sub-object instances of the measured object instance associated with the threshold. May be present if a sub-object is defined in clause 6.2 of ETSI GS NFV-IFA 027 for the related measurement type. If this attribute is absent and a sub-object is defined in clause 6.2 of ETSI GS NFV-IFA 027 for the related measured object type, measurements will be taken for all sub-object instances of the measured object instance.\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": "array",
+ "items": {
+ "description": "This type represents a threshold.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "objectType",
+ "objectInstanceId",
+ "criteria",
+ "callbackUri",
+ "_links"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
"type": "string"
- }
- },
- "criteria": {
- "description": "This type represents criteria that define a threshold.\n",
- "type": "object",
- "required": [
- "performanceMetric",
- "thresholdType"
- ],
- "properties": {
- "performanceMetric": {
- "description": "Defines the performance metric associated with the threshold. Valid values are specified as \"Measurement Name\" values in clause 7.2 of ETSI GS NFV-IFA 027.\n",
+ },
+ "objectType": {
+ "description": "Type of the measured object. The applicable measured object type for a measurement is defined in clause 7.2 of ETSI GS NFV-IFA 027.\n",
+ "type": "string"
+ },
+ "objectInstanceId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "subObjectInstanceIds": {
+ "description": "Identifiers of the sub-object instances of the measured object instance associated with the threshold. May be present if a sub-object is defined in clause 6.2 of ETSI GS NFV-IFA 027 for the related measurement type. If this attribute is absent and a sub-object is defined in clause 6.2 of ETSI GS NFV-IFA 027 for the related measured object type, measurements will be taken for all sub-object instances of the measured object instance.\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"
- },
- "thresholdType": {
- "description": "Type of threshold. This attribute determines which other attributes are present in the data structure. Permitted values: * SIMPLE: Single-valued static threshold In the present document, simple thresholds are defined. The definition of additional threshold types is left for future specification.\n",
- "type": "string",
- "enum": [
- "SIMPLE"
- ]
- },
- "simpleThresholdDetails": {
- "description": "Details of a simple threshold. Shall be present if thresholdType=\"SIMPLE\".\n",
- "type": "object",
- "required": [
- "thresholdValue",
- "hysteresis"
- ],
- "properties": {
- "thresholdValue": {
- "description": "The threshold value. Shall be represented as a floating point number.\n",
- "type": "number",
- "format": "float"
- },
- "hysteresis": {
- "description": "The hysteresis of the threshold. Shall be represented as a non-negative floating point number. A notification with crossing direction \"UP\" will be generated if the measured value reaches or exceeds \"thresholdValue\" + \"hysteresis\". A notification with crossing direction \"DOWN\" will be generated if the measured value reaches or undercuts \"thresholdValue\" - \"hysteresis\". The hysteresis is defined to prevent storms of threshold crossing notifications. When processing a request to create a threshold, implementations should enforce a suitable minimum value for this attribute (e.g. override the value or reject the request).\n",
- "type": "number",
- "minimum": 0,
- "maximum": 1024,
- "format": "float"
+ }
+ },
+ "criteria": {
+ "description": "This type represents criteria that define a threshold.\nNOTE 1:\tIn the present document, simple thresholds are defined. The definition of additional threshold types is left for \n future specification.\nNOTE 2:\tThe hysteresis is defined to prevent storms of threshold crossing notifications. When processing a request to create \n a threshold, implementations should enforce a suitable minimum value for this attribute (e.g. override the value or \n reject the request). \n",
+ "type": "object",
+ "required": [
+ "performanceMetric",
+ "thresholdType"
+ ],
+ "properties": {
+ "performanceMetric": {
+ "description": "Defines the performance metric associated with the threshold. Valid values are specified as \"Measurement Name\" values in clause 7.2 of ETSI GS NFV-IFA 027.\n",
+ "type": "string"
+ },
+ "thresholdType": {
+ "description": "Type of threshold. This attribute determines which other attributes are present in the data structure.\nPermitted values: -\tSIMPLE: Single-valued static threshold. See note 1.\n",
+ "type": "string",
+ "enum": [
+ "SIMPLE"
+ ]
+ },
+ "simpleThresholdDetails": {
+ "description": "Details of a simple threshold. Shall be present if thresholdType=\"SIMPLE\".\n",
+ "type": "object",
+ "required": [
+ "thresholdValue",
+ "hysteresis"
+ ],
+ "properties": {
+ "thresholdValue": {
+ "description": "The threshold value. Shall be represented as a floating point number.\n",
+ "type": "number",
+ "format": "float"
+ },
+ "hysteresis": {
+ "description": "The hysteresis of the threshold. Shall be represented as a non-negative floating point number.\nA notification with crossing direction \"UP\" will be generated if the measured value reaches or exceeds \"thresholdValue\" + \"hysteresis\". A notification with crossing direction \"DOWN\" will be generated if the measured value reaches or undercuts \"thresholdValue\" - \"hysteresis\". See note 2.\n",
+ "type": "number",
+ "minimum": 0,
+ "maximum": 1024,
+ "format": "float"
+ }
}
}
}
- }
- },
- "callbackUri": {
- "description": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- },
- "_links": {
- "description": "Links for this resource.\n",
- "type": "object",
- "required": [
- "self"
- ],
- "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"
+ },
+ "callbackUri": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ },
+ "_links": {
+ "description": "Links for this resource.\n",
+ "type": "object",
+ "required": [
+ "self"
+ ],
+ "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"
+ }
}
- }
- },
- "object": {
- "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"
+ },
+ "object": {
+ "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"
+ }
}
}
}
}
}
}
- }
}
\ No newline at end of file
diff --git a/SOL002/VNFPerformanceManagement-API/schemas/criteria.schema.json b/SOL002/VNFPerformanceManagement-API/schemas/criteria.schema.json
index 319d15f53d4d49980a3c4c451bc82efd983abf36..7dc6d89684a269ccfcf11cff97869a6865d4a6ef 100644
--- a/SOL002/VNFPerformanceManagement-API/schemas/criteria.schema.json
+++ b/SOL002/VNFPerformanceManagement-API/schemas/criteria.schema.json
@@ -1,32 +1,39 @@
{
- "description": "Criteria of the collection of performance information.\n",
+ "description": "This type represents collection criteria for PM jobs.\nNOTE 1:\tAt the end of each reportingPeriod, the API producer will inform the API consumer about availability of the \n performance data collected for each completed collection period during this reportingPeriod. \n The reportingPeriod should be equal to or a multiple of the collectionPeriod. In the latter case, the performance \n data for the collection periods within one reporting period are reported together.\nNOTE 2:\tIn particular when choosing short collection and reporting periods, the number of PM jobs that can be supported \n depends on the capability of the producing entity.\n",
"type": "object",
- "required": ["collectionPeriod", "reportingPeriod"],
+ "required": [
+ "collectionPeriod",
+ "reportingPeriod"
+ ],
"properties": {
"performanceMetric": {
- "description": "This defines the types of performance metrics for the specified object instances, as specified in ETSI GS NFV-IFA 027). At least one of the two attributes (performance metric or group) shall be present.\n",
+ "description": "This defines the types of performance metrics for the specified object instances. Valid values are specified as \"Measurement Name\" values in clause 7.2 of ETSI GS NFV-IFA 027. At least one of the two attributes (performance metric or group) shall be present.\n",
"type": "array",
"items": {
"type": "string"
}
},
"performanceMetricGroup": {
- "description": "Group of performance metrics. A metric group is a pre-defined list of metrics, known to the producer that it can decompose to individual metrics. At least one of the two attributes (performance metric or group) shall be present.\n",
+ "description": "Group of performance metrics. A metric group is a pre-defined list of metrics, known to the API producer that it can decompose to individual metrics. Valid values are specified as \"Measurement Group\" values in clause 7.2 of ETSI GS NFV-IFA 027. At least one of the two attributes (performance metric or group) shall be present.\n",
"type": "array",
"items": {
"type": "string"
}
},
"collectionPeriod": {
- "description": "Specifies the periodicity at which the producer will collect performance information. The unit shall be seconds. At the end of each reportingPeriod, the producer will inform the consumer about availability of the performance data collected for each completed collection period during this reportingPeriod. The reportingPeriod should be equal to or a multiple of the collectionPeriod. In the latter case, the performance data for the collection periods within one reporting period are reported together.\n",
- "type": "integer"
+ "description": "Specifies the periodicity at which the API producer will collect performance information. The unit shall be seconds. See notes 1 and 2.\n",
+ "type": "integer",
+ "minimum": 0,
+ "maximum": 1024
},
"reportingPeriod": {
- "description": "Specifies the periodicity at which the producer will report to the consumer. about performance information. The unit shall be seconds. At the end of each reportingPeriod, the producer will inform the consumer about availability of the performance data collected for each completed collection period during this reportingPeriod. The reportingPeriod should be equal to or a multiple of the collectionPeriod. In the latter case, the performance data for the collection periods within one reporting period are reported together.\n",
- "type": "integer"
+ "description": "Specifies the periodicity at which the API producer will report to the API consumer about performance information. The unit shall be seconds. See notes 1 and 2.\n",
+ "type": "integer",
+ "minimum": 0,
+ "maximum": 1024
},
"reportingBoundary": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
"type": "string",
"format": "date-time"
}
diff --git a/SOL002/VNFPerformanceManagement-API/schemas/links.schema.json b/SOL002/VNFPerformanceManagement-API/schemas/links.schema.json
index ef262a8c875b5c00bf32d4fd6f279cc4d5965bc9..bfdddc1a3c739352434a12144feac3a03352dd5f 100644
--- a/SOL002/VNFPerformanceManagement-API/schemas/links.schema.json
+++ b/SOL002/VNFPerformanceManagement-API/schemas/links.schema.json
@@ -1,32 +1,36 @@
{
"description": "Links for this resource.\n",
"type": "object",
- "required": ["self"],
+ "required": [
+ "self"
+ ],
"properties": {
"self": {
- "description": "This type represents a link to a resource.\n",
+ "description": "This type represents a link to a resource using an absolute URI.\n",
"type": "object",
- "required": ["href"],
+ "required": [
+ "href"
+ ],
"properties": {
"href": {
- "description": "URI of the referenced resource.\n",
- "type": "string",
- "format": "url"
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
}
}
},
"objects": {
- "description": "Links to resources representing the VNF instances for which performance information is collected. Shall be present if the VNF instance information is accessible as a resource.\n",
+ "description": "Links to resources representing the measure object instances for which performance information is collected. Shall be present if the measured object instance information is accessible as a resource.\n",
"type": "array",
"items": {
- "description": "This type represents a link to a resource.\n",
+ "description": "This type represents a link to a resource using an absolute URI.\n",
"type": "object",
- "required": ["href"],
+ "required": [
+ "href"
+ ],
"properties": {
"href": {
- "description": "URI of the referenced resource.\n",
- "type": "string",
- "format": "url"
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
}
}
}
diff --git a/SOL002/VNFPerformanceManagement-API/schemas/reports.schema.json b/SOL002/VNFPerformanceManagement-API/schemas/reports.schema.json
index 834ded68723d9a72b3be565e72b71d5ef650e0cc..97347a437ae6b3329e99765b019e7f6ce9c3f47f 100644
--- a/SOL002/VNFPerformanceManagement-API/schemas/reports.schema.json
+++ b/SOL002/VNFPerformanceManagement-API/schemas/reports.schema.json
@@ -1,26 +1,31 @@
{
"description": "Information about available reports collected by this PM job.\n",
"type": "object",
- "required": ["href", "readyTime"],
+ "required": [
+ "href",
+ "readyTime"
+ ],
"properties": {
"href": {
- "description": "The Uri where the report can be obtained.\n",
+ "description": "The URI where the report can be obtained.\n",
"type": "string",
"format": "url"
},
"readyTime": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
"type": "string",
"format": "date-time"
},
"expiryTime": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
"type": "string",
"format": "date-time"
},
"fileSize": {
"description": "The size of the report file in bytes, if known.\n",
- "type": "integer"
+ "type": "integer",
+ "minimum": 0,
+ "maximum": 1024
}
}
}
\ No newline at end of file
diff --git a/SOL002/VNFPerformanceManagementNotification-API/Notifications.robot b/SOL002/VNFPerformanceManagementNotification-API/Notifications.robot
index a285e5ee080808a6fa5ea76310185a7995bf3a15..b2f11b8dbc0c94bda4a61b09670eac2841e1cc29 100644
--- a/SOL002/VNFPerformanceManagementNotification-API/Notifications.robot
+++ b/SOL002/VNFPerformanceManagementNotification-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] v3.6.1
+ ... Reference: Clause 6.4.9.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.9.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL002/VNFPerformanceManagementNotification-API/schemas/PerformanceInformationAvailableNotification.schema.json b/SOL002/VNFPerformanceManagementNotification-API/schemas/PerformanceInformationAvailableNotification.schema.json
index 512c26401bdc3de7df1a871ea51c50d0a72f2c51..603a16a099beadb7afb4a74fb24d377f073fb58e 100644
--- a/SOL002/VNFPerformanceManagementNotification-API/schemas/PerformanceInformationAvailableNotification.schema.json
+++ b/SOL002/VNFPerformanceManagementNotification-API/schemas/PerformanceInformationAvailableNotification.schema.json
@@ -40,7 +40,7 @@
"type": "string"
},
"subObjectInstanceIds": {
- "description": "Identifiers of the sub-object instances of the measured object instance for which the measurements have been taken. Shall be present if the related PM job has been set up to measure only a subset of all sub-object instances of the measured object instance and a sub-object is defined in clause\n 6.2 of ETSI GS NFV-IFA 027 for the related measured object type.\nShall be absent otherwise.\n",
+ "description": "Identifiers of the sub-object instances of the measured object instance for which the measurements have been taken. Shall be present if the related PM job has been set up to measure only a subset of all sub-object instances of the measured object instance and a sub-object is defined in clause 6.2 of ETSI GS NFV-IFA 027 for the related measured object type. Shall be absent otherwise.\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",
diff --git a/SOL002/VNFPerformanceManagementNotification-API/schemas/ProblemDetails.schema.json b/SOL002/VNFPerformanceManagementNotification-API/schemas/ProblemDetails.schema.json
index 2af3ef9b3f8c0e1dc6bfa39a818ba45e63ca223c..a4c007a5c1501eaf4ae57b5973cda6ef1d4bbea5 100644
--- a/SOL002/VNFPerformanceManagementNotification-API/schemas/ProblemDetails.schema.json
+++ b/SOL002/VNFPerformanceManagementNotification-API/schemas/ProblemDetails.schema.json
@@ -1 +1,32 @@
-{ "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
+{
+ "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/SOL002/VNFPerformanceManagementNotification-API/schemas/ThresholdCrossedNotification.schema.json b/SOL002/VNFPerformanceManagementNotification-API/schemas/ThresholdCrossedNotification.schema.json
index e5cec2303f1bcfcfdb9df5affc9fc0767cd8a2c8..6db468d08d48c1c6c53dec2de98b9d9306d8cc89 100644
--- a/SOL002/VNFPerformanceManagementNotification-API/schemas/ThresholdCrossedNotification.schema.json
+++ b/SOL002/VNFPerformanceManagementNotification-API/schemas/ThresholdCrossedNotification.schema.json
@@ -1,113 +1,104 @@
{
- "description": "This type represents a notification that is sent when a threshold has been crossed. The notification shall be triggered by the VNFM when a threshold has been crossed.\n",
- "type": "object",
- "required": [
- "id",
- "notificationType",
- "subscriptionId",
- "timeStamp",
- "thresholdId",
- "crossingDirection",
- "objectInstanceId",
- "performanceMetric",
- "performanceValue",
- "_links"
- ],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "notificationType": {
- "description": "Discriminator for the different notification types. Shall be set to \"ThresholdCrossedNotification\" for this notification type.\n",
- "type": "string",
- "enum": [
- "ThresholdCrossedNotification"
- ]
- },
- "subscriptionId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "timeStamp": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "thresholdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "crossingDirection": {
- "type": "string",
- "enum": [
- "UP",
- "DOWN"
- ]
- },
- "objectInstanceId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "performanceMetric": {
- "description": "Performance metric associated with the threshold.\n",
- "type": "string"
- },
- "performanceValue": {
- "description": "Value of the metric that resulted in threshold crossing. The type of the \"performanceValue\" attribute (i.e. scalar, structure (Object in JSON), or array (of scalars, arrays or structures / Objects)) is assumed to be defined in the external measurement specification (see ETSI GS NFV-IFA 027).\n",
- "type": "object"
- },
- "_links": {
- "description": "Links to resources related to this notification.\n",
- "type": "object",
- "required": [
- "subscription",
- "threshold"
- ],
- "properties": {
- "subscription": {
- "description": "This type represents a link to a resource.\n",
- "type": "object",
- "required": [
- "href"
- ],
- "properties": {
- "href": {
- "description": "URI of the referenced resource.\n",
- "type": "string",
- "format": "url"
- }
+ "description": "This type represents a notification that is sent when a threshold has been crossed.\nNOTE:\tThe timing of sending this notification is determined by the capability of the \n producing entity to evaluate the threshold crossing condition.\n \nThe notification shall be triggered by the VNFM when a threshold has been crossed.\nNOTE:\tThe sub-object allows to structure the measured object, but is not to be confused \n with sub-counters which allow to structure the measurement.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "notificationType",
+ "timeStamp",
+ "thresholdId",
+ "crossingDirection",
+ "objectType",
+ "objectInstanceId",
+ "performanceMetric",
+ "performanceValue",
+ "_links"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "notificationType": {
+ "description": "Discriminator for the different notification types. Shall be set to \"ThresholdCrossedNotification\" for this notification type.\n",
+ "type": "string",
+ "enum": [
+ "ThresholdCrossedNotification"
+ ]
+ },
+ "timeStamp": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "thresholdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "crossingDirection": {
+ "type": "string",
+ "enum": [
+ "UP",
+ "DOWN"
+ ]
+ },
+ "objectType": {
+ "description": "Type of the measured object. The applicable measured object type for a measurement is defined in clause 7.2 of ETSI GS NFV-IFA 027.\n",
+ "type": "string"
+ },
+ "objectInstanceId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "subObjectInstanceId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "performanceMetric": {
+ "description": "Performance metric associated with the threshold. This attribute shall contain the related \"Measurement Name\" value as defined in clause 7.2 of ETSI GS NFV-IFA 027.\n",
+ "type": "string"
+ },
+ "performanceValue": {
+ "description": "Value of the metric that resulted in threshold crossing. The type of this attribute shall correspond to the related \"Measurement Unit\" as defined in clause 7.2 of ETSI GS NFV-IFA 027.\n",
+ "type": "object"
+ },
+ "context": {
+ "description": "This 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"
+ },
+ "_links": {
+ "description": "Links to resources related to this notification.\n",
+ "type": "object",
+ "required": [
+ "threshold"
+ ],
+ "properties": {
+ "objectInstance": {
+ "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": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
}
- },
- "objectInstance": {
- "description": "This type represents a link to a resource.\n",
- "type": "object",
- "required": [
- "href"
- ],
- "properties": {
- "href": {
- "description": "URI of the referenced resource.\n",
- "type": "string",
- "format": "url"
- }
- }
- },
- "threshold": {
- "description": "This type represents a link to a resource.\n",
- "type": "object",
- "required": [
- "href"
- ],
- "properties": {
- "href": {
- "description": "URI of the referenced resource.\n",
- "type": "string",
- "format": "url"
- }
+ }
+ },
+ "threshold": {
+ "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": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
}
}
}
}
}
- }
\ No newline at end of file
+ }
+}
\ No newline at end of file
diff --git a/SOL003/README.md b/SOL003/README.md
index 7d6aaefef6c6460ec0a4661362fae3ecfb34b6a3..94ca3e8233dfa5f30c4e6260ef43d7e08ab25cdd 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 v3.6.1: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/03.06.01_60/gs_nfv-sol003v030601p.pdf
+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
diff --git a/SOL003/VNFFaultManagement-API/Alarms.robot b/SOL003/VNFFaultManagement-API/Alarms.robot
index bcbdca7802cc06e414cd0695b6dd797da20c5d18..628c447215d10c271ca715dd9cf122a74cacf9a1 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] v3.6.1
+ ... Reference: Clause 7.4.2.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.2.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.2.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.2.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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 34a5fc61dff005d138f5986845a49013e2db2238..95c9392e5fd30f7ce190bb6f9e022a8cbe0aa69c 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] v3.5.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFFaultManagement-API/FaultManagement-APIKeyword.robot b/SOL003/VNFFaultManagement-API/FaultManagement-APIKeyword.robot
index dcd00475e83098e22998ed02de80ee6127afe5c8..5fae4b6bb83155fb34dba38b7327930b4b54cd27 100644
--- a/SOL003/VNFFaultManagement-API/FaultManagement-APIKeyword.robot
+++ b/SOL003/VNFFaultManagement-API/FaultManagement-APIKeyword.robot
@@ -61,6 +61,13 @@ Check HTTP Response Header Contains
Should Contain ${response['headers']} ${HEADER_TOCHECK}
Log Header is present
+Check HTTP Response Header Contains ETag and Last-Modified
+ Pass Execution If ${HEADER_TEST_SUPPORTED} == 0 Headers testing not supported. Skipping the Test.
+ Log ${response['headers']}
+ Should Contain ${response['headers']} Etag
+ Should Contain ${response['headers']} Last-Modified
+ Log Etag and Last-Modified Headers are present
+
Check HTTP Response Body Json Schema Is
[Arguments] ${input}
Run Keyword If '${input}' == 'ProblemDetails' Should Contain ${response['headers']['Content-Type']} application/problem+json
diff --git a/SOL003/VNFFaultManagement-API/IndividualAlarm.robot b/SOL003/VNFFaultManagement-API/IndividualAlarm.robot
index 9d3a70191d548d6269ee64dd7a9bd0d9951ebd92..30b8f5be91c4ada8df87ebdb7b3238f6694ead84 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] v3.6.1
+ ... Reference: Clause 7.4.3.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -26,11 +26,12 @@ 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] v3.6.1
+ ... Reference: Clause 7.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
GET Fault Management Individual Alarm
+ Check HTTP Response Header Contains ETag and Last-Modified
Check HTTP Response Status Code Is 200
Check HTTP Response Body Json Schema Is alarm
@@ -39,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] v3.6.1
+ ... Reference: Clause 7.4.3.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -51,11 +52,12 @@ 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] v3.6.1
+ ... Reference: Clause 7.4.3.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
PATCH Fault Management Individual Alarm
+ Check HTTP Response Header Contains ETag and Last-Modified
Check HTTP Response Status Code Is 200
Check HTTP Response Body Json Schema Is alarmModification
@@ -64,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] v3.6.1
+ ... Reference: Clause 7.4.3.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -77,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] v3.6.1
+ ... Reference: Clause 7.4.3.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -91,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] v3.6.1
+ ... Reference: Clause 7.4.3.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -103,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] v3.6.1
+ ... Reference: Clause 7.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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 9814802c6884bd0f4950f88becebdfaaeeb7f7fd..89dfc5b8a31a99d37216776d38c8381e2b1ba9a3 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] v3.6.1
+ ... Reference: Clause 7.4.5.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.5.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.5.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.5.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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 edf84a6b1fc6e56ad17b50251999ebca32c825ab..26e0d3804165c9a79a32bccb939c572664823dd4 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] v3.6.1
+ ... Reference: Clause 7.4.6.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.6.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.6.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFFaultManagement-API/Subscriptions.robot b/SOL003/VNFFaultManagement-API/Subscriptions.robot
index b44f224d32b5a9b7420800363d350b6031658dff..03fcc2eeb8b0dadd82d80641925604158f9d0cf3 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] v3.6.1
+ ... Reference: Clause 7.4.4.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.4.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.4.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... RReference: Clause 7.4.4.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.4.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.4.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability:
... Post-Conditions:
@@ -297,7 +297,7 @@ POST Create a new Subscription - Unprocessable Entity
... 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.
... re-conditions: none
- ... Reference: Clause 7.4.5.3.1 - ETSI GS NFV-SOL 003 [1] v3.6.1
+ ... Reference: Clause 7.4.5.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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 29207a1533619f98d9f36b496e33d251674cb097..af645c81e24b10a3f70626de83e8cd480933c29f 100644
--- a/SOL003/VNFFaultManagement-API/environment/variables.txt
+++ b/SOL003/VNFFaultManagement-API/environment/variables.txt
@@ -39,6 +39,7 @@ ${eventType} COMMUNICATIONS_ALARM
${perceivedSeverity} CRITICAL
${probableCause} ""
+${HEADER_TEST_SUPPORTED} 0
${response} {}
diff --git a/SOL003/VNFFaultManagement-API/jsons/AlarmClearedNotification.json b/SOL003/VNFFaultManagement-API/jsons/AlarmClearedNotification.json
index f8a50fb3b45af0e487e475184ee1f78048dd8bf7..3ac4bfcce32f1fd61705b7f6d66c10f806b82fbf 100644
--- a/SOL003/VNFFaultManagement-API/jsons/AlarmClearedNotification.json
+++ b/SOL003/VNFFaultManagement-API/jsons/AlarmClearedNotification.json
@@ -4,7 +4,7 @@
"subscriptionId":"{subscriptionId}",
"timeStamp":"",
"alarmId":"{alarmId}",
- "alarmCleareTime":"",
+ "alarmClearedTime":"",
"_links":{{
"subscription":"",
"alarm":""
diff --git a/SOL003/VNFFaultManagement-API/jsons/AlarmNotification.json b/SOL003/VNFFaultManagement-API/jsons/AlarmNotification.json
index 2a8e86425bac0e428e5eabff99767ed67665121d..6cfc9693ec5807c9e05fb103bf8b4229fc783edb 100644
--- a/SOL003/VNFFaultManagement-API/jsons/AlarmNotification.json
+++ b/SOL003/VNFFaultManagement-API/jsons/AlarmNotification.json
@@ -5,7 +5,14 @@
"timeStamp":"",
"alarm":{{
"id":"",
- "managedObjectId":""
+ "managedObjectId":"",
+ "alarmRaisedTime":"",
+ "ackState":"",
+ "perceivedSeverity":"",
+ "eventTime":"",
+ "eventType":"",
+ "probableCause":"",
+ "isRootCause":""
}},
"_links":{{
"subscription":""
diff --git a/SOL003/VNFFaultManagement-API/schemas/AlarmModification.schema.json b/SOL003/VNFFaultManagement-API/schemas/AlarmModification.schema.json
index 7bab37286b1cd780be2042a2e37460a89dd57a5d..b5e4fa9c24e5d627b02fdc6f2ad01d8ba46dc0bc 100644
--- a/SOL003/VNFFaultManagement-API/schemas/AlarmModification.schema.json
+++ b/SOL003/VNFFaultManagement-API/schemas/AlarmModification.schema.json
@@ -7,11 +7,9 @@
],
"properties": {
"ackState": {
- "description": "New value of the \"ackState\" attribute in \"Alarm\". Permitted values: * ACKNOWLEDGED\n",
+ "description": "New value of the \"ackState\" attribute in \"Alarm\". Permitted values: * ACKNOWLEDGED * UNACKNOWLEDGED\n",
"type": "string",
- "enum": [
- "ACKNOWLEDGED"
- ]
+ "enum": ["ACKNOWLEDGED", "UNACKNOWLEDGED"]
}
}
}
diff --git a/SOL003/VNFFaultManagement-API/schemas/Alarms.schema.json b/SOL003/VNFFaultManagement-API/schemas/Alarms.schema.json
index 95cfbe78ba051e799a28f6e03aee9fa9e87f88bf..cddec9e6f8c30de68c816b572e40b495329a5bc7 100644
--- a/SOL003/VNFFaultManagement-API/schemas/Alarms.schema.json
+++ b/SOL003/VNFFaultManagement-API/schemas/Alarms.schema.json
@@ -3,12 +3,11 @@
"items": {
"type": "object",
"items": {
- "description": "The alarm data type encapsulates information about an alarm.\n",
+ "description": "The alarm data type encapsulates information about an alarm. \nNOTE 1: For an alarm about upcoming impact due to NFVI operation and maintenance (i.e. the attribute \n \"faultType\" has the value \"NFVI_OAM_VIRTUALISED_RESOURCE_STATE_CHANGE\"), the attribute \n \"rootCauseFaultyResource\" indicates a resource to be impacted. Further information on the upcoming\n impact (e.g. group of impacted resources, time of impact) is provided in the attribute \"faultDetails\".\nNOTE 2: When alarms are due to upcoming NFVI operation and maintenance (i.e. the attribute \"faultType\" has the \n value \"NFVI_OAM_VIRTUALISED_RESOURCE_STATE_CHANGE\"), the attribute \"faultDetails\" shall include \n information about the anticipated time of the maintenance. See provisions under the present table.\n\nIf the attribute \"faultType\" has the value \"NFVI_OAM_VIRTUALISED_RESOURCE_STATE_CHANGE\", the following provisions apply for the values of the attribute \"faultDetails\" related to changes in the state of virtualised resources:\n - One of the entries in the array shall provide information about the anticipated time of maintenance in the \n following format: \"anticipatedTime=$time\", wherein \"$time\" shall be formatted as a \"DateTime\", as specified \n in ETSI GS NFV-SOL 013 [8]. \n - One of the entries in the array shall provide identification information about the affinity/anti-affinity\n group defined in the VNFD that is associated to the affected virtualised resource indicated by \n \"rootCauseFaultyResource\" in the following format: \"affinityOrAntiAffinityGroupId=$group\", wherein \n \"$group\" shall be equal to the \"affinityOrAntiAffinityGroupId\" value in the corresponding \"VduProfile\" (for a \n VNFC/COMPUTE affected resource) or \"VirtualLinkProfile\" for a VL/NETWORK affected resource) in the \n VNFD, which is mapped by the VNFM to the virtualised resource group identifier in the virtualised resource \n change notification received by the VNFM from the VIM.\n",
"type": "object",
"required": [
"id",
"managedObjectId",
- "rootCauseFaultyResource",
"alarmRaisedTime",
"ackState",
"perceivedSeverity",
@@ -30,18 +29,12 @@
"rootCauseFaultyResource": {
"description": "This type represents the faulty virtual resources that have a negative impact on a VNF.\n",
"type": "object",
- "required": [
- "faultyResource",
- "faultyResourceType"
- ],
+ "required": ["faultyResource", "faultyResourceType"],
"properties": {
"faultyResource": {
- "required": [
- "vimConnectionId",
- "resourceId"
- ],
+ "required": ["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",
+ "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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
@@ -52,11 +45,33 @@
"type": "string"
},
"resourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
"type": "string"
},
"vimLevelResourceType": {
- "description": "Type of the resource in the scope of the VIM or the resource provider.\n",
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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"
}
}
@@ -64,38 +79,37 @@
"faultyResourceType": {
"description": "The enumeration FaultyResourceType represents those types of faulty resource.\n",
"type": "string",
- "enum": [
- "COMPUTE",
- "STORAGE",
- "NETWORK"
- ]
+ "enum": ["COMPUTE", "STORAGE", "NETWORK"]
}
}
},
"alarmRaisedTime": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
"type": "string",
"format": "date-time"
},
"alarmChangedTime": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
"type": "string",
"format": "date-time"
},
"alarmClearedTime": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "alarmAcknowledgedTime": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
"type": "string",
"format": "date-time"
},
"ackState": {
- "description": "Acknowledgement state of the alarm. Permitted values: * UNACKNOWLEDGED * ACKNOWLEDGED.\n",
+ "description": "Acknowledgement state of the alarm. Permitted values: * UNACKNOWLEDGED * ACKNOWLEDGED.\n",
"type": "string",
- "enum": [
- "UNACKNOWLEDGED",
- "ACKNOWLEDGED"
- ]
+ "enum": ["UNACKNOWLEDGED", "ACKNOWLEDGED"]
},
"perceivedSeverity": {
+ "description": "Indicates the relative level of urgency for operator attention. * CRITICAL: The Critical severity level indicates that a service\n affecting condition has occurred and an immediate corrective action\n is required. Such a severity can be reported, for example, when a\n managed object becomes totally out of service and its capability needs\n to be restored (ITU-T Recommendation X.733).\n* MAJOR: The Major severity level indicates that a service affecting\n condition has developed and an urgent corrective action is required.\n Such a severity can be reported, for example, when there is a severe\n degradation in the capability of the managed object and its full\n capability needs to be restored (ITU-T Recommendation X.733).\n* MINOR: The Minor severity level indicates the existence of a\n non-service affecting fault condition and that corrective action\n should be taken in order to prevent a more serious (for example,\n service affecting) fault. Such a severity can be reported, for\n example, when the detected alarm condition is not currently degrading\n the capacity of the managed object (ITU-T Recommendation X.733).\n* WARNING: The Warning severity level indicates the detection of a\n potential or impending service affecting fault, before any significant\n effects have been felt. Action should be taken to further diagnose (if\n necessary) and correct the problem in order to prevent it from\n becoming a more serious service affecting fault (ITU-T Recommendation\n X.733).\n* INDETERMINATE: The Indeterminate severity level indicates that the\n severity level cannot be determined (ITU-T Recommendation X.733).\n* CLEARED: The Cleared severity level indicates the clearing of one or\n more previously reported alarms. This alarm clears all alarms for this\n managed object that have the same Alarm type, Probable cause and\n Specific problems (if given) (ITU-T Recommendation X.733).\n",
"type": "string",
"enum": [
"CRITICAL",
@@ -107,12 +121,12 @@
]
},
"eventTime": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
"type": "string",
"format": "date-time"
},
"eventType": {
- "description": "The enumeration EventType represents those types of events that trigger an alarm. * COMMUNICATIONS_ALARM: An alarm of this type is associated with the procedure and/or process required conveying information from one point\n to another (ITU-T Recommendation X.733).\n* PROCESSING_ERROR_ALARM: An alarm of this type is associated with a software or processing fault (ITU-T Recommendation X.733).\n* ENVIRONMENTAL_ALARM: An alarm of this type is associated with a condition related to an enclosure in which the equipment resides\n (ITU-T Recommendation X.733).\n* QOS_ALARM: An alarm of this type is associated with degradation in the quality of a service (ITU-T Recommendation X.733).\n* EQUIPMENT_ALARM: An alarm of this type is associated with an equipment fault (ITU-T Recommendation X.733).\n",
+ "description": "The enumeration EventType represents those types of events that trigger an alarm. * COMMUNICATIONS_ALARM: An alarm of this type is associated with the\n procedure and/or process required conveying information from one point\n to another (ITU-T Recommendation X.733).\n* PROCESSING_ERROR_ALARM: An alarm of this type is associated with a\n software or processing fault (ITU-T Recommendation X.733).\n* ENVIRONMENTAL_ALARM: An alarm of this type is associated with a\n condition related to an enclosure in which the equipment resides\n (ITU-T Recommendation X.733).\n* QOS_ALARM: An alarm of this type is associated with degradation in the\n quality of a service (ITU-T Recommendation X.733).\n* EQUIPMENT_ALARM: An alarm of this type is associated with an equipment\n fault (ITU-T Recommendation X.733).\n",
"type": "string",
"enum": [
"COMMUNICATIONS_ALARM",
@@ -123,15 +137,15 @@
]
},
"faultType": {
- "description": "Additional information to clarify the type of the fault.\n",
+ "description": "Additional information to clarify the type of the fault. If the alarm is related to changes in the state of virtualised resources due to NFVI operation and maintenance, this attribute shall be set to \"NFVI_OAM_VIRTUALISED_RESOURCE_STATE_CHANGE\".\n",
"type": "string"
},
"probableCause": {
- "description": "Information about the probable cause of the fault.\n",
+ "description": "Information about the probable cause of the fault. If the attribute \"faultType\" has the value “NFVI_OAM_VIRTUALISED_RESOURCE_STATE_CHANGEâ€, the permitted values are: \n - \"NFVI_COMPONENT_MAINTENANCE\": Maintenance of NFVI components, e.g. \n physical maintenance/repair, hypervisor software updates, etc.\n - \"NFVI_COMPONENT_EVACUATION\": Evacuation of physical hosts.\n - \"NFVI_COMPONENT_OPTIMIZATION\": Operation and management of NFVI resources, e.g.\n to support energy efficiency or resource usage.\n",
"type": "string"
},
"isRootCause": {
- "description": "Attribute indicating if this fault is the root for other correlated alarms. If TRUE, then the alarms listed in the attribute CorrelatedAlarmId are caused by this fault.\n",
+ "description": "Attribute indicating if this fault is the root for other correlated alarms. If true, then the alarms listed in the attribute \"correlatedAlarmIds\" are caused by this fault.\n",
"type": "boolean"
},
"correlatedAlarmIds": {
@@ -143,7 +157,7 @@
}
},
"faultDetails": {
- "description": "Provides additional information about the fault.\n",
+ "description": "Provides additional information about the fault. See notes 1 and 2.\n",
"type": "array",
"items": {
"type": "string"
@@ -152,35 +166,27 @@
"_links": {
"description": "Links for this resource.\n",
"type": "object",
- "required": [
- "self"
- ],
+ "required": ["self"],
"properties": {
"self": {
- "description": "This type represents a link to a resource.\n",
+ "description": "This type represents a link to a resource using an absolute URI.\n",
"type": "object",
- "required": [
- "href"
- ],
+ "required": ["href"],
"properties": {
"href": {
- "description": "URI of the referenced resource.\n",
- "type": "string",
- "format": "url"
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
}
}
},
"objectInstance": {
- "description": "This type represents a link to a resource.\n",
+ "description": "This type represents a link to a resource using an absolute URI.\n",
"type": "object",
- "required": [
- "href"
- ],
+ "required": ["href"],
"properties": {
"href": {
- "description": "URI of the referenced resource.\n",
- "type": "string",
- "format": "url"
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
}
}
}
diff --git a/SOL003/VNFFaultManagement-API/schemas/FmSubscription.schema.json b/SOL003/VNFFaultManagement-API/schemas/FmSubscription.schema.json
index 9acc07f2440c98630074d08e44d12b597e5281d8..67f360ad6cfc05771a0f456d9b0dc8c0b4c60e50 100644
--- a/SOL003/VNFFaultManagement-API/schemas/FmSubscription.schema.json
+++ b/SOL003/VNFFaultManagement-API/schemas/FmSubscription.schema.json
@@ -1,26 +1,44 @@
{
"description": "This type represents a subscription related to notifications about VNF faults.\n",
"type": "object",
- "required": [
- "id",
- "callbackUri",
- "_links"
- ],
+ "required": ["id", "callbackUri", "_links"],
"properties": {
"id": {
"description": "An identifier with the intention of being globally unique.\n",
"type": "string"
},
"filter": {
- "description": "This type represents a subscription filter related to notifications about VNF faults. At a particular nesting level in the filter structure, the following applies: All attributes shall match in order for the filter to match (logical \"and\" between different filter attributes). If an attribute is an array, the attribute shall match if at least one of the values in the array matches (logical \"or\" between the values of one filter attribute).\n",
+ "description": "This type represents a subscription filter related to notifications about VNF faults.\nAt a particular nesting level in the filter structure, the following applies: All attributes shall match in order for the filter to match (logical \"and\" between different filter attributes). If an attribute is an array, the attribute shall match if at least one of the values in the array matches (logical \"or\" between the values of one filter attribute).\nNOTE:\tThe permitted values of the \"notificationTypes\" attribute are spelled exactly as the names \n of the notification types to facilitate automated code generation systems.\n",
"type": "object",
"properties": {
"vnfInstanceSubscriptionFilter": {
- "description": "This type represents subscription filter criteria to match VNF instances.\n",
+ "description": "This type represents subscription filter criteria to match VNF instances. * NOTE 1:\tThe attributes \"vnfdIds\" and \"vnfProductsFromProviders\" are alternatives to reference to VNF instances\n that are based on certain VNFDs in a filter. They should not be used both in the same filter instance,\n but one alternative should be chosen.\n NOTE 2:\tThe attributes \"vnfInstanceIds\" and \"vnfInstanceNames\" are alternatives to reference to particular VNF\n instances in a filter. They should not be used both in the same filter instance, but one alternative\n should be chosen.\n",
"type": "object",
+ "anyOf": [
+ {
+ "oneOf": [
+ {
+ "required": ["vnfdId"]
+ },
+ {
+ "required": ["vnfProductsFromProviders"]
+ }
+ ]
+ },
+ {
+ "oneOf": [
+ {
+ "required": ["vnfInstanceIds"]
+ },
+ {
+ "required": ["vnfInstanceNames"]
+ }
+ ]
+ }
+ ],
"properties": {
"vnfdIds": {
- "description": "If present, match VNF instances that were created based on a VNFD identified by one of the vnfdId values listed in this attribute. The attributes \"vnfdIds\" and \"vnfProductsFromProviders\" are alternatives to reference to VNF instances that are based on certain VNFDs in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n",
+ "description": "If present, match VNF instances that were created based on a VNFD identified by one of the vnfdId values listed in this attribute. See note 1.\n",
"type": "array",
"items": {
"description": "An identifier with the intention of being globally unique.\n",
@@ -28,13 +46,11 @@
}
},
"vnfProductsFromProviders": {
- "description": "If present, match VNF instances that belong to VNF products from certain providers. The attributes \"vnfdIds\" and \"vnfProductsFromProviders\" are alternatives to reference to VNF instances that are based on certain VNFDs in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n",
+ "description": "If present, match VNF instances that belong to VNF products from certain providers. See note 1.\n",
"type": "array",
"items": {
"type": "object",
- "required": [
- "vnfProvider"
- ],
+ "required": ["vnfProvider"],
"properties": {
"vnfProvider": {
"description": "Name of the VNF provider to match.\n",
@@ -45,9 +61,7 @@
"type": "array",
"items": {
"type": "object",
- "required": [
- "vnfProductName"
- ],
+ "required": ["vnfProductName"],
"properties": {
"vnfProductName": {
"description": "Name of the VNF product to match.\n",
@@ -58,9 +72,7 @@
"type": "array",
"items": {
"type": "object",
- "required": [
- "vnfSoftwareVersion"
- ],
+ "required": ["vnfSoftwareVersion"],
"properties": {
"vnfSoftwareVersion": {
"description": "A version.\n",
@@ -84,7 +96,7 @@
}
},
"vnfInstanceIds": {
- "description": "If present, match VNF instances with an instance identifier listed in this attribute. The attributes \"vnfInstanceIds\" and \"vnfInstanceNames\" are alternatives to reference to particular VNF Instances in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n",
+ "description": "If present, match VNF instances with an instance identifier listed in this attribute. See note 2.\n",
"type": "array",
"items": {
"description": "An identifier with the intention of being globally unique.\n",
@@ -92,7 +104,7 @@
}
},
"vnfInstanceNames": {
- "description": "If present, match VNF instances with a VNF Instance Name listed in this attribute. The attributes \"vnfInstanceIds\" and \"vnfInstanceNames\" are alternatives to reference to particular VNF Instances in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n",
+ "description": "If present, match VNF instances with a VNF Instance Name listed in this attribute. See note 2.\n",
"type": "array",
"items": {
"type": "string"
@@ -101,7 +113,7 @@
}
},
"notificationTypes": {
- "description": "Match particular notification types. Permitted values: * AlarmNotification * AlarmClearedNotification * AlarmListRebuiltNotification The permitted values of the \"notificationTypes\" attribute are spelled exactly as the names of the notification types to facilitate automated code generation systems.\n",
+ "description": "Match particular notification types. \nPermitted values: -\tAlarmNotification -\tAlarmClearedNotification -\tAlarmListRebuiltNotification See note.\n",
"type": "array",
"items": {
"type": "string",
@@ -118,11 +130,7 @@
"items": {
"description": "The enumeration FaultyResourceType represents those types of faulty resource.\n",
"type": "string",
- "enum": [
- "COMPUTE",
- "STORAGE",
- "NETWORK"
- ]
+ "enum": ["COMPUTE", "STORAGE", "NETWORK"]
}
},
"perceivedSeverities": {
@@ -166,32 +174,26 @@
}
},
"callbackUri": {
- "description": "The URI of the endpoint to send the notification to.\n",
- "type": "string",
- "format": "url"
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
},
"_links": {
"description": "Links for this resource.\n",
"type": "object",
- "required": [
- "self"
- ],
+ "required": ["self"],
"properties": {
"self": {
- "description": "This type represents a link to a resource.\n",
+ "description": "This type represents a link to a resource using an absolute URI.\n",
"type": "object",
- "required": [
- "href"
- ],
+ "required": ["href"],
"properties": {
"href": {
- "description": "URI of the referenced resource.\n",
- "type": "string",
- "format": "url"
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
}
}
}
}
}
}
-}
+}
\ No newline at end of file
diff --git a/SOL003/VNFFaultManagement-API/schemas/FmSubscriptions.schema.json b/SOL003/VNFFaultManagement-API/schemas/FmSubscriptions.schema.json
index 219d19e4efdc715b2cc1d6ba5e405549b8b6d3ee..d70aa2eebacde1e2e08453e2aac7d7da2970ee86 100644
--- a/SOL003/VNFFaultManagement-API/schemas/FmSubscriptions.schema.json
+++ b/SOL003/VNFFaultManagement-API/schemas/FmSubscriptions.schema.json
@@ -3,26 +3,44 @@
"items": {
"description": "This type represents a subscription related to notifications about VNF faults.\n",
"type": "object",
- "required": [
- "id",
- "callbackUri",
- "_links"
- ],
+ "required": ["id", "callbackUri", "_links"],
"properties": {
"id": {
"description": "An identifier with the intention of being globally unique.\n",
"type": "string"
},
"filter": {
- "description": "This type represents a subscription filter related to notifications about VNF faults. At a particular nesting level in the filter structure, the following applies: All attributes shall match in order for the filter to match (logical \"and\" between different filter attributes). If an attribute is an array, the attribute shall match if at least one of the values in the array matches (logical \"or\" between the values of one filter attribute).\n",
+ "description": "This type represents a subscription filter related to notifications about VNF faults.\nAt a particular nesting level in the filter structure, the following applies: All attributes shall match in order for the filter to match (logical \"and\" between different filter attributes). If an attribute is an array, the attribute shall match if at least one of the values in the array matches (logical \"or\" between the values of one filter attribute).\nNOTE:\tThe permitted values of the \"notificationTypes\" attribute are spelled exactly as the names \n of the notification types to facilitate automated code generation systems.\n",
"type": "object",
"properties": {
"vnfInstanceSubscriptionFilter": {
- "description": "This type represents subscription filter criteria to match VNF instances.\n",
+ "description": "This type represents subscription filter criteria to match VNF instances. * NOTE 1:\tThe attributes \"vnfdIds\" and \"vnfProductsFromProviders\" are alternatives to reference to VNF instances\n that are based on certain VNFDs in a filter. They should not be used both in the same filter instance,\n but one alternative should be chosen.\n NOTE 2:\tThe attributes \"vnfInstanceIds\" and \"vnfInstanceNames\" are alternatives to reference to particular VNF\n instances in a filter. They should not be used both in the same filter instance, but one alternative\n should be chosen.\n",
"type": "object",
+ "anyOf": [
+ {
+ "oneOf": [
+ {
+ "required": ["vnfdId"]
+ },
+ {
+ "required": ["vnfProductsFromProviders"]
+ }
+ ]
+ },
+ {
+ "oneOf": [
+ {
+ "required": ["vnfInstanceIds"]
+ },
+ {
+ "required": ["vnfInstanceNames"]
+ }
+ ]
+ }
+ ],
"properties": {
"vnfdIds": {
- "description": "If present, match VNF instances that were created based on a VNFD identified by one of the vnfdId values listed in this attribute. The attributes \"vnfdIds\" and \"vnfProductsFromProviders\" are alternatives to reference to VNF instances that are based on certain VNFDs in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n",
+ "description": "If present, match VNF instances that were created based on a VNFD identified by one of the vnfdId values listed in this attribute. See note 1.\n",
"type": "array",
"items": {
"description": "An identifier with the intention of being globally unique.\n",
@@ -30,13 +48,11 @@
}
},
"vnfProductsFromProviders": {
- "description": "If present, match VNF instances that belong to VNF products from certain providers. The attributes \"vnfdIds\" and \"vnfProductsFromProviders\" are alternatives to reference to VNF instances that are based on certain VNFDs in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n",
+ "description": "If present, match VNF instances that belong to VNF products from certain providers. See note 1.\n",
"type": "array",
"items": {
"type": "object",
- "required": [
- "vnfProvider"
- ],
+ "required": ["vnfProvider"],
"properties": {
"vnfProvider": {
"description": "Name of the VNF provider to match.\n",
@@ -47,9 +63,7 @@
"type": "array",
"items": {
"type": "object",
- "required": [
- "vnfProductName"
- ],
+ "required": ["vnfProductName"],
"properties": {
"vnfProductName": {
"description": "Name of the VNF product to match.\n",
@@ -60,9 +74,7 @@
"type": "array",
"items": {
"type": "object",
- "required": [
- "vnfSoftwareVersion"
- ],
+ "required": ["vnfSoftwareVersion"],
"properties": {
"vnfSoftwareVersion": {
"description": "A version.\n",
@@ -86,7 +98,7 @@
}
},
"vnfInstanceIds": {
- "description": "If present, match VNF instances with an instance identifier listed in this attribute. The attributes \"vnfInstanceIds\" and \"vnfInstanceNames\" are alternatives to reference to particular VNF Instances in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n",
+ "description": "If present, match VNF instances with an instance identifier listed in this attribute. See note 2.\n",
"type": "array",
"items": {
"description": "An identifier with the intention of being globally unique.\n",
@@ -94,7 +106,7 @@
}
},
"vnfInstanceNames": {
- "description": "If present, match VNF instances with a VNF Instance Name listed in this attribute. The attributes \"vnfInstanceIds\" and \"vnfInstanceNames\" are alternatives to reference to particular VNF Instances in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n",
+ "description": "If present, match VNF instances with a VNF Instance Name listed in this attribute. See note 2.\n",
"type": "array",
"items": {
"type": "string"
@@ -103,7 +115,7 @@
}
},
"notificationTypes": {
- "description": "Match particular notification types. Permitted values: * AlarmNotification * AlarmClearedNotification * AlarmListRebuiltNotification The permitted values of the \"notificationTypes\" attribute are spelled exactly as the names of the notification types to facilitate automated code generation systems.\n",
+ "description": "Match particular notification types. \nPermitted values: -\tAlarmNotification -\tAlarmClearedNotification -\tAlarmListRebuiltNotification See note.\n",
"type": "array",
"items": {
"type": "string",
@@ -120,11 +132,7 @@
"items": {
"description": "The enumeration FaultyResourceType represents those types of faulty resource.\n",
"type": "string",
- "enum": [
- "COMPUTE",
- "STORAGE",
- "NETWORK"
- ]
+ "enum": ["COMPUTE", "STORAGE", "NETWORK"]
}
},
"perceivedSeverities": {
@@ -168,28 +176,22 @@
}
},
"callbackUri": {
- "description": "The URI of the endpoint to send the notification to.\n",
- "type": "string",
- "format": "url"
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
},
"_links": {
"description": "Links for this resource.\n",
"type": "object",
- "required": [
- "self"
- ],
+ "required": ["self"],
"properties": {
"self": {
- "description": "This type represents a link to a resource.\n",
+ "description": "This type represents a link to a resource using an absolute URI.\n",
"type": "object",
- "required": [
- "href"
- ],
+ "required": ["href"],
"properties": {
"href": {
- "description": "URI of the referenced resource.\n",
- "type": "string",
- "format": "url"
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
}
}
}
@@ -197,4 +199,4 @@
}
}
}
-}
+}
\ No newline at end of file
diff --git a/SOL003/VNFFaultManagement-API/schemas/alarm.schema.json b/SOL003/VNFFaultManagement-API/schemas/alarm.schema.json
index 553252dddd8b2fbaf3158079638702dc10b61148..628e398e2361889b0522302c7a16de841d68cdfc 100644
--- a/SOL003/VNFFaultManagement-API/schemas/alarm.schema.json
+++ b/SOL003/VNFFaultManagement-API/schemas/alarm.schema.json
@@ -30,7 +30,7 @@
"faultyResource": {
"required": ["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",
+ "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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
@@ -41,11 +41,33 @@
"type": "string"
},
"resourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
"type": "string"
},
"vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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"
}
}
@@ -115,7 +137,7 @@
"type": "string"
},
"probableCause": {
- "description": "Information about the probable cause of the fault. If the attribute \"faultType\" has the value ΓÇ£NFVI_OAM_VIRTUALISED_RESOURCE_STATE_CHANGEΓÇ¥, the permitted values are: \n - \"NFVI_COMPONENT_MAINTENANCE\": Maintenance of NFVI components, e.g. \n physical maintenance/repair, hypervisor software updates, etc.\n - \"NFVI_COMPONENT_EVACUATION\": Evacuation of physical hosts.\n - \"NFVI_COMPONENT_OPTIMIZATION\": Operation and management of NFVI resources, e.g.\n to support energy efficiency or resource usage optimization.\n",
+ "description": "Information about the probable cause of the fault. If the attribute \"faultType\" has the value “NFVI_OAM_VIRTUALISED_RESOURCE_STATE_CHANGEâ€, the permitted values are: \n - \"NFVI_COMPONENT_MAINTENANCE\": Maintenance of NFVI components, e.g. \n physical maintenance/repair, hypervisor software updates, etc.\n - \"NFVI_COMPONENT_EVACUATION\": Evacuation of physical hosts.\n - \"NFVI_COMPONENT_OPTIMIZATION\": Operation and management of NFVI resources, e.g.\n to support energy efficiency or resource usage.\n",
"type": "string"
},
"isRootCause": {
diff --git a/SOL003/VNFFaultManagement-API/schemas/alarmModifications.schema.json b/SOL003/VNFFaultManagement-API/schemas/alarmModifications.schema.json
index 460ad06565d3e2bd8ee356b8448f14202150b7cf..9e0c34e703ec56b1e2bc0ace4d0d0986f90c47eb 100644
--- a/SOL003/VNFFaultManagement-API/schemas/alarmModifications.schema.json
+++ b/SOL003/VNFFaultManagement-API/schemas/alarmModifications.schema.json
@@ -1,16 +1,12 @@
{
"description": "This type represents attribute modifications for an \"Individual alarm\" resource, i.e. modifications to a resource representation based on the \"Alarm\" data type. The attributes of \"Alarm\" that can be modified are included in the \"AlarmModifications\" data type.\n",
"type": "object",
- "required": [
- "ackState"
- ],
+ "required": ["ackState"],
"properties": {
"ackState": {
- "description": "New value of the \"ackState\" attribute in \"Alarm\". Permitted values: * ACKNOWLEDGED\n",
+ "description": "New value of the \"ackState\" attribute in \"Alarm\". Permitted values: * ACKNOWLEDGED * UNACKNOWLEDGED\n",
"type": "string",
- "enum": [
- "ACKNOWLEDGED"
- ]
+ "enum": ["ACKNOWLEDGED", "UNACKNOWLEDGED"]
}
}
}
\ No newline at end of file
diff --git a/SOL003/VNFFaultManagementNotification-API/Notifications.robot b/SOL003/VNFFaultManagementNotification-API/Notifications.robot
index 0e0bffd3d64ca985d1c08078af712ed83e0fae74..74a5deb97f60381cc1c3074558016acbc55bcf53 100644
--- a/SOL003/VNFFaultManagementNotification-API/Notifications.robot
+++ b/SOL003/VNFFaultManagementNotification-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] v3.6.1
+ ... Reference: Clause 7.4.6.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.6.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.6.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFFaultManagementNotification-API/schemas/alarmClearedNotification.schema.json b/SOL003/VNFFaultManagementNotification-API/schemas/alarmClearedNotification.schema.json
index 08131723d82361c2b27ba85b4ad5e7bc1077da2f..b3a8795b0fb2dcd12623cedd95fc14985bc409ee 100644
--- a/SOL003/VNFFaultManagementNotification-API/schemas/alarmClearedNotification.schema.json
+++ b/SOL003/VNFFaultManagementNotification-API/schemas/alarmClearedNotification.schema.json
@@ -18,16 +18,14 @@
"notificationType": {
"description": "Discriminator for the different notification types. Shall be set to \"AlarmClearedNotification\" for this notification type.\n",
"type": "string",
- "enum": [
- "AlarmClearedNotification"
- ]
+ "enum": ["AlarmClearedNotification"]
},
"subscriptionId": {
"description": "An identifier with the intention of being globally unique.\n",
"type": "string"
},
"timeStamp": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
"type": "string",
"format": "date-time"
},
@@ -36,41 +34,34 @@
"type": "string"
},
"alarmClearedTime": {
- "description": "The time stamp indicating when the alarm was cleared.\n"
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
},
"_links": {
"description": "Links to resources related to this notification.\n",
"type": "object",
- "required": [
- "subscription",
- "alarm"
- ],
+ "required": ["subscription", "alarm"],
"properties": {
"subscription": {
- "description": "This type represents a link to a resource.\n",
+ "description": "This type represents a link to a resource in a notification, using an absolute or relative URI.\n",
"type": "object",
- "required": [
- "href"
- ],
+ "required": ["href"],
"properties": {
"href": {
- "description": "URI of the referenced resource.\n",
- "type": "string",
- "format": "url"
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
}
}
},
"alarm": {
- "description": "This type represents a link to a resource.\n",
+ "description": "This type represents a link to a resource in a notification, using an absolute or relative URI.\n",
"type": "object",
- "required": [
- "href"
- ],
+ "required": ["href"],
"properties": {
"href": {
- "description": "URI of the referenced resource.\n",
- "type": "string",
- "format": "url"
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
}
}
}
diff --git a/SOL003/VNFFaultManagementNotification-API/schemas/alarmListRebuiltNotification.schema.json b/SOL003/VNFFaultManagementNotification-API/schemas/alarmListRebuiltNotification.schema.json
index bfe018df8f3dec0fc2526d02254fa13486ea68b9..14ca3dc978cdc10f810ad23dbf2bb3cc3cd08a0c 100644
--- a/SOL003/VNFFaultManagementNotification-API/schemas/alarmListRebuiltNotification.schema.json
+++ b/SOL003/VNFFaultManagementNotification-API/schemas/alarmListRebuiltNotification.schema.json
@@ -1,5 +1,5 @@
{
- "description": "This type represents a notification that the alarm list has been rebuilt, e.g. if the VNFM detects its storage holding the alarm list is corrupted. The notification shall be triggered by the VNFM when the alarm list has been rebuilt.\n",
+ "description": "This type represents a notification that the alarm list has been rebuilt, e.g. if the VNFM detects its storage holding the alarm list is corrupted. The notification shall be triggered by the VNFM when the alarm list has been rebuilt, e.g. because the VNFM has detected that its storage holding the alarm list was corrupted.\n",
"type": "object",
"required": [
"id",
@@ -16,52 +16,41 @@
"notificationType": {
"description": "Discriminator for the different notification types. Shall be set to \"AlarmListRebuiltNotification\" for this notification type.\n",
"type": "string",
- "enum": [
- "AlarmListRebuiltNotification"
- ]
+ "enum": ["AlarmListRebuiltNotification"]
},
"subscriptionId": {
"description": "An identifier with the intention of being globally unique.\n",
"type": "string"
},
"timeStamp": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
"type": "string",
"format": "date-time"
},
"_links": {
"description": "Links to resources related to this notification.\n",
"type": "object",
- "required": [
- "subscription",
- "alarms"
- ],
+ "required": ["subscription", "alarms"],
"properties": {
"subscription": {
- "description": "This type represents a link to a resource.\n",
+ "description": "This type represents a link to a resource in a notification, using an absolute or relative URI.\n",
"type": "object",
- "required": [
- "href"
- ],
+ "required": ["href"],
"properties": {
"href": {
- "description": "URI of the referenced resource.\n",
- "type": "string",
- "format": "url"
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
}
}
},
"alarms": {
- "description": "This type represents a link to a resource.\n",
+ "description": "This type represents a link to a resource in a notification, using an absolute or relative URI.\n",
"type": "object",
- "required": [
- "href"
- ],
+ "required": ["href"],
"properties": {
"href": {
- "description": "URI of the referenced resource.\n",
- "type": "string",
- "format": "url"
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
}
}
}
diff --git a/SOL003/VNFFaultManagementNotification-API/schemas/alarmNotification.schema.json b/SOL003/VNFFaultManagementNotification-API/schemas/alarmNotification.schema.json
index 1d31e7e34a01f343971896a0653622fd430b3f67..1d80e9031d90ae08eb346a383ff64d14bff61290 100644
--- a/SOL003/VNFFaultManagementNotification-API/schemas/alarmNotification.schema.json
+++ b/SOL003/VNFFaultManagementNotification-API/schemas/alarmNotification.schema.json
@@ -1,246 +1,238 @@
{
- "name": "AlarmNotification",
- "description": "Information of a VNF alarm.\n",
- "in": "body",
- "required": true,
- "schema": {
- "description": "This type represents an alarm notification about VNF faults. This notification shall be triggered by the VNFM when: * An alarm has been created. * An alarm has been updated, e.g. if the severity of the alarm has changed.\n",
- "type": "object",
- "required": [
- "id",
- "notificationType",
- "subscriptionId",
- "timeStamp",
- "alarm",
- "_links"
- ],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "notificationType": {
- "description": "Discriminator for the different notification types. Shall be set to \"AlarmNotification\" for this notification type.\n",
- "type": "string",
- "enum": [
- "AlarmNotification"
- ]
- },
- "subscriptionId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "timeStamp": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "alarm": {
- "description": "The alarm data type encapsulates information about an alarm.\n",
- "type": "object",
- "required": [
- "id",
- "managedObjectId",
- "rootCauseFaultyResource",
- "alarmRaisedTime",
- "ackState",
- "perceivedSeverity",
- "eventTime",
- "eventType",
- "probableCause",
- "isRootCause",
- "_links"
- ],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "managedObjectId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "rootCauseFaultyResource": {
- "description": "This type represents the faulty virtual resources that have a negative impact on a VNF.\n",
- "type": "object",
- "required": [
- "faultyResource",
- "faultyResourceType"
- ],
- "properties": {
- "faultyResource": {
- "required": [
- "vimConnectionId",
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Type of the resource in the scope of the VIM or the resource provider.\n",
- "type": "string"
+ "description": "This type represents an alarm notification about VNF faults. This notification shall be triggered by the VNFM when: * An alarm has been created. * An alarm has been updated, e.g. if the severity of the alarm has\n changed.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "notificationType",
+ "subscriptionId",
+ "timeStamp",
+ "alarm",
+ "_links"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "notificationType": {
+ "description": "Discriminator for the different notification types. Shall be set to \"AlarmNotification\" for this notification type.\n",
+ "type": "string",
+ "enum": ["AlarmNotification"]
+ },
+ "subscriptionId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "timeStamp": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "alarm": {
+ "description": "The alarm data type encapsulates information about an alarm. \nNOTE 1: For an alarm about upcoming impact due to NFVI operation and maintenance (i.e. the attribute \n \"faultType\" has the value \"NFVI_OAM_VIRTUALISED_RESOURCE_STATE_CHANGE\"), the attribute \n \"rootCauseFaultyResource\" indicates a resource to be impacted. Further information on the upcoming\n impact (e.g. group of impacted resources, time of impact) is provided in the attribute \"faultDetails\".\nNOTE 2: When alarms are due to upcoming NFVI operation and maintenance (i.e. the attribute \"faultType\" has the \n value \"NFVI_OAM_VIRTUALISED_RESOURCE_STATE_CHANGE\"), the attribute \"faultDetails\" shall include \n information about the anticipated time of the maintenance. See provisions under the present table.\n\nIf the attribute \"faultType\" has the value \"NFVI_OAM_VIRTUALISED_RESOURCE_STATE_CHANGE\", the following provisions apply for the values of the attribute \"faultDetails\" related to changes in the state of virtualised resources:\n - One of the entries in the array shall provide information about the anticipated time of maintenance in the \n following format: \"anticipatedTime=$time\", wherein \"$time\" shall be formatted as a \"DateTime\", as specified \n in ETSI GS NFV-SOL 013 [8]. \n - One of the entries in the array shall provide identification information about the affinity/anti-affinity\n group defined in the VNFD that is associated to the affected virtualised resource indicated by \n \"rootCauseFaultyResource\" in the following format: \"affinityOrAntiAffinityGroupId=$group\", wherein \n \"$group\" shall be equal to the \"affinityOrAntiAffinityGroupId\" value in the corresponding \"VduProfile\" (for a \n VNFC/COMPUTE affected resource) or \"VirtualLinkProfile\" for a VL/NETWORK affected resource) in the \n VNFD, which is mapped by the VNFM to the virtualised resource group identifier in the virtualised resource \n change notification received by the VNFM from the VIM.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "managedObjectId",
+ "alarmRaisedTime",
+ "ackState",
+ "perceivedSeverity",
+ "eventTime",
+ "eventType",
+ "probableCause",
+ "isRootCause",
+ "_links"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "managedObjectId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "rootCauseFaultyResource": {
+ "description": "This type represents the faulty virtual resources that have a negative impact on a VNF.\n",
+ "type": "object",
+ "required": ["faultyResource", "faultyResourceType"],
+ "properties": {
+ "faultyResource": {
+ "required": ["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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
}
+ },
+ "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"
}
- },
- "faultyResourceType": {
- "description": "The enumeration FaultyResourceType represents those types of faulty resource.\n",
- "type": "string",
- "enum": [
- "COMPUTE",
- "STORAGE",
- "NETWORK"
- ]
}
+ },
+ "faultyResourceType": {
+ "description": "The enumeration FaultyResourceType represents those types of faulty resource.\n",
+ "type": "string",
+ "enum": ["COMPUTE", "STORAGE", "NETWORK"]
}
- },
- "alarmRaisedTime": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "alarmChangedTime": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "alarmClearedTime": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "ackState": {
- "description": "Acknowledgement state of the alarm. Permitted values: * UNACKNOWLEDGED * ACKNOWLEDGED.\n",
- "type": "string",
- "enum": [
- "UNACKNOWLEDGED",
- "ACKNOWLEDGED"
- ]
- },
- "perceivedSeverity": {
- "description": "Indicates the relative level of urgency for operator attention. * CRITICAL: The Critical severity level indicates that a service affecting condition has occurred and an immediate corrective action\n is required. Such a severity can be reported, for example, when a\n managed object becomes totally out of service and its capability needs\n to be restored (ITU-T Recommendation X.733).\n* MAJOR: The Major severity level indicates that a service affecting condition has developed and an urgent corrective action is required.\n Such a severity can be reported, for example, when there is a severe\n degradation in the capability of the managed object and its full\n capability needs to be restored (ITU-T Recommendation X.733).\n* MINOR: The Minor severity level indicates the existence of a non-service affecting fault condition and that corrective action\n should be taken in order to prevent a more serious (for example,\n service affecting) fault. Such a severity can be reported, for\n example, when the detected alarm condition is not currently degrading\n the capacity of the managed object (ITU-T Recommendation X.733).\n* WARNING: The Warning severity level indicates the detection of a potential or impending service affecting fault, before any significant\n effects have been felt. Action should be taken to further diagnose (if\n necessary) and correct the problem in order to prevent it from\n becoming a more serious service affecting fault (ITU-T Recommendation\n X.733).\n* INDETERMINATE: The Indeterminate severity level indicates that the severity level cannot be determined (ITU-T Recommendation X.733).\n* CLEARED: The Cleared severity level indicates the clearing of one or more previously reported alarms. This alarm clears all alarms for this\n managed object that have the same Alarm type, Probable cause and\n Specific problems (if given) (ITU-T Recommendation X.733).\n",
- "type": "string",
- "enum": [
- "CRITICAL",
- "MAJOR",
- "MINOR",
- "WARNING",
- "INDETERMINATE",
- "CLEARED"
- ]
- },
- "eventTime": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "eventType": {
- "description": "The enumeration EventType represents those types of events that trigger an alarm. * COMMUNICATIONS_ALARM: An alarm of this type is associated with the procedure and/or process required conveying information from one point\n to another (ITU-T Recommendation X.733).\n* PROCESSING_ERROR_ALARM: An alarm of this type is associated with a software or processing fault (ITU-T Recommendation X.733).\n* ENVIRONMENTAL_ALARM: An alarm of this type is associated with a condition related to an enclosure in which the equipment resides\n (ITU-T Recommendation X.733).\n* QOS_ALARM: An alarm of this type is associated with degradation in the quality of a service (ITU-T Recommendation X.733).\n* EQUIPMENT_ALARM: An alarm of this type is associated with an equipment fault (ITU-T Recommendation X.733).\n",
- "type": "string",
- "enum": [
- "COMMUNICATIONS_ALARM",
- "PROCESSING_ERROR_ALARM",
- "ENVIRONMENTAL_ALARM",
- "QOS_ALARM",
- "EQUIPMENT_ALARM"
- ]
- },
- "faultType": {
- "description": "Additional information to clarify the type of the fault.\n",
+ }
+ },
+ "alarmRaisedTime": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "alarmChangedTime": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "alarmClearedTime": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "alarmAcknowledgedTime": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "ackState": {
+ "description": "Acknowledgement state of the alarm. Permitted values: * UNACKNOWLEDGED * ACKNOWLEDGED.\n",
+ "type": "string",
+ "enum": ["UNACKNOWLEDGED", "ACKNOWLEDGED"]
+ },
+ "perceivedSeverity": {
+ "description": "Indicates the relative level of urgency for operator attention. * CRITICAL: The Critical severity level indicates that a service\n affecting condition has occurred and an immediate corrective action\n is required. Such a severity can be reported, for example, when a\n managed object becomes totally out of service and its capability needs\n to be restored (ITU-T Recommendation X.733).\n* MAJOR: The Major severity level indicates that a service affecting\n condition has developed and an urgent corrective action is required.\n Such a severity can be reported, for example, when there is a severe\n degradation in the capability of the managed object and its full\n capability needs to be restored (ITU-T Recommendation X.733).\n* MINOR: The Minor severity level indicates the existence of a\n non-service affecting fault condition and that corrective action\n should be taken in order to prevent a more serious (for example,\n service affecting) fault. Such a severity can be reported, for\n example, when the detected alarm condition is not currently degrading\n the capacity of the managed object (ITU-T Recommendation X.733).\n* WARNING: The Warning severity level indicates the detection of a\n potential or impending service affecting fault, before any significant\n effects have been felt. Action should be taken to further diagnose (if\n necessary) and correct the problem in order to prevent it from\n becoming a more serious service affecting fault (ITU-T Recommendation\n X.733).\n* INDETERMINATE: The Indeterminate severity level indicates that the\n severity level cannot be determined (ITU-T Recommendation X.733).\n* CLEARED: The Cleared severity level indicates the clearing of one or\n more previously reported alarms. This alarm clears all alarms for this\n managed object that have the same Alarm type, Probable cause and\n Specific problems (if given) (ITU-T Recommendation X.733).\n",
+ "type": "string",
+ "enum": [
+ "CRITICAL",
+ "MAJOR",
+ "MINOR",
+ "WARNING",
+ "INDETERMINATE",
+ "CLEARED"
+ ]
+ },
+ "eventTime": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "eventType": {
+ "description": "The enumeration EventType represents those types of events that trigger an alarm. * COMMUNICATIONS_ALARM: An alarm of this type is associated with the\n procedure and/or process required conveying information from one point\n to another (ITU-T Recommendation X.733).\n* PROCESSING_ERROR_ALARM: An alarm of this type is associated with a\n software or processing fault (ITU-T Recommendation X.733).\n* ENVIRONMENTAL_ALARM: An alarm of this type is associated with a\n condition related to an enclosure in which the equipment resides\n (ITU-T Recommendation X.733).\n* QOS_ALARM: An alarm of this type is associated with degradation in the\n quality of a service (ITU-T Recommendation X.733).\n* EQUIPMENT_ALARM: An alarm of this type is associated with an equipment\n fault (ITU-T Recommendation X.733).\n",
+ "type": "string",
+ "enum": [
+ "COMMUNICATIONS_ALARM",
+ "PROCESSING_ERROR_ALARM",
+ "ENVIRONMENTAL_ALARM",
+ "QOS_ALARM",
+ "EQUIPMENT_ALARM"
+ ]
+ },
+ "faultType": {
+ "description": "Additional information to clarify the type of the fault. If the alarm is related to changes in the state of virtualised resources due to NFVI operation and maintenance, this attribute shall be set to \"NFVI_OAM_VIRTUALISED_RESOURCE_STATE_CHANGE\".\n",
+ "type": "string"
+ },
+ "probableCause": {
+ "description": "Information about the probable cause of the fault. If the attribute \"faultType\" has the value “NFVI_OAM_VIRTUALISED_RESOURCE_STATE_CHANGEâ€, the permitted values are: \n - \"NFVI_COMPONENT_MAINTENANCE\": Maintenance of NFVI components, e.g. \n physical maintenance/repair, hypervisor software updates, etc.\n - \"NFVI_COMPONENT_EVACUATION\": Evacuation of physical hosts.\n - \"NFVI_COMPONENT_OPTIMIZATION\": Operation and management of NFVI resources, e.g.\n to support energy efficiency or resource usage.\n",
+ "type": "string"
+ },
+ "isRootCause": {
+ "description": "Attribute indicating if this fault is the root for other correlated alarms. If true, then the alarms listed in the attribute \"correlatedAlarmIds\" are caused by this fault.\n",
+ "type": "boolean"
+ },
+ "correlatedAlarmIds": {
+ "description": "List of identifiers of other alarms correlated to this fault.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
"type": "string"
- },
- "probableCause": {
- "description": "Information about the probable cause of the fault.\n",
+ }
+ },
+ "faultDetails": {
+ "description": "Provides additional information about the fault. See notes 1 and 2.\n",
+ "type": "array",
+ "items": {
"type": "string"
- },
- "isRootCause": {
- "description": "Attribute indicating if this fault is the root for other correlated alarms. If TRUE, then the alarms listed in the attribute CorrelatedAlarmId are caused by this fault.\n",
- "type": "boolean"
- },
- "correlatedAlarmIds": {
- "description": "List of identifiers of other alarms correlated to this fault.\n",
- "type": "array",
- "items": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- }
- },
- "faultDetails": {
- "description": "Provides additional information about the fault.\n",
- "type": "array",
- "items": {
- "type": "string"
- }
- },
- "_links": {
- "description": "Links for 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 the referenced resource.\n",
- "type": "string",
- "format": "url"
- }
+ }
+ },
+ "_links": {
+ "description": "Links for this resource.\n",
+ "type": "object",
+ "required": ["self"],
+ "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"
}
- },
- "objectInstance": {
- "description": "This type represents a link to a resource.\n",
- "type": "object",
- "required": [
- "href"
- ],
- "properties": {
- "href": {
- "description": "URI of the referenced resource.\n",
- "type": "string",
- "format": "url"
- }
+ }
+ },
+ "objectInstance": {
+ "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"
}
}
}
}
}
- },
- "_links": {
- "description": "Links to resources related to this notification.\n",
- "type": "object",
- "required": [
- "subscription"
- ],
- "properties": {
- "subscription": {
- "description": "This type represents a link to a resource.\n",
- "type": "object",
- "required": [
- "href"
- ],
- "properties": {
- "href": {
- "description": "URI of the referenced resource.\n",
- "type": "string",
- "format": "url"
- }
+ }
+ },
+ "_links": {
+ "description": "Links to resources related to this notification.\n",
+ "type": "object",
+ "required": ["subscription"],
+ "properties": {
+ "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": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
}
}
}
diff --git a/SOL003/VNFIndicator-API/ApiVersion.robot b/SOL003/VNFIndicator-API/ApiVersion.robot
index 542ae0a3669bdc4760f4d329ecbb8bd4db72f536..bd7666d7b34f07932322cef52d0b22df6b199d6a 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] v3.5.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.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 80531a569cef5bdc01fa3e9362b2ed8ee1589aea..dc9a90a569e46391ddd78cbd1d0308cab6c4acd9 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] v3.6.1
+ ... Reference: Clause 8.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.6.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.6.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.6.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.6.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.6.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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 30b12f5b7ecf0662d253b6d36873790e9f1389d7..9a58f1933cc942bbc13fb099fd40693c72b18c25 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] v3.6.1
+ ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.4.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.4.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.4.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.3.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.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 4a54f7c1a781e253c4141d4bda0272caf98a176d..691fc5657399e38b80674ebccb0dacf11bed4d6a 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] v3.6.1
+ ... Reference: Clause 8.4.7.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.7.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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 113955a806c4669ec7a8232f503fd06b957bfd4f..0895d01f7c58adca56e18ac8f759d427f8f00552 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] v3.6.1
+ ... Reference: Clause 8.4.7.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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 3976f566617c7c2433b08f8a9bb47b96f030a354..99f78e2d5c45b763ddfeb79dcbb7b21cd614efc3 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] v3.6.1
+ ... Reference: Clause 8.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.5.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.5.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.5.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.5.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.5.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.5.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -177,7 +177,7 @@ POST Create a new Subscription - Unprocessable Entity
... 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.
... re-conditions: none
- ... Reference: Clause 8.4.5.3.1 - ETSI GS NFV-SOL 003 [1] v3.6.1
+ ... Reference: Clause 8.4.5.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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 76cd1d34d0b9f1e700eb0be486a0814ff7a9dcb3..1afeee3f3499eafed5c621c738f60c57eb343442 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] v3.6.1
+ ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.2.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.2.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.2.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.2.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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 35e18254b1dfcc6c6d10a12e5e53863fb01ecd6b..d815b49f114623d3b851bf98014871111846a216 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] v3.6.1
+ ... Reference: Clause 8.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.3.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.3.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.3.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.3.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFIndicator-API/schemas/SupportedIndicatorsChangeNotification.schema.json b/SOL003/VNFIndicator-API/schemas/SupportedIndicatorsChangeNotification.schema.json
index 35cf33eb74bfc5321d333895df5bf10ae038e53c..9982d94ea515f668289cc72e68594ec685c6299c 100644
--- a/SOL003/VNFIndicator-API/schemas/SupportedIndicatorsChangeNotification.schema.json
+++ b/SOL003/VNFIndicator-API/schemas/SupportedIndicatorsChangeNotification.schema.json
@@ -1,93 +1,83 @@
{
- "description": "This type represents a notification to inform the receiver that the set of indicators supported by a VNF instance has changed. It shall comply with the provisions defined in table 8.5.2.6-1. The notification shall be triggered by the VNFM when the set of supported VNF indicators has changed as a side effect of the \"Change current VNF package\" operation. It may be triggered by the VNFM when a VNF has been instantiated.\n",
- "type": "object",
- "required": [
- "id",
- "notificationType",
- "subscriptionId",
- "timeStamp",
- "vnfInstanceId",
- "_links"
- ],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "notificationType": {
- "description": "Discriminator for the different notification types. Shall be set to \"SupportedIndicatorsChangeNotification\" for this notification type.\n",
- "type": "string",
- "enum": [
- "VnfIndicatorValueChangeNotification"
- ]
- },
- "subscriptionId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "timeStamp": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "vnfInstanceId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "supportedIndicators": {
- "description": "Set of VNF indicators supported by the VNF instance.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": [
- "vnfIndicatorId"
- ],
- "properties": {
- "vnfIndicatorId": {
- "description": "An identifier that is unique within a VNF descriptor.\n",
- "type": "string"
- },
- "name": {
- "description": "Human readable name of the VNF indicator. Shall be present if defined in the VNFD. ETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on TOSCA specifications.\n",
- "type": "string"
- }
- }
- }
- },
- "_links": {
- "description": "Links for this resource.\n",
- "type": "object",
- "required": [
- "subscription"
- ],
- "properties": {
- "vnfInstance": {
- "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": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- }
- }
- },
- "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": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- }
- }
- }
- }
- }
- }
+ "description": "This type represents a notification to inform the receiver that the set of indicators supported by a VNF instance has changed.\nThe notification shall be triggered by the VNFM when the set of supported VNF indicators has changed as a side effect of the \"Change current VNF package\" operation. It may be triggered by the VNFM when a VNF has been instantiated.\nNOTE:\tETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on TOSCA specifications.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "notificationType",
+ "subscriptionId",
+ "timeStamp",
+ "vnfInstanceId",
+ "_links"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "notificationType": {
+ "description": "Discriminator for the different notification types. Shall be set to \"SupportedIndicatorsChangeNotification\" for this notification type.\n",
+ "type": "string",
+ "enum": ["VnfIndicatorValueChangeNotification"]
+ },
+ "subscriptionId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "timeStamp": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "vnfInstanceId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "supportedIndicators": {
+ "description": "Set of VNF indicators supported by the VNF instance.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": ["vnfIndicatorId"],
+ "properties": {
+ "vnfIndicatorId": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "name": {
+ "description": "Human readable name of the VNF indicator. Shall be present if defined in the VNFD. See note.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "_links": {
+ "description": "Links for this resource.\n",
+ "type": "object",
+ "required": ["subscription"],
+ "properties": {
+ "vnfInstance": {
+ "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": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ }
+ }
+ },
+ "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": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ }
+ }
+ }
+ }
+ }
+ }
}
\ No newline at end of file
diff --git a/SOL003/VNFIndicator-API/schemas/VnfIndicatorSubscription.schema.json b/SOL003/VNFIndicator-API/schemas/VnfIndicatorSubscription.schema.json
index 7609ac928880813b73de07501fe8534f4b565ab6..785c46630822f5fc6838a9c600f583b9c986683c 100644
--- a/SOL003/VNFIndicator-API/schemas/VnfIndicatorSubscription.schema.json
+++ b/SOL003/VNFIndicator-API/schemas/VnfIndicatorSubscription.schema.json
@@ -1,26 +1,44 @@
{
"description": "This type represents a subscription related to notifications about VNF indicator value changes.\n",
"type": "object",
- "required": [
- "id",
- "callbackUri",
- "_links"
- ],
+ "required": ["id", "callbackUri", "_links"],
"properties": {
"id": {
"description": "An identifier with the intention of being globally unique.\n",
"type": "string"
},
"filter": {
- "description": "This type represents a subscription filter related to notifications about VNF indicator value changes. At a particular nesting level in the filter structure, the following applies: All attributes shall match in order for the filter to match (logical \"and\" between different filter attributes). If an attribute is an array, the attribute shall match if at least one of the values in the array matches (logical \"or\" between the values of one filter attribute).\n",
+ "description": "This type represents a subscription filter for notifications related to VNF indicators.\nAt a particular nesting level in the filter structure, the following applies: All attributes shall match in order for the filter to match (logical \"and\" between different filter attributes). If an attribute is an array, the attribute shall match if at least one of the values in the array matches (logical \"or\" between the values of one filter attribute).\nNOTE:\tThe permitted values of the \"notificationTypes\" attribute are spelled exactly as the names \n of the notification types to facilitate automated code generation systems.\n",
"type": "object",
"properties": {
"vnfInstanceSubscriptionFilter": {
- "description": "This type represents subscription filter criteria to match VNF instances.\n",
+ "description": "This type represents subscription filter criteria to match VNF instances. * NOTE 1:\tThe attributes \"vnfdIds\" and \"vnfProductsFromProviders\" are alternatives to reference to VNF instances\n that are based on certain VNFDs in a filter. They should not be used both in the same filter instance,\n but one alternative should be chosen.\n NOTE 2:\tThe attributes \"vnfInstanceIds\" and \"vnfInstanceNames\" are alternatives to reference to particular VNF\n instances in a filter. They should not be used both in the same filter instance, but one alternative\n should be chosen.\n",
"type": "object",
+ "anyOf": [
+ {
+ "oneOf": [
+ {
+ "required": ["vnfdId"]
+ },
+ {
+ "required": ["vnfProductsFromProviders"]
+ }
+ ]
+ },
+ {
+ "oneOf": [
+ {
+ "required": ["vnfInstanceIds"]
+ },
+ {
+ "required": ["vnfInstanceNames"]
+ }
+ ]
+ }
+ ],
"properties": {
"vnfdIds": {
- "description": "If present, match VNF instances that were created based on a VNFD identified by one of the vnfdId values listed in this attribute. The attributes \"vnfdIds\" and \"vnfProductsFromProviders\" are alternatives to reference to VNF instances that are based on certain VNFDs in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n",
+ "description": "If present, match VNF instances that were created based on a VNFD identified by one of the vnfdId values listed in this attribute. See note 1.\n",
"type": "array",
"items": {
"description": "An identifier with the intention of being globally unique.\n",
@@ -28,13 +46,11 @@
}
},
"vnfProductsFromProviders": {
- "description": "If present, match VNF instances that belong to VNF products from certain providers. The attributes \"vnfdIds\" and \"vnfProductsFromProviders\" are alternatives to reference to VNF instances that are based on certain VNFDs in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n",
+ "description": "If present, match VNF instances that belong to VNF products from certain providers. See note 1.\n",
"type": "array",
"items": {
"type": "object",
- "required": [
- "vnfProvider"
- ],
+ "required": ["vnfProvider"],
"properties": {
"vnfProvider": {
"description": "Name of the VNF provider to match.\n",
@@ -45,9 +61,7 @@
"type": "array",
"items": {
"type": "object",
- "required": [
- "vnfProductName"
- ],
+ "required": ["vnfProductName"],
"properties": {
"vnfProductName": {
"description": "Name of the VNF product to match.\n",
@@ -58,9 +72,7 @@
"type": "array",
"items": {
"type": "object",
- "required": [
- "vnfSoftwareVersion"
- ],
+ "required": ["vnfSoftwareVersion"],
"properties": {
"vnfSoftwareVersion": {
"description": "A version.\n",
@@ -84,7 +96,7 @@
}
},
"vnfInstanceIds": {
- "description": "If present, match VNF instances with an instance identifier listed in this attribute. The attributes \"vnfInstanceIds\" and \"vnfInstanceNames\" are alternatives to reference to particular VNF Instances in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n",
+ "description": "If present, match VNF instances with an instance identifier listed in this attribute. See note 2.\n",
"type": "array",
"items": {
"description": "An identifier with the intention of being globally unique.\n",
@@ -92,7 +104,7 @@
}
},
"vnfInstanceNames": {
- "description": "If present, match VNF instances with a VNF Instance Name listed in this attribute. The attributes \"vnfInstanceIds\" and \"vnfInstanceNames\" are alternatives to reference to particular VNF Instances in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n",
+ "description": "If present, match VNF instances with a VNF Instance Name listed in this attribute. See note 2.\n",
"type": "array",
"items": {
"type": "string"
@@ -100,6 +112,14 @@
}
}
},
+ "notificationTypes": {
+ "description": "Match particular notification types. \nPermitted values: -\tVnfIndicatorValueChangeNotification -\tSupportedIndicatorsChangeNotification See note.\n",
+ "type": "string",
+ "enum": [
+ "VnfIndicatorValueChangeNotification",
+ "SupportedIndicatorsChangeNotification"
+ ]
+ },
"indicatorIds": {
"description": "Match particular VNF indicator identifiers.\n",
"type": "array",
@@ -118,25 +138,20 @@
"_links": {
"description": "Links for this resource.\n",
"type": "object",
- "required": [
- "self"
- ],
+ "required": ["self"],
"properties": {
"self": {
- "description": "This type represents a link to a resource.\n",
+ "description": "This type represents a link to a resource using an absolute URI.\n",
"type": "object",
- "required": [
- "href"
- ],
+ "required": ["href"],
"properties": {
"href": {
- "description": "URI of the referenced resource.\n",
- "type": "string",
- "format": "url"
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
}
}
}
}
}
}
-}
+}
\ No newline at end of file
diff --git a/SOL003/VNFIndicator-API/schemas/VnfIndicatorSubscriptions.schema.json b/SOL003/VNFIndicator-API/schemas/VnfIndicatorSubscriptions.schema.json
index 987c0d713128c0d6dec31383604cb3da17540bd2..ec36ca6dd94757ea2c5cc1f2208a52e2d766af17 100644
--- a/SOL003/VNFIndicator-API/schemas/VnfIndicatorSubscriptions.schema.json
+++ b/SOL003/VNFIndicator-API/schemas/VnfIndicatorSubscriptions.schema.json
@@ -1 +1,160 @@
-{ "type": "array", "items": { "description": "This type represents a subscription related to notifications about VNF indicator value changes.\n", "type": "object", "required": [ "id", "callbackUri", "_links" ], "properties": { "id": { "description": "An identifier with the intention of being globally unique.\n", "type": "string" }, "filter": { "description": "This type represents a subscription filter related to notifications about VNF indicator value changes. At a particular nesting level in the filter structure, the following applies: All attributes shall match in order for the filter to match (logical \"and\" between different filter attributes). If an attribute is an array, the attribute shall match if at least one of the values in the array matches (logical \"or\" between the values of one filter attribute).\n", "type": "object", "properties": { "vnfInstanceSubscriptionFilter": { "description": "This type represents subscription filter criteria to match VNF instances.\n", "type": "object", "properties": { "vnfdIds": { "description": "If present, match VNF instances that were created based on a VNFD identified by one of the vnfdId values listed in this attribute. The attributes \"vnfdIds\" and \"vnfProductsFromProviders\" are alternatives to reference to VNF instances that are based on certain VNFDs in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n", "type": "array", "items": { "description": "An identifier with the intention of being globally unique.\n", "type": "string" } }, "vnfProductsFromProviders": { "description": "If present, match VNF instances that belong to VNF products from certain providers. The attributes \"vnfdIds\" and \"vnfProductsFromProviders\" are alternatives to reference to VNF instances that are based on certain VNFDs in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n", "type": "array", "items": { "type": "object", "required": [ "vnfProvider" ], "properties": { "vnfProvider": { "description": "Name of the VNF provider to match.\n", "type": "string" }, "vnfProducts": { "description": "If present, match VNF instances that belong to VNF products with certain product names, from one particular provider.\n", "type": "array", "items": { "type": "object", "required": [ "vnfProductName" ], "properties": { "vnfProductName": { "description": "Name of the VNF product to match.\n", "type": "string" }, "versions": { "description": "If present, match VNF instances that belong to VNF products with certain versions and a certain product name, from one particular provider.\n", "type": "array", "items": { "type": "object", "required": [ "vnfSoftwareVersion" ], "properties": { "vnfSoftwareVersion": { "description": "A version.\n", "type": "string" }, "vnfdVersions": { "description": "If present, match VNF instances that belong to VNF products with certain VNFD versions, a certain software version and a certain product name, from one particular provider.\n", "type": "array", "items": { "description": "A version.\n", "type": "string" } } } } } } } } } } }, "vnfInstanceIds": { "description": "If present, match VNF instances with an instance identifier listed in this attribute. The attributes \"vnfInstanceIds\" and \"vnfInstanceNames\" are alternatives to reference to particular VNF Instances in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n", "type": "array", "items": { "description": "An identifier with the intention of being globally unique.\n", "type": "string" } }, "vnfInstanceNames": { "description": "If present, match VNF instances with a VNF Instance Name listed in this attribute. The attributes \"vnfInstanceIds\" and \"vnfInstanceNames\" are alternatives to reference to particular VNF Instances in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n", "type": "array", "items": { "type": "string" } } } }, "indicatorIds": { "description": "Match particular VNF indicator identifiers.\n", "type": "array", "items": { "description": "An identifier that is unique within a VNF descriptor.\n", "type": "string" } } } }, "callbackUri": { "description": "The URI of the endpoint to send the notification to.\n", "type": "string", "format": "url" }, "_links": { "description": "Links for 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 the referenced resource.\n", "type": "string", "format": "url" } } } } } } }}
\ No newline at end of file
+{
+ "type": "array",
+ "items": {
+ "description": "This type represents a subscription related to notifications about VNF indicator value changes.\n",
+ "type": "object",
+ "required": ["id", "callbackUri", "_links"],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "filter": {
+ "description": "This type represents a subscription filter for notifications related to VNF indicators.\nAt a particular nesting level in the filter structure, the following applies: All attributes shall match in order for the filter to match (logical \"and\" between different filter attributes). If an attribute is an array, the attribute shall match if at least one of the values in the array matches (logical \"or\" between the values of one filter attribute).\nNOTE:\tThe permitted values of the \"notificationTypes\" attribute are spelled exactly as the names \n of the notification types to facilitate automated code generation systems.\n",
+ "type": "object",
+ "properties": {
+ "vnfInstanceSubscriptionFilter": {
+ "description": "This type represents subscription filter criteria to match VNF instances. * NOTE 1:\tThe attributes \"vnfdIds\" and \"vnfProductsFromProviders\" are alternatives to reference to VNF instances\n that are based on certain VNFDs in a filter. They should not be used both in the same filter instance,\n but one alternative should be chosen.\n NOTE 2:\tThe attributes \"vnfInstanceIds\" and \"vnfInstanceNames\" are alternatives to reference to particular VNF\n instances in a filter. They should not be used both in the same filter instance, but one alternative\n should be chosen.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "oneOf": [
+ {
+ "required": ["vnfdId"]
+ },
+ {
+ "required": ["vnfProductsFromProviders"]
+ }
+ ]
+ },
+ {
+ "oneOf": [
+ {
+ "required": ["vnfInstanceIds"]
+ },
+ {
+ "required": ["vnfInstanceNames"]
+ }
+ ]
+ }
+ ],
+ "properties": {
+ "vnfdIds": {
+ "description": "If present, match VNF instances that were created based on a VNFD identified by one of the vnfdId values listed in this attribute. See note 1.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ },
+ "vnfProductsFromProviders": {
+ "description": "If present, match VNF instances that belong to VNF products from certain providers. See note 1.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": ["vnfProvider"],
+ "properties": {
+ "vnfProvider": {
+ "description": "Name of the VNF provider to match.\n",
+ "type": "string"
+ },
+ "vnfProducts": {
+ "description": "If present, match VNF instances that belong to VNF products with certain product names, from one particular provider.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": ["vnfProductName"],
+ "properties": {
+ "vnfProductName": {
+ "description": "Name of the VNF product to match.\n",
+ "type": "string"
+ },
+ "versions": {
+ "description": "If present, match VNF instances that belong to VNF products with certain versions and a certain product name, from one particular provider.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": ["vnfSoftwareVersion"],
+ "properties": {
+ "vnfSoftwareVersion": {
+ "description": "A version.\n",
+ "type": "string"
+ },
+ "vnfdVersions": {
+ "description": "If present, match VNF instances that belong to VNF products with certain VNFD versions, a certain software version and a certain product name, from one particular provider.\n",
+ "type": "array",
+ "items": {
+ "description": "A version.\n",
+ "type": "string"
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ },
+ "vnfInstanceIds": {
+ "description": "If present, match VNF instances with an instance identifier listed in this attribute. See note 2.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ },
+ "vnfInstanceNames": {
+ "description": "If present, match VNF instances with a VNF Instance Name listed in this attribute. See note 2.\n",
+ "type": "array",
+ "items": {
+ "type": "string"
+ }
+ }
+ }
+ },
+ "notificationTypes": {
+ "description": "Match particular notification types. \nPermitted values: -\tVnfIndicatorValueChangeNotification -\tSupportedIndicatorsChangeNotification See note.\n",
+ "type": "string",
+ "enum": [
+ "VnfIndicatorValueChangeNotification",
+ "SupportedIndicatorsChangeNotification"
+ ]
+ },
+ "indicatorIds": {
+ "description": "Match particular VNF indicator identifiers.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "callbackUri": {
+ "description": "The URI of the endpoint to send the notification to.\n",
+ "type": "string",
+ "format": "url"
+ },
+ "_links": {
+ "description": "Links for this resource.\n",
+ "type": "object",
+ "required": ["self"],
+ "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"
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+}
diff --git a/SOL003/VNFIndicator-API/schemas/VnfIndicatorValueChangeNotification.schema.json b/SOL003/VNFIndicator-API/schemas/VnfIndicatorValueChangeNotification.schema.json
index 9e5c6758177599abbe74731801ce9738e31aecd0..8cfc37af21b7e1f46b0bd6cc0acc23d9c6efdab6 100644
--- a/SOL003/VNFIndicator-API/schemas/VnfIndicatorValueChangeNotification.schema.json
+++ b/SOL003/VNFIndicator-API/schemas/VnfIndicatorValueChangeNotification.schema.json
@@ -1,90 +1,79 @@
{
- "description": "This type represents a VNF indicator value change notification. The notification shall be triggered by the VNFM when the value of an indicator has changed.\n",
- "type": "object",
- "required": [
- "id",
- "notificationType",
- "subscriptionId",
- "timeStamp",
- "vnfIndicatorId",
- "value",
- "vnfInstanceId",
- "_links"
- ],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "notificationType": {
- "description": "Discriminator for the different notification types. Shall be set to \"VnfIndicatorValueChangeNotification\" for this notification type.\n",
- "type": "string",
- "enum": [
- "VnfIndicatorValueChangeNotification"
- ]
- },
- "subscriptionId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "timeStamp": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "vnfIndicatorId": {
- "description": "An identifier that is unique within a VNF descriptor.\n",
- "type": "string"
- },
- "name": {
- "description": "Human readable name of the VNF indicator. Shall be present if defined in the VNFD.\n",
- "type": "string"
- },
- "value": {
- "description": "Provides the value of the VNF indicator. The value format is defined in the VNFD. ETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on TOSCA specifications.\n",
- "type": "object"
- },
- "vnfInstanceId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "_links": {
- "description": "Links for this resource.\n",
- "type": "object",
- "required": [
- "vnfInstance",
- "subscription"
- ],
- "properties": {
- "vnfInstance": {
- "description": "This type represents a link to a resource.\n",
- "type": "object",
- "required": [
- "href"
- ],
- "properties": {
- "href": {
- "description": "URI of the referenced resource.\n",
- "type": "string",
- "format": "url"
- }
+ "description": "This type represents a VNF indicator value change notification.\nThe notification shall be triggered by the VNFM when the value of an indicator has changed.\nNOTE:\tETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on TOSCA specifications.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "notificationType",
+ "subscriptionId",
+ "timeStamp",
+ "vnfIndicatorId",
+ "value",
+ "vnfInstanceId",
+ "_links"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "notificationType": {
+ "description": "Discriminator for the different notification types. Shall be set to \"VnfIndicatorValueChangeNotification\" for this notification type.\n",
+ "type": "string",
+ "enum": ["VnfIndicatorValueChangeNotification"]
+ },
+ "subscriptionId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "timeStamp": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "vnfIndicatorId": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "name": {
+ "description": "Human readable name of the VNF indicator. Shall be present if defined in the VNFD.\n",
+ "type": "string"
+ },
+ "value": {
+ "description": "Provides the value of the VNF indicator. The value format is defined in the VNFD. See note.\n",
+ "type": "object"
+ },
+ "vnfInstanceId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "_links": {
+ "description": "Links for this resource.\n",
+ "type": "object",
+ "required": ["vnfInstance", "subscription"],
+ "properties": {
+ "vnfInstance": {
+ "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": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
}
- },
- "subscription": {
- "description": "This type represents a link to a resource.\n",
- "type": "object",
- "required": [
- "href"
- ],
- "properties": {
- "href": {
- "description": "URI of the referenced resource.\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": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
}
}
}
}
}
- }
\ No newline at end of file
+ }
+}
diff --git a/SOL003/VNFIndicator-API/schemas/vnfIndicator.schema.json b/SOL003/VNFIndicator-API/schemas/vnfIndicator.schema.json
index 2d7f7b52452f72d0587f812484f7bc6b00884722..d3da336c36a8fb2670d9770f0c020ca89596d71e 100644
--- a/SOL003/VNFIndicator-API/schemas/vnfIndicator.schema.json
+++ b/SOL003/VNFIndicator-API/schemas/vnfIndicator.schema.json
@@ -1 +1,52 @@
-{ "description": "This type represents a VNF indicator value.\n", "type": "object", "required": [ "id", "value", "vnfInstanceId", "_links" ], "properties": { "id": { "description": "An identifier that is unique within a VNF descriptor.\n", "type": "string" }, "name": { "description": "Human readable name of the indicator. Shall be present if defined in the VNFD.\n", "type": "string" }, "value": { "description": "Provides the value of the indicator. The value format is defined in the VNFD. ETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on TOSCA specifications.\n", "type": "object" }, "vnfInstanceId": { "description": "An identifier with the intention of being globally unique.\n", "type": "string" }, "_links": { "description": "Links for this resource.\n", "type": "object", "required": [ "self", "vnfInstance" ], "properties": { "self": { "description": "This type represents a link to a resource.\n", "type": "object", "required": [ "href" ], "properties": { "href": { "description": "URI of the referenced resource.\n", "type": "string", "format": "url" } } }, "vnfInstance": { "description": "This type represents a link to a resource.\n", "type": "object", "required": [ "href" ], "properties": { "href": { "description": "URI of the referenced resource.\n", "type": "string", "format": "url" } } } } } }}
\ No newline at end of file
+{
+ "description": "This type represents a VNF indicator value.\nNOTE:\tETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on TOSCA specifications.\n",
+ "type": "object",
+ "required": ["id", "value", "vnfInstanceId", "_links"],
+ "properties": {
+ "id": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "name": {
+ "description": "Human readable name of the indicator. Shall be present if defined in the VNFD.\n",
+ "type": "string"
+ },
+ "value": {
+ "description": "Provides the value of the indicator. The value format is defined in the VNFD. See note.\n",
+ "type": "object"
+ },
+ "vnfInstanceId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "_links": {
+ "description": "Links for this resource.\n",
+ "type": "object",
+ "required": ["self", "vnfInstance"],
+ "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"
+ }
+ }
+ },
+ "vnfInstance": {
+ "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"
+ }
+ }
+ }
+ }
+ }
+ }
+}
\ No newline at end of file
diff --git a/SOL003/VNFIndicator-API/schemas/vnfIndicators.schema.json b/SOL003/VNFIndicator-API/schemas/vnfIndicators.schema.json
index 7aae0e6d20e1514b0215e1957d6513ae5e9681dc..5db41b729a0b54e1b35c0636a880bb6b93217eff 100644
--- a/SOL003/VNFIndicator-API/schemas/vnfIndicators.schema.json
+++ b/SOL003/VNFIndicator-API/schemas/vnfIndicators.schema.json
@@ -1 +1,55 @@
-{ "type": "array", "items": { "description": "This type represents a VNF indicator value.\n", "type": "object", "required": [ "id", "value", "vnfInstanceId", "_links" ], "properties": { "id": { "description": "An identifier that is unique within a VNF descriptor.\n", "type": "string" }, "name": { "description": "Human readable name of the indicator. Shall be present if defined in the VNFD.\n", "type": "string" }, "value": { "description": "Provides the value of the indicator. The value format is defined in the VNFD. ETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on TOSCA specifications.\n", "type": "object" }, "vnfInstanceId": { "description": "An identifier with the intention of being globally unique.\n", "type": "string" }, "_links": { "description": "Links for this resource.\n", "type": "object", "required": [ "self", "vnfInstance" ], "properties": { "self": { "description": "This type represents a link to a resource.\n", "type": "object", "required": [ "href" ], "properties": { "href": { "description": "URI of the referenced resource.\n", "type": "string", "format": "url" } } }, "vnfInstance": { "description": "This type represents a link to a resource.\n", "type": "object", "required": [ "href" ], "properties": { "href": { "description": "URI of the referenced resource.\n", "type": "string", "format": "url" } } } } } } }}
\ No newline at end of file
+{
+ "type": "array",
+ "items": {
+ "description": "This type represents a VNF indicator value.\nNOTE:\tETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on TOSCA specifications.\n",
+ "type": "object",
+ "required": ["id", "value", "vnfInstanceId", "_links"],
+ "properties": {
+ "id": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "name": {
+ "description": "Human readable name of the indicator. Shall be present if defined in the VNFD.\n",
+ "type": "string"
+ },
+ "value": {
+ "description": "Provides the value of the indicator. The value format is defined in the VNFD. See note.\n",
+ "type": "object"
+ },
+ "vnfInstanceId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "_links": {
+ "description": "Links for this resource.\n",
+ "type": "object",
+ "required": ["self", "vnfInstance"],
+ "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"
+ }
+ }
+ },
+ "vnfInstance": {
+ "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"
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+}
\ No newline at end of file
diff --git a/SOL003/VNFLifecycleManagement-API/ApiVersion.robot b/SOL003/VNFLifecycleManagement-API/ApiVersion.robot
index c77088874c5a1f757d5d13a416530d7e46571810..5b311ffb630b059790d1c09d6a2b3bc8441668fb 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] v3.5.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.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 183dfb19efc0338b3b8ab112bf03afecee6f39b9..777f97321481791e39d7d8357322e9eeb06086e8 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] v3.6.1
+ ... Reference: Clause 5.4.17.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.17.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.17.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.17.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.17.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.17.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.17.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.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 ffb32e234b41fd2308ffec9a68f4003dcb30c876..de51239d67e33fb112e0bd202cdccd8277083da8 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] v3.6.1
+ ... Reference: Clause 5.4.17 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.3.10 - ETSI GS NFV-SOL 003 [1] v4.3.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 62ab3ee558b32cc0dcf30e8b075b34590a83014c..c8166226b42613fb9aaad198a1dfe5d10d8d2117 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] v3.6.1
+ ... Reference: Clause 5.4.11a.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.11a.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.11a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.11a.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.11a.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.11a.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.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 f6d35bfd34546dc897266ac0e668d70f7f09943a..2cc5c9a66a6b5a03a03fd851a4e82313dbed4613 100644
--- a/SOL003/VNFLifecycleManagement-API/ChangeExternalVNFConnectivityTask.robot
+++ b/SOL003/VNFLifecycleManagement-API/ChangeExternalVNFConnectivityTask.robot
@@ -12,20 +12,21 @@ 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] v3.6.1
+ ... Reference: Clause 5.4.11.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: in response header Location shall not be null
POST Change External VNF Connectivity
Check HTTP Response Status Code Is 202
- Check Operation Occurrence Id existence
+ Check HTTP Response Header Contains Location
+ Check Individual VNF LCM operation occurrence operationState is STARTING
GET Change external VNF connectivity - Method not implemented
[Documentation] Test ID: 7.3.1.10.2
... 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] v3.6.1
+ ... Reference: Clause 5.4.11.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -37,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] v3.6.1
+ ... Reference: Clause 5.4.11.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -49,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] v3.6.1
+ ... Reference: Clause 5.4.11.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -61,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] v3.6.1
+ ... Reference: Clause 5.4.11.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.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 bbce7c0529ced3242dce283f721b6d5d398606d1..29221a24d7b6078824a55bdc1bc4080c609f971c 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] v3.6.1
+ ... Reference: Clause 5.4.11 - ETSI GS NFV-SOL 003 [1] v4.3.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 9429b18dd340b238e1c2a4689566044a8666fa72..6449c94c0d0cbe94a3a88fe7c31666744fb9680c 100644
--- a/SOL003/VNFLifecycleManagement-API/ChangeVNFFlavourTask.robot
+++ b/SOL003/VNFLifecycleManagement-API/ChangeVNFFlavourTask.robot
@@ -12,20 +12,21 @@ 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] v3.6.1
+ ... Reference: Clause 5.4.7.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: in response header Location shall not be null
POST Change VNF deployment flavour
Check HTTP Response Status Code Is 202
- Check Operation Occurrence Id existence
+ Check HTTP Response Header Contains Location
+ Check Individual VNF LCM operation occurrence operationState is STARTING
POST Change deployment flavour of a vnfInstance Conflict (Not-Instantiated)
[Documentation] Test ID: 7.3.1.6.2
... 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] v3.6.1
+ ... Reference: Clause 5.4.7.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -38,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] v3.6.1
+ ... Reference: Clause 5.4.7.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -51,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] v3.6.1
+ ... Reference: Clause 5.4.7.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -63,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] v3.6.1
+ ... Reference: Clause 5.4.7.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -75,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] v3.6.1
+ ... Reference: Clause 5.4.7.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -87,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] v3.6.1
+ ... Reference: Clause 5.4.7.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.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 6a568bab3753843101d1fd5ed21be0c98b6f605f..3d4460210e72e81e3087092c53a976c7741bb20e 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] v3.6.1
+ ... Reference: Clause 5.4.7 - ETSI GS NFV-SOL 003 [1] v4.3.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 cb0e3529b1b427dea27e8fec7e0356412aaa5846..462c333d2746521a03f697dd8675df7cde160175 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] v3.6.1
+ ... Reference: Clause 5.4.21.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.21.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.21.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: VNF instance is in NOT_INSTANTIATED state.
... Post-Conditions: none
@@ -52,7 +52,7 @@ POST Create VNF Snapshot Task - UNPROCESSIBLE ENTITY
... Test title: POST Create VNF Snapshot Task - UNPROCESSIBLE ENTITY
... 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] v3.6.1
+ ... Reference: Clause 5.4.21.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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
@@ -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] v3.6.1
+ ... Reference: Clause 5.4.21.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.21.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.21.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.21.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.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 a86840659520cc64c08e72a5713e436b407455c6..a9a438fd3a0b8c540a26e6f056f3d45f16792347 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] v3.6.1
+ ... Reference: Clause 5.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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 b3a9908e4be9a65b3e2dbd6cc8ee59e6e3c67379..57788346983f33b2a488c9710631b62efb255ee6 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] v3.6.1
+ ... Reference: Clause 5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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 a1b21fc88f978701a46406df6a12c87695ea9c07..999ec95e2f72e97678919180b8e645415c7bf228 100644
--- a/SOL003/VNFLifecycleManagement-API/FailOperationTask.robot
+++ b/SOL003/VNFLifecycleManagement-API/FailOperationTask.robot
@@ -12,13 +12,13 @@ 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] v3.6.1
+ ... Reference: Clause 5.4.16.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: VNF resource state is FINALLY_FAILED
Post Fail operation
Check HTTP Response Status Code Is 202
- Check Operation Occurrence Id existence
+ Check HTTP Response Header Contains Location
Check operation resource state is FINALLY_FAILED
Post Fail operation task Conflict (Not-FAILED_TEMP)
@@ -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] v3.6.1
+ ... Reference: Clause 5.4.16.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.16.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.16.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.16.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.16.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.16.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.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 096660996a6fa1dd078ee628a57eb56901df4350..ad52b6092e42f02edcaa17e272948b8f400f767f 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] v3.6.1
+ ... Reference: Clause 5.4.16 - ETSI GS NFV-SOL 003 [1] v4.3.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 2743da5903f01f6b436584afdc8cf69cd1ae37e7..9456305c71c173874eac7eb55a5636dbb27ff2cd 100644
--- a/SOL003/VNFLifecycleManagement-API/HealVNFTask.robot
+++ b/SOL003/VNFLifecycleManagement-API/HealVNFTask.robot
@@ -12,20 +12,21 @@ 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] v3.6.1
+ ... Reference: Clause 5.4.9.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
POST Heal VNF
Check HTTP Response Status Code Is 202
- Check Operation Occurrence Id existence
+ Check HTTP Response Header Contains Location
+ Check Individual VNF LCM operation occurrence operationState is STARTING
POST Heal a vnfInstance Conflict (Not-Instantiated)
[Documentation] Test ID: 7.3.1.8.2
... 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] v3.6.1
+ ... Reference: Clause 5.4.9.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -38,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] v3.6.1
+ ... Reference: Clause 5.4.9.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -51,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] v3.6.1
+ ... Reference: Clause 5.4.9.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -63,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] v3.6.1
+ ... Reference: Clause 5.4.9.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -75,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] v3.6.1
+ ... Reference: Clause 5.4.9.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -87,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] v3.6.1
+ ... Reference: Clause 5.4.9.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.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 70d32f3dcf389c54aa8b67acc75edb68852c14b5..bde625380b89ccd66ace01a3fa86ef4c9cb6a17b 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] v3.6.1
+ ... Reference: Clause 5.4.9 - ETSI GS NFV-SOL 003 [1] v4.3.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 1766408afd5f60e39d36289d0cd0c151aba22007..7f97967f5509d4e15e4ab9603c1f3998c76d5544 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] v3.6.1
+ ... Reference: Clause 5.4.19.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.19.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.19.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.19.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.19.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.19.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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 8df439c5ee4afcc241cbe556767a13dd94c3a38d..6564a97caa264fbaafdd75bc2ce9790167ea48a3 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] v3.6.1
+ ... Reference: Clause 5.4.3.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -28,11 +28,12 @@ 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] v3.6.1
+ ... Reference: Clause 5.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
GET individual vnfInstance
+ Check HTTP Response Header Contains ETag and Last-Modified
Check HTTP Response Status Code Is 200
Check HTTP Response Body Json Schema Is vnfInstance
Check HTTP Response Body vnfInstance content against VNF Descriptor
@@ -42,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] v3.6.1
+ ... Reference: Clause 5.4.3.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -54,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] v3.6.1
+ ... Reference: Clause 5.4.3.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: VNFInstance modified
@@ -67,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] v3.6.1
+ ... Reference: Clause 5.4.3.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -80,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] v3.6.1
+ ... Reference: Clause 5.4.3.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: VNFInstance not modified
@@ -93,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] v3.6.1
+ ... Reference: Clause 5.4.3.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: VNFInstance deleted
@@ -105,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] v3.6.1
+ ... Reference: Clause 5.4.3.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: Resources are not deleted
@@ -119,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] v3.6.1
+ ... Reference: Clause 5.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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 cd67168ed8e8db4e0d4e7d96e33dccff71b26178..dcae1ad2fe34ed2237e278671712087355b9be07 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] v3.6.1
+ ... Reference: Clause 5.4.24.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -19,11 +19,12 @@ 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] v3.6.1
+ ... Reference: Clause 5.4.24.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
GET individual VNF Snapshot
+ Check HTTP Response Header Contains ETag and Last-Modified
Check HTTP Response Status Code Is 200
Check HTTP Response Body Json Schema Is VnfSnapshotInfo
@@ -32,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] v3.6.1
+ ... Reference: Clause 5.4.24.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -45,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] v3.6.1
+ ... Reference: Clause 5.4.24.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: VNF Snapshot not modified
@@ -57,11 +58,12 @@ 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] v3.6.1
+ ... Reference: Clause 5.4.24.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: VNF Snapshot modified
PATCH individual VNF Snapshot
+ Check HTTP Response Header Contains ETag and Last-Modified
Check HTTP Response Status Code Is 200
Check HTTP Response Body Json Schema Is VnfSnapshotInfoModifications
@@ -70,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] v3.6.1
+ ... Reference: Clause 5.4.24.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.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
@@ -83,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] v3.6.1
+ ... Reference: Clause 5.4.24.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: VNF snapshot is not modified
@@ -96,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] v3.6.1
+ ... Reference: Clause 5.4.24.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: VNF Snapshot deleted
@@ -109,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] v3.6.1
+ ... Reference: Clause 5.4.24.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.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 49c8dcbddbee1900a7d31693b0f7d73341b9c347..6791de45b537724d0ba1c769867f7be7c9446a7b 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] v3.6.1
+ ... Reference: Clause 5.4.13.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.13.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.13.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.13.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.13.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.13.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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 ecd047ebf0c56ebc3f3193882050583e2c60ccb3..f4de0362c81e0557f950abeaae0d7091dd8bad27 100644
--- a/SOL003/VNFLifecycleManagement-API/InstantiateVNFTask.robot
+++ b/SOL003/VNFLifecycleManagement-API/InstantiateVNFTask.robot
@@ -13,20 +13,21 @@ 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] v3.6.1
+ ... Reference: Clause 5.4.4.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
POST instantiate individual vnfInstance
Check HTTP Response Status Code Is 202
- Check Operation Occurrence Id existence
+ Check HTTP Response Header Contains Location
+ Check Individual VNF LCM operation occurrence operationState is STARTING
Instantiate a vnfInstance Conflict
[Documentation] Test ID: 7.3.1.3.2
... 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] v3.6.1
+ ... Reference: Clause 5.4.4.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -39,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] v3.6.1
+ ... Reference: Clause 5.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -51,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] v3.6.1
+ ... Reference: Clause 5.4.4.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -63,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] v3.6.1
+ ... Reference: Clause 5.4.4.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -75,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] v3.6.1
+ ... Reference: Clause 5.4.4.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.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 59a1ac3f8f0bdb0fbeebbaa65b796d75c7104d1b..c2ad47b788b3968b4b999585ce3d9f36374805d8 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] v3.6.1
+ ... Reference: Clause 5.4.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: NFVO is able to receive notifications from VNFM
... Post-Conditions: VNF instance in INSTANTIATED state
@@ -32,6 +32,42 @@ VNF Instantiation
Check Operation Notification For Instantiation PROCESSING
Check Operation Notification For Instantiation COMPLETED
Check Postcondition VNF Status INSTANTIATED
+
+VNF Instantiation with attribute instantiationLevelId
+ [Documentation] Test ID: 7.3.1.26.2
+ ... 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
+ ... Config ID: Config_prod_VNFM
+ ... Applicability: NFVO is able to receive notifications from VNFM
+ ... Post-Conditions: VNF instance in INSTANTIATED state
+ Send VNF Instantiation Request with attribute instantiationLevelId
+ Check HTTP Response Status Code Is 202
+ Check HTTP Response Header Contains Location
+ Check Operation Occurrence Id existence
+ Check Operation Notification For Instantiation STARTING
+ Check Operation Notification For Instantiation PROCESSING
+ Check Operation Notification For Instantiation COMPLETED
+ Check Postcondition VNF Status INSTANTIATED
+
+VNF Instantiation with attribute targetScaleLevelInfo
+ [Documentation] Test ID: 7.3.1.26.3
+ ... 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
+ ... Config ID: Config_prod_VNFM
+ ... Applicability: NFVO is able to receive notifications from VNFM
+ ... Post-Conditions: VNF instance in INSTANTIATED state
+ Send VNF Instantiation Request with attribute targetScaleLevelInfo
+ Check HTTP Response Status Code Is 202
+ Check HTTP Response Header Contains Location
+ Check Operation Occurrence Id existence
+ Check Operation Notification For Instantiation STARTING
+ Check Operation Notification For Instantiation PROCESSING
+ Check Operation Notification For Instantiation COMPLETED
+ Check Postcondition VNF Status INSTANTIATED
*** Keywords ***
Send VNF Instantiation Request
@@ -42,6 +78,24 @@ Send VNF Instantiation Request
${body}= Get File jsons/instantiateVnfRequest.json
${response}= Post ${apiRoot}/${apiName}/${apiMajorVersion}/vnf_instances/${vnfInstanceId}/instantiate ${body}
+Send VNF Instantiation Request with attribute instantiationLevelId
+ Log Instantiate a VNF Instance
+ Set Headers {"Accept":"${ACCEPT}"}
+ Set Headers {"Content-Type": "${CONTENT_TYPE}"}
+ Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"${AUTHORIZATION_HEADER}":"${AUTHORIZATION_TOKEN}"}
+ ${template}= Get File jsons/instantiateVnfRequestInstantiationLevelId.json
+ ${body}= Format String ${template} instantiationLevelId= ${instantiationLevelId}
+ ${response}= Post ${apiRoot}/${apiName}/${apiMajorVersion}/vnf_instances/${vnfInstanceId}/instantiate ${body}
+
+Send VNF Instantiation Request with attribute targetScaleLevelInfo
+ Log Instantiate a VNF Instance
+ Set Headers {"Accept":"${ACCEPT}"}
+ Set Headers {"Content-Type": "${CONTENT_TYPE}"}
+ Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"${AUTHORIZATION_HEADER}":"${AUTHORIZATION_TOKEN}"}
+ ${template}= Get File jsons/instantiateVnfRequestTargetScaleLevelInfo.json
+ ${body}= Format String ${template} aspectId=${scaleAspectId}
+ ${response}= Post ${apiRoot}/${apiName}/${apiMajorVersion}/vnf_instances/${vnfInstanceId}/instantiate ${body}
+
Check Operation Notification For Instantiation
[Arguments] ${status}
Check Operation Notification VnfLcmOperationOccurrenceNotification ${status}
diff --git a/SOL003/VNFLifecycleManagement-API/ModifyVNFInformationWorkflow.robot b/SOL003/VNFLifecycleManagement-API/ModifyVNFInformationWorkflow.robot
index 6fda691354fd72fb4c46b01ec417b81c2dca1c54..5be4723e000784a1d0bd7506addd79aeba48c5a3 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] v3.6.1
+ ... Reference: Clause 5.3.6 - ETSI GS NFV-SOL 003 [1] v4.3.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 09cbc320369776fc03aa8c3ccbde56e353823669..abfaa9d5b081c3f990d74dff13df690c49d3024b 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] v3.6.1
+ ... Reference: Clause 5.4.20.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.20.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.20.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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 2b269cd7b165633b2dfe04053ba6e8449ea9762e..d66983b1449ca07b0ccf2e32e1a548f06ae6d7b1 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] v3.6.1
+ ... Reference: Clause 5.4.20.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.20.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.20.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.18.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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 a05cd466506d2dcfddf50db4bdb85f45b8728967..c77030125f6e4db6c600437bc0c88db5987aa758 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] v3.6.1
+ ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.10.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.10.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.10.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.10.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.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 06f6c318fa45ca1bfcd424b8cb114689aa9d6214..a678af07e528d37f839a70824b6c038b9621e834 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] v3.6.1
+ ... Reference: Clause 5.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.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 19bd00ec07b27394ca782f2db6c9545263515f2c..2c480c27383427efdfb1570467a721b3dbc29ba2 100644
--- a/SOL003/VNFLifecycleManagement-API/RetryOperationTask.robot
+++ b/SOL003/VNFLifecycleManagement-API/RetryOperationTask.robot
@@ -15,20 +15,21 @@ 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] v3.6.1
+ ... Reference: Clause 5.4.14.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
Post Retry operation
Check HTTP Response Status Code Is 202
- Check Operation Occurrence Id existence
+ Check HTTP Response Header Contains Location
+ Check Individual VNF LCM operation occurrence operationState is STARTING
Post Retry operation task Conflict (Not-FAILED_TEMP)
[Documentation] Test ID: 7.3.1.13.2
... 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] v3.6.1
+ ... Reference: Clause 5.4.14.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -41,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] v3.6.1
+ ... Reference: Clause 5.4.14.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -54,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] v3.6.1
+ ... Reference: Clause 5.4.14.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -66,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] v3.6.1
+ ... Reference: Clause 5.4.14.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -78,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] v3.6.1
+ ... Reference: Clause 5.4.14.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -90,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] v3.6.1
+ ... Reference: Clause 5.4.14.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.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 1282071330b4d10ac9b4d800a362796275fb969e..39509283ad7ae96023eae2b0165b4145182a3027 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] v3.6.1
+ ... Reference: Clause 5.3.10 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.3.10 - ETSI GS NFV-SOL 003 [1] v4.3.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 a9732ae198fc0b6eeb42affa43e93e2daa453d7f..5ffc640159dc82c60d2a66c275040925444f98a6 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] v3.6.1
+ ... Reference: Clause 5.4.22.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.22.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.22.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.22.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.22.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.22.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.22.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.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 50904098a093fb91b815432cca7fa398cb48746d..26556498aeace7c2599e57ca94268d94d8ff7e0b 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] v3.6.1
+ ... Reference: Clause 5.3.11 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.3.10 - ETSI GS NFV-SOL 003 [1] v4.3.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 c4a3c3518649781ab41bafd065e86d5aa6041c37..4e1193ea2170690873ba83e3ca0547b6d8f51c31 100644
--- a/SOL003/VNFLifecycleManagement-API/RollbackOperationTask.robot
+++ b/SOL003/VNFLifecycleManagement-API/RollbackOperationTask.robot
@@ -14,20 +14,21 @@ 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] v3.6.1
+ ... Reference: Clause 5.4.15.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
Post Rollback operation
Check HTTP Response Status Code Is 202
- Check Operation Occurrence Id existence
+ Check HTTP Response Header Contains Location
+ Check Individual VNF LCM operation occurrence operationState is STARTING
POST Rollback operation task Conflict (Not-FAILED_TEMP)
[Documentation] Test ID: 7.3.1.14.2
... 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] v3.6.1
+ ... Reference: Clause 5.4.15.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -40,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] v3.6.1
+ ... Reference: Clause 5.4.15.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -53,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] v3.6.1
+ ... Reference: Clause 5.4.15.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -65,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] v3.6.1
+ ... Reference: Clause 5.4.15.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -77,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] v3.6.1
+ ... Reference: Clause 5.4.15.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -89,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] v3.6.1
+ ... Reference: Clause 5.4.15.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.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 656c7d5641a92e66bf0a479272aa23281d130a2e..d549acbab6286913e08820e33171c82c5257e94b 100644
--- a/SOL003/VNFLifecycleManagement-API/ScaleVNFTask.robot
+++ b/SOL003/VNFLifecycleManagement-API/ScaleVNFTask.robot
@@ -13,20 +13,21 @@ 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] v3.6.1
+ ... Reference: Clause 5.4.5.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
POST Scale vnfInstance
Check HTTP Response Status Code Is 202
- Check Operation Occurrence Id existence
+ Check HTTP Response Header Contains Location
+ Check Individual VNF LCM operation occurrence operationState is STARTING
POST Scale a vnfInstance Conflict (Not-Instantiated)
[Documentation] Test ID: 7.3.1.4.2
... 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] v3.6.1
+ ... Reference: Clause 5.4.5.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -39,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] v3.6.1
+ ... Reference: Clause 5.4.5.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -52,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] v3.6.1
+ ... Reference: Clause 5.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -64,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] v3.6.1
+ ... Reference: Clause 5.4.5.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -76,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] v3.6.1
+ ... Reference: Clause 5.4.5.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -88,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] v3.6.1
+ ... Reference: Clause 5.4.5.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.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 02d4b797ed92d1aa53ff7543b9f438806d29a9fc..b083243c863af7c906d2a5a23209e99a482b578b 100644
--- a/SOL003/VNFLifecycleManagement-API/ScaleVNFToLevelTask.robot
+++ b/SOL003/VNFLifecycleManagement-API/ScaleVNFToLevelTask.robot
@@ -7,25 +7,26 @@ Library JSONSchemaLibrary schemas/
Resource VnfLcmMntOperationKeywords.robot
*** Test Cases ***
-POST Scale a vnfInstance to level
+POST Scale a vnfInstance to level - with InstantiationLevelId attribute
[Documentation] Test ID: 7.3.1.5.1
... 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] v3.6.1
+ ... Reference: Clause 5.4.6.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
- POST Scale vnfInstance to level
+ POST Scale vnfInstance to level with InstantiationLevelId attribute
Check HTTP Response Status Code Is 202
- Check Operation Occurrence Id existence
+ Check HTTP Response Header Contains Location
+ Check Individual VNF LCM operation occurrence operationState is STARTING
POST Scale a vnfInstance to level Conflict (Not-Instantiated)
[Documentation] Test ID: 7.3.1.5.2
... 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] v3.6.1
+ ... Reference: Clause 5.4.6.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -38,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] v3.6.1
+ ... Reference: Clause 5.4.6.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -51,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] v3.6.1
+ ... Reference: Clause 5.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -63,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] v3.6.1
+ ... Reference: Clause 5.4.6.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -75,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] v3.6.1
+ ... Reference: Clause 5.4.6.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -87,9 +88,22 @@ 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] v3.6.1
+ ... Reference: Clause 5.4.6.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
DELETE Scale vnfInstance to level
- Check HTTP Response Status Code Is 405
\ No newline at end of file
+ Check HTTP Response Status Code Is 405
+
+POST Scale a vnfInstance to level - with scaleInfo attribute
+ [Documentation] Test ID: 7.3.1.5.8
+ ... 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
+ ... Config ID: Config_prod_VNFM
+ ... Applicability: none
+ ... Post-Conditions: none
+ POST Scale vnfInstance to level with scaleInfo attribute
+ Check HTTP Response Status Code Is 202
+ Check Operation Occurrence Id existence
\ No newline at end of file
diff --git a/SOL003/VNFLifecycleManagement-API/ScaleVNFToLevelWorkflow.robot b/SOL003/VNFLifecycleManagement-API/ScaleVNFToLevelWorkflow.robot
index 0718fc9a2349f8cef09773c9b424ccbeddcf5a3c..636082f6080638cbd307a4083c1e0c4966df00ea 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] v3.6.1
+ ... Reference: Clause 5.4.6 - ETSI GS NFV-SOL 003 [1] v4.3.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 2d333c3809b10a576bb06982f1c22f88b944599e..7068248f529475e25c398acf1b78d231ff939903 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] v3.6.1
+ ... Reference: Clause 5.4.5 - ETSI GS NFV-SOL 003 [1] v4.3.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 151e1fc22f43043c74623234c53525de535dd160..a32dc7cce29c4bba7c80648244a2bc9924cf0f35 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] v3.6.1
+ ... Reference: Clause 5.4.18.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.18.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.18.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.18.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.18.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.18.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.18.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.18.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.18.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.18.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.18.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -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] v3.6.1
+ ... Reference: Clause 5.4.18.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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 44f069453460fadf0fb3b77ef618c18a5591ac73..71d70c8254068f5b290c7ecd1bc4c465281ba8c3 100644
--- a/SOL003/VNFLifecycleManagement-API/TerminateVNFTask.robot
+++ b/SOL003/VNFLifecycleManagement-API/TerminateVNFTask.robot
@@ -13,20 +13,21 @@ 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] v3.6.1
+ ... Reference: Clause 5.4.8.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
POST Terminate VNF
Check HTTP Response Status Code Is 202
- Check Operation Occurrence Id existence
+ Check HTTP Response Header Contains Location
+ Check Individual VNF LCM operation occurrence operationState is STARTING
POST Terminate a vnfInstance Conflict (Not-Instantiated)
[Documentation] Test ID: 7.3.1.7.2
... 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] v3.6.1
+ ... Reference: Clause 5.4.8.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -39,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] v3.6.1
+ ... Reference: Clause 5.4.8.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -51,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] v3.6.1
+ ... Reference: Clause 5.4.8.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -63,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] v3.6.1
+ ... Reference: Clause 5.4.8.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -75,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] v3.6.1
+ ... Reference: Clause 5.4.8.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.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 7faec489e3462d73582271d4ca084ec551350657..eb6c4784bded10b9841573f0d3023de2d8788ffe 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] v3.6.1
+ ... Reference: Clause 5.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.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 4b36a7a4ce4f622391c9aca802568bd9c9d1a219..a49eb2caaf8a8d45e271a3068429d5e2e2722b5e 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] v3.6.1
+ ... Reference: Clause 5.4.2.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1).
- ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v3.6.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.3.1).
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1).
- ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v3.6.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.3.1).
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.2.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.2.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.2.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1).
- ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v3.6.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.3.1).
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -205,7 +205,7 @@ POST Create a new vnfInstance - Unprocessible Entity
... Test title: POST Create a new vnfInstance - Unprocessible Entity
... 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] v3.6.1
+ ... Reference: Clause 5.4.2.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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 d4b84de4ff7b4c970823f14e81be186a2c47a08f..2fd0ddad8af1d2f66fcf1d7a1ec7c69b82576ae3 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] v3.6.1
+ ... Reference: Clause 5.4.23.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.23.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.23.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.23.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.23.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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 5c2237879e952be6a17bc81a8dc1a4b237d10a46..18e7ebaa62b99a2e44176af1202a91e0e6c36cdf 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] v3.6.1
+ ... Reference: Clause 5.4.25.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.25.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.25.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.25.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.25.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.25.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.25.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.25.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.25.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFLifecycleManagement-API/VnfLcmMntOperationKeywords.robot b/SOL003/VNFLifecycleManagement-API/VnfLcmMntOperationKeywords.robot
index ae0e906fb33223fe1fb5832c99b1b2bda19a7938..180d7fa340bcc2efa08593d9a07f2f4ce8841e63 100644
--- a/SOL003/VNFLifecycleManagement-API/VnfLcmMntOperationKeywords.robot
+++ b/SOL003/VNFLifecycleManagement-API/VnfLcmMntOperationKeywords.robot
@@ -32,6 +32,13 @@ Check HTTP Response Status Code Is
Should Be Equal As Strings ${response['status']} ${expected_status}
Log Status code validated
+Check HTTP Response Header Contains ETag and Last-Modified
+ Pass Execution If ${HEADER_TEST_SUPPORTED} == 0 Headers testing not supported. Skipping the Test.
+ Log ${response['headers']}
+ Should Contain ${response['headers']} Etag
+ Should Contain ${response['headers']} Last-Modified
+ Log Etag and Last-Modified Headers are present
+
Check Operation Occurrence IdS
${vnfLcmOpOccId}= Get Value From Json ${response['headers']} $..Location
Should Not Be Empty ${vnfLcmOpOccId}
@@ -107,6 +114,14 @@ Check HTTP Response Header Contains
Should Contain ${response['headers']} ${CONTENT_TYPE}
Log Header is present
+Check Individual VNF LCM operation occurrence operationState is
+ [Arguments] ${status}
+ Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"${AUTHORIZATION_HEADER}":"${AUTHORIZATION_TOKEN}"}
+ ${opOccResponse}= Get ${response['headers']['Location']}
+ Log Validate operationState
+ Should Be Equal as Strings ${opOccResponse['body']['operationState']} ${status}
+ Log operationState validated
+
Send VNF Scale Out Request
Log Trying to scale a vnf Instance
Set Headers {"Accept":"${ACCEPT}"}
@@ -211,49 +226,6 @@ Send Cancel Operation Request
Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"${AUTHORIZATION_HEADER}":"${AUTHORIZATION_TOKEN}"}
${response}= Post ${apiRoot}/${apiName}/${apiMajorVersion}/vnf_lcm_op_occs/${vnfLcmOpOccId}/cancel ${CancelMode}
-Create a new Grant - Synchronous mode
- [Arguments] ${vnfInstanceId} ${vnfLcmOpOccId} ${operation}
- Log Request a new Grant for a VNF LCM operation by POST to ${apiRoot}/${apiName}/${apiMajorVersion}/grants
- Pass Execution If ${SYNC_MODE} == 0 The Granting process is asynchronous mode. Skipping the test
- Set Headers {"Accept":"${ACCEPT}"}
- Set Headers {"Content-Type": "${CONTENT_TYPE}"}
- Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"${AUTHORIZATION_HEADER}":"${AUTHORIZATION_TOKEN}"}
- ${body}= Get File jsons/grantRequest.json
- ${json_body}= evaluate json.loads('''${body}''') json
- Set To Dictionary ${json_body} vnfInstanceId=${vnfInstanceId} vnfLcmOpOccId=${vnfLcmOpOccId} operation=${operation}
- ${body}= evaluate json.dumps(${json_body}) json
- Post ${apiRoot}/${apiName}/${apiMajorVersion}/grants ${body}
- Integer response status 201
- Log Status code validated
- ${headers}= Output response headers
- Should Contain ${headers} Location
- ${contentType}= Output response headers Content-Type
- Should Contain ${contentType} ${CONTENT_TYPE}
- ${result}= Output response body
- Validate Json grant.schema.json ${result}
- Log Validation OK
-
-Create a new Grant - Asynchronous mode
- [Arguments] ${vnfInstanceId} ${vnfLcmOpOccId} ${operation}
- Log Request a new Grant for a VNF LCM operation by POST to ${apiRoot}/${apiName}/${apiMajorVersion}/grants
- Pass Execution If ${SYNC_MODE} == 1 The Granting process is synchronous mode. Skipping the test
- Set Headers {"Accept": "${ACCEPT}"}
- Set Headers {"Content-Type": "${CONTENT_TYPE}"}
- Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"${AUTHORIZATION_HEADER}":"${AUTHORIZATION_TOKEN}"}
- ${body}= Get File jsons/grantRequest.json
- ${json_body}= evaluate json.loads('''${body}''') json
- Set To Dictionary ${json_body} vnfInstanceId=${vnfInstanceId} vnfLcmOpOccId=${vnfLcmOpOccId} operation=${operation}
- ${body}= evaluate json.dumps(${json_body}) json
- Post ${apiRoot}/${apiName}/${apiMajorVersion}/grants ${body}
- Output response
- Integer response status 202
- Log Status code validated
- ${headers}= Output response headers
- Should Contain ${headers} Location
- ${contentType}= Output response headers Content-Type
- Should Contain ${contentType} ${CONTENT_TYPE}
- Log Validation OK
-
POST Cancel operation task
Log Cancel an ongoing VNF lifecycle operation
Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"${AUTHORIZATION_HEADER}":"${AUTHORIZATION_TOKEN}"}
@@ -745,16 +717,26 @@ DELETE Scale vnfInstance
Delete ${apiRoot}/${apiName}/${apiMajorVersion}/vnf_instances/${vnfInstanceId}/scale
${outputResponse}= Output response
Set Global Variable ${response} ${outputResponse}
-POST Scale vnfInstance to level
+POST Scale vnfInstance to level with InstantiationLevelId attribute
Log Trying to scale a vnf Instance to level
Set Headers {"Accept":"${ACCEPT}"}
Set Headers {"Content-Type": "${CONTENT_TYPE}"}
Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"${AUTHORIZATION_HEADER}":"${AUTHORIZATION_TOKEN}"}
- ${template}= Get File jsons/scaleVnfToLevelRequest.json
+ ${template}= Get File jsons/scaleVnfToLevelRequestInstantiationLevelId.json
${body}= Format String ${template} instantiationLevelId=${instantiationLevelId}
Post ${apiRoot}/${apiName}/${apiMajorVersion}/vnf_instances/${vnfInstanceId}/scale_to_level ${body}
${outputResponse}= Output response
Set Global Variable ${response} ${outputResponse}
+POST Scale vnfInstance to level with scaleInfo attribute
+ Log Trying to scale a vnf Instance to level
+ Set Headers {"Accept":"${ACCEPT}"}
+ Set Headers {"Content-Type": "${CONTENT_TYPE}"}
+ Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"${AUTHORIZATION_HEADER}":"${AUTHORIZATION_TOKEN}"}
+ ${template}= Get File jsons/scaleVnfToLevelRequestScaleInfo.json
+ ${body}= Format String ${template} aspectId=${scaleAspectId}
+ Post ${apiRoot}/${apiName}/${apiMajorVersion}/vnf_instances/${vnfInstanceId}/scale_to_level ${body}
+ ${outputResponse}= Output response
+ Set Global Variable ${response} ${outputResponse}
POST Scale vnfInstance to level with VNF NOT-INSTANTIATED
Log Trying to scale a vnf Instance to level
Set Headers {"Accept":"${ACCEPT}"}
diff --git a/SOL003/VNFLifecycleManagement-API/VnfLcmOperationOccurences.robot b/SOL003/VNFLifecycleManagement-API/VnfLcmOperationOccurences.robot
index dff44f5cb7fa37ec5d9746bd8feb6ec704351086..fbf69eecac88d1c043b6117db76c54cfd6d823f4 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] v3.6.1
+ ... Reference: Clause 5.4.12.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.12.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.12.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.12.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.12.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFLifecycleManagement-API/environment/variables.txt b/SOL003/VNFLifecycleManagement-API/environment/variables.txt
index d76575c05f471c1838499b66ae8a625e993592d9..81a2d522085a227207eade2c84e8651beb565ce9 100644
--- a/SOL003/VNFLifecycleManagement-API/environment/variables.txt
+++ b/SOL003/VNFLifecycleManagement-API/environment/variables.txt
@@ -103,6 +103,7 @@ ${stopType} FORCEFUL
${terminationType} GRACEFUL
+${HEADER_TEST_SUPPORTED} 0
${scaleInfo}
${element}
diff --git a/SOL003/VNFLifecycleManagement-API/jsons/RevertToVnfSnapshotRequest.json b/SOL003/VNFLifecycleManagement-API/jsons/RevertToVnfSnapshotRequest.json
index 014b500d325e2cd61c428f3c89ec22f488a5b2cf..55e7f94ce2ac02a80c11c65b21129aef54e54ecf 100644
--- a/SOL003/VNFLifecycleManagement-API/jsons/RevertToVnfSnapshotRequest.json
+++ b/SOL003/VNFLifecycleManagement-API/jsons/RevertToVnfSnapshotRequest.json
@@ -1,5 +1,3 @@
{{
- "vnfSnapshotInfoId": "{vnfSnapshotInfoId}",
- "vnfcInstanceId": "",
- "vnfcSnapshotInfoId": ""
+ "vnfSnapshotInfoId": "{vnfSnapshotInfoId}"
}}
\ No newline at end of file
diff --git a/SOL003/VNFLifecycleManagement-API/jsons/changeExtVnfConnectivityRequest.json b/SOL003/VNFLifecycleManagement-API/jsons/changeExtVnfConnectivityRequest.json
index b53584eeabe3531068498b5a4d9198ddbcd58f3c..aee8e90f9d6c3d498703f66275f65216af4409ff 100644
--- a/SOL003/VNFLifecycleManagement-API/jsons/changeExtVnfConnectivityRequest.json
+++ b/SOL003/VNFLifecycleManagement-API/jsons/changeExtVnfConnectivityRequest.json
@@ -1,4 +1,4 @@
-{
+{{
"extVirtualLinks": [
{
"id": "string",
@@ -62,4 +62,4 @@
}
],
"additionalParams": {}
-}
\ No newline at end of file
+}}
\ No newline at end of file
diff --git a/SOL003/VNFLifecycleManagement-API/jsons/grantRequest.json b/SOL003/VNFLifecycleManagement-API/jsons/grantRequest.json
deleted file mode 100644
index 74b326828dccd6517c183eb0e5959f38268bc241..0000000000000000000000000000000000000000
--- a/SOL003/VNFLifecycleManagement-API/jsons/grantRequest.json
+++ /dev/null
@@ -1,16 +0,0 @@
-{
- "vnfInstanceId": "myVnfInstanceId",
- "vnfLcmOpOccId": "myLcmOccId",
- "vnfdId": "myVnF",
- "flavourId": "string",
- "operation": "INSTANTIATE",
- "isAutomaticInvocation": true,
- "_links": {
- "vnfLcmOpOcc": {
- "href": "string"
- },
- "vnfInstance": {
- "href": "string"
- }
- }
-}
\ No newline at end of file
diff --git a/SOL003/VNFLifecycleManagement-API/jsons/instantiateVnfRequest.json b/SOL003/VNFLifecycleManagement-API/jsons/instantiateVnfRequest.json
index d250c895147d5a79c64e075efbdb5bc9cb952cf8..15624dcb54f8a668e627e5126efb150d5cd8c611 100644
--- a/SOL003/VNFLifecycleManagement-API/jsons/instantiateVnfRequest.json
+++ b/SOL003/VNFLifecycleManagement-API/jsons/instantiateVnfRequest.json
@@ -1,79 +1,79 @@
-{
- "flavourId": "myFlavour",
- "instantiationLevelId": "string",
- "extVirtualLinks": [
- {
- "id": "string",
- "vimConnectionId": "string",
- "resourceProviderId": "string",
- "resourceId": "string",
- "extCps": [
- {
- "cpdId": "string",
- "cpConfig": [
- {
- "cpInstanceId": "string",
- "linkPortId": "string",
- "cpProtocolData": [
- {
- "layerProtocol": "IP_OVER_ETHERNET",
- "ipOverEthernet": {
- "macAddress": "string",
- "ipAddresses": [
- {
- "type": "IPV4",
- "fixedAddresses": [
- "string"
- ],
- "numDynamicAddresses": 0,
- "addressRange": {
- "minAddress": "string",
- "maxAddress": "string"
- },
- "subnetId": "string"
- }
- ]
+{{
+ "flavourId": "myFlavour",
+ "instantiationLevelId": "string",
+ "extVirtualLinks": [
+ {
+ "id": "string",
+ "vimConnectionId": "string",
+ "resourceProviderId": "string",
+ "resourceId": "string",
+ "extCps": [
+ {
+ "cpdId": "string",
+ "cpConfig": [
+ {
+ "cpInstanceId": "string",
+ "linkPortId": "string",
+ "cpProtocolData": [
+ {
+ "layerProtocol": "IP_OVER_ETHERNET",
+ "ipOverEthernet": {
+ "macAddress": "string",
+ "ipAddresses": [
+ {
+ "type": "IPV4",
+ "fixedAddresses": [
+ "string"
+ ],
+ "numDynamicAddresses": 0,
+ "addressRange": {
+ "minAddress": "string",
+ "maxAddress": "string"
+ },
+ "subnetId": "string"
+ }
+ ]
+ }
}
- }
- ]
+ ]
+ }
+ ]
+ }
+ ],
+ "extLinkPorts": [
+ {
+ "id": "string",
+ "resourceHandle": {
+ "vimConnectionId": "string",
+ "resourceProviderId": "string",
+ "resourceId": "string",
+ "vimLevelResourceType": "string"
}
- ]
- }
- ],
- "extLinkPorts": [
- {
- "id": "string",
- "resourceHandle": {
- "vimConnectionId": "string",
- "resourceProviderId": "string",
- "resourceId": "string",
- "vimLevelResourceType": "string"
}
- }
- ]
- }
- ],
- "extManagedVirtualLinks": [
- {
- "id": "string",
- "virtualLinkDescId": "string",
- "vimConnectionId": "string",
- "resourceProviderId": "string",
- "resourceId": "string"
- }
- ],
- "vimConnectionInfo": [
- {
- "id": "string",
- "vimId": "string",
- "vimType": "string",
- "interfaceInfo": {},
- "accessInfo": {},
- "extra": {}
- }
- ],
- "localizationLanguage": "English",
- "extensions": {},
- "additionalParams": {},
- "vnfConfigurableProperties": {}
-}
\ No newline at end of file
+ ]
+ }
+ ],
+ "extManagedVirtualLinks": [
+ {
+ "id": "string",
+ "virtualLinkDescId": "string",
+ "vimConnectionId": "string",
+ "resourceProviderId": "string",
+ "resourceId": "string"
+ }
+ ],
+ "vimConnectionInfo": [
+ {
+ "id": "string",
+ "vimId": "string",
+ "vimType": "string",
+ "interfaceInfo": {},
+ "accessInfo": {},
+ "extra": {}
+ }
+ ],
+ "localizationLanguage": "English",
+ "extensions": {},
+ "additionalParams": {},
+ "vnfConfigurableProperties": {}
+ }}
\ No newline at end of file
diff --git a/SOL003/VNFLifecycleManagement-API/jsons/instantiateVnfRequestInstantiationLevelId.json b/SOL003/VNFLifecycleManagement-API/jsons/instantiateVnfRequestInstantiationLevelId.json
new file mode 100644
index 0000000000000000000000000000000000000000..b988eee4dd579c26adad86cf723f69066c85b26d
--- /dev/null
+++ b/SOL003/VNFLifecycleManagement-API/jsons/instantiateVnfRequestInstantiationLevelId.json
@@ -0,0 +1,79 @@
+{{
+ "flavourId": "myFlavour",
+ "instantiationLevelId": "{instantiationLevelId}",
+ "extVirtualLinks": [
+ {
+ "id": "string",
+ "vimConnectionId": "string",
+ "resourceProviderId": "string",
+ "resourceId": "string",
+ "extCps": [
+ {
+ "cpdId": "string",
+ "cpConfig": [
+ {
+ "cpInstanceId": "string",
+ "linkPortId": "string",
+ "cpProtocolData": [
+ {
+ "layerProtocol": "IP_OVER_ETHERNET",
+ "ipOverEthernet": {
+ "macAddress": "string",
+ "ipAddresses": [
+ {
+ "type": "IPV4",
+ "fixedAddresses": [
+ "string"
+ ],
+ "numDynamicAddresses": 0,
+ "addressRange": {
+ "minAddress": "string",
+ "maxAddress": "string"
+ },
+ "subnetId": "string"
+ }
+ ]
+ }
+ }
+ ]
+ }
+ ]
+ }
+ ],
+ "extLinkPorts": [
+ {
+ "id": "string",
+ "resourceHandle": {
+ "vimConnectionId": "string",
+ "resourceProviderId": "string",
+ "resourceId": "string",
+ "vimLevelResourceType": "string"
+ }
+ }
+ ]
+ }
+ ],
+ "extManagedVirtualLinks": [
+ {
+ "id": "string",
+ "virtualLinkDescId": "string",
+ "vimConnectionId": "string",
+ "resourceProviderId": "string",
+ "resourceId": "string"
+ }
+ ],
+ "vimConnectionInfo": [
+ {
+ "id": "string",
+ "vimId": "string",
+ "vimType": "string",
+ "interfaceInfo": {},
+ "accessInfo": {},
+ "extra": {}
+ }
+ ],
+ "localizationLanguage": "English",
+ "extensions": {},
+ "additionalParams": {},
+ "vnfConfigurableProperties": {}
+}}
\ No newline at end of file
diff --git a/SOL003/VNFLifecycleManagement-API/jsons/instantiateVnfRequestTargetScaleLevelInfo.json b/SOL003/VNFLifecycleManagement-API/jsons/instantiateVnfRequestTargetScaleLevelInfo.json
new file mode 100644
index 0000000000000000000000000000000000000000..e72a745dcfd034bc619b138883591fd81235cb20
--- /dev/null
+++ b/SOL003/VNFLifecycleManagement-API/jsons/instantiateVnfRequestTargetScaleLevelInfo.json
@@ -0,0 +1,85 @@
+{{
+ "flavourId": "myFlavour",
+ "targetScaleLevelInfo": [
+ {
+ "aspectId": "{aspectId}",
+ "vnfdId": "string",
+ "scaleToLevel": "1"
+ }
+ ],
+ "extVirtualLinks": [
+ {
+ "id": "string",
+ "vimConnectionId": "string",
+ "resourceProviderId": "string",
+ "resourceId": "string",
+ "extCps": [
+ {
+ "cpdId": "string",
+ "cpConfig": [
+ {
+ "cpInstanceId": "string",
+ "linkPortId": "string",
+ "cpProtocolData": [
+ {
+ "layerProtocol": "IP_OVER_ETHERNET",
+ "ipOverEthernet": {
+ "macAddress": "string",
+ "ipAddresses": [
+ {
+ "type": "IPV4",
+ "fixedAddresses": [
+ "string"
+ ],
+ "numDynamicAddresses": 0,
+ "addressRange": {
+ "minAddress": "string",
+ "maxAddress": "string"
+ },
+ "subnetId": "string"
+ }
+ ]
+ }
+ }
+ ]
+ }
+ ]
+ }
+ ],
+ "extLinkPorts": [
+ {
+ "id": "string",
+ "resourceHandle": {
+ "vimConnectionId": "string",
+ "resourceProviderId": "string",
+ "resourceId": "string",
+ "vimLevelResourceType": "string"
+ }
+ }
+ ]
+ }
+ ],
+ "extManagedVirtualLinks": [
+ {
+ "id": "string",
+ "virtualLinkDescId": "string",
+ "vimConnectionId": "string",
+ "resourceProviderId": "string",
+ "resourceId": "string"
+ }
+ ],
+ "vimConnectionInfo": [
+ {
+ "id": "string",
+ "vimId": "string",
+ "vimType": "string",
+ "interfaceInfo": {},
+ "accessInfo": {},
+ "extra": {}
+ }
+ ],
+ "localizationLanguage": "English",
+ "extensions": {},
+ "additionalParams": {},
+ "vnfConfigurableProperties": {}
+ }}
\ No newline at end of file
diff --git a/SOL003/VNFLifecycleManagement-API/jsons/scaleVnfToLevelRequest.json b/SOL003/VNFLifecycleManagement-API/jsons/scaleVnfToLevelRequestInstantiationLevelId.json
similarity index 100%
rename from SOL003/VNFLifecycleManagement-API/jsons/scaleVnfToLevelRequest.json
rename to SOL003/VNFLifecycleManagement-API/jsons/scaleVnfToLevelRequestInstantiationLevelId.json
diff --git a/SOL003/VNFLifecycleManagement-API/jsons/scaleVnfToLevelRequestScaleInfo.json b/SOL003/VNFLifecycleManagement-API/jsons/scaleVnfToLevelRequestScaleInfo.json
new file mode 100644
index 0000000000000000000000000000000000000000..11c31f508a924f98736ef68d74078d1ccf734913
--- /dev/null
+++ b/SOL003/VNFLifecycleManagement-API/jsons/scaleVnfToLevelRequestScaleInfo.json
@@ -0,0 +1,9 @@
+{{
+ "scaleInfo":[
+ {
+ "aspectId": "{aspectId}",
+ "vnfdId": "string",
+ "scaleToLevel": "1"
+ }
+ ]
+}}
\ No newline at end of file
diff --git a/SOL003/VNFLifecycleManagement-API/schemas/LccnSubscription.schema.json b/SOL003/VNFLifecycleManagement-API/schemas/LccnSubscription.schema.json
index c86be18a0cd5dfb678cbf90df540243272f97782..59cf21d9a680ef3768c37240f9a3c8139b1237df 100644
--- a/SOL003/VNFLifecycleManagement-API/schemas/LccnSubscription.schema.json
+++ b/SOL003/VNFLifecycleManagement-API/schemas/LccnSubscription.schema.json
@@ -1,219 +1,196 @@
{
- "description": "This type represents a subscription related to notifications about VNF lifecycle changes.\n",
- "type": "object",
- "required": [
- "id",
- "callbackUri",
- "verbosity",
- "_links"
- ],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "filter": {
- "description": "This type represents a subscription filter related to notifications about VNF lifecycle changes. At a particular nesting level in the filter structure, the following applies: All attributes shall match in order for the filter to match (logical \"and\" between different filter attributes). If an attribute is an array, the attribute shall match if at least one of the values in the array matches (logical \"or\" between the values of one filter attribute).\n",
- "type": "object",
- "properties": {
- "vnfInstanceSubscriptionFilter": {
- "description": "This type represents subscription filter criteria to match VNF instances.\n",
- "type": "object",
- "anyOf": [{
- "oneOf": [{
- "required": [
- "vnfdId"
- ]
- },
- {
- "required": [
- "vnfProductsFromProviders"
- ]
- }
- ]
- },
- {
- "oneOf": [{
- "required": [
- "vnfInstanceIds"
- ]
- },
- {
- "required": [
- "vnfInstanceNames"
- ]
- }
- ]
- }
- ],
- "properties": {
- "vnfdIds": {
- "description": "If present, match VNF instances that were created based on a VNFD identified by one of the vnfdId values listed in this attribute. The attributes \"vnfdIds\" and \"vnfProductsFromProviders\" are alternatives to reference to VNF instances that are based on certain VNFDs in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n",
- "type": "array",
- "items": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- }
- },
- "vnfProductsFromProviders": {
- "description": "If present, match VNF instances that belong to VNF products from certain providers. The attributes \"vnfdIds\" and \"vnfProductsFromProviders\" are alternatives to reference to VNF instances that are based on certain VNFDs in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": [
- "vnfProvider"
- ],
- "properties": {
- "vnfProvider": {
- "description": "Name of the VNF provider to match.\n",
- "type": "string"
- },
- "vnfProducts": {
- "description": "If present, match VNF instances that belong to VNF products with certain product names, from one particular provider.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": [
- "vnfProductName"
- ],
- "properties": {
- "vnfProductName": {
- "description": "Name of the VNF product to match.\n",
- "type": "string"
- },
- "versions": {
- "description": "If present, match VNF instances that belong to VNF products with certain versions and a certain product name, from one particular provider.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": [
- "vnfSoftwareVersion"
- ],
- "properties": {
- "vnfSoftwareVersion": {
- "description": "A version.\n",
- "type": "string"
- },
- "vnfdVersions": {
- "description": "If present, match VNF instances that belong to VNF products with certain VNFD versions, a certain software version and a certain product name, from one particular provider.\n",
- "type": "array",
- "items": {
- "description": "A version.\n",
- "type": "string"
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- },
- "vnfInstanceIds": {
- "description": "If present, match VNF instances with an instance identifier listed in this attribute. The attributes \"vnfInstanceIds\" and \"vnfInstanceNames\" are alternatives to reference to particular VNF Instances in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n",
- "type": "array",
- "items": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- }
- },
- "vnfInstanceNames": {
- "description": "If present, match VNF instances with a VNF Instance Name listed in this attribute. The attributes \"vnfInstanceIds\" and \"vnfInstanceNames\" are alternatives to reference to particular VNF Instances in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n",
- "type": "array",
- "items": {
- "type": "string"
- }
- }
- }
- },
- "notificationTypes": {
- "description": "Match particular notification types. Permitted values: * VnfLcmOperationOccurrenceNotification * VnfIdentifierCreationNotification * VnfIdentifierDeletionNotification The permitted values of the \"notificationTypes\" attribute are spelled exactly as the names of the notification types to facilitate automated code generation systems.\n",
- "type": "array",
- "items": {
- "type": "string",
- "enum": [
- "VnfLcmOperationOccurrenceNotification",
- "VnfIdentifierCreationNotification",
- "VnfIdentifierDeletionNotification"
- ]
- }
- },
- "operationTypes": {
- "description": "Match particular VNF lifecycle operation types for the notification of type VnfLcmOperationOccurrenceNotification. May be present if the \"notificationTypes\" attribute contains the value \"VnfLcmOperationOccurrenceNotification\", and shall be absent otherwise.\n",
- "type": "array",
- "items": {
- "description": "Value | Description ------|------------ INSTANTIATE | Represents the \"Instantiate VNF\" LCM operation. SCALE | Represents the \"Scale VNF\" LCM operation. SCALE_TO_LEVEL | Represents the \"Scale VNF to Level\" LCM operation. CHANGE_FLAVOUR | Represents the \"Change VNF Flavour\" LCM operation. TERMINATE | Represents the \"Terminate VNF\" LCM operation. HEAL | Represents the \"Heal VNF\" LCM operation. OPERATE | Represents the \"Operate VNF\" LCM operation. CHANGE_EXT_CONN | Represents the \"Change external VNF connectivity\" LCM operation. MODIFY_INFO | Represents the \"Modify VNF Information\" LCM operation. CREATE_SNAPSHOT | Represents the \"Create VNF Snapshot\" LCM operation. REVERT_TO_SNAPSHOT | Represents the “Revert-To VNF Snapshot\" LCM operation. CHANGE_VNFPKG | Represents the \"Change current VNF package\" LCM operation.\n",
- "type": "string",
- "enum": [
- "INSTANTIATE",
- "SCALE",
- "SCALE_TO_LEVEL",
- "CHANGE_FLAVOUR",
- "TERMINATE",
- "HEAL",
- "OPERATE",
- "CHANGE_EXT_CONN",
- "MODIFY_INFO",
- "CREATE_SNAPSHOT",
- "REVERT_TO_SNAPSHOT",
- "CHANGE_VNFPKG"
- ]
- }
- },
- "operationStates": {
- "description": "Match particular LCM operation state values as reported in notifications of type VnfLcmOperationOccurrenceNotification. May be present if the \"notificationTypes\" attribute contains the value \"VnfLcmOperationOccurrenceNotification\", and shall be absent otherwise.\n",
- "type": "array",
- "items": {
- "description": "STARTING: The LCM operation is starting. PROCESSING: The LCM operation is currently in execution. COMPLETED: The LCM operation has been completed successfully. FAILED_TEMP: The LCM operation has failed and execution has stopped, but the execution of the operation is not considered to be closed. FAILED: The LCM operation has failed and it cannot be retried or rolled back, as it is determined that such action won't succeed. ROLLING_BACK: The LCM operation is currently being rolled back. ROLLED_BACK: The LCM operation has been successfully rolled back, i.e. The state of the VNF prior to the original operation invocation has been restored as closely as possible.\n",
- "type": "string",
- "enum": [
- "STARTING",
- "PROCESSING",
- "COMPLETED",
- "FAILED_TEMP",
- "FAILED",
- "ROLLING_BACK",
- "ROLLED_BACK"
- ]
- }
- }
- }
- },
- "callbackUri": {
- "description": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- },
- "verbosity": {
- "description": "The enumeration LcmOpOccNotificationVerbosityType provides values to control the verbosity of LCM operation occurrence notifications. * 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"
- ]
- },
- "_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 using an absolute URI.\n",
- "type": "object",
- "required": [
- "href"
- ],
- "properties": {
- "href": {
- "description": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- }
- }
- }
- }
- }
- }
+ "description": "This type represents a subscription related to notifications about VNF lifecycle changes.\n",
+ "type": "object",
+ "required": ["id", "callbackUri", "verbosity", "_links"],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "filter": {
+ "description": "This type represents a subscription filter related to notifications about VNF lifecycle changes.\nAt a particular nesting level in the filter structure, the following applies: All attributes shall match in order for the filter to match (logical \"and\" between different filter attributes). If an attribute is an array, the attribute shall match if at least one of the values in the array matches (logical \"or\" between the values of one filter attribute).\nNOTE:\tThe permitted values of the \"notificationTypes\" attribute are spelled exactly as the names of \n the notification types to facilitate automated code generation systems.\n",
+ "type": "object",
+ "properties": {
+ "vnfInstanceSubscriptionFilter": {
+ "description": "This type represents subscription filter criteria to match VNF instances. * NOTE 1:\tThe attributes \"vnfdIds\" and \"vnfProductsFromProviders\" are alternatives to reference to VNF instances\n that are based on certain VNFDs in a filter. They should not be used both in the same filter instance,\n but one alternative should be chosen.\n NOTE 2:\tThe attributes \"vnfInstanceIds\" and \"vnfInstanceNames\" are alternatives to reference to particular VNF\n instances in a filter. They should not be used both in the same filter instance, but one alternative\n should be chosen.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "oneOf": [
+ {
+ "required": ["vnfdId"]
+ },
+ {
+ "required": ["vnfProductsFromProviders"]
+ }
+ ]
+ },
+ {
+ "oneOf": [
+ {
+ "required": ["vnfInstanceIds"]
+ },
+ {
+ "required": ["vnfInstanceNames"]
+ }
+ ]
+ }
+ ],
+ "properties": {
+ "vnfdIds": {
+ "description": "If present, match VNF instances that were created based on a VNFD identified by one of the vnfdId values listed in this attribute. See note 1.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ },
+ "vnfProductsFromProviders": {
+ "description": "If present, match VNF instances that belong to VNF products from certain providers. See note 1.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": ["vnfProvider"],
+ "properties": {
+ "vnfProvider": {
+ "description": "Name of the VNF provider to match.\n",
+ "type": "string"
+ },
+ "vnfProducts": {
+ "description": "If present, match VNF instances that belong to VNF products with certain product names, from one particular provider.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": ["vnfProductName"],
+ "properties": {
+ "vnfProductName": {
+ "description": "Name of the VNF product to match.\n",
+ "type": "string"
+ },
+ "versions": {
+ "description": "If present, match VNF instances that belong to VNF products with certain versions and a certain product name, from one particular provider.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": ["vnfSoftwareVersion"],
+ "properties": {
+ "vnfSoftwareVersion": {
+ "description": "A version.\n",
+ "type": "string"
+ },
+ "vnfdVersions": {
+ "description": "If present, match VNF instances that belong to VNF products with certain VNFD versions, a certain software version and a certain product name, from one particular provider.\n",
+ "type": "array",
+ "items": {
+ "description": "A version.\n",
+ "type": "string"
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ },
+ "vnfInstanceIds": {
+ "description": "If present, match VNF instances with an instance identifier listed in this attribute. See note 2.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ },
+ "vnfInstanceNames": {
+ "description": "If present, match VNF instances with a VNF Instance Name listed in this attribute. See note 2.\n",
+ "type": "array",
+ "items": {
+ "type": "string"
+ }
+ }
+ }
+ },
+ "notificationTypes": {
+ "description": "Match particular notification types. \nPermitted values: -\tVnfLcmOperationOccurrenceNotification -\tVnfIdentifierCreationNotification -\tVnfIdentifierDeletionNotification See note.\n",
+ "type": "array",
+ "items": {
+ "type": "string",
+ "enum": [
+ "VnfLcmOperationOccurrenceNotification",
+ "VnfIdentifierCreationNotification",
+ "VnfIdentifierDeletionNotification"
+ ]
+ }
+ },
+ "operationTypes": {
+ "description": "Match particular VNF lifecycle operation types for the notification of type VnfLcmOperationOccurrenceNotification. May be present if the \"notificationTypes\" attribute contains the value \"VnfLcmOperationOccurrenceNotification\", and shall be absent otherwise.\n",
+ "type": "array",
+ "items": {
+ "description": "The enumeration LcmOpType defines the permitted values to represent VNF lifecycle operation types in VNF lifecycle management operation occurrence resources and VNF lifecycle management operation occurrence notifications.\nValue | Description ------|------------ INSTANTIATE | Represents the \"Instantiate VNF\" LCM operation. SCALE | Represents the \"Scale VNF\" LCM operation. SCALE_TO_LEVEL | Represents the \"Scale VNF to Level\" LCM operation. CHANGE_FLAVOUR | Represents the \"Change VNF Flavour\" LCM operation. TERMINATE | Represents the \"Terminate VNF\" LCM operation. HEAL | Represents the \"Heal VNF\" LCM operation. OPERATE | Represents the \"Operate VNF\" LCM operation. CHANGE_EXT_CONN | Represents the \"Change external VNF connectivity\" LCM operation. MODIFY_INFO | Represents the \"Modify VNF Information\" LCM operation. CREATE_SNAPSHOT | Represents the \"Create VNF Snapshot\" LCM operation. REVERT_TO_SNAPSHOT | Represents the “Revert-To VNF Snapshot\" LCM operation. CHANGE_VNFPKG | Represents the \"Change current VNF package\" LCM operation.\n",
+ "type": "string",
+ "enum": [
+ "INSTANTIATE",
+ "SCALE",
+ "SCALE_TO_LEVEL",
+ "CHANGE_FLAVOUR",
+ "TERMINATE",
+ "HEAL",
+ "OPERATE",
+ "CHANGE_EXT_CONN",
+ "MODIFY_INFO",
+ "CREATE_SNAPSHOT",
+ "REVERT_TO_SNAPSHOT",
+ "CHANGE_VNFPKG"
+ ]
+ }
+ },
+ "operationStates": {
+ "description": "Match particular LCM operation state values as reported in notifications of type VnfLcmOperationOccurrenceNotification. May be present if the \"notificationTypes\" attribute contains the value \"VnfLcmOperationOccurrenceNotification\", and shall be absent otherwise.\n",
+ "type": "array",
+ "items": {
+ "description": "STARTING: The LCM operation is starting. PROCESSING: The LCM operation is currently in execution. COMPLETED: The LCM operation has been completed successfully. FAILED_TEMP: The LCM operation has failed and execution has stopped, but the execution of the operation is not considered to be closed. FAILED: The LCM operation has failed and it cannot be retried or rolled back, as it is determined that such action won't succeed. ROLLING_BACK: The LCM operation is currently being rolled back. ROLLED_BACK: The LCM operation has been successfully rolled back, i.e. The state of the VNF prior to the original operation invocation has been restored as closely as possible.\n",
+ "type": "string",
+ "enum": [
+ "STARTING",
+ "PROCESSING",
+ "COMPLETED",
+ "FAILED_TEMP",
+ "FAILED",
+ "ROLLING_BACK",
+ "ROLLED_BACK"
+ ]
+ }
+ }
+ }
+ },
+ "callbackUri": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ },
+ "verbosity": {
+ "description": "The enumeration LcmOpOccNotificationVerbosityType provides values to control the verbosity of LCM operation occurrence notifications. * 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"]
+ },
+ "_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 using an absolute URI.\n",
+ "type": "object",
+ "required": ["href"],
+ "properties": {
+ "href": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ }
+ }
+ }
+ }
+ }
+ }
}
\ No newline at end of file
diff --git a/SOL003/VNFLifecycleManagement-API/schemas/LccnSubscriptions.schema.json b/SOL003/VNFLifecycleManagement-API/schemas/LccnSubscriptions.schema.json
index 03137a04d696e209b8a4e8701ef8295c4c16de95..fc01964d8dd0c79e47705c2ac5754322f149d0d2 100644
--- a/SOL003/VNFLifecycleManagement-API/schemas/LccnSubscriptions.schema.json
+++ b/SOL003/VNFLifecycleManagement-API/schemas/LccnSubscriptions.schema.json
@@ -1,223 +1,199 @@
{
"type": "array",
- "items":
- {
- "description": "This type represents a subscription related to notifications about VNF lifecycle changes.\n",
- "type": "object",
- "required": [
- "id",
- "callbackUri",
- "verbosity",
- "_links"
- ],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "filter": {
- "description": "This type represents a subscription filter related to notifications about VNF lifecycle changes. At a particular nesting level in the filter structure, the following applies: All attributes shall match in order for the filter to match (logical \"and\" between different filter attributes). If an attribute is an array, the attribute shall match if at least one of the values in the array matches (logical \"or\" between the values of one filter attribute).\n",
- "type": "object",
- "properties": {
- "vnfInstanceSubscriptionFilter": {
- "description": "This type represents subscription filter criteria to match VNF instances.\n",
- "type": "object",
- "anyOf": [{
- "oneOf": [{
- "required": [
- "vnfdId"
- ]
- },
- {
- "required": [
- "vnfProductsFromProviders"
- ]
- }
- ]
- },
- {
- "oneOf": [{
- "required": [
- "vnfInstanceIds"
- ]
- },
- {
- "required": [
- "vnfInstanceNames"
- ]
- }
- ]
- }
- ],
- "properties": {
- "vnfdIds": {
- "description": "If present, match VNF instances that were created based on a VNFD identified by one of the vnfdId values listed in this attribute. The attributes \"vnfdIds\" and \"vnfProductsFromProviders\" are alternatives to reference to VNF instances that are based on certain VNFDs in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n",
- "type": "array",
- "items": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- }
- },
- "vnfProductsFromProviders": {
- "description": "If present, match VNF instances that belong to VNF products from certain providers. The attributes \"vnfdIds\" and \"vnfProductsFromProviders\" are alternatives to reference to VNF instances that are based on certain VNFDs in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": [
- "vnfProvider"
- ],
- "properties": {
- "vnfProvider": {
- "description": "Name of the VNF provider to match.\n",
- "type": "string"
- },
- "vnfProducts": {
- "description": "If present, match VNF instances that belong to VNF products with certain product names, from one particular provider.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": [
- "vnfProductName"
- ],
- "properties": {
- "vnfProductName": {
- "description": "Name of the VNF product to match.\n",
- "type": "string"
- },
- "versions": {
- "description": "If present, match VNF instances that belong to VNF products with certain versions and a certain product name, from one particular provider.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": [
- "vnfSoftwareVersion"
- ],
- "properties": {
- "vnfSoftwareVersion": {
- "description": "A version.\n",
- "type": "string"
- },
- "vnfdVersions": {
- "description": "If present, match VNF instances that belong to VNF products with certain VNFD versions, a certain software version and a certain product name, from one particular provider.\n",
- "type": "array",
- "items": {
- "description": "A version.\n",
- "type": "string"
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- },
- "vnfInstanceIds": {
- "description": "If present, match VNF instances with an instance identifier listed in this attribute. The attributes \"vnfInstanceIds\" and \"vnfInstanceNames\" are alternatives to reference to particular VNF Instances in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n",
- "type": "array",
- "items": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- }
- },
- "vnfInstanceNames": {
- "description": "If present, match VNF instances with a VNF Instance Name listed in this attribute. The attributes \"vnfInstanceIds\" and \"vnfInstanceNames\" are alternatives to reference to particular VNF Instances in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n",
- "type": "array",
- "items": {
- "type": "string"
- }
- }
- }
- },
- "notificationTypes": {
- "description": "Match particular notification types. Permitted values: * VnfLcmOperationOccurrenceNotification * VnfIdentifierCreationNotification * VnfIdentifierDeletionNotification The permitted values of the \"notificationTypes\" attribute are spelled exactly as the names of the notification types to facilitate automated code generation systems.\n",
- "type": "array",
- "items": {
- "type": "string",
- "enum": [
- "VnfLcmOperationOccurrenceNotification",
- "VnfIdentifierCreationNotification",
- "VnfIdentifierDeletionNotification"
- ]
- }
- },
- "operationTypes": {
- "description": "Match particular VNF lifecycle operation types for the notification of type VnfLcmOperationOccurrenceNotification. May be present if the \"notificationTypes\" attribute contains the value \"VnfLcmOperationOccurrenceNotification\", and shall be absent otherwise.\n",
- "type": "array",
- "items": {
- "description": "Value | Description ------|------------ INSTANTIATE | Represents the \"Instantiate VNF\" LCM operation. SCALE | Represents the \"Scale VNF\" LCM operation. SCALE_TO_LEVEL | Represents the \"Scale VNF to Level\" LCM operation. CHANGE_FLAVOUR | Represents the \"Change VNF Flavour\" LCM operation. TERMINATE | Represents the \"Terminate VNF\" LCM operation. HEAL | Represents the \"Heal VNF\" LCM operation. OPERATE | Represents the \"Operate VNF\" LCM operation. CHANGE_EXT_CONN | Represents the \"Change external VNF connectivity\" LCM operation. MODIFY_INFO | Represents the \"Modify VNF Information\" LCM operation. CREATE_SNAPSHOT | Represents the \"Create VNF Snapshot\" LCM operation. REVERT_TO_SNAPSHOT | Represents the “Revert-To VNF Snapshot\" LCM operation. CHANGE_VNFPKG | Represents the \"Change current VNF package\" LCM operation.\n",
- "type": "string",
- "enum": [
- "INSTANTIATE",
- "SCALE",
- "SCALE_TO_LEVEL",
- "CHANGE_FLAVOUR",
- "TERMINATE",
- "HEAL",
- "OPERATE",
- "CHANGE_EXT_CONN",
- "MODIFY_INFO",
- "CREATE_SNAPSHOT",
- "REVERT_TO_SNAPSHOT",
- "CHANGE_VNFPKG"
- ]
- }
- },
- "operationStates": {
- "description": "Match particular LCM operation state values as reported in notifications of type VnfLcmOperationOccurrenceNotification. May be present if the \"notificationTypes\" attribute contains the value \"VnfLcmOperationOccurrenceNotification\", and shall be absent otherwise.\n",
- "type": "array",
- "items": {
- "description": "STARTING: The LCM operation is starting. PROCESSING: The LCM operation is currently in execution. COMPLETED: The LCM operation has been completed successfully. FAILED_TEMP: The LCM operation has failed and execution has stopped, but the execution of the operation is not considered to be closed. FAILED: The LCM operation has failed and it cannot be retried or rolled back, as it is determined that such action won't succeed. ROLLING_BACK: The LCM operation is currently being rolled back. ROLLED_BACK: The LCM operation has been successfully rolled back, i.e. The state of the VNF prior to the original operation invocation has been restored as closely as possible.\n",
- "type": "string",
- "enum": [
- "STARTING",
- "PROCESSING",
- "COMPLETED",
- "FAILED_TEMP",
- "FAILED",
- "ROLLING_BACK",
- "ROLLED_BACK"
- ]
- }
- }
- }
- },
- "callbackUri": {
- "description": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- },
- "verbosity": {
- "description": "The enumeration LcmOpOccNotificationVerbosityType provides values to control the verbosity of LCM operation occurrence notifications. * 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"
- ]
- },
- "_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 using an absolute URI.\n",
- "type": "object",
- "required": [
- "href"
- ],
- "properties": {
- "href": {
- "description": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- }
- }
- }
- }
- }
- }
+ "items": {
+ "description": "This type represents a subscription related to notifications about VNF lifecycle changes.\n",
+ "type": "object",
+ "required": ["id", "callbackUri", "verbosity", "_links"],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "filter": {
+ "description": "This type represents a subscription filter related to notifications about VNF lifecycle changes.\nAt a particular nesting level in the filter structure, the following applies: All attributes shall match in order for the filter to match (logical \"and\" between different filter attributes). If an attribute is an array, the attribute shall match if at least one of the values in the array matches (logical \"or\" between the values of one filter attribute).\nNOTE:\tThe permitted values of the \"notificationTypes\" attribute are spelled exactly as the names of \n the notification types to facilitate automated code generation systems.\n",
+ "type": "object",
+ "properties": {
+ "vnfInstanceSubscriptionFilter": {
+ "description": "This type represents subscription filter criteria to match VNF instances. * NOTE 1:\tThe attributes \"vnfdIds\" and \"vnfProductsFromProviders\" are alternatives to reference to VNF instances\n that are based on certain VNFDs in a filter. They should not be used both in the same filter instance,\n but one alternative should be chosen.\n NOTE 2:\tThe attributes \"vnfInstanceIds\" and \"vnfInstanceNames\" are alternatives to reference to particular VNF\n instances in a filter. They should not be used both in the same filter instance, but one alternative\n should be chosen.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "oneOf": [
+ {
+ "required": ["vnfdId"]
+ },
+ {
+ "required": ["vnfProductsFromProviders"]
+ }
+ ]
+ },
+ {
+ "oneOf": [
+ {
+ "required": ["vnfInstanceIds"]
+ },
+ {
+ "required": ["vnfInstanceNames"]
+ }
+ ]
+ }
+ ],
+ "properties": {
+ "vnfdIds": {
+ "description": "If present, match VNF instances that were created based on a VNFD identified by one of the vnfdId values listed in this attribute. See note 1.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ },
+ "vnfProductsFromProviders": {
+ "description": "If present, match VNF instances that belong to VNF products from certain providers. See note 1.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": ["vnfProvider"],
+ "properties": {
+ "vnfProvider": {
+ "description": "Name of the VNF provider to match.\n",
+ "type": "string"
+ },
+ "vnfProducts": {
+ "description": "If present, match VNF instances that belong to VNF products with certain product names, from one particular provider.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": ["vnfProductName"],
+ "properties": {
+ "vnfProductName": {
+ "description": "Name of the VNF product to match.\n",
+ "type": "string"
+ },
+ "versions": {
+ "description": "If present, match VNF instances that belong to VNF products with certain versions and a certain product name, from one particular provider.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": ["vnfSoftwareVersion"],
+ "properties": {
+ "vnfSoftwareVersion": {
+ "description": "A version.\n",
+ "type": "string"
+ },
+ "vnfdVersions": {
+ "description": "If present, match VNF instances that belong to VNF products with certain VNFD versions, a certain software version and a certain product name, from one particular provider.\n",
+ "type": "array",
+ "items": {
+ "description": "A version.\n",
+ "type": "string"
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ },
+ "vnfInstanceIds": {
+ "description": "If present, match VNF instances with an instance identifier listed in this attribute. See note 2.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ },
+ "vnfInstanceNames": {
+ "description": "If present, match VNF instances with a VNF Instance Name listed in this attribute. See note 2.\n",
+ "type": "array",
+ "items": {
+ "type": "string"
+ }
+ }
+ }
+ },
+ "notificationTypes": {
+ "description": "Match particular notification types. \nPermitted values: -\tVnfLcmOperationOccurrenceNotification -\tVnfIdentifierCreationNotification -\tVnfIdentifierDeletionNotification See note.\n",
+ "type": "array",
+ "items": {
+ "type": "string",
+ "enum": [
+ "VnfLcmOperationOccurrenceNotification",
+ "VnfIdentifierCreationNotification",
+ "VnfIdentifierDeletionNotification"
+ ]
+ }
+ },
+ "operationTypes": {
+ "description": "Match particular VNF lifecycle operation types for the notification of type VnfLcmOperationOccurrenceNotification. May be present if the \"notificationTypes\" attribute contains the value \"VnfLcmOperationOccurrenceNotification\", and shall be absent otherwise.\n",
+ "type": "array",
+ "items": {
+ "description": "The enumeration LcmOpType defines the permitted values to represent VNF lifecycle operation types in VNF lifecycle management operation occurrence resources and VNF lifecycle management operation occurrence notifications.\nValue | Description ------|------------ INSTANTIATE | Represents the \"Instantiate VNF\" LCM operation. SCALE | Represents the \"Scale VNF\" LCM operation. SCALE_TO_LEVEL | Represents the \"Scale VNF to Level\" LCM operation. CHANGE_FLAVOUR | Represents the \"Change VNF Flavour\" LCM operation. TERMINATE | Represents the \"Terminate VNF\" LCM operation. HEAL | Represents the \"Heal VNF\" LCM operation. OPERATE | Represents the \"Operate VNF\" LCM operation. CHANGE_EXT_CONN | Represents the \"Change external VNF connectivity\" LCM operation. MODIFY_INFO | Represents the \"Modify VNF Information\" LCM operation. CREATE_SNAPSHOT | Represents the \"Create VNF Snapshot\" LCM operation. REVERT_TO_SNAPSHOT | Represents the “Revert-To VNF Snapshot\" LCM operation. CHANGE_VNFPKG | Represents the \"Change current VNF package\" LCM operation.\n",
+ "type": "string",
+ "enum": [
+ "INSTANTIATE",
+ "SCALE",
+ "SCALE_TO_LEVEL",
+ "CHANGE_FLAVOUR",
+ "TERMINATE",
+ "HEAL",
+ "OPERATE",
+ "CHANGE_EXT_CONN",
+ "MODIFY_INFO",
+ "CREATE_SNAPSHOT",
+ "REVERT_TO_SNAPSHOT",
+ "CHANGE_VNFPKG"
+ ]
+ }
+ },
+ "operationStates": {
+ "description": "Match particular LCM operation state values as reported in notifications of type VnfLcmOperationOccurrenceNotification. May be present if the \"notificationTypes\" attribute contains the value \"VnfLcmOperationOccurrenceNotification\", and shall be absent otherwise.\n",
+ "type": "array",
+ "items": {
+ "description": "STARTING: The LCM operation is starting. PROCESSING: The LCM operation is currently in execution. COMPLETED: The LCM operation has been completed successfully. FAILED_TEMP: The LCM operation has failed and execution has stopped, but the execution of the operation is not considered to be closed. FAILED: The LCM operation has failed and it cannot be retried or rolled back, as it is determined that such action won't succeed. ROLLING_BACK: The LCM operation is currently being rolled back. ROLLED_BACK: The LCM operation has been successfully rolled back, i.e. The state of the VNF prior to the original operation invocation has been restored as closely as possible.\n",
+ "type": "string",
+ "enum": [
+ "STARTING",
+ "PROCESSING",
+ "COMPLETED",
+ "FAILED_TEMP",
+ "FAILED",
+ "ROLLING_BACK",
+ "ROLLED_BACK"
+ ]
+ }
+ }
+ }
+ },
+ "callbackUri": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ },
+ "verbosity": {
+ "description": "The enumeration LcmOpOccNotificationVerbosityType provides values to control the verbosity of LCM operation occurrence notifications. * 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"]
+ },
+ "_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 using an absolute URI.\n",
+ "type": "object",
+ "required": ["href"],
+ "properties": {
+ "href": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ }
+ }
+ }
+ }
+ }
+ }
}
}
\ No newline at end of file
diff --git a/SOL003/VNFLifecycleManagement-API/schemas/Subscription.schema.json b/SOL003/VNFLifecycleManagement-API/schemas/Subscription.schema.json
index 608d47f588b06c6ed4b4cc2554e8b5b7c207af87..8f2bb9906373c0e56ed08f108c79ac596e5acd1b 100644
--- a/SOL003/VNFLifecycleManagement-API/schemas/Subscription.schema.json
+++ b/SOL003/VNFLifecycleManagement-API/schemas/Subscription.schema.json
@@ -1 +1,196 @@
-{ "description": "This type represents a subscription related to notifications about VNF lifecycle changes.\n", "type": "object", "required": [ "id", "callbackUri", "_links" ], "properties": { "id": { "description": "An identifier with the intention of being globally unique.\n", "type": "string" }, "filter": { "description": "This type represents a subscription filter related to notifications about VNF lifecycle changes. At a particular nesting level in the filter structure, the following applies: All attributes shall match in order for the filter to match (logical \"and\" between different filter attributes). If an attribute is an array, the attribute shall match if at least one of the values in the array matches (logical \"or\" between the values of one filter attribute).\n", "type": "object", "properties": { "vnfInstanceSubscriptionFilter": { "description": "This type represents subscription filter criteria to match VNF instances.\n", "type": "object", "properties": { "vnfdIds": { "description": "If present, match VNF instances that were created based on a VNFD identified by one of the vnfdId values listed in this attribute. The attributes \"vnfdIds\" and \"vnfProductsFromProviders\" are alternatives to reference to VNF instances that are based on certain VNFDs in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n", "type": "array", "items": { "description": "An identifier with the intention of being globally unique.\n", "type": "string" } }, "vnfProductsFromProviders": { "description": "If present, match VNF instances that belong to VNF products from certain providers. The attributes \"vnfdIds\" and \"vnfProductsFromProviders\" are alternatives to reference to VNF instances that are based on certain VNFDs in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n", "type": "array", "items": { "type": "object", "required": [ "vnfProvider" ], "properties": { "vnfProvider": { "description": "Name of the VNF provider to match.\n", "type": "string" }, "vnfProducts": { "description": "If present, match VNF instances that belong to VNF products with certain product names, from one particular provider.\n", "type": "array", "items": { "type": "object", "required": [ "vnfProductName" ], "properties": { "vnfProductName": { "description": "Name of the VNF product to match.\n", "type": "string" }, "versions": { "description": "If present, match VNF instances that belong to VNF products with certain versions and a certain product name, from one particular provider.\n", "type": "array", "items": { "type": "object", "required": [ "vnfSoftwareVersion" ], "properties": { "vnfSoftwareVersion": { "description": "A version.\n", "type": "string" }, "vnfdVersions": { "description": "If present, match VNF instances that belong to VNF products with certain VNFD versions, a certain software version and a certain product name, from one particular provider.\n", "type": "array", "items": { "description": "A version.\n", "type": "string" } } } } } } } } } } }, "vnfInstanceIds": { "description": "If present, match VNF instances with an instance identifier listed in this attribute. The attributes \"vnfInstanceIds\" and \"vnfInstanceNames\" are alternatives to reference to particular VNF Instances in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n", "type": "array", "items": { "description": "An identifier with the intention of being globally unique.\n", "type": "string" } }, "vnfInstanceNames": { "description": "If present, match VNF instances with a VNF Instance Name listed in this attribute. The attributes \"vnfInstanceIds\" and \"vnfInstanceNames\" are alternatives to reference to particular VNF Instances in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n", "type": "array", "items": { "type": "string" } } } }, "notificationTypes": { "description": "Match particular notification types. Permitted values: * VnfLcmOperationOccurrenceNotification * VnfIdentifierCreationNotification * VnfIdentifierDeletionNotification The permitted values of the \"notificationTypes\" attribute are spelled exactly as the names of the notification types to facilitate automated code generation systems.\n", "type": "array", "items": { "type": "string", "enum": [ "VnfLcmOperationOccurrenceNotification", "VnfIdentifierCreationNotification", "VnfIdentifierDeletionNotification" ] } }, "operationTypes": { "description": "Match particular VNF lifecycle operation types for the notification of type VnfLcmOperationOccurrenceNotification. May be present if the \"notificationTypes\" attribute contains the value \"VnfLcmOperationOccurrenceNotification\", and shall be absent otherwise.\n", "type": "array", "items": { "description": "Value | Description ------|------------ INSTANTIATE | Represents the \"Instantiate VNF\" LCM operation. SCALE | Represents the \"Scale VNF\" LCM operation. SCALE_TO_LEVEL | Represents the \"Scale VNF to Level\" LCM operation. CHANGE_FLAVOUR | Represents the \"Change VNF Flavour\" LCM operation. TERMINATE | Represents the \"Terminate VNF\" LCM operation. HEAL | Represents the \"Heal VNF\" LCM operation. OPERATE | Represents the \"Operate VNF\" LCM operation. CHANGE_EXT_CONN | Represents the \"Change external VNF connectivity\" LCM operation. MODIFY_INFO | Represents the \"Modify VNF Information\" LCM operation. \n", "type": "string", "enum": [ "INSTANTIATE", "SCALE", "SCALE_TO_LEVEL", "CHANGE_FLAVOUR", "TERMINATE", "HEAL", "OPERATE", "CHANGE_EXT_CONN", "MODIFY_INFO" ] } }, "operationStates": { "description": "Match particular LCM operation state values as reported in notifications of type VnfLcmOperationOccurrenceNotification. May be present if the \"notificationTypes\" attribute contains the value \"VnfLcmOperationOccurrenceNotification\", and shall be absent otherwise.\n", "type": "array", "items": { "description": "Value | Description ------|------------ STARTING | The LCM operation is starting. PROCESSING | The LCM operation is currently in execution. COMPLETED | he LCM operation has been completed successfully. FAILED_TEMP | The LCM operation has failed and execution has stopped, but the execution of the operation is not considered to be closed. FAILED | The LCM operation has failed and it cannot be retried or rolled back, as it is determined that such action won't succeed. ROLLING_BACK | The LCM operation is currently being rolled back. ROLLED_BACK | The LCM operation has been successfully rolled back, i.e. The state of the VNF prior to the original operation invocation has been restored as closely as possible.\n", "type": "string", "enum": [ "STARTING", "PROCESSING", "COMPLETED", "FAILED_TEMP", "FAILED", "ROLLING_BACK", "ROLLED_BACK" ] } } } }, "callbackUri": { "description": "String formatted according to IETF RFC 3986.\n", "type": "string" }, "_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 the referenced resource.\n", "type": "string", "format": "url" } } } } } }}
\ No newline at end of file
+{
+ "description": "This type represents a subscription related to notifications about VNF lifecycle changes.\n",
+ "type": "object",
+ "required": ["id", "callbackUri", "verbosity", "_links"],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "filter": {
+ "description": "This type represents a subscription filter related to notifications about VNF lifecycle changes.\nAt a particular nesting level in the filter structure, the following applies: All attributes shall match in order for the filter to match (logical \"and\" between different filter attributes). If an attribute is an array, the attribute shall match if at least one of the values in the array matches (logical \"or\" between the values of one filter attribute).\nNOTE:\tThe permitted values of the \"notificationTypes\" attribute are spelled exactly as the names of \n the notification types to facilitate automated code generation systems.\n",
+ "type": "object",
+ "properties": {
+ "vnfInstanceSubscriptionFilter": {
+ "description": "This type represents subscription filter criteria to match VNF instances. * NOTE 1:\tThe attributes \"vnfdIds\" and \"vnfProductsFromProviders\" are alternatives to reference to VNF instances\n that are based on certain VNFDs in a filter. They should not be used both in the same filter instance,\n but one alternative should be chosen.\n NOTE 2:\tThe attributes \"vnfInstanceIds\" and \"vnfInstanceNames\" are alternatives to reference to particular VNF\n instances in a filter. They should not be used both in the same filter instance, but one alternative\n should be chosen.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "oneOf": [
+ {
+ "required": ["vnfdId"]
+ },
+ {
+ "required": ["vnfProductsFromProviders"]
+ }
+ ]
+ },
+ {
+ "oneOf": [
+ {
+ "required": ["vnfInstanceIds"]
+ },
+ {
+ "required": ["vnfInstanceNames"]
+ }
+ ]
+ }
+ ],
+ "properties": {
+ "vnfdIds": {
+ "description": "If present, match VNF instances that were created based on a VNFD identified by one of the vnfdId values listed in this attribute. See note 1.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ },
+ "vnfProductsFromProviders": {
+ "description": "If present, match VNF instances that belong to VNF products from certain providers. See note 1.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": ["vnfProvider"],
+ "properties": {
+ "vnfProvider": {
+ "description": "Name of the VNF provider to match.\n",
+ "type": "string"
+ },
+ "vnfProducts": {
+ "description": "If present, match VNF instances that belong to VNF products with certain product names, from one particular provider.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": ["vnfProductName"],
+ "properties": {
+ "vnfProductName": {
+ "description": "Name of the VNF product to match.\n",
+ "type": "string"
+ },
+ "versions": {
+ "description": "If present, match VNF instances that belong to VNF products with certain versions and a certain product name, from one particular provider.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": ["vnfSoftwareVersion"],
+ "properties": {
+ "vnfSoftwareVersion": {
+ "description": "A version.\n",
+ "type": "string"
+ },
+ "vnfdVersions": {
+ "description": "If present, match VNF instances that belong to VNF products with certain VNFD versions, a certain software version and a certain product name, from one particular provider.\n",
+ "type": "array",
+ "items": {
+ "description": "A version.\n",
+ "type": "string"
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ },
+ "vnfInstanceIds": {
+ "description": "If present, match VNF instances with an instance identifier listed in this attribute. See note 2.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ },
+ "vnfInstanceNames": {
+ "description": "If present, match VNF instances with a VNF Instance Name listed in this attribute. See note 2.\n",
+ "type": "array",
+ "items": {
+ "type": "string"
+ }
+ }
+ }
+ },
+ "notificationTypes": {
+ "description": "Match particular notification types. \nPermitted values: -\tVnfLcmOperationOccurrenceNotification -\tVnfIdentifierCreationNotification -\tVnfIdentifierDeletionNotification See note.\n",
+ "type": "array",
+ "items": {
+ "type": "string",
+ "enum": [
+ "VnfLcmOperationOccurrenceNotification",
+ "VnfIdentifierCreationNotification",
+ "VnfIdentifierDeletionNotification"
+ ]
+ }
+ },
+ "operationTypes": {
+ "description": "Match particular VNF lifecycle operation types for the notification of type VnfLcmOperationOccurrenceNotification. May be present if the \"notificationTypes\" attribute contains the value \"VnfLcmOperationOccurrenceNotification\", and shall be absent otherwise.\n",
+ "type": "array",
+ "items": {
+ "description": "The enumeration LcmOpType defines the permitted values to represent VNF lifecycle operation types in VNF lifecycle management operation occurrence resources and VNF lifecycle management operation occurrence notifications.\nValue | Description ------|------------ INSTANTIATE | Represents the \"Instantiate VNF\" LCM operation. SCALE | Represents the \"Scale VNF\" LCM operation. SCALE_TO_LEVEL | Represents the \"Scale VNF to Level\" LCM operation. CHANGE_FLAVOUR | Represents the \"Change VNF Flavour\" LCM operation. TERMINATE | Represents the \"Terminate VNF\" LCM operation. HEAL | Represents the \"Heal VNF\" LCM operation. OPERATE | Represents the \"Operate VNF\" LCM operation. CHANGE_EXT_CONN | Represents the \"Change external VNF connectivity\" LCM operation. MODIFY_INFO | Represents the \"Modify VNF Information\" LCM operation. CREATE_SNAPSHOT | Represents the \"Create VNF Snapshot\" LCM operation. REVERT_TO_SNAPSHOT | Represents the “Revert-To VNF Snapshot\" LCM operation. CHANGE_VNFPKG | Represents the \"Change current VNF package\" LCM operation.\n",
+ "type": "string",
+ "enum": [
+ "INSTANTIATE",
+ "SCALE",
+ "SCALE_TO_LEVEL",
+ "CHANGE_FLAVOUR",
+ "TERMINATE",
+ "HEAL",
+ "OPERATE",
+ "CHANGE_EXT_CONN",
+ "MODIFY_INFO",
+ "CREATE_SNAPSHOT",
+ "REVERT_TO_SNAPSHOT",
+ "CHANGE_VNFPKG"
+ ]
+ }
+ },
+ "operationStates": {
+ "description": "Match particular LCM operation state values as reported in notifications of type VnfLcmOperationOccurrenceNotification. May be present if the \"notificationTypes\" attribute contains the value \"VnfLcmOperationOccurrenceNotification\", and shall be absent otherwise.\n",
+ "type": "array",
+ "items": {
+ "description": "STARTING: The LCM operation is starting. PROCESSING: The LCM operation is currently in execution. COMPLETED: The LCM operation has been completed successfully. FAILED_TEMP: The LCM operation has failed and execution has stopped, but the execution of the operation is not considered to be closed. FAILED: The LCM operation has failed and it cannot be retried or rolled back, as it is determined that such action won't succeed. ROLLING_BACK: The LCM operation is currently being rolled back. ROLLED_BACK: The LCM operation has been successfully rolled back, i.e. The state of the VNF prior to the original operation invocation has been restored as closely as possible.\n",
+ "type": "string",
+ "enum": [
+ "STARTING",
+ "PROCESSING",
+ "COMPLETED",
+ "FAILED_TEMP",
+ "FAILED",
+ "ROLLING_BACK",
+ "ROLLED_BACK"
+ ]
+ }
+ }
+ }
+ },
+ "callbackUri": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ },
+ "verbosity": {
+ "description": "The enumeration LcmOpOccNotificationVerbosityType provides values to control the verbosity of LCM operation occurrence notifications. * 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"]
+ },
+ "_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 using an absolute URI.\n",
+ "type": "object",
+ "required": ["href"],
+ "properties": {
+ "href": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ }
+ }
+ }
+ }
+ }
+ }
+}
diff --git a/SOL003/VNFLifecycleManagement-API/schemas/VnfIdentifierCreationNotification.schema.json b/SOL003/VNFLifecycleManagement-API/schemas/VnfIdentifierCreationNotification.schema.json
index 142c16386b215ab3493f6868b74a10cf11ed694c..9f8efd572b5d4fe342d314a274f72aef01d20352 100644
--- a/SOL003/VNFLifecycleManagement-API/schemas/VnfIdentifierCreationNotification.schema.json
+++ b/SOL003/VNFLifecycleManagement-API/schemas/VnfIdentifierCreationNotification.schema.json
@@ -1,87 +1,76 @@
{
- "description": "This type represents a VNF identifier creation notification, which informs the receiver of the creation of a new \"Individual VNF instance\" resource and the associated VNF instance identifier. This notification shall be triggered by the VNFM when it has created an \"Individual VNF instance\" resource and the associated VNF instance identifier.\n",
+ "description": "This type represents a VNF identifier creation notification, which informs the receiver of the creation of a new \"Individual VNF instance\" resource and the associated VNF instance identifier. This notification shall be triggered by the VNFM when it has created an \"Individual VNF instance\" resource and the associated VNF instance identifier.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "notificationType",
+ "subscriptionId",
+ "timeStamp",
+ "vnfInstanceId",
+ "_links"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "notificationType": {
+ "description": "Discriminator for the different notification types. Shall be set to \"VnfIdentifierCreationNotification\" for this notification type.\n",
+ "type": "string",
+ "enum": ["VnfIdentifierCreationNotification"]
+ },
+ "subscriptionId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "timeStamp": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "vnfInstanceId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "_links": {
+ "description": "This type represents the links to resources that a notification can contain.\n",
"type": "object",
- "required": [
- "id",
- "notificationType",
- "subscriptionId",
- "timeStamp",
- "vnfInstanceId",
- "_links"
- ],
+ "required": ["vnfInstance", "subscription"],
"properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "notificationType": {
- "description": "Discriminator for the different notification types. Shall be set to \"VnfIdentifierCreationNotification\" for this notification type.\n",
- "type": "string",
- "enum": [
- "VnfIdentifierCreationNotification"
- ]
- },
- "subscriptionId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "timeStamp": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
+ "vnfInstance": {
+ "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": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ }
+ }
},
- "vnfInstanceId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
+ "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": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ }
+ }
},
- "_links": {
- "description": "This type represents the links to resources that a notification can contain.\n",
+ "vnfLcmOpOcc": {
+ "description": "This type represents a link to a resource in a notification, using an absolute or relative URI.\n",
"type": "object",
- "required": [
- "vnfInstance",
- "subscription"
- ],
+ "required": ["href"],
"properties": {
- "vnfInstance": {
- "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": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- }
- }
- },
- "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": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- }
- }
- },
- "vnfLcmOpOcc": {
- "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": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- }
- }
+ "href": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
}
}
}
}
- }
\ No newline at end of file
+ }
+ }
+}
\ No newline at end of file
diff --git a/SOL003/VNFLifecycleManagement-API/schemas/VnfLcmOpOcc.schema.json b/SOL003/VNFLifecycleManagement-API/schemas/VnfLcmOpOcc.schema.json
index 269c77bc9a53c2b9f2aa65729504159930001292..3a3c6a866b53c3f7239cd52d53a07aea529cddd2 100644
--- a/SOL003/VNFLifecycleManagement-API/schemas/VnfLcmOpOcc.schema.json
+++ b/SOL003/VNFLifecycleManagement-API/schemas/VnfLcmOpOcc.schema.json
@@ -1,1025 +1,1261 @@
{
- "description": "This type represents a VNF lifecycle management operation occurrence. It shall comply with the provisions defined in table 5.5.2.13-1.\nNOTE 1:\tThis allows the NFVO to obtain the information contained in the latest \n \"result\" notification if it has not received it due to an error or a \n wrongly configured subscription filter.\nNOTE 2:\tNot more than one of changedInfo and modificationsTriggeredByVnfPkgChange \n shall be present.\nNOTE 3:\tFor a particular affected VL, there shall be as many \"AffectedVirtualLink\" \n entries as needed for signalling the different types of changes, i.e. one \n per virtual link and change type. For instance, in the case of signaling \n affected VL instances involving the addition of a particular VL instance \n with links ports, one \"AffectedVirtualLink\" entry signals the addition of \n the VL by using the \"changeType\" attribute of \"AffectedVirtualLink\" structure \n equal to \"ADDED\", and another \"AffectedVirtualLink\" entry signals the addition \n of externally visible VNF link ports of the VL by using the \"changeType\" equal \n to \"LINK_PORT_ADDED\".\nNOTE 4:\tA coordination action has timed out if the VNFM has not been able to read the \n \"Individual coordination action\" resource within a timeout interval after requesting \n the coordination to be started or to be cancelled. The length of the timeout interval \n is defined by means outside the scope of the present document.\nNOTE 5: The list of rejected coordinations may be garbage collected if the LCM operation\n occurrence has reached a terminal state, i.e. one of \"COMPLETED\", \"FAILED\" and \"ROLLED_BACK\".\n",
- "type": "object",
- "oneOf": [
- {
- "required": ["changedInfo"]
- },
- {
- "required": ["modificationsTriggeredByVnfPkgChange"]
- }
- ],
- "required": [
- "id",
- "operationState",
- "stateEnteredTime",
- "startTime",
- "vnfInstanceId",
- "operation",
- "isAutomaticInvocation",
- "isCancelPending"
- ],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "operationState": {
- "description": "STARTING: The LCM operation is starting. PROCESSING: The LCM operation is currently in execution. COMPLETED: The LCM operation has been completed successfully. FAILED_TEMP: The LCM operation has failed and execution has stopped, but the execution of the operation is not considered to be closed. FAILED: The LCM operation has failed and it cannot be retried or rolled back, as it is determined that such action won't succeed. ROLLING_BACK: The LCM operation is currently being rolled back. ROLLED_BACK: The LCM operation has been successfully rolled back, i.e. The state of the VNF prior to the original operation invocation has been restored as closely as possible.\n",
- "type": "string",
- "enum": [
- "STARTING",
- "PROCESSING",
- "COMPLETED",
- "FAILED_TEMP",
- "FAILED",
- "ROLLING_BACK",
- "ROLLED_BACK"
- ]
- },
- "stateEnteredTime": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "startTime": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "vnfInstanceId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "grantId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "operation": {
- "description": "The enumeration LcmOpType defines the permitted values to represent VNF lifecycle operation types in VNF lifecycle management operation occurrence resources and VNF lifecycle management operation occurrence notifications. It shall comply with the provisions defined in table 5.5.4.5-1.\nValue | Description ------|------------ INSTANTIATE | Represents the \"Instantiate VNF\" LCM operation. SCALE | Represents the \"Scale VNF\" LCM operation. SCALE_TO_LEVEL | Represents the \"Scale VNF to Level\" LCM operation. CHANGE_FLAVOUR | Represents the \"Change VNF Flavour\" LCM operation. TERMINATE | Represents the \"Terminate VNF\" LCM operation. HEAL | Represents the \"Heal VNF\" LCM operation. OPERATE | Represents the \"Operate VNF\" LCM operation. CHANGE_EXT_CONN | Represents the \"Change external VNF connectivity\" LCM operation. MODIFY_INFO | Represents the \"Modify VNF Information\" LCM operation. CREATE_SNAPSHOT | Represents the \"Create VNF Snapshot\" LCM operation. REVERT_TO_SNAPSHOT | Represents the ΓÇ£Revert-To VNF Snapshot\" LCM operation. CHANGE_VNFPKG | Represents the \"Change current VNF package\" LCM operation.\n",
- "type": "string",
- "enum": [
- "INSTANTIATE",
- "SCALE",
- "SCALE_TO_LEVEL",
- "CHANGE_FLAVOUR",
- "TERMINATE",
- "HEAL",
- "OPERATE",
- "CHANGE_EXT_CONN",
- "MODIFY_INFO",
- "CREATE_SNAPSHOT",
- "REVERT_TO_SNAPSHOT",
- "CHANGE_VNFPKG"
- ]
- },
- "isAutomaticInvocation": {
- "description": "The Boolean is a data type having two values (true and false).\n",
- "type": "boolean"
- },
- "operationParams": {
- "description": "Input parameters of the LCM operation. This attribute shall be formatted according to the request data type of the related LCM operation. In addition, the provisions in clause 5.7 shall apply. \nThe following mapping between operationType and the data type of this attribute shall apply: * INSTANTIATE: InstantiateVnfRequest * SCALE: ScaleVnfRequest * SCALE_TO_LEVEL: ScaleVnfToLevelRequest * CHANGE_FLAVOUR: ChangeVnfFlavourRequest * OPERATE: OperateVnfRequest * HEAL: HealVnfRequest * CHANGE_EXT_CONN: ChangeExtVnfConnectivityRequest * TERMINATE: TerminateVnfRequest * MODIFY_INFO: VnfInfoModifications * CREATE_SNAPSHOT: CreateVnfSnapshotRequest * REVERT_TO_SNAPSHOT: RevertToVnfSnapshotRequest * CHANGE_VNFPKG: ChangeCurrentVnfPkgRequest\n",
- "type": "object"
- },
- "isCancelPending": {
- "description": "The Boolean is a data type having two values (true and false).\n",
- "type": "boolean"
- },
- "cancelMode": {
- "description": "Cancellation mode. GRACEFUL: If the VNF LCM operation occurrence is in \"PROCESSING\" or \"ROLLING_BACK\" state, the VNFM shall not start any new resource management operation and shall wait for the ongoing resource management operations in the underlying system, typically the VIM, to finish execution or to time out. After that, the VNFM shall put the operation occurrence into the FAILED_TEMP state. If the VNF LCM operation occurrence is in \"STARTING\" state, the VNFM shall not start any resource management operation and shall wait for the granting request to finish execution or time out. After that, the VNFM shall put the operation occurrence into the ROLLED_BACK state. FORCEFUL: If the VNF LCM operation occurrence is in \"PROCESSING\" or \"ROLLING_BACK\" state, the VNFM shall not start any new resource management operation, shall cancel the ongoing resource management operations in the underlying system, typically the VIM, and shall wait for the cancellation to finish or to time out. After that, the VNFM shall put the operation occurrence into the FAILED_TEMP state. If the VNF LCM operation occurrence is in \"STARTING\" state, the VNFM shall not start any resource management operation and put the operation occurrence into the ROLLED_BACK state.\n",
- "type": "string",
- "enum": ["GRACEFUL", "FORCEFUL"]
- },
- "error": {
- "description": "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 is reproduced inthis structure. Compared to the general framework defined in IETF RFC 7807, 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 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.\n",
- "type": "object",
- "required": ["status", "detail"],
- "properties": {
- "type": {
- "description": "A URI reference according to IETF RFC 3986 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"
- }
- }
- },
- "resourceChanges": {
- "description": "This attribute contains information about the cumulative changes to virtualised resources that were performed so far by the LCM operation since its start, if applicable.\n",
- "type": "object",
- "properties": {
- "affectedVnfcs": {
- "description": "Information about VNFC 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 VNFCs. It shall comply with the provisions in table 5.5.3.13-1.\nNOTE:\tThe \"resourceDefinitionId\" attribute provides information to the API consumer \n (i.e. the NFVO) to assist in correlating the resource changes performed during \n the LCM operation with the granted resources in a specific Grant exchange, which \n is identified by the \"grantId\" available in the \"Individual VNF lifecycle management \n operation occurrence\" and the \"id\" in the \"Individual Grant\".\n",
- "type": "object",
- "required": ["id", "vduId", "changeType", "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"
- },
- "vduId": {
- "description": "An identifier that is unique within a VNF descriptor.\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: * ADDED * REMOVED * MODIFIED * TEMPORARY For a temporary resource, an AffectedVnfc structure exists as long as the temporary resource exists.\n",
- "type": "string",
- "enum": ["ADDED", "REMOVED", "MODIFIED", "TEMPORARY"]
- },
- "computeResource": {
- "required": ["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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
- "type": "string"
- }
- }
- },
- "resourceDefinitionId": {
- "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\n",
- "type": "string"
- },
- "zoneId": {
- "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 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"
- },
- "affectedVnfcCpIds": {
- "description": "Identifiers of CP(s) of the VNFC instance that were affected by the change. Shall be present for those affected CPs of the VNFC instance that are associated to an external CP of the VNF instance. May be present for further affected CPs of the VNFC instance.\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"
- }
- },
- "addedStorageResourceIds": {
- "description": "References to VirtualStorage resources that have been added. Each value refers to a VirtualStorageResourceInfo item in the VnfInstance that was added to the VNFC. It shall be provided if at least one storage resource was added to the VNFC.\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"
- }
- },
- "removedStorageResourceIds": {
- "description": "References to VirtualStorage resources that have been removed. The value contains the identifier of a VirtualStorageResourceInfo item that has been removed from the VNFC, and might no longer exist in the VnfInstance. It shall be provided if at least one storage resource was removed from the VNFC.\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"
- }
- }
- }
- }
- },
- "affectedVirtualLinks": {
- "description": "Information about VL instances that were affected during the lifecycle operation. See notes 1 and 3.\n",
- "type": "array",
- "items": {
- "description": "This type provides information about added, deleted, modified and temporary VLs, and added or removed VNF link ports.\nNOTE 1:\tWhen signalling the addition (LINK_PORT_ADDED) or removal (LINK_PORT_REMOVED) of VNF link ports, \n the \"networkResource\" and \"resourceDefinitionId\" attributes refer to the affected virtual link \n instance, not the link port instance. The resource handles of the affected VNF link ports can be \n found by dereferencing the identifiers in the \"vnfLinkPortIds\" attribute.\nNOTE 2:\tThe \"resourceDefinitionId\" attribute provides information to the API consumer (i.e. the NFVO) to \n assist in correlating the resource changes performed during the LCM operation with the granted \n resources in a specific Grant exchange, which is identified by the \"grantId\" available in the \n \"Individual VNF lifecycle management operation occurrence\" and the \"id\" in the \"Individual Grant\".\n",
- "type": "object",
- "required": [
- "id",
- "vnfVirtualLinkDescId",
- "changeType",
- "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"
- },
- "vnfVirtualLinkDescId": {
- "description": "An identifier that is unique within a VNF descriptor.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "changeType": {
- "description": "Signals the type of change.\nPermitted values: -\tADDED -\tREMOVED -\tMODIFIED -\tTEMPORARY -\tLINK_PORT_ADDED -\tLINK_PORT_REMOVED For a temporary resource, an AffectedVirtualLink structure exists as long as the temporary resource exists. See note 1.\n",
- "type": "string",
- "enum": [
- "ADDED",
- "REMOVED",
- "MODIFIED",
- "TEMPORARY",
- "LINK_PORT_ADDED",
- "LINK_PORT_REMOVED"
- ]
- },
- "networkResource": {
- "required": ["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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
- "type": "string"
- }
- }
- },
- "vnfLinkPortIds": {
- "description": "Identifiers of the link ports of the affected VL related to the change. Each identifier references a \"VnfLinkPortInfo\" structure.\nShall be set when changeType is equal to \"LINK_PORT_ADDED\" or \"LINK_PORT_REMOVED\", and the related \"VnfLinkPortInfo\" structures are present (case \"added\") or have been present (case \"removed\") in the \"VnfVirtualLinkResourceInfo\" or \"ExtManagedVirtualLinkInfo\" structures that are represented by the \"vnfVirtualLinkResource¬Info\" or \"extManagedVirtualLinkInfo\" attribute in the \"VnfInstance\" structure. See note 1.\n",
- "type": "array",
- "items": {
- "description": "An identifier that is unique within a VNF descriptor.\n",
- "type": "string"
- }
- },
- "resourceDefinitionId": {
- "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\n",
- "type": "string"
- },
- "zoneId": {
- "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 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"
- }
- }
- }
- },
- "affectedExtLinkPorts": {
- "description": "Information about external VNF link ports that were affected during the lifecycle operation. See note 1.\n",
- "type": "array",
- "items": {
- "description": "This type provides information about added and deleted external link ports (link ports attached to external virtual links). It shall comply with the provisions in table 5.5.3.14a-1.\nNOTE:\tThe \"resourceDefinitionId\" attribute provides information to the API consumer (i.e. the NFVO) to assist in correlating \n the resource changes performed during the LCM operation with the granted resources in a specific Grant exchange, which \n is identified by the \"grantId\" available in the \"Individual VNF lifecycle management operation occurrence\" and the \"id\" \n in the \"Individual Grant\".\n",
- "type": "object",
- "required": [
- "id",
- "changeType",
- "extCpInstanceId",
- "resourceHandle"
- ],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "changeType": {
- "description": "Signals the type of change. Permitted values: -\tADDED - MODIFIED -\tREMOVED\n",
- "type": "string",
- "enum": ["ADDED", "REMOVED"]
- },
- "extCpInstanceId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "resourceHandle": {
- "required": ["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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
- "type": "string"
- }
- }
- },
- "resourceDefinitionId": {
- "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- }
- },
- "affectedVirtualStorages": {
- "description": "Information about virtualised storage 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 virtual storage resources. It shall comply with the provisions in table 5.5.3.15-1.\nNOTE:\tThe \"resourceDefinitionId\" attribute provides information to the API consumer (i.e. the NFVO) to \n assist in correlating the resource changes performed during the LCM operation with the granted \n resources in a specific Grant exchange, which is identified by the \"grantId\" available in the \n \"Individual VNF lifecycle management operation occurrence\" and the \"id\" in the \"Individual Grant\".\n",
- "type": "object",
- "required": [
- "id",
- "virtualStorageDescId",
- "changeType",
- "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": "An identifier that is unique within a VNF descriptor.\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: * ADDED * REMOVED * MODIFIED * TEMPORARY For a temporary resource, an AffectedVirtualStorage structure exists as long as the temporary resource exists.\n",
- "type": "string",
- "enum": ["ADDED", "REMOVED", "MODIFIED", "TEMPORARY"]
- },
- "storageResource": {
- "required": ["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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
- "type": "string"
- }
- }
- },
- "resourceDefinitionId": {
- "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\n",
- "type": "string"
- },
- "zoneId": {
- "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 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"
- }
- }
- }
- }
- }
- },
- "changedInfo": {
- "description": "This type represents attribute modifications that were performed on an \"Individual VNF instance\" resource. The attributes that can be included consist of those requested to be modified explicitly in the \"VnfInfoModificationRequest\" data structure, and additional attributes of the \"VnfInstance\" data structure that were modified implicitly e.g. when modifying the referenced VNF package. The \"VnfInfoModifications\" data type shall comply with the provisions defined in table 5.5.2.12a-1.\nNOTE:\tIf present, this attribute (which depends on the value of the \"vnfdId\" attribute) \n was modified implicitly following a request to modify the \"vnfdId\" attribute, by \n copying the value of this attribute from the VNFD in the VNF Package identified by \n the \"vnfdId\" attribute.\n",
- "type": "object",
- "properties": {
- "vnfInstanceName": {
- "description": "A string defined in IETF RFC 8259.\n",
- "type": "string"
- },
- "vnfInstanceDescription": {
- "description": "A string defined in IETF RFC 8259.\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 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"
- },
- "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 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"
- },
- "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 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"
- },
- "vimConnectionInfo": {
- "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 for managing the resources of a VNF instance. * 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 is provided through a secure connection over\n HTTP Secure (HTTP over SSL/TLS), and the connection might also be established through a VPN\n (for example TLS-based VPN tunnelling) for site-to-site connection, the \"accessInfo\" JSON data\n structure, and the sensitive data related information (\"username\"/\"password\" as required properties\n for authentication purpose), will be transmitted as plain text through a TLS tunnel without additional\n encoding/encryption before transmitting it, making the sensitive data visible to the endpoint.\n The base64 encoded certificates are only used by the VNFM to verify the authenticity of the\n interface endpoint of the VIM.\n",
- "type": "object",
- "required": ["vimType"],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vimType": {
- "description": "Discriminator for the different types of the VIM information. The value of this attribute determines the structure of the \"interfaceInfo\" and \"accessInfo\" attributes, based on the type of the VIM. The set of permitted values is expected to change over time as new types or versions of VIMs become available. The ETSI NFV registry of VIM-related information provides access to information about VimConnectionInfo definitions for various VIM types. The structure of the registry is defined in Annex C of SOL003.\n",
- "type": "string"
- },
- "interfaceInfo": {
- "description": "This 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"
- },
- "accessInfo": {
- "description": "This 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"
- },
- "extra": {
- "description": "This 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"
- }
- }
- }
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfProvider": {
- "description": "A string defined in IETF RFC 8259.\n",
- "type": "string"
- },
- "vnfProductName": {
- "description": "A string defined in IETF RFC 8259.\n",
- "type": "string"
- },
- "vnfSoftwareVersion": {
- "description": "A version.\n",
- "type": "string"
- },
- "vnfdVersion": {
- "description": "A version.\n",
- "type": "string"
- }
- }
- },
- "affectedVipCps": {
- "description": "Information about virtual IP CP instances that were affected during the execution of the lifecycle management operation.\n",
- "type": "array",
- "items": {
- "description": "This type provides information about added, deleted and modified virtual IP CP instances.\n",
- "type": "object",
- "required": ["cpInstanceId", "cpdId", "changeType"],
- "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": "An identifier that is unique within a VNF descriptor.\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: -\tADDED -\tREMOVED -\tMODIFIED\n",
- "type": "string",
- "enum": ["ADDED", "REMOVED", "MODIFIED"]
- }
- }
- }
- },
- "changedExtConnectivity": {
- "description": "Information about changed external connectivity, if applicable. See note 1.\n",
- "type": "array",
- "items": {
- "description": "This type represents information about an external VL. It shall comply with the provisions defined in table 5.5.3.2-1.\nNOTE:\tThis attribute reflects the current configuration information that has resulted from merging into this attribute \n the \"VnfExtCpData\" information which was passed as part of the \"ExtVirtualLinkData\" structure in the input of the \n most recent VNF LCM operation such as \"InstantiateVnfRequest\", \"ChangeExtVnfConnectivityRequest\", \"ChangeVnfFlavourRequest\" \n or \"ChangeCurrentVnfPkgRequest\", or in the Grant response. If applying such change results in an empty list of \n \"currentVnfExtCpData\" structure instances, the affected instance of \"ExtVirtualLinkInfo\" shall be removed from its \n parent data structure.\n",
- "type": "object",
- "required": ["id", "resourceHandle", "currentVnfExtCpData"],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceHandle": {
- "required": ["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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\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. It shall comply with the provisions defined in table 5.5.3.9-1.\nNOTE 1:\tThe use cases UC#4 and UC#5 in clause A.4 of ETSI GS NFV-IFA 007 provide examples for such a configuration. NOTE 2:\tThe 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": {
- "required": ["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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\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.\n",
- "type": "string"
- }
- }
- }
- },
- "currentVnfExtCpData": {
- "description": "Allows the API consumer to read the current CP configuration information for the connection of external CPs to the external virtual link. See note.\n",
- "type": "array",
- "items": {
- "description": "This type represents configuration information for external CPs created. * NOTE 1: \tIn case this identifier refers to a CPD with trunking enabled, the external CP instances created\n from this CPD will represent ports in a trunk.\n* NOTE 2: \tWithin one VNF instance, all VNFC instances created from a particular VDU have the same external\n connectivity. Thus, given a particular value of the \"cpdId\" attribute, there shall be one\n \"cpConfig\" entry for each VNFC instance that has been or can be created from a VDU which includes\n a CPD identified by the \"cpdId\" attribute. If the cpConfig represents a subport in a trunk,\n all \"cpConfig\" entries in this list shall have the same segmentationId, which means they are\n connected to the same set of external VLs via the trunk.\n* NOTE 3: \tThe map entry value shall be set to \"null\" in order to delete a \"VnfExtCpConfig\" entry identified\n by a particular key value from the map, i.e. for the disconnection of an existing external\n CP instance addressed by cpInstanceId in the deleted map entry from a particular external\n virtual link, and deletion of that instance in case it represents a subport. Deleting the\n last key from the map removes the affected instance of the \"VnfExtCpData\" structure from\n its parent data structure.\n* NOTE 4: If, as defined by the input parameters of a \"ChangeVnfFlavour\", \"ChangeExtVnfConnectivity\" or \n \"ChangeCurrentVnfPkg\" operation or as part of the Grant response for any of these operations, a \n cpConfig map entry identified by a particular map key value is moved into another \"ExtVirtualLinkData\"\n or \"VnfExtCpData\" structure, this particular cpConfig map entry may be used by an external CP instance\n different than the one that has used it before the operation, or by no external CP instance at all.\n Renaming a CPD identifier during the \"changeCurrentVnfPkg\" operation does not count as moving the\n related \"cpConfig\" map entries to a new \"extCpData\" structure.\n",
- "type": "object",
- "required": ["cpdId"],
- "properties": {
- "cpdId": {
- "description": "An identifier that is unique within a VNF descriptor.\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). See notes 2, 3 and 4.\n",
- "type": "object",
- "additionalProperties": {
- "description": "This type represents an externally provided link port or network address information per instance of an external connection point. In case a link port is provided, the VNFM shall use that link port when connecting the external CP to the external VL. In a link port is not provided, the VNFM shall create a link port on the external VL, and use that link port to connect the external CP to the external VL. * NOTE: The following conditions apply to the attributes \"linkPortId\" and \"cpProtocolData\":\n 1) Void.\n 2) At least one of the \"linkPortId\" and \"cpProtocolData\" attributes shall be present for an external\n CP instance representing a subport that is to be created, or an external CP instance that is to be\n created by creating the corresponding VNFC or VNF instance during the current or a subsequent LCM\n operation, or for an existing external CP instance that is to be re-configured or added to a\n 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\n a pre created link port, and the VNFM can use means outside the scope of the present document to obtain\n the pre-configured address information for the connection point from the resource representing\n the link port.\n 5) If both \"cpProtocolData\" and \"linkportId\" are provided, the API consumer shall ensure that the\n cpProtocolData can be used with the pre-created link port referenced by \"linkPortId\".\n",
- "anyOf": [
- {
- "required": ["linkPortId"]
- },
- {
- "required": ["cpProtocolData"]
- }
- ],
- "type": "object",
- "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 to the VNFM the need to create a dedicated link port for the external CP. If set to True, the VNFM shall create a link port. If set to False, the VNFM shall not create a link port. 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 note.\n",
- "type": "array",
- "items": {
- "description": "This type represents network protocol data. * NOTE:\tThis attribute allows to signal the addition of further types of layer and protocol\n in future versions of the present document in a backwards-compatible way. In the current\n 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). See note.\n",
- "type": "string",
- "enum": ["IP_OVER_ETHERNET"]
- },
- "ipOverEthernet": {
- "description": "This type represents network address data for IP over Ethernet. * NOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. * NOTE 2:\tExactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present. * NOTE 3:\tIf the CP instance represents a subport in a trunk, segmentationId shall be present.\n Otherwise it shall not be present.\n* NOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the actual\n network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header\n of the packets or it may be an identifier used between the application and the NFVI networking\n infrastructure to identify the network sub-interface of the trunk port in question. In the latter\n case the NFVI infrastructure will map this local segmentationId to whatever segmentationId is\n actually used by the NFVIΓÇÖs transport technology.\n",
- "type": "object",
- "anyOf": [
- {
- "required": ["macAddress"]
- },
- {
- "required": ["ipAddresses"]
- }
- ],
- "oneOf": [
- {
- "required": ["fixedAddresses"]
- },
- {
- "required": ["numDynamicAddresses"]
- },
- {
- "required": ["ipAddressRange"]
- }
- ],
- "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: -\tVLAN: the subport uses VLAN as encapsulation type. -\tINHERIT: the subport gets its segmentation type from the network itΓÇÖs 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"],
- "properties": {
- "type": {
- "description": "The type of the IP addresses. Permitted values: IPV4, IPV6.\n",
- "type": "string",
- "enum": ["IPV4", "IPV6"]
- },
- "fixedAddresses": {
- "description": "Fixed addresses to assign (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"
- }
- },
- "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. 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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- },
- "modificationsTriggeredByVnfPkgChange": {
- "description": "This type represents attribute modifications that were performed on an \"Individual VNF instance\" resource when changing the current VNF package. The attributes that can be included consist of those requested to be modified explicitly in the \"ChangeCurrentVnfPkgRequest\" data structure, and additional attributes of the \"VnfInstance\" data structure that were modified implicitly during the operation. The \"ModificationsTriggeredByVnfPkgChange\" data type shall comply with the provisions defined in table 5.5.3.21-1.\nNOTE 1:\tThis attribute represents the delta (semantics as per IETF RFC 7396, JSON Merge Patch) between the value \n of the attribute at the start of the \"Change current VNF package\" operation and the value of the attribute \n at its completion.\nNOTE 2:\tIf present, this attribute (which depends on the value of the \"vnfdId\" attribute) was modified implicitly \n during the related operation and contains a copy of the value of the related attribute from the VNFD in the \n VNF Package identified by the \"vnfdId\" attribute.\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 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"
- },
- "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 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"
- },
- "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 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"
- },
- "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\". See note 2.\n",
- "type": "string"
- },
- "vnfProductName": {
- "description": "If present, this attribute signals the new value of the \"vnfProductName\" attribute in \"VnfInstance\". See note 2.\n",
- "type": "string"
- },
- "vnfSoftwareVersion": {
- "description": "A version.\n",
- "type": "string"
- },
- "vnfdVersion": {
- "description": "A version.\n",
- "type": "string"
- },
- "vimConnectionInfo": {
- "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 for managing the resources of a VNF instance. * 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 is provided through a secure connection over\n HTTP Secure (HTTP over SSL/TLS), and the connection might also be established through a VPN\n (for example TLS-based VPN tunnelling) for site-to-site connection, the \"accessInfo\" JSON data\n structure, and the sensitive data related information (\"username\"/\"password\" as required properties\n for authentication purpose), will be transmitted as plain text through a TLS tunnel without additional\n encoding/encryption before transmitting it, making the sensitive data visible to the endpoint.\n The base64 encoded certificates are only used by the VNFM to verify the authenticity of the\n interface endpoint of the VIM.\n",
- "type": "object",
- "required": ["vimType"],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vimType": {
- "description": "Discriminator for the different types of the VIM information. The value of this attribute determines the structure of the \"interfaceInfo\" and \"accessInfo\" attributes, based on the type of the VIM. The set of permitted values is expected to change over time as new types or versions of VIMs become available. The ETSI NFV registry of VIM-related information provides access to information about VimConnectionInfo definitions for various VIM types. The structure of the registry is defined in Annex C of SOL003.\n",
- "type": "string"
- },
- "interfaceInfo": {
- "description": "This 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"
- },
- "accessInfo": {
- "description": "This 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"
- },
- "extra": {
- "description": "This 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"
- }
- }
- }
- }
- }
- },
- "vnfSnapshotInfoId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "lcmCoordinations": {
- "description": "Information about LCM coordination actions (see clause 10 in ETSI GS NFV-SOL002) related to this LCM operation occurrence.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": [
- "id",
- "coordinationActionName",
- "startTime",
- "endpointType"
- ],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "coordinationActionName": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "coordinationResult": {
- "description": "The enumeration LcmCoordResultType defines the permitted values to represent the result of executing an LCM coordination action. The coordination result also implies the action to be performed by the VNFM as the follow-up to this coordination. Value | Description ------|------------ CONTINUE | The related LCM operation shall be continued, staying in the state \"PROCESSING\". ABORT | The related LCM operation shall be aborted by transitioning into the state \"FAILED_TEMP\". CANCELLED | The coordination action has been cancelled upon request of the API consumer, i.e. the VNFM. The related LCM operation shall be aborted by transitioning into the state \"FAILED_TEMP\".\n",
- "type": "string",
- "enum": ["CONTINUE", "ABORT", "CANCELLED"]
- },
- "startTime": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "endTime": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "delay": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "endpointType": {
- "description": "The endpoint type used by this coordination action. Valid values: ΓÇó\tMGMT: coordination with other operation supporting management systems (e.g. EM) ΓÇó\tVNF: coordination with the VNF instance\n",
- "type": "string",
- "enum": ["MGMT", "VNF"]
- }
- }
- }
- },
- "rejectedLcmCoordinations": {
- "description": "Information about LCM coordination actions (see clause 10 in ETSI GS NFV-SOL002) that were rejected by 503 error which means they can be tried again after a delay. See note 5.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": [
- "coordinationActionName",
- "rejectionTime",
- "endpointType",
- "delay"
- ],
- "properties": {
- "coordinationActionName": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "rejectionTime": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "delay": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "endpointType": {
- "description": "The endpoint type used by this coordination action. Valid values: ΓÇó\tMGMT: coordination with other operation supporting management systems (e.g. EM) ΓÇó\tVNF: coordination with the VNF instance\n",
- "type": "string",
- "enum": ["MGMT", "VNF"]
- }
- }
- }
- },
- "warnings": {
- "description": "Warning messages that were generated while the operation was executing.\nIf the operation has included LCM coordination actions and these have resulted in warnings, such warnings should be added to this attribute.\n",
- "type": "array",
- "items": {
- "type": "string"
- }
- },
- "_links": {
- "description": "Links to resources related to this resource.\n",
- "type": "object",
- "required": ["self", "vnfInstance"],
- "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"
- }
- }
- },
- "vnfInstance": {
- "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"
- }
- }
- },
- "grant": {
- "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"
- }
- }
- },
- "cancel": {
- "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"
- }
- }
- },
- "retry": {
- "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"
- }
- }
- },
- "rollback": {
- "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"
- }
- }
- },
- "fail": {
- "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"
- }
- }
- },
- "vnfSnapshot": {
- "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"
- }
- }
- }
- }
- }
- }
-}
\ No newline at end of file
+ "description": "This type represents a VNF lifecycle management operation occurrence.\nNOTE 1:\tThis allows the NFVO to obtain the information contained in the latest \n \"result\" notification if it has not received it due to an error or a \n wrongly configured subscription filter.\nNOTE 2:\tNot more than one of changedInfo and modificationsTriggeredByVnfPkgChange \n shall be present.\nNOTE 3:\tFor a particular affected VL, there shall be as many \"AffectedVirtualLink\" \n entries as needed for signalling the different types of changes, i.e. one \n per virtual link and change type. For instance, in the case of signaling \n affected VL instances involving the addition of a particular VL instance \n with links ports, one \"AffectedVirtualLink\" entry signals the addition of \n the VL by using the \"changeType\" attribute of \"AffectedVirtualLink\" structure \n equal to \"ADDED\", and another \"AffectedVirtualLink\" entry signals the addition \n of externally visible VNF link ports of the VL by using the \"changeType\" equal \n to \"LINK_PORT_ADDED\".\nNOTE 4:\tA coordination action has timed out if the VNFM has not been able to read the \n \"Individual coordination action\" resource within a timeout interval after requesting \n the coordination to be started or to be cancelled. The length of the timeout interval \n is defined by means outside the scope of the present document.\nNOTE 5: The list of rejected coordinations may be garbage collected if the LCM operation\n occurrence has reached a terminal state, i.e. one of \"COMPLETED\", \"FAILED\" and \"ROLLED_BACK\".\n",
+ "type": "object",
+ "oneOf": [
+ {
+ "required": ["changedInfo"]
+ },
+ {
+ "required": ["modificationsTriggeredByVnfPkgChange"]
+ }
+ ],
+ "required": [
+ "id",
+ "operationState",
+ "stateEnteredTime",
+ "startTime",
+ "vnfInstanceId",
+ "operation",
+ "isAutomaticInvocation",
+ "isCancelPending"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "operationState": {
+ "description": "STARTING: The LCM operation is starting. PROCESSING: The LCM operation is currently in execution. COMPLETED: The LCM operation has been completed successfully. FAILED_TEMP: The LCM operation has failed and execution has stopped, but the execution of the operation is not considered to be closed. FAILED: The LCM operation has failed and it cannot be retried or rolled back, as it is determined that such action won't succeed. ROLLING_BACK: The LCM operation is currently being rolled back. ROLLED_BACK: The LCM operation has been successfully rolled back, i.e. The state of the VNF prior to the original operation invocation has been restored as closely as possible.\n",
+ "type": "string",
+ "enum": [
+ "STARTING",
+ "PROCESSING",
+ "COMPLETED",
+ "FAILED_TEMP",
+ "FAILED",
+ "ROLLING_BACK",
+ "ROLLED_BACK"
+ ]
+ },
+ "stateEnteredTime": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "startTime": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "vnfInstanceId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "grantId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "operation": {
+ "description": "The enumeration LcmOpType defines the permitted values to represent VNF lifecycle operation types in VNF lifecycle management operation occurrence resources and VNF lifecycle management operation occurrence notifications.\nValue | Description ------|------------ INSTANTIATE | Represents the \"Instantiate VNF\" LCM operation. SCALE | Represents the \"Scale VNF\" LCM operation. SCALE_TO_LEVEL | Represents the \"Scale VNF to Level\" LCM operation. CHANGE_FLAVOUR | Represents the \"Change VNF Flavour\" LCM operation. TERMINATE | Represents the \"Terminate VNF\" LCM operation. HEAL | Represents the \"Heal VNF\" LCM operation. OPERATE | Represents the \"Operate VNF\" LCM operation. CHANGE_EXT_CONN | Represents the \"Change external VNF connectivity\" LCM operation. MODIFY_INFO | Represents the \"Modify VNF Information\" LCM operation. CREATE_SNAPSHOT | Represents the \"Create VNF Snapshot\" LCM operation. REVERT_TO_SNAPSHOT | Represents the “Revert-To VNF Snapshot\" LCM operation. CHANGE_VNFPKG | Represents the \"Change current VNF package\" LCM operation.\n",
+ "type": "string",
+ "enum": [
+ "INSTANTIATE",
+ "SCALE",
+ "SCALE_TO_LEVEL",
+ "CHANGE_FLAVOUR",
+ "TERMINATE",
+ "HEAL",
+ "OPERATE",
+ "CHANGE_EXT_CONN",
+ "MODIFY_INFO",
+ "CREATE_SNAPSHOT",
+ "REVERT_TO_SNAPSHOT",
+ "CHANGE_VNFPKG"
+ ]
+ },
+ "isAutomaticInvocation": {
+ "description": "The Boolean is a data type having two values (true and false).\n",
+ "type": "boolean"
+ },
+ "operationParams": {
+ "description": "Input parameters of the LCM operation. This attribute shall be formatted according to the request data type of the related LCM operation. In addition, the provisions in clause 5.7 shall apply. \nThe following mapping between operationType and the data type of this attribute shall apply: * INSTANTIATE: InstantiateVnfRequest * SCALE: ScaleVnfRequest * SCALE_TO_LEVEL: ScaleVnfToLevelRequest * CHANGE_FLAVOUR: ChangeVnfFlavourRequest * OPERATE: OperateVnfRequest * HEAL: HealVnfRequest * CHANGE_EXT_CONN: ChangeExtVnfConnectivityRequest * TERMINATE: TerminateVnfRequest * MODIFY_INFO: VnfInfoModifications * CREATE_SNAPSHOT: CreateVnfSnapshotRequest * REVERT_TO_SNAPSHOT: RevertToVnfSnapshotRequest * CHANGE_VNFPKG: ChangeCurrentVnfPkgRequest\n",
+ "type": "object"
+ },
+ "isCancelPending": {
+ "description": "The Boolean is a data type having two values (true and false).\n",
+ "type": "boolean"
+ },
+ "cancelMode": {
+ "description": "Cancellation mode. GRACEFUL: If the VNF LCM operation occurrence is in \"PROCESSING\" or \"ROLLING_BACK\" state, the VNFM shall not start any new resource management operation and shall wait for the ongoing resource management operations in the underlying system, typically the VIM, to finish execution or to time out. After that, the VNFM shall put the operation occurrence into the FAILED_TEMP state. If the VNF LCM operation occurrence is in \"STARTING\" state, the VNFM shall not start any resource management operation and shall wait for the granting request to finish execution or time out. After that, the VNFM shall put the operation occurrence into the ROLLED_BACK state. FORCEFUL: If the VNF LCM operation occurrence is in \"PROCESSING\" or \"ROLLING_BACK\" state, the VNFM shall not start any new resource management operation, shall cancel the ongoing resource management operations in the underlying system, typically the VIM, and shall wait for the cancellation to finish or to time out. After that, the VNFM shall put the operation occurrence into the FAILED_TEMP state. If the VNF LCM operation occurrence is in \"STARTING\" state, the VNFM shall not start any resource management operation and put the operation occurrence into the ROLLED_BACK state.\n",
+ "type": "string",
+ "enum": ["GRACEFUL", "FORCEFUL"]
+ },
+ "error": {
+ "description": "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 is reproduced inthis structure. Compared to the general framework defined in IETF RFC 7807, 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 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.\n",
+ "type": "object",
+ "required": ["status", "detail"],
+ "properties": {
+ "type": {
+ "description": "A URI reference according to IETF RFC 3986 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"
+ }
+ }
+ },
+ "resourceChanges": {
+ "description": "This attribute contains information about the cumulative changes to virtualised resources that were performed so far by the LCM operation since its start, if applicable.\n",
+ "type": "object",
+ "properties": {
+ "affectedVnfcs": {
+ "description": "Information about VNFC 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 VNFCs.\nNOTE:\tThe \"resourceDefinitionId\" attribute provides information to the API consumer \n (i.e. the NFVO) to assist in correlating the resource changes performed during \n the LCM operation with the granted resources in a specific Grant exchange, which \n is identified by the \"grantId\" available in the \"Individual VNF lifecycle management \n operation occurrence\" and the \"id\" in the \"Individual Grant\".\n",
+ "type": "object",
+ "required": ["id", "vduId", "changeType", "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"
+ },
+ "vduId": {
+ "description": "An identifier that is unique within a VNF descriptor.\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: * ADDED * REMOVED * MODIFIED * TEMPORARY For a temporary resource, an AffectedVnfc structure exists as long as the temporary resource exists.\n",
+ "type": "string",
+ "enum": ["ADDED", "REMOVED", "MODIFIED", "TEMPORARY"]
+ },
+ "computeResource": {
+ "required": ["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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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"
+ }
+ }
+ },
+ "resourceDefinitionId": {
+ "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "zoneId": {
+ "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 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"
+ },
+ "affectedVnfcCpIds": {
+ "description": "Identifiers of CP(s) of the VNFC instance that were affected by the change. Shall be present for those affected CPs of the VNFC instance that are associated to an external CP of the VNF instance. May be present for further affected CPs of the VNFC instance.\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"
+ }
+ },
+ "addedStorageResourceIds": {
+ "description": "References to VirtualStorage resources that have been added. Each value refers to a VirtualStorageResourceInfo item in the VnfInstance that was added to the VNFC. It shall be provided if at least one storage resource was added to the VNFC.\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"
+ }
+ },
+ "removedStorageResourceIds": {
+ "description": "References to VirtualStorage resources that have been removed. The value contains the identifier of a VirtualStorageResourceInfo item that has been removed from the VNFC, and might no longer exist in the VnfInstance. It shall be provided if at least one storage resource was removed from the VNFC.\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"
+ }
+ }
+ }
+ }
+ },
+ "affectedVirtualLinks": {
+ "description": "Information about VL instances that were affected during the lifecycle operation. See notes 1 and 3.\n",
+ "type": "array",
+ "items": {
+ "description": "This type provides information about added, deleted, modified and temporary VLs, and added or removed VNF link ports.\nNOTE 1:\tWhen signalling the addition (LINK_PORT_ADDED) or removal (LINK_PORT_REMOVED) of VNF link ports, \n the \"networkResource\" and \"resourceDefinitionId\" attributes refer to the affected virtual link \n instance, not the link port instance. The resource handles of the affected VNF link ports can be \n found by dereferencing the identifiers in the \"vnfLinkPortIds\" attribute.\nNOTE 2:\tThe \"resourceDefinitionId\" attribute provides information to the API consumer (i.e. the NFVO) to \n assist in correlating the resource changes performed during the LCM operation with the granted \n resources in a specific Grant exchange, which is identified by the \"grantId\" available in the \n \"Individual VNF lifecycle management operation occurrence\" and the \"id\" in the \"Individual Grant\".\n",
+ "type": "object",
+ "required": [
+ "id",
+ "vnfVirtualLinkDescId",
+ "changeType",
+ "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"
+ },
+ "vnfVirtualLinkDescId": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "changeType": {
+ "description": "Signals the type of change.\nPermitted values: -\tADDED -\tREMOVED -\tMODIFIED -\tTEMPORARY -\tLINK_PORT_ADDED -\tLINK_PORT_REMOVED For a temporary resource, an AffectedVirtualLink structure exists as long as the temporary resource exists. See note 1.\n",
+ "type": "string",
+ "enum": [
+ "ADDED",
+ "REMOVED",
+ "MODIFIED",
+ "TEMPORARY",
+ "LINK_PORT_ADDED",
+ "LINK_PORT_REMOVED"
+ ]
+ },
+ "networkResource": {
+ "required": ["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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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"
+ }
+ }
+ },
+ "vnfLinkPortIds": {
+ "description": "Identifiers of the link ports of the affected VL related to the change. Each identifier references a \"VnfLinkPortInfo\" structure.\nShall be set when changeType is equal to \"LINK_PORT_ADDED\" or \"LINK_PORT_REMOVED\", and the related \"VnfLinkPortInfo\" structures are present (case \"added\") or have been present (case \"removed\") in the \"VnfVirtualLinkResourceInfo\" or \"ExtManagedVirtualLinkInfo\" structures that are represented by the \"vnfVirtualLinkResource¬Info\" or \"extManagedVirtualLinkInfo\" attribute in the \"VnfInstance\" structure. See note 1.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ }
+ },
+ "resourceDefinitionId": {
+ "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "zoneId": {
+ "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 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"
+ }
+ }
+ }
+ },
+ "affectedExtLinkPorts": {
+ "description": "Information about external VNF link ports that were affected during the lifecycle operation. See note 1.\n",
+ "type": "array",
+ "items": {
+ "description": "This type provides information about added and deleted external link ports (link ports attached to external virtual links).\nNOTE:\tThe \"resourceDefinitionId\" attribute provides information to the API consumer (i.e. the NFVO) to assist in correlating \n the resource changes performed during the LCM operation with the granted resources in a specific Grant exchange, which \n is identified by the \"grantId\" available in the \"Individual VNF lifecycle management operation occurrence\" and the \"id\" \n in the \"Individual Grant\".\n",
+ "type": "object",
+ "required": [
+ "id",
+ "changeType",
+ "extCpInstanceId",
+ "resourceHandle"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "changeType": {
+ "description": "Signals the type of change. Permitted values: -\tADDED - MODIFIED -\tREMOVED\n",
+ "type": "string",
+ "enum": ["ADDED", "MODIFIED", "REMOVED"]
+ },
+ "extCpInstanceId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "resourceHandle": {
+ "required": ["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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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"
+ }
+ }
+ },
+ "resourceDefinitionId": {
+ "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "affectedVirtualStorages": {
+ "description": "Information about virtualised storage 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 virtual storage resources.\nNOTE:\tThe \"resourceDefinitionId\" attribute provides information to the API consumer (i.e. the NFVO) to \n assist in correlating the resource changes performed during the LCM operation with the granted \n resources in a specific Grant exchange, which is identified by the \"grantId\" available in the \n \"Individual VNF lifecycle management operation occurrence\" and the \"id\" in the \"Individual Grant\".\n",
+ "type": "object",
+ "required": [
+ "id",
+ "virtualStorageDescId",
+ "changeType",
+ "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": "An identifier that is unique within a VNF descriptor.\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: * ADDED * REMOVED * MODIFIED * TEMPORARY For a temporary resource, an AffectedVirtualStorage structure exists as long as the temporary resource exists.\n",
+ "type": "string",
+ "enum": ["ADDED", "REMOVED", "MODIFIED", "TEMPORARY"]
+ },
+ "storageResource": {
+ "required": ["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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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"
+ }
+ }
+ },
+ "resourceDefinitionId": {
+ "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "zoneId": {
+ "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 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"
+ }
+ }
+ }
+ }
+ }
+ },
+ "changedInfo": {
+ "description": "This type represents attribute modifications that were performed on an \"Individual VNF instance\" resource. The attributes that can be included consist of those requested to be modified explicitly in the \"VnfInfoModificationRequest\" data structure, and additional attributes of the \"VnfInstance\" data structure that were modified implicitly e.g. when modifying the referenced VNF package.\nNOTE:\tIf present, this attribute (which depends on the value of the \"vnfdId\" attribute) \n was modified implicitly following a request to modify the \"vnfdId\" attribute, by \n copying the value of this attribute from the VNFD in the VNF Package identified by \n the \"vnfdId\" attribute.\n",
+ "type": "object",
+ "properties": {
+ "vnfInstanceName": {
+ "description": "A string defined in IETF RFC 8259.\n",
+ "type": "string"
+ },
+ "vnfInstanceDescription": {
+ "description": "A string defined in IETF RFC 8259.\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 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"
+ },
+ "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 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"
+ },
+ "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 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"
+ },
+ "vimConnectionInfo": {
+ "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",
+ "type": "object",
+ "required": ["vimType"],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vimType": {
+ "description": "Discriminator for the different types of the VIM information. The value of this attribute determines the structure of the \"interfaceInfo\" and \"accessInfo\" attributes, based on the type of the VIM., CISM, CIR or MCIOP repository. The set of permitted values is expected to change over time as new types or versions of VIMs become available. The ETSI NFV registry of VIM-related information [i.3] provides access to information about VimConnectionInfo definitions for various VIM, CISM, CIR or MCIOP repository types. The structure of the registry is defined in annex C.\n",
+ "type": "string"
+ },
+ "interfaceInfo": {
+ "description": "This 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"
+ },
+ "accessInfo": {
+ "description": "This 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"
+ },
+ "extra": {
+ "description": "This 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"
+ }
+ }
+ }
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfProvider": {
+ "description": "A string defined in IETF RFC 8259.\n",
+ "type": "string"
+ },
+ "vnfProductName": {
+ "description": "A string defined in IETF RFC 8259.\n",
+ "type": "string"
+ },
+ "vnfSoftwareVersion": {
+ "description": "A version.\n",
+ "type": "string"
+ },
+ "vnfdVersion": {
+ "description": "A version.\n",
+ "type": "string"
+ }
+ }
+ },
+ "affectedVipCps": {
+ "description": "Information about virtual IP CP instances that were affected during the execution of the lifecycle management operation.\n",
+ "type": "array",
+ "items": {
+ "description": "This type provides information about added, deleted and modified virtual IP CP instances.\n",
+ "type": "object",
+ "required": ["cpInstanceId", "cpdId", "changeType"],
+ "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": "An identifier that is unique within a VNF descriptor.\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: -\tADDED -\tREMOVED -\tMODIFIED\n",
+ "type": "string",
+ "enum": ["ADDED", "REMOVED", "MODIFIED"]
+ }
+ }
+ }
+ },
+ "changedExtConnectivity": {
+ "description": "Information about changed external connectivity, if applicable. See note 1.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents information about an external VL.\nNOTE:\tThis attribute reflects the current configuration information that has resulted from merging into this attribute \n the \"VnfExtCpData\" information which was passed as part of the \"ExtVirtualLinkData\" structure in the input of the \n most recent VNF LCM operation such as \"InstantiateVnfRequest\", \"ChangeExtVnfConnectivityRequest\", \"ChangeVnfFlavourRequest\" \n or \"ChangeCurrentVnfPkgRequest\", or in the Grant response. If applying such change results in an empty list of \n \"currentVnfExtCpData\" structure instances, the affected instance of \"ExtVirtualLinkInfo\" shall be removed from its \n parent data structure.\n",
+ "type": "object",
+ "required": ["id", "resourceHandle", "currentVnfExtCpData"],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceHandle": {
+ "required": ["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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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.\nNOTE 1:\tThe use cases UC#4 and UC#5 in clause A.4 of ETSI GS NFV-IFA 007 provide examples for such a configuration. NOTE 2:\tThe 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": {
+ "required": ["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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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 the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "currentVnfExtCpData": {
+ "description": "Allows the API consumer to read the current CP configuration information for the connection of external CPs to the external virtual link. See note.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents configuration information for external CPs created. * NOTE 1: \tIn case this identifier refers to a CPD with trunking enabled, the external CP instances created\n from this CPD will represent ports in a trunk.\n* NOTE 2: \tWithin one VNF instance, all VNFC instances created from a particular VDU have the same external\n connectivity. Thus, given a particular value of the \"cpdId\" attribute, there shall be one\n \"cpConfig\" entry for each VNFC instance that has been or can be created from a VDU which includes\n a CPD identified by the \"cpdId\" attribute. If the cpConfig represents a subport in a trunk,\n all \"cpConfig\" entries in this list shall have the same segmentationId, which means they are\n connected to the same set of external VLs via the trunk.\n* NOTE 3: \tThe map entry value shall be set to \"null\" in order to delete a \"VnfExtCpConfig\" entry identified\n by a particular key value from the map, i.e. for the disconnection of an existing external\n CP instance addressed by cpInstanceId in the deleted map entry from a particular external\n virtual link, and deletion of that instance in case it represents a subport. Deleting the\n last key from the map removes the affected instance of the \"VnfExtCpData\" structure from\n its parent data structure.\n* NOTE 4: If, as defined by the input parameters of a \"ChangeVnfFlavour\", \"ChangeExtVnfConnectivity\" or\n \"ChangeCurrentVnfPkg\" operation or as part of the Grant response for any of these operations, a cpConfig\n map entry identified by a particular map key value is moved into another \"ExtVirtualLinkData\" or\n \"VnfExtCpData\" structure, this particular cpConfig map entry may be used by an external CP instance\n different than the one that has used it before the operation, or by no external CP instance at all.\n Renaming a CPD identifier during the \"changeCurrentVnfPkg\" operation does not count as moving the related\n \"cpConfig\" map entries to a new \"extCpData\" structure.\n",
+ "type": "object",
+ "required": ["cpdId"],
+ "properties": {
+ "cpdId": {
+ "description": "An identifier that is unique within a VNF descriptor.\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 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",
+ "anyOf": [
+ {
+ "required": ["linkPortId"]
+ },
+ {
+ "required": ["cpProtocolData"]
+ },
+ {
+ "required": ["netAttDefResourceId"]
+ }
+ ],
+ "type": "object",
+ "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 to the VNFM the need to create a dedicated link port for the external CP. If set to True, the VNFM shall create a link port. If set to False, the VNFM shall not create a link port. 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"
+ },
+ "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 2, 3 and 4.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ },
+ "cpProtocolData": {
+ "description": "Parameters for configuring the network protocols on the link port that connects the CP to a VL. See notes 1 and 2.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents network protocol data. * NOTE:\tThis attribute allows to signal the addition of further types of layer and protocol\n in future versions of the present document in a backwards-compatible way. In the current\n 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:\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 network address data for IP over Ethernet. * NOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. * NOTE 2:\tExactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present. * NOTE 3:\tIf the CP instance represents a subport in a trunk, segmentationId shall be present.\n Otherwise it shall not be present.\n* NOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the actual\n network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header\n of the packets or it may be an identifier used between the application and the NFVI networking\n infrastructure to identify the network sub-interface of the trunk port in question. In the latter\n case the NFVI infrastructure will map this local segmentationId to whatever segmentationId is\n actually used by the NFVI’s transport technology.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "required": ["macAddress"]
+ },
+ {
+ "required": ["ipAddresses"]
+ }
+ ],
+ "oneOf": [
+ {
+ "required": ["fixedAddresses"]
+ },
+ {
+ "required": ["numDynamicAddresses"]
+ },
+ {
+ "required": ["ipAddressRange"]
+ }
+ ],
+ "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: -\tVLAN: the subport uses VLAN as encapsulation type. -\tINHERIT: the subport gets its segmentation type from the network it’s 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"],
+ "properties": {
+ "type": {
+ "description": "The type of the IP addresses. Permitted values: IPV4, IPV6.\n",
+ "type": "string",
+ "enum": ["IPV4", "IPV6"]
+ },
+ "fixedAddresses": {
+ "description": "Fixed addresses to assign (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"
+ }
+ },
+ "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. 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.\n",
+ "type": "string"
+ }
+ }
+ }
+ }
+ }
+ },
+ "virtualCpAddress": {
+ "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",
+ "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"
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ },
+ "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 contains 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": {
+ "required": ["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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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 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 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"
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ },
+ "modificationsTriggeredByVnfPkgChange": {
+ "description": "This type represents attribute modifications that were performed on an \"Individual VNF instance\" resource when changing the current VNF package. The attributes that can be included consist of those requested to be modified explicitly in the \"ChangeCurrentVnfPkgRequest\" data structure, and additional attributes of the \"VnfInstance\" data structure that were modified implicitly during the operation.\nNOTE 1:\tThis attribute represents the delta (semantics as per IETF RFC 7396, JSON Merge Patch) between the value \n of the attribute at the start of the \"Change current VNF package\" operation and the value of the attribute \n at its completion.\nNOTE 2:\tIf present, this attribute (which depends on the value of the \"vnfdId\" attribute) was modified implicitly \n during the related operation and contains a copy of the value of the related attribute from the VNFD in the \n VNF Package identified by the \"vnfdId\" attribute.\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 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"
+ },
+ "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 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"
+ },
+ "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 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"
+ },
+ "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\". See note 2.\n",
+ "type": "string"
+ },
+ "vnfProductName": {
+ "description": "If present, this attribute signals the new value of the \"vnfProductName\" attribute in \"VnfInstance\". See note 2.\n",
+ "type": "string"
+ },
+ "vnfSoftwareVersion": {
+ "description": "A version.\n",
+ "type": "string"
+ },
+ "vnfdVersion": {
+ "description": "A version.\n",
+ "type": "string"
+ },
+ "vimConnectionInfo": {
+ "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",
+ "type": "object",
+ "required": ["vimType"],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vimType": {
+ "description": "Discriminator for the different types of the VIM information. The value of this attribute determines the structure of the \"interfaceInfo\" and \"accessInfo\" attributes, based on the type of the VIM., CISM, CIR or MCIOP repository. The set of permitted values is expected to change over time as new types or versions of VIMs become available. The ETSI NFV registry of VIM-related information [i.3] provides access to information about VimConnectionInfo definitions for various VIM, CISM, CIR or MCIOP repository types. The structure of the registry is defined in annex C.\n",
+ "type": "string"
+ },
+ "interfaceInfo": {
+ "description": "This 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"
+ },
+ "accessInfo": {
+ "description": "This 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"
+ },
+ "extra": {
+ "description": "This 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"
+ }
+ }
+ }
+ }
+ }
+ },
+ "vnfSnapshotInfoId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "lcmCoordinations": {
+ "description": "Information about LCM coordination actions (see clause 10 in ETSI GS NFV-SOL002) related to this LCM operation occurrence.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": [
+ "id",
+ "coordinationActionName",
+ "startTime",
+ "endpointType"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "coordinationActionName": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "coordinationResult": {
+ "description": "The enumeration LcmCoordResultType defines the permitted values to represent the result of executing an LCM coordination action. The coordination result also implies the action to be performed by the VNFM as the follow-up to this coordination. Value | Description ------|------------ CONTINUE | The related LCM operation shall be continued, staying in the state \"PROCESSING\". ABORT | The related LCM operation shall be aborted by transitioning into the state \"FAILED_TEMP\". CANCELLED | The coordination action has been cancelled upon request of the API consumer, i.e. the VNFM. The related LCM operation shall be aborted by transitioning into the state \"FAILED_TEMP\".\n",
+ "type": "string",
+ "enum": ["CONTINUE", "ABORT", "CANCELLED"]
+ },
+ "startTime": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "endTime": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "delay": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "endpointType": {
+ "description": "The endpoint type used by this coordination action. Valid values: •\tMGMT: coordination with other operation supporting management systems (e.g. EM) •\tVNF: coordination with the VNF instance\n",
+ "type": "string",
+ "enum": ["MGMT", "VNF"]
+ }
+ }
+ }
+ },
+ "rejectedLcmCoordinations": {
+ "description": "Information about LCM coordination actions (see clause 10 in ETSI GS NFV-SOL002) that were rejected by 503 error which means they can be tried again after a delay. See note 5.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": [
+ "coordinationActionName",
+ "rejectionTime",
+ "endpointType",
+ "delay"
+ ],
+ "properties": {
+ "coordinationActionName": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "rejectionTime": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "delay": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "endpointType": {
+ "description": "The endpoint type used by this coordination action. Valid values: •\tMGMT: coordination with other operation supporting management systems (e.g. EM) •\tVNF: coordination with the VNF instance\n",
+ "type": "string",
+ "enum": ["MGMT", "VNF"]
+ }
+ }
+ }
+ },
+ "warnings": {
+ "description": "Warning messages that were generated while the operation was executing.\nIf the operation has included LCM coordination actions and these have resulted in warnings, such warnings should be added to this attribute.\n",
+ "type": "array",
+ "items": {
+ "type": "string"
+ }
+ },
+ "_links": {
+ "description": "Links to resources related to this resource.\n",
+ "type": "object",
+ "required": ["self", "vnfInstance"],
+ "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"
+ }
+ }
+ },
+ "vnfInstance": {
+ "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"
+ }
+ }
+ },
+ "grant": {
+ "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"
+ }
+ }
+ },
+ "cancel": {
+ "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"
+ }
+ }
+ },
+ "retry": {
+ "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"
+ }
+ }
+ },
+ "rollback": {
+ "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"
+ }
+ }
+ },
+ "fail": {
+ "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"
+ }
+ }
+ },
+ "vnfSnapshot": {
+ "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"
+ }
+ }
+ }
+ }
+ }
+ }
+}
diff --git a/SOL003/VNFLifecycleManagement-API/schemas/VnfLcmOpOccs.schema.json b/SOL003/VNFLifecycleManagement-API/schemas/VnfLcmOpOccs.schema.json
index 3cd4bfc886b9cf69034c82040737b271b47b50ec..72866792b6ff21e725b212f808b025d2b4571eab 100644
--- a/SOL003/VNFLifecycleManagement-API/schemas/VnfLcmOpOccs.schema.json
+++ b/SOL003/VNFLifecycleManagement-API/schemas/VnfLcmOpOccs.schema.json
@@ -1,1028 +1,1267 @@
{
- "type":"array",
- "items": {
- "description": "This type represents a VNF lifecycle management operation occurrence. It shall comply with the provisions defined in table 5.5.2.13-1.\nNOTE 1:\tThis allows the NFVO to obtain the information contained in the latest \n \"result\" notification if it has not received it due to an error or a \n wrongly configured subscription filter.\nNOTE 2:\tNot more than one of changedInfo and modificationsTriggeredByVnfPkgChange \n shall be present.\nNOTE 3:\tFor a particular affected VL, there shall be as many \"AffectedVirtualLink\" \n entries as needed for signalling the different types of changes, i.e. one \n per virtual link and change type. For instance, in the case of signaling \n affected VL instances involving the addition of a particular VL instance \n with links ports, one \"AffectedVirtualLink\" entry signals the addition of \n the VL by using the \"changeType\" attribute of \"AffectedVirtualLink\" structure \n equal to \"ADDED\", and another \"AffectedVirtualLink\" entry signals the addition \n of externally visible VNF link ports of the VL by using the \"changeType\" equal \n to \"LINK_PORT_ADDED\".\nNOTE 4:\tA coordination action has timed out if the VNFM has not been able to read the \n \"Individual coordination action\" resource within a timeout interval after requesting \n the coordination to be started or to be cancelled. The length of the timeout interval \n is defined by means outside the scope of the present document.\nNOTE 5: The list of rejected coordinations may be garbage collected if the LCM operation\n occurrence has reached a terminal state, i.e. one of \"COMPLETED\", \"FAILED\" and \"ROLLED_BACK\".\n",
- "type": "object",
- "oneOf": [
- {
- "required": ["changedInfo"]
- },
- {
- "required": ["modificationsTriggeredByVnfPkgChange"]
- }
- ],
- "required": [
- "id",
- "operationState",
- "stateEnteredTime",
- "startTime",
- "vnfInstanceId",
- "operation",
- "isAutomaticInvocation",
- "isCancelPending"
- ],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "operationState": {
- "description": "STARTING: The LCM operation is starting. PROCESSING: The LCM operation is currently in execution. COMPLETED: The LCM operation has been completed successfully. FAILED_TEMP: The LCM operation has failed and execution has stopped, but the execution of the operation is not considered to be closed. FAILED: The LCM operation has failed and it cannot be retried or rolled back, as it is determined that such action won't succeed. ROLLING_BACK: The LCM operation is currently being rolled back. ROLLED_BACK: The LCM operation has been successfully rolled back, i.e. The state of the VNF prior to the original operation invocation has been restored as closely as possible.\n",
- "type": "string",
- "enum": [
- "STARTING",
- "PROCESSING",
- "COMPLETED",
- "FAILED_TEMP",
- "FAILED",
- "ROLLING_BACK",
- "ROLLED_BACK"
- ]
- },
- "stateEnteredTime": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "startTime": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "vnfInstanceId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "grantId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "operation": {
- "description": "The enumeration LcmOpType defines the permitted values to represent VNF lifecycle operation types in VNF lifecycle management operation occurrence resources and VNF lifecycle management operation occurrence notifications. It shall comply with the provisions defined in table 5.5.4.5-1.\nValue | Description ------|------------ INSTANTIATE | Represents the \"Instantiate VNF\" LCM operation. SCALE | Represents the \"Scale VNF\" LCM operation. SCALE_TO_LEVEL | Represents the \"Scale VNF to Level\" LCM operation. CHANGE_FLAVOUR | Represents the \"Change VNF Flavour\" LCM operation. TERMINATE | Represents the \"Terminate VNF\" LCM operation. HEAL | Represents the \"Heal VNF\" LCM operation. OPERATE | Represents the \"Operate VNF\" LCM operation. CHANGE_EXT_CONN | Represents the \"Change external VNF connectivity\" LCM operation. MODIFY_INFO | Represents the \"Modify VNF Information\" LCM operation. CREATE_SNAPSHOT | Represents the \"Create VNF Snapshot\" LCM operation. REVERT_TO_SNAPSHOT | Represents the ΓÇ£Revert-To VNF Snapshot\" LCM operation. CHANGE_VNFPKG | Represents the \"Change current VNF package\" LCM operation.\n",
- "type": "string",
- "enum": [
- "INSTANTIATE",
- "SCALE",
- "SCALE_TO_LEVEL",
- "CHANGE_FLAVOUR",
- "TERMINATE",
- "HEAL",
- "OPERATE",
- "CHANGE_EXT_CONN",
- "MODIFY_INFO",
- "CREATE_SNAPSHOT",
- "REVERT_TO_SNAPSHOT",
- "CHANGE_VNFPKG"
- ]
- },
- "isAutomaticInvocation": {
- "description": "The Boolean is a data type having two values (true and false).\n",
- "type": "boolean"
- },
- "operationParams": {
- "description": "Input parameters of the LCM operation. This attribute shall be formatted according to the request data type of the related LCM operation. In addition, the provisions in clause 5.7 shall apply. \nThe following mapping between operationType and the data type of this attribute shall apply: * INSTANTIATE: InstantiateVnfRequest * SCALE: ScaleVnfRequest * SCALE_TO_LEVEL: ScaleVnfToLevelRequest * CHANGE_FLAVOUR: ChangeVnfFlavourRequest * OPERATE: OperateVnfRequest * HEAL: HealVnfRequest * CHANGE_EXT_CONN: ChangeExtVnfConnectivityRequest * TERMINATE: TerminateVnfRequest * MODIFY_INFO: VnfInfoModifications * CREATE_SNAPSHOT: CreateVnfSnapshotRequest * REVERT_TO_SNAPSHOT: RevertToVnfSnapshotRequest * CHANGE_VNFPKG: ChangeCurrentVnfPkgRequest\n",
- "type": "object"
- },
- "isCancelPending": {
- "description": "The Boolean is a data type having two values (true and false).\n",
- "type": "boolean"
- },
- "cancelMode": {
- "description": "Cancellation mode. GRACEFUL: If the VNF LCM operation occurrence is in \"PROCESSING\" or \"ROLLING_BACK\" state, the VNFM shall not start any new resource management operation and shall wait for the ongoing resource management operations in the underlying system, typically the VIM, to finish execution or to time out. After that, the VNFM shall put the operation occurrence into the FAILED_TEMP state. If the VNF LCM operation occurrence is in \"STARTING\" state, the VNFM shall not start any resource management operation and shall wait for the granting request to finish execution or time out. After that, the VNFM shall put the operation occurrence into the ROLLED_BACK state. FORCEFUL: If the VNF LCM operation occurrence is in \"PROCESSING\" or \"ROLLING_BACK\" state, the VNFM shall not start any new resource management operation, shall cancel the ongoing resource management operations in the underlying system, typically the VIM, and shall wait for the cancellation to finish or to time out. After that, the VNFM shall put the operation occurrence into the FAILED_TEMP state. If the VNF LCM operation occurrence is in \"STARTING\" state, the VNFM shall not start any resource management operation and put the operation occurrence into the ROLLED_BACK state.\n",
- "type": "string",
- "enum": ["GRACEFUL", "FORCEFUL"]
- },
- "error": {
- "description": "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 is reproduced inthis structure. Compared to the general framework defined in IETF RFC 7807, 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 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.\n",
- "type": "object",
- "required": ["status", "detail"],
- "properties": {
- "type": {
- "description": "A URI reference according to IETF RFC 3986 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"
- }
- }
- },
- "resourceChanges": {
- "description": "This attribute contains information about the cumulative changes to virtualised resources that were performed so far by the LCM operation since its start, if applicable.\n",
- "type": "object",
- "properties": {
- "affectedVnfcs": {
- "description": "Information about VNFC 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 VNFCs. It shall comply with the provisions in table 5.5.3.13-1.\nNOTE:\tThe \"resourceDefinitionId\" attribute provides information to the API consumer \n (i.e. the NFVO) to assist in correlating the resource changes performed during \n the LCM operation with the granted resources in a specific Grant exchange, which \n is identified by the \"grantId\" available in the \"Individual VNF lifecycle management \n operation occurrence\" and the \"id\" in the \"Individual Grant\".\n",
- "type": "object",
- "required": ["id", "vduId", "changeType", "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"
- },
- "vduId": {
- "description": "An identifier that is unique within a VNF descriptor.\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: * ADDED * REMOVED * MODIFIED * TEMPORARY For a temporary resource, an AffectedVnfc structure exists as long as the temporary resource exists.\n",
- "type": "string",
- "enum": ["ADDED", "REMOVED", "MODIFIED", "TEMPORARY"]
- },
- "computeResource": {
- "required": ["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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
- "type": "string"
- }
- }
- },
- "resourceDefinitionId": {
- "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\n",
- "type": "string"
- },
- "zoneId": {
- "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 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"
- },
- "affectedVnfcCpIds": {
- "description": "Identifiers of CP(s) of the VNFC instance that were affected by the change. Shall be present for those affected CPs of the VNFC instance that are associated to an external CP of the VNF instance. May be present for further affected CPs of the VNFC instance.\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"
- }
- },
- "addedStorageResourceIds": {
- "description": "References to VirtualStorage resources that have been added. Each value refers to a VirtualStorageResourceInfo item in the VnfInstance that was added to the VNFC. It shall be provided if at least one storage resource was added to the VNFC.\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"
- }
- },
- "removedStorageResourceIds": {
- "description": "References to VirtualStorage resources that have been removed. The value contains the identifier of a VirtualStorageResourceInfo item that has been removed from the VNFC, and might no longer exist in the VnfInstance. It shall be provided if at least one storage resource was removed from the VNFC.\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"
- }
- }
- }
- }
- },
- "affectedVirtualLinks": {
- "description": "Information about VL instances that were affected during the lifecycle operation. See notes 1 and 3.\n",
- "type": "array",
- "items": {
- "description": "This type provides information about added, deleted, modified and temporary VLs, and added or removed VNF link ports.\nNOTE 1:\tWhen signalling the addition (LINK_PORT_ADDED) or removal (LINK_PORT_REMOVED) of VNF link ports, \n the \"networkResource\" and \"resourceDefinitionId\" attributes refer to the affected virtual link \n instance, not the link port instance. The resource handles of the affected VNF link ports can be \n found by dereferencing the identifiers in the \"vnfLinkPortIds\" attribute.\nNOTE 2:\tThe \"resourceDefinitionId\" attribute provides information to the API consumer (i.e. the NFVO) to \n assist in correlating the resource changes performed during the LCM operation with the granted \n resources in a specific Grant exchange, which is identified by the \"grantId\" available in the \n \"Individual VNF lifecycle management operation occurrence\" and the \"id\" in the \"Individual Grant\".\n",
- "type": "object",
- "required": [
- "id",
- "vnfVirtualLinkDescId",
- "changeType",
- "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"
- },
- "vnfVirtualLinkDescId": {
- "description": "An identifier that is unique within a VNF descriptor.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "changeType": {
- "description": "Signals the type of change.\nPermitted values: -\tADDED -\tREMOVED -\tMODIFIED -\tTEMPORARY -\tLINK_PORT_ADDED -\tLINK_PORT_REMOVED For a temporary resource, an AffectedVirtualLink structure exists as long as the temporary resource exists. See note 1.\n",
- "type": "string",
- "enum": [
- "ADDED",
- "REMOVED",
- "MODIFIED",
- "TEMPORARY",
- "LINK_PORT_ADDED",
- "LINK_PORT_REMOVED"
- ]
- },
- "networkResource": {
- "required": ["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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
- "type": "string"
- }
- }
- },
- "vnfLinkPortIds": {
- "description": "Identifiers of the link ports of the affected VL related to the change. Each identifier references a \"VnfLinkPortInfo\" structure.\nShall be set when changeType is equal to \"LINK_PORT_ADDED\" or \"LINK_PORT_REMOVED\", and the related \"VnfLinkPortInfo\" structures are present (case \"added\") or have been present (case \"removed\") in the \"VnfVirtualLinkResourceInfo\" or \"ExtManagedVirtualLinkInfo\" structures that are represented by the \"vnfVirtualLinkResource¬Info\" or \"extManagedVirtualLinkInfo\" attribute in the \"VnfInstance\" structure. See note 1.\n",
- "type": "array",
- "items": {
- "description": "An identifier that is unique within a VNF descriptor.\n",
- "type": "string"
- }
- },
- "resourceDefinitionId": {
- "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\n",
- "type": "string"
- },
- "zoneId": {
- "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 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"
- }
- }
- }
- },
- "affectedExtLinkPorts": {
- "description": "Information about external VNF link ports that were affected during the lifecycle operation. See note 1.\n",
- "type": "array",
- "items": {
- "description": "This type provides information about added and deleted external link ports (link ports attached to external virtual links). It shall comply with the provisions in table 5.5.3.14a-1.\nNOTE:\tThe \"resourceDefinitionId\" attribute provides information to the API consumer (i.e. the NFVO) to assist in correlating \n the resource changes performed during the LCM operation with the granted resources in a specific Grant exchange, which \n is identified by the \"grantId\" available in the \"Individual VNF lifecycle management operation occurrence\" and the \"id\" \n in the \"Individual Grant\".\n",
- "type": "object",
- "required": [
- "id",
- "changeType",
- "extCpInstanceId",
- "resourceHandle"
- ],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "changeType": {
- "description": "Signals the type of change. Permitted values: -\tADDED - MODIFIED -\tREMOVED\n",
- "type": "string",
- "enum": ["ADDED", "REMOVED"]
- },
- "extCpInstanceId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "resourceHandle": {
- "required": ["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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
- "type": "string"
- }
- }
- },
- "resourceDefinitionId": {
- "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- }
- },
- "affectedVirtualStorages": {
- "description": "Information about virtualised storage 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 virtual storage resources. It shall comply with the provisions in table 5.5.3.15-1.\nNOTE:\tThe \"resourceDefinitionId\" attribute provides information to the API consumer (i.e. the NFVO) to \n assist in correlating the resource changes performed during the LCM operation with the granted \n resources in a specific Grant exchange, which is identified by the \"grantId\" available in the \n \"Individual VNF lifecycle management operation occurrence\" and the \"id\" in the \"Individual Grant\".\n",
- "type": "object",
- "required": [
- "id",
- "virtualStorageDescId",
- "changeType",
- "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": "An identifier that is unique within a VNF descriptor.\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: * ADDED * REMOVED * MODIFIED * TEMPORARY For a temporary resource, an AffectedVirtualStorage structure exists as long as the temporary resource exists.\n",
- "type": "string",
- "enum": ["ADDED", "REMOVED", "MODIFIED", "TEMPORARY"]
- },
- "storageResource": {
- "required": ["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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
- "type": "string"
- }
- }
- },
- "resourceDefinitionId": {
- "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\n",
- "type": "string"
- },
- "zoneId": {
- "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 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"
- }
- }
- }
- }
- }
- },
- "changedInfo": {
- "description": "This type represents attribute modifications that were performed on an \"Individual VNF instance\" resource. The attributes that can be included consist of those requested to be modified explicitly in the \"VnfInfoModificationRequest\" data structure, and additional attributes of the \"VnfInstance\" data structure that were modified implicitly e.g. when modifying the referenced VNF package. The \"VnfInfoModifications\" data type shall comply with the provisions defined in table 5.5.2.12a-1.\nNOTE:\tIf present, this attribute (which depends on the value of the \"vnfdId\" attribute) \n was modified implicitly following a request to modify the \"vnfdId\" attribute, by \n copying the value of this attribute from the VNFD in the VNF Package identified by \n the \"vnfdId\" attribute.\n",
- "type": "object",
- "properties": {
- "vnfInstanceName": {
- "description": "A string defined in IETF RFC 8259.\n",
- "type": "string"
- },
- "vnfInstanceDescription": {
- "description": "A string defined in IETF RFC 8259.\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 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"
- },
- "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 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"
- },
- "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 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"
- },
- "vimConnectionInfo": {
- "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 for managing the resources of a VNF instance. * 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 is provided through a secure connection over\n HTTP Secure (HTTP over SSL/TLS), and the connection might also be established through a VPN\n (for example TLS-based VPN tunnelling) for site-to-site connection, the \"accessInfo\" JSON data\n structure, and the sensitive data related information (\"username\"/\"password\" as required properties\n for authentication purpose), will be transmitted as plain text through a TLS tunnel without additional\n encoding/encryption before transmitting it, making the sensitive data visible to the endpoint.\n The base64 encoded certificates are only used by the VNFM to verify the authenticity of the\n interface endpoint of the VIM.\n",
- "type": "object",
- "required": ["vimType"],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vimType": {
- "description": "Discriminator for the different types of the VIM information. The value of this attribute determines the structure of the \"interfaceInfo\" and \"accessInfo\" attributes, based on the type of the VIM. The set of permitted values is expected to change over time as new types or versions of VIMs become available. The ETSI NFV registry of VIM-related information provides access to information about VimConnectionInfo definitions for various VIM types. The structure of the registry is defined in Annex C of SOL003.\n",
- "type": "string"
- },
- "interfaceInfo": {
- "description": "This 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"
- },
- "accessInfo": {
- "description": "This 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"
- },
- "extra": {
- "description": "This 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"
- }
- }
- }
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfProvider": {
- "description": "A string defined in IETF RFC 8259.\n",
- "type": "string"
- },
- "vnfProductName": {
- "description": "A string defined in IETF RFC 8259.\n",
- "type": "string"
- },
- "vnfSoftwareVersion": {
- "description": "A version.\n",
- "type": "string"
- },
- "vnfdVersion": {
- "description": "A version.\n",
- "type": "string"
- }
- }
- },
- "affectedVipCps": {
- "description": "Information about virtual IP CP instances that were affected during the execution of the lifecycle management operation.\n",
- "type": "array",
- "items": {
- "description": "This type provides information about added, deleted and modified virtual IP CP instances.\n",
- "type": "object",
- "required": ["cpInstanceId", "cpdId", "changeType"],
- "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": "An identifier that is unique within a VNF descriptor.\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: -\tADDED -\tREMOVED -\tMODIFIED\n",
- "type": "string",
- "enum": ["ADDED", "REMOVED", "MODIFIED"]
- }
- }
- }
- },
- "changedExtConnectivity": {
- "description": "Information about changed external connectivity, if applicable. See note 1.\n",
- "type": "array",
- "items": {
- "description": "This type represents information about an external VL. It shall comply with the provisions defined in table 5.5.3.2-1.\nNOTE:\tThis attribute reflects the current configuration information that has resulted from merging into this attribute \n the \"VnfExtCpData\" information which was passed as part of the \"ExtVirtualLinkData\" structure in the input of the \n most recent VNF LCM operation such as \"InstantiateVnfRequest\", \"ChangeExtVnfConnectivityRequest\", \"ChangeVnfFlavourRequest\" \n or \"ChangeCurrentVnfPkgRequest\", or in the Grant response. If applying such change results in an empty list of \n \"currentVnfExtCpData\" structure instances, the affected instance of \"ExtVirtualLinkInfo\" shall be removed from its \n parent data structure.\n",
- "type": "object",
- "required": ["id", "resourceHandle", "currentVnfExtCpData"],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceHandle": {
- "required": ["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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\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. It shall comply with the provisions defined in table 5.5.3.9-1.\nNOTE 1:\tThe use cases UC#4 and UC#5 in clause A.4 of ETSI GS NFV-IFA 007 provide examples for such a configuration. NOTE 2:\tThe 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": {
- "required": ["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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\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.\n",
- "type": "string"
- }
- }
- }
- },
- "currentVnfExtCpData": {
- "description": "Allows the API consumer to read the current CP configuration information for the connection of external CPs to the external virtual link. See note.\n",
- "type": "array",
- "items": {
- "description": "This type represents configuration information for external CPs created. * NOTE 1: \tIn case this identifier refers to a CPD with trunking enabled, the external CP instances created\n from this CPD will represent ports in a trunk.\n* NOTE 2: \tWithin one VNF instance, all VNFC instances created from a particular VDU have the same external\n connectivity. Thus, given a particular value of the \"cpdId\" attribute, there shall be one\n \"cpConfig\" entry for each VNFC instance that has been or can be created from a VDU which includes\n a CPD identified by the \"cpdId\" attribute. If the cpConfig represents a subport in a trunk,\n all \"cpConfig\" entries in this list shall have the same segmentationId, which means they are\n connected to the same set of external VLs via the trunk.\n* NOTE 3: \tThe map entry value shall be set to \"null\" in order to delete a \"VnfExtCpConfig\" entry identified\n by a particular key value from the map, i.e. for the disconnection of an existing external\n CP instance addressed by cpInstanceId in the deleted map entry from a particular external\n virtual link, and deletion of that instance in case it represents a subport. Deleting the\n last key from the map removes the affected instance of the \"VnfExtCpData\" structure from\n its parent data structure.\n* NOTE 4: If, as defined by the input parameters of a \"ChangeVnfFlavour\", \"ChangeExtVnfConnectivity\" or \n \"ChangeCurrentVnfPkg\" operation or as part of the Grant response for any of these operations, a \n cpConfig map entry identified by a particular map key value is moved into another \"ExtVirtualLinkData\"\n or \"VnfExtCpData\" structure, this particular cpConfig map entry may be used by an external CP instance\n different than the one that has used it before the operation, or by no external CP instance at all.\n Renaming a CPD identifier during the \"changeCurrentVnfPkg\" operation does not count as moving the\n related \"cpConfig\" map entries to a new \"extCpData\" structure.\n",
- "type": "object",
- "required": ["cpdId"],
- "properties": {
- "cpdId": {
- "description": "An identifier that is unique within a VNF descriptor.\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). See notes 2, 3 and 4.\n",
- "type": "object",
- "additionalProperties": {
- "description": "This type represents an externally provided link port or network address information per instance of an external connection point. In case a link port is provided, the VNFM shall use that link port when connecting the external CP to the external VL. In a link port is not provided, the VNFM shall create a link port on the external VL, and use that link port to connect the external CP to the external VL. * NOTE: The following conditions apply to the attributes \"linkPortId\" and \"cpProtocolData\":\n 1) Void.\n 2) At least one of the \"linkPortId\" and \"cpProtocolData\" attributes shall be present for an external\n CP instance representing a subport that is to be created, or an external CP instance that is to be\n created by creating the corresponding VNFC or VNF instance during the current or a subsequent LCM\n operation, or for an existing external CP instance that is to be re-configured or added to a\n 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\n a pre created link port, and the VNFM can use means outside the scope of the present document to obtain\n the pre-configured address information for the connection point from the resource representing\n the link port.\n 5) If both \"cpProtocolData\" and \"linkportId\" are provided, the API consumer shall ensure that the\n cpProtocolData can be used with the pre-created link port referenced by \"linkPortId\".\n",
- "anyOf": [
- {
- "required": ["linkPortId"]
- },
- {
- "required": ["cpProtocolData"]
- }
- ],
- "type": "object",
- "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 to the VNFM the need to create a dedicated link port for the external CP. If set to True, the VNFM shall create a link port. If set to False, the VNFM shall not create a link port. 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 note.\n",
- "type": "array",
- "items": {
- "description": "This type represents network protocol data. * NOTE:\tThis attribute allows to signal the addition of further types of layer and protocol\n in future versions of the present document in a backwards-compatible way. In the current\n 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). See note.\n",
- "type": "string",
- "enum": ["IP_OVER_ETHERNET"]
- },
- "ipOverEthernet": {
- "description": "This type represents network address data for IP over Ethernet. * NOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. * NOTE 2:\tExactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present. * NOTE 3:\tIf the CP instance represents a subport in a trunk, segmentationId shall be present.\n Otherwise it shall not be present.\n* NOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the actual\n network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header\n of the packets or it may be an identifier used between the application and the NFVI networking\n infrastructure to identify the network sub-interface of the trunk port in question. In the latter\n case the NFVI infrastructure will map this local segmentationId to whatever segmentationId is\n actually used by the NFVIΓÇÖs transport technology.\n",
- "type": "object",
- "anyOf": [
- {
- "required": ["macAddress"]
- },
- {
- "required": ["ipAddresses"]
- }
- ],
- "oneOf": [
- {
- "required": ["fixedAddresses"]
- },
- {
- "required": ["numDynamicAddresses"]
- },
- {
- "required": ["ipAddressRange"]
- }
- ],
- "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: -\tVLAN: the subport uses VLAN as encapsulation type. -\tINHERIT: the subport gets its segmentation type from the network itΓÇÖs 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"],
- "properties": {
- "type": {
- "description": "The type of the IP addresses. Permitted values: IPV4, IPV6.\n",
- "type": "string",
- "enum": ["IPV4", "IPV6"]
- },
- "fixedAddresses": {
- "description": "Fixed addresses to assign (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"
- }
- },
- "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. 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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- },
- "modificationsTriggeredByVnfPkgChange": {
- "description": "This type represents attribute modifications that were performed on an \"Individual VNF instance\" resource when changing the current VNF package. The attributes that can be included consist of those requested to be modified explicitly in the \"ChangeCurrentVnfPkgRequest\" data structure, and additional attributes of the \"VnfInstance\" data structure that were modified implicitly during the operation. The \"ModificationsTriggeredByVnfPkgChange\" data type shall comply with the provisions defined in table 5.5.3.21-1.\nNOTE 1:\tThis attribute represents the delta (semantics as per IETF RFC 7396, JSON Merge Patch) between the value \n of the attribute at the start of the \"Change current VNF package\" operation and the value of the attribute \n at its completion.\nNOTE 2:\tIf present, this attribute (which depends on the value of the \"vnfdId\" attribute) was modified implicitly \n during the related operation and contains a copy of the value of the related attribute from the VNFD in the \n VNF Package identified by the \"vnfdId\" attribute.\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 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"
- },
- "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 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"
- },
- "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 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"
- },
- "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\". See note 2.\n",
- "type": "string"
- },
- "vnfProductName": {
- "description": "If present, this attribute signals the new value of the \"vnfProductName\" attribute in \"VnfInstance\". See note 2.\n",
- "type": "string"
- },
- "vnfSoftwareVersion": {
- "description": "A version.\n",
- "type": "string"
- },
- "vnfdVersion": {
- "description": "A version.\n",
- "type": "string"
- },
- "vimConnectionInfo": {
- "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 for managing the resources of a VNF instance. * 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 is provided through a secure connection over\n HTTP Secure (HTTP over SSL/TLS), and the connection might also be established through a VPN\n (for example TLS-based VPN tunnelling) for site-to-site connection, the \"accessInfo\" JSON data\n structure, and the sensitive data related information (\"username\"/\"password\" as required properties\n for authentication purpose), will be transmitted as plain text through a TLS tunnel without additional\n encoding/encryption before transmitting it, making the sensitive data visible to the endpoint.\n The base64 encoded certificates are only used by the VNFM to verify the authenticity of the\n interface endpoint of the VIM.\n",
- "type": "object",
- "required": ["vimType"],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vimType": {
- "description": "Discriminator for the different types of the VIM information. The value of this attribute determines the structure of the \"interfaceInfo\" and \"accessInfo\" attributes, based on the type of the VIM. The set of permitted values is expected to change over time as new types or versions of VIMs become available. The ETSI NFV registry of VIM-related information provides access to information about VimConnectionInfo definitions for various VIM types. The structure of the registry is defined in Annex C of SOL003.\n",
- "type": "string"
- },
- "interfaceInfo": {
- "description": "This 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"
- },
- "accessInfo": {
- "description": "This 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"
- },
- "extra": {
- "description": "This 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"
- }
- }
- }
- }
- }
- },
- "vnfSnapshotInfoId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "lcmCoordinations": {
- "description": "Information about LCM coordination actions (see clause 10 in ETSI GS NFV-SOL002) related to this LCM operation occurrence.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": [
- "id",
- "coordinationActionName",
- "startTime",
- "endpointType"
- ],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "coordinationActionName": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "coordinationResult": {
- "description": "The enumeration LcmCoordResultType defines the permitted values to represent the result of executing an LCM coordination action. The coordination result also implies the action to be performed by the VNFM as the follow-up to this coordination. Value | Description ------|------------ CONTINUE | The related LCM operation shall be continued, staying in the state \"PROCESSING\". ABORT | The related LCM operation shall be aborted by transitioning into the state \"FAILED_TEMP\". CANCELLED | The coordination action has been cancelled upon request of the API consumer, i.e. the VNFM. The related LCM operation shall be aborted by transitioning into the state \"FAILED_TEMP\".\n",
- "type": "string",
- "enum": ["CONTINUE", "ABORT", "CANCELLED"]
- },
- "startTime": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "endTime": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "delay": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "endpointType": {
- "description": "The endpoint type used by this coordination action. Valid values: ΓÇó\tMGMT: coordination with other operation supporting management systems (e.g. EM) ΓÇó\tVNF: coordination with the VNF instance\n",
- "type": "string",
- "enum": ["MGMT", "VNF"]
- }
- }
- }
- },
- "rejectedLcmCoordinations": {
- "description": "Information about LCM coordination actions (see clause 10 in ETSI GS NFV-SOL002) that were rejected by 503 error which means they can be tried again after a delay. See note 5.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": [
- "coordinationActionName",
- "rejectionTime",
- "endpointType",
- "delay"
- ],
- "properties": {
- "coordinationActionName": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "rejectionTime": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "delay": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "endpointType": {
- "description": "The endpoint type used by this coordination action. Valid values: ΓÇó\tMGMT: coordination with other operation supporting management systems (e.g. EM) ΓÇó\tVNF: coordination with the VNF instance\n",
- "type": "string",
- "enum": ["MGMT", "VNF"]
- }
- }
- }
- },
- "warnings": {
- "description": "Warning messages that were generated while the operation was executing.\nIf the operation has included LCM coordination actions and these have resulted in warnings, such warnings should be added to this attribute.\n",
- "type": "array",
- "items": {
- "type": "string"
- }
- },
- "_links": {
- "description": "Links to resources related to this resource.\n",
- "type": "object",
- "required": ["self", "vnfInstance"],
- "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"
- }
- }
- },
- "vnfInstance": {
- "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"
- }
- }
- },
- "grant": {
- "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"
- }
- }
- },
- "cancel": {
- "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"
- }
- }
- },
- "retry": {
- "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"
- }
- }
- },
- "rollback": {
- "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"
- }
- }
- },
- "fail": {
- "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"
- }
- }
- },
- "vnfSnapshot": {
- "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"
- }
- }
- }
- }
- }
- }
- }
+ "type": "array",
+ "items": {
+ "description": "This type represents a VNF lifecycle management operation occurrence.\nNOTE 1:\tThis allows the NFVO to obtain the information contained in the latest \n \"result\" notification if it has not received it due to an error or a \n wrongly configured subscription filter.\nNOTE 2:\tNot more than one of changedInfo and modificationsTriggeredByVnfPkgChange \n shall be present.\nNOTE 3:\tFor a particular affected VL, there shall be as many \"AffectedVirtualLink\" \n entries as needed for signalling the different types of changes, i.e. one \n per virtual link and change type. For instance, in the case of signaling \n affected VL instances involving the addition of a particular VL instance \n with links ports, one \"AffectedVirtualLink\" entry signals the addition of \n the VL by using the \"changeType\" attribute of \"AffectedVirtualLink\" structure \n equal to \"ADDED\", and another \"AffectedVirtualLink\" entry signals the addition \n of externally visible VNF link ports of the VL by using the \"changeType\" equal \n to \"LINK_PORT_ADDED\".\nNOTE 4:\tA coordination action has timed out if the VNFM has not been able to read the \n \"Individual coordination action\" resource within a timeout interval after requesting \n the coordination to be started or to be cancelled. The length of the timeout interval \n is defined by means outside the scope of the present document.\nNOTE 5: The list of rejected coordinations may be garbage collected if the LCM operation\n occurrence has reached a terminal state, i.e. one of \"COMPLETED\", \"FAILED\" and \"ROLLED_BACK\".\n",
+ "type": "object",
+ "oneOf": [
+ {
+ "required": ["changedInfo"]
+ },
+ {
+ "required": ["modificationsTriggeredByVnfPkgChange"]
+ }
+ ],
+ "required": [
+ "id",
+ "operationState",
+ "stateEnteredTime",
+ "startTime",
+ "vnfInstanceId",
+ "operation",
+ "isAutomaticInvocation",
+ "isCancelPending"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "operationState": {
+ "description": "STARTING: The LCM operation is starting. PROCESSING: The LCM operation is currently in execution. COMPLETED: The LCM operation has been completed successfully. FAILED_TEMP: The LCM operation has failed and execution has stopped, but the execution of the operation is not considered to be closed. FAILED: The LCM operation has failed and it cannot be retried or rolled back, as it is determined that such action won't succeed. ROLLING_BACK: The LCM operation is currently being rolled back. ROLLED_BACK: The LCM operation has been successfully rolled back, i.e. The state of the VNF prior to the original operation invocation has been restored as closely as possible.\n",
+ "type": "string",
+ "enum": [
+ "STARTING",
+ "PROCESSING",
+ "COMPLETED",
+ "FAILED_TEMP",
+ "FAILED",
+ "ROLLING_BACK",
+ "ROLLED_BACK"
+ ]
+ },
+ "stateEnteredTime": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "startTime": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "vnfInstanceId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "grantId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "operation": {
+ "description": "The enumeration LcmOpType defines the permitted values to represent VNF lifecycle operation types in VNF lifecycle management operation occurrence resources and VNF lifecycle management operation occurrence notifications.\nValue | Description ------|------------ INSTANTIATE | Represents the \"Instantiate VNF\" LCM operation. SCALE | Represents the \"Scale VNF\" LCM operation. SCALE_TO_LEVEL | Represents the \"Scale VNF to Level\" LCM operation. CHANGE_FLAVOUR | Represents the \"Change VNF Flavour\" LCM operation. TERMINATE | Represents the \"Terminate VNF\" LCM operation. HEAL | Represents the \"Heal VNF\" LCM operation. OPERATE | Represents the \"Operate VNF\" LCM operation. CHANGE_EXT_CONN | Represents the \"Change external VNF connectivity\" LCM operation. MODIFY_INFO | Represents the \"Modify VNF Information\" LCM operation. CREATE_SNAPSHOT | Represents the \"Create VNF Snapshot\" LCM operation. REVERT_TO_SNAPSHOT | Represents the “Revert-To VNF Snapshot\" LCM operation. CHANGE_VNFPKG | Represents the \"Change current VNF package\" LCM operation.\n",
+ "type": "string",
+ "enum": [
+ "INSTANTIATE",
+ "SCALE",
+ "SCALE_TO_LEVEL",
+ "CHANGE_FLAVOUR",
+ "TERMINATE",
+ "HEAL",
+ "OPERATE",
+ "CHANGE_EXT_CONN",
+ "MODIFY_INFO",
+ "CREATE_SNAPSHOT",
+ "REVERT_TO_SNAPSHOT",
+ "CHANGE_VNFPKG"
+ ]
+ },
+ "isAutomaticInvocation": {
+ "description": "The Boolean is a data type having two values (true and false).\n",
+ "type": "boolean"
+ },
+ "operationParams": {
+ "description": "Input parameters of the LCM operation. This attribute shall be formatted according to the request data type of the related LCM operation. In addition, the provisions in clause 5.7 shall apply. \nThe following mapping between operationType and the data type of this attribute shall apply: * INSTANTIATE: InstantiateVnfRequest * SCALE: ScaleVnfRequest * SCALE_TO_LEVEL: ScaleVnfToLevelRequest * CHANGE_FLAVOUR: ChangeVnfFlavourRequest * OPERATE: OperateVnfRequest * HEAL: HealVnfRequest * CHANGE_EXT_CONN: ChangeExtVnfConnectivityRequest * TERMINATE: TerminateVnfRequest * MODIFY_INFO: VnfInfoModifications * CREATE_SNAPSHOT: CreateVnfSnapshotRequest * REVERT_TO_SNAPSHOT: RevertToVnfSnapshotRequest * CHANGE_VNFPKG: ChangeCurrentVnfPkgRequest\n",
+ "type": "object"
+ },
+ "isCancelPending": {
+ "description": "The Boolean is a data type having two values (true and false).\n",
+ "type": "boolean"
+ },
+ "cancelMode": {
+ "description": "Cancellation mode. GRACEFUL: If the VNF LCM operation occurrence is in \"PROCESSING\" or \"ROLLING_BACK\" state, the VNFM shall not start any new resource management operation and shall wait for the ongoing resource management operations in the underlying system, typically the VIM, to finish execution or to time out. After that, the VNFM shall put the operation occurrence into the FAILED_TEMP state. If the VNF LCM operation occurrence is in \"STARTING\" state, the VNFM shall not start any resource management operation and shall wait for the granting request to finish execution or time out. After that, the VNFM shall put the operation occurrence into the ROLLED_BACK state. FORCEFUL: If the VNF LCM operation occurrence is in \"PROCESSING\" or \"ROLLING_BACK\" state, the VNFM shall not start any new resource management operation, shall cancel the ongoing resource management operations in the underlying system, typically the VIM, and shall wait for the cancellation to finish or to time out. After that, the VNFM shall put the operation occurrence into the FAILED_TEMP state. If the VNF LCM operation occurrence is in \"STARTING\" state, the VNFM shall not start any resource management operation and put the operation occurrence into the ROLLED_BACK state.\n",
+ "type": "string",
+ "enum": ["GRACEFUL", "FORCEFUL"]
+ },
+ "error": {
+ "description": "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 is reproduced inthis structure. Compared to the general framework defined in IETF RFC 7807, 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 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.\n",
+ "type": "object",
+ "required": ["status", "detail"],
+ "properties": {
+ "type": {
+ "description": "A URI reference according to IETF RFC 3986 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"
+ }
+ }
+ },
+ "resourceChanges": {
+ "description": "This attribute contains information about the cumulative changes to virtualised resources that were performed so far by the LCM operation since its start, if applicable.\n",
+ "type": "object",
+ "properties": {
+ "affectedVnfcs": {
+ "description": "Information about VNFC 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 VNFCs.\nNOTE:\tThe \"resourceDefinitionId\" attribute provides information to the API consumer \n (i.e. the NFVO) to assist in correlating the resource changes performed during \n the LCM operation with the granted resources in a specific Grant exchange, which \n is identified by the \"grantId\" available in the \"Individual VNF lifecycle management \n operation occurrence\" and the \"id\" in the \"Individual Grant\".\n",
+ "type": "object",
+ "required": ["id", "vduId", "changeType", "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"
+ },
+ "vduId": {
+ "description": "An identifier that is unique within a VNF descriptor.\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: * ADDED * REMOVED * MODIFIED * TEMPORARY For a temporary resource, an AffectedVnfc structure exists as long as the temporary resource exists.\n",
+ "type": "string",
+ "enum": ["ADDED", "REMOVED", "MODIFIED", "TEMPORARY"]
+ },
+ "computeResource": {
+ "required": ["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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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"
+ }
+ }
+ },
+ "resourceDefinitionId": {
+ "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "zoneId": {
+ "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 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"
+ },
+ "affectedVnfcCpIds": {
+ "description": "Identifiers of CP(s) of the VNFC instance that were affected by the change. Shall be present for those affected CPs of the VNFC instance that are associated to an external CP of the VNF instance. May be present for further affected CPs of the VNFC instance.\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"
+ }
+ },
+ "addedStorageResourceIds": {
+ "description": "References to VirtualStorage resources that have been added. Each value refers to a VirtualStorageResourceInfo item in the VnfInstance that was added to the VNFC. It shall be provided if at least one storage resource was added to the VNFC.\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"
+ }
+ },
+ "removedStorageResourceIds": {
+ "description": "References to VirtualStorage resources that have been removed. The value contains the identifier of a VirtualStorageResourceInfo item that has been removed from the VNFC, and might no longer exist in the VnfInstance. It shall be provided if at least one storage resource was removed from the VNFC.\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"
+ }
+ }
+ }
+ }
+ },
+ "affectedVirtualLinks": {
+ "description": "Information about VL instances that were affected during the lifecycle operation. See notes 1 and 3.\n",
+ "type": "array",
+ "items": {
+ "description": "This type provides information about added, deleted, modified and temporary VLs, and added or removed VNF link ports.\nNOTE 1:\tWhen signalling the addition (LINK_PORT_ADDED) or removal (LINK_PORT_REMOVED) of VNF link ports, \n the \"networkResource\" and \"resourceDefinitionId\" attributes refer to the affected virtual link \n instance, not the link port instance. The resource handles of the affected VNF link ports can be \n found by dereferencing the identifiers in the \"vnfLinkPortIds\" attribute.\nNOTE 2:\tThe \"resourceDefinitionId\" attribute provides information to the API consumer (i.e. the NFVO) to \n assist in correlating the resource changes performed during the LCM operation with the granted \n resources in a specific Grant exchange, which is identified by the \"grantId\" available in the \n \"Individual VNF lifecycle management operation occurrence\" and the \"id\" in the \"Individual Grant\".\n",
+ "type": "object",
+ "required": [
+ "id",
+ "vnfVirtualLinkDescId",
+ "changeType",
+ "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"
+ },
+ "vnfVirtualLinkDescId": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "changeType": {
+ "description": "Signals the type of change.\nPermitted values: -\tADDED -\tREMOVED -\tMODIFIED -\tTEMPORARY -\tLINK_PORT_ADDED -\tLINK_PORT_REMOVED For a temporary resource, an AffectedVirtualLink structure exists as long as the temporary resource exists. See note 1.\n",
+ "type": "string",
+ "enum": [
+ "ADDED",
+ "REMOVED",
+ "MODIFIED",
+ "TEMPORARY",
+ "LINK_PORT_ADDED",
+ "LINK_PORT_REMOVED"
+ ]
+ },
+ "networkResource": {
+ "required": ["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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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"
+ }
+ }
+ },
+ "vnfLinkPortIds": {
+ "description": "Identifiers of the link ports of the affected VL related to the change. Each identifier references a \"VnfLinkPortInfo\" structure.\nShall be set when changeType is equal to \"LINK_PORT_ADDED\" or \"LINK_PORT_REMOVED\", and the related \"VnfLinkPortInfo\" structures are present (case \"added\") or have been present (case \"removed\") in the \"VnfVirtualLinkResourceInfo\" or \"ExtManagedVirtualLinkInfo\" structures that are represented by the \"vnfVirtualLinkResource¬Info\" or \"extManagedVirtualLinkInfo\" attribute in the \"VnfInstance\" structure. See note 1.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ }
+ },
+ "resourceDefinitionId": {
+ "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "zoneId": {
+ "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 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"
+ }
+ }
+ }
+ },
+ "affectedExtLinkPorts": {
+ "description": "Information about external VNF link ports that were affected during the lifecycle operation. See note 1.\n",
+ "type": "array",
+ "items": {
+ "description": "This type provides information about added and deleted external link ports (link ports attached to external virtual links).\nNOTE:\tThe \"resourceDefinitionId\" attribute provides information to the API consumer (i.e. the NFVO) to assist in correlating \n the resource changes performed during the LCM operation with the granted resources in a specific Grant exchange, which \n is identified by the \"grantId\" available in the \"Individual VNF lifecycle management operation occurrence\" and the \"id\" \n in the \"Individual Grant\".\n",
+ "type": "object",
+ "required": [
+ "id",
+ "changeType",
+ "extCpInstanceId",
+ "resourceHandle"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "changeType": {
+ "description": "Signals the type of change. Permitted values: -\tADDED - MODIFIED -\tREMOVED\n",
+ "type": "string",
+ "enum": ["ADDED", "MODIFIED", "REMOVED"]
+ },
+ "extCpInstanceId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "resourceHandle": {
+ "required": ["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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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"
+ }
+ }
+ },
+ "resourceDefinitionId": {
+ "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "affectedVirtualStorages": {
+ "description": "Information about virtualised storage 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 virtual storage resources.\nNOTE:\tThe \"resourceDefinitionId\" attribute provides information to the API consumer (i.e. the NFVO) to \n assist in correlating the resource changes performed during the LCM operation with the granted \n resources in a specific Grant exchange, which is identified by the \"grantId\" available in the \n \"Individual VNF lifecycle management operation occurrence\" and the \"id\" in the \"Individual Grant\".\n",
+ "type": "object",
+ "required": [
+ "id",
+ "virtualStorageDescId",
+ "changeType",
+ "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": "An identifier that is unique within a VNF descriptor.\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: * ADDED * REMOVED * MODIFIED * TEMPORARY For a temporary resource, an AffectedVirtualStorage structure exists as long as the temporary resource exists.\n",
+ "type": "string",
+ "enum": ["ADDED", "REMOVED", "MODIFIED", "TEMPORARY"]
+ },
+ "storageResource": {
+ "required": ["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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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"
+ }
+ }
+ },
+ "resourceDefinitionId": {
+ "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "zoneId": {
+ "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 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"
+ }
+ }
+ }
+ }
+ }
+ },
+ "changedInfo": {
+ "description": "This type represents attribute modifications that were performed on an \"Individual VNF instance\" resource. The attributes that can be included consist of those requested to be modified explicitly in the \"VnfInfoModificationRequest\" data structure, and additional attributes of the \"VnfInstance\" data structure that were modified implicitly e.g. when modifying the referenced VNF package.\nNOTE:\tIf present, this attribute (which depends on the value of the \"vnfdId\" attribute) \n was modified implicitly following a request to modify the \"vnfdId\" attribute, by \n copying the value of this attribute from the VNFD in the VNF Package identified by \n the \"vnfdId\" attribute.\n",
+ "type": "object",
+ "properties": {
+ "vnfInstanceName": {
+ "description": "A string defined in IETF RFC 8259.\n",
+ "type": "string"
+ },
+ "vnfInstanceDescription": {
+ "description": "A string defined in IETF RFC 8259.\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 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"
+ },
+ "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 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"
+ },
+ "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 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"
+ },
+ "vimConnectionInfo": {
+ "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",
+ "type": "object",
+ "required": ["vimType"],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vimType": {
+ "description": "Discriminator for the different types of the VIM information. The value of this attribute determines the structure of the \"interfaceInfo\" and \"accessInfo\" attributes, based on the type of the VIM., CISM, CIR or MCIOP repository. The set of permitted values is expected to change over time as new types or versions of VIMs become available. The ETSI NFV registry of VIM-related information [i.3] provides access to information about VimConnectionInfo definitions for various VIM, CISM, CIR or MCIOP repository types. The structure of the registry is defined in annex C.\n",
+ "type": "string"
+ },
+ "interfaceInfo": {
+ "description": "This 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"
+ },
+ "accessInfo": {
+ "description": "This 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"
+ },
+ "extra": {
+ "description": "This 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"
+ }
+ }
+ }
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfProvider": {
+ "description": "A string defined in IETF RFC 8259.\n",
+ "type": "string"
+ },
+ "vnfProductName": {
+ "description": "A string defined in IETF RFC 8259.\n",
+ "type": "string"
+ },
+ "vnfSoftwareVersion": {
+ "description": "A version.\n",
+ "type": "string"
+ },
+ "vnfdVersion": {
+ "description": "A version.\n",
+ "type": "string"
+ }
+ }
+ },
+ "affectedVipCps": {
+ "description": "Information about virtual IP CP instances that were affected during the execution of the lifecycle management operation.\n",
+ "type": "array",
+ "items": {
+ "description": "This type provides information about added, deleted and modified virtual IP CP instances.\n",
+ "type": "object",
+ "required": ["cpInstanceId", "cpdId", "changeType"],
+ "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": "An identifier that is unique within a VNF descriptor.\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: -\tADDED -\tREMOVED -\tMODIFIED\n",
+ "type": "string",
+ "enum": ["ADDED", "REMOVED", "MODIFIED"]
+ }
+ }
+ }
+ },
+ "changedExtConnectivity": {
+ "description": "Information about changed external connectivity, if applicable. See note 1.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents information about an external VL.\nNOTE:\tThis attribute reflects the current configuration information that has resulted from merging into this attribute \n the \"VnfExtCpData\" information which was passed as part of the \"ExtVirtualLinkData\" structure in the input of the \n most recent VNF LCM operation such as \"InstantiateVnfRequest\", \"ChangeExtVnfConnectivityRequest\", \"ChangeVnfFlavourRequest\" \n or \"ChangeCurrentVnfPkgRequest\", or in the Grant response. If applying such change results in an empty list of \n \"currentVnfExtCpData\" structure instances, the affected instance of \"ExtVirtualLinkInfo\" shall be removed from its \n parent data structure.\n",
+ "type": "object",
+ "required": ["id", "resourceHandle", "currentVnfExtCpData"],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceHandle": {
+ "required": ["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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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.\nNOTE 1:\tThe use cases UC#4 and UC#5 in clause A.4 of ETSI GS NFV-IFA 007 provide examples for such a configuration. NOTE 2:\tThe 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": {
+ "required": ["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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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 the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "currentVnfExtCpData": {
+ "description": "Allows the API consumer to read the current CP configuration information for the connection of external CPs to the external virtual link. See note.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents configuration information for external CPs created. * NOTE 1: \tIn case this identifier refers to a CPD with trunking enabled, the external CP instances created\n from this CPD will represent ports in a trunk.\n* NOTE 2: \tWithin one VNF instance, all VNFC instances created from a particular VDU have the same external\n connectivity. Thus, given a particular value of the \"cpdId\" attribute, there shall be one\n \"cpConfig\" entry for each VNFC instance that has been or can be created from a VDU which includes\n a CPD identified by the \"cpdId\" attribute. If the cpConfig represents a subport in a trunk,\n all \"cpConfig\" entries in this list shall have the same segmentationId, which means they are\n connected to the same set of external VLs via the trunk.\n* NOTE 3: \tThe map entry value shall be set to \"null\" in order to delete a \"VnfExtCpConfig\" entry identified\n by a particular key value from the map, i.e. for the disconnection of an existing external\n CP instance addressed by cpInstanceId in the deleted map entry from a particular external\n virtual link, and deletion of that instance in case it represents a subport. Deleting the\n last key from the map removes the affected instance of the \"VnfExtCpData\" structure from\n its parent data structure.\n* NOTE 4: If, as defined by the input parameters of a \"ChangeVnfFlavour\", \"ChangeExtVnfConnectivity\" or\n \"ChangeCurrentVnfPkg\" operation or as part of the Grant response for any of these operations, a cpConfig\n map entry identified by a particular map key value is moved into another \"ExtVirtualLinkData\" or\n \"VnfExtCpData\" structure, this particular cpConfig map entry may be used by an external CP instance\n different than the one that has used it before the operation, or by no external CP instance at all.\n Renaming a CPD identifier during the \"changeCurrentVnfPkg\" operation does not count as moving the related\n \"cpConfig\" map entries to a new \"extCpData\" structure.\n",
+ "type": "object",
+ "required": ["cpdId"],
+ "properties": {
+ "cpdId": {
+ "description": "An identifier that is unique within a VNF descriptor.\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 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",
+ "anyOf": [
+ {
+ "required": ["linkPortId"]
+ },
+ {
+ "required": ["cpProtocolData"]
+ },
+ {
+ "required": ["netAttDefResourceId"]
+ }
+ ],
+ "type": "object",
+ "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 to the VNFM the need to create a dedicated link port for the external CP. If set to True, the VNFM shall create a link port. If set to False, the VNFM shall not create a link port. 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"
+ },
+ "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 2, 3 and 4.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ },
+ "cpProtocolData": {
+ "description": "Parameters for configuring the network protocols on the link port that connects the CP to a VL. See notes 1 and 2.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents network protocol data. * NOTE:\tThis attribute allows to signal the addition of further types of layer and protocol\n in future versions of the present document in a backwards-compatible way. In the current\n 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:\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 network address data for IP over Ethernet. * NOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. * NOTE 2:\tExactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present. * NOTE 3:\tIf the CP instance represents a subport in a trunk, segmentationId shall be present.\n Otherwise it shall not be present.\n* NOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the actual\n network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header\n of the packets or it may be an identifier used between the application and the NFVI networking\n infrastructure to identify the network sub-interface of the trunk port in question. In the latter\n case the NFVI infrastructure will map this local segmentationId to whatever segmentationId is\n actually used by the NFVI’s transport technology.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "required": ["macAddress"]
+ },
+ {
+ "required": ["ipAddresses"]
+ }
+ ],
+ "oneOf": [
+ {
+ "required": ["fixedAddresses"]
+ },
+ {
+ "required": ["numDynamicAddresses"]
+ },
+ {
+ "required": ["ipAddressRange"]
+ }
+ ],
+ "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: -\tVLAN: the subport uses VLAN as encapsulation type. -\tINHERIT: the subport gets its segmentation type from the network it’s 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"],
+ "properties": {
+ "type": {
+ "description": "The type of the IP addresses. Permitted values: IPV4, IPV6.\n",
+ "type": "string",
+ "enum": ["IPV4", "IPV6"]
+ },
+ "fixedAddresses": {
+ "description": "Fixed addresses to assign (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"
+ }
+ },
+ "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. 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.\n",
+ "type": "string"
+ }
+ }
+ }
+ }
+ }
+ },
+ "virtualCpAddress": {
+ "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",
+ "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"
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ },
+ "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 contains 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": {
+ "required": ["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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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 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 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"
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ },
+ "modificationsTriggeredByVnfPkgChange": {
+ "description": "This type represents attribute modifications that were performed on an \"Individual VNF instance\" resource when changing the current VNF package. The attributes that can be included consist of those requested to be modified explicitly in the \"ChangeCurrentVnfPkgRequest\" data structure, and additional attributes of the \"VnfInstance\" data structure that were modified implicitly during the operation.\nNOTE 1:\tThis attribute represents the delta (semantics as per IETF RFC 7396, JSON Merge Patch) between the value \n of the attribute at the start of the \"Change current VNF package\" operation and the value of the attribute \n at its completion.\nNOTE 2:\tIf present, this attribute (which depends on the value of the \"vnfdId\" attribute) was modified implicitly \n during the related operation and contains a copy of the value of the related attribute from the VNFD in the \n VNF Package identified by the \"vnfdId\" attribute.\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 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"
+ },
+ "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 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"
+ },
+ "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 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"
+ },
+ "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\". See note 2.\n",
+ "type": "string"
+ },
+ "vnfProductName": {
+ "description": "If present, this attribute signals the new value of the \"vnfProductName\" attribute in \"VnfInstance\". See note 2.\n",
+ "type": "string"
+ },
+ "vnfSoftwareVersion": {
+ "description": "A version.\n",
+ "type": "string"
+ },
+ "vnfdVersion": {
+ "description": "A version.\n",
+ "type": "string"
+ },
+ "vimConnectionInfo": {
+ "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",
+ "type": "object",
+ "required": ["vimType"],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vimType": {
+ "description": "Discriminator for the different types of the VIM information. The value of this attribute determines the structure of the \"interfaceInfo\" and \"accessInfo\" attributes, based on the type of the VIM., CISM, CIR or MCIOP repository. The set of permitted values is expected to change over time as new types or versions of VIMs become available. The ETSI NFV registry of VIM-related information [i.3] provides access to information about VimConnectionInfo definitions for various VIM, CISM, CIR or MCIOP repository types. The structure of the registry is defined in annex C.\n",
+ "type": "string"
+ },
+ "interfaceInfo": {
+ "description": "This 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"
+ },
+ "accessInfo": {
+ "description": "This 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"
+ },
+ "extra": {
+ "description": "This 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"
+ }
+ }
+ }
+ }
+ }
+ },
+ "vnfSnapshotInfoId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "lcmCoordinations": {
+ "description": "Information about LCM coordination actions (see clause 10 in ETSI GS NFV-SOL002) related to this LCM operation occurrence.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": [
+ "id",
+ "coordinationActionName",
+ "startTime",
+ "endpointType"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "coordinationActionName": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "coordinationResult": {
+ "description": "The enumeration LcmCoordResultType defines the permitted values to represent the result of executing an LCM coordination action. The coordination result also implies the action to be performed by the VNFM as the follow-up to this coordination. Value | Description ------|------------ CONTINUE | The related LCM operation shall be continued, staying in the state \"PROCESSING\". ABORT | The related LCM operation shall be aborted by transitioning into the state \"FAILED_TEMP\". CANCELLED | The coordination action has been cancelled upon request of the API consumer, i.e. the VNFM. The related LCM operation shall be aborted by transitioning into the state \"FAILED_TEMP\".\n",
+ "type": "string",
+ "enum": ["CONTINUE", "ABORT", "CANCELLED"]
+ },
+ "startTime": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "endTime": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "delay": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "endpointType": {
+ "description": "The endpoint type used by this coordination action. Valid values: •\tMGMT: coordination with other operation supporting management systems (e.g. EM) •\tVNF: coordination with the VNF instance\n",
+ "type": "string",
+ "enum": ["MGMT", "VNF"]
+ }
+ }
+ }
+ },
+ "rejectedLcmCoordinations": {
+ "description": "Information about LCM coordination actions (see clause 10 in ETSI GS NFV-SOL002) that were rejected by 503 error which means they can be tried again after a delay. See note 5.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": [
+ "coordinationActionName",
+ "rejectionTime",
+ "endpointType",
+ "delay"
+ ],
+ "properties": {
+ "coordinationActionName": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "rejectionTime": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "delay": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "endpointType": {
+ "description": "The endpoint type used by this coordination action. Valid values: •\tMGMT: coordination with other operation supporting management systems (e.g. EM) •\tVNF: coordination with the VNF instance\n",
+ "type": "string",
+ "enum": ["MGMT", "VNF"]
+ }
+ }
+ }
+ },
+ "warnings": {
+ "description": "Warning messages that were generated while the operation was executing.\nIf the operation has included LCM coordination actions and these have resulted in warnings, such warnings should be added to this attribute.\n",
+ "type": "array",
+ "items": {
+ "type": "string"
+ }
+ },
+ "_links": {
+ "description": "Links to resources related to this resource.\n",
+ "type": "object",
+ "required": ["self", "vnfInstance"],
+ "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"
+ }
+ }
+ },
+ "vnfInstance": {
+ "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"
+ }
+ }
+ },
+ "grant": {
+ "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"
+ }
+ }
+ },
+ "cancel": {
+ "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"
+ }
+ }
+ },
+ "retry": {
+ "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"
+ }
+ }
+ },
+ "rollback": {
+ "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"
+ }
+ }
+ },
+ "fail": {
+ "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"
+ }
+ }
+ },
+ "vnfSnapshot": {
+ "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"
+ }
+ }
+ }
+ }
+ }
+ }
+ }
}
diff --git a/SOL003/VNFLifecycleManagement-API/schemas/VnfLcmOperationOccurrenceNotification.schema.json b/SOL003/VNFLifecycleManagement-API/schemas/VnfLcmOperationOccurrenceNotification.schema.json
index d85ba3b6677bb2d2dc7de15b53b8dc7d36e7c747..8867491a38428167a017680a0ac347836f09887c 100644
--- a/SOL003/VNFLifecycleManagement-API/schemas/VnfLcmOperationOccurrenceNotification.schema.json
+++ b/SOL003/VNFLifecycleManagement-API/schemas/VnfLcmOperationOccurrenceNotification.schema.json
@@ -1,5 +1,5 @@
{
- "description": "This type represents a VNF lifecycle management operation occurrence notification, which informs the receiver of changes in the VNF lifecycle caused by a VNF LCM operation occurrence. It shall comply with the provisions defined in table 5.5.2.17-1. The support of the notification is mandatory. \nThis notification shall be triggered by the VNFM when there is a change in the state of a VNF LCM operation occurrence that changes the VNF lifecycle, which represents an occurrence of one the following LCM operations: - Instantiation of the VNF - Scaling of the VNF instance (including auto-scaling) - Healing of the VNF instance (including auto-healing) - Change of the state of the VNF instance (i.e. Operate VNF) - Change of the deployment flavour of the VNF instance - Change of the external connectivity of the VNF instance - Change of the current VNF package - Termination of the VNF instance - Modification of VNF instance information and/or VNF configurable properties through the \"PATCH\" \n method on the \"Individual VNF instance\" resource\n- Creation of a VNF snapshot - Reversion of the VNF instance to a VNF snapshot\nClause 5.6.2 defines the states and state transition of a VNF LCM operation occurrence, and also specifies details of the notifications to be emitted at each state transition. If this is the initial notification about the start of a VNF LCM operation occurrence, it is assumed that the notification is sent by the VNFM before any action (including sending the grant request) is taken as part of the LCM operation. Due to possible race conditions, the \"start\" notification, the grant request and the LCM operation acknowledgment (i.e. the \"202 Accepted\" response) can arrive in any order at the NFVO, and the NFVO shall be able to handle such a situation. If this is a notification about a final or intermediate result state of a VNF LCM operation occurrence, the notification shall be sent after all related actions of the LCM operation that led to this state have been executed. The new state shall be set in the \"Individual VNF LCM operation occurrence\" resource before the notification about the state change is sent. The amount of information provided in the LCM operation occurrence notifications to be issued by the VNFM when a particular subscription matches can be controlled by the API consumer using the \"verbosity\" attribute in the subscription request (see clause 5.5.2.15). The \"verbosity\" setting in a particular individual subscription shall only apply to the LCM operation occurrence notifications triggered by that subscription. However, it shall not affect the amount of information in the \"VnfLcmOpOcc\" structure (see clause 5.5.2.13) which represents the \"Individual LCM operation occurrence\" resource associated with each of the notifications. See clause 5.6.2.2 for further provisions regarding sending this notification, including in cases of handling LCM operation errors.\nNOTE 1:\tShall be present if the \"notificationStatus\" is set to \"RESULT\", the \"verbosity\" attribute is set to \"FULL\" \n and the operation has performed any resource modification. Shall be absent otherwise. This attribute contains \n information about the cumulative changes to virtualised resources that were performed so far by the VNF LCM \n operation occurrence and by any of the error handling procedures for that operation occurrence.\nNOTE 2:\tFor a particular affected VL, there shall be as many \"AffectedVirtualLink\" entries as needed for signalling \n the different types of changes, i.e. one per virtual link and change type. For instance, in the case of signaling \n affected VL instances involving the addition of a particular VL instance with links ports, one \"AffectedVirtualLink\" \n entry signals the addition of the VL by using the \"changeType\" attribute of \"AffectedVirtualLink\" structure equal to \n \"ADDED\", and another \"AffectedVirtualLink\" entry signals the addition of externally visible VNF link ports of the VL \n by using the \"changeType\" equal to \"LINK_PORT_ADDED\".\nNote 3: Not more than one of changedInfo and modificationsTriggeredByVnfPkgChange shall be present.\n",
+ "description": "This type represents a VNF lifecycle management operation occurrence notification, which informs the receiver of changes in the VNF lifecycle caused by a VNF LCM operation occurrence.\nThe support of the notification is mandatory. \nThis notification shall be triggered by the VNFM when there is a change in the state of a VNF LCM operation occurrence that changes the VNF lifecycle, which represents an occurrence of one the following LCM operations: - Instantiation of the VNF - Scaling of the VNF instance (including auto-scaling) - Healing of the VNF instance (including auto-healing) - Change of the state of the VNF instance (i.e. Operate VNF) - Change of the deployment flavour of the VNF instance - Change of the external connectivity of the VNF instance - Change of the current VNF package - Termination of the VNF instance - Modification of VNF instance information and/or VNF configurable properties through the \"PATCH\" \n method on the \"Individual VNF instance\" resource\n- Creation of a VNF snapshot - Reversion of the VNF instance to a VNF snapshot\nClause 5.6.2 defines the states and state transition of a VNF LCM operation occurrence, and also specifies details of the notifications to be emitted at each state transition. If this is the initial notification about the start of a VNF LCM operation occurrence, it is assumed that the notification is sent by the VNFM before any action (including sending the grant request) is taken as part of the LCM operation. Due to possible race conditions, the \"start\" notification, the grant request and the LCM operation acknowledgment (i.e. the \"202 Accepted\" response) can arrive in any order at the NFVO, and the NFVO shall be able to handle such a situation. If this is a notification about a final or intermediate result state of a VNF LCM operation occurrence, the notification shall be sent after all related actions of the LCM operation that led to this state have been executed. The new state shall be set in the \"Individual VNF LCM operation occurrence\" resource before the notification about the state change is sent. The amount of information provided in the LCM operation occurrence notifications to be issued by the VNFM when a particular subscription matches can be controlled by the API consumer using the \"verbosity\" attribute in the subscription request (see clause 5.5.2.15). The \"verbosity\" setting in a particular individual subscription shall only apply to the LCM operation occurrence notifications triggered by that subscription. However, it shall not affect the amount of information in the \"VnfLcmOpOcc\" structure (see clause 5.5.2.13) which represents the \"Individual LCM operation occurrence\" resource associated with each of the notifications. See clause 5.6.2.2 for further provisions regarding sending this notification, including in cases of handling LCM operation errors.\nNOTE 1:\tShall be present if the \"notificationStatus\" is set to \"RESULT\", the \"verbosity\" attribute is set to \"FULL\" \n and the operation has performed any resource modification. Shall be absent otherwise. This attribute contains \n information about the cumulative changes to virtualised resources that were performed so far by the VNF LCM \n operation occurrence and by any of the error handling procedures for that operation occurrence.\nNOTE 2:\tFor a particular affected VL, there shall be as many \"AffectedVirtualLink\" entries as needed for signalling \n the different types of changes, i.e. one per virtual link and change type. For instance, in the case of signaling \n affected VL instances involving the addition of a particular VL instance with links ports, one \"AffectedVirtualLink\" \n entry signals the addition of the VL by using the \"changeType\" attribute of \"AffectedVirtualLink\" structure equal to \n \"ADDED\", and another \"AffectedVirtualLink\" entry signals the addition of externally visible VNF link ports of the VL \n by using the \"changeType\" equal to \"LINK_PORT_ADDED\".\nNote 3: Not more than one of changedInfo and modificationsTriggeredByVnfPkgChange shall be present.\n",
"type": "object",
"required": [
"id",
@@ -56,7 +56,7 @@
"type": "string"
},
"operation": {
- "description": "The enumeration LcmOpType defines the permitted values to represent VNF lifecycle operation types in VNF lifecycle management operation occurrence resources and VNF lifecycle management operation occurrence notifications. It shall comply with the provisions defined in table 5.5.4.5-1.\nValue | Description ------|------------ INSTANTIATE | Represents the \"Instantiate VNF\" LCM operation. SCALE | Represents the \"Scale VNF\" LCM operation. SCALE_TO_LEVEL | Represents the \"Scale VNF to Level\" LCM operation. CHANGE_FLAVOUR | Represents the \"Change VNF Flavour\" LCM operation. TERMINATE | Represents the \"Terminate VNF\" LCM operation. HEAL | Represents the \"Heal VNF\" LCM operation. OPERATE | Represents the \"Operate VNF\" LCM operation. CHANGE_EXT_CONN | Represents the \"Change external VNF connectivity\" LCM operation. MODIFY_INFO | Represents the \"Modify VNF Information\" LCM operation. CREATE_SNAPSHOT | Represents the \"Create VNF Snapshot\" LCM operation. REVERT_TO_SNAPSHOT | Represents the ΓÇ£Revert-To VNF Snapshot\" LCM operation. CHANGE_VNFPKG | Represents the \"Change current VNF package\" LCM operation.\n",
+ "description": "The enumeration LcmOpType defines the permitted values to represent VNF lifecycle operation types in VNF lifecycle management operation occurrence resources and VNF lifecycle management operation occurrence notifications.\nValue | Description ------|------------ INSTANTIATE | Represents the \"Instantiate VNF\" LCM operation. SCALE | Represents the \"Scale VNF\" LCM operation. SCALE_TO_LEVEL | Represents the \"Scale VNF to Level\" LCM operation. CHANGE_FLAVOUR | Represents the \"Change VNF Flavour\" LCM operation. TERMINATE | Represents the \"Terminate VNF\" LCM operation. HEAL | Represents the \"Heal VNF\" LCM operation. OPERATE | Represents the \"Operate VNF\" LCM operation. CHANGE_EXT_CONN | Represents the \"Change external VNF connectivity\" LCM operation. MODIFY_INFO | Represents the \"Modify VNF Information\" LCM operation. CREATE_SNAPSHOT | Represents the \"Create VNF Snapshot\" LCM operation. REVERT_TO_SNAPSHOT | Represents the “Revert-To VNF Snapshot\" LCM operation. CHANGE_VNFPKG | Represents the \"Change current VNF package\" LCM operation.\n",
"type": "string",
"enum": [
"INSTANTIATE",
@@ -78,7 +78,7 @@
"type": "boolean"
},
"verbosity": {
- "description": "The enumeration LcmOpOccNotificationVerbosityType provides values to control the verbosity of LCM operation occurrence notifications. * 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",
+ "description": "The enumeration LcmOpOccNotificationVerbosityType provides values to control the verbosity of LCM operation occurrence notifications. * 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"]
},
@@ -90,7 +90,7 @@
"description": "Information about VNFC 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 VNFCs. It shall comply with the provisions in table 5.5.3.13-1.\nNOTE:\tThe \"resourceDefinitionId\" attribute provides information to the API consumer \n (i.e. the NFVO) to assist in correlating the resource changes performed during \n the LCM operation with the granted resources in a specific Grant exchange, which \n is identified by the \"grantId\" available in the \"Individual VNF lifecycle management \n operation occurrence\" and the \"id\" in the \"Individual Grant\".\n",
+ "description": "This type provides information about added, deleted, modified and temporary VNFCs.\nNOTE:\tThe \"resourceDefinitionId\" attribute provides information to the API consumer \n (i.e. the NFVO) to assist in correlating the resource changes performed during \n the LCM operation with the granted resources in a specific Grant exchange, which \n is identified by the \"grantId\" available in the \"Individual VNF lifecycle management \n operation occurrence\" and the \"id\" in the \"Individual Grant\".\n",
"type": "object",
"required": ["id", "vduId", "changeType", "computeResource"],
"properties": {
@@ -114,7 +114,7 @@
"computeResource": {
"required": ["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",
+ "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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
@@ -125,11 +125,33 @@
"type": "string"
},
"resourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
"type": "string"
},
"vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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"
}
}
@@ -213,7 +235,7 @@
"networkResource": {
"required": ["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",
+ "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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
@@ -224,17 +246,39 @@
"type": "string"
},
"resourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
"type": "string"
},
"vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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"
}
}
},
"vnfLinkPortIds": {
- "description": "Identifiers of the link ports of the affected VL related to the change. Each identifier references a \"VnfLinkPortInfo\" structure.\nShall be set when changeType is equal to \"LINK_PORT_ADDED\" or \"LINK_PORT_REMOVED\", and the related \"VnfLinkPortInfo\" structures are present (case \"added\") or have been present (case \"removed\") in the \"VnfVirtualLinkResourceInfo\" or \"ExtManagedVirtualLinkInfo\" structures that are represented by the \"vnfVirtualLinkResource¬Info\" or \"extManagedVirtualLinkInfo\" attribute in the \"VnfInstance\" structure. See note 1.\n",
+ "description": "Identifiers of the link ports of the affected VL related to the change. Each identifier references a \"VnfLinkPortInfo\" structure.\nShall be set when changeType is equal to \"LINK_PORT_ADDED\" or \"LINK_PORT_REMOVED\", and the related \"VnfLinkPortInfo\" structures are present (case \"added\") or have been present (case \"removed\") in the \"VnfVirtualLinkResourceInfo\" or \"ExtManagedVirtualLinkInfo\" structures that are represented by the \"vnfVirtualLinkResource¬Info\" or \"extManagedVirtualLinkInfo\" attribute in the \"VnfInstance\" structure. See note 1.\n",
"type": "array",
"items": {
"description": "An identifier that is unique within a VNF descriptor.\n",
@@ -260,7 +304,7 @@
"description": "Information about external VNF link ports that were affected during the lifecycle operation. See note 1.\n",
"type": "array",
"items": {
- "description": "This type provides information about added and deleted external link ports (link ports attached to external virtual links). It shall comply with the provisions in table 5.5.3.14a-1.\nNOTE:\tThe \"resourceDefinitionId\" attribute provides information to the API consumer (i.e. the NFVO) to assist in correlating \n the resource changes performed during the LCM operation with the granted resources in a specific Grant exchange, which \n is identified by the \"grantId\" available in the \"Individual VNF lifecycle management operation occurrence\" and the \"id\" \n in the \"Individual Grant\".\n",
+ "description": "This type provides information about added and deleted external link ports (link ports attached to external virtual links).\nNOTE:\tThe \"resourceDefinitionId\" attribute provides information to the API consumer (i.e. the NFVO) to assist in correlating \n the resource changes performed during the LCM operation with the granted resources in a specific Grant exchange, which \n is identified by the \"grantId\" available in the \"Individual VNF lifecycle management operation occurrence\" and the \"id\" \n in the \"Individual Grant\".\n",
"type": "object",
"required": ["id", "changeType", "extCpInstanceId", "resourceHandle"],
"properties": {
@@ -271,7 +315,7 @@
"changeType": {
"description": "Signals the type of change. Permitted values: -\tADDED - MODIFIED -\tREMOVED\n",
"type": "string",
- "enum": ["ADDED", "MODIFIED","REMOVED"]
+ "enum": ["ADDED", "MODIFIED", "REMOVED"]
},
"extCpInstanceId": {
"description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
@@ -280,7 +324,7 @@
"resourceHandle": {
"required": ["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",
+ "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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
@@ -291,11 +335,33 @@
"type": "string"
},
"resourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
"type": "string"
},
"vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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"
}
}
@@ -311,7 +377,7 @@
"description": "Information about virtualised storage 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 virtual storage resources. It shall comply with the provisions in table 5.5.3.15-1.\nNOTE:\tThe \"resourceDefinitionId\" attribute provides information to the API consumer (i.e. the NFVO) to \n assist in correlating the resource changes performed during the LCM operation with the granted \n resources in a specific Grant exchange, which is identified by the \"grantId\" available in the \n \"Individual VNF lifecycle management operation occurrence\" and the \"id\" in the \"Individual Grant\".\n",
+ "description": "This type provides information about added, deleted, modified and temporary virtual storage resources.\nNOTE:\tThe \"resourceDefinitionId\" attribute provides information to the API consumer (i.e. the NFVO) to \n assist in correlating the resource changes performed during the LCM operation with the granted \n resources in a specific Grant exchange, which is identified by the \"grantId\" available in the \n \"Individual VNF lifecycle management operation occurrence\" and the \"id\" in the \"Individual Grant\".\n",
"type": "object",
"required": [
"id",
@@ -340,7 +406,7 @@
"storageResource": {
"required": ["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",
+ "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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
@@ -351,11 +417,33 @@
"type": "string"
},
"resourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
"type": "string"
},
"vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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"
}
}
@@ -376,7 +464,7 @@
}
},
"changedInfo": {
- "description": "This type represents attribute modifications that were performed on an \"Individual VNF instance\" resource. The attributes that can be included consist of those requested to be modified explicitly in the \"VnfInfoModificationRequest\" data structure, and additional attributes of the \"VnfInstance\" data structure that were modified implicitly e.g. when modifying the referenced VNF package. The \"VnfInfoModifications\" data type shall comply with the provisions defined in table 5.5.2.12a-1.\nNOTE:\tIf present, this attribute (which depends on the value of the \"vnfdId\" attribute) \n was modified implicitly following a request to modify the \"vnfdId\" attribute, by \n copying the value of this attribute from the VNFD in the VNF Package identified by \n the \"vnfdId\" attribute.\n",
+ "description": "This type represents attribute modifications that were performed on an \"Individual VNF instance\" resource. The attributes that can be included consist of those requested to be modified explicitly in the \"VnfInfoModificationRequest\" data structure, and additional attributes of the \"VnfInstance\" data structure that were modified implicitly e.g. when modifying the referenced VNF package.\nNOTE:\tIf present, this attribute (which depends on the value of the \"vnfdId\" attribute) \n was modified implicitly following a request to modify the \"vnfdId\" attribute, by \n copying the value of this attribute from the VNFD in the VNF Package identified by \n the \"vnfdId\" attribute.\n",
"type": "object",
"properties": {
"vnfInstanceName": {
@@ -403,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 for managing the resources of a VNF instance. * 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 is provided through a secure connection over\n HTTP Secure (HTTP over SSL/TLS), and the connection might also be established through a VPN\n (for example TLS-based VPN tunnelling) for site-to-site connection, the \"accessInfo\" JSON data\n structure, and the sensitive data related information (\"username\"/\"password\" as required properties\n for authentication purpose), will be transmitted as plain text through a TLS tunnel without additional\n encoding/encryption before transmitting it, making the sensitive data visible to the endpoint.\n The base64 encoded certificates are only used by the VNFM to verify the authenticity of the\n interface endpoint of the VIM.\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",
"type": "object",
"required": ["vimType"],
"properties": {
@@ -412,7 +500,7 @@
"type": "string"
},
"vimType": {
- "description": "Discriminator for the different types of the VIM information. The value of this attribute determines the structure of the \"interfaceInfo\" and \"accessInfo\" attributes, based on the type of the VIM. The set of permitted values is expected to change over time as new types or versions of VIMs become available. The ETSI NFV registry of VIM-related information provides access to information about VimConnectionInfo definitions for various VIM types. The structure of the registry is defined in Annex C of SOL003.\n",
+ "description": "Discriminator for the different types of the VIM information. The value of this attribute determines the structure of the \"interfaceInfo\" and \"accessInfo\" attributes, based on the type of the VIM., CISM, CIR or MCIOP repository. The set of permitted values is expected to change over time as new types or versions of VIMs become available. The ETSI NFV registry of VIM-related information [i.3] provides access to information about VimConnectionInfo definitions for various VIM, CISM, CIR or MCIOP repository types. The structure of the registry is defined in annex C.\n",
"type": "string"
},
"interfaceInfo": {
@@ -480,11 +568,39 @@
}
}
},
+ "affectedVirtualCps": {
+ "description": "Information about virtual CP instances that were affected during the execution of the lifecycle management operation, if this notification represents the result of a lifecycle management operation occurrence. Shall be present if the \"notificationStatus\" is set to \"RESULT\", the \"verbosity\" attribute is set to \"FULL\" and the operation has made any changes to the virtual CP instances of the VNF instance. Shall be absent otherwise. Only information about virtual CP instances that have been added, deleted or modified shall be provided.",
+ "type": "array",
+ "items": {
+ "description": "This type provides information about added, deleted and modified virtual CP instances.\n",
+ "type": "object",
+ "required": ["cpInstanceId", "cpdId", "changeType"],
+ "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": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "changeType": {
+ "description": "Signals the type of change.\nPermitted values:\n - ADDED\n - REMOVED\n - MODIFIED\n",
+ "type": "string",
+ "enum": ["ADDED", "REMOVED", "MODIFIED"]
+ }
+ }
+ }
+ },
"changedExtConnectivity": {
"description": "Information about changed external connectivity, if this notification represents the result of a lifecycle operation occurrence. Shall be present if the \"notificationStatus\" is set to \"RESULT\", the \"verbosity\" attribute is set to \"FULL\" and the operation has made any changes to the external connectivity of the VNF instance. Shall be absent otherwise. Only information about external VL instances that have been added or modified shall be provided.\n",
"type": "array",
"items": {
- "description": "This type represents information about an external VL. It shall comply with the provisions defined in table 5.5.3.2-1.\nNOTE:\tThis attribute reflects the current configuration information that has resulted from merging into this attribute \n the \"VnfExtCpData\" information which was passed as part of the \"ExtVirtualLinkData\" structure in the input of the \n most recent VNF LCM operation such as \"InstantiateVnfRequest\", \"ChangeExtVnfConnectivityRequest\", \"ChangeVnfFlavourRequest\" \n or \"ChangeCurrentVnfPkgRequest\", or in the Grant response. If applying such change results in an empty list of \n \"currentVnfExtCpData\" structure instances, the affected instance of \"ExtVirtualLinkInfo\" shall be removed from its \n parent data structure.\n",
+ "description": "This type represents information about an external VL.\nNOTE:\tThis attribute reflects the current configuration information that has resulted from merging into this attribute \n the \"VnfExtCpData\" information which was passed as part of the \"ExtVirtualLinkData\" structure in the input of the \n most recent VNF LCM operation such as \"InstantiateVnfRequest\", \"ChangeExtVnfConnectivityRequest\", \"ChangeVnfFlavourRequest\" \n or \"ChangeCurrentVnfPkgRequest\", or in the Grant response. If applying such change results in an empty list of \n \"currentVnfExtCpData\" structure instances, the affected instance of \"ExtVirtualLinkInfo\" shall be removed from its \n parent data structure.\n",
"type": "object",
"required": ["id", "resourceHandle", "currentVnfExtCpData"],
"properties": {
@@ -495,7 +611,7 @@
"resourceHandle": {
"required": ["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",
+ "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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
@@ -506,11 +622,33 @@
"type": "string"
},
"resourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
"type": "string"
},
"vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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"
}
}
@@ -519,7 +657,7 @@
"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. It shall comply with the provisions defined in table 5.5.3.9-1.\nNOTE 1:\tThe use cases UC#4 and UC#5 in clause A.4 of ETSI GS NFV-IFA 007 provide examples for such a configuration. NOTE 2:\tThe value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\" attribute.\n",
+ "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.\nNOTE 1:\tThe use cases UC#4 and UC#5 in clause A.4 of ETSI GS NFV-IFA 007 provide examples for such a configuration. NOTE 2:\tThe value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\" attribute.\n",
"type": "object",
"required": ["id", "resourceHandle"],
"properties": {
@@ -530,7 +668,7 @@
"resourceHandle": {
"required": ["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",
+ "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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
@@ -541,11 +679,33 @@
"type": "string"
},
"resourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
"type": "string"
},
"vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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"
}
}
@@ -559,7 +719,7 @@
"type": "string"
},
"trunkResourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
"type": "string"
}
}
@@ -569,7 +729,7 @@
"description": "Allows the API consumer to read the current CP configuration information for the connection of external CPs to the external virtual link. See note.\n",
"type": "array",
"items": {
- "description": "This type represents configuration information for external CPs created. * NOTE 1: \tIn case this identifier refers to a CPD with trunking enabled, the external CP instances created\n from this CPD will represent ports in a trunk.\n* NOTE 2: \tWithin one VNF instance, all VNFC instances created from a particular VDU have the same external\n connectivity. Thus, given a particular value of the \"cpdId\" attribute, there shall be one\n \"cpConfig\" entry for each VNFC instance that has been or can be created from a VDU which includes\n a CPD identified by the \"cpdId\" attribute. If the cpConfig represents a subport in a trunk,\n all \"cpConfig\" entries in this list shall have the same segmentationId, which means they are\n connected to the same set of external VLs via the trunk.\n* NOTE 3: \tThe map entry value shall be set to \"null\" in order to delete a \"VnfExtCpConfig\" entry identified\n by a particular key value from the map, i.e. for the disconnection of an existing external\n CP instance addressed by cpInstanceId in the deleted map entry from a particular external\n virtual link, and deletion of that instance in case it represents a subport. Deleting the\n last key from the map removes the affected instance of the \"VnfExtCpData\" structure from\n its parent data structure.\n* NOTE 4: If, as defined by the input parameters of a \"ChangeVnfFlavour\", \"ChangeExtVnfConnectivity\" or \n \"ChangeCurrentVnfPkg\" operation or as part of the Grant response for any of these operations, a \n cpConfig map entry identified by a particular map key value is moved into another \"ExtVirtualLinkData\"\n or \"VnfExtCpData\" structure, this particular cpConfig map entry may be used by an external CP instance\n different than the one that has used it before the operation, or by no external CP instance at all.\n Renaming a CPD identifier during the \"changeCurrentVnfPkg\" operation does not count as moving the\n related \"cpConfig\" map entries to a new \"extCpData\" structure.\n",
+ "description": "This type represents configuration information for external CPs created. * NOTE 1: \tIn case this identifier refers to a CPD with trunking enabled, the external CP instances created\n from this CPD will represent ports in a trunk.\n* NOTE 2: \tWithin one VNF instance, all VNFC instances created from a particular VDU have the same external\n connectivity. Thus, given a particular value of the \"cpdId\" attribute, there shall be one\n \"cpConfig\" entry for each VNFC instance that has been or can be created from a VDU which includes\n a CPD identified by the \"cpdId\" attribute. If the cpConfig represents a subport in a trunk,\n all \"cpConfig\" entries in this list shall have the same segmentationId, which means they are\n connected to the same set of external VLs via the trunk.\n* NOTE 3: \tThe map entry value shall be set to \"null\" in order to delete a \"VnfExtCpConfig\" entry identified\n by a particular key value from the map, i.e. for the disconnection of an existing external\n CP instance addressed by cpInstanceId in the deleted map entry from a particular external\n virtual link, and deletion of that instance in case it represents a subport. Deleting the\n last key from the map removes the affected instance of the \"VnfExtCpData\" structure from\n its parent data structure.\n* NOTE 4: If, as defined by the input parameters of a \"ChangeVnfFlavour\", \"ChangeExtVnfConnectivity\" or\n \"ChangeCurrentVnfPkg\" operation or as part of the Grant response for any of these operations, a cpConfig\n map entry identified by a particular map key value is moved into another \"ExtVirtualLinkData\" or\n \"VnfExtCpData\" structure, this particular cpConfig map entry may be used by an external CP instance\n different than the one that has used it before the operation, or by no external CP instance at all.\n Renaming a CPD identifier during the \"changeCurrentVnfPkg\" operation does not count as moving the related\n \"cpConfig\" map entries to a new \"extCpData\" structure.\n",
"type": "object",
"required": ["cpdId"],
"properties": {
@@ -578,16 +738,19 @@
"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). See notes 2, 3 and 4.\n",
+ "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 network address information per instance of an external connection point. In case a link port is provided, the VNFM shall use that link port when connecting the external CP to the external VL. In a link port is not provided, the VNFM shall create a link port on the external VL, and use that link port to connect the external CP to the external VL. * NOTE: The following conditions apply to the attributes \"linkPortId\" and \"cpProtocolData\":\n 1) Void.\n 2) At least one of the \"linkPortId\" and \"cpProtocolData\" attributes shall be present for an external\n CP instance representing a subport that is to be created, or an external CP instance that is to be\n created by creating the corresponding VNFC or VNF instance during the current or a subsequent LCM\n operation, or for an existing external CP instance that is to be re-configured or added to a\n 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\n a pre created link port, and the VNFM can use means outside the scope of the present document to obtain\n the pre-configured address information for the connection point from the resource representing\n the link port.\n 5) If both \"cpProtocolData\" and \"linkportId\" are provided, the API consumer shall ensure that the\n cpProtocolData can be used with the pre-created link port referenced by \"linkPortId\".\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) 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",
"anyOf": [
{
"required": ["linkPortId"]
},
{
"required": ["cpProtocolData"]
+ },
+ {
+ "required": ["netAttDefResourceId"]
}
],
"type": "object",
@@ -604,8 +767,16 @@
"description": "Indicates to the VNFM the need to create a dedicated link port for the external CP. If set to True, the VNFM shall create a link port. If set to False, the VNFM shall not create a link port. 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"
},
+ "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 2, 3 and 4.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ },
"cpProtocolData": {
- "description": "Parameters for configuring the network protocols on the link port that connects the CP to a VL. See note.\n",
+ "description": "Parameters for configuring the network protocols on the link port that connects the CP to a VL. See notes 1 and 2.\n",
"type": "array",
"items": {
"description": "This type represents network protocol data. * NOTE:\tThis attribute allows to signal the addition of further types of layer and protocol\n in future versions of the present document in a backwards-compatible way. In the current\n version of the present document, only IP over Ethernet is supported.\n",
@@ -613,12 +784,12 @@
"required": ["layerProtocol"],
"properties": {
"layerProtocol": {
- "description": "Identifier of layer(s) and protocol(s). See note.\n",
+ "description": "Identifier of layer(s) and protocol(s). Permitted values:\n - IP_OVER_ETHERNET.\n - IP_FOR_VIRTUAL_CP\nSee note\n",
"type": "string",
- "enum": ["IP_OVER_ETHERNET"]
+ "enum": ["IP_OVER_ETHERNET", "IP_FOR_VIRTUAL_CP"]
},
"ipOverEthernet": {
- "description": "This type represents network address data for IP over Ethernet. * NOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. * NOTE 2:\tExactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present. * NOTE 3:\tIf the CP instance represents a subport in a trunk, segmentationId shall be present.\n Otherwise it shall not be present.\n* NOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the actual\n network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header\n of the packets or it may be an identifier used between the application and the NFVI networking\n infrastructure to identify the network sub-interface of the trunk port in question. In the latter\n case the NFVI infrastructure will map this local segmentationId to whatever segmentationId is\n actually used by the NFVIΓÇÖs transport technology.\n",
+ "description": "This type represents network address data for IP over Ethernet. * NOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. * NOTE 2:\tExactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present. * NOTE 3:\tIf the CP instance represents a subport in a trunk, segmentationId shall be present.\n Otherwise it shall not be present.\n* NOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the actual\n network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header\n of the packets or it may be an identifier used between the application and the NFVI networking\n infrastructure to identify the network sub-interface of the trunk port in question. In the latter\n case the NFVI infrastructure will map this local segmentationId to whatever segmentationId is\n actually used by the NFVI’s transport technology.\n",
"type": "object",
"anyOf": [
{
@@ -646,7 +817,7 @@
"format": "MAC"
},
"segmentationType": {
- "description": "Specifies the encapsulation type for the traffics coming in and out of the trunk subport. Permitted values: -\tVLAN: the subport uses VLAN as encapsulation type. -\tINHERIT: the subport gets its segmentation type from the network itΓÇÖs 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",
+ "description": "Specifies the encapsulation type for the traffics coming in and out of the trunk subport. Permitted values: -\tVLAN: the subport uses VLAN as encapsulation type. -\tINHERIT: the subport gets its segmentation type from the network it’s 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"]
},
@@ -700,13 +871,30 @@
}
},
"subnetId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
"type": "string"
}
}
}
}
}
+ },
+ "virtualCpAddress": {
+ "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",
+ "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"
+ }
+ }
}
}
}
@@ -716,12 +904,88 @@
}
}
}
+ },
+ "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 contains 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": {
+ "required": ["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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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 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 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"
+ }
+ }
+ }
+ }
}
}
}
},
"modificationsTriggeredByVnfPkgChange": {
- "description": "This type represents attribute modifications that were performed on an \"Individual VNF instance\" resource when changing the current VNF package. The attributes that can be included consist of those requested to be modified explicitly in the \"ChangeCurrentVnfPkgRequest\" data structure, and additional attributes of the \"VnfInstance\" data structure that were modified implicitly during the operation. The \"ModificationsTriggeredByVnfPkgChange\" data type shall comply with the provisions defined in table 5.5.3.21-1.\nNOTE 1:\tThis attribute represents the delta (semantics as per IETF RFC 7396, JSON Merge Patch) between the value \n of the attribute at the start of the \"Change current VNF package\" operation and the value of the attribute \n at its completion.\nNOTE 2:\tIf present, this attribute (which depends on the value of the \"vnfdId\" attribute) was modified implicitly \n during the related operation and contains a copy of the value of the related attribute from the VNFD in the \n VNF Package identified by the \"vnfdId\" attribute.\n",
+ "description": "This type represents attribute modifications that were performed on an \"Individual VNF instance\" resource when changing the current VNF package. The attributes that can be included consist of those requested to be modified explicitly in the \"ChangeCurrentVnfPkgRequest\" data structure, and additional attributes of the \"VnfInstance\" data structure that were modified implicitly during the operation.\nNOTE 1:\tThis attribute represents the delta (semantics as per IETF RFC 7396, JSON Merge Patch) between the value \n of the attribute at the start of the \"Change current VNF package\" operation and the value of the attribute \n at its completion.\nNOTE 2:\tIf present, this attribute (which depends on the value of the \"vnfdId\" attribute) was modified implicitly \n during the related operation and contains a copy of the value of the related attribute from the VNFD in the \n VNF Package identified by the \"vnfdId\" attribute.\n",
"type": "object",
"properties": {
"vnfConfigurableProperties": {
@@ -760,7 +1024,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 for managing the resources of a VNF instance. * 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 is provided through a secure connection over\n HTTP Secure (HTTP over SSL/TLS), and the connection might also be established through a VPN\n (for example TLS-based VPN tunnelling) for site-to-site connection, the \"accessInfo\" JSON data\n structure, and the sensitive data related information (\"username\"/\"password\" as required properties\n for authentication purpose), will be transmitted as plain text through a TLS tunnel without additional\n encoding/encryption before transmitting it, making the sensitive data visible to the endpoint.\n The base64 encoded certificates are only used by the VNFM to verify the authenticity of the\n interface endpoint of the VIM.\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",
"type": "object",
"required": ["vimType"],
"properties": {
@@ -769,7 +1033,7 @@
"type": "string"
},
"vimType": {
- "description": "Discriminator for the different types of the VIM information. The value of this attribute determines the structure of the \"interfaceInfo\" and \"accessInfo\" attributes, based on the type of the VIM. The set of permitted values is expected to change over time as new types or versions of VIMs become available. The ETSI NFV registry of VIM-related information provides access to information about VimConnectionInfo definitions for various VIM types. The structure of the registry is defined in Annex C of SOL003.\n",
+ "description": "Discriminator for the different types of the VIM information. The value of this attribute determines the structure of the \"interfaceInfo\" and \"accessInfo\" attributes, based on the type of the VIM., CISM, CIR or MCIOP repository. The set of permitted values is expected to change over time as new types or versions of VIMs become available. The ETSI NFV registry of VIM-related information [i.3] provides access to information about VimConnectionInfo definitions for various VIM, CISM, CIR or MCIOP repository types. The structure of the registry is defined in annex C.\n",
"type": "string"
},
"interfaceInfo": {
@@ -859,4 +1123,4 @@
}
}
}
-}
\ No newline at end of file
+}
diff --git a/SOL003/VNFLifecycleManagement-API/schemas/VnfSnapshotInfo.schema.json b/SOL003/VNFLifecycleManagement-API/schemas/VnfSnapshotInfo.schema.json
index 63e536508576fab7ca0bcc5f10c11317342edb8c..ad5405ed9333c635fbef3c8ed9f3dbcbe6c2716a 100644
--- a/SOL003/VNFLifecycleManagement-API/schemas/VnfSnapshotInfo.schema.json
+++ b/SOL003/VNFLifecycleManagement-API/schemas/VnfSnapshotInfo.schema.json
@@ -1,1542 +1,2412 @@
{
- "description": "This type represents an \"Individual VNF snapshot\" resource. It shall comply with the provisions defined in table 5.5.2.22-1.\n",
- "type": "object",
- "required": [
- "id",
- "_links"
- ],
- "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 5.5.2.23-1.\n",
- "type": "object",
- "required": [
- "id",
- "vnfInstanceId",
- "triggeredAt",
- "vnfdId",
- "vnfInfo",
- "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",
- "type": "string"
- },
- "creationStartedAt": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "creationFinishedAt": {
- "description": "Date-time stamp. Representation: String formatted according to 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.\n",
- "type": "object",
- "required": [
- "id",
- "vnfdId",
- "vnfProvider",
- "vnfProductName",
- "vnfSoftwareVersion",
- "vnfdVersion",
- "instantiationState"
- ],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfInstanceName": {
- "description": "Name of the VNF instance. This attribute can be modified with the PATCH method.\n",
- "type": "string"
- },
- "vnfInstanceDescription": {
- "description": "Human-readable description of the VNF instance. This attribute can be modified with the PATCH method.\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.\n",
- "type": "string"
- },
- "vnfdVersion": {
- "description": "A version.\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 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"
- },
- "vimConnectionInfo": {
- "description": "Information about VIM 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 VNF-related resource management in direct mode is pplicable. This attribute can be modified with the PATCH method.\n",
- "type": "object",
- "additionalProperties": {
- "description": "This type represents parameters to connect to a VIM for managing the resources of a VNF instance. This structure is used to convey VIM-related parameters over the Or-Vnfm interface. Additional parameters for a VIM may be configured into the VNFM by means outside the scope of the present document, and bound to the identifier of that VIM.\n",
- "type": "object",
- "required": [
- "vimType"
- ],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vimType": {
- "description": "Discriminator for the different types of the VIM information. The value of this attribute determines the structure of the \"interfaceInfo\" and \"accessInfo\" attributes, based on the type of the VIM. The set of permitted values is expected to change over time as new types or versions of VIMs become available. The ETSI NFV registry of VIM-related information provides access to information about VimConnectionInfo definitions for various VIM types. The structure of the registry is defined in Annex C of SOL003.\n",
- "type": "string"
- },
- "interfaceInfo": {
- "description": "This 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"
- },
- "accessInfo": {
- "description": "This 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"
- },
- "extra": {
- "description": "This 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"
- }
- }
- }
- },
- "instantiationState": {
- "description": "The instantiation state of the VNF.\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"
- ],
- "properties": {
- "flavourId": {
- "description": "An identifier that is unique within a VNF descriptor.\n",
- "type": "string"
- },
- "vnfState": {
- "description": "STARTED: The VNF instance is up and running. STOPPED: The VNF instance has been shut down.\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. This attribute shall be present if the VNF supports scaling. See clause B.2 for an explanation of VNF scaling.\n",
- "type": "array",
- "items": {
- "required": [
- "aspectId",
- "scaleLevel"
- ],
- "type": "object",
- "properties": {
- "aspectId": {
- "description": "An identifier that is unique within a VNF descriptor.\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"
- }
- }
- }
- },
- "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": "An identifier that is unique within a VNF descriptor.\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"
- }
- }
- }
- },
- "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 5.5.3.25 1.\n",
- "type": "object",
- "required": [
- "id",
- "cpdId",
- "cpConfigId",
- "cpProtocolInfo"
- ],
- "oneOf": [{
- "required": [
- "associatedVnfcCpId"
- ]
- },
- {
- "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": "An identifier that is unique within a VNF descriptor.\n",
- "type": "string"
- },
- "cpConfigId": {
- "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"
- },
- "cpProtocolInfo": {
- "description": "Network protocol information for this CP.\n",
- "type": "array",
- "items": {
- "description": "This type describes the protocol layer(s) that a CP uses together with protocol-related information, like addresses.\n",
- "type": "object",
- "required": [
- "layerProtocol"
- ],
- "properties": {
- "layerProtocol": {
- "description": "The identifier of layer(s) and protocol(s) associated to the network address information. Permitted values: IP_OVER_ETHERNET 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": "string",
- "enum": [
- "IP_OVER_ETHERNET"
- ]
- },
- "ipOverEthernet": {
- "description": "This type represents information about a network address that has been assigned.\n",
- "type": "object",
- "anyOf": [{
- "required": [
- "macAddress"
- ]
- },
- {
- "required": [
- "ipAddresses"
- ]
- }
- ],
- "oneOf": [{
- "required": [
- "addresses"
- ]
- },
- {
- "required": [
- "addressRange"
- ]
- }
- ],
- "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. If the Cp instance represents a subport in a trunk, segmentationId shall be present. Otherwise it shall not be present. 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": "string"
- },
- "ipAddresses": {
- "description": "Addresses assigned to the CP instance. Each entry represents IP addresses assigned by fixed or dynamic IP address assignment per subnet. At least one of \"macAddress\" or \"ipAddresses\" shall be present.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": [
- "type"
- ],
- "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). Exactly one of \"addresses\" or \"addressRange\" 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"
- }
- },
- "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.\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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- }
- }
- }
- }
- }
- }
- }
- }
- },
- "extLinkPortId": {
- "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 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"
- },
- "associatedVnfcCpId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "associatedVnfVirtualLinkId": {
- "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": {
- "type": "object",
- "required": [
- "id",
- "resourceHandle",
- "currentVnfExtCpData"
- ],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceHandle": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\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.\n",
- "type": "object",
- "required": [
- "id",
- "resourceHandle"
- ],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceHandle": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\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"
- }
- }
- }
- },
- "currentVnfExtCpData": {
- "description": "Allows the API consumer to read the current CP configuration information for the connection of external CPs to the external virtual link. This attribute reflects the current configuration information that has resulted from merging into this attribute the \"VnfExtCpData\" information which was passed as part of the \"ExtVirtualLinkData\" structure in the input of the most recent VNF LCM operation such as \"InstantiateVnfRequest\", \"ChangeExtVnfConnectivityRequest\", \"ChangeVnfFlavourRequest\" or \"ChangeCurrentVnfPkgRequest\", or has been provided by the NFVO during the granting procedure. If applying such change results in an empty list of \"currentVnfExtCpData\" structure instances, the affected instance of \"ExtVirtualLinkInfo\" shall be removed from its parent data structure.\n",
- "type": "array",
- "items": {
- "description": "This type represents configuration information for external CPs created from a CPD.\n",
- "type": "object",
- "required": [
- "cpdId"
- ],
- "properties": {
- "cpdId": {
- "description": "An identifier that is unique within a VNF descriptor.\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 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). 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. 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.\n",
- "type": "object",
- "additionalProperties": {
- "description": "This type represents an externally provided link port or network address information per instance of an external connection point. In case a link port is provided, the VNFM shall use that link port when connecting the external CP to the external VL. In a link port is not provided, the VNFM shall create a link port on the external VL, and use that link port to connect the external CP to the external VL.\n",
- "anyOf": [{
- "required": [
- "linkPortId"
- ]
- },
- {
- "required": [
- "cpProtocolData"
- ]
- }
- ],
- "type": "object",
- "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"
- },
- "cpProtocolData": {
- "description": "Parameters for configuring the network protocols on the link port that connects the CP to a VL. The following conditions apply to the attributes \"linkPortId\" and \"cpProtocolData\": 1) Void 2) At least one of the \"linkPortId\" and \"cpProtocolData\" attributes \n shall be present for an external CP instance representing a subport \n that is to be created, or an external CP instance that is to be created \n by creating the corresponding VNFC or VNF instance during the current or \n a subsequent LCM operation, or for an existing external CP instance \n that is to be re-configured or added to a particular external virtual link.\n3) If the \"linkPortId\" attribute is absent, the VNFM shall create a\n link port.\n4) If the \"cpProtocolData\" attribute is absent, the \"linkPortId\"\n attribute shall be provided referencing a pre-created link port,\n and the VNFM can use means outside the scope of the present\n document to obtain the pre-configured address information for the\n connection point from the resource representing the link port.\n5) If both \"cpProtocolData\" and \"linkportId\" are provided, the API\n consumer shall ensure that the cpProtocolData can be used with the\n pre-created link port referenced by \"linkPortId\".\n",
- "type": "array",
- "items": {
- "description": "This type represents network protocol data.\n",
- "type": "object",
- "required": [
- "layerProtocol"
- ],
- "properties": {
- "layerProtocol": {
- "description": "Identifier of layer(s) and protocol(s). 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": "string",
- "enum": [
- "IP_OVER_ETHERNET"
- ]
- },
- "ipOverEthernet": {
- "description": "This type represents network address data for IP over Ethernet.\n",
- "type": "object",
- "anyOf": [{
- "required": [
- "macAddress"
- ]
- },
- {
- "required": [
- "ipAddresses"
- ]
- }
- ],
- "oneOf": [{
- "required": [
- "fixedAddresses"
- ]
- },
- {
- "required": [
- "numDynamicAddresses"
- ]
- },
- {
- "required": [
- "ipAddressRange"
- ]
- }
- ],
- "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. If the Cp instance represents a subport in a trunk, segmentationId shall be present. Otherwise it shall not be present. 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": "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.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": [
- "type"
- ],
- "properties": {
- "type": {
- "description": "The type of the IP addresses. Permitted values: IPV4, 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). Exactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present.\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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- },
- "extManagedVirtualLinkInfo": {
- "description": "Information about the externally-managed internal VLs of the VNF instance.\nNOTE: 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 VNF internal VL shall indicate so by referencing to the same VnfVirtualLinkDesc and externally-managed multi-site VL instance (refer to clause 5.5.3.3).\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": [
- "id",
- "vnfVirtualLinkDescId",
- "networkResource"
- ],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfVirtualLinkDescId": {
- "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"
- },
- "networkResource": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
- "type": "string"
- }
- }
- },
- "vnfLinkPorts": {
- "description": "Link ports of this VL.\n",
- "type": "array",
- "items": {
- "type": "object",
- "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": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\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.\n",
- "type": "string",
- "enum": [
- "VNFC_CP",
- "EXT_CP"
- ]
- }
- }
- }
- },
- "extManagedMultisiteVirtualLinkId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- }
- }
- }
- },
- "monitoringParameters": {
- "description": "Active monitoring parameters.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": [
- "id",
- "performanceMetric"
- ],
- "properties": {
- "id": {
- "description": "An identifier that is unique within a VNF descriptor.\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.\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"
- },
- "vduId": {
- "description": "An identifier that is unique within a VNF descriptor.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "computeResource": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
- "type": "string"
- }
- }
- },
- "zoneId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "storageResourceIds": {
- "description": "References to the VirtualStorage resources. 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": "All the 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. 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. 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 VNF descriptor.\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. The information can be omitted because it is already available as part of the external CP information.\n",
- "type": "array",
- "items": {
- "description": "This type describes the protocol layer(s) that a CP uses together with protocol-related information, like addresses.\n",
- "type": "object",
- "required": [
- "layerProtocol"
- ],
- "properties": {
- "layerProtocol": {
- "description": "The identifier of layer(s) and protocol(s) associated to the network address information. Permitted values: IP_OVER_ETHERNET 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": "string",
- "enum": [
- "IP_OVER_ETHERNET"
- ]
- },
- "ipOverEthernet": {
- "description": "This type represents information about a network address that has been assigned.\n",
- "type": "object",
- "anyOf": [{
- "required": [
- "macAddress"
- ]
- },
- {
- "required": [
- "ipAddresses"
- ]
- }
- ],
- "oneOf": [{
- "required": [
- "addresses"
- ]
- },
- {
- "required": [
- "addressRange"
- ]
- }
- ],
- "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. If the Cp instance represents a subport in a trunk, segmentationId shall be present. Otherwise it shall not be present. 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": "string"
- },
- "ipAddresses": {
- "description": "Addresses assigned to the CP instance. Each entry represents IP addresses assigned by fixed or dynamic IP address assignment per subnet. At least one of \"macAddress\" or \"ipAddresses\" shall be present.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": [
- "type"
- ],
- "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). Exactly one of \"addresses\" or \"addressRange\" 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"
- }
- },
- "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.\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 other resource provider. It is expected to be unique within the VIM instance.\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": "This 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"
- }
- }
- }
- },
- "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 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"
- }
- }
- }
- },
- "virtualLinkResourceInfo": {
- "description": "Information about the virtualised network resources used by the VLs of the VNF instance.\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"
- },
- "vnfVirtualLinkDescId": {
- "description": "An identifier that is unique within a VNF descriptor.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "networkResource": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
- "type": "string"
- }
- }
- },
- "zoneId": {
- "description": "An identifier with the intention of being globally unique.\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",
- "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": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\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.\n",
- "type": "string",
- "enum": [
- "VNFC_CP",
- "EXT_CP"
- ]
- }
- }
- }
- },
- "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 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"
- }
- }
- }
- },
- "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": "An identifier that is unique within a VNF descriptor.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "storageResource": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
- "type": "string"
- }
- }
- },
- "zoneId": {
- "description": "An identifier with the intention of being globally unique.\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 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"
- }
- }
- }
- }
- }
- },
- "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 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"
- },
- "extensions": {
- "description": "Additional VNF-specific attributes that affect the lifecycle management of this VNF instance. These attributes represent values that are stored persistently in the VnfInstance structure for consumption by the VNFM or the lifecycle management scripts during the execution of VNF lifecycle management operations. All extensions that are allowed for the VNF are declared in the VNFD. The declaration of an extension in the VNFD contains information on whether its presence is optional or required, and optionally can specify an initial value. See note 2 and note 4. The VNFM shall reject requests to write extension attributes that are not declared in the VNFD with a \"422 Unprocessable entity\" error response as defined in clause 6.4 of ETSI GS NFV-SOL 013. Modifying the values of these attributes has no direct effect on the VNF instance; however, the modified attribute values can be considered during subsequent VNF lifecycle management operations, which means that the modified values can indirectly affect the configuration of the VNF instance. These attributes can be initialized with default values from the VNFD. These attributes can be modified with values passed in the request structures of certain LCM operations, such as the InstantiateVnfRequest structure. Further, these attributes can be created, modified or deleted with the PATCH method.\nNOTE: Upon creation of the VnfInstance structure, the VNFM shall create and initialize all child attributes of \"vnfConfigurableProperties\", \"metadata\" and \"extensions\" that were declared in the VNFD with a defined initial value. The defined initial values can be declared in the VNFD, and/or, in case of \"metadata\", obtained from the \"CreateVnfRequest\" structure. Child attributes of \"vnfConfigurableProperties\", \"metadata\" and \"extensions\" that have no defineddeclared initial value shall not be created, in order to be consistent with the semantics of the JSON Merge Patch method (see IETF RFC 7396) that interprets null values as deletion request.\n"
- },
- "_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 using an absolute URI.\n",
- "type": "object",
- "required": [
- "href"
- ],
- "properties": {
- "href": {
- "description": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- }
- }
- },
- "indicators": {
- "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"
- }
- }
- },
- "instantiate": {
- "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"
- }
- }
- },
- "terminate": {
- "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"
- }
- }
- },
- "scale": {
- "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"
- }
- }
- },
- "scaleToLevel": {
- "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"
- }
- }
- },
- "changeFlavour": {
- "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"
- }
- }
- },
- "heal": {
- "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"
- }
- }
- },
- "operate": {
- "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"
- }
- }
- },
- "changeExtConn": {
- "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"
- }
- }
- },
- "createSnapshot": {
- "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"
- }
- }
- },
- "revertToSnapshot": {
- "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"
- }
- }
- }
- }
- }
- }
- },
- "vnfcSnapshots": {
- "description": "Information about VNFC snapshots constituting this VNF snapshot.\n",
- "type": "array",
- "items": {
- "description": "This type represents a VNFC snapshot.\n",
- "type": "object",
- "required": [
- "id",
- "vnfcInstanceId",
- "triggeredAt",
- "vnfcResourceId"
- ],
- "properties": {
- "id": {
- "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\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 to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "creationFinishedAt": {
- "description": "Date-time stamp. Representation: String formatted according to 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": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
- "type": "string"
- }
- }
- },
- "storageSnapshotResources": {
- "description": "Mapping of the storage resources associated to the VNFC with the storage snapshot resources.\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"
- },
- "storageSnapshotResource": {
- "description": "This 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"
- }
- }
- }
- },
- "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 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"
- }
- }
- }
- },
- "vnfStateSnapshotInfo": {
- "description": "This type represents information about VNF-specific state snapshot data.\n",
- "type": "object",
- "required": [
- "checksum",
- "isEncrypted"
- ],
- "properties": {
- "checksum": {
- "description": "Checksum of the VNF state snapshot file. Hash algorithms applicable to VNF snapshot package artifacts are defined in ETSI GS NFV-SOL 010. $ref: \"../definitions/SOL002SOL003_def.yaml#/definitions/Checksum\"\n"
- },
- "isEncrypted": {
- "description": "Reflects whether the VNF state snapshot content is encrypted (true) or not (false). $ref: \"../definitions/SOL002SOL003_def.yaml#/definitions/Boolean\"\n"
- },
- "metadata": {
- "description": "The metadata with additional information such as content type, size, creation date, etc. $ref: \"../definitions/SOL002SOL003_def.yaml#/definitions/KeyValuePairs\"\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 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"
- },
- "_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 using an absolute URI.\n",
- "type": "object",
- "required": [
- "href"
- ],
- "properties": {
- "href": {
- "description": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- }
- }
- },
- "vnfStateSnapshot": {
- "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"
- }
- }
- }
- }
- }
- }
- },
- "_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 using an absolute URI.\n",
- "type": "object",
- "required": [
- "href"
- ],
- "properties": {
- "href": {
- "description": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- }
- }
- },
- "takenFrom": {
- "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"
- }
- }
- }
- }
- }
- }
+ "description": "This type represents an \"Individual VNF snapshot\" resource.\n",
+ "type": "object",
+ "required": ["id", "_links"],
+ "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.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "vnfInstanceId",
+ "triggeredAt",
+ "vnfdId",
+ "vnfInfo",
+ "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",
+ "type": "string"
+ },
+ "creationStartedAt": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "creationFinishedAt": {
+ "description": "Date-time stamp. Representation: String formatted according to 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.\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",
+ "type": "object",
+ "required": [
+ "id",
+ "vnfdId",
+ "vnfProvider",
+ "vnfProductName",
+ "vnfSoftwareVersion",
+ "vnfdVersion",
+ "instantiationState",
+ "_links"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfInstanceName": {
+ "description": "Name of the VNF instance. This attribute can be modified with the PATCH method.\n",
+ "type": "string"
+ },
+ "vnfInstanceDescription": {
+ "description": "Human-readable description of the VNF instance. This attribute can be modified with the PATCH method.\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.\n",
+ "type": "string"
+ },
+ "vnfdVersion": {
+ "description": "A version.\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 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"
+ },
+ "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",
+ "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",
+ "type": "object",
+ "required": ["vimType"],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vimType": {
+ "description": "Discriminator for the different types of the VIM information. The value of this attribute determines the structure of the \"interfaceInfo\" and \"accessInfo\" attributes, based on the type of the VIM., CISM, CIR or MCIOP repository. The set of permitted values is expected to change over time as new types or versions of VIMs become available. The ETSI NFV registry of VIM-related information [i.3] provides access to information about VimConnectionInfo definitions for various VIM, CISM, CIR or MCIOP repository types. The structure of the registry is defined in annex C.\n",
+ "type": "string"
+ },
+ "interfaceInfo": {
+ "description": "This 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"
+ },
+ "accessInfo": {
+ "description": "This 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"
+ },
+ "extra": {
+ "description": "This 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"
+ }
+ }
+ }
+ },
+ "cirConnectionInfo": {
+ "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",
+ "type": "object",
+ "required": ["vimType"],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vimType": {
+ "description": "Discriminator for the different types of the VIM information. The value of this attribute determines the structure of the \"interfaceInfo\" and \"accessInfo\" attributes, based on the type of the VIM., CISM, CIR or MCIOP repository. The set of permitted values is expected to change over time as new types or versions of VIMs become available. The ETSI NFV registry of VIM-related information [i.3] provides access to information about VimConnectionInfo definitions for various VIM, CISM, CIR or MCIOP repository types. The structure of the registry is defined in annex C.\n",
+ "type": "string"
+ },
+ "interfaceInfo": {
+ "description": "This 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"
+ },
+ "accessInfo": {
+ "description": "This 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"
+ },
+ "extra": {
+ "description": "This 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"
+ }
+ }
+ }
+ },
+ "mciopRepositoryInfo": {
+ "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",
+ "type": "object",
+ "required": ["vimType"],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vimType": {
+ "description": "Discriminator for the different types of the VIM information. The value of this attribute determines the structure of the \"interfaceInfo\" and \"accessInfo\" attributes, based on the type of the VIM., CISM, CIR or MCIOP repository. The set of permitted values is expected to change over time as new types or versions of VIMs become available. The ETSI NFV registry of VIM-related information [i.3] provides access to information about VimConnectionInfo definitions for various VIM, CISM, CIR or MCIOP repository types. The structure of the registry is defined in annex C.\n",
+ "type": "string"
+ },
+ "interfaceInfo": {
+ "description": "This 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"
+ },
+ "accessInfo": {
+ "description": "This 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"
+ },
+ "extra": {
+ "description": "This 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"
+ }
+ }
+ }
+ },
+ "instantiationState": {
+ "description": "The instantiation state of the VNF. Permitted 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": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "vnfState": {
+ "description": "STARTED: The VNF instance is up and running. STOPPED: The VNF instance has been shut down.\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. This attribute shall be present if the VNF supports scaling. See clause B.2 for an explanation of VNF scaling.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the scale level of a VNF instance related to a scaling aspect.\n",
+ "type": "object",
+ "required": ["aspectId", "scaleLevel"],
+ "properties": {
+ "aspectId": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "scaleToLevel": {
+ "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": {
+ "description": "This type represents the scale level of a VNF instance related to a scaling aspect.\n",
+ "type": "object",
+ "required": ["aspectId", "scaleLevel"],
+ "properties": {
+ "aspectId": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "scaleToLevel": {
+ "description": "An identifier with the intention of being globally unique.\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.\nNOTE 1:\tThe attributes \"associatedVnfcCpId\", \"associatedVipCpId\", \"associatedVirtualCpId\" and \n \"associatedVnfVirtualLinkId\" are mutually exclusive. Exactly one shall be present.\nNOTE 2:\tAn external CP instance is not associated to a link port in the cases indicated for the \n “extLinkPorts†attribute in clause 4.4.1.11.\nNOTE 3: 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 \n CP, e.g. to build a link redundant mated pair in SR-IOV cases.\nNOTE 4: When more than one netAttDefResourceId is indicated, all shall belong to the same namespace.\n",
+ "type": "object",
+ "required": ["id", "cpdId", "cpConfigId", "cpProtocolInfo"],
+ "oneOf": [
+ {
+ "required": ["associatedVnfcCpId"]
+ },
+ {
+ "required": ["associatedVipCpId"]
+ },
+ {
+ "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": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "cpConfigId": {
+ "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"
+ },
+ "cpProtocolInfo": {
+ "description": "Network protocol information for this CP.\n",
+ "type": "array",
+ "items": {
+ "description": "This type describes the protocol layer(s) that a CP uses together with protocol-related information, like addresses.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the \n present document in a backwards-compatible way. In the current version of the present document, only IP over \n Ethernet is supported.\n",
+ "type": "object",
+ "required": ["layerProtocol"],
+ "properties": {
+ "layerProtocol": {
+ "description": "The identifier of layer(s) and protocol(s) associated to the network address information.\nPermitted 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:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, segmentationId shall be present. \n Otherwise it shall not be present.\nNOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the \n actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the \n transport header of the packets or it may be an identifier used between the application \n and the NFVI networking infrastructure to identify the network sub-interface of the trunk \n port in question. In the latter case the NFVI infrastructure will map this local segmentationId \n to whatever segmentationId is actually used by the NFVI’s transport technology.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "required": ["macAddress"]
+ },
+ {
+ "required": ["ipAddresses"]
+ }
+ ],
+ "oneOf": [
+ {
+ "required": ["addresses"]
+ },
+ {
+ "required": ["addressRange"]
+ }
+ ],
+ "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 notes 3 and 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"],
+ "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. 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.\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"
+ },
+ "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 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"
+ },
+ "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"
+ },
+ "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 with the intention of being 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",
+ "minItems": 1,
+ "items": {
+ "description": "This type provides information related to virtual IP (VIP) CP.\nNOTE 1:\tIt is possible that there is no associated VnfcCp because the VIP CP is available but not associated yet. NOTE 2: If only the value or the presence of this attribute is changed in the \"VipCpInfo\" structure by an LCM operation occurrence, this does not represent a change that requires including a related \"AffectedVipCp\" structure in the VNF LCM operation occurrence notifications or the \"VnfLcmOpOcc\" structure related to this LCM operation occurrence.\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": "An identifier that is unique within a VNF descriptor.\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 uses together with protocol-related information, like addresses.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the \n present document in a backwards-compatible way. In the current version of the present document, only IP over \n Ethernet is supported.\n",
+ "type": "object",
+ "required": ["layerProtocol"],
+ "properties": {
+ "layerProtocol": {
+ "description": "The identifier of layer(s) and protocol(s) associated to the network address information.\nPermitted 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:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, segmentationId shall be present. \n Otherwise it shall not be present.\nNOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the \n actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the \n transport header of the packets or it may be an identifier used between the application \n and the NFVI networking infrastructure to identify the network sub-interface of the trunk \n port in question. In the latter case the NFVI infrastructure will map this local segmentationId \n to whatever segmentationId is actually used by the NFVI’s transport technology.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "required": ["macAddress"]
+ },
+ {
+ "required": ["ipAddresses"]
+ }
+ ],
+ "oneOf": [
+ {
+ "required": ["addresses"]
+ },
+ {
+ "required": ["addressRange"]
+ }
+ ],
+ "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 notes 3 and 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"],
+ "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. 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.\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": "This 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"
+ }
+ }
+ }
+ },
+ "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 provides information related to a virtual CP instance of a VNF.\nNOTE: A consumer of the VNF LCM interface can learn the actual VNFC instances implementing the service \n accessible via the virtual CP instance by querying the \"vnfcResourceInfo\" from the \"InstantiatedVnfInfo\" \n and filtering by corresponding \"vduIds\" values.\n",
+ "type": "object",
+ "required": [
+ "cpInstanceId",
+ "cpdId",
+ "resourceHandle",
+ "vduIds"
+ ],
+ "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": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "resourceHandle": {
+ "required": ["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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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 uses together with protocol-related information, like addresses.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the \n present document in a backwards-compatible way. In the current version of the present document, only IP over \n Ethernet is supported.\n",
+ "type": "object",
+ "required": ["layerProtocol"],
+ "properties": {
+ "layerProtocol": {
+ "description": "The identifier of layer(s) and protocol(s) associated to the network address information.\nPermitted 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:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, segmentationId shall be present. \n Otherwise it shall not be present.\nNOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the \n actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the \n transport header of the packets or it may be an identifier used between the application \n and the NFVI networking infrastructure to identify the network sub-interface of the trunk \n port in question. In the latter case the NFVI infrastructure will map this local segmentationId \n to whatever segmentationId is actually used by the NFVI’s transport technology.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "required": ["macAddress"]
+ },
+ {
+ "required": ["ipAddresses"]
+ }
+ ],
+ "oneOf": [
+ {
+ "required": ["addresses"]
+ },
+ {
+ "required": ["addressRange"]
+ }
+ ],
+ "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 notes 3 and 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"],
+ "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. 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.\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"
+ }
+ }
+ }
+ }
+ }
+ },
+ "vduIds": {
+ "description": "Reference to the VDU(s) which implement the service accessible via the virtual CP instance. See note.\n",
+ "type": "array",
+ "minItems": 1,
+ "items": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ }
+ },
+ "additionalServiceInfo": {
+ "description": "Additional service identification information of the virtual CP instance.\n",
+ "type": "array",
+ "items": {
+ "description": "This type provides 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 \n termination within the VNF, such as for example a URL path information in an HTTP request required \n to allow a single virtual CP IP address to be used for several HTTP based services that use the \n same port number.\n",
+ "type": "object",
+ "required": ["portInfo"],
+ "properties": {
+ "portInfo": {
+ "description": "Service port numbers exposed by the virtual CP instance.\n",
+ "minItems": 1,
+ "type": "array",
+ "items": {
+ "description": "This type describes the service identifying port properties exposed by the virtual CP instance.\n",
+ "type": "object",
+ "required": [
+ "name",
+ "port",
+ "portConfigurable"
+ ],
+ "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.\nPermitted values: - TCP - UDP - SCTP\n",
+ "type": "string",
+ "enum": ["TCP", "UDP", "SCTP"]
+ },
+ "port": {
+ "description": "The L4 port number exposed by the virtual CP instance.\n",
+ "type": "integer"
+ },
+ "portConfigurable": {
+ "description": "The Boolean is a data type having two values (true and false).\n",
+ "type": "boolean"
+ }
+ }
+ }
+ },
+ "serviceInfo": {
+ "description": "This 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"
+ }
+ }
+ }
+ },
+ "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 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"
+ }
+ }
+ }
+ },
+ "extVirtualLinkInfo": {
+ "description": "Information about the external VLs the VNF instance is connected to.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents information about an external VL.\nNOTE:\tThis attribute reflects the current configuration information that has resulted from merging into this attribute \n the \"VnfExtCpData\" information which was passed as part of the \"ExtVirtualLinkData\" structure in the input of the \n most recent VNF LCM operation such as \"InstantiateVnfRequest\", \"ChangeExtVnfConnectivityRequest\", \"ChangeVnfFlavourRequest\" \n or \"ChangeCurrentVnfPkgRequest\", or in the Grant response. If applying such change results in an empty list of \n \"currentVnfExtCpData\" structure instances, the affected instance of \"ExtVirtualLinkInfo\" shall be removed from its \n parent data structure.\n",
+ "type": "object",
+ "required": ["id", "resourceHandle", "currentVnfExtCpData"],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceHandle": {
+ "required": ["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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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.\nNOTE 1:\tThe use cases UC#4 and UC#5 in clause A.4 of ETSI GS NFV-IFA 007 provide examples for such a configuration. NOTE 2:\tThe 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": {
+ "required": ["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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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 the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "currentVnfExtCpData": {
+ "description": "Allows the API consumer to read the current CP configuration information for the connection of external CPs to the external virtual link. See note.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents configuration information for external CPs created. * NOTE 1: \tIn case this identifier refers to a CPD with trunking enabled, the external CP instances created\n from this CPD will represent ports in a trunk.\n* NOTE 2: \tWithin one VNF instance, all VNFC instances created from a particular VDU have the same external\n connectivity. Thus, given a particular value of the \"cpdId\" attribute, there shall be one\n \"cpConfig\" entry for each VNFC instance that has been or can be created from a VDU which includes\n a CPD identified by the \"cpdId\" attribute. If the cpConfig represents a subport in a trunk,\n all \"cpConfig\" entries in this list shall have the same segmentationId, which means they are\n connected to the same set of external VLs via the trunk.\n* NOTE 3: \tThe map entry value shall be set to \"null\" in order to delete a \"VnfExtCpConfig\" entry identified\n by a particular key value from the map, i.e. for the disconnection of an existing external\n CP instance addressed by cpInstanceId in the deleted map entry from a particular external\n virtual link, and deletion of that instance in case it represents a subport. Deleting the\n last key from the map removes the affected instance of the \"VnfExtCpData\" structure from\n its parent data structure.\n* NOTE 4: If, as defined by the input parameters of a \"ChangeVnfFlavour\", \"ChangeExtVnfConnectivity\" or\n \"ChangeCurrentVnfPkg\" operation or as part of the Grant response for any of these operations, a cpConfig\n map entry identified by a particular map key value is moved into another \"ExtVirtualLinkData\" or\n \"VnfExtCpData\" structure, this particular cpConfig map entry may be used by an external CP instance\n different than the one that has used it before the operation, or by no external CP instance at all.\n Renaming a CPD identifier during the \"changeCurrentVnfPkg\" operation does not count as moving the related\n \"cpConfig\" map entries to a new \"extCpData\" structure.\n",
+ "type": "object",
+ "required": ["cpdId"],
+ "properties": {
+ "cpdId": {
+ "description": "An identifier that is unique within a VNF descriptor.\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 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",
+ "anyOf": [
+ {
+ "required": ["linkPortId"]
+ },
+ {
+ "required": ["cpProtocolData"]
+ },
+ {
+ "required": ["netAttDefResourceId"]
+ }
+ ],
+ "type": "object",
+ "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 to the VNFM the need to create a dedicated link port for the external CP. If set to True, the VNFM shall create a link port. If set to False, the VNFM shall not create a link port. 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"
+ },
+ "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 2, 3 and 4.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ },
+ "cpProtocolData": {
+ "description": "Parameters for configuring the network protocols on the link port that connects the CP to a VL. See notes 1 and 2.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents network protocol data. * NOTE:\tThis attribute allows to signal the addition of further types of layer and protocol\n in future versions of the present document in a backwards-compatible way. In the current\n 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:\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 network address data for IP over Ethernet. * NOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. * NOTE 2:\tExactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present. * NOTE 3:\tIf the CP instance represents a subport in a trunk, segmentationId shall be present.\n Otherwise it shall not be present.\n* NOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the actual\n network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header\n of the packets or it may be an identifier used between the application and the NFVI networking\n infrastructure to identify the network sub-interface of the trunk port in question. In the latter\n case the NFVI infrastructure will map this local segmentationId to whatever segmentationId is\n actually used by the NFVI’s transport technology.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "required": ["macAddress"]
+ },
+ {
+ "required": ["ipAddresses"]
+ }
+ ],
+ "oneOf": [
+ {
+ "required": ["fixedAddresses"]
+ },
+ {
+ "required": [
+ "numDynamicAddresses"
+ ]
+ },
+ {
+ "required": ["ipAddressRange"]
+ }
+ ],
+ "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: -\tVLAN: the subport uses VLAN as encapsulation type. -\tINHERIT: the subport gets its segmentation type from the network it’s 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"],
+ "properties": {
+ "type": {
+ "description": "The type of the IP addresses. Permitted values: IPV4, IPV6.\n",
+ "type": "string",
+ "enum": ["IPV4", "IPV6"]
+ },
+ "fixedAddresses": {
+ "description": "Fixed addresses to assign (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"
+ }
+ },
+ "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. 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.\n",
+ "type": "string"
+ }
+ }
+ }
+ }
+ }
+ },
+ "virtualCpAddress": {
+ "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",
+ "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"
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ },
+ "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 contains 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": {
+ "required": ["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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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 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 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"
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ },
+ "extManagedVirtualLinkInfo": {
+ "description": "Information about the externally-managed internal VLs of the VNF instance. See notes 5 and 6.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": [
+ "id",
+ "vnfVirtualLinkDescId",
+ "networkResource"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfVirtualLinkDescId": {
+ "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"
+ },
+ "networkResource": {
+ "required": ["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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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": {
+ "description": "This type represents a link port of an internal VL of a VNF.\nNOTE 1: Either cpInstanceId with cpInstanceType set to \"EXT_CP\" or any combination of cpInstanceId\n with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId (i.e. one or both of them) shall be \n present for a VnfLinkPortInfo. In case both cpInstanceId with cpInstanceType set to \"VNFC_CP\" \n and vipCpInstanceId are present, the two different CP instances share the linkport.\nNOTE 2: Annex A.4 of ETSI GS NFV-IFA 007 provides examples for configurations where both vipCpInstanceId\n and vnfcCpInstanceId are present (UC#5 and UC#5-b), only vnfcCpInstanceId is present (UC#2), or \n only vipCpInstanceId is present (UC6 and UC#6-b).\nNOTE 3: The value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\"\n attribute.\n",
+ "type": "object",
+ "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": {
+ "required": ["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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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.\nPermitted values: - VNFC_CP: The link port is connected to a VNFC CP. -\tEXT_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 the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "vnfNetAttDefResource": {
+ "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 contains 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": {
+ "required": ["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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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 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 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": "Active monitoring parameters.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": ["id", "performanceMetric"],
+ "properties": {
+ "id": {
+ "description": "An identifier that is unique within a VNF descriptor.\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. Depending on the form of virtualisation container of the VNFC:\n - For a VNFC based on VM, a reference to the corresponding VirtualCompute shall be provided, and\n - For a VNFC based on OS container(s), a reference to the Compute MCIO shall be provided. Hence, exposure of\n information by the VNFM to the NFVO is at the MCIO level.\nIn addition, the references to the storage resources depend on the form of the VNFC:\n a) For a VNFC based on VM, storage resource identifiers shall refer to VirtualStorage resources, and\n b) For a VNFC based on OS container(s), storage resource identifiers shall refer to Storage MCIOs.\n\nNOTE 1:\tETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on \n TOSCA specifications.\nNOTE 2:\tA VNFC CP is \"connected to\" an external CP if the VNFC CP is connected to an \n internal VL that exposes an external CP. A VNFC CP is \"exposed as\" an external \n CP if it is connected directly to an external VL.\nNOTE 3:\tThe information can be omitted because it is already available as part of the \n external CP information.\nNOTE 4: If only the value or the presence of this attribute is changed in the \"VnfcResourceInfo\"\n structure by an LCM operation occurrence, this does not represent a change that requires\n including a related \"AffectedVnfc\" structure in the VNF LCM operation occurrence notifications\n or the \"VnfLcmOpOcc\" structure related to this LCM operation occurrence.\nNOTE 5: 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 internal CP, e.g. to build a link\n redundant mated pair in SR-IOV cases.\nNOTE 6: 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"
+ },
+ "vduId": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "computeResource": {
+ "required": ["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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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"
+ }
+ }
+ },
+ "zoneId": {
+ "description": "An identifier with the intention of being globally unique.\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 VNF descriptor.\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 uses together with protocol-related information, like addresses.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the \n present document in a backwards-compatible way. In the current version of the present document, only IP over \n Ethernet is supported.\n",
+ "type": "object",
+ "required": ["layerProtocol"],
+ "properties": {
+ "layerProtocol": {
+ "description": "The identifier of layer(s) and protocol(s) associated to the network address information.\nPermitted 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:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, segmentationId shall be present. \n Otherwise it shall not be present.\nNOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the \n actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the \n transport header of the packets or it may be an identifier used between the application \n and the NFVI networking infrastructure to identify the network sub-interface of the trunk \n port in question. In the latter case the NFVI infrastructure will map this local segmentationId \n to whatever segmentationId is actually used by the NFVI’s transport technology.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "required": ["macAddress"]
+ },
+ {
+ "required": ["ipAddresses"]
+ }
+ ],
+ "oneOf": [
+ {
+ "required": ["addresses"]
+ },
+ {
+ "required": ["addressRange"]
+ }
+ ],
+ "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 notes 3 and 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"],
+ "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. 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.\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"
+ }
+ }
+ }
+ }
+ }
+ },
+ "vnfLinkPortId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "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"
+ },
+ "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 5 and 6. 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 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 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"
+ }
+ }
+ }
+ },
+ "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 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"
+ }
+ }
+ }
+ },
+ "vnfVirtualLinkResourceInfo": {
+ "description": "Information about the virtualised network resources used by the VLs of the VNF instance. See note 6.\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.\nNote: If only the value or the presence of this attribute is changed in the \"VnfVirtualLinkResourceInfo\"\n structure by an LCM operation occurrence, this does not represent a change that requires including\n a related \"AffectedVirtualLink\" structure in the VNF LCM operation occurrence notifications or the\n \"VnfLcmOpOcc\" structure related to this LCM operation occurrence.\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"
+ },
+ "vnfVirtualLinkDescId": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "networkResource": {
+ "required": ["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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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"
+ }
+ }
+ },
+ "zoneId": {
+ "description": "An identifier with the intention of being globally unique.\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": {
+ "description": "This type represents a link port of an internal VL of a VNF.\nNOTE 1: Either cpInstanceId with cpInstanceType set to \"EXT_CP\" or any combination of cpInstanceId\n with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId (i.e. one or both of them) shall be \n present for a VnfLinkPortInfo. In case both cpInstanceId with cpInstanceType set to \"VNFC_CP\" \n and vipCpInstanceId are present, the two different CP instances share the linkport.\nNOTE 2: Annex A.4 of ETSI GS NFV-IFA 007 provides examples for configurations where both vipCpInstanceId\n and vnfcCpInstanceId are present (UC#5 and UC#5-b), only vnfcCpInstanceId is present (UC#2), or \n only vipCpInstanceId is present (UC6 and UC#6-b).\nNOTE 3: The value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\"\n attribute.\n",
+ "type": "object",
+ "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": {
+ "required": ["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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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.\nPermitted values: - VNFC_CP: The link port is connected to a VNFC CP. -\tEXT_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 the CISM or other resource provider. It is expected to be unique within the VIM instance.\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 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"
+ }
+ }
+ }
+ },
+ "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.\nNote: If only the value or the presence of this attribute is changed in the \"VirtualStorageResourceInfo\"\n structure by an LCM operation occurrence, this does not represent a change that requires\n including a related \"AffectedVirtualStorage\" structure in the VNF LCM operation occurrence\n notifications or the \"VnfLcmOpOcc\" structure related to this LCM operation occurrence.\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": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "storageResource": {
+ "required": ["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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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"
+ }
+ }
+ },
+ "zoneId": {
+ "description": "An identifier with the intention of being globally unique.\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 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"
+ }
+ }
+ }
+ },
+ "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. Within the CISM, an MCIO controller monitors the actual state of an MCIO representing the set of VNFC instances realized by one or a set of OS containers and compare it to the desired state as specified in the respective declarative descriptor. It triggers actions toward the CIS to align the actual to the desired state. Monitoring the actual state includes monitoring the number of MCIO instances available at any specific point in time. In addition, an MCIO controller maintains properties and runtime information on the MCIO instances which have been created based on the same VDU. The McioInfo data structure provides the runtime information on the MCIOs obtained from the MCIO controller.\nNOTE: There are different types of MCIOs. The set of VNFC instances based on the same VDU is represented \n by one MCIO, e.g. of type Deployment. Each individual VNFC instance is represented by another type \n of MCIO, e.g. a POD.\n\nRuntime information of the set of OS containers realizing an individual VNFC instance is not part of the McioInfo data structure; such runtime information is provided in the ResourceHandle data structure referenced from the VnfcResourceInfo. The McioInfo does not provide runtime information of a constituent VNFC instance created based on a specific VDU.\nNOTE 1: The type of MCIO as specified in the declarative descriptor of the MCIO, and that can be read from \n the CISM. EXAMPLE: In case of MCIOs managed by Kubernetes®, the type of MCIO corresponds to the \n “kind†property of the declarative descriptor.\nNOTE 2: If the attribute additionalInfo is present, it may contain runtime information on the actual and \n desired state of the MCIO(s). \nNOTE 3: When the container infrastructure service is a Kubernetes® instance, the mcioId is the combined \n values from the kind and name fields of the Kubernetes resource object, separated by a slash. \n Example: \"Deployment/abcd\". \nNOTE 4: When the container infrastructure service is a Kubernetes® instance, the mcioName is the name \n field of the resource object. \n",
+ "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": "An identifier that is unique within a VNF descriptor.\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 5.5.4.9. Additional values are also permitted. See note 1.\n",
+ "type": "string",
+ "enum": ["Deployment", "Statefulset"]
+ },
+ "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 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"
+ }
+ }
+ }
+ }
+ }
+ },
+ "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 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"
+ },
+ "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 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"
+ },
+ "_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 using an absolute URI.\n",
+ "type": "object",
+ "required": ["href"],
+ "properties": {
+ "href": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ }
+ }
+ },
+ "indicators": {
+ "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"
+ }
+ }
+ },
+ "instantiate": {
+ "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"
+ }
+ }
+ },
+ "terminate": {
+ "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"
+ }
+ }
+ },
+ "scale": {
+ "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"
+ }
+ }
+ },
+ "scaleToLevel": {
+ "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"
+ }
+ }
+ },
+ "changeFlavour": {
+ "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"
+ }
+ }
+ },
+ "heal": {
+ "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"
+ }
+ }
+ },
+ "operate": {
+ "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"
+ }
+ }
+ },
+ "changeExtConn": {
+ "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"
+ }
+ }
+ },
+ "createSnapshot": {
+ "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"
+ }
+ }
+ },
+ "revertToSnapshot": {
+ "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"
+ }
+ }
+ },
+ "changeCurrentVnfPkg": {
+ "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"
+ }
+ }
+ }
+ }
+ }
+ }
+ },
+ "vnfcSnapshots": {
+ "description": "Information about VNFC snapshots constituting this VNF snapshot.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents a VNFC snapshot.\nNOTE 1:\tThe identifier of the compute snapshot resource is assigned during creation of a VNFC snapshot \n being returned from the VIM as output data in the response message of the individual resource \n operations. This attribute shall only be present for a VNFC snapshot that has been newly created \n by the VNFM as a result of the \"Create VNF snapshot task\".\nNOTE 2:\tThe identifier of the storage snapshot resource is assigned during creation of a VNFC snapshot being \n returned from the VIM as output data in the response message of the individual resource operations. \n This attribute shall only be present for a VNFC snapshot with an associated storage resource and that \n has been newly created by the VNFM as a result of the \"Create VNF snapshot task\".\n",
+ "type": "object",
+ "required": [
+ "id",
+ "vnfcInstanceId",
+ "triggeredAt",
+ "vnfcResourceId"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\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 to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "creationFinishedAt": {
+ "description": "Date-time stamp. Representation: String formatted according to 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": {
+ "required": ["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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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": "Mapping of the storage resources associated to the VNFC with the storage snapshot resources.\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"
+ },
+ "storageSnapshotResource": {
+ "description": "This 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"
+ }
+ }
+ }
+ },
+ "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 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"
+ }
+ }
+ }
+ },
+ "vnfStateSnapshotInfo": {
+ "description": "This type represents information about VNF-specific state snapshot data.\n",
+ "type": "object",
+ "required": ["checksum", "isEncrypted"],
+ "properties": {
+ "checksum": {
+ "description": "Cheksum description\n",
+ "type": "string"
+ },
+ "isEncrypted": {
+ "description": "The Boolean is a data type having two values (true and false).\n",
+ "type": "boolean"
+ },
+ "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 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"
+ }
+ }
+ },
+ "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 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"
+ },
+ "_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 using an absolute URI.\n",
+ "type": "object",
+ "required": ["href"],
+ "properties": {
+ "href": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ }
+ }
+ },
+ "vnfStateSnapshot": {
+ "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"
+ }
+ }
+ }
+ }
+ }
+ }
+ },
+ "_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 using an absolute URI.\n",
+ "type": "object",
+ "required": ["href"],
+ "properties": {
+ "href": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ }
+ }
+ },
+ "takenFrom": {
+ "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"
+ }
+ }
+ }
+ }
+ }
+ }
}
\ No newline at end of file
diff --git a/SOL003/VNFLifecycleManagement-API/schemas/VnfSnapshotInfoModifications.schema.json b/SOL003/VNFLifecycleManagement-API/schemas/VnfSnapshotInfoModifications.schema.json
index dee7a6ddfd3639626664464f70cf7fec44a712fc..105dc0032df6698418fc4809668a1c3b4e291667 100644
--- a/SOL003/VNFLifecycleManagement-API/schemas/VnfSnapshotInfoModifications.schema.json
+++ b/SOL003/VNFLifecycleManagement-API/schemas/VnfSnapshotInfoModifications.schema.json
@@ -1,1499 +1,2635 @@
{
- "description": "This type represents attribute modifications that were performed on an \"Individual VNF snapshot\" \nresource. The attributes that can be included consist of those requested to be modified explicitly \nin the \"VnfSnapshotInfoModificationRequest\" data structure, and additional attributes of the \n\"VnfSnapshotInfo\" data structure that were modified implicitly. The \"VnfSnapshotInfoModifications\" \ndata type shall comply with the provisions defined in table 5.5.2.25-1.\n",
+ "description": "This type represents attribute modifications that were performed on an \"Individual VNF snapshot\" \nresource. The attributes that can be included consist of those requested to be modified explicitly \nin the \"VnfSnapshotInfoModificationRequest\" data structure, and additional attributes of the \n\"VnfSnapshotInfo\" data structure that were modified implicitly.\n",
"type": "object",
"properties": {
- "vnfSnapshotPkgId": {
+ "vnfSnapshotPkgId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfSnapshot": {
+ "description": "This type represents a VNF snapshot.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "vnfInstanceId",
+ "triggeredAt",
+ "vnfdId",
+ "vnfInfo",
+ "vnfcSnapshots"
+ ],
+ "properties": {
+ "id": {
"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 5.5.2.23-1.\n",
+ "vnfInstanceId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "creationStartedAt": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "creationFinishedAt": {
+ "description": "Date-time stamp. Representation: String formatted according to 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.\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",
"type": "object",
"required": [
- "id",
- "vnfInstanceId",
- "triggeredAt",
- "vnfdId",
- "vnfInfo",
- "vnfcSnapshots"
+ "id",
+ "vnfdId",
+ "vnfProvider",
+ "vnfProductName",
+ "vnfSoftwareVersion",
+ "vnfdVersion",
+ "instantiationState",
+ "_links"
],
"properties": {
- "id": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfInstanceName": {
+ "description": "Name of the VNF instance. This attribute can be modified with the PATCH method.\n",
+ "type": "string"
+ },
+ "vnfInstanceDescription": {
+ "description": "Human-readable description of the VNF instance. This attribute can be modified with the PATCH method.\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.\n",
+ "type": "string"
+ },
+ "vnfdVersion": {
+ "description": "A version.\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 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"
+ },
+ "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",
+ "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",
+ "type": "object",
+ "required": [
+ "vimType"
+ ],
+ "properties": {
+ "vimId": {
"description": "An identifier with the intention of being globally unique.\n",
"type": "string"
- },
- "vnfInstanceId": {
+ },
+ "vimType": {
+ "description": "Discriminator for the different types of the VIM information. The value of this attribute determines the structure of the \"interfaceInfo\" and \"accessInfo\" attributes, based on the type of the VIM., CISM, CIR or MCIOP repository. The set of permitted values is expected to change over time as new types or versions of VIMs become available. The ETSI NFV registry of VIM-related information [i.3] provides access to information about VimConnectionInfo definitions for various VIM, CISM, CIR or MCIOP repository types. The structure of the registry is defined in annex C.\n",
+ "type": "string"
+ },
+ "interfaceInfo": {
+ "description": "This 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"
+ },
+ "accessInfo": {
+ "description": "This 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"
+ },
+ "extra": {
+ "description": "This 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"
+ }
+ }
+ }
+ },
+ "cirConnectionInfo": {
+ "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",
+ "type": "object",
+ "required": [
+ "vimType"
+ ],
+ "properties": {
+ "vimId": {
"description": "An identifier with the intention of being globally unique.\n",
"type": "string"
- },
- "creationStartedAt": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "creationFinishedAt": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "vnfdId": {
+ },
+ "vimType": {
+ "description": "Discriminator for the different types of the VIM information. The value of this attribute determines the structure of the \"interfaceInfo\" and \"accessInfo\" attributes, based on the type of the VIM., CISM, CIR or MCIOP repository. The set of permitted values is expected to change over time as new types or versions of VIMs become available. The ETSI NFV registry of VIM-related information [i.3] provides access to information about VimConnectionInfo definitions for various VIM, CISM, CIR or MCIOP repository types. The structure of the registry is defined in annex C.\n",
+ "type": "string"
+ },
+ "interfaceInfo": {
+ "description": "This 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"
+ },
+ "accessInfo": {
+ "description": "This 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"
+ },
+ "extra": {
+ "description": "This 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"
+ }
+ }
+ }
+ },
+ "mciopRepositoryInfo": {
+ "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",
+ "type": "object",
+ "required": [
+ "vimType"
+ ],
+ "properties": {
+ "vimId": {
"description": "An identifier with the intention of being globally unique.\n",
"type": "string"
+ },
+ "vimType": {
+ "description": "Discriminator for the different types of the VIM information. The value of this attribute determines the structure of the \"interfaceInfo\" and \"accessInfo\" attributes, based on the type of the VIM., CISM, CIR or MCIOP repository. The set of permitted values is expected to change over time as new types or versions of VIMs become available. The ETSI NFV registry of VIM-related information [i.3] provides access to information about VimConnectionInfo definitions for various VIM, CISM, CIR or MCIOP repository types. The structure of the registry is defined in annex C.\n",
+ "type": "string"
+ },
+ "interfaceInfo": {
+ "description": "This 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"
+ },
+ "accessInfo": {
+ "description": "This 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"
+ },
+ "extra": {
+ "description": "This 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"
+ }
+ }
+ }
+ },
+ "instantiationState": {
+ "description": "The instantiation state of the VNF. Permitted 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": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "vnfState": {
+ "description": "STARTED: The VNF instance is up and running. STOPPED: The VNF instance has been shut down.\n",
+ "type": "string",
+ "enum": [
+ "STARTED",
+ "STOPPED"
+ ]
},
- "vnfInstance": {
- "description": "This type represents a VNF instance.\n",
+ "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. This attribute shall be present if the VNF supports scaling. See clause B.2 for an explanation of VNF scaling.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the scale level of a VNF instance related to a scaling aspect.\n",
"type": "object",
"required": [
- "id",
- "vnfdId",
- "vnfProvider",
- "vnfProductName",
- "vnfSoftwareVersion",
- "vnfdVersion",
- "instantiationState"
+ "aspectId",
+ "scaleLevel"
],
"properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
+ "aspectId": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
},
- "vnfInstanceName": {
- "description": "Name of the VNF instance. This attribute can be modified with the PATCH method.\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. This attribute can be modified with the PATCH method.\n",
- "type": "string"
+ "scaleToLevel": {
+ "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": {
+ "description": "This type represents the scale level of a VNF instance related to a scaling aspect.\n",
+ "type": "object",
+ "required": [
+ "aspectId",
+ "scaleLevel"
+ ],
+ "properties": {
+ "aspectId": {
+ "description": "An identifier that is unique within a VNF descriptor.\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"
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
},
- "vnfProductName": {
- "description": "Name to identify the VNF Product. The value is copied from the VNFD.\n",
- "type": "string"
+ "scaleToLevel": {
+ "description": "An identifier with the intention of being globally unique.\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.\nNOTE 1:\tThe attributes \"associatedVnfcCpId\", \"associatedVipCpId\", \"associatedVirtualCpId\" and \n \"associatedVnfVirtualLinkId\" are mutually exclusive. Exactly one shall be present.\nNOTE 2:\tAn external CP instance is not associated to a link port in the cases indicated for the \n “extLinkPorts†attribute in clause 4.4.1.11.\nNOTE 3: 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 \n CP, e.g. to build a link redundant mated pair in SR-IOV cases.\nNOTE 4: When more than one netAttDefResourceId is indicated, all shall belong to the same namespace.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "cpdId",
+ "cpConfigId",
+ "cpProtocolInfo"
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "associatedVnfcCpId"
+ ]
},
- "vnfSoftwareVersion": {
- "description": "A version.\n",
- "type": "string"
+ {
+ "required": [
+ "associatedVipCpId"
+ ]
},
- "vnfdVersion": {
- "description": "A version.\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"
},
- "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 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"
+ "cpdId": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
},
- "vimConnectionInfo": {
- "description": "Information about VIM 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 VNF-related resource management in direct mode is pplicable. This attribute can be modified with the PATCH method.\n",
- "type": "object",
- "additionalProperties": {
- "description": "This type represents parameters to connect to a VIM for managing the resources of a VNF instance. This structure is used to convey VIM-related parameters over the Or-Vnfm interface. Additional parameters for a VIM may be configured into the VNFM by means outside the scope of the present document, and bound to the identifier of that VIM.\n",
- "type": "object",
- "required": [
- "vimType"
- ],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vimType": {
- "description": "Discriminator for the different types of the VIM information. The value of this attribute determines the structure of the \"interfaceInfo\" and \"accessInfo\" attributes, based on the type of the VIM. The set of permitted values is expected to change over time as new types or versions of VIMs become available. The ETSI NFV registry of VIM-related information provides access to information about VimConnectionInfo definitions for various VIM types. The structure of the registry is defined in Annex C of SOL003.\n",
- "type": "string"
- },
- "interfaceInfo": {
- "description": "This 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"
- },
- "accessInfo": {
- "description": "This 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"
- },
- "extra": {
- "description": "This 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"
- }
- }
- }
+ "cpConfigId": {
+ "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.\n",
- "type": "string",
- "enum": [
- "NOT_INSTANTIATED",
- "INSTANTIATED"
- ]
+ "vnfdId": {
+ "description": "An identifier with the intention of being 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",
+ "cpProtocolInfo": {
+ "description": "Network protocol information for this CP.\n",
+ "type": "array",
+ "items": {
+ "description": "This type describes the protocol layer(s) that a CP uses together with protocol-related information, like addresses.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the \n present document in a backwards-compatible way. In the current version of the present document, only IP over \n Ethernet is supported.\n",
"type": "object",
"required": [
- "flavourId",
- "vnfState"
+ "layerProtocol"
],
"properties": {
- "flavourId": {
- "description": "An identifier that is unique within a VNF descriptor.\n",
- "type": "string"
+ "layerProtocol": {
+ "description": "The identifier of layer(s) and protocol(s) associated to the network address information.\nPermitted 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:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, segmentationId shall be present. \n Otherwise it shall not be present.\nNOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the \n actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the \n transport header of the packets or it may be an identifier used between the application \n and the NFVI networking infrastructure to identify the network sub-interface of the trunk \n port in question. In the latter case the NFVI infrastructure will map this local segmentationId \n to whatever segmentationId is actually used by the NFVI’s transport technology.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "required": [
+ "macAddress"
+ ]
},
- "vnfState": {
- "description": "STARTED: The VNF instance is up and running. STOPPED: The VNF instance has been shut down.\n",
- "type": "string",
- "enum": [
- "STARTED",
- "STOPPED"
+ {
+ "required": [
+ "ipAddresses"
+ ]
+ }
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "addresses"
+ ]
+ },
+ {
+ "required": [
+ "addressRange"
]
+ }
+ ],
+ "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 notes 3 and 4.\n",
+ "type": "string"
},
- "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. This attribute shall be present if the VNF supports scaling. See clause B.2 for an explanation of VNF scaling.\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"
+ ],
+ "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. See note 2.\n",
+ "type": "object",
"required": [
- "aspectId",
- "scaleLevel"
+ "minAddress",
+ "maxAddress"
],
- "type": "object",
"properties": {
- "aspectId": {
- "description": "An identifier that is unique within a VNF descriptor.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being 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"
},
- "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.\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"
+ },
+ "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 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"
+ },
+ "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"
+ },
+ "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 with the intention of being 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",
+ "minItems": 1,
+ "items": {
+ "description": "This type provides information related to virtual IP (VIP) CP.\nNOTE 1:\tIt is possible that there is no associated VnfcCp because the VIP CP is available but not associated yet. NOTE 2: If only the value or the presence of this attribute is changed in the \"VipCpInfo\" structure by an LCM operation occurrence, this does not represent a change that requires including a related \"AffectedVipCp\" structure in the VNF LCM operation occurrence notifications or the \"VnfLcmOpOcc\" structure related to this LCM operation occurrence.\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": "An identifier that is unique within a VNF descriptor.\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 uses together with protocol-related information, like addresses.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the \n present document in a backwards-compatible way. In the current version of the present document, only IP over \n Ethernet is supported.\n",
+ "type": "object",
+ "required": [
+ "layerProtocol"
+ ],
+ "properties": {
+ "layerProtocol": {
+ "description": "The identifier of layer(s) and protocol(s) associated to the network address information.\nPermitted 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:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, segmentationId shall be present. \n Otherwise it shall not be present.\nNOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the \n actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the \n transport header of the packets or it may be an identifier used between the application \n and the NFVI networking infrastructure to identify the network sub-interface of the trunk \n port in question. In the latter case the NFVI infrastructure will map this local segmentationId \n to whatever segmentationId is actually used by the NFVI’s transport technology.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "required": [
+ "macAddress"
+ ]
+ },
+ {
+ "required": [
+ "ipAddresses"
+ ]
+ }
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "addresses"
+ ]
+ },
+ {
+ "required": [
+ "addressRange"
+ ]
+ }
+ ],
+ "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 notes 3 and 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",
+ "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"
+ ],
+ "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. See note 2.\n",
+ "type": "object",
"required": [
- "aspectId",
- "scaleLevel"
+ "minAddress",
+ "maxAddress"
],
- "type": "object",
"properties": {
- "aspectId": {
- "description": "An identifier that is unique within a VNF descriptor.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being 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"
},
- "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.\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"
+ ]
},
- "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 5.5.3.25 1.\n",
- "type": "object",
- "required": [
- "id",
- "cpdId",
- "cpConfigId",
- "cpProtocolInfo"
- ],
- "oneOf": [{
- "required": [
- "associatedVnfcCpId"
- ]
- },
- {
- "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": "An identifier that is unique within a VNF descriptor.\n",
- "type": "string"
- },
- "cpConfigId": {
- "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"
- },
- "cpProtocolInfo": {
- "description": "Network protocol information for this CP.\n",
- "type": "array",
- "items": {
- "description": "This type describes the protocol layer(s) that a CP uses together with protocol-related information, like addresses.\n",
- "type": "object",
- "required": [
- "layerProtocol"
- ],
- "properties": {
- "layerProtocol": {
- "description": "The identifier of layer(s) and protocol(s) associated to the network address information. Permitted values: IP_OVER_ETHERNET 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": "string",
- "enum": [
- "IP_OVER_ETHERNET"
- ]
- },
- "ipOverEthernet": {
- "description": "This type represents information about a network address that has been assigned.\n",
- "type": "object",
- "anyOf": [{
- "required": [
- "macAddress"
- ]
- },
- {
- "required": [
- "ipAddresses"
- ]
- }
- ],
- "oneOf": [{
- "required": [
- "addresses"
- ]
- },
- {
- "required": [
- "addressRange"
- ]
- }
- ],
- "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. If the Cp instance represents a subport in a trunk, segmentationId shall be present. Otherwise it shall not be present. 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": "string"
- },
- "ipAddresses": {
- "description": "Addresses assigned to the CP instance. Each entry represents IP addresses assigned by fixed or dynamic IP address assignment per subnet. At least one of \"macAddress\" or \"ipAddresses\" shall be present.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": [
- "type"
- ],
- "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). Exactly one of \"addresses\" or \"addressRange\" 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"
- }
- },
- "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.\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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- }
- }
- }
- }
- }
- }
- }
- }
- },
- "extLinkPortId": {
- "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 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"
- },
- "associatedVnfcCpId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "associatedVnfVirtualLinkId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- }
- }
- }
+ "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": "This 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"
+ }
+ }
+ }
+ },
+ "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 provides information related to a virtual CP instance of a VNF.\nNOTE: A consumer of the VNF LCM interface can learn the actual VNFC instances implementing the service \n accessible via the virtual CP instance by querying the \"vnfcResourceInfo\" from the \"InstantiatedVnfInfo\" \n and filtering by corresponding \"vduIds\" values.\n",
+ "type": "object",
+ "required": [
+ "cpInstanceId",
+ "cpdId",
+ "resourceHandle",
+ "vduIds"
+ ],
+ "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": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "resourceHandle": {
+ "required": [
+ "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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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"
},
- "extVirtualLinkInfo": {
- "description": "Information about the external VLs the VNF instance is connected to.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": [
- "id",
- "resourceHandle",
- "currentVnfExtCpData"
- ],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceHandle": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\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.\n",
- "type": "object",
- "required": [
- "id",
- "resourceHandle"
- ],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceHandle": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\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"
- }
- }
- }
- },
- "currentVnfExtCpData": {
- "description": "Allows the API consumer to read the current CP configuration information for the connection of external CPs to the external virtual link. This attribute reflects the current configuration information that has resulted from merging into this attribute the \"VnfExtCpData\" information which was passed as part of the \"ExtVirtualLinkData\" structure in the input of the most recent VNF LCM operation such as \"InstantiateVnfRequest\", \"ChangeExtVnfConnectivityRequest\", \"ChangeVnfFlavourRequest\" or \"ChangeCurrentVnfPkgRequest\", or has been provided by the NFVO during the granting procedure. If applying such change results in an empty list of \"currentVnfExtCpData\" structure instances, the affected instance of \"ExtVirtualLinkInfo\" shall be removed from its parent data structure.\n",
- "type": "array",
- "items": {
- "description": "This type represents configuration information for external CPs created from a CPD.\n",
- "type": "object",
- "required": [
- "cpdId"
- ],
- "properties": {
- "cpdId": {
- "description": "An identifier that is unique within a VNF descriptor.\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 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). 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. 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.\n",
- "type": "object",
- "additionalProperties": {
- "description": "This type represents an externally provided link port or network address information per instance of an external connection point. In case a link port is provided, the VNFM shall use that link port when connecting the external CP to the external VL. In a link port is not provided, the VNFM shall create a link port on the external VL, and use that link port to connect the external CP to the external VL.\n",
- "anyOf": [{
- "required": [
- "linkPortId"
- ]
- },
- {
- "required": [
- "cpProtocolData"
- ]
- }
- ],
- "type": "object",
- "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"
- },
- "cpProtocolData": {
- "description": "Parameters for configuring the network protocols on the link port that connects the CP to a VL. The following conditions apply to the attributes \"linkPortId\" and \"cpProtocolData\": 1) Void 2) At least one of the \"linkPortId\" and \"cpProtocolData\" attributes \n shall be present for an external CP instance representing a subport \n that is to be created, or an external CP instance that is to be created \n by creating the corresponding VNFC or VNF instance during the current or \n a subsequent LCM operation, or for an existing external CP instance \n that is to be re-configured or added to a particular external virtual link.\n3) If the \"linkPortId\" attribute is absent, the VNFM shall create a\n link port.\n4) If the \"cpProtocolData\" attribute is absent, the \"linkPortId\"\n attribute shall be provided referencing a pre-created link port,\n and the VNFM can use means outside the scope of the present\n document to obtain the pre-configured address information for the\n connection point from the resource representing the link port.\n5) If both \"cpProtocolData\" and \"linkportId\" are provided, the API\n consumer shall ensure that the cpProtocolData can be used with the\n pre-created link port referenced by \"linkPortId\".\n",
- "type": "array",
- "items": {
- "description": "This type represents network protocol data.\n",
- "type": "object",
- "required": [
- "layerProtocol"
- ],
- "properties": {
- "layerProtocol": {
- "description": "Identifier of layer(s) and protocol(s). 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": "string",
- "enum": [
- "IP_OVER_ETHERNET"
- ]
- },
- "ipOverEthernet": {
- "description": "This type represents network address data for IP over Ethernet.\n",
- "type": "object",
- "anyOf": [{
- "required": [
- "macAddress"
- ]
- },
- {
- "required": [
- "ipAddresses"
- ]
- }
- ],
- "oneOf": [{
- "required": [
- "fixedAddresses"
- ]
- },
- {
- "required": [
- "numDynamicAddresses"
- ]
- },
- {
- "required": [
- "ipAddressRange"
- ]
- }
- ],
- "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. If the Cp instance represents a subport in a trunk, segmentationId shall be present. Otherwise it shall not be present. 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": "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.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": [
- "type"
- ],
- "properties": {
- "type": {
- "description": "The type of the IP addresses. Permitted values: IPV4, 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). Exactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present.\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 other resource provider. It is expected to be unique within the VIM instance.\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"
},
- "extManagedVirtualLinkInfo": {
- "description": "Information about the externally-managed internal VLs of the VNF instance.\nNOTE: 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 VNF internal VL shall indicate so by referencing to the same VnfVirtualLinkDesc and externally-managed multi-site VL instance (refer to clause 5.5.3.3).\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": [
- "id",
- "vnfVirtualLinkDescId",
- "networkResource"
- ],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfVirtualLinkDescId": {
- "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"
- },
- "networkResource": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
- "type": "string"
- }
- }
- },
- "vnfLinkPorts": {
- "description": "Link ports of this VL.\n",
- "type": "array",
- "items": {
- "type": "object",
- "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": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\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.\n",
- "type": "string",
- "enum": [
- "VNFC_CP",
- "EXT_CP"
- ]
- }
- }
- }
- },
- "extManagedMultisiteVirtualLinkId": {
- "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 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"
+ }
+ }
+ },
+ "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 uses together with protocol-related information, like addresses.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the \n present document in a backwards-compatible way. In the current version of the present document, only IP over \n Ethernet is supported.\n",
+ "type": "object",
+ "required": [
+ "layerProtocol"
+ ],
+ "properties": {
+ "layerProtocol": {
+ "description": "The identifier of layer(s) and protocol(s) associated to the network address information.\nPermitted 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:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, segmentationId shall be present. \n Otherwise it shall not be present.\nNOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the \n actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the \n transport header of the packets or it may be an identifier used between the application \n and the NFVI networking infrastructure to identify the network sub-interface of the trunk \n port in question. In the latter case the NFVI infrastructure will map this local segmentationId \n to whatever segmentationId is actually used by the NFVI’s transport technology.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "required": [
+ "macAddress"
+ ]
+ },
+ {
+ "required": [
+ "ipAddresses"
+ ]
+ }
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "addresses"
+ ]
+ },
+ {
+ "required": [
+ "addressRange"
+ ]
+ }
+ ],
+ "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 notes 3 and 4.\n",
+ "type": "string"
},
- "monitoringParameters": {
- "description": "Active monitoring parameters.\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"
+ ],
+ "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. See note 2.\n",
"type": "object",
"required": [
- "id",
- "performanceMetric"
+ "minAddress",
+ "maxAddress"
],
"properties": {
- "id": {
- "description": "An identifier that is unique within a VNF descriptor.\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"
+ "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"
},
- "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"
+ "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.\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"
+ ]
},
- "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",
+ "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"
+ }
+ }
+ }
+ }
+ }
+ },
+ "vduIds": {
+ "description": "Reference to the VDU(s) which implement the service accessible via the virtual CP instance. See note.\n",
+ "type": "array",
+ "minItems": 1,
+ "items": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ }
+ },
+ "additionalServiceInfo": {
+ "description": "Additional service identification information of the virtual CP instance.\n",
+ "type": "array",
+ "items": {
+ "description": "This type provides 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 \n termination within the VNF, such as for example a URL path information in an HTTP request required \n to allow a single virtual CP IP address to be used for several HTTP based services that use the \n same port number.\n",
+ "type": "object",
+ "required": [
+ "portInfo"
+ ],
+ "properties": {
+ "portInfo": {
+ "description": "Service port numbers exposed by the virtual CP instance.\n",
+ "minItems": 1,
+ "type": "array",
+ "items": {
+ "description": "This type describes the service identifying port properties exposed by the virtual CP instance.\n",
+ "type": "object",
+ "required": [
+ "name",
+ "port",
+ "portConfigurable"
+ ],
+ "properties": {
+ "name": {
+ "description": "The name of the port exposed by the virtual CP instance.\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.\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"
- },
- "vduId": {
- "description": "An identifier that is unique within a VNF descriptor.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
+ },
+ "protocol": {
+ "description": "The L4 protocol for this port exposed by the virtual CP instance.\nPermitted values: - TCP - UDP - SCTP\n",
+ "type": "string",
+ "enum": [
+ "TCP",
+ "UDP",
+ "SCTP"
+ ]
+ },
+ "port": {
+ "description": "The L4 port number exposed by the virtual CP instance.\n",
+ "type": "integer"
+ },
+ "portConfigurable": {
+ "description": "The Boolean is a data type having two values (true and false).\n",
+ "type": "boolean"
+ }
+ }
+ }
+ },
+ "serviceInfo": {
+ "description": "This 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"
+ }
+ }
+ }
+ },
+ "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 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"
+ }
+ }
+ }
+ },
+ "extVirtualLinkInfo": {
+ "description": "Information about the external VLs the VNF instance is connected to.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents information about an external VL.\nNOTE:\tThis attribute reflects the current configuration information that has resulted from merging into this attribute \n the \"VnfExtCpData\" information which was passed as part of the \"ExtVirtualLinkData\" structure in the input of the \n most recent VNF LCM operation such as \"InstantiateVnfRequest\", \"ChangeExtVnfConnectivityRequest\", \"ChangeVnfFlavourRequest\" \n or \"ChangeCurrentVnfPkgRequest\", or in the Grant response. If applying such change results in an empty list of \n \"currentVnfExtCpData\" structure instances, the affected instance of \"ExtVirtualLinkInfo\" shall be removed from its \n parent data structure.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "resourceHandle",
+ "currentVnfExtCpData"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceHandle": {
+ "required": [
+ "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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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.\nNOTE 1:\tThe use cases UC#4 and UC#5 in clause A.4 of ETSI GS NFV-IFA 007 provide examples for such a configuration. NOTE 2:\tThe 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": {
+ "required": [
+ "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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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 the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "currentVnfExtCpData": {
+ "description": "Allows the API consumer to read the current CP configuration information for the connection of external CPs to the external virtual link. See note.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents configuration information for external CPs created. * NOTE 1: \tIn case this identifier refers to a CPD with trunking enabled, the external CP instances created\n from this CPD will represent ports in a trunk.\n* NOTE 2: \tWithin one VNF instance, all VNFC instances created from a particular VDU have the same external\n connectivity. Thus, given a particular value of the \"cpdId\" attribute, there shall be one\n \"cpConfig\" entry for each VNFC instance that has been or can be created from a VDU which includes\n a CPD identified by the \"cpdId\" attribute. If the cpConfig represents a subport in a trunk,\n all \"cpConfig\" entries in this list shall have the same segmentationId, which means they are\n connected to the same set of external VLs via the trunk.\n* NOTE 3: \tThe map entry value shall be set to \"null\" in order to delete a \"VnfExtCpConfig\" entry identified\n by a particular key value from the map, i.e. for the disconnection of an existing external\n CP instance addressed by cpInstanceId in the deleted map entry from a particular external\n virtual link, and deletion of that instance in case it represents a subport. Deleting the\n last key from the map removes the affected instance of the \"VnfExtCpData\" structure from\n its parent data structure.\n* NOTE 4: If, as defined by the input parameters of a \"ChangeVnfFlavour\", \"ChangeExtVnfConnectivity\" or\n \"ChangeCurrentVnfPkg\" operation or as part of the Grant response for any of these operations, a cpConfig\n map entry identified by a particular map key value is moved into another \"ExtVirtualLinkData\" or\n \"VnfExtCpData\" structure, this particular cpConfig map entry may be used by an external CP instance\n different than the one that has used it before the operation, or by no external CP instance at all.\n Renaming a CPD identifier during the \"changeCurrentVnfPkg\" operation does not count as moving the related\n \"cpConfig\" map entries to a new \"extCpData\" structure.\n",
+ "type": "object",
+ "required": [
+ "cpdId"
+ ],
+ "properties": {
+ "cpdId": {
+ "description": "An identifier that is unique within a VNF descriptor.\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 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",
+ "anyOf": [
+ {
+ "required": [
+ "linkPortId"
+ ]
+ },
+ {
+ "required": [
+ "cpProtocolData"
+ ]
+ },
+ {
+ "required": [
+ "netAttDefResourceId"
+ ]
+ }
+ ],
+ "type": "object",
+ "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 to the VNFM the need to create a dedicated link port for the external CP. If set to True, the VNFM shall create a link port. If set to False, the VNFM shall not create a link port. 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"
+ },
+ "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 2, 3 and 4.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ },
+ "cpProtocolData": {
+ "description": "Parameters for configuring the network protocols on the link port that connects the CP to a VL. See notes 1 and 2.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents network protocol data. * NOTE:\tThis attribute allows to signal the addition of further types of layer and protocol\n in future versions of the present document in a backwards-compatible way. In the current\n 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:\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 network address data for IP over Ethernet. * NOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. * NOTE 2:\tExactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present. * NOTE 3:\tIf the CP instance represents a subport in a trunk, segmentationId shall be present.\n Otherwise it shall not be present.\n* NOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the actual\n network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header\n of the packets or it may be an identifier used between the application and the NFVI networking\n infrastructure to identify the network sub-interface of the trunk port in question. In the latter\n case the NFVI infrastructure will map this local segmentationId to whatever segmentationId is\n actually used by the NFVI’s transport technology.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "required": [
+ "macAddress"
+ ]
},
- "computeResource": {
+ {
"required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
- "type": "string"
- }
- }
+ "ipAddresses"
+ ]
+ }
+ ],
+ "oneOf": [
+ {
+ "required": [
+ "fixedAddresses"
+ ]
},
- "zoneId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
+ {
+ "required": [
+ "numDynamicAddresses"
+ ]
},
- "storageResourceIds": {
- "description": "References to the VirtualStorage resources. 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"
- }
+ {
+ "required": [
+ "ipAddressRange"
+ ]
+ }
+ ],
+ "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: -\tVLAN: the subport uses VLAN as encapsulation type. -\tINHERIT: the subport gets its segmentation type from the network it’s 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"
+ ]
},
- "reservationId": {
- "description": "An identifier with the intention of being globally unique.\n",
+ "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": "All the 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. 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. 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": [
+ "type"
+ ],
+ "properties": {
+ "type": {
+ "description": "The type of the IP addresses. Permitted values: IPV4, IPV6.\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
+ },
+ "fixedAddresses": {
+ "description": "Fixed addresses to assign (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"
+ }
+ },
+ "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. See note 2.\n",
"type": "object",
"required": [
- "id",
- "cpdId"
+ "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": "An identifier that is unique within a VNF descriptor.\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. The information can be omitted because it is already available as part of the external CP information.\n",
- "type": "array",
- "items": {
- "description": "This type describes the protocol layer(s) that a CP uses together with protocol-related information, like addresses.\n",
- "type": "object",
- "required": [
- "layerProtocol"
- ],
- "properties": {
- "layerProtocol": {
- "description": "The identifier of layer(s) and protocol(s) associated to the network address information. Permitted values: IP_OVER_ETHERNET 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": "string",
- "enum": [
- "IP_OVER_ETHERNET"
- ]
- },
- "ipOverEthernet": {
- "description": "This type represents information about a network address that has been assigned.\n",
- "type": "object",
- "anyOf": [{
- "required": [
- "macAddress"
- ]
- },
- {
- "required": [
- "ipAddresses"
- ]
- }
- ],
- "oneOf": [{
- "required": [
- "addresses"
- ]
- },
- {
- "required": [
- "addressRange"
- ]
- }
- ],
- "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. If the Cp instance represents a subport in a trunk, segmentationId shall be present. Otherwise it shall not be present. 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": "string"
- },
- "ipAddresses": {
- "description": "Addresses assigned to the CP instance. Each entry represents IP addresses assigned by fixed or dynamic IP address assignment per subnet. At least one of \"macAddress\" or \"ipAddresses\" shall be present.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": [
- "type"
- ],
- "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). Exactly one of \"addresses\" or \"addressRange\" 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"
- }
- },
- "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.\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 other resource provider. It is expected to be unique within the VIM instance.\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"
},
- "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": "This 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"
+ "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.\n",
+ "type": "string"
+ }
}
+ }
+ }
+ }
+ },
+ "virtualCpAddress": {
+ "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",
+ "type": "object",
+ "required": [
+ "type"
+ ],
+ "properties": {
+ "type": {
+ "description": "The type of the IP addresses. Permitted values: IPV4, IPV6.\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
},
- "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 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"
+ "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"
+ }
}
}
- }
- },
- "virtualLinkResourceInfo": {
- "description": "Information about the virtualised network resources used by the VLs of the VNF instance.\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",
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ },
+ "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 contains 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": {
+ "required": [
+ "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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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 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 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"
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ },
+ "extManagedVirtualLinkInfo": {
+ "description": "Information about the externally-managed internal VLs of the VNF instance. See notes 5 and 6.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": [
+ "id",
+ "vnfVirtualLinkDescId",
+ "networkResource"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfVirtualLinkDescId": {
+ "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"
+ },
+ "networkResource": {
+ "required": [
+ "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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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": {
+ "description": "This type represents a link port of an internal VL of a VNF.\nNOTE 1: Either cpInstanceId with cpInstanceType set to \"EXT_CP\" or any combination of cpInstanceId\n with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId (i.e. one or both of them) shall be \n present for a VnfLinkPortInfo. In case both cpInstanceId with cpInstanceType set to \"VNFC_CP\" \n and vipCpInstanceId are present, the two different CP instances share the linkport.\nNOTE 2: Annex A.4 of ETSI GS NFV-IFA 007 provides examples for configurations where both vipCpInstanceId\n and vnfcCpInstanceId are present (UC#5 and UC#5-b), only vnfcCpInstanceId is present (UC#2), or \n only vipCpInstanceId is present (UC6 and UC#6-b).\nNOTE 3: The value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\"\n attribute.\n",
+ "type": "object",
+ "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": {
+ "required": [
+ "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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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.\nPermitted values: - VNFC_CP: The link port is connected to a VNFC CP. -\tEXT_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 the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "vnfNetAttDefResource": {
+ "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 contains 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": {
+ "required": [
+ "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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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 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 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": "Active monitoring parameters.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": [
+ "id",
+ "performanceMetric"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier that is unique within a VNF descriptor.\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. Depending on the form of virtualisation container of the VNFC:\n - For a VNFC based on VM, a reference to the corresponding VirtualCompute shall be provided, and\n - For a VNFC based on OS container(s), a reference to the Compute MCIO shall be provided. Hence, exposure of\n information by the VNFM to the NFVO is at the MCIO level.\nIn addition, the references to the storage resources depend on the form of the VNFC:\n a) For a VNFC based on VM, storage resource identifiers shall refer to VirtualStorage resources, and\n b) For a VNFC based on OS container(s), storage resource identifiers shall refer to Storage MCIOs.\n\nNOTE 1:\tETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on \n TOSCA specifications.\nNOTE 2:\tA VNFC CP is \"connected to\" an external CP if the VNFC CP is connected to an \n internal VL that exposes an external CP. A VNFC CP is \"exposed as\" an external \n CP if it is connected directly to an external VL.\nNOTE 3:\tThe information can be omitted because it is already available as part of the \n external CP information.\nNOTE 4: If only the value or the presence of this attribute is changed in the \"VnfcResourceInfo\"\n structure by an LCM operation occurrence, this does not represent a change that requires\n including a related \"AffectedVnfc\" structure in the VNF LCM operation occurrence notifications\n or the \"VnfLcmOpOcc\" structure related to this LCM operation occurrence.\nNOTE 5: 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 internal CP, e.g. to build a link\n redundant mated pair in SR-IOV cases.\nNOTE 6: 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"
+ },
+ "vduId": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "computeResource": {
+ "required": [
+ "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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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"
+ }
+ }
+ },
+ "zoneId": {
+ "description": "An identifier with the intention of being globally unique.\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 VNF descriptor.\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 uses together with protocol-related information, like addresses.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the \n present document in a backwards-compatible way. In the current version of the present document, only IP over \n Ethernet is supported.\n",
+ "type": "object",
+ "required": [
+ "layerProtocol"
+ ],
+ "properties": {
+ "layerProtocol": {
+ "description": "The identifier of layer(s) and protocol(s) associated to the network address information.\nPermitted 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:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, segmentationId shall be present. \n Otherwise it shall not be present.\nNOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the \n actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the \n transport header of the packets or it may be an identifier used between the application \n and the NFVI networking infrastructure to identify the network sub-interface of the trunk \n port in question. In the latter case the NFVI infrastructure will map this local segmentationId \n to whatever segmentationId is actually used by the NFVI’s transport technology.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "required": [
+ "macAddress"
+ ]
+ },
+ {
+ "required": [
+ "ipAddresses"
+ ]
+ }
+ ],
+ "oneOf": [
+ {
"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"
- },
- "vnfVirtualLinkDescId": {
- "description": "An identifier that is unique within a VNF descriptor.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "networkResource": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
- "type": "string"
- }
- }
- },
- "zoneId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "reservationId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
+ "addresses"
+ ]
+ },
+ {
+ "required": [
+ "addressRange"
+ ]
+ }
+ ],
+ "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 notes 3 and 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"
+ ],
+ "properties": {
+ "type": {
+ "description": "The type of the IP addresses. Permitted values: IPV4, IPV6.\n",
+ "type": "string",
+ "enum": [
+ "IPV4",
+ "IPV6"
+ ]
},
- "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",
+ "addresses": {
+ "description": "Fixed addresses assigned (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
"type": "array",
"items": {
- "type": "object",
- "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": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\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.\n",
- "type": "string",
- "enum": [
- "VNFC_CP",
- "EXT_CP"
- ]
- }
- }
+ "description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In 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 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"
- }
- }
- }
- },
- "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": "An identifier that is unique within a VNF descriptor.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being 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"
},
- "storageResource": {
+ "addressRange": {
+ "description": "An IP address range used, e.g. in case of egress connections. See note 2.\n",
+ "type": "object",
"required": [
- "resourceId"
+ "minAddress",
+ "maxAddress"
],
- "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",
"properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\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"
+ }
}
},
- "zoneId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "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.\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 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"
+ }
}
}
- }
- }
- }
- },
- "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 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"
- },
- "extensions": {
- "description": "Additional VNF-specific attributes that affect the lifecycle management of this VNF instance. These attributes represent values that are stored persistently in the VnfInstance structure for consumption by the VNFM or the lifecycle management scripts during the execution of VNF lifecycle management operations. All extensions that are allowed for the VNF are declared in the VNFD. The declaration of an extension in the VNFD contains information on whether its presence is optional or required, and optionally can specify an initial value. See note 2 and note 4. The VNFM shall reject requests to write extension attributes that are not declared in the VNFD with a \"422 Unprocessable entity\" error response as defined in clause 6.4 of ETSI GS NFV-SOL 013. Modifying the values of these attributes has no direct effect on the VNF instance; however, the modified attribute values can be considered during subsequent VNF lifecycle management operations, which means that the modified values can indirectly affect the configuration of the VNF instance. These attributes can be initialized with default values from the VNFD. These attributes can be modified with values passed in the request structures of certain LCM operations, such as the InstantiateVnfRequest structure. Further, these attributes can be created, modified or deleted with the PATCH method.\nNOTE: Upon creation of the VnfInstance structure, the VNFM shall create and initialize all child attributes of \"vnfConfigurableProperties\", \"metadata\" and \"extensions\" that were declared in the VNFD with a defined initial value. The defined initial values can be declared in the VNFD, and/or, in case of \"metadata\", obtained from the \"CreateVnfRequest\" structure. Child attributes of \"vnfConfigurableProperties\", \"metadata\" and \"extensions\" that have no defineddeclared initial value shall not be created, in order to be consistent with the semantics of the JSON Merge Patch method (see IETF RFC 7396) that interprets null values as deletion request.\n"
- },
- "_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 using an absolute URI.\n",
- "type": "object",
- "required": [
- "href"
- ],
- "properties": {
- "href": {
- "description": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- }
- }
- },
- "indicators": {
- "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"
}
}
- },
- "instantiate": {
- "description": "This type represents a link to a resource using an absolute URI.\n",
+ },
+ "virtualCpAddress": {
+ "description": "This type represents information about a network address that has been assigned to a virtual CP.\n",
"type": "object",
"required": [
- "href"
+ "type"
],
"properties": {
- "href": {
- "description": "String formatted according to IETF RFC 3986.\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"
}
}
- },
- "terminate": {
- "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"
- }
}
+ }
+ }
+ },
+ "vnfLinkPortId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "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"
+ },
+ "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 5 and 6. 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 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 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"
+ }
+ }
+ }
+ },
+ "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 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"
+ }
+ }
+ }
+ },
+ "vnfVirtualLinkResourceInfo": {
+ "description": "Information about the virtualised network resources used by the VLs of the VNF instance. See note 6.\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.\nNote: If only the value or the presence of this attribute is changed in the \"VnfVirtualLinkResourceInfo\"\n structure by an LCM operation occurrence, this does not represent a change that requires including\n a related \"AffectedVirtualLink\" structure in the VNF LCM operation occurrence notifications or the\n \"VnfLcmOpOcc\" structure related to this LCM operation occurrence.\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"
+ },
+ "vnfVirtualLinkDescId": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "networkResource": {
+ "required": [
+ "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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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"
},
- "scale": {
- "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"
- }
- }
+ "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"
},
- "scaleToLevel": {
- "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"
- }
- }
+ "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 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"
+ }
+ }
+ },
+ "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"
+ }
+ }
+ },
+ "zoneId": {
+ "description": "An identifier with the intention of being globally unique.\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": {
+ "description": "This type represents a link port of an internal VL of a VNF.\nNOTE 1: Either cpInstanceId with cpInstanceType set to \"EXT_CP\" or any combination of cpInstanceId\n with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId (i.e. one or both of them) shall be \n present for a VnfLinkPortInfo. In case both cpInstanceId with cpInstanceType set to \"VNFC_CP\" \n and vipCpInstanceId are present, the two different CP instances share the linkport.\nNOTE 2: Annex A.4 of ETSI GS NFV-IFA 007 provides examples for configurations where both vipCpInstanceId\n and vnfcCpInstanceId are present (UC#5 and UC#5-b), only vnfcCpInstanceId is present (UC#2), or \n only vipCpInstanceId is present (UC6 and UC#6-b).\nNOTE 3: The value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\"\n attribute.\n",
+ "type": "object",
+ "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": {
+ "required": [
+ "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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "type": "string"
},
- "changeFlavour": {
- "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"
- }
- }
+ "resourceProviderId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
},
- "heal": {
- "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"
- }
- }
+ "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.\n",
+ "type": "string"
},
- "operate": {
- "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"
- }
- }
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 1.\n",
+ "type": "string"
},
- "changeExtConn": {
- "description": "This type represents a link to a resource using an absolute URI.\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.\n* NOTE: At least one attribute shall be present.\n",
"type": "object",
- "required": [
- "href"
- ],
"properties": {
- "href": {
- "description": "String formatted according to IETF RFC 3986.\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 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"
}
- },
- "createSnapshot": {
- "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"
- }
}
},
- "revertToSnapshot": {
- "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"
- }
- }
+ "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.\nPermitted values: - VNFC_CP: The link port is connected to a VNFC CP. -\tEXT_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 the CISM or other resource provider. It is expected to be unique within the VIM instance.\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 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"
}
}
+ }
},
- "vnfcSnapshots": {
- "description": "Information about VNFC snapshots constituting this VNF snapshot.\n",
+ "virtualStorageResourceInfo": {
+ "description": "Information on the virtualised storage resource(s) used as storage for the VNF instance.\n",
"type": "array",
"items": {
- "description": "This type represents a VNFC snapshot.\n",
- "type": "object",
+ "description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance.\nNote: If only the value or the presence of this attribute is changed in the \"VirtualStorageResourceInfo\"\n structure by an LCM operation occurrence, this does not represent a change that requires\n including a related \"AffectedVirtualStorage\" structure in the VNF LCM operation occurrence\n notifications or the \"VnfLcmOpOcc\" structure related to this LCM operation occurrence.\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": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "storageResource": {
"required": [
- "id",
- "vnfcInstanceId",
- "triggeredAt",
- "vnfcResourceId"
+ "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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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": {
- "id": {
- "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\n",
- "type": "string"
+ "vimConnectionId": {
+ "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 to 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.\n",
+ "type": "string"
},
- "creationFinishedAt": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 1.\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",
+ "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.\n* NOTE: At 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"
- },
- "computeSnapshotResource": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
- "type": "string"
- }
- }
- },
- "storageSnapshotResources": {
- "description": "Mapping of the storage resources associated to the VNFC with the storage snapshot resources.\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"
- },
- "storageSnapshotResource": {
- "description": "This 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"
- }
- }
- }
- },
- "userDefinedData": {
+ },
+ "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 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"
+ }
+ }
+ },
+ "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"
}
}
+ },
+ "zoneId": {
+ "description": "An identifier with the intention of being globally unique.\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 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"
+ }
+ }
}
},
- "vnfStateSnapshotInfo": {
- "description": "This type represents information about VNF-specific state snapshot data.\n",
+ "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. Within the CISM, an MCIO controller monitors the actual state of an MCIO representing the set of VNFC instances realized by one or a set of OS containers and compare it to the desired state as specified in the respective declarative descriptor. It triggers actions toward the CIS to align the actual to the desired state. Monitoring the actual state includes monitoring the number of MCIO instances available at any specific point in time. In addition, an MCIO controller maintains properties and runtime information on the MCIO instances which have been created based on the same VDU. The McioInfo data structure provides the runtime information on the MCIOs obtained from the MCIO controller.\nNOTE: There are different types of MCIOs. The set of VNFC instances based on the same VDU is represented \n by one MCIO, e.g. of type Deployment. Each individual VNFC instance is represented by another type \n of MCIO, e.g. a POD.\n\nRuntime information of the set of OS containers realizing an individual VNFC instance is not part of the McioInfo data structure; such runtime information is provided in the ResourceHandle data structure referenced from the VnfcResourceInfo. The McioInfo does not provide runtime information of a constituent VNFC instance created based on a specific VDU.\nNOTE 1: The type of MCIO as specified in the declarative descriptor of the MCIO, and that can be read from \n the CISM. EXAMPLE: In case of MCIOs managed by Kubernetes®, the type of MCIO corresponds to the \n “kind†property of the declarative descriptor.\nNOTE 2: If the attribute additionalInfo is present, it may contain runtime information on the actual and \n desired state of the MCIO(s). \nNOTE 3: When the container infrastructure service is a Kubernetes® instance, the mcioId is the combined \n values from the kind and name fields of the Kubernetes resource object, separated by a slash. \n Example: \"Deployment/abcd\". \nNOTE 4: When the container infrastructure service is a Kubernetes® instance, the mcioName is the name \n field of the resource object. \n",
"type": "object",
"required": [
- "checksum",
- "isEncrypted"
+ "mcioId",
+ "mcioName",
+ "mcioNamespace",
+ "vduId",
+ "cismId",
+ "mcioType",
+ "desiredInstances",
+ "availableInstances"
],
"properties": {
- "checksum": {
- "description": "Checksum of the VNF state snapshot file. Hash algorithms applicable to VNF snapshot package artifacts are defined in ETSI GS NFV-SOL 010. $ref: \"../definitions/SOL002SOL003_def.yaml#/definitions/Checksum\"\n"
+ "mcioId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
},
- "isEncrypted": {
- "description": "Reflects whether the VNF state snapshot content is encrypted (true) or not (false). $ref: \"../definitions/SOL002SOL003_def.yaml#/definitions/Boolean\"\n"
+ "mcioName": {
+ "description": "Human readable name of this MCIO. See note 4.\n",
+ "type": "string"
},
- "metadata": {
- "description": "The metadata with additional information such as content type, size, creation date, etc. $ref: \"../definitions/SOL002SOL003_def.yaml#/definitions/KeyValuePairs\"\n"
+ "mcioNamespace": {
+ "description": "Namespace of this MCIO.\n",
+ "type": "string"
+ },
+ "vduId": {
+ "description": "An identifier that is unique within a VNF descriptor.\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 5.5.4.9. Additional values are also permitted. See note 1.\n",
+ "type": "string",
+ "enum": [
+ "Deployment",
+ "Statefulset"
+ ]
+ },
+ "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 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"
}
}
+ }
+ }
+ }
+ },
+ "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 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"
+ },
+ "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 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"
+ },
+ "_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 using an absolute URI.\n",
+ "type": "object",
+ "required": [
+ "href"
+ ],
+ "properties": {
+ "href": {
+ "description": "String formatted according to IETF RFC 3986.\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 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"
+ "indicators": {
+ "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"
+ }
+ }
},
- "_links": {
- "description": "Links to resources related to this resource.\n",
+ "instantiate": {
+ "description": "This type represents a link to a resource using an absolute URI.\n",
"type": "object",
"required": [
- "self"
+ "href"
],
"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"
- }
- }
+ "href": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ }
+ }
+ },
+ "terminate": {
+ "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"
+ }
+ }
+ },
+ "scale": {
+ "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"
+ }
+ }
+ },
+ "scaleToLevel": {
+ "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"
+ }
+ }
+ },
+ "changeFlavour": {
+ "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"
+ }
+ }
+ },
+ "heal": {
+ "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"
+ }
+ }
+ },
+ "operate": {
+ "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"
+ }
+ }
+ },
+ "changeExtConn": {
+ "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"
+ }
+ }
+ },
+ "createSnapshot": {
+ "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"
+ }
+ }
+ },
+ "revertToSnapshot": {
+ "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"
+ }
+ }
+ },
+ "changeCurrentVnfPkg": {
+ "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"
+ }
+ }
+ }
+ }
+ }
+ }
+ },
+ "vnfcSnapshots": {
+ "description": "Information about VNFC snapshots constituting this VNF snapshot.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents a VNFC snapshot.\nNOTE 1:\tThe identifier of the compute snapshot resource is assigned during creation of a VNFC snapshot \n being returned from the VIM as output data in the response message of the individual resource \n operations. This attribute shall only be present for a VNFC snapshot that has been newly created \n by the VNFM as a result of the \"Create VNF snapshot task\".\nNOTE 2:\tThe identifier of the storage snapshot resource is assigned during creation of a VNFC snapshot being \n returned from the VIM as output data in the response message of the individual resource operations. \n This attribute shall only be present for a VNFC snapshot with an associated storage resource and that \n has been newly created by the VNFM as a result of the \"Create VNF snapshot task\".\n",
+ "type": "object",
+ "required": [
+ "id",
+ "vnfcInstanceId",
+ "triggeredAt",
+ "vnfcResourceId"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\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 to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "creationFinishedAt": {
+ "description": "Date-time stamp. Representation: String formatted according to 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": {
+ "required": [
+ "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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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"
},
- "vnfStateSnapshot": {
- "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"
- }
- }
+ "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 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"
}
}
+ },
+ "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": "Mapping of the storage resources associated to the VNFC with the storage snapshot resources.\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"
+ },
+ "storageSnapshotResource": {
+ "description": "This 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"
+ }
+ }
+ }
+ },
+ "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 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"
+ }
+ }
+ }
+ },
+ "vnfStateSnapshotInfo": {
+ "description": "This type represents information about VNF-specific state snapshot data.\n",
+ "type": "object",
+ "required": [
+ "checksum",
+ "isEncrypted"
+ ],
+ "properties": {
+ "checksum": {
+ "description": "Cheksum description\n",
+ "type": "string"
+ },
+ "isEncrypted": {
+ "description": "The Boolean is a data type having two values (true and false).\n",
+ "type": "boolean"
+ },
+ "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 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"
+ }
+ }
+ },
+ "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 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"
+ },
+ "_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 using an absolute URI.\n",
+ "type": "object",
+ "required": [
+ "href"
+ ],
+ "properties": {
+ "href": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ }
+ }
+ },
+ "vnfStateSnapshot": {
+ "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"
}
+ }
+ }
}
}
+ }
+ }
}
}
\ No newline at end of file
diff --git a/SOL003/VNFLifecycleManagement-API/schemas/VnfSnapshotsInfo.schema.json b/SOL003/VNFLifecycleManagement-API/schemas/VnfSnapshotsInfo.schema.json
index 8347ed0a5dec47b7321292909ca5dfa4f1218a3e..29623d2df1d4b59454598ca67552abe6265c3980 100644
--- a/SOL003/VNFLifecycleManagement-API/schemas/VnfSnapshotsInfo.schema.json
+++ b/SOL003/VNFLifecycleManagement-API/schemas/VnfSnapshotsInfo.schema.json
@@ -1,1546 +1,2433 @@
{
"type": "array",
- "items":
- {
- "description": "This type represents an \"Individual VNF snapshot\" resource. It shall comply with the provisions defined in table 5.5.2.22-1.\n",
- "type": "object",
- "required": [
- "id",
- "_links"
- ],
- "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 5.5.2.23-1.\n",
- "type": "object",
- "required": [
- "id",
- "vnfInstanceId",
- "triggeredAt",
- "vnfdId",
- "vnfInfo",
- "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",
- "type": "string"
- },
- "creationStartedAt": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "creationFinishedAt": {
- "description": "Date-time stamp. Representation: String formatted according to 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.\n",
- "type": "object",
- "required": [
- "id",
- "vnfdId",
- "vnfProvider",
- "vnfProductName",
- "vnfSoftwareVersion",
- "vnfdVersion",
- "instantiationState"
- ],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfInstanceName": {
- "description": "Name of the VNF instance. This attribute can be modified with the PATCH method.\n",
- "type": "string"
- },
- "vnfInstanceDescription": {
- "description": "Human-readable description of the VNF instance. This attribute can be modified with the PATCH method.\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.\n",
- "type": "string"
- },
- "vnfdVersion": {
- "description": "A version.\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 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"
- },
- "vimConnectionInfo": {
- "description": "Information about VIM 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 VNF-related resource management in direct mode is pplicable. This attribute can be modified with the PATCH method.\n",
- "type": "object",
- "additionalProperties": {
- "description": "This type represents parameters to connect to a VIM for managing the resources of a VNF instance. This structure is used to convey VIM-related parameters over the Or-Vnfm interface. Additional parameters for a VIM may be configured into the VNFM by means outside the scope of the present document, and bound to the identifier of that VIM.\n",
- "type": "object",
- "required": [
- "vimType"
- ],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vimType": {
- "description": "Discriminator for the different types of the VIM information. The value of this attribute determines the structure of the \"interfaceInfo\" and \"accessInfo\" attributes, based on the type of the VIM. The set of permitted values is expected to change over time as new types or versions of VIMs become available. The ETSI NFV registry of VIM-related information provides access to information about VimConnectionInfo definitions for various VIM types. The structure of the registry is defined in Annex C of SOL003.\n",
- "type": "string"
- },
- "interfaceInfo": {
- "description": "This 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"
- },
- "accessInfo": {
- "description": "This 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"
- },
- "extra": {
- "description": "This 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"
- }
- }
- }
- },
- "instantiationState": {
- "description": "The instantiation state of the VNF.\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"
- ],
- "properties": {
- "flavourId": {
- "description": "An identifier that is unique within a VNF descriptor.\n",
- "type": "string"
- },
- "vnfState": {
- "description": "STARTED: The VNF instance is up and running. STOPPED: The VNF instance has been shut down.\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. This attribute shall be present if the VNF supports scaling. See clause B.2 for an explanation of VNF scaling.\n",
- "type": "array",
- "items": {
- "required": [
- "aspectId",
- "scaleLevel"
- ],
- "type": "object",
- "properties": {
- "aspectId": {
- "description": "An identifier that is unique within a VNF descriptor.\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"
- }
- }
- }
- },
- "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": "An identifier that is unique within a VNF descriptor.\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"
- }
- }
- }
- },
- "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 5.5.3.25 1.\n",
- "type": "object",
- "required": [
- "id",
- "cpdId",
- "cpConfigId",
- "cpProtocolInfo"
- ],
- "oneOf": [{
- "required": [
- "associatedVnfcCpId"
- ]
- },
- {
- "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": "An identifier that is unique within a VNF descriptor.\n",
- "type": "string"
- },
- "cpConfigId": {
- "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"
- },
- "cpProtocolInfo": {
- "description": "Network protocol information for this CP.\n",
- "type": "array",
- "items": {
- "description": "This type describes the protocol layer(s) that a CP uses together with protocol-related information, like addresses.\n",
- "type": "object",
- "required": [
- "layerProtocol"
- ],
- "properties": {
- "layerProtocol": {
- "description": "The identifier of layer(s) and protocol(s) associated to the network address information. Permitted values: IP_OVER_ETHERNET 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": "string",
- "enum": [
- "IP_OVER_ETHERNET"
- ]
- },
- "ipOverEthernet": {
- "description": "This type represents information about a network address that has been assigned.\n",
- "type": "object",
- "anyOf": [{
- "required": [
- "macAddress"
- ]
- },
- {
- "required": [
- "ipAddresses"
- ]
- }
- ],
- "oneOf": [{
- "required": [
- "addresses"
- ]
- },
- {
- "required": [
- "addressRange"
- ]
- }
- ],
- "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. If the Cp instance represents a subport in a trunk, segmentationId shall be present. Otherwise it shall not be present. 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": "string"
- },
- "ipAddresses": {
- "description": "Addresses assigned to the CP instance. Each entry represents IP addresses assigned by fixed or dynamic IP address assignment per subnet. At least one of \"macAddress\" or \"ipAddresses\" shall be present.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": [
- "type"
- ],
- "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). Exactly one of \"addresses\" or \"addressRange\" 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"
- }
- },
- "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.\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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- }
- }
- }
- }
- }
- }
- }
- }
- },
- "extLinkPortId": {
- "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 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"
- },
- "associatedVnfcCpId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "associatedVnfVirtualLinkId": {
- "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": {
- "type": "object",
- "required": [
- "id",
- "resourceHandle",
- "currentVnfExtCpData"
- ],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceHandle": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\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.\n",
- "type": "object",
- "required": [
- "id",
- "resourceHandle"
- ],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceHandle": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\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"
- }
- }
- }
- },
- "currentVnfExtCpData": {
- "description": "Allows the API consumer to read the current CP configuration information for the connection of external CPs to the external virtual link. This attribute reflects the current configuration information that has resulted from merging into this attribute the \"VnfExtCpData\" information which was passed as part of the \"ExtVirtualLinkData\" structure in the input of the most recent VNF LCM operation such as \"InstantiateVnfRequest\", \"ChangeExtVnfConnectivityRequest\", \"ChangeVnfFlavourRequest\" or \"ChangeCurrentVnfPkgRequest\", or has been provided by the NFVO during the granting procedure. If applying such change results in an empty list of \"currentVnfExtCpData\" structure instances, the affected instance of \"ExtVirtualLinkInfo\" shall be removed from its parent data structure.\n",
- "type": "array",
- "items": {
- "description": "This type represents configuration information for external CPs created from a CPD.\n",
- "type": "object",
- "required": [
- "cpdId"
- ],
- "properties": {
- "cpdId": {
- "description": "An identifier that is unique within a VNF descriptor.\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 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). 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. 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.\n",
- "type": "object",
- "additionalProperties": {
- "description": "This type represents an externally provided link port or network address information per instance of an external connection point. In case a link port is provided, the VNFM shall use that link port when connecting the external CP to the external VL. In a link port is not provided, the VNFM shall create a link port on the external VL, and use that link port to connect the external CP to the external VL.\n",
- "anyOf": [{
- "required": [
- "linkPortId"
- ]
- },
- {
- "required": [
- "cpProtocolData"
- ]
- }
- ],
- "type": "object",
- "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"
- },
- "cpProtocolData": {
- "description": "Parameters for configuring the network protocols on the link port that connects the CP to a VL. The following conditions apply to the attributes \"linkPortId\" and \"cpProtocolData\": 1) Void 2) At least one of the \"linkPortId\" and \"cpProtocolData\" attributes \n shall be present for an external CP instance representing a subport \n that is to be created, or an external CP instance that is to be created \n by creating the corresponding VNFC or VNF instance during the current or \n a subsequent LCM operation, or for an existing external CP instance \n that is to be re-configured or added to a particular external virtual link.\n3) If the \"linkPortId\" attribute is absent, the VNFM shall create a\n link port.\n4) If the \"cpProtocolData\" attribute is absent, the \"linkPortId\"\n attribute shall be provided referencing a pre-created link port,\n and the VNFM can use means outside the scope of the present\n document to obtain the pre-configured address information for the\n connection point from the resource representing the link port.\n5) If both \"cpProtocolData\" and \"linkportId\" are provided, the API\n consumer shall ensure that the cpProtocolData can be used with the\n pre-created link port referenced by \"linkPortId\".\n",
- "type": "array",
- "items": {
- "description": "This type represents network protocol data.\n",
- "type": "object",
- "required": [
- "layerProtocol"
- ],
- "properties": {
- "layerProtocol": {
- "description": "Identifier of layer(s) and protocol(s). 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": "string",
- "enum": [
- "IP_OVER_ETHERNET"
- ]
- },
- "ipOverEthernet": {
- "description": "This type represents network address data for IP over Ethernet.\n",
- "type": "object",
- "anyOf": [{
- "required": [
- "macAddress"
- ]
- },
- {
- "required": [
- "ipAddresses"
- ]
- }
- ],
- "oneOf": [{
- "required": [
- "fixedAddresses"
- ]
- },
- {
- "required": [
- "numDynamicAddresses"
- ]
- },
- {
- "required": [
- "ipAddressRange"
- ]
- }
- ],
- "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. If the Cp instance represents a subport in a trunk, segmentationId shall be present. Otherwise it shall not be present. 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": "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.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": [
- "type"
- ],
- "properties": {
- "type": {
- "description": "The type of the IP addresses. Permitted values: IPV4, 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). Exactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present.\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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- },
- "extManagedVirtualLinkInfo": {
- "description": "Information about the externally-managed internal VLs of the VNF instance.\nNOTE: 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 VNF internal VL shall indicate so by referencing to the same VnfVirtualLinkDesc and externally-managed multi-site VL instance (refer to clause 5.5.3.3).\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": [
- "id",
- "vnfVirtualLinkDescId",
- "networkResource"
- ],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfVirtualLinkDescId": {
- "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"
- },
- "networkResource": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
- "type": "string"
- }
- }
- },
- "vnfLinkPorts": {
- "description": "Link ports of this VL.\n",
- "type": "array",
- "items": {
- "type": "object",
- "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": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\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.\n",
- "type": "string",
- "enum": [
- "VNFC_CP",
- "EXT_CP"
- ]
- }
- }
- }
- },
- "extManagedMultisiteVirtualLinkId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- }
- }
- }
- },
- "monitoringParameters": {
- "description": "Active monitoring parameters.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": [
- "id",
- "performanceMetric"
- ],
- "properties": {
- "id": {
- "description": "An identifier that is unique within a VNF descriptor.\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.\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"
- },
- "vduId": {
- "description": "An identifier that is unique within a VNF descriptor.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "computeResource": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
- "type": "string"
- }
- }
- },
- "zoneId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "storageResourceIds": {
- "description": "References to the VirtualStorage resources. 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": "All the 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. 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. 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 VNF descriptor.\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. The information can be omitted because it is already available as part of the external CP information.\n",
- "type": "array",
- "items": {
- "description": "This type describes the protocol layer(s) that a CP uses together with protocol-related information, like addresses.\n",
- "type": "object",
- "required": [
- "layerProtocol"
- ],
- "properties": {
- "layerProtocol": {
- "description": "The identifier of layer(s) and protocol(s) associated to the network address information. Permitted values: IP_OVER_ETHERNET 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": "string",
- "enum": [
- "IP_OVER_ETHERNET"
- ]
- },
- "ipOverEthernet": {
- "description": "This type represents information about a network address that has been assigned.\n",
- "type": "object",
- "anyOf": [{
- "required": [
- "macAddress"
- ]
- },
- {
- "required": [
- "ipAddresses"
- ]
- }
- ],
- "oneOf": [{
- "required": [
- "addresses"
- ]
- },
- {
- "required": [
- "addressRange"
- ]
- }
- ],
- "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. If the Cp instance represents a subport in a trunk, segmentationId shall be present. Otherwise it shall not be present. 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": "string"
- },
- "ipAddresses": {
- "description": "Addresses assigned to the CP instance. Each entry represents IP addresses assigned by fixed or dynamic IP address assignment per subnet. At least one of \"macAddress\" or \"ipAddresses\" shall be present.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": [
- "type"
- ],
- "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). Exactly one of \"addresses\" or \"addressRange\" 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"
- }
- },
- "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.\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 other resource provider. It is expected to be unique within the VIM instance.\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": "This 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"
- }
- }
- }
- },
- "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 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"
- }
- }
- }
- },
- "virtualLinkResourceInfo": {
- "description": "Information about the virtualised network resources used by the VLs of the VNF instance.\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"
- },
- "vnfVirtualLinkDescId": {
- "description": "An identifier that is unique within a VNF descriptor.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "networkResource": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
- "type": "string"
- }
- }
- },
- "zoneId": {
- "description": "An identifier with the intention of being globally unique.\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",
- "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": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\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.\n",
- "type": "string",
- "enum": [
- "VNFC_CP",
- "EXT_CP"
- ]
- }
- }
- }
- },
- "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 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"
- }
- }
- }
- },
- "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": "An identifier that is unique within a VNF descriptor.\n",
- "type": "string"
- },
- "vnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "storageResource": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
- "type": "string"
- }
- }
- },
- "zoneId": {
- "description": "An identifier with the intention of being globally unique.\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 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"
- }
- }
- }
- }
- }
- },
- "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 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"
- },
- "extensions": {
- "description": "Additional VNF-specific attributes that affect the lifecycle management of this VNF instance. These attributes represent values that are stored persistently in the VnfInstance structure for consumption by the VNFM or the lifecycle management scripts during the execution of VNF lifecycle management operations. All extensions that are allowed for the VNF are declared in the VNFD. The declaration of an extension in the VNFD contains information on whether its presence is optional or required, and optionally can specify an initial value. See note 2 and note 4. The VNFM shall reject requests to write extension attributes that are not declared in the VNFD with a \"422 Unprocessable entity\" error response as defined in clause 6.4 of ETSI GS NFV-SOL 013. Modifying the values of these attributes has no direct effect on the VNF instance; however, the modified attribute values can be considered during subsequent VNF lifecycle management operations, which means that the modified values can indirectly affect the configuration of the VNF instance. These attributes can be initialized with default values from the VNFD. These attributes can be modified with values passed in the request structures of certain LCM operations, such as the InstantiateVnfRequest structure. Further, these attributes can be created, modified or deleted with the PATCH method.\nNOTE: Upon creation of the VnfInstance structure, the VNFM shall create and initialize all child attributes of \"vnfConfigurableProperties\", \"metadata\" and \"extensions\" that were declared in the VNFD with a defined initial value. The defined initial values can be declared in the VNFD, and/or, in case of \"metadata\", obtained from the \"CreateVnfRequest\" structure. Child attributes of \"vnfConfigurableProperties\", \"metadata\" and \"extensions\" that have no defineddeclared initial value shall not be created, in order to be consistent with the semantics of the JSON Merge Patch method (see IETF RFC 7396) that interprets null values as deletion request.\n"
- },
- "_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 using an absolute URI.\n",
- "type": "object",
- "required": [
- "href"
- ],
- "properties": {
- "href": {
- "description": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- }
- }
- },
- "indicators": {
- "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"
- }
- }
- },
- "instantiate": {
- "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"
- }
- }
- },
- "terminate": {
- "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"
- }
- }
- },
- "scale": {
- "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"
- }
- }
- },
- "scaleToLevel": {
- "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"
- }
- }
- },
- "changeFlavour": {
- "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"
- }
- }
- },
- "heal": {
- "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"
- }
- }
- },
- "operate": {
- "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"
- }
- }
- },
- "changeExtConn": {
- "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"
- }
- }
- },
- "createSnapshot": {
- "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"
- }
- }
- },
- "revertToSnapshot": {
- "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"
- }
- }
- }
- }
- }
- }
- },
- "vnfcSnapshots": {
- "description": "Information about VNFC snapshots constituting this VNF snapshot.\n",
- "type": "array",
- "items": {
- "description": "This type represents a VNFC snapshot.\n",
- "type": "object",
- "required": [
- "id",
- "vnfcInstanceId",
- "triggeredAt",
- "vnfcResourceId"
- ],
- "properties": {
- "id": {
- "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\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 to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "creationFinishedAt": {
- "description": "Date-time stamp. Representation: String formatted according to 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": {
- "required": [
- "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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
- "type": "string"
- }
- }
- },
- "storageSnapshotResources": {
- "description": "Mapping of the storage resources associated to the VNFC with the storage snapshot resources.\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"
- },
- "storageSnapshotResource": {
- "description": "This 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"
- }
- }
- }
- },
- "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 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"
- }
- }
- }
- },
- "vnfStateSnapshotInfo": {
- "description": "This type represents information about VNF-specific state snapshot data.\n",
- "type": "object",
- "required": [
- "checksum",
- "isEncrypted"
- ],
- "properties": {
- "checksum": {
- "description": "Checksum of the VNF state snapshot file. Hash algorithms applicable to VNF snapshot package artifacts are defined in ETSI GS NFV-SOL 010. $ref: \"../definitions/SOL002SOL003_def.yaml#/definitions/Checksum\"\n"
- },
- "isEncrypted": {
- "description": "Reflects whether the VNF state snapshot content is encrypted (true) or not (false). $ref: \"../definitions/SOL002SOL003_def.yaml#/definitions/Boolean\"\n"
- },
- "metadata": {
- "description": "The metadata with additional information such as content type, size, creation date, etc. $ref: \"../definitions/SOL002SOL003_def.yaml#/definitions/KeyValuePairs\"\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 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"
- },
- "_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 using an absolute URI.\n",
- "type": "object",
- "required": [
- "href"
- ],
- "properties": {
- "href": {
- "description": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- }
- }
- },
- "vnfStateSnapshot": {
- "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"
- }
- }
- }
- }
- }
- }
- },
- "_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 using an absolute URI.\n",
- "type": "object",
- "required": [
- "href"
- ],
- "properties": {
- "href": {
- "description": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- }
- }
- },
- "takenFrom": {
- "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"
- }
- }
- }
- }
- }
- }
+ "items": {
+ "description": "This type represents an \"Individual VNF snapshot\" resource.\n",
+ "type": "object",
+ "required": ["id", "_links"],
+ "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.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "vnfInstanceId",
+ "triggeredAt",
+ "vnfdId",
+ "vnfInfo",
+ "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",
+ "type": "string"
+ },
+ "creationStartedAt": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "creationFinishedAt": {
+ "description": "Date-time stamp. Representation: String formatted according to 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.\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",
+ "type": "object",
+ "required": [
+ "id",
+ "vnfdId",
+ "vnfProvider",
+ "vnfProductName",
+ "vnfSoftwareVersion",
+ "vnfdVersion",
+ "instantiationState",
+ "_links"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfInstanceName": {
+ "description": "Name of the VNF instance. This attribute can be modified with the PATCH method.\n",
+ "type": "string"
+ },
+ "vnfInstanceDescription": {
+ "description": "Human-readable description of the VNF instance. This attribute can be modified with the PATCH method.\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.\n",
+ "type": "string"
+ },
+ "vnfdVersion": {
+ "description": "A version.\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 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"
+ },
+ "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",
+ "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",
+ "type": "object",
+ "required": ["vimType"],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vimType": {
+ "description": "Discriminator for the different types of the VIM information. The value of this attribute determines the structure of the \"interfaceInfo\" and \"accessInfo\" attributes, based on the type of the VIM., CISM, CIR or MCIOP repository. The set of permitted values is expected to change over time as new types or versions of VIMs become available. The ETSI NFV registry of VIM-related information [i.3] provides access to information about VimConnectionInfo definitions for various VIM, CISM, CIR or MCIOP repository types. The structure of the registry is defined in annex C.\n",
+ "type": "string"
+ },
+ "interfaceInfo": {
+ "description": "This 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"
+ },
+ "accessInfo": {
+ "description": "This 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"
+ },
+ "extra": {
+ "description": "This 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"
+ }
+ }
+ }
+ },
+ "cirConnectionInfo": {
+ "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",
+ "type": "object",
+ "required": ["vimType"],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vimType": {
+ "description": "Discriminator for the different types of the VIM information. The value of this attribute determines the structure of the \"interfaceInfo\" and \"accessInfo\" attributes, based on the type of the VIM., CISM, CIR or MCIOP repository. The set of permitted values is expected to change over time as new types or versions of VIMs become available. The ETSI NFV registry of VIM-related information [i.3] provides access to information about VimConnectionInfo definitions for various VIM, CISM, CIR or MCIOP repository types. The structure of the registry is defined in annex C.\n",
+ "type": "string"
+ },
+ "interfaceInfo": {
+ "description": "This 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"
+ },
+ "accessInfo": {
+ "description": "This 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"
+ },
+ "extra": {
+ "description": "This 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"
+ }
+ }
+ }
+ },
+ "mciopRepositoryInfo": {
+ "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",
+ "type": "object",
+ "required": ["vimType"],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vimType": {
+ "description": "Discriminator for the different types of the VIM information. The value of this attribute determines the structure of the \"interfaceInfo\" and \"accessInfo\" attributes, based on the type of the VIM., CISM, CIR or MCIOP repository. The set of permitted values is expected to change over time as new types or versions of VIMs become available. The ETSI NFV registry of VIM-related information [i.3] provides access to information about VimConnectionInfo definitions for various VIM, CISM, CIR or MCIOP repository types. The structure of the registry is defined in annex C.\n",
+ "type": "string"
+ },
+ "interfaceInfo": {
+ "description": "This 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"
+ },
+ "accessInfo": {
+ "description": "This 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"
+ },
+ "extra": {
+ "description": "This 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"
+ }
+ }
+ }
+ },
+ "instantiationState": {
+ "description": "The instantiation state of the VNF. Permitted 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": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "vnfState": {
+ "description": "STARTED: The VNF instance is up and running. STOPPED: The VNF instance has been shut down.\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. This attribute shall be present if the VNF supports scaling. See clause B.2 for an explanation of VNF scaling.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents the scale level of a VNF instance related to a scaling aspect.\n",
+ "type": "object",
+ "required": ["aspectId", "scaleLevel"],
+ "properties": {
+ "aspectId": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "scaleToLevel": {
+ "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": {
+ "description": "This type represents the scale level of a VNF instance related to a scaling aspect.\n",
+ "type": "object",
+ "required": ["aspectId", "scaleLevel"],
+ "properties": {
+ "aspectId": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "scaleToLevel": {
+ "description": "An identifier with the intention of being globally unique.\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.\nNOTE 1:\tThe attributes \"associatedVnfcCpId\", \"associatedVipCpId\", \"associatedVirtualCpId\" and \n \"associatedVnfVirtualLinkId\" are mutually exclusive. Exactly one shall be present.\nNOTE 2:\tAn external CP instance is not associated to a link port in the cases indicated for the \n “extLinkPorts†attribute in clause 4.4.1.11.\nNOTE 3: 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 \n CP, e.g. to build a link redundant mated pair in SR-IOV cases.\nNOTE 4: When more than one netAttDefResourceId is indicated, all shall belong to the same namespace.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "cpdId",
+ "cpConfigId",
+ "cpProtocolInfo"
+ ],
+ "oneOf": [
+ {
+ "required": ["associatedVnfcCpId"]
+ },
+ {
+ "required": ["associatedVipCpId"]
+ },
+ {
+ "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": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "cpConfigId": {
+ "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"
+ },
+ "cpProtocolInfo": {
+ "description": "Network protocol information for this CP.\n",
+ "type": "array",
+ "items": {
+ "description": "This type describes the protocol layer(s) that a CP uses together with protocol-related information, like addresses.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the \n present document in a backwards-compatible way. In the current version of the present document, only IP over \n Ethernet is supported.\n",
+ "type": "object",
+ "required": ["layerProtocol"],
+ "properties": {
+ "layerProtocol": {
+ "description": "The identifier of layer(s) and protocol(s) associated to the network address information.\nPermitted 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:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, segmentationId shall be present. \n Otherwise it shall not be present.\nNOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the \n actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the \n transport header of the packets or it may be an identifier used between the application \n and the NFVI networking infrastructure to identify the network sub-interface of the trunk \n port in question. In the latter case the NFVI infrastructure will map this local segmentationId \n to whatever segmentationId is actually used by the NFVI’s transport technology.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "required": ["macAddress"]
+ },
+ {
+ "required": ["ipAddresses"]
+ }
+ ],
+ "oneOf": [
+ {
+ "required": ["addresses"]
+ },
+ {
+ "required": ["addressRange"]
+ }
+ ],
+ "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 notes 3 and 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"],
+ "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. 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.\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"
+ },
+ "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 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"
+ },
+ "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"
+ },
+ "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 with the intention of being 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",
+ "minItems": 1,
+ "items": {
+ "description": "This type provides information related to virtual IP (VIP) CP.\nNOTE 1:\tIt is possible that there is no associated VnfcCp because the VIP CP is available but not associated yet. NOTE 2: If only the value or the presence of this attribute is changed in the \"VipCpInfo\" structure by an LCM operation occurrence, this does not represent a change that requires including a related \"AffectedVipCp\" structure in the VNF LCM operation occurrence notifications or the \"VnfLcmOpOcc\" structure related to this LCM operation occurrence.\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": "An identifier that is unique within a VNF descriptor.\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 uses together with protocol-related information, like addresses.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the \n present document in a backwards-compatible way. In the current version of the present document, only IP over \n Ethernet is supported.\n",
+ "type": "object",
+ "required": ["layerProtocol"],
+ "properties": {
+ "layerProtocol": {
+ "description": "The identifier of layer(s) and protocol(s) associated to the network address information.\nPermitted 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:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, segmentationId shall be present. \n Otherwise it shall not be present.\nNOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the \n actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the \n transport header of the packets or it may be an identifier used between the application \n and the NFVI networking infrastructure to identify the network sub-interface of the trunk \n port in question. In the latter case the NFVI infrastructure will map this local segmentationId \n to whatever segmentationId is actually used by the NFVI’s transport technology.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "required": ["macAddress"]
+ },
+ {
+ "required": ["ipAddresses"]
+ }
+ ],
+ "oneOf": [
+ {
+ "required": ["addresses"]
+ },
+ {
+ "required": ["addressRange"]
+ }
+ ],
+ "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 notes 3 and 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"],
+ "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. 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.\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": "This 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"
+ }
+ }
+ }
+ },
+ "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 provides information related to a virtual CP instance of a VNF.\nNOTE: A consumer of the VNF LCM interface can learn the actual VNFC instances implementing the service \n accessible via the virtual CP instance by querying the \"vnfcResourceInfo\" from the \"InstantiatedVnfInfo\" \n and filtering by corresponding \"vduIds\" values.\n",
+ "type": "object",
+ "required": [
+ "cpInstanceId",
+ "cpdId",
+ "resourceHandle",
+ "vduIds"
+ ],
+ "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": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "resourceHandle": {
+ "required": ["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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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 uses together with protocol-related information, like addresses.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the \n present document in a backwards-compatible way. In the current version of the present document, only IP over \n Ethernet is supported.\n",
+ "type": "object",
+ "required": ["layerProtocol"],
+ "properties": {
+ "layerProtocol": {
+ "description": "The identifier of layer(s) and protocol(s) associated to the network address information.\nPermitted 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:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, segmentationId shall be present. \n Otherwise it shall not be present.\nNOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the \n actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the \n transport header of the packets or it may be an identifier used between the application \n and the NFVI networking infrastructure to identify the network sub-interface of the trunk \n port in question. In the latter case the NFVI infrastructure will map this local segmentationId \n to whatever segmentationId is actually used by the NFVI’s transport technology.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "required": ["macAddress"]
+ },
+ {
+ "required": ["ipAddresses"]
+ }
+ ],
+ "oneOf": [
+ {
+ "required": ["addresses"]
+ },
+ {
+ "required": ["addressRange"]
+ }
+ ],
+ "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 notes 3 and 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"],
+ "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. 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.\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"
+ }
+ }
+ }
+ }
+ }
+ },
+ "vduIds": {
+ "description": "Reference to the VDU(s) which implement the service accessible via the virtual CP instance. See note.\n",
+ "type": "array",
+ "minItems": 1,
+ "items": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ }
+ },
+ "additionalServiceInfo": {
+ "description": "Additional service identification information of the virtual CP instance.\n",
+ "type": "array",
+ "items": {
+ "description": "This type provides 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 \n termination within the VNF, such as for example a URL path information in an HTTP request required \n to allow a single virtual CP IP address to be used for several HTTP based services that use the \n same port number.\n",
+ "type": "object",
+ "required": ["portInfo"],
+ "properties": {
+ "portInfo": {
+ "description": "Service port numbers exposed by the virtual CP instance.\n",
+ "minItems": 1,
+ "type": "array",
+ "items": {
+ "description": "This type describes the service identifying port properties exposed by the virtual CP instance.\n",
+ "type": "object",
+ "required": [
+ "name",
+ "port",
+ "portConfigurable"
+ ],
+ "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.\nPermitted values: - TCP - UDP - SCTP\n",
+ "type": "string",
+ "enum": ["TCP", "UDP", "SCTP"]
+ },
+ "port": {
+ "description": "The L4 port number exposed by the virtual CP instance.\n",
+ "type": "integer"
+ },
+ "portConfigurable": {
+ "description": "The Boolean is a data type having two values (true and false).\n",
+ "type": "boolean"
+ }
+ }
+ }
+ },
+ "serviceInfo": {
+ "description": "This 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"
+ }
+ }
+ }
+ },
+ "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 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"
+ }
+ }
+ }
+ },
+ "extVirtualLinkInfo": {
+ "description": "Information about the external VLs the VNF instance is connected to.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents information about an external VL.\nNOTE:\tThis attribute reflects the current configuration information that has resulted from merging into this attribute \n the \"VnfExtCpData\" information which was passed as part of the \"ExtVirtualLinkData\" structure in the input of the \n most recent VNF LCM operation such as \"InstantiateVnfRequest\", \"ChangeExtVnfConnectivityRequest\", \"ChangeVnfFlavourRequest\" \n or \"ChangeCurrentVnfPkgRequest\", or in the Grant response. If applying such change results in an empty list of \n \"currentVnfExtCpData\" structure instances, the affected instance of \"ExtVirtualLinkInfo\" shall be removed from its \n parent data structure.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "resourceHandle",
+ "currentVnfExtCpData"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceHandle": {
+ "required": ["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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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.\nNOTE 1:\tThe use cases UC#4 and UC#5 in clause A.4 of ETSI GS NFV-IFA 007 provide examples for such a configuration. NOTE 2:\tThe 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": {
+ "required": ["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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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 the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "currentVnfExtCpData": {
+ "description": "Allows the API consumer to read the current CP configuration information for the connection of external CPs to the external virtual link. See note.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents configuration information for external CPs created. * NOTE 1: \tIn case this identifier refers to a CPD with trunking enabled, the external CP instances created\n from this CPD will represent ports in a trunk.\n* NOTE 2: \tWithin one VNF instance, all VNFC instances created from a particular VDU have the same external\n connectivity. Thus, given a particular value of the \"cpdId\" attribute, there shall be one\n \"cpConfig\" entry for each VNFC instance that has been or can be created from a VDU which includes\n a CPD identified by the \"cpdId\" attribute. If the cpConfig represents a subport in a trunk,\n all \"cpConfig\" entries in this list shall have the same segmentationId, which means they are\n connected to the same set of external VLs via the trunk.\n* NOTE 3: \tThe map entry value shall be set to \"null\" in order to delete a \"VnfExtCpConfig\" entry identified\n by a particular key value from the map, i.e. for the disconnection of an existing external\n CP instance addressed by cpInstanceId in the deleted map entry from a particular external\n virtual link, and deletion of that instance in case it represents a subport. Deleting the\n last key from the map removes the affected instance of the \"VnfExtCpData\" structure from\n its parent data structure.\n* NOTE 4: If, as defined by the input parameters of a \"ChangeVnfFlavour\", \"ChangeExtVnfConnectivity\" or\n \"ChangeCurrentVnfPkg\" operation or as part of the Grant response for any of these operations, a cpConfig\n map entry identified by a particular map key value is moved into another \"ExtVirtualLinkData\" or\n \"VnfExtCpData\" structure, this particular cpConfig map entry may be used by an external CP instance\n different than the one that has used it before the operation, or by no external CP instance at all.\n Renaming a CPD identifier during the \"changeCurrentVnfPkg\" operation does not count as moving the related\n \"cpConfig\" map entries to a new \"extCpData\" structure.\n",
+ "type": "object",
+ "required": ["cpdId"],
+ "properties": {
+ "cpdId": {
+ "description": "An identifier that is unique within a VNF descriptor.\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 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",
+ "anyOf": [
+ {
+ "required": ["linkPortId"]
+ },
+ {
+ "required": ["cpProtocolData"]
+ },
+ {
+ "required": ["netAttDefResourceId"]
+ }
+ ],
+ "type": "object",
+ "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 to the VNFM the need to create a dedicated link port for the external CP. If set to True, the VNFM shall create a link port. If set to False, the VNFM shall not create a link port. 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"
+ },
+ "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 2, 3 and 4.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ },
+ "cpProtocolData": {
+ "description": "Parameters for configuring the network protocols on the link port that connects the CP to a VL. See notes 1 and 2.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents network protocol data. * NOTE:\tThis attribute allows to signal the addition of further types of layer and protocol\n in future versions of the present document in a backwards-compatible way. In the current\n 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:\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 network address data for IP over Ethernet. * NOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. * NOTE 2:\tExactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present. * NOTE 3:\tIf the CP instance represents a subport in a trunk, segmentationId shall be present.\n Otherwise it shall not be present.\n* NOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the actual\n network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header\n of the packets or it may be an identifier used between the application and the NFVI networking\n infrastructure to identify the network sub-interface of the trunk port in question. In the latter\n case the NFVI infrastructure will map this local segmentationId to whatever segmentationId is\n actually used by the NFVI’s transport technology.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "required": ["macAddress"]
+ },
+ {
+ "required": ["ipAddresses"]
+ }
+ ],
+ "oneOf": [
+ {
+ "required": ["fixedAddresses"]
+ },
+ {
+ "required": [
+ "numDynamicAddresses"
+ ]
+ },
+ {
+ "required": ["ipAddressRange"]
+ }
+ ],
+ "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: -\tVLAN: the subport uses VLAN as encapsulation type. -\tINHERIT: the subport gets its segmentation type from the network it’s 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"],
+ "properties": {
+ "type": {
+ "description": "The type of the IP addresses. Permitted values: IPV4, IPV6.\n",
+ "type": "string",
+ "enum": ["IPV4", "IPV6"]
+ },
+ "fixedAddresses": {
+ "description": "Fixed addresses to assign (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"
+ }
+ },
+ "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. 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.\n",
+ "type": "string"
+ }
+ }
+ }
+ }
+ }
+ },
+ "virtualCpAddress": {
+ "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",
+ "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"
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ },
+ "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 contains 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": {
+ "required": ["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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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 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 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"
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ },
+ "extManagedVirtualLinkInfo": {
+ "description": "Information about the externally-managed internal VLs of the VNF instance. See notes 5 and 6.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": [
+ "id",
+ "vnfVirtualLinkDescId",
+ "networkResource"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfVirtualLinkDescId": {
+ "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"
+ },
+ "networkResource": {
+ "required": ["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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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": {
+ "description": "This type represents a link port of an internal VL of a VNF.\nNOTE 1: Either cpInstanceId with cpInstanceType set to \"EXT_CP\" or any combination of cpInstanceId\n with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId (i.e. one or both of them) shall be \n present for a VnfLinkPortInfo. In case both cpInstanceId with cpInstanceType set to \"VNFC_CP\" \n and vipCpInstanceId are present, the two different CP instances share the linkport.\nNOTE 2: Annex A.4 of ETSI GS NFV-IFA 007 provides examples for configurations where both vipCpInstanceId\n and vnfcCpInstanceId are present (UC#5 and UC#5-b), only vnfcCpInstanceId is present (UC#2), or \n only vipCpInstanceId is present (UC6 and UC#6-b).\nNOTE 3: The value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\"\n attribute.\n",
+ "type": "object",
+ "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": {
+ "required": ["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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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.\nPermitted values: - VNFC_CP: The link port is connected to a VNFC CP. -\tEXT_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 the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "vnfNetAttDefResource": {
+ "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 contains 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": {
+ "required": ["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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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 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 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": "Active monitoring parameters.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": ["id", "performanceMetric"],
+ "properties": {
+ "id": {
+ "description": "An identifier that is unique within a VNF descriptor.\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. Depending on the form of virtualisation container of the VNFC:\n - For a VNFC based on VM, a reference to the corresponding VirtualCompute shall be provided, and\n - For a VNFC based on OS container(s), a reference to the Compute MCIO shall be provided. Hence, exposure of\n information by the VNFM to the NFVO is at the MCIO level.\nIn addition, the references to the storage resources depend on the form of the VNFC:\n a) For a VNFC based on VM, storage resource identifiers shall refer to VirtualStorage resources, and\n b) For a VNFC based on OS container(s), storage resource identifiers shall refer to Storage MCIOs.\n\nNOTE 1:\tETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on \n TOSCA specifications.\nNOTE 2:\tA VNFC CP is \"connected to\" an external CP if the VNFC CP is connected to an \n internal VL that exposes an external CP. A VNFC CP is \"exposed as\" an external \n CP if it is connected directly to an external VL.\nNOTE 3:\tThe information can be omitted because it is already available as part of the \n external CP information.\nNOTE 4: If only the value or the presence of this attribute is changed in the \"VnfcResourceInfo\"\n structure by an LCM operation occurrence, this does not represent a change that requires\n including a related \"AffectedVnfc\" structure in the VNF LCM operation occurrence notifications\n or the \"VnfLcmOpOcc\" structure related to this LCM operation occurrence.\nNOTE 5: 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 internal CP, e.g. to build a link\n redundant mated pair in SR-IOV cases.\nNOTE 6: 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"
+ },
+ "vduId": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "computeResource": {
+ "required": ["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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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"
+ }
+ }
+ },
+ "zoneId": {
+ "description": "An identifier with the intention of being globally unique.\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 VNF descriptor.\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 uses together with protocol-related information, like addresses.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the \n present document in a backwards-compatible way. In the current version of the present document, only IP over \n Ethernet is supported.\n",
+ "type": "object",
+ "required": ["layerProtocol"],
+ "properties": {
+ "layerProtocol": {
+ "description": "The identifier of layer(s) and protocol(s) associated to the network address information.\nPermitted 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:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, segmentationId shall be present. \n Otherwise it shall not be present.\nNOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the \n actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the \n transport header of the packets or it may be an identifier used between the application \n and the NFVI networking infrastructure to identify the network sub-interface of the trunk \n port in question. In the latter case the NFVI infrastructure will map this local segmentationId \n to whatever segmentationId is actually used by the NFVI’s transport technology.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "required": ["macAddress"]
+ },
+ {
+ "required": ["ipAddresses"]
+ }
+ ],
+ "oneOf": [
+ {
+ "required": ["addresses"]
+ },
+ {
+ "required": ["addressRange"]
+ }
+ ],
+ "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 notes 3 and 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"],
+ "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. 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.\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"
+ }
+ }
+ }
+ }
+ }
+ },
+ "vnfLinkPortId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "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"
+ },
+ "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 5 and 6. 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 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 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"
+ }
+ }
+ }
+ },
+ "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 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"
+ }
+ }
+ }
+ },
+ "vnfVirtualLinkResourceInfo": {
+ "description": "Information about the virtualised network resources used by the VLs of the VNF instance. See note 6.\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.\nNote: If only the value or the presence of this attribute is changed in the \"VnfVirtualLinkResourceInfo\"\n structure by an LCM operation occurrence, this does not represent a change that requires including\n a related \"AffectedVirtualLink\" structure in the VNF LCM operation occurrence notifications or the\n \"VnfLcmOpOcc\" structure related to this LCM operation occurrence.\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"
+ },
+ "vnfVirtualLinkDescId": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "networkResource": {
+ "required": ["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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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"
+ }
+ }
+ },
+ "zoneId": {
+ "description": "An identifier with the intention of being globally unique.\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": {
+ "description": "This type represents a link port of an internal VL of a VNF.\nNOTE 1: Either cpInstanceId with cpInstanceType set to \"EXT_CP\" or any combination of cpInstanceId\n with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId (i.e. one or both of them) shall be \n present for a VnfLinkPortInfo. In case both cpInstanceId with cpInstanceType set to \"VNFC_CP\" \n and vipCpInstanceId are present, the two different CP instances share the linkport.\nNOTE 2: Annex A.4 of ETSI GS NFV-IFA 007 provides examples for configurations where both vipCpInstanceId\n and vnfcCpInstanceId are present (UC#5 and UC#5-b), only vnfcCpInstanceId is present (UC#2), or \n only vipCpInstanceId is present (UC6 and UC#6-b).\nNOTE 3: The value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\"\n attribute.\n",
+ "type": "object",
+ "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": {
+ "required": ["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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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.\nPermitted values: - VNFC_CP: The link port is connected to a VNFC CP. -\tEXT_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 the CISM or other resource provider. It is expected to be unique within the VIM instance.\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 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"
+ }
+ }
+ }
+ },
+ "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.\nNote: If only the value or the presence of this attribute is changed in the \"VirtualStorageResourceInfo\"\n structure by an LCM operation occurrence, this does not represent a change that requires\n including a related \"AffectedVirtualStorage\" structure in the VNF LCM operation occurrence\n notifications or the \"VnfLcmOpOcc\" structure related to this LCM operation occurrence.\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": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "vnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "storageResource": {
+ "required": ["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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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"
+ }
+ }
+ },
+ "zoneId": {
+ "description": "An identifier with the intention of being globally unique.\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 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"
+ }
+ }
+ }
+ },
+ "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. Within the CISM, an MCIO controller monitors the actual state of an MCIO representing the set of VNFC instances realized by one or a set of OS containers and compare it to the desired state as specified in the respective declarative descriptor. It triggers actions toward the CIS to align the actual to the desired state. Monitoring the actual state includes monitoring the number of MCIO instances available at any specific point in time. In addition, an MCIO controller maintains properties and runtime information on the MCIO instances which have been created based on the same VDU. The McioInfo data structure provides the runtime information on the MCIOs obtained from the MCIO controller.\nNOTE: There are different types of MCIOs. The set of VNFC instances based on the same VDU is represented \n by one MCIO, e.g. of type Deployment. Each individual VNFC instance is represented by another type \n of MCIO, e.g. a POD.\n\nRuntime information of the set of OS containers realizing an individual VNFC instance is not part of the McioInfo data structure; such runtime information is provided in the ResourceHandle data structure referenced from the VnfcResourceInfo. The McioInfo does not provide runtime information of a constituent VNFC instance created based on a specific VDU.\nNOTE 1: The type of MCIO as specified in the declarative descriptor of the MCIO, and that can be read from \n the CISM. EXAMPLE: In case of MCIOs managed by Kubernetes®, the type of MCIO corresponds to the \n “kind†property of the declarative descriptor.\nNOTE 2: If the attribute additionalInfo is present, it may contain runtime information on the actual and \n desired state of the MCIO(s). \nNOTE 3: When the container infrastructure service is a Kubernetes® instance, the mcioId is the combined \n values from the kind and name fields of the Kubernetes resource object, separated by a slash. \n Example: \"Deployment/abcd\". \nNOTE 4: When the container infrastructure service is a Kubernetes® instance, the mcioName is the name \n field of the resource object. \n",
+ "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": "An identifier that is unique within a VNF descriptor.\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 5.5.4.9. Additional values are also permitted. See note 1.\n",
+ "type": "string",
+ "enum": ["Deployment", "Statefulset"]
+ },
+ "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 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"
+ }
+ }
+ }
+ }
+ }
+ },
+ "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 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"
+ },
+ "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 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"
+ },
+ "_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 using an absolute URI.\n",
+ "type": "object",
+ "required": ["href"],
+ "properties": {
+ "href": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ }
+ }
+ },
+ "indicators": {
+ "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"
+ }
+ }
+ },
+ "instantiate": {
+ "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"
+ }
+ }
+ },
+ "terminate": {
+ "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"
+ }
+ }
+ },
+ "scale": {
+ "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"
+ }
+ }
+ },
+ "scaleToLevel": {
+ "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"
+ }
+ }
+ },
+ "changeFlavour": {
+ "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"
+ }
+ }
+ },
+ "heal": {
+ "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"
+ }
+ }
+ },
+ "operate": {
+ "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"
+ }
+ }
+ },
+ "changeExtConn": {
+ "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"
+ }
+ }
+ },
+ "createSnapshot": {
+ "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"
+ }
+ }
+ },
+ "revertToSnapshot": {
+ "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"
+ }
+ }
+ },
+ "changeCurrentVnfPkg": {
+ "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"
+ }
+ }
+ }
+ }
+ }
+ }
+ },
+ "vnfcSnapshots": {
+ "description": "Information about VNFC snapshots constituting this VNF snapshot.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents a VNFC snapshot.\nNOTE 1:\tThe identifier of the compute snapshot resource is assigned during creation of a VNFC snapshot \n being returned from the VIM as output data in the response message of the individual resource \n operations. This attribute shall only be present for a VNFC snapshot that has been newly created \n by the VNFM as a result of the \"Create VNF snapshot task\".\nNOTE 2:\tThe identifier of the storage snapshot resource is assigned during creation of a VNFC snapshot being \n returned from the VIM as output data in the response message of the individual resource operations. \n This attribute shall only be present for a VNFC snapshot with an associated storage resource and that \n has been newly created by the VNFM as a result of the \"Create VNF snapshot task\".\n",
+ "type": "object",
+ "required": [
+ "id",
+ "vnfcInstanceId",
+ "triggeredAt",
+ "vnfcResourceId"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\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 to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "creationFinishedAt": {
+ "description": "Date-time stamp. Representation: String formatted according to 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": {
+ "required": ["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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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": "Mapping of the storage resources associated to the VNFC with the storage snapshot resources.\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"
+ },
+ "storageSnapshotResource": {
+ "description": "This 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"
+ }
+ }
+ }
+ },
+ "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 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"
+ }
+ }
+ }
+ },
+ "vnfStateSnapshotInfo": {
+ "description": "This type represents information about VNF-specific state snapshot data.\n",
+ "type": "object",
+ "required": ["checksum", "isEncrypted"],
+ "properties": {
+ "checksum": {
+ "description": "Cheksum description\n",
+ "type": "string"
+ },
+ "isEncrypted": {
+ "description": "The Boolean is a data type having two values (true and false).\n",
+ "type": "boolean"
+ },
+ "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 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"
+ }
+ }
+ },
+ "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 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"
+ },
+ "_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 using an absolute URI.\n",
+ "type": "object",
+ "required": ["href"],
+ "properties": {
+ "href": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ }
+ }
+ },
+ "vnfStateSnapshot": {
+ "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"
+ }
+ }
+ }
+ }
+ }
+ }
+ },
+ "_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 using an absolute URI.\n",
+ "type": "object",
+ "required": ["href"],
+ "properties": {
+ "href": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ }
+ }
+ },
+ "takenFrom": {
+ "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"
+ }
+ }
+ }
+ }
+ }
+ }
}
}
\ No newline at end of file
diff --git a/SOL003/VNFLifecycleManagement-API/schemas/grant.schema.json b/SOL003/VNFLifecycleManagement-API/schemas/grant.schema.json
deleted file mode 100644
index b9f967b952fb174fdd0655d536105f9b8d62787d..0000000000000000000000000000000000000000
--- a/SOL003/VNFLifecycleManagement-API/schemas/grant.schema.json
+++ /dev/null
@@ -1 +0,0 @@
-{ "description": "This type represents a grant.\n", "type": "object", "required": [ "id", "vnfInstanceId", "vnfLcmOpOccId", "_links" ], "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", "type": "string" }, "vnfLcmOpOccId": { "description": "An identifier with the intention of being globally unique.\n", "type": "string" }, "vimConnections": { "description": "Provides information regarding VIM connections that are approved to be used by the VNFM to allocate resources, and provides parameters of these VIM 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 VimConnection entries passed earlier; for that, the VnfInfoModificationRequest structure shall be used. This attribute shall only be supported when VNF-related Resource Management in direct mode is applicable. In direct mode, this parameter shall be absent if the VIM information was configured to the VNFM in another way, present otherwise. This interface allows to signal the use of multiple VIMs per VNF. However, due to the partial support of this feature in the present release, it is recommended in the present document that the number of entries in the \"vims\" attribute in the Grant is not greater than 1.\n", "type": "array", "items": { "description": "This type represents parameters to connect to a VIM for managing the resources of a VNF instance. This structure is used to convey VIM-related parameters over the Or-Vnfm interface. Additional parameters for a VIM may be configured into the VNFM by means outside the scope of the present document, and bound to the identifier of that VIM.\n", "type": "object", "required": [ "id", "vimType" ], "properties": { "id": { "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" }, "vimType": { "description": "Discriminator for the different types of the VIM information. The value of this attribute determines the structure of the \"interfaceInfo\" and \"accessInfo\" attributes, based on the type of the VIM. The set of permitted values is expected to change over time as new types or versions of VIMs become available. The ETSI NFV registry of VIM-related information provides access to information about VimConnectionInfo definitions for various VIM types. The structure of the registry is defined in Annex C of SOL003.\n", "type": "string" }, "interfaceInfo": { "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n", "type": "object" }, "accessInfo": { "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n", "type": "object" }, "extra": { "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n", "type": "object" } } } }, "zones": { "description": "Identifies resource zones where the resources are approved to be allocated by the VNFM.\n", "type": "array", "items": { "description": "This type provides information regarding a resource zone.\n", "type": "object", "required": [ "id", "zoneId" ], "properties": { "id": { "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\n", "type": "string" }, "zoneId": { "description": "An identifier with the intention of being globally unique.\n", "type": "string" }, "vimConnectionId": { "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" } } } }, "zoneGroups": { "description": "Information about groups of resource zones that are related and that the NFVO has chosen to fulfil a zoneGroup constraint in the GrantVnfLifecycleOperation request. This information confirms that the NFVO has honoured the zoneGroup constraints that were passed as part of \"placementConstraints\" in the GrantRequest.\n", "type": "array", "items": { "description": "This type provides information regarding a resource zone group. A resource zone group is a group of one or more related resource zones which can be used in resource placement constraints. To fulfil such constraint, the NFVO may decide to place a resource into any zone that belongs to a particular group. NOTE: A resource zone group can be used to support overflow from one resource zone into another, in case a particular deployment supports only non-elastic resource zones.\n", "type": "object", "required": [ "zoneId" ], "properties": { "zoneId": { "description": "References of identifiers of \"ZoneInfo\" structures, each of which provides information about a resource zone that belongs to this group.\n", "type": "array", "items": { "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\n", "type": "string" } } } } }, "computeReservationId": { "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n", "type": "string" }, "networkReservationId": { "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n", "type": "string" }, "storageReservationId": { "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n", "type": "string" }, "addResources": { "description": "List of resources that are approved to be added, with one entry per resource.\n", "type": "array", "items": { "description": "This type contains information about a Compute, storage or network resource whose addition/update/deletion was granted.\n", "type": "object", "required": [ "resourceDefinitionId" ], "properties": { "resourceDefinitionId": { "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\n", "type": "string" }, "reservationId": { "description": "An identifier with the intention of being globally unique.\n", "type": "string" }, "vimConnectionId": { "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" }, "zoneId": { "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\n", "type": "string" }, "resourceGroupId": { "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n", "type": "string" } } } }, "tempResources": { "description": "List of resources that are approved to be temporarily instantiated during the runtime of the lifecycle operation, with one entry per resource.\n", "type": "array", "items": { "description": "This type contains information about a Compute, storage or network resource whose addition/update/deletion was granted.\n", "type": "object", "required": [ "resourceDefinitionId" ], "properties": { "resourceDefinitionId": { "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\n", "type": "string" }, "reservationId": { "description": "An identifier with the intention of being globally unique.\n", "type": "string" }, "vimConnectionId": { "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" }, "zoneId": { "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\n", "type": "string" }, "resourceGroupId": { "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n", "type": "string" } } } }, "removeResources": { "description": "List of resources that are approved to be removed, with one entry per resource.\n", "type": "array", "items": { "description": "This type contains information about a Compute, storage or network resource whose addition/update/deletion was granted.\n", "type": "object", "required": [ "resourceDefinitionId" ], "properties": { "resourceDefinitionId": { "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\n", "type": "string" }, "reservationId": { "description": "An identifier with the intention of being globally unique.\n", "type": "string" }, "vimConnectionId": { "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" }, "zoneId": { "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\n", "type": "string" }, "resourceGroupId": { "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n", "type": "string" } } } }, "updateResources": { "description": "List of resources that are approved to be modified, with one entry per resource.\n", "type": "array", "items": { "description": "This type contains information about a Compute, storage or network resource whose addition/update/deletion was granted.\n", "type": "object", "required": [ "resourceDefinitionId" ], "properties": { "resourceDefinitionId": { "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\n", "type": "string" }, "reservationId": { "description": "An identifier with the intention of being globally unique.\n", "type": "string" }, "vimConnectionId": { "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" }, "zoneId": { "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\n", "type": "string" }, "resourceGroupId": { "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n", "type": "string" } } } }, "vimAssets": { "description": "Information about assets for the VNF that are managed by the NFVO in the VIM, such as software images and virtualised compute resource flavours. This attribute is not intended for the modification of vimAssets entries passed earlier. Modification of VIM assets during the lifetime of a VNF instance is not necessary, since it is expected that all applicable assets have been on boarded into the VIM before the VNF is instantiated.\n", "type": "object", "properties": { "computeResourceFlavours": { "description": "Mappings between virtual compute descriptors defined in the VNFD and compute resource flavours managed in the VIM.\n", "type": "array", "items": { "description": "If the VIM requires the use of virtual compute resource flavours during compute resource instantiation, it is assumed that such flavours are selected or created by the NFVO based on the information in the virtual compute descriptor defined in the VNFD. This type defines the mapping between a virtual compute descriptor in the VNFD and the corresponding compute resource flavour managed by the NFVO in the VIM.\n", "type": "object", "required": [ "vnfdVirtualComputeDescId", "vimFlavourId" ], "properties": { "vimConnectionId": { "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" }, "vnfdVirtualComputeDescId": { "description": "An identifier that is unique within a VNF descriptor.\n", "type": "string" }, "vimFlavourId": { "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n", "type": "string" } } } }, "softwareImages": { "description": "Mappings between software images defined in the VNFD and software images managed in the VIM.\n", "type": "array", "items": { "description": "This type contains a mapping between a software image definition the VNFD and the corresponding software image managed by the NFVO in the VIM which is needed during compute resource instantiation.\n", "type": "object", "required": [ "vnfdSoftwareImageId", "vimSoftwareImageId" ], "properties": { "vimConnectionId": { "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" }, "vnfdSoftwareImageId": { "description": "An identifier that is unique within a VNF descriptor.\n", "type": "string" }, "vimSoftwareImageId": { "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n", "type": "string" } } } } } }, "extVirtualLinks": { "description": "Information about external VLs to connect the VNF to. External and/or externally-managed internal VLs can be passed in VNF lifecycle management operation requests such as InstantiateVnf or ChangeVnfFlavor, and/or in the grant response. The NFVO may choose to override in the grant response external and/or externally-managed VL instances that have been passed previously in the associated VNF lifecycle management request, if the lifecycle management request has originated from the NFVO itself.\n", "type": "array", "items": { "description": "This type represents an external VL.\n", "type": "object", "required": [ "id", "resourceId", "extCps" ], "properties": { "id": { "description": "An identifier with the intention of being globally unique.\n", "type": "string" }, "vimConnectionId": { "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 other resource provider. It is expected to be unique within the VIM instance.\n", "type": "string" }, "extCps": { "description": "External CPs of the VNF to be connected to this external VL.\n", "type": "array", "items": { "description": "This type represents configuration information for external CPs created from a CPD.\n", "type": "object", "required": [ "cpdId" ], "properties": { "cpdId": { "description": "An identifier that is unique within a VNF descriptor.\n", "type": "string" }, "cpConfig": { "description": "List of instance data that need to be configured on the CP instances created from the respective CPD.\n", "type": "array", "items": { "description": "This type represents an externally provided link port or network address information per instance of an external connection point. In case a link port is provided, the VNFM shall use that link port when connecting the external CP to the external VL. In a link port is not provided, the VNFM shall create a link port on the external VL, and use that link port to connect the external CP to the external VL.\n", "type": "object", "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" }, "linkPortId": { "description": "An identifier with the intention of being globally unique.\n", "type": "string" }, "cpProtocolData": { "description": "Parameters for configuring the network protocols on the link port that connects the CP to a VL. The following conditions apply to the attributes \"linkPortId\" and \"cpProtocolData\": * The \"linkPortId\" and \"cpProtocolData\" attributes shall both be absent for the deletion of an existing external CP instance\n addressed by cpInstanceId. \n* At least one of these attributes shall be present for a to-be-created external CP instance or an existing external\n CP instance.\n* If the \"linkPortId\" attribute is absent, the VNFM shall create a link port.\n* If the \"cpProtocolData\" attribute is absent, the \"linkPortId\" attribute shall be provided referencing a pre-created link port,\n and the VNFM can use means outside the scope of the present\n document to obtain the pre-configured address information for the\n connection point from the resource representing the link port.\n* If both \"cpProtocolData\" and \"linkportId\" are provided, the API consumer shall ensure that the cpProtocolData can be used with the\n pre-created link port referenced by \"linkPortId\".\n", "type": "array", "items": { "description": "This type represents network protocol data.\n", "type": "object", "required": [ "layerProtocol" ], "properties": { "layerProtocol": { "description": "Identifier of layer(s) and protocol(s). 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": "string", "enum": [ "IP_OVER_ETHERNET" ] }, "ipOverEthernet": { "description": "This type represents network address data for IP over Ethernet.\n", "type": "object", "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" }, "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.\n", "type": "array", "items": { "type": "object", "required": [ "type" ], "properties": { "type": { "description": "The type of the IP addresses. Permitted values: IPV4, 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). Exactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present.\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 other resource provider. It is expected to be unique within the VIM instance.\n", "type": "string" } } } } } } } } } } } } } } }, "extLinkPorts": { "description": "Externally provided link ports to be used to connect external connection points to this external VL. If this attribute is not present, the VNFM shall create the link ports on the external VL.\n", "type": "array", "items": { "description": "This type represents an externally provided link port to be used to connect an external connection point to an external VL.\n", "type": "object", "required": [ "id", "resourceHandle" ], "properties": { "id": { "description": "An identifier with the intention of being globally unique.\n", "type": "string" }, "resourceHandle": { "required": [ "vimConnectionId", "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", "properties": { "vimConnectionId": { "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 other resource provider. It is expected to be unique within the VIM instance.\n", "type": "string" }, "vimLevelResourceType": { "description": "Type of the resource in the scope of the VIM or the resource provider.\n", "type": "string" } } } } } } } } }, "extManagedVirtualLinks": { "description": "Information about internal VLs that are managed by other entities than the VNFM. The indication of externally-managed internal VLs is needed in case networks have been pre-configured for use with certain VNFs, for instance to ensure that these networks have certain properties such as security or acceleration features, or to address particular network topologies. The present document assumes that externally-managed internal VLs are managed by the NFVO and created towards the VIM. External and/or externally-managed internal VLs can be passed in VNF lifecycle management operation requests such as InstantiateVnf or ChangeVnfFlavor, and/or in the grant response. The NFVO may choose to override in the grant response external and/or externally-managed VL instances that have been passed previously in the associated VNF lifecycle management request, if the lifecycle management request has originated from the NFVO itself.\n", "type": "array", "items": { "type": "object", "required": [ "id", "virtualLinkDescId", "resourceId" ], "properties": { "id": { "description": "An identifier with the intention of being globally unique.\n", "type": "string" }, "virtualLinkDescId": { "description": "An identifier that is unique within a VNF descriptor.\n", "type": "string" }, "vimConnectionId": { "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 other resource provider. It is expected to be unique within the VIM instance.\n", "type": "string" } } } }, "additionalParams": { "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- 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", "vnfLcmOpOcc", "vnfInstance" ], "properties": { "self": { "description": "This type represents a link to a resource.\n", "type": "object", "required": [ "href" ], "properties": { "href": { "description": "URI of the referenced resource.\n", "type": "string", "format": "url" } } }, "vnfLcmOpOcc": { "description": "This type represents a link to a resource.\n", "type": "object", "required": [ "href" ], "properties": { "href": { "description": "URI of the referenced resource.\n", "type": "string", "format": "url" } } }, "vnfInstance": { "description": "This type represents a link to a resource.\n", "type": "object", "required": [ "href" ], "properties": { "href": { "description": "URI of the referenced resource.\n", "type": "string", "format": "url" } } } } } }}
\ No newline at end of file
diff --git a/SOL003/VNFLifecycleManagement-API/schemas/subscriptions.schema.json b/SOL003/VNFLifecycleManagement-API/schemas/subscriptions.schema.json
index 75ab7eb899910a4119074e104c15378b8586c851..595f0c9f8349e48f10809ad45734cf8d9487f947 100644
--- a/SOL003/VNFLifecycleManagement-API/schemas/subscriptions.schema.json
+++ b/SOL003/VNFLifecycleManagement-API/schemas/subscriptions.schema.json
@@ -1,148 +1,199 @@
{
- "type": "array",
- "items": {
- "description": "This type represents a subscription related to notifications about VNF lifecycle changes.\n",
- "type": "object",
- "required": ["id", "callbackUri", "_links"],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "filter": {
- "description": "This type represents a subscription filter related to notifications about VNF lifecycle changes. At a particular nesting level in the filter structure, the following applies: All attributes shall match in order for the filter to match (logical \"and\" between different filter attributes). If an attribute is an array, the attribute shall match if at least one of the values in the array matches (logical \"or\" between the values of one filter attribute).\n",
- "type": "object",
- "properties": {
- "vnfInstanceSubscriptionFilter": {
- "description": "This type represents subscription filter criteria to match VNF instances.\n",
- "type": "object",
- "properties": {
- "vnfdIds": {
- "description": "If present, match VNF instances that were created based on a VNFD identified by one of the vnfdId values listed in this attribute. The attributes \"vnfdIds\" and \"vnfProductsFromProviders\" are alternatives to reference to VNF instances that are based on certain VNFDs in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n",
- "type": "array",
- "items": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- }
- },
- "vnfProductsFromProviders": {
- "description": "If present, match VNF instances that belong to VNF products from certain providers. The attributes \"vnfdIds\" and \"vnfProductsFromProviders\" are alternatives to reference to VNF instances that are based on certain VNFDs in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": ["vnfProvider"],
- "properties": {
- "vnfProvider": {
- "description": "Name of the VNF provider to match.\n",
- "type": "string"
- },
- "vnfProducts": {
- "description": "If present, match VNF instances that belong to VNF products with certain product names, from one particular provider.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": ["vnfProductName"],
- "properties": {
- "vnfProductName": {
- "description": "Name of the VNF product to match.\n",
- "type": "string"
- },
- "versions": {
- "description": "If present, match VNF instances that belong to VNF products with certain versions and a certain product name, from one particular provider.\n",
- "type": "array",
- "items": {
- "type": "object",
- "required": ["vnfSoftwareVersion"],
- "properties": {
- "vnfSoftwareVersion": {
- "description": "A version.\n",
- "type": "string"
- },
- "vnfdVersions": {
- "description": "If present, match VNF instances that belong to VNF products with certain VNFD versions, a certain software version and a certain product name, from one particular provider.\n",
- "type": "array",
- "items": {
- "description": "A version.\n",
- "type": "string"
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- },
- "vnfInstanceIds": {
- "description": "If present, match VNF instances with an instance identifier listed in this attribute. The attributes \"vnfInstanceIds\" and \"vnfInstanceNames\" are alternatives to reference to particular VNF Instances in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n",
- "type": "array",
- "items": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- }
- },
- "vnfInstanceNames": {
- "description": "If present, match VNF instances with a VNF Instance Name listed in this attribute. The attributes \"vnfInstanceIds\" and \"vnfInstanceNames\" are alternatives to reference to particular VNF Instances in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n",
- "type": "array",
- "items": {
- "type": "string"
- }
- }
- }
- },
- "notificationTypes": {
- "description": "Match particular notification types. Permitted values: * VnfLcmOperationOccurrenceNotification * VnfIdentifierCreationNotification * VnfIdentifierDeletionNotification The permitted values of the \"notificationTypes\" attribute are spelled exactly as the names of the notification types to facilitate automated code generation systems.\n",
- "type": "array",
- "items": {
- "type": "string",
- "enum": ["VnfLcmOperationOccurrenceNotification", "VnfIdentifierCreationNotification", "VnfIdentifierDeletionNotification"]
- }
- },
- "operationTypes": {
- "description": "Match particular VNF lifecycle operation types for the notification of type VnfLcmOperationOccurrenceNotification. May be present if the \"notificationTypes\" attribute contains the value \"VnfLcmOperationOccurrenceNotification\", and shall be absent otherwise.\n",
- "type": "array",
- "items": {
- "description": "Value | Description ------|------------ INSTANTIATE | Represents the \"Instantiate VNF\" LCM operation. SCALE | Represents the \"Scale VNF\" LCM operation. SCALE_TO_LEVEL | Represents the \"Scale VNF to Level\" LCM operation. CHANGE_FLAVOUR | Represents the \"Change VNF Flavour\" LCM operation. TERMINATE | Represents the \"Terminate VNF\" LCM operation. HEAL | Represents the \"Heal VNF\" LCM operation. OPERATE | Represents the \"Operate VNF\" LCM operation. CHANGE_EXT_CONN | Represents the \"Change external VNF connectivity\" LCM operation. MODIFY_INFO | Represents the \"Modify VNF Information\" LCM operation. \n",
- "type": "string",
- "enum": ["INSTANTIATE", "SCALE", "SCALE_TO_LEVEL", "CHANGE_FLAVOUR", "TERMINATE", "HEAL", "OPERATE", "CHANGE_EXT_CONN", "MODIFY_INFO"]
- }
- },
- "operationStates": {
- "description": "Match particular LCM operation state values as reported in notifications of type VnfLcmOperationOccurrenceNotification. May be present if the \"notificationTypes\" attribute contains the value \"VnfLcmOperationOccurrenceNotification\", and shall be absent otherwise.\n",
- "type": "array",
- "items": {
- "description": "Value | Description ------|------------ STARTING | The LCM operation is starting. PROCESSING | The LCM operation is currently in execution. COMPLETED | he LCM operation has been completed successfully. FAILED_TEMP | The LCM operation has failed and execution has stopped, but the execution of the operation is not considered to be closed. FAILED | The LCM operation has failed and it cannot be retried or rolled back, as it is determined that such action won't succeed. ROLLING_BACK | The LCM operation is currently being rolled back. ROLLED_BACK | The LCM operation has been successfully rolled back, i.e. The state of the VNF prior to the original operation invocation has been restored as closely as possible.\n",
- "type": "string",
- "enum": ["STARTING", "PROCESSING", "COMPLETED", "FAILED_TEMP", "FAILED", "ROLLING_BACK", "ROLLED_BACK"]
- }
- }
- }
- },
- "callbackUri": {
- "description": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- },
- "_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 the referenced resource.\n",
- "type": "string",
- "format": "url"
- }
- }
- }
- }
- }
- }
- }
+ "type": "array",
+ "items": {
+ "description": "This type represents a subscription related to notifications about VNF lifecycle changes.\n",
+ "type": "object",
+ "required": ["id", "callbackUri", "verbosity", "_links"],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "filter": {
+ "description": "This type represents a subscription filter related to notifications about VNF lifecycle changes.\nAt a particular nesting level in the filter structure, the following applies: All attributes shall match in order for the filter to match (logical \"and\" between different filter attributes). If an attribute is an array, the attribute shall match if at least one of the values in the array matches (logical \"or\" between the values of one filter attribute).\nNOTE:\tThe permitted values of the \"notificationTypes\" attribute are spelled exactly as the names of \n the notification types to facilitate automated code generation systems.\n",
+ "type": "object",
+ "properties": {
+ "vnfInstanceSubscriptionFilter": {
+ "description": "This type represents subscription filter criteria to match VNF instances. * NOTE 1:\tThe attributes \"vnfdIds\" and \"vnfProductsFromProviders\" are alternatives to reference to VNF instances\n that are based on certain VNFDs in a filter. They should not be used both in the same filter instance,\n but one alternative should be chosen.\n NOTE 2:\tThe attributes \"vnfInstanceIds\" and \"vnfInstanceNames\" are alternatives to reference to particular VNF\n instances in a filter. They should not be used both in the same filter instance, but one alternative\n should be chosen.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "oneOf": [
+ {
+ "required": ["vnfdId"]
+ },
+ {
+ "required": ["vnfProductsFromProviders"]
+ }
+ ]
+ },
+ {
+ "oneOf": [
+ {
+ "required": ["vnfInstanceIds"]
+ },
+ {
+ "required": ["vnfInstanceNames"]
+ }
+ ]
+ }
+ ],
+ "properties": {
+ "vnfdIds": {
+ "description": "If present, match VNF instances that were created based on a VNFD identified by one of the vnfdId values listed in this attribute. See note 1.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ },
+ "vnfProductsFromProviders": {
+ "description": "If present, match VNF instances that belong to VNF products from certain providers. See note 1.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": ["vnfProvider"],
+ "properties": {
+ "vnfProvider": {
+ "description": "Name of the VNF provider to match.\n",
+ "type": "string"
+ },
+ "vnfProducts": {
+ "description": "If present, match VNF instances that belong to VNF products with certain product names, from one particular provider.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": ["vnfProductName"],
+ "properties": {
+ "vnfProductName": {
+ "description": "Name of the VNF product to match.\n",
+ "type": "string"
+ },
+ "versions": {
+ "description": "If present, match VNF instances that belong to VNF products with certain versions and a certain product name, from one particular provider.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": ["vnfSoftwareVersion"],
+ "properties": {
+ "vnfSoftwareVersion": {
+ "description": "A version.\n",
+ "type": "string"
+ },
+ "vnfdVersions": {
+ "description": "If present, match VNF instances that belong to VNF products with certain VNFD versions, a certain software version and a certain product name, from one particular provider.\n",
+ "type": "array",
+ "items": {
+ "description": "A version.\n",
+ "type": "string"
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ },
+ "vnfInstanceIds": {
+ "description": "If present, match VNF instances with an instance identifier listed in this attribute. See note 2.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ },
+ "vnfInstanceNames": {
+ "description": "If present, match VNF instances with a VNF Instance Name listed in this attribute. See note 2.\n",
+ "type": "array",
+ "items": {
+ "type": "string"
+ }
+ }
+ }
+ },
+ "notificationTypes": {
+ "description": "Match particular notification types. \nPermitted values: -\tVnfLcmOperationOccurrenceNotification -\tVnfIdentifierCreationNotification -\tVnfIdentifierDeletionNotification See note.\n",
+ "type": "array",
+ "items": {
+ "type": "string",
+ "enum": [
+ "VnfLcmOperationOccurrenceNotification",
+ "VnfIdentifierCreationNotification",
+ "VnfIdentifierDeletionNotification"
+ ]
+ }
+ },
+ "operationTypes": {
+ "description": "Match particular VNF lifecycle operation types for the notification of type VnfLcmOperationOccurrenceNotification. May be present if the \"notificationTypes\" attribute contains the value \"VnfLcmOperationOccurrenceNotification\", and shall be absent otherwise.\n",
+ "type": "array",
+ "items": {
+ "description": "The enumeration LcmOpType defines the permitted values to represent VNF lifecycle operation types in VNF lifecycle management operation occurrence resources and VNF lifecycle management operation occurrence notifications.\nValue | Description ------|------------ INSTANTIATE | Represents the \"Instantiate VNF\" LCM operation. SCALE | Represents the \"Scale VNF\" LCM operation. SCALE_TO_LEVEL | Represents the \"Scale VNF to Level\" LCM operation. CHANGE_FLAVOUR | Represents the \"Change VNF Flavour\" LCM operation. TERMINATE | Represents the \"Terminate VNF\" LCM operation. HEAL | Represents the \"Heal VNF\" LCM operation. OPERATE | Represents the \"Operate VNF\" LCM operation. CHANGE_EXT_CONN | Represents the \"Change external VNF connectivity\" LCM operation. MODIFY_INFO | Represents the \"Modify VNF Information\" LCM operation. CREATE_SNAPSHOT | Represents the \"Create VNF Snapshot\" LCM operation. REVERT_TO_SNAPSHOT | Represents the “Revert-To VNF Snapshot\" LCM operation. CHANGE_VNFPKG | Represents the \"Change current VNF package\" LCM operation.\n",
+ "type": "string",
+ "enum": [
+ "INSTANTIATE",
+ "SCALE",
+ "SCALE_TO_LEVEL",
+ "CHANGE_FLAVOUR",
+ "TERMINATE",
+ "HEAL",
+ "OPERATE",
+ "CHANGE_EXT_CONN",
+ "MODIFY_INFO",
+ "CREATE_SNAPSHOT",
+ "REVERT_TO_SNAPSHOT",
+ "CHANGE_VNFPKG"
+ ]
+ }
+ },
+ "operationStates": {
+ "description": "Match particular LCM operation state values as reported in notifications of type VnfLcmOperationOccurrenceNotification. May be present if the \"notificationTypes\" attribute contains the value \"VnfLcmOperationOccurrenceNotification\", and shall be absent otherwise.\n",
+ "type": "array",
+ "items": {
+ "description": "STARTING: The LCM operation is starting. PROCESSING: The LCM operation is currently in execution. COMPLETED: The LCM operation has been completed successfully. FAILED_TEMP: The LCM operation has failed and execution has stopped, but the execution of the operation is not considered to be closed. FAILED: The LCM operation has failed and it cannot be retried or rolled back, as it is determined that such action won't succeed. ROLLING_BACK: The LCM operation is currently being rolled back. ROLLED_BACK: The LCM operation has been successfully rolled back, i.e. The state of the VNF prior to the original operation invocation has been restored as closely as possible.\n",
+ "type": "string",
+ "enum": [
+ "STARTING",
+ "PROCESSING",
+ "COMPLETED",
+ "FAILED_TEMP",
+ "FAILED",
+ "ROLLING_BACK",
+ "ROLLED_BACK"
+ ]
+ }
+ }
+ }
+ },
+ "callbackUri": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ },
+ "verbosity": {
+ "description": "The enumeration LcmOpOccNotificationVerbosityType provides values to control the verbosity of LCM operation occurrence notifications. * 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"]
+ },
+ "_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 using an absolute URI.\n",
+ "type": "object",
+ "required": ["href"],
+ "properties": {
+ "href": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ }
+ }
+ }
+ }
+ }
+ }
+ }
}
diff --git a/SOL003/VNFLifecycleManagement-API/schemas/vnfIdentifierDeletionNotification.schema.json b/SOL003/VNFLifecycleManagement-API/schemas/vnfIdentifierDeletionNotification.schema.json
index 253ccce96b2de34faba43dd5093c2a3ab9e561ef..50f5d52d83d556daed7b2c94455a391e0e88410d 100644
--- a/SOL003/VNFLifecycleManagement-API/schemas/vnfIdentifierDeletionNotification.schema.json
+++ b/SOL003/VNFLifecycleManagement-API/schemas/vnfIdentifierDeletionNotification.schema.json
@@ -1,87 +1,76 @@
{
- "description": "This type represents a VNF identifier deletion notification, which informs the receiver of the deletion of a new \"Individual VNF instance\" resource and the associated VNF instance identifier. This notification shall be triggered by the VNFM when it has deleted an \"Individual VNF instance\" resource and the associated VNF instance identifier.\n",
+ "description": "This type represents a VNF identifier deletion notification, which informs the receiver of the deletion of a new \"Individual VNF instance\" resource and the associated VNF instance identifier. This notification shall be triggered by the VNFM when it has deleted an \"Individual VNF instance\" resource and the associated VNF instance identifier.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "notificationType",
+ "subscriptionId",
+ "timeStamp",
+ "vnfInstanceId",
+ "_links"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "notificationType": {
+ "description": "Discriminator for the different notification types. Shall be set to \"VnfIdentifierDeletionNotification\" for this notification type.\n",
+ "type": "string",
+ "enum": ["VnfIdentifierDeletionNotification"]
+ },
+ "subscriptionId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "timeStamp": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "vnfInstanceId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "_links": {
+ "description": "This type represents the links to resources that a notification can contain.\n",
"type": "object",
- "required": [
- "id",
- "notificationType",
- "subscriptionId",
- "timeStamp",
- "vnfInstanceId",
- "_links"
- ],
+ "required": ["vnfInstance", "subscription"],
"properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "notificationType": {
- "description": "Discriminator for the different notification types. Shall be set to \"VnfIdentifierDeletionNotification\" for this notification type.\n",
- "type": "string",
- "enum": [
- "VnfIdentifierDeletionNotification"
- ]
- },
- "subscriptionId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "timeStamp": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
+ "vnfInstance": {
+ "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": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ }
+ }
},
- "vnfInstanceId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
+ "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": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ }
+ }
},
- "_links": {
- "description": "This type represents the links to resources that a notification can contain.\n",
+ "vnfLcmOpOcc": {
+ "description": "This type represents a link to a resource in a notification, using an absolute or relative URI.\n",
"type": "object",
- "required": [
- "vnfInstance",
- "subscription"
- ],
+ "required": ["href"],
"properties": {
- "vnfInstance": {
- "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": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- }
- }
- },
- "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": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- }
- }
- },
- "vnfLcmOpOcc": {
- "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": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- }
- }
+ "href": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
}
}
}
}
- }
\ No newline at end of file
+ }
+ }
+}
\ No newline at end of file
diff --git a/SOL003/VNFLifecycleManagement-API/schemas/vnfInstance.schema.json b/SOL003/VNFLifecycleManagement-API/schemas/vnfInstance.schema.json
index 2736911a7dfd419c679cb00290f35552ab4f2a91..a1c00316949b29edc813c5bdd52b02bc8d44dbdb 100644
--- a/SOL003/VNFLifecycleManagement-API/schemas/vnfInstance.schema.json
+++ b/SOL003/VNFLifecycleManagement-API/schemas/vnfInstance.schema.json
@@ -1,5 +1,5 @@
{
- "description": "This type represents a VNF instance. It shall comply with the provisions defined in table 5.5.2.2-1.\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 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",
"type": "object",
"required": [
"id",
@@ -8,7 +8,8 @@
"vnfProductName",
"vnfSoftwareVersion",
"vnfdVersion",
- "instantiationState"
+ "instantiationState",
+ "_links"
],
"properties": {
"id": {
@@ -48,10 +49,10 @@
"type": "object"
},
"vimConnectionInfo": {
- "description": "Information about VIM 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 VNF-related resource management in direct mode is pplicable. 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.\n",
"type": "object",
"additionalProperties": {
- "description": "This type represents parameters to connect to a VIM for managing the resources of a VNF instance. * 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 is provided through a secure connection over\n HTTP Secure (HTTP over SSL/TLS), and the connection might also be established through a VPN\n (for example TLS-based VPN tunnelling) for site-to-site connection, the \"accessInfo\" JSON data\n structure, and the sensitive data related information (\"username\"/\"password\" as required properties\n for authentication purpose), will be transmitted as plain text through a TLS tunnel without additional\n encoding/encryption before transmitting it, making the sensitive data visible to the endpoint.\n The base64 encoded certificates are only used by the VNFM to verify the authenticity of the\n interface endpoint of the VIM.\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",
"type": "object",
"required": ["vimType"],
"properties": {
@@ -60,7 +61,69 @@
"type": "string"
},
"vimType": {
- "description": "Discriminator for the different types of the VIM information. The value of this attribute determines the structure of the \"interfaceInfo\" and \"accessInfo\" attributes, based on the type of the VIM. The set of permitted values is expected to change over time as new types or versions of VIMs become available. The ETSI NFV registry of VIM-related information provides access to information about VimConnectionInfo definitions for various VIM types. The structure of the registry is defined in Annex C of SOL003.\n",
+ "description": "Discriminator for the different types of the VIM information. The value of this attribute determines the structure of the \"interfaceInfo\" and \"accessInfo\" attributes, based on the type of the VIM., CISM, CIR or MCIOP repository. The set of permitted values is expected to change over time as new types or versions of VIMs become available. The ETSI NFV registry of VIM-related information [i.3] provides access to information about VimConnectionInfo definitions for various VIM, CISM, CIR or MCIOP repository types. The structure of the registry is defined in annex C.\n",
+ "type": "string"
+ },
+ "interfaceInfo": {
+ "description": "This 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"
+ },
+ "accessInfo": {
+ "description": "This 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"
+ },
+ "extra": {
+ "description": "This 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"
+ }
+ }
+ }
+ },
+ "cirConnectionInfo": {
+ "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",
+ "type": "object",
+ "required": ["vimType"],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vimType": {
+ "description": "Discriminator for the different types of the VIM information. The value of this attribute determines the structure of the \"interfaceInfo\" and \"accessInfo\" attributes, based on the type of the VIM., CISM, CIR or MCIOP repository. The set of permitted values is expected to change over time as new types or versions of VIMs become available. The ETSI NFV registry of VIM-related information [i.3] provides access to information about VimConnectionInfo definitions for various VIM, CISM, CIR or MCIOP repository types. The structure of the registry is defined in annex C.\n",
+ "type": "string"
+ },
+ "interfaceInfo": {
+ "description": "This 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"
+ },
+ "accessInfo": {
+ "description": "This 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"
+ },
+ "extra": {
+ "description": "This 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"
+ }
+ }
+ }
+ },
+ "mciopRepositoryInfo": {
+ "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",
+ "type": "object",
+ "required": ["vimType"],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vimType": {
+ "description": "Discriminator for the different types of the VIM information. The value of this attribute determines the structure of the \"interfaceInfo\" and \"accessInfo\" attributes, based on the type of the VIM., CISM, CIR or MCIOP repository. The set of permitted values is expected to change over time as new types or versions of VIMs become available. The ETSI NFV registry of VIM-related information [i.3] provides access to information about VimConnectionInfo definitions for various VIM, CISM, CIR or MCIOP repository types. The structure of the registry is defined in annex C.\n",
"type": "string"
},
"interfaceInfo": {
@@ -79,14 +142,14 @@
}
},
"instantiationState": {
- "description": "The instantiation state of the VNF.\n",
+ "description": "The instantiation state of the VNF. Permitted 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"],
+ "required": ["flavourId", "vnfState", "extCpInfo"],
"properties": {
"flavourId": {
"description": "An identifier that is unique within a VNF descriptor.\n",
@@ -98,11 +161,12 @@
"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. This attribute shall be present if the VNF supports scaling. See clause B.2 for an explanation of VNF scaling.\n",
+ "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. This attribute shall be present if the VNF supports scaling. See clause B.2 for an explanation of VNF scaling.\n",
"type": "array",
"items": {
- "required": ["aspectId", "scaleLevel"],
+ "description": "This type represents the scale level of a VNF instance related to a scaling aspect.\n",
"type": "object",
+ "required": ["aspectId", "scaleLevel"],
"properties": {
"aspectId": {
"description": "An identifier that is unique within a VNF descriptor.\n",
@@ -112,9 +176,9 @@
"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"
+ "scaleToLevel": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
}
}
}
@@ -123,8 +187,9 @@
"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"],
+ "description": "This type represents the scale level of a VNF instance related to a scaling aspect.\n",
"type": "object",
+ "required": ["aspectId", "scaleLevel"],
"properties": {
"aspectId": {
"description": "An identifier that is unique within a VNF descriptor.\n",
@@ -134,9 +199,9 @@
"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"
+ "scaleToLevel": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
}
}
}
@@ -146,7 +211,7 @@
"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 5.5.3.17 1.\nNOTE 1:\tThe attributes \"associatedVnfcCpId\", \"associatedVipCpId\" and \"associatedVnfVirtualLinkId\" \n are mutually exclusive. Exactly one shall be present.\nNOTE 2:\tAn external CP instance is not associated to a link port in the cases indicated for the \n ΓÇ£extLinkPortsΓÇ¥ attribute in clause 4.4.1.11.\n",
+ "description": "This type represents information about an external CP of a VNF.\nNOTE 1:\tThe attributes \"associatedVnfcCpId\", \"associatedVipCpId\", \"associatedVirtualCpId\" and \n \"associatedVnfVirtualLinkId\" are mutually exclusive. Exactly one shall be present.\nNOTE 2:\tAn external CP instance is not associated to a link port in the cases indicated for the \n “extLinkPorts†attribute in clause 4.4.1.11.\nNOTE 3: 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 \n CP, e.g. to build a link redundant mated pair in SR-IOV cases.\nNOTE 4: When more than one netAttDefResourceId is indicated, all shall belong to the same namespace.\n",
"type": "object",
"required": ["id", "cpdId", "cpConfigId", "cpProtocolInfo"],
"oneOf": [
@@ -181,17 +246,17 @@
"description": "Network protocol information for this CP.\n",
"type": "array",
"items": {
- "description": "This type describes the protocol layer(s) that a CP uses together with protocol-related information, like addresses. It shall comply with the provisions defined in table 5.5.3.9b-1.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the \n present document in a backwards-compatible way. In the current version of the present document, only IP over \n Ethernet is supported.\n",
+ "description": "This type describes the protocol layer(s) that a CP uses together with protocol-related information, like addresses.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the \n present document in a backwards-compatible way. In the current version of the present document, only IP over \n Ethernet is supported.\n",
"type": "object",
"required": ["layerProtocol"],
"properties": {
"layerProtocol": {
- "description": "The identifier of layer(s) and protocol(s) associated to the network address information.\nPermitted values: IP_OVER_ETHERNET See note.\n",
+ "description": "The identifier of layer(s) and protocol(s) associated to the network address information.\nPermitted values:\n - IP_OVER_ETHERNET\n - IP_FOR_VIRTUAL_CP\nSee note.\n",
"type": "string",
- "enum": ["IP_OVER_ETHERNET"]
+ "enum": ["IP_OVER_ETHERNET", "IP_FOR_VIRTUAL_CP"]
},
"ipOverEthernet": {
- "description": "This type represents information about a network address that has been assigned. It shall comply with the provisions defined in table 5.5.3.10-1.\nNOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, segmentationId shall be present. \n Otherwise it shall not be present.\nNOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the \n actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the \n transport header of the packets or it may be an identifier used between the application \n and the NFVI networking infrastructure to identify the network sub-interface of the trunk \n port in question. In the latter case the NFVI infrastructure will map this local segmentationId \n to whatever segmentationId is actually used by the NFVIΓÇÖs transport technology.\n",
+ "description": "This type represents information about a network address that has been assigned.\nNOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, segmentationId shall be present. \n Otherwise it shall not be present.\nNOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the \n actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the \n transport header of the packets or it may be an identifier used between the application \n and the NFVI networking infrastructure to identify the network sub-interface of the trunk \n port in question. In the latter case the NFVI infrastructure will map this local segmentationId \n to whatever segmentationId is actually used by the NFVI’s transport technology.\n",
"type": "object",
"anyOf": [
{
@@ -262,13 +327,30 @@
}
},
"subnetId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\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"
+ }
+ }
}
}
}
@@ -289,9 +371,21 @@
"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"
+ },
+ "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 with the intention of being globally unique.\n",
+ "type": "string"
+ }
}
}
}
@@ -301,7 +395,7 @@
"type": "array",
"minItems": 1,
"items": {
- "description": "This type provides information related to virtual IP (VIP) CP. It shall comply with the provisions defined in table 5.5.3.28-1.\nNOTE 1:\tIt is possible that there is no associated VnfcCp because the VIP CP is available but not associated yet. NOTE 2: If only the value or the presence of this attribute is changed in the \"VipCpInfo\" structure by an LCM operation occurrence, this does not represent a change that requires including a related \"AffectedVipCp\" structure in the VNF LCM operation occurrence notifications or the \"VnfLcmOpOcc\" structure related to this LCM operation occurrence.\n",
+ "description": "This type provides information related to virtual IP (VIP) CP.\nNOTE 1:\tIt is possible that there is no associated VnfcCp because the VIP CP is available but not associated yet. NOTE 2: If only the value or the presence of this attribute is changed in the \"VipCpInfo\" structure by an LCM operation occurrence, this does not represent a change that requires including a related \"AffectedVipCp\" structure in the VNF LCM operation occurrence notifications or the \"VnfLcmOpOcc\" structure related to this LCM operation occurrence.\n",
"type": "object",
"required": ["cpInstanceId", "cpdId"],
"properties": {
@@ -325,17 +419,17 @@
"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 uses together with protocol-related information, like addresses. It shall comply with the provisions defined in table 5.5.3.9b-1.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the \n present document in a backwards-compatible way. In the current version of the present document, only IP over \n Ethernet is supported.\n",
+ "description": "This type describes the protocol layer(s) that a CP uses together with protocol-related information, like addresses.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the \n present document in a backwards-compatible way. In the current version of the present document, only IP over \n Ethernet is supported.\n",
"type": "object",
"required": ["layerProtocol"],
"properties": {
"layerProtocol": {
- "description": "The identifier of layer(s) and protocol(s) associated to the network address information.\nPermitted values: IP_OVER_ETHERNET See note.\n",
+ "description": "The identifier of layer(s) and protocol(s) associated to the network address information.\nPermitted values:\n - IP_OVER_ETHERNET\n - IP_FOR_VIRTUAL_CP\nSee note.\n",
"type": "string",
- "enum": ["IP_OVER_ETHERNET"]
+ "enum": ["IP_OVER_ETHERNET", "IP_FOR_VIRTUAL_CP"]
},
"ipOverEthernet": {
- "description": "This type represents information about a network address that has been assigned. It shall comply with the provisions defined in table 5.5.3.10-1.\nNOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, segmentationId shall be present. \n Otherwise it shall not be present.\nNOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the \n actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the \n transport header of the packets or it may be an identifier used between the application \n and the NFVI networking infrastructure to identify the network sub-interface of the trunk \n port in question. In the latter case the NFVI infrastructure will map this local segmentationId \n to whatever segmentationId is actually used by the NFVIΓÇÖs transport technology.\n",
+ "description": "This type represents information about a network address that has been assigned.\nNOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, segmentationId shall be present. \n Otherwise it shall not be present.\nNOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the \n actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the \n transport header of the packets or it may be an identifier used between the application \n and the NFVI networking infrastructure to identify the network sub-interface of the trunk \n port in question. In the latter case the NFVI infrastructure will map this local segmentationId \n to whatever segmentationId is actually used by the NFVI’s transport technology.\n",
"type": "object",
"anyOf": [
{
@@ -406,13 +500,30 @@
}
},
"subnetId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\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"
+ }
+ }
}
}
}
@@ -430,12 +541,246 @@
"type": "string"
},
"metadata": {
- "description": "Metadata about this VIP CP.\n",
+ "description": "This 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"
+ }
+ }
+ }
+ },
+ "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 provides information related to a virtual CP instance of a VNF.\nNOTE: A consumer of the VNF LCM interface can learn the actual VNFC instances implementing the service \n accessible via the virtual CP instance by querying the \"vnfcResourceInfo\" from the \"InstantiatedVnfInfo\" \n and filtering by corresponding \"vduIds\" values.\n",
+ "type": "object",
+ "required": ["cpInstanceId", "cpdId", "resourceHandle", "vduIds"],
+ "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": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "resourceHandle": {
+ "required": ["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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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 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"
+ "description": "This type describes the protocol layer(s) that a CP uses together with protocol-related information, like addresses.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the \n present document in a backwards-compatible way. In the current version of the present document, only IP over \n Ethernet is supported.\n",
+ "type": "object",
+ "required": ["layerProtocol"],
+ "properties": {
+ "layerProtocol": {
+ "description": "The identifier of layer(s) and protocol(s) associated to the network address information.\nPermitted 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:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, segmentationId shall be present. \n Otherwise it shall not be present.\nNOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the \n actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the \n transport header of the packets or it may be an identifier used between the application \n and the NFVI networking infrastructure to identify the network sub-interface of the trunk \n port in question. In the latter case the NFVI infrastructure will map this local segmentationId \n to whatever segmentationId is actually used by the NFVI’s transport technology.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "required": ["macAddress"]
+ },
+ {
+ "required": ["ipAddresses"]
+ }
+ ],
+ "oneOf": [
+ {
+ "required": ["addresses"]
+ },
+ {
+ "required": ["addressRange"]
+ }
+ ],
+ "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 notes 3 and 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"],
+ "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. 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.\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"
+ }
+ }
+ }
+ }
+ }
+ },
+ "vduIds": {
+ "description": "Reference to the VDU(s) which implement the service accessible via the virtual CP instance. See note.\n",
+ "type": "array",
+ "minItems": 1,
+ "items": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
}
+ },
+ "additionalServiceInfo": {
+ "description": "Additional service identification information of the virtual CP instance.\n",
+ "type": "array",
+ "items": {
+ "description": "This type provides 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 \n termination within the VNF, such as for example a URL path information in an HTTP request required \n to allow a single virtual CP IP address to be used for several HTTP based services that use the \n same port number.\n",
+ "type": "object",
+ "required": ["portInfo"],
+ "properties": {
+ "portInfo": {
+ "description": "Service port numbers exposed by the virtual CP instance.\n",
+ "minItems": 1,
+ "type": "array",
+ "items": {
+ "description": "This type describes the service identifying port properties exposed by the virtual CP instance.\n",
+ "type": "object",
+ "required": ["name", "port", "portConfigurable"],
+ "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.\nPermitted values: - TCP - UDP - SCTP\n",
+ "type": "string",
+ "enum": ["TCP", "UDP", "SCTP"]
+ },
+ "port": {
+ "description": "The L4 port number exposed by the virtual CP instance.\n",
+ "type": "integer"
+ },
+ "portConfigurable": {
+ "description": "The Boolean is a data type having two values (true and false).\n",
+ "type": "boolean"
+ }
+ }
+ }
+ },
+ "serviceInfo": {
+ "description": "This 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"
+ }
+ }
+ }
+ },
+ "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 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"
}
}
}
@@ -444,7 +789,7 @@
"description": "Information about the external VLs the VNF instance is connected to.\n",
"type": "array",
"items": {
- "description": "This type represents information about an external VL. It shall comply with the provisions defined in table 5.5.3.2-1.\nNOTE:\tThis attribute reflects the current configuration information that has resulted from merging into this attribute \n the \"VnfExtCpData\" information which was passed as part of the \"ExtVirtualLinkData\" structure in the input of the \n most recent VNF LCM operation such as \"InstantiateVnfRequest\", \"ChangeExtVnfConnectivityRequest\", \"ChangeVnfFlavourRequest\" \n or \"ChangeCurrentVnfPkgRequest\", or in the Grant response. If applying such change results in an empty list of \n \"currentVnfExtCpData\" structure instances, the affected instance of \"ExtVirtualLinkInfo\" shall be removed from its \n parent data structure.\n",
+ "description": "This type represents information about an external VL.\nNOTE:\tThis attribute reflects the current configuration information that has resulted from merging into this attribute \n the \"VnfExtCpData\" information which was passed as part of the \"ExtVirtualLinkData\" structure in the input of the \n most recent VNF LCM operation such as \"InstantiateVnfRequest\", \"ChangeExtVnfConnectivityRequest\", \"ChangeVnfFlavourRequest\" \n or \"ChangeCurrentVnfPkgRequest\", or in the Grant response. If applying such change results in an empty list of \n \"currentVnfExtCpData\" structure instances, the affected instance of \"ExtVirtualLinkInfo\" shall be removed from its \n parent data structure.\n",
"type": "object",
"required": ["id", "resourceHandle", "currentVnfExtCpData"],
"properties": {
@@ -455,7 +800,7 @@
"resourceHandle": {
"required": ["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",
+ "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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
@@ -466,11 +811,33 @@
"type": "string"
},
"resourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
"type": "string"
},
"vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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"
}
}
@@ -479,7 +846,7 @@
"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. It shall comply with the provisions defined in table 5.5.3.9-1.\nNOTE 1:\tThe use cases UC#4 and UC#5 in clause A.4 of ETSI GS NFV-IFA 007 provide examples for such a configuration. NOTE 2:\tThe value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\" attribute.\n",
+ "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.\nNOTE 1:\tThe use cases UC#4 and UC#5 in clause A.4 of ETSI GS NFV-IFA 007 provide examples for such a configuration. NOTE 2:\tThe value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\" attribute.\n",
"type": "object",
"required": ["id", "resourceHandle"],
"properties": {
@@ -490,7 +857,7 @@
"resourceHandle": {
"required": ["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",
+ "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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
@@ -501,11 +868,33 @@
"type": "string"
},
"resourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
"type": "string"
},
"vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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"
}
}
@@ -519,7 +908,7 @@
"type": "string"
},
"trunkResourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
"type": "string"
}
}
@@ -529,7 +918,7 @@
"description": "Allows the API consumer to read the current CP configuration information for the connection of external CPs to the external virtual link. See note.\n",
"type": "array",
"items": {
- "description": "This type represents configuration information for external CPs created. * NOTE 1: \tIn case this identifier refers to a CPD with trunking enabled, the external CP instances created\n from this CPD will represent ports in a trunk.\n* NOTE 2: \tWithin one VNF instance, all VNFC instances created from a particular VDU have the same external\n connectivity. Thus, given a particular value of the \"cpdId\" attribute, there shall be one\n \"cpConfig\" entry for each VNFC instance that has been or can be created from a VDU which includes\n a CPD identified by the \"cpdId\" attribute. If the cpConfig represents a subport in a trunk,\n all \"cpConfig\" entries in this list shall have the same segmentationId, which means they are\n connected to the same set of external VLs via the trunk.\n* NOTE 3: \tThe map entry value shall be set to \"null\" in order to delete a \"VnfExtCpConfig\" entry identified\n by a particular key value from the map, i.e. for the disconnection of an existing external\n CP instance addressed by cpInstanceId in the deleted map entry from a particular external\n virtual link, and deletion of that instance in case it represents a subport. Deleting the\n last key from the map removes the affected instance of the \"VnfExtCpData\" structure from\n its parent data structure.\n* NOTE 4: If, as defined by the input parameters of a \"ChangeVnfFlavour\", \"ChangeExtVnfConnectivity\" or \n \"ChangeCurrentVnfPkg\" operation or as part of the Grant response for any of these operations, a \n cpConfig map entry identified by a particular map key value is moved into another \"ExtVirtualLinkData\"\n or \"VnfExtCpData\" structure, this particular cpConfig map entry may be used by an external CP instance\n different than the one that has used it before the operation, or by no external CP instance at all.\n Renaming a CPD identifier during the \"changeCurrentVnfPkg\" operation does not count as moving the\n related \"cpConfig\" map entries to a new \"extCpData\" structure.\n",
+ "description": "This type represents configuration information for external CPs created. * NOTE 1: \tIn case this identifier refers to a CPD with trunking enabled, the external CP instances created\n from this CPD will represent ports in a trunk.\n* NOTE 2: \tWithin one VNF instance, all VNFC instances created from a particular VDU have the same external\n connectivity. Thus, given a particular value of the \"cpdId\" attribute, there shall be one\n \"cpConfig\" entry for each VNFC instance that has been or can be created from a VDU which includes\n a CPD identified by the \"cpdId\" attribute. If the cpConfig represents a subport in a trunk,\n all \"cpConfig\" entries in this list shall have the same segmentationId, which means they are\n connected to the same set of external VLs via the trunk.\n* NOTE 3: \tThe map entry value shall be set to \"null\" in order to delete a \"VnfExtCpConfig\" entry identified\n by a particular key value from the map, i.e. for the disconnection of an existing external\n CP instance addressed by cpInstanceId in the deleted map entry from a particular external\n virtual link, and deletion of that instance in case it represents a subport. Deleting the\n last key from the map removes the affected instance of the \"VnfExtCpData\" structure from\n its parent data structure.\n* NOTE 4: If, as defined by the input parameters of a \"ChangeVnfFlavour\", \"ChangeExtVnfConnectivity\" or\n \"ChangeCurrentVnfPkg\" operation or as part of the Grant response for any of these operations, a cpConfig\n map entry identified by a particular map key value is moved into another \"ExtVirtualLinkData\" or\n \"VnfExtCpData\" structure, this particular cpConfig map entry may be used by an external CP instance\n different than the one that has used it before the operation, or by no external CP instance at all.\n Renaming a CPD identifier during the \"changeCurrentVnfPkg\" operation does not count as moving the related\n \"cpConfig\" map entries to a new \"extCpData\" structure.\n",
"type": "object",
"required": ["cpdId"],
"properties": {
@@ -538,16 +927,19 @@
"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). See notes 2, 3 and 4.\n",
+ "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 network address information per instance of an external connection point. In case a link port is provided, the VNFM shall use that link port when connecting the external CP to the external VL. In a link port is not provided, the VNFM shall create a link port on the external VL, and use that link port to connect the external CP to the external VL. * NOTE: The following conditions apply to the attributes \"linkPortId\" and \"cpProtocolData\":\n 1) Void.\n 2) At least one of the \"linkPortId\" and \"cpProtocolData\" attributes shall be present for an external\n CP instance representing a subport that is to be created, or an external CP instance that is to be\n created by creating the corresponding VNFC or VNF instance during the current or a subsequent LCM\n operation, or for an existing external CP instance that is to be re-configured or added to a\n 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\n a pre created link port, and the VNFM can use means outside the scope of the present document to obtain\n the pre-configured address information for the connection point from the resource representing\n the link port.\n 5) If both \"cpProtocolData\" and \"linkportId\" are provided, the API consumer shall ensure that the\n cpProtocolData can be used with the pre-created link port referenced by \"linkPortId\".\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) 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",
"anyOf": [
{
"required": ["linkPortId"]
},
{
"required": ["cpProtocolData"]
+ },
+ {
+ "required": ["netAttDefResourceId"]
}
],
"type": "object",
@@ -564,8 +956,16 @@
"description": "Indicates to the VNFM the need to create a dedicated link port for the external CP. If set to True, the VNFM shall create a link port. If set to False, the VNFM shall not create a link port. 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"
},
+ "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 2, 3 and 4.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ },
"cpProtocolData": {
- "description": "Parameters for configuring the network protocols on the link port that connects the CP to a VL. See note.\n",
+ "description": "Parameters for configuring the network protocols on the link port that connects the CP to a VL. See notes 1 and 2.\n",
"type": "array",
"items": {
"description": "This type represents network protocol data. * NOTE:\tThis attribute allows to signal the addition of further types of layer and protocol\n in future versions of the present document in a backwards-compatible way. In the current\n version of the present document, only IP over Ethernet is supported.\n",
@@ -573,12 +973,15 @@
"required": ["layerProtocol"],
"properties": {
"layerProtocol": {
- "description": "Identifier of layer(s) and protocol(s). See note.\n",
+ "description": "Identifier of layer(s) and protocol(s). Permitted values:\n - IP_OVER_ETHERNET.\n - IP_FOR_VIRTUAL_CP\nSee note\n",
"type": "string",
- "enum": ["IP_OVER_ETHERNET"]
+ "enum": [
+ "IP_OVER_ETHERNET",
+ "IP_FOR_VIRTUAL_CP"
+ ]
},
"ipOverEthernet": {
- "description": "This type represents network address data for IP over Ethernet. * NOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. * NOTE 2:\tExactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present. * NOTE 3:\tIf the CP instance represents a subport in a trunk, segmentationId shall be present.\n Otherwise it shall not be present.\n* NOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the actual\n network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header\n of the packets or it may be an identifier used between the application and the NFVI networking\n infrastructure to identify the network sub-interface of the trunk port in question. In the latter\n case the NFVI infrastructure will map this local segmentationId to whatever segmentationId is\n actually used by the NFVIΓÇÖs transport technology.\n",
+ "description": "This type represents network address data for IP over Ethernet. * NOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. * NOTE 2:\tExactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present. * NOTE 3:\tIf the CP instance represents a subport in a trunk, segmentationId shall be present.\n Otherwise it shall not be present.\n* NOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the actual\n network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header\n of the packets or it may be an identifier used between the application and the NFVI networking\n infrastructure to identify the network sub-interface of the trunk port in question. In the latter\n case the NFVI infrastructure will map this local segmentationId to whatever segmentationId is\n actually used by the NFVI’s transport technology.\n",
"type": "object",
"anyOf": [
{
@@ -606,7 +1009,7 @@
"format": "MAC"
},
"segmentationType": {
- "description": "Specifies the encapsulation type for the traffics coming in and out of the trunk subport. Permitted values: -\tVLAN: the subport uses VLAN as encapsulation type. -\tINHERIT: the subport gets its segmentation type from the network itΓÇÖs 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",
+ "description": "Specifies the encapsulation type for the traffics coming in and out of the trunk subport. Permitted values: -\tVLAN: the subport uses VLAN as encapsulation type. -\tINHERIT: the subport gets its segmentation type from the network it’s 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"]
},
@@ -660,13 +1063,30 @@
}
},
"subnetId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
"type": "string"
}
}
}
}
}
+ },
+ "virtualCpAddress": {
+ "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",
+ "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"
+ }
+ }
}
}
}
@@ -676,6 +1096,82 @@
}
}
}
+ },
+ "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 contains 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": {
+ "required": ["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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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 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 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"
+ }
+ }
+ }
+ }
}
}
}
@@ -702,7 +1198,7 @@
"networkResource": {
"required": ["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",
+ "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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
@@ -713,11 +1209,33 @@
"type": "string"
},
"resourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
"type": "string"
},
"vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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"
}
}
@@ -726,7 +1244,7 @@
"description": "Link ports of this VL.\n",
"type": "array",
"items": {
- "description": "This type represents a link port of an internal VL of a VNF. It shall comply with the provisions defined in table 5.5.3.8 1.\nNOTE 1: Either cpInstanceId with cpInstanceType set to \"EXT_CP\" or any combination of cpInstanceId\n with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId (i.e. one or both of them) shall be \n present for a VnfLinkPortInfo. In case both cpInstanceId with cpInstanceType set to \"VNFC_CP\" \n and vipCpInstanceId are present, the two different CP instances share the linkport.\nNOTE 2: Annex A.4 of ETSI GS NFV-IFA 007 provides examples for configurations where both vipCpInstanceId\n and vnfcCpInstanceId are present (UC#5 and UC#5-b), only vnfcCpInstanceId is present (UC#2), or \n only vipCpInstanceId is present (UC6 and UC#6-b).\nNOTE 3: The value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\"\n attribute.\n",
+ "description": "This type represents a link port of an internal VL of a VNF.\nNOTE 1: Either cpInstanceId with cpInstanceType set to \"EXT_CP\" or any combination of cpInstanceId\n with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId (i.e. one or both of them) shall be \n present for a VnfLinkPortInfo. In case both cpInstanceId with cpInstanceType set to \"VNFC_CP\" \n and vipCpInstanceId are present, the two different CP instances share the linkport.\nNOTE 2: Annex A.4 of ETSI GS NFV-IFA 007 provides examples for configurations where both vipCpInstanceId\n and vnfcCpInstanceId are present (UC#5 and UC#5-b), only vnfcCpInstanceId is present (UC#2), or \n only vipCpInstanceId is present (UC6 and UC#6-b).\nNOTE 3: The value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\"\n attribute.\n",
"type": "object",
"required": ["id", "resourceHandle"],
"properties": {
@@ -737,7 +1255,7 @@
"resourceHandle": {
"required": ["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",
+ "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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
@@ -748,11 +1266,33 @@
"type": "string"
},
"resourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
"type": "string"
},
"vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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"
}
}
@@ -771,12 +1311,88 @@
"type": "string"
},
"trunkResourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
"type": "string"
}
}
}
},
+ "vnfNetAttDefResource": {
+ "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 contains 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": {
+ "required": ["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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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 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 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"
@@ -818,7 +1434,7 @@
"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. It shall comply with the provisions defined in table 5.5.3.5-1.\nNOTE 1:\tETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on \n TOSCA specifications.\nNOTE 2:\tA VNFC CP is \"connected to\" an external CP if the VNFC CP is connected to an \n internal VL that exposes an external CP. A VNFC CP is \"exposed as\" an external \n CP if it is connected directly to an external VL.\nNOTE 3:\tThe information can be omitted because it is already available as part of the \n external CP information.\nNOTE 4: If only the value or the presence of this attribute is changed in the \"VnfcResourceInfo\"\n structure by an LCM operation occurrence, this does not represent a change that requires\n including a related \"AffectedVnfc\" structure in the VNF LCM operation occurrence notifications\n or the \"VnfLcmOpOcc\" structure related to this LCM operation occurrence.\n",
+ "description": "This type represents the information on virtualised compute and storage resources used by a VNFC in a VNF instance. Depending on the form of virtualisation container of the VNFC:\n - For a VNFC based on VM, a reference to the corresponding VirtualCompute shall be provided, and\n - For a VNFC based on OS container(s), a reference to the Compute MCIO shall be provided. Hence, exposure of\n information by the VNFM to the NFVO is at the MCIO level.\nIn addition, the references to the storage resources depend on the form of the VNFC:\n a) For a VNFC based on VM, storage resource identifiers shall refer to VirtualStorage resources, and\n b) For a VNFC based on OS container(s), storage resource identifiers shall refer to Storage MCIOs.\n\nNOTE 1:\tETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on \n TOSCA specifications.\nNOTE 2:\tA VNFC CP is \"connected to\" an external CP if the VNFC CP is connected to an \n internal VL that exposes an external CP. A VNFC CP is \"exposed as\" an external \n CP if it is connected directly to an external VL.\nNOTE 3:\tThe information can be omitted because it is already available as part of the \n external CP information.\nNOTE 4: If only the value or the presence of this attribute is changed in the \"VnfcResourceInfo\"\n structure by an LCM operation occurrence, this does not represent a change that requires\n including a related \"AffectedVnfc\" structure in the VNF LCM operation occurrence notifications\n or the \"VnfLcmOpOcc\" structure related to this LCM operation occurrence.\nNOTE 5: 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 internal CP, e.g. to build a link\n redundant mated pair in SR-IOV cases.\nNOTE 6: When more than one netAttDefResourceId is indicated, all shall belong to the same namespace.\n",
"type": "object",
"required": ["id", "vduId", "computeResource"],
"properties": {
@@ -837,7 +1453,7 @@
"computeResource": {
"required": ["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",
+ "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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
@@ -848,11 +1464,33 @@
"type": "string"
},
"resourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
"type": "string"
},
"vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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"
}
}
@@ -862,7 +1500,7 @@
"type": "string"
},
"storageResourceIds": {
- "description": "References to the VirtualStorage resources. The value refers to a VirtualStorageResourceInfo item in the VnfInstance.\n",
+ "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",
@@ -896,17 +1534,17 @@
"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 uses together with protocol-related information, like addresses. It shall comply with the provisions defined in table 5.5.3.9b-1.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the \n present document in a backwards-compatible way. In the current version of the present document, only IP over \n Ethernet is supported.\n",
+ "description": "This type describes the protocol layer(s) that a CP uses together with protocol-related information, like addresses.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the \n present document in a backwards-compatible way. In the current version of the present document, only IP over \n Ethernet is supported.\n",
"type": "object",
"required": ["layerProtocol"],
"properties": {
"layerProtocol": {
- "description": "The identifier of layer(s) and protocol(s) associated to the network address information.\nPermitted values: IP_OVER_ETHERNET See note.\n",
+ "description": "The identifier of layer(s) and protocol(s) associated to the network address information.\nPermitted values:\n - IP_OVER_ETHERNET\n - IP_FOR_VIRTUAL_CP\nSee note.\n",
"type": "string",
- "enum": ["IP_OVER_ETHERNET"]
+ "enum": ["IP_OVER_ETHERNET", "IP_FOR_VIRTUAL_CP"]
},
"ipOverEthernet": {
- "description": "This type represents information about a network address that has been assigned. It shall comply with the provisions defined in table 5.5.3.10-1.\nNOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, segmentationId shall be present. \n Otherwise it shall not be present.\nNOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the \n actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the \n transport header of the packets or it may be an identifier used between the application \n and the NFVI networking infrastructure to identify the network sub-interface of the trunk \n port in question. In the latter case the NFVI infrastructure will map this local segmentationId \n to whatever segmentationId is actually used by the NFVIΓÇÖs transport technology.\n",
+ "description": "This type represents information about a network address that has been assigned.\nNOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, segmentationId shall be present. \n Otherwise it shall not be present.\nNOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the \n actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the \n transport header of the packets or it may be an identifier used between the application \n and the NFVI networking infrastructure to identify the network sub-interface of the trunk \n port in question. In the latter case the NFVI infrastructure will map this local segmentationId \n to whatever segmentationId is actually used by the NFVI’s transport technology.\n",
"type": "object",
"anyOf": [
{
@@ -962,10 +1600,7 @@
"addressRange": {
"description": "An IP address range used, e.g. in case of egress connections. See note 2.\n",
"type": "object",
- "required": [
- "minAddress",
- "maxAddress"
- ],
+ "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",
@@ -980,13 +1615,30 @@
}
},
"subnetId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\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"
+ }
+ }
}
}
}
@@ -995,6 +1647,18 @@
"description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
"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"
+ },
+ "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 5 and 6. 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 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 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"
@@ -1002,10 +1666,6 @@
}
}
},
- "parentCpId": {
- "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 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"
@@ -1036,7 +1696,7 @@
"networkResource": {
"required": ["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",
+ "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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
@@ -1047,11 +1707,33 @@
"type": "string"
},
"resourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
"type": "string"
},
"vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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"
}
}
@@ -1068,7 +1750,7 @@
"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": {
- "description": "This type represents a link port of an internal VL of a VNF. It shall comply with the provisions defined in table 5.5.3.8 1.\nNOTE 1: Either cpInstanceId with cpInstanceType set to \"EXT_CP\" or any combination of cpInstanceId\n with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId (i.e. one or both of them) shall be \n present for a VnfLinkPortInfo. In case both cpInstanceId with cpInstanceType set to \"VNFC_CP\" \n and vipCpInstanceId are present, the two different CP instances share the linkport.\nNOTE 2: Annex A.4 of ETSI GS NFV-IFA 007 provides examples for configurations where both vipCpInstanceId\n and vnfcCpInstanceId are present (UC#5 and UC#5-b), only vnfcCpInstanceId is present (UC#2), or \n only vipCpInstanceId is present (UC6 and UC#6-b).\nNOTE 3: The value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\"\n attribute.\n",
+ "description": "This type represents a link port of an internal VL of a VNF.\nNOTE 1: Either cpInstanceId with cpInstanceType set to \"EXT_CP\" or any combination of cpInstanceId\n with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId (i.e. one or both of them) shall be \n present for a VnfLinkPortInfo. In case both cpInstanceId with cpInstanceType set to \"VNFC_CP\" \n and vipCpInstanceId are present, the two different CP instances share the linkport.\nNOTE 2: Annex A.4 of ETSI GS NFV-IFA 007 provides examples for configurations where both vipCpInstanceId\n and vnfcCpInstanceId are present (UC#5 and UC#5-b), only vnfcCpInstanceId is present (UC#2), or \n only vipCpInstanceId is present (UC6 and UC#6-b).\nNOTE 3: The value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\"\n attribute.\n",
"type": "object",
"required": ["id", "resourceHandle"],
"properties": {
@@ -1079,7 +1761,7 @@
"resourceHandle": {
"required": ["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",
+ "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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
@@ -1090,11 +1772,33 @@
"type": "string"
},
"resourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
"type": "string"
},
"vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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"
}
}
@@ -1113,7 +1817,7 @@
"type": "string"
},
"trunkResourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
"type": "string"
}
}
@@ -1149,7 +1853,7 @@
"storageResource": {
"required": ["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",
+ "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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
@@ -1160,11 +1864,33 @@
"type": "string"
},
"resourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
"type": "string"
},
"vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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"
}
}
@@ -1183,6 +1909,63 @@
}
}
}
+ },
+ "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. Within the CISM, an MCIO controller monitors the actual state of an MCIO representing the set of VNFC instances realized by one or a set of OS containers and compare it to the desired state as specified in the respective declarative descriptor. It triggers actions toward the CIS to align the actual to the desired state. Monitoring the actual state includes monitoring the number of MCIO instances available at any specific point in time. In addition, an MCIO controller maintains properties and runtime information on the MCIO instances which have been created based on the same VDU. The McioInfo data structure provides the runtime information on the MCIOs obtained from the MCIO controller.\nNOTE: There are different types of MCIOs. The set of VNFC instances based on the same VDU is represented \n by one MCIO, e.g. of type Deployment. Each individual VNFC instance is represented by another type \n of MCIO, e.g. a POD.\n\nRuntime information of the set of OS containers realizing an individual VNFC instance is not part of the McioInfo data structure; such runtime information is provided in the ResourceHandle data structure referenced from the VnfcResourceInfo. The McioInfo does not provide runtime information of a constituent VNFC instance created based on a specific VDU.\nNOTE 1: The type of MCIO as specified in the declarative descriptor of the MCIO, and that can be read from \n the CISM. EXAMPLE: In case of MCIOs managed by Kubernetes®, the type of MCIO corresponds to the \n “kind†property of the declarative descriptor.\nNOTE 2: If the attribute additionalInfo is present, it may contain runtime information on the actual and \n desired state of the MCIO(s). \nNOTE 3: When the container infrastructure service is a Kubernetes® instance, the mcioId is the combined \n values from the kind and name fields of the Kubernetes resource object, separated by a slash. \n Example: \"Deployment/abcd\". \nNOTE 4: When the container infrastructure service is a Kubernetes® instance, the mcioName is the name \n field of the resource object. \n",
+ "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": "An identifier that is unique within a VNF descriptor.\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 5.5.4.9. Additional values are also permitted. See note 1.\n",
+ "type": "string",
+ "enum": ["Deployment", "Statefulset"]
+ },
+ "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 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/SOL003/VNFLifecycleManagement-API/schemas/vnfInstances.schema.json b/SOL003/VNFLifecycleManagement-API/schemas/vnfInstances.schema.json
index 46632c64566c43d66fdb07de6589170627213e00..a25322e6a67dd3746cfbace583dfb30d7763ad8a 100644
--- a/SOL003/VNFLifecycleManagement-API/schemas/vnfInstances.schema.json
+++ b/SOL003/VNFLifecycleManagement-API/schemas/vnfInstances.schema.json
@@ -1,7 +1,7 @@
{
- "type": "array",
- "items": {
- "description": "This type represents a VNF instance. It shall comply with the provisions defined in table 5.5.2.2-1.\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",
+ "type": "array",
+ "items": {
+ "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",
"type": "object",
"required": [
"id",
@@ -10,7 +10,8 @@
"vnfProductName",
"vnfSoftwareVersion",
"vnfdVersion",
- "instantiationState"
+ "instantiationState",
+ "_links"
],
"properties": {
"id": {
@@ -50,10 +51,10 @@
"type": "object"
},
"vimConnectionInfo": {
- "description": "Information about VIM 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 VNF-related resource management in direct mode is pplicable. 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.\n",
"type": "object",
"additionalProperties": {
- "description": "This type represents parameters to connect to a VIM for managing the resources of a VNF instance. * 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 is provided through a secure connection over\n HTTP Secure (HTTP over SSL/TLS), and the connection might also be established through a VPN\n (for example TLS-based VPN tunnelling) for site-to-site connection, the \"accessInfo\" JSON data\n structure, and the sensitive data related information (\"username\"/\"password\" as required properties\n for authentication purpose), will be transmitted as plain text through a TLS tunnel without additional\n encoding/encryption before transmitting it, making the sensitive data visible to the endpoint.\n The base64 encoded certificates are only used by the VNFM to verify the authenticity of the\n interface endpoint of the VIM.\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",
"type": "object",
"required": ["vimType"],
"properties": {
@@ -62,7 +63,69 @@
"type": "string"
},
"vimType": {
- "description": "Discriminator for the different types of the VIM information. The value of this attribute determines the structure of the \"interfaceInfo\" and \"accessInfo\" attributes, based on the type of the VIM. The set of permitted values is expected to change over time as new types or versions of VIMs become available. The ETSI NFV registry of VIM-related information provides access to information about VimConnectionInfo definitions for various VIM types. The structure of the registry is defined in Annex C of SOL003.\n",
+ "description": "Discriminator for the different types of the VIM information. The value of this attribute determines the structure of the \"interfaceInfo\" and \"accessInfo\" attributes, based on the type of the VIM., CISM, CIR or MCIOP repository. The set of permitted values is expected to change over time as new types or versions of VIMs become available. The ETSI NFV registry of VIM-related information [i.3] provides access to information about VimConnectionInfo definitions for various VIM, CISM, CIR or MCIOP repository types. The structure of the registry is defined in annex C.\n",
+ "type": "string"
+ },
+ "interfaceInfo": {
+ "description": "This 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"
+ },
+ "accessInfo": {
+ "description": "This 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"
+ },
+ "extra": {
+ "description": "This 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"
+ }
+ }
+ }
+ },
+ "cirConnectionInfo": {
+ "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",
+ "type": "object",
+ "required": ["vimType"],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vimType": {
+ "description": "Discriminator for the different types of the VIM information. The value of this attribute determines the structure of the \"interfaceInfo\" and \"accessInfo\" attributes, based on the type of the VIM., CISM, CIR or MCIOP repository. The set of permitted values is expected to change over time as new types or versions of VIMs become available. The ETSI NFV registry of VIM-related information [i.3] provides access to information about VimConnectionInfo definitions for various VIM, CISM, CIR or MCIOP repository types. The structure of the registry is defined in annex C.\n",
+ "type": "string"
+ },
+ "interfaceInfo": {
+ "description": "This 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"
+ },
+ "accessInfo": {
+ "description": "This 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"
+ },
+ "extra": {
+ "description": "This 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"
+ }
+ }
+ }
+ },
+ "mciopRepositoryInfo": {
+ "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",
+ "type": "object",
+ "required": ["vimType"],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vimType": {
+ "description": "Discriminator for the different types of the VIM information. The value of this attribute determines the structure of the \"interfaceInfo\" and \"accessInfo\" attributes, based on the type of the VIM., CISM, CIR or MCIOP repository. The set of permitted values is expected to change over time as new types or versions of VIMs become available. The ETSI NFV registry of VIM-related information [i.3] provides access to information about VimConnectionInfo definitions for various VIM, CISM, CIR or MCIOP repository types. The structure of the registry is defined in annex C.\n",
"type": "string"
},
"interfaceInfo": {
@@ -81,14 +144,14 @@
}
},
"instantiationState": {
- "description": "The instantiation state of the VNF.\n",
+ "description": "The instantiation state of the VNF. Permitted 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"],
+ "required": ["flavourId", "vnfState", "extCpInfo"],
"properties": {
"flavourId": {
"description": "An identifier that is unique within a VNF descriptor.\n",
@@ -100,11 +163,12 @@
"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. This attribute shall be present if the VNF supports scaling. See clause B.2 for an explanation of VNF scaling.\n",
+ "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. This attribute shall be present if the VNF supports scaling. See clause B.2 for an explanation of VNF scaling.\n",
"type": "array",
"items": {
- "required": ["aspectId", "scaleLevel"],
+ "description": "This type represents the scale level of a VNF instance related to a scaling aspect.\n",
"type": "object",
+ "required": ["aspectId", "scaleLevel"],
"properties": {
"aspectId": {
"description": "An identifier that is unique within a VNF descriptor.\n",
@@ -114,9 +178,9 @@
"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"
+ "scaleToLevel": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
}
}
}
@@ -125,8 +189,9 @@
"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"],
+ "description": "This type represents the scale level of a VNF instance related to a scaling aspect.\n",
"type": "object",
+ "required": ["aspectId", "scaleLevel"],
"properties": {
"aspectId": {
"description": "An identifier that is unique within a VNF descriptor.\n",
@@ -136,9 +201,9 @@
"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"
+ "scaleToLevel": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
}
}
}
@@ -148,7 +213,7 @@
"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 5.5.3.17 1.\nNOTE 1:\tThe attributes \"associatedVnfcCpId\", \"associatedVipCpId\" and \"associatedVnfVirtualLinkId\" \n are mutually exclusive. Exactly one shall be present.\nNOTE 2:\tAn external CP instance is not associated to a link port in the cases indicated for the \n ΓÇ£extLinkPortsΓÇ¥ attribute in clause 4.4.1.11.\n",
+ "description": "This type represents information about an external CP of a VNF.\nNOTE 1:\tThe attributes \"associatedVnfcCpId\", \"associatedVipCpId\", \"associatedVirtualCpId\" and \n \"associatedVnfVirtualLinkId\" are mutually exclusive. Exactly one shall be present.\nNOTE 2:\tAn external CP instance is not associated to a link port in the cases indicated for the \n “extLinkPorts†attribute in clause 4.4.1.11.\nNOTE 3: 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 \n CP, e.g. to build a link redundant mated pair in SR-IOV cases.\nNOTE 4: When more than one netAttDefResourceId is indicated, all shall belong to the same namespace.\n",
"type": "object",
"required": ["id", "cpdId", "cpConfigId", "cpProtocolInfo"],
"oneOf": [
@@ -183,17 +248,17 @@
"description": "Network protocol information for this CP.\n",
"type": "array",
"items": {
- "description": "This type describes the protocol layer(s) that a CP uses together with protocol-related information, like addresses. It shall comply with the provisions defined in table 5.5.3.9b-1.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the \n present document in a backwards-compatible way. In the current version of the present document, only IP over \n Ethernet is supported.\n",
+ "description": "This type describes the protocol layer(s) that a CP uses together with protocol-related information, like addresses.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the \n present document in a backwards-compatible way. In the current version of the present document, only IP over \n Ethernet is supported.\n",
"type": "object",
"required": ["layerProtocol"],
"properties": {
"layerProtocol": {
- "description": "The identifier of layer(s) and protocol(s) associated to the network address information.\nPermitted values: IP_OVER_ETHERNET See note.\n",
+ "description": "The identifier of layer(s) and protocol(s) associated to the network address information.\nPermitted values:\n - IP_OVER_ETHERNET\n - IP_FOR_VIRTUAL_CP\nSee note.\n",
"type": "string",
- "enum": ["IP_OVER_ETHERNET"]
+ "enum": ["IP_OVER_ETHERNET", "IP_FOR_VIRTUAL_CP"]
},
"ipOverEthernet": {
- "description": "This type represents information about a network address that has been assigned. It shall comply with the provisions defined in table 5.5.3.10-1.\nNOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, segmentationId shall be present. \n Otherwise it shall not be present.\nNOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the \n actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the \n transport header of the packets or it may be an identifier used between the application \n and the NFVI networking infrastructure to identify the network sub-interface of the trunk \n port in question. In the latter case the NFVI infrastructure will map this local segmentationId \n to whatever segmentationId is actually used by the NFVIΓÇÖs transport technology.\n",
+ "description": "This type represents information about a network address that has been assigned.\nNOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, segmentationId shall be present. \n Otherwise it shall not be present.\nNOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the \n actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the \n transport header of the packets or it may be an identifier used between the application \n and the NFVI networking infrastructure to identify the network sub-interface of the trunk \n port in question. In the latter case the NFVI infrastructure will map this local segmentationId \n to whatever segmentationId is actually used by the NFVI’s transport technology.\n",
"type": "object",
"anyOf": [
{
@@ -264,13 +329,30 @@
}
},
"subnetId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\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"
+ }
+ }
}
}
}
@@ -291,9 +373,21 @@
"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"
+ },
+ "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 with the intention of being globally unique.\n",
+ "type": "string"
+ }
}
}
}
@@ -303,7 +397,7 @@
"type": "array",
"minItems": 1,
"items": {
- "description": "This type provides information related to virtual IP (VIP) CP. It shall comply with the provisions defined in table 5.5.3.28-1.\nNOTE 1:\tIt is possible that there is no associated VnfcCp because the VIP CP is available but not associated yet. NOTE 2: If only the value or the presence of this attribute is changed in the \"VipCpInfo\" structure by an LCM operation occurrence, this does not represent a change that requires including a related \"AffectedVipCp\" structure in the VNF LCM operation occurrence notifications or the \"VnfLcmOpOcc\" structure related to this LCM operation occurrence.\n",
+ "description": "This type provides information related to virtual IP (VIP) CP.\nNOTE 1:\tIt is possible that there is no associated VnfcCp because the VIP CP is available but not associated yet. NOTE 2: If only the value or the presence of this attribute is changed in the \"VipCpInfo\" structure by an LCM operation occurrence, this does not represent a change that requires including a related \"AffectedVipCp\" structure in the VNF LCM operation occurrence notifications or the \"VnfLcmOpOcc\" structure related to this LCM operation occurrence.\n",
"type": "object",
"required": ["cpInstanceId", "cpdId"],
"properties": {
@@ -327,17 +421,17 @@
"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 uses together with protocol-related information, like addresses. It shall comply with the provisions defined in table 5.5.3.9b-1.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the \n present document in a backwards-compatible way. In the current version of the present document, only IP over \n Ethernet is supported.\n",
+ "description": "This type describes the protocol layer(s) that a CP uses together with protocol-related information, like addresses.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the \n present document in a backwards-compatible way. In the current version of the present document, only IP over \n Ethernet is supported.\n",
"type": "object",
"required": ["layerProtocol"],
"properties": {
"layerProtocol": {
- "description": "The identifier of layer(s) and protocol(s) associated to the network address information.\nPermitted values: IP_OVER_ETHERNET See note.\n",
+ "description": "The identifier of layer(s) and protocol(s) associated to the network address information.\nPermitted values:\n - IP_OVER_ETHERNET\n - IP_FOR_VIRTUAL_CP\nSee note.\n",
"type": "string",
- "enum": ["IP_OVER_ETHERNET"]
+ "enum": ["IP_OVER_ETHERNET", "IP_FOR_VIRTUAL_CP"]
},
"ipOverEthernet": {
- "description": "This type represents information about a network address that has been assigned. It shall comply with the provisions defined in table 5.5.3.10-1.\nNOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, segmentationId shall be present. \n Otherwise it shall not be present.\nNOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the \n actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the \n transport header of the packets or it may be an identifier used between the application \n and the NFVI networking infrastructure to identify the network sub-interface of the trunk \n port in question. In the latter case the NFVI infrastructure will map this local segmentationId \n to whatever segmentationId is actually used by the NFVIΓÇÖs transport technology.\n",
+ "description": "This type represents information about a network address that has been assigned.\nNOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, segmentationId shall be present. \n Otherwise it shall not be present.\nNOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the \n actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the \n transport header of the packets or it may be an identifier used between the application \n and the NFVI networking infrastructure to identify the network sub-interface of the trunk \n port in question. In the latter case the NFVI infrastructure will map this local segmentationId \n to whatever segmentationId is actually used by the NFVI’s transport technology.\n",
"type": "object",
"anyOf": [
{
@@ -408,13 +502,30 @@
}
},
"subnetId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\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"
+ }
+ }
}
}
}
@@ -432,12 +543,246 @@
"type": "string"
},
"metadata": {
- "description": "Metadata about this VIP CP.\n",
+ "description": "This 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"
+ }
+ }
+ }
+ },
+ "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 provides information related to a virtual CP instance of a VNF.\nNOTE: A consumer of the VNF LCM interface can learn the actual VNFC instances implementing the service \n accessible via the virtual CP instance by querying the \"vnfcResourceInfo\" from the \"InstantiatedVnfInfo\" \n and filtering by corresponding \"vduIds\" values.\n",
+ "type": "object",
+ "required": ["cpInstanceId", "cpdId", "resourceHandle", "vduIds"],
+ "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": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "resourceHandle": {
+ "required": ["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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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 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"
+ "description": "This type describes the protocol layer(s) that a CP uses together with protocol-related information, like addresses.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the \n present document in a backwards-compatible way. In the current version of the present document, only IP over \n Ethernet is supported.\n",
+ "type": "object",
+ "required": ["layerProtocol"],
+ "properties": {
+ "layerProtocol": {
+ "description": "The identifier of layer(s) and protocol(s) associated to the network address information.\nPermitted 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:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, segmentationId shall be present. \n Otherwise it shall not be present.\nNOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the \n actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the \n transport header of the packets or it may be an identifier used between the application \n and the NFVI networking infrastructure to identify the network sub-interface of the trunk \n port in question. In the latter case the NFVI infrastructure will map this local segmentationId \n to whatever segmentationId is actually used by the NFVI’s transport technology.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "required": ["macAddress"]
+ },
+ {
+ "required": ["ipAddresses"]
+ }
+ ],
+ "oneOf": [
+ {
+ "required": ["addresses"]
+ },
+ {
+ "required": ["addressRange"]
+ }
+ ],
+ "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 notes 3 and 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"],
+ "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. 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.\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"
+ }
+ }
+ }
+ }
+ }
+ },
+ "vduIds": {
+ "description": "Reference to the VDU(s) which implement the service accessible via the virtual CP instance. See note.\n",
+ "type": "array",
+ "minItems": 1,
+ "items": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
}
+ },
+ "additionalServiceInfo": {
+ "description": "Additional service identification information of the virtual CP instance.\n",
+ "type": "array",
+ "items": {
+ "description": "This type provides 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 \n termination within the VNF, such as for example a URL path information in an HTTP request required \n to allow a single virtual CP IP address to be used for several HTTP based services that use the \n same port number.\n",
+ "type": "object",
+ "required": ["portInfo"],
+ "properties": {
+ "portInfo": {
+ "description": "Service port numbers exposed by the virtual CP instance.\n",
+ "minItems": 1,
+ "type": "array",
+ "items": {
+ "description": "This type describes the service identifying port properties exposed by the virtual CP instance.\n",
+ "type": "object",
+ "required": ["name", "port", "portConfigurable"],
+ "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.\nPermitted values: - TCP - UDP - SCTP\n",
+ "type": "string",
+ "enum": ["TCP", "UDP", "SCTP"]
+ },
+ "port": {
+ "description": "The L4 port number exposed by the virtual CP instance.\n",
+ "type": "integer"
+ },
+ "portConfigurable": {
+ "description": "The Boolean is a data type having two values (true and false).\n",
+ "type": "boolean"
+ }
+ }
+ }
+ },
+ "serviceInfo": {
+ "description": "This 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"
+ }
+ }
+ }
+ },
+ "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 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"
}
}
}
@@ -446,7 +791,7 @@
"description": "Information about the external VLs the VNF instance is connected to.\n",
"type": "array",
"items": {
- "description": "This type represents information about an external VL. It shall comply with the provisions defined in table 5.5.3.2-1.\nNOTE:\tThis attribute reflects the current configuration information that has resulted from merging into this attribute \n the \"VnfExtCpData\" information which was passed as part of the \"ExtVirtualLinkData\" structure in the input of the \n most recent VNF LCM operation such as \"InstantiateVnfRequest\", \"ChangeExtVnfConnectivityRequest\", \"ChangeVnfFlavourRequest\" \n or \"ChangeCurrentVnfPkgRequest\", or in the Grant response. If applying such change results in an empty list of \n \"currentVnfExtCpData\" structure instances, the affected instance of \"ExtVirtualLinkInfo\" shall be removed from its \n parent data structure.\n",
+ "description": "This type represents information about an external VL.\nNOTE:\tThis attribute reflects the current configuration information that has resulted from merging into this attribute \n the \"VnfExtCpData\" information which was passed as part of the \"ExtVirtualLinkData\" structure in the input of the \n most recent VNF LCM operation such as \"InstantiateVnfRequest\", \"ChangeExtVnfConnectivityRequest\", \"ChangeVnfFlavourRequest\" \n or \"ChangeCurrentVnfPkgRequest\", or in the Grant response. If applying such change results in an empty list of \n \"currentVnfExtCpData\" structure instances, the affected instance of \"ExtVirtualLinkInfo\" shall be removed from its \n parent data structure.\n",
"type": "object",
"required": ["id", "resourceHandle", "currentVnfExtCpData"],
"properties": {
@@ -457,7 +802,7 @@
"resourceHandle": {
"required": ["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",
+ "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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
@@ -468,11 +813,33 @@
"type": "string"
},
"resourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
"type": "string"
},
"vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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"
}
}
@@ -481,7 +848,7 @@
"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. It shall comply with the provisions defined in table 5.5.3.9-1.\nNOTE 1:\tThe use cases UC#4 and UC#5 in clause A.4 of ETSI GS NFV-IFA 007 provide examples for such a configuration. NOTE 2:\tThe value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\" attribute.\n",
+ "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.\nNOTE 1:\tThe use cases UC#4 and UC#5 in clause A.4 of ETSI GS NFV-IFA 007 provide examples for such a configuration. NOTE 2:\tThe value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\" attribute.\n",
"type": "object",
"required": ["id", "resourceHandle"],
"properties": {
@@ -492,7 +859,7 @@
"resourceHandle": {
"required": ["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",
+ "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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
@@ -503,11 +870,33 @@
"type": "string"
},
"resourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
"type": "string"
},
"vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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"
}
}
@@ -521,7 +910,7 @@
"type": "string"
},
"trunkResourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
"type": "string"
}
}
@@ -531,7 +920,7 @@
"description": "Allows the API consumer to read the current CP configuration information for the connection of external CPs to the external virtual link. See note.\n",
"type": "array",
"items": {
- "description": "This type represents configuration information for external CPs created. * NOTE 1: \tIn case this identifier refers to a CPD with trunking enabled, the external CP instances created\n from this CPD will represent ports in a trunk.\n* NOTE 2: \tWithin one VNF instance, all VNFC instances created from a particular VDU have the same external\n connectivity. Thus, given a particular value of the \"cpdId\" attribute, there shall be one\n \"cpConfig\" entry for each VNFC instance that has been or can be created from a VDU which includes\n a CPD identified by the \"cpdId\" attribute. If the cpConfig represents a subport in a trunk,\n all \"cpConfig\" entries in this list shall have the same segmentationId, which means they are\n connected to the same set of external VLs via the trunk.\n* NOTE 3: \tThe map entry value shall be set to \"null\" in order to delete a \"VnfExtCpConfig\" entry identified\n by a particular key value from the map, i.e. for the disconnection of an existing external\n CP instance addressed by cpInstanceId in the deleted map entry from a particular external\n virtual link, and deletion of that instance in case it represents a subport. Deleting the\n last key from the map removes the affected instance of the \"VnfExtCpData\" structure from\n its parent data structure.\n* NOTE 4: If, as defined by the input parameters of a \"ChangeVnfFlavour\", \"ChangeExtVnfConnectivity\" or \n \"ChangeCurrentVnfPkg\" operation or as part of the Grant response for any of these operations, a \n cpConfig map entry identified by a particular map key value is moved into another \"ExtVirtualLinkData\"\n or \"VnfExtCpData\" structure, this particular cpConfig map entry may be used by an external CP instance\n different than the one that has used it before the operation, or by no external CP instance at all.\n Renaming a CPD identifier during the \"changeCurrentVnfPkg\" operation does not count as moving the\n related \"cpConfig\" map entries to a new \"extCpData\" structure.\n",
+ "description": "This type represents configuration information for external CPs created. * NOTE 1: \tIn case this identifier refers to a CPD with trunking enabled, the external CP instances created\n from this CPD will represent ports in a trunk.\n* NOTE 2: \tWithin one VNF instance, all VNFC instances created from a particular VDU have the same external\n connectivity. Thus, given a particular value of the \"cpdId\" attribute, there shall be one\n \"cpConfig\" entry for each VNFC instance that has been or can be created from a VDU which includes\n a CPD identified by the \"cpdId\" attribute. If the cpConfig represents a subport in a trunk,\n all \"cpConfig\" entries in this list shall have the same segmentationId, which means they are\n connected to the same set of external VLs via the trunk.\n* NOTE 3: \tThe map entry value shall be set to \"null\" in order to delete a \"VnfExtCpConfig\" entry identified\n by a particular key value from the map, i.e. for the disconnection of an existing external\n CP instance addressed by cpInstanceId in the deleted map entry from a particular external\n virtual link, and deletion of that instance in case it represents a subport. Deleting the\n last key from the map removes the affected instance of the \"VnfExtCpData\" structure from\n its parent data structure.\n* NOTE 4: If, as defined by the input parameters of a \"ChangeVnfFlavour\", \"ChangeExtVnfConnectivity\" or\n \"ChangeCurrentVnfPkg\" operation or as part of the Grant response for any of these operations, a cpConfig\n map entry identified by a particular map key value is moved into another \"ExtVirtualLinkData\" or\n \"VnfExtCpData\" structure, this particular cpConfig map entry may be used by an external CP instance\n different than the one that has used it before the operation, or by no external CP instance at all.\n Renaming a CPD identifier during the \"changeCurrentVnfPkg\" operation does not count as moving the related\n \"cpConfig\" map entries to a new \"extCpData\" structure.\n",
"type": "object",
"required": ["cpdId"],
"properties": {
@@ -540,16 +929,19 @@
"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). See notes 2, 3 and 4.\n",
+ "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 network address information per instance of an external connection point. In case a link port is provided, the VNFM shall use that link port when connecting the external CP to the external VL. In a link port is not provided, the VNFM shall create a link port on the external VL, and use that link port to connect the external CP to the external VL. * NOTE: The following conditions apply to the attributes \"linkPortId\" and \"cpProtocolData\":\n 1) Void.\n 2) At least one of the \"linkPortId\" and \"cpProtocolData\" attributes shall be present for an external\n CP instance representing a subport that is to be created, or an external CP instance that is to be\n created by creating the corresponding VNFC or VNF instance during the current or a subsequent LCM\n operation, or for an existing external CP instance that is to be re-configured or added to a\n 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\n a pre created link port, and the VNFM can use means outside the scope of the present document to obtain\n the pre-configured address information for the connection point from the resource representing\n the link port.\n 5) If both \"cpProtocolData\" and \"linkportId\" are provided, the API consumer shall ensure that the\n cpProtocolData can be used with the pre-created link port referenced by \"linkPortId\".\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) 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",
"anyOf": [
{
"required": ["linkPortId"]
},
{
"required": ["cpProtocolData"]
+ },
+ {
+ "required": ["netAttDefResourceId"]
}
],
"type": "object",
@@ -566,8 +958,16 @@
"description": "Indicates to the VNFM the need to create a dedicated link port for the external CP. If set to True, the VNFM shall create a link port. If set to False, the VNFM shall not create a link port. 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"
},
+ "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 2, 3 and 4.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ },
"cpProtocolData": {
- "description": "Parameters for configuring the network protocols on the link port that connects the CP to a VL. See note.\n",
+ "description": "Parameters for configuring the network protocols on the link port that connects the CP to a VL. See notes 1 and 2.\n",
"type": "array",
"items": {
"description": "This type represents network protocol data. * NOTE:\tThis attribute allows to signal the addition of further types of layer and protocol\n in future versions of the present document in a backwards-compatible way. In the current\n version of the present document, only IP over Ethernet is supported.\n",
@@ -575,12 +975,15 @@
"required": ["layerProtocol"],
"properties": {
"layerProtocol": {
- "description": "Identifier of layer(s) and protocol(s). See note.\n",
+ "description": "Identifier of layer(s) and protocol(s). Permitted values:\n - IP_OVER_ETHERNET.\n - IP_FOR_VIRTUAL_CP\nSee note\n",
"type": "string",
- "enum": ["IP_OVER_ETHERNET"]
+ "enum": [
+ "IP_OVER_ETHERNET",
+ "IP_FOR_VIRTUAL_CP"
+ ]
},
"ipOverEthernet": {
- "description": "This type represents network address data for IP over Ethernet. * NOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. * NOTE 2:\tExactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present. * NOTE 3:\tIf the CP instance represents a subport in a trunk, segmentationId shall be present.\n Otherwise it shall not be present.\n* NOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the actual\n network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header\n of the packets or it may be an identifier used between the application and the NFVI networking\n infrastructure to identify the network sub-interface of the trunk port in question. In the latter\n case the NFVI infrastructure will map this local segmentationId to whatever segmentationId is\n actually used by the NFVIΓÇÖs transport technology.\n",
+ "description": "This type represents network address data for IP over Ethernet. * NOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. * NOTE 2:\tExactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present. * NOTE 3:\tIf the CP instance represents a subport in a trunk, segmentationId shall be present.\n Otherwise it shall not be present.\n* NOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the actual\n network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header\n of the packets or it may be an identifier used between the application and the NFVI networking\n infrastructure to identify the network sub-interface of the trunk port in question. In the latter\n case the NFVI infrastructure will map this local segmentationId to whatever segmentationId is\n actually used by the NFVI’s transport technology.\n",
"type": "object",
"anyOf": [
{
@@ -608,7 +1011,7 @@
"format": "MAC"
},
"segmentationType": {
- "description": "Specifies the encapsulation type for the traffics coming in and out of the trunk subport. Permitted values: -\tVLAN: the subport uses VLAN as encapsulation type. -\tINHERIT: the subport gets its segmentation type from the network itΓÇÖs 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",
+ "description": "Specifies the encapsulation type for the traffics coming in and out of the trunk subport. Permitted values: -\tVLAN: the subport uses VLAN as encapsulation type. -\tINHERIT: the subport gets its segmentation type from the network it’s 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"]
},
@@ -662,13 +1065,30 @@
}
},
"subnetId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
"type": "string"
}
}
}
}
}
+ },
+ "virtualCpAddress": {
+ "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",
+ "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"
+ }
+ }
}
}
}
@@ -678,6 +1098,85 @@
}
}
}
+ },
+ "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 contains 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": {
+ "required": ["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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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 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 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"
+ }
+ }
+ }
+ }
}
}
}
@@ -704,7 +1203,7 @@
"networkResource": {
"required": ["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",
+ "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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
@@ -715,11 +1214,33 @@
"type": "string"
},
"resourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
"type": "string"
},
"vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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"
}
}
@@ -728,7 +1249,7 @@
"description": "Link ports of this VL.\n",
"type": "array",
"items": {
- "description": "This type represents a link port of an internal VL of a VNF. It shall comply with the provisions defined in table 5.5.3.8 1.\nNOTE 1: Either cpInstanceId with cpInstanceType set to \"EXT_CP\" or any combination of cpInstanceId\n with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId (i.e. one or both of them) shall be \n present for a VnfLinkPortInfo. In case both cpInstanceId with cpInstanceType set to \"VNFC_CP\" \n and vipCpInstanceId are present, the two different CP instances share the linkport.\nNOTE 2: Annex A.4 of ETSI GS NFV-IFA 007 provides examples for configurations where both vipCpInstanceId\n and vnfcCpInstanceId are present (UC#5 and UC#5-b), only vnfcCpInstanceId is present (UC#2), or \n only vipCpInstanceId is present (UC6 and UC#6-b).\nNOTE 3: The value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\"\n attribute.\n",
+ "description": "This type represents a link port of an internal VL of a VNF.\nNOTE 1: Either cpInstanceId with cpInstanceType set to \"EXT_CP\" or any combination of cpInstanceId\n with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId (i.e. one or both of them) shall be \n present for a VnfLinkPortInfo. In case both cpInstanceId with cpInstanceType set to \"VNFC_CP\" \n and vipCpInstanceId are present, the two different CP instances share the linkport.\nNOTE 2: Annex A.4 of ETSI GS NFV-IFA 007 provides examples for configurations where both vipCpInstanceId\n and vnfcCpInstanceId are present (UC#5 and UC#5-b), only vnfcCpInstanceId is present (UC#2), or \n only vipCpInstanceId is present (UC6 and UC#6-b).\nNOTE 3: The value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\"\n attribute.\n",
"type": "object",
"required": ["id", "resourceHandle"],
"properties": {
@@ -739,7 +1260,7 @@
"resourceHandle": {
"required": ["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",
+ "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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
@@ -750,11 +1271,33 @@
"type": "string"
},
"resourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
"type": "string"
},
"vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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"
}
}
@@ -773,12 +1316,91 @@
"type": "string"
},
"trunkResourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
"type": "string"
}
}
}
},
+ "vnfNetAttDefResource": {
+ "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 contains 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": {
+ "required": ["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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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 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 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"
@@ -820,7 +1442,7 @@
"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. It shall comply with the provisions defined in table 5.5.3.5-1.\nNOTE 1:\tETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on \n TOSCA specifications.\nNOTE 2:\tA VNFC CP is \"connected to\" an external CP if the VNFC CP is connected to an \n internal VL that exposes an external CP. A VNFC CP is \"exposed as\" an external \n CP if it is connected directly to an external VL.\nNOTE 3:\tThe information can be omitted because it is already available as part of the \n external CP information.\nNOTE 4: If only the value or the presence of this attribute is changed in the \"VnfcResourceInfo\"\n structure by an LCM operation occurrence, this does not represent a change that requires\n including a related \"AffectedVnfc\" structure in the VNF LCM operation occurrence notifications\n or the \"VnfLcmOpOcc\" structure related to this LCM operation occurrence.\n",
+ "description": "This type represents the information on virtualised compute and storage resources used by a VNFC in a VNF instance. Depending on the form of virtualisation container of the VNFC:\n - For a VNFC based on VM, a reference to the corresponding VirtualCompute shall be provided, and\n - For a VNFC based on OS container(s), a reference to the Compute MCIO shall be provided. Hence, exposure of\n information by the VNFM to the NFVO is at the MCIO level.\nIn addition, the references to the storage resources depend on the form of the VNFC:\n a) For a VNFC based on VM, storage resource identifiers shall refer to VirtualStorage resources, and\n b) For a VNFC based on OS container(s), storage resource identifiers shall refer to Storage MCIOs.\n\nNOTE 1:\tETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on \n TOSCA specifications.\nNOTE 2:\tA VNFC CP is \"connected to\" an external CP if the VNFC CP is connected to an \n internal VL that exposes an external CP. A VNFC CP is \"exposed as\" an external \n CP if it is connected directly to an external VL.\nNOTE 3:\tThe information can be omitted because it is already available as part of the \n external CP information.\nNOTE 4: If only the value or the presence of this attribute is changed in the \"VnfcResourceInfo\"\n structure by an LCM operation occurrence, this does not represent a change that requires\n including a related \"AffectedVnfc\" structure in the VNF LCM operation occurrence notifications\n or the \"VnfLcmOpOcc\" structure related to this LCM operation occurrence.\nNOTE 5: 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 internal CP, e.g. to build a link\n redundant mated pair in SR-IOV cases.\nNOTE 6: When more than one netAttDefResourceId is indicated, all shall belong to the same namespace.\n",
"type": "object",
"required": ["id", "vduId", "computeResource"],
"properties": {
@@ -839,7 +1461,7 @@
"computeResource": {
"required": ["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",
+ "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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
@@ -850,11 +1472,33 @@
"type": "string"
},
"resourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
"type": "string"
},
"vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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"
}
}
@@ -864,7 +1508,7 @@
"type": "string"
},
"storageResourceIds": {
- "description": "References to the VirtualStorage resources. The value refers to a VirtualStorageResourceInfo item in the VnfInstance.\n",
+ "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",
@@ -898,17 +1542,17 @@
"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 uses together with protocol-related information, like addresses. It shall comply with the provisions defined in table 5.5.3.9b-1.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the \n present document in a backwards-compatible way. In the current version of the present document, only IP over \n Ethernet is supported.\n",
+ "description": "This type describes the protocol layer(s) that a CP uses together with protocol-related information, like addresses.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the \n present document in a backwards-compatible way. In the current version of the present document, only IP over \n Ethernet is supported.\n",
"type": "object",
"required": ["layerProtocol"],
"properties": {
"layerProtocol": {
- "description": "The identifier of layer(s) and protocol(s) associated to the network address information.\nPermitted values: IP_OVER_ETHERNET See note.\n",
+ "description": "The identifier of layer(s) and protocol(s) associated to the network address information.\nPermitted values:\n - IP_OVER_ETHERNET\n - IP_FOR_VIRTUAL_CP\nSee note.\n",
"type": "string",
- "enum": ["IP_OVER_ETHERNET"]
+ "enum": ["IP_OVER_ETHERNET", "IP_FOR_VIRTUAL_CP"]
},
"ipOverEthernet": {
- "description": "This type represents information about a network address that has been assigned. It shall comply with the provisions defined in table 5.5.3.10-1.\nNOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, segmentationId shall be present. \n Otherwise it shall not be present.\nNOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the \n actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the \n transport header of the packets or it may be an identifier used between the application \n and the NFVI networking infrastructure to identify the network sub-interface of the trunk \n port in question. In the latter case the NFVI infrastructure will map this local segmentationId \n to whatever segmentationId is actually used by the NFVIΓÇÖs transport technology.\n",
+ "description": "This type represents information about a network address that has been assigned.\nNOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, segmentationId shall be present. \n Otherwise it shall not be present.\nNOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the \n actual network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the \n transport header of the packets or it may be an identifier used between the application \n and the NFVI networking infrastructure to identify the network sub-interface of the trunk \n port in question. In the latter case the NFVI infrastructure will map this local segmentationId \n to whatever segmentationId is actually used by the NFVI’s transport technology.\n",
"type": "object",
"anyOf": [
{
@@ -982,13 +1626,30 @@
}
},
"subnetId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\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"
+ }
+ }
}
}
}
@@ -997,6 +1658,18 @@
"description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
"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"
+ },
+ "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 5 and 6. 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 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 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"
@@ -1004,10 +1677,6 @@
}
}
},
- "parentCpId": {
- "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 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"
@@ -1038,7 +1707,7 @@
"networkResource": {
"required": ["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",
+ "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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
@@ -1049,11 +1718,33 @@
"type": "string"
},
"resourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
"type": "string"
},
"vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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"
}
}
@@ -1070,7 +1761,7 @@
"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": {
- "description": "This type represents a link port of an internal VL of a VNF. It shall comply with the provisions defined in table 5.5.3.8 1.\nNOTE 1: Either cpInstanceId with cpInstanceType set to \"EXT_CP\" or any combination of cpInstanceId\n with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId (i.e. one or both of them) shall be \n present for a VnfLinkPortInfo. In case both cpInstanceId with cpInstanceType set to \"VNFC_CP\" \n and vipCpInstanceId are present, the two different CP instances share the linkport.\nNOTE 2: Annex A.4 of ETSI GS NFV-IFA 007 provides examples for configurations where both vipCpInstanceId\n and vnfcCpInstanceId are present (UC#5 and UC#5-b), only vnfcCpInstanceId is present (UC#2), or \n only vipCpInstanceId is present (UC6 and UC#6-b).\nNOTE 3: The value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\"\n attribute.\n",
+ "description": "This type represents a link port of an internal VL of a VNF.\nNOTE 1: Either cpInstanceId with cpInstanceType set to \"EXT_CP\" or any combination of cpInstanceId\n with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId (i.e. one or both of them) shall be \n present for a VnfLinkPortInfo. In case both cpInstanceId with cpInstanceType set to \"VNFC_CP\" \n and vipCpInstanceId are present, the two different CP instances share the linkport.\nNOTE 2: Annex A.4 of ETSI GS NFV-IFA 007 provides examples for configurations where both vipCpInstanceId\n and vnfcCpInstanceId are present (UC#5 and UC#5-b), only vnfcCpInstanceId is present (UC#2), or \n only vipCpInstanceId is present (UC6 and UC#6-b).\nNOTE 3: The value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\"\n attribute.\n",
"type": "object",
"required": ["id", "resourceHandle"],
"properties": {
@@ -1081,7 +1772,7 @@
"resourceHandle": {
"required": ["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",
+ "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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
@@ -1092,11 +1783,33 @@
"type": "string"
},
"resourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
"type": "string"
},
"vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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"
}
}
@@ -1115,7 +1828,7 @@
"type": "string"
},
"trunkResourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
"type": "string"
}
}
@@ -1151,7 +1864,7 @@
"storageResource": {
"required": ["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",
+ "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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
@@ -1162,11 +1875,33 @@
"type": "string"
},
"resourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
"type": "string"
},
"vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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"
}
}
@@ -1185,6 +1920,63 @@
}
}
}
+ },
+ "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. Within the CISM, an MCIO controller monitors the actual state of an MCIO representing the set of VNFC instances realized by one or a set of OS containers and compare it to the desired state as specified in the respective declarative descriptor. It triggers actions toward the CIS to align the actual to the desired state. Monitoring the actual state includes monitoring the number of MCIO instances available at any specific point in time. In addition, an MCIO controller maintains properties and runtime information on the MCIO instances which have been created based on the same VDU. The McioInfo data structure provides the runtime information on the MCIOs obtained from the MCIO controller.\nNOTE: There are different types of MCIOs. The set of VNFC instances based on the same VDU is represented \n by one MCIO, e.g. of type Deployment. Each individual VNFC instance is represented by another type \n of MCIO, e.g. a POD.\n\nRuntime information of the set of OS containers realizing an individual VNFC instance is not part of the McioInfo data structure; such runtime information is provided in the ResourceHandle data structure referenced from the VnfcResourceInfo. The McioInfo does not provide runtime information of a constituent VNFC instance created based on a specific VDU.\nNOTE 1: The type of MCIO as specified in the declarative descriptor of the MCIO, and that can be read from \n the CISM. EXAMPLE: In case of MCIOs managed by Kubernetes®, the type of MCIO corresponds to the \n “kind†property of the declarative descriptor.\nNOTE 2: If the attribute additionalInfo is present, it may contain runtime information on the actual and \n desired state of the MCIO(s). \nNOTE 3: When the container infrastructure service is a Kubernetes® instance, the mcioId is the combined \n values from the kind and name fields of the Kubernetes resource object, separated by a slash. \n Example: \"Deployment/abcd\". \nNOTE 4: When the container infrastructure service is a Kubernetes® instance, the mcioName is the name \n field of the resource object. \n",
+ "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": "An identifier that is unique within a VNF descriptor.\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 5.5.4.9. Additional values are also permitted. See note 1.\n",
+ "type": "string",
+ "enum": ["Deployment", "Statefulset"]
+ },
+ "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 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/SOL003/VNFLifecycleOperationGranting-API/ApiVersion.robot b/SOL003/VNFLifecycleOperationGranting-API/ApiVersion.robot
index 21f2b1280b02675454988fa9e2e6e617c04d0e01..2ce93d54b60756b8078d5f82550759bd05955ab5 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] v3.5.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.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 d5a158b674a125b14cd01d03a1e8aa54a20036eb..59bfb2b27280951c7d4f05ff2e48141ccbd68e22 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] v3.6.1
+ ... Reference: Clause 9.4.2.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.2.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.2.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -72,11 +72,11 @@ GET Grants - Method not implemented
Check HTTP Response Status Code Is 405
PUT Grants - Method not implemented
- [Documentation] Test ID: 7.3.2.1.5
+ [Documentation] Test ID: 7.3.2.1.5
... 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] v3.6.1
+ ... Reference: Clause 9.4.2.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.2.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -100,13 +100,55 @@ 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] v3.6.1
+ ... Reference: Clause 9.4.2.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: resources are not deleted
Delete Grants
Check HTTP Response Status Code Is 405
-
+
+Requests a grant for a particular VNF lifecycle operation - Synchronous mode using instantiationLevelId for Target size
+ [Documentation] Test ID: 7.3.2.1.8
+ ... 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
+ ... 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.
+ Send Request Grant Request in Synchronous mode with attribute instantiationLevelId
+ Check HTTP Response Status Code Is 201
+ Check Operation Occurrence Id existence
+ Check HTTP Response Body Json Schema Is grant
+
+Requests a grant for a particular VNF lifecycle operation - Synchronous mode using targetScaleLevelInfo for Target size
+ [Documentation] Test ID: 7.3.2.1.9
+ ... 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
+ ... 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.
+ Send Request Grant Request in Synchronous mode with attribute targetScaleLevelInfo
+ Check HTTP Response Status Code Is 201
+ Check Operation Occurrence Id existence
+ Check HTTP Response Body Json Schema Is grant
+
+Requests a grant for a particular VNF lifecycle operation - Synchronous mode using attribute addResources for Target size
+ [Documentation] Test ID: 7.3.2.1.10
+ ... 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
+ ... 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.
+ Send Request Grant Request in Synchronous mode with attribute addResources
+ Check HTTP Response Status Code Is 201
+ Check Operation Occurrence Id existence
+ Check HTTP Response Body Json Schema Is grant
+
*** Keywords ***
Wait for individual grant successful notification
Wait Until Keyword Succeeds ${retry} ${polling} Get an individual grant - Successful
\ No newline at end of file
diff --git a/SOL003/VNFLifecycleOperationGranting-API/IndividualGrant.robot b/SOL003/VNFLifecycleOperationGranting-API/IndividualGrant.robot
index b3f12afa710bc2640783b12bda5ae47e78cd3d67..33a06584d049f6093eaaeca89e27f4c6546f7dce 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] v3.6.1
+ ... Reference: Clause 9.4.2.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.3.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.3.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.3.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFLifecycleOperationGranting-API/VNFLifecycleOperationGrantingKeywords.robot b/SOL003/VNFLifecycleOperationGranting-API/VNFLifecycleOperationGrantingKeywords.robot
index bcc612f9f7733757352ef0fd23853a79af1c54a6..ab5b2fd723a1e1bc7f1507a3edecb13ad132a378 100644
--- a/SOL003/VNFLifecycleOperationGranting-API/VNFLifecycleOperationGrantingKeywords.robot
+++ b/SOL003/VNFLifecycleOperationGranting-API/VNFLifecycleOperationGrantingKeywords.robot
@@ -26,6 +26,45 @@ Send Request Grant Request in Synchronous mode
Post ${apiRoot}/${apiName}/${apiMajorVersion}/grants ${body}
${body}= Output response
Set Suite Variable ${response} ${body}
+
+Send Request Grant Request in Synchronous mode with attribute instantiationLevelId
+ Log Request a new Grant for a VNF LCM operation by POST to ${apiRoot}/${apiName}/${apiMajorVersion}/grants
+ Pass Execution If ${SYNC_MODE} == 0 The Granting process is asynchronous mode. Skipping the test
+ Set Headers {"Accept": "${ACCEPT}"}
+ Set Headers {"Content-Type": "${CONTENT_TYPE}"}
+ Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"${AUTHORIZATION_HEADER}":"${AUTHORIZATION_TOKEN}"}
+ Run Keyword If ${check_descriptors} == 1 PARSE the Descriptor File
+ ${template}= Get File jsons/grantRequestWithAttributeInstantiationLevelId.json
+ ${body}= Format String ${template} vnfInstanceId=${vnfInstanceId} vnfLcmOpOccId=${vnfLcmOpOccId} vnfdId=${Descriptor_ID} flavourId=${Flavour_ID} instantiationLevelId=${instantiationLevelId}
+ Post ${apiRoot}/${apiName}/${apiMajorVersion}/grants ${body}
+ ${body}= Output response
+ Set Suite Variable ${response} ${body}
+
+Send Request Grant Request in Synchronous mode with attribute targetScaleLevelInfo
+ Log Request a new Grant for a VNF LCM operation by POST to ${apiRoot}/${apiName}/${apiMajorVersion}/grants
+ Pass Execution If ${SYNC_MODE} == 0 The Granting process is asynchronous mode. Skipping the test
+ Set Headers {"Accept": "${ACCEPT}"}
+ Set Headers {"Content-Type": "${CONTENT_TYPE}"}
+ Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"${AUTHORIZATION_HEADER}":"${AUTHORIZATION_TOKEN}"}
+ Run Keyword If ${check_descriptors} == 1 PARSE the Descriptor File
+ ${template}= Get File jsons/grantRequestWithAttributeTargetScaleLevelInfo.json
+ ${body}= Format String ${template} vnfInstanceId=${vnfInstanceId} vnfLcmOpOccId=${vnfLcmOpOccId} vnfdId=${Descriptor_ID} flavourId=${Flavour_ID} aspectId=${scaleAspectId}
+ Post ${apiRoot}/${apiName}/${apiMajorVersion}/grants ${body}
+ ${body}= Output response
+ Set Suite Variable ${response} ${body}
+
+Send Request Grant Request in Synchronous mode with attribute addResources
+ Log Request a new Grant for a VNF LCM operation by POST to ${apiRoot}/${apiName}/${apiMajorVersion}/grants
+ Pass Execution If ${SYNC_MODE} == 0 The Granting process is asynchronous mode. Skipping the test
+ Set Headers {"Accept": "${ACCEPT}"}
+ Set Headers {"Content-Type": "${CONTENT_TYPE}"}
+ Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"${AUTHORIZATION_HEADER}":"${AUTHORIZATION_TOKEN}"}
+ Run Keyword If ${check_descriptors} == 1 PARSE the Descriptor File
+ ${template}= Get File jsons/grantRequestWithAttributeAddResources.json
+ ${body}= Format String ${template} vnfInstanceId=${vnfInstanceId} vnfLcmOpOccId=${vnfLcmOpOccId} vnfdId=${Descriptor_ID} flavourId=${Flavour_ID}
+ Post ${apiRoot}/${apiName}/${apiMajorVersion}/grants ${body}
+ ${body}= Output response
+ Set Suite Variable ${response} ${body}
Send Request Grant Request in Asynchronous mode
Log Request a new Grant for a VNF LCM operation by POST to ${apiRoot}/${apiName}/${apiMajorVersion}/grants
diff --git a/SOL003/VNFLifecycleOperationGranting-API/environment/variables.txt b/SOL003/VNFLifecycleOperationGranting-API/environment/variables.txt
index 6f09a3ad38268ae42af5fc1c2e4c2e624b5d8fca..ec3012e38ae2816d0830f42ed7379d2b66d6c164 100644
--- a/SOL003/VNFLifecycleOperationGranting-API/environment/variables.txt
+++ b/SOL003/VNFLifecycleOperationGranting-API/environment/variables.txt
@@ -24,6 +24,7 @@ ${VNFM_SCHEMA} https
${subscriptionId} 6fc3539c-e602-4afa-8e13-962fb5a7d81f
${vnfInstanceId} myVnfInstanceId
${vnfLcmOpOccId} myLcmOccId
+${instantiationLevelId}
${descriptorType} SOL001
${check_descriptors} 1
@@ -36,6 +37,8 @@ ${VDU_IDs}
${externalCP_IDs}
${Compute_IDs}
+${scaleAspectId}
+
${Descriptor_ID}
${Provider}
${Product_Name}
diff --git a/SOL003/VNFLifecycleOperationGranting-API/jsons/grantRequestWithAttributeAddResources.json b/SOL003/VNFLifecycleOperationGranting-API/jsons/grantRequestWithAttributeAddResources.json
new file mode 100644
index 0000000000000000000000000000000000000000..e3ac3d22b32ea229bdd15420eed5f7900f8f2d5a
--- /dev/null
+++ b/SOL003/VNFLifecycleOperationGranting-API/jsons/grantRequestWithAttributeAddResources.json
@@ -0,0 +1,23 @@
+{{
+ "vnfInstanceId": "{vnfInstanceId}",
+ "vnfLcmOpOccId": "{vnfLcmOpOccId}",
+ "vnfdId": "{vnfdId}",
+ "flavourId": "{flavourId}",
+ "operation": "INSTANTIATE",
+ "isAutomaticInvocation": true,
+ "addResources": [
+ {
+ "id": "",
+ "type": "",
+ "resourceTemplateId": []
+ }
+ ],
+ "_links": {{
+ "vnfLcmOpOcc": {{
+ "href": "string"
+ }},
+ "vnfInstance": {{
+ "href": "string"
+ }}
+ }}
+ }}
\ No newline at end of file
diff --git a/SOL003/VNFLifecycleOperationGranting-API/jsons/grantRequestWithAttributeInstantiationLevelId.json b/SOL003/VNFLifecycleOperationGranting-API/jsons/grantRequestWithAttributeInstantiationLevelId.json
new file mode 100644
index 0000000000000000000000000000000000000000..a8cff7e62b49b6044bb3c301bec7685a6d17f761
--- /dev/null
+++ b/SOL003/VNFLifecycleOperationGranting-API/jsons/grantRequestWithAttributeInstantiationLevelId.json
@@ -0,0 +1,17 @@
+{{
+ "vnfInstanceId": "{vnfInstanceId}",
+ "vnfLcmOpOccId": "{vnfLcmOpOccId}",
+ "vnfdId": "{vnfdId}",
+ "flavourId": "{flavourId}",
+ "operation": "INSTANTIATE",
+ "isAutomaticInvocation": true,
+ "instantiationLevelId": "{instantiationLevelId}",
+ "_links": {{
+ "vnfLcmOpOcc": {{
+ "href": "string"
+ }},
+ "vnfInstance": {{
+ "href": "string"
+ }}
+ }}
+ }}
\ No newline at end of file
diff --git a/SOL003/VNFLifecycleOperationGranting-API/jsons/grantRequestWithAttributeTargetScaleLevelInfo.json b/SOL003/VNFLifecycleOperationGranting-API/jsons/grantRequestWithAttributeTargetScaleLevelInfo.json
new file mode 100644
index 0000000000000000000000000000000000000000..21ed58a0ffbd3d33bf9b641ad3c5b854f9015990
--- /dev/null
+++ b/SOL003/VNFLifecycleOperationGranting-API/jsons/grantRequestWithAttributeTargetScaleLevelInfo.json
@@ -0,0 +1,22 @@
+{{
+ "vnfInstanceId": "{vnfInstanceId}",
+ "vnfLcmOpOccId": "{vnfLcmOpOccId}",
+ "vnfdId": "{vnfdId}",
+ "flavourId": "{flavourId}",
+ "operation": "INSTANTIATE",
+ "isAutomaticInvocation": true,
+ "targetScaleLevelInfo": [
+ {
+ "aspectId": "{aspectId}",
+ "scaleLevel": 2
+ }
+ ],
+ "_links": {{
+ "vnfLcmOpOcc": {{
+ "href": "string"
+ }},
+ "vnfInstance": {{
+ "href": "string"
+ }}
+ }}
+ }}
\ No newline at end of file
diff --git a/SOL003/VNFLifecycleOperationGranting-API/schemas/grant.schema.json b/SOL003/VNFLifecycleOperationGranting-API/schemas/grant.schema.json
index 89f70ebfd046e8bd315543297cbb29b93c5c3a70..17941f08344ef6a88c726c453ef44b29eb70210f 100644
--- a/SOL003/VNFLifecycleOperationGranting-API/schemas/grant.schema.json
+++ b/SOL003/VNFLifecycleOperationGranting-API/schemas/grant.schema.json
@@ -1,672 +1,1025 @@
{
- "description": "This type represents a grant.\nNOTE 1: This interface allows to signal the use of multiple VIMs per VNF. The specification\n for managing the VNF internal VL requirements across multiple VIMs is supported via\n \"externally-managed internal VLs\" and \"multi-site connectivity services\".\nNOTE 2: Void. NOTE 3: The Grant response allows the NFVO to pass to the VNFM VIM assets related to the VNF \n package that is identified in the corresponding Grant request. Because only the operations\n InstantiateVnf, ChangeCurrentVnfPkg and the update of the vnfdId by PATCH can imply changes\n in the set of VIM assets, the NFVO shall not change this set in any other case. To signal the\n set of VIM assets, the following applies:\n a)\tIf the current LCM operation is InstantiateVnf, the NFVO shall send in the Grant response\n the full set of VIM assets related to the VNF package defined by the vnfdId in the related\n Grant request.\n b)\tIf the current LCM operation is ChangeCurrentVnfPkg, the NFVO shall send in the\n Grant response the full set of VIM assets related to the VNF package defined by the destVnfdId\n in the related Grant request.\n c)\tFor any other operation: If the set of VIM assets has changed since the end of the previous\n granted operation because a PATCH operation has changed the vnfdId between the previous granted\n operation and the operation to which the current granting exchange relates, the NFVO shall send\n in the Grant response the full set of VIM assets related to the VNF package defined by the vnfdId\n in the related Grant request. Otherwise, the NFVO shall either send in the Grant response the full\n set of VIM assets related to the VNF package defined by the vnfdId in the related Grant request, or\n shall not send any VIM assets at all.\n During each LCM operation occurrence other than a \"ChangeCurrentVnfPkg\" operation,\n the VIM assets that relate to the VNF package identified by the current value of\n the vnfdId attribute in the \"VnfInstance\" structure shall be used by the\n VNFM for newly created resources and updated resources.\nNOTE 4: The indication of externally-managed internal VLs is needed in case networks have been\n pre-configured for use with certain VNFs, for instance to ensure that these networks have\n certain properties such as security or acceleration features, or to address particular network\n topologies (e.g., multi-site connectivity). The present document assumes that externally-managed\n internal VLs are managed by the NFVO and created towards the VIM and WIM.\nNOTE 5: For any VNF lifecycle management operation request that allows to pass \"extVirtualLinks\" and/or\n \"extManagedVirtualLinks\" parameters, such as InstantiateVnf, ChangeVnfFlavour, ChangeExtVnfConnectivity or\n ChangeCurrentVnfPackage, the NFVO may provide the \"extVirtualLinks\" and/or \"extManagedVirtualLinks\" attributes\n in the Grant to override the values passed in these parameters previously in the associated VNF lifecycle\n management request, if the lifecycle management request has originated from the NFVO itself. The NFVO shall\n not provide the \"extVirtualLinks\" and/or \"extManagedVirtualLinks\" attributes in the Grant in case the LCM\n request did not originate from the NFVO itself or the granted LCM operation request does not allow to pass\n these parameters.\nNOTE 6: The NFVO shall set the value of the attribute by copying the value from the associated \n GrantRequest.\nNOTE 7: In case of granting an InstantiateVnf request that has originated from the NFVO and that \n did not contain the \"extVirtualLinks\" attribute, this attribute shall be set by the NFVO. \n Further in case of granting an InstantiateVnf request that has originated from the NFVO \n and that did not contain the \"extManagedVirtualLinks\" attribute, this attribute shall be \n set by the NFVO if there is the need to provide information about externally-managed virtual \n links.\nNOTE 8: The resulting \"extVirtualLinks\" or \"extManagedVirtualLinks\" information is calculated as follows: \n In a first step, the information passed in the related LCM operation is applied to the baseline\n information known from earlier LCM operation executions. In a second step, the information passed\n in the Grant is applied to the information resulting from the first step.\n",
- "type": "object",
- "required": ["id", "vnfInstanceId", "vnfLcmOpOccId", "_links"],
- "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",
- "type": "string"
- },
- "vnfLcmOpOccId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vimConnectionInfo": {
- "description": "Provides information regarding VIM connections that are approved to be used by the VNFM to allocate resources and provides parameters of these VIM connections. \nThe VNFM shall update the \"vimConnectionInfo\" attribute of the \"VnfInstance\" structure by adding unknown entries received in this attribute. \nThis attribute is not intended for the modification of VimConnectionInfo entries passed earlier; for that, the VnfInfoModificationRequest structure shall be used.\nThis attribute shall only be supported when VNF-related Resource Management in direct mode is applicable. In direct mode, this parameter shall be absent if the VIM 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 for managing the resources of a VNF instance. * 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 is provided through a secure connection over\n HTTP Secure (HTTP over SSL/TLS), and the connection might also be established through a VPN\n (for example TLS-based VPN tunnelling) for site-to-site connection, the \"accessInfo\" JSON data\n structure, and the sensitive data related information (\"username\"/\"password\" as required properties\n for authentication purpose), will be transmitted as plain text through a TLS tunnel without additional\n encoding/encryption before transmitting it, making the sensitive data visible to the endpoint.\n The base64 encoded certificates are only used by the VNFM to verify the authenticity of the\n interface endpoint of the VIM.\n",
- "type": "object",
- "required": ["vimType"],
- "properties": {
- "vimId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vimType": {
- "description": "Discriminator for the different types of the VIM information. The value of this attribute determines the structure of the \"interfaceInfo\" and \"accessInfo\" attributes, based on the type of the VIM. The set of permitted values is expected to change over time as new types or versions of VIMs become available. The ETSI NFV registry of VIM-related information provides access to information about VimConnectionInfo definitions for various VIM types. The structure of the registry is defined in Annex C of SOL003.\n",
- "type": "string"
- },
- "interfaceInfo": {
- "description": "This 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"
- },
- "accessInfo": {
- "description": "This 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"
- },
- "extra": {
- "description": "This 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"
- }
- }
- }
- },
- "zones": {
- "description": "Identifies resource zones where the resources are approved to be allocated by the VNFM.\n",
- "type": "array",
- "items": {
- "description": "This type provides information regarding a resource zone.\n",
- "type": "object",
- "required": ["id", "zoneId"],
- "properties": {
- "id": {
- "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\n",
- "type": "string"
- },
- "zoneId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vimConnectionId": {
- "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"
- }
- }
- }
- },
- "zoneGroups": {
- "description": "Information about groups of resource zones that are related and that the NFVO has chosen to fulfil a zoneGroup constraint in the GrantVnfLifecycleOperation request. This information confirms that the NFVO has honoured the zoneGroup constraints that were passed as part of \"placementConstraints\" in the GrantRequest.\n",
- "type": "array",
- "items": {
- "description": "This type provides information regarding a resource zone group. A resource zone group is a group of one or more related resource zones which can be used in resource placement constraints. To fulfil such constraint, the NFVO may decide to place a resource into any zone that belongs to a particular group. NOTE: A resource zone group can be used to support overflow from one resource zone into another, in case a particular deployment supports only non-elastic resource zones.\n",
- "type": "object",
- "required": ["zoneId"],
- "properties": {
- "zoneId": {
- "description": "References of identifiers of \"ZoneInfo\" structures, each of which provides information about a resource zone that belongs to this group.\n",
- "type": "array",
- "items": {
- "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- }
- }
- },
- "addResources": {
- "description": "List of resources that are approved to be added, with one entry per resource. Shall be set when resources are approved to be added and shall contain the same set of resources requested to be added in the related GrantRequest.\n",
- "type": "array",
- "items": {
- "description": "This type contains information about a Compute, storage or network resource whose addition/update/deletion was granted.\n",
- "type": "object",
- "required": ["resourceDefinitionId"],
- "properties": {
- "resourceDefinitionId": {
- "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\n",
- "type": "string"
- },
- "reservationId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimConnectionId": {
- "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"
- },
- "zoneId": {
- "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\n",
- "type": "string"
- },
- "resourceGroupId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- }
- }
- }
- },
- "tempResources": {
- "description": "List of resources that are approved to be temporarily instantiated during the runtime of the lifecycle operation, with one entry per resource. Shall be set when resources are approved to be temporarily instantiated and shall contain the same set of resources requested to be temporarily instantiated in the related GrantRequest.\n",
- "type": "array",
- "items": {
- "description": "This type contains information about a Compute, storage or network resource whose addition/update/deletion was granted.\n",
- "type": "object",
- "required": ["resourceDefinitionId"],
- "properties": {
- "resourceDefinitionId": {
- "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\n",
- "type": "string"
- },
- "reservationId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimConnectionId": {
- "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"
- },
- "zoneId": {
- "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\n",
- "type": "string"
- },
- "resourceGroupId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- }
- }
- }
- },
- "removeResources": {
- "description": "List of resources that are approved to be removed, with one entry per resource. Shall be set when resources are approved to be removed and shall contain the same set of resources requested to be removed in the related GrantRequest.\n",
- "type": "array",
- "items": {
- "description": "This type contains information about a Compute, storage or network resource whose addition/update/deletion was granted.\n",
- "type": "object",
- "required": ["resourceDefinitionId"],
- "properties": {
- "resourceDefinitionId": {
- "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\n",
- "type": "string"
- },
- "reservationId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimConnectionId": {
- "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"
- },
- "zoneId": {
- "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\n",
- "type": "string"
- },
- "resourceGroupId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- }
- }
- }
- },
- "updateResources": {
- "description": "List of resources that are approved to be modified, with one entry per resource. Shall be set when resources are approved to be updated and shall contain the same set of resources requested to be updated in the related GrantRequest.\n",
- "type": "array",
- "items": {
- "description": "This type contains information about a Compute, storage or network resource whose addition/update/deletion was granted.\n",
- "type": "object",
- "required": ["resourceDefinitionId"],
- "properties": {
- "resourceDefinitionId": {
- "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\n",
- "type": "string"
- },
- "reservationId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimConnectionId": {
- "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"
- },
- "zoneId": {
- "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\n",
- "type": "string"
- },
- "resourceGroupId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- }
- }
- }
- },
- "vimAssets": {
- "description": "Information about assets for the VNF that are managed by the NFVO in the VIM, such as software images and virtualised compute resource flavours. See note 3.\n",
- "type": "object",
- "properties": {
- "computeResourceFlavours": {
- "description": "Mappings between virtual compute descriptors defined in the VNFD and compute resource flavours managed in the VIM.\n",
- "type": "array",
- "items": {
- "description": "If the VIM requires the use of virtual compute resource flavours during compute resource instantiation, it is assumed that such flavours are selected or created by the NFVO based on the information in the virtual compute descriptor defined in the VNFD. This type defines the mapping between a virtual compute descriptor in the VNFD and the corresponding compute resource flavour managed by the NFVO in the VIM.\n",
- "type": "object",
- "required": ["vnfdVirtualComputeDescId", "vimFlavourId"],
- "properties": {
- "vimConnectionId": {
- "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"
- },
- "vnfdVirtualComputeDescId": {
- "description": "An identifier that is unique within a VNF descriptor.\n",
- "type": "string"
- },
- "vimFlavourId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- }
- }
- }
- },
- "softwareImages": {
- "description": "Mappings between software images defined in the VNFD and software images managed in the VIM.\n",
- "type": "array",
- "items": {
- "description": "This type contains a mapping between a software image definition the VNFD and the corresponding software image managed by the NFVO in the VIM which is needed during compute resource instantiation.\n",
- "type": "object",
- "required": ["vnfdSoftwareImageId", "vimSoftwareImageId"],
- "properties": {
- "vimConnectionId": {
- "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"
- },
- "vnfdSoftwareImageId": {
- "description": "An identifier that is unique within a VNF descriptor.\n",
- "type": "string"
- },
- "vimSoftwareImageId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- }
- }
- }
- },
- "snapshotResources": {
- "description": "Mappings between snapshot resources defined in the VNF snapshot package and resources managed in the VIM.\n",
- "type": "array",
- "items": {
- "description": "This type contains a mapping between a snapshot resource definition related to a VNF snapshot and the corresponding resource managed by the NFVO in the VIM which is needed during the revert to VNF snapshot operation.\n",
- "type": "object",
- "required": [
- "vnfSnapshotId",
- "vnfcSnapshotId",
- "vimSnapshotResourceId"
- ],
- "properties": {
- "vimConnectionId": {
- "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"
- },
- "vnfSnapshotId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfcSnapshotId": {
- "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\n",
- "type": "string"
- },
- "storageSnapshotId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "vimSnapshotResourceId": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- }
- }
- }
- }
- }
- },
- "extVirtualLinks": {
- "description": "Information about external VLs to connect the VNF to. See notes 5, 7 and 8. If this attribute is present according to note 5 or note 7, it need not contain those entries that are unchanged compared to the entries that were passed in the LCM operation which is related to this granting exchange.\n",
- "type": "array",
- "items": {
- "description": "This type represents an external VL. * NOTE:\tA link port is not needed for an external CP instance that exposes a VIP CP in the following cases:\n 1\tFor a VIP CP directly exposed as extCP:\n 1.1\tNo dedicated IP address is allocated as VIP address, as indicated in the VNFD.\n 1.2\tA dedicated IP addresss is allocated as VIP address, but the NFVO indicates that no port\n is needed (createExtLinkPort in VnfExtCpconfig set to false).\n 2\tFor a VIP CP exposed as extCP via a floating IP address:\n 2.1\tNo dedicated IP address is allocated as VIP address, as indicated in the VNFD, and the VNFC\n CP associated to the VIP CP is also exposed via a floating IP addresss.\n",
- "type": "object",
- "required": ["id", "resourceId", "extCps"],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "extCps": {
- "description": "External CPs of the VNF to be connected to this external VL. Entries in the list of external CP data that are unchanged need not be supplied if the ExtVirtualLinkData structure is part of a request or response that modifies the external connectivity.\n",
- "type": "array",
- "items": {
- "description": "This type represents configuration information for external CPs created. * NOTE 1: \tIn case this identifier refers to a CPD with trunking enabled, the external CP instances created\n from this CPD will represent ports in a trunk.\n* NOTE 2: \tWithin one VNF instance, all VNFC instances created from a particular VDU have the same external\n connectivity. Thus, given a particular value of the \"cpdId\" attribute, there shall be one\n \"cpConfig\" entry for each VNFC instance that has been or can be created from a VDU which includes\n a CPD identified by the \"cpdId\" attribute. If the cpConfig represents a subport in a trunk,\n all \"cpConfig\" entries in this list shall have the same segmentationId, which means they are\n connected to the same set of external VLs via the trunk.\n* NOTE 3: \tThe map entry value shall be set to \"null\" in order to delete a \"VnfExtCpConfig\" entry identified\n by a particular key value from the map, i.e. for the disconnection of an existing external\n CP instance addressed by cpInstanceId in the deleted map entry from a particular external\n virtual link, and deletion of that instance in case it represents a subport. Deleting the\n last key from the map removes the affected instance of the \"VnfExtCpData\" structure from\n its parent data structure.\n* NOTE 4: If, as defined by the input parameters of a \"ChangeVnfFlavour\", \"ChangeExtVnfConnectivity\" or \n \"ChangeCurrentVnfPkg\" operation or as part of the Grant response for any of these operations, a \n cpConfig map entry identified by a particular map key value is moved into another \"ExtVirtualLinkData\"\n or \"VnfExtCpData\" structure, this particular cpConfig map entry may be used by an external CP instance\n different than the one that has used it before the operation, or by no external CP instance at all.\n Renaming a CPD identifier during the \"changeCurrentVnfPkg\" operation does not count as moving the\n related \"cpConfig\" map entries to a new \"extCpData\" structure.\n",
- "type": "object",
- "required": ["cpdId"],
- "properties": {
- "cpdId": {
- "description": "An identifier that is unique within a VNF descriptor.\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). See notes 2, 3 and 4.\n",
- "type": "object",
- "additionalProperties": {
- "description": "This type represents an externally provided link port or network address information per instance of an external connection point. In case a link port is provided, the VNFM shall use that link port when connecting the external CP to the external VL. In a link port is not provided, the VNFM shall create a link port on the external VL, and use that link port to connect the external CP to the external VL. * NOTE: The following conditions apply to the attributes \"linkPortId\" and \"cpProtocolData\":\n 1) Void.\n 2) At least one of the \"linkPortId\" and \"cpProtocolData\" attributes shall be present for an external\n CP instance representing a subport that is to be created, or an external CP instance that is to be\n created by creating the corresponding VNFC or VNF instance during the current or a subsequent LCM\n operation, or for an existing external CP instance that is to be re-configured or added to a\n 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\n a pre created link port, and the VNFM can use means outside the scope of the present document to obtain\n the pre-configured address information for the connection point from the resource representing\n the link port.\n 5) If both \"cpProtocolData\" and \"linkportId\" are provided, the API consumer shall ensure that the\n cpProtocolData can be used with the pre-created link port referenced by \"linkPortId\".\n",
- "anyOf": [
- {
- "required": ["linkPortId"]
- },
- {
- "required": ["cpProtocolData"]
- }
- ],
- "type": "object",
- "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 to the VNFM the need to create a dedicated link port for the external CP. If set to True, the VNFM shall create a link port. If set to False, the VNFM shall not create a link port. 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 note.\n",
- "type": "array",
- "items": {
- "description": "This type represents network protocol data. * NOTE:\tThis attribute allows to signal the addition of further types of layer and protocol\n in future versions of the present document in a backwards-compatible way. In the current\n 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). See note.\n",
- "type": "string",
- "enum": ["IP_OVER_ETHERNET"]
- },
- "ipOverEthernet": {
- "description": "This type represents network address data for IP over Ethernet. * NOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. * NOTE 2:\tExactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present. * NOTE 3:\tIf the CP instance represents a subport in a trunk, segmentationId shall be present.\n Otherwise it shall not be present.\n* NOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the actual\n network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header\n of the packets or it may be an identifier used between the application and the NFVI networking\n infrastructure to identify the network sub-interface of the trunk port in question. In the latter\n case the NFVI infrastructure will map this local segmentationId to whatever segmentationId is\n actually used by the NFVIΓÇÖs transport technology.\n",
- "type": "object",
- "anyOf": [
- {
- "required": ["macAddress"]
- },
- {
- "required": ["ipAddresses"]
- }
- ],
- "oneOf": [
- {
- "required": ["fixedAddresses"]
- },
- {
- "required": ["numDynamicAddresses"]
- },
- {
- "required": ["ipAddressRange"]
- }
- ],
- "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: -\tVLAN: the subport uses VLAN as encapsulation type. -\tINHERIT: the subport gets its segmentation type from the network itΓÇÖs 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"],
- "properties": {
- "type": {
- "description": "The type of the IP addresses. Permitted values: IPV4, IPV6.\n",
- "type": "string",
- "enum": ["IPV4", "IPV6"]
- },
- "fixedAddresses": {
- "description": "Fixed addresses to assign (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"
- }
- },
- "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. 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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- },
- "extLinkPorts": {
- "description": "Externally provided link ports to be used to connect external connection points to this external VL. If this attribute is not present, the VNFM shall create the link ports on the external VL unless the extCp exposes a VIP CP and a link port is not needed for it based on the conditions defined below. See note.\n",
- "type": "array",
- "items": {
- "description": "This type represents an externally provided link port to be used to connect an external connection point to an external VL. * NOTE:\tThe 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": {
- "required": ["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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\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.\n",
- "type": "string"
- }
- }
- }
- }
- }
- }
- },
- "extManagedVirtualLinks": {
- "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": {
- "type": "object",
- "required": ["id", "vnfVirtualLinkDescId", "resourceId"],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfVirtualLinkDescId": {
- "description": "An identifier that is unique within a VNF descriptor.\n",
- "type": "string"
- },
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vnfLinkPort": {
- "description": "Externally provided link ports to be used to connect VNFC connection points to this externally-managed VL on this network resource. If this attribute is not present, the VNFM shall create the link ports on the externally-managed VL.\n",
- "type": "array",
- "items": {
- "description": "This type represents an externally provided link port to be used to connect a VNFC connection point to an exernally managed VL.\n",
- "type": "object",
- "required": ["vnfLinkPortId", "resourceHandle"],
- "properties": {
- "vnfLinkPortId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "resourceHandle": {
- "required": ["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",
- "properties": {
- "vimConnectionId": {
- "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 other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
- "type": "string"
- }
- }
- }
- }
- }
- },
- "extManagedMultisiteVirtualLinkId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- }
- }
- }
- },
- "additionalParams": {
- "description": "This 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"
- },
- "_links": {
- "description": "Links to resources related to this resource.\n",
- "type": "object",
- "required": ["self", "vnfLcmOpOcc", "vnfInstance"],
- "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"
- }
- }
- },
- "vnfLcmOpOcc": {
- "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"
- }
- }
- },
- "vnfInstance": {
- "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"
- }
- }
- }
- }
- }
- }
+ "description": "This type represents a grant.\nNOTE 1: This interface allows to signal the use of multiple VIMs per VNF. The specification\n for managing the VNF internal VL requirements across multiple VIMs is supported via\n \"externally-managed internal VLs\" and \"multi-site connectivity services\".\nNOTE 2: Void. NOTE 3: The Grant response allows the NFVO to pass to the VNFM VIM assets related to the VNF \n package that is identified in the corresponding Grant request. Because only the operations\n InstantiateVnf, ChangeCurrentVnfPkg and the update of the vnfdId by PATCH can imply changes\n in the set of VIM assets, the NFVO shall not change this set in any other case. To signal the\n set of VIM assets, the following applies:\n a)\tIf the current LCM operation is InstantiateVnf, the NFVO shall send in the Grant response\n the full set of VIM assets related to the VNF package defined by the vnfdId in the related\n Grant request.\n b)\tIf the current LCM operation is ChangeCurrentVnfPkg, the NFVO shall send in the\n Grant response the full set of VIM assets related to the VNF package defined by the destVnfdId\n in the related Grant request.\n c)\tFor any other operation: If the set of VIM assets has changed since the end of the previous\n granted operation because a PATCH operation has changed the vnfdId between the previous granted\n operation and the operation to which the current granting exchange relates, the NFVO shall send\n in the Grant response the full set of VIM assets related to the VNF package defined by the vnfdId\n in the related Grant request. Otherwise, the NFVO shall either send in the Grant response the full\n set of VIM assets related to the VNF package defined by the vnfdId in the related Grant request, or\n shall not send any VIM assets at all.\n During each LCM operation occurrence other than a \"ChangeCurrentVnfPkg\" operation,\n the VIM assets that relate to the VNF package identified by the current value of\n the vnfdId attribute in the \"VnfInstance\" structure shall be used by the\n VNFM for newly created resources and updated resources.\nNOTE 4: The indication of externally-managed internal VLs is needed in case networks have been\n pre-configured for use with certain VNFs, for instance to ensure that these networks have\n certain properties such as security or acceleration features, or to address particular network\n topologies (e.g., multi-site connectivity). The present document assumes that externally-managed\n internal VLs are managed by the NFVO and created towards the VIM and WIM.\nNOTE 5: For any VNF lifecycle management operation request that allows to pass \"extVirtualLinks\" and/or\n \"extManagedVirtualLinks\" parameters, such as InstantiateVnf, ChangeVnfFlavour, ChangeExtVnfConnectivity or\n ChangeCurrentVnfPackage, the NFVO may provide the \"extVirtualLinks\" and/or \"extManagedVirtualLinks\" attributes\n in the Grant to override the values passed in these parameters previously in the associated VNF lifecycle\n management request, if the lifecycle management request has originated from the NFVO itself. The NFVO shall\n not provide the \"extVirtualLinks\" and/or \"extManagedVirtualLinks\" attributes in the Grant in case the LCM\n request did not originate from the NFVO itself or the granted LCM operation request does not allow to pass\n these parameters.\nNOTE 6: The NFVO shall set the value of the attribute by copying the value from the associated \n GrantRequest.\nNOTE 7: In case of granting an InstantiateVnf request that has originated from the NFVO and that \n did not contain the \"extVirtualLinks\" attribute, this attribute shall be set by the NFVO. \n Further in case of granting an InstantiateVnf request that has originated from the NFVO \n and that did not contain the \"extManagedVirtualLinks\" attribute, this attribute shall be \n set by the NFVO if there is the need to provide information about externally-managed virtual \n links.\nNOTE 8: The resulting \"extVirtualLinks\" or \"extManagedVirtualLinks\" information is calculated as follows: \n In a first step, the information passed in the related LCM operation is applied to the baseline\n information known from earlier LCM operation executions. In a second step, the information passed\n in the Grant is applied to the information resulting from the first step.\n",
+ "type": "object",
+ "required": ["id", "vnfInstanceId", "vnfLcmOpOccId", "_links"],
+ "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",
+ "type": "string"
+ },
+ "vnfLcmOpOccId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vimConnectionInfo": {
+ "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",
+ "type": "object",
+ "required": ["vimType"],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vimType": {
+ "description": "Discriminator for the different types of the VIM information. The value of this attribute determines the structure of the \"interfaceInfo\" and \"accessInfo\" attributes, based on the type of the VIM., CISM, CIR or MCIOP repository. The set of permitted values is expected to change over time as new types or versions of VIMs become available. The ETSI NFV registry of VIM-related information [i.3] provides access to information about VimConnectionInfo definitions for various VIM, CISM, CIR or MCIOP repository types. The structure of the registry is defined in annex C.\n",
+ "type": "string"
+ },
+ "interfaceInfo": {
+ "description": "This 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"
+ },
+ "accessInfo": {
+ "description": "This 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"
+ },
+ "extra": {
+ "description": "This 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"
+ }
+ }
+ }
+ },
+ "cirConnectionInfo": {
+ "description": "Provides information regarding a CIR connection that is approved to be used by the VNFM to obtain information about OS container images. It shall be absent in case of rejection or if the CIR information was configured to the VNFM in another way or if the granted resources are not managed by a CISM, present 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",
+ "type": "object",
+ "required": ["vimType"],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vimType": {
+ "description": "Discriminator for the different types of the VIM information. The value of this attribute determines the structure of the \"interfaceInfo\" and \"accessInfo\" attributes, based on the type of the VIM., CISM, CIR or MCIOP repository. The set of permitted values is expected to change over time as new types or versions of VIMs become available. The ETSI NFV registry of VIM-related information [i.3] provides access to information about VimConnectionInfo definitions for various VIM, CISM, CIR or MCIOP repository types. The structure of the registry is defined in annex C.\n",
+ "type": "string"
+ },
+ "interfaceInfo": {
+ "description": "This 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"
+ },
+ "accessInfo": {
+ "description": "This 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"
+ },
+ "extra": {
+ "description": "This 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"
+ }
+ }
+ }
+ },
+ "mciopRepositoryInfo": {
+ "description": "Provides information regarding a MCIOP repository. It shall be absent in case of rejection or if the MCIOP repository information was configured to the VNFM in another way or if the granted resources are not managed by a CISM, present 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",
+ "type": "object",
+ "required": ["vimType"],
+ "properties": {
+ "vimId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vimType": {
+ "description": "Discriminator for the different types of the VIM information. The value of this attribute determines the structure of the \"interfaceInfo\" and \"accessInfo\" attributes, based on the type of the VIM., CISM, CIR or MCIOP repository. The set of permitted values is expected to change over time as new types or versions of VIMs become available. The ETSI NFV registry of VIM-related information [i.3] provides access to information about VimConnectionInfo definitions for various VIM, CISM, CIR or MCIOP repository types. The structure of the registry is defined in annex C.\n",
+ "type": "string"
+ },
+ "interfaceInfo": {
+ "description": "This 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"
+ },
+ "accessInfo": {
+ "description": "This 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"
+ },
+ "extra": {
+ "description": "This 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"
+ }
+ }
+ }
+ },
+ "zones": {
+ "description": "Identifies resource zones where the resources are approved to be allocated by the VNFM.\n",
+ "type": "array",
+ "items": {
+ "description": "This type provides information regarding a resource zone.\n",
+ "type": "object",
+ "required": ["id", "zoneId"],
+ "properties": {
+ "id": {
+ "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "zoneId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vimConnectionId": {
+ "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"
+ }
+ }
+ }
+ },
+ "zoneGroups": {
+ "description": "Information about groups of resource zones that are related and that the NFVO has chosen to fulfil a zoneGroup constraint in the GrantVnfLifecycleOperation request. This information confirms that the NFVO has honoured the zoneGroup constraints that were passed as part of \"placementConstraints\" in the GrantRequest.\n",
+ "type": "array",
+ "items": {
+ "description": "This type provides information regarding a resource zone group. A resource zone group is a group of one or more related resource zones which can be used in resource placement constraints. To fulfil such constraint, the NFVO may decide to place a resource into any zone that belongs to a particular group. NOTE: A resource zone group can be used to support overflow from one resource zone into another, in case a particular deployment supports only non-elastic resource zones.\n",
+ "type": "object",
+ "required": ["zoneId"],
+ "properties": {
+ "zoneId": {
+ "description": "References of identifiers of \"ZoneInfo\" structures, each of which provides information about a resource zone that belongs to this group.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\n",
+ "type": "string"
+ }
+ }
+ }
+ }
+ },
+ "addResources": {
+ "description": "List of resources that are approved to be added, with one entry per resource. Shall be set when resources are approved to be added and shall contain the same set of resources requested to be added in the related GrantRequest.\n",
+ "type": "array",
+ "items": {
+ "description": "This type contains information about a Compute, storage or network resource whose addition/update/deletion was granted.\n",
+ "type": "object",
+ "required": ["resourceDefinitionId"],
+ "properties": {
+ "resourceDefinitionId": {
+ "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "reservationId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "type": "string"
+ },
+ "vimConnectionId": {
+ "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"
+ },
+ "zoneId": {
+ "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "resourceGroupId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "type": "string"
+ },
+ "containerNamespace": {
+ "description": "A string defined in IETF RFC 8259.\n",
+ "type": "string"
+ },
+ "mcioConstraints": {
+ "description": "The constraint values to be assigned to MCIOs of a VNF with containerized components. The key in the key-value pair indicates the parameter name of the MCIO constraint in the MCIO declarative descriptor and shall be one of the possible enumeration values of the \"mcioConstraintsParams\" attribute as specified in clause 7.1.6.2.2 of ETSI GS NFV-IFA 011 [10]. The value in the keyvalue pair indicates the value to be assigned to the MCIO constraint. This attribute shall be present if the granted resources are managed by a CISM. The attribute shall be absent if the granted resources are not managed by a CISM.\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 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"
+ }
+ }
+ }
+ }
+ },
+ "tempResources": {
+ "description": "List of resources that are approved to be temporarily instantiated during the runtime of the lifecycle operation, with one entry per resource. Shall be set when resources are approved to be temporarily instantiated and shall contain the same set of resources requested to be temporarily instantiated in the related GrantRequest.\n",
+ "type": "array",
+ "items": {
+ "description": "This type contains information about a Compute, storage or network resource whose addition/update/deletion was granted.\n",
+ "type": "object",
+ "required": ["resourceDefinitionId"],
+ "properties": {
+ "resourceDefinitionId": {
+ "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "reservationId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "type": "string"
+ },
+ "vimConnectionId": {
+ "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"
+ },
+ "zoneId": {
+ "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "resourceGroupId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "type": "string"
+ },
+ "containerNamespace": {
+ "description": "A string defined in IETF RFC 8259.\n",
+ "type": "string"
+ },
+ "mcioConstraints": {
+ "description": "The constraint values to be assigned to MCIOs of a VNF with containerized components. The key in the key-value pair indicates the parameter name of the MCIO constraint in the MCIO declarative descriptor and shall be one of the possible enumeration values of the \"mcioConstraintsParams\" attribute as specified in clause 7.1.6.2.2 of ETSI GS NFV-IFA 011 [10]. The value in the keyvalue pair indicates the value to be assigned to the MCIO constraint. This attribute shall be present if the granted resources are managed by a CISM. The attribute shall be absent if the granted resources are not managed by a CISM.\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 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"
+ }
+ }
+ }
+ }
+ },
+ "removeResources": {
+ "description": "List of resources that are approved to be removed, with one entry per resource. Shall be set when resources are approved to be removed and shall contain the same set of resources requested to be removed in the related GrantRequest.\n",
+ "type": "array",
+ "items": {
+ "description": "This type contains information about a Compute, storage or network resource whose addition/update/deletion was granted.\n",
+ "type": "object",
+ "required": ["resourceDefinitionId"],
+ "properties": {
+ "resourceDefinitionId": {
+ "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "reservationId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "type": "string"
+ },
+ "vimConnectionId": {
+ "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"
+ },
+ "zoneId": {
+ "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "resourceGroupId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "type": "string"
+ },
+ "containerNamespace": {
+ "description": "A string defined in IETF RFC 8259.\n",
+ "type": "string"
+ },
+ "mcioConstraints": {
+ "description": "The constraint values to be assigned to MCIOs of a VNF with containerized components. The key in the key-value pair indicates the parameter name of the MCIO constraint in the MCIO declarative descriptor and shall be one of the possible enumeration values of the \"mcioConstraintsParams\" attribute as specified in clause 7.1.6.2.2 of ETSI GS NFV-IFA 011 [10]. The value in the keyvalue pair indicates the value to be assigned to the MCIO constraint. This attribute shall be present if the granted resources are managed by a CISM. The attribute shall be absent if the granted resources are not managed by a CISM.\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 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"
+ }
+ }
+ }
+ }
+ },
+ "updateResources": {
+ "description": "List of resources that are approved to be modified, with one entry per resource. Shall be set when resources are approved to be updated and shall contain the same set of resources requested to be updated in the related GrantRequest.\n",
+ "type": "array",
+ "items": {
+ "description": "This type contains information about a Compute, storage or network resource whose addition/update/deletion was granted.\n",
+ "type": "object",
+ "required": ["resourceDefinitionId"],
+ "properties": {
+ "resourceDefinitionId": {
+ "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "reservationId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "type": "string"
+ },
+ "vimConnectionId": {
+ "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"
+ },
+ "zoneId": {
+ "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "resourceGroupId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "type": "string"
+ },
+ "containerNamespace": {
+ "description": "A string defined in IETF RFC 8259.\n",
+ "type": "string"
+ },
+ "mcioConstraints": {
+ "description": "The constraint values to be assigned to MCIOs of a VNF with containerized components. The key in the key-value pair indicates the parameter name of the MCIO constraint in the MCIO declarative descriptor and shall be one of the possible enumeration values of the \"mcioConstraintsParams\" attribute as specified in clause 7.1.6.2.2 of ETSI GS NFV-IFA 011 [10]. The value in the keyvalue pair indicates the value to be assigned to the MCIO constraint. This attribute shall be present if the granted resources are managed by a CISM. The attribute shall be absent if the granted resources are not managed by a CISM.\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 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"
+ }
+ }
+ }
+ }
+ },
+ "vimAssets": {
+ "description": "Information about assets for the VNF that are defined in VNFD and managed by the NFVO in the VIM/NFVI, such as software images and virtualised compute resource flavours. See note 3.\n",
+ "type": "object",
+ "properties": {
+ "computeResourceFlavours": {
+ "description": "Mappings between virtual compute descriptors defined in the VNFD and compute resource flavours managed in the VIM.\n",
+ "type": "array",
+ "items": {
+ "description": "If the VIM requires the use of virtual compute resource flavours during compute resource instantiation, it is assumed that such flavours are selected or created by the NFVO based on the information in the virtual compute descriptor defined in the VNFD. This type defines the mapping between a virtual compute descriptor in the VNFD and the corresponding compute resource flavour managed by the NFVO in the VIM.\n",
+ "type": "object",
+ "required": ["vnfdVirtualComputeDescId", "vimFlavourId"],
+ "properties": {
+ "vimConnectionId": {
+ "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"
+ },
+ "vnfdVirtualComputeDescId": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "vimFlavourId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "softwareImages": {
+ "description": "Mappings between software images defined in the VNFD and software images managed in the VIM.\n",
+ "type": "array",
+ "items": {
+ "description": "This type contains a mapping between a software image definition the VNFD and the corresponding software image managed by the NFVO in the VIM or CIR which is needed during compute resource instantiation.\nNOTE: For an OS container image, the value of this attribute is a string concatenating the name and tag of the\n image in the CIR separated by a colon ':' with no spaces, e.g. “dbImage:001â€.\n",
+ "type": "object",
+ "required": ["vnfdSoftwareImageId", "vimSoftwareImageId"],
+ "properties": {
+ "vimConnectionId": {
+ "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"
+ },
+ "vnfdSoftwareImageId": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "vimSoftwareImageId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "snapshotResources": {
+ "description": "Mappings between snapshot resources defined in the VNF snapshot package and resources managed in the VIM.\n",
+ "type": "array",
+ "items": {
+ "description": "This type contains a mapping between a snapshot resource definition related to a VNF snapshot and the corresponding resource managed by the NFVO in the VIM which is needed during the revert to VNF snapshot operation.\n",
+ "type": "object",
+ "required": [
+ "vnfSnapshotId",
+ "vnfcSnapshotId",
+ "vimSnapshotResourceId"
+ ],
+ "properties": {
+ "vimConnectionId": {
+ "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"
+ },
+ "vnfSnapshotId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfcSnapshotId": {
+ "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "storageSnapshotId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "vimSnapshotResourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "storageAssets": {
+ "description": "Mappings between virtual storages defined in the VNFD and virtual storages managed in the NFVI.\n",
+ "type": "array",
+ "items": {
+ "description": "This type provides a mapping between a VirtualStorageDesc in the VNFD and the corresponding virtual storage managed by the NFVO in the NFVI.\n",
+ "type": "object",
+ "required": ["virtualStorageDescId", "storageClassName"],
+ "properties": {
+ "vimConnectionId": {
+ "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"
+ },
+ "virtualStorageDescId": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "storageClassName": {
+ "description": "A string defined in IETF RFC 8259.\n",
+ "type": "string"
+ }
+ }
+ }
+ }
+ }
+ },
+ "extVirtualLinks": {
+ "description": "Information about external VLs to connect the VNF to. See notes 5, 7 and 8. If this attribute is present according to note 5 or note 7, it need not contain those entries that are unchanged compared to the entries that were passed in the LCM operation which is related to this granting exchange.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents an external VL.\n* NOTE 1:\tA link port is not needed for an external CP instance that exposes a VIP CP in the following cases:\n 1) For a VIP CP directly exposed as an external CP:\n 1.1) No dedicated IP address is allocated as VIP address, as indicated in the VNFD.\n 1.2) A dedicated IP address is allocated as VIP address, but the NFVO indicates that no port is needed\n (createExtLinkPort in VnfExtCpConfig set to false).\n 2) For a VIP CP exposed as an external CP via a floating IP address:\n 2.1) No dedicated IP address is allocated as VIP address, as indicated in the VNFD, and the VNFC CP\n associated to the VIP CP is also exposed via a floating IP address.\n 3) For a VIRTUAL CP exposed as an external CP.\n 4) For a VNFC CP exposed as an external CP in a secondary container cluster external network or a\n secondary container cluster internal network.\n\n* NOTE 2: 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", "resourceId", "extCps"],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vimConnectionId": {
+ "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.\n",
+ "type": "string"
+ },
+ "extCps": {
+ "description": "External CPs of the VNF to be connected to this external VL. Entries in the list of external CP data that are unchanged need not be supplied if the ExtVirtualLinkData structure is part of a request or response that modifies the external connectivity.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents configuration information for external CPs created. * NOTE 1: \tIn case this identifier refers to a CPD with trunking enabled, the external CP instances created\n from this CPD will represent ports in a trunk.\n* NOTE 2: \tWithin one VNF instance, all VNFC instances created from a particular VDU have the same external\n connectivity. Thus, given a particular value of the \"cpdId\" attribute, there shall be one\n \"cpConfig\" entry for each VNFC instance that has been or can be created from a VDU which includes\n a CPD identified by the \"cpdId\" attribute. If the cpConfig represents a subport in a trunk,\n all \"cpConfig\" entries in this list shall have the same segmentationId, which means they are\n connected to the same set of external VLs via the trunk.\n* NOTE 3: \tThe map entry value shall be set to \"null\" in order to delete a \"VnfExtCpConfig\" entry identified\n by a particular key value from the map, i.e. for the disconnection of an existing external\n CP instance addressed by cpInstanceId in the deleted map entry from a particular external\n virtual link, and deletion of that instance in case it represents a subport. Deleting the\n last key from the map removes the affected instance of the \"VnfExtCpData\" structure from\n its parent data structure.\n* NOTE 4: If, as defined by the input parameters of a \"ChangeVnfFlavour\", \"ChangeExtVnfConnectivity\" or\n \"ChangeCurrentVnfPkg\" operation or as part of the Grant response for any of these operations, a cpConfig\n map entry identified by a particular map key value is moved into another \"ExtVirtualLinkData\" or\n \"VnfExtCpData\" structure, this particular cpConfig map entry may be used by an external CP instance\n different than the one that has used it before the operation, or by no external CP instance at all.\n Renaming a CPD identifier during the \"changeCurrentVnfPkg\" operation does not count as moving the related\n \"cpConfig\" map entries to a new \"extCpData\" structure.\n",
+ "type": "object",
+ "required": ["cpdId"],
+ "properties": {
+ "cpdId": {
+ "description": "An identifier that is unique within a VNF descriptor.\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 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",
+ "anyOf": [
+ {
+ "required": ["linkPortId"]
+ },
+ {
+ "required": ["cpProtocolData"]
+ },
+ {
+ "required": ["netAttDefResourceId"]
+ }
+ ],
+ "type": "object",
+ "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 to the VNFM the need to create a dedicated link port for the external CP. If set to True, the VNFM shall create a link port. If set to False, the VNFM shall not create a link port. 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"
+ },
+ "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 2, 3 and 4.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ },
+ "cpProtocolData": {
+ "description": "Parameters for configuring the network protocols on the link port that connects the CP to a VL. See notes 1 and 2.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents network protocol data. * NOTE:\tThis attribute allows to signal the addition of further types of layer and protocol\n in future versions of the present document in a backwards-compatible way. In the current\n 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:\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 network address data for IP over Ethernet. * NOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. * NOTE 2:\tExactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present. * NOTE 3:\tIf the CP instance represents a subport in a trunk, segmentationId shall be present.\n Otherwise it shall not be present.\n* NOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the actual\n network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header\n of the packets or it may be an identifier used between the application and the NFVI networking\n infrastructure to identify the network sub-interface of the trunk port in question. In the latter\n case the NFVI infrastructure will map this local segmentationId to whatever segmentationId is\n actually used by the NFVI’s transport technology.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "required": ["macAddress"]
+ },
+ {
+ "required": ["ipAddresses"]
+ }
+ ],
+ "oneOf": [
+ {
+ "required": ["fixedAddresses"]
+ },
+ {
+ "required": ["numDynamicAddresses"]
+ },
+ {
+ "required": ["ipAddressRange"]
+ }
+ ],
+ "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: -\tVLAN: the subport uses VLAN as encapsulation type. -\tINHERIT: the subport gets its segmentation type from the network it’s 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"],
+ "properties": {
+ "type": {
+ "description": "The type of the IP addresses. Permitted values: IPV4, IPV6.\n",
+ "type": "string",
+ "enum": ["IPV4", "IPV6"]
+ },
+ "fixedAddresses": {
+ "description": "Fixed addresses to assign (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"
+ }
+ },
+ "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. 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.\n",
+ "type": "string"
+ }
+ }
+ }
+ }
+ }
+ },
+ "virtualCpAddress": {
+ "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",
+ "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"
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ },
+ "extLinkPorts": {
+ "description": "Externally provided link ports to be used to connect external connection points to this external VL. If this attribute is not present, the VNFM shall create the link ports on the external VL except in the cases defined below. See note 1.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents an externally provided link port to be used to connect an external connection point to an external VL. * NOTE:\tThe 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": {
+ "required": ["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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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"
+ }
+ }
+ },
+ "trunkResourceId": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "extNetAttDefResourceData": {
+ "description": "Externally provided network attachment definition resource(s) that provide the specification of the interface to attach external CPs to this external VL. See note 2. It is only applicable if the external VL is realized by a secondary container cluster network. It shall not be present otherwise.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents a network attachment definition resource that provides the specification of the interface to be used to connect one or multiple connection points to a secondary container cluster network realizing a VL.\n",
+ "type": "object",
+ "required": ["netAttDefResourceId", "resourceHandle"],
+ "properties": {
+ "netAttDefResourceId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceHandle": {
+ "required": ["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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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"
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ },
+ "extManagedVirtualLinks": {
+ "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",
+ "type": "object",
+ "required": ["id", "vnfVirtualLinkDescId", "resourceId"],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfVirtualLinkDescId": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "vimConnectionId": {
+ "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.\n",
+ "type": "string"
+ },
+ "netAttDefResourceData": {
+ "description": "Externally provided network attachment definition resource(s) that provide the specification of the interface to attach VNFC connection points to this externallymanaged VL. See notes 1 and 3.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents a network attachment definition resource that provides the specification of the interface to be used to connect one or multiple connection points to a secondary container cluster network realizing a VL.\n",
+ "type": "object",
+ "required": ["netAttDefResourceId", "resourceHandle"],
+ "properties": {
+ "netAttDefResourceId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceHandle": {
+ "required": ["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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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"
+ }
+ }
+ }
+ }
+ }
+ },
+ "intCp": {
+ "description": "Internal CPs of the VNF to be connected to this externally-managed VL. See note 1.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents input information related to one or more VNF internal CP instances created based on the same CPD.\nNOTE: 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 VNF internal CP, e.g. to build a link\n redundant mated pair in SR-IOV cases. When more than one netAttDefResourceId is indicated, all shall\n belong to the same namespace as defined by the corresponding \"netAttDefResourceNamespace\" attribute\n in the \"NetAttDefResourceData\".\n",
+ "type": "object",
+ "required": ["cpdId", "netAttDefResourceId"],
+ "properties": {
+ "cpdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "netAttDefResourceId": {
+ "description": "Identifiers of the “NetAttDefResourceData†structure that provides the specification of the interface to attach the VNF internal CP created from the CPD identified by cpdId to a secondary container cluster network. See note.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ }
+ }
+ }
+ },
+ "vnfLinkPort": {
+ "description": "Externally provided link ports to be used to connect VNFC connection points to this externally-managed VL on this network resource. If this attribute is not present, the VNFM shall create the link ports on the externally-managed VL. See note 2.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents an externally provided link port to be used to connect a VNFC connection point to an exernally managed VL.\n",
+ "type": "object",
+ "required": ["vnfLinkPortId", "resourceHandle"],
+ "properties": {
+ "vnfLinkPortId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "resourceHandle": {
+ "required": ["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 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. This value set is different from \n the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2). When the container \n infrastructure service management is a Kubernetes® instance the vimLevelResourceType is the type of \n resource, as would correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, \n e.g.: Pod, PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 2: When the container infrastructure service management is a Kubernetes® instance the resourceId shall be \n populated in the 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",
+ "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.\n",
+ "type": "string"
+ },
+ "vimLevelResourceType": {
+ "description": "Type of the resource in the scope of 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.\n* NOTE: At 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 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"
+ }
+ }
+ },
+ "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"
+ }
+ }
+ }
+ }
+ }
+ },
+ "extManagedMultisiteVirtualLinkId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "additionalParams": {
+ "description": "This 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"
+ },
+ "_links": {
+ "description": "Links to resources related to this resource.\n",
+ "type": "object",
+ "required": ["self", "vnfLcmOpOcc", "vnfInstance"],
+ "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"
+ }
+ }
+ },
+ "vnfLcmOpOcc": {
+ "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"
+ }
+ }
+ },
+ "vnfInstance": {
+ "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"
+ }
+ }
+ }
+ }
+ }
+ }
}
\ No newline at end of file
diff --git a/SOL003/VNFPackageManagement-API/ApiVersion.robot b/SOL003/VNFPackageManagement-API/ApiVersion.robot
index 41f0fbd755efb2539f5e3d40e793f969bcd5665f..ec0708c558de9c21b4c389405a00761021de5772 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] v3.5.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.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 f681dc9a0c1679e0bb8f4af26c5dadb635f5f9c8..26800b0549048a1ac089fd8fe2e9fbdced8c5276 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] v3.6.1
+ ... Reference: Clause 10.4.8.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.8.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.8.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.8.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.8.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.8.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.8.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.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 b73e74b588065afbda55767e633d2185f52e291f..6dd91307982b0baba096079225f07ac0d6187baa 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] v3.6.1
+ ... Reference: Clause 10.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.3.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.3.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.3.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.3.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.3.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.3.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.3.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.3.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.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 94151acfeded0b18ca76db4a8dea3843a2da219c..f67249059144aba6069186961601276d9303b75a 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] v3.6.1
+ ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.6.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.6.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.6.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.6.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.6.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.6.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.6.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.6.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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 0e1382a39f136b161936edfece4ddb7bf1967acf..b6e1b9a4a0f49273584e571f73a216f796527242 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] v3.6.1
+ ... Reference: Clause 10.4.4a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.4a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.4a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.4a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.4a.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.4a.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.4a.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.4a.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.4a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.4a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.4a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.4a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.4a.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.4a.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.4a.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.4a.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.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 721692e8ad7b8f5e46e245bb7683218092ad8435..9a63cc72427915f79bf9f48468e75fae38e38098 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] v3.6.1
+ ... Reference: Clause 10.4.9.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.9.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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 5591e12ad39dd44f0e315e0d73dda4adec11dbf0..4310c5a550c65ef3d41ff1d6adde60ec5e18e5a8 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] v3.6.1
+ ... Reference: Clause 10.4.9.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.9.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.9.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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 6700f3566ed97bf8ffdaf8930c92c2a7f09ffb9d..ae8a0c6f45e5f8efa8392fd383f37c7e5dd76408 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] v3.6.1
+ ... Reference: Clause 10.4.7.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.7.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.7.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.7.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.7.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.7.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.7.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.7.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.7.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.7.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.7.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.7.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.7.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -191,7 +191,7 @@ Get VNF Package Subscriptions - Unprocessable Entity
... 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.
... 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] v3.6.1
+ ... Reference: Clause 10.4.7.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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 40833b0aa4decf906d3e6e6a8fc56738918c02c3..c7256b1a1a18efd9a57e0cf5b52f124c8fdaff93 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] v3.6.1
+ ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.4.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.4.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.4.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.4.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.4.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.4.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.4.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.4.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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 7eb7e3723065fc9e71fc4eacd5ba3294c96097d1..1e22a6ef52651b3392b646d05459262df0439da5 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] v3.6.1
+ ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.5a.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.5a.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.5a.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.6.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.5a.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.5a.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.5a.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.6.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.5a.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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 63cd723d15c7977b5f10a52cc869edb9d6498355..1aa94439caeaa1de545e0b2ed2cac34b3e1df36c 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] v3.6.1
+ ... Reference: Clause 10.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.3.5.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.3.5.3 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.3.5.4 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.3.5.5 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.3.5.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.3.5.3 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.3.5.4 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.3.5.5 - ETSI GS NFV-SOL 003 [1] v4.3.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 eaa111a909f8e472fa48b22d2d5e1481ca9266e3..c04f763739cd628555930bf3c9328af54e2fe45e 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] v3.6.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.2.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.2.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.2.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.2.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 4.3.3.2.1, 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 4.3.3.2.1, 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 4.3.3.2.1, 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 4.3.3.2.1, 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.2.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.2.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.2.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.2.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 4.3.3.2.1, 10.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: The VNFM supports the use of fields attribute selector
... Post-Conditions: none
diff --git a/SOL003/VNFPackageManagement-API/jsons/VnfPackageOnboardingNotification.json b/SOL003/VNFPackageManagement-API/jsons/VnfPackageOnboardingNotification.json
index f9b87c055cc9a43d45416870c028f4a953752aa5..4671a7c6c19175454e38f7eae2eaf091b14c631d 100644
--- a/SOL003/VNFPackageManagement-API/jsons/VnfPackageOnboardingNotification.json
+++ b/SOL003/VNFPackageManagement-API/jsons/VnfPackageOnboardingNotification.json
@@ -5,5 +5,6 @@
"timeStamp":"",
"vnfPkgId":"{indicatorId} ",
"vnfdId":"{vndId}",
+ "vnfmInfo": [],
"_links":""
}}
diff --git a/SOL003/VNFPackageManagement-API/schemas/PkgmSubscription.schema.json b/SOL003/VNFPackageManagement-API/schemas/PkgmSubscription.schema.json
index 4c32bc8bcec4fd906d115ec6a7348aa77542897d..d7b8073681932d6b98b01ac37e63636dce8fb514 100644
--- a/SOL003/VNFPackageManagement-API/schemas/PkgmSubscription.schema.json
+++ b/SOL003/VNFPackageManagement-API/schemas/PkgmSubscription.schema.json
@@ -1,22 +1,33 @@
{
"description": "This type represents a subscription related to notifications about VNF package management.\n",
"type": "object",
- "required": [
- "id",
- "callbackUri",
- "_links"
- ],
+ "required": ["id", "callbackUri", "_links"],
"properties": {
"id": {
"description": "An identifier with the intention of being globally unique.\n",
"type": "string"
},
"filter": {
- "description": "This type represents a subscription filter related to notifications related to VNF package management. At a particular nesting level in the filter structure, the following applies: All attributes shall match in order for the filter to match (logical \"and\" between different filter attributes). If an attribute is an array, the attribute shall match if at least one of the values in the array matches (logical \"or\" between the values of one filter attribute).\n",
+ "description": "This type represents a subscription filter related to notifications related to VNF package management.\nAt a particular nesting level in the filter structure, the following applies: All attributes shall match in order for the filter to match (logical \"and\" between different filter attributes). If an attribute is an array, the attribute shall match if at least one of the values in the array matches (logical \"or\" between the values of one filter attribute).\nNOTE 1:\tThe permitted values of the \"notificationTypes\" attribute are spelled exactly as the names of the \n notification types to facilitate automated code generation systems.\nNOTE 2:\tThe attributes \"vnfProductsFromProviders\", \"vnfdId\" and \"vnfPkgId\" are alternatives to reference to \n particular VNF packages in a filter. They should not be used both in the same filter instance, but \n one alternative should be chosen.\n",
"type": "object",
+ "anyOf": [
+ {
+ "oneOf": [
+ {
+ "required": ["vnfProductsFromProviders"]
+ },
+ {
+ "required": ["vnfdId"]
+ },
+ {
+ "required": ["vnfPkgId"]
+ }
+ ]
+ }
+ ],
"properties": {
"notificationTypes": {
- "description": "Match particular notification types. Permitted values: - VnfPackageOnboardingNotification - VnfPackageChangeNotification The permitted values of the \"notificationTypes\" attribute are spelled exactly as the names of the notification types to facilitate automated code generation systems.\n",
+ "description": "Match particular notification types. Permitted values: - VnfPackageOnboardingNotification - VnfPackageChangeNotification See note 1.\n",
"type": "array",
"items": {
"type": "string",
@@ -27,16 +38,14 @@
}
},
"vnfProductsFromProviders": {
- "description": "If present, match VNF packages that contain VNF products from certain providers. The attributes \"vnfProductsFromProviders\", \"vnfdId\" and \"vnfPkgId\" are alternatives to reference to particular VNF packages in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n",
+ "description": "If present, match VNF packages that contain VNF products from certain providers. See note 2.\n",
"type": "array",
"items": {
"type": "object",
- "required": [
- "vnfProvider"
- ],
+ "required": ["vnfProvider"],
"properties": {
"vnfProvider": {
- "description": "Name of the VNF provider to match.\n",
+ "description": "A string defined in IETF RFC 8259.\n",
"type": "string"
},
"vnfProducts": {
@@ -44,12 +53,10 @@
"type": "array",
"items": {
"type": "object",
- "required": [
- "vnfProductName"
- ],
+ "required": ["vnfProductName"],
"properties": {
"vnfProductName": {
- "description": "Name of the VNF product to match.\n",
+ "description": "A string defined in IETF RFC 8259.\n",
"type": "string"
},
"versions": {
@@ -57,19 +64,17 @@
"type": "array",
"items": {
"type": "object",
- "required": [
- "vnfSoftwareVersion"
- ],
+ "required": ["vnfSoftwareVersion"],
"properties": {
"vnfSoftwareVersion": {
- "description": "A Version.\n",
+ "description": "A version.\n",
"type": "string"
},
"vnfdVersions": {
"description": "If present, match VNF packages that contain VNF products with certain VNFD versions, a certain software version and a certain product name, from one particular provider.\n",
"type": "array",
"items": {
- "description": "A Version.\n",
+ "description": "A version.\n",
"type": "string"
}
}
@@ -83,7 +88,7 @@
}
},
"vnfdId": {
- "description": "Match VNF packages with a VNFD identifier listed in the attribute. The attributes \"vnfProductsFromProviders\", \"vnfdId\" and \"vnfPkgId\" are alternatives to reference to particular VNF packages in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n",
+ "description": "Match VNF packages with a VNFD identifier listed in the attribute. See note 2.\n",
"type": "array",
"items": {
"description": "An identifier with the intention of being globally unique.\n",
@@ -91,7 +96,7 @@
}
},
"vnfPkgId": {
- "description": "Match VNF packages with a package identifier listed in the attribute. May be present if the \"notificationTypes\" attribute contains the value \"VnfPackageChangeNotification\", and shall be absent otherwise. The attributes \"vnfProductsFromProviders\", \"vnfdId\" and \"vnfPkgId\" are alternatives to reference to particular VNF packages in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n",
+ "description": "Match VNF packages with a package identifier listed in the attribute. May be present if the \"notificationTypes\" attribute contains the value \"VnfPackageChangeNotification\" and shall be absent otherwise. See note 2.\n",
"type": "array",
"items": {
"description": "An identifier with the intention of being globally unique.\n",
@@ -99,15 +104,22 @@
}
},
"operationalState": {
- "description": "- ENABLED: The VNF package is enabled, i.e. it can be used for instantiation of new VNF instances.\n- DISABLED: The VNF package is disabled, i.e. it cannot be used for further VNF instantiation requests (unless and until the VNF package\n is re-enabled).\n",
+ "description": "- ENABLED: The VNF package is enabled, i.e. it can be used for\n the creation of new \"Individual VNF instance\" resources.\n- DISABLED: The VNF package is disabled, i.e. it shall not be used for\n the creation of further \"Individual VNF instance\" resources\n (unless and until the VNF package is re-enabled).\n",
"type": "string",
- "enum": [
- "ENABLED",
- "DISABLED"
- ]
+ "enum": ["ENABLED", "DISABLED"]
},
"usageState": {
- "description": "- IN_USE: VNF instances instantiated from this VNF package exist. - NOT_IN_USE: No existing VNF instance is instantiated from this VNF package.\n"
+ "description": "- 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",
+ "type": "string",
+ "enum": ["IN_USE", "NOT_IN_USE"]
+ },
+ "vnfmInfo": {
+ "description": "Match strings that specify VNFMs compatible with the VNF. See table 10.5.2.2-1.\n",
+ "type": "array",
+ "items": {
+ "description": "A string defined in IETF RFC 8259.\n",
+ "type": "string"
+ }
}
}
},
@@ -118,21 +130,16 @@
"_links": {
"description": "Links to resources related to this resource.\n",
"type": "object",
- "required": [
- "self"
- ],
+ "required": ["self"],
"properties": {
"self": {
- "description": "This type represents a link to a resource.\n",
+ "description": "This type represents a link to a resource using an absolute URI.\n",
"type": "object",
- "required": [
- "href"
- ],
+ "required": ["href"],
"properties": {
"href": {
- "description": "URI of the referenced resource.\n",
- "type": "string",
- "format": "url"
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
}
}
}
diff --git a/SOL003/VNFPackageManagement-API/schemas/PkgmSubscriptions.schema.json b/SOL003/VNFPackageManagement-API/schemas/PkgmSubscriptions.schema.json
index 5a318309d4efbe578c0b6d2658105212d5b7667b..da51850cf7d97296bb7665f0118187076219fae6 100644
--- a/SOL003/VNFPackageManagement-API/schemas/PkgmSubscriptions.schema.json
+++ b/SOL003/VNFPackageManagement-API/schemas/PkgmSubscriptions.schema.json
@@ -1 +1,152 @@
-{ "type": "array", "items": { "description": "This type represents a subscription related to notifications about VNF package management.\n", "type": "object", "required": [ "id", "callbackUri", "_links" ], "properties": { "id": { "description": "An identifier with the intention of being globally unique.\n", "type": "string" }, "filter": { "description": "This type represents a subscription filter related to notifications related to VNF package management. At a particular nesting level in the filter structure, the following applies: All attributes shall match in order for the filter to match (logical \"and\" between different filter attributes). If an attribute is an array, the attribute shall match if at least one of the values in the array matches (logical \"or\" between the values of one filter attribute).\n", "type": "object", "properties": { "notificationTypes": { "description": "Match particular notification types. Permitted values: - VnfPackageOnboardingNotification - VnfPackageChangeNotification The permitted values of the \"notificationTypes\" attribute are spelled exactly as the names of the notification types to facilitate automated code generation systems.\n", "type": "array", "items": { "type": "string", "enum": [ "VnfPackageOnboardingNotification", "VnfPackageChangeNotification" ] } }, "vnfProductsFromProviders": { "description": "If present, match VNF packages that contain VNF products from certain providers. The attributes \"vnfProductsFromProviders\", \"vnfdId\" and \"vnfPkgId\" are alternatives to reference to particular VNF packages in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n", "type": "array", "items": { "type": "object", "required": [ "vnfProvider" ], "properties": { "vnfProvider": { "description": "Name of the VNF provider to match.\n", "type": "string" }, "vnfProducts": { "description": "If present, match VNF packages that contain VNF products with certain product names, from one particular provider.\n", "type": "array", "items": { "type": "object", "required": [ "vnfProductName" ], "properties": { "vnfProductName": { "description": "Name of the VNF product to match.\n", "type": "string" }, "versions": { "description": "If present, match VNF packages that contain VNF products with certain versions and a certain product name, from one particular provider.\n", "type": "array", "items": { "type": "object", "required": [ "vnfSoftwareVersion" ], "properties": { "vnfSoftwareVersion": { "description": "A Version.\n", "type": "string" }, "vnfdVersions": { "description": "If present, match VNF packages that contain VNF products with certain VNFD versions, a certain software version and a certain product name, from one particular provider.\n", "type": "array", "items": { "description": "A Version.\n", "type": "string" } } } } } } } } } } }, "vnfdId": { "description": "Match VNF packages with a VNFD identifier listed in the attribute. The attributes \"vnfProductsFromProviders\", \"vnfdId\" and \"vnfPkgId\" are alternatives to reference to particular VNF packages in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n", "type": "array", "items": { "description": "An identifier with the intention of being globally unique.\n", "type": "string" } }, "vnfPkgId": { "description": "Match VNF packages with a package identifier listed in the attribute. May be present if the \"notificationTypes\" attribute contains the value \"VnfPackageChangeNotification\", and shall be absent otherwise. The attributes \"vnfProductsFromProviders\", \"vnfdId\" and \"vnfPkgId\" are alternatives to reference to particular VNF packages in a filter. They should not be used both in the same filter instance, but one alternative should be chosen.\n", "type": "array", "items": { "description": "An identifier with the intention of being globally unique.\n", "type": "string" } }, "operationalState": { "description": "- ENABLED: The VNF package is enabled, i.e. it can be used for instantiation of new VNF instances.\n- DISABLED: The VNF package is disabled, i.e. it cannot be used for further VNF instantiation requests (unless and until the VNF package\n is re-enabled).\n", "type": "string", "enum": [ "ENABLED", "DISABLED" ] }, "usageState": { "description": "- IN_USE: VNF instances instantiated from this VNF package exist. - NOT_IN_USE: No existing VNF instance is instantiated from this VNF package.\n" } } }, "callbackUri": { "description": "String formatted according to IETF RFC 3986.\n", "type": "string" }, "_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 the referenced resource.\n", "type": "string", "format": "url" } } } } } } }}
\ No newline at end of file
+{
+ "type": "array",
+ "items": {
+ "description": "This type represents a subscription related to notifications about VNF package management.\n",
+ "type": "object",
+ "required": ["id", "callbackUri", "_links"],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "filter": {
+ "description": "This type represents a subscription filter related to notifications related to VNF package management.\nAt a particular nesting level in the filter structure, the following applies: All attributes shall match in order for the filter to match (logical \"and\" between different filter attributes). If an attribute is an array, the attribute shall match if at least one of the values in the array matches (logical \"or\" between the values of one filter attribute).\nNOTE 1:\tThe permitted values of the \"notificationTypes\" attribute are spelled exactly as the names of the \n notification types to facilitate automated code generation systems.\nNOTE 2:\tThe attributes \"vnfProductsFromProviders\", \"vnfdId\" and \"vnfPkgId\" are alternatives to reference to \n particular VNF packages in a filter. They should not be used both in the same filter instance, but \n one alternative should be chosen.\n",
+ "type": "object",
+ "anyOf": [
+ {
+ "oneOf": [
+ {
+ "required": ["vnfProductsFromProviders"]
+ },
+ {
+ "required": ["vnfdId"]
+ },
+ {
+ "required": ["vnfPkgId"]
+ }
+ ]
+ }
+ ],
+ "properties": {
+ "notificationTypes": {
+ "description": "Match particular notification types. Permitted values: - VnfPackageOnboardingNotification - VnfPackageChangeNotification See note 1.\n",
+ "type": "array",
+ "items": {
+ "type": "string",
+ "enum": [
+ "VnfPackageOnboardingNotification",
+ "VnfPackageChangeNotification"
+ ]
+ }
+ },
+ "vnfProductsFromProviders": {
+ "description": "If present, match VNF packages that contain VNF products from certain providers. See note 2.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": ["vnfProvider"],
+ "properties": {
+ "vnfProvider": {
+ "description": "A string defined in IETF RFC 8259.\n",
+ "type": "string"
+ },
+ "vnfProducts": {
+ "description": "If present, match VNF packages that contain VNF products with certain product names, from one particular provider.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": ["vnfProductName"],
+ "properties": {
+ "vnfProductName": {
+ "description": "A string defined in IETF RFC 8259.\n",
+ "type": "string"
+ },
+ "versions": {
+ "description": "If present, match VNF packages that contain VNF products with certain versions and a certain product name, from one particular provider.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": ["vnfSoftwareVersion"],
+ "properties": {
+ "vnfSoftwareVersion": {
+ "description": "A version.\n",
+ "type": "string"
+ },
+ "vnfdVersions": {
+ "description": "If present, match VNF packages that contain VNF products with certain VNFD versions, a certain software version and a certain product name, from one particular provider.\n",
+ "type": "array",
+ "items": {
+ "description": "A version.\n",
+ "type": "string"
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ },
+ "vnfdId": {
+ "description": "Match VNF packages with a VNFD identifier listed in the attribute. See note 2.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ },
+ "vnfPkgId": {
+ "description": "Match VNF packages with a package identifier listed in the attribute. May be present if the \"notificationTypes\" attribute contains the value \"VnfPackageChangeNotification\" and shall be absent otherwise. See note 2.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ },
+ "operationalState": {
+ "description": "- ENABLED: The VNF package is enabled, i.e. it can be used for\n the creation of new \"Individual VNF instance\" resources.\n- DISABLED: The VNF package is disabled, i.e. it shall not be used for\n the creation of further \"Individual VNF instance\" resources\n (unless and until the VNF package is re-enabled).\n",
+ "type": "string",
+ "enum": ["ENABLED", "DISABLED"]
+ },
+ "usageState": {
+ "description": "- 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",
+ "type": "string",
+ "enum": ["IN_USE", "NOT_IN_USE"]
+ },
+ "vnfmInfo": {
+ "description": "Match strings that specify VNFMs compatible with the VNF. See table 10.5.2.2-1.\n",
+ "type": "array",
+ "items": {
+ "description": "A string defined in IETF RFC 8259.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "callbackUri": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ },
+ "_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 using an absolute URI.\n",
+ "type": "object",
+ "required": ["href"],
+ "properties": {
+ "href": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+}
diff --git a/SOL003/VNFPackageManagement-API/schemas/VnfPackageChangeNotification.schema.json b/SOL003/VNFPackageManagement-API/schemas/VnfPackageChangeNotification.schema.json
index 5cf4045fa21b0955b8579801e4ab4e02e234047a..4f73147a88bf57a833d470821e1065b19b66c320 100644
--- a/SOL003/VNFPackageManagement-API/schemas/VnfPackageChangeNotification.schema.json
+++ b/SOL003/VNFPackageManagement-API/schemas/VnfPackageChangeNotification.schema.json
@@ -1,97 +1,92 @@
{
- "description": "This type represents a VNF package management notification, which informs the receiver of a change of the status in an on-boarded VNF package. Only changes in the \"operationalState\" attribute of an on-boarded VNF package and the deletion NF package will be reported. Changes in the \"usageState\" and \"onboardingState\" attributes are not reported. The notification shall be triggered by the NFVO when there is a change in the status of an onboarded VNF package, as follows: * The \"operationalState\" attribute of a VNF package has changed, and the\n \"onboardingState\" attribute of the package has the value \"ONBOARDED\"\n (i.e. the package has been onboarded previously).\n* The on-boarded VNF package has been deleted.\n",
- "type": "object",
- "required": [
- "id",
- "notificationType",
- "timeStamp",
- "vnfPkgId",
- "vnfdId",
- "changeType",
- "_links"
- ],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "notificationType": {
- "description": "Discriminator for the different notification types. Shall be set to \"VnfPackageChangeNotification\" for this notification type.\n",
- "type": "string",
- "enum": [
- "VnfPackageChangeNotification"
- ]
- },
- "subscriptionId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "timeStamp": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "vnfPkgId": {
- "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"
- },
- "changeType": {
- "description": "- OP_STATE_CHANGE: The \"operationalState\" attribute has been changed. - PKG_DELETE: The VNF package has been deleted.\n",
- "type": "string",
- "enum": [
- "OP_STATE_CHANGE",
- "PKG_DELETE"
- ]
- },
- "operationalState": {
- "description": "- ENABLED: The VNF package is enabled, i.e. it can be used for\n instantiation of new VNF instances.\n- DISABLED: The VNF package is disabled, i.e. it cannot be used for\n further VNF instantiation requests (unless and until the VNF package\n is re-enabled).\n",
- "type": "string",
- "enum": [
- "ENABLED",
- "DISABLED"
- ]
- },
- "_links": {
- "description": "This type represents the links to resources that a VNF package management notification can contain.\n",
- "type": "object",
- "required": [
- "vnfPackage",
- "subscription"
- ],
- "properties": {
- "vnfPackage": {
- "description": "This type represents a link to a resource.\n",
- "type": "object",
- "required": [
- "href"
- ],
- "properties": {
- "href": {
- "description": "URI of the referenced resource.\n",
- "type": "string",
- "format": "url"
- }
- }
- },
- "subscription": {
- "description": "This type represents a link to a resource.\n",
- "type": "object",
- "required": [
- "href"
- ],
- "properties": {
- "href": {
- "description": "URI of the referenced resource.\n",
- "type": "string",
- "format": "url"
- }
- }
- }
- }
- }
- }
-}
\ No newline at end of file
+ "description": "This type represents a VNF package management notification, which informs the receiver of a change of the status in an on-boarded VNF package. Only changes in the \"operationalState\" attribute of an on-boarded VNF package and the deletion NF package will be reported. Changes in the \"usageState\" and \"onboardingState\" attributes are not reported. The notification shall be triggered by the NFVO when there is a change in the status of an onboarded VNF package, as follows: * The \"operationalState\" attribute of a VNF package has changed, and the\n \"onboardingState\" attribute of the package has the value \"ONBOARDED\"\n (i.e. the package has been onboarded previously).\n* The on-boarded VNF package has been deleted, and the \"onboardingState\"\n attribute of the deleted package had the value \"ONBOARDED\".\n",
+ "type": "object",
+ "required": [
+ "id",
+ "notificationType",
+ "subscriptionId",
+ "timeStamp",
+ "vnfPkgId",
+ "vnfdId",
+ "changeType",
+ "_links"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "notificationType": {
+ "description": "Discriminator for the different notification types. Shall be set to \"VnfPackageChangeNotification\" for this notification type.\n",
+ "type": "string",
+ "enum": ["VnfPackageChangeNotification"]
+ },
+ "subscriptionId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "timeStamp": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "vnfPkgId": {
+ "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"
+ },
+ "changeType": {
+ "description": "- OP_STATE_CHANGE: The \"operationalState\" attribute has been changed. - PKG_DELETE: The VNF package has been deleted.\n",
+ "type": "string",
+ "enum": ["OP_STATE_CHANGE", "PKG_DELETE"]
+ },
+ "operationalState": {
+ "description": "- ENABLED: The VNF package is enabled, i.e. it can be used for\n the creation of new \"Individual VNF instance\" resources.\n- DISABLED: The VNF package is disabled, i.e. it shall not be used for\n the creation of further \"Individual VNF instance\" resources\n (unless and until the VNF package is re-enabled).\n",
+ "type": "string",
+ "enum": ["ENABLED", "DISABLED"]
+ },
+ "_links": {
+ "description": "This type represents the links to resources that a VNF package management notification can contain.\n",
+ "type": "object",
+ "required": ["vnfPackage", "subscription"],
+ "properties": {
+ "vnfPackage": {
+ "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": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ }
+ }
+ },
+ "vnfPackageByVnfdId": {
+ "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": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ }
+ }
+ },
+ "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": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ }
+ }
+ }
+ }
+ }
+ }
+}
diff --git a/SOL003/VNFPackageManagement-API/schemas/VnfPackageOnboardingNotification.schema.json b/SOL003/VNFPackageManagement-API/schemas/VnfPackageOnboardingNotification.schema.json
index 903f0bf44cf71f37dadf14ac873ff028bf971a38..b7952972d0a4246dcc65b90415479d1e74d44b9a 100644
--- a/SOL003/VNFPackageManagement-API/schemas/VnfPackageOnboardingNotification.schema.json
+++ b/SOL003/VNFPackageManagement-API/schemas/VnfPackageOnboardingNotification.schema.json
@@ -1,12 +1,14 @@
{
- "description": "This type represents a VNF package management notification, which informs the receiver that the onboarding process of a VNF package is complete and the package is ready for use. The notification shall be triggered by the NFVO when the \"onboardingState\" attribute of a new VNF package has changed to \"ONBOARDED\".",
+ "description": "This type represents a VNF package management notification, which informs the receiver that the onboarding process of a VNF package is complete and the package is ready for use. The notification shall be triggered by the NFVO when the \"onboardingState\" attribute of a new VNF package has changed to \"ONBOARDED\".\n",
"type": "object",
"required": [
"id",
"notificationType",
+ "subscriptionId",
"timeStamp",
"vnfPkgId",
"vnfdId",
+ "vnfmInfo",
"_links"
],
"properties": {
@@ -17,16 +19,14 @@
"notificationType": {
"description": "Discriminator for the different notification types. Shall be set to \"VnfPackageOnboardingNotification\" for this notification type.\n",
"type": "string",
- "enum": [
- "VnfPackageOnboardingNotification"
- ]
+ "enum": ["VnfPackageOnboardingNotification"]
},
"subscriptionId": {
"description": "An identifier with the intention of being globally unique.\n",
"type": "string"
},
"timeStamp": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
"type": "string",
"format": "date-time"
},
@@ -38,39 +38,49 @@
"description": "An identifier with the intention of being globally unique.\n",
"type": "string"
},
+ "vnfmInfo": {
+ "description": "Specifies VNFMs compatible with the VNF. This information is copied from the VNFD. See table 10.5.2.2-1.\n",
+ "type": "array",
+ "items": {
+ "description": "A string defined in IETF RFC 8259.\n",
+ "type": "string"
+ }
+ },
"_links": {
"description": "This type represents the links to resources that a VNF package management notification can contain.\n",
"type": "object",
- "required": [
- "vnfPackage",
- "subscription"
- ],
+ "required": ["vnfPackage", "subscription"],
"properties": {
"vnfPackage": {
- "description": "This type represents a link to a resource.\n",
+ "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": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ }
+ }
+ },
+ "vnfPackageByVnfdId": {
+ "description": "This type represents a link to a resource in a notification, using an absolute or relative URI.\n",
"type": "object",
- "required": [
- "href"
- ],
+ "required": ["href"],
"properties": {
"href": {
- "description": "URI of the referenced resource.\n",
- "type": "string",
- "format": "url"
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
}
}
},
"subscription": {
- "description": "This type represents a link to a resource.\n",
+ "description": "This type represents a link to a resource in a notification, using an absolute or relative URI.\n",
"type": "object",
- "required": [
- "href"
- ],
+ "required": ["href"],
"properties": {
"href": {
- "description": "URI of the referenced resource.\n",
- "type": "string",
- "format": "url"
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
}
}
}
diff --git a/SOL003/VNFPackageManagement-API/schemas/additionalArtifacts.schema.json b/SOL003/VNFPackageManagement-API/schemas/additionalArtifacts.schema.json
index bff5343dc2b70989f02523fd7ee600b8ccf6c333..a8d34a22b55e8e8c64c5b035c059b6c25cfae42a 100644
--- a/SOL003/VNFPackageManagement-API/schemas/additionalArtifacts.schema.json
+++ b/SOL003/VNFPackageManagement-API/schemas/additionalArtifacts.schema.json
@@ -1,34 +1,44 @@
{
- "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 a VNF package.\n",
- "type": "object",
- "required": ["artifactPath", "checksum"],
- "properties": {
- "artifactPath": {
- "description": "Path in the VNF package, which identifies the artifact and also allows to access a copy of the artifact.\n",
- "type": "string"
- },
- "checksum": {
- "description": "This type represents the checksum of a VNF package or an artifact file.\n",
- "type": "object",
- "required": ["algorithm", "hash"],
- "properties": {
- "algorithm": {
- "description": "Name of the algorithm used to generate the checksum, as defined in ETSI GS NFV-SOL 004. For example, SHA-256, SHA-512.\n",
- "type": "string"
- },
- "hash": {
- "description": "The hexadecimal value of the checksum.\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"
- }
- }
- }
+ "description": "Information about VNF package artifacts contained in the VNF package that are not software images. Every local and external artifact declared in the manifest shall be included, except the software images and the files that make up the parts of the VNFD (see clause 10.4.4.3.2). Signature files and certificate files are not considered as artifacts, however, the content of the \"Licenses\" and \"Testing\" directories in the VNF package is. This attribute shall not be present before the VNF package content is on-boarded. Otherwise, this attribute shall be present if the VNF package contains additional artifacts.\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.\n",
+ "type": "object",
+ "required": ["artifactPath", "checksum", "isEncrypted"],
+ "properties": {
+ "artifactPath": {
+ "description": "A string defined in IETF RFC 8259.\n",
+ "type": "string"
+ },
+ "artifactURI": {
+ "description": "URI of the artifact as defined in the VNF package manifest. Shall be present if the artifact is external to the package and shall be absent otherwise.\nEXAMPLE: https://example.com/m%40ster.sh\n",
+ "type": "array",
+ "items": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ }
+ },
+ "checksum": {
+ "description": "Cheksum description\n",
+ "type": "string"
+ },
+ "isEncrypted": {
+ "description": "The Boolean is a data type having two values (true and false).\n",
+ "type": "boolean"
+ },
+ "nonManoArtifactSetId": {
+ "description": "A string defined in IETF RFC 8259.\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.\nValid values: -\tHISTORY: a history artifact as per clause 4.3.3 in ETSI GS NFV-SOL 004 -\tTESTING: a testing artifact as per clause 4.3.4 in ETSI GS NFV-SOL 004 -\tLICENSE: 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 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"
+ }
+ }
+ }
}
\ No newline at end of file
diff --git a/SOL003/VNFPackageManagement-API/schemas/links.schema.json b/SOL003/VNFPackageManagement-API/schemas/links.schema.json
index 5cc0e74fa5b66bfb92009ec3aada60336206a7b5..74b352e786bc58e9831870cde5675ce6ae72bcab 100644
--- a/SOL003/VNFPackageManagement-API/schemas/links.schema.json
+++ b/SOL003/VNFPackageManagement-API/schemas/links.schema.json
@@ -1,43 +1,40 @@
{
- "description": "Links to resources related to this resource.\n",
- "type": "object",
- "required": ["self", "packageContent"],
- "properties": {
- "self": {
- "description": "This type represents a link to a resource.\n",
- "type": "object",
- "required": ["href"],
- "properties": {
- "href": {
- "description": "URI of the referenced resource.\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 the referenced resource.\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 the referenced resource.\n",
- "type": "string",
- "format": "url"
- }
- }
- }
- }
-}
\ No newline at end of file
+ "description": "Links to resources related to this resource.\n",
+ "type": "object",
+ "required": ["self", "packageContent"],
+ "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"
+ }
+ }
+ },
+ "vnfd": {
+ "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"
+ }
+ }
+ },
+ "packageContent": {
+ "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"
+ }
+ }
+ }
+ }
+}
diff --git a/SOL003/VNFPackageManagement-API/schemas/softwareImage.schema.json b/SOL003/VNFPackageManagement-API/schemas/softwareImage.schema.json
index 90610b4a14928b5321764c0eab77ddc89586130d..0dfb28ae12f1bea7440032c2ecce4fabb177c367 100644
--- a/SOL003/VNFPackageManagement-API/schemas/softwareImage.schema.json
+++ b/SOL003/VNFPackageManagement-API/schemas/softwareImage.schema.json
@@ -1,81 +1,94 @@
{
- "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 a VNF package which represents a software image.\n",
- "type": "object",
- "required": ["id", "name", "provider", "version", "checksum", "containerFormat", "diskFormat", "createdAt", "minDisk", "minRam", "size", "imagePath"],
- "properties": {
- "id": {
- "description": "An identifier that is unique within a VNF descriptor.\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.\n",
- "type": "string"
- },
- "checksum": {
- "description": "This type represents the checksum of a VNF package or an artifact file.\n",
- "type": "object",
- "required": ["algorithm", "hash"],
- "properties": {
- "algorithm": {
- "description": "Name of the algorithm used to generate the checksum, as defined in ETSI GS NFV-SOL 004. For example, SHA-256, SHA-512.\n",
- "type": "string"
- },
- "hash": {
- "description": "The hexadecimal value of the checksum.\n",
- "type": "string"
- }
- }
- },
- "containerFormat": {
- "description": "Container format indicates whether the software image is in a file format that also contains metadata about the actual software. Permitted values: - AKI: a kernel image format - AMI: a machine image format - ARI: a ramdisk image format - BARE: the image does not have a container or metadata envelope - DOCKER: docker container format - OVA: OVF package in a tarfile - OVF: OVF container format The list of permitted values was taken from \"Container formats\" in http://docs.openstack.org/image-guide/image-formats.html\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\n- QCOW2: a common disk image format, which can expand dynamically and supports copy on write\n- 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 The list of permitted values was adapted from \"Disk formats\" in http://docs.openstack.org/image-guide/image-formats.html\n",
- "type": "string",
- "enum": ["AKI", "AMI", "ISO", "QCOW2", "RAW", "VDI", "VHD", "VHDX", "VMDK"]
- },
- "createdAt": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "minDisk": {
- "description": "The minimal disk for this software image in bytes.\n",
- "type": "integer"
- },
- "minRam": {
- "description": "The minimal RAM for this software image in bytes.\n",
- "type": "integer"
- },
- "size": {
- "description": "Size of this software image in bytes.\n",
- "type": "integer"
- },
- "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 in the VNF package, which identifies the image artifact and also allows to access a copy of the image artifact.\n",
- "type": "string"
- },
- "imageUri": {
- "description": "URI of the image artifact as defined in the VNF package manifest.\n",
- "type": "string"
- }
- }
- }
+ "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..\n* NOTE 1:\tThe list of permitted values was taken from \"Container formats\" in OpenStack® documentation: \"Disk and container formats for images\"\n (Available at https://docs.openstack.org/glance/pike/user/formats.html).\n* NOTE 2:\tThe list of permitted values was adapted from \"Disk formats\" in OpenStack® documentation: \"Disk and container formats for images\"\n (Available at https://docs.openstack.org/glance/pike/user/formats.html).\n* NOTE 3: The attribute shall be present for VM-based software images referenced from a Vdu, and shall be absent\n otherwise.\n* NOTE 4: The attribute shall be present for software images referenced from a VirtualStorageDesc, and shall be absent\n otherwise.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "name",
+ "provider",
+ "version",
+ "checksum",
+ "isEncrypted",
+ "containerFormat",
+ "createdAt",
+ "size"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "name": {
+ "description": "A string defined in IETF RFC 8259.\n",
+ "type": "string"
+ },
+ "provider": {
+ "description": "A string defined in IETF RFC 8259.\n",
+ "type": "string"
+ },
+ "version": {
+ "description": "A version.\n",
+ "type": "string"
+ },
+ "checksum": {
+ "description": "Cheksum description\n",
+ "type": "string"
+ },
+ "isEncrypted": {
+ "description": "The Boolean is a data type having two values (true and false).\n",
+ "type": "boolean"
+ },
+ "containerFormat": {
+ "description": "Container format indicates whether the software image is in a file format that also contains metadata about the actual software. Permitted values: - AKI: a kernel image format - AMI: a machine image format - ARI: a ramdisk image format - BARE: the image does not have a container or metadata envelope - DOCKER: docker container format - OVA: OVF package in a tarfile - OVF: OVF container format See 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:\n - AKI: a kernel image format\n - AMI: a machine image format\n - ARI: a ramdisk image format\n - ISO: an archive format for the data contents of an optical disc,\n such as CD-ROM\n - QCOW2: a common disk image format, which can expand dynamically\n and supports copy on write\n - RAW: an unstructured disk image format\n - VDI: a common disk image format\n - VHD: a common disk image format\n - VHDX: enhanced version of VHD format\n - VMDK: a common disk image format\nSee notes 2 and 3.\n",
+ "type": "string",
+ "enum": [
+ "AKI",
+ "AMI",
+ "ISO",
+ "QCOW2",
+ "RAW",
+ "VDI",
+ "VHD",
+ "VHDX",
+ "VMDK"
+ ]
+ },
+ "createdAt": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "minDisk": {
+ "description": "The minimal disk for this software image in bytes. See note 4.\n",
+ "type": "integer"
+ },
+ "minRam": {
+ "description": "The minimal RAM for this software image in bytes. See note 3.\n",
+ "type": "integer"
+ },
+ "size": {
+ "description": "Size of this software image in bytes.\n",
+ "type": "integer"
+ },
+ "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 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"
+ },
+ "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 \"/\". EXAMPLE: foo/bar/m%40ster.vhd For 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"
+ }
+ }
+ }
}
\ No newline at end of file
diff --git a/SOL003/VNFPackageManagement-API/schemas/userDefinedData.schema.json b/SOL003/VNFPackageManagement-API/schemas/userDefinedData.schema.json
index fa31850fc78a82427e55bceac29ccfbcd00e8a96..6e443e0ea61fc1a9b5334345c1d7bcd737b680be 100644
--- a/SOL003/VNFPackageManagement-API/schemas/userDefinedData.schema.json
+++ b/SOL003/VNFPackageManagement-API/schemas/userDefinedData.schema.json
@@ -1,4 +1,4 @@
{
- "description": "",
+ "description": "This 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"
}
\ No newline at end of file
diff --git a/SOL003/VNFPackageManagement-API/schemas/vnfPkgInfo.schema.json b/SOL003/VNFPackageManagement-API/schemas/vnfPkgInfo.schema.json
index 684c5f8347730e55963a353e9ea9d7a73cf6025b..caf8122e11d32a481cc591bb8be3456158f643c1 100644
--- a/SOL003/VNFPackageManagement-API/schemas/vnfPkgInfo.schema.json
+++ b/SOL003/VNFPackageManagement-API/schemas/vnfPkgInfo.schema.json
@@ -1,262 +1,293 @@
{
- "description": "This type represents the information of a VNF package. It shall comply with the provisions defined in table 10.5.2.2-1.\nNOTE 1:\tIf the value of the onboardingState attribute is not equal to \"ONBOARDED\", the value of the operationalState \n attribute shall be equal to \"DISABLED\".\nNOTE 2:\tIf the value of the onboardingState attribute is not equal to \"ONBOARDED\", the value of the usageState attribute \n shall be equal to \"NOT_IN_USE\".\nNOTE 3:\tETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on TOSCA specifications.\n",
- "type": "object",
- "required": ["id", "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"
- },
- "vnfProvider": {
- "description": "A string defined in IETF RFC 8259.\n",
- "type": "string"
- },
- "vnfProductName": {
- "description": "A string defined in IETF RFC 8259.\n",
- "type": "string"
- },
- "vnfSoftwareVersion": {
- "description": "A version.\n",
- "type": "string"
- },
- "vnfdVersion": {
- "description": "A version.\n",
- "type": "string"
- },
- "compatibleSpecificationVersions": {
- "description": "Indicates which versions of the ETSI GS NFV-SOL 004 specification the package complies to, as defined in the manifest of the package. Each entry shall be formatted as defined in clause 4.3.2 of ETSI GS NFV-SOL 004.\n",
- "type": "array",
- "items": {
- "description": "A version.\n",
- "type": "string"
- }
- },
- "checksum": {
- "description": "Cheksum description\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": "A string defined in IETF RFC 8259.\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. It shall comply with the provisions defined in table 10.5.3.2-1.\nNOTE 1:\tThe list of permitted values was taken from \"Container formats\" in OpenStack® documentation: \"Disk and container formats for images\"\n (Available at https://docs.openstack.org/glance/pike/user/formats.html).\nNOTE 2:\tThe list of permitted values was adapted from \"Disk formats\" in OpenStack® documentation: \"Disk and container formats for images\"\n (Available at https://docs.openstack.org/glance/pike/user/formats.html).\n",
- "type": "object",
- "required": ["id", "name", "provider", "version", "checksum", "isEncrypted", "containerFormat", "diskFormat", "createdAt", "minDisk", "minRam", "size"],
- "properties": {
- "id": {
- "description": "An identifier that is unique within a VNF descriptor.\n",
- "type": "string"
- },
- "name": {
- "description": "A string defined in IETF RFC 8259.\n",
- "type": "string"
- },
- "provider": {
- "description": "A string defined in IETF RFC 8259.\n",
- "type": "string"
- },
- "version": {
- "description": "A version.\n",
- "type": "string"
- },
- "checksum": {
- "description": "Cheksum description\n",
- "type": "string"
- },
- "isEncrypted": {
- "description": "The Boolean is a data type having two values (true and false).\n",
- "type": "boolean"
- },
- "containerFormat": {
- "description": "Container format indicates whether the software image is in a file format that also contains metadata about the actual software. Permitted values: - AKI: a kernel image format - AMI: a machine image format - ARI: a ramdisk image format - BARE: the image does not have a container or metadata envelope - DOCKER: docker container format - OVA: OVF package in a tarfile - OVF: OVF container format See 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\n- QCOW2: a common disk image format, which can expand dynamically and supports copy on write\n- 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 See note 2.\n",
- "type": "string",
- "enum": ["AKI", "AMI", "ISO", "QCOW2", "RAW", "VDI", "VHD", "VHDX", "VMDK"]
- },
- "createdAt": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "minDisk": {
- "description": "The minimal disk for this software image in bytes.\n",
- "type": "integer"
- },
- "minRam": {
- "description": "The minimal RAM for this software image in bytes.\n",
- "type": "integer"
- },
- "size": {
- "description": "Size of this software image in bytes.\n",
- "type": "integer"
- },
- "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 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"
- },
- "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 \"/\". EXAMPLE: foo/bar/m%40ster.vhd For 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"
- }
- }
- }
- },
- "additionalArtifacts": {
- "description": "Information about VNF package artifacts contained in the VNF package that are not software images. Every local and external artifact declared in the manifest shall be included, except the software images and the files that make up the parts of the VNFD (see clause 10.4.4.3.2). Signature files and certificate files are not considered as artifacts, however, the content of the \"Licenses\" and \"Testing\" directories in the VNF package is. This attribute shall not be present before the VNF package content is on-boarded. Otherwise, this attribute shall be present if the VNF package contains additional artifacts.\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.\n",
- "type": "object",
- "required": ["artifactPath", "checksum", "isEncrypted"],
- "properties": {
- "artifactPath": {
- "description": "A string defined in IETF RFC 8259.\n",
- "type": "string"
- },
- "artifactURI": {
- "description": "URI of the artifact as defined in the VNF package manifest. Shall be present if the artifact is external to the package and shall be absent otherwise.\nEXAMPLE: https://example.com/m%40ster.sh\n",
- "type": "array",
- "items": {
- "description": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- }
- },
- "checksum": {
- "description": "Cheksum description\n",
- "type": "string"
- },
- "isEncrypted": {
- "description": "The Boolean is a data type having two values (true and false).\n",
- "type": "boolean"
- },
- "nonManoArtifactSetId": {
- "description": "A string defined in IETF RFC 8259.\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.\nValid values: -\tHISTORY: a history artifact as per clause 4.3.3 in ETSI GS NFV-SOL 004 -\tTESTING: a testing artifact as per clause 4.3.4 in ETSI GS NFV-SOL 004 -\tLICENSE: 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 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"
- }
- }
- }
- },
- "onboardingState": {
- "description": "CREATED: The \"Individual VNF package\" resource has been created. UPLOADING: The associated VNF package content is being uploaded. PROCESSING: The associated VNF package content is being processed, e.g., validation.\nONBOARDED: The associated VNF package content has been on-boarded successfully. ERROR: There was an error during upload of the VNF package content or external artifacts, or during VNF package processing.\n",
- "type": "string",
- "enum": ["CREATED", "UPLOADING", "PROCESSING", "ONBOARDED", "ERROR"]
- },
- "operationalState": {
- "description": "- ENABLED: The VNF package is enabled, i.e. it can be used for the creation of new \"Individual VNF instance\" resources.\n- DISABLED: The VNF package is disabled, i.e. it shall not be used for the creation of further \"Individual VNF instance\" resources\n (unless and until the VNF package is re-enabled).\n",
- "type": "string",
- "enum": ["ENABLED", "DISABLED"]
- },
- "usageState": {
- "description": "- 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",
- "type": "string",
- "enum": ["IN_USE", "NOT_IN_USE"]
- },
- "vnfmInfo": {
- "description": "A string defined in IETF RFC 8259.\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 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"
- },
- "onboardingFailureDetails": {
- "description": "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 is reproduced inthis structure. Compared to the general framework defined in IETF RFC 7807, 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 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.\n",
- "type": "object",
- "required": ["status", "detail"],
- "properties": {
- "type": {
- "description": "A URI reference according to IETF RFC 3986 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"
- }
- }
- },
- "_links": {
- "description": "Links to resources related to this resource.\n",
- "type": "object",
- "required": ["self", "packageContent"],
- "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"
- }
- }
- },
- "vnfd": {
- "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"
- }
- }
- },
- "packageContent": {
- "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"
- }
- }
- }
- }
- }
- }
+ "description": "This type represents the information of a VNF package.\nNOTE 1:\tIf the value of the onboardingState attribute is not equal to \"ONBOARDED\", the value of the operationalState \n attribute shall be equal to \"DISABLED\".\nNOTE 2:\tIf the value of the onboardingState attribute is not equal to \"ONBOARDED\", the value of the usageState attribute \n shall be equal to \"NOT_IN_USE\".\nNOTE 3:\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": "A string defined in IETF RFC 8259.\n",
+ "type": "string"
+ },
+ "vnfProductName": {
+ "description": "A string defined in IETF RFC 8259.\n",
+ "type": "string"
+ },
+ "vnfSoftwareVersion": {
+ "description": "A version.\n",
+ "type": "string"
+ },
+ "vnfdVersion": {
+ "description": "A version.\n",
+ "type": "string"
+ },
+ "compatibleSpecificationVersions": {
+ "description": "Indicates which versions of the ETSI GS NFV-SOL 004 specification the package complies to, as defined in the manifest of the package. Each entry shall be formatted as defined in clause 4.3.2 of ETSI GS NFV-SOL 004.\n",
+ "type": "array",
+ "items": {
+ "description": "A version.\n",
+ "type": "string"
+ }
+ },
+ "checksum": {
+ "description": "Cheksum description\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": "A string defined in IETF RFC 8259.\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..\n* NOTE 1:\tThe list of permitted values was taken from \"Container formats\" in OpenStack® documentation: \"Disk and container formats for images\"\n (Available at https://docs.openstack.org/glance/pike/user/formats.html).\n* NOTE 2:\tThe list of permitted values was adapted from \"Disk formats\" in OpenStack® documentation: \"Disk and container formats for images\"\n (Available at https://docs.openstack.org/glance/pike/user/formats.html).\n* NOTE 3: The attribute shall be present for VM-based software images referenced from a Vdu, and shall be absent\n otherwise.\n* NOTE 4: The attribute shall be present for software images referenced from a VirtualStorageDesc, and shall be absent\n otherwise.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "name",
+ "provider",
+ "version",
+ "checksum",
+ "isEncrypted",
+ "containerFormat",
+ "createdAt",
+ "size"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "name": {
+ "description": "A string defined in IETF RFC 8259.\n",
+ "type": "string"
+ },
+ "provider": {
+ "description": "A string defined in IETF RFC 8259.\n",
+ "type": "string"
+ },
+ "version": {
+ "description": "A version.\n",
+ "type": "string"
+ },
+ "checksum": {
+ "description": "Cheksum description\n",
+ "type": "string"
+ },
+ "isEncrypted": {
+ "description": "The Boolean is a data type having two values (true and false).\n",
+ "type": "boolean"
+ },
+ "containerFormat": {
+ "description": "Container format indicates whether the software image is in a file format that also contains metadata about the actual software. Permitted values: - AKI: a kernel image format - AMI: a machine image format - ARI: a ramdisk image format - BARE: the image does not have a container or metadata envelope - DOCKER: docker container format - OVA: OVF package in a tarfile - OVF: OVF container format See 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:\n - AKI: a kernel image format\n - AMI: a machine image format\n - ARI: a ramdisk image format\n - ISO: an archive format for the data contents of an optical disc,\n such as CD-ROM\n - QCOW2: a common disk image format, which can expand dynamically\n and supports copy on write\n - RAW: an unstructured disk image format\n - VDI: a common disk image format\n - VHD: a common disk image format\n - VHDX: enhanced version of VHD format\n - VMDK: a common disk image format\nSee notes 2 and 3.\n",
+ "type": "string",
+ "enum": [
+ "AKI",
+ "AMI",
+ "ISO",
+ "QCOW2",
+ "RAW",
+ "VDI",
+ "VHD",
+ "VHDX",
+ "VMDK"
+ ]
+ },
+ "createdAt": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "minDisk": {
+ "description": "The minimal disk for this software image in bytes. See note 4.\n",
+ "type": "integer"
+ },
+ "minRam": {
+ "description": "The minimal RAM for this software image in bytes. See note 3.\n",
+ "type": "integer"
+ },
+ "size": {
+ "description": "Size of this software image in bytes.\n",
+ "type": "integer"
+ },
+ "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 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"
+ },
+ "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 \"/\". EXAMPLE: foo/bar/m%40ster.vhd For 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"
+ }
+ }
+ }
+ },
+ "additionalArtifacts": {
+ "description": "Information about VNF package artifacts contained in the VNF package that are not software images. Every local and external artifact declared in the manifest shall be included, except the software images and the files that make up the parts of the VNFD (see clause 10.4.4.3.2). Signature files and certificate files are not considered as artifacts, however, the content of the \"Licenses\" and \"Testing\" directories in the VNF package is. This attribute shall not be present before the VNF package content is on-boarded. Otherwise, this attribute shall be present if the VNF package contains additional artifacts.\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.\n",
+ "type": "object",
+ "required": ["artifactPath", "checksum", "isEncrypted"],
+ "properties": {
+ "artifactPath": {
+ "description": "A string defined in IETF RFC 8259.\n",
+ "type": "string"
+ },
+ "artifactURI": {
+ "description": "URI of the artifact as defined in the VNF package manifest. Shall be present if the artifact is external to the package and shall be absent otherwise.\nEXAMPLE: https://example.com/m%40ster.sh\n",
+ "type": "array",
+ "items": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ }
+ },
+ "checksum": {
+ "description": "Cheksum description\n",
+ "type": "string"
+ },
+ "isEncrypted": {
+ "description": "The Boolean is a data type having two values (true and false).\n",
+ "type": "boolean"
+ },
+ "nonManoArtifactSetId": {
+ "description": "A string defined in IETF RFC 8259.\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.\nValid values: -\tHISTORY: a history artifact as per clause 4.3.3 in ETSI GS NFV-SOL 004 -\tTESTING: a testing artifact as per clause 4.3.4 in ETSI GS NFV-SOL 004 -\tLICENSE: 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 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"
+ }
+ }
+ }
+ },
+ "onboardingState": {
+ "description": "CREATED: The \"Individual VNF package\" resource has been created. UPLOADING: The associated VNF package content is being uploaded. PROCESSING: The associated VNF package content is being processed, e.g.,\n validation.\nONBOARDED: The associated VNF package content has been on-boarded successfully. ERROR: There was an error during upload of the VNF package content or external\n artifacts, or during VNF package processing.\n",
+ "type": "string",
+ "enum": ["CREATED", "UPLOADING", "PROCESSING", "ONBOARDED", "ERROR"]
+ },
+ "operationalState": {
+ "description": "- ENABLED: The VNF package is enabled, i.e. it can be used for\n the creation of new \"Individual VNF instance\" resources.\n- DISABLED: The VNF package is disabled, i.e. it shall not be used for\n the creation of further \"Individual VNF instance\" resources\n (unless and until the VNF package is re-enabled).\n",
+ "type": "string",
+ "enum": ["ENABLED", "DISABLED"]
+ },
+ "usageState": {
+ "description": "- 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",
+ "type": "string",
+ "enum": ["IN_USE", "NOT_IN_USE"]
+ },
+ "vnfmInfo": {
+ "description": "A string defined in IETF RFC 8259.\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 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"
+ },
+ "onboardingFailureDetails": {
+ "description": "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 is reproduced inthis structure. Compared to the general framework defined in IETF RFC 7807, 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 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.\n",
+ "type": "object",
+ "required": ["status", "detail"],
+ "properties": {
+ "type": {
+ "description": "A URI reference according to IETF RFC 3986 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"
+ }
+ }
+ },
+ "_links": {
+ "description": "Links to resources related to this resource.\n",
+ "type": "object",
+ "required": ["self", "packageContent"],
+ "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"
+ }
+ }
+ },
+ "vnfd": {
+ "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"
+ }
+ }
+ },
+ "packageContent": {
+ "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"
+ }
+ }
+ }
+ }
+ }
+ }
}
\ No newline at end of file
diff --git a/SOL003/VNFPackageManagement-API/schemas/vnfPkgsInfo.schema.json b/SOL003/VNFPackageManagement-API/schemas/vnfPkgsInfo.schema.json
index 6977bc12b5bfb3244f89e04225f52bffe7a397ad..06ac70f4c9f7fd53f0b64ce336b35e26e3973441 100644
--- a/SOL003/VNFPackageManagement-API/schemas/vnfPkgsInfo.schema.json
+++ b/SOL003/VNFPackageManagement-API/schemas/vnfPkgsInfo.schema.json
@@ -1,265 +1,296 @@
{
- "type": "array",
- "items": {
- "description": "This type represents the information of a VNF package. It shall comply with the provisions defined in table 10.5.2.2-1.\nNOTE 1:\tIf the value of the onboardingState attribute is not equal to \"ONBOARDED\", the value of the operationalState \n attribute shall be equal to \"DISABLED\".\nNOTE 2:\tIf the value of the onboardingState attribute is not equal to \"ONBOARDED\", the value of the usageState attribute \n shall be equal to \"NOT_IN_USE\".\nNOTE 3:\tETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on TOSCA specifications.\n",
- "type": "object",
- "required": ["id", "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"
- },
- "vnfProvider": {
- "description": "A string defined in IETF RFC 8259.\n",
- "type": "string"
- },
- "vnfProductName": {
- "description": "A string defined in IETF RFC 8259.\n",
- "type": "string"
- },
- "vnfSoftwareVersion": {
- "description": "A version.\n",
- "type": "string"
- },
- "vnfdVersion": {
- "description": "A version.\n",
- "type": "string"
- },
- "compatibleSpecificationVersions": {
- "description": "Indicates which versions of the ETSI GS NFV-SOL 004 specification the package complies to, as defined in the manifest of the package. Each entry shall be formatted as defined in clause 4.3.2 of ETSI GS NFV-SOL 004.\n",
- "type": "array",
- "items": {
- "description": "A version.\n",
- "type": "string"
- }
- },
- "checksum": {
- "description": "Cheksum description\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": "A string defined in IETF RFC 8259.\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. It shall comply with the provisions defined in table 10.5.3.2-1.\nNOTE 1:\tThe list of permitted values was taken from \"Container formats\" in OpenStack® documentation: \"Disk and container formats for images\"\n (Available at https://docs.openstack.org/glance/pike/user/formats.html).\nNOTE 2:\tThe list of permitted values was adapted from \"Disk formats\" in OpenStack® documentation: \"Disk and container formats for images\"\n (Available at https://docs.openstack.org/glance/pike/user/formats.html).\n",
- "type": "object",
- "required": ["id", "name", "provider", "version", "checksum", "isEncrypted", "containerFormat", "diskFormat", "createdAt", "minDisk", "minRam", "size"],
- "properties": {
- "id": {
- "description": "An identifier that is unique within a VNF descriptor.\n",
- "type": "string"
- },
- "name": {
- "description": "A string defined in IETF RFC 8259.\n",
- "type": "string"
- },
- "provider": {
- "description": "A string defined in IETF RFC 8259.\n",
- "type": "string"
- },
- "version": {
- "description": "A version.\n",
- "type": "string"
- },
- "checksum": {
- "description": "Cheksum description\n",
- "type": "string"
- },
- "isEncrypted": {
- "description": "The Boolean is a data type having two values (true and false).\n",
- "type": "boolean"
- },
- "containerFormat": {
- "description": "Container format indicates whether the software image is in a file format that also contains metadata about the actual software. Permitted values: - AKI: a kernel image format - AMI: a machine image format - ARI: a ramdisk image format - BARE: the image does not have a container or metadata envelope - DOCKER: docker container format - OVA: OVF package in a tarfile - OVF: OVF container format See 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\n- QCOW2: a common disk image format, which can expand dynamically and supports copy on write\n- 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 See note 2.\n",
- "type": "string",
- "enum": ["AKI", "AMI", "ISO", "QCOW2", "RAW", "VDI", "VHD", "VHDX", "VMDK"]
- },
- "createdAt": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "minDisk": {
- "description": "The minimal disk for this software image in bytes.\n",
- "type": "integer"
- },
- "minRam": {
- "description": "The minimal RAM for this software image in bytes.\n",
- "type": "integer"
- },
- "size": {
- "description": "Size of this software image in bytes.\n",
- "type": "integer"
- },
- "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 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"
- },
- "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 \"/\". EXAMPLE: foo/bar/m%40ster.vhd For 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"
- }
- }
- }
- },
- "additionalArtifacts": {
- "description": "Information about VNF package artifacts contained in the VNF package that are not software images. Every local and external artifact declared in the manifest shall be included, except the software images and the files that make up the parts of the VNFD (see clause 10.4.4.3.2). Signature files and certificate files are not considered as artifacts, however, the content of the \"Licenses\" and \"Testing\" directories in the VNF package is. This attribute shall not be present before the VNF package content is on-boarded. Otherwise, this attribute shall be present if the VNF package contains additional artifacts.\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.\n",
- "type": "object",
- "required": ["artifactPath", "checksum", "isEncrypted"],
- "properties": {
- "artifactPath": {
- "description": "A string defined in IETF RFC 8259.\n",
- "type": "string"
- },
- "artifactURI": {
- "description": "URI of the artifact as defined in the VNF package manifest. Shall be present if the artifact is external to the package and shall be absent otherwise.\nEXAMPLE: https://example.com/m%40ster.sh\n",
- "type": "array",
- "items": {
- "description": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- }
- },
- "checksum": {
- "description": "Cheksum description\n",
- "type": "string"
- },
- "isEncrypted": {
- "description": "The Boolean is a data type having two values (true and false).\n",
- "type": "boolean"
- },
- "nonManoArtifactSetId": {
- "description": "A string defined in IETF RFC 8259.\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.\nValid values: -\tHISTORY: a history artifact as per clause 4.3.3 in ETSI GS NFV-SOL 004 -\tTESTING: a testing artifact as per clause 4.3.4 in ETSI GS NFV-SOL 004 -\tLICENSE: 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 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"
- }
- }
- }
- },
- "onboardingState": {
- "description": "CREATED: The \"Individual VNF package\" resource has been created. UPLOADING: The associated VNF package content is being uploaded. PROCESSING: The associated VNF package content is being processed, e.g., validation.\nONBOARDED: The associated VNF package content has been on-boarded successfully. ERROR: There was an error during upload of the VNF package content or external artifacts, or during VNF package processing.\n",
- "type": "string",
- "enum": ["CREATED", "UPLOADING", "PROCESSING", "ONBOARDED", "ERROR"]
- },
- "operationalState": {
- "description": "- ENABLED: The VNF package is enabled, i.e. it can be used for the creation of new \"Individual VNF instance\" resources.\n- DISABLED: The VNF package is disabled, i.e. it shall not be used for the creation of further \"Individual VNF instance\" resources\n (unless and until the VNF package is re-enabled).\n",
- "type": "string",
- "enum": ["ENABLED", "DISABLED"]
- },
- "usageState": {
- "description": "- 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",
- "type": "string",
- "enum": ["IN_USE", "NOT_IN_USE"]
- },
- "vnfmInfo": {
- "description": "A string defined in IETF RFC 8259.\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 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"
- },
- "onboardingFailureDetails": {
- "description": "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 is reproduced inthis structure. Compared to the general framework defined in IETF RFC 7807, 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 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.\n",
- "type": "object",
- "required": ["status", "detail"],
- "properties": {
- "type": {
- "description": "A URI reference according to IETF RFC 3986 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"
- }
- }
- },
- "_links": {
- "description": "Links to resources related to this resource.\n",
- "type": "object",
- "required": ["self", "packageContent"],
- "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"
- }
- }
- },
- "vnfd": {
- "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"
- }
- }
- },
- "packageContent": {
- "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"
- }
- }
- }
- }
- }
- }
- }
+ "type": "array",
+ "items": {
+ "description": "This type represents the information of a VNF package.\nNOTE 1:\tIf the value of the onboardingState attribute is not equal to \"ONBOARDED\", the value of the operationalState \n attribute shall be equal to \"DISABLED\".\nNOTE 2:\tIf the value of the onboardingState attribute is not equal to \"ONBOARDED\", the value of the usageState attribute \n shall be equal to \"NOT_IN_USE\".\nNOTE 3:\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": "A string defined in IETF RFC 8259.\n",
+ "type": "string"
+ },
+ "vnfProductName": {
+ "description": "A string defined in IETF RFC 8259.\n",
+ "type": "string"
+ },
+ "vnfSoftwareVersion": {
+ "description": "A version.\n",
+ "type": "string"
+ },
+ "vnfdVersion": {
+ "description": "A version.\n",
+ "type": "string"
+ },
+ "compatibleSpecificationVersions": {
+ "description": "Indicates which versions of the ETSI GS NFV-SOL 004 specification the package complies to, as defined in the manifest of the package. Each entry shall be formatted as defined in clause 4.3.2 of ETSI GS NFV-SOL 004.\n",
+ "type": "array",
+ "items": {
+ "description": "A version.\n",
+ "type": "string"
+ }
+ },
+ "checksum": {
+ "description": "Cheksum description\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": "A string defined in IETF RFC 8259.\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..\n* NOTE 1:\tThe list of permitted values was taken from \"Container formats\" in OpenStack® documentation: \"Disk and container formats for images\"\n (Available at https://docs.openstack.org/glance/pike/user/formats.html).\n* NOTE 2:\tThe list of permitted values was adapted from \"Disk formats\" in OpenStack® documentation: \"Disk and container formats for images\"\n (Available at https://docs.openstack.org/glance/pike/user/formats.html).\n* NOTE 3: The attribute shall be present for VM-based software images referenced from a Vdu, and shall be absent\n otherwise.\n* NOTE 4: The attribute shall be present for software images referenced from a VirtualStorageDesc, and shall be absent\n otherwise.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "name",
+ "provider",
+ "version",
+ "checksum",
+ "isEncrypted",
+ "containerFormat",
+ "createdAt",
+ "size"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier that is unique within a VNF descriptor.\n",
+ "type": "string"
+ },
+ "name": {
+ "description": "A string defined in IETF RFC 8259.\n",
+ "type": "string"
+ },
+ "provider": {
+ "description": "A string defined in IETF RFC 8259.\n",
+ "type": "string"
+ },
+ "version": {
+ "description": "A version.\n",
+ "type": "string"
+ },
+ "checksum": {
+ "description": "Cheksum description\n",
+ "type": "string"
+ },
+ "isEncrypted": {
+ "description": "The Boolean is a data type having two values (true and false).\n",
+ "type": "boolean"
+ },
+ "containerFormat": {
+ "description": "Container format indicates whether the software image is in a file format that also contains metadata about the actual software. Permitted values: - AKI: a kernel image format - AMI: a machine image format - ARI: a ramdisk image format - BARE: the image does not have a container or metadata envelope - DOCKER: docker container format - OVA: OVF package in a tarfile - OVF: OVF container format See 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:\n - AKI: a kernel image format\n - AMI: a machine image format\n - ARI: a ramdisk image format\n - ISO: an archive format for the data contents of an optical disc,\n such as CD-ROM\n - QCOW2: a common disk image format, which can expand dynamically\n and supports copy on write\n - RAW: an unstructured disk image format\n - VDI: a common disk image format\n - VHD: a common disk image format\n - VHDX: enhanced version of VHD format\n - VMDK: a common disk image format\nSee notes 2 and 3.\n",
+ "type": "string",
+ "enum": [
+ "AKI",
+ "AMI",
+ "ISO",
+ "QCOW2",
+ "RAW",
+ "VDI",
+ "VHD",
+ "VHDX",
+ "VMDK"
+ ]
+ },
+ "createdAt": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "minDisk": {
+ "description": "The minimal disk for this software image in bytes. See note 4.\n",
+ "type": "integer"
+ },
+ "minRam": {
+ "description": "The minimal RAM for this software image in bytes. See note 3.\n",
+ "type": "integer"
+ },
+ "size": {
+ "description": "Size of this software image in bytes.\n",
+ "type": "integer"
+ },
+ "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 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"
+ },
+ "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 \"/\". EXAMPLE: foo/bar/m%40ster.vhd For 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"
+ }
+ }
+ }
+ },
+ "additionalArtifacts": {
+ "description": "Information about VNF package artifacts contained in the VNF package that are not software images. Every local and external artifact declared in the manifest shall be included, except the software images and the files that make up the parts of the VNFD (see clause 10.4.4.3.2). Signature files and certificate files are not considered as artifacts, however, the content of the \"Licenses\" and \"Testing\" directories in the VNF package is. This attribute shall not be present before the VNF package content is on-boarded. Otherwise, this attribute shall be present if the VNF package contains additional artifacts.\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.\n",
+ "type": "object",
+ "required": ["artifactPath", "checksum", "isEncrypted"],
+ "properties": {
+ "artifactPath": {
+ "description": "A string defined in IETF RFC 8259.\n",
+ "type": "string"
+ },
+ "artifactURI": {
+ "description": "URI of the artifact as defined in the VNF package manifest. Shall be present if the artifact is external to the package and shall be absent otherwise.\nEXAMPLE: https://example.com/m%40ster.sh\n",
+ "type": "array",
+ "items": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ }
+ },
+ "checksum": {
+ "description": "Cheksum description\n",
+ "type": "string"
+ },
+ "isEncrypted": {
+ "description": "The Boolean is a data type having two values (true and false).\n",
+ "type": "boolean"
+ },
+ "nonManoArtifactSetId": {
+ "description": "A string defined in IETF RFC 8259.\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.\nValid values: -\tHISTORY: a history artifact as per clause 4.3.3 in ETSI GS NFV-SOL 004 -\tTESTING: a testing artifact as per clause 4.3.4 in ETSI GS NFV-SOL 004 -\tLICENSE: 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 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"
+ }
+ }
+ }
+ },
+ "onboardingState": {
+ "description": "CREATED: The \"Individual VNF package\" resource has been created. UPLOADING: The associated VNF package content is being uploaded. PROCESSING: The associated VNF package content is being processed, e.g.,\n validation.\nONBOARDED: The associated VNF package content has been on-boarded successfully. ERROR: There was an error during upload of the VNF package content or external\n artifacts, or during VNF package processing.\n",
+ "type": "string",
+ "enum": ["CREATED", "UPLOADING", "PROCESSING", "ONBOARDED", "ERROR"]
+ },
+ "operationalState": {
+ "description": "- ENABLED: The VNF package is enabled, i.e. it can be used for\n the creation of new \"Individual VNF instance\" resources.\n- DISABLED: The VNF package is disabled, i.e. it shall not be used for\n the creation of further \"Individual VNF instance\" resources\n (unless and until the VNF package is re-enabled).\n",
+ "type": "string",
+ "enum": ["ENABLED", "DISABLED"]
+ },
+ "usageState": {
+ "description": "- 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",
+ "type": "string",
+ "enum": ["IN_USE", "NOT_IN_USE"]
+ },
+ "vnfmInfo": {
+ "description": "A string defined in IETF RFC 8259.\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 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"
+ },
+ "onboardingFailureDetails": {
+ "description": "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 is reproduced inthis structure. Compared to the general framework defined in IETF RFC 7807, 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 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.\n",
+ "type": "object",
+ "required": ["status", "detail"],
+ "properties": {
+ "type": {
+ "description": "A URI reference according to IETF RFC 3986 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"
+ }
+ }
+ },
+ "_links": {
+ "description": "Links to resources related to this resource.\n",
+ "type": "object",
+ "required": ["self", "packageContent"],
+ "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"
+ }
+ }
+ },
+ "vnfd": {
+ "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"
+ }
+ }
+ },
+ "packageContent": {
+ "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"
+ }
+ }
+ }
+ }
+ }
+ }
+ }
}
\ No newline at end of file
diff --git a/SOL003/VNFPerformanceManagement-API/ApiVersion.robot b/SOL003/VNFPerformanceManagement-API/ApiVersion.robot
index 18203be32850493179f3712c391f041bad4d1c12..7ba80ff5d5a2fb1e44c154ef44fb296a9aa07f5f 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] v3.5.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.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 0b8228b07959abc73424e3e53fbae6961bd3fb1e..bf0539c59653436f31dafb14450c5a16713b210d 100644
--- a/SOL003/VNFPerformanceManagement-API/IndividualPmJob.robot
+++ b/SOL003/VNFPerformanceManagement-API/IndividualPmJob.robot
@@ -17,11 +17,12 @@ 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] v3.6.1
+ ... Reference: Clause 6.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
GET individual VNF Performance Job
+ Check HTTP Response Header Contains ETag and Last-Modified
Check HTTP Response Status Code Is 200
Check HTTP Response Body Json Schema Is PmJob
Check HTTP Response Body Pm Job Identifier matches the requested Pm Job
@@ -31,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] v3.6.1
+ ... Reference: Clause 6.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -44,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] v3.6.1
+ ... Reference: Clause 6.4.3.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: The VNF Performance Job is no more available in the VNFM
@@ -57,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] v3.6.1
+ ... Reference: Clause 6.4.3.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -70,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] v3.6.1
+ ... Reference: Clause 6.4.3.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -82,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] v3.6.1
+ ... Reference: Clause 6.4.3.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -94,11 +95,12 @@ 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] v3.6.1
+ ... Reference: Clause 6.4.3.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions:
Send Patch request for individual VNF Performance Job
+ Check HTTP Response Header Contains ETag and Last-Modified
Check HTTP Response Status Code Is 200
Check HTTP Response Body Json Schema Is PMJobModifications
@@ -107,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] v3.6.1
+ ... Reference: Clause 6.4.3.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: The VNF Performance Job is not modified by the operation
@@ -121,7 +123,7 @@ PATCH Individual VNF Performance Job - Unprocessable Entity
... Test title: PATCH Individual VNF Performance Job - Unprocessable Entity
... 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] v3.6.1
+ ... Reference: Clause 6.4.3.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -271,3 +273,10 @@ Check HTTP Response Body Json Schema Is
${schema} = Catenate SEPARATOR= ${input} .schema.json
Validate Json ${schema} ${response['body']}
Log Json Schema Validation OK
+
+Check HTTP Response Header Contains ETag and Last-Modified
+ Pass Execution If ${HEADER_TEST_SUPPORTED} == 0 Headers testing not supported. Skipping the Test.
+ Log ${response['headers']}
+ Should Contain ${response['headers']} Etag
+ Should Contain ${response['headers']} Last-Modified
+ Log Etag and Last-Modified Headers are present
\ No newline at end of file
diff --git a/SOL003/VNFPerformanceManagement-API/IndividualReport.robot b/SOL003/VNFPerformanceManagement-API/IndividualReport.robot
index d177070ee0d96b6b008084c42b189b6b1e47c510..7e01ef3e0dfa382c95e21014f196aa280620dfd2 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] v3.6.1
+ ... Reference: Clause 6.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.4.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.4.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.4.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.4.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.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 b9ce9c368758c8602707f2b5c2d017e39e2dd7ab..9b8b6ed44c8c72704d7489a64d89e25733a9f47a 100644
--- a/SOL003/VNFPerformanceManagement-API/IndividualThreshold.robot
+++ b/SOL003/VNFPerformanceManagement-API/IndividualThreshold.robot
@@ -17,12 +17,13 @@ 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] v3.6.1
+ ... Reference: Clause 6.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
GET individual VNF Performance Threshold
Check HTTP Response Status Code Is 200
+ Check HTTP Response Header Contains ETag and Last-Modified
Check HTTP Response Body Json Schema Is Threshold
Check HTTP Response Body Threshold Identifier matches the requested Threshold
@@ -31,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] v3.6.1
+ ... Reference: Clause 6.4.6.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -44,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] v3.6.1
+ ... Reference: Clause 6.4.6.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: The VNF Performance Threshold is not available anymore in the VNFM
@@ -57,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] v3.6.1
+ ... Reference: Clause 6.4.6.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -70,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] v3.6.1
+ ... Reference: Clause 6.4.6.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -82,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] v3.6.1
+ ... Reference: Clause 6.4.6.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -94,11 +95,12 @@ 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] v3.6.1
+ ... Reference: Clause 6.4.6.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions:
Send Patch request for individual VNF Performance Threshold
+ Check HTTP Response Header Contains ETag and Last-Modified
Check HTTP Response Status Code Is 200
Check HTTP Response Body Json Schema Is ThresholdModifications
@@ -107,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] v3.6.1
+ ... Reference: Clause 6.4.6.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -120,7 +122,7 @@ 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] v3.6.1
+ ... Reference: Clause 6.4.6.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -260,3 +262,10 @@ Check HTTP Response Body Json Schema Is
${schema} = Catenate SEPARATOR= ${input} .schema.json
Validate Json ${schema} ${response['body']}
Log Json Schema Validation OK
+
+Check HTTP Response Header Contains ETag and Last-Modified
+ Pass Execution If ${HEADER_TEST_SUPPORTED} == 0 Headers testing not supported. Skipping the Test.
+ Log ${response['headers']}
+ Should Contain ${response['headers']} Etag
+ Should Contain ${response['headers']} Last-Modified
+ Log Etag and Last-Modified Headers are present
diff --git a/SOL003/VNFPerformanceManagement-API/NotificationEndpoint.robot b/SOL003/VNFPerformanceManagement-API/NotificationEndpoint.robot
index bd73241f8962b7fd8a7d64d15df69d1f0c065243..9ff195f698d81f2400292282f099303c695a46ef 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] v3.6.1
+ ... Reference: Clause 6.4.9.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.9.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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 f8114e200d9e41bec1f0155f12312610dfb0105d..f31db000f2f36f0f9ccf167fec5224992d959ec8 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] v3.6.1
+ ... Reference: Clause 6.4.9.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.9.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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 765330c76705547c60361132017d447395281743..539649d2dee739dfc2feec3e82a3bb163ca77e87 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] v3.6.1
+ ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.2.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.2.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.2.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.2.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: The VNFM supports the use of fields and exclude_fields attribute selector
... Post-Conditions: none
@@ -230,7 +230,7 @@ POST Create new VNF Performance Monitoring Job - Unprocessable Entity
... Test title: POST Create new VNF Performance Monitoring Job - Unprocessable Entity
... 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] v3.6.1
+ ... Reference: clause 6.4.2.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFPerformanceManagement-API/Thresholds.robot b/SOL003/VNFPerformanceManagement-API/Thresholds.robot
index 821caefe7595b7a2c52e04615d3efc428a7371b1..ee0dca470d88e048e14363fedfa3a4f9e9ed8c6c 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] v3.6.1
+ ... Reference: Clause 6.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.5.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.5.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.5.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.5.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -147,7 +147,7 @@ POST create new Performance Threshold - Unprocessable Entity
... Test title: POST create new Performance Threshold - Unprocessable Entity
... 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] v3.6.1
+ ... Reference: Clause 6.4.5.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFPerformanceManagement-API/environment/variables.txt b/SOL003/VNFPerformanceManagement-API/environment/variables.txt
index 67a7c28a748b22832108b83cd2284e3b37e2d065..576c93a629c6415d35f5c006db03945ac44ab736 100644
--- a/SOL003/VNFPerformanceManagement-API/environment/variables.txt
+++ b/SOL003/VNFPerformanceManagement-API/environment/variables.txt
@@ -51,6 +51,7 @@ ${callback_endpoint_fwd} /endpoint/check
${notification_request} []
${notification_response} []
+${HEADER_TEST_SUPPORTED} 0
${POS_FILTER} objectInstanceIds=${objectInstanceIds}
${NEG_FILTER} criteriaPmJob=erroneousAttributeName
diff --git a/SOL003/VNFPerformanceManagement-API/jsons/CreatePmJobRequest.json b/SOL003/VNFPerformanceManagement-API/jsons/CreatePmJobRequest.json
index 8355d506b62d47dc9ca54307ecaa77d9c61ac53b..7b6f6acd5bebae707ab6759f4bd74f5574c613b9 100644
--- a/SOL003/VNFPerformanceManagement-API/jsons/CreatePmJobRequest.json
+++ b/SOL003/VNFPerformanceManagement-API/jsons/CreatePmJobRequest.json
@@ -1,4 +1,5 @@
{{
+ "objectType": "",
"objectInstanceIds" : ["{objectInstanceIds}"],
"criteria" : {{
"performanceMetric": [],
diff --git a/SOL003/VNFPerformanceManagement-API/jsons/CreateThresholdRequest.json b/SOL003/VNFPerformanceManagement-API/jsons/CreateThresholdRequest.json
index 9094634bc8e7501e62361a34a28cb42b37cb4ae6..9d9b56e264042398428036774d12ca0a59748b2a 100644
--- a/SOL003/VNFPerformanceManagement-API/jsons/CreateThresholdRequest.json
+++ b/SOL003/VNFPerformanceManagement-API/jsons/CreateThresholdRequest.json
@@ -1,4 +1,5 @@
{{
+ "objectType": "",
"objectInstanceIds" : "{objectInstanceIds}",
"criteria" : {{
"performanceMetric": "cpu_util",
diff --git a/SOL003/VNFPerformanceManagement-API/jsons/PerformanceInformationAvailableNotification.json b/SOL003/VNFPerformanceManagement-API/jsons/PerformanceInformationAvailableNotification.json
index cbe45fa78eb1068c0153b95e2ac7a74b90231019..736d1e2c79e8c92f1dc46ae359c1154cd7a4a66d 100644
--- a/SOL003/VNFPerformanceManagement-API/jsons/PerformanceInformationAvailableNotification.json
+++ b/SOL003/VNFPerformanceManagement-API/jsons/PerformanceInformationAvailableNotification.json
@@ -2,7 +2,9 @@
"id": "id",
"notificationType" : "PerformanceInformationAvailableNotification",
"subscriptionId ": "subscriptionId",
+ "pmJobId": "",
"timeStamp": "2012-04-21T18:25:43-05:00",
+ "objectType": "",
"objectInstanceId": "vnfID",
"_links": {
"subscription": "link to subscription",
diff --git a/SOL003/VNFPerformanceManagement-API/schemas/PerformanceInformationAvailableNotification.schema.json b/SOL003/VNFPerformanceManagement-API/schemas/PerformanceInformationAvailableNotification.schema.json
index 87a11368362a5b684b53e447c4182a29ad678c97..787029289845d028a590775503e07ea8ca5ebe4b 100644
--- a/SOL003/VNFPerformanceManagement-API/schemas/PerformanceInformationAvailableNotification.schema.json
+++ b/SOL003/VNFPerformanceManagement-API/schemas/PerformanceInformationAvailableNotification.schema.json
@@ -1,100 +1,89 @@
{
- "description": "This notification informs the receiver that performance information is available. The notification shall be triggered by the VNFM when new performance information collected by a PM job is available. The periodicity of triggering this notification is influenced by the \"reportingPeriod\" attribute in the \"PmJobCriteria\" data structure.\n",
- "type": "object",
- "required": [
- "id",
- "notificationType",
- "timeStamp",
- "pmJobId",
- "objectType",
- "objectInstanceId",
- "_links"
- ],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "notificationType": {
- "description": "Discriminator for the different notification types. Shall be set to \"PerformanceInformationAvailableNotification\" for this notification type.\n",
- "type": "string",
- "enum": [
- "PerformanceInformationAvailableNotification"
- ]
- },
- "timeStamp": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "pmJobId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "objectType": {
- "description": "Type of the measured object. The applicable measured object type for a measurement is defined in clause 7.2 of ETSI GS NFV-IFA 027.\n",
- "type": "string"
- },
- "objectInstanceId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "subObjectInstanceIds": {
- "description": "Identifiers of the sub-object instances of the measured object instance for which the measurements have been taken. Shall be present if the related PM job has been set up to measure only a subset of all sub-object instances of the measured object instance and a sub-object is defined in clause\n 6.2 of ETSI GS NFV-IFA 027 for the related measured object type.\nShall be absent 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"
- }
- },
- "_links": {
- "description": "Links to resources related to this notification.\n",
- "type": "object",
- "required": [
- "pmJob",
- "performanceReport"
- ],
- "properties": {
- "objectInstance": {
- "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": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- }
- }
- },
- "pmJob": {
- "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": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- }
- }
- },
- "performanceReport": {
- "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": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- }
- }
- }
- }
- }
- }
+ "description": "This notification informs the receiver that performance information is available. The notification shall be triggered by the VNFM when new performance information collected by a PM job is available. The periodicity of triggering this notification is influenced by the \"reportingPeriod\" attribute in the \"PmJobCriteria\" data structure.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "notificationType",
+ "timeStamp",
+ "pmJobId",
+ "objectType",
+ "objectInstanceId",
+ "_links"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "notificationType": {
+ "description": "Discriminator for the different notification types. Shall be set to \"PerformanceInformationAvailableNotification\" for this notification type.\n",
+ "type": "string",
+ "enum": ["PerformanceInformationAvailableNotification"]
+ },
+ "timeStamp": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "pmJobId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "objectType": {
+ "description": "Type of the measured object. The applicable measured object type for a measurement is defined in clause 7.2 of ETSI GS NFV-IFA 027.\n",
+ "type": "string"
+ },
+ "objectInstanceId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "subObjectInstanceIds": {
+ "description": "Identifiers of the sub-object instances of the measured object instance for which the measurements have been taken. Shall be present if the related PM job has been set up to measure only a subset of all sub-object instances of the measured object instance and a sub-object is defined in clause 6.2 of ETSI GS NFV-IFA 027 for the related measured object type. Shall be absent otherwise.\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"
+ }
+ },
+ "_links": {
+ "description": "Links to resources related to this notification.\n",
+ "type": "object",
+ "required": ["pmJob", "performanceReport"],
+ "properties": {
+ "objectInstance": {
+ "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": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ }
+ }
+ },
+ "pmJob": {
+ "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": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ }
+ }
+ },
+ "performanceReport": {
+ "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": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ }
+ }
+ }
+ }
+ }
+ }
}
\ No newline at end of file
diff --git a/SOL003/VNFPerformanceManagement-API/schemas/PerformanceReport.schema.json b/SOL003/VNFPerformanceManagement-API/schemas/PerformanceReport.schema.json
index c0a9c444eb6cf2ac6e2a8b8800cccc857683a336..3b560b3d19019e31237c15837963e3b40f207614 100644
--- a/SOL003/VNFPerformanceManagement-API/schemas/PerformanceReport.schema.json
+++ b/SOL003/VNFPerformanceManagement-API/schemas/PerformanceReport.schema.json
@@ -1 +1,61 @@
-{ "description": "This type defines the format of a performance report provided by the VNFM to the NFVO as a result of collecting performance information as part of a PM job.\n", "type": "object", "properties": { "entries": { "description": "List of performance information entries. Each performance report entry is for a given metric of a given object (i.e. VNF instance), but can include multiple collected values.\n", "type": "array", "items": { "type": "object", "required": [ "objectType", "objectInstanceId", "performanceMetric", "performanceValue" ], "properties": { "objectType": { "description": "Defines the object type for which performance information is reported (i.e. VNF type). The string value shall be set to the vnfdId of the VNF instance to which the performance information relates.\n", "type": "string" }, "objectInstanceId": { "description": "An identifier with the intention of being globally unique.\n", "type": "string" }, "performanceMetric": { "description": "Name of the metric collected.\n", "type": "string" }, "performanceValues": { "description": "List of performance values with associated timestamp.\n", "type": "array", "items": { "type": "object", "required": [ "timeStamp", "performanceValue" ], "properties": { "timeStamp": { "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n", "type": "string", "format": "date-time" }, "value": { "description": "Value of the metric collected. The type of the \"value\" attribute (i.e. scalar, structure (Object in JSON), or array (of scalars, arrays or structures / Objects)) is assumed to be defined in the external measurement specification (see ETSI GS NFV-IFA 027).\n", "type": "object" } } } } } } } }}
\ No newline at end of file
+{
+ "description": "This type defines the format of a performance report provided by the VNFM to the NFVO as a result of collecting performance information as part of a PM job.\nNOTE:\tThe sub-object allows to structure the measured object but is not to be confused with sub-counters which allow \n to structure the measurement value.\n\nEXAMPLE:\n Measured object: VnfInstanceXYZ\n Sub-object: VnfcInstance1\n Measurement: vCPU_utilization\n Sub-counters: vCPU utilization of each of the vCPUs of VnfcInstance1 (vCPU utilization.vCPU1, vCPU_utilization.vCPU2, etc.).\n",
+ "type": "object",
+ "required": ["entries"],
+ "properties": {
+ "entries": {
+ "description": "List of performance information entries. Each performance report entry is for a given metric of a given object (i.e. VNF instance), but can include multiple collected values.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": [
+ "objectType",
+ "objectInstanceId",
+ "performanceMetric",
+ "performanceValue"
+ ],
+ "properties": {
+ "objectType": {
+ "description": "Type of the measured object. The applicable measured object type for a measurement is defined in clause 7.2 of ETSI GS NFV-IFA 027.\n",
+ "type": "string"
+ },
+ "objectInstanceId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "subObjectInstanceId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "performanceMetric": {
+ "description": "Name of the metric collected. This attribute shall contain the related \"Measurement Name\" value as defined in clause 7.2 of ETSI GS NFV-IFA 027.\n",
+ "type": "string"
+ },
+ "performanceValues": {
+ "description": "List of performance values with associated timestamp.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": ["timeStamp", "value"],
+ "properties": {
+ "timeStamp": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "value": {
+ "description": "Value of the metric collected. The type of this attribute shall correspond to the related \"Measurement Unit\" as defined in clause 7.2. of ETSI GS NFV-IFA 027.\n",
+ "type": "object"
+ },
+ "context": {
+ "description": "This 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"
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+}
\ No newline at end of file
diff --git a/SOL003/VNFPerformanceManagement-API/schemas/PmJob.schema.json b/SOL003/VNFPerformanceManagement-API/schemas/PmJob.schema.json
index 65121412dcdc18bd63c0b3ddf837a3da8073a8d7..46be3313e35b372f4409bdf4b11874abea1c8201 100644
--- a/SOL003/VNFPerformanceManagement-API/schemas/PmJob.schema.json
+++ b/SOL003/VNFPerformanceManagement-API/schemas/PmJob.schema.json
@@ -1 +1,110 @@
-{ "description": "This type represents a PM job.\n", "type": "object", "required": [ "id", "objectInstanceIds", "criteria" ], "properties": { "id": { "description": "An identifier with the intention of being globally unique.\n", "type": "string" }, "objectInstanceIds": { "description": "Identifiers of the VNF instances for which performance information is collected.\n", "type": "array", "items": { "description": "An identifier with the intention of being globally unique.\n", "type": "string" } }, "criteria": { "description": "Criteria of the collection of performance information.\n", "type": "object", "required": [ "collectionPeriod", "reportingPeriod" ], "properties": { "performanceMetric": { "description": "This defines the types of performance metrics for the specified object instances, as specified in ETSI GS NFV-IFA 027). At least one of the two attributes (performance metric or group) shall be present.\n", "type": "array", "items": { "type": "string" } }, "performanceMetricGroup": { "description": "Group of performance metrics. A metric group is a pre-defined list of metrics, known to the producer that it can decompose to individual metrics. At least one of the two attributes (performance metric or group) shall be present.\n", "type": "array", "items": { "type": "string" } }, "collectionPeriod": { "description": "Specifies the periodicity at which the producer will collect performance information. The unit shall be seconds. At the end of each reportingPeriod, the producer will inform the consumer about availability of the performance data collected for each completed collection period during this reportingPeriod. The reportingPeriod should be equal to or a multiple of the collectionPeriod. In the latter case, the performance data for the collection periods within one reporting period are reported together.\n", "type": "integer" }, "reportingPeriod": { "description": "Specifies the periodicity at which the producer will report to the consumer. about performance information. The unit shall be seconds. At the end of each reportingPeriod, the producer will inform the consumer about availability of the performance data collected for each completed collection period during this reportingPeriod. The reportingPeriod should be equal to or a multiple of the collectionPeriod. In the latter case, the performance data for the collection periods within one reporting period are reported together.\n", "type": "integer" }, "reportingBoundary": { "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n", "type": "string", "format": "date-time" } } }, "reports": { "description": "Information about available reports collected by this PM job.\n", "type": "object", "required": [ "href", "readyTime", "_links" ], "properties": { "href": { "description": "The Uri where the report can be obtained.\n", "type": "string", "format": "url" }, "readyTime": { "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n", "type": "string", "format": "date-time" }, "expiryTime": { "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n", "type": "string", "format": "date-time" }, "fileSize": { "description": "The size of the report file in bytes, if known.\n", "type": "integer" }, "_links": { "description": "Links for 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 the referenced resource.\n", "type": "string", "format": "url" } } }, "objects": { "description": "Links to resources representing the VNF instances for which performance information is collected. Shall be present if the VNF instance information is accessible as a resource.\n", "type": "array", "items": { "description": "This type represents a link to a resource.\n", "type": "object", "required": [ "href" ], "properties": { "href": { "description": "URI of the referenced resource.\n", "type": "string", "format": "url" } } } } } } } } }}
\ No newline at end of file
+{
+ "description": "This type represents a PM job.\n",
+ "type": "object",
+ "required": ["id", "objectInstanceIds", "criteria"],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "objectInstanceIds": {
+ "description": "Identifiers of the VNF instances for which performance information is collected.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ },
+ "criteria": {
+ "description": "Criteria of the collection of performance information.\n",
+ "type": "object",
+ "required": ["collectionPeriod", "reportingPeriod"],
+ "properties": {
+ "performanceMetric": {
+ "description": "This defines the types of performance metrics for the specified object instances, as specified in ETSI GS NFV-IFA 027). At least one of the two attributes (performance metric or group) shall be present.\n",
+ "type": "array",
+ "items": { "type": "string" }
+ },
+ "performanceMetricGroup": {
+ "description": "Group of performance metrics. A metric group is a pre-defined list of metrics, known to the producer that it can decompose to individual metrics. At least one of the two attributes (performance metric or group) shall be present.\n",
+ "type": "array",
+ "items": { "type": "string" }
+ },
+ "collectionPeriod": {
+ "description": "Specifies the periodicity at which the producer will collect performance information. The unit shall be seconds. At the end of each reportingPeriod, the producer will inform the consumer about availability of the performance data collected for each completed collection period during this reportingPeriod. The reportingPeriod should be equal to or a multiple of the collectionPeriod. In the latter case, the performance data for the collection periods within one reporting period are reported together.\n",
+ "type": "integer"
+ },
+ "reportingPeriod": {
+ "description": "Specifies the periodicity at which the producer will report to the consumer. about performance information. The unit shall be seconds. At the end of each reportingPeriod, the producer will inform the consumer about availability of the performance data collected for each completed collection period during this reportingPeriod. The reportingPeriod should be equal to or a multiple of the collectionPeriod. In the latter case, the performance data for the collection periods within one reporting period are reported together.\n",
+ "type": "integer"
+ },
+ "reportingBoundary": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ }
+ }
+ },
+ "reports": {
+ "description": "Information about available reports collected by this PM job.\n",
+ "type": "object",
+ "required": ["href", "readyTime", "_links"],
+ "properties": {
+ "href": {
+ "description": "The Uri where the report can be obtained.\n",
+ "type": "string",
+ "format": "url"
+ },
+ "readyTime": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "expiryTime": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "fileSize": {
+ "description": "The size of the report file in bytes, if known.\n",
+ "type": "integer"
+ },
+ "_links": {
+ "description": "Links for 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 the referenced resource.\n",
+ "type": "string",
+ "format": "url"
+ }
+ }
+ },
+ "objects": {
+ "description": "Links to resources representing the VNF instances for which performance information is collected. Shall be present if the VNF instance information is accessible as a resource.\n",
+ "type": "array",
+ "items": {
+ "description": "This type represents a link to a resource.\n",
+ "type": "object",
+ "required": ["href"],
+ "properties": {
+ "href": {
+ "description": "URI of the referenced resource.\n",
+ "type": "string",
+ "format": "url"
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+}
diff --git a/SOL003/VNFPerformanceManagement-API/schemas/PmJobModifications.json b/SOL003/VNFPerformanceManagement-API/schemas/PmJobModifications.json
index 8da79dfe086b7699fbf73082692fb8873f62268d..bef4998095ea30bdd2bacf5e30fa95ac3769128f 100644
--- a/SOL003/VNFPerformanceManagement-API/schemas/PmJobModifications.json
+++ b/SOL003/VNFPerformanceManagement-API/schemas/PmJobModifications.json
@@ -1,62 +1,65 @@
{
- "description": "This type represents modifications to a PM job. It shall comply with the provisions defined in table 6.5.2.12-1.\n",
- "type": "object",
- "properties": {
- "callbackUri": {
- "description": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- },
- "authentication": {
- "type": "object",
- "required": [
- "authType"
- ],
- "properties": {
- "authType": {
- "description": "Defines the types of Authentication / Authorization which the API consumer is willing to accept when receiving a notification. Permitted values: * BASIC: In every HTTP request to the notification endpoint, use\n HTTP Basic authentication with the client credentials. \n* OAUTH2_CLIENT_CREDENTIALS: In every HTTP request to the\n notification endpoint, use an OAuth 2.0 Bearer token, obtained\n using the client credentials grant type.\n* TLS_CERT: Every HTTP request to the notification endpoint is sent\n over a mutually authenticated TLS session, i.e. not only the\n server is authenticated, but also the client is authenticated\n during the TLS tunnel setup.\n",
- "type": "array",
- "items": {
- "type": "string",
- "enum": [
- "BASIC",
- "OAUTH2_CLIENT_CREDENTIALS",
- "TLS_CERT"
- ]
- }
- },
- "paramsBasic": {
- "description": "Parameters for authentication/authorization using BASIC. Shall be present if authType is \"BASIC\" and the contained information has not been provisioned out of band. Shall be absent otherwise.\n",
- "type": "object",
- "properties": {
- "userName": {
- "description": "Username to be used in HTTP Basic authentication. Shall be present if it has not been provisioned out of band.\n",
- "type": "string"
- },
- "password": {
- "description": "Password to be used in HTTP Basic authentication. Shall be present if it has not been provisioned out of band.\n",
- "type": "string"
- }
+ "description": "This type represents modifications to a PM job.\nNOTE:\tAt least one of the attributes defined in this type shall be present in request bodies.\n",
+ "type": "object",
+ "oneOf": [
+ {
+ "required": ["callbackUri"]
+ },
+ {
+ "required": ["authentication"]
+ }
+ ],
+ "properties": {
+ "callbackUri": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ },
+ "authentication": {
+ "description": "* NOTE: The clientId and clientPassword passed in a subscription shall not be the same as the clientId and\n clientPassword that are used to obtain authorization for API requests. Client credentials may differ between\n subscriptions. The value of clientPassword should be generated by a random process\n",
+ "type": "object",
+ "required": ["authType"],
+ "properties": {
+ "authType": {
+ "description": "Defines the types of Authentication / Authorization which the API consumer is willing to accept when receiving a notification. Permitted values: * BASIC: In every HTTP request to the notification endpoint, use\n HTTP Basic authentication with the client credentials. \n* OAUTH2_CLIENT_CREDENTIALS: In every HTTP request to the\n notification endpoint, use an OAuth 2.0 Bearer token, obtained\n using the client credentials grant type.\n* TLS_CERT: Every HTTP request to the notification endpoint is sent\n over a mutually authenticated TLS session, i.e. not only the\n server is authenticated, but also the client is authenticated\n during the TLS tunnel setup.\n",
+ "type": "array",
+ "items": {
+ "type": "string",
+ "enum": ["BASIC", "OAUTH2_CLIENT_CREDENTIALS", "TLS_CERT"]
+ }
+ },
+ "paramsBasic": {
+ "description": "Parameters for authentication/authorization using BASIC. Shall be present if authType is \"BASIC\" and the contained information has not been provisioned out of band. Shall be absent otherwise.\n",
+ "type": "object",
+ "properties": {
+ "userName": {
+ "description": "Username to be used in HTTP Basic authentication. Shall be present if it has not been provisioned out of band.\n",
+ "type": "string"
+ },
+ "password": {
+ "description": "Password to be used in HTTP Basic authentication. Shall be present if it has not been provisioned out of band.\n",
+ "type": "string"
}
- },
- "paramsOauth2ClientCredentials": {
- "description": "Parameters for authentication/authorization using OAUTH2_CLIENT_CREDENTIALS. Shall be present if authType is \"OAUTH2_CLIENT_CREDENTIALS\" and the contained information has not been provisioned out of band. Shall be absent otherwise.\n",
- "type": "object",
- "properties": {
- "clientId": {
- "description": "Client identifier to be used in the access token request of the OAuth 2.0 client credentials grant type. Shall be present if it has not been provisioned out of band. The clientId and clientPassword passed in a subscription shall not be the same as the clientId and clientPassword that are used to obtain authorization for API requests. Client credentials may differ between subscriptions. The value of clientPassword should be generated by a random process.\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 be present if it has not been provisioned out of band. The clientId and clientPassword passed in a subscription shall not be the same as the clientId and clientPassword that are used to obtain authorization for API requests. Client credentials may differ between subscriptions. The value of clientPassword should be generated by a random process.\n",
- "type": "string"
- },
- "tokenEndpoint": {
- "description": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- }
+ }
+ },
+ "paramsOauth2ClientCredentials": {
+ "description": "Parameters for authentication/authorization using OAUTH2_CLIENT_CREDENTIALS. Shall be present if authType is \"OAUTH2_CLIENT_CREDENTIALS\" and the contained information has not been provisioned out of band. Shall be absent otherwise.\n",
+ "type": "object",
+ "properties": {
+ "clientId": {
+ "description": "Client identifier to be used in the access token request of the OAuth 2.0 client credentials grant type. Shall be present if it has not been provisioned out of band. See note.\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 be present if it has not been provisioned out of band. See note.\n",
+ "type": "string"
+ },
+ "tokenEndpoint": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
}
}
}
}
}
- }
\ No newline at end of file
+ }
+}
diff --git a/SOL003/VNFPerformanceManagement-API/schemas/PmJobs.schema.json b/SOL003/VNFPerformanceManagement-API/schemas/PmJobs.schema.json
index 654acdcf1f41f72b24464e32472a944bbf422120..51b0301944540165c615c468f89c7d3a58a5b29a 100644
--- a/SOL003/VNFPerformanceManagement-API/schemas/PmJobs.schema.json
+++ b/SOL003/VNFPerformanceManagement-API/schemas/PmJobs.schema.json
@@ -3,11 +3,7 @@
"items": {
"description": "This type represents a PM job.\n",
"type": "object",
- "required": [
- "id",
- "objectInstanceIds",
- "criteria"
- ],
+ "required": ["id", "objectInstanceIds", "criteria"],
"properties": {
"id": {
"description": "An identifier with the intention of being globally unique.\n",
@@ -24,24 +20,17 @@
"criteria": {
"description": "Criteria of the collection of performance information.\n",
"type": "object",
- "required": [
- "collectionPeriod",
- "reportingPeriod"
- ],
+ "required": ["collectionPeriod", "reportingPeriod"],
"properties": {
"performanceMetric": {
"description": "This defines the types of performance metrics for the specified object instances, as specified in ETSI GS NFV-IFA 027). At least one of the two attributes (performance metric or group) shall be present.\n",
"type": "array",
- "items": {
- "type": "string"
- }
+ "items": { "type": "string" }
},
"performanceMetricGroup": {
"description": "Group of performance metrics. A metric group is a pre-defined list of metrics, known to the producer that it can decompose to individual metrics. At least one of the two attributes (performance metric or group) shall be present.\n",
"type": "array",
- "items": {
- "type": "string"
- }
+ "items": { "type": "string" }
},
"collectionPeriod": {
"description": "Specifies the periodicity at which the producer will collect performance information. The unit shall be seconds. At the end of each reportingPeriod, the producer will inform the consumer about availability of the performance data collected for each completed collection period during this reportingPeriod. The reportingPeriod should be equal to or a multiple of the collectionPeriod. In the latter case, the performance data for the collection periods within one reporting period are reported together.\n",
@@ -61,11 +50,7 @@
"reports": {
"description": "Information about available reports collected by this PM job.\n",
"type": "object",
- "required": [
- "href",
- "readyTime",
- "_links"
- ],
+ "required": ["href", "readyTime", "_links"],
"properties": {
"href": {
"description": "The Uri where the report can be obtained.\n",
@@ -89,16 +74,12 @@
"_links": {
"description": "Links for this resource.\n",
"type": "object",
- "required": [
- "self"
- ],
+ "required": ["self"],
"properties": {
"self": {
"description": "This type represents a link to a resource.\n",
"type": "object",
- "required": [
- "href"
- ],
+ "required": ["href"],
"properties": {
"href": {
"description": "URI of the referenced resource.\n",
@@ -113,9 +94,7 @@
"items": {
"description": "This type represents a link to a resource.\n",
"type": "object",
- "required": [
- "href"
- ],
+ "required": ["href"],
"properties": {
"href": {
"description": "URI of the referenced resource.\n",
@@ -131,4 +110,4 @@
}
}
}
-}
\ No newline at end of file
+}
diff --git a/SOL003/VNFPerformanceManagement-API/schemas/Threshold.schema.json b/SOL003/VNFPerformanceManagement-API/schemas/Threshold.schema.json
index d3138727464e922b3a29c7a564406a68e16c869d..af5b3dfe8f6196bba77a377d80a2f852fdde3cd3 100644
--- a/SOL003/VNFPerformanceManagement-API/schemas/Threshold.schema.json
+++ b/SOL003/VNFPerformanceManagement-API/schemas/Threshold.schema.json
@@ -3,8 +3,10 @@
"type": "object",
"required": [
"id",
+ "objectType",
"objectInstanceId",
"criteria",
+ "callbackUri",
"_links"
],
"properties": {
@@ -12,72 +14,87 @@
"description": "An identifier with the intention of being globally unique.\n",
"type": "string"
},
+ "objectType": {
+ "description": "Type of the measured object. The applicable measured object type for a measurement is defined in clause 7.2 of ETSI GS NFV-IFA 027.\n",
+ "type": "string"
+ },
"objectInstanceId": {
"description": "An identifier with the intention of being globally unique.\n",
"type": "string"
},
+ "subObjectInstanceIds": {
+ "description": "Identifiers of the sub-object instances of the measured object instance associated with the threshold. May be present if a sub-object is defined in clause 6.2 of ETSI GS NFV-IFA 027 for the related measurement type. If this attribute is absent and a sub-object is defined in clause 6.2 of ETSI GS NFV-IFA 027 for the related measured object type, measurements will be taken for all sub-object instances of the measured object instance.\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"
+ }
+ },
"criteria": {
- "description": "This type represents criteria that define a threshold.\n",
+ "description": "This type represents criteria that define a threshold.\nNOTE 1:\tIn the present document, simple thresholds are defined. The definition of additional threshold types is left for \n future specification.\nNOTE 2:\tThe hysteresis is defined to prevent storms of threshold crossing notifications. When processing a request to create \n a threshold, implementations should enforce a suitable minimum value for this attribute (e.g. override the value or \n reject the request). \n",
"type": "object",
- "required": [
- "performanceMetric",
- "thresholdType"
- ],
+ "required": ["performanceMetric", "thresholdType"],
"properties": {
"performanceMetric": {
- "description": "Defines the performance metric associated with the threshold, as specified in ETSI GS NFV-IFA 027).\n",
+ "description": "Defines the performance metric associated with the threshold. Valid values are specified as \"Measurement Name\" values in clause 7.2 of ETSI GS NFV-IFA 027.\n",
"type": "string"
},
"thresholdType": {
- "description": "Type of threshold. This attribute determines which other attributes are present in the data structure. Permitted values: * SIMPLE: Single-valued static threshold In the present document, simple thresholds are defined. The definition of additional threshold types is left for future specification.\n",
+ "description": "Type of threshold. This attribute determines which other attributes are present in the data structure.\nPermitted values: -\tSIMPLE: Single-valued static threshold. See note 1.\n",
"type": "string",
- "enum": [
- "SIMPLE"
- ]
+ "enum": ["SIMPLE"]
},
"simpleThresholdDetails": {
"description": "Details of a simple threshold. Shall be present if thresholdType=\"SIMPLE\".\n",
"type": "object",
- "required": [
- "thresholdValue",
- "hysteresis"
- ],
+ "required": ["thresholdValue", "hysteresis"],
"properties": {
"thresholdValue": {
"description": "The threshold value. Shall be represented as a floating point number.\n",
- "type": "integer"
+ "type": "number",
+ "format": "float"
},
"hysteresis": {
- "description": "The hysteresis of the threshold. Shall be represented as a non-negative floating point number. A notification with crossing direction \"UP\" will be generated if the measured value reaches or exceeds \"thresholdValue\" + \"hysteresis\". A notification with crossing direction \"DOWN\" will be generated if the measured value reaches or undercuts \"thresholdValue\" - \"hysteresis\". The hysteresis is defined to prevent storms of threshold crossing notifications. When processing a request to create a threshold, implementations should enforce a suitable minimum value for this attribute (e.g. override the value or reject the request).\n",
- "type": "integer"
+ "description": "The hysteresis of the threshold. Shall be represented as a non-negative floating point number.\nA notification with crossing direction \"UP\" will be generated if the measured value reaches or exceeds \"thresholdValue\" + \"hysteresis\". A notification with crossing direction \"DOWN\" will be generated if the measured value reaches or undercuts \"thresholdValue\" - \"hysteresis\". See note 2.\n",
+ "type": "number",
+ "minimum": 0,
+ "maximum": 1024,
+ "format": "float"
}
}
}
}
},
+ "callbackUri": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ },
"_links": {
"description": "Links for this resource.\n",
"type": "object",
- "required": [
- "self"
- ],
+ "required": ["self"],
"properties": {
"self": {
- "description": "This type represents a link to a resource.\n",
+ "description": "This type represents a link to a resource using an absolute URI.\n",
"type": "object",
- "required": [
- "href"
- ],
+ "required": ["href"],
"properties": {
"href": {
- "description": "URI of the referenced resource.\n",
- "type": "string",
- "format": "url"
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
}
}
},
"object": {
- "description": "Link to a resource representing the VNF instance for which performance information is collected. Shall be present if the VNF instance information is accessible as a resource.\n"
+ "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"
+ }
+ }
}
}
}
diff --git a/SOL003/VNFPerformanceManagement-API/schemas/ThresholdCrossedNotification.schema.json b/SOL003/VNFPerformanceManagement-API/schemas/ThresholdCrossedNotification.schema.json
index e5cec2303f1bcfcfdb9df5affc9fc0767cd8a2c8..b0d99be61b3d6a4bf1337e43f1f401e66e088a67 100644
--- a/SOL003/VNFPerformanceManagement-API/schemas/ThresholdCrossedNotification.schema.json
+++ b/SOL003/VNFPerformanceManagement-API/schemas/ThresholdCrossedNotification.schema.json
@@ -1,113 +1,93 @@
{
- "description": "This type represents a notification that is sent when a threshold has been crossed. The notification shall be triggered by the VNFM when a threshold has been crossed.\n",
- "type": "object",
- "required": [
- "id",
- "notificationType",
- "subscriptionId",
- "timeStamp",
- "thresholdId",
- "crossingDirection",
- "objectInstanceId",
- "performanceMetric",
- "performanceValue",
- "_links"
- ],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "notificationType": {
- "description": "Discriminator for the different notification types. Shall be set to \"ThresholdCrossedNotification\" for this notification type.\n",
- "type": "string",
- "enum": [
- "ThresholdCrossedNotification"
- ]
- },
- "subscriptionId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "timeStamp": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "thresholdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "crossingDirection": {
- "type": "string",
- "enum": [
- "UP",
- "DOWN"
- ]
- },
- "objectInstanceId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "performanceMetric": {
- "description": "Performance metric associated with the threshold.\n",
- "type": "string"
- },
- "performanceValue": {
- "description": "Value of the metric that resulted in threshold crossing. The type of the \"performanceValue\" attribute (i.e. scalar, structure (Object in JSON), or array (of scalars, arrays or structures / Objects)) is assumed to be defined in the external measurement specification (see ETSI GS NFV-IFA 027).\n",
- "type": "object"
- },
- "_links": {
- "description": "Links to resources related to this notification.\n",
- "type": "object",
- "required": [
- "subscription",
- "threshold"
- ],
- "properties": {
- "subscription": {
- "description": "This type represents a link to a resource.\n",
- "type": "object",
- "required": [
- "href"
- ],
- "properties": {
- "href": {
- "description": "URI of the referenced resource.\n",
- "type": "string",
- "format": "url"
- }
+ "description": "This type represents a notification that is sent when a threshold has been crossed.\nNOTE:\tThe timing of sending this notification is determined by the capability of the \n producing entity to evaluate the threshold crossing condition.\n \nThe notification shall be triggered by the VNFM when a threshold has been crossed.\nNOTE:\tThe sub-object allows to structure the measured object, but is not to be confused \n with sub-counters which allow to structure the measurement.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "notificationType",
+ "timeStamp",
+ "thresholdId",
+ "crossingDirection",
+ "objectType",
+ "objectInstanceId",
+ "performanceMetric",
+ "performanceValue",
+ "_links"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "notificationType": {
+ "description": "Discriminator for the different notification types. Shall be set to \"ThresholdCrossedNotification\" for this notification type.\n",
+ "type": "string",
+ "enum": ["ThresholdCrossedNotification"]
+ },
+ "timeStamp": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "thresholdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "crossingDirection": {
+ "type": "string",
+ "enum": ["UP", "DOWN"]
+ },
+ "objectType": {
+ "description": "Type of the measured object. The applicable measured object type for a measurement is defined in clause 7.2 of ETSI GS NFV-IFA 027.\n",
+ "type": "string"
+ },
+ "objectInstanceId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "subObjectInstanceId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "performanceMetric": {
+ "description": "Performance metric associated with the threshold. This attribute shall contain the related \"Measurement Name\" value as defined in clause 7.2 of ETSI GS NFV-IFA 027.\n",
+ "type": "string"
+ },
+ "performanceValue": {
+ "description": "Value of the metric that resulted in threshold crossing. The type of this attribute shall correspond to the related \"Measurement Unit\" as defined in clause 7.2 of ETSI GS NFV-IFA 027.\n",
+ "type": "object"
+ },
+ "context": {
+ "description": "This 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"
+ },
+ "_links": {
+ "description": "Links to resources related to this notification.\n",
+ "type": "object",
+ "required": ["threshold"],
+ "properties": {
+ "objectInstance": {
+ "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": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
}
- },
- "objectInstance": {
- "description": "This type represents a link to a resource.\n",
- "type": "object",
- "required": [
- "href"
- ],
- "properties": {
- "href": {
- "description": "URI of the referenced resource.\n",
- "type": "string",
- "format": "url"
- }
- }
- },
- "threshold": {
- "description": "This type represents a link to a resource.\n",
- "type": "object",
- "required": [
- "href"
- ],
- "properties": {
- "href": {
- "description": "URI of the referenced resource.\n",
- "type": "string",
- "format": "url"
- }
+ }
+ },
+ "threshold": {
+ "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": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
}
}
}
}
}
- }
\ No newline at end of file
+ }
+}
\ No newline at end of file
diff --git a/SOL003/VNFPerformanceManagement-API/schemas/ThresholdModifications.json b/SOL003/VNFPerformanceManagement-API/schemas/ThresholdModifications.json
index 688bbfe8a750085ab4a6c64169fb2d8677fe67dd..7feaabf7e8cd4de687d45abd205a13641f4369ec 100644
--- a/SOL003/VNFPerformanceManagement-API/schemas/ThresholdModifications.json
+++ b/SOL003/VNFPerformanceManagement-API/schemas/ThresholdModifications.json
@@ -1,62 +1,65 @@
{
- "description": "This type represents modifications to a threshold. It shall comply with the provisions defined in table 6.5.2.11-1.\n",
- "type": "object",
- "properties": {
- "callbackUri": {
- "description": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- },
- "authentication": {
- "type": "object",
- "required": [
- "authType"
- ],
- "properties": {
- "authType": {
- "description": "Defines the types of Authentication / Authorization which the API consumer is willing to accept when receiving a notification. Permitted values: * BASIC: In every HTTP request to the notification endpoint, use\n HTTP Basic authentication with the client credentials. \n* OAUTH2_CLIENT_CREDENTIALS: In every HTTP request to the\n notification endpoint, use an OAuth 2.0 Bearer token, obtained\n using the client credentials grant type.\n* TLS_CERT: Every HTTP request to the notification endpoint is sent\n over a mutually authenticated TLS session, i.e. not only the\n server is authenticated, but also the client is authenticated\n during the TLS tunnel setup.\n",
- "type": "array",
- "items": {
- "type": "string",
- "enum": [
- "BASIC",
- "OAUTH2_CLIENT_CREDENTIALS",
- "TLS_CERT"
- ]
- }
- },
- "paramsBasic": {
- "description": "Parameters for authentication/authorization using BASIC. Shall be present if authType is \"BASIC\" and the contained information has not been provisioned out of band. Shall be absent otherwise.\n",
- "type": "object",
- "properties": {
- "userName": {
- "description": "Username to be used in HTTP Basic authentication. Shall be present if it has not been provisioned out of band.\n",
- "type": "string"
- },
- "password": {
- "description": "Password to be used in HTTP Basic authentication. Shall be present if it has not been provisioned out of band.\n",
- "type": "string"
- }
+ "description": "This type represents modifications to a threshold.\nNOTE:\tAt least one of the attributes defined in this type shall be present in request bodies.\n",
+ "type": "object",
+ "oneOf": [
+ {
+ "required": ["callbackUri"]
+ },
+ {
+ "required": ["authentication"]
+ }
+ ],
+ "properties": {
+ "callbackUri": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ },
+ "authentication": {
+ "description": "* NOTE: The clientId and clientPassword passed in a subscription shall not be the same as the clientId and\n clientPassword that are used to obtain authorization for API requests. Client credentials may differ between\n subscriptions. The value of clientPassword should be generated by a random process\n",
+ "type": "object",
+ "required": ["authType"],
+ "properties": {
+ "authType": {
+ "description": "Defines the types of Authentication / Authorization which the API consumer is willing to accept when receiving a notification. Permitted values: * BASIC: In every HTTP request to the notification endpoint, use\n HTTP Basic authentication with the client credentials. \n* OAUTH2_CLIENT_CREDENTIALS: In every HTTP request to the\n notification endpoint, use an OAuth 2.0 Bearer token, obtained\n using the client credentials grant type.\n* TLS_CERT: Every HTTP request to the notification endpoint is sent\n over a mutually authenticated TLS session, i.e. not only the\n server is authenticated, but also the client is authenticated\n during the TLS tunnel setup.\n",
+ "type": "array",
+ "items": {
+ "type": "string",
+ "enum": ["BASIC", "OAUTH2_CLIENT_CREDENTIALS", "TLS_CERT"]
+ }
+ },
+ "paramsBasic": {
+ "description": "Parameters for authentication/authorization using BASIC. Shall be present if authType is \"BASIC\" and the contained information has not been provisioned out of band. Shall be absent otherwise.\n",
+ "type": "object",
+ "properties": {
+ "userName": {
+ "description": "Username to be used in HTTP Basic authentication. Shall be present if it has not been provisioned out of band.\n",
+ "type": "string"
+ },
+ "password": {
+ "description": "Password to be used in HTTP Basic authentication. Shall be present if it has not been provisioned out of band.\n",
+ "type": "string"
}
- },
- "paramsOauth2ClientCredentials": {
- "description": "Parameters for authentication/authorization using OAUTH2_CLIENT_CREDENTIALS. Shall be present if authType is \"OAUTH2_CLIENT_CREDENTIALS\" and the contained information has not been provisioned out of band. Shall be absent otherwise.\n",
- "type": "object",
- "properties": {
- "clientId": {
- "description": "Client identifier to be used in the access token request of the OAuth 2.0 client credentials grant type. Shall be present if it has not been provisioned out of band. The clientId and clientPassword passed in a subscription shall not be the same as the clientId and clientPassword that are used to obtain authorization for API requests. Client credentials may differ between subscriptions. The value of clientPassword should be generated by a random process.\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 be present if it has not been provisioned out of band. The clientId and clientPassword passed in a subscription shall not be the same as the clientId and clientPassword that are used to obtain authorization for API requests. Client credentials may differ between subscriptions. The value of clientPassword should be generated by a random process.\n",
- "type": "string"
- },
- "tokenEndpoint": {
- "description": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- }
+ }
+ },
+ "paramsOauth2ClientCredentials": {
+ "description": "Parameters for authentication/authorization using OAUTH2_CLIENT_CREDENTIALS. Shall be present if authType is \"OAUTH2_CLIENT_CREDENTIALS\" and the contained information has not been provisioned out of band. Shall be absent otherwise.\n",
+ "type": "object",
+ "properties": {
+ "clientId": {
+ "description": "Client identifier to be used in the access token request of the OAuth 2.0 client credentials grant type. Shall be present if it has not been provisioned out of band. See note.\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 be present if it has not been provisioned out of band. See note.\n",
+ "type": "string"
+ },
+ "tokenEndpoint": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
}
}
}
}
}
- }
\ No newline at end of file
+ }
+}
diff --git a/SOL003/VNFPerformanceManagement-API/schemas/Thresholds.schema.json b/SOL003/VNFPerformanceManagement-API/schemas/Thresholds.schema.json
index 42ba2c0b089f920bf2a6dbfd87791b1fbefecd7f..7267757f21df060d7c12dd447b78f433ef847c49 100644
--- a/SOL003/VNFPerformanceManagement-API/schemas/Thresholds.schema.json
+++ b/SOL003/VNFPerformanceManagement-API/schemas/Thresholds.schema.json
@@ -5,8 +5,10 @@
"type": "object",
"required": [
"id",
+ "objectType",
"objectInstanceId",
"criteria",
+ "callbackUri",
"_links"
],
"properties": {
@@ -14,72 +16,87 @@
"description": "An identifier with the intention of being globally unique.\n",
"type": "string"
},
+ "objectType": {
+ "description": "Type of the measured object. The applicable measured object type for a measurement is defined in clause 7.2 of ETSI GS NFV-IFA 027.\n",
+ "type": "string"
+ },
"objectInstanceId": {
"description": "An identifier with the intention of being globally unique.\n",
"type": "string"
},
+ "subObjectInstanceIds": {
+ "description": "Identifiers of the sub-object instances of the measured object instance associated with the threshold. May be present if a sub-object is defined in clause 6.2 of ETSI GS NFV-IFA 027 for the related measurement type. If this attribute is absent and a sub-object is defined in clause 6.2 of ETSI GS NFV-IFA 027 for the related measured object type, measurements will be taken for all sub-object instances of the measured object instance.\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"
+ }
+ },
"criteria": {
- "description": "This type represents criteria that define a threshold.\n",
+ "description": "This type represents criteria that define a threshold.\nNOTE 1:\tIn the present document, simple thresholds are defined. The definition of additional threshold types is left for \n future specification.\nNOTE 2:\tThe hysteresis is defined to prevent storms of threshold crossing notifications. When processing a request to create \n a threshold, implementations should enforce a suitable minimum value for this attribute (e.g. override the value or \n reject the request). \n",
"type": "object",
- "required": [
- "performanceMetric",
- "thresholdType"
- ],
+ "required": ["performanceMetric", "thresholdType"],
"properties": {
"performanceMetric": {
- "description": "Defines the performance metric associated with the threshold, as specified in ETSI GS NFV-IFA 027).\n",
+ "description": "Defines the performance metric associated with the threshold. Valid values are specified as \"Measurement Name\" values in clause 7.2 of ETSI GS NFV-IFA 027.\n",
"type": "string"
},
"thresholdType": {
- "description": "Type of threshold. This attribute determines which other attributes are present in the data structure. Permitted values: * SIMPLE: Single-valued static threshold In the present document, simple thresholds are defined. The definition of additional threshold types is left for future specification.\n",
+ "description": "Type of threshold. This attribute determines which other attributes are present in the data structure.\nPermitted values: -\tSIMPLE: Single-valued static threshold. See note 1.\n",
"type": "string",
- "enum": [
- "SIMPLE"
- ]
+ "enum": ["SIMPLE"]
},
"simpleThresholdDetails": {
"description": "Details of a simple threshold. Shall be present if thresholdType=\"SIMPLE\".\n",
"type": "object",
- "required": [
- "thresholdValue",
- "hysteresis"
- ],
+ "required": ["thresholdValue", "hysteresis"],
"properties": {
"thresholdValue": {
"description": "The threshold value. Shall be represented as a floating point number.\n",
- "type": "integer"
+ "type": "number",
+ "format": "float"
},
"hysteresis": {
- "description": "The hysteresis of the threshold. Shall be represented as a non-negative floating point number. A notification with crossing direction \"UP\" will be generated if the measured value reaches or exceeds \"thresholdValue\" + \"hysteresis\". A notification with crossing direction \"DOWN\" will be generated if the measured value reaches or undercuts \"thresholdValue\" - \"hysteresis\". The hysteresis is defined to prevent storms of threshold crossing notifications. When processing a request to create a threshold, implementations should enforce a suitable minimum value for this attribute (e.g. override the value or reject the request).\n",
- "type": "integer"
+ "description": "The hysteresis of the threshold. Shall be represented as a non-negative floating point number.\nA notification with crossing direction \"UP\" will be generated if the measured value reaches or exceeds \"thresholdValue\" + \"hysteresis\". A notification with crossing direction \"DOWN\" will be generated if the measured value reaches or undercuts \"thresholdValue\" - \"hysteresis\". See note 2.\n",
+ "type": "number",
+ "minimum": 0,
+ "maximum": 1024,
+ "format": "float"
}
}
}
}
},
+ "callbackUri": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ },
"_links": {
"description": "Links for this resource.\n",
"type": "object",
- "required": [
- "self"
- ],
+ "required": ["self"],
"properties": {
"self": {
- "description": "This type represents a link to a resource.\n",
+ "description": "This type represents a link to a resource using an absolute URI.\n",
"type": "object",
- "required": [
- "href"
- ],
+ "required": ["href"],
"properties": {
"href": {
- "description": "URI of the referenced resource.\n",
- "type": "string",
- "format": "url"
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
}
}
},
"object": {
- "description": "Link to a resource representing the VNF instance for which performance information is collected. Shall be present if the VNF instance information is accessible as a resource.\n"
+ "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"
+ }
+ }
}
}
}
diff --git a/SOL003/VNFPerformanceManagement-API/schemas/criteria.schema.json b/SOL003/VNFPerformanceManagement-API/schemas/criteria.schema.json
index 319d15f53d4d49980a3c4c451bc82efd983abf36..047abc915903021566070156829fb1abddf7a8e3 100644
--- a/SOL003/VNFPerformanceManagement-API/schemas/criteria.schema.json
+++ b/SOL003/VNFPerformanceManagement-API/schemas/criteria.schema.json
@@ -1,34 +1,38 @@
{
- "description": "Criteria of the collection of performance information.\n",
- "type": "object",
- "required": ["collectionPeriod", "reportingPeriod"],
- "properties": {
- "performanceMetric": {
- "description": "This defines the types of performance metrics for the specified object instances, as specified in ETSI GS NFV-IFA 027). At least one of the two attributes (performance metric or group) shall be present.\n",
- "type": "array",
- "items": {
- "type": "string"
- }
- },
- "performanceMetricGroup": {
- "description": "Group of performance metrics. A metric group is a pre-defined list of metrics, known to the producer that it can decompose to individual metrics. At least one of the two attributes (performance metric or group) shall be present.\n",
- "type": "array",
- "items": {
- "type": "string"
- }
- },
- "collectionPeriod": {
- "description": "Specifies the periodicity at which the producer will collect performance information. The unit shall be seconds. At the end of each reportingPeriod, the producer will inform the consumer about availability of the performance data collected for each completed collection period during this reportingPeriod. The reportingPeriod should be equal to or a multiple of the collectionPeriod. In the latter case, the performance data for the collection periods within one reporting period are reported together.\n",
- "type": "integer"
- },
- "reportingPeriod": {
- "description": "Specifies the periodicity at which the producer will report to the consumer. about performance information. The unit shall be seconds. At the end of each reportingPeriod, the producer will inform the consumer about availability of the performance data collected for each completed collection period during this reportingPeriod. The reportingPeriod should be equal to or a multiple of the collectionPeriod. In the latter case, the performance data for the collection periods within one reporting period are reported together.\n",
- "type": "integer"
- },
- "reportingBoundary": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- }
- }
+ "description": "This type represents collection criteria for PM jobs.\nNOTE 1:\tAt the end of each reportingPeriod, the API producer will inform the API consumer about availability of the \n performance data collected for each completed collection period during this reportingPeriod. \n The reportingPeriod should be equal to or a multiple of the collectionPeriod. In the latter case, the performance \n data for the collection periods within one reporting period are reported together.\nNOTE 2:\tIn particular when choosing short collection and reporting periods, the number of PM jobs that can be supported \n depends on the capability of the producing entity.\n",
+ "type": "object",
+ "required": ["collectionPeriod", "reportingPeriod"],
+ "properties": {
+ "performanceMetric": {
+ "description": "This defines the types of performance metrics for the specified object instances. Valid values are specified as \"Measurement Name\" values in clause 7.2 of ETSI GS NFV-IFA 027. At least one of the two attributes (performance metric or group) shall be present.\n",
+ "type": "array",
+ "items": {
+ "type": "string"
+ }
+ },
+ "performanceMetricGroup": {
+ "description": "Group of performance metrics. A metric group is a pre-defined list of metrics, known to the API producer that it can decompose to individual metrics. Valid values are specified as \"Measurement Group\" values in clause 7.2 of ETSI GS NFV-IFA 027. At least one of the two attributes (performance metric or group) shall be present.\n",
+ "type": "array",
+ "items": {
+ "type": "string"
+ }
+ },
+ "collectionPeriod": {
+ "description": "Specifies the periodicity at which the API producer will collect performance information. The unit shall be seconds. See notes 1 and 2.\n",
+ "type": "integer",
+ "minimum": 0,
+ "maximum": 1024
+ },
+ "reportingPeriod": {
+ "description": "Specifies the periodicity at which the API producer will report to the API consumer about performance information. The unit shall be seconds. See notes 1 and 2.\n",
+ "type": "integer",
+ "minimum": 0,
+ "maximum": 1024
+ },
+ "reportingBoundary": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ }
+ }
}
\ No newline at end of file
diff --git a/SOL003/VNFPerformanceManagement-API/schemas/links.schema.json b/SOL003/VNFPerformanceManagement-API/schemas/links.schema.json
index ef262a8c875b5c00bf32d4fd6f279cc4d5965bc9..eb50dfa6bbad941c878553237572dd5916cef12f 100644
--- a/SOL003/VNFPerformanceManagement-API/schemas/links.schema.json
+++ b/SOL003/VNFPerformanceManagement-API/schemas/links.schema.json
@@ -1,35 +1,33 @@
{
- "description": "Links for 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 the referenced resource.\n",
- "type": "string",
- "format": "url"
- }
- }
- },
- "objects": {
- "description": "Links to resources representing the VNF instances for which performance information is collected. Shall be present if the VNF instance information is accessible as a resource.\n",
- "type": "array",
- "items": {
- "description": "This type represents a link to a resource.\n",
- "type": "object",
- "required": ["href"],
- "properties": {
- "href": {
- "description": "URI of the referenced resource.\n",
- "type": "string",
- "format": "url"
- }
- }
- }
- }
- }
+ "description": "Links for this resource.\n",
+ "type": "object",
+ "required": ["self"],
+ "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"
+ }
+ }
+ },
+ "objects": {
+ "description": "Links to resources representing the measure object instances for which performance information is collected. Shall be present if the measured object instance information is accessible as a resource.\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"
+ }
+ }
+ }
+ }
+ }
}
\ No newline at end of file
diff --git a/SOL003/VNFPerformanceManagement-API/schemas/reports.schema.json b/SOL003/VNFPerformanceManagement-API/schemas/reports.schema.json
index 834ded68723d9a72b3be565e72b71d5ef650e0cc..7a61c8fd7a78b4e20a900df6cec94874db8f6603 100644
--- a/SOL003/VNFPerformanceManagement-API/schemas/reports.schema.json
+++ b/SOL003/VNFPerformanceManagement-API/schemas/reports.schema.json
@@ -1,26 +1,28 @@
{
- "description": "Information about available reports collected by this PM job.\n",
- "type": "object",
- "required": ["href", "readyTime"],
- "properties": {
- "href": {
- "description": "The Uri where the report can be obtained.\n",
- "type": "string",
- "format": "url"
- },
- "readyTime": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "expiryTime": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "fileSize": {
- "description": "The size of the report file in bytes, if known.\n",
- "type": "integer"
- }
- }
-}
\ No newline at end of file
+ "description": "Information about available reports collected by this PM job.\n",
+ "type": "object",
+ "required": ["href", "readyTime"],
+ "properties": {
+ "href": {
+ "description": "The URI where the report can be obtained.\n",
+ "type": "string",
+ "format": "url"
+ },
+ "readyTime": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "expiryTime": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "fileSize": {
+ "description": "The size of the report file in bytes, if known.\n",
+ "type": "integer",
+ "minimum": 0,
+ "maximum": 1024
+ }
+ }
+}
diff --git a/SOL003/VNFSnapshotPackageManagement-API/ApiVersion.robot b/SOL003/VNFSnapshotPackageManagement-API/ApiVersion.robot
index c154290c5503748e0e3a8e83cd0526cdda9175a2..bec74efda5adb3a5e6a6625200cbddc39c303a7f 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] v3.5.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.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 fb9aec1e98c42d97fc6d5fe997fd6c9b61405732..8417e9265c8af9451aae0c2eab6b2430a2ccdcaf 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] v3.6.1
+ ... Reference: Clause 12.4.3.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 12.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 12.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 12.4.3.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 12.4.3.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 12.4.3.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.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 16edc7640322734b0c5f54f4d2d148905ca37f58..8dfa012839c420dde8eb2d347f9186fb18182a72 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] v3.6.1
+ ... Reference: Clause 12.4.5.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 12.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 12.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 12.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 12.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 12.4.5.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 12.4.5.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 12.4.5.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 12.4.5.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.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 e39a29f4bf8501308e65763dcc2850403c59ca26..96f55612fe8f5b39e3a0a334db3ac2b448b75192 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] v3.6.1
+ ... Reference: Clause 12.4.4.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 12.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 12.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 12.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 12.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 12.4.4.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 12.4.4.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 12.4.4.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 12.4.4.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.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 7bf125028e4039a68d0f275f97c752d4ce55497b..28e47facd7657c16b0c8cf59da0a4d7f87e2fa63 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] v3.6.1
+ ... Reference: Clause 12.4.2.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 12.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 12.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 12.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 12.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 12.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 12.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 12.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 12.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 12.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 12.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 12.4.2.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 12.4.2.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 12.4.2.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 12.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VNFSnapshotPackageManagement-API/schemas/VnfSnapshotPkgInfo.schema.json b/SOL003/VNFSnapshotPackageManagement-API/schemas/VnfSnapshotPkgInfo.schema.json
index 50b278a27b5f7596cb72aa301f3c904a995b39da..1bd9fcd8b7fa7979cfbb5e373ccbb52281a30302 100644
--- a/SOL003/VNFSnapshotPackageManagement-API/schemas/VnfSnapshotPkgInfo.schema.json
+++ b/SOL003/VNFSnapshotPackageManagement-API/schemas/VnfSnapshotPkgInfo.schema.json
@@ -1,273 +1,318 @@
{
- "description": "This type represents the information of a VNF snapshot package. It shall comply with the provisions defined in table 12.5.2.2-1.\nNOTE:\tThe attribute shall not be present before the VNF snapshot package content has been uploaded or built. Otherwise, this \n attribute shall be present unless it has been requested to be excluded per attribute selector.\n",
- "type": "object",
- "required": ["id", "name", "isFullSnapshot", "state", "isCancelPending", "_links"],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfSnapshotPkgUniqueId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "name": {
- "description": "A string defined in IETF RFC 8259.\n",
- "type": "string"
- },
- "checksum": {
- "description": "Cheksum description\n",
- "type": "string"
- },
- "createdAt": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "vnfSnapshotId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfcSnapshotInfoIds": {
- "description": "Identifiers of information held by the VNFM about specific VNFC snapshots part of the VNF snapshot and contained in the VNF snapshot package. This identifier is allocated by the VNFM during the VNF snapshot creation.\nSee note.\n",
- "type": "object",
- "items": {
- "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\n",
- "type": "string"
- }
- },
- "isFullSnapshot": {
- "description": "The Boolean is a data type having two values (true and false).\n",
- "type": "boolean"
- },
- "vnfdInfo": {
- "description": "This type represents the VNFD which is contained in a VNF snapshot package.\n",
- "type": "object",
- "required": ["avnfdId", "vnfdPath", "checksum", "isEncrypted"],
- "properties": {
- "avnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfdPath": {
- "description": "A string defined in IETF RFC 8259.\n",
- "type": "string"
- },
- "checksum": {
- "description": "Cheksum description\n",
- "type": "string"
- },
- "isEncrypted": {
- "description": "The Boolean is a data type having two values (true and false).\n",
- "type": "boolean"
- }
- }
- },
- "vnfsr": {
- "description": "This type represents the VNF snapshot record which is contained in a VNF snapshot package.\n",
- "type": "object",
- "required": ["recordPath", "checksum", "isEncrypted"],
- "properties": {
- "recordPath": {
- "description": "A string defined in IETF RFC 8259.\n",
- "type": "string"
- },
- "checksum": {
- "description": "Cheksum description\n",
- "type": "string"
- },
- "isEncrypted": {
- "description": "The Boolean is a data type having two values (true and false).\n",
- "type": "boolean"
- }
- }
- },
- "vnfcSnapshotImages": {
- "description": "Information about VNF snapshot artifacts that are VNFC snapshot images. Every local and external snapshot image shall be included. No other artifacts shall be included.\nSee note.\n",
- "type": "object",
- "items": {
- "description": "This type represents an artifact contained in a VNF snapshot package which represents a snapshot image. It shall comply with the provisions defined in table 12.5.3.2-1.\nNOTE 1:\tThe list of permitted values was taken from \"Container formats\" in OpenStack® documentation: \"Disk and container formats for images\"\n (Available at https://docs.openstack.org/glance/pike/user/formats.html).\nNOTE 2:\tThe list of permitted values was adapted from \"Disk formats\" in OpenStack® documentation: \"Disk and container formats for images\"\n (Available at https://docs.openstack.org/glance/pike/user/formats.html).\n",
- "type": "object",
- "required": ["id", "name", "checksum", "isEncrypted", "vnfcInstanceId", "containerFormat", "diskFormat", "createdAt", "minDisk", "minRam", "size"],
- "properties": {
- "id": {
- "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\n",
- "type": "string"
- },
- "name": {
- "description": "A string defined in IETF RFC 8259.\n",
- "type": "string"
- },
- "checksum": {
- "description": "Cheksum description\n",
- "type": "string"
- },
- "isEncrypted": {
- "description": "The Boolean is a data type having two values (true and false).\n",
- "type": "boolean"
- },
- "vnfcInstanceId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "containerFormat": {
- "description": "Container format indicates whether the snapshot image is in a file format that also contains metadata about the actual snapshot.\nPermitted values: - AKI: a kernel image format - AMI: a machine image format - ARI: a ramdisk image format - BARE: the image does not have a container or metadata envelope - DOCKER: docker container format - OVA: OVF package in a tarfile - OVF: OVF container format\nSee note 1.\n",
- "type": "string",
- "enum": ["AKI", "AMI", "ARI", "BARE", "DOCKER", "OVA", "OVF"]
- },
- "diskFormat": {
- "description": "Disk format of a snapshot image is the format of the underlying disk image.\nPermitted 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 to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "minDisk": {
- "description": "Unsigned integer number\n",
- "type": "integer",
- "minimum": 0
- },
- "minRam": {
- "description": "Unsigned integer number\n",
- "type": "integer",
- "minimum": 0
- },
- "size": {
- "description": "Unsigned integer number\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 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"
- },
- "imagePath": {
- "description": "A string defined in IETF RFC 8259.\n",
- "type": "string"
- },
- "imageUri": {
- "description": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- }
- }
- }
- },
- "additionalArtifacts": {
- "description": "Information about VNF snapshot artifacts that are not VNFC snapshot images.\nSee note.\n",
- "type": "object",
- "items": {
- "description": "This type represents an artifact other than a software image which is contained in a VNF snapshot package.\n",
- "type": "object",
- "required": ["checksum", "isEncrypted"],
- "properties": {
- "artifactPath": {
- "description": "A string defined in IETF RFC 8259.\n",
- "type": "string"
- },
- "artifactUri": {
- "description": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- },
- "checksum": {
- "description": "Cheksum description\n",
- "type": "string"
- },
- "isEncrypted": {
- "description": "The Boolean is a data type having two values (true and false).\n",
- "type": "boolean"
- },
- "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 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"
- }
- }
- }
- },
- "state": {
- "description": "State of the VNF snapshot package. Permitted values: - CREATED: the VNF snapshot package information has been created. - BUILDING: the VNF snapshot package is being built. - UPLOADING: the VNF snapshot package is being uploaded. - EXTRACTING: the VNF snapshot package’s content is being extracted. - AVAILABLE: the VNF snapshot package is available (i.e., build or upload is completed). - PROCESSING: the VNF snapshot is being processed. - ERROR: failure during the VNF snapshot package building, uploading or processing. - ERROR_EXTRACTING: failure during the VNF snapshot package extraction task.\n",
- "type": "string",
- "enum": ["CREATED", "BUILDING", "UPLOADING", "EXTRACTING", "AVAILABLE", "PROCESSING", "ERROR", "ERROR_EXTRACTING"]
- },
- "isCancelPending": {
- "description": "The Boolean is a data type having two values (true and false).\n",
- "type": "boolean"
- },
- "failureDetails": {
- "description": "Failure details associated to current error state of the VNF snapshot package state. If \"state\" is \"ERROR\" or \"ERROR_EXTRACTING\", this attribute shall be present unless it has been requested to be excluded via an attribute selector.\n",
- "type": "object",
- "required": ["errorType", "details"],
- "properties": {
- "errorType": {
- "description": "Type of error, when the failure happened (building, upload, processing, extracting).\nPermitted values: - BUILD_ERROR - UPLOAD_ERROR - PROCESS_ERROR - CANCELLED - EXTRACTION_ERROR\n",
- "type": "string",
- "enum": ["BUILD_ERROR", "UPLOAD_ERROR", "PROCESS_ERROR", "CANCELLED", "EXTRACTION_ERROR"]
- },
- "details": {
- "description": "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 is reproduced inthis structure. Compared to the general framework defined in IETF RFC 7807, 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 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.\n",
- "type": "object",
- "required": ["status", "detail"],
- "properties": {
- "type": {
- "description": "A URI reference according to IETF RFC 3986 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"
- }
- }
- }
- }
- },
- "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 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"
- },
- "_links": {
- "description": "Links to resources related to this resource.\n",
- "type": "object",
- "required": ["self", "packageContent"],
- "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"
- }
- }
- },
- "packageContent": {
- "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"
- }
- }
- }
- }
- }
- }
+ "description": "This type represents the information of a VNF snapshot package.\nNOTE:\tThe attribute shall not be present before the VNF snapshot package content has been uploaded or built.\n Otherwise, this attribute shall be present unless it has been requested to be excluded per attribute selector.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "name",
+ "isFullSnapshot",
+ "state",
+ "isCancelPending",
+ "_links"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfSnapshotPkgUniqueId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "name": {
+ "description": "A string defined in IETF RFC 8259.\n",
+ "type": "string"
+ },
+ "checksum": {
+ "description": "Cheksum description\n",
+ "type": "string"
+ },
+ "createdAt": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "vnfSnapshotId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfcSnapshotInfoIds": {
+ "description": "Identifiers of information held by the VNFM about specific VNFC snapshots part of the VNF snapshot and contained in the VNF snapshot package. This identifier is allocated by the VNFM during the VNF snapshot creation.\nSee note.\n",
+ "type": "object",
+ "items": {
+ "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\n",
+ "type": "string"
+ }
+ },
+ "isFullSnapshot": {
+ "description": "The Boolean is a data type having two values (true and false).\n",
+ "type": "boolean"
+ },
+ "vnfdInfo": {
+ "description": "This type represents the VNFD which is contained in a VNF snapshot package.\n",
+ "type": "object",
+ "required": ["avnfdId", "vnfdPath", "checksum", "isEncrypted"],
+ "properties": {
+ "avnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfdPath": {
+ "description": "A string defined in IETF RFC 8259.\n",
+ "type": "string"
+ },
+ "checksum": {
+ "description": "Cheksum description\n",
+ "type": "string"
+ },
+ "isEncrypted": {
+ "description": "The Boolean is a data type having two values (true and false).\n",
+ "type": "boolean"
+ }
+ }
+ },
+ "vnfsr": {
+ "description": "This type represents the VNF snapshot record which is contained in a VNF snapshot package.\n",
+ "type": "object",
+ "required": ["recordPath", "checksum", "isEncrypted"],
+ "properties": {
+ "recordPath": {
+ "description": "A string defined in IETF RFC 8259.\n",
+ "type": "string"
+ },
+ "checksum": {
+ "description": "Cheksum description\n",
+ "type": "string"
+ },
+ "isEncrypted": {
+ "description": "The Boolean is a data type having two values (true and false).\n",
+ "type": "boolean"
+ }
+ }
+ },
+ "vnfcSnapshotImages": {
+ "description": "Information about VNF snapshot artifacts that are VNFC snapshot images. Every local and external snapshot image shall be included. No other artifacts shall be included.\nSee note.\n",
+ "type": "object",
+ "items": {
+ "description": "This type represents an artifact contained in a VNF snapshot package which represents a snapshot image.\nNOTE 1:\tThe list of permitted values was taken from \"Container formats\" in OpenStack® documentation: \"Disk and container formats for images\"\n (Available at https://docs.openstack.org/glance/pike/user/formats.html).\nNOTE 2:\tThe list of permitted values was adapted from \"Disk formats\" in OpenStack® documentation: \"Disk and container formats for images\"\n (Available at https://docs.openstack.org/glance/pike/user/formats.html).\n",
+ "type": "object",
+ "required": [
+ "id",
+ "name",
+ "checksum",
+ "isEncrypted",
+ "vnfcInstanceId",
+ "containerFormat",
+ "diskFormat",
+ "createdAt",
+ "minDisk",
+ "minRam",
+ "size"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "name": {
+ "description": "A string defined in IETF RFC 8259.\n",
+ "type": "string"
+ },
+ "checksum": {
+ "description": "Cheksum description\n",
+ "type": "string"
+ },
+ "isEncrypted": {
+ "description": "The Boolean is a data type having two values (true and false).\n",
+ "type": "boolean"
+ },
+ "vnfcInstanceId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "containerFormat": {
+ "description": "Container format indicates whether the snapshot image is in a file format that also contains metadata about the actual snapshot.\nPermitted values: - AKI: a kernel image format - AMI: a machine image format - ARI: a ramdisk image format - BARE: the image does not have a container or metadata envelope - DOCKER: docker container format - OVA: OVF package in a tarfile - OVF: OVF container format\nSee note 1.\n",
+ "type": "string",
+ "enum": ["AKI", "AMI", "ARI", "BARE", "DOCKER", "OVA", "OVF"]
+ },
+ "diskFormat": {
+ "description": "Disk format of a snapshot image is the format of the underlying disk image.\nPermitted 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 to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "minDisk": {
+ "description": "Unsigned integer number\n",
+ "type": "integer",
+ "minimum": 0
+ },
+ "minRam": {
+ "description": "Unsigned integer number\n",
+ "type": "integer",
+ "minimum": 0
+ },
+ "size": {
+ "description": "Unsigned integer number\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 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"
+ },
+ "imagePath": {
+ "description": "A string defined in IETF RFC 8259.\n",
+ "type": "string"
+ },
+ "imageUri": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "additionalArtifacts": {
+ "description": "Information about VNF snapshot artifacts that are not VNFC snapshot images.\nSee note.\n",
+ "type": "object",
+ "items": {
+ "description": "This type represents an artifact other than a software image which is contained in a VNF snapshot package.\n",
+ "type": "object",
+ "required": ["checksum", "isEncrypted"],
+ "properties": {
+ "artifactPath": {
+ "description": "A string defined in IETF RFC 8259.\n",
+ "type": "string"
+ },
+ "artifactUri": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ },
+ "checksum": {
+ "description": "Cheksum description\n",
+ "type": "string"
+ },
+ "isEncrypted": {
+ "description": "The Boolean is a data type having two values (true and false).\n",
+ "type": "boolean"
+ },
+ "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 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"
+ }
+ }
+ }
+ },
+ "state": {
+ "description": "State of the VNF snapshot package. Permitted values: - CREATED: the VNF snapshot package information has been created. - BUILDING: the VNF snapshot package is being built. - UPLOADING: the VNF snapshot package is being uploaded. - EXTRACTING: the VNF snapshot package’s content is being extracted. - AVAILABLE: the VNF snapshot package is available (i.e., build or upload is completed). - PROCESSING: the VNF snapshot is being processed. - ERROR: failure during the VNF snapshot package building, uploading or processing. - ERROR_EXTRACTING: failure during the VNF snapshot package extraction task.\n",
+ "type": "string",
+ "enum": [
+ "CREATED",
+ "BUILDING",
+ "UPLOADING",
+ "EXTRACTING",
+ "AVAILABLE",
+ "PROCESSING",
+ "ERROR",
+ "ERROR_EXTRACTING"
+ ]
+ },
+ "isCancelPending": {
+ "description": "The Boolean is a data type having two values (true and false).\n",
+ "type": "boolean"
+ },
+ "failureDetails": {
+ "description": "Failure details associated to current error state of the VNF snapshot package state. If \"state\" is \"ERROR\" or \"ERROR_EXTRACTING\", this attribute shall be present unless it has been requested to be excluded via an attribute selector.\n",
+ "type": "object",
+ "required": ["errorType", "details"],
+ "properties": {
+ "errorType": {
+ "description": "Type of error, when the failure happened (building, upload, processing, extracting).\nPermitted values: - BUILD_ERROR - UPLOAD_ERROR - PROCESS_ERROR - CANCELLED - EXTRACTION_ERROR\n",
+ "type": "string",
+ "enum": [
+ "BUILD_ERROR",
+ "UPLOAD_ERROR",
+ "PROCESS_ERROR",
+ "CANCELLED",
+ "EXTRACTION_ERROR"
+ ]
+ },
+ "details": {
+ "description": "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 is reproduced inthis structure. Compared to the general framework defined in IETF RFC 7807, 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 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.\n",
+ "type": "object",
+ "required": ["status", "detail"],
+ "properties": {
+ "type": {
+ "description": "A URI reference according to IETF RFC 3986 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"
+ }
+ }
+ }
+ }
+ },
+ "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 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"
+ },
+ "_links": {
+ "description": "Links to resources related to this resource.\n",
+ "type": "object",
+ "required": ["self", "packageContent"],
+ "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"
+ }
+ }
+ },
+ "packageContent": {
+ "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"
+ }
+ }
+ }
+ }
+ }
+ }
}
\ No newline at end of file
diff --git a/SOL003/VNFSnapshotPackageManagement-API/schemas/VnfSnapshotPkgInfos.schema.json b/SOL003/VNFSnapshotPackageManagement-API/schemas/VnfSnapshotPkgInfos.schema.json
index 4f0ece55b3dfb54bc2f5ae2b44e591b169002439..cafc038a0fc80faa3eb4b48588d0c399175c07fe 100644
--- a/SOL003/VNFSnapshotPackageManagement-API/schemas/VnfSnapshotPkgInfos.schema.json
+++ b/SOL003/VNFSnapshotPackageManagement-API/schemas/VnfSnapshotPkgInfos.schema.json
@@ -1,276 +1,321 @@
{
- "type": "array",
- "items": {
- "description": "This type represents the information of a VNF snapshot package. It shall comply with the provisions defined in table 12.5.2.2-1.\nNOTE:\tThe attribute shall not be present before the VNF snapshot package content has been uploaded or built. Otherwise, this \n attribute shall be present unless it has been requested to be excluded per attribute selector.\n",
- "type": "object",
- "required": ["id", "name", "isFullSnapshot", "state", "isCancelPending", "_links"],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfSnapshotPkgUniqueId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "name": {
- "description": "A string defined in IETF RFC 8259.\n",
- "type": "string"
- },
- "checksum": {
- "description": "Cheksum description\n",
- "type": "string"
- },
- "createdAt": {
- "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "vnfSnapshotId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfcSnapshotInfoIds": {
- "description": "Identifiers of information held by the VNFM about specific VNFC snapshots part of the VNF snapshot and contained in the VNF snapshot package. This identifier is allocated by the VNFM during the VNF snapshot creation.\nSee note.\n",
- "type": "object",
- "items": {
- "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\n",
- "type": "string"
- }
- },
- "isFullSnapshot": {
- "description": "The Boolean is a data type having two values (true and false).\n",
- "type": "boolean"
- },
- "vnfdInfo": {
- "description": "This type represents the VNFD which is contained in a VNF snapshot package.\n",
- "type": "object",
- "required": ["avnfdId", "vnfdPath", "checksum", "isEncrypted"],
- "properties": {
- "avnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfdPath": {
- "description": "A string defined in IETF RFC 8259.\n",
- "type": "string"
- },
- "checksum": {
- "description": "Cheksum description\n",
- "type": "string"
- },
- "isEncrypted": {
- "description": "The Boolean is a data type having two values (true and false).\n",
- "type": "boolean"
- }
- }
- },
- "vnfsr": {
- "description": "This type represents the VNF snapshot record which is contained in a VNF snapshot package.\n",
- "type": "object",
- "required": ["recordPath", "checksum", "isEncrypted"],
- "properties": {
- "recordPath": {
- "description": "A string defined in IETF RFC 8259.\n",
- "type": "string"
- },
- "checksum": {
- "description": "Cheksum description\n",
- "type": "string"
- },
- "isEncrypted": {
- "description": "The Boolean is a data type having two values (true and false).\n",
- "type": "boolean"
- }
- }
- },
- "vnfcSnapshotImages": {
- "description": "Information about VNF snapshot artifacts that are VNFC snapshot images. Every local and external snapshot image shall be included. No other artifacts shall be included.\nSee note.\n",
- "type": "object",
- "items": {
- "description": "This type represents an artifact contained in a VNF snapshot package which represents a snapshot image. It shall comply with the provisions defined in table 12.5.3.2-1.\nNOTE 1:\tThe list of permitted values was taken from \"Container formats\" in OpenStack® documentation: \"Disk and container formats for images\"\n (Available at https://docs.openstack.org/glance/pike/user/formats.html).\nNOTE 2:\tThe list of permitted values was adapted from \"Disk formats\" in OpenStack® documentation: \"Disk and container formats for images\"\n (Available at https://docs.openstack.org/glance/pike/user/formats.html).\n",
- "type": "object",
- "required": ["id", "name", "checksum", "isEncrypted", "vnfcInstanceId", "containerFormat", "diskFormat", "createdAt", "minDisk", "minRam", "size"],
- "properties": {
- "id": {
- "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\n",
- "type": "string"
- },
- "name": {
- "description": "A string defined in IETF RFC 8259.\n",
- "type": "string"
- },
- "checksum": {
- "description": "Cheksum description\n",
- "type": "string"
- },
- "isEncrypted": {
- "description": "The Boolean is a data type having two values (true and false).\n",
- "type": "boolean"
- },
- "vnfcInstanceId": {
- "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
- "type": "string"
- },
- "containerFormat": {
- "description": "Container format indicates whether the snapshot image is in a file format that also contains metadata about the actual snapshot.\nPermitted values: - AKI: a kernel image format - AMI: a machine image format - ARI: a ramdisk image format - BARE: the image does not have a container or metadata envelope - DOCKER: docker container format - OVA: OVF package in a tarfile - OVF: OVF container format\nSee note 1.\n",
- "type": "string",
- "enum": ["AKI", "AMI", "ARI", "BARE", "DOCKER", "OVA", "OVF"]
- },
- "diskFormat": {
- "description": "Disk format of a snapshot image is the format of the underlying disk image.\nPermitted 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 to IETF RFC 3339.\n",
- "type": "string",
- "format": "date-time"
- },
- "minDisk": {
- "description": "Unsigned integer number\n",
- "type": "integer",
- "minimum": 0
- },
- "minRam": {
- "description": "Unsigned integer number\n",
- "type": "integer",
- "minimum": 0
- },
- "size": {
- "description": "Unsigned integer number\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 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"
- },
- "imagePath": {
- "description": "A string defined in IETF RFC 8259.\n",
- "type": "string"
- },
- "imageUri": {
- "description": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- }
- }
- }
- },
- "additionalArtifacts": {
- "description": "Information about VNF snapshot artifacts that are not VNFC snapshot images.\nSee note.\n",
- "type": "object",
- "items": {
- "description": "This type represents an artifact other than a software image which is contained in a VNF snapshot package.\n",
- "type": "object",
- "required": ["checksum", "isEncrypted"],
- "properties": {
- "artifactPath": {
- "description": "A string defined in IETF RFC 8259.\n",
- "type": "string"
- },
- "artifactUri": {
- "description": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- },
- "checksum": {
- "description": "Cheksum description\n",
- "type": "string"
- },
- "isEncrypted": {
- "description": "The Boolean is a data type having two values (true and false).\n",
- "type": "boolean"
- },
- "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 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"
- }
- }
- }
- },
- "state": {
- "description": "State of the VNF snapshot package. Permitted values: - CREATED: the VNF snapshot package information has been created. - BUILDING: the VNF snapshot package is being built. - UPLOADING: the VNF snapshot package is being uploaded. - EXTRACTING: the VNF snapshot package’s content is being extracted. - AVAILABLE: the VNF snapshot package is available (i.e., build or upload is completed). - PROCESSING: the VNF snapshot is being processed. - ERROR: failure during the VNF snapshot package building, uploading or processing. - ERROR_EXTRACTING: failure during the VNF snapshot package extraction task.\n",
- "type": "string",
- "enum": ["CREATED", "BUILDING", "UPLOADING", "EXTRACTING", "AVAILABLE", "PROCESSING", "ERROR", "ERROR_EXTRACTING"]
- },
- "isCancelPending": {
- "description": "The Boolean is a data type having two values (true and false).\n",
- "type": "boolean"
- },
- "failureDetails": {
- "description": "Failure details associated to current error state of the VNF snapshot package state. If \"state\" is \"ERROR\" or \"ERROR_EXTRACTING\", this attribute shall be present unless it has been requested to be excluded via an attribute selector.\n",
- "type": "object",
- "required": ["errorType", "details"],
- "properties": {
- "errorType": {
- "description": "Type of error, when the failure happened (building, upload, processing, extracting).\nPermitted values: - BUILD_ERROR - UPLOAD_ERROR - PROCESS_ERROR - CANCELLED - EXTRACTION_ERROR\n",
- "type": "string",
- "enum": ["BUILD_ERROR", "UPLOAD_ERROR", "PROCESS_ERROR", "CANCELLED", "EXTRACTION_ERROR"]
- },
- "details": {
- "description": "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 is reproduced inthis structure. Compared to the general framework defined in IETF RFC 7807, 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 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.\n",
- "type": "object",
- "required": ["status", "detail"],
- "properties": {
- "type": {
- "description": "A URI reference according to IETF RFC 3986 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"
- }
- }
- }
- }
- },
- "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 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"
- },
- "_links": {
- "description": "Links to resources related to this resource.\n",
- "type": "object",
- "required": ["self", "packageContent"],
- "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"
- }
- }
- },
- "packageContent": {
- "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"
- }
- }
- }
- }
- }
- }
- }
-}
\ No newline at end of file
+ "type": "array",
+ "items": {
+ "description": "This type represents the information of a VNF snapshot package.\nNOTE:\tThe attribute shall not be present before the VNF snapshot package content has been uploaded or built.\n Otherwise, this attribute shall be present unless it has been requested to be excluded per attribute selector.\n",
+ "type": "object",
+ "required": [
+ "id",
+ "name",
+ "isFullSnapshot",
+ "state",
+ "isCancelPending",
+ "_links"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfSnapshotPkgUniqueId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "name": {
+ "description": "A string defined in IETF RFC 8259.\n",
+ "type": "string"
+ },
+ "checksum": {
+ "description": "Cheksum description\n",
+ "type": "string"
+ },
+ "createdAt": {
+ "description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "vnfSnapshotId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfcSnapshotInfoIds": {
+ "description": "Identifiers of information held by the VNFM about specific VNFC snapshots part of the VNF snapshot and contained in the VNF snapshot package. This identifier is allocated by the VNFM during the VNF snapshot creation.\nSee note.\n",
+ "type": "object",
+ "items": {
+ "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\n",
+ "type": "string"
+ }
+ },
+ "isFullSnapshot": {
+ "description": "The Boolean is a data type having two values (true and false).\n",
+ "type": "boolean"
+ },
+ "vnfdInfo": {
+ "description": "This type represents the VNFD which is contained in a VNF snapshot package.\n",
+ "type": "object",
+ "required": ["avnfdId", "vnfdPath", "checksum", "isEncrypted"],
+ "properties": {
+ "avnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfdPath": {
+ "description": "A string defined in IETF RFC 8259.\n",
+ "type": "string"
+ },
+ "checksum": {
+ "description": "Cheksum description\n",
+ "type": "string"
+ },
+ "isEncrypted": {
+ "description": "The Boolean is a data type having two values (true and false).\n",
+ "type": "boolean"
+ }
+ }
+ },
+ "vnfsr": {
+ "description": "This type represents the VNF snapshot record which is contained in a VNF snapshot package.\n",
+ "type": "object",
+ "required": ["recordPath", "checksum", "isEncrypted"],
+ "properties": {
+ "recordPath": {
+ "description": "A string defined in IETF RFC 8259.\n",
+ "type": "string"
+ },
+ "checksum": {
+ "description": "Cheksum description\n",
+ "type": "string"
+ },
+ "isEncrypted": {
+ "description": "The Boolean is a data type having two values (true and false).\n",
+ "type": "boolean"
+ }
+ }
+ },
+ "vnfcSnapshotImages": {
+ "description": "Information about VNF snapshot artifacts that are VNFC snapshot images. Every local and external snapshot image shall be included. No other artifacts shall be included.\nSee note.\n",
+ "type": "object",
+ "items": {
+ "description": "This type represents an artifact contained in a VNF snapshot package which represents a snapshot image.\nNOTE 1:\tThe list of permitted values was taken from \"Container formats\" in OpenStack® documentation: \"Disk and container formats for images\"\n (Available at https://docs.openstack.org/glance/pike/user/formats.html).\nNOTE 2:\tThe list of permitted values was adapted from \"Disk formats\" in OpenStack® documentation: \"Disk and container formats for images\"\n (Available at https://docs.openstack.org/glance/pike/user/formats.html).\n",
+ "type": "object",
+ "required": [
+ "id",
+ "name",
+ "checksum",
+ "isEncrypted",
+ "vnfcInstanceId",
+ "containerFormat",
+ "diskFormat",
+ "createdAt",
+ "minDisk",
+ "minRam",
+ "size"
+ ],
+ "properties": {
+ "id": {
+ "description": "An identifier that is unique within a limited local scope other than above listed identifiers, such as within a complex data structure or within a request-response pair. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "name": {
+ "description": "A string defined in IETF RFC 8259.\n",
+ "type": "string"
+ },
+ "checksum": {
+ "description": "Cheksum description\n",
+ "type": "string"
+ },
+ "isEncrypted": {
+ "description": "The Boolean is a data type having two values (true and false).\n",
+ "type": "boolean"
+ },
+ "vnfcInstanceId": {
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
+ "type": "string"
+ },
+ "containerFormat": {
+ "description": "Container format indicates whether the snapshot image is in a file format that also contains metadata about the actual snapshot.\nPermitted values: - AKI: a kernel image format - AMI: a machine image format - ARI: a ramdisk image format - BARE: the image does not have a container or metadata envelope - DOCKER: docker container format - OVA: OVF package in a tarfile - OVF: OVF container format\nSee note 1.\n",
+ "type": "string",
+ "enum": ["AKI", "AMI", "ARI", "BARE", "DOCKER", "OVA", "OVF"]
+ },
+ "diskFormat": {
+ "description": "Disk format of a snapshot image is the format of the underlying disk image.\nPermitted 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 to IETF RFC 3339.\n",
+ "type": "string",
+ "format": "date-time"
+ },
+ "minDisk": {
+ "description": "Unsigned integer number\n",
+ "type": "integer",
+ "minimum": 0
+ },
+ "minRam": {
+ "description": "Unsigned integer number\n",
+ "type": "integer",
+ "minimum": 0
+ },
+ "size": {
+ "description": "Unsigned integer number\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 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"
+ },
+ "imagePath": {
+ "description": "A string defined in IETF RFC 8259.\n",
+ "type": "string"
+ },
+ "imageUri": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "additionalArtifacts": {
+ "description": "Information about VNF snapshot artifacts that are not VNFC snapshot images.\nSee note.\n",
+ "type": "object",
+ "items": {
+ "description": "This type represents an artifact other than a software image which is contained in a VNF snapshot package.\n",
+ "type": "object",
+ "required": ["checksum", "isEncrypted"],
+ "properties": {
+ "artifactPath": {
+ "description": "A string defined in IETF RFC 8259.\n",
+ "type": "string"
+ },
+ "artifactUri": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ },
+ "checksum": {
+ "description": "Cheksum description\n",
+ "type": "string"
+ },
+ "isEncrypted": {
+ "description": "The Boolean is a data type having two values (true and false).\n",
+ "type": "boolean"
+ },
+ "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 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"
+ }
+ }
+ }
+ },
+ "state": {
+ "description": "State of the VNF snapshot package. Permitted values: - CREATED: the VNF snapshot package information has been created. - BUILDING: the VNF snapshot package is being built. - UPLOADING: the VNF snapshot package is being uploaded. - EXTRACTING: the VNF snapshot package’s content is being extracted. - AVAILABLE: the VNF snapshot package is available (i.e., build or upload is completed). - PROCESSING: the VNF snapshot is being processed. - ERROR: failure during the VNF snapshot package building, uploading or processing. - ERROR_EXTRACTING: failure during the VNF snapshot package extraction task.\n",
+ "type": "string",
+ "enum": [
+ "CREATED",
+ "BUILDING",
+ "UPLOADING",
+ "EXTRACTING",
+ "AVAILABLE",
+ "PROCESSING",
+ "ERROR",
+ "ERROR_EXTRACTING"
+ ]
+ },
+ "isCancelPending": {
+ "description": "The Boolean is a data type having two values (true and false).\n",
+ "type": "boolean"
+ },
+ "failureDetails": {
+ "description": "Failure details associated to current error state of the VNF snapshot package state. If \"state\" is \"ERROR\" or \"ERROR_EXTRACTING\", this attribute shall be present unless it has been requested to be excluded via an attribute selector.\n",
+ "type": "object",
+ "required": ["errorType", "details"],
+ "properties": {
+ "errorType": {
+ "description": "Type of error, when the failure happened (building, upload, processing, extracting).\nPermitted values: - BUILD_ERROR - UPLOAD_ERROR - PROCESS_ERROR - CANCELLED - EXTRACTION_ERROR\n",
+ "type": "string",
+ "enum": [
+ "BUILD_ERROR",
+ "UPLOAD_ERROR",
+ "PROCESS_ERROR",
+ "CANCELLED",
+ "EXTRACTION_ERROR"
+ ]
+ },
+ "details": {
+ "description": "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 is reproduced inthis structure. Compared to the general framework defined in IETF RFC 7807, 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 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.\n",
+ "type": "object",
+ "required": ["status", "detail"],
+ "properties": {
+ "type": {
+ "description": "A URI reference according to IETF RFC 3986 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"
+ }
+ }
+ }
+ }
+ },
+ "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 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"
+ },
+ "_links": {
+ "description": "Links to resources related to this resource.\n",
+ "type": "object",
+ "required": ["self", "packageContent"],
+ "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"
+ }
+ }
+ },
+ "packageContent": {
+ "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"
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+}
diff --git a/SOL003/VirtualisedResourcesQuotaAvailableNotification-API/ApiVersion.robot b/SOL003/VirtualisedResourcesQuotaAvailableNotification-API/ApiVersion.robot
index d58e0d85e5b192176da91fe67afdb9d04ef8d339..ded892a98e75b4f0c38d29efde4dcc81c03e1e57 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] v3.5.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.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 0d3ae4cf8386a178d14e63bca1f6d80c6ac2bf4b..4aac234ce7ce51b35619e952c8e72ca0cb622b2e 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] v3.6.1
+ ... Reference: Clause 11.4.3.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.3.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.3.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.3.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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 0079238108dbbabcaf79b26036c203c3cec1ac30..8b3ad2f081ab4ed54fd561073b3d27c6a9368f70 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] v3.6.1
+ ... Reference: Clause 11.4.4.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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 3d7c0e1c525ea565e8d92ce8cc07c6688840c79f..24f1c21e83f268363ad64926d642665f2fc90859 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] v3.6.1
+ ... Reference: Clause 11.4.4.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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 4f43bfac52d18bc1fc7326f3e3590451c92ddf08..4b23bc3bd77993d16f6d246effa93cec21afbfa6 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] v3.6.1
+ ... Reference: Clause 11.4.2.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.2.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.2.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.2.3.3 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.2.3.4 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.2.3.5 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
@@ -169,7 +169,7 @@ Create new Virtualised Resources Quota Available Notification Subscription - Unp
... 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.
... re-conditions: none
- ... Reference: Clause 11.4.2.3.1 - ETSI GS NFV-SOL 003 [1] v3.6.1
+ ... Reference: Clause 11.4.2.3.1 - ETSI GS NFV-SOL 003 [1] v4.3.1
... Config ID: Config_prod_VNFM
... Applicability: none
... Post-Conditions: none
diff --git a/SOL003/VirtualisedResourcesQuotaAvailableNotification-API/schemas/VrQuotaAvailSubscription.schema.json b/SOL003/VirtualisedResourcesQuotaAvailableNotification-API/schemas/VrQuotaAvailSubscription.schema.json
index 8f37c51c13940fb8e3a3ac7e6c803ba621f9c9cb..bc26b36715c3b8f6fe12efa6bc847bc463caa955 100644
--- a/SOL003/VirtualisedResourcesQuotaAvailableNotification-API/schemas/VrQuotaAvailSubscription.schema.json
+++ b/SOL003/VirtualisedResourcesQuotaAvailableNotification-API/schemas/VrQuotaAvailSubscription.schema.json
@@ -1,83 +1,71 @@
{
- "description": "This type represents a subscription related to notifications related to the availability of the virtualised resources quotas.\n",
- "type": "object",
- "required": [
- "id",
- "callbackUri",
- "_links"
- ],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "filter": {
- "description": "This type represents a subscription filter related to notifications about the availability of the virtualised resources quotas. At a particular nesting level in the filter structure, the following applies: All attributes shall match in order for the filter to match (logical \"and\" between different filter attributes). If an attribute is an array, the attribute shall match if at least one of the values in the array matches (logical \"or\" between the values of one filter attribute).\n",
- "type": "object",
- "properties": {
- "vimIds": {
- "description": "Match VIMs that were created the quota for a consumer of the virtualised resources. This attribute shall only be supported when VNF-related Resource Management in direct mode is applicable.\n",
- "type": "array",
- "items": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- }
- },
- "resourceProviderIds": {
- "description": "Match the entities responsible for the management of the virtualised resources that were allocated by the NFVO. This attribute shall only be supported when VNF-related Resource Management in indirect mode is applicable. The identification scheme 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"
- }
- },
- "resourceTypes": {
- "description": "Match particular resource types.\n",
- "type": "array",
- "items": {
- "type": "string",
- "enum": [
- "COMPUTE",
- "STORAGE",
- "NETWORK"
- ]
- }
- },
- "resourceGroupIds": {
- "description": "Match the \"infrastructure resource groups\" that are logical groupings of the virtualised resources assigned to a tenant within an infrastructure Domain.\n",
- "type": "array",
- "items": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- }
- }
- }
- },
- "callbackUri": {
- "description": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- },
- "_links": {
- "description": "Links for this resource\n",
- "type": "object",
- "required": [
- "self"
- ],
- "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"
- }
- }
- }
- }
- }
- }
+ "description": "This type represents a subscription related to notifications related to the availability of the virtualised resources quotas.\n",
+ "type": "object",
+ "required": ["id", "callbackUri", "_links"],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "filter": {
+ "description": "This type represents a subscription filter related to notifications about the availability of the virtualised resources quotas. At a particular nesting level in the filter structure, the following applies: All attributes shall match in order for the filter to match (logical \"and\" between different filter attributes). If an attribute is an array, the attribute shall match if at least one of the values in the array matches (logical \"or\" between the values of one filter attribute).\n",
+ "type": "object",
+ "properties": {
+ "vimIds": {
+ "description": "Match VIMs that were created the quota for a consumer of the virtualised resources. This attribute shall only be supported when VNF-related Resource Management in direct mode is applicable.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ },
+ "resourceProviderIds": {
+ "description": "Match the entities responsible for the management of the virtualised resources that were allocated by the NFVO. This attribute shall only be supported when VNF-related Resource Management in indirect mode is applicable. The identification scheme 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"
+ }
+ },
+ "resourceTypes": {
+ "description": "Match particular resource types.\n",
+ "type": "array",
+ "items": {
+ "type": "string",
+ "enum": ["COMPUTE", "STORAGE", "NETWORK"]
+ }
+ },
+ "resourceGroupIds": {
+ "description": "Match the \"infrastructure resource groups\" that are logical groupings of the virtualised resources assigned to a tenant within an infrastructure Domain.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "callbackUri": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ },
+ "_links": {
+ "description": "Links for this resource\n",
+ "type": "object",
+ "required": ["self"],
+ "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"
+ }
+ }
+ }
+ }
+ }
+ }
}
\ No newline at end of file
diff --git a/SOL003/VirtualisedResourcesQuotaAvailableNotification-API/schemas/VrQuotaAvailSubscriptions.schema.json b/SOL003/VirtualisedResourcesQuotaAvailableNotification-API/schemas/VrQuotaAvailSubscriptions.schema.json
index 9ad57bc211fa48c9296b5ca4daba991bcb06ccb7..bde7a786d6c364b7f3b517a5809daefd6239690c 100644
--- a/SOL003/VirtualisedResourcesQuotaAvailableNotification-API/schemas/VrQuotaAvailSubscriptions.schema.json
+++ b/SOL003/VirtualisedResourcesQuotaAvailableNotification-API/schemas/VrQuotaAvailSubscriptions.schema.json
@@ -1,87 +1,74 @@
{
"type": "array",
- "items":
- {
- "description": "This type represents a subscription related to notifications related to the availability of the virtualised resources quotas.\n",
- "type": "object",
- "required": [
- "id",
- "callbackUri",
- "_links"
- ],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "filter": {
- "description": "This type represents a subscription filter related to notifications about the availability of the virtualised resources quotas. At a particular nesting level in the filter structure, the following applies: All attributes shall match in order for the filter to match (logical \"and\" between different filter attributes). If an attribute is an array, the attribute shall match if at least one of the values in the array matches (logical \"or\" between the values of one filter attribute).\n",
- "type": "object",
- "properties": {
- "vimIds": {
- "description": "Match VIMs that were created the quota for a consumer of the virtualised resources. This attribute shall only be supported when VNF-related Resource Management in direct mode is applicable.\n",
- "type": "array",
- "items": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- }
- },
- "resourceProviderIds": {
- "description": "Match the entities responsible for the management of the virtualised resources that were allocated by the NFVO. This attribute shall only be supported when VNF-related Resource Management in indirect mode is applicable. The identification scheme 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"
- }
- },
- "resourceTypes": {
- "description": "Match particular resource types.\n",
- "type": "array",
- "items": {
- "type": "string",
- "enum": [
- "COMPUTE",
- "STORAGE",
- "NETWORK"
- ]
- }
- },
- "resourceGroupIds": {
- "description": "Match the \"infrastructure resource groups\" that are logical groupings of the virtualised resources assigned to a tenant within an infrastructure Domain.\n",
- "type": "array",
- "items": {
- "description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
- "type": "string"
- }
- }
- }
- },
- "callbackUri": {
- "description": "String formatted according to IETF RFC 3986.\n",
- "type": "string"
- },
- "_links": {
- "description": "Links for this resource\n",
- "type": "object",
- "required": [
- "self"
- ],
- "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"
- }
- }
- }
- }
- }
- }
+ "items": {
+ "description": "This type represents a subscription related to notifications related to the availability of the virtualised resources quotas.\n",
+ "type": "object",
+ "required": ["id", "callbackUri", "_links"],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "filter": {
+ "description": "This type represents a subscription filter related to notifications about the availability of the virtualised resources quotas. At a particular nesting level in the filter structure, the following applies: All attributes shall match in order for the filter to match (logical \"and\" between different filter attributes). If an attribute is an array, the attribute shall match if at least one of the values in the array matches (logical \"or\" between the values of one filter attribute).\n",
+ "type": "object",
+ "properties": {
+ "vimIds": {
+ "description": "Match VIMs that were created the quota for a consumer of the virtualised resources. This attribute shall only be supported when VNF-related Resource Management in direct mode is applicable.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ },
+ "resourceProviderIds": {
+ "description": "Match the entities responsible for the management of the virtualised resources that were allocated by the NFVO. This attribute shall only be supported when VNF-related Resource Management in indirect mode is applicable. The identification scheme 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"
+ }
+ },
+ "resourceTypes": {
+ "description": "Match particular resource types.\n",
+ "type": "array",
+ "items": {
+ "type": "string",
+ "enum": ["COMPUTE", "STORAGE", "NETWORK"]
+ }
+ },
+ "resourceGroupIds": {
+ "description": "Match the \"infrastructure resource groups\" that are logical groupings of the virtualised resources assigned to a tenant within an infrastructure Domain.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier maintained by the VIM or the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
+ "type": "string"
+ }
+ }
+ }
+ },
+ "callbackUri": {
+ "description": "String formatted according to IETF RFC 3986.\n",
+ "type": "string"
+ },
+ "_links": {
+ "description": "Links for this resource\n",
+ "type": "object",
+ "required": ["self"],
+ "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"
+ }
+ }
+ }
+ }
+ }
+ }
}
}
\ No newline at end of file
diff --git a/SOL005/NFVICapacityInformation-API/ApiVersion.robot b/SOL005/NFVICapacityInformation-API/ApiVersion.robot
index 2bd409479c467c774efb4b93651b1a57af67fc85..7565b18839f951bdc624e10082f1cdd91a3115db 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] v3.5.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.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 17cd530b104c72408625b99aca7df099ea8464b9..c0575ad034a5c80f1109d3f49db25270b733bf22 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] v3.6.1
+ ... Reference: Clause 10.4.4.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -21,7 +21,7 @@ POST Create Capacity Threshold - Unprocessible Entity
... Test title: POST Create Capacity Threshold - Unprocessible Entity
... 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] v3.6.1
+ ... Reference: Clause 10.4.4.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.4.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.4.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.4.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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 42b6fe0131bb7abfdcb4ddfa8f699f5ff9dfe487..e70d34dfce03dd7b18235b2218ace22c61da3e20 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] v3.6.1
+ ... Reference: Clause 10.4.5.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.5.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.5.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: Capacity Threshold modified
@@ -70,7 +70,7 @@ 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] v3.6.1
+ ... Reference: Clause 10.4.5.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -83,7 +83,7 @@ PATCH Individual Capacity Threshold - Unprocessible Entity
... Test title: PATCH Individual Capacity Threshold - Precondition Failed
... 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] v3.6.1
+ ... Reference: Clause 10.4.5.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -96,7 +96,7 @@ 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] v3.6.1
+ ... Reference: Clause 10.4.5.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: Capacity threshold is deleted
diff --git a/SOL005/NFVICapacityInformation-API/IndividualVIMsNFVICapacityInformation.robot b/SOL005/NFVICapacityInformation-API/IndividualVIMsNFVICapacityInformation.robot
index 89a7ec2d0e2515741fc777dbbd6d113f67246363..bcacd63c06ae87b5a1f1b77b09cefb52a6a2cb48 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] v3.6.1
+ ... Reference: Clause 10.4.3.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.3.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.3.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.3.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.3.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.3.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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 355a245f6e6ebdc4f58c90deca0ea7f143ad0b79..18da26d8e21470ee6cceb677dd74f59e1c513b38 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] v3.6.1
+ ... Reference: Clause 10.4.2.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.2.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.2.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.2.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/NFVICapacityInformation-API/NotificationEndpoint.robot b/SOL005/NFVICapacityInformation-API/NotificationEndpoint.robot
index a880338752af0258664edd20b80264902d61b4d3..d6361043b28b371e6ec39269f5fb06531903e184 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] v3.6.1
+ ... Reference: Clause 10.4.6.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.6.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.6.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.6.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 10.4.6.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_Notif_Endpoint
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/NSDManagement-API/ApiVersion.robot b/SOL005/NSDManagement-API/ApiVersion.robot
index 2d7ba78bf2317294a4b86ff9bd9f8a1846a17e7f..1361f8086c5d896b941743f664b7bf9c34407766 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] v3.5.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.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 27102e5918c53c050516277a51a2d23b477939be..8350c492d5852d7ac3f4a2fa3a4919a45a025a5e 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] v3.6.1
+ ... Reference: Clause 5.4.4c.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.4c.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.4c.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.4c.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.4c.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.4c.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.4c.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.4c.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.4c.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.4c.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.4c.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.4c.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.4c.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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 ce14edd24529d5cd99f00e49236c158d0cfeed24..b0400b27f5e8b6a13e0605b3105e3141324faf14 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] v3.6.1
+ ... Reference: Clause 5.4.3.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.3.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -100,7 +100,7 @@ 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] v3.6.1
+ ... Reference: Clause 5.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -123,7 +123,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] v3.6.1
+ ... Reference: Clause 5.4.3.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: The Network Service Descriptor is not available anymore in the NFVO
@@ -136,7 +136,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] v3.6.1
+ ... Reference: Clause 5.4.3.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: The Network Service Descriptor is not deleted by the failed operation.
@@ -150,7 +150,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] v3.6.1
+ ... Reference: Clause 5.4.3.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -162,7 +162,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] v3.6.1
+ ... Reference: Clause 5.4.3.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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 144746acef45fcc9344da0af25c2f4be876482bd..476c7abbe7e965c02a17cb8f0ebb16d950b50212 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] v3.6.1
+ ... Reference: Clause 5.4.7c.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.7c.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.7c.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.7c.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.7c.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.7c.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.7c.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.7c.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.7c.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.7c.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.7c.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.7c.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.7c.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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 7fd007b5bd938eb2465b20268b9ccadf5f1ec02f..99e123ebb675ecf8e282c179a4af5a641710f2c4 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] v3.6.1
+ ... Reference: Clause 5.4.6.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.6.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.6.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: The PNF Descriptor is modified according to the update request
@@ -55,7 +55,7 @@ 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] v3.6.1
+ ... Reference: Clause 5.4.6.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -67,7 +67,7 @@ POST Individual PNF Descriptor - Method not implemented
... 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] v3.6.1
+ ... Reference: Clause 5.4.6.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -79,7 +79,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] v3.6.1
+ ... Reference: Clause 5.4.6.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -91,7 +91,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] v3.6.1
+ ... Reference: Clause 5.4.6.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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 fd70f029d86cb3fbee51f8d16a63a646a564ac12..e79a4f0bb831007484afbad7e1e0d0cf7da79b80 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] v3.6.1
+ ... Reference: Clause 5.4.9.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.9.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.9.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.9.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.9.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.9.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.9.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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 3ed43486e525558529f453fb473b82b50c1bf4d0..d154e4107db7a762338167b0ac98781fd8823ed3 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] v3.6.1
+ ... Reference: Clause 5.4.4a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.4a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.4a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.4a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.4a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.4a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.4a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.4a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.4a.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.4a.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.4a.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.4a.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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 6b8f639f94d404c19770ff1715aa5e2b09334547..7aa3c6f57a3394371df22df9966a2907393d6895 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] v3.6.1
+ ... Reference: Clause 5.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.4.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.4.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.4.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.4.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.4.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.4.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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 b0636f4d873f3b2a0271d408907c3e30ffbe264e..5fb375333da075d72c6a52041a428dbe90d8918d 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] v3.6.1
+ ... Reference: Clause 5.4.4b.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.4b.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.4b.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.4b.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.4b.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.4b.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.4b.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/NSDManagement-API/NSDescriptors.robot b/SOL005/NSDManagement-API/NSDescriptors.robot
index 06d3addc7a02376aae8a03d72a850dcf57197c9d..8927a94a74f2427e0dc8f18ebe50e538a920e231 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] v3.6.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.2.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.2.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.2.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.2.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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 aa66153719707fe860905b916353488635be073c..41ed637fec2b55a83c1ed0e854a26c5bb9bfe470 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] v3.6.1
+ ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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 9f0c67b0fdd2686b30af6ec5fc37dde048cc347a..c10fd6bf7cb138ddda647c27f64291f02f4410b5 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] v3.6.1
+ ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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 16f55f60b411d563eddad619cd1a70db219e7d25..c2b837a407b280809be7b30cefe24c3291350f26 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] v3.6.1
+ ... Reference: Clause 5.4.7a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.7a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.7a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.7a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.7a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.7a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.7a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.7a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.7a.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.7a.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.7a.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.7a.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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 d1094eb0c17500a095454148ca251bf08be0fa4c..6cf83c7178a54a0c82880f21f75772019c34faff 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] v3.6.1
+ ... Reference: Clause 5.4.7.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.7.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.7.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.7.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.7.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.7.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.7.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.7.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.7.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.7.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.7.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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 80425d608d1fea3bd43476324e021aa2be8b49c4..30502dda55b79edaf1f16ab911f77f170326c08b 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] v3.6.1
+ ... Reference: Clause 5.4.7b.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.7b.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.7b.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.7b.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.7b.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.7b.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.7b.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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 134d45be326f5874562ca4c45bb2f07a643f4626..81bbe41f7231b4489e31e52fec0a80d2dba1c512 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] v3.6.1
+ ... Reference: Clause 5.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.5.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.5.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.5.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.5.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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 f8b390791da51846468b6a5cab81ed01e08fd47d..ecc2dd21eac81d5399c71fd5c845bb6e3d768a70 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] v3.6.1
+ ... Reference: Clause 5.4.8.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.8.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.8.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.8.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.8.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.8.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.8.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.8.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.8.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.8.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.8.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 5.4.8.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -178,7 +178,7 @@ Create new NSD Management subscription - Unprocessable Entity
... Test title: Create new NSD Management subscription - Unprocessable Entity
... 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] v3.6.1
+ ... Reference: Clause 5.4.8.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/NSDManagement-API/schemas/NsdInfo.schema.json b/SOL005/NSDManagement-API/schemas/NsdInfo.schema.json
index 1cc5abe596ff06011f0be177b75bcdc3fd0085a0..63be88441b27ac9aae05b641fa8ea91c44513998 100644
--- a/SOL005/NSDManagement-API/schemas/NsdInfo.schema.json
+++ b/SOL005/NSDManagement-API/schemas/NsdInfo.schema.json
@@ -1,161 +1,186 @@
{
- "type": "object",
- "required": [
- "id",
- "nsdOnboardingState",
- "nsdOperationalState",
- "nsdUsageState",
- "_links"
- ],
- "properties": {
- "id": {
- "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"
- },
- "nsdName": {
- "type": "string",
- "description": "\"Name of the on boarded NSD. This information is copied from the NSD content and shall be present after the NSD content is on-boarded.\"\n"
- },
- "nsdVersion": {
- "description": "A Version.\n",
- "type": "string"
- },
- "nsdDesigner": {
- "type": "string",
- "description": "\"Designer of the on-boarded NSD. This information is copied from the NSD content and shall be present after the NSD content is on-boarded.\"\n"
- },
- "nsdInvariantId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfPkgIds": {
- "description": "Identifies the VNF package for the VNFD referenced by the on-boarded NS descriptor resource.\n",
- "type": "array",
- "items": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- }
- },
- "pnfdInfoIds": {
- "description": "Identifies the PnfdInfo element for the PNFD referenced by the on-boarded NS descriptor resource.\n",
- "type": "array",
- "items": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- }
- },
- "nestedNsdInfoIds": {
- "description": "Identifies the NsdInfo element for the nested NSD referenced by the on-boarded NS descriptor resource.\n",
- "type": "array",
- "items": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- }
- },
- "nsdOnboardingState": {
- "type": "string",
- "description": "\"The enumeration NsdOnboardingStateType shall comply with the provisions defined in Table 5.5.4.5-1 of GS NFV-SOL 005. It indicates the on-boarding state of the NSD. CREATED = The NSD information object is created. UPLOADING = The associated NSD content is being uploaded. PROCESSING = The associated NSD content is being processed, e.g. validation. ONBOARDED = The associated NSD content is on-boarded.\"\n",
- "enum": [
- "CREATED",
- "UPLOADING",
- "PROCESSING",
- "ONBOARDED"
- ]
- },
- "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"
- }
- }
- },
- "nsdOperationalState": {
- "type": "string",
- "description": "\"The enumeration NsdOperationalStateType shall comply with the provisions defined in Table 5.5.4.3-1 of GS NFV_SOL 005. It indicates the operational state of the resource. ENABLED = The operational state of the resource is enabled. DISABLED = The operational state of the resource is disabled.\"\n",
- "enum": [
- "ENABLED",
- "DISABLED"
- ]
- },
- "nsdUsageState": {
- "type": "string",
- "description": "\"The enumeration NsdUsageStateType shall comply with the provisions defined in Table 5.5.4.4-1 of GS NFV-SOL 005. It indicates the usage state of the resource.IN_USE = The resource is in use.NOT_IN_USE = The resource is not-in-use.\"\n",
- "enum": [
- "IN_USE",
- "NOT_IN_USE"
- ]
- },
- "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": {
- "type": "object",
- "required": [
- "self",
- "nsd_content"
- ],
- "description": "\"Links to resources related to this resource.\"\n",
- "properties": {
- "self": {
- "description": "This type represents a link to a resource.\n",
- "type": "object",
- "required": [
- "href"
- ],
- "properties": {
- "href": {
- "description": "URI of the referenced resource.\n",
- "type": "string",
- "format": "url"
- }
- }
- },
- "nsd_content": {
- "description": "This type represents a link to a resource.\n",
- "type": "object",
- "required": [
- "href"
- ],
- "properties": {
- "href": {
- "description": "URI of the referenced resource.\n",
- "type": "string",
- "format": "url"
- }
- }
- }
- }
- }
- },
- "description": "\"This type represents a response for the query NSD operation.\"\t\n"
+ "description": "This type represents a response for the query NSD operation. NOTE 1: At least one of the attributes - vnfPkgId and nestedNsdInfoId shall be present, after the NSD is on-boarded. NOTE 2: If the value of the nsdOnboardingState attribute is not equal to \"ONBOARDED\", the value of the nsdOperationalState attribute shall be equal to \"DISABLED\". NOTE 3: If the value of the nsdOnboardingState attribute is not equal to \"ONBOARDED\", the value of the nsdUsageState attribute shall be equal to \"NOT_IN_USE\". NOTE 4: State changes of an NSD are illustrated in clause B.2. NOTE 5: This attribute shall be present after the NSD is on-boarded for those VNF packages that are already on-boarded. NOTE 6: This attribute shall be present after the NSD is on-boarded for those PNFDs that are already on-boarded. NOTE 7: This attribute shall be present after the NSD is on-boarded for those nested NSDs that are already on-boarded.",
+ "type": "object",
+ "anyOf": [{
+ "required": ["vnfPkgIds"]
+ }, {
+ "required": ["nestedNsdInfoIds"]
+ }],
+ "required": ["id", "nsdOnboardingState", "nsdOperationalState", "nsdUsageState", "_links"],
+ "properties": {
+ "id": {
+ "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"
+ },
+ "nsdExtInvariantId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "nsdName": {
+ "type": "string",
+ "description": "Name of the on boarded NSD. This information is copied from the NSD content and shall be present after the NSD content is on-boarded.\n"
+ },
+ "nsdVersion": {
+ "description": "A Version. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "nsdDesigner": {
+ "type": "string",
+ "description": "Designer of the on-boarded NSD. This information is copied from the NSD content and shall be present after the NSD content is on-boarded.\n"
+ },
+ "nsdInvariantId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfPkgIds": {
+ "description": "Identifies the VNF package for the VNFD referenced by the on-boarded NS descriptor resource. See notes 1 and 5.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ },
+ "pnfdInfoIds": {
+ "description": "Identifies the PnfdInfo element for the PNFD referenced by the on-boarded NS descriptor resource. See note 6.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ },
+ "nestedNsdInfoIds": {
+ "description": "Identifies the NsdInfo element for the nested NSD referenced by the on-boarded NS descriptor resource. See notes 1 and 7.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ },
+ "archiveSecurityOption": {
+ "description": "Signals the security option used by the NSD archive as defined in clause 5.1 of ETSI GS NFV SOL 007. 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": "A string as defined in IETF RFC 8259.\n",
+ "type": "string"
+ },
+ "artifacts": {
+ "description": "Information about NSD archive artifacts contained in the NSD archive. This attribute shall not be present before the NSD archive content is on-boarded. Otherwise, this attribute shall be present if the NSD archive contains artifacts.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "description": "This type represents an artifact contained in an NSD archive. It shall comply with provisions defined in Table 5.5.3.5-1.\n",
+ "required": ["artifactPath", "checksum"],
+ "properties": {
+ "artifactPath": {
+ "description": "A string as defined in IETF RFC 8259.\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"
+ }
+ }
+ },
+ "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"
+ }
+ }
+ }
+ },
+ "nsdOnboardingState": {
+ "type": "string",
+ "description": "The enumeration NsdOnboardingStateType shall comply with the provisions defined in Table 5.5.4.5-1 of GS NFV-SOL 005. It indicates the on-boarding state of the NSD. CREATED = The NSD information object has been created. UPLOADING = The associated NSD content is being uploaded. PROCESSING = The associated NSD content is being processed, e.g. validation. ONBOARDED = The associated NSD content has been on-boarded. ERROR = There was an error during upload or processing of the NSD content.\n",
+ "enum": ["CREATED", "UPLOADING", "PROCESSING", "ONBOARDED", "ERROR"]
+ },
+ "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"
+ }
+ }
+ },
+ "nsdOperationalState": {
+ "type": "string",
+ "description": "The enumeration NsdOperationalStateType shall comply with the provisions defined in Table 5.5.4.3-1 of GS NFV_SOL 005. It indicates the operational state of the resource. ENABLED = The operational state of the resource is enabled. DISABLED = The operational state of the resource is disabled.\n",
+ "enum": ["ENABLED", "DISABLED"]
+ },
+ "nsdUsageState": {
+ "type": "string",
+ "description": "The enumeration NsdUsageStateType shall comply with the provisions defined in Table 5.5.4.4-1 of GS NFV-SOL 005. It indicates the usage state of the resource.IN_USE = The resource is in use.NOT_IN_USE = The resource is not-in-use.\n",
+ "enum": ["IN_USE", "NOT_IN_USE"]
+ },
+ "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": {
+ "type": "object",
+ "required": ["self", "nsd_content"],
+ "description": "Links to resources related to this resource.\n",
+ "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"
+ }
+ }
+ },
+ "nsd_content": {
+ "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
diff --git a/SOL005/NSDManagement-API/schemas/NsdInfos.schema.json b/SOL005/NSDManagement-API/schemas/NsdInfos.schema.json
index 226ebe7d3829c4aad50209f76ae997fa93d52dae..3cbe8b81ab083a8b6eb6197dcc26ff044e2b04d4 100644
--- a/SOL005/NSDManagement-API/schemas/NsdInfos.schema.json
+++ b/SOL005/NSDManagement-API/schemas/NsdInfos.schema.json
@@ -1,164 +1,189 @@
{
- "type": "array",
- "items": {
- "type": "object",
- "required": [
- "id",
- "nsdOnboardingState",
- "nsdOperationalState",
- "nsdUsageState",
- "_links"
- ],
- "properties": {
- "id": {
- "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"
- },
- "nsdName": {
- "type": "string",
- "description": "\"Name of the on boarded NSD. This information is copied from the NSD content and shall be present after the NSD content is on-boarded.\"\n"
- },
- "nsdVersion": {
- "description": "A Version.\n",
- "type": "string"
- },
- "nsdDesigner": {
- "type": "string",
- "description": "\"Designer of the on-boarded NSD. This information is copied from the NSD content and shall be present after the NSD content is on-boarded.\"\n"
- },
- "nsdInvariantId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "vnfPkgIds": {
- "description": "Identifies the VNF package for the VNFD referenced by the on-boarded NS descriptor resource.\n",
- "type": "array",
- "items": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- }
- },
- "pnfdInfoIds": {
- "description": "Identifies the PnfdInfo element for the PNFD referenced by the on-boarded NS descriptor resource.\n",
- "type": "array",
- "items": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- }
- },
- "nestedNsdInfoIds": {
- "description": "Identifies the NsdInfo element for the nested NSD referenced by the on-boarded NS descriptor resource.\n",
- "type": "array",
- "items": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- }
- },
- "nsdOnboardingState": {
- "type": "string",
- "description": "\"The enumeration NsdOnboardingStateType shall comply with the provisions defined in Table 5.5.4.5-1 of GS NFV-SOL 005. It indicates the on-boarding state of the NSD. CREATED = The NSD information object is created. UPLOADING = The associated NSD content is being uploaded. PROCESSING = The associated NSD content is being processed, e.g. validation. ONBOARDED = The associated NSD content is on-boarded.\"\n",
- "enum": [
- "CREATED",
- "UPLOADING",
- "PROCESSING",
- "ONBOARDED"
- ]
- },
- "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"
- }
- }
- },
- "nsdOperationalState": {
- "type": "string",
- "description": "\"The enumeration NsdOperationalStateType shall comply with the provisions defined in Table 5.5.4.3-1 of GS NFV_SOL 005. It indicates the operational state of the resource. ENABLED = The operational state of the resource is enabled. DISABLED = The operational state of the resource is disabled.\"\n",
- "enum": [
- "ENABLED",
- "DISABLED"
- ]
- },
- "nsdUsageState": {
- "type": "string",
- "description": "\"The enumeration NsdUsageStateType shall comply with the provisions defined in Table 5.5.4.4-1 of GS NFV-SOL 005. It indicates the usage state of the resource.IN_USE = The resource is in use.NOT_IN_USE = The resource is not-in-use.\"\n",
- "enum": [
- "IN_USE",
- "NOT_IN_USE"
- ]
- },
- "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": {
- "type": "object",
- "required": [
- "self",
- "nsd_content"
- ],
- "description": "\"Links to resources related to this resource.\"\n",
- "properties": {
- "self": {
- "description": "This type represents a link to a resource.\n",
- "type": "object",
- "required": [
- "href"
- ],
- "properties": {
- "href": {
- "description": "URI of the referenced resource.\n",
- "type": "string",
- "format": "url"
- }
- }
- },
- "nsd_content": {
- "description": "This type represents a link to a resource.\n",
- "type": "object",
- "required": [
- "href"
- ],
- "properties": {
- "href": {
- "description": "URI of the referenced resource.\n",
- "type": "string",
- "format": "url"
- }
- }
- }
- }
- }
- },
- "description": "\"This type represents a response for the query NSD operation.\"\t\n"
- }
+ "type": "array",
+ "items": {
+ "description": "This type represents a response for the query NSD operation. NOTE 1: At least one of the attributes - vnfPkgId and nestedNsdInfoId shall be present, after the NSD is on-boarded. NOTE 2: If the value of the nsdOnboardingState attribute is not equal to \"ONBOARDED\", the value of the nsdOperationalState attribute shall be equal to \"DISABLED\". NOTE 3: If the value of the nsdOnboardingState attribute is not equal to \"ONBOARDED\", the value of the nsdUsageState attribute shall be equal to \"NOT_IN_USE\". NOTE 4: State changes of an NSD are illustrated in clause B.2. NOTE 5: This attribute shall be present after the NSD is on-boarded for those VNF packages that are already on-boarded. NOTE 6: This attribute shall be present after the NSD is on-boarded for those PNFDs that are already on-boarded. NOTE 7: This attribute shall be present after the NSD is on-boarded for those nested NSDs that are already on-boarded.",
+ "type": "object",
+ "anyOf": [{
+ "required": ["vnfPkgIds"]
+ }, {
+ "required": ["nestedNsdInfoIds"]
+ }],
+ "required": ["id", "nsdOnboardingState", "nsdOperationalState", "nsdUsageState", "_links"],
+ "properties": {
+ "id": {
+ "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"
+ },
+ "nsdExtInvariantId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "nsdName": {
+ "type": "string",
+ "description": "Name of the on boarded NSD. This information is copied from the NSD content and shall be present after the NSD content is on-boarded.\n"
+ },
+ "nsdVersion": {
+ "description": "A Version. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "nsdDesigner": {
+ "type": "string",
+ "description": "Designer of the on-boarded NSD. This information is copied from the NSD content and shall be present after the NSD content is on-boarded.\n"
+ },
+ "nsdInvariantId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "vnfPkgIds": {
+ "description": "Identifies the VNF package for the VNFD referenced by the on-boarded NS descriptor resource. See notes 1 and 5.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ },
+ "pnfdInfoIds": {
+ "description": "Identifies the PnfdInfo element for the PNFD referenced by the on-boarded NS descriptor resource. See note 6.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ },
+ "nestedNsdInfoIds": {
+ "description": "Identifies the NsdInfo element for the nested NSD referenced by the on-boarded NS descriptor resource. See notes 1 and 7.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ },
+ "archiveSecurityOption": {
+ "description": "Signals the security option used by the NSD archive as defined in clause 5.1 of ETSI GS NFV SOL 007. 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": "A string as defined in IETF RFC 8259.\n",
+ "type": "string"
+ },
+ "artifacts": {
+ "description": "Information about NSD archive artifacts contained in the NSD archive. This attribute shall not be present before the NSD archive content is on-boarded. Otherwise, this attribute shall be present if the NSD archive contains artifacts.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "description": "This type represents an artifact contained in an NSD archive. It shall comply with provisions defined in Table 5.5.3.5-1.\n",
+ "required": ["artifactPath", "checksum"],
+ "properties": {
+ "artifactPath": {
+ "description": "A string as defined in IETF RFC 8259.\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"
+ }
+ }
+ },
+ "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"
+ }
+ }
+ }
+ },
+ "nsdOnboardingState": {
+ "type": "string",
+ "description": "The enumeration NsdOnboardingStateType shall comply with the provisions defined in Table 5.5.4.5-1 of GS NFV-SOL 005. It indicates the on-boarding state of the NSD. CREATED = The NSD information object has been created. UPLOADING = The associated NSD content is being uploaded. PROCESSING = The associated NSD content is being processed, e.g. validation. ONBOARDED = The associated NSD content has been on-boarded. ERROR = There was an error during upload or processing of the NSD content.\n",
+ "enum": ["CREATED", "UPLOADING", "PROCESSING", "ONBOARDED", "ERROR"]
+ },
+ "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"
+ }
+ }
+ },
+ "nsdOperationalState": {
+ "type": "string",
+ "description": "The enumeration NsdOperationalStateType shall comply with the provisions defined in Table 5.5.4.3-1 of GS NFV_SOL 005. It indicates the operational state of the resource. ENABLED = The operational state of the resource is enabled. DISABLED = The operational state of the resource is disabled.\n",
+ "enum": ["ENABLED", "DISABLED"]
+ },
+ "nsdUsageState": {
+ "type": "string",
+ "description": "The enumeration NsdUsageStateType shall comply with the provisions defined in Table 5.5.4.4-1 of GS NFV-SOL 005. It indicates the usage state of the resource.IN_USE = The resource is in use.NOT_IN_USE = The resource is not-in-use.\n",
+ "enum": ["IN_USE", "NOT_IN_USE"]
+ },
+ "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": {
+ "type": "object",
+ "required": ["self", "nsd_content"],
+ "description": "Links to resources related to this resource.\n",
+ "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"
+ }
+ }
+ },
+ "nsd_content": {
+ "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
diff --git a/SOL005/NSDManagement-API/schemas/PnfdInfo.schema.json b/SOL005/NSDManagement-API/schemas/PnfdInfo.schema.json
index 9ca602167a3f1723982b07365ce2cfab3a224967..491503eb20f10e66841e1cad845d9a2d0815df59 100644
--- a/SOL005/NSDManagement-API/schemas/PnfdInfo.schema.json
+++ b/SOL005/NSDManagement-API/schemas/PnfdInfo.schema.json
@@ -1,131 +1,156 @@
{
- "type": "object",
- "required": [
- "id",
- "pnfdOnboardingState",
- "pnfdUsageState",
- "_links"
- ],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "pnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "pnfdName": {
- "description": "Name of the on-boarded PNFD. This information is copied from the PNFD content and shall be present after the PNFD content is on-boarded.\n",
- "type": "string"
- },
- "pnfdersion": {
- "description": "A Version.\n",
- "type": "string"
- },
- "pnfdProvider": {
- "description": "\"Provider of the on-boarded PNFD. This information is copied from the PNFD content and shall be present after the PNFD content is on-boarded.\"\n",
- "type": "string"
- },
- "pnfdInvariantId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "pnfdOnboardingState": {
- "type": "string",
- "description": "The enumeration PnfdOnboardingStateType shall comply with the provisions defined in Table 5.5.4.6-1 of GS-NFV SOL005. It indicates the on-boarding state of the individual PNF descriptor resource. CREATED = The PNF descriptor resource is created. UPLOADING = The associated PNFD content is being uploaded. PROCESSING = The associated PNFD content is being processed, e.g. validation. ONBOARDED = The associated PNFD content is on-boarded.\n",
- "enum": [
- "CREATED",
- "UPLOADING",
- "PROCESSING",
- "ONBOARDING"
- ]
- },
- "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": [
- "statussss",
- "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"
- }
- }
- },
- "pnfdUsageState": {
- "type": "string",
- "description": "\"The enumeration PnfdUsageStateType shall comply with the provisions defined in Table 5.5.4.7-1 of GS NFV-SOL005. It indicates the usage state of the resource.IN-USE = The resource is in use.NOT_IN_USE = The resource is not-in-use.\"\n",
- "enum": [
- "IN_USE",
- "NOT_IN_USE"
- ]
- },
- "userDefinedData": {
- "type": "array",
- "description": "User defined data for the individual PNF descriptor resource. This attribute can be modified with the PATCH method.\n",
- "items": {
- "type": "object"
- }
- },
- "_links": {
- "required": [
- "pnfd_content",
- "self"
- ],
- "type": "object",
- "description": "\"Links to resources related to this resource.\"\n",
- "properties": {
- "self": {
- "description": "This type represents a link to a resource.\n",
- "type": "object",
- "required": [
- "href"
- ],
- "properties": {
- "href": {
- "description": "URI of the referenced resource.\n",
- "type": "string",
- "format": "url"
- }
- }
- },
- "pnfd_content": {
- "description": "This type represents a link to a resource.\n",
- "type": "object",
- "required": [
- "href"
- ],
- "properties": {
- "href": {
- "description": "URI of the referenced resource.\n",
- "type": "string",
- "format": "url"
- }
- }
- }
- }
- }
- },
- "description": "\"This type represents a response for the query PNFD operation.\""
+ "type": "object",
+ "required": ["id", "pnfdOnboardingState", "pnfdUsageState", "_links"],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "pnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "pnfdName": {
+ "description": "Name of the on-boarded PNFD. This information is copied from the PNFD content and shall be present after the PNFD content is on-boarded.\n",
+ "type": "string"
+ },
+ "pnfdVersion": {
+ "description": "A Version. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "pnfdProvider": {
+ "description": "Provider of the on-boarded PNFD. This information is copied from the PNFD content and shall be present after the PNFD content is on-boarded.\n",
+ "type": "string"
+ },
+ "pnfdInvariantId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "pnfdExtInvariantId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "archiveSecurityOption": {
+ "description": "Signals the security option used by the PNFD archive as defined in clause 5.1 of ETSI GS NFV SOL 004. Valid values: OPTION_1, OPTION_2\n",
+ "type": "string",
+ "enum": ["OPTION_1", "OPTION_2"]
+ },
+ "signingCertificate": {
+ "description": "A string as defined in IETF RFC 8259.\n",
+ "type": "string"
+ },
+ "artifacts": {
+ "description": "Information about PNFD archive artifacts contained in the PNFD archive. This attribute shall not be present before the PNFD archive content is on-boarded. Otherwise, this attribute shall be present if the PNFD archive contains artifacts.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "description": "This type represents an artifact contained in a PNFD archive. It shall comply with provisions defined in Table 5.5.3.6-1.\n",
+ "required": ["artifactPath", "checksum"],
+ "properties": {
+ "artifactPath": {
+ "description": "A string as defined in IETF RFC 8259.\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"
+ }
+ }
+ },
+ "nonManoArtifactSetId": {
+ "description": "A string as defined in IETF RFC 8259.\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"
+ }
+ }
+ }
+ },
+ "pnfdOnboardingState": {
+ "type": "string",
+ "description": "The enumeration PnfdOnboardingStateType shall comply with the provisions defined in Table 5.5.4.6-1 of GS-NFV SOL005. It indicates the on-boarding state of the individual PNF descriptor resource. CREATED = The PNF descriptor resource has been created. UPLOADING = The associated PNFD content is being uploaded. PROCESSING = The associated PNFD content is being processed, e.g. validation. ONBOARDED = The associated PNFD content has been on-boarded. ERROR = There was an error during upload or processing of the associated PNFD content.\n",
+ "enum": ["CREATED", "UPLOADING", "PROCESSING", "ONBOARDING", "ERROR"]
+ },
+ "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"
+ }
+ }
+ },
+ "pnfdUsageState": {
+ "type": "string",
+ "description": "The enumeration PnfdUsageStateType shall comply with the provisions defined in Table 5.5.4.7-1 of GS NFV-SOL005. It indicates the usage state of the resource.IN-USE = The resource is in use.NOT_IN_USE = The resource is not-in-use.\n",
+ "enum": ["IN_USE", "NOT_IN_USE"]
+ },
+ "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": {
+ "required": ["pnfd_content", "self"],
+ "type": "object",
+ "description": "Links to resources related to this resource.\n",
+ "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"
+ }
+ }
+ },
+ "pnfd_content": {
+ "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"
+ }
+ }
+ }
+ }
+ }
+ },
+ "description": "This type represents a response for the query PNFD operation.\n"
}
\ No newline at end of file
diff --git a/SOL005/NSDManagement-API/schemas/PnfdInfos.schema.json b/SOL005/NSDManagement-API/schemas/PnfdInfos.schema.json
index 84b604a0bd0306fa8f10d0a87f1a07f2b999afc2..b44cd8765d76ee63a63dc67ca9fb59087fc61317 100644
--- a/SOL005/NSDManagement-API/schemas/PnfdInfos.schema.json
+++ b/SOL005/NSDManagement-API/schemas/PnfdInfos.schema.json
@@ -1,134 +1,159 @@
{
- "type": "array",
- "items": {
- "type": "object",
- "required": [
- "id",
- "pnfdOnboardingState",
- "pnfdUsageState",
- "_links"
- ],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "pnfdId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "pnfdName": {
- "description": "Name of the on-boarded PNFD. This information is copied from the PNFD content and shall be present after the PNFD content is on-boarded.\n",
- "type": "string"
- },
- "pnfdersion": {
- "description": "A Version.\n",
- "type": "string"
- },
- "pnfdProvider": {
- "description": "\"Provider of the on-boarded PNFD. This information is copied from the PNFD content and shall be present after the PNFD content is on-boarded.\"\n",
- "type": "string"
- },
- "pnfdInvariantId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "pnfdOnboardingState": {
- "type": "string",
- "description": "The enumeration PnfdOnboardingStateType shall comply with the provisions defined in Table 5.5.4.6-1 of GS-NFV SOL005. It indicates the on-boarding state of the individual PNF descriptor resource. CREATED = The PNF descriptor resource is created. UPLOADING = The associated PNFD content is being uploaded. PROCESSING = The associated PNFD content is being processed, e.g. validation. ONBOARDED = The associated PNFD content is on-boarded.\n",
- "enum": [
- "CREATED",
- "UPLOADING",
- "PROCESSING",
- "ONBOARDING"
- ]
- },
- "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": [
- "statussss",
- "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"
- }
- }
- },
- "pnfdUsageState": {
- "type": "string",
- "description": "\"The enumeration PnfdUsageStateType shall comply with the provisions defined in Table 5.5.4.7-1 of GS NFV-SOL005. It indicates the usage state of the resource.IN-USE = The resource is in use.NOT_IN_USE = The resource is not-in-use.\"\n",
- "enum": [
- "IN_USE",
- "NOT_IN_USE"
- ]
- },
- "userDefinedData": {
- "type": "array",
- "description": "User defined data for the individual PNF descriptor resource. This attribute can be modified with the PATCH method.\n",
- "items": {
- "type": "object"
- }
- },
- "_links": {
- "required": [
- "pnfd_content",
- "self"
- ],
- "type": "object",
- "description": "\"Links to resources related to this resource.\"\n",
- "properties": {
- "self": {
- "description": "This type represents a link to a resource.\n",
- "type": "object",
- "required": [
- "href"
- ],
- "properties": {
- "href": {
- "description": "URI of the referenced resource.\n",
- "type": "string",
- "format": "url"
- }
- }
- },
- "pnfd_content": {
- "description": "This type represents a link to a resource.\n",
- "type": "object",
- "required": [
- "href"
- ],
- "properties": {
- "href": {
- "description": "URI of the referenced resource.\n",
- "type": "string",
- "format": "url"
- }
- }
- }
- }
- }
- },
- "description": "\"This type represents a response for the query PNFD operation.\""
- }
+ "type": "array",
+ "items": {
+ "type": "object",
+ "required": ["id", "pnfdOnboardingState", "pnfdUsageState", "_links"],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "pnfdId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "pnfdName": {
+ "description": "Name of the on-boarded PNFD. This information is copied from the PNFD content and shall be present after the PNFD content is on-boarded.\n",
+ "type": "string"
+ },
+ "pnfdVersion": {
+ "description": "A Version. Representation: string of variable length.\n",
+ "type": "string"
+ },
+ "pnfdProvider": {
+ "description": "Provider of the on-boarded PNFD. This information is copied from the PNFD content and shall be present after the PNFD content is on-boarded.\n",
+ "type": "string"
+ },
+ "pnfdInvariantId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "pnfdExtInvariantId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "archiveSecurityOption": {
+ "description": "Signals the security option used by the PNFD archive as defined in clause 5.1 of ETSI GS NFV SOL 004. Valid values: OPTION_1, OPTION_2\n",
+ "type": "string",
+ "enum": ["OPTION_1", "OPTION_2"]
+ },
+ "signingCertificate": {
+ "description": "A string as defined in IETF RFC 8259.\n",
+ "type": "string"
+ },
+ "artifacts": {
+ "description": "Information about PNFD archive artifacts contained in the PNFD archive. This attribute shall not be present before the PNFD archive content is on-boarded. Otherwise, this attribute shall be present if the PNFD archive contains artifacts.\n",
+ "type": "array",
+ "items": {
+ "type": "object",
+ "description": "This type represents an artifact contained in a PNFD archive. It shall comply with provisions defined in Table 5.5.3.6-1.\n",
+ "required": ["artifactPath", "checksum"],
+ "properties": {
+ "artifactPath": {
+ "description": "A string as defined in IETF RFC 8259.\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"
+ }
+ }
+ },
+ "nonManoArtifactSetId": {
+ "description": "A string as defined in IETF RFC 8259.\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"
+ }
+ }
+ }
+ },
+ "pnfdOnboardingState": {
+ "type": "string",
+ "description": "The enumeration PnfdOnboardingStateType shall comply with the provisions defined in Table 5.5.4.6-1 of GS-NFV SOL005. It indicates the on-boarding state of the individual PNF descriptor resource. CREATED = The PNF descriptor resource has been created. UPLOADING = The associated PNFD content is being uploaded. PROCESSING = The associated PNFD content is being processed, e.g. validation. ONBOARDED = The associated PNFD content has been on-boarded. ERROR = There was an error during upload or processing of the associated PNFD content.\n",
+ "enum": ["CREATED", "UPLOADING", "PROCESSING", "ONBOARDING", "ERROR"]
+ },
+ "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"
+ }
+ }
+ },
+ "pnfdUsageState": {
+ "type": "string",
+ "description": "The enumeration PnfdUsageStateType shall comply with the provisions defined in Table 5.5.4.7-1 of GS NFV-SOL005. It indicates the usage state of the resource.IN-USE = The resource is in use.NOT_IN_USE = The resource is not-in-use.\n",
+ "enum": ["IN_USE", "NOT_IN_USE"]
+ },
+ "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": {
+ "required": ["pnfd_content", "self"],
+ "type": "object",
+ "description": "Links to resources related to this resource.\n",
+ "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"
+ }
+ }
+ },
+ "pnfd_content": {
+ "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"
+ }
+ }
+ }
+ }
+ }
+ },
+ "description": "This type represents a response for the query PNFD operation.\n"
+ }
}
\ No newline at end of file
diff --git a/SOL005/NSFaultManagement-API/Alarms.robot b/SOL005/NSFaultManagement-API/Alarms.robot
index f03a3fd079b86099b7c7fa1bc6f0e780ddd6b08f..6b81ff9de336c50a8cdac22d0c691f6f9483290b 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] v3.6.1
+ ... Reference: Clause 8.4.2.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.2.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.2.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.2.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.2.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.2.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.2.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.2.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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 19fd62840383bdc4a31f05aa8eed007e38362538..7d2e9a46904f8f0417e938464190de45855d3e06 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] v3.5.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.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 7ae2c6d06da5e4abb920ad3f6e6b84e6eb281d48..70318462838a3b21a096b2a86850058ac9f86dca 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] v3.6.1
+ ... Reference: Clause 8.4.3.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.3.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.3.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.3.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions:
@@ -103,7 +103,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 for Fault management individual alarm on NFV
... Pre-conditions: none
- ... Reference: Clause 8.4.3.3.5 - ETSI GS NFV-SOL 005 [3] v3.6.1
+ ... Reference: Clause 8.4.3.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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 dae7a7bafa17fbe0d8b94b81a4eea90bdd7427cf..8b2f372faed578303588a9ca17537e31504145fc 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] v3.6.1
+ ... Reference: Clause 8.4.5.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.5.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.5.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.5.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: subscription is not deleted
diff --git a/SOL005/NSFaultManagement-API/NotificationEndpoint.robot b/SOL005/NSFaultManagement-API/NotificationEndpoint.robot
index 9794778006ab6479c45fa6910fe6093c2fa8c1a3..099e56302846958fa1cc8a67b741edbf2a710167 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] v3.6.1
+ ... Reference: Clause 8.4.6.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.6.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.6.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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 3deda11a08e58bec18f87fc0625a8590f223ebff..34910d3b87091e1744709f6046cbb5d339bb8ab3 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] v3.6.1
+ ... Reference: Clause 8.4.6.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.6.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.6.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.6.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.6.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.6.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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 0e2850de1508737cfec77b94da9059584eae2fce..eb6fe275e8381407aab4c0838565c3b82fec5ad2 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] v3.6.1
+ ... Reference: Clause 8.4.4.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.4.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.4.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.4.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.4.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 8.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -291,7 +291,7 @@ Create a new alarm subscription - Unprocessable Entity
... Test title: Create a new alarm subscription- Unprocessable Entity
... 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] v3.6.1
+ ... Reference: Clause 8.4.4.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/NSFaultManagement-API/schemas/alarm.schema.json b/SOL005/NSFaultManagement-API/schemas/alarm.schema.json
index 5aadd14cd7b2e0f32beb78a7d6084972770added..c57cc1d4ca5ada92be31763a25284ed613ef6d66 100644
--- a/SOL005/NSFaultManagement-API/schemas/alarm.schema.json
+++ b/SOL005/NSFaultManagement-API/schemas/alarm.schema.json
@@ -1,189 +1,176 @@
{
- "description": "The alarm data type encapsulates information about an alarm. It shall comply with the provisions defined in Table 8.5.2.4-1\n",
- "type": "object",
- "required": [
- "id",
- "managedObjectId",
- "alarmRaisedTime",
- "ackState",
- "perceivedSeverity",
- "eventTime",
- "eventType",
- "probableCause",
- "isRootCause",
- "_links"
- ],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "managedObjectId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "rootCauseFaultyComponent": {
- "description": "This type represents the faulty component that has a negative impact on an NS. It shall comply with the provisions defined in Table 8.5.3.4-1.\n",
- "type": "object",
- "properties": {
- "faultyNestedNsInstanceId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "faultyResourceType": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "faultyNsVirtualLinkInstanceId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- }
- }
- },
- "rootCauseFaultyResource": {
- "description": "This type represents the faulty virtual resources that have a negative impact on a NS.\n",
- "type": "object",
- "required": [
- "faultyResource",
- "faultyResourceType"
- ],
- "properties": {
- "faultyResource": {
- "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.\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 other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Type of the resource in the scope of the VIM or the resource provider. The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle.\n",
- "type": "string"
- }
- }
- },
- "faultyResourceType": {
- "description": "The enumeration FaultyResourceType represents those types of faulty resource. Acceptable values are: - COMPUTE - Virtual compute resource. - STORAGE - Virtual storage resource. - NETWORK - Virtual network resource.\n",
- "type": "string",
- "enum": [
- "COMPUTE",
- "STORAGE",
- "NETWORK"
- ]
- }
- }
- },
- "alarmRaisedTime": {
- "description": "Date-time stamp. Representation: String formatted according toas defined by the date-time production in IETF RFC 3339.\n",
- "format": "date-time"
- },
- "alarmChangedTime": {
- "description": "Date-time stamp. Representation: String formatted according toas defined by the date-time production in IETF RFC 3339.\n",
- "format": "date-time"
- },
- "alarmClearedTime": {
- "description": "Date-time stamp. Representation: String formatted according toas defined by the date-time production in IETF RFC 3339.\n",
- "format": "date-time"
- },
- "alarmAcknowledgedTime": {
- "description": "Date-time stamp. Representation: String formatted according toas defined by the date-time production in IETF RFC 3339.\n",
- "format": "date-time"
- },
- "ackState": {
- "description": "Acknowledgment state of the alarm. Permitted values: UNACKNOWLEDGED ACKNOWLEDGED\n",
- "type": "string",
- "enum": [
- "UNACKNOWLEDGED",
- "ACKNOWLEDGED"
- ]
- },
- "perceivedSeverity": {
- "description": "Indicates the relative level of urgency for operator attention. * CRITICAL: The Critical severity level indicates that a service\n affecting condition has occurred and an immediate corrective action\n is required. Such a severity can be reported, for example, when a\n managed object becomes totally out of service and its capability needs\n to be restored (ITU-T Recommendation X.733).\n* MAJOR: The Major severity level indicates that a service affecting\n condition has developed and an urgent corrective action is required.\n Such a severity can be reported, for example, when there is a severe\n degradation in the capability of the managed object and its full\n capability needs to be restored (ITU-T Recommendation X.733).\n* MINOR: The Minor severity level indicates the existence of a\n non-service affecting fault condition and that corrective action\n should be taken in order to prevent a more serious (for example,\n service affecting) fault. Such a severity can be reported, for\n example, when the detected alarm condition is not currently degrading\n the capacity of the managed object (ITU-T Recommendation X.733).\n* WARNING: The Warning severity level indicates the detection of a\n potential or impending service affecting fault, before any significant\n effects have been felt. Action should be taken to further diagnose (if\n necessary) and correct the problem in order to prevent it from\n becoming a more serious service affecting fault (ITU-T Recommendation\n X.733).\n* INDETERMINATE: The Indeterminate severity level indicates that the\n severity level cannot be determined (ITU-T Recommendation X.733).\n* CLEARED: The Cleared severity level indicates the clearing of one or\n more previously reported alarms. This alarm clears all alarms for this\n managed object that have the same Alarm type, Probable cause and\n Specific problems (if given) (ITU-T Recommendation X.733).\n",
- "type": "string",
- "enum": [
- "CRITICAL",
- "MAJOR",
- "MINOR",
- "WARNING",
- "INDETERMINATE",
- "CLEARED"
- ]
- },
- "eventTime": {
- "description": "Date-time stamp. Representation: String formatted according toas defined by the date-time production in IETF RFC 3339.\n",
- "format": "date-time"
- },
- "eventType": {
- "description": "The enumeration EventType represents those types of events that trigger an alarm. - COMMUNICATIONS_ALARM: An alarm of this type is associated with the\n procedure and/or process required conveying information from one point\n to another (ITU-T Recommendation X.733).\n- PROCESSING_ERROR_ALARM: An alarm of this type is associated with a\n software or processing fault (ITU-T Recommendation X.733).\n- ENVIRONMENTAL_ALARM: An alarm of this type is associated with a\n condition related to an enclosure in which the equipment resides\n (ITU-T Recommendation X.733).\n- QOS_ALARM: An alarm of this type is associated with degradation in the\n quality of a service (ITU-T Recommendation X.733).\n- EQUIPMENT_ALARM: An alarm of this type is associated with an equipment\n fault (ITU-T Recommendation X.733).\n",
- "type": "string",
- "enum": [
- "COMMUNICATIONS_ALARM",
- "PROCESSING_ERROR_ALARM",
- "ENVIRONMENTAL_ALARM",
- "QOS_ALARM",
- "EQUIPMENT_ALARM"
- ]
- },
- "faultType": {
- "description": "Additional information to clarify the type of the fault.\n",
- "type": "string"
- },
- "probableCause": {
- "description": "Information about the probable cause of the fault.\n",
- "type": "string"
- },
- "isRootCause": {
- "description": "Attribute indicating if this fault is the root for other correlated alarms. If TRUE, then the alarms listed in the attribute CorrelatedAlarmId are caused by this fault.\n",
- "type": "boolean"
- },
- "correlatedAlarmIds": {
- "description": "List of identifiers of other alarms correlated to this fault.\n",
- "type": "array",
- "items": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- }
- },
- "faultDetails": {
- "description": "Provides additional information about the fault..\n",
- "type": "array",
- "items": {
- "type": "string"
- }
- },
- "_links": {
- "description": "Links for 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
+ "description": "The alarm data type encapsulates information about an alarm. It shall comply with the provisions defined in Table 8.5.2.4-1\n",
+ "type": "object",
+ "required": ["id", "managedObjectId", "alarmRaisedTime", "ackState", "perceivedSeverity", "eventTime", "eventType", "probableCause", "isRootCause", "_links"],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "managedObjectId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "rootCauseFaultyComponent": {
+ "description": "This type represents the faulty component that has a negative impact on an NS. It shall comply with the provisions defined in Table 8.5.3.4-1. NOTE:\tAt least one of the attributes shall be present.\n",
+ "type": "object",
+ "properties": {
+ "faultyNestedNsInstanceId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "faultyResourceType": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "faultyNsVirtualLinkInstanceId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ }
+ },
+ "rootCauseFaultyResource": {
+ "description": "This type represents the faulty virtual resources that have a negative impact on a NS.\n",
+ "type": "object",
+ "required": ["faultyResource", "faultyResourceType"],
+ "properties": {
+ "faultyResource": {
+ "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"
+ }
+ }
+ },
+ "faultyResourceType": {
+ "description": "The enumeration FaultyResourceType represents those types of faulty resource. Acceptable values are: - COMPUTE - Virtual compute resource. - STORAGE - Virtual storage resource. - NETWORK - Virtual network resource.\n",
+ "type": "string",
+ "enum": ["COMPUTE", "STORAGE", "NETWORK"]
+ }
+ }
+ },
+ "alarmRaisedTime": {
+ "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"
+ },
+ "alarmChangedTime": {
+ "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"
+ },
+ "alarmClearedTime": {
+ "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"
+ },
+ "alarmAcknowledgedTime": {
+ "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"
+ },
+ "ackState": {
+ "description": "Acknowledgment state of the alarm. Permitted values: UNACKNOWLEDGED ACKNOWLEDGED\n",
+ "type": "string",
+ "enum": ["UNACKNOWLEDGED", "ACKNOWLEDGED"]
+ },
+ "perceivedSeverity": {
+ "description": "Indicates the relative level of urgency for operator attention. * CRITICAL: The Critical severity level indicates that a service affecting condition has occurred and an immediate corrective action\n is required. Such a severity can be reported, for example, when a\n managed object becomes totally out of service and its capability needs\n to be restored (ITU-T Recommendation X.733).\n* MAJOR: The Major severity level indicates that a service affecting condition has developed and an urgent corrective action is required.\n Such a severity can be reported, for example, when there is a severe\n degradation in the capability of the managed object and its full\n capability needs to be restored (ITU-T Recommendation X.733).\n* MINOR: The Minor severity level indicates the existence of a non-service affecting fault condition and that corrective action\n should be taken in order to prevent a more serious (for example,\n service affecting) fault. Such a severity can be reported, for\n example, when the detected alarm condition is not currently degrading\n the capacity of the managed object (ITU-T Recommendation X.733).\n* WARNING: The Warning severity level indicates the detection of a potential or impending service affecting fault, before any significant\n effects have been felt. Action should be taken to further diagnose (if\n necessary) and correct the problem in order to prevent it from\n becoming a more serious service affecting fault (ITU-T Recommendation\n X.733).\n* INDETERMINATE: The Indeterminate severity level indicates that the severity level cannot be determined (ITU-T Recommendation X.733).\n* CLEARED: The Cleared severity level indicates the clearing of one or more previously reported alarms. This alarm clears all alarms for this\n managed object that have the same Alarm type, Probable cause and\n Specific problems (if given) (ITU-T Recommendation X.733).\n",
+ "type": "string",
+ "enum": ["CRITICAL", "MAJOR", "MINOR", "WARNING", "INDETERMINATE", "CLEARED"]
+ },
+ "eventTime": {
+ "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"
+ },
+ "eventType": {
+ "description": "The enumeration EventType represents those types of events that trigger an alarm. - COMMUNICATIONS_ALARM: An alarm of this type is associated with the procedure and/or process required conveying information from one point\n to another (ITU-T Recommendation X.733).\n- PROCESSING_ERROR_ALARM: An alarm of this type is associated with a software or processing fault (ITU-T Recommendation X.733).\n- ENVIRONMENTAL_ALARM: An alarm of this type is associated with a condition related to an enclosure in which the equipment resides\n (ITU-T Recommendation X.733).\n- QOS_ALARM: An alarm of this type is associated with degradation in the quality of a service (ITU-T Recommendation X.733).\n- EQUIPMENT_ALARM: An alarm of this type is associated with an equipment fault (ITU-T Recommendation X.733).\n",
+ "type": "string",
+ "enum": ["COMMUNICATIONS_ALARM", "PROCESSING_ERROR_ALARM", "ENVIRONMENTAL_ALARM", "QOS_ALARM", "EQUIPMENT_ALARM"]
+ },
+ "faultType": {
+ "description": "Additional information to clarify the type of the fault.\n",
+ "type": "string"
+ },
+ "probableCause": {
+ "description": "Information about the probable cause of the fault.\n",
+ "type": "string"
+ },
+ "isRootCause": {
+ "description": "Attribute indicating if this fault is the root for other correlated alarms. If TRUE, then the alarms listed in the attribute CorrelatedAlarmId are caused by this fault.\n",
+ "type": "boolean"
+ },
+ "correlatedAlarmIds": {
+ "description": "List of identifiers of other alarms correlated to this fault.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ },
+ "faultDetails": {
+ "description": "Provides additional information about the fault..\n",
+ "type": "array",
+ "items": {
+ "type": "string"
+ }
+ },
+ "_links": {
+ "description": "Links for 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
diff --git a/SOL005/NSFaultManagement-API/schemas/alarms.schema.json b/SOL005/NSFaultManagement-API/schemas/alarms.schema.json
index b43c87fb1721b96df740c6947c620eb715767bc7..6d4c27e04aca9a14cfc0ef61f6b068f4498db4b0 100644
--- a/SOL005/NSFaultManagement-API/schemas/alarms.schema.json
+++ b/SOL005/NSFaultManagement-API/schemas/alarms.schema.json
@@ -1,192 +1,180 @@
{
- "type": "array",
- "items": {
- "description": "The alarm data type encapsulates information about an alarm. It shall comply with the provisions defined in Table 8.5.2.4-1\n",
- "type": "object",
- "required": [
- "id",
- "managedObjectId",
- "alarmRaisedTime",
- "ackState",
- "perceivedSeverity",
- "eventTime",
- "eventType",
- "probableCause",
- "isRootCause",
- "_links"
- ],
- "properties": {
- "id": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "managedObjectId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "rootCauseFaultyComponent": {
- "description": "This type represents the faulty component that has a negative impact on an NS. It shall comply with the provisions defined in Table 8.5.3.4-1.\n",
- "type": "object",
- "properties": {
- "faultyNestedNsInstanceId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "faultyResourceType": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- },
- "faultyNsVirtualLinkInstanceId": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- }
- }
- },
- "rootCauseFaultyResource": {
- "description": "This type represents the faulty virtual resources that have a negative impact on a NS.\n",
- "type": "object",
- "required": [
- "faultyResource",
- "faultyResourceType"
- ],
- "properties": {
- "faultyResource": {
- "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.\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 other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Type of the resource in the scope of the VIM or the resource provider. The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle.\n",
- "type": "string"
- }
- }
- },
- "faultyResourceType": {
- "description": "The enumeration FaultyResourceType represents those types of faulty resource. Acceptable values are: - COMPUTE - Virtual compute resource. - STORAGE - Virtual storage resource. - NETWORK - Virtual network resource.\n",
- "type": "string",
- "enum": [
- "COMPUTE",
- "STORAGE",
- "NETWORK"
- ]
- }
- }
- },
- "alarmRaisedTime": {
- "description": "Date-time stamp. Representation: String formatted according toas defined by the date-time production in IETF RFC 3339.\n",
- "format": "date-time"
- },
- "alarmChangedTime": {
- "description": "Date-time stamp. Representation: String formatted according toas defined by the date-time production in IETF RFC 3339.\n",
- "format": "date-time"
- },
- "alarmClearedTime": {
- "description": "Date-time stamp. Representation: String formatted according toas defined by the date-time production in IETF RFC 3339.\n",
- "format": "date-time"
- },
- "alarmAcknowledgedTime": {
- "description": "Date-time stamp. Representation: String formatted according toas defined by the date-time production in IETF RFC 3339.\n",
- "format": "date-time"
- },
- "ackState": {
- "description": "Acknowledgment state of the alarm. Permitted values: UNACKNOWLEDGED ACKNOWLEDGED\n",
- "type": "string",
- "enum": [
- "UNACKNOWLEDGED",
- "ACKNOWLEDGED"
- ]
- },
- "perceivedSeverity": {
- "description": "Indicates the relative level of urgency for operator attention. * CRITICAL: The Critical severity level indicates that a service\n affecting condition has occurred and an immediate corrective action\n is required. Such a severity can be reported, for example, when a\n managed object becomes totally out of service and its capability needs\n to be restored (ITU-T Recommendation X.733).\n* MAJOR: The Major severity level indicates that a service affecting\n condition has developed and an urgent corrective action is required.\n Such a severity can be reported, for example, when there is a severe\n degradation in the capability of the managed object and its full\n capability needs to be restored (ITU-T Recommendation X.733).\n* MINOR: The Minor severity level indicates the existence of a\n non-service affecting fault condition and that corrective action\n should be taken in order to prevent a more serious (for example,\n service affecting) fault. Such a severity can be reported, for\n example, when the detected alarm condition is not currently degrading\n the capacity of the managed object (ITU-T Recommendation X.733).\n* WARNING: The Warning severity level indicates the detection of a\n potential or impending service affecting fault, before any significant\n effects have been felt. Action should be taken to further diagnose (if\n necessary) and correct the problem in order to prevent it from\n becoming a more serious service affecting fault (ITU-T Recommendation\n X.733).\n* INDETERMINATE: The Indeterminate severity level indicates that the\n severity level cannot be determined (ITU-T Recommendation X.733).\n* CLEARED: The Cleared severity level indicates the clearing of one or\n more previously reported alarms. This alarm clears all alarms for this\n managed object that have the same Alarm type, Probable cause and\n Specific problems (if given) (ITU-T Recommendation X.733).\n",
- "type": "string",
- "enum": [
- "CRITICAL",
- "MAJOR",
- "MINOR",
- "WARNING",
- "INDETERMINATE",
- "CLEARED"
- ]
- },
- "eventTime": {
- "description": "Date-time stamp. Representation: String formatted according toas defined by the date-time production in IETF RFC 3339.\n",
- "format": "date-time"
- },
- "eventType": {
- "description": "The enumeration EventType represents those types of events that trigger an alarm. - COMMUNICATIONS_ALARM: An alarm of this type is associated with the\n procedure and/or process required conveying information from one point\n to another (ITU-T Recommendation X.733).\n- PROCESSING_ERROR_ALARM: An alarm of this type is associated with a\n software or processing fault (ITU-T Recommendation X.733).\n- ENVIRONMENTAL_ALARM: An alarm of this type is associated with a\n condition related to an enclosure in which the equipment resides\n (ITU-T Recommendation X.733).\n- QOS_ALARM: An alarm of this type is associated with degradation in the\n quality of a service (ITU-T Recommendation X.733).\n- EQUIPMENT_ALARM: An alarm of this type is associated with an equipment\n fault (ITU-T Recommendation X.733).\n",
- "type": "string",
- "enum": [
- "COMMUNICATIONS_ALARM",
- "PROCESSING_ERROR_ALARM",
- "ENVIRONMENTAL_ALARM",
- "QOS_ALARM",
- "EQUIPMENT_ALARM"
- ]
- },
- "faultType": {
- "description": "Additional information to clarify the type of the fault.\n",
- "type": "string"
- },
- "probableCause": {
- "description": "Information about the probable cause of the fault.\n",
- "type": "string"
- },
- "isRootCause": {
- "description": "Attribute indicating if this fault is the root for other correlated alarms. If TRUE, then the alarms listed in the attribute CorrelatedAlarmId are caused by this fault.\n",
- "type": "boolean"
- },
- "correlatedAlarmIds": {
- "description": "List of identifiers of other alarms correlated to this fault.\n",
- "type": "array",
- "items": {
- "description": "An identifier with the intention of being globally unique.\n",
- "type": "string"
- }
- },
- "faultDetails": {
- "description": "Provides additional information about the fault..\n",
- "type": "array",
- "items": {
- "type": "string"
- }
- },
- "_links": {
- "description": "Links for 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"
- }
- }
- }
- }
- }
- }
- }
+ "type": "array",
+ "items": {
+
+ "description": "The alarm data type encapsulates information about an alarm. It shall comply with the provisions defined in Table 8.5.2.4-1\n",
+ "type": "object",
+ "required": ["id", "managedObjectId", "alarmRaisedTime", "ackState", "perceivedSeverity", "eventTime", "eventType", "probableCause", "isRootCause", "_links"],
+ "properties": {
+ "id": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "managedObjectId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "rootCauseFaultyComponent": {
+ "description": "This type represents the faulty component that has a negative impact on an NS. It shall comply with the provisions defined in Table 8.5.3.4-1. NOTE:\tAt least one of the attributes shall be present.\n",
+ "type": "object",
+ "properties": {
+ "faultyNestedNsInstanceId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "faultyResourceType": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ },
+ "faultyNsVirtualLinkInstanceId": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ }
+ },
+ "rootCauseFaultyResource": {
+ "description": "This type represents the faulty virtual resources that have a negative impact on a NS.\n",
+ "type": "object",
+ "required": ["faultyResource", "faultyResourceType"],
+ "properties": {
+ "faultyResource": {
+ "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"
+ }
+ }
+ },
+ "faultyResourceType": {
+ "description": "The enumeration FaultyResourceType represents those types of faulty resource. Acceptable values are: - COMPUTE - Virtual compute resource. - STORAGE - Virtual storage resource. - NETWORK - Virtual network resource.\n",
+ "type": "string",
+ "enum": ["COMPUTE", "STORAGE", "NETWORK"]
+ }
+ }
+ },
+ "alarmRaisedTime": {
+ "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"
+ },
+ "alarmChangedTime": {
+ "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"
+ },
+ "alarmClearedTime": {
+ "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"
+ },
+ "alarmAcknowledgedTime": {
+ "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"
+ },
+ "ackState": {
+ "description": "Acknowledgment state of the alarm. Permitted values: UNACKNOWLEDGED ACKNOWLEDGED\n",
+ "type": "string",
+ "enum": ["UNACKNOWLEDGED", "ACKNOWLEDGED"]
+ },
+ "perceivedSeverity": {
+ "description": "Indicates the relative level of urgency for operator attention. * CRITICAL: The Critical severity level indicates that a service affecting condition has occurred and an immediate corrective action\n is required. Such a severity can be reported, for example, when a\n managed object becomes totally out of service and its capability needs\n to be restored (ITU-T Recommendation X.733).\n* MAJOR: The Major severity level indicates that a service affecting condition has developed and an urgent corrective action is required.\n Such a severity can be reported, for example, when there is a severe\n degradation in the capability of the managed object and its full\n capability needs to be restored (ITU-T Recommendation X.733).\n* MINOR: The Minor severity level indicates the existence of a non-service affecting fault condition and that corrective action\n should be taken in order to prevent a more serious (for example,\n service affecting) fault. Such a severity can be reported, for\n example, when the detected alarm condition is not currently degrading\n the capacity of the managed object (ITU-T Recommendation X.733).\n* WARNING: The Warning severity level indicates the detection of a potential or impending service affecting fault, before any significant\n effects have been felt. Action should be taken to further diagnose (if\n necessary) and correct the problem in order to prevent it from\n becoming a more serious service affecting fault (ITU-T Recommendation\n X.733).\n* INDETERMINATE: The Indeterminate severity level indicates that the severity level cannot be determined (ITU-T Recommendation X.733).\n* CLEARED: The Cleared severity level indicates the clearing of one or more previously reported alarms. This alarm clears all alarms for this\n managed object that have the same Alarm type, Probable cause and\n Specific problems (if given) (ITU-T Recommendation X.733).\n",
+ "type": "string",
+ "enum": ["CRITICAL", "MAJOR", "MINOR", "WARNING", "INDETERMINATE", "CLEARED"]
+ },
+ "eventTime": {
+ "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"
+ },
+ "eventType": {
+ "description": "The enumeration EventType represents those types of events that trigger an alarm. - COMMUNICATIONS_ALARM: An alarm of this type is associated with the procedure and/or process required conveying information from one point\n to another (ITU-T Recommendation X.733).\n- PROCESSING_ERROR_ALARM: An alarm of this type is associated with a software or processing fault (ITU-T Recommendation X.733).\n- ENVIRONMENTAL_ALARM: An alarm of this type is associated with a condition related to an enclosure in which the equipment resides\n (ITU-T Recommendation X.733).\n- QOS_ALARM: An alarm of this type is associated with degradation in the quality of a service (ITU-T Recommendation X.733).\n- EQUIPMENT_ALARM: An alarm of this type is associated with an equipment fault (ITU-T Recommendation X.733).\n",
+ "type": "string",
+ "enum": ["COMMUNICATIONS_ALARM", "PROCESSING_ERROR_ALARM", "ENVIRONMENTAL_ALARM", "QOS_ALARM", "EQUIPMENT_ALARM"]
+ },
+ "faultType": {
+ "description": "Additional information to clarify the type of the fault.\n",
+ "type": "string"
+ },
+ "probableCause": {
+ "description": "Information about the probable cause of the fault.\n",
+ "type": "string"
+ },
+ "isRootCause": {
+ "description": "Attribute indicating if this fault is the root for other correlated alarms. If TRUE, then the alarms listed in the attribute CorrelatedAlarmId are caused by this fault.\n",
+ "type": "boolean"
+ },
+ "correlatedAlarmIds": {
+ "description": "List of identifiers of other alarms correlated to this fault.\n",
+ "type": "array",
+ "items": {
+ "description": "An identifier with the intention of being globally unique.\n",
+ "type": "string"
+ }
+ },
+ "faultDetails": {
+ "description": "Provides additional information about the fault..\n",
+ "type": "array",
+ "items": {
+ "type": "string"
+ }
+ },
+ "_links": {
+ "description": "Links for 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
diff --git a/SOL005/NSLCMCoordination-API/ApiVersion.robot b/SOL005/NSLCMCoordination-API/ApiVersion.robot
index 9343f79aad1fb258d8a794cc9d52fa6a833c5794..2766a31ca085ed2dd256f9be3e5cb5bdabd0847b 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] v3.5.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.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 cbee6a52056727e9b1a98ae958b758ddd9b5d063..14f2befc326dcb23e89d2a0e83012a7caa710f6e 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] v3.6.1
+ ... Reference: Clause 12.4.4.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 12.4.4.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 12.4.4.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 12.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 12.4.4.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 12.4.4.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 12.4.4.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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 fed441e366ec79accd6489e5965e089b98480fc4..cfb9ef73018d87fda7ccb47bd0d20daf8f76e5ea 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] v3.6.1
+ ... Reference: Clause 12.4.2.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 12.4.2.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 12.4.2.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 12.4.2.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 12.4.2.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 12.4.2.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 12.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 12.4.2.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 12.4.2.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 12.4.2.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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 b98414ac604caf1cbfd12ef4040cc5f36b9d3d21..e31cdcf44adabf2cb6336e6c608f80eb316669f2 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] v3.6.1
+ ... Reference: Clause 12.4.3.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 12.4.3.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 12.4.3.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 12.4.3.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 12.4.3.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 12.4.3.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 12.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 12.4.3.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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 2427766bb02e918b7dbf694503b7a524a1d7a81d..5434374b67a94b6c151b287d5dedcbe20472cd56 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] v3.5.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.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 ff4b85ed4a5ec93a446979f604c6838cb102b95c..b3c5c4563a078882a709d0df48f8da69a63328f7 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] v3.6.1
+ ... Reference: Clause 6.4.15.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.15.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.15.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.15.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.15.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.15.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.15.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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 52bf55bb39d1e451f44c46e97e0ecf58881cbad6..4e63abe8c9369e536564e05fb88b7a17b7aa1086 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] v3.6.1
+ ... Reference: Clause 6.4.13.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.13.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.13.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.13.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.13.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.14.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.14.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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 1da52b45cad93c279c96433ab3c4692bcadca69b..5e404603a05a859118ca15b71c63c2526dd8af7f 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] v3.6.1
+ ... Reference: Clause 6.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clauses 6.4.2.3.1 and 5.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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 be95463748bfc2ecc0237d43182e4133b6344d91..6d3fba20fb1a575ffa3bd036f9d0ce32a7274631 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] v3.6.1
+ ... Reference: Clause 6.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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 08c115144741a570d7a6df6722a17f8e4c451c8b..f4ee17dfc452acafc49d518949af9e38012c3dbc 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] v3.6.1
+ ... Reference: Clause 6.4.14.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.14.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.14.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.14.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.14.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.14.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.14.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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 af824ea7c1f1b76f144134cd295b3ff534fe4f7e..4991bbb487eb04e23e7ad6b31ea00073e5d1bdb0 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] v3.6.1
+ ... Reference: Clause 6.4.7.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.7.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.7.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.7.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.7.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.7.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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 42a522eccb9eef714b5e764e7848d65a5bf17689..bd55a78d50685954d238339e4a66b419df3149c6 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] v3.6.1
+ ... Reference: Clause 6.4.7 - ETSI GS NFV-SOL 005 [3] v4.3.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 702e8d2017960738cc45041524a0fa1b42a4650d..c6953f83b0712eaf252801dc9c5ded893aeb34dc 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] v3.6.1
+ ... Reference: Clause 6.4.3.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.3.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.3.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.3.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.3.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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 21123f1c3dd3ef1b1f6f9b331ca8b62e12d042a6..87aa0d02fe7cac46b9969bfdac9f25ad9a1adc1b 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] v3.6.1
+ ... Reference: Clause 6.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.10.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -38,31 +38,44 @@ 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] v3.6.1
+ ... Reference: Clause 6.4.10.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
PUT Individual NS LCM OP Occurrence
Check HTTP Response Status Code Is 405
-PATCH status information about Individual NS LCM occurrences - Method not implemented
+PATCH status information about Individual NS LCM occurrences
[Documentation] Test ID: 5.3.2.9.4
- ... Test title: PATCH status information about Individual 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.10.3.4 - ETSI GS NFV-SOL 005 [3] v3.6.1
+ ... 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
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
PATCH Individual NS LCM OP Occurrence
- Check HTTP Response Status Code Is 405
+ Check HTTP Response Status Code Is 204
+
+PATCH status information about Individual NS LCM occurrences - scheduled operation already started
+ [Documentation] Test ID: 5.3.2.9.4b
+ ... 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
+ ... Config ID: Config_prod_NFVO
+ ... Applicability: none
+ ... Post-Conditions: none
+ PATCH Individual NS LCM OP Occurrence of Already Started Scheduled Operation
+ Check HTTP Response Status Code Is 409
+ 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] v3.6.1
+ ... Reference: Clause 6.4.10.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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 df447ea4f04ffa0f57c97b58a48a6d812d6ff298..f090495de1c3937d2869f97f86326edc8d9e890a 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] v3.6.1
+ ... Reference: Clause 6.4.17.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.17.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.17.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.17.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.17.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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 91c0c64ed8c18009774f340bc7c215810eb3cced..f118fb6eaa0a960ddb75641915a8de568aa258db 100644
--- a/SOL005/NSLifecycleManagement-API/IndividualVNFSnapshot.robot
+++ b/SOL005/NSLifecycleManagement-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 6.4.20.3.1 - ETSI GS NFV-SOL 005 [3] v3.6.1
+ ... Reference: Clause 6.4.20.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... 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 6.4.20.3.2 - ETSI GS NFV-SOL 005 [3] v3.6.1
+ ... Reference: Clause 6.4.20.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -32,7 +32,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 6.4.20.3.2 - ETSI GS NFV-SOL 005 [3] v3.6.1
+ ... Reference: Clause 6.4.20.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -45,7 +45,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 6.4.20.3.3 - ETSI GS NFV-SOL 005 [3] v3.6.1
+ ... Reference: Clause 6.4.20.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -57,7 +57,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 6.4.20.3.4 - ETSI GS NFV-SOL 005 [3] v3.6.1
+ ... Reference: Clause 6.4.20.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: VNF Snapshot not modified
@@ -69,7 +69,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 6.4.20.3.5 - ETSI GS NFV-SOL 005 [3] v3.6.1
+ ... Reference: Clause 6.4.20.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: VNF Snapshot resource is 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 6.4.20.3.5 - ETSI GS NFV-SOL 005 [3] v3.6.1
+ ... Reference: Clause 6.4.20.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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 0c2edd662933f4efb3c5752c12053c04e0266a4a..322db1cf345de3c32e0f11d2b21355f112aa0ffc 100644
--- a/SOL005/NSLifecycleManagement-API/InstantiateNSTask.robot
+++ b/SOL005/NSLifecycleManagement-API/InstantiateNSTask.robot
@@ -13,35 +13,48 @@ 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] v3.6.1
+ ... Reference: Clause 6.4.4.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
- ... Post-Conditions: The NS instance is instantiated on the NFVO
+ ... Post-Conditions: none
POST Instantiate nsInstance
Check HTTP Response Status Code Is 202
Check HTTP Response Header Contains Location
- Check resource INSTANTIATED
+ Check Operation Occurrence Id
+
+POST Instantiate a nsInstance with feasibility check only
+ [Documentation] Test ID: 5.3.2.3.1a
+ ... 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
+ ... Config ID: Config_prod_NFVO
+ ... Applicability: none
+ ... Post-Conditions: none
+ POST Instantiate nsInstance with feasibility check only
+ Check HTTP Response Status Code Is 202
+ Check HTTP Response Header Contains Location
+ Check Operation Occurrence Id
POST Instantiate a nsInstance Conflict
[Documentation] Test ID: 5.3.2.3.2
... 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] v3.6.1
+ ... Reference: Clause 6.4.4.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: The NS instance is not instantiated on the NFVO
POST Instantiate nsInstance
Check HTTP Response Status Code Is 409
Check HTTP Response Body Json Schema Is ProblemDetails
- Check resource not_instantiated
GET Instantiate NSInstance - Method not implemented
[Documentation] Test ID: 5.3.2.3.3
... 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] v3.6.1
+ ... Reference: Clause 6.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none.
@@ -53,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] v3.6.1
+ ... Reference: Clause 6.4.4.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none.
@@ -65,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] v3.6.1
+ ... Reference: Clause 6.4.4.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none.
@@ -77,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] v3.6.1
+ ... Reference: Clause 6.4.4.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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 4818c87ff32806e1451e18df19a28f753f712484..2074371c09633977e991d5af7d175abea958aae6 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] v3.6.1
+ ... Reference: Clause 6.4.4 - ETSI GS NFV-SOL 005 [3] v4.3.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 8f20b068860559b0646bb918e99b7eff7adef749..8536aa60fb9b3d11debd91f4ead1961a9615341d 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] v3.6.1
+ ... Reference: Clause 6.4.2.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1).
- ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v3.6.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.3.1).
+ ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1).
- ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v3.6.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.3.1).
+ ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.2.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.2.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.2.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1).
- ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v3.6.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.3.1).
+ ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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 fed51e211f436c2b1d9fbf929f3af025dba19806..74e615b64d22445ec5a8daa7f87e4241ecba2ebc 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] v3.6.1
+ ... Reference: Clause 6.4.9.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.9.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.9.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.9.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.9.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.9.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.9.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.9.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.9.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.9.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.9.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.9.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.9.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.9.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.9.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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 7640733739f4ecf39b49247f6aec0a92a13e509b..fd6825d440af72962360646b4495f653cc3401e6 100644
--- a/SOL005/NSLifecycleManagement-API/NSLCMOperationKeywords.robot
+++ b/SOL005/NSLifecycleManagement-API/NSLCMOperationKeywords.robot
@@ -595,6 +595,18 @@ GET Instantiate NSInstance
${outputResponse}= Output response
Set Global Variable ${response} ${outputResponse}
+POST Instantiate nsInstance with feasibility check only
+ Log Trying to Instantiate a ns Instance
+ Set Headers {"Accept":"${ACCEPT}"}
+ Set Headers {"Content-Type": "${CONTENT_TYPE}"}
+ Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"${AUTHORIZATION_HEADER}":"${AUTHORIZATION_TOKEN}"}
+ Run Keyword If ${check_descriptors} == 1 PARSE the NS Descriptor File
+ ${template}= Get File jsons/InstantiateNs_withFeasibilityCheck.json
+ ${body}= Format String ${template} nsFlavourId=${nsFlavourId} vimAccountId=${vimAccountId} nsdId=${nsdId} sapdId=${SAP_IDs[0]}
+ Post ${apiRoot}/${apiName}/${apiMajorVersion}/ns_instances/${nsInstanceId}/instantiate ${body}
+ ${outputResponse}= Output response
+ Set Global Variable ${response} ${outputResponse}
+
DELETE Scale NSInstance
log Trying to delete an Scale NS instance. This method should not be implemented
Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"${AUTHORIZATION_HEADER}":"${AUTHORIZATION_TOKEN}"}
@@ -688,6 +700,19 @@ POST Update NSInstance
${outputResponse}= Output response
Set Global Variable ${response} ${outputResponse}
+POST Update NSInstance with feasibility check only
+ Log Trying to Instantiate a Update NS Instance
+ Set Headers {"Accept":"${ACCEPT}"}
+ Set Headers {"Content-Type": "${CONTENT_TYPE}"}
+ Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"${AUTHORIZATION_HEADER}":"${AUTHORIZATION_TOKEN}"}
+ Run Keyword If ${check_descriptors} == 1 PARSE the Descriptor File
+ Run Keyword If ${check_descriptors} == 1 PARSE the NS Descriptor File
+ ${template} = Get File jsons/UpdateNsRequest_withFeasibilityCheck.json
+ ${body}= Format String ${template} vnfdId=${descriptor_id} vnfFlavourId=${Flavour_ID} newFlavourId=${Flavour_ID} vnfVirtualLinkDescId=${VirtualLink_IDs[0]} instantiationLevelId=${InstantiationLevel_IDs[1]} vnfInstantiationLevelId=${InstantiationLevel_IDs[0]} newNsdId=${NS_DescriptorID} sapdId=${SAP_IDs[0]} vnfInstanceId=${vnfInstanceId}
+ Post ${apiRoot}/${apiName}/${apiMajorVersion}/ns_instances/${nsInstanceId}/update ${body}
+ ${outputResponse}= Output response
+ Set Global Variable ${response} ${outputResponse}
+
DELETE Heal NSInstance
log Trying to Delete an Heal NS instance. This method should not be implemented
Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"${AUTHORIZATION_HEADER}":"${AUTHORIZATION_TOKEN}"}
@@ -894,13 +919,27 @@ PUT Individual NS LCM OP Occurrence
Set Global Variable ${response} ${outputResponse}
PATCH Individual NS LCM OP Occurrence
- log Trying to perform a PATCH. This method should not be implemented
- Set Headers {"Accept":"${ACCEPT}"}
+ 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}"}
- Patch ${apiRoot}/${apiName}/${apiMajorVersion}/ns_lcm_op_occs/${nsLcmOpOccId}
+ ${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 of Already Started Scheduled Operation
+ 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_alreadyStarted} ${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 2bec8523bc203e28406b7437e78dfc885c7edffa..0c0e1daabbb14082fee45602a2d720ac1ba1b631 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] v3.6.1
+ ... Reference: Clause 6.4.18.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.18.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.18.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.18.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.18.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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 c6bb52418d2980a8a09c2caab25e4f41a298112b..347b4a41047a4cb943ad5bf58dc9c0dd37a1ead9 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] v3.6.1
+ ... Reference: Clause 6.4.18.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.18.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.18.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.18.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.18.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.18.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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 8d93c3ea64e709cea5d8113865f8e1a685f53d9f..7c4184bff336da33c91544a279da0fa362e1fdba 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] v3.6.1
+ ... Reference: Clause 6.4.11.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.11.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.11.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.11.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.11.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.11.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.11.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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 d35e5c004cc3a441868ec3572614a8390442fa6e..40bc366e1e84b0c29b8697648ea525b25cb83d86 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] v3.6.1
+ ... Reference: Clause 6.4.12.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.12.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.12.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.12.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.12.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.12.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.12.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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 98d21a2cfe45888590baf3377a52e88a385e660b..5d32c1898461dd100f9bdb62c84d9309a63c5019 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] v3.6.1
+ ... Reference: Clause 6.4.5.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.5.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.5.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.5.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.5.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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 5919ca2e257ddb0290422ad2e6c0c9e4f60b3ba4..5f103c786bc3e8da5ac558a4abb2d68c4f14d199 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] v3.6.1
+ ... Reference: Clause 6.4.5 - ETSI GS NFV-SOL 005 [3] v4.3.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 d4b369308a863bc70be7a531d2ca2c40c2d75de7..bcdfb321832c266a29c0a33989ce867009140eda 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] v3.6.1
+ ... Reference: Clause 6.4.16.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.16.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.16.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.16.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.16.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.16.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.16.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.16.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.16.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.16.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.16.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.16.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.16.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.16.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.16.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: NFVO does not support paged response
... Post-Conditions: none
@@ -209,7 +209,7 @@ POST Create a new subscription - Unprocessable Entity
... Test title: POST Create a new subscription - Unprocessable Entity
... 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] v3.6.1
+ ... Reference: Clause 6.4.16.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/NSLifecycleManagement-API/TerminateNSTask.robot b/SOL005/NSLifecycleManagement-API/TerminateNSTask.robot
index dc177804ef0f1ff13baa8d79088a57a7c39d8e3e..5a031f0bffdfc11b5414e9b0b03f05f8c5114f1b 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] v3.6.1
+ ... Reference: Clause 6.4.8.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.8.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.8.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.8.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.8.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.8.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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 0306c595702700705bc27ae7181df80b9387a89d..eef642c6830ffb37721443a0501f6f845d2d4a36 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] v3.6.1
+ ... Reference: Clause 6.4.8 - ETSI GS NFV-SOL 005 [3] v4.3.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 5fb26834aafbb4b8f59b4d848096e89c81feaf00..6bc1b62a2f3f47812f0c643ac91dc9a7b1157024 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] v3.6.1
+ ... Reference: Clause 6.4.6.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: The NS instance is still INSTANTIATED and updated on the NFVO
@@ -21,12 +21,25 @@ POST Update a NSInstance
Check HTTP Response Status Code Is 202
Check HTTP Response Header Contains Location
+POST Update a NSInstance with feasibility check only
+ [Documentation] Test ID: 5.3.2.5.1a
+ ... 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
+ ... Config ID: Config_prod_NFVO
+ ... Applicability: none
+ ... Post-Conditions: none
+ POST Update NSInstance with feasibility check only
+ Check HTTP Response Status Code Is 202
+ Check HTTP Response Header Contains Location
+
POST Update a NSInstance - Conflict (Not Instantited)
[Documentation] Test ID: 5.3.2.5.2
... 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] v3.6.1
+ ... Reference: Clause 6.4.6.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: The NS instance is not updated on the NFVO
@@ -39,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] v3.6.1
+ ... Reference: Clause 6.4.6.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -51,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] v3.6.1
+ ... Reference: Clause 6.4.6.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -63,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] v3.6.1
+ ... Reference: Clause 6.4.6.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -75,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] v3.6.1
+ ... Reference: Clause 6.4.6.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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 49b189a51cd665abe83acbe57886e283ef5755a0..8b645238e4ef13c541be7105e813906b278a210a 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] v3.6.1
+ ... Reference: Clause 6.4.6 - ETSI GS NFV-SOL 005 [3] v4.3.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 968ebefb2ce3600f9878cec2f81ac67610343688..e731d1aad9e41a2f450da33352f175a0f7f2e5c6 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] v3.6.1
+ ... Reference: Clause 6.4.19.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.19.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.19.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.19.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.19.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.19.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.19.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.19.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.19.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.19.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.19.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.19.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.19.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.19.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.19.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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 343077286446d727f746798a429b1e4925668165..3250455c16882b6fca4706517895cf4ba86c084d 100644
--- a/SOL005/NSLifecycleManagement-API/environment/variables.txt
+++ b/SOL005/NSLifecycleManagement-API/environment/variables.txt
@@ -8,6 +8,7 @@ ${AUTHORIZATION_TOKEN} Bearer 0b79bab50daca910b000d4f1a2b675d604257e42
${CONTENT_TYPE} application/json
${ACCEPT_JSON} application/json
${ACCEPT} application/json
+${CONTENT_TYPE_PATCH} application/merge-patch+json
${apiRoot} /
${apiName} nslcm
${apiMajorVersion} v2
@@ -23,6 +24,8 @@ ${nsFlavourId} 0
${nsDegreeHealing} HEAL_RESTORE
${vimAccountId} 931f6a4d-6a97-43f3-a6f0-13853ef577ea
${nsLcmOpOccId} 6fc3539c-e602-4afa-8e13-962fb5a7d81d
+${nsLcmOpOccId_scheduledOp_notStarted} 6fc3539c-e602-4afa-8e13-962fb5a7d81d
+${nsLcmOpOccId_scheduledOp_alreadyStarted} 6fc3539c-e602-4afa-8e13-962fb5a7d81d
${NFVO_DUPLICATION} 0
${sub_filter} id=41fdd38a-3d4c-465c-83e0-f80e014425f8
${sub_filter_invalid} nfvid=41fdd38a-3d4c-465c-83e0-f80e014425f8
@@ -31,6 +34,8 @@ ${fields_nsInstances} monitoringParameter,wanConnectionInfo
${POS_filter_nsInstances} id=41fdd38a-3d4c-465c-83e0-f80e014425f8
${NEG_filter_nsInstances} nfvid=41fdd38a-3d4c-465c-83e0-f80e014425f8
+${schedule_for_new_operation_start} 2023-05-12T07:20:50.52Z
+
${fields_nsLcmOpOcc} cancelMode,error
${POS_filter_nsLcmOpOcc} id=41fdd38a-3d4c-465c-83e0-f80e014425f8
${NEG_filter_nsLcmOpOcc} nfvid=41fdd38a-3d4c-465c-83e0-f80e014425f8
diff --git a/SOL005/NSLifecycleManagement-API/jsons/InstantiateNsRequest_withFeasibilityCheck.json b/SOL005/NSLifecycleManagement-API/jsons/InstantiateNsRequest_withFeasibilityCheck.json
new file mode 100644
index 0000000000000000000000000000000000000000..0a9329fcbad3e81ce3b8ef3f69ac8c1399093bc2
--- /dev/null
+++ b/SOL005/NSLifecycleManagement-API/jsons/InstantiateNsRequest_withFeasibilityCheck.json
@@ -0,0 +1,17 @@
+{
+ "nsFlavourId": "flavour_id",
+ "sapData":[
+ "{sapdId}"
+ ],
+ "addpnfData":[],
+ "vnfInstanceData":[],
+ "nestedNsInstanceData":[],
+ "locationConstraints":[],
+ "nestedNsLocationConstraints":[],
+ "additionalParamsForNs":{},
+ "additionalParamForNestedNs":[],
+ "additionalParamsForVnf":[],
+ "startTime": "",
+ "nsInstantiationLevelId": "",
+ "feasibilityCheckReserve": "FEASIBILITY_CHECK_ONLY"
+}
\ No newline at end of file
diff --git a/SOL005/NSLifecycleManagement-API/jsons/NsLcmInfoModificationRequest.json b/SOL005/NSLifecycleManagement-API/jsons/NsLcmInfoModificationRequest.json
new file mode 100644
index 0000000000000000000000000000000000000000..56869537410d70182aa3a5502c2b41107c1a0b14
--- /dev/null
+++ b/SOL005/NSLifecycleManagement-API/jsons/NsLcmInfoModificationRequest.json
@@ -0,0 +1,3 @@
+{{
+ "scheduledTime": "2023-05-12T07:20:50.52Z"
+}}
\ No newline at end of file
diff --git a/SOL005/NSLifecycleManagement-API/jsons/UpdateNsRequest_withFeasibilityCheck.json b/SOL005/NSLifecycleManagement-API/jsons/UpdateNsRequest_withFeasibilityCheck.json
new file mode 100644
index 0000000000000000000000000000000000000000..00f4d941c4681ef8546a24d566db4d5e1ce741e8
--- /dev/null
+++ b/SOL005/NSLifecycleManagement-API/jsons/UpdateNsRequest_withFeasibilityCheck.json
@@ -0,0 +1,28 @@
+{{
+ "updateType": "{vnfUpdateType}",
+ "feasibilityCheckReserve": "FEASIBILITY_CHECK_ONLY,
+ "addVnfInstance": [
+ {{
+ "vnfInstanceId": "{vnfInstanceId}"
+ }}
+ ],
+ "instantiateVnfData": {{
+ "vnfdId": "{vnfdId}",
+ "vnfFlavourId": "{vnfFlavourId}",
+ "vnfInstantiationLevelId": "{vnfInstantiationLevelId}",
+ "extManagedVirtualLinks": {{
+ "vnfVirtualLinkDescId": "{vnfVirtualLinkDescId}"
+ }},
+ "changeVnfFlavourData": {{
+ "vnfInstanceId": {},
+ "newFlavourId": "{newFlavourId}",
+ "instantiationLevelId": "{instantiationLevelId}"
+ }},
+ "assocNewNsdVersionData": {{
+ "newNsdId": "{newNsdId}"
+ }},
+ "addSap": {{
+ "sapdId": "{sapdId}"
+ }}
+ }}
+}}
diff --git a/SOL005/NSLifecycleManagement-API/schemas/NsInstance.schema.json b/SOL005/NSLifecycleManagement-API/schemas/NsInstance.schema.json
index bb203caba2a6db896990d815080e66b5eb586e52..fe1b03d4b25236b98061cf975376c89f58a725ab 100644
--- a/SOL005/NSLifecycleManagement-API/schemas/NsInstance.schema.json
+++ b/SOL005/NSLifecycleManagement-API/schemas/NsInstance.schema.json
@@ -1,5 +1,5 @@
{
- "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:\tIf the \"nsState\" attribute is INSTANTIATED, at least either one\n \"vnfInstance\" attribute or one \"nestedNsInstanceId\" attribute shall be present.\nNOTE 2:\tThe “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:\tExamples 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. \"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": {
@@ -19,6 +19,40 @@
"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 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"
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ },
"nsdInfoId": {
"description": "An identifier with the intention of being globally unique.\n",
"type": "string"
@@ -32,7 +66,7 @@
"type": "number"
},
"vnfInstance": {
- "description": "Information on constituent VNF(s) of the NS instance. See note 1.\n",
+ "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",
@@ -71,6 +105,40 @@
"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 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"
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ },
"vnfPkgId": {
"description": "An identifier with the intention of being globally unique.\n",
"type": "string"
@@ -150,11 +218,15 @@
"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:\tThe attributes \"associatedVnfcCpId\", \"associatedVipCpId\" and \"associatedVnfVirtualLinkId\" are mutually exclusive. Exactly one shall be present. NOTE 2:\tAn external CP instance is not associated to a link port in the cases indicated for the “extLinkPorts” attribute in clause 6.5.3.26.\n",
+ "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"],
+ "required": ["id", "cpdId", "cpProtocolInfo"],
"oneOf": [{
"required": ["associatedVnfcCpId"]
+ }, {
+ "required": ["associatedVipCpId"]
+ }, {
+ "required": ["associatedVirtualCpId"]
}, {
"required": ["associatedVnfVirtualLinkId"]
}],
@@ -180,17 +252,17 @@
"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:\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",
+ "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\nSee note.\n",
+ "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"]
+ "enum": ["IP_OVER_ETHERNET", "IP_FOR_VIRTUAL_CP"]
},
"ipOverEthernet": {
- "description": "This type represents information about a network address that has been assigned.\nNOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4:\tDepending 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",
+ "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"]
@@ -255,7 +327,7 @@
}
},
"subnetId": {
- "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",
+ "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"
}
}
@@ -303,10 +375,27 @@
"format": "IP"
},
"subnetId": {
- "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",
+ "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"
+ }
+ }
}
}
}
@@ -315,6 +404,14 @@
"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"
@@ -327,6 +424,10 @@
"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"
@@ -362,17 +463,17 @@
"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:\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",
+ "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\nSee note.\n",
+ "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"]
+ "enum": ["IP_OVER_ETHERNET", "IP_FOR_VIRTUAL_CP"]
},
"ipOverEthernet": {
- "description": "This type represents information about a network address that has been assigned.\nNOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4:\tDepending 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",
+ "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"]
@@ -437,7 +538,7 @@
}
},
"subnetId": {
- "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",
+ "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"
}
}
@@ -485,10 +586,27 @@
"format": "IP"
},
"subnetId": {
- "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",
+ "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"
+ }
+ }
}
}
}
@@ -516,19 +634,303 @@
}
}
},
+ "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"],
+ "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. NOTE: The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle.\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": {
@@ -541,11 +943,33 @@
"type": "string"
},
"resourceId": {
- "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",
+ "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": "Type of the resource in the scope of the VIM, the WIM or the resource provider. The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. See note.\n",
+ "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"
}
}
@@ -554,7 +978,7 @@
"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:\tThe 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:\tThe value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\" attribute.\n",
+ "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": {
@@ -563,7 +987,7 @@
"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. NOTE: The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle.\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": {
@@ -576,11 +1000,33 @@
"type": "string"
},
"resourceId": {
- "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",
+ "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": "Type of the resource in the scope of the VIM, the WIM or the resource provider. The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. See note.\n",
+ "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"
}
}
@@ -600,8 +1046,84 @@
}
}
},
+ "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:\tIn 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: \tThe 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: \tWithin 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",
+ "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": {
@@ -613,9 +1135,9 @@
"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 network address information per instance of an external connection point. In case a link port is provided, the VNFM shall use that link port when connecting the external CP to the external VL. In a link port is not provided, the VNFM shall create a link port on the external VL, and use that link port to connect the external CP to the external VL. NOTE 1:\tThe following conditions apply to the attributes \"linkPortId\" and \"cpProtocolData\":\n -\tAt 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 -\tIf the \"cpProtocolData\" attribute is absent, the \"linkPortId\" attribute shall be provided\n referencing a pre-created link port with pre-configured address information.\n -\tIf 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:\tIn 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.\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 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",
- "anyOf": [{
+ "oneOf": [{
"required": ["linkPortId"]
}, {
"required": ["cpProtocolData"]
@@ -634,20 +1156,20 @@
"type": "boolean"
},
"cpProtocolData": {
- "description": "Parameters for configuring the network protocols on the link port that connects the CP to a VL. See note 1.\n",
+ "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.\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.\n",
+ "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"]
+ "enum": ["IP_OVER_ETHERNET", "IP_FOR_VIRTUAL_CP"]
},
"ipOverEthernet": {
- "description": "This type represents network address data for IP over Ethernet. NOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present. NOTE 3:\tIf the CP instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4:\tDepending 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",
+ "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"]
@@ -661,7 +1183,7 @@
"format": "MAC"
},
"segmentationType": {
- "description": "Specifies the encapsulation type for the traffics coming in and out of the trunk subport. Permitted values are: -\tVLAN: The subport uses VLAN as encapsulation type. -\tINHERIT: 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",
+ "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"]
},
@@ -719,16 +1241,41 @@
}
},
"subnetId": {
- "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",
+ "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"
+ }
}
}
}
@@ -742,41 +1289,68 @@
"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"],
+ "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": "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. NOTE: The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle.\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 other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Type of the resource in the scope of the VIM, the WIM or the resource provider. The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. See note.\n",
- "type": "string"
+ "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"
+ }
}
}
},
@@ -785,7 +1359,7 @@
"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:\tEither 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",
+ "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": {
@@ -793,7 +1367,7 @@
"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. NOTE: The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle.\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": {
@@ -806,11 +1380,33 @@
"type": "string"
},
"resourceId": {
- "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",
+ "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": "Type of the resource in the scope of the VIM, the WIM or the resource provider. The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. See note.\n",
+ "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"
}
}
@@ -835,6 +1431,78 @@
}
}
},
+ "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"
@@ -877,7 +1545,7 @@
"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. NOTE 1:\tETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on TOSCA specifications. NOTE 2:\tA 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:\tThe information can be omitted because it is already available as part of the external CP information. \n",
+ "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": {
@@ -894,7 +1562,7 @@
"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. NOTE: The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle.\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": {
@@ -907,20 +1575,42 @@
"type": "string"
},
"resourceId": {
- "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",
+ "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": "Type of the resource in the scope of the VIM, the WIM or the resource provider. The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. See note.\n",
+ "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. The value refers to a VirtualStorageResourceInfo item in the VnfInstance.\n",
+ "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 with the intention of being globally unique.\n",
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
"type": "string"
}
},
@@ -951,17 +1641,17 @@
"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:\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",
+ "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\nSee note.\n",
+ "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"]
+ "enum": ["IP_OVER_ETHERNET", "IP_FOR_VIRTUAL_CP"]
},
"ipOverEthernet": {
- "description": "This type represents information about a network address that has been assigned.\nNOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4:\tDepending 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",
+ "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"]
@@ -1026,7 +1716,7 @@
}
},
"subnetId": {
- "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",
+ "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"
}
}
@@ -1074,10 +1764,27 @@
"format": "IP"
},
"subnetId": {
- "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",
+ "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"
+ }
+ }
}
}
}
@@ -1090,6 +1797,14 @@
"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"
@@ -1125,7 +1840,7 @@
"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. NOTE: The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle.\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": {
@@ -1138,11 +1853,33 @@
"type": "string"
},
"resourceId": {
- "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",
+ "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": "Type of the resource in the scope of the VIM, the WIM or the resource provider. The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. See note.\n",
+ "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"
}
}
@@ -1156,7 +1893,7 @@
"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:\tEither 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",
+ "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": {
@@ -1164,7 +1901,7 @@
"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. NOTE: The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle.\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": {
@@ -1177,11 +1914,33 @@
"type": "string"
},
"resourceId": {
- "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",
+ "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": "Type of the resource in the scope of the VIM, the WIM or the resource provider. The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. See note.\n",
+ "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"
}
}
@@ -1234,7 +1993,7 @@
"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. NOTE: The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle.\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": {
@@ -1247,11 +2006,33 @@
"type": "string"
},
"resourceId": {
- "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",
+ "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": "Type of the resource in the scope of the VIM, the WIM or the resource provider. The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. See note.\n",
+ "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"
}
}
@@ -1266,6 +2047,53 @@
}
}
}
+ },
+ "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"
+ }
+ }
+ }
}
}
},
@@ -1300,6 +2128,40 @@
"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 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"
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ },
"pnfdInfoId": {
"description": "An identifier with the intention of being globally unique.\n",
"type": "string"
@@ -1325,17 +2187,17 @@
"description": "Parameters for configuring the network protocols on the CP.\n",
"type": "array",
"items": {
- "description": "This type represents network protocol data.\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.\n",
+ "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"]
+ "enum": ["IP_OVER_ETHERNET", "IP_FOR_VIRTUAL_CP"]
},
"ipOverEthernet": {
- "description": "This type represents network address data for IP over Ethernet. NOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present. NOTE 3:\tIf the CP instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4:\tDepending 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",
+ "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"]
@@ -1349,7 +2211,7 @@
"format": "MAC"
},
"segmentationType": {
- "description": "Specifies the encapsulation type for the traffics coming in and out of the trunk subport. Permitted values are: -\tVLAN: The subport uses VLAN as encapsulation type. -\tINHERIT: 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",
+ "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"]
},
@@ -1407,13 +2269,30 @@
}
},
"subnetId": {
- "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",
+ "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"
+ }
+ }
}
}
}
@@ -1427,7 +2306,7 @@
"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:\tAs 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",
+ "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": {
@@ -1447,7 +2326,7 @@
"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. NOTE: The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle.\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": {
@@ -1460,11 +2339,33 @@
"type": "string"
},
"resourceId": {
- "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",
+ "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": "Type of the resource in the scope of the VIM, the WIM or the resource provider. The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. See note.\n",
+ "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"
}
}
@@ -1474,7 +2375,7 @@
"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:\tWhen 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",
+ "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": {
@@ -1483,7 +2384,7 @@
"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. NOTE: The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle.\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": {
@@ -1496,17 +2397,39 @@
"type": "string"
},
"resourceId": {
- "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",
+ "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": "Type of the resource in the scope of the VIM, the WIM or the resource provider. The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. See note.\n",
+ "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:\tFor the VNF external CP instance, both vnfInstanceId and vnfExtCpInstanceId shall be present as a pair. NOTE 2:\tFor the PNF external CP instance, both pnfInfoId and PnfExtCpInstanceId shall be present as a pair. NOTE 3:\tFor the SAP instance, both nsInstanceId and nsSapInstanceId shall be present as a pair. NOTE 4:\tOne pair of identifiers (VNF external CP, PNF external CP or SAP) shall be present.\n",
+ "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"]
@@ -1552,7 +2475,7 @@
"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:\tIt indicates an exhaustive list of all the CP instances and SAP instances of the VNFFG.\n",
+ "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": {
@@ -1589,7 +2512,7 @@
}
},
"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:\tFor the VNF external CP instance, both vnfInstanceId and vnfExtCpInstanceId shall be present as a pair. NOTE 2:\tFor the PNF external CP instance, both pnfInfoId and PnfExtCpInstanceId shall be present as a pair. NOTE 3:\tFor the SAP instance, both nsInstanceId and nsSapInstanceId shall be present as a pair. NOTE 4:\tOne pair of identifiers (VNF external CP, PNF external CP or SAP) shall be present.\n",
+ "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"]
@@ -1656,17 +2579,17 @@
"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:\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",
+ "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\nSee note.\n",
+ "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"]
+ "enum": ["IP_OVER_ETHERNET", "IP_FOR_VIRTUAL_CP"]
},
"ipOverEthernet": {
- "description": "This type represents information about a network address that has been assigned.\nNOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4:\tDepending 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",
+ "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"]
@@ -1731,7 +2654,7 @@
}
},
"subnetId": {
- "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",
+ "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"
}
}
@@ -1779,10 +2702,27 @@
"format": "IP"
},
"subnetId": {
- "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",
+ "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"
+ }
+ }
}
}
}
@@ -1791,7 +2731,7 @@
}
},
"nestedNsInstanceId": {
- "description": "Identifier of the nested NS(s) of the NS instance. See note.\n",
+ "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",
@@ -1902,7 +2842,7 @@
"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:\tEither a \"nsVirtualLinkInfoId\" or a \"vnfVirtualLinkResourceInfoId\" shall be provided, but not both.\n",
+ "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": [{
@@ -1945,12 +2885,12 @@
"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: -\tL2 -\tL3\n",
+ "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: -\tEVPN_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\". -\tVPLS_BGP: as specified in IETF RFC 4761 and IETF RFC 6624. Only applicable for mscsType=\"L2\". -\tVPLS_LDP_L2TP: as specified in IETF RFC 4762. Only applicable for mscsType=\"L2\". -\tVPWS_LDP_L2TP: as specified in IETF RFC 6074. Only applicable for mscsType=\"L2\". -\tBGP_IP_VPN: BGP/MPLS based IP VPN as specified in IETF RFC 4364. Only applicable for mscsType=\"L3\".\n",
+ "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"]
},
@@ -1961,7 +2901,7 @@
"type": "object",
"properties": {
"locationConstraints": {
- "description": "This type represents location constraints for a VNF to be instantiated. The location constraints can be represented as follows: •\tas a country code •\tas a civic address combined with a country code •\tas an area, conditionally combined with a country code\nNOTE:\tIf 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",
+ "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": {
@@ -1993,7 +2933,7 @@
}
},
"protectionScheme": {
- "description": "Defines the protection scheme. Permitted values: -\tUNPROTECTED: to indicate no protection. -\tONE_TO_ONE: to indicate an active-passive access protection. -\tONE_PLUS_ONE: to indicate an active-active access protection. -\tONE_TO_N: to indicate an N active to 1 passive access protection.\n",
+ "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"]
}
@@ -2017,7 +2957,7 @@
"type": "string"
},
"directionality": {
- "description": "Directionality of the data traffic in the context of the terminating MSCS endpoint from WAN’s perspective. Permitted values: -\tINBOUND: to indicate into the WAN. -\tOUTBOUND: to indicate from the WAN. -\tBOTH: to indicate bidirectional data traffic to/from the WAN.\n",
+ "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"]
},
@@ -2051,7 +2991,7 @@
"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:\tEither \"networkResources\" or \"vnSegmentsIds\" shall be provided, but not both.\n",
+ "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": {
@@ -2061,27 +3001,27 @@
"required": ["connectionType", "interfaceType", "interfaceTagging", "encapsulationType"],
"properties": {
"connectionType": {
- "description": "The type of connection to be established on the connectivity service point. Permitted values: -\tCSE: defined by the characteristics of the existing referred connectivity service point. -\tAGGREGATE_CSE: create an aggregation of the connectivity service endpoints.\n",
+ "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: -\tPARENT: use the mapped interface to the connectivity service endpoint as is, i.e., do not create logical interfaces. -\tLOGICAL: create logical interfaces.\n",
+ "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: -\tUNTAGGED: an interface where frames are not tagged. -\tTAGGED: an interface configured to forward tagged frames (i.e., enabled for VLAN tagging).\n",
+ "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: -\tETH: generic Ethernet encapsulation. -\tVLAN: encapsulation based on VLAN. -\tVXLAN: encapsulation based on VXLAN.\n",
+ "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: -\tDOT1Q: used when packets on the CSE are encapsulated with one or a set of customer VLAN identifiers. -\tQINQ: 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",
+ "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"]
},
@@ -2106,7 +3046,7 @@
"required": ["peerMode"],
"properties": {
"peerMode": {
- "description": "Type of VXLAN access mode. Default value is \"STATIC\".\nPermitted values: -\tSTATIC -\tBGP_EVPN\n",
+ "description": "Type of VXLAN access mode. Default value is \"STATIC\".\nPermitted values: - STATIC - BGP_EVPN\n",
"type": "string",
"enum": ["STATIC", "BGP_EVPN"]
},
@@ -2178,7 +3118,7 @@
"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. NOTE: The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle.\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": {
@@ -2191,11 +3131,33 @@
"type": "string"
},
"resourceId": {
- "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",
+ "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": "Type of the resource in the scope of the VIM, the WIM or the resource provider. The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. See note.\n",
+ "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"
}
}
@@ -2247,7 +3209,7 @@
"required": ["routingProtocol", "routingAddressFamily"],
"properties": {
"routingProtocol": {
- "description": "The routing protocol that is activated on the connectivity service endpoint. Permitted values: -\tBGP: used for dynamic routing BGPv4. -\tRIP: used for dynamic routing RIPv2. -\tOSPF: used for dynamic routing (OSPF version 2 for IPv4; and OSPF version 3 for IPv6). -\tSTATIC: used for static routing. -\tDIRECT: used when the NFVI-PoP network is directly connected to the WAN provider network. -\tVRRP: used when the NFVI-PoP network is directly connected to the WAN provider network with virtual\n router redundancy protocol support (VRRP).\n",
+ "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"]
},
@@ -2257,7 +3219,7 @@
"required": ["ipVersion", "ipPrefix", "prefixSize", "nextHop"],
"properties": {
"ipVersion": {
- "description": "The IP version applicable to the routing entry. Permitted values: -\tIPV4 -\tIPV6\n",
+ "description": "The IP version applicable to the routing entry. Permitted values: - IPV4 - IPV6\n",
"type": "string",
"enum": ["IPV4", "IPV6"]
},
@@ -2278,7 +3240,7 @@
}
},
"routingAddressFamily": {
- "description": "The IP version applicable to the dynamic routing protocol. Shall be present for dynamic routing protocols. Permitted values: -\tIPV4 -\tIPV6\n",
+ "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"]
},
@@ -2319,7 +3281,7 @@
"required": ["policy", "sequence", "matchAndSetRule"],
"properties": {
"policy": {
- "description": "The policy to apply to the route distribution.\nPermitted values: -\tPERMIT -\tDENY\n",
+ "description": "The policy to apply to the route distribution.\nPermitted values: - PERMIT - DENY\n",
"type": "string",
"enum": ["PERMIT", "DENY"]
},
diff --git a/SOL005/NSLifecycleManagement-API/schemas/NsInstances.schema.json b/SOL005/NSLifecycleManagement-API/schemas/NsInstances.schema.json
index e6f5f9db462298c006cc2d69baca7d79454aba28..93b66e55058e206dbdc04174d89ce257554a48d8 100644
--- a/SOL005/NSLifecycleManagement-API/schemas/NsInstances.schema.json
+++ b/SOL005/NSLifecycleManagement-API/schemas/NsInstances.schema.json
@@ -1,7 +1,7 @@
{
"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:\tIf the \"nsState\" attribute is INSTANTIATED, at least either one\n \"vnfInstance\" attribute or one \"nestedNsInstanceId\" attribute shall be present.\nNOTE 2:\tThe “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:\tExamples 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. \"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": {
@@ -21,6 +21,40 @@
"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 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"
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ },
"nsdInfoId": {
"description": "An identifier with the intention of being globally unique.\n",
"type": "string"
@@ -34,7 +68,7 @@
"type": "number"
},
"vnfInstance": {
- "description": "Information on constituent VNF(s) of the NS instance. See note 1.\n",
+ "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",
@@ -73,6 +107,40 @@
"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 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"
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ },
"vnfPkgId": {
"description": "An identifier with the intention of being globally unique.\n",
"type": "string"
@@ -152,11 +220,15 @@
"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:\tThe attributes \"associatedVnfcCpId\", \"associatedVipCpId\" and \"associatedVnfVirtualLinkId\" are mutually exclusive. Exactly one shall be present. NOTE 2:\tAn external CP instance is not associated to a link port in the cases indicated for the “extLinkPorts” attribute in clause 6.5.3.26.\n",
+ "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"],
+ "required": ["id", "cpdId", "cpProtocolInfo"],
"oneOf": [{
"required": ["associatedVnfcCpId"]
+ }, {
+ "required": ["associatedVipCpId"]
+ }, {
+ "required": ["associatedVirtualCpId"]
}, {
"required": ["associatedVnfVirtualLinkId"]
}],
@@ -182,17 +254,17 @@
"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:\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",
+ "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\nSee note.\n",
+ "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"]
+ "enum": ["IP_OVER_ETHERNET", "IP_FOR_VIRTUAL_CP"]
},
"ipOverEthernet": {
- "description": "This type represents information about a network address that has been assigned.\nNOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4:\tDepending 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",
+ "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"]
@@ -257,7 +329,7 @@
}
},
"subnetId": {
- "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",
+ "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"
}
}
@@ -305,10 +377,27 @@
"format": "IP"
},
"subnetId": {
- "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",
+ "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"
+ }
+ }
}
}
}
@@ -317,6 +406,14 @@
"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"
@@ -329,6 +426,10 @@
"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"
@@ -364,17 +465,17 @@
"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:\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",
+ "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\nSee note.\n",
+ "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"]
+ "enum": ["IP_OVER_ETHERNET", "IP_FOR_VIRTUAL_CP"]
},
"ipOverEthernet": {
- "description": "This type represents information about a network address that has been assigned.\nNOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4:\tDepending 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",
+ "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"]
@@ -439,7 +540,7 @@
}
},
"subnetId": {
- "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",
+ "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"
}
}
@@ -487,10 +588,27 @@
"format": "IP"
},
"subnetId": {
- "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",
+ "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"
+ }
+ }
}
}
}
@@ -518,19 +636,303 @@
}
}
},
+ "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"],
+ "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. NOTE: The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle.\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": {
@@ -543,11 +945,33 @@
"type": "string"
},
"resourceId": {
- "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",
+ "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": "Type of the resource in the scope of the VIM, the WIM or the resource provider. The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. See note.\n",
+ "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"
}
}
@@ -556,7 +980,7 @@
"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:\tThe 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:\tThe value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\" attribute.\n",
+ "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": {
@@ -565,7 +989,7 @@
"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. NOTE: The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle.\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": {
@@ -578,11 +1002,33 @@
"type": "string"
},
"resourceId": {
- "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",
+ "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": "Type of the resource in the scope of the VIM, the WIM or the resource provider. The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. See note.\n",
+ "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"
}
}
@@ -602,8 +1048,84 @@
}
}
},
+ "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:\tIn 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: \tThe 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: \tWithin 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",
+ "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": {
@@ -615,9 +1137,9 @@
"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 network address information per instance of an external connection point. In case a link port is provided, the VNFM shall use that link port when connecting the external CP to the external VL. In a link port is not provided, the VNFM shall create a link port on the external VL, and use that link port to connect the external CP to the external VL. NOTE 1:\tThe following conditions apply to the attributes \"linkPortId\" and \"cpProtocolData\":\n -\tAt 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 -\tIf the \"cpProtocolData\" attribute is absent, the \"linkPortId\" attribute shall be provided\n referencing a pre-created link port with pre-configured address information.\n -\tIf 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:\tIn 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.\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 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",
- "anyOf": [{
+ "oneOf": [{
"required": ["linkPortId"]
}, {
"required": ["cpProtocolData"]
@@ -636,20 +1158,20 @@
"type": "boolean"
},
"cpProtocolData": {
- "description": "Parameters for configuring the network protocols on the link port that connects the CP to a VL. See note 1.\n",
+ "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.\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.\n",
+ "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"]
+ "enum": ["IP_OVER_ETHERNET", "IP_FOR_VIRTUAL_CP"]
},
"ipOverEthernet": {
- "description": "This type represents network address data for IP over Ethernet. NOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present. NOTE 3:\tIf the CP instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4:\tDepending 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",
+ "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"]
@@ -663,7 +1185,7 @@
"format": "MAC"
},
"segmentationType": {
- "description": "Specifies the encapsulation type for the traffics coming in and out of the trunk subport. Permitted values are: -\tVLAN: The subport uses VLAN as encapsulation type. -\tINHERIT: 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",
+ "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"]
},
@@ -721,16 +1243,41 @@
}
},
"subnetId": {
- "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",
+ "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"
+ }
}
}
}
@@ -744,41 +1291,68 @@
"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"],
+ "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": "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. NOTE: The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle.\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 other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Type of the resource in the scope of the VIM, the WIM or the resource provider. The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. See note.\n",
- "type": "string"
+ "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"
+ }
}
}
},
@@ -787,7 +1361,7 @@
"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:\tEither 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",
+ "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": {
@@ -795,7 +1369,7 @@
"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. NOTE: The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle.\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": {
@@ -808,11 +1382,33 @@
"type": "string"
},
"resourceId": {
- "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",
+ "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": "Type of the resource in the scope of the VIM, the WIM or the resource provider. The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. See note.\n",
+ "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"
}
}
@@ -837,6 +1433,78 @@
}
}
},
+ "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"
@@ -879,7 +1547,7 @@
"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. NOTE 1:\tETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on TOSCA specifications. NOTE 2:\tA 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:\tThe information can be omitted because it is already available as part of the external CP information. \n",
+ "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": {
@@ -896,7 +1564,7 @@
"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. NOTE: The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle.\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": {
@@ -909,20 +1577,42 @@
"type": "string"
},
"resourceId": {
- "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",
+ "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": "Type of the resource in the scope of the VIM, the WIM or the resource provider. The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. See note.\n",
+ "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. The value refers to a VirtualStorageResourceInfo item in the VnfInstance.\n",
+ "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 with the intention of being globally unique.\n",
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
"type": "string"
}
},
@@ -953,17 +1643,17 @@
"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:\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",
+ "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\nSee note.\n",
+ "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"]
+ "enum": ["IP_OVER_ETHERNET", "IP_FOR_VIRTUAL_CP"]
},
"ipOverEthernet": {
- "description": "This type represents information about a network address that has been assigned.\nNOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4:\tDepending 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",
+ "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"]
@@ -1028,7 +1718,7 @@
}
},
"subnetId": {
- "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",
+ "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"
}
}
@@ -1076,10 +1766,27 @@
"format": "IP"
},
"subnetId": {
- "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",
+ "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"
+ }
+ }
}
}
}
@@ -1092,6 +1799,14 @@
"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"
@@ -1127,7 +1842,7 @@
"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. NOTE: The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle.\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": {
@@ -1140,11 +1855,33 @@
"type": "string"
},
"resourceId": {
- "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",
+ "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": "Type of the resource in the scope of the VIM, the WIM or the resource provider. The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. See note.\n",
+ "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"
}
}
@@ -1158,7 +1895,7 @@
"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:\tEither 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",
+ "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": {
@@ -1166,7 +1903,7 @@
"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. NOTE: The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle.\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": {
@@ -1179,11 +1916,33 @@
"type": "string"
},
"resourceId": {
- "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",
+ "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": "Type of the resource in the scope of the VIM, the WIM or the resource provider. The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. See note.\n",
+ "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"
}
}
@@ -1236,7 +1995,7 @@
"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. NOTE: The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle.\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": {
@@ -1249,11 +2008,33 @@
"type": "string"
},
"resourceId": {
- "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",
+ "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": "Type of the resource in the scope of the VIM, the WIM or the resource provider. The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. See note.\n",
+ "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"
}
}
@@ -1268,6 +2049,53 @@
}
}
}
+ },
+ "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"
+ }
+ }
+ }
}
}
},
@@ -1302,6 +2130,40 @@
"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 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"
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ },
"pnfdInfoId": {
"description": "An identifier with the intention of being globally unique.\n",
"type": "string"
@@ -1327,17 +2189,17 @@
"description": "Parameters for configuring the network protocols on the CP.\n",
"type": "array",
"items": {
- "description": "This type represents network protocol data.\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.\n",
+ "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"]
+ "enum": ["IP_OVER_ETHERNET", "IP_FOR_VIRTUAL_CP"]
},
"ipOverEthernet": {
- "description": "This type represents network address data for IP over Ethernet. NOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present. NOTE 3:\tIf the CP instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4:\tDepending 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",
+ "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"]
@@ -1351,7 +2213,7 @@
"format": "MAC"
},
"segmentationType": {
- "description": "Specifies the encapsulation type for the traffics coming in and out of the trunk subport. Permitted values are: -\tVLAN: The subport uses VLAN as encapsulation type. -\tINHERIT: 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",
+ "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"]
},
@@ -1409,13 +2271,30 @@
}
},
"subnetId": {
- "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",
+ "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"
+ }
+ }
}
}
}
@@ -1429,7 +2308,7 @@
"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:\tAs 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",
+ "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": {
@@ -1449,7 +2328,7 @@
"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. NOTE: The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle.\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": {
@@ -1462,11 +2341,33 @@
"type": "string"
},
"resourceId": {
- "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",
+ "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": "Type of the resource in the scope of the VIM, the WIM or the resource provider. The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. See note.\n",
+ "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"
}
}
@@ -1476,7 +2377,7 @@
"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:\tWhen 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",
+ "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": {
@@ -1485,7 +2386,7 @@
"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. NOTE: The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle.\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": {
@@ -1498,17 +2399,39 @@
"type": "string"
},
"resourceId": {
- "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",
+ "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": "Type of the resource in the scope of the VIM, the WIM or the resource provider. The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. See note.\n",
+ "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:\tFor the VNF external CP instance, both vnfInstanceId and vnfExtCpInstanceId shall be present as a pair. NOTE 2:\tFor the PNF external CP instance, both pnfInfoId and PnfExtCpInstanceId shall be present as a pair. NOTE 3:\tFor the SAP instance, both nsInstanceId and nsSapInstanceId shall be present as a pair. NOTE 4:\tOne pair of identifiers (VNF external CP, PNF external CP or SAP) shall be present.\n",
+ "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"]
@@ -1554,7 +2477,7 @@
"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:\tIt indicates an exhaustive list of all the CP instances and SAP instances of the VNFFG.\n",
+ "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": {
@@ -1591,7 +2514,7 @@
}
},
"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:\tFor the VNF external CP instance, both vnfInstanceId and vnfExtCpInstanceId shall be present as a pair. NOTE 2:\tFor the PNF external CP instance, both pnfInfoId and PnfExtCpInstanceId shall be present as a pair. NOTE 3:\tFor the SAP instance, both nsInstanceId and nsSapInstanceId shall be present as a pair. NOTE 4:\tOne pair of identifiers (VNF external CP, PNF external CP or SAP) shall be present.\n",
+ "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"]
@@ -1658,17 +2581,17 @@
"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:\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",
+ "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\nSee note.\n",
+ "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"]
+ "enum": ["IP_OVER_ETHERNET", "IP_FOR_VIRTUAL_CP"]
},
"ipOverEthernet": {
- "description": "This type represents information about a network address that has been assigned.\nNOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4:\tDepending 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",
+ "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"]
@@ -1733,7 +2656,7 @@
}
},
"subnetId": {
- "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",
+ "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"
}
}
@@ -1781,10 +2704,27 @@
"format": "IP"
},
"subnetId": {
- "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",
+ "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"
+ }
+ }
}
}
}
@@ -1793,7 +2733,7 @@
}
},
"nestedNsInstanceId": {
- "description": "Identifier of the nested NS(s) of the NS instance. See note.\n",
+ "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",
@@ -1904,7 +2844,7 @@
"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:\tEither a \"nsVirtualLinkInfoId\" or a \"vnfVirtualLinkResourceInfoId\" shall be provided, but not both.\n",
+ "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": [{
@@ -1947,12 +2887,12 @@
"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: -\tL2 -\tL3\n",
+ "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: -\tEVPN_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\". -\tVPLS_BGP: as specified in IETF RFC 4761 and IETF RFC 6624. Only applicable for mscsType=\"L2\". -\tVPLS_LDP_L2TP: as specified in IETF RFC 4762. Only applicable for mscsType=\"L2\". -\tVPWS_LDP_L2TP: as specified in IETF RFC 6074. Only applicable for mscsType=\"L2\". -\tBGP_IP_VPN: BGP/MPLS based IP VPN as specified in IETF RFC 4364. Only applicable for mscsType=\"L3\".\n",
+ "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"]
},
@@ -1963,7 +2903,7 @@
"type": "object",
"properties": {
"locationConstraints": {
- "description": "This type represents location constraints for a VNF to be instantiated. The location constraints can be represented as follows: •\tas a country code •\tas a civic address combined with a country code •\tas an area, conditionally combined with a country code\nNOTE:\tIf 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",
+ "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": {
@@ -1995,7 +2935,7 @@
}
},
"protectionScheme": {
- "description": "Defines the protection scheme. Permitted values: -\tUNPROTECTED: to indicate no protection. -\tONE_TO_ONE: to indicate an active-passive access protection. -\tONE_PLUS_ONE: to indicate an active-active access protection. -\tONE_TO_N: to indicate an N active to 1 passive access protection.\n",
+ "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"]
}
@@ -2019,7 +2959,7 @@
"type": "string"
},
"directionality": {
- "description": "Directionality of the data traffic in the context of the terminating MSCS endpoint from WAN’s perspective. Permitted values: -\tINBOUND: to indicate into the WAN. -\tOUTBOUND: to indicate from the WAN. -\tBOTH: to indicate bidirectional data traffic to/from the WAN.\n",
+ "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"]
},
@@ -2053,7 +2993,7 @@
"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:\tEither \"networkResources\" or \"vnSegmentsIds\" shall be provided, but not both.\n",
+ "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": {
@@ -2063,27 +3003,27 @@
"required": ["connectionType", "interfaceType", "interfaceTagging", "encapsulationType"],
"properties": {
"connectionType": {
- "description": "The type of connection to be established on the connectivity service point. Permitted values: -\tCSE: defined by the characteristics of the existing referred connectivity service point. -\tAGGREGATE_CSE: create an aggregation of the connectivity service endpoints.\n",
+ "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: -\tPARENT: use the mapped interface to the connectivity service endpoint as is, i.e., do not create logical interfaces. -\tLOGICAL: create logical interfaces.\n",
+ "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: -\tUNTAGGED: an interface where frames are not tagged. -\tTAGGED: an interface configured to forward tagged frames (i.e., enabled for VLAN tagging).\n",
+ "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: -\tETH: generic Ethernet encapsulation. -\tVLAN: encapsulation based on VLAN. -\tVXLAN: encapsulation based on VXLAN.\n",
+ "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: -\tDOT1Q: used when packets on the CSE are encapsulated with one or a set of customer VLAN identifiers. -\tQINQ: 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",
+ "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"]
},
@@ -2108,7 +3048,7 @@
"required": ["peerMode"],
"properties": {
"peerMode": {
- "description": "Type of VXLAN access mode. Default value is \"STATIC\".\nPermitted values: -\tSTATIC -\tBGP_EVPN\n",
+ "description": "Type of VXLAN access mode. Default value is \"STATIC\".\nPermitted values: - STATIC - BGP_EVPN\n",
"type": "string",
"enum": ["STATIC", "BGP_EVPN"]
},
@@ -2180,7 +3120,7 @@
"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. NOTE: The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle.\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": {
@@ -2193,11 +3133,33 @@
"type": "string"
},
"resourceId": {
- "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",
+ "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": "Type of the resource in the scope of the VIM, the WIM or the resource provider. The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. See note.\n",
+ "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"
}
}
@@ -2249,7 +3211,7 @@
"required": ["routingProtocol", "routingAddressFamily"],
"properties": {
"routingProtocol": {
- "description": "The routing protocol that is activated on the connectivity service endpoint. Permitted values: -\tBGP: used for dynamic routing BGPv4. -\tRIP: used for dynamic routing RIPv2. -\tOSPF: used for dynamic routing (OSPF version 2 for IPv4; and OSPF version 3 for IPv6). -\tSTATIC: used for static routing. -\tDIRECT: used when the NFVI-PoP network is directly connected to the WAN provider network. -\tVRRP: used when the NFVI-PoP network is directly connected to the WAN provider network with virtual\n router redundancy protocol support (VRRP).\n",
+ "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"]
},
@@ -2259,7 +3221,7 @@
"required": ["ipVersion", "ipPrefix", "prefixSize", "nextHop"],
"properties": {
"ipVersion": {
- "description": "The IP version applicable to the routing entry. Permitted values: -\tIPV4 -\tIPV6\n",
+ "description": "The IP version applicable to the routing entry. Permitted values: - IPV4 - IPV6\n",
"type": "string",
"enum": ["IPV4", "IPV6"]
},
@@ -2280,7 +3242,7 @@
}
},
"routingAddressFamily": {
- "description": "The IP version applicable to the dynamic routing protocol. Shall be present for dynamic routing protocols. Permitted values: -\tIPV4 -\tIPV6\n",
+ "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"]
},
@@ -2321,7 +3283,7 @@
"required": ["policy", "sequence", "matchAndSetRule"],
"properties": {
"policy": {
- "description": "The policy to apply to the route distribution.\nPermitted values: -\tPERMIT -\tDENY\n",
+ "description": "The policy to apply to the route distribution.\nPermitted values: - PERMIT - DENY\n",
"type": "string",
"enum": ["PERMIT", "DENY"]
},
diff --git a/SOL005/NSLifecycleManagement-API/schemas/NsLcmOperationOccurrenceNotification.schema.json b/SOL005/NSLifecycleManagement-API/schemas/NsLcmOperationOccurrenceNotification.schema.json
index ab1f0d9de2653bc506f50ff8790a2b5db3d2dd2d..f4420d9291c13fb30f3b029f63d8df22000f30d7 100644
--- a/SOL005/NSLifecycleManagement-API/schemas/NsLcmOperationOccurrenceNotification.schema.json
+++ b/SOL005/NSLifecycleManagement-API/schemas/NsLcmOperationOccurrenceNotification.schema.json
@@ -1,1371 +1,1234 @@
{
- "type": "object",
- "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",
- "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": "The enumeration NsLcmOperationStateType shall comply with the provisions defined in Table 6.5.4.4-1. Value | Description ------|------------ PROCESSING | The LCM operation is currently in execution. COMPLETED | The LCM operation has been completed successfully. PARTIALLY_COMPLETED | The LCM operation has been partially completed with accepTable errors. FAILED_TEMP | The LCM operation has failed and execution has stopped, but the execution of the operation is not considered to be closed. FAILED | The LCM operation has failed and it cannot be retried or rolled back, as it is determined that such action won't succeed. OLLING_BACK | The LCM operation is currently being rolled back. ROLLED_BACK | The LCM operation has been successfully rolled back, i.e. The state of the VNF prior to the original operation invocation has been restored as closely as possible.\n",
- "type": "string",
- "enum": [
- "PROCESSING",
- "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. Shall be present if the \"notificationStatus\" is set to \"RESULT\", the \"verbosity\" attribute is set to \"FULL\" and the operation has performed any resource modification. Shall be absent otherwise. This attribute contains information about the cumulative changes to virtualised resources that were performed so far by the NS LCM operation occurrence and by any of the error handling procedures for that operation occurrence.\n",
- "type": "array",
- "items": {
- "description": "This type provides information about added, deleted and modified VNFs. It shall comply with the provisions in Table 6.5.3.2-1.\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 -\tCHANGE_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"
- },
- "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"
- },
- "vnfdId": {
- "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"
- },
- "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"
- }
- }
- },
- "changedExtConnectivity": {
- "description": "Information about changed external connectivity, if applicable.\n",
- "type": "array",
- "items": {
- "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.\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 other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Type of the resource in the scope of the VIM, the WIM or the resource provider. The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle.\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. \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.\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 other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Type of the resource in the scope of the VIM, the WIM or the resource provider. The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle.\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"
- }
- }
- }
- },
- "currentVnfExtCpData": {
- "description": "This type represents configuration information for external CPs created from a CPD.\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 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). 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. 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.\n",
- "type": "object",
- "additionalProperties": {
- "description": "This type represents an externally provided link port or network address information per instance of an external connection point. In case a link port is provided, the VNFM shall use that link port when connecting the external CP to the external VL. In a link port is not provided, the VNFM shall create a link port on the external VL, and use that link port to connect the external CP to the external VL.\n",
- "type": "object",
- "anyOf": [
- {
- "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"
- },
- "cpProtocolData": {
- "description": "Parameters for configuring the network protocols on the link port that connects the CP to a VL. The following conditions apply to the attributes \"linkPortId\" and \"cpProtocolData\": * At least one of the \"linkPortId\" and \"cpProtocolData\" attributes\n shall be present for a to-be-created external CP instance or an\n existing external CP instance.\n* If the \"linkPortId\" attribute is absent, the VNFM shall create a\n link port.\n* If the \"cpProtocolData\" attribute is absent, the \"linkPortId\"\n attribute shall be provided referencing a pre-created link port,\n and the VNFM can use means outside the scope of the present\n document to obtain the pre-configured address information for the\n connection point from the resource representing the link port.\n* If both \"cpProtocolData\" and \"linkportId\" are provided, the API\n consumer shall ensure that the cpProtocolData can be used with the\n pre-created link port referenced by \"linkPortId\".\n",
- "type": "array",
- "items": {
- "description": "This type represents network protocol data.\n",
- "type": "object",
- "required": [
- "layerProtocol"
- ],
- "properties": {
- "layerProtocol": {
- "description": "Identifier of layer(s) and protocol(s). Permitted values: IP_OVER_ETHERNET.\n",
- "type": "string",
- "enum": [
- "IP_OVER_ETHERNET"
- ]
- },
- "ipOverEthernet": {
- "description": "This type represents network address data for IP over Ethernet.\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"
- },
- "segmentationId": {
- "description": "Identification of the network segment to which the Cp instance connects to. If the Cp instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. 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": "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.\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, 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). Exactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present.\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 other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- }
- },
- "modificationsTriggeredByVnfPkgChange": {
- "description": "This type represents attribute modifications that were performed on an \"Individual VNF instance\" resource when changing the current VNF package. The attributes that can be included consist of those requested to be modified explicitly in the \"ChangeCurrentVnfPkgRequest\" data structure, and additional attributes of the \"VnfInstance\" data structure that were modified implicitly during the operation. 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. Shall be present if the \"notificationStatus\" is set to \"RESULT\", the \"verbosity\" attribute is set to \"FULL\" and the operation has performed any resource modification. Shall be absent otherwise. This attribute contains information about the cumulative changes to virtualised resources that were performed so far by the NS LCM operation occurrence and by any of the error handling procedures for that operation occurrence.\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. Shall be present if the \"notificationStatus\" is set to \"RESULT\", the \"verbosity\" attribute is set to \"FULL\" and the operation has performed any resource modification. Shall be absent otherwise. This attribute contains information about the cumulative changes to virtualised resources that were performed so far by the NS LCM operation occurrence and by any of the error handling procedures for that operation occurrence.\n",
- "type": "array",
- "items": {
- "description": "This type provides information about added, deleted, modified and temporary VLs.\n",
- "type": "object",
- "required": [
- "id",
- "virtualLinkDescId",
- "changeType",
- "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"
- },
- "virtualLinkDescId": {
- "description": "Identifier of the VNF Virtual Link Descriptor (VLD) in the VNFD.\n",
- "type": "string"
- },
- "changeType": {
- "description": "Signals the type of change. Permitted values: * ADDED * REMOVED * MODIFIED * TEMPORARY * LINK_PORT_ADDED * LINK_PORT_REMOVED For a temporary resource, an AffectedVirtualLink structure exists as long as the temporary resource exists.\n",
- "type": "string",
- "enum": [
- "ADDED",
- "REMOVED",
- "MODIFIED",
- "TEMPORARY",
- "LINK_PORT_ADDED",
- "LINK_PORT_REMOVED"
- ]
- },
- "linkPortIds": {
- "description": "Identifiers of the link ports of the affected VL related to the change. Each identifier references an \"NsLinkPortInfo\" structure. Shall 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. The resource handles of the affected NS link ports can be found by dereferencing the identifiers in the \"linkPortIds\" attribute.\n",
- "type": "array",
- "items": {
- "description": "An identifier that is unique with respect to a NS. Representation: string of variable length.\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.\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 other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Type of the resource in the scope of the VIM, the WIM or the resource provider. The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle.\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"
- }
- }
- }
- },
- "affectedVnffg": {
- "description": "Information about the VNFFG instances that were affected during the lifecycle operation. Shall be present if the \"notificationStatus\" is set to \"RESULT\", the \"verbosity\" attribute is set to \"FULL\" and the operation has performed any resource modification. Shall be absent otherwise. This attribute contains information about the cumulative changes to virtualised resources that were performed so far by the NS LCM operation occurrence and by any of the error handling procedures for that operation occurrence.\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. Shall be present if the \"notificationStatus\" is set to \"RESULT\", the \"verbosity\" attribute is set to \"FULL\" and the operation has performed any resource modification. Shall be absent otherwise. This attribute contains information about the cumulative changes to virtualised resources that were performed so far by the NS LCM operation occurrence and by any of the error handling procedures for that operation occurrence.\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"
- },
- "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"
- },
- "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"
- },
- "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 WAN’s perspective. Permitted values: -\tINBOUND: to indicate into the WAN. -\tOUTBOUND: to indicate from the WAN. -\tBOTH: 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"
- }
- }
- }
- }
- },
- "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.\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: -\tCSE: defined by the characteristics of the existing referred connectivity service point. -\tAGGREGATE_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: -\tPARENT: use the mapped interface to the connectivity service endpoint as is, i.e., do not create logical interfaces. -\tLOGICAL: create logical interfaces.\n",
- "type": "string",
- "enum": [
- "PARENT",
- "LOGICAL"
- ]
- },
- "interfaceTagging": {
- "description": "The type of frames to forward on the connectivity service point. Permitted values: -\tUNTAGGED: an interface where frames are not tagged. -\tTAGGED: 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: -\tETH: generic Ethernet encapsulation. -\tVLAN: encapsulation based on VLAN. -\tVXLAN: 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: -\tDOT1Q: used when packets on the CSE are encapsulated with one or a set of customer VLAN identifiers. -\tQINQ: 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: -\tSTATIC -\tBGP_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. Either \"networkResources\" or \"vnSegmentsIds\" shall be provided, but not both.\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.\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 other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Type of the resource in the scope of the VIM, the WIM or the resource provider. The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle.\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: -\tBGP: used for dynamic routing BGPv4. -\tRIP: used for dynamic routing RIPv2. -\tOSPF: used for dynamic routing (OSPF version 2 for IPv4; and OSPF version 3 for IPv6). -\tSTATIC: used for static routing. -\tDIRECT: used when the NFVI-PoP network is directly connected to the WAN provider network. -\tVRRP: 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: -\tIPV4 -\tIPV6\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: -\tIPV4 -\tIPV6\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: -\tPERMIT -\tDENY\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. Shall be present if the \"notificationStatus\" is set to \"RESULT\", the \"verbosity\" attribute is set to \"FULL\" and the operation has performed any resource modification. Shall be absent otherwise. This attribute contains information about the cumulative changes to virtualised resources that were performed so far by the NS LCM operation occurrence and by any of the error handling procedures for that operation occurrence.\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"
- ]
- }
- }
- }
- },
- "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",
- "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": [
- "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"
- }
- }
- }
- }
- }
- }
+ "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"],
+ "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": {
+ "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"
+ },
+ "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"
+ },
+ "vnfdId": {
+ "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"
+ },
+ "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"
+ }
+ }
+ },
+ "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",
+ "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"
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ },
+ "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"
+ },
+ "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"]
+ }
+ }
+ }
+ },
+ "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"
+ },
+ "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"
+ },
+ "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"
+ },
+ "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 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"
+ }
+ }
+ }
+ }
+ },
+ "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 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"
+ }
+ }
+ }
+ }
+ }
+ },
+ "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"]
+ }
+ }
+ }
+ },
+ "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",
+ "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": ["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"
+ }
+ }
+ }
+ }
+ }
+ }
}
\ 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 008e86cc3e591e126220b5fba2bcd5a12596cf4a..b10ddb60c02f5d91f8c8ad05d6eb4f7391bd0a9b 100644
--- a/SOL005/NSLifecycleManagement-API/schemas/VnfSnapshotInfo.schema.json
+++ b/SOL005/NSLifecycleManagement-API/schemas/VnfSnapshotInfo.schema.json
@@ -26,10 +26,12 @@
},
"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": {
@@ -73,6 +75,40 @@
"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 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"
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ },
"vnfPkgId": {
"description": "An identifier with the intention of being globally unique.\n",
"type": "string"
@@ -152,11 +188,15 @@
"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:\tThe attributes \"associatedVnfcCpId\", \"associatedVipCpId\" and \"associatedVnfVirtualLinkId\" are mutually exclusive. Exactly one shall be present. NOTE 2:\tAn external CP instance is not associated to a link port in the cases indicated for the “extLinkPorts” attribute in clause 6.5.3.26.\n",
+ "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"],
+ "required": ["id", "cpdId", "cpProtocolInfo"],
"oneOf": [{
"required": ["associatedVnfcCpId"]
+ }, {
+ "required": ["associatedVipCpId"]
+ }, {
+ "required": ["associatedVirtualCpId"]
}, {
"required": ["associatedVnfVirtualLinkId"]
}],
@@ -182,17 +222,17 @@
"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:\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",
+ "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\nSee note.\n",
+ "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"]
+ "enum": ["IP_OVER_ETHERNET", "IP_FOR_VIRTUAL_CP"]
},
"ipOverEthernet": {
- "description": "This type represents information about a network address that has been assigned.\nNOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4:\tDepending 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",
+ "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"]
@@ -257,7 +297,7 @@
}
},
"subnetId": {
- "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",
+ "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"
}
}
@@ -305,10 +345,27 @@
"format": "IP"
},
"subnetId": {
- "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",
+ "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"
+ }
+ }
}
}
}
@@ -317,6 +374,14 @@
"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"
@@ -329,6 +394,10 @@
"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"
@@ -364,17 +433,17 @@
"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:\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",
+ "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\nSee note.\n",
+ "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"]
+ "enum": ["IP_OVER_ETHERNET", "IP_FOR_VIRTUAL_CP"]
},
"ipOverEthernet": {
- "description": "This type represents information about a network address that has been assigned.\nNOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4:\tDepending 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",
+ "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"]
@@ -439,7 +508,7 @@
}
},
"subnetId": {
- "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",
+ "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"
}
}
@@ -487,10 +556,27 @@
"format": "IP"
},
"subnetId": {
- "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",
+ "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"
+ }
+ }
}
}
}
@@ -508,7 +594,290 @@
"type": "string"
},
"metadata": {
- "description": "Allows the OSS/BSS to provide additional parameter(s) to the termination process at the NS level.\n",
+ "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",
@@ -522,15 +891,16 @@
"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"],
+ "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. NOTE: The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle.\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": {
@@ -543,11 +913,33 @@
"type": "string"
},
"resourceId": {
- "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",
+ "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": "Type of the resource in the scope of the VIM, the WIM or the resource provider. The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. See note.\n",
+ "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"
}
}
@@ -556,7 +948,7 @@
"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:\tThe 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:\tThe value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\" attribute.\n",
+ "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": {
@@ -565,7 +957,7 @@
"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. NOTE: The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle.\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": {
@@ -578,11 +970,33 @@
"type": "string"
},
"resourceId": {
- "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",
+ "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": "Type of the resource in the scope of the VIM, the WIM or the resource provider. The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. See note.\n",
+ "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"
}
}
@@ -602,8 +1016,84 @@
}
}
},
+ "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:\tIn 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: \tThe 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: \tWithin 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",
+ "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": {
@@ -615,9 +1105,9 @@
"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 network address information per instance of an external connection point. In case a link port is provided, the VNFM shall use that link port when connecting the external CP to the external VL. In a link port is not provided, the VNFM shall create a link port on the external VL, and use that link port to connect the external CP to the external VL. NOTE 1:\tThe following conditions apply to the attributes \"linkPortId\" and \"cpProtocolData\":\n -\tAt 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 -\tIf the \"cpProtocolData\" attribute is absent, the \"linkPortId\" attribute shall be provided\n referencing a pre-created link port with pre-configured address information.\n -\tIf 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:\tIn 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.\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 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",
- "anyOf": [{
+ "oneOf": [{
"required": ["linkPortId"]
}, {
"required": ["cpProtocolData"]
@@ -636,20 +1126,20 @@
"type": "boolean"
},
"cpProtocolData": {
- "description": "Parameters for configuring the network protocols on the link port that connects the CP to a VL. See note 1.\n",
+ "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.\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.\n",
+ "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"]
+ "enum": ["IP_OVER_ETHERNET", "IP_FOR_VIRTUAL_CP"]
},
"ipOverEthernet": {
- "description": "This type represents network address data for IP over Ethernet. NOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present. NOTE 3:\tIf the CP instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4:\tDepending 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",
+ "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"]
@@ -663,7 +1153,7 @@
"format": "MAC"
},
"segmentationType": {
- "description": "Specifies the encapsulation type for the traffics coming in and out of the trunk subport. Permitted values are: -\tVLAN: The subport uses VLAN as encapsulation type. -\tINHERIT: 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",
+ "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"]
},
@@ -721,16 +1211,41 @@
}
},
"subnetId": {
- "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",
+ "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"
+ }
}
}
}
@@ -744,8 +1259,9 @@
"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"],
+ "required": ["id", "vnfVirtualLinkDescId", "networkResource"],
"properties": {
"id": {
"description": "An identifier with the intention of being globally unique.\n",
@@ -760,25 +1276,51 @@
"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. NOTE: The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle.\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 other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Type of the resource in the scope of the VIM, the WIM or the resource provider. The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. See note.\n",
- "type": "string"
+ "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"
+ }
}
}
},
@@ -787,7 +1329,7 @@
"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:\tEither 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",
+ "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": {
@@ -795,7 +1337,7 @@
"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. NOTE: The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle.\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": {
@@ -808,11 +1350,33 @@
"type": "string"
},
"resourceId": {
- "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",
+ "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": "Type of the resource in the scope of the VIM, the WIM or the resource provider. The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. See note.\n",
+ "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"
}
}
@@ -837,6 +1401,78 @@
}
}
},
+ "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"
@@ -879,7 +1515,7 @@
"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. NOTE 1:\tETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on TOSCA specifications. NOTE 2:\tA 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:\tThe information can be omitted because it is already available as part of the external CP information. \n",
+ "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": {
@@ -896,7 +1532,7 @@
"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. NOTE: The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle.\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": {
@@ -909,20 +1545,42 @@
"type": "string"
},
"resourceId": {
- "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",
+ "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": "Type of the resource in the scope of the VIM, the WIM or the resource provider. The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. See note.\n",
+ "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. The value refers to a VirtualStorageResourceInfo item in the VnfInstance.\n",
+ "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 with the intention of being globally unique.\n",
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
"type": "string"
}
},
@@ -953,17 +1611,17 @@
"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:\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",
+ "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\nSee note.\n",
+ "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"]
+ "enum": ["IP_OVER_ETHERNET", "IP_FOR_VIRTUAL_CP"]
},
"ipOverEthernet": {
- "description": "This type represents information about a network address that has been assigned.\nNOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4:\tDepending 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",
+ "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"]
@@ -1028,7 +1686,7 @@
}
},
"subnetId": {
- "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",
+ "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"
}
}
@@ -1076,10 +1734,27 @@
"format": "IP"
},
"subnetId": {
- "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",
+ "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"
+ }
+ }
}
}
}
@@ -1092,6 +1767,14 @@
"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"
@@ -1127,7 +1810,7 @@
"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. NOTE: The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle.\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": {
@@ -1140,11 +1823,33 @@
"type": "string"
},
"resourceId": {
- "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",
+ "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": "Type of the resource in the scope of the VIM, the WIM or the resource provider. The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. See note.\n",
+ "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"
}
}
@@ -1158,7 +1863,7 @@
"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:\tEither 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",
+ "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": {
@@ -1166,7 +1871,7 @@
"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. NOTE: The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle.\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": {
@@ -1179,11 +1884,33 @@
"type": "string"
},
"resourceId": {
- "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",
+ "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": "Type of the resource in the scope of the VIM, the WIM or the resource provider. The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. See note.\n",
+ "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"
}
}
@@ -1236,7 +1963,7 @@
"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. NOTE: The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle.\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": {
@@ -1249,11 +1976,33 @@
"type": "string"
},
"resourceId": {
- "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",
+ "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": "Type of the resource in the scope of the VIM, the WIM or the resource provider. The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. See note.\n",
+ "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"
}
}
@@ -1268,6 +2017,53 @@
}
}
}
+ },
+ "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"
+ }
+ }
+ }
}
}
},
@@ -1285,7 +2081,7 @@
"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:\tThe 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:\tThe 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",
+ "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": {
@@ -1299,10 +2095,12 @@
},
"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": {
@@ -1310,7 +2108,7 @@
"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. NOTE: The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle.\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": {
@@ -1323,11 +2121,33 @@
"type": "string"
},
"resourceId": {
- "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",
+ "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": "Type of the resource in the scope of the VIM, the WIM or the resource provider. The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. See note.\n",
+ "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"
}
}
@@ -1344,7 +2164,7 @@
"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. NOTE: The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle.\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": {
@@ -1357,11 +2177,33 @@
"type": "string"
},
"resourceId": {
- "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",
+ "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": "Type of the resource in the scope of the VIM, the WIM or the resource provider. The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. See note.\n",
+ "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"
}
}
diff --git a/SOL005/NSLifecycleManagement-API/schemas/VnfSnapshotsInfo.schema.json b/SOL005/NSLifecycleManagement-API/schemas/VnfSnapshotsInfo.schema.json
index b539fb692ce4685b81def336b4c15614fe04d1b0..986e20101d2be0e26fba70fc7dd5ca389546ebcc 100644
--- a/SOL005/NSLifecycleManagement-API/schemas/VnfSnapshotsInfo.schema.json
+++ b/SOL005/NSLifecycleManagement-API/schemas/VnfSnapshotsInfo.schema.json
@@ -28,10 +28,12 @@
},
"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": {
@@ -75,6 +77,40 @@
"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 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"
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ },
"vnfPkgId": {
"description": "An identifier with the intention of being globally unique.\n",
"type": "string"
@@ -154,11 +190,15 @@
"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:\tThe attributes \"associatedVnfcCpId\", \"associatedVipCpId\" and \"associatedVnfVirtualLinkId\" are mutually exclusive. Exactly one shall be present. NOTE 2:\tAn external CP instance is not associated to a link port in the cases indicated for the “extLinkPorts” attribute in clause 6.5.3.26.\n",
+ "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"],
+ "required": ["id", "cpdId", "cpProtocolInfo"],
"oneOf": [{
"required": ["associatedVnfcCpId"]
+ }, {
+ "required": ["associatedVipCpId"]
+ }, {
+ "required": ["associatedVirtualCpId"]
}, {
"required": ["associatedVnfVirtualLinkId"]
}],
@@ -184,17 +224,17 @@
"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:\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",
+ "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\nSee note.\n",
+ "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"]
+ "enum": ["IP_OVER_ETHERNET", "IP_FOR_VIRTUAL_CP"]
},
"ipOverEthernet": {
- "description": "This type represents information about a network address that has been assigned.\nNOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4:\tDepending 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",
+ "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"]
@@ -259,7 +299,7 @@
}
},
"subnetId": {
- "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",
+ "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"
}
}
@@ -307,10 +347,27 @@
"format": "IP"
},
"subnetId": {
- "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",
+ "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"
+ }
+ }
}
}
}
@@ -319,6 +376,14 @@
"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"
@@ -331,6 +396,10 @@
"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"
@@ -366,17 +435,17 @@
"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:\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",
+ "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\nSee note.\n",
+ "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"]
+ "enum": ["IP_OVER_ETHERNET", "IP_FOR_VIRTUAL_CP"]
},
"ipOverEthernet": {
- "description": "This type represents information about a network address that has been assigned.\nNOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4:\tDepending 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",
+ "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"]
@@ -441,7 +510,7 @@
}
},
"subnetId": {
- "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",
+ "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"
}
}
@@ -489,10 +558,27 @@
"format": "IP"
},
"subnetId": {
- "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",
+ "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"
+ }
+ }
}
}
}
@@ -510,7 +596,290 @@
"type": "string"
},
"metadata": {
- "description": "Allows the OSS/BSS to provide additional parameter(s) to the termination process at the NS level.\n",
+ "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",
@@ -524,15 +893,16 @@
"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"],
+ "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. NOTE: The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle.\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": {
@@ -545,11 +915,33 @@
"type": "string"
},
"resourceId": {
- "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",
+ "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": "Type of the resource in the scope of the VIM, the WIM or the resource provider. The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. See note.\n",
+ "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"
}
}
@@ -558,7 +950,7 @@
"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:\tThe 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:\tThe value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\" attribute.\n",
+ "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": {
@@ -567,7 +959,7 @@
"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. NOTE: The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle.\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": {
@@ -580,11 +972,33 @@
"type": "string"
},
"resourceId": {
- "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",
+ "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": "Type of the resource in the scope of the VIM, the WIM or the resource provider. The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. See note.\n",
+ "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"
}
}
@@ -604,8 +1018,84 @@
}
}
},
+ "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:\tIn 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: \tThe 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: \tWithin 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",
+ "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": {
@@ -617,9 +1107,9 @@
"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 network address information per instance of an external connection point. In case a link port is provided, the VNFM shall use that link port when connecting the external CP to the external VL. In a link port is not provided, the VNFM shall create a link port on the external VL, and use that link port to connect the external CP to the external VL. NOTE 1:\tThe following conditions apply to the attributes \"linkPortId\" and \"cpProtocolData\":\n -\tAt 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 -\tIf the \"cpProtocolData\" attribute is absent, the \"linkPortId\" attribute shall be provided\n referencing a pre-created link port with pre-configured address information.\n -\tIf 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:\tIn 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.\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 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",
- "anyOf": [{
+ "oneOf": [{
"required": ["linkPortId"]
}, {
"required": ["cpProtocolData"]
@@ -638,20 +1128,20 @@
"type": "boolean"
},
"cpProtocolData": {
- "description": "Parameters for configuring the network protocols on the link port that connects the CP to a VL. See note 1.\n",
+ "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.\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.\n",
+ "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"]
+ "enum": ["IP_OVER_ETHERNET", "IP_FOR_VIRTUAL_CP"]
},
"ipOverEthernet": {
- "description": "This type represents network address data for IP over Ethernet. NOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" shall be present. NOTE 3:\tIf the CP instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4:\tDepending 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",
+ "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"]
@@ -665,7 +1155,7 @@
"format": "MAC"
},
"segmentationType": {
- "description": "Specifies the encapsulation type for the traffics coming in and out of the trunk subport. Permitted values are: -\tVLAN: The subport uses VLAN as encapsulation type. -\tINHERIT: 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",
+ "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"]
},
@@ -723,16 +1213,41 @@
}
},
"subnetId": {
- "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",
+ "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"
+ }
}
}
}
@@ -746,8 +1261,9 @@
"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"],
+ "required": ["id", "vnfVirtualLinkDescId", "networkResource"],
"properties": {
"id": {
"description": "An identifier with the intention of being globally unique.\n",
@@ -762,25 +1278,51 @@
"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. NOTE: The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle.\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 other resource provider. It is expected to be unique within the VIM instance. Representation: string of variable length.\n",
- "type": "string"
- },
- "vimLevelResourceType": {
- "description": "Type of the resource in the scope of the VIM, the WIM or the resource provider. The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. See note.\n",
- "type": "string"
+ "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"
+ }
}
}
},
@@ -789,7 +1331,7 @@
"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:\tEither 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",
+ "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": {
@@ -797,7 +1339,7 @@
"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. NOTE: The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle.\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": {
@@ -810,11 +1352,33 @@
"type": "string"
},
"resourceId": {
- "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",
+ "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": "Type of the resource in the scope of the VIM, the WIM or the resource provider. The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. See note.\n",
+ "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"
}
}
@@ -839,6 +1403,78 @@
}
}
},
+ "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"
@@ -881,7 +1517,7 @@
"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. NOTE 1:\tETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on TOSCA specifications. NOTE 2:\tA 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:\tThe information can be omitted because it is already available as part of the external CP information. \n",
+ "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": {
@@ -898,7 +1534,7 @@
"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. NOTE: The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle.\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": {
@@ -911,20 +1547,42 @@
"type": "string"
},
"resourceId": {
- "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",
+ "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": "Type of the resource in the scope of the VIM, the WIM or the resource provider. The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. See note.\n",
+ "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. The value refers to a VirtualStorageResourceInfo item in the VnfInstance.\n",
+ "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 with the intention of being globally unique.\n",
+ "description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
"type": "string"
}
},
@@ -955,17 +1613,17 @@
"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:\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",
+ "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\nSee note.\n",
+ "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"]
+ "enum": ["IP_OVER_ETHERNET", "IP_FOR_VIRTUAL_CP"]
},
"ipOverEthernet": {
- "description": "This type represents information about a network address that has been assigned.\nNOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. NOTE 2:\tExactly one of \"addresses\" or \"addressRange\" shall be present. NOTE 3:\tIf the Cp instance represents a subport in a trunk, \"segmentationId\" shall be present. Otherwise it shall not be present. NOTE 4:\tDepending 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",
+ "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"]
@@ -1030,7 +1688,7 @@
}
},
"subnetId": {
- "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",
+ "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"
}
}
@@ -1078,10 +1736,27 @@
"format": "IP"
},
"subnetId": {
- "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",
+ "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"
+ }
+ }
}
}
}
@@ -1094,6 +1769,14 @@
"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"
@@ -1129,7 +1812,7 @@
"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. NOTE: The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle.\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": {
@@ -1142,11 +1825,33 @@
"type": "string"
},
"resourceId": {
- "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",
+ "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": "Type of the resource in the scope of the VIM, the WIM or the resource provider. The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. See note.\n",
+ "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"
}
}
@@ -1160,7 +1865,7 @@
"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:\tEither 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",
+ "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": {
@@ -1168,7 +1873,7 @@
"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. NOTE: The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle.\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": {
@@ -1181,11 +1886,33 @@
"type": "string"
},
"resourceId": {
- "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",
+ "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": "Type of the resource in the scope of the VIM, the WIM or the resource provider. The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. See note.\n",
+ "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"
}
}
@@ -1238,7 +1965,7 @@
"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. NOTE: The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle.\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": {
@@ -1251,11 +1978,33 @@
"type": "string"
},
"resourceId": {
- "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",
+ "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": "Type of the resource in the scope of the VIM, the WIM or the resource provider. The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. See note.\n",
+ "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"
}
}
@@ -1270,6 +2019,53 @@
}
}
}
+ },
+ "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"
+ }
+ }
+ }
}
}
},
@@ -1287,7 +2083,7 @@
"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:\tThe 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:\tThe 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",
+ "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": {
@@ -1301,10 +2097,12 @@
},
"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": {
@@ -1312,7 +2110,7 @@
"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. NOTE: The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle.\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": {
@@ -1325,11 +2123,33 @@
"type": "string"
},
"resourceId": {
- "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",
+ "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": "Type of the resource in the scope of the VIM, the WIM or the resource provider. The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. See note.\n",
+ "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"
}
}
@@ -1346,7 +2166,7 @@
"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. NOTE: The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle.\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": {
@@ -1359,11 +2179,33 @@
"type": "string"
},
"resourceId": {
- "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",
+ "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": "Type of the resource in the scope of the VIM, the WIM or the resource provider. The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM, the WIM or the resource provider and can be used as information that complements the ResourceHandle. See note.\n",
+ "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"
}
}
diff --git a/SOL005/NSPerformanceManagement-API/ApiVersion.robot b/SOL005/NSPerformanceManagement-API/ApiVersion.robot
index e9fba6908d5940b1436b772c8c08daf91e407a1f..ab7fd566544c93d15da50d2580044deafaca2bb9 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 v2.7.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.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 v2.7.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.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 v2.7.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.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 v2.7.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.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 v2.7.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.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 v2.7.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.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 v2.7.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.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 v2.7.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.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 v2.7.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.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 v2.7.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.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 f638d83a2c10009a35a61f6bad238b2dad7083b8..5cdc8137874297cfc9344b745ced13d7386330a4 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] v3.6.1
+ ... Reference: Clause 7.4.3.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.3.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.3.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.3.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.3.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 6.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.3.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: The NS Performance Job is no more available in the NFVO
@@ -105,7 +105,7 @@ 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] v3.6.1
+ ... Reference: Clause 7.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: The resource is not modified
@@ -118,7 +118,7 @@ PATCH Individual NS Performance Job - Unprocessable Entity
... Test title: PATCH Individual NS Performance Job - Unprocessable Entity
... 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] v3.6.1
+ ... Reference: Clause 7.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/NSPerformanceManagement-API/IndividualReport.robot b/SOL005/NSPerformanceManagement-API/IndividualReport.robot
index 9da05363b2cc275eb2e9a9350192309f7ede0d95..3b8d7ae460628a6ec4ca367438f6d39b60e37ff6 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] v3.6.1
+ ... Reference: Clause 7.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.4.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.4.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.4.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.4.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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 8a7d666ce3bc164e0f76ba4189df19689dc69aea..6cef2d8ab09405adba56994cc6021869b92b854e 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] v3.6.1
+ ... Reference: Clause 7.4.6.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.6.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.6.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.6.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.6.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.6.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.6.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.6.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: The NS performance Threshold is not modified by the operation
@@ -122,7 +122,7 @@ PATCH Individual Threshold - Unprocessable Entity
... Test title: PATCH Individual NS Performance Job - Unprocessable Entity
... 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] v3.6.1
+ ... Reference: Clause 7.4.6.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: The NS performance Threshold is not modified by the operation
diff --git a/SOL005/NSPerformanceManagement-API/NotificationEndpoint.robot b/SOL005/NSPerformanceManagement-API/NotificationEndpoint.robot
index ff0698f922e51c28e474adf9d6b902256913a41a..7bc788615474002d9acfe0a05b119c0255d29987 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] v3.6.1
+ ... Reference: Clause 7.4.9.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.9.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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 bc86b4197eda550d83983b929118e836615ff960..b88feb22e739460c64445f9ea09115d2d3be2350 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] v3.6.1
+ ... Reference: Clause 7.4.9.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.9.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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 ccf8fd2830e1d71ca1067f3a69fdde76b7ce9fe3..1525374ec72e212672590eaf8e998bb04428cea2 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] v3.6.1
+ ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 4.3.3.2.1, 7.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 4.3.3.2.1, 7.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 4.3.3.2.1, 7.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 4.3.3.2.1, 7.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.2.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.2.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.2.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.2.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 4.3.3.2.1, 7.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO supports the use of "include" attribute selector
... Post-Conditions: none
@@ -217,7 +217,7 @@ POST new NS Performance Monitoring Job - Unprocessable Entity
... Test title: POST new NS Performance Monitoring Job - Unprocessable Entity
... 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] v3.6.1
+ ... Reference: clause 7.4.2.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/NSPerformanceManagement-API/Thresholds.robot b/SOL005/NSPerformanceManagement-API/Thresholds.robot
index 80347a935848952cae1323205e7b52c27fea4736..832c4e5c3cd0a8d0762cb8a5407bae1158be5c4e 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] v3.6.1
+ ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.5.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.5.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.5.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.5.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 7.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -148,7 +148,7 @@ POST new Performance Threshold - Unprocessable Entity
... Test title: POST new Performance Threshold - Unprocessable Entity
... 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] v3.6.1
+ ... Reference: clause 7.4.5.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/VNFPackageManagement-API/AccessConfigurationForExternalArtifacts.robot b/SOL005/VNFPackageManagement-API/AccessConfigurationForExternalArtifacts.robot
index 23ade2531d0cbc681bed124d67d3ece61436c860..9d8a6e0800421ec86188206bb7b7c8ba980dc1b2 100644
--- a/SOL005/VNFPackageManagement-API/AccessConfigurationForExternalArtifacts.robot
+++ b/SOL005/VNFPackageManagement-API/AccessConfigurationForExternalArtifacts.robot
@@ -11,7 +11,7 @@ Get Access configuration for external artifacts
... 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] v3.6.1
+ ... Reference: Clause 9.4.4a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -24,7 +24,7 @@ Get Access configuration for external artifacts - Not Found
... 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] v3.6.1
+ ... Reference: Clause 9.4.4a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -37,7 +37,7 @@ PUT Access configuration for external artifacts
... 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] v3.6.1
+ ... Reference: Clause 9.4.4a.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -51,7 +51,7 @@ PUT Access configuration for external artifacts - Downloading
... 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] v3.6.1
+ ... Reference: Clause 9.4.4a.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -64,7 +64,7 @@ PUT Access configuration for external artifacts - Conflict
... 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] v3.6.1
+ ... Reference: Clause 9.4.4a.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -77,7 +77,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 allowed to create access configuration for external artifacts
... Pre-conditions: none
- ... Reference: Clause 9.4.4a.3.1 - ETSI GS NFV-SOL 005 [3] v3.6.1
+ ... Reference: Clause 9.4.4a.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -89,7 +89,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 allowed to update access configuration for external artifacts
... Pre-conditions: none
- ... Reference: Clause 9.4.4a.3.4 - ETSI GS NFV-SOL 005 [3] v3.6.1
+ ... Reference: Clause 9.4.4a.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -101,7 +101,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 allowed to delete access configuration for external artifacts
... Pre-conditions: none
- ... Reference: Clause 9.4.4a.3.5 - ETSI GS NFV-SOL 005 [3] v3.6.1
+ ... Reference: Clause 9.4.4a.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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 033ec626e75acb06ba000f8df5f4ece4e3bfc656..792731e76973ad88384b4baa3891e834d09c5a79 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] v3.5.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.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 e0c9c7de3654745b673cde5f6ce65a4f80f4f889..b6e959c2100e611a22982df0de751fddaf033f51 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] v3.6.1
+ ... Reference: Clause 9.4.9.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.9.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.9.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.9.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.9.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.9.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.9.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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 7a699c53f82ff426aa1d81eb33342e808614529b..ef2d378624eca5953c22f0915c9c1b8ed3931693 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] v3.6.1
+ ... Reference: Clause 9.4.3.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.3.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.3.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.3.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.3.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.3.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.3.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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 d4fab8ece5d48a348a0f6ecfe9ffbdf6e6ac24a0..f933d346d7c490ef01a50e70cd82ffb57ab802bb 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] v3.6.1
+ ... Reference: Clause 9.4.7.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.7.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.7.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.7.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.7.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.7.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.7.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.7.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.7.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.7.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.7.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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 20a7c5c87f0f813bda8c4a3901dbdc97efb724a8..2f08a9855f7e96e26d400ac49db23d3228d2c1eb 100644
--- a/SOL005/VNFPackageManagement-API/ManifestInIndividualVNFPackage.robot
+++ b/SOL005/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 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] v3.6.1
+ ... Reference: Clause 9.4.4b.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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 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] v3.6.1
+ ... Reference: Clause 9.4.4b.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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 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] v3.6.1
+ ... Reference: Clause 9.4.4b.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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 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] v3.6.1
+ ... Reference: Clause 9.4.4b.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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 Manifest
... Pre-conditions: none
- ... Reference: Clause 9.4.4b.3.1 - ETSI GS NFV-SOL 005 [3] v3.6.1
+ ... Reference: Clause 9.4.4b.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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 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] v3.6.1
+ ... Reference: Clause 9.4.4b.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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 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] v3.6.1
+ ... Reference: Clause 9.4.4b.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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 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] v3.6.1
+ ... Reference: Clause 9.4.4b.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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 ffb270f92b3aa9977f7ad4551ea9036384a39282..151a3b510ca1475f530e23384957344f1e55d21a 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] v3.6.1
+ ... Reference: Clause 9.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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 489eeeca2e30e36d8dc1e9319ec803cd06bb9278..9f0cede4615ae2d1f5abe1219ee42abd61501467 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] v3.6.1
+ ... Reference: Clause 9.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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 9a08d309673db3a2741d6df7637270bc04bfe25f..8bed781d057c7dbcb3e44511f7ebc8ba69714aa5 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] v3.6.1
+ ... Reference: Clause 9.4.8.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.8.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.8.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.8.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.8.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.8.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.8.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.8.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.8.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.8.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.8.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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 64d3d6a4e5a63ed9c93d6c2213e4994025b694a2..9a0db3c6a450bb612023d268ca391032022d6d4d 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] v3.6.1
+ ... Reference: Clause 9.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.4.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.4.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.4.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.4.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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 f8ebd2cfee724bb6d96d3feeaef658f273be6367..21c99fd66540b14f7e827e2357c46905aa187d79 100644
--- a/SOL005/VNFPackageManagement-API/VNFPackageArtifacts.robot
+++ b/SOL005/VNFPackageManagement-API/VNFPackageArtifacts.robot
@@ -12,7 +12,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 9.4.5a.3.2 - ETSI GS NFV-SOL 005 [3] v3.6.1
+ ... Reference: Clause 9.4.5a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -25,7 +25,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 9.4.5a.3.2 - ETSI GS NFV-SOL 005 [3] v3.6.1
+ ... Reference: Clause 9.4.5a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -38,7 +38,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 9.4.5a.3.2 - ETSI GS NFV-SOL 005 [3] v3.6.1
+ ... Reference: Clause 9.4.5a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -51,7 +51,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 9.4.5a.3.2 - ETSI GS NFV-SOL 005 [3] v3.6.1
+ ... Reference: Clause 9.4.5a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -64,7 +64,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 9.4.5a.3.2 - ETSI GS NFV-SOL 005 [3] v3.6.1
+ ... Reference: Clause 9.4.5a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -77,7 +77,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 9.4.5a.3.2 - ETSI GS NFV-SOL 005 [3] v3.6.1
+ ... Reference: Clause 9.4.5a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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
@@ -91,7 +91,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 9.4.5a.3.2 - ETSI GS NFV-SOL 005 [3] v3.6.1
+ ... Reference: Clause 9.4.5a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -104,7 +104,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 9.4.5a.3.2 - ETSI GS NFV-SOL 005 [3] v3.6.1
+ ... Reference: Clause 9.4.5a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -117,7 +117,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 9.4.5a.3.2 - ETSI GS NFV-SOL 005 [3] v3.6.1
+ ... Reference: Clause 9.4.5a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -130,7 +130,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 9.4.5a.3.2 - ETSI GS NFV-SOL 005 [3] v3.6.1
+ ... Reference: Clause 9.4.5a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -143,7 +143,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 9.4.5a.3.2 - ETSI GS NFV-SOL 005 [3] v3.6.1
+ ... Reference: Clause 9.4.5a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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
@@ -156,7 +156,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 9.4.5a.3.1 - ETSI GS NFV-SOL 005 [3] v3.6.1
+ ... Reference: Clause 9.4.5a.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -168,7 +168,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 9.4.5a.3.3 - ETSI GS NFV-SOL 005 [3] v3.6.1
+ ... Reference: Clause 9.4.5a.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -180,7 +180,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 9.4.5a.3.4 - ETSI GS NFV-SOL 005 [1] v3.3.1
+ ... Reference: Clause 9.4.5a.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -192,7 +192,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 9.4.6.3.5 - ETSI GS NFV-SOL 005 [3] v3.6.1
+ ... Reference: Clause 9.4.6.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
@@ -204,7 +204,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 9.4.5a.3.2 - ETSI GS NFV-SOL 005 [3] v3.6.1
+ ... Reference: Clause 9.4.5a.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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 a2848c116397c681e3b0f71f27cb9f74239e8699..20138c9d2d2bb63043f041f5a685103852c623e0 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] v3.6.1
+ ... Reference: Clause 9.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.5.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.5.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.5.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.5.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.5.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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 c7ae7ec5abe2f3d3d5f3603dd01a394ea0c0071c..fd930246af8183a5675f3f33f5981b8eced196bd 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] v3.6.1
+ ... Reference: Clause 9.4.6.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.6.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.6.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.6.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.6.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.6.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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 b0a23a9061d38c47bb46d322445afa83228f3105..ad935d8e9dfcc5dbcc4a914d6a90cd7d0ddd814a 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] v3.6.1
+ ... Reference: Clause 9.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 4.5.3.3, 9.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 4.5.3.3, 9.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 4.3.3.2.1, 9.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 4.3.3.2.1, 9.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 4.3.3.2.1, 9.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 4.3.3.2.1, 9.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.2.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.2.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.2.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.2.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 9.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL005/VNFPackageManagement-API/schemas/vnfPkgInfo.schema.json b/SOL005/VNFPackageManagement-API/schemas/vnfPkgInfo.schema.json
index c4aca23993b7e250c8b722fdad0f330919665dd8..fee9780add425e18f3b4567b0c5cf8c4952d0be1 100644
--- a/SOL005/VNFPackageManagement-API/schemas/vnfPkgInfo.schema.json
+++ b/SOL005/VNFPackageManagement-API/schemas/vnfPkgInfo.schema.json
@@ -11,6 +11,10 @@
"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"
@@ -110,6 +114,7 @@
},
"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": {
diff --git a/SOL005/VNFPackageManagement-API/schemas/vnfPkgsInfo.schema.json b/SOL005/VNFPackageManagement-API/schemas/vnfPkgsInfo.schema.json
index a3b8c3071a9c9e8b92e5b42b5b662670e15d8600..c9e165f061c64b5a03b59d5a6a7b3237e4dc6668 100644
--- a/SOL005/VNFPackageManagement-API/schemas/vnfPkgsInfo.schema.json
+++ b/SOL005/VNFPackageManagement-API/schemas/vnfPkgsInfo.schema.json
@@ -1,7 +1,6 @@
{
"type": "array",
- "items":
- {
+ "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"],
@@ -14,6 +13,10 @@
"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"
@@ -113,6 +116,7 @@
},
"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": {
diff --git a/SOL005/VNFSnapshotPackageManagement-API/AccessConfigurationForExternalArtifacts.robot b/SOL005/VNFSnapshotPackageManagement-API/AccessConfigurationForExternalArtifacts.robot
index 765b106acfd8c92b6fbe26ce51244d3ca6418f5c..ae16fc6ce482514b9af7efa5e932c98dac933b6e 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] v3.6.1
+ ... Reference: Clause 11.4.9.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.9.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.9.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.9.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.8.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.8.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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 8701c947447c85ce4132ba6aa8b46c22e4d0a3b2..8f7d9b223163e1e881309cb01913115536248baf 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] v3.5.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.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 21a1ddef956704e6a6d65227bc64ba8e3e23aa48..1adf0ed4bc91c87a5207dcded24f9308a3d74e5c 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] v3.6.1
+ ... Reference: Clause 11.4.6.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.6.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.6.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.6.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.6.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.6.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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 625a843f66d39020cb011935368d5b38b19a81cf..a37504eb2975bfef2d2cc6fc9141a46c4d71b5db 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] v3.6.1
+ ... Reference: Clause 11.4.8.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.8.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.8.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.8.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.8.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.8.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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 24a70238f98f467fc08593e02dfebd2eebbce628..dec6b8c119898f137a1a955fd1a40a0b5e7030ed 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] v3.6.1
+ ... Reference: Clause 11.4.7.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.7.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.7.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.7.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.7.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.7.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.7.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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 adfb3096567361f2fccfdf57cce93e36c371d74f..9361a41e4062a1ce7be5692a0e7162f1ed0e2f5e 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] v3.6.1
+ ... Reference: Clause 11.4.3.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.3.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.3.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.3.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.3.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.3.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.3.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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 88f47847a62cef80d0b97d80d48f76a4f5b08e2a..0b58125d004592184ec6b20a9728d2564bc5e866 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] v3.6.1
+ ... Reference: Clause 11.4.10.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.10.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.10.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.10.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.10.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.10.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.10.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.10.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.10.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.10.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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 5d78f2c540c9ff5d65af13a7f232628e330b256c..d9f9f145b177f99db31576cf4cd8ee4598270072 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] v3.6.1
+ ... Reference: Clause 11.4.5.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.5.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.5.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.5.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.5.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.5.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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 b72afd421845e9b3dddb4d2dd84edf8b977944f7..8f9a42c9d54cacdb80ecb0eedc72e0c1f8f84d75 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] v3.6.1
+ ... Reference: Clause 11.4.4.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.4.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.4.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.4.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.4.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.4.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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 bde1b8a62654ca75fdccd92da5321a812fa5d648..50323c3701b9dd8f65bdbef869525b6dd25f4a0f 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] v3.6.1
+ ... Reference: Clause 11.4.2.3.1 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.2.3.3 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.2.3.4 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.2.3.5 - ETSI GS NFV-SOL 005 [3] v4.3.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] v3.6.1
+ ... Reference: Clause 11.4.2.3.2 - ETSI GS NFV-SOL 005 [3] v4.3.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL009/NFVMANOFaultManagement-API/Alarms.robot b/SOL009/NFVMANOFaultManagement-API/Alarms.robot
index 43eec3bc899d92c7d0b3def7cdc9409e3ccd7e9f..2943ff2483474aa58c17289564b1d74cb3514c59 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] v3.6.1
+ ... Reference: clause 7.5.3.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 7.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 7.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 7.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: Clause 7.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: Clause 7.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: Clause 7.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: Clause 7.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: Clause 7.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: Clause 7.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: Clause 7.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 7.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 7.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 7.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 7.5.3.3.3 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 7.5.3.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 7.5.3.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.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 7bdc6705dd76add2f8947b77d8ca353c2df57513..ad92531537f1559036a25897cf9532e5351a4904 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] v3.5.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.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 6411fcf1af4b45ceb3e80957bbef033fe133db01..9a09ca222f25efe64a66569a8d3928e7eecad121 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] v3.6.1
+ ... Reference: clause 7.5.4.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 7.5.4.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 7.5.4.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 7.5.4.3.3 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 7.5.4.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 7.5.4.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 7.5.4.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 7.5.4.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.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 6e3ed3d88250d7a636fd489037d130d8c7ba6640..7fd7c312a80a19cfe345893433e239366c27e36f 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] v3.6.1
+ ... Reference: clause 7.5.6.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 7.5.6.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 7.5.6.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 7.5.6.3.3 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 7.5.6.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 7.5.6.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.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 514d2719aa0146bdb6f1201d0cc874d4c9a4717e..808192e9d94d92a8e7f46c6dc15a3c3fa0750856 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] v3.6.1
+ ... Reference: clause 7.5.7.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 7.5.7.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 7.5.7.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.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 8af8869b66ff77f83c65608e5c52e190a3f0d0c0..b482d9983ce3ba29af4f66b4f45b64243c9cb04d 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] v3.6.1
+ ... Reference: clause 7.5.7.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 7.5.7.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 7.5.7.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.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 1abc5cae5050eacdb42a7308fe4f03dbc7d299dd..b46e5fcab1141b38570c841b0650c880e3da545c 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] v3.6.1
+ ... Reference: clause 7.5.5.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 7.5.5.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 7.5.5.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 7.5.5.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 7.5.5.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: Clause 7.5.5.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 7.5.5.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: Clause clause 7.5.5.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: Clause 7.5.5.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: Clause 7.5.5.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: Clause 7.5.5.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: Clause 7.5.5.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: Clause 7.5.5.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... RReference: clause 7.5.5.3.3 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 7.5.5.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -211,7 +211,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.5.5.3.5 - ETSI GS NFV-SOL 009 [7] v3.6.1
+ ... Reference: clause 7.5.5.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -223,7 +223,7 @@ POST Create a new Fault Management alarm subscription - Unprocessable entity
... Test title: POST Create a new fault management alarm subscription - Unprocessable entity
... 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] v3.6.1
+ ... Reference: clause 7.5.5.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.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 f62263c942bbeb152b37778d2108df0198479eda..efd72ad08dc7018bb870cde88651e1e73bf5e6e5 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] v3.5.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.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 7a9e38a2fd064d4f15d73580c0e4667ccd1c9fe3..8b0f24d294d7fd2a57155b1a0e4c4b00b9056d0c 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] v3.6.1
+ ... Reference: clause 8.5.6.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 8.5.6.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 8.5.6.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -49,7 +49,7 @@ 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 entity
... 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] v3.6.1
+ ... Reference: clause 8.5.6.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 8.5.6.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 8.5.6.3.3 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 8.5.6.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -98,7 +98,7 @@ 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] v3.6.1
+ ... Reference: clause 8.5.6.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
diff --git a/SOL009/NFVMANOLogManagement-API/IndividualLoggingJob.robot b/SOL009/NFVMANOLogManagement-API/IndividualLoggingJob.robot
index 94937003f8ba2d26ef14e901262bc6d86d780dff..16a366f691dc889ff2193f80edfb1e37527b49c1 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] v3.6.1
+ ... Reference: clause 8.5.4.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 8.5.4.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 8.5.4.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 8.5.4.3.3 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 6.5.4.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 8.5.4.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 8.5.4.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.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 754fa25ea355b1518ec00d8642ecf6c17f9a8708..c710c34baca85acc4ee4ea97ac1b88c1ec75f38b 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] v3.6.1
+ ... Reference: clause 8.5.5.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 8.5.5.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 8.5.5.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 8.5.5.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 8.5.5.3.3 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 8.5.5.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 8.5.5.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.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 5bb4e788fe02708ccabd31d62087deaa63e69535..c3a842ac87a5df006d31bb6a38515061f9330f59 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] v3.6.1
+ ... Reference: clause 8.5.8.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 8.5.8.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 8.5.8.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 8.5.8.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 8.5.8.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 8.5.8.3.3 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 8.5.8.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.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 e7bf4b1e5dcff14c4ce6e53e935e0d9570efdeec..eafc5be21c4a4e668ba9eec07f25d53c04c4f9d3 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] v3.6.1
+ ... Reference: clause 8.5.3.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 8.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 8.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 8.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 8.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 8.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 8.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 8.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 8.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 8.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 8.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 8.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 8.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 8.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 8.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 8.5.3.3.3 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 8.5.3.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 8.5.3.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.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 cd01c4081abe625aceef98493bdd333cabfe3c95..67181a745c35f8a63cf9c03e218d078d18938e23 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] v3.6.1
+ ... Reference: clause 8.5.9.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.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 c0b06e97cce12c2114a1b1d92234ce457d8a3823..4f797cd6be3a3f52fb8a409f16ab5ff39b0990f1 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] v3.6.1
+ ... Reference: clause 8.5.9.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.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 96575f7385f9f2bb0ecf3862ac35250d77c3269e..a513bf9b9baa2e2bbd039621e0971c5f651b2f50 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] v3.6.1
+ ... Reference: clause 8.5.7.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 8.5.7.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 8.5.7.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 8.5.7.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 8.5.7.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 8.5.7.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 8.5.7.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 8.5.7.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 8.5.7.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 8.5.7.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 8.5.7.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 8.5.7.3.3 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 8.5.7.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -186,7 +186,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 delete subscriptions
... Pre-conditions: none
- ... Reference: clause 8.5.7.3.5 - ETSI GS NFV-SOL 009 [7] v3.6.1
+ ... Reference: clause 8.5.7.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -198,7 +198,7 @@ POST Create new Subscription - Unprocessable entity
... Test title: POST Create new Subscription - Unprocessable entity
... 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] v3.6.1
+ ... Reference: clause 8.5.7.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.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/ApiVersion.robot b/SOL009/NFVMANOPerformanceManagement-API/ApiVersion.robot
index 493f316fa84bd71c00d618cbbd63f86a59bae22f..f3543a290f41734b7b99a3fbe52f388aa214c5e7 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] v3.5.1 v3.5.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.1 v3.5.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] v3.5.1 v3.5.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.1 v3.5.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] v3.5.1 v3.5.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.1 v3.5.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] v3.5.1 v3.5.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.1 v3.5.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] v3.5.1 v3.5.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1 v3.5.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] v3.5.1 v3.5.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.1 v3.5.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] v3.5.1 v3.5.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.1 v3.5.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] v3.5.1 v3.5.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.1 v3.5.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] v3.5.1 v3.5.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.1 v3.5.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] v3.5.1 v3.5.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1 v3.5.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 b84a4282ff077cfbc5dfa176a30e5ddd296fa67d..056cc8ccc22cbfce535aaafee2c5d1c9aefe5de8 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] v3.6.1
+ ... Reference: clause 6.5.4.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 6.5.4.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 6.5.4.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 6.5.4.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 6.5.4.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 6.5.4.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 6.5.4.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 6.5.4.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: PM Job resource is not modified.
@@ -109,7 +109,7 @@ PATCH Individual NFV-MANO Performance Job - Unprocessable entity
... Test title: PATCH Individual NFV-MANO Performance Job - Unprocessable entity
... 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] v3.6.1
+ ... Reference: clause 6.5.4.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: PM Job resource is not modified.
diff --git a/SOL009/NFVMANOPerformanceManagement-API/IndividualReport.robot b/SOL009/NFVMANOPerformanceManagement-API/IndividualReport.robot
index 4ab5b8937783c3d0bdf6600bb7bc5545d24fadcf..b122db873e1cabc4aca6b9a1b89bb0427c52bd28 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] v3.6.1
+ ... Reference: clause 6.5.5.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 6.5.5.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 6.5.5.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 6.5.5.3.3 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 6.5.5.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 6.5.5.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.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 10b68f44ae78f578e1276fcbb2d8eaac47e27b0e..83da2ff4e309b3e8ce4967d5b6c1410b86270b0d 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] v3.6.1
+ ... Reference: clause 6.5.7.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 6.5.7.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 6.5.7.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 6.5.7.3.3 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 6.5.7.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 6.5.7.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 6.5.7.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 6.5.7.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: Threshold resource is not modified.
@@ -108,7 +108,7 @@ PATCH Individual Threshold - Unprocessable entity
... Test title: PATCH Individual Threshold - Unprocessable entity
... 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] v3.6.1
+ ... Reference: clause 6.5.7.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: Threshold resource is not modified.
diff --git a/SOL009/NFVMANOPerformanceManagement-API/NotificationEndpoint.robot b/SOL009/NFVMANOPerformanceManagement-API/NotificationEndpoint.robot
index 77fa25a8327dc669e7ff100ff69649d8bacf0670..09835042d5b4fa1d7f74b1677c4fb2e8b93e023c 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] v3.6.1
+ ... Reference: clause 6.5.10.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 6.5.10.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.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 a6aec7e3da226fd844838445eab57e2bfd137818..98211c3f3120e7e0759501bb4c9b599ac95ce50e 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] v3.6.1
+ ... Reference: clause 6.5.10.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 6.5.10.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.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 7200463bfc392a8206f6b154d123fea582387b6d..ebb291870f395d156e6abcb8433fa3eff37f8c2d 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] v3.6.1
+ ... Reference: clause 6.5.3.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 6.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 6.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 6.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 6.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 6.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 6.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 6.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 6.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 6.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 6.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.8.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 6.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 6.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 6.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 6.5.3.3.3 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 6.5.3.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 6.5.3.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 6.5.3.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.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 8e876161533beb560dce5954c8596e3122e15fbe..d0b07cb04ffb885bc8272afa344e7ea1529d1666 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] v3.6.1
+ ... Reference: clause 6.5.6.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 6.5.6.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 6.5.6.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 6.5.6.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 6.5.6.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 6.5.6.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 6.5.6.3.3 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 6.5.6.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -112,7 +112,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 NFV-MANO Performance Thresholds
... Pre-conditions: none
- ... Reference: clause 6.5.6.3.5 - ETSI GS NFV-SOL 009 [7] v3.6.1
+ ... Reference: clause 6.5.6.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -125,7 +125,7 @@ POST Create new Performance Threshold - Unprocessable entity
... 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] v3.6.1
+ ... Reference: clause 6.5.6.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.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 3dbcc8b514b856009a42353c6d58db4c46f65543..52d5e7b5e8eb74becd81c1de15bc85dbe3eb6bec 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] v3.5.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.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] v3.5.1
+ ... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.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 4277976d6d2cf0768c5dc4edf252ddd892d1acf6..a094501817201c50f33dcfb26a08c03f45565897 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] v3.6.1
+ ... Reference: clause 5.5.12.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.12.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.12.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.12.3.3 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.12.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.12.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.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 048c79d5d97d83b67b6a97f48185708a2d63b27e..30f968022f43ab20478ed280b8ed99fdc59e422d 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] v3.6.1
+ ... Reference: clause 5.5.7.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.7.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.7.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.7.3.3 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.7.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.7.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.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 fec65a2f3bbc3d8dc62798189f1d075484f02da9..3b3086b040c313773db3db74ce1aabce143f7937 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] v3.6.1
+ ... Reference: clause 5.5.8.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.8.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.8.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.8.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.8.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.8.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.8.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.8.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.8.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.8.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.8.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.8.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.8.3.3 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.8.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.8.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.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 8030beae3620e895186df2f7ee699369178341ee..56c50789c9b59d3650280a7681f7baa8ecdb98a9 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] v3.6.1
+ ... Reference: clause 5.5.11.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.11.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.11.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.11.3.3 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.11.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.11.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.11.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.11.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.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 1a8bd721d0d980a2eb39b8109ca94bd01e4ad8d2..b084730e74e414b7cc9e939d2b82f6fabf7c6208 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] v3.6.1
+ ... Reference: clause 5.5.14.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.14.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.14.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.14.3.3 - ETSI GS NFV-SOL 009 [7] v4.3.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -62,7 +62,7 @@ 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] v3.6.1
+ ... Reference: clause 5.5.14.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: Peer Entity Resource is modified by the operation
@@ -75,7 +75,7 @@ PATCH Individual Peer Entity - Conflict
... 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] v3.6.1
+ ... Reference: clause 5.5.14.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.14.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.14.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.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 1c15c36b73319d0571585de913d9d0a48c8b9aa6..a60ab0d9eaf6bde2a3099509b1bffd0f2926a6c6 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] v3.6.1
+ ... Reference: clause 5.5.9.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.9.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.9.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.9.3.3 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.9.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.9.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.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 5e8eb662b2b67e4c33a67a60c445ae7712f1dd29..f406fad84bf4c81ee0dfa66f4f241a3775172973 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] v3.6.1
+ ... Reference: clause 5.5.5.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.5.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.5.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.5.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.5.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.5.3.3 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.5.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.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 6390f249a3708cd8fe8d8b2750132d8277412d5f..832156bdf9c4d40ec39509fdffcf086ac7315d0e 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] v3.6.1
+ ... Reference: clause 5.5.3.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.3.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.3.3.3 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.3.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.3.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.3.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.3.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.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 8a33126bb548dcd3a4e615128ebb757a337ac9e1..bd7c62ae2546399fb8ce2aab1d6966b82ceb2dcb 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] v3.6.1
+ ... Reference: clause 5.5.10.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.10.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.10.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.10.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.10.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.10.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.10.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.10.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.10.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.10.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.10.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.10.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.10.3.3 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.10.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.10.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.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 6ee2110c35e41ba1bcc9e07eaeece3cb3a91718e..b51c7d3964ee3b7fa94d9811c375a2f49996c762 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] v3.6.1
+ ... Reference: clause 5.5.6.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.6.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.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 78afcbce542839f74ca2ab969a8ad9a14d7ad9fd..592bf0c284438941ab0047808014c6b8a5f7550e 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] v3.6.1
+ ... Reference: clause 5.5.6.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.6.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.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 e95817368b7460aec629006b1a359dee696b2401..2a62dccfc85ca2e2199ac4a5bb07ac648b22f4c6 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] v3.6.1
+ ... Reference: clause 5.5.13.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.13.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.13.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.13.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.13.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.13.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.13.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.13.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.13.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.13.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.13.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.13.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.13.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.13.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.13.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.13.3.3 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.13.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.13.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.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 1e561b4549e254f5d051f7f1502352a174e1ff26..2d890a6dfd7c8efb5f3017e4ac36a47ac620dd54 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] v3.6.1
+ ... Reference: clause 5.5.4.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.4.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.4.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.4.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.4.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.4.3.2 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.4.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.4.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.4.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.4.3.3 - ETSI GS NFV-SOL 009 [7] v4.3.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] v3.6.1
+ ... Reference: clause 5.5.4.3.4 - ETSI GS NFV-SOL 009 [7] v4.3.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -166,7 +166,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 delete subscriptions
... Pre-conditions: none
- ... Reference: clause 5.5.4.3.5 - ETSI GS NFV-SOL 009 [7] v3.6.1
+ ... Reference: clause 5.5.4.3.5 - ETSI GS NFV-SOL 009 [7] v4.3.1
... Config ID: Config_prod_NFV-MANO
... Applicability: none
... Post-Conditions: none
@@ -178,7 +178,7 @@ POST Create a new subscription - Unprocessable Entity
... Test title: POST Create a new Subscription - Unprocessable Entity
... 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] v3.6.1
+ ... Reference: clause 5.5.4.3.1 - ETSI GS NFV-SOL 009 [7] v4.3.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 5ad4bca3a59e96ac8a57cf3a7b00c16ec0b7cebf..4e9bd8cbb5a1feab54d70de7bf4ff04f55d7a9d1 100644
--- a/SOL009/NFVManoConfigurationAndInformationManagement-API/schemas/ManoEntity.schema.json
+++ b/SOL009/NFVManoConfigurationAndInformationManagement-API/schemas/ManoEntity.schema.json
@@ -1,5 +1,5 @@
{
- "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.\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. \n",
"type": "object",
"required": ["id", "type", "name", "description", "provider", "softwareVersion", "manoConfigurableParams", "manoApplicationState", "_links"],
"properties": {
@@ -8,9 +8,9 @@
"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",
+ "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",
"type": "string",
- "enum": ["NFVO", "VNFM", "VIM", "WIM"]
+ "enum": ["NFVO", "VNFM", "VIM", "WIM", "CISM"]
},
"name": {
"description": "Human-readable name of the NFV-MANO functional entity.\nThis attribute can be modified with the PATCH method.\n",
@@ -28,6 +28,10 @@
"description": "A version.\n",
"type": "string"
},
+ "softwareInfo": {
+ "description": "This 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"
+ },
"manoEntityComponents": {
"description": "The deployed NFV-MANO functional entity components which realize the NFV-MANO functional entity. See note 5.\n",
"type": "array",
@@ -224,7 +228,7 @@
"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 [i.16] and all values for \"container-format\" as defined in ETSI GS NFV-SOL 006 [i.17].\n",
+ "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",
"type": "array",
"items": {
"type": "string"
@@ -338,6 +342,11 @@
}
}
},
+ "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"
+ }
+ },
"_links": {
"description": "Links to resources related to this resource.\n",
"type": "object",
diff --git a/SOL009/NFVManoConfigurationAndInformationManagement-API/schemas/PeerEntities.schema.json b/SOL009/NFVManoConfigurationAndInformationManagement-API/schemas/PeerEntities.schema.json
index 2e02794be901c90b4e6b2a85b720b014c98c1c3f..34582033f9db04cb526d2bf418b2c204f3d76c80 100644
--- a/SOL009/NFVManoConfigurationAndInformationManagement-API/schemas/PeerEntities.schema.json
+++ b/SOL009/NFVManoConfigurationAndInformationManagement-API/schemas/PeerEntities.schema.json
@@ -1,212 +1,166 @@
{
- "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",
- "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. - EM\t The peer functional entity is an EM. - OSS\t The peer functional entity is an OSS/BSS. - WIM The peer functional is a WIM.\n",
- "type": "string",
- "enum": [
- "NFVO",
- "VNFM",
- "VIM",
- "WIM",
- "EM",
- "OSS",
- "WIM"
- ]
- },
- "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",
- "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. - 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
- }
- }
- }
- }
- }
- }
- }
- }
- },
- "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"
- ]
- }
- }
- }
+ "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",
+ "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. - 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",
+ "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",
+ "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. - 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
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ },
+ "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"]
+ }
+ }
+ }
}
\ 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 67233fbbbe3e92ce03b5a02a04ba5722fdcdba56..c7b3a60d1f62eb532bf364575361d781187a4f65 100644
--- a/SOL009/NFVManoConfigurationAndInformationManagement-API/schemas/PeerEntity.schema.json
+++ b/SOL009/NFVManoConfigurationAndInformationManagement-API/schemas/PeerEntity.schema.json
@@ -1,209 +1,163 @@
{
- "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",
- "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. - EM\t The peer functional entity is an EM. - OSS\t The peer functional entity is an OSS/BSS. - WIM The peer functional is a WIM.\n",
- "type": "string",
- "enum": [
- "NFVO",
- "VNFM",
- "VIM",
- "WIM",
- "EM",
- "OSS",
- "WIM"
- ]
- },
- "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",
- "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. - 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
- }
- }
- }
- }
- }
- }
- }
- }
- },
- "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"
- ]
- }
- }
+ "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",
+ "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. - 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",
+ "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",
+ "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. - 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
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ },
+ "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"]
+ }
+ }
}
\ No newline at end of file