1 / 6

LHCb priorities for WLCG-OPS

LHCb priorities for WLCG-OPS. Marco Cattaneo Stefan Roiser On behalf of the LHCb Computing Group. Applications software management. R3.1 : Software deployment via CVMFS Adopt for use as shared software area at all WLCG sites Tier1 and Tier2 Robust and redundant infrastructure

caesar
Télécharger la présentation

LHCb priorities for WLCG-OPS

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. LHCb priorities for WLCG-OPS Marco Cattaneo Stefan Roiser On behalf of the LHCb Computing Group

  2. Applications software management • R3.1: Software deployment via CVMFS • Adopt for use as shared software area at all WLCG sites • Tier1 and Tier2 • Robust and redundant infrastructure • Not yet the case, e.g. manager machines not on safe power

  3. Middleware Configuration, Deployment and Distribution • Would like pre-compiled UI distribution that is binary compatible with LCG-AA platform+compiler+python • e.g. SLC5 + gcc 4.3 + Python 2.6 • e.g. SLC6 + gcc 4.6 + Python 2.6 (or 2.7 later) • Installed in LCG-AA software shared area • Including agile process for requesting and releasing patches • Ability to request specific patches to a given release • without waiting for next release cycle • without picking up new features of next release • e.g. ROOT deployment model: • Root 5.30.xx • Patches on 5.30, kept alive even after 5.32 release

  4. Monitoring • 1.4 Streamline availability calculation and visualization • LHCb supports proposal of one system for visualization and a single availability calculation • LHCb does not want to be tied exclusively to an external system for running experiment specific tests • Require a gateway to inject experiment view of availability coming from experiment information system • Take advantage of advanced monitoring already available in DIRAC without re-implementing it in another system

  5. Backup SLIDE

  6. Example: a possible LHCb setup SAM/ATP GOCDB topology.xml SAM “generic” probes CE discovery “LHCb” probes BDII RSS feeder for “generic” probes SAM/MRSS generic results SAM VO specific results SAM/ACE Grid View Site Status Board Site Usability One of -> Site View

More Related