On 2 August 2014 5:10:43 AM AEST, Alan McKinnon <alan.mckin...@gmail.com> wrote: >On 01/08/2014 19:50, Сергей wrote: >> Also you can have a look at anacron. >> >> >> > > >Unfortunately, anacron doesn't suit my needs at all. Here's how anacron >works: > >this bunch of job will all happen today regardless of what time it is. >That's not what I need, I need something that has very little to do >with >time. Example: > >1. Start backup job on db server A >2. When complete, copy backup to server B and do a test import >3. If import succeeds, move backup to permanent storage and log the >fact >4. If import fails, raise an alert and trigger the whole cycle to start >again at 1 > >Meanwhile, > >1. All servers are regularly doing apt-get update and downloading >.debs, >and applying security packages. Delay this on the db server if a backup >is in progress. > >Meanwhile there is the regular Friday 5am code-publish cycle and >month-end finance runs - this is a DevOps environment.
I'm not sure if its quite what you have in mind, and it comes with a bit of a steep learning curve, but cfengine might fit the bill. http://cfengine.com Bruce -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
