On 06/25/2013 02:12 PM, Vishvananda Ishaya wrote: > > On Jun 25, 2013, at 10:38 AM, Andrew Laski <andrew.la...@rackspace.com> wrote: > >> <snip> >> >> You're correct that there's not a large benefit to a deployer unless >> resources are reclaimed. Perhaps some small power savings, and the freedom >> to migrate the instance transparently if desired. I would prefer to remove >> the instance when it's shelved rather than waiting for something, like a >> periodic task or admin api call, to trigger it. But booting disk based >> images can take a fairly long time so I've optimized for the case of an >> instance being shelved for a day or a weekend. That way users get >> acceptable unshelve times for the expected case, and deployers benefit when >> an instance is shelved longer term. I don't think this needs to be set in >> stone and the internal working can be modified as we find ways to improve it. > > We had a lively discussion at the summit about this feature: > > https://etherpad.openstack.org/HavanaMothballServer > > The entire value proposition of this feature is that resources are the same > on unshelve. I don't see any way to do this outside of nova. Also, it bears > mentioning there is room for optimization on the unshelve using something > similar to live-snapshotting [1]. > > Vish > > [1] https://review.openstack.org/#/c/33698/
FWIW, totally agreed that this has to be in nova. -- Russell Bryant _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
