-
Notifications
You must be signed in to change notification settings - Fork 0
Fix/add object detail #57
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -19,7 +19,9 @@ At the top of the page, you will find a dashboard summarizing the state of S3 st | |
|
|
||
| <CardGrid> | ||
| <Card title="Bucket" icon="tabler:bucket"> | ||
| The total number of S3 buckets currently defined in the system. | ||
| The total number of S3 buckets currently defined in the system. | ||
|
|
||
| The RGW endpoint IP that clients use to access the bucket via S3-compatible APIs. | ||
| </Card> | ||
|
Comment on lines
21
to
25
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The information about the RGW endpoint seems misplaced within the "Bucket" card, which primarily describes the total count of buckets. The RGW endpoint is a service-level detail that applies to all buckets. Consider moving this information to a more general location, such as the introductory paragraph of the "Bucket" section (around line 14) or the main "Object" page introduction (around line 8), for better logical organization. |
||
| <Card title="Usage" icon="tabler:chart-pie"> | ||
| The combined storage consumption across all buckets, including object data and metadata overhead. | ||
|
|
@@ -30,12 +32,12 @@ At the top of the page, you will find a dashboard summarizing the state of S3 st | |
|
|
||
| The Bucket table displays a list of all buckets. The table includes the following information: | ||
|
|
||
| | Column | Description | | ||
| | :--------------- | :---------------------------------------------- | | ||
| | **Name** | The name of the bucket. | | ||
| | **Owner** | The user ID of the bucket owner. | | ||
| | **Usage** | The total size of objects stored in the bucket. | | ||
| | **Created Time** | The creation timestamp of the bucket. | | ||
| | Column | Description | | ||
| | :--------------- | :-------------------------------------------------------------------------- | | ||
| | **Name** | The name of the bucket. | | ||
| | **Owner** | The user ID of the bucket owner. | | ||
| | **Usage** | The total size of objects stored in the bucket. | | ||
| | **Created Time** | Displays how long ago the bucket was created, relative to the current time. | | ||
|
|
||
| ### Create Bucket | ||
|
|
||
|
|
@@ -52,6 +54,32 @@ You can create new buckets to store your data. | |
|
|
||
| </Steps> | ||
|
|
||
| ### Access Bucket with S3 Browser | ||
|
|
||
| This section demonstrates how to access a Ceph Object Gateway (RGW) bucket using S3 Browser, a graphical S3 client. | ||
| This approach is useful for manual verification, browsing objects, and basic upload/download operations without writing code. | ||
|
|
||
| #### Prerequisites | ||
| - S3 Browser installed on the client machine (Windows). | ||
|
|
||
| <Steps> | ||
|
|
||
| 1. Create a user in User section. | ||
| 2. Create an access key for the user and copy the secret key. | ||
| 3. Create a bucket and assign the user as the owner. The bucket owner always has full control of the bucket regardless of the selected ACL. | ||
| 4. Open S3 Browser. | ||
| 5. Fill in the account settings: | ||
| - Account type: S3 compatible storage | ||
| - API endpoint: RGW endpoint | ||
| - Access Key ID: User’s access key. | ||
| - Secret Access Key: The copied secret key. | ||
| - Use secure transfer: Disable SSL | ||
| 6. Add new account | ||
|
|
||
| </Steps> | ||
|
|
||
|
|
||
|
|
||
|
Comment on lines
+67
to
+82
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This new section is a great addition! To make it even clearer for users, I've suggested a few improvements:
Additionally, in step 5, could you clarify where the user can find the |
||
| ### Manage Buckets | ||
|
|
||
| You can modify or delete existing buckets using the **Actions** menu. | ||
|
|
@@ -81,7 +109,7 @@ Permanently removes a bucket and all its objects. | |
| </Steps> | ||
|
|
||
| <Aside type="danger"> | ||
| Deleting a Object bucket is irreversible. Ensure that you have backed up any critical data. | ||
| Deleting an Object bucket is irreversible. Ensure that you have backed up any critical data. | ||
| </Aside> | ||
|
|
||
| ## User | ||
|
|
@@ -152,7 +180,7 @@ Permanently removes a user. | |
| </Steps> | ||
|
|
||
| <Aside type="danger"> | ||
| Deleting a Object user is irreversible. Ensure that you have backed up any critical data. | ||
| Deleting an Object user is irreversible. Ensure that you have backed up any critical data. | ||
| </Aside> | ||
|
|
||
| ### Manage Keys | ||
|
|
@@ -190,5 +218,5 @@ Permanently removes an access key. | |
| </Steps> | ||
|
|
||
| <Aside type="danger"> | ||
| Deleting a Object key is irreversible. Ensure that you have backed up any critical data. | ||
| Deleting an Object key is irreversible. Ensure that you have backed up any critical data. | ||
| </Aside> | ||
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.
The "Applications" step has been removed from the pool creation process in the documentation. However, the "Applications" column is still listed in the pool overview table (line 28), suggesting it's an important property. Was this removal intentional? If users can no longer set applications during creation, it would be helpful to document how this property is assigned. If it was an accidental removal, please consider adding it back.