• Globus Online Testing
  • Support implemented in Rucio
  • Needs testing within ATLAS
    • Start to test transfers first, later on also do deletion
  • Currently ATLAS:
    • Harvester manages transfer to Globus endpoint
    • Would like to use Rucio to manage these transfers since US HPC facilities might move away from offering GridFTP endpoints
  • Questions/Issues/Ideas
    • Authentication
      • Each transfer has its own refresh token
        • Matt: There is a forever token tied to the auth_client - So no individual tokens needed
      • Need to handle Globus credentials (Safe way to inject/store)
      • How to handle this in the Multi-VO world?
        • Right now: Different submitters for each VO
    • Integration Testbed
      • Need to populate it with some data
      • Should be integrated to Panda testtools as well
      • 2 Endpoints we can use: SLAC and BNL (dual use)
        • No GLOBUS only endpoints yet
      • Will setup daemon on ATLAS integration cluster
    • Transfer/Scale testing
      • Once we are happy with transfers, also test reaper
    • Need to plan for 2 rules
      • WLCG <-> EDGE <-> GLOBUS
      • No multi-hop for this (Yet?)
      • EDGE node supports both WLCG world and GLOBUS world
    • Transfer limitations in GO
      • 100 transfers concurrently
      • Need to bulk them (Is there a bulk limit? 1Mio per transfer?)
      • Can submit more, GO will queue them?
    • Monitoring
      • Need to get the transfer events for GO also into the CERN monit stream
  • Further communication and followup on Slack: https://rucio.slack.com/archives/C8Z07UWKV