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

Brian Lamar brian.lamar at rackspace.com
Fri Jan 18 18:59:39 UTC 2013

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?


On Jan 18, 2013, at 11:10 AM, Jay Pipes <jaypipes at gmail.com<mailto: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.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130118/75bf0ac1/attachment.html>

More information about the OpenStack-dev mailing list