Open Stack

+1

It is certainly worth a session to decide how to modify the scheduler.

I suspect all you would need is to do on the compute side is add a stub implementations for add/remove host operations in the compute manager base class (rather than throw NotImplemented exceptions), and maybe an extra XenServer specific flag to suppress the pool creation. I think it has all the DB and metadata functionality required.

One thing worth raising, is that currently all hosts in an aggregate must be in the same availability zone. That seems reasonable to me.

From: Vishvananda Ishaya [mailto:vishvananda at gmail.com]
Sent: 03 April 2012 19:11
To: Day, Phil
Cc: John Garbutt; Jan Drake; Lorin Hochstein; openstack at lists.launchpad.net
Subject: Re: [Openstack] Limit flavors to specific hosts


On Apr 3, 2012, at 6:45 AM, Day, Phil wrote:


Hi John,

Maybe the problem with host aggregates is that it too quickly became something that was linked to hypervisor capability, rather than being the more general mechanism of which one form of aggregate could be linked to hypervisor capabilities ?

Should we have a "host aggregates 2.0" session at the Design Summit ?

+ 1

I think the primary use case is associating metadata with groups of hosts that can be interpreted by the scheduler.  Obviously, this same metadata can be used to create pools/etc. in the hypervisor, but we can't forget about the scheduler.  Modifying flags on the hosts for capabilities is ugly.

Vish

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20120403/721501ce/attachment.html>