4 ms·
> These are lessons that Ansible actively refused to learn. At least until recently. what changed?
by zufallsheld 5y ago
> These are lessons that Ansible actively refused to learn. At least until recently.
what changed?
- bradknowles 5y agoThey continued to get repeated complaints about scalability, and it became more and more clear to them that they would have to implement their own agent, in the vein of Puppet and Chef. They also got complaints about Ansible scripts failing in weird ways because of all the different shell versions, and their scripts weren’t written in a sufficiently robust manner. That was a pretty killer one-two punch.
- zufallsheld 5y agoCan you point to some sources about this?
- bradknowles 5y agoVarious private conversations that I had with folks at Opscode/Chef and various people I’ve spoken to from AnsibleWorks. UT Austin was a user of Cobbler, and after leaving UT Austin, I learned Chef to completely redesign and redeploy the production service networks for a small startup here in Austin, by the name of ihiji (who was since bought by Control4). Many thanks to my good friend Matt Ray for that referral. I have stayed in the Chef community and broader DevOps community, working as a consultant for Momentum Software (before and after they got bought by VMWare), and even leading up to the work I was doing as a consultant at Whole Foods (before they got bought by Amazon), I continued to have contacts and conversations with various people in this space. So, nothing on paper. Just private conversations with various people over the years.