...
Using the the Tulip log analysis script's results for the last 3 days for enabled landmarks and results for the last 3 days for disabled landmarks we can identify the hosts and their success percentages. We opted to disable all the hosts which were having success less than 20%, and to enable the ones with success rate greater than 20%.
| Wiki Markup |
|---|
The tulip-tuning.pl script is in /afs/slac.stanford.edu/package/pinger/tulip and it performs the listed functions. It uses the LWP package to call reflector.cgi?function=analyze&days=3&ability=\[1\|0\] to access the Tulip analyzed log data for the last 3 days, downloads the analyzed tulip log file by requesting it from the reflector using [http://www-wanmon.slac.stanford.edu/cgi-wrap/reflector.cgi?function=analyze&days=3|http://www-wanmon.slac.stanford.edu/cgi-wrap/reflector.cgi?function=analyze&days=3] and saves it in a file and then parses the output to get: for option ability=1, the faulty landmarks (i.e. the enabled ones with below 20% success rate by default) are updated in the database to disable them; or option ability=0 the disabled landmarks with a success rate greater than 20% which are re-enabled in the database. |
It (tulip-tuning.pl) is run twice nightly (see the trscrontab) once to disable non working landmarks, once to enable landmarks that are now working again. tulip-tuning.pl is run before the sites.xml or sites-disabled.xml are created by http://www-dev.slac.stanford.edu/cgi-wrap/scriptdoc.pl?name=create_sites-xml.pl.
...