The grid events for VMs that are implemented by the respective Orchestration Server 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 |
|
|
clone_event |
|
|
move_event |
|
|
start_event |
|
|
shutdown_event |
|
|
restart_event |
|
|
destroy_event |
|
|
suspend_event |
|
|
pause_event |
|
|
resume_event |
|
|
personalize_event |
|
|
saveConfig_event |
|
|
applyConfig_event |
|
|
createTemplate_event |
|
|
migrate_event |
|
|
checkpoint_event |
|
|
restore_event |
|
|
installAgent_event |
|
|
checkStatus_event |
|
|
discoverVmHost_event |
|
|
discoverRepository_event |
|
|
makeStandalone_event |
|
|
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.