Fix quickstart links

Checking http://files.openstack.org/docs-404s/2017-09-08.txt the link
/kolla-ansible/latest/quickstart.html gives a 404 and is most wanted.

The link now is /kolla-ansible/latest/user/quickstart.html - let's
update in tree docs for this.

Fix other broken links as well - with using intra-links instead of
external links - this will make it easier to notice breakage when files
are moved.

Change-Id: I62655afd9f270fa83c07d86aa91346af6337ca32

README.rst

@@ -35,7 +35,7 @@ Learn about Kolla-Ansible by reading the documentation online
 `docs.openstack.org <https://docs.openstack.org/kolla-ansible/latest/>`__.
 
 Get started by reading the `Developer
-Quickstart <https://docs.openstack.org/kolla-ansible/latest/quickstart.html>`__.
+Quickstart <https://docs.openstack.org/kolla-ansible/latest/user/quickstart.html>`__.
 
 OpenStack services
 ------------------

doc/source/contributor/CONTRIBUTING.rst

@@ -30,11 +30,9 @@ Basics
 Development Environment
 =======================
 
-Please follow our `quickstart`_ to deploy your environment and test your
+Please follow our :doc:`/user/quickstart` to deploy your environment and test your
 changes.
 
-.. _quickstart: https://docs.openstack.org/kolla-ansible/latest/quickstart.html
-
 Please use the existing sandbox repository, available at
 https://git.openstack.org/cgit/openstack-dev/sandbox, for learning, understanding
 and testing the `Gerrit Workflow`_.

doc/source/reference/bifrost.rst

@@ -166,7 +166,7 @@ group.  In the ``all-in-one`` and ``multinode`` inventory files, a ``bifrost``
 group is defined which contains all hosts in the ``deployment`` group.  This
 top level ``deployment`` group is intended to represent the host running the
 ``bifrost_deploy`` container.  By default, this group contains ``localhost``.
-See `Multinode Deployment of Kolla <https://docs.openstack.org/kolla-ansible/latest/multinode.html>`_
+See :doc:`/user/multinode`
 for details on how to modify the Ansible inventory in a multinode deployment.
 
 Bifrost does not currently support running on multiple hosts so the ``bifrost``

doc/source/reference/manila-guide.rst

@@ -306,8 +306,7 @@ Modify the file ``/etc/kolla/config/manila.conf`` and add the contents:
 .. note::
 
     Share migration requires have more than one back end configured.
-    `Configure multiple back ends
+    For details, see :ref:`hnas_configure_multiple_back_ends`.
-    <https://docs.openstack.org/kolla-ansible/latest/manila-hnas-guide.html#configure-multiple-back-ends>`__.
 
 Use the manila migration command, as shown in the following example:
 

doc/source/reference/manila-hnas-guide.rst

@@ -265,6 +265,8 @@ Verify Operation
     | metadata                    | {}                                                              |
     +-----------------------------+-----------------------------------------------------------------+
 
+.. _hnas_configure_multiple_back_ends:
+
 Configure multiple back ends
 ============================
 

doc/source/reference/zun-guide.rst

@@ -9,7 +9,7 @@ Preparation and Deployment
 --------------------------
 
 Zun requires kuryr and etcd services, for more information about how to
-configure kuryr refer to `Kuryr Guide <https://docs.openstack.org/kolla-ansible/latest/kuryr-guide.html>`_.
+configure kuryr refer to :doc:`kuryr-guide`.
 
 To allow Zun Compute connect to the Docker Daemon, add the following in the
 ``docker.service`` file on each zun-compute node.

doc/source/user/quickstart.rst

@@ -29,7 +29,7 @@ bare metal or a virtual machine with Kolla.
 
 If developing Kolla on a system that provides VirtualBox or Libvirt in addition
 to Vagrant, use the Vagrant virtual environment documented in
-`Development Environment with Vagrant <https://docs.openstack.org/kolla-ansible/latest/vagrant-dev-env.html>`_.
+:doc:`/contributor/vagrant-dev-env`.
 
 Prerequisites
 =============