From: "DERUMIER, Alexandre" <Alexandre.DERUMIER@groupe-cyllene.com>
To: "uwe.sauter.de@gmail.com" <uwe.sauter.de@gmail.com>,
"pve-user@lists.proxmox.com" <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] How to configure which network is used for migration
Date: Thu, 15 Dec 2022 08:01:16 +0000 [thread overview]
Message-ID: <448a49514cec8fa89ea87821a41aa95248216b00.camel@groupe-cyllene.com> (raw)
In-Reply-To: <0792849c-8d3f-e0de-460c-e89245c8d12b@gmail.com>
Hi,
datacenter->options->migration settings->network
Le jeudi 15 décembre 2022 à 08:23 +0100, Uwe Sauter a écrit :
> Good morning,
>
> I'm currently replacing one PVE cluster with another. The new
> hardware has a bunch of different
> network interfaces that I want to use to separate VM traffic from
> Corosync/Ceph/migration traffic.
>
> Is there a way to configure the interface/network that is used for
> migration or does this depend on
> the combination of hostname resolution and which hostname was used to
> create the cluster?
> (I have various hostnames configured per host, for each configured
> network one, so that I can
> explicitly choose which interface I use to connect to a host.)
>
> Regards,
>
> Uwe
>
>
> Interface configuration:
>
> eno1np0 --+-- untagged VLAN X -- Corosync ring 1/management network
> (192.168.1.0/24)
>
> eno2np1 N/C
>
> enp3s0 --+
> +-- bond0 --+-- bond0.100 -- vmbr100 \
> enp4s0 --+ +-- bond0.101 -- vmbr101 +-- VM traffic
> +-- bond0.102 -- vmbr102 /
>
> enp5s0 --+
> +-- bond1 --+-- untagged VLAN Y -- Corosync ring 0/Ceph
> (172.16.1.0/24)
> enp6s0 --+
>
> _______________________________________________
> 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-12-15 8:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 7:23 Uwe Sauter
2022-12-15 8:01 ` DERUMIER, Alexandre [this message]
[not found] ` <em7e8e2199-2131-46e9-8480-80695f479cc6@4148cfe7.com>
2022-12-15 8:11 ` Uwe Sauter
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=448a49514cec8fa89ea87821a41aa95248216b00.camel@groupe-cyllene.com \
--to=alexandre.derumier@groupe-cyllene.com \
--cc=pve-user@lists.proxmox.com \
--cc=uwe.sauter.de@gmail.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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal