Any good alternatives?
https://www.versity.com/products/versitygw/
I haven't tried it though. Seems simple enough to run.
MinIO is now in maintenance-mode
201–210 of 338 posts
Re: MinIO is now in maintenance-mode
#202Earlier quoted context omitted.
> they abandoned POSIX compatibility, built a massively over-complicated product This is a wild sentence--how can you criticize them for abandoning POSIX support __and__ building a massively over-complicated product? Making a reliable POSIX system is inherently very complex.
I think the criticism (just interpreting the post, don’t know anything about the technical situation) is that the complication is not necessary/worthwhile. POSIX can be complicated, but it puts you in a nice ecosystem, so for some use-cases complex POSIX support is not over complicated. It is just… appropriately complicated.
Sure, but then you can make that argument about any of the features in Minio, in which case the parent's argument about Minio as a whole being overcomplicated is invalidated. Probably the more sensible way to look at things is "value / complexity" or "bang for buck", but even there I think POSIX loses since it's relatively little value for a relatively large amount of complexity.
Re: MinIO is now in maintenance-mode
#203There is https://github.com/seaweedfs/seaweedfs I haver not used it but will be likely a good minio alternative for people who want to run a server and don't use minio just as s3 client.
Is it stable now? Last time I checked, the amount of correctness bugs being fixed in the Git history wasn't very confidence-inspiring.
Since storage is a critical component, I closely watched it and engaged with the project for about 2 years circa as i contemplated adding it to our project, but the project is still immature from a reliability perspective in my opinion.
No test suite, plenty of regressions, and data loss bugs on core code paths that should have been battled tested after so many years. There are many moving parts, which is both its strength and its weakness as anything can break - and does break. Even Erasure Coding/Decoding has had problems, but a guy from Proton has contributed a lot of fixes in this area lately.
One of the big positive in my opinion, is the maintainer. He is an extremely friendly and responsive gentleman. Seaweedfs is also the most lightweight storage system you can find, and it is extremely easy to set up, and can run on servers with very little hardware resources.
Many people are happy with it, but you'd better be ready to understand their file format to fix corruption issues by hand. As far as i am concerned, i realized that after watching all these bugs, the idea of using seaweedfs was causing me more anxiety than peace of mind. Since we didn't need to store billions of files yet, not even millions, we went with creating a file storage API in ASP.NET Core in 1 or 2 hours, hosted on a VPS, that we can replicate using rsync without problem. Since i made this decision, i have peace of mind and no longer think about my storage system. Simplicity is often better, and OSes have long been optimized to cache and serve files natively.
If you are not interested in contributing fixes and digging into the file format when a problem occurs, and if your data is important to you, unless you operate at the billions of files scalability tier Seaweedfs shines at, i'd suggest rolling your own boring storage system.
Re: MinIO is now in maintenance-mode
#204Does anyone have any recommendations for a simple S3-wrapper to a standard dir? I've got a few apps/services that can send data to S3 (or S3 compatible services) that I want to point to a local server I have, but they don't support SFTP or any of the more "primitive" solutions. I did use a python local-s3 thing, but it was... not good.
Versity Gateway looks like a reasonable option here. I haven't personally used it, but I know some folks who say it performs pretty great as a "ZFS-backed S3" alternative. https://github.com/versity/versitygw Unlike other options like Garage or Minio, it doesn't have any clustering, replication, erasure coding, ... Your S3 objects are just files on disk, and Versity exposes it. I gather it exists to provide an S3 int…
Garage also decide to not implement erasure coding.
Re: MinIO is now in maintenance-mode
#205Earlier quoted context omitted.
They have a CLA that assigns copyright to them: https://github.com/rustfs/rustfs/blob/5b0a3a07645364d998e3f5... So, arguably worse than MinIO.
How would you run a project like this? People come and go. People do a one-time contribution and then you never hear from them again. People work on a project for years and then just go silent. Honestly, credit where credit is due, but how is a project like this supposed to manage this?
You can have CLA without assigning copyright to the project.
You don't need assignment to the project if you are not planning to change project's license.
You do need assignment to the project if you need to ever rugpull the community and close the code
Re: MinIO is now in maintenance-mode
#206Earlier quoted context omitted.
MinIO still makes no sense, as Ceph is fundamentally already RADOS at its core (fully compatible with S3 API.) For a proper Ceph setup, even the 45drives budget configuration is still not "hobby" grade. I will have to dive into the MinIO manual at some point, as the value proposition still seems like a mystery. Cheers =3
MinIO is far less complex than getting same functionality on Ceph stack. But that's kind of advantage only on the small companies and hobbyist market, big company either have enough needs to run big ceph cluster, or to buy it as a service. Minio is literally "point it at storage(s), done". And at far smaller RAM usage. Ceph is mon servers, osd servers, then rados gatway server on top of that.
It sounds a lot like SwiftOnFile with GlusterFS, but I would need to look at it more closely on personal time. =3
Re: MinIO is now in maintenance-mode
#207What is the purpose of MinIO, Seaweedfs and similar object storage systems? They lack durability guarantees provided by S3 and GCS. They lack "infinite" storage promise contrary to S3 and GCS. They lack "infinite" bandwidth unlike S3 and GCS. They are more expensive than other storage options, unlike S3 and GCS.
Re: MinIO is now in maintenance-mode
#208What is the purpose of MinIO, Seaweedfs and similar object storage systems? They lack durability guarantees provided by S3 and GCS. They lack "infinite" storage promise contrary to S3 and GCS. They lack "infinite" bandwidth unlike S3 and GCS. They are more expensive than other storage options, unlike S3 and GCS.
I haven't used it in a while, but it used to be great as a test double for s3
Re: MinIO is now in maintenance-mode
#209Earlier quoted context omitted.
"Ceph is fundamentally already RADOS at its core (fully compatible with S3 API.)" Yes, Ceph is RADOS at its core. However, RADOS != S3. Ceph provides an S3 compatible backend with the RADOS Gateway (RGW).
My point was even 45drives virtualization of Ceph host roles to squeeze the entire setup into a single box was not a "hobby" grade project. I don't understand yet exactly what MinIO would add on top of that to make it relevant at any scale. I'll peruse the manual on the weekend, because their main site was not helpful. Thanks for trying though ¯\_(ツ)_/¯
What I tried to say (perhaps not successfully) was that core Ceph knows nothing about S3. One gets S3 endpoint capability from the radosgw which is not a required component in a ceph cluster.
Re: MinIO is now in maintenance-mode
#210Open source is not a sustainable business model.
There are two ways open source projects continue.
1. The creator has a real, solid way to make money (React by Facebook, Go by Google).
2. The project is extremely popular (Linux, PostreSQL).
Is it possible for people to reliably keep working for ~free? In theory yes, but if you expect that, you have a very bad understanding of 98% of human behavior.