This section explains configurations after the installation.
Server Virtualization Software Definition File
Operations related to server virtualization software can be changed by configuring values in the following definition files beforehand.
Use the UTF-8 character code for definition files.
[Windows]
Installation_folder\Manager\etc\customize_data
[Linux]
/etc/opt/FJSVrcvmr/customize_data
vm.rcxprop
Describe each line of the definition file in the following format:
Key = Value |
Item | Key | Value | Remarks |
|---|---|---|---|
Configuration of power control for VMware DRS and DPM | drs_power_on_vm | true|false | When server virtualization software is VMware, the values are valid.
If left blank, "false" is set. When specifying "true", set VMware DRS and VMware DPM as follows:
When specifying "Manual", startup of L-Servers and VM guests may fail. For detail on VMware DRS/DPM, refer to "When using VMware DRS or VMware DPM" in "E.2.2 Preparations" |
Definition Files to Configure using Console Connections from Public LAN
When using console connections from the public LAN, configure the connection destination for the VM host in the following definition files:
[Windows]
Installation_folder\Manager\etc\customize_data
[Linux]
/etc/opt/FJSVrcvmr/customize_data
vm_console.rcxprop
Specify a folder or tenant name, the physical server name of the VM host, and the corresponding connection destination in one line, separated by commas (",").
folder_or_tenant_name, physical_server_name, destination_to_connect |
Item | Description |
|---|---|
Folder or tenant name | Specify the folder name or tenant name using a full path (the first letter must be "/"). |
Physical server name | Specify the physical server name of the VM host. |
Connection destination | Specify the IP address for a VM host that can be connected to through the admin client, or the host name for which name resolution is available in the admin client environment. |
/, bx900-1, 192.168.10.100 (*1) |
*1: Definition for root folder (/). The default settings in all tenants.
*2: Definition for folder (/folderA). Specify the destination to connect to using using host name.
*3: Definition of tenants (/folderA/tenantB). Specify multiple hosts.
Note
When describing more than three commas (",") in one line, any descriptions after the third comma are ignored.
When the descriptions start with a "#", the string is regarded as a comment line.
If reading of the definition file fails, set the IP address of the admin LAN for the VM host registered in Resource Orchestrator as the connection destination.
When the folder or tenant name, and the physical server name do not match the definition file specifications, perform console connections using the IP address of the admin LAN for the VM host.
When there are multiple VM hosts used in a folder or a tenant, settings using the same folder or tenant must be described separately, in multiple lines.
When specifying a folder, apply the relevant settings to the sub folders and tenants under that folder.
When settings targeting the sub folders or tenants under the specified folder are configured, and definitions with the same physical server name also exist, the priority is given to the definitions.
Example
When there are the following definitions of (1) and (2), the folder or tenant name is "/folderA/tenantB" and the physical server name is virtual L-Server of "bx900-1", console connections are performed by using the IP address (2).
(1)/folderA,bx900-1,192.168.10.100
(2)/folderA/tenantB,bx900-1,192.168.20.100
When describing the same physical server configurations in the same folder or tenant using multiple lines, the configurations in the latter descriptions are valid.
Example
When there are the following definitions of (1) and (2), the definition (2) is valid.
(1)/folderA,bx900-1,192.168.10.100
(2)/folderA,bx900-1,192.168.20.100
