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. > > But I think for a true split of responsibilities Cobbler would need to > support the distribution's repository being external. If you manually adjust > the Kickstart Metadata in the Cobbler's profiles you could probably > accomplish this, but cobbler would still need a source for the kernel and > initrd in the PXE environment to be defined in the profile.. > > I cross posted this to the cobbler list. > > -greg > > On Wed, Oct 26, 2011 at 10:59, Dan White <[email protected]> wrote: > So how then do I mix the two ? > > “Sometimes I think the surest sign that intelligent life exists elsewhere in > the universe is that none of it has tried to contact us.” > Bill Waterson (Calvin & Hobbes) > > ----- Phil Gardner <[email protected]> wrote: > > I am actually just now setting up a similar environment. From what I can > > tell, Pulp is better at managing repos with keeping track of package > > versions, and can push updates out to the consumers without actually > > interacting with the server (consumer). > > > > I have been testing with adding a second non-ssl vhost to Pulp's apache > > and using that url as the install/updates repos when kickstarting > > (inside cobbler kickstart templates). Or you could just import the base > > install trees into cobbler and just use that for installs. Each would work. > > > > Any other important differences between the two? Some of their > > functionality does overlap, but pulp is better at dealing with lots of > > repos, and cobbler is great for managing kickstart stuff. > > > > On 10/26/2011 11:40 AM, Dan White wrote: > > > I have a Cobbler/Puppet/Kickstart environment I am running with, but I am > > > running into problems maintaining a local set of repo mirrors. > > > > > > Is it possible to roll Pulp into this mix ? > > > > > > “Sometimes I think the surest sign that intelligent life exists elsewhere > > > in the universe is that none of it has tried to contact us.” > > > Bill Waterson (Calvin & Hobbes) > > > > > > _______________________________________________ > > > Pulp-list mailing list > > > [email protected] > > > https://www.redhat.com/mailman/listinfo/pulp-list > > > > -- > > _____________________ > > Phil Gardner > > PGP Key ID 0xFECC890C > > OTR Fingerprint 6707E9B8 BD6062D3 5010FE8B 36D614E3 D2F80538 > > > > _______________________________________________ > > Pulp-list mailing list > > [email protected] > > https://www.redhat.com/mailman/listinfo/pulp-list > > > _______________________________________________ > Pulp-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/pulp-list >
_______________________________________________ Pulp-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-list
