Bringing Loic into CC in hopes he'll correct my mistakes and
misconceptions below.
So systemd is digging around in /dev and /sys proding for devices with
Ceph properties, and then starts the required ceph-(mon|osd|mds|mgr).
Or Udev-events telling systemd to act on a device that presents itself
in the system?
I don't know about ceph-(mon|mds|mgr), but for osd it works
approximately like the following:
See udev/95-ceph-osd.rules
systemd triggers udev, and the udev rules look for partitions with
certain "partition GUID codes" ("ceph data" and "ceph journal"
respectively) and run "ceph-disk trigger" on them.
Cluster deployment tooling is expected to run "ceph-disk prepare" to set
up the partition GUID codes. AFAIK "ceph-disk activate" is run for each
OSD at startup as a consequence of "ceph-disk trigger".
HTH,
Nathan
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
