Bug 1866320
| Summary: | [RHOCS Usability Study][Dashboard] Users were confused by Available Capacity and the Total Capacity | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Harish NV Rao <hnallurv> | ||||
| Component: | Console Storage Plugin | Assignee: | Bipul Adhikari <badhikar> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Elena Bondarenko <ebondare> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 4.4 | CC: | aos-bugs, badhikar, bkunal, ebondare, lithomas, nberry, nthomas, ocs-bugs, tdesala | ||||
| Target Milestone: | --- | Keywords: | UsabilityStudyPriority | ||||
| Target Release: | 4.7.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2021-02-24 15:14:01 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Harish NV Rao
2020-08-05 11:08:36 UTC
As of OCS 4.5 release, Total capacity is removed. Shifting this to UX team for further deliberation. we are working on improving that for 4.7 and 4.8 Created attachment 1740310 [details]
Two capacity cards on the dashboard
I retested with 4.7.0-0.nightly-2020-12-18-031435. A new Raw capacity card has been added as described in Comment 4. It is a huge improvement comparing to the initial card. However, my concern is whether the difference between Used in Raw capacity card (3.12 Gib on the scrennshot) and the total of Used Capacity Breakdown card (354 MiB) might also confuse the user and requires some additional explanation. Harish, what do you think? (In reply to Elena Bondarenko from comment #8) > I retested with 4.7.0-0.nightly-2020-12-18-031435. A new Raw capacity card > has been added as described in Comment 4. @Elena, the comment 4 says: "The new card "Raw Capacity Card" shows the following information. The card has textual(enlarged legends) and graphical information(donut chart): Used Capacity (ceph_cluster_total_used_raw_bytes) Total Capacity (ceph_cluster_total_bytes) Available Capacity ( Total - Used )" I don't see Total Capacity in the screenshot of this card. The screenshot shows available capacity as 6 TiB whereas the total capacity is 6 TiB in your case. Right? Can you please check and confirm? > It is a huge improvement comparing to the initial card. However, my concern > is whether the difference between Used in Raw capacity card (3.12 Gib on the > scrennshot) and the total of Used Capacity Breakdown card (354 MiB) might > also confuse the user and requires some additional explanation. > Harish, what do you think? Did you notice the infotip text on "Used Capacity Breakdown card"? Please check if it's useful or not. As per comment 4, the info tip should have mentioned "This card shows the used capacity for Usable storage, broken-down by different kubernetes resources. Usable storage is all the data that can be stored in the system after decreasing the replication policies.". I feel the last sentence could be reworded as "Usable storage is all the storage capacity that is available for actual data storage after applying replication policies". Somehow I feel " decreasing the replication policies" is not conveying right info. I am fine with considering other proposals also. As Bipul has explained during the meeting, the available capacity is shown as 6 TiB because of rounding; when some meaningful amount of data is stored in OCS, it will show a smaller value than the total. The total capacity is shown on the chart, so there's no need to repeat it in the legend. The tootlip is to be re-worded. The new tooltip text hasn't been approved by the ux team yet. I'll open a separate BZ if there is any issue with it. The major work on re-organizing the data representation on capacity usage has been done. 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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:5633 |