7f15455d8d
Pair nodes dynamically via a distributed coordination backend for network burn-in. The algorithm uses a group to pair nodes: after acquiring a lock, a first node joins the group, releases the lock, waits for a second node, then they both leave, and release the lock for the next pair. Story: #2007523 Task: #42796 Change-Id: I572093b144bc90a49cd76929c7e8685ed45d9f6e
24 lines
863 B
Plaintext
24 lines
863 B
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.
|
|
pbr!=2.1.0,>=2.0.0 # Apache-2.0
|
|
importlib_metadata>=1.7.0;python_version<'3.8' # Apache-2.0
|
|
eventlet!=0.18.3,!=0.20.1,>=0.18.2 # MIT
|
|
netifaces>=0.10.4 # MIT
|
|
oslo.config>=5.2.0 # Apache-2.0
|
|
oslo.concurrency>=3.26.0 # Apache-2.0
|
|
oslo.log>=3.36.0 # Apache-2.0
|
|
oslo.serialization!=2.19.1,>=2.18.0 # Apache-2.0
|
|
oslo.service!=1.28.1,>=1.24.0 # Apache-2.0
|
|
oslo.utils>=3.34.0 # Apache-2.0
|
|
Pint>=0.5 # BSD
|
|
psutil>=3.2.2 # BSD
|
|
pyudev>=0.18 # LGPLv2.1+
|
|
requests>=2.14.2 # Apache-2.0
|
|
stevedore>=1.20.0 # Apache-2.0
|
|
tenacity>=6.2.0 # Apache-2.0
|
|
ironic-lib>=5.1.0 # Apache-2.0
|
|
Werkzeug>=1.0.1 # BSD License
|
|
cryptography>=2.3 # BSD/Apache-2.0
|
|
tooz>=2.7.2 # Apache-2.0
|