lp://staging/~jimbaker/pyjuju/debug-relation-hook-context

Branch merges

Propose for merging

No branches dependent on this one.

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

534. By Jim Baker on 2012-04-29

Add missing invoker.start call

533. By Jim Baker on 2012-04-27

Log actual caching of relation hook contexts

532. By Jim Baker on 2012-04-25

merge relation-ids-whitespace-separated [r=hazmat][f=988065]

[trivial] Default output format of relation-ids now uses newline to
separate (so like relation-list), instead of defaulting to json.

531. By Kapil Thangavelu on 2012-04-15

[trivial] update terminate-machine to utilize JUJU_ENV if set [f=981387]

530. By Kapil Thangavelu on 2012-04-15

[trivial] update status to utilize JUJU_ENV if set [f=981387]

529. By Kapil Thangavelu on 2012-04-13

[trivial] fix some recent tests that fail to pass without AWS_ env vars set [r=clint-fewbar]

528. By Clint Byrum on 2012-04-12

[r=hazmat][f=964640] Adding a basic description of debug-log to online help and reordering log levels

527. By William Reade on 2012-04-12

orchestra provider now respects ubuntu-series constraint

This is done by setting a new system profile before powering on the machine;
and assumes that the Cobbler system profiles created as part of the
ubuntu-orchestra-server install actually exist. Anecdotal evidence suggests
that people really don't mess with the distros and profiles available (they
just set up their systems and go) and so I consider the impact of this
drawback to be extremely limited.

Furthermore, while it is possible to extract real arch and series info from
cobbler (ie we can get a system's arch from its profile's distro, and we can
partially match new profiles by checking the distro's series and arch) this
is not enough to select an actual profile without depending on some
convention: we either have to infer the presence of the juju preseed from
the profile name (as I do currently) or to check the profile itself for
a magic string (ie the path to the juju preseed).

So: we depend on orchestra install conventions, whatever we do; and IMO it's
cleanest and simplest to actually embrace that and save all the mucking
about with distros and profiles.

R=hazmat
CC=
https://codereview.appspot.com/6012045

526. By Kapil Thangavelu on 2012-04-12

merge managed-zk-client, also fix trunk test, and disable topo migration [r=fwereade]

 juju now uses the txzookeeper.managed Client which automatically restablishes
 sessions recreating presence nodes and triggering extant watches.

 This also fixes some subordinte changes, namely a broken lxc test, and disables the
 transparent topology migration as without accompanying code changes to running agents
 it will cause problems.

525. By Benjamin Saller on 2012-04-12

Subordinate support in unit agent lifecycle [r=kapil] [f=805585,963355]

This branch lands the support in the unit agent which allows it to deploy
subordinate services in its own container.