The New Way to BOSH Deploy - Urvashi Reddy, Pivotal
summary
BOSH 2.0 replaces fragile manifest generators with layered ops files that perform concrete operations like remove and replace, and support array appends and conditional paths. Use the go CLI commands bosh interpolate and --var-errors to preview manifests and catch missing vars. Project experience (Dedicated MySQL V2 for PCF) shows ops files are order dependent, so authors must ship a base manifest, versioned ops files, and documented workflows; unit-tested ops files prevent surprising overrides during deploy.
AI-written summary · about
chapters (8)
- 0:00Introduction and context
- 1:23What changed with ops files
- 4:59Basic ops file example
- 8:05Remove and replace operations
- 13:10Order dependency and overrides
- 16:44Ops files for release authors
- 19:14Best practices for ops files
- 21:22Conclusion and Q&A
related talks
30mBOSH CLI v2: the evolution of the BOSH command line interface
41mBOSH 101 - A Beginners Guide
25mBOSH: The Simple Solution for Complex Systems
32mIntroducing bosh-workspace: how we deploy all things BOSH
23mDeploying Cloud Foundry with BBL, BOSH 2.0 and CF-Deployment
30mStreamlining the BOSH Experience
24mOn-Demand Service Provisioning with BOSH 2.0
26mBOSH Splitter