<div dir="ltr">Just speaking for myself here, but when Red Hat converged on Puppet (~2011?), we went all-in on that so we're a Puppet shop. We didn't expect Red Hat to go flipmode on us and buy Ansible 3 years later. So I'm only interested in Puppet right now :)</div><div class="gmail_extra"> <div class="gmail_quote">On Thu, Dec 8, 2016 at 2:29 PM, Dennis Kliban <<a href="mailto:dkliban@redhat.com" target="_blank">dkliban@redhat.com</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Have you considered using Ansible? I noticed that jtyr has published a role[0] on Ansible Galaxy that allow users to manage Pulp repos. The same person has published a role[1] for deploying Pulp. [0] <a href="https://galaxy.ansible.com/jtyr/pulp_repos/" rel="noreferrer" target="_blank">https://galaxy.ansible.com/jtyr/pulp_repos/</a> [1] <a href="https://galaxy.ansible.com/jtyr/pulp/" rel="noreferrer" target="_blank">https://galaxy.ansible.com/jtyr/pulp/</a> -Dennis <div class="HOEnZb"><div class="h5"> ----- Original Message ----- > I'm all for it. I won't be able to contribute much, but would be down to > test. > > The biggest thing I'd like would be to have repo definitions definable in > Hiera something like this: > pulp_server::repositories: > rhel-7-server: > feed: <a href="https://cdn.redhat.com/content/dist/rhel/server/7/7Server/x86_64/os" rel="noreferrer" target="_blank">https://cdn.redhat.com/content/dist/rhel/server/7/7Server/x86_64/os</a> > proxy_host: <a href="http://proxy.college.edu" rel="noreferrer" target="_blank">http://proxy.college.edu</a> > proxy_port: 8080 > relative_url: rhel-os/server/7Server/x86_64/os/ > serve_http: true > feed_ca_cert: /etc/rhsm/ca/redhat-uep.pem > feed_cert: /etc/pki/entitlement/somecert.pem > feed_key: /etc/pki/entitlement/somecert.pem > remove_missing: true > retain_old_count: 4 > > yadda yadda. > > It would be important for this Puppet module to not mess with stuff not > defined in puppet, so that it could coexist with other interfaces to Pulp > such as Katello and CLI interaction w/ Pulp. > > My $0.02 > > - Kodiak Firesmith > > On Thu, Dec 8, 2016 at 1:28 PM, Baird, Josh < <a href="mailto:jbaird@follett.com">jbaird@follett.com</a> > wrote: > > > > > > Is anyone here managing things like repository definitions, schedules, > parent/child relationships, etc with Puppet? > > > > I’m considering working on extending the katello/puppet-pulp [1] module to > handle these types of things, but didn’t want to re-invent the wheel if the > work has already been done. > > > > [1] <a href="https://github.com/Katello/puppet-pulp" rel="noreferrer" target="_blank">https://github.com/Katello/puppet-pulp</a> > > > > Thanks, > > > > Josh > > > > _______________________________________________ > Pulp-list mailing list > <a href="mailto:Pulp-list@redhat.com">Pulp-list@redhat.com</a> > <a href="https://www.redhat.com/mailman/listinfo/pulp-list" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/pulp-list</a> > > > _______________________________________________ > Pulp-list mailing list > <a href="mailto:Pulp-list@redhat.com">Pulp-list@redhat.com</a> > <a href="https://www.redhat.com/mailman/listinfo/pulp-list" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/pulp-list</a> </div></div></blockquote></div> </div>