Bug 1465795 - Top utilized Resources (Storage) - VMs should be sorted by actual use, not over-allocation percentage
Top utilized Resources (Storage) - VMs should be sorted by actual use, not ov...
Status: ON_QA
Product: ovirt-engine-dashboard
Classification: oVirt
Component: Core (Show other bugs)
unspecified
Unspecified Unspecified
unspecified Severity medium
: ovirt-4.2.0
: ---
Assigned To: Shirly Radco
Pavel Novotny
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-06-28 04:32 EDT by Yaniv Kaul
Modified: 2017-10-26 08:44 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: Metrics
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
rule-engine: ovirt‑4.2+


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
oVirt gerrit 82514 master MERGED dashboards: fix storage.vm_utilization query sorting 2017-10-17 06:35 EDT

  None (edit)
Description Yaniv Kaul 2017-06-28 04:32:59 EDT
Description of problem:
Currently there ordering is by over-allocation percentage. That provides very little value to the customer. The real interesting question is how much space is actually, on disk, occupied by VM or template disk(s).

Version-Release number of selected component (if applicable):
4.1.3
Comment 2 Yaniv Kaul 2017-07-03 07:38:20 EDT
Shirly, please check which query is used and should we use a different one, etc.

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