update group_vars/osds.yml.sample for the new lvm_volumes examples

Signed-off-by: Andrew Schoen <aschoen@redhat.com>
pull/2172/head
Andrew Schoen 2017-11-14 13:19:03 -06:00
parent 3c604f1115
commit 6dc090a4c8
1 changed files with 9 additions and 3 deletions

View File

@ -203,9 +203,9 @@ dummy:
#
# Filestore: Each dictionary must contain a data, journal and vg_name key. Any
# logical volume or logical group used must be a name and not a path. data
# must be a logical volume. journal can be either a lv, device or partition.
# can be a logical volume, device or partition. journal can be either a lv or partition.
# You can not use the same journal for many data lvs.
# data_vg must be the volume group name of the data lv
# data_vg must be the volume group name of the data lv, only applicable when data is an lv.
# journal_vg is optional and must be the volume group name of the journal lv, if applicable.
# For example:
# lvm_volumes:
@ -214,11 +214,15 @@ dummy:
# journal: journal-lv1
# journal_vg: vg2
# - data: data-lv2
# journal: /dev/sda
# journal: /dev/sda1
# data_vg: vg1
# - data: data-lv3
# journal: /dev/sdb1
# data_vg: vg2
# - data: /dev/sda
# journal: /dev/sdb1
# - data: /dev/sda1
# journal: /dev/sdb1
#
# Bluestore: Each dictionary must contain at least data. When defining wal or
# db, it must have both the lv name and vg group (db and wal are not required).
@ -240,6 +244,8 @@ dummy:
# db_vg: vg3
# - data: data-lv4
# data_vg: vg4
# - data: /dev/sda
# - data: /dev/sdb1
#lvm_volumes: []