[openstack-dev] Listing regions and availability zones - Doesn't this belong in Keystone?

John Griffith john.griffith at solidfire.com
Fri Jan 18 19:14:40 UTC 2013

On Fri, Jan 18, 2013 at 11:59 AM, Brian Lamar <brian.lamar at rackspace.com>wrote:

>  Woah there, why are we talking about scaling?
>  I'm not 100% confident in my knowledge of availability zones, but aren't
> they just a lightweight concept that is basically nothing more than a
> property on compute nodes? How does scaling come in to play?
>  IMO AZs seem to be very much nova-centric and that data belongs to Nova
> or *potentially* some sort of orchestration service. The same goes for host
> aggregate groups, which I still very much confuse with AZs.
>  Once again, my terminology may be off but I feel like you're talking
> about cells?
>  Brian
>   On Jan 18, 2013, at 11:10 AM, Jay Pipes <jaypipes at gmail.com> wrote:
> Many installations of Nova (including ours) do not use one giant Nova
> database that stores data for instances in multiple availability zones.
> To scale more effectively, we have a single Nova database for one
> availability zone in a region.
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> FWIW there the same AZ properties are used/required on the Cinder side.
 Personally due to the whole issue of trying to sync things up between the
two projects I think having a central location such as Keystone would make
things much more useful and significantly more robust in the long term.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130118/2a3b0b90/attachment.html>

More information about the OpenStack-dev mailing list