Hi,
response inline...
Zitat von Alan Murrell <Alan@xxxxxxxx>:
I strongly recommend to let cephadm handle the entire process of
OSD creation, just ensure you have a fitting spec file. Don't
prepare any LVs manually beforehand, except for such a case as
right now where you want to move DBs out of the main device.
So if I create a spec file so Ceph automatically puts the DBs of the
rotational devices onto a specified SSD (whether I do it by size,
vendor, model, or all three), Ceph will crate the necessary LVs on
the SSD automatically? How does it determine the size to use (or
would that also get specified in the spec file)?
Yes, Ceph creates VGs/LVs automatically if there's enough free space.
You can also specify the db/wal sizes in your spec file.
What if I have an SSD with he LVs already created? I assume Ceph
wouldn't see that as a valid device for the DB/WAL?
I haven't tested each possible scenario in detail, but in general,
cephadm can re-use freed up space of the SSD, for example after HDD
replacement which also requires to zap the respective block.db LV. I'm
not familiar which filters ceph-volume uses to determine if it can use
the existing SSD.
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
