Comment 7 for bug 1346741
Revision history for this message
| Thiago Martins (martinx) wrote Re: Enable "Stop Instance" button | #7 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Guys,
I just realized one more thing... This new "feature in nova", that is required to make this "Stop button" to work, which is an `ACPI Call` called via libvirt at the Compute Node, needs to be applied to "Terminate button" too!
I mean, currently, the "Terminate button" also does not gracefully shutdown an instance! It simple destroys it.
This is very bad, simple because lots of cloud providers (Like AWS EC2, RackSpace, etc) sends an `ACPI Call` to a instance that is about to be destroyed, this is the only way to trigger the famous "decommissioning scripts" within an instance, that is heavily used by Righscale, for example, and by my company.
The current implementation of Nova (libvirt), make it impossible to decommission an Instance! Because it is just destroyed (not gracefully halted), so, `init 0` is never triggered by the Linux guest S.O..
So, before "Terminate", and delete an Instance, Nova needs to first, send an `ACPI call` to trigger "init 0" on Linux instances, wait about 5 minutes to destroy (and delete) it, then, the decommissioning scripts will work.
Best!
Thiago