public inbox for pbs-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Stefan Hanreich <s.hanreich@proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>,
	Proxmox Backup Server development discussion
	<pbs-devel@lists.proxmox.com>
Subject: Re: [pbs-devel] [PATCH proxmox-network-interface-pinning 1/1] initial commit
Date: Wed, 30 Jul 2025 15:14:45 +0200	[thread overview]
Message-ID: <2367bf22-edcf-4798-8acd-8cd8dd91e4c6@proxmox.com> (raw)
In-Reply-To: <a8ada30c-c123-44e4-b001-cb775728eb5f@proxmox.com>

On 7/30/25 3:07 PM, Thomas Lamprecht wrote:
> Am 29.07.25 um 18:57 schrieb Stefan Hanreich:
>> +    // This is run on a PVE host, so we use the PVE-specific pinning tool instead with the
>> +    // parameters supplied.
>> +    if std::fs::exists("/usr/bin/proxmox-network-interface-pinning")? {
> 
> Hmm, why does this here live in libexec if it's intended to be the main one?
> 
> Should we rather move the one from pve-manager into libexec with a product
> specific name like "pve-network-interface-pinning" and keep this here in
> bin with the generic name? As otherwise one needs to use the full libexec
> path when using this on PBS/PMG/PDM? Or what's the idea here?

Yes, that sounds better, so the pve-manager one into

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

and this one into

  /usr/bin/proxmox-network-interface-pinning

Or even sbin?

I assume, we would then install the standalone package by default in PVE?

> btw. no need to commit Cargo.lock here, at least not for initial commit
> to the list.

duly noted


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


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

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-29 16:56 [pbs-devel] [PATCH proxmox{-ve-rs, , -backup, -firewall, -network-interface-pinning} 0/8] proxmox-network-interface-pinning Stefan Hanreich
2025-07-29 16:56 ` [pbs-devel] [PATCH proxmox-ve-rs 1/1] host: network: move to proxmox-network-api Stefan Hanreich
2025-07-29 16:56 ` [pbs-devel] [PATCH proxmox 1/3] pbs-api-types: use proxmox-network-api types Stefan Hanreich
2025-07-29 16:56 ` [pbs-devel] [PATCH proxmox 2/3] proxmox-network-api: use ip link for querying interface information Stefan Hanreich
2025-07-29 16:56 ` [pbs-devel] [PATCH proxmox 3/3] network-api: add rename_interfaces method Stefan Hanreich
2025-07-29 16:56 ` [pbs-devel] [PATCH proxmox-backup 1/2] config: network: move to proxmox-network-api Stefan Hanreich
2025-07-29 16:56 ` [pbs-devel] [PATCH proxmox-backup 2/2] metric_collection: use ip link for determining the type of interfaces Stefan Hanreich
2025-07-29 16:56 ` [pbs-devel] [PATCH proxmox-firewall 1/1] firewall: config: use proxmox-network-api Stefan Hanreich
2025-07-29 16:56 ` [pbs-devel] [PATCH proxmox-network-interface-pinning 1/1] initial commit Stefan Hanreich
2025-07-30 13:07   ` Thomas Lamprecht
2025-07-30 13:14     ` Stefan Hanreich [this message]
2025-07-30 13:24       ` Thomas Lamprecht
2025-07-30 13:30         ` Fabian Grünbichler
2025-07-30 13:35           ` Stefan Hanreich
2025-07-30 13:42             ` Thomas Lamprecht
2025-07-30 14:37 ` [pbs-devel] superseded: [PATCH proxmox{-ve-rs, , -backup, -firewall, -network-interface-pinning} 0/8] proxmox-network-interface-pinning Stefan Hanreich

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=2367bf22-edcf-4798-8acd-8cd8dd91e4c6@proxmox.com \
    --to=s.hanreich@proxmox.com \
    --cc=pbs-devel@lists.proxmox.com \
    --cc=t.lamprecht@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