update test cases of VNFPerformanceManagement as per SOL 002 version 5.1.1 (8b020ec2) · Commits · NFV - Network Functions Virtualisation / api-tests

SOL002/VNFPerformanceManagement-API/schemas/PmJob.schema.json

+48 −2

Original line number	Diff line number	Diff line
		@@ -105,8 +105,54 @@
		"fileSize": {
		"description": "The size of the report file in bytes, if known.\n",
		"type": "integer",
		"minimum": 0,
		"maximum": 1024
		"minimum": 0
		}
		}
		},
		"pmJobConnection": {
		"description": "An access information and interface information of PM job to monitor the PM of VNF instance by the VNFM. This can include for instance certain interface endpoint URI together with necessary credentials to access it.\n",
		"type": "array",
		"items": {
		"description": "The MonitoringConnection shall follow the indications. * NOTE:\tThe VNFM can be made aware of monitoring connection information, including their identifiers to \n be used by configuration means outside the scope of the present document (e.g. using relevant NFV-MANO management \n APIs as defined in ETSI GS NFV-SOL 009). \n",
		"type": "object",
		"required": [
		"id",
		"monitoringType"
		],
		"properties": {
		"id": {
		"description": "An identifier with the intention of being globally unique.\n",
		"type": "string"
		},
		"monitoringType": {
		"description": "Type of monitoring way. VALUES: \n ΓÇó\tVIM_CISM\n ΓÇó\tEXTERNAL\n ΓÇó\tPAAS\n",
		"type": "string",
		"enum": [
		"VIM_CISM",
		"EXTERNAL",
		"PAAS"
		]
		},
		"vimId": {
		"description": "An identifier with the intention of being globally unique.\n",
		"type": "string"
		},
		"paasServiceId": {
		"description": "An identifier with the intention of being globally unique.\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": "A string defined in IETF RFC 8259.\n",
		"type": "string"
		}
		}
		}
		},

SOL002/VNFPerformanceManagement-API/schemas/PmJobs.schema.json

+48 −2

Original line number	Diff line number	Diff line
		@@ -107,8 +107,54 @@
		"fileSize": {
		"description": "The size of the report file in bytes, if known.\n",
		"type": "integer",
		"minimum": 0,
		"maximum": 1024
		"minimum": 0
		}
		}
		},
		"pmJobConnection": {
		"description": "An access information and interface information of PM job to monitor the PM of VNF instance by the VNFM. This can include for instance certain interface endpoint URI together with necessary credentials to access it.\n",
		"type": "array",
		"items": {
		"description": "The MonitoringConnection shall follow the indications. * NOTE:\tThe VNFM can be made aware of monitoring connection information, including their identifiers to \n be used by configuration means outside the scope of the present document (e.g. using relevant NFV-MANO management \n APIs as defined in ETSI GS NFV-SOL 009). \n",
		"type": "object",
		"required": [
		"id",
		"monitoringType"
		],
		"properties": {
		"id": {
		"description": "An identifier with the intention of being globally unique.\n",
		"type": "string"
		},
		"monitoringType": {
		"description": "Type of monitoring way. VALUES: \n ΓÇó\tVIM_CISM\n ΓÇó\tEXTERNAL\n ΓÇó\tPAAS\n",
		"type": "string",
		"enum": [
		"VIM_CISM",
		"EXTERNAL",
		"PAAS"
		]
		},
		"vimId": {
		"description": "An identifier with the intention of being globally unique.\n",
		"type": "string"
		},
		"paasServiceId": {
		"description": "An identifier with the intention of being globally unique.\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": "A string defined in IETF RFC 8259.\n",
		"type": "string"
		}
		}
		}
		},