5 ms·
I dug into to this looking for some greater insight, but found the article a bit lacking. I looked into the both of them for managing a couple of personal mach
by dmayle 14y ago
I dug into to this looking for some greater insight, but found the article a bit lacking.
I looked into the both of them for managing a couple of personal machines, and decided against Chef because of the very heavy stack.
What I found really lacking, however, was the bootstrap process. I want a way to provision a machine from the ground up, automated installation, followed by insertion into the managaed network, and then management following my policies.
Trying to get this into place was quite difficult, and I'm currently stalled in my project. Does anyone have any insights?
- ashayh 14y agoNot sure where you are stuck, but maybe Foreman can help? http://theforeman.org/ http://theforeman.org/ . It does VM (and bare-metal) creation, DNS, DHCP, PXE, Kickstart and then Puppet.
- cmer 14y agoI recently released a very lightweight Bash-based alternative. Check it out, it might float your boat: https://github.com/cmer/shoestrap https://github.com/cmer/shoestrap
- bryanwb 14y agoI have been able to automate that whole process but it is hard for me to give specific feedback w/out knowing more about your infrastructure. Come find me or other helpful Cheffolk on #chef at irc.freenode.net or the mailing list lists.opscode.com Also, you may want to check out FoodFight, the bi-weekly Chef Community podcast http://foodfightshow.org http://foodfightshow.org
- jrussbowman 14y agoI'll be doing a follow up blog once I'm done building our deployment process for Chef in house. However, I'm not sure you're saying you've already ruled that out and are looking at Puppet instead? So what I come up with may not be very helpful. I think the general gist for both Chef and Puppet is you'll need to build the machine, build Chef/Puppet and their dependencies, then you can automate the rest of the build using them.