My only blocker for a fork to maintain compatibility and path to upgrade from earlier versions.
MinIO is now in maintenance-mode
111–120 of 338 posts
Re: MinIO is now in maintenance-mode
#112They have been removing features from the open source version for a while. The closest alternative seems to be RustFS. Has anyone tried it? I was waiting until they support site replication before switching.
Re: MinIO is now in maintenance-mode
#113It sucks that S3 somehow became the defacto object storage interface, the API is terrible IMO. Too many headers, too many unknowns with support. WebDAV isn't any better, but I feel like we missed an opportunity here for a standardized interface.
? Its like GET /object, PUT /object. To me its the most obvious mapping of HTTP to immutable object key value storage you could imagine. It is bad that the control plane responses can be malformed XML (e.g keys are not escaped right if you put XML control characters in object paths) but that can be forgiven as an oversight. Its not perfect but I don't think its a strange API at all.
And many S3-compatible alternatives (probably most but the big ones like Ceph) don't implement all of the features.
For example for lifecycles backblaze have completely different JSON syntax
Re: MinIO is now in maintenance-mode
#114So if the minio maintainers (or anybody that forks the project and wants to work it) can fix any security issues that may occur I don't see any problems with using it.
Re: MinIO is now in maintenance-mode
#115Earlier quoted context omitted.
I don't see a contributor licensing agreement (CLA), so you may be right. (I personally choose not to contribute to projects with CLAs, I don't want my contributions to become closed-source in the future.)
Its worse than I thought: https://blog.min.io/weka-violates-minios-open-source-license... They think they can revoke someone's AGPL license. That's not at all how that license works!
> All rights granted under this License are granted for the term of copyright on the Program, and are irrevocable provided the stated conditions are met.
it also says
> You may not propagate or modify a covered work except as expressly provided under this License. Any attempt otherwise to propagate or modify it is void, and will automatically terminate your rights under this License (including any patent licenses granted under the third paragraph of section 11).
> However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation.
> Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice.
This is in common with the GPLv3. It is much longer than the corresponding terms of the GPLv2 to remedy a sort of fragility in the GPLv2 which says your license terminates permanently if you ever violate the GPL, even temporarily and by accident.
I have no knowledge of whether Weka did or didn't violate the license, but if they did violate it and refused to fix it, MinIO's revocation of their license is completely in accordance with the terms of the license as written. I don't think a GPL termination case has yet been litigated.
Re: MinIO is now in maintenance-mode
#116Like many smart people they focused on telling people the "how", and assume visitors to their wall of "AI"/hype text already understand the use-case "why". 1. I like that it is written in Go 2. I saw nothing above what Apache Spark+Hadoop with _consistent_ object stores already offers on Amazon (S3), Google Cloud (GCS), and or Microsoft (Azure Storage, ADLS Gen2) Best of luck, maybe folks should look around for that…
it was very simple to setup, and even if you just leased a bunch of servers off say OVH, far FAR cheaper to run your own than paying any of the big cloud providers.
It also had pretty low requirements, ceph can do all that but setup is more complex and RAM requirements far, far higher
Re: MinIO is now in maintenance-mode
#117Minio is more or less feature complete for most use cases. Actually the last big update of minio removed features (the UI). I am using minio for 5 years and haven't messed with it or used any new thingie for the last 5 years (i.e since I installed it); I only update to new versions. So if the minio maintainers (or anybody that forks the project and wants to work it) can fix any security issues that may occur I don't…
AFIK they removed it only to move it to their paid version, didn't they?
Re: MinIO is now in maintenance-mode
#118Earlier quoted context omitted.
Downvoted because nobody knows how far a distance 39.5 feet is.
they do if they know the shoe size of the person who measured it
Your brain is full of spiders
You've got garlic in your soul, Mr. Grinch
I wouldn't touch you with a
39 and a half foot pole!Re: MinIO is now in maintenance-mode
#119Minio is more or less feature complete for most use cases. Actually the last big update of minio removed features (the UI). I am using minio for 5 years and haven't messed with it or used any new thingie for the last 5 years (i.e since I installed it); I only update to new versions. So if the minio maintainers (or anybody that forks the project and wants to work it) can fix any security issues that may occur I don't…
> Actually the last big update of minio removed features (the UI) AFIK they removed it only to move it to their paid version, didn't they?