Re: [pve-devel] [PATCH] PVE/API2/LXC.pm ssh-public-keys alias

On Wed, Jan 31, 2018 at 12:14:43AM +0100, Geert Stappers wrote: > Parameter name 'ssh-public-keys' causes trouble > when written as ssh-public-keys. Because it can read as > arthmetic expression ssh minus public minus keys. > > So an alias to the rescue. > Parameter name is 'ssh_public_keys'. >

[pve-devel] [PATCH] PVE/API2/LXC.pm ssh-public-keys alias

Parameter name 'ssh-public-keys' causes trouble when written as ssh-public-keys. Because it can read as arthmetic expression ssh minus public minus keys. So an alias to the rescue. Parameter name is 'ssh_public_keys'. Signed-off-by: Geert Stappers --- src/PVE/API2/LXC.pm

Re: [pve-devel] [PATCH cluster] datacenter.cfg: add bwlimit

I think this is the wrong place to add defaults. We need default for various different task, so we should use a more generic concept? > On January 30, 2018 at 4:34 PM Wolfgang Bumiller > wrote: > > > This will define the global defaults which can be overridden > by

Re: [pve-devel] proxmox 2018 : add support for "virtual" network and network plugins ?

On 30 January 2018 at 14:32, Alexandre DERUMIER wrote: > >>I understand what your getting at, but to avoid confusion I would suggest > >>to skip the term symmetric routing here (which would suggest that data > >>to/from follows the same path), > >>routed traffic is usually

[pve-devel] applied: [PATCH v2] improve serial terminal handling

applied whole series On Fri, Jan 26, 2018 at 11:57:58AM +0100, Dominik Csapak wrote: > this series adds the ability to show serial ports on the gui, > and disabling the xtermjs button when no serial device exists for the vm > > changes from v1: > * rebase on current master > * changed icon to

[pve-devel] [PATCH common] schema: add bwlimit standard option and format

Signed-off-by: Wolfgang Bumiller --- This is the single place where new task types can be added. Feel free to comment on the ones below. src/PVE/JSONSchema.pm | 36 1 file changed, 36 insertions(+) diff --git a/src/PVE/JSONSchema.pm

[pve-devel] [PATCH storage] add Storage::get_bandwidth_limit helper

Takes an operation, an optional requested bandwidth limit override, and a list of storages involved in the operation and lowers the requested bandwidth against global and storage-specific limits unless the user has permissions to change those. This means: * Global limits apply to all users

[pve-devel] [PATCH cluster] datacenter.cfg: add bwlimit

This will define the global defaults which can be overridden by per-storage limits. Signed-off-by: Wolfgang Bumiller --- data/PVE/Cluster.pm | 1 + 1 file changed, 1 insertion(+) diff --git a/data/PVE/Cluster.pm b/data/PVE/Cluster.pm index 5fc7d86..b49fd94 100644 ---

[pve-devel] [PATCH 0/3] generic bandwidth limit schema & helper

This series should be the beginning for bringing some consistency into the whole bandwidth/io/rate limiting we have all over the place (vzdump.conf, replication, migration) and allow creating limits for particular tasks, globally and per-storages, since those are usually affected by eg. long tasks

Re: [pve-devel] git repo with PVE/API2/LXC.pm

On Tue, Jan 30, 2018 at 02:18:10PM +0100, Andreas Steinel wrote: > On Tue, Jan 30, 2018 at 2:05 PM, Geert Stappers wrote: > > > Which git repository has the file PVE/API2/LXC.pm ? > > > > Check via dpkg: > > root@proxmox ~ > dpkg -S PVE/API2/LXC.pm > pve-container:

Re: [pve-devel] proxmox 2018 : add support for "virtual" network and network plugins ?

>>I understand what your getting at, but to avoid confusion I would suggest >>to skip the term symmetric routing here (which would suggest that data >>to/from follows the same path), >>routed traffic is usually very asymmetric. I mean symetric because egress/ingress on the proxmox node where the

Re: [pve-devel] git repo with PVE/API2/LXC.pm

On Tue, Jan 30, 2018 at 2:05 PM, Geert Stappers wrote: > Which git repository has the file PVE/API2/LXC.pm ? > Check via dpkg: root@proxmox ~ > dpkg -S PVE/API2/LXC.pm pve-container: /usr/share/perl5/PVE/API2/LXC.pm so

[pve-devel] git repo with PVE/API2/LXC.pm

Hi, Which git repository has the file PVE/API2/LXC.pm ? Cheers Geert Stappers -- Leven en laten leven ___ pve-devel mailing list pve-devel@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

Re: [pve-devel] proxmox 2018 : add support for "virtual" network and network plugins ?

On Jan 30, 2018 09:19, "Alexandre DERUMIER" wrote: 2)if a routing protocol exist between the proxmox nodes and the router, the router can send directly traffic to the correct proxmox node. (symetric routing). I understand what your getting at, but to avoid confusion I

[pve-devel] [PATCH manager] fix #1635: correctly change maxIds in ControllerSelector in wizard

we want to change the maxIds value even when not rendered, since in the wizard, the controller can change from a different panel in the tabpanel Signed-off-by: Dominik Csapak --- www/manager6/form/ControllerSelector.js | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

[pve-devel] applied: [PATCH ha-manager 0/8] simulate and cope with unavailable cfs

applied with Dominik's R-b and T-b tags and very minor whitespace cleanup. Much thanks for the review and testing!! ___ pve-devel mailing list pve-devel@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

Re: [pve-devel] proxmox 2018 : add support for "virtual" network and network plugins ?

I have thinked about the external gateway with vxlan ebgp, it's not so difficult, 1)if the upstream router can't do bgp or other routing protocol, we simply need to manage an ha vip on our side (vrrp) for the ingress traffic from the router and routed inside the vxlan. the egress traffic will

Re: [pve-devel] proxmox 2018 : add support for "virtual" network and network plugins ?

I have thinked about the external gateway with vxlan ebgp, it's not so difficult, 1)if the upstream router can't do bgp or other routing protocol, we simply need to manage an ha vip on our side (vrrp) for the ingress traffic from the router and routed inside the vxlan. the egress traffic