From: Alfredo Deza Date: Tue, 28 Aug 2018 20:22:20 +0000 (-0700) Subject: doc/ceph-volume uncomment section of newly supported batch operations X-Git-Tag: v13.2.2~65^2~2 X-Git-Url: http://git-server-git.apps.pok.os.sepia.ceph.com/?a=commitdiff_plain;h=45719e200f61c3a71b313163d7c623b75effa700;p=ceph.git doc/ceph-volume uncomment section of newly supported batch operations Signed-off-by: Alfredo Deza (cherry picked from commit 02652343c8501a144c5ae2c012f335e8d0f236cf) --- diff --git a/doc/ceph-volume/lvm/batch.rst b/doc/ceph-volume/lvm/batch.rst index 18f465f423897..f6c1005735d03 100644 --- a/doc/ceph-volume/lvm/batch.rst +++ b/doc/ceph-volume/lvm/batch.rst @@ -13,11 +13,10 @@ devices in an efficient way? The process is similar to :ref:`ceph-volume-lvm-create`, and will do the preparation and activation at once, following the same workflow for each OSD. -.. - All the features that ``ceph-volume lvm create`` supports, like ``dmcrypt``, - avoiding ``systemd`` units from starting, defining bluestore or filestore, - are supported. Any fine-grained option that may affect a single OSD is not - supported, for example: specifying where journals should be placed. +All the features that ``ceph-volume lvm create`` supports, like ``dmcrypt``, +avoiding ``systemd`` units from starting, defining bluestore or filestore, +are supported. Any fine-grained option that may affect a single OSD is not +supported, for example: specifying where journals should be placed. .. _ceph-volume-lvm-batch_bluestore: