RepoMirrors/ceph
1
0
Fork 0
mirror of https://github.com/ceph/ceph synced 2024-12-18 09:25:49 +00:00
Code Issues Packages Projects Releases Wiki Activity
69cdfcb15f
ceph/udev/95-ceph-osd.rules

44 lines
2.1 KiB
Plaintext
Raw Normal View History

udev: trigger ceph-disk-activate directly from udev There is no need to depend on upstart for this. Signed-off-by: Sage Weil <sage@inktank.com>
2013-02-14 01:30:19 +00:00
# activate ceph-tagged partitions
ACTION=="add", SUBSYSTEM=="block", \
ENV{DEVTYPE}=="partition", \
ENV{ID_PART_ENTRY_TYPE}=="4fbd7e29-9d25-41b8-afd0-062c0ceff05d", \
remove ceph-disk-{activate,prepare} wrappers These ancient aliases shouldn't be used. We should have removed them immediately way back when, honestly. Signed-off-by: Sage Weil <sage@redhat.com>
2015-07-30 14:00:29 +00:00
RUN+="/usr/sbin/ceph-disk activate /dev/$name"
udev: trigger on dmcrypted osd partitions Automatically map encrypted journal partitions. For encrypted OSD partitions, map them, wait for the mapped device to appear, and then ceph-disk-activate. This is much simpler than doing the work in ceph-disk-activate. Signed-off-by: Sage Weil <sage@inktank.com>
2013-02-14 02:22:45 +00:00
ceph-disk: implement 'activate-journal' Activate an osd via its journal device. udev populates its symlinks and triggers events in an order that is not related to whether the device is an osd data partition or a journal. That means that triggering 'ceph-disk activate' can happen before the journal (or journal symlink) is present and then fail. Similarly, it may be that they are on different disks that are hotplugged with the journal second. This can be wired up to the journal partition type to ensure that osds are started when the journal appears second. Include the udev rules to trigger this. Signed-off-by: Sage Weil <sage@inktank.com>
2013-06-13 22:54:58 +00:00
# activate ceph-tagged partitions
ACTION=="add", SUBSYSTEM=="block", \
ENV{DEVTYPE}=="partition", \
ENV{ID_PART_ENTRY_TYPE}=="45b0969e-9b03-4f30-b4c6-b4b80ceff106", \
RUN+="/usr/sbin/ceph-disk activate-journal /dev/$name"
Rework ceph-disk to allow LUKS for encrypted partitions LUKS allows for validation of the key at mount time (rather than simply mounting a random partition), specification of the encryption parameters in the header and key rollover of the slot key (the one that needs to be stored). New parameters 'osd cryptsetup parameters' and 'osd dmcrypt key size' are added. These allow these important policy choices to be overridden or kept consistent per-site. The previous default plain mode (rather than using LUKS) remains, select LUKS by setting 'osd dmcrypt type = luks' Signed-off-by: Andrew Bartlett <abartlet@catalyst.net.nz>
2014-10-30 21:29:36 +00:00
# Map journal if using dm-crypt and plain
udev: trigger on dmcrypted osd partitions Automatically map encrypted journal partitions. For encrypted OSD partitions, map them, wait for the mapped device to appear, and then ceph-disk-activate. This is much simpler than doing the work in ceph-disk-activate. Signed-off-by: Sage Weil <sage@inktank.com>
2013-02-14 02:22:45 +00:00
ACTION=="add" SUBSYSTEM=="block", \
ENV{DEVTYPE}=="partition", \
ENV{ID_PART_ENTRY_TYPE}=="45b0969e-9b03-4f30-b4c6-5ec00ceff106", \
RUN+="/sbin/cryptsetup --key-file /etc/ceph/dmcrypt-keys/$env{ID_PART_ENTRY_UUID} --key-size 256 create $env{ID_PART_ENTRY_UUID} /dev/$name"
Rework ceph-disk to allow LUKS for encrypted partitions LUKS allows for validation of the key at mount time (rather than simply mounting a random partition), specification of the encryption parameters in the header and key rollover of the slot key (the one that needs to be stored). New parameters 'osd cryptsetup parameters' and 'osd dmcrypt key size' are added. These allow these important policy choices to be overridden or kept consistent per-site. The previous default plain mode (rather than using LUKS) remains, select LUKS by setting 'osd dmcrypt type = luks' Signed-off-by: Andrew Bartlett <abartlet@catalyst.net.nz>
2014-10-30 21:29:36 +00:00
# Map journal if using dm-crypt and luks
ACTION=="add" SUBSYSTEM=="block", \
ENV{DEVTYPE}=="partition", \
ENV{ID_PART_ENTRY_TYPE}=="45b0969e-9b03-4f30-b4c6-35865ceff106", \
RUN+="/sbin/cryptsetup --key-file /etc/ceph/dmcrypt-keys/$env{ID_PART_ENTRY_UUID}.luks.key luksOpen /dev/$name $env{ID_PART_ENTRY_UUID}"
udev: trigger on dmcrypted osd partitions Automatically map encrypted journal partitions. For encrypted OSD partitions, map them, wait for the mapped device to appear, and then ceph-disk-activate. This is much simpler than doing the work in ceph-disk-activate. Signed-off-by: Sage Weil <sage@inktank.com>
2013-02-14 02:22:45 +00:00
# Map data device and
# activate ceph-tagged partitions
Rework ceph-disk to allow LUKS for encrypted partitions LUKS allows for validation of the key at mount time (rather than simply mounting a random partition), specification of the encryption parameters in the header and key rollover of the slot key (the one that needs to be stored). New parameters 'osd cryptsetup parameters' and 'osd dmcrypt key size' are added. These allow these important policy choices to be overridden or kept consistent per-site. The previous default plain mode (rather than using LUKS) remains, select LUKS by setting 'osd dmcrypt type = luks' Signed-off-by: Andrew Bartlett <abartlet@catalyst.net.nz>
2014-10-30 21:29:36 +00:00
# for dm-crypted data devices and plain
udev: trigger on dmcrypted osd partitions Automatically map encrypted journal partitions. For encrypted OSD partitions, map them, wait for the mapped device to appear, and then ceph-disk-activate. This is much simpler than doing the work in ceph-disk-activate. Signed-off-by: Sage Weil <sage@inktank.com>
2013-02-14 02:22:45 +00:00
ACTION=="add" SUBSYSTEM=="block", \
ENV{DEVTYPE}=="partition", \
ENV{ID_PART_ENTRY_TYPE}=="4fbd7e29-9d25-41b8-afd0-5ec00ceff05d", \
RUN+="/sbin/cryptsetup --key-file /etc/ceph/dmcrypt-keys/$env{ID_PART_ENTRY_UUID} --key-size 256 create $env{ID_PART_ENTRY_UUID} /dev/$name", \
Fix: use absolute path with udev Avoids the following: udevd[61613]: failed to execute '/lib/udev/bash' 'bash -c 'while [ ! -e /dev/mapper/.... Signed-off-by: Alexandre Marangone <alexandre.marangone@inktank.com>
2013-04-15 22:57:00 +00:00
RUN+="/bin/bash -c 'while [ ! -e /dev/mapper/$env{ID_PART_ENTRY_UUID} ];do sleep 1; done'", \
remove ceph-disk-{activate,prepare} wrappers These ancient aliases shouldn't be used. We should have removed them immediately way back when, honestly. Signed-off-by: Sage Weil <sage@redhat.com>
2015-07-30 14:00:29 +00:00
RUN+="/usr/sbin/ceph-disk activate /dev/mapper/$env{ID_PART_ENTRY_UUID}"
Rework ceph-disk to allow LUKS for encrypted partitions LUKS allows for validation of the key at mount time (rather than simply mounting a random partition), specification of the encryption parameters in the header and key rollover of the slot key (the one that needs to be stored). New parameters 'osd cryptsetup parameters' and 'osd dmcrypt key size' are added. These allow these important policy choices to be overridden or kept consistent per-site. The previous default plain mode (rather than using LUKS) remains, select LUKS by setting 'osd dmcrypt type = luks' Signed-off-by: Andrew Bartlett <abartlet@catalyst.net.nz>
2014-10-30 21:29:36 +00:00
# Map data device and
# activate ceph-tagged partitions
# for dm-crypted data devices and luks
ACTION=="add" SUBSYSTEM=="block", \
ENV{DEVTYPE}=="partition", \
ENV{ID_PART_ENTRY_TYPE}=="4fbd7e29-9d25-41b8-afd0-35865ceff05d", \
RUN+="/sbin/cryptsetup --key-file /etc/ceph/dmcrypt-keys/$env{ID_PART_ENTRY_UUID}.luks.key luksOpen /dev/$name $env{ID_PART_ENTRY_UUID}", \
RUN+="/bin/bash -c 'while [ ! -e /dev/mapper/$env{ID_PART_ENTRY_UUID} ];do sleep 1; done'", \
remove ceph-disk-{activate,prepare} wrappers These ancient aliases shouldn't be used. We should have removed them immediately way back when, honestly. Signed-off-by: Sage Weil <sage@redhat.com>
2015-07-30 14:00:29 +00:00
RUN+="/usr/sbin/ceph-disk activate /dev/mapper/$env{ID_PART_ENTRY_UUID}"
Reference in New Issue Copy Permalink