[Gluster-devel] Snapshot Scheduler

[Avra Sengupta]

Thanks Alastair for the feedback. As of today we have auto-delete which 
when enabled deletes the oldest snapshot on exceeding the 
snap-max-soft-limit. Is this what you were trying to achieve, or were 
you thinking of more of a policy based approach, where like creation, 
deletion policies can be set, to target specific snapshots?


On 07/12/2016 11:45 PM, Alastair Neil wrote:
> I don't know if I did something wrong, but I found the location that 
> the scheduler wanted the shared storage was problematic as I recall it 
> was under /run/gluster/snaps.  On CentOS 7 this failed to mount on 
> boot.  I hacked the scheduler to use a location under /var/lib.
>
> I also think there needs to be a way to schedule the removal of snapshots.
>
> -Alastair
>
>
> On 8 July 2016 at 06:01, Avra Sengupta <asengupt at redhat.com 
> <mailto:asengupt at redhat.com>> wrote:
>
>     Hi,
>
>     Snaphsots in gluster have a scheduler, which relies heavily on
>     crontab, and the shared storage. I would like people using this
>     scheduler, or for people to use this scheduler, and provide us
>     feedback on it's experience. We are looking for feedback on ease
>     of use, complexity of features, additional feature support etc.
>
>     It will help us in deciding if we need to revamp the existing
>     scheduler, or maybe rethink relying on crontab and re-writing our
>     own, thus providing us more flexibility. Thanks.
>
>     Regards,
>     Avra
>     _______________________________________________
>     Gluster-devel mailing list
>     Gluster-devel at gluster.org <mailto:Gluster-devel at gluster.org>
>     http://www.gluster.org/mailman/listinfo/gluster-devel
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.gluster.org/pipermail/gluster-devel/attachments/20160713/bcc97a4e/attachment-0001.html>