Juju Charm - Pacemaker Remote
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
Alex Kavanagh e3fb59f43a Updates to pin charm-tools to 2.8.3 1 week ago
src Add Groovy to the test gate 3 weeks ago
unit_tests Stop to use the __future__ module. 9 months ago
.gitignore Add functional & unit tests 1 year ago
.gitreview OpenDev Migration Patch 1 year ago
.stestr.conf Add functional & unit tests 1 year ago
.zuul.yaml [ussuri][goal] Updates for python 2.7 drop 11 months ago
LICENSE Initial commit 1 year ago
README.md Update README for supported status 9 months ago
rebuild Rebuild with udpated charm-tools 2.8.2 3 weeks ago
requirements.txt Updates to pin charm-tools to 2.8.3 1 week ago
test-requirements.txt Updates for testing period for 20.01 release 1 month ago
tox.ini Updates to pin charm-tools to 2.8.3 1 week ago

README.md

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.