The ability to assign consumers to groups would be nice as well. I don't know how this functionality works with the consumer client. I'm curious how Sat6's "katello-agent" (the pulp-consumer client plus a few more things) will be deployed as well.
Josh -----Original Message----- From: Steven Roberts [mailto:[email protected]] Sent: Monday, November 11, 2013 12:34 AM To: Baird, Josh Cc: [email protected] Subject: Re: [Pulp-list] Automating the deployment of pulp-consumer On Mon, Oct 21, 2013 at 08:11:44PM +0000, Baird, Josh wrote: > Hi, > > Is anyone currently deploying the pulp-consumer client and > registering/binding to repos in an automated fashion? I was surprised > to see that there was not a Puppet module out on Forge for this > already. I do see a module on github: > > https://github.com/KrisBuytaert/puppet-pulp > > While this module does install the pulp-consumer client, it doesn't > do anything beyond that like registering to the Pulp server or binding > to repositories. I would think that this would be somewhat of a > standard procedure for those running Pulp, but maybe not? I am not depoying pulp via puppet currently, but was actually going to be looking into that shortly. Getting ready to start moving pulp into a more general use and that means deploying it via puppet. So pretty good timing on your email. I took a look at the module, and like you does look like a good start, but not complete. What sort of things would you want the module to do? you mentioned registering to the pulp server and binding to repos. Been trying to think of other items that would be good for a puppet module for pulp to do (at least from a consumer perspective) and figured check to see if you had additional ideas... Steve P.S. kudos to the pulp dev's. 2.2 is much faster and better on memory usage during repo syncs. _______________________________________________ Pulp-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-list
