RepoMirrors/ceph
1
0
Fork 0
mirror of https://github.com/ceph/ceph synced 2025-02-21 01:47:25 +00:00
Code Issues Packages Projects Releases Wiki Activity

doc/ceph-volume update filestore to indicate it is not the only/default objectstore

Browse Source 
Signed-off-by: Alfredo Deza <adeza@redhat.com>
This commit is contained in:
Alfredo Deza 2017-10-20 10:15:09 -04:00
parent 1dc24d1a70
commit c93603e576
1 changed files with 12 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
doc/ceph-volume/lvm/prepare.rst
View File

@ -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 <ceph-volume-lvm-prepare_filestore>`
* ``--bluestore``
.. when available, this will need to be updated to:
.. * :ref:`--bluestore <ceph-volume-prepare_bluestore>`
* :ref:`--bluestore <ceph-volume-lvm-prepare_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::