-
Notifications
You must be signed in to change notification settings - Fork 155
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
Project is alive? #1197
Comments
@Argentum88 Sorry for the late reply. Originally @yosukehara project lead should answer your question but he seems busy so I'd like to answer instead of him. Now he and other project members (including me) have been involved in other projects with more high priority so LeoFS has been not active these days. One thing I can say at this moment is we will keep doing the maintenance release for LeoFS whenever we find any bugs which should be fixed. @yosukehara please fix me if there are something wrong on the above comment. |
@Argentum88 |
@yosukehara @mocchira could you tell when you plan to return to the development of LeoFS? |
Thank you for your comment. |
@wulfgar93 The situation I've been in is almost same as @yosukehara. I'm not sure when I can come back to LeoFS developement for now however I'll be back ASAP. |
I was recently looking for a storage system with properties of LeoFS and wonder whether it's a good idea to use LeoFS in production considering it's not backend by any commercial interest any more. Any new insights? |
I am interested in knowing if LeoFS would be recommended for new projects as well |
+1 |
@dyasny In the meantime I have found out that seaweedfs is the established and recommended alternative. Hope this helps |
@nkosi23 yeah, I'm aware of it. Unfortunately, it doesn't support NFS, and that's what I need for now |
Maybe Ganesha can be of help? It is an NFS server in user space that can present Fuse file systems over NFS. SeaweedFS is not great with POSIX compliance/compatibility... I wholeheartedly recommend MooseFS as alternative. |
I can simply set up a basic NFS server, I think performance would actually be better. But What I actually need is a resilient NFS service, distributed, replicated, the works. I am aware of ceph and gluster of course and they are an overkill for me.
Frankly, I don't care too much about posix compliance. What I need to do is mount the same NFS export on all of my k8s workers and use that mountpoint for hostPath volumes. Inside the volumes there's an app with a few sidecars and an sqlite file. |
@dyasny have you looked at ZFS? |
I noticed that in late April, active development was suspended. What happened?
The text was updated successfully, but these errors were encountered: