Scaling a Migration to CD at Airbnb
summary
Airbnb migrates its deployment system from a Rails deploy board to Spinnaker, running Spinnaker on Kubernetes via a OneTouch framework and teaching it new artifact types and stages with extensions to CloudDriver, Orca and Echo. Developers use Anchor pipelines as code to generate pipelines and canaries; a deadweight stress tool simulates load; about 40-ish services are on Spinnaker today; automated canary analysis validates ~90% of changes and has avoided 29 incidents that would have caused rollbacks, so the approach scales and works.
AI-written summary · about
chapters (33)
- 0:00Introduction
- 1:20Overview
- 2:32Airbnb History
- 3:08Monorail
- 3:45Deploy Board
- 5:15Rapid Growth
- 8:35SOA started falling apart
- 9:02Deployment challenges
- 11:22Deployment pipelines
- 11:50Why did Airbnb adopt Spinnaker
- 16:32Spinnaker on Kubernetes
- 18:25Spinnaker setup
- 21:38Spinnaker deployment
- 24:12Anchor
- 25:52Spinnaker Pipelines
- 26:56Build a CD Platform
- 28:12Extend Echo
- 29:42Watchpoint
- 32:28Extending Spinnaker
- 33:51Extending Backend Services
- 38:11Migration to Spinnaker
- 38:24SOA Services
- 38:48Migration Plan
- 39:41Wrong Boarding Strategy
- 40:10Featured Roadmap
- 40:39Dead Weight
- 41:20Default Pipeline
- 41:33Where are we today
- 41:51GA
- 42:08Continuous Delivery
- 43:24Opportunities
- 44:35Conclusion
- 45:42QA
related talks
28mSpinnaker at Airbnb, one year in
33mPanel Discussion: Spinnaker Success - CD as a Service using Spinnaker
12mImplementing Advanced Deployment Using Spinnaker and Canary
52mContinuous Deployment to the Cloud using Spinnaker
36mSpinnaker - Land of a 1000 Builds
25mEnabling Diverse Application Use Cases using Spinnaker
50mSpinnaker get control over your deployements
31mHow Spinnaker is Shaping Delivery Excellence at SAP