You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 12, 2021. It is now read-only.
Currently I am workarounding this by adding in /usr/share/conjure-up/conjure/juju.py (L:120) additional hardcoded command line params: --config bootstrap-timeout=3600 --config http-proxy=[proxy] --config https-proxy=[proxy] --config apt-http-proxy=[proxy] --config apt-https-proxy=[proxy] --config --config apt-ftp-proxy=[proxy] --config ftp-proxy=[proxy] no-proxy=[IPs]
It would be good to have these parameters configurable or provide a possibility to propagate them from env variables/MAAS 2.0 settings (if MAAS is used).
The text was updated successfully, but these errors were encountered:
I'm using this version, but I'm not seeing any global way to set the proxy before a model is created. It seems the only workaround is to use --config everywhere.
In previous versions of juju (prior to 2.0?) it was possible to change timeout and other settings like this: http://askubuntu.com/questions/458535/how-to-change-juju-bootstrap-time-from-the-10min-it-gives-you
In latest version of juju (2.0-beta9-xenial-amd64) and conjure-up (2.0.0.3-0
459ubuntu16.04.1) I don't see any way to provide proxy settings and juju bootstrap timeout. There is a thread on stackoverflow which already mentions that: http://askubuntu.com/questions/770624/how-to-set-bootstrap-timeout-when-deploying-landscape-dense-maas-from-conjure-upCurrently I am workarounding this by adding in /usr/share/conjure-up/conjure/juju.py (L:120) additional hardcoded command line params: --config bootstrap-timeout=3600 --config http-proxy=[proxy] --config https-proxy=[proxy] --config apt-http-proxy=[proxy] --config apt-https-proxy=[proxy] --config --config apt-ftp-proxy=[proxy] --config ftp-proxy=[proxy] no-proxy=[IPs]
It would be good to have these parameters configurable or provide a possibility to propagate them from env variables/MAAS 2.0 settings (if MAAS is used).
The text was updated successfully, but these errors were encountered: