New/updated ceph charms for quantal

Bug #1064908 reported by James Page
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juju Charms Collection
Fix Released

Bug Description

With the release of ceph 0.48 onwards, automating deployment of a ceph cluster is much easier.

This 'charm set' (for want of a better word) allows deployment of a ceph cluster, expansion using the ceph-osd charm and access over HTTP using the ceph-radosgw charm.

I've also included a ceph-client charm to show how to configure other services to use the ceph-client interface.

Note that it is also possible to use these charms with precise; however you will need a backport of ceph from quantal as provided in:


This is supported as a configuration option for the charm.

Related branches

Revision history for this message
James Page (james-page) wrote :

Tested OK on an OpenStack based cloud; however I have seen issues with ec2 when odd hostnames (domU-XXX) are generated in the instances.

Won't work with local provider as requires block device access.

Main target would really be MAAS based deployments (earlier version of 'ceph' did test OK in this type of environment as well)

summary: - New/updated ceph charms
+ New/updated ceph charms for quantal
description: updated
Revision history for this message
Adam Gandelman (gandelman-a) wrote :

Tested these charms today as a standalone Ceph cluster with the ceph-client service, as well as integrated with an OpenStack cloud. The code is clean, easy to read and pep8 clean (!!). Pushing to the charm store for Quantal.

Changed in charms:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.