glusterfs-snapshot.git/extras, branch upstream

mgmt/glusterd: add option to specify a different base-port

2013-10-31T16:31:21+00:00

This is (arguably) a hack to work around a bug in libvirt which is not
well behaved wrt to using TCP ports in the unreserved space between
49152-65535. (See RFC 6335)

Normally glusterd starts and binds to the first available port in range,
usually 49152. libvirt's live migration also tries to use ports in this
range, but has no fallback to use (an)other port(s) when the one it wants
is already in use.

Change-Id: Id8fe35c08b6ce4f268d46804bbb6dddab7a6b7bb
BUG: 1018178
Signed-off-by: Kaleb S. KEITHLEY 
Reviewed-on: http://review.gluster.org/6210
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

extras/hook-scripts: Enable per client logging for gluster shares served by SAMBA

2013-10-22T19:55:37+00:00

Edited hook scrips to add a variable in the option 'log file', which will be
substituted for client IP.

Change-Id: I50f143bb3114eb00afab2e1237d749804c885ca6
BUG: 1020848
Signed-off-by: Poornima 
Reviewed-on: http://review.gluster.org/6109
Reviewed-by: Niels de Vos 
Tested-by: Gluster Build System

build: disable logging framework on rhel6

2013-10-18T15:30:08+00:00

As rsyslog-mmcount is not yet available in rhel6 variant, this patch
disables logging framework on rhel6 and its dependency

BUG: 1018308
Change-Id: I6b7c04640f8d38055e00c697d1017c7a530463d0
Signed-off-by: Bala.FA 
Reviewed-on: http://review.gluster.org/6108
Reviewed-by: Niels de Vos 
Tested-by: Gluster Build System

extras/hookscripts: Fix the multiple entries in smb.conf problem.

2013-10-08T16:22:00+00:00

Problem:
1. Force starts and user.smb sets were adding multiple entries to
the smb.conf file for the same volume.
Make a check for the entry and search with exact name.

2. Again, while deleting the share name from smb.conf search with
exact name so that volumes with names which are substrings of ones to
be deleted don't get deleted.

3. We don't need to use a tmp file while using sed -i, fixed that.

Change-Id: Ie0f7c9d4790ef9a177a043378a761c9ffe1628e5
BUG: 994727
Signed-off-by: Raghavendra Talur 
Reviewed-on: http://review.gluster.org/6043
Reviewed-by: Niels de Vos 
Reviewed-by: Lalatendu Mohanty 
Tested-by: Lalatendu Mohanty

hookscripts: Changes in hook scripts to make it work on all Linux/GNU distribution

2013-10-05T00:05:35+00:00

Removed the hard coded values for smb.conf, smb logfile location and smbd.pid.
The current hook scripts also work for manully compiled (make, make install)
instance of gluster and Samba. But we have to manually copy the hook scripts
to respective locations.

Change-Id: I14056830fcd2ecb48b3c4df89265f4408c8de3e3
Signed-off-by: Lalatendu Mohanty 
Reviewed-on: http://review.gluster.org/5947
Reviewed-by: poornima g 
Reviewed-by: susant palai 
Reviewed-by: Raghavendra Talur 
Tested-by: Raghavendra Talur 
Reviewed-by: Anand Avati

geo-rep: logrotate: Logrotate handling

2013-10-04T04:26:00+00:00

In existing georep logrotate was implemented by handling SIGSTOP
and SIGCONT, gsyncd was failing to start again after SIGSTOP.
New approach uses WatchedFileHandler in logging, which tracks the
log file changes or logrotate. Reopens the log file if logrotate is
triggered or if same log file is updated from other process.

As per python doc:
http://docs.python.org/2/library/logging.handlers.html:
The WatchedFileHandler class, located in the logging.handlers module,
is a FileHandler which watches the file it is logging to. If the file
changes, it is closed and reopened using the file name.

A file change can happen because of usage of programs such as newsyslog
and logrotate which perform log file rotation. This handler, intended
for use under Unix/Linux, watches the file to see if it has changed
since the last emit. (A file is deemed to have changed if its device
or inode have changed.) If the file has changed, the old file stream
is closed, and the file opened to get a new stream.

Change-Id: I30f65eb1e9778b12943d6e43b60a50344a7885c6
BUG: 1012776
Signed-off-by: Aravinda VK 
Reviewed-on: http://review.gluster.org/5968
Reviewed-by: Amar Tumballi 
Reviewed-by: Harshavardhana 
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

extras: add script and config for generating "Who wrote GlusterFS"

2013-09-29T23:56:23+00:00

This script and configuration can be used to generate statistics similar
to the "Who wrote " series available on http://lwn.net.

Example usage for statistics from the initial branchpoint of 3.4 to the
current development of the release-3.4 branch:

 $ extras/who-wrote-glusterfs/who-wrote-glusterfs.sh \
       v3.4.0alpha...origin/release-3.4

By default the statistics will be calculated over the currently checked
out branch.

Change-Id: Ie7b8b655c50dcb14257e42599e2f89642c8b5b42
Signed-off-by: Niels de Vos 
Reviewed-on: http://review.gluster.org/5912
Reviewed-by: Amar Tumballi 
Tested-by: Amar Tumballi 
Reviewed-by: Harshavardhana 
Reviewed-by: Anand Avati

glusterd.service (systemd), ensure glusterd starts before local mounts

2013-09-20T18:50:15+00:00

NOTICE: this patch was accepted onto the release-3.4 branch for 3.4.1,
but this same patch for master is languishing here in review.

Try (emphasis on the try) to ensure that glusterd starts, and in turn
starts glusterfsd before init attempt to mount any gluster (or gluster
NFS) volumes in /etc/fstab.

N.B. Joe Julian says this doesn't fix the problem for him, although it
worked for me in kvm. Lennart Poettering says it should, and we should
file a BZ against systemd if it doesn't. See
https://lists.fedoraproject.org/pipermail/devel/2013-July/185870.html

Change-Id: I4d8061217d8301beb0da485dc63a1984a7c57c37
Signed-off-by: Kaleb S. KEITHLEY 
BUG: 1004795
Reviewed-on: http://review.gluster.org/5823
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

Fix typo in systemd service definition file

2013-09-20T18:03:22+00:00

Change-Id: Ia9dac04ad508fbaafbed24b2137b09872a1ca53c
BUG: 1010352
Signed-off-by: Justin Clift 
Reviewed-on: http://review.gluster.org/5981
Reviewed-by: Kaleb KEITHLEY 
Tested-by: Anand Avati

glusterd/gverify.sh: Stops session being created with invalid slave details

2013-09-05T02:29:17+00:00

create force will fail with proper message, if the ip is not
reachable, or is unable to fetch slave details.

Change-Id: I44a3ba777b37702ffd0e48e9cb46c51e293327d4
BUG: 988314
Signed-off-by: Avra Sengupta 
Signed-off-by: Venky Shankar 
Reviewed-on: http://review.gluster.org/5516
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati