=== al-maisan is now known as almaisan-away === almaisan-away is now known as al-maisan === al-maisan is now known as almaisan-away [08:28] Morning fellas === daker_ is now known as daker [14:44] Good mornings! [14:44] niemeyer: g'morning [14:45] A bit late today.. broke my glasses over the weekend, and had to run to try getting new ones before the trip :-( [14:45] niemeyer: i pushed an old branch of txzk into review, i realized i needed it for some of the connection level error handling in the subsequent session branch [14:45] hazmat_: Sounds good.. will do another pass in the queue today [14:46] niemeyer: that sucks, i finally broke down and got a new pair (my last pair was being held together by electrical tape..) [14:46] hazmat_: Ouch :) [14:46] hazmat_: I'm tempted to get an extra pair [14:46] hazmat_: Btw, there were several things pending there on Friday in the review queue. Would be good to have a pass there if you find a moment. [14:47] niemeyer: sure [14:51] <_mup_> txzookeeper/session-event-handling r46 committed by kapil.foss@gmail.com [14:51] <_mup_> - merge swap-sync-errors-to-failures [14:51] <_mup_> - allow for connection error handler to return a deferred, whose result will be chained [14:51] <_mup_> to the api deferred. [15:51] <_mup_> txzookeeper/session-event-handling r47 committed by kapil.foss@gmail.com [15:51] <_mup_> Improve connection error handler to api call result chaining. [16:51] hazmat_: session-event-handling mentions a pre-requisite branch which doesn't seem to be in review [16:53] niemeyer: it is in review in txzookeeper [16:53] niemeyer: its not visible in the ensemble kanban [16:53] niemeyer: the mp for session-event-handling has a link [16:53] hazmat_: Should it be to enable others to more easily pick it up as well? [16:55] niemeyer: i can add a cross linked bug for it, if that's helpful [16:56] hazmat_: Either that or we can harass someone directly to look at it :-) [16:56] niemeyer: i was going for the later ;-) [16:56] hazmat_: Sounds good too [16:57] off to see a man about a new car, bbiab [16:57] I'll have lunch now too.. [16:57] Will go through the branches after it [16:57] biab [17:30] niemeyer: so, re the man page.. I think you're right. While I was writing the man page manually, I kept thinking this should probably be in the online help, and just auto-generated into the man page. [17:31] niemeyer: I'll take a look at doing just that. [17:34] SpamapS: Ah, manually generated would work wonderfully too! [17:34] SpamapS: Erm [17:34] SpamapS: Ah, automatically generated would work wonderfully too! [17:34] * niemeyer takes his pills [17:46] " [17:46] AWS CloudFormation enables system administrators [17:46] and developers to create repeatable AWS [17:46] infrastructure deployments (Stacks) using [17:46] customizable architecture templates." [17:47] Sounds like we picked the right term for the concept.. (stacks) :-) [17:48] yeah [17:48] is there a draft spec for that yet? [17:52] SpamapS: No, just evolving over conversations for now [17:56] <_mup_> ensemble/debug-log-relation-settings-changes r266 committed by jim.baker@canonical.com [17:56] <_mup_> Doc strings, better total ordering on YAMLState item changes when logged [18:01] the cloudformation example templates use amazon [18:01] 's distribution [18:03] m_3: indeed, cloudformation is pretty much built around amazon's distro [18:05] SpamapS: the events seem to be the template's responsibility... http://paste.ubuntu.com/629916/ [18:08] m_3: yeah, another hacky thing just like running chef from one cookbook on another host. === bcsaller1 is now known as bcsaller [18:14] <_mup_> ensemble/debug-log-relation-settings-changes r267 committed by jim.baker@canonical.com [18:14] <_mup_> Verify representation of change items [18:14] SpamapS: https://bugs.launchpad.net/principia/+bug/799837 ( tomcat / no clustering ) [18:14] <_mup_> Bug #799837: new-formula ( tomcat6 ) < https://launchpad.net/bugs/799837 > [18:15] SpamapS: I have to do some other work for now but, will work on tomcat clustering when I get a chance. [18:15] negronjl: ok.. yeah I have some other stuff that has been neglected.. will take a look later today. [18:16] SpamapS: I know you're just neglecting me. :) [18:36] <_mup_> ensemble/debug-log-relation-settings-changes r268 committed by jim.baker@canonical.com [18:36] <_mup_> Test flush directly to ensure it returns the change items [18:42] <_mup_> ensemble/debug-log-relation-settings-changes r269 committed by jim.baker@canonical.com [18:42] <_mup_> PEP8, fix misspelling === daker is now known as daker_ [19:29] Anyone up for a quick review on this: https://code.launchpad.net/~kim0/ensemble/updating-faq/+merge/64679? [19:33] niemeyer, taking a look [19:39] what's the purpose of tagging new formulas with "new-formula" ? [19:41] that's probably the only way today to locate formulas in foreign branches ? [19:45] kim0: so you can find them for review. [19:45] kim0: I don't think we've agreed to that convention [19:45] kim0: At least I didn't see it being mentioned [19:45] Its how I'm reviewing new formulas in principia. :) [19:45] its just a bug tag [19:45] SpamapS: It's nice to present convention suggestions in general [19:45] SpamapS: Otherwise you'll be the only one using it :) [19:45] niemeyer: I did, in my Principia wiki page [19:46] SpamapS: Heh [19:46] https://ensemble.ubuntu.com/Principia mentions it and did from the very first revision I think. [19:47] https://bugs.launchpad.net/principia/+bugs?field.tag=new-formula [19:47] Quite a list. :) [19:47] That's nice! [19:48] I heard Launchpad may get support for listing branches through the API as soon as next week [19:48] Which means we'll be able to evolve the remote repo support pretty soon [19:48] Sweet.. the mr solution I have now *sucks*. :) [19:49] kim0, niemeyer - approved the FAQ branch [19:49] jimbaker`: Nothing will beat "deploy lp:~spamaps/formula" I guess :-) [19:49] Oops [19:49] SpamapS: Nothing will beat "deploy lp:~spamaps/formula" I guess :-) [19:50] niemeyer: and even better will just be the ability to not pull down all of the formulas in order to have a chance at automatic dependency resolution. [19:51] SpamapS: Ah, definitely [19:51] SpamapS: This will be the next step [19:52] or even stepping back further, forget the dependencies, just a 'ensemble search tomcat' and have it show you the available formulas.. very useful. [19:54] jimbaker`: Thanks. Can you please please merge it then? [19:54] Erm [19:54] s/please please/please/ :) [19:54] kim0, also according to wikipedia (can we really say that? someone else at least...), it should apparently "at run time" (http://en.wikipedia.org/wiki/Run_time) [19:54] SpamapS: Ah, that'll be awesome indeed [19:54] niemeyer, good to know it's not so urgent ;) [19:55] SpamapS: Or "info tomcat" [19:55] jimbaker`: Hehe :) [19:55] jimbaker`: Brain hiccup [19:55] niemeyer, ok, i will make the fixes we both recommended [19:55] jimbaker`: I think he already handled my review [19:55] kim0: Right? [19:57] niemeyer, kim0 applied the changes you requested [19:58] * kim0 reading .. catching up [19:58] niemeyer, i can take care of the minor fixes i suggested [19:58] jimbaker`: Sweet, thanks [19:58] or kim0, since you're here, maybe easier process from a branch history perspective if you just do it :) [20:00] jimbaker`: okie, applying your comments .. thanks for the review :) [20:03] jimbaker`: hmm, is there a smart way to reference your merge proposal comments, in my commit message? [20:05] kim0, i'm not aware of being able to link this in at the commit level [20:05] kim0, but our usual practice is to always reply to each comment, if only with an "ack" [20:06] jimbaker`: updates pushed .. can I do the merge? [20:06] kim0, i personally find that if i do that, the chance that i inadvertently let a review comment slide w/o action goes way down [20:06] kim0, hey, if you are able to do so, i will certainly let you merge :), but otherwise i can readily do it [20:07] * kim0 takes a shot [20:16] merged === _mup__ is now known as _mup_ === almaisan-away is now known as al-maisan === al-maisan is now known as almaisan-away