Re:Introducing AWS OpsWorks, a Powerful AWS Application Mana...
by ironchef on Tuesday February 19, 2013 @09:29AM
(#5244418)
So Jesse (one of the founders of opscode (makers of chef)) used to work at amazon before he founded chef along with Adam. Adam had been working almost 2 years using puppet at other companies and it was pretty obvious he wasn't happy with the way puppet did things. I've heard that chef was closer to the method of thinking that amazon employed in their automated operations (which wasn't really exposed to the public). That being said, they're both fine solutions and are in use in a number of large enterprises (goog, etc.)...the key is to be automating your operations in some manner. Hell...use both and see which aspects are / are not important to you / your people.
Re:Introducing AWS OpsWorks, a Powerful AWS Application Mana...
by bryanwb on Tuesday February 19, 2013 @08:18AM
(#5244055)
here is my view on the topic http://devopsanywhere.blogspot.it/2011/10/puppet-vs-chef-fig...
Re:Introducing AWS OpsWorks, a Powerful AWS Application Mana...
by makerbreaker on Tuesday February 19, 2013 @09:36AM
(#5244460)
"Chef's Data Bags are incredibly useful." Very true. Not having to deal with a DSL (which is a personal opinion) is the reason I chose chef over puppet. Plus the IRC channel seems to be more active.
Is the AWS opswork link broken for anyone else? I tried to view their pricing/sign up, but received 404's.
Re:Introducing AWS OpsWorks, a Powerful AWS Application Mana...
by mpdehaan2 on Tuesday February 19, 2013 @10:04AM
(#5244621)
I like data driven stuff. Though there's still a DSL. This is a large reason why I made http://ansible.cc, as I wanted the actual description of the policy to be data as well.
It'd pretty interesting to also know why Amazon went with chef first.