Skip to content

Commit 2ee87b3

Browse files
authored
Merge pull request ceph#54232 from zdover23/wip-doc-2023-10-29-ceph-volume-lvm-activate-2
doc/ceph-volume: improve front matter Reviewed-by: Anthony D'Atri <[email protected]>
2 parents a91ba13 + 23190dd commit 2ee87b3

File tree

1 file changed

+8
-7
lines changed

1 file changed

+8
-7
lines changed

doc/ceph-volume/lvm/activate.rst

Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -3,19 +3,20 @@
33
``activate``
44
============
55

6-
Once :ref:`ceph-volume-lvm-prepare` is completed, and all the various steps
7-
that entails are done, the volume is ready to get "activated".
6+
After :ref:`ceph-volume-lvm-prepare` has completed its run, the volume can be
7+
activated.
88

9-
This activation process enables a systemd unit that persists the OSD ID and its
10-
UUID (also called ``fsid`` in Ceph CLI tools), so that at boot time it can
11-
understand what OSD is enabled and needs to be mounted.
9+
Activating the volume involves enabling a ``systemd`` unit that persists the
10+
``OSD ID`` and its ``UUID`` (which is also called the ``fsid`` in the Ceph CLI
11+
tools). After this information has been persisted, the cluster can determine
12+
which OSD is enabled and must be mounted.
1213

1314
.. note:: The execution of this call is fully idempotent. This means that the
1415
call can be executed multiple times without changing the result of its first
1516
successful execution.
1617

17-
For OSDs deployed by cephadm, please refer to :ref:`cephadm-osd-activate`
18-
instead.
18+
For information about OSDs deployed by cephadm, refer to
19+
:ref:`cephadm-osd-activate`.
1920

2021
New OSDs
2122
--------

0 commit comments

Comments
 (0)