On 19.05.2015 16:37, Stephen Harris wrote: > On Tue, May 19, 2015 at 09:25:30AM -0500, Jim Perrin wrote: >> If you have a good config management environment set up, rolling out a >> new build to replace older systems is much easier than walking through >> an update on each system. I really recommend people use ansible, chef, >> puppet.. whatever they're comfortable with to do some basic automation. > > Just do lots of testing, first :-) There are sufficient differences > between major OS releases (5, 6, 7) that you may need different rules > for each type. > > For example, postfix is different version on each so main.cf and master.cf > are different and have version specific differences. > Apache is sufficiently the same between 5 and 6, but 7 has a totally > new way of doing things > And, of course, sysvinit vs upstart vs systemd! > > Config managementis a great way of rebuilding a new copy of an existing > version, but it's not a panacea when changing versions. It's a good way to keep track of what makes your system unique though. Kind off a diff between the core installation and the final production system. For a lot of people it seems the biggest problem is to identify what they need to migrate to get things running again and adapting that to new versions is actually that that big an issue. Sure you remember to copy /etc/httpd but did you also copy that script you wrote that tweaks some queue settings in /sys or that maintenance script that you stored under /usr/local or /opt or wherever that you haven't had to use in a year? If you have the discipline to put all that into a configuration management system then you don't have to search for these things. Regards, Dennis