From: Adam King Date: Fri, 29 Sep 2023 19:32:53 +0000 (-0400) Subject: doc/cephadm: document --rm-crush-entry host rm flag X-Git-Tag: v19.0.0~152^2~2 X-Git-Url: http://git-server-git.apps.pok.os.sepia.ceph.com/?a=commitdiff_plain;h=c2ecc9d95fe5a211cb55fc68aba9692e39e85668;p=ceph.git doc/cephadm: document --rm-crush-entry host rm flag Signed-off-by: Adam King --- diff --git a/doc/cephadm/host-management.rst b/doc/cephadm/host-management.rst index 4b964c5f455..c1aa88cd60a 100644 --- a/doc/cephadm/host-management.rst +++ b/doc/cephadm/host-management.rst @@ -316,10 +316,33 @@ create a new CRUSH host located in the specified hierarchy. The ``location`` attribute will be only affect the initial CRUSH location. Subsequent changes of the ``location`` property will be ignored. Also, removing a host will not remove - any CRUSH buckets. + any CRUSH buckets unless the ``--rm-crush-entry`` flag is provided to the ``orch host rm`` command See also :ref:`crush_map_default_types`. +Removing a host from the CRUSH map +================================== + +The ``ceph orch host rm`` command has support for removing the bucket entry for the host +in the CRUSH map. This is done by providing the ``--rm-crush-entry`` flag. + +.. prompt:: bash [ceph:root@host1/]# + + ceph orch host rm host1 --rm-crush-entry + +When this flag is specified, cephadm will attempt to remove the bucket entry +for the host from the CRUSH map as part of the host removal process. Note that if +it fails to do so, cephadm will report the failure and the host will remain under +cephadm control. + +.. note:: + + The removal from the CRUSH map will fail if there are OSDs deployed on the + host. If you would like to remove all the host's OSDs as well, please start + by using the ``ceph orch host drain`` command to do so. Once the OSDs + are all gone, then you may have cephadm remove the CRUSH entry along with the + host using the ``--rm-crush-entry`` flag. + OS Tuning Profiles ==================