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
|
Undecided
|
Unassigned | ||
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:
ppa:
This is supported as a configuration option for the charm.
Related branches
lp://staging/~james-page/charms/quantal/ceph/trunk
- Juan L. Negron (community): Approve
-
Diff: 156 lines (+59/-17)4 files modifiedconfig.yaml (+11/-2)
hooks/hooks.py (+28/-7)
hooks/utils.py (+19/-7)
revision (+1/-1)
lp://staging/~james-page/charms/quantal/ceph-osd/trunk
- Juan L. Negron (community): Approve
-
Diff: 177 lines (+71/-21)4 files modifiedconfig.yaml (+11/-2)
hooks/hooks.py (+28/-7)
hooks/utils.py (+31/-11)
revision (+1/-1)
lp://staging/~james-page/charms/quantal/ceph-radosgw/trunk
- Juan L. Negron (community): Approve
-
Diff: 65 lines (+25/-11)2 files modifiedconfig.yaml (+1/-1)
hooks/utils.py (+24/-10)
Revision history for this message
| James Page (james-page) wrote | #1 |
| summary: |
- New/updated ceph charms + New/updated ceph charms for quantal |
| description: | updated |
Revision history for this message
| Adam Gandelman (gandelman-a) wrote | #2 |
| Changed in charms: | |
| status: | New → Fix Released |
To post a comment you must log in.
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)