[pbs-devel] [PATCH proxmox-network-interface-pinning 1/1] initial commit

[Stefan Hanreich]

On 7/30/25 3:30 PM, Fabian Grünbichler wrote:

[snip]

>>> I assume, we would then install the standalone package by default in PVE?
>>
>> That's the only small "ugliness" there is with this approach, as it would
>> not be required per se.
>>
>> The alternative I see is that both life in /usr/bin, either with
>> "pve" and "proxmox" prefix in the name, respectively, or under the same
>> name but with conflicts on packaging level and this package here being
>> added only as Recommended for PBS/PDM/PMG to allow co-installation.
>>
>> tbh. I'm not opposed of either variant, CC'in Fabian, maybe he can act
>> as tie breaker here.
> 
> I think installing the rust one always is the simplest solution, even if
> it is basically a wrapper doing nothing except forwarding the invocation
> on systems with PVE installed.
> 
> we could also solve this cleanly on the packaging level, but all the
> variants I can come up with[0] are more involved - and at some point we
> will probably want to drop the PVE specific one anyway, i.e., when we
> switch the network config parsing there over to the Rust-based one one
> it reaches feature parity ;)
> 
> 0: alternatives preferring the PVE one, diverting by the PVE package, ..

Yeh, I'm also gravitating towards that solution, imo the easiest path
after all.

So:

pve-network-interface-pinning in /usr/libexec/proxmox
proxmox-network-interface-pinning in /usr/bin

I'll send a v2 for this series, as well as a new patch for pve-manager -
unless there are any objections? @Thomas