Greetings,
I've deployed a few solutions involving Puppet in my professional
past, and always found upgrades to be somewhat non-trivial.
Transitioning from 0.24.x to 0.25.x was quite difficult due to some
fairly big structural changes. In general upgrading the puppetmaster
is easily achieved, being a single central box managed day-to-day by
my team, however slinging all of the nodes which are managed onto a
new version is decidedly less easy.
What techniques and tricks have people developed to aid this process?
For the current solution I'm deploying there will be a need to manage
a veritable cornucopia of different systems, including --
* HP-UX
* RHEL 5.3 -> 6.0
* Debian 'Lenny'
* Ubuntu 10.04 LTS
Is there a good way to handle clients which may be running slightly
different versions of Puppet? Following on from that thought, in
addition to the interaction between client and server, does anyone
have a good way to run test cases against manifests to ensure they'll
work on all the clients we may be running?
I would prefer, where possible, to avoid maintaining our own package
repositories for all the distributions we manage, and would prefer to
use repositories provided by the vendor where practical.
Many Thanks,
Alex
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
