[openstack-dev] [horizon][keystone][heat] Are "AVAILABLE_REGIONS" and multi-region service catalog mutually exclusive?

Geoff Arnold geoff at geoffarnold.com
Wed May 13 21:06:25 UTC 2015


Further digging suggests that we might consider deprecating AVAILABLE_REGIONS in Horizon and enhancing the multi-region support in Keystone. It wouldn’t take a lot; the main points:
Implement the Regions API discussed back in the Havana time period - https://etherpad.openstack.org/p/havana-availability-zone-and-region-management <https://etherpad.openstack.org/p/havana-availability-zone-and-region-management> - but with full CRUD
Enhance the Endpoints API to allow filtering by region
Supporting two different multi region models is problematic if we’re serious about things like multi-region Heat.

Thoughts?

Geoff

> On May 13, 2015, at 12:01 PM, Geoff Arnold <geoff at GEOFFARNOLD.COM> wrote:
> 
> I’m looking at implementing dynamically-configured multi-region support for service federation, and the prior art on multi-region support in Horizon is pretty sketchy. This thread:
> http://lists.openstack.org/pipermail/openstack/2014-January/004372.html
> is the only real discussion I’ve found, and it’s pretty inconclusive.
> 
> More precisely, if I configure a single Horizon with AVAILABLE_REGIONS pointing at two different Keystones with region names “X” and “Y", and each of those Keystones returns a service catalog with multiple regions (“A” and “B” for one, “P”, “Q”, and “R” for the other), what’s Horizon going to do? Or rather, what’s it expected to do?
> 
> Yes, I’m being lazy: I could actually configure this to see what happens, but hopefully it was considered during the design.
> 
> Geoff
> 
> PS I’ve added Heat to the subject, because from a quick read of https://wiki.openstack.org/wiki/Heat/Blueprints/Multi_Region_Support_for_Heat it looks as if Heat won’t support the AVAILABLE_REGIONS model. That seems like an unfortunate disconnect.
> 
> 
> 
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150513/98da09b3/attachment.html>


More information about the OpenStack-dev mailing list