From: Christian Ebner <c.ebner@proxmox.com>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>,
Stefan Hanreich <s.hanreich@proxmox.com>
Subject: Re: [pbs-devel] [PATCH proxmox{-ve-rs, , -backup, -firewall, -network-interface-pinning} v4 00/10] proxmox-network-interface-pinning
Date: Fri, 1 Aug 2025 11:51:12 +0200 [thread overview]
Message-ID: <7646ff4e-3db5-4768-8ae3-e79c212bae4d@proxmox.com> (raw)
In-Reply-To: <20250731140855.573717-1-s.hanreich@proxmox.com>
Tested:
- Installed packages build with patches applied on top of PBS4 testing
repo patchset (including latest proxmox-widget-toolkit)
- Created multiple NICs, created bridge and attached 2 NICs as ports
- Checked the network config is applied on reboot
- Generated pinned nic names, verified network config after reboot
- Generated VLAN, basic connnectivity testing via ping and monitoring
via tcpdump
- Added influxdb (udp) as metric server
Apart from the nic altnames which would be nice to also have in PBS
(analogous to PVE), didn't notice anything wrong/broken. Is there
anything blocking us from doing so, now that the altnames are also part
of the api response?
Independent from that, with an up to date proxmox-widget-toolkit
consider this:
Tested-by: Christian Ebner <c.ebner@proxmox.com>
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
next prev parent reply other threads:[~2025-08-01 9:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-31 14:08 Stefan Hanreich
2025-07-31 14:08 ` [pbs-devel] [PATCH proxmox-ve-rs v4 1/1] host: network: move to proxmox-network-api Stefan Hanreich
2025-07-31 14:08 ` [pbs-devel] [PATCH proxmox v4 1/3] pbs-api-types: use proxmox-network-api types Stefan Hanreich
2025-07-31 14:08 ` [pbs-devel] [PATCH proxmox v4 2/3] proxmox-network-api: use ip link for querying interface information Stefan Hanreich
2025-07-31 14:08 ` [pbs-devel] [PATCH proxmox v4 3/3] network-api: add rename_interfaces method Stefan Hanreich
2025-08-04 12:55 ` Wolfgang Bumiller
2025-08-04 14:24 ` Stefan Hanreich
2025-07-31 14:08 ` [pbs-devel] [PATCH proxmox-backup v4 1/4] config: network: move to proxmox-network-api Stefan Hanreich
2025-07-31 14:08 ` [pbs-devel] [PATCH proxmox-backup v4 2/4] metric_collection: use ip link for determining the type of interfaces Stefan Hanreich
2025-07-31 14:08 ` [pbs-devel] [PATCH proxmox-backup v4 3/4] docs: add documentation for proxmox-network-interface-pinning Stefan Hanreich
2025-07-31 14:08 ` [pbs-devel] [PATCH proxmox-backup v4 4/4] ui: show altnames Stefan Hanreich
2025-07-31 14:08 ` [pbs-devel] [PATCH proxmox-firewall v4 1/1] firewall: config: use proxmox-network-api Stefan Hanreich
2025-07-31 14:08 ` [pbs-devel] [PATCH proxmox-network-interface-pinning v4 1/1] initial commit Stefan Hanreich
2025-08-04 13:48 ` Wolfgang Bumiller
2025-08-04 14:46 ` Stefan Hanreich
2025-08-01 9:51 ` Christian Ebner [this message]
2025-08-01 10:26 ` [pbs-devel] [PATCH proxmox{-ve-rs, , -backup, -firewall, -network-interface-pinning} v4 00/10] proxmox-network-interface-pinning Christian Ebner
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=7646ff4e-3db5-4768-8ae3-e79c212bae4d@proxmox.com \
--to=c.ebner@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
--cc=s.hanreich@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.