Julien will repackage the changes done by Mark in MHVTL, and test them.
If it works fine then we can ask Mark to tag it. We will no longer need to use a homebrew version.
Apply unified code style / formatting
Vova will talk with the Gitlab team at CERN to see if they can push for the support of .git-blame-ignore-revs in gitlab.
Rework catalogue release procedure and deployment path
Joao will come up with a detailed plan on how we will automatically check which versions of the Catalogue are supported by the code.
We will use the pivot version vX.Y.0-k for catalogue releases.
Julien suggested that we configure in Cmake what are the catalogue versions compatible with a certain pivot release. This would be checked during pivot versions.
Schema verify fails for postgres in catalogue v13
We will fix this and tag as4.7.10-2
Modifications to eosevict/stagerrmcommand
The changes are done, and approved by the team.
Next steps: Merge eos evict to EOS / Fix operational tools (including FST GC) / remove eos stagerrm
Refactor RDBMS functions for catching SQL exceptions
Lasse will test the changes that he proposed only with the new catalogue physical library table.
We will then review this. If everything is good, we will adopt the strategy for other parts of the code.
[Ops] Repacks failing because of open denied
We need to create a new dev ticket that makes repack rm remove all old files.
For the lock problem (probably due to xrootd), Julien will ask David if he can take a look.
[Ops] Increase the repack expanding limit from 2 to 10
We will add this as a configuration to the tape server config file.
The default value should be kept as 2.
CMS usage of eos archive to eosctacms
Something like cta-admin invalidate cache should allow us to avoid restarting the frontend and alert all eoscta operators on things like that.
Changing the values should also invalidate the cache (although this only works for the current cta frontend).
15:20
→
15:30
dCache Integration10m
AOBs
15:40
→
15:50
AOB10m
AOBs
15:50
→
16:00
CTA dev board review10m
Objective
Look at the active issues in our CTA dev board.
Decide if they should be kept, removed, reassigned, prioritised, etc.