Top
ServerView Resource Orchestrator Cloud Edition V3.1.1 Setup Guide
ServerView

C.2.1 Creating Definition Files

This section explains how to create definition files.

For definition files common to virtual L-Servers, refer to "C.1 Definition Files Commonly Shared when Creating Virtual L-Servers".

This section explains the definition files specific to VMware.

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.

Location of the Definition File

[Windows Manager]
Installation_folder\SVROR\Manager\etc\customize_data

[Linux Manager]
/etc/opt/FJSVrcvmr/customize_data

Definition File Name

vm.rcxprop

Definition File Format

Describe each line of the definition file in the following format:

Key = Value

Definition File Items
Table C.4 List of Items

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.

  • When starting an L-Server (VM guest), if moving an L-Server (VM guest) between VM hosts using VMware DRS, or turning on a VM host using VMware DPM

    Specify "true".

  • If other than the above

    Specify "false".

If left blank, "false" is set.
Restarting of the server is not required after changing this configuration.

When specifying "true", set VMware DRS and VMware DPM as follows:

  • VMware DRS

    "partly automatic" or "full automatic"

  • VMware DPM

    "off" or "automatic"

When specifying "Manual", startup of L-Servers and VM guests may fail.

For details on VMware DRS/DPM, refer to "When using VMware DRS or VMware DPM" in "E.1.2 Preparations for Servers" in the "Design Guide CE".


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:

Location of the Definition File

[Windows Manager]
Installation_folder\SVROR\Manager\etc\customize_data

[Linux Manager]
/etc/opt/FJSVrcvmr/customize_data

Definition File Name

vm_console.rcxprop

Definition File Format

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

Definition File Items
Table C.5 List of Items

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.

Example Definition File

/, bx900-1, 192.168.10.100 (*1)
/folderA, bx900-1, host1 (*2)
/folderA/tenantB, bx900-1, 192.168.30.100 (*3)
/folderA/tenantB, bx900-2, 192.168.30.200 (*3)

*1: Definition for root folder (/). The default settings in all tenants.
*2: Definition for folder (/folderA). Specify the destination to connect to 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