[ovs-git] [openvswitch/ovs] d9f9e0: ovn-controller: Datapath based conntrack zone for ...

[GitHub]

  Branch: refs/heads/branch-2.6
  Home:   https://github.com/openvswitch/ovs
  Commit: d9f9e0c830a2fafa663451f91d0b64ab4e14769a
      https://github.com/openvswitch/ovs/commit/d9f9e0c830a2fafa663451f91d0b64ab4e14769a
  Author: Gurucharan Shetty <guru at ovn.org>
  Date:   2016-09-09 (Fri, 09 Sep 2016)

  Changed paths:
    M include/ovn/actions.h
    M ovn/controller/lflow.c
    M ovn/lib/actions.c
    M ovn/ovn-sb.xml
    M tests/test-ovn.c

  Log Message:
  -----------
  ovn-controller: Datapath based conntrack zone for load-balancing.

Currently ct_lb() logical action is only added for a logical switch and
we use the conntrack zone allocated for the logical port.  A future commit
will use ct_lb() for a logical router too.  In that case, use the allocated
DNAT zone.

Rationale for not passing zone as an argument for ct_lb():
One way to look at it would be that a "zone" is an internal implementation
detail and should not be seen in a action of logical flow.  But we can then
say that we could rename "zone" as "datapath" in the logical action.  But,
then we would be limiting it to 2 anyway (datapath=lswitch or
datapath=lrouter) - in which case we are inferring it with the current patch.

Signed-off-by: Gurucharan Shetty <guru at ovn.org>
Acked-by: Ben Pfaff <blp at ovn.org>


  Commit: ab9a3323b47fe68870f52c6f7860890a7b854b71
      https://github.com/openvswitch/ovs/commit/ab9a3323b47fe68870f52c6f7860890a7b854b71
  Author: Gurucharan Shetty <guru at ovn.org>
  Date:   2016-09-09 (Fri, 09 Sep 2016)

  Changed paths:
    M ovn/northd/ovn-northd.8.xml
    M ovn/northd/ovn-northd.c
    M ovn/ovn-nb.ovsschema
    M ovn/ovn-nb.xml
    M tests/system-ovn.at

  Log Message:
  -----------
  ovn-northd: Add load-balancers to gateway routers.

Load-balancers in gateway routers lets us load-balance
north-south traffic.

This commit adds a new table called "DEFRAG" in the
logical router pipeline to defragment packets and to track them.
Once the packet is tracked, new connections get a group id as
an action. The group in turn chooses a DNAT action.  Established
connections go through the DNAT table for a regular DNAT.

Signed-off-by: Gurucharan Shetty <guru at ovn.org>
Acked-by: Ben Pfaff <blp at ovn.org>


Compare: https://github.com/openvswitch/ovs/compare/f09c5b710621...ab9a3323b47f