[pve-devel] ZFS encryption

2018-04-03 Thread Andreas Steinel
Hi everyone, are you (Proxmox staff) actively testing encrypted ZFS or are you waiting for the upstream "activation"? -- With kind regards / Mit freundlichen Grüßen Andreas Steinel M.Sc. Visual Computing M.Sc. Informatik ___ pve-devel mailing list

Re: [pve-devel] [RFC kernel 0/2] pve-kernel helper scripts for patch-queue management

2018-04-03 Thread Thomas Lamprecht
Am 04/03/2018 um 01:30 PM schrieb Fabian Grünbichler: this patch series introduces helper scripts for - importing the exported patchqueue into a patchqueue branch inside the submodule - exporting the (updated) patchqueue from the patchqueue branch inside the submodule - importing a new

Re: [pve-devel] [RFC kernel 1/2] debian/scripts: add patchqueue scripts

2018-04-03 Thread Thomas Lamprecht
Am 04/03/2018 um 01:30 PM schrieb Fabian Grünbichler: $ import-patchqueue repo dir [branch] imports a (previously exported) patchqueue from 'dir' into a new branch (default 'pq') in 'repo' $ export-patchqueue repo dir ref exports a patchqueue from 'ref' to current HEAD of 'repo' into 'dir'

[pve-devel] [RFC manager 0/1] introduce pvesrd, replacing systemd pvesr.{timer, service}

2018-04-03 Thread Thomas Lamprecht
This is a POC of replacing the systemd timer which ran pvesr.service (an exec of `pvesr run`) once a minute. The timer was not used, somehow, to trigger pvesr on the correct time, as one could think, but rather as a daemon replacement. our replication logic handles the "when must which job run"

[pve-devel] [RFC manager 1/1] WIP: replace systemd timer with pvesrd daemon

2018-04-03 Thread Thomas Lamprecht
The whole thing is already prepared for this, the systemd timer was just a fixed periodic timer with a frequency of one minute. And we just introduced it as the assumption was made that less memory usage would be generated with this approach, AFAIK. But logging 4+ lines just about that the timer

Re: [pve-devel] [RFC manager 4/5] ui: add cluster join window POC

2018-04-03 Thread Dominik Csapak
On 04/03/2018 02:43 PM, Thomas Lamprecht wrote: Am 04/03/2018 um 01:52 PM schrieb Dominik Csapak: On 04/03/2018 10:49 AM, Thomas Lamprecht wrote: Am 04/03/2018 um 10:16 AM schrieb Dominik Csapak: even with the autoflush patch, i could not get this to work properly: * i clicked join * for

Re: [pve-devel] [RFC manager 4/5] ui: add cluster join window POC

2018-04-03 Thread Thomas Lamprecht
Am 04/03/2018 um 01:52 PM schrieb Dominik Csapak: On 04/03/2018 10:49 AM, Thomas Lamprecht wrote: Am 04/03/2018 um 10:16 AM schrieb Dominik Csapak: even with the autoflush patch, i could not get this to work properly: * i clicked join * for some seconds nothing happened * some things appeared

Re: [pve-devel] [PATCH librados2-perl] Split method pve_rados_connect

2018-04-03 Thread Dietmar Maurer
comments inline > On March 30, 2018 at 12:25 PM Alwin Antreich wrote: > > > To be able to connect through librados2 without a config file, the > method pve_rados_connect is split up into pve_rados_connect and > pve_rados_conf_read_file. > > Signed-off-by: Alwin

Re: [pve-devel] [RFC manager 4/5] ui: add cluster join window POC

2018-04-03 Thread Dominik Csapak
On 04/03/2018 10:49 AM, Thomas Lamprecht wrote: Am 04/03/2018 um 10:16 AM schrieb Dominik Csapak: even with the autoflush patch, i could not get this to work properly: * i clicked join * for some seconds nothing happened * some things appeared (the other node, etc) * all api calls returned an

[pve-devel] [RFC kernel 0/2] pve-kernel helper scripts for patch-queue management

2018-04-03 Thread Fabian Grünbichler
this patch series introduces helper scripts for - importing the exported patchqueue into a patchqueue branch inside the submodule - exporting the (updated) patchqueue from the patchqueue branch inside the submodule - importing a new upstream tag into the submodule, optionally rebasing the

[pve-devel] [RFC kernel 2/2] debian/scripts: add import-upstream-tag

2018-04-03 Thread Fabian Grünbichler
$ import-upstream-tag path/to/kernel/submodule path/to/kernel/patches tag [rebase] fetches 'tag' from default remote, optionally imports, rebases and exports patchqueue, checks out 'tag' and commits the resulting changes. Signed-off-by: Fabian Grünbichler ---

[pve-devel] [RFC kernel 1/2] debian/scripts: add patchqueue scripts

2018-04-03 Thread Fabian Grünbichler
$ import-patchqueue repo dir [branch] imports a (previously exported) patchqueue from 'dir' into a new branch (default 'pq') in 'repo' $ export-patchqueue repo dir ref exports a patchqueue from 'ref' to current HEAD of 'repo' into 'dir' 'repo' can be any checked out non-bare repository,

Re: [pve-devel] [RFC manager 4/5] ui: add cluster join window POC

2018-04-03 Thread Thomas Lamprecht
Am 04/03/2018 um 10:16 AM schrieb Dominik Csapak: even with the autoflush patch, i could not get this to work properly: * i clicked join * for some seconds nothing happened * some things appeared (the other node, etc) * all api calls returned an error with no further message am i missing

Re: [pve-devel] [PATCH manager 3/5] dc/Cluster: allow to get join information

2018-04-03 Thread Thomas Lamprecht
Am 04/03/2018 um 10:16 AM schrieb Dominik Csapak: i guess it would be good to make this window non-resizable because the fields do not really resize well OK. otherwise looks good On 03/27/2018 03:45 PM, Thomas Lamprecht wrote: Signed-off-by: Thomas Lamprecht ---  

Re: [pve-devel] [PATCH manager 2/5] dc/Cluster: allow cluster create over WebUI

2018-04-03 Thread Thomas Lamprecht
Am 04/03/2018 um 10:16 AM schrieb Dominik Csapak: The window always allows me to click on create, it would be better to only allow this if all necessary fields are filled otherwise: great :) Ah yes, just forgot to add the respective config to the cluster name component, the API catches it

Re: [pve-devel] [PATCH manager 1/5] dc: add simple cluster panel

2018-04-03 Thread Thomas Lamprecht
Am 04/03/2018 um 10:16 AM schrieb Dominik Csapak: comments inline On 03/27/2018 03:45 PM, Thomas Lamprecht wrote: Show configured cluster nodes with their addresses, votes, IDs. Also show cluster name, config_version, and node count. Prepares for creating and joining a cluster over the WebUI.

Re: [pve-devel] [PATCH librados2-perl] Split method pve_rados_connect

2018-04-03 Thread Thomas Lamprecht
Am 03/30/2018 um 12:25 PM schrieb Alwin Antreich: To be able to connect through librados2 without a config file, the method pve_rados_connect is split up into pve_rados_connect and pve_rados_conf_read_file. Signed-off-by: Alwin Antreich --- PVE/RADOS.pm | 9

Re: [pve-devel] [PATCH manager 3/5] dc/Cluster: allow to get join information

2018-04-03 Thread Dominik Csapak
i guess it would be good to make this window non-resizable because the fields do not really resize well otherwise looks good On 03/27/2018 03:45 PM, Thomas Lamprecht wrote: Signed-off-by: Thomas Lamprecht --- www/manager6/dc/Cluster.js | 20 +++

Re: [pve-devel] [PATCH manager 2/5] dc/Cluster: allow cluster create over WebUI

2018-04-03 Thread Dominik Csapak
The window always allows me to click on create, it would be better to only allow this if all necessary fields are filled otherwise: great :) On 03/27/2018 03:45 PM, Thomas Lamprecht wrote: Signed-off-by: Thomas Lamprecht --- www/manager6/Makefile | 1 +

Re: [pve-devel] [RFC manager 4/5] ui: add cluster join window POC

2018-04-03 Thread Dominik Csapak
even with the autoflush patch, i could not get this to work properly: * i clicked join * for some seconds nothing happened * some things appeared (the other node, etc) * all api calls returned an error with no further message am i missing something still? the rest is really good (the

Re: [pve-devel] [PATCH manager 1/5] dc: add simple cluster panel

2018-04-03 Thread Dominik Csapak
comments inline On 03/27/2018 03:45 PM, Thomas Lamprecht wrote: Show configured cluster nodes with their addresses, votes, IDs. Also show cluster name, config_version, and node count. Prepares for creating and joining a cluster over the WebUI. Signed-off-by: Thomas Lamprecht

Re: [pve-devel] [PATCH manager 0/5] cluster create/join UI

2018-04-03 Thread Dominik Csapak
Looks great, a few things are still rough, please refer to my mails to the relevant patches On 03/27/2018 03:45 PM, Thomas Lamprecht wrote: First 3 patches (1/5, 2/5, 3/5) should be quite polished and could be, if deemed OK, already applied. The last two, 4/5 and 5/5, are more a WIP/POC but

[pve-devel] applied: [PATCH v2] add APT hook to prevent proxmox-ve removal

2018-04-03 Thread Thomas Lamprecht
applied, thanks! Am 04/03/2018 um 09:18 AM schrieb Fabian Grünbichler: since this happens quite regularly when users accidentally install conflicting packages. sample output: $ apt remove pve-qemu-kvm Reading package lists... Done Building dependency tree Reading state information... Done The

[pve-devel] applied: [PATCH cluster] pvecm join: also default to resolved IP with use_ssh param

2018-04-03 Thread Fabian Grünbichler
___ pve-devel mailing list pve-devel@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

[pve-devel] [PATCH v2] add APT hook to prevent proxmox-ve removal

2018-04-03 Thread Fabian Grünbichler
since this happens quite regularly when users accidentally install conflicting packages. sample output: $ apt remove pve-qemu-kvm Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer

Re: [pve-devel] [PATCH cluster] pvecm join: also default to resolved IP with use_ssh param

2018-04-03 Thread Thomas Lamprecht
Any objections? Else I'd apply this later today myself... It syncs the behaviour from SSH join with API join and create, so it isn't new untested code. Am 03/29/2018 um 11:06 AM schrieb Thomas Lamprecht: We already switched to this behaviour in pvecm create and pvecm join (with API) but did not

Re: [pve-devel] [PATCH cluster] API/Cluster: autoflush STDOUT for join and create

2018-04-03 Thread Thomas Lamprecht
Any comments? Am 03/27/2018 um 08:08 AM schrieb Thomas Lamprecht: We're in a forked worker here, so STDOUT isn't connected to a (pseudo)TTY directly, so perl flushes only when it's intewrnal buffer is full. Ensure each line gets flushed out to the API client in use to give immediate feedback