1 / 4

POOL Migration

This project aims to migrate the POOL project code into the ATLAS offline codebase, proving its feasibility, estimating effort, detecting surprises in advance, and validating claims about POOL components used by ATLAS. The methodology involves migrating code from POOL CMT project to ATLAS CMT project, restructuring directories, rewriting requirement files, and taking only what ATLAS uses. This will establish a code repository and functional test base before making significant changes.

sgreene
Télécharger la présentation

POOL Migration

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 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 Marcin Nowak BNL PAS Group

  2. POOL Migration • POOL project package list • Migrated packages POOLCoreStorageSvcRootStorageSvc FileCatalog XMLCatalogPersistencySvcCollectionBase RootCollectionImplicitCollectionRelationalCollectionCollectionUtilitiesTests • Packages not migrated • ObjectRelationalAccessRelationalStorageServiceRulesFileCatalogRelationalFileCatalogLFCCatalogDataSvcCollection Marcin Nowak BNL PAS Group

  3. 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 Marcin Nowak BNL PAS Group

  4. 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 Marcin Nowak BNL PAS Group

More Related