Open Stack

Hi Matthew,
for "spare" compute nodes we are using what Phil said.
The difference that I see in your blueprint is that a "spare host will be guaranteed not to have any VMs".
An this is not true if we disable the nova-compute service.

Instead, couldn't we have a flag in nova that guarantees (or not) this behaviour in disabled compute nodes?

cheers,
Belmiro

On Mar 25, 2013, at 11:19 AM, "Day, Phil" <philip.day at hp.com> wrote:

> Hi Matthew,
>  
> Doesn’t just setting “enable_new_services=False” give you what you want ?   
>  
> We run this on all of our servers so that any newly installed systems can be checked before they are allowed to start hosting Instances.    Couple that with a change we’ve been trying to get through for a while now to add a short text field to the services to capture what they are disabled (https://review.openstack.org/#/c/10877/  ) and you could just set the reason field to “Spare” on the ones you decide not to enable.
>  
> Cheers,
> Phil
>  
> From: Matthew Sherborne [mailto:msherborne at gmail.com] 
> Sent: 22 March 2013 16:28
> To: OpenStack Development Mailing List
> Subject: [openstack-dev] blueprint for 'spare-hosts'
>  
> 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