This section explains how to create definition files.
For definition files common to virtual L-Servers, refer to "8.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.
[Windows Manager]
Installation_folder\SVROR\Manager\etc\customize_data
[Linux Manager]
/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 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:
[Windows Manager]
Installation_folder\SVROR\Manager\etc\customize_data
[Linux Manager]
/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 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 "#", 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
When using console connections of a virtual L-Server from the public LAN through the proxy server in the following environments, specify an IP address that can be communicated with using the proxy server.
VMware vSphere 5.1
VMware vSphere 5.5
VMware vSphere 6.0
GUIRunOnce Definition Files
When the OS of the virtual L-Server is Windows, it is possible to specify the GUIRunOnce command (*) when creating a virtual L-Server with an image specified.
* Note: This is the command that is executed the first time a user performs GUI login on a guest OS.
When specifying the GUIRunOnce command, configure the following definition file.
For details on the GUIRunOnce command, refer to the Sysprep documentation of Microsoft Windows.
The support scope in Resource Orchestrator is shown as below.
However, there are OS types of virtual L-Server that are not supported by the virtual software depending on the software version. For details, refer to the manuals of virtualization software.
Target | Support Scope |
|---|---|
Virtualization software | VMware vSphere 4.0 |
Virtual L-Server OS type | Microsoft(R) Windows(R) 2008 |
Resource Orchestrator manager | Windows Manager |
[Windows Manager]
Installation_folder\SVROR\Manager\etc\customize_data\sysprep_guirunonce
[Linux Manager]
/etc/opt/FJSVrcvmr/customize_data/sysprep_guirunonce
Use the file extension ".rcxprop" for an arbitrary file name. However, define the file name using the following character string:
The file name must start with an alphanumeric character, and can contain up to 64 alphanumeric characters, underscores ("_"), and hyphens ("-").
Describe the definition file in individual lines as below:
Command string specified as the GUIRunOnce command |
The command is described using line breaks to separate each command.
As the specified string itself is used, symbols such as double quotes or single quotes must be specified in a format that can be recognized as a command string on Windows.
Empty lines are ignored.
Up to 500 commands (500 lines) can be specified. If a line after the 501th line is specified, the line will be ignored.
Lines starting with "#" are considered as comments.
The command is executed from the first line to the last line, in order. Commands are not executed until the previous command is completed.
The character-code of the file is UTF-8.
Configure the line break code of the file as follows:
[Windows Manager]
CR+LF
[Linux Manager]
LF
Example
c:\setup\setup_first.bat
netsh advfirewall firewall set rule group="remote desktop" new enable=yes
...
c:\setup\setup_last.bat
SCSI Controller Definition File
SCSI controllers for virtual disks connected to guest OSs can be configured for each OS type using the following definition file.
Use the UTF-8 character code for definition files.
[Windows Manager]
Installation_folder\SVROR\Manager\etc\customize_data
[Linux Manager]
/etc/opt/FJSVrcvmr/customize_data
Information
The definition file sample (scsicontroller.rcxprop.sample) is stored in the location above.
When using the sample as the definition file, place the file after deleting the ".sample" included in the file name.
scsicontroller.rcxprop
Describe each line of the definition file in the following format:
Key = Value |
The character-code of the file is UTF-8.
Configure the line break code of the file as follows:
[Windows Manager]
CR+LF
[Linux Manager]
LF
Item | Key | Value | Remarks |
|---|---|---|---|
SCSI controller type | Specify an OS type. (*) | Specify one of the following SCSI controller types:
| For OS types with no SCSI controller type specified, the following SCSI controller is connected:
|
* Note: Refer to the following VMware web site and specify the value in the "NAME" column for the corresponding OS.
URL: |
For Windows Server 2012, refer to the following web site:
URL: |
Information
In the definition file, the following values are configured by default:
windows8Server64Guest=lsilogicsas |
Note
SCSI controllers are created based on the content of the definition file at the following timings:
When creating virtual L-Servers without using cloning images
When attaching the 14th, the 28th, or the 42nd data disk
Note that it is not possible to change the type of a SCSI controller that has already been created.
Due to the design of VMware products, there is no differentiation between Windows Server 2012 and Windows Server 2012 R2. For this reason, it is not possible to configure different SCSI controllers for each of these OSs.
When more than two lines are written, the configurations described in the last line are valid.
Blank spaces and tabs directly before and after an equal sign ("=") are ignored.
Lines starting with "#" are regarded as comment lines.
If you edit and save a UTF-8 text file using Windows Notepad, the Byte Order Mark (BOM) is stored in the first three bytes of the file, and the information specified on the first line of the file will not be analyzed correctly. When using Notepad, specify the information from the second line.
Example
Example of the Definition File Description
########################################################################### |
