Skip to content

Tape REST API - Implement "default" targeted metadata handling

Requirements

Check the EOS Jira issue: https://its.cern.ch/jira/browse/EOS-6201

Copy paste:

As discussed here: https://gitlab.cern.ch/cta/operations/-/issues/1322#note_8431692

Targeted metadata allows clients to pass extra information for each file they want to stage. This field content is a JSON object that contains specific metadata for a targeted site name. The site is free to interpret this metadata or not and to act upon them.

Example:

"targetedMetadata": {  
   "atlas-eoscta@cern.ch": {     
     "activity": "expe_t0_daq"  
   }
}

Currently EOS only look at the targetedMetadata that are named according to the sitename. It would be nice that if the targetedMetadata named "default" are passed to each file to stage, that EOS takes them into account.

Example:

"targetedMetadata": {  
   "default": {     
     "activity": "expe_t0_daq"  
   }
}

Beware: if the sitename's targeted metadata are provided, EOS must take them into account and not look at the "default" targeted metadata:

Example:

"targetedMetadata": {  
   "default": {     
     "activity": "expe_t0_daq"  
   },
   "atlas-eoscta@cern.ch": {     
     "activity": "THIS_ONE_WILL_BE_CONSIDERED"  
   }
}