From 98b5330b1a170547e7b166da5a489872cfc7e352 Mon Sep 17 00:00:00 2001 From: Zac Dover Date: Fri, 28 Oct 2022 12:42:00 +1000 Subject: [PATCH] doc/ceph-volume: add A. D'Atri's suggestions Add Anthony D'Atri's notes on doc/ceph-volume/lvm/prepare.rst as expressed in https://github.com/ceph/ceph/pull/48634. Signed-off-by: Zac Dover --- doc/ceph-volume/lvm/prepare.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/ceph-volume/lvm/prepare.rst b/doc/ceph-volume/lvm/prepare.rst index 889de6dafb1..e5190a288c9 100644 --- a/doc/ceph-volume/lvm/prepare.rst +++ b/doc/ceph-volume/lvm/prepare.rst @@ -28,7 +28,7 @@ the backend, which can be done by using the following flags and arguments: ``bluestore`` ------------- -:term:`Bluestore` is the default object store for new OSDs. It +:term:`Bluestore` is the default backend for new OSDs. It offers more flexibility for devices than :term:`filestore` does. Bluestore supports the following configurations: @@ -37,13 +37,13 @@ supports the following configurations: * a block device and a block.db device * a single block device -The bluestore subcommand accepts physical block devices, partitions on physical +The ``bluestore`` subcommand accepts physical block devices, partitions on physical block devices, or logical volumes as arguments for the various device parameters. If a physical block device is provided, a logical volume will be created. If the provided volume group's name begins with `ceph`, it will be created if it does not yet exist and it will be clobbered and reused if it already exists. This allows for a simpler approach to using LVM but at the -cost of flexibility: no options or configurations can be used to change how the +cost of flexibility: no option or configuration can be used to change how the logical volume is created. The ``block`` is specified with the ``--data`` flag, and in its simplest use -- 2.39.5