[ovs-dev] [PATCH RFC] ofproto-dpif: Expose datapath's capability to ovsdb.

The patch adds support for fetching the datapath's capabilities from the result of 'check_support()', and write the supported capability to a new database column, called 'capabilities' under Datapath table. To see how it works, run: # ovs-vsctl -- add-br br0 -- set Bridge br0

Re: [ovs-dev] [PATCH 1/3] Update project name in RST file headers.

On Fri, Sep 20, 2019 at 03:35:08PM -0400, Russell Bryant wrote: > All of the RST files referred to "Open vSwitch documentation". Do a > big search and replace to change this to "OVN documentation" since OVN > is now in its own repository. > > I started doing this by hand in a handful of files as

[ovs-dev] [PATCH 1/3] Update project name in RST file headers.

All of the RST files referred to "Open vSwitch documentation". Do a big search and replace to change this to "OVN documentation" since OVN is now in its own repository. I started doing this by hand in a handful of files as I modified them. I figured I'd just do an automated bulk pass at it

Re: [ovs-dev] [PATCH 2/3] Remove the OVS charter.

On Fri, Sep 20, 2019 at 03:35:09PM -0400, Russell Bryant wrote: > Since OVN has been split out from OVS and is now hosted under its own, > independent github org, the OVS project charter is no longer > applicable. Formal governance under the LF or something similar would > be set up separately

Re: [ovs-dev] [PATCH 3/3] Acknowledge that OVN committers are a new group.

On Fri, Sep 20, 2019 at 03:35:10PM -0400, Russell Bryant wrote: > The MAINTAINRES.rst and related files still discussed the OVS > committers group. Since OVN was split out into its own repository, > the group of people with commit rights to OVN is different, and has > evolved to include a couple

Re: [ovs-dev] [PATCH] fatal-signal: Catch SIGSEGV and print backtrace.

On Wed, Sep 18, 2019 at 04:27:46PM -0700, Ben Pfaff wrote: > On Wed, Sep 18, 2019 at 01:16:37PM -0700, William Tu wrote: > > Thanks for the feedback. > > > > On Wed, Sep 18, 2019 at 11:30 AM Ben Pfaff wrote: > > > > > > On Tue, Sep 17, 2019 at 04:13:24PM -0700, William Tu wrote: > > > > The

[ovs-dev] [PATCH 2/3] Remove the OVS charter.

Since OVN has been split out from OVS and is now hosted under its own, independent github org, the OVS project charter is no longer applicable. Formal governance under the LF or something similar would be set up separately from OVS. Signed-off-by: Russell Bryant ---

Re: [ovs-dev] [PATCH 1/3] Update project name in RST file headers.

Bleep bloop. Greetings Russell Bryant, I am a robot and I have tried out your patch. Thanks for your contribution. I encountered some error that I wasn't expecting. See the details below. git-am: fatal: sha1 information is lacking or useless (Documentation/faq/contributing.rst). Repository

Re: [ovs-dev] [PATCHv2] stream_ssl: fix important memory leak in ssl_connect() function

Hi Ben, I'm not the co-author of this patch, I'm just sending for the original author. Please remove me, thanks William On Fri, Sep 20, 2019 at 10:01 AM 0-day Robot wrote: > > Bleep bloop. Greetings William Tu, I am a robot and I have tried out your > patch. > Thanks for your contribution. > >

[ovs-dev] [PATCH 3/3] Acknowledge that OVN committers are a new group.

The MAINTAINRES.rst and related files still discussed the OVS committers group. Since OVN was split out into its own repository, the group of people with commit rights to OVN is different, and has evolved to include a couple of people that were not previously OVS committers. This change aims to

Re: [ovs-dev] [PATCH] fatal-signal: Catch SIGSEGV and print backtrace.

On Fri, Sep 20, 2019 at 10:28:36AM -0700, William Tu wrote: > On Wed, Sep 18, 2019 at 04:27:46PM -0700, Ben Pfaff wrote: > > On Wed, Sep 18, 2019 at 01:16:37PM -0700, William Tu wrote: > > > Thanks for the feedback. > > > > > > On Wed, Sep 18, 2019 at 11:30 AM Ben Pfaff wrote: > > > > > > > > On

Re: [ovs-dev] [PATCH v2 python3 0/6] Remove Python 2 support

On Fri, Sep 20, 2019 at 11:09:55AM +0530, Numan Siddique wrote: > I tested this series and it builds fine for me. > Acked-by: Numan Siddique for the whole series with > one correction in patch 4 - which I replied separately. Thank you for the reviews and especially for the fix. I had applied

Re: [ovs-dev] [PATCH] configure: Properly handle case where sphinx-build is not available.

On Fri, Sep 20, 2019 at 05:34:29PM -0700, Justin Pettit wrote: > > > On Sep 20, 2019, at 12:00 PM, Ben Pfaff wrote: > > > > Reported-by: Justin Pettit > > Fixes: ab4514890587 ("Recommend Sphinx from Python 3 in documentation and > > packaging.") > > Signed-off-by: Ben Pfaff > > Acked-by:

Re: [ovs-dev] [PATCH v2.11] ovn-ctl: Support passing ssl certs for northd

Bleep bloop. Greetings aginwala aginwala, I am a robot and I have tried out your patch. Thanks for your contribution. I encountered some error that I wasn't expecting. See the details below. git-am: Failed to merge in the changes. Patch failed at 0001 ovn-ctl: Support passing ssl certs for

[ovs-dev] [PATCH] configure: Properly handle case where sphinx-build is not available.

Reported-by: Justin Pettit Fixes: ab4514890587 ("Recommend Sphinx from Python 3 in documentation and packaging.") Signed-off-by: Ben Pfaff --- m4/openvswitch.m4 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/m4/openvswitch.m4 b/m4/openvswitch.m4 index

[ovs-dev] [PATCH v2.11] ovn-ctl: Support passing ssl certs for northd

From: Aliasgar Ginwala When using ssl mode for ovn nb/sb active-standby/cluster db service models, northd can use ssl mode too. e.g. one can pass --ovn-northd-ssl-key, --ovn-northd-ssl-ca-cert and --ovn-northd-ssl-cert to start northd with ssl Signed-off-by: Aliasgar Ginwala Acked-by: Han

Re: [ovs-dev] [PATCH] configure: Properly handle case where sphinx-build is not available.

> On Sep 20, 2019, at 12:00 PM, Ben Pfaff wrote: > > Reported-by: Justin Pettit > Fixes: ab4514890587 ("Recommend Sphinx from Python 3 in documentation and > packaging.") > Signed-off-by: Ben Pfaff Acked-by: Justin Pettit --Justin ___ dev

[ovs-dev] You got caught.

Hello! I know, you may wondering what is with this message, so let me explain. I know you use to watch adult content on your phone... quite often I could say... and what you don't know is the fact that I got you recorded while you satysfing yourself haha. So how I did this? Well, it's my job.

Re: [ovs-dev] [Branch 2.9 Patch] compat: Fixup ipv6 fragmentation on 4.9.135+ kernels

> > > > I'll be able to provide the patches but you will need to test them > > since I no longer have an > > environment that will build branches older than 2.8.  I'll post > > patches for 2.8, 2.7 and 2.6 > > in a bit. > > The patches are posted Vishal, please test and review. > Thanks Greg. I

Re: [ovs-dev] [PATCH 1/1] stream_ssl: fix important memory leak in ssl_connect() function

On Wed, Sep 18, 2019 at 09:26:34AM -0700, Ben Pfaff wrote: > On Mon, Sep 16, 2019 at 04:44:11PM -0700, William Tu wrote: > > On Mon, Sep 16, 2019 at 12:20 AM Damijan Skvarc > > wrote: > > > > > > Hi William and thanks for your review. > > > I agree with your proposed changes. > > > Is there

[ovs-dev] [PATCHv2] stream_ssl: fix important memory leak in ssl_connect() function

From: Damijan Skvarc While checking valgrind reports after running "make check-valgrind" I have noticed reports for several tests similar to the following: ==5345== Memcheck, a memory error detector ==5345== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al. ==5345== Using

Re: [ovs-dev] [PATCH 01/10] raft: Free leaked json data

I applied this series to master. I'm looking at backports now. ___ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Re: [ovs-dev] [PATCHv2] stream_ssl: fix important memory leak in ssl_connect() function

Bleep bloop. Greetings William Tu, I am a robot and I have tried out your patch. Thanks for your contribution. I encountered some error that I wasn't expecting. See the details below. checkpatch: WARNING: Unexpected sign-offs from developers who are not authors or co-authors or committers: