From: Maximiliano Sandoval <m.sandoval@proxmox.com>
To: "Shannon Sterz" <s.sterz@proxmox.com>
Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH docs v2] pvesr: Document replication network setting
Date: Thu, 14 Aug 2025 14:23:47 +0200 [thread overview]
Message-ID: <s8ozfc2f5ws.fsf@proxmox.com> (raw)
In-Reply-To: <DBJB9Q08UNIK.1TZ0OHXYR7HHA@proxmox.com> (Shannon Sterz's message of "Wed, 23 Jul 2025 11:02:06 +0200")
"Shannon Sterz" <s.sterz@proxmox.com> writes:
> On Mon Jul 21, 2025 at 4:44 PM CEST, Maximiliano Sandoval wrote:
>> Signed-off-by: Maximiliano Sandoval <m.sandoval@proxmox.com>
>> ---
>> Differences from v1:
>> - s/live guest migration/guest migration/
>>
>> pvesr.adoc | 18 +++++++++++++-----
>> 1 file changed, 13 insertions(+), 5 deletions(-)
>>
>> diff --git a/pvesr.adoc b/pvesr.adoc
>> index 9ad02f5..186a1bd 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 guest
>> +migration traffic. If the migration network is not set this will in turn default
>> +to the management 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
>> -------------------------------
>
> looks good to me, so:
>
> Reviewed-by: Shannon Sterz <s.sterz@proxmox.com>
Bump
--
Maximiliano
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-08-14 12:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-21 14:44 Maximiliano Sandoval
2025-07-23 9:02 ` Shannon Sterz
2025-08-14 12:23 ` Maximiliano Sandoval [this message]
2025-08-14 13:46 ` [pve-devel] applied: " Fiona Ebner
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=s8ozfc2f5ws.fsf@proxmox.com \
--to=m.sandoval@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.sterz@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