This might give you a starting point. It's pitched as a full-stack, lightweight config management solution, but it can also do some light reverse-engineering on systems and generate a Chef cookbook as the output. Thanks, --Charles -- Charles Johnson Solutions Engineer - Opscode, Inc. (510) 545-9485 - Direct Line
From: Mike Dillion <
">
> Reply-To: " "> " < "> > Date: Tuesday, April 23, 2013 6:44 AM To: " "> " < "> > Subject: [chef] Chef on existing infrastructure/nodes Hey y'all,
I heard something on a Puppet Labs podcast* recently that gave me a pause for though: developing cookbooks (manifests in Puppet?) against production machines as a way of migrating to a coded infrastructure. i.e. instead of starting from scratch and attempting to duplicate current infrastructure, slowly adding pieces (automating processes) to cookbooks in order to gain immediate benefits. Are there any patterns for this? Does anyone have any experience, good or bad? I thought it was interesting at the least. Cheers, Mike Dillion |
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
Archive powered by MHonArc 2.6.16.