system-config/playbooks/roles/nodepool-launcher
Clark Boylan c0fd3e0894 Pull and prune docker images together
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
2020-05-07 12:51:09 -07:00
..
defaults Run nodepool launchers with ansible and containers 2020-04-30 17:37:22 +00:00
files Run nodepool launchers with ansible and containers 2020-04-30 17:37:22 +00:00
handlers Run nodepool launchers with ansible and containers 2020-04-30 17:37:22 +00:00
tasks Pull and prune docker images together 2020-05-07 12:51:09 -07:00
templates Pass -f to nodepool to run in foreground 2020-05-06 14:06:56 -05:00
README.rst Run nodepool launchers with ansible and containers 2020-04-30 17:37:22 +00:00

Deploy nodepool launchers