Re: [ovirt-devel] Killing XMLRPC on master

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. There also were some issues with eventfd in the json library, I assume those are fixed now. Martin On Sun, Jun 19, 2016 at 1:02 PM, Nir Soffer <nsoffer(a)redhat.com&gt; wrote: > Hi all, > > We are still wasting time on maintaining both xmlrpc and jsonrpc. If we kill > xmlrpc, we can greatly simplify the code base, making it easier to mainain > and add new features. > > I suggest to kill xmlrpc in 4.1, and disable it *now* on master. > > Currently the we have 3 issues: > > > 2. sos plugin using vdsClient > > Need to port it to use jsonrpc library, or jsonrpc client > > New jsonrpc client: https://gerrit.ovirt.org/35181 > > 3. Engine is using xmlrpc server for ovf upload/download > > We must support current engine in 4.1, so we cannot remove > upload/download feature in this version, but we can remove the > xmlrpc support in this server. > > Currently we abuse the xmlrpc server, supporting PUT and GET for > upload and download (XMLRPC is using only POST). We can disable > POST requests in protocoldetector, and not register anything with > the xmlrpc server. > > Thoughts? > > Nir