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".
Configure the definition files for enabling Solaris Zones so that VM hosts are registered based on whether the Logical Domains Manager daemon is enabled or disabled.
For details, refer to "8.7.1 Creating Definition Files".
Definition File of Whether to Save the Configuration Information
Defines whether to save the configuration information of VM guests automatically when changes are made to them.
The scope of this definition file includes all VM hosts.
Automatic saving of the configuration information is triggered by the following operations:
When performing the following operations using Resource Orchestrator:
Power operations of VM guests/virtual L-Servers (power on/power off/forced power off/reboot/reboot (forced))
Migration between servers on VM guests/virtual L-Servers
Creating and Deleting Virtual L-Servers
Modification of virtual L-Server specifications (the number of CPUs, memory size)
Attachment/detachment of disks to and from a virtual L-Server
When performing the following operations for a guest domain on the control domain:
Creation/removal of guest domains
Binding/unbinding of resources
Stopping/starting of a guest domain
Modification of the number of CPUs and memory size
Addition/deletion of virtual disks
Migration of a guest domain
[Windows Manager]
Installation_folder\SVROR\Manager\etc\customize_data
[Linux Manager]
/etc/opt/FJSVrcvmr/customize_data
Information
The sample definition file (sparc_vm.rcxprop.sample) is stored in the location above.
When using the sample as the definition file, delete the ".sample" included in the file name after changing the content.
sparc_vm.rcxprop
UTF-8
[Windows Manager]
CR/LF
[Linux Manager]
LF
In the definition file, an item to define is entered on each line. Each line must be entered in the following format.
Key = Value |
When adding comments, start the line with a number sign ("#").
Specify the following items:
Key | Description |
|---|---|
OVM_AUTO_SAVE_CONFIG | Use this key to specify whether to save the configuration information of VM guests automatically.
|
Example
When saving the configuration information of VM guests automatically
OVM_AUTO_SAVE_CONFIG=true |
Note
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.
Describe the definitions carefully, as entry is case-sensitive.
When it corresponds to the following conditions, the operation becomes the same as the case when "true" is specified.
When the definition is omitted
When a value other than true/false is specified
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.
The definition file configurations are reflected without restarting the manager in Resource Orchestrator.
Definition of connection information of the installation server
Define the following required information in order to connect with the installation server of Solaris 11.
Use the UTF-8 character code for definition files.
URL which shows the location of an installation server
Indicate the URL for the wanboot-cgi program on an installation server in the definition file.
The URL for the wanboot-cgi program is defined as a parameter called "root_server" of the following configuration file on the installation server.
File Name
/etc/netboot/wanboot.conf
The parameter name defined for the URL
root_server
[Windows Manager]
Installation_folder\SVROR\Manager\etc\customize_data
[Linux Manager]
/etc/opt/FJSVrcvmr/customize_data
Information
The sample definition file (ovm_sparc_install_server.rcxprop.sample) is stored in the location above.
When using the sample as the definition file, delete the ".sample" included in the file name after changing the content.
ovm_sparc_install_server.rcxprop
UTF-8
[Windows Manager]
CR/LF
[Linux Manager]
LF
In the definition file, an item to define is entered on each line. Each line must be entered in the following format.
Key = Value |
When adding comments, start the line with a number sign ("#").
Specify the following items:
Key | Description |
|---|---|
INSTALL_SERVER | Specify the URL which shows the location of the installation server. Example http://192.168.11.12:5555/cgi-bin/wanboot-cgi |
Note
When the same key is defined in more than two lines, the configuration in the last line is valid.
Blank spaces and tabs directly before and after an equal sign ("=") are ignored.
Describe the definitions carefully, as entry is case-sensitive.
When a definition is omitted, error message number 67136 is output.
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.
The definition file configurations are reflected without restarting the manager in Resource Orchestrator.
Automatic release cancellation of the resource at the time of L-Server deletion
When deletion of L-Server is performed with this product and the guest domain for deletion is in a bound state, this product releases resources automatically (unbind) and deletes the guest domain in the bound state.
When changing a setup so that a guest domain that is in a bound state may not be deleted, indicate the definition in the following definition files.
[Windows Manager]
Installation_folder\SVROR\Manager\etc\customize_data
[Linux Manager]
/etc/opt/FJSVrcvmr/customize_data
Information
The sample definition file (sparc_vm.rcxprop.sample) is stored in the location above.
When using the sample as the definition file, delete the ".sample" included in the file name after changing the content.
sparc_vm.rcxprop
UTF-8
[Windows Manager]
CR/LF
[Linux Manager]
LF
In the definition file, an item to define is entered on each line. Each line must be entered in the following format.
Key = Value |
When adding comments, start the line with a number sign ("#").
Specify the following items:
Key | Description |
|---|---|
OVM_FORCE_DELETION | Define whether to change the value of auto-boot? into "false" at the time of execution of migration.
|
Note
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.
Describe the definitions carefully, as entry is case-sensitive.
When it corresponds to the following conditions, the operation becomes the same as the case when "true" is specified.
When the definition is omitted
When a value other than true/false is specified
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.
The definition file configurations are reflected without restarting the manager in Resource Orchestrator.
Validation of the auto-boot? change function on migration
When performing VM guest or migration of L-Server from this product, you are advised to saving configuration information automatically by setting the value of auto-boot? to "false" in advance.
When the value of auto-boot? is set as "false" and configuration information is saved automatically on migration, include the definition for validating the function in the following definition files.
By indicating the definition for validating a function, the following processes are automatically performed on migration.
Change the value of auto-boot? into "false" before execution of migration, and save the configuration information.
Return the value of auto-boot? to the original value (true) after execution of migration.
[Windows Manager]
Installation_folder\SVROR\Manager\etc\customize_data
[Linux Manager]
/etc/opt/FJSVrcvmr/customize_data
Information
The sample definition file (sparc_vm.rcxprop.sample) is stored in the location above.
When using the sample as the definition file, delete the ".sample" included in the file name after changing the content.
sparc_vm.rcxprop
UTF-8
[Windows Manager]
CR/LF
[Linux Manager]
LF
In the definition file, an item to define is entered on each line. Each line must be entered in the following format.
Key = Value |
When adding comments, start the line with a number sign ("#").
Specify the following items:
Key | Description |
|---|---|
OVM_SAFE_MIGRATION | Define whether to change the value of auto-boot? to "false" on execution of migration.
|
Note
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.
Describe the definitions carefully, as entry is case-sensitive.
In the following cases, the same operation as when "false" is specified will be performed:
When the definition is omitted
When a value other than true/false is specified
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.
The definition file configurations are reflected without restarting the manager in Resource Orchestrator.
Operation mode definition file for when simultaneously creating multiple L-Servers with a Solaris 11 image specified
When creation of multiple L-Servers with a Solaris 11 image specified is performed by using this product, an error may occur.
It is possible to carry out serial execution of the creation process so that an error does not occur, by indicating the operation for each L-Server in this definition file.
If necessary, edit the definition to change operation mode of the L-Server.
For example, when large numbers of L-Servers need to be created, such as during initial installations, etc., it is recommended to specify "true" for this definition.
[Windows Manager]
Installation_folder\SVROR\Manager\etc\customize_data
[Linux Manager]
/etc/opt/FJSVrcvmr/customize_data
Information
The sample definition file (sparc_vm.rcxprop.sample) is stored in the location above.
When using the sample as the definition file, delete the ".sample" included in the file name after changing the content.
sparc_vm.rcxprop
UTF-8
[Windows Manager]
CR/LF
[Linux Manager]
LF
In the definition file, an item to define is entered on each line. Each line must be entered in the following format.
Key = Value |
When adding comments, start the line with a number sign ("#").
Specify the following items:
Key | Description |
|---|---|
OVM_SOL11_SERIAL_CREATION | Define the operation to be performed when creating multiple L-Servers with a Solaris 11 image specified.
|
Note
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.
Describe the definitions carefully, as entry is case-sensitive.
In the following cases, the same operation as when "false" is specified will be performed:
When the definition is omitted
When a value other than true/false is specified
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.
The definition file configurations are reflected without restarting the manager in Resource Orchestrator.
