[04:40] <hazmat> http://gigaom.com/cloud/vmware-open-source-cloud/
[04:41] <hazmat> jimbaker, yup.. i named it workflowclientstate to distinguish
[04:41] <hazmat> er. workflowstateclient
[04:41] <hazmat> it would also make sense as a method
[04:42] <niemeyer> "Gustavo Niemeyer (niemeyer) has assigned this bug to you for Ensemble:"
[04:43] <niemeyer> It'd be cool if Launchpad knew that "Gustavo Niemeyer" and "you" are the same person
[04:44] <_mup_> ensemble/bashified-wordpress-mysql-examples r180 committed by jim.baker@canonical.com
[04:44] <_mup_> Addressed review points re comments and db check
[04:44] <_mup_> ensemble/bashified-wordpress-mysql-examples r181 committed by jim.baker@canonical.com
[04:44] <_mup_> Merged trunk
[05:04] <jimbaker> hazmat, i like the quote "[mongodb evp] says it took about three months to integrate MongoDB with Cloud Foundry"
[05:05] <jimbaker> surely the average app won't take any longer than that
[05:07] <jimbaker>  hazmat, ok, i will wait for this branch so we don't duplicate work
[05:07] <jimbaker> it's obviously pretty minimal
[05:54] <_mup_> ensemble/bashified-wordpress-mysql-examples r182 committed by jim.baker@canonical.com
[05:54] <_mup_> Get the public hostname for wp config
[06:06] <_mup_> ensemble/bashified-wordpress-mysql-examples r183 committed by jim.baker@canonical.com
[06:06] <_mup_> Comment on the secret key used in wp config
[12:55] <kim0> hey guys .. is the principia repo now broken ?
[12:55] <kim0> how hard is it to fix it
[13:35] <kim0> niemeyer: I wanted to ask if now we have some simple path for contributing formulas. I suppose that's a good topic to discuss within today's irc meeting
[13:36] <kim0> I am aware of previous discussions to customize launchpad for that purpose .. but that's probably more long term 
[13:36] <niemeyer> kim0: Yeah, right now the easiest path is simply to publish them in whatever form and expect people to download them 
[13:36] <niemeyer> kim0: The repository is on the pipeline
[13:37] <kim0> ok .. I'll bring that up today
[13:38] <kim0> niemeyer: the other thing .. I understand principia is currently broken due to ensemble updates ? What would it take to fix it to match ensemble head
[13:39] <kim0> I was wanting to contribute a doc page about usage, but that needs a working formula :)
[13:40] <niemeyer> kim0: It would actually be very simple to fix it
[13:41] <niemeyer> kim0: I'm hoping to get a hand from SpamapS in the near future to push that forward
[13:41] <niemeyer> kim0: Feel free to bring that up in the meeting too
[13:41]  * kim0 nods
[13:42] <kim0> what caused the breakage ? a new hook .. trying to remember
[13:43] <niemeyer> kim0: Yeah, we've split a single hook in three
[13:44] <niemeyer> kim0: But it's trivial to fix because it was actually already three different hooks conflated into one
[13:44] <niemeyer> kim0: So it's basically copy & pasting part of the content out of a file
[13:47] <kim0> niemeyer: changed => {changed,established,broken} right ?
[13:47] <niemeyer> jimbaker: Almost, changed => {joined, changed, departed}
[13:49] <kim0> niemeyer: is joined a rename for established? same for departed/broken ? if so, I'll update docs
[13:49] <niemeyer> kim0: It's not, I think jimbaker is already updating them, though
[13:50] <kim0> ok
[13:50] <niemeyer> kim0: He mentioned yesterday in the call he had a branch to push for review
[13:51] <niemeyer> kim0: joined/changed/departed runs whenever a remote unit is detected/modified/removed in a relation
[13:51] <niemeyer> kim0: established/broken is called when the unit executing the hook has been taken out of the relation by itself
[13:51] <niemeyer> kim0: -broken means the world of that relation is gone.. -departed means a remote unit has left
[13:52] <niemeyer> kim0: There may still be other units after -departed.. there's nothing after -broken
[13:56] <kim0> niemeyer: so the last departed necessitates a broken, right
[13:57] <niemeyer> kim0: That's right!
[15:18] <niemeyer> hazmat: ping
[15:39] <jimbaker> kim0, the docs are very confusing on that i think
[15:39] <jimbaker> my doc branch should fix that, i will be pushing it for review sometime in the next couple of hours
[15:40] <hazmat> niemeyer, pong
[15:45] <niemeyer> hazmat: Hey there
[15:45] <niemeyer> hazmat: It looks like your UDS registration is still pending
[15:45] <hazmat> registration?
[15:45] <niemeyer> hazmat: Can you please check Marianna's email to allhands?
[15:45] <hazmat> i booked a ticket
[15:45] <hazmat> k
[15:48] <hazmat> oh.. missed that, thanks, bedless and badgeless sounds bad ;-)
[15:51] <kim0> jimbaker: awesome :)
[16:31] <_mup_> ensemble/new-hook-semantics-5-docs r197 committed by jim.baker@canonical.com
[16:31] <_mup_> More copy editing
[17:04] <_mup_> ensemble/new-hook-semantics-5-docs r198 committed by jim.baker@canonical.com
[17:04] <_mup_> More copy editing. Removed unimplemented -relation-established hook description
[17:12] <_mup_> ensemble/new-hook-semantics-5-docs r199 committed by jim.baker@canonical.com
[17:12] <_mup_> Copy editing on relation settings
[17:22] <_mup_> ensemble/unit-status-remote r200 committed by kapil.thangavelu@canonical.com
[17:22] <_mup_> unit and unit relation remote workflow clients.
[17:25] <_mup_> Bug #759981 was filed: The ensemble command line needs access to the workflow states of units and unit relations. <Ensemble:New> < https://launchpad.net/bugs/759981 >
[17:25] <_mup_> ensemble/new-hook-semantics-5-docs r200 committed by jim.baker@canonical.com
[17:25] <_mup_> Minor fix
[17:33] <_mup_> ensemble/unit-agent-formula-upgrade r205 committed by kapil.thangavelu@canonical.com
[17:33] <_mup_> merge unit-status-remote, throw away lots of upgrade workflow tests.
[17:34] <jimbaker> kim0, i just pushed up lp:~jimbaker/ensemble/new-hook-semantics-5-docs for review
[17:54] <_mup_> ensemble/bashified-wordpress-mysql-examples r184 committed by jim.baker@canonical.com
[17:54] <_mup_> Better comments
[17:55] <SpamapS> heh.. Marten Mickos talking about how FOSS has changed from "distribution centric" to "service centric" .. hmmm.. where have I heard that before? ;)
[18:02] <_mup_> ensemble/unit-agent-formula-upgrade r206 committed by kapil.thangavelu@canonical.com
[18:02] <_mup_> ensure that install error in agent is handled correctly (skips transition attempt to started)
[18:04] <hazmat> niemeyer, so for units of a service just report they won't be upgraded since their not running, and upgrade those that are?
[18:10] <_mup_> ensemble/bashified-wordpress-mysql-examples r185 committed by jim.baker@canonical.com
[18:10] <_mup_> Removed unnecessary sudo
[18:24] <hazmat> niemeyer, also on install_error.. ensemble resolved, would leave it at the installed state, right now post install, the agent moves things through to started. it seems like we should move it to the started state, but on a resolved without --retry from install_error  should we execute the 'start' hook, its not a retried hook, its a hook that hasn't been executed
[18:24] <hazmat> else sans workflow manipulation the unit is in a terminal state
[18:24] <hazmat> s/terminal/final
[18:25] <niemeyer> hazmat: Sorry, I've been in an intense conversatin for the past hour or so
[18:25] <niemeyer> Related to the repository tech
[18:25] <hazmat> niemeyer, cool  w/ lp folks?
[18:25] <niemeyer> hazmat: Yeah, sounds good regarding the upgrade=reporting+upgrade rest
[18:26] <jimbaker> i have pushed up an updated version of lp:~jimbaker/ensemble/bashified-wordpress-mysql-examples for review, this might be useful for people writing formulas
[18:26] <niemeyer> hazmat: I think install_error+resolved should move it to installed so that start is run normally
[18:27] <niemeyer> hazmat: No, with ISD
[18:48] <_mup_> ensemble/unit-agent-formula-upgrade r207 committed by kapil.thangavelu@canonical.com
[18:48] <_mup_> filtering and reporting for unit state on upgrade.
[18:49] <_mup_> ensemble/unit-agent-formula-upgrade r208 committed by kapil.thangavelu@canonical.com
[18:49] <_mup_> filtering and reporting for unit state on upgrade.
[18:57] <niemeyer> kim0: What time is our meeting today?  In 3 minutes?
[18:58] <kim0> niemeyer: yes
[18:58] <kim0> :)
[18:58] <jimbaker> are we meeting on skype?
[18:59] <niemeyer> kim0: I have a meeting overlapping with it this week specifically :-(
[18:59] <kim0> ew
[18:59] <kim0> jimbaker: irc
[18:59] <niemeyer> kim0: I'll keep an eye on it, though
[18:59] <kim0> ok cool
[18:59] <kim0> so let's jump over to #ubuntu-cloud
[19:00] <kim0> and start rumbling
[19:00] <kim0> jimbaker: can you please ping others who'd be joining
[19:00] <hazmat> kim0, what's the cloud rumble topic?
[19:01] <kim0> basically weekly overview of the development of ensemble
[19:01] <kim0> let's talk there
[19:01] <hazmat> kim0, sounds good
[19:01] <jimbaker> bcsaller, we are meeting over in #ubuntu-cloud
[19:02] <bcsaller> jimbaker: thanks
[19:02] <jimbaker> SpamapS, others, feel free to join us
[19:30] <hazmat> bcsaller, jimbaker anything to add in #ubuntu-ensemble
[19:30] <bcsaller> not really
[19:51] <hazmat> bcsaller, jimbaker, niemeyer postpone standup till tomorrow?
[19:52] <bcsaller> hazmat: works for me
[19:52] <niemeyer> hazmat: Hmm
[19:52] <niemeyer> robbiew: Are you still up for it?
[19:52] <robbiew> huh...what?
[19:52] <robbiew> heh
[19:53] <robbiew> niemeyer: I'm up for whatever ;)
[19:53] <niemeyer> Cool, let's do it
[19:54] <niemeyer> hazmat, bcsaller, jimbaker: Let's do a quick stand up with robbiew to talk about the reorg
[19:54] <niemeyer> hazmat: Can you quick it off?
[19:54] <jimbaker> ok, on skype?
[19:55] <niemeyer> Yea
[19:55] <niemeyer> h
[19:57] <niemeyer> hazmat?
[19:58] <robbiew> niemeyer: so having never conferenced in skype, is it just a simple means of having one person conference in everyone else?
[19:58] <robbiew> I'm a mumble man, damn it!!! :P
[19:58] <niemeyer> robbiew: Yeah, exactly :)
[19:59] <niemeyer> robbiew: It feels like getting someone with more bandwidth to host has shown better results, which is why I generally ask someone else rather than just firing it off
[19:59] <robbiew> ah, cool
[20:01] <hazmat> niemeyer, sure
[20:01] <hazmat> sorry.. zoned
[20:02] <hazmat> robbiew, what's your skype id
[20:02] <hazmat> robbiew, yeah.. its one person dialer
[20:02] <robbiew> hazmat: robbie.v.williamson
[20:02] <robbiew> very original
[20:03] <niemeyer> kim0: Thanks a lot for the meeting.. that was awesome
[20:03] <kim0> niemeyer: thanks man .. great work .. great team
[20:03] <hazmat> kim0, indeed. thanks
[20:26] <_mup_> ensemble/unit-agent-formula-upgrade r208 committed by kapil.thangavelu@canonical.com
[20:26] <_mup_> upgrade --dryrun reports unupgradeable service units.
[20:39] <_mup_> ensemble/unit-agent-formula-upgrade r209 committed by kapil.thangavelu@canonical.com
[20:39] <_mup_> additional tests for upgrade-formula cli around unupgradeable units.
[20:51] <kim0> hazmat: Hi, You had reviewed my tiny branch at https://code.launchpad.net/~kim0/ensemble/doc-fixes .. but it wasnt merged afaict .. should I rebase and bug you to merge it ? :)
[21:04] <hazmat> kim0, yeah. i was looking at that earlier today.. if you wouldn't mind rebasing that would be great
[21:32] <_mup_> ensemble/unit-agent-formula-upgrade r210 committed by kapil.thangavelu@canonical.com
[21:32] <_mup_> hook execution prioritization support for upgrade-formula hook.
[21:43] <_mup_> ensemble/unit-agent-formula-upgrade r211 committed by kapil.thangavelu@canonical.com
[21:43] <_mup_> ensure mutation access to _running attribute of hook executor is always done with the run lock.
[21:52] <hazmat> its a strange semantic to interact with prioritize through the workflow, with a stopped hook executor
[21:53] <hazmat> the workflow responds to the hook exit, but we won't have that till the executor is restarted
[21:53] <hazmat> i guess we restart it  inline.
[21:53] <hazmat> yeah.
[22:07] <_mup_> ensemble/unit-agent-formula-upgrade r212 committed by kapil.thangavelu@canonical.com
[22:07] <_mup_> hook executor.prioritize now returns after the priority hook is scheduled, and returns the exec deferred of the priority hook, unit lifecycle.upgrade_formula will prioritize the upgrade-formula hook, and start the executor.
[22:38] <hazmat> argh.. unity fail
[22:41] <hazmat> mumble seems to cause issues with unity
[22:41] <hazmat> at least for me
[23:57] <jimbaker> bbl, i'm going to the boulder hadoop meetup. my neighbor is giving a talk on katta (distributed lucene), which uses zk to support its scaling