glusterfs.git/extras/ganesha/scripts, branch release-3.10

common-ha/scripts : pass the list of servers properly to stop_ganesha_all()

2018-04-04T04:05:00+00:00

Change-Id: I6d92623cd9fb450d7a27f5acc61eca0b3cbc9b08
BUG: 1563500
Signed-off-by: Jiffin Tony Thottan

ganesha-ha: don't set SELinux booleans if SELinux is disabled

2017-09-16T13:01:48+00:00

semanage commands inside ganesha-ha.sh script will fail if selinux is
Disabled. This patch introduces a check if selinux is enabled or not,
and subsequently run semange commands only on selinux enabled systems.

Change-Id: Ibee61cbb1d51a73e6c326b49bac5c7ce06feb310
BUG: 1490909
Signed-off-by: Ambarish 
Reviewed-on: https://review.gluster.org/18264
Reviewed-by: Niels de Vos 
Smoke: Gluster Build System 
Reviewed-by: Kaleb KEITHLEY 
Reviewed-by: jiffin tony Thottan 
Reviewed-by: Daniel Gryniewicz 
CentOS-regression: Gluster Build System

common-ha: enable and disable selinux gluster_use_execmem

2017-07-28T12:28:41+00:00

Starting in Fedora 26 and RHEL 7.4 there are new targeted policies in
selinux which include a tuneable to allow glusterd->ganesha-ha.sh->pcs
to access the pcs config, i.e. gluster-use-execmem.

Note. rpm doesn't have a way to distinguish between RHEL 7.3 or 7.4
or between 3.13.1-X and 3.13.1-Y so it can't be enabled for RHEL at
this time.

/usr/sbin/semanage is in policycoreutils-python in RHEL (versus
policycoreutils-python-utils in Fedora.)

Requires selinux-policy >= 3.13.1-160 in RHEL7. The corresponding
version in Fedora 26 seems to be selinux-policy-3.13.1-259 or so. (Maybe
earlier versions, but that's what was in F26 when I checked.)

Change-Id: Ic474b3f7739ff5be1e99d94d00b55caae4ceb5a0
BUG: 1471917
Signed-off-by: Kaleb S. KEITHLEY 
Reviewed-on: https://review.gluster.org/17806
Smoke: Gluster Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: soumya k 
Reviewed-by: Atin Mukherjee

common-ha: surviving ganesha.nfsd not put in grace on fail-over

2017-06-14T11:46:35+00:00

Behavior change is seen in new HA in RHEL 7.4 Beta. Up to now clone
RAs have been created with "pcs resource create ... meta notify=true".
Their notify method is invoked with pre-start or post-stop when one of
the clone RAs is started or stopped.

In 7.4 Beta the notify method we observe that the notify method is not
invoked when one of the clones is stopped (or started).

Ken Gaillot, one of the pacemaker devs, wrote:
  With the above command, pcs puts the notify=true meta-attribute
  on the primitive instead of the clone. Looking at the pcs help,
  that seems expected (--clone notify=true would put it on the clone,
  meta notify=true puts it on the primitive). If you drop the "meta"
  above, I think it will work again.

And indeed his suggested fix does work on both RHEL 7.4 Beta and RHEL
7.3 and presumably Fedora.

Change-Id: Idbb539f1366df6d39f77431c357dff4e53a2df6d
BUG: 1461019
Signed-off-by: Kaleb S. KEITHLEY 
Reviewed-on: https://review.gluster.org/17534
Smoke: Gluster Build System 
Reviewed-by: soumya k 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System

common-ha: adding a node to existing cluster failed to start pacemaker

2017-05-17T09:33:56+00:00

`pcs cluster start` in add_node() needs to wait for SSL certs to
propagate, etc. -- just like setup.

Change-Id: I44876305630a82e471824c085ed9ac58df08caa2
BUG: 1450053
Signed-off-by: Kaleb S. KEITHLEY 
Reviewed-on: https://review.gluster.org/17255
Reviewed-by: soumya k 
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: jiffin tony Thottan

ganesha : minor improvments for commit e91cdf4 (17081)

2017-05-03T22:35:56+00:00

Change-Id: I3af13e081c5e46cc6f2c132e7a5106ac3355c850
BUG: 1443490
Signed-off-by: Jiffin Tony Thottan 
Reviewed-on: https://review.gluster.org/17152
Smoke: Gluster Build System 
Reviewed-by: soumya k 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Kaleb KEITHLEY

ganesha/scripts : remove dependency over export configuration file for unexport

2017-05-01T21:44:23+00:00

Currently unexport is performed by reading export id from volume configuration
file. So unexport has dependency over that file. This patch will unexport with
help of dbus command ShowExport. And it will only unexport the share which is
added via cli.

Change-Id: I6f3c9b2bb48f0328b18e9cc0e4b9356174afd596
BUG: 1427079
Signed-off-by: Jiffin Tony Thottan 
Reviewed-on: https://review.gluster.org/16771
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Kaleb KEITHLEY 
Reviewed-by: Raghavendra Talur

ganesha : allow refresh-config and volume export/unexport in failover state

2017-04-24T10:33:51+00:00

If ganesha is not running on one of nodes in HA cluster, then alli dbus
commands send to that ganesha server will fail. This results in both
refresh-config and volume export/unepxort failure. This change will
gracefully handle those scenarios.

Change-Id: I3f1b7b7ca98e54c273c266e56357d8e24dd1b14b
BUG: 1443490
Signed-off-by: Jiffin Tony Thottan 
Reviewed-on: https://review.gluster.org/17081
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: soumya k 
Reviewed-by: Kaleb KEITHLEY

common-ha: Use UpdateExports dbus msg for refresh-config

2017-04-24T10:33:28+00:00

In nfs-ganesha 2.4, new dbs msg type "UpdateExports" support
has been added. With this support, the exports can be re-configured
dynamically without the need to re-export the entries.

Note : This change was of part of 3.10 branching, but the commit 142ee0c
overwrites this patch. Hence resubmitting this change
Upstream reference :
>Change-Id: Iee7330d33e91db1126974a2ff46becb3764f2e5e
>BUG: 1382258
>Author:    Soumya Koduri 
>Reviewed-on: http://review.gluster.org/15617
>Smoke: Gluster Build System 
>CentOS-regression: Gluster Build System 
>NetBSD-regression: NetBSD Build System 
>Reviewed-by: Kaleb KEITHLEY 

Change-Id: Iee7330d33e91db1126974a2ff46becb3764f2e5e
BUG: 1443478
Author:    Soumya Koduri 
Signed-off-by: Jiffin Tony Thottan 
Reviewed-on: https://review.gluster.org/17080
Smoke: Gluster Build System 
Reviewed-by: soumya k 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System

ganesha/scripts : Stop ganesha process on all nodes if cluster setup fails

2017-04-24T10:32:39+00:00

During staging phase of volume option "nfs-ganesha", symlink "ganesha.conf"
will be created plus ganesha process will be started. The cluster setup
happens during commit phase of that option. So if cluster set up fails, the
ganesha process will be running on all cluster nodes.

Change-Id: Ib2cb85364b7ef5b702acb4826ffdf8e6f31a2acd
BUG: 1426156
Signed-off-by: Jiffin Tony Thottan 
Reviewed-on: https://review.gluster.org/16823
Smoke: Gluster Build System 
Tested-by: Kaleb KEITHLEY 
Reviewed-by: soumya k 
Reviewed-by: Kaleb KEITHLEY 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System