openstack
/
ha-guide
Code Issues Proposed changes

Adjust URLs for admin-guide-cloud RST 

Replace old URLs with current ones.

Change-Id: I85337ca918116698ffa81e5cbd2202783bd8657a
This commit is contained in:
Andreas Jaeger 2015-08-23 08:59:13 +02:00
parent f4c03f3afe
commit 2d29a8d229
7 changed files with 10 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
doc/ha-guide/source/controller-ha-telemetry.rst
View File

@ -67,8 +67,9 @@ in the OpenStack Configuration Reference.
otherwise samples may be missing or duplicated. The list of meters to poll
can be set in the :file:`/etc/ceilometer/pipeline.yaml` configuration file.
For more information about pipelines see the `Data collection and
processing <http://docs.openstack.org/admin-guide-cloud/content/
section_telemetry-data-collection-processing.html>`__ section.
processing
<http://docs.openstack.org/admin-guide-cloud/telemetry-data-collection.html#data-collection-and-processing>`__
section.
To enable the compute agent to run multiple instances simultaneously with
workload partitioning, the workload_partitioning option has to be set to

2
doc/ha-guide/source/install-ha-memcached.rst
View File

@ -40,6 +40,6 @@ if the host goes down, `controller2` does the job.
For more information about memcached installation,
see the
`OpenStack Cloud Administrator Guide
<http://docs.openstack.org/admin-guide-cloud/content/>`_.
<http://docs.openstack.org/admin-guide-cloud/>`_.

2
doc/ha-guide/source/storage-ha-backend.rst
View File

@ -77,7 +77,7 @@ or even the failure of the data center itself.
When Ceph RBD is used for ephemeral volumes
as well as block and image storage, it supports
`live migration
<http://docs.openstack.org/admin-guide-cloud/content/section_live-migration-usage.html>`_
<http://docs.openstack.org/admin-guide-cloud/compute-live-migration-usage.html>`_
of VMs with ephemeral drives;
LVM only supports live migration of volume-backed VMs.

2
doc/high-availability-guide/ha_aa_controllers/section_memcached.xml
View File

@ -23,6 +23,6 @@
<para>By default, <literal>controller1</literal> handles the caching service
but if the host goes down, <literal>controller2</literal> does the job. For
more information about <application>Memcached</application> installation,
see the <link xlink:href="http://docs.openstack.org/admin-guide-cloud/content/">
see the <link xlink:href="http://docs.openstack.org/admin-guide-cloud/">
OpenStack Cloud Administrator Guide</link>.</para>
</section>

2
doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml
View File

@ -67,7 +67,7 @@
<title>Telemetry Central agent</title>
<para>The Telemetry Central agent can be configured to partition its
polling workload between multiple agents, enabling high availability.
Please refer to <link xlink:href="http://docs.openstack.org/admin-guide-cloud/content/section_telemetry-cetral-compute-agent-ha.html">
Please refer to <link xlink:href="http://docs.openstack.org/admin-guide-cloud/telemetry-data-collection.html#support-for-ha-deployment-of-the-central-and-compute-agent-services">
this section</link> of the <citetitle>OpenStack Cloud Administrator Guide</citetitle>
for the requirements and implementation details of this configuration.</para>
</section>

2
doc/high-availability-guide/network/section_highly_available_neutron_dhcp_agent.xml
View File

@ -11,7 +11,7 @@ default). High availability for the DHCP agent is achieved by adopting
Pacemaker.</para>
<note>
<para>Here is the <link
xlink:href="http://docs.openstack.org/admin-guide-cloud/content/app_demo_multi_dhcp_agents.html">documentation</link> for installing neutron DHCP agent.</para>
xlink:href="http://docs.openstack.org/admin-guide-cloud/networking_multi-dhcp-agents.html">documentation</link> for installing neutron DHCP agent.</para>
</note>
<section xml:id="_add_neutron_dhcp_agent_resource_to_pacemaker">

3
doc/high-availability-guide/network/section_highly_available_neutron_l3_agent.xml
View File

@ -10,7 +10,8 @@
for VMs on tenant networks. High availability for the L3 agent is achieved by
adopting Pacemaker.</para>
<note>
<para>Here is the <link xlink:href="http://docs.openstack.org/admin-guide-cloud/content/install_neutron-l3.html">documentation</link> for installing neutron L3 agent.</para>
<para>Here is the <link xlink:href="http://docs.openstack.org/admin-guide-cloud/networking_config-agents.html#configure-l3-agent">documentation</link>
for installing neutron L3 agent.</para>
</note>
<section xml:id="_add_neutron_l3_agent_resource_to_pacemaker">