I’m getting there... I abandoned the debug-hooks approach, since it appeared it wasn’t working for me, and instead went for this:
1) set up another shell executing the command ‘juju debug-log’ running as soon as the environment is setup (after bootstrap, I think); 2) monitor the ‘cloud’ bits (in my case AWS EC2) to see what is happening there. Then I was able to execute the deploys and sets and see the activity on the debug-log (which also shows hook activity). Two observations: 1) the `debug-log` command is not documented very well: executing it without parameters tails the log (forever) until ^C’d out. To see the whole of the log so far execute "juju debug-log -n 1”, and then ^C out. (“-n 0” is invalid for some reason); 2) there is a lot of pinging going on in the log, which you have to ignore, basically; it is hard to tell when everything quiesces, and it appears that it is important to know! Anyhow, I’m now running a jenkins server and two connected slaves with customised tools setup in the cloud without having to touch these machines or the cloud services (after getting the keys). I’m quite happy! On 8 Jan 2014, at 16:46, Steve Powell <[email protected]> wrote: > I’m going to try again, waiting a long time between steps, and monitoring the > debug-log as I go.
-- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
