[pve-devel] [PATCH pve-docs] Update Dokumentation to Systemd Network Interface Names

--- pve-network.adoc | 72 +--- pvecm.adoc | 12 +- qm.adoc | 2 +- 3 files changed, 60 insertions(+), 26 deletions(-) diff --git a/pve-network.adoc b/pve-network.adoc index 45f6424..102bb8e 100644 --- a/pve-network.adoc

[pve-devel] [pve-zsync] Fix send_config with IPv6

Add square brackets on IP. --- pve-zsync | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pve-zsync b/pve-zsync index 5fa5292..b3241ff 100644 --- a/pve-zsync +++ b/pve-zsync @@ -948,7 +948,7 @@ sub send_image { run_cmd(['scp', '--', $source_target, "root\@[$dest

[pve-devel] [PATCH pve-manager] Fix pveceph createosd

The --filestore flag is now required see doc of ceph. If the --bluestore argument is given, a bluestore objectstore will be created. If --filestore is provided, a legacy FileStore objectstore will be created. If neither is specified, we default to BlueStore. --- PVE/API2/Ceph.pm | 2 +- 1 file

[pve-devel] [PATCH qemu-server] Fix freeze_needed

We want freeze the filesystem if the vmstate is not saved, because when we save the state we need not to freeze the filesystem. --- PVE/QemuConfig.pm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/PVE/QemuConfig.pm b/PVE/QemuConfig.pm index e327482..e2fa2ba 100644 --- a/PVE/Q

[pve-devel] [PATCH pve-storage] We allow uppercase characters in snapshot names. pvesm import and export must allow uppercase characters too.

--- PVE/CLI/pvesm.pm | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/PVE/CLI/pvesm.pm b/PVE/CLI/pvesm.pm index 9455595..6b37c05 100755 --- a/PVE/CLI/pvesm.pm +++ b/PVE/CLI/pvesm.pm @@ -183,7 +183,7 @@ __PACKAGE__->register_method ({ base => { des

[pve-devel] [PATCH V2 pve-storage] Use json format instead of hard code regex.

--- PVE/CLI/pvesm.pm | 6 ++ 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/PVE/CLI/pvesm.pm b/PVE/CLI/pvesm.pm index 9455595..66ae955 100755 --- a/PVE/CLI/pvesm.pm +++ b/PVE/CLI/pvesm.pm @@ -183,8 +183,7 @@ __PACKAGE__->register_method ({ base => { d

[pve-devel] Adapt regex in pvesm import/export.

We allow uppercase characters in snapshot names. pvesm import and export must allow uppercase characters too. [PATCH V2 pve-storage] Use JSON schema instead of hardcoding. ___ pve-devel mailing list pve-devel@pve.proxmox.com https://pve.proxmox.com/cgi

[pve-devel] [PATCH pve-common] Extend JSON format schema with pve_base_snapshot.

--- src/PVE/JSONSchema.pm | 11 +++ 1 file changed, 11 insertions(+) diff --git a/src/PVE/JSONSchema.pm b/src/PVE/JSONSchema.pm index 3295599..92d60b9 100644 --- a/src/PVE/JSONSchema.pm +++ b/src/PVE/JSONSchema.pm @@ -163,6 +163,17 @@ sub pve_verify_vmid { return $vmid; } +registe

[pve-devel] [PATCH V3 pve-storage] Use json format instead of hard code regex.

--- PVE/CLI/pvesm.pm | 6 ++ 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/PVE/CLI/pvesm.pm b/PVE/CLI/pvesm.pm index 9455595..12e68fc 100755 --- a/PVE/CLI/pvesm.pm +++ b/PVE/CLI/pvesm.pm @@ -183,8 +183,7 @@ __PACKAGE__->register_method ({ base => { d

[pve-devel] Adapt regex in pvesm import/export.

We allow uppercase characters in snapshot names. pvesm import and export must allow uppercase characters too. [PATCH V2 pve-storage] Use JSON schema instead of hardcoding. [PATCH V3 pve-storage] Correct typo. ___ pve-devel mailing list pve-devel@pve.p

[pve-devel] [PATCH pve-common] Extend JSON format schema with pve_base_snapshot.

--- src/PVE/JSONSchema.pm | 11 +++ 1 file changed, 11 insertions(+) diff --git a/src/PVE/JSONSchema.pm b/src/PVE/JSONSchema.pm index 3295599..92d60b9 100644 --- a/src/PVE/JSONSchema.pm +++ b/src/PVE/JSONSchema.pm @@ -163,6 +163,17 @@ sub pve_verify_vmid { return $vmid; } +registe

[pve-devel] [pve-container] Exclude .zfs dir on vzdump

The .zfs snapdir is normally hidden, but when it is set to 'visible' we back it up. On restore vzdump try to write .zfs dir what is always read only. --- src/PVE/VZDump/LXC.pm | 7 +++ 1 file changed, 7 insertions(+) diff --git a/src/PVE/VZDump/LXC.pm b/src/PVE/VZDump/LXC.pm index 45a851c..c

[pve-devel] [PATCH] Exclude .zfs folder which is located on zfs subvolume.

The .zfs snapdir is usually hidden, but if it is set to "visible", we can back it up. This increases the amount of backup space and makes restoration impossible. We will exclude only the .zfs in the root of the mountponit and in all other volumes which are mounted in the container. This applies on

[pve-devel] [PATCH V4 pve-common] Extend the JSON format schema with pve_base_snapshot.

A base snapshot can be a replication snapshot or a normal snapshot. Normal snapshots use the format configid. --- src/PVE/JSONSchema.pm | 14 ++ 1 file changed, 14 insertions(+) diff --git a/src/PVE/JSONSchema.pm b/src/PVE/JSONSchema.pm index 3295599..501f0fa 100644 --- a/src/PVE/JSON

[pve-devel] [PATCH V4 pve-storage] Use json format instead of hard code regex.

--- PVE/CLI/pvesm.pm | 6 ++ 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/PVE/CLI/pvesm.pm b/PVE/CLI/pvesm.pm index 9455595..12e68fc 100755 --- a/PVE/CLI/pvesm.pm +++ b/PVE/CLI/pvesm.pm @@ -183,8 +183,7 @@ __PACKAGE__->register_method ({ base => { d

[pve-devel] Adapt regex in pvesm import/export.

We allow uppercase characters in snapshot names. pvesm import and export must allow uppercase characters too. [PATCH V2] Use JSON schema instead of hardcoding. [PATCH V3 pve-storage] Correct typo. [PATCH V4] Make base snapshot more specific. ___ pve-

[pve-devel] [PATCH 3/4] Remove unneeded packages.

--- pvepatches/remove-unneeded-from-control.patch | 59 ++- 1 file changed, 58 insertions(+), 1 deletion(-) diff --git a/pvepatches/remove-unneeded-from-control.patch b/pvepatches/remove-unneeded-from-control.patch index 7d68ae8..ddf8ac4 100644 --- a/pvepatches/remove-unn

[pve-devel] RFC bump Version to 2.8.0 OpenvSwitch

To build the package "make download" must be called first. openvswitch tarball is not included. This series bump the openvswitch version to 2.8.0. Fix an unsightly dependency in the deb package. Remove new packages wich are not supported by us. ___ pve

[pve-devel] [PATCH 4/4] Remove useless rules.

--- pvepatches/remove-unneeded-rules.patch | 39 ++ pvepatches/series | 1 + 2 files changed, 40 insertions(+) create mode 100644 pvepatches/remove-unneeded-rules.patch diff --git a/pvepatches/remove-unneeded-rules.patch b/pvepatches/remove-

[pve-devel] [PATCH 2/4] Change dependency.

The new Package libopenvswitch need not libssl-dev package. Libssl1.1 ok and will not install a new package. Libssl-dev is need for the libopenvswitch. --- pvepatches/remove-unneeded-from-control.patch | 17 + 1 file changed, 17 insertions(+) diff --git a/pvepatches/remove-unneed

Re: [pve-devel] RFC bump Version to 2.8.0 OpenvSwitch

n has only 16.11.1 in stretch. > I had sent a patch some months ago > > https://pve.proxmox.com/pipermail/pve-devel/2017-April/026089.html > > It's only add support to dpdk, but don't enable it by default, so I think > it's quite safe. > > > - Mail o

[pve-devel] [PATCH V5 pve-manager] Adjust the option name to a new name scheme.

--- PVE/CLI/pvesr.pm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/PVE/CLI/pvesr.pm b/PVE/CLI/pvesr.pm index 7da94404..1ed3d535 100644 --- a/PVE/CLI/pvesr.pm +++ b/PVE/CLI/pvesr.pm @@ -75,7 +75,7 @@ __PACKAGE__->register_method ({ minimum => 0,

[pve-devel] [PATCH V5 pve-common 2/2] Extend the JSON format schema with pve-base-snapshot.

A base snapshot can be a replication snapshot or a normal snapshot. --- src/PVE/JSONSchema.pm | 13 + 1 file changed, 13 insertions(+) diff --git a/src/PVE/JSONSchema.pm b/src/PVE/JSONSchema.pm index 996aef2..2ed5b9a 100644 --- a/src/PVE/JSONSchema.pm +++ b/src/PVE/JSONSchema.pm @@ -1

[pve-devel] [PATCH V5 pve-storage] Use a json format instead of hard code regex.

--- PVE/CLI/pvesm.pm | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/PVE/CLI/pvesm.pm b/PVE/CLI/pvesm.pm index 9455595..57d10f4 100755 --- a/PVE/CLI/pvesm.pm +++ b/PVE/CLI/pvesm.pm @@ -183,7 +183,7 @@ __PACKAGE__->register_method ({ base => { des

[pve-devel] [PATCH V5 pve-container] Move option 'pve-lxc-snapshot-name' to PVE::JSONSchema.

Rename pve-lxc-snapshot-name to pve-snapshotname to have a unified name schema. --- src/PVE/API2/LXC.pm | 4 ++-- src/PVE/API2/LXC/Snapshot.pm | 12 ++-- src/PVE/LXC/Config.pm| 6 -- 3 files changed, 8 insertions(+), 14 deletions(-) diff --git a/src/PVE/API2/LXC.pm

[pve-devel] [PATCH V5 qemu-server] Move option 'pve-snapshot-name' to PVE::JSONSchema.

To avoid update problems rename pve-snapshot-name to pve-snapshotname. --- PVE/API2/Qemu.pm | 16 PVE/QemuServer.pm | 8 +--- 2 files changed, 9 insertions(+), 15 deletions(-) diff --git a/PVE/API2/Qemu.pm b/PVE/API2/Qemu.pm index 66ffc07..761120c 100644 --- a/PVE/API2/Qemu

[pve-devel] [PATCH V5 pve-common 1/2] merge pve-snapshot-name and pve-lxc-snapshot-name to pve-snapshotname.

This format was two time declared in PVE::LXC::Config and PVE::QemuServer. It is necessary to call the new option different to avoid upgrade problems. --- src/PVE/JSONSchema.pm | 17 + 1 file changed, 17 insertions(+) diff --git a/src/PVE/JSONSchema.pm b/src/PVE/JSONSchema.pm inde

[pve-devel] Adapt regex in pvesm import/export.

We allow uppercase characters in snapshot names. pvesm import and export must allow uppercase characters too. [PATCH V2] Use JSON schema instead of hardcoding. [PATCH V3 pve-storage] Correct typo. [PATCH V4] Make base snapshot more specific. [PATCH V5] Merge pve-lxc-snapshot-name and pve-snapsh

[pve-devel] [PATCH pve-manager] Clean up unnecessary code.

The jobid is already parsed by the file parser. --- PVE/API2/Replication.pm | 2 -- 1 file changed, 2 deletions(-) diff --git a/PVE/API2/Replication.pm b/PVE/API2/Replication.pm index 15499508..f396615d 100644 --- a/PVE/API2/Replication.pm +++ b/PVE/API2/Replication.pm @@ -60,8 +60,6 @@ sub run_s

Re: [pve-devel] [PATCH V5 qemu-server] Move option 'pve-snapshot-name' to PVE::JSONSchema.

> Wolfgang Bumiller hat am 21. September 2017 um 09:25 > geschrieben: > > > On Mon, Sep 18, 2017 at 11:52:48AM +0200, Wolfgang Link wrote: > > To avoid update problems rename pve-snapshot-name to pve-snapshotname. > > When not renaming this the new pve-common

[pve-devel] Adapt regex in pvesm import/export.

We allow uppercase characters in snapshot names. pvesm import and export must allow uppercase characters too. [PATCH V2] Use JSON schema instead of hardcoding. [PATCH V3 pve-storage] Correct typo. [PATCH V4] Make base snapshot more specific. [PATCH V5] Merge pve-lxc-snapshot-name and pve-snapsh

[pve-devel] [PATCH V6 storage] Use a json format instead of hard code regex.

--- PVE/CLI/pvesm.pm | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/PVE/CLI/pvesm.pm b/PVE/CLI/pvesm.pm index 9455595..57d10f4 100755 --- a/PVE/CLI/pvesm.pm +++ b/PVE/CLI/pvesm.pm @@ -183,7 +183,7 @@ __PACKAGE__->register_method ({ base => { des

[pve-devel] [PATCH V6 common 1/2] merge pve-snapshot-name and pve-lxc-snapshot-name to pve-snapshot-name.

This format was two time declared in PVE::LXC::Config and PVE::QemuServer. --- src/PVE/JSONSchema.pm | 17 + 1 file changed, 17 insertions(+) diff --git a/src/PVE/JSONSchema.pm b/src/PVE/JSONSchema.pm index 3295599..5b1d59e 100644 --- a/src/PVE/JSONSchema.pm +++ b/src/PVE/JSONSche

[pve-devel] [PATCH V6 common 2/2] Extend the JSON format schema with pve_base_snapshot.

A base snapshot can be a replication snapshot or a normal snapshot. Normal snapshots use the format configid. --- src/PVE/JSONSchema.pm | 13 + 1 file changed, 13 insertions(+) diff --git a/src/PVE/JSONSchema.pm b/src/PVE/JSONSchema.pm index 5b1d59e..fdf8119 100644 --- a/src/PVE/JSONS

[pve-devel] [PATCH V6 qemu-server] Move option 'pve-snapshot-name' to PVE::JSONSchema.

--- PVE/QemuServer.pm | 6 -- 1 file changed, 6 deletions(-) diff --git a/PVE/QemuServer.pm b/PVE/QemuServer.pm index 2b6fda9..bd4f6cd 100644 --- a/PVE/QemuServer.pm +++ b/PVE/QemuServer.pm @@ -62,12 +62,6 @@ PVE::JSONSchema::register_standard_option('pve-qm-stateuri', { optional => 1,

[pve-devel] [PATCH V6 container] Move option 'pve-lxc-snapshot-name' to PVE::JSONSchema.

Rename pve-lxc-snapshot-name to pve-snapshot-name to have a unified name schema. --- src/PVE/API2/LXC.pm | 4 ++-- src/PVE/API2/LXC/Snapshot.pm | 12 ++-- src/PVE/LXC/Config.pm| 6 -- 3 files changed, 8 insertions(+), 14 deletions(-) diff --git a/src/PVE/API2/LXC.pm

[pve-devel] [PATCH guest-common] Send email when a replication job fails.

A email notification will be send for each job when the job fails. This message will continued as long the job is failing. --- PVE/Replication.pm | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/PVE/Replication.pm b/PVE/Replication.pm index e53928e..0075b45 100644 --- a/PVE/

Re: [pve-devel] [PATCH guest-common] Send email when a replication job fails.

> Philip Abernethy hat am 3. Oktober 2017 um 10:20 > geschrieben: > > > On Tue, Oct 03, 2017 at 09:55:06AM +0200, Wolfgang Link wrote: > > A email notification will be send for each job when the job fails. > > This message will continued as long the job i

[pve-devel] [PATCH pve-guest-common] Add logfunc in storage_migration.

This will redirect export and import output to the correct log, instead of paring it into the syslog. --- PVE/Replication.pm | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/PVE/Replication.pm b/PVE/Replication.pm index e53928e..c25ed44 100644 --- a/PVE/Replication.pm +++

[pve-devel] [PATCH pve-storage] Add logfung in storage_migrate

The log function is used by storage replication to redirect the output in the correct log. --- PVE/Storage.pm | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/PVE/Storage.pm b/PVE/Storage.pm index b226082..94be04e 100755 --- a/PVE/Storage.pm +++ b/PVE/Storage.pm @@ -536,7 +

[pve-devel] Add logfunc to storage_migrate.

This redirect the output form pvesm export to the correct log instead of the syslog. ___ pve-devel mailing list pve-devel@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

[pve-devel] PVE Replica Email notification on failure.

Now you get a email if a replication job fail. The mail is only send the first time, when a job switched from ok state in error state. No more notification will come when a job with error state retry to sync. ___ pve-devel mailing list pve-devel@pve.pr

[pve-devel] [PATCH guest-common] Send email when a replication job fails.

A email notification will be send for each job when the job fails. This message will only send when an error occurs and the fail count is on 1. --- PVE/API2/Replication.pm | 18 -- PVE/CLI/pvesr.pm | 11 ++- bin/init.d/pvesr.service | 2 +- 3 files changed, 27 ins

[pve-devel] [PATCH guest-common] Remove noerr form replication.

We will handle this errors in the API and decide what to do. --- PVE/Replication.pm | 17 + 1 file changed, 5 insertions(+), 12 deletions(-) diff --git a/PVE/Replication.pm b/PVE/Replication.pm index e53928e..2b3df36 100644 --- a/PVE/Replication.pm +++ b/PVE/Replication.pm @@ -304

[pve-devel] PVE Replica email notification on failure.

[PATCH manager V2] Indentation cleanup. Small clenup like W.Bumiller has suggested. ___ pve-devel mailing list pve-devel@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

[pve-devel] [PATCH manager V2 2/2] Send an email when a replication job fails.

A email notification will be send for each job when the job fails. This message will only send when an error occurs and the fail count is on 1. --- PVE/API2/Replication.pm | 18 -- PVE/CLI/pvesr.pm | 11 ++- bin/init.d/pvesr.service | 2 +- 3 files changed, 27 ins

[pve-devel] [PATCH guest-common V2] Remove noerr form replication.

We will handle this errors in the API and decide what to do. --- PVE/Replication.pm | 17 + 1 file changed, 5 insertions(+), 12 deletions(-) diff --git a/PVE/Replication.pm b/PVE/Replication.pm index e53928e..2b3df36 100644 --- a/PVE/Replication.pm +++ b/PVE/Replication.pm @@ -304

[pve-devel] [PATCH manager V2 1/2] Indentation cleanup.

--- PVE/API2/Replication.pm | 14 +++--- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/PVE/API2/Replication.pm b/PVE/API2/Replication.pm index f396615d..38449892 100644 --- a/PVE/API2/Replication.pm +++ b/PVE/API2/Replication.pm @@ -77,15 +77,15 @@ sub run_jobs { my $i

[pve-devel] [PATCH manager V3 1/2] Indentation cleanup.

--- PVE/API2/Replication.pm | 14 +++--- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/PVE/API2/Replication.pm b/PVE/API2/Replication.pm index f396615d..38449892 100644 --- a/PVE/API2/Replication.pm +++ b/PVE/API2/Replication.pm @@ -77,15 +77,15 @@ sub run_jobs { my $i

[pve-devel] PVE Replica email notification on failure.

Now you get a email if a replication job fail. The mail is only send the first time, when a job switched from ok state in error state. No more notification will come when a job with error state retry to sync. [PATCH manager V2] Indentation cleanup. Small clenup like W.Bumiller has suggested. [PA

[pve-devel] [PATCH guest-common V3] Remove noerr form replication.

We will handle this errors in the API and decide what to do. --- PVE/Replication.pm | 29 + 1 file changed, 9 insertions(+), 20 deletions(-) diff --git a/PVE/Replication.pm b/PVE/Replication.pm index e53928e..0650726 100644 --- a/PVE/Replication.pm +++ b/PVE/Replicatio

[pve-devel] [PATCH manager V3 2/2] Send an email when a replication job fails.

A email notification will be send for each job when the job fails. This message will only send when an error occurs and the fail count is on 1. --- PVE/API2/Replication.pm | 18 -- PVE/CLI/pvesr.pm | 11 ++- bin/init.d/pvesr.service | 2 +- 3 files changed, 27 ins

[pve-devel] [PATCH docs] add VLAN explanation.

--- pve-network.adoc | 88 1 file changed, 88 insertions(+) diff --git a/pve-network.adoc b/pve-network.adoc index d221c32..c5d5b40 100644 --- a/pve-network.adoc +++ b/pve-network.adoc @@ -344,6 +344,94 @@ iface vmbr0 inet static

[pve-devel] [PATCH zsync] Fix: You can now use the pool as replication source.

In previous version you need a dataset as replication source. --- pve-zsync | 14 +++--- 1 file changed, 11 insertions(+), 3 deletions(-) diff --git a/pve-zsync b/pve-zsync index b3241ff..4020ba6 100644 --- a/pve-zsync +++ b/pve-zsync @@ -860,7 +860,8 @@ sub snapshot_destroy { if ($d

Re: [pve-devel] [PATCH docs] add VLAN explanation.

Hi Alexandre, I will wirte the doku like you suggest, but the configuration will also brake if you use it in combination with VLan awareness. I will make a node in the Doku to warn about this behavior. > Alexandre DERUMIER hat am 16. November 2017 um 17:38 > geschrieben: > > > Hi, > > Abou

[pve-devel] [PATCH V2 docs] add VLAN explanation.

--- pve-network.adoc | 115 +++ 1 file changed, 115 insertions(+) [Patch V2] Include suggestion from Thomas and Alexandre diff --git a/pve-network.adoc b/pve-network.adoc index d221c32..6605f5b 100644 --- a/pve-network.adoc +++ b/pve-network.ad

Re: [pve-devel] ha and zfs replication bug

Hi Alexandre, > Is it a bug or an expected behaviour ? At the moment this is expected behavior. When a HA migration is done the source is offline, so we can't migrate the actual state of this replica job. The replica try to sync a full image what will not work because the image exists on the out

[pve-devel] [PATCH manager] Show VLAN aware setting in NetworkView.

--- www/manager6/node/NetworkView.js | 10 ++ 1 file changed, 10 insertions(+) diff --git a/www/manager6/node/NetworkView.js b/www/manager6/node/NetworkView.js index 848aa7b5..b2fe6106 100644 --- a/www/manager6/node/NetworkView.js +++ b/www/manager6/node/NetworkView.js @@ -262,6 +262,16 @

[pve-devel] [PATCH V3 docs] add VLAN explanation.

--- pve-network.adoc | 117 +++ 1 file changed, 117 insertions(+) [PATCH V2] Include suggestion from Thomas and Alexandre. [PATCH V3] Fix Typo and add hint about trunk mode as Dominik Csapak suggest. diff --git a/pve-network.adoc b/pve-network

Re: [pve-devel] [PATCH manager] Show VLAN aware setting in NetworkView.

> > no gettext() translation for Yes/No? I suggest to use the same style we > use elsewhere ... > At the moment we nowhere translate the Boolean values. But you are right, we should do it. I will anyway send a new patch that refactors it for the web-tool-kit. __

[pve-devel] PVE Replica Email notification on failure.

Now you get a email if a replication job fail. The mail is only send the first time, when a job switched from 'ok' state in 'error' state. No more notification will come when a job with error state retry to sync. [PATCH manager V2] Indentation cleanup. Small clenup like W.Bumiller has suggested.

[pve-devel] [PATCH V4 manager 1/2] Indentation cleanup.

--- PVE/API2/Replication.pm | 14 +++--- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/PVE/API2/Replication.pm b/PVE/API2/Replication.pm index f396615d..38449892 100644 --- a/PVE/API2/Replication.pm +++ b/PVE/API2/Replication.pm @@ -77,15 +77,15 @@ sub run_jobs { my $i

[pve-devel] [PATCH V4 guset-common] Remove noerr form replication.

We will handle this errors in the API and decide what to do. --- PVE/Replication.pm | 95 +++--- 1 file changed, 41 insertions(+), 54 deletions(-) diff --git a/PVE/Replication.pm b/PVE/Replication.pm index c25ed44..9bc4e61 100644 --- a/PVE/Replicati

[pve-devel] [PATCH V4 manager 2/2] Send an email when a replication job fails.

A email notification will be send for each job when the job fails. This message will only send when an error occurs and the fail count is on 1. --- PVE/API2/Replication.pm | 18 -- PVE/CLI/pvesr.pm | 11 ++- bin/init.d/pvesr.service | 2 +- 3 files changed, 27 ins

Re: [pve-devel] [PATCH V4 manager 2/2] Send an email when a replication job fails.

> Thomas Lamprecht hat am 12. Dezember 2017 um 08:20 > geschrieben: > > > On 12/07/2017 12:07 PM, Wolfgang Link wrote: > > A email notification will be send for each job when the job fails. > > This message will only send when an error occurs and the fail count is

[pve-devel] [PATCH guest-common 4/6] Get snapshots when no state is available.

--- PVE/Replication.pm | 7 +++ 1 file changed, 7 insertions(+) diff --git a/PVE/Replication.pm b/PVE/Replication.pm index dac0994..e69b0c2 100644 --- a/PVE/Replication.pm +++ b/PVE/Replication.pm @@ -54,6 +54,13 @@ sub find_common_replication_snapshot { ($last_snapshots-

[pve-devel] [PATCH guest-common 2/6] Add config field 'source'.

This field is usfull to restore the replication state. Also correct this field if is not present or wrong. --- PVE/ReplicationConfig.pm | 6 ++ PVE/ReplicationState.pm | 5 + 2 files changed, 11 insertions(+) diff --git a/PVE/ReplicationConfig.pm b/PVE/ReplicationConfig.pm index 51cfe81.

[pve-devel] [PATCH guest-common 1/6] Cleanup fix for stateless jobs.

If a VM config was stolen or migrated through HA there is no state on that node. It must be possible to cleanup the remote-side without state. --- PVE/Replication.pm | 8 +++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/PVE/Replication.pm b/PVE/Replication.pm index c25ed44..ce

[pve-devel] [PATCH guest-common 3/6] Delete replication snapshots only if last_sync exists.

If last_sync is 0 then the VM config was stolen or the VM migrated by HA manager in case of a node failure. On this precondition the replication snapshot should not deleted. This snapshot will be used to restore the replication. --- PVE/Replication.pm | 9 ++--- 1 file changed, 6 insertions(+)

[pve-devel] [PATCH guest-common 0/6]pversr recover state.

This patch series allows to restore a replica without status. A HA migration ends in a lost state, even a manual configuration movement generates this behavior. This patch series also fixes the problem of cleanup without status. Wolfgang Link (6): Cleanup fix for stateless jobs. Add config

[pve-devel] [PATCH guest-common 5/6] Add function: swap source and target in replication config

--- PVE/ReplicationConfig.pm | 17 + 1 file changed, 17 insertions(+) diff --git a/PVE/ReplicationConfig.pm b/PVE/ReplicationConfig.pm index b6cd514..a696a81 100644 --- a/PVE/ReplicationConfig.pm +++ b/PVE/ReplicationConfig.pm @@ -258,6 +258,23 @@ sub delete_job { lock($code)

[pve-devel] [PATCH guest-common 6/6] Swap source and target in replication config, if VM was stolen.

--- PVE/ReplicationState.pm | 10 +- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/PVE/ReplicationState.pm b/PVE/ReplicationState.pm index 0851195..52688bb 100644 --- a/PVE/ReplicationState.pm +++ b/PVE/ReplicationState.pm @@ -255,7 +255,15 @@ sub job_status { my $ta

Re: [pve-devel] [PATCH guest-common 3/6] Delete replication snapshots only if last_sync exists.

> Thomas Lamprecht hat am 14. Dezember 2017 um 07:47 > geschrieben: > > > > + $last_snapshots->{$volid}->{$snap} = 1; > > } > > } > > } > > @@ -207,11 +210,11 @@ sub replicate { > > } > > > > my $ssh_info = PVE::Cluster::get_ssh_info($jobcfg->{target

[pve-devel] [PATCH V2 guest-common 1/6] Cleanup for stateless jobs.

If a VM configuration has been manually moved or migrated by HA, there is no status on this new node. In this case, the replication snapshots still exist on the remote side. It must be possible to remove a job without status, otherwise a new replication job on the same remote node will fail and the

[pve-devel] [PATCH V2 guest-common 2/6] Add config parameter 'source'.

This parameter is useful for restoring the replication status. It is also corrected if it is missing or wrong. --- PVE/ReplicationConfig.pm | 6 ++ PVE/ReplicationState.pm | 5 + 2 files changed, 11 insertions(+) diff --git a/PVE/ReplicationConfig.pm b/PVE/ReplicationConfig.pm index 51cf

[pve-devel] [PATCH V2 guest-common 5/6] Add function: swap source and target in replication config

--- PVE/ReplicationConfig.pm | 17 + 1 file changed, 17 insertions(+) diff --git a/PVE/ReplicationConfig.pm b/PVE/ReplicationConfig.pm index b6cd514..a696a81 100644 --- a/PVE/ReplicationConfig.pm +++ b/PVE/ReplicationConfig.pm @@ -258,6 +258,23 @@ sub delete_job { lock($code)

[pve-devel] [PATCH guest-common 0/6]pversr recover state.

Modify commit message. Add an error message if the status is not recoverable. Sort the snapshots to test newer ones first. 0006-Add error message in case the state is not recoverable.patch Correct typos in the page nodes as t.lamprecht suggest. Wolfga

[pve-devel] [PATCH V2 guest-common 4/6] Get snapshots when no state is available.

With this patch we can restore the state of a state less job. It may happen that there are more replication snapshots, because no job state is known can not delete any snapshot. Existing multiple replication-snapshot happens when a node fails in middel of a replication and then the VM is moved to a

[pve-devel] [PATCH V2 guest-common 3/6] Delete replication snapshots only if last_sync is not 0.

If last_sync is 0, the VM configuration has been stolen (either manually or by HA restoration). Under this condition, the replication snapshot should not be deleted. This snapshot is used to restore replication state. If the last_snap is greater than 0 and does not match the snap name it must be a

[pve-devel] [PATCH V2 guest-common 6/6] Swap source and target in replication config, if VM was stolen.

--- PVE/ReplicationState.pm | 12 ++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/PVE/ReplicationState.pm b/PVE/ReplicationState.pm index 0851195..60e009b 100644 --- a/PVE/ReplicationState.pm +++ b/PVE/ReplicationState.pm @@ -254,8 +254,16 @@ sub job_status {

[pve-devel] [PATCH i18n] add translation VLAN-enabled to de

--- proxmox-widget-toolkit-de.po | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/proxmox-widget-toolkit-de.po b/proxmox-widget-toolkit-de.po index dcf7618..cdf6c74 100644 --- a/proxmox-widget-toolkit-de.po +++ b/proxmox-widget-toolkit-de.po @@ -453,8 +453,9 @@ msgid "User nam

[pve-devel] [widget-toolkit 1/2] show VLAN aware setting in NetworkView.

--- node/NetworkView.js | 10 ++ 1 file changed, 10 insertions(+) diff --git a/node/NetworkView.js b/node/NetworkView.js index c2ea0dd..90be36f 100644 --- a/node/NetworkView.js +++ b/node/NetworkView.js @@ -295,6 +295,16 @@ Ext.define('Proxmox.node.NetworkView', {

[pve-devel] [widget-toolkit 2/2] change the hard coded text against the translated text

--- node/NetworkView.js | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/node/NetworkView.js b/node/NetworkView.js index 90be36f..b38a07e 100644 --- a/node/NetworkView.js +++ b/node/NetworkView.js @@ -280,9 +280,9 @@ Ext.define('Proxmox.node.NetworkView', {

[pve-devel] [PATCH_V2] Change zfs path when link clone are used

The new naming is coherent to Dir plugin. So if we make an licked clone the parent will be coded in the path of the storage. --- PVE/Storage.pm | 3 ++- PVE/Storage/ZFSPoolPlugin.pm | 58 2 files changed, 39 insertions(+), 22 deletions(

[pve-devel] [PATCH 2/2] Add Tests for ZFSPoolPlugin

--- test/Makefile |6 + test/run_test_zfspoolplugin.pl | 2490 2 files changed, 2496 insertions(+) create mode 100644 test/Makefile create mode 100755 test/run_test_zfspoolplugin.pl diff --git a/test/Makefile b/test/Makefile new file

[pve-devel] [PATCH] Skip invalid property's in storage parser

There is no need to remove the hole storage, if one property is not valid. Just ignore the property. --- PVE/Storage/Plugin.pm | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/PVE/Storage/Plugin.pm b/PVE/Storage/Plugin.pm index ccb3280..6f29838 100644 --- a/PVE/Storage/Plu

[pve-devel] [PATCH 2/3] add test PVE::Storage::path

--- test/run_test_zfspoolplugin.pl | 181 - 1 file changed, 180 insertions(+), 1 deletion(-) diff --git a/test/run_test_zfspoolplugin.pl b/test/run_test_zfspoolplugin.pl index fc68195..2512db9 100755 --- a/test/run_test_zfspoolplugin.pl +++ b/test/run_test_

[pve-devel] [PATCH 1/3] Select test form command

It is possible to select the test what should run. synopsis: run_test_zfspoolplugin.pl [ | ] --- test/run_test_zfspoolplugin.pl | 14 -- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/test/run_test_zfspoolplugin.pl b/test/run_test_zfspoolplugin.pl index 8e43b7b..fc681

[pve-devel] [PATCH 3/3] In path use parsed volname not the volid and add 'basevol'

--- PVE/Storage/ZFSPoolPlugin.pm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/PVE/Storage/ZFSPoolPlugin.pm b/PVE/Storage/ZFSPoolPlugin.pm index c381648..7e91625 100644 --- a/PVE/Storage/ZFSPoolPlugin.pm +++ b/PVE/Storage/ZFSPoolPlugin.pm @@ -148,7 +148,7 @@ sub path { m

[pve-devel] [PATCH] Fix error handling if ram hot-plug fail.

There is no need to cancel the program if the ram can't remove. The user will see that it is pending. --- PVE/API2/Qemu.pm | 9 - 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/PVE/API2/Qemu.pm b/PVE/API2/Qemu.pm index 0d33f6c..96829c8 100644 --- a/PVE/API2/Qemu.pm +++ b/PVE/

[pve-devel] [PATCH 2/2] Remove experimental flag

clone ct is now full implemented. There is no need fore this anymore. --- src/PVE/API2/LXC.pm | 6 -- 1 file changed, 6 deletions(-) diff --git a/src/PVE/API2/LXC.pm b/src/PVE/API2/LXC.pm index e64ee17..68f0a59 100644 --- a/src/PVE/API2/LXC.pm +++ b/src/PVE/API2/LXC.pm @@ -1035,12 +1035,6 @@

[pve-devel] [PATCH 1/2] Add the functionality of full clone

--- src/PVE/API2/LXC.pm | 21 ++--- src/PVE/LXC.pm | 49 + 2 files changed, 59 insertions(+), 11 deletions(-) diff --git a/src/PVE/API2/LXC.pm b/src/PVE/API2/LXC.pm index 90cdba6..e64ee17 100644 --- a/src/PVE/API2/LXC.pm +++ b/s

[pve-devel] [PATCH] Add empty field text.

This is useful if user not really know what is the scheme or which value comes in. --- www/manager6/storage/DirEdit.js | 1 + www/manager6/storage/GlusterFsEdit.js | 1 + www/manager6/storage/IScsiEdit.js | 1 + www/manager6/storage/NFSEdit.js | 1 + www/manager6/storage/RBDEdit.j

[pve-devel] [PATCH] add Windows 10 and 2012r2 to OS selection

So user now we support also Win 10 and R2. --- www/manager6/Utils.js | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/www/manager6/Utils.js b/www/manager6/Utils.js index 3b7848a..8c91a85 100644 --- a/www/manager6/Utils.js +++ b/www/manager6/Utils.js @@ -88,7 +88,7 @@ Ext.define(

Re: [pve-devel] [PATCH] add Windows 10 and 2012r2 to OS selection

Yes 2012R2 but to keep it shorter R2 > Dietmar Maurer hat am 19. April 2016 um 17:01 > geschrieben: > > > > > > On April 19, 2016 at 2:38 PM Wolfgang Link wrote: > > > > > > So user now we support also Win 10 and R2. > > --- > >

[pve-devel] [[PATCH pve-container] 2/4] Add move_volume.

Now it is possible to move the volume to an other storage. This works only when the CT is off, to keep the volume consistent. --- src/PVE/API2/LXC.pm | 116 src/PVE/CLI/pct.pm | 1 + 2 files changed, 117 insertions(+) diff --git a/src/PVE/AP

[pve-devel] [[PATCH_2 pve-container]] Add the functionality of full clone

--- src/PVE/API2/LXC.pm | 21 +-- src/PVE/LXC.pm | 58 + 2 files changed, 68 insertions(+), 11 deletions(-) diff --git a/src/PVE/API2/LXC.pm b/src/PVE/API2/LXC.pm index 90cdba6..537ab69 100644 --- a/src/PVE/API2/LXC.pm +++ b

[pve-devel] [[PATCH pve-container] 3/4] clone disk is complete, so we can remove the experimental flag

--- src/PVE/API2/LXC.pm | 6 -- 1 file changed, 6 deletions(-) diff --git a/src/PVE/API2/LXC.pm b/src/PVE/API2/LXC.pm index 976e25d..5c0ae99 100644 --- a/src/PVE/API2/LXC.pm +++ b/src/PVE/API2/LXC.pm @@ -1035,12 +1035,6 @@ __PACKAGE__->register_method({ "you clone a normal

[pve-devel] clone volume

With this new function it is possible to copy a rootfs or a mount-point, if the mp is a volume. Also we use this function to create full clones of CT and now we can move volumes to an other volume too. ___ pve-devel mailing list pve-devel@pve.proxmox.co

[pve-devel] [[PATCH pve-container] 4/4] Prevent that CT run at clone time.

If we make a linked clone the CT must be a template, so it is not allowed to run. If we make a full clone, it is safer to have the CT offline. --- src/PVE/API2/LXC.pm | 8 ++-- 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/src/PVE/API2/LXC.pm b/src/PVE/API2/LXC.pm index 5c0ae9

<    1   2   3   4   5   6   7   8   9   10   >