[pve-devel] linux bridge vlan aware implementation config in cumulus network linux

[Alexandre DERUMIER]

>>My feeling is that the number of packages we need to maintain gets far too high.
>>
>>So if we go that way, we need to make sure that debian people will integrate
>>those changes.

I just tried iproute2 (4.0) package from debian stretch repository, it's working fine.



The vlan range feature in from kernel 4.0, it's only 3 small patches,  I would like to add them to current 3.19 kernel.
Any objection ?



Also , I have looked a little bit more to cumuslus ifupdown2,
they have a big advantage, is that it's possible to reload network config, and ifupdown2 can manage dependencies,incremental updates
with need to stop/start network device.
That mean : be able to apply /etc/network/interfaces changes without reboot easily.

https://www.youtube.com/watch?v=HXFkzHbFQfw
http://cumulusnetworks.com/blog/ifupdown2/

Seem that cumulus guys are trying to push ifupdown2 as default for next debian version.
It's backward compatible with current ifupdown, but I think that only ovs syntax is not managed.
I need to do more test to see how it's works.



----- Mail original -----
De: "dietmar" <dietmar at proxmox.com>
À: "aderumier" <aderumier at odiso.com>, "pve-devel" <pve-devel at pve.proxmox.com>
Envoyé: Jeudi 23 Juillet 2015 17:56:08
Objet: Re: [pve-devel] linux bridge vlan aware implementation config in cumulus network linux

> Seem that they completly replace ifupdown by their own implementation in 
> python 
> 
> https://github.com/CumulusNetworks/ifupdown2 
> 
> 
> so, I think I'll just take ideas from syntax, et reimplemented them in bash. 
> 
> 
> BTW, It could be wonderfull if we upgrade iproute2 to match the kernel version 
> we used 
> http://git.kernel.org/cgit/linux/kernel/git/shemminger/iproute2.git/commit/?id=46d364fe8fa9fd6f5ca3989b572a2548d9caf56a 
> 
> They are a missing feature to define vlans range in current jessie iproute2 
> (feature introduce in kernel 3.19). 

My feeling is that the number of packages we need to maintain gets far too high. 

So if we go that way, we need to make sure that debian people will integrate 
those changes.