I took another look at this and now I understand the problem that it is
meant to solve. I think that it assumes that a hypervisor that only
offers, for example, STT, to remote hypervisors, is not capable of
using Geneve or VXLAN for tunneling to remote hypervisors. I don't
think that's a correct
If one end is configured external-ids:ovn-encap-type=geneve,stt,the other
end is configured external-ids:ovn-encap-type=stt,
then the tunnel is not available based on the current
implementation,because one end is geneve,the other end is stt.
After this revision,the tunnel will be stt on both ends
---
ovn/controller/encaps.c | 13 ++---
1 file changed, 10 insertions(+), 3 deletions(-)
diff --git a/ovn/controller/encaps.c b/ovn/controller/encaps.c
index f187a8f..5da7fbe 100644
--- a/ovn/controller/encaps.c
+++ b/ovn/controller/encaps.c
@@ -136,14 +136,14 @@ exit:
}
static struct
