[01:09] <lp|sprint> blr: its currently in preview mode
[01:10] <lp|sprint> blr: marco was working on it for a while, and i'm pretty sure its still in progress as he gets time to get back to it- he was working on turning it into a framework charm
[01:22] <blr> lp|sprint: good to know thanks.
[07:06] <stub> aisrael: Working from UTC+7, but generally stick to around UTC+2 with significant drift
[12:02] <stub> This is driving me nuts. Every time I rebootstrap my local environment, the apt-http-proxy environment setting is being set incorrectly.
[12:03] <stub> Where might this be cached?
[12:05] <stub> In .juju/environments/local.jenv I see the incorrect value in the bootstrap-config: section
[12:06] <stub> apt-mirror is being set no problems, but apt-http-proxy is getting set to http://10.0.3.1:8000, which would be a squid-deb-proxy that no longer exists
[14:06] <lp|sprint> stub: do you have that exported as a juju set env variable?
[14:07] <stub> lp|sprint: It is in my environments.yaml file. If I get-env the value after bootstrap, I get the wrong value. So for now, I'm manually overriding it after bootstrap
[14:08] <lp|sprint> ah, ok
[14:08] <stub> I noticed some code that rewrites localhost URLS to the bridge address so have filed a bug, but I still wonder if it is being pulled from somewhere else.
[14:09] <stub> But /etc/default/lxc*, /etc/lxc don't mention it and I've cleaned out everything juju I can find (templates, caches, the works)
[14:16] <lp|sprint> yeah, thats a bit strange. I dont think i've seen that behavior
[14:32] <aisrael> stub: I have a similar setup in my vagrant image. squid is installed on the host machine, and apt's proxy set in /etc/apt/apt.conf.d
[15:28] <jcastro> mbruzek, sudo docker run --rm -ti --net=host -v $JUJU_HOME:/home/ubuntu/.juju johnsca/charmbox
[16:01] <cory_fu> mbruzek: http://pythonhosted.org/charmhelpers/examples/services.html
[16:31] <web> blr: Thank for the help yesterday.  Already got it working.  Just wish I had time to implement a better algorithm beside roundrobin.  But I did find NGINX is supper close to HAPROXY efficiency.  Especially at my scale. https://jimbesser.wordpress.com/2014/08/13/efficient-load-balancing-and-ssl-termination-for-websockets-and-node-js/
[16:32] <web> But those how-to were well written
[16:34] <web> easier to point multiple namespace to though.
[16:46] <jose> jcastro: scheduling ubuntu on air sessions, will need some details
[16:46] <jcastro> jose, ah good I was just coming to look for you
[16:46] <jose> :)
[16:46] <jcastro> jose, so I set it to recur for every 3 thursdays
[16:47] <jose> recurring doesn't work with airbot, it's manually anyways :P
[16:47] <jcastro> so the one after should be 5/7
[16:47] <jcastro> ok, want me to just invite you to the calendar meeting?
[16:48] <jose> sure, that's fine
[16:49] <jcastro> ugh
[16:49] <jose> if you can tell me who's gonna be on each time, that'd be fantastic
[16:49] <jcastro> I meant 16 April in the email
[16:49] <jcastro> I made a mistake, reposting
[16:49] <jose> insights needs to be corrected too
[16:49] <jcastro> can you set it to "everyone"?
[16:49] <jose> huh?
[16:49] <jose> oh, the people?
[16:50] <jose> I can do that
[16:54] <jcastro> ok everything corrected, invite sent jose
[16:54] <jose> cool, thanks
[16:54] <jose> will schedule in calendar in a minute
[17:04] <mbruzek> cory_fu: https://bugs.launchpad.net/bugs/1419116
[17:04] <mup> Bug #1419116: New trusty/cassandra charm <Juju Charms Collection:Fix Committed> <https://launchpad.net/bugs/1419116>
[17:12] <lukasa> Is it possible for me to use Juju with physical hardware but to not use MAAS? Basically to just point Juju at a set of running machines that already have Trusty installed on them?
[17:12] <jose> lukasa: you could use the manual provider, though things are a bit more complicated
[17:12] <lukasa> jose: How so?
[17:13] <jcastro> https://jujucharms.com/docs/1.20/config-manual
[17:13] <jose> the point with MAAS is that it provisions machines when you need them, and once things are not needed the machines are destroyed
[17:13] <jose> but with manual, Juju is only used to run scripts, but not to manage machines
[17:13] <jose> meaning that if you install something over Juju and want to undo it, you'd have to manually do it
[17:14] <jose> or do a fresh install, then remove from your enviornment and then re-add
[17:14] <lukasa> Sure, but in this case I'm demonstrating in someone else's environment, so I'll have a well-defined deploy.
[17:14] <jcastro> lukasa, that link I posted has everything you need to do a manual deployment
[17:14] <jose> oh, then I believe it suits you :)
[17:14] <lukasa> jcastro: I saw, thankyou. =)
[17:14] <jcastro> though I wish manual wasn't so ... manual.
[17:15] <lukasa> The one question I have is with the bootstrap-host
[17:15] <lukasa> Is it acceptable for bootstrap-host to be my own machine?
[17:15] <jose> if it's going to be constantly connected to all of the other instances, I would say yes
[19:20] <bdx1> mmcc, stokachu: how are things?