4.1 The VMware vSphere Provisioning Adapter

Because you probably want to get your Cloud Manager Orchestration environment configured for use in your vCenter hypervisor environment at installation time, detailed configuration information you need for the vSphere provisioning adapter is included in the Configuring the vsphere Provisioning Adapter in the NetIQ Cloud Manager 2.1.5 Orchestration Installation Guide.

This section includes the following supplementary information about the provisioning adapter:

4.1.1 Provisioning Actions Supported by the vSphere Provisioning Adapter

The following table lists the VM provisioning actions supported by the Orchestration Console for the vsphere provisioning adapter job.

Table 4-1 Provisioning Actions Supported by the vSphere Provisioning Adapter on Guest Operating Systems

Orchestration Server Managed VM Action

SLES 10

SLES 11

RHEL 4

RHEL 5

RHEL 6

Other Linux

Windows 2003 R2

Windows 2008 R2

Provision

X

X

X

X

X

X

X

X

Clone

X

X

X

X

X

X

X

X

Shutdown

X

X

X

X

X

X

X

X

Destroy

X

X

X

X

X

X

X

X

Suspend

X

X

X

X

X

X

X

X

Pause

 

 

 

Resume

 

 

 

Create Template

X

X

X

X

X

X

X

X

Move Disk Image1

X

X

X

X

X

X

X

X

Hot Migrate2

X

X

X

X

X

X

X

X

Warm Migrate3

X

X

X

X

X

X

X

X

Checkpoint

X

X

X

X

X

X

X

X

Restore

X

X

X

X

X

X

X

X

Install Orchestration Agent

X

X

X

X

X

X

X

X

Make Standalone

X

X

X

X

X

X

X

X

Check Status

X

X

X

X

X

X

X

X

Save Config

X

X

X

X

X

X

X

X

Cancel Action

X

X

X

X

X

X

X

X

Check Host Assignment

X

X

X

X

X

X

X

X

Launch Remote Desktop

X

X

X

X

X

X

X

X

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

The VMware vsphere provisioning adapter supports only VMware Virtual Center 2.x. Virtual Center 1.x is not supported.

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 action 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 action 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 action requires shared storage.

4.1.2 Known Configuration Limitations for Virtual Center VMs

When a vSphere VM is deleted by the vSphere client, it can leave behind a VM template in a “defined” state that can be subsequently discovered and registered as a resource in the Orchestration Server.

If you attempt to remove this VM template in the Orchestration Console, the Orchestration Server attempts to remove the VM’s files from the file system, but because the VM has no files to delete, the provisioning job fails with the following error:

Error: Delete : Failed delete of Managed Entity :

For identified vCenter VM issues slated for eventual correction, see the “vSphere VM Issues in the Orchestration Console” section of the NetIQ Cloud Manager 2.0 Readme. For ongoing vCenter VM issues, see Troubleshooting vSphere VM Provisioning Actions in the NetIQ Cloud Manager 2.1.5 Troubleshooting Reference.