[Pulp-dev] Puppet setup on prepare_node script (pulp_packaging)
bbouters at redhat.com
Tue Jan 3 16:35:56 UTC 2017
+1 to pulling out puppet to unblock the builds.
+1 to replacing any puppet usage with Ansible, which is consistent with the
After digging around in git some, it looks like those puppet lines were
originally added in 2015 with this commit. That commit both installs
puppet and runs some `puppet apply ...` statements, so pulling puppet out
should be fine as long as those `puppet apply` statements get replaced with
something else (either Ansible, or $ANOTHER_IDEA).
Thank you for raising this and whatever you can do on it.
On Mon, Jan 2, 2017 at 9:58 AM, Elyezer Rezende <erezende at redhat.com> wrote:
> The prepare_node script is responsible to prepare the nodepool nodes we
> use on Jenkins. Other than installing basic packages and the machinery to
> make the node a Jenkins slave it installs puppet .
> I am wondering why setting up puppet is needed since it seems to be
> related to the unittest jobs only. I am wondering that because there is no
> Puppet for Fedora 25 yet  and that is blocking us to have Fedora 25
> nodes since they can't be built.
> With all that said, I have some questions:
> 1) Can we drop puppet setup and let the jobs that need it to set it up?
> 2) Can we move away from Puppet to Ansible? If yes, what needs to be done
> to have that?
> I am raising this up because I want to test Pulp ASAP on Fedora 25 and I
> don't know all the details about the Puppet need on the slaves.
> Thank you
>  https://github.com/pulp/pulp_packaging/blob/master/ci/
>  https://yum.puppetlabs.com/
> Elyézer Rezende
> Senior Quality Engineer
> irc: elyezer
> Pulp-dev mailing list
> Pulp-dev at redhat.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pulp-dev