public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Stefan Hanreich <s.hanreich@proxmox.com>,
	Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Dominik Csapak <d.csapak@proxmox.com>
Subject: Re: [pve-devel] [PATCH pve-manager v2 1/1] api/ui: show/return alternative interface names
Date: Tue, 15 Jul 2025 15:15:57 +0200	[thread overview]
Message-ID: <e8d11256-6be2-4a11-a770-56087d34154a@proxmox.com> (raw)
In-Reply-To: <64d42fb0-77de-4803-96b6-da72574daab9@proxmox.com>

Am 15.07.25 um 15:08 schrieb Stefan Hanreich:
> On 7/15/25 14:36, Thomas Lamprecht wrote:
>> but what changes are there required if it's _transparent_ altname support?
> 
> We would refer to the newly generated, pinned, names then in the
> configuration files.

That can be done when serializing those out the next time they get
written though? IMO there's not much benefit for adding such a big
churn, that's only asking for trouble with no advantage for all users
that do not manually edit the firewall rule (or SDN) configs, and
that would still work, it just might be slightly confusing at first;
but the latter can be defused by mentioning this explicitly, e.g. in
documentation about pinning and maybe a CLI stdout message in the tool.


>> And then probably have two commands for preparing the pinning for one or
>> more interface and for applying the prepared changes.
>> As I'd find it very odd if I–as user–could create the preparation for
>> pinning here, but then would need to login on the web ui to apply
>> that on the various panels (in what order?!).
>> And ideally firewall and SDN handles this transparently, so it doesn't
>> matter if that configs get changed for the common case.
> 
> See my post on the other thread for the pinning tool itself where I
> basically propose something like that.

Thanks for the pointer.


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

  reply	other threads:[~2025-07-15 13:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-15  9:07 [pve-devel] [PATCH manager/widget-toolkit v2 0/2] show altenative interface names in the web ui Dominik Csapak
2025-07-15  9:07 ` [pve-devel] [PATCH widget-toolkit v2 1/1] network: optionally show alternative interface names Dominik Csapak
2025-07-15 19:56   ` Thomas Lamprecht
2025-07-16 22:47   ` Thomas Lamprecht
2025-07-15  9:07 ` [pve-devel] [PATCH pve-manager v2 1/1] api/ui: show/return " Dominik Csapak
2025-07-15  9:21   ` Stefan Hanreich
2025-07-15  9:30     ` Dominik Csapak
2025-07-15  9:41       ` Stefan Hanreich
2025-07-15 10:33         ` Dominik Csapak
2025-07-15 11:06           ` Stefan Hanreich
2025-07-15 12:36             ` Thomas Lamprecht
2025-07-15 13:08               ` Stefan Hanreich
2025-07-15 13:15                 ` Thomas Lamprecht [this message]
2025-07-15 13:47                   ` Stefan Hanreich
2025-07-17 16:00   ` [pve-devel] applied: " 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=e8d11256-6be2-4a11-a770-56087d34154a@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=d.csapak@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    --cc=s.hanreich@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