From: Stefan Hanreich <s.hanreich@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] superseded: [RFC common/manager 0/3] arbitrary prefixes for pinning network interfaces
Date: Tue, 29 Jul 2025 19:17:48 +0200 [thread overview]
Message-ID: <139d7623-2439-43a2-9d89-c5c6d2993f41@proxmox.com> (raw)
In-Reply-To: <20250724144959.374061-1-s.hanreich@proxmox.com>
https://lore.proxmox.com/pve-devel/20250729171649.708219-1-s.hanreich@proxmox.com/T/#t
On 7/24/25 4:49 PM, Stefan Hanreich wrote:
> This patch series lifts the restriction for naming physical interfaces.
> Previously we relied on a regex (PHYSICAL_NIC_RE) for determining whether an
> interface was physical or not. This patch series changes that, by querying the
> kernel for the type of the interface and using that to determine whether an
> interface is a physical interface or not. This allows us to use arbitrary names
> for physical interfaces, which in turn allows proxmox-network-interface-pinning
> to use arbitrary prefixes / target-names when pinning network interfaces.
>
> The main change here is with pvestatd and metric collection, where we used the
> regex to determine the type of interface in PullMetric. I introduced a new key
> in the netdev hash that indicates the type of interface. Since my knowledge of
> this component is almost zero, I'm not sure if this is the proper approach.
> Maybe someone with more experience can chime in on possible issues /
> improvements.
>
> This patch series applies on top of my previous series that improves several
> aspects of the pinning tool [1].
>
> pve-manager depends on pve-common
>
> [1] https://lore.proxmox.com/pve-devel/20250724093459.76397-1-s.hanreich@proxmox.com/T/#t
>
> pve-common:
>
> Stefan Hanreich (1):
> inotify/interfaces: use ip link for detecting physical interfaces
>
> src/PVE/INotify.pm | 25 +++++++++++++------------
> 1 file changed, 13 insertions(+), 12 deletions(-)
>
>
> pve-manager:
>
> Stefan Hanreich (2):
> pvestatd: pull metric: use ip link to detect physical interfaces
> network-interface-pinning: allow arbitrary names
>
> PVE/CLI/proxmox_network_interface_pinning.pm | 7 ++++---
> PVE/PullMetric.pm | 15 ++++++++++++---
> PVE/Service/pvestatd.pm | 13 ++++++++++++-
> 3 files changed, 28 insertions(+), 7 deletions(-)
>
>
> Summary over all repositories:
> 4 files changed, 41 insertions(+), 19 deletions(-)
>
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-07-29 17:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-24 14:49 [pve-devel] " Stefan Hanreich
2025-07-24 14:49 ` [pve-devel] [PATCH pve-common 1/1] inotify/interfaces: use ip link for detecting physical interfaces Stefan Hanreich
2025-07-24 14:49 ` [pve-devel] [PATCH pve-manager 1/2] pvestatd: pull metric: use ip link to detect " Stefan Hanreich
2025-07-24 14:49 ` [pve-devel] [PATCH pve-manager 2/2] network-interface-pinning: allow arbitrary names Stefan Hanreich
2025-07-29 17:17 ` Stefan Hanreich [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=139d7623-2439-43a2-9d89-c5c6d2993f41@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