<div dir="ltr"><div>Matt,</div><div><br></div>I don't think it's a bike-shedding. The problem is not the existing name being a bit obscure - until I hit some issues with Keystone native regions I didn't have any troubles with it. The problem is that we have the _same_ name for different things, and no additional comments will remedy the confusion caused by this.</div><br><div class="gmail_quote"><div dir="ltr">On Thu, Jul 9, 2015 at 4:03 AM Matt Fischer <<a href="mailto:matt@mattfischer.com">matt@mattfischer.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Is it really worth it to change the name? I agree the old name is somewhat confusing but the new name is not perfectly clear either and will still require a several line comment to explain what it's trying to do. What could simply be done now is to improve the existing comment in the conf file as well as the docs. This eliminates everyone downstream from you having to change things (puppet/chef/ansible for example). The bike shed really just needs touch-up paint here.</div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jul 8, 2015 at 6:47 PM, David Lyle <span dir="ltr"><<a href="mailto:dklyle0@gmail.com" target="_blank">dklyle0@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><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><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>
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>
<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><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><div>
<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>
<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></blockquote></div><br></div>
__________________________________________________________________________<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>
</blockquote></div>