.. code-block:: bash
cephadm rm-daemon --fsid CLUSTER_ID --name SERVICE_NAME
+
+
+.. _cephadm-spec-unmanaged:
+
+Disable automatic deployment of daemons
+=======================================
+
+Cephadm supports disabling the automated deployment and removal of daemons per service. In
+this case, the CLI supports two commands that are dedicated to this mode.
+
+To disable the automatic management of dameons, apply
+the :ref:`orchestrator-cli-service-spec` with ``unmanaged=True``.
+
+``mgr.yaml``:
+
+.. code-block:: yaml
+
+ service_type: mgr
+ unmanaged: true
+ placement:
+ label: mgr
+
+.. code-block:: bash
+
+ ceph orch apply -i mgr.yaml
+
+.. note::
+
+ cephadm will no longer deploy any new daemons, if the placement
+ specification matches additional hosts.
+
+To manually deploy a daemon on a host, please execute:
+
+.. code-block:: bash
+
+ ceph orch daemon add <daemon-type> --placement=<placement spec>
+
+For example
+
+.. code-block:: bash
+
+ ceph orch daemon add mgr --placement=my_host
+
+To manually remove a daemon, please run:
+
+.. code-block:: bash
+
+ ceph orch daemon rm <daemon name>... [--force]
+
+For example
+
+.. code-block:: bash
+
+ ceph orch daemon rm mgr.my_host.xyzxyz
+
+.. note::
+
+ For managed services (``unmanaged=False``), cephadm will automatically
+ deploy a new daemon a few seconds later.
+
+* See :ref:`orchestrator-cli-create-osds` for special handling of unmanaged OSDs.
+* See also :ref:`cephadm-pause`
\ No newline at end of file
As cephadm deploys daemons as containers, troubleshooting daemons is slightly
different. Here are a few tools and commands to help investigating issues.
+.. _cephadm-pause:
+
Pausing or disabling cephadm
----------------------------
deployed daemon containers will still continue to exist and start as they
did before.
+Please refer to :ref:`cephadm-spec-unmanaged` for disabling individual
+services.
+
Per-service and per-daemon events
---------------------------------
ceph orch apply osd --all-available-devices --unmanaged=true
+* For cephadm, see also :ref:`cephadm-spec-unmanaged`.
+
Remove an OSD
-------------
::
If set to ``true``, the orchestrator will not deploy nor
remove any daemon associated with this service. Placement and all other
properties will be ignored. This is useful, if this service should not
- be managed temporarily.
+ be managed temporarily. For cephadm, See :ref:`cephadm-spec-unmanaged`
Each service type can have additional service specific properties.