From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 90D9C1FF142 for ; Fri, 22 May 2026 11:38:06 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id CACE052FF; Fri, 22 May 2026 11:38:04 +0200 (CEST) Message-ID: Date: Fri, 22 May 2026 11:38:01 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Beta 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 To: Dominik Csapak , pdm-devel@lists.proxmox.com References: <20260522083412.1223719-1-d.csapak@proxmox.com> Content-Language: en-US From: Thomas Lamprecht In-Reply-To: <20260522083412.1223719-1-d.csapak@proxmox.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1779442663450 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.005 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: TAC3OEXU7RSJ2OPVDQTKPBQW7RRRDDB5 X-Message-ID-Hash: TAC3OEXU7RSJ2OPVDQTKPBQW7RRRDDB5 X-MailFrom: t.lamprecht@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox Datacenter Manager development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: 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.