summaryrefslogtreecommitdiffstats
path: root/requirements
diff options
context:
space:
mode:
authorRyota Mibu <r-mibu@cq.jp.nec.com>2015-11-25 13:29:49 +0000
committerGerrit Code Review <gerrit@172.30.200.206>2015-11-25 13:29:49 +0000
commitc2f8523fe12c93813b8e459d093f0111c9dc1f31 (patch)
tree3efa03e67e1eb148c88ce66d9bfdb7a8349051e9 /requirements
parentdb992d5fed0acf2b80a5a62f8e6bc4277489cd8c (diff)
parent236143f29b63205a6e3271bab553de448d9dfe1d (diff)
Merge "Fencing requirement."
Diffstat (limited to 'requirements')
-rw-r--r--requirements/03-architecture.rst15
1 files changed, 12 insertions, 3 deletions
diff --git a/requirements/03-architecture.rst b/requirements/03-architecture.rst
index 14055485..9b618e01 100644
--- a/requirements/03-architecture.rst
+++ b/requirements/03-architecture.rst
@@ -183,9 +183,18 @@ Without fencing -- when the perceived disconnection is due to some transient
or partial failure -- the evacuation might lead into two identical instances
running together and having a dangerous conflict.
-There is a cross-project effort in OpenStack ongoing to implement fencing. A
-general description of fencing in OpenStack is available here:
-https://wiki.openstack.org/wiki/Fencing_Instances_of_an_Unreachable_Host .
+There is a cross-project definition in OpenStack of how to implement
+fencing, but there has not been any progress. The general description is
+available here:
+https://wiki.openstack.org/wiki/Fencing_Instances_of_an_Unreachable_Host
+
+As OpenStack does not cover fencing it is in the responsibility of the Doctor
+project to make sure fencing is done by using tools like pacemaker and by
+calling OpenStack APIs. Only after fencing is done OpenStack resources can be
+marked as down. In case there are gaps in OpenStack projects to have all
+relevant resources marked as down, those gaps need to be identified and fixed.
+The Doctor Inspector component will be responsible of marking resources down in
+the OpenStack and back up if necessary.
Recovery Action
^^^^^^^^^^^^^^^