Basic infrastructure automation is a no-brainer – Why aren’t you doing it?
Everyone knows they need to automate. That is not a thought-provoking statement. In fact, when we ask infrastructure decision leaders their top priorities, automation shows up at #3, just behind consolidation and implementing operations analytics.
However, when we dig deeper with clients, we find hesitation. I would break their concerns into three broad camps:
People are confused, but who can blame them? Between enterprise and open source, there are dozens of options for infrastructure automation. Which ones are best?
To reach that baseline, you need to use so-called “configuration management” tools. This includes well-known players like Chef, Puppet, Ansible and Salt, new players like Normation, and stalwarts like CFengine and Microsoft. In a new Wave, Rob Stroud and I evaluate these using 25 unique criteria, including not only how they handle configurations on-premises and in the cloud, but how to visually edit models, monitoring and governance, and community support. It is not just about keeping configurations in sync – it is how these tools integrate with critical service delivery, DevOps and compliance initiatives.
Whether you are new to infrastructure automation or an old hat, you owe it to yourself to see how these tools scored. You may be surprised.