# The order of packages is significant, because pip processes them in the order
# of appearance. Changing the order has an impact on the overall integration
# process, which may cause wedges in the gate later.

-e git+https://github.com/openstack/neutron.git@kilo-eol#egg=neutron
-e git+https://github.com/openstack/python-heatclient@kilo-eol#egg=heatclient
hacking>=0.9.2,<0.10

cliff<1.11.0,>=1.10.0 # Apache-2.0
coverage>=3.6
fixtures<1.3.0,>=0.3.14
httplib2>=0.7.5
mock<1.1.0,>=1.0
ordereddict
oslosphinx>=2.5.0,<2.6.0  # Apache-2.0
python-subunit>=0.0.18
requests>=2.2.0,!=2.4.0,<2.8.0
requests-mock<0.8.0,>=0.6.0 # Apache-2.0
sphinx!=1.2.0,!=1.3b1,<1.3,>=1.1.2
testrepository>=0.0.18
testtools!=1.2.0,<2.0.0,>=0.9.36
testscenarios>=0.4
WebTest>=2.0
oslotest<1.6.0,>=1.5.1 # Apache-2.0
tempest-lib<0.5.0,>=0.4.0

-e git+https://github.com/noironetworks/python-opflex-agent.git@stable/kilo#egg=neutron_opflex_agent
-e git+https://github.com/noironetworks/apic-ml2-driver.git@kilo#egg=neutron_ml2_driver_apic
