Ceph is a distributed storage and network file system designed to provide
excellent performance, reliability, and scalability.
This charm provides the Ceph OSD personality for expanding storage capacity
within a ceph deployment.


Ceph is a distributed storage and network file system designed to provide
excellent performance, reliability, and scalability.

This charm deploys additional Ceph OSD storage service units and should be
used in conjunction with the 'ceph' charm to scale out the amount of storage
available in a Ceph cluster.


The charm also supports specification of the storage devices to use in the ceph

    A list of devices that the charm will attempt to detect, initialise and
    activate as ceph storage.

    This this can be a superset of the actual storage devices presented to
    each service unit and can be changed post ceph-osd deployment using
    `juju set`.

For example::

    osd-devices: /dev/vdb /dev/vdc /dev/vdd /dev/vde

Boot things up by using::

juju deploy -n 3 --config ceph.yaml ceph

You can then deploy this charm by simple doing::

juju deploy -n 10 --config ceph.yaml ceph-osd
juju add-relation ceph-osd ceph

Once the ceph charm has bootstrapped the cluster, it will notify the ceph-osd
charm which will scan for the configured storage devices and add them to the
pool of available storage.

Network Space support

This charm supports the use of Juju Network Spaces, allowing the charm to be bound to network space configurations managed directly by Juju. This is only supported with Juju 2.0 and above.

Network traffic can be bound to specific network spaces using the public (front-side) and cluster (back-side) bindings:

juju deploy ceph-osd --bind "public=data-space cluster=cluster-space"

alternatively these can also be provided as part of a Juju native bundle configuration:

  charm: cs:xenial/ceph-osd
  num_units: 1
    public: data-space
    cluster: cluster-space

Please refer to the Ceph Network Reference for details on how using these options effects network traffic within a Ceph deployment.

NOTE: Spaces must be configured in the underlying provider prior to attempting to use them.

NOTE: Existing deployments using ceph-*-network configuration options will continue to function; these options are preferred over any network space binding provided if set.

Contact Information

Author: James Page james.page@ubuntu.com
Report bugs at: http://bugs.launchpad.net/charms/+source/ceph-osd/+filebug
Location: http://jujucharms.com/charms/ceph-osd


                            Apply system hardening. Supports a space-delimited list of modules
to run. Supported modules currently include os, ssh, apache and mysql.

                            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.

                            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.

                            YAML-formatted associative array of sysctl key/value pairs to be set
persistently. By default we set pid_max, max_map_count and
threads-max to a high value to avoid problems with large numbers (>20)
of OSDs recovering. very large clusters should set those values even
higher (e.g. max for kernel.pid_max is 4194303).

{ kernel.pid_max : 2097152, vm.max_map_count : 524288, kernel.threads-max: 2097152 }
                            A comma-separated list of nagios servicegroups.
If left empty, the nagios_context will be used as the servicegroup

                            OSD debug level. Max is 20.
                            Used by the nrpe-external-master subordinate charm.
A string that will be prepended to instance name to set the host name
in nagios. So for instance the hostname would be something like:
If you're running multiple environments with the same services in them
this allows you to differentiate between them.

                            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.

                            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.

                            The IP address and netmask of the public (front-side) network (e.g.,
If multiple networks are to be used, a space-delimited list of a.b.c.d/x
can be provided.

                            Optional configuration to support use of additional sources such as:

  - ppa:myteam/ppa
  - cloud:trusty-proposed/kilo
  - http://my.archive.com/ubuntu main

The last option should be used in conjunction with the key configuration

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.

                            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.

                            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.

                            The IP address and netmask of the cluster (back-side) network (e.g.,
If multiple networks are to be used, a space-delimited list of a.b.c.d/x
can be provided.

                            Key ID to import to the apt keyring to support use with arbitary source
configuration from outside of Launchpad archives or PPA's.

                            Configure use of direct IO for OSD journals.
                            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.

                            By default, the charm will not encrypt Ceph OSD devices; however, by
setting osd-encrypt to True, Ceph's dmcrypt support will be used to
encrypt OSD devices.

Specifying this option on a running Ceph OSD node will have no effect
until new disks are added, at which point new disks will be encrypted.

                            If set to True, supporting services will log to syslog.

                            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).