[00:18] <niemeyer> Okay, some great code reviewed, and now it's really time for bed.
[00:18] <niemeyer> Night all
[09:51] <ivoks> idea: does it make sense to use micro for example?
[10:17] <niemeyer> ivoks: You mean the micro instance type?
[10:17] <ivoks> yes
[10:17] <ivoks> for bootstrap
[10:17] <niemeyer> ivoks: It's too small
[10:17] <niemeyer> ivoks: Well.. maybe for bootstrap it's not
[10:17] <niemeyer> ivoks: But in general it's too slugish
[10:17] <niemeyer> sluggish
[10:18] <ivoks> i know
[10:18] <niemeyer> ivoks: We actually used it across the board until very recently
[10:18] <ivoks> but for learning and playing with ensemble...
[10:18] <niemeyer> ivoks: But we had complaints about it being extremely unpredictable in terms of performance
[10:18] <ivoks> amazone gives two micro instances for free for 1 year
[10:19] <niemeyer> ivoks: So we gave up on the idea to avoid burning the project image just because the instance is unreliably slow
[10:19] <ivoks> for someone that wants to try and play with ensemble (no production), those would be enough
[10:19] <ivoks> ok
[10:20] <niemeyer> ivoks: Yeah, it's a bit of a pity, but there's a reason why they give it for free :-)
[10:23] <ivoks> i know :)
[11:25] <_mup_> ensemble/expose-provision-machines r267 committed by jim.baker@canonical.com
[11:25] <_mup_> Add test re assigning a machine to a service unit with opened ports, opens ports on that machine
[14:55]  * hazmat waits for the coffee to kick in
[16:13] <niemeyer> hazmat: ping
[16:14] <hazmat> niemeyer, pong
[16:14] <niemeyer> hazmat: Yo
[16:14] <niemeyer> hazmat: All good there?
[16:14] <hazmat> just chatting with bcsaller about the config-set branch and orchestra
[16:14] <hazmat> niemeyer, all good.. wimbledon on in the background
[16:14] <hazmat> niemeyer, working on security doc, and upstart today
[16:14] <niemeyer> hazmat: Ah, awesome
[16:15] <hazmat> niemeyer, ready for the meeting anytime 
[16:15] <niemeyer> hazmat: How's the image stuff?
[16:15] <hazmat> niemeyer, in review
[16:15] <niemeyer> hazmat++
[16:15] <bcsaller> hazmat: I expect to have a draft doc of the co-located services proposal out soon too, so you can hear our thinking on that 
[16:15] <hazmat> niemeyer, looking good, start time for the bootstrap node is a little longer, but the rest seems quite workable
[16:15] <niemeyer> hazmat: Can I trow something else on your table without you falling down?
[16:15] <niemeyer> throw even
[16:15] <hazmat> niemeyer, shoot, we'll see if it sticks ;-)
[16:16] <niemeyer> hazmat: Juan had difficulties with peer relations
[16:16] <niemeyer> hazmat: It's my understanding that they were supposed to work already, is that right?
[16:16] <hazmat> niemeyer, hmm.. how so.. i've been using them a little for the mongodb stuff, but we don't have many formulas that use them
[16:16] <bcsaller> hazmat: the peer events didn't seem to fire, we haven't looked into it yet
[16:16] <hazmat> actually any
[16:16] <hazmat> hmm
[16:16] <niemeyer> hazmat: Hah, sweet
[16:16] <hazmat> niemeyer, i'll dig into that
[16:16] <niemeyer> hazmat: So it's likely something minor
[16:16] <niemeyer> hazmat: Let me send you his formula
[16:16] <hazmat> niemeyer, which formula .. thanks
[16:17] <hazmat> i can prioritize that, its probably a minor one
[16:18] <niemeyer> hazmat: Should be in your inbox
[16:20] <hazmat> niemeyer, not seeing it yet
[16:21] <hazmat> niemeyer, got it
[16:21] <niemeyer> hazmat: Sweet
[16:22] <hazmat> niemeyer, no attachment though
[16:22] <niemeyer> hazmat: Meeting in 1:40.. will try to dial you in a little earlier
[16:22] <niemeyer> hazmat: The branch is there
[16:22] <hazmat> niemeyer, ah right.. regular phone or skype?
[16:22] <niemeyer> hazmat: What phone number should I dial?
[16:22] <hazmat> niemeyer, in priv msg
[16:23] <niemeyer> hazmat: Thanks
[16:39] <hazmat> negronjl, so the problem with the tomcat formula is that its using relative addressing to files
[16:39] <hazmat> 2011-06-29 11:38:28,105 unit:tomcat6/1: hook.output ERROR: sed: can't read /usr/lib/ensemble/txzookeeper/../templates/tomcat-server-xml-top.tmpl: No such file or directory
[16:39] <hazmat> hth
[16:39] <hazmat> that output is from the debug-log which is very useful for debugging problems..  as is the debug-hooks cmd
[16:40] <hazmat> negronjl, there's a branch in review to ensure that formula hooks are always executed from the formula dir
[16:40] <hazmat> but it hasn't landed, atm the hook PWD isn't something that can be relied on by hooks
[16:40] <hazmat> and addressing paths from there should be absolute
[16:40] <hazmat> negronjl, i guess in this case your trying to get to some formula included config?
[16:41] <hazmat> negronjl, which will become more easier once bug 761015 is fixed
[16:41] <_mup_> Bug #761015: FORMULA_DIR should be available to hooks <Ensemble:In Progress by hazmat> < https://launchpad.net/bugs/761015 >
[16:41]  * hazmat grabs some food
[18:06] <niemeyer> hazmat: ping?
[18:06] <hazmat> niemeyer, pong
[18:06] <niemeyer> hazmat: Ring.. ring.. ring..
[18:06] <niemeyer> hazmat: Ring.. ring.. ring..
[18:06] <hazmat> niemeyer, no ring here
[18:06] <hazmat> niemeyer, phone or skype?
[18:06] <niemeyer> hazmat: We just talked to your answering machine
[18:07] <hazmat> niemeyer, hmm.. my phone is low let me plug-in and see if works better
[18:07] <niemeyer> hazmat: Again
[18:19] <hazmat> niemeyer, bcsaller, jimbaker, anyone.. i dropped.. pls callback
[18:20] <niemeyer> hazmat: Calling
[18:20] <hazmat> niemeyer, thanks
[19:05] <hazmat> niemeyer, bcsaller, jimbaker, anyone.. i dropped again.. pls callback
[19:05] <niemeyer>  hazmat Calling
[19:16] <hazmat> niemeyer, bcsaller, jimbaker, anyone.. argh! i dropped again.. pls callback
[19:17]  * hazmat kicks his phone company where the light don't shine
[19:19] <hazmat> niemeyer, bcsaller, jimbaker, anyone.. argh! i dropped again.. it might be time to give up.. 
[20:03] <hazmat> niemeyer, i've been curious while looking at zeromq go bindings, how the general problem of thread local resources is handled in go, since there isn't any easy way of distinguishing thread from a goroutine (ie their mapped m to  n to threads)
[20:04] <hazmat> seems like its also relevant in the context of gui apps where typically only one thread is managing interacting with the gui run loop
[20:06] <hazmat> the only thing variant i've seen for this seems a bit like overkill (runtime.LockOSThread etc)
[20:07] <niemeyer> hazmat: We have exactly the same problem with zk
[20:07] <niemeyer> hazmat: It's handled by giving it its own thread
[20:07] <niemeyer> hazmat: But the zeromq Go author wasn't very clever at that
[20:08] <niemeyer> hazmat: Which means it will blow up on people's face
[20:08] <hazmat> indeed, it looks experimental at best
[20:08] <hazmat> interestingly the erlang for (zeromq) version does much the same (separate thread allocation)
[20:08] <hazmat> niemeyer, thanks, i'll take a look at the gozk impl for ideas
[20:09] <niemeyer> hazmat: Haven't seen that, but it's the only option that makes sense.. goroutines with free threading is a feature which we shouldn't undermine