IP Anycast: DC/OS Networking for the Modern Datacenter
summary
New Relic experiments show IP anycast for DC/OS/Docker by advertising per-container /32 host routes from a BGP daemon on each host, using a spine‑leaf fabric and equal-cost multipath (ECMP) so routers load‑share traffic. Implementation uses routed container networking (create veth, proxy ARP, host route) and a ready repo—Medallia routed plugin—to export routes. Works well for UDP collectors and front‑end HAProxy with caveats: ECMP knobs and router limits (~16–32 paths) can reset flows and break graceful maintenance.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 0:58What is Anycast
- 3:03ECNP
- 5:51ECNP Hashing
- 7:22Routing
- 8:09Drawbacks
- 8:36Spineleaf topology
- 12:19Host Routes
- 12:59Docker
- 15:23Anycast
- 17:11Plugins
- 18:54Container Plugin
- 20:42Routing Network
- 21:09Virtual Ethernet Pair
- 22:46Container Routing
- 23:41Use Cases
- 28:19C routed plugin
related talks
33mContainer Networking for Micro-Services: An Apache Mesos Networking Deep Dive
37mGlobal Container Networks on Kubernetes at DigitalOcean - Andrew Sy Kim, DigitalOcean
29mUsing the Internet as Your Load-Balancer
22mLayer 3 networking with BGP in hyperscale DCs
32mCF Networking: All Your Packets are Belong to Us
22mTransparent MultiNIC Routing for Large AI Models
32mLeveraging open source dynamic routing to implement a spine/leaf in datacenter
26mContainer Networking: The Play of BPF and Network NS with different...
