openstack
/
masakari
Code Issues Proposed changes
Virtual Machine High Availability (VMHA) service for OpenStack.
338 Commits 11 Branches 38 Tags 9.4 MiB
Python 98.8%
Shell 1.1%
Go to file
shilpa f2343ef09c Handle KeyError: 'progress_details' 
If user tries to get notification details before masakari-engine taskflow
driver add progress details of the first task of the recovery workflow,
it's giving Keyerror: 'progress_details'.

Fixed the issue by checking progress_details is available in the meta.
If it's not present, then get notification details will return empty list
of recovery_workflow_details.

Change-Id: I79af240d7715718b424695253ee452dc9552607d
Closes-Bug: #1819422
 		2019-03-13 14:50:00 +05:30
api-ref/source Add progress details for recovery workflows 2019-03-08 10:52:51 +05:30
devstack Configure taskflow connection 2019-03-09 16:28:44 +09:00
doc Add progress details for recovery workflows 2019-03-08 10:52:51 +05:30
etc/masakari Add masakari-custom-recovery-methods.conf in etc/masakari 2018-08-13 08:09:42 +00:00
masakari Handle KeyError: 'progress_details' 2019-03-13 14:50:00 +05:30
playbooks/devstack Add functional CI job and tests for segments 2019-03-05 12:22:07 +05:30
releasenotes Add progress details for recovery workflows 2019-03-08 10:52:51 +05:30
roles/devstack-config/tasks Add functional CI job and tests for segments 2019-03-05 12:22:07 +05:30
.coveragerc Initial Cookiecutter Commit. 2016-06-28 13:28:27 +09:00
.gitignore Merge "Remove testrepository" 2018-12-18 06:52:22 +00:00
.gitreview Added .gitreview 2016-06-23 06:57:16 +00:00
.mailmap Initial Cookiecutter Commit. 2016-06-28 13:28:27 +09:00
.stestr.conf Switch to using stestr 2018-07-03 12:02:08 -04:00
.zuul.yaml Add functional CI job and tests for segments 2019-03-05 12:22:07 +05:30
CONTRIBUTING.rst Optimize the link address 2017-06-08 18:37:08 +07:00
HACKING.rst Register and Document policy in code 2018-07-27 12:15:14 +05:30
LICENSE Initial Cookiecutter Commit. 2016-06-28 13:28:27 +09:00
MANIFEST.in Drop MANIFEST.in - it's not needed by pbr 2016-10-13 16:55:15 +05:30
README.rst Update README 2018-11-27 05:42:04 +00:00
babel.cfg Initial Cookiecutter Commit. 2016-06-28 13:28:27 +09:00
lower-constraints.txt Add progress details for recovery workflows 2019-03-08 10:52:51 +05:30
requirements.txt Add progress details for recovery workflows 2019-03-08 10:52:51 +05:30
setup.cfg Change openstack-dev to openstack-discuss 2018-12-04 11:35:40 +08:00
setup.py Updated from global requirements 2017-04-02 01:04:58 +00:00
test-requirements.txt Add progress details for recovery workflows 2019-03-08 10:52:51 +05:30
tox.ini Add functional CI job and tests for segments 2019-03-05 12:22:07 +05:30

README.rst

Masakari

Virtual Machine High Availability (VMHA) service for OpenStack

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 manage and control the automated rescue mechanism.

NOTE: Use masakari only if instance path is configured on shared storage system i.e, 'instances_path' config option of nova has a path of shared directory otherwise instance data will be lost after the evacuation of instance from failed host if, * instance is booted from image * flavor using ephemeral disks is used

Original version of Masakari: https://github.com/ntt-sic/masakari

Tokyo Summit Session: https://www.youtube.com/watch?v=BmjNKceW_9A

Masakari is distributed under the terms of the Apache License, Version 2.0. The full terms and conditions of this license are detailed in the LICENSE file.

Configure masakari-api

  1. Create masakari user:

    openstack user create --password-prompt masakari
(give password as masakari)

  2. Add admin role to masakari user:

    openstack role add --project service --user masakari admin

  3. Create new service:

    openstack service create --name masakari --description "masakari high availability" instance-ha

  4. Create endpoint for masakari service:

    openstack endpoint create --region RegionOne masakari --publicurl http://<ip-address>:<port>/v1/%\(tenant_id\)s --adminurl http://<ip-address>:<port>/v1/%\(tenant_id\)s --internalurl http://<ip-address>:<port>/v1/%\(tenant_id\)s

  5. Clone masakari using

    git clone https://github.com/openstack/masakari.git

  6. Run setup.py from masakari

    sudo python setup.py install

  7. Create directory /etc/masakari

  8. Copy masakari.conf, api-paste.ini and policy.json file from masakari/etc/ to /etc/masakari folder

  9. To run masakari-api simply use following binary:

    masakari-api

Configure masakari database

  1. Create 'masakari' database

  2. After running setup.py for masakari (sudo python setup.py install), run masakari-manage command to sync the database

    masakari-manage db sync

Features

  • TODO