1 / 18

Paul Watson & Chris Fowler School of Computing Science University of Newcastle

Dynasoar Dynamic Deployment of Web Services on a Grid or the Internet or Why it’s good to be Jobless. Paul Watson & Chris Fowler School of Computing Science University of Newcastle.

irma-nieves
Download Presentation

Paul Watson & Chris Fowler School of Computing Science University of Newcastle

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. DynasoarDynamic Deployment of Web Services on a Grid or the InternetorWhy it’s good to be Jobless Paul Watson & Chris Fowler School of Computing Science University of Newcastle The Dynasoar team: Chris Fowler, Paul Watson, Charles Kubicek, Arijit Mukherjee, John Colquhoun, Savas Parastatidis, Mark Hewitt The GridShed team: Isi Mitrani, Jennie Palmer, Rob Smith, Paul McKee (BT) & Mike Fisher (BT)

  2. Why Jobs & Services? • Grid applications are being built from Web Services • If the computational requirements can’t be met by the service hosting environment then a job must be created • Do we need both jobs and services? • Dynasoar • a service-only approach to building grid applications • an infrastructure for the dynamic deployment of web services

  3. Web Services

  4. Dynasoar Components • Web Service Provider (WSP) • exposes service endpoints • accepts the incoming SOAP message sent to the endpoint • chooses a Host Provider and passes the message to it • holds a copy of service code • Host Provider (HP) • manages computational resources (e.g. a cluster or a grid) • accepts the message from the WSP • dynamically deploys the service if necessary • processes the message and returns any response Consumer

  5. Routing to an Existing Service Deployment A request for s2 is routed to an existing deployment of the service

  6. Dynamic service deployment A request to s4 cannot be met by an existing deployment of the service R The deployed service remains in place and can be re-used - unlike job scheduling

  7. Dynasoar Advantages • Simplicity: just services • Efficiency: a deployed service can process many messages • important if cost of deployment is high… e.g. VMs • Support a range of new e-science/ e-business models: • defining the interactions between the major components allows them to be distributed in a variety of ways

  8. Dynamic Outsourcing • Biocorp are experts in writing bioinformatics services • They don’t want to manage their own compute resources • Therefore, they use Hosting Inc to process messages sent to their services • In e-science, BioCorp could be a research group writing specialist e-science services, and Hosting Inc the NGS

  9. The National Grid Service as a Host Provider • A researcher writes their own services but does not have sufficient local compute resources • They deploy a local WSP, and configure it so that it sends messages to the National Grid Service • their services are then transparently deployed on the NGS as required

  10. A Marketplace for e-Science Local Campus Grid National Grid Service

  11. Moving Computation to Data • In many e-science applications analysis services operate on data extracted from a data store (e.g. OGSA-DAI, SRB…) • often large amounts of data are transferred • this may severely limit the performance

  12. Moving Computation to Data • The data owner provides compute resources close to a database • Researchers can write services and deploy them on their own WSP • The service is dynamically deployed close to the database when requests are sent to the WSP

  13. Results for Deploying a Service Close to a Database

  14. Tripartite Security Model The 3 actors can define policies (XACML) that Dynasoar enforces at run-time, e.g…. WSP: only use Host Providers trusted to not re-use the deployed service without payment HP: accept only messages from WSPs trusted to not send malicious code C: only send the message to a HP trusted not to look at the contents

  15. Current Implementation GridShed Cluster Management

  16. New Host Provider Architecture • Layer as high-level infrastructure over lower level grid fabric • Use OMII Job Submission and Monitoring Service to provide stable interface to different underlying fabrics • Newcastle Grid (Condor), National Grid Service, local clusters,….

  17. Current Work • Deploying Services in Virtual Machines • can encapsulate a complex service implementation environment • Use of QoS to enhance decisions on where to deploy a service • Dynamic database deployment • ogsa-dai, ogsa-dqp

  18. Conclusions • Grid applications can be built entirely from services • jobless grid computing • simpler conceptual model • performance improvements due to sharing the cost of service deployment over multiple requests • Dynasoar is built as a high-level infrastructure on top of existing grid fabrics • Separating the Web Service Provider from the Host Provider – with a well-defined interface – opens up a range of e-science/ e-business models • Demo available at the North East Regional e-Science Centre stand

More Related