• Traceability Challenge (see slides):
  • All VOs replied with various delays (mostly communication issues)
  • Issues/improvement identified and to be followed up
  • Challenge problem: impossible to verify if VO identified the right job
    • It might be possible to identify user/payload from artefacts from the running environment
    • A new challenge should be scheduled in late automn with this information
• VO framework & local submission:
  • Alice: All should go through central but local submission still exists (users are on their own)
  • ATLAS: Same situation (local submission not forbidden), situation might be more complex for small T3 with special configuration.
  • The situation seems to vary case-by-case between sites (esp. T3 or lightweight sites)
  • Singularity integration in pilot jobs might unify usage (controlled environment, no pool account mapping, etc)
    • The situation should be re-evaluated in several months/a year
• HTCondor CE 8.6.3 contains the necessary patch to implement the traceability mentioned at the last meeting (pilot pushing information to the CE which can then log it). Details on how to use: https://htcondor-wiki.cs.wisc.edu/index.cgi/tktview?tn=6213
• Traceability procedures within CMS: https://twiki.cern.ch/twiki/bin/view/Main/CmsTraceability