aling.com>]
Sent: 19 September 2012 19:02
To: Day, Phil
Cc: openstack@lists.launchpad.net<mailto:openstack@lists.launchpad.net>
(openstack@lists.launchpad.net<mailto:openstack@lists.launchpad.net>)
(openstack@lists.launchpad.net<mailto:openstack@lists.launchpad.net>)
Subject
: Re: [Openstack] Generalsied host aggregates in Folsom
On Wed, Sep 19, 2012 at 1:14 PM, Day, Phil
mailto:philip@hp.com>> wrote:
Thanks Joe,
I was anticipating something more complex to be able to say when an aggregate
should or shouldn't be linked to the hypevisor and overlooked
mailto:j...@cloudscaling.com]
> *Sent:* 19 September 2012 19:02
> *To:* Day, Phil
> *Cc:* openstack@lists.launchpad.net (openstack@lists.launchpad.net) (
> openstack@lists.launchpad.net)
> *Subject:* Re: [Openstack] Generalsied host aggregates in Folsom
>
> ** **
>
> **
Re: [Openstack] Generalsied host aggregates in Folsom
On Wed, Sep 19, 2012 at 10:18 AM, Day, Phil
mailto:philip@hp.com>> wrote:
Hi Folks,
Trying to catch-up (I'm thinking of changing my middle name to catch-up :) )
with the generalisation of host aggregates - and looking at the code
On Wed, Sep 19, 2012 at 10:18 AM, Day, Phil 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
Hi Folks,
Trying to catch-up (I'm thinking of changing my middle name to catch-up :) )
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/aggr
6 matches
Mail list logo
