docs for creating encrypted OSDs with the lvm scenario

Signed-off-by: Andrew Schoen <aschoen@redhat.com>

diff --git a/docs/source/osds/scenarios.rst b/docs/source/osds/scenarios.rst
index b3cd1994dc9b6b2b3a8e502ade7ff8f242b5d046..f77f5bfa479786b652b0cfb394395be878a55a0e 100644 (file)
--- a/docs/source/osds/scenarios.rst
+++ b/docs/source/osds/scenarios.rst
@@ -176,6 +176,9 @@ mappings for devices to be deployed. It is a list of dictionaries which expects
 a volume name and a volume group for logical volumes, but can also accept
 a partition in the case of ``filestore`` for the ``journal``.
 
+This scenario supports encrypting your OSDs by setting ``dmcrypt: True``. If set,
+all OSDs defined in ``lvm_volumes`` will be encrypted.
+
 The ``data`` key represents the logical volume name, raw device or partition that is to be used for your
 OSD data.  The ``data_vg`` key represents the volume group name that your
 ``data`` logical volume resides on. This key is required for purging of OSDs
@@ -231,6 +234,18 @@ For example, a configuration to use the ``lvm`` osd scenario would look like::
         journal: journal-lv1
         journal_vg: vg2
 
+For example, a configuration to use the ``lvm`` osd scenario with encryption would look like::
+
+    osd_objectstore: filestore
+    osd_scenario: lvm
+    dmcrypt: True
+    lvm_volumes:
+      - data: data-lv1
+        data_vg: vg1
+        journal: journal-lv1
+        journal_vg: vg2
+        crush_device_class: foo
+
 
 ``bluestore``
 ^^^^^^^^^^^^^