[Bugs] [Bug 1501029] setting storage.owner-gid should also change the mode to have setgid

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1501029

Niels de Vos <ndevos at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
              Flags|needinfo?(ndevos at redhat.com |
                   |)                           |



--- Comment #5 from Niels de Vos <ndevos at redhat.com> ---
It is already possible (though not through the Gluster CLI) to inherit the
group ownership on new files/directories. This can be done with ACLs or
(depending on the environment) with 'chmod g+s ...'.

It is still crucial that the umask is set correctly too. The 0644 mode (umask
0022) it often a default for newly created files, and even if the group-owner
is set correctly, members of that group will not be able to write to the file.

Depending what the actual feature request here is, issue 301 might be a more
suitable approach. If, however configuring the permissions solely though the
Gluster CLI is a requirement, then adjusting the umask/mode when
storage.owner-gid is set will needed as well.

The request in 301 is a little more flexible, as the group-owner can be
different between subdirectories on the volume (w/ ACL and "chmod +s").
storage.owner-gid is set per volume, which makes it more restrictive in its
usage (different teams/departments/projects can not share the same Gluster
volume if they have their own dedicated owner-gid).

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=SwBoAU6x2u&a=cc_unsubscribe