[Spacewalk-list] Best practices for Yum Repo

[Snyder, Chris]

In my environment, I'm doing option 1.  I've got my mrepo/yum repos on the same file system as my spacewalk filesystem.  After every round of updating mrepo and Spacewalk,  I run 'hardlinks' which results in only one physical copy per RPM on the file system.

From: spacewalk-list-bounces at redhat.com [mailto:spacewalk-list-bounces at redhat.com] On Behalf Of Sam Sen
Sent: Wednesday, February 06, 2013 2:22 PM
To: spacewalk-list at redhat.com
Subject: [Spacewalk-list] Best practices for Yum Repo

What's the best practices for handling software channel? I'll give two examples, the first is how I'm handling things now for archaic reasoning within our infrastructure. What I'm trying to accomplish is to allow non-spacewalk clients to query the yum repos. I want Spacewalk to handle OS/software patches along with yum repository management.


1)      Download yum repos to a centralize internal yum repo. Any client within our network can get to the repos we set up. Spacewalk syncs the selected repos from our yum repo server. The con is, we have duplicate packages on two systems.

2)      Sync all external yum repos we care for into the spacewalk server. This way we can get rid of the other yum repo and have packages in one central location.

Thanks

Sam
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20130207/ee8f7452/attachment.htm>