[00:00] <davecheney> unsubtle reminder, https://docs.google.com/a/canonical.com/document/d/1eeHzbtyt_4dlKQMof-vRfplMWMrClBx32k6BFI-77MI/edit#heading=h.reab82nqtett
[00:08] <arosales> bigjools, thanks again for the help on the azure bits
[00:09] <bigjools> arosales: no prob
[00:09] <bigjools> wallyworld gets the baton next week and he told me he's really looking forward to it
[00:10] <wallyworld> no he's not and no he isn't
[00:57] <bigjools> davecheney: I want to move the gwacl code on to the juju landing bot. Where do I start?
[00:57] <davecheney> bigjools: i'm sorry I don't know how to do that
[00:57] <davecheney> john owns the bot
[00:57] <bigjools> ok HAL
[00:58] <bigjools> jam, when you get in.... ta :)
[01:32] <smoser> bigjools, so saucy + azure + juju core "works for me"
[01:32] <bigjools> smoser: yeah I just got it working too
[01:32] <bigjools> NFI why it didn't before
[01:33] <smoser> http://paste.ubuntu.com/6012428/
[01:33] <smoser> bigjools, i think you just were'nt being patient.
[01:34] <bigjools> smoser: 30 minutes ought to be enough patience.
[01:34] <bigjools> and actually I left it several hours
[01:35] <bigjools> although I have a sneaking suspiscion that it was booting an image without the new cloud-init
[01:36] <smoser> not on saucy.
[01:36] <smoser> Cloud-init v. 0.7.3 finished at Wed, 21 Aug 2013 21:33:21 +0000. Datasource DataSourceAzureNet [seed=/dev/sr0].  Up 534.78 seconds
[01:36] <smoser> thats from bootstrap node.
[01:41] <smoser> i certainly dont think you could have been running saucy without cloud-init.  there was a fix in a few days ago
[01:41] <smoser> Cloud-init v. 0.7.3 finished at Wed, 21 Aug 2013 21:48:55 +0000. Datasource DataSourceAzureNet [seed=/dev/sr0].  Up 520.95 seconds
[01:41] <smoser> oops
[01:41] <smoser> https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1214541
[01:41] <_mup_> Bug #1214541: hostname setting is erroring out <amd64> <apport-bug> <cloud-images> <saucy> <cloud-init (Ubuntu):Fix Released> <https://launchpad.net/bugs/1214541>
[01:41] <smoser> but that didn't really stop boot.
[01:43] <smoser> bigjools, one thing to note, it sure appears to me that you're sending in the linuxprovisioningxml

[01:44] <bigjools> smoser: not sure we even set that
[01:44] <smoser> oh. maybe not.
[01:44] <smoser> it probably makes sense to send the hostname as the hostname :)
[02:15] <thumper> axw: I don't suppose you can work your test speed ups on the ec2 tests?
[02:15] <axw> thumper: heh :) I was planning to go across the codebase
[02:15] <thumper> \o/
[02:15] <axw> just responding to fwereade's comments on manual provisioning now
[02:22] <thumper> cool
[02:22]  * thumper is trying to finish off the refactoring branch of doom
[02:23] <axw> thumper: which is that? agent config changes?
[02:23] <thumper> axw: yeah, replacing agent.Conf with an interface
[02:24] <thumper> getting kinda epic
[02:24] <axw> :)
[02:24] <thumper> even for the minimum case
[02:31] <axw> thumper: https://codereview.appspot.com/12831043/patch/8002/9024  -- second last comment. fwereade suggested I ask you about whether the upstart job's name ought to go into agent config
[02:31] <axw> what do you reckon?
[02:32] <thumper> hmm...
[02:32]  * thumper looks and considers
[02:33] <thumper> axw: so my answer is yes, but not now
[02:33] <axw> okey dokey
[02:33] <thumper> axw: I want to add an environment type thing to agent config
[02:33] <thumper> but that is coming after the mega branch
[02:33] <axw> environment type thing?
[02:33] <thumper> so the agent config can have key/value string pairs
[02:33] <axw> ah right
[02:33] <thumper> for arbitrary extra info
[02:34] <axw> *nods*
[02:34] <axw> I will add a TODO here then
[02:34] <thumper> kk
[02:45] <wallyworld> thumper: axw: you guys run the ec2 tests on trunk recently? i have a failure in TestAddresses
[02:45] <thumper> wallyworld: have you updated goamz?
[02:45] <wallyworld> thumper: axw: also, reading back scroll, rodger is working on ec2 test speedups
[02:45] <wallyworld> maybe not
[02:46] <thumper> my trunk from the other day works
[02:46] <wallyworld> ok, i was out of date, thanks. will try again in a bit
[02:47] <axw> wallyworld: I think gz changed something. and yeah I saw the other day he sped them up significantly - not sure where he's at with it now. I'll ping him later
[02:48] <wallyworld> it may have been rodger not martin
[02:48] <axw> sorry, I conflated two comments
[02:48] <axw> yes, rog
[02:53] <thumper> OOPS: 1 passed, 3 FAILED, 1 PANICKED, 4 MISSED
[02:53] <thumper> but at least they now freaking compile
[02:53] <thumper> that is the agent tests
[02:53]  * thumper digs
[02:55] <thumper> 2 passed
[02:57] <thumper> 3 passed
[02:58] <thumper> 4 passed
[02:59] <thumper> kid run
[03:19]  * thumper stabs useless tests  in the face
[03:19] <thumper> testing something that never happens and doesn't make sense
[03:39] <thumper> omg might be there...
[03:39] <thumper> running make check
[03:40] <axw> woo :)
[03:41] <thumper> heh
[03:41] <thumper> I got more strict in what I expect
[03:41] <thumper> now I have a few more failures to fix
[03:41] <thumper> although should be trivial
[04:03] <thumper> not as trivial as I had hoped...
[04:05] <thumper> 22 files changed, 781 insertions(+), 866 deletions(-)
[04:05] <thumper> totalling around 2.5k changes
[04:05] <thumper> at least william will do it :)
[04:17] <thumper> finally, all tests pass
[04:24] <thumper> for the interested: https://codereview.appspot.com/13164043 (and fwereade)
[04:24]  * thumper goes to take kid to sport
[04:25] <thumper> back for the meeting
[04:25] <axw> adios
[05:24] <jam> bigjools: I'm around, where do you need gwacl moved to?
[05:24] <jam> also, wallyworld, dimitern and some other people should know how to do it in case I'm not available
[05:26] <bigjools> jam: I currently have a landing bot on my home server, and I want it moved so the juju bot lands it please
[05:26] <jam> bigjools: ah, just moved to the bot. Sure. Is it just tarmac?
[05:26] <bigjools> the project is part of juju
[05:26] <bigjools> yes, thanks
[05:26] <bigjools> I can give you the tarmac conf later if you need it - my home server decided to crash and burn so I am rebuilding it
[05:28] <jam> bigjools: so the "standard" config I have is this: http://paste.ubuntu.com/6012846/
[05:29] <jam> I think we need a little bit of change for your code, because we need to put it in a different GOPATH so you can land stuff that would otherwise break juju-core until you have the patch that matches juju-core again.
[05:29] <jam> bigjools: but otherwise, whatever verify_command, etc you want , just let me know (make check, etc)
[05:30] <jam> bigjools: maybe it was only with older tools but "-gocheck.v" wasn't compatible with "./..." when I've tested it in the past.
[05:31] <jam> I guess it doesn't matter terribly, but I'm guessing your bot wasn't testing "dedent" and "logging" on each run.
[05:32] <jam> "make check | grep dedent" doesn't show anything for me
[05:32] <bigjools> jam: make check is all you need
[05:32] <jam> bigjools: but it doesn't run the tests in the subdirs
[05:32] <jam> (as I mentioned just now)
[05:32] <jam> it is a bug in "go test" but if you pass special flags like "-gocheck.v" it doesn't notice "./..."
[05:33] <bigjools> make check works fine locally, what's up with the bot?
[05:33] <jam> bigjools: test it yourself "make check | grep dedent"
[05:33] <jam> empty output for me
[05:33] <jam> on my personal machine
[05:33] <jam> go 1.1.1
[05:34] <bigjools> why are you grepping for dedent?
[05:34] <jam> bigjools: because that is part of your test suite "dedent/dedent_test.go"
[05:34] <bigjools> oh////
[05:34] <bigjools> meh
[05:34] <bigjools> sorry I am slow todya
[05:34] <jam> bigjools: so your "make check" doesn't run tests in subdirs
[05:36] <bigjools> jam: ok so the regular go test ./...
[05:36] <bigjools> and
[05:36] <bigjools> go build example/*/run.go
[05:36] <bigjools> we can add something for formatting later
[05:36] <bigjools> alternatively we can add a new make target for the bot
[05:57] <davecheney> afternoon all, see in yo in a few hours for the meeting
[08:03] <natefinch> jam: is the hangout link different from the morning standup link?
[08:04] <axw> natefinch: https://plus.google.com/hangouts/_/bf3f4cfe715017bf60521d59b0628e5873f2a1d3?authuser=1
[08:04] <natefinch> axw: thanks
[08:08] <jam> natefinch: you should be on the calendar entry, which is the g+ hangout we use. Just checking that it is working for you.
[08:16] <mramm> hey, for some reason I can't get back in the hangout
[08:19] <nate-finch> jam: Yep, I have the calendar entry - I just missed the link in the event... I'm too used to seeing a long ugly URL, not a small "Join Video Call" link :)
[09:11] <wallyworld> fwereade: if you want a (slightly) smaller branch ( 2392 lines (+425/-580) 36 files modified) as an entree to thumper's: https://codereview.appspot.com/13081044/   plus I updated https://codereview.appspot.com/13047043/
[09:11] <fwereade> wallyworld, aww, thanks ;p
[09:11] <wallyworld> i'm here to please :-P
[09:12] <wallyworld> it's a net deletion of code which i a good thing, a lot of duplicated stuff gone :-)
[09:15] <fwereade> wallyworld, cool, thanks
[09:19] <axw> jam: just looking at the upgrade bug again...
[09:19] <axw> what happened was, I did an upgrade-juju --upload-tools in local
[09:19] <axw> the bootstrap machine agent got the tools it needed to upgrade, and restarted
[09:20] <axw> then upgrade-juju proceeded to attempt to upload additional tools, and failed
[09:20] <axw> *additionally* the machine agent just restarts in a loop
[09:28] <fwereade> axw, huh, don't we upload all the tools before we set the agent version?
[09:28]  * axw has a look
[09:28] <axw> I have no idea :)
[09:28] <fwereade> axw, (and, sorry, which machine agent? 0?)
[09:28] <axw> yes, 0
[09:29] <fwereade> axw, don't suppose the log said anything useful about why?
[09:29] <axw> there are some errors about connecting to a websocket? but I haven't had time to dig
[09:30]  * fwereade sighs
[09:30] <fwereade> thanks axw
[09:30] <fwereade> I think it's probably clear how to fix it
[09:31] <fwereade> we just need to wait to make connections rather than bouncing every time things go wrong
[09:36] <axw> fwereade: yes it does appear that the version is set last. Perhaps I already had machine-0 in a bad state when I attempted to upgrade again
[09:37] <axw> but the simple upgrade-juju is still a problem
[09:37] <axw> i.e. the steps in #1214676 are repeatable
[09:37] <_mup_> Bug #1214676: upgrade-juju in local environment causes bootstrap machine agent to restart continuously <juju-core:Triaged> <https://launchpad.net/bugs/1214676>
[09:39] <fwereade> axw, sure, I'm not trying to claim otherwise -- thanks :)
[09:39]  * fwereade breakfast
[09:40] <jam>  axw: it sounds like we should be uploading all the tools before we ask things to upgrade themselves.
[09:41] <axw> jam: possibly we are. I'm no longer sure about the interaction of this bug and the one I link to the description
[09:41] <axw> I'll have to try and reproduce the original one again
[09:41] <axw> anywho, gotta get dinner on - I'll be back for a bit later
[09:42] <jam> np
[09:42] <jam> have a good evening
[10:23] <fwereade> wallyworld, remind me: are we now requiring that we bootstrap with matching version rather than picking latest? or is that really really imminent?
[10:24] <wallyworld> fwereade: soon. i justed wanted to get the core refactoring done first. there will be a lot of tests etc to fix when we change the boot strap tools search
[10:25] <wallyworld> and the branch was already huge
[10:36] <fwereade> wallyworld, sure, understood :)
[10:40] <fwereade> wallyworld, btw, why the change from tools-metadata-url to tools-url? the first feels more correct to me
[10:41] <fwereade> mgz, you have quite a lot of branches up that I think are already LGTMed, are there any I should be looking at?
[10:43] <mgz> fwereade: nope, though last check I think a couple of the trivial ones weren't lgmted, I'll look again
[10:43] <yolanda> hi, i'm using juju-core with canonistack. I destroyed a service but now it keeps on status "dying" for all the time. Tried to terminate the machine, removing the unit, without success, and now i cannot redeploy that again although i destroy all the environment. Is there some way where i can manually destroy that buggy service?
[10:43] <mgz> nope, all ready to land, I'll queue 'em up
[10:45] <mgz> yolanda: you may be able to resolve the unit, then destroy it, depending on exactly what state things got confused in. otherwise, it's destroy-environment to wipe everything
[10:46] <yolanda> mgz, machine was stuck with out of memory errors, but charm state looked as started
[10:46] <yolanda> i tried everything without success, now i manually removed the machine with nova delete, but no progress
[10:46] <mgz> yolanda: what's the current state of the unit? can you pastebin status?
[10:46] <mgz> ah, probably not easily cleanupable any more then
[10:47] <mgz> destroy-environment for the wipe :)
[10:47] <yolanda> http://paste.ubuntu.com/6013589/
[10:47] <yolanda> but that's after all the things i've done
[10:47] <yolanda> i was trying to setup a jenkins unit, but complained about memory
[10:47] <yolanda> ok, i'll destroy everything and try again
[10:48] <mgz> you probably need a constraint on mem=somethingbig for the jenkins service
[10:50]  * TheMue => lunchtime
[10:52] <yolanda> mgz, will try with 2G now
[11:05] <jam> fwereade: https://plus.google.com/hangouts/_/6c44984654c782bf948ffabe55b69414a3a38aea ?
[11:15] <arosales> jam, thanks for the ideas on azure
[11:32] <nate-finch> I was up at 4am, and I'm in the standup....
[11:34] <jam> mgz: wallyworld: https://plus.google.com/hangouts/_/f497381ca4d154890227b3b35a85a985b894b471 standup ?
[11:34] <nate-finch> mgz: standup
[11:34] <mgz> ta
[12:00] <jam> mgz: poke if you could ask jamespage whether they will be getting go-1.1.x into precise's backports
[12:07] <yolanda> mgz, problems with jenkins again, now nova show machine is on error state, and juju shows it as pending, is there any way to solve it without destroying?
[12:07] <yolanda> i got a nasty error:
[12:08] <yolanda> http://paste.ubuntu.com/6013816/
[12:11] <jamespage> jam: you could ask me yourself :-)
[12:11] <jam> jamespage: I thought given it was Thurs he might be sitting right next to you, and could have the high-bandwidth conversation
[12:12] <jam> the question also originated on our phone call, but he lagged out for a bit.
[12:12] <jam> but yes, jamespage, what is the current plan for getting juju into precise-backports and its associated build dependencies
[12:12] <jam> ?
[12:30] <fwereade> TheMue, ping
[12:32] <fwereade> TheMue, I'm in the standup hangout when you're ready
[12:41] <TheMue> fwereade: I wanted to to it here, but hangout is fine too.
[12:41] <TheMue> fwereade: still there?
[13:15] <jam> jamespage: that's why I don't ask you, you don't answer :)
[13:15] <jamespage> jam: urgh - sorry
[13:15] <jamespage> I have my head in a nasty openvswitch datapath compatibility issue
[13:15] <jamespage> and was mid cherry pick
[13:16] <jam> np
[13:16] <jam> it isn't urgent
[13:16] <jamespage> jam: right now backporting is on hold
[13:16] <jamespage> jam: two reasons - 1) we now have a stable PPA and 2) 12.04 cloud archive is going to get a cloud-tools pocket which would have golang + other stuff in
[16:43]  * fwereade needs to be off a bit early today, see you all soon
[16:44] <mgz_> later fwereade!
[16:54] <TheRealMue> cu
[21:07] <thumper> morning
[21:10]  * thumper stretches
[21:15] <weblife> morning thumper
[21:17] <thumper> hi weblife
[21:32] <thumper> fwereade: hey
[21:32] <thumper> fwereade: you really around?
[21:44]  * thumper sighs
[21:44] <thumper> lots of test failures after merging trunk
[22:05]  * thumper does some manual testing
[22:21] <thumper> bah humbug
[22:21]  * thumper has broken the local provider... locally at least
[22:21]  * thumper enfixorates
[22:23] <fwereade> thumper, heyhey
[22:23] <thumper> fwereade: hey
[22:23] <thumper> fwereade: I was going to ask about the breaking bootstrap change
[22:24] <thumper> and now my local provider is unauthorized in bootstrap
[22:24]  * thumper needs to figure out how...
[22:25] <fwereade> thumper, it's just that juju currently bootstraps with the latest available tools, regardless of client version -- but is it possible it's finding *older* installed tools and trying to bootstrap with those?
[22:25] <fwereade> thumper, wallyworld is going to be changing it to demand matching tools on bootstrap, which I think will help
[22:25] <thumper> I remember change some behaviour around the initial password
[22:26] <thumper> fwereade: but I didn't change that, right?
[22:26] <fwereade> thumper, ehhh, I felt a tiny twinge around that but read it quite carefully and *thought* it was solid
[22:26] <thumper> yeah, I thought it was solid too
[22:26] <thumper> but not enough to commit it to trunk without trying it out :)
[22:27] <thumper> ec2 is working
[22:27] <thumper> hmm... "bzr ssh 0 " doesn't do what I mean
[22:27] <thumper> I mean "juju ssh 0"
[22:27] <thumper> my computer needs more mind reading
[22:28] <fwereade> thumper, well, I am inclined to prejudge it as all being about the upload/sync confusion in the local provider, but that says more about me than about juju I think
[22:28] <fwereade> thumper, ha, yeah, I confuse the two quite a lot
[22:28] <thumper> can't wait until we can change the certs to be stored in base64
[22:28] <thumper> kinda crazy looking at the config files now
[22:29] <thumper> fwereade: no, I don't think it is that...
[22:29] <thumper> fwereade: more likely to be assumptions made during the initial config writing and bootstrapping
[22:30] <fwereade> thumper, ha, yes, tis true those bits don't quite match the non-local case either, right?
[22:30] <thumper> no, it is a bit hand wavey
[22:30] <thumper> and "this is not the config you are looking for"
[22:31] <fwereade> thumper, haha
[22:31] <thumper> there is a very slight change in behaviour
[22:31] <thumper> prior, when writing out the new password
[22:31] <thumper> it would not keep the old one
[22:31] <thumper> but replace it with ""
[22:31] <thumper> now I keep the old one around
[22:32] <thumper> however I don't think that is the current problem
[22:32] <thumper> there is an assumed two-phase commit with the passwords
[22:32] <thumper> which isn't quite there
[22:32] <thumper> save the password, then change it
[22:32] <thumper> and hope all is god
[22:32] <thumper> good
[22:33] <thumper> however since it is possible for the rename of the file to fail
[22:33] <thumper> there is a possibility, however small, that we get stuffed up
[22:34] <fwereade> heh, damn, I missed that; I'd prefer not to lose that just because it's a possible screwup
[22:34] <fwereade> I doubt it's what you're seeing though
[22:34] <thumper> it is no different to before
[22:34] <thumper> just I realised it is there
[22:34] <thumper> the behaviour is the same
[22:35] <thumper> no, this isn't what I'm seeing
[22:35] <thumper> it is just an unauth on the initial create log db part in mongo
[22:35] <fwereade> ah, that's good then, I *thought* I had verified it still was, but was feeling ready to assume hallucinations on my part
[22:44] <thumper> ah fuck
[22:44] <thumper> I think I know what it is
[22:44] <thumper> fuckity fuck fuck
[22:44] <thumper> it is the magic "localhost"
[22:44] <thumper> which I noticed while doing the local provier
[22:44] <thumper> provider
[22:45]  * thumper double checks
[22:48] <thumper> yep...
[22:58] <thumper> at least that fixed
[22:58] <thumper> it
[23:05]  * thumper wonders if he'll conflict with wallyworld
[23:06] <wallyworld> hope not
[23:06]  * thumper just checks
[23:06] <thumper> wallyworld: how are you doing?
[23:08] <wallyworld> ok, landing a bunch of stuff
[23:11] <wallyworld> thumper: i was hoping to get in first with my stuff. now i will have lots of conflicts i'm sure :-(
[23:11] <thumper> wallyworld: well, mine is in the queue too :)
[23:11] <bigjools> good day
[23:12] <thumper> the freaking epic add an interface branch
[23:12] <thumper> hi bigjools
[23:12] <wallyworld> thumper: yours in landing now
[23:12] <thumper> \o/
[23:12] <bigjools> wallyworld: where did you buy your microserver?
[23:13] <wallyworld> bigjools: some online place, i searched on staticice.com.au
[23:13] <bigjools> ok ta
[23:13] <bigjools> hp's site is useless
[23:13] <wallyworld> yep
[23:24] <wallyworld> thumper: only one conflict :-)
[23:26]  * bigjools hugs hot coffee
[23:26]  * wallyworld still has no coffee machine :-(
[23:27] <thumper> wallyworld: still?
[23:27] <thumper> geez
[23:27] <thumper> go get a rental
[23:27]  * thumper needs another coffee
[23:32] <thumper> wallyworld: I have some errands in town
[23:32] <thumper> so will be back later
[23:32] <bigjools> wallyworld: you can always work here
[23:32] <thumper> happy to have my epic branch landed though
[23:32] <wallyworld> thumper: i'm about to go to the police station myself
[23:32] <thumper> wallyworld: is you tools branch the one that fixes bootstrap?
[23:32] <thumper> so don't try to bootstrap with old tools?
[23:33] <thumper> wallyworld: ack
[23:33] <wallyworld> thumper: not quite. next branch
[23:33] <thumper> cool
[23:33] <thumper> I'll be doing more reviews this afternoon
[23:33] <wallyworld> mine does a bunch of other pre -req stuff
[23:33] <thumper> around axw's work on manual provisioning
[23:33] <wallyworld> yay
[23:33]  * thumper nods
[23:34] <thumper> I want to add a new branch for adding string key/value pairs into agent config
[23:34] <thumper> which would lead to the logging branch working
[23:34] <thumper> and tweaking the maas stuff for containers
[23:34] <thumper> bigjools: I have a fix for the maas provider which is less smash of the network conf
[23:34] <thumper> bigjools: using "source" as an include mechanism
[23:35] <thumper> bigjools: so when maas gets better at network handling
[23:35] <bigjools> thumper: splendid.
[23:35] <thumper> it won't kill it
[23:35] <bigjools> when you say better ...
[23:35] <thumper> :)
[23:35] <bigjools> we're adding more constraint types next week
[23:35] <thumper> what does that mean for me?
[23:35] <bigjools> so the core had better hurry up and support it :)
[23:36] <bigjools> custom tags as per the pyjuju
[23:36] <bigjools> --to in the new world IIRC