Juju Charm - Masakari Instances High Availability Service
Go to file
Alex Kavanagh b902a59fa7 Updates for caracal testing support
These updates, on the master branch, are to support testing the caracal
packages and support of the charms for caracal.  They do NOT lock the charms
down, and don't change the testing branches to stable branches.

Change-Id: I75d4112af25ae1980e9901b35325c798040e7294
2024-02-24 19:54:24 +00:00
src Updates for caracal testing support 2024-02-24 19:54:24 +00:00
unit_tests Use unittest.mock instead of mock 2021-12-15 11:19:29 +00:00
.gitignore Add *.charm to gitignore 2022-04-18 21:08:03 +01:00
.gitreview Distribute direct charm dependencies 2019-08-15 12:31:11 +02:00
.stestr.conf Add unit tests 2019-03-20 09:20:01 +00:00
.zuul.yaml Add Antelope support 2023-03-07 23:14:21 +00:00
LICENSE first 2019-02-08 12:17:58 +01:00
README.md Add charm icon 2020-05-28 07:06:14 +02:00
bindep.txt Add Kinetic and Zed support 2022-10-26 14:32:00 +00:00
charmcraft.yaml Updates for caracal testing support 2024-02-24 19:54:24 +00:00
metadata.yaml Update to build using charmcraft 2022-02-21 15:14:50 +00:00
osci.yaml Add 2023.2 Bobcat support 2023-08-02 14:24:41 -04:00
rebuild Ensure get_requests_for_local_unit doesn't fail on incomplete relation 2023-08-04 18:48:17 +01:00
rename.sh Update to build using charmcraft 2022-02-21 15:14:50 +00:00
requirements.txt Add Kinetic and Zed support 2022-10-26 14:32:00 +00:00
test-generate-requirements.txt first 2019-02-08 12:17:58 +01:00
test-requirements.txt Add Kinetic and Zed support 2022-10-26 14:32:00 +00:00
tox.ini Updates for caracal testing support 2024-02-24 19:54:24 +00:00

README.md

Overview

Masakari is used to provide automated recovery of KVM-based OpenStack machine instances for deployments that use shared storage (volumes).

The masakari charm deploys the Masakari engine and the Masakari API. It is used in conjunction with the masakari-monitors and pacemaker-remote charms. Together, these charms provide the following functionality:

  1. Evacuation of instances (supported since OpenStack Stein)
    In the event of hypervisor failure, instances can be migrated to another hypervisor.

  2. Restarting of instances (supported since OpenStack Ussuri)
    A failed instance can be restarted.

For details see the Automated Instance Recovery appendix in the OpenStack Charms Deployment Guide.

Note: The restarting of services (e.g. nova-compute) is not supported by the charm as it is considered a systemd task.

Usage

Configuration

See file config.yaml for the full list of configuration options, along with their descriptions and default values.

Deployment

To deploy a single masakari unit:

juju deploy masakari

High availability

When more than one unit is deployed with the hacluster application the charm will bring up an HA active/active cluster.

To deploy a three-node cluster:

juju deploy -n 3 masakari

There are two mutually exclusive high availability options: using virtual IP(s) or DNS. In both cases the hacluster subordinate charm is used to provide the Corosync and Pacemaker backend HA functionality.

See the OpenStack high availability appendix in the OpenStack Charms Deployment Guide for details.

Actions

This section lists Juju actions supported by the charm. Actions allow specific operations to be performed on a per-unit basis. To display action descriptions run juju actions masakari. If the charm is not deployed then see file actions.yaml.

  • openstack-upgrade
  • pause
  • restart-services
  • resume

Bugs

Please report bugs on Launchpad.

For general charm questions refer to the OpenStack Charm Guide.