Bug 1402007 - Dashboard: Over commit: XX% (allocated XX%) parameters are not clear
Summary: Dashboard: Over commit: XX% (allocated XX%) parameters are not clear
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine-dashboard
Classification: oVirt
Component: General
Version: unspecified
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ovirt-4.2.1
: ---
Assignee: Scott Dickerson
QA Contact: Pavel Novotny
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-06 14:54 UTC by Shira Maximov
Modified: 2018-02-12 11:47 UTC (History)
4 users (show)

Fixed In Version: ovirt-engine-dashboard-1.2.1-1
Clone Of:
Environment:
Last Closed: 2018-02-12 11:47:35 UTC
oVirt Team: UX
Embargoed:
rule-engine: ovirt-4.2+


Attachments (Terms of Use)
screen: Dashboard - utilization card text & tooltip improved (23.21 KB, image/png)
2018-01-19 16:40 UTC, Pavel Novotny
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 84979 0 master MERGED Better text and tooltip for utilization virtual resource allocation 2021-02-04 09:28:15 UTC
oVirt gerrit 86322 0 ovirt-engine-dashboard-1.2 MERGED Better text and tooltip for utilization virtual resource allocation 2021-02-04 09:28:15 UTC

Description Shira Maximov 2016-12-06 14:54:02 UTC
Description of problem:
In the Dashboard we can find this parameters: Over commit: 11% (allocated 33%)
in CPU/Memory/Storage.
This parameters are not clear- what's their meaning and how they are calculated. 

This parameters should be more clear,
we can choose better titles / add a tooltip to show the calculation or rethink if we need all this values. 

Version-Release number of selected component (if applicable):
oVirt Engine Version: 4.1.0-0.0.master.20161120231325.gitba51756.el7.centos

Comment 1 Oved Ourfali 2016-12-11 13:01:29 UTC
Moran - any thoughts on that?

Comment 2 Moran Goldboim 2017-01-02 12:57:16 UTC
(In reply to Oved Ourfali from comment #1)
> Moran - any thoughts on that?

yes, the requirements are listed on the requirement doc.
over commit - should represent the pysical resources allocated for running vms.
allocated - is the total physical resources allocated in the system for vms running or not- how much physical resources will be used if we'll run all the vms in the system.
the one thing that might be misleading here is the use of "overcommit" when there isn't actually resources overcommitment. 
we should probably change the use of it to virtualized resources committed and allocated.

thoughts?

Comment 3 Oved Ourfali 2017-01-11 09:58:04 UTC
Can you phrase something to be put on tooltip?

Comment 4 Moran Goldboim 2017-02-05 18:29:56 UTC
(In reply to Oved Ourfali from comment #3)
> Can you phrase something to be put on tooltip?

I can suggest:
Virtual resources - Committed: XXX% Allocated: XXX%

I think it would make more sense.

Comment 5 Scott Dickerson 2017-12-01 07:50:52 UTC
I updated the display text on the global utilization cards as suggested.  I also added a tooltip as originally suggested in the requirements doc.

The tooltip currently reads, "The committed and allocated virtual resources are percentages indicating the running virtual resource compared to actual resources."

Comment 6 Pavel Novotny 2018-01-19 16:39:33 UTC
Verified in
ovirt-engine-4.2.1.2-0.1.el7.noarch
ovirt-engine-dashboard-1.2.1-1.el7ev.noarch

The bottom text on each utilization card is now "Virtual resources - Committed: X%, Allocated: Y%".
Hovering over it shows tooltip with text
"The committed and allocated virtual resources are percentages indicating the running virtual resource compared to actual resources.".
See attached screenshot.

Comment 7 Pavel Novotny 2018-01-19 16:40:26 UTC
Created attachment 1383500 [details]
screen: Dashboard - utilization card text & tooltip improved

Comment 8 Sandro Bonazzola 2018-02-12 11:47:35 UTC
This bugzilla is included in oVirt 4.2.1 release, published on Feb 12th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.1 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.