HP Storage Provisioning Manager (SPM) version 2.3 User Guide

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.
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.
Volume Name Prefix requirement
A Volume Name Prefix requirement specifies a string that will be used by SPM to name volumes
when SPM creates a new volume on an HP 3PAR StoreServ Storage System or using an array
adapter. The string may be up to 24 characters long, and may contain digits, upper or lower-case
letters, underscore (_), and period (.). SPM concatenates the prefix with a random number up to
seven digits long to create a unique volume name. By default, SPM uses SPM_ as the volume prefix.
If an array interfaced by an adapter has more restrictive limits on what may be included in a
volume name, it may alter the volume name from the suggested volume name without error. The
conformance of a service created with a volume name prefix requirement is not affected by the
volume name. This requirement only influences volume creation.
32 Storage service policy