Remove all kolla-ansible related docs

The goal of this patch is to reduce the docs hosted for this repo down
to just the container images.

Hyperlinks are provided to each of the available deployment mechanisms,
currently kolla-ansible and kolla-kubernetes.

This is to cut down confusion on which doc patches go where, as well as
the massive duplication we currently have between kolla and
kolla-ansible documentation. Further improvements could involve breaking
out the 'Building Container Images' section into separate pages, e.g.
quickstart, customisation, advanced, etc.

Change-Id: Ia7959c71a241b9d7139ec50b34e36b24fbcf76e6

1 files changed, 0 insertions, 157 deletions

diff --git a/doc/multinode.rst b/doc/multinode.rst
deleted file mode 100644
index b88a248ff..000000000
--- a/doc/multinode.rst
+++ /dev/null
@@ -1,157 +0,0 @@
-.. _multinode:
-
-=============================
-Multinode Deployment of Kolla
-=============================
-
-.. _deploy_a_registry:
-
-Deploy a registry
-=================
-
-A Docker registry is a locally hosted registry that replaces the need to pull
-from the Docker Hub to get images. Kolla can function with or without a local
-registry, however for a multinode deployment some type of registry is mandatory.
-Only one registry must be deployed, although HA features exist for registry
-services.
-
-The Docker registry prior to version 2.3 has extremely bad performance because
-all container data is pushed for every image rather than taking advantage of
-Docker layering to optimize push operations. For more information reference
-`pokey registry <https://github.com/docker/docker/issues/14018>`__.
-
-The Kolla community recommends using registry 2.3 or later. To deploy registry
-with version 2.3 or later, do the following:
-
-::
-
-    tools/start-registry
-
-.. _configure_docker_all_nodes:
-
-Configure Docker on all nodes
-=============================
-
-.. note:: As the subtitle for this section implies, these steps should be
-          applied to all nodes, not just the deployment node.
-
-The ``start-registry`` script configures a docker registry that proxies Kolla
-images from Docker Hub, and can also be used with custom built images (see
-:doc:`image-building`).
-
-After starting the registry, it is necessary to instruct Docker that it will
-be communicating with an insecure registry. To enable insecure registry
-communication on CentOS, modify the ``/etc/sysconfig/docker`` file to contain
-the following where 192.168.1.100 is the IP address of the machine where the
-registry is currently running:
-
-::
-
-    # CentOS
-    INSECURE_REGISTRY="--insecure-registry 192.168.1.100:5000"
-
-For Ubuntu, check whether its using upstart or systemd.
-
-::
-
-    # stat /proc/1/exe
-    File: '/proc/1/exe' -> '/lib/systemd/systemd'
-
-Edit ``/etc/default/docker`` and add:
-
-::
-
-    # Ubuntu
-    DOCKER_OPTS="--insecure-registry 192.168.1.100:5000"
-
-If Ubuntu is using systemd, additional settings needs to be configured.
-Copy Docker's systemd unit file to ``/etc/systemd/system/`` directory:
-
-::
-
-    cp /lib/systemd/system/docker.service /etc/systemd/system/docker.service
-
-Next, modify ``/etc/systemd/system/docker.service``, add ``environmentFile``
-variable and add ``$DOCKER_OPTS`` to the end of ExecStart in ``[Service]``
-section:
-
-::
-
-    # CentOS
-    [Service]
-    MountFlags=shared
-    EnvironmentFile=/etc/sysconfig/docker
-    ExecStart=/usr/bin/docker daemon $INSECURE_REGISTRY
-
-    # Ubuntu
-    [Service]
-    MountFlags=shared
-    EnvironmentFile=-/etc/default/docker
-    ExecStart=/usr/bin/docker daemon -H fd:// $DOCKER_OPTS
-
-Restart Docker by executing the following commands:
-
-::
-
-    # CentOS or Ubuntu with systemd
-    systemctl daemon-reload
-    systemctl restart docker
-
-    # Ubuntu with upstart or sysvinit
-    sudo service docker restart
-
-.. _edit-inventory:
-
-Edit the Inventory File
-=======================
-
-The ansible inventory file contains all the information needed to determine
-what services will land on which hosts. Edit the inventory file in the kolla
-directory ``ansible/inventory/multinode``. If kolla was installed with pip,
-the inventory file can be found in ``/usr/share/kolla``.
-
-Add the ip addresses or hostnames to a group and the services associated with
-that group will land on that host:
-
-::
-
-   # These initial groups are the only groups required to be modified. The
-   # additional groups are for more control of the environment.
-   [control]
-   # These hostname must be resolvable from your deployment host
-   control01
-   192.168.122.24
-
-
-For more advanced roles, the operator can edit which services will be
-associated in with each group. Keep in mind that some services have to be
-grouped together and changing these around can break your deployment:
-
-::
-
-   [kibana:children]
-   control
-
-   [elasticsearch:children]
-   control
-
-   [haproxy:children]
-   network
-
-Deploying Kolla
-===============
-
-First, check that the deployment targets are in a state where Kolla may deploy
-to them:
-
-::
-
-    kolla-ansible prechecks -i <path/to/multinode/inventory/file>
-
-For additional environment setup see the :ref:`deploying-kolla`.
-
-Run the deployment:
-
-::
-
-    kolla-ansible deploy -i <path/to/multinode/inventory/file>