11.1 Deciding Server Virtualization Software

This section explains how to decide the settings for server virtualization software.

Select the server virtualization software to use
Select the server virtualization software.
Resource Orchestrator can perform resource management using the server virtualization software indicated below.
- VMware
- Hyper-V
- RHEL5-Xen
- RHEL-KVM
- Oracle VM
- Solaris Containers

Settings differ according to the server virtualization software being used.

When using server virtualization software, refer to "Appendix E Preparations for Creating a Virtual L-Server".

Note

When registering managed servers to the manager, the password for the administrative privilege user of the managed server is required.
Configure the password for the administrator account of managed server in advance.

Resource Orchestrator Functions Enabled with the Functions of Each Server Virtualization Software

The Resource Orchestrator functions enabled by using the functions of each server virtualization software are indicated below.

Table 11.1 List of Resource Orchestrator Functions Enabled by Using Each Server Virtualization Function
Resource Orchestrator Function	VMware Function	Hyper-V Function	RHEL5-Xen Function	RHEL-KVM Function	Oracle VM Function	Solaris Containers Function	Reference
L-Server power operations	VM guest power operations						Refer to "17.1 Power Operations" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
L-Server cloning image	Template		Yes	Yes	Template	BladeLogic Virtual Guest Package	Refer to the setup section for the server virtualization software to use in "Appendix E Preparations for Creating a Virtual L-Server".
L-Server snapshots	Snapshot	Checkpoints	-	-	-	-	Refer to "17.6 Snapshots, and Backup and Restoration of L-Servers" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
VM host maintenance mode	Maintenance mode		-	-	Maintenance mode	-	Refer to "15.2 VM Maintenance Mode of VM Hosts" in the "User's Guide VE".
Moving an L-Server between VM hosts (migration)	Migration	Migration using clusters	Migration			Yes	Refer to "17.7 Migration of VM Hosts between Servers" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Overcommit (CPU)	Reservation / Limit / Shares	Reservation / Limit / Virtual Quantity of VMs	-	Yes	-	Yes	[VMware] Refer to "C.2.11 Overcommit" in the "Setup Guide CE". [Hyper-V] Refer to "C.3.12 Overcommit" in the "Setup Guide CE". [RHEL-KVM] Refer to "C.6.10 Overcommit" in the "Setup Guide CE". [Solaris Containers] Refer to "C.7.9 Overcommit" in the "Setup Guide CE".
Overcommit (memory)	Reservation / Limit / Shares	Dynamic Memory	-	Yes	-	Yes	[VMware] Refer to "C.2.11 Overcommit" in the "Setup Guide CE". [Hyper-V] Refer to "C.3.12 Overcommit" in the "Setup Guide CE". [RHEL-KVM] Refer to "C.6.10 Overcommit" in the "Setup Guide CE". [Solaris Containers] Refer to "C.7.9 Overcommit" in the "Setup Guide CE".
Server Recovery	Located on a cluster for which VMware HA is enabled	Located on the MSFC	-	-	Located on a server pool for which HA is enabled	Yes	Refer to "16.3.2 [Server] Tab" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Alive Monitoring	VMware HA Cluster VM and Application Monitoring	MSFC Heartbeat	-	-	-	-	Refer to "16.3.2 [Server] Tab" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Thin Provisioning	Thin Provisioning	-	-	-	-	-	Refer to "10.1.1 Allocating Storage".
L-Server Console	Virtual Machine Console in the vSphere Web Client	Virtual Machine Console in the SCVMM Administrator Console	-	-	-	-	For details, refer to "17.3 Using the L-Server Console" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".

Function name: Function name used in Resource Orchestrator
Yes: Function provided without using server virtualization software function
-: Function not provided in Resource Orchestrator

Functions of Each Server Virtualization Software That Must Not Be Directly Used / Operated

The functions of each server virtualization software that must not be directly used/operated are indicated below.

Table 11.2 List of Functions of Each Server Virtualization Software That Must Not Be Directly Used/Operated
Server Virtualization Software	Functions with no Support of Combined Use
VMware vSphere 4.0 VMware vSphere 4.1 VMware vSphere 5.0	Cisco Nexus 1000V virtual switch
Microsoft(R) System Center Virtual Machine Manager 2008 R2 Microsoft(R) System Center 2012 Virtual Machine Manager	Movement of storage areas Movement changing the virtual machine storage destination Saving in the virtual machine library

[Hyper-V]
VMware ESX and Citrix(R) XenServer(TM) can be managed by SCVMM, but only VM hosts for Hyper-V can be managed when using SCVMM in Resource Orchestrator.