Skip to content

Commit 2366391

Browse files
committed
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 <[email protected]>
1 parent b7328fe commit 2366391

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

doc/cephadm/host-management.rst

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -303,14 +303,18 @@ Setting the initial CRUSH location of host
303303
==========================================
304304

305305
Hosts can contain a ``location`` identifier which will instruct cephadm to
306-
create a new CRUSH host located in the specified hierarchy.
306+
create a new CRUSH host bucket located in the specified hierarchy.
307+
You can specify more than one element of the tree when doing so (for
308+
instance if you want to ensure that the rack that a host is being
309+
added to is also added to the default bucket), for example:
307310

308311
.. code-block:: yaml
309312
310313
service_type: host
311314
hostname: node-00
312315
addr: 192.168.0.10
313316
location:
317+
root: default
314318
rack: rack1
315319
316320
.. note::

0 commit comments

Comments
 (0)