DIRAC Review (13th December 2005) Stuart K. Paterson 1

DIRAC Review

Exposing DIRAC Functionality

DIRAC Review (13th December 2005) Stuart K. Paterson 2

Contents

Introduction

DIRAC FunctionalityCommand Line Interfaces

Specialised shells

DIRAC API

Outlook & Improvements

DIRAC Review (13th December 2005) Stuart K. Paterson 3

Introduction

Command Line Interfaces Collection of scripts

Specialised shellsLFC File Catalog Client

Configuration Service Interface

DIRAC API for user production and analysisProvides a very simple mechanism for job submission to the Grid (LCG) as well as standard DIRAC sites (PCs, batch systems)

Tuned for running user jobs

DIRAC Review (13th December 2005) Stuart K. Paterson 4

DIRAC Functionality 1

Effort has been made to group functionality in several powerful APIs

Job API – Workflow description

DIRAC API – Job manipulation and monitoring

Replica Manager – Data management operations

In principle, all DIRAC functionality could be exposed through specialised shell

AliEn approach

DIRAC Review (13th December 2005) Stuart K. Paterson 5

DIRAC Functionality 2

DIRAC scripts directory contains a number of useful command line scripts

Replica Manager operations

Job manipulation

Administrative operations

In principle all DIRAC functionality could be exposed through the command line

LCG Utils approach

DIRAC Review (13th December 2005) Stuart K. Paterson 6

DIRAC Functionality 3

Need to streamline how DIRAC functionality is exposedAPIs – will be maintained and developed Command line – less clear, lots of code duplication

Useful for simple operations, e.g. retrieve LFN locallySpecialised shell – easier to maintain

Can be tailored for usersProvides on-line helpCommand completion etc.

What is the best way to do provide users with access to DIRAC functionality?

DIRAC Review (13th December 2005) Stuart K. Paterson 7

Outlook & Improvements

Explore the use of IPython shell

GUI for DIRAC AdministrationFile Catalog browsing

Configuration Service parameters

Clean up of various scripts in the scripts directoryLeave only ‘user’ level commands

Provide some extra useful commands

e.g. Upload Sandbox to Grid storage