Integration of Masakari with OpenStack-Ansible¶
openstack, masakari, masakari-monitors
- Blueprint on Launchpad:
Masakari provides Virtual Machine High Availability (VMHA) service for OpenStack clouds by automatically recovering the KVM-based Virtual Machine(VM)s from failure events such as VM process down, provisioning process down, and nova-compute host failure. It also provides API service for managing and controlling the automated rescue mechanism. The Masakari service consists of the following components:
masakari-api: An OpenStack-native REST API that processes API requests by sending them to the
masakari-engineover Remote Procedure Call (RPC).
masakari-engine: Processes the notifications received from
masakari-apiby execcuting the recovery workflow in asynchronus way.
masakari-monitors: Monitors for Masakari provides Virtual Machine High Availability (VMHA) service for OpenStack clouds by automatically detecting the failure events such as VM process down, provisioning process down, and nova-compute host failure. If it detects the events, it sends notifications to the masakari-api.
This spec outlines the steps required to integrate Masakari with OpenStack-Ansible.
Masakari provides Instances High Availability Service for OpenStack clouds by automatically recovering failed Instances. However, it needs to be installed manually with OpenStack-Ansible. No role exists to deploy it as other services are deployed.
The proposed changes would include:
Import a proof of concept role for Masakari from https://github.com/NirajSingh90/openstack-ansible-os_masakari to
Follow the usual path described in the developer documentation.
There are no alternatives.
This is a new feature added into OpenStack-Ansible. No role currently exists. Therefore, new role, openstack-ansible-os_masakari needs to be written from scratch.
No upgrade impact since this would be the first implementation of the proposed change.
No security impact.
No performance impact.
End user impact¶
End user will be able to use masakari as a service within OpenStack-Ansible.
Deployers will need to enable Masakari deployments if they choose to use this. Masakari will not be deployed by default.
By employing a combination of Corosync and Pacemaker, OpenStack Masakari creates a cluster of servers, detecting and reporting failure of hosts in the cluster. So masakari is dependent on Corosync and Pacemaker.
We will reuse an external role for corosync and pacemaker to not re-invent the wheel, like the one found in https://github.com/leucos/ansible-pacemaker-corosync .
- Primary assignee:
Niraj Singh (IRC: niraj_singh)
Masakari is not available as a service for OpenStack-Ansible. No role already exists. A new role will be developed from scratch in compliance with the standards set by the community. It will be added under https://github.com/openstack/openstack-ansible-os_masakari
Note: Masakari role will install below services: masakari-api masakari-engine masakari-processmonitor masakari-hostmonitor masakari-instancemonitor
masakari-processmonitor, masakari-hostmonitor and masakari-instancemonitor will be installed only on nova-compute nodes
Tests will be developed to ensure that deployment of Masakari works. Masakari doesn’t have tempest tests therefore we will start by testing the API responses codes. Masakari-monitor and Masakari-engine services tests will be added in future using third party CI tests.
As this would be new feature added to OpenStack-Ansible, it needs to be documented, explaining all the configuration parameters.
Masakari developer/operator documentation