180 likes | 355 Views
Dynasoar Dynamic Deployment of Web Services on a Grid or the Internet or Why it’s good to be Jobless. Paul Watson School of Computing Science University of Newcastle.
E N D
DynasoarDynamic Deployment of Web Services on a Grid or the InternetorWhy it’s good to be Jobless Paul Watson 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, Paul McKee (BT) & Mike Fisher (BT)
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
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
Routing to an Existing Service Deployment A request for s2 is routed to an existing deployment of the service
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
Dynasoar Advantages • Simplicity: just services • Efficiency: a deployed service can process many messages • 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
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
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
A Marketplace for Matching Web Service Providers to Host Providers
A Marketplace for e-Science Local Campus Grid National Grid Service
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
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
Current Implementation GridShed Cluster Management
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,….
Current Work • Exploring Virtual Machines as a general service deployment mechanism • Freeze services and their environments in a VM • Store in Service Store • Dynamically Deploy as required • Use of QoS to enhance decisions on where to deploy a service • Exploring tripartite security model • Consumer, Web Service Provider and Host Provider express policies that are enforced at run-time • A HP may only accept messages from WSPs that it trusts to not send malicious code • A WSP may only deploy services on HPs it trusts won’t use the service without paying • Dynamic database deployment • ogsa-dai, ogsa-dqp
Conclusions • It is possible to build grid applications entirely from services • jobless grid computing • simpler conceptual model • performance improvements due to sharing the cost of service deployment over multiple requests • Separating the Web Service Provider from the Host Provider opens a range of deployment options • Dynasoar can be built as a high-level infrastructure on top of existing grid fabrics • Ongoing work on VMs, QoS, Security, dynamic db deployment • Technical Report on-line: Newcastle CS-TR-890… • http://www.cs.ncl.ac.uk/research/pubs/trs/papers/890.pdf
Thanks • The Dynasoar team • Chris Fowler, Charles Kubicek, Arijit Mukherjee, John Colquhoun, Savas Parastatidis, Mark Hewitt • The GridShed team • Isi Mitrani, Jennie Palmer • BT • Paul McKee & Mike Fisher • This work is supported by the DTI, EPSRC, Core e-Science Programme & CodeWorks