
To be able to create profiling traces for Neutron, client should be able to send special HTTP header that contains trace info. This patch is also important to be able to make cross project traces. (Typical case nova calls neutron via python client, if profiler is initialized in nova, neutron client will add extra header, that will be parsed by special osprofiler middleware in neutron api.) Closes-Bug: #1335640 Co-Authored-By: Roman Podoliaka <rpodolyaka@mirantis.com> Change-Id: Ic11796889075b2a0e589b70398fc4d4ed6f3ef7c
22 lines
736 B
Plaintext
22 lines
736 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.
|
|
hacking<0.11,>=0.10.0
|
|
|
|
coverage>=4.0 # Apache-2.0
|
|
fixtures>=3.0.0 # Apache-2.0/BSD
|
|
mox3!=0.19.0,>=0.7.0 # Apache-2.0
|
|
mock>=2.0 # BSD
|
|
oslosphinx>=4.7.0 # Apache-2.0
|
|
oslotest>=1.10.0 # Apache-2.0
|
|
osprofiler>=1.4.0 # Apache-2.0
|
|
python-openstackclient>=3.3.0 # Apache-2.0
|
|
python-subunit>=0.0.18 # Apache-2.0/BSD
|
|
reno>=1.8.0 # Apache-2.0
|
|
requests-mock>=1.1 # Apache-2.0
|
|
sphinx!=1.3b1,<1.4,>=1.2.1 # BSD
|
|
testrepository>=0.0.18 # Apache-2.0/BSD
|
|
testtools>=1.4.0 # MIT
|
|
testscenarios>=0.4 # Apache-2.0/BSD
|
|
tempest>=12.1.0 # Apache-2.0
|