CloudBolt 4.6.1 and newer
CloudBolt 4.6 and earlier
[Boto]
debug = 0
num_retries = 10
proxy = myproxy.com
proxy_port = 8080
proxy_user = foo
proxy_pass = bar
Then run:
chown apache:apache /etc/boto.cfg
service httpd restart
[Boto]
debug = 0
num_retries = 10
proxy = myproxy.com
proxy_port = 8080
proxy_user = foo
proxy_pass = bar
Then run:
chown apache:apache /etc/boto.cfg
service httpd restart
This is a HUGE downfall for so many applications where installation in a corporate environment is an afterthought. Thanks for catching this in advance.
Is there a similar setting for other cloud providers? What about a global setting? When will this appear in the UI?
Dillon,
We are looking into this for other cloud providers, are there specific one(s) you're interested in seeing this for? Some expose better support for this than others.
We haven't yet scoped adding it as a global setting to the UI (it will appear in the quick setup wizard and also in the admin --> misc settings page), but seems likely that it will fit in our next release (4.6.1, out in December).
Thanks,
Bernard
Azure would be the most desirable at this point. The UI hook would be a nice to have, but the proxy support is a must have.
Dillon,
We figured out a way to do this for Azure and will be working on implementing & testing it. It should fit into our 4.6.1 release (December) with little trouble. Once we've got a better estimate for when it can be done, we'll reach out to you to see if you'd like an update for this earlier than that.
Thanks,
Bernard
It appears that SSL proxy support is not included. This precludes users from using intermediary certs that are used for internal SSL packet inspection. Still investigating.
The ability to configure a proxy to use globally in CloudBolt (to connect to AWS, Azure, etc) has been added for 4.6.1, which will be out in December, 2014. If you would like an alpha/beta before then, contact CloudBolt support (support@cloudboltsoftware.com) and they can get you an upgrader.
thanks,
Bernard
7 Comments