<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>Kolla Devs as well as the Technical Committee,</div>
<div><br>
</div>
<div>I wanted to get the TC’s thoughts on this plan of action as we intend to apply for big tent once our Ansible code has completed implementation. If the approach outlined in this email seems like a blocker and we should just start with #4 instead, it would
be immensely helpful to know now.</div>
<div><br>
</div>
<div>The problem:</div>
<div>A whole slew of OpenStack modules exist upstream in the Ansible core directory. Kolla wants to use these modules. These files are licensed under the GPLv3. They will be released with Ansible 2.0 but Ansible 2.0 is not yet available. In the meantime
we need these modules to execute our system. The repo in question is:</div>
<div><br>
</div>
<div><a href="https://github.com/ansible/ansible-modules-core">https://github.com/ansible/ansible-modules-core</a></div>
<div><br>
</div>
<div>The possible solutions:</div>
<div>1. Mordred suggested just merging the code in our repo, but I thought this might trigger license contamination so I am not hot on this idea.</div>
<div>2. Relicense the upstream modules in ASL short term. Mordred tried this but thinks its not possible because of the varied contributors.</div>
<div>3. Fork the repo In question, remove everything except cloud/openstack directory and turn this into a pip installable library.</div>
<div>4. Make a hacky solution that doesn’t use any upstream modules but gets the job done.</div>
<div><br>
</div>
<div>For the moment we have settled on #3, that is creating a repo here:</div>
<div><br>
</div>
<div><a href="https://github.com/sdake/kolla-pre-ansible-2-openstack/">https://github.com/sdake/kolla-pre-ansible-2-openstack/</a></div>
<div><br>
</div>
<div>And installing these in the deployment system. Once Ansible 2.0 is available, we would deprecate this model, and rely on Ansible 2.0 exclusively.</div>
<div><br>
</div>
<div>Thoughts or concerns on this approach?</div>
<div><br>
</div>
<div>Thanks</div>
<div>-steve</div>
</body>
</html>