From: zdover23 Date: Mon, 30 Oct 2023 00:54:32 +0000 (+1000) Subject: Merge pull request #54232 from zdover23/wip-doc-2023-10-29-ceph-volume-lvm-activate-2 X-Git-Tag: v19.0.0~232 X-Git-Url: http://git-server-git.apps.pok.os.sepia.ceph.com/?a=commitdiff_plain;h=2ee87b3e4d9054952021e2c0792c738d281c1760;p=ceph.git Merge pull request #54232 from zdover23/wip-doc-2023-10-29-ceph-volume-lvm-activate-2 doc/ceph-volume: improve front matter Reviewed-by: Anthony D'Atri --- 2ee87b3e4d9054952021e2c0792c738d281c1760 diff --cc doc/ceph-volume/lvm/activate.rst index 3f86e98b70cc7,bf7dab06aef35..fe34ecb713a98 --- a/doc/ceph-volume/lvm/activate.rst +++ b/doc/ceph-volume/lvm/activate.rst @@@ -3,19 -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, and there is no - side-effects when running multiple times +.. 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 --------