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
As noted in another separate issue, installations behind a Proxy (which would be common) causes a bit of grief.
At the current trunk version there is a PPA that is being added (that fails for me due to proxy/key issues), APT-GET processes that require the use of a proxy to get out, and CURL processes for downloading the latest boot images bzImage and Hash checks.
I think it would be a good investment to as the installer/admin to optionally provide a proxy server IP, port and (optionally) ask for any credentials for an authenticated proxy server. This information could be fed into APT, CURL and any other internet grab functions.
As it stands at the moment I need to go into the scripts and comment out the (mysterious) PPA that fails, and all CURL statements for acquiring the images. I then pull down the images manually as it's easier then editing all of the CURL statements at the moment.
I would be glad to help with pulling the source and making a mockup of the changes to the installation scripts (with proxy) over the next week.
The text was updated successfully, but these errors were encountered:
You might want to continue this in the fog forum to get better exposure.
But with that said, I run my fog servers behind corporate proxies. In my case I use RHEL/Centos for the fog servers so I have to do 2 steps (I know they don't directly translate to Ubuntu).
SVN Rev 5661
Running Version 8064
As noted in another separate issue, installations behind a Proxy (which would be common) causes a bit of grief.
At the current trunk version there is a PPA that is being added (that fails for me due to proxy/key issues), APT-GET processes that require the use of a proxy to get out, and CURL processes for downloading the latest boot images bzImage and Hash checks.
I think it would be a good investment to as the installer/admin to optionally provide a proxy server IP, port and (optionally) ask for any credentials for an authenticated proxy server. This information could be fed into APT, CURL and any other internet grab functions.
As it stands at the moment I need to go into the scripts and comment out the (mysterious) PPA that fails, and all CURL statements for acquiring the images. I then pull down the images manually as it's easier then editing all of the CURL statements at the moment.
I would be glad to help with pulling the source and making a mockup of the changes to the installation scripts (with proxy) over the next week.
The text was updated successfully, but these errors were encountered: