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".
Selecting Disk Data Type for Virtual L-Servers [KVM]
When performing the following operations for a virtual L-Server on RHEL-KVM, the data type to be deleted can be selected.
When the definition file has been edited, restart the manager.
Deleting an L-Server
Detaching L-Server Disks
Deleting Cloning Images
[Windows Manager]
Installation_folder\SVROR\Manager\etc\customize_data
[Linux Manager]
/etc/opt/FJSVrcvmr/customize_data
storage.rcxprop
In the definition file, the items to set are entered on individual lines. Each line is entered in the following format.
Item_specified = Value_specified |
When performing the following operations for a virtual L-Server on RHEL-KVM, the data type to be deleted can be selected.
Deleting an L-Server
Detaching L-Server Disks
Deleting Cloning Images
When the following values are used for specified values.
If "true" is specified
The data of disks is deleted.
If "false" is specified
The data of disks is not deleted.
If nothing is specified
"false" is set.
Example
An example definition file is indicated below.
CLEAN_VM_GUEST_DISK_RESOURCE = true |
Note
When specifying "true" for the specified value, check the following advisory notes.
Operations such as deleting virtual L-Servers on RHEL-KVM will take more time. Operation time changes depending on the number of disks and the disk size.
When starting to delete disks, message 22502 is output in the event log.
While deleting the disk data, the status of disk resource will be "unknown".
When deletion of the data is complete, the message 22503 is output in the event log, and the status of disk resource changes to "normal".
If the deletion of data fails, message 42504 is output in the event log. The status of disk resources will not be changed from "unknown".
Definition File that Configures Resource Sizes to Secure for VM Hosts [KVM]
To configure the size of the resources to be secured for VM hosts, enter the values in the following definition file:
After defining the settings in the definition file, execute the rcxadm vmhostctl command to reflect the description of the definition file on the management information of Resource Orchestrator.
For details on the rcxadm vmhostctl command, refer to "5.26 rcxadm vmhostctl" in the "Reference Guide (Command/XML) CE".
[Windows Manager]
Installation_folder\SVROR\Manager\etc\customize_data
[Linux Manager]
/etc/opt/FJSVrcvmr/customize_data
host_config_RHEL-KVM.rcxprop
Specify the values separated by commas (",") as follows:
ALL, configuration scope, memory size, CPU capacity
Or
Configuration scope type, configuration scope, memory size, CPU capacity
The items to specify are shown below.
When specifying for the entire system
Item | Description | Remarks |
---|---|---|
ALL | The identifier for specifying the entire system | |
Memory size | Setting value
|
|
CPU Capacity | {Value}{Unit}
|
|
When specifying the values by tenant, pool, or physical server
| Description | Remarks |
---|---|---|
Configuration scope type | The identifier for specifying the scope of configuration. The following can be specified:
| |
Setting range | The following can be specified:
| |
Memory size | Set the value in the same way for setting the memory size of the entire system. | |
CPU Capacity | Set the value in the same way for setting the CPU capacity of the entire system. |
Example
An example definition file is indicated below.
ALL,3,10% TENANT,/hoge_FLODER/HOGE_TENANT,4,20% POOL,/hoge/VMPool,3,1core POOL,/TENANT_1/hoge_pool,,20% PHYSICAL_SERVER,bx600_1,1 PHYSICAL_SERVER,bx900_1,4,3core |
Note
About Comment Lines
Lines starting with "#" are regarded as comment lines.
Lines consisting of only blank spaces (" "), tab symbols, and line breaks are also regarded as comment lines.
Comment lines are skipped.
If there are duplicated definitions, the last occurrence will be used.
A KVM host that has not been registered to a VM pool can be specified if the physical server has been specified.
When not defining the memory size, do not define anything between commas (",").
Example
POOL,/VMPool,,3core
When not defining the CPU capacity, do not enter anything at the corresponding part.
Example
POOL,/VMPool,1