On Thu, Sep 23, 2010 at 12:34 PM, Ohad Levy
mailto:ohadl...@gmail.com>> wrote:
I can also recommend using frozen repos, with a testing cycle every time you
update them...
I a while ago I wrote a small web app[1] to collect all versions of all
packages across all of your hosts, you might find it
On Sep 22, 2010, at 14:06 , Leslie Giles wrote:
> I'm working on rolling out Puppet, but I'm stuck and I know somebody has
> solved this problem...
>
> We have an engineering environment of around 200 Centos servers, plus a
> production environment of roughly the same size. Currently, when we r
On Thu, Sep 23, 2010 at 12:34 PM, Ohad Levy wrote:
> I can also recommend using frozen repos, with a testing cycle every time
> you update them...
> I a while ago I wrote a small web app[1] to collect all versions of all
> packages across all of your hosts, you might find it useful to know which
I can also recommend using frozen repos, with a testing cycle every time you
update them...
I a while ago I wrote a small web app[1] to collect all versions of all
packages across all of your hosts, you might find it useful to know which
package is installed on which server... in anycase, if you fr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Has anybody else been faced with this problem, and if so, how did you
> resolve it?
use Spacewalk for patch management. At least at your scale this makes
sense. It makes manual repository management a lot easier.
cheers pete
-BEGIN PGP SIGNATUR
On Wed, 22 Sep 2010, Leslie Giles wrote:
We have an engineering environment of around 200 Centos servers, plus a
production environment of roughly the same size. Currently, when we roll out
a new server, we do a 'yum update' so the new server has the latest
packages; however this means that just
Hi Lezz,
Another approach is to maintain your own repos by freezing them over time,
e.g. monthly pull the latest packages for your repos and put them as your
frozen repo, provide these frozen repos through puppet and once you have
validated all the updates in the frozen repos you can relase those
On Sep 22, 2010, at 8:06 AM, Leslie Giles wrote:
> We have an engineering environment of around 200 Centos servers, plus a
> production environment of roughly the same size. Currently, when we roll out
> a new server, we do a 'yum update' so the new server has the latest packages;
> however thi
I'm working on rolling out Puppet, but I'm stuck and I know somebody has
solved this problem...
We have an engineering environment of around 200 Centos servers, plus a
production environment of roughly the same size. Currently, when we roll out
a new server, we do a 'yum update' so the new server
