From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Hannes Laimer <h.laimer@proxmox.com>
Subject: Re: [PATCH docs/manager/network/proxmox{-ve-rs,-perl-rs} v6 0/9] sdn: add BGP fabric
Date: Mon, 18 May 2026 12:20:37 +0200 [thread overview]
Message-ID: <177909919151.3110381.4677532552380222478.b4-ty@b4> (raw)
In-Reply-To: <20260515102500.216264-1-h.laimer@proxmox.com>
On Fri, 15 May 2026 12:24:51 +0200, Hannes Laimer wrote:
> This patch series adds BGP as a third fabric protocol alongside OpenFabric and
> OSPF. It targets eBGP unnumbered underlays where each node has a unique ASN and
> peers over physical interfaces without IP assignment on fabric links.
>
> ## Dependencies
>
> This series is based on the wireguard, evpn, and ospf-redist series ([3]-[5]).
>
> [...]
Applied, thanks!
A few changes we did on top:
* folded review fixes into the proxmox-ve-rs commit (UpdaterType type
mismatch on NodeData<BgpNode>, broken delete API from a stray
#[serde(untagged)] on BgpNodeDeletableProperties, always-Some if let around
local_as setup, drive-by reorder of the From<Section> arms, "an Bgp" / "an
BGP" doc-comment grammar)
* folded review fixes into the proxmox-perl-rs commits (missing
Protocol::Bgp arm in get_status so a healthy BGP fabric reported NotOk in the
UI; enabled bgpd in enabled_daemons since Debian's vanilla /etc/frr/daemons
has bgpd=no; revert drive-by import reorder to keep rustfmt-2024 style; drop
stale doc comment on mod bgp)
* two small follow-ups on top of proxmox-ve-rs (frr: bgp: document
merge_fabric preservation semantics; ve-config: sdn: fabric: bgp: gate
0.0.0.0 router-id at validation)
* bumped proxmox-frr to 0.5.1, proxmox-ve-config to 0.10,
libpve-rs-perl to 0.15.0 and libpve-network-perl to 1.6.0
[proxmox-ve-rs]
[1/1] sdn: fabric: add BGP protocol support
commit: f7a336978c8fb22735dd91254cd1bbd6097cf2a5
[proxmox-perl-rs]
[1/2] sdn: fabrics: add BGP config generation
commit: 01868d9f50c471831c0589ae044e04419ef7ce9d
[2/2] sdn: fabrics: add BGP status endpoints
commit: af5c8d4105ad7d349ac0153af1923400052f79d9
[pve-network]
[1/4] sdn: fabrics: register bgp as a fabric protocol type
commit: 9d8533d7fa1cfd65016b3307a5ec3a2a07dcc4fd
[2/4] sdn: forbid BGP controller and BGP fabric coexistence
commit: 188f2c5e076419acd8b9609c1f2cbc848942725b
[3/4] sdn: evpn: support eBGP VTEPs over BGP fabric underlays
commit: ee78539eb61e066655f568049655f8f05e9b9ef8
[4/4] test: evpn: add integration test for EVPN over BGP fabric
commit: 1574df2c303df0e277a9258263dc3e01cdb92b0d
[pve-manager]
[1/1] ui: sdn: add BGP fabric support
commit: 64876b483d363898451740f65bea4b131759ada0
[pve-docs]
[1/1] sdn: add bgp fabric section
commit: b657b3e6b1bca5d1c41b79ebeb65886a47defb90
prev parent reply other threads:[~2026-05-18 10:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 10:24 [PATCH docs/manager/network/proxmox{-ve-rs,-perl-rs} v6 0/9] sdn: add BGP fabric Hannes Laimer
2026-05-15 10:24 ` [PATCH proxmox-ve-rs v6 1/9] sdn: fabric: add BGP protocol support Hannes Laimer
2026-05-15 10:24 ` [PATCH proxmox-perl-rs v6 2/9] sdn: fabrics: add BGP config generation Hannes Laimer
2026-05-15 10:24 ` [PATCH proxmox-perl-rs v6 3/9] sdn: fabrics: add BGP status endpoints Hannes Laimer
2026-05-15 10:24 ` [PATCH pve-network v6 4/9] sdn: fabrics: register bgp as a fabric protocol type Hannes Laimer
2026-05-15 10:24 ` [PATCH pve-network v6 5/9] sdn: forbid BGP controller and BGP fabric coexistence Hannes Laimer
2026-05-15 10:24 ` [PATCH pve-network v6 6/9] sdn: evpn: support eBGP VTEPs over BGP fabric underlays Hannes Laimer
2026-05-15 10:24 ` [PATCH pve-network v6 7/9] test: evpn: add integration test for EVPN over BGP fabric Hannes Laimer
2026-05-15 10:24 ` [PATCH pve-manager v6 8/9] ui: sdn: add BGP fabric support Hannes Laimer
2026-05-15 10:25 ` [PATCH pve-docs v6 9/9] sdn: add bgp fabric section Hannes Laimer
2026-05-18 10:20 ` Thomas Lamprecht [this message]
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=177909919151.3110381.4677532552380222478.b4-ty@b4 \
--to=t.lamprecht@proxmox.com \
--cc=h.laimer@proxmox.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