+++ This bug was initially created as a clone of Bug #1081049 +++ The current communication between engine and vdsm is done using XML-RPC, where the engine actually acts as client and each vdsm is the server. This pauses a few issues that when it comes to scale effect drastically: - XML is expensive to parse - This mechanism forces the engine to poll each vdsm frequently for information The intent for this phase is to: - move to json-rpc (same API) - change transport to a real bidirectional transport to enable vdsm->engine events in the future
Hi Kliczewski This feature looks like a wide infrastructure change. Can you please provide a URL to the spec page so we can design a test plan for this?
Here is a link [1] to design spec. [1] http://www.ovirt.org/Features/Design/JsonRpc
still not fixed on vt2.2, should come with next respin.
Feature can be tested... if it has bugs it doesn't mean it can't be tested.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2015-0158.html