[ovs-dev] [PATCH v3] ovs-tcpdump: Cleanup mirror port on SIGHUP/SIGTERM

2022-09-08 Thread Daniel Ding
If ovs-tcpdump received HUP or TERM signal, mirror and mirror interface should be destroyed. This often happens, when controlling terminal is closed, like ssh session closed, and other users use kill to terminate it. Acked-by: Mike Pattrick Signed-off-by: Daniel Ding --- utilities/ovs-tcpdump.i

Re: [ovs-dev] [PATCH v3] ovs-tcpdump: Cleanup mirror port on SIGHUP/SIGTERM

2022-09-08 Thread Daniel Ding
Excuse me, This patch is invalid because of indentation. On 2022/9/8 15:07, Daniel Ding wrote: If ovs-tcpdump received HUP or TERM signal, mirror and mirror interface should be destroyed. This often happens, when controlling terminal is closed, like ssh session closed, and other users use kill

[ovs-dev] [PATCH v4] ovs-tcpdump: Cleanup mirror port on SIGHUP/SIGTERM

2022-09-08 Thread Daniel Ding
If ovs-tcpdump received HUP or TERM signal, mirror and mirror interface should be destroyed. This often happens, when controlling terminal is closed, like ssh session closed, and other users use kill to terminate it. Acked-by: Mike Pattrick Signed-off-by: Daniel Ding --- utilities/ovs-tcpdump.i

[ovs-dev] [branch-2.16] dpdk: Use DPDK 20.11.6 release.

2022-09-08 Thread Michael Phelan
CI Linux build script updated to use DPDK version 20.11.6. Documentation updated to use DPDK version 20.11.6. NEWS entry added for DPDK 20.11.6 validation. Updated FAQ to recommend use of DPDK 20.11.6. Signed-off-by: Michael Phelan --- .ci/linux-build.sh | 2 +- Documentation/f

[ovs-dev] [branch-2.15] dpdk: Use DPDK 20.11.6 release.

2022-09-08 Thread Michael Phelan
CI Linux build script updated to use DPDK version 20.11.6. Documentation updated to use DPDK version 20.11.6. NEWS entry added for DPDK 20.11.6 validation. Updated FAQ to recommend use of DPDK 20.11.6. Signed-off-by: Michael Phelan --- .ci/linux-build.sh | 2 +- Documentation/f

[ovs-dev] [branch-3.0] dpdk: Use DPDK 21.11.2 release.

2022-09-08 Thread Michael Phelan
CI linux build script updated to use DPDK version 21.11.2. Documentation updated to use DPDK version 21.11.2. NEWS entry added for DPDK 21.11.2 validation. Updated FAQ to recommend use of DPDK 21.11.2. Signed-off-by: Michael Phelan --- .ci/linux-build.sh | 2 +- Documentation/f

[ovs-dev] [branch-2.17] dpdk: Use DPDK 21.11.2 release.

2022-09-08 Thread Michael Phelan
CI linux build script updated to use DPDk version 21.11.2. Documentation updated to use DPDK version 21.11.2. NEWS entry added for DPDK 21.11.2 validation. Updated FAQ to recommend use of DPDK 21.11.2. Signed-off-by: Michael Phelan --- .ci/linux-build.sh | 2 +- Documentation/f

[ovs-dev] [PATCH] dpdk: Use DPDK 21.11.2 release.

2022-09-08 Thread Michael Phelan
CI Linux build script updated to use DPDK version 21.11.2. Documentation updated to use DPDK version 21.11.2. NEWS entry added for DPDK 21.11.2 validation. Updated FAQ to recommend use of DPDK version 21.11.2. Signed-off-by: Michael Phelan --- .ci/linux-build.sh | 2 +- Documen

[ovs-dev] [PATCH ovn] northd: drop traffic to disabled LSPs in ingress pipeline

2022-09-08 Thread Vladislav Odintsov
Prior to this patch traffic to LSPs, which are disabled with `ovn-nbctl lsp-set-enabled disabled` was dropped in the end of lswitch egress pipeline. This means that traffic is processed in vain: - traffic, which should be dropped, first travels from one chassis to another (if source/dest LSPs r

Re: [ovs-dev] [PATCH ovn] northd: drop traffic to disabled LSPs in ingress pipeline

2022-09-08 Thread Vladislav Odintsov
Please, ignore this patch. It contains errors, I’ll resend v2. Regards, Vladislav Odintsov > On 8 Sep 2022, at 14:40, Vladislav Odintsov wrote: > > Prior to this patch traffic to LSPs, which are disabled with > `ovn-nbctl lsp-set-enabled disabled` was dropped in the end of > lswitch egress pip

[ovs-dev] [PATCH ovn v2] northd: drop traffic to disabled LSPs in ingress pipeline

2022-09-08 Thread Vladislav Odintsov
Prior to this patch traffic to LSPs, which are disabled with `ovn-nbctl lsp-set-enabled disabled` was dropped in the end of lswitch egress pipeline. This means that traffic is processed in vain: - traffic, which should be dropped, first travels from one chassis to another (if source/dest LSPs r

[ovs-dev] [PATCH ovn] northd: Accumulate more database updates before processing.

2022-09-08 Thread Ilya Maximets
northd doesn't process changes incrementally, so it makes sense to accumulate more database updates and process them in bulk, so we can cover everything in a single recompute. ovsdb-server has a mechanism to start accumulating changes if the client doesn't receive them fast enough, but it relies o

Re: [ovs-dev] [PATCH ovn] northd: Do not relay local IP multicast (224.0.0.X).

2022-09-08 Thread Han Zhou
On Tue, Aug 9, 2022 at 3:21 AM Numan Siddique wrote: > > On Tue, Aug 9, 2022 at 5:21 PM Ales Musil wrote: > > > > On Wed, Aug 3, 2022 at 1:21 PM Dumitru Ceara wrote: > > > > > Reported-at: https://bugzilla.redhat.com/show_bug.cgi?id=2077306 > > > Signed-off-by: Dumitru Ceara > > > --- > > > no

Re: [ovs-dev] [PATCH ovn v2] Don't blindly save original dst IP and Port to avoid megaflow unwildcarding.

2022-09-08 Thread Han Zhou
On Wed, Sep 7, 2022 at 8:47 AM Dumitru Ceara wrote: > > On 9/6/22 22:03, Han Zhou wrote: > > On Tue, Sep 6, 2022 at 6:42 AM Dumitru Ceara wrote: > >> > >> On 8/31/22 16:59, Han Zhou wrote: > >>> On Wed, Aug 31, 2022 at 1:38 AM Dumitru Ceara wrote: > > On 8/31/22 02:17, Han Zhou wrote:

[ovs-dev] OVSCI Automation Upgrade planned for Friday 9/9/22

2022-09-08 Thread Michael Santana
Hi all, We are planning on doing a system upgrade on our OVSCI automation system this Friday 9/9/22. This will affect our upstream robots (i.e. ovs, ovn, dpdk). This affects patchwork sync and github actions sync, etc. After the upgrade is completed the robots will be started again and expected t

Re: [ovs-dev] [PATCH ovn 2/3] ovn-controller: Track OVSDB column open_vswitch:external_ids.

2022-09-08 Thread Han Zhou
Thanks for the review and sorry for the late response. On Tue, Aug 23, 2022 at 5:22 AM Dumitru Ceara wrote: > > Hi Han, > > On 8/23/22 06:44, Han Zhou wrote: > > On Tue, Jul 5, 2022 at 3:41 PM Han Zhou wrote: > >> > >> The column was not tracked before while it should. The column includes > >> m

Re: [ovs-dev] [PATCH ovn] northd: Always propagate LB proto to lflows

2022-09-08 Thread Han Zhou
On Tue, Sep 6, 2022 at 6:02 AM Ales Musil wrote: > > The current behavior is that load balancers > default to tcp protocol if it is not specified. > However, this is not propagated to lflows which > specify proto only when port is specified as part > of the protocol e.g. udp.port == X. Always incl

Re: [ovs-dev] [PATCH ovn] northd: Properly check the wakeup time in MAC banding aging

2022-09-08 Thread Han Zhou
On Tue, Sep 6, 2022 at 4:12 AM Ales Musil wrote: > > We shouldn't run the MAC binding aging if the waker did not > expire. This wouldn't cause any issue if the bulk removal limit > is not configured. When the limit is configured and hit there > will be some MAC bindings expired, just waiting for t

Re: [ovs-dev] [PATCH ovn] northd: Always propagate LB proto to lflows

2022-09-08 Thread Ales Musil
On Fri, Sep 9, 2022 at 7:43 AM Han Zhou wrote: > > > On Tue, Sep 6, 2022 at 6:02 AM Ales Musil wrote: > > > > The current behavior is that load balancers > > default to tcp protocol if it is not specified. > > However, this is not propagated to lflows which > > specify proto only when port is sp

Re: [ovs-dev] [PATCH ovn] northd: Accumulate more database updates before processing.

2022-09-08 Thread Han Zhou
On Thu, Sep 8, 2022 at 8:46 AM Ilya Maximets wrote: > > northd doesn't process changes incrementally, so it makes sense to > accumulate more database updates and process them in bulk, so we can > cover everything in a single recompute. > > ovsdb-server has a mechanism to start accumulating changes