Bug 1009712 - [RFE] [rhevm-reports] Reports should include host shared memory data
[RFE] [rhevm-reports] Reports should include host shared memory data
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-reports (Show other bugs)
Unspecified Unspecified
medium Severity medium
: ---
: 3.4.0
Assigned To: Yaniv Lavi
Barak Dagan
: FutureFeature
Depends On: 1045501 1045502 1045503
  Show dependency treegraph
Reported: 2013-09-18 20:19 EDT by Bryan Yount
Modified: 2016-02-10 14:40 EST (History)
12 users (show)

See Also:
Fixed In Version: ovirt-3.4.0-alpha1
Doc Type: Enhancement
Doc Text:
Red Hat Enterprise Virtualization Reports now includes host shared memory data that can be used in Ad Hoc reports, and accessed via the 'getVdsStats' command.
Story Points: ---
Clone Of:
: 1045501 1045502 1045503 (view as bug list)
Last Closed: 2014-06-09 11:26:21 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: Infra
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
oVirt gerrit 22957 None None None Never
oVirt gerrit 22959 None None None Never

  None (edit)
Description Bryan Yount 2013-09-18 20:19:53 EDT
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.

11. Would the customer be able to assist in testing this functionality if implemented?
Comment 4 Michael Everette 2013-12-20 10:32:32 EST

I have opened 1045501 1045502 1045503 to address the other components.
Comment 5 Yaniv Bronhaim 2013-12-30 02:53:51 EST
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?
Comment 6 Yaniv Lavi 2013-12-30 09:28:09 EST
(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.

Comment 7 Yaniv Lavi 2014-01-05 08:57:00 EST
Still need to add it to ad hoc. Currently added only to history database.

Comment 8 Barak Dagan 2014-03-12 11:55:55 EDT
Verified on av2.1:


# 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


$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)
Comment 9 errata-xmlrpc 2014-06-09 11:26:21 EDT
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.


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