Nice! I don't have a strong opinion about this but what I might recommend would be to chat with the openshift-ansible [1] and the kolla-ansible [2] folks.
I'm happy to do the introductions if necessary ! Their models, requirements or context might be different than ours but at the end of the day, it's a set of Ansible roles and playbooks to install something. It would be a good idea just to informally chat about the reasons why their things are set up the way they are, what are the pros, cons.. or their challenges. I'm not saying we should structure our things like theirs. What I'm trying to say is that they've surely learned a lot over the years these projects have existed and it's surely worthwhile to chat with them so we don't repeat some of the same mistakes. Generally just draw from their experience, learn from their conclusions and take that into account before committing to any particular model we'd like to have in TripleO ? [1]: https://github.com/openshift/openshift-ansible [2]: https://github.com/openstack/kolla-ansible David Moreau Simard Senior Software Engineer | Openstack RDO dmsimard = [irc, github, twitter] On Thu, Mar 29, 2018, 12:34 PM David Peacock, <dpeac...@redhat.com> wrote: > Hi everyone, > > During the recent PTG in Dublin, it was decided that we'd prototype a way > forward with Ansible tasks in TripleO that adhere to Ansible best > practises, creating dedicated roles with unique git repositories and RPM > packaging per role. > > With a view to moving in this direction, a couple of us on the TripleO > team have begun developing tooling to facilitate this. Initially we've > worked on a tool [0] to extract Ansible tasks lists from > tripleo-heat-templates and move them into new formally structured Ansible > roles. > > An example with the existing keystone docker service [1]: > > The upgrade_tasks block will become: > > ``` > upgrade_tasks: > - import_role: > name: tripleo-role-keystone > tasks_from: upgrade.yaml > ``` > > The fast_forward_upgrade_tasks block will become: > > ``` > fast_forward_upgrade_tasks: > - import_role: > name: tripleo-role-keystone > tasks_from: fast_forward_upgrade.yaml > ``` > > And this role [2] will be structured: > > ``` > tripleo-role-keystone/ > └── tasks > ├── fast_forward_upgrade.yaml > ├── main.yaml > └── upgrade.yaml > ``` > > We'd love to hear any feedback from the community as we move towards this. > > Thank you, > David Peacock > > [0] https://github.com/davidjpeacock/openstack-role- > extract/blob/master/role-extractor-creator.py > [1] https://github.com/openstack/tripleo-heat-templates/blob/ > master/docker/services/keystone.yaml > [2] https://github.com/davidjpeacock/tripleo-role-keystone > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
