[one-users] [RFC] Release 1.4 - Support for hooks

[Javier Fontan]

Support for hooks
=================

This new feature will allow you to program the execution of predefined  
commands or actions when a given event occurs. This functionality can  
be used to implement several "advance" features, e.g:
  * Synchronize the scheduler with the Core
  * Perform custom configuration operations
  * Define a specific behavior in case of failure
  * ...

The Hooks can be specified system-wide for all the VMs (in oned.conf),  
or for an specific VM in its template. A hook is defined by
  HOOK = [
    EVENT  = <VM_STATE>,
    ACTION = <pre-defined action | command>
    ARGUMENTS = [for command actions]
    TYPE   = <local | remote>
  ]

  EVENT: The event that will trigger the execution of the hook. The  
events are VM states (BOOT,RUNNING...)
  ACTION: pre-defined actions will include restart and destroy.  
Commands will be generic programs specified by its path
  ARGUMENTS: for the command, the user will be able to specify VM  
attributes like $NAME, $NIC[IP], $VMID
  TYPE: local, to be executed in the front-end or remote to be execute  
on the host where the VM is allocated.

Please send your comments and thoughts to the mailing list or in the  
following
ticket:
http://trac.opennebula.org/ticket/15

-- 
Javier Fontan, Grid & Virtualization Technology Engineer/Researcher
DSA Research Group: http://dsa-research.org
Globus GridWay Metascheduler: http://www.GridWay.org
OpenNebula Virtual Infrastructure Engine: http://www.OpenNebula.org