1. OGSA-UK: Putting the users first Steven Newhouse OMII Deputy Director

2. © Motivation Moving from experimentation to production UK: ETF Level 2 Grid  NGS EU: DataGrid  EGEE User driven requirements Need stable grid infrastructure Need stable grid programming model Need stable grid programming interface Happy & productive users are essential! But where are they?

3. © Evolving technology UK e-Science Core Programme (July 2001) Globus (GT2), Condor & SRB Grid & Web Service convergence (Feb. 2002) OGSI: Extending WS into new directions OGSA: Defining an ‘open’ grid services architecture Grid & Web Service re-convergence (Jan. 2004) WS-RF: Refactor OGSI to align with industrial goals Other approaches: WS-I+, WS-Transfer, …

4. © Where are we now? Different approaches in different projects: GT2: DataGrid, ETF, EGEE, … Web Services: MyGrid, AstroGrid, EGEE, … GT3: OGSA-DAI, NeeSGrid, … GT4: GridCast, OGSA-DAI, … No clear consensus on the ‘best’ way… but: Web services provide a good technology base Accessing resources/capability through a service The technology MUST STOP disrupting the user

5. © Web Service Grids: An Evolutionary Approach (WS-I+) WS-I (Core Architecture): XSD, SOAP, WSDL UDDI (Service Discovery) BPEL (Workflow) WS-ReliableMessaging (~ WS-Reliability) WS-Addressing Now W3C activity with WS-Message Delivery Notification: No clear solution NB: An evolving set of specifications

6. © OGSA-UK Considerations Services (the capability within a Grid) Job Submission & Monitoring Data Access File Transfer Technology (the tools to build Grids) WS-I+ WS-RF WS-Transfer & other more experimental approaches

7. © OGSA-WG: Service Groupings Information Services Naming, Service Annotation, … Data Services DIAS, … Execution Management Services JSDL, Brokering, … Context Services Security Services Infrastructure Services Resource Management Services Self-Management Services

8. © OGSA-WG: Profiles Defines how the specifications are used: Ensure interoperability by further specialisation Clarifies the use (or not) of extensibility elements Follow existing GGF document routes: Recommendations track: Proposed: On profile submission Standard: On demonstrated interoperability Informational track: Identify future recommendations For Basic (Infrastructure) & Service (Application)

9. © OGSA-UK: Profiles Infrastructure / Profile Build on WS-I+ Combined WS-Addressing/WS-MessageDelivery WS-Eventing to provide basic notification Services Job Submission: JSDL to specify a job Data Access: DIAS to access data sources Emerging areas: Steering, Brokering

10. © OMII’s contribution to OGSA-UK Work with SB & users directly & through projects GGF: JSDL-WG (GridSAM), SAGA-WG (GeodiseLab) Other: RAHWL (OASIS) Support for WS-I+ & WS-RM/R & WS-E/N FINS, FIRMS, UCL-BPEL, Grimoires Service Implementation GridSAM: Job Submission using JSDL OGSA-DAI: Data Access GeodiseLab: Client Environment

11. © OGSA Client/Server Interaction Application WS-RFWS-I+Other. … Internet WS-RFWS-I+Other. … Client Library Service USERS

12. © Summary GGF: Defining application & service interaction OGSA: Needs to consolidate on community consensus SAGA: Key role in interaction between services & users Focus on delivering useable application capability UK activity can/is/will play a lead Further information: http://www.omii.ac.uk Dissemination  Publications http://www.omii.ac.uk WSG: An Evolutionary Approach State of Grid Users: Conversations with 25 UK e-Science Groups email: s.newhouse@omii.ac.uk