Tom Sugden EPCC OGSA-DAI Future Directions OGSA-DAI User's Forum GridWorld 2006, Washington DC 14 September 2006

Whats next? OGSA-DAI WSI 3.0 and OGSA-DAI WSRF 3.0 Due in March 2007 –Release schedule is now determined by functionality –No longer every 6 months Main efforts are focussed on: –Multi-Resource Requests data integration capabilities –Expanded Resource Model standardised, separate concerns –Persistence robustness, dynamic reconfiguration –Clustering scalability, robustness –New Activity Framework simpler, more powerful –Monitoring Framework logging, auditing, status reporting

14 September 2006http:// Multi-Resource Requests Data Request Execution Service Data Request Execution Resource Client Data Resource Data Data Resource Data Data Resource Data One Two Three Perform Document sqlQuery(One) sqlQuery(Two) sqlQuery(Three) integrateData deliverToGridFTP Client-server interaction Service-resource association Resource-resource association Resource-database association

14 September 2006http:// Expanded Resource Model Data Resource Session Data Data Resource Data Data Resource Data Session Request Client Data Request Execution Service Data Resource Information Service Session Management Service Request Management Service Data Request Execution Resource

14 September 2006http:// Persistence Database Data Request Execution Resource Client Data Resource Session Request OGSA-DAI Server Data Resource Data Service and Resource Configuration and State Data Request Execution Service Data Resource Information Service Session Management Service Request Management Service

14 September 2006http:// Persistence Allows configuration and state to persist between container shutdowns/crashes Persistence API –File-based implementation for backwards compatibility –Relational implementation for compatibility with common databases –Extensibility point Caching to reduce overheads of communication with persistence database Some resources are sticky –Stored in memory and not persisted –Only accessible via server that created them –e.g. data sources and sinks

14 September 2006http:// Clustering Persistence Database Client OGSA-DAI cluster Front-end Router

14 September 2006http:// Scalability and Robustness Release 3 will afford future provision of clustering and load balancing Clustered OGSA-DAI servers –Different JVM –Different machine Load balancer –Simple e.g. round robin –Complex e.g. decide on basis of current load of each server Scalable –Increases number of requests that OGSA-DAI can handle concurrently Robust –Seamless operation in the face of errors e.g. server failures Sticky sessions and resources –Session and resource state may be non-serializable or be lightweight in- memory components

14 September 2006http:// New Activity Framework Data Resource Data Data Resource Data Data Resource Data Request One Two Three Client Data Request Execution Service Data Request Execution Resource sqlQuery(One) sqlQuery(Two) sqlQuery(Three) merge federatedQuery webRowSet deliverToFTP Spawned Activities Perform Document Activities

14 September 2006http:// New Activity Framework Concurrent processing model –Buffering to improve pipeline performance Activities may spawn child activities –Greater encapsulation, simpler for the end user Flexible inputs/outputs (literals, pipes, sessions) –More powerful pipelining and inter-request communication Intermediate request cancellation –Activities are interruptible Asynchronous status reporting –Activity status no longer swallowed Extension interfaces –Activities have their own specific concerns

14 September 2006http:// Simplified Activity Interface All activities must implement the Activity interface An abstract ActivityBase class is provided which implements common functionality Concrete classes implement the process() method

14 September 2006http:// Activity Extension Interfaces Optional interfaces for activities with specific requirements –Activities that access data resources –Activities that create new activities –Activities that interact with sessions –etc

14 September 2006http:// The Monitoring Framework Request sqlQuery(One) sqlQuery(Two) sqlQuery(Three) merge federatedQuery webRowSet deliverToFTP Spawned Activities Activity Status Reporter Event Logger Auditor Events are dispatched to listeners

14 September 2006http:// The Monitoring Framework Defines Event classes and Listener interfaces The Activity Framework dispatches events Activity Listeners receive activity events: –Activity initialised –Activity processing –Error occurred –Processing completed –Custom events … Pipe Listeners receive pipe events: –Block produced –Block consumed Implementations to support logging, auditing, etc.

14 September 2006http:// Other Planned Features Security Message-level + Transport-level including delegation New Releases OGSA-DAIR OGSA-DAIX OGSA-DQP Registries Guidelines for Grimoires and Service Groups

14 September 2006http:// Other Planned Features Support for registries –Guidelines on how to best use standard registries (e.g. GRIMOIRES or GT4 ServiceGroups) and tools to help you do so within OGSA-DAI Improved support for message-level and transport- level security including delegation Concurrent or closely-following releases of –Implementations of WS-DAIR and WS-DAIX specs –Refactored OGSA-DQP with a Java-compliant query compiler and which runs under Linux, Solaris or Windows

14 September 2006http:// Further Information The OGSA-DAI project site – The DAIS-WG site – OGSA-DAI users mailing list –General discussion on OGSA-DAI, data and the grid Formal support for OGSA-DAI releases – OGSA-DAI training courses