ceph-volume / ecnrypted OSD issues with functionalities

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello,

I have made some tests with creating OSDs and I have found out that there
are big issues with the ceph-volume functionality.

1) If using dmcrypt and separate data and db block devices, ceph-volume
creates cryprodevs/PVs/VGs/LVs  for both devices. This might seem as
normal, until one considers the possibility that a single SSD will support
multiple OSDs and the whole concept of being able to resize bluestore DB
partitions gets very complicated like this; I can have a full SSD
encrypted, create a PV/VG on top and provide the LVs myself without an
extra layer of encryption.

2) If I try to circumvent this limitation by asking ceph-volume to use
already encrypted devices for both the data and the bluestore db, the OSDs
are not auto scanned at startup, ceph-volume simple scan complaints that
they are not real devices and nothing starts.

  Am I missing something?
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx



[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Ceph Dev]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux