From: Neha Ojha Date: Tue, 7 Aug 2018 20:08:38 +0000 (+0000) Subject: infrastructure-playbooks/vars/lv_vars.yaml: minor fixes X-Git-Tag: v3.2.0beta2~52 X-Git-Url: http://git-server-git.apps.pok.os.sepia.ceph.com/?a=commitdiff_plain;h=909b38da829485b2ec56b61bf2b2fa0df02b0ed4;p=ceph-ansible.git infrastructure-playbooks/vars/lv_vars.yaml: minor fixes Signed-off-by: Neha Ojha --- diff --git a/infrastructure-playbooks/vars/lv_vars.yaml b/infrastructure-playbooks/vars/lv_vars.yaml index 5e597d075..52d9e3b67 100644 --- a/infrastructure-playbooks/vars/lv_vars.yaml +++ b/infrastructure-playbooks/vars/lv_vars.yaml @@ -1,11 +1,11 @@ # This file configures logical volume creation for FS Journals on NVMe, a NVMe based bucket index, and HDD based OSDs. # This playbook configures one NVMe device at a time. If your OSD systems contain multiple NVMe devices, you will need to edit the key variables ("nvme_device", "hdd_devices") for each run. -# It is meant to be used when osd_objectstore=filestore and it outputs the the necessary input for group_vars/osds.yml when configured with osd_scenario=lvm -# The LVs for journals are created first then the LVs for data. All LVs for journals correspond to a LV for data +# It is meant to be used when osd_objectstore=filestore and it outputs the necessary input for group_vars/osds.yml when configured with osd_scenario=lvm. +# 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 ## -# Path of nvme device primed for LV creation for journals and data. Only one NVMe device is allowed at a time. +# 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 # Path of hdd devices designated for LV creation.