[00:03] <beisner> skylerberg, indeed nova-compute needs to be on metal or in a vm.
[00:04] <skylerberg> beisner: Yeah, it worked out though because I didn't need it to run correctly to check if it set the config properly. Now I am just learning how to make a merge request on launchpad.
[00:06] <skylerberg> beisner: Got it! I now have a merge request proposed for the change I need: https://code.launchpad.net/~sberg-l/charms/trusty/nova-compute/next/+merge/268680
[00:07] <beisner> skylerberg, i won't be able to take a deep dive, but i can confirm that you have it proposed against the right charm in the right place.  woot!   the testing bot will see that and start to give feedback.  once those tests are done, humans will take a deeper look and provide feedback.  appreciate your work!
[00:08] <skylerberg> beisner: Cool! Sounds good.
[00:37] <Egyptian[Home]> hi - when i run juju status or juju debug-log .. nothing happens it just hangs there
[01:10] <Egyptian[Home]> i installed ntp on the maas server and it worked - it was able to deploy and all
[20:07] <puzzolo> ping lazyPower
[20:10] <puzzolo> i am seeing quite some bugs floating on this lxc networking issues. I'll take a look, but something is definitly wrong between lxc networking and juju-br0
[20:15] <lazyPower> puzzolo: i had the talk with dimiter this morning
[20:15] <lazyPower> puzzolo: question about your setup. Are you letting maas manage the networking? or are you using an un-managed network w/ maas?
[20:15] <puzzolo> maas manages dhcp and dns.
[20:16] <puzzolo> on dns side i use a forwarder to resolve external hosts
[20:16] <lazyPower> puzzolo: if maas is managing the network, it cross host container reachability should work ootb
[20:16] <lazyPower> as the containers would be requesting ip addressing from the DHCP server, and get a proper address for the LAN
[20:17] <lazyPower> puzzolo: additionally, the containers should be visible in the MAAS UI
[20:17] <lazyPower> if they are not, its time to start filing bugs, and getting eyeballs on the issue as its probably a localized issue or we've got a gap in our testing coverage
[20:19] <puzzolo> If your setups are working ... problem lays on my libvirt setup with macvlan canibilized bridges
[20:20] <puzzolo> on top of kvm vm passed to maas... and used for containerization by juju
[20:20] <lazyPower> puzzolo: if you could get that configuration posted, along with versions of maas, and juju, and a bundle of the services, we can try to reproduce.
[20:20] <lazyPower> it might be a configuration detail, without having the details of how things are currently configured, its difficult to discern where the root cause is.
[20:27] <puzzolo> i will try a deployment on a physical server. If issue remains i'll post a bug. Is it safe using maas on 15.04?
[20:28] <lazyPower> Certainly
[20:28] <lazyPower> so long as maas is managing the network it should "just work"
[20:34] <puzzolo> once i installed maas i had huge problems resolving outside. I had to manually edit bind9 configuration for outside resolving. Is it normal?
[20:34] <lazyPower> puzzolo: i haven't had that issue myself, the DNS was forwarded when not found.
[20:35] <lazyPower> but that might be a recent change. I haven't had my hands in maas in exess of 4 months.
[20:52] <puzzolo> lost ya after asking
[21:30] <lazyPower> puzzolo: i haven't had that issue myself, the DNS was forwarded when not found.
[21:30] <lazyPower> but that might be a recent change. I haven't had my hands in maas in exess of 4 months.
[21:30] <lazyPower> doh, i should probably re-enable join/part messages