The Python IDL implementation supports ovsdb cluster connections.
This patch is a follow up to commit 31e434fc98, it adds the option of
connecting to the leader (the default) in the Raft-based cluster. It mimics
the exisiting C IDL support for clusters introduced in commit 1b1d2e6daa.
The _Server
Thanks for taking a look. I will send a revised patch that addresses both
issues you
pointed to, in particular backward compatibility with _Server-less ovsdbs.
Thanks,
Ted
On 12/27/18, 9:23 AM, "Ben Pfaff" wrote:
On Tue, Dec 18, 2018 at 12:18:06AM +, Ted Elhourani wrote:
> The Py
On 01/03/2019 12:36 PM, Nitin Katiyar wrote:
> Port rx queues that have not been statically assigned to PMDs are currently
> assigned based on periodically sampled load measurements.
> The assignment is performed at specific instances – port addition, port
> deletion, upon reassignment request via
Hi Martin,
Sorry the delay, coming back from PTO and holidays.
On Thu, Dec 13, 2018 at 02:50:22PM -0800, Martin Xu wrote:
> Hi Flavio,
>
> I remember when we had a discussion about package "succession" when I had
> the "Obsoletes" tag added in one of the previous patches submitted for the
> fedo
From: Numan Siddique
Signed-off-by: Numan Siddique
---
ovn/northd/ovn-northd.8.xml | 83 +-
ovn/northd/ovn-northd.c | 89 ++-
tests/ovn.at| 165
3 files changed, 331 insertions(+), 6 deletions(-)
diff --
From: Numan Siddique
Previous commit added a new OVS action 'check_pkt_larger'. This
patch supports that action in OVN. The syntax to use this would be
reg0[0] = check_pkt_larger(LEN)
Upcoming commit will make use of this action in ovn-northd and
will generate an ICMP4 packet if the packet leng
From: Numan Siddique
In order to support OVN specific fields (which are not yet
supported in OpenvSwitch to set or modify values) a generic
OVN field support is added in this patch. These OVN fields are
expected to be used as nested OVN actions inside OVN actions
like icmp4, icmp6 etc. This patch
From: Numan Siddique
This patch adds a new action 'check_pkt_larger' which checks if the
packet is larger than the given size and stores the result in the
destination register.
Usage: check_pkt_larger:len->REGISTER
Eg. match=...,actions=check_pkt_larger:1442->NXM_NX_REG0[0],next;
This patch mak
From: Numan Siddique
[Please note, this patch is submitted as RFC in ovs-dev ML to
get feedback before submitting to netdev ML]
This patch adds a new action which checks the packet length and
executes a set of actions if the packet length is greater than
the specified length or executes another
From: Numan Siddique
This is an RFC series to address the MTU issues for OVN reported
here [1].
To address this issue, a new OVS action - check_pkt_larger is added.
A new datapath action is also added - check_pkt_len.
The datapath patch is submitted here to get feedback before submitting
to the
On Thu, Jan 03, 2019 at 10:11:29AM -0500, Aaron Conole wrote:
> Aaron Conole writes:
>
> > Ben Pfaff writes:
> >
> >> On Thu, Dec 20, 2018 at 01:22:18PM -0500, Aaron Conole wrote:
> >>> Kevin Traynor writes:
> >>>
> >>> > On 12/19/2018 08:23 AM, Darrell Ball wrote:
> >>> >> On Tue, Dec 18, 201
0-day Robot writes:
> Bleep bloop. Greetings Ilya Maximets, 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
> (tmp/cirrus-c
Aaron Conole writes:
> Ben Pfaff writes:
>
>> On Thu, Dec 20, 2018 at 01:22:18PM -0500, Aaron Conole wrote:
>>> Kevin Traynor writes:
>>>
>>> > On 12/19/2018 08:23 AM, Darrell Ball wrote:
>>> >> On Tue, Dec 18, 2018 at 6:57 PM 0-day Robot wrote:
>>> >>
>>> >>> Bleep bloop. Greetings Darrell
Nitin Katiyar writes:
> Port rx queues that have not been statically assigned to PMDs are currently
> assigned based on periodically sampled load measurements.
> The assignment is performed at specific instances – port addition, port
> deletion, upon reassignment request via CLI etc.
>
> Due to c
Port rx queues that have not been statically assigned to PMDs are currently
assigned based on periodically sampled load measurements.
The assignment is performed at specific instances – port addition, port
deletion, upon reassignment request via CLI etc.
Due to change in traffic pattern over time
On 1/2/2019 9:27 PM, Ben Pfaff wrote:
> On Wed, Jan 02, 2019 at 05:52:20PM +, Eli Britstein wrote:
>> On 1/2/2019 6:02 PM, Ben Pfaff wrote:
>>> On Wed, Jan 02, 2019 at 03:23:14PM +, Eli Britstein wrote:
Hello,
Simple bridge, with 2 ports:
ovs-vs
Oh and I forgot to mention that we are seeing this issue on OVS versions 2.5.0
and 2.5.2.
thanks
Ani
On Jan 3, 2019, 1:10 PM +0530, Ani Sinha , wrote:
Hi Ben:
In order to reproduce, please put the node in a network with flood of ARP
broadcast packets, for example in an environment where machin
17 matches
Mail list logo
