From: Aaron Lauterer <a.lauterer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs] Revert "Document that active-backup is recommended for corosync"
Date: Tue, 12 Jan 2021 14:20:08 +0100 [thread overview]
Message-ID: <20210112132008.8621-1-a.lauterer@proxmox.com> (raw)
This reverts commit 649098a64ecaffc7215ec0556e76787595b38e88.
This seems to be related to the use of multicast in older corosync
versions. Since corosync v3 is using unicast we can drop this
---
pve-network.adoc | 6 +-----
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/pve-network.adoc b/pve-network.adoc
index 34cc6c8..1c3a17c 100644
--- a/pve-network.adoc
+++ b/pve-network.adoc
@@ -336,11 +336,7 @@ traffic.
If your switch support the LACP (IEEE 802.3ad) protocol then we recommend using
the corresponding bonding mode (802.3ad). Otherwise you should generally use the
-active-backup mode. +
-// http://lists.linux-ha.org/pipermail/linux-ha/2013-January/046295.html
-If you intend to run your cluster network on the bonding interfaces, then you
-have to use active-passive mode on the bonding interfaces, other modes are
-unsupported.
+active-backup mode.
The following bond configuration can be used as distributed/shared
storage network. The benefit would be that you get more speed and the
--
2.20.1
reply other threads:[~2021-01-12 13:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210112132008.8621-1-a.lauterer@proxmox.com \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.