openstack
/
charm-ceph-osd
Code Issues Proposed changes

Extending a Bluestore config options with examples 

This proposal is about adding some usage instructions and
examples for future charm users.

Change-Id: If6698e37e32fc2b526d546cb046a7c8091f66634
This commit is contained in:
Vladimir Grevtsev 2018-11-16 22:16:12 +03:00
parent 17c64df681
commit e35ee0399b
1 changed files with 18 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
config.yaml
View File

@ -97,16 +97,28 @@ options:
type: int
default: 0
description: |
Size of a partition or file to use for BlueStore WAL (RocksDB WAL)
A default value is not set as it is calculated by ceph-disk if
not specified.
Size (in bytes) of a partition, file or LV to use for
BlueStore WAL (RocksDB WAL), provided on a per backend device basis.
.
Example: 128 GB device, 8 data devices provided in "osd-devices"
gives 128 / 8 GB = 16 GB = 16000000000 bytes per device.
.
A default value is not set as it is calculated by ceph-disk (before Luminous)
or the charm itself, when ceph-volume is used (Luminous and above).
bluestore-block-db-size:
type: int
default: 0
description: |
Size of a partition or file to use for BlueStore metadata
or RocksDB SSTs. A default value is not set as it is calculated
by ceph-disk if not specified.
Size (in bytes) of a partition, file or LV to use for BlueStore
metadata or RocksDB SSTs, provided on a per backend device basis.
.
Example: 128 GB device, 8 data devices provided in "osd-devices"
gives 128 / 8 GB = 16 GB = 16000000000 bytes per device.
.
A default value is not set as it is calculated by ceph-disk (before Luminous)
or the charm itself, when ceph-volume is used (Luminous and above).
osd-format:
type: string
default: xfs