glusterfs.git/extras/hook-scripts/start/post, branch v3.7.10

build: use 'make install' to install the hook scripts

2016-02-04T06:11:08+00:00

This is a backport of http://review.gluster.org/#/c/13072

The installation should be the same on all distributions, and doing
manual installation of files in the .spec is very ugly. This change adds
the rules so that 'make install' places the hook scripts in the right
location.

Also, the hook script(s) for NFS-Ganesha should be part of the
glusterfs-ganesha sub-package and got moved there.

> BUG: 1174765
> Change-Id: Iba25a7a5112c7d40db4c10ff4a5ac7a5fb4f7c4e
> Signed-off-by: Niels de Vos 
> Reviewed-on: http://review.gluster.org/13072
> Tested-by: Gluster Build System 
> Reviewed-by: Kaleb KEITHLEY 

Change-Id: I8fade7e9e540eedc1e619f116d356a2b26f599a9
BUG: 1302955
Signed-off-by: vmallika 
Reviewed-on: http://review.gluster.org/13313
Smoke: Gluster Build System 
CentOS-regression: Gluster Build System 
NetBSD-regression: NetBSD Build System 
Reviewed-by: Kaleb KEITHLEY

scripts: prevent running 'showmount' from the start/post hook script

2016-01-14T11:34:40+00:00

The 31ganesha-start.sh hook script tries to run 'showmount' to see if
the volume that is getting started should get exported by NFS-Ganesha.
It was reported that this caused the 'gluster volume start ...' command
to hang in case rpcbind is not running.

Instead of running 'showmount', we can use DBus to contact NFS-Ganesha
directly, and request the available exports. This will immediately fail
in case NFS-Ganesha is not running.

Cherry picked from commit 2b2294d2a4ef221fccb6eb9f74e9b7dc233b9f1d:
> BUG: 1294446
> Change-Id: I3aba1f86fead67116ca5adb1864a8be626c334fa
> Reported-by: Jeff Darcy 
> Signed-off-by: Niels de Vos 
> Reviewed-on: http://review.gluster.org/13098
> Tested-by: Raghavendra Talur 
> Reviewed-by: jiffin tony Thottan 
> Reviewed-by: Kaleb KEITHLEY 

BUG: 1297862
Change-Id: I3aba1f86fead67116ca5adb1864a8be626c334fa
Signed-off-by: Niels de Vos 
Reviewed-on: http://review.gluster.org/13230
Tested-by: NetBSD Build System 
Reviewed-by: Kaleb KEITHLEY

hook-scripts: fix S30Samba scripts on systemd systems

2015-12-19T05:04:53+00:00

/etc/init.d/smb does not exist on systemd systems.
Using "service smb " is the portable way.
It calls init scripts on sysv systems, and redirects
to systemctl on systemd systems.

> Change-Id: I7146c9998a51d8b170d3321f3477e92704ae7615
> BUG: 1290604
> Signed-off-by: Michael Adam 
> Reviewed-on: http://review.gluster.org/12945
> Tested-by: Gluster Build System 
> Reviewed-by: Anoop C S 
> Tested-by: NetBSD Build System 
> Reviewed-by: Niels de Vos 

(cherry picked from commit ce3ff7e328483dffdae6ae2914924bc2380db67e)

Change-Id: Ied6b5fe330f8d29df10a9aea1809be5c5f0c8a5e
BUG: 1292755
Signed-off-by: Michael Adam 
Reviewed-on: http://review.gluster.org/13000
Tested-by: NetBSD Build System 
Tested-by: Gluster Build System 
Reviewed-by: Rajesh Joseph

hook-scripts: don't let ctdb script change samba config

2015-12-18T09:17:12+00:00

There are several reasons why the behaviour in
the hook scripts was bad:

1. A samba installation is clustered or non-clustered.
   That does not change because of the availability
   of the CTDB lock-volume. If the lock-volume is not
   available (and hence CTDB is not available or not
   healthy), then Samba won't be operational. But turning
   it into a non-clustered Samba-installation can in
   the worst case lead to data corruption if clients
   manage to access the same files (on share volumes).
   Hence 'clustering = yes/no' in Samba's config should
   not be touched.

   In particular, Samba should not be stopped/started by
   the hook script. If needed, then ctdb will take care
   of it.

2. Changing the idmap configuration is potentially
   dangerous as well. In particular the used tdb2
   backend is legacy nowadays and should not be used
   any more in new installs. (I stems from the times
   when ctdb could not host persistent databases.)
   Changing the idmap can result in loss of access
   to files or in giving access to files where it is
   not intended.

3. The pattern used for detecting need for change is
   fragile. It may or may not play well possible
   manual changes to smb.conf.

This change removes the parts that change the smb.conf
file and start or stop Samba from the S29CTDB* hook scripts.

> Change-Id: I72f7aabafa8f089da4531fca2572a72c22825bcc
> BUG: 1290151
> Signed-off-by: Michael Adam 
> Reviewed-on: http://review.gluster.org/12930
> Tested-by: Gluster Build System 
> Reviewed-by: Raghavendra Talur 

(cherry picked from commit 27c16d6da82876a689dfba53b8d45c3a3a657954)

Change-Id: Ie1f787cebb5f6da1a658f7dead879fa854901ef5
BUG: 1292254
Signed-off-by: Michael Adam 
Reviewed-on: http://review.gluster.org/12986
Tested-by: Gluster Build System 
Reviewed-by: Raghavendra Talur

extras/hookscripts : introducing additional check in S31ganesha-start.sh

2015-09-24T08:53:41+00:00

New export file with default configuration will be created for a volume
when it is started again. This patch will create new export file only
when it is not present. This change is required for scenarios such as
snapshot restore , node reboot etc.

Change-Id: I34123911f176dcb29d5c016aa097af3a3b2c727b
BUG: 1261444
Signed-off-by: Jiffin Tony Thottan 
Reviewed-on: http://review.gluster.org/12219
Tested-by: NetBSD Build System 
Tested-by: Gluster Build System 
Reviewed-by: Kaleb KEITHLEY 
Reviewed-by: Niels de Vos

NFS-Ganesha : Unexport fails after S31ganesha-start script is run

2015-07-02T14:51:11+00:00

The dbus-send script extracts the export ID from the export config
file. It expects the export ID to be written in a particular format.
The post-phase hook-script created the export file in a different
format, and the dbus-send never gets the correct export ID because
of this. Fixing the issue by replacing the write_conf function in the
S31ganesha-start hook-script. Also, NFS-Ganesha service stops when
dbus signal is sent more than once on the same export. Consecutive
start/stop operations creates problems. Fixing all the issues at once.

Change-Id: I1306c68e2bc9abd91be1b7f1558c93060cc9c98d
BUG: 1238752
Signed-off-by: Kaleb S. KEITHLEY 
Reviewed-on: http://review.gluster.org/11511

NFS-Ganesha : Exporting volume fails

2015-06-30T10:01:52+00:00

Due to a recent fix, the dbus-send.sh looked
for a .export_added file even before it was
created. This resulted in the ganesha.enable
option failing consistently. Fixing it.

This is a backport of the fix in master,
http://review.gluster.org/#/c/11456/

Change-Id: I9658ff8eced405eed7a26fab334f7172171133e8
BUG: 1236933
Signed-off-by: Meghana 
Reviewed-on: http://review.gluster.org/11458
Tested-by: Gluster Build System 
Tested-by: NetBSD Build System 
Reviewed-by: Niels de Vos

NFS-Ganesha : Automatically export volume after volume restart

2015-06-27T09:58:11+00:00

The export file was not getting created in the correct
path. Fixing the path in this patch.

This is the backport of the fix merged on master,
http://review.gluster.org/#/c/11432/

Change-Id: I812f9d97252ee83a239f05ad683d2d727f3f5f59
BUG: 1232335
Signed-off-by: meghana 
Reviewed-on: http://review.gluster.org/11435
Tested-by: NetBSD Build System 
Tested-by: Gluster Build System 
Reviewed-by: soumya k 
Reviewed-by: Kaleb KEITHLEY

NFS-Ganesha: Automatically export vol that was exported before vol restart

2015-06-18T17:24:42+00:00

Consider a volume that is exported via NFS-Ganesha. Stopping this
volume will automatically unexport the volume. Starting this volume
should automatically export it. Although the logic was already there,
there was a bug in it. Fixing the same by introducing a hook script.

Also with the new CLI options, the hook script S31ganesha-set.sh
is no longer required. Hence, removing the same.
Adding a comment to tell the user that one of the CLI
commands will take a few minutes to complete.

This is a backport of the patch merged on master,
http://review.gluster.org/#/c/11247/

Change-Id: I1c16a978b9e2093a4298ea3024d031fd1a5bb577
BUG: 1232335
Signed-off-by: Meghana Madhusudhan 
Reviewed-on: http://review.gluster.org/11259
Tested-by: Gluster Build System 
Reviewed-by: Kaleb KEITHLEY 
Reviewed-by: soumya k 
Reviewed-by: Niels de Vos

build: make GLUSTERD_WORKDIR rely on localstatedir

2014-08-07T08:17:29+00:00

- Break-way from '/var/lib/glusterd' hard-coded previously,
  instead rely on 'configure' value from 'localstatedir'
- Provide 's/lib/db' as default working directory for gluster
  management daemon for BSD and Darwin based installations
- loff_t is really off_t on Darwin
- fix-off the warnings generated by clang on FreeBSD/Darwin
- Now 'tests/*' use GLUSTERD_WORKDIR a common variable for all
  platforms.
- Define proper environment for running tests, define correct PATH
  and LD_LIBRARY_PATH when running tests, so that the desired version
  of glusterfs is used, regardless where it is installed.
  (Thanks to manu@netbsd.org for this additional work)

Change-Id: I2339a0d9275de5939ccad3e52b535598064a35e7
BUG: 1111774
Signed-off-by: Harshavardhana 
Signed-off-by: Emmanuel Dreyfus 
Reviewed-on: http://review.gluster.org/8246
Tested-by: Gluster Build System