Feature #44911
closedsupport dmcrypt device that is already encrypted by user
0%
Description
I need to create OSDs on top of dmcrypt HDDs. Although ceph-volume provides
a way to encrypt by itself, it does not match my use-case. It's because I make
use of TPM to encrypt HDDs1 and ceph-volume doesn't support any options
to tweak the encryption method.
I consider it's better to allow the dmcrypt disks, that are encrypted by users,
instead of complicating ceph-volume to support many encryption methods
one by one.
Updated by Banji Inoue about 4 years ago
Hi, how is this issue going?
I am related to this issue and this PR(https://github.com/ceph/ceph/pull/34375).
I would be happy if I could know the situation of this issue.
Thanks,
Updated by Satoru Takeuchi almost 4 years ago
As a result of the discussion in the following PR, I found this issue should be closed
since raw mode OSD can be created in crypt type device.
https://github.com/ceph/ceph/pull/34375
So, please close this ticket.
We should still fix `ceph-volume inventory` to judge crypt device is regarded
as available. This problem is tracked by the following another issue.
Updated by Jan Fajerski over 3 years ago
- Related to Bug #45443: ceph-volume: support mode-specific availability fields in inventory subcommand added