From 8a19c730367b4d4cc4e172692cc4dcbed83d0bf3 Mon Sep 17 00:00:00 2001 From: Travis Nielsen Date: Wed, 12 Feb 2020 17:29:21 -0700 Subject: [PATCH] ceph: clarify docs for erasure coding 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 --- Documentation/ceph-pool-crd.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/ceph-pool-crd.md b/Documentation/ceph-pool-crd.md index ec4e0edd5..50cb9f1d0 100644 --- a/Documentation/ceph-pool-crd.md +++ b/Documentation/ceph-pool-crd.md @@ -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.