From: "Lukas Wagner" <l.wagner@proxmox.com>
To: "Proxmox Datacenter Manager development discussion"
<pdm-devel@lists.proxmox.com>,
"Hannes Laimer" <h.laimer@proxmox.com>
Subject: Re: [pdm-devel] [PATCH proxmox{, -datacenter-manager, -yew-comp} v5 00/12] add basic integration of PVE firewall
Date: Thu, 27 Nov 2025 14:38:06 +0100 [thread overview]
Message-ID: <DEJIO8GZO8XD.C8XRZ2X0QXJR@proxmox.com> (raw)
In-Reply-To: <20251127092209.213535-1-h.laimer@proxmox.com>
On Thu Nov 27, 2025 at 10:21 AM CET, Hannes Laimer wrote:
> Generally loading the status involves 2 requests per entity, so the PDM
> server has to do quite a bit of work collecting all the relevant data.
> That is the reason we have multiple status endpoints
> - for all pve remotes
> - for a specific remote
> - for a specific node
> a bit more context on the commit adding these endpoints. With these we
> can limit the number of requests the PDM potentially has to do. In this
> context a cache could also make sense, should be somewhat straight
> forward integrating something like Dominik proposed in [1]. But since
> these are configs, caches would have to be really short lived, but still,
> they could help with different useres requesting the same data at close
> to the same time.
>
> Firewall options edit form and the firewall rules tables were added to
> yew-comp as they are not necesarrily PDM specific. I tried having them
> in a way so it would not be too complicated reusing them in other places
> at some point.
>
> This also includes an updated pve-api.json, some api endpoint specs did
> require minor adjustments so they'd work with the type generator.
> Generally this is build with the latest master of proxmox-yew-comp and
> proxmox-yew-widget-toolkit.
>
> Notes: node or guest firewalls could be enabled, but end up being masked
> by the cluster setting. I tried visualizing that by having the checkmark
> normal if masked and green if not.
Looking really good. Gave this another spin on the latest master.
Noticed that there are some error messages in the browser console, see
my other reply - but this can also be fixed in a trivial followup-patch
(or also when applying).
Tested-by: Lukas Wagner <l.wagner@proxmox.com>
_______________________________________________
pdm-devel mailing list
pdm-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pdm-devel
next prev parent reply other threads:[~2025-11-27 13:38 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-27 9:21 Hannes Laimer
2025-11-27 9:21 ` [pdm-devel] [PATCH proxmox v5 1/4] pve-api-types: update pve-api.json Hannes Laimer
2025-11-27 9:21 ` [pdm-devel] [PATCH proxmox v5 2/4] pve-api-types: add get/update firewall options endpoints Hannes Laimer
2025-11-27 20:46 ` [pdm-devel] applied: " Thomas Lamprecht
2025-11-27 9:22 ` [pdm-devel] [PATCH proxmox v5 3/4] pve-api-types: add list firewall rules endpoints Hannes Laimer
2025-11-27 20:46 ` [pdm-devel] applied: " Thomas Lamprecht
2025-11-27 9:22 ` [pdm-devel] [PATCH proxmox v5 4/4] pve-api-types: regenerate Hannes Laimer
2025-11-27 9:22 ` [pdm-devel] [PATCH proxmox-datacenter-manager v5 1/4] pdm-api-types: add firewall status types Hannes Laimer
2025-11-27 21:36 ` [pdm-devel] applied: " Thomas Lamprecht
2025-11-27 9:22 ` [pdm-devel] [PATCH proxmox-datacenter-manager v5 2/4] api: firewall: add option, rules and status endpoints Hannes Laimer
2025-11-27 21:36 ` [pdm-devel] applied: " Thomas Lamprecht
2025-11-27 9:22 ` [pdm-devel] [PATCH proxmox-datacenter-manager v5 3/4] pdm-client: add api methods for firewall options, " Hannes Laimer
2025-11-27 21:36 ` [pdm-devel] applied: " Thomas Lamprecht
2025-11-27 9:22 ` [pdm-devel] [PATCH proxmox-datacenter-manager v5 4/4] ui: add firewall status tree Hannes Laimer
2025-11-27 13:35 ` Lukas Wagner
2025-11-27 21:37 ` [pdm-devel] applied: " Thomas Lamprecht
2025-11-27 9:22 ` [pdm-devel] [PATCH proxmox-yew-comp v5 1/4] form: add helpers for extractig data out of schemas Hannes Laimer
2025-11-27 21:26 ` [pdm-devel] applied: " Thomas Lamprecht
2025-11-27 9:22 ` [pdm-devel] [PATCH proxmox-yew-comp v5 2/4] firewall: add FirewallContext Hannes Laimer
2025-11-27 21:26 ` [pdm-devel] applied: " Thomas Lamprecht
2025-11-27 9:22 ` [pdm-devel] [PATCH proxmox-yew-comp v5 3/4] firewall: add options edit form Hannes Laimer
2025-11-27 21:26 ` [pdm-devel] applied: " Thomas Lamprecht
2025-11-27 9:22 ` [pdm-devel] [PATCH proxmox-yew-comp v5 4/4] firewall: add rules table Hannes Laimer
2025-11-27 21:26 ` [pdm-devel] applied: " Thomas Lamprecht
2025-11-27 13:38 ` Lukas Wagner [this message]
2025-11-27 14:14 ` [pdm-devel] [PATCH proxmox{, -datacenter-manager, -yew-comp} v5 00/12] add basic integration of PVE firewall Michael Köppl
2025-11-27 22:01 ` Thomas Lamprecht
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=DEJIO8GZO8XD.C8XRZ2X0QXJR@proxmox.com \
--to=l.wagner@proxmox.com \
--cc=h.laimer@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.