<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Dec 13, 2014 at 10:58 PM, Venky Shankar <span dir="ltr"><<a href="mailto:yknev.shankar@gmail.com" target="_blank">yknev.shankar@gmail.com</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Sat, Dec 13, 2014 at 4:06 PM, Deepak Shetty <<a href="mailto:dpkshetty@gmail.com">dpkshetty@gmail.com</a>> wrote:<br>
> It would be good to add few usecases to the document for completeness. I<br>
> would say add usecases first, then the design should follow so that its a<br>
> good logical flow for the reader.<br>
><br>
> Few that i can think of:<br>
><br>
> 1) Archival/Compliance usecase<br>
<br>
</span>That's the major use case. But it does has a wide variety of use cases. <br></blockquote><div><br></div><div>It would be good to document those.. atleast 2-3 lines for each usecase.<br></div><div>These would eventually help consumers figure where all BitRot can fit and thus can<br>showcase the potential consumers for this feature/functionality. Feature page could<br>be a good place to add usecases. I (for my openstack requirements) had added<br>Usecase as a new section in feature page, you might want to do the same.<br><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class=""><br>
><br>
> 2) Openstack cinder usecase - GlusterFS can act as a backup target for<br>
> Cinder where we can have the bitrot functionality enabled, can help act as a<br>
> differentiator and attraction for using glusterfs as a backup target<br>
><br>
> 3) Gluster health usecase - BitRot can potentially act as *one* of the<br>
> indicators for the health of gluster volume, which can pave way for 'gluster<br>
> health status' kind of a new command. See "BitRot Notes" thread for more<br>
> info on gluster health cmd i proposed<br>
<br>
</span>Good that you've mentioned it here. I'll put this up in the bitrot feature page.<br>
<span class=""><br>
><br>
> -----------------<br>
><br>
> It would also be good to add high level steps a storage admin has to<br>
> take to enable BitRot, what he/she should do when an error gets reported by<br>
> BitRot, how to check for errors etc. Visualising this would help the<br>
> interface/CLI effort and also gives a better picture for mgmt applns (eg:<br>
> openstack) on what it needs to do (since it would try to<br>
> automate/orchestrate what otherwise admin would have done)<br>
<br>
</span>Agreed. The interface specification doc was also written at about the<br>
same time as the design and can be accessed here: <a href="http://goo.gl/2o12Fn" target="_blank">http://goo.gl/2o12Fn</a><br>
<br>
Credit goes to Rachana for preparing this doc.<br></blockquote><div><br></div><div>@racpatel - nice work.<br></div><div>I added few comments/suggestions to your CLI doc.. pls have a look.<br><br></div><div>Also looks like there are numerous docs for someone to refer to....<br></div><div>* feature page<br></div><div>* CLI doc<br></div><div>* design doc<br></div><div>* silent-corruption.doc - which was referred to in this thread<br><br></div><div>Is there a way all of these can be referenced from the feature page so that<br>just giving the feature page link can have the reader know the links to all of these other docs ?<br><br></div><div>There should be one common place from where anyone can navigate to all other related docs<br>that matter for this feature/functionality<br></div><div> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class=""><br>
><br>
> Also, could you provide some high level view of how the CLIs for BitRot<br>
> would look like ? That would help me map to the cinder usecase ( see (2)<br>
> above )<br>
<br>
</span>As above. The interface is not set in stone, it's just a start. Let us<br>
know your views.<br></blockquote><div><br></div><div>I just added few suggestions, pls have a look<br><br></div><div>thanx,.<br>deepak<br></div><br></div></div></div>