On Wed, Nov 12, 2014 at 7:42 PM, Edward Ned Harvey (lopser) < lop...@nedharvey.com> wrote:
> I would build a system, perhaps on AWS, Vmware, whatever. Get it > configured and working. And then tell some tool to basically snapshot that > machine's configuration, including list of packages installed, and their > configurations, and all the other stuff that defines the machine state... > In most of my environments, I have some ability to actually snapshot the > machine storage, and then spin up clones of the machine. But I have to > keep a documented procedure of how the original config was created, so it's > not magic "special sauce." But snapshotting & cloning the storage is > undesirable because it is not portable. I'd like to build a VM on my local > vmware or virtualbox or whatever, and then essentially clone it to AWS or > vice versa... Make some change on a development machine, test it, and then > after it's validated, replicate that change to the production environment > by sending essentia > lly the snapshot differential of the configuration. > > For some reason, this is what I thought puppet/chef/etc did. Am I wrong? > Is this a pipe dream? > It's not possible, because there are far too many things you could change *and* far too many ways that those changes might be applied to something which is in any way different (hardware settings, for example; even if it's VM to VM, don't bet on an AWS emulated network card being identical to VMware's). -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
_______________________________________________ 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/
