[openstack-dev] blueprint for 'spare-hosts'

Sam Morrison sorrison at gmail.com
Sun Mar 24 22:50:31 UTC 2013


Hi Matthew,

I think you should be able to do all this with host aggregates?

http://docs.openstack.org/trunk/openstack-compute/admin/content/host-aggregates.html
Note: availability zones are no longer tied to aggregates in Grizzly. The docs need to be updated.


Cheers,
Sam


On 23/03/2013, at 3:27 AM, Matthew Sherborne <msherborne at gmail.com> wrote:

> All comments appreciated.
> 
> https://blueprints.launchpad.net/nova/+spec/spare-hosts
> 
> In summary, when one sets up a nova install, they can set some of the machines to spare.
> 
> Spare means disabled plus the guarantee that there are no customer vms running on there.
> 
> It differs from maintenance mode in that setting a spare that has VMs on it, will just fail, rather than cause a migration.
> 
> Spare machines can be used for quick chassis swaps or can be enabled to receive an emergency migration, or when an end user needs more space than was initially planned.
> 
> Having 'spare' machines in your install a useful safety buffer to let you know when to start adding more.
> 
> https://wiki.openstack.org/wiki/Blueprint-spare-hosts#Possible_later_additions
> 
> ----
> 
> Please comment on implementation ideas, additional features, and perceived usefulness.
> 
> Many Thanks,
> Matthew Sherborne
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130325/d395271f/attachment.html>


More information about the OpenStack-dev mailing list