Nine Questions to Build Great Infrastructure Automation Pipelines
summary
Nine practical questions that reveal why CICD models fail for infrastructure and how to build predictable, reusable pipelines that move persistent resources across cloud, VM and bare metal. Details include nine questions that drive design, pipeline segments like discovery, burn‑in, OS install, app install with standard pre/post work and classification-based profile assignment, explicit state sharing between tools (Terraform, Ansible, PXE) and a working implementation in Digital Rebar 4.7 showing modular, composable pipelines.
AI-written summary · about
chapters (12)
- 0:00Intro
- 3:43Why doesn't my CI/CD pipeline understand infrastructure?
- 5:12Why is a "Pipeline Flow" different than other Orchestration
- 6:27Why focus on Intents instead of the chained actions?
- 8:22Why are provisioning and configuration so different?
- 10:16Why can't I share state between tools?
- 12:32Why can't I ignore what is between pipeline flows?
- 14:08Why is lac central to Infrastructure Pipelines?
- 15:39Why is it so hard to reuse and share automation parts?
- 17:04What is holding us back from doing this work?!
- 18:15What is a Standardized Infrastructure Pipeline? Infrastructure Service
- 24:56Five things that can help you build Infrastructure Pipelines.
related talks
46mImplementing Infrastructure as Code
43mEvolutionary Infrastructure Using Pipelines
31mI Coded 47 IaC Pipelines Before I Understood: The Ultimate Pipeline Guide
01h 02mTools and Techniques for Infrastructure as Code
46mThink of your infrastructure as code
28mContinuous Integration and Continuous Delivery Pipelines for Beginners and Managers
22mInfra vs Apps – Where are my Pipelines?
26mIntelligent Deployment Pipelines