Set up global proxy environment variables from user variable
Bug #1452456 reported by
Ian Cordasco
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack-Ansible |
Fix Released
|
Wishlist
|
Ian Cordasco | ||
Juno |
Fix Released
|
Wishlist
|
Hugh Saunders | ||
Kilo |
Fix Released
|
Wishlist
|
Ian Cordasco | ||
Trunk |
Fix Released
|
Wishlist
|
Ian Cordasco |
Bug Description
For users deploying from behind a proxy, pip (and requests) needs to know what those proxies are. It would be useful to have a variable that can be configured to automatically configure the HTTP_PROXY and HTTPS_PROXY environment variables. pip and the python clients will respect these variables as necessary. Defining these on the hosts and containers should be a common task only when the user variable is defined.
Changed in openstack-ansible: | |
assignee: | nobody → Ian Cordasco (icordasc) |
To post a comment you must log in.
We should also, at the same time, calculate a NO_PROXY environment variable. We should probably add to that, the container network CIDR, and a few other IPs/hosts (localhost, etc) that we know we won't need to talk to the proxy for since they're internal only.