Re: [pve-devel] applied: [PATCH V2 ifupdown2 1/1] openvswitch: don't remove tap|veth interfaces when adding an internal ovs port

2020-05-19 Thread Alexandre DERUMIER
>>I saw that ifupdown2 3.0.0 got tagged recently, seems to be partly for python3
>>compat, AFAICS.

yes, it's full rewrite in python3.


>>Or do you know of bigger featuers/fixes om that version?

They are newer features, like 1vxlan tunnel mapping with multiple vlans.
(I don't use it currently).

They was the veth-couple handling, I'll need it for vlanplugin with 
non-vlanaware bridge,
but I can backport it to 2.0 if needed.

openvswitch addon is upstream.


I have already prepared patches for proxmox package for testing, I can upload 
them if you want.
I don't have see regression.

The changes are lower than 1.X->2.X upgrade, it's mainly python3 upgrade + some 
new features.
1.X->2.X was a bigger change with full netlink support (and they was regression 
first)

So, I think it should be ok, but it need more testing of course



- Mail original -
De: "Thomas Lamprecht" 
À: "pve-devel" , "aderumier" 
Envoyé: Mardi 19 Mai 2020 08:28:16
Objet: applied: [pve-devel] [PATCH V2 ifupdown2 1/1] openvswitch: don't remove 
tap|veth interfaces when adding an internal ovs port

On 5/16/20 2:07 PM, Alexandre Derumier wrote: 
> Currently, tap|veth interfaces are removed if user add a new ovs internal 
> port and reload. 
> 
> add ovs-ports-condone-regex option, like for bridge (to have the patch 
> upstream). 
> default options to "tap|veth|fwpr" 
> 
> to avoid to remove theses interfaces 
> 
> Signed-off-by: Alexandre Derumier  
> --- 
> .../pve/0008-add-openvswitch-addon.patch | 37 +++ 
> 1 file changed, 30 insertions(+), 7 deletions(-) 
> 

applied, much thanks! 

I saw that ifupdown2 3.0.0 got tagged recently, seems to be partly for python3 
compat, AFAICS. Or do you know of bigger featuers/fixes om that version? 

___
pve-devel mailing list
pve-devel@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


[pve-devel] applied: [PATCH V2 ifupdown2 1/1] openvswitch: don't remove tap|veth interfaces when adding an internal ovs port

2020-05-18 Thread Thomas Lamprecht
On 5/16/20 2:07 PM, Alexandre Derumier wrote:
> Currently, tap|veth interfaces are removed if user add a new ovs internal 
> port and reload.
> 
> add ovs-ports-condone-regex option, like for bridge (to have the patch 
> upstream).
> default options to "tap|veth|fwpr"
> 
> to avoid to remove theses interfaces
> 
> Signed-off-by: Alexandre Derumier 
> ---
>  .../pve/0008-add-openvswitch-addon.patch  | 37 +++
>  1 file changed, 30 insertions(+), 7 deletions(-)
> 

applied, much thanks!

I saw that ifupdown2 3.0.0 got tagged recently, seems to be partly for python3
compat, AFAICS. Or do you know of bigger featuers/fixes om that version?

___
pve-devel mailing list
pve-devel@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel