<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jun 20, 2016 at 12:11 PM, Martin Sivak <span dir="ltr"><<a href="mailto:msivak@redhat.com" target="_blank">msivak@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">> We do not support this mode but with some work we could trigger an event<br>
> containing this information so mom can register to get it.<br>
<br>
</span>Wasn't polling for stats removed? I thought we send more using events<br>
than just VM status.<br>
<span class="HOEnZb"><font color="#888888"><br></font></span></blockquote><div><br></div><div>We send only vm status changes and small bunch of additional data that Francesco added.<br></div><div>They are not one to one replacement. If there amount of data is good enough for mom than<br></div><div>it is enough to register for this event.<br><br></div><div>The engine still calls to get all vm stats every 15 seconds.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="HOEnZb"><font color="#888888">
Martin<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
On Mon, Jun 20, 2016 at 11:48 AM, Piotr Kliczewski <<a href="mailto:pkliczew@redhat.com">pkliczew@redhat.com</a>> wrote:<br>
><br>
><br>
> On Mon, Jun 20, 2016 at 11:43 AM, Martin Sivak <<a href="mailto:msivak@redhat.com">msivak@redhat.com</a>> wrote:<br>
>><br>
>> > Won't we miss all mom's smart policy if we do that?<br>
>><br>
>> - Mom uses getAllVmStats (and one or two others) for stats collection<br>
>> and it polls for those atm. We can avoid that in the broker mode (VDSM<br>
>> sends the stats to the engine and we can listen).<br>
><br>
><br>
> We do not support this mode but with some work we could trigger an event<br>
> containing this information so mom can register to get it.<br>
><br>
>><br>
>> - Engine sends mom configuration through VDSM, but VDSM only converts<br>
>> that to different format and forwards that to MOM. This can be<br>
>> processed directly in MOM if VDSM knows how to ignore calls that are<br>
>> not relevant for it.<br>
>><br>
>> We will have to call VDSM to set values, but that should be still<br>
>> possible.<br>
>><br>
>> Martin<br>
>><br>
>> On Mon, Jun 20, 2016 at 11:05 AM, Dan Kenigsberg <<a href="mailto:danken@redhat.com">danken@redhat.com</a>><br>
>> wrote:<br>
>> > On Mon, Jun 20, 2016 at 10:33:19AM +0200, Martin Sivak wrote:<br>
>> >> > 1. Mom is still using xmlrpc<br>
>> >> ><br>
>> >> > Mom must move to jsonrpc.<br>
>> >> > Martin: can you update on progress of this work?<br>
>> >><br>
>> >> We would like to avoid going through VDSM completely, except from the<br>
>> >> broker part. Is it possible now to "parasitically" listen to vdsm<br>
>> >> events and engine commands without having to go through VDSM API?<br>
>> >><br>
>> >> You can drop XML RPC,. vdsm does not depend on MOM working anymore.<br>
>> >> Just the balloon and ksm stats will be missing from data that are<br>
>> >> being sent to the engine.<br>
>> ><br>
>> > Won't we miss all mom's smart policy if we do that?<br>
>> >><br>
>> >><br>
>> >> There also were some issues with eventfd in the json library, I assume<br>
>> >> those are fixed now.<br>
>> >><br>
>> >> Martin<br>
><br>
><br>
</div></div></blockquote></div><br></div></div>