[pve-devel] [PATCH docs 1/2] pvesr: fix possible issues storage ID

[pve-devel] [PATCH docs 1/2] pvesr: fix possible issues storage ID

[Aaron Lauterer]

The same storage needs to be configured on the target node for the
replication to work.

Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
---
 pvesr.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pvesr.adoc b/pvesr.adoc
index 9eda008..4fc2de1 100644
--- a/pvesr.adoc
+++ b/pvesr.adoc
@@ -101,7 +101,7 @@ setup there may be another cause.
 
 * No free space left on the replication target storage.
 
-* Storage with same storage ID available on the target node
+* Storage with same storage ID is not available on the target node
 
 NOTE: You can always use the replication log to find out what is causing the problem.
 
-- 
2.39.5



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

[pve-devel] [PATCH docs 2/2] pvesr: mention how to configure specific network for replication

[Aaron Lauterer]

Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
---
 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
+place the replication traffic on a specific network, configure the `Migration
+Network` over the web interface, `Datacenter -> Options -> Migration Settings`.
 
 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

Re: [pve-devel] [PATCH docs 2/2] pvesr: mention how to configure specific network for replication

[Fiona Ebner]

Am 05.11.24 um 12:08 schrieb Aaron Lauterer:
> Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
> ---
>  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

[pve-devel] applied: [PATCH docs 1/2] pvesr: fix possible issues storage ID

[Fiona Ebner]

Am 05.11.24 um 12:08 schrieb Aaron Lauterer:
> The same storage needs to be configured on the target node for the
> replication to work.
> 
> Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
> ---
>  pvesr.adoc | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/pvesr.adoc b/pvesr.adoc
> index 9eda008..4fc2de1 100644
> --- a/pvesr.adoc
> +++ b/pvesr.adoc
> @@ -101,7 +101,7 @@ setup there may be another cause.
>  
>  * No free space left on the replication target storage.
>  
> -* Storage with same storage ID available on the target node
> +* Storage with same storage ID is not available on the target node
>  
>  NOTE: You can always use the replication log to find out what is causing the problem.
>  

Thanks! Did a small followup (add "the" for "the same storage ID") and
finish with a dot for consistency.


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

Re: [pve-devel] [PATCH docs 2/2] pvesr: mention how to configure specific network for replication

[Aaron Lauterer]

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 <a.lauterer@proxmox.com>
>> ---
>>   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