Re: Juju2 behind proxy

2017-03-30 Thread Dmitrii Shcherbakov
Hi Vladimir, I would white-list at least the following: ubuntu-cloud.archive.canonical.com - TCP/80, TCP/443 cloud-images.ubuntu.com - TCP/80, TCP/443 keyserver.ubuntu.com - TCP/80, TCP/11371 archive.ubuntu.com - TCP/80, TCP/443 launchpad.net - TCP/22, TCP/80, TCP/443 launchpadlibrarian.net - TCP

Re: Juju2 behind proxy

2017-03-28 Thread Vladimir Burlakov
Hello guys, I wonder, if you can you tell, is there any way to get a list of domains (urls), where maas/juju getting os images, services etc. by default.., i mean something like "whitelist".. Now, i'm in a process of getting this from our firewall, but maybe such list is already there.. just,

Re: Juju2 behind proxy

2017-02-20 Thread Menno Smits
On 10 February 2017 at 19:07, Mark Shuttleworth wrote: > On 09/02/17 12:27, Vladimir Burlakov wrote: > > Hi Guys, > > Thank you a lot, it’s worked, you really helped me. :) as said my > > friend: "community - is the power !" > > :) > > Welcome aboard, Vladimir! > > One question - are we good abo

Re: Juju2 behind proxy

2017-02-20 Thread Charles Butler
Greetings Vladimir, As an author of the Canonical Distribution of Kubernetes charms I'm curious which connection attempts were blocking you. We've taken great care with respect to ensuring the charms will work in an offline environment. Our last hold-out issue was with the docker images. Docker ju

Re: Juju2 behind proxy

2017-02-20 Thread Merlijn Sebrechts
The issue with an https proxy is that this is an application level tunnel, not a network level tunnel. This means that EVERY application needs to change its behavior. You can't change this from the OS level. Juju correctly sets the https proxy variables, but those are only suggestions. It is still

Re: Juju2 behind proxy

2017-02-20 Thread Vladimir Burlakov
Hi Mark, Some thoughts/tests on how charms works after/in deployment state in proxy environment, f.e in deploying Kubernetes charm we stuck, cause application trying to connect to public http/s servers without proxy, and it not reads system settings for proxy .. so maybe there (in juju) should

Re: Juju2 behind proxy

2017-02-09 Thread Mark Shuttleworth
On 09/02/17 12:27, Vladimir Burlakov wrote: > Hi Guys, > Thank you a lot, it’s worked, you really helped me. :) as said my > friend: "community - is the power !" :) Welcome aboard, Vladimir! One question - are we good about passing this proxy information on to the various machines that get spu

Re: Juju2 behind proxy

2017-02-09 Thread Vladimir Burlakov
Hi Guys, Thank you a lot, it’s worked, you really helped me. :) as said my friend: "community - is the power !" Best, Vladimir > 9 февр. 2017 г., в 6:35, Menno Smits написал(а): > > One thing to be aware of is that many of the downloads done for a given model > (for example charms and re

Re: Juju2 behind proxy

2017-02-08 Thread Menno Smits
One thing to be aware of is that many of the downloads done for a given model (for example charms and resources) are done on the controller. This means you need to set the proxy settings for the controller model as well as any other models hosted on the controller. This is probably somewhat unexpec

Re: Juju2 behind proxy

2017-02-08 Thread Reed O'Brien
On Wed, Feb 8, 2017 at 8:31 AM, John Meinel wrote: > There is model configuration that you can set to tell juju what the proxies > are. Normally you set them at bootstrap time with: > juju bootstrap --model-default http-proxy=http://... --model-default > https-proxy... --model-default no-proxy=

Re: Juju2 behind proxy

2017-02-08 Thread John Meinel
There is model configuration that you can set to tell juju what the proxies are. Normally you set them at bootstrap time with: juju bootstrap --model-default http-proxy=http://... --model-default https-proxy... --model-default no-proxy= You can also put these settings into ~/.local/share/clouds.