[datamodel-upd][SOL002][VNF-LCM][v5.2.1][6.3.5.x.x Test-IDs] Add attribute... (505bf4bf) · Commits · NFV - Network Functions Virtualisation / api-tests

SOL002/VNFLifecycleManagement-API/schemas/VnfSnapshotInfo.schema.json

+33 −4

Original line number	Diff line number	Diff line
		@@ -870,6 +870,13 @@
		"type": "string"
		}
		}
		},
		"fullyQualifiedDomainNames": {
		"description": "Fully qualified domain names that have been configured (statically or dynamically) and been associated to the CP.\n",
		"type": "array",
		"items": {
		"type": "string"
		}
		}
		}
		}
		@@ -1079,7 +1086,15 @@
		"type": "string"
		}
		}
		},
		"fullyQualifiedDomainNames": {
		"description": "Fully qualified domain names that have been configured (statically or dynamically) and been associated to the CP.\n",
		"type": "array",
		"items": {
		"type": "string"
		}
		}

		}
		}
		},
		@@ -1313,6 +1328,13 @@
		"type": "string"
		}
		}
		},
		"fullyQualifiedDomainNames": {
		"description": "Fully qualified domain names that have been configured (statically or dynamically) and been associated to the CP.\n",
		"type": "array",
		"items": {
		"type": "string"
		}
		}
		}
		}
		@@ -2373,6 +2395,13 @@
		"type": "string"
		}
		}
		},
		"fullyQualifiedDomainNames": {
		"description": "Fully qualified domain names that have been configured (statically or dynamically) and been associated to the CP.\n",
		"type": "array",
		"items": {
		"type": "string"
		}
		}
		}
		}

SOL002/VNFLifecycleManagement-API/schemas/VnfSnapshotsInfo.schema.json

+33 −4

Original line number	Diff line number	Diff line
		@@ -872,6 +872,13 @@
		"type": "string"
		}
		}
		},
		"fullyQualifiedDomainNames": {
		"description": "Fully qualified domain names that have been configured (statically or dynamically) and been associated to the CP.\n",
		"type": "array",
		"items": {
		"type": "string"
		}
		}
		}
		}
		@@ -1081,6 +1088,13 @@
		"type": "string"
		}
		}
		},
		"fullyQualifiedDomainNames": {
		"description": "Fully qualified domain names that have been configured (statically or dynamically) and been associated to the CP.\n",
		"type": "array",
		"items": {
		"type": "string"
		}
		}
		}
		}
		@@ -1315,7 +1329,15 @@
		"type": "string"
		}
		}
		},
		"fullyQualifiedDomainNames": {
		"description": "Fully qualified domain names that have been configured (statically or dynamically) and been associated to the CP.\n",
		"type": "array",
		"items": {
		"type": "string"
		}
		}

		}
		}
		},
		@@ -2375,6 +2397,13 @@
		"type": "string"
		}
		}
		},
		"fullyQualifiedDomainNames": {
		"description": "Fully qualified domain names that have been configured (statically or dynamically) and been associated to the CP.\n",
		"type": "array",
		"items": {
		"type": "string"
		}
		}
		}
		}

SOL002/VNFLifecycleManagement-API/schemas/vnfInstance.schema.json

+32 −4

Original line number	Diff line number	Diff line
		@@ -696,7 +696,7 @@
		]
		},
		"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",
		"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": [
		{
		@@ -816,6 +816,13 @@
		"type": "string"
		}
		}
		},
		"fullyQualifiedDomainNames": {
		"description": "Fully qualified domain names that have been configured (statically or dynamically) and been associated to the CP.\n",
		"type": "array",
		"items": {
		"type": "string"
		}
		}
		}
		}
		@@ -905,7 +912,7 @@
		]
		},
		"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",
		"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": [
		{
		@@ -1025,6 +1032,13 @@
		"type": "string"
		}
		}
		},
		"fullyQualifiedDomainNames": {
		"description": "Fully qualified domain names that have been configured (statically or dynamically) and been associated to the CP.\n",
		"type": "array",
		"items": {
		"type": "string"
		}
		}
		}
		}
		@@ -1139,7 +1153,7 @@
		]
		},
		"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",
		"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": [
		{
		@@ -1259,6 +1273,13 @@
		"type": "string"
		}
		}
		},
		"fullyQualifiedDomainNames": {
		"description": "Fully qualified domain names that have been configured (statically or dynamically) and been associated to the CP.\n",
		"type": "array",
		"items": {
		"type": "string"
		}
		}
		}
		}
		@@ -2199,7 +2220,7 @@
		]
		},
		"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",
		"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": [
		{
		@@ -2319,6 +2340,13 @@
		"type": "string"
		}
		}
		},
		"fullyQualifiedDomainNames": {
		"description": "Fully qualified domain names that have been configured (statically or dynamically) and been associated to the CP.\n",
		"type": "array",
		"items": {
		"type": "string"
		}
		}
		}
		}

SOL002/VNFLifecycleManagement-API/schemas/vnfInstances.schema.json

+31 −3

File changed.

Preview size limit exceeded, changes collapsed.