[openstack-dev] [horizon] [keystone] [docs] Two kinds of 'region' entity: finding better names for them
Fox, Kevin M
Kevin.Fox at pnnl.gov
Wed Jul 8 13:50:17 UTC 2015
In one case horizon uses region to refer to completelely seperate clouds. +1 for coming up with a different term for that concept.
From: Jay Pipes
Sent: Wednesday, July 08, 2015 6:35:22 AM
To: openstack-dev at lists.openstack.org
Subject: Re: [openstack-dev] [horizon] [keystone] [docs] Two kinds of 'region' entity: finding better names for them
On 07/08/2015 08:50 AM, Timur Sufiev wrote:
> 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.
I understand what the Keystone region represents: a simple,
non-geographically-connotated division of the entire OpenStack deployment.
Unfortunately, I don't know what the Horizon regions represent. Could
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev