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 599441FF17A for ; Tue, 11 Nov 2025 12:14:02 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id BF77D7387; Tue, 11 Nov 2025 12:14:46 +0100 (CET) Message-ID: <68a53042-4b5c-4540-82c9-56f11bd92e30@proxmox.com> Date: Tue, 11 Nov 2025 12:14:13 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Content-Language: en-US To: Thomas Lamprecht , pve-devel@lists.proxmox.com References: <20251103220024.2488005-1-a.lauterer@proxmox.com> <20251103220024.2488005-3-a.lauterer@proxmox.com> <176280281155.3000805.13988201036395926641.b4-ty@proxmox.com> From: Aaron Lauterer In-Reply-To: <176280281155.3000805.13988201036395926641.b4-ty@proxmox.com> X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1762859630609 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.011 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: Re: [pve-devel] applied: [PATCH cluster v2 2/3] RRD: fetch data from old rrd file if present and needed X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE development discussion Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" the follow up changes in 2316ac8bcd19142f8253e13a2a5c427dc6cfac67 look good. I built pve-cluster with the latest master and tested it with the not yet applied patches for the other involved repos in this series on my personal production machine. Going through the summary pages of different resources still worked as in my earlier test. On 2025-11-10 20:28, Thomas Lamprecht wrote: > On Mon, 03 Nov 2025 23:00:17 +0100, Aaron Lauterer wrote: >> One side effect of the RRD migration is that MAX spikes are flattened >> due to the new more fine grained resolution. >> >> If we request RRD data that was still covered in the old rrd file, we >> can fetch those data from there and then append newer data from the new >> RRD files. This way, we still have the older more coarse resolution for >> the old data and keep spikes present. >> >> [...] > > Applied, with some clean-ups/refcatoring in two follow-ups (maybe you can take > another look on them to ensure I didn't miss something) thanks! > > [2/3] RRD: fetch data from old rrd file if present and needed > commit: e43b29e90e5ac73e81292a8c32f8b6230b65b2a4 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel