Feature #45416
closedAllow running ceph on crypt devices
0%
Description
The python bindings for ceph seem to only return devices of type 'disk'.
In the change here (https://github.com/ceph/ceph/commit/b35e8c485f73b5b65e0be29444eb06172d6df3e3), get_devices (line 696) explicitly filters to only devices named 'disk' (line 714). Is there a reason that ceph doesn't support other device types? Specifically, I'd like to use 'crypt' devices, which are created using luks.
I tried to scan the repo to understand why ceph would limit itself to only 'disk' types, but didn't find anything that stuck out. Similarly, simple testing in which I allowed other types brought up osds that previously hadn't worked.
Is there a reason that ceph only returns 'disk' devices here? Would there be any downside to permitting other types as well? Please let me know.
I apologize if I'm filing this in the wrong place. Please let me know if I should re-route.
Updated by Behram Mistree almost 4 years ago
Sorry for the confusion. I wanted to clarify something:
Similarly, simple testing in which I allowed other types brought up osds that previously hadn't worked.
only seems to work when the additional type was 'linear' for a linear raid array.
Updated by Jan Fajerski almost 4 years ago
- Status changed from New to Duplicate
The reason for not allowing crypt device for the lvm subcommand is that these OSDs can be encrypted too. This creates a crypt device and currently ceph-volume can't tell if a crypt device was created prior or if it is pointed at an OSDs crypt device.
See https://tracker.ceph.com/issues/44911 for more discussion and a path forward.