On Tue, Jun 19, 2018 at 7:58 PM, Gregory Farnum <gfarnum@xxxxxxxxxx> wrote: > On Tue, Jun 19, 2018 at 12:35 PM Alfredo Deza <adeza@xxxxxxxxxx> wrote: >> >> One of the top questions for ceph-volume has been "why this doesn't create >> partitions like ceph-disk does?". Although we have initially focused on LVM, >> the same question is true (except for LVs instead of partitions). Now >> that ceph-volume is >> stabilizing, we can expand on a more user-friendly approach. >> >> We are planning on creating an interface to size devices automatically based on >> some simple criteria. There are three distinct use cases that we are going to >> support, that should allow easy OSD provisioning with defaults, to more >> esoteric use cases with third-party systems (like rook, ceph-ansible, seasalt, >> etc...) >> >> This is being implemented as a separate sub-command to avoid pilling up the >> complexity on the existing `lvm` one, and reflect the automation behind it. >> >> Here are some examples on how the API is being designed, for fully automatic >> configuration, semi-automatic (allows input), and manual via a config >> management system: >> >> Automatic (no configuration or options required): >> ------------------------------------------------- >> >> Single device type: >> >> $ ceph-volume auto >> Use --yes to run >> Detected devices: >> [rotational] /dev/sda 1TB >> [rotational] /dev/sdb 1TB >> [rotational] /dev/sdc 1TB >> >> Expected Bluestore OSDs: >> >> data: /dev/sda (100%) >> data: /dev/sdb (100%) >> data: /dev/sdc (100%) >> >> This scenario will detect a single type of unused device (rotational) >> so the bluestore >> OSD will be created on each without block.db or block.wal >> >> In the case above (single device type) where you only specify rotational drives, where does the block.db and block.wal get created if there are no SSDs available - on the same disk as the data? -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
