The following procedures are required.
When you create Solaris zones on the OVM for SPARC guest domain, consider the guest domain to be a global zone, and design in the same way to create a global zone on a physical server.
Preparation Common to Solaris Zones (Solaris 10)/Solaris Zones (Solaris 11)
Configure the managed servers
When configuring Solaris 11 as the OS of the global zone, configure a guest domain of OVM for SPARC as a server for the global zone.
Installation and configuration of the admin OS
Install and configure the global zone.
When the OS of the global zone is Solaris 10, use UFS as the file system.
Set SSH access permission for the global zone, 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 "Appendix G 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.
If this product is used for managing resources, create a Solaris Zones resource pool for only the non-global zone, and name the Solaris Zones resource pool "pool_resource".
The resource pool name can be changed.
For details, refer to "8.7 Solaris Zones" in the "Setup Guide CE".
It is necessary to enable the target resource pool's service.
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.
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
Preparation for Solaris Zones (Solaris 11)
Define the Repository Server
Decide the repository server used for installing the non-global zone.
Configure the repository server as necessary.
For details on how to configure repository servers, refer to the Solaris manuals.
Pre-configuring Managed Servers (Global Zones)
Configure the Solaris publisher (publisher)
Configure the URI repository server for the Solaris publisher of the global zone.
For details on how to configure the publisher, refer to the Solaris manuals.
When configuring multiple Solaris publishers, the last publisher output by executing the "pkg publisher" command is used for the repository URI of the cloning image.
Example
In the following example, "http://192.168.1.10:16000/" is the URI for the repository.
#pkg publisher <RETURN>PUBLISHER TYPE STATUS P LOCATION solaris origin online F http://192.168.1.10:11000/ solaris origin online F http://192.168.1.10:16000/ |
Register Alternate MAC Addresses
Register alternate MAC addresses for the virtual network device of the guest domain that will be the global zone.
Alternate MAC address registration is necessary for virtual network devices to be used by virtual L-Servers.
Register as many alternate MAC addresses as necessary for the NICs allocated to the virtual network device.
For details on how to register alternate MAC addresses, refer to manual of the server virtualization software (OVM for SPARC).
Preparation for Solaris Zones (Solaris 10)
Install the RSCD Agent
When using the function that needs BMC BladeLogic Server Automation described in "Table 11.6 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".
