Christian Berendt c3d8262ec5 Add doc8 test and improve rst syntax
This will test all rst files inside the doc directory for style issues with
doc8 (an opinionated style checker for rst styles of documentation).

This will fix all syntax issues identified by doc8 and will improve
the syntax.

Change-Id: Id1b9563e07e77e306aef5a0767c98c27f87c5c0e
2016-08-04 15:09:10 +02:00

3.7 KiB

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.

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


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 is the IP address of the machine where the registry is currently running:

# CentOS

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

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:

# Ubuntu
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 stop docker
systemctl start docker

# Ubuntu with upstart or sysvinit
sudo service docker restart

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.
# These hostname must be resolvable from your deployment host

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:




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 deploying-kolla.

Run the deployment:

kolla-ansible deploy -i <path/to/multinode/inventory/file>