From: GM <gianni.milo22@gmail.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] 2 host cluster, direct link: best configuration?
Date: Sat, 19 Feb 2022 19:00:43 +0000 [thread overview]
Message-ID: <CACzVk9WhsDG4E_1c23wLQV+8Rhyw7trLuA5KF2KHLA0s8K6yng@mail.gmail.com> (raw)
In-Reply-To: <4535ei-8j11.ln1@hermione.lilliput.linux.it>
I'd personally use option 1, dedicated nic(s) or vlans for LAN and Corosync
network.Then I'd use the dedicated 10G link only for storage replication.
All 3 networks would be setup on different network subnets. Storage
replication uses "migration network" for the replication, so you could
setup that on the dedicated 10G link, so that it does not interfere with
the corosync/lan traffic. Migration network can be setup either via the
datacenter.cfg or via the web gui (Datacenter -> Options -> Migration
settings).
On Sat, 19 Feb 2022 at 16:10, Marco Gaiarin <gaio@lilliput.linux.it> wrote:
>
> We have to setup a little 2 node cluster, with symmetrical nodes, using
> replication.
>
> For that, we have added a 10G interface, and setup a direct link between
> the
> two server.
>
> But how is better to setup the link? Some ideas:
>
> 1) another network, different from LAN
>
> pro: simple
> cons: replica happen only on cluster/corosync interface? So i have to
> setup corosync on direct link addresses?
>
>
> 2) ip override; eg LAN interfaces are 10.37.5.21/21 and 10.37.5.22/21;
> direct link interfaces are 10.37.5.21/32 and 10.37.5.22/32, and an
> explicitly route to other host
>
> pro: if direct link go down, we can simple tear down interfaces
> cons: no auto, interfaces have to tear down manually
>
>
> 3) setup a bridge around LAN and direct link cable, setup STP and leave the
> switches all the work.
>
> This config suggested, more or less, by:
> https://pve.proxmox.com/wiki/Full_Mesh_Network_for_Ceph_Server
>
>
> Thanks.
>
> --
> Io chiedo quando sara` che l'uomo potra` imparare
> a vivere senza ammazzare e il vento si posera` (F. Guccini)
>
>
>
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
>
next prev parent reply other threads:[~2022-02-19 19:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-18 17:55 Marco Gaiarin
2022-02-19 19:00 ` GM [this message]
2022-02-21 12:14 ` Marco Gaiarin
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=CACzVk9WhsDG4E_1c23wLQV+8Rhyw7trLuA5KF2KHLA0s8K6yng@mail.gmail.com \
--to=gianni.milo22@gmail.com \
--cc=pve-user@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