public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Fiona Ebner <f.ebner@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Maximiliano Sandoval <m.sandoval@proxmox.com>
Subject: Re: [pve-devel] [PATCH docs] pvesr: Document replication network setting
Date: Mon, 21 Jul 2025 15:50:22 +0200	[thread overview]
Message-ID: <2bc1e0be-419d-42ec-8759-0bc773ecc5de@proxmox.com> (raw)
In-Reply-To: <20250721121556.192727-1-m.sandoval@proxmox.com>

Am 21.07.25 um 2:15 PM schrieb Maximiliano Sandoval:
> Signed-off-by: Maximiliano Sandoval <m.sandoval@proxmox.com>
> ---
>  pvesr.adoc | 18 +++++++++++++-----
>  1 file changed, 13 insertions(+), 5 deletions(-)
> 
> diff --git a/pvesr.adoc b/pvesr.adoc
> index 9ad02f5..9715bea 100644
> --- a/pvesr.adoc
> +++ b/pvesr.adoc
> @@ -184,11 +184,19 @@ This ID must only be specified manually if the CLI tool is used.
>  Network
>  -------
>  
> -Replication traffic will use the same network as the live guest migration. By
> -default, this is the management network. To use a different network for the
> -migration, configure the `Migration Network` in the web interface under
> -`Datacenter -> Options -> Migration Settings` or in the `datacenter.cfg`. See
> -xref:pvecm_migration_network[Migration Network] for more details.
> +By default replication traffic will go through the same network as the live
> +guest migration traffic. If the live migration network is not set this will in
> +turn default to the management network.
> +

Pre-existing, but should be fixed: it's not only live migration traffic,
but migration traffic in general. Offline storage migration will also
use the migration network.

> +To use a different network for the replication traffic, configure the
> +`Replication Network` in the web interface under `Datacenter -> Options ->
> +Replication Settings` or set the `replication` property in the `datacenter.cfg`
> +file:
> +
> +----
> +# use dedicated replication network
> +replication: secure,network=10.1.2.0/24
> +----
>  
>  Command-line Interface Examples
>  -------------------------------



_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


      reply	other threads:[~2025-07-21 13:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-21 12:15 Maximiliano Sandoval
2025-07-21 13:50 ` Fiona Ebner [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=2bc1e0be-419d-42ec-8759-0bc773ecc5de@proxmox.com \
    --to=f.ebner@proxmox.com \
    --cc=m.sandoval@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal