deckhand/requirements.txt
Felipe Monteiro 38c1d7a1a3 fix: Pin down Deckhand package requirements
This patch set pins down package requirements for the following
reasons:

* Inconsistencies between ranges and direct pins
* Deckhand isn't gated against requirements repo so changes to
  some packages isn't actively tested
* Other Airship components use pins, so Deckhand might break them
  when package requirements go out of sync between components
* Deckhand as of yet has no stable release so Airship relies on
  master for stability so it is better to ensure stability over
  anything else

Change-Id: I20ef4be3e01cd267771098d33447ccb61aee20b4
2018-10-18 02:36:35 +01:00

49 lines
1.0 KiB
Plaintext

# 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==1.1.0
alembic==1.0.1
beaker==1.9.1
cryptography==2.3.1
deepdiff==3.3.0
falcon==1.2.0
jsonpath-ng==1.4.3
jsonschema==2.6.0
keystoneauth1==3.4.0
keystonemiddleware==4.17.0
networkx==2.1
oslo.cache==1.31.0
oslo.concurrency==3.28.1
oslo.config==6.6.1
oslo.context>=2.21.0
oslo.messaging==8.1.2
oslo.db==4.41.1
oslo.log==3.40.1
oslo.middleware==3.36.0
oslo.policy==1.40.0
oslo.serialization==2.28.1
oslo.utils==3.37.1
pbr==5.0.0
PasteDeploy==1.5.2
Paste==2.0.3
psycopg2==2.7.4
# TODO(alanmeadows)
# this must match the container service
# likely this should be imported from a
# container sidecar long-term
python-barbicanclient==4.7.0
python-keystoneclient==3.17.0
python-memcached==1.59
requests==2.19.1
Routes==2.4.1
six==1.11.0
stevedore==1.29.0
urllib3==1.23
uwsgi==2.0.17
# To support profiling in non-prod
Werkzeug==0.14.1