From: Zac Dover Date: Sun, 29 Oct 2023 12:15:13 +0000 (+1000) Subject: doc/ceph-volume: improve front matter X-Git-Tag: v17.2.8~710^2 X-Git-Url: http://git-server-git.apps.pok.os.sepia.ceph.com/?a=commitdiff_plain;h=refs%2Fpull%2F54236%2Fhead;p=ceph.git doc/ceph-volume: improve front matter Simplify and improve the readability of the front matter of doc/ceph-volume/lvm/activate.rst. Co-authored-by: Anthony D'Atri Signed-off-by: Zac Dover (cherry picked from commit 23190dd91861d1dcb8d03b78fb378e042394dfad) --- diff --git a/doc/ceph-volume/lvm/activate.rst b/doc/ceph-volume/lvm/activate.rst index 58889ca837b..10ad99c7525 100644 --- a/doc/ceph-volume/lvm/activate.rst +++ b/doc/ceph-volume/lvm/activate.rst @@ -3,19 +3,20 @@ ``activate`` ============ -Once :ref:`ceph-volume-lvm-prepare` is completed, and all the various steps -that entails are done, the volume is ready to get "activated". +After :ref:`ceph-volume-lvm-prepare` has completed its run, the volume can be +activated. -This activation process enables a systemd unit that persists the OSD ID and its -UUID (also called ``fsid`` in Ceph CLI tools), so that at boot time it can -understand what OSD is enabled and needs to be mounted. +Activating the volume involves enabling a ``systemd`` unit that persists the +``OSD ID`` and its ``UUID`` (which is also called the ``fsid`` in the Ceph CLI +tools). After this information has been persisted, the cluster can determine +which OSD is enabled and must be mounted. .. note:: The execution of this call is fully idempotent. This means that the call can be executed multiple times without changing the result of its first successful execution. -For OSDs deployed by cephadm, please refer to :ref:`cephadm-osd-activate` -instead. +For information about OSDs deployed by cephadm, refer to +:ref:`cephadm-osd-activate`. New OSDs --------