[pve-devel] [PATCH docs/manager v2 0/7] by expanding on it in the docs and the UI.

[pve-devel] [PATCH docs/manager v2 0/7] by expanding on it in the docs and the UI.

[Aaron Lauterer]

the doc patches have some cleanup and new anchor patches
the second ui patch is to fix an external link that I noticed and is
just a drive-by patch.

docs:

Aaron Lauterer (5):
  pvecm: drop notes about old version incompatibilities
  pvecm: add anchor for cluster requirements
  pvecm: add anchor for corosync exernal vote support
  pvecm: extend cluster Requirements
  ha-manager: expand requirements

 ha-manager.adoc |  7 ++++++-
 pvecm.adoc      | 41 ++++++++++++++++++++++++++---------------
 2 files changed, 32 insertions(+), 16 deletions(-)


manager:

Aaron Lauterer (2):
  ui: cluster create: add recommendations for cluster networks
  ui: guest import: make sure an external link has target _blank

 www/manager6/dc/ClusterEdit.js     | 18 +++++++++++++++++-
 www/manager6/window/GuestImport.js |  2 +-
 2 files changed, 18 insertions(+), 2 deletions(-)


Summary over all repositories:
  4 files changed, 50 insertions(+), 18 deletions(-)

-- 
Generated by git-murpp 0.8.1


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

[pve-devel] [PATCH docs v2 1/5] pvecm: drop notes about old version incompatibilities

[Aaron Lauterer]

Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
---
 pvecm.adoc | 12 ------------
 1 file changed, 12 deletions(-)

diff --git a/pvecm.adoc b/pvecm.adoc
index 18f7389..47e42e2 100644
--- a/pvecm.adoc
+++ b/pvecm.adoc
@@ -77,18 +77,6 @@ Requirements
 * Online migration of virtual machines is only supported when nodes have CPUs
   from the same vendor. It might work otherwise, but this is never guaranteed.
 
-NOTE: It is not possible to mix {pve} 3.x and earlier with {pve} 4.X cluster
-nodes.
-
-NOTE: While it's possible to mix {pve} 4.4 and {pve} 5.0 nodes, doing so is
-not supported as a production configuration and should only be done temporarily,
-during an upgrade of the whole cluster from one major version to another.
-
-NOTE: Running a cluster of {pve} 6.x with earlier versions is not possible. The
-cluster protocol (corosync) between {pve} 6.x and earlier versions changed
-fundamentally. The corosync 3 packages for {pve} 5.4 are only intended for the
-upgrade procedure to {pve} 6.0.
-
 
 Preparing Nodes
 ---------------
-- 
2.39.5



_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

[pve-devel] partially-applied: [PATCH docs v2 1/5] pvecm: drop notes about old version incompatibilities

[Thomas Lamprecht]

On Fri, 27 Jun 2025 15:44:49 +0200, Aaron Lauterer wrote:
> 


Applied the docs patches, thanks!


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

[pve-devel] [PATCH docs v2 2/5] pvecm: add anchor for cluster requirements

[Aaron Lauterer]

so we can link help buttons to it

Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
---
 pvecm.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pvecm.adoc b/pvecm.adoc
index 47e42e2..a38351c 100644
--- a/pvecm.adoc
+++ b/pvecm.adoc
@@ -54,7 +54,7 @@ Grouping nodes into a cluster has the following advantages:
 
 * Cluster-wide services like firewall and HA
 
-
+[[pvecm_cluster_requirements]]
 Requirements
 ------------
 
-- 
2.39.5



_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

[pve-devel] [PATCH docs v2 3/5] pvecm: add anchor for corosync exernal vote support

[Aaron Lauterer]

so we can reference the chapter. Manually set the automatically
generated one to avoid breaking existing deep links.

Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
---
 pvecm.adoc | 1 +
 1 file changed, 1 insertion(+)

diff --git a/pvecm.adoc b/pvecm.adoc
index a38351c..3b9cfc4 100644
--- a/pvecm.adoc
+++ b/pvecm.adoc
@@ -999,6 +999,7 @@ case $- in
 esac
 ----
 
+[[_corosync_external_vote_support]]
 Corosync External Vote Support
 ------------------------------
 
-- 
2.39.5



_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

[pve-devel] [PATCH docs v2 4/5] pvecm: extend cluster Requirements

[Aaron Lauterer]

by expanding on best practices with background information as to how and
why.

Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
---

Notes:
    changes since:
    v1:
    * rephrase and reformat recommendations for additional corosync links

 pvecm.adoc | 26 ++++++++++++++++++++++++--
 1 file changed, 24 insertions(+), 2 deletions(-)

diff --git a/pvecm.adoc b/pvecm.adoc
index 3b9cfc4..d649e26 100644
--- a/pvecm.adoc
+++ b/pvecm.adoc
@@ -68,9 +68,31 @@ Requirements
 * If you are interested in High Availability, you need to have at
   least three nodes for reliable quorum. All nodes should have the
   same version.
++
+NOTE: For smaller 2-node clusters, the xref:_corosync_external_vote_support[QDevice]
+can be used to provide a 3rd vote.
 
-* We recommend a dedicated NIC for the cluster traffic, especially if
-  you use shared storage.
+* We recommend a dedicated physical NIC for the cluster traffic.
++
+NOTE: The {pve} cluster communication uses the Corosync protocol. It needs consistent
+low latency but not a lot of bandwidth. A dedicated 1 Gbit NIC is enough in
+most situations. It helps to avoid situations where other services can use up
+all the available bandwidth. Which in turn would increase the latency for the
+Corosync packets.
+
+* Additional links for cluster traffic offers redundancy in case the dedicated
+network is down.
++
+NOTE: Corosync supports up to 8 links.
++
+NOTE: To ensure reliable Corosync redundancy, it is essential to have at least
+another link on a different physical network. This enables Corosync to keep the
+cluster communication alive should the dedicated network be down.
++
+NOTE: A single link backed by a bond is not enough to provide Corosync
+redundancy. When a bonded interface fails and Corosync cannot fall back to
+another link, it can lead to  asymmetric communication in the cluster, which in
+turn can lead to the cluster losing quorum.
 
 * The root password of a cluster node is required for adding nodes.
 
-- 
2.39.5



_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

[pve-devel] [PATCH docs v2 5/5] ha-manager: expand requirements

[Aaron Lauterer]

* make it clear that the corosync/cluster communication is important
* mark hardware watchdogs as optional

Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
---
 ha-manager.adoc | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/ha-manager.adoc b/ha-manager.adoc
index 3d6fc4a..592ef96 100644
--- a/ha-manager.adoc
+++ b/ha-manager.adoc
@@ -111,6 +111,11 @@ Requirements
 You must meet the following requirements before you start with HA:
 
 * at least three cluster nodes (to get reliable quorum)
++
+NOTE: A stable {pve} cluster communication is the foundation for the high
+availability feature of {pve}. Follow the recommendations in
+xref:pvecm_cluster_requirements[{pve} cluster requirements] to avoid issues
+like nodes fencing themselves, due to an unreliable cluster communication.
 
 * shared storage for VMs and containers
 
@@ -118,7 +123,7 @@ You must meet the following requirements before you start with HA:
 
 * use reliable “server” components
 
-* hardware watchdog - if not available we fall back to the
+* optional hardware watchdog - if not available we fall back to the
   linux kernel software watchdog (`softdog`)
 
 * optional hardware fencing devices
-- 
2.39.5



_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

[pve-devel] [PATCH manager v2 1/2] ui: cluster create: add recommendations for cluster networks

[Aaron Lauterer]

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>
---

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

[pve-devel] [PATCH manager v2 2/2] ui: guest import: make sure an external link has target _blank

[Aaron Lauterer]

otherwise it will most likely open in the current tab and not in a new
one.

Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
---
 www/manager6/window/GuestImport.js | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/www/manager6/window/GuestImport.js b/www/manager6/window/GuestImport.js
index 1858bf18..19122565 100644
--- a/www/manager6/window/GuestImport.js
+++ b/www/manager6/window/GuestImport.js
@@ -1020,7 +1020,7 @@ Ext.define('PVE.window.GuestImport', {
                     gettext(
                         'EFI state cannot be imported, you may need to reconfigure the boot order (see {0})',
                     ),
-                    '<a href="https://pve.proxmox.com/wiki/OVMF/UEFI_Boot_Entries">OVMF/UEFI Boot Entries</a>',
+                    '<a target="_blank" href="https://pve.proxmox.com/wiki/OVMF/UEFI_Boot_Entries">OVMF/UEFI Boot Entries</a>',
                 ),
                 'ova-needs-extracting': gettext(
                     'Importing an OVA temporarily requires extra space on the working storage while extracting the contained disks for further processing.',
-- 
2.39.5



_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel