[07:14] <erik_lonroth_> Hello people! Anyone here that knows where to figure out what url:s/domains that is used by "snap" to install juju? Our firewall/proxy is not being nice to me when trying to "snap install juju". Any pointers?
[11:33] <hloeung> erik_lonroth_: snaps are hosted on a CDN
[11:38] <hloeung> erik_lonroth_: maybe '068ed04f23.site.internapcdn.net.' ?
[11:41] <hloeung> that's from turning on query logging on my DNS resolver and running 'snap download juju'
[11:42] <hloeung> it also hits api.snapcraft.io before the CDN
[11:44] <magicaltrout> just won another local k8s contract, my ability to blag answers are second to none.....
[11:46] <rick_h> magicaltrout: lol awesome and congrats.
[12:12] <erik_lonroth_> hloeung: Thanx for trying to help out. I'm in the black here so I could use any help to compile a whitelist for the proxy.
[13:05] <stub> proof: E: config.yaml: ca does not conform to naming pattern
[13:05] <stub> Anyone know what that means?
[18:49] <magicaltrout> er right
[18:49] <magicaltrout> so I left my lovely k8s stack running last week
[18:49] <magicaltrout> this week
[18:49] <magicaltrout> I'm getting lots of this:
[18:49] <magicaltrout> manifold worker returned unexpected error: leadership failure: lease manager stopped
[18:49] <magicaltrout> on about 20 nodes
[18:49] <magicaltrout> what have i missed?
[18:53] <magicaltrout> https://paste.ubuntu.com/25473709/
[18:57] <magicaltrout> 2017-09-03 21:59:25 ERROR juju.worker.uniter.context context.go:675 could not write settings from "update-status" to relation 26: cannot write settings: read tcp 127.0.0.1:37346->127.0.0.1:37017: i/o timeout
[18:57] <magicaltrout> does juju really suffer such a meltdown if there is a network issue?
[18:59] <tvansteenburgh> balloons, that mean anything to you? ^
[19:01] <balloons> magicaltrout, what does juju status say/show?
[19:01] <magicaltrout> i've rebooted the controller and the connections seem to be coming back
[19:01] <magicaltrout> but its spent 2 days in that weird failed state
[19:02] <magicaltrout> https://pastebin.com/ETBuBTS4
[19:02] <magicaltrout> before the restart it said that balloons
[19:03] <magicaltrout> back to green *phew* I don't like read
[19:03] <magicaltrout> red
[19:03] <balloons> yea, a bunch of failed workers.
[19:03] <balloons> curious how it got that way
[19:03] <magicaltrout> that said, the network was fine, I could ssh around from the controller to other nodes and stuff
[19:03] <magicaltrout> so I dunno why it got so sad for 2 days straight
[20:42] <magicaltrout> cicleci for juju builds is possibly the best thing I've ever found
[20:43] <magicaltrout> and snap builds for that matter
[20:44] <rick_h> magicaltrout: charming circleci? I was going to play with that at one point but it was missing something I needed. /me tries to remember...
[20:47] <magicaltrout> https://github.com/spiculedata/circleci-juju i wrote a simple dockerfile for it rick_h
[20:47] <magicaltrout> doesn't support resources yet
[20:47] <rick_h> magicaltrout: nice
[20:48] <magicaltrout> https://pastebin.com/1PrpjrP6
[20:48] <magicaltrout> build files look like that
[20:48] <magicaltrout> it can clearly be cleaned up and extended a bit, does the job nicely though for per commit builds of stuff
[23:06] <bdx> can I specify a subnet to bootstrap to?
[23:06] <bdx> for AWS
[23:06] <bdx> I thought I saw that land
[23:06] <bdx> rick_h: ^
[23:08] <rick_h> bdx: yea should be able to in 2.2.2
[23:08] <bdx> oh nice
[23:08] <rick_h> Thought it was in there.
[23:08] <bdx> yeah I thought so too
[23:09] <bdx> jam: ^?
[23:17] <bdx> found it https://bugs.launchpad.net/juju/+bug/1659640
[23:17] <mup> Bug #1659640: Juju needs to support specifying subnets for controller <juju:Fix Released by jameinel> <https://launchpad.net/bugs/1659640>
[23:18] <bdx> aweeeee it works too :)
[23:18] <bdx> that is really exciting
[23:18] <bdx> I've been cursing that bug for a long time
[23:19] <bdx> very nice get deterministic bootstraps
[23:19] <bdx> I feel so at peace