Bug 1102046

Summary:	[RFE] vdsm should get guest data from qemu-ga
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Jiri Belka <jbelka>
Component:	vdsm	Assignee:	Nobody <nobody>
Status:	CLOSED WONTFIX	QA Contact:	meital avital <mavital>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	bazulay, gklein, iheim, lpeer, michal.skrivanek, yeylon
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	virt
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-05-29 08:35:01 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:	1101915
Bug Blocks:

Description Jiri Belka 2014-05-28 11:45:53 UTC

Description of problem:
we have qemu-ga, which can do some things. i made a RFE https://bugzilla.redhat.com/show_bug.cgi?id=1101915 to request qemu-ga reporting memory statistics. as qemu-ga is main agent (generally) for virtualized guests then it would make sense to exploit its usage (fyi ovirt-guest-agent already depends on it).

so... my point:

- qemu-ga should report most of the data (cpu, ip..., memory, hostname..., some of them already are reported)
- ovirt-guest-agent should do all those fancy enterprise things (SSO...)

benefits:

- community focus on qemu-ga
- ovirt focus on fancy enterprise features of ovirt-guest-agent

setting depends on https://bugzilla.redhat.com/show_bug.cgi?id=1101915 as more work should be done on qemu-ga before switching main data provider.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Michal Skrivanek 2014-05-29 08:35:01 UTC

currently ovirt GA allows us greater flexibility in adding/tweaking things. Not considering switching to qemu-ga in foreseeable future. It doesn't report anything yet nor it is properly supported on platforms ovirtGA is

We may reconsider once qemu-ga is more mature, but requiring 2 agents running is always less preferred than having only one