[pve-devel] [PATCH pve-manager v2 1/1] api/ui: show/return alternative interface names

[Thomas Lamprecht]

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.