openstack
/
charm-masakari-monitors
Code Issues Proposed changes
Juju Charm - Masakari Monitors
47 Commits 24 Branches 0 Tags 15 MiB
Python 99.2%
Jinja 0.8%
Go to file
Alex Kavanagh 02d6b7e0eb Updates to pin charm-tools to 2.8.3 
* Update requirements.txt to pin charm-tools to 2.8.3
* Update tox.ini to change the build parameters.
* This upgrades from <2.7 which adds reproducible charms
* Bug was fixed that controlled the default output directory
  doesn't get 'builds' appended.  The tox change puts it
  back so that stable & master both build to the same
  directory.  This may be reviewed in the future.

Change-Id: Ibc4a8b508697208e1be4be0548df1cdcf92a472c
 		2021-02-17 12:13:48 +00:00
src Updates for testing period for 20.01 release 2021-01-15 16:31:48 +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.