GoSƐ
GlusterFS
Our great sponsors
| GoSƐ | GlusterFS | |
|---|---|---|
| 2 | 19 | |
| 174 | 4,471 | |
| - | 1.4% | |
| 8.7 | 6.8 | |
| 8 days ago | 6 days ago | |
| Go | C | |
| Apache License 2.0 | GNU General Public License v3.0 only |
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.
GoSƐ
-
One-way hidden upload app
Gose could help
-
Looking for a selfhosted file share service with unique urls for upload
Its on the agenda for Gos3: https://github.com/stv0g/Gose
GlusterFS
-
Tell HN: ZFS silent data corruption bugfix – my research results
https://github.com/gluster/glusterfs/issues/894
And apparently apart from modern coreutils using that, it is mostly gentoo users hitting the bugs in lseek.
-
System Design: Netflix
This allows us to fetch the desired quality of the video as per the user's request, and once the media file finishes processing, it will be uploaded to a distributed file storage such as HDFS, GlusterFS, or an object storage such as Amazon S3 for later retrieval during streaming.
-
What's the best way to periodically sync two remote servers?
GlusterFS
-
System Design: The complete course
But where can we store files at scale? Well, object storage is what we're looking for. Object stores break data files up into pieces called objects. It then stores those objects in a single repository, which can be spread out across multiple networked systems. We can also use distributed file storage such as HDFS or GlusterFS.
-
First Apartment and First Homelab
GlusterFS - same as above (https://www.gluster.org/)
-
Blocky DNS & synchronizing two instances (primary & secondary DNS)
I'm running three Blocky instances in Docker (and CoreDNS for internal zone resolving) by placing YAML files on a GlusterFS share, so I can update configs on one VM, and then just restart Blocky containers via SSH.
-
Why are you not using kubernetes?
Longhorn and storage in general the hardest part of any HA setup, but also not the only choice, at the most basic level something like glusterFS is easy to get running and usable in k8s as NFS volumes, it however doesn't have all the extra features of longhorn.
-
HPC design choices
Do you mean https://www.gluster.org/ ?
What are some alternatives?
minio - The Object Store for AI Data Infrastructure
lizardfs - LizardFS is an Open Source Distributed File System licensed under GPLv3.
Tahoe-LAFS - The Tahoe-LAFS decentralized secure filesystem.
Go IPFS - IPFS implementation in Go [Moved to: https://github.com/ipfs/kubo]
btrfs - Haskell bindings to the btrfs API
OpenAFS - Fork of OpenAFS from git.openafs.org for visualization
MooseFS - MooseFS – Open Source, Petabyte, Fault-Tolerant, Highly Performing, Scalable Network Distributed File System (Software-Defined Storage)
Ceph - Ceph is a distributed object, block, and file storage platform
Apache Hadoop - Apache Hadoop
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]
BorgBackup - Deduplicating archiver with compression and authenticated encryption.
Swift - OpenStack Storage (Swift). Mirror of code maintained at opendev.org.