Bug 1401588

Summary: [RFE] Support HTTP / REST based external scheduler proxy instead of XML-RPC
Product: [oVirt] ovirt-engine Reporter: Martin Sivák <msivak>
Component: RFEsAssignee: Scott Herold <sherold>
Status: CLOSED DEFERRED QA Contact: Gil Klein <gklein>
Severity: low Docs Contact:
Priority: unspecified    
Version: futureCC: bugs
Target Milestone: ---Keywords: FutureFeature
Target Release: ---Flags: msivak: ovirt-future?
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-09-04 10:52:07 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: SLA RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Martin Sivák 2016-12-05 15:51:10 UTC 
Description of problem:

The current external scheduler proxy acts as XML-RPC. XML-RPC has some limitations in the standardized version (like 32 bit signed numbers).

I might make sense to remove the XML-RPC protocol and use the underlying HTTP with something like JSON for structuring data. That would give more freedom to external scheduler users as they would be free to use whatever technology or proxy they want.

It would also allow utilizing the ovirt-optimizer as a real scheduler (the support is already present in the optimizer, it is just used for debugging only atm).

The external scheduler is the only component using XML-RPC in the engine and there is nothing that would be missing from the architecture as it is also request/response based.
Comment 2 Martin Sivák 2017-09-04 10:52:07 UTC 
It is a valid idea, but we are currently pursuing a different direction.