1 / 15

AHM 2005 Automatic Deployment and Interoperability of Grid Services

AHM 2005 Automatic Deployment and Interoperability of Grid Services. G.Kecskemeti, Yonatan Zetuny , G.Terstyanszky, T.Kiss, P.Kacsuk, S. Winter Centre for Parallel Computing Cavendish School of Computer Science University of Westminster y.zetuny@wmin.ac.uk. Presentation Outline.

jin-chen
Télécharger la présentation

AHM 2005 Automatic Deployment and Interoperability of Grid Services

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. AHM 2005Automatic Deployment and Interoperability of Grid Services G.Kecskemeti, Yonatan Zetuny, G.Terstyanszky, T.Kiss, P.Kacsuk, S. Winter Centre for Parallel Computing Cavendish School of Computer Science University of Westminster y.zetuny@wmin.ac.uk www.cpc.wmin.ac.uk

  2. Presentation Outline • Legacy Code Services for the Grid • GEMLCA Concept • GEMLCA Architecture • Current Limitations of GEMLCA • GEMLCA Extension Roadmap • Automatic Deployment Service in GEMLCA • Service Interoperability • Conclusion and Further Work • Useful resources • Summary www.cpc.wmin.ac.uk

  3. Legacy Code Services for the Grid • 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 minimal user effort www.cpc.wmin.ac.uk

  4. The GEMLCA Concept Grid Host Compute GEMLCA Service Environment (GT3/GT4) Servers Client: to apply legacy code Grid service Legacy Code Factory OGSA Container MMJFS Legacy Code Process Legacy Job Manager Code Job (Condor/Fork) Resource manager deploys: a. LC, b. GT3/4, c. GEMLCA Use the integrated P-GRADE/GEMLCA Portal for each case Client: to deploy legacy code Grid service www.cpc.wmin.ac.uk

  5. 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 The GEMLCA Architecture P-GRADE Portal Server www.cpc.wmin.ac.uk

  6. Current Limitations of GEMLCA • Current limitations of GEMLCA: • No Automatic Deployment Service Static mapping of legacy components onto resources. • No Resource Broker • No Information System • No Interoperability Bridge Service Deployment, management and invocation is limited to a single Grid site (security & policy, middleware, etc) www.cpc.wmin.ac.uk

  7. GEMLCA Extension Roadmap (i) • Extending GEMLCA with QoS based brokering and load balancing capabilities. • What are the main barriers? • Deployment: LC services are deployed and mapped manually to Grid resources at workflow construction time. • Interoperability: LC services are deployed and managed within a single Grid environment (single security/policy domain). www.cpc.wmin.ac.uk

  8. GEMLCA with Brokering, Information System and Automatic Deployment Support The GEMLCA Extension Roadmap (ii) Interoperability Bridge www.cpc.wmin.ac.uk

  9. Automatic Deployment Service in GEMLCA (i) • GEMLCA services deployment limitations • Deployment scenarios • Deploying new Grid services • Migrating existing Grid services • The need for an Automatic Deployment Service • Automatic selection services • Grid systems integration • Refining existing services • Deployment Service Architecture • Deployment steps www.cpc.wmin.ac.uk

  10. Figure 3 Automatic Deployment Service Architecture Automatic Deployment Service in GEMLCA (ii) www.cpc.wmin.ac.uk

  11. Service Interoperability (i) • Policy & Security challenges for Grid services interoperability. • Multiple security implementations • Dynamic creation of services • Dynamic trust domain establishment • Policy & Security interoperability scenarios. • Deployment and migration of Grid services • Invocation of Grid services • Interoperability Bridge Service architecture • Negotiator Layer • Analyzer Layer • Classifier Layer • Dispatcher Layer • Bridge Layer www.cpc.wmin.ac.uk

  12. Figure 4 ADS and the x-Service Interoperability Layer Service Interoperability (ii) www.cpc.wmin.ac.uk

  13. Conclusion and Further Work • The industrial need for converting LC applications into Grid services with a minimal user effort. • GEMLCA – The answer for deploying legacy applications on the Grid. • Making GEMLCA a more comprehensive solution for Grid users by developing/extending the following features: • Information system support • Brokering • Load balancing • Automatic deployment and migration of services in a single/multi domain environments. • Implementing of these architectures and integration with GEMLCA is currently in progress. www.cpc.wmin.ac.uk

  14. Useful Resources • GEMLCA URL: • http://www.cpc.wmin.ac.uk/gemlca/ • P-GRADE portal URL: • http://www.lpds.sztaki.hu/pgportal/ • P-GRADE NGS portal URL: • http://www.cpc.wmin.ac.uk/ngsportal/ • P-GRADE NGS GEMLCA portal • http://www.cpc.wmin.ac.uk/ngsportal/gngsportal/ www.cpc.wmin.ac.uk

  15. - Summary –Automatic Deployment and Interoperability of Grid Services • Questions? • Comments? • Suggestions? Contact us: The GEMLCA Team Email: gemlca-discuss@wmin.ac.uk URL: http://www.cpc.wmin.ac.uk/gemlca/ Thank you! www.cpc.wmin.ac.uk

More Related