[00:21] <perrito666> anastasiamac_: I am about 500 m from that but yes, my house is in slight higher ground
[00:46] <perrito666> jw4: sorry mate, I dont understand the implications of your change enough to review it
[00:46] <jw4> perrito666: I'm quite disappointed
[00:47] <jw4> perrito666: :)
[00:47] <perrito666> s*** happens
[00:47] <jw4> :)
[00:49] <perrito666> 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] <jw4> lol
[01:07] <thumper> axw: oh hai mr on call reviewer
[01:07] <thumper> axw: http://reviews.vapour.ws/r/952/
[01:07] <katco> thumper: i think he's on holiday
[01:07] <thumper> :(
[01:07] <katco> thumper: for the lunar new year
[01:08] <thumper> ah, I see yes, that is on the calendar
[01:08] <thumper> I was just looking for the reviewer
[01:08] <thumper> wallyworld: this one is quick:
[01:08] <anastasiamac_> thumper: for "the" reviewer or "a" reviewer?
[01:08] <wallyworld> sure, that's what you always say
[01:08] <thumper> wallyworld: helps out sinzui and abentley re bug https://bugs.launchpad.net/juju-core/+bug/1421237
[01:08] <mup> Bug #1421237: DEBUG messages show when only INFO was asked for <ci> <security> <juju-core:In Progress by thumper> <https://launchpad.net/bugs/1421237>
[01:08] <wallyworld> looking
[01:09] <sinzui> thank you thumper
[01:09] <thumper> sinzui: np
[01:09] <lazyPower> New golang dev in #juju, if someone has a moment to stop in and greet them, potential contributor.
[01:10] <lazyPower> name: hnix
[01:10] <perrito666> thumper: I would say ship it, but it has little value :p
[01:10] <thumper> perrito666: heh, but thanks anyway
[01:10] <katco> perrito666: thumper: same here
[01:10] <katco> perrito666: maybe collectively our vote adds up to 1?
[01:11] <thumper> lazyPower: don't suppose that is 'hiro black sun' on google?
[01:11] <lazyPower> Not sure, is there a correlation i should be aware of?
[01:12] <thumper> only that someone requested access to a private canonical spec
[01:12] <thumper> not even sure how they found it existed
[01:12] <thumper> wallyworld: I have to run to the doctors shortly, if you approve, please attempt to merge
[01:13] <thumper> wallyworld: and I'll forward port to master
[01:13] <wallyworld> sure
[01:13] <thumper> cheers
[01:13] <wallyworld> thumper: i'm suggesting another test
[01:13] <wallyworld> i'll add to commet
[01:13] <thumper> wallyworld: for the default?
[01:13] <wallyworld> yeah
[01:13] <thumper> wallyworld: it is there already
[01:13] <thumper> just not obviously
[01:13]  * thumper finds it
[01:13] <wallyworld> convert the new test to a help
[01:13] <wallyworld> er
[01:13] <wallyworld> ah ok
[01:14] <thumper> line 277
[01:14] <thumper> of the cloutinit_test
[01:14] <thumper> those tests are horrible
[01:14] <thumper> and should be rewritten fully
[01:14] <thumper> I repeatedly want to gouge my own eyes out when I have do change them
[01:14] <katco> thumper: hey, don't. we need those eyes.
[01:15] <thumper> ok... really gotta run now, or I'll be late for appt
[01:15] <wallyworld> thumper: ok, np, i'll +1
[01:16] <anastasiamac_> wallyworld: standup?
[02:47] <thumper-afk> sinzui: fix landed in 1.22, forward porting to 1.23
[02:48] <sinzui> \o/
[04:08] <jam> wallyworld: quick thing to pass by you. you were part of the "juju status --format=tabular" right ?
[04:10] <jam> menn0: I sent you an email about my benchmarking script
[04:10] <jam> well, scale testing script
[04:10] <jam> 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
[04:10] <jam> we might want to add something like "--debug-log" which makes us much more chatty
[04:13] <wallyworld> jam: yes, eco floks had a fair bit of input on requirements, katherine did the work
[04:13] <jam> wallyworld: sure. I just sent an email to juju-dev for what could be a nice improvement.
[04:13] <jam> Specifically, use number sorted order rather than just string order.
[04:14] <wallyworld> jam: ah yes, just saw it. the age old problem. yep, we can do that easily.
[04:14] <jam> 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] <wallyworld> i'll get that done next week
[04:14] <wallyworld> so we make the cut off
[05:11] <thumper> wallyworld: can we talk about destroy environment?
[05:11] <wallyworld> sure
[05:11] <thumper> wallyworld: use our 1:1 hangout
[05:28] <thumper> night all
[05:29] <jam> 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] <wallyworld> jam: what sort of issues?
[05:30] <jam> lxc is failing to create containers. Let me paste the error
[05:31] <jam> wallyworld: http://paste.ubuntu.com/10302503/
[05:31] <jam> I *think* the failure in that garble is:
[05:31] <jam> Connecting to 10.102.0.39:17070... connected.; HTTP request sent, awaiting
[05:31] <jam>           response... 500 Internal Server Error; 2015-02-19 05:19:33 ERROR 500: Internal
[05:31] <jam>           Server Error.;
[05:31] <jam> given the ports, that looks like something is trying to connect back to the API server, and getting a 500 ISE
[05:32] <wallyworld> jam: looks like cloud-image-utils is not installed
[05:32] <wallyworld> there should have been a check for that
[05:32] <wallyworld> is this local provider?
[05:33] <jam> wallyworld: ec2
[05:33] <wallyworld> jam: what version of juju?
[05:33] <jam> wallyworld: trunk
[05:33] <wallyworld> precise image?
[05:33] <jam> wallyworld: pretty sure trusty
[05:33] <jam> yeah, trusty
[05:34] <wallyworld> hmmm. let me check, there should have been apt-get cloud-image-utils added to init sctips
[05:34] <jam> wallyworld: I was trying to do a scale test with containers
[05:34] <jam> http://paste.ubuntu.com/10302530/
[05:34] <jam> thats the full status output, which is a bit verbose
[05:36] <jam> wallyworld: afaict cloud-image-utils is, indeed, not installed on machine-0
[05:37] <wallyworld> jam: ah, i know. in cloudinit.go, c.AddPackage("cloud-image-utils") is missing
[05:38] <wallyworld> that caused issues on precise till just recently
[05:38] <wallyworld> trusty should have been ok; it worked for me
[05:38] <wallyworld> i guess it depends on the image you get
[05:38] <wallyworld> for now, you can add that line, and i will do a simple fix
[05:39] <jam> wallyworld: I'm trying this out on us-wesw-1
[05:39] <jam> us-west-1 maybe it has an older trusty image?
[05:39] <wallyworld> could do, yeah, not sure
[05:39] <jam> wallyworld: want an explicit bug?
[05:40] <wallyworld> i can raise it
[05:40] <jam> It feels like we need to understand this a bit more
[05:40] <wallyworld> the issue is that cloud-image-utils needs to be installed
[05:40] <wallyworld> otherwise juju can't determine the url to download the image from
[05:41] <wallyworld> we were installing cloud-image-utils but a packaging bug broke precise
[05:41] <wallyworld> that upstream deb fix got into cloud archie today i think
[05:41] <wallyworld> so we can add back the apt install of that package
[05:43] <jam> wallyworld: damned if you do, damned if you don't sounds like a bad place to be in
[05:43] <wallyworld> yeah, bt it's all fixed now
[05:44] <wallyworld> just got to add back the apt install
[05:44] <wallyworld> i'm surprised it failed on trusty
[05:44] <wallyworld> trusty onwards should have been ok; well, it has been for me
[05:45] <wallyworld> we just had to get the deb packaging fixed on precise which has now been done to make precise good too
[05:45] <jam> wallyworld: i'm trying to reproduce with a simple case
[05:52] <jam> wow, juju bootstrap took 7m26s
[05:55] <jam> hmm... this bootstrap seems to have cloud-image-utils available already...
[05:55] <wallyworld> yeah, go figure
[05:56] <jam> only thing I can think of is instance size, but that shouldn't affect it IMO
[05:59] <wallyworld> i don't think so either
[06:14] <wallyworld> jam: i've raised bug 1423454, it's a one line fix which i'll do now
[06:15] <mup> Bug #1423454: cloud-image-utils needs to be installed <juju-core:In Progress by wallyworld> <https://launchpad.net/bugs/1423454>
[06:20] <jam> thanks wallyworld
[07:38] <jam> wallyworld: poke
[08:17] <Murali> Hi
[08:18] <Murali> I need some help in opensatck jujucharms
[08:19] <Murali> we deployed the openstack-dash board and keystone in one node
[08:19] <Murali> mysql and rabbtmq in other node
[08:19] <Murali> but we able to launch the horizon dashboard but couldnt able to login
[08:19] <Murali> ceadentails are not accepting
[08:20] <Murali> credentials not accepted
[08:20] <Murali> we added admin-password : openstack while deploying the keystone
[08:21] <Murali> could someone help us to come out of this issue??
[08:22] <Murali> or please redirect to right to conatct
[08:30] <wallyworld> jam: hi
[08:31] <wallyworld> jamespage: are you able to point Murali ^^^^^ to someone who can help
[08:35] <jam> wallyworld: was just prepping if you had anything else for me to bring before mark
[08:35] <jam> but it got moved to Monday
[08:35] <wallyworld> ah, np, thanks for asking
[08:36] <wallyworld> the storage CLI is the ot topic atm
[08:36] <wallyworld> hot
[08:37] <jamespage> Murali, hey
[08:37] <jamespage> 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] <jamespage> Murali: https://wiki.ubuntu.com/ServerTeam/OpenStackCharms/ProviderColocationSupport
[08:39] <Murali> Hi Jamespage
[08:39] <Murali> we are running the MAAS
[08:39] <Murali> and we have multiple nodes connected
[08:40] <Murali> in bootstrap node we deployed mysql and rabbitmq
[08:40] <jamespage> Murali, are you using LXC containers?
[08:40] <jamespage> (see the doc I referenced above)
[08:43] <Murali> we are not using LXC containers jamespage
[08:43] <jamespage> Murali, please do - basically if you deploy keystone and horizon in the same container, one or the other will not function correctly
[08:43] <Murali> our juju env is MAAS
[08:43] <jamespage> Murali, you can use LXC and KVM with MAAS
[08:43] <jamespage> Murali,
[08:43] <jamespage> juju deploy --to lxc:0 mysql
[08:43] <jamespage> for example
[08:44] <jamespage> Juju will create the container and deploy the charm to it
[08:44] <jamespage> lxc:0 means an LXC container on machine 0
[08:44] <Murali> ohh ok
[08:44] <jamespage> 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] <Murali> will go through this deployment and try thanks jamespage
[08:47] <Murali> thanks a lot for your kind response
[08:47] <jamespage> Murali, np
[08:47] <jamespage> Murali, feel free to ping me or gnuoy with questions if you have them
[08:48] <jamespage> Murali, better on #juju so we don't distract these busy juju developers :-)
[08:48] <jamespage> thanks for the ping wallyworld
[08:48] <Murali> ok wll move #juju
[08:48] <wallyworld> sure, i wasn't sure who else to ask, thanks for looking
[08:50] <wallyworld> fwereade: hey, tim made me promise i'd nag you until you looked at his JES document before tomorrow
[08:57] <fwereade> wallyworld, cheers
[09:34] <perrito666> morning
[09:39] <TheMue> perrito666: o/
[11:56] <dooferlad> TheMue, dimitern: https://nanosheep.org/Publicly-addressable-LXC/
[11:56] <TheMue> dooferlad: *click*
[11:57] <dimitern> dooferlad, sweet! thanks - will give it a try later today
[11:58] <TheMue> dooferlad: cool stuff
[11:58] <TheMue> dooferlad: just created site?
[11:59] <dooferlad> TheMue: Yea, I used http://gohugo.io/ because now everything has to be related to go :-D
[11:59] <TheMue> 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] <dooferlad> 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] <TheMue> dooferlad: that is fine for me. just seen that Dave is quoted *lol*
[12:22] <perrito666> oh man, CI still blocked?
[12:50] <wwitzel3> perrito666: it wasn't just a minute ago when I did a $$merge
[12:52] <perrito666> oh, ok :p
[12:52] <perrito666> our topic seems to be really out of sync with that
[12:52] <wwitzel3> perrito666: yeah, we should make the bot do it
[12:54] <TheMue> sounds like a good idea, block-sync-bot
[12:58] <wwitzel3> 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] <wwitzel3> so assuming my assumptions are correct, should be pretty easy :P
[12:58] <perrito666> wwitzel3: you are missing the key part, we are extremely lazy
[12:59] <TheMue> *lol*
[12:59] <wwitzel3> perrito666: I explictly said "should"
[12:59] <wwitzel3> perrito666: I didn't say anyone actually would do it
[12:59] <wwitzel3> haha
[13:00] <perrito666> we need interns
[13:00] <wwitzel3> we would just teach them to be lazy
[13:00] <wwitzel3> vicious cycle
[13:00] <perrito666> wwitzel3: nah, i usually teach the interns to be useful, they learn the lazy part all by themselves
[13:01] <perrito666> last time I had training interns (i had to teach them python+django) I got the website for my wedding
[13:11] <wwitzel3> perrito666: hah, nice
[14:14] <wwitzel3> ericsnow: ping
[14:41] <lazyPower> 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?
[14:51] <sinzui> dooferlad, how goes the port of bug 1416928 to master
[14:51] <mup> Bug #1416928: juju agent using lxcbr0 address as apiaddress instead of juju-br0 breaks agents <api> <lxc> <network> <juju-core:In Progress by dooferlad> <juju-core 1.21:Fix Released by dimitern> <juju-core 1.22:Fix Released by dooferlad> <https://launchpad.net/bugs/1416928>
[14:52] <dooferlad> sinzui: not long
[14:52] <sinzui> thank you dooferlad
[15:04] <perrito666> ericsnow: wwitzel3 ?
[15:05] <ericsnow> perrito666: perhaps you have not *joined* the hangout <wink>
[15:05] <ericsnow> perrito666: we are both here
[15:48] <dooferlad> TheMue, dimitern: http://reviews.vapour.ws/r/960/diff should be familiar :-)
[15:48] <TheMue> dooferlad: I'll take a look
[15:51] <dimitern> dooferlad, cheers, looking
[16:05] <dimitern> dooferlad, LGTM
[16:05] <dimitern> dooferlad, + a quick test
[16:05] <dooferlad> dimitern: Yea, I did manual and MAAS tests
[16:06] <dimitern> dooferlad, cool - all ok then?
[16:06] <dooferlad> yep
[16:06] <dooferlad> dimitern: ^^
[16:08] <dimitern> dooferlad, then $$great$$ :)
[16:14] <jamespage> dimitern, does juju-br0 hardcode to eth0?
[16:15] <jamespage> dimitern, helping someone in #juju who does not have ethX naming on their boxes
[16:15] <jamespage> and the bridge is not wired properly
[16:22] <dimitern> jamespage, no, it defaults to the "primary" nic
[16:23] <jamespage> dimitern, ack - the user is using a 1.21.1 release of juju
[16:23] <dimitern> jamespage, i.e. whatever we can see in lshw xml dump during machine commissioning
[16:24] <dimitern> 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
[16:57] <perrito666> ericsnow: tx for the review
[16:57] <ericsnow> perrito666: hope it helps
[17:07] <TheMue> 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] <TheMue> dimitern: just thinking  about it
[17:09] <dimitern> TheMue, we'll need to straighten those terms across the code base and make them consistent
[17:09] <TheMue> dimitern: yeah, and here we have multiple possibilities
[17:12] <dimitern> TheMue, as always :)
[17:12] <TheMue> dimitern: renaming MachineNetworkInfo to MachineNetworkConfig (or better: add a second and call it) would make it consistent with the server side
[17:12] <TheMue> dimitern: still it returns InterfaceInfo
[17:12] <TheMue> dimitern: but this could be a third step ;)
[17:13] <dimitern> TheMue, some of those API methods will need to either go away or be refactored anyway
[17:14] <TheMue> dimitern: ok, so I'll start with a simple renaming. server now likes both names.
[18:04] <alexisb> cmars, team meeting??
[18:46] <perrito666> cmars: thank you, I was seconds away of being nominated to lead by alexisb
[18:46] <cmars> perrito666, heh cool. just in time :) distracted by email.. so much of it today
[19:04] <ericsnow> 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] <ericsnow> so the current doc is only 8 pages now
[19:06] <ericsnow> hope that helps, perrito666 :)
[19:09] <perrito666> ericsnow: by the time it gets to 40 again I hope Ill have managed to change computers
[19:09] <perrito666> ericsnow: tx a  lot
[20:39] <natefinch> ericsnow, wwitzel3: where are you guys on responding to the review comments of GCE?
[20:39] <ericsnow> natefinch: yep
[20:42] <natefinch> ericsnow: reread my question :)  Asking how it's going :)
[20:42] <ericsnow> natefinch: ha, missed "where"
[20:43] <ericsnow> natefinch: wwitzel3 has done a lot and I'm planning on tackling some today
[20:43] <perrito666> natefinch: well you did not specify the type of your question, ericsnow just answered got casted to bool
[20:43] <ericsnow> natefinch: none of them look like show stoppers
[20:44] <natefinch> ericsnow: cool
[20:44] <natefinch> perrito666: heh
[20:44] <natefinch> func WhereAreYouOnGCE() string {}
[20:45] <natefinch> I guess "yep" still qualifies ;)
[20:45] <perrito666> troll python programmer is troll
[21:35] <thumper> ericsnow: ping
[21:35] <ericsnow> thumper: hey
[21:36] <thumper> ericsnow: I hear you have some concerns around logging and mongo, wanna chat about it?
[21:36] <thumper> wwitzel3: you around too?
[21:36] <ericsnow> thumper: sure
[21:36] <thumper> menn0: perhaps a logging hangout
[21:36]  * thumper makes
[21:36] <thumper> menn0, ericsnow, wwitzel3: https://plus.google.com/hangouts/_/canonical.com/logging
[21:37] <ericsnow> thumper: wwitzel3 had some specific feedback and more familiarlity with the topic...
[21:38] <thumper> ericsnow: I had a chat with wwitzel3 the other day
[22:12] <menn0> thumper: sorry I missed that hangout - was at swimming
[22:13] <menn0> thumper: what did I miss?
[22:15] <rick_h_> menn0: you've got to fix it all by EOD, that'll teach you to go swimming :)
[22:15] <menn0> rick_h_: ha
[22:47] <wallyworld> thumper: did william look atyour doc? i asked him to and he said he would
[22:48] <thumper> wallyworld: don't know
[22:48] <thumper> didn't see any comments
[22:48] <wallyworld> bet he didn't :-)
[23:46] <wallyworld> 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] <wallyworld> ie 2 individual commands but specifying where the packages are to come from
[23:51] <wallyworld> axw: hey, can you ping me when you're on?