public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Christoph Heiss <c.heiss@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH docs 3/7] pve-network-interface-pinning: init man(1) page
Date: Tue, 23 Jun 2026 11:43:20 +0200	[thread overview]
Message-ID: <20260623094419.330174-4-c.heiss@proxmox.com> (raw)
In-Reply-To: <20260623094419.330174-1-c.heiss@proxmox.com>

Signed-off-by: Christoph Heiss <c.heiss@proxmox.com>
---
FWIW; this already includes the help text for the new `rename`
subcommand introduced in patch #6.

 ...-network-interface-pinning.1-synopsis.adoc | 50 ++++++++++++++++
 pve-admin-guide.adoc                          |  8 +++
 pve-network-interface-pinning.adoc            | 60 +++++++++++++++++++
 3 files changed, 118 insertions(+)
 create mode 100644 generated/pve-network-interface-pinning.1-synopsis.adoc
 create mode 100644 pve-network-interface-pinning.adoc

diff --git a/generated/pve-network-interface-pinning.1-synopsis.adoc b/generated/pve-network-interface-pinning.1-synopsis.adoc
new file mode 100644
index 0000000..f8eb18d
--- /dev/null
+++ b/generated/pve-network-interface-pinning.1-synopsis.adoc
@@ -0,0 +1,50 @@
+[[cli_pve-network-interface-pinning]]
+*pve-network-interface-pinning* `<COMMAND> [ARGS] [OPTIONS]`
+
+[[cli_pve-network-interface-pinning_generate]]
+*pve-network-interface-pinning generate* `[OPTIONS]`
+
+Generate systemd.link files to pin the names of one or more network
+interfaces and update all network-related configuration files.
+
+`--interface` `<string>` ('default =' `<all>`)::
+
+Only pin a specific interface.
+
+`--prefix` `^[a-zA-Z][a-zA-Z0-9-_]{0,7}$` ('default =' `nic`)::
+
+Use a specific prefix for automatically choosing the pinned name.
+
+`--target-name` `<string>` ::
+
+Pin the interface to a specific name.
++
+NOTE: Requires option(s): `interface`
+
+[[cli_pve-network-interface-pinning_help]]
+*pve-network-interface-pinning help* `[OPTIONS]`
+
+Get help about specified command.
+
+`--extra-args` `<array>` ::
+
+Shows help for a specific command
+
+`--verbose` `<boolean>` ::
+
+Verbose output format.
+
+[[cli_pve-network-interface-pinning_rename]]
+*pve-network-interface-pinning rename* `<interface> <target-name>`
+
+Rename an existing pin for a network interface to a specific name.
+
+`<interface>`: `<string>` ::
+
+The interface to rename.
+
+`<target-name>`: `<string>` ::
+
+The new pinned interface name.
+
+
diff --git a/pve-admin-guide.adoc b/pve-admin-guide.adoc
index fd37b1e..c086377 100644
--- a/pve-admin-guide.adoc
+++ b/pve-admin-guide.adoc
@@ -226,6 +226,14 @@ include::generated/ha-manager.1-synopsis.adoc[]
 
 :leveloffset: 0
 
+*pve-network-interface-pinning* - {pve} Network Interface Pinning Tool
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+:leveloffset: 1
+include::generated/pve-network-interface-pinning.1-synopsis.adoc[]
+
+:leveloffset: 0
+
 
 [appendix]
 Service Daemons
diff --git a/pve-network-interface-pinning.adoc b/pve-network-interface-pinning.adoc
new file mode 100644
index 0000000..79d6aeb
--- /dev/null
+++ b/pve-network-interface-pinning.adoc
@@ -0,0 +1,60 @@
+ifdef::manvolnum[]
+pve-network-interface-pinning(1)
+================================
+:pve-toplevel:
+
+NAME
+----
+
+pve-network-interface-pinning - Proxmox VE Network Interface Pinning Tool
+
+SYNOPSIS
+--------
+
+include::generated/pve-network-interface-pinning.1-synopsis.adoc[]
+
+DESCRIPTION
+-----------
+endif::manvolnum[]
+
+ifndef::manvolnum[]
+Overriding Network Device Names
+===============================
+endif::manvolnum[]
+
+Command line tool to generate and rename pinned network interface names.
+
+ifdef::manvolnum[]
+
+In order to apply the changes made by `pve-network-interface-pinning`, the node
+needs to be rebooted.
+
+EXAMPLES
+--------
+
+To generate .link for all present physical interfaces:
+
+----
+pve-network-interface-pinning generate
+----
+
+As above, but with a custom prefix instead of `nic`:
+
+----
+pve-network-interface-pinning generate --prefix myprefix
+----
+
+Or just pin a specific network interface to a chosen name:
+
+----
+pve-network-interface-pinning generate --interface enp1s0 --target-name mynic
+----
+
+To rename an already pinned interface, e.g. `nic0` to `fiber10g0`:
+
+----
+pve-network-interface-pinning rename nic0 fiber10g0
+----
+
+include::pve-copyright.adoc[]
+endif::manvolnum[]
-- 
2.54.0





  parent reply	other threads:[~2026-06-23  9:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-23  9:43 [PATCH docs/manager 0/7] interface-pinning: add rename subcommand and man(1) page Christoph Heiss
2026-06-23  9:43 ` [PATCH docs 1/7] network: fix typo occurences -> occurrences Christoph Heiss
2026-06-23  9:43 ` [PATCH docs 2/7] pve-doc-generator: handle CLI tools/services with dashes in their name Christoph Heiss
2026-06-23  9:43 ` Christoph Heiss [this message]
2026-06-23  9:43 ` [PATCH docs 4/7] network: pinning: mention how to rename an interface Christoph Heiss
2026-06-23  9:43 ` [PATCH manager 5/7] network-interface-pinning: avoid warning if `bond-primary` is unset Christoph Heiss
2026-06-23  9:43 ` [PATCH manager 6/7] network-interface-pinning: add method for renaming existing pins Christoph Heiss
2026-06-23  9:43 ` [PATCH manager 7/7] network-interface-pinning: generate proper manpage from docs Christoph Heiss

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=20260623094419.330174-4-c.heiss@proxmox.com \
    --to=c.heiss@proxmox.com \
    --cc=pve-devel@lists.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