From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 4512C1FF161 for ; Wed, 4 Dec 2024 17:09:22 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 2A33DC075; Wed, 4 Dec 2024 17:09:22 +0100 (CET) Message-ID: Date: Wed, 4 Dec 2024 17:08:49 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Content-Language: en-US To: Fiona Ebner , Proxmox VE development discussion References: <20241105110801.151806-1-a.lauterer@proxmox.com> <20241105110801.151806-2-a.lauterer@proxmox.com> <755a2dbb-439d-47ae-bf53-01d39d07bc11@proxmox.com> From: Aaron Lauterer In-Reply-To: <755a2dbb-439d-47ae-bf53-01d39d07bc11@proxmox.com> X-SPAM-LEVEL: Spam detection results: 0 AWL -0.035 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [proxmox.com] Subject: Re: [pve-devel] [PATCH docs 2/2] pvesr: mention how to configure specific network for replication X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE development discussion Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" I sent a v2 https://lore.proxmox.com/pve-devel/20241204160749.1868857-1-a.lauterer@proxmox.com/T/#t On 2024-11-29 16:17, Fiona Ebner wrote: > Am 05.11.24 um 12:08 schrieb Aaron Lauterer: >> Signed-off-by: Aaron Lauterer >> --- >> pvesr.adoc | 6 ++++++ >> 1 file changed, 6 insertions(+) >> >> diff --git a/pvesr.adoc b/pvesr.adoc >> index 4fc2de1..209f306 100644 >> --- a/pvesr.adoc >> +++ b/pvesr.adoc >> @@ -181,6 +181,12 @@ 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 >> +------- >> + >> +By default, the replication traffic will choose the management network. To > Maybe s/choose/use/ ? > >> +place the replication traffic on a specific network, configure the `Migration >> +Network` over the web interface, `Datacenter -> Options -> Migration Settings`. > > I kinda feel like it's better the other way around: > Say replication traffic will use the Migration Network (which is also > used for guest migration) and then say what that is by default and where > to find it. I'd also mention that it's in the datacenter.cfg > configuration file via CLI. > > Just nits of course, but if we're already at it ;) _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel