[admin-guide-cloud] Fix links

Fix inter-book links to use :ref: instead of absolute links to the old
XML guide that do not work anymore.

Fix wrongly placed labels so that the references work.

Change-Id: I7fbf725c623d458c592eada102591346b18db5df

doc/admin-guide-cloud/source/blockstorage-manage-volumes.rst

@@ -46,9 +46,7 @@ settings for OpenStack Compute.
 
 The network mode does not interfere with OpenStack Block Storage
 operations, but you must set up networking for Block Storage to work.
-For details, see Chapter 7, Networking.
-
-.. TODO (MZ) Add ch_networking as a reference to the sentence above.
+For details, see :ref:`networking`.
 
 To set up Compute to use volumes, ensure that Block Storage is
 installed along with ``lvm2``. This guide describes how to

doc/admin-guide-cloud/source/blockstorage_volume_backups.rst

@@ -1,8 +1,8 @@
-.. _volume_backups:
-
 .. highlight: ini
    :linenothreshold: 5
 
+.. _volume_backups:
+
 ===========================
 Back up and restore volumes
 ===========================
@@ -73,8 +73,7 @@ also back up your Block Storage database regularly to ensure data recovery.
     when you back up and restore the volume.
 
     For more information about how to export and import volume backup metadata,
-    see the `section called “Export and import backup metadata”
-    <http://docs.openstack.org/admin-guide-cloud/content/volume-backup-restore-export-import.html>`__.
+    see the section called :ref:`volume_backups_export_import`.
 
 By default, the swift object store is used for the backup repository.
 

doc/admin-guide-cloud/source/blockstorage_volume_backups_export_import.rst

@@ -1,8 +1,8 @@
-.. _volume_backups_export_import:
-
 .. highlight: ini
    :linenothreshold: 5
 
+.. _volume_backups_export_import:
+
 =================================
 Export and import backup metadata
 =================================
@@ -15,10 +15,7 @@ the database used by the Block Storage service.
 .. note::
 
     For information about how to back up and restore a volume, see
-    `the section called “Back up and restore volumes”
-    <http://docs.openstack.org/admin-guide-cloud/content/volume-backup-restore.html>`__.
-
-.. TODO (zhangguoqing) I will replace the url to :ref:
+    the section called :ref:`volume_backups`.
 
 You can, however, export the metadata of a volume backup. To do so, run
 this command as an OpenStack ``admin`` user (presumably, after creating
@@ -57,7 +54,4 @@ To import backup metadata, run the following command as an OpenStack
 Where *METADATA* is the backup metadata exported earlier.
 
 Once you have imported the backup metadata into a Block Storage database,
-restore the volume (`the section called “Back up and restore volumes”
-<http://docs.openstack.org/admin-guide-cloud/content/volume-backup-restore.html>`__).
-
-.. TODO (zhangguoqing) I will replace the url to :ref:
+restore the volume (see the section called :ref:`volume_backups`).

doc/admin-guide-cloud/source/telemetry-best-practices.rst

@@ -29,8 +29,8 @@ Data collection
 
       .. note::
 
-         For more information, see the `Pipeline Configuration
-         Options <http://docs.openstack.org/admin-guide-cloud/content/section_telemetry-pipeline-configuration.html>`__.
+         For more information, see the
+         :ref:`telemetry-pipeline-configuration`.
 
 #. If you are using the Kilo version of Telemetry, you can delay or adjust
    polling requests by enabling the jitter support. This adds a random
@@ -46,8 +46,7 @@ Data collection
 
    .. note::
 
-      For more information see, `HA deployment for Central and Compute Agents
-      <http://docs.openstack.org/admin-guide-cloud/content/section_telemetry-central-compute-agent-ha.html>`__.
+      For more information see, :ref:`ha-deploy-services`.
 
 #. If you are using Juno or later releases, use the ``notifier://``
    publisher rather than ``rpc://`` as there is a certain level of overhead
@@ -99,9 +98,7 @@ Data storage
    .. note::
 
       For more information on how to set the TTL, see
-      `TTL support for various back ends
-      <http://docs.openstack.org/admin-guide-cloud/content/
-      section_telemetry-storing-data.html>`__.
+      :ref:`telemetry-storing-samples`.
 
 #. We recommend that you do not use SQLAlchemy back end prior to the Juno
    release, as it previously contained extraneous relationships to handle