Red Hat Bugzilla – Bug 1009712
[RFE] [rhevm-reports] Reports should include host shared memory data
Last modified: 2016-02-10 14:40:59 EST
3. What is the nature and description of the request? The customer would like the ability, in rhevm-reports, to see a host's shared memory usage over time (KSM %). 4. Why does the customer need this? (List the business requirements here) This would allow them to gauge the memory overcommit on their hypervisors and decide if additional memory needs to be purchased. 5. How would the customer like to achieve this? (List the functional requirements here) A field in rhevm-reports that shows shared memory % that can be used in an ad-hoc report. 8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)? 10. List any affected packages or components. ovirt-engine-reports ovirt-engine-dwh 11. Would the customer be able to assist in testing this functionality if implemented? Yes
Yaniv, I have opened 1045501 1045502 1045503 to address the other components.
we expose memShared field in getVdsStats, this comes from ksm monitor (self._cif.ksmMonitor.memsharing() * PAGE_SIZE_BYTES). We also grab it in engine's side under VdsStatistics object for each host. Isn't that enough?
(In reply to Yaniv Bronhaim from comment #5) > we expose memShared field in getVdsStats, this comes from ksm monitor > (self._cif.ksmMonitor.memsharing() * PAGE_SIZE_BYTES). > > We also grab it in engine's side under VdsStatistics object for each host. > Isn't that enough? It's good. Yaniv
Still need to add it to ad hoc. Currently added only to history database. Yaniv
Verified on av2.1: rhevm-3.4.0-0.3.master.el6ev.noarch rhevm-dwh-3.4.0-0.4.master.20140224152332.el6ev.noarch rhevm-reports-3.4.0-0.4.master.20140226133324.el6ev.noarch jasperreports-server-pro-5.5.0-8.el6ev.noarch # vdsClient -s 0 getVdsStats | egrep 'ksm|mem' ksmCpu = 0 ksmPages = 100 ksmState = False memAvailable = 1643 memCommitted = 5445 memFree = 7153 memShared = 0 memUsed = '8' $ psql -d engine -c "select ksm_cpu_percent, ksm_pages, ksm_state from vds_statistics;" ksm_cpu_percent | ksm_pages | ksm_state -----------------+-----------+----------- 0 | 100 | f $psql -d ovirt_engine_history -c "select ksm_shared_memory_percent from v3_4_statistics_hosts_resources_usage_samples;" | less -S ksm_shared_memory_percent --------------------------- 0 0 0 0 0 $psql -d ovirt_engine_history -c "select ksm_shared_memory_percent, max_ksm_shared_memory_percent from v3_4_statistics_hosts_resources_usage_hourly;" | less -S ksm_shared_memory_percent | max_ksm_shared_memory_percent ---------------------------+------------------------------- 0 | 0 0 | 0 0 | 0 0 | 0 0 | 0 (5 rows) $psql -d ovirt_engine_history -c "select ksm_shared_memory_percent, max_ksm_shared_memory_percent from v3_4_statistics_hosts_resources_usage_daily;" | less -S ksm_shared_memory_percent | max_ksm_shared_memory_percent ---------------------------+------------------------------- (0 rows)
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. http://rhn.redhat.com/errata/RHEA-2014-0602.html