[ovs-dev] Only Faithful Believe.

Only Faithful Believe. How are you? Hope everything goes well. Although i am not comfortable to send this proposal to you because of increase in SCAM and FRAUD especially in Africa. It's my pleasure to Brief you with this. I am writing this mail to you with heavy tears In my eyes and great

[ovs-dev] [PATCH v11 5/5] ovn: rewrite redirect-chassis description in ovn-nb.xml

This optional patch addresses offline comments that the documentation in ovn-nb.xml should not describe southbound constructs or flow details, since it is user facing documentation. Signed-off-by: Mickey Spiegel --- ovn/ovn-nb.xml | 25 ++--- 1 file

[ovs-dev] [PATCH v11 3/5] ovn: distributed NAT flows

This patch implements the flows required in the ingress and egress pipeline stages in order to support NAT on a distributed logical router. NAT functionality is associated with the logical router gateway port. The flows that carry out NAT functionality all have match conditions on inport or

[ovs-dev] [PATCH v11 4/5] ovn: ovn-nbctl commands for distributed NAT

This patch adds the new optional arguments "logical_port" and "external_mac" to lr-nat-add, and displays that information in lr-nat-list. Signed-off-by: Mickey Spiegel --- ovn/utilities/ovn-nbctl.8.xml | 27 +++--- ovn/utilities/ovn-nbctl.c | 54

[ovs-dev] [PATCH v11 2/5] ovn: avoid snat recirc only on gateway routers

Currently, for performance reasons on gateway routers, ct_snat that does not specify an IP address does not immediately trigger recirculation. On gateway routers, ct_snat that does not specify an IP address happens in the UNSNAT pipeline stage, which is followed by the DNAT pipeline stage that

[ovs-dev] [PATCH v11 1/5] ovn: move load balancing flows after NAT flows

This will make it easy for distributed NAT to reuse some of the existing code for NAT flows, while leaving load balancing and defrag as functionality specific to gateway routers. There is no intent to change any functionality in this patch. Signed-off-by: Mickey Spiegel

Re: [ovs-dev] [PATCH v3 7/8] actions: Make "next" action able to jump from egress to ingress pipeline.

On Sat, Jan 21, 2017 at 12:32 PM, Ben Pfaff wrote: > On Sat, Jan 21, 2017 at 12:18:59PM -0800, Mickey Spiegel wrote: > > On Sat, Jan 21, 2017 at 11:13 AM, Ben Pfaff wrote: > > > > > This feature is useful for centralized gateways. > > > > > > Signed-off-by: Ben Pfaff

Re: [ovs-dev] [PATCH v3 7/8] actions: Make "next" action able to jump from egress to ingress pipeline.

On Sat, Jan 21, 2017 at 12:18:59PM -0800, Mickey Spiegel wrote: > On Sat, Jan 21, 2017 at 11:13 AM, Ben Pfaff wrote: > > > This feature is useful for centralized gateways. > > > > Signed-off-by: Ben Pfaff > > Acked-by: Mickey Spiegel > > > >

Re: [ovs-dev] [PATCH v3 1/8] ovn-trace: Fix selection of table that "next" jumps to.

On Sat, Jan 21, 2017 at 12:17:42PM -0800, Mickey Spiegel wrote: > On Sat, Jan 21, 2017 at 11:13 AM, Ben Pfaff wrote: > > > The common case is that "next" advances to the next table, but it can > > jump to any table. > > > > Reported-by: Mickey Spiegel > >

Re: [ovs-dev] [PATCH v3 7/8] actions: Make "next" action able to jump from egress to ingress pipeline.

On Sat, Jan 21, 2017 at 11:13 AM, Ben Pfaff wrote: > This feature is useful for centralized gateways. > > Signed-off-by: Ben Pfaff > Acked-by: Mickey Spiegel > The ovn-trace.c changes look good to me. No more comments. Thank you very much

Re: [ovs-dev] [PATCH v3 1/8] ovn-trace: Fix selection of table that "next" jumps to.

On Sat, Jan 21, 2017 at 11:13 AM, Ben Pfaff wrote: > The common case is that "next" advances to the next table, but it can > jump to any table. > > Reported-by: Mickey Spiegel > Signed-off-by: Ben Pfaff > Acked-by: Mickey Spiegel

Re: [ovs-dev] [PATCH 00/10] Add actions for egress loopback

On Sat, Jan 21, 2017 at 11:23 AM, Ben Pfaff wrote: > On Fri, Jan 20, 2017 at 04:00:34PM -0800, Mickey Spiegel wrote: > > On Fri, Jan 20, 2017 at 3:33 PM, Ben Pfaff wrote: > > > > > On Fri, Jan 20, 2017 at 03:17:19PM -0800, Mickey Spiegel wrote: > > > > On Fri, Jan

Re: [ovs-dev] [PATCH 00/10] Add actions for egress loopback

On Fri, Jan 20, 2017 at 04:00:34PM -0800, Mickey Spiegel wrote: > On Fri, Jan 20, 2017 at 3:33 PM, Ben Pfaff wrote: > > > On Fri, Jan 20, 2017 at 03:17:19PM -0800, Mickey Spiegel wrote: > > > On Fri, Jan 20, 2017 at 2:43 PM, Ben Pfaff wrote: > > > > > > > On Fri, Jan

[ovs-dev] [PATCH v3 8/8] actions: Add new "ct_clear" action.

Signed-off-by: Ben Pfaff Acked-by: Mickey Spiegel --- include/ovn/actions.h | 1 + ovn/lib/actions.c | 16 ovn/ovn-sb.xml| 4 ovn/utilities/ovn-trace.c | 1 + tests/ovn.at | 4 5 files

[ovs-dev] [PATCH v3 7/8] actions: Make "next" action able to jump from egress to ingress pipeline.

This feature is useful for centralized gateways. Signed-off-by: Ben Pfaff Acked-by: Mickey Spiegel --- include/ovn/actions.h | 63 -- ovn/controller/lflow.c| 7 +++-- ovn/lib/actions.c | 70

[ovs-dev] [PATCH v3 5/8] actions: Omit table number when possible for formatting "next" action.

Until now, formatting the "next" action has always required including the table number, because the action struct didn't include enough context so that the formatter could decide whether the table number was the next table or some other table. This is more or less OK, but an upcoming commit will

[ovs-dev] [PATCH v3 4/8] actions: Separate action structures for "next" and "ct_next".

These actions aren't very similar but until now they both had the same action structure. These structures are going to diverge in an upcoming commit, so separate them now. Signed-off-by: Ben Pfaff Acked-by: Mickey Spiegel --- include/ovn/actions.h | 10

[ovs-dev] [PATCH v3 3/8] actions: Add new OVN action "clone".

Signed-off-by: Ben Pfaff Acked-by: Mickey Spiegel --- include/ovn/actions.h | 5 ++-- ovn/lib/actions.c | 61 --- ovn/ovn-sb.xml| 10 ovn/utilities/ovn-trace.c | 19 +++

Re: [ovs-dev] [PATCH v2 6/7] actions: Make "next" action able to jump from egress to ingress pipeline.

On Fri, Jan 20, 2017 at 04:59:57PM -0800, Mickey Spiegel wrote: > On Fri, Jan 20, 2017 at 2:48 PM, Ben Pfaff wrote: > > > This feature is useful for centralized gateways. > > > > Signed-off-by: Ben Pfaff > > > > Acked-by: Mickey Spiegel > >

Re: [ovs-dev] [PATCH v2 4/7] actions: Omit table number when possible for formatting "next" action.

On Fri, Jan 20, 2017 at 04:27:04PM -0800, Mickey Spiegel wrote: > On Fri, Jan 20, 2017 at 2:48 PM, Ben Pfaff wrote: > > > Until now, formatting the "next" action has always required including > > the table number, because the action struct didn't include enough context > > so that

[ovs-dev] question about ovs's bandwidth limition

hi,all: i have two questiones to consult.  software version:  openvswitch-2.6.90.13454.gita9ba22b7 , 3.10.0-327.36.3.el7 1. why logical_switch_port's rate and burst is  set on physical device, rather than port's tap device?  apprently this policy does not work  .why ovn does not choose to