# 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.11,>=0.10.0
coverage>=3.6
fixtures>=1.3.1
mock>=1.2
mox3>=0.7.0
psycopg2>=2.5
PyMySQL>=0.6.2 # MIT License
python-barbicanclient>=3.3.0
python-ironicclient>=0.8.0
python-subunit>=0.0.18
requests-mock>=0.6.0 # Apache-2.0
sphinx!=1.2.0,!=1.3b1,<1.3,>=1.1.2
oslosphinx>=2.5.0 # Apache-2.0
oslotest>=1.10.0 # Apache-2.0
os-testr>=0.4.1
testrepository>=0.0.18
testtools>=1.4.0
tempest-lib>=0.9.0
bandit>=0.13.2

# vmwareapi driver specific dependencies
oslo.vmware>=1.16.0 # Apache-2.0

# 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.11,>=0.10.0
coverage>=3.6
fixtures>=1.3.1
mock>=1.2
mox3>=0.7.0
psycopg2>=2.5
PyMySQL>=0.6.2 # MIT License
python-barbicanclient>=3.3.0
python-ironicclient>=0.8.0
python-subunit>=0.0.18
requests-mock>=0.6.0 # Apache-2.0
sphinx!=1.2.0,!=1.3b1,<1.3,>=1.1.2
oslosphinx>=2.5.0 # Apache-2.0
oslotest>=1.10.0 # Apache-2.0
os-testr>=0.4.1
testrepository>=0.0.18
testresources>=0.2.4
testtools>=1.4.0
tempest-lib>=0.9.0
bandit>=0.13.2

# vmwareapi driver specific dependencies
oslo.vmware>=1.16.0 # Apache-2.0

Add testresources used by oslo.db fixture
Add testresources used by oslo.db fixture

If we use oslo.db fixtures, we'll need the package or
the next version of oslo.db release will break us.

Closes-Bug: #1503501
Change-Id: I176c85551007d3d9e7de8896ad12e9b87ff278d8
