| 2014-12-11 21:03:48 |
Ante Karamatić |
description |
In an environment where proxy for http exists, adding relation between swift-storage (SS) and swift-proxy (SP) will fail.
What happens is that juju provides http_proxy and no-proxy options to SS, which then uses that when it wgets rings from SP. Since SP's IP is not in no-proxy variable, wget will fail. This can be fixed by adding SP's IP into juju's no-proxy variable. But, the problem is that IP might be unknown until SP is deployed. This is easy to solve when VIP for SP is known before deploying.
Ideally, SS would always append SP's VIP and SP's IP to no-proxy provided by juju. |
In an environment where proxy for http exists, adding relation between swift-storage (SS) and swift-proxy (SP) will fail.
What happens is that juju provides http_proxy and no-proxy options to SS, which then uses that when it wgets rings from SP. Since SP's IP is not in no-proxy variable, wget might fail, depending on http proxy's configuration (it could be set to proxy only external requests). This can be fixed by adding SP's IP into juju's no-proxy variable. But, the problem is that IP might be unknown until SP is deployed. This is easy to solve when VIP for SP is known before deploying.
Ideally, SS would always append SP's VIP and SP's IP to no-proxy provided by juju. |
|
