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.
 
Zuul c08c70a5d5 Merge "Add impish to metadata.yaml" 3 weeks ago
src Add impish to metadata.yaml 3 weeks ago
unit_tests Stop to use the __future__ module. 1 year ago
.gitignore Add functional & unit tests 2 years ago
.gitreview OpenDev Migration Patch 2 years ago
.stestr.conf Add functional & unit tests 2 years ago
.zuul.yaml [ussuri][goal] Updates for python 2.7 drop 1 year ago
LICENSE Initial commit 2 years ago
README.md Update README for supported status 1 year ago
osci.yaml Test bundles for focal-wallaby and hirsute-wallaby 2 months ago
rebuild rebuild - restore c-h proxy env vars for add-apt-repository 1 month ago
requirements.txt Updates to pin charm-tools to 2.8.3 4 months ago
test-requirements.txt Updates to flip all libraries back to master 2 months ago
tox.ini 21.04 libraries freeze for charms on master branch 3 months 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.