[Pulp-list] [devel] Create a `devel` repository for Pulp

[Jiri Tyr]

If you want to make the Ansible role reusable, I recommend to put it into a
separate Git repository and make it available via Ansible Galaxy. I also
recommend do make it more atomic (one role for Pulp, one role for MongoDB
and one role for Qpid). The role should also take advantage of existing
Ansible modules (e.g. package, yum_repository, ...).

I have created such role myself and made it available on GitHub:

https://github.com/jtyr/ansible-pulp

Best regards,
Jiri


On Mon, Jun 20, 2016 at 7:55 PM, Jeremy Cline <jcline at redhat.com> wrote:

> On 06/20/2016 02:40 PM, Sean Myers wrote:
> > Yes. I'm also happy to see the ansible books live in devel since they're
> primarly
> > used by vagrant and CI, which would both live in devel, and you can't do
> either
> > without one or the ansible playbooks.
>
> I was thinking that maybe we should consolidate the roles and package
> them for Ansible Galaxy[0]. Just to be clear, the roles are reusable
> and live in the `roles` directory[1]. The playbooks[2] describe what
> roles should be applied to which host and are particular to our
> development environment.
>
>
> [0] https://galaxy.ansible.com/
> [1] https://github.com/pulp/pulp/tree/master/playpen/ansible/roles
> [2]
>
> https://github.com/pulp/pulp/blob/master/playpen/ansible/vagrant-playbook.yml
>
> --
> Jeremy Cline
>
>
> _______________________________________________
> Pulp-list mailing list
> Pulp-list at redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-list/attachments/20160620/0b38d8d7/attachment.htm>