17b1d9d573
When Load Balancer and its member has FIP assigned and environment is configured to use DVR the member FIP needs to be centralized. It is current core OVN limitation, that should be solved in [1]. This patch adds this mechanism to OVN Client and OVN Octavia provider driver. It covers cases: 1) FIP association on port that is a member of some LB - make it centralized. 2) FIP association on LB VIP - find a members FIPs and centralized them. 3) Add a member to LB that has FIP already configured - checks if a member has FIP and centralize it. 4) The reverse of each of the above cases. In addition I needed to extend OVN LB member external_id entry to add an information about member subnet_id in order to easly track member port from mechanism OVN driver. That means I needed also to support both old and new conventions. This patch adds also this code. Old convention: member_`member_id`_`ip_address`:`port` New convention: member_`member_id`_`ip_address`:`port`_`subnet_id` [1] https://bugzilla.redhat.com/show_bug.cgi?id=1793897 Related-Bug: #1860662 Change-Id: I254f0ac28f7585b699a8238e01ffb37dd70282ef (cherry picked from networking-ovn commit 57ac38921efa6bbf0bc4a22950355256cc3ebe6d)
ovn-octavia-provider - OVN Provider driver for Octavia LoadBalancer
OVN provides virtual networking for Open vSwitch and is a component of the Open vSwitch project. This project provides integration between OpenStack Octavia and OVN.
- Free software: Apache license
- Source: https://opendev.org/openstack/ovn-octavia-provider
- Bugs: https://bugs.launchpad.net/neutron/+bugs?field.tag=ovn-octavia-provider
- Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss
- IRC: #openstack-neutron on Freenode.
- Docs: https://docs.openstack.org/ovn-octavia-provider/latest
Team and repository tags
- Release notes for the project can be found at: https://docs.openstack.org/releasenotes/ovn-octavia-provider