Pulp

The new 'ansible-pulp' repository should be created by following the guide[0] from Ansible Galaxy. The 'pulp' ansible role defined in pulp_packaging[1] CAN be used as the basis for the new 'pulp' role.

The new 'pulp' role should only install Pulp and it's dependencies. This EXCLUDES the message broker and the database. The new role should use parameters to determine which Pulp services should be made available on the host. The default behavior is to enable all the services.

The README should provide an example playbook that uses the new 'pulp' role in combination with 'mongodb' and 'qpid_cpp_server' to deploy Pulp on a single machine.

Once this repository is ready, it should be published on Ansible Galaxy.

Please not that there is already a pulp Ansible role[2] available on Ansible Galaxy. It is most likely less work to fork this repository instead of using ours as the basis.

The existing role does depend on other roles[3-6] authored by the same person. We should decide if we want to fork all of these.

[0] https://galaxy.ansible.com/intro#share
[1] https://github.com/pulp/pulp_packaging/tree/master/ci/ansible/roles/pulp
[2] https://galaxy.ansible.com/jtyr/pulp/
[3] https://github.com/jtyr/ansible-mongodb
[4] https://github.com/jtyr/ansible-yumrepo
[5] https://github.com/jtyr/ansible-qpid_cpp_server
[6] https://github.com/jtyr/config-encoder-macros