[Gluster-devel] [Gluster-users] User-serviceable snapshots design

[Anand Subramanian]

Hi Sobhan,

Thanks for the comments. It was a very quick writeup so that there is at 
least some clarity on the implementation internals. I will try to find 
time and plug in some more details.

I am not quite sure what you mean by "the default value of the option of 
uss" but am assuming its the option of turning the feature on/off? If 
so, this will be set to "off" by default initially. The admin would need 
to turn uss on for a given vol.

Thanks,
Anand

On 05/06/2014 10:08 PM, Sobhan Samantaray wrote:
> Hi Anand,
>     Thanks to come-up with the nice design. I have couple of comments.
>
> 1. It should be mention in the design the access-protocols that should be used(NFS/CIFS etc) although the requirement states that.
> 2. Consideration section:
> "Again, this is not a performance oriented feature. Rather, the goal is to allow a seamless user-experience by allowing easy and useful access to snapshotted volumes and individual data stored in those volumes".
>
> If it is something that fops performance would not be impacted due to the introduction of this feature then it should be clarified.
>
> 3. It's good to mention the default value of the option of uss.
>
> Regards
> Sobhan
>
>
> From: "Paul Cuzner" <pcuzner at redhat.com>
> To: anands at redhat.com
> Cc: gluster-devel at gluster.org, "gluster-users" <gluster-users at gluster.org>, "Anand Avati" <aavati at redhat.com>
> Sent: Tuesday, May 6, 2014 7:27:29 AM
> Subject: Re: [Gluster-devel] [Gluster-users] User-serviceable snapshots	design
>
> 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-devel mailing list
> Gluster-devel at gluster.org
> http://supercolony.gluster.org/mailman/listinfo/gluster-devel