Bug 1346010

Summary:	Introduce API support for requesting mandatory locks
Product:	[Community] GlusterFS	Reporter:	Anoop C S <anoopcs>
Component:	libgfapi	Assignee:	Anoop C S <anoopcs>
Status:	CLOSED DEFERRED	QA Contact:	Sudhir D <sdharane>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	mainline	CC:	bugs
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1346013 1348975 (view as bug list)		Environment:
Last Closed:	2018-01-17 05:17:50 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:
Bug Depends On:
Bug Blocks:	1346013, 1348975

Description Anoop C S 2016-06-13 16:21:34 UTC

Description of problem:
In spite of having the mandatory-locks feature for GlusterFS, its native C API lacks support for requesting the same. This bug is to track the implementation/extension of libgfapi to provide this support for applications.

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

Comment 1 Vijay Bellur 2016-06-15 06:03:29 UTC

REVIEW: http://review.gluster.org/11177 (libgfapi: Add new api for supporting mandatory-locks) posted (#17) for review on master by Anoop C S (anoopcs)

Comment 2 Vijay Bellur 2016-07-08 09:58:16 UTC

REVIEW: http://review.gluster.org/11177 (libgfapi: Add new api for supporting mandatory-locks) posted (#19) for review on master by Anoop C S (anoopcs)

Comment 3 Vijay Bellur 2016-07-15 14:03:55 UTC

REVIEW: http://review.gluster.org/11177 (libgfapi: Add new api for supporting mandatory-locks) posted (#20) for review on master by Anoop C S (anoopcs)

Comment 4 Worker Ant 2017-07-28 10:34:18 UTC

REVIEW: https://review.gluster.org/11177 (libgfapi: Add new api for supporting mandatory-locks) posted (#21) for review on master by Anoop C S (anoopcs)

Comment 5 Anoop C S 2018-01-17 05:11:03 UTC

This will be tracked in future via https://github.com/gluster/glusterfs/issues/393. So closing out the bug report.