We only need those on the domservers (& admin machines).

…ed (DOMjudge#126)yet.

This is not possible (yet) for php_fpm but that one also exposes theleast interesting metrics for people snooping. If we would want that wewould need to do something with nginx for this.This is relevant for the online judge but also makes sense as teams canalways query the node endpoint on domservers.

Alternative is to do the same as for the PHP-FPM exporter

Add intended final to naming, shortened naming for readability

There is not clean way to keep the playbooks the same and keep our generic variables.The structure:wf46 - domserverwf47 - domserverwould get all variables from wf47 as that is the last defined hostgroup above domserver, putting the contest belowwould put all hosts (even judgehosts) in the domserver group.By symlinking we get the least worse solution as we have the variables, but for ansible those all look like new groups.Where possible we use the value from `all`, online is fully copied tomake sure we don't pick any value from the onsite branch.Use default values for Luxor

We import our admin accounts in the analyst instance, using anotherpassword only makes this more difficult.

The replication password is set lower in the wf46/wf47 as besides therisk for leaking the database we would also setup replication on theanalyst instance.The ICPC-tools variables are not relevant here as we at this point don'tsetup the CDS.

We still need to manually set our IP for the different instances for thekeepalived (although we could ask the DNS for that value) but this is astart. This is not tested yet but should be relatively simple to test.

eldering left a comment