Re: [ovs-dev] [PATCH] datapath-windows: Specify external include paths

Alin, Does it make sense to apply this patch to stable branches too. I see that 2.15 fails with a similar error. Thanks, Guru On Thu, 17 Jun 2021 at 02:31, Alin-Gabriel Serdean wrote: > On Wed, 2021-06-16 at 18:06 +0300, Alin-Gabriel Serdean wrote: > > On Tue, 2021-06-15 at 18:06 +0200, Ilya

Re: [ovs-dev] [PATCH] Update scripts to support RHEL 7.9

On Tue, 17 Nov 2020 at 13:32, Greg Rose wrote: > From: Greg Rose > > Add support for RHEL7.9 GA release with kernel 3.10.0-1160 > > Signed-off-by: Greg Rose > --- > Thank you. I applied this to master. > rhel/openvswitch-kmod-fedora.spec.in | 6 -- >

Re: [ovs-dev] [PATCH] ovs-lib: Handle daemon segfaults during exit.

On Mon, 21 Sep 2020 at 10:53, Yi-Hung Wei wrote: > On Fri, Sep 18, 2020 at 9:54 AM Gurucharan Shetty wrote: > > > > Currently, we terminate a daemon by trying > > "ovs-appctl exit", "SIGTERM" and finally "SIGKILL". > > But the logic fails if during "ovs-appctl exit", the > > daemon crashes

Re: [ovs-dev] [PATCH v2 2/2] Prepare for post-2.13.0 (2.13.90).

On Tue, 21 Jan 2020 at 12:46, Ben Pfaff wrote: > Signed-off-by: Ben Pfaff > For both: Acked-by: Gurucharan Shetty > --- > NEWS | 4 > configure.ac | 2 +- > debian/changelog | 6 ++ > 3 files changed, 11 insertions(+), 1 deletion(-) > > diff --git a/NEWS b/NEWS >

Re: [ovs-dev] [PATCH] Prepare for 2.13.0.

On Tue, 21 Jan 2020 at 12:27, Ben Pfaff wrote: > Signed-off-by: Ben Pfaff > Usually I see one more "Prepare for post-" patch. But I guess, you intend to do it later. Acked-by: Guru Shetty > --- > NEWS | 2 +- > configure.ac | 2 +- > debian/c

Re: [ovs-dev] [PATCH] rhel: Revert RHEL 7.4 comp_ver change

On Tue, 3 Sep 2019 at 08:50, Greg Rose wrote: > I looked at the wrong list of kernels when I changed the value for the > RHEL 7.4 comp_ver variable. Revert that part of commit e64c2c1 > ("rhel: Fix ovs-kmod-manage.sh to work with RHEL 7.3"). > > Fixes: e64c2c1 ("rhel: Fix ovs-kmod-manage.sh to

Re: [ovs-dev] [PATCH] rhel: Add case for RHEL 7.5 major version to kmod manage script

On Wed, 28 Aug 2019 at 10:42, Gregory Rose wrote: > > > On 8/28/2019 10:16 AM, Gregory Rose wrote: > > > > > > On 8/28/2019 10:07 AM, Guru Shetty wrote: > >> I applied this to master and 2.12. I got a conflict for 2.11. If you > >> need this for 2.11,

Re: [ovs-dev] [PATCH] rhel: Add case for RHEL 7.5 major version to kmod manage script

I applied this to master and 2.12. I got a conflict for 2.11. If you need this for 2.11, can you please rebase? On Tue, 27 Aug 2019 at 14:12, Yifeng Sun wrote: > Reviewed-by: Yifeng Sun > > On Tue, Aug 27, 2019 at 2:06 PM Greg Rose wrote: > > > > A Centos 7.5 kernel with an unencountered set

Re: [ovs-dev] [PATCH] rhel: Add case for RHEL 7.5 major version to kmod manage script

On Tue, 27 Aug 2019 at 14:06, Greg Rose wrote: > A Centos 7.5 kernel with an unencountered set of minor build numbers > caused an upgrade bug. Adding the case for the rhel 7.5 kmod management > script fixes the problem. > > Signed-off-by: Greg Rose > --- >

Re: [ovs-dev] [PATCHv2] ovs-lib: Add timeout at ovs-check-dead-ifs.

On Tue, 27 Aug 2019 at 11:10, William Tu wrote: > At SUSE12 SP3, we hit a case where ovs-check-dead-ifs tries to read > an entry in /proc//fd/ but hangs forever. The pid is > a qemu-system-x86_64 process and we suspect it's an issue related to > qemu, not ovs. As a result, force-reload-kmod

Re: [ovs-dev] [PATCH] ovs-lib: Add timeout at ovs-check-dead-ifs.

On Fri, 23 Aug 2019 at 11:29, William Tu wrote: > At SUSE12 SP3, we hit a case where ovs-check-dead-ifs tries to read > an entry in /proc//fd/ but hangs forever. The pid is > a qemu-system-x86_64 process and we suspect it's an issue related to > qemu, not ovs. As a result, force-reload-kmod

Re: [ovs-dev] [branch2.12] ovn: Add a new logical switch port type - 'virtual'

On Thu, 1 Aug 2019 at 10:52, wrote: > From: Numan Siddique > > This new type is added for the following reasons: > > - When a load balancer is created in an OpenStack deployment with Octavia > service, it creates a logical port 'VIP' for the virtual ip. > > - This logical port is not

Re: [ovs-dev] [PATCH v9] ovn: Add a new logical switch port type - 'virtual'

On Thu, 18 Jul 2019 at 07:58, wrote: > From: Numan Siddique > > This new type is added for the following reasons: > > - When a load balancer is created in an OpenStack deployment with Octavia > service, it creates a logical port 'VIP' for the virtual ip. > > - This logical port is not

Re: [ovs-dev] [PATCH v7] ovn: Add a new logical switch port type - 'virtual'

On Tue, 16 Jul 2019 at 17:48, wrote: > From: Numan Siddique > > This new type is added for the following reasons: > > - When a load balancer is created in an OpenStack deployment with Octavia > service, it creates a logical port 'VIP' for the virtual ip. > > - This logical port is not

Re: [ovs-dev] [PATCH] ovs-atomic-c++.h: Fix for 64 bit atomics.

On Thu, 13 Jun 2019 at 09:54, Ben Pfaff wrote: > On Wed, Jun 12, 2019 at 09:48:59PM -0700, Gurucharan Shetty wrote: > > Commit e981a45a6cae4 (ovs-atomic: Add 64 bit apis.) > > added a few 64 bit apis (e.g: atomic_count_inc64). For C++, > > this invokes std::atomic_fetch_*_explicit() functions

Re: [ovs-dev] [PATCH v2] rhel: Add 4.12 kernel support in ovs-kmod-manage.sh

On Mon, 20 May 2019 at 12:48, Yi-Hung Wei wrote: > This patch extends c3570519ecaf ("rhel: add 4.4 kernel in kmod build > with mulitple versions, fedora") that updates ovs-kmod-manage.sh to > support SLES 12 SP4 kernel (4.12.x, x>=14). > > For some distros, openvswitch-kmod rpm package may

Re: [ovs-dev] [PATCH 2/2] fedora: Handle upgrades from rhel package.

> > >> > +# daemons. Another "restart" (outside the package postinst script) >> is >> > +# needed to actually run new daemons. >> > +if [ -e "%{_tmppath}/ovs-upgrade-from-sysv" ]; then >> t seems that if rpm package that was built from rhel spec file was >> removed (without upgrade)

Re: [ovs-dev] [PATCH 2/2] fedora: Handle upgrades from rhel package.

On Thu, 9 May 2019 at 17:37, Ansis Atteka wrote: > On Fri, 3 May 2019 at 11:19, Gurucharan Shetty wrote: > > > > Currently we have rhel/openvswitch.spec.in that provides > > sysv scripts. The fedora package provides systemd scripts. > > If one upgrades openvswitch package from sysv to systemd,

Re: [ovs-dev] [PATCH 1/2] fedora: Ability to auto enable openvswitch service.

> > > Hi, > usually a package on Fedora/RHEL7+ is never enabled by default, unless > it's necessary to enable it for a really good reason. > I would like to put an argument on why this a good reason in this case. When I did a grep on 2 large repositories at VMware that use openvswitch RPMs,

Re: [ovs-dev] [PATCH] ovs-save: Handle cases of upgrades from very old OVS versions.

On Thu, 9 May 2019 at 14:09, Ben Pfaff wrote: > On Wed, May 08, 2019 at 07:11:56AM -0700, Gurucharan Shetty wrote: > > We have added code to ovs-save over the last few releases > > which makes the following bad assumptions. > > > > 1. The default OpenFlow version of running daemon is OpenFlow14.

Re: [ovs-dev] [PATCH 2/2] fedora: Handle upgrades from rhel package.

On Fri, 3 May 2019 at 13:05, Aaron Conole wrote: > Guru Shetty writes: > > > On Fri, 3 May 2019 at 11:36, Aaron Conole wrote: > > > > Gurucharan Shetty writes: > > > > > Currently we have rhel/openvswitch.spec.in that provides > > > sysv scri

Re: [ovs-dev] [PATCH 2/2] fedora: Handle upgrades from rhel package.

On Fri, 3 May 2019 at 11:36, Aaron Conole wrote: > Gurucharan Shetty writes: > > > Currently we have rhel/openvswitch.spec.in that provides > > sysv scripts. The fedora package provides systemd scripts. > > If one upgrades openvswitch package from sysv to systemd, > > you will end up in a

Re: [ovs-dev] OVN/OVS Split POC: version 2

Mark, The debian directory currently has scripts that build OVN packages for Ubuntu. You plan to move that, right? On Wed, 24 Apr 2019 at 05:27, Mark Michelson wrote: > On 4/23/19 5:35 PM, Justin Pettit wrote: > > > >> On Apr 23, 2019, at 2:25 PM, Ben Pfaff wrote: > >> > >> I got the right

Re: [ovs-dev] [PATCH] rhel: Use PIDFile on forking systemd service files

On Mon, 22 Apr 2019 at 14:02, Guru Shetty wrote: > > > On Thu, 28 Feb 2019 at 09:37, Timothy Redaelli > wrote: > >> Currently, PIDFile is not used in systemd service files with >> Type=forking. This means sometimes systemd fails to restart a daemon >

Re: [ovs-dev] [PATCH] rhel: Use PIDFile on forking systemd service files

On Thu, 28 Feb 2019 at 09:37, Timothy Redaelli wrote: > Currently, PIDFile is not used in systemd service files with > Type=forking. This means sometimes systemd fails to restart a daemon > that is killed (with SIGKILL) or that is crashed. > > This commit adds PIDFile to all systemd service file

Re: [ovs-dev] [PATCH v2] ovn: Avoid tunneling for VLAN packets redirected to a gateway chassis

On Mon, 19 Nov 2018 at 08:18, wrote: > From: Numan Siddique > > An OVN deployment can have multiple logical switches each with a > localnet port connected to a distributed logical router in which one > logical switch may provide external connectivity and the rest of > the localnet logical

Re: [ovs-dev] Possible OVN enhancement: implementing OpenShift's "unidling" behavior

I don't have specific comments. But I do believe that "holding" packet may not work well as the time taken to create new pods, assign IPs to those pod, create new load-balancer rules for the new pods, will be in "seconds". On Fri, 9 Nov 2018 at 12:26, Mark Michelson wrote: > Yesterday during

Re: [ovs-dev] [PATCH 1/2] ovn: Avoid tunneling for VLAN packets redirected to a gateway chassis

On Fri, 5 Oct 2018 at 10:15, wrote: > From: Numan Siddique > > An OVN deployment can have multiple logical switches each with a > localnet port connected to a distributed logical router with one > logical router port providing external connectivity (provider network) > and others used as tenant

Re: [ovs-dev] [PATCH 1/2] ovn: Avoid tunneling for VLAN packets redirected to a gateway chassis

On Fri, 5 Oct 2018 at 10:15, wrote: > From: Numan Siddique > > An OVN deployment can have multiple logical switches each with a > localnet port connected to a distributed logical router with one > logical router port providing external connectivity (provider network) > and others used as tenant

Re: [ovs-dev] VLAN tenant network patches

ve, we have identified some gaps, which we intend to fix. > > > As we progress further, we will have to add some features as well. > But, as of now we are focused on getting basic functionality to work > correctly first. > > > > Please feel free to put forth more queries/

Re: [ovs-dev] VLAN tenant network patches

my feedback here: > > https://mail.openvswitch.org/pipermail/ovs-dev/2018-November/353701.html > > > > Providing some more comments inline. > > Thanks again Guru, Numan, Mark and Han for spending time on the proposal > and providing feedback. > I am preparing a v2, which

Re: [ovs-dev] VLAN tenant network patches

> > Ankur's proposal: > > == > > > > Though the complete patches do not exist, Ankur wants to solve the > problem > > 1 by having a chassis specific MAC. So when packet leaves a hypervisor > for > > east-west routing, it uses a unique mac. The disadvantage with this > > proposal is

[ovs-dev] VLAN tenant network patches

I have tried to summarize the problem statement that Numan and Ankur are trying to solve here based on my understanding so far. Please correct me and I will revise it along. Current feature set in OVN. == A logical switch should only have one localnet logical port. If a

Re: [ovs-dev] OVN based distributed virtual routing for VLAN backed networks

On Wed, 7 Nov 2018 at 15:01, Guru Shetty wrote: > > > On Fri, 19 Oct 2018 at 15:17, Ankur Sharma > wrote: > >> Hi Guru, >> >> Thanks for taking a look. >> Please find the detailed explanation of problem statement inline. >> >> Thanks >

Re: [ovs-dev] OVN based distributed virtual routing for VLAN backed networks

On Wed, 7 Nov 2018 at 15:01, Guru Shetty wrote: > > > On Fri, 19 Oct 2018 at 15:17, Ankur Sharma > wrote: > >> Hi Guru, >> >> Thanks for taking a look. >> Please find the detailed explanation of problem statement inline. >> >> Thanks >

Re: [ovs-dev] OVN based distributed virtual routing for VLAN backed networks

On Fri, 19 Oct 2018 at 15:17, Ankur Sharma wrote: > Hi Guru, > > Thanks for taking a look. > Please find the detailed explanation of problem statement inline. > > Thanks > > Regards, > Ankur > > > > *From:* Guru Shetty > *Sent:* Friday, October 19, 2018

Re: [ovs-dev] [branch 2.9][PATCH] ovn: Fix IPv6 DAD failure for container ports

On Tue, 23 Oct 2018 at 03:22, wrote: > From: Numan Siddique > > When a container port is created inside a VM, the below kernel message > is seen and IPv6 doesn't work on that interface. > > [ 138.000753] IPv6: vlan4: IPv6 duplicate address detected! > > When a container port sends a ethernet

Re: [ovs-dev] OVN based distributed virtual routing for VLAN backed networks

On Tue, 16 Oct 2018 at 15:43, Ankur Sharma wrote: > Hi, > > We have done some effort in evaluating usage of OVN for > Distributed Virtual Routing (DVR) for vlan backed networks. > Would you mind explaining the above statement with a lot of details? I would like to understand the problem well

Re: [ovs-dev] [PATCH] ovs-save: Parse geneve tlv map correctly.

On Mon, 8 Oct 2018 at 11:12, Ben Pfaff wrote: > On Sun, Oct 07, 2018 at 09:53:15PM -0700, Gurucharan Shetty wrote: > > We now have an extra space in the o/p of `ovs-ofctl dump-tlv-map`. > > > > Fixes: 5a0e4aec1af (treewide: Convert leading tabs to spaces.) > > Signed-off-by: Gurucharan Shetty >

Re: [ovs-dev] [PATCH] dpif-netlink: fix null pointer

happen when > dpif_netlink_port_add__() is called and dpif->handlers is 0. > > Restore the old behaviour of using a zero pid when dpif->handlers is 0. > > Fixes: 69c51582f ("dpif-netlink: don't allocate per thread netlink > sockets") > Reported-by: Flavio Leitner > Rep

Re: [ovs-dev] [PATCH v2] dpif-netlink: don't allocate per thread netlink sockets

are available. Distributor ID: Ubuntu Description: Ubuntu 14.04.2 LTS Release: 14.04 Codename: trusty On Fri, 5 Oct 2018 at 16:27, Guru Shetty wrote: > > > On Tue, 25 Sep 2018 at 01:51, Matteo Croce wrote: > >> When using the kernel datapath, OVS allocates a pool of sockets to handle

Re: [ovs-dev] [PATCH v2] dpif-netlink: don't allocate per thread netlink sockets

On Tue, 25 Sep 2018 at 01:51, Matteo Croce wrote: > When using the kernel datapath, OVS allocates a pool of sockets to handle > netlink events. The number of sockets is: ports * n-handler-threads, where > n-handler-threads is user configurable and defaults to 3/4*number of cores. > > This

Re: [ovs-dev] [PATCH v2] ovn: Fix IPv6 DAD failure for container ports

On Fri, 5 Oct 2018 at 07:35, wrote: > From: Numan Siddique > > When a container port is created inside a VM, the below kernel message > is seen and IPv6 doesn't work on that interface. > > [ 138.000753] IPv6: vlan4: IPv6 duplicate address detected! > > When a container port sends a ethernet

Re: [ovs-dev] [PATCH] ovn: Fix IPv6 DAD failure for child ports

On Thu, 4 Oct 2018 at 13:29, Numan Siddique wrote: > > Thanks for the review Guru. > > Please see below for the comments. > > > > On Fri, Oct 5, 2018 at 12:09 AM Guru Shetty wrote: > >> >> >> On Mon, 17 Sep 2018 at 02:24, wrote: >> >>&g

Re: [ovs-dev] [PATCH] ovn: Fix IPv6 DAD failure for child ports

On Mon, 17 Sep 2018 at 02:24, wrote: > From: Numan Siddique > > When a child vlan interface is created inside a VM, the below kernel > message > is seen and IPv6 doesn't work on that interface. > On which interface doesn't IPv6 work? On the Vm's interface or on the container's interface? > >

Re: [ovs-dev] [PATCH v7 4/4] Replace router internal MAC with gateway MAC for reply packets

sical world and is chassis bound. But OpenStack-OVN as a client did not want to handle the complication of maintaining 2 routers. > > [1] > https://github.com/openvswitch/ovs/blob/master/Documentation/topics/high-availability.rst > > > > On Fri, Sep 21, 2018 at 9:28 PM Numan

Re: [ovs-dev] [PATCH] ovs-save: save and restore groups on restart

On Tue, 25 Sep 2018 at 14:18, Ben Pfaff wrote: > On Mon, Sep 24, 2018 at 11:18:03AM -0700, Zak Whittington wrote: > > VMware-BZ: 2192560 > > Signed-off-by: Zak Whittington > > Thanks, applied to master. > > Do we need backports for this? > Backports don't hurt. >

Re: [ovs-dev] [PATCH] ovs-save: save and restore groups on restart

On Fri, 21 Sep 2018 at 10:38, Zak Whittington wrote: > VMware-BZ: 2192560 > Signed-off-by: Zak Whittington > Acked-by: Gurucharan Shetty > --- > utilities/ovs-save | 14 +- > 1 file changed, 13 insertions(+), 1 deletion(-) > > diff --git a/utilities/ovs-save b/utilities/ovs-save

Re: [ovs-dev] [PATCH v7 4/4] Replace router internal MAC with gateway MAC for reply packets

> > > I have tried to make sense of this patch series a few times. I think > adding increasing complications like this will make gateway code > unmaintainable. The whole gateway redirect chassis already makes it > un-understandable and now this will mean that no one will be able to > understand it

Re: [ovs-dev] [PATCH v7 4/4] Replace router internal MAC with gateway MAC for reply packets

On Wed, 1 Aug 2018 at 05:18, wrote: > From: venkata anil > > Previous patches in the series doesn't address issue 1 explained in [1] > i.e > 1) removal of router gateway port MAC address on external switches >after expiring of aging time. > 2) then external switches unable to learn the

Re: [ovs-dev] [PATCH] meta-flow: Make "nw_frag" a synonym for "ip_frag".

On Thu, 20 Sep 2018 at 11:34, Ben Pfaff wrote: > Since the time that support for IP fragments was introduce, the OVS > functions that format flows have used "nw_frag", but the ones that parse > flows have expected "ip_frag". Obviously this is a bug and it's a surprise > that it's gone so long

Re: [ovs-dev] [PATCH] ovn: Fix IPv6 DAD failure for child ports

On Tue, 18 Sep 2018 at 01:25, Ben Pfaff wrote: > On Mon, Sep 17, 2018 at 02:54:10PM +0530, nusid...@redhat.com wrote: > > From: Numan Siddique > > > > When a child vlan interface is created inside a VM, the below kernel > message > > is seen and IPv6 doesn't work on that interface. > > > > [

Re: [ovs-dev] [PATCH] ovs-save: Don't always include the default flow during restore

On Sun, 9 Sep 2018 at 05:20, Timothy Redaelli wrote: > Currently the default flow (actions=NORMAL) is present in the flow table > after > the flow table is restored also when the default flow is removed. > > This commit changes the behaviour of the "ovs-save save-flows" command to > use >

Re: [ovs-dev] [PATCH] ovs-save: Don't always include the default flow during restore

On Thu, 13 Sep 2018 at 10:38, Timothy Redaelli wrote: > On Wed, 12 Sep 2018 10:36:22 -0700 > Guru Shetty wrote: > > > On Tue, 11 Sep 2018 at 09:07, Flavio Leitner wrote: > > > > > On Sun, Sep 09, 2018 at 02:20:02PM +0200, Timothy Redaelli wrote: > > >

Re: [ovs-dev] [PATCH] ovs-save: Don't always include the default flow during restore

On Sun, 9 Sep 2018 at 05:20, Timothy Redaelli wrote: > Currently the default flow (actions=NORMAL) is present in the flow table > after > the flow table is restored also when the default flow is removed. > > This commit changes the behaviour of the "ovs-save save-flows" command to > use >

Re: [ovs-dev] [PATCH] ovs-save: Don't always include the default flow during restore

On Tue, 11 Sep 2018 at 09:07, Flavio Leitner wrote: > On Sun, Sep 09, 2018 at 02:20:02PM +0200, Timothy Redaelli wrote: > > Currently the default flow (actions=NORMAL) is present in the flow table > after > > the flow table is restored also when the default flow is removed. > > > > This commit

Re: [ovs-dev] [PATCH] daemon-unix: Use same name for original or restarted children.

On Thu, 6 Sep 2018 at 10:45, Ben Pfaff wrote: > Linux has an idea of process name that is visible in /proc/$pid/comm. This > is "ovs-vswitchd" for a freshly started ovs-vswitchd process. When the > monitor code restarted a crash child, it changed it to the empty string. > This confused the

Re: [ovs-dev] Ovn-Kubernetes over multus

l be able to be connected to > different layer 2 logical networks. > > On Tue, Sep 4, 2018, 18:57 Guru Shetty wrote: > > > I think people have tried with Multus. But we do not have official > support > > for it. Someone will have to spend some time to figure out what is > need

Re: [ovs-dev] Ovn-Kubernetes over multus

I think people have tried with Multus. But we do not have official support for it. Someone will have to spend some time to figure out what is needed. On Mon, 3 Sep 2018 at 10:29, Alona Kaplan wrote: > Hi all, > > I'm KubeVirt developer and we want to examine using ovn-Kubernetes over > multus.

Re: [ovs-dev] [PATCH 1/2] windows: Add set_deatch function to daemon-windows.c

On Wed, 22 Aug 2018 at 06:24, wrote: > > On Tue, 21 Aug 2018 at 11:19, Ben Pfaff wrote: > > > > > On Tue, Aug 21, 2018 at 05:57:47PM +0300, Alin Gabriel Serdean wrote: > > > > The daemon-windows file is missing a `set_detach` routine, so add it. > > > > > > > > This will be useful in the long

Re: [ovs-dev] [PATCH 1/2] windows: Add set_deatch function to daemon-windows.c

On Tue, 21 Aug 2018 at 11:19, Ben Pfaff wrote: > On Tue, Aug 21, 2018 at 05:57:47PM +0300, Alin Gabriel Serdean wrote: > > The daemon-windows file is missing a `set_detach` routine, so add it. > > > > This will be useful in the long run. > > > > Signed-off-by: Alin Gabriel Serdean > > Thank you

Re: [ovs-dev] [ovs-discuss] ovsdb-server core dump and ovsdb corruption using raft cluster

I was able to reproduce it. I will work with Ben to get this fixed. On 26 July 2018 at 23:14, Girish Moodalbail wrote: > Hello Ben, > > Sorry, got distracted with something else at work. I am still able to > reproduce the issue, and this is what I have and what I did > (if you need the core,

Re: [ovs-dev] MPLS performance question

MTU? Big drops in performance numbers are usually because of packet fragmentation. Keep the MTU of your packet origin to, say 1450 and retry? On 31 July 2018 at 12:01, Carl Baldwin wrote: > My apologies. I failed to include the ovs version number that I'm using. It > is 2.7.3. Is there anything

Re: [ovs-dev] The “overlay” mode issue while setting up OVS with DPDK

t;> website. So it installed 2.5.4 by default. Do you want me to build and >>> install OVS? >>> >>> https://software.intel.com/en-us/articles/using-docker-conta >>> iners-with-open-vswitch-and-dpdk-on-ubuntu-1710 >>> >>> Regards, >>> S

Re: [ovs-dev] The “overlay” mode issue while setting up OVS with DPDK

a640d7cdd55', > u'external_ids:subnet=192.168.22.0/24 <http://192.168.22.0/24>', > u'external_ids:gateway_ip=192.168.22.1'] * > > > > Regards, > Sandeep > > On Mon, Jul 23, 2018 at 5:01 PM, Guru Shetty wrote: > >> Yes. >> >> On 23 July

Re: [ovs-dev] The “overlay” mode issue while setting up OVS with DPDK

Yes. On 23 July 2018 at 13:43, Sandeep Adapala wrote: > So you are saying just do the overlay part in this doc ? > http://docs.openvswitch.org/en/latest/howto/docker/#the-overlay-mode > > On Mon, Jul 23, 2018 at 4:35 PM, Guru Shetty wrote: > >> May I suggest tha

Re: [ovs-dev] The “overlay” mode issue while setting up OVS with DPDK

still learning things. So can you explain me >> what I should configure in lcore-mask and cpu-mask >> >> I have a 28 core with 10G intel NIC's >> >> Regards >> Sandeep >> >> On Mon, Jul 23, 2018 at 3:49 PM, Guru Shetty wrote: >> >>> 1. Use

Re: [ovs-dev] The “overlay” mode issue while setting up OVS with DPDK

1. Use the same IP address for both CENTRAL_IP and LOCAL_IP. And this should be the IP of your host. 2. ENCAP_TYPE="geneve". On 23 July 2018 at 12:41, Sandeep Adapala wrote: > Hello All, > > I am trying to use this doc to setup the containers using OVS-DPDK ( >

Re: [ovs-dev] Creation of network using ovs in Docker

I would suggest to create a new topic with a valid subject name to attract the dpdk folks and post it in disc...@openvswitch.org On 10 July 2018 at 13:44, Sandeep Adapala wrote: > Hello Guru, > > Now I have installed DPDK and OVS both of them are compatible with each > other but now I got stuck

Re: [ovs-dev] Creation of network using ovs in Docker

ss family not supported by protocol) > > > I am getting this error when I try to add interface > > > On Mon, Jul 9, 2018 at 3:32 PM, Sandeep Adapala < > sandeepadapal...@gmail.com> wrote: > >> Let me try with 2.9.2 Guru. >> >> On Mon, Jul 9, 2018 at 3:2

Re: [ovs-dev] Creation of network using ovs in Docker

> --log-file=/var/log/openvswitch/ovsdb-server.log > --pidfile=/var/run/openvswitch/ovsdb-server.pid --detach --monitor > ubuntu 10124 9325 0 14:42 pts/500:00:00 grep --color=auto ovsdb-server > ubuntu@tbserver14:~$ > > > On Mon, Jul 9, 2018 at 2:24 PM, Guru Shetty

Re: [ovs-dev] Creation of network using ovs in Docker

caabc22601b17134a4c54cc33be18 > ovn-nbctl: tcp:192.168.14.33:6642: database connection failed (Connection > refused) > ubuntu@tbserver14:~$ > > > On Mon, Jul 9, 2018 at 2:22 PM, Guru Shetty wrote: > >> Run "/usr/share/openvswitch/scripts/ovn-ctl restart_northd"

Re: [ovs-dev] Creation of network using ovs in Docker

t; > ovs-vsctl set Open_vSwitch . \ > external_ids:ovn-remote="tcp:192.168.14.33:6642" \ > external_ids:ovn-nb="tcp:192.168.14.33:6641" \ > external_ids:ovn-encap-ip=192.168.14.33 \ > external_ids:ovn-encap-type=geneve > I don't have a remote serve

Re: [ovs-dev] Creation of network using ovs in Docker

--version; ovn-nbctl --version > ovs-vsctl (Open vSwitch) 2.5.4 > Compiled Oct 30 2017 10:38:01 > DB Schema 7.12.1 > ovn-nbctl (Open vSwitch) 2.5.4 > Compiled Oct 30 2017 10:38:01 > DB Schema 2.0.1 > > OVN plugin is also the same version. > > > Regards, > > San

Re: [ovs-dev] Creation of network using ovs in Docker

On 9 July 2018 at 09:33, Sandeep Adapala wrote: > Hello All, > > I am planning to have 2 containers talk to each other using ovs-dpdk > interface on a same host. this is how I started installing OVN on Docker. > > http://docs.openvswitch.org/en/latest/howto/docker/#the-overlay-mode > > I was

Re: [ovs-dev] [PATCH v2] OVN: do not mark ND packets for conntrack in PRE_LB stage

On 1 June 2018 at 04:05, Lorenzo Bianconi wrote: > Do not send Neighbor Discovery packets to conntrack module if > load balancing rules have been added to NB db since otherwise > Neighbor Advertisement frames will be discarded by OVN. > In order to reproduce the issue it is enough to add 2

Re: [ovs-dev] [patch v1] ovn: Fix gateway load balancing.

On 27 June 2018 at 18:49, Darrell Ball wrote: > Non-distributed and distributed gateway load balancing is broken. > Recent changes for port unreachable handling broke the associated > unsnat functionality. > > Fixes: 86558ac2e476 ("OVN: add UDP port unreachable support to OVN > logical

Re: [ovs-dev] [patch v2] ovn: Fix gateway load balancing.

> > > > After a bit of chewing on the finer grained filtering question, I take back > the above suggestion regarding "lb_force_snat_ip", as it will not work > in all cases. Implementing finer grained filtering would involve checking > several pieces of information; I am not sure it is worth the

Re: [ovs-dev] [patch v2] ovn: Fix gateway load balancing.

On 28 June 2018 at 11:44, Han Zhou wrote: > Hi Mark, what I meant is the test for the feature of LB in Gateway. If we > had a test case, the problem would have been noticed when Lorenzo is > working on ICMP feature. > We have a few test cases. The tests weren't run likely as they are system

Re: [ovs-dev] gateway logic question (was: Re: [PATCH v2 1/5] ovsdb-idl: Redesign use of indexes.)

There are 2 types of gateways in OVN - a "gateway router" and a "distributed gateway router port". The latter is where BFD is used and has been mostly been maintained by the OpenStack folks. I am adding the original authors for comment. I am not very familiar with the latter implementation. On 12

Re: [ovs-dev] [PATCH] utilities/ovs-ctl: Force removal of ip_gre/gre

On 31 May 2018 at 14:20, Greg Rose wrote: > On Linux kernels older than 4.16 the user cannot take advantage of > OVS ERSPAN features if the older ip_gre and gre kernel modules are > loaded. In addition, the openvswitch kernel module will fail to > load because it cannot grab the IPPROTO_GRE

Re: [ovs-dev] [PATCH] OVN: do not mark ND packets for conntrack in PRE_LB stage

On 31 May 2018 at 08:05, Lorenzo Bianconi wrote: > Do not send Neighbor Discovery packets to conntrack module if > load balancing rules have been added to NB db since otherwise > Neighbor Advertisement frames will be discarded by OVN. > In order to reproduce the issue it is enough to add 2

Re: [ovs-dev] Regarding VLAN and source code compilation - Team Please reply !

On 4 May 2018 at 06:20, rakesh kumar wrote: > Hello Team, > > I am very new to ovs, Start with http://docs.openvswitch.org/en/latest/ ___ dev mailing list d...@openvswitch.org

Re: [ovs-dev] [PATCH 1/2] ovn: support applying ACLs to port groups

port groups directly instead of > applying to each related lswitch individually. It provides convenience > for clients such as k8s and OpenStack Neutron. > > Requested-at: https://mail.openvswitch.org/pipermail/ovs-dev/2018-March/ > 344856.html > Requested-by: Guru Shetty <g.

Re: [ovs-dev] How OVS is currently being used with Core Network emulator - Please reply

Hello Rakesh, It is unlikely anyone in this list knows what a "Core Network emulator " is. OVS is a production grade virtual switch and used in real environments. mininet is a popular "simulator" that uses OVS. But you won't get answers around that topic here. You should head to a mininet

Re: [ovs-dev] [PATCH] rhel/systemd: Prevent deletion of runtime directory.

On 4 April 2018 at 08:13, Aaron Conole wrote: > Gurucharan Shetty writes: > > > Currently, when we do a 'service openvswitch stop', > > '/var/run/openvswitch' gets deleted. This is a problem > > if you have other users (like OVN) using the same > > runtime

Re: [ovs-dev] [PATCH] ovn: Recirculate packets after a unSNAT.

On 4 April 2018 at 14:47, Ben Pfaff wrote: > On Mon, Mar 26, 2018 at 02:18:28PM -0700, Gurucharan Shetty wrote: > > commit f6fabcc6245 (ofproto-dpif: Mark packets as "untracked" > > after call to ct().) changed the behavior after a call to ct(). > > The +trk bit would automatically

Re: [ovs-dev] [PATCH 3/3] rhel: add "force-reload-kmod" support in "ovs-systemd-reload"

On 11 April 2018 at 11:03, Timothy Redaelli <tredae...@redhat.com> wrote: > On Wed, 11 Apr 2018 10:05:53 -0700 > Guru Shetty <g...@ovn.org> wrote: > > > On 22 December 2017 at 07:00, Timothy Redaelli <tredae...@redhat.com> > > wrote: > > > &g

Re: [ovs-dev] [PATCH 3/3] rhel: add "force-reload-kmod" support in "ovs-systemd-reload"

On 22 December 2017 at 07:00, Timothy Redaelli wrote: > Since you can't use "ovs-ctl force-reload-kmod" on Fedora/RHEL, due to > systemd dependencies, this commit adds the "force-reload-kmod" feature on > ovs-systemd-reload. > > Signed-off-by: Timothy Redaelli

Re: [ovs-dev] [PATCH 1/2] ovn: Support port groups in ACLs

On 1 March 2018 at 15:43, Han Zhou <zhou...@gmail.com> wrote: > > > On Thu, Mar 1, 2018 at 12:26 PM, Guru Shetty <g...@ovn.org> wrote: > > > > > > > > On 1 March 2018 at 12:21, Han Zhou <zhou...@gmail.com> wrote: > >> > >>

Re: [ovs-dev] [PATCH 1/2] ovn: Support port groups in ACLs

On 1 March 2018 at 12:21, Han Zhou <zhou...@gmail.com> wrote: > > > On Thu, Mar 1, 2018 at 12:13 PM, Guru Shetty <g...@ovn.org> wrote: > > > > > > > > On 28 February 2018 at 19:37, Han Zhou <zhou...@gmail.com> wrote: > >> > >&

Re: [ovs-dev] [PATCH 1/2] ovn: Support port groups in ACLs

On 28 February 2018 at 19:37, Han Zhou wrote: > This patch enables using port group names in ACL match conditions. > Users can create a port group in northbound DB Port_Group table, > and then use the name of the port group in ACL match conditions > for "inport" or "outport".

Re: [ovs-dev] [PATCH v3] ovn-controller: Support multiple gateway port on a distributed router

This is a little more complicated for a quick review. I think it will need a round from me to understand the implications for gateway routers and one round from Numan (or someone from openstack) that use distributed gateway routers. On 14 February 2018 at 16:42, Ben Pfaff wrote: >

Re: [ovs-dev] [PATCH] ovn-northd: Support logical router port with config CIDR, such as 192.168.1.0/24.

On 6 February 2018 at 20:21, Guoshuai Li wrote: > Support logical router port who is gateway can configure CIDR whitout IP > address, > so as to save the public network IP when connecting to the external > network. > > With this configuration, the gateway's default snat

Re: [ovs-dev] [PATCH] Drop support for RHEL 5 and 6

and try and get a schedule going to move to systemd. > > fbl > > > On Wed, Jan 17, 2018 at 08:48:13AM -0500, Russell Bryant wrote: > > OK - fine with me. > > > > So an alternative patch would be to document that this spec is now > > just an alternative

Re: [ovs-dev] [PATCH V2] rhel: Ensure proper OVS kernel modules load after upgrade

On 16 January 2018 at 08:44, Greg Rose wrote: > Add post install and post un-install scripts to make sure that the > openvswitch kernel modules are correctly written with the weak-modules > utility. This ensures that after an upgrade to a newer kernel the > correct

Re: [ovs-dev] [PATCH V2 2/2] rhel: Add post installation check for kernel modules

On 12 January 2018 at 10:16, Gregory Rose <gvrose8...@gmail.com> wrote: > On 1/12/2018 9:37 AM, Guru Shetty wrote: > > > > On 12 January 2018 at 08:37, Greg Rose <gvrose8...@gmail.com> wrote: > >> A bug in RHEL 7.2 has been found in which a customer who instal

Re: [ovs-dev] [PATCH V2 2/2] rhel: Add post installation check for kernel modules

On 12 January 2018 at 08:37, Greg Rose wrote: > A bug in RHEL 7.2 has been found in which a customer who installed > a RHEL 7.2 openvswitch kernel module rpm with a slightly different > minor build number than the running kernel found that the kernel > modules were

Re: [ovs-dev] [PATCH V2 1/2] rhel: Add depmod file for openvswitch module search

On 12 January 2018 at 08:37, Greg Rose wrote: > From: Gurucharan Shetty > > There are occasions when an openvswitch kernel module rpm which does > not match the exact build number of the running kernel. In that > case the openvswitch kernel modules

Re: [ovs-dev] [PATCH] ofp-print: Include full hex dump of messages that fail decode.

On 4 January 2018 at 22:40, Ben Pfaff wrote: > In debugging issues with a controller that appears to send invalid > OpenFlow messages, it can be difficult to actually see the important > details of those messages, because OpenFlow message logging (in the vconn > log module) will

  1   2   3   >