ceph-ansible - Ansible playbooks for Ceph

  •        0

General support for:* Monitors* OSDs* MDSs* RGWMore details:* Authentication (cephx), this can be disabled.* Supports cluster public and private network.* Monitors deployment. You can easily start with one monitor and then progressively add new nodes. So can deploy one monitor for testing purpose. For production, I recommend to always use an odd number of monitors, 3 tends to be the standard.* Object Storage Daemons. Like the monitors you can start with a certain amount of nodes and then grow this number. The playbook either supports a dedicated device for storing the journal or both journal and OSD data on the same device (using a tiny partition at the beginning of the device).* Metadata daemons.* Collocation. The playbook supports collocating Monitors, OSDs and MDSs on the same machine.* The playbook was validated on Debian Wheezy, Ubuntu 12.04 LTS and CentOS 6.4.* Tested on Ceph Dumpling and Emperor.* A rolling upgrade playbook was written, an upgrade from Dumpling to Emperor was performed and worked.




comments powered by Disqus

Related Projects

ansible-ceph_facts - This module currently dumps out facts for the ceph distributed object store.

This module currently dumps out facts for the ceph distributed object store.

compass-core - Automating Distributed System Deployment to Baremetal Resources

As a platform-independent deployment automation system, Compass simplifies the complex and error-prone deployment process of various distributed systems such as Openstack, Ceph and so on. It dramatically reduces the time of datacenter server management. Compass, designed with an extensible architecture, can be easily integrated with most of the popular automation tools (Cobbler, Chef, Ansible) and allows third-parties (vendors) plugins for hardware discovery.