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

[Stefan Hanreich]

On 7/15/25 15:15, Thomas Lamprecht wrote:
> 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.

But if the (alt-)name of the NIC changes in the meanwhile and the
configuration doesn't get written inbetween, how would we ever be able
to infer which NIC was initially referenced in the configuration file?
Isn't this the exact case we're trying to solve with pinning? Or am I
misunderstanding something here?