Bug 1361126

Summary:	[RFE]: Fuse events
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Raghavendra G <rgowdapp>
Component:	fuse	Assignee:	Ravishankar N <ravishankar>
Status:	CLOSED WONTFIX	QA Contact:	storage-qa-internal <storage-qa-internal>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.1	CC:	amukherj, csaba, 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:		Environment:
Last Closed:	2016-08-18 10:05:32 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:38:37 UTC

Description of problem:
This RFE is to track the changes required in the fuse-bridge 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 Ravishankar N 2016-08-18 10:05:32 UTC

The log messages in the gluster fuse code (namely fuse-bridge.c,fuse-resolve.c and fuse-helpers.c) are mostly related to inode/fd resolution and invalidation. These are not particularly useful to the admin/ user from a asynchronous event notification point of view, Syscalls made by the application would anyway receive an errno when the FOP fails. 

As there are no user-relevant messages at the moment that are possible candidates for consumption by the eventing framework , I am closing the BZ for now.