RETIRED, Kubernetes integration with OpenStack networking
Go to file
Michał Dulko 2f65d993f3 CNI split - introducing CNI daemon
This commit implements basic CNI daemon service. The aim of this new
entity is to increase scalability of CNI operations by moving watching
for VIF to a separate process.

This commit:
* Introduces kuryr-daemon service
* Implements communication between CNI driver and CNI daemon using HTTP
* Consolidates watching for VIF on CNI side to a single Watcher that
  looks for all the pods on the node it is running on.
* Solves bug 1731485 when running with CNI daemon.
* Enables new service in DevStack plugin
* Provides unit tests for new code.

Follow up patches will include:
- Documentation.
- Support for running in containerized mode.

To test the patch add `enable_service kuryr-daemon` to your DevStack's
local.conf file.

Partial-Bug: 1731485
Co-Authored-By: Janonymous <janonymous.codevulture@gmail.com>
Implements: blueprint cni-split-exec-daemon
Change-Id: I1bd6406dacab0735a94474e146645c63d933be16
2017-11-21 08:50:04 +01:00
contrib Add list and show pool commands to Pool Manager 2017-10-10 10:36:10 +00:00
devstack CNI split - introducing CNI daemon 2017-11-21 08:50:04 +01:00
doc Add readiness probe to kuryr-controller pod 2017-11-14 12:03:15 +01:00
etc Remove 99-loopback.conf 2017-10-09 15:32:20 +02:00
hooks Add support to install Kuryr as a network addon 2017-09-14 13:33:53 +02:00
kuryr_kubernetes CNI split - introducing CNI daemon 2017-11-21 08:50:04 +01:00
playbooks Merge "Enable Neutron Metadata Agent in Tempest jobs" 2017-11-06 19:46:17 +00:00
scripts Controller service base 2016-10-04 21:56:50 +03:00
tools Add readiness probe to kuryr-controller pod 2017-11-14 12:03:15 +01:00
.coveragerc tox: fix coverage 2016-11-18 10:14:56 +03:00
.dockerignore Add support to install Kuryr as a network addon 2017-09-14 13:33:53 +02:00
.gitignore Add support to install Kuryr as a network addon 2017-09-14 13:33:53 +02:00
.gitreview Added .gitreview 2016-05-12 09:14:08 +00:00
.testr.conf cookiecutter commit for kuryr-kubernetes 2016-05-22 08:54:07 +03:00
.zuul.yaml Zuul: add file extension to playbook path 2017-10-29 13:03:18 -07:00
babel.cfg cookiecutter commit for kuryr-kubernetes 2016-05-22 08:54:07 +03:00
cni_builder CNI container: parametrize and clean up 2017-09-14 13:33:53 +02:00
cni_builder.Dockerfile Clean up ENV vars mistmatches in Dockerfiles 2017-09-20 10:35:36 +02:00
cni_ds_init Remove 99-loopback.conf 2017-10-09 15:32:20 +02:00
cni_main.patch Add support to install Kuryr as a network addon 2017-09-14 13:33:53 +02:00
cni.Dockerfile Clean up ENV vars mistmatches in Dockerfiles 2017-09-20 10:35:36 +02:00
cni.spec Add support to install Kuryr as a network addon 2017-09-14 13:33:53 +02:00
CONTRIBUTING.rst Use https links for documentation 2017-06-12 23:05:25 +08:00
controller.Dockerfile Add support to install Kuryr as a network addon 2017-09-14 13:33:53 +02:00
HACKING.rst Update URLs in documents according to document migration 2017-07-21 14:47:10 +08:00
k8s_client.patch Add support to install Kuryr as a network addon 2017-09-14 13:33:53 +02:00
LICENSE cookiecutter commit for kuryr-kubernetes 2016-05-22 08:54:07 +03:00
README.rst Update URLs in documents according to document migration 2017-07-21 14:47:10 +08:00
requirements.txt CNI split - introducing CNI daemon 2017-11-21 08:50:04 +01:00
setup.cfg CNI split - introducing CNI daemon 2017-11-21 08:50:04 +01:00
setup.py Updated from global requirements 2017-03-15 12:44:19 +00:00
test-requirements.txt Updated from global requirements 2017-09-27 13:41:21 +00:00
tox.ini Enable some off-by-default checks 2017-06-22 17:04:44 +08:00

Team and repository tags

image

Project description

Kubernetes integration with OpenStack networking

The OpenStack Kuryr project enables native Neutron-based networking in Kubernetes. With Kuryr-Kubernetes it's now possible to choose to run both OpenStack VMs and Kubernetes Pods on the same Neutron network if your workloads require it or to use different segments and, for example, route between them.

Contribution guidelines

For the process of new feature addition, refer to the Kuryr Policy