The behavior that ISP exhibits when allocating storage can be controlled by setting the value of the allocation_priority_order attribute. For example, this attribute determines if growing the storage pool is preferred to dropping the desired rules when there is insufficient storage to create a volume. The default behavior can be changed by editing the definition of the attribute in the /etc/default/allocator file, or, for a single invocation of the vxassist or vxvoladm command, by specifying the -o allocation_priority=value option as a command-line argument.
Values of the precedence order shows that the value argument can take an integer value from 1 to 12.
Precedence order symbols shows the meaning of the precedence order symbols.
For example, the default behavior of ISP (equivalent to setting allocation_policy_order=7), A < S < T < D, has the following meaning:
If a set of capabilities are specified for a volume during creation, ISP may find that there are multiple sets of templates that provide the same set of capabilities. These sets are referred to as template combinations. Some of the available template combinations may provide additional capabilities (extraneous capabilities) to those that were requested for the volume. By preferring not to select a different template combination, you can avoid implicitly specifying the extraneous capabilities. This assumes that you would request these capabilities explicitly if you required them.
The templates that are associated with a storage pool define the characteristics of the volumes that can be created in that pool. The selfsufficient policy of the storage pool allows you to control whether ISP can redefine the pool definition automatically, and, if so, to what extent.