[00:17] hazmat: Yo! [01:08] niemeyer, pong [01:24] <_mup_> Bug #826498 was filed: virtualbox machine provider for osx local dev < https://launchpad.net/bugs/826498 > [13:46] g'morning [13:46] i guess i'm on point === ricardokirkner is now known as pindonga [14:37] Hello everyone! [14:49] niemeyer, hi [14:49] jimbaker: Hey man [14:55] * kim0 pushing an ensemble mongodb cluster screencast in an hour [14:57] kim0: Where? [14:57] I'm still uploading :) [14:57] will hit the usual places [14:58] figuring out if replication was actually working, was way much harder than deploying with ensemble hehe :) [15:10] kim0: Ah, cool [15:26] robbiew: ping [15:28] niemeyer: pong [15:28] robbiew: Hey there [15:29] robbiew: Had a good trip back home? ;-) [15:29] robbiew: Quick pvt question [18:41] niemeyer, it looks like the kanban is stale again [18:41] 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] 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] We should really put Eureka in place, though [18:43] hey all [18:43] fwereade! [18:43] niemeyer, sounds good re eureka [18:44] fwereade: Made it home safely? [18:44] niemeyer: yeah, all good :) [18:44] Great to hear [18:44] niemeyer: great to be ;) [18:44] fwereade, great.. that travel sounded hard [18:44] hazmat: well, worse things happen at sea ;) [18:46] niemeyer: while travelling I got lp:~fwereade/ensemble/hide-instances basically reverted [18:46] I need to do some live verification now I have a connection again [18:47] but if it works -- and the UI is no worse than before -- will that be ok to merge? [18:47] fwereade: Ok.. please take a careful time with this branch and reevaluate whether the issues there are all fixed [18:47] fwereade: As Kapil pointed out, the UI is worse than before [18:47] fwereade: "Machine not found" after a bootstrap is senseless to a user [18:49] niemeyer: I think that's been dealt with, but I'll reverify everything [18:49] fwereade: Sounds good [18:49] niemeyer: and mark it "needs review" again when I'm done [18:50] fwereade: Please try it in a few real interactions [18:50] fwereade: Try e.g. ensemble status several times right after ensemble bootstrap [18:50] niemeyer: I have been, it was a surprising real interaction that led me to back stuff out [18:51] fwereade: That's cool then.. I'm all for less code as you know :) [18:51] 2011-08-15 20:51:29,795 ERROR Ensemble environment is not accessible: machine i-d1e8bdb0 has no address assigned yet [18:52] tolerable? [18:52] human-readable intro, machine specification for those who need to know [18:53] (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] fwereade: That's beautiful IMO [19:05] 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] fwereade: LOL.. I can agree with that [19:36] 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] fwereade: Sounds great, thanks! [19:36] niemeyer: a pleasure :) [19:44] right, that's definitely it for me today [19:44] nn all :) [20:01] jimbaker: ping [20:35] jimbaker: ping? [20:48] adam_g: reading your openstack deploy stuff with glee.. looks pretty cool [20:55] SpamapS: So, I've heard we are getting ftests automated? Do you know something about that? :-) [20:58] SpamapS: cool, thanks [21:01] 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] adam_g: It was actually about "functional tests" [21:05] 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] adam_g: It's pretty ineffective at the moment, though, because we don't really run the tests [21:06] 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] adam_g: and then enhance those tests [21:06] niemeyer: ah, gotcha. [21:06] Also makes a lot of sense in that final runway towards 11.10 [21:24] niemeyer, hi [21:25] 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] niemeyer, sounds good [21:27] 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] that's odd using --fixes=lp:bug_num when committing a branch merge adds a link to the bug against trunk [23:16] i thought it was supposed to just close the bug.. [23:18] 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