<html><body><div style="font-family: lucida console,sans-serif; font-size: 12pt; color: #000000"><div>Just one question relating to thoughts around how you apply a filter to the snapshot view from a user's perspective.<br></div><div><br></div><div>In the "considerations" section, it states - <span style="white-space: pre-wrap; font-size: 12pt;">"We plan to introduce a configurable option to limit the number of snapshots visible under the USS feature."</span><pre style="word-wrap: break-word; white-space: pre-wrap;" data-mce-style="word-wrap: break-word; white-space: pre-wrap;"></pre></div><div><span style="white-space: pre-wrap; font-size: 12pt;">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.</span></div><div><span style="white-space: pre-wrap; font-size: 12pt;"><br></span></div><div><span style="white-space: pre-wrap; font-size: 12pt;">i.e.</span></div><div><span style="white-space: pre-wrap; font-size: 12pt;">.snaps</span></div><div><span style="white-space: pre-wrap; font-size: 12pt;"> \/ Today</span></div><div><span style="white-space: pre-wrap; font-size: 12pt;"> +-- snap01_20140503_0800</span></div><div><span style="white-space: pre-wrap; font-size: 12pt;"> +-- snap02_<span style="white-space: pre-wrap;" data-mce-style="white-space: pre-wrap;">20140503_</span>1400</span></div><div><span style="font-size: 12pt; white-space: pre-wrap;"> > </span><span style="font-size: 12pt; white-space: pre-wrap;">Last 7 days</span></div><div><span style="white-space: pre-wrap; font-size: 12pt;"> > 7-21 days</span></div><div><span style="white-space: pre-wrap; font-size: 12pt;"> > 21-60 days</span></div><div><span style="white-space: pre-wrap; font-size: 12pt;"> > 60-180days</span></div><div><span style="white-space: pre-wrap; font-size: 12pt;"> > 180days</span></div><div><span style="white-space: pre-wrap; font-size: 12pt;"><br></span></div><div><span style="white-space: pre-wrap; font-size: 12pt;"><br></span></div><div><span style="white-space: pre-wrap; font-size: 12pt;"><br></span></div><div><span style="white-space: pre-wrap; font-size: 12pt;"><br></span></div><div><span style="white-space: pre-wrap; font-size: 12pt;"><br></span></div><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From: </b>"Anand Subramanian" <ansubram@redhat.com><br><b>To: </b>gluster-devel@nongnu.org, "gluster-users" <gluster-users@gluster.org><br><b>Cc: </b>"Anand Avati" <aavati@redhat.com><br><b>Sent: </b>Saturday, 3 May, 2014 2:35:26 AM<br><b>Subject: </b>[Gluster-users] User-serviceable snapshots design<br><div><br></div>Attached is a basic write-up of the user-serviceable snapshot feature <br>design (Avati's). Please take a look and let us know if you have <br>questions of any sort...<br><div><br></div>We have a basic implementation up now; reviews and upstream commit <br>should follow very soon over the next week.<br><div><br></div>Cheers,<br>Anand<br><div><br></div>_______________________________________________<br>Gluster-users mailing list<br>Gluster-users@gluster.org<br>http://supercolony.gluster.org/mailman/listinfo/gluster-users</blockquote><div><br></div></div></body></html>