Regarding the "tape reclaim" command, we have decided to only allow it on ACTIVE/DISABLED states.
HTTP Tape REST API tests feedback
We should not worry about stalling (unless we set stalling rules, it should not affect us). Ideally, stalling could be entirely removed for tape-enabled instances of EOS, but this is a task that needs to be discussed in more detail.
The important thing is to clearly define how we do backpressure on the CTA side. Julien will provide this info.
Add feature to disable tape files on problematic tapes
This is a desired feature also for Jacek / dCache!
We will separate the work in two parts: (1) Modify catalogue and cta-admin tool to be able to mark files as unavailable; (2) Modify scheduler logic to ignore retrieval of disabled files, or requeue them in case of dual tape copy.
Listing of tests to execute in pre-production
We will add a wiki page on gitlab to track every test that needs to be performed in pre-production. This table should be completed by the developers every time that they do a merge request. It will be part of the merge request procedure, and checked during every release to see if no entry is missing.
"" vs <> in headers
We will follow Jorge's suggestion and only use <> for external packages such as stdlib ones.
Release notes conflict
Updated release notes have been a common source of merge conflicts during a merge to main. This will need to be addressed, but for now will keep the discussion open. Jorge will open a ticket to keep track of it.
CTA dev board review10m
Look at the active issues in our CTA dev board.
Decide if they should be kept, removed, reassigned, prioritised, etc.