Abandoned

After writing this, I don't think there is a usecase for it. The reason to always send VM's traffic from the same port is that if we did not do that, the physical switch would be confused about whereabouts of the VM. In case of overlay, the VM traffic is not visible to the switch, so there is nothing to be confused about.

The real motivation for port-based-hash seems to be performance of hash calculation.

------

Goal

Support active-active bonding without a need to configure physical switches, while evenly balancing network overlay traffic.

User Stories

• As an admin, configuring bonding in active-active mode, unable to reconfigure physical switch, supporting infrastructure for many VMs connected through overlay networks,
  I want traffic of these VMs to be spread equally within the ports of the bonding.

Non-Requirements

• <List of things not included in this epic, to alleviate any doubt raised during the grooming process.>

Notes

• Customers coming from VMware are used to having bond active-active bond modes that do not require switch-side configuration:

• • "Route Based on Source MAC Hash" is something we are now addressing with SLB bonding with MAC+VLAN used for the hash
  • "Route Based on Originating Virtual Port" is something we don't have an alternative for, this gap is tracked by this epic
• With basic bridge+VLAN networking, the two modes described above produce the same result. However, when overlay networking is used, all the traffic is tunneled from br-ex, and so MAC+VLAN hashing is not a good fit.