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 by vSphereUpdater.
Table 19-1 Provisioning Actions Supported by the vSphere Provisioning Adapter on Guest Operating Systems
|
Orchestration Server Managed VM Action |
vSphere Provisioning Adapter on Guest OS |
|---|---|
|
Provision |
Yes |
|
Clone |
Yes |
|
Shutdown |
Yes |
|
Destroy |
Yes |
|
Suspend |
Yes |
|
Pause |
No |
|
Resume |
No |
|
Create Template |
Yes |
|
Move Disk Image1 |
Yes |
|
Hot Migrate2 |
Yes |
|
Warm Migrate3 |
Yes |
|
Checkpoint |
Yes |
|
Restore |
Yes |
|
Install Orchestration Agent |
Yes |
|
Make Standalone |
Yes |
|
Check Status |
Yes |
|
Save Config |
Yes |
|
Cancel Action |
Yes |
|
Check Host Assignment |
Yes |
|
Launch Remote Desktop |
Yes |
NOTE:Host operating systems are dependent on the VMware vSphere support matrix
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.