RE: Implement system reboot via juju hooks

2014-08-10 Thread Gabriel Samfira
Hi Bishop, What you are describing sounds like a scheduling framework. While that is a great feature to have, it goes beyond the scope of what I am trying to achieve. I agree that rescheduling a hook to be run later can be useful in more then the context I am describing, but the change I am pro

Re: issuing a jujud restart

2014-08-10 Thread Menno Smits
How this happens is slightly complex but the short answer is that if any of jujud's workers exit with a fatalError (as defined in cmd/jujud/agent.go), then jujud will terminate (and then be restarted by upstart). I'm not sure how you should propagate the need to exit from the restore API call thro

Re: avoiding unnecessarily entering "upgrade mode"

2014-08-10 Thread Menno Smits
On 6 August 2014 18:32, John Meinel wrote: > That sounds like what I would have expected was happening (we only run > upgrade steps if we think they have a reason to change things, and then > only set the last known version once all the upgrade steps have finished.) > > I'm concerned about the "

Re: avoiding unnecessarily entering "upgrade mode"

2014-08-10 Thread Menno Smits
On 6 August 2014 19:09, Dimiter Naydenov wrote: > > I would like to change the machine agent so that upgrade mode is > > only entered if the version in agent.conf is different from the > > running software version. This would mean that upgrade mode is > > only entered if there is an actual upgra

Re: avoiding unnecessarily entering "upgrade mode"

2014-08-10 Thread Menno Smits
On 7 August 2014 03:13, William Reade wrote: > SGTM too. It should always have worked like this -- rerunning all our > upgrade steps every time is *crazy*. > > Sorry, I got this detail wrong. The machine agent isn't rerunning upgrade steps unnecessarily, but it is waiting for an unnecessarily lon

Re: issuing a jujud restart

2014-08-10 Thread Andrew Wilkins
On Mon, Aug 11, 2014 at 5:41 AM, Menno Smits wrote: > How this happens is slightly complex but the short answer is that if any > of jujud's workers exit with a fatalError (as defined in > cmd/jujud/agent.go), then jujud will terminate (and then be restarted by > upstart). > > I'm not sure how you

Re: issuing a jujud restart

2014-08-10 Thread Menno Smits
On 11 August 2014 13:48, Andrew Wilkins wrote: > On Mon, Aug 11, 2014 at 5:41 AM, Menno Smits > wrote: > >> How this happens is slightly complex but the short answer is that if any >> of jujud's workers exit with a fatalError (as defined in >> cmd/jujud/agent.go), then jujud will terminate (and