From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Dominik Csapak <d.csapak@proxmox.com>, pdm-devel@lists.proxmox.com
Subject: Re: [PATCH datacenter-manager/proxmox-geojson-data/yew-widget-toolkit/yew-widget-toolkit-assets v3 00/11] add a new map widget for custom views
Date: Fri, 22 May 2026 11:38:01 +0200 [thread overview]
Message-ID: <b1e14acb-7078-4615-8cc3-7f429987d4ae@proxmox.com> (raw)
In-Reply-To: <20260522083412.1223719-1-d.csapak@proxmox.com>
Am 22.05.26 um 10:34 schrieb Dominik Csapak:
> Locations are now taken from PVE/PBS themselves and are cached.
> I chose 24 hours as default max-age for the cache for now, but we might
> want to increase that to something even higher (maybe a month?).
> There is also currently no mechanism that updates the location in the background
> automatically, but this can be done in the next version or as a followup
> if we can agree on a sensible interval for that. (I'd suggest once a week
> or something like that?)
I mean, that data is in fast to parse "hot" configs tracked by pmxcfs, so
I'd not bother to much with an overly long caching policy, even "just" an
hour would be fine here, especially as we can also pull other data from
those configs while at it, at least for PVE (descriptions, acme domains,
...?). OTOH, this is probably something where one wants like 10s or less
if one actually is in process to set that up initially and after that,
weeks. months or just opportunistically (if that config needs to be
fetched for something else) in between would be fine.
> If there is a differing opinion or suggestion on any of that, please do tell.
Fine for the MVP for now. A force-refresh for a remote or all remotes is
basically the only thing needed that gives admin an escape hatch. As IMO,
one normally detects that it's wrong when checking that map, so one fixes
the data and rechecks the map, if it then needs 24h or 1h or 1 week doesn't
matter, as that's all to slow for that operation. With a force reload we
can make the period of the reload matter way less.
Anyway, I'll try to look at this in detail today, starting out with
proxmox-geojson-data package.
next prev parent reply other threads:[~2026-05-22 9:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-22 8:33 [PATCH datacenter-manager/proxmox-geojson-data/yew-widget-toolkit/yew-widget-toolkit-assets v3 00/11] add a new map widget for custom views Dominik Csapak
2026-05-22 8:33 ` [PATCH yew-widget-toolkit v3 1/3] js-helper: add client-to-svg-coordinate conversion helper Dominik Csapak
2026-05-22 8:33 ` [PATCH yew-widget-toolkit v3 2/3] widget: charts: add interactive Map with zoom/pan and clustering Dominik Csapak
2026-05-22 13:30 ` Shannon Sterz
2026-05-22 8:33 ` [PATCH yew-widget-toolkit v3 3/3] widget: charts: add WorldMap with GeoJSON rendering Dominik Csapak
2026-05-22 8:34 ` [PATCH yew-widget-toolkit-assets v3 1/1] charts: add necessary classes for Map Dominik Csapak
2026-05-22 8:34 ` [PATCH proxmox-geojson-data v3 1/1] initial commit Dominik Csapak
2026-05-22 13:30 ` Shannon Sterz
2026-05-22 8:34 ` [PATCH datacenter-manager v3 1/6] server: pbs client: add node_config method Dominik Csapak
2026-05-22 8:34 ` [PATCH datacenter-manager v3 2/6] lib/api: add 'location-info' api call with cached information Dominik Csapak
2026-05-22 13:30 ` Shannon Sterz
2026-05-22 8:34 ` [PATCH datacenter-manager v3 3/6] lib/api: add new 'remote-list' info to the resource status Dominik Csapak
2026-05-22 8:34 ` [PATCH datacenter-manager v3 4/6] server: serve geojson worldmap Dominik Csapak
2026-05-22 8:34 ` [PATCH datacenter-manager v3 5/6] ui: views: refactor required api call info into struct Dominik Csapak
2026-05-22 8:34 ` [PATCH datacenter-manager v3 6/6] ui: views: add map component Dominik Csapak
2026-05-22 13:30 ` Shannon Sterz
2026-05-22 9:38 ` Thomas Lamprecht [this message]
2026-05-22 13:33 ` [PATCH datacenter-manager/proxmox-geojson-data/yew-widget-toolkit/yew-widget-toolkit-assets v3 00/11] add a new map widget for custom views Shannon Sterz
2026-05-24 2:31 ` applied: " 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=b1e14acb-7078-4615-8cc3-7f429987d4ae@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=d.csapak@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.