Container Orchestration and Software Defined Network: A Field Report
summary
Claims building DC/OS networking with Erlang-backed components, actual artifacts and outcomes: a two-person team creates a shared control plane called Lashup control plane, a per-node Minuteman load balancer, and the Spartan DNS edge resolver, using CRDTs, distributed Erlang, property testing and kernel netlink hooks. Lashup runs adaptive gossip and spanning-tree routing, supports an eventually consistent KV and scales to ~10,000 nodes in production; failure tests show near-zero throughput impact versus a Zookeeper-style approach.
AI-written summary · about
chapters (14)
- 0:00Intro
- 1:24Data Center Networking in 2007
- 3:04DevOps in 2008
- 6:25Business Value
- 7:59What is DCS
- 8:28Service Discovery
- 12:39New Services
- 14:27DNS
- 18:14Global State
- 20:48HyperView
- 26:50Demo
- 29:26Erlang
- 31:08Components of Erlang
- 34:45Testing
related talks
43mPanel Discussion: Containers and Networking: A Symbiotic Relationship
36mNetwork Machinery: A United-Front for Network Troubleshooting with CRDs
28mOverview Of Challenges And Solutions For Orchestrating Applications To Multiple DC And Edge Clusters
10mLightning Talk: Join the Cloud Native Journey to Shuttle Back and Forth Applications Across Edges
40mKubernetes Networking Panel: Collaborate on the Spec, Compete on Execution
30mContainers and Next Gen Infrastructure Ecosystem
31mReverse Engineering Cloud Native: Interoperability and Community
31mBreaking the Single-Network Barrier: A Cross-Domain Look at…