Proxy Support not present in tempest framework

Bug #1712537 reported by Ankit Arora
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
tempest
Confirmed
Undecided
Ankit Arora

Bug Description

Tempest framework currently uses urllib3 PoolManager to invoke api calls. This works in all cases except in those where the api calls have to be routed via a proxy server. There might be many usecases for routing api calls via a proxy. One of them is routing the calls to a proxy server(on a particular port) where a security scan tool is listening to these api calls. Support for routing calls to a proxy server is available in python requests library where it can either be set via a environment variable (HTTPS_PROXY) or send as an input api parameter. However, tempest framework does not use requests library yet.

urllib3 library has a class named ProxyManager (exactly same as and inherited from PoolManager but with proxy support). This can be used instead of PoolManager. Tempest users can be given an option to input proxy ip and port via a config attribute.

https://github.com/openstack/tempest/blob/master/tempest/lib/common/http.py#L20

Ankit Arora (aarora06)
Changed in tempest:
assignee: nobody → Ankit Arora (aarora06)
Changed in tempest:
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.