From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 5E6F11FF137 for ; Tue, 31 Mar 2026 22:45:01 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id C8B137850; Tue, 31 Mar 2026 22:45:28 +0200 (CEST) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Daniel Kral Subject: partially-applied: [PATCH-SERIES cluster/ha-manager/perl-rs/proxmox v3 00/40] dynamic scheduler + load rebalancer Date: Tue, 31 Mar 2026 22:44:18 +0200 Message-ID: <177498975801.536830.13867106505875506200.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260330144101.668747-1-d.kral@proxmox.com> References: <20260330144101.668747-1-d.kral@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: 1774989868459 X-SPAM-LEVEL: Spam detection results: 0 AWL -1.629 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 KAM_LOTSOFHASH 0.25 Emails with lots of hash-like gibberish RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 1 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 1 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 1 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 Message-ID-Hash: SWKSYDFPWNNNCOEFYL5AQ47FEZFRGXA2 X-Message-ID-Hash: SWKSYDFPWNNNCOEFYL5AQ47FEZFRGXA2 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 VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Mon, 30 Mar 2026 16:30:09 +0200, Daniel Kral wrote: > Most of the patches for the v3 are already R-b'd by @Dominik (many > thanks!). A lot less has changed than from v1 -> v2, I've still added > per-patch changelogs to make reviewing the rest more straightforward. > > Most changes went into > > - #05 - resource-scheduling: implement generic cluster usage > implementation > - #09 - resource-scheduling: implement rebalancing migration selection > - #13 - pve-rs: resource-scheduling: use generic usage implementation > - #19 - datacenter config: add auto rebalancing options > - #30 - usage: use add_service to add service usage to nodes > > [...] Applied the proxmox and pve-rs parts, waiting for a v4 for the rest, thanks! proxmox: [1/9] resource-scheduling: inline add_cpu_usage in score_nodes_to_start_service commit: d458ef65736a041ec58ca59d6c803c33670e534a [2/9] resource-scheduling: move score_nodes_to_start_service to scheduler crate commit: 6e538346c302113f2a611dfa1d83147679d51dca [3/9] resource-scheduling: rename service to resource where appropriate commit: d90d70dec2f55fdd93b491ebc982a318fa3850a0 [4/9] resource-scheduling: introduce generic scheduler implementation commit: 83bca6f691bf5211f366f88b07c1e5d0154054f7 [5/9] resource-scheduling: implement generic cluster usage implementation commit: 02892ae5f610e17d09e220542482803bc957232e [6/9] resource-scheduling: topsis: handle empty criteria without panics commit: 3757312486e536c7dc67c6ca35d246573f8bf9b9 [7/9] resource-scheduling: compare by nodename in score_nodes_to_start_resource commit: f05d59e81c55508483099194e5b4274dba690fad [8/9] resource-scheduling: factor out topsis alternative mapping commit: 124eebc7e31fc997d83a1e790d8325f61c3f7036 [9/9] resource-scheduling: implement rebalancing migration selection commit: 19a7e0dabc2784b004659c2b837dae1210c380cb pve-rs: [1/7] pve-rs: resource-scheduling: remove pedantic error handling from remove_node commit: 166f321127f0c72b2a3122abf92757fb135188d3 [2/7] pve-rs: resource-scheduling: remove pedantic error handling from remove_service_usage commit: 565f427d4d0ea0cd2d980f6d851b3f6bf52ac1e3 [3/7] pve-rs: resource-scheduling: move pve_static into resource_scheduling module commit: 1bac15f2b622bbb703fb69e0964671dd51cd91c2 [4/7] pve-rs: resource-scheduling: use generic usage implementation commit: c85a0ccb353624940f3366edb948a87504fd211c [5/7] pve-rs: resource-scheduling: static: replace deprecated usage structs commit: e1ab8dad3012e5175025634a9df41fe31b3af92b [6/7] pve-rs: resource-scheduling: implement pve_dynamic bindings commit: a14036cd58935aad1c75539c3fa9db37f5e4d60f [7/7] pve-rs: resource-scheduling: expose auto rebalancing methods commit: a658483556345b2e1473930b6cad9872fd2d9d8c