[pve-devel] applied: translation updates

2017-06-29 Thread Dietmar Maurer
applied, including the fix "Max. riavvii" ___ pve-devel mailing list pve-devel@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

[pve-devel] applied: [PATCH novnc] Replace 'migrating' info strings with more generic 'connecting' messages

2017-06-29 Thread Dietmar Maurer
applied ___ pve-devel mailing list pve-devel@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

Re: [pve-devel] [PATCH manager 1/4] improve italian translation

2017-06-29 Thread Gandalf Corvotempesta
Il 29 giu 2017 4:37 PM, "Thomas Lamprecht" ha scritto: #: ../www/manager6/ha/ResourceEdit.js:82 ../www/manager6/ha/Resources. js:154 msgid "Max. Restart" -msgstr "Massimo ravvivamenti" +msgstr "Max. ravvii" This should be "Max. riavvii" (rIavvii not rAvvii, the "i" letter is missing) I'm on

Re: [pve-devel] [PATCH v7 pve-storage 02/10] Basic FreeNAS API interaction code

2017-06-29 Thread Michael Rasmussen
On Wed, 21 Jun 2017 15:58:13 +0200 Fabian Grünbichler wrote: > > +die $res->code."\n" unless $res->is_success; > > this deviates from v5 - now you die with the HTTP error code, and not > with the full status message (except for in freenas_create_target_group > and freenas_create_target) -

Re: [pve-devel] [PATCH container 1/2] Add disk operations to vmstatus

2017-06-29 Thread Dietmar Maurer
> So, if there is no reliable way to fetch these data for containers, what > would be the proper way to reflect that in the generic VM stats? Setting > these values to "undef" for containers and not rendering a graph seems > to be the only sensible way, I guess. Or is there a better way to handle >

[pve-devel] [PATCH manager 3/4] update translations - it

2017-06-29 Thread Thomas Lamprecht
Signed-off-by: Thomas Lamprecht --- po/it.po | 608 ++- 1 file changed, 367 insertions(+), 241 deletions(-) diff --git a/po/it.po b/po/it.po index 72c5cb5f..5ac1d29c 100644 --- a/po/it.po +++ b/po/it.po @@ -7,7 +7,7 @@ msgid "" msgstr

[pve-devel] [PATCH manager 2/4] replication: reuse fitting translations

2017-06-29 Thread Thomas Lamprecht
while it does not makes sense do over-reuse translations for the sake of translating less, imo, here we can safely reuse already existing ones and pull out the unit 'MB/s' from the gettext. Signed-off-by: Thomas Lamprecht --- www/manager6/grid/Replication.js | 4 ++-- 1 file changed, 2 insertion

[pve-devel] translation updates

2017-06-29 Thread Thomas Lamprecht
Note that I splitted the italian translation updates for a good reason. The first batch is a fixup from my last update which was provided by Marco Menardi (thanks again!) and the second batch are new translations which weren't yet reviewed by another native speaker - thus I wanted to split revied a

[pve-devel] [PATCH manager 4/4] update translations - de

2017-06-29 Thread Thomas Lamprecht
Signed-off-by: Thomas Lamprecht --- po/de.po | 588 +++ 1 file changed, 363 insertions(+), 225 deletions(-) diff --git a/po/de.po b/po/de.po index a27008d9..8b54db29 100644 --- a/po/de.po +++ b/po/de.po @@ -7,7 +7,7 @@ msgid "" msgstr

[pve-devel] [PATCH manager 1/4] improve italian translation

2017-06-29 Thread Thomas Lamprecht
Thanks to Marco Menardi we get some better translations for some entries. Signed-off-by: Thomas Lamprecht --- po/it.po | 40 1 file changed, 20 insertions(+), 20 deletions(-) diff --git a/po/it.po b/po/it.po index f0a33f24..72c5cb5f 100644 --- a/po/it.po

[pve-devel] [PATCH novnc] Replace 'migrating' info strings with more generic 'connecting' messages

2017-06-29 Thread Emmanuel Kasper
This fixes the problem that a restarted container was seen as migrating in the UI. Background: The check for migration happens on a 'disconnected' event, but can very well come for other reasons, like entering reboot on the LXC console. Since we have no idea about what have caused the disconnectio

[pve-devel] applied: [PATCH common v3 0/1] Add run_fork_with_timeout utility

2017-06-29 Thread Wolfgang Bumiller
applied both patches On Thu, Jun 29, 2017 at 02:48:11PM +0200, Emmanuel Kasper wrote: > changes since v2: > * in v3-0001-Add-run_fork_with_timeout-utility.patch >* set writer on both pipes just after the beginning of the child process >* use $pipe->flush() after writing to the pipe to mak

[pve-devel] [PATCH common v3 0/1] Add run_fork_with_timeout utility

2017-06-29 Thread Emmanuel Kasper
changes since v2: * in v3-0001-Add-run_fork_with_timeout-utility.patch * set writer on both pipes just after the beginning of the child process * use $pipe->flush() after writing to the pipe to make our intent more evident ( perl _exit will close the file handles but will not flush IO bu

[pve-devel] [PATCH common v3 1/1] Add run_fork_with_timeout utility

2017-06-29 Thread Emmanuel Kasper
This runs subroutine in a forked process and kills it after a timeout --- src/PVE/Tools.pm | 66 1 file changed, 66 insertions(+) diff --git a/src/PVE/Tools.pm b/src/PVE/Tools.pm index da7da5d..fce2b1c 100644 --- a/src/PVE/Tools.pm +++ b/sr

[pve-devel] [PATCH v3] Fixes: #1415 do not block pvestatd when nfsd is stopped on the server side

2017-06-29 Thread Emmanuel Kasper
Wrap the -d test with run_or_get_killed sub this test can make pvestatd hang on I/O wait when a nfsd process is stopped This might help with other file based storages, for instance directory storages on unplugged USB devices. --- PVE/Storage/Plugin.pm | 9 +++-- 1 file changed, 7 insertions(+

[pve-devel] [PATCH manager] pvesr: allow schedule now from CLI

2017-06-29 Thread Thomas Lamprecht
Signed-off-by: Thomas Lamprecht --- PVE/CLI/pvesr.pm | 1 + 1 file changed, 1 insertion(+) diff --git a/PVE/CLI/pvesr.pm b/PVE/CLI/pvesr.pm index 16989308..7da94404 100644 --- a/PVE/CLI/pvesr.pm +++ b/PVE/CLI/pvesr.pm @@ -375,6 +375,7 @@ my $print_job_status = sub { our $cmddef = { statu

[pve-devel] applied: [PATCH manager] pvesr status: handle disabled jobs

2017-06-29 Thread Dietmar Maurer
applied ___ pve-devel mailing list pve-devel@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

[pve-devel] applied: [PATCH manager v2] replication; merge status and status text and add to dc mode

2017-06-29 Thread Dietmar Maurer
applied ___ pve-devel mailing list pve-devel@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

[pve-devel] [PATCH manager] pvesr status: handle disabled jobs

2017-06-29 Thread Thomas Lamprecht
As the nodes replication status call also returns disabled jobs now, we need to handle them here too. Signed-off-by: Thomas Lamprecht --- PVE/CLI/pvesr.pm | 7 --- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/PVE/CLI/pvesr.pm b/PVE/CLI/pvesr.pm index f5d4db5b..16989308 10064

Re: [pve-devel] [PATCH container 1/2] Add disk operations to vmstatus

2017-06-29 Thread Tobias Böhm
> On Wed, Jun 28, 2017 at 10:01:59AM +0200, Wolfgang Bumiller wrote: > > On Mon, Jun 19, 2017 at 12:10:10PM +0200, Tobias Böhm wrote: > > > Currently, only read/write bytes are extracted from cgroups stats. > > > > s/bytes/operations/ > > > > > In order to provide IO operation stats these counter

[pve-devel] [PATCH manager v2] replication; merge status and status text and add to dc mode

2017-06-29 Thread Thomas Lamprecht
It was a bit strange to have two separate status columns, which do effectively the same thing. So merge them together to save a bit space and have less columns. We do not need to translate 'Status Text' as a nice side effect. Signed-off-by: Thomas Lamprecht --- changes since v1: * we cannot sho

[pve-devel] applied: [PATCH manager 2/2] replication: show disabled jobs and allow enabling/disabling

2017-06-29 Thread Dietmar Maurer
applied ___ pve-devel mailing list pve-devel@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

[pve-devel] [PATCH manager] replication; merge status and status text and add to dc mode

2017-06-29 Thread Thomas Lamprecht
It was a bit strange to have two separate status columns, which do effectively the same thing. So merge them together to save a bit space and have less columns. Show this field also in the datacenter replication panel, as else we have no feed back about jobs there. This was especially confusing wh

[pve-devel] applied: [PATCH guest-common 1/2] replication job_status: add get_disabled parameter

2017-06-29 Thread Dietmar Maurer
applied ___ pve-devel mailing list pve-devel@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

[pve-devel] [PATCH manager 2/2] replication: show disabled jobs and allow enabling/disabling

2017-06-29 Thread Thomas Lamprecht
Signed-off-by: Thomas Lamprecht --- PVE/API2/Replication.pm | 2 +- www/manager6/grid/Replication.js | 23 ++- 2 files changed, 23 insertions(+), 2 deletions(-) diff --git a/PVE/API2/Replication.pm b/PVE/API2/Replication.pm index dca93d8c..1f792d39 100644 --- a/PVE/

[pve-devel] [PATCH guest-common 1/2] replication job_status: add get_disabled parameter

2017-06-29 Thread Thomas Lamprecht
allows the API/frontend to get the disabled jobs easier Signed-off-by: Thomas Lamprecht --- PVE/ReplicationState.pm | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/PVE/ReplicationState.pm b/PVE/ReplicationState.pm index b817f08..88a2daf 100644 --- a/PVE/ReplicationState.pm