[ovirt-devel] Removal of xmlrpc

[Martin Sivak]

> Is there any reason why we need it?

Yes, the external scheduler proxy interface uses XML-RPC (this is
totally unrelated to VDSM).

> Do we plan to rewrite it to use
> other protocol?

Not at the moment. The external scheduler has no issues with XML-RPC
and it can easily (and is) be used by any implementation you want (we
provide our own proxy, but anybody can replace that with their
solution).

> I am going to leave this code and xmlrpc dependency in the engine so
> we can improve it later.

There is no reason to remove XML-RPC completely. It is still an useful
tool even though VDSM got rid of it. I think we might replace that
with pure and simple HTTP REST based proxy in the future, but we do
not have the time for it right now.

Martin

On Wed, Nov 23, 2016 at 12:00 PM, Piotr Kliczewski
<piotr.kliczewski at gmail.com> wrote:
> I am working on xmlrpc removal from the engine. I see bunch of
> references in [1] to xmlrpc client.
> Is there any reason why we need it? Do we plan to rewrite it to use
> other protocol?
>
> I am going to leave this code and xmlrpc dependency in the engine so
> we can improve it later.
>
> Thanks,
> Piotr
>
>
> [1] https://github.com/oVirt/ovirt-engine/blob/67880b549bada18aa3466d20a77da5c036edac60/backend/manager/modules/bll/src/main/java/org/ovirt/engine/core/bll/scheduling/external/ExternalSchedulerBrokerImpl.java