DIRAC - Distributed Infrastructure with Remote Agent Control

• Published in: arXiv.org
• Main Authors: Brook, N, Bogdanchikov, A, Buckley, A, Closier, J, Egede, U, Frank, M, Galli, D, Gandelman, M, Garonne, V, Gaspar, C, R Graciani Diaz, Harrison, K, E van Herwijnen, Khan, A, Klous, S, Korolko, I, Kuznetsov, G, Loverre, F, Marconi, U, Palacios, J P, Patrick, G N, Pickford, A, Ponce, S, Romanovski, V, Saborido, J J, Schmelling, M, Soroko, A, Tsaregorodtsev, A, Vagnoni, V, Washbrook, A
• Format: Paper
• Language: English
• Published: Ithaca Cornell University Library, arXiv.org 12.06.2003
• Subjects: Client server systems; Computer architecture; Computer simulation; Metadata; Middleware; Production management; Queues; Remote control; Software; Software agents
• ISSN: 2331-8422

This paper describes DIRAC, the LHCb Monte Carlo production system. DIRAC has a client/server architecture based on: Compute elements distributed among the collaborating institutes; Databases for production management, bookkeeping (the metadata catalogue) and software configuration; Monitoring and cataloguing services for updating and accessing the databases. Locally installed software agents implemented in Python monitor the local batch queue, interrogate the production database for any outstanding production requests using the XML-RPC protocol and initiate the job submission. The agent checks and, if necessary, installs any required software automatically. After the job has processed the events, the agent transfers the output data and updates the metadata catalogue. DIRAC has been successfully installed at 18 collaborating institutes, including the DataGRID, and has been used in recent Physics Data Challenges. In the near to medium term future we must use a mixed environment with different types of grid middleware or no middleware. We describe how this flexibility has been achieved and how ubiquitously available grid middleware would improve DIRAC.