Re: [Pulp-list] [devel] Create a `devel` repository for Pulp
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 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@redhat.com > https://www.redhat.com/mailman/listinfo/pulp-list > ___ Pulp-list mailing list Pulp-list@redhat.com https://www.redhat.com/mailman/listinfo/pulp-list
Re: [Pulp-list] [devel] Create a `devel` repository for Pulp
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 signature.asc Description: OpenPGP digital signature ___ Pulp-list mailing list Pulp-list@redhat.com https://www.redhat.com/mailman/listinfo/pulp-list
Re: [Pulp-list] [devel] Create a `devel` repository for Pulp
On 06/20/2016 01:49 PM, Jeremy Cline wrote: > Hi all, > > Currently, we have development-related files and packages spread out > across our Git repositories on GitHub. It would be nice if it was all > part of one repository for developers. This would include things like: > > * The Vagrantfile currently in pulp/pulp > * The devel Python packages currently in each repo > * Release engineering tooling currently in pulp/pulp > * Jenkins jobs definitions currently in pulp/pulp_packaging > * Ansible playbooks currently in pulp/pulp and pulp/pulp_packaging > * Various tools and scripts living in "playpens" > > It might also be worth breaking out our Ansible roles into their own > `ansible` repository. Right now we have _two_ sets of Ansible roles > (one in pulp/pulp and on in pulp/pulp_packaging). > > What do you all think? 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. +1 for 'devel' and not 'pulp_devel', I still sometimes think that we have a 'packaging' plugin because of the 'pulp_packaging' repo name. signature.asc Description: OpenPGP digital signature ___ Pulp-list mailing list Pulp-list@redhat.com https://www.redhat.com/mailman/listinfo/pulp-list
[Pulp-list] [devel] Create a `devel` repository for Pulp
Hi all, Currently, we have development-related files and packages spread out across our Git repositories on GitHub. It would be nice if it was all part of one repository for developers. This would include things like: * The Vagrantfile currently in pulp/pulp * The devel Python packages currently in each repo * Release engineering tooling currently in pulp/pulp * Jenkins jobs definitions currently in pulp/pulp_packaging * Ansible playbooks currently in pulp/pulp and pulp/pulp_packaging * Various tools and scripts living in "playpens" It might also be worth breaking out our Ansible roles into their own `ansible` repository. Right now we have _two_ sets of Ansible roles (one in pulp/pulp and on in pulp/pulp_packaging). What do you all think? -- Jeremy Cline signature.asc Description: OpenPGP digital signature ___ Pulp-list mailing list Pulp-list@redhat.com https://www.redhat.com/mailman/listinfo/pulp-list
