openstack/openstack-manuals
Code Issues Proposed changes

[ha-guide] Add info about instance HA

Browse Source 
Change-Id: I4b986c2e18051e0c62d37c1770a936fd7bd29e2e
This commit is contained in:
Dawid Deja 2016-08-24 16:48:36 +02:00 committed by Adam Spiers
parent 6b166dcf80
commit ffc2057087
2 changed files with 47 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/ha-guide/source/compute-node-ha.rst
View File

@ -7,4 +7,4 @@ Configuring the compute node for high availability
:maxdepth: 2
compute-node-ha-api.rst
instance-ha.rst

46
doc/ha-guide/source/instance-ha.rst Normal file
View File

@ -0,0 +1,46 @@
========================================
Configure high availability of instances
========================================
As of September 2016, the OpenStack High Availability community is
designing and developing an official and unified way to provide high
availability for instances. That is, we are developing automatic
recovery from failures of hardware or hypervisor-related software on
the compute node, or other failures which could prevent instances from
functioning correctly - issues with a cinder volume I/O path, for example.
More details are available in the `user story
<http://specs.openstack.org/openstack/openstack-user-stories/user-stories/proposed/ha_vm.html>`_
co-authored by OpenStack's HA community and `Product Working Group
<https://wiki.openstack.org/wiki/ProductTeam>`_ (PWG), who have
identified this feature as missing functionality in OpenStack which
should be addressed with high priority.
Existing solutions
------------------
The architectural challenges of instance HA and several currently
existing solutions were presented in `a talk at the Austin summit
<https://www.openstack.org/videos/video/high-availability-for-pets-and-hypervisors-state-of-the-nation>`_,
for which `slides are also available
<http://aspiers.github.io/openstack-summit-2016-austin-compute-ha/>`_.
The code for three of these solutions can be found online:
* `a mistral-based auto-recovery workflow
<https://github.com/gryf/mistral-evacuate>`_, by Intel
* `masakari <https://launchpad.net/masakari>`_, by NTT
* `OCF RAs
<http://aspiers.github.io/openstack-summit-2016-austin-compute-ha/#/ocf-pros-cons>`_,
as used by Red Hat and SUSE
Current upstream work
---------------------
Work is in progress on a unified approach, which combines the best
aspects of existing upstream solutions. More details are available on
`the HA VMs user story wiki
<https://wiki.openstack.org/wiki/ProductTeam/User_Stories/HA_VMs>`_.
To get involved with this work, please see the section on the
:doc:`ha-community`.