openstack
/
kuryr-libnetwork
Code Issues Proposed changes

requirements: fix to point to upstream 

As a temporary measure, we were pointing to Vikas' fork for kuryr-lib
since he did most of the split work. Kuryr-lib is starting to take good
shape and it is necessary for community guidelines and for devstack
correct operation that we point to OpenStack's own kuryr-lib
(openstack/kuryr) repository.

Additionally, I manually published a development package to pypi for
kuryr-lib so that when devstack's pip install of kuryr-libnetwork tries
to find the kuryr-lib version in pypi, it finds one.

In the future, once kuryr-lib stabilizes, it would be good to operate
like Neutron does with Neutron lib, i.e., point to a specific kuryr-lib
release in requirements. Until then, `pip install -r requirements` will
install from master and `pip install .` will find the pypi wheel.

Change-Id: If9b5da3a1853a6aa1e5ef177952591684c0e6053
Signed-off-by: Antoni Segura Puimedon <antonisp@celebdor.com>
changes/31/356831/1
Antoni Segura Puimedon 2016-08-18 04:14:42 +02:00
parent 9961e9d39a
commit 1963cb4e20
No known key found for this signature in database
GPG Key ID: 2329618D2967720A
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
requirements.txt
View File

@ -16,4 +16,4 @@ oslo.utils>=3.11.0 # Apache-2.0
python-neutronclient>=4.2.0 # Apache-2.0
os-client-config>=1.13.1 # Apache-2.0
neutron-lib>=0.2.0 # Apache-2.0
-e git+https://github.com/vikaschoudhary16/kuryr.git@drop_libnet_specific_code#egg=kuryr-lib
-e git://git.openstack.org/openstack/kuryr#egg=kuryr_lib