remove mojibake special characters from response bodies (673a01e3) · Commits · NFV - Network Functions Virtualisation / api-tests

interconnectedTestCases/SOL003/schemas/Subscription.schema.json

+1 −1

Original line number	Diff line number	Diff line
		@@ -128,7 +128,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": "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. SELECT_DEPL_MODS \| Represents the ΓÇ£Select VNF deployable modulesΓÇ¥ 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. SELECT_DEPL_MODS \| Represents the \"Select VNF deployable modules\" LCM operation\n",
		"type": "string",
		"enum": [
		"INSTANTIATE",

interconnectedTestCases/SOL003/schemas/VnfLcmOpOccs.schema.json

+5 −5

Original line number	Diff line number	Diff line
		@@ -58,7 +58,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.\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. SELECT_DEPL_MODS \| Represents the ΓÇ£Select VNF deployable modulesΓÇ¥ 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. SELECT_DEPL_MODS \| Represents the \"Select VNF deployable modules\" LCM operation\n",
		"type": "string",
		"enum": [
		"INSTANTIATE",
		@@ -765,7 +765,7 @@
		"description": "Map of instance data that need to be configured on the CP instances created from the respective CPD. The key of the map which identifies the individual VnfExtCpConfig entries is of type \"IdentifierInVnf\" and is managed by the NFVO. The entries shall be applied by the VNFM according to the rules of JSON Merge Patch (see IETF RFC 7396). See notes 2, 3, 4, 5, 6.\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) Void.\n 2) The \"netAttDefResourceId\" attribute shall be present and the \"cpProtocolData\" attribute may be present for\n a to-be-created external CP instance or an existing external CP instance.\n* NOTE 3: Cardinality greater than 1 is only applicable for specific cases where more than one network attachment\n definition resource is needed to fulfil the connectivity requirements of the external CP, e.g. to build a link\n redundant mated pair in SR-IOV cases. When more than one netAttDefResourceId is indicated, all shall belong\n to the same namespace as defined by the corresponding \"containerNamespace\" attribute in the \"resourceHandle\" a attribute in the\n \"NetAttDefResourceData\".\n* NOTE 4: Either linkPortId or netAttDefResourceId may be included, but not both.\n",
		"description": "This type represents an externally provided link port, or a network attachment definition resource of secondary container cluster network, or network address information per instance of an external connection point. In the case of VM-based deployment of the VNFC exposing the external CP:\n 1. In case a link port is provided, the VNFM shall use that link port when connecting the external CP to the\n external VL.\n 2. In case a link port is not provided, the VNFM shall create a link port on the external VL and use that link port\n to connect the external CP to the external VL.\nIn the case of container-based deployment of the VNFC exposing the external CP, the VNFM shall use the network attachment definition resource of secondary container cluster network when connecting the CP to the external VL.\n* NOTE 1: The following conditions apply to the attributes \"linkPortId\" and \"cpProtocolData\" for an external CP\n instance connected or to be connected to a virtual network not categorized as secondary container cluster network:\n 1) Void.\n 2) At least one of the \"linkPortId\" and \"cpProtocolData\" attributes shall be present for an external CP instance\n representing a subport that is to be created, or an external CP instance that is to be created by creating the\n corresponding VNFC or VNF instance during the current or a subsequent LCM operation, or for an existing\n external CP instance that is to be re-configured or added to a particular external virtual link.\n 3) If the \"linkPortId\" attribute is absent, the VNFM shall create a link port.\n 4) If the \"cpProtocolData\" attribute is absent, the \"linkPortId\" attribute shall be provided referencing a\n precreated link port, and the VNFM can use means outside the scope of the present document to obtain the\n pre-configured address information for the connection point from the resource representing the link port.\n 5) If both \"cpProtocolData\" and \"linkportId\" are provided, the NFVO shall ensure that the\n cpProtocolData can be used with the pre-created link port referenced by \"linkPortId\".\n\n* NOTE 2: The following conditions apply to the attributes \"netAttDefResourceId\" and \"cpProtocolData\" for an external CP\n instance connected or to be connected to a secondary container cluster network:\n 1) Void.\n 2) The \"netAttDefResourceId\" attribute shall be present and the \"cpProtocolData\" attribute may be present for\n a to-be-created external CP instance or an existing external CP instance.\n* NOTE 3: Cardinality greater than 1 is only applicable for specific cases where more than one network attachment\n definition resource is needed to fulfil the connectivity requirements of the external CP, e.g. to build a link\n redundant mated pair in SR-IOV cases. When more than one netAttDefResourceId is indicated, all shall belong\n to the same namespace as defined by the corresponding \"containerNamespace\" attribute in the \"resourceHandle\" a attribute in the\n \"NetAttDefResourceData\".\n* NOTE 4: Either linkPortId or netAttDefResourceId may be included, but not both.\n",
		"anyOf": [
		{
		"required": ["linkPortId"]
		@@ -792,7 +792,7 @@
		"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",
		"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",
		@@ -1193,7 +1193,7 @@
		"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",
		"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",
		@@ -1230,7 +1230,7 @@
		"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",
		"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",

interconnectedTestCases/SOL003/schemas/vnfInstance.schema.json

+6 −6

File changed.

Preview size limit exceeded, changes collapsed.

interconnectedTestCases/SOL003/schemas/vnfInstances.schema.json

+7 −7

File changed.

Preview size limit exceeded, changes collapsed.