openstack
/
charm-masakari-monitors
Code Issues Proposed changes
Juju Charm - Masakari Monitors
80 Commits 24 Branches 0 Tags 15 MiB
Python 99.2%
Jinja 0.8%
Go to file
Alex Kavanagh 5397f617f6 Stable artefacts for stable/2023.1 (antelope) 
This patch is to lock the stable/2023.1 (antelope release) charms
down so that as much as possible.
In particular, this patch does:

- set the .gitreview to stable/2023.1
- lock zaza and zaza-openstack-tests to stable/antelope branches
- for reactive charms Add build.lock files to lock the layers
  and python modules used to build the charm.
- for ops framework charms, extract a pip freeze from the
  charmcraft container after building the charm to lock the
  modules used to build the charm.
- drop the kinetic bundles if the exist. (Note the updates to
  tests.yaml is in another batch (topic: antelope-voting)
- update the bundles so that they point to the antelope specific
  channels.  e.g. 2023.1/edge for OpenStack charms, 23.03/edge for
  OVN charms, quincy/edge for Ceph charms and generally, the
  appropriate LTS Jammy branch for the various support charms.

Change-Id: I4a84b4e295f3d1c1178d863cd573168ffc2c3a1f
 		2023-04-22 10:03:47 +00:00
src Stable artefacts for stable/2023.1 (antelope) 2023-04-22 10:03:47 +00:00
unit_tests Fix config-flags support 2022-11-22 19:54:53 +00:00
.gitignore Add *.charm to gitignore 2022-04-18 21:08:13 +01:00
.gitreview Stable artefacts for stable/2023.1 (antelope) 2023-04-22 10:03:47 +00:00
.stestr.conf Add unit tests 2019-03-20 09:56:19 +00:00
.zuul.yaml Add Antelope support 2023-03-08 14:15:18 +00:00
LICENSE Initial commit 2019-02-22 15:59:02 +00:00
README.md Update README for supported status 2020-05-19 12:32:11 -04:00
__init__.py Add unit tests 2019-03-20 09:56:19 +00:00
bindep.txt Fix config-flags support 2022-11-22 19:54:53 +00:00
charmcraft.yaml Add Antelope support 2023-03-08 14:15:18 +00:00
metadata.yaml Migrate charm to charmhub latest/edge track 2022-01-27 21:37:27 +00:00
osci.yaml Add Antelope support 2023-03-08 14:15:18 +00:00
rebuild Add xena bundles 2021-09-27 14:48:55 +01:00
requirements.txt Add Kinetic and Zed support 2022-11-23 16:08:18 +00:00
test-requirements.txt Stable artefacts for stable/2023.1 (antelope) 2023-04-22 10:03:47 +00:00
tox.ini Fix charm for tox4 compatibility 2023-01-17 14:58:46 +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-monitors charm deploys Monitors for Masakari whose purpose is to detect hypervisor and instances failures and to inform Masakari about them.

The charm is a subordinate charm (to the nova-compute charm) and is used in conjunction with the masakari 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 masakari-monitors:

juju deploy masakari-monitors

Because this is a subordinate charm a relation will need to be added to another application to have the charm deployed on a machine.

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.

  • pause
  • restart-services
  • resume

Bugs

Please report bugs on Launchpad.

For general charm questions refer to the OpenStack Charm Guide.