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 required:
___
pve-devel mailing list
pve-devel@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
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 f
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 they
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 copy/paste
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
---
www/manager
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 +++
www/manager6/dc/ClusterEdit.js |
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 +
www/manager6/dc/Cluster.js
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 -
RADOS.xs | 26 +++
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.
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 stil
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
---
www/manager6/dc/Cluster.
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 someth
$ 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, includi
$ 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
---
debian/scripts/import-upstream-tag
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
pat
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 e
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 Antreich
> ---
> PVE/RADOS.pm
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
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 some
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 w
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" log
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'
'r
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 upst
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
pve
25 matches
Mail list logo
