y4m4b4

Attribution needs to be explicit for Open Source Licenses prominently available for customers to look at.

Making money off from another product calling it your own innovation is plagiarism.

https://www.weka.io/blog/cloud-storage/amazon-s3-protocol/

There is never a mention of that it uses MinIO underneath.

Of course they use it, its there in their container :-)

Nutanix does not carry EULA or reference even today while continuing to use it.

Read Apache v2 attribution clauses.

Ask your corporate to pay for it.

I am glad they kept AGPLv3 to keep freeloaders in corporate under check.

No, gateway mode is EOL'ed and it is not taking any new features

AWS drive speed has not changed much, neither is their network for the same instance and model.

https://github.com/minio/minio/tree/master/docs/distributed#... - MinIO has been strictly consistent from Day 1.

AWS S3 recently launched strict consistency.

Wasabi is eventually consistent for overwrites ``eventual consistency for overwrite HTTP PUTs and HTTP DELETEs``

This is not the same.

https://github.com/minio/minio is here

For all enthusiastic folks you may want to read more here on SipHash comparisons

https://github.com/fwessels/HashCompare/blob/master/README.m...

https://github.com/fwessels/HashCompare/issues/1

There is no C++ in the code, it is a native Go library of Google's HighwayHash implementation

With 16 x 8TB drives, we are talking about 64TB usable space after erasure coding. Minio is designed to serve the needs of a single tenant - 64TB is usually much bigger than a single tenant's needs. However you often see 100s of thousands of such tenants in a cloud like environment.

Making a single large PB sized volume where the disks and nodes are managed like a blackbox by the filesystem is quite scary to us at Minio. Any crash means we blew up all the tenants at once. 1000s of individual Minio tenants means, we know when we add the million'th minio instance, it is not any more complex than the first instance of Minio.

Provisioning with k8s [1], mesos [2] or other external orchestration tools is better than Minio's own resource management system. When it comes to the applications, objects are just represented as URLs. Some data sitting on Amazon S3 and some on Minio makes no difference to the application.

We are also planning to introduce a namespace layer to work on top to combine these individual tenants into single namespace. This would allow you to transparently add new clusters as you scale without loosing the ability to have a single namespace.

We hang out at slack [3], please reach out if you have further questions.

[1] - https://github.com/kubernetes/charts/tree/master/stable/mini... [2] - https://github.com/dcos/examples/tree/master/1.8/minio [3] - https://slack.minio.io

For that you can just do

```

package main

import minio "github.com/minio/minio/cmd"

func main() {

        go minio.Main()

        ... do your stuff ...

}

```

GNU AGPL is an ideal license for free software projects. We are a strong supporter of the GNU project. We chose Apache License for Minio purely for adoption reasons. Most of our users build proprietary software around Minio and their legal council has a default NO policy towards GNU licenses. Besides, FSF has also approved Apache License v2 as a free software license.

Proprietary forks are OK with us. It will be too expensive to maintain branches of their own and catch up with the upstream.

Quite easy actually you can look at

https://github.com/restic/restic/blob/master/run_integration...

Currently we have a single node multi disk version relevant docs here - https://docs.minio.io/docs/minio-erasure-code-quickstart-gui...

We are also about to finish distributed server functionality you can track the work here https://github.com/minio/minio/tree/distributed

Additionally "SwiftTempURLs" equivalent is called PresignedURLs in S3 API so we indeed support that as well.

Relevant docs here https://docs.minio.io/docs/using-pre-signed-urls-to-download...

Yes definitely you can read our docs here https://docs.minio.io/docs/minio-erasure-code-quickstart-gui... for more understanding and even hardware recommendations.

We are currently working on the distributed version and will be making a beta release soon.

Currently minio supports

- pure FS backend with single disk - pure Erasure coded backend with multiple disks on single node (like ZFS)

For more information you can read here - https://docs.minio.io/docs/minio-erasure-code-quickstart-gui...

We do not do any sort of replication erasure code handles disk failures and we also implement transparent bit-rot protection as well.

To replicate one setup to many you can use 'mc mirror -w' which would watch on events and do continuous replication.

Relevant docs can be found here

https://docs.minio.io/docs/minio-client-complete-guide#mirro...

Great to know, we explored sqlite didn't serve our purpose earlier. Feel free to open a bug and we will evaluate it.

Gollum is a great project and it is really nice to see great supportive community around it.

Doctor only solves a niche problem of serving existing content, aggregating it and managing it using github.com directly.

Postgres is generally for the CRUD in grouping, aggregating/associating and customization. Do you have any better suggestion?

Feel free to play with it and give us your feedback.

Yes true. OpenSSL version gives a great boost. Rather than SHA512 we ended up using Blake2b - https://github.com/minio/blake2b-simd (also optimized with SIMD instructions) internally for bit-rot verification in https://github.com/minio/minio

Thanks this is a nice share, we are definitely looking forward to this.

This is the plan, which will happen eventually right now we are keeping it out there for community comments and improvement in quality that might be needed before it is submitted upstream.

For comparison with other checksums you should look here

https://github.com/minio/sha256-simd#comparison-to-other-has...

Another project to be added to this list would be

https://github.com/minio/minio - Minio is an object storage server compatible with Amazon S3 and licensed under Apache 2.0 License.

Disclaimer: I work for Minio.

Hello HN,

Here is a bit more explanation about erasure code and bit-rot protection.

Minio along with being S3 compatible also protects data against hardware failures and silent data corruption using erasure code and checksums. You may lose roughly half the number ((N/2)-1) of drives and still be able to recover the data.

Minio uses Reed-Solomon code to stripe objects into N/2 data and N/2 parity blocks. This means that in a 12 drive setup, an object is striped across as 6 data and 6 parity blocks. You can lose as many as 5 drives (be it parity or data) and still reconstruct the data reliably from the remaining drives.

Minio also supports bit-rot detection transparently which works along with erasure code using high speed BLAKE2 - https://github.com/minio/blake2b-simd hash based checksums.

Thanks @unknownhad

Minio Go library is a simple client library for S3 compatible cloud storage servers. Supports AWS Signature Version 4 and 2. AWS Signature Version 4 is chosen as default.

List of supported cloud storage providers.

* AWS Signature Version 4 - Amazon S3, Minio

* AWS Signature Version 2 - Google Cloud Storage (Compatibility Mode), Openstack Swift + Swift3 middleware, Ceph Object Gateway, Riak CS