/srv/irclogs.ubuntu.com/2013/09/17/#juju-dev.txt

thumperaxw or wallyworld: Rietveld: https://codereview.appspot.com/1371704402:06
thumperwallyworld: how's baldrick?02:06
axwthumper: otp02:06
wallyworldok. stupid tail02:06
thumperaxw: ack02:06
thumperstupid tail or stupid dog?02:07
wallyworldboth02:07
wallyworldthumper: did you talk to william?02:07
thumperwallyworld: yeah, but he was packing and moving yesterday02:08
thumperwallyworld: landed the first part where it doesn't write to the agent conf02:08
thumperand I don't need to any more02:08
wallyworldok02:08
thumperso now we have just one place where the logging conf is saved02:08
thumperand that is in state02:08
wallyworldgreat02:08
thumperso we start the machine and unit agents with --debug02:09
thumperalways02:09
thumperand the logger worker updates as necessary02:09
thumperas soon as it starts02:09
wallyworldsounds good02:09
wallyworldthumper: i'm not 100% across it - will unilaterally removing the file writer stuff up new environments? don't we want to only remove it for old envs?02:11
thumperwallyworld: the new environments won't ever set it02:12
wallyworldok02:13
thumperwallyworld: and unfortunately we have no way to know which version it is from02:13
thumperno point asking if it is there02:13
wallyworldok02:13
thumperthe method returns an error if it isn't there02:13
thumperbut we just ignore it02:13
axwsorry thumper was having my one-on-one with robbie ... reading back now02:45
thumpernp, wallyworld handled it02:45
thumperwas just a review02:45
axwah cool02:45
thumperI have another coming02:45
thumperwallyworld: re: an integration style test, no we don't have one, and I think the effort in all the wiring up is out of proportion to result03:10
thumpergiven that all the parts are tested03:10
wallyworldfamous last words :-P03:10
wallyworldok though03:10
thumperperhaps it is something that we want to add to the more "live tests" that we do daily with jenkins03:10
wallyworldyeah03:10
thumperwallyworld: well, we have tests for all the parts03:11
thumperso I'm pretty confident there03:11
wallyworldok03:11
thumper24 files changed, 31 insertions(+), 158 deletions(-)03:20
thumperthat is a good metric I reckon03:20
* thumper waits for lbox to calculate the diff that LP has already done03:21
thumperwallyworld or axw: https://code.launchpad.net/~thumper/juju-core/add-cleanup/+merge/18596403:22
thumperlbox finally caught up03:22
thumperthe description has the link now03:22
wallyworldjust fixing some stuff, will look in a sec03:23
thumperkk03:24
axwthumper: just one question on rietveld03:31
thumpershoot03:31
axwno I mean, there's a question waiting for you on your MP03:32
thumperoh03:32
thumperok03:32
thumperreplied03:34
axwthumper: thanks, LGTM03:38
thumperta03:38
wallyworldaxw: whenever you have a moment, i've updated https://codereview.appspot.com/13725043/ to move the httpstorage as requested03:58
axwthanks wallyworld, I'll take a look03:59
wallyworldta, no real urgency03:59
axwwallyworld: I thought it was ok being in environs, since it's used by things other than the provider. doesn't really matter I suppose.04:00
wallyworldaxw: in environs, i'd prefer to keep stuff there generic. if it's ec2 specific, it belongs under the ec2 package imo04:00
wallyworldi'd also prefer that stuff not use it outside the provider i guess04:01
wallyworldsince it is ec2 specific04:01
wallyworldand general code should not depend on ec2 isms04:01
wallyworldthere's been way too much of that which has caused grief dealing with other providers04:02
axwdoesn't tools lookup still use this to fall back on?04:02
wallyworldtools uses a http data source04:02
wallyworldwhich is not ec2 specific04:02
wallyworldi really wish the ec2 specific one would go away04:03
axwok. for some reason I thought FindTools still depended on it04:04
axwwallyworld: ah, right. it's the sync code that I'm thinking of.04:05
wallyworldyeah, that will be migrated to use http://juju.canonical.com as soon as that is ready04:06
wallyworldso it's short term04:06
=== thumper is now known as thumper-afk
wallyworldaxw: thanks for the review, i'll address the issues04:42
wallyworldi really wish Go had better debugging facilities04:43
wallyworldfeels like a bad 1970's timewarp sometimes. everything is sooooo primitive04:43
axwwallyworld: heh :)   there is gdb support...04:48
wallyworldbut not good IDe support04:48
axwI believe there's even some IDE integration with gdb/go04:48
axwliteide?04:48
wallyworldi use intellij04:48
wallyworldliteide may work, i will need to take another look i guess04:48
wallyworldwasn't much last time i looked from memory04:49
axwwallyworld: it certainly isn't up to par with Java, but I'll take it over C++ any day for debugging04:49
wallyworldreally?04:49
axwthen again, I'm not much of an IDE person :)04:50
wallyworldapart from java, which is first class, python is also great04:50
axwyeah04:50
wallyworldso how to you refactor etc with good ide support?04:50
axwto  be fair, they're much older04:50
wallyworldor navigate code, or find semantic usages etc04:50
wallyworldwell go is 4 or 5 years old now?04:50
axwyeah, 404:51
axwerm, the hard way :)04:51
wallyworld4 years is plenty long enough for good tools to have emerged04:51
axwnot sure if you follow the mailing lists, but there was an announcement last week of a new tool called "The Go Oracle"04:52
axwthis will drive IDE developments04:52
axwfor doing callgraph analyses and whatnot04:52
wallyworldyay, about time :-P05:01
axwwallyworld: also, there's basic renaming/refactoring capabilities in gofmt05:05
axwgodoc gofmt05:05
axwif you're not aware of it..05:05
wallyworldi was not :-)05:05
wallyworldalthough in 2013 "basic" isn't enough anymore :-)05:06
axwyeah, it's certainly not all there05:06
davecheneywhy the fuck is the juju-core repo 22mb ?!?!05:46
davecheneywho has been storing guttenberg in there05:46
davecheneyhelp05:55
davecheney% bzr push  bzr+ssh://bazaar.launchpad.net/~go-bot/juju-core/1.1405:55
davecheneybzr: ERROR: Cannot lock LockDir(chroot-80212880:///~go-bot/juju-core/1.14/.bzr/branch/lock): Transport operation not possible: readonly transport05:55
davecheneycannot tag 1.1405:55
davecheneycannot tag 1.14.005:55
=== tasdomas_afk is now known as tasdomas
davechen1yaxw_: is there an issue for juju debug-log screwing up ?06:51
axw_davechen1y: not that I'm aware of?06:52
davechen1yok06:52
davechen1yi guess that one went through to th keeper06:52
davechen1ybut it's fixed ? right06:52
davechen1yon 1.14.0 ?06:52
axw_oh sorry06:52
axw_yes there was one06:52
axw_and yes it was fixed a while ago06:53
axw_I thought you meant one outstanding06:53
axw_I'll have a look for it06:53
axw_davechen1y:  here's one https://bugs.launchpad.net/juju-core/+bug/121114706:54
_mup_Bug #1211147: Deploying service to bootstrap node causes debug-log to spew messages <juju-core:Fix Released by axwalk> <https://launchpad.net/bugs/1211147>06:54
axw_I can't remember what the other issue was...06:55
axw_davechen1y: https://bugs.launchpad.net/juju-core/+bug/121214806:59
_mup_Bug #1212148: rsyslog accumulator strips newlines <juju-core:Fix Released by axwalk> <https://launchpad.net/bugs/1212148>06:59
axw_both merged in 1.13.206:59
rogpeppemornin' all07:01
rogpeppei'll be out this morning for a doctor's appointment for a couple of hours (hopefully less), leaving in an hour.07:02
axw_hey rogpeppe. okey dokey.07:03
rogpeppeaxw_: hiya07:03
=== axw_ is now known as axw
rogpeppedimitern, jam: i've got a doctor's appointment now. back before the standup i hope.08:02
wallyworld___jam: if you are interested - https://codereview.appspot.com/13632056 is part 1, part 2 to follow. part 2 will adjust tools fetching to use retry logic when necessary. this current work always does not use retry logic for tools fetching. bootstrap is fast again :-)09:03
wallyworld___well, upload tools is still slow09:04
wallyworld___but tools seeking is fast09:04
=== tasdomas is now known as tasdomas_afk
=== tasdomas_afk is now known as tasdomas
rogpeppeback09:42
mgzjam: mumble?09:59
arosalesjam, ping10:58
davecheneyjam: help11:12
davecheneyi can't tag the 1.14 branch11:12
mgzdavecheney: what's up sepcifically?11:13
mgzyou should just be able to set your user to the bot and run tag against the remote branch as usual11:14
davecheneymgz: hmm, maybe that was it11:14
davecheneymy history from the last tag is missing11:14
jamdavecheney, arosales: ?11:15
davecheneymgz: bzr push  bzr+ssh://bazaar.launchpad.net/~go-bot/juju-core/1.1411:15
davecheneywhat am I missing ?11:15
arosalesjam, davecheney needs some assistance with the tagging of 1.411:15
mgzah, that's not creating the tag, you want to make the branch?11:15
arosales1.14, blocking the release needed today11:15
jamdavecheney: "bzr tag -d bzr+ssh://go-bot@bazaar.launchpad.net/~go-bot/juju-core/1.14"11:15
mgzyou need ://go-bot@11:15
jamwell, you need to specify the tag as well :011:15
mgzotherwise you're probably running it as dave11:15
jambzr tag -d bzr+ssh://go-bot@bazaar.launchpad.net/~go-bot/juju-core/1.14 -r -1 juju-core-1.1411:16
jamnatefinch: https://wiki.canonical.com/CDO/UbuntuServer/IOM-Lab is the "garage maas" that we have set up (I believe)11:16
* TheMue => lunch11:17
davecheneyjam: mgz thank you11:17
natefinchjam: thanks11:18
davecheneyjam: mgz https://code.launchpad.net/~go-bot/gwacl/test11:21
davecheney^ is this lp:gwacl ?11:21
mgzdavecheney: nope.though it's probably a branch of it11:22
mgzlp:gwacl is ~gwacl-hackers/gwacl/trunk11:23
davecheneymgz: i'm confused the bot doesn't own the branch11:26
davecheneythe bot owns the test branch11:26
mgzdavecheney: the bot only owns branches that it manages11:28
davecheneymeh11:28
davecheneyno time for scenary today11:28
davecheneyneed to get mr page a release11:29
arosalesmgz, jam, davecheney, once we have the source tar ball any way the ubuntu package can be built without directly (without going through saucy first)?11:31
arosalessorry, let me restate11:32
arosalesmgz, jam, davecheney, once we have the source tar ball any way the ubuntu package can be built  directly (without going through saucy first)?11:32
davecheneyarosales: no, but I can build from the source of the tarball to test11:32
mgz...I'm still not sure I understand11:32
davecheneymight need some jiggery pokery to get the tools to work11:32
mgzyou can pull the tarball into the packaging branch and build that with the normal debian tools11:32
davecheneymgz: good idea11:33
davecheneythat will work11:33
davecheneybut probably not necessary11:33
davecheneyi think I can fake the tools11:33
arosalesmgz, I think davecheney dputs the built packages once they are available in saucy11:33
davecheneyarosales: the build-release-tarball also does a smoke test compile of the source after building it anyway11:33
arosalesI was asking if we could just build directly, and avoid the dput step11:34
davecheneyarosales: no, i _want_ to do that, but we don't currently11:34
arosalesdavecheney, ah so you currently don't wait for it to be available in saucy.11:35
davecheneyarosales: we need to wait for saucy _AND_ the ppa backports before we can announce the release11:35
davecheneybut we do not need to wait for either of those to test it11:35
davecheneythere will be ways of working around that11:35
arosalestechnically I don't see why we need to wait for saucy. That was my questions about building directly11:36
davecheneyarosales: my mistake11:37
davecheneyi was not clear in understanding your goal11:37
* arosales not wording well either mgz didn't understand either.11:37
davecheneyarosales: what do you want, not what do you want us to do :)11:38
arosalesonce you have the source tar ball building the packages should be identical to what gets built in saucy.11:39
davecheneyarosales: correct11:39
davecheneynot should11:39
davecheney_is_11:39
davecheneythe tarball contains all the source code11:39
davecheneythere are no external build depdencies11:39
arosalesThus to help get the release in the ppa today would it be possible to build juju 1.14 outside of the saucy archive so it is available in juju/stable sooner?11:40
davecheneyarosales: no, that is not possible11:40
davecheneywe do not have a build recipe for that11:41
davecheneyi would *like* the juju source to contain the debian/ build recipe11:41
davecheneybut at the moment that is not done11:41
davecheneyok 1/2 branches waiting on the bot to merge11:41
davecheneythe other can be submitte after the release11:42
arosalesdavecheney, ok . . .11:42
davecheneyarosales: i have not been clear11:42
davecheneythe build release tarball contains the upstream source11:42
davecheneythe magical ubuntu debian parts are missing11:43
davecheneyso while you can build juju from the srouce11:43
davecheneyyou cannot replicate the packaging11:43
davecheneythat magic is not something i have access too11:43
davecheneyhowever, I do not think this is a major hurdle for smoke testing11:43
arosalessmoke no, maybe for getting something out the door today.11:44
arosalesafik anyone can build a ppa if they have the upstream source and the debian source package11:44
davecheneyarosales: yes, it is possible11:44
davecheneyno, we do not have the magic to do so11:44
davecheneyarosales: i am working as fast as possible11:45
arosalesdavecheney, I know and its appreciated. I know your up late too. I was just inquiring about the getting the release into juju/stable step.11:45
davecheneyarosales: in theory it is possible to skip that step11:45
davecheneyat the 11th hour, without ever having tried it11:46
davecheneyi don't know how to do it11:46
davecheneynor recommend it11:46
mgzarosales: so, I've not found the ppa useful or a good recommendation11:46
davecheneyarosales: what do you need, and what time do you need it by ?11:46
davecheneywhen is the announcement ?11:46
arosalesmgz, juju/stable?11:46
davecheneywill a binary .zip be sufficient ?11:47
mgzbut, it would be pretty trivial to change it to do basically what the release into saucy does, by just making it use a packaging branch straight up and merging the tarball into that11:47
davecheneyjamespage: hello11:47
arosalesdavecheney, we'll need a ubuntu package.11:47
arosalesdavecheney, time wise it was never set to an actual hour. If it is not available in the next 4 hours then we'll probably miss today as the UK folks go offline and they are the web team that will do the announce.11:48
davecheneytarball is ~30 mins away11:48
davecheneyless11:48
dimiternrogpeppe, ping11:51
rogpeppedimitern: pong11:51
dimiternrogpeppe, I have a weird panic in a test when I run the full suite, but it's ok if I run each test on its own11:52
rogpeppedimitern: which suite?11:52
hazmatso.. right now the most stable version of juju till the next tarball is ppa/devel11:52
natefinchjam: FYI logging in to garage maas is not working.  Seems likely I don't have permission.11:52
rogpeppedimitern: and what's the panic?11:52
davecheneyarg, fucking build falied11:52
dimiternrogpeppe, http://paste.ubuntu.com/6119111/11:52
davecheneytrying again11:52
dimiternrogpeppe, provisioner - this is the code http://paste.ubuntu.com/6119112/11:53
hazmatarosales, davecheney re new stable version.. afaics we should have 1.13.3 in stable ppa11:53
davecheneyhazmat: NO11:53
dimiternrogpeppe, it doesn't happen with the deployer, which also uses PasswordChanger the same way11:53
davecheneyno, no no, a thousand nos11:53
hazmatdavecheney,  why not.. forget the  undocumented even/odd stuff..11:53
davecheneyhazmat: even if I could11:54
davecheneythe tools owuldn't work11:54
davecheneyreally11:54
davecheneyno11:54
hazmathmm11:54
davecheneythis is not a good idea to be trying11:54
hazmattrunk has a bunch of tools issues11:54
davecheneyhazmat: sure, we're not releasing trunk11:54
hazmatdavecheney, didn't you tell me to use 1.13.3 earlier today for a customer setup?11:54
davecheneywe are relasing 1.14.0 which is 1.13.3 + 4 small patches11:54
hazmatah.. ic11:54
rogpeppedimitern: does it happen consistently?11:54
davecheneyso, the best version of juju we have11:54
dimiternrogpeppe, so far on each run11:54
davecheneyplus some azure fixes from brisbane11:54
davecheneyso it's even betterer11:55
dimiternrogpeppe, tried updating mgo to r240, as the dependencies.tsv says - still the same error11:55
hazmatdavecheney, so what's the transition process from dev to stable?  last dev gets incremental fixes.. till its marked stable?11:55
dimiternrogpeppe, would've tried with the latest mgo tip, but that just fails on its own tests11:55
davecheneyhazmat: as it stands, we develop on trunk under an unstable dev version11:56
davecheneythen a decision is made that a particular unstable tag looks good11:56
davecheneyso we branch from there11:56
davecheneythen start a new unstable series11:56
davecheneyso11:56
davecheney1.13.3 -> 1.14.011:56
rogpeppedimitern: could you put a log print just before line 114?11:56
davecheney       -> 1.15.0 -> 1.15.111:56
rogpeppedimitern: the weird thing is line 3511:58
davecheneyarosales: 15 minute delay, the bot failed to run the tests correctly11:58
davecheneytrynig again11:58
hazmatdavecheney, so basically we tag a version of trunk or dev tag as release series, and create a release series branch against that and then do bug fixes against till its stable?11:58
davecheneyif it fails, we'll go around th bot11:58
dimiternrogpeppe, the log doesn't show at all11:58
dimiternrogpeppe, what's weird about line 35?11:58
davecheneyhazmat: no11:58
davecheneyhazmat: docs/juju-release-process.txt11:59
rogpeppedimitern: provisioner.SetPasswords should make an API call, right?11:59
davecheneyhazmat: also https://docs.google.com/a/canonical.com/document/d/1bxekJclEzXT3b8fEmP2wHfZ2hiiYI-ojzBnr_2mVfpo/edit11:59
dimiternrogpeppe, no11:59
davecheneyand about a million other google docs11:59
dimiternrogpeppe, that's the server-side test11:59
hazmatdavecheney, if only they could be searched ;-) thanks11:59
davecheneyhazmat: i believe you can ask your govt. for assistance there12:00
rogpeppedimitern: oh, of course, sorry.12:00
hazmatdavecheney, nice. citizens only get guns.. info requires using it12:00
dimiternrogpeppe, why is the session getting closed anyway? and why only on the last test12:00
rogpeppedimitern: but you're not seeing a log message that's printed just before line 114?12:00
arosalesdavecheney, thanks for the continued work on it.12:01
dimiternrogpeppe, ah, sorry I see it yes12:01
dimiternrogpeppe, just after that the log continues with reset dummy environment12:01
rogpeppedimitern: so you see the reset *after* the log message?12:02
dimiternrogpeppe, yes12:02
davecheneyarosales: no problem, it's what i;m here for12:02
davecheneyarosales: we're really close12:02
davecheneyi'd like to not cowboy the packaging12:03
davecheneyit is one of the few things that works well12:03
rogpeppedimitern: could you print out the callers of dummy.Reset?12:03
davecheneyand we'll only cock it up if we rush12:03
rogpeppedimitern: (you can use "code.google.com/p/rog-go/exp/runtime/debug".Callers(0, 20))12:03
rogpeppedimitern: e.g. log.Infof("dummy resetting; callers: %s", debug.Callers(0, 20))12:04
arosalesdavecheney, ack we should follow the process12:04
dimiternrogpeppe, just a sec12:04
davecheneyarosales: merged, tag updated, building tarball12:05
arosalesgetting closer :-)12:05
hazmatdavecheney, that doc seem quite right.. there is only one dev branch and tags.. so my previous description seems accurate. but the doc states.. "For stable releases they are branched from a known working devel branch"12:06
hazmater.. doesn't seem quite right12:06
davecheneyhazmat: for the 2 stable releases ive done12:08
davecheneyone of which I am doing right now12:08
davecheneyI branched from a devel tag12:08
davecheneythat is all I can tell you12:08
hazmatdavecheney, k12:09
davecheneyhazmat: the pirate code is more, um, a guideline12:10
natefinchdavecheney: nice12:10
dimiternrogpeppe, http://paste.ubuntu.com/6119176/12:10
davecheneyarrr12:11
natefincharosales, davecheney:  I'm building the 1.14 juju client windows installer.  I have a windows build of the juju client that I made off of the 1.14 branch.   I believe that's all that is required.  is there anything I'm missing?   The windows installer code didn't actually make it into 1.14, but it's completely separate from the client code, so it shouldn't matter.12:11
davecheneynatefinch: just make sure you get the right revisions of GWACL et al12:12
dimiternrogpeppe, it seems somehow TearDownTest gets called12:12
davecheneythe revisions are in the build-release-tools script12:12
davecheneydependencies.txt in the root of the 1.14 branch is incorrect12:12
davecheneyin fact12:12
davecheneyi'm going to delet eit12:12
davecheneyarosales: release tarball: /home/dfc/devel/juju-core/1.14/scripts/build-release-tarball/juju-core_1.14.0.tar.gz12:12
davecheneyDONE!12:12
rogpeppedimitern: could you paste the log from running with -gocheck.vv12:12
arosalesnatefinch, I defer to davecheney12:12
davecheneyjamespage: relase incoming in ~ 5 mins12:13
dimiternrogpeppe, http://paste.ubuntu.com/6119185/12:14
arosalesjamespage, do you have a rough estimate on when saucy could have 1.14 available ?12:14
jamespagearosales, I'll pick it up tomorrow AM12:14
jamespageneed to checkin with the release team as well12:14
rogpeppedimitern: that is weird12:15
jamespagebut as its 'stable 1.13' that should not be to much of a problem12:15
dimiternrogpeppe, it seems it calls both SetUpTest and TearDownTest before trying the actual test12:15
rogpeppedimitern: could you push the branch - there are a couple of things i want to check12:16
jamespagedavecheney, arosales, mramm: speaking of which I really need to get what we want to ship in Saucy nailed down here - https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/121987912:16
_mup_Bug #1219879: [FFe] juju-core to 1.14.0 stable release for Ubuntu 13.10 <juju-core (Ubuntu):New> <https://launchpad.net/bugs/1219879>12:16
davecheneyjamespage: arosales i would like to assign that bug to mark ramm12:17
davecheneydoes he have the bandwidth to deal with it ATM ?12:17
dimiternrogpeppe, https://codereview.appspot.com/1372004512:19
arosalesjamespage, ack.  I will follow up on that bug. I think thumper-afk and jam had some ideas on bits needed for Saucy.12:19
davecheneyarosales: will you please hold the bug for the moment12:20
davecheneyjamespage: arosales https://launchpad.net/juju-core/1.14/1.14.012:20
davecheneysinzui: https://launchpad.net/juju-core/1.14/1.14.012:20
davecheney^ sorry mate, stole your thunder12:20
arosalesdavecheney, will do. I was mostly going to sync up with thumper-afk and jam on saucy and update bug comments.12:20
davecheneyjamespage: is it possible to build this release directly into the juju:ppa/stable PPA ?12:21
davecheneyfor P, Q, R and S ?12:21
rogpeppedimitern: ok, i can reproduce the problem at least12:21
jamespagedavecheney, I'm just prepping for saucy now then I can backport (have a script)12:22
sinzuidavecheney, no12:22
dimiternrogpeppe, good start :)12:22
arosalesdavecheney, thanks for getting it built12:22
sinzuidavecheney, jam controls gobot? did you ask jam to add the tags to goose and 1.14 branch?12:22
davecheneyjamespage: BOJAH12:22
davecheneysinzui: looks lie he did gwacl12:22
davecheneysee https://docs.google.com/a/canonical.com/document/d/1DuQfYq3SB1MJigrnpcuKBkfJfMJaTstQc4bRzN5Q0Uo/edit#12:22
davecheneyi did the rest12:22
sinzuiI did gwacl because I had permission12:22
davecheneyahhh12:23
davecheneycool12:23
* davecheney table flips over our stupid permission model12:23
=== tasdomas is now known as tasdomas_afk
rogpeppedimitern: this is very odd - somehow the call to mgo.Query.One is triggering the TearDownTest call12:31
dimiternrogpeppe, hmmm12:32
davecheneyhttps://code.launchpad.net/~dave-cheney/juju-core/9001-update-release-tarball-for-1.14.0/+merge/18602412:36
=== tasdomas_afk is now known as tasdomas
natefincharosales, davecheney: <unintelligible swearing>  my windows fixes didn't make it into 1.14... which means when you run juju on windows, what you get is "error: cannot determine juju home, neither $JUJU_HOME nor $HOME are set"12:40
jamnatefinch: why didn't those get landed?12:41
natefinchthey were landed the day after 1.14 was cut12:41
natefinch... after 3 landing tries failed12:41
natefinch(from conflicts and then some bot problems IIRC)12:42
davecheneynatefinch: are you sure12:42
davecheneyoh12:42
davecheneyso they only landed on trunk12:42
davecheneyand they were not backported to 1.14 series12:42
davecheneywell, fuck12:42
natefinchcorrect12:42
natefinchindeed12:42
davecheneyarosales: what do you want to do ?12:42
davecheneyi recommend not cutting a new release12:42
mgz1.14.1 with some more things from trunk is fine12:42
davecheneybut comitting nates fix to 1.1412:43
davecheneyand he can do a dodgy .zip release12:43
mgzright.12:43
davecheneyit'll be fine12:43
davecheneynatefinch: can you please propse the merge anyhoo12:43
natefinchdavecheney: sure12:43
davecheneywe'll figure out the policy reguardless12:43
dimiternrogpeppe, any more progress?12:44
davecheneycan I get a F'yeah for https://code.launchpad.net/~dave-cheney/juju-core/9001-update-release-tarball-for-1.14.0/+merge/18602412:44
rogpeppedimitern: just more weirdness12:44
mgzdavecheney: I don't like it much, because just fixing the release script is easy... but it seems okay for now12:44
rogpeppedimitern: i'm starting to suspect a compiler bug - i'll try against go tip12:44
jamdavecheney: I find it very inverted to have juju-1.14 as a label on gwacl/goose, but I can understand it from a pragmatic perspective.12:45
arosalesdavecheney, yes we'll need to get nate fixes in. Sounds like a 1.14.1 is needed.12:45
dimiternrogpeppe, wow.. these always come to me12:45
rogpeppedimitern: yeah12:45
rogpeppedimitern: i think somehow a stack frame may be being mashed12:45
davecheneyjam: it was something that happened without much thought12:46
natefinchjam, mgz: how do I cherry pick revisions to merge into 1.14?  I have 1.14 checked out... but I don't want to waste people's time figuring out the bzr syntax12:46
arosalesdavecheney, so is it correct to state that a 1.14.1 is needed?12:46
davecheneya while back wallyworld___ and I started tagging goose with juju-x.y.z tags12:46
davecheneyand it snowballed form there12:46
davecheneyfrom there12:46
mgznatefinch: similar to your revert the other day12:46
davecheneyarosales: i'd like to avoid it12:46
jamnatefinch: cd $1.14 branch12:46
rogpeppedimitern: because i can put a defer func(){sleep(some time); log.Printf("returning")}() into mgo.Query.One and it sleeps and i see the print12:46
jamnatefinch: bzr merge -c REVINTRUNKITLANDED lp:juju-core12:46
davecheneyand cut a special .zip file for windows from the tip of 1.14 series12:47
rogpeppedimitern: but a log statement immediately after the return i never see12:47
dimiternrogpeppe, right12:47
dimiternrogpeppe, well, if it works with tip, we have something at least12:47
arosalesdavecheney, will there be a tools mismatch if natefinch pull from 1.14 tip?12:47
davecheneyarosales: no, they won't notice12:48
dimiternrogpeppe, any ideas how to work around it?12:48
rogpeppedimitern: i need to characterise it first12:48
arosalesthey = juju, correct?12:48
davecheneybecause nate's build will still think it is 1.14.012:48
arosalesdavecheney, akc12:48
arosalesack12:48
davecheneyto be sure, this is a BAD idea12:48
davecheneybut something we can live with12:48
davecheneyto avoid resetting the clock with the work jamespage is doing12:48
arosalesdavecheney, ok12:48
jamnatefinch: with the caveat that you have to then backout your logrotaet changes again12:49
jamespagedavecheney, don't like the sound of that12:49
jamespageI just uploaded to saucy12:49
jamnatefinch:  "bzr merge -c 1788 lp:juju-core" should be about right12:49
natefinchjam: yep, had already taken that into account12:49
davecheneyjamespage: thank you12:49
davecheneyarosales: this is more importnat than a small bodge12:49
rogpeppedimitern: thank goodness the bug doesn't seem to be too sensitive to code changes12:49
davecheneyjamespage: i can cut 1.14.1 as soon as natefinch 's change is ready12:50
davecheneycan you upload that to sauce and backport today ?12:50
natefinchjam: should I be merging directly into the 1.14 branch or a branch off of that?12:50
dimiternrogpeppe, good12:50
davecheneynatefinch: checkout 1.14 branch12:51
davecheneymerge the change there12:51
natefinchdavecheney: cool12:51
davecheneybzr push lp:~natefinch/juju-core/1000-fix-windows-build12:51
rogpeppedimitern: just building go tip12:51
jamespagedavecheney, later tonight yes - you caught me on a baby break :-)12:51
davecheneythen go to lp12:51
davecheneyjamespage: ok, we'll do it properly12:51
davecheneysinzui: do you want to drive 1.14.1 ?12:52
dimiternrogpeppe, did you manage to isolate it to a minimal code snippet?12:53
sinzuidavecheney, I suppose so.12:53
davecheneysinzui: "no" is a perfectly acceptable answer12:53
rogpeppedimitern: ha ha12:53
dimiternrogpeppe, what?12:53
davecheneynatefinch: is there a bug for the JUJU_HOME thing ?12:53
davecheneyi need to assign it to a 1.14.1 milestone12:53
natefinchdavecheney: I think so, lemme look12:54
rogpeppedimitern: no chance!12:54
sinzuidavecheney, Is dependencies.tsv really wrong in the 1.14 branch?12:54
rogpeppedimitern: (not yet anyway)12:54
natefinchdavecheney: at least indirectly12:54
davecheneysinzui: yes12:54
davecheneyand we dont' use it12:54
* rogpeppe now *actually* builds go tip12:54
davecheneyand we can always add back a correct one in the future12:54
davecheneybut an incorrect file is a hand grenade with the pin loose12:54
davecheneysinzui: in the future the goal is for the release-tarball script (and everything else) to consume dependencies.tsv12:56
davecheneybut it doesn't today12:56
davecheneyso on this stable branch12:56
davecheneyi have voted to remove it12:56
davecheneyas a 2nd pair of underpands12:56
davecheneypants12:56
davecheneynatefinch: https://launchpad.net/juju-core/+milestone/1.14.112:57
davecheneyplease adjust the JUJU_HOME bug to include this series12:57
davecheneyor give me the original bug number and I'll do it12:57
jamespagedavecheney, backports for p q and r uploaded to stable ppa as well12:57
davecheneyjamespage: wonderful12:57
davecheneysorry, you're going tohave to do it all again in 40 minutes12:57
rogpeppedimitern: ok, the issue's still there in go tip12:57
sinzuidavecheney, understood. I see you removed dependencies.tsv from your branch to avoid confusion12:58
natefinchdavecheney: should I not be using lbox propose? It keeps trying to propose against trunk12:58
davecheneynatefinch: nah, that'll fuck up12:59
davecheneyjust propose the branch by hand12:59
davecheneysinzui: correct, this is just to avoid confusion12:59
davecheneywe can always add a correct one tomorrow12:59
dimiternrogpeppe, bugger..12:59
davecheney... for small values of tomorrow13:00
natefinchdavecheney: https://code.launchpad.net/~natefinch/juju-core/014-fix-windows-build/+merge/18602813:00
rogpeppedimitern: now trying to isolate13:00
sinzuidavecheney, I only hesitate because I have just gotten up and finishing my first cup of coffee. I try not to commit when I don't have my wits about me13:00
dimiternrogpeppe, great13:00
davecheneysinzui: https://code.launchpad.net/~dave-cheney/juju-core/9002-set-stable-release-version-to-1.14.1/+merge/18602913:00
davecheneysets the version to 1.14.113:00
davecheneysinzui: like i said, "no" is a perfectly acceptable answer13:00
davecheneythere will be many more releases13:01
davecheneysome less shotgun13:01
davecheneynatefinch: bloody hell, this isn't a small change13:01
natefinchdavecheney: 99% is mechanical, changing $HOME to a small function call13:02
davecheneyok, jam rogpeppe dimitern etc, https://code.launchpad.net/~natefinch/juju-core/014-fix-windows-build/+merge/18602813:02
natefinchdavecheney: the comment is unfortunate, since it was written when the change was just a single line :/13:02
davecheneycan we get a _113:02
davecheney+113:02
davecheneynatefinch: found that bug ?13:03
davecheneysinzui: i'm going to reuse the 1.14.1 release notes13:03
sinzuiunderstood13:03
sinzuidavecheney, LGTM13:03
davecheneytradition dictates that i mention that 1.14.0 was replaced with 1.14.113:03
davecheneynobody seems to care13:03
rogpeppenatefinch: please can you use lbox propose (you can use lbox propose -for lp:juju-core/1.14) so the changes can be seen in context13:04
davecheneysinzui:13:04
davecheney1.11.4 is a small bugfix release for 1.11.3, please refer to the13:04
davecheneyrelease notes for 1.11.3 for full details.13:04
natefinchrogpeppe: I tried that and it still tried to do it into trunk13:04
davecheney^ for example, this was one previous release note13:04
rogpeppenatefinch: it worked ok for me recently13:04
natefinchdavecheney: I think I was hallucinating... no bug for that, but we do have: https://bugs.launchpad.net/juju-core/+bug/119575713:04
_mup_Bug #1195757: Package Juju for Windows <juju-core:Triaged> <https://launchpad.net/bugs/1195757>13:04
davecheneynatefinch: that's a paddling13:05
rogpeppenatefinch: it might work now if you just do lbox propose13:05
davecheneyI have to AFK for 10 mins to meet my partner at the train station (it is late, and she's coming home on her own)13:05
davecheneyi will be back v shortly13:05
natefinchrogpeppe: trying13:06
natefinchrogpeppe: no luck13:10
natefinchrogpeppe: it completes, but nothing is in rietveld13:10
rogpeppenatefinch: did it print a codereview link?13:11
natefinchrogpeppe:  no :/13:11
rogpeppenatefinch: try "lbox propose -cr -for lp:juju-core/1.14"13:11
natefinchrogpeppe: right, oops13:12
* natefinch forgot the -cr13:12
rogpeppenatefinch: the -cr *should* be automatic, but...13:12
natefinchrogpeppe:  still nothing printed out13:12
natefinchrogpeppe:  and nothing in rietveld....13:13
rogpeppenatefinch: odd. what does it print if you use the -verbose (or -debug) flag?13:13
natefinchrogpeppe:  it's really spammy, but looks like it's bailing because it was already proposed.... http://pastebin.ubuntu.com/6119401/13:15
natefinchrogpeppe: I gotta run for a few to help my wife with the kids, sorry13:15
natefinchrogpeppe: already put her off for a half hour13:16
rogpeppenatefinch: ok, np - i'll pull it locally and have a look in a bit13:16
natefinchrogpeppe:  thanks13:16
rogpeppenatefinch: currently trying to track down dimiter's bug13:16
davecheneybak13:18
rogpeppedimitern: there's definitely *something* wrong going on. i've got it down to this so far: http://paste.ubuntu.com/6119414/13:19
davecheneyrogpeppe: natefinch i think it would be better not to overcomplicate things nad just propose this via lp13:19
rogpeppedimitern: if i change line 42 to use s.machine not s.machines[0], the test passes13:19
davecheneynatefinch: rogpeppe please be mindful of jamespage 's time13:19
davecheneythe more screwing around we do13:19
davecheneythe more time he has to wait13:19
rogpeppedavecheney: ok, i'm on it13:19
davecheneyrogpeppe: thanks13:20
sinzuifor fsck's sake...my computer just rebooted and mir blocked me from logging back in13:20
davecheneyyou can take raring from my cold dead hands13:22
davecheneyi'm not falling for the unstabl eupgrade trap again13:22
jamespagedavecheney, I'm out for the next ~8 hours or so13:22
dimiternrogpeppe, interesting13:22
jamespageif you need more time I can do first thing UK time tomorrow13:22
dimiternrogpeppe, so it might be a stack overflow kind of thing perhaps? with the slice present13:22
davecheneyjamespage: understood13:22
rogpeppenatefinch: in config.expandTilde, shouldn't path.Join in expandTilde be filepath.Join ?13:23
rogpeppedimitern: no13:23
sinzuisaucy has been quite a naught series. My keyboard is often unmapped and the audio drivers work on the roll of the dice13:23
rogpeppedimitern: it really seems like a compiler bug13:23
rogpeppedimitern: ha ha!13:23
rogpeppedimitern: i thought you meant something suitable for a stackoverflow.com question!13:23
rogpeppedimitern: i don't *think* it looks like stack overflow13:23
rogpeppedimitern: after i've done this review, i'll have a look at the assembly13:24
arosalesdavecheney, so jamespage  uploaded 1.14.0 to the ppa but the client still needed a 1.14.1 release, which is in progress, correct?13:24
davecheneyarosales: yes13:25
* arosales thought natefinch was just going to use 1.14 tip . . .13:25
davecheneyarosales: we changed our minds about 2 pages ago13:25
arosalesok13:25
davecheneyjamespage prefered that we did it correctly and said there was no blocker in getting 1.14.1 done 1st thing UK time13:25
arosalesaside from to companies holding their PR announces13:26
arosaless/to/two/13:26
davecheneyarosales: i need you to give me clear directoin13:26
arosalesI guess I let folks know we'll shoot for tomorrow13:26
dimiternrogpeppe, ok, thanks for the help13:26
davecheneyi can sto the 1.14.1 process and as soon as nates' windows fiz lands we can build a dodgy .zip version from trunk13:27
davecheney/s/trunk/tip13:27
arosalesdavecheney, jamespage: do you think we'll have a 1.14.1 ready UK morning?13:27
arosalesdavecheney, nah is already in progress13:27
davecheneyarosales: ok, understood, the plan is to continue to release a 1.14.1 as soon as possible13:30
arosalesdavecheney, to confirm does 1.14.1 have natefinch fixes? Or is that still under review by rogpeppe ?13:30
davecheneystill in review13:30
davecheneywhen it lands 1.14.1 will contain nates fixes13:31
sinzuidavecheney, who is adding the tags to goose and 1.14.x branch? You?13:31
rogpeppearosales: still in review, sorry - it's quite a substantial change13:31
davecheneybot is batting 2 for 013:31
davecheneysinzui: I will do it13:31
* arosales not sure how davecheney is cutting a 1.14.1 release with code still under review13:32
* arosales goes to break the news that we are not releasing 1.14 today . . .13:33
davecheneyarosales: stop13:35
davecheneywe _CAN_ release a 1.14.x today13:35
davecheneywe can bodge up a windows client release without going through the release process13:35
davecheneyarosales: i can cut the release as soon as the banch land13:36
davecheneythe commands are queued up in my buffer13:36
davecheneyarosales: i am waiting on your word to try for a proper 1.14.1 or keep 1.14.0 that we have now and bodge in the windows zip fix13:38
davecheneyif we go for the latter option13:39
davecheneywe can fix it in short order with a proper 1.14.1 release on the next day13:39
arosalesit would be nice to have something that works today13:40
arosalesand then we can fix the bits behind the scenes by tomorrow13:40
arosalesdavecheney, what if we go with the former option13:41
davecheneyarosales: both options need natefinch rogpeppe  to land that branch13:41
davecheneygoing with a proper 1.14.1 probably adds another 8 hours delay13:41
davecheneyat minimum13:41
rogpeppedavecheney: i've just finished the review13:41
davecheneyrogpeppe: sweet13:41
rogpeppedavecheney: it LGTM with one minor issue13:41
davecheneymark that sukka as approved13:41
davecheneyoh13:41
rogpeppedavecheney: one place is using path.Join instead of filepath.Join13:42
rogpeppedavecheney: as nate's not around, i think i might just fix it, and approve it myself13:42
rogpeppedavecheney: could you confirm my comment on https://code.launchpad.net/~natefinch/juju-core/014-fix-windows-build/+merge/186028 please?13:43
natefinchrogpeppe:  sorry... wrangling two kids right now... yes, you're probably right13:44
rogpeppenatefinch: are you able to fix it and approve soon, or i could do it if you can't13:44
natefinchrogpeppe: probably better for you13:44
natefinchrogpeppe: sorry and thanks13:46
arosalesdavecheney, lets proceed with the following:13:46
arosalesfor today we use the 1.14.0 with a hacked 1.14.0 msft client installer13:46
arosalestomorrow we update the links to use the 1.14.1 msft installer13:47
arosalesdavecheney, ack?13:47
davecheneyarosales: ack13:47
davecheneyarosales: hold13:47
davecheneyi am locating the 1.14.0 debs to produce tools13:48
arosalesnatefinch, I'll need a 1.14.0 tools that uses 1.14.0 tip download link13:48
davecheneyarosales: um, can you say again please13:50
rogpeppedavecheney: approved13:50
davecheneybecause we havne't bumped the version string in 1.14 trunk13:50
davecheneyany release produced from there thinks it is 1.14.013:50
davecheneyrogpeppe: thanks13:51
arosalesdavecheney, I was saying for today we can use the 1.14.0 release jamespage already uploaded with natefinch msft client that pulls from tip.13:51
arosalesafter natefinch has the 1.14.0 build from tip we can proceede with a 1.14.1 proper release and I can adjust download links tomorrow.13:52
davecheneyarosales: yes, that is is correct13:52
davecheneyarosales: yes, that is also correct13:52
arosalesok so now I just need natefinch to kick a 1.14.0 msft client build that pulls from tip.13:53
davecheneyok, please hold13:54
davecheneyhttps://code.launchpad.net/~dave-cheney/juju-core/9002-set-stable-release-version-to-1.14.1/+merge/18602913:54
davecheneywaiting on this merge to fail13:54
davecheneyif it _succeeds_ i'll have to back it out13:55
sinzuiarosales, by adjust the download links, I think you mean remove the 1.4.0 tarballs from Lp after the 1.4.1 files re uploaded. Lp will show the new links because they are the latest uploads and since they are the only uploads on series 1.14, that is the only links available for that series14:00
arosalessinzui, no I mean downloads links of the msft installer from juju.u.c/install14:01
davecheneyarosales: sinzui which we haven't yet procued14:01
davecheneyso we can bodge that14:01
davecheneysinzui: arosales ignore14:02
davecheneywhat i just said was wrong14:02
davecheneyignore it14:02
davecheneyi will _not_ be changing the tarball on the milestone14:02
davecheneyas jamespage has alreday submitted it14:03
sinzuiah!14:03
davecheneynate, do this to make yorself a new tarball14:03
davecheneycd scripts/build-release-tarball/14:03
davecheneychange line 41 to read14:04
davecheneybzr-checkout lp:juju-core/1.14 $TAG launchpad.net/juju-core14:04
davecheneybzr-checkout lp:juju-core/1.14 -1 launchpad.net/juju-core14:04
davecheneythen run14:04
davecheneybash build-release-tarball.bash juju-1.14.014:04
davecheneythis will produce a tarball that is identical to what we uploaded to the milestone, but follows 1.14 trunk14:04
davecheneythen you should be able to feed that to whatever prodeuces your windows .zip build14:04
arosalesnatefinch, note I'll need a msft download link to give the web team asap.14:08
davecheneynatefinch: ping me if my instructions are unclear14:09
rogpeppedimitern: i still don't know the underlying cause, but i've discovered a quick workaround for your problem (which also fixes a bug in your code)14:10
rogpeppedimitern: set s.machines to nil at the start of provisionerSuite.SetUpTest14:10
dimiternrogpeppe, ah, ok will do, tyvm14:11
dimiternrogpeppe, if you manage to isolate and file a golang bug report, please give me a link to put it in a comment there14:12
rogpeppedimitern: that's something you want to do anyway - otherwise you add 3 new machines in each test, ending up with 9 in total by the start of the last test14:13
natefincharosales, rogpeppe, davecheney: back, sorry for the delay14:13
rogpeppedimitern: tbh, you could probably just rename to SetUpSuite14:13
dimiternrogpeppe, no, I need a SetUpTest with the machines created before each case14:14
rogpeppedimitern: ah, ok14:15
rogpeppedimitern: in which case you want to reset the slice14:15
rogpeppedimitern: aaaargh!14:15
rogpeppedimitern: i see the problem!14:15
rogpeppedimitern: it's not a compiler bug at all14:16
rogpeppedimitern: the above issue *is* your problem14:16
rogpeppedimitern: and that's it14:16
arosalesnatefinch, no worries I understand daddy duty14:16
rogpeppedimitern: you're using Machines with stale state14:16
arosalesnatefinch, I was just needing a msft client installer that uses 1.14.0 tip14:16
rogpeppedimitern: hmm, though...14:17
natefincharosales: no problem, working on it14:17
rogpeppedimitern: i still don't see why TearDownTest is being called14:18
arosalesnatefinch, thanks, ping me when you have it.14:18
rogpeppedimitern: ah, yes, i understand that too now14:18
rogpeppedimitern: it all becomes crystal clear, phew14:18
davecheneyarosales: i have located the ppa's for 1.14.014:19
davecheneyproceeding to make tools14:19
davecheneylets hope this release bloody works14:20
arosalesdavecheney, lol14:20
natefincharosales: http://ubuntuone.com/7aKY92pbRTXGe6IiSVzcMl14:20
* rogpeppe crosses his fingers for the release14:20
dimiternrobbiew, oh really?14:20
robbiewrogpeppe: ^14:20
robbiewlol14:20
rogpeppelol14:20
dimiternoops :) sorry14:20
arosalesI did that yesterday14:21
rogpeppedimitern: yeah14:21
mgzit's funny every time it happens... :)14:21
arosalesdang auto complete14:21
dimiternquassel had better tab completion than xchat it seems14:21
dimiternuntil it stopped working at all14:21
rogpeppedimitern: it would have helped the diagnosis quite a bit if mongo didn't panic in Session.cluster, but returned an error instead14:21
dimiternrogpeppe, so you replaced the panic and caught it?14:22
rogpeppedimitern: no14:22
rogpeppedimitern: the panic was just a symptom of the bug in your code14:22
dimiternrogpeppe, what's the bug?14:23
rogpeppedimitern: the bug is the one i pointed out above - you don't reset the slice in SetUpTest14:23
rogpeppedimitern: which means that the first machines that you call Refresh on are from a previous test, and so have a stale mongo connection14:24
dimiternrogpeppe, oh god, yes!14:24
rogpeppedimitern: innit14:24
dimiternrogpeppe, so it's no compiler bug then14:25
rogpeppedimitern: no indeed.14:25
dimiternrobbiew, whew :)14:25
dimiternrobbiew, sorry14:25
rogpeppedimitern: and my ba14:25
dimiternrogpeppe, I really ought to start typing 2 chars at least before pressing tab14:26
dimitern3 actually14:26
rogpeppedimitern: and my length of time to find the problem was exacerbated by the fact that i was seeing Query.One return - which it was, but only because a panic was happening14:26
rogpeppedimitern: your IRC client should be better behaved14:26
rogpeppedimitern: and choose the last-addressed username by default14:27
dimiternrogpeppe, absolutely - quassel does that14:27
rogpeppedimitern: (mine seems to do that)14:27
rogpeppedimitern: Konversation works pretty well for me14:27
dimiternrogpeppe, ah, there it is - just a option I need to tweak, and now it completes last spoken to nick14:28
natefinchdavecheney: is there a script or something that sets the release number in the code?  I need to get the windows installer script hooked into something like that, so we don't have to hand-update the version in the script14:30
davecheneynatefinch: there is a little logic in the package recipe that extracts the detail from version/version.go14:30
* davecheney finds link14:30
sinzuiokay, davecheney , natefinch I don't understand how we are avoiding a tools mismatch...oh, ^ are we tinkering with the version?14:31
davecheneynatefinch: http://bazaar.launchpad.net/~dave-cheney/juju-core/package/view/head:/debian/rules#L1014:32
davecheneysinzui: no, no tinkering14:32
davecheneythe version/version.go file continues to report 1.14.014:32
natefinchsinzui: tinkering would be required for it to know it's a different version14:32
davecheneyit sounds like nates biuld script doesn't extract the version automagically like the packageing does14:32
natefinchdavecheney: right now my build script is cd cmd/juju && go-windows-386 build14:34
davecheneynatefinch: that'l work fine14:34
davecheneyseeya mup14:35
sinzuiAre we incrementing to 1.14.1 *after* natefinch cuts the window's installer. Thus the windows release is different from the *nix release?14:35
natefinchdavecheney: good :)  ...and then open up a windows VM and build the installer from the stuff under scripts/win-installer    ...my intent is to try to get it done via wine and an actual script at some point14:35
davecheneysgtm, lets boil one ocean at at eim14:36
davecheneytime14:36
natefinchdavecheney: agreed14:36
davecheneysinzui: http://paste.ubuntu.com/6119698/14:36
davecheney^ how to bodge the tools uploader for saucy universe packages14:37
sinzui! thank you davecheney14:38
davecheneyim sorry for the hack14:38
davecheneyfolling the various naming gyrations is complicated14:39
davecheneyfollowing14:40
davecheneyarosales: et al, tools coming online very shortly14:40
davecheneysaucy is there14:40
davecheneyraring is coming14:40
davecheneyif anyone is running those series14:40
davecheneyand wants to test14:40
davecheneynow is the time14:40
davecheneysudo apt-add-repository -r  ppa:juju/devel14:41
davecheneysudo apt-add-repository ppa:juju/stable14:41
davecheneysudo apt-get update && sudo apt-get install juju-core14:41
davecheneymake sure $(which juju) points to /usr/bin/juju14:41
arosalesdavecheney, for aws only correct?14:42
davecheneyarosales: at this stage yes14:42
arosalesdavecheney, ok14:42
davecheneywe can sync-tools in a sec14:43
davecheneybut lets make sure nothing is cocked up14:43
arosalesdavecheney, ack14:43
davecheneyjam, mgz: are you able to sync-tools to hp cloud and canonistack ?14:44
mgzdavecheney: I should have the instructions and creds in my inbox somewhere14:45
davecheneymgz: ta14:46
davecheneymgz hold for a few mins14:47
davecheneystill getting Q and P tools14:47
mgzsure.14:47
=== benji__ is now known as benji
davecheneynatefinch: i'm getting the wind up here14:49
davecheneyhow is your confidence on makig the 1.14.0 windows release ?14:50
natefinchdavecheney: 100%.  I already gave the installer to arosales (at least, I gave him a link)14:50
davecheneymgz: sync tools14:50
davecheneyarosales: 1.13.3 to 1.14.0 upgrade worked fine14:50
davecheneynatefinch: cool14:51
davecheneyi need to sign off very shortly14:51
davecheneyotherwise there won't be much of me left to sign on tomorrow14:51
natefinchdavecheney: thanks for all the hard work so late at night14:51
davecheneynatefinch: not a problem, it is what i am here for14:52
davecheneymgz will confirm this is nothing like the hilarity of the 1.10.0 release14:52
mgzthat was indeed fun.14:52
davecheneyhttp://paste.ubuntu.com/6119756/14:53
natefinchin case I get hit by a bus, here's the build process for the windows installer: https://docs.google.com/document/d/1WMm6lcUTDA4wZnmA8YzfSXyLnQRz6Fqrr5g2lDtZZes14:53
davecheneyOH SHIT14:53
davecheneythis is not good14:53
davecheneywell14:53
davecheneyit's not terrible14:53
davecheneybut fucking auto sync tools is extending the bootstrap time14:53
davecheneymgz: is this because the 'waves hands' magic data in simple streams needs to be updated ?14:54
davecheneyhmm, only appears to affect ap-southeast-114:55
davecheneytoo bad14:55
davecheneywe'll live with it14:55
davecheneybootstrap works fine on ap-southeast-214:55
mgzdavecheney: maybe, I'm not up to date on what error messages are what with simplestreams14:55
davecheneyyup, just a problem with ap-southeast-114:56
davecheneywe'll survive14:56
davecheneyap-southeast-2 and us-west-2 work fine14:56
davecheneythis is another hilarous eventually consisent problem on aws14:56
sinzui:(14:56
davecheneyarosales: i think, to the extent that I can test at 1 am14:56
davecheneywe're good14:56
arosalesdavecheney, thank you sir for the late night hard push14:57
arosalesmgz, let me know when aws, hp cloud tools are sync'ed14:57
davecheneyif anyone wants to test in hp cloud14:57
arosalesI can work on Azure14:57
davecheneyit will work right now without tools synced14:58
davecheneyit will just take longer14:58
davecheneyto bootstrap14:58
davecheney-v, always -v14:58
mgzarosales: I'm assuming aws is done, because I'm using that as a source14:58
davecheneynatefinch: don't forget to port your patches for the windows fixes, path => filepath back to trunk15:02
natefinchdavecheney: thanks15:02
mgzhm, sync-tools needs a -v15:07
mgzhaving it just sitting there quietly makes me nervous15:07
mgzokay, canonistack done15:07
davecheneyarosales: http://ec2-54-202-26-90.us-west-2.compute.amazonaws.com/?p=415:08
davecheneydone15:08
mgzand cute, 1.14 includes the armhf binaries, if canonistack grows an arm region :)15:08
davecheneymgz: but only for saucy15:08
davecheneyatm15:08
davecheneyall: i have to sign off15:08
davecheneybe online in (insert short amount of time)15:08
sinzuithank you davecheney15:08
davecheneywe'll do a proper 1.14.1 tomorrow15:08
mgzhp... I need to check creds with arosales I think15:08
arosalesdavecheney, woot15:08
mgzdavecheney: thanks, have a good night15:08
davecheneynight ya'll15:08
arosalesdavecheney, have a good night15:09
arosalesthanks for your work15:09
arosalesi'll sync with sinzui on 1.14.115:09
arosalesmgz, do you need a password reset for hp?15:09
mgzarosales: I'm going to check now15:14
mgzcan't remember where we left it last time15:14
arosalesok, let me know.15:14
arosalesI think you said you were able to login, but we had to update your info.15:15
mgzarosales: what user name do you have for me on that account?15:17
sinzuiarosales, Lp will not promote the 1.14x releases because they are on an older series: https://launchpad.net/juju-core lists the latest release from trunk15:17
mgzthe issue is my own account uses my canonical email address, so not sure how I log into the tools one instead15:18
sinzuihttps://launchpad.net/juju-core/+download lists the release after it lists all the releases from trunk15:18
dimiternok, wrong channel15:31
rogpeppedimitern: lovely, looking15:31
dimiternrogpeppe, https://codereview.appspot.com/13720045/ I have a review for you :)15:31
dimiternrogpeppe, thanks15:31
gary_posterdimitern, we like having you over there though :-)15:32
dimiterngary_poster, I'm there all the time :)15:33
gary_postercool :-)15:33
rogpeppedimitern: ping15:55
dimiternrogpeppe, here15:56
rogpeppedimitern: just wondering why the provisioner auth function allows access to any machine15:57
dimiternrogpeppe, how else would you do it?15:57
rogpeppedimitern: doesn't that depend on whether the machine is an environmanager or not?15:57
dimiternrogpeppe, hmm it should yeah15:57
rogpeppedimitern: as it is, any machine can remove any other machine...15:58
dimiternrogpeppe, how about the lxc provisioner?15:58
dimiternrogpeppe, it has to be able to change any machine, which has parentId == currently auth'ed machine's id15:59
rogpeppedimitern: that sounds reasonable15:59
dimiternrogpeppe, ok, so I'll make the getAuthFunc smarter15:59
rogpeppedimitern: sgtm16:00
dimiternrogpeppe, it has to be either an environ manager, hence - access to all machines, or a machine agent, and access only that machine's children16:00
rogpeppedimitern: seems reasonable. although...16:01
rogpeppedimitern: should the environ manager be able to remove machines several levels deep?16:01
rogpeppedimitern: i guess it probably should, as i suppose we should be able to force-remove a machine16:01
dimiternrogpeppe, yeah, leave a fallback option16:02
rogpeppedimitern: i wonder if that should be the case for machine agents too16:02
dimiternrogpeppe, what?16:02
rogpeppedimitern: so you're allowed access to all machines below the current machine16:02
dimiternrogpeppe, I don't think this is easier16:03
rogpeppedimitern: i wasn't suggesting it because it was easier16:03
dimiternrogpeppe, it's easy enough to check the parent of a machine, but all parents up?16:03
rogpeppedimitern: but because i think it might be more correct16:03
dimiternrogpeppe, don't think so16:04
rogpeppedimitern: why should the global provisioner be able to force-remove a machine, but a machine-local provisioner not be able to force-remove a container?16:04
dimiternrogpeppe, we shouldn't jump levels of agents like that16:04
dimiternrogpeppe, it will be, but not more than 1 level deep16:04
dimiternrogpeppe, same goes for the environ provisioner16:05
rogpeppedimitern: that means if you've got a totally broken instance/container, you won't ever be able to remove it, no?16:05
dimiternrogpeppe, can you do that now?16:05
rogpeppedimitern: i don't know, but it's a definite issue16:06
dimiternrogpeppe, if it is, it's not an agent api problem16:06
rogpeppedimitern: things do break, and we need to be able to clean up when they do16:06
dimiternrogpeppe, it's more like a management cli/api thing16:06
rogpeppedimitern: hmm, you may well be right16:06
dimiternrogpeppe, yeah, let's not overcomplicate things just now16:07
rogpeppedimitern: so the client does the remova16:07
rogpeppel16:07
rogpeppedimitern: sgtm16:07
dimiternrogpeppe, well, the cli does that now - and it's the only way16:07
rogpeppedimitern: so i guess the environ manager *doesn't* get access to all machines16:07
dimiternrogpeppe, only the ones without a parent?16:08
rogpeppedimitern: yeah16:08
dimiternrogpeppe, ok, looks better to me this way, nicely symmetrical16:08
rogpeppedimitern: yeah16:09
* dimitern has to step out for 10m16:09
* dimitern is back16:26
dimiternrogpeppe, so, about that review?16:30
rogpeppedimitern: still on it16:30
dimiternrogpeppe, ah, ok, sorry16:31
rogpeppedimitern: reviewed16:37
dimiternrogpeppe, cheers16:37
arosalesnatefinch, juju-tools uploaded to Azure, when you have  a spare moment could you test msft client 1.14.0 with 1.14.0-juju-core in Azure?17:49
* rogpeppe finishes for the day17:49
arosalesmgz, did you get the hp tools uploaded?17:50
rogpeppeg'night all17:50
natefincharosales: will do17:50
arosalesrogpeppe, night17:50
arosalesnatefinch, thanks.17:50
natefincharosales: I presume normally, we'd do that *before* the announcement, right? :)17:51
arosalesyes, normally it would be part of the release process17:53
arosalesmgz, for aws I see all the tools at /tools17:54
arosaleshttp://juju-dist.s3.amazonaws.com/17:54
arosalesmgz, however for hpcloud I see the 1.14.0 juju-tools @ tools/releases17:55
arosalesfor azure I followed the aws convention17:55
natefincharosales: bootstrapped, waiting for machine 0 to get out of pending state18:07
TheMue*phew* all tests work18:15
TheMueso, time to leave. good night all.18:29
natefincharosales: hmm didn't notice this before, but juju ssh doesn't work, because it expects to run the ssh command (which doesn't exist on windows)  I had always assumed we just used an ssh implementation in Go, but evidently not.18:35
arosalesnatefinch, hmm19:03
arosalesnatefinch, btw did your bootstrap come back with the default juju-tools bucket?19:04
arosaleson the precise release stream?19:04
arosalesnatefinch, not sure how to handle ssh on windows but be good to log a bug for tracking/triage purposes19:04
natefincharosales: how can I tell what bucket it uses?19:07
natefincharosales: juju status gives me19:07
natefinchenvironment: azure19:07
natefinchmachines:19:07
natefinch  "0":19:07
natefinch    agent-state: pending19:07
natefinch    dns-name: juju-azure-x4upm0herf.cloudapp.net19:07
natefinch    instance-id: juju-azure-x4upm0herf19:07
natefinch    instance-state: Created19:07
natefinch    series: precise19:07
natefinchservices: {}19:07
arosaleshmm, not sure post bootstarp19:07
natefincharosales: it hasn't ever gotten off pending19:07
arosalesduring bootstrap you can see which tools are choosen during a --debug19:07
* arosales will fire up an instance from ubuntu19:08
natefinchahh ok. I'll rebootstrap after I try deploynig some stuff19:08
arosalesnatefinch, without ssh on windows your nice page, https://juju.ubuntu.com/docs/getting-started-keygen-win.html, is invalid, correct?19:10
arosalesnatefinch, well not invalid just doensn't function atm19:10
natefincharosales: no no. That's still valid and needed to connect to the clouds... it's just that trying to do "juju ssh 0" won't work19:11
sinzuinatefinch, I bootstrap with the -v which tells you what was used.19:12
* sinzui looks for hidden log19:12
natefinchyeah, seems like everyone uses -debug or -v ... seems like we should have some better default than no output19:12
sinzuinatefinch, As a developer withing with unstable tools, it becomes common. Canonistack has good months and bad weeks. I like to know when it is a bad week19:13
arosalesnatefinch, ah you are saying for msft clients connecting to clouds other than Azure19:13
natefincharosales: yep, exactly19:14
arosalesgotcha, just 'juju ssh 0' won't work19:15
natefincharosales: I think there's a major bug with the windows client19:27
natefincharosales: major is probably an understatement.  Critical? Catastrophic?  Will not function.19:30
arosales:-(19:31
arosalesI don't think the juju tools got up thier correctly19:31
arosalesI am re-uploading19:31
arosalesnot sure if that is what you are hitting.19:31
natefincharosales: unlikely.  This looks like the client is telling the server to create directories with windows-style backslash path separators19:32
arosalesnatefinch, ok, I'll let you debug then19:32
natefincharosales: I'll switch to EC2 to double check that it's not azure19:33
arosalesnatefinch, ack19:33
arosaleswell at least you hit that issue too19:38
* arosales types into wrong window19:39
hazmatnatefinch, you should be able to ssh into and have a look at the cloud init log19:46
hazmatnatefinch, you can't use juju ssh .. but you should be able to ssh into the dns name with an ssh client.. juju ssh uses the bootstrap node19:49
natefinchhazmat: yeah, ssh is working, and ec2 shows the same symptoms when bootstrapped from the windows client19:50
natefinchsigh19:50
hazmatsinzui,  natefinch, incidentally  on the topic of using -v --debug all the time.. bug 122678619:50
_mup_Bug #1226786: mechanism to set default --params to commands <juju-core:New> <https://launchpad.net/bugs/1226786>19:50
hazmatnatefinch, can you pastebin /var/log/cloud-init-output.log19:50
natefinchhaz19:51
natefinchhazmat: yep19:51
natefinchhazmat: https://pastebin.canonical.com/97613/19:55
natefinchhazmat: an example of the problem is   mkdir -p varlibjujudb/journal19:57
hazmatjam, incidentally all the places your doing for ssl cert support are all the same places we'll need to hit up again for proxy afaics19:57
hazmatnatefinch,  that does look suspicious, client path separator perhaps.. is juju running on the machine?.. the end state there looks sane (mongo running, juju state initialized)20:00
natefinchhazmat: yeah, the path separator was my first thought.  I also see  \varlogjujumachine-0.log and  \var\lib\juju\server.pem as files in the root directory  (note, those are the filenames... not a path)20:02
natefinchhazmat: mongo is running, but jujud is not20:04
hazmatnatefinch, we've got tons of filepath.Join which is going to be problematic20:04
natefinchhazmat: yeah.... ironically, by using the "right" function... we're shooting ourselves in the foot20:04
hazmatit would be nice to see the raw cloudinit, i'm curious how yaml is treating the \ separation20:04
hazmatindeed20:04
natefinchhazmat: I'm kinda surprised that the client is the one that defines the paths that get set up on the server20:05
hazmatnatefinch, its only for bootstrap's cloudinit20:05
hazmatnatefinch, although possible we'll see other issues with charm deploys and bundle assembly20:05
natefinchhazmat: I guess that makes sense20:05
hazmatsince those are also client assembled20:05
hazmatnatefinch, so the quick fix for this release, is to make a utils.PathJoin which does the unix thing, and replace extant uses of filepath.Join20:06
hazmatalthough we really need to check for other uses of filepath i guess since there are others uses of os.PathSep20:06
natefinchhazmat: yeah20:06
hazmatnatefinch, and then revisit as we get further into windows support20:07
natefinchhazmat: k. I'll start working on that20:09
natefinchhazmat: if it were me, I'd pull the current installer off the website... it's just cause heartache and pain20:09
hazmatnatefinch, given we have a press release out..20:09
natefinchhazmat: yes, but the big announcement was azure, not windows client.  I was looking for the windows client announcement, and almost didn't see it20:10
hazmati'd rather yank it to be honest, and replace with a note for windows then have peopl dl something totally broken20:10
hazmatarosales, ^20:10
hazmatyeah.. its making its way through the news wires/pundit sphere now..20:11
hazmatnatefinch, i don't actually see the download though20:11
natefinchhazmat: https://juju.ubuntu.com/install/20:12
hazmatoh. there it is20:12
hazmatjcastro, do you know how to update that till we get this fixed20:12
hazmatthe windows download link.. its off of juju.ubuntu.com which we could fix there.. but really we also want to yank the binary from http://assets.ubuntu.com/sites/ubuntu/latest/u/files/juju/juju-setup-1.14.0.exe20:13
* hazmat escalates via email20:14
hazmatmramm, ^20:14
natefinchhazmat: thanks, I was going to do the same20:14
natefinchhazmat: also: Searching 784 files for "filepath.Join"  307 matches across 92 files20:14
mrammarosales: ^^^^20:15
* arosales reading backscroll20:16
natefincharosales: short version: windows client is unusable20:16
hazmatarosales, posted to canonical-juju20:16
arosaleshazmat, mramm, jcastro and I no longer have access to juju.u.c20:17
arosalesI can file an RT and hopefully the IS team have access, but other than than we'll need to await the web team.20:18
* arosales sure the IS does.20:18
mrammI would file an RT, IS does have access!20:18
mramm;)20:18
arosaless/IS/IS team/20:18
arosalesnatefinch, is this a 1.14 specific issue you didn't see in your earlier testing?20:19
hazmatmramm, WTF to the rescue ;-)20:20
natefincharosales: windows-specific ...  the version doesn't really matter.  Yes, I didn't see it in earlier testing. My testing was a lot lighter than it should have been. I thought it had already been tested, so I just tested the fixes I made.20:20
=== tasdomas is now known as tasdomas_afk
hazmatnatefinch, really we only need to the filepath.Join fix on cloudinit parts20:25
hazmatnatefinch, at least thats worth testing to see if that works by itself  for bootstrap and deploy20:26
arosalesRT filed20:26
hazmatarosales, cool20:26
natefinchhazmat:  yep, definitely the place to start.  *at least* those parts need to be fixed20:26
arosalestechnically mark baker said in his blog availability tomorrow so natefinch you may have some time to cut a new release if you find the bug.20:27
* hazmat returns to prepping training20:27
natefincharosales: the problem is, it could be 100 spots in the code.20:27
arosalesnatefinch, understood, just letting you know20:29
=== tasdomas_afk is now known as tasdomas
=== tasdomas is now known as tasdomas_afk
andreas__natefinch: could line termination be an issue too? Just wondering, since it's another difference between windows and *nux21:04
natefinchandreas__: could be.   The immediate problems I saw were definitely path separators, though.21:06
andreas__yeah, sure, that was very visible21:07
andreas__in a screenshot someone sent to the list21:07
andreas__just wondering if the content is ok21:07
natefinchme :)21:07
andreas__ah :)21:07
andreas__do you still have that instance up? Might want to run cat -vet on one of those files21:08
andreas__should end in $, not ^M$21:08
andreas__iirc21:08
natefinchit's gone now... but in general, Go is actually really good about always just using \n and not \r\n, even on windows21:08
natefinchandreas__: fixed a couple spots in cloud init where we definitely want unix line endings (or rather, line endings that match the server OS, not the client OS).... seeing what else breaks now21:13
=== thumper-afk is now known as thumper
natefinchthumper: good morning21:23
thumperhi natefinch21:23
* thumper trawls through the emails21:27
sinzuinatefinch, arosales do we want to file a bug about the win client path non-sense and target it to the 1.14.1 milestone?21:36
arosalessinzui, yes as we'll need that but for the milestone and release21:37
arosalessinzui, I don't have the error but I can file a bug and assign to natefinch21:38
arosales1.14 on Azure seems to be working on a sniff test21:39
arosaleshttp://juju-azure-8jdith6sql.cloudapp.net/21:39
arosalessinzui, were you able to do any preliminary testing on HP?21:39
thumpernatefinch: how goes the windows path fun?21:39
sinzuiarosales, natefinch I think the bug just needs to state that the windows client needs to make unix paths when working with the bootstrap node.21:40
sinzuiarosales, I have not21:40
natefinchthumper: I found at least one spot that needed to be fixed.. but still seem to be having problems21:43
thumpernatefinch: need any help or someone to talk to?21:44
arosalesbug 1226840 opened21:44
_mup_Bug #1226840: Windows client needs to make unix paths when working with the bootstrap node <juju-core:New> <https://launchpad.net/bugs/1226840>21:44
natefinchthumper: yeah... I don't know the cloud init stuff well.  Not to mention, my in-laws came over for the evening and it's about dinner time21:45
thumpernatefinch, arosales: does the bug have all the details?21:45
arosalesnatefinch, mind putting your findings in the bug 1226840 and handing off?21:45
_mup_Bug #1226840: Windows client needs to make unix paths when working with the bootstrap node <juju-core:In Progress by natefinch> <https://launchpad.net/bugs/1226840>21:45
natefinchyep21:46
thumperheh, the dreaded slash vs. backslash issue21:46
thumperusing filepath instead of path21:46
natefinchthumper: yep21:47
thumperI think path.Join always uses / yes?21:47
natefinchthumper: yep21:47
thumperbut filepath.Join will use local21:47
thumpernatefinch: so I may need to go grab a windows laptop?21:47
thumperat least I have one in the lounge21:47
thumpernatefinch: how hard is the windows setup?21:47
natefinchthumper: you'd want to build on linux... I don't even know if it'll build on windows21:48
natefinchthumper: using Dave's cross compile scripts, at least, that's what I did21:48
thumperoh...21:48
arosalesthumper, if you want to see the error the installer natefinch is nice for widows21:48
thumpernatefinch: do you have a branch in progress?21:48
thumperI've poked the cloudinit stuff a lot before21:48
natefinchthumper: I have a couple changes, but they're really small21:48
thumpernatefinch: can you commit and push?21:49
natefinchyep21:49
thumperand give me the branch21:49
thumperI could use it as a starting point21:49
thumperand I'll work with Ian and Andrew and Dave to move forwards21:49
thumperdavecheney: you around?21:49
arosalesthumper, current installer is at http://ubuntuone.com/7aKY92pbRTXGe6IiSVzcMl  per natefinch21:49
thumperarosales: no point me using that if it is broken21:49
natefinchthumper: branch is here: bzr+ssh://bazaar.launchpad.net/~natefinch/juju-core/014-fix-windows-build/21:50
arosalesthumper, ack. Wasn't sure if you wanted to see the current error21:50
thumpernatefinch: I wonder how go get works on windows with git & hg branches21:50
thumperarosales: can see it in the bug21:50
natefinchthumper: you have to install git and hg21:50
natefinchthumper: and bzr, obviously21:50
thumperand also, should be easy enough to find the parts in cloud init21:51
thumperif you know what you are looking for21:51
thumperit is the old problem21:51
thumper$1 to hit the machine with the hammer21:51
thumper$9999 to know where to hit it21:51
arosalesthumper ok thanks. Any help on moving the bug forward would be a plus so we can move https://juju.ubuntu.com/install/ back to a download button.21:51
natefinchthumper: really appreciate the help.   Is there anything I need to do to give you permission to work on my branch?21:53
thumpernatefinch: all I do is branch yours and commit locally21:55
thumpercan then push to my area21:55
thumperand it has your changes21:55
thumperDVCS FTW21:55
natefinchthumper: btw, I made a "utils.JoinServerPath" so that we could 1.) find all the spots where we're intentionally not using filepath.Join, and 2.) use it later in case we ever have the client on linux and server on windows (not implemented, but available)21:55
natefinchthumper: ahh, right. awesome21:55
thumpernatefinch: ah intersting point21:56
thumperalthough21:56
natefinchthumper: right now it just passes through to path.Join21:56
natefinchthumper: and the couple of spots in cloud init that use it seem to fix the problems I saw with files in root with backslashes...  but it seems to never finish bootstrap21:57
natefinch(even with the new fix that is)21:57
natefinchthat's where I stopped21:57
thumperotp22:00
thumperok22:02
thumpernatefinch: so you are bootstrapping ec2 from a windows box?22:03
natefinchthumper: correct22:03
* thumper nods22:03
natefinchthumper: also tried azure, same deal22:03
thumperok, I'll take a look and talk with davecheney about his cross comple stuff22:04
thumperand grab one of the kids laptops to test on22:04
arosalesthumper, note I didn't see this problem on 1.14 with ubuntu on Azure, and davecheney tried aws22:05
arosalesI'll bootstrap hpcloud real quick too22:05
thumperarosales: you *don't* see the problem?22:05
natefinchthumper: cross compile is pretty easy.  basically just need  to be running Go from source, run Dave's script to generate the different builders, and then you can run "go-windows-386  build"   (or generically go-OS-arch  in place of regular go tool to run that tool)22:05
thumpernatefinch: is your branch based on 1.14 or trunk?22:06
arosalesthumper, correct, I do _not_ see the problem on ubuntu clients22:06
natefinchthumper: the one I linked is based on 1.1422:06
thumperso who does see a problem?22:06
natefinchthumper: he's not running the client from windows22:06
thumperah22:06
thumperin which case arosales, you don't count22:06
thumpernatefinch: hmm, I'm not running go from source22:07
thumperI may ask davecheney to do the actual compiles for me :-)22:07
thumperhmm...22:07
* thumper starts22:07
thumpernatefinch: we aren't likely to use cloudinit on windows servers22:08
thumpernatefinch: so using a server path there not such a big deal22:08
thumpernatefinch: but useful to have the method for all the agents22:08
arosalesthumper, just passing along a data point.  I'll let you get to it.22:11
thumper:)22:11
thumperack22:11
natefinchthumper: thanks again for the help.  I'm going AFK for dinner, but will check in after. You can also throw builds at me to run until Dave gets online.  he may be in late, he was up until 1am.22:20
* thumper nods22:21
=== natefinch is now known as natefinch-afk
thumperfound and fixed one22:21
natefinch-afkthumper: nice22:21
thumperin a way, this is kind of funny22:23
thumpernatefinch-afk: lp:~thumper/juju-core/014-fix-windows-build, I have just used path.Join in cloudinit and upstart, as those are linux specific as far as I know22:49
thumperand I think we need more thought about supporting multiple server operating systems22:49
thumperI also added a trace to write out the cloud init that is generated22:50
thumperso the commandline can see the bootstrapped cloudinit22:50
thumperdavecheney: can you ping when you arrive?22:50
thumperdavecheney: although if you are starting late due to your late start, you might hit me at the gym, so I'll reply when back22:50
thumpernatefinch-afk: at least writing out the cloudinit will let us eyeball the setup so we can see if there are other places where we are missing slash/backslash tweaks22:51
thumpersimplest way to see it is to do this:22:51
thumperjuju bootstrap --log-config=juju.environs=TRACE --show-log22:52
natefinch-afkthumper: back22:52
natefinch-afkthumper: good thinking about printing out cloudinit ... probably handy to have anyway22:52
thumpergah, I hit the 1.14 / trunk azure thing trying locally22:53
thumpernatefinch-afk: yeah, I think so22:53
thumperand since it is at TRACE level22:53
thumperyou have to explicitly ask for it22:53
thumper--debug won't show it22:53
thumpernatefinch-afk: there was another place in cloudinit you had missed, but also the upstart service scripts22:53
thumperit seems that go tries to be magic22:54
thumperif you call filepath.Join('/var/lib/juju', 'blah') on windows it gives you '\var\lib\juju\blah'22:54
thumperat least that is what it looks like22:55
thumpernot tried it22:55
natefinch-afkthumper: ug... that seems like too much magic.22:55
thumperI think that is why we see 'varlibjujudb'22:56
thumperas the \v -> v22:56
thumperweird that sometimes the slashes get switched completely22:56
thumperand sometimes, just bits of it22:56
natefinch-afkit's interesting that in certain spots we were getting no separator and certain spots we got backslashes22:56
natefinch-afkyeah22:56
=== natefinch-afk is now known as natefinch
thumperif you are able to comple and run that branch, with the logging and pastebin the cloudinit, we can eyeball it while it tries to start22:57
thumpernatefinch: in two weeks, I'll be an hour clouser to you22:57
thumperas nz hits UTC+1322:57
natefinchheh22:57
thumperseems that there is a month of that, then we hit another hour closer as you fall back an hour22:58
thumperhi davecheney22:58
thumperand your alter ego davechen1y22:58
natefinchthumper: error: flag provided but not defined: --show-log22:59
thumperah... yeah22:59
thumperuse --debug isntead22:59
thumperbut the log-config should still work22:59
thumper--show-log is obviously just on trunk22:59
natefinchthumper: <unintelligible swearing>   why the hell does the command line's scrollback default to like 200 lines :/23:01
thumperhaha23:01
thumpercan you set it to bigger?23:01
natefinchthumper: yeah23:01
natefinchdefault is 300.... wtf is this, 1990? :/23:02
natefinchthumper: http://pastebin.ubuntu.com/6121592/23:04
natefinchthumper: apologies ahead of time for line ending munging23:04
natefinchthumper: actually sort of nice for the certs, though :)23:05
* thumper reads23:05
thumpernatefinch: ok, that looks like it should work23:07
thumperlets wait and see23:07
natefinchthumper: looking good.... machine 0 is up23:08
thumper\o/23:09
thumpernow the rest of the cloudinit bits are created by machine 023:09
thumperso there shouldn't be any more issues23:09
thumperlets get this merged into 1.1423:09
thumperand then into trunk23:09
thumpernatefinch: I can push and propose mine, and you can review if you like23:10
natefinchsounds good23:10
thumperoh ffs23:11
* thumper just uses LP23:11
natefinchhaha23:11
natefinchthumper: just in case, here's the contents of cloud-init-output.log: http://pastebin.ubuntu.com/6121614/23:12
thumpernatefinch: https://code.launchpad.net/~thumper/juju-core/014-fix-windows-build/+merge/18617923:14
thumpernatefinch: so you were able to get a successful 'juju status' from windows?23:15
natefinchyep23:15
thumperawesome23:15
natefinchthumper: http://ec2-23-20-77-242.compute-1.amazonaws.com/wp-admin/install.php23:15
natefinchthumper: end to end.  makes me happy.23:16
thumper\o/23:16
thumpernatefinch: fyi, you don't need to claim the review before you do it, if you are a member of the team that has a pending review, and you provide a review status with the comment, you claim it automagically23:19
natefinchcool23:20
arosaleswallyworld___, hello do you have an RT open for hosting juju-tools simple streams?23:23
wallyworld___arosales: yes - you were cc'ed on it :-)23:23
wallyworld___i can look up the number23:23
wallyworld___6392523:24
arosaleswallyworld___, thanks for reminding me. I'll post to that RT23:25
wallyworld___ok. hope they act on it soon23:25
natefinchthumper: reviewed, approved.  I gotta close it up for the night23:25
wallyworld___thumper: looks like i missed some fun with windows. i skimmed some of the backscroll23:27
natefinchwallyworld___: fun.... yeah.23:28
natefinchI'm at EOD. Thanks for the help thumper.23:28
davecheneysinzui: ping, we should tool up for a 1.14.1 release later this week23:31
davecheneyjust as a tester23:31
thumperwallyworld___: yeah23:32
thumperwallyworld___: there is a clear difference between something running on windows and not crashing, and having the tool actually work23:33
thumperwallyworld___: magic path issues23:33
wallyworld___sigh23:33
wallyworld___unix was there first23:33
thumperexpect more pain like this when we want to have the server be windows23:33
wallyworld___why didn't windows stick to convention23:33
* thumper shrugs23:33
thumperI expect that msdos just followed the earlier dos23:34
thumperand it flowed from there23:34
wallyworld___cpm23:34
wallyworld___thumper: i have a thing at the school today at the same time as the code review meeting23:34
thumperok23:34
wallyworld___so we could reschedule till tomotrrow23:34
thumperdid you want to do it earlier?23:34
thumperI'm also happy to reschedule23:35
wallyworld___i'd prefer to do some coding :-)23:35
thumperhaha23:35
wallyworld___i want to get some bootstrap things done23:35
thumperack23:35
wallyworld___should be finished today though, hence clear my plate wrt that issue23:35
wallyworld___i just wish my branch had been looked at by the ocr last night :-(23:36
wallyworld___sigh23:36
thumperwallyworld___: which branch, I could look23:42
wallyworld___thumper: that would be neat, but be careful what you wish for :-) https://codereview.appspot.com/13632056/23:42
wallyworld___i had a high level pre imp with roger, but the exact implementation was not discussed, just the high level removing of reties in s323:43
thumperwow23:43
wallyworld___it's a lot of files touched, but only a few lines in each23:43
thumperI'll look when back from the gym23:44
* thumper nods23:44
wallyworld___ok, thanks muchly23:44
wallyworld___bootstrap is fast again now :-)23:44
wallyworld___and live tests on ec2 pass23:44
wallyworld___but they sure do take ages to run23:44
thumper\o/23:46
thumperI know what you mean about wanting to code again23:46
wallyworld___yeah23:46
thumperI've now cleared my plate from all previous pending branches23:46
thumperand was going to start with the kvm stuff this morning23:47
thumperbut saw the windows bootstrap issues23:47
wallyworld___cool23:47
thumperso helped out there23:47
thumperwill look at your review this avo, and start poking kvm23:47
wallyworld___ok, ta23:47

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!