POOL Migration

General goal Exercise migration of POOL project code into ATLAS offline codebase

Prove it can be, Estimate effort Detect any surprises in advance and validate claims about which POOL components

ATLAS is using or not

Methodology Migrate code from POOL CMT project intoATLAS CMT project

CVS -> SVN Restructure directories Rewrite the requirement files

Take only what ATLAS is using Package-level granularity

Minimize changes to the files and code Easier to keep in synch with LCG POOL Establish code repository and functional test base before big changes

1

ATLAS Software Week Oct 2011Marcin Nowak BNL PAS Group

POOL Migration

POOL project package list Migrated packages

POOLCoreStorageSvcRootStorageSvc FileCatalog XMLCatalogPersistencySvcCollectionBase RootCollectionImplicitCollectionRelationalCollectionCollectionUtilitiesTests

2

ATLAS Software Week Oct 2011Marcin Nowak BNL PAS Group

Packages not migratedObjectRelationalAccessRelationalStorageServiceRulesFileCatalogRelationalFileCatalogLFCCatalogDataSvcCollection

POOL Migration

Migration status Packages migrated to ATLAS SVN offline repository

Database/APR/ Many integration tests had to be skipped because they were based on DataSvc

Nightly migration builds in MIG2 Using special „no-pool” LCGCMT release and Gaudi version External/AtlasPOOL glue package redirects to APR

Totally transparent for all clients 1 AANT utility needed a change in requirements 3 packages fail due to absence of DataSvc

2 tests and AtlCoolCopy.exe – need to be dropped or changed to use PersistencySvc

AthenaPOOL tests working RecExCommon example working

3

ATLAS Software Week Oct 2011Marcin Nowak BNL PAS Group

POOL Migration

Conclusions The migration was a huge exercise in CMT

... as expected Especially when migrating tests Not many problems with the code itself

MIG2 contains a working version of offline software without LCG POOL APR code is in ATLAS SVN repository and ready for further modifications

4

ATLAS Software Week Oct 2011Marcin Nowak BNL PAS Group