Garage, an open-source distributed storage service you can self-host to fullfill many needs
-
https://garagehq.deuxfleurs.fr/
Alternative to Minio, specially made for selfhosting setup.
See: https://garagehq.deuxfleurs.fr/blog/2022-introducing-garage/
Code: https://git.deuxfleurs.fr/Deuxfleurs/garage -
https://garagehq.deuxfleurs.fr/
Alternative to Minio, specially made for selfhosting setup.
See: https://garagehq.deuxfleurs.fr/blog/2022-introducing-garage/
Code: https://git.deuxfleurs.fr/Deuxfleurs/garage@ruihildt this sounds absolutely brilliant, thanks for sharing!
-
Too bad this is only replicated storage. (from what I can tell with a look of the front page)
Minio can use error correcting codes instead of replication.
-
Too bad this is only replicated storage. (from what I can tell with a look of the front page)
Minio can use error correcting codes instead of replication.
-
Too bad this is only replicated storage. (from what I can tell with a look of the front page)
Minio can use error correcting codes instead of replication.
@robi said in Garage, an open-source distributed storage service you can self-host to fullfill many needs:
Too bad this is only replicated storage. (from what I can tell with a look of the front page)
Minio can use error correcting codes instead of replication.
@infogulch said in Garage, an open-source distributed storage service you can self-host to fullfill many needs:
@robi Yeah unfortunately.
Non-goals include:
- ...
- Erasure coding (our replication model is simply to copy the data as is on several nodes, in different datacenters if possible)
What's the difference? or advantage of error correcting / erasure codiing?
-
@robi said in Garage, an open-source distributed storage service you can self-host to fullfill many needs:
Too bad this is only replicated storage. (from what I can tell with a look of the front page)
Minio can use error correcting codes instead of replication.
@infogulch said in Garage, an open-source distributed storage service you can self-host to fullfill many needs:
@robi Yeah unfortunately.
Non-goals include:
- ...
- Erasure coding (our replication model is simply to copy the data as is on several nodes, in different datacenters if possible)
What's the difference? or advantage of error correcting / erasure codiing?
@jdaviescoates You can read about it in many places online comparing the two architectures and implementations.
EC is more space efficient, especially at large scale (Petabyte, Exabyte, etc), while replication always uses 100% more per replica and doesn't guarantee bit flip protection, etc. hence it doesn't scale well.
EC can always compute any missing pieces and self-heal or regenerate.
That's why you can hear all the words speaking with someone on the phone from across the planet, as many lost packets are recomputed to fill in gaps instead of long retransmits.
This applies to huge storage on continuously failing hardware under it too.
-
@jdaviescoates You can read about it in many places online comparing the two architectures and implementations.
EC is more space efficient, especially at large scale (Petabyte, Exabyte, etc), while replication always uses 100% more per replica and doesn't guarantee bit flip protection, etc. hence it doesn't scale well.
EC can always compute any missing pieces and self-heal or regenerate.
That's why you can hear all the words speaking with someone on the phone from across the planet, as many lost packets are recomputed to fill in gaps instead of long retransmits.
This applies to huge storage on continuously failing hardware under it too.
@robi said in Garage, an open-source distributed storage service you can self-host to fullfill many needs:
@jdaviescoates You can read about it in many places online comparing the two architectures and implementations.
EC is more space efficient, especially at large scale (Petabyte, Exabyte, etc), while replication always uses 100% more per replica and doesn't guarantee bit flip protection, etc. hence it doesn't scale well.
EC can always compute any missing pieces and self-heal or regenerate.
That's why you can hear all the words speaking with someone on the phone from across the planet, as many lost packets are recomputed to fill in gaps instead of long retransmits.
This applies to huge storage on continuously failing hardware under it too.
You have a gift for explaining things.
-
https://garagehq.deuxfleurs.fr/
Alternative to Minio, specially made for selfhosting setup.
See: https://garagehq.deuxfleurs.fr/blog/2022-introducing-garage/
Code: https://git.deuxfleurs.fr/Deuxfleurs/garage@ruihildt said in Garage, an open-source distributed storage service you can self-host to fullfill many needs:
https://garagehq.deuxfleurs.fr/
Alternative to Minio, specially made for selfhosting setup.
See: https://garagehq.deuxfleurs.fr/blog/2022-introducing-garage/
Code: https://git.deuxfleurs.fr/Deuxfleurs/garageI haven't checked out this suggestion yet, but if it like what I have in mind, it could be brilliant for Cloudron.
Cloudron is all about self-hosting. and there are a huge number of games with outdated gaming systems that could be repurposed to Cloudron self-hosting. These machines would have large amounts of RAM (for games), a very fast SSD (for running the system) and also a large storage drive (to hold the games).
That sort of legacy hardware is, I think, absolutely ripe for Cloudron! The Garage software could make those old storage disks have a new life!
-
@ruihildt said in Garage, an open-source distributed storage service you can self-host to fullfill many needs:
https://garagehq.deuxfleurs.fr/
Alternative to Minio, specially made for selfhosting setup.
See: https://garagehq.deuxfleurs.fr/blog/2022-introducing-garage/
Code: https://git.deuxfleurs.fr/Deuxfleurs/garageI haven't checked out this suggestion yet, but if it like what I have in mind, it could be brilliant for Cloudron.
Cloudron is all about self-hosting. and there are a huge number of games with outdated gaming systems that could be repurposed to Cloudron self-hosting. These machines would have large amounts of RAM (for games), a very fast SSD (for running the system) and also a large storage drive (to hold the games).
That sort of legacy hardware is, I think, absolutely ripe for Cloudron! The Garage software could make those old storage disks have a new life!
Garage still doesn't support 100% the s3 protocol.
And due to how is written, modern NVMe will not get a BIG boost if you don't have a powerful CPU (it CPU intensive for big files like cloudron Backup, and is still not well-performing if you have small files like in a Nextcloud with small docs.)MooCloud is testing Garage, and we have an agreement with Garage leading developer to publish the data collected using garage in a modern cloud environment.
Matteo. R.
Founder and Tech-Support Manager.
MooCloud MSP
Swiss Managed Service Provider -
Garage still doesn't support 100% the s3 protocol.
And due to how is written, modern NVMe will not get a BIG boost if you don't have a powerful CPU (it CPU intensive for big files like cloudron Backup, and is still not well-performing if you have small files like in a Nextcloud with small docs.)MooCloud is testing Garage, and we have an agreement with Garage leading developer to publish the data collected using garage in a modern cloud environment.
@MooCloud_Matt Have you looked at SeaweedFS yet?
-
@MooCloud_Matt Have you looked at SeaweedFS yet?
@robi
We did, but i don't recall the reason we excluded as an alternate to ceph(that we are using in prod currently)
