We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

Use case: Configuration Management in an enterprise Linux Team

Formal Metadata

Title
Use case: Configuration Management in an enterprise Linux Team
Subtitle
How I automated myself out of my job
Title of Series
Number of Parts
199
Author
License
CC Attribution 2.0 Belgium:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Identifiers
Publisher
Release Date2014
LanguageEnglish

Content Metadata

Subject Area
Genre
Abstract
About a year ago I accepted a new job in an enterprise Linux environment, running ~450 Linux servers. These servers were running on an internal network and had never been updated. Most work was done ad-hoc and in response to issues or failure. I transformed the team to a pro-active way of working where automation was key. By solving the most frequent problems first, we found the time to automate more and more. Every server was updated and configuration management was introduced. One interesting year later I've automated myself out of my job. The team can easily handle the (now much lighter) workload without me. Users are happy, so mission completed! Configuration management is done using CFEngine 3 and we use other DevOps style tools like Git, Vagrant, Trello, Logstash etc.