No news items.
Streams info can be found at: https://indico.in2p3.fr/event/19937/contributions/75972/attachments/56927/75787/ESCAPE-T2.2-update.pdf
A.1 Collect information about what QoS options are currently available in the ESCAPE testbed. This is by a simple survey.
https://wiki.escape2020.de/index.php/ESCAPE_storage_QoS
Add storage path, missing info and modify it. (if required)
A.2 Build prototype QoS in ESCAPE testbed by adding QoS-specific RSEs and QoS-specific labels.
AP/ Gather all possible QoS labels.
Rohini: Can contact Alastair Dewhurst (at STFC) to ask about adding ECHO storage to the ESCAPE QoS testbed.
Ron: Interested in Amazon S3 storage?
Paul: yes because Rucio supports it.
Martin: Confirmed.
Rohini: Can we look into Rucio Web UI with non-CERN certificate?
Martin: It is ready but not tested
Ricardo: Will test it and let us know
B1. Build initial contact with experiments data-management experts through ESCAPE sites.
We have been building a wiki page to hold this information:
https://wiki.escape2020.de/index.php/Experiment_and_partners
Corrections may be needed.
Once contact is established with an ESFRI community, we will create doodle poll to select an interview day. We will then send this doodle poll on the mailing list, to allow people to participate who are interested.
C.1 Put together an architecture/design paper, based on the DOMA-QoS white paper:
https://twiki.cern.ch/twiki/bin/view/LCG/QoSWhitePaper
The details will be discussed at the ESCAPE QoS mini-workshop 2020-02-24 to 2020-02-25.
Next meeting will be on 2020-02-19, starting at 14:00 CET.