From: "Lukas Wagner" <l.wagner@proxmox.com>
To: "Lukas Sichert" <l.sichert@proxmox.com>,
"Lukas Wagner" <l.wagner@proxmox.com>,
<pdm-devel@lists.proxmox.com>
Subject: Re: [PATCH datacenter-manager v2 0/2] improvements for ParallelFetcher
Date: Tue, 03 Mar 2026 08:38:09 +0100 [thread overview]
Message-ID: <DGSZ4XI4IHF8.2XQZ808B9WOHO@proxmox.com> (raw)
In-Reply-To: <ab6ff0b0-3e1f-4091-b78e-2b4e1b84675b@proxmox.com>
Hi Lukas,
thanks for testing/reviewing these changes. I'll post a v3 with some
additional (minor) improvements and will include your R-b/T-b tags
there.
On Tue Feb 24, 2026 at 2:42 PM CET, Lukas Sichert wrote:
> 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.
Very nice catch! I'll consider this for a future followup - although I'm
not yet sure where the best place for adding a timeout mechanism would
be, either right inside the parallel fetcher code, the individual
handler fn's in the call sites, or directly in the PVE API bindings.
>
> Reviewed-by: Lukas Sichert <l.sichert@proxmox.com>
> Tested-by: Lukas Sichert <l.sichert@proxmox.com>
>
prev parent reply other threads:[~2026-03-03 7:37 UTC|newest]
Thread overview: 5+ 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 ` [PATCH datacenter-manager v2 0/2] improvements for ParallelFetcher Lukas Sichert
2026-03-03 7:38 ` Lukas Wagner [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=DGSZ4XI4IHF8.2XQZ808B9WOHO@proxmox.com \
--to=l.wagner@proxmox.com \
--cc=l.sichert@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 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.