openstack team mailing list archive

[Joe Gordon <jogo@xxxxxxxxxxxxxxxx>]

On Wed, Sep 19, 2012 at 10:18 AM, Day, Phil <philip.day@xxxxxx> wrote:

>  Hi Folks,****
>
> ** **
>
> Trying to catch-up  (I’m thinking of changing my middle name to catch-up J
> ) with the generalisation of host aggregates – and looking at the code it
> looks to me as if the chain for adding a host to an aggregate still ends up
> calling the virt layer   ****
>
> ** **
>
> api/openstack/compute/contrib/aggregates/AggregateController/action()****
>
> compute/api/AggregateAPI/add_host_to_aggregate()****
>
> <RPC>****
>
> compute/manager/add_aggregate_host()****
>
> virt/add_to_aggregate()****
>
> ** **
>
> I thought the change was to be able to create aggregates that can be
> linked to a hypervisor concept, but could also just be a way of “tagging”
> hosts into pools for other scheduler reasons – am I missing somethign ?
>

The RPC component is there to ensure XenAPI still works.  In the libvirt
driver, add_to_aggregate() is a noop.

So you can create an aggregate that can be linked to a hypervisor but also
as a way to tag hosts

****
>
> ** **
>
> Thanks,****
>
> Phil****
>
> ** **
>
> ** **
>
> ** **
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>