* update: - charmcraft.yaml for v3 - tox.ini to use py3.12 by default - test-requirements.in to use zaza for juju3 - update test bundles to work with charmcraft v3 - update .zuul.yaml to point at correct jobs for master (for now) - fix cs -> ch typo in noble-basic.yaml * generate: - merged-requirements-py312.txt - test-requirements-py312.txt * add: - update-requirements env to tox.ini and src/tox.ini Change-Id: I2aec11060a38b556bf51188fcc3411d414aa2d2e Signed-off-by: Alex RamÃrez <alex.ramirez@canonical.com>
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.
