[00:21] anastasiamac_: I am about 500 m from that but yes, my house is in slight higher ground [00:46] jw4: sorry mate, I dont understand the implications of your change enough to review it [00:46] perrito666: I'm quite disappointed [00:47] perrito666: :) [00:47] s*** happens [00:47] :) [00:49] ok, definitely I need a reset, see you all tomorrow [00:50] * perrito666 pulls the plug from the back of his head and falls out of the matrix into his kindle [00:51] lol [01:07] axw: oh hai mr on call reviewer [01:07] axw: http://reviews.vapour.ws/r/952/ [01:07] thumper: i think he's on holiday [01:07] :( [01:07] thumper: for the lunar new year [01:08] ah, I see yes, that is on the calendar [01:08] I was just looking for the reviewer [01:08] wallyworld: this one is quick: [01:08] thumper: for "the" reviewer or "a" reviewer? [01:08] sure, that's what you always say [01:08] wallyworld: helps out sinzui and abentley re bug https://bugs.launchpad.net/juju-core/+bug/1421237 [01:08] Bug #1421237: DEBUG messages show when only INFO was asked for

[01:08] looking [01:09] thank you thumper [01:09] sinzui: np [01:09] New golang dev in #juju, if someone has a moment to stop in and greet them, potential contributor. [01:10] name: hnix [01:10] thumper: I would say ship it, but it has little value :p [01:10] perrito666: heh, but thanks anyway [01:10] perrito666: thumper: same here [01:10] perrito666: maybe collectively our vote adds up to 1? [01:11] lazyPower: don't suppose that is 'hiro black sun' on google? [01:11] Not sure, is there a correlation i should be aware of? [01:12] only that someone requested access to a private canonical spec [01:12] not even sure how they found it existed [01:12] wallyworld: I have to run to the doctors shortly, if you approve, please attempt to merge [01:13] wallyworld: and I'll forward port to master [01:13] sure [01:13] cheers [01:13] thumper: i'm suggesting another test [01:13] i'll add to commet [01:13] wallyworld: for the default? [01:13] yeah [01:13] wallyworld: it is there already [01:13] just not obviously [01:13] * thumper finds it [01:13] convert the new test to a help [01:13] er [01:13] ah ok [01:14] line 277 [01:14] of the cloutinit_test [01:14] those tests are horrible [01:14] and should be rewritten fully [01:14] I repeatedly want to gouge my own eyes out when I have do change them [01:14] thumper: hey, don't. we need those eyes. [01:15] ok... really gotta run now, or I'll be late for appt === thumper is now known as thumper-afk [01:15] thumper: ok, np, i'll +1 [01:16] wallyworld: standup? === kadams54 is now known as kadams54-away [02:47] sinzui: fix landed in 1.22, forward porting to 1.23 === thumper-afk is now known as thumper [02:48] \o/ [04:08] wallyworld: quick thing to pass by you. you were part of the "juju status --format=tabular" right ? [04:10] menn0: I sent you an email about my benchmarking script [04:10] well, scale testing script [04:10] I was putting it together for testing out different DB backends, but I think it would fit quite well with what you're trying to do === kadams54 is now known as kadams54-away [04:10] we might want to add something like "--debug-log" which makes us much more chatty [04:13] jam: yes, eco floks had a fair bit of input on requirements, katherine did the work [04:13] wallyworld: sure. I just sent an email to juju-dev for what could be a nice improvement. [04:13] Specifically, use number sorted order rather than just string order. [04:14] jam: ah yes, just saw it. the age old problem. yep, we can do that easily. [04:14] If you want, there is "natural sort" which handles mixing numbers inside the string, but just sorting alphabetically except for the unit number by number would be nice. [04:14] i'll get that done next week [04:14] so we make the cut off [05:11] wallyworld: can we talk about destroy environment? [05:11] sure [05:11] wallyworld: use our 1:1 hangout [05:28] night all [05:29] wallyworld: I'm running into problems with LXC stuff. Want me to just file an LP bug, or work on it with you [05:30] jam: what sort of issues? [05:30] lxc is failing to create containers. Let me paste the error [05:31] wallyworld: http://paste.ubuntu.com/10302503/ [05:31] I *think* the failure in that garble is: [05:31] Connecting to 10.102.0.39:17070... connected.; HTTP request sent, awaiting [05:31] response... 500 Internal Server Error; 2015-02-19 05:19:33 ERROR 500: Internal [05:31] Server Error.; [05:31] given the ports, that looks like something is trying to connect back to the API server, and getting a 500 ISE [05:32] jam: looks like cloud-image-utils is not installed [05:32] there should have been a check for that [05:32] is this local provider? [05:33] wallyworld: ec2 [05:33] jam: what version of juju? [05:33] wallyworld: trunk [05:33] precise image? [05:33] wallyworld: pretty sure trusty [05:33] yeah, trusty [05:34] hmmm. let me check, there should have been apt-get cloud-image-utils added to init sctips [05:34] wallyworld: I was trying to do a scale test with containers [05:34] http://paste.ubuntu.com/10302530/ [05:34] thats the full status output, which is a bit verbose [05:36] wallyworld: afaict cloud-image-utils is, indeed, not installed on machine-0 [05:37] jam: ah, i know. in cloudinit.go, c.AddPackage("cloud-image-utils") is missing [05:38] that caused issues on precise till just recently [05:38] trusty should have been ok; it worked for me [05:38] i guess it depends on the image you get [05:38] for now, you can add that line, and i will do a simple fix [05:39] wallyworld: I'm trying this out on us-wesw-1 [05:39] us-west-1 maybe it has an older trusty image? [05:39] could do, yeah, not sure [05:39] wallyworld: want an explicit bug? [05:40] i can raise it [05:40] It feels like we need to understand this a bit more [05:40] the issue is that cloud-image-utils needs to be installed [05:40] otherwise juju can't determine the url to download the image from [05:41] we were installing cloud-image-utils but a packaging bug broke precise [05:41] that upstream deb fix got into cloud archie today i think [05:41] so we can add back the apt install of that package [05:43] wallyworld: damned if you do, damned if you don't sounds like a bad place to be in [05:43] yeah, bt it's all fixed now [05:44] just got to add back the apt install [05:44] i'm surprised it failed on trusty [05:44] trusty onwards should have been ok; well, it has been for me [05:45] we just had to get the deb packaging fixed on precise which has now been done to make precise good too [05:45] wallyworld: i'm trying to reproduce with a simple case [05:52] wow, juju bootstrap took 7m26s [05:55] hmm... this bootstrap seems to have cloud-image-utils available already... [05:55] yeah, go figure [05:56] only thing I can think of is instance size, but that shouldn't affect it IMO [05:59] i don't think so either [06:14] jam: i've raised bug 1423454, it's a one line fix which i'll do now [06:15] Bug #1423454: cloud-image-utils needs to be installed [06:20] thanks wallyworld === mup_ is now known as mup === mup__ is now known as mup [07:38] wallyworld: poke === tasdomas` is now known as tasdomas === \b is now known as benonsoftware [08:17] Hi [08:18] I need some help in opensatck jujucharms [08:19] we deployed the openstack-dash board and keystone in one node [08:19] mysql and rabbtmq in other node [08:19] but we able to launch the horizon dashboard but couldnt able to login [08:19] ceadentails are not accepting [08:20] credentials not accepted [08:20] we added admin-password : openstack while deploying the keystone [08:21] could someone help us to come out of this issue?? [08:22] or please redirect to right to conatct [08:30] jam: hi [08:31] jamespage: are you able to point Murali ^^^^^ to someone who can help [08:35] wallyworld: was just prepping if you had anything else for me to bring before mark [08:35] but it got moved to Monday [08:35] ah, np, thanks for asking [08:36] the storage CLI is the ot topic atm [08:36] hot [08:37] Murali, hey [08:37] Murali, when you say " in one node" how exactly have you done that - not all charms support being placed in the same container [08:38] Murali: https://wiki.ubuntu.com/ServerTeam/OpenStackCharms/ProviderColocationSupport [08:39] Hi Jamespage [08:39] we are running the MAAS [08:39] and we have multiple nodes connected [08:40] in bootstrap node we deployed mysql and rabbitmq [08:40] Murali, are you using LXC containers? [08:40] (see the doc I referenced above) [08:43] we are not using LXC containers jamespage [08:43] Murali, please do - basically if you deploy keystone and horizon in the same container, one or the other will not function correctly [08:43] our juju env is MAAS [08:43] Murali, you can use LXC and KVM with MAAS [08:43] Murali, [08:43] juju deploy --to lxc:0 mysql [08:43] for example [08:44] Juju will create the container and deploy the charm to it [08:44] lxc:0 means an LXC container on machine 0 [08:44] ohh ok [08:44] Murali, you may find https://jujucharms.com/openstack/ useful as well - that's a 4 node MAAS deployment of openstack using containers where possible [08:47] will go through this deployment and try thanks jamespage [08:47] thanks a lot for your kind response [08:47] Murali, np [08:47] Murali, feel free to ping me or gnuoy with questions if you have them [08:48] Murali, better on #juju so we don't distract these busy juju developers :-) [08:48] thanks for the ping wallyworld [08:48] ok wll move #juju [08:48] sure, i wasn't sure who else to ask, thanks for looking [08:50] fwereade: hey, tim made me promise i'd nag you until you looked at his JES document before tomorrow === mup_ is now known as mup [08:57] wallyworld, cheers [09:34] morning [09:39] perrito666: o/ [11:56] TheMue, dimitern: https://nanosheep.org/Publicly-addressable-LXC/ [11:56] dooferlad: *click* [11:57] dooferlad, sweet! thanks - will give it a try later today [11:58] dooferlad: cool stuff [11:58] dooferlad: just created site? [11:59] TheMue: Yea, I used http://gohugo.io/ because now everything has to be related to go :-D [11:59] dooferlad: oh, never heard of it, will take a look here too. I'm not so happy with the software I use for my tideland blog [12:00] TheMue: It basically converts markdown into HTML and applies a theme. After that it is a static site. [12:01] * dooferlad gets lunch [12:01] dooferlad: that is fine for me. just seen that Dave is quoted *lol* [12:22] oh man, CI still blocked? [12:50] perrito666: it wasn't just a minute ago when I did a $$merge [12:52] oh, ok :p [12:52] our topic seems to be really out of sync with that [12:52] perrito666: yeah, we should make the bot do it [12:54] sounds like a good idea, block-sync-bot [12:58] pretty sure the source for our bot is in LP somewhere and I believe the blocking bugs are exposed via some HTTP resource [12:58] so assuming my assumptions are correct, should be pretty easy :P [12:58] wwitzel3: you are missing the key part, we are extremely lazy [12:59] *lol* [12:59] perrito666: I explictly said "should" [12:59] perrito666: I didn't say anyone actually would do it [12:59] haha [13:00] we need interns [13:00] we would just teach them to be lazy [13:00] vicious cycle [13:00] wwitzel3: nah, i usually teach the interns to be useful, they learn the lazy part all by themselves [13:01] last time I had training interns (i had to teach them python+django) I got the website for my wedding [13:11] perrito666: hah, nice === frankban__ is now known as frankban [14:14] ericsnow: ping [14:41] question regarding ssh key exchange during juju ssh - i redeployed a host and now i'm getting ssh-key-exchange errors when trying to juju ssh into that unit - its 100% likely that the host ssh key changed since its a new host - is there an authorized keys file i need to update? === kadams54 is now known as kadams54-away [14:51] dooferlad, how goes the port of bug 1416928 to master [14:51] Bug #1416928: juju agent using lxcbr0 address as apiaddress instead of juju-br0 breaks agents

[14:52] sinzui: not long [14:52] thank you dooferlad === kadams54-away is now known as kadams54 [15:04] ericsnow: wwitzel3 ? [15:05] perrito666: perhaps you have not *joined* the hangout [15:05] perrito666: we are both here [15:48] TheMue, dimitern: http://reviews.vapour.ws/r/960/diff should be familiar :-) [15:48] dooferlad: I'll take a look [15:51] dooferlad, cheers, looking [16:05] dooferlad, LGTM [16:05] dooferlad, + a quick test [16:05] dimitern: Yea, I did manual and MAAS tests [16:06] dooferlad, cool - all ok then? [16:06] yep [16:06] dimitern: ^^ [16:08] dooferlad, then $$great$$ :) [16:14] dimitern, does juju-br0 hardcode to eth0? [16:15] dimitern, helping someone in #juju who does not have ethX naming on their boxes [16:15] and the bridge is not wired properly [16:22] jamespage, no, it defaults to the "primary" nic [16:23] dimitern, ack - the user is using a 1.21.1 release of juju [16:23] jamespage, i.e. whatever we can see in lshw xml dump during machine commissioning [16:24] jamespage, that might be interesting.. I'll have a look if the fix to pick the "correct" primary nic was already in place in 1.21.1 === kadams54 is now known as kadams54-away [16:57] ericsnow: tx for the review [16:57] perrito666: hope it helps === kadams54-away is now known as kadams54 [17:07] dimitern: in the client API MachineNetworkInfo returns network.InterfaceInfo. so imho renaming Info to Config makes no sense here, or InterfaceInfo would have to be renamed too [17:08] dimitern: just thinking about it [17:09] TheMue, we'll need to straighten those terms across the code base and make them consistent [17:09] dimitern: yeah, and here we have multiple possibilities [17:12] TheMue, as always :) [17:12] dimitern: renaming MachineNetworkInfo to MachineNetworkConfig (or better: add a second and call it) would make it consistent with the server side [17:12] dimitern: still it returns InterfaceInfo [17:12] dimitern: but this could be a third step ;) [17:13] TheMue, some of those API methods will need to either go away or be refactored anyway [17:14] dimitern: ok, so I'll start with a simple renaming. server now likes both names. [18:04] cmars, team meeting?? [18:46] cmars: thank you, I was seconds away of being nominated to lead by alexisb [18:46] perrito666, heh cool. just in time :) distracted by email.. so much of it today [19:04] FYI, I copied out the 2013 and 2014 "agendas" into their own docs (and added links and a TOC to the 2015 doc) [19:05] so the current doc is only 8 pages now [19:06] hope that helps, perrito666 :) [19:09] ericsnow: by the time it gets to 40 again I hope Ill have managed to change computers [19:09] ericsnow: tx a lot === kadams54 is now known as kadams54-away === kadams54-away is now known as kadams54 === kadams54 is now known as kadams54-away === kadams54-away is now known as kadams54 [20:39] ericsnow, wwitzel3: where are you guys on responding to the review comments of GCE? [20:39] natefinch: yep [20:42] ericsnow: reread my question :) Asking how it's going :) [20:42] natefinch: ha, missed "where" [20:43] natefinch: wwitzel3 has done a lot and I'm planning on tackling some today [20:43] natefinch: well you did not specify the type of your question, ericsnow just answered got casted to bool [20:43] natefinch: none of them look like show stoppers [20:44] ericsnow: cool [20:44] perrito666: heh [20:44] func WhereAreYouOnGCE() string {} [20:45] I guess "yep" still qualifies ;) [20:45] troll python programmer is troll === kadams54 is now known as kadams54-away [21:35] ericsnow: ping [21:35] thumper: hey [21:36] ericsnow: I hear you have some concerns around logging and mongo, wanna chat about it? [21:36] wwitzel3: you around too? [21:36] thumper: sure [21:36] menn0: perhaps a logging hangout [21:36] * thumper makes [21:36] menn0, ericsnow, wwitzel3: https://plus.google.com/hangouts/_/canonical.com/logging [21:37] thumper: wwitzel3 had some specific feedback and more familiarlity with the topic... [21:38] ericsnow: I had a chat with wwitzel3 the other day === ChanServ changed the topic of #juju-dev to: https://juju.ubuntu.com | On-call reviewer: see calendar | Open critical bugs: 1423036 [22:12] thumper: sorry I missed that hangout - was at swimming [22:13] thumper: what did I miss? [22:15] menn0: you've got to fix it all by EOD, that'll teach you to go swimming :) [22:15] rick_h_: ha [22:47] thumper: did william look atyour doc? i asked him to and he said he would [22:48] wallyworld: don't know [22:48] didn't see any comments [22:48] bet he didn't :-) === kadams54-away is now known as kadams54 [23:46] sinzui: i think this will work? "apt-get install --target-release precise-updates/cloud-tools cloud-utils" followed by "apt-get install --target-release precise-updates/cloud-tools cloud-image-utils" [23:46] ie 2 individual commands but specifying where the packages are to come from [23:51] axw: hey, can you ping me when you're on?