{
	"description": "This type represents a VNF instance. It shall comply with the provisions defined in table 5.5.2.2-1.\nNOTE:\tClause B.3.2 provides examples illustrating the relationship among the different run-time \n      information elements (CP, VL and link ports) used to represent the connectivity of a VNF.\n\nNOTE 1:\tModifying the value of this attribute shall not be performed when conflicts exist between \n        the previous and the newly referred VNF package, i.e. when the new VNFD is changed with \n        respect to the previous VNFD in other aspects than merely referencing to other VNF software \n        images. In order to avoid misalignment of the VnfInstance with the current VNF's on-boarded \n        VNF Package, the values of attributes in the VnfInstance that have corresponding attributes \n        in the VNFD shall be kept in sync with the values in the VNFD.\nNOTE 2:\tETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on TOSCA specifications. NOTE 3:\tVNF configurable properties are sometimes also referred to as configuration parameters applicable \n        to a VNF. Some of these are set prior to instantiation and cannot be modified if the VNF is instantiated, \n        some are set prior to instantiation (are part of initial configuration) and can be modified later, \n        and others can be set only after instantiation. The applicability of certain configuration may \n        depend on the VNF and the required operation of the VNF at a certain point in time.\nNOTE 4:\tUpon creation of the VnfInstance structure, the VNFM shall create and initialize all child attributes \n        of \"vnfConfigurableProperties\", \"metadata\" and \"extensions\" that were declared in the VNFD with a defined \n        initial value. The defined initial values can be declared in the VNFD, and/or, in case of \"metadata\", \n        obtained from the \"CreateVnfRequest\" structure. Child attributes of \"vnfConfigurableProperties\", \n        \"metadata\" and \"extensions\" that have no defined initial value shall not be created, in order to be \n        consistent with the semantics of the JSON Merge Patch method (see IETF RFC 7396) that interprets null \n        values as deletion request.\nNOTE 5:\tIt is possible to have several ExtManagedVirtualLinkInfo for the same VNF internal VL in case of a \n        multi-site VNF spanning several VIMs. The set of ExtManagedVirtualLinkInfo corresponding to the same \n        VNF internal VL shall indicate so by referencing to the same VnfVirtualLinkDesc and externally-managed \n        multi-site VL instance (refer to clause 5.5.3.3).\nNOTE 6:\tEven though externally-managed internal VLs are also used for VNF-internal connectivity, they shall \n        not be listed in the \"vnfVirtualLinkResourceInfo\" attribute as this would be redundant.\n",
	"type": "object",
	"required": ["id", "vnfdId", "vnfProvider", "vnfProductName", "vnfSoftwareVersion", "vnfdVersion", "instantiationState"],
	"properties": {
		"id": {
			"description": "An identifier with the intention of being globally unique.\n",
			"type": "string"
		},
		"vnfInstanceName": {
			"description": "Name of the VNF instance. This attribute can be modified with the PATCH method.\n",
			"type": "string"
		},
		"vnfInstanceDescription": {
			"description": "Human-readable description of the VNF instance. This attribute can be modified with the PATCH method.\n",
			"type": "string"
		},
		"vnfdId": {
			"description": "An identifier with the intention of being globally unique.\n",
			"type": "string"
		},
		"vnfProvider": {
			"description": "Provider of the VNF and the VNFD. The value is copied from the VNFD.\n",
			"type": "string"
		},
		"vnfProductName": {
			"description": "Name to identify the VNF Product. The value is copied from the VNFD.\n",
			"type": "string"
		},
		"vnfSoftwareVersion": {
			"description": "A version.\n",
			"type": "string"
		},
		"vnfdVersion": {
			"description": "A version.\n",
			"type": "string"
		},
		"vnfConfigurableProperties": {
			"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"
		},
		"vimConnectionInfo": {
			"description": "Information about VIM connections to be used for managing the resources for the VNF instance. The keys of the map, each of which identifies information about a particular VIM connection, are managed by the NFVO and referenced from other data structures via the \"vimConnectionId\" attribute. This attribute shall only be supported and present if VNF-related resource management in direct mode is pplicable. This attribute can be modified with the PATCH method.\n",
			"type": "object",
			"additionalProperties": {
				"description": "This type represents parameters to connect to a VIM for managing the resources of a VNF instance. * NOTE 1:\tIf applicable, this attribute also provides information about the resourceGroupIds\n          that are accessible using a particular set of credentials. See definition of\n          \"resourceGroupId\" in clause 9.5.3.3.\n* NOTE 2:\tOnce the connectivity between VNFM and VIM is provided through a secure connection over\n          HTTP Secure (HTTP over SSL/TLS), and the connection might also be established through a VPN\n          (for example TLS-based VPN tunnelling) for site-to-site connection, the \"accessInfo\" JSON data\n          structure, and the sensitive data related information (\"username\"/\"password\" as required properties\n          for authentication purpose), will be transmitted as plain text through a TLS tunnel without additional\n          encoding/encryption before transmitting it, making the sensitive data visible to the endpoint.\n          The base64 encoded certificates are only used by the VNFM to verify the authenticity of the\n          interface endpoint of the VIM.\n",
				"type": "object",
				"required": ["vimType"],
				"properties": {
					"vimId": {
						"description": "An identifier with the intention of being globally unique.\n",
						"type": "string"
					},
					"vimType": {
						"description": "Discriminator for the different types of the VIM information. The value of this attribute determines the structure of the \"interfaceInfo\" and \"accessInfo\" attributes, based on the type of the VIM. The set of permitted values is expected to change over time as new types or versions of VIMs become available. The ETSI NFV registry of VIM-related information provides access to information about VimConnectionInfo definitions for various VIM types. The structure of the registry is defined in Annex C of SOL003.\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": "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"
					}
				}
			}
		},
		"instantiationState": {
			"description": "The instantiation state of the VNF.\n",
			"type": "string",
			"enum": ["NOT_INSTANTIATED", "INSTANTIATED"]
		},
		"instantiatedVnfInfo": {
			"description": "Information specific to an instantiated VNF instance. This attribute shall be present if the instantiateState attribute value is INSTANTIATED.\n",
			"type": "object",
			"required": ["flavourId", "vnfState"],
			"properties": {
				"flavourId": {
					"description": "An identifier that is unique within a VNF descriptor.\n",
					"type": "string"
				},
				"vnfState": {
					"description": "STARTED: The VNF instance is up and running. STOPPED: The VNF instance has been shut down.\n",
					"type": "string",
					"enum": ["STARTED", "STOPPED"]
				},
				"scaleStatus": {
					"description": "Scale status of the VNF, one entry per aspect. Represents for every scaling aspect how \"big\" the VNF has been scaled w.r.t. that aspect. This attribute shall be present if the VNF supports scaling. See clause B.2 for an explanation of VNF scaling.\n",
					"type": "array",
					"items": {
						"required": ["aspectId", "scaleLevel"],
						"type": "object",
						"properties": {
							"aspectId": {
								"description": "An identifier that is unique within a VNF descriptor.\n",
								"type": "string"
							},
							"vnfdId": {
								"description": "An identifier with the intention of being globally unique.\n",
								"type": "string"
							},
							"scaleLevel": {
								"description": "Indicates the scale level. The minimum value shall be 0 and the maximum value shall be <= maxScaleLevel as described in the VNFD.\n",
								"type": "integer"
							}
						}
					}
				},
				"maxScaleLevels": {
					"description": "Maximum allowed scale levels of the VNF, one entry per aspect. This attribute shall be present if the VNF supports scaling.\n",
					"type": "array",
					"items": {
						"required": ["aspectId", "scaleLevel"],
						"type": "object",
						"properties": {
							"aspectId": {
								"description": "An identifier that is unique within a VNF descriptor.\n",
								"type": "string"
							},
							"vnfdId": {
								"description": "An identifier with the intention of being globally unique.\n",
								"type": "string"
							},
							"scaleLevel": {
								"description": "Indicates the scale level. The minimum value shall be 0 and the maximum value shall be <= maxScaleLevel as described in the VNFD.\n",
								"type": "integer"
							}
						}
					}
				},
				"extCpInfo": {
					"description": "Information about the external CPs exposed by the VNF instance. When trunking is enabled, the list of entries includes both, external CPs corresponding to parent ports of a trunk, and external CPs associated to sub-ports of a trunk.\n",
					"type": "array",
					"minItems": 1,
					"items": {
						"description": "This type represents information about an external CP of a VNF.  It shall comply with the provisions defined in table 5.5.3.17 1.\nNOTE 1:\tThe attributes \"associatedVnfcCpId\", \"associatedVipCpId\" and \"associatedVnfVirtualLinkId\" \n        are mutually exclusive. Exactly one shall be present.\nNOTE 2:\tAn external CP instance is not associated to a link port in the cases indicated for the \n        “extLinkPorts” attribute in clause 4.4.1.11.\n",
						"type": "object",
						"required": ["id", "cpdId", "cpConfigId", "cpProtocolInfo"],
						"oneOf": [{
							"required": ["associatedVnfcCpId"]
						}, {
							"required": ["associatedVipCpId"]
						}, {
							"required": ["associatedVnfVirtualLinkId"]
						}],
						"properties": {
							"id": {
								"description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
								"type": "string"
							},
							"cpdId": {
								"description": "An identifier that is unique within a VNF descriptor.\n",
								"type": "string"
							},
							"cpConfigId": {
								"description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
								"type": "string"
							},
							"vnfdId": {
								"description": "An identifier with the intention of being globally unique.\n",
								"type": "string"
							},
							"cpProtocolInfo": {
								"description": "Network protocol information for this CP.\n",
								"type": "array",
								"items": {
									"description": "This type describes the protocol layer(s) that a CP uses together with protocol-related information, like addresses.  It shall comply with the provisions defined in table 5.5.3.9b-1.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the \n      present document in a backwards-compatible way. In the current version of the present document, only IP over \n      Ethernet is supported.\n",
									"type": "object",
									"required": ["layerProtocol"],
									"properties": {
										"layerProtocol": {
											"description": "The identifier of layer(s) and protocol(s) associated to the network address information.\nPermitted values: IP_OVER_ETHERNET See note.\n",
											"type": "string",
											"enum": ["IP_OVER_ETHERNET"]
										},
										"ipOverEthernet": {
											"description": "This type represents information about a network address that has been assigned.  It shall comply with the provisions defined in table 5.5.3.10-1.\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": [{
												"required": ["macAddress"]
											}, {
												"required": ["ipAddresses"]
											}],
											"oneOf": [{
												"required": ["addresses"]
											}, {
												"required": ["addressRange"]
											}],
											"properties": {
												"macAddress": {
													"description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
													"type": "string",
													"format": "MAC"
												},
												"segmentationId": {
													"description": "Identification of the network segment to which the Cp instance connects to. See notes 3 and 4.\n",
													"type": "string"
												},
												"ipAddresses": {
													"description": "Addresses assigned to the CP instance. Each entry represents IP addresses assigned by fixed or  dynamic IP address assignment per subnet. See note 1.\n",
													"type": "array",
													"items": {
														"type": "object",
														"required": ["type"],
														"properties": {
															"type": {
																"description": "The type of the IP addresses. Permitted values: IPV4, IPV6.\n",
																"type": "string",
																"enum": ["IPV4", "IPV6"]
															},
															"addresses": {
																"description": "Fixed addresses assigned (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
																"type": "array",
																"items": {
																	"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
																	"type": "string",
																	"format": "IP"
																}
															},
															"isDynamic": {
																"description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
																"type": "boolean"
															},
															"addressRange": {
																"description": "An IP address range used, e.g. in case of egress connections. See note 2.\n",
																"type": "object",
																"required": ["minAddress", "maxAddress"],
																"properties": {
																	"minAddress": {
																		"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
																		"type": "string",
																		"format": "IP"
																	},
																	"maxAddress": {
																		"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
																		"type": "string",
																		"format": "IP"
																	}
																}
															},
															"subnetId": {
																"description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
																"type": "string"
															}
														}
													}
												}
											}
										}
									}
								}
							},
							"extLinkPortId": {
								"description": "An identifier with the intention of being globally unique.\n",
								"type": "string"
							},
							"metadata": {
								"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"
							},
							"associatedVnfcCpId": {
								"description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
								"type": "string"
							},
							"associatedVipCpId": {
								"description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
								"type": "string"
							},
							"associatedVnfVirtualLinkId": {
								"description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
								"type": "string"
							}
						}
					}
				},
				"vipCpInfo": {
					"description": "VIP CPs that are part of the VNF instance. Shall be present when that particular VIP CP of the VNFC instance is associated to an external CP of the VNF instance. May be present otherwise.\n",
					"type": "array",
					"minItems": 1,
					"items": {
						"description": "This type provides information related to virtual IP (VIP) CP. It shall comply with the provisions defined in table 5.5.3.28-1.\nNOTE:\tIt is possible that there is no associated VnfcCp because the VIP CP is available but not associated yet.\n",
						"type": "object",
						"required": ["cpInstanceId", "cpdId"],
						"properties": {
							"cpInstanceId": {
								"description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
								"type": "string"
							},
							"cpdId": {
								"description": "An identifier that is unique within a VNF descriptor.\n",
								"type": "string"
							},
							"vnfExtCpId": {
								"description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
								"type": "string"
							},
							"cpProtocolInfo": {
								"description": "Protocol information for this CP. There shall be one cpProtocolInfo for layer 3. There may be one cpProtocolInfo for layer 2.\n",
								"type": "array",
								"items": {
									"description": "This type describes the protocol layer(s) that a CP uses together with protocol-related information, like addresses.  It shall comply with the provisions defined in table 5.5.3.9b-1.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the \n      present document in a backwards-compatible way. In the current version of the present document, only IP over \n      Ethernet is supported.\n",
									"type": "object",
									"required": ["layerProtocol"],
									"properties": {
										"layerProtocol": {
											"description": "The identifier of layer(s) and protocol(s) associated to the network address information.\nPermitted values: IP_OVER_ETHERNET See note.\n",
											"type": "string",
											"enum": ["IP_OVER_ETHERNET"]
										},
										"ipOverEthernet": {
											"description": "This type represents information about a network address that has been assigned.  It shall comply with the provisions defined in table 5.5.3.10-1.\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": [{
												"required": ["macAddress"]
											}, {
												"required": ["ipAddresses"]
											}],
											"oneOf": [{
												"required": ["addresses"]
											}, {
												"required": ["addressRange"]
											}],
											"properties": {
												"macAddress": {
													"description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
													"type": "string",
													"format": "MAC"
												},
												"segmentationId": {
													"description": "Identification of the network segment to which the Cp instance connects to. See notes 3 and 4.\n",
													"type": "string"
												},
												"ipAddresses": {
													"description": "Addresses assigned to the CP instance. Each entry represents IP addresses assigned by fixed or  dynamic IP address assignment per subnet. See note 1.\n",
													"type": "array",
													"items": {
														"type": "object",
														"required": ["type"],
														"properties": {
															"type": {
																"description": "The type of the IP addresses. Permitted values: IPV4, IPV6.\n",
																"type": "string",
																"enum": ["IPV4", "IPV6"]
															},
															"addresses": {
																"description": "Fixed addresses assigned (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
																"type": "array",
																"items": {
																	"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
																	"type": "string",
																	"format": "IP"
																}
															},
															"isDynamic": {
																"description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
																"type": "boolean"
															},
															"addressRange": {
																"description": "An IP address range used, e.g. in case of egress connections. See note 2.\n",
																"type": "object",
																"required": ["minAddress", "maxAddress"],
																"properties": {
																	"minAddress": {
																		"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
																		"type": "string",
																		"format": "IP"
																	},
																	"maxAddress": {
																		"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
																		"type": "string",
																		"format": "IP"
																	}
																}
															},
															"subnetId": {
																"description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
																"type": "string"
															}
														}
													}
												}
											}
										}
									}
								}
							},
							"associatedVnfcCpIds": {
								"description": "Identifiers of the VnfcCps that share the virtual IP addresse allocated to the VIP CP instance. See note.\n",
								"type": "array",
								"items": {
									"description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
									"type": "string"
								}
							},
							"vnfLinkPortId": {
								"description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
								"type": "string"
							},
							"metadata": {
								"description": "Metadata about this VIP CP.\n",
								"type": "array",
								"items": {
									"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"
								}
							}
						}
					}
				},
				"extVirtualLinkInfo": {
					"description": "Information about the external VLs the VNF instance is connected to.\n",
					"type": "array",
					"items": {
						"description": "This type represents information about an external VL. It shall comply with the provisions defined in table 5.5.3.2-1.\nNOTE:\tThis attribute reflects the current configuration information that has resulted from merging into this attribute \n      the \"VnfExtCpData\" information which was passed as part of the \"ExtVirtualLinkData\" structure in the input of the \n      most recent VNF LCM operation such as \"InstantiateVnfRequest\", \"ChangeExtVnfConnectivityRequest\", \"ChangeVnfFlavourRequest\" \n      or \"ChangeCurrentVnfPkgRequest\", or in the Grant response. If applying such change results in an empty list of \n      \"currentVnfExtCpData\" structure instances, the affected instance of \"ExtVirtualLinkInfo\" shall be removed from its \n      parent data structure.\n",
						"type": "object",
						"required": ["id", "resourceHandle", "currentVnfExtCpData"],
						"properties": {
							"id": {
								"description": "An identifier with the intention of being globally unique.\n",
								"type": "string"
							},
							"resourceHandle": {
								"required": ["resourceId"],
								"type": "object",
								"description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance. Information about the resource is available from the VIM.\n",
								"properties": {
									"vimConnectionId": {
										"description": "An identifier with the intention of being globally unique.\n",
										"type": "string"
									},
									"resourceProviderId": {
										"description": "An identifier with the intention of being globally unique.\n",
										"type": "string"
									},
									"resourceId": {
										"description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
										"type": "string"
									},
									"vimLevelResourceType": {
										"description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
										"type": "string"
									}
								}
							},
							"extLinkPorts": {
								"description": "Link ports of this VL.\n",
								"type": "array",
								"items": {
									"description": "This type represents information about a link port of an external VL, i.e. a port providing connectivity for the VNF to  an NS VL. It shall comply with the provisions defined in table 5.5.3.9-1.\nNOTE 1:\tThe use cases UC#4 and UC#5 in Annex A.4 of ETSI GS NFV-IFA 007 provide examples for such a configuration. NOTE 2:\tThe value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\" attribute.\n",
									"type": "object",
									"required": ["id", "resourceHandle"],
									"properties": {
										"id": {
											"description": "An identifier with the intention of being globally unique.\n",
											"type": "string"
										},
										"resourceHandle": {
											"required": ["resourceId"],
											"type": "object",
											"description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance. Information about the resource is available from the VIM.\n",
											"properties": {
												"vimConnectionId": {
													"description": "An identifier with the intention of being globally unique.\n",
													"type": "string"
												},
												"resourceProviderId": {
													"description": "An identifier with the intention of being globally unique.\n",
													"type": "string"
												},
												"resourceId": {
													"description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
													"type": "string"
												},
												"vimLevelResourceType": {
													"description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
													"type": "string"
												}
											}
										},
										"cpInstanceId": {
											"description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
											"type": "string"
										},
										"secondaryCpInstanceId": {
											"description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
											"type": "string"
										},
										"trunkResourceId": {
											"description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
											"type": "string"
										}
									}
								}
							},
							"currentVnfExtCpData": {
								"description": "Allows the API consumer to read the current CP configuration information for the connection of external CPs  to the external virtual link. See note.\n",
								"type": "array",
								"items": {
									"description": "This type represents configuration information for external CPs created. * NOTE 1: \tIn case this identifier refers to a CPD with trunking enabled, the external CP instances created\n              from this CPD will represent ports in a trunk.\n* NOTE 2: \tWithin one VNF instance, all VNFC instances created from a particular VDU have the same external\n              connectivity. Thus, given a particular value of the \"cpdId\" attribute, there shall be one\n              \"cpConfig\" entry for each VNFC instance that has been or can be created from a VDU which includes\n              a CPD identified by the \"cpdId\" attribute. If the cpConfig represents a subport in a trunk,\n              all \"cpConfig\" entries in this list shall have the same segmentationId, which means they are\n              connected to the same set of external VLs via the trunk.\n* NOTE 3: \tThe map entry value shall be set to \"null\" in order to delete a \"VnfExtCpConfig\" entry identified\n              by a particular key value from the map, i.e. for the disconnection of an existing external\n              CP instance addressed by cpInstanceId in the deleted map entry from a particular external\n              virtual link, and deletion of that instance in case it represents a subport. Deleting the\n              last key from the map removes the affected instance of the \"VnfExtCpData\" structure from\n              its parent data structure.\n",
									"type": "object",
									"required": ["cpdId"],
									"properties": {
										"cpdId": {
											"description": "An identifier that is unique within a VNF descriptor.\n",
											"type": "string"
										},
										"cpConfig": {
											"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 managed by the API consumer. The entries shall be applied by the VNFM according to the rules of JSON Merge Patch (see IETF RFC 7396). See note 2 and note 3.\n",
											"type": "object",
											"additionalProperties": {
												"description": "This type represents an externally provided link port or network address information per instance of an external connection point. In case a link port is provided, the VNFM shall use that link port when connecting the external CP to the external VL. In a link port is not provided, the VNFM shall create a link port on the external VL, and use that link port to connect the external CP to the external VL. * NOTE: The following conditions apply to the attributes \"linkPortId\" and \"cpProtocolData\":    1)  Void.\n    2)  At least one of the \"linkPortId\" and \"cpProtocolData\" attributes shall be present for an external\n        CP instance representing a subport that is to be created, or an external CP instance that is to be\n        created by creating the corresponding VNFC or VNF instance during the current or a subsequent LCM\n        operation, or for an existing external CP instance that is to be re-configured or added to a\n        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\n        a pre created link port, and the VNFM can use means outside the scope of the present document to obtain\n        the pre-configured address information for the connection point from the resource representing\n        the link port.\n    5)  If both \"cpProtocolData\" and \"linkportId\" are provided, the API consumer shall ensure that the\n        cpProtocolData can be used with the pre-created link port referenced by \"linkPortId\".\n",
												"anyOf": [{
													"required": ["linkPortId"]
												}, {
													"required": ["cpProtocolData"]
												}],
												"type": "object",
												"properties": {
													"parentCpConfigId": {
														"description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
														"type": "string"
													},
													"linkPortId": {
														"description": "An identifier with the intention of being globally unique.\n",
														"type": "string"
													},
													"createExtLinkPort": {
														"description": "Indicates to the VNFM the need to create a dedicated link port for the external CP. If set to True, the VNFM shall create a link port. If set to False, the VNFM shall not create a link port. This attribute is only applicable for external CP instances without a floating IP address that expose a VIP CP instance for which a dedicated IP address is allocated. It shall be present in that case and shall be absent otherwise.\n",
														"type": "boolean"
													},
													"cpProtocolData": {
														"description": "Parameters for configuring the network protocols on the link port that connects the CP to a VL. See note.\n",
														"type": "array",
														"items": {
															"description": "This type represents network protocol data. * NOTE:\tThis attribute allows to signal the addition of further types of layer and protocol\n          in future versions of the present document in a backwards-compatible way. In the current\n          version of the present document, only IP over Ethernet is supported.\n",
															"type": "object",
															"required": ["layerProtocol"],
															"properties": {
																"layerProtocol": {
																	"description": "Identifier of layer(s) and protocol(s). See note.\n",
																	"type": "string",
																	"enum": ["IP_OVER_ETHERNET"]
																},
																"ipOverEthernet": {
																	"description": "This type represents network address data for IP over Ethernet. * NOTE 1:\tAt least one of \"macAddress\" or \"ipAddresses\" shall be present. * NOTE 2:\tExactly one of \"fixedAddresses\", \"numDynamicAddresses\" or \"ipAddressRange\" 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.\n* NOTE 4:\tDepending on the NFVI networking infrastructure, the segmentationId may indicate the actual\n          network segment value (e.g. vlan Id, Vxlan segmentation id, etc.) used in the transport header\n          of the packets or it may be an identifier used between the application and the NFVI networking\n          infrastructure to identify the network sub-interface of the trunk port in question. In the latter\n          case the NFVI infrastructure will map this local segmentationId to whatever segmentationId is\n          actually used by the NFVI’s transport technology.\n",
																	"type": "object",
																	"anyOf": [{
																		"required": ["macAddress"]
																	}, {
																		"required": ["ipAddresses"]
																	}],
																	"oneOf": [{
																		"required": ["fixedAddresses"]
																	}, {
																		"required": ["numDynamicAddresses"]
																	}, {
																		"required": ["ipAddressRange"]
																	}],
																	"properties": {
																		"macAddress": {
																			"description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
																			"type": "string",
																			"format": "MAC"
																		},
																		"segmentationType": {
																			"description": "Specifies the encapsulation type for the traffics coming in and out of the trunk subport. Permitted values: -\tVLAN: the subport uses VLAN as encapsulation type. -\tINHERIT: the subport gets its segmentation type from the network it’s connected to. This attribute may be present for CP instances that represent subports in a trunk and shall be absent otherwise. If this attribute is not present for a subport CP instance, default value VLAN shall be used.\n",
																			"type": "string",
																			"enum": ["VLAN", "INHERIT"]
																		},
																		"segmentationId": {
																			"description": "Identification of the network segment to which the CP instance connects to. See note 3 and note 4.\n",
																			"type": "string"
																		},
																		"ipAddresses": {
																			"description": "List of IP addresses to assign to the CP instance. Each entry represents IP address data for fixed or dynamic IP address assignment per subnet. If this attribute is not present, no IP address shall be assigned. See note 1.\n",
																			"type": "array",
																			"items": {
																				"type": "object",
																				"required": ["type"],
																				"properties": {
																					"type": {
																						"description": "The type of the IP addresses. Permitted values: IPV4, IPV6.\n",
																						"type": "string",
																						"enum": ["IPV4", "IPV6"]
																					},
																					"fixedAddresses": {
																						"description": "Fixed addresses to assign (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
																						"type": "array",
																						"items": {
																							"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
																							"type": "string",
																							"format": "IP"
																						}
																					},
																					"numDynamicAddresses": {
																						"description": "Number of dynamic addresses to assign (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
																						"type": "integer"
																					},
																					"addressRange": {
																						"description": "An IP address range to be used, e.g. in case of egress connections. In case this attribute is present, IP addresses from the range will be used. See note 2.\n",
																						"type": "object",
																						"required": ["minAddress", "maxAddress"],
																						"properties": {
																							"minAddress": {
																								"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
																								"type": "string",
																								"format": "IP"
																							},
																							"maxAddress": {
																								"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
																								"type": "string",
																								"format": "IP"
																							}
																						}
																					},
																					"subnetId": {
																						"description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
																						"type": "string"
																					}
																				}
																			}
																		}
																	}
																}
															}
														}
													}
												}
											}
										}
									}
								}
							}
						}
					}
				},
				"extManagedVirtualLinkInfo": {
					"description": "Information about the externally-managed internal VLs of the VNF instance. See note 5 and note 6.\n",
					"type": "array",
					"items": {
						"type": "object",
						"required": ["id", "vnfVirtualLinkDescId", "networkResource"],
						"properties": {
							"id": {
								"description": "An identifier with the intention of being globally unique.\n",
								"type": "string"
							},
							"vnfVirtualLinkDescId": {
								"description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
								"type": "string"
							},
							"vnfdId": {
								"description": "An identifier with the intention of being globally unique.\n",
								"type": "string"
							},
							"networkResource": {
								"required": ["resourceId"],
								"type": "object",
								"description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance. Information about the resource is available from the VIM.\n",
								"properties": {
									"vimConnectionId": {
										"description": "An identifier with the intention of being globally unique.\n",
										"type": "string"
									},
									"resourceProviderId": {
										"description": "An identifier with the intention of being globally unique.\n",
										"type": "string"
									},
									"resourceId": {
										"description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
										"type": "string"
									},
									"vimLevelResourceType": {
										"description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
										"type": "string"
									}
								}
							},
							"vnfLinkPorts": {
								"description": "Link ports of this VL.\n",
								"type": "array",
								"items": {
									"description": "This type represents a link port of an internal VL of a VNF. It shall comply with the provisions  defined in table 5.5.3.8 1.\nNOTE 1: Either cpInstanceId with cpInstanceType set to \"EXT_CP\" or any combination of cpInstanceId        with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId (i.e. one or both of them) shall be \n        present for a VnfLinkPortInfo. In case both cpInstanceId with cpInstanceType set to \"VNFC_CP\" \n        and vipCpInstanceId are present, the two different CP instances share the linkport.\nNOTE 2: Annex A.4 of ETSI GS NFV-IFA 007 provides examples for configurations where both vipCpInstanceId        and vnfcCpInstanceId are present (UC#5 and UC#5-b), only vnfcCpInstanceId is present (UC#2), or \n        only vipCpInstanceId is present (UC6 and UC#6-b).\nNOTE 3: The value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\"        attribute.\n",
									"type": "object",
									"required": ["id", "resourceHandle"],
									"properties": {
										"id": {
											"description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
											"type": "string"
										},
										"resourceHandle": {
											"required": ["resourceId"],
											"type": "object",
											"description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance. Information about the resource is available from the VIM.\n",
											"properties": {
												"vimConnectionId": {
													"description": "An identifier with the intention of being globally unique.\n",
													"type": "string"
												},
												"resourceProviderId": {
													"description": "An identifier with the intention of being globally unique.\n",
													"type": "string"
												},
												"resourceId": {
													"description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
													"type": "string"
												},
												"vimLevelResourceType": {
													"description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
													"type": "string"
												}
											}
										},
										"cpInstanceId": {
											"description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
											"type": "string"
										},
										"cpInstanceType": {
											"description": "Type of the CP instance that is identified by cpInstanceId.  Shall be present if \"cpInstanceId\" is present and shall be absent otherwise.\nPermitted values: - VNFC_CP: The link port is connected to a VNFC CP. -\tEXT_CP: The link port is associated to an external CP. See note 1.\n",
											"type": "string",
											"enum": ["VNFC_CP", "EXT_CP"]
										},
										"vipCpInstanceId": {
											"description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
											"type": "string"
										},
										"trunkResourceId": {
											"description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
											"type": "string"
										}
									}
								}
							},
							"extManagedMultisiteVirtualLinkId": {
								"description": "An identifier with the intention of being globally unique.\n",
								"type": "string"
							}
						}
					}
				},
				"monitoringParameters": {
					"description": "Active monitoring parameters.\n",
					"type": "array",
					"items": {
						"type": "object",
						"required": ["id", "performanceMetric"],
						"properties": {
							"id": {
								"description": "An identifier that is unique within a VNF descriptor.\n",
								"type": "string"
							},
							"vnfdId": {
								"description": "An identifier with the intention of being globally unique.\n",
								"type": "string"
							},
							"name": {
								"description": "Human readable name of the monitoring parameter, as defined in the VNFD.\n",
								"type": "string"
							},
							"performanceMetric": {
								"description": "Performance metric that is monitored. This attribute shall contain the related \"Measurement Name\" value as defined in clause 7.2 of ETSI GS NFV-IFA 027.\n",
								"type": "string"
							}
						}
					}
				},
				"localizationLanguage": {
					"description": "Information about localization language of the VNF (includes e.g. strings in the VNFD). The localization languages supported by a VNF can be declared in the VNFD, and localization language selection can take place at instantiation time. The value shall comply with the format defined in IETF RFC 5646.\n",
					"type": "string"
				},
				"vnfcResourceInfo": {
					"description": "Information about the virtualised compute and storage resources used by the VNFCs of the VNF instance.\n",
					"type": "array",
					"items": {
						"description": "This type represents the information on virtualised compute and storage resources  used by a VNFC in a VNF instance. It shall comply with the provisions defined in  table 5.5.3.5-1.\nNOTE 1:\tETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on \n        TOSCA specifications.\nNOTE 2:\tA VNFC CP is \"connected to\" an external CP if the VNFC CP is connected to an \n        internal VL that exposes an external CP. A VNFC CP is \"exposed as\" an external \n        CP if it is connected directly to an external VL.\nNOTE 3:\tThe information can be omitted because it is already available as part of the \n        external CP information.\n",
						"type": "object",
						"required": ["id", "vduId", "computeResource"],
						"properties": {
							"id": {
								"description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
								"type": "string"
							},
							"vduId": {
								"description": "An identifier that is unique within a VNF descriptor.\n",
								"type": "string"
							},
							"vnfdId": {
								"description": "An identifier with the intention of being globally unique.\n",
								"type": "string"
							},
							"computeResource": {
								"required": ["resourceId"],
								"type": "object",
								"description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance. Information about the resource is available from the VIM.\n",
								"properties": {
									"vimConnectionId": {
										"description": "An identifier with the intention of being globally unique.\n",
										"type": "string"
									},
									"resourceProviderId": {
										"description": "An identifier with the intention of being globally unique.\n",
										"type": "string"
									},
									"resourceId": {
										"description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
										"type": "string"
									},
									"vimLevelResourceType": {
										"description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
										"type": "string"
									}
								}
							},
							"zoneId": {
								"description": "An identifier with the intention of being globally unique.\n",
								"type": "string"
							},
							"storageResourceIds": {
								"description": "References to the VirtualStorage resources. The value refers to a VirtualStorageResourceInfo item in the VnfInstance.\n",
								"type": "array",
								"items": {
									"description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
									"type": "string"
								}
							},
							"reservationId": {
								"description": "An identifier with the intention of being globally unique.\n",
								"type": "string"
							},
							"vnfcCpInfo": {
								"description": "CPs of the VNFC instance. Shall be present when that particular CP of the VNFC instance  is exposed as an external CP of the VNF instance or is connected to an external CP of the  VNF instance. See note 2. May be present otherwise.\n",
								"type": "array",
								"items": {
									"type": "object",
									"required": ["id", "cpdId"],
									"properties": {
										"id": {
											"description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
											"type": "string"
										},
										"cpdId": {
											"description": "An identifier that is unique within a VNF descriptor.\n",
											"type": "string"
										},
										"vnfExtCpId": {
											"description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
											"type": "string"
										},
										"cpProtocolInfo": {
											"description": "Network protocol information for this CP. May be omitted if the VNFC CP is exposed as an external CP.  See note 3.\n",
											"type": "array",
											"items": {
												"description": "This type describes the protocol layer(s) that a CP uses together with protocol-related information, like addresses.  It shall comply with the provisions defined in table 5.5.3.9b-1.\nNOTE:\tThis attribute allows to signal the addition of further types of layer and protocol in future versions of the \n      present document in a backwards-compatible way. In the current version of the present document, only IP over \n      Ethernet is supported.\n",
												"type": "object",
												"required": ["layerProtocol"],
												"properties": {
													"layerProtocol": {
														"description": "The identifier of layer(s) and protocol(s) associated to the network address information.\nPermitted values: IP_OVER_ETHERNET See note.\n",
														"type": "string",
														"enum": ["IP_OVER_ETHERNET"]
													},
													"ipOverEthernet": {
														"description": "This type represents information about a network address that has been assigned.  It shall comply with the provisions defined in table 5.5.3.10-1.\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": [{
															"required": ["macAddress"]
														}, {
															"required": ["ipAddresses"]
														}],
														"oneOf": [{
															"required": ["addresses"]
														}, {
															"required": ["addressRange"]
														}],
														"properties": {
															"macAddress": {
																"description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
																"type": "string",
																"format": "MAC"
															},
															"segmentationId": {
																"description": "Identification of the network segment to which the Cp instance connects to. See notes 3 and 4.\n",
																"type": "string"
															},
															"ipAddresses": {
																"description": "Addresses assigned to the CP instance. Each entry represents IP addresses assigned by fixed or  dynamic IP address assignment per subnet. See note 1.\n",
																"type": "array",
																"items": {
																	"type": "object",
																	"required": ["type"],
																	"properties": {
																		"type": {
																			"description": "The type of the IP addresses. Permitted values: IPV4, IPV6.\n",
																			"type": "string",
																			"enum": ["IPV4", "IPV6"]
																		},
																		"addresses": {
																			"description": "Fixed addresses assigned (from the subnet defined by \"subnetId\" if provided). See note 2.\n",
																			"type": "array",
																			"items": {
																				"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
																				"type": "string",
																				"format": "IP"
																			}
																		},
																		"isDynamic": {
																			"description": "Indicates whether this set of addresses was assigned dynamically (true) or based on address information provided as input from the API consumer (false). Shall be present if \"addresses\" is present and shall be absent otherwise.\n",
																			"type": "boolean"
																		},
																		"addressRange": {
																			"description": "An IP address range used, e.g. in case of egress connections. See note 2.\n",
																			"type": "object",
																			"required": ["minAddress", "maxAddress"],
																			"properties": {
																				"minAddress": {
																					"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
																					"type": "string",
																					"format": "IP"
																				},
																				"maxAddress": {
																					"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
																					"type": "string",
																					"format": "IP"
																				}
																			}
																		},
																		"subnetId": {
																			"description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
																			"type": "string"
																		}
																	}
																}
															}
														}
													}
												}
											}
										},
										"vnfLinkPortId": {
											"description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
											"type": "string"
										},
										"metadata": {
											"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"
										}
									}
								}
							},
							"parentCpId": {
								"description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
								"type": "string"
							},
							"metadata": {
								"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"
							}
						}
					}
				},
				"vnfVirtualLinkResourceInfo": {
					"description": "Information about the virtualised network resources used by the VLs of the VNF instance. See note 6.\n",
					"type": "array",
					"items": {
						"description": "This type represents the information that allows addressing a virtualised resource that is used by an internal VL instance in a VNF instance.\n",
						"type": "object",
						"required": ["id", "vnfVirtualLinkDescId", "networkResource"],
						"properties": {
							"id": {
								"description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
								"type": "string"
							},
							"vnfVirtualLinkDescId": {
								"description": "An identifier that is unique within a VNF descriptor.\n",
								"type": "string"
							},
							"vnfdId": {
								"description": "An identifier with the intention of being globally unique.\n",
								"type": "string"
							},
							"networkResource": {
								"required": ["resourceId"],
								"type": "object",
								"description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance. Information about the resource is available from the VIM.\n",
								"properties": {
									"vimConnectionId": {
										"description": "An identifier with the intention of being globally unique.\n",
										"type": "string"
									},
									"resourceProviderId": {
										"description": "An identifier with the intention of being globally unique.\n",
										"type": "string"
									},
									"resourceId": {
										"description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
										"type": "string"
									},
									"vimLevelResourceType": {
										"description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
										"type": "string"
									}
								}
							},
							"zoneId": {
								"description": "An identifier with the intention of being globally unique.\n",
								"type": "string"
							},
							"reservationId": {
								"description": "An identifier with the intention of being globally unique.\n",
								"type": "string"
							},
							"vnfLinkPorts": {
								"description": "Links ports of this VL. Shall be present when the linkPort is used for external connectivity by the VNF (refer to VnfLinkPortInfo). May be present otherwise.\n",
								"type": "array",
								"items": {
									"description": "This type represents a link port of an internal VL of a VNF. It shall comply with the provisions  defined in table 5.5.3.8 1.\nNOTE 1: Either cpInstanceId with cpInstanceType set to \"EXT_CP\" or any combination of cpInstanceId        with cpInstanceType set to \"VNFC_CP\" and vipCpInstanceId (i.e. one or both of them) shall be \n        present for a VnfLinkPortInfo. In case both cpInstanceId with cpInstanceType set to \"VNFC_CP\" \n        and vipCpInstanceId are present, the two different CP instances share the linkport.\nNOTE 2: Annex A.4 of ETSI GS NFV-IFA 007 provides examples for configurations where both vipCpInstanceId        and vnfcCpInstanceId are present (UC#5 and UC#5-b), only vnfcCpInstanceId is present (UC#2), or \n        only vipCpInstanceId is present (UC6 and UC#6-b).\nNOTE 3: The value of \"trunkResourceId\" is scoped by the value of \"vimConnectionId\" in the \"resourceHandle\"        attribute.\n",
									"type": "object",
									"required": ["id", "resourceHandle"],
									"properties": {
										"id": {
											"description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
											"type": "string"
										},
										"resourceHandle": {
											"required": ["resourceId"],
											"type": "object",
											"description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance. Information about the resource is available from the VIM.\n",
											"properties": {
												"vimConnectionId": {
													"description": "An identifier with the intention of being globally unique.\n",
													"type": "string"
												},
												"resourceProviderId": {
													"description": "An identifier with the intention of being globally unique.\n",
													"type": "string"
												},
												"resourceId": {
													"description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
													"type": "string"
												},
												"vimLevelResourceType": {
													"description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
													"type": "string"
												}
											}
										},
										"cpInstanceId": {
											"description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
											"type": "string"
										},
										"cpInstanceType": {
											"description": "Type of the CP instance that is identified by cpInstanceId.  Shall be present if \"cpInstanceId\" is present and shall be absent otherwise.\nPermitted values: - VNFC_CP: The link port is connected to a VNFC CP. -\tEXT_CP: The link port is associated to an external CP. See note 1.\n",
											"type": "string",
											"enum": ["VNFC_CP", "EXT_CP"]
										},
										"vipCpInstanceId": {
											"description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
											"type": "string"
										},
										"trunkResourceId": {
											"description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
											"type": "string"
										}
									}
								}
							},
							"metadata": {
								"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"
							}
						}
					}
				},
				"virtualStorageResourceInfo": {
					"description": "Information on the virtualised storage resource(s) used as storage for the VNF instance.\n",
					"type": "array",
					"items": {
						"description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance.\n",
						"type": "object",
						"required": ["id", "virtualStorageDescId", "storageResource"],
						"properties": {
							"id": {
								"description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
								"type": "string"
							},
							"virtualStorageDescId": {
								"description": "An identifier that is unique within a VNF descriptor.\n",
								"type": "string"
							},
							"vnfdId": {
								"description": "An identifier with the intention of being globally unique.\n",
								"type": "string"
							},
							"storageResource": {
								"required": ["resourceId"],
								"type": "object",
								"description": "This type represents the information that allows addressing a virtualised resource that is used by a VNF instance. Information about the resource is available from the VIM.\n",
								"properties": {
									"vimConnectionId": {
										"description": "An identifier with the intention of being globally unique.\n",
										"type": "string"
									},
									"resourceProviderId": {
										"description": "An identifier with the intention of being globally unique.\n",
										"type": "string"
									},
									"resourceId": {
										"description": "An identifier maintained by the VIM or other resource provider. It is expected to be unique within the VIM instance.\n",
										"type": "string"
									},
									"vimLevelResourceType": {
										"description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
										"type": "string"
									}
								}
							},
							"zoneId": {
								"description": "An identifier with the intention of being globally unique.\n",
								"type": "string"
							},
							"reservationId": {
								"description": "An identifier with the intention of being globally unique.\n",
								"type": "string"
							},
							"metadata": {
								"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"
							}
						}
					}
				}
			}
		},
		"metadata": {
			"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"
		},
		"extensions": {
			"description": "Additional VNF-specific attributes that affect the lifecycle management of this VNF instance.\nThese attributes represent values that are stored persistently in the VnfInstance structure for  consumption by the VNFM or the lifecycle management scripts during the execution of VNF lifecycle  management operations.\nAll extensions that are allowed for the VNF are declared in the VNFD. The declaration of an extension  in the VNFD contains information on whether its presence is optional or required, and optionally can  specify an initial value. See notes 2 and 4. The VNFM shall reject requests to write extension attributes  that are not declared in the VNFD with a \"422 Unprocessable entity\" error response as defined in clause  6.4 of ETSI GS NFV-SOL 013.\nModifying the values of these attributes has no direct effect on the VNF instance; however, the modified  attribute values can be considered during subsequent VNF lifecycle management operations, which means that  the modified values can indirectly affect the configuration of the VNF instance.\nThese attributes can be initialized with default values from the VNFD (see note 4).\nThese attributes can be modified with values passed in the request structures of certain LCM operations,  such as the InstantiateVnfRequest structure.\nFurther, these attributes can be created, modified or deleted with the PATCH method.\nIn addition, the provisions in clause 5.7 shall apply.\n"
		},
		"_links": {
			"description": "Links to resources related to this resource.\n",
			"type": "object",
			"required": ["self"],
			"properties": {
				"self": {
					"description": "This type represents a link to a resource using an absolute URI.\n",
					"type": "object",
					"required": ["href"],
					"properties": {
						"href": {
							"description": "String formatted according to IETF RFC 3986.\n",
							"type": "string"
						}
					}
				},
				"indicators": {
					"description": "This type represents a link to a resource using an absolute URI.\n",
					"type": "object",
					"required": ["href"],
					"properties": {
						"href": {
							"description": "String formatted according to IETF RFC 3986.\n",
							"type": "string"
						}
					}
				},
				"instantiate": {
					"description": "This type represents a link to a resource using an absolute URI.\n",
					"type": "object",
					"required": ["href"],
					"properties": {
						"href": {
							"description": "String formatted according to IETF RFC 3986.\n",
							"type": "string"
						}
					}
				},
				"terminate": {
					"description": "This type represents a link to a resource using an absolute URI.\n",
					"type": "object",
					"required": ["href"],
					"properties": {
						"href": {
							"description": "String formatted according to IETF RFC 3986.\n",
							"type": "string"
						}
					}
				},
				"scale": {
					"description": "This type represents a link to a resource using an absolute URI.\n",
					"type": "object",
					"required": ["href"],
					"properties": {
						"href": {
							"description": "String formatted according to IETF RFC 3986.\n",
							"type": "string"
						}
					}
				},
				"scaleToLevel": {
					"description": "This type represents a link to a resource using an absolute URI.\n",
					"type": "object",
					"required": ["href"],
					"properties": {
						"href": {
							"description": "String formatted according to IETF RFC 3986.\n",
							"type": "string"
						}
					}
				},
				"changeFlavour": {
					"description": "This type represents a link to a resource using an absolute URI.\n",
					"type": "object",
					"required": ["href"],
					"properties": {
						"href": {
							"description": "String formatted according to IETF RFC 3986.\n",
							"type": "string"
						}
					}
				},
				"heal": {
					"description": "This type represents a link to a resource using an absolute URI.\n",
					"type": "object",
					"required": ["href"],
					"properties": {
						"href": {
							"description": "String formatted according to IETF RFC 3986.\n",
							"type": "string"
						}
					}
				},
				"operate": {
					"description": "This type represents a link to a resource using an absolute URI.\n",
					"type": "object",
					"required": ["href"],
					"properties": {
						"href": {
							"description": "String formatted according to IETF RFC 3986.\n",
							"type": "string"
						}
					}
				},
				"changeExtConn": {
					"description": "This type represents a link to a resource using an absolute URI.\n",
					"type": "object",
					"required": ["href"],
					"properties": {
						"href": {
							"description": "String formatted according to IETF RFC 3986.\n",
							"type": "string"
						}
					}
				},
				"createSnapshot": {
					"description": "This type represents a link to a resource using an absolute URI.\n",
					"type": "object",
					"required": ["href"],
					"properties": {
						"href": {
							"description": "String formatted according to IETF RFC 3986.\n",
							"type": "string"
						}
					}
				},
				"revertToSnapshot": {
					"description": "This type represents a link to a resource using an absolute URI.\n",
					"type": "object",
					"required": ["href"],
					"properties": {
						"href": {
							"description": "String formatted according to IETF RFC 3986.\n",
							"type": "string"
						}
					}
				}
			}
		}
	}
}