openstack
/
charm-masakari-monitors
Code Issues Proposed changes
Juju Charm - Masakari Monitors
48 Commits 24 Branches 0 Tags 15 MiB
Python 99.2%
Jinja 0.8%
Go to file
Alex Kavanagh fbe04d5665 Add hirsute and remove trusty from metadata.yaml 
This update adds the new hirsute Ubuntu release (21.04) and
removes trusty support (14.04 which is EOL at 21.04).

Change-Id: I8623128fd878d22b4b89c1316eb8c1c9234304b6
 		2021-03-02 20:59:05 +00:00
src Add hirsute and remove trusty from metadata.yaml 2021-03-02 20:59:05 +00:00
unit_tests Stop to use the __future__ module. 2020-06-02 19:56:45 +02: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
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
rebuild Rebuild with udpated charm-tools 2.8.2 2021-02-01 14:09:59 -08:00
requirements.txt Updates to pin charm-tools to 2.8.3 2021-02-17 12:13:48 +00:00
test-requirements.txt Sync release-tools 2020-12-15 10:56:56 +01:00
tox.ini Updates to pin charm-tools to 2.8.3 2021-02-17 12:13:48 +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.