e357f2a1b5
This change adds support for pacmaker-remots joining the cluster via the pacemaher-remote relation. The pacemaker-remotes can advertise whether they should host resources. If the pacemaker-remotes are only being used for failure detection (as is the case with masakari host monitors) then they will not host resources. Pacemaker remotes are managed in the cluster as resources which nominally run on a member in the main cluster. The resource that corresponds to the pacemaker-remote is managed via configure_pacemaker_remotes and configure_pacemaker_remote functions. If the pacemaker-remotes should not run resources then the cluster needs to be switched to an opt-in cluster. In an opt-in cluster location rules are needed to explicitly allow a resource to run on a specific node. This behaviour is controlled via the global cluster parameter 'symmetric-cluster' this is set via the new method set_cluster_symmetry. The method add_location_rules_for_local_nodes is used for creating these explicit rules. Change-Id: I0a66cfb1ecad02c2b185c5e6402e77f713d25f8b
33 lines
646 B
YAML
33 lines
646 B
YAML
name: hacluster
|
|
summary: Corosync Cluster Engine - membership, messaging and quorum
|
|
maintainer: OpenStack Charmers <openstack-charmers@lists.ubuntu.com>
|
|
subordinate: true
|
|
description: |
|
|
Corosync/Pacemaker
|
|
tags:
|
|
- misc
|
|
series:
|
|
- xenial
|
|
- bionic
|
|
- cosmic
|
|
- trusty
|
|
requires:
|
|
juju-info:
|
|
interface: juju-info
|
|
scope: container
|
|
peer-availability:
|
|
interface: juju-info
|
|
scope: container
|
|
pacemaker-remote:
|
|
interface: pacemaker-remote
|
|
provides:
|
|
ha:
|
|
interface: hacluster
|
|
scope: container
|
|
nrpe-external-master:
|
|
interface: nrpe-external-master
|
|
scope: container
|
|
peers:
|
|
hanode:
|
|
interface: hacluster
|