Top
ServerView Resource Orchestrator Cloud Edition V3.1.2 Design Guide
FUJITSU Software

11.1 Deciding Server Virtualization Software

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

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.



Functional Differences Depending on Server Virtualization Software

The functions that can be used differ depending on the server virtualization software.
The required software also differs depending on the server virtualization software used. For details, refer to "2.4.2.4 Required Software".

Table 11.1 Functional Differences Depending on Server Virtualization Software

Function

VMware

(*1)

Hyper-V

(*2)

RHEL-Xen

OVM for x86 2.2

(*3)

RHEL-KVM

Solaris Zones

OVM for SPARC

Citrix XenServer

(*4)

OVM for x86 3.2

Virtual L-Server creation

Yes

Yes

Yes

Yes

Yes

Yes (*5, *6)

Yes (*5)

Yes (*7, *8)

Yes (*7, *8)

Linking and unlinking of configured virtual machines and L-Servers

Yes

Yes

No

No

No

Yes

Yes

Yes

Yes

Importing to L-Platforms (*9)

Yes

Yes

No

No

Yes

Yes

Yes

Yes

Yes

Modification

Modification of specifications and basic information

Yes

Yes

Yes

Yes

Yes

Yes (*5, *6)

Yes (*5)

Yes (*10)

Yes

Attaching and detaching of disks

Yes

Yes

Yes

Yes

Yes

No

Yes (*5)

Yes (*8, *10)

Yes (*8)

Expansion of disk space

Yes

Yes

No

No

No

No

No

No

No

Sharing disks between L-Servers

No

No

Yes (*11)

No

No

No

No

No

No

Modifying network resource settings (*12)

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Addition and deletion of NICs (When the status of an L-Server is "defined")

Yes

Yes

No

Yes

No

Yes

Yes

No

Yes

Addition and deletion of NICs (When the status of an L-Server is "allocated" or "preserved")

Yes

Yes

No

Yes (*13)

Yes

Yes (*13)

Yes (*13)

Yes (*13)

Yes (*13)

Use of the L-Server console

Yes

Yes

No

No

No

No

No

No

No

Deletion of L-Servers

Yes

Yes

Yes

Yes

Yes

Yes (*5, *6)

Yes (*5)

Yes

Yes

Cloning images of Virtual L-Server

Collection, registration, and deletion

Yes

Yes

Yes

Yes

Yes

Yes (*14)

Yes (*14)

Yes

Yes

Display and unregistration

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Snapshot

Collection, deletion, and restoration

Yes

Yes

No

No

Yes (*15)

No

No

Yes (*10)

No

Moving an L-Server between VM hosts (migration)

Yes

Yes

Yes

Yes

Yes

Yes (*5, *6, *16)

Yes (*5)

Yes

Yes

Allocation and release of resources to L-Servers (*17)

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Server switchover

Yes (*18)

Yes (*18)

No

No

Yes

Yes (*19, *20)

No

Yes

No

Dashboard

Pool Conditions

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

System Conditions

Yes

Yes

Yes

No

Yes

Yes

Yes

No

No

Capacity Planning

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes: Supported
Yes (*): Possible when server management software has been registered.
No: Not supported

*1: VMware vCenter Server is necessary to manage VM guests and VM hosts.
*2: The following software is necessary to manage VM guests and VM hosts.

*3: Oracle VM Manager is necessary to manage VM guests and VM hosts.
*4: XenServer 6.0 or later is supported.
*5: BMC BladeLogic Server Automation or BMC BladeLogic Server Automation Console is necessary.
*6: For Solaris 11 Zones, operation and modification is not possible.
*7: Only creation of L-Servers with images specified is supported.
*8: RDM disks cannot be specified.
*9: For the conditions regarding import of L-Platforms, refer to "7.2.3.2 Importing L-Servers" in the "Operation Guide CE".
*10: Operation while an L-Server is powered on is not supported.
*11: For the prerequisites for sharing disks, refer to "17.2.4 Sharing Disks Between L-Servers" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
*12: IP addresses and network resources of virtual L-Servers can only be changed when the server's status is "defined".
*13: NICs cannot be added or deleted. Only NIC definitions can be added or deleted.
*14: Only the registration function is available.
*15: Only supported in NAS environments.
*16: This function is in an exclusive relationship with server switchover.
*17: The values in the definition files used when a configured virtual machine and an L-Server were linked will be imported to the L-Server.
*18: When using the VIOM server profile switchover method, ServerView Virtual-IO Manager is necessary.
*19: When using the storage affinity switchover method, ETERNUS SF Storage Cruiser is necessary.
*20: This function is in an exclusive relationship with moving an L-Server between VM hosts (migration).


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.2 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

OVM for x86 2.2 Functions

Solaris Zone Function

OVM for SPARC Function

Citrix XenServer Functions

OVM for x86 3.2 Functions

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

BladeLogic System Package

Template

Template

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

-

Snapshot

-

-

-

Snapshot

-

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

-

-

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

Migration

Migration

Migration

Refer to "17.7 Migration between VM Hosts" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".

Overcommit (CPU)

Reservation / Limit / Shares

Reservation / Limit / Virtual Quantity of VMs

-

Yes

-

Yes

Yes

Yes

Yes

[VMware]
Refer to "C.2.11 Overcommit" in the "Setup Guide CE".

[Hyper-V]
Refer to "C.3.11 Overcommit" in the "Setup Guide CE".

[KVM]
Refer to "C.6.10 Overcommit" in the "Setup Guide CE".

[Solaris Zones]
Refer to "C.7.9 Overcommit" in the "Setup Guide CE".

[OVM for SPARC]
Refer to "C.8.9 Overcommit" in the "Setup Guide CE".

[Citrix Xen]
Refer to "C.9.11 Overcommit" in the "Setup Guide CE".

[OVM for x86 3.2]
Refer to "C.10.11 Overcommit" in the "Setup Guide CE".

Overcommit (memory)

Reservation / Limit / Shares

Dynamic Memory

-

Yes

-

Yes

Yes

Yes

Yes

[VMware]
Refer to "C.2.11 Overcommit" in the "Setup Guide CE".

[Hyper-V]
Refer to "C.3.11 Overcommit" in the "Setup Guide CE".

[KVM]
Refer to "C.6.10 Overcommit" in the "Setup Guide CE".

[Solaris Zones]
Refer to "C.7.9 Overcommit" in the "Setup Guide CE".

[OVM for SPARC]
Refer to "C.8.9 Overcommit" in the "Setup Guide CE".

[Citrix Xen]
Refer to "C.9.11 Overcommit" in the "Setup Guide CE".

[OVM for x86 3.2]
Refer to "C.10.11 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

Yes

Located on a server pool for which HA is enabled

Located on a server pool for which HA is enabled

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

-

-

Allocation of qcow2 sparse files

-

-

-

-

(*1)

Sparse allocation

Refer to "10.1.1 Allocating Storage".

L-Server Console

Virtual Machine Console in the vSphere Web Client/VMware Remote Console Plug-in

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

*1: The settings of thin provisioning cannot be set from this product. The actual setting of thin provisioning follows the setting of storage repository (SR) of XenServer.


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.3 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
VMware vSphere 5.1
VMware vSphere 5.5

Virtual switches other than VMware standard functions
(Cisco Nexus 1000V, etc. are not supported)

VMware vSphere 5.5

vSphere Flash Read Cache

Microsoft(R) System Center Virtual Machine Manager 2008 R2
Microsoft(R) System Center 2012 Virtual Machine Manager
Microsoft(R) System Center 2012 R2 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.