From c63f8940ee0bc407ead80d857c3e9c549c8562ab Mon Sep 17 00:00:00 2001 From: Hans van den Bogert Date: Sun, 17 Sep 2017 18:29:24 +0200 Subject: [PATCH] doc: refer to CustomResourceDefinition and not TPR Signed-off-by: Hans van den Bogert --- Documentation/advanced-configuration.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/advanced-configuration.md b/Documentation/advanced-configuration.md index 285674091..64607d90a 100644 --- a/Documentation/advanced-configuration.md +++ b/Documentation/advanced-configuration.md @@ -232,7 +232,7 @@ ID WEIGHT TYPE NAME UP/DOWN REWEIGHT PRIMARY-AFFINITY Now we have a separate storage group for our SSDs, but we can't use that storage until we associate a pool with it. The default group already has a pool called -`rbd` in many cases. If you [created a pool via ThirdPartyResource](pool-crd.md), +`rbd` in many cases. If you [created a pool via CustomResourceDefinition](pool-crd.md), it will use the default storage group as well. Here's how to create new pools: @@ -299,7 +299,7 @@ and OSDs in the `default` root hierarchy. The `size` setting of a pool tells the cluster how many copies of the data should be kept for redundancy. By default the cluster will distribute these copies between `host` buckets in the CRUSH Map This can be set when [creating a -pool via ThirdPartyResource](pool-crd.md) or after creation with `ceph`. +pool via CustomResourceDefinition](pool-crd.md) or after creation with `ceph`. So for example let's change the `size` of the `rbd` pool to three: