[pve-devel] [PATCH pve-network 1/4] vxlan: use vxlan interface name

2019-06-03 Thread Alexandre Derumier
we can't change online vxlan tag, better to map interface name to vxlan tag. (ifreload with delete old interface, and create a new with correct vxlan) also vxlan-id are unique Signed-off-by: Alexandre Derumier --- PVE/Network/Network/VxlanMulticastPlugin.pm | 8 1 file changed, 4 inser

[pve-devel] [PATCH pve-network 3/4] generateconfig test: remove verify merge config

2019-06-03 Thread Alexandre Derumier
we can check conflict with ifquery now Signed-off-by: Alexandre Derumier --- test/generateconfig.pl | 21 - 1 file changed, 21 deletions(-) diff --git a/test/generateconfig.pl b/test/generateconfig.pl index cf55192..fa4e74f 100644 --- a/test/generateconfig.pl +++ b/test/gene

[pve-devel] [PATCH pve-network 2/4] generateconfig: use uplink$id if interface don't exist

2019-06-03 Thread Alexandre Derumier
don't die, generate config, and we'll check error with ifquery as interface don't exist Signed-off-by: Alexandre Derumier --- PVE/Network/Network/VlanPlugin.pm | 3 +-- PVE/Network/Network/VxlanMulticastPlugin.pm | 3 +-- 2 files changed, 2 insertions(+), 4 deletions(-) diff --git a/P

[pve-devel] [PATCH pve-network 0/4] config generation improvments

2019-06-03 Thread Alexandre Derumier
don't stop on error for config generation, we'll check that with ifquery Alexandre Derumier (4): vxlan: use vxlan interface name generateconfig: use uplink$id if interface don't exist generateconfig test: remove verify merge config plugins: generate config: don't check vlan range PVE/Ne

[pve-devel] [PATCH pve-network 4/4] plugins: generate config: don't check vlan range

2019-06-03 Thread Alexandre Derumier
we already have done it on create/modify hooks Signed-off-by: Alexandre Derumier --- PVE/Network/Network/VlanPlugin.pm | 7 --- PVE/Network/Network/VxlanMulticastPlugin.pm | 7 --- 2 files changed, 14 deletions(-) diff --git a/PVE/Network/Network/VlanPlugin.pm b/PVE/Network/N

Re: [pve-devel] [PATCH pve-network 2/3] add ifquery compare status

2019-06-03 Thread Thomas Lamprecht
Dietmar already applied this, but I see a real problem on parsing (mixing of stdout and stderr outputs, see below) and some style problems/ nitpicks, could you please take a look at them and try to send a follow up? That'd be great! (FYI: those marked nit have been already fixed up by me) On 6/3/

[pve-devel] applied: [PATCH pve-network 0/3] add ifquery && status code

2019-06-03 Thread Dietmar Maurer
applied > On 03 June 2019 at 17:57 Alexandre Derumier wrote: > > > prelimary code to handle status of vnets && transports > for later use in pvestatd > > Alexandre Derumier (3): > create api: test if $scfg vnet exist > add ifquery compare status > add test statuscheck.pl > > PVE/API2/N

[pve-devel] [PATCH pve-network 0/3] add ifquery && status code

2019-06-03 Thread Alexandre Derumier
prelimary code to handle status of vnets && transports for later use in pvestatd Alexandre Derumier (3): create api: test if $scfg vnet exist add ifquery compare status add test statuscheck.pl PVE/API2/Network/Network.pm | 2 +- PVE/Network/Network.pm | 28 +++

[pve-devel] [PATCH pve-network 3/3] add test statuscheck.pl

2019-06-03 Thread Alexandre Derumier
could be reuse later in pvestatd to broadcast status. --- test/statuscheck.pl | 44 1 file changed, 44 insertions(+) create mode 100644 test/statuscheck.pl diff --git a/test/statuscheck.pl b/test/statuscheck.pl new file mode 100644 index 000..0a8a

[pve-devel] [PATCH pve-network 1/3] create api: test if $scfg vnet exist

2019-06-03 Thread Alexandre Derumier
--- PVE/API2/Network/Network.pm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/PVE/API2/Network/Network.pm b/PVE/API2/Network/Network.pm index 9c73d19..14d9903 100644 --- a/PVE/API2/Network/Network.pm +++ b/PVE/API2/Network/Network.pm @@ -139,7 +139,7 @@ __PACKAGE__->register_

[pve-devel] [PATCH pve-network 2/3] add ifquery compare status

2019-06-03 Thread Alexandre Derumier
--- PVE/Network/Network.pm | 28 1 file changed, 28 insertions(+) diff --git a/PVE/Network/Network.pm b/PVE/Network/Network.pm index ee0b973..3a33ecd 100644 --- a/PVE/Network/Network.pm +++ b/PVE/Network/Network.pm @@ -3,6 +3,8 @@ package PVE::Network::Network; use s

Re: [pve-devel] [PATCH pve-qemu/qemu-server 0/2] intel MDS CVE fixes

2019-06-03 Thread Thomas Lamprecht
On 6/3/19 3:17 PM, Oguz Bektas wrote: > qemu-server: > > Oguz Bektas (1): > add md-clear cpu flag > > PVE/QemuServer.pm | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > pve-qemu: > > Oguz Bektas (1): > add fixes for intel MDS CVEs > > ...port-to-KVM_GET_MSR_FEATURE_INDEX_LIST-

[pve-devel] applied: [PATCH] apt updates: show full package description conditionally

2019-06-03 Thread Thomas Lamprecht
On 6/3/19 2:32 PM, Tim Marx wrote: > Looks good. > Maybe instead of "Show Full Description" just "Show details". > Thanks for the feedback, with the suggested change: applied ___ pve-devel mailing list pve-devel@pve.proxmox.com https://pve.proxmox.com/

[pve-devel] [PATCH qemu 1/2] add fixes for intel MDS CVEs

2019-06-03 Thread Oguz Bektas
fixes for: * CVE-2018-12126 * CVE-2018-12127 * CVE-2018-12130 * CVE-2019-11091 adds the md-clear cpuflag. Not included by default in any Intel CPU model. Must be explicitly turned on for all Intel CPU models. Requires the host CPU microcode to support this feature before it can be used for gues

[pve-devel] [PATCH qemu-server 2/2] add md-clear cpu flag

2019-06-03 Thread Oguz Bektas
Signed-off-by: Oguz Bektas --- PVE/QemuServer.pm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/PVE/QemuServer.pm b/PVE/QemuServer.pm index 1a22fb4..159a90d 100644 --- a/PVE/QemuServer.pm +++ b/PVE/QemuServer.pm @@ -166,7 +166,7 @@ my $cpu_vendor_list = { max => 'default

[pve-devel] [PATCH pve-qemu/qemu-server 0/2] intel MDS CVE fixes

2019-06-03 Thread Oguz Bektas
qemu-server: Oguz Bektas (1): add md-clear cpu flag PVE/QemuServer.pm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) pve-qemu: Oguz Bektas (1): add fixes for intel MDS CVEs ...port-to-KVM_GET_MSR_FEATURE_INDEX_LIST-an.patch | 146 +++ ...UID-bit-and-feature-words-for-IA32_ARCH

Re: [pve-devel] [PATCH] apt updates: show full package description conditionally

2019-06-03 Thread Tim Marx
Looks good. Maybe instead of "Show Full Description" just "Show details". > Thomas Lamprecht hat am 3. Juni 2019 um 13:02 > geschrieben: > > > The full package description is often quite long, and for upgrades > it's not relevant most of the time. But, it can be intresting to > have, if one wo

[pve-devel] [PATCH] apt updates: show full package description conditionally

2019-06-03 Thread Thomas Lamprecht
The full package description is often quite long, and for upgrades it's not relevant most of the time. But, it can be intresting to have, if one wonders what a package is even used for. So add a checkbox in the top bar which allows to switch between showing and hiding the description, simply done b

[pve-devel] [PATCH v2 widget-toolkit] add network selector widget

2019-06-03 Thread Tim Marx
Signed-off-by: Tim Marx --- * changes since v1: move from manager to widget-tollkit changed prefix from PVE to proxmox Makefile| 1 + form/NetworkSelector.js | 77 + 2 files changed, 78 insertions(+) create mode 100644 form/Netw

Re: [pve-devel] can you bump ifupdown2 mirror to last master ?

2019-06-03 Thread Alexandre DERUMIER
Thanks Thomas ! - Mail original - De: "Thomas Lamprecht" À: "pve-devel" , "Alexandre Derumier" Envoyé: Lundi 3 Juin 2019 11:10:54 Objet: Re: [pve-devel] can you bump ifupdown2 mirror to last master ? On 6/3/19 7:00 AM, Alexandre DERUMIER wrote: > ifupdown2 1.26 is not yet release, but

Re: [pve-devel] can you bump ifupdown2 mirror to last master ?

2019-06-03 Thread Thomas Lamprecht
On 6/3/19 7:00 AM, Alexandre DERUMIER wrote: > ifupdown2 1.26 is not yet release, but can you already update it to last > master ? done, via force push ___ pve-devel mailing list pve-devel@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listin

Re: [pve-devel] can you bump ifupdown2 mirror to last master ?

2019-06-03 Thread Thomas Lamprecht
Hi, On 6/3/19 7:00 AM, Alexandre DERUMIER wrote: > I have pushed upstream some optimisations for ifquery speed > and also a fix with forwarding on reload. > > ifupdown2 1.26 is not yet release, but can you already update it to last > master ? The issue is that we would need to force push master