I have dealt with the confusion caused by this issue on multiple
occasions and would love to see AVAILABLE_REGIONS changed to something
like AVAILABLE_KEYSTONE_ENDPOINTS which would be much clearer.
Justin
On 7/8/2015 8:10 AM, Douglas Fish wrote:
Timur Sufiev <[email protected]> wrote on 07/08/2015 07:50:49 AM:
From: Timur Sufiev <[email protected]>
To: "OpenStack Development Mailing List (not for usage questions)"
<[email protected]>
Date: 07/08/2015 07:53 AM
Subject: [openstack-dev] [horizon] [keystone] [docs] Two kinds of
'region' entity: finding better names for them
Hello, folks!
Somehow it happened that we have 2 different kinds of regions: the
service regions inside Keystone catalog and AVAILABLE_REGIONS
setting inside Horizon, yet use the same name 'regions' for both of
them. That creates a lot of confusion when solving some region-
related issues at the Horizon/Keystone junction, even explaining
what is exactly being broken poses a serious challenge when our
common language has such a flaw!
I propose to invent 2 distinct terms for these entities, so at least
we won't be terminologically challenged when fixing the related bugs.
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
[email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Hey Timur, thanks for starting this discussion!
I just had some confusion over this within the last few weeks as well. I
think that Horizon's use of regions to reference service regions in the
keystone catalog is the "correct" usage and the one we should maintain.
AVAILABLE_REGIONS is a Horizon setting that lets you configure multiple
independent keystone endpoints to be known to Horizon.
http://docs.openstack.org/developer/horizon/topics/settings.html
I don't think that's the usual meaning of "Region" in OpenStack, but
Horizon has labelled both the service catalog and multiple keystone related
widgets in the UI as "Regions". I guess we just hope people don't enable
both, or can guess the meaning from the values.
Doug
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
