Hi,
1) I am mostly asking about an non-cephadm environment and would
just like to know if ceph-volume can also manage the VG of a DB/WAL
device that is used for multiple OSD and create the individual LVs
which are used for DB or WAL devices when creating a single OSD.
Below you give an
On 25.08.23 09:09, Eugen Block wrote:
I'm still not sure if we're on the same page.
Maybe not, I'll respond inline to clarify.
By looking at
https://docs.ceph.com/en/latest/man/8/ceph-volume/#cmdoption-ceph-volume-lvm-prepare-block.db
it seems that ceph-volume wants an LV or partition.
Hi,
I'm still not sure if we're on the same page.
By looking at
https://docs.ceph.com/en/latest/man/8/ceph-volume/#cmdoption-ceph-volume-lvm-prepare-block.db 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 /
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
Hi,
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). I'm not sure if
automating db/wal migration has been considered, it might be (too)
