3 ms·
As someone who has written utilities to check for configuration changes presented by packages systems when they update, glossing over this issue is a bad idea.
by kbenson 13y ago
As someone who has written utilities to check for configuration changes presented by packages systems when they update, glossing over this issue is a bad idea.
Having a unified configuration that you can track and push is good, but if you are installing from RPM or DEB, you want to know if the package is pushing a new config itself, or providing a new config for review.
The utility I wrote looked for .rpmnew and .rpmsave save files and checked with a central repo for whether they were whitelisted (by MD5) or not. Anything not whitelisted resulted in mail being sent alerting admins. Along with an fairly comprehensive per-host auto-update exclude list (which I got yum-autoupdate patched upstream to allow), this allowed us to be fairly confident in allowing our 100+ boxes to auto update every day.
Without paying close attention to packages release notes, interesting things can come down from the maintainers, usually from them back-porting a fix from a later version (or a feature, if it's a RHEL point release).
I think configuration management is a good thing, but I'm not sure it's the best thing to be taught first, unless there's mentors to work with. Some things you just won't think of until it's bit you in the ass, and have that bite be at small scale until you've figured it all out is probably a good thing.
- falcolas 13y agoTo address just the package concern, it's worth noting that Ansible can pin packages to a particular version, by naming the version you want installed. Then, even if a new package is pushed to the repo, you will not receive it (and will be notified by an error by subsequent runs if it's been manually updated) until you update the inventory file. Many things in Ansible can be pinned in similar ways. http://www.ansibleworks.com/docs/modules.html#yum http://www.ansibleworks.com/docs/modules.html#yum
- mpdehaan2 13y agoI'd also highly recommend maintaining a local mirror, regardless of your CM system. Makes things faster and ensures even if you don't pin versions you are not going to get upstream surprises.