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)
*** Bug 1112219 has been marked as a duplicate of this bug. ***
We are passed feature freeze for 3.5, moving to 3.6 Yaniv
I attached the output example of the report. Can you please reach out to the customer for feedback on the report?
Created attachment 1032855 [details] capacity planing in cluster grouping
Created attachment 1032856 [details] capacity planing in DC grouping
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.
Please do not fail the RFE and please open separate bug and block this RFE.
all the blockers are solved, feature functionality is correct with few minor issues which will be solved with 3.6.3 moving to VERIFIED
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