<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">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:<div class=""><ul class=""><li class="">Implement the Regions API discussed back in the Havana time period - <a href="https://etherpad.openstack.org/p/havana-availability-zone-and-region-management" class="">https://etherpad.openstack.org/p/havana-availability-zone-and-region-management</a> - but with full CRUD</li><li class="">Enhance the Endpoints API to allow filtering by region</li></ul><div class="">Supporting two different multi region models is problematic if we’re serious about things like multi-region Heat.</div><div class=""><br class=""></div><div class="">Thoughts?</div><div class=""><br class=""></div><div class="">Geoff</div></div><div class=""><br class=""></div><div class=""><div><blockquote type="cite" class=""><div class="">On May 13, 2015, at 12:01 PM, Geoff Arnold <<a href="mailto:geoff@GEOFFARNOLD.COM" class="">geoff@GEOFFARNOLD.COM</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">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:<br class=""><a href="http://lists.openstack.org/pipermail/openstack/2014-January/004372.html" class="">http://lists.openstack.org/pipermail/openstack/2014-January/004372.html</a><br class="">is the only real discussion I’ve found, and it’s pretty inconclusive.<br class=""><br class="">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?<br class=""><br class="">Yes, I’m being lazy: I could actually configure this to see what happens, but hopefully it was considered during the design.<br class=""><br class="">Geoff<br class=""><br class="">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.<br class=""><br class=""><br class=""><br class="">__________________________________________________________________________<br class="">OpenStack Development Mailing List (not for usage questions)<br class="">Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br class=""></div></blockquote></div><br class=""></div></body></html>