/srv/irclogs.ubuntu.com/2013/08/01/#juju-dev.txt

davecheneywallyworld: bigjools needs gwacls updated on the bot ?00:00
* bigjools needs gwacl updating on there so I can land a dependent core branch00:00
wallyworldi think i can. never done it. let me try00:00
bigjoolsmucho grassy ass00:00
wallyworldbigjools: i can ssh into the bot machine and i've found the src tree but when i do a bzr status in the gwacl directory i get: bzr: ERROR: No such file: u'/home/tarmac/trees/src/launchpad.net/gwacl/.bzr/checkout/shelf'00:07
wallyworldnfi00:07
bigjoolscan you just do a "bzr up"00:07
bigjoolsseems like it's a checkout00:07
wallyworldwhy wouldn't bzr status work?00:08
bigjoolsnfi00:08
bigjoolsdoes bzr info work?00:08
wallyworldyes00:08
wallyworldthere's a lock preventing update right now. but there's also a build running00:09
wallyworldi'll try again after the build00:09
bigjoolshow often does tarmac run?00:09
bigjoolsyou might need to disable it temporarily00:09
wallyworldactually, it's a permission denied00:09
bigjoolsO_o00:10
wallyworldbecause i'm logged in as ubuntu and it seems i need to be ~tarmac00:10
wallyworldand i don't know the password to su00:11
wallyworldi'll see if it's in an email somewhere00:11
bigjoolscan you ssh tarmac@ ... ?00:11
wallyworldno, permission denied public key00:12
bigjoolsah well00:12
wallyworldi'll try and find a password00:12
bigjoolsthanks man00:12
wallyworldbigjools: done00:23
bigjoolswallyworld: \o/  thanks00:23
bigjoolscoffee++00:23
wallyworldnp. rev is 20700:23
wallyworldyeah coffee00:23
thumperwallyworld: while you are in the landing bot, care to update loggo?01:10
davecheneyheads up, 1.12.0  has been released https://launchpad.net/juju-core/1.12/1.12.001:10
wallyworldthumper: sure01:10
jcastroheya davecheney and thumper!01:12
thumperhi jcastro01:12
davecheneyjcastro: sup!01:13
jcastroshiny 1.12!01:13
davecheneyjcastro: yeah, just doing the paperwork now01:14
thumperwallyworld: to deploy wordpress in a container on machine 0 I can do `juju deploy wordpress --to lxc:0` ?01:14
thumperwallyworld: and for a new machine "--to lxc"01:15
wallyworldthumper: supposedly :-)01:15
thumper?01:15
thumperwallyworld: I'll try01:15
thumpermy eyes are funny01:15
wallyworldthe --to lxc doesn't work i don't think01:15
thumperI think it is lack of oxygen or something01:15
jcastroI deployed an entire wordpress stack to one AWS node today, it was glorious01:15
thumperjcastro: yeah, saw the blog post01:15
* thumper waits for scp so he can bootstrap01:16
thumperthen I can go do something else while it boots01:16
thumperjcastro: do you have any test maas environments?01:16
wallyworldthumper: loggo on tarmac says no new revisions to pull01:17
jcastrothumper: nope01:17
thumperwallyworld: check to see if it is a branch or checkout01:17
thumperwallyworld: also check revno01:17
jcastrothumper: I do know the world wants constraints for the maas provider01:17
thumperwallyworld: want 3901:18
wallyworldthumper: yep, it is01:18
thumperoh... ok01:18
thumperseems updated then01:18
thumper\o/01:18
wallyworldcoolio01:18
thumperjcastro: perhaps I should ask sabdfl for access to his maas :)01:19
jcastroI was going to recommend that exact thing01:20
jcastromims is on holiday so it's probably sitting idle01:20
davecheneyhttps://docs.google.com/a/canonical.com/document/d/1eeHzbtyt_4dlKQMof-vRfplMWMrClBx32k6BFI-77MI/edit#heading=h.o3idq0wwl0yz01:20
* thumper turns the lights on in bigjools's room01:20
davecheney^ nudge, please add agenda items for tonight01:20
davecheneyevilnickveitch: ping01:20
thumperdavecheney: ack01:21
bigjools<huummmmmm>01:21
davecheneystill can't access all hands ...01:23
wallyworldthumper: i didn't know bigjools liked it with the light on?01:30
bigjoolstrue, you normally turn it off for us01:31
wallyworldyep, but then i can't watch :-(01:31
davecheneyaxw: do you think https://canonical.leankit.com/Boards/View/103148069/105051172 is done ?01:34
davecheney(sorry if you don't have perms for leankit)01:35
axwdavecheney: looking01:35
axwI do now01:35
axwdavecheney: it works fine for me01:35
axwI have the 13.04 packaged version01:35
axwnever saw any of the weirdness that was logged in the LP bugs01:36
davecheneycool, assign to yourself and move it to the RHS01:36
axwokey dokey01:36
evilnickveitchdavecheney, hi01:36
wallyworldm_3: marcoceppi: thanks for the replies. could you copy to the list also so others can see your thoughts? sorry, i should have cc'ed you to the original juju-dev email01:37
marcoceppiwallyworld: yeah, just joined the juju-dev mailing list. Surprised I wasn't already on it01:37
davecheneyaxw: how about this one ? https://canonical.leankit.com/Boards/View/103148069/10607170501:38
axwdavecheney: no. thumper has something in the works that changes logging, so I'm holding off for now01:38
* thumper is back01:38
marcoceppiwallyworld: cc'd01:38
wallyworldthanks :-)01:38
davecheneyok01:39
thumperdavecheney: yeah I have a branch pending that messes with logging somewhat01:39
davecheneythumper: ok01:40
davecheneycool01:40
jcastrohey, remove-unit also takes the instance down right?01:41
axwdavecheney: when you say move to the right, do you mean into the review column?01:41
davecheneyjcastro: yes01:41
jcastrothat's what I thought01:42
davecheneyaxw: at your judgement, if it isn't reviewable, then drop it in merged01:42
davecheneyi look in that column when writing the release notes01:42
axwok01:42
thumperwallyworld: so... how do I deploy something into a new machine in a container01:47
thumperwhat's the syntax?01:47
wallyworldthumper: let me check. i thought you needed to use add-machine first01:47
wallyworldthere was a constraint also01:48
thumperright01:48
thumperI'm hoping I can just go 'juju deploy mysql --constraints container=lxc01:48
thumpersomething like that01:48
wallyworldthumper: yes that will work01:50
wallyworldbut it's not what big mark likes01:50
thumper:)01:51
wallyworldhe prefers add-machine01:51
wallyworldto create a container01:51
wallyworldthen --to to select01:51
* thumper tries it01:51
wallyworldthumper: we haven't publicised the constraints version01:51
wallyworldbecause it is verboten01:51
thumperok, that is starting01:51
wallyworldbut the code was already committed01:52
* thumper waits 25 minutes01:52
thumperI have wordpress coming up in 0/lxc/001:52
thumperand mysql in 1/lxc/001:52
bigjoolsthumper: I see node 2 startting01:52
wallyworldyay01:52
thumperand we'll see if they can talk to each other01:52
bigjoolsthat one has a VGA cable on it :)01:52
wallyworlddon't forget to add a relation01:52
thumperbigjools: yep, up it comes01:52
thumperrelation added01:53
thumpernow we wait01:53
axwif anyone's bored, I would appreciate some more eyes on this: https://codereview.appspot.com/12019043/02:10
axwdavecheney: I yoinked the code out of your old branch for debug-hooks02:10
axwthanks02:11
axw:)02:11
bigjoolsthumper: it's booting locally now02:11
thumper\o/02:12
bigjoolsthumper: might be done02:15
thumperbigjools: no, it is downloading the cloud image for the container now02:22
bigjoolsthumper: my interwebs don't look that busy, so I suspect not02:23
thumperah... dumb bug02:23
thumperI saw the same bug on ec202:23
thumperbigjools: how's those interweb tubes now?02:25
bigjoolsthumper: busy02:25
bigjoolsI see blinkenlights02:26
thumper\o/02:26
bigjoolstwo lots of routers, three lots of switches and a modem all looking furious with you02:26
thumperoh fark02:38
* thumper stabs maas02:38
thumperthe uniter internally dies inside the container02:38
thumper/var/lib/juju/MAASmachine.txt: no such file or directory02:39
bigjoolsis container a verb here? :)02:39
* thumper hacks something02:39
* davecheney containers something02:40
thumperaahgg02:40
* thumper stabs the nearest thing02:40
* davecheney goes for lunch02:41
thumperpoo bum02:44
* thumper grrs02:44
thumperI know what that failed now02:45
thumperbigjools: hey02:47
bigjoolsyarp02:47
thumperbigjools: is there a monitor attached to your maas controller?02:47
thumperand keyboard?02:47
thumperbigjools: if you hit http://10.0.0.208 what do you see?02:47
thumperbigjools: I'm hoping for a wordpress error page02:47
thumpersaying no db configured02:47
bigjoolsyou mean the server or one of the nodes?02:48
thumperor something like that02:48
thumperbigjools: just something on the 10 net02:48
thumperbigjools: the server is fine02:48
bigjoolsI don't, I would only ssh into the server and use wget02:48
thumper:(02:49
thumperok02:49
bigjoolsbut you can do that too :)02:49
* thumper noes02:50
bigjoolsthe 10. network is totally isolated for safety, I only access via ssh to the maas server02:50
bigjoolsyou could port forward with ssh02:50
bigjoolsremember how -L works02:50
bigjools-L localport:remotehost:remoteport02:51
bigjoolswhere remotehost is the IP as seen from the host you're sshing into02:51
thumperoh yeah...02:55
thumperwallyworld: definitely got a problem with the machine watcher02:56
thumperon new machines02:56
thumperwallyworld: where it is looking for containers02:56
thumperwallyworld: it isn't getting initial state02:56
wallyworldthat bit was rewritten by william i think02:56
thumper:(02:57
wallyworldthere was a large refactoring some weeks back02:57
thumperagent-state-info: 'hook failed: "config-changed"'03:13
thumperjpw dp O fox tjat?03:13
thumperhehe03:13
thumperhow do I fix that?03:13
thumperthat was an unintentional weird right hand shift cypher03:13
* thumper sets up two ssh tunnels03:44
* thumper wonders if this weird shit will work03:44
* thumper has broken juju in a number of ways today03:44
thumper*sad face*03:54
* thumper needs debug hooks03:54
axwthumper: https://codereview.appspot.com/12019043/ ;)04:08
thumpershortly, off to make a coffee and drown my woes in caffeine04:08
axwheh :)04:09
davecheneyaxw: do you think debug hooks will land this week ?04:21
thumperaxw: I have a feeling that review is going to take longer than I can actually give right now04:36
* thumper hands it to wallyworld04:36
* thumper writes up learnings04:36
* wallyworld is trying to get ^#@!%^^! tests to pass04:36
axwdavecheney: sorry, was making lunch. not sure - still at 0 LGTMs ;)04:40
axwthumper: nps04:41
* thumper back for the meeting later04:56
=== thumper is now known as thumper-afk
=== tasdomas_afk is now known as tasdomas
davecheneywallyworld: https://docs.google.com/a/canonical.com/document/d/1WpyfTgaChhmYFqPESBvfavbqLD1Fsj16NLW5PhmWxis/edit#06:07
davecheney^ as you've made everyone very happy with the --to flag06:07
davecheneycould you write a line or two about it06:07
davecheneynatefinch: bonjour!06:07
wallyworlddavecheney: when is the release? friday?06:08
davecheneyyup06:09
davecheneyor next week06:09
davecheneybut it's been two weeks since we did one06:09
wallyworlddavecheney: i have to go get my kid from school, i'll do it a bit later06:09
davecheneywallyworld: no hurry06:09
wallyworlddavecheney: --to was already released in 1.11.306:11
davecheneywallyworld: really ?06:11
davecheneydid we call it out ?06:11
wallyworldyeah06:11
wallyworldi just checked the relese notes06:11
davecheneyoh well, ignore it then06:11
wallyworldok :-)06:12
* wallyworld drives to do school pickup06:12
davecheneywallyworld:  https://codereview.appspot.com/12232043/06:33
davecheney^ won't this CL drive bigjools even more mental ?06:34
davecheneyie, we're moving state out of the state, back to the local disk ?06:34
wallyworlddavecheney: it's not state but rather configuration06:54
wallyworldstuff that was in env.yaml but will now be separate06:55
wallyworldit's as per big mark and william's design06:55
davecheneyfair enough06:55
davecheneyi'm sure they know what they are doing06:55
wallyworldlet's hope so ;-)06:55
davecheneyconfig is a cluster fuck06:55
wallyworldyep06:55
davecheneyit' can't get any worse06:55
wallyworldyep :-)06:56
wallyworldthis will make it much easier for users06:56
wallyworldit's one step of many06:56
davecheneyi'm sure it's written down06:56
wallyworldto clean up env.yaml06:56
davecheneyi just missed it06:56
wallyworlddavecheney: https://docs.google.com/a/canonical.com/document/d/1ncsNzDHauV_9Fwsm59GjX0-O-_g48UYnObefwtBStG0/edit06:57
davecheneythat's the ticket06:57
rogpeppemornin' all06:57
rogpeppedavecheney: hiya06:57
wallyworldg'day06:57
rogpeppedavecheney: do you know where i can get hold of a copy of juju v1.12 ?06:57
davecheneyrogpeppe: https://launchpad.net/juju-core/1.12/1.12.006:58
rogpeppedavecheney: does that have the dependencies too?06:58
davecheneyrogpeppe: yes06:58
rogpeppedavecheney: great, thanks!06:59
davecheneyuntar it, set your GOPATH to the base of the tar06:59
davecheneygo install ...06:59
rogpeppedavecheney: the idea with config is that bootstrapping gives us a nugget of information that we store to the local disk (or in some other service).06:59
rogpeppedavecheney: we then use that to connect back to the environment06:59
rogpeppedavecheney: it's definitely a change of model, but i think it makes some kind of sense07:00
rogpeppedavecheney: and we've already moved in that direction by storing the CA cert locally07:00
davecheneyrogpeppe: wallyworld not arguing with you two in anyway07:01
davecheneybut bigjools with go ape balls07:01
davecheneythat may or may not be a concern07:01
rogpeppedavecheney: i'm interested in your reaction, because this is definitely a change in direction and i don't think it's been widely discussed07:01
rogpeppedavecheney: and i'm interested what concerns bigjools might have too07:02
davecheneyrogpeppe: in as much as I am repeating what bigjools said, he doesn't like all the stuff we store in ~/.juju07:02
davecheneyi take no position on the matter as I have not been invovled in the design07:02
wallyworldthe long term goal is to store it in the cloud, for jaas etc07:03
wallyworldit's all in the doc07:03
rogpeppedavecheney: do you know why he doesn't like the stuff we store in ~/.juju ?07:03
davecheneyrogpeppe: he has more than one computer07:03
wallyworldhence the long term goal :-)07:03
rogpeppedavecheney: presumably he has to replicate his environments.yaml across all his computers07:03
wallyworldand this isn't adding anything more locally07:04
wallyworldjust moving the deck chairs a little07:04
rogpeppedavecheney: i guess he only has to do that once though (now), for a given environment07:04
rogpeppewallyworld: actually i think this *is* adding more locally07:04
wallyworldand it will still be only once07:04
rogpeppewallyworld: it's manufacturing a control bucket07:04
wallyworldwe do that *now*07:04
wallyworldwith juju init07:04
rogpeppewallyworld: that's different07:05
rogpeppewallyworld: you don't need to use juju init07:05
wallyworldbut most people do07:05
rogpeppewallyworld: and it's a manual editing step07:05
davecheneyi've read that documenta nd mow even more confused07:05
wallyworldsorry, whats manual?07:05
rogpeppewallyworld: and it only happens once for a given environment, no matter how many times that env is bootstrapped07:05
rogpeppewallyworld: you edit environments.yaml manually07:05
wallyworldthat's all that happens with the new stuff too07:05
wallyworldit's on;y done once07:06
wallyworldno need to edit env.yaml with juju init07:06
wallyworldso long as your env variables contain creds07:06
rogpeppewallyworld: so you don't create a new .environments/xxx file every time an env is bootstrapped?07:06
wallyworldnope07:06
wallyworldjust the first time07:06
wallyworldfor a given environment07:06
rogpeppewallyworld: hmm, interesting. i'm not sure that's right actually, but i'll reserve judgement07:07
wallyworldso new env.yaml + local = old env yaml07:07
wallyworldso same info, just now in 2 places07:07
wallyworldenv.yaml is the user facing bit07:07
wallyworldwe want to make that as simple as possib;e07:07
wallyworldusers don't need to edit admin secret or control bucket07:08
wallyworldthat's internal juju magic07:08
wallyworldthat shouldn't be exposed07:08
davecheneywallyworld: oh, so is this CL just hiding those two config options and setting them automatically ?07:09
davecheneyyou're not actually deleteing hte concept of a control bucket ?07:09
wallyworldyep07:09
wallyworldnope :-)07:09
rogpeppewallyworld: the difficulty is that now we're assuming that the control bucket we automatically generate (out of the user's control) is going to be ok to use for all time07:09
davecheneyright, objection withdrawn, i completely misunderstood what you were proposing07:09
davecheney+1, carry on07:09
wallyworld:-)07:09
wallyworldrogpeppe: i gotta take the dog for a walk, happy to discuss later07:10
rogpeppewallyworld: enjoy!07:10
=== axw_ is now known as axw
mgzsomeone remind me to reboot five mins before the meeting please :)07:14
axwwallyworld: I don't understand all the implications, but I was confused by those things in environments.yaml when I came across them. Wasn't sure what, if anything, I was meant to do with them.07:14
* bigjools reads scrollback and thinks that davecheney thinks I'm an ogre07:29
rogpeppebigjools: you're not?07:29
rogpeppebigjools: :-)07:29
bigjoolsI am simply impatient with fuckwittery :)07:30
rogpeppebigjools: makes you scary to all us fuckwits :-)07:31
bigjoolsha07:31
bigjoolsit's probably the meds I am taking, they make me do crazy things07:31
rogpeppebigjools: i am interested in your thoughts on this direction BTW07:31
bigjoolscan you summarise?  I didn't read scrollback in detail07:32
TheMuemorning07:32
rogpeppebigjools: basically, we're moving towards a model where bootstrapping an environment yields a nugget of information that's later used to connect to that environment07:32
davecheneybigjools: i was recalling your conversation when you found out how much environment specific state we stored on the client07:32
rogpeppebigjools: that will currently be stored in local disk, but later can be stored in the cloud07:33
bigjoolsah right07:33
davecheneyTOO THE CLOUD!07:33
bigjoolsmy thoughts are that this should be as HA as anything else07:33
davecheneyhttps://twitter.com/riskybusiness/status/36245676252112076807:33
rogpeppebigjools: this makes it possible to elimininate currently manually specified attributes such as control-bucket, and possibly admin-secret and others07:33
bigjoolsI know that film...07:33
bigjoolsrogpeppe: +1 to config elimination07:34
davecheneyrogpeppe: it sounds like you and wallyworld are working at cross purposes07:34
davecheneywallyworld: is just making them take sensible defaults07:34
davecheneyand you are trying to move them07:34
rogpeppebigjools: obviously we can't eliminate config *entirely* because we need cloud credentials07:35
rogpeppedavecheney: i don't *think* so07:35
bigjoolswell obviously, but there's some stuff that's always been unnecessary07:35
rogpeppedavecheney: there's no sensible default for control-bucket, because of s3's global name space07:36
davecheneyrogpeppe: a guid is a sensible default07:36
rogpeppedavecheney: sure, but then you need to store that guid somewhere07:36
davecheneyrogpeppe: hence why i say that you and wallyworld are working at cross purposes07:36
rogpeppedavecheney: you may well be right07:37
rogpeppedavecheney: i'm coming from my understanding of fwereade and big mark's discussions07:37
davecheneyi read that document07:37
rogpeppedavecheney: which may well be critically flawed07:37
davecheneyit appears unrelated07:37
bigjoolsdavecheney: btw I'll let you know tomorrow about azure improvements07:38
rogpeppedavecheney: search for "# write local state as follows:" in the document07:38
rogpeppedavecheney: that's the related piece07:39
rogpeppewallyworld: it looks to me from https://codereview.appspot.com/12232043/diff/1/cmd/juju/bootstrap.go that the local state *is* written every time we call Bootstrap07:49
davecheneynatefinch: it's dangerous to go alone, take this https://plus.google.com/hangouts/_/calendar/bWFyay5yYW1tLWNocmlzdGVuc2VuQGNhbm9uaWNhbC5jb20.mut2dk4mvoj39eq8jqni20ukoc?authuser=107:53
axwmgz: 5 mins (or so)07:54
natefinchdavecheney: thanks07:55
mgzaxw: ta!07:56
rogpeppefwereade: meeting?08:01
dimiternfwereade: meeting?08:02
dimiternwallyworld: ^^08:02
thumper-afkmramm: I'm counting on you cancelling the managers meeting in 2.5 hours :)08:28
=== thumper-afk is now known as thumper
thumpermramm: just saw the notification \o/08:29
mrammthumper: cool08:30
mrammsee you in a couple of days ;)08:30
thumpermramm: yep08:31
thumpertravel safe08:31
natefinchok, back to bed for me.08:36
axwnight08:36
rogpeppefwereade, wallyworld: lost you08:36
wallyworld___rogpeppe: dimitern: stupid network died again, will talk to you guys after dinner08:48
rogpeppewallyworld___: ok08:48
rogpeppe([a-z]+:)?[0-9]+(/[a-z]+/[0-9]+)*08:52
mgzenlightening08:53
rogpeppemgz: :-)08:53
mgzdoesn't match08:53
rogpeppelxc:0/kvm/1208:54
fwereaderogpeppe, lxc:0/kvm/12 is meaningless, I think08:54
fwereadeah I see08:54
rogpeppefwereade: orly?08:54
fwereaderogpeppe, yeah, ignore me08:55
fwereaderogpeppe, wallyworld___, dimitern: my internets seem to be maybe functional again08:55
fwereaderogpeppe, wallyworld___, dimitern: so I'm back in the team meeting hangout if I'm wanted08:56
rogpeppefwereade: i'm suggesting that we should have something in the names package that understands that syntax, and knows at least how to split off the new container part08:56
fwereaderogpeppe, still don't really think it's about names08:56
axwrogpeppe: are you okay with my response to your destroy-environment comments? okay to land?08:57
wallyworld___rogpeppe: dimitern: try again?08:59
dimiternwallyworld___: i filed bug 1207230 for it09:06
_mup_Bug #1207230: cmd/juju/addmachine.go might fail with unsupported container <juju-core:Confirmed> <https://launchpad.net/bugs/1207230>09:06
dimiternit's not urgent, i'll take care of it today or tomorrow09:07
wallyworld___dimitern: there error is that is not rejecting a machine id as an arg with a friendly message09:07
dimiternwallyworld___: oh?09:07
dimiternwallyworld___: isn't it supposed to accept both type:machine and machine?09:08
wallyworld___the arg has to be either an container type (lxc) or a container with machine (lxc:1)09:08
wallyworld___no09:08
wallyworld___remember it is adding a machine09:08
dimiternexactly, that's what i was saying09:08
wallyworld___add-machine machine-id makes no sense09:08
dimiternaaa09:08
dimiternok09:08
dimiternso it should be "type:machine" or "type" only09:09
wallyworld___the error is the syntax check above the split is broken09:09
wallyworld___yes09:09
dimiternyep, ok will amend the bug09:09
wallyworld___thanks, sorry that i was initially unclear09:09
wallyworld___i had to cast my mind back09:09
dimiternno worries, thanks for clarifying09:11
* fwereade back much later10:22
dimiternrogpeppe, TheMue: https://codereview.appspot.com/12198044 - StringsWorker10:23
axwgood night10:26
TheMuedimitern: you've got a review10:35
dimiternTheMue: cheers10:35
dimiternrogpeppe: ping10:36
rogpeppedimitern: pong10:36
dimiternrogpeppe: can you take a look at https://codereview.appspot.com/1219804410:36
rogpeppedimitern: will do10:36
dimiternrogpeppe: thanks10:37
mgzrogpeppe: after that, can you look at the branches I've put up and tell me where I'm going wrong?10:46
rogpeppemgz: i'll have a look10:46
mgzthanks10:46
=== ChanServ changed the topic of #juju-dev to: https://juju.ubuntu.com | On-call reviewer: - | Bugs: 5 Critical, 81 High - https://bugs.launchpad.net/juju-core/
rogpeppedimitern: reviewed11:18
rogpeppemgz: which branch should i look at first?11:19
natefinchI feel like I was just here...11:22
dimiternrogpeppe: thanks!11:23
dimiternrogpeppe: no Stop() ?11:24
rogpeppedimitern: indeed.11:24
dimiternrogpeppe: i don't get it11:24
rogpeppedimitern: not necessary11:24
dimiternrogpeppe: expand please11:24
rogpeppedimitern: worker.Stop(typeWithKillAndWaitOnly) == w.Stop()11:25
rogpeppedimitern: oops, didn't mean to send that11:25
rogpeppedimitern: basically, nothing needs Stop - it's entirely implementable with Kill and Wait11:25
rogpeppedimitern: and the only thing we need workers for is to pass to worker.Runner11:25
dimiternrogpeppe: but there are tests about stopping it cleanly11:25
rogpeppedimitern: which does not require a Stop method11:25
rogpeppedimitern: well then they should check that worker.Stop(w) stops it cleanly11:26
dimiternrogpeppe: wait, so there is a global Stop method in worker?11:26
rogpeppedimitern: function, yes11:26
dimiterns/method/function/11:26
dimiternI see11:26
dimiternrogpeppe: ok then11:27
TheMuestandup, lunch is waiting ;)11:33
TheMuedimitern, rogpeppe: ^^^11:33
natefinchor breakfast, for some of us ;)11:33
wallyworld_or more wine :-)11:34
natefinchrogpeppe: let me know when you'd like to do the code walkthrough, whenever is good for you is fine with me.11:49
rogpeppenatefinch: now's good if you like11:49
natefinchSure11:49
rogpeppenatefinch: shall we reuse the standup hangout?11:49
natefinchrogpeppe: yep11:50
* TheMue => lunchtime11:53
ahasenackhm, is something going on with the amazon tools bucket and juju?12:07
ahasenack2013-08-01 12:07:09 ERROR juju supercommand.go:254 command failed: Get https://juju-dist.s3.amazonaws.com/tools/juju-1.11.4-precise-amd64.tgz: EOF12:07
ahasenackerror: Get https://juju-dist.s3.amazonaws.com/tools/juju-1.11.4-precise-amd64.tgz: EOF12:07
ahasenackwget works on that url12:07
* ahasenack freshens trunk12:10
rvbaahasenack: ohoh!  That's something thumper saw with the MAAS provider as well… I think it's worth filing a bug.12:12
ahasenackrvba: ok, let me just see if a recent trunk has it too. Mine is from yesterday12:14
ahasenackrvba: do you know if there is some rate limiting being applied to that bucket? I was trying sync-tools a few times before, testing --public (filed a bug), and now without --public and it started happening12:15
rvbaahasenack: no idea, maybe mgz/jam will know…12:16
bigjoolsthis is the potential Go bug12:18
rvbabigjools: yes :)12:18
rvbaThat's him in person :)12:18
ahasenackrvba: it's working now. Either it was the delay (I waited until a new copy of trunk was downloaded and build), or the new code12:23
ahasenackI'm on Go 1.1.112:23
ahasenackthe bug I filed before about sync-tools and --public is https://bugs.launchpad.net/juju-core/+bug/120729412:24
rvbaahasenack: I think it was just a genuine but transient problem… maybe rooted in Go itself.12:24
_mup_Bug #1207294: sync-tools fails with --public <juju-core:New> <https://launchpad.net/bugs/1207294>12:24
ahasenackI'm working around that bug now by making my control bucket temporarily named juju-dist ;)12:24
ahasenackI have a question, when generate-image is run and outputs this:12:42
ahasenack$ juju-metadata generate-image -i 65a1e7ba-eb56-48e6-9b4e-8f7c0c05e779  -s precise -r serverstack12:42
ahasenackBoilerplate image metadata files "index.json, imagemetadata.json" have been written to /home/andreas/.juju.12:42
ahasenackCopy the files to the path "streams/v1" in your cloud's public bucket.12:42
ahasenackthat path, "streams/v1"12:42
ahasenackdoes that mean a bucket called streams?12:42
ahasenackor is that inside the juju-dist bucket? Or your control bucket?12:42
ahasenacksince the public bucket url doesn't have a bucket component12:45
mgzrogpeppe: sorry, missed your question earlier. one branch depends on t'other, but they're pretty seperate. the machine one is the first.12:46
marcoceppiHas anyone gotten this error before?12:49
marcoceppierror: cannot get latest charm revision: charm not found in "/home/marco/Projects/charms": local:precise/relation-sentry12:49
rogpeppemgz: ta12:49
marcoceppiHowever, ~/Projects/charms/precise/relation-sentry does indeed exist12:50
dimiternrogpeppe: updated https://codereview.appspot.com/1219804412:55
dimiternoops, missed one typo12:56
dimiternand one extra return, will repropose again after running tests12:58
ahasenackmarcoceppi: hm, I might have, but I don't remember when or how now12:58
marcoceppiahasenack: bleh, I'm really at a loss as to why it's freaking out. There are 5 charms in this local repo: wp, mysql, two custom subs, and this one standalone, and juju just does not like this charm12:59
ahasenackmarcoceppi: I would check if that path is bzr branch, has or not a revision file, and if it's the same charm ou actually deployed, if you have deployed one already13:00
ahasenackmarcoceppi: could it be that you have two or more metadata.yaml files with the same charm name inside? The directory of the charm dosn't matter13:00
marcoceppiahasenack: checked that and it's not the case. These three charms are being auto-generated so I'm really just trying to focus on what I did wrong13:01
marcoceppiIt has a .bzr dir and has revision information, I added a revision file to the charm (the other two that dpeloy don't have it and worked OK), metadata.yaml are all unique wrt names13:02
marcoceppicharm proof only complains about things like copyright file, etc13:02
ahasenackmarcoceppi: -v?13:03
marcoceppiahasenack: OH13:03
marcoceppithis is a problem13:03
ahasenackdo tell13:03
marcoceppifirst of all, feel really silly for not using -v, total shame on me over here13:04
marcoceppi2013-08-01 13:03:37 WARNING juju repo.go:341 charm: failed to load charm at "/home/marco/Projects/charms/precise/relation-sentry": charm "relation-sentry" using a duplicated relation name: "mysql_db-wordpress_db"13:04
marcoceppiI have a provide and require using the same relation name, didn't realize that was a no-no13:04
marcoceppiThis makes things a little more complicated, but I can work around it. ahasenack thanks!13:05
ahasenackmarcoceppi: still, totally incorrect error message before13:06
dimiternrogpeppe: updated https://codereview.appspot.com/12198044/ now with all suggestions; sorry for the spam13:06
ahasenackmarcoceppi: worth a papercut bug13:06
marcoceppiahasenack: yeah, I'll open a bug about the wording for it13:06
marcoceppiahasenack: and charm proof can be updated to catch things like this as well13:06
rogpeppedimitern: np - am giving nate a walkthrough, will be a little while, sorry13:06
ahasenackmarcoceppi: where can I get charm proof?13:06
dimiternrogpeppe: no worries13:06
marcoceppiahasenack: charm-tools project13:06
ahasenackmarcoceppi: got a ppa handy or is it just in a branch?13:07
marcoceppiahasenack: it's in ppa:juju/pkgs13:07
marcoceppito be moved to ppa:juju/<whatever we decide for tools>13:07
ahasenackmarcoceppi: that's the one with pyjuju too, right?13:07
marcoceppiahasenack: correct13:07
marcoceppispeaking of which ahasenack, I'm tempted to bite the bullet make a ppa:juju/tools and dump charm-tools, amulet, deployer, etc to it13:08
ahasenackmarcoceppi: I like that name13:08
marcoceppiI don't think stable is the best name for it since a lot of these are just using build recipies13:08
ahasenackright13:08
* marcoceppi pulls trigger13:08
rogpeppedimitern: reviewed13:31
dimiternrogpeppe: cheers13:34
marcoceppiahasenack: there's a ppa:juju/tools now, if you want to move the builds for juju-deployer/api over to it13:40
ahasenackok13:41
ahasenackmarcoceppi: do I have upload permissions?13:42
marcoceppiahasenack: are you in the ~juju group?13:42
ahasenacklet me check13:42
ahasenackmarcoceppi: I'm not13:43
ahasenackmarcoceppi: let's just let hazmat copy the branches and recipes and use them in ~juju13:43
marcoceppiahasenack: works for me13:43
rogpeppemgz: could you re-propose https://codereview.appspot.com/12218043/ please; i'm getting a chunk mismatch13:49
ahasenack:( I can't get juju to use my custom image13:53
mgzrogpeppe: wha?13:55
rogpeppemgz: it's a not-uncomming rietveld/lbox error (i don't know which one's to blame)13:55
mgz'ing reitveld13:55
rogpeppeuncommon13:55
rogpeppemgz: your TestSetAddresses function isn't testing what you think it is13:57
mgzthat's what I suspect13:57
rogpeppemgz: the state.address type is broken13:57
mgzbut... I'm not sure what the right way of asserting that stuff actually arrives in state is13:57
rogpeppemgz: i suggest marshalling instance.Address directly (but change it so it doesn't embed the network scope)13:58
rogpeppemgz: the usual thing is to call Machine again (or call Refresh)13:58
rogpeppemgz: because otherwise you're not actually reading from mgo13:58
rogpeppemgz: the reason that the address type is currently broken is that the fields are not exported13:59
mgzI may well end up sticking instance.Address straight in, but wanted parallel types for now so the serialisation is seperate from the various populating logic13:59
mgz...gah, I changed that per a review comment13:59
mgzno wonder I was sure this worked previously :)14:00
mgzjust recapitalise then?14:00
rogpeppemgz: just use instance.Address :-)14:00
rogpeppemgz: if it's got some "bson:" struct tags then it should be obvious that it's being serialised14:01
rogpeppemgz: although i do really want some more formal controls on changes to structs that are serialised14:01
rogpepperight, i need lunch14:03
mgzokay, that fails then passes correctly14:05
dimiternrogpeppe, TheMue: next in line https://codereview.appspot.com/12254043 - Deployer and MinUnitsWorker use StringsWorker now14:06
TheMuedimitern: reviewed14:10
dimiternTheMue: thanks14:10
mgzwell, that was easy to make working at least14:21
mattywI was going to take a look at https://bugs.launchpad.net/juju-core/+bug/1020322, but it looks like it's already been done?14:22
_mup_Bug #1020322: Unit not found message is repetitive <bitesize> <papercut> <ui> <juju-core:Triaged> <https://launchpad.net/bugs/1020322>14:22
dimiternmgz: you've got a review14:25
dimiternmgz: also, please live test this14:25
TheMuehmmpf14:26
TheMueset --default would also introduce a behavior change14:27
TheMueempty strings as configuration values are alowed then14:28
TheMuedunno if this leads to compatibility problems14:28
mgzdimitern: I don't understand this comment of yours:14:29
dimiternmgz: and another one14:30
dimiternmgz: yeah?14:30
mgz> Also it's good to check this before that:14:30
mgz> c.Assert(machine.Addresses(), HasLen, 0)14:30
mgzthat will never be the case I think? the issue I had was I got non-zero length even though the addresses never got in the doc14:30
dimiternmgz: I mean check there are no addresses before calling SetAddresses, then check the same once more before calling Refresh, and then check they're set after Refresh14:31
mgzbut with the refresh, it will still be non-zero length, it will just also reload to actually exercise state14:31
dimiternmgz: hmm? i wonder why's that14:31
mgzah, you meant right at the start after making the machine?14:32
dimiternmgz: so there should be a test to check what's the state when you never called SetAddresses on a fresh machine, and they should be an empty slice, i think14:32
mgzokay.14:32
dimiternrogpeppe: got a moment?14:32
dimiternmgz: could you return the favor by reviewing https://codereview.appspot.com/12254043/ ? :)14:37
mgzsure :)14:40
dimiternthanks!14:40
mgzoo, it even looks educational14:41
rogpeppedimitern: just back from lunch, yes i've got a mo14:41
dimiternrogpeppe: about https://codereview.appspot.com/12254043/14:41
mrammhey hey14:46
mrammso we need to get provider specific constraints on the roadmap for the next few weeks14:47
dimiternmramm: like instance-type and such?14:48
rogpeppedimitern: reviewed14:50
dimiternrogpeppe: thanks14:50
dimiternwell, what do you know.. i ran out of stuff to do this week :)14:50
dimiternlooking at bugs currently though14:51
dimiternmramm: is there a plan who's going to work on bugs and who on the remaining api stuff until the end of next week?14:52
=== tasdomas is now known as tasdomas_afk
dimiternrogpeppe: is this card merged now? Upgrader API only worker14:53
rogpeppedimitern: nope14:54
rogpeppedimitern: i'm just testing the 1.10->1.12->current upgrade path now14:54
dimiternrogpeppe: I see14:55
mrammdimitern: I think if you are working on API and can safely continue to do so it makes sense that you do15:03
mrammI don't think there is a "plan" from above15:04
dimiternmramm: ok then15:04
mrammI think you guys can work it all out ;)15:04
dimiternrogpeppe: I think I can start implementing the uniter API now, with the UA having connection to the API already, right?15:08
rogpeppedimitern: well, it will have a connection to the API when my CL lands15:08
rogpeppedimitern: which only has one review so far (https://codereview.appspot.com/12183043/ hint hint anyone :-])15:09
dimiternrogpeppe: yeah, but it'll happen soon anyway, and I won't be ready with it for a few days perhaps15:09
dimiternmgz: perhaps? ^^15:10
dimiternmgz: you hate responding to comments on rietveld, right? :)15:12
mgzsomewhat :)15:26
natefinchrogpeppe: (or anyone else) got a second to help the newbie?  I made a small change that requires changes to several tests, so I want to make sure it's the right thing to do before I go changing 8 different tests15:27
dimiternnatefinch: sure, bring it on :)15:27
natefinchLooking at this bug: https://bugs.launchpad.net/juju-core/+bug/115493815:27
_mup_Bug #1154938: juju status should give the same help as juju bootstrap <bitesize> <cmdline> <ui> <juju-core:Triaged by natefinch> <https://launchpad.net/bugs/1154938>15:27
natefinchIt says juju status should give the same message, but really ,wouldn't it be an appropriate message for any command that needs the default environment file?15:28
dimiternnatefinch: ok, but where's your CL?15:28
mgzhm, the state package really doesn't use loggo anywhere?15:29
natefinchI'll check it in, it just breaks some tests as-is... wasn't sure if I should check in and then ask15:29
dimiternmgz: not yet15:29
dimiternnatefinch: if it breaks tests, then definitely don't :) the bot won't let you anyway15:29
natefinchdimitern: ok, good.  So... the change is just to have environs.ReadEnvirons to return a specific error if it can't read the default environments.yaml file... and then in cmd/Main() check for the file and output that error message to the context's stderr  (just like it did for bootstrap)15:31
dimiternnatefinch: can I see a link to the branch please?15:32
natefinchlike I said, the changes are only local right now, they're not commited.15:34
natefinchMaybe I'm not using the right terminology for bzr... I'm still new to it.15:34
dimiternnatefinch: can you push it on LP so I can have a look? you can do lbox propose -wip15:34
natefinchdimitern: thanks... new to LP too :)15:34
mgznatefinch: bzr diff|pastebinit15:35
dimiternnatefinch: that way it's pushed on LP, and a CL on rietveld is created, but no mails are sent15:35
dimiternnatefinch: ah, sorry15:35
mgzfor the even more lo-fi method15:35
dimiternnatefinch: do you have lbox working?15:35
natefinchit's installed, haven't run it, so....15:35
dimiternthen, in your work dir with the branch, bzr commit it, and then run lbox propose -wip15:36
dimitern-wip is for work-in-progress = don't send review emails, just push it to codereview.appspot.com (rietveld)15:37
natefinchdimitern: rietveld appears to be asking for google login credentials? How does that work with SSO?15:42
dimiternnatefinch: do you want to have a g+ chat, so I can help you as you go?15:42
natefinchdimitern: yeah15:43
dimiternnatefinch: just a sec, i'll start a hangout15:43
dimiternman they changed g+ *yet again*! how do I start a hangout now?15:45
natefinchhaha15:45
natefinchupper right15:46
dimiterni don't want to invite, i just want the link15:47
dimiternah.. it's hidden down there https://plus.google.com/hangouts/_/375c6630051efe7089a102bc829f8afd25fb80d9?hl=en15:47
dimiternnatefinch: ^^15:47
rogpeppedimitern: just tested the upgrade path from 1.10 -> 1.12 -> api-based upgrader branch and it all seems to work15:55
dimiternrogpeppe: woohoo!15:55
rogpeppedimitern: :-)15:56
rogpeppedimitern: unfortunately fwereade not-LGTM'd a prereq branch so i can't get anything in until he's available again15:57
rogpeppeplease someone: another review of https://codereview.appspot.com/12183043/ would be much appreciated15:57
TheMuerogpeppe: looking15:59
rogpeppeTheMue: thanks15:59
TheMuerogpeppe: done16:06
rogpeppeTheMue: thanks!16:06
* TheMue still thinks about setting empty strings in config16:06
TheMuesetting to default now works, but the empty string leads to changes deep in the charm config16:07
rogpeppeTheMue: have you implemented juju set --default now?16:12
TheMuerogpeppe: set --default works, but set option= to set it to empty string not16:14
TheMuerogpeppe: currently discussing is on #juju16:14
rogpeppeTheMue: ah16:14
mgzdimitern: where's a simple non-horrible example of table tests?16:15
TheMuerogpeppe: in that case I have to change config in .../charm16:15
TheMuerogpeppe: that could break charms16:16
* rogpeppe looks for a particularly nice table-based test16:16
mgzta rog16:17
TheMuemgz: cmd/juju/config_test.go16:17
mgzthanks!16:18
TheMuemgz: an about string/info string, input args, a possible error and the expected results16:18
rogpeppemgz: charm/url_test.go has a few reasonable simple examples16:19
rogpeppemgz: although actually Commentf stuff is a bit antiquated now16:19
rogpeppes/Comment/the Comment/16:19
rogpeppemgz: version/version_test.go is another nice example16:20
rogpeppemgz: i think we'd probably add some more identifying information to the Logf statement now16:21
rogpeppehmm, oops: http://paste.ubuntu.com/5936989/16:44
* rogpeppe needs to go16:49
rogpeppeg'night all16:49
=== natefinch is now known as natefinch-lunch
* TheMue has to go too17:01
TheMuecu tomorrow17:01
=== natefinch-lunch is now known as natefinch
thumpermorning20:39
thumperI'm going to be in and out today as I organise stuff for travel20:39
sidneihey thumper! i'd love some comment on the cloud-init message. mramm suggested talking to fwereade but i guess he's en-route too20:47
=== BradCrittenden is now known as bac
davecheneyarosales: ping23:40
=== gary_poster is now known as gary_poster|away
=== gary_poster|away is now known as gary_poster

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