Distribution of ATLAS Software and configuration data Costin Caramarcu on behalf of ATLAS TDAQ SysAdmins.

Slides:



Advertisements
Similar presentations
Topology The physical topology of a network refers to the configuration of cables, computers and other peripherals. The main types of network topologies.
Advertisements

Releases & validation Simon George & Ricardo Goncalo Royal Holloway University of London HLT UK – RAL – 13 July 2009.
Native Monitoring packsOps Mgr SP1Ops Mgr R2Ops Mgr 2012 Ops Mgr 2012 Feature PacksN/AOps Mgr 2012 Product Ship.
1 Databases in ALICE L.Betev LCG Database Deployment and Persistency Workshop Geneva, October 17, 2005.
G O B E Y O N D C O N V E N T I O N WORF: Developing DB2 UDB based Web Services on a Websphere Application Server Kris Van Thillo, ABIS Training & Consulting.
Replication Technologies at WLCG Lorena Lobato Pardavila CERN IT Department – DB Group JINR/CERN Grid and Management Information Systems, Dubna (Russia)
F Fermilab Database Experience in Run II Fermilab Run II Database Requirements Online databases are maintained at each experiment and are critical for.
1 The ATLAS Online High Level Trigger Framework: Experience reusing Offline Software Components in the ATLAS Trigger Werner Wiedenmann University of Wisconsin,
Database Infrastructure for Application Development Designing tables and relations (Oracle Designer) Creating and maintaining database tables d0om - ORACLE.
Large Scale and Performance Tests of the ATLAS Online Software CERN ATLAS TDAQ Online Software System D.Burckhart-Chromek, I.Alexandrov, A.Amorim, E.Badescu,
Cloud Computing for the Enterprise November 18th, This work is licensed under a Creative Commons.
2/10/2000 CHEP2000 Padova Italy The BaBar Online Databases George Zioulas SLAC For the BaBar Computing Group.
Ramiro Voicu December Design Considerations  Act as a true dynamic service and provide the necessary functionally to be used by any other services.
1 Alice DAQ Configuration DB
Databases E. Leonardi, P. Valente. Conditions DB Conditions=Dynamic parameters non-event time-varying Conditions database (CondDB) General definition:
Control in ATLAS TDAQ Dietrich Liko on behalf of the ATLAS TDAQ Group.
ALICE, ATLAS, CMS & LHCb joint workshop on
ATLAS Detector Description Database Vakho Tsulaia University of Pittsburgh 3D workshop, CERN 14-Dec-2004.
Clara Gaspar, March 2005 LHCb Online & the Conditions DB.
G. Cancio, L. Cons, Ph. Defert - n°1 October 2002 Software Packages Management System for the EU DataGrid G. Cancio Melia, L. Cons, Ph. Defert. CERN/IT.
Introduction CMS database workshop 23 rd to 25 th of February 2004 Frank Glege.
Online Software 8-July-98 Commissioning Working Group DØ Workshop S. Fuess Objective: Define for you, the customers of the Online system, the products.
Consulting Services JobScheduler Architecture Decision Template Information for Consulting Parties Information for Consulting Parties.
Oracle Data Integrator Agents. 8-2 Understanding Agents.
Database Server Concepts and Possibilities Lee Lueking D0 Data Browser Workshop April 8, 2002.
Peter Chochula ALICE Offline Week, October 04,2005 External access to the ALICE DCS archives.
CHEP March 2003 Sarah Wheeler 1 Supervision of the ATLAS High Level Triggers Sarah Wheeler on behalf of the ATLAS Trigger/DAQ High Level Trigger.
Artemis School On Calibration and Performance of ATLAS Detectors Jörg Stelzer / David Berge.
April 2003 Iosif Legrand MONitoring Agents using a Large Integrated Services Architecture Iosif Legrand California Institute of Technology.
CERN - IT Department CH-1211 Genève 23 Switzerland t High Availability Databases based on Oracle 10g RAC on Linux WLCG Tier2 Tutorials, CERN,
Maite Barroso - 10/05/01 - n° 1 WP4 PM9 Deliverable Presentation: Interim Installation System Configuration Management Prototype
Consulting Services JobScheduler Architecture Decision Template Information for Consulting Parties Information for Consulting Parties.
TDAQ Experience in the BNL Liquid Argon Calorimeter Test Facility Denis Oliveira Damazio (BNL), George Redlinger (BNL).
The ATLAS DAQ System Online Configurations Database Service Challenge J. Almeida, M. Dobson, A. Kazarov, G. Lehmann-Miotto, J.E. Sloper, I. Soloviev and.
LHCb Configuration Database Lana Abadie, PhD student (CERN & University of Pierre et Marie Curie (Paris VI), LIP6.
Alignment in real-time in current detector and upgrade 6th LHCb Computing Workshop 18 November 2015 Beat Jost / Cern.
The DCS Databases Peter Chochula. 31/05/2005Peter Chochula 2 Outline PVSS basics (boring topic but useful if one wants to understand the DCS data flow)
Computing Facilities CERN IT Department CH-1211 Geneva 23 Switzerland t CF CC Monitoring I.Fedorko on behalf of CF/ASI 18/02/2011 Overview.
Maria del Carmen Barandela Pazos CERN CHEP 2-7 Sep 2007 Victoria LHCb Online Interface to the Conditions Database.
ATLAS The ConditionDB is accessed by the offline reconstruction framework (ATHENA). COOLCOnditions Objects for LHC The interface is provided by COOL (COnditions.
INFSO-RI Enabling Grids for E-sciencE File Transfer Software and Service SC3 Gavin McCance – JRA1 Data Management Cluster Service.
Online DBs in run Frank Glege on behalf of several contributors of the LHC experiments.
Geant4 GRID production Sangwan Kim, Vu Trong Hieu, AD At KISTI.
1 Copyright © 2008, Oracle. All rights reserved. Repository Basics.
L1Calo DBs: Status and Plans ● Overview of L1Calo databases ● Present status ● Plans Murrough Landon 20 November 2006.
DCS Status and Amanda News
Understanding Solutions
Database Replication and Monitoring
IT-DB Physics Services Planning for LHC start-up
Status of Fabric Management at CERN
Database Services at CERN Status Update
Consulting Services JobScheduler Architecture Decision Template
ATLAS Software Distribution
Database operations in CMS
Controlling a large CPU farm using industrial tools
German Cancio CERN IT .quattro architecture German Cancio CERN IT.
A Messaging Infrastructure for WLCG
Level 1 (Calo) Databases
CHAPTER 3 Architectures for Distributed Systems
Conditions Data access using FroNTier Squid cache Server
TYPES OF SERVER. TYPES OF SERVER What is a server.
Workshop Summary Dirk Duellmann.
Local secondary storage (local disks)
TriggerDB copy in TriggerTool
Database Services for CERN Deployment and Monitoring
Database.
Chapter 17: Database System Architectures
Ruth Pordes, Lauri Loebel Carpenter, Elizabeth Schermerhorn
The Performance and Scalability of the back-end DAQ sub-system
Nominal Technologies for Modelling and High Level Applications of LCLS
Presentation transcript:

Distribution of ATLAS Software and configuration data Costin Caramarcu on behalf of ATLAS TDAQ SysAdmins

Outline Distribution of ATLAS Software Serving the configuration database and calibration coefficients

3 Distribution of ATLAS Software Software is installed only on CFS1 Software: TDAQ, HLT, Offline, external (LCG, JAVA, etc.) We provide the following on LFSs: Bins and libs from the OS (e.g. libshift for castor) ATLAS software (/sw, multiple versions)  tdaq: 5.9G  offline: 18G … etc. Detector specific sw (/det)  level1 calo: 36G  muons: 2.8G  hadronic calo: 696M …etc.

4 Distribution of ATLAS Software Use rsync over NILE Parallel and hierarchical sync Part or whole of the sw area can be sync’d Advantageous over other methods like bittorrent, etc.. Knowledge of Network topology CFS01CFS02 LFSs Clients

5 Measurements Flat hierarchy (1 level of sync, 10 nodes): 1 node syncs the other 10 nodes (Nightly sync) 2 h for 78 GBytes (no changes to sync) Hierarchy (3 levels of sync, 12 nodes): 1 node syncs 2 nodes after this finishes the 2 nodes sync the other 9 nodes 4h 40m for 116 GBytes Advantages for hierarchy Smaller CPU load on top level servers (~2h for flat, ~1.2h for hierarchy) Spreading of CPU usage over the levels For a larger configuration, this time should decrease

6 Other uses of LFS We are running TDAQ related services on the LFSs for its own clients TDAQ applications controller TDAQ Information service (to gather statistics from the tdaq apps) Services to serve databases TDAQ configuration Detector / trigger configuration

7 Local File Server RDB node X TDAQ Conf DB RACK Z NFS, later CORBA Serving the Configuration Database TDAQ configuration xml files to describe ATLAS online sw and hw parameters for given run Information about what runs where, how and at which moment required by each online application accessed via Remote DB Server (RDB) on top of CORBA protocol More then one application per node RDB server gets data via NFS from db repository (will be replaced by CORBA) Application

Local File Server DBProxyRDB node X TDAQ Conf DB NFS, later CORBA MySQL DBProxy Oracle RACK Z Serving the Configuration Database Trigger / detector config systems-specific config & conditions data are stored in relational DB DBProxy – cache and relay for MySQL (possibly Oracle in future) Hierarchical tree of DBProxy over cluster POOL files for calibration data Retrieved by dedicated server from offline Possibility to store data for next run on LFS and accessed via NFS by application