From: Friedrich Weber <f.weber@proxmox.com>
To: "Michael Köppl" <m.koeppl@proxmox.com>, pve-devel@lists.proxmox.com
Subject: Re: [PATCH cluster v2 6/8] api: add token timeout and warning level to cluster join info
Date: Tue, 21 Apr 2026 09:20:59 +0200 [thread overview]
Message-ID: <1b7c1d79-8524-4da8-89d4-ee91a236ec8b@proxmox.com> (raw)
In-Reply-To: <20260420164314.370023-7-m.koeppl@proxmox.com>
Thanks for the v2!
On 20/04/2026 18:42, Michael Köppl wrote:
> The token timeout in seconds and the warning level provide additional
> information for users regarding the expected token timeout in seconds
> after adding an additional node and whether changing the token
> coefficient is recommended.
>
> Signed-off-by: Michael Köppl <m.koeppl@proxmox.com>
> ---
> src/PVE/API2/ClusterConfig.pm | 22 ++++++++++++++++++++++
> 1 file changed, 22 insertions(+)
>
> diff --git a/src/PVE/API2/ClusterConfig.pm b/src/PVE/API2/ClusterConfig.pm
> index bbed40e..5739e4c 100644
> --- a/src/PVE/API2/ClusterConfig.pm
> +++ b/src/PVE/API2/ClusterConfig.pm
> @@ -571,6 +571,18 @@ __PACKAGE__->register_method({
> preferred_node => get_standard_option('pve-node'),
> totem => { type => 'object' },
> config_digest => { type => 'string' },
> + expected_timeout => {
> + type => 'number',
> + description =>
> + "Expected total timeout (in seconds) if an additional node is added.",
> + optional => 1,
> + },
> + timeout_warning_level => {
> + type => 'string',
> + description => "Warning level for the expected total timeout.",
> + optional => 1,
> + enum => ['optimize', 'change-recommended', 'change-strongly-recommended'],
> + },
> },
IMO it would be good to clarify the broad "timeout" term also here
(since it's part of the public API). But do I realize that
"expected_membership_recovery_timeout" is very long. (I guess
"timeout_warning_level" is probably fine) Maybe someone who has a better
overview over our API design can chime in?
> },
> code => sub {
> @@ -599,12 +611,22 @@ __PACKAGE__->register_method({
> $node->{pve_addr} = scalar(PVE::Cluster::remote_node_ip($name));
> }
>
> + # Total timeout if additional node is added
> + my $total_timeout_secs = PVE::Corosync::calculate_membership_recovery_timeout(
> + $totem_cfg,
> + scalar(keys %$nodelist) + 1,
> + );
> +
> + my $warning_level = PVE::Corosync::get_timeout_warning_level($total_timeout_secs);
> +
> my $res = {
> nodelist => [values %$nodelist],
> preferred_node => $nodename,
> totem => $totem_cfg,
> config_digest => $corosync_config_digest,
> + expected_timeout => $total_timeout_secs,
> };
> + $res->{timeout_warning_level} = $warning_level if defined($warning_level);
>
> return $res;
> },
next prev parent reply other threads:[~2026-04-21 7:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-20 16:43 [PATCH cluster/docs/manager v2 0/8] add warning messages for high token timeouts in clusters Michael Köppl
2026-04-20 16:43 ` [PATCH docs v2 1/8] asciidoc-pve: allow linking sections with get_help_link Michael Köppl
2026-04-20 16:43 ` [PATCH docs v2 2/8] pvecm: add explicit anchor for token coefficient section Michael Köppl
2026-04-20 16:43 ` [PATCH docs v2 3/8] pvecm: add info about warnings regarding token coefficient Michael Köppl
2026-04-20 16:43 ` [PATCH cluster v2 4/8] add functions to determine warning level for high token timeouts Michael Köppl
2026-04-20 16:43 ` [PATCH cluster v2 5/8] pvecm: warn users of high token timeouts when using status command Michael Köppl
2026-04-20 16:43 ` [PATCH cluster v2 6/8] api: add token timeout and warning level to cluster join info Michael Köppl
2026-04-21 7:20 ` Friedrich Weber [this message]
2026-04-20 16:43 ` [PATCH manager v2 7/8] ui: cluster info: move initialization of items to initComponent Michael Köppl
2026-04-20 16:43 ` [PATCH manager v2 8/8] ui: cluster info: warn users of high token timeout in join info Michael Köppl
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=1b7c1d79-8524-4da8-89d4-ee91a236ec8b@proxmox.com \
--to=f.weber@proxmox.com \
--cc=m.koeppl@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