Open Stack

IMHO, this seems fit better of the availability since location is more about availability like power supply, network switch availability etc.

Or, what's the boundary of host aggregate and availability zone? Seems host aggregate is so magic that it can cover every requirement to separate/group the host, but also, because it's so magic, it's sure to require some other mechanism to help it to do the real separation/group.

Thanks
--jyh

From: Mike Spreitzer [mailto:mspreitz at us.ibm.com]
Sent: Tuesday, October 01, 2013 6:53 AM
To: OpenStack Development Mailing List
Subject: Re: [openstack-dev] [nova] [scheduler] blueprint for host/hypervisor location information

Maybe the answer is hiding in plain sight: host aggregates.  This is a concept we already have, and it allows identification of arbitrary groupings for arbitrary purposes.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20131002/9e45a258/attachment.html>