From: Stefan Hanreich <s.hanreich@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH manager/proxmox{-ve-rs, -perl-rs} 0/6] proxmox-network-interface-pinning fixes
Date: Thu, 17 Jul 2025 17:28:35 +0200 [thread overview]
Message-ID: <20250717152841.397830-1-s.hanreich@proxmox.com> (raw)
!!! This series is intended for the trixie branch. I will send a separate series
for bookworm.
This patch series addresses several issues with the new
proxmox-network-interface-pinning tool which have been introduced with the merge
of the fabrics patch series:
* pve-sdn-commit failed on reboot, since the fabrics series reworked how the FRR
config generation worked. Use the new API for generating the SDN config.
* proxmox-network-interface-pinning did not update the fabric configuration when
pinning network interfaces
* failing to generate the interfaces file would not throw an error
* pinning, rebooting, then pinning additional interfaces would cause errors on
generating the interfaces file
proxmox-perl-rs depends on proxmox-ve-rs
pve-manager depends on proxmox-perl-rs
proxmox-ve-rs:
Stefan Hanreich (1):
ve-config: fabrics: add helpers for proxmox-network-interface-pinning
proxmox-ve-config/src/sdn/fabric/mod.rs | 5 +++++
.../fabric/section_config/protocol/openfabric.rs | 16 ++++++++++++++--
.../sdn/fabric/section_config/protocol/ospf.rs | 15 ++++++++++++++-
3 files changed, 33 insertions(+), 3 deletions(-)
proxmox-perl-rs:
Stefan Hanreich (1):
pve-rs: fabrics: helper for mapping interface names
pve-rs/src/bindings/sdn/fabrics.rs | 64 +++++++++++++++++++++++++++++-
1 file changed, 63 insertions(+), 1 deletion(-)
pve-manager:
Stefan Hanreich (4):
pve-sdn-commit: fix reloading logic
proxmox-network-interface-pinning: add fabrics support
proxmox-network-interface-pinning: die on failing to write interfaces
proxmox-network-interface-pinning: fix pinning after reboot
PVE/CLI/proxmox_network_interface_pinning.pm | 22 +++++++++++++++++++-
bin/pve-sdn-commit | 19 +++++++++++++++--
2 files changed, 38 insertions(+), 3 deletions(-)
Summary over all repositories:
6 files changed, 134 insertions(+), 7 deletions(-)
--
Generated by git-murpp 0.8.0
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2025-07-17 15:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-17 15:28 Stefan Hanreich [this message]
2025-07-17 15:28 ` [pve-devel] [PATCH proxmox-ve-rs 1/1] ve-config: fabrics: add helpers for proxmox-network-interface-pinning Stefan Hanreich
2025-07-17 19:27 ` [pve-devel] applied: " Thomas Lamprecht
2025-07-17 15:28 ` [pve-devel] [PATCH proxmox-perl-rs 1/1] pve-rs: fabrics: helper for mapping interface names Stefan Hanreich
2025-07-17 19:00 ` [pve-devel] applied: " Thomas Lamprecht
2025-07-17 15:28 ` [pve-devel] [PATCH pve-manager 1/4] pve-sdn-commit: fix reloading logic Stefan Hanreich
2025-07-17 19:27 ` [pve-devel] applied-series: " Thomas Lamprecht
2025-07-17 15:28 ` [pve-devel] [PATCH pve-manager 2/4] proxmox-network-interface-pinning: add fabrics support Stefan Hanreich
2025-07-17 15:28 ` [pve-devel] [PATCH pve-manager 3/4] proxmox-network-interface-pinning: die on failing to write interfaces Stefan Hanreich
2025-07-17 15:28 ` [pve-devel] [PATCH pve-manager 4/4] proxmox-network-interface-pinning: fix pinning after reboot Stefan Hanreich
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=20250717152841.397830-1-s.hanreich@proxmox.com \
--to=s.hanreich@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