document missing support for non-containerized deployment

Signed-off-by: Kai Wembacher <kai@ktwe.de>
pull/3466/head
Kai Wembacher 2018-12-21 00:35:53 +01:00 committed by mergify[bot]
parent 561746f75e
commit 1dd26f76bf
2 changed files with 6 additions and 6 deletions

View File

@ -123,9 +123,9 @@ dummy:
# - The devices listed in 'devices' will get 2 partitions, one for 'block' and one for 'data'. # - The devices listed in 'devices' will get 2 partitions, one for 'block' and one for 'data'.
# 'data' is only 100MB big and do not store any of your data, it's just a bunch of Ceph metadata. # 'data' is only 100MB big and do not store any of your data, it's just a bunch of Ceph metadata.
# 'block' will store all your actual data. # 'block' will store all your actual data.
# - The devices in 'dedicated_devices' will get one partition for RocksDB DB, called 'block.db' # - The devices in 'dedicated_devices' will get 1 partition for RocksDB DB, called 'block.db'
# and one for RocksDB WAL, called 'block.wal'. To use a single partition for RocksDB and WAL together # and one for RocksDB WAL, called 'block.wal'. To use a single partition for RocksDB and WAL together
# set bluestore_wal_devices to []. # set bluestore_wal_devices to [] (supported only for non-containerized deployment).
# #
# By default dedicated_devices will represent block.db # By default dedicated_devices will represent block.db
# #
@ -149,7 +149,7 @@ dummy:
# By default, if 'bluestore_wal_devices' is empty, it will get the content of 'dedicated_devices'. # By default, if 'bluestore_wal_devices' is empty, it will get the content of 'dedicated_devices'.
# If set, then you will have a dedicated partition on a specific device for block.wal. # If set, then you will have a dedicated partition on a specific device for block.wal.
# #
# Set bluestore_wal_devices: [] to use the same partition for RocksDB and WAL. # Set bluestore_wal_devices: [] to use the same partition for RocksDB and WAL (supported only for non-containerized deployment).
# #
# Example of what you will get: # Example of what you will get:
# [root@ceph-osd0 ~]# blkid /dev/sd* # [root@ceph-osd0 ~]# blkid /dev/sd*

View File

@ -115,9 +115,9 @@ valid_osd_scenarios:
# - The devices listed in 'devices' will get 2 partitions, one for 'block' and one for 'data'. # - The devices listed in 'devices' will get 2 partitions, one for 'block' and one for 'data'.
# 'data' is only 100MB big and do not store any of your data, it's just a bunch of Ceph metadata. # 'data' is only 100MB big and do not store any of your data, it's just a bunch of Ceph metadata.
# 'block' will store all your actual data. # 'block' will store all your actual data.
# - The devices in 'dedicated_devices' will get one partition for RocksDB DB, called 'block.db' # - The devices in 'dedicated_devices' will get 1 partition for RocksDB DB, called 'block.db'
# and one for RocksDB WAL, called 'block.wal'. To use a single partition for RocksDB and WAL together # and one for RocksDB WAL, called 'block.wal'. To use a single partition for RocksDB and WAL together
# set bluestore_wal_devices to []. # set bluestore_wal_devices to [] (supported only for non-containerized deployment).
# #
# By default dedicated_devices will represent block.db # By default dedicated_devices will represent block.db
# #
@ -141,7 +141,7 @@ dedicated_devices: []
# By default, if 'bluestore_wal_devices' is empty, it will get the content of 'dedicated_devices'. # By default, if 'bluestore_wal_devices' is empty, it will get the content of 'dedicated_devices'.
# If set, then you will have a dedicated partition on a specific device for block.wal. # If set, then you will have a dedicated partition on a specific device for block.wal.
# #
# Set bluestore_wal_devices: [] to use the same partition for RocksDB and WAL. # Set bluestore_wal_devices: [] to use the same partition for RocksDB and WAL (supported only for non-containerized deployment).
# #
# Example of what you will get: # Example of what you will get:
# [root@ceph-osd0 ~]# blkid /dev/sd* # [root@ceph-osd0 ~]# blkid /dev/sd*