Bug 1112217

Summary: [RFE] Report clusters capacity
Product: Red Hat Enterprise Virtualization Manager Reporter: Shirly Radco <sradco>
Component: ovirt-engine-reportsAssignee: Shirly Radco <sradco>
Status: CLOSED ERRATA QA Contact: Lukas Svaty <lsvaty>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.4.0CC: audgiri, gklein, iheim, jentrena, khajna, lsvaty, pdwyer, rbalakri, Rhev-m-bugs, sherold, yeylon, ylavi
Target Milestone: ovirt-3.6.0-rcKeywords: FutureFeature
Target Release: 3.6.0Flags: sherold: Triaged+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rhevm-reports-3.6.0-0.0.master.20150602141841.el6ev.noarch.rpm Doc Type: Enhancement
Doc Text:
The Capacity Planning report has been added to Red Hat Enterprise Virtualization 3.6 to track cluster capacity. This report tracks overall cluster allocations and shows details including number of hosts, number of virtual machines (running and configured), number of CPUs (configured, running and physical), memory size (configured, running and physical) including shared memory and ballooning, and storage size (amount allocated and used; configured, running) for defined disks and actual size per disk.
Story Points: ---
Clone Of:
: 1179118 (view as bug list) Environment:
Last Closed: 2016-03-09 21:15:28 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Reports RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1179118, 1257798    
Bug Blocks:    
Attachments:
Description Flags
capacity planing in cluster grouping
none
capacity planing in DC grouping none

Description Shirly Radco 2014-06-23 11:06:04 UTC
Created attachment 911394 [details]
BA reports examples - see first report

Description :

The report will show for each cluster:
- Number of hosts
- Number vms -running and configured
- Number of CPUs - configured , running and physical
- Memory size - configured , running and physical - address shared memory and ballooning
- Storage size - amount allocated, used - configured , running 
(defined disks and actual size per disk)

Comment 1 Shirly Radco 2014-06-25 06:36:46 UTC
*** Bug 1112219 has been marked as a duplicate of this bug. ***

Comment 2 Yaniv Lavi 2014-06-25 06:37:43 UTC
We are passed feature freeze for 3.5, moving to 3.6



Yaniv

Comment 4 Yaniv Lavi 2015-05-31 12:35:56 UTC
I attached the output example of the report. Can you please reach out to the customer for feedback on the report?

Comment 5 Yaniv Lavi 2015-05-31 12:36:51 UTC
Created attachment 1032855 [details]
capacity planing in cluster grouping

Comment 6 Yaniv Lavi 2015-05-31 12:37:29 UTC
Created attachment 1032856 [details]
capacity planing in DC grouping

Comment 7 Karolína Hajná 2015-08-25 12:10:17 UTC
In RHEVM I have the same problem with this report as in oVirt (marked as duplicate). 

The behavior of this report is also quite unpredictable. I added a host to my engine and the report showed that the host has 0 CPUs and 0 RAM. I tried to refresh and relog few times, still the same result. Then the values changed suddenly to 16 CPUs (while the host has 4) and 4 GB of RAM. I would understand that it takes some time to load the new data but in that case there shouldn't be even the correct number of hosts.

When I added two VMs, one running and one turned of, disk section was showing correct data while other sections were not showing any VMs at all. Data in these sections showed after adding a host to new cluster (but still incorrect in some cases). Also there were no VMs on the new host but when I used "Display by cluster" option, it showed number of VMs data from the first cluster.

Comment 8 Yaniv Lavi 2015-08-27 12:51:55 UTC
Please do not fail the RFE and please open separate bug and block this RFE.

Comment 9 Lukas Svaty 2016-01-25 14:40:41 UTC
all the blockers are solved, feature functionality is correct with few minor issues which will be solved with 3.6.3 moving to VERIFIED

Comment 11 errata-xmlrpc 2016-03-09 21:15:28 UTC
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.

https://rhn.redhat.com/errata/RHEA-2016-0425.html