On 4 March 2015 at 13:45, Jorge O. Castro wrote:
> Hi everyone,
>
> Sometimes people deploy things like a complex bundle on a cloud and it
> doesn't work. Having to wrangle the person to find out which units
> broke, juju sshing in and manually digging around logs and refiring
> off hooks, etc. is
On Wed, Mar 4, 2015 at 10:12 AM, Adam Collard
wrote:
> Why not stick to the UNIX principle and compose a pipeline?
That would also do the trick, as long as it's something that can
capture what's going on in one snippet.
--
Jorge Castro
Canonical Ltd.
http://juju.ubuntu.com/ - Automate your Clou
Why not stick to the UNIX principle and compose a pipeline?
With https://bugs.launchpad.net/juju-core/+bug/1390585 fixed it could be as
simple as "juju debug-log --no-stream --replay | pastebinit"
On 4 March 2015 at 13:45, Jorge O. Castro wrote:
> Hi everyone,
>
> Sometimes people deploy things
Hi everyone,
Sometimes people deploy things like a complex bundle on a cloud and it
doesn't work. Having to wrangle the person to find out which units
broke, juju sshing in and manually digging around logs and refiring
off hooks, etc. is time consuming.
Marco and I thought something like `juju pa
