RETIRED, Kubernetes integration with OpenStack networking
f0e1c206a9
This patch introduces ControllerPipeline which is an entry point handler for the Kuryr-Kubernetes controller. ControllerPipeline allows registering ResourceEventHandlers and ensures the proper handler is called for each event that is passed to the ControllerPipeline. Also it ensures the following behavior: - multiple ResourceEventHandlers can be registered for the same resource type (OBJECT_KIND) - failing handlers (i.e. ones that raise Exceptions) are retried until either the handler succeeds or a finite amount of time passes, in which case the most recent exception is logged - in case there are multiple handlers registered for the same resource type, all such handlers are considered independent (i.e. if one handler fails, other handlers will still be called regardless; and the order in which such handlers are called is not determined) - events for different Kubernetes objects can be handled concurrently - events for the same Kubernetes object are handled sequentially in the order of arrival Change-Id: Ib17e0c7a2790cdbc31be4f59d50972b43c272480 Partially-Implements: blueprint kuryr-k8s-integration |
||
---|---|---|
devstack | ||
doc/source | ||
etc/oslo-config-generator | ||
kuryr_kubernetes | ||
scripts | ||
tools | ||
usr/libexec/kubernetes/kubelet-plugins/net/exec | ||
.gitignore | ||
.gitreview | ||
.testr.conf | ||
babel.cfg | ||
CONTRIBUTING.rst | ||
HACKING.rst | ||
LICENSE | ||
MANIFEST.in | ||
README.rst | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
kuryr-kubernetes
Kubernetes integration with OpenStack networking
Please fill here a long description which must be at least 3 lines wrapped on 80 cols, so that distribution package maintainers can use it in their packages. Note that this is a hard requirement.
- Free software: Apache license
- Documentation: http://docs.openstack.org/developer/kuryr-kubernetes
- Source: http://git.openstack.org/cgit/openstack/kuryr-kubernetes
- Bugs: http://bugs.launchpad.net/kuryr-kubernetes
Configuring Kuryr
Generate sample config, etc/kuryr.conf.sample, running the following:
$ ./tools/generate_config_file_samples.sh
Rename and copy config file at required path:
$ cp etc/kuryr.conf.sample /etc/kuryr/kuryr.conf
Edit Neutron section in /etc/kuryr/kuryr.conf, replace ADMIN_PASSWORD:
[neutron]
auth_url = http://127.0.0.1:35357/v3/
username = admin
user_domain_name = Default
password = ADMIN_PASSWORD
project_name = service
project_domain_name = Default
auth_type = password
In the same file uncomment the bindir parameter with the path to the Kuryr vif binding executables. For example, if you installed it on Debian or Ubuntu:
[DEFAULT]
bindir = /usr/local/libexec/kuryr
Features
- TODO