Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

When Puppet and Chef Aren’t Quite Enough

DZone's Guide to

When Puppet and Chef Aren’t Quite Enough

· DevOps Zone
Free Resource

Download the blueprint that can take a company of any maturity level all the way up to enterprise-scale continuous delivery using a combination of Automic Release Automation, Automic’s 20+ years of business automation experience, and the proven tools and practices the company is already leveraging.

I recently came across this blog post by Mark Needham  that highlights a common problem we hear from our users: even when they use an automated deployment tool like Puppet or Chef, they still run into environment and configuration drift problems. Mark does a great job explaining how this could happen if you’re using Puppet so I’m not going to repeat it here. But suffice to say that when drift does happen, finding it is a slow and painful process and it has the potential to trigger disastrous results:

“…a version got bumped and something elsewhere stopped working and it took us quite a while to work out what had changed.”

Yup, this happens to everybody, even in well managed environments. John Vincent discusses his thoughts on this problem at length here .

While configuration management tools like Chef or Puppet are a critical component of the DevOps Toolchain for building scalable infrastructure, they are only one piece of the automation puzzle. These tools do a great job helping to prevent drift but drift inevitably finds a way to sneak in. Sometimes it’s for the reasons that Mark talked about in his post. Sometimes it’s because humans are still a part of the IT process and where there are humans, chaos (in this case changes that go undocumented or unnoticed!) will ensue .

To ensure that the actual state of your environment is what you think it is, you need to verify it regularly by checking for any deviations from its previous or intended state. This step allows you to close the feedback loop of your automation system.

Just like any good security system which requires firewalls for prevention as well as intrusion detection to catch any sneaky viruses that manage to get in, a robust automation system should include both an automated deployment platform and a drift detection solution . Only then can you be confident that you know the actual state of your environment.

Download the ‘Practical Blueprint to Continuous Delivery’ to learn how Automic Release Automation can help you begin or continue your company’s digital transformation.

Topics:

Opinions expressed by DZone contributors are their own.

THE DZONE NEWSLETTER

Dev Resources & Solutions Straight to Your Inbox

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

X

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}