-
Notifications
You must be signed in to change notification settings - Fork 200
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEATURE] mfsbdev as standard (TCP/Unix Socket) NBD server #570
Comments
A direct iSCSI server would also be interesting, especially as it could then be more easily used for things like booting a machine off the network with storage on MooseFS, but I think the iSCSI protocol is a lot more complicated than NBD (so that'd be a whole separate feature request / larger engineering effort, I think). 😄 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Related to #527 (comment) and #113, I finally looked deeper at
mfsbdev
again, especially as I found https://manpages.debian.org/bookworm/qemu-system-x86/qemu-system-x86_64.1.en.html#NBD which makes it ~easy for QEMU to connect directly to an NBD server over TCP or Unix Domain Sockets, which seemed perfect!However, I quickly re-realized that
mfsbdev
seems to be more of a helper for directly creating block devices on a host that are backed by MooseFS (via NBD), and I could not find a way to expose a "standard" NBD server from it.So, in short, my feature request is that
mfsbdev
have some way to just expose a "proper" NBD server over TCP and/or unix socket instead of just the (AFAICT) custom protocol it currently supports. 🙇 ❤️The text was updated successfully, but these errors were encountered: