<div dir="ltr">I went forward and filed a bug for this issue (since we agreed that it should be fixed): <a href="https://bugs.launchpad.net/horizon/+bug/1494251">https://bugs.launchpad.net/horizon/+bug/1494251</a><div>The code is already in gerrit (see links in bug), feel free to review.</div></div><br><div class="gmail_quote"><div dir="ltr">On Fri, Jul 10, 2015 at 1:51 AM Douglas Fish <<a href="mailto:drfish@us.ibm.com">drfish@us.ibm.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I think another important question is how to represent this to the user on<br>
the login screen. "Keystone Endpoint:" matches the setting, but seems like<br>
a weird choice to me. Is there a better terminology to use for the label<br>
for this on the login screen?<br>
<br>
I see the related selector has no label at all in the header. Maybe using<br>
the same label there would be a good idea.<br>
<br>
Doug<br>
<br>
Thai Q Tran/Silicon Valley/IBM@IBMUS wrote on 07/08/2015 01:05:53 PM:<br>
<br>
> From: Thai Q Tran/Silicon Valley/IBM@IBMUS<br>
> To: "OpenStack Development Mailing List \(not for usage questions\)"<br>
> <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>><br>
> Date: 07/09/2015 01:17 PM<br>
> Subject: Re: [openstack-dev] [horizon] [keystone] [docs] Two kinds<br>
> of 'region' entity: finding better names for them<br>
><br>
> Had the same issue when I worked on the context selection menu for<br>
> switching domain and project. I think it make sense to rename it to<br>
> AVAILABLE_KEYSTONE_ENDPOINTS. Since it is local_settings.py, its<br>
> going to affect some folks (maybe even break) until they also update<br>
> their setting, something that would have to be done manually.<br>
><br>
> -----Jay Pipes <<a href="mailto:jaypipes@gmail.com" target="_blank">jaypipes@gmail.com</a>> wrote: -----<br>
> To: <a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a><br>
> From: Jay Pipes <<a href="mailto:jaypipes@gmail.com" target="_blank">jaypipes@gmail.com</a>><br>
> Date: 07/08/2015 07:14AM<br>
> Subject: Re: [openstack-dev] [horizon] [keystone] [docs] Two kinds<br>
> of 'region' entity: finding better names for them<br>
<br>
> Got it, thanks for the excellent explanation, Timur! Yeah, I think<br>
> renaming to AVAILABLE_KEYSTONE_ENDPOINTS would be a good solution.<br>
><br>
> Best,<br>
> -jay<br>
><br>
> On 07/08/2015 09:53 AM, Timur Sufiev wrote:<br>
> > Hi, Jay!<br>
> ><br>
> > As Doug said, Horizon regions are just different Keystone endpoints<br>
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<br>
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>
> > <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:<br>
the<br>
> > > service regions inside Keystone catalog and AVAILABLE_REGIONS<br>
setting<br>
> > > inside Horizon, yet use the same name 'regions' for both of<br>
them.<br>
> > That<br>
> > > creates a lot of confusion when solving some<br>
region-relatedissues at<br>
> > > the Horizon/Keystone junction, even explaining what is exactly<br>
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<br>
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.<br>
Could<br>
> > you explain?<br>
> ><br>
> > Best,<br>
> > -jay<br>
> ><br>
> ><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>
> ><br>
<<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><br>
> ><br>
> ><br>
> ><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>
> > <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>
><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>
> <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>
__________________________________________________________________________<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>
> <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>
<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>
</blockquote></div>