From: Lukas Sichert <l.sichert@proxmox.com>
To: Lukas Wagner <l.wagner@proxmox.com>, pdm-devel@lists.proxmox.com
Subject: Re: [PATCH datacenter-manager v2 0/2] improvements for ParallelFetcher
Date: Tue, 24 Feb 2026 14:42:14 +0100 [thread overview]
Message-ID: <ab6ff0b0-3e1f-4091-b78e-2b4e1b84675b@proxmox.com> (raw)
In-Reply-To: <20260206094304.117465-1-l.wagner@proxmox.com>
The changes were reviewed and tested in a cluster consisting of two
PVE nodes and one PBS. The following features were considered for testing:
Update handling:
The update summary could be retrieved without issues.
Tasks:
The task log was displayed correctly.
Only for the cluster:
SDN:
A Simple Zone and an EVPN Zone were created.
Both zones and the EVPN Controller were displayed correctly.
Firewall:
Node firewall rules and datacenter firewall configuration were shown
correctly.
The tests were also repeated with one of the nodes offline, and
everything still worked as expected.
While reviewing the code, I noticed that the async fetchers currently
have no explicit timeouts. If one of the fetch operations blocks
indefinitely, it could stall the overall execution. Adding this in a
future commit would improve robustness.
Reviewed-by: Lukas Sichert <l.sichert@proxmox.com>
Tested-by: Lukas Sichert <l.sichert@proxmox.com>
On 2/6/26 10:41, Lukas Wagner wrote:
> A couple of improvents for the parallel_fetcher module:
> - inherit log context so that logging in worker tasks works
> - response type improvements, better ergonomics for callers
> - documentation
>
> Changes since v2:
> - Change type names from *Outcome to *Response
>
>
> proxmox-datacenter-manager:
>
> Lukas Wagner (2):
> parallel fetcher: improve result type ergonomics
> parallel fetcher: add module documentation
>
> server/src/api/pve/firewall.rs | 53 +--
> server/src/api/sdn/controllers.rs | 38 +-
> server/src/api/sdn/vnets.rs | 35 +-
> server/src/api/sdn/zones.rs | 35 +-
> .../tasks/remote_tasks.rs | 33 +-
> server/src/parallel_fetcher.rs | 333 +++++++++++++-----
> server/src/remote_updates.rs | 36 +-
> 7 files changed, 340 insertions(+), 223 deletions(-)
>
>
> Summary over all repositories:
> 7 files changed, 340 insertions(+), 223 deletions(-)
>
prev parent reply other threads:[~2026-02-24 13:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-06 9:43 Lukas Wagner
2026-02-06 9:43 ` [PATCH datacenter-manager v2 1/2] parallel fetcher: improve result type ergonomics Lukas Wagner
2026-02-06 9:43 ` [PATCH datacenter-manager v2 2/2] parallel fetcher: add module documentation Lukas Wagner
2026-02-24 13:42 ` Lukas Sichert [this message]
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=ab6ff0b0-3e1f-4091-b78e-2b4e1b84675b@proxmox.com \
--to=l.sichert@proxmox.com \
--cc=l.wagner@proxmox.com \
--cc=pdm-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