-
Notifications
You must be signed in to change notification settings - Fork 535
HDDS-12727. Document high level architecture of S3 Gateway #8184
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
Change-Id: I455848c2d5d2ee65cdce7456814cb4e5e8247973
@kerneltime please review this |
Ozone separates metadata and data management: | ||
- **Ozone Manager (OM):** Handles volumes, buckets, keys. | ||
- **Storage Container Manager (SCM):** Manages DataNodes and allocates containers (storage units). | ||
- **DataNodes:** Store the actual data chunks. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is redundant on this page in the broader context.
|
||
### Mapping S3 to Ozone Concepts | ||
|
||
In Ozone, data is organized into **volumes**, **buckets**, and **keys**. By default, the S3 Gateway uses a special volume named `/s3v` to store all S3 buckets. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is not entirely accurate as the volume name can be changed. Also, bucket linking needs to be discussed.
|
||
This simplifies scaling and failure recovery. | ||
|
||
### Authentication and Security |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This section needs to touch kerberos.
Please include the LLM footer |
What changes were proposed in this pull request?
HDDS-12727. [Docs] High level architecture of Ozone S3 Gateway.
Please describe your PR in detail:
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-12727
How was this patch tested?
Doc only.