AMI Databases The AMI Database Project Atlas Data

AMI Databases The AMI Database Project Atlas Data Challenge Bookkeeping, and the Tag Collector, a new tool for Release Management. Solveig Albrand, Johann Collot, Jerôme Fulachier 10/25/2020 S. A. CHEP 03 1

AMI Databases First Steps • The AMI project started in the spring of 2000. The first realization was an electronic notebook for Atlas LAr testbeam runs. • Soon, we had other requests for other database projects: Needed to reuse software, and to make databases “self describing” so they can be used in a generic way. The AMI web site is at http: //larbookkeeping. in 2 p 3. fr/AMI (has a PDF version of this presentation) 10/25/2020 S. A. CHEP 03 2

AMI Databases Some Design Principles • • • Use an RDBMS. Use many RDBMS. Be generic. Distribute geographically Manage long term projects (schema evolution) • Place emphasis on user interfaces. SQL and Java were chosen 10/25/2020 S. A. CHEP 03 3

AMI Databases AMI Architecture 10/25/2020 S. A. CHEP 03 4

AMI Databases The Deployment of AMI on Several Servers. • Connections pass through a router database. • This enables selection of the correct server, jdbc driver, and database for access to the data. • The databases contain their own description. (Entities, relations, and meta – information and behaviour. 10/25/2020 S. A. CHEP 03 5

AMI Databases The Indirect Database Connection Mechanism BKK JDBC AMI Router Database AMI router tables project, process… AMI tables AMI Router Loader references 1 * Bookkeeping Database AMI DB Loader BKK tables AMI tables 10/25/2020 S. A. CHEP 03 6

AMI Databases Current Status • Used by ~6 projects. • In particular for the Atlas Data Challenge 1, for the “Application Meta Data” alias Production Bookkeeping. (> 50 000 files) (Physics logical file name) Does not deal with physical locations or replication. Atlas uses Magda for this function. • Available interfaces: Java, Command line, Web, (C++ prototype) 10/25/2020 S. A. CHEP 03 7

AMI Databases Instances of the “element” object Database Specific Objects Database Schema Overview Generic Objects 10/25/2020 S. A. CHEP 03 8

AMI Databases 10/25/2020 S. A. CHEP 03 9

AMI Databases 10/25/2020 S. A. CHEP 03 10

AMI Databases Future Plans for AMI/ Atlas Bookkeeping • Replication at several sites. (Atlas DB group) • Build tools to manage AMI databases. • Introduce WEB SERVICES – GRID Integration, certificate authorisation (Spitfire) – Communication with MAGDA (talk tomorrow Wensheng Deng) • Build application specific tools especially for Atlas Bookkeeping. (Production Managers, more features for physicists) 10/25/2020 S. A. CHEP 03 11

AMI Databases Tag Collector • A databased application for release management. • AMI compliant (but uses PHP). • Sits on top of CVS, and CMT (our configuration management tool) • In use since September 2001. Some History… 10/25/2020 S. A. CHEP 03 12

AMI Databases Atlas Release Approaches Anarchy! I goofed with the tag for the External/Gaudi. Interface package for release OK, I've moved Reconstruction-01 -03 -01 on egamma. Rec-00 -00 -03 2. 0. 1. It won't affect the SRT release, but it will affect attempts to build Dear All, and on Reconstruction the CMT release. Many thanks to those of you who responded to /Change. Log. I had forgotten (and I suspect I won't be the last one to do this) that CMT the mail about missing tags. Sorry about that has a very formal response when the major version ID increases (I changed There are still some problems - mainly David incomplete tags. from 01 -02 -07 to 02 -00 -00). It takes it to mean that the new version is On Thu, 18 Jan 2001 09: 13: 02 -0500 (EST) "S. Rajagopalan" Such accidents are inevitable if the same 2 -3 incompatible with the earlier one, and that packages that depend upon this people tag most of the <srinir@bnl. gov> wrote: package will essentially break. At the very least they should change their packages for practically every release and if one > > dependency on this package from something like: person (myself) has to > Hi - The tag for egamma. Rec should be egamma. Rec-00 -00 -03, not "02". use Gaudi. Interface-01 -* External collect and sort out a large number of > Please pick up the correct tags for this release. Thanks. (sometimes incomplete or to srini conflicting) tags. use Gaudi. Interface-02 -* External > This has to stop. I mindlessly chose 02 -00 -00 without thinking about this implication. > On Thu, 18 Jan 2001, David Rousseau wrote: In order to be backwards compatible I have created a new tag for > > Hello Maya External/Gaudi. Interface > > Please include Reconstruction-01 -03 -01 in the release (details below) Gaudi. Interface-01 -03 -00 > > Cheers > > David The code is identical to that of 02 -00 -00. But this version of the package should be used for any CMT release build, be it 2. 0. 1, 2. 0. 2 or 2. 1. 0. * egamma. Rec-00 -00 -02 Sorry about that. Sigh. . . > > - add _load and _entries files > > 10/25/2020 > > David S. A. CHEP 03 - update to CBNT ntuple 13

AMI Databases 10/25/2020 S. A. CHEP 03 14

AMI Databases Enforce some control! • Forbid anarchic tagging. (which packages are tagged, and when, respect the hierarchy) • Reduce developer error. Tag selection and CMT requirements files. • Make release building more efficient. • Centralize information on packages, especially documentation. 10/25/2020 S. A. CHEP 03 15

AMI Databases Tag Collector Architecture CVS Repository Tag. Collector Database View. CVS Tag. Collector PHP Services Web Interface WWW Mail AFS CLIENT 10/25/2020 S. A. CHEP 03 16

AMI Databases 10/25/2020 S. A. CHEP 03 17

AMI Databases Conclusions • Tag Collector is a victim of its own success. • Will be rewritten using AMI base classes. – Made more modular. – More features. • To look at the Tag Collector go to http: //larbookkeeping. in 2 p 3. fr/athena Username = “demo”, no password 10/25/2020 S. A. CHEP 03 18