From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <pve-devel-bounces@lists.proxmox.com> Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 9D3841FF171 for <inbox@lore.proxmox.com>; Fri, 13 Dec 2024 16:00:41 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id C49601122C; Fri, 13 Dec 2024 16:00:46 +0100 (CET) Message-ID: <b1151ece-0461-48e4-9368-448fe1404299@proxmox.com> Date: Fri, 13 Dec 2024 16:00:43 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird To: Fiona Ebner <f.ebner@proxmox.com>, Proxmox VE development discussion <pve-devel@lists.proxmox.com> References: <20241213143251.190391-1-h.duerr@proxmox.com> <9b61c54a-74f9-44b5-a451-6ef714a62f07@proxmox.com> Content-Language: en-US From: =?UTF-8?Q?Hannes_D=C3=BCrr?= <h.duerr@proxmox.com> In-Reply-To: <9b61c54a-74f9-44b5-a451-6ef714a62f07@proxmox.com> X-SPAM-LEVEL: Spam detection results: 0 AWL 0.037 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 URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [proxmox.com] Subject: Re: [pve-devel] [PATCH pve-docs] ha crs: remove technology preview note of static-load scheduler X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com> List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-devel>, <mailto:pve-devel-request@lists.proxmox.com?subject=unsubscribe> List-Archive: <http://lists.proxmox.com/pipermail/pve-devel/> List-Post: <mailto:pve-devel@lists.proxmox.com> List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help> List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>, <mailto:pve-devel-request@lists.proxmox.com?subject=subscribe> Reply-To: Proxmox VE development discussion <pve-devel@lists.proxmox.com> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" <pve-devel-bounces@lists.proxmox.com> Do I understand you correctly that the feature is not yet ready to be removed from the technology preview? On 12/13/24 15:49, Fiona Ebner wrote: > Am 13.12.24 um 15:32 schrieb Hannes Duerr: >> The static load scheduler feature was applied on 17/11/2022 [0] and can >> be considered stable now >> > The timing alone doesn't tell much. While there don't seem to be any > real issues with the implementation, it was never fully fleshed out and > there are certainly some fundamental improvements that can be made, e.g. > consider non-HA guests, improve calculation when there are thousands of > services. > >> [0] https://lore.proxmox.com/pve-devel/20221117140018.105004-1-f.ebner@proxmox.com/ >> >> Signed-off-by: Hannes Duerr <h.duerr@proxmox.com> >> --- >> ha-manager.adoc | 2 -- >> 1 file changed, 2 deletions(-) >> >> diff --git a/ha-manager.adoc b/ha-manager.adoc >> index 3d6fc4a..666576d 100644 >> --- a/ha-manager.adoc >> +++ b/ha-manager.adoc >> @@ -1053,8 +1053,6 @@ Non-HA-managed services are currently not counted. >> Static-Load Scheduler >> ~~~~~~~~~~~~~~~~~~~~~ >> >> -IMPORTANT: The static mode is still a technology preview. >> - >> Static usage information from HA services on each node is used to choose a >> recovery node. Usage of non-HA-managed services is currently not considered. >> _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel