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. Yes, I know I can hack something together with bash scripts and cron with a truly insane number of flag files. But this doesn't work for sane definitions of work involving other people. I can't expect my support crew to read bash scripts they found from crontabs and figure out what they mean. They need a picture that shows what will happen when and what the environment looks like. So basically I need something to replace bash and cron the same way puppet replaces scp and for loops -- Alan McKinnon alan.mckin...@gmail.com
