3 ms·

That was my sense too back than, Puppet had early traction, but lost out to Chef, and then Ansible turned out to be the marathoner of the 3.

tnolet 5y ago
Seems like doing $100M+ in ARR (as hinted in the article) is a win. Even more because Chef was acquired for $220M. I think Perforce will pay a bit more for Puppet.
- polynomial 5y ago
  Their last round in 2020 ($40M from Black Round) was debt financing, not investment. That to me is generally a sign of a struggling company. And when the CEO of such a company claims they were looking for other companies to acquire, it raises a number of questions.
teh_klev 5y ago
Back in the day (~10 years ago?) when the company I worked for was looking at replacing our internal custom provisioning and desired state configuration tooling it was Ansible that won out. We were running a mixed fleet of Windows and Linux hosts - the company was an ISP and shared hoster. At that point in time both Puppet and Chef needed agents to be installed on your servers and we really didn't want to have to manage another background service running on hundreds to thousands of boxes. Ansible didn't have this requirement. Also Windows support was pretty sketchy on Chef and Puppet back then, to the point of being almost studiously ignored, Ansible provided remote PowerShell support. And that was primarily the deciding factor.
- twic 5y ago
  I used Puppet around 2012. I remember looking at Ansible, and immediately seeing that its agentless, SSH-based approach was highly preferable. But every time i discussed it with the devops experts in and contracted to our company, they assured me that agentless was terrible, and had too many disadvantages, and couldn't scale. And yet, here we are. Puppet grew an agentless mode, and then lost anyway. My former company's deep investment in integrating Puppet and MCollective into our infrastructure tooling must look increasingly like a millstone. Oh well, it was all interesting to work on.

tnolet 5y ago

Seems like doing $100M+ in ARR (as hinted in the article) is a win. Even more because Chef was acquired for $220M. I think Perforce will pay a bit more for Puppet.

polynomial 5y ago
Their last round in 2020 ($40M from Black Round) was debt financing, not investment. That to me is generally a sign of a struggling company. And when the CEO of such a company claims they were looking for other companies to acquire, it raises a number of questions.

teh_klev 5y ago

Back in the day (~10 years ago?) when the company I worked for was looking at replacing our internal custom provisioning and desired state configuration tooling it was Ansible that won out. We were running a mixed fleet of Windows and Linux hosts - the company was an ISP and shared hoster. At that point in time both Puppet and Chef needed agents to be installed on your servers and we really didn't want to have to manage another background service running on hundreds to thousands of boxes. Ansible didn't have this requirement. Also Windows support was pretty sketchy on Chef and Puppet back then, to the point of being almost studiously ignored, Ansible provided remote PowerShell support. And that was primarily the deciding factor.

twic 5y ago
I used Puppet around 2012. I remember looking at Ansible, and immediately seeing that its agentless, SSH-based approach was highly preferable. But every time i discussed it with the devops experts in and contracted to our company, they assured me that agentless was terrible, and had too many disadvantages, and couldn't scale. And yet, here we are. Puppet grew an agentless mode, and then lost anyway. My former company's deep investment in integrating Puppet and MCollective into our infrastructure tooling must look increasingly like a millstone. Oh well, it was all interesting to work on.