Feature #2452
Let users control what happens when a VM guest is shutdown
| Status: | Closed | Start date: | 11/12/2013 | |
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assignee: |  Carlos Martín | % Done: | 0% | |
| Category: | Documentation | |||
| Target version: | Release 4.8 | |||
| Resolution: | fixed | Pull request: |
Description
When a VM is shutdown from winthin, OpenNebula changes the VM status to unknown.
But we could add an option similar to ec2's --instance-initiated-shutdown-behavior to let the admin or user decide if the VM should be set to unk, done, or poweroff.
More context in this mailing list thread:
http://lists.opennebula.org/pipermail/users-opennebula.org/2013-October/024773.html
Related issues
Associated revisions
feature #2452: slighlty re-structure of xen_kvm probes to accomodate hypervisor failures
feature #2452: Move lost VMs in hypervisor to power off state
History
#1
Updated by Carlos Martín over 7 years ago
- Related to Request #2069: Synchronize power-off states with hypervisor added
#2
Updated by Ruben S. Montero over 7 years ago
- Tracker changed from Request to Feature
- Status changed from Pending to New
- Target version set to Release 4.6
#3
Updated by Jaime Melis over 7 years ago
- Target version changed from Release 4.6 to Release 4.8
#4
Updated by Jaime Melis about 7 years ago
- Priority changed from Normal to High
#5
Updated by Ruben S. Montero about 7 years ago
This has been implemented as follows:
- A shutdown from the guest will remove the VM from the hypervisor list. In that situation the VM will be moved to POWEROFF. This way the VM state changes are coherent with operations issued from OpenNebula
- On host failures the VMs are moved to unknwon state as this may require admin intervention
#6
Updated by Ruben S. Montero about 7 years ago
- Category changed from Core & System to Documentation
- Assignee set to Carlos Martín
#7
Updated by Carlos Martín almost 7 years ago
- Status changed from New to Closed
- Resolution set to fixed