+++ This bug was initially created as a clone of Bug #1881704 +++ +++ This bug was initially created as a clone of Bug #1881697 +++ +++ This bug was initially created as a clone of Bug #1841526 +++ Description of problem: right now VXLAN is not supported by OVN for regular inter-chassis communication. There is VXLAN support for "vtep" ovsdb schema compliant external switches (aka ramp switches). This RFE is to extend core OVN to support VXLAN for regular in-cluster traffic. Initial upstream discussion: https://www.mail-archive.com/ovs-discuss@openvswitch.org/msg06771.html Demo implementation: https://patchwork.ozlabs.org/project/openvswitch/patch/20200320050711.247351-1-ihrachys@redhat.com/ Related links: https://blog.russellbryant.net/2017/05/30/ovn-geneve-vs-vxlan-does-it-matter/ Core OVN work is tracked in bug 1841526. Neutron work is tracked in bug 1881697. This bug is to adjust TripleO to allow to enable VXLAN network type for OVN setups. We should also consider if we want to enable it by default or not. An example of a fix can be seen here: https://review.opendev.org/753453 --- Additional comment from on 2020-12-07 16:05:13 UTC --- moving to networking for prioritization.
*** This bug has been marked as a duplicate of bug 1881697 ***
*** This bug has been marked as a duplicate of bug 1881704 ***