public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Friedrich Weber <f.weber@proxmox.com>
To: "Michael Köppl" <m.koeppl@proxmox.com>, pve-devel@lists.proxmox.com
Subject: Re: [PATCH manager 5/5] ui: cluster info: warn users of high token timeout in join info
Date: Fri, 17 Apr 2026 10:34:47 +0200	[thread overview]
Message-ID: <3ec55616-d80a-4c69-af89-3b61b2415a72@proxmox.com> (raw)
In-Reply-To: <20260330144321.321072-6-m.koeppl@proxmox.com>

On 30/03/2026 16:47, Michael Köppl wrote:
> If another node would increase Corosync's token timeout to a level that
> might affect the stability of the cluster, display a warning hint to
> users, pointing them to the documentation section about changing the
> token coefficient, allowing them to make an informed change before
> another node.
> 
> Signed-off-by: Michael Köppl <m.koeppl@proxmox.com>
> ---
>  www/manager6/dc/Cluster.js     |  4 ++++
>  www/manager6/dc/ClusterEdit.js | 37 ++++++++++++++++++++++++++++++++++
>  2 files changed, 41 insertions(+)
> 
> diff --git a/www/manager6/dc/Cluster.js b/www/manager6/dc/Cluster.js
> index 2ec5588c3..00138f328 100644
> --- a/www/manager6/dc/Cluster.js
> +++ b/www/manager6/dc/Cluster.js
> @@ -91,6 +91,8 @@ Ext.define('PVE.ClusterAdministration', {
>                      vm.set('totem', data.totem);
>                      vm.set('isInCluster', !!data.totem.cluster_name);
>                      vm.set('nodelist', data.nodelist);
> +                    vm.set('expected_timeout', data.expected_timeout);
> +                    vm.set('timeout_warning_level', data.timeout_warning_level);
>  
>                      let nodeinfo = data.nodelist.find((el) => el.name === data.preferred_node);
>  
> @@ -133,6 +135,8 @@ Ext.define('PVE.ClusterAdministration', {
>                              peerLinks: vm.get('preferred_node.peerLinks'),
>                              ring_addr: vm.get('preferred_node.ring_addr'),
>                              totem: vm.get('totem'),
> +                            expected_timeout: vm.get('expected_timeout'),
> +                            timeout_warning_level: vm.get('timeout_warning_level'),
>                          },
>                      });
>                  },
> diff --git a/www/manager6/dc/ClusterEdit.js b/www/manager6/dc/ClusterEdit.js
> index aff1515ab..a1720dbca 100644
> --- a/www/manager6/dc/ClusterEdit.js
> +++ b/www/manager6/dc/ClusterEdit.js
> @@ -55,6 +55,8 @@ Ext.define('PVE.ClusterInfoWindow', {
>          ipAddress: undefined,
>          fingerprint: undefined,
>          totem: {},
> +        expected_timeout: undefined,
> +        timeout_warning_level: undefined,
>      },
>  
>      initComponent: function () {
> @@ -113,6 +115,41 @@ Ext.define('PVE.ClusterInfoWindow', {
>              },
>          );
>  
> +        if (joinInfo.expected_timeout && joinInfo.timeout_warning_level) {
> +            let level;
> +            if (joinInfo.timeout_warning_level === 'change-strongly-recommended') {
> +                level = gettext('Changing token coefficient is strongly recommended');
> +            } else if (joinInfo.timeout_warning_level === 'change-recommended') {
> +                level = gettext('Changing token coefficient is recommended');
> +            } else if (joinInfo.timeout_warning_level === 'optimize') {
> +                level = gettext('Token coefficient can be optimized');
> +            }
> +
> +            let msg = Ext.String.format(
> +                gettext(
> +                    "Adding another node will increase the sum of Corosync's token and consensus timeout to {0}s. {1}." +
> +                        ' See {2} for details.',
> +                ),
> +                joinInfo.expected_timeout,
> +                level,
> +                '<a target="_blank" href="https://pve.proxmox.com/pve-docs/chapter-pvecm.html#_changing_the_token_coefficient">the documentation</a>',

This should probably link to the local copy of the docs.

> +            );
> +
> +            me.items.push({
> +                xtype: 'container',
> +                border: false,
> +                padding: '0 10 10 10',
> +                items: [
> +                    {
> +                        itemId: 'joinInfoWarningHint',
> +                        xtype: 'displayfield',
> +                        userCls: 'pmx-hint',
> +                        value: msg,
> +                    },
> +                ],
> +            });
> +        }
> +
>          me.callParent();
>      },
>      dockedItems: [





  reply	other threads:[~2026-04-17  8:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-30 14:43 [PATCH cluster/manager 0/5] add warning messages for high token timeouts in clusters Michael Köppl
2026-03-30 14:43 ` [PATCH cluster 1/5] add functions to determine warning level for high token timeouts Michael Köppl
2026-04-17  8:33   ` Friedrich Weber
2026-04-17  8:33   ` Friedrich Weber
2026-03-30 14:43 ` [PATCH cluster 2/5] pvecm: warn users of high token timeouts when using nodes command Michael Köppl
2026-04-17  8:33   ` Friedrich Weber
2026-03-30 14:43 ` [PATCH cluster 3/5] api: add token timeout and warning level to cluster join info Michael Köppl
2026-04-17  8:33   ` Friedrich Weber
2026-03-30 14:43 ` [PATCH manager 4/5] ui: cluster info: move initialization of items to initComponent Michael Köppl
2026-04-17  8:33   ` Friedrich Weber
2026-03-30 14:43 ` [PATCH manager 5/5] ui: cluster info: warn users of high token timeout in join info Michael Köppl
2026-04-17  8:34   ` Friedrich Weber [this message]
2026-04-17  8:33 ` [PATCH cluster/manager 0/5] add warning messages for high token timeouts in clusters Friedrich Weber

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=3ec55616-d80a-4c69-af89-3b61b2415a72@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal