]>
Commit | Line | Data |
---|---|---|
3efd9988 FG |
1 | .. _ceph-volume-simple-systemd: |
2 | ||
3 | systemd | |
4 | ======= | |
5 | Upon startup, it will identify the logical volume by loading the JSON file in | |
6 | ``/etc/ceph/osd/{id}-{uuid}.json`` corresponding to the instance name of the | |
7 | systemd unit. | |
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 | ||
20 | ||
21 | Once that process is complete, a call will be made to start the OSD:: | |
22 | ||
23 | systemctl start ceph-osd@0 | |
24 | ||
25 | The systemd portion of this process is handled by the ``ceph-volume simple | |
26 | trigger`` sub-command, which is only in charge of parsing metadata coming from | |
27 | systemd and startup, and then dispatching to ``ceph-volume simple activate`` which | |
28 | would proceed with activation. |