9.1 Grid Events for VMs That Are Implemented by Provisioning Adapters

The grid events for VMs that are implemented by the respective PlateSpin Orchestrate provisioning adapters are shown in the following table. The actual event names use a “pre_” or “post_” suffix, depending on whether it occurs as a pre-event or post-event.

Table 9-1 Grid Events Implemented by Provision Adapters

Event Name

Parameters Passed with the Event

Provisioning Adapters That Support the Event

build_event

  • vm_host

  • vm

  • xen

clone_event

  • vm_host?

  • vm

  • new_vm

  • xen

  • vsphere

move_event

  • vm_host?

  • vm

  • xen

  • vsphere

  • hyperv

start_event

  • vm_host?

  • vm

  • xen

  • vsphere

  • hyperv

shutdown_event

  • vm

  • xen

  • vsphere

  • hyperv

restart_event

  • vm

  • xen

  • vsphere

  • hyperv

destroy_event

  • vm

  • xen

  • vsphere

  • hyperv

suspend_event

  • vm

  • xen

  • vsphere

  • hyperv

pause_event

  • vm

  • xen

  • hyperv

resume_event

  • vm

  • xen

  • hyperv

personalize_event

  • vm

  • xen

  • vsphere

saveConfig_event

  • vm

  • xen

  • vsphere

  • hyperv

applyConfig_event

  • vm

  • xen

createTemplate_event

  • vm_host?

  • vm

  • new_vm

  • xen

  • vsphere

migrate_event

  • vm

  • new_vm_host

  • xen

  • vsphere

  • hyperv

checkpoint_event

  • vm

  • vsphere

  • hyperv

restore_event

  • vm

  • vsphere

  • hyperv

installAgent_event

  • vm

  • xen

checkStatus_event

  • vm

  • xen

  • vsphere

  • hyperv

discoverVmHost_event

  • vm_hosts

  • xen

  • vsphere

  • hyperv

discoverRepository_event

  • repository

  • xen

  • vsphere

  • hyperv

makeStandalone_event

  • vm

  • xen

  • vsphere

NOTE:A vm_host parameter with the (?) annotation signifies that it is passed by the event only if the engine actually has the parameter when the event occurs. If the engine has only a VM but not a VM host, the hooks framework performs an internal lookup for the VM host.