Masakari is used to provide automated recovery of KVM-based OpenStack machine instances for deployments that use shared storage (volumes).
The masakari charm deploys the Masakari engine and the Masakari API. It is used in conjunction with the masakari-monitors and pacemaker-remote charms. Together, these charms provide the following functionality:
Evacuation of instances (supported since OpenStack Stein)
In the event of hypervisor failure, instances can be migrated to another hypervisor.
Restarting of instances (supported since OpenStack Ussuri)
A failed instance can be restarted.
Note: The restarting of services (e.g. nova-compute) is not supported by the charm as it is considered a
config.yaml for the full list of configuration options, along with
their descriptions and default values.
To deploy a single masakari unit:
juju deploy masakari
When more than one unit is deployed with the hacluster application the charm will bring up an HA active/active cluster.
To deploy a three-node cluster:
juju deploy -n 3 masakari
There are two mutually exclusive high availability options: using virtual IP(s) or DNS. In both cases the hacluster subordinate charm is used to provide the Corosync and Pacemaker backend HA functionality.
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
Please report bugs on Launchpad.
For general charm questions refer to the OpenStack Charm Guide.