gluster: GlusterFS Volume Snapshot Feature

This is the initial patch for the Snapshot feature. Current patch
includes following features:
* Snapshot create
* Snapshot delete
* Snapshot restore
* Snapshot list
* Snapshot info
* Snapshot status
* Snapshot config

Change-Id: I2f46920c0d61c515f6a60e0f8b46fff886d9f6a9
BUG: 1061685
Signed-off-by: shishir gowda <sgowda@redhat.com>
Signed-off-by: Sachin Pandit <spandit@redhat.com>
Signed-off-by: Vijaikumar M <vmallika@redhat.com>
Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
Signed-off-by: Rajesh Joseph <rjoseph@redhat.com>
Signed-off-by: Joseph Fernandes <josferna@redhat.com>
Signed-off-by: Avra Sengupta <asengupt@redhat.com>
Reviewed-on: http://review.gluster.org/7128
Tested-by: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Vijay Bellur <vbellur@redhat.com>

1 files changed, 0 insertions, 106 deletions

diff --git a/tests/basic/volume-locks.t b/tests/basic/volume-locks.t
deleted file mode 100755
index b9e94b7e166..00000000000
--- a/tests/basic/volume-locks.t
+++ /dev/null
@@ -1,106 +0,0 @@
-#!/bin/bash
-
-. $(dirname $0)/../include.rc
-. $(dirname $0)/../cluster.rc
-
-function check_peers {
-        $CLI_1 peer status | grep 'Peer in Cluster (Connected)' | wc -l
-}
-
-function volume_count {
-        local cli=$1;
-        if [ $cli -eq '1' ] ; then
-                $CLI_1 volume info | grep 'Volume Name' | wc -l;
-        else
-                $CLI_2 volume info | grep 'Volume Name' | wc -l;
-        fi
-}
-
-function volinfo_field()
-{
-    local vol=$1;
-    local field=$2;
-
-    $CLI_1 volume info $vol | grep "^$field: " | sed 's/.*: //';
-}
-
-function two_diff_vols_create {
-        # Both volume creates should be successful
-        $CLI_1 volume create $V0 $H1:$B1/$V0 $H2:$B2/$V0 $H3:$B3/$V0 &
-        $CLI_2 volume create $V1 $H1:$B1/$V1 $H2:$B2/$V1 $H3:$B3/$V1
-}
-
-function two_diff_vols_start {
-        # Both volume starts should be successful
-        $CLI_1 volume start $V0 &
-        $CLI_2 volume start $V1
-}
-
-function two_diff_vols_stop_force {
-        # Force stop, so that if rebalance from the
-        # remove bricks is in progress, stop can
-        # still go ahead. Both volume stops should
-        # be successful
-        $CLI_1 volume stop $V0 force &
-        $CLI_2 volume stop $V1 force
-}
-
-function same_vol_remove_brick {
-
-        # Running two same vol commands at the same time can result in
-        # two success', two failures, or one success and one failure, all
-        # of which are valid. The only thing that shouldn't happen is a
-        # glusterd crash.
-
-        local vol=$1
-        local brick=$2
-        $CLI_1 volume remove-brick $1 $2 start &
-        $CLI_2 volume remove-brick $1 $2 start
-}
-
-cleanup;
-
-TEST launch_cluster 3;
-TEST $CLI_1 peer probe $H2;
-TEST $CLI_1 peer probe $H3;
-
-EXPECT_WITHIN 20 2 check_peers
-
-two_diff_vols_create
-EXPECT 'Created' volinfo_field $V0 'Status';
-EXPECT 'Created' volinfo_field $V1 'Status';
-
-two_diff_vols_start
-EXPECT 'Started' volinfo_field $V0 'Status';
-EXPECT 'Started' volinfo_field $V1 'Status';
-
-same_vol_remove_brick $V0 $H2:$B2/$V0
-# Checking glusterd crashed or not after same volume remove brick
-# on both nodes.
-EXPECT_WITHIN 20 2 check_peers
-
-same_vol_remove_brick $V1 $H2:$B2/$V1
-# Checking glusterd crashed or not after same volume remove brick
-# on both nodes.
-EXPECT_WITHIN 20 2 check_peers
-
-$CLI_1 volume set $V0 diagnostics.client-log-level DEBUG &
-$CLI_1 volume set $V1 diagnostics.client-log-level DEBUG
-kill_glusterd 3
-$CLI_1 volume status $V0
-$CLI_2 volume status $V1
-$CLI_1 peer status
-EXPECT_WITHIN 20 1 check_peers
-EXPECT 'Started' volinfo_field $V0 'Status';
-EXPECT 'Started' volinfo_field $V1 'Status';
-
-TEST $glusterd_3
-$CLI_1 volume status $V0
-$CLI_2 volume status $V1
-$CLI_1 peer status
-#EXPECT_WITHIN 20 2 check_peers
-#EXPECT 'Started' volinfo_field $V0 'Status';
-#EXPECT 'Started' volinfo_field $V1 'Status';
-#two_diff_vols_stop_force
-#EXPECT_WITHIN 20 2 check_peers
-cleanup;