70 likes | 217 Views
An Overview of OGSA-DAI. Kostas Tourlas tourlas@nesc.ac.uk. Goals for OGSA-DAI. Aim to deliver application mechanisms that: Meet the data requirements of Grid applications Functionality, performance and reliability Reduce development cost of data-centric Grid applications
E N D
An Overview ofOGSA-DAI Kostas Tourlas tourlas@nesc.ac.uk
Goals for OGSA-DAI • Aim to deliver application mechanisms that: • Meet the data requirements of Grid applications • Functionality, performance and reliability • Reduce development cost of data-centric Grid applications • Provide consistent interfaces to data resources • Acceptable and supportable by database providers • Trustable, imposed demand is acceptable, etc. • Provide a standard framework that satisfies standard requirements • A base for developing higher-level services • Data federation • Distributed query processing • Data mining • Data visualisation ReSC Access Grid meeting, May 2005
Core features of OGSA-DAI • An extensible framework for building applications • Supports relational, xml and some files • MySQL, Oracle, DB2, SQL Server, Postgres, XIndice, CSV, EMBL • Supports various delivery options • SOAP, FTP, GridFTP, HTTP, files, email, inter-service • Supports various transforms • XSLT, ZIP, GZip • Supports message level security using X509 • Client Toolkit library for application developers • Comprehensive documentation and tutorials • Fourth production release coming up: • OGSI (GT3), WS-I (OMII) and WS-RF (GT4) flavours • Highly extensible • Strength is in customising out-of-box features ReSC Access Grid meeting, May 2005
Why Use OGSA-DAI • Provides common access view • Regardless of underlying infrastructure • Exposed through Java API or XML • Integrates well with other Grid software • OGSA, WSRF and OMII compliant • Flexibility • OGSA-DAI’s major selling point! • Extensible activity framework • Won’t tie you to storage infrastructure ReSC Access Grid meeting, May 2005
Why You Might Not Want To Use OGSA-DAI • OGSA-DAI slower than direct connection methods • E.g., compared to JDBC • This should improve with time • Scalability issues • Mostly but not completely known • Depend on type of use (e.g. delivery mechanism) • Only planning to use one type of data resource • and don’t care about interoperability with other Grid software • OGSA-DAI an overkill in that case ReSC Access Grid meeting, May 2005
Considerations checklist • Grid-enabled solution required? • Web-service interfaces desirable? • Data access by apps as well as individuals • FTP/GridFTP delivery acceptable? • Mitigates against SOAP limitations • Workflow control required? • More than just single, isolated queries • Diverse data resources? • E.g., databases & flat files • Format translations & transforms required? • E.g., XML to SQL, or between file formats • Java development effort available? • A few weeks, with support from OGSA-DAI team ReSC Access Grid meeting, May 2005
Further info • The OGSA-DAI Project Site: • http://www.ogsadai.org.uk • The DAIS-WG site: • http://forge.gridforum.org/projects/dais-wg/ • OGSA-DAI Users Mailing list • users@ogsadai.org.uk • General discussion on grid DAI matters • Formal support for OGSA-DAI releases • http://www.ogsadai.org.uk/support • support@ogsadai.org.uk • OGSA-DAI training courses ReSC Access Grid meeting, May 2005