f6e9c8e693
It was pointed out that the MountFlags=shared entry was missing for Ubuntu in the multinode deployment guide. The entry has been added back in. Change-Id: I164932848eeaec3963fa205d4493a3b7f2343dfd Closes-Bug: #1640618
146 lines
3.9 KiB
ReStructuredText
146 lines
3.9 KiB
ReStructuredText
.. _multinode:
|
|
|
|
=============================
|
|
Multinode Deployment of Kolla
|
|
=============================
|
|
|
|
Deploy a registry (required for multinode)
|
|
==========================================
|
|
|
|
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 a registry is required.
|
|
|
|
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 greater than 2.3, do the following:
|
|
|
|
::
|
|
|
|
docker run -d -p 4000:5000 --restart=always --name registry registry:2
|
|
|
|
.. note:: Kolla looks for the Docker registry to use port 4000. (Docker default is
|
|
port 5000)
|
|
|
|
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:4000"
|
|
|
|
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:4000"
|
|
|
|
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`` or if kolla was installed with pip,
|
|
it 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>
|