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

Bug 1083070

Summary: [RFE] Optimization of the communication between VDSM and the Engine for Virtual Machine data
Product: [Retired] oVirt Reporter: Vinzenz Feenstra [evilissimo] <vfeenstr>
Component: vdsmAssignee: Vinzenz Feenstra [evilissimo] <vfeenstr>
Status: CLOSED DUPLICATE QA Contact: Gil Klein <gklein>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.5CC: bazulay, bugs, gklein, iheim, mgoldboi, michal.skrivanek, rbalakri, yeylon
Target Milestone: ---Keywords: FutureFeature
Target Release: 3.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: virt
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-03 08:00:30 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Vinzenz Feenstra [evilissimo] 2014-04-01 12:40:29 UTC
Currently VDSM gets polled for a lot of data from the engine. A lot of this data does not need to be transmitted.

Currently we have the following calls
* Every 3 seconds `list`
* Every 15 seconds `getAllVmStats`

The call to getAllVmStats can easily grow to several hundreds of kilobytes per call.

However the majority of the data sent by VDSM to the engine is not required by the engine at all. However since there is currently no more effective way the engine is required to query the data all the time.

Goals for this RFE:

Reduce the VM data transfer size to a minimum and provide means to get only data which did really changed since the last request.

Comment 1 Michal Skrivanek 2014-05-28 14:45:15 UTC
didn't make much progress yet...

Comment 2 Michal Skrivanek 2015-05-21 08:21:57 UTC
dropping 3s interval by implementing events over JSON-RPC (see http://gerrit.ovirt.org/#/q/status:open+project:vdsm+branch:master+topic:events_vm_status)

Comment 3 Michal Skrivanek 2015-06-03 08:00:30 UTC
moving over there

*** This bug has been marked as a duplicate of bug 1225368 ***