WLCG Tape REST API message exchange discussion

Friday 10 Dec 2021, 15:00 → 16:00 Europe/Zurich

Cedric Caffy (CERN), Mihai Patrascoiu (CERN)

The first topic I would like to discuss is the STAGE cancellation. Cancelling a STAGE
request will be done via POST /api/v1/stage/{id}cancel.

FTS would require that we allow the cancellation of a specified subset of the files that were previously
submitted for staging. Example: As FTS is per-file oriented, it might want to cancel the staging of only 3
files out of the 10 it previously submitted in the same request.

We need to discuss on a way to do it. I will come with a proposal, feel free to think about this ahead of the meeting.

We will then continue our discussion about the structure of the JSON messages that will be exchanged between the API and the client.

The following fields are needed by EOSCTA to stage files from tape:

• activity (string)

• priority (unsigned int)

• QoS (string)

• bringonlinedeadline (epoch timestamp)

• parentdataset (string given by Rucio)

• datasetsize (unsigned long given by Rucio)

• enduser (behind Rucio authentication)

• FTS job ID (UUID)

• FTS file ID (unsigned long)

• FTS endpoint (string)

As these fields need to be passed for each file, what are the ones we would like
to support in common and what are the ones we would like to put in the
targeted_metadata object?

Please come prepared to this meeting to find an agreement on this. You can use the following CodiMD document to give some ideas: https://codimd.web.cern.ch/xapLlnBpTJi9dApaCw4_jQ#
 

REST TAPE API Minutes 10th of December 2021.pdf

15:00 → 16:00 Message exchange discussion

Speaker: Cedric Caffy (CERN)