From: Aaron Lauterer <a.lauterer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH manager 6/7] ui: cluster create: add recommendations for cluster networks
Date: Tue, 29 Apr 2025 15:57:48 +0200 [thread overview]
Message-ID: <20250429135749.1335521-7-a.lauterer@proxmox.com> (raw)
In-Reply-To: <20250429135749.1335521-1-a.lauterer@proxmox.com>
adding a short list of recommendations regarding the cluster network
right where the cluster is created will hopefully reduce the amount of
clusters that don't follow best practices.
We also point the help button to the requirements a little bit earlier
in the docs than what it used to be.
Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
---
www/manager6/dc/ClusterEdit.js | 15 ++++++++++++++-
1 file changed, 14 insertions(+), 1 deletion(-)
diff --git a/www/manager6/dc/ClusterEdit.js b/www/manager6/dc/ClusterEdit.js
index b56df713..399d2393 100644
--- a/www/manager6/dc/ClusterEdit.js
+++ b/www/manager6/dc/ClusterEdit.js
@@ -12,7 +12,7 @@ Ext.define('PVE.ClusterCreateWindow', {
subject: gettext('Cluster'),
showTaskViewer: true,
- onlineHelp: 'pvecm_create_cluster',
+ onlineHelp: 'pvecm_cluster_requirements',
items: {
xtype: 'inputpanel',
@@ -33,6 +33,19 @@ Ext.define('PVE.ClusterCreateWindow', {
name: 'links',
},
],
+ },
+ {
+ xtype: 'box',
+ html: `<ul><li>
+ ${gettext('Use a dedicated physical network for the first Corosync link.')}
+ </li><li>
+ ${gettext('Configuring multiple links is recommended for redundancy.')}
+ </li><li>
+ ${Ext.String.format(
+ gettext('For more information, check the <a target="_blank" href="{0}">reference documentation</a>.'),
+ Proxmox.Utils.get_help_link('pvecm_cluster_requirements'))}
+ </li></ul>`,
+ border: 0,
}],
},
});
--
2.39.5
_______________________________________________
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:[~2025-04-29 13:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 13:57 [pve-devel] [PATCH docs, manager 0/7] add and expand on cluster recommendations Aaron Lauterer
2025-04-29 13:57 ` [pve-devel] [PATCH docs 1/7] pvecm: drop notes about old version incompatibilities Aaron Lauterer
2025-05-07 15:22 ` Kevin Schneider
2025-05-12 12:01 ` Thomas Lamprecht
2025-04-29 13:57 ` [pve-devel] [PATCH docs 2/7] pvecm: add anchor for cluster requirements Aaron Lauterer
2025-04-29 13:57 ` [pve-devel] [PATCH docs 3/7] pvecm: add anchor for corosync exernal vote support Aaron Lauterer
2025-04-29 13:57 ` [pve-devel] [PATCH docs 4/7] pvecm: extend cluster Requirements Aaron Lauterer
2025-05-07 15:22 ` Kevin Schneider
2025-05-08 11:54 ` Robin Christ
2025-04-29 13:57 ` [pve-devel] [PATCH docs 5/7] ha-manager: expand requirements Aaron Lauterer
2025-04-29 13:57 ` Aaron Lauterer [this message]
2025-04-29 13:57 ` [pve-devel] [PATCH manager 7/7] ui: guest import: make sure an external link has target _blank Aaron Lauterer
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=20250429135749.1335521-7-a.lauterer@proxmox.com \
--to=a.lauterer@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