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:
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