BOSH – Restore from an Availability Zone Outage
summary
Migrates director state to an external blobstore and a managed RDS database (using pg_dump), replaces static IPs with hostnames, and adds ACLs plus connection termination to isolate the old director before provisioning a new director in another AZ; blob migration needed retry logic and AWS root CA fixes. The cutover aims for zero downtime for VMs, requires rotating DB passwords and removing DNS records, and a manual restore sequence currently takes about 10–20 minutes to bring a new director up.
AI-written summary · about
chapters (8)
- 0:00Introduction to BOSH
- 2:10Multi-AZ outages impact
- 4:21Scenario of AZ outage
- 6:49Externalizing BOSH components
- 9:00Externalizing director database
- 11:32Recovering from AZ outage
- 14:25Key takeaways and future work
- 15:49Q&A session
related talks
30mStreamlining the BOSH Experience
28mBurning Down The House: How to Plan for and Deal with Disaster Recovery in CF
27mBOSH: The Road Ahead
30mBeyond 1000 BOSH Deployments
30mBurning Down the House: How to Plan for and Deal with Disaster Recovery in CF
25mBOSH Bootstrapping
32mLossless Upgrade of BOSH Deployment
35mMigrating a live site across the country without downtime
