Skip to content

What if config Management was created by Game Designers - Patrick Debois

talks 2 min read

The “game designers” behind config management – Mark Burgess, Luke Kanies, Adam Jacob, and Michael DeHaan – did not start out designing games, but their creations share striking parallels with game design. Everyone starts the same way: an SSH for-loop. That is your first level. But you need an engine eventually, because nobody writes assembly code for graphics anymore. Chef Solo, Puppet Apply – those are your casual single-player games. Chef Server, Puppet Server with MCollective – that is your massively multiplayer online experience.

Game designers want you to care about your servers like they are your own characters. Who has named their servers after animals? That is character creation. You think you are a special snowflake, mixing standard components into something unique. But we know that does not scale. Good recipes and manifests are like good stories – that is where it starts. And the tools create passionate communities: Puppet users will argue against Chef users the same way console fanboys argue about platforms. That is not a bug – it is engagement.

What would a high score look like for config management? Uptime? Number of successful changes? Happiness of your users? Change requests finished? It is worth thinking about what makes your config management successful in business terms. Virtual cash could be GitHub stars – getting credit for sharing your code. Cheating happens too: services report as running when the daemon crashed, facts get mimicked, exit codes lie. At scale, people become obsessed with inventory tracking because reality and the configured state can diverge.

The unexplored territory is fascinating: prediction (downloading packages ahead of time because other systems are about to trigger a run), mobile-scale config management (agents on phones), and inter-system orchestration beyond simple convergence runs. And the quote that sticks: there are 40,000 Minecraft servers hosted around the world. Kids are learning DevOps on their own. That is the accessibility level we should aim for.

Watch on YouTube – available on the jedi4ever channel

This summary was generated using AI based on the auto-generated transcript.

Navigate with