The following table lists the VM provisioning actions supported by the Orchestration Console for the vsphere provisioning adapter job.
NOTE:For a list of changes this provisioning adapter detects in the vSphere environment and synchronizes to Cloud Manager, see vSphere Server Changes Synchronized to Cloud Manager.
Table 18-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.
The Cloud Manager vSphere Provisioning Adapter detects changes occurring in the vSphere Server environment and synchronizes many of them to the Cloud Manager Orchestration Server, which then communicates them to the Cloud Manager Application Server and ultimately to the Web console.
The following sections detail the changes that are synchronized.
For information about configuring the provisioning adapter, see Configuring the vSphere Provisioning Adapter
in the NetIQ Cloud Manager 2.3 Installation Guide.
When aspects of unique virtual machines are changed in the vSphere environment, Cloud Manager synchronizes these changes to its interface:
A vDisk is created, modified, or deleted on the VM.
A vNIC is created, modified, or deleted on theVM.
A VM host and its datastore is migrated.
A VM is moved to a new resource pool.
A VM is renamed.
The RAM or CPU is changed on a VM.
When aspects of vSphere repositories are changed, Cloud Manager synchronizes these changes to its interface:
A repository is created, renamed, or deleted.
A repository on a cluster is created, renamed, or deleted.
When aspects of vSphere networks are changed, Cloud Manager synchronizes these changes to its interface:
A network is created, modified, or deleted.
When aspects of vSphere Resource Pool are changed, Cloud Manager synchronizes these changes to its interface:
A VM is moved into or out of the resource pool.
The configuration of a resource pool is changed.