summaryrefslogtreecommitdiffstats
path: root/xlators/cluster/dht
diff options
context:
space:
mode:
authorCsaba Henk <csaba@gluster.com>2011-08-24 23:01:31 +0200
committerVijay Bellur <vijay@gluster.com>2011-09-12 06:24:20 -0700
commit09eeaf4e68c225b8e5ccc0a9b4f10f8c4748e205 (patch)
treee0f7fde644913d70a8b8b16ed48d58fb6cfc0f87 /xlators/cluster/dht
parent37ac355cbbd36497f914905615bffb3e35805f0a (diff)
geo-rep: partial support for unprivileged gsyncd via mountbroker
gsyncd: - mounting code is split to a direct and a mountbroker based backend - option gluster-command gone - new options: gluster-params, gluster-cli-options, mountbroker - mountbroker mount backend is used if either a mountbroker label is given through the mountbroker option, or if gsyncd is unprivileged; in this case the username is used as label - have gluster cli invocations log to stderr so that we don't hit a permission issue with the logfiles glusterd: - do gsyncd pre-config with new options - add option geo-replication-log-group, so if that specified geo-rep logfile directories are given to that group (and thus members of the given group can do logging there) This is just WIP as geo-rep relies on trusted extended attributes and those are not accessible for unprivileged users. Even if we solved this issue, glusterd security settings are too coarse, so that if we made it possible for an unprivileged gsyncd to operate, we would open up too far. Change-Id: Icd520b58cbadccea3fad7c0f437b99de1e22db14 BUG: 2825 Reviewed-on: http://review.gluster.com/399 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Vijay Bellur <vijay@gluster.com>
Diffstat (limited to 'xlators/cluster/dht')
0 files changed, 0 insertions, 0 deletions