On Fri, Jan 20, 2017 at 2:48 PM, Ben Pfaff <[email protected]> wrote: > This feature is useful for centralized gateways. > > Signed-off-by: Ben Pfaff <[email protected]> >
Acked-by: Mickey Spiegel <[email protected]> I think there is some missing functionality in ovn-trace.c. It looks to me like ovn-trace.c assumes that "next" actions always go to the next table, i.e. it ignores "(3)" or "(pipeline=ingress, table=3)". For my particular usage, egress loopback will only happen after NAT, so the trace will never reach the "next(pipeline=ingress, table=0)" action. Mickey > --- > include/ovn/actions.h | 63 ++++++++++++++++++++++++------------------ > ovn/controller/lflow.c | 7 +++-- > ovn/lib/actions.c | 70 ++++++++++++++++++++++++++++++ > ++++++++++------- > ovn/ovn-sb.xml | 12 ++++++-- > ovn/utilities/ovn-trace.c | 3 ++ > tests/ovn.at | 22 ++++++++++++++- > tests/test-ovn.c | 6 ++-- > 7 files changed, 138 insertions(+), 45 deletions(-) _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
