This section describes the different definition files for server virtualization software, when configuring server virtualization software as managed servers.
Definition Files for Enabling Solaris Zones [Solaris Zones] [OVM for SPARC]
Define if registering VM hosts as Solaris Zones regardless of whether the Logical Domains Manager daemon is enabled or disabled.
These definitions are used for registering agents of VM hosts. The types of already registered VM hosts are not affected.
[Windows Manager]
Installation_folder\SVROR\Manager\etc\customize_data
[Linux Manager]
/etc/opt/FJSVrcvmr/customize_data
Information
In the storage location above, the sample definition file (sparc_vm.rcxprop.sample) is stored.
When using the sample as the definition file, delete the ".sample" included in the file name.
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. Enter each line in the following format.
Key = Value |
One of the following items can be specified.
Key | Description |
---|---|
ALWAYS_ZONE | Specify if registering VM hosts as Solaris Zones regardless of whether the Logical Domains Manager daemon is enabled or disabled.
|
Example
When registering VM hosts as Solaris Zones regardless of whether the Logical Domains Manager daemon is enabled or disabled
ALWAYS_ZONE=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.
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 Files for Saving of VM Guest Configurations [OVM for SPARC]
Define whether to automatically save VM guest configurations when there is a change made to VM guest configurations.
This definition is applied to all VM hosts.
The target operation is as follows:
When the following operations are performed from Resource Orchestrator
Power control of VM guests (ON/OFF/OFF(Forced)/Reboot/Reboot(Forced))
When the following operations are performed from the control domain
Creation/deletion of guest domains
Binding/unbinding of resources
Starting/stopping of guest domains
Modification of VCPU numbers and memory sizes of guest domains
Adding/removal of Virtual disks to guest domains
Migration of guest domains
[Windows Manager]
Installation_folder\SVROR\Manager\etc\customize_data
[Linux Manager]
/etc/opt/FJSVrcvmr/customize_data
Information
In the storage location above, the sample definition file (sparc_vm.rcxprop.sample) is stored.
When using the sample as the definition file, delete the ".sample" included in the file name.
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. Enter each line in the following format.
Key = Value |
When adding comments, start the line with a number sign ("#").
One of the following items can be specified.
Key | Description |
---|---|
OVM_AUTO_SAVE_CONFIG | Specify whether to save VM guest configurations.
|
Example
When saving VM guest configurations
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.
Under the following conditions, operation becomes the same as when "true" is specified.
When a definition is omitted
When value other than "true" and "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.