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

ganesha/scripts : use export id for dbus signals

2016-12-05T07:03:13+00:00

Currently for add export and update export parameter passed for executing those signal
is "PATH". This is based on assumption that volume name and PATH will always be same.
But it is wrong for subdir exports. The only reliable parameter in export configuration
file is "Export_Id".

Upstream reference :
>Change-Id: Ic63ff44ac7736e14502034b74beaae27292eddf9
>BUG: 1389746
>Signed-off-by: Jiffin Tony Thottan 
>Reviewed-on: http://review.gluster.org/15751
>Smoke: Gluster Build System 
>NetBSD-regression: NetBSD Build System 
>CentOS-regression: Gluster Build System 
>Reviewed-by: soumya k 
>Reviewed-by: Kaleb KEITHLEY 

Change-Id: Ic63ff44ac7736e14502034b74beaae27292eddf9
BUG: 1399635
Signed-off-by: Jiffin Tony Thottan 
Reviewed-on: http://review.gluster.org/15970
Smoke: Gluster Build System 
Reviewed-by: soumya k 
CentOS-regression: Gluster Build System 
NetBSD-regression: NetBSD Build System 
Reviewed-by: Kaleb KEITHLEY

Revert "NFS-Ganesha : scripts related changes for supporting multiple export entires for volume"

2016-04-24T14:29:47+00:00

This reverts change-id I2286af4877f96f4334435818f67beea87efa2b1f.
While testing, I had found that ganesha-ha.sh is not working as expected. It is
almost equivalent to rewrite entire thing again

Change-Id: Ia85e50fe8e043e8a2bc6441b7c45dcc726b36672
BUG: 1275966
Signed-off-by: Jiffin Tony Thottan 
Reviewed-on: http://review.gluster.org/13673
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Soumya Koduri 
Reviewed-by: Kaleb S KEITHLEY 
Reviewed-by: Niels de Vos 
Smoke: Gluster Build System

NFS-Ganesha : scripts related changes for supporting multiple export entires for volume

2016-03-01T08:00:04+00:00

Previously script such as dbus-send.sh, ganesha-ha.sh can handle only one EXPORT{} block.

Change-Id: I2286af4877f96f4334435818f67beea87efa2b1f
BUG: 1275966
Signed-off-by: Jiffin Tony Thottan 
Reviewed-on: http://review.gluster.org/13283
Smoke: Gluster Build System 
CentOS-regression: Gluster Build System 
NetBSD-regression: NetBSD Build System 
Reviewed-by: Kaleb KEITHLEY 
Reviewed-by: Jeff Darcy

hook-scripts: S29CTDBsetup: clean and fix mount commands and options

2016-01-15T13:52:56+00:00

This refactors the mount options of S29CTDBstart.sh into one
variable, removing the superfluous mentioning of 'default'.
The manual mount command is fixed to:
- also use the common options, thereby adding
  _netdev,transport=tcp
  (while this does not have an effect for the _netdev
   option, it makes a difference for the transport option),
- also use the HOSTNAME variable just like the fstab entry,
- use a "/" in the remote location specification.
Hence it now behaves identically to the fstab mount.

Change-Id: Ibb7613b1b1278ab13745846baa79268db226ef19
BUG: 1295520
Signed-off-by: Michael Adam 
Reviewed-on: http://review.gluster.org/13170
Tested-by: Raghavendra Talur 
Reviewed-by: Raghavendra Talur 
Reviewed-by: Rajesh Joseph 
NetBSD-regression: NetBSD Build System 
Smoke: Gluster Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Niels de Vos

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

2016-01-12T15:38:22+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.

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

hook-scripts: remove RHS-2.0 reference from S29CTDB scripts

2016-01-11T09:09:38+00:00

This is old. And such downstream reference should not
appear in upstream code.

Change-Id: Ifa0664dae0fe5ac913a49afe2fefa43b0112b024
BUG: 1295505
Signed-off-by: Michael Adam 
Reviewed-on: http://review.gluster.org/13169
Tested-by: Gluster Build System 
Reviewed-by: Anoop C S 
Reviewed-by: Raghavendra Talur

hook-scripts: remove outdated comment from C29CTDB start scipt

2016-01-10T10:52:54+00:00

This script does not change Samba's config any more.

Change-Id: Ie6001f9a49006f95b291e24252dc362f2a7db14c
BUG: 1295504
Signed-off-by: Michael Adam 
Reviewed-on: http://review.gluster.org/13168
Tested-by: Gluster Build System 
Reviewed-by: Anoop C S 
Reviewed-by: Niels de Vos

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

2015-12-26T17:31:24+00:00

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

hook-scripts: fix S30Samba scripts on systemd systems

2015-12-17T12:11:36+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

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

2015-12-16T19:13:36+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