6df6a3ab81
Since the contents of the status.json is only available in-memory from the Zuul scheduler, the contents are lost forever if the scheduler, or the server it is hosted on, crash. This implements two crons: 1) A curl to download a timestamped status.json, if it is available 2) File deletion so we keep no more than 180 timestamped status files at any time. The files are stored at a location within the scope of the zuul-web vhost in order to make it easily possible to dump queues with something like: /opt/zuul/tools/zuul-changes.py http://zuulv3.openstack.org/backup/status_timestamp.json Change-Id: Ia1923bfae0222559b8d2dcb5e0618848b3a618d0 |
||
---|---|---|
files | ||
manifests | ||
spec/acceptance | ||
templates | ||
.gitignore | ||
.gitreview | ||
Gemfile | ||
LICENSE | ||
README.md | ||
Rakefile | ||
metadata.json |
README.md
OpenStack Zuul Module
Overview
TODO: Quick overview