Replies: 2 comments
-
|
Hi @silvanias You are trying to compare volume concept with respect to S3, about its benefits. One of benefit is "multi-tenancy feature" where a volume can be managed by respective tenant completely. Below are details about the feature: Having volume a top entity designed to have better administrative control, some of description is given in below link, Few of benefits as summary:
|
Beta Was this translation helpful? Give feedback.
-
|
We are working on a new documentation website which is for now hosted here: https://kerneltime.github.io/ozone-site/docs/core-concepts/namespace/volumes/overview/ |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi Ozone team,
Hope you're all doing well! My colleagues and I have been working with Ozone and we're trying to better understand the design decisions around volumes.
We've noticed that volumes seem to have similar quota and permission capabilities as buckets, and since S3 doesn't have this concept, we're curious about the specific benefits and use cases that drove this design choice.
A few questions we've been discussing:
Are there any docs or design discussions we should check out, or could someone share some insights?
Thanks for all the great work on Ozone - we're really enjoying working with it!
Beta Was this translation helpful? Give feedback.
All reactions