Reviewed: https://review.opendev.org/726787 Committed: https://git.openstack.org/cgit/openstack/ovn-octavia-provider/commit/?id=23d743a444a426379499193324723a9c7ab33734 Submitter: Zuul Branch: master
commit 23d743a444a426379499193324723a9c7ab33734 Author: Maciej Józefczyk <[email protected]> Date: Mon May 11 10:16:56 2020 +0000 Add support for OVN LB selection fields Prior this patch OVN Octavia provider driver used default 5-tuple-hash algorithm which is pretty similar to SOURCE_IP_PORT. Unfornutelly because of the bug described here [1] it was not clear how 5-tuple-hash works and some inconsistencies between kernel and user space implementations were found. OVN recently added support for selective fields in OVN LB, to explicitly define what fields are being hashed to tackle this problem. This commit adds support for that kind of hashing. If installation of OVN on which OVN Octavia provider is running doesn't support selective fields - it will use old behavior. [1] https://mail.openvswitch.org/pipermail/ovs-discuss/2020-April/049896.html [2] https://github.com/ovn-org/ovn/commit/5af304e7478adcf5ac50ed41e96a55bebebff3e8 Change-Id: I7b4ab99d1be2855e18b186557990c85f170ad548 Closes-Bug: #1871239 ** Changed in: neutron Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1871239 Title: ovn-octavia-provider is not using load balancing algorithm source-ip- port Status in neutron: Fix Released Bug description: When using the ovn-octavia-provider, OVN is not honoring the SOURCE_IP_PORT pool load balancing algorithm. The ovn-octavia-provider only supports the SOURCE_IP_PORT load balancing algorithm. The following test was created for the SOURCE_IP_PORT algorithm in tempest: octavia_tempest_plugin.tests.scenario.v2.test_traffic_ops.TrafficOperationsScenarioTest.test_source_ip_port_tcp_traffic Available in this patch: https://review.opendev.org/#/c/714004/ The test run shows that OVN is randomly distributing the connections from the same source IP and port across the backend member servers. One server is configured to return '1' and the other '5'. Loadbalancer response totals: {'1': 12, '5': 8} It should be seeing a result of: Loadbalancer response totals: {'1': 20} The attached files provide: ovn-provider.pcap -- A pcap file capturing the test run. ovn-tempest-output.txt -- The tempest console output. tempest.log -- The tempest framework log from the test run. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1871239/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
