September 2007 - ogsa-wg

updated 'Execution Environment & BES Model in OGSA Grids' document per public comment review
by Ellen Stokes 25 Sep '07

25 Sep '07

Folks, I've updated the referenced document (in the subject of this email) per the comments received during the public comment period. Here's the link to see the public comments and their resolution: https://forge.gridforum.org/sf/discussion/do/listTopics/projects.ggf-editor… Here's the link the updated document: https://forge.gridforum.org/sf/go/doc14004?nav=1 I've also made 2 other changes: (1) updated OGSA in the title to reflect that it is now a registered trademark. (2) asked Joel Repolgle to get a GFD number assigned to Fred's Guidelines document so I can complete the reference in the reference section of my document. We'll be reviewing this on the OGSA call this Thurs Sep 27 @ 9am Central....details on the OGSA workgroup GridForge wiki. Ellen

1 0

Re: [ogsa-wg] OGSA Information Services
by Hiro Kishimoto 24 Sep '07

24 Sep '07

Hi all, Discussion material for Information Services by Laurence Field and Felix Ehm is now on the GridForge. https://forge.gridforum.org/sf/go/doc14692 > This document covers the problem description, experience in GIN, > overview of existing systems, generalized system and suggested > areas for standardization. Please have a look before the call today. Felix Ehm will lead the discussion. Thanks, ---- Hiro Kishimoto

10 18

OGSA Data Architecture Now in Public Comment
by Hiro Kishimoto 24 Sep '07

24 Sep '07

Per Allen's request, I am forwarding his message to ogsa-wg mailing list. The OGSA Data Architecture architecture document has been placed into its 30 day public comment period. Please take a look at it and submit your comments, even if it is little more than "I read it". Thanks. Allen Luniewski, co-chair OGSA Data Architecture Working Group IBM Cross Brand Services IBM Silicon Valley Laboratory 555 Bailey Ave. San Jose, CA 95141 408-463-2255 408-930-1844 (mobile) -- ogsa-d-wg mailing list ogsa-d-wg(a)ogf.org http://www.ogf.org/mailman/listinfo/ogsa-d-wg

1 0

Re: [ogsa-wg] [OGSA-D-WG] OGSA Data Architecture Now in Public Comment
by Mario Antonioletti 24 Sep '07

24 Sep '07

Hi, For the record you can make your public comments at: http://forge.gridforum.org/sf/discussion/do/listTopics/projects.ggf-editor/… and you have to be logged in in order to be able to do this. Happy commenting ... Mario On Sun, 23 Sep 2007, Allen Luniewski wrote: > > The OGSA Data Architecture architecture document has been placed into its > 30 day public comment period. Please take a look at it and submit your > comments, even if it is little more than "I read it". > > Thanks. > > Allen Luniewski, co-chair OGSA Data Architecture Working Group > > IBM Cross Brand Services > IBM Silicon Valley Laboratory > 555 Bailey Ave. > San Jose, CA 95141 > > 408-463-2255 > 408-930-1844 (mobile) +-----------------------------------------------------------------------+ |Mario Antonioletti:EPCC,JCMB,The King's Buildings,Edinburgh EH9 3JZ. | |Tel:0131 650 5141|mario@epcc.ed.ac.uk|http://www.epcc.ed.ac.uk/~mario/ | +-----------------------------------------------------------------------+

1 0

SLA terms for data services
by Hiro Kishimoto 22 Sep '07

22 Sep '07

Hi Andrew, Mark, and Steve, OGSA-Data WG has a suggested service level terms (they call policies) in their OGSA data architecture document. - Throughput: the number of access requests that can be satisfied per unit time. - Response time: the time allowed to satisfy an access request. - Availability: the percentage of time that the service must be up. - Recovery time: time allowed for the service to recover from a failure. - Data resiliency: a specification of the effort the service should make to ensure that data is not lost in the face of failures. - Access accuracy: if the primary source of some data is not available, how should the service act? Report an error? Find an alternate source (with potentially stale data)? Return partial answers? Another term for this policy might be degradation of answers. - Currency of data: can the data used by the service, and the data returned, be out of date? If so, by how much? I've put them on GridForge SLT design team wiki page for future reference. Thanks, -- Hiro Kishimoto

1 0

Re: [ogsa-wg] OGSA roadmap v1.1
by Hiro Kishimoto 21 Sep '07

21 Sep '07

Hi Chris, New version and corresponding spreadsheet is now on the GridForge. It includes the following modifications: - Accept confirmed modifications, remove resolved comments, and close most of document tracker entries. - Add spec dependency table for RSS and DMI specs. - Update spec dependency table for ACS, HPCP, BSP-SA, SP-SS, SP-ST, and Summary table in Appendix A. - OGSA is now (r) instead of (tm) https://forge.gridforum.org/sf/go/doc13733 Please double check if these changes are ok for you. Also, please confirm remaining three tracker entries are properly incorporated in this version. Then I will make them "closed." https://forge.gridforum.org/sf/go/artf5980 https://forge.gridforum.org/sf/go/artf5974 https://forge.gridforum.org/sf/go/artf5971 If everything is ok, I will clean up the document and make a WG final call on the mailing list shortly. Thanks, ---- Hiro Kishimoto -------- Original Message -------- Subject: Re:OGSA roadmap From: Christopher T Jordan <ctjordan(a)sdsc.edu> To: Hiro Kishimoto <hiro.kishimoto(a)jp.fujitsu.com> Cc: Michael Behrens <michael.behrens(a)r2ad.com>, Savva Andreas <andreas.savva(a)jp.fujitsu.com>, Christopher T Jordan <ctjordan(a)sdsc.edu> Date: 2007/09/11 8:52 > > Hiro, > > No problem. I'll get a new draft uploaded and let you know when I am > passing the pen. > > Thanks. > > On Tue, 11 Sep 2007, Hiro Kishimoto wrote: > >> Hi Chris, >> >> We have chatted document status at OGSA general call today. >> >> Before make an OGSA roadmap v1.1 final call for OGF Editor >> submission on the mailing list, I want to have a pen once again if >> you are ok. >> >> Can you upload revise version to the GridForge or send it to me by >> email? >> >> We are still waiting for a new session for GLUE spec but if they >> cannot make on time, we will leave it for public comments. >> >> Thanks, >> >

1 0

OGSA trademark is now fully registered
by Hiro Kishimoto 21 Sep '07

21 Sep '07

Hi all, At last, OGSA trademark is fully registered. From now forward, we should use (R) instead of (TM). Thanks, -- Hiro Kishimoto

1 0

minutes from today's session
by Donal K. Fellows 20 Sep '07

20 Sep '07

Minutes for EMS Scenarios 1.1 session online at: https://forge.gridforum.org/sf/go/doc14775?nav=1 Donal.

1 0

RNS experiences document
by Andrew Grimshaw 19 Sep '07

19 Sep '07

All, We have done an implementation of RNS and have several observations before we write our experiences document. First, the version of the document I am referring to is the September 22, 2006 version. p.4 Add function We're fine with this BUT we had to make some assumptions. You'll note that the function returns an EPR. Our interpretation was: In the case that no EPR was passed in, i.e., I'm creating and linking a new directory, the function is to return an EPR of a new directory resource. If the case that an EPR was passed in, i.e., I'm adding a link to an existing EPR, the EPR that was passed in is returned. We'll call this the "obvious" implementation An alternative interpretation is that a new resource is created for the DIRECTORY ENTRY ITSELF. In this case the EPR of this entry is returned. We'll call this the "entry" implementation. Note that if the "entry" implementation is used, that after the "add" is performed there is no way to subsequently look up or find the EPR of the entry! We therefore use the "obvious" implementation. Both the "entry" and "obvious" implementations have ramifications and/or inconsistencies with later parts of the spec. Note on page 7 the pseudo schema for an entry (returned by "list") <rns:entry> <rns:entry_name> xsd:string </rns:entry_name> {any}* <rns:entry_reference> wsa:EndpointReferenceType </rns:entry_reference> </rns:entry>* This is consistent with our "obvious" interpretation. One of the things we have observed is that for very large directories this may create messages that are larger than the SOAP max - we may need to extend with an iterator. Also note on page 10 the query operation (which takes NO parameters) and returns <rns:EntryProperties> <rns:entry_parent> wsa:EndpointReferenceType </rns:entry_parent> <rns:entry_name> xsd:string </rns:entry_name> {any}* <rns:entry_reference> wsa:EndpointReferenceType </rns:entry_reference> </rns:EntryProperties> The implication of query is that the "entry" interpretation is being using because there is no way to tell the directory which entry to return data about therefore the SOAP headers contain the target in the form of a ws-addressing epr. In other words - this query seems to be targeted to an entry rather than a directory. The objective of the "entry" implementation seems to be to work with query. The only stuff that seems to be added is the concept on a "entry parent" EPR - which in our opinion could be placed in the {any}* part if needed (the whole notion of parents is a bit problematic; it is likely to be a list not a singleton, and using it for garbage collection is difficult in a distributed system.) Thus, query seems mostly to be a highly specific form of list. Thus, we have chosen the "obvious" implementation. That means that the query operation makes no sense by itself (beyond "list") and we have not implemented it. Page 8, move Move takes two parameters, a target directory and a "new" name for the entry, i.e., file1. This seems to imply an "entry" implementation. However, that means the client must be keeping track of the EPR's of the entries in order to do a move. That's the whole point of a directory services. Therefore, we believe that move should be an operation on a directory (i.e., the EPR of the directory is in the SOAP header) and take two parameters, the old name and the new name - in other words this is a rename. Finally, from a interoperability point of view the fact that the RNS spec does not include a normative specification of the schema/WSDL, we don't believe that it is likely for interoperable implementations to exist solely based on the spec. Modulo the above changes we have an implementation of RNS (we don't think that given the existing spec it is possible to completely implement RNS as specified) and a set of tools that interact with RNS name spaces, command line tools for ls, mkdir, etc, as well as a Linux file system software shim that intercepts file system calls and redirects (when appropriate) to RNS/ByteIO space. A

2 3

[Reminder] EMS scenario 1.1 (Andreas Savva and Steven Newhouse) @ 2007-09-20 09:00 - 10:00 ()
by Google Calendar 19 Sep '07

19 Sep '07

ogsa-wg(a)ogf.org, this is a reminder for Title: EMS scenario 1.1 (Andreas Savva and Steven Newhouse) Time: 2007-09-20 09:00 - 10:00 (Central Time) Calendar: Description: When: 10-11am EDT, 9-10am CDT, 7-8am PDT, 11pm-midnight JST, 3-4pm UK Dial-in numbers for Thursday: Free: +1-888-452-0308 Intl/Toll: +(210) 234-7446 PIN: 71815 See more information: - https://forge.gridforum.org/sf/go/wiki1715 Screen share service: URL: http://ogsa.glance.net/ Usage: https://forge.gridforum.org/sf/go/wiki1584 Note: ** OGF IPR POLICY APPLIES ** http://www.ogf.org/About/abt_policies.php 1) Early discussion Social study notification - https://forge.gridforum.org/sf/go/wiki1717 Note taker assignment - https://forge.gridforum.org/sf/go/wiki1848 Roll call Minutes approval and AI review (see the bottom of this agenda) Agenda bashing 2) EMS scenarios 5) AoB Minutes approval Aug. 14 F2F: https://forge.gridforum.org/sf/go/doc14717 Action Item review http://forge.ogf.org/short/ogsa-wg/ailist You can view this event at http://www.google.com/calendar/event?action=VIEW&eid=YWFzcDN2NmhwbnFyMDI0Yn… You are receiving this courtesy email at the account ogsa-wg(a)ogf.org because you are an attendee of this event. To stop receiving future notifications for this event, decline this event. Alternatively you can sign up for a Google Calendar account at http://www.google.com/calendar/ and control your notification settings for your entire calendar.

1 0