@tomo @rafael if you have any review on this (should be ok as its kind of same commit than last update one, but well)

/reviewed-on nexedi/slapos!433

This release should be now stable enough for release

/reviewed-on !391

This reverts commit 9b3dfa01

  This version contains optimisation for restore (and a bit for backup), specially in case of large sets of unmodified files.

  In order to make an resilient backup, resilience stack wait for the internal backup finishes,
  before proceed to notify the pbs. This commit keeps the default behaviour (wait for 10 min w/o changes),
  however allows test software release adopt a much shorter waiting time (1min).

  With this commit we can accelerate resilience tests in several minutes.

  as buildout.hash.cfg uses templates/.. filename has to be defined here again.

 Life is too short to update md5sum by hand.

This fixes commit:
"resilient: fix parse error bug when parameters are multilines"

Otherwise, performances get awful on HDD, and not far better on SSD.

resilient: adds a promise to test integrity and the status of the last run of the feeds generated by notifier scripts

This commit is a fix for 8787716d. It allows to get the random cron string
generated previously through parameters, and not reading manually .installed.cfg.

The more there is data to backup, the more likely something can go wrong.
Running the exporter script several times will copy less and less things
at each run, so it should increase the probability to succeed.

This solution is better than adding a sleep in a crontab, because it will be a new
date every day

Revert "resilient: new paramater to define the time to sleep before running the backup in the cron job."

This reverts commit 30d1a937.

Default is a random value between 0 and 6 hours. KVM and Slaprunner test instances set it at 0.