[01:09] blr: its currently in preview mode [01:10] 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] lp|sprint: good to know thanks. [07:06] aisrael: Working from UTC+7, but generally stick to around UTC+2 with significant drift === brandon is now known as Guest73551 === Guest73551 is now known as web [12:02] This is driving me nuts. Every time I rebootstrap my local environment, the apt-http-proxy environment setting is being set incorrectly. [12:03] Where might this be cached? [12:05] In .juju/environments/local.jenv I see the incorrect value in the bootstrap-config: section [12:06] 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] stub: do you have that exported as a juju set env variable? [14:07] 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] ah, ok [14:08] 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] 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] yeah, thats a bit strange. I dont think i've seen that behavior [14:32] 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] mbruzek, sudo docker run --rm -ti --net=host -v $JUJU_HOME:/home/ubuntu/.juju johnsca/charmbox === rvba` is now known as rvba [16:01] mbruzek: http://pythonhosted.org/charmhelpers/examples/services.html === jcastro changed the topic of #juju to: Welcome to Juju! || Office Hours, here 16 April 2000UTC || Docs: http://juju.ubuntu.com/docs || FAQ: http://goo.gl/MsNu4I || Review Queue: http://review.juju.solutions || Unanswered Questions: http://goo.gl/dNj8CP === brandon is now known as Guest81584 === Guest81584 is now known as web [16:31] 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] But those how-to were well written === natefinch is now known as natefinch-afk [16:34] easier to point multiple namespace to though. [16:46] jcastro: scheduling ubuntu on air sessions, will need some details [16:46] jose, ah good I was just coming to look for you [16:46] :) [16:46] jose, so I set it to recur for every 3 thursdays [16:47] recurring doesn't work with airbot, it's manually anyways :P [16:47] so the one after should be 5/7 [16:47] ok, want me to just invite you to the calendar meeting? [16:48] sure, that's fine [16:49] ugh [16:49] if you can tell me who's gonna be on each time, that'd be fantastic [16:49] I meant 16 April in the email [16:49] I made a mistake, reposting [16:49] insights needs to be corrected too [16:49] can you set it to "everyone"? [16:49] huh? [16:49] oh, the people? [16:50] I can do that [16:54] ok everything corrected, invite sent jose [16:54] cool, thanks [16:54] will schedule in calendar in a minute [17:04] cory_fu: https://bugs.launchpad.net/bugs/1419116 [17:04] Bug #1419116: New trusty/cassandra charm [17:12] 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] lukasa: you could use the manual provider, though things are a bit more complicated [17:12] jose: How so? [17:13] https://jujucharms.com/docs/1.20/config-manual [17:13] 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] but with manual, Juju is only used to run scripts, but not to manage machines [17:13] meaning that if you install something over Juju and want to undo it, you'd have to manually do it [17:14] or do a fresh install, then remove from your enviornment and then re-add [17:14] Sure, but in this case I'm demonstrating in someone else's environment, so I'll have a well-defined deploy. [17:14] lukasa, that link I posted has everything you need to do a manual deployment [17:14] oh, then I believe it suits you :) [17:14] jcastro: I saw, thankyou. =) [17:14] though I wish manual wasn't so ... manual. [17:15] The one question I have is with the bootstrap-host [17:15] Is it acceptable for bootstrap-host to be my own machine? [17:15] if it's going to be constantly connected to all of the other instances, I would say yes === natefinch-afk is now known as natefinch === brandon is now known as Guest55960 === mup_ is now known as mup [19:20] mmcc, stokachu: how are things? === brandon is now known as Guest90393 === Guest90393 is now known as web === anthonyf is now known as Guest42183