1c2320e11e
pyroute2.IPDB is an interesting entity. It's much more than a simple interface to `ip` command, as it is more similar to a database process. When created IPDB object spawns a thread that will be responsible for updating the object with changes to the underlying OS. Thread stays up until the user will call `release()` method. Turns out code in kuryr_kubernetes.cni.binding wasn't taking that into account and was slowly leaking threads (and possibly processes). This became apparent when running Kuryr with CNI daemon enabled. This commit fixes the problem by switching all IPDB usages to context managers, so `release()` method is called automatically. Also the IPDB objects cache is removed as already released IPDB objects cannot be reused. kuryr_kubernetes.cni.binding modules were missing unit tests, this commit adds them as well. Change-Id: I82afda3f217dac56228677bb66703c3d80e5d751 Closes-Bug: 1728996
Team and repository tags
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.
- Free software: Apache license
- Documentation: https://docs.openstack.org/kuryr-kubernetes/latest
- Source: https://git.openstack.org/cgit/openstack/kuryr-kubernetes
- Bugs: https://bugs.launchpad.net/kuryr-kubernetes
- Overview and demo: http://superuser.openstack.org/articles/networking-kubernetes-kuryr
Contribution guidelines
For the process of new feature addition, refer to the Kuryr Policy