Bug 1326233

Summary: Richacl support and enforcing in Gluster
Product: [Community] GlusterFS Reporter: Niels de Vos <ndevos>
Component: posix-aclAssignee: rjoseph
Status: CLOSED NOTABUG QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: mainlineCC: atumball, bugs
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-11-03 18:18:52 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 Niels de Vos 2016-04-12 08:39:50 UTC
Richacl is intended to be a common ACL implementation for different protocols. When Gluster supports richacl, it should become much easier to apply the same ACLs over FUSE, Samba, NFS and other access protocols.

Comment 1 Niels de Vos 2016-05-10 11:52:03 UTC
This didnt make it for GlusterFS 3.8, moving out of the tracking tree.

Comment 2 Niels de Vos 2016-05-10 11:52:27 UTC
WIP patches posted: http://review.gluster.org/13866

Comment 3 Amar Tumballi 2017-11-03 18:18:52 UTC
The issue is now open in github for the feature @ https://github.com/gluster/glusterfs/issues/225

Closing as 'NOTABUG' as this is a feature.