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 CE0C31FF15C for ; Fri, 17 Oct 2025 14:03:03 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 82DAFDC5; Fri, 17 Oct 2025 14:03:24 +0200 (CEST) From: Dominik Csapak To: pdm-devel@lists.proxmox.com Date: Fri, 17 Oct 2025 14:00:48 +0200 Message-ID: <20251017120315.2723235-1-d.csapak@proxmox.com> X-Mailer: git-send-email 2.47.3 MIME-Version: 1.0 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.028 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 RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [pdm-devel] [PATCH datacenter-manager v2 0/3] refactor api caching & try to reuse the cache X-BeenThere: pdm-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox Datacenter Manager development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox Datacenter Manager development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pdm-devel-bounces@lists.proxmox.com Sender: "pdm-devel" This series introduces a small refactored struct to access the api cache (like we used for resources + subscription) so that we don't have to repeat the same way for every bit of data we want to cache. It also shows how we can add a mechanism to live update this cache for e.g. pve resources api call and utilize it when the remote is not reachable changes from v2: * use proper api type to convey that the result was cached * abstract the 'update, fall back to cache' helper into the ApiCache struct (it'll probably be useful for more api calls) * update the cli client for this too * some smaller things @Lukas mentioned (thanks!) Dominik Csapak (3): server: api: resources: change use of remote to reference server: introduce ApiCache abstraction api/ui: pve: get cluster resources from cache if remote is unreachable cli/client/src/pve.rs | 4 +- lib/pdm-api-types/src/resource.rs | 24 +++ lib/pdm-client/src/lib.rs | 4 +- server/src/api/pve/mod.rs | 63 ++++--- server/src/api/resources.rs | 163 +++++-------------- server/src/api_cache.rs | 128 +++++++++++++++ server/src/lib.rs | 1 + server/src/metric_collection/top_entities.rs | 2 +- ui/src/pve/mod.rs | 27 ++- 9 files changed, 259 insertions(+), 157 deletions(-) create mode 100644 server/src/api_cache.rs -- 2.47.3 _______________________________________________ pdm-devel mailing list pdm-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pdm-devel