Juju Charm - Masakari Monitors
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
Corey Bryant 7991de8a8c rebuild - restore c-h proxy env vars for add-apt-repository 1 month ago
src Updates to flip all libraries back to master 2 months ago
unit_tests Stop to use the __future__ module. 1 year ago
.gitignore Add unit tests 2 years ago
.gitreview Add gitreview, zuul config, fix coverage, fix lint 2 years ago
.stestr.conf Add unit tests 2 years ago
.zuul.yaml Add gitreview, zuul config, fix coverage, fix lint 2 years ago
LICENSE Initial commit 2 years ago
README.md Update README for supported status 1 year ago
__init__.py Add unit tests 2 years ago
osci.yaml Add new osci.yaml 3 months ago
rebuild rebuild - restore c-h proxy env vars for add-apt-repository 1 month ago
requirements.txt Updates to pin charm-tools to 2.8.3 4 months ago
test-requirements.txt Updates to flip all libraries back to master 2 months ago
tox.ini 21.04 libraries freeze for charms on master branch 3 months ago

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.