openstack/charm-masakari
Code Issues Proposed changes
master
charm-masakari/src
History
Myles Penner 05f07b44da Add charmcraft 3 support 
Summary of changes:
- Update the charmcraft.yaml file to use base and platforms, only
  allowing noble support.
- Update config to default to caracal.
- Update osci.yaml to use the charmcraft 3.x/beta
- Drop non-noble tests
- Update constraints file from -2024.1.txt to -noble.txt

Change-Id: I37e8e4f804993bb51f78bc1611cfc1e44f4ae03f
2024-09-03 19:31:30 +00: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 Add os_region_name config option 2023-11-07 12:22:37 +02:00
tests Add charmcraft 3 support 2024-09-03 19:31:30 +00:00
config.yaml Add charmcraft 3 support 2024-09-03 19:31:30 +00: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 Add charmcraft 3 support 2024-09-03 19:31:30 +00:00
README.md Update README for supported status 2020-05-19 12:33:18 -04:00
test-requirements.txt Fix charm for tox4 compatibility 2023-01-17 09:33:16 +00:00
tox.ini Add charmcraft 3 support 2024-09-03 19:31:30 +00: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.