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

[Alexandre DERUMIER]

>>But nobody really use that - not even debian plans to switch to that 
>>implementation? 

cumulus linux used it on their switch ;) I don't known if debian is planning to switch for buster in 1 or 2 years or not.
But it's backward compatible with current ifupdown (excluding) ovs.  (they have vlan aware bridge support, vxlan support, ...)

I have see a recent presentation at debconf 14
https://www.youtube.com/watch?v=lDPPcDoShEI


>>Never tried, but why not? Well, AFAIK it is written in C. 
I'll try to take time to look at it.


>>I guess this is the fasted way to go, but then we need to write 
>>and maintain everything ourselves. I would prefer to work on 
>>something that can be shared across multiple projects? 

I think that we also need network plugin, because if we want to implement something else than bridge or ovs,
we need to manage the tap plug/unplug (or vhost-user if we wan't to play with dpdk), maybe specicic implementation.
or if we want to manage something more complex which need global config. (
for example, opencontrail allow to define ip range by network, and have an integrated dhcp)
or vxlan + evpn-bgp, which need to manage a bgp daemon on host
...

I'm not sure that all is possible with a simple local configuration in systemd-networkd




----- Mail original -----
De: "dietmar" <dietmar at proxmox.com>
À: "aderumier" <aderumier at odiso.com>
Cc: "pve-devel" <pve-devel at pve.proxmox.com>
Envoyé: Mardi 2 Janvier 2018 08:52:48
Objet: Re: [pve-devel] proxmox 2018 : add support for "virtual" network and network plugins ?

> note that cumulus linux have rewrite ifupdown in python (ifupdown2 package) 
> https://packages.debian.org/stretch/ifupdown2 
> 
> (better ipv6 handing, and graph dependencies between interfaces-bridge-....) 
> but it's limited to linux bridge, no ovs. and I don't known if it's easily 
> extendible 

But nobody really use that - not even debian plans to switch to that 
implementation? 

> >>My original plan was to use systemd networkd: 
> >> 
> >>https://www.freedesktop.org/software/systemd/man/systemd-networkd.service.html 
> >> 
> 
> >>What do you think about that? 
> 
> I don't known too much how systemd networkd is work. is it easily extendible ? 
> 

Never tried, but why not? Well, AFAIK it is written in C. 

> What I mean in mind, in a perl management plugin, to manage more complex 
> network sdn, with virtual networks config shared across nodes. 
> something like openstack neutron 
> plugins should management tap_plug/unplug or vhost_user plug/unplug, firewall 
> rules (iptables or other implement if sdn support it), routing (quagga/frr) 
> like vxlan + evpn-bgp, dhcp/ip management, ... 
> 
> A lot of thing can be improved, I'm not sure in can handle by 
> ifupdown,systemd-networkd,... which are more about local network setup 
> configuration. 

I guess this is the fasted way to go, but then we need to write 
and maintain everything ourselves. I would prefer to work on 
something that can be shared across multiple projects?