Nelson: Rigorous Deployment for a Functional World
summary
Nelson is an open-source Verizon deployment system built from free algebras and coproducts that turns application topology into a graph-based dependency model so the platform can auto-provision credentials, route traffic and prune unused services. It integrates with schedulers (Nomad, Mesos, Kubernetes work underway), uses Vault for per-container ephemeral credentials, offers encrypted-at-rest artifacts, power-curve runtime traffic shifting, and automated lifecycle garbage collection that cut provisioning from two weeks to ~1 minute in practice.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:05What is rigor
- 2:16What is a rigorous system
- 5:27The antithesis of rigor
- 6:09Problem statement
- 8:10Lessons learned
- 9:28Goals
- 11:39Nelson
- 14:57Ops vs Dev
- 15:51Nelson features
- 17:10Rigorous systems
- 22:08Life cycle
- 28:05Security policy
- 31:13namespaces
- 34:55Discovery vs routing
- 36:51Workflow
- 39:10Integration
- 39:59Summary
related talks
40mNelson - Functional programming in system design
33mAbstracting Nomad: Patterns for Deploying to Nomad at Scale
32mDeployment Nirvana
22mRainbow deployments with Nomad
25mNetDevOps: Applying lessons of DevOps to networking
35mCloud Native Development Without the Toil
49mTaming Your Data Networks with the Power of NetDevOps
50mScaling Security Assessment at the Speed of DevOps