Recent pep8 upgrade and corresponding pycodestyle(2.4.0) update break
neutron-lbaas pep8 job due to the new rules.
This commit fixes the following new errors:
- E501 line too long
- E402 module level import not at top of file
- W503 line break before binary operator
Story: 2001828
Task: 12584
Change-Id: Ifa5a75745bd03aba6af63422623c5cd9eef344e4
Currently, lbaas agent refresh loadbalancer based on the number of active
listener, and will update the port with device_own='' if delete the last
listener in loadbalancer.
So the device_owner of the vip port of exist loadbalancer will never
update to the correct one.
This patch add port device_owner field to PUT to guarantee the field is
'neutron:LOADBALANCERV2'.
Change-Id: I2de5800f4a6b06f98174ef42390f0e2c91bf0cfd
Closes-Bug:#1692995
With the merge of [1], plugin constants are now available in
neutron_lib, so it makes sense to move there .
[1] https://review.openstack.org/#/c/429036/
Change-Id: Ic6e5620d6d3ff33447d3804919cd63716d4a6894
This patch refactors networking-lbaas to use portbindings
from neutron-lib. For more details see [1].
NeutronLibImpact
[1] https://review.openstack.org/422210/
Change-Id: Ic8ae6d9ab9fdc5c9c4dcd7b085ac72dcc648b7b0
nova boot on lbaas_vip port is not blocked as nova throws PortInUse exception
only if the port device_id is set. Currently device_id is updated during
lbaas listener create.
This fix sets the device_id to loadbalancer id during the loadbalancer create.
Change-Id: I2dfce54322eff5f4830b94ac8424057780ebeb9d
Closes-Bug: #1482763
Added the agent callbacks so that an agent can call back to
the neutron API server to retrieve information or perform
an action that an agent cannot do because it does not
have access to the same resources as the neutron API server
(such as DB access).
Also added from_dict methods in the data_models as callbacks
and the agent will need these.
Change-Id: I292415206b23731ea8197aeb91fc87ff148bc14c
Depends-On: Ic9179ef0a95b91d1b7662537fffeb0a949efc925
Partially-implements: blueprint lbaas-refactor-haproxy-namespace-driver-to-new-driver-interface
Co-Authored-By: Brandon Logan <brandon.logan@rackspace.com>
Adam Harwell