On 01/07/15 at 08:56am, Tom Herbert wrote: > On Wed, Jan 7, 2015 at 8:21 AM, Thomas Graf <tg...@suug.ch> wrote: > > If the VNI is not already used for another purpose, yes. The solution > > as proposed can be integrated into existing VXLAN overlays separated by > > VNI. It is also compatible with hardware VXLAN VTEPs which ignore the > > reserved bits while continueing to maintain VNI separation. > > It seems like it should be relatively easy to group VNIs together to > have the same mark with the current use of VNI. The works up to the > point that all packets corresponding to a single VNI get the same > mark.
This really depends on the network architecture and assumes that you can remap the VNIs in the entire network. You might want to run L3 with group definitions across multiple L2 VNI segments. A second issue is that many hardware VXLAN VTEPs do VNI based learning and will run into capacity limits. I'm not saying it's impossible but it's very tricky to intergrate if you can't start from scratch. The whole point of this is to come up with something that is painfully easy to use and integrate without requiring to change much. _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
