c0fd3e0894
We noticed that our zuul scheduler was running out of disk and one of the causes of this is we are pulling all of the wonderful new zuul images and not pruning them. This happens because we were only pruning when (re)starting services and we don't do that automatically with Zuul. Address this by always pruning after pulling even if we don't restart services. This should be safe because prune will leave the latest tagged images as well as the running images. This should keep our disk consumption down. Change-Id: Ibdd22ac42d86781f1e87c3d11e05fd8f99677167 |
||
---|---|---|
.. | ||
defaults | ||
files | ||
handlers | ||
tasks | ||
templates | ||
README.rst |
Deploy nodepool launchers