<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jun 20, 2016 at 11:05 AM, Dan Kenigsberg <span dir="ltr"><<a href="mailto:danken@redhat.com" target="_blank">danken@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="">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></span></blockquote><div><br></div><div>Yes, you can use jsonrpc client and register for specific events assuming that they are sent.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
> 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>
</span>Won't we miss all mom's smart policy if we do that?<br>
<div class="HOEnZb"><div class="h5">><br>
><br>
> There also were some issues with eventfd in the json library, I assume<br>
> those are fixed now.<br>
><br>
> Martin<br>
</div></div></blockquote></div><br></div></div>