#bluestore_wal_devices: "{{ dedicated_devices }}"
# III. Use ceph-volume to create OSDs from logical volumes.
-# Use 'osd_scenario: lvm' to enable this scenario. Currently we only support dedicated journals
+# Use 'osd_scenario: lvm' to enable this scenario.
# when using lvm, not collocated journals.
-# lvm_volumes is a list of dictionaries. 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. You can not use the same journal for many data lvs.
+# lvm_volumes is a list of dictionaries.
+#
+# 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.
+# You can not use the same journal for many data lvs.
# data_vg must be the volume group name of the data lv
-# journal_vg is optional and must be the volume group name of the journal lv, if applicable
+# journal_vg is optional and must be the volume group name of the journal lv, if applicable.
# For example:
# lvm_volumes:
# - data: data-lv1
# - data: data-lv3
# journal: /dev/sdb1
# data_vg: vg2
+#
+# 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).
+# This allows for four combinations: just data, data and wal, data and wal and
+# db, data and db.
+# For example:
+# lvm_volumes:
+# - data: data-lv1
+# data_vg: vg1
+# wal: wal-lv1
+# wal_vg: vg1
+# - data: data-lv2
+# db: db-lv2
+# db_vg: vg2
+# - data: data-lv3
+# wal: wal-lv1
+# wal_vg: vg3
+# db: db-lv3
+# db_vg: vg3
+# - data: data-lv4
+# data_vg: vg4
+
#lvm_volumes: []