Config Management Camp 2024 Ghent

Finding config management's place in the continuous delivery pipeline
2024-02-05, 14:00–14:50, B.3.036

In a small environment a single devops engineer or team of engineers can automate changes to production with a well tuned configuration management system. In a large production environment that spans the globe and contains more functional parts than a single team could manage, running config management as continuous delivery is practically untenable. Risky changes need to be incremented by smaller deployment steps or separated into smaller deliverables. High risk services and locations need more validation time before accepting changes. With many teams pushing dozens of changes to production daily, there is a need for health-mediated deployment. Ideally, service owners self-serve change management+health metrics with state enforcement completely decoupled and below the API.

I work at Cloudflare on the Platform Configuration team. We maintain the software that automates the provisioning and maintenance of all servers routers and switches in Cloudflares global fleet.

This speaker also appears in: