This is a pre-production deployment of Warehouse, however changes made here WILL affect the production instance of PyPI.
Latest Version Dependencies status unknown Test status unknown Test coverage unknown
Project Description

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.

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” masakari

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

  1. Create masakari directory in /etc/
  2. 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
Release History

Release History

3.0.0

This version

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

2.0.1.dev19

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.0.1

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

Supported By

WebFaction WebFaction Technical Writing Elastic Elastic Search Pingdom Pingdom Monitoring Dyn Dyn DNS Sentry Sentry Error Logging CloudAMQP CloudAMQP RabbitMQ Heroku Heroku PaaS Kabu Creative Kabu Creative UX & Design Fastly Fastly CDN DigiCert DigiCert EV Certificate Rackspace Rackspace Cloud Servers DreamHost DreamHost Log Hosting