[datamodel-upd][SOL002][VNF-LCM][v5.3.1][6.3.5.x.x Test-IDs][NFVSOL(25)000166]... (f665c24a) · Commits · NFV - Network Functions Virtualisation / api-tests

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

+21 −0

Original line number	Diff line number	Diff line
		@@ -718,6 +718,27 @@
		"description": "A number defined in IETF RFC 8259.\n",
		"type": "number"
		}
		},
		"cpuPowerStateRequirements": {
		"description": "Requirements of virtual CPU power state configuration data for the virtual compute resource.\n",
		"type": "object",
		"required": [
		"cpuPowerStateManagementPolicy"
		],
		"properties": {
		"cpuPowerStateManagementPolicy": {
		"description": "Indicates the policy for CPU power state management. Permitted values:\n * STATIC\n * DYNAMIC\nIn case of \"STATIC\", the virtual CPU cores are requested to be allocated to logical CPU cores according to the cpuOperationalPowerStates attribute. In case of \"DYNAMIC\", the CPU power states of virtual CPU cores can be allocated to logical CPU cores whose power states can be adjusted dynamically depending on core utilization (see note 1).\n",
		"type": "string",
		"enum": [
		"STATIC",
		"DYNAMIC"
		]
		},
		"cpuOperationalPowerStates": {
		"description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of keyvalue pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 8259. In the following example, a list of key-value pairs with four keys (\"aString\", \"aNumber\", \"anArray\" and \"anObject\") is provided to illustrate that the values associated with different keys can be of different type.\n",
		"type": "object"
		}
		}
		}
		}
		},

+21 −0

Original line number	Diff line number	Diff line
		@@ -720,6 +720,27 @@
		"description": "A number defined in IETF RFC 8259.\n",
		"type": "number"
		}
		},
		"cpuPowerStateRequirements": {
		"description": "Requirements of virtual CPU power state configuration data for the virtual compute resource.\n",
		"type": "object",
		"required": [
		"cpuPowerStateManagementPolicy"
		],
		"properties": {
		"cpuPowerStateManagementPolicy": {
		"description": "Indicates the policy for CPU power state management. Permitted values:\n * STATIC\n * DYNAMIC\nIn case of \"STATIC\", the virtual CPU cores are requested to be allocated to logical CPU cores according to the cpuOperationalPowerStates attribute. In case of \"DYNAMIC\", the CPU power states of virtual CPU cores can be allocated to logical CPU cores whose power states can be adjusted dynamically depending on core utilization (see note 1).\n",
		"type": "string",
		"enum": [
		"STATIC",
		"DYNAMIC"
		]
		},
		"cpuOperationalPowerStates": {
		"description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of keyvalue pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 8259. In the following example, a list of key-value pairs with four keys (\"aString\", \"aNumber\", \"anArray\" and \"anObject\") is provided to illustrate that the values associated with different keys can be of different type.\n",
		"type": "object"
		}
		}
		}
		}
		},

+21 −0

Original line number	Diff line number	Diff line
		@@ -664,6 +664,27 @@
		"description": "A number defined in IETF RFC 8259.\n",
		"type": "number"
		}
		},
		"cpuPowerStateRequirements": {
		"description": "Requirements of virtual CPU power state configuration data for the virtual compute resource.\n",
		"type": "object",
		"required": [
		"cpuPowerStateManagementPolicy"
		],
		"properties": {
		"cpuPowerStateManagementPolicy": {
		"description": "Indicates the policy for CPU power state management. Permitted values:\n * STATIC\n * DYNAMIC\nIn case of \"STATIC\", the virtual CPU cores are requested to be allocated to logical CPU cores according to the cpuOperationalPowerStates attribute. In case of \"DYNAMIC\", the CPU power states of virtual CPU cores can be allocated to logical CPU cores whose power states can be adjusted dynamically depending on core utilization (see note 1).\n",
		"type": "string",
		"enum": [
		"STATIC",
		"DYNAMIC"
		]
		},
		"cpuOperationalPowerStates": {
		"description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of keyvalue pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 8259. In the following example, a list of key-value pairs with four keys (\"aString\", \"aNumber\", \"anArray\" and \"anObject\") is provided to illustrate that the values associated with different keys can be of different type.\n",
		"type": "object"
		}
		}
		}
		}
		},

+21 −0

Original line number	Diff line number	Diff line
		@@ -666,6 +666,27 @@
		"description": "A number defined in IETF RFC 8259.\n",
		"type": "number"
		}
		},
		"cpuPowerStateRequirements": {
		"description": "Requirements of virtual CPU power state configuration data for the virtual compute resource.\n",
		"type": "object",
		"required": [
		"cpuPowerStateManagementPolicy"
		],
		"properties": {
		"cpuPowerStateManagementPolicy": {
		"description": "Indicates the policy for CPU power state management. Permitted values:\n * STATIC\n * DYNAMIC\nIn case of \"STATIC\", the virtual CPU cores are requested to be allocated to logical CPU cores according to the cpuOperationalPowerStates attribute. In case of \"DYNAMIC\", the CPU power states of virtual CPU cores can be allocated to logical CPU cores whose power states can be adjusted dynamically depending on core utilization (see note 1).\n",
		"type": "string",
		"enum": [
		"STATIC",
		"DYNAMIC"
		]
		},
		"cpuOperationalPowerStates": {
		"description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of keyvalue pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 8259. In the following example, a list of key-value pairs with four keys (\"aString\", \"aNumber\", \"anArray\" and \"anObject\") is provided to illustrate that the values associated with different keys can be of different type.\n",
		"type": "object"
		}
		}
		}
		}
		},