Merge lp:~kim0/pyjuju/adding-hook-traces-to-readme-for-bashified-example into lp:pyjuju
Proposed by
Ahmed Kamal
Status: | Work in progress |
---|---|
Proposed branch: | lp:~kim0/pyjuju/adding-hook-traces-to-readme-for-bashified-example |
Merge into: | lp:pyjuju |
Diff against target: |
55 lines (+32/-2) 1 file modified
examples/readme.txt (+32/-2) |
To merge this branch: | bzr merge lp:~kim0/pyjuju/adding-hook-traces-to-readme-for-bashified-example |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Clint Byrum (community) | Needs Fixing | ||
William Reade (community) | Approve | ||
Review via email: mp+62537@code.launchpad.net |
Description of the change
Fixed docs to match hook changes (joined instead of changed) and new execution order
To post a comment you must log in.
Unmerged revisions
- 188. By Ahmed Kamal
-
Updating hook trace, changed always gets fired after joined
- 187. By Ahmed Kamal
-
Fixing docs to match hook changes (joined)
- 186. By Ahmed Kamal
-
Adding a sample hook execution trace to readme to better understand execution dynamics
Excerpts from Ahmed Kamal's message of Thu May 26 18:51:41 UTC 2011: /code.launchpad .net/~kim0/ ensemble/ adding- hook-traces- to-readme- for-bashified- example/ +merge/ 62537
> Ahmed Kamal has proposed merging lp:~kim0/ensemble/adding-hook-traces-to-readme-for-bashified-example into lp:ensemble.
>
> Requested reviews:
> Ensemble Team (ensemble)
>
> For more details, see:
> https:/
>
> Fixed docs to match hook changes (joined instead of changed) and new execution order
Thanks again, for working on the documentation. Looks good but there are some errors in the traces.
There is no ensemble 'established' hook for relations. Instead we have joined called, all joines
are followed by a changed invocation (independent of if there is an actual change subsequent to
the join). All subsequent change invocations are due to changes in the related units.