October 2005 - ogsa-d-wg

Telcon Agenda, THURSDAY October 20th
by Dave Berry 12 Oct '05

12 Oct '05

Dear all, The next OGSA-D telcon will be on an unusual day, Thursday 20th October, at the usual time of 8:00am Pacific / 11:00am Eastern / 4:00pm UK / 5:00pm Europe. It will also have a DIFFERENT PIN: UK Dial In: 0845 245 0224 US Dial In: 1 866 838 0046 International Dial In: +44 1452 542309 PIN Number: 275 359 Agenda for the October 20th teleconference: 1) Early discussion (5 minutes) Note taker assignment Roll call Minutes approval from October 12th teleconference (http://tinyurl.com/9bkxm) Agenda bashing 2) Action report (5 minutes) - Dave to put slides and reports from GGF on GridForge. - Dave to forward OGSA-DAI internal memo to Allen - Allen to comment on OGSA 1.5 draft; Dave to revise and send to list - Dave to send F2F plans to mailing list. - Peter to rewrite storage managment section to reflect changes from GSM-WG. - Allen to write text about policy. - Allen to write an overview section on security - Section authors to add security notes to their sections, once the overview is ready. - Dave to revamp section 3 of the architecture document - 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) Planning update (5 minutes) Update on plans for telcon, F2F and document writing 4) OGSA 1.5 Discussion (45 minutes) Review of the OGSA 1.5 draft 5) Wrap up (5 minutes) AOB

1 0

Telcon Agenda, 11th October: Security and planning our first drafts
by Dave Berry 11 Oct '05

11 Oct '05

Dear All, The next teleconference of the OGSA Data Architecture working group will be held on Wednesday, October 11th, 2005 at the usual time of 8:00am Pacific / 11:00am Eastern / 4:00pm UK / 5:00pm Europe. 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 October 11th teleconference: 1) Early discussion (5 minutes) Note taker assignment Roll call Minutes approval from September 28th teleconference (http://tinyurl.com/72v6w) Agenda bashing 2) Action report (5 minutes) - Various actions relating to GGF15 [Done] - Dave to chase section authors re dates for their review sessions - Mario to check whether internal OGSA-DAI notes on security could be released, possibly just to Allen and Dave [Done] - Dave to redraft data sections for OGSA 1.5 document [Ongoing] - Allen to write an overview section on security [Ongoing] - Section authors to add security notes to their sections, once the overview is ready. - Everyone to talk with your contacts to get more participation in this WG. - Dave to revamp section 3 of the architecture document [Ongoing] - Allen/Dave to contact David Martin & Hiro Kishimoto to get reviewers & expert participation (after internal reviews). 3) Planning our first drafts (15 minutes) Allen & Dave have drafted a timetable for completing the first draft of both documents. This includes telcon schedules and F2F meetings. We will present this and discuss. 4) Security Discussion (15 minutes) Assimilating the information we've received from GGF. 5) Wrap up (5 minutes) AOB DONM - THURSDAY 20th: OGSA 1.5 revision Dave Berry Research Manager, National e-Science Centre 15 South College St., Edinburgh Tel: +44 131 6514039

1 0

Telcon number and schedule: Oct 12 - Nov 30
by Dave Berry 08 Oct '05

08 Oct '05

Dear all, Here is a provisional timetable for OGSA-D telcons for the next two months. Please note that the reviews have been rescheduled to ensure that key people will be present. On the four weeks from Oct 26th to Nov 16th we will review four sections of the services document along with their associated scenarios. With the exception of the Oct 20th call, all telcons will be on Wednesdays at the usual time of 8:00am Pacific / 11:00am Eastern / 4:00pm UK / 5:00pm Europe. Oct 12th: Security Oct 20th: Review of OGSA 1.5 document (THURSDAY, at the usual time) Oct 26th: Section review Nov 2nd: Section review Nov 9th: Section review Nov 16th: Section review Nov 23rd: No telcon (Thanksgiving) Nov 30th: Review of scenarios document Here is the dialin information for the Wednesday calls: UK dialin: 0845 245 0224 US dialin: 1 866 838 0046 Intl dialin: +44 1452 542309 Passcode: 369786 Best wishes, Dave Berry Research Manager, National e-Science Centre 15 South College St., Edinburgh Tel: +44 131 6514039

1 0

schedule change
by Osamu Tatebe 04 Oct '05

04 Oct '05

Hi all, We would like to swap session topics #1 and #2. Now, * GFS-WG #2 (GFS-ARCH) Tuesday, October 4 2:00 pm - 3:30 pm Location: White Hill Grid File System Use Case (45 min) Grid File System Diagram (45 min) * GFS-WG #1 (RNS/VFDS) Wednesday, October 5 6:00 pm - 7:30 pm Location: Whitter RNS specification (30 min) VFDS specification (60 min) Sorry for this, Osamu >> On Tue, 27 Sep 2005 10:56:24 +0900 (JST), Osamu Tatebe <o.tatebe(a)aist.go.jp> said: >> Hi all, >> We will have two sessions at GGF15; one is for RNS/VFDS discussion, >> and the other is for architecture of Grid file system. >> * GFS-WG #1 (RNS/VFDS) >> Tuesday, October 4 2:00 pm - 3:30 pm Location: White Hill >> RNS specification (30 min) >> VFDS specification (60 min) >> * GFS-WG #2 (GFS-ARCH) >> Wednesday, October 5 6:00 pm - 7:30 pm Location: Whitter >> Grid File System Use Case (45 min) >> Grid File System Diagram (45 min) >> Regarding RNS specification, the real final spec that reflects >> comments at August OGSA-WG F2F meeting will be available soon. >> Regarding Architecture session, we will start detailed and concrete >> discussion. At GGF12, we discussed the service diagram, see the >> picture of the blackboard; >> https://forge.gridforum.org/projects/gfs-wg/document/GFS_Architecture_Black… >> The goal is to identify >> * necessary services and their functionality, and >> * interaction among these services >> to provide Grid file system functionality (or file system use case). >> For this purpose, we would like to invite speakers to share current >> solutions. Main points are what kind of services are needed and how >> these services are related each other to provide Grid file system >> functionality. Please respond to this email if you can give a talk. >> EGEE, distributed storage tank, and other efforts are quite welcome. >> Thanks, >> Osamu >> --- >> Osamu Tatebe, Ph.D. Tel: +81-29-861-5844 FAX: +81-29-862-6601 >> Grid Technology Research Center, >> National Institute of Advanced Industrial Science and Technology (AIST) >> AIST Tsukuba Central 2, 1-1-1 Umezono, Tsukuba, Ibaraki 3058568 JAPAN >> E-mail: o.tatebe(a)aist.go.jp http://phase.hpcc.jp/people/tatebe/

1 0

Stepping back: the high-level view
by Dave Berry 03 Oct '05

03 Oct '05

All, I've been tasked with rewriting the sections of the main OGSA document that deal with data services. This is providing interesting as a check on the work we've been doing on the data architecture document itself. The good news is that much of the existing description in the OGSA document remains accurate. This suggests we did a good job early on. The OGSA document does describe some higher-level features that we haven't developed sufficiently in the data architecture document. I think the most important is the specification of policy, QoS, etc. We've always been aware of this during our discussions but we haven't really developed it, at least not across the whole architecture. I think we need to make this the next cross-cutting issue that we address (analogous to the way we have addressed transactions and security). I also think we need to raise this with the OGSA WG, as we will need to use the same mechanisms as the rest of OGSA. (It may be that we force the pace of this, as I suspect QoS is more important in data services). We also need to think about how to provide performance information, e.g. latency, bandwicth, network location, etc. This is clearly linked to the QoS question. Another cross-cutting concern is graceful degradation of availability. The OGSA document says, "The OGSA data services provide features for graceful degradation in the event of network or other failures. For example, query services may be configured to return partial results when only a subset of sources is available". I suspect we need to address this as another cross-cutting feature. Another major feature from the OGSA document that we haven't addressed is that of transformations and derived data services. I think we took an explicit decision to leave these to a later version of the architecture - does this match your memories? If we agree this is the case, I'll discuss with the OGSA WG how best to reflect this in the OGSA document. The OGSA document also lists provenance as a particular feature that data services support. Provenance is clearly important but I doubt we will address it explicitly in the current version of the data architecture. We made need to address it in the longer term. It seems to me that provenance should be just another form of metadata - but I do know of projects that have developed particular architectures for storing provenance data (e.g. the PASOA project in the UK). Best wishes, Dave Berry Research Manager, National e-Science Centre 15 South College St., Edinburgh Tel: +44 131 6514039

1 0