The ONAP Data Model implements the IM's StorageDesc element as TOSCA capabilities of the type onap.capabilities.Storage.
This capability characterizes an attached storage device. Like onap.capabilities.Compute, intended to be used primarily as part of a TOSCA requirement clause. Normally, requirements of this type are never satisfied within the model. They stay “dangling” until instantiation. On instantiation, the orchestrator satisfies them out of the available inventory.
Definition
capability_types:
onap.capabilities.Storage:
description: |
When used with a requirement, characterizes the requested attached storage functionality
derived_from: tosca.capabilities.Attachment
properties:
storage_type:
description: the type of the required storage resource (e.g., volume, object, etc)
type: string
required: false
storage_size:
description: amount of internal disk storage
type: scalar-unit.size
required: false
constraints:
- greater_or_equal: 0 MB
io_bitrate:
description: IO performance, in bits per second
type: integer
required: false
architecture:
description: vendor+architecture, for example, Intel64
type: string
required: false
custom_features:
description: |
Additional features description, serialized in a well-known format.
type: onap.datatypes.json
required: false
In addtition to the obvious properties required by the IM, this capability type also includes properties that allow for easy customization:
- architecture - allows the VNF vendors to focus their requirements on a specific hardware architecture, for example "EMC" or "NetApp".
- custom_features - an opaque container for a list of feature definitions. It is of the onap.datatypes.json data type, meaning that it is a JSON-formatted string. Can be treated as just a plain string.
These customization-oriented properties are very similar to those of onap.capabilities.Compute.