17 March 2008Standards for Interoperable Grids 1 Data Management Standards for Interoperable Grids: Experience from NextGRID and OMII-Europe Clive Davenhall.

Slides:



Advertisements
Similar presentations
Bulk Data Copy Generalization Some DMI/JSDL overlap (this indeed might be out of scope of JSDL) Extensibility options / possibly some new requirements.
Advertisements

March 6 th, 2009 OGF 25 Unicore 6 and IPv6 readiness and IPv6 readiness
Genesis II Open Source, OGSA Implementation Genesis II: Mapping Grids into the Local File System: Access, RNS, and ByteIO Andrew Grimshaw Genesis II Team.
© 2007 Open Grid Forum Data Management Challenge - The View from OGF OGF22 – February 28, 2008 Cambridge, MA, USA Erwin Laure David E. Martin Data Area.
Fujitsu Laboratories of Europe © 2004 What is a (Grid) Resource? Dr. David Snelling Fujitsu Laboratories of Europe W3C TAG - Edinburgh September 20, 2005.
WS-JDML: A Web Service Interface for Job Submission and Monitoring Stephen M C Gough William Lee London e-Science Centre Department of Computing, Imperial.
1 OGSA-DAI Platform Dependencies Malcolm Atkinson for OMII SC 18 th January 2005.
17 March 2008Standards for Interoperable Grids 1 Job Execution Standards for Interoperable Grids: Experience from NextGRID and OMII-Europe Clive Davenhall.
Service Description: WSDL COMP6017 Topics on Web Services Dr Nicholas Gibbins –
An Introduction to Web Services Sriram Krishnan, Ph.D.
BiodiversityWorld GRID Workshop NeSC, Edinburgh – 30 June and 1 July 2005 Resource wrappers, web services, grid services Jaspreet Singh School of Computer.
1 Introduction to XML. XML eXtensible implies that users define tag content Markup implies it is a coded document Language implies it is a metalanguage.
4a.1 Grid Computing Standards ITCS 4010 Grid Computing, 2005, UNC-Charlotte, B. Wilkinson, slides 4a.
NextGRID & OGSA Data Architectures: Example Scenarios Stephen Davey, NeSC, UK ISSGC06 Summer School, Ischia, Italy 12 th July 2006.
1 An Introduction to OGSA-DAI Konstantinos Karasavvas 13 th September 2005.
CSE 636 Data Integration Web Services.
The Open Grid Service Architecture (OGSA) Standard for Grid Computing Prepared by: Haoliang Robin Yu.
© 2008 Open Grid Forum Grid Standards Realizing Basic Grid Use Cases Using Existing Standards and Profiles.
Possible Architectural Principles for OGSA-UK and other Grids UK e-Science Core Programme Town Meeting London Monday 31st January 2005 “Defining the next.
T Network Application Frameworks and XML Web Services and WSDL Sasu Tarkoma Based on slides by Pekka Nikander.
Data Management Kelly Clynes Caitlin Minteer. Agenda Globus Toolkit Basic Data Management Systems Overview of Data Management Data Movement Grid FTP Reliable.
OPEN GRID SERVICES ARCHITECTURE AND GLOBUS TOOLKIT 4
GT Components. Globus Toolkit A “toolkit” of services and packages for creating the basic grid computing infrastructure Higher level tools added to this.
Grid-enabling OGC Web Services Andrew Woolf, Arif Shaon STFC e-Science Centre Rutherford Appleton Lab.
Grid Resource Allocation and Management (GRAM) Execution management Execution management –Deployment, scheduling and monitoring Community Scheduler Framework.
© 2008 Open Grid Forum Independent Software Vendor (ISV) Remote Computing Primer Steven Newhouse.
Application code Registry 1 Alignment of R-GMA with developments in the Open Grid Services Architecture (OGSA) is advancing. The existing Servlets and.
Andrew Jones Interop. in changing infrastructure BiodiversityWorld GRID Workshop NeSC, Edinburgh – 30 June and 1 July Design Decisions Interoperability.
XML Web Services Architecture Siddharth Ruchandani CS 6362 – SW Architecture & Design Summer /11/05.
© 2006 Open Grid Forum DAIS-WG Status Report Implementations and Interoperability Testing Steven Lynden AIST.
Web: Minimal Metadata for Data Services Through DIALOGUE Neil Chue Hong AHM2007.
Grids - the near future Mark Hayes NIEeS Summer School 2003.
An information and monitoring system for static and dynamic information about grid resources, applications, networks … RDBMS Servlet aware of API during.
OGSA-DAI.
Grid Services I - Concepts
INFSO-RI Enabling Grids for E-sciencE OGSA DAI Data Access and Integration Marek Ciglan Institute of Informatics, Slovac Academy.
State Key Laboratory of Resources and Environmental Information System China Integration of Grid Service and Web Processing Service Gao Ang State Key Laboratory.
Mike Jackson EPCC OGSA-DAI Architecture + Extensibility OGSA-DAI Tutorial GGF17, Tokyo.
Prof S.Ramachandram Dept of CSE,UCE Osmania University
On Using BPEL Extensibility to Implement OGSI and WSRF Grid Workflows Aleksander Slomiski Presented by Onyeka Ezenwoye CIS Advanced Topics in Software.
Condor Services for the Global Grid: Interoperability between OGSA and Condor Clovis Chapman 1, Paul Wilson 2, Todd Tannenbaum 3, Matthew Farrellee 3,
Satisfying Requirements BPF for DRA shall address: –DAQ Environment (Eclipse RCP): Gumtree ISEE workbench integration; –Design Composing and Configurability,
© 2004 IBM Corporation WS-ResourceFramework Service Groups Tom Maguire.
INFSO-RI Enabling Grids for E-sciencE NPM Mediator JRA4 F2F, Edinburgh, July 2005 Alistair K Phipps University.
© 2005 Global Grid Forum The information contained herein is subject to change without notice Leading the pervasive adoption of grid computing for research.
© 2006 Open Grid Forum BES, HPC, JSDL and GLUE Profiling OGF 23, Barcelona, Tuesday 16 October 2007.
© 2005 Global Grid Forum The information contained herein is subject to change without notice Leading the pervasive adoption of grid computing for research.
OGSA-DAI.
A service Oriented Architecture & Web Service Technology.
ISC321 Database Systems I Chapter 2: Overview of Database Languages and Architectures Fall 2015 Dr. Abdullah Almutairi.
Amy Krause EPCC OGSA-DAI An Overview OGSA-DAI on OMII 2.0 OMII The Open Middleware Infrastructure Institute NeSC,
ByteIO Discussion OGSA F2F, London 26 May To Recap … Why are we here? –Many OGSA WGs have a need for a simple way of reading and writing blocks.
WS-Resource Framework University of Amsterdam
Leading the pervasive adoption of grid computing for research and industry © 2006 Global Grid Forum The information contained herein is subject to change.
OGF24 15 September 2008 Data Area Overview Erwin Laure David E. Martin Data Area Directors.
Data services on the NGS
Sabri Kızanlık Ural Emekçi
T Network Application Frameworks and XML Web Services and WSDL Sasu Tarkoma Based on slides by Pekka Nikander.
The Open Grid Service Architecture (OGSA) Standard for Grid Computing
The OGSA Data Architecture
Unicore and the EM Profile
Norman Paton University of Manchester
Status and Future Steps
Chairs: Mario Antonioletti, EPCC Shahbaz Memon, FZJ Ravi Madduri, UoC
Unicore and Standards Dr. David Snelling
OGF19 – Chapel Hill, NC, USA 30 January 2007
RELATIONAL GRID MONITORING ARCHITECHTURE
Introduction to OGF Standards
OGSA Data Architecture
Presentation transcript:

17 March 2008Standards for Interoperable Grids 1 Data Management Standards for Interoperable Grids: Experience from NextGRID and OMII-Europe Clive Davenhall National e-Science Centre, University of Edinburgh

Standards for Interoperable Grids2 Data Management: Overview Manipulation and management of data. Typically including:  Processing  Transfer  Storage  Access

Standards for Interoperable Grids3 Data Management: Overview Manipulation and management of data. Typically including:  Processing Job execution, BES, JSDL  Transfer  Storage  Access

Standards for Interoperable Grids4 OGSA Standards There are a number of OGSA data management standards: DMI: data transfer. ByteIO: data access (file-like), data transfer. WS-DAI: data access (database-like). Can be used individually or in concert with other OGSA standards.

Standards for Interoperable Grids5 OGSA-DMI DMI: Data Management Interface. Not yet a specification; still a draft:  currently receiving public comments,  completion is imminent. A standard mechanism for moving data between locations:  from a source of data,  to a sink (or destination) of data.

Standards for Interoperable Grids6 OGSA-DMI Architecture A standard structure or interface  Various resources can use and interoperate. Support a variety of protocols for the actual data transfer:  GridFTP, file access, OGSA-ByteIO, SRB. Supports ‘third party’ transfers,  a superintending process initiates a transfer from a remote source to a remote sink. Only concerned with moving bytes from the source to the sink:  not concerned with the semantics or structure of the data,  though future versions might be.

Standards for Interoperable Grids7 Port Types DMI: a mechanism for scheduling and managing data transfers. Provides two port types. Uses the factory pattern. DTF: Data Transfer Factory  Client invokes a DTF to create a DTI. DTI: Data Transfer Instance  Service created to perform a specific transfer.

Standards for Interoperable Grids8 DTI Operations A DTI (Data Transfer Instance) will support the following operations:  Start  Activate  Stop  Resume  Suspend  GetState  GetInstanceAttributeDocument

Standards for Interoperable Grids9 Sources and Sinks Source:  Emits an ordered sequence of bytes. Sink:  Receives an ordered sequence of bytes. For a resource to act as a source or sink in a DMI transfer it must:  Provide suitable services to send or receive data.  Furnish a list of protocols that it can use. Information about how data are to be sent or received is encapsulated in a DEPR (Data Endpoint Reference).

Standards for Interoperable Grids10 DEPR DEPR: Data Endpoint Reference. Encapsulates all the information about:  How data in a source are to be accessed.  How data sent to a sink are to be received. Includes all the transport protocols supported by a source or sink. Contains endpoint references to access the data. In future versions these endpoint references will use WS-Addressing.

Standards for Interoperable Grids11 NextGRID Recommendations Resources should be modelled as WS- resources. Transfers must be implemented as ‘Logical Data Transfers’  (the most flexible of several options available). Prescribes a mechanism to query the protocols available to a source or sink. OGSA-ByteIO must be one of the protocols available to both the source and sink.

Standards for Interoperable Grids12 OGSA Data Management Standards DMI: data transfer. ByteIO: data access (file-like), data transfer. WS-DAI: data access (database-like).

Standards for Interoperable Grids13 OGSA ByteIO POSIX-like access to remote resources. The remote resource can be any source of data:  files,  sensors,  live-data streams,  etc… Aims to provide access transparency.

Standards for Interoperable Grids14 Mapping to Web Services Core OGSA ByteIO Specification  Independent of any basic profile. ByteIO OGSA WSRF Basic Profile Rendering  Mapping to WSRF Basic Profile. Currently WSRF is the only mapping. Others are anticipated.

Standards for Interoperable Grids15 ByteIO Access Methods Two access methods. Implemented as port-types. Each is optional. RandomByteIO:  Direct random access to a portion of data resource.  Portion to access specified as offset from start of the resource. StreamableByteIO :  Streamed access to a data resource.  Each access relative to the previous access.

Standards for Interoperable Grids16 RandomByteIO read(startOffset: unsignedLong, bytesPerBlock: unsignedInt, numBlocks: unsignedInt, stride: long): byte[] write(startOffset:unsignedLong, bytesPerBlock: unsignedInt, stride: long, data: byte[]): void append(data: byte[]): void truncAppend(offset: unsignedLong, data: byte[]): void

Standards for Interoperable Grids17 RandomByteIO read as XML xsd:unsignedLong xsd:unsignedInt xsd:long byteio:transfer-information-type

Standards for Interoperable Grids18 StreamableByteIO seekRead(offset: long, seekOrigin: URI, bytesToRead: unsignedInt): byte[] seekWrite(offset: long, seekOrigin: URI, data: byte[]): void

Standards for Interoperable Grids19 NextGRID Recommendations Must conform to the WSRF rendering. Must support RandomByteIO. Restrictions on naming.

Standards for Interoperable Grids20 OGSA Data Management Standards DMI: data transfer. ByteIO: data access (file-like), data transfer. WS-DAI: data access (database-like).

Standards for Interoperable Grids21 OGSA WS-DAI WS-DAI: Web Service Data Access and Integration. Access to remote data resources. Modelled on access to databases,  - of various sorts.

Standards for Interoperable Grids22 WS-DAI Data Resource Models The CORE WS-DAI Specification  Independent of data model.  Implemented as a model-dependent realisation. WS-DAIR  Modelled on access to relational databases.  Queries in SQL. WS-DAIX  Modelled on access to XML databases.  Queries in XPath, XQuery and XUpdate. Anticipated that additional realisations will be developed:  eg, RDF, object databases…

Standards for Interoperable Grids23 Properties A WS-DAI resource has a number of properties which a client can interrogate to determine the resource’s characteristics:  DataResourceAbstractName:  ParentDataResource:  DataResourceManagement:  DatasetMap:  ConfigurationMap:  LanguageMap:  DataResourceDescription:  Readable  Writeable:  ConcurrentAccess:  TransactionInitiation:  TransactionIsolation  ChildSensitiveToParent

Standards for Interoperable Grids24 Data Resources Externally managed resources  Data stored using a pre-existing DBMS which has its own existence apart from WS-DAI.  WS-DAI gives access to this resource. Service managed resources  No independent existence.  WS-DAI exists to manage the resource.  For example, the results of a previous query could be made available as a serivce-managed resource.

Standards for Interoperable Grids25 Direct and Indirect Access Patterns for obtaining the results of queries to a resource. Direct Access  The results are simply returned in response to the query. Indirect Access  Effectively implements the ‘factory pattern’.  The results are not returned in the response to the query.  Rather, they are made available as a data resource in their own right.

Standards for Interoperable Grids26 NextGRID Recommendations WS-DAI access is optional for NextGRID. Resources should be modelled as WS- resources. Restrictions on naming.