Is Bootstrapping BOSH Incredibly Simple Yet?
summary
bosh-deployment repo provides a concrete bootstrap: pick a CPI folder, supply cloud credentials and network vars, run bosh create-env to produce a director VM that embeds a cloud-specific CPI and then use manifests (cloud config, operator files) to deploy workloads. It removes bespoke chef/vagrant hacks, supports VirtualBox for local testing, adds optional UAA and credhub, and can wire Concourse via buck. Networking and org boundaries still cause friction, but the repo reliably yields a working director ready for CF or Kubo.
AI-written summary · about
chapters (11)
- 0:00Introduction and background
- 4:10Why BOSH and its challenges
- 10:39Bootstrapping complexity and networking
- 15:00History of BOSH and MicroBOSH
- 19:27Modern BOSH CLI and external CPIs
- 22:56BOSH deployment manifest basics
- 27:19Local vs. internal CPIs
- 30:31CredHub and automation tools
- 33:21Is BOSH simple yet?
- 34:46The Ultimate Guide to BOSH
- 36:50Closing and recommendations
related talks
25mBOSH Bootstrapping
25mBOSH: The Simple Solution for Complex Systems
30mStreamlining the BOSH Experience
41mBOSH 101 - A Beginners Guide
32mIntroducing bosh-workspace: how we deploy all things BOSH
28mHow to Deploy CF and Other Bosh Releases on Bare-Metal Environment
23mDeploying Cloud Foundry with BBL, BOSH 2.0 and CF-Deployment
34mBUCC - Getting Started with Single Tenant Cloud Foundry