Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Why doesn't suspend release vCPUs/memory?

Per the Openstack documentation, it's implied that both vCPUs and memory are to be released when an instance is successfully suspended. However, when I suspend an instance, neither resources are reclaimed.

Documentation: http://docs.openstack.org/user-guide/content/suspend_resume.html

Administrative users might want to suspend an instance if it is infrequently used or to perform system maintenance. When you suspend an instance, its VM state is stored on disk, all memory is written to disk, and the virtual machine is stopped. Suspending an instance is similar to placing a device in hibernation; memory and vCPUs become available to create other instances.

Releasing resources would be extremely helpful for my situation, which is I have users who have their own instances that they use on demand for a short period of time (basically a lab). The majority of an instance's life is wasted CPU cycles. The only workaround is to create a snapshot, destroy the instance and then re-deploy from the snapshot, but this is both tedious and time consuming...also, in our environment, the services running on the machine will not handle a sudden IP change very gracefully.