fb5e0dfc9f
Due to a build problem with the reactive plugin, this change falls back
on overriding the steps and doing a manual build, but it also ensures
the CI system builds the charm using charmcraft. Changes:
- add a build-requirements.txt
- modify charmcraft.yaml
- modify osci.yaml
-> indicate build with charmcraft
- modify tox.ini
-> tox -e build does charmcraft build/rename
-> tox -e build-reactive does the reactive build
- modify bundles to use the <charm>.charm artifact in tests.
and fix deprecation warning re: prefix
- tox inception to enable tox -e func-test in the CI
Change-Id: Ief58dc3b09a7b9c3f23fd2cb9054fb01306e56a9
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.