I took an initial stab at a pulp puppet module here: http://forge.puppetlabs.com/hawknewton/pulp.
At the moment it doesn't try to do any kind of registration, but it might be a good place to start. -- H On 11/11/2013 12:34 AM, Steven Roberts wrote: > 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. I'm also interested in the automated registering/binding with puppet. I've been thinking a lot about this recently, especially since I am going to need to register/bind several hundred VMs that already exist but are not currently registered to the pulp server. Its relatively easy to do at the deploy/kickstart process, but for the hosts already running, I was thinking of doing some hacky parsing of the output of 'pulp-consumer status' to find out if it has been registered already. The binding can obviously be scripted out on the pulp server later. I also thought of using the same certs that puppet is using (like we do with func) so it possibly wouldn't have to actually register to the pulp server/pupetmaster, but I guess when you register a system, it populates a document in mongodb. -- _____________________ 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
