This section explains overcommit definition files.
The following settings are configured in overcommit definition files:
VM pools used for overcommit
Calculation methods for the available space for VM pools used for overcommit
Configurations for Thin Provisioning attributes on storage pools
Point
Overcommit definition files are provided to remain compatible between V2.3 and V3.1, and V3.0 and V3.1 of Resource Orchestrator. Do not use overcommit definition files for anything other than the intended use.
Overcommit definition files may not be provided in future versions of Resource Orchestrator. Use the following procedure to transfer the configuration information and start to use the specification method in V3.1 at an early stage.
Transfer of Configurations for Overcommit Attributes
Execute the rcxmigrate_oc command.
For details on the rcxmigrate_oc command, refer to "5.2 rcxmigrate_oc" in the "Reference Guide (Command/XML) CE".
Delete the following key and value from the definition file.
over_commit
over_commit_calculate_by_reserve_value
Transfer of Configurations for Thin Provisioning Attributes
Delete the following key and value from the definition file.
thin_provisioning
[Windows Manager]
Installation_folder\SVROR\Manager\etc\customize_data
[Linux Manager]
/etc/opt/FJSVrcvmr/customize_data
pool.rcxprop
over_commit=pool1,pool2,... |
Specify the VM pools used for overcommit.
Multiple VM pool names can be specified. When specifying multiple resource pools, separate them using commas (",").
If the VM pool is arranged in a hierarchy, specify the name using an absolute path.
For a VM pool directly under the orchestration tree, specify only its name.
Example
over_commit=VMPool,/folder1/VMPool
Point
When creating L-Servers that use overcommit and L-Servers that do not, both a VM pool that uses overcommit and a VM pool that does not must be created.
After editing overcommit definition files, open the [Resource] tab of the ROR console, and then confirm that the modification has been reflected on the resource pool attributes displayed in the resource details or the resource pool list.
Specify the calculation method for available space for a VM pool used for overcommit.
One of the following values can be specified.
When using a reservation value
Specify "true".
When using a maximum value
Specify "false".
"false" is specified in the following cases:
When specification of "over_commit_calculate_by_reserve_value" is omitted
When an invalid value is specified
Example
over_commit_calculate_by_reserve_value=true
Specify names of storage pools that have Thin Provisioning attributes configured.
Multiple storage pool names can be specified. When specifying multiple resource pools, separate them using commas (",").
If a storage pool is arranged in a hierarchy, specify the name using an absolute path.
For a storage pool directly under the orchestration tree, specify only its name.
Example
thin_provisioning=StoragePool,/folder/StoragePool
Note
Thin Provisioning attributes of a storage pool are configured when the storage pool is created.
If the thin_provisioning key is specified in a overcommit definition file (the file is configured when a storage pool is created and is loaded into Resource Orchestrator), a storage pool with Thin Provisioning attributes will be created.
If the thin_provisioning key is not specified in the definition file, a storage pool without Thin Provisioning attributes will be created.
For storage pools that have already been created, the setting for Thin Provisioning attributes cannot be changed even if the following operations are performed:
Changing the value of the thin_provisioning key
Changing storage pool names
When creating storage pools for which Thin Provisioning attributes are configured, specify the names of storage pools that are planned for the thin_provisioning key beforehand.
