1. Chairs: Mario Antonioletti, EPCC Shahbaz Memon, FZJ Ravi Madduri, UoC
OGF25 OGSA-DMI Status
Chairs: Mario Antonioletti, EPCC
Shahbaz Memon, FZJ
Ravi Madduri, UoC

2. OGF IPR Policies Apply
“I acknowledge that participation in this meeting is subject to the OGF Intellectual Property Policy.”
Intellectual Property Notices Note Well: All statements related to the activities of the OGF and addressed to the OGF are subject to all provisions of Appendix B of GFD-C.1, which grants to the OGF and its participants certain licenses and rights in such statements. Such statements include verbal statements in OGF meetings, as well as written and electronic communications made at any time or place, which are addressed to:
the OGF plenary session,
any OGF working group or portion thereof,
the OGF Board of Directors, the GFSG, or any member thereof on behalf of the OGF,
the ADCOM, or any member thereof on behalf of the ADCOM,
any OGF mailing list, including any group list, or any other list functioning under OGF auspices,
the OGF Editor or the document authoring and review process
Statements made outside of a OGF meeting, mailing list or other function, that are clearly not intended to be input to an OGF activity, group or function, are not subject to these provisions.
Excerpt from Appendix B of GFD-C.1: ”Where the OGF knows of rights, or claimed rights, the OGF secretariat shall attempt to obtain from the claimant of such rights, a written assurance that upon approval by the GFSG of the relevant OGF document(s), any party will be able to obtain the right to implement, use and distribute the technology or works when implementing, using or distributing technology based upon the specific specification(s) under openly specified, reasonable, non-discriminatory terms. The working group or research group proposing the use of the technology with respect to which the proprietary rights are claimed may assist the OGF secretariat in this effort. The results of this procedure shall not affect advancement of document, except that the GFSG may defer approval where a delay may facilitate the obtaining of such assurances. The results will, however, be recorded by the OGF Secretariat, and made available. The GFSG may also direct that a summary of the results be included in any GFD published containing the specification.”
OGF Intellectual Property Policies are adapted from the IETF Intellectual Property Policies that support the Internet Standards Process.
IPR Notices Note Well for OGF meetings 2

3. Outline Background Overview of DMI Renderings Group Documents
Implementations
Next steps
Conclusions 3

4. Background Group formed 2006 Published Functional spec (GDF 134)
BoF GGF16 (Athens)
Published Functional spec (GDF 134)
Defines the building blocks
Renderings put in the detail
Plain WS rendering
Currently in public comment
WSRF rendering
Extends the plain WS rendering
In Progress 4

5. DMI Scenario (an analogy)

6. User moves data from A  B
User does not care how it is done
User does not want to:
Deal with different protocols
Deal with different security models
Learn new interface for different data types
Handle structured & un-structured data
Agnostic about the data semantics 6

7. Requirements High-level interface and abstractions
i.e. Unix cp – no concern if local/remote disk
Automatically select sensible protocols
Work with multiple security models
Extensible & integrateable into other services 7

8. OGSA-DMI in a nutshell The Problem! Service User Client EPR Transfer
http
ftp
GridFTP
Services capable of retrieving data from the source
The Problem!
DEPR
Source
Location
Service
Data Transfer Factory
Port Type
Data
@ A
Existing
Data
Transfer
protocol
EPR
User
Client
Transfer
AB
Data
Transfer
Instance
Port Type
DEPR
GridFTP
ftp
Services capable of placing data at the sink
Data
@ B
Sink
Location
OGSA-DMI protocol
Existing data
transfer protocols 8

9. What we have done … Define port types to enable data transfers
Allow use of different protocols
Composeable with other WS specs
Core spec agnostic about WS renderings
Normative renderings for different WS ‘flavors’
Have a plain WS rendering
Working on a WSRF rendering
Could add additional renderings 9

10. What are we not doing … Bandwidth negotiation Service Level Agreements
Co-scheduling of compute & data transfer
Optimizing data transfer
Reliability through data replication
Protocol negotiation with the source/sink 10

11. The Data EPR - DEPR A DEPR for each source and sink
Where the DTI can find & access your data
Where the DTI is going to put your data
Encapsulate meta-data to access the data
Protocols used to access the data
Identified through defined URIs
Protocol specific data location
e.g. file path, FTP URL, …
Any authentication tokens needed for access
Why YOU? This is because of the authentication token? Can’t exchange DEPRs? 11

12. DEPR Use Cases Know explicit data source & sink & protocol
Data location & protocol wrapped in DEPR
DTF uses protocol to start the DTI
Data accessible through multiple protocols
Data locations & protocols passed in DEPR
DTF finds a matching protocol and starts DTI
Logical data names passed in DEPR
DTF resolves names to data locations
Could use 3rd party lookup service 12

13. Where will the DEPRs come from?
Is not specified by OGSA-DMI
Instead, we define what we need…
For a simple file copy command
Use local security token
Explicit file location information
For a large data catalog
Maps logical name to real data locations
Provide protocol(s) to access the data 13

14. Data Transfer Factory (DTF)
DTFs only know about certain protocols
Defined undo strategy for each protocol
Selection of a protocol from the DEPRs
Creates an EPR to a DTI instance
In the future (for DMI or other groups):
Negotiate networking SLAs
Consider geographical replica locations
Co-schedule transfers with other tasks 14

15. Data Transfer Instance (DTI)
New EPR used for each transfer
If it fails a new EPR must be obtained
DTI manages the selected data transfer
Start/Stop
Suspend/Resume
DTI provides client with transfer status
GetState
Current state
Transfer progress 15

16. DTI State Diagram
Have coloured in bright yellow - should wake up anyone that dares to fall asleep. 16

17. Renderings Plain WS Rendering WSRF-Rendering
Intrinsically WS-I compliant
Intra Rendering interoperability
Inter-Rendering interoperability baseline
WSRF-Rendering
Extends Plain WS Rendering
Doubled interface definition
Single implementation 17

18. DMI Factory WS Rendering WSRF Rendering Attributes Plain attributes
Resource Properties
Operations
GetDataTransferInstance()
GetFactoryAttributesDocument()
GetRPDocument()
GetRP()
GetMultipleRP()
Other
RP Value Change Notification? 18

19. DMI Instance WS Rendering WSRF Rendering Attributes Plain attributes
Resource Properties
Operations
Start, Stop, …
GetFactoryAttributesDocument()
GetRPDocument()
GetRP()
GetMultipleRP()
Other
RP Value Change Notification?
RM Management Lifecycle? 19

20. Changes in Group Composition
Core group:
Michel Drescher, Steven Newhouse, Mario Antonioletti, Allen Luniewski, Shahbaz Memon, Ravi Madduri
Changes:
Michel left Fujitsu, no longer involved
Steven moved from Microsoft
Shahbaz joined from FZJ as a new Chair
Welcome new members 20

21. Documents Done In process: To do:
OGSA-DMI Functional Specification 1.0
In process:
OGSA-DMI Plain Web Service Rendering Specification 1.0
In public comment (up to 10th March) – PLEASE COMMENT!
To do:
Experiences document for plain WS rendering
WSRF rendering
Experiences document for WSRF rendering 21

22. Document Hierarchy OGSA-DMI Functional Specification 1.0
Plain WS Rendering
Plain WS Experiences Document
WSRF Rendering
WSRF Experiences Document 22

23. Implementations Plain WS Rendering WSRF Rendering (in progress)
Fujitsu implementation
Steven Newhouse implementation
WSRF Rendering (in progress)
FZJ implementation
Looking for others… 23

24. Next Steps Write plain WS experiences doc
Write the WSRF rendering document
Find at least two implementations
Do an interop
Write up a WSRF experiences doc
Consider if there is more to do
Socialise specs? 24

25. How can I participate? Comment on the plain WS spec
Have up to the 10th of March!
Join the mailing list
Links from the DMI account on Grid Forge
Attend the telcons
Publicised on the mailing list
Implement the specifications
Participate in the interop 25

26. Conclusions Overview of DMI Current status Welcome new blood
Please join us!
Shahbaz will present a UNICORE perspective … 26

27. Full Copyright Notice
Copyright (C) Open Grid Forum (2009). All Rights Reserved.
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works.
The limited permissions granted above are perpetual and will not be revoked by the OGF or its successors or assignees.
OGF Full Copyright Notice if necessary 27