all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Stefan Hanreich <s.hanreich@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] superseded: [PATCH manager 0/4] improvements to proxmox-network-interface-pinning
Date: Thu, 24 Jul 2025 11:35:46 +0200	[thread overview]
Message-ID: <6a67b0b0-0785-41eb-8821-027ffd672820@proxmox.com> (raw)
In-Reply-To: <20250724093224.70863-1-s.hanreich@proxmox.com>

forgot to run make tidy...

https://lore.proxmox.com/pve-devel/20250724093459.76397-1-s.hanreich@proxmox.com/T/#t

On 7/24/25 11:32, Stefan Hanreich wrote:
> Several improvements to the network interface pinning tool:
> * interfaces are now iterated according to ifindex
> * output of the mapping is now sorted and less verbose
> * users can now set a specific target name
> * if has been introduced as an additional legal prefix
> 
> Still looking into removing the PHYSICAL_NIC_RE altogether, but sending this
> patch series as-is nevertheless for review / feedback. If I manage to remove the
> PHYSICAL_NIC_RE in time, we could get rid of the constraints of prefix /
> target-name altogether...
> 
> pve-manager:
> 
> Stefan Hanreich (4):
>   network-interface-pinning: use ifindex as order for pinning
>   network-interface-pinning: improve printing mapping
>   network-interface-pinning: add target-name parameter
>   network-interface-pinning: add if prefix to list of allowed prefixes
> 
>  PVE/CLI/proxmox_network_interface_pinning.pm | 76 +++++++++++++++++---
>  1 file changed, 65 insertions(+), 11 deletions(-)
> 
> 
> Summary over all repositories:
>   1 files changed, 65 insertions(+), 11 deletions(-)
> 



_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


      parent reply	other threads:[~2025-07-24  9:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-24  9:32 [pve-devel] " Stefan Hanreich
2025-07-24  9:32 ` [pve-devel] [PATCH pve-manager 1/4] network-interface-pinning: use ifindex as order for pinning Stefan Hanreich
2025-07-24  9:32 ` [pve-devel] [PATCH pve-manager 2/4] network-interface-pinning: improve printing mapping Stefan Hanreich
2025-07-24  9:32 ` [pve-devel] [PATCH pve-manager 3/4] network-interface-pinning: add target-name parameter Stefan Hanreich
2025-07-24  9:32 ` [pve-devel] [PATCH pve-manager 4/4] network-interface-pinning: add if prefix to list of allowed prefixes Stefan Hanreich
2025-07-24  9:35 ` 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=6a67b0b0-0785-41eb-8821-027ffd672820@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal