The OMII Perspective on Grid and Web Services At the University of Southampton

April 2004UK OMII2 Presentation overview OMII in context Objective, need, people and funding Roles of the OMII OMII position on grid and web services

April 2004UK OMII3 Objective of the OMII The OMII will become the source for reliable, interoperable, open-source Grid middleware => Success is measured by people using our software infrastructure and services

April 2004UK OMII4 Time to deliver “To ensure that middleware becomes production-quality, part of the infrastructure, and acquires sufficient functionality quickly enough to meet the expectations of the emerging grid user communities” Paul Messina

April 2004UK OMII5 Why do we need the OMII? Key Issue: Software is Infrastructure; we need to develop and maintain it accordingly If we want e-Infrastructure to be an enabling technology for research and commerce, we have treat software as infrastructure just as we do hardware and networks. This implies emphasis on robustness, functionality, evolution, and persistence (code and standards)

April 2004UK OMII6 Problems in moving prototype middleware to “infrastructure” Research projects are not funded to do regression testing, configuration, and QA required to create production quality middleware Rule of thumb is that it requires at least 10 times more effort to take proof-of-concept research software to production-quality Additionally, interoperability is a key issue for Grid Middleware

April 2004UK OMII7 Achieving the Vision Manage a repository of grid middleware Graded, tested, re-engineered software Primary contribution from UK e-science programme Establish and coordinate a managed grid middleware research programme > £3m targeted funding over 3 yrs First round proposals due end May Deliver reliable, interoperable, grid middleware infrastructure Integration, regression tested (additive model)

April 2004UK OMII8 Key objectives for first 9 months Publish Roadmap (end Feb) Now available at Initiate first round funding under managed programme (initiate end Feb) Managed program call now available at Establish OMII repository (end March) Deliver first OMII release (Sept/Oct)

April 2004UK OMII9 Who’s Involved? Proposal team Southampton University, IT Innovation, IBM Industrial Partners

April 2004UK OMII10 Success criteria People will use our software if It’s easy to install, Reliable, Lightweight. Interoperable with other infrastructures, etc… AND It uses familiar tooling It uses a familiar programming model Application programmers see commercial gain => There must be a low entry barrier

April 2004UK OMII11 Users choice Unknown with regards to OGSI Resounding “YES” to Web Services Definitely SOAP, WSDL and UDDI Probably “YES” to WS-Security and WS- Addressing Jury out on higher level web services and frameworks like WS-RF Is this going to change or disappear?

April 2004UK OMII12 OMII View Advised by TAB and SC to adopt conservative web service approach Still seeking guidance We will only adopt agreed “standards” or “specifications” that are universally agreed upon Need a formal OGSA view of the world and identified web services required to support this view

April 2004UK OMII13 OMII Infrastructure and interoperability OMII will supply a framework capable of hosting WS-I / WS-RF services OMII framework will interoperate with other WS-I / WS-RF frameworks (e.g., GT4, EGEE, etc) WS-I 1.0 comprises SOAP 1.1, WSDL 1.1 and UDDI 2.04 plus other open standards

April 2004UK OMII14 OMII Components Sourced from community and through the managed programme Component types: E.g., Workflow agreed to open standards Component Interoperability: components provide the means to construct bespoke grid services that interoperate (through open standards) with grid services supplied by other major suppliers Components will operate in various WS-I / WS-RF frameworks

April 2004UK OMII15 OMII added value OMII will publish exemplary Grid applications that can run on WS-I / WS-RF compliant infrastructures Develop tutorials and training for infrastructure and components in conjunction with NeSC and GOC OMII software will be open source.

April 2004UK OMII16 OMII in Context Infrastructure Costs £3M Research & Development Programme (Themed Calls - £3.5M) RC Project1 Core Project 1 RC Project 2 Core Project 2 ETC …. OMII Steering Committee (OMIISC) Director SOFTWARE REPOSITORY OPEN SOURCE ETC …. ETC …. ETC …. OMII Software Engineering Team Projects performed Within and outside Centre OMII Technical Advisory Board (OMIITAB)

April 2004UK OMII17 Other OMII Influences Grid Operations Centre and NeSC Support and training role UK ETF and NGS Deployment of components and frameworks