<div dir="ltr"><div dir="ltr"><div dir="ltr"><br></div><div>Hi Xiubo,</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Mar 22, 2019 at 5:48 PM Xiubo Li <<a href="mailto:xiubli@redhat.com">xiubli@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
<div class="gmail-m_-807191363764354585moz-cite-prefix">On 2019/3/21 11:29, Xiubo Li wrote:<br>
</div>
<blockquote type="cite">
<p class="gmail-m_-807191363764354585part">All,</p>
<p class="gmail-m_-807191363764354585part">I am one of the contributor for<span> </span><a href="https://github.com/gluster/gluster-block" rel="noopener" target="_blank">gluster-block</a>[1] project, and also I contribute to linux kernel and<span> </span><a href="https://github.com/open-iscsi" rel="noopener" target="_blank">open-iscsi</a> project.[2]</p>
<p class="gmail-m_-807191363764354585part">NBD was around for some time, but in recent time, linux kernel’s Network Block Device (NBD) is enhanced and made to work with more devices and also the option to integrate with netlink is added. So, I tried to provide a glusterfs client based NBD driver recently. Please refer<span> </span><a href="https://github.com/gluster/glusterfs/issues/633" rel="noopener" target="_blank">github issue #633</a>[3], and good news is I have a working code, with most basic things @<span> </span><a href="https://github.com/gluster/nbd-runner" rel="noopener" target="_blank">nbd-runner project</a>[4].</p></blockquote></div></blockquote><div><br></div><div>This is nice. Thank you for your work!</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF"><blockquote type="cite">
</blockquote>
<p>As mentioned the nbd-runner(NBD proto) will work in the same layer with tcmu-runner(iSCSI proto), this is not trying to replace the gluster-block/ceph-iscsi-gateway great projects.<br>
</p>
<p>It just provides the common library to do the low level stuff, like the sysfs/netlink operations and the IOs from the nbd kernel socket, and the great tcmu-runner project is doing the sysfs/uio operations and IOs from the kernel SCSI/iSCSI.</p>
<p>The nbd-cli tool will work like the iscsi-initiator-utils, and the nbd-runner daemon will work like the tcmu-runner daemon, that's all.</p></div></blockquote><div><br></div><div>Do you have thoughts on how nbd-runner currently differs or would differ from tcmu-runner? It might be useful to document the differences in github (or elsewhere) so that users can make an informed choice between nbd-runner & tcmu-runner.</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF">
<p>In tcmu-runner for different backend storages, they have separate handlers, glfs.c handler for Gluster, rbd.c handler for Ceph, etc. And what the handlers here are doing the actual IOs with the backend storage services once the IO paths setup are done by ceph-iscsi-gateway/gluster-block....<br>
</p>
<p>Then we can support all the kind of backend storages, like the Gluster/Ceph/Azure... as one separate handler in nbd-runner, which no need to care about the NBD low level's stuff updates and changes.<br></p></div></blockquote><div><br></div><div>Given that the charter for this project is to support multiple backend storage projects, would not it be better to host the project in the github repository associated with nbd [5]? Doing it that way could provide a more neutral (as perceived by users) venue for hosting nbd-runner and help you in getting more adoption for your work.</div><div><br></div><div>Thanks,</div><div>Vijay</div><div><br></div><div>[5] <a href="https://github.com/NetworkBlockDevice/nbd">https://github.com/NetworkBlockDevice/nbd</a></div><div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF"><p>
</p>
<p>Thanks.</p>
<p><br>
</p>
<blockquote type="cite">
<p class="gmail-m_-807191363764354585part">While this email is about announcing the project, and asking for more collaboration, I would also like to discuss more about the placement of the project itself. Currently nbd-runner project is expected to be shared by our friends at Ceph project too, to provide NBD driver for Ceph. I have personally worked with some of them closely while contributing to open-iSCSI project, and we would like to take this project to great success.</p>
<p class="gmail-m_-807191363764354585part">Now few questions:</p>
<ol class="gmail-m_-807191363764354585part">
<li>Can I continue to use<span> </span><a href="http://github.com/gluster/nbd-runner" rel="noopener" target="_blank">http://github.com/gluster/nbd-runner</a><span> </span>as home for this project, even if its shared by other filesystem projects?</li>
</ol>
<ul class="gmail-m_-807191363764354585part">
<li>I personally am fine with this.</li>
</ul>
<ol start="2" class="gmail-m_-807191363764354585part">
<li>Should there be a separate organization for this repo?</li>
</ol>
<ul class="gmail-m_-807191363764354585part">
<li>While it may make sense in future, for now, I am not planning to start any new thing?</li>
</ul>
<p class="gmail-m_-807191363764354585part">It would be great if we have some consensus on this soon as nbd-runner is a new repository. If there are no concerns, I will continue to contribute to the existing repository.</p>
<p class="gmail-m_-807191363764354585part">Regards,<br>Xiubo Li (@lxbsz)</p>
<p class="gmail-m_-807191363764354585part">[1] -<span> </span><a href="https://github.com/gluster/gluster-block" rel="noopener" target="_blank">https://github.com/gluster/gluster-block</a><br>[2] -<span> </span><a href="https://github.com/open-iscsi" rel="noopener" target="_blank">https://github.com/open-iscsi</a><br>[3] -<span> </span><a href="https://github.com/gluster/glusterfs/issues/633" rel="noopener" target="_blank">https://github.com/gluster/glusterfs/issues/633</a><br>[4] -<span> </span><a href="https://github.com/gluster/nbd-runner" rel="noopener" target="_blank">https://github.com/gluster/nbd-runner</a></p>
<br>
<fieldset class="gmail-m_-807191363764354585mimeAttachmentHeader"></fieldset> <pre class="gmail-m_-807191363764354585moz-quote-pre">_______________________________________________
Gluster-users mailing list
<a class="gmail-m_-807191363764354585moz-txt-link-abbreviated" href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a>
<a class="gmail-m_-807191363764354585moz-txt-link-freetext" href="https://lists.gluster.org/mailman/listinfo/gluster-users" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-users</a></pre>
</blockquote>
<p><br>
</p>
</div>_______________________________________________<br>Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
<a href="https://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-users</a></blockquote></div></div></div>