LHCb priorities for WLCG-OPS

Marco CattaneoStefan Roiser

On behalf of the LHCb Computing Group

LHC

b p

riori

ties

2

Applications software management

m R3.1: Software deployment via CVMFSo Adopt for use as shared software area at all WLCG

sitesP Tier1 and Tier2

o Robust and redundant infrastructureP Not yet the case, e.g. manager machines not on safe

power

LHC

b p

riori

ties

3

Middleware Configuration, Deployment and Distribution

m Would like pre-compiled UI distribution that is binary compatible with LCG-AA platform+compiler+python

P e.g. SLC5 + gcc 4.3 + Python 2.6P e.g. SLC6 + gcc 4.6 + Python 2.6 (or 2.7 later)

o Installed in LCG-AA software shared area

o Including agile process for requesting and releasing patches

P Ability to request specific patches to a given released without waiting for next release cycled without picking up new features of next release

P e.g. ROOT deployment model:d Root 5.30.xx

Patches on 5.30, kept alive even after 5.32 release

LHC

b p

riori

ties

4

Monitoring

m 1.4 Streamline availability calculation and visualization

o LHCb supports proposal of one system for visualization and a single availability calculation

o LHCb does not want to be tied exclusively to an external system for running experiment specific tests

P Require a gateway to inject experiment view of availability coming from experiment information system

P Take advantage of advanced monitoring already available in DIRAC without re-implementing it in another system

LHC

b p

riori

ties

5

BACKUP SLIDE

CERN IT Department

CH-1211 Geneva 23

Switzerlandwww.cern.ch/

it

ES

6Andrea Sciabà

Example: a possible LHCb setup

SAM/ATP

GOCDB

BDII CEdiscovery

“generic”probes

topology.xml

VO

specific

results

generic

results

SAM

SAM

RSS SAM/

MRSS

SAM/ACE

“LHCb”probes

feeder for“generic” probes

One of ->

Site StatusBoard

Site Usability Site View

Grid View