Not your Grandmother's On-Prem
summary
Argues that modern on‑prem setups use the same cloud-era tools to become manageable: packages everything as Docker Compose containers, publishes a VM image via AWS Marketplace and Azure, builds images with Packer, and stores container images in ECR so customers can spin up a working instance in minutes. Targets mostly single-host deployments to avoid orchestration, accepts strict no‑call‑home and no direct log access policies, and reports upgrades as a one‑command image pull while support relies on guided remote sessions.
AI-written summary · about
chapters (12)
- 0:00Redefining on-prem
- 3:56Why on-prem is challenging
- 8:32When to use on-prem
- 10:11Modern tools for on-prem
- 12:00Key design considerations
- 14:39The on-prem toolkit
- 20:25Orchestration complexities
- 21:55Leveraging public clouds
- 27:32Support in isolated environments
- 31:02Case study of a deployment
- 43:11Overcoming deployment hurdles
- 46:24Conclusion and Q&A
related talks
28mEmbracing On-Prem delivery with DevOps
31mContainers: Not Just for the Cloud?
06mSwitching to On-Premise - The When and the Why
19mDevOps Challenges: The Key Is Technical Excellence
40mHow to build your own cloud while staying in business
31mDockerized app in production? YES WE CAN!!
23mOrchestration and CI/CD
49mThe state of on-prem Kubernetes