The following procedures are required.
When you construct the Solaris zones on the guest domain, please consider the guest domain to be a global zone, and design as well as the case to construct a global zone on a physical server.
Installation and configuration of the admin OS
Install and configure the global zone.
When the OS of a VM host is Solaris10, use UFS as the file system.
Set SSH access permission, and enable password authentication for accounts with administrator privileges.
When mounting a pool on a system, resources are classified using their settings.
Create pools with configurations that give consideration to operation with reduced hardware.
This configuration is necessary to obtain information of Virtual L-Servers and VM guests and perform power operation of them.
When the Logical Domains Manager daemon is enabled, VM hosts can be registered as Solaris Zones by configuring the definition files. For details, refer to "Chapter 8 Creating Definition Files" in the "Setup Guide CE".
Create the Solaris Zone resource pool
Create the Solaris Zone resource pool for the global zone and the non-global zone.
The resource pools of Solaris Zones are referred to as Solaris Zone resource pools.
If this product is used for managing resources, create a resource pool for the non-global zone only, and name the resource pool "pool_resource".
The resource pool name can be changed.
For details, refer to "C.7 Solaris Zones" in the "Setup Guide CE".
Set the capping of CPU and capping of the memory for the non-global zone
Already created non-global zones will be the target of resource management when the capping value is set.
The capping supported with this product is as follows.
CPU capping
zone.cpu-cap
Memory capping
rcapd
This product does not show the capping value applied to the running non-global zone (using the prctl command) but configuration information of the non-global zone.
Therefore set the zone.cpu-cap using the zonecfg command.
Design capping values based on the estimated resource usage of a non-global zone.
When the non-global zone uses resources beyond capping, it will have impact on system performance.
Please refer to the relevant version of the document, referring to the following URL:
Oracle corporation
URL: http://www.oracle.com/index.html |
When the non-global zone is the target of resource management, the amount of resources of this product is calculated as follows:
CPU capping
Number of CPUs = capping of CPUs / 100 (if there is a decimal value, round it up)
CPU performance = (capping of CPUs / (number of CPUs * 100)) * performance of physical CPUs(GHz)
Example
When capping of CPUs is 720 and performance of physical CPUs is 3.0GHz
Number of CPUs = 720 / 100 (rounded up) = 8
CPU performance = (720 / (8 * 100)) * 3.0 = 2.7(GHz)
Memory capping
Capping of memory resources
Install the RSCD agent
When using the function which needs BMC BladeLogic Server Automation described in "Table 11.1 Functional Differences Depending on Server Virtualization Software" in "11.1 Deciding Server Virtualization Software", do so using the following procedure.
Install the RSCD agent.
Enable control of the global zone of the RSCD agent.
Add the managed server to BladeLogic.
At this time, specify the IP address of the managed server when adding it.
For details, contact Fujitsu technical staff.
Pre-configuration of Server Management Software
When coordinating with BMC BladeLogic Server Automation, register BMC BladeLogic Server Automation in Resource Orchestrator as server management software. Perform pre-configuration before registration.
For details on pre-configuration, refer to "H.1 Coordination with BMC BladeLogic Server Automation" in the "Setup Guide CE".
