Operating Environment Software Owner manual

Storage Pool Available Capacity requirement
The Storage Pool Available Capacity and Storage Pool Available Capacity
(percentage) requirements specify the amount of free capacity (noncommitted available capacity)
that must exist in a pool after the provisioning request is completed. The amount of free capacity
can be expressed as a data size or as a percentage of the pool size.
This requirement enables the storage architect to control the amount of remaining free space that
must exist for provisioning to be performed from a pool.
This requirement is enforced only when a volume is created or grown, and evaluates as a Match
when the remaining free space in a storage pool is left after the provisioning is complete. After
provisioning, the requirement always evaluates as a Match. For example, the requirement does
not make existing volume service nonconformant because the required pool free space was no
longer satisfied.
Storage Pool Subscription Ratio requirement
The Storage Pool Subscription Ratio requirement specifies the ratio of subscribed
capacity of a pool to its physical capacity that must exist in order to create or grow a volume within
the pool. Because it is expressed as a ratio of the pool subscribed capacity, a value of “1” means
no oversubscription is performed. A value of “2” means that new volumes are created in the pool
up to twice the physical capacity of the pool. A value of “3” means triple, and so on. This
requirement controls thinly provisioned volume creation and growth.
NOTE: The Storage Pool Subscription Ratio requirement is specific to thin provisioning.
Storage Pool Volume Count requirement
The Storage Pool Volume Count requirement specifies the number of volumes in a pool.
This requirement can be used to control volume creation within a pool to keep a pool from becoming
overallocated.
Tag requirement
The Tag requirement specifies a tag that must exist on at least one resource (array, storage pool,
volume or network) within the matching service.
Use Resource requirement
The Use Resource requirement specifies a resource that must be included (or excluded) from a
service. Types of objects referenced can be Volumes, Storage Pools, Arrays, or SANs. Storage
architects or administrators may use this requirement to ensure a given template fulfills service
requests using only a specific set of storage resources.
Volume Capacity requirement
The Volume Capacity requirement specifies the capacity, or size, of the storage service. The
capacity is the storage size as advertised to the server, and may or may not be actually allocated
on a storage array depending on whether thin provisioning is used.
Volume Committed Capacity requirement
The Volume Committed Capacity requirement specifies the percentage of capacity that should
be committed or allocated. The remainder of capacity will be thinly provisioned. A purely thin
provisioned volume would have a Volume Committed Capacity = 0, whereas a purely thick
provisioned volume would have a Volume Committed Capacity = 100. A storage device
supporting hybrid allocation, where part was thickly provisioned and part was thinly provisioned,
would implement values between 0 and 100.
Requirement types 29