glusterfs.git/extras, branch v3.7.9

geo-rep: Script to Schedule Geo-replication

2016-03-08T10:00:01+00:00

This script can be used to run Geo-replication when required. can be
scheduled using cron job to run Geo-replication.

This script does the following,
  1. Stop Geo-replication if Started
  2. Start Geo-replication
  3. Set Checkpoint
  4. Check the Status and see Checkpoint is Complete.(LOOP)
  5. If checkpoint complete, Stop Geo-replication

Usage:
    python /usr/share/glusterfs/scripts/schedule_georep.py  \
                  

For example,
    python /usr/share/glusterfs/scripts/schedule_georep.py gv1 fvm1 gv2

To schedule the Geo-replication to run once in a day using cron,
   # Run daily at 08:30pm
      30 20 * * * root python /usr/share/glusterfs/scripts/schedule_georep.py \
            --no-color gv1 fvm1 gv2 >> /var/log/glusterfs/schedule_georep.log 2>&1

BUG: 1309191
Signed-off-by: Aravinda VK 
Reviewed-on: http://review.gluster.org/13279
Change-Id: Ie1507be00afd9ff189bb1664b156328dced4076a
Reviewed-on: http://review.gluster.org/13510
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Kotresh HR

quota: heal object-limit on a root dir of a newly added brick

2016-03-04T06:15:37+00:00

This is a backport of http://review.gluster.org/13422

When a new brick is added, xattr trusted.glusterfs.quota.limit-objects
is not healed on a root directory.
This patch will fix the problem

> Change-Id: I776609ebf4d7822c541b6262e63d465ea3a86db4
> BUG: 1306220
> Signed-off-by: vmallika 
> Reviewed-on: http://review.gluster.org/13422
> Smoke: Gluster Build System 
> CentOS-regression: Gluster Build System 
> NetBSD-regression: NetBSD Build System 
> Reviewed-by: Atin Mukherjee 

Change-Id: I47412b4da35c0f5d28106020daf32212d267cb9e
BUG: 1312954
Signed-off-by: vmallika 
Reviewed-on: http://review.gluster.org/13551
Smoke: Gluster Build System 
CentOS-regression: Gluster Build System 
NetBSD-regression: NetBSD Build System 
Reviewed-by: Atin Mukherjee

nfs-ganesha: pcs cluster setup needs '--name' option

2016-03-04T02:11:14+00:00

Even on fedora machines (on f22, f23), pcs cluster setup CLI
expects '--name' to be provided. This patch addresses the same.

Change-Id: Id33c8bbdc33955dd54729b10c720f4fa646f7e8c
BUG: 1314204
Signed-off-by: Soumya Koduri 
Reviewed-on: http://review.gluster.org/13590
Smoke: Gluster Build System 
Reviewed-by: jiffin tony Thottan 
CentOS-regression: Gluster Build System 
Reviewed-by: Kaleb KEITHLEY 
NetBSD-regression: NetBSD Build System

ganesha: Read export_id on each node while performing refresh-config

2016-02-28T20:14:35+00:00

As mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=1309238#c1,
there could be cases which shall result in having different ExportIDs
for the same volume on each node forming the ganesha cluster.

Hence during refresh-config, it is necessary to read the ExportID on
each of those nodes and re-export that volume with the same ID.

Change-Id: I44058352fe977ccc649d378da3b68bbfb992fcd7
BUG: 1309238
Signed-off-by: Soumya Koduri 
Reviewed-on: http://review.gluster.org/13459
CentOS-regression: Gluster Build System 
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
Reviewed-by: Kaleb KEITHLEY

common-ha: reliable grace using pacemaker notify actions

2016-02-26T11:00:38+00:00

Using *-dead_ip-1 resources to track on which nodes the ganesha.nfsd
had died was found to be unreliable.

Running `pcs status` in the ganesha_grace monitor action was seen to
time out during failover; the HA devs opined that it was, generally,
not a good idea to run `pcs status` in a monitor action in any event.
They suggested using the notify feature, where the resources on all
the nodes are notified when a clone resource agent dies.

This change adds a notify action to the ganesha_grace RA. The ganesha_mon
RA monitors its ganesha.nfsd daemon. While the daemon is running, it
creates two attributes: ganesha-active and grace-active. When the daemon
stops for any reason, the attributes are deleted. Deleting the
ganesha-active attribute triggers the failover of the virtual IP (the
IPaddr RA) to another node where ganesha.nfsd is still running. The
ganesha_grace RA monitors the grace-active attribute. When the
grace-active attibute is deleted, the ganesha_grace RA stops, and will
not restart. This triggers pacemaker to trigger the notify action in
the ganesha_grace RAs on the other nodes in the cluster; which send a
DBUS message to their ganesha.nfsd.

(N.B. grace-active is a bit of a misnomer. while the grace-active
attribute exists, everything is normal and healthy. Deleting the
attribute triggers putting the surviving ganesha.nfsds into GRACE.)

To ensure that the remaining/surviving ganesha.nfsds are put into
NFS-GRACE before the IPaddr (virtual IP) fails over there is a short
delay (sleep) between deleting the grace-active attribute and the
ganesha-active attribute. To summarize:
  1. on node 2 ganesha_mon:monitor notices that ganesha.nfsd has died
  2. on node 2 ganesha_mon:monitor deletes its grace-active attribute
  3. on node 2 ganesha_grace:monitor notices that grace-active is gone
     and returns OCF_ERR_GENERIC, a.k.a. new error. When pacemaker
     tries to (re)start ganesha_grace, its start action will return
     OCF_NOT_RUNNING, a.k.a. known error, don't attempt further
     restarts.
  4. on nodes 1, 3, etc., ganesha_grace:notify receives a post-stop
     notification indicating that node 2 is gone, and sends a DBUS
     message to its ganesha.nfsd putting it into NFS-GRACE.
  5. on node 2 ganesha_mon:monitor waits a short period, then deletes
     its ganesha-active attribute. This triggers the IPaddr (virt IP)
     failover according to constraint location rules.

ganesha_nfsd modified to run for the duration, start action is invoked
to setup the /var/lib/nfs symlink, stop action is invoked to restore it.
ganesha-ha.sh modified accordingly to create it as a clone resource.

Change-Id: Iad60b0c5222bbd55ef95c8b8f955e791caa3ffd0
BUG: 1290865
Signed-off-by: Kaleb S KEITHLEY 
Reviewed-on: http://review.gluster.org/12964
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System

quota: fix quota hook script for add-brick

2016-02-10T08:58:23+00:00

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

Hook script should not call any CLI commands
as this can cause parallel operation problem,
so remove quota list command from the script

> Change-Id: I76a364133403371b172e063abd5f742075b20a2f
> BUG: 1294637
>Signed-off-by: vmallika 

Change-Id: I9f2850e53c2ce69b33a82acec3fc739bc5bf54e5
BUG: 1296040
Signed-off-by: vmallika 
Reviewed-on: http://review.gluster.org/13182
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Atin Mukherjee

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

all: reduce "inline" usage

2016-01-18T09:02:34+00:00

There are three kinds of inline functions: plain inline, extern inline,
and static inline.  All three have been removed from .c files, except
those in "contrib" which aren't our problem.  Inlines in .h files, which
are overwhelmingly "static inline" already, have generally been left
alone.  Over time we should be able to "lower" these into .c files, but
that has to be done in a case-by-case fashion requiring more manual
effort.  This part was easy to do automatically without (as far as I can
tell) any ill effect.

In the process, several pieces of dead code were flagged by the
compiler, and were removed.

backport of Change-Id: I56a5e614735c9e0a6ee420dab949eac22e25c155,
http://review.gluster.org/11769, BUG: 1245331

Change-Id: Iba1efb0bc578ea4a5e9bf76b7bd93dc1be9eba44
BUG: 1283302
Signed-off-by: Kaleb S KEITHLEY 
Reviewed-on: http://review.gluster.org/12646
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Niels de Vos

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

extras: fix deprecation warining in checkpatch.pl

2016-01-10T10:58:42+00:00

Left braces in patterns need to be escaped.
Otherwise, for perl >= 5.16, we get a warning:
"Unescaped left brace in regex is deprecated, passed through in regex;"
This patch fixes the relevant braces.

Hence perl -c ./examples/checkpatch.pl is clean again.

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

(cherry picked from commit 2e9376a2f1b992d3649dd1d5a8e844b4c031ef3c)

Change-Id: I2a38e8e2d0652af519bf139ec046edc42c5e5356
BUG: 1290534
Signed-off-by: Michael Adam 
Reviewed-on: http://review.gluster.org/12942
Tested-by: Gluster Build System 
Reviewed-by: Anoop C S 
Reviewed-by: Raghavendra Talur 
Reviewed-by: Niels de Vos