Merge lp:~themue/clouddocs/003-splitted-and-continued-ceph into lp:~jujudocs/clouddocs/trunk

Proposed by Frank Mueller on 2014-04-04
Status: Merged
Approved by: Nick Veitch on 2014-04-04
Approved revision: 11
Merged at revision: 12
Proposed branch: lp:~themue/clouddocs/003-splitted-and-continued-ceph
Merge into: lp:~jujudocs/clouddocs/trunk
Diff against target: 69 lines (+18/-35)
1 file modified
Scaling-Ceph.md (+18/-35)
To merge this branch: bzr merge lp:~themue/clouddocs/003-splitted-and-continued-ceph
Reviewer Review Type Date Requested Status
Nick Veitch 2014-04-04 Pending
Review via email: mp+214233@code.launchpad.net

Description of the change

Splitted Ceph into installation and scaling and continued work. Scaling has to be continued later based on an information by James Page about possible inefficiencies when adding storrage nodes later.

To post a comment you must log in.

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file 'Scaling-Ceph.md'
2--- Scaling-Ceph.md 2014-04-02 16:18:10 +0000
3+++ Scaling-Ceph.md 2014-04-04 13:07:55 +0000
4@@ -5,47 +5,30 @@
5
6 ## Introduction
7
8-As documented in the *OpenStack Installation Guide* we're using Ceph as block device
9-for Cinder. It stripes block device images as objects across a cluster. This way it
10-provides a better performance than a typical standalone server. So it allows scalability
11-and redundancy needs to be satisified and Cinder's RBD driver used to create, export and
12-connect volumes to instances. This assumes a functioning Ceph cluster has already been
13+Beside the redundancy for more safety and the higher performance through the usage of
14+Ceph as storage backend for OpenStack the user also benefits from the more simple way
15+of scaling the storage of the needs grow.
16
17 ## Scope
18
19 **TODO**
20
21-## Deployment
22-
23-**TODO** Check installation document and compare to Information by James Page.
24-
25-The usage of Ceph as block device for our Cinder needs a deployed and configured Ceph
26-cluster. This has been described in the document mentioned above. Here our
27-`openstack-config.yaml` contains the setting `block-device: None` for Cinder.
28-This way we don't use the local device for Cinder.
29-
30-The next step has to be adding the relations between Cinder and Ceph as well as Cinder
31-and other needed services.
32-
33-````
34-juju add-relation cinder ceph
35-juju add-relation cinder keystone
36-juju add-relation cinder mysql
37-juju add-relation cinder rabbitmq-server
38-juju add-relation cinder nova-cloud-controller
39-````
40-
41 ## Scaling
42
43 The addition of Ceph nodes is done using the Juju `add-node` command. By default
44 it adds only one node, but it is possible to add the number of wanted nodes as
45-argument.
46-
47-````
48-# Add one ceph node
49-$ juju add-node ceph
50-# Add ten ceph nodes
51-$ juju add-node ceph -n 10
52-````
53-
54-**SEE ALSO** https://jujucharms.com/precise/ceph-22/#readme
55+argument. To add one more Ceph OSD Daemon node you simply call
56+
57+```
58+juju add-node ceph-osd
59+```
60+
61+Larger numbers of nodes can be added using the `-n` argument, e.g. 10 nodes
62+with
63+
64+```
65+juju add-node -n 10 ceph-osd
66+```
67+
68+**TODO** Adding nodes later can cause some in-efficiencies. This should be covered.
69+

Subscribers

People subscribed via source and target branches