From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: "DERUMIER, Alexandre" <alexandre.derumier@groupe-cyllene.com>,
"pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH 1/4] frr: bump from 8.5.2 to 10.2.1
Date: Tue, 11 Mar 2025 15:11:05 +0100 [thread overview]
Message-ID: <9c776de3-4115-42c9-a6b8-4fe65216f259@proxmox.com> (raw)
In-Reply-To: <b071a6e9d7e234a14eddabf4f7bd3ce1dbd6167c.camel@groupe-cyllene.com>
Hi Alexandre,
On 11/03/2025 11:56, DERUMIER, Alexandre wrote:
> Personally, I would wait for major pve9 before bumping frr,
>
> because from my experience, I had a lot of regression with frr, (really
> a lot ^_^)
Yeah, it's definitively a bigger jump, but having late PVE 8 and future
PVE 9 start out with the same FRR version would be nice and should make
backporting fixes easier; also PVE 9 should then start out more stable
w.r.t. FRR and SDN stack. And yes, we looked into backporting some patches
that Gabriel needs for the SDN Fabrics work to the FRR version we had,
but too much changed. Also, IIRC updating FRR to newer minor version
releases (e.g., from 8.5.2 to 8.5.7) often caused also some regressions,
so a bigger jump should make addressing those at least a bit more
worthwile; at least that's what I'm hoping ^^
FYI: I just uploaded the build to the pvetest repository, would move it
to no-subscription sometime next week, if nothing comes up until then.
I can naturally delay the move, or fasten it up, depending on your
feedback or if you would like to have some more time, I just would like
to move it to no-subscription no later than the 28th March, to ensure it
gets long enough time for broad exposure in no-subscription before the
next point releases.
> and this really need a lot of test with different setup to be sure
> everything is working fine with differents setup.
>
>
> I can begin to do test on my production with this version if it can
> help
That would be really appreciated, thanks.
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-03-11 14:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 12:29 Gabriel Goller
2025-03-07 12:29 ` [pve-devel] [PATCH 2/4] frr: port patches to latest stable version, add topotests Gabriel Goller
2025-03-07 12:29 ` [pve-devel] [PATCH 3/4] frr: add the dummy_as_loopback patch series, enable it by default Gabriel Goller
2025-03-07 12:29 ` [pve-devel] [PATCH 4/4] debian: update changelog Gabriel Goller
2025-03-07 12:31 ` [pve-devel] [PATCH 1/4] frr: bump from 8.5.2 to 10.2.1 Gabriel Goller
2025-03-11 10:56 ` DERUMIER, Alexandre via pve-devel
2025-03-11 13:27 ` Gabriel Goller
[not found] ` <b071a6e9d7e234a14eddabf4f7bd3ce1dbd6167c.camel@groupe-cyllene.com>
2025-03-11 14:11 ` Thomas Lamprecht [this message]
2025-03-11 16:16 ` DERUMIER, Alexandre via pve-devel
2025-03-07 14:06 ` [pve-devel] applied-series: " Thomas Lamprecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9c776de3-4115-42c9-a6b8-4fe65216f259@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=alexandre.derumier@groupe-cyllene.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal