diff options
author | Joseph Fernandes <josferna@redhat.com> | 2014-04-14 19:18:41 +0530 |
---|---|---|
committer | Vijay Bellur <vbellur@redhat.com> | 2014-05-02 09:27:46 -0700 |
commit | 0f56f0ce2d2e18fbb2eedf14e93b5a592f0005c3 (patch) | |
tree | e5cca809f024f8e31433bd5a8d22ae352b574a0e /tests/snapshot.rc | |
parent | b189bb33edc2582e53923dec51bdef0f118c3d36 (diff) |
glusterd/snapshot: Activation and De-activation of snapshot
Previously, snapshots by default were activated on creation and there was
no option to activate or deactivate them on demand.
This will allow the user to activate and deactivate on demand.
The CLI goes as follows
1) Activate the snap using a command "gluster snapshot activate <snapname> [force]"
2) Deactivate the snap using a command "gluster snapshot deactivate <snapname>"
Note: Even now the snapshot will be activated during creation.
Change-Id: I0946d800780f26c63fa1fcaf29aabc900140448f
BUG: 1061685
Signed-off-by: Joseph Fernandes <josferna@redhat.com>
Reviewed-on: http://review.gluster.org/7476
Tested-by: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Vijaikumar Mallikarjuna <vmallika@redhat.com>
Reviewed-by: Vijay Bellur <vbellur@redhat.com>
Diffstat (limited to 'tests/snapshot.rc')
-rwxr-xr-x | tests/snapshot.rc | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/tests/snapshot.rc b/tests/snapshot.rc index 37c250344f1..a208fa3d410 100755 --- a/tests/snapshot.rc +++ b/tests/snapshot.rc @@ -286,6 +286,19 @@ function snapshot_n_exists() { return $ret } +#Check for the status of snapshot for a volume +#Arg1 : <Snap Name> +function snapshot_status() +{ + local snap=$1; + + #TODO: Right now just fetches the status of the single snap volume. + #When snapshot will have multiple snap volumes, should have a + #cummulative logic for status + $CLI_1 snapshot info $snap | grep "Status" | sed 's/.*: //'; +} + + # TODO: Cleanup code duplication function volinfo_field() { |