glusterfs.git/extras, branch release-3.9

extras: Add more options to group virt

2017-02-27T05:00:28+00:00

        Backport of: https://review.gluster.org/16577

Apart from some of the option configurations already listed
in the group-virt.example file, we also recommend that the
users set certain other options added by this patch for
VM use-case. This also helps Gluster-oVirt users in configuring
virt options for new volumes at the click of a button as opposed
to setting them manually through volume-set command.

Change-Id: I3a0c72b514e717268ccc4d02f23660e1d19ce232
BUG: 1424932
Signed-off-by: Krutika Dhananjay 
Reviewed-on: https://review.gluster.org/16682
NetBSD-regression: NetBSD Build System 
Smoke: Gluster Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Pranith Kumar Karampuri

common-ha: unable to start HA, Connection Error

2017-02-26T19:14:44+00:00

See BZ 1284404. pcsd behavior has changed and pcsd will not accept
connections until SSL certificates have fully propagated throughout
all the nodes

HA devels suggest a 12 second delay between the `pcs cluster setup ...`
and the `pcs cluster start --all`

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

common-ha: All statd related files need to be owned by rpcuser

2017-01-19T23:32:03+00:00

Statd service is started as rpcuser by default. Hence the
files/directories needed by it under '/var/lib/nfs' should be
owned by the same user.

Note: This change is not in mainline as the cluster-bits
are being moved to storehaug project -
http://review.gluster.org/#/c/16349/
http://review.gluster.org/#/c/16333/

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

eventsapi: JSON output and different error codes

2016-12-29T06:27:15+00:00

JSON outputs are added to all commands, use `--json` to
get JSON output.

Following error codes are added to differenciate between errors.
Any other Unknown errors will have return code 1

ERROR_SAME_CONFIG             = 2
ERROR_ALL_NODES_STATUS_NOT_OK = 3
ERROR_PARTIAL_SUCCESS         = 4
ERROR_WEBHOOK_ALREADY_EXISTS  = 5
ERROR_WEBHOOK_NOT_EXISTS      = 6
ERROR_INVALID_CONFIG          = 7
ERROR_WEBHOOK_SYNC_FAILED     = 8
ERROR_CONFIG_SYNC_FAILED      = 9

Also hidden `node-` commands in the help message.

> Reviewed-on: http://review.gluster.org/15867
> Smoke: Gluster Build System 
> Reviewed-by: Prashanth Pai 
> NetBSD-regression: NetBSD Build System 
> CentOS-regression: Gluster Build System 

BUG: 1400845
Change-Id: I962b5435c8a448b4573059da0eae42f3f93cc97e
Signed-off-by: Aravinda VK 
(cherry picked from commit da71bdcf82a8dc71a1170ad3f190702fa49d2838)
Reviewed-on: http://review.gluster.org/16008
Reviewed-by: Prashanth Pai 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Smoke: Gluster Build System

ganesha/scripts : Prevent removal of entries in ganesha.conf during deletion of a node

2016-12-22T22:04:04+00:00

Upstream reference :
>Change-Id: Ia6c653eeb9bef7ff4107757f845218c2316db2e4
>BUG: 1406249
>Signed-off-by: Jiffin Tony Thottan 
>Reviewed-on: http://review.gluster.org/16209
>Smoke: Gluster Build System 
>NetBSD-regression: NetBSD Build System 
>CentOS-regression: Gluster Build System 
>Reviewed-by: soumya k 
>(cherry picked from commit 8b42e1b5688f8600086ecc0e33ac4abf5e7c2772)

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

common-ha: Correct the VIP assigned to the new node added

2016-12-22T15:50:02+00:00

There is a regression introduced with patch#16115. An incorrect
VIP gets assigned to the new node being added to the cluster.
This patch fixes the same.

This is backport of below mainline patch:

http://review.gluster.org/16213

> Change-Id: I468c7d16bf7e4efa04692db83b1c5ee58fbb7d5f
> BUG: 1406410
> Signed-off-by: Soumya Koduri 

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

common-ha: add node create new node dirs in shared storage

2016-12-22T14:20:19+00:00

When adding a node to the ganesha HA cluster, create the directory
tree in shared storage for the added node and create sets of symlinks
to match what is/was created for the other nodes.  I.e. in a four
node cluster the new node needs a set of links to the four existing
nodes:
 /run/gluster/shared/nfs-ganesha/$new/nfs/{ganesha,statd}/$e1 -> e1
 /run/gluster/shared/nfs-ganesha/$new/nfs/{ganesha,statd}/$e2 -> e2
 /run/gluster/shared/nfs-ganesha/$new/nfs/{ganesha,statd}/$e3 -> e3
 /run/gluster/shared/nfs-ganesha/$new/nfs/{ganesha,statd}/$e4 -> e4
and all the existing nodes need links added for the new node:
 /run/gluster/shared/nfs-ganesha/$e1/nfs/{ganesha,statd}/$new -> new
 /run/gluster/shared/nfs-ganesha/$e2/nfs/{ganesha,statd}/$new -> new
 /run/gluster/shared/nfs-ganesha/$e3/nfs/{ganesha,statd}/$new -> new
 /run/gluster/shared/nfs-ganesha/$e5/nfs/{ganesha,statd}/$new -> new

Likewise when deleting, remove the dir and symlinks.

original change http://review.gluster.org/16036
original change release-3.9 http://review.gluster.org/16170
master change http://review.gluster.org/16216
master BZ 1400613

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

ganesha/scripts : find export id for already exported volume in S31ganesha-start.sh

2016-12-19T10:06:06+00:00

Upstream reference :
>Change-Id: Iada90ed215966d3f526fa20aa5359b67f25a6944
>BUG: 1401822
>Signed-off-by: Jiffin Tony Thottan 
>Reviewed-on: http://review.gluster.org/16037
>Smoke: Gluster Build System 
>NetBSD-regression: NetBSD Build System 
>CentOS-regression: Gluster Build System 
>Reviewed-by: soumya k 
>Reviewed-by: Kaleb KEITHLEY 
>(cherry picked from commit 58a58e706da73ee751b7cd98c23e6675667fefdb)

Change-Id: Iada90ed215966d3f526fa20aa5359b67f25a6944
BUG: 1403144
Signed-off-by: Jiffin Tony Thottan 
Reviewed-on: http://review.gluster.org/16093
CentOS-regression: Gluster Build System 
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
Reviewed-by: Kaleb KEITHLEY

common-ha: add node create new node dirs in shared storage

2016-12-18T12:44:01+00:00

When adding a node to the ganesha HA cluster, create the directory
tree in shared storage for the added node and create sets of symlinks
to match what is/was created for the other nodes.  I.e. in a four
node cluster the new node needs a set of links to the four existing
nodes:
 /run/gluster/shared/nfs-ganesha/$new/nfs/{ganesha,statd}/$e1 -> e1
 /run/gluster/shared/nfs-ganesha/$new/nfs/{ganesha,statd}/$e2 -> e2
 /run/gluster/shared/nfs-ganesha/$new/nfs/{ganesha,statd}/$e3 -> e3
 /run/gluster/shared/nfs-ganesha/$new/nfs/{ganesha,statd}/$e4 -> e4
and all the existing nodes need links added for the new node:
 /run/gluster/shared/nfs-ganesha/$e1/nfs/{ganesha,statd}/$new -> new
 /run/gluster/shared/nfs-ganesha/$e2/nfs/{ganesha,statd}/$new -> new
 /run/gluster/shared/nfs-ganesha/$e3/nfs/{ganesha,statd}/$new -> new
 /run/gluster/shared/nfs-ganesha/$e5/nfs/{ganesha,statd}/$new -> new

Likewise when deleting, remove the dir and symlinks.

master BZ: 1400613

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

common-ha: explicitly set udpu transport for corosync

2016-12-15T15:54:24+00:00

On RHEL7 corosync uses udpu (udp unicast) by default. On RHEL6 the
default is (now) udp multi-cast. In network environments that don't
support udp multi-cast this causes the ever growing lists of
[TOTEM ] Retransmit errors.

Always specifying --transport udpu is thus a no-op on RHEL7.

Using the same transport on both RHEL6 and RHEL7 may (or may not
give similar behavior and performance--it's hard to say.

It remains a mystery why things have always worked on RHEL6 prior to
now. Further investigation is required to uncover why this is the
case.

main http://review.gluster.org/16122
main BZ 1404410

Change-Id: I4d0de97fe4425c47f249beaaf51aeca3e91731fa
BUG: 1405002
Signed-off-by: Kaleb S. KEITHLEY 
Reviewed-on: http://review.gluster.org/16139
Smoke: Gluster Build System 
Reviewed-by: soumya k 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System