Bug 1326233 - Richacl support and enforcing in Gluster
Summary: Richacl support and enforcing in Gluster
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: GlusterFS
Classification: Community
Component: posix-acl
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: rjoseph
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-12 08:39 UTC by Niels de Vos
Modified: 2017-11-03 18:18 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-11-03 18:18:52 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.