Linux trunking, bonding, and bridging is outdated, awkward to configure, and doesn't do vlans or virtual interfaces very well. With today's modern infrastructure requirements, I think proxmox 4 should switch to openvswitch by default instead of legacy software. It does everything that the other three do, it does it with a simpler to manage interface, and it does it in one unified package. Not only that, any moderately sized data center will need these features to be properly configured anyway. Having them set up out of the box and ready to go can only help.
Proxmox 4 should use OVS by default
- Thread starter aarcane
- Start date
I you want to try I have made an example for default proxmox network configuration using OVS instead available here: https://pve.proxmox.com/wiki/Open_v...ternal_Ports_.2B_Untagged_traffic_.2B_No_LACP
I've got proxmox + ovs set up in testing now. It's working wonderfully already, and I've got another debian system about to go into proxmox testing with LACP as well. Having configured both in both linux and proxmox, I definitely think OVS should be default.
Code:
Linux trunking, bonding, and bridging is outdated, awkward to configure, and doesn't do vlans or virtual interfaces very well.since kernel 3.10, linux bridge support vlan tagging. (and also q-in-q vlan stack).
Cumulus network is doing a fantastic job since some months on briding/network stack, because they use it to manage physical switches.
We are looking to implement that currently.
OVS still missing igmp snooping, q-in-q but coming ovs 2.4 will improve that.
After that, we'll be able to evaluate which one is the best by default