[pve-devel] [PATCH v2 2/3] remove unnecessary eslint.js

Signed-off-by: Dominik Csapak --- src/eslint.js | 138871 --- 1 file changed, 138871 deletions(-) delete mode 100755 src/eslint.js diff --git a/src/eslint.js b/src/eslint.js deleted file mode 100755 index 6115dea..000 -- 2.30.2 ___

[pve-devel] [PATCH v2 3/3] use worker_threads for linting

instead linting all files in the main thread, use worker threads for that (4 by default) and add the '-t' switch to able to control that a basic benchmark of eslint of pve-manager showed some performance gains: Benchmark #1: Current Time (mean ± σ): 6.468 s ± 0.116 s[User: 9.803 s, Sy

[pve-devel] [PATCH v2 1/3] ship proper nodejs module 'pve-eslint'

instead of concatenating the eslint module into our app.js, ship a 'pve-eslint' module that exports the built eslint module to do this, we have to leave the module type on 'umd' instead of changing to 'var' so that nodejs can properly import it. Signed-off-by: Dominik Csapak --- Makefile

[pve-devel] [PATCH v2 0/3] make linting threaded

NOTE: this series will not build until a 'make buildupstream' is executed (and 'src/lib/eslint.js' should be committed as well). I did not send it because it would be too big. this series convert the package into a proper nodejs module 'pve-eslint', and adds threading to the linting binary change

[pve-devel] [PATCH pve-docs] fix typo: operation system -> operating system

Signed-off-by: Dylan Whyte --- local-lvm.adoc | 2 +- qm.adoc| 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/local-lvm.adoc b/local-lvm.adoc index 2489b9d..6abdee8 100644 --- a/local-lvm.adoc +++ b/local-lvm.adoc @@ -33,7 +33,7 @@ VG: swap pve -wi-ao 896.00m

[pve-devel] [PATCH manager] vzdump: allow backups on btrfs

see forum post [0] [0]: https://forum.proxmox.com/threads/cant-use-storage-type-btrfs-for-backup-500-help.92918/ Signed-off-by: Oguz Bektas --- PVE/VZDump.pm | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/PVE/VZDump.pm b/PVE/VZDump.pm index 46cb9e6d..39b5e46d 100644 --- a

Re: [pve-devel] [PATCH manager] vzdump: allow backups on btrfs

On 19.07.21 13:58, Oguz Bektas wrote: > see forum post [0] > > [0]: > https://forum.proxmox.com/threads/cant-use-storage-type-btrfs-for-backup-500-help.92918/ > > Signed-off-by: Oguz Bektas > --- > PVE/VZDump.pm | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/PVE/VZD

[pve-devel] [PATCH v2 manager] vzdump: allow backups from plugins

remove type check for the specific plugins, instead we can deduce it from the supported content type in config (this can only be set on storages that declare to support backups). should also work with external storage plugins. Signed-off-by: Oguz Bektas --- v1->v2: * remove type check instead of

[pve-devel] [PATCH v1 storage 1/9] storage: expose find_free_diskname

We do not expose the parameter 'add_fmt_suffix' used by the internal implemantion of 'find_free_diskname'. This is something only the plugins themselves know but cannot be determined easily and reliably from an outside caller. This is why the new 'wants_fmt_suffix' method has been introduced. For

[pve-devel] [PATCH v1 container 9/9] api: move-volume: cleanup very long lines

Signed-off-by: Aaron Lauterer --- src/PVE/API2/LXC.pm | 33 +++-- 1 file changed, 27 insertions(+), 6 deletions(-) diff --git a/src/PVE/API2/LXC.pm b/src/PVE/API2/LXC.pm index 0af22c1..fecd4ca 100644 --- a/src/PVE/API2/LXC.pm +++ b/src/PVE/API2/LXC.pm @@ -1820,13 +18

[pve-devel] [PATCH v1 container 7/9] cli: pct: change move_volume to move-volume

also add alias to keep move_volume working Signed-off-by: Aaron Lauterer --- src/PVE/CLI/pct.pm | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/PVE/CLI/pct.pm b/src/PVE/CLI/pct.pm index 8c40bbe..7ac5a55 100755 --- a/src/PVE/CLI/pct.pm +++ b/src/PVE/CLI/pct.pm @@ -849,7

[pve-devel] [PATCH v1 qemu-server 4/9] Drive: add valid_drive_names_with_unused

Signed-off-by: Aaron Lauterer --- PVE/QemuServer/Drive.pm | 4 1 file changed, 4 insertions(+) diff --git a/PVE/QemuServer/Drive.pm b/PVE/QemuServer/Drive.pm index 5110190..09f37c1 100644 --- a/PVE/QemuServer/Drive.pm +++ b/PVE/QemuServer/Drive.pm @@ -393,6 +393,10 @@ sub valid_drive_names

[pve-devel] [PATCH v1 qemu-server 3/9] cli: qm: change move_disk to move-disk

also add alias to keep move_disk working. Signed-off-by: Aaron Lauterer --- PVE/CLI/qm.pm | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/PVE/CLI/qm.pm b/PVE/CLI/qm.pm index 8307dc1..ef99b6d 100755 --- a/PVE/CLI/qm.pm +++ b/PVE/CLI/qm.pm @@ -910,7 +910,8 @@ our $cmddef = {

[pve-devel] [PATCH v1 qemu-server 6/9] api: move-disk: cleanup very long lines

Signed-off-by: Aaron Lauterer --- PVE/API2/Qemu.pm | 25 - 1 file changed, 20 insertions(+), 5 deletions(-) diff --git a/PVE/API2/Qemu.pm b/PVE/API2/Qemu.pm index ed1179b..0529c1b 100644 --- a/PVE/API2/Qemu.pm +++ b/PVE/API2/Qemu.pm @@ -3301,13 +3301,15 @@ __PACKAGE__->re

[pve-devel] [PATCH v1 storage qemu-server container 0/9] move disk or volume to other guests

This is the continuation of 'disk-reassign' but instead of a separate API endpoint we now follow the approach to make it part of the 'move-disk' and 'move-volume' endpoints for VMs and containers. The main idea is to make it easy to move a disk/volume to another guest. Currently this is a manual a

[pve-devel] [PATCH v1 storage 2/9] add disk rename feature

Functionality has been added for the following storage types: * directory ones, based on the default implementation: * directory * NFS * CIFS * gluster * ZFS * (thin) LVM * Ceph A new feature `rename` has been introduced to mark which storage plugin supports the feature. Version

[pve-devel] [PATCH v1 qemu-server 5/9] api: move-disk: add move to other VM

The goal of this is to expand the move-disk API endpoint to make it possible to move a disk to another VM. Previously this was only possible with manual intervertion either by renaming the VM disk or by manually adding the disks volid to the config of the other VM. Signed-off-by: Aaron Lauterer -

[pve-devel] [PATCH v1 container 8/9] api: move-volume: add move to another container

The goal of this is to expand the move-volume API endpoint to make it possible to move a container volume / mountpoint to another container. Currently it works for regular mountpoints though it would be nice to be able to do it for unused mounpoints as well. Signed-off-by: Aaron Lauterer --- Thi

[pve-devel] applied: [PATCH pve-docs] fix typo: operation system -> operating system

On 19.07.21 13:41, Dylan Whyte wrote: > Signed-off-by: Dylan Whyte > --- > local-lvm.adoc | 2 +- > qm.adoc| 2 +- > 2 files changed, 2 insertions(+), 2 deletions(-) > > applied, thanks! ___ pve-devel mailing list pve-devel@lists.proxmox.com

[pve-devel] applied: [PATCH proxmox-widget-toolkit] apt: match "Debian Backports" origin

On 15.07.21 10:08, Fabian Grünbichler wrote: > some users might have that enabled, and we know it is from Debian and > not '?' > > Signed-off-by: Fabian Grünbichler > --- > src/node/APTRepositories.js | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > applied, thanks! __

[pve-devel] applied: [PATCH widget-toolkit] api-viewer: drop extra slash in api path

On 15.07.21 13:10, Dominik Csapak wrote: > 'endpoint' already begins with a slash, so drop it after /api2/json > > Signed-off-by: Dominik Csapak > --- > src/api-viewer/APIViewer.js | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > applied, thanks! __