glusterfs.git/extras/hook-scripts, branch v3.7.4

rpm: include required directory for glusterfind

2015-08-25T15:50:55+00:00

The directory was marked as %ghost, which causes the following
installation failure:

  Error unpacking rpm package glusterfs-server-3.8dev-0.446.git45e13fe.el7.centos.x86_64
  error: unpacking of archive failed on file /var/lib/glusterd/hooks/1/delete/post/S57glusterfind-delete-post.py;5581f20e: cpio: open

Also, *all* Python files should be part of the RPM package. This
includes generated .pyc and .pyo files.

BUG: 1256307
Change-Id: Iee74905b101912c4a845257742c470c3fe42ce2a
Signed-off-by: Niels de Vos 
Signed-off-by: Aravinda VK 
Reviewed-on: http://review.gluster.org/11298
Reviewed-on: http://review.gluster.org/12000
Tested-by: NetBSD Build System 
Tested-by: Gluster Build System

glusterd/shared_storage: Use /var/lib/glusterd/ss_brick as shared storage's brick

2015-07-07T05:55:48+00:00

     Backport of http://review.gluster.org/#/c/11533/

The brick path we use to create shared storage is
/var/run/gluster/ss_brick.

The problem with using this brick path is /var/run/gluster
is a tmpfs and all the brick/shared storage data will be wiped
off when the node restarts. Hence using /var/lib/glusterd/ss_brick
as the brick path for shared storage volume as this brick and
the shared storage volume is internally created by us (albeit on
user's request), and contains only internal state data and no user data.

Change-Id: I808d1aa3e204a5d2022086d23bdbfdd44a2cfb1c
BUG: 1230399
Signed-off-by: Avra Sengupta 
Reviewed-on: http://review.gluster.org/11534
Tested-by: Gluster Build System 
Reviewed-by: Rajesh Joseph

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

gluster/shared_storage: Add/Remove shared storage from /etc/fstab during enable/disable

2015-06-24T09:13:14+00:00

    Backport of http://review.gluster.org/#/c/11272/

While creating/deleting shared storage volume, add/remove the shared storage
entry from /etc/fstab, so as to ensure availability of the shared storage,
even after a node reboot

Change-Id: Ib9edc8fd02c74a677062ca53ffd10be997b056c6
BUG: 1232889
Signed-off-by: Avra Sengupta 
Reviewed-on: http://review.gluster.org/11295
Tested-by: Gluster Build System 
Reviewed-by: Atin Mukherjee 
Reviewed-by: Rajesh Joseph 
Tested-by: NetBSD Build System

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

tools/glusterfind: Cleanup glusterfind dir after a volume delete

2015-06-12T18:35:35+00:00

If `glusterfind delete` command was not run before volume delete, stale
session directories exists in /var/lib/glusterd/glusterfind directories.

Also shows these sessions in `glusterfind list`

When Volume is deleted, Post hook will be run which cleans up the stale
session directories

BUG: 1225551
Change-Id: I54c46c30313e92c1bb4cb07918ed2029b375462c
Signed-off-by: Aravinda VK 
Reviewed-on: http://review.gluster.org/#/c/10944
Reviewed-on: http://review.gluster.org/11186
Tested-by: NetBSD Build System 
Tested-by: Gluster Build System 
Reviewed-by: Kotresh HR 
Reviewed-by: Vijay Bellur

build: fix compiling on older distributions

2015-06-11T14:29:03+00:00

data-tiering is disabled on RHEL-5 because it depends on a too new
SQLite version.

This change also prevents installing some of files that are used by
geo-replication, which is also not available on RHEL-5. geo-replication
depends on a too recent version of Python.

Due to an older version of OpenSSL, some of the newer functions can not
be used. A fallback to previous functions is done. Unfortunately RHEL-5
does not seem to have TLSv1.2 support, so only older versions can be
used.

Cherry picked from commit 0209b18fd65f9df5ebd0a8764ebf864d0d392998:
> Change-Id: I672264a673f5432358d2e83b17e2a34efd9fd913
> BUG: 1222317
> Signed-off-by: Niels de Vos 
> Reviewed-on: http://review.gluster.org/10803
> Tested-by: NetBSD Build System 
> Tested-by: Gluster Build System 
> Reviewed-by: Kaleb KEITHLEY 
> Reviewed-by: Vijay Bellur 

Also including the changes from http://review.gluster.org/11140:

> build: improve detection of new OpenSSL features
>
> Building on Mac OS X revealed that the current check for
> CRYPTO_THREADID_set_callback() availability in OpenSSL is not correct.
>
> There also does not seem to be a guarantee that TLSv1_2_method() is
> available when TLS1_2_VERSION is #define'd.
>
> Change-Id: I21508065fc181a1c74bee4fd6d23bb5bdf7cea7a
> BUG: 1222317
> Reviewed-on: http://review.gluster.org/11140
> Original-author: Kaleb KEITHLEY 
> Signed-off-by: Niels de Vos 

Change-Id: I672264a673f5432358d2e83b17e2a34efd9fd913
BUG: 1228510
Signed-off-by: Niels de Vos 
Reviewed-on: http://review.gluster.org/11096
Tested-by: Gluster Build System 
Reviewed-by: Atin Mukherjee 
Reviewed-by: Kaleb KEITHLEY

glusterd/shared_storage: Provide a volume set option to create and mount the shared storage

2015-06-05T09:20:26+00:00

     Backport of http://review.gluster.org/#/c/10793/

Introducing a global volume set option(cluster.enable-shared-storage)
which helps create and set-up the shared storage meta volume.

gluster volume set all cluster.enable-shared-storage enable

On enabling this option, the system analyzes the number of peers
in the cluster, which are currently connected, and chooses three
such peers(including the node the command is issued from). From these
peers a volume(gluster_shared_storage) is created. Depending on the
number of peers available the volume is either a replica 3
volume(if there are 3 connected peers),  or a replica 2 volume(if there
are 2 connected peers). "/var/run/gluster/ss_brick" serves as the
brick path on each node for the shared storage volume. We also mount
the shared storage at "/var/run/gluster/shared_storage" on all the nodes
in the cluster as part of enabling this option. If there is only one node
in the cluster,  or only one node is up then the command will fail

Once the volume is created, and mounted the maintainance of the
volume like adding-bricks, removing bricks etc., is expected to
be the onus of the user.

On disabling the option, we provide the user a warning, and on
affirmation from the user we stop the shared storage volume, and unmount
it from all the nodes in the cluster.

gluster volume set all cluster.enable-shared-storage disable

Change-Id: Idd92d67b93f444244f99ede9f634ef18d2945dbc
BUG: 1228181
Signed-off-by: Avra Sengupta 
Reviewed-on: http://review.gluster.org/11086
Tested-by: NetBSD Build System 
Tested-by: Gluster Build System 
Reviewed-by: Rajesh Joseph 
Reviewed-by: Krishnan Parthasarathi