Update the BFD todo item to clarify where we might use BFD as it
previously seemed to imply we wanted to enable it for all
hypervisor-to-hypervisor tunnels.
Signed-off-by: Russell Bryant <russ...@ovn.org>
---
This patch attemptes to update the TODO item based on our ML discussion.
Alternatively, we could just remove the TODO item since it's more speculative
at this point.
ovn/TODO | 15 +++++++++++----
1 file changed, 11 insertions(+), 4 deletions(-)
diff --git a/ovn/TODO b/ovn/TODO
index 1f2a73f..22d6bd8 100644
--- a/ovn/TODO
+++ b/ovn/TODO
@@ -306,11 +306,18 @@ think it does everything else.
the Multicast_Group table entry in ovn-sb database into
Mcast_Macs_Remote table configuration in VTEP database.
-* Use BFD as tunnel monitor.
+* Consider the use BFD as tunnel monitor.
- Both ovn-controller and ovn-contorller-vtep should use BFD to
- monitor the tunnel liveness. Both ovs-vswitchd schema and
- VTEP schema supports BFD.
+ The use of BFD for hypervisor-to-hypervisor tunnels is probably not worth it,
+ since there's no alternative to switch to if a tunnel goes down. It could
+ make sense at a slow rate if someone does OVN monitoring system integration,
+ but not otherwise.
+
+ When OVN gets to supporting HA for gateways (see ovn/OVN-GW-HA.md), BFD is
+ likely needed as a part of that solution.
+
+ There's more commentary in this ML post:
+ http://openvswitch.org/pipermail/dev/2015-November/062385.html
* ACL
--
2.5.0
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
