Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Update README.md on Ceph section #10220

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update README.md on Ceph section #10220

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
23 changes: 22 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3907,10 +3907,31 @@ True

<details>
<summary>What is the workflow of retrieving data from Ceph?</summary><br><b>
The work flow is as follows:

1. The client sends a request to the ceph cluster to retrieve data:
> **Client could be any of the following**
>> * Ceph Block Device
>> * Ceph Object Gateway
>> * Any third party ceph client


2. The client retrieves the latest cluster map from the Ceph Monitor
3. The client uses the CRUSH algorithm to map the object to a placement group. The placement group is then assigned to a OSD.
4. Once the placement group and the OSD Daemon are determined, the client can retrieve the data from the appropriate OSD


</b></details>

<details>
<summary>What is the workflow of retrieving data from Ceph?</summary><br><b>
<summary>What is the workflow of writing data to Ceph?</summary><br><b>
The work flow is as follows:

1. The client sends a request to the ceph cluster to retrieve data
2. The client retrieves the latest cluster map from the Ceph Monitor
3. The client uses the CRUSH algorithm to map the object to a placement group. The placement group is then assigned to a Ceph OSD Daemon dynamically.
4. The client sends the data to the primary OSD of the determined placement group. If the data is stored in an erasure-coded pool, the primary OSD is responsible for encoding the object into data chunks and coding chunks, and distributing them to the other OSDs.

</b></details>

<details>
Expand Down