On 8/3/12 4:35 PM, Peter Conerly wrote:
I'm getting the feeling that my event might not happen. (Well, it'll
still happen, but it's going to be a one-person event :D ) The reason I
decided on a workday is that I really think it's going to take that long
to get a Chef cookbook that'll do everything a person needs. (I also
chose a workday because, hey, Chef is a really good skill for an
employee to have. Your employer should be fine with you taking a day to
learn.)
Also, some of you are wondering why you should learn Chef (rather than
another framework). I went to the last deployment meeting and it was
pretty clear that Chef is the framework with the most maturity and
community support. That means that there are going to be a lot of
pre-written Chef scripts that we can just grab and not worry about as much.
The key quotes from the deployment meeting was: "just pick a deployment
system and go with it" and "Every week you put off implementing a
deployment system makes for a more painful transition".
i think puppet and chef are basically equal in terms of maturity and
community (puppet has been around a bit longer than chef), so you can't
go wrong with either. however, one might be slightly better than the
other for your specific stack. i would start there, by reading the
puppet/chef code already out there for managing your stack, and pick the
one that looks better.
-Michael
