Hi all,

We wrote a role to configure Pacemaker clusters, and I'd like to share it with the community. Any questions or comments welcome.

Unlike similar roles/playbooks, this one works directly on CIB XML dump, as recommended by Pacemaker Explained document, and not parsing pcs output. It changes the document as needed, validates it using crm_verify, and pushes to the cluster. The role is idempotent (won't make unnecessary changes) and supports check mode.

We tested it on Scientific Linux 7, so it will work fine on RHEL 7, and compatible Fedora/CentOS. Ansible 2.5 is required, because it uses some new grammar and modules, but luckily 2.5 is already in Debian Sid that we run on our laptops.

What it currently doesn't do is detecting/configuring Firewalld (for Corosync/Pacemaker), but we'll probably add this feature. Configuring rules for the cluster-managed apps is on the user, of course.

It's GPLv3, so enjoy, share, and fork:
https://github.com/devgateway/ansible-role-pacemaker
--
Best regards,
Styopa Semenukha,
Senior IT Analyst at Development Gateway.
_______________________________________________
Users mailing list: Users@clusterlabs.org
https://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

Reply via email to