openstack
/
charm-masakari
Code Issues Proposed changes
charm-masakari/src
History
Alex Kavanagh fb0b98c45d Updates to enable jammy and finalise charmcraft builds 
- Add 22.04 to charmcraft.yaml
- Update metadata to include jammy
- Remove impish from metadata
- Update osci.yaml to include py3.10 default job
- Modify tox.ini to remove py35,py36,py37 tox target and add py310
  target.
- ensure that the openstack-origin is yoga

Change-Id: I59ab3d2fa63b534296c5a703322e9aa3e061bff5
 		2022-04-06 15:45:44 +01:00
..
files Sync charm/ceph helpers, tox, and requirements 2019-09-30 20:59:19 -05:00
lib/charm/openstack Fix install hook on Groovy 2021-01-11 13:19:20 +01:00
reactive Specify certificates relation to update endpoints. 2021-08-18 15:03:26 -05:00
templates Fix transport_url with multiple rabbit servers 2021-12-07 18:18:49 -03:00
tests Update to build using charmcraft 2022-02-21 15:14:50 +00:00
README.md Update README for supported status 2020-05-19 12:33:18 -04:00
config.yaml Updates to enable jammy and finalise charmcraft builds 2022-04-06 15:45:44 +01:00
copyright first 2019-02-08 12:17:58 +01:00
icon.svg Add charm icon 2020-05-28 07:06:14 +02:00
layer.yaml Distribute direct charm dependencies 2019-08-15 12:31:11 +02:00
metadata.yaml Updates to enable jammy and finalise charmcraft builds 2022-04-06 15:45:44 +01:00
test-requirements.txt Update to build using charmcraft 2022-02-21 15:14:50 +00:00
tox.ini Add xena bundles 2021-09-27 14:45:25 +01:00
wheelhouse.txt Update to build using charmcraft 2022-02-21 15:14:50 +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.