update sources to 12.2.7

[ceph.git] / ceph / doc / ceph-volume / lvm / activate.rst

diff --git a/ceph/doc/ceph-volume/lvm/activate.rst b/ceph/doc/ceph-volume/lvm/activate.rst
index 66bed5a82e9b654f6d960e99dbae1476dced8f3c..e757f5266e5ae10226892ccb50d86dfebf0ff015 100644 (file)
--- a/ceph/doc/ceph-volume/lvm/activate.rst
+++ b/ceph/doc/ceph-volume/lvm/activate.rst
@@ -22,6 +22,18 @@ need to be supplied. For example::
 .. note:: The UUID is stored in the ``fsid`` file in the OSD path, which is
           generated when :ref:`ceph-volume-lvm-prepare` is used.
 
+Activating all OSDs
+-------------------
+It is possible to activate all existing OSDs at once by using the ``--all``
+flag. For example::
+
+    ceph-volume lvm activate --all
+
+This call will inspect all the OSDs created by ceph-volume that are inactive
+and will activate them one by one. If any of the OSDs are already running, it
+will report them in the command output and skip them, making it safe to rerun
+(idempotent).
+
 requiring uuids
 ^^^^^^^^^^^^^^^
 The :term:`OSD uuid` is being required as an extra step to ensure that the
@@ -29,6 +41,13 @@ right OSD is being activated. It is entirely possible that a previous OSD with
 the same id exists and would end up activating the incorrect one.
 
 
+dmcrypt
+^^^^^^^
+If the OSD was prepared with dmcrypt by ceph-volume, there is no need to
+specify ``--dmcrypt`` on the command line again (that flag is not available for
+the ``activate`` subcommand). An encrypted OSD will be automatically detected.
+
+
 Discovery
 ---------
 With either existing OSDs or new ones being activated, a *discovery* process is
@@ -63,9 +82,11 @@ The systemd unit will look for the matching OSD device, and by looking at its
 
 Existing OSDs
 -------------
-For exsiting OSDs that have been deployed with different tooling, the only way
-to port them over to the new mechanism is to prepare them again (losing data).
-See :ref:`ceph-volume-lvm-existing-osds` for details on how to proceed.
+For existing OSDs that have been deployed with ``ceph-disk``, they need to be
+scanned and activated :ref:`using the simple sub-command <ceph-volume-simple>`.
+If a different tooling was used then the only way to port them over to the new
+mechanism is to prepare them again (losing data). See
+:ref:`ceph-volume-lvm-existing-osds` for details on how to proceed.
 
 Summary
 -------