AddPathForTraverse addes the given path into an existing paths for traverse check.

GetPathsForDelTraverse resolves the parent paths of p on which the traverse role should be removed.

GetPathsForSetTraverse resolves the parent paths of p on which the traverse role should be set.

GetRoler returns a proper roler determined from the given path.

IsSameProjectPath checks whether the two given paths are pointing to the same project storage directory.

IsValidRole checks if the given role is a valid one.

The valid Roles are listed below: Manager: the role with read/write/management permission Contributor: the role with read/write permission Writer: the role with read/write permission but cannot delete files or (sub-)directories Viewer: the role with read permission Traverse: the role for passing through the directory System: the role referring to the Linux system permissions.

The valid Roles are listed below: Manager: the role with read/write/management permission Contributor: the role with read/write permission Writer: the role with read/write permission but cannot delete files or (sub-)directories Viewer: the role with read permission Traverse: the role for passing through the directory System: the role referring to the Linux system permissions.

The valid Roles are listed below: Manager: the role with read/write/management permission Contributor: the role with read/write permission Writer: the role with read/write permission but cannot delete files or (sub-)directories Viewer: the role with read permission Traverse: the role for passing through the directory System: the role referring to the Linux system permissions.

The valid Roles are listed below: Manager: the role with read/write/management permission Contributor: the role with read/write permission Writer: the role with read/write permission but cannot delete files or (sub-)directories Viewer: the role with read permission Traverse: the role for passing through the directory System: the role referring to the Linux system permissions.

The valid Roles are listed below: Manager: the role with read/write/management permission Contributor: the role with read/write permission Writer: the role with read/write permission but cannot delete files or (sub-)directories Viewer: the role with read permission Traverse: the role for passing through the directory System: the role referring to the Linux system permissions.

The valid Roles are listed below: Manager: the role with read/write/management permission Contributor: the role with read/write permission Writer: the role with read/write permission but cannot delete files or (sub-)directories Viewer: the role with read permission Traverse: the role for passing through the directory System: the role referring to the Linux system permissions.

RolerMap defines a list of supported rolers with associated path as key of the map.

ACE holds the attributes of a NFSv4 Access-Control Entry (ACE).

CephFsRoler implements roler interface for the CephFS.

FreeNasRoler implements Roler interfaces for the FreeNAS filer.

NetAppRoler implements Roler interfaces for the NetApp filer.

PosixACE is the posix-style access-control entry.

RolePathMap is a data structure where the RoleMap is associated with a Path.

Runner implements high-level functions for setting and deleting project roles in a given path.

Roler defines interfaces for managing user roles on a filesystem path referred by the FilePathMode (in package dccn.nl/utility/filepath).

Role is a enumeratable integer referring to one of the data-access role: Manager, Contributor, Viewer, Traverse, and System.

RoleMap is a map with key as the role, and value as a list of usernames in the role.