Helge: Upcoming events: Condor workshop at RAL 04 – 07 September is still missing (Note: added now.)
Romain: Spectre and Meltdown:
Variant 1 and 3 of vulnerabilities as listed on the slide are easily exploitable – and fixable by installing updated kernels, hence keep your systems up to date!
Variant 2 is more involved, requires microcode update, which are not available for all CPU types concerned yet.
Mattias: With Debian and Ubuntu, microcode is not installed by default, what is the situation with RedHat/CentOS/SL?
Romain: It is installed by default on these distributions
Maarten: HTCondorCE not yet ready for large-scale deployment due to issues concerning monitoring and accounting.
Ian C: Has a process been defined yet how to address these issues? Perhaps in the context of EOSCHub something can be foreseen; the accounting task force should take ownership.
Helge: Monitoring issues were already discussed in HEPiX, and a working group was formed that did not really take off; we should take this up again in the HEPiX board.
Ian C: We should profit from the proximity (in space and time) of the spring HEPiX with the HTCondor week to address these issues, which requires a list of issues to be addressed to be prepared in advance.
Mattias: I’m not aware of any bug tracker holding all the strings together.
Tim B: Note that some large sites are using HTCondorCE just fine, avoiding a full load of issues encountered with CreamCE previously.
Maarten: Will update the document with known issues.
Julia A: It is not clear whether solutions working at CERN and PIC are generic enough, in particular if they work with all batch systems.
Helge: This is not required – HTCondorCE is expected to be used with HTCondor only. (Julia: but people try nonetheless!)