LSF may soon be replaced at SLAC, where the new batch allocation system may not support all Fermi OSes such as Windows and Mac. The committee'srestricted Confluence page is here. Two top contenders are SLURM and Univa Grid Engine: SLURM does not support Windows and they further claim it would be a 'big deal' to make that happen. On the other hand, UGE (Univa Grid Engine) hints that OSX support might not be so difficult (and they do support Windows).
It certainly not clear what the ultimate decision will be, and perhaps LSF will still be deemed the "best deal".
Our Options
Keep LSF
Amber has offered the possibility that we could retain some LSF licenses. Who would maintain LSF in that scenario?
...
We actually briefly discussed this back in Sept. 2011. Below are some exchanges with Tony from last year:
Need to teach Hudson about LATEST, HEADs and Releases:
We normally run hudson whenever a change is made in cvs/subversion. I
imagine it can be configured to run on specific tags, alternatively we
could write a module which triggers the build externally as we did for
the workbook.
Handling things like Doxygen generation, running unit tests, red dot summary etc
I didn't read the full list of tasks, but for EXO we certainly run make
and the use root to generate documentation, so doing similar things for
Fermi should be possible. This would certainly require some setup, maybe
Kim Lo would be available to help with some of this? We should also be
able to store extra information about the builds in our own database,
and augment the hudson interface with extra web pages using information
from the database.