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 AAA9A1FF165 for ; Thu, 31 Jul 2025 06:11:36 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 4B62831066; Thu, 31 Jul 2025 06:13:01 +0200 (CEST) Message-ID: Date: Thu, 31 Jul 2025 06:12:57 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Beta To: Proxmox VE development discussion , Aaron Lauterer References: <20250726010626.1496866-1-a.lauterer@proxmox.com> Content-Language: en-US From: Thomas Lamprecht In-Reply-To: <20250726010626.1496866-1-a.lauterer@proxmox.com> X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1753935165839 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.031 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: [pve-devel] applied: [PATCH many v4 00/31] Expand and migrate RRD data and add/change summary graphs 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-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" Am 26.07.25 um 03:06 schrieb Aaron Lauterer: > This patch series does a few things. It expands the RRD format for nodes and > VMs. For all types (nodes, VMs, storage) we adjust the aggregation to align > them with the way they are done on the Backup Server. Therefore, we have new > RRD defitions for all 3 types. applied series with a bunch of follow-ups from Lukas (thanks!) and myself, thanks! > KNOWN ISSUES: > * on a live system, renaming the source RRD files to FILE.old doesn't seem to > work as expected and besides the renamed ones, new ones without the .old prefix > show up again. I suspect some interaction with rrdached and/or pmxcfs receiving > new data. FWIW, while I prepared a service to handle this on-boot, delaying that by more than a one or two minutes is not ideal either, and while we could differentiate between smaller and bigger setups (thus less or more time required for the migration), it is probably simpler just doing it on the upgrade itself, albeit getting this synchronized would be good too, maybe playing around with stopping rrdcached before the upgrade might help, or make pmxcfs not commit anything if it sees a flag file or the like, but it's only a short period of time of RRD metrics, nothing critical, so I did not want to block this on that. btw. It would be still very important to add a short section for this to the upgrade guide, mentioning how one can continue the upgrade again later, not all will see the message in the d/postinst output. _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel