From c90e473ff35d15d309eb92dbdc6b9df2e8bd5ecc Mon Sep 17 00:00:00 2001 From: Alfredo Deza Date: Fri, 20 Oct 2017 10:15:09 -0400 Subject: [PATCH] doc/ceph-volume update filestore to indicate it is not the only/default objectstore Signed-off-by: Alfredo Deza (cherry picked from commit c93603e5764e021305cfeb1c297ee16318126fe1) --- doc/ceph-volume/lvm/prepare.rst | 25 ++++++++++++------------- 1 file changed, 12 insertions(+), 13 deletions(-) diff --git a/doc/ceph-volume/lvm/prepare.rst b/doc/ceph-volume/lvm/prepare.rst index add0f185d8646..0ed652f304dee 100644 --- a/doc/ceph-volume/lvm/prepare.rst +++ b/doc/ceph-volume/lvm/prepare.rst @@ -2,10 +2,11 @@ ``prepare`` =========== -This subcommand allows a :term:`filestore` setup (:term:`bluestore` support is -planned) and currently consumes only logical volumes for both the data and -journal. It will not create or modify the logical volumes except for adding -extra metadata. +This subcommand allows a :term:`filestore` or :term:`bluestore` setup. It is +recommended to pre-provision a logical volume before using it with +``ceph-volume lvm``. + +Logical volumes are not altered except for adding extra metadata. .. note:: This is part of a two step process to deploy an OSD. If looking for a single-call way, please see :ref:`ceph-volume-lvm-create` @@ -23,21 +24,19 @@ the back end can be specified with: * :ref:`--filestore ` -* ``--bluestore`` - -.. when available, this will need to be updated to: -.. * :ref:`--bluestore ` +* :ref:`--bluestore ` .. _ceph-volume-lvm-prepare_filestore: ``filestore`` ------------- -This is the default OSD backend and allows preparation of logical volumes for -a :term:`filestore` OSD. +This is the OSD backend that allows preparation of logical volumes for +a :term:`filestore` objectstore OSD. -The process is *very* strict, it requires two logical volumes that are ready to -be used. No special preparation is needed for these volumes other than -following the minimum size requirements for data and journal. +The process is *very* strict, it requires an existing logical volume for the +OSD data and a partitioned physical device or logical volume for the journal. +No special preparation is needed for these volumes other than following the +minimum size requirements for data and journal. The API call looks like:: -- 2.39.5