/srv/irclogs.ubuntu.com/2012/09/14/#juju-dev.txt

fwereademorning davecheney06:21
davecheneyfwereade: hello06:22
davecheneythank you for your reviews06:22
* davecheney is still pondering the theological implication of juju set KEY=""06:22
fwereadedavecheney, a pleasure, sorry they've been a little vague06:22
fwereadedavecheney, yeah, that is definitely a pain point...06:22
fwereadedavecheney, but, have you been reading the "incompatible charm upgrades" thread?06:23
davecheneyfwereade: not closely06:23
davecheneyreading the python juju set06:24
davecheneyit's a lot more complicated than KEY=VALUE06:24
fwereadedavecheney, I *think* what that should always mean, based on clint's point re fallback-to-defaults, is "clear out the setting, use the service default instead"06:24
davecheneyit's actually "key: value" _when_ the charm is a yaml charm06:24
davecheneyand other options when the charm is something else06:24
fwereadedavecheney, yeah, this is something I had not fully appreciated the intricacies of myself06:24
fwereadedavecheney, sorry, what do you mean by "yaml charm"?06:25
davecheney    charm_format = (yield charm.get_metadata()).format06:25
davecheney    formatter = get_charm_formatter(charm_format)06:25
davecheney        options = formatter.parse_keyvalue_pairs(service_options)06:25
fwereadedavecheney, oh, hell06:25
davecheney(insert dramatic chipmonk)06:25
fwereadehaha06:25
davecheneyhowever get_charm_formatter does allow for something called "PythonFormat"06:26
fwereadedavecheney, I'm reluctant to claim possession of truth here, but please talk to niemeyer about this... I'm *sure* I saw him saying something to jimbaker yesterday that strongly implied that was not the correct approach on the client side06:26
davecheneyT06:26
davecheneyi'd suggest it's pretty crack for the user of a charm to have to specify the config data in the native charm format06:27
davecheneygiven we don't make it obvious what that format is06:27
fwereadedavecheney, I *think* (again) that there was a recent thread which laid this out... or possibly just made reference to an earlier thread which did06:29
davecheneyill search the archive06:29
rogdavecheney, fwereade: morning!06:58
fwereaderog, heyhey07:00
fwereaderog, PATH change is merged07:01
fwereaderog, is it just the security groups now?07:01
rogfwereade: i've just seen that. will pull and see what happens in my branch...07:01
fwereaderog, (that we currently know of ;))07:01
rogfwereade: no, they're in07:01
rogfwereade: it should just work now07:02
fwereaderog, ah, cool, I didn't try because https://code.launchpad.net/juju-core/+activereviews still shows it aproved but unmerged07:02
rogfwereade: although of course you won't be able to *tell* that it's working - the uniter-upgrade branch will do that07:02
davecheneyhello lads07:02
fwereaderog, oh? what does that do07:02
fwereaderog, well, obviously it upgrades the uniter07:03
rogfwereade: good point - i'd moved it in to my "submitted" list, but it seems i never did07:03
fwereaderog, but... can't we tell anyway?07:03
rogfwereade: i suppose so, from the unit status07:03
fwereaderog, via status07:03
fwereaderog, yeah07:03
rogfwereade: will submit the security groups stuff pronto07:04
fwereaderog, cool07:04
rogfwereade: ah, no, it *is* submitted, but i had to remake the merge proposal because the prereq changed07:05
rogfwereade: i'll add a comment to the original07:05
fwereaderog, ah cool07:09
fwereaderog, dammit, it's the addresses again08:13
rogfwereade: ah, sorry, that fix is in the unit-upgrader branch08:13
fwereaderog, ahh that's why :)08:14
rogfwereade: i should push it out as a trivial08:14
fwereaderog, do it do it :)08:14
rogfwereade: although it's not *entirely* trivial - there's the arguable case over "latest" vs some fixed version number08:14
rogfwereade: which others might wish to weigh in on08:15
rogdavecheney: ping08:15
rogfwereade: i have a feeling it was me that pushed for the fixed version in the first place. oh i am fickle.08:15
rogfwereade: anyway, if you want it to work, just change "1.0" to "latest"08:16
fwereaderog, I *kinda* think it's probably best to go with any specific version that has the metadata we need08:22
fwereaderog, I do in general trust amazon not to screw it up08:22
fwereaderog, but yu never know08:22
rogfwereade: ok, i'll do that then.08:22
fwereaderog, it's just one extra thing that *might* go wrong08:22
rogfwereade: perhaps a relatively recent version, so that we have access to other stuff as well if we want08:22
fwereaderog, yeah, the current target of latest would be fine with me08:23
rogfwereade: BTW what state are the relation hooks in?08:23
fwereaderog, basically, they're not08:23
fwereaderog, because so many of the details depend on lifecycles not just existence08:24
rogfwereade: ahhh08:24
fwereaderog, I have a branch that I'm 90 sure will work with only minor tweaks once the substrate is available08:24
fwereaderog, but it is 3 weeks old now08:24
rogsubstrate is such a good word08:24
fwereaderog, and I'm a bit worried about when I'll be able to make actual *progress* on it08:24
fwereaderog, fingers crossed for lisbon08:25
rogfwereade: yeah ikwym08:25
rogfwereade: what i tend to do is keep things roughly up to date, so i don't have an almighty job when i come to merge it later08:25
rogfwereade: but that can have its own problems of course08:26
fwereaderog, I gave up on that a long time ago, I'm just planning to recreate everything using it for inspiration08:26
rogfwereade: lol08:26
fwereaderog, ffs, git is not installed by default :)08:38
rogfwereade: nbd. we have other dependencies too.08:38
fwereaderog, indeed08:39
fwereaderog, just another irritating step ;)08:39
rogfwereade: and some time later, we will should provide images that don't take 5 minutes to get all their stuff before becoming usable08:39
rogs/will //08:39
fwereaderog, yeah, definitely08:40
fwereaderog, can I get a trivial LGTM on https://codereview.appspot.com/6495129 before I pop out for coffee please?09:05
rogfwereade: assuming it works, LGTM09:06
fwereaderog, it appeared to :)09:06
rogfwereade: cool09:06
rogfwereade: did you see the charm actually running some commands then?09:07
fwereade-on-jujuso, the *only* hack this is using (compared to trunk) is the latest metadata10:36
fwereade-on-jujuhttp://ec2-174-129-106-129.compute-1.amazonaws.com:3000/10:37
fwereade-on-jujurog, *surely* we can make that a trivial and get trunk actually *working* ..?10:37
rogfwereade-on-juju: so... you're actually connecting from a charm?10:38
rogfwereade-on-juju: YAYAYYAYAYAYAAYYA!!!!10:39
rogfwereade-on-juju: ok, i'll frikkin' do it10:39
fwereade-on-jujurog, oh yes I am :)10:40
fwereade-on-jujuoops, bugger, need cash for cleaner, brb10:40
rogfwereade-on-juju: while you've got an instance up, could you do a quick curl http://169.254.169.254/ and paste me the results please?10:41
rogfwereade-on-juju: that is - do that on an ssh session in your instance10:41
rogfwereade-on-juju: actually, scratch that10:42
rogfwereade-on-juju: https://codereview.appspot.com/649812810:46
rogfwereade-on-juju: hmm, pity your server doesn't seem to be actually connecting to IRC for me10:53
rogfwereade: oh yes, that CL also renames a directory, which the codereview page doesn't show.10:54
fwereade-on-jujurog, sorry, back; looking10:56
fwereade-on-jujurog, LGTM10:57
fwereade-on-jujurog, but... what's not working for you?10:57
fwereade-on-jujurog, you *should* just be able to do new connection to chat.freenode.net and pick a name10:58
rogfwereade-on-juju: i tried, but it hung. i did use "irc.freenode.net" though10:58
fwereaderog, tbh subway *does* apear to be a touch flaky, it misses messages occasionally10:58
fwereaderog, but I *think* we can blame the service rather than juju for that ;)10:59
rogfwereade: i tried it in two windows, different server names, etc10:59
rogfwereade: but yeah, i see the page!10:59
rogfwereade: i just wanted to join you as rog-on-juju :-)10:59
fwereade-on-jujurog, yeah, indeed10:59
fwereade-on-jujuit's lonely up here ;p10:59
rogfwereade-on-juju: ok, so trunk should now be working!10:59
fwereade-on-jujurog, ok, I'm shutting this down and trying it out :)11:00
rogfwereade: "you were disconnected from the server" :-)11:00
fwereaderog, that works, anyway ;p11:01
rogfwereade: yeah, i could navigate other pages too11:01
rogfwereade: just not get through to irc11:01
fwereaderog, sorry, but I'm getting 404s from 2012-06-01...11:37
rogfuck11:37
rogfwereade: that's the version they mentioned on the web page11:37
rogfwereade: i just assumed...11:37
rogfwereade: bloody amz11:37
rogfwereade: have you got an instance up now?11:38
fwereaderog, bad luck11:38
fwereaderog, yeah, I was just about to poke around and try to figure out what it should be11:38
rogfwereade: ssh to it and do curl http://169.254.169.254/11:38
rogfwereade: that should give you the list of available versions i think11:38
fwereaderog, huh, latest is 2012-01-1211:39
rogfwereade: ok11:39
rogfwereade: i *so nearly* went for a 2011 version!11:39
fwereaderog, haha11:39
fwereaderog, wonder wtf the deal is with versions not existing :/11:39
rogfwereade: only amazon knows11:40
rogfwereade: ok, will change it11:40
fwereaderog, 2012-01-12 verified live btw ;)11:40
rogfwereade: thanks. i didn't want to wait for another live test to complete :-)11:41
rogfwereade: could you verify 2011-01-0111:42
rog?11:42
rogfwereade: i think i'll go for that, as who knows how consistent amz is across regions11:42
fwereaderog, sorry, just killed the env -- but it was advertised11:42
rogfwereade: that gives us everything we want, i think11:43
fwereaderog, sgtm11:43
rogfwereade:  https://codereview.appspot.com/649413611:51
fwereaderog, LGTM11:52
rogfwereade: submitted11:53
fwereaderog, trying it out11:53
fwereade-on-jujuoh yes indeed12:14
rogfwereade-on-juju: fanbloodytastic!12:16
fwereade-on-jujurog, ain't it :D12:16
fwereade-on-jujurog, not one lick of manual intervention12:16
rogfwereade-on-juju: am very glad you got to be the first!12:16
fwereade-on-jujurog, bah, there's more than enough credit to go around :)12:17
fwereade-on-jujurog, http://ec2-23-20-195-110.compute-1.amazonaws.com:3000/ -- maybe subway will be happier this time12:17
rogfwereade-on-juju: you don't have to log in or register first?12:17
fwereaderog, I just picked a name and a server and that ws it12:17
rogfwereade: nah12:20
rogfwereade: tried from my phone too. page serves fine though12:21
fwereaderog, weird12:21
fwereaderog, ah well12:21
=== rog is now known as Guest96454
mrammFor those wondering about sprint plans, Marianna says: "I'm booking the same venue as for the July's sprint"13:01
fwereademramm, cool13:01
mrammsomething went wrong in the notification system, so she got started late13:02
mrammbut is finalizing the details this morning13:02
mrammso we should be all set to go13:02
fwereademramm, not sure if you saw that I just deployed a charm on trunk :)13:02
mrammrock and roll13:02
mrammgreat work everybody!13:02
niemeyerHellos!13:27
fwereadeniemeyer, heyhey13:46
fwereadeniemeyer, with a pair of trivials merged by me and rog this morning, current trunk can deploy subway :)13:47
niemeyerfwereade: Wooooooo14:02
fwereade:D14:02
niemeyerfwereade: Sooooo awesome.. we should have a beer on Sunday :-)14:02
fwereadeniemeyer, SGTM :) when are you getting in?14:02
Guest96454niemeyer: yo!14:04
niemeyerfwereade: Let me check14:05
niemeyerGuest96454: Morning! :-)14:05
=== Guest96454 is now known as rogpeppe
rogpeppehow did that happen?!14:05
rogpeppeguess i was on the last available name14:06
niemeyerfwereade: Just sent another reply on the upgrade thread14:38
fwereadeniemeyer, cool, looking14:38
fwereadeniemeyer, replied14:58
niemeyerfwereade: Cheers14:58
* fwereade acknowledges a good point by niemeyer, and goes off to think for a bit15:16
niemeyerLunch time!16:36
* rogpeppe wishes there was an easy way of splitting a branch in two17:10
rogpeppegah!17:21
niemeyerrogpeppe: git is *slightly* better at that, via rebase17:28
niemeyerrogpeppe: Unfortunately we don't yet have something as complete as git's rebase yet17:29
rogpeppeniemeyer: i'm just gonna copy the files into a branch off trunk and lose the revision history17:29
rogpeppeniemeyer: sucks a bit, but i don't mind much17:29
niemeyerrogpeppe: Well, that's unavoidable unfortunately17:36
niemeyerrogpeppe: Splitting content in half always trashes or modifies history somehow17:36
rogpeppeniemeyer: unless you use darcs apparently17:37
rogpeppeniemeyer: well "alters" i'm sure17:37
niemeyerrogpeppe: I believe this is a theoretical constraint17:37
rogpeppewe have a place to stay!17:45
niemeyerrogpeppe: Yeah, that was tight :-)17:46
rogpeppeniemeyer: not quite as convenient as before17:46
rogpeppeniemeyer: here's the upgrader logic we talked about: https://codereview.appspot.com/6492123/17:52
rogpeppeniemeyer: unfortunately i can't propose the uniter upgrade branch until we decide about UnitWatcher17:54
niemeyerrogpeppe: I don't get the comment about WaitForEnviron17:55
rogpeppeniemeyer: WaitForEnviron absorbs the first event17:55
rogpeppeniemeyer: but we need to see it17:55
niemeyerrogpeppe: Yeah, it absorbs to return the environ17:55
niemeyerrogpeppe: We don't "miss it"17:55
niemeyerrogpeppe: It's handling the event for us17:55
rogpeppeniemeyer: yes, but we need that event in the upgrader loop17:55
rogpeppeniemeyer: unless...17:56
rogpeppeniemeyer: we could just start an independent environ watcher17:56
niemeyerrogpeppe: It just sounds a bit confusing.. the comment says that we can't use it because it does precisely what it should do17:56
niemeyerrogpeppe: The goal is precisely to "initialize the environ when we're first able"17:56
rogpeppeniemeyer: ok. i'll try to think of another way of phrasing the comment17:57
niemeyerrogpeppe: So far I'm arguing mainly about the comment.. I don't understand what's the constraint yet17:57
niemeyerrogpeppe: It says something like "we initialize the environ when we're first able, so we can't use WaitForEnviron" but that's *exactly* what WaitForEnviron does.. not sure if you see what I mena?17:58
niemeyerrogpeppe: It feels like we could just use it, to be honest17:59
niemeyerrogpeppe: Why can't we?17:59
rogpeppeniemeyer: if we use it and the environ config does not change, we won't see any more events on the watcher, so we'll never do an upgrade.18:00
rogpeppeniemeyer: here's a possible updated version of the comment:18:02
rogpeppe// We can't use worker.WaitForEnviron because then we don't18:02
rogpeppe// see the first event from the watcher, which we need18:02
rogpeppe// to see because it has version information in that we18:02
rogpeppe// must see.18:02
rogpeppeniemeyer: slightly better:18:03
rogpeppe// We can't use worker.WaitForEnviron because then we don't18:03
rogpeppe// see the first event from the watcher, which contains version information18:03
rogpeppe// that we must see.18:03
=== cmagina_ is now known as cmagina_away
rogpeppeniemeyer: i need to go, i'm afraid18:05
rogpeppeniemeyer: looking forward to an awesome sprint!18:05
rogpeppeniemeyer: hope your travel goes well18:05
niemeyerrogpeppe: I see, it's still not entirely right, though18:05
rogpeppeniemeyer: oh?18:05
niemeyerrogpeppe: WaitForEnviron does more than simply waiting for first event18:05
niemeyerrogpeppe: We need it to handle the bootstrap behavior18:06
rogpeppeniemeyer: i *think* i do that18:06
niemeyerrogpeppe: Doesn't look like so..18:06
niemeyerrogpeppe: The logic within the switch says18:06
niemeyer139 »       »       »       »       »       // continue on, because the version number is stil18:06
niemeyer     l significant.18:06
niemeyerrogpeppe: We can't move on with an invalid configuration18:06
niemeyerrogpeppe: We talk to the environment mid-way through18:06
rogpeppeniemeyer: what about line 132?18:07
niemeyerrogpeppe: Ah, yeah, you're right18:07
niemeyerrogpeppe: Anyway, we can talk next week.. have fun there18:08
niemeyerrogpeppe: and safe travels18:08
rogpeppeniemeyer: and you too.18:08
niemeyerrogpeppe: Thanks18:08
rogpeppeniemeyer: you too!18:09
=== cmagina_away is now known as cmagina_

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