]>
Commit | Line | Data |
---|---|---|
3efd9988 | 1 | .. _ceph-volume-lvm-systemd: |
b5b8bbf5 FG |
2 | |
3 | systemd | |
4 | ======= | |
b5b8bbf5 FG |
5 | Upon startup, it will identify the logical volume using :term:`LVM tags`, |
6 | finding a matching ID and later ensuring it is the right one with | |
7 | the :term:`OSD uuid`. | |
8 | ||
9 | After identifying the correct volume it will then proceed to mount it by using | |
10 | the OSD destination conventions, that is:: | |
11 | ||
12 | /var/lib/ceph/osd/<cluster name>-<osd id> | |
13 | ||
14 | For our example OSD with an id of ``0``, that means the identified device will | |
15 | be mounted at:: | |
16 | ||
17 | ||
18 | /var/lib/ceph/osd/ceph-0 | |
19 | ||
3efd9988 | 20 | |
b5b8bbf5 FG |
21 | Once that process is complete, a call will be made to start the OSD:: |
22 | ||
23 | systemctl start ceph-osd@0 | |
3efd9988 FG |
24 | |
25 | The systemd portion of this process is handled by the ``ceph-volume lvm | |
26 | trigger`` sub-command, which is only in charge of parsing metadata coming from | |
27 | systemd and startup, and then dispatching to ``ceph-volume lvm activate`` which | |
28 | would proceed with activation. |