36900e12cd
There's a logic bug in the destroy action: ip_flag is assuming string context when it should be assuming list context. This causes ip_flag to never get set to true and therefore floating IP's never get destroyed. This can lead to floating IP exhaustion, particularly in environments with a low number of allocatable floating IP's. This patch corrects the problem by fixing the logic to check for a list length of zero rather than an empty string. Change-Id: I0205ac406e604365560360fc2953a5e90e1c9be3 Depends-On: Ifa9eeb9d761d9801cab580445e6c43c8cf1dfdaa
interop-workloads
A project for workload development to meet the OpenStack Interop Challenge
With the success of the Interop Challenge in Barcelona, the Interop Challenge mission continues to gain momentum. We will use this project and repository where we can focus on creating and iterating on new OpenStack workloads that will be used to demonstrate that OpenStack clouds are interoperable across a variety of application domains including enterprise workloads, NFV workloads, K8s, and many others under evaluation. We will also use this repo to store our best practices documents and other collateral that facilitates improving the state of OpenStack Clouds' ability to interoperate.
- Free software: Open software under Apache 2.0 license
- Documentation: http://docs.openstack.org/developer/interop-workloads
- Source: http://git.openstack.org/cgit/openstack/interop-workloads
- Bugs: http://bugs.launchpad.net/interop-workloads
Features
- TODO