<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Sep 25, 2016 at 7:02 PM, Nadav Goldin <span dir="ltr"><<a href="mailto:ngoldin@redhat.com" target="_blank">ngoldin@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br>
As discussed in the PR[1], we might need to think of restructuring our<br>
demos/examples repositories.<br>
<br>
I suggest the following structure:<br>
<br>
- lago-project/lago-examples.git - Examples of how to use lago to deploy 'X'<br>
This repository will hold all examples of deploying Lago, each example<br>
will have its own directory. Currently we have:<br>
lago-project/lago-examples/<wbr>jenkins - the current lago-demo<br>
repository[1](scripts to deploy Jenkins using Lago)<br>
lago-project/lago-examples/<wbr>ovirt-system-tests - installing lago +<br>
ovirt-system-tests[3]<br></blockquote><div><br></div><div>+1 for this.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
- lago-project/lago-ansible-<wbr>examples.git<br>
The same as 'lago-examples.git', only it will hold ansible playbooks<br>
that use lago and ansible for deployment(such as the PR)<br>
<br>
- lago-project/lago-ansible.git<br>
Holding a generic ansible playbook to install lago(once we have one :)<br>
<br></blockquote><div><br></div><div>I think its still unclear for a user what will be the diff between those 2 repos.</div><div>We need first to list the Ansible use cases that are possible within Lago:</div><div><ol><li>Using Ansible to install Lago for a user ( + optionally run a test suite, like ovirt-system-tests)</li><li>Using Ansible to install Lago for developer (might be similar to 1 only with more deps installed )</li><li>Using Ansible as Dynamic Inventory Script [1]</li><li>Using Ansible as deployment scripts ( should be in the relvant project, like OST ) <br></li><li>?? probably there are more.</li></ol></div><div>Once we agree on the set of 'roles' Ansible can take, we can decide on the repos to hold them. </div><div><br></div><div><br></div><div>[1] <a href="https://github.com/lago-project/lago/issues/281">https://github.com/lago-project/lago/issues/281</a></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Though I'll note that I have no concrete idea of what are the ansible<br>
conventions.<br>
<br>
Thoughts?<br>
<br>
<br>
<br>
Thanks,<br>
<br>
Nadav.<br>
<br>
<br>
[1] <a href="https://github.com/lago-project/lago/pull/326" rel="noreferrer" target="_blank">https://github.com/lago-<wbr>project/lago/pull/326</a><br>
[2] <a href="https://github.com/lago-project/lago-demo" rel="noreferrer" target="_blank">https://github.com/lago-<wbr>project/lago-demo</a><br>
[2] <a href="https://github.com/lago-project/lago-demo/tree/master/install_scripts" rel="noreferrer" target="_blank">https://github.com/lago-<wbr>project/lago-demo/tree/master/<wbr>install_scripts</a><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div>Eyal Edri<br>Associate Manager</div><div>RHV DevOps<br>EMEA ENG Virtualization R&D<br>Red Hat Israel<br><br>phone: +972-9-7692018<br>irc: eedri (on #tlv #rhev-dev #rhev-integ)</div></div></div></div></div></div></div>
</div></div>