Feature #2019
VM hooks and determining from which state is recovering
| Status: | Closed | Start date: | 05/10/2013 | |
|---|---|---|---|---|
| Priority: | Low | Due date: | ||
| Assignee: |  Ruben S. Montero | % Done: | 0% | |
| Category: | Core & System | |||
| Target version: | Release 4.2 | |||
| Resolution: | fixed | Pull request: |
Description
Changing the VM_HOOK definitions by adding a "FROM" attribute, ex.:
VM_HOOK = [
ON = "RUNNING",
FROM = "UNKNOWN"
]
Or passing the previous state as a hook parameter:
VM_HOOK = [
name = "vm_state_change",
on = "RUNNING",
command = "vm_state_change.sh",
arguments = "$ID $PREVSTATE $TEMPLATE"
]
Briefly discussed here: http://www.mail-archive.com/users@lists.opennebula.org/msg10273.html
Associated revisions
feature #2019: Adds PREV_STATE and PREV_LCM_STATE to hook attributes.
feature #2019: Adds PREV_STATE and PREV_LCM_STATE to hook attributes.
(cherry picked from commit 2d102df0c7fa6e457b2fe12ddc4141b0af924939)
History
#1
Updated by Ruben S. Montero about 8 years ago
- Tracker changed from Feature to Backlog
- Priority changed from Normal to Low
#2
Updated by Simon Boulet about 8 years ago
Perhaps using environment variables could be a good idea for hooks instead of using command line parameters.
#3
Updated by Ruben S. Montero about 8 years ago
- Tracker changed from Backlog to Feature
- Category set to Core & System
- Status changed from Pending to New
- Target version set to Release 4.2
As the hooks can be executed remotely (through ssh) it's easier to pass it through the command line arguments. We'll have $PREV_STATE and $PREV_LCM_STATE to get the complete state description.
#4
Updated by Ruben S. Montero about 8 years ago
- Status changed from New to Assigned
- Assignee set to Ruben S. Montero
#5
Updated by Jaime Melis about 8 years ago
- Status changed from Assigned to Closed
- Resolution set to fixed