Bug 1361127

Summary:	[RFE]: rpc events
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Raghavendra G <rgowdapp>
Component:	rpc	Assignee:	Raghavendra Talur <rtalur>
Status:	CLOSED WONTFIX	QA Contact:	storage-qa-internal <storage-qa-internal>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.1	CC:	amukherj, avishwan, rcyriac, rhinduja, rhs-bugs
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	USM-Gluster integration
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1367382 (view as bug list)		Environment:
Last Closed:	2016-08-23 07:32:17 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Raghavendra G 2016-07-28 11:41:15 UTC

Description of problem:
This RFE is to track the changes required in the rpc to generate the events to be consumed by the eventing framework.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 Raghavendra Talur 2016-08-16 10:16:40 UTC

I currently do not see a need of generating events from rpc layer. It should rather be handled by consumers of rpc, just like glusterd is currently performing it.

I have created a bug in protocol component for the same, in case we need events for client connects and disconnects by brick processes. Bug: https://bugzilla.redhat.com/show_bug.cgi?id=1367382


Aravinda, it would be great if you could also confirm that we don't need events from RPC layer, rather from its users.

Comment 4 Atin Mukherjee 2016-08-23 07:32:17 UTC

Given that the consumers of the RPC is going to push the events, there is no change required at RPC component.