>>We currently store network settings in /etc/network/interfaces and use >>ifupdown >>to >>manage everything. But ifupdown is badly maintained and there is no more >>developement >>on that package, so we want to move away from that.
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 >>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 ? 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'm asking about this, because currently, we are running a big flat layer2 network with vlan, and with 4000vms, it's begin to do a lot of broadcast and macs address on switchs, so we are planing to do a full layer3 network with network overlay (maybe vxlan+ evpn bgp, maybe opencontrail, maybe something else), and cross datacenter interconnect). _______________________________________________ pve-devel mailing list pve-devel@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
