f3e89a488c
Change the default parameters to the role to be zuul site variables. Because of variable precedence, having these not be site variables means someone could override them in a job. Since one of the actions is to read and log the contents of a file, we likely don't want to give people the ability to do that with an arbitrary file. The traceroute host isn't as important to be a site variable, but it's still not actually something that jobs should override - it's a feature of the deployment. Both variables work if they are not set, so deployers should still be able to use this role without defining site-variables. But it should be made clear to them that if they want those features they really should define the locations in a site-variable and not in a normal job variable. configure-mirror similarly allows in-job override, but maybe that's ok for now and leaving the site-variable value as a default is fine? Finally, add a new zuul_site_image_manifest_files list, so that we can specify more than one file to read. Set the defaults of it to be the files that the dib nodepool elements emit. We'll also look in to pushing those manifest files up a level into dib so that expecting nodepool nodes to have them is even more reasonable. Change-Id: I632a32fdfac4bfe57eb269ac8e183fb8df34d48f
1.2 KiB
1.2 KiB
Log information about the build node
Role Variables
If defined, a host to run a traceroute against to verify build node network connectivity.