UK e-Science Town Meeting

1
UK e-Science Town Meeting

• Defining the Next Level of Services for e-Science
• - An OGSA-UK Paper?

2
Architecture of a Grid
Discipline Specific Portals andScientific
Workflow Management Systems
Applications Simulations, Data Analysis,
etc. Toolkits Visualization, Data
Publication/Subscription, etc.
Grid Common Services Standardized Services and
Resources Interfaces
Collaboration and Remote Instrument Services
Grid Information Service
UniformResourceAccess
Co-Scheduling
Network Cache
Authentication Authorization
Security Services
Communication Services
Global Queuing
Global EventServices
Data Cataloguing
Uniform Data Access
Fault Management
Monitoring
Brokering
Auditing
Globus services
clusters
Distributed Resources
national supercomputer facilities
tertiary storage
national user facilities
Condor pools
networkcaches
High-speed Networks and Communications Services
3
OGSA is an SOA
Uses Cases, Processes Applications
HPC HTC
ERP, CRM, SC
BI BA
OGSA Services
Resource Mgt.
Configuration Provisioning
Security
Distributed Services
Data Information
Self-Mgt.
Execution Mgt.
WS-Infrastructure
Networked Resources
Storage
Network
Compute
4
The Web Services Magic Bullet
Company C (.Net)
5
A Problem?

• IBM, HP, Fujitsu
• WS-ResourceFramework
• WS-Notification
• WS-DistributedManagement
• Microsoft,
• WS-Transfer, WS-Enumeration
• WS-Eventing
• WS-Management

6
How WS-Resource relates to OGSA
WS-Resource Framework as an evolution of OGSI
Applications
OGSA Architected Services
OGSI Open Grid Services Infrastructure
7
Web Service Grids An Evolutionary Approach
WS-I
8
Stateful Interactions

• State appears in almost all applications
• Data in a purchase order
• Current usage agreement for resources on a grid
• Metrics associated with work load on a Web server
• There are (at least) two approaches to specifying
  state for an e-Science application
• WSRF
• Uses metadata of a resource to identify state
  associated with particular session
• WS-I
• Pure Web Service leaves state specification
  with the application e.g. put a context in the
  SOAP body

9
Interoperability?

• Application Programming Interfaces (APIs)
• Define high level functionalities and specify
  interfaces to particular libraries, languages and
  hosting environments
• Interoperability issues not addressed
• Specifications and Standards
• High level services built on top of universally
  agreed specifications/standards
• Profiles
• WS-I use profiles to describe how to use existing
  specifications
• OGSA defining profiles for specific functionality

10
Agenda (am)

• 10.30 Introduction Tony Hey
• OGSA-UK Session
• 10.40 Andrew Grimshaw (GGF)
• 11.00 Steven Newhouse (OMII)
• 11.20 Zhiwei Xu (CN Grid)
• 11.40 Fabrizio Gagliardi (CERN)
• 12.00 Geoffrey Fox (Indiana)
• 12.20 Malcolm Atkinson (OGSA-DAI)
• 12.40 Lunch

11
Agenda (pm)

• 13.40 Open Discussion on OGSA-UK
• GGF-OGSA Session
• 14.40 Mark Linesch (GGF)
• 15.00 Marvin Theimer (Microsoft)
• 15.10 Panel Mark Linesch, Marvin
• Theimer, Andrew Grimshaw,
• Zhiwei Xu, Fabrizio Gagliardi,
• Geoffrey Fox, Malcolm Atkinson
• 16.20 Summary and Close Tony Hey