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

pbr!=2.1.0,>=2.0.0 # Apache-2.0
Babel!=2.4.0,>=2.3.4 # BSD
croniter>=0.3.4 # MIT License
eventlet!=0.18.3,!=0.20.1,<0.21.0,>=0.18.2 # MIT
greenlet>=0.3.2 # MIT
icalendar>=3.10 # BSD
keystoneauth1>=2.21.0 # Apache-2.0
keystonemiddleware>=4.12.0 # Apache-2.0
python-manilaclient>=1.12.0 # Apache-2.0
oslo.config!=4.3.0,!=4.4.0,>=4.0.0 # Apache-2.0
oslo.concurrency>=3.8.0 # Apache-2.0
oslo.context>=2.14.0 # Apache-2.0
oslo.db>=4.23.0 # Apache-2.0
oslo.log>=3.22.0 # Apache-2.0
oslo.messaging!=5.25.0,>=5.24.2 # Apache-2.0
oslo.middleware>=3.27.0 # Apache-2.0
oslo.policy>=1.23.0 # Apache-2.0
oslo.serialization>=1.10.0 # Apache-2.0
oslo.service>=1.10.0 # Apache-2.0
oslo.versionedobjects>=1.17.0 # Apache-2.0
Paste # MIT
PasteDeploy>=1.5.0 # MIT
python-glanceclient>=2.7.0 # Apache-2.0
python-novaclient>=9.0.0 # Apache-2.0
python-cinderclient>=2.1.0 # Apache-2.0
requests>=2.14.2 # Apache-2.0
Routes>=2.3.1 # MIT
python-neutronclient>=6.3.0 # Apache-2.0
six>=1.9.0 # MIT
SQLAlchemy!=1.1.5,!=1.1.6,!=1.1.7,!=1.1.8,>=1.0.10 # MIT
sqlalchemy-migrate>=0.11.0 # Apache-2.0
stevedore>=1.20.0 # Apache-2.0
taskflow>=2.7.0 # Apache-2.0
WebOb>=1.7.1 # MIT
oslo.i18n!=3.15.2,>=2.1.0 # Apache-2.0
python-swiftclient>=3.2.0 # Apache-2.0
python-heatclient>=1.6.1 # Apache-2.0
python-karborclient>=0.2.0 # Apache-2.0
abclient>=0.2.3 # Apache-2.0