|So, if I understand the patterns (I'm new to using producer/consumer patterns),|
I set up a Pulp Server to manage the mirror-repositories (producer)
and point the Cobbler Server at them (as a client/consumer) and let Cobbler feed out the RPM's to the cobbler-ized client-hosts.
This sounds very do-able !
I have a repo on my Cobbler server of RPM's that are not from another repo, so I have to run "createrepo" manually whenever I update the collection. The client-hosts connecting thru Cobbler pick up the changes.
OK, one more question: I'm using Red Hat Enterprise Linux 5. Can I still register these client-hosts with Red Hat Network ? I recently encountered a problem with Cobbler-generated yum mirror-repositories and the yum-rhn-plugin not playing nice together.
On Oct 26, 2011, at 1:29 PM, Greg Swift wrote:
As Phil said, the easiest mix would probably be to create all of the repos in Pulp and just define them as external repos in Cobbler.