From: Alfredo Deza Date: Thu, 17 May 2018 12:45:26 +0000 (-0400) Subject: doc/ceph-volume prepapre accepts a --dmcrypt flag X-Git-Tag: v12.2.6~33^2~3 X-Git-Url: http://git-server-git.apps.pok.os.sepia.ceph.com/?a=commitdiff_plain;h=64414217a473884c260ae3771d5a101b0a3a2f44;p=ceph.git doc/ceph-volume prepapre accepts a --dmcrypt flag Signed-off-by: Alfredo Deza (cherry picked from commit e97d0717d323a08a46aa997c63d2416da7e4941f) --- diff --git a/doc/ceph-volume/lvm/prepare.rst b/doc/ceph-volume/lvm/prepare.rst index de29a782a10..700d1216a55 100644 --- 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 prepare --filestore --data data --journal journal +For enabling :ref:`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 @@ -148,6 +152,9 @@ A raw device can be specified in the same way:: ceph-volume lvm prepare --bluestore --data /path/to/device +For enabling :ref:`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``