7733488f00
Tobiko has used the oslo_concurrency.lockutils.synchronized to lock execution of functions inter-process/worker. The synchronized decorator does not support to disable intra-worker locks. This is a problem for tobiko because there are some functions that need to be locked between different workers, but not inside a worker. Why? - Tobiko execution (based on pytest) is multi-worker, but not multi-thread. - The creation of Tobiko resources (which is what we need to lock to avoid concurrency issues between workers) sometimes depends on the creation of other Tobiko resources that are defined in either parent or child classes from the first ones, getting blocked due to the locks applied. Change-Id: I0b1c2d707b585fd4e45cad9968c88cedf2932eed
33 lines
1.3 KiB
Plaintext
33 lines
1.3 KiB
Plaintext
# Tobiko framework requirements
|
|
|
|
decorator>=4.4.2 # BSD
|
|
docker>=4.4.1 # Apache-2.0
|
|
fixtures>=3.0.0 # Apache-2.0/BSD
|
|
Jinja2>=2.11.2 # BSD
|
|
keystoneauth1>=4.3.0 # Apache-2.0
|
|
metalsmith>=1.6.2 # Apache-2.0
|
|
netaddr>=0.8.0 # BSD
|
|
neutron-lib>=2.7.0 # Apache-2.0
|
|
openstacksdk>=0.31.2 # Apache-2.0
|
|
oslo.concurrency>=3.26.0 # Apache-2.0
|
|
oslo.config>=8.4.0 # Apache-2.0
|
|
oslo.log>=4.4.0 # Apache-2.0
|
|
oslo.utils>=4.12.3 # Apache-2.0
|
|
packaging>=20.4 # Apache-2.0
|
|
paramiko>=2.9.2 # LGPLv2.1
|
|
pbr>=5.5.1 # Apache-2.0
|
|
psutil>=5.8.0 # BSD
|
|
python-dateutil>=2.8.0 # Apache-2.0
|
|
python-designateclient>=4.4.0 # Apache-2.0
|
|
python-glanceclient>=3.2.2 # Apache-2.0
|
|
python-heatclient>=2.3.0 # Apache-2.0
|
|
python-ironicclient>=4.6.1 # Apache-2.0
|
|
python-manilaclient>=4.5.1 # Apache-2.0
|
|
python-neutronclient>=7.2.1 # Apache-2.0
|
|
python-novaclient>=17.2.1 # Apache-2.0
|
|
python-octaviaclient>=2.2.0 # Apache-2.0
|
|
python-openstackclient>=5.4.0 # Apache-2.0
|
|
PyYAML>=5.4.1 # MIT
|
|
sshtunnel>=0.3.1 # MIT
|
|
testtools>=2.5.0 # MIT
|