<div dir="ltr"><div><div><div><div><div>It would be good to add few usecases to the document for completeness. I would say add usecases first, then the design should follow so that its a good logical flow for the reader. <br><br>Few that i can think of:<br><br></div>1) Archival/Compliance usecase<br><br></div>2) Openstack cinder usecase - GlusterFS can act as a backup target for Cinder where we can have the bitrot functionality enabled, can help act as a differentiator and attraction for using glusterfs as a backup target<br><br></div>3) Gluster health usecase - BitRot can potentially act as *one* of the indicators for the health of gluster volume, which can pave way for 'gluster health status' kind of a new command. See "BitRot Notes" thread for more info on gluster health cmd i proposed<br><br>-----------------<br><br></div> It would also be good to add high level steps a storage admin has to take to enable BitRot, what he/she should do when an error gets reported by BitRot, how to check for errors etc. Visualising this would help the interface/CLI effort and also gives a better picture for mgmt applns (eg: openstack) on what it needs to do (since it would try to automate/orchestrate what otherwise admin would have done)<br></div><div><br>Also, could you provide some high level view of how the CLIs for BitRot would look like ? That would help me map to the cinder usecase ( see (2) above )<br><br>thanx,<br></div>deepak<br><br><div><div><br></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Dec 12, 2014 at 5:33 PM, Venky Shankar <span dir="ltr"><<a href="mailto:vshankar@redhat.com" target="_blank">vshankar@redhat.com</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi folks,<br>
<br>
The design document for the upcoming "BitRot detection" feature (for 3.7) is here: <a href="http://goo.gl/Mjy4mD" target="_blank">http://goo.gl/Mjy4mD</a><br>
<br>
Thanks to Raghavendra, Rachana, Kotresh and Ajeet for helping out in the design. We plan to start implementation as soon as the design gets mature and approved.<br>
<br>
As usual comment/suggestions are more than welcome.<br>
<br>
Venky<br>
______________________________<u></u>_________________<br>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@gluster.org" target="_blank">Gluster-devel@gluster.org</a><br>
<a href="http://supercolony.gluster.org/mailman/listinfo/gluster-devel" target="_blank">http://supercolony.gluster.<u></u>org/mailman/listinfo/gluster-<u></u>devel</a><br>
</blockquote></div></div>