openstack/charm-masakari-monitors
Code Issues Proposed changes
Juju Charm - Masakari Monitors
62 Commits 24 Branches 0 Tags 15 MiB
Python 95.7%
Shell 3.5%
Jinja 0.8%
2f33d9afeb
Go to file
James Page 2f33d9afeb Remove all traces of process monitor 
The Masakari process monitor is explicitly outside the scope of
what we chose to enable when the original charm development was
done for Masakari.

Drop installation of the process monitor package and related
templates and configuration.

Drive-by fixup of requirements for older Pythons.

Related-Bug: 1941623
Change-Id: Id883c117e73e71842fbe7a96e0471b37e999020f
2021-11-04 14:06:56 +00:00
src Remove all traces of process monitor 2021-11-04 14:06:56 +00:00
unit_tests Stop to use the __future__ module. 2020-06-02 19:56:45 +02:00
__init__.py Add unit tests 2019-03-20 09:56:19 +00:00
.gitignore Add unit tests 2019-03-20 09:56:19 +00: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 Add gitreview, zuul config, fix coverage, fix lint 2019-07-31 22:15:35 -05:00
LICENSE Initial commit 2019-02-22 15:59:02 +00:00
osci.yaml Test bundles for focal-wallaby and hirsute-wallaby 2021-06-29 13:48:31 +02:00
pip.sh Add xena bundles 2021-09-27 14:48:55 +01:00
README.md Update README for supported status 2020-05-19 12:32:11 -04:00
rebuild Add xena bundles 2021-09-27 14:48:55 +01:00
requirements.txt Remove all traces of process monitor 2021-11-04 14:06:56 +00:00
test-requirements.txt Remove all traces of process monitor 2021-11-04 14:06:56 +00:00
tox.ini Add xena bundles 2021-09-27 14:48:55 +01: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.