Open Stack

pip install –e . is not viable either for a variety of reasons.  We expect developers to be able to find their way to the tools directory and operate the commands directly from there.

Regards
-steve


From: Clay Gerrard <clay.gerrard at gmail.com>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org>
Date: Tuesday, September 13, 2016 at 5:11 PM
To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org>
Subject: Re: [openstack-dev] [kolla] warning about PBR issue for kolla operators

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

That seems less than ideal for a developer - did I miss a `pip install -e .` somewhere?

-Clay

1. http://docs.openstack.org/developer/kolla/quickstart.html#installing-kolla-and-dependencies-for-development

On Tue, Sep 13, 2016 at 4:33 PM, Steven Dake (stdake) <stdake at cisco.com<mailto:stdake at cisco.com>> wrote:
Hey folks,

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.

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).

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.

The documentation is located here:
http://docs.openstack.org/developer/kolla



__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe<http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160914/1404801f/attachment.html>