On Wed, Aug 9, 2023 at 9:38 AM wrote:
>
> From: Numan Siddique
>
Thanks Numan for the enhancement.
> Instead of maintaing the lport to lflow references using
> 'struct lflow_ref_list', this patch makes use of the existing
> objdep APIs. Since objdep_mgr is not thread safe, an instance
> of objd
When the a revalidator thread is updating statistics for an XC_LEARN
xcache entry in xlate_push_stats_entry it uses ofproto_flow_mod_learn.
The revalidator will update stats for rules even if they are in a
removed state or marked as invisible. However, ofproto_flow_mod_learn
will detect if a flow h
Hi everyone,
As I announced a few weeks ago, the soft freeze date for OVN 23.09 is
tomorrow, 18 August, 2023. This is the final date that patches for new
features may be submitted for inclusion in OVN 23.09.
The OVN team will spend the next two weeks attempting to get those
patches merged. T
Hi Dumitru,
I had a look through the series, and it looks good to me.
Acked-by: Mark Michelson
On 8/10/23 08:44, Dumitru Ceara wrote:
This series cleans up, factors out and then adds incremental processing
support to the code that processes port group updates in ovn-northd.
Some performance
On Thu, Aug 17, 2023 at 9:42 PM Han Zhou wrote:
>
> On Thu, Aug 17, 2023 at 12:05 AM wrote:
> >
> > From: Numan Siddique
> >
> > When changes to port bindings corresponding to router ports are
> > handled by northd engine node, incorrect warning logs (like below)
> > are logged.
> >
> >
> >
Currently a bond will not always revalidate when an active member
changes. This can result in counter-intuitive behaviors like the fact
that using ovs-appctl bond/set-active-member will cause the bond to
revalidate but changing other_config:bond-primary will not trigger a
revalidate in the bond.
W
On Wed, Aug 16, 2023 at 4:18 PM Ilya Maximets wrote:
>
> On 8/9/23 19:00, Mike Pattrick wrote:
> > Currently a bond will not always revalidate when an active member
> > changes. This can result in counter-intuitive behaviors like the fact
> > that using ovs-appctl bond/set-active-member will cause
On Thu, Aug 17, 2023 at 2:13 AM Ales Musil wrote:
>
>
>
> On Wed, Aug 16, 2023 at 2:56 AM Han Zhou wrote:
>>
>> Commit 1eb09838 fixed an incremental processing problem by falling back
>> to recompute. The problem was handling VIF changes for a LS that
>> has router ports when:
>> - adding the fir
On Thu, Aug 17, 2023 at 12:05 AM wrote:
>
> From: Numan Siddique
>
> When changes to port bindings corresponding to router ports are
> handled by northd engine node, incorrect warning logs (like below)
> are logged.
>
>
> northd|WARN|A port-binding for lrp0 is created but the LSP is not foun
On 8/17/23 17:16, Eelco Chaudron wrote:
>
>
> On 17 Aug 2023, at 15:25, Ilya Maximets wrote:
>
>> According to our release process, it's time to release v3.2.0!
>>
>> Ilya Maximets (2):
>> Set release date for 3.2.0.
>> Prepare for 3.2.1.
>
>
> Ack on the series!
>
> Acked-by: Eelco Chaud
On 8/17/23 12:43, Ales Musil wrote:
> On Wed, Aug 16, 2023 at 10:42 PM Dumitru Ceara wrote:
>
>> This is beneficial in a few ways:
>> - first, it reduces the number of different types of data the northd
>> I-P node has to process.
>> - it turns out the northd I-P node (whose recompute is rather
This is beneficial in a few ways:
- first, it reduces the number of different types of data the northd
I-P node has to process.
- it turns out the northd I-P node (whose recompute is rather costly)
doesn't really depend on meters or ACLs.
- prepares the ground for a pure I-P implementation for
Use the band_cmp() function instead of duplicating code. Also simplify
some of the band related code.
Suggested-by: Ales Musil
Signed-off-by: Dumitru Ceara
---
northd/northd.c | 22 --
1 file changed, 4 insertions(+), 18 deletions(-)
diff --git a/northd/northd.c b/northd
Changes in V2:
- Refactored a bit the meter code and added that as first patch.
Dumitru Ceara (2):
northd: Refactor meter code to avoid duplication.
northd: Add a separate I-P node for handling meters.
lib/stopwatch-names.h| 1 +
northd/automake.mk | 2 +
northd/en-lfl
On 17 Aug 2023, at 15:25, Ilya Maximets wrote:
> According to our release process, it's time to release v3.2.0!
>
> Ilya Maximets (2):
> Set release date for 3.2.0.
> Prepare for 3.2.1.
Ack on the series!
Acked-by: Eelco Chaudron
___
dev mail
On 8/17/23 15:36, 0-day Robot wrote:
> 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:
> error: Failed to merge in the changes.
> hi
Thanks Dumitru for the efforts!
> On 15 Aug 2023, at 13:39, Dumitru Ceara wrote:
>
> On 8/14/23 00:24, Han Zhou wrote:
>> On Fri, Aug 11, 2023 at 5:25 AM Dumitru Ceara wrote:
>>>
>>> It's safe to assume that tables that existed in the previous LTS branch
>>> first release (currently 22.03.0) c
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:
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the fai
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.
Patch skipped due to previous failure.
Please check this out. If you feel there has been an error, pleas
On Thu, Aug 17, 2023 at 03:25:03PM +0200, Ilya Maximets wrote:
> According to our release process, it's time to release v3.2.0!
>
> Ilya Maximets (2):
> Set release date for 3.2.0.
> Prepare for 3.2.1.
>
> NEWS | 5 -
> configure.ac | 2 +-
> debian/changelog | 8 +++-
Signed-off-by: Ilya Maximets
---
NEWS | 3 +++
configure.ac | 2 +-
debian/changelog | 6 ++
3 files changed, 10 insertions(+), 1 deletion(-)
diff --git a/NEWS b/NEWS
index a3a5c2e4a..790cab495 100644
--- a/NEWS
+++ b/NEWS
@@ -1,3 +1,6 @@
+v3.2.1 - xx xxx
+--
According to our release process, it's time to release v3.2.0!
Ilya Maximets (2):
Set release date for 3.2.0.
Prepare for 3.2.1.
NEWS | 5 -
configure.ac | 2 +-
debian/changelog | 8 +++-
3 files changed, 12 insertions(+), 3 deletions(-)
--
2.40.1
Signed-off-by: Ilya Maximets
---
NEWS | 2 +-
debian/changelog | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/NEWS b/NEWS
index 1438f9f8d..a3a5c2e4a 100644
--- a/NEWS
+++ b/NEWS
@@ -1,4 +1,4 @@
-v3.2.0 - xx xxx
+v3.2.0 - 17 Aug 2023
On 8/17/23 12:03, Ilya Maximets wrote:
> On 8/17/23 09:31, Dumitru Ceara wrote:
>> On 8/17/23 00:26, Ilya Maximets wrote:
>>> This fixes the obsolescence warning for AC_TRY_RUN with autoconf 2.70+:
>>>
>>> $ ./boot.sh
>>> configure.ac:141: warning: The macro `AC_TRY_RUN' is obsolete.
>>> conf
On 8/17/23 11:31, Ales Musil wrote:
> On Thu, Aug 17, 2023 at 12:26 AM Ilya Maximets wrote:
>
>> autoconf 2.70+ complais about these obsolete macros.
>> Replacements are available in our baseline 2.63, so
>> use them instead.
>>
>> It also complains about AC_PROG_CC_C99, but I'm not
>> sure if we
On Wed, Aug 16, 2023 at 10:42 PM Dumitru Ceara wrote:
> This is beneficial in a few ways:
> - first, it reduces the number of different types of data the northd
> I-P node has to process.
> - it turns out the northd I-P node (whose recompute is rather costly)
> doesn't really depend on meters
On 8/17/23 09:31, Dumitru Ceara wrote:
> On 8/17/23 00:26, Ilya Maximets wrote:
>> This fixes the obsolescence warning for AC_TRY_RUN with autoconf 2.70+:
>>
>> $ ./boot.sh
>> configure.ac:141: warning: The macro `AC_TRY_RUN' is obsolete.
>> configure.ac:141: You should run autoupdate.
>> .
On Thu, Aug 17, 2023 at 12:26 AM Ilya Maximets wrote:
> autoconf 2.70+ complais about these obsolete macros.
> Replacements are available in our baseline 2.63, so
> use them instead.
>
> It also complains about AC_PROG_CC_C99, but I'm not
> sure if we want to or how to correctly replace it.
> Sug
On Wed, Aug 16, 2023 at 2:56 AM Han Zhou wrote:
> Commit 1eb09838 fixed an incremental processing problem by falling back
> to recompute. The problem was handling VIF changes for a LS that
> has router ports when:
> - adding the first switch port to the LS, or
> - deleting the last switch port fr
On Thu, Jul 20, 2023 at 5:02 PM Lorenzo Bianconi <
lorenzo.bianc...@redhat.com> wrote:
> When using VLAN backed networks and OVN routers leveraging the
> 'ovn-chassis-mac-mappings' option for east-west traffic, the eth.src field
> is
> replaced by the chassis mac address in order to not expose the
On 8/17/23 00:26, Ilya Maximets wrote:
> This fixes the obsolescence warning for AC_TRY_RUN with autoconf 2.70+:
>
> $ ./boot.sh
> configure.ac:141: warning: The macro `AC_TRY_RUN' is obsolete.
> configure.ac:141: You should run autoupdate.
> ./lib/autoconf/general.m4:2997: AC_TRY_RUN is e
From: Numan Siddique
When changes to port bindings corresponding to router ports are
handled by northd engine node, incorrect warning logs (like below)
are logged.
northd|WARN|A port-binding for lrp0 is created but the LSP is not found.
Fix these warnings.
Fixes: 3b120ccf7f7c ("north
On Thu, Aug 17, 2023 at 11:47 AM Han Zhou wrote:
>
> On Wed, Aug 16, 2023 at 1:27 AM wrote:
> >
> > From: Numan Siddique
> >
> > When changes to port bindings corresponding to router ports are
> > handled by northd engine node, incorrect warning logs (like below)
> > are logged.
> >
> >
> >
33 matches
Mail list logo
