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

hacking!=0.13.0,<0.14,>=0.12.0 # Apache-2.0
python-dateutil>=2.4.2 # BSD
coverage!=4.4,>=4.0 # Apache-2.0
lxml!=3.7.0,>=3.4.1 # BSD
networkx<2.0,>=1.10 # BSD
PyMySQL>=0.7.6 # MIT License
python-ceilometerclient>=2.5.0 # Apache-2.0
python-cinderclient>=3.3.0 # Apache-2.0
python-neutronclient>=6.7.0 # Apache-2.0
python-novaclient>=9.1.0 # Apache-2.0
python-heatclient>=1.10.0 # Apache-2.0
python-subunit>=1.0.0 # Apache-2.0/BSD
pyzabbix>=0.7.4 # LGPL
oslo.db>=4.27.0 # Apache-2.0
oslo.log>=3.36.0 # Apache-2.0
oslotest>=3.2.0 # Apache-2.0
oslo.service!=1.28.1,>=1.24.0 # Apache-2.0
oslo.config>=5.1.0 # Apache-2.0
oslo.messaging>=5.29.0 # Apache-2.0
oslo.i18n>=3.15.3 # Apache-2.0
oslo.policy>=1.30.0 # Apache-2.0
pecan!=1.0.2,!=1.0.3,!=1.0.4,!=1.2,>=1.0.0 # BSD
requests-mock>=1.1.0 # Apache-2.0
testrepository>=0.0.18 # Apache-2.0/BSD
testscenarios>=0.4 # Apache-2.0/BSD
testtools>=2.2.0 # MIT
stestr>=1.0.0  # Apache-2.0
stevedore>=1.20.0 # Apache-2.0
voluptuous>=0.8.9 # BSD License
sympy>=0.7.6 # BSD
reno>=2.5.0 # Apache-2.0
pysnmp>=4.2.3 # BSD
osprofiler>=1.4.0 # Apache-2.0
SQLAlchemy!=1.1.5,!=1.1.6,!=1.1.7,!=1.1.8,>=1.0.10 # MIT