From: Aaron Lauterer <a.lauterer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs v2 2/2] pvesr: mention how to configure specific network for replication
Date: Wed, 4 Dec 2024 17:07:49 +0100 [thread overview]
Message-ID: <20241204160749.1868857-2-a.lauterer@proxmox.com> (raw)
In-Reply-To: <20241204160749.1868857-1-a.lauterer@proxmox.com>
Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
---
changes since v1:
* reworded and mention datacenter.cfg and link to the section explaining
it in more detail
pvesr.adoc | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/pvesr.adoc b/pvesr.adoc
index e626835..9ad02f5 100644
--- a/pvesr.adoc
+++ b/pvesr.adoc
@@ -181,6 +181,14 @@ A replication job is identified by a cluster-wide unique ID. This ID is
composed of the VMID in addition to a job number.
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.
Command-line Interface Examples
-------------------------------
--
2.39.5
_______________________________________________
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:[~2024-12-04 16:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-04 16:07 [pve-devel] [PATCH docs v2 1/2] pvecm: add anchor for the migration network chapter Aaron Lauterer
2024-12-04 16:07 ` Aaron Lauterer [this message]
2024-12-09 18:58 ` [pve-devel] applied-series: " Thomas Lamprecht
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=20241204160749.1868857-2-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox