From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [45.144.208.40]) by lore.proxmox.com (Postfix) with ESMTPS id C0A8B1FF0C0 for ; Wed, 18 Nov 2026 15:41:54 +0100 (CET) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 4BE892173D; Wed, 18 Nov 2026 15:41:53 +0100 (CET) Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Wed, 18 Nov 2026 15:41:48 +0100 Message-Id: Subject: superseded: [PATCH-SERIES ha-manager v2 00/16] some sid parsing and LRM speedup improvements From: "Daniel Kral" To: "Daniel Kral" , X-Mailer: aerc 0.22.0-45-gc30c872fde7b-dirty References: <20261112163113.294302-3-d.kral@proxmox.com> In-Reply-To: <20261112163113.294302-3-d.kral@proxmox.com> X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1795012908551 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.498 Adjusted score from AWL reputation of From: address DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust 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: JHSW5HQ2WL6H6CWO6525YFFM5XNLIJYS X-Message-ID-Hash: JHSW5HQ2WL6H6CWO6525YFFM5XNLIJYS X-MailFrom: d.kral@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 VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Thanks a lot for testing @Michael! Superseded-by: https://lore.proxmox.com/pve-devel/20261118142556.218589-1-d= .kral@proxmox.com/ Though barely missed being able to rebase on the new master, will send a v4! On Thu Nov 12, 2026 at 5:30 PM CET, Daniel Kral wrote: > Changes since v1: > - rebase on master > - cleanup the patch messages a bit > - cache the read_service_config() instead of putting it in the 'new' > update_lrm_status() to not change the current behavior as well > unnecessarily reading the HA resource config in idle rounds > - do not prune LRM results in flush_lrm_status() but properly prune > these in update_lrm_status() and resource_command_finished(), because > flush_lrm_status() could be called by a signal handler calling > shutdown_request()