openstack/charm-masakari
Code Issues Proposed changes
Juju Charm - Masakari Instances High Availability Service
96 Commits 24 Branches 0 Tags 1.7 MiB
Python 96.6%
Shell 2.8%
Jinja 0.6%
master
Go to file
James Page 3df925994c
Misc tidyup 
Drop test-generate-requirements.txt as its not used.

Change-Id: I8fdad6adfca5f670388cf2be77de19f663a074d2
2024-09-06 10:10:36 +01:00
src Add charmcraft 3 support 2024-09-03 19:31:30 +00:00
unit_tests Use unittest.mock instead of mock 2021-12-15 11:19:29 +00:00
.coverage Fix issues related to py312 compatibility 2024-08-21 14:45:41 +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 charmcraft 3 support 2024-09-03 19:31:30 +00:00
bindep.txt Add Kinetic and Zed support 2022-10-26 14:32:00 +00:00
charmcraft.yaml Add charmcraft 3 support 2024-09-03 19:31:30 +00:00
LICENSE first 2019-02-08 12:17:58 +01:00
metadata.yaml Update to build using charmcraft 2022-02-21 15:14:50 +00:00
osci.yaml Add charmcraft 3 support 2024-09-03 19:31:30 +00:00
README.md Add charm icon 2020-05-28 07:06:14 +02: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 Fix issues related to py312 compatibility 2024-08-21 14:45:41 +00:00
test-requirements.txt Fix issues related to py312 compatibility 2024-08-21 14:45:41 +00:00
tox.ini Add charmcraft 3 support 2024-09-03 19:31:30 +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.