From 4d9ca8cb58d663705e9cb773fa2d1658735f998d Mon Sep 17 00:00:00 2001 From: Matthew Vernon Date: Wed, 22 May 2024 16:31:33 +0100 Subject: [PATCH] doc: clarify use of location: in host spec It wasn't clear that you can specify more than one element of the CRUSH hierarchy in a spec file, nor that it might be useful to do so (e.g. to ensure the host ends up beneath the default root). So update the text to make it clearer, and similarly the example. Signed-off-by: Matthew Vernon (cherry picked from commit 2366391ccec0fb6d8a1c159d6e3cdf5ff4f1d603) --- doc/cephadm/host-management.rst | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/doc/cephadm/host-management.rst b/doc/cephadm/host-management.rst index 1fba8e582d3..05c0ccf97d6 100644 --- a/doc/cephadm/host-management.rst +++ b/doc/cephadm/host-management.rst @@ -303,7 +303,10 @@ Setting the initial CRUSH location of host ========================================== Hosts can contain a ``location`` identifier which will instruct cephadm to -create a new CRUSH host located in the specified hierarchy. +create a new CRUSH host bucket located in the specified hierarchy. +You can specify more than one element of the tree when doing so (for +instance if you want to ensure that the rack that a host is being +added to is also added to the default bucket), for example: .. code-block:: yaml @@ -311,6 +314,7 @@ create a new CRUSH host located in the specified hierarchy. hostname: node-00 addr: 192.168.0.10 location: + root: default rack: rack1 .. note:: -- 2.39.5