yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #22361
[Bug 1373927] Re: Inconsistent usage of "Status" and "State" in System Info panel makes them hard to translate
Hmm..... my previous comment seems wrong.
Anyway consistency is important and the majority of tabs is
to use "Status" columns with "enabled/disabled".
I will swap "status" and "state" in "Network Agents".
** Changed in: horizon
Importance: Medium => Undecided
** Changed in: horizon
Status: New => Invalid
** Changed in: horizon
Assignee: Akihiro Motoki (amotoki) => (unassigned)
--
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/1373927
Title:
Inconsistent usage of "Status" and "State" in System Info panel makes
them hard to translate
Status in OpenStack Dashboard (Horizon):
Invalid
Bug description:
There are columns named "State" and "Status" in "Compute Services", "Volume Services" and "Network Agents" tabs in System Information panel, however the meaning of these two words are inconsistent.
It makes hard to translate them appropriately and needs to assign the same/similar words in translations.
"State" in "Compute Services" and "Volume Services" and "Status" in "Network Agents" are used in the same meaning.
"Status" in "Compute Services" and "Volume Services" and "State" in "Network Agents" are used in the same meaning.
It is very confusing.
At least we need to use consistent terms in System Information Panel.
I would suggest to swap "Status" and "State" in "Network Agents" tab.
This inconsistency comes from inconsistency wording in back-end API (nova/cinder and neutron).
nova and cinder use "status" to indicate "administrative mode" which takes Enabled/Disabled, but Neutron API uses "admin_state_up" in this meaning.
As a long term solution, we need to resolve this kind of API inconsistency among projects.
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1373927/+subscriptions
References