HP Storage Provisioning Manager (SPM) version 2.1 User Guide

Storage Pool Subscription Ratio requirement
The Storage Pool Subscription Ratio requirement specifies the ratio of subscribed
capacity of a pool to its physical capacity which 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, etc. 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 which 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 which 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 only fulfills service
requests using a specific set of storage arrays.
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 or not.
Volume Committed Capacity requirement
The Volume Committed Capacity requirement specifies the percentage of capacity which
should be committed or allocated. The remainder of capacity is to 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.
Volume Creation Security Group requirement
The Volume Creation Security Group requirement specifies the security group into which
a created volume is placed. If not specified, SPM attempts to put the volume in the same security
group as specified for the storage pool. If that is not possible due to the security configuration,
SPM attempts to use the security group of the service or else the only security group in which the
user has the CreateResource permission if there is only one such security group.
30 Storage service policy