x/development-proposals
Code Issues Proposed changes

Merge "be more precise about failure events"

Browse Source
This commit is contained in:
Jenkins
2016-06-09 20:01:48 +00:00
committed by Gerrit Code Review
parent 887e35dd5d e8b6d26043
commit 4e8fc3f6cc
1 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
user-stories/proposed/ha_vm.rst
View File

@@ -52,11 +52,11 @@ can be detected and recovered by the system. Possible failure events include:
* ``nova-compute`` service crashes or becomes unresponsive.
* Compute host is down.
* Compute host crashes or hangs.
* Hypervisor has failed (e.g. libvirtd process is dead or unresponsive).
* Hypervisor fails, e.g. libvirtd process dies or becomes unresponsive.
* Network is down
* Network component fails.
There are many ways a network component could fail, e.g. NIC
configuration error, NIC driver failure, NIC hardware failure, cable
@@ -91,11 +91,11 @@ The goal of the user story is to reduce that interruption via automated recovery
Usage Scenario Examples
+++++++++++++++++++++++
* VM is down
* Recovery from VM failure
Monitor the VM. Detect VM down failure and notify system to recover the VM.
* VM provisioning process is down
* Recovery from ``nova-compute`` failure
Monitor the provisioning process (nova-compute service). Detect
process failure and notify system to restart the service.
@@ -107,7 +107,7 @@ Usage Scenario Examples
the hosts must be fenced to prevent two instances writing to the same shared
storage that lead to data corruption.
* Hypervisor host is down
* Recovery from hypervisor host failure
Monitor the hypervisor host. When failure is detected, resurrect
all VMs from the failed host onto new hosts that enable an