360 likes | 492 Views
Deploying Legacy Applications on Service-oriented Grid. Grid Execution Management for Legacy Code Architecture. Tamas Kiss – Stephen Winter Centre for Parallel Computing University of Westminster kisst@wmin.ac.uk. Presentation Outline. Grid computing – a short introduction
E N D
Deploying Legacy Applications on Service-orientedGrid GridExecutionManagementforLegacyCodeArchitecture Tamas Kiss – Stephen Winter Centre for Parallel Computing University of Westminster kisst@wmin.ac.uk
Presentation Outline • Grid computing – a short introduction • GEMLCA objectives and concept • GEMLCA architecture • Deployment examples • Conclusion – future work • Live demonstration
What is a Grid? • Grid is a collection of computers, storages, special devices, services that can dynamically join and leave the Grid • They are heterogeneous in every aspect • They are geographically distributedandconnected by a wide-area network • They can be accessed on-demand by a set of users
Why use a Grid? • A user has a complex problem that requires many services/resources in order to • reduce computation time • access large databases • access special equipments • collaborate with other users
Grid enabled application runs on Grid machines Collaborative work by the Grid Remote Visualisation in Tokyo Visualisation of data from previous simulations in a Vienna café Remote steering and monitoring from airport Remote Visualisation and steering from Rome Germany USA Grid gateway Simulations launched from London
High-performance systems Client/server systems Network Computing Cluster computing Super- computing High-performance computing Web Services High-throughput computing Generations of Grid Systems Grid Systems 2nd Gen. 1st Gen. Globus 2 Condor 3rd Gen. OGSA/Globus 3/4 G-Lite
OGSA Testbed Grid UK E-science OGSA Testbed • test and evaluate OGSA/GT3 core • evaluate performance, ease of deployment and use, and interoperability University of Portsmouth University of Westminster University of Manchester University of Reading Daresbury, CCLRC University of Southampton SZTAKI (Hungary)
Presentation Outline • Grid computing – a short introduction • GEMLCA objectives and concept • GEMLCA architecture • Deployment examples • Conclusion – future work • Live demonstration
Legacy Applications • Code from the past, maintained because it works • Often supports business critical functions • Not Grid enabled What to do with legacy codes when utilising the Grid? • Bin them and implement Grid enabled applications • Reengineer them • Port them onto the Grid with minimum user effort
GEMLCA – Grid Execution Management for Legacy Code Architecture Objectives • To deploy legacy code applications as Grid services without reengineering the original code and minimal user effort • To create complex Grid workflows where components are legacy code applications • To make these functions available from a Grid Portal GEMLCA GEMLCA PGPortal Integration
3rd generation Grids: (OGSA: GT4, gLite) Web browser Grid Site 1 Desktop 1 Legacy applications Grid Site 2 Web browser Legacy applications Desktop N Legacy applications in service-oriented GridsGemlca – PGrade portal approach: thin client P-GRADE Portal Server
GEMLCA Concept GEMLCA Resource Grid Host Compute Environment (GT3/GT4) Servers Legacy Code Client: to apply legacy code Grid service Process OGSA Container MMJFS Legacy Code Job Job Manager (Condor/Fork) • Resource managerdeploys: • a. LC Use the integrated P-GRADE/GEMLCA Portal in each case Client: to deploy legacy code Grid service • b. GT3/4 • c. GEMLCA
Presentation Outline • Grid computing – a short introduction • GEMLCA objectives and concept • GEMLCA architecture • Deployment examples • Conclusion – future work • Live demonstration
GEMLCA Server Side Grid Host Compute GEMLCA Resource Client Environment (GT3/GT4) Servers Grid Service Client Legacy Code OGSA Container Process MMJFS Legacy Job Manager Code Job (Condor/Fork)
GEMLCA at Server Side Required GEMLCA Resources • GT3/GT4 installed • MMJFS tested • Fork/Condor job manager • Grid FTP running • GEMLCA server package and Tomcat 4 installed • GEMLCA legacy code deployed
GEMLCA at Server Side Legacy Code Deployment
GEMLCA Client SideP-GRADE Portal Grid Host Compute GEMLCA Resource Client Environment (GT3/GT4) Servers Grid Service Client Legacy Code OGSA Container Process MMJFS Legacy Job Manager Code Job (Condor/Fork)
Gemlca Client in a nutshell in the P-GRADE portal Proxy Management
Gemlca Client in a nutshell in the P-GRADE portal Definition of GEMLCA Resources
Gemlca Client in a nutshell in the P-GRADE portal Workflow Creation UoW Sztaki UoR
Gemlca Client in a nutshell in the P-GRADE portal Execution Visualisation
Presentation Outline • Grid computing – a short introduction • GEMLCA objectives and concept • Server side • GEMLCA client – the P-GRADE portal • Deployment examples • Conclusion – future work • Live demonstration
Deployment examples Workflow to analyse road traffic Manhattan road network generator Traffic simulators Analyser
Further examples • GAMESS-UK • Ab initio molecular electronic structure program for performing SCF-, DFT-, and MCSCF-gradient calculations using a variety of techniques for post Hartree-Fock calculations • Developed by Daresbury Laboratory • MultiBayes • Phylogenetic Tree Construction • Developed at the School of Animal and Microbial Sciences at University of Reading
I’m a biologist not a Grid expert Sorry, no additional utilities to be deployed on core resources ??? UK NGS Leeds Oxford • Service reliability • Administration GT2 Manchester Rutherford GEMLCA and Production Grids The problem
User-friendly Web interface UK NGS Leeds Oxford GT2 Manchester Portal server at UoW Rutherford The solution
3rd generation Grids: (OGSA: GT3, WSRF, gLite) Web browser Grid Site 1 Desktop 1 Legacy applications Grid Site 2 Web browser Legacy applications Desktop N Centralised GEMLCA solution P-GRADE Portal Server
interface GEMLCA interface The scenarios Scenario 1 – legacy code repository 3rd party service provider (UoW) GEMLCA resource (GT4 + GEMLCA classes) NGS site1 (GT2) Workflow definition NGS site2 (GT2) P-Grade Portal Central repository legacy code1 legacy code2 …. legacy coden NGS siten (GT2) user job submission
Advantages of Scenario 1 • legacy codes can be uploaded into a central repository and made available for authorised users through a Grid portal • would extend the usability of NGS as users utilise others’ legacy codes stored in the repository • No support needed at the NGS sites
The scenarios Scenario 2 – Legacy code services NGS site1 (GT2) Legacy codes 3rd party service provider (UoW) Workflow definition GEMLCA resource (GT4 + GEMLCA classes) NGS site2 (GT2) Legacy codes P-Grade Portal user NGS siten (GT2) Legacy codes Execution request
Advantages of Scenario 2 • extends the NGS Grid towards the service-oriented Grid concept • Userscan access the legacy codes that are deployed on the NGS sites • NGS system administrators have full control of legacy codes that they deploy on their own resources
Presentation Outline • Grid computing – a short introduction • GEMLCA objectives and concept • GEMLCA architecture • Deployment examples • Conclusion – future work • Live demonstration
Conclusions • GEMLCA enables the deployment of legacy code applications as Grid services without any real user effort. • GEMLCA is integrated with the P-GRADE portal to offer user-friendly development and execution environment. • The integrated GEMLCA P-GRADE solution was successfully demonstrated using the traffic simulator and other applications
Further GEMLCA Development Automatic service deployment, discovery and selection Grid Site 1 Web browser Information Service P-GRADE Portal Server Desktop 1 Broker Legacy applications Grid Site 2 Web browser Abstract workflow Automatic deployer Desktop N Legacy applications
Any questions? Thank you for your attention … Email: gemlca-discuss@cpc.wmin.ac.uk Website: www.cpc.wmin.ac.uk/gemlca