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
*** Bug 1100243 has been marked as a duplicate of this bug. ***
Jsonrpc can be selected when adding a host and despite of some minor bugs tracked separately it works.
oVirt 3.5 has been released and should include the fix for this issue.