From: Fiona Ebner <f.ebner@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Hannes Duerr <h.duerr@proxmox.com>
Subject: Re: [pve-devel] [PATCH pve-docs] ha crs: remove technology preview note of static-load scheduler
Date: Fri, 13 Dec 2024 15:49:31 +0100 [thread overview]
Message-ID: <9b61c54a-74f9-44b5-a451-6ef714a62f07@proxmox.com> (raw)
In-Reply-To: <20241213143251.190391-1-h.duerr@proxmox.com>
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
next prev parent reply other threads:[~2024-12-13 14:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 14:32 Hannes Duerr
2024-12-13 14:49 ` Fiona Ebner [this message]
2024-12-13 15:00 ` Hannes Dürr
2024-12-13 15:05 ` Fiona Ebner
2024-12-13 18:41 ` Thomas Lamprecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9b61c54a-74f9-44b5-a451-6ef714a62f07@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=h.duerr@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox