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 36E6E1FF136 for ; Mon, 18 May 2026 23:56:03 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id A8DBF1B7B8; Mon, 18 May 2026 23:56:01 +0200 (CEST) From: Thomas Lamprecht To: pdm-devel@lists.proxmox.com, Lukas Wagner Subject: applied: [PATCH datacenter-manager v3 0/4] add generic, per-remote (and global) cache for remote API responses Date: Mon, 18 May 2026 23:53:10 +0200 Message-ID: <177914118716.151791.7544822894393702702.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260515144927.427114-1-l.wagner@proxmox.com> References: <20260515144927.427114-1-l.wagner@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1779141344577 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.004 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: EU77DVUXX7THBNSXRQFQWUIR6KOF3VB2 X-Message-ID-Hash: EU77DVUXX7THBNSXRQFQWUIR6KOF3VB2 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: On Fri, 15 May 2026 16:49:23 +0200, Lukas Wagner wrote: > The main intention is to avoid a sprawl of different caching approaches by > establishing a simple, easy to use cache implementation that can be used to > persistently cache API responses from remotes (and derived aggregations). > > The `namespaced_cache` module is pretty generic and can be moved to proxmox.git > (maybe in proxmox-shared-cache) once it has sufficiently stabilized. > > [...] Applied, thanks! Nice work, and once the dust settles on this we probably can move the core over to its own crate in the proxmox workspace, but totally fine to keep it here for now. Btw. I squashed in small doc typo and some small style nits squashed in, and two tiny slightly opinionated code-reuse clean-ups as follow-up, I did not think requesting a v4 was worth it for them. [1/4] add persistent, generic, namespaced key-value cache implementation commit: cef510ddbf2856414157e2ddb258d54b66c80bb0 [2/4] add api_cache as a specialized wrapper around the namespaced cache commit: ea30a924f1b9dfc0c3259eb7468dd907c6c8fe09 [3/4] api: resources: subscriptions: switch over to api_cache commit: 2b1735d601f4ecebe68bcc1d15653b3e2d65598e [4/4] remote-updates: switch over to new api_cache commit: 0ae2279c621298dc08118dae70b06e290c7b4bac