Bug 1199002

Summary:	[RFE] Provide cpu scheduler/tune information in bulk stats
Product:	Red Hat Enterprise Linux 7	Reporter:	Francesco Romani <fromani>
Component:	libvirt	Assignee:	Peter Krempa <pkrempa>
Status:	CLOSED DUPLICATE	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.0	CC:	dyuan, honzhang, jdenemar, libvirt-maint, mzhan, rbalakri, shyu
Target Milestone:	rc	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:	1191428	Environment:
Last Closed:	2015-03-09 13:29:50 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1191428
Bug Blocks:

Description Francesco Romani 2015-03-05 10:06:51 UTC

+++ This bug was initially created as a clone of Bug #1191428 +++

Description of problem:
To fully replace individual APIs with bulk stats in oVirt, we just lack an equivalent of virDomainGetSchedulerParameters()


Version-Release number of selected component (if applicable):
1.2.12


How reproducible:
100%


Actual results:
No way to get scheduler parameters from bulk stats


Expected results:
new bulk stats group to fetch these stats.


Additional info:
I have a patch in the workings to address this issue, will post for review ASAP

--- Additional comment from Francesco Romani on 2015-02-11 10:32:17 EST ---

Patch posted for review

https://www.redhat.com/archives/libvir-list/2015-February/msg00367.html

Comment 2 Peter Krempa 2015-03-09 13:29:50 UTC

Libvirt already has an event that is called when the tunables change from libvirt's point of view.

Adding information that depend on the configured state doesn't go well with the semantics of the bulk stats api as configuration actually doesn't represent any statistics.

I'm closing this as a duplicate of the bug that introduced the cpu tunables event as that is enough to get the required data.

*** This bug has been marked as a duplicate of bug 1115898 ***