openstack
/
charm-ceph-mon
Code Issues Proposed changes
Juju Charm - Ceph MON
20 Commits 30 Branches 3 Tags 25 MiB
Python 99.5%
Shell 0.5%
Go to file
James Page dbd2a656cb Updates for pep8 compliance, added peer hinting to mon hook, removed redundant mon-relation-changed hook, updated copyright, added start/stop hooks to keep charm proof quiet 2012-10-04 09:28:49 +01:00
files/upstart import upstart scripts from argonaut 2012-10-03 21:19:53 +13:00
hooks Updates for pep8 compliance, added peer hinting to mon hook, removed redundant mon-relation-changed hook, updated copyright, added start/stop hooks to keep charm proof quiet 2012-10-04 09:28:49 +01:00
templates write fsid to ceph.conf 2012-10-03 21:19:14 +13:00
README add README and some prototype hooks 2012-10-02 22:25:11 +13:00
TODO start a TODO 2012-10-03 23:01:49 +13:00
config.yaml wait for 3 potential monitors to show up, and then try to configure the cluster 2012-10-03 23:02:28 +13:00
copyright Updates for pep8 compliance, added peer hinting to mon hook, removed redundant mon-relation-changed hook, updated copyright, added start/stop hooks to keep charm proof quiet 2012-10-04 09:28:49 +01:00
metadata.yaml Updates for pep8 compliance, added peer hinting to mon hook, removed redundant mon-relation-changed hook, updated copyright, added start/stop hooks to keep charm proof quiet 2012-10-04 09:28:49 +01:00
revision Fixed subprocess exception handling in is_quorum, use socket.gethostname() for better hostname resolution, drop extra call for wait_for_quorum from osdize_and_activate 2012-10-03 16:07:47 +01:00

README 

This charm deploys a Ceph cluster.

It uses the new-style Ceph deployment as reverse-engineered from the
Chef cookbook at https://github.com/ceph/ceph-cookbooks

This charm is currently deliberately inflexible and potentially
destructive.  It is designed to deploy on exactly three machines.
Each machine will run mon and osd.

The osds use so-called "OSD hotplugging".  ceph-disk-prepare is used
to create the filesystems with a special GPT partition type.  udev is
set up to mount such filesystems and start the osd daemons as their
storage becomes visible to the system (or after "udevadm trigger").

The Chef cookbook above performs some extra steps to generate an OSD
bootstrapping key and propagate it to the other nodes in the cluster.
Since all our OSDs run on nodes that also run mon, we don't need this
and did not implement it.