doc/ceph-volume prepapre accepts a --dmcrypt flag

Signed-off-by: Alfredo Deza <adeza@redhat.com>
(cherry picked from commit e97d0717d323a08a46aa997c63d2416da7e4941f)

diff --git a/doc/ceph-volume/lvm/prepare.rst b/doc/ceph-volume/lvm/prepare.rst
index f59215a75b3360223a0f364f746cfc60f6289e95..c2e38ec52a10c1d54ab68101e226d91ae645f276 100644 (file)
--- a/doc/ceph-volume/lvm/prepare.rst
+++ b/doc/ceph-volume/lvm/prepare.rst
@@ -42,6 +42,10 @@ The API call looks like::
 
     ceph-volume lvm prepare --filestore --data volume_group/lv_name --journal journal
 
+For enabling :ref:`encryption <ceph-volume-lvm-encryption>`, the ``--dmcrypt`` flag is required::
+
+    ceph-volume lvm prepare --filestore --dmcrypt --data volume_group/lv_name --journal journal
+
 There is flexibility to use a raw device or partition as well for ``--data``
 that will be converted to a logical volume. This is not ideal in all situations
 since ``ceph-volume`` is just going to create a unique volume group and
@@ -188,6 +192,9 @@ A raw device can be specified in the same way::
 
     ceph-volume lvm prepare --bluestore --data /path/to/device
 
+For enabling :ref:`encryption <ceph-volume-lvm-encryption>`, the ``--dmcrypt`` flag is required::
+
+    ceph-volume lvm prepare --bluestore --dmcrypt --data vg/lv
 
 If a ``block.db`` or a ``block.wal`` is needed (they are optional for
 bluestore) they can be specified with ``--block.db`` and ``--block.wal``