4 ms·
As cool as they are, I have 2 problems with Chef/Puppet/CFengine/Rightscripts. 1. Long boot times. This gets worse as your recipes get beefier. 2. Same script
by shykes 17y ago
As cool as they are, I have 2 problems with Chef/Puppet/CFengine/Rightscripts.
1. Long boot times. This gets worse as your recipes get beefier.
2. Same script, different results. Running your recipe next year might not yield the same result (e.g. if you don't specify a precise version of a package to install).
- dylanz 17y ago1. Quite true 2. I think it's always important to be explicit about, and have backups, of the packages used in these scripts.
- mark_l_watson 17y agoI agree. I do use Chef and Capistrano to automate creating AMIs, but then I like to just save the AMIs and boot from them. Also, creating a new AMI from an old one is quick and easy.
- moted 17y ago1. This is certainly true, but hopefully we can find a good way to combine the benefits of booting from EBS and having a fast root partition, with that of the agility of Chef/RightScript model, to decrease boot times. 2. You can version server templates to use specific revisions of RightScripts and recipes. In fact, the Chef implementation is built around using a branch or commit SHA1 to specify what versions of the recipes you want to use from your repository. disclaimer: I work for RightScale