Skip to main content

Puppet vs Chef

I hear many people asking which is better Chef or Puppet.  Which is for developers and which is for Admins?  Then, you throw in Ansible and Salt and you get even more drama and stress.  Some companies have pockets of Chef and then, another of Puppet.  Then, someone brings in another tool and everyone is debating and struggling.   Here is my opinion and many of you are not going to like it because it will cause one vendor or team to be critical of my recommendation.

I recommend going with which ever your Ops teams like or uses.  This is the team that needs the most help in this area.  Tools like Puppet and Chef provide the most value when everyone is on the same page and want to use them.  If your Dev teams are shoving Chef down the Ops guys throats, they will never buy in.  If the Ops guys start using any tool, Devs should be able to pick them up easily.  

If you have multiple ops teams, and they are using multiple tools, that might be ok but you will never fully mature them to an enterprise level.  In this case, I recommend evaluating which one has the most mature process and the most code written.  Then, either do all new work in that tool or migrate them all to that tool.  It should be easy but will take some man hours to accomplish.  It is important to treat tools like Chef and Puppet like enterprise tools and not like  tools that can stand on their own for a team.

So you chose a tool, now what?  I will talk about this in a future post.

Comments

Post a Comment

Popular posts from this blog

2020 State of DevSecOps by Accurics

 This is an excellent report for all IT Pros and Engineers.   Highlights: Storage is most impacted solution Open security groups or network configuration Secrets are not so secret Unused resources are not secure. Take a look at these.  Look again.  These are not highly skilled problems.  They just need guidelines and proactive management.  The article uses policy as code as a solution for many of the problems.  I will drill into each of these more in the future.  I wanted to get the awareness out first and then, come back to solutions.  
Post a Comment
Read more

Learn Anti-Leadership from Basecamp

 There are many different articles out there and Twitter comments about the Basecamp drama.  I am not going to post any here because it might seem biased depending on the article.  Google them yourself.  In short, Basecamp made a policy to not allow political discussions at work.  Coinbase did this previously too and applauded Basecamp for it.   Apparently, for years there has been a list of funny customer names at floating around Basecamp.  This list or even the knowledge that Basecamp had a list, was disturbing to some employees.  Also, some employees tried to start a Diversity and Inclusion practice.  Despite how much the founders of Basecamp promoted DI, they didn't feel they were being taken serious.  They felt the company was only about the founders and not about employees.    If this isn't enough, the founders debated and even called out employees for their comments regarding the topics, publicly.  This is my s...
Post a Comment
Read more

Cloud Ops: The New IT for the Cloud Era

Over the past few months of interviewing and researching dozens of companies—particularly small to mid-sized SaaS businesses—one pattern keeps emerging: the desire to stand up a Cloud Operations (Cloud Ops) organization. It makes sense on the surface. Cloud is now the infrastructure of choice, so naturally, someone needs to “own” it. But what’s unfolding in practice often misses the mark. Many companies are attempting to solve growing cloud complexity by taking all their DevOps, SRE, and platform engineering talent and consolidating them into a Cloud Ops team. The idea? Share them across product teams so no one gets overwhelmed. If that sounds familiar, it should. It’s the same centralization tactic used by traditional IT for decades. And it's creating the same problems. When Cloud Ops Becomes Old IT in Disguise Here’s the playbook we’re seeing: Move DevOps, SRE, and Ops into a central Cloud Ops team. Let them handle infrastructure, CI/CD, monitoring, and cloud securit...
Post a Comment
Read more