| _mup_ | ensemble/expose-provisioning r253 committed by jim.baker@canonical.com | 00:00 |
|---|---|---|
| _mup_ | Make explicit that a couple of methods are only to be used for testing | 00:00 |
| _mup_ | ensemble/unit-agent-resolved r275 committed by kapil.thangavelu@canonical.com | 00:39 |
| _mup_ | complete the change over to more transitions, fill out coverage | 00:39 |
| _mup_ | ensemble/unit-agent-resolved-part-two r274 committed by kapil.thangavelu@canonical.com | 00:48 |
| _mup_ | merge and resolve conflict | 00:48 |
| _mup_ | ensemble/unit-agent-resolved-part-two r274 committed by kapil.thangavelu@canonical.com | 01:01 |
| _mup_ | redo merge resolve conflict, grabbed the wrong resolved file | 01:01 |
| niemeyer | Yo! | 02:11 |
| niemeyer | hazmat: ping | 02:33 |
| hazmat | niemeyer, pong | 02:33 |
| niemeyer | hazmat: Yo | 02:33 |
| niemeyer | hazmat: I'm having some trouble to review the new unit-agent-resolved, for lack of a good based to compare it with | 02:33 |
| niemeyer | hazmat: ensemble-resolved, which is the pre-requisite, doesn't include the trunk yet | 02:33 |
| niemeyer | hazmat: the trunk doesn't include ensemble-resolved | 02:33 |
| niemeyer | hazmat: and unit-agent-resolved contains both | 02:34 |
| hazmat | niemeyer, no.. it doesn't, unit-agent-resolved is after ensemble-resolved in my pipeline | 02:34 |
| niemeyer | hazmat: So no matter what's the base, there are cross-changes | 02:34 |
| niemeyer | hazmat: Yes it is, thus, it includes the changes from it | 02:34 |
| hazmat | niemeyer, the base is ensemble-resolved | 02:34 |
| niemeyer | hazmat: Yes it is | 02:34 |
| hazmat | i need to push my latest which merges trunk | 02:34 |
| hazmat | of ensemble-resolved | 02:34 |
| hazmat | if you want to utilize it as a base | 02:35 |
| niemeyer | hazmat: unit-agent-resolved contains both the latest from trunk and the latest from ensemble-resolved | 02:35 |
| hazmat | niemeyer, yes | 02:35 |
| niemeyer | hazmat: I can't compare it with either without getting irrelevant changes | 02:35 |
| niemeyer | hazmat: (in the diff) | 02:35 |
| hazmat | niemeyer, the diff to ensemble-resolved looked fine to me | 02:36 |
| niemeyer | hazmat: The solution is to handle the ensemble-resolved merge on trunk, or to update it | 02:36 |
| niemeyer | -html_static_path = ['_static'] | 02:36 |
| niemeyer | +#html_static_path = ['_static'] | 02:36 |
| niemeyer | hazmat: That's part of that diff | 02:36 |
| niemeyer | hazmat: (and a lot of other things from trunk) | 02:36 |
| hazmat | pushing the latest ensemble-resolved | 02:37 |
| niemeyer | hazmat: That should handle it if you have trunk merged on it, thanks | 02:37 |
| hazmat | niemeyer, let me know if that fixes the issue | 02:37 |
| hazmat | its pushed | 02:37 |
| hazmat | that's current with trunk | 02:38 |
| niemeyer | hazmat: Yep, that did it, thank you | 02:38 |
| hazmat | niemeyer, cool, np | 02:39 |
| niemeyer | Phew, 2 to go | 03:01 |
| niemeyer | Tomorrow, though | 03:01 |
| _mup_ | ensemble/config-set r216 committed by bcsaller@gmail.com | 03:15 |
| _mup_ | checkpoint | 03:15 |
| _mup_ | ensemble/auto-dependency-resolution r217 committed by kapil.thangavelu@canonical.com | 03:53 |
| _mup_ | flesh out some tests using a new test ease of use api. | 03:53 |
| _mup_ | ensemble/expose-provisioning r254 committed by jim.baker@canonical.com | 04:17 |
| _mup_ | Test added to verify opened port parsing | 04:17 |
| kim0 | morning folks | 09:05 |
| _mup_ | ensemble/config-get r219 committed by bcsaller@gmail.com | 10:37 |
| _mup_ | use get_formula_state in get_relation_endpoints, removes duplicate code | 10:37 |
| _mup_ | ensemble/config-get r220 committed by bcsaller@gmail.com | 10:39 |
| _mup_ | rename hook's local_* methods as get_local_* | 10:39 |
| _mup_ | expanded test coverage | 10:39 |
| _mup_ | ensemble/config-get r221 committed by bcsaller@gmail.com | 10:41 |
| _mup_ | merge trunk | 10:41 |
| _mup_ | ensemble/trunk r219 committed by bcsaller@gmail.com | 10:44 |
| _mup_ | Merge config-get [r=niemeyer] [f=776605] | 10:44 |
| _mup_ | Merge support for config-get cli tool for use in hooks. This makes local service options available within hooks. | 10:44 |
| kim0 | config-get lovely :) | 11:40 |
| _mup_ | Bug #777816 was filed: Ensemble should resolve dependencies upon deploy <Ensemble:In Progress by hazmat> < https://launchpad.net/bugs/777816 > | 14:01 |
| niemeyer | hazmat: Morning! | 14:27 |
| hazmat | niemeyer, morning | 14:28 |
| kim0 | niemeyer: hazmat morning | 14:30 |
| hazmat | kim0, top of the morning | 14:30 |
| kim0 | hehe | 14:30 |
| hazmat | morning always seems a bit arbitrary given the our globally distributed nature | 14:31 |
| kim0 | Yeah .. maybe we should get a bot for translating timezone salutations | 14:31 |
| hazmat | from a symbolism perspective, morning is nice though, expressing at hope and joy at the beginning of a new day | 14:32 |
| hazmat | hmm.. puppet's changing licensing to apache | 14:37 |
| kim0 | so how do I have to bribe to merge my doc branches :) | 14:41 |
| kim0 | s/how/who/ | 14:41 |
| hazmat | kim0, i'll do it now | 14:49 |
| hazmat | niemeyer, do you know if the bzr --author flag on commit takes a full name or an lp name? | 14:49 |
| niemeyer | hazmat: I suppose it takes a full name | 14:50 |
| niemeyer | hazmat: Or, actually | 14:50 |
| niemeyer | hazmat: I think this is just metadata | 14:50 |
| hazmat | niemeyer, it is just metadata, but its displayed onlp | 14:50 |
| hazmat | niemeyer, the gopher ppa has the latest go packages? | 14:50 |
| niemeyer | hazmat: Displayed as is, I think | 14:50 |
| niemeyer | hazmat: It does | 14:50 |
| niemeyer | hazmat: ppa:gophers/go | 14:50 |
| hazmat | niemeyer, thanks | 14:51 |
| niemeyer | hazmat: np | 14:51 |
| niemeyer | Actually, I have to send those packages again.. some third-party libraries got included by mistake | 14:51 |
| _mup_ | ensemble/trunk r220 committed by kapil.thangavelu@canonical.com | 14:56 |
| _mup_ | merge kim0's new user guide and faq [a=kim0][r=niemeyer][f=734975] | 14:56 |
| _mup_ | Provides a tutorial within the documentation taking the user through | 14:56 |
| _mup_ | the process of getting started with Ensemble as well as an FAQ. | 14:56 |
| hazmat | kim0, done, and your noted as the author on lp and bzr history | 14:57 |
| hazmat | kim0, thanks again, that was much needed | 14:59 |
| _mup_ | ensemble/auto-dependency-resolution r218 committed by kapil.thangavelu@canonical.com | 15:10 |
| _mup_ | additional test for solving deps from both environment and formula repos. | 15:10 |
| hazmat | doing some bug milestone management, sorry about the noise | 15:20 |
| _mup_ | ensemble/resolved-state-api r204 committed by kapil.thangavelu@canonical.com | 15:31 |
| _mup_ | merge trunk | 15:31 |
| hazmat | niemeyer, should i change the relation resolved api now (it doesn't need the retry flag).. or just wait, since the entire stack uses the api.. | 15:33 |
| kim0 | hazmat: thanks man | 15:33 |
| hazmat | kim0, np | 15:34 |
| niemeyer | hazmat: Sorry, ECONTEXT | 15:35 |
| niemeyer | hazmat: What's that about again? | 15:35 |
| hazmat | niemeyer, sure.. the set_relation_resolved(relation_map) really just needs to be set_relation_resolved(relation_list) .. since retry hook has no meaning | 15:36 |
| hazmat | hmm.. i think i suggested that i just make the cli barf in this case | 15:36 |
| hazmat | i guess that api has other pending cleanups as well though | 15:36 |
| niemeyer | hazmat: Do we plan to make it retry in the future? | 15:36 |
| hazmat | niemeyer, hmm.. good question | 15:36 |
| hazmat | niemeyer, its concievable.. but not nesc. correct | 15:37 |
| hazmat | a hook execution may be obsolete in a relation context | 15:37 |
| hazmat | by the time we want to retry it | 15:37 |
| hazmat | i go ahead cli fix, and note is as something that needs adjustment as part of the staterequest protocol work | 15:39 |
| hazmat | ^it | 15:39 |
| hazmat | hmm. | 15:41 |
| hazmat | i guess i can try it and see how much work it really is | 15:41 |
| hazmat | niemeyer, thoughts on retry? | 15:44 |
| hazmat | uds sessions are posted | 15:45 |
| koolhead17 | hi all | 15:52 |
| kim0 | hey | 15:53 |
| koolhead17 | kim0: am at https://code.launchpad.net/~kim0/ensemble/user-tutorial-and-FAQ/+merge/58861 will buzz you later :) | 15:54 |
| kim0 | koolhead17: it's been merged .. http://people.canonical.com/~niemeyer/ensemble/user-tutorial.html | 15:55 |
| koolhead17 | ok :) | 15:56 |
| niemeyer | hazmat: Sorry, was answering that message in the cloud ML | 15:58 |
| niemeyer | hazmat: Hmm | 15:58 |
| niemeyer | hazmat: So, let's try to come up with a scenario | 15:59 |
| niemeyer | hazmat: DNS goes off for whatever reason | 15:59 |
| niemeyer | hazmat: db-relation-changed explodes | 15:59 |
| niemeyer | hazmat: Intended change done by the other side of the relation isn't acted upon | 15:59 |
| niemeyer | hazmat: No other changes are done | 15:59 |
| niemeyer | hazmat: DNS goes live | 16:00 |
| niemeyer | hazmat: ensemble resolved unit/0 db | 16:00 |
| niemeyer | hazmat: Change is lost | 16:00 |
| hazmat | niemeyer, yes | 16:00 |
| hazmat | niemeyer, we could capture enough information to retry the hook | 16:00 |
| hazmat | but then say unit/0 departs | 16:00 |
| hazmat | should we be retrying a hook for something which doesn't exist anymore? | 16:01 |
| niemeyer | hazmat: How would that take place? | 16:01 |
| niemeyer | hazmat: resolved shouldn't work on a relation which doesn't exist (!?) | 16:01 |
| hazmat | niemeyer, the relation exists but the remote peer that caused the change has departed | 16:01 |
| hazmat | s/peer/unit | 16:01 |
| niemeyer | hazmat: Hmm | 16:03 |
| niemeyer | hazmat: Thinking | 16:03 |
| hazmat | some of this might be more clear if we do on disk persistence and recovery, since the merge of last known to current is applicable | 16:03 |
| niemeyer | hazmat: Hmm.. maybe | 16:04 |
| hazmat | niemeyer, i'll leave the api as is for now | 16:04 |
| niemeyer | hazmat: Sounds good | 16:04 |
| niemeyer | hazmat: Can you please [trivial] a comment explaining that debate please? | 16:05 |
| niemeyer | hazmat: Just enough to give us context for following on that conversation at a latter time | 16:05 |
| hazmat | niemeyer, sure in the commit, merge proposal, bug report, code ? | 16:05 |
| niemeyer | hazmat: Code feels more visible.. next to the API which we should change | 16:05 |
| hazmat | niemeyer, sounds good | 16:05 |
| niemeyer | hazmat: Thanks | 16:05 |
| _mup_ | ensemble/expose-provisioning r255 committed by jim.baker@canonical.com | 16:16 |
| _mup_ | Merged trunk & resolved conflicts | 16:16 |
| _mup_ | ensemble/expose-dummy-provider r217 committed by jim.baker@canonical.com | 16:16 |
| _mup_ | Merged trunk | 16:16 |
| * hazmat lunches | 16:23 | |
| _mup_ | ensemble/expose-dummy-provider r218 committed by jim.baker@canonical.com | 16:25 |
| _mup_ | Use fail/succeed instead of inlineCallbacks for dummy methods w/o internal yield needs | 16:25 |
| niemeyer | hazmat: Enjoy | 16:28 |
| _mup_ | ensemble/expose-provisioning r256 committed by jim.baker@canonical.com | 16:28 |
| _mup_ | Merged upstream | 16:28 |
| niemeyer | One branch pending | 16:37 |
| niemeyer | jimbaker: Will review your lunch after lunch | 16:38 |
| niemeyer | Erm | 16:38 |
| niemeyer | jimbaker: Will review your branch after lunch | 16:38 |
| niemeyer | "Will review your lunch after branch" would be nice too | 16:38 |
| jimbaker | niemeyer, i believe i'm to have some sort of chicken soup to deal with my cold symptoms... i will see what my mother-in-law prepares ;) | 16:40 |
| niemeyer | jimbaker: ;-) | 16:40 |
| === niemeyer is now known as niemeyer_lunch | ||
| _mup_ | ensemble/trunk r221 committed by jim.baker@canonical.com | 16:47 |
| _mup_ | merge expose-dummy-provider [r=niemeyer][f=766241] | 16:47 |
| _mup_ | Adds dummy provider support for port opening/closing. | 16:47 |
| _mup_ | ensemble/expose-provisioning r257 committed by jim.baker@canonical.com | 16:48 |
| _mup_ | Merged trunk | 16:48 |
| _mup_ | ensemble/expose-hook-commands r249 committed by jim.baker@canonical.com | 16:49 |
| _mup_ | CLI commands | 16:49 |
| _mup_ | ensemble/expose-hook-commands r250 committed by jim.baker@canonical.com | 16:50 |
| _mup_ | Merged upstream & resolved conflicts | 16:50 |
| _mup_ | ensemble/resolved-state-api r205 committed by kapil.thangavelu@canonical.com | 17:14 |
| _mup_ | document set_relation_resolved api todo discussion | 17:14 |
| _mup_ | ensemble/resolved-state-api r206 committed by kapil.thangavelu@canonical.com | 17:18 |
| _mup_ | doc string cleanups per review. | 17:18 |
| _mup_ | ensemble/trunk r222 committed by kapil.thangavelu@canonical.com | 17:47 |
| _mup_ | merge resolved-state-api [r=niemeyer][f=767762] | 17:47 |
| _mup_ | Provides a get/set/clear/watch state api for marking unit errors as resolved. | 17:47 |
| _mup_ | ensemble/trunk-merge r191 committed by kapil.thangavelu@canonical.com | 17:48 |
| _mup_ | merge trunk | 17:48 |
| === niemeyer_lunch is now known as niemeyer | ||
| _mup_ | ensemble/ensemble-resolved r259 committed by kapil.thangavelu@canonical.com | 17:54 |
| _mup_ | update code comments per review comment | 17:54 |
| _mup_ | ensemble/trunk r223 committed by kapil.thangavelu@canonical.com | 17:57 |
| _mup_ | merge ensemble-resolved [r=niemeyer][f=767948] | 17:57 |
| _mup_ | Provides a new ensemble resolved subcommand for marking unit errors | 17:57 |
| _mup_ | as resolved. | 17:57 |
| niemeyer | Alright, last branch in review! | 18:16 |
| hazmat | niemeyer, i've got some comments on the unit-agent-resolved review that i would like to discuss | 18:26 |
| hazmat | already attached to the review | 18:26 |
| niemeyer | hazmat: Ok.. I'll need some time to go over this review I'm doing | 18:41 |
| _mup_ | ensemble/unit-agent-resolved r279 committed by kapil.thangavelu@canonical.com | 18:41 |
| _mup_ | address review comments re formatting | 18:41 |
| === deryck is now known as deryck[lunch] | ||
| niemeyer | jimbaker: I really wish this branch was pushed in a more fine grained way | 19:14 |
| niemeyer | I'm not sure I'll be able to get through it today | 19:15 |
| jimbaker | niemeyer, there is an obvious split between the service changes and the specific support for provisioning | 19:16 |
| jimbaker | although the service changes are all very much boiler plate cut & paste | 19:17 |
| jimbaker | however, if you want me to split the branch in that way, i can certainly do so | 19:17 |
| niemeyer | jimbaker: Yeah, hundreds of lines of boilerplate ;) | 19:17 |
| niemeyer | jimbaker: That'd take even more time | 19:18 |
| jimbaker | niemeyer, i don't like any of it, but hopefully post budapest it can be removed | 19:18 |
| niemeyer | jimbaker: The idea is to not get into this state | 19:18 |
| niemeyer | jimbaker: As you said, there are several split points.. | 19:18 |
| niemeyer | jimbaker: Pushing such a huge branch 3 days before UDS isn't good | 19:18 |
| hazmat | niemeyer, jimbaker, bcsaller test api https://pastebin.canonical.com/47175/ | 19:38 |
| hazmat | i'm implementing parts as part of the dependency resolver work | 19:39 |
| hazmat | most of it is cribbed from other test helpers we have around | 19:39 |
| === deryck[lunch] is now known as deryck | ||
| _mup_ | ensemble/trunk r224 committed by kapil.thangavelu@canonical.com | 21:02 |
| _mup_ | merge unit-agent-resolved [r=niemeyer][f=767961] | 21:02 |
| _mup_ | Provides a unit lifecycle support for processing resolved unit relations. | 21:02 |
| * niemeyer => break | 21:35 | |
| === niemeyer is now known as niemeyer_break | ||
| _mup_ | ensemble/unit-agent-resolved-part-two r279 committed by kapil.thangavelu@canonical.com | 21:38 |
| _mup_ | update unit agent to use correct transition depending on retry setting. | 21:38 |
| _mup_ | ensemble/trunk r225 committed by kapil.thangavelu@canonical.com | 21:43 |
| _mup_ | merge unit-agent-resolved-part-two [r=niemeyer][f=776014] | 21:43 |
| _mup_ | Provides unit agent support for transitioning resolved units and unit relations. | 21:43 |
| _mup_ | ensemble/debug-hook-scope-guard r211 committed by kapil.thangavelu@canonical.com | 21:50 |
| _mup_ | merge trunk | 21:50 |
| _mup_ | Bug #778134 was filed: debug hook seems to have lost hook cli context when using hook api <Ensemble:New> < https://launchpad.net/bugs/778134 > | 22:03 |
| hazmat | we really do need to have ensemble changed in the environment | 22:03 |
| hazmat | or use byobu.. its hard to tell what the debug is actively working on otherwise | 22:03 |
| hazmat | sigh.. we need more release testing, or feature freezes before a release. so many new features this release, i'm seeing a few behavior regressions | 22:09 |
| jimbaker | hazmat, agreed - i haven't fired up AWS recently since i'm working on stuff that just needs unit testing, *for now* | 22:11 |
| jimbaker | but experience has shown repeatedly that we don't anticipate enough in our unit tests | 22:11 |
| _mup_ | ensemble/debug-hook-scope-guard r212 committed by kapil.thangavelu@canonical.com | 22:14 |
| _mup_ | switch to using byobu | 22:14 |
| * niemeyer_break waves | 22:56 | |
| === niemeyer_break is now known as niemeyer | ||
| _mup_ | ensemble/trunk r226 committed by kapil.thangavelu@canonical.com | 23:04 |
| _mup_ | merge debug-hook-scope-guard [r=niemeyer][f=776014] | 23:04 |
| _mup_ | Enables live hook debugging via screen/byobu, with better start/end condition handling. | 23:04 |
| _mup_ | ensemble/expose-hook-commands r251 committed by jim.baker@canonical.com | 23:05 |
| _mup_ | Hook command skeleton, plus parse_port_protocol for that arg | 23:05 |
| * niemeyer => dinner | 23:58 | |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!