1. The GT 4 GRAM Service Sam Meder (meder@mcs.anl.gov)meder@mcs.anl.gov Middleware Workshop

2. Service: GT4 GRAM l GRAM provides a service interface to compute resources (clusters etc). u Job submission u Staging u Discovery l Not yet available (first alpha at end of month) u URL: http://www.globus.org/toolkit u License: Globus Toolkit Public License (BSD style) u Support: Will become fully supported with the release of GT 4.0 l SOA Model:WS-RF

3. Design Goals l Performance u Scalability u Throughput u (Latency) l Modularity u Staging u Delegation

5. Service Operations (Factory) l WS-ResourceProperties operations l createManagedJob() u Description: u IN: Job description u OUT: EPR for created job resource

6. Service Operations (Service) l WS-ResourceProperties operations l WS-ResourceLifetime operations l WS-BaseNotification NotificationProducer operations l start() u Description: u IN: void u OUT: current state of job

7. Performance vs. GT3 GRAM l Reduced number of roundtrips l Single hosting environment l Modular: What you don’t use you don’t pay for l Event based scheduler/job monitoring

8. What do you use to build your service? (i.e. How ‘standard’ is your service?) NB:A low score means less risk & more mainstream l Widely Implemented Standard Specification (1pt) u SOAP, WSDL, etc (where to start?) l Implemented draft specification (2pt) u WS-Security l Implemented draft specification (3pt) u WS-Resource Framework, WS-Notification l Implemented proposal (4pt) u WS-Addressing l Non-implemented proposal (5pt) u The service itself is a proposal? l Concept (6pt) l TOTAL: (find this a bit silly)

9. Service Dependencies l What else does your service depend on (i.e. external dependencies)? u GT4 Core which in turn depends on a host of third party technologies (RDBMs etc) l What does your implementation depend on? u Languages: Java, C, Perl u Container type: Web container/servlet

10. AAA & Security l What authentication mechanism do you use? u Any provided by GT 4 Security (WS-Security: Username/Password, X.509 (w & w/o proxy certs) and GSI Secure Conversation l What authorisation mechanism do you use? u Any provided by GT 4 Security (identity, gridmap, self, CAS, callout, custom) l What accounting mechanism do you use? u Deferred to scheduler implementation l Does service interaction need to be encrypted? u No, but it can be l Delegation of rights: u Delegation service

11. Exploiting the Service Architecture l What features from your ‘plumbing’ do you use in your service? u Logging u Event notification u Lifetime management u Registry discovery/advertisement u State inspection u (probably more than that)

12. Service Activity l Multiple interaction or single user? u multiple l Throughput (1/per day or 100/per second?) u Depends/unknown l Typical data volume moved in l Typical data volume moved out

13. Service Failure l Required Reliability u Failure semantics? l Positive ack (two phase commit) l Required Persistence u Work never lost? - Yes l Required Availability u Should always be available

14. Required Service Management l Remote access to: u Current state l Job l System