On Tue, Mar 20, 2012 at 09:09, Miles Fidelman <[email protected]>wrote:
> What I keep coming back to is that they seem like overkill for what I'm > doing right now - and carry with them the need to: > - install a layer of infrastructure > - work in yet another language (bash and sed do pretty much all I need, > why have to wade through recipes written in Ruby or Python or whatever)? > - do I really need to deal with lots of recipes to ultimately execute a > few install and config. statements (who really needs the overhead to > execute "apt-get install" or "./configure; ./make; ./make test, ./make > install") - at least for the stuff I'm managing now, the details are in > site-specific configurations, and it seems like a lot of getting that right > with Chef (or whatever) involves wading into and understanding how the > individual recipes work (or writing them) > Yes, it's overkill for small environments --- but going back and adding it after you've grown is a much larger job than setting it up to begin with, and it's not especially common to be able to reliably say that you are unlikely to grow into the situations where you need this. It just seems to be the nature of our profession that small, simple setups grow and become more complex and you find yourself needing better tools. -- brandon s allbery [email protected] wandering unix systems administrator (available) (412) 475-9364 vm/sms
_______________________________________________ Tech mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
