Download presentation
Presentation is loading. Please wait.
Published byMark Walton Modified over 9 years ago
1
LHCb-ATLAS GANGA Workshop, 21 April 2004, CERN 1 DIRAC Software distribution A.Tsaregorodtsev, CPPM, Marseille LHCb-ATLAS GANGA Workshop, 21 April 2004
2
LHCb-ATLAS GANGA Workshop, 21 April 2004, CERN 2 Software to be installed Before an LHCb application can run on a Worker Node the following software components should be installed: Application software itself; Software packages on which the application depends; Necessary databases DIRAC software Before the software can be installed it should be packaged: Single untar command to install in place
3
LHCb-ATLAS GANGA Workshop, 21 April 2004, CERN 3 Software packaging The application packaging tools: Based on the projects; Using InstallArea populated while a project release; Automatic resolution of the dependencies between the projects: Analysing CMT dependencies information; Analysing CMTPATH defined by a project bootstrapping script. All the options are expanded to avoid including files All the necessary libraries are included – no assumption made about the availability of whatever software on the destination site (except python interpreter): External libraries; Compiler libraries.
4
LHCb-ATLAS GANGA Workshop, 21 April 2004, CERN 4 Software packaging (2) GAUDI + ExternalLibs + ROOT + Compiler libs GAUDI + ExternalLibs + ROOT + Compiler libs LHCb DaVinci Brunel Boole Gauss ParamFiles Geant4Files dkcards XmlDDDB Applications Data Packages Base libraries … …
5
LHCb-ATLAS GANGA Workshop, 21 April 2004, CERN 5 Software packaging (3) Package software: TAR files for the DIRAC style installation; RPM files suitable for the LCG installation; DIRAC software is packaged in a similar way Structure of installed DIRAC software is the same as that of the CVS repository The packaging tools are: Implemented as a set of python classes; Meant to be a part of the project release procedure Done by a software librarian
6
LHCb-ATLAS GANGA Workshop, 21 April 2004, CERN 6 Software installation Software repository: Web server (http protocol) LCG Storage Element Installation in place DIRAC way: By Agent upon reception of a job with particular software requirements; OR By a running job itself. Installation in place LCG2 way: Special kind of a job running standard DIRAC software installation utility
7
LHCb-ATLAS GANGA Workshop, 21 April 2004, CERN 7 Package structure Binary package structure: $LHCBPRODROOT=/opt/lhcb on LCG2 Common root for all the LHCb software on a production site or CE; Contains both application and DIRAC software $LHCBPRODROOT/lib/DaVinci/v12r3/bin/.../lib/.../options/.../setup.csh.../dependencies $LHCBPRODROOT/lib/DaVinci/v12r3/bin/.../lib/.../options/.../setup.csh.../dependencies
8
LHCb-ATLAS GANGA Workshop, 21 April 2004, CERN 8 Package setup dependenices file contains all the packages/versions on which the package depends Used to check and/or installed dependencies of the package setup.csh is executed before invoking the application: Setting up the application environment; Invokes setup.csh of each dependency package
9
LHCb-ATLAS GANGA Workshop, 21 April 2004, CERN 9 Analysis software Basic software (DaVinci, Gaudi, databases) installed in the same way from the LHCb repository; User algorithms: Shipped in the InputSandbox *.so libraries Python scripts DaVinci user options are appended to the standard options
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.