Supercharging Development of Cloud Foundry
summary
Containerized Cloud Foundry development uses Fissile to turn BOSH releases into Docker images, a vagrant dev VM with Kubernetes and Helm, and a large shared packages layer (≈30 GB) plus per-role job layers on an openSUSE stemcell. Workflow runs: BOSH create-release, fissile build, then helm install; make targets and caching compute deltas so only changed packages rebuild. Tooling adds linting/validation, self-signed cert generation, and a current issue with secret rotation on helm upgrades.
AI-written summary · about
chapters (14)
- 0:00Introduction to development
- 1:05Introducing Fissile tool
- 4:19Building container images
- 8:15Role manifests explained
- 11:56Configuration and templates
- 14:05From config to Bosh properties
- 16:21Opinionated image settings
- 17:50Makefile and build process
- 20:00Deploying with make run
- 22:37Dependencies and setup
- 23:34Configuration challenges
- 24:41Validation and linting
- 26:24Open source and future
- 28:10Q&A session
related talks
10mCloud Foundry Accelerates "DevOps+"
29mWriting Cloud Foundry Open Source Tools for Everyone...
32mBoost your Cloud Foundry Edit-Build-Deploy-Test-Debug Speed!
33mHow dorma+kaba Leverages and Deploys on CloudFoundry
59mDeep Dive: DotNet and CF Pipeline
19mThe Developer Experience – Zero to Hero
32mCloud Foundry for Everyone!
19mBuilding the Ideal Developer Platform
