On 10/13/22 07:35, Lorenzo Bianconi wrote:
Hi Lorenzo,
Hi Mark,
Is load balancer affinity intended to work with
a) Load balancers that do not specify a protocol?
If not specified tcp is used as default value.
TCP is the default only if a port is specified but no protocol is
specified. If no port is specified and no protocol is specified, then
all L3 traffic should be load-balanced.
b) Load balancers that do not specify a VIP port?
ack, I need to fix it.
c) Load balancers that do not specify a backend port?
ack, I need to fix it.
Regards,
Lorenzo
On 10/4/22 09:02, Lorenzo Bianconi wrote:
Introduce load-balancer affinity timeout in order to dnat connections received
from the same client to a given load-balancer to the same backend if received
in the affinity timeslot specified by the CMS.
Reported-at: https://bugzilla.redhat.com/show_bug.cgi?id=2127959
Lorenzo Bianconi (3):
actions: introduce commit_lb_aff action
actions: introduce chk_lb_aff action
northd: rely on new actions for lb affinity
controller/lflow.h | 1 +
include/ovn/actions.h | 16 ++
include/ovn/logical-fields.h | 3 +
lib/actions.c | 389 +++++++++++++++++++++++++++++++++++
lib/lb.c | 3 +
lib/lb.h | 1 +
northd/northd.c | 185 ++++++++++++++---
northd/ovn-northd.8.xml | 208 ++++++++++++++++---
ovn-sb.xml | 44 ++++
tests/ovn-northd.at | 346 +++++++++++++++++++------------
tests/ovn.at | 65 +++---
tests/system-ovn.at | 182 +++++++++++++++-
utilities/ovn-trace.c | 4 +
13 files changed, 1226 insertions(+), 221 deletions(-)
_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev
