Norouter: Running Cloud Foundry without the Gorouter
summary
A BOSH-deployable agent called Norouter collects NATS route events and programs F5 LTM via REST so the enterprise load balancer becomes the single hop into Cloud Foundry, reducing latency and simplifying global DNS, TCP VIPs and sticky sessions via LTM scripts. Norouter converts LTM logs to dropsonde and forwards them to metron for access logs and metrics. It is open source (Apache 2.0), Java-based, beta-quality, does not yet support Diego route API or wildcard/context-path routes, and currently targets F5-only deployments.
AI-written summary · about
chapters (13)
- 0:00Intro
- 1:20The Team
- 1:53Our CF Routing Architecture
- 2:46Big IP Local Traffic Manager
- 4:40Value of LTM
- 6:03Desired Routing Architecture
- 6:24Why does it matter?
- 10:48Open source
- 11:40Norouter architecture
- 16:59Gorouter Troubleshooting Benefits
- 18:32Logging/Metrics Solution
- 20:53Norouter Pros
- 25:11Questions?
related talks
06mLightning Talk: Cloud Foundry Revisited: UDP, VoIP, and Beyond!
15mRecent Enhancements to Routing in Cloud Foundry
22mLayer 3 networking with BGP in hyperscale DCs
29mSetting up a Multi-Cloud, Enterprise-Grade Cloud Foundry Installation: Bridging Infrastructure
25mEnable IoT and Media Support in CF with Custom TCP/UDP Routers
31mCloud Foundry Networking: Enabling Direct Communication for Microservices - Chin, McClure
32mCF Networking: All Your Packets are Belong to Us
20mCompletely Isolate your App's Traffic: Isolation Segments at the Routing Tier