1 / 6

OGSA-DAI

OGSA-DAI. Neil Chue Hong (chair), Amy Krause Mario Antonioletti, Malcolm Atkinson, Bartek Dobrzelecki, Ally Hume, Malcolm Illingworth, Mike Jackson, Kostas Karasavvas, Mark Parsons, David Scott, Elias Theocharopoulos Nix McDonnell, Alistair Grant EPCC + NeSC, The University of Edinburgh

vanna
Download Presentation

OGSA-DAI

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. OGSA-DAI Neil Chue Hong (chair), Amy Krause Mario Antonioletti, Malcolm Atkinson, Bartek Dobrzelecki, Ally Hume, Malcolm Illingworth, Mike Jackson, Kostas Karasavvas, Mark Parsons, David Scott, Elias Theocharopoulos Nix McDonnell, Alistair Grant EPCC + NeSC, The University of Edinburgh OMII-UK, OMII-Europe, NextGRID

  2. Goals of the Project • Assist with access and integration of data from separate sources • Provide an extensible framework for executing data-centric workflows • Base functionality to expose data resources (relational and XML databases, flat files) • A collection of components for querying, transformation and delivery of data • Extension points for plugging in new components (activities, resources, security, …) • A Java client toolkit API • Work with user projects

  3. Relationship to Other Globus Projects • WS Core: build on top of • GridFTP: use for delivery of data • Security: use aspects of GT security • MDS: register some information • Introduce: use in future to build services? • WEEP: use in future to provide multi-level workflow?

  4. Current Work • Implementation of completely redesigned version 3.0 – complete code and documentation rewrite. • new service and resource model • APIs to write new web service layers • persistence module • new activity framework • input/output types, invocation, iteration • A revised test architecture

  5. Planned Next Steps • Beta test programme for some users in June. • Public release aimed for late June, • dependent on final testing and beta test findings. • Revise OGSA-DQP for 3.0 and make it easier to deploy • Millions more ideas … (but no effort :-) • Graphical user interfaces • Integration into workflow • Integration with file and replica management • Make use of Globus Usage stats collection mechanism • Continue work with users (NanoCMOS, Astrogrid,…)

  6. Critical Issues • WS-Addressing: useful for us to move to final version (tooling and interop with other middleware) • Axis2: streaming model and MTOM support would be very useful, but worries about maturity (already discussed!) • Documentation: fragments don't work in our opinion :-( although structuring doc by roles does :-) • Communication and Coordination: more notice and a published (moving) roadmap? Feels like decision making is carried out in non-public fora. Who owns and who communicates a decision? When does it get bigger than one particular component? (controversial!) • Existing Infrastructure: still not properly integrated. Wider implications of changes to releases across toolkit. Significant effort required - what benefits do you get apart from testing? (discuss!) • Toolkits, toolkits: how do you easily deploy, configure and integrate some of the parts of Globus? (general!)

More Related