AVAILABLE_REGIONS setting name gets confused with regions within Keystone service catalog
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Dashboard (Horizon) |
In Progress
|
Low
|
Timur Sufiev |
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://
Changed in horizon: | |
importance: | Undecided → Low |
Fix proposed to branch: master /review. openstack. org/222131
Review: https:/