From 87d6d3e198f46a6742f903ba40d9c37549a5a173 Mon Sep 17 00:00:00 2001
From: Andreas Jaeger <aj@suse.de>
Date: Wed, 14 Oct 2015 09:31:08 +0200
Subject: [PATCH] Update links for HA Guide

The HA Guide has been moved, update links.

Change-Id: I77425c175e7638b48f3b9935bf8c600ae9ec54b8
---
 doc/openstack-ops/ch_ops_advanced_configuration.xml | 2 +-
 doc/openstack-ops/ch_ops_backup_recovery.xml        | 2 +-
 doc/openstack-ops/ch_ops_maintenance.xml            | 2 +-
 doc/openstack-ops/preface_ops.xml                   | 2 +-
 4 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/doc/openstack-ops/ch_ops_advanced_configuration.xml b/doc/openstack-ops/ch_ops_advanced_configuration.xml
index 40b54812..338907fb 100644
--- a/doc/openstack-ops/ch_ops_advanced_configuration.xml
+++ b/doc/openstack-ops/ch_ops_advanced_configuration.xml
@@ -195,7 +195,7 @@
       <title>High Availability</title>
 
       <para>The <emphasis><link
-      xlink:href="http://docs.openstack.org/high-availability-guide/content/">OpenStack High Availability
+      xlink:href="http://docs.openstack.org/ha-guide/index.html">OpenStack High Availability
       Guide</link></emphasis> offers suggestions for elimination of a single
       point of failure that could cause system downtime. While it is not a
       completely prescriptive document, it offers methods and techniques for
diff --git a/doc/openstack-ops/ch_ops_backup_recovery.xml b/doc/openstack-ops/ch_ops_backup_recovery.xml
index 817e1ebb..42f8ae29 100644
--- a/doc/openstack-ops/ch_ops_backup_recovery.xml
+++ b/doc/openstack-ops/ch_ops_backup_recovery.xml
@@ -23,7 +23,7 @@
   <note>
     <para>If you cannot have any data loss at all, you should also focus on a
     highly available deployment. The <emphasis><link
-    xlink:href="http://docs.openstack.org/high-availability-guide/content/">OpenStack High Availability
+    xlink:href="http://docs.openstack.org/ha-guide/index.html">OpenStack High Availability
     Guide</link></emphasis> offers suggestions for elimination of a single
     point of failure that could cause system downtime. While it is not a
     completely prescriptive document, it offers methods and techniques for
diff --git a/doc/openstack-ops/ch_ops_maintenance.xml b/doc/openstack-ops/ch_ops_maintenance.xml
index 54db7050..6cfa6c12 100644
--- a/doc/openstack-ops/ch_ops_maintenance.xml
+++ b/doc/openstack-ops/ch_ops_maintenance.xml
@@ -144,7 +144,7 @@
       <para>To avoid this situation, create a highly available cloud
       controller cluster. This is outside the scope of this document, but you
       can read more in the draft <link
-      xlink:href="http://docs.openstack.org/high-availability-guide/content/ch-intro.html">OpenStack High Availability
+      xlink:href="http://docs.openstack.org/ha-guide/index.html">OpenStack High Availability
       Guide</link>.</para>
 
       <para>The next best approach is to use a configuration-management tool,
diff --git a/doc/openstack-ops/preface_ops.xml b/doc/openstack-ops/preface_ops.xml
index adeb7b45..b4d4d405 100644
--- a/doc/openstack-ops/preface_ops.xml
+++ b/doc/openstack-ops/preface_ops.xml
@@ -208,7 +208,7 @@
         </varlistentry>
 
         <varlistentry>
-          <term><link xlink:href="http://docs.openstack.org/high-availability-guide/content/index.html">OpenStack
+          <term><link xlink:href="http://docs.openstack.org/ha-guide/index.html">OpenStack
               High Availability Guide</link></term>
 
           <listitem>