[00:17] <niemeyer> hazmat: Yo!
[01:08] <hazmat> niemeyer, pong
[01:24] <_mup_> Bug #826498 was filed: virtualbox machine provider for osx local dev <Ensemble:New> < https://launchpad.net/bugs/826498 >
[13:46] <hazmat> g'morning
[13:46] <hazmat> i guess i'm on point
[14:37] <niemeyer> Hello everyone!
[14:49] <jimbaker> niemeyer, hi
[14:49] <niemeyer> jimbaker: Hey man
[14:55]  * kim0 pushing an ensemble mongodb cluster screencast in an hour
[14:57] <niemeyer> kim0: Where?
[14:57] <kim0> I'm still uploading :)
[14:57] <kim0> will hit the usual places 
[14:58] <kim0> figuring out if replication was actually working, was way much harder than deploying with ensemble hehe :)
[15:10] <niemeyer> kim0: Ah, cool
[15:26] <niemeyer> robbiew: ping
[15:28] <robbiew> niemeyer: pong
[15:28] <niemeyer> robbiew: Hey there
[15:29] <niemeyer> robbiew: Had a good trip back home? ;-)
[15:29] <niemeyer> robbiew: Quick pvt question
[18:41] <hazmat> niemeyer, it looks like the kanban is stale again
[18:41] <hazmat> niemeyer, also i've been brainstorming on our workflow and tooling, i think we might be able to use a bzr plugin to some good effect to solve some of our workflow issues
[18:43] <niemeyer> hazmat: Use http://people.canonical.com/~niemeyer/dublin.html, I didn't stop it given the number of recent issues we've had
[18:43] <niemeyer> We should really put Eureka in place, though
[18:43] <fwereade> hey all
[18:43] <niemeyer> fwereade!
[18:43] <hazmat> niemeyer, sounds good re eureka
[18:44] <niemeyer> fwereade: Made it home safely?
[18:44] <fwereade> niemeyer: yeah, all good :)
[18:44] <niemeyer> Great to hear
[18:44] <fwereade> niemeyer: great to be ;)
[18:44] <hazmat> fwereade, great.. that travel sounded hard
[18:44] <fwereade> hazmat: well, worse things happen at sea ;)
[18:46] <fwereade> niemeyer: while travelling I got lp:~fwereade/ensemble/hide-instances basically reverted
[18:46] <fwereade> I need to do some live verification now I have a connection again
[18:47] <fwereade> but if it works -- and the UI is no worse than before -- will that be ok to merge?
[18:47] <niemeyer> fwereade: Ok.. please take a careful time with this branch and reevaluate whether the issues there are all fixed
[18:47] <niemeyer> fwereade: As Kapil pointed out, the UI is worse than before
[18:47] <niemeyer> fwereade: "Machine not found" after a bootstrap is senseless to a user
[18:49] <fwereade> niemeyer: I think that's been dealt with, but I'll reverify everything
[18:49] <niemeyer> fwereade: Sounds good
[18:49] <fwereade> niemeyer: and mark it "needs review" again when I'm done
[18:50] <niemeyer> fwereade: Please try it in a few real interactions
[18:50] <niemeyer> fwereade: Try e.g. ensemble status several times right after ensemble bootstrap
[18:50] <fwereade> niemeyer: I have been, it was a surprising real interaction that led me to back stuff out
[18:51] <niemeyer> fwereade: That's cool then.. I'm all for less code as you know :)
[18:51] <fwereade> 2011-08-15 20:51:29,795 ERROR Ensemble environment is not accessible: machine i-d1e8bdb0 has no address assigned yet
[18:52] <fwereade> tolerable?
[18:52] <fwereade> human-readable intro, machine specification for those who need to know
[18:53] <fwereade> (that's the only change; I'm pretty sure we can do better, but that'll come in another branch when I generalise it to cobbler)
[19:04] <niemeyer> fwereade: That's beautiful IMO
[19:05] <fwereade> niemeyer: cool -- I'll check everything else, but that was the specfic really bad bit (it certainly beats "NoneType has no attribute 'groups'") ;)
[19:06] <niemeyer> fwereade: LOL.. I can agree with that
[19:36] <fwereade>  niemeyer: ok, it's back on "needs review", but I can't seems to ask for another from you... it thinks you've already approved it
[19:36] <niemeyer> fwereade: Sounds great, thanks!
[19:36] <fwereade> niemeyer: a pleasure :)
[19:44] <fwereade> right, that's definitely it for me today
[19:44] <fwereade> nn all :)
[20:01] <niemeyer> jimbaker: ping
[20:35] <niemeyer> jimbaker: ping?
[20:48] <SpamapS> adam_g: reading your openstack deploy stuff with glee.. looks pretty cool
[20:55] <niemeyer> SpamapS: So, I've heard we are getting ftests automated?  Do you know something about that? :-)
[20:58] <adam_g> SpamapS: cool, thanks
[21:01] <adam_g> niemeyer: if by ftests you mean formula tests, james came up with a cool way of testing and aggregating results back to jenkins via a "tester" formula.
[21:05] <niemeyer> adam_g: It was actually about "functional tests"
[21:05] <niemeyer> adam_g: We have some interesting logic in the tree already that runs a real deployment against EC2 and performs checks against it
[21:05] <niemeyer> adam_g: It's pretty ineffective at the moment, though, because we don't really run the tests
[21:06] <niemeyer> adam_g: It'd be awesome to have these tests being run on every commit to trunk, to ensure ensemble works for real at all times
[21:06] <niemeyer> adam_g: and then enhance those tests
[21:06] <adam_g> niemeyer: ah, gotcha. 
[21:06] <niemeyer> Also makes a lot of sense in that final runway towards 11.10
[21:24] <jimbaker> niemeyer, hi
[21:25] <niemeyer> jimbaker: Hi.. we have to talk about tasks for the next couple of months, but I can't do that right now unfortunately.  Let's talk tomorrow.
[21:25] <jimbaker> niemeyer, sounds good
[21:27] <niemeyer> I'll step out for now..
[22:56] <_mup_> ensemble/pythonpath-fix-bug-816264 r305 committed by kapil.thangavelu@canonical.com
[22:56] <_mup_> update injection of ENSEMBLE_PYTHON_PATH per review
[23:01] <_mup_> ensemble/trunk r312 committed by kapil.thangavelu@canonical.com
[23:01] <_mup_> merge python-path-fix-bug-816264 [r=niemeyer,jimbaker][f=816264]
[23:01] <_mup_> Avoid setting PYTHONPATH when executing hooks, as it can have
[23:01] <_mup_> side-effects on hook execution. Per the bug report mod-wsgi pkg
[23:01] <_mup_> install was a reproducable error on natty). 
[23:01] <_mup_> Instead utilize ENSEMBLE_PYTHONPATH environment variable and some shim
[23:01] <_mup_> code in each hook CLI-API to support development scenarios where the
[23:01] <_mup_> PYTHONPATH is needed for the CLI-API.
[23:15] <hazmat> that's odd using --fixes=lp:bug_num when committing a branch merge adds a link to the bug against trunk
[23:16] <hazmat> i thought it was supposed to just close the bug..
[23:18] <hazmat> hmm. ic, i was using it incorrectly.. it has to be used on the branch to be merged, and then it creates the bug-branch link