On Fri, May 25, 2012 at 09:27:39AM -0700, Jagga Soorma wrote: > Hi Guys, > > I currently manage all patching (and rpm installs) of RHEL 5 servers via our > internal RHN Satellite server. However, due to funding and other reasons, we > are trying to save $$ and would prefer not to purchase management licenses for > our RHN Satellite server. I was wondering how other folks out there are > managing their RHEL servers? > > What I am thinking of doing is only having a few licenses for my Satellite > server and then using reposync to create manual repositories on a physical > server (by extracting the rpms from RHN channels on our internal satellite) > and > have the clients register to these repositories instead of the satellite > server. This way I would have the same patches and cut on the cost of > purchasing management licenses for our Satellite server. Do you see any > downside to this approach? Are others doing something similar? I have a > growing environment of about 500 RHEL servers. > > Also, I only use the internal RHN Satellite server for patching and nothing > else (no provisioning, kickstart files etc - done elsewhere). > > Thanks in advance for your assistance,
What you describe will work, but why not just ditch Satellite entirely then and reposync against RHN directly? As long as you're paying for your entitlements for each RHEL instance I think you should be good (but recommend you check w/ your account rep first of course). Alternaetly you could also do the reposync/mrepo thing against RHN and then slurp it up into Spacewalk and register your RHEL hosts there. This would give you a near-Satellite experience sans support[1] Ray [1] Note I'm not 100% sure you *can* register RHEL hosts to Spacewalk. I think you can... _______________________________________________ rhelv5-list mailing list rhelv5-list@redhat.com https://www.redhat.com/mailman/listinfo/rhelv5-list
