From 8afded3f3cd92ca6e8c29fe566dfb9d4441d5a87 Mon Sep 17 00:00:00 2001 From: Shilla Saebi Date: Sat, 6 Sep 2014 15:02:29 -0400 Subject: [PATCH] changes to ch_intro.xml in high availability guide MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit remove , and since it’s listed added “an” uptime of Change-Id: I055baf97df6719321ecac9e33e7a43ca17a2cdfa --- doc/high-availability-guide/ch_intro.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/high-availability-guide/ch_intro.xml b/doc/high-availability-guide/ch_intro.xml index 7e6f65c636..4e60f5f3c0 100644 --- a/doc/high-availability-guide/ch_intro.xml +++ b/doc/high-availability-guide/ch_intro.xml @@ -10,7 +10,7 @@ High Availability systems seek to minimize two things: - System downtime — occurs when a user-facing service is unavailable beyond a specified maximum amount of time, and + System downtime — occurs when a user-facing service is unavailable beyond a specified maximum amount of time. @@ -43,7 +43,7 @@ Facility services such as power, air conditioning, and fire protection Most high availability systems will fail in the event of multiple independent (non-consequential) failures. In this case, most systems will protect data over maintaining availability. - High-availability systems typically achieve uptime of 99.99% or more, which roughly equates to less than an hour of cumulative downtime per year. In order to achieve this, high availability systems should keep recovery times after a failure to about one to two minutes, sometimes significantly less. + High-availability systems typically achieve an uptime percentage of 99.99% or more, which roughly equates to less than an hour of cumulative downtime per year. In order to achieve this, high availability systems should keep recovery times after a failure to about one to two minutes, sometimes significantly less. OpenStack currently meets such availability requirements for its own infrastructure services, meaning that an uptime of 99.99% is feasible for the OpenStack infrastructure proper. However, OpenStack does not guarantee 99.99% availability for individual guest instances. Preventing single points of failure can depend on whether or not a service is stateless.