On Fri, Nov 14, 2014 at 3:44 PM, Edward Ned Harvey (lopser) <lop...@nedharvey.com> wrote: >> From: Phil Pennock [mailto:lopsa-t...@spodhuis.org] >> >> If you want to build manually, then snapshot: Docker >> can be used in vmware or virtualbox or AWS or whatever: Packer
> > I don't really understand the use case of frequent spinning up machines - > except in a few circumstances, such as to create a pristine QA environment > for testing some development code. I mostly agree with this sentiment and the rest of your note as well. Configuration management is clearly useful when you have lots of machines and/or have to frequently recreate a pristine environment. However, it has never made sense to me for small environments which aren't going to grow. (Yes, they do exist.) I've only come up with one reason to do CM for small installations: disaster recovery. With backups of your CM details and "user" data, it is going to be much easier to recover after a disaster. Whether the "cost" of doing CM is worth incurring for this benefit has been unclear to me. I've also looked at etckeeper as an alternative to CM systems for disaster recovery. Unfortunately, it only covers /etc. Athough you can clone systems with it, you are left with manually making all the changes required to differentiate the clone from the original. Still, you might take a look at it and see if it helps you. Bill Bogstad _______________________________________________ Tech mailing list Tech@lists.lopsa.org https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
