# 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>=1.6
anyjson>=0.3.3
keystonemiddleware!=2.4.0,>=2.0.0
oslo.config>=2.3.0 # Apache-2.0
oslo.concurrency>=2.3.0 # Apache-2.0
oslo.context>=0.2.0 # Apache-2.0
oslo.db>=2.4.1 # Apache-2.0
oslo.log>=1.8.0 # Apache-2.0
oslo.messaging!=1.17.0,!=1.17.1,!=2.6.0,!=2.6.1,!=2.7.0,!=2.8.0,!=2.8.1,!=2.9.0,!=3.1.0,>=1.16.0 # Apache-2.0
oslo.middleware!=3.0.0,!=3.1.0,!=3.2.0,>=2.8.0 # Apache-2.0
oslo.policy>=0.5.0 # Apache-2.0
oslo.reports>=0.1.0 # Apache-2.0
oslo.rootwrap>=2.0.0 # Apache-2.0
oslo.serialization>=1.4.0 # Apache-2.0
oslo.service>=0.7.0 # Apache-2.0
oslo.utils!=2.6.0,>=2.0.0 # Apache-2.0
oslo.versionedobjects>=0.9.0
oslo.i18n>=1.5.0 # Apache-2.0
osprofiler>=0.3.0 # Apache-2.0
openstacksdk>=0.46.0 # Apache-2.0
six>=1.9.0
SQLAlchemy>=1.2.19 # MIT
sqlalchemy-migrate>=0.9.6
PyMySQL>=0.7.11
elasticsearch>=7.10.1
apscheduler>=3.6.3
paste>=3.0.2
webob>=1.8.5
lxml>=4.4.0

stevedore>=3.3.0
Routes>=2.5.1
eventlet>=0.30.0
greenlet>=0.4.17
urllib3>=1.24.2
retrying>=1.3.3
argparse>=1.4.0
setuptools>=39.2.0