66e025a5eb
Add the 'docs' key and point it at a Discourse topic previously populated with the charm's README contents. When the new charm revision is released to the Charmhub, this Discourse-based content will be displayed there. In the absense of the this new key, the Charmhub's default behaviour is to display the value of the charm's 'description' key. Depends-On: I5c0b66cdbbef9ea8fcac83039bf2d1f9ccd4f804 Change-Id: Ie9c07b47cd942886525c24b76f131d10c6233bfb |
||
---|---|---|
src | ||
unit_tests | ||
.gitignore | ||
.gitreview | ||
.stestr.conf | ||
.zuul.yaml | ||
bindep.txt | ||
charmcraft.yaml | ||
LICENSE | ||
metadata.yaml | ||
osci.yaml | ||
README.md | ||
rebuild | ||
rename.sh | ||
requirements.txt | ||
test-requirements.txt | ||
tox.ini |
Overview
Pacemaker Remote is a small daemon that allows a host to be used as a Pacemaker node without running the full cluster stack. The pacemaker-remote charm is a subordinate charm that deploys the daemon.
This charm can be used to help deploy Masakari, which provides automated recovery of KVM-based OpenStack machine instances. See the masakari charm for more information on that use case.
Usage
Configuration
See file config.yaml
for the full list of configuration options, along with
their descriptions and default values.
Deployment
To deploy pacemaker-remote:
juju deploy pacemaker-remote
Because this is a subordinate charm a relation will need to be added to another application to have the charm deployed on a machine.
Bugs
Please report bugs on Launchpad.
For general charm questions refer to the OpenStack Charm Guide.