Updated 12 june: Minimum packages version (available in no-subscription-repo) libpve-network-perl_0.4-6 ifupdown2_3.0.0-1+pve2 pve-manager_6.2-6 Changelog beta v2: - reworked the vnet design - add support for vlanware vnet. (you can use now vlan tag or thruk in vm nics, inside a vxlan,qinq,vlan tunnel) - lot of fixes with ovs + vlan/qinq plugin (thanks to pieteras.meyer for testing!)
proxmox 6.2 include a new sdn (software delivery network) feature, it's beta for now.
I'm the main author of this feature, and I would like to have some feedback of community to improve it.
Doc is here:
The main idea, to to defined virtual network at datacenter level.
The more simple example, is a vlan network. Instead of defined the vlan tag on the vm nic, we define the network at datacenter level.
This will allow to define permissions of this network. (like for a storage).
The sdn feature use a plugins, so it can be extended easily.
Currently, it's support
vlan,qinq (stack vlan), vxlan
bgp-evpn network is the most complex and true sdn network. it's need a controlller (it's using frr routing software), to manage the flow of the bridge.
It's allowing anycast routing across different vxlan network. (each proxmox host have same ip for each bgp-evpn network, and are the gateway of the vm/ct).
I think it could help too users on public servers like ovh,hetzner with different public subnet/failover ips. (you could easily diffined 1virtual network by subnet).
If users need some other sdn plugins, I'll could look to implement them in the future. (but first, I would like to have 0 bugs on current plugins)
If you have time to test it, and give some feedback on this thread, it could be wonderfull.
You can also contact me directly by email : email@example.com
Feedback/Need to be fixed:
Gui: the vlan field on the vm/ct nic should be grey-out when a sdn vnet is choose. (keep it empty for now)