Open Stack

On 06/18/2013 01:27 PM, Joe Topjian wrote:
> Hi Jay,
>
>     If you have multiple regions and availability zones returning the
>     same service types  -- e.g. compute -- and you point your
>     nova|quantum|cinder|__glanceclient to a Keystone endpoint in one of
>     those zones that is sharing the identity database with other zones,
>     then the Keystone endpoint will return the service catalog for all
>     of the regions and zones. At this point, the X-client will happily
>     go to the first matching service type endpoint for its service type,
>     irrespective of which region or availability zone you actually
>     originally hit.
>
>
> Just a quick note that this is only a problem in Horizon (as of Folsom -
> I haven't verified in Grizzly).
>
> I'm not sure about Availability Zones, but Regions are a bit easier to
> work with in this scenario. All command-line-based tools acknowledge the
> OS_REGION environment variable. If OS_REGION is set, Keystone will
> return the endpoints for the given region.
>
> Horizon, though, will return all endpoints in all regions regardless of
> the region you're in.

If you have multiple zones within a region, however, there is no such 
OS_AVAILABILITY_ZONE env variable to tell the clients which one to go 
to. Instead, you need to manually pass the override --url option to the 
client CLI.

Best,
-jay