* Update requirements.txt to pin charm-tools to 2.8.3 * Update tox.ini to change the build parameters. * This upgrades from <2.7 which adds reproducible charms * Bug was fixed that controlled the default output directory doesn't get 'builds' appended. The tox change puts it back so that stable & master both build to the same directory. This may be reviewed in the future. Change-Id: I9a4ceac2d4faf884dd8ee9a0cbf38143f24e2868
|1 week ago|
|src||3 weeks ago|
|unit_tests||9 months ago|
|.gitignore||1 year ago|
|.gitreview||1 year ago|
|.stestr.conf||1 year ago|
|.zuul.yaml||11 months ago|
|LICENSE||1 year ago|
|README.md||9 months ago|
|rebuild||3 weeks ago|
|requirements.txt||1 week ago|
|test-requirements.txt||1 month ago|
|tox.ini||1 week ago|
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.
config.yaml for the full list of configuration options, along with
their descriptions and default values.
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.
Please report bugs on Launchpad.
For general charm questions refer to the OpenStack Charm Guide.