Hi, The new style "ceph-volume" LVM way of provisioning OSDs introduces a little challange for us. In order to create the OSDs as logical, consistent and easily recognizable as possible, we try to name the Volume Groups (VG) and Logical Volumes (LV) the same as the OSD. For example: OSD no. 12 will be named /dev/osd.12/osd.12. So we don't use: "ceph-volume lvm create /dev/device" but use: "ceph-volume lvm prepare --bluestore --data osd.$OSD_ID/osd.$OSD_ID" and "ceph-volume lvm activate --bluestore $OSD_ID $OSD_FSID" However, this way of provisioning requires to know the OSD_ID before creating the VG/LV. Is there a way to ask Ceph which OSD_ID would be next up? Thanks, Stefan P.s. During the provisioning runs we see that Ceph just increments the OSD_ID. But when replacing an OSD_ID it _might_ re-use an OSD_ID. -- | BIT BV http://www.bit.nl/ Kamer van Koophandel 09090351 | GPG: 0xD14839C6 +31 318 648 688 / info@xxxxxx _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |