We agreed that the Liquibase solution does what we want for the time being. The risk of software abandonment or lock-in is low, because we can easily replace Liquibase with something else.
CTA v1.0-3 is deployed, EOS and FTS running on XRootD 4.11.0.
Note that we have to use ctaprod for the recall exercise because the source and target DBs for migration have to be on the same Oracle instance, and ctaprod is the only DB schema available on the castor production instance.
Update after the meeting: ATLAS migration was done on Friday/Saturday. Julien ran tests over the weekend. We are ready for ATLAS recall exercise starting on Monday.
The concurrent archvial/retrieval/deletion "mutex" test and Rucio+FTS multi-hop test are in progress.
Five tapes were repacked one-at-a-time.
Next test changed the mount policy to use three drives in parallel. There was an intervention on the library so drives had to be shut down. When they were brought back up, repack restarted but did not complete properly. This was identified as a logic problem in the queuing system when no drives are available.
Note: This problem is a general one which does not only affect repack.
Vlado will continue with tests when drives are available again (after ATLAS recall exercise): 10 tapes × 3 drives; 10 tapes × 5 drives; etc.
David is working on CTA repack automation scripts.