Pain Point: juju debug-hooks

[David Cheney]

HI David,

I'm sure you've found this bug by now,
https://bugs.launchpad.net/juju-core/+bug/1027876. In short we know
debug-hooks is something that needs to be implemented for feature parity.
The juju 2.0 milestone was supposed to be 13.04, but now represents a point
in the future (13.10 maybe) when a major version number (read, possibly
breaking change, or not as automagic upgrade) change will occur. I have no
information on when this feature is scheduled to be worked on at this time.

Cheers

Dave


On Sat, Jun 1, 2013 at 1:07 AM, David Britton
<david.britton at canonical.com>wrote:

> Hi All --
>
> The landscape team has been testing and porting various charms to
> juju-core, and one of the pain points has been the lack of juju
> debug-hooks.  This has bitten us in many subtle ways:
>
>  - You can't interactively debug quickly/easliy
>  - You can't "try out" commands in a hook environment to introspect
> relations, for example
>  - Studying hook interaction between services (one of the hard parts of
> juju) is difficult to understand without slowing things down with
> debug-hooks.
>
> The workaround at this point has been to modify scripts in place on the
> deployed unit and then retry relations/installs to get it right.  As you
> can imagine the lengthening of the debug cycle there is quite frustrating.
>  Anyone in the community using juju-core is probably hitting the same
> issues (just a guess).
>
> Is there a way to implement something in this space?  Even if it's not as
> nice and full featured as the pyjuju version, it would be quite welcome and
> useful.
>
> Thanks!
>
> --
> David Britton <david.britton at canonical.com>
>
> --
> Juju-dev mailing list
> Juju-dev at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20130603/a71a625f/attachment.html>