glusterfs.git/extras/snap_scheduler/gcron.py, branch v4.0dev

snapshot/scheduler: Reload /etc/cron.d/glusterfs_snap_cron_tasks when shared storage is available

2015-06-11T07:08:17+00:00

If shared storage is not accessible, create a flag in /var/run/gluster/
So that when /etc/cron.d/glusterfs_snap_cron_tasks is
available again, the flag will tell us, to reload
/etc/cron.d/glusterfs_snap_cron_tasks

Change-Id: I41b19f57ff0b8f7e0b820eaf592b0fdedb0a5d86
BUG: 1218573
Signed-off-by: Avra Sengupta 
Reviewed-on: http://review.gluster.org/11139
Tested-by: NetBSD Build System 
Reviewed-by: Rajesh Joseph 
Reviewed-by: Krishnan Parthasarathi

snapshot/scheduler: Check if GCRON_TASKS exists before

2015-06-10T10:02:20+00:00

accessing it's mtime

Change-Id: I873c83d21620527b20d7de428d11582c5499d1af
BUG: 1228613
Signed-off-by: Avra Sengupta 
Reviewed-on: http://review.gluster.org/11138
Tested-by: NetBSD Build System 
Reviewed-by: Rajesh Joseph 
Reviewed-by: Krishnan Parthasarathi

snapshot/scheduler: Adhering to the common storage for scheduler

2015-04-10T08:20:12+00:00

Making snapshot scheduler use the common storage
shared by nfs, snapshot and geo-rep. The meta volume
should be named as gluster_shared_storage, and it
should be mounted at "/var/run/gluster/shared_storage/".

Each component(nfs, snapshot, and geo-rep) should have
their own repos inside the shared storage, and perform
their operations in the shared storage

Change-Id: I4f670bf089c80037bd2b0716ddf743f48d7411ca
BUG: 1210344
Signed-off-by: Avra Sengupta 
Reviewed-on: http://review.gluster.org/10183
Tested-by: Gluster Build System 
Reviewed-by: Aravinda VK 
Reviewed-by: Krishnan Parthasarathi 
Tested-by: Krishnan Parthasarathi

snapshot/scheduler: Don't append timestamp in scheduled snapshots

2015-04-07T13:50:45+00:00

The scheduled snapshots will now have names as follows:
Scheduled--.

Stopped appending time-stamp in scheduled snapshots because
time-stamps are appended in snapshots by default unless
explicitly asked not to. 

Therefore snapshot created from "Job1" of "test_vol" volume
will look like
Scheduled-Job1-test_vol_GMT-2015.04.02-09.43.02

Change-Id: I75b4a87d265ed55193f08153fd7ffe521cc5ef68
BUG: 1208097
Signed-off-by: Avra Sengupta 
Reviewed-on: http://review.gluster.org/10115
Tested-by: Gluster Build System 
Reviewed-by: Rajesh Joseph 
Reviewed-by: Vijay Bellur

snapshot/scheduler: Fix the snapshot create command.

2015-04-04T17:49:58+00:00

The create command being executed was sent with wrong
parameters.

Change-Id: I9b3cf23b3a02cf8309d50bf70439ad02b37f191a
BUG: 1208067
Signed-off-by: Avra Sengupta 
Reviewed-on: http://review.gluster.org/10114
Reviewed-by: Aravinda VK 
Tested-by: Gluster Build System

snapshot/scheduling: A cron based scheduler for snapshot scheduling

2015-03-19T01:31:54+00:00

GlusterFS volume snapshot provides point-in-time copy
of a GlusterFS volume. Currently, GlusterFS volume
snapshots can be easily scheduled by setting up 
cron jobs on one of the nodes in the GlusterFS
trusted storage pool. This has a single point failure (SPOF),
as scheduled jobs can be missed if the node running the cron
jobs dies.

The solution to the above problems is addressed in this patch.
The snap_scheduler.py helper script expects the user to install
the argparse python module before using it.

Further details for the same are available at:

http://www.gluster.org/community/documentation/index.php/Features/Scheduling_of_Snapshot

Change-Id: I2c357af5b7d3e66f270d20eef50cdeecdcbe15c7
BUG: 1198027
Signed-off-by: Avra Sengupta 
Signed-off-by: Aravinda VK 
Reviewed-on: http://review.gluster.org/9788
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur