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.laute...@proxmox.com>
---
Notes:
changes since:
v1:
* rebase on new indentations
* make it clear that different physical networks are needed for good
redundancy
www/manager6/dc/ClusterEdit.js | 18 +++++++++++++++++-
1 file changed, 17 insertions(+), 1 deletion(-)
diff --git a/www/manager6/dc/ClusterEdit.js b/www/manager6/dc/ClusterEdit.js
index 10932585..d5ee5357 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',
@@ -37,6 +37,22 @@ Ext.define('PVE.ClusterCreateWindow', {
},
],
},
+ {
+ xtype: 'box',
+ html: `<ul><li>
+ ${gettext('Use a dedicated physical network for the
first Corosync link.')}
+ </li><li>
+ ${gettext('Configuring multiple physical 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
