From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Aaron Lauterer <a.lauterer@proxmox.com>
Subject: [pve-devel] applied: [PATCH docs] network: rephrase corosync and bonds recommendations
Date: Tue, 6 Jun 2023 16:47:56 +0200 [thread overview]
Message-ID: <ab36cbe4-6d1b-9a1b-04ec-9180406923ab@proxmox.com> (raw)
In-Reply-To: <20230324130347.737762-1-a.lauterer@proxmox.com>
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@proxmox.com>
> ---
> pve-network.adoc | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
>
applied, thanks!
prev parent reply other threads:[~2023-06-06 14:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 13:03 [pve-devel] " Aaron Lauterer
2023-06-06 14:47 ` Thomas Lamprecht [this message]
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=ab36cbe4-6d1b-9a1b-04ec-9180406923ab@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=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