MooseFS
gcp-filestore-csi-driver
MooseFS | gcp-filestore-csi-driver | |
---|---|---|
3 | 2 | |
1,587 | 82 | |
1.1% | - | |
4.8 | 8.8 | |
2 months ago | about 10 hours ago | |
C | Go | |
GNU General Public License v3.0 only | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
MooseFS
- Google Cloud Storage FUSE
-
Garage, our self-hosted distributed object storage solution
MooseFS is designed for large files and can have a global goal of 1 copy (no replication)
https://moosefs.com/
-
Can someone tell me if this is possible or even a good idea?
My friends and I all use Linux and often use each others laptops or desktops when we forget ours. Then I had the idea to install Linux on a USB so I could have all my stuff and use my system on any system. Which was cool but then I ran into the same problem of forgetting it sometimes. So my new idea (which I have no idea how I'd achieve) is to use something like MooseFS or ceph or some distributed filesystem for our home partition. So then we can just login and have all our files and customization's be there almost seamlessly. I don't know how or if it would work but it seems like it could. What do you think?
gcp-filestore-csi-driver
-
Google Cloud Storage FUSE
Hi Ofek,
I am a contributor who works on the Google Cloud Storage FUSE CSI Driver project. The project is partially inspired by your CSI implementation. Thank you so much for the contribution to the Kubernetes community. However, I would like to clarify a few things regarding your post.
The Cloud Storage FUSE CSI Driver project does not have “in large part copied code” from your implementation. The initial commit you referred to in the post was based on a fork of another open source project: https://github.com/kubernetes-sigs/gcp-filestore-csi-driver. If you compare the Google Cloud Storage FUSE CSI Driver repo with the Google Cloud Filestore CSI Driver repo, you will notice the obvious similarities, in terms of the code structure, the Dockerfile, the usage of Kustomize, and the way the CSI is implemented. Moreover, the design of the Google Cloud Storage FUSE CSI Driver included a proxy server, and then evolved to a sidecar container mode, which are all significantly different from your implementation.
As for the Dockerfile annotations you pointed out in the initial commit, I did follow the pattern in your repo because I thought it was the standard way to declare the copyright. However, it didn't take me too long to realize that the Dockerfile annotations are not required, so I removed them.
Thank you again for your contribution to the open source community. I have included your project link on the readme page. I take the copyright very seriously, so please feel free to directly create issues or PRs on the Cloud Storage FUSE CSI Driver GitHub project page if I missed any other copyright information.
-
Introduction to Day 2 Kubernetes
Any Kubernetes cluster requires persistent storage - whether organizations choose to begin with an on-premise Kubernetes cluster and migrate to the public cloud, or provision a Kubernetes cluster using a managed service in the cloud. Kubernetes supports multiple types of persistent storage – from object storage (such as Azure Blob storage or Google Cloud Storage), block storage (such as Amazon EBS, Azure Disk, or Google Persistent Disk), or file sharing storage (such as Amazon EFS, Azure Files or Google Cloud Filestore). The fact that each cloud provider has its implementation of persistent storage adds to the complexity of storage management, not to mention a scenario where an organization is provisioning Kubernetes clusters over several cloud providers. To succeed in managing Kubernetes clusters over a long period, knowing which storage type to use for each scenario, requires storage expertise.
What are some alternatives?
Ceph - Ceph is a distributed object, block, and file storage platform
gcs-fuse-csi-driver - The Google Cloud Storage FUSE Container Storage Interface (CSI) Plugin.
lizardfs - LizardFS is an Open Source Distributed File System licensed under GPLv3.
gcp-compute-persistent-disk-csi-driver - The Google Compute Engine Persistent Disk (GCE PD) Container Storage Interface (CSI) Storage Plugin.
GlusterFS - Web Content for gluster.org -- Deprecated as of September 2017
blob-csi-driver - Azure Blob Storage CSI driver
Seaweed File System - SeaweedFS is a fast distributed storage system for blobs, objects, files, and data lake, for billions of files! Blob store has O(1) disk seek, cloud tiering. Filer supports Cloud Drive, cross-DC active-active replication, Kubernetes, POSIX FUSE mount, S3 API, S3 Gateway, Hadoop, WebDAV, encryption, Erasure Coding. [Moved to: https://github.com/seaweedfs/seaweedfs]
geesefs - Finally, a good FUSE FS implementation over S3
Apache Hadoop - Apache Hadoop
curve - Curve is a sandbox project hosted by the CNCF Foundation. It's cloud-native, high-performance, and easy to operate. Curve is an open-source distributed storage system for block and shared file storage.
GlusterFS - Gluster Filesystem : Build your distributed storage in minutes
google-drive-ocamlfuse - FUSE filesystem over Google Drive