<div dir="ltr">There's a note in the "for development" section [1] that notes the development instructions don't include anything that puts kolla in your sys.path or any bin scripts copied out anywhere into the PATH - i.e. it's not installed<div><br></div><div>That seems less than ideal for a developer - did I miss a `pip install -e .` somewhere?</div><div><br></div><div>-Clay<br><div><br></div><div>1. <a href="http://docs.openstack.org/developer/kolla/quickstart.html#installing-kolla-and-dependencies-for-development">http://docs.openstack.org/developer/kolla/quickstart.html#installing-kolla-and-dependencies-for-development</a></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Sep 13, 2016 at 4:33 PM, Steven Dake (stdake) <span dir="ltr"><<a href="mailto:stdake@cisco.com" target="_blank">stdake@cisco.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="white" lang="EN-US" link="#0563C1" vlink="#954F72">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt">Hey folks,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">The quickstart guide was modified as a result of a lot of painful debugging over the last cycle approximately a month ago. The only solution available to us was to split the workflow into an operator workflow
(working on stable branches) and a developer workflow (working on master). We recognize operators are developers and the docs indicate as much. Many times operators want to work with master as they are evaluating Newton and planning to place it into production.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">I’d invite folks using master with the pip install ./ method to have a re-read of the quickstart documentation. The documentation was changed in subtle ways (with warning and info boxes) but folks that have
been using Kolla prior to the quckstart change may be using kolla in the same way the quickstart previously recommended. Folks tend to get jammed up on this issue – we have helped 70-100 people work past this problem before we finally sorted out a workable
solution (via documentation).<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">The real issue lies in how PBR operates and pip interacts with Kolla and is explained in the quickstart. From consulting with Doug Hellman and others in the release team, it appears the issue that impacts
Kolla is not really solveable within PBR itself. (I don’t mean to put words in Doug’s mouth, but that is how I parsed our four+ hour discussion) on the topic.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">The documentation is located here:<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><a href="http://docs.openstack.org/developer/kolla" target="_blank">http://docs.openstack.org/<wbr>developer/kolla</a><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><u></u> <u></u></span></p>
</div>
</div>
<br>______________________________<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" 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" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
<br></blockquote></div><br></div>