awesome/devops-exercises
1
0
Fork 0
mirror of https://github.com/bregman-arie/devops-exercises.git synced 2024-11-19 20:31:47 +02:00
Code Issues Releases Activity

Update README.md on Ceph section (#10220)

Browse Source 
1. The "What is the workflow of retrieving data from Ceph?" question was repeated twice.
2. Added the question "What is the workflow of writing data to Ceph?"
3. There was no answer on the workflow on  writeing/reading data. They have been added
This commit is contained in:
Ali 2024-06-12 12:46:52 +03:30 committed by GitHub
parent f893160e75
commit afacd3885f
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 22 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
README.md
View File

@ -3953,10 +3953,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>