dbf754655f
For compliance with the Project Testing Interface [1] as described in [2] [1] https://governance.openstack.org/tc/reference/project-testing-interface.html [2] http://lists.openstack.org/pipermail/openstack-dev/2017-December/125710.html doc8 command is dropped from docs tox envs. So this affect nothing and run in PEP8. Related-Bug: #1765348 Depends-On: Icc7fe3a8f9716281de88825e9d5b2fd84de3d00a Change-Id: Idf9a16111479ccc64004eac9508da575822a3df5
1.7 KiB
Kuryr in Kolla
"Kuryr is a Docker network plugin that uses Neutron to provide networking services to Docker containers. It provides containerized images for the common Neutron plugins. Kuryr requires at least Keystone and neutron. Kolla makes kuryr deployment faster and accessible.
Requirements
- A minimum of 3 hosts for a vanilla deploy
Preparation and Deployment
To allow Docker daemon connect to the etcd, add the following in the
docker.service file.
ExecStart= -H tcp://172.16.1.13:2375 -H unix:///var/run/docker.sock --cluster-store=etcd://172.16.1.13:2379 --cluster-advertise=172.16.1.13:2375The IP address is host running the etcd service.
`2375 is port that allows Docker
daemon to be accessed remotely. 2379` is the etcd
listening port.
By default etcd and kuryr are disabled in the
group_vars/all.yml. In order to enable them, you need to
edit the file globals.yml and set the following variables
enable_etcd: "yes"
enable_kuryr: "yes"Deploy the OpenStack cloud and kuryr network plugin
kolla-ansible deployCreate a Virtual Network
docker network create -d kuryr --ipam-driver=kuryr --subnet=10.1.0.0/24 --gateway=10.1.0.1 docker-net1To list the created network:
docker network lsThe created network is also available from OpenStack CLI:
openstack network listFor more information about how kuryr works, see kuryr (OpenStack Containers Networking).