# 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
etcd3gw>=0.2.0 # Apache-2.0
cassandra-driver!=3.6.0,>=2.1.4 # Apache-2.0
kazoo>=2.2 # Apache-2.0
ovs>=2.8.0 # Apache-2.0
pyzmq>=14.3.1 # LGPL+BSD
ryu>=4.24 # Apache-2.0
SQLAlchemy>=1.2.0 # MIT
alembic>=0.8.10 # MIT
neutron-lib>=1.18.0 # Apache-2.0
oslo.config>=5.2.0 # Apache-2.0
oslo.db>=4.27.0 # Apache-2.0
oslo.i18n>=3.15.3 # Apache-2.0
oslo.log>=3.36.0 # Apache-2.0
oslo.reports>=1.18.0 # Apache-2.0
oslo.serialization!=2.19.1,>=2.18.0 # Apache-2.0
oslo.upgradecheck>=0.1.0 # Apache-2.0
ovsdbapp>=0.11.0 # Apache-2.0
crc16>=0.1.1 # LGPLv3+
netaddr>=0.7.18 # BSD
six>=1.11.0 # MIT
httplib2>=0.9.1 # MIT
WebOb>=1.7.1 # MIT
jsonmodels>=2.1.5 # BSD License (3 clause)
skydive-client>=0.4.5 # Apache-2.0
cotyledon>=1.3.0  # Apache-2.0
PyYAML>=3.12  # MIT

# These repos are installed from git in OpenStack CI if the job
# configures them as required-projects:
neutron>=13.0.0.0b1  # Apache-2.0
networking-sfc>=6.0.0  # Apache-2.0

# The comment below indicates this project repo is current with neutron-lib
# and should receive neutron-lib consumption patches as they are released
# in neutron-lib. It also implies the project will stay current with TC
# and infra initiatives ensuring consumption patches can land.
# neutron-lib-current