Juju Charm - Ceph OSD
Go to file
2017-01-25 16:26:40 +00:00
actions Skip osd-devices not absolute paths 2016-12-22 16:34:25 -07:00
files Revert "Remove /var/lib/ceph from updatedb" 2017-01-23 08:38:40 +00:00
hooks Merge "Remove /var/lib/ceph from updatedb" 2017-01-25 16:26:40 +00:00
lib Move a disk with an action 2016-12-12 11:34:49 -05:00
templates Perf Optimizations 2016-07-14 15:24:59 -07:00
tests Remove /var/lib/ceph from updatedb 2017-01-25 09:22:14 -05:00
unit_tests Merge "Skip osd-devices not absolute paths" 2017-01-16 13:13:23 +00:00
.coveragerc Add unit tests for service status 2015-10-06 21:15:38 +01:00
.gitignore Clean up dependency chain 2016-08-11 11:01:24 -04:00
.gitreview Add gitreview prior to migration to openstack 2016-02-24 21:53:28 +00:00
.project Initial ceph-osd charm 2012-10-08 15:07:16 +01:00
.pydevproject Add unit tests for service status 2015-10-06 21:15:38 +01:00
.testr.conf Add tox support 2015-10-30 11:22:54 +09:00
actions.yaml Move a disk with an action 2016-12-12 11:34:49 -05:00
charm-helpers-hooks.yaml Add support for apparmor security profiles 2016-09-28 09:30:52 +01:00
charm-helpers-tests.yaml Move charm-helpers-sync.yaml to charm-helpers-hooks.yaml and 2014-09-27 02:28:51 +00:00
config.yaml Add availability_zone to the OSD configuration 2016-12-09 15:06:47 -05:00
copyright Re-license charm as Apache-2.0 2016-06-28 12:01:05 +01:00
hardening.yaml Add hardening support 2016-03-24 11:14:47 +00:00
icon.svg Add ceph icon 2013-06-25 14:04:30 +01:00
LICENSE Re-license charm as Apache-2.0 2016-06-28 12:01:05 +01:00
Makefile Update Make jobs to separate out ceph lib sync 2016-12-01 09:19:17 -05:00
metadata.yaml Update Amulet defs, series metadata and c-h sync 2016-12-03 16:41:49 +00:00
README.md Add support for Juju network spaces 2016-04-08 22:42:36 +01:00
requirements.txt Add action to list unmounted disks 2016-11-28 16:53:04 -05:00
revision [hopem] Added use-syslog cfg option to allow logging to syslog 2014-03-25 18:44:23 +00:00
setup.cfg Add unit tests for service status 2015-10-06 21:15:38 +01:00
test-requirements.txt Use bundletester for amulet test execution 2016-07-21 18:06:41 +00:00
TODO Enable cephx support by default 2012-10-09 12:19:16 +01:00
tox.ini Update tox.ini files from release-tools gold copy 2016-09-09 19:42:56 +00:00

Overview

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.

Usage

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

osd-devices:
    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::

ceph-osd:
    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:

ceph-osd:
  charm: cs:xenial/ceph-osd
  num_units: 1
  bindings:
    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