074e02ab94
Switch functional tests to use cephx; Tests should really align to default configuration, which is to have cephx enabled for a deployment. Updated README to be a little simpler, and default to Xenial rather than Trusty. Added proper Ceph icon. Drop layer dependency on ceph-base - it brings in loads of stuff we don't need. Tidy config.yaml to drop duplicate ceph-public-network. Depends-On: Ied8d5306ab77b8e68efd0a8e5df4087a067f0367 Change-Id: I4ab5438db93ae613e9232ca42df1c23614e212e6 |
||
---|---|---|
.. | ||
actions | ||
reactive | ||
templates | ||
tests | ||
README.md | ||
actions.yaml | ||
config.yaml | ||
copyright | ||
icon.svg | ||
layer.yaml | ||
metadata.yaml | ||
test-requirements.txt | ||
tox.ini | ||
wheelhouse.txt |
README.md
CephFS Charm
Overview
Ceph is a distributed storage and network file system designed to provide excellent performance, reliability, and scalability.
This charm deploys a Ceph MDS cluster.
Usage
Boot things up by using:
juju deploy -n 3 ceph-mon
juju deploy -n 3 ceph-osd
In my example deployments on EC2 the following ceph.yaml will work:
You can then deploy this charm by simply doing:
juju deploy ceph-fs
juju add-relation ceph-fs ceph-mon
Once the ceph-mon and osd charms have bootstrapped the cluster, the ceph-mon charm will notify the ceph-fs charm.