70 likes | 191 Vues
This presentation focuses on database (DB) related services essential for experiments at CCRC'08. Highlights include critical services like LFC, FTS, and DDM applications, along with their significance in supporting production activities. Key communication channels for setting up and configuring DB services are presented, including direct contacts with experiment coordinators. Regular attendance at meetings helps maintain operational efficiency and collaboration. The overview emphasizes the importance of clear communication and proactive management to avoid service instability.
E N D
Distributed DB Services – View on Communications Maria Girone, IT-DM CCRC’08 F2F – April 1st 2008
Overview • This talk focuses on DB-related services (experiment, Grid) • LFC, FTS, conditions, experiment applications – e.g. DDM, PhEDEx, .., also SAM / GridView, … • These are (largely speaking) among the services ranked by the experiments as (Highly) Critical and are hence on the ‘critical path’ for CCRC’08 and any other production activities • It does not cover (external) ‘Grid infrastructure’ DB-usage • GOCDB, CIC portal, … Communication in DBs- 2
DB services at Tier0 • Information regarding setting-up, configuring, upgrading and supporting the DB services at Tier0 • mailing list with the experiments/WLCG DB responsible for general announcements (mgt-physics-database@cern.ch) • direct contact to the experiments/WLCG services DB coordinators and application developers • Support at phydb.support@cern.ch • Up-to-date list maintained in Physics DB service wiki (https://twiki.cern.ch/twiki/bin/view/PSSGroup/PDBContacts) • DB sessions at 3D and WLCG workshops • DB resource requests and allocation • Experiments DB and WLCG services coordinators Communication in DBs- 3
DB services at Tier0 (2) • ATLAS • direct contact with offline and online DB coordinators (H. Von Der Schmitt, R. Hawkings, S. Vanyashin) and with the ATLAS DBAs (G. Dimitrov, F. Viegas) • regular attendance at the ATLAS DB meetings • regular attendance from ATLAS at the 3D operations meetings • CMS • direct contact with the offline and online DB coordinators (D. Schlatter, P. Paolucci, F. Glege) and CMS DBAs (B. Sulmanas, P. Picca) • regular attendance at the CMS DB meetings and at the CMS/IT coordination meetings • regular attendance from CMS/Frontier at the 3D operations meetings Communication in DBs- 4
DB services at Tier0 (3) • LHCb • direct contact to the online and offline DB responsible (N. Neufeld, J. Closier) • regular attendance to the LHCb/IT coordination meeting • regular attendance from LHCb at the 3D operations meetings • WLCG • direct contact to the WLCG Service Coordination team (H. Renshall, J. Shiers) • regular attendance to joint operations, LCG service coordination and CCRC'08 meetings • ALICE • direct contact with the offline and online DB responsible (L. Betev, P. Chochula) and ALICE online DBA (S. Kupusta) Communication in DBs- 5
Communication with Tier1s • Mailing list for announcements/discussions/problems (grid-service-databases@cern.ch) • 3D meetings (every two weeks) • Tier0 and Tier1 DBAs • Experiments DBAs and developers • Wiki pages (https://twiki.cern.ch/twiki/bin/view/PSSGroup/LCG3DWiki) • Up-to-date list of database interventions/outages • 3D workshops (also in conjunction with the WLCG workshops) Communication in DBs- 6
Some points to discuss • Hardware requirements and evolution not always clear – long lead times for acquisition and power / space constraints! • DB view Service view User view – are these always understood? Can we improve information flow(s)? • DB house-keeping operations: “transparent” interventions are still often done in an un-scheduled manner on production services – has resulted in service instability and even prolonged downtimes… Communication in DBs- 7