372bc4947e
The concurrent.futures module is one of the ways that async activities can be done in the future, so we should try to work on getting to that future by using more futures. To enable this (as well as to enable getting off eventlet), add a thread pool based executor which will process incoming messages using the pool. Also begins adding according docs as well for the different types of executors that are available. Change-Id: I1482fd70abbf69f4e2994597c5e95d91fecb815e
32 lines
757 B
Plaintext
32 lines
757 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>=0.6,!=0.7,<1.0
|
|
|
|
oslo.config>=1.4.0 # Apache-2.0
|
|
oslo.utils>=1.1.0 # Apache-2.0
|
|
oslo.serialization>=1.0.0 # Apache-2.0
|
|
oslo.i18n>=1.0.0 # Apache-2.0
|
|
stevedore>=1.1.0 # Apache-2.0
|
|
|
|
# for jsonutils
|
|
six>=1.7.0
|
|
|
|
# FIXME(markmc): remove this when the drivers no longer
|
|
# import eventlet
|
|
|
|
eventlet>=0.15.2
|
|
|
|
# for the routing notifier
|
|
PyYAML>=3.1.0
|
|
|
|
# rabbit driver is the default
|
|
kombu>=2.5.0
|
|
|
|
# middleware
|
|
oslo.middleware>=0.1.0 # Apache-2.0
|
|
|
|
# for the futures based executor
|
|
futures>=2.1.6
|