feedc0de/my-rook-config
1
0
Fork 0
forked from rook/rook
Code Pull Requests Activity

ceph: clarify docs for erasure coding

Browse Source 
Setting up the topology for the CRUSH map was outdated in the EC doc.
Now a link to the node labels is provided for the configuration.

Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
This commit is contained in:
Travis Nielsen
2020-03-16 15:13:52 -06:00
parent 9c5c78cf01
commit 8a19c73036
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Documentation/ceph-pool-crd.md
+2 -2
View File
@@ -106,6 +106,6 @@ The `failureDomain` must be also be taken into account when determining the numb
* `host`: All chunks will be placed on unique hosts
* `osd`: All chunks will be placed on unique OSDs
If you do not have a sufficient number of hosts or OSDs for unique placement the pool can be created, although a PUT to the pool will hang.
If you do not have a sufficient number of hosts or OSDs for unique placement the pool can be created, a PUT to the pool will hang.
Rook currently only configures two levels in the CRUSH map. It is also possible to configure other levels such as `rack` with the [Ceph tools](http://docs.ceph.com/docs/master/rados/operations/crush-map/).
Rook currently only configures two levels in the CRUSH map. It is also possible to configure other levels such as `rack` with by adding [topology labels](ceph-cluster-crd.md#osd-topology) to the nodes.