openstack
/
charm-ceph
Code Issues Proposed changes

General tidy of README

This commit is contained in:
James Page 2013-06-24 10:15:45 +01:00
parent 5f09a0fad1
commit 6d02728d50
1 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
README.md
View File

@ -15,28 +15,28 @@ are provided:
fsid: fsid:
uuid specific to a ceph cluster used to ensure that different uuid specific to a ceph cluster used to ensure that different
clusters don't get mixed up - use `uuid` to generate one. clusters don't get mixed up - use `uuid` to generate one.
monitor-secret: monitor-secret:
a ceph generated key used by the daemons that manage to cluster a ceph generated key used by the daemons that manage to cluster
to control security. You can use the ceph-authtool command to to control security. You can use the ceph-authtool command to
generate one: generate one:
ceph-authtool /dev/stdout --name=mon. --gen-key ceph-authtool /dev/stdout --name=mon. --gen-key
These two pieces of configuration must NOT be changed post bootstrap; attempting These two pieces of configuration must NOT be changed post bootstrap; attempting
todo this will cause a reconfiguration error and new service units will not join todo this will cause a reconfiguration error and new service units will not join
the existing ceph cluster. the existing ceph cluster.
The charm also supports specification of the storage devices to use in the ceph The charm also supports specification of the storage devices to use in the ceph
cluster. cluster.
osd-devices: osd-devices:
A list of devices that the charm will attempt to detect, initialise and A list of devices that the charm will attempt to detect, initialise and
activate as ceph storage. activate as ceph storage.
This this can be a superset of the actual storage devices presented to This this can be a superset of the actual storage devices presented to
each service unit and can be changed post ceph bootstrap using `juju set`. each service unit and can be changed post ceph bootstrap using `juju set`.
At a minimum you must provide a juju config file during initial deployment At a minimum you must provide a juju config file during initial deployment
with the fsid and monitor-secret options (contents of cepy.yaml below): with the fsid and monitor-secret options (contents of cepy.yaml below):
@ -44,7 +44,7 @@ with the fsid and monitor-secret options (contents of cepy.yaml below):
fsid: ecbb8960-0e21-11e2-b495-83a88f44db01 fsid: ecbb8960-0e21-11e2-b495-83a88f44db01
monitor-secret: AQD1P2xQiKglDhAA4NGUF5j38Mhq56qwz+45wg== monitor-secret: AQD1P2xQiKglDhAA4NGUF5j38Mhq56qwz+45wg==
osd-devices: /dev/vdb /dev/vdc /dev/vdd /dev/vde osd-devices: /dev/vdb /dev/vdc /dev/vdd /dev/vde
Specifying the osd-devices to use is also a good idea. Specifying the osd-devices to use is also a good idea.
Boot things up by using: Boot things up by using:
@ -62,7 +62,7 @@ Author: Paul Collins <paul.collins@canonical.com>,
James Page <james.page@ubuntu.com> James Page <james.page@ubuntu.com>
Report bugs at: http://bugs.launchpad.net/charms/+source/ceph/+filebug Report bugs at: http://bugs.launchpad.net/charms/+source/ceph/+filebug
Location: http://jujucharms.com/charms/ceph Location: http://jujucharms.com/charms/ceph
Technical Bootnotes Technical Bootnotes
=================== ===================
@ -89,4 +89,4 @@ all OSDs run on nodes that also run mon, we don't need this and did not
implement it. implement it.
See http://ceph.com/docs/master/dev/mon-bootstrap/ for more information on Ceph See http://ceph.com/docs/master/dev/mon-bootstrap/ for more information on Ceph
monitor cluster deployment strategies and pitfalls. monitor cluster deployment strategies and pitfalls.