List features in documentation #365

New issue

Closed

opened 2022-08-25 17:38:51 +00:00 by lx · 3 comments

lx commented

2022-08-25 17:38:51 +00:00

Owner

Features we want to mention:

Provides an S3 API
Geo-distributed
Several replication modes (1 copy, 2 copies, 3 copies, with various levels of consistency)
REST API for administration
Exports metrics and traces
more ?

Currently, we have no page in our documentation that lists all of Garage's features. We should add this at visible locations (maybe even on the front page), or at least add visible links, because features are the main selling point. Features we want to mention: - Provides an S3 API - Geo-distributed - Several replication modes (1 copy, 2 copies, 3 copies, with various levels of consistency) - REST API for administration - Exports metrics and traces - more ?

👍 1

lx added the

scope

documentation

label 2022-08-25 17:38:59 +00:00

quentin commented

2022-08-25 17:57:22 +00:00

Owner

"Flexible topology" -> this is an important feature, minio deployments are way more static.

quentin commented

2022-08-25 18:00:52 +00:00

Owner

Also thinking to:

Many node discovery methods: Kubernetes integration, Nomad integration through Consul
Support Dynamic IP addresses (as long as all nodes don't change their IP at the same time)
Standalone/self contained
Can expose websites (remember, only Amazon offers this, and maybe Ceph partially but definitely not Minio)
Scoped buckets: 2 users can have a different bucket with the same name -> avoid collision. Helpful if you want to write an application that creates per-user bucket always with the same name.

Also thinking to: - Many node discovery methods: Kubernetes integration, Nomad integration through Consul - Support Dynamic IP addresses (as long as all nodes don't change their IP at the same time) - Standalone/self contained - Can expose websites (remember, only Amazon offers this, and maybe Ceph partially but definitely not Minio) - Scoped buckets: 2 users can have a different bucket with the same name -> avoid collision. Helpful if you want to write an application that creates per-user bucket always with the same name.

👍 1

quentin commented

2022-08-25 18:45:33 +00:00

Owner

Also thinking to "Bucket alias". It has many interesting outcomes:

bucket renaming is possible
the same bucket may have multiple names (useful when exposing websites for example)

Also thinking to "Bucket alias". It has many interesting outcomes: - bucket renaming is possible - the same bucket may have multiple names (useful when exposing websites for example)

lx added this to the v0.8 milestone 2022-09-14 11:39:14 +00:00

lx referenced this issue from a pull request that will close it,

2022-09-15 12:11:43 +00:00

updates to documentation for v0.8 #385

lx closed this issue

2022-09-19 08:45:12 +00:00