An Approach to Air-Gapped Deployment
summary
Built a small Chef-based system called chef countertop that packages Chef server, client RPMs, ChefDK, policyfiles and production cookbooks as cookbook-artifacts and uses chef-zero plus the machine resource’s converge_only action to turn existing air-gapped VMs into a full Chef organization. Validation runs on a cloned org via GitLab CI and knife-vsphere: CI clones a golden org, uploads the cookbook, triggers a node run, inspects success, destroys the temp org and only then publishes to production; this prevents broken uploads and scales in practice.
AI-written summary · about
chapters (6)
- 0:00Introduction and context
- 2:20About the speaker and Sandia
- 5:46Challenges of air-gapped infrastructure
- 11:41Architecting the solution
- 24:44Validation and CI pipelines
- 31:27Lessons and best practices
related talks
33mDeveloping for Multi-Component Environments While Keeping Your Sanity
42mCI Techniques for Delivering the Chef-Repo: Three Case Studies
33mScaling Chef Emotionally
41mDon't Depend on a Single Chef Server Divide and conquer...
28mChef Cookbook Design Patterns
40mJenkins and Chef: Infrastructure CI and Application Deployment
41mManaging the Unmanageable
39mInstalling and Configuring Artifactory using Chef Recipes