Safe Deployment: Exploring Methodologies
summary
Meta describes a Safe Deployment program that moves from unit and integration tests to a canary phase that can qualify changes by the next day, then does slow rollouts across 25 data centers and thousands of switches. A centralized Network Health Service runs snapshot vs point‑in‑time checks (post‑update wait 2 minutes, extended monitoring every 15 minutes) and triggers human pauses. An emulation‑based routing verification system checks routing policy changes and policy limits cap how much capacity or access automation can remove.
AI-written summary · about
chapters (6)
- 0:00Safe deployment challenges
- 4:05Safe change strategies
- 5:09Rollout testing process
- 9:05Centralized Network Health Service
- 14:06Blast radius limits
- 17:17Future plans and collaboration
related talks
23mContinuous Deployment - The Last Frontier for Continuous Delivery
44mI Deploy On Fridays
34mDeploying Without Crying: Deployment Strategies for Peaceful Nights
21mChange Management in Physical Network Lifecycle Automation
35mIntelligent Deployments at Scale: Effortless Continuous Deploy...
14mCanary Deployments for Infrastructure Upgrades
01h 01mI deploy on Fridays (and maybe you should too)
50mRings and Canaries - Advanced Deployment Scenarios
