glusterfs.git/geo-replication/src/gverify.sh, branch v3.7.2

geo-rep/gverify: Ignore .trashcan while checking slave is empty.

2015-03-20T17:27:05+00:00

With trash translator, '.trashcan' is created in gluster volume
during init. So geo-rep create used to fail, with slave not
being empty. The gverify script should ignore '.trashcan' while
checking whether slave is empty.

Change-Id: Ib7ee265c6aa99b63c7ccf103747d47a6f756ad35
BUG: 1203086
Signed-off-by: Kotresh HR 
Reviewed-on: http://review.gluster.org/9921
Reviewed-by: Aravinda VK 
Tested-by: Gluster Build System 
Reviewed-by: Venky Shankar 
Tested-by: Venky Shankar

Regression test portability: mktemp

2014-08-20T20:46:44+00:00

Linux mktemp accepts to run without a template, NetBSD mandates it. Since
the template option has the same syntax, add it everywhere. While there,
also do this in scripts outside of regression testing.

BUG: 764655
Change-Id: I3ec140afbc9009257c81a56d77afcc21fef74cc4
Signed-off-by: Emmanuel Dreyfus 
Reviewed-on: http://review.gluster.org/8432
Tested-by: Gluster Build System 
Reviewed-by: Harshavardhana 
Tested-by: Harshavardhana

geo-rep/gverify: Never use ping to check for host reachability

2014-06-12T12:48:23+00:00

On many linux distributions with iptables enabled, ICMP traffic
is usually dropped even when port 22 is open for SSH service

So practically `ping` is an unreliable command

~~~
root@rhs1:/var/log/glusterfs # gluster volume geo-replication geo-test \
                          17.16.10.1::geo-test-slave create push-pem force
172.16.10.1 not reachable.
geo-replication command failed
~~~

~~~
root@rhs1:/var/log/glusterfs # ping 172.16.10.1
PING rhs2.sjc.redhat.com (172.16.10.1) 56(84) bytes of data.
From rhs2.sjc.redhat.com (172.16.10.1) icmp_seq=1 Destination Host Prohibited
...
...
~~~

~~~
root@rhs2:/var/log/glusterfs # service iptables status | grep 22
4    ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           tcp dpt:22
root@rhs2:/var/log/glusterfs # service iptables status | grep icmp-host-prohibited
25   REJECT     all  --  0.0.0.0/0            0.0.0.0/0           reject-with icmp-host-prohibited
~~~

Change-Id: I33206ca071aa5d755c0762f7c486da222ec3c7db
BUG: 1105337
Signed-off-by: Harshavardhana 
Reviewed-on: http://review.gluster.org/7997
Tested-by: Gluster Build System 
Reviewed-by: Aravinda VK 
Reviewed-by: Venky Shankar 
Tested-by: Venky Shankar

glusterd/geo-rep: Not setting the user name as the user group by default

2014-06-05T07:07:35+00:00

Also removing multiple mounts in gverify.sh

Change-Id: I1567a9f711222c5f571a12f7c4ab49cef32d60c9
BUG: 1101948
Signed-off-by: Avra Sengupta 
Reviewed-on: http://review.gluster.org/7911
Tested-by: Gluster Build System 
Reviewed-by: Kotresh HR 
Reviewed-by: Venky Shankar 
Tested-by: Venky Shankar

glusterd/geo-rep: Creating .ssh dir with right ownership

2014-05-26T02:49:31+00:00

Also adding -P option to the usage of df for portability in gverify.sh

Change-Id: I0be19d26ea63769a934c6ccbfc04ef80768ebc9a
BUG: 1099041
Signed-off-by: Avra Sengupta 
Reviewed-on: http://review.gluster.org/7812
Reviewed-by: Kotresh HR 
Tested-by: Gluster Build System 
Reviewed-by: Venky Shankar 
Tested-by: Venky Shankar 
Reviewed-by: Aravinda VK

glusterd/geo-rep: Allow gverify.sh and S56glusterd-geo-rep-create-post.sh

2014-05-14T17:24:25+00:00

to operate for non-root privileged slave volume

Mounting the slave-volume on local node, to perform disk checks
in order to allow gverify.sh to operate for non-root privileged
slave volume

Allowing the hook script S56glusterd-geo-rep-create-post.sh
to operate for non-root privileged slave volume

Modified peer_add_secret_pub.in to accept username as argument
and add the pem keys to the users's_home_dir/.ssh/authorized_keys

Wrote set_geo_rep_pem_keys.sh which accepts username as argument
and copies the pem keys from the user's home directory to
$GLUSTERD_WORKING_DIR/geo-replication/ and then copies the keys
to other nodes in the cluster and add them to the respective
authorized keys. The script takes as argument the user name and
assumes that the user will be present in all the nodes in the
cluster. It is not needed for root.

To summarize:
For a privileged slave user, execute the following on master node as super user:
gluster system:: execute gsec_create
gluster volume geo-replication  [root@]:: create push_pem

For a non-privileged slave user execute the following on master node as super user:
gluster system:: execute gsec_create
gluster volume geo-replication  @:: create push_pem
then on the slave node execute the following as super user:
/usr/local/libexec/glusterfs/set_geo_rep_pem_keys.sh 

BUG: 1077452
Change-Id: I88020968aa5b13a2c2ab86b1d6661b60071f6f5e
Signed-off-by: Avra Sengupta 
Reviewed-on: http://review.gluster.org/7744
Tested-by: Gluster Build System 
Reviewed-by: Venky Shankar 
Tested-by: Venky Shankar

gsyncd / geo-rep: Partial support for Non-root geo-replication.

2014-05-14T17:24:01+00:00

This patch enables geo-replication to be run as an unprivileged
user. As of now, this is just the partial support, but is very
close to achieve full functionality.

Current limitation
* Geo-replication executed Gluster CLI commands on the slave
  via SSH. On a non-root setup, Gluster CLI would run as an
  unprivileged user, failing to execute the command. As a
  workaround (for testing), setuid(2) Gluster CLI executable
  or use the glusterd option to accept commands by unprivileged
  CLI process. The nature of cli commands are "system::"
  commands (for key management) and remote volume info fetching.

Remote volume info fetching has been modified to use --remote-host
gluster cli option rather than ssh and remote cli execution.

Change-Id: Ica89e2ba9b7f48fd6e1c876c477d7822dc693617
BUG: 1077452
Signed-off-by: Venky Shankar 
Reviewed-on: http://review.gluster.org/7658
Tested-by: Gluster Build System

gverify: Correcting variable names

2014-02-08T02:59:33+00:00

Change-Id: I851a50e0ebb7554b821fb591375bb6ebd6240ade
BUG: 1036539
Signed-off-by: Avra Sengupta 
Reviewed-on: http://review.gluster.org/6939
Reviewed-by: Venky Shankar 
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

geo-replication: gverify should use disk_size and available_size

2014-02-06T15:31:23+00:00

"commit ef4bb42382a5c9c3ca0907136669a659c2a20311" was incomplete since
reduction in sizes doesn't really have any affect on the problem when
disks sizes are similar.

Actual fix is to verify disk_size and then verify available_size

Change-Id: Idb57f606df229c0bdaeda8852c74e84d29109ffc
BUG: 1020154
Signed-off-by: Harshavardhana 
Reviewed-on: http://review.gluster.org/6844
Tested-by: Gluster Build System 
Reviewed-by: Venky Shankar

geo-rep: Fix no error when slave size less than master size

2014-01-23T17:41:10+00:00

in df command output, default block-size is 1K, but BUFFER_SIZE is
in bytes, so verify will succeed even if slave size is less than
master size.

Added -B1 to df command(that is --block-size=1) to get all values in
bytes.

BUG: 1056518
Change-Id: I2384d2a6f2505d967e0538b95fbf111c15b26f30
Signed-off-by: Aravinda VK 
Reviewed-on: http://review.gluster.org/6746
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur