<div dir="ltr">I have no issue changing the name of AVAILABLE_REGIONS to AVAILABLE_KEYSTONE_ENDPOINTS, however, the old setting will need to go through a deprecation cycle as this is a fundamental setting in Horizon.<div><div><br></div><div>David</div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jul 8, 2015 at 8:07 AM, Jay Pipes <span dir="ltr"><<a href="mailto:jaypipes@gmail.com" target="_blank">jaypipes@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Got it, thanks for the excellent explanation, Timur! Yeah, I think renaming to AVAILABLE_KEYSTONE_ENDPOINTS would be a good solution.<br>
<br>
Best,<br>
-jay<span class=""><br>
<br>
On 07/08/2015 09:53 AM, Timur Sufiev wrote:<br>
</span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
Hi, Jay!<br>
<br>
As Doug said, Horizon regions are just different Keystone endpoints that<br>
Horizon could use to authorize against (and retrieve the whole catalog<br>
from any of them afterwards).<br>
<br>
Another example of how complicated things could be: imagine that Horizon<br>
config has two Keystone endpoints inside AVAILABLE_REGIONS setting,<br>
<a href="http://keystone.europe" rel="noreferrer" target="_blank">http://keystone.europe</a> and <a href="http://keystone.asia" rel="noreferrer" target="_blank">http://keystone.asia</a>, each of them hosting a<br>
different catalog with service endpoint pointing to Europe/Asia located<br>
services. For European Keystone all Europe-based services are marked as<br>
'RegionOne', for Asian Keystone all its Asia-based services are marked<br>
as 'RegionOne'. Then, imagine that each Keystone also has 'RegionTwo'<br>
region, for European Keystone the Asian services are marked so, for<br>
Asian Keystone the opposite is true. One of customers did roughly the<br>
same thing (with both Keystones using common LDAP backend), and<br>
understanding what exactly in Horizon didn't work well was a puzzling<br>
experience.<br>
<br>
On Wed, Jul 8, 2015 at 4:37 PM Jay Pipes <<a href="mailto:jaypipes@gmail.com" target="_blank">jaypipes@gmail.com</a><br></span><div><div class="h5">
<mailto:<a href="mailto:jaypipes@gmail.com" target="_blank">jaypipes@gmail.com</a>>> wrote:<br>
<br>
    On 07/08/2015 08:50 AM, Timur Sufiev wrote:<br>
     > Hello, folks!<br>
     ><br>
     > Somehow it happened that we have 2 different kinds of regions: the<br>
     > service regions inside Keystone catalog and AVAILABLE_REGIONS setting<br>
     > inside Horizon, yet use the same name 'regions' for both of them.<br>
    That<br>
     > creates a lot of confusion when solving some region-related issues at<br>
     > the Horizon/Keystone junction, even explaining what is exactly being<br>
     > broken poses a serious challenge when our common language has<br>
    such a flaw!<br>
     ><br>
     > I propose to invent 2 distinct terms for these entities, so at<br>
    least we<br>
     > won't be terminologically challenged when fixing the related bugs.<br>
<br>
    Hi!<br>
<br>
    I understand what the Keystone region represents: a simple,<br>
    non-geographically-connotated division of the entire OpenStack<br>
    deployment.<br>
<br>
    Unfortunately, I don't know what the Horizon regions represent. Could<br>
    you explain?<br>
<br>
    Best,<br>
    -jay<br>
<br>
    __________________________________________________________________________<br>
    OpenStack Development Mailing List (not for usage questions)<br>
    Unsubscribe:<br>
    <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br></div></div>
    <<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>><br>
    <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><span class=""><br>
<br>
<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
</span></blockquote><div class="HOEnZb"><div class="h5">
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br></div>