Bug 1158820

Summary: [RFE] add event mechanism to send events from the host to the engine
Product: Red Hat Enterprise Virtualization Manager Reporter: Oved Ourfali <oourfali>
Component: RFEsAssignee: Piotr Kliczewski <pkliczew>
Status: CLOSED ERRATA QA Contact: Pavol Brilla <pbrilla>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.4.0CC: fdeutsch, gklein, iheim, lpeer, lsurette, pkliczew, pstehlik, rbalakri, sherold, yeylon, ykaul
Target Milestone: ovirt-3.6.0-rcKeywords: CodeChange, FutureFeature
Target Release: 3.6.0Flags: sherold: Triaged+
ylavi: testing_beta_priority+
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: OVIRT 3.6.0-3 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-03-09 20:50:13 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:

Description Oved Ourfali 2014-10-30 10:10:59 UTC
Description of problem:
The introduction of the jsonrpc communication mechanism is leading the way to further improve the engine-hypervisor communication.
This RFE is for adding a mechanism to send events from the host to the engine.

Comment 1 Fabian Deutsch 2014-10-31 17:57:36 UTC
Let me mention the https://wiki.mozilla.org/WebAPI/SimplePush which integrates well with at least Firefox.

Comment 2 Oved Ourfali 2015-07-01 10:51:48 UTC
Piotr, any testing required here, or will the tests be performed only on the VM monitoring changes?

Comment 3 Piotr Kliczewski 2015-07-01 11:19:24 UTC
There is no way to test this infrastructure without using it and the only way to use it without writing additional code is vm monitoring.

Comment 4 Pavol Brilla 2015-09-22 14:26:23 UTC
verified on 3.6.0-0.16.master.el6

Comment 6 errata-xmlrpc 2016-03-09 20:50:13 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.