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 Solaris Zones.
Definition Files of Managed Resource Pools for Solaris Zones
In Resource Orchestrator, the resource pool for Solaris Zones, with the name "pool_resource", is the target of management.
When changing the managed resource pools for Solaris Zones, specify either MANAGED_POOL or the admin IP address for the VM host, or both of them, in the definition file in advance.
When MANAGED_POOL and the admin IP address of the VM host are both specified, priority is given to the admin IP address of the VM host.
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
Point
The sample definition file (container_resource.sample.rcxprop) is stored in the storage location above.
When using the sample as the definition file, place the file after deleting the ".sample" included in the file name.
container_resource.rcxprop
In the definition file, an item to define is entered on each line. Each line must be entered in the following format.
Key = Value |
If there is duplicated configuration information for the same VM host, the values that appear first will be used.
Key | Description |
|---|---|
MANAGED_POOL | Specify this item when using common resource pools for Solaris Zones in the overall managed VM host (global zone) in Resource Orchestrator. |
Admin IP address of the VM host | Define a Solaris Zones resource pool for each managed VM host (global zone) in Resource Orchestrator. |
When there are no definitions corresponding to the managed VM host, the resource pool with the name "pool_resource" will be the target of management.
Note
In a Solaris Zone environment, it is necessary to enable the resource pools service corresponding to MANAGED_POOL specified in the definitions.
When definitions are changed during operation, or the name of the resource pool for Solaris Zones is changed, also change the calculation and display of the resource capacity in Resource Orchestrator. Do not change the definitions during operation.
When changing the VM host IP address, also modify the definition files.
When the descriptions start with "#", the string is regarded as a comment line.
Definition Files of Reserved Memory Size for VM Hosts
Define the reserved memory size for the global zone of a Solaris Zone.
When calculating and displaying available memory resources, the reserved memory size for VM hosts specified in this definition file is used.
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 sample definition file (global_zone_reserved_memory.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.
global_zone_reserved_memory.rcxprop
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 the same key is stated in multiple lines, the definition in the line described last is valid.
Specify the following items:
Key | Description |
|---|---|
ALL | Specify the reserved memory size to be used between VM hosts (global_zone) managed by ROR. |
Admin IP address of the VM host | Specify the reserved memory size for the VM host (global_zone) to which the specified IP address has been assigned. |
Note
If this definition is modified during operation, the resource amount calculated and displayed by Resource Orchestrator will be changed as well.
When changing the IP address of the VM host, modify this definition file.
If valid values are not specified in this definition file, it will be treated as if the value for capped-memory configured for the global zone has been specified.
If capped-memory has not been configured for the global zone, it will be treated as if 0 has been specified.
Definition File for SPARC-specific Functions
When using the following functions in Solaris Zones, configure this definition file.
Settings for enabling Solaris Zones
Define if registering VM hosts as Solaris Zones regardless of whether the Logical Domains Manager daemon is enabled or disabled.
This definition is used when registering the agent of a VM host. It has no effect on the types of registered VM hosts.
[Solaris Zones (Solaris 11)]
Configuration of the time-out period of the OS installation process performed during L-Server creation
The time-out period of the OS installation process is set to 6 hours (21600 seconds).
To modify the value of the time-out period from the default, specify the desired time-out period in this definition file.
Configuration of a VM host with "auto" specified for the mac-address property for the anet resource in a non-global zone
When creating an L-Server for the VM host specified in this definition file, "auto" is set for the mac-address property of the anet resource in the non-global zone.
Perform this setting if modification of the MAC address of virtual NIC when restarting the L-Server causes no problems.
[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, place the file after deleting 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. Each line must be entered in the following format.
Key = Value |
When duplicate key values are detected, the process operates based on the last definition detected.
Specify the following items:
Key | Description |
|---|---|
ALWAYS_ZONE | Specify if registering VM hosts as Solaris Zones regardless of whether the Logical Domains Manager daemon is enabled or disabled.
|
ZONE_INSTALL_TIMEOUT | Configure the time-out period for the OS installation process performed when creating an L-Server using seconds. |
ZONE_CHANGEABLE_MAC_HOSTS | When creating an L-Server for the global zone on a virtual server, specify a global zone for which "auto" has been configured for the value for the mac-address property of an anet resource in the non-global zone. Specify an admin LAN IP address of the VM host. Multiple values can be specified by separating each value with a comma (","). Avoid having both non-global zones with "auto" specified and non-global zones with something other than "auto" specified for each global zone at the same time. When this key is specified, the values configured for the properties of the anet resource change as follows:
For details on each property, refer to the manuals for Solaris Zones. |
Example
When registering VM hosts as Solaris Zones regardless of whether the Logical Domains Manager daemon is enabled or disabled
ALWAYS_ZONE=true |
When configuring the time-out period for the OS installation process performed during L-Server creation as 18000 seconds (5 hours)
ZONE_INSTALL_TIMEOUT=18000 |
When creating an L-Server, and specifying two global zones (the admin LAN IP addresses are 192.168.10.10 and 192.168.10.20) to specify "auto" for mac-address in anet
ZONE_CHANGEABLE_MAC_HOSTS=192.168.10.10,192.168.10.20 |
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.
Completion Waiting Time Definition File for the Initial Boot Service [Solaris Zones (Solaris11)]
When creating an L-Server specifying the image to execute the initial boot service, configure this definition file.
When creating an L-Server, after temporarily starting a non-global zone, perform OS customization, and then process the initial boot service. This definition file determines that the initial boot service is completed, if both of the following conditions are satisfied:
The status of the initial boot service configured in the definition file is "disabled"
The property value of the script completion flag configured in the definition file is "true"
Note
When creating an L-Server without configuring the definition file correctly for the image executing the initial boot service, creation of the L-Server may complete before the initial boot service completes. In that case, check if the initial boot service process has completed, by referring to the logs of the initial boot service. If it has not completed, perform corrective action such as executing process again based on the process details of the initial boot service.
Do not use the initial boot service for which the completion flag for Solaris 11.1 or earlier is not configured. When using the service, the process of waiting for completion cannot be performed correctly, and as a result, the process fails due to timeout.
[Windows Manager]
Installation_folder\SVROR\Manager\etc\customize_data
[Linux Manager]
/etc/opt/FJSVrcvmr/customize_data
Information
The definition file sample (sparc_first_boot_service.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.
sparc_first_boot_service.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.
Image_name=Initial_boot_service_name_(FMRI), Property_name_of_script_completion_name |
When duplicate keys are detected, the key operates based on the last definition detected.
Specify the following items:
Key | Description |
|---|---|
Image name | Name of the cloning image to use to create an L-Server. In image names, an asterisk ("*") can be used as a wildcard. Therefore, an asterisk ("*") can be specified as the substitute for an unspecified character string. When there are multiple lines to use, the line closest to the top is used. |
Initial boot service name (FMRI) | Name of the initial boot service executed when using specified images. The name of the service, in FMRI format, included in the package for the initial boot service specified in the image, in ai_manifest.xml. |
Property name of the script completion flag | Property name of the completion flag of the initial boot service. |
Example
When specifying the image name and the initial boot service name as one to one, and also the image name and the property name of the script completion flag as one to one
zone_sol11=svc:/site/first-boot-script-svc:default,config/completed |
When specifying the same initial boot service name and property name of the script completion flag for an image with a name starting with "zone_"
zone_*=svc:/site/first-boot-script-svc:default,config/completed |
When specifying the same initial boot service name and property name of the script completion flag for all images
*=svc:/site/first-boot-script-svc:default,config/completed |
Note
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.
