clarify that 100% availability is out of scope
100% availability is sometimes described as "Fault Tolerance". That's much harder to achieve, however, so it's not the goal of this user story. Change-Id: I01c1a225051d0a8ffc1c75498d6175eae6fddf74 Signed-off-by: Adam Spiers <aspiers@suse.com>
This commit is contained in:
committed by
Yih Leong Sun
parent
688b7093a8
commit
56b0e36a8c
@@ -50,6 +50,9 @@ can be detected and recovered by the system. Possible failure events include:
|
||||
|
||||
* Availability Zone/Data Center/Region failure
|
||||
|
||||
N.B. This user story concerns high availability, not 100% availability.
|
||||
Therefore some service interruption is usually expected when failures occur.
|
||||
The goal of the user story is to reduce that interruption via automated recovery.
|
||||
|
||||
Usage Scenario Examples
|
||||
+++++++++++++++++++++++
|
||||
|
||||
Reference in New Issue
Block a user