system-config/playbooks/roles/cloud-launcher-cron
Monty Taylor ebae022d07 Use project-config from zuul instead of direct clones
We use project-config for gerrit, gitea and nodepool config. That's
cool, because can clone that from zuul too and make sure that each
prod run we're doing runs with the contents of the patch in question.

Introduce a flag file that can be touched in /home/zuulcd that will
block zuul from running prod playbooks. By default, if the file is
there, zuul will wait for an hour before giving up.

Rename zuulcd to zuul

To better align prod and test, name the zuul user zuul.

Change-Id: I83c38c9c430218059579f3763e02d6b9f40c7b89
2020-04-15 12:29:33 -05:00
..
defaults Disable cloud launcher cron job during CI 2019-07-16 15:01:55 +10:00
tasks Use project-config from zuul instead of direct clones 2020-04-15 12:29:33 -05:00
README.rst Disable cloud launcher cron job during CI 2019-07-16 15:01:55 +10:00

Setup periodic runs of run_cloud_launcher.sh, which runs the cloud setup playbook against our clouds.

Note that this runs in an independent cron beacuse we don't need to run it as frequently as our normal ansible runs and this ansible process needs access to the all-clouds.yaml file which we don't run the normal ansible runs with.

Role Variables