[Openstack] Limit flavors to specific hosts

Lorin Hochstein lorin at nimbisservices.com
Mon Apr 2 19:04:54 UTC 2012


Phil:

I don't know of a way to do this in Essex. However, when I was working at ISI, we added a configuration option called "extra_node_capabilities" that allows you to specify the capabilities of a particular host in the /etc/nova/nova.conf, and these capabilities are checked against the extra_specs. 

See the following lines of code in ISI's repo:

https://github.com/usc-isi/nova/blob/hpc-trunk/nova/virt/libvirt/connection.py#L163
https://github.com/usc-isi/nova/blob/hpc-trunk/nova/virt/libvirt/connection.py#L2669

I don't know how much reporting of capabilities has changed from diablo to essex, though, so no clue if that code would still work if ported to the current trunk.

Take care,

Lorin
--
Lorin Hochstein
Lead Architect - Cloud Services
Nimbis Services, Inc.
www.nimbisservices.com





On Apr 2, 2012, at 1:36 PM, Day, Phil wrote:

> Hi Folks,
>  
> I’m looking for a capability to limit some flavours to some hosts.  I want the mapping to be as flexible as possible, and work within a zone/cell  (I don’t want to add zones just to get this mapping).    For example I want to express something like:
>  
> Host_1 supports flavours A, C
> Host_2 supports flavours A, B
> Host_3 supports flavours A, B, C
> Host_4 supports flavours D
>  
> Ideally there would be some form of grouping to sets of flavours:
>  
> Flavour_A  is part of Flavour_Sets 1, 2, 3
> Flavour_B is part of Flavour_Sets 2, 3
> Flavour_C is part of Flavour_Sets 1, 3, 4
>  
> Host_1 supports flavour Set 1
> Host_2 supports flavour Set 2
> Host_3 supports flavour Set 3
> Host_4 supports flavour Set 4
>  
>  
> From the Essex design summit I thought that host aggregates was going to give this sort of capability, but having looked through the code that seems to be quite tightly coupled with specific hypervisor functionality, whereas this is purely a scheduler feature.
>  
> I can see that I could define flavour group membership through the instanace_type_extra_specs, but not how to then associate these with specific hosts. 
>  
> I know I’m a tad behind some of the recent changes – so before suggesting a design summit session on this I thought I’d ask - is there something that already does this type of mapping ?
>  
> Cheers,
> Phil
>  
>  
>  
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack at lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20120402/5a7d67f9/attachment.html>


More information about the Openstack mailing list