1. ByteIO Discussion OGSA F2F, London 26 May 2005

2. To Recap … Why are we here? –Many OGSA WGs have a need for a simple way of reading and writing blocks of raw, non-interpreted data (like files) –A simple, posix-like interface suffices and seems to be what most are looking for –Great desire to maintain extreme simplicity and to accelerate time to spec. “Is this all that I am, is there nothing more?” –Nope, that’s it.

3. Timetable High level (taken from charter) –Deliverable/Milestone 1: BOF – March 2005, Korea. –Deliverable/Milestone 2: Draft use case document and draft recommendation document, June 2005. –Deliverable/Milestone 3: Draft experience documents, September, 2005. –Deliverable/Milestone 4: Use case document and recommendation document ready for public review, October, 2005. –Deliverable/Milestone 5: Final use case and recommendation documents, Spring, 2006. Use Case Document (taken from ogsa roadmap) –First Draft, June 2005 –Public Comment Review, October 2005 –GWD-I publication, March 2006

4. Agenda –Statement of Meeting Goals Prototype Port Type Use Case Discussion –Use Case Document Template –File Use Case –DAIS Use Case –Sensor Use Case

5. Goals for this meeting… Present Current Thoughts of byteio-wg Gather feedback on BoF interface Present thoughts on bulk data transfer –Brainstorm on alternatives, addendums Present (after some fashion) Use Case Template Document –Unless significant hyperventilating ensues, adopt as working group template document within next week. Discuss initial use cases –File –DAIS –Sensors? Brainstorm on other use cases

6. Agenda Prototype Port Type Use Case Discussion –Use Case Document Template –File Use Case –DAIS Use Case –Sensor Use Case

7. Simple Quick to Prototype –Both in terms of design of the spec. and implementation APIs do not have to correspond to service interfaces –E.g. A stateless service interface does not necessitate a stateless client API POSIX-like functionality ByteIO is an interface, not a service… Many other things I have forgotten to mention… Recall Goals and Mantras So says Mark… (pseudo-decided)

8. Conceptual UML, as presented at GGF13 BoF ByteIO read (offset: long, length: long): byte[] write(offset: long, data: byte[]): void append(offset: long, data: byte[]): void truncAppend(data: byte[]): void

9. What about streaming? What about locking? What about …? Service interface does not dictate (though in the limit it may influence or suggest) API –Streams in Unix are an API on a block oriented read/write protocol of the OS reminiscent of ByteIO Prototype interface. Locking is important, but so is simplicity “Wrapper” interfaces can be used for session- able service resource interactions “Wrapper” interfaces also can be used for advisory file locking –Examples of this exist in grid systems

10. Bulk Data Transfer DIME MTOM Raw Sockets Base64 in the SOAP Body None of these is right for every solution Don’t want to unnecessarily over- complicate a simple specification.

11. Bulk Data Transfer Goals Efficient when possible/desirable Interoperable Should “play well” with others –Firewall traversal –NAT traversal –Security –In the limit, any WS-* solution that OGSA uses should be available to data transfer when desired

12. Bulk Data Transfer We can’t realistically pick one transfer mechanism for everyone Recommendation: Let’s allow a ByteIO implementation to advertise available transfer mechanisms Clients will pick the transfer mechanism they prefer

13. UML (take 2) ByteIO read (offset: long, length: long, xferMech: QName): byte[] write(offset: long, data: byte[], xferMech: QName): void append(offset: long, data: byte[], xferMech: QName): void truncAppend(data: byte[], xferMech: QName): void

14. How this might work… xsd:long xsd:any “profile” these

15. “profiles” for transfer, some examples byteio-xfer:inline byteio-xfer:DIME byteio-xfer:MTOM byteio-xfer:raw-tcp Possibly require this one as a minimum Risky, but “might” be very performant

16. Bulk Data Transfer (Rough, back of the “web-service” numbers)

17. “profiles”, some examples (contd.) 1024 MIIEGTCCA8OgAwIBAgIQfS6SxdPyXp5PizFQTafBUzANBgkqhkiG9w0BAQQF ADCBrDEkMCIGCSqGSIb3DQEJARYVYWRtaW5AY3MudmlyZ2luaWEuZWR1 MQswCQYDVQQGEwJVUzELMAkGA1UECBMCVkExGDAWBgNVBAcTD0NoY XJsb3R0ZXN2aWxsZTEfMB0GA1UEChMWVW5pdmVyc2l0eSBvZiBWaXJnaW 5pYTEvMC0GA1UEAxMmQ29tcHV0ZXIgU2NpZW5jZSBEZXBhcnRtZW50IElJU

18. “profiles”, some examples (contd.) 1024 1025 foo.bar.com internal.foo.bar.com

19. What about properties? File Size Create Time Modification Time Owner File Type? Supported Bulk Transfer Types?

20. Agenda Prototype Port Type Use Case Discussion –Use Case Document Template –File Use Case –DAIS Use Case –Sensor Use Case

21. Use Case Document Template Based on OGSA Use Case Document –Take into account ByteIO is simpler ByteIO is much lower level In fact, ByteIO is in some ways almost foundational –in other words, we expect many grid technologies to build on it

22. Use Case Template Document (sections) Summary –Here you would summarize the use case that you are describing. Scenarios –Here you list all of the various scenarios that can make up your use case. Involved Resources –What resources are involved in this use case? Functional Requirements –What functional pieces are required to make this work? What abilities must we have in place in order to give clients the functionality that they would expect from this use case? Situation Analysis –Discusses other specifications and how ByteIO will fit with them. Here we are talking about resources that might build on the use case. Security/Reliability Considerations –What kinds of security considerations do you think apply to this particular use case. Performance Considerations –What role does performance play in this use case? What is the expected bandwidth required? References –Any pertinent references…

23. File Use Case Mark to present –Flat File – aka, Direct Grid Aware Access –NFS/CIFS – aka, Transparent, Legacy Access –Stream-able Session

24. DAIS Use Case Neil to present

25. Sensor Use Case Dave to present

26. Other Use Cases? Ideas are welcome, submissions applauded –Would like to have a deadline on draft submissions by “Close of Business” Friday, 10 June 2005 Close of business is 9AM Eastern on Monday the 12 th of June. “Cry havoc, and let slip the use cases of war…”