Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1112594

Summary: Use jsonrpc during migration of vms
Product: [oVirt] vdsm Reporter: Piotr Kliczewski <pkliczew>
Component: GeneralAssignee: Oved Ourfali <oourfali>
Status: CLOSED CURRENTRELEASE QA Contact: Petr Kubica <pkubica>
Severity: medium Docs Contact:
Priority: unspecified    
Version: ---CC: bazulay, bugs, gklein, mgoldboi, oourfali, rbalakri, yeylon
Target Milestone: ovirt-3.6.0-rcFlags: pkubica: needinfo-
rule-engine: ovirt-3.6.0+
ylavi: planning_ack+
rule-engine: devel_ack+
pstehlik: testing_ack+
Target Release: 4.17.10   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-02-10 12:52:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Piotr Kliczewski 2014-06-24 09:47:25 UTC
Current communication between two vdsm hosts uses xmlrpc during vm migration. 

We replaced engine-vdsm communication with jsonrpc and we need to do the same for vm migration.

Comment 1 Max Kovgan 2015-06-28 14:12:41 UTC
ovirt-3.6.0-3 release

Comment 2 Red Hat Bugzilla Rules Engine 2015-10-18 08:34:11 UTC
Bug tickets that are moved to testing must have target release set to make sure tester knows what to test. Please set the correct target release before moving to ON_QA.

Comment 3 Red Hat Bugzilla Rules Engine 2015-11-02 12:26:55 UTC
Bug tickets that are moved to testing must have target release set to make sure tester knows what to test. Please set the correct target release before moving to ON_QA.

Comment 4 Sandro Bonazzola 2015-11-04 14:43:43 UTC
This issue should be fixed in oVirt 3.6.0 released on November 4th 2015 but still need to be checked by QE

Comment 5 Petr Kubica 2016-01-07 15:35:20 UTC
Hi, can you provide any ways how to check it ?
If I understand it correctly it's only about using jsonrpc instead of xmlrpc while migrating VM. Is there any way how to monitor communication between the hosts (tcpdump, wireshark) or the communication is encrypted ?

Comment 7 Petr Kubica 2016-02-03 16:28:25 UTC
Verified in 3.6.3-0.1.el6

Checked log:
There are many logs about using jsonrpc.Executor for migrating VM from first host to second
...
jsonrpc.Executor/4::DEBUG::2016-02-03 17:19:37,351::API::581::vds::(migrationCreate) Migration create
..
jsonrpc.Executor/4::DEBUG::2016-02-03 17:19:37,546::API::599::vds::(migrationCreate) Destination VM creation succeeded
...