Bridge between container framework networking and storage models to OpenStack networking and storage abstractions.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Dongcan Ye d4e71a3794 Add unit tests for nested binding driver 2 years ago
contrib/busybox Base busybox container for tests 2 years ago
doc Delete and move outdated docs 2 years ago
etc Refactoring: Drop all the code except common one 2 years ago
kuryr Add unit tests for nested binding driver 2 years ago
releasenotes Add reno support to kuryr 2 years ago
tools All kuryr-lib CI failed since kuryr-lib add in upper-constraints.txt 2 years ago
usr/libexec/kuryr kuryr bind port error with neutron linux bridge driver 2 years ago
.coveragerc tox: fix coverage call 2 years ago
.gitignore Merge "Add reno support to kuryr" 2 years ago
.gitreview Added .gitreview 3 years ago
.testr.conf Separate unit tests from fullstack tests 3 years ago
CONTRIBUTING.rst Initial template commit 3 years ago
HACKING.rst Initial template commit 3 years ago
LICENSE Initial template commit 3 years ago
MANIFEST.in Remove 'MANIFEST.in' 3 years ago
README.rst Show team and repo badges on README 2 years ago
__init__.py Removes unnecessary utf-8 encoding 2 years ago
babel.cfg Initial template commit 3 years ago
requirements.txt Updated from global requirements 2 years ago
setup.cfg Remove support for py34 2 years ago
setup.py Updated from global requirements 3 years ago
test-requirements.txt Updated from global requirements 2 years ago
tox.ini Pass located tests directory in oslo debug 2 years ago

README.rst

Team and repository tags

image

kuryr

Kuryr mascot

Docker for OpenStack Neutron

Kuryr is a Docker network plugin that uses Neutron to provide networking services to Docker containers. It provides containerised images for the common Neutron plugins.

Features

  • TODO

Getting Code

$ git clone https://git.openstack.org/openstack/kuryr.git
$ cd kuryr

Prerequisites

$ sudo pip install -r requirements.txt

Installing Kuryr's libnetwork driver

For kuryr-libnetwork driver installation refer:

http://docs.openstack.org/developer/kuryr-libnetwork/readme.html

Configuring Kuryr

Generate sample config, etc/kuryr.conf.sample, running the following

$ tox -e genconfig

Rename and copy config file at required path

$ cp etc/kuryr.conf.sample /etc/kuryr/kuryr.conf

Edit keystone section in /etc/kuryr/kuryr.conf, replace ADMIN_PASSWORD:

auth_uri = http://127.0.0.1:35357/v2.0
admin_user = admin
admin_tenant_name = service
admin_password = ADMIN_PASSWORD

In the same file uncomment the bindir parameter with the path for the Kuryr vif binding executables:

bindir = /usr/local/libexec/kuryr

By default, Kuryr will use veth pairs for performing the binding. However, the Kuryr library ships with two other drivers that you can configure in the binding section:

[binding]
#driver = kuryr.lib.binding.drivers.ipvlan
#driver = kuryr.lib.binding.drivers.macvlan

Drivers may make use of other binding options. Both Kuryr library drivers in the previous snippet can be further configured setting the interface that will act as link interface for the virtual devices:

link_iface = enp4s0

Running Kuryr

Currently, Kuryr utilizes a bash script to start the service. Make sure that you have installed tox before the execution of the below command.

$ sudo ./scripts/run_kuryr.sh

After the booting, please restart your Docker service, e.g.,

$ sudo service docker restart

The bash script creates the following file if it is missing.

  • /usr/lib/docker/plugins/kuryr/kuryr.json: Json spec file for libnetwork.

Note the root privilege is required for creating and deleting the veth pairs with pyroute2 to run.

Testing Kuryr

For a quick check that Kuryr is working create a network:

$ docker network create --driver kuryr test_net
785f8c1b5ae480c4ebcb54c1c48ab875754e4680d915b270279e4f6a1aa52283
$ docker network ls
NETWORK ID          NAME                DRIVER
785f8c1b5ae4        test_net            kuryr

To test it with tox:

$ tox

You can also run specific test cases using the -e flag, e.g., to only run the fullstack test case.

$ tox -e fullstack

Generating Documentation

We use Sphinx to maintain the documentation. You can install Sphinx using pip.

$ pip install -U Sphinx

In addition to Sphinx you will also need the following requirements (not covered by requirements.txt):

$ pip install oslosphinx reno 'reno[sphinx]'

The source code of the documentation are under doc, you can generate the html files using the following command. If the generation succeeds,a build/html dir will be created under doc.

$ cd doc
$ make html

Now you can serve the documentation at http://localhost:8080 as a simple website.

$ cd build/html
$ python -m SimpleHTTPServer 8080