I missed the discussion on this patch set. I can see that it's been accepted. Still, I'd like to ask a question.
Originally there was the VTEP-only VxLAN scenario that worked great in OVN. Then, the patch by Ihar Hrachyshka provided support for internal VxLANs. The tunnel id space was severely limited which, in turn, became the limitation for the VTEP-only VxLAN scenario as well. In other words, the patch that introduced internal VxLANs broke the scenario for VTEP-only VxLANs. In essence, Vladislav Odintsov asserts that the patch by Ihar Hrachyshka introduced an implicit configuration option the state of which was determined in software (the function is_vxlan_mode()). The new patch by Vladislav Odintsov makes that option explicit. That makes the behavior of a configured cluster completely depend on its value - as opposed to determining the behavior in software from configuration. On the one hand, that makes it simple - one option to control whether the cluster supports internal VxLANs or it is VTEP-only VxLANs. On the other hand I can't help but wonder - why can't that be determined in software - like in the original patch? I would think that all necessary data is present in a configuration and there's no need for an extra explicit option. With the new patch from Vladislav Odintsov it can be done just once in one place. So the question is: what are the pros and cons of each variant? Why is the variant with a new option chosen? Thanks! _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
