124 lines
4.3 KiB
YAML
124 lines
4.3 KiB
YAML
options:
|
|
osd-devices:
|
|
type: string
|
|
default: /dev/vdb
|
|
description: |
|
|
The devices to format and set up as osd volumes.
|
|
.
|
|
These devices are the range of devices that will be checked for and
|
|
used across all service units.
|
|
.
|
|
For ceph >= 0.56.6 these can also be directories instead of devices - the
|
|
charm assumes anything not starting with /dev is a directory instead.
|
|
osd-journal:
|
|
type: string
|
|
default:
|
|
description: |
|
|
The device to use as a shared journal drive for all OSD's. By default
|
|
no journal device will be used.
|
|
.
|
|
Only supported with ceph >= 0.48.3.
|
|
osd-journal-size:
|
|
type: int
|
|
default: 1024
|
|
description: |
|
|
Ceph osd journal size. The journal size should be at least twice the
|
|
product of the expected drive speed multiplied by filestore max sync
|
|
interval. However, the most common practice is to partition the journal
|
|
drive (often an SSD), and mount it such that Ceph uses the entire
|
|
partition for the journal.
|
|
.
|
|
Only supported with ceph >= 0.48.3.
|
|
osd-format:
|
|
type: string
|
|
default: xfs
|
|
description: |
|
|
Format of filesystem to use for OSD devices; supported formats include:
|
|
.
|
|
xfs (Default >= 0.48.3)
|
|
ext4 (Only option < 0.48.3)
|
|
btrfs (experimental and not recommended)
|
|
.
|
|
Only supported with ceph >= 0.48.3.
|
|
osd-reformat:
|
|
type: string
|
|
default:
|
|
description: |
|
|
By default, the charm will not re-format a device that already looks
|
|
as if it might be an OSD device. This is a safeguard to try to
|
|
prevent data loss.
|
|
.
|
|
Specifying this option (any value) forces a reformat of any OSD devices
|
|
found which are not already mounted.
|
|
ignore-device-errors:
|
|
type: boolean
|
|
default: False
|
|
description: |
|
|
By default, the charm will raise errors if a whitelisted device is found,
|
|
but for some reason the charm is unable to initialize the device for use
|
|
by Ceph.
|
|
.
|
|
Setting this option to 'True' will result in the charm classifying such
|
|
problems as warnings only and will not result in a hook error.
|
|
ephemeral-unmount:
|
|
type: string
|
|
default:
|
|
description: |
|
|
Cloud instances provider ephermeral storage which is normally mounted
|
|
on /mnt.
|
|
.
|
|
Providing this option will force an unmount of the ephemeral device
|
|
so that it can be used as a OSD storage device. This is useful for
|
|
testing purposes (cloud deployment is not a typical use case).
|
|
source:
|
|
type: string
|
|
default: cloud:precise-updates/folsom
|
|
description: |
|
|
Optional configuration to support use of additional sources such as:
|
|
.
|
|
- ppa:myteam/ppa
|
|
- cloud:precise-proposed/folsom
|
|
- http://my.archive.com/ubuntu main
|
|
.
|
|
The last option should be used in conjunction with the key configuration
|
|
option.
|
|
.
|
|
Note that a minimum ceph version of 0.48.2 is required for use with this
|
|
charm which is NOT provided by the packages in the main Ubuntu archive
|
|
for precise but is provided in the Ubuntu cloud archive.
|
|
key:
|
|
type: string
|
|
default:
|
|
description: |
|
|
Key ID to import to the apt keyring to support use with arbitary source
|
|
configuration from outside of Launchpad archives or PPA's.
|
|
use-syslog:
|
|
type: boolean
|
|
default: False
|
|
description: |
|
|
If set to True, supporting services will log to syslog.
|
|
ceph-public-network:
|
|
type: string
|
|
default:
|
|
description: |
|
|
The IP address and netmask of the public (front-side) network (e.g.,
|
|
192.168.0.0/24)
|
|
ceph-cluster-network:
|
|
type: string
|
|
default:
|
|
description: |
|
|
The IP address and netmask of the cluster (back-side) network (e.g.,
|
|
192.168.0.0/24)
|
|
prefer-ipv6:
|
|
type: boolean
|
|
default: False
|
|
description: |
|
|
If True enables IPv6 support. The charm will expect network interfaces
|
|
to be configured with an IPv6 address. If set to False (default) IPv4
|
|
is expected.
|
|
.
|
|
NOTE: these charms do not currently support IPv6 privacy extension. In
|
|
order for this charm to function correctly, the privacy extension must be
|
|
disabled and a non-temporary address must be configured/available on
|
|
your network interface.
|