[01:54] <aisrael> I think I've got something funky going on with my dns on wily w/juju 1.25. It'll work, then stop (can't resolve internal dns), then start working again. At the same time, I'm having deployed machines able to resolve names but not connect (i.e., apt-get update)
[01:57] <aisrael> Ok, that last part gets fixed by restarting lxc-net (a side-effect of my iptables script to port forward to containers.
[02:31] <blahdeblah> aisrael: I experience that all the time completely without respect to juju
[02:32] <blahdeblah> NetworkManager seems to be very stop-start when it comes to rational DNS resolution.
[02:33] <aisrael> blahdeblah: So I've noticed. The quickest way to get it back is to ssh in and restart nm. I'm combing logs now to try to find what's getting run that confuses it
[02:34] <blahdeblah> It has been like that since at least trusty; I got into the habit of adding /etc/hosts entries for anything important.  I probably should rather start debugging it a little and submit bugs against NM.
[04:47] <DarkNet> oh, so sad. this is not about jujujoints :(
[06:45] <blahdeblah> lazypower: I've read your DNS charm documentation today for the 2nd time, and I'm still trying to work out whether it's what I should be using for my particular application.  If you're around late in your day sometime, would you mind me picking your brain about it for a few minutes?
[08:26] <gnuoy> jamespage, Could I get a second opinion on https://code.launchpad.net/~ionutbalutoiu/charms/trusty/neutron-gateway/next/+merge/276833 ? I'm inclined to merge it and add a comment to config.yaml saying "if you need to use this config option please consider filing a bug against the charm to explicitly expose the config option you are setting"
[08:27] <gnuoy> or words to that effect that actually make sense
[09:15] <jamespage> gnuoy, agreed - and some unit tests would also be nice
[16:42] <jose> arosales: hey, good news! we got accepted into Google Code-In - we're on the search for tasks right now :)
[16:46] <arosales> jose: woot!
[16:46] <arosales> jose: good to hear
[16:46] <arosales> jose we can certainly help with tasks :-)
[16:47] <jose> \o/
[16:47] <arosales> jose: would you like me to just send them to you or do you have have a google doc, git-hub page, or something I can reference?
[16:49] <jose> arosales: google doc is fine. marcoceppi offered to be a mentor I believe, so maybe you can work with him, or if you want you can be a mentor too
[16:52] <arosales> jose: I would be interested. I am not sure how the whole process works, but I would like to learn more and work with you to make it sucessfull.
[16:53] <arosales> jose: would you perfet github repo or google doc?
[16:53] <jose> arosales: google doc works for me - I'm working on mobile a lot and it's easier to access :)
[16:53] <arosales> jose: oh, I was talking more long term too, not just for today
[16:54] <jose> arosales: yeah, university schedule keeps me here 7am-8pm :D
[16:54] <jose> and semester finishes second week of december
[16:54] <arosales> I bet  :-)
[16:54] <jose> so, mentors are basically the ones who publish tasks and review that they have been done
[16:54] <jose> and if students have any questions about an specific task they can ask the mentor they published
[16:54] <jose> yes, it's easy as it sounds
[17:01] <arosales> jose: I made https://docs.google.com/document/d/1ZFAJiuml59dF_1qJmCmrTqRoJxQRJddcL3baxnkmoh8/edit just for the initial plannin
[17:01] <arosales> open to anyone if anyone elses has any ides