December 2004 - ogsa-wg - lists.ogf.org

Proposed agenda for Dec. 1st call
by Hiro Kishimoto 20 Dec '04

20 Dec '04

Hi all, The following is a proposed agenda for OGSA-WG telecon on December 1st Wednesday from 5pm to 7pm (CST). The dial-in number for Wednesday. Free: +1-888-452-0308 Intl/Toll: +1-484-644-0505 PIN: 71815 Screen share service will be provided. URL: http://hiro.glance.net Session key: 1201 See more explanation: http://www-unix.gridforum.org/mail_archive/ogsa-wg/2004/06/msg00077.html 1) Early discussion (10 min) Note taker assignment Roll call Telecon minutes approval (if available) Agenda bashing 2) December F2F meeting discussion (30 min) Agenda discussion Any other update 3) Interested party list discussion (30 min) Revised template review. - http://tinyurl.com/5fxfd/OGSA_interested_party_survey - http://tinyurl.com/5fxfd/BusinessGrid_draft List of expected responders by F2F meetings 4) OGSA arch v1 document update (30 min) Continue with review of v1 public comments. Last spreadsheet: https://forge.gridforum.org/projects/ogsa-wg/documen/ogsa-v1-public-comment… 5) OGSA glossary update (10 min) Continue with review of glossary public comments. Last summary: http://www-unix.gridforum.org/mail_archive/ogsa-wg/2004/10/msg00008.html 5) Wrap up (10 min) AOB Dec. 6th: No tele-con (Ravi is not available) Dec. 8th - 10th is F2F meeting in Washington D.C. <pending issues> ?) Process discussion until December F2F (?) Agenda items Design teams' deliverable and schedule Solicit attendees from related WG/RG/TCs https://forge.gridforum.org/projects/ogsa-wg/document/200412_draft_agenda_o… e/en/1 ?) Roadmap document review (?) > - Ian had some comments on the revised version and it was decided > that it would be better to have him on the call. The version of the roadmap that came out of the Sept 1st call is on gridforge: http://tinyurl.com/5fxfd/draft-ggf-ogsa-roadmap/en/2 ?) GGF12 Action Items () - Andreas will send out shortly ?) Aug F2F meeting Action Item review (?) Action: Heather to send details on the work WSDM is doing on Events. - Ravi and Andrew would like to be involved in this discussion. > Fred will keep an eye on work progress and inform the group > Andreas to send reminder to Heather again > Done Action: Andrew to check with Data team if producing a set of notes each detailing a decision and its rationale (Architecture (AR) notes) would be appropriate to solve the 'communication' problem (what OGSA-WG has discussed and decided) > - Andrew did not receive a positive or negative response so far > - Andrew to talk with people who brought it up; this will likely > not be before GGF12. Action: Frank to ask Ian for an MDS representative to join the Information Services design team > - Frank asked Ian; waiting for reply; will followup. Action: Jay to talk with Ian and Hiro and form a core design team to work on dependencies at architecture level (roadmap). > - Hiro will contact Jay Thanks, ---- Hiro Kishimoto

2 4

FW: [dais-wg] WSRF Embodiments and DAIS
by Dave Berry 18 Dec '04

18 Dec '04

FYI, the DAIS WG has raised the following issues with the OASIS WSRF group. -----Original Message----- From: Susan Malaika [mailto:malaika@us.ibm.com] Sent: 17 December 2004 10:21 To: dais-wg(a)gridforum.org; wsrf(a)lists.oasis-open.org Subject: [dais-wg] WSRF Embodiments and DAIS The Oasis WSRF group asked the GGF DAIS working group to consider the WSRF "WSDL 1.1 Binding Element Embodiment". An item was posted to the DAIS mailing list entitled "DAIS mapping and WSRF embodiments" on 23 November 2004. There has been discussion among the DAIS community on the use of the WSRF embodiments. Some of the DAIS community involved in the discussions are the implementers of the first open source version of DAIS known as OGSA-DAI; they are the first users of DAIS; they are active in promoting DAIS among data grid communities around the world. These are some interim conclusions: 1. Multiple kinds of DAIS Users It is still not clear if DAIS should mandate WSRF because some of the participants in the DAIS group rely on non-WSRF middleware. DAIS could go some way towards satisfying WSRF and non-WSRF users by placing the resource identifier in the DAIS messages (so a single DAIS message format could be used by both WSRF and non-WSRF DAIS users). A note on resource properties: * Resource properties requests cannot include resource identifiers in the message body. The resource identifier must be placed in the header. A suggestion for the WSRF group : * It would be helpful to know if specifying a resource identifier in the DAIS messages as well as in the header is acceptable to the WSRF folk. 2. Multiple resources in a single request (see below for use cases) Currently, each DAIS service request accesses a single resource, and the resource being accessed determines the underlying resources that should be accessed too, e.g., the exposed single resource can perform resource name mappings . In this case, the WS-Resource concept may (or may not) be used to represent the exposed resources in DAIS. (depending on whether DAIS adopts WSRF) In some proposed extensions and applications of DAIS, multiple resources of different types are accessed through a single service request. It is required that the multiple resources be visible to the client. The WS-Resource concept could be used to represent a collection of resources. An identifier to represent the collection could be placed in the header, while the individual resource identifiers in the collection could appear in the message content. A note on resource properties: * Resource properties requests could result in properties for all the resources in the collection being examined. (see below for alternatives for representing the resource properties documents) A suggestion for the WSRF group : * It would be helpful to know if representing a collection of resources as a WS-Resource is a recommended use of WSRF. 3. WSRF "WSDL 1.1 Binding Element Embodiment" If DAIS does adopt WSRF then the "WSDL 1.1 Binding Element Embodiment" is helpful because it permits a client supplied resource identifier to appear in the message header (in other words the resource identifier is not opaque to the client). However note that there are client side prerequisites for the "WSDL 1.1 Binding Element Embodiment", e.g., the client software would have to know to place the resource identifiers in the right place in the header A suggestion for the WSRF group : * It would be helpful to know if there are any tools that support embodiment "WSDL 1.1 Binding Element Embodiment" ................................................................. Use Cases ......... Here are some use cases for multiple resources in a single request: U1. In an interaction with a DAIS service, many resources may be created to represent the results of requests. There may come a time when several of these resources can safely be removed. In such a setting, the options are to: U1.1. Invoke something like "remove() => EPR representing resource" for each of the resources. U1.2 Invoke something like "remove([EPR representing resource-1, ...,EPR representing resource-n]) => EPR representing service" once. How would option U1.2 be modeled through WSRF? U2. In an interaction with a DAIS service, it may be necessary to aggregate multiple results sets and return the combined result set via ftp. In such a setting, the options are to: U2.1 Invoke something like "ftp (..) => EPR for resource1" for each of the resources and then aggregate the results on the client U2.2 Invoke something like : - "aggregate ([EPR representing resource-1, ...,EPR representing resource-n]) => EPR representing service" - "ftp (..) => EPR representing aggregated resource" (the result aggregation would be done at the server.) How would option U2.2 be modeled through WSRF? (BTW it is possible that a combined aggregate and ftp operation would be desirable) U3. In an interaction with a DAIS service, it may be necessary to issue a query over multiple databases and files. In such a setting, the options are to: U3.1 Invoke something like "query (..) => EPR for resource1" for each of the resources, returning each query result to the client, and then aggregate the results on the client (the result aggregation process could be very complex.) U3.2 Invoke something like "copy (..) => EPR for resource1" for each of the resources and then issue the queries locally on the client (this means having a query engine on the client.) U3.3 Invoke something like "query([EPR representing resource-1, ...,EPR representing resource-n]) => EPR representing service" once (the query result aggregation would be done at the server.) How would option U3.3 be modeled through WSRF? Alternatives for modeling resource properties documents for U1.2, U2.2, U3.3 ........................................................................ ..... <ResourceNames> <ResourceName>resource1</> <ResourceName>resourceX</> </> Or as complex as <Resources> <Resource> <ResourceName>resource1</> <ResourceType>RDB</> <ResourceSchema>....</> </> <Resource> ... </> </> A suggestion for the WSRF group : It would be helpful to know which modeling approach is preferred Thanks to everyone who contributed and reviewed this note. Happy Happy Holiday Season :-) Susan Malaika

1 0

Teleconference minutes - Dec. 15, 2004
by Andreas Savva 16 Dec '04

16 Dec '04

Minutes attached. Gridforge link: https://forge.gridforum.org/projects/ogsa-wg/document/minutes-20041215/en/1 or http://tinyurl.com/5fxfd/minutes-20041215/en/1 -- Andreas Savva Fujitsu Laboratories Ltd.

1 1

Data: date of next telcon
by Dave Berry 13 Dec '04

13 Dec '04

Dear all, I won't be available for the usual telcon slot this week. I doubt we will want to meet during (what is for most of us) the holiday season, so the next telcon will be on Wednesday January 5th. This will be at the usual time: 8.00am (PST) / 11.00am EST / 4.00pm (GMT) / 5.00 pm (CET). UK Dial In: 0845 245 0224 US Dial In: 18668380046 International Dial In: +44 1452 542309 PIN: 632065 (Reference Number: 2361592) Our main need is to progress the straw man architecture. I am setting aside some days in January to work on this. If anyone can progress parts of the straw man before then, the rest of us would be very grateful. Dave Berry Research Manager, National e-Science Centre 15 South College St., Edinburgh Tel: +44 131 6514039

1 0

FW: Revised Naming Document
by Hiro Kishimoto 12 Dec '04

12 Dec '04

Dave's mail bounced. ---- Hiro Kishimoto

1 0

Re: [ogsa-wg] Dial-in number for today's f2f session...
by Susan Malaika 10 Dec '04

10 Dec '04

Is there a dial-in for this morning which I assume is covering data? Susan Malaika Jem Treadwell <Jem.Treadwell(a)hp.com>@ggf.org on 12/09/2004 06:16:14 AM Sent by: owner-ogsa-wg(a)ggf.org To: ogsa-wg(a)ggf.org cc: Subject: [ogsa-wg] Dial-in number for today's f2f session... ... is 1-800-480-3702 id 778485# Thanks, - Jem -- Jem Treadwell Hewlett-Packard Company Phone: (732) 577-6043 200 Route 9 North Fax: (732) 577-6003 Manalapan, NJ 07726 E-mail: Jem.Treadwell(a)hp.com

2 1

EGEE Documents
by Steven Newhouse 09 Dec '04

09 Dec '04

All, EGEE have documented their architecture and described their interfaces ... https://edms.cern.ch/document/476451/ - SHORT (70 pages) https://edms.cern.ch/document/487871/ - LONG (300 pages) Enjoy! Steven -- ---------------------------------------------------------------- Dr Steven Newhouse Tel:+44 (0)2380 598789 Deputy Director, Open Middleware Infrastructure Institute (OMII) Suite 6005, Faraday Building (B21), Highfield Campus, Southampton University, Highfield, Southampton, SO17 1BJ, UK

1 0

Info/Links for new Apache WSRF, WSN & WSDM projects
by Jem Treadwell 09 Dec '04

09 Dec '04

Hi, this is some info that I provided at the f2f about about Apache's new Apollo, Hermes and Muse projects, which I hope will be of interest to many of the organizations involved in OGSA. The info below is a digest of the announcements that Ian Springer of HP sent to the OASIS WSDM, WSRF & WSN technical committees on December 2nd. Please pass the information on to anyone else who may be interested within your own organization. Thanks and regards, - Jem The below links provide info on the new Apollo, Hermes and Muse projects at Apache. It's HP's and Globus' hope that other organizations will choose to use and/or contribute to these projects. If you have any questions about the project, please post to the appropriate mailing lists, as detailed below (subscription required). Thanks! --Ian Springer, senior software engineer, HP Overview of Apollo, Hermes, and Muse Projects ============================================= o Presentation: http://incubator.apache.org/muse/apollo-hermes-muse_overview.ppt o Roadmap: http://incubator.apache.org/muse/apollo-hermes-muse_roadmap.txt Apollo Project Info =================== o Web Site: http://incubator.apache.org/apollo/ o Mailing List: apollo-dev(a)ws.apache.org - Subscribe: send blank email to: apollo-dev-subscribe(a)ws.apache.org - Archive: http://ws.apache.org/mail/apollo-dev/ o SVN Repo: http://svn.apache.org/repos/asf/incubator/apollo/ o Issue Tracking: http://nagoya.apache.org/jira/browse/Apollo o Chat Room: #apache-ws-fx (on irc.freenode.net) o Incubator Project Proposal: http://wiki.apache.org/incubator/ApolloProposal o Incubation Status Tracking Page: http://incubator.apache.org/projects/apollo.html o Mentor: Davanum Srinivas - WS PMC chair, ASF member * dims(a)apache.org, dims(a)yahoo.com * http://webservices.apache.org/~dims/ <http://webservices.apache.org/%7Edims/>, http://blogs.cocoondev.org/dims/ Hermes Project Info =================== o Web Site: http://incubator.apache.org/hermes/ o Mailing List: hermes-dev(a)ws.apache.org - Subscribe: send blank email to: hermes-dev-subscribe(a)ws.apache.org - Archive: http://ws.apache.org/mail/hermes-dev/ o SVN Repo: http://svn.apache.org/repos/asf/incubator/hermes/ o Issue Tracking: http://nagoya.apache.org/jira/browse/Hermes o Chat Room: #apache-ws-fx (on irc.freenode.net) o Incubator Project Proposal: http://wiki.apache.org/incubator/HermesProposal o Incubation Status Tracking Page: http://incubator.apache.org/projects/hermes.html o Mentor: Davanum Srinivas - WS PMC chair, ASF member * dims(a)apache.org, dims(a)yahoo.com * http://webservices.apache.org/~dims/ <http://webservices.apache.org/%7Edims/>, http://blogs.cocoondev.org/dims/ Muse Project Info ================= o Web Site: http://incubator.apache.org/muse/ o Mailing List: muse-dev(a)ws.apache.org - Subscribe: send blank email to: muse-dev-subscribe(a)ws.apache.org - Archive: http://ws.apache.org/mail/muse-dev/ o SVN Repo: http://svn.apache.org/repos/asf/incubator/muse/ o Issue Tracking: http://nagoya.apache.org/jira/browse/Muse o Chat Room: #apache-ws-fx (on irc.freenode.net) o Incubator Project Proposal: http://wiki.apache.org/incubator/MuseProposal o Incubation Status Tracking Page: http://incubator.apache.org/projects/muse.html o Mentor: Davanum Srinivas - WS PMC chair, ASF member * dims(a)apache.org, dims(a)yahoo.com * http://webservices.apache.org/~dims/ <http://webservices.apache.org/%7Edims/>, http://blogs.cocoondev.org/dims/ General Apache Incubator Info ============================= o Web Site: http://incubator.apache.org/ o SVN Repo: http://svn.apache.org/repos/asf/incubator/public/ o Wiki: http://wiki.apache.org/incubator General Apache WS Project Info ============================== o Web Site: http://ws.apache.org/ o Web Site CVS: http://cvs.apache.org/viewcvs.cgi/ws-site/ o Mailing List: general(a)ws.apache.org (general-subscribe(a)ws.apache.org) o IRC: #apache-ws (on irc.freenode.net) o Wiki: http://wiki.apache.org/ws/ -- Jem Treadwell Hewlett-Packard Company Phone: (732) 577-6043 200 Route 9 North Fax: (732) 577-6003 Manalapan, NJ 07726 E-mail: Jem.Treadwell(a)hp.com

1 0

GT4 monitoring and discovery services
by Ian Foster 09 Dec '04

09 Dec '04

The topic arose yesterday of what we're doing in GT4 for monitoring and discovery. I enclose a summary. What I find neat about this is that the WSRF/WSN mechanisms make this come out really nicely.

1 0

On the subject of profiles...
by Steven Newhouse 09 Dec '04

09 Dec '04

Could I draw your attention to some work that went on in the UK over the summer on profiling the web service specifications to build web service grids. http://www.omii.ac.uk/web_service_grids.htm Steven -- ---------------------------------------------------------------- Dr Steven Newhouse Tel:+44 (0)2380 598789 Deputy Director, Open Middleware Infrastructure Institute (OMII) Suite 6005, Faraday Building (B21), Highfield Campus, Southampton University, Highfield, Southampton, SO17 1BJ, UK

1 0