On 04/20/2014 02:38 AM, Jasmine Lognnes wrote:
Dear all =)
I have a CentOS5 node that I would like to upgrade to CentOS6, but how
can I trust that my CentOS5 node manifest won't destroy the config files
on the CentOS6 node because the config files have changed from CentOS5
to CentOS6?
How do you prevent this kind of situation? Do you make a copy of all the
CentOS5 config files and diff them with the CentOS6 ones? If, how do you
do that in an automated way?
You can use facter variables to control which for example template you
will use depending on the major version of OS.
Similar issue can be observed with versions of software - for example if
you try to manage Zabbix, there are versions 1.8, 2.0, 2.2 and soon
there will be 2.4. With Cobbler for example, there is 2.2 and 2.4.
The way I do it is to test new version in a dev environement and rewrite
modules/templates with version-aware configs as needed... It's an
unpleasant task, but on the upside it has to be done only once.
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/53539671.2090802%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
