> If you want to specify vgname/lvname you have to create them manually and run: > > ceph-volume lvm create --data /dev/sdc --block.db vgname/db-sdc --block.wal vgname/wal-sdc Apt helpfully told me I need to install ceph-osd, which I did. The ceph-volume command then told me : Running command: /usr/bin/ceph-authtool --gen-print-key Running command: /usr/bin/ceph --cluster ceph --name client.bootstrap-osd --keyring /var/lib/ceph/bootstrap-osd/ceph.keyring -i - osd new ... stderr: [errno 13] RADOS permission denied (error connecting to the cluster) --> RuntimeError: Unable to create a new OSD id I note the keyring file doesn’t exist - is this something I need to create or should exist already? Or will it be created by this command? > ceph-volume lvm batch /dev/sdb ... /dev/sdj --db-devices /dev/sdk --wal-devices /dev/sdl > but then you don't get to choose vgname/lvname, the batch command creates the volume groups and logical volumes for you. I’m not too fussed about the vg/lv names if they’re created for me. Can the db and Wal devices be the same device? > I would say the drive_groups approach is designed to automate things so you don't need to worry about creating VGs and LVs. Again, can WAL and DB be pointed at the same SSD? Sorry if I’m being stupid, the documentation just seems a little lacking. Will _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |