infrastructure-playbooks: add comments for lv_vars.yml

Add comments telling user that devices used in
playbooks must not have GPT/FS/RAID signatures

Signed-off-by: Ali Maredia <amaredia@redhat.com>
pull/3075/merge
Ali Maredia 2018-08-29 15:44:55 -04:00 committed by mergify[bot]
parent 77eb459a88
commit 561ec9203d
1 changed files with 6 additions and 0 deletions

View File

@ -4,6 +4,12 @@
# The LVs for journals are created first then the LVs for data. All LVs for journals correspond to a LV for data. # The LVs for journals are created first then the LVs for data. All LVs for journals correspond to a LV for data.
# #
## CHANGE THESE VARS ## ## CHANGE THESE VARS ##
#
# The NVMe device and the hdd devices must be raw and not have any GPT, FS, or RAID signatures.
# GPT, FS, & RAID signatures should be removed from a device prior to running the lv-create.yml playbook.
#
# Having leftover signatures can result in ansible errors that say "device $device_name excluded by a filter" after running the lv-create.yml playbook.
# This can be done by running `wipefs -a $device_name`.
# Path of nvme device primed for LV creation for journals and data. Only one NVMe device is allowed at a time. Providing a list will not work in this case. # Path of nvme device primed for LV creation for journals and data. Only one NVMe device is allowed at a time. Providing a list will not work in this case.
nvme_device: /dev/nvme0n1 nvme_device: /dev/nvme0n1