[pve-devel] applied: [PATCH docs] network: rephrase corosync and bonds recommendations

Thomas Lamprecht t.lamprecht at proxmox.com
Tue Jun 6 16:47:56 CEST 2023


Am 24/03/2023 um 14:03 schrieb Aaron Lauterer:
> I suspect that the old one seems to be related to multicast traffic and
> LACP bonds.
> 
> The link in the comment is dead by now. It seems this is one occasion
> where the internet actually forgets as I cannot find the actual message
> of that mailing list thread anymore. Therefore I cannot say for sure
> what the exact issue was. But it was introduced in commit
> 649098a64ecaffc7215ec0556e76787595b38e88 which unfortunately also
> doesn't have more information.
> 
> Since with Corosync 3, unicast is used, that recommentation is probably
> not accurate anymore. At least I am not aware of any issues with
> Corosync on LACP bonds in recent years. Therefore, rather recommend to
> configure Corosync on multiple networks instead of bonds to follow best
> practice.
> 
> Signed-off-by: Aaron Lauterer <a.lauterer at proxmox.com>
> ---
>  pve-network.adoc | 10 +++++-----
>  1 file changed, 5 insertions(+), 5 deletions(-)
> 
>

applied, thanks!





More information about the pve-devel mailing list