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.
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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
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)
A request for s2 is routed to an existing
deployment of the service
A request to s4 cannot be met by an existing deployment of the service
The deployed service remains in place and
can be re-used
- unlike job scheduling
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