From e9527e65d5da503107e21dc5b695f287c8529049 Mon Sep 17 00:00:00 2001 From: Alfredo Deza Date: Tue, 7 Nov 2017 13:41:12 -0500 Subject: [PATCH] doc/ceph-volume lvm add back a system.rst with just the lvm portion of it Signed-off-by: Alfredo Deza (cherry picked from commit f872cd29b93e02b77172f7b382c4746af9ba845d) --- doc/ceph-volume/lvm/systemd.rst | 28 ++++++++++++++++++++++++++++ 1 file changed, 28 insertions(+) create mode 100644 doc/ceph-volume/lvm/systemd.rst diff --git a/doc/ceph-volume/lvm/systemd.rst b/doc/ceph-volume/lvm/systemd.rst new file mode 100644 index 000000000000..30260de7e882 --- /dev/null +++ b/doc/ceph-volume/lvm/systemd.rst @@ -0,0 +1,28 @@ +.. _ceph-volume-lvm-systemd: + +systemd +======= +Upon startup, it will identify the logical volume using :term:`LVM tags`, +finding a matching ID and later ensuring it is the right one with +the :term:`OSD uuid`. + +After identifying the correct volume it will then proceed to mount it by using +the OSD destination conventions, that is:: + + /var/lib/ceph/osd/- + +For our example OSD with an id of ``0``, that means the identified device will +be mounted at:: + + + /var/lib/ceph/osd/ceph-0 + + +Once that process is complete, a call will be made to start the OSD:: + + systemctl start ceph-osd@0 + +The systemd portion of this process is handled by the ``ceph-volume lvm +trigger`` sub-command, which is only in charge of parsing metadata coming from +systemd and startup, and then dispatching to ``ceph-volume lvm activate`` which +would proceed with activation. -- 2.47.3