<div dir="ltr"><div dir="auto"><div style="font-family:arial,helvetica,sans-serif;display:inline" class="gmail_default">​Nice!<br><br>​</div>I don't have a strong opinion <div style="font-family:arial,helvetica,sans-serif;display:inline" class="gmail_default">​about this but what I might recommend would be to chat with the openshift-ansible [1] and the kolla-ansible [2] folks.​</div><br><div style="font-family:arial,helvetica,sans-serif" class="gmail_default">​I'm happy to do the introductions if necessary !​<br><br></div><div style="font-family:arial,helvetica,sans-serif" class="gmail_default">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.<br></div><div style="font-family:arial,helvetica,sans-serif" class="gmail_default">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.<br><br>I'm not saying we should structure our things like theirs.<br>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.<br><br></div><div style="font-family:arial,helvetica,sans-serif" class="gmail_default">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 ?<br></div><br><div style="font-family:arial,helvetica,sans-serif" class="gmail_default">​[1]: <a href="https://github.com/openshift/openshift-ansible">https://github.com/openshift/openshift-ansible</a><br>[2]: <a href="https://github.com/openstack/kolla-ansible">https://github.com/openstack/kolla-ansible</a>​</div><br><div>David Moreau Simard<br>Senior Software Engineer | Openstack RDO<br><br>dmsimard = [irc, github, twitter]</div></div><br><div class="gmail_quote"><div dir="ltr">On Thu, Mar 29, 2018, 12:34 PM David Peacock, <<a href="mailto:dpeacock@redhat.com" target="_blank">dpeacock@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Hi everyone,</div><div><br></div><div>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.</div><div><br></div><div>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.</div><div><br></div><div>An example with the existing keystone docker service [1]:</div><div><br></div><div>The <font face="monospace, monospace">upgrade_tasks</font> block will become:</div><div><br></div><div><font face="monospace, monospace">```</font></div><div><font face="monospace, monospace">upgrade_tasks:</font></div><div><font face="monospace, monospace">  - import_role:</font></div><div><font face="monospace, monospace">      name: tripleo-role-keystone</font></div><div><font face="monospace, monospace">      tasks_from: upgrade.yaml</font></div><div><font face="monospace, monospace">```</font></div><div><br></div><div>The <font face="monospace, monospace">fast_forward_upgrade_tasks</font> block will become:</div><div><br></div><div><font face="monospace, monospace">```</font></div><div><font face="monospace, monospace">fast_forward_upgrade_tasks:</font></div><div><font face="monospace, monospace">  - import_role:</font></div><div><font face="monospace, monospace">      name: tripleo-role-keystone</font></div><div><font face="monospace, monospace">      tasks_from: fast_forward_upgrade.yaml</font></div><div><font face="monospace, monospace">```</font></div><div><br></div><div>And this role [2] will be structured:</div><div><br></div><div><font face="monospace, monospace">```</font></div><div><div><font face="monospace, monospace">tripleo-role-keystone/</font></div><div><font face="monospace, monospace">└── tasks</font></div><div><font face="monospace, monospace">    ├── fast_forward_upgrade.yaml</font></div><div><font face="monospace, monospace">    ├── main.yaml</font></div><div><font face="monospace, monospace">    └── upgrade.yaml</font></div></div><div><font face="monospace, monospace">```</font></div><div><br></div><div>We'd love to hear any feedback from the community as we move towards this.</div><div><br></div><div>Thank you,</div><div>David Peacock</div><div><br></div><div>[0] <a href="https://github.com/davidjpeacock/openstack-role-extract/blob/master/role-extractor-creator.py" rel="noreferrer" target="_blank">https://github.com/<wbr>davidjpeacock/openstack-role-<wbr>extract/blob/master/role-<wbr>extractor-creator.py</a></div><div>[1] <a href="https://github.com/openstack/tripleo-heat-templates/blob/master/docker/services/keystone.yaml" rel="noreferrer" target="_blank">https://github.com/openstack/<wbr>tripleo-heat-templates/blob/<wbr>master/docker/services/<wbr>keystone.yaml</a></div><div>[2] <a href="https://github.com/davidjpeacock/tripleo-role-keystone" rel="noreferrer" target="_blank">https://github.com/<wbr>davidjpeacock/tripleo-role-<wbr>keystone</a></div></div>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
</blockquote></div></div>