[datamodel-upd][SOL002][VNF-LCM][v5.2.1][6.3.5.x.x Test-IDs] Add attribute for... (d76356c6) · Commits · NFV - Network Functions Virtualisation / api-tests

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

+102 −0

Original line number	Diff line number	Diff line
		@@ -1892,6 +1892,57 @@
		}
		}
		}
		},
		"routingResource": {
		"description": "Network resources that provide the forwarding/routing capabilities associated to the network resource realizing this VL.\n",
		"type": "array",
		"items": {
		"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* NOTE 1: The information about the VIM or CISM connection referenced by the VIM connection id is known to the\n VNFM. Moreover, the identifier of the VIM connection provides scope to the resourceId.\n\n* NOTE 2: The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or CISM or the resource \n provider and can be used as information that complements the ResourceHandle. When the container\n infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would \n correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, \n PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 3: When the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the \n following way:\n - For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide \n per resource type.\n - For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, \n i.e. the value of the 'claimName' field in the Kubernetes® manifest, or a compound name built by \n Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own \n manifest.\n - For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of \n the 'metadata.name' field in Kubernetes® manifest.\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 the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
		"type": "string"
		},
		"vimLevelResourceType": {
		"description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\n",
		"type": "string"
		},
		"vimLevelAdditionalResourceInfo": {
		"description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider.\n* NOTE: At least one attribute shall be present.\n",
		"type": "object",
		"properties": {
		"hostName": {
		"description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
		"type": "string"
		},
		"persistentVolume": {
		"description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
		"type": "string"
		},
		"additionalInfo": {
		"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"
		}
		}
		},
		"containerNamespace": {
		"description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
		"type": "string"
		}
		}
		}
		}
		}
		}
		@@ -2132,6 +2183,57 @@
		}
		}
		}
		},
		"routingResource": {
		"description": "Network resources that provide the forwarding/routing capabilities associated to the network resource realizing this VL.\n",
		"type": "array",
		"items": {
		"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* NOTE 1: The information about the VIM or CISM connection referenced by the VIM connection id is known to the\n VNFM. Moreover, the identifier of the VIM connection provides scope to the resourceId.\n\n* NOTE 2: The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or CISM or the resource \n provider and can be used as information that complements the ResourceHandle. When the container\n infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would \n correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, \n PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 3: When the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the \n following way:\n - For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide \n per resource type.\n - For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, \n i.e. the value of the 'claimName' field in the Kubernetes® manifest, or a compound name built by \n Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own \n manifest.\n - For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of \n the 'metadata.name' field in Kubernetes® manifest.\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 the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
		"type": "string"
		},
		"vimLevelResourceType": {
		"description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\n",
		"type": "string"
		},
		"vimLevelAdditionalResourceInfo": {
		"description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider.\n* NOTE: At least one attribute shall be present.\n",
		"type": "object",
		"properties": {
		"hostName": {
		"description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
		"type": "string"
		},
		"persistentVolume": {
		"description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
		"type": "string"
		},
		"additionalInfo": {
		"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"
		}
		}
		},
		"containerNamespace": {
		"description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
		"type": "string"
		}
		}
		}
		}
		}
		}

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

+102 −0

Original line number	Diff line number	Diff line
		@@ -1894,6 +1894,57 @@
		}
		}
		}
		},
		"routingResource": {
		"description": "Network resources that provide the forwarding/routing capabilities associated to the network resource realizing this VL.\n",
		"type": "array",
		"items": {
		"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* NOTE 1: The information about the VIM or CISM connection referenced by the VIM connection id is known to the\n VNFM. Moreover, the identifier of the VIM connection provides scope to the resourceId.\n\n* NOTE 2: The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or CISM or the resource \n provider and can be used as information that complements the ResourceHandle. When the container\n infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would \n correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, \n PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 3: When the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the \n following way:\n - For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide \n per resource type.\n - For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, \n i.e. the value of the 'claimName' field in the Kubernetes® manifest, or a compound name built by \n Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own \n manifest.\n - For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of \n the 'metadata.name' field in Kubernetes® manifest.\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 the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
		"type": "string"
		},
		"vimLevelResourceType": {
		"description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\n",
		"type": "string"
		},
		"vimLevelAdditionalResourceInfo": {
		"description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider.\n* NOTE: At least one attribute shall be present.\n",
		"type": "object",
		"properties": {
		"hostName": {
		"description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
		"type": "string"
		},
		"persistentVolume": {
		"description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
		"type": "string"
		},
		"additionalInfo": {
		"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"
		}
		}
		},
		"containerNamespace": {
		"description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
		"type": "string"
		}
		}
		}
		}
		}
		}
		@@ -2134,6 +2185,57 @@
		}
		}
		}
		},
		"routingResource": {
		"description": "Network resources that provide the forwarding/routing capabilities associated to the network resource realizing this VL.\n",
		"type": "array",
		"items": {
		"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* NOTE 1: The information about the VIM or CISM connection referenced by the VIM connection id is known to the\n VNFM. Moreover, the identifier of the VIM connection provides scope to the resourceId.\n\n* NOTE 2: The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or CISM or the resource \n provider and can be used as information that complements the ResourceHandle. When the container\n infrastructure service is a Kubernetes® instance the vimLevelResourceType is the type of resource, as would \n correspond to the 'kind' field if the resource is declared in its own Kubernetes® manifest, e.g.: Pod, \n PersistentVolumeClaim, NetworkAttachmentDefinition.\n\n* NOTE 3: When the container infrastructure service is a Kubernetes® instance the resourceId shall be populated in the \n following way:\n - For a compute MCIO, it is the instance identifier that Kubernetes® assigns, which is unique cluster wide \n per resource type.\n - For a storage MCIO modelled as a persistent volume claim, it is the name of the persistent volume claim, \n i.e. the value of the 'claimName' field in the Kubernetes® manifest, or a compound name built by \n Kubernetes® if the persistent volume claim is defined inline in another template instead of in its own \n manifest.\n - For a network MCIO representing a NetworkAttachmentDefinition, a Service or an Ingress, it is the value of \n the 'metadata.name' field in Kubernetes® manifest.\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 the CISM or other resource provider. It is expected to be unique within the VIM instance.\n",
		"type": "string"
		},
		"vimLevelResourceType": {
		"description": "Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 2.\n",
		"type": "string"
		},
		"vimLevelAdditionalResourceInfo": {
		"description": "This type represents additional resource information which resource and resource type specific, and which is available from the VIM or the CISM or the resource provider.\n* NOTE: At least one attribute shall be present.\n",
		"type": "object",
		"properties": {
		"hostName": {
		"description": "Name of the host where the resource is allocated. It shall be present for compute resources in the scope of the CISM and shall be absent otherwise. See note.\n",
		"type": "string"
		},
		"persistentVolume": {
		"description": "Name of the persistent volume to which the persistent volume claim representing the storage resource is bound. It may be present for storage resources in the scope of the CISM and shall be absent otherwise. See note.\n",
		"type": "string"
		},
		"additionalInfo": {
		"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"
		}
		}
		},
		"containerNamespace": {
		"description": "The value of the namespace in which the MCIO corresponding to the resource is deployed. This attribute shall be present if the resource is managed by a CISM and it shall be absent otherwise.\n",
		"type": "string"
		}
		}
		}
		}
		}
		}

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

+102 −0

File changed.

Preview size limit exceeded, changes collapsed.

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

+102 −0

File changed.

Preview size limit exceeded, changes collapsed.