Bug 1401588 - [RFE] Support HTTP / REST based external scheduler proxy instead of XML-RPC
Summary: [RFE] Support HTTP / REST based external scheduler proxy instead of XML-RPC
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: RFEs
Version: future
Hardware: Unspecified
OS: Unspecified
unspecified
low vote
Target Milestone: ---
: ---
Assignee: Scott Herold
QA Contact: Gil Klein
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-05 15:51 UTC by Martin Sivák
Modified: 2017-09-04 10:52 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-09-04 10:52:07 UTC
oVirt Team: SLA
msivak: ovirt-future?
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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.
Note You need to log in before you can comment on or make changes to this bug.