[Gluster-users] User-serviceable snapshots design

[Sobhan Samantaray]

----- Original Message -----
From: "Varun Shastry" <vshastry at redhat.com>
To: "Sobhan Samantaray" <ssamanta at redhat.com>, anands at redhat.com
Cc: gluster-devel at gluster.org, "gluster-users" <gluster-users at gluster.org>, "Anand Avati" <aavati at redhat.com>
Sent: Thursday, May 8, 2014 11:16:11 AM
Subject: Re: [Gluster-users] User-serviceable snapshots design

Hi Sobhan,

On Wednesday 07 May 2014 09:12 PM, Sobhan Samantaray wrote:
> I think its a good idea to include the auto-remove of the snapshots based on the time or space as threshold as mentioned in below link.
>
> http://www.howtogeek.com/110138/how-to-back-up-your-linux-system-with-back-in-time/


I think this feature is already implemented (partially?) as part of the 
snapshot feature.


The feature proposed here only concentrates on the user serviceability 
of the snapshots taken.

I understand that it would be part of core snapshot feature. I was talking w.r.t Paul's suggestion of scheduling the snapshot based on threshold levels in snapshot which will be part of phase-2.
 
- Varun Shastry

>
> ----- Original Message -----
> From: "Anand Subramanian" <ansubram at redhat.com>
> To: "Paul Cuzner" <pcuzner at redhat.com>
> Cc: gluster-devel at gluster.org, "gluster-users" <gluster-users at gluster.org>, "Anand Avati" <aavati at redhat.com>
> Sent: Wednesday, May 7, 2014 7:50:30 PM
> Subject: Re: [Gluster-users] User-serviceable snapshots design
>
> Hi Paul, that is definitely doable and a very nice suggestion. It is just that we probably won't be able to get to that in the immediate code drop (what we like to call phase-1 of the feature). But yes, let us try to implement what you suggest for phase-2. Soon :-)
>
> Regards,
> Anand
>
> On 05/06/2014 07:27 AM, Paul Cuzner wrote:
>
>
>
> Just one question relating to thoughts around how you apply a filter to the snapshot view from a user's perspective.
>
> In the "considerations" section, it states - "We plan to introduce a configurable option to limit the number of snapshots visible under the USS feature."
> Would it not be possible to take the meta data from the snapshots to form a tree hierarchy when the number of snapshots present exceeds a given threshold, effectively organising the snaps by time. I think this would work better from an end-user workflow perspective.
>
> i.e.
> .snaps
> \/ Today
> +-- snap01_20140503_0800
> +-- snap02_ 20140503_ 1400
>> Last 7 days
>> 7-21 days
>> 21-60 days
>> 60-180days
>> 180days
>
>
>
>
>
>
> From: "Anand Subramanian" <ansubram at redhat.com>
> To: gluster-devel at nongnu.org , "gluster-users" <gluster-users at gluster.org>
> Cc: "Anand Avati" <aavati at redhat.com>
> Sent: Saturday, 3 May, 2014 2:35:26 AM
> Subject: [Gluster-users] User-serviceable snapshots design
>
> Attached is a basic write-up of the user-serviceable snapshot feature
> design (Avati's). Please take a look and let us know if you have
> questions of any sort...
>
> We have a basic implementation up now; reviews and upstream commit
> should follow very soon over the next week.
>
> Cheers,
> Anand
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://supercolony.gluster.org/mailman/listinfo/gluster-users
>
>
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://supercolony.gluster.org/mailman/listinfo/gluster-users
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://supercolony.gluster.org/mailman/listinfo/gluster-users