Change Iba195e7c5cec372c6ba4daf7059da5b6fb6740ec implemented
collection of output for `df -i` (inode counts) and `df -m`
(megabytes data) in validate-host, but did not add them to the
report file template. Correct this oversight so that the collected
information will be included in that file.
Change-Id: I8c2c4a90f18394a04fde84355a89a15bf5aa66b4
Split the network testing component of the validate-host rule into a
separate task, so it can be retried a couple of times in case
something is a bit slow about bringing up external networking. Add
failure collection of unbound logs if they appear to be in some common
locations (such as will be there on infra nodes).
Change-Id: Id12f1ba064fa2e5f75b9a5cfba76d238d23d3f57
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
Jeremy Stanley