|
|
|
|
|
A volume template (or template for short) is a meaningful collection of rules that provides capabilities for volumes as defined by those rules, or by reference to other capabilities. ISP refers to templates when creating an application volume. It chooses an appropriate template to use based on the capabilities that you request for the volume, and allocates storage by using the rules that the template contains.
The format of a typical template specification is shown in the following definition:
volume_template template_name {
extends template1, template2, ...
inherits capability5, capability6, ...
provides capability1, capability2, ...
requires capability3, capability4, ...
This definition has the following important components:
Indicates the nature of the volume that can be created by the template, for example, | |
Indicates that the template includes all the capabilities, rules and variables from the named templates. See extends. | |
Indicates that the template can inherit capabilities when required from those listed. See inherits. | |
Indicates the capabilities that are provided by volumes created from the template. See provides. | |
Indicates that the template can acquire rules when required from other templates that provide the specified capabilities. See requires. | |
References the message catalog where localized versions of the description may be found, and provides an index number for the description in the catalog. | |
Specifies the start of the section that contains the rules for selecting and laying out storage, and which implement the capabilities that the template provides. The rules usually operate on the values that were specified for the arguments of the requested capabilities. See Rules. See Compound rules. | |
The following sections describe the keywords in detail: