update datamodel: VnfcConfigurationData as per clause 9.5.3.4 (519e60a7) · Commits · NFV - Network Functions Virtualisation / api-tests

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

+56 −0

Original line number	Diff line number	Diff line
		@@ -200,6 +200,62 @@
		}
		}
		},
		"certificateData": {
		"description": "Certificates data to be configured or modified into VNFC instance. Shall be present if delegation-mode is used. Otherwise it shall be absent.\n",
		"type": "array",
		"items": {
		"description": "This type provides input information related to subject of certificate.\nNOTE : Either set of ΓÇ£privatekeyΓÇ¥ and ΓÇ£certificateFileΓÇ¥ or ΓÇ£keystoreFileΓÇ¥ but not both shall be present.\n",
		"type": "object",
		"properties": {
		"privateKey": {
		"type": "string",
		"description": "Private key paired with the signed public key. VNFM shall generate both the private key and public key and set this attribute. See note.\n"
		},
		"certificateFile": {
		"type": "string",
		"description": "Signed certificate including the public key and certificate chain. See note.\n"
		},
		"keystoreFile": {
		"type": "string",
		"description": "Keystore which includes the private key, signed certificate, and certificate chain (e.g., pkcs#12, pfx). Credentials to read this file shall be provided to the VNF instance by outbound. See note.\n"
		},
		"certSubjectData": {
		"description": "This type provides input information related to subject of certificate.\n* NOTE: At least one overriding attributes shall be present, otherwise shall be absent.\n",
		"type": "object",
		"properties": {
		"commonName": {
		"description": "Information of certification target subject FQDN. See note.",
		"type": "string"
		},
		"organization": {
		"description": "Information of certification target subject Organization. See note.",
		"type": "string"
		},
		"country": {
		"description": "Information of certification target subject Country. See note.",
		"type": "string"
		},
		"state": {
		"description": "Information of certification target subject State. See note.",
		"type": "string"
		},
		"locality": {
		"description": "Information of certification target subject Locality. See note.",
		"type": "string"
		},
		"emailAddress": {
		"description": "Information of certification contact email address. See note.",
		"type": "string"
		}
		}
		},
		"certifiateProfileName": {
		"type": "string",
		"description": "Name of the certificate profile to be signed.\n"
		}
		}
		}
		},
		"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 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"

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

+56 −0

Original line number	Diff line number	Diff line
		@@ -191,6 +191,62 @@
		}
		}
		},
		"certificateData": {
		"description": "Certificates data to be configured or modified into VNFC instance. Shall be present if delegation-mode is used. Otherwise it shall be absent.\n",
		"type": "array",
		"items": {
		"description": "This type provides input information related to subject of certificate.\nNOTE : Either set of ΓÇ£privatekeyΓÇ¥ and ΓÇ£certificateFileΓÇ¥ or ΓÇ£keystoreFileΓÇ¥ but not both shall be present.\n",
		"type": "object",
		"properties": {
		"privateKey": {
		"type": "string",
		"description": "Private key paired with the signed public key. VNFM shall generate both the private key and public key and set this attribute. See note.\n"
		},
		"certificateFile": {
		"type": "string",
		"description": "Signed certificate including the public key and certificate chain. See note.\n"
		},
		"keystoreFile": {
		"type": "string",
		"description": "Keystore which includes the private key, signed certificate, and certificate chain (e.g., pkcs#12, pfx). Credentials to read this file shall be provided to the VNF instance by outbound. See note.\n"
		},
		"certSubjectData": {
		"description": "This type provides input information related to subject of certificate.\n* NOTE: At least one overriding attributes shall be present, otherwise shall be absent.\n",
		"type": "object",
		"properties": {
		"commonName": {
		"description": "Information of certification target subject FQDN. See note.",
		"type": "string"
		},
		"organization": {
		"description": "Information of certification target subject Organization. See note.",
		"type": "string"
		},
		"country": {
		"description": "Information of certification target subject Country. See note.",
		"type": "string"
		},
		"state": {
		"description": "Information of certification target subject State. See note.",
		"type": "string"
		},
		"locality": {
		"description": "Information of certification target subject Locality. See note.",
		"type": "string"
		},
		"emailAddress": {
		"description": "Information of certification contact email address. See note.",
		"type": "string"
		}
		}
		},
		"certifiateProfileName": {
		"type": "string",
		"description": "Name of the certificate profile to be signed.\n"
		}
		}
		}
		},
		"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 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"