Re: [ovirt-devel] Killing XMLRPC on master

Wasn't polling for stats removed? I thought we send more using events than just VM status. Martin On Mon, Jun 20, 2016 at 11:48 AM, Piotr Kliczewski <pkliczew(a)redhat.com&gt; wrote: > > > On Mon, Jun 20, 2016 at 11:43 AM, Martin Sivak <msivak(a)redhat.com&gt; wrote: >> >> > Won't we miss all mom's smart policy if we do that? >> >> - Mom uses getAllVmStats (and one or two others) for stats collection >> and it polls for those atm. We can avoid that in the broker mode (VDSM >> sends the stats to the engine and we can listen). > > > >> >> - Engine sends mom configuration through VDSM, but VDSM only converts >> that to different format and forwards that to MOM. This can be >> processed directly in MOM if VDSM knows how to ignore calls that are >> not relevant for it. >> >> We will have to call VDSM to set values, but that should be still >> possible. >> >> Martin >> >> On Mon, Jun 20, 2016 at 11:05 AM, Dan Kenigsberg <danken(a)redhat.com&gt; >> wrote: >> > On Mon, Jun 20, 2016 at 10:33:19AM +0200, Martin Sivak wrote: >> >> > 1. Mom is still using xmlrpc >> >> > >> >> > Mom must move to jsonrpc. >> >> > Martin: can you update on progress of this work? >> >> >> >> We would like to avoid going through VDSM completely, except from the >> >> broker part. Is it possible now to "parasitically" listen to vdsm >> >> events and engine commands without having to go through VDSM API? >> >> >> >> You can drop XML RPC,. vdsm does not depend on MOM working anymore. >> >> Just the balloon and ksm stats will be missing from data that are >> >> being sent to the engine. >> > >> > Won't we miss all mom's smart policy if we do that? >> >> >> >> >> >> There also were some issues with eventfd in the json library, I assume >> >> those are fixed now. >> >> >> >> Martin > >