Package upgrade - how to organize ?

[New user]

Hello,

we slowly are trying to get into Puppet world. So far we have basic configuration for a few hosts.
In the next step I'd like to get automatic packages upgrade (CentOS/RH) on each Puppet-managed server but since
there are first (the most important), second (little less important), third, testing  line of servers
I would like to upgrade packages on testing servers then (a week later) on third line of server then (another week later)
second and so on. Could you recommend how to approach this problem ?

[Jakov Sosic]

I'm also interested in this one...

You could use strict version adherences in your manifests (package
{blah: ensure => 'version', }), and use different environments on
different line of servers.

But the problem I see with this approach is that only packages
explicitly defined in your manifests will get upgraded, and just *part*
of their dependencies. For example centos-release package won't be
upgraded ever.

So if anyone has any better approach in automating upgrades I would be
more than interested too...



--
Jakov Sosic
www.srce.unizg.hr