implementation of deltas between 2.7.1 and 3.3.1 (035ce244) · Commits · NFV - Network Functions Virtualisation / api-tests

SOL002/VNFConfiguration-API/schemas/vnfConfigModifications.schema.json

+124 −52

Original line number	Original line	Diff line number	Diff line
	{		{
	"description": "This type represents request parameters for the \"Set Configuration\" operation. * NOTE 1: At least one of \"vnfConfigurationData\" and \"vnfcConfigurationData\"\n shall be present.\n * NOTE 2: The VnfcConfiguration data type can only be used to modify the configuration\n of existing VNFC instances.\n",		"description": "This type represents request parameters for the \"Set Configuration\" operation.\n * NOTE 1: At least one of \"vnfConfigurationData\" and \"vnfcConfigurationData\"\n shall be present.\n * NOTE 2: The VnfcConfiguration data type can only be used to modify the configuration\n of existing VNFC instances.\n",
	"type": "object",		"type": "object",
			"anyOf": [
			{
			"required": [
			"vnfConfigurationData"
			]
			},
			{
			"required": [
			"vnfcConfigurationData"
			]
			}
			],
	"properties": {		"properties": {
	"vnfConfigurationData": {		"vnfConfigurationData": {
	"description": "This type represents configuration parameters of a VNF instance.\n",		"description": "This type represents configuration parameters of a VNF instance.\n",
	"type": "object",		"type": "object",
	"properties": {		"properties": {
	"extCpConfig": {		"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",		"description": "This type represents configuration parameters of a CP instance.\n",
	"type": "object",		"type": "object",
	"required": [		"required": [
	@@ -27,8 +42,32 @@
	"description": "Network address and port assigned to the CP.\n",		"description": "Network address and port assigned to the CP.\n",
	"type": "array",		"type": "array",
	"items": {		"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",		"type": "object",
			"oneOf": [
			{
			"required": [
			"address"
			]
			},
			{
			"required": [
			"useDynamicAddress"
			]
			}
			],
			"anyOf": [
			{
			"required": [
			"macAddress"
			]
			},
			{
			"required": [
			"ipAddress"
			]
			}
			],
	"properties": {		"properties": {
	"address": {		"address": {
	"description": "Network address that has been configured on the CP. See NOTE 1.\n",		"description": "Network address that has been configured on the CP. See NOTE 1.\n",
	@@ -58,6 +97,7 @@
	}		}
	}		}
	}		}
			}
	},		},
	"dhcpServer": {		"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",		"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
	@@ -65,13 +105,13 @@
	"format": "IP"		"format": "IP"
	},		},
	"vnfSpecificData": {		"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"		"type": "object"
	}		}
	}		}
	},		},
	"vnfcConfigurationData": {		"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: 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",		"type": "array",
	"items": {		"items": {
	"description": "This type represents configuration parameters of a VNFC instance.\n",		"description": "This type represents configuration parameters of a VNFC instance.\n",
	@@ -108,8 +148,32 @@
	"description": "Network address and port assigned to the CP.\n",		"description": "Network address and port assigned to the CP.\n",
	"type": "array",		"type": "array",
	"items": {		"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",		"type": "object",
			"oneOf": [
			{
			"required": [
			"address"
			]
			},
			{
			"required": [
			"useDynamicAddress"
			]
			}
			],
			"anyOf": [
			{
			"required": [
			"macAddress"
			]
			},
			{
			"required": [
			"ipAddress"
			]
			}
			],
	"properties": {		"properties": {
	"address": {		"address": {
	"description": "Network address that has been configured on the CP. See NOTE 1.\n",		"description": "Network address that has been configured on the CP. See NOTE 1.\n",
	@@ -147,11 +211,19 @@
	"format": "IP"		"format": "IP"
	},		},
	"vnfcSpecificData": {		"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"		"type": "object"
	}		}
	}		}
	}		}
			},
			"vnfcConfigurationDataDeleteIds": {
			"description": "List of identifiers entries to be deleted from the 'vnfcConfigurationData\" attribute array to be used as \"deleteIdList\" as defined below this table.\n",
			"type": "array",
			"items": {
			"description": "An identifier with the intention of being globally unique.\n",
			"type": "string"
			}
	}		}
	}		}
	}		}
			No newline at end of file

Admin message