glusterfs.git/extras/ganesha/scripts/ganesha-ha.sh, branch v3.7.3

NFS-Ganesha : Add-node does not copy "exports" directory correctly

2015-07-15T00:56:34+00:00

Add-node logic has to copy the "exports" directory into the
new node in the same path. There was an error in copying to the correct
path. Fixing it.

This is a backport of the patch merged upstream,
http://review.gluster.org/#/c/11618/

Change-Id: I76d8679966372d6fcee2dcf38bc20c9b5c522132
BUG: 1242192
Signed-off-by: Meghana M 
Reviewed-on: http://review.gluster.org/11635
Tested-by: NetBSD Build System 
Tested-by: Gluster Build System 
Reviewed-by: Kaleb KEITHLEY

NFS-Ganesha : Export fails on RHEL 7.1

2015-07-10T17:41:17+00:00

We grep for CONFFILE parameter in "/etc/syconfig/ganesha"
file to find out the path of the ganesha config file.
In RHEL 7.1, this parameter does not exist in the file and
we can't find out the ganesha config file. Export
fails invariably due to this. Changing this pattern to
a more generic one and default it to "/etc/ganesha/ganesha.conf"

This patch is a backport of the fix merged upstream,
http://review.gluster.org/#/c/11594/

Change-Id: Ia0f87f964a5771b97d9077f17a0387d7a01e02b6
BUG: 1241885
Signed-off-by: Meghana Madhusudhan 
Reviewed-on: http://review.gluster.org/11621
Tested-by: Gluster Build System 
Reviewed-by: Kaleb KEITHLEY

common-ha: ganesha-ha.sh status tries to read ganesha-ha.conf

2015-07-09T15:17:09+00:00

status doesn't need to read the config

backport of
> Change-Id: Id02252abe52820dbc263f4a880bde72a23b121bd
> BUG: 1241133
> http://review.gluster.org/#/c/11581/

Change-Id: I036fd3072f38958373b1a85b0dc5c97245a72af4
BUG: 1241134
Signed-off-by: Kaleb S. KEITHLEY 
Reviewed-on: http://review.gluster.org/11582
Tested-by: Gluster Build System 
Tested-by: NetBSD Build System

common-ha: Fix '/var/lib/nfs/statd/state' path creation

2015-07-01T10:04:41+00:00

'/var/lib/nfs/statd/state' which contains NSM state number
should be a file instead of directory.

This is a backport of the below fix -
http://review.gluster.org/#/c/11468/

Change-Id: Id008b4f4dd810fe6d6b4d2599cbc0b488010384b
BUG: 1238057
Signed-off-by: Soumya Koduri 
Reviewed-on: http://review.gluster.org/11468
Reviewed-by: Kaleb KEITHLEY 
Reviewed-by: Niels de Vos 
Reviewed-on: http://review.gluster.org/11476
Tested-by: NetBSD Build System 
Tested-by: Gluster Build System

common-ha: fix delete-node

2015-06-26T19:36:09+00:00

delete-node is a designed to be "disruptive"

surgically delete a node from the config and stop nfs-ganesh on that
node.

finish the implementation and fix a few minor issues

>-Id: I964bb72a76ee635b5fc484ec5b541e69eeececcd
> BUG: 1234474
> http://review.gluster.org/11353

Change-Id: Ic06952df8f42f80cfeb82d419757a8b99dff275a
BUG: 1234584
Signed-off-by: Kaleb S. KEITHLEY 
Reviewed-on: http://review.gluster.org/11427
Tested-by: Gluster Build System

NFS-Ganesha : Implement refresh-config

2015-06-25T01:08:39+00:00

It is important that we give an automatic way of refreshing the config
when the user has changed the export file manually.
Without this, the user will be forced to restart the server.
Implementing refresh_config by using dbus signals to unexport
and export the same export dynamically.
Making a few changes to make sure that "--help"
doesn't throw unnecessary error messages.

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

Change-Id: I2e17edeffc191e2cc30a328b2999e1a04f5bc498
BUG: 1235258
Signed-off-by: Meghana M 
Reviewed-on: http://review.gluster.org/11380
Tested-by: Gluster Build System 
Tested-by: NetBSD Build System 
Reviewed-by: Kaleb KEITHLEY

common-ha : Fixing add node operation

2015-06-22T09:37:11+00:00

Resource create for the added node referenced a variable
new_node that was never passed. This led to a wrong schema
type in the cib file and hence the added node always ended
up in failed state. And also, resources were wrongly
created twice and led to more errors. I have fixed the variable
name and deleted the repetitive invocation of the recreate-resource
function.

The new node has to be added to the existing ganesha-ha config
file for correct behaviour during subsequent add-node operations.
This edited file has to be copied to all the other cluster nodes.
I have added a fix for this as well.

This is a backport of the fix that is merged on master,
http://review.gluster.org/#/c/11316/5

Change-Id: I21e3fcffe8274986be53766e12a2c049eaa2da09
BUG: 1234216
Signed-off-by: Meghana M 
Reviewed-on: http://review.gluster.org/11337
Tested-by: NetBSD Build System 
Tested-by: Gluster Build System 
Reviewed-by: soumya k 
Reviewed-by: Kaleb KEITHLEY

common-ha: cluster setup issues on RHEL7

2015-06-19T09:19:54+00:00

 * use --name on RHEL7 (later versions of pcs drop --name) we guessed
   wrong and did not get the version that dropped use of --name option
 * more robust config file param parsing for n/v with ""s in the value
   after not sourcing the config file
 * pid file fix. RHEL6 init.d adds -p /var/run/ganesha.nfsd.pid to
   cmdline options. RHEL7 systemd does not, so defaults to
   /var/run/ganesha.pid.

Change-Id: I2236d41c8a87e4ead082274dddec19307d1f4db9
BUG: 1232333
Signed-off-by: Kaleb S. KEITHLEY 
Reviewed-on: http://review.gluster.org/11258
Tested-by: Gluster Build System 
Tested-by: NetBSD Build System 
Reviewed-by: soumya k 
Reviewed-by: Meghana M

common-ha: cluster HA setup sometimes fails

2015-06-18T17:17:11+00:00

the "s in the VIP_foo="x.x.x.x" lines are problematic now that the
config file isn't sourced.

Revised to also handle names containing '-', e.g. host-11, and FQNs,
e.g. host-11.lab.gluster.org

backport of
> Change-Id: I1a52afbf398a024cdff851d0c415d8363f699c90
> BUG: 1232001
> Signed-off-by: Kaleb S. KEITHLEY 
> http://review.gluster.org/#/c/11281/

Change-Id: Icef306554911b2238b230700f1866a441eaf1189
BUG: 1232002
Signed-off-by: Kaleb S. KEITHLEY 
Reviewed-on: http://review.gluster.org/11299
Tested-by: Gluster Build System 
Reviewed-by: Meghana M 
Reviewed-by: soumya k

common-ha: cluster HA setup sometimes fails

2015-06-16T15:37:08+00:00

the "s in the VIP_foo="x.x.x.x" lines are problematic now that
the config file isn't sourced.

(A short term work-around is to simply eliminate them.)


> Change-Id: I65f375f2d3b8453adb45dc3dbbc7d3fb07cf85d0 
> BUG: 1232001 
> Signed-off-by: Kaleb S. KEITHLEY  
> http://review.gluster.org/#/c/11237/

Change-Id: Ib626795af5be0d23524271d32923ed4a0e7079f5
BUG: 1232002
Signed-off-by: Kaleb S. KEITHLEY 
Reviewed-on: http://review.gluster.org/11238
Reviewed-by: soumya k 
Reviewed-by: Niels de Vos