- ogsa-d-wg - lists.ogf.org

RE: [ogsa-d-wg] Format for interface descriptions in OGSA-D
by Stephen Davey 09 Jan '06

09 Jan '06

Hi Michael, I prefer your version for the format for interface descriptions. Though it is perhaps not ideal to include the actual operation and property names, it does make the interfaces much more readable. Adding the table lines will also make them stand out more, which will help me when I try to match up the scenario steps with appropriate interfaces - whether we want to emphasize the interfaces in the data architecture document is another matter I guess. Cheers, Stephen. -----Original Message----- From: owner-ogsa-d-wg(a)ggf.org [mailto:owner-ogsa-d-wg@ggf.org] On Behalf Of Michael Behrens Sent: 23 December 2005 02:08 To: Dave Berry Cc: ogsa-d-wg(a)ggf.org Subject: Re: [ogsa-d-wg] Format for interface descriptions in OGSA-D I attempted to rearange the text a bit and added lines, thinking that might be easier for the reader when confronting that pattern? It's attached - not sure if you'll like it. Its a little more UML-ish. BTW: The strawman architecture (v601) is looking good - covers a lot of ground! Good concepts for global access to information via caching, naming, etc. Dave Berry wrote: >Folks, > >On yesterday's telcon we discussed how to describe interfaces in the >OGSA Data Architecture document. I undertook to draft a straw man >description of the ByteIO interface as an example. I attach this draft >for comment. (Note: it is based on the ByteIO interface described in >our document, which is significantly out of date. What we're interested >in here is the format, not the content). > >On the telcon we agreed that we wanted to abstract away the details of >the operations such as their names and the names and types of their >parameters. This is so that (a) we don't swamp our readers with detail, >and (b) we don't have to keep changing our document to track changes in >the detailed specification. On the other hand, we do want to describe >the key operations, so that (a) readers can better understand what the >interface does, and (b) we show how the interface will interact with >other parts of the system. > >I'm not wedded to the format in the attachment. It is purely intended >as a starting point for discussion. > >Best wishes, > >Dave. > > -- Michael Behrens R2AD, LLC (571) 594-3008 (cell) *new* (703) 714-0442 (land)

1 0

IVOA work on Grid storage and personal data management
by Dave Berry 09 Jan '06

09 Jan '06

Dear All, The International Virtual Observatory Alliance is a group of astronomers who are working on shared Grid software for astronomy. I asked them about their work on managing data in a distributed environment and they pointed me at the following document: http://www.ivoa.net/internal/IVOA/IvoaGridAndWebServices/vostore-0.18.pd f. At a quick glance, this seems to describe requirements for one interface to abstract storage provision and another to abstract data distribution (such as grid file systems). I suggest that this is worth a look to see what overlap, if any, exists with the work of the OGSA-D and GFS WGs (and possibly also GSM?). The IVOA are actively working on this, so the document referenced above will be superseded in due course. Best wishes, Dave Berry Research Manager, National e-Science Centre 15 South College St., Edinburgh Tel: +44 131 6514039

1 0

OGSA-D telcon agenda for January 11th - formats and structure
by Dave Berry 09 Jan '06

09 Jan '06

Dear All, Please let me know in advance if you plan to attend this week's telcon. For those of you calling in, please note the new passcode. The next teleconference of the OGSA Data Architecture working group will be held on Wednesday, January 11th, 2006 at the usual time of 8:00am Pacific / 11:00am Eastern / 4:00pm UK / 5:00pm Europe. In this telcon we will discuss plans for the F2F & GGF, what format to use for describing interfaces, and how to link the scenarios and architecture documents. Here is the updated teleconference information: UK dialin: 0845 245 0224 US dialin: 1 866 838 0046 Intl dialin: +44 1452 542309 NEW Passcode: 275359 Agenda for the January 11th teleconference: 1) Early discussion (5 minutes) Note taker assignment Roll call Minutes Approval (http://tinyurl.com/ace5k) Agenda bashing 2) Action report (5 minutes) - Allen to work on an integration pass, including a scoping section. - Dave to iterate the description of the ByteIO interface (and let Mario know). - Dave to investigate Skype or phone for OGSA Data session at F2F. - Stephen to investigate whether transient data is supported by RNS. - Allen & Dave to draft message to GFS co-chair & ADs, saying RNS is too complicated. - Ann to check the Access section for suitability for file replication. - Mario to update the Access section and make text available for comment. - Section authors to add security notes to their sections. - Everyone to talk with your contacts to get more participation in this WG. - Allen/Dave to contact David Martin & Hiro Kishimoto to get reviewers & expert participation (after internal reviews). 3) Progess & planning update (10 minutes) Update on document writing, links with other WGs, plans for F2F and telcons up to GGF16. 4) Format for documenting interfaces (15 minutes) See the messages from myself and Michael Behrens on 22nd/23rd Dec (attached) 5) Linking the scenarios and architecture documents (15 minutes) Right now, the scenarios document is fairly loosely tied to the architecture document. Do we want to go into greater detail about how the diagrammatic solutions in the scenarios document tie to specific sections of the architecture document? Do we want to create interaction diagrams that show how and when the architectural components interact to effect a solution? Should the architecture document also refer to the scenarios document? 6) Wrap up (5 minutes) Next meetings: Jan 16th-20th: OGSA F2F in Sunnyvale Jan 25th: Report from F2F; review of documents? Feb 1st: Feb 8th: Feb 13th-16th: GGF16 in Athens Dave Berry Research Manager, National e-Science Centre 15 South College St., Edinburgh Tel: +44 131 6514039

1 0

Format for interface descriptions in OGSA-D
by Dave Berry 23 Dec '05

23 Dec '05

Folks, On yesterday's telcon we discussed how to describe interfaces in the OGSA Data Architecture document. I undertook to draft a straw man description of the ByteIO interface as an example. I attach this draft for comment. (Note: it is based on the ByteIO interface described in our document, which is significantly out of date. What we're interested in here is the format, not the content). On the telcon we agreed that we wanted to abstract away the details of the operations such as their names and the names and types of their parameters. This is so that (a) we don't swamp our readers with detail, and (b) we don't have to keep changing our document to track changes in the detailed specification. On the other hand, we do want to describe the key operations, so that (a) readers can better understand what the interface does, and (b) we show how the interface will interact with other parts of the system. I'm not wedded to the format in the attachment. It is purely intended as a starting point for discussion. Best wishes, Dave.

2 1

IPAW 06: Provenance and Annotation Workshop
by Dave Berry 22 Dec '05

22 Dec '05

Dear OGSA-D members, Please see the attached call for papers for IPAW 2006. Currently the OGSA architecture does not explicitly address provenance and annotation but these could areas where interested people could develop the architecture in the future. Best wishes, Dave Berry Research Manager, National e-Science Centre 15 South College St., Edinburgh Tel: +44 131 6514039

1 0

Minutes, 21st December
by Dave Berry 21 Dec '05

21 Dec '05

All, I have put minutes of today's call on GridForge, at http://tinyurl.com/ace5k. I'd like to thank everyone who has contributed time and effort to this working group during 2005. We've made good progress. With a concentrated effort now, we will have a pair of documents ready for GGF16. I wish you all a happy christmas (if applicable) and a prosperous new year. Dave.

1 0

Updated Architecture Document
by Allen Luniewski 20 Dec '05

20 Dec '05

I have consolidated changes into a new version of the strawman document. Changes include: 1. Security information (Allen) 2. Updated Data Access section (Mario) 3. Updated Replication section (Ann) 4. Updated Storage section (Peter) 5. Rewritten section 3 (Dave) I have accepted all edits to the document so we start this round with a "clean" document - no tracked changes other than a few that I made after doing the merge. This should make it easier for us to track what changes we are making in this next round of discussions. It also has the desirable effect (IMHO) of encouraging a complete r-read of the document. The revised document is on Grid Forge as https://forge.gridforum.org/projects/ogsa-d-wg/document/Strawman-Architectu… The document is also attached below. I have taken back write locks on all sections except for Data Access for which Mario retains the write lock. Allen

1 0

Telcon agenda for 21st December - Architecture document review
by Dave Berry 19 Dec '05

19 Dec '05

Dear All, The next teleconference of the OGSA Data Architecture working group will be held on Wednesday, December 21st, 2005 at the usual time of 8:00am Pacific / 11:00am Eastern / 4:00pm UK / 5:00pm Europe. In this telcon we will discuss the overall shape, structure and progress of the architecture/services document. Please read this document and bring issues to the call. As a reminder, here is the teleconference information: UK dialin: 0845 245 0224 US dialin: 1 866 838 0046 Intl dialin: +44 1452 542309 Passcode: 369786 Agenda for the December 21st teleconference: 1) Early discussion (5 minutes) Note taker assignment Roll call Minutes Approval (http://tinyurl.com/9sxqu) Agenda bashing 2) Action report (5 minutes) - Dave to investigate Skype or phone for OGSA Data session at F2F. - Mark to post UVa's "RNS-lite" document, requesting people to comment. [Done] - Stephen to investigate whether transient data is supported. - Allen & Dave to mail GFS saying that we want to collaborate on architectural design. - Allen & Dave to draft message to GFS & ADs, saying RNS is too complicated. - Ann to update replication section. - Ann to check the Access section for suitability for file replication. - Mario to update the Access section and make text available for comment. - Section authors to add security notes to their sections. - Dave to revamp section 3 of the architecture document [Done] - Everyone to talk with your contacts to get more participation in this WG. - Allen/Dave to contact David Martin & Hiro Kishimoto to get reviewers & expert participation (after internal reviews). 3) Progess & planning update (5 minutes) Update on document writing, plans for telcons and F2F. 4) Review of architecture document (40 minutes) Issues that we should consider include, but are not limited to: - Scope - Level of detail - How to describe interfaces - Security implications - Consistency between sections - Identify where work is needed on metadata or on naming conventions 5) Wrap up (5 minutes) Next meetings: Dec 28th: No meeting. Jan 4th: No meeting. Jan 11th: (Planning for F2F, Status review of documents, ...) Jan 16th-23rd: OGSA F2F in Sunnyvale Dave Berry Research Manager, National e-Science Centre 15 South College St., Edinburgh Tel: +44 131 6514039

1 0

WS-Directory (a.k.a. RNS-lite)
by Dave Berry 15 Dec '05

15 Dec '05

Mark's mail bounced. -----Original Message----- From: "Mark Morgan" <mmm2a(a)virginia.edu> To: <ogsa-d-wg(a)ggf.org> Subject: WS-Directory (a.k.a. RNS-lite) Date: Thu, 15 Dec 2005 11:03:35 -0500 As promised, Andrew and I have uploaded the documents describing Uva's prototype and proposed RNS-lite specification and rendering. They can be found at: https://forge.gridforum.org/projects/ogsa-naming-wg/document/draft-wsdir -rec -doc-v1/en/1 https://forge.gridforum.org/projects/ogsa-naming-wg/document/draft-wsdir -wsr f-rendering-doc-v1/en/1 -Mark -- Mark Morgan Research Scientist Department of Computer Science University of Virginia http://www.cs.virginia.edu mmm2a(a)virginia.edu (434) 982-2047

1 0

RE: [ogsa-d-wg] what needs naming in the Data Architecture
by Ziu, Peter 15 Dec '05

15 Dec '05

Just a few comments with respect to naming distributed things. If you look at the problem outside of any current addressing scheme and first address referential integrity of the distributed set, you can think of the following: If you would like to distribute or make copies of the same thing to multiple places, and make it both relevant and irrelevant as to copy you are working with, each distributed "object" needs a unique id to identify itself from other copies in the distributed set, and each copy needs to contain the same unique id representing the distributed set from which it belongs. Then the action of a discovery or addressing service to find one of the objects needs to account for methods to: 1.) find the "best [nearest, cleanest, best performing, most complete, most in sync, etc.]" object by distributed set, or 2.) find a particular object copy/replica/cache by unique object id. Pete -----Original Message----- From: owner-ogsa-d-wg(a)ggf.org [mailto:owner-ogsa-d-wg@ggf.org] On Behalf Of Michael Behrens Sent: Wednesday, December 14, 2005 10:25 PM To: Stephen Davey Cc: ogsa-d-wg(a)ggf.org Subject: Re: [ogsa-d-wg] what needs naming in the Data Architecture I find this helpful....especially when considering caches as mentioned below ( cacheing came up in the other telecon tonight too). I presume that binding needs to be done by something other than the user of the named thing, so that cached values can be used. Is the basic goal to be able to name anything, stick it in the virtual grid ethernet storage container, and ask for it later using that name from anyplace and get it (perhaps from a cache, perhaps not)? Meaning is the name might also usable as a static reference? Stephen Davey wrote: >Hi everyone, >As part of the RNS & GFS discussion today I wonder if it would be >useful to think of all the things in the data architecture that might >need naming, and then to check that these would be covered by the 2 specs. >Below is my list of all things vaguely data related that I could think >of. > >Is it planned to also discuss the Naming section (3.2) of the Data >Architecture document? > >Cheers, Stephen. > > >caches >containers (of resources) >data bytes >data streams >database tables >databases >defaults >digital libraries >endpoint references (EPRs) >file directories >file locations >files >identities >languages >locales >metadata >namespaces >naming schemes >networks >people >policies >properties >queries >query result row sets >references >registries >replicas >repositories >resource locations >resources >roles >schema >schema mappings >services >storage (space) >transactions >transformations >transport protocols >user defined entities >vocabularies >workflows > > >--------------------------------------------------------- >Stephen Davey, NextGrid Software Architect, National e-Science Centre, >15 South College St., Edinburgh, EH8 9AA, UK >Tel: +44 131 6 509820 > > > > > > -- Michael Behrens, R2AD, LLC

1 0