openstack
/
charm-masakari-monitors
Code Issues Proposed changes
Juju Charm - Masakari Monitors
75 Commits 24 Branches 0 Tags 15 MiB
Python 99.2%
Jinja 0.8%
Go to file
Corey Bryant 123e8e06f6 Build separately for each supported series and use binary builds 
Charms for OpenStack Yoga supports both Ubuntu Focal and Jammy
which means Python 3.8 and Python 3.10.  Managing dependencies
across those two versions is non-trivial and we need to build
the charm on the series the charm is supposed to support.

Switch to using a binary build which allows pip's dependency
resolution to work.

This patch also drops the impish bundle and unused overlay
bundles.

Change-Id: I85d45fd390eccfef2fbdcd9de96b7b7cf01483f4
 		2022-11-23 16:07:05 +00:00
src Build separately for each supported series and use binary builds 2022-11-23 16:07:05 +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 Add gitreview, zuul config, fix coverage, fix lint 2019-07-31 22:15:35 -05:00
.stestr.conf Add unit tests 2019-03-20 09:56:19 +00:00
.zuul.yaml Updates to enable jammy and finalise charmcraft builds 2022-04-04 15:50:52 +01: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
build-requirements.txt Update to build using charmcraft 2022-02-17 12:30:11 -05:00
charmcraft.yaml Build separately for each supported series and use binary builds 2022-11-23 16:07:05 +00:00
metadata.yaml Migrate charm to charmhub latest/edge track 2022-01-27 21:37:27 +00:00
osci.yaml Build separately for each supported series and use binary builds 2022-11-23 16:07:05 +00:00
pip.sh Add xena bundles 2021-09-27 14:48:55 +01:00
rebuild Add xena bundles 2021-09-27 14:48:55 +01:00
rename.sh Update to build using charmcraft 2022-02-17 12:30:11 -05:00
requirements.txt Updates to enable jammy and finalise charmcraft builds 2022-04-04 15:50:52 +01:00
test-requirements.txt Update to build using charmcraft 2022-02-17 12:30:11 -05:00
tox.ini Build separately for each supported series and use binary builds 2022-11-23 16:07:05 +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.