ceph
/
ceph-ansible
mirror of https://github.com/ceph/ceph-ansible.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

docs for creating encrypted OSDs with the lvm scenario 

Signed-off-by: Andrew Schoen <aschoen@redhat.com>
pull/2351/head
Andrew Schoen 2018-01-22 10:53:40 -06:00 committed by Guillaume Abrioux
parent 79473badfe
commit 21931c544c
1 changed files with 15 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
docs/source/osds/scenarios.rst
View File

@ -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``
^^^^^^^^^^^^^