yahoo-eng-team team mailing list archive

[Timur Sufiev <tsufiev@xxxxxxxxxxxx>]

Public bug reported:

Currently 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.

According to the discussion in ML (see
http://lists.openstack.org/pipermail/openstack-
dev/2015-July/068917.html), the name 'AVAILABLE_KEYSTONE_ENDPOINTS' was
chosen as a proper replacement.

** Affects: horizon
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1494251

Title:
  AVAILABLE_REGIONS setting name gets confused with regions within
  Keystone service catalog

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  Currently 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.

  According to the discussion in ML (see
  http://lists.openstack.org/pipermail/openstack-
  dev/2015-July/068917.html), the name 'AVAILABLE_KEYSTONE_ENDPOINTS'
  was chosen as a proper replacement.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1494251/+subscriptions