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

[Kevin Schneider]

On 29.04.25 15:57, Aaron Lauterer wrote:

> 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.
> +
> +* Configuring additional links for the cluster traffic can help in situations where
> +  the dedicated network is down.
> ++

Might be a nitpick, but this can be more direct and shorter I suggest

It avoids situations where other services use up the available 
bandwidth. Thus increasing the latency of the Corosync packets

Additional links for cluster traffic offers redundancy in case the 
dedicated network is down

> +NOTE: The Corosync protocol used for the {pve} cluster communication can
> +switch between multiple networks by itself and does not rely on a bonded network
> +for redundancy. You can configure up to 8 networks to be used by Corosync.

IMO this isn't strict enough and we should empathize on the importance 
of the problem. I would go for

To ensure reliable Corosync redundancy, it's essential to use at least 
two separate physical and logical networks. Single bonded interfaces do 
not provide Corosync redundancy. When a bonded interface fails without 
redundancy, it can lead to asymmetric communication, causing all nodes 
to lose quorum—even if more than half of them can still communicate with 
each other.