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" <ansub...@redhat.com>
> To: gluster-de...@nongnu.org, "gluster-users" <gluster-us...@gluster.org>
> Cc: "Anand Avati" <aav...@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-us...@gluster.org
> http://supercolony.gluster.org/mailman/listinfo/gluster-users
_______________________________________________
Gluster-devel mailing list
Gluster-devel@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-devel
