Re: Can ceph-volume manage the LVs optionally used for DB / WAL at all?

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


On 11.08.23 16:06, Eugen Block wrote:
if you deploy OSDs from scratch you don't have to create LVs manually, that is handled entirely by ceph-volume (for example on cephadm based clusters you only provide a drivegroup definition).

By looking at it seems that ceph-volume wants an LV or partition. So it's apparently not just taking a VG itself? Also if there were multiple VGs / devices , I likely would need to at least pick those.

But I suppose this orchestration would then require cephadm ( and cannot be done via ceph-volume which merely takes care of ONE OSD at a time.

I'm not sure if automating db/wal migration has been considered, it might be (too) difficult. But moving the db/wal devices to new/different devices doesn't seem to be a reoccuring issue (corner case?), so maybe having control over that process for each OSD individually is the safe(r) option in case something goes wrong.

Sorry for the confusion. I was not talking about any migrations, just the initial creation of spinning rust OSDs with DB or WAL on fast storage.


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