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:mspre...@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.
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
