All,

I am one of the contributor forgluster-block <https://github.com/gluster/gluster-block>[1] project, and also I contribute to linux kernel andopen-iscsi <https://github.com/open-iscsi> project.[2]

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 refergithub issue #633 <https://github.com/gluster/glusterfs/issues/633>[3], and good news is I have a working code, with most basic things @nbd-runner project <https://github.com/gluster/nbd-runner>[4].

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.

Now few questions:

1. Can I continue to usehttp://github.com/gluster/nbd-runneras home for
   this project, even if its shared by other filesystem projects?

 * I personally am fine with this.

2. Should there be a separate organization for this repo?

 * While it may make sense in future, for now, I am not planning to
   start any new thing?

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.

Regards,
Xiubo Li (@lxbsz)

[1] -https://github.com/gluster/gluster-block
[2] -https://github.com/open-iscsi
[3] -https://github.com/gluster/glusterfs/issues/633
[4] -https://github.com/gluster/nbd-runner

_______________________________________________
Gluster-devel mailing list
Gluster-devel@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-devel

Reply via email to