From: Alfredo Deza Date: Thu, 17 May 2018 12:44:41 +0000 (-0400) Subject: doc/ceph-volume activate does not need a dmcrypt flag X-Git-Tag: v13.2.1~134^2~4 X-Git-Url: http://git-server-git.apps.pok.os.sepia.ceph.com/?a=commitdiff_plain;h=0e983e82e571c92a53f7d0761872d0ddfca7f589;p=ceph.git doc/ceph-volume activate does not need a dmcrypt flag Signed-off-by: Alfredo Deza (cherry picked from commit ac0c925c576868107e585ba458fbff956467bccb) --- diff --git a/doc/ceph-volume/lvm/activate.rst b/doc/ceph-volume/lvm/activate.rst index 3990a3d53f3..f4a989a4db6 100644 --- a/doc/ceph-volume/lvm/activate.rst +++ b/doc/ceph-volume/lvm/activate.rst @@ -29,6 +29,13 @@ right OSD is being activated. It is entirely possible that a previous OSD with the same id exists and would end up activating the incorrect one. +dmcrypt +^^^^^^^ +If the OSD was prepared with dmcrypt by ceph-volume, there is no need to +specify ``--dmcrypt`` on the command line again (that flag is not available for +the ``activate`` subcommand). An encrypted OSD will be automatically detected. + + Discovery --------- With OSDs previously created by ``ceph-volume``, a *discovery* process is