A.3 VMware Virtual Center

The following tables represent the PlateSpin Orchestrate VM actions and whether or not PlateSpin Orchestrate can perform that action on the guest operating system.

IMPORTANT:The PlateSpin Orchestrate Server supports only one VMware Virtual Center server per grid.

Table A-3 PlateSpin Orchestrate VM Actions Supported Guest Operating Systems Using VMware Virtual Center

PlateSpin Orchestrate Managed VM Action

SLES 8

SLES 9

SLES 10

RHEL 4

RHEL 5

Other Linux

Windows

Provision

X

X

X

X

X

X

X

Clone

X

X

X

X

X

X

X

Shutdown

X

X

X

X

X

X

X

Destroy

X

X

X

X

X

X

X

Suspend

X

X

X

X

X

X

X

Pause

Resume

Create Template

X

X

X

X

X

X

X

Move Disk Image 1

X

X

X

X

X

X

X

Hot Migrate 2

X

X

X

X

X

X

X

Warm Migrate 3

X

X

X

X

X

X

X

Checkpoint

X

X

X

X

X

X

X

Restore

X

X

X

X

X

X

X

Install Orchestrate Agent

X

X

X

X

X

X

X

Make Standalone

X

X

X

X

X

X

X

Check Status

X

X

X

X

X

X

X

Save Config

X

X

X

X

X

X

X

Cancel Action

X

X

X

X

X

X

X

Check Host Assignment

X

X

X

X

X

X

X

Launch Remote Desktop

X

X

X

X

X

X

X

NOTE:Host operating systems are dependent on the VMware Virtual Center support matrix.

In the 2.0.2 release of PlateSpin Orchestrate, the VMware Virtual Center Provisioning Adapter supports only VMware Virtual Center 2.x. Virtual Center 1.x is not supported in this release.

1 A “move” is the relocation of VM disk images between two storage devices when the VM is in a not running state (including VMs that are suspended with a checkpoint file). This function does not require shared storage; the move is between separate repositories.

2 A “hot migrate” (also called a “live migrate”) is the migration of a running VM to another host and starting it there with minimal resulting downtime (measured in milliseconds). This function requires shared storage.

3 A “warm migrate” is the migration of a suspended VM to another host and starting it there with brief resulting downtime (measured in seconds). This function requires shared storage.

A.3.1 Additional VMware Virtual Center Provisioning Adapter Information

The vcenterDiscovery.policy file includes fixed paths the to vxpd.exe file:

If you have installed Vcenter in a location other than those listed as default in the policy file, you can copy one of the three existing listelement values, modify the path to point to their installation location for the vpxd.exe process, and then append this new item to the end of the vcenter.path.vpxd list.

For example, if vxpd.exe is installed at D:\foo\bar\VMware\VMware VirtualCenter2.0\vpxd.exe, you could modify the XML policy file as follows: