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.