This section explains how to maintain compatibility with earlier versions of Resource Orchestrator.
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 maintain compatibility between V3.0.0 and V2.3 of FUJITSU Software ServerView 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.
This section explains the definition files for display control of VM pool attribute information.
Point
The definition files for display control of VM pool attribute information provided to remain compatible between V3.0.0 and this version of Resource Orchestrator.
When performing upgrade from ROR V3.0.0, the definition files for display control of VM pool attribute information are created to provide compatibility between V3.0.0 and V3.1 for execution of the rcxadm pool list -extend attributes command.
To display the "ATTRIBUTES" item of a VM pool as a result of the command execution, delete this definition file.
[Windows Manager]
Installation_folder\SVROR\Manager\etc\customize_data
[Linux Manager]
/etc/opt/FJSVrcvmr/customize_data
cli_notlist_oc.rcxprop
If the definition file exists
The "ATTRIBUTES" item of a VM pool will not be displayed when the rcxadm pool list -extend attributes command is executed.
If the definition file does not exist
The "ATTRIBUTES" item of a VM pool will be displayed when the rcxadm pool list -extend attributes command is executed.
This section describes the way to change the sorting order of the resource list in the tree.
In V3.1.0, the tree on the ROR console [Resource] tab displays the resources listed in ascending order of name, by resource type.
As with earlier versions of Resource Orchestrator, to display resources in order of registration or creation, edit the following definition file.
[Windows Manager]
Installation_folder\SVROR\Manager\etc\customize_data
[Linux Manager]
/etc/opt/FJSVrcvmr/customize_data
gui_config.rcxprop
RESOURCE_TREE_SORT_ORDER=RESOURCE_TREE_ORDER
RESOURCE_TREE_ORDER
Specify the display order using one of the following options:
Displays the resource list in alphabetical order of resource names.
Displays the resource list in the order in which the resources were registered or created.
Note
To enable the above-mentioned setting, restart the manager after editing the definition file.
The orders of some lists, such as for blade servers in the server tree, cannot be changed.
This section explains the server status of L-Platform API "GetLPlatformConfiguration".
The prorgam has been corrected so that the server status of L-Platform API "GetLPlatformConfiguration" (lserverStatus) is no longer returned.
Details of Modification
In the L-Platform API "GetLPlatformConfiguration" specifications, the server status (lserverStatus) was not contained in the response but was returned due to a problem. In V3.1.1A or later, the server status is no longer contained in the response.
Corrective Action
If it is expected that the server status is contained in the response from the L-Platform API "GetLPlatformConfiguration", edit the following definition file.
Open the definition file using a text editor.
The definition file is stored in the following location.
[Windows Manager]
Installation_folder\RCXCFMG\config\api_config.xml
[Linux Manager]
/etc/opt/FJSVcfmg/config/api_config.xml
Set the following items in the definition file.
Key name
getlplatformconfiguration-lservestatus
Value to be Set
true: Return the server status
false: Do not return the server status (default)
Save the file.
Restart the manager.
Refer to "2.1 Starting and Stopping Managers" in the "Operation Guide CE" for information on the manager restart method.
