Chris, thank you for the reply. We had the same kind of setup in mind - download all packages to the satellite server, and use Puppet to manage which packages are installed on the different systems. And using the satellite''s channel utility we will have full control over which patches/upgrades are available to the managed environments (testing, production, etc). Kenneth ------------------------------ Message: 5 Date: Tue, 29 Jan 2008 11:21:52 -0500 From: "Chris MacLeod" <stickm@gmail.com> Subject: Re: [Puppet-users] (no subject) To: "Puppet User Discussion" <puppet-users@madstop.com> Message-ID: <426cef8e0801290821g5ef372fr32a84cd1a0baec60@mail.gmail.com> Content-Type: text/plain; charset="iso-8859-1" I''m doing that exact thing and no there isn''t a document (that I know of) on the subject. I will probably have on when I''m done but not at this time. The way I handle the interaction is my provisioning tool (cobbler) does os install and basic puppet bootstapping as well as satellite registration. puppet handles all the package installations but no where does it specify versions etc. I use ensure => installed everywhere rather than ensure => latest or ensure => $version. I basically use the satellite as a package store. On 1/29/08, Holter, Kenneth <Kenneth.Holter@nav.no> wrote:> > Hi. > > I posted this question on the RedHat Network mailing list, but not too > many people seem to have much experience with Red Hat Network andPuppet.> Maybe someone here can give me some advise on the following: > > I''m planning to use both RHN Satellite server and Puppet to manage our > medium size network of RHEL 4 and 5 servers. > Does anyone have any experience with this kind of management setup?And> does there exists some kind of best practice document on this subject? > > Regards, > Kenneth Holter > > _______________________________________________ > Puppet-users mailing list > Puppet-users@madstop.com > https://mail.madstop.com/mailman/listinfo/puppet-users > >