1. ETF and Level 2 Grid UK e-Science Grid Now up and running! Rob Allan David Boyd

2. e-Science Grid – Level 2 deployment A Globus GT2-based Grid infrastructure with resources, middleware and applications from the e-Science Centres and CCLRC * ETF has created an intensive working group with common goals and vision. No “political” problems - strong focus on technical issues * Leading Grid deployment worldwide and showing by example what can be achieved on the European level Key points ● Large pool of heterogeneous resources integrated ● Support from GSC in deploying and maintaining GT2 and MDS infrastructure ● Middleware from Centre developments deployed ● Real applications and e-Science project users starting to generate scientific results ● Tasks being identified for next phase

3. Project leaders, work packages and results WPNameLeaderDeputiesResults delivered 0Project management Rob AllanAlistair Mills David Boyd Level 1 paper, Level 2 paper, L2G plan v1, L2G plan v2 1Grid middlewareJon Giddy (Nick Hill) Andy Richards Middleware spec, s/w config notes, GT2 installed infrastructure 2Information services Rob AllanDharmesh Chohan MDS installed infrastructure, InfoPortal, XML db, Web services 3User authentication Alistair MillsJens JensenCA, CPS, RA network, User and server certificates 4User management and accounting Steven Newhouse Marko Krznaric VOM prototype deployed 5Grid securityJon HillierAndy Richards Firewalls paper, security papers, secure firewalls IP database 6Grid platform support Alistair MillsRon FowlerSupport from GSC, monitoring test results 7Integration testing David BakerMark McKeown GITS scripts, XML db, Web services 8Grid applicationsSimon CoxDavid BakerApplications portfolio

4. What resources have we used? Site VO-name Key resources Belfast BeSC MP Sun Cambridge CeSC Pentium cluster, Condor pool Cardiff WeSC MP Sun, Condor pool, MP SGI systems Daresbury DL-eSC MP Athlon, alpha cluster, IBM SP, HPCx (soon) Edinburgh NeSC EdinburghIBM p690 (soon) Glasgow NeSC GlasgowSun E450 London LeSC Condor pool, Pentium clusters, Sun MP Manchester ESNW CSAR resources, workstations, Sony PS2 Newcastle NEReSCPentium cluster Oxford OeSCworkstations Rutherford RAL-eSC Athlon cluster, HP cluster Southampton University of Large and smaller pentium clusters Southampton See http://esc.dl.ac.uk/InfoPortal Key remaining tasks: increase ease of access, address common usage policy, accounting and remaining firewall issues, deploy distributed s/w maintenance, version control and operational monitoring tools.

5. What tools have we developed and deployed? Lead site Client or management tool Daresbury InfoPortal, XML resource/application/user database, related Web services London VOM authorisation management server and client tools Oxford Secure firewall IP database RAL CA, monitoring tools, GridSite for project management, Website S’ton/ManchGITS integration test script, XML database, related Web services CambridgeCondor-G task farming tool Cardiff Nimrod-G task-farming client tool Daresbury HPCPortal GT2-based client tool for secure Grid access EdinburghSunDCG TOG (Transfer-queue Over Globus) LondonEPIC, ICENI tools Manchester RealityGrid-Lite steering and visualisation (with SGI VizServer) S’ton GEODISE Computational Toolbox (with MatLab and Java CoG) Key remaining tasks: document and increase use of these tools by e-Science projects

6. What applications and users are we supporting? Lead site Application Users Participating sites Belfast R-MatrixAstronomersCamb, Cardiff, London, Manch, Oxf, S’ton - electron-atom interactions in astrophysics and plasma physics Daresbury DL_POLY e-Minerals Cambridge, Manchester, Belfast - molecular dynamics simulations Cambridge Monte Carlo e-Minerals DL, RAL, S’ton, Oxford, Newcastle - ionic diffusion through radiation damaged crystal structures CardiffFortran appAstrophysicsManchester - simulation code distributed using Nimrod/G Glasgow BLASTBiologistsGlasgow, Belfast, RAL - genome sequence searching on fragment of E-Coli London GENIEGENIEReading, Southampton - Integrated Earth Systems Model for climate modelling parameter studies Manchester Lattice Boltzmann RealityGrid London - remote steering and visualisation of condensed matter simulations S’ton GEODISEEngineersOxford, Belfast, Cambridge, DL, RAL, London - structural engineering optimisation, e.g. with NASA or Rolls-Royce Key remaining tasks: increase number of applications and users

7. What we found Issues –Job monitoring and debugging difficult –Need to open specific ports –Poor performance of job schedulers with many jobs –Software version incompatibility –Globus interface problems with job managers –Availability of site licences for software –Effort required to populate resource information services –Lot of work to get accounts set up at remote sites –Globus version incompatibilities –Ensuring enough local resources (eg filespace) available to run jobs However, in spite of these difficulties, everyone got their applications to run successfully over the Grid –“the infrastructure has proven to be robust”

8. Who was involved? The main contributors to these applications tests were: –Rob Allan (CLRC, DL) –David Baker, Simon Cox, Hakki Eres (S’ton) –Jonathan Giddy (Cardiff) –Terry Harmer (Belfast) –Mark Hayes (Cambridge) –Steven Newhouse (London) –Robin Pinning (Manchester) –John Watt (Glasgow)

9. e-Science Grid – towards Level 3 Tasks for period Easter-October 2003 (subject to approval) ● Enhance production GT2-based Grid, addressing tasks highlighted above ● Improve basic infrastructure operation and management tools ● Include OGSI/ GT3-based development Grid and support for migration ● Grid retreat (NeSC, summer 2003) to identify additional tools/ middleware to deploy from Centres ● Add more participating sites, e.g. Centres of Excellence, JISC resources ● Add databases and instruments (workshop at RAL, June 2003) ● Address key longer-term challenges and fill gaps based on recent Gap Analysis by Core Programme ● All Hands meeting in September ● Increasing collaboration with European/ US/ Asia partners including EGEE project in FP6 What more should we be doing?