Bug 1393919 - [RFE] - Switch to the new jsonrpc client
Summary: [RFE] - Switch to the new jsonrpc client
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: ovirt-hosted-engine-setup
Classification: oVirt
Component: RFEs
Version: 2.0.3.1
Hardware: Unspecified
OS: Unspecified
unspecified
high vote
Target Milestone: ---
: ---
Assignee: Simone Tiraboschi
QA Contact: meital avital
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-10 16:00 UTC by Simone Tiraboschi
Modified: 2017-11-16 16:46 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-11-16 16:46:40 UTC
oVirt Team: Integration
ylavi: 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 Simone Tiraboschi 2016-11-10 16:00:05 UTC 
Description of problem:
the current VDSM jsonrpcclient will be deprecated in favor of a simple string based client.
The new client is under review here:
https://gerrit.ovirt.org/#/c/64502/

The call mechanism will change from:
 cli.getVmStats('bc26bd11-ee3b-4a56-80d4-770f383a47b9')
to
 cli.call('VM.getStats', {'vmID': 'bc26bd11-ee3b-4a56-80d4-770f383a47b9'})

Rebase all the code on the new client.
Comment 1 Yaniv Kaul 2017-11-16 14:08:48 UTC 
Is this still relevant with the new Ansible-based installation flow in 4.2?
Comment 2 Simone Tiraboschi 2017-11-16 14:19:08 UTC 
(In reply to Yaniv Kaul from comment #1)
> Is this still relevant with the new Ansible-based installation flow in 4.2?

Not on ovirt-hosted-engine-setup side and we completed it on ovirt-hosted-engine-ha side.
Comment 3 Yaniv Kaul 2017-11-16 16:46:40 UTC 
(In reply to Simone Tiraboschi from comment #2)
> (In reply to Yaniv Kaul from comment #1)
> > Is this still relevant with the new Ansible-based installation flow in 4.2?
> 
> Not on ovirt-hosted-engine-setup side and we completed it on
> ovirt-hosted-engine-ha side.

Closing then as NEXTRELEASE.
Note You need to log in before you can comment on or make changes to this bug.