lxcfs
GlusterFS
lxcfs | GlusterFS | |
---|---|---|
1 | 19 | |
999 | 4,502 | |
1.2% | 1.0% | |
6.8 | 6.4 | |
1 day ago | 10 days ago | |
C | C | |
GNU General Public License v3.0 or later | 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.
lxcfs
-
Go, Containers, and the Linux Scheduler
> I wondered for a while if docker could make a fake /proc/cpuinfo
This exists: https://github.com/lxc/lxcfs
lxcfs is a FUSE filesystem that mocks /proc by inferring cgroup values in a way that makes other applications and libraries work without having to care about whether it runs in a container (to the best of its ability - there are definitely caveats).
One such example is that /proc/uptime should reflect the uptime of the container, not the host; additionally /proc/cpuinfo reflects the number of CPUs as a combination of cpu.max and cpuset.cpus (whichever the lower bound is).
As others also mentioned, inferring the number of CPUs could also be done using the sched_getaffinity syscall - this doesn't depend on /proc/cpuinfo, so depending on the library you're using you might be in a pickle.
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.
-
Linux deserves a better class of friends
This Product Appendix does not apply to online service offerings managed by Red Hat or generally available open source projects such as www.wildfly.org, www.fedoraproject.org, www.openstack.redhat.com, www.gluster.org, www.centos.org, okd.io, Ansible Project Software or other community projects.
-
Which distributed filesystem to use on a 4 node cluster?
Just because Red Hat will stop selling commercial support for their product, does not mean GlusterFS itself is dying. It's an open source project like any other - https://github.com/gluster/glusterfs
-
Setting up a 2 node distributed network share
https://www.gluster.org/ Is the way to do this across nodes
-
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/)
-
Multiple DS units acting as one?
What you look for is a clustered file system. Like https://www.gluster.org/. As long as all units are closeby with low latency there are a couple solutions that allow you to create distributed storage solutions of various kinds. Key value stores applenty, clustered file systems that pretent to be one file system etc. If you have geographically distributed solutions with high latencies it becomes harder. Most open source systems don't work really well in this scenario. There were a couple attempts like Hydrabase but they didn't go so far. It normally is solved by doing two clusters and then replicate between them.
-
Upload pdf file to mongodb atlas
I'd imagine most managed service providers are going to require a credit card, though most of them have a free tier. If you want to take an unmanaged approach, maybe look into Gluster. I've used it before and never had issue with it, but I also had an infrastructure team that set it up, so I'm not familiar with the challenges that way: https://www.gluster.org/
What are some alternatives?
LXC - LXC - Linux Containers
minio - The Object Store for AI Data Infrastructure
x11fs - A tool for manipulating X windows
lizardfs - LizardFS is an Open Source Distributed File System licensed under GPLv3.
automaxprocs - Automatically set GOMAXPROCS to match Linux container CPU quota.
Tahoe-LAFS - The Tahoe-LAFS decentralized secure filesystem.
go - The Go programming language
Go IPFS - IPFS implementation in Go [Moved to: https://github.com/ipfs/kubo]
btrfs - Haskell bindings to the btrfs API
Ceph - Ceph is a distributed object, block, and file storage platform
MooseFS - MooseFS – Open Source, Petabyte, Fault-Tolerant, Highly Performing, Scalable Network Distributed File System (Software-Defined Storage)
OpenAFS - Fork of OpenAFS from git.openafs.org for visualization