From: "Michael Köppl" <m.koeppl@proxmox.com>
To: "Michael Köppl" <m.koeppl@proxmox.com>, pve-devel@lists.proxmox.com
Subject: superseded: [PATCH cluster/manager 0/5] add warning messages for high token timeouts in clusters
Date: Mon, 20 Apr 2026 18:44:20 +0200 [thread overview]
Message-ID: <DHY4TA3CFBZ0.3L6S0CUIODPN0@proxmox.com> (raw)
In-Reply-To: <20260330144321.321072-1-m.koeppl@proxmox.com>
Superseded-by:
https://lore.proxmox.com/pve-devel/20260420164314.370023-1-m.koeppl@proxmox.com
On Mon Mar 30, 2026 at 4:43 PM CEST, Michael Köppl wrote:
> This patch series introduces warnings informing users about high token
> timeouts in their clusters. A recent change [0] lowered the token
> coefficient for clusters and allowed adapting it. However, this change
> only affects new clusters. As described in [1], users with existing
> cluster should be informed about the high token timeouts in their
> configurations and what they can do to alleviate this problem.
>
> Thus, warnings are added to the `pvecm nodes` command as well as to the
> cluster join info dialog in the web UI. The warning in the web UI warns
> users about the effect adding another node would have to allow them to
> make an informed change before adding another node.
>
> [0] https://git.proxmox.com/?p=pve-cluster.git;a=commit;h=a7b1c765b9223a81fb2dc4f072d6a6c095583cda
> [1] https://bugzilla.proxmox.com/show_bug.cgi?id=7398
>
> pve-cluster:
>
> Michael Köppl (3):
> add functions to determine warning level for high token timeouts
> pvecm: warn users of high token timeouts when using nodes command
> api: add token timeout and warning level to cluster join info
>
> src/PVE/API2/ClusterConfig.pm | 20 ++++++++++++++
> src/PVE/CLI/pvecm.pm | 9 +++++++
> src/PVE/Corosync.pm | 50 +++++++++++++++++++++++++++++++++++
> 3 files changed, 79 insertions(+)
>
>
> pve-manager:
>
> Michael Köppl (2):
> ui: cluster info: move initialization of items to initComponent
> ui: cluster info: warn users of high token timeout in join info
>
> www/manager6/dc/Cluster.js | 4 +
> www/manager6/dc/ClusterEdit.js | 139 +++++++++++++++++++++------------
> 2 files changed, 95 insertions(+), 48 deletions(-)
>
>
> Summary over all repositories:
> 5 files changed, 174 insertions(+), 48 deletions(-)
prev parent reply other threads:[~2026-04-20 16:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-30 14:43 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-20 8:28 ` Michael Köppl
2026-04-20 9:39 ` Friedrich Weber
2026-04-20 13:50 ` Michael Köppl
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-04-20 13:33 ` Michael Köppl
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
2026-04-17 8:33 ` [PATCH cluster/manager 0/5] add warning messages for high token timeouts in clusters Friedrich Weber
2026-04-20 16:44 ` Michael Köppl [this message]
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=DHY4TA3CFBZ0.3L6S0CUIODPN0@proxmox.com \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.