Description of problem:
Some of the labeling in the Cluster Configuration page is incorrect. See https://docs.google.com/presentation/d/1-3HWjwCcpeeH9Tq2ip9GggQo0I4koWZtfNcmAfogNA8/edit#slide=id.g11293b91de_0_5 for more details.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Go to Clusters list
2.Select a cluster and view details
3.Click on Configuration tab.
Created attachment 1165742 [details]
What needs to be fixed
The notification and utilization tables (where the problems are identified) are generated from API response data.
As long as we fix them on the backend, they should render fine on the frontend.
Releasing this to be reassigned to backend team.
@Deb, backend api returns field names and values. The labels for the fields are hardcoded in UI code. We need to correct as per suggestion.
Checking with rhscon-ui-0.0.48-1.el7scon.noarch
The cluster Configuration tab now reports the following:
* Cluster Availability (no change needed)
* Host Availability (no change needed)
* Quorum Loss (no change needed)
* Monitor Availability (no change needed)
* OSD Availability (fixed)
Thresholds (here the list of items changed compared to state when
the BZ was reported):
* OSD Utilization (not fixed, see below)
* Storage Utilization not fixed, see below)
* Cluster (fixed)
* Storage Profile (fixed)
* Block Device Utilization (not fixed, see below)
Looking at the description from Matt, I see that he proposed 2 types of changes
for the Thresholds (was Utilization) table:
* fixing typos (such as Osd -> OSD, Cpu -> CPU, Df -> OSD, ...)
* dropping Utilization from the 1st column of the table
(eg. Cluster Utilization -> Cluster)
And while I see that the typos were fixed, I still see word "Utilization"
in the 1st column of few lines in the table. Based on Matt's description,
I would expect that it should not be there.
As per the typos mentioned in the attached screen shot everything is changed. Wherever he asked to remove "Utilization", its removed.
Also Df is not OSD actually. In reality it is Mount Point utilization so named like this.
As such I don't find anything wrong done as part of fix. Not sure if this is really a FailedQA.
When something suggested in UX guidelines its just a guideline and its dev's responsibility to make sure that Df is not replaced with OSD rather it is Mount Point utilization.
These comments are solely mine... and request Nishanth/Matt to comment.
(In reply to Shubhendu Tripathi from comment #9)
> As such I don't find anything wrong done as part of fix. Not sure if this is
> really a FailedQA.
When I look at "what needs to be fixed" image attached to this BZ, I see that
for every line in the table which contains word "Utilization" in the 1st column,
the design team suggested to remove it. This makes me think that the design team
have removing all occurrences of word "Utilization" in mind. So when I see that
there are lines which contains word "Utilization" in the current implementation,
I consider this to be an issue which should be addressed (by removing the word
"Utilization" from affected lines). Moreover I expect that all lines in the table
are about some kind of utilization, so I don't understand why some name there
includes "Utilization" in it's name while some others don't.
This is the only problem I describe in comment 7.
Created attachment 1181925 [details]
The patches https://review.gerrithub.io/#/c/283170/ and https://review.gerrithub.io/#/c/283165/ remove the "Utilization" keyword from the UI.
Order not logical for Utilization
It seems to me, that nothing was done in the regard, the order is not lexicographical nor logical e.g. for logical one I expect to have swap next to memory.
(In reply to Lubos Trilety from comment #16)
> What about:
> Order not logical for Utilization
> It seems to me, that nothing was done in that regard, the order is not
> lexicographical nor logical e.g. for logical one I expect to have swap next
> to memory.
After discussion the order will not be changed.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.