February 2006 - ogsa-wg - lists.ogf.org

JSDL Workshop at GGF16
by Ali Anjomshoaa 10 Feb '06

10 Feb '06

Dear colleagues, [My apologies for cross-posting] Just a quick announcement of the JSDL-WG Workshop at GGF16. Date: Wed. 15th Feb. Time: 08:30 - 12:00 Room: Mycenae The talks are in the schedule below. We all look forward to seeing you there and to your feedback and contributions towards our ongoing work in the JSDL-WG. Kind regards, Ali (on behalf of the JSDL-WG) JSDL-WG: https://forge.gridforum.org/projects/jsdl-wg/ JSDL-Spec: http://www.gridforum.org/documents/GFD.56.pdf -- ---------------------------------------------------- |epcc| - Ali Anjomshoaa EPCC, University of Edinburgh James Clerk Maxwell Building Mayfield Road E-mail: ali(a)epcc.ed.ac.uk Edinburgh, EH9 3JZ Phone: + 44 (0) 131 650 5818 United Kingdom Fax: + 44 (0) 131 650 6555 ------------------------------------------------------------- ---- GGF16, JSDL Workshop Schedule ---- 08:30 - Welcome and Introductions 08:35 - JSDL Tutorial Andreas Savva (Fujitsu Laboratories Ltd, Japan) Steve McGough (LeSC, Imperial College London, UK) William Lee (Lesc, Imperial College London, UK) 09:20 - GridSAM presentation William Lee, (LeSC, Imperial College London, UK) 09:40 - NAREGI presentation Kazushige Saga (National Institute of Informatics, Japan) 10:00 - *** BREAK *** 10:30 - HPCEuropa presentation Ariel Oleksiak (Poznan Supercomputing and Networking Centre, Poland) 10:50 - Japan Business Grid presentation Andreas Savva (Fujitsu Laboratories Ltd, Japan) 11:10 - UniGrids presentation Michel Drescher (Fujitsu Laboratories of Europe, UK) 11:30 - Platform Computing presentation Christopher Smith (Platform Computing, USA) 11:50 - Conclusions and closing remarks 12:00 - END ----------

1 0

Teleconference minutes - 1 February 2006
by Andreas Savva 10 Feb '06

10 Feb '06

Attached. Also https://forge.gridforum.org/projects/ogsa-wg/document/minutes-20060201/en/1 -- Andreas Savva Fujitsu Laboratories Ltd OGSA Teleconference - 1 February 2006 ===================================== * Participants Mike Behrens (R2AD) Hiro Kishimoto (FJ) Allen Luniewski (IBM) Fred Maciel (Hitachi) Steve McGough (IC) Dejan Milojicic (HP) Takuya Mori (NEC) Andreas Savva (FJ) Chuck Spitz (CA) Jun Tatemura (NEC) Jem Treadwell (HP) Minutes: Andreas Savva * Summary of Actions Action: Andreas will check Greg's email again and followup with Hiro. Action: - Dejan(CDDLM) to provide a CDL for deploying and configuring BLAST - Steve/Andreas(JSDL) to provide a JSDL document for submitting a BLAST job Action: GGF16 panel followup (see detailed list below) * January F2F (01/19) ByteIO minutes approved with no changes * January 25 minutes approved with no changes * January 30 minutes approved with no changes * Basic security profile - Core and Secure channel - Takuya has issued a final call on the list. - Review and comment by next Monday ** "Status of memo" question to Greg No problem with changing the text, but it is not clear if the title could be changed also. Action: Andreas will check Greg's email again and followup with Hiro. ** WSRF BP 1.0 status - WSRF is entering the process towards becoming an OASIS standard - Tom proposed that the WSRF BP should be re-submitted once the WSRF specs become OASIS standards. - There is another document in the GGF pipeline (ByteIO spec) that uses the WSRF BP normatively. The desire is to publish the WSRF BP some time in advance of the end of the public comment of dependent documents. - Hiro proposed waiting until GGF16 or end of February before re-submission but not longer. (No decisions made.) ** RSM License: no update ** CDDLM discussion Jun sent out slides on CDL before the call and the group reviewed them. ** (2) Example 1: Application Server - 'Component provider' defines the components - And in this case also provides the instance of the component (component in the 'running' state) - 'Component user' in this case might also take on the role of a system provider. In other words, the 'component user' may be composing the system for himself or to provide a service to other users - There are some issues with terminology (but perhaps it is unavoidable). - Boundaries here are the components and the roles relative to components ** (3) Component description - CDL does not define how to relate configuration and resource parameters - There is also no requirement that such information be present. The interaction or combination is not defined and is probably an open issue that should be addressed by this group. - Some such information may be present as properties for reference purposes - The semantics of configurable parameters are not defined. It is possible to include semantic description in a separate document or as annotations, etc. - Since this level of description is still too abstract, it was proposed to show a concrete example of JSDL and CDL and how the two relate to each other. - Dejan also suggested doing an implementation fest: - Bring together people developing various components and do a 'reality check' by trying to combine the various components of the EMS architecture. (Different from an interoperability test which brings together people developing the same component.) - And do it as a regular event, e.g., at each GGF. - It was pointed out that the purpose of the 'EMS Scenarios' document is to drill down to that level. Doing a real example, e.g., BLAST, for CDL and JSDL could be useful as a next step. - Agreed to work through such an example at the next GGF. Action: - Dejan(CDDLM) to provide a CDL for deploying and configuring BLAST - Steve/Andreas(JSDL) to provide a JSDL document for submitting a BLAST job ** (4) System composition - Text in red are the results of a refinement of the CDL document - The deployment API expects that all the values in a CDL are instantiated by the time the CDL is submitted. There is no statement on how that refinement is done. ** (5) System template The document on the left is a user 'template' (in contrast, in this presentation component provider templates are yellow). This template is an intermediate description of the system and further refinement is shown on the right side. ** (6)-(8) - There was confusion on the objective of this second example, some of it stemming from the introduction of the term 'job'. The example may be seen as setting up a cluster with a DRM. - It is a more complex example, and it was agreed to concentrate first on the simple case described earlier. ** (9) Further Examples - Clarified that the server/machine/linux boxes essentially represent the same things in the slide. * OGSA(tm) EMS Architecture Scenarios - No objections to the proposal to change the name of the document. - Question about meaning of 'policy' appearing in some of the sequence diagrams (Section 2.5 and some of the Appendices). - 'Policy' is a placeholder for now. - The document is still changing and contains internal inconsistencies. * GGF16 Planning ** Panel: Monday 1:30 - 3:00 Discussed possible candidates for the panel: - JSDL: Steve or one of the other JSDL-WG chairs (ok) - EGEE: Steve will make initial contact with people in EGEE (and cc Hiro) - DAIS: Hiro to ask Malcom - Other possible candidates: - Hiro to ask someone from NAREGI (Japan), Globus (Ian) - Steven Newhouse (OMII) - Vendors: who? - Panel Moderator: Hiro to consult Dave S on candidates. - The panel should be at most 5 people, excluding the moderator. - Send proposal to Hiro on how to publicize the panel ** Information model session - Use the teleconf next Wednesday to prepare for the GGF session. ** GGF16 F2F meeting Agenda proposals: - CDDLM and EMS joint session - Other EMS scenarios (including RSS-WG etc) - Information Model - General session - In particular finalize dates/locations for April F2F and GGF17 F2F meeting * GGF17 F2F - Hiro has speculatively reserved a room both Monday and Saturday at the NAREGI office. * April F2F - April 3-7 seems to be the more popular choice at this moment - SF or London are equally popular

1 1

Teleconference minutes - 8 February 2006
by Andreas Savva 09 Feb '06

09 Feb '06

Minutes attached. https://forge.gridforum.org/projects/ogsa-wg/document/minutes-20060208/en/1 Have a good trip and see you at GGF16. -- Andreas Savva OSGA Teleconference minutes - 8 February 2006 ============================================= * Participants Hiro Kishimoto (Fujitsu) Fred Maciel (Hitachi) Mark Morgan (UVa) Takuya Mori (NEC) Andreas Savva (Fujitsu) Ellen Stokes (IBM) Ravi Subramaniam (Intel) Jem Treadwell (HP) Minutes: Andreas Savva * Summary of Actions Action: Hiro to upload the Profiles to the GGF Editor tracker Action: Hiro will post the panel proposal text to the list and followup with the identified candidates to confirm the final selection. * February 6 minutes approved with no changes * Monday teleconference information (dial-in numbers) will change after GGF16. - Many thanks to HP (Jeffrin) for providing the facilities so far. * Basic security profiles update - Final call finished last Monday - Some minor revisions from Hiro and Jem - Agreed that the profiles can be submitted to the GGF Editor Action: Hiro to upload the Profiles to the GGF Editor tracker * WSRF Basic Profile update - no update * RSM license - Ellen is following up. * Glossary - Data Federation: Accepted 'logical' and added "In OGSA," since this is an OGSA specific definition. - Re-worked definitions for "use case" and "scenarios" merging the two proposals. Jem will upload the document but will not issue a final call. There will be a combined OGSA 1.5 final call (Architecture and Glossary) when Andreas uploads the final version late this week, early next week. * Wikipedia - OGSA entry - Jem has updated the entry (OGSA). The motivation is just to make sure that the correct information is provided in that public forum. More detailed information will be maintained on the GGF site. * GGF16 planning ** Panel discussion - Reviewed Andreas' draft panel description, proposed balance and identified candidates for participants and moderator. - One proposal is to have two moderators, one from industry the other from academia. It is interesting but there was some uncertainty on how well the format would work. - Candidates so far are mostly from academia. Looking for more commercial/industry representatives. Possible candidates: - Tony Hey (MS) - Franco Travostino (Nortel) - David Martin (IBM) - /Someone from Univa/ Action: Hiro will post the panel proposal text to the list and followup with the identified candidates to confirm the final selection. ** Information model session agenda The session will be a working session focusing on the Modeling guidelines (Fred) and the container documents (Ellen) Proposed and accepted that it should be a bottom-up session, starting with the BES container to motivate the more general guidelines discussion---make it clear that the 'guidelines' is based off the process that came up with the container. It should be made very clear that the guidelines are formulated based on work actually done and are not a blue-sky description of an untried process. Expected audience for this session: EMS (mainly) and possibly Data - BES was initially chosen as a candidate since it is a simple(r) component in EMS. Along the same lines of thoughts a likely first candidate in data is the BYTEIO-WG---it deals with files. - It should also be emphasized that the RM design team is not trying to make more work for other WGs. The main work will be done in OGSA; but domain expert collaboration is needed. - A grid view of storage is another candidate (ref. SNIA) * Modeling Guidelines document review There was not sufficient time to review the document in detail. Some comments were to add - information on how to get access to tools (RSM license); - that the process has been used to come up with the BES container model (and is not a blue-sky approach); and - in the introduction that basing the work on CIM is a *proposal* (it is mentioned in the Status section but some people might not look at that section). ** F2F agenda review - Hiro is working to fill in logistical info (location and how to get there) - Agreed to put 'Next F2F' discussion earlier in the agenda. Sometime in the morning is better to make sure that most interested parties are present.

2 1

Proposed agenda for Feb. 8th call
by Hiro Kishimoto 08 Feb '06

08 Feb '06

Hi all, The following is a proposed agenda for OGSA-WG telecon on Feb. 8th Wednesday from 4pm to 6pm (CST). Dial-in numbers for Wednesday: Free: +1-888-452-0308 Intl/Toll: +1-484-644-0505 PIN: 71815 Screen share service will be provided. URL: http://ogsa.glance.net Session key: 0208 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 (Feb. 6th) https://forge.gridforum.org/projects/ogsa-wg/document/minutes-20060206/en/1 OGSA Basic Security Profile final call status (Takuya) IBM RSM academic/SDOs license program update (Jay) Agenda bashing 2) OGSA glossary 1.5 final review (20 min) Jem will lead the last three term definitions. - scenarios, usecase, data federation 3) 2) GGF16 prep (30 min) OGSA round table panel @ Monday > - Panel preparation: no update yet. > - Hiro is looking for participants. > - Proposals for candidates, etc, should be sent to Hiro before the > next call. OGSA back-to-back F2F meeting on Friday - Hiro will send out proposed agenda before the call. Updated attendees list https://forge.gridforum.org/projects/ogsa-wg/document/OGSA-WG-GGF16-GGF17-A… 4) Information model discussion (60 min) > Fred updated the modeling guidelines document. It's starting to take > shape. The latest version can be found at: > > http://forge.gridforum.org/projects/ogsa-wg/document/Modeling_Guidelines > /en/ > > We will review this document on the teleconference next wednesday, so > please give a look. BTW, Ellen will post updates of her documents too. 5) Wrap up AOB <NEXT CALL> GGF16 (Athens): Feb. 13-16 OGSA-WG F2F meeting (NTUA @ Athens): Feb. 17 -- Hiro Kishimoto

1 1

RE: [ogsa-wg] Trackers
by Treadwell, Jem 08 Feb '06

08 Feb '06

Hi Mark, Near the bottom of the left-hand index panel there's an Administration menu, which has a Tracker Admin item. From there you can select your tracker and delete it. - Jem > -----Original Message----- > From: owner-ogsa-wg(a)ggf.org [mailto:owner-ogsa-wg@ggf.org] On > Behalf Of Mark Morgan > Sent: Wednesday, February 08, 2006 9:06 AM > To: ogsa-wg(a)ggf.org; ogsa-naming-wg(a)ggf.org > Subject: [ogsa-wg] Trackers > > While attempting to learn how to use trackers in Gridforge, I > created one which I wish to delete. How do I do this? I > can't seem to find a delete button anywhere. > > -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

Trackers
by Mark Morgan 08 Feb '06

08 Feb '06

While attempting to learn how to use trackers in Gridforge, I created one which I wish to delete. How do I do this? I can't seem to find a delete button anywhere. -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-wg] Glossary definitions for discussion on Wednesday's telecon
by Subramaniam, Ravi 07 Feb '06

07 Feb '06

Hi Jem, I have added my suggestions for modifications to proposed definitions. Would you be able to include the mods as one input for the Wed discussion? For data federation, I added 'logical integration' I think the word 'contract' for a use case sounds rather too severe :-). My experience seem to suggest that a use case also has environment, goals etc. Please see below for modifications/additions. Ravi a. Data Federation: The logical integration of multiple services or data resources so that they can be accessed as if they were a single service. b. Use case: A use case captures all interactions of an agent or entity with a system and/or its constituents and the expected behavior of the parties as a consequence where such interactions are directed towards and relevant to achieving/meeting a specific explicit goal. Such a capture could also include the environment, context and modes salient to that interaction. c. Scenario: A scenario is a specific sequence or path of interactions from initiation to goal occurring within a particular environment and/or context and defined by a particular mode of usage. A use case may contain multiple scenarios. d. Mode: is a particular functioning condition or arrangement. -----Original Message----- From: owner-ogsa-wg(a)ggf.org [mailto:owner-ogsa-wg@ggf.org] On Behalf Of Treadwell, Jem Sent: Tuesday, February 07, 2006 8:28 AM To: ogsa-wg Subject: [ogsa-wg] Glossary definitions for discussion on Wednesday's telecon Hi, the three definitions below are the last that are planned for the OGSA Glossary v1.5, and will be discussed on Wednesday's call. Thanks to Andreas for providing the use case and scenario definitions, and to the OGSA-D team for data federation. Please let me know if you have any comments. Thanks, - Jem Data federation: The integration of multiple services or data resources so that they can be accessed as if they were a single service. Use case: A use case captures a contract between the stakeholders of a system about its behavior. Different sequences of behavior, or scenarios, can unfold, depending on the particular requests made and conditions surrounding the requests. The use case collects together those different scenarios. OGSA use cases are high-level and described in a casual style. They are not at the level of detail required for a formal requirements analysis but are meant to provide sufficient detail to inform the architectural definition process. Source: "Writing Effective Use Cases," Alistair Cockburn, Addison-Wesley Professional; 1st edition (January 15, 2000) Scenario: A use case scenario contains a sequence of steps showing how their actions and interactions unfold. OGSA scenarios are high-level and described in a casual style. See also use case. Source: "Writing Effective Use Cases," Alistair Cockburn, Addison-Wesley Professional; 1st edition (January 15, 2000) ________________________________ Jem Treadwell Hewlett-Packard Company 6000 Irwin Road Mount Laurel, NJ 08054 Phone: 856-638-6021 Fax: 856-638-6190 E-mail: Jem.Treadwell(a)hp.com

1 0

Glossary definitions for discussion on Wednesday's telecon
by Treadwell, Jem 07 Feb '06

07 Feb '06

Hi, the three definitions below are the last that are planned for the OGSA Glossary v1.5, and will be discussed on Wednesday's call. Thanks to Andreas for providing the use case and scenario definitions, and to the OGSA-D team for data federation. Please let me know if you have any comments. Thanks, - Jem Data federation: The integration of multiple services or data resources so that they can be accessed as if they were a single service. Use case: A use case captures a contract between the stakeholders of a system about its behavior. Different sequences of behavior, or scenarios, can unfold, depending on the particular requests made and conditions surrounding the requests. The use case collects together those different scenarios. OGSA use cases are high-level and described in a casual style. They are not at the level of detail required for a formal requirements analysis but are meant to provide sufficient detail to inform the architectural definition process. Source: "Writing Effective Use Cases," Alistair Cockburn, Addison-Wesley Professional; 1st edition (January 15, 2000) Scenario: A use case scenario contains a sequence of steps showing how their actions and interactions unfold. OGSA scenarios are high-level and described in a casual style. See also use case. Source: "Writing Effective Use Cases," Alistair Cockburn, Addison-Wesley Professional; 1st edition (January 15, 2000) ________________________________ Jem Treadwell Hewlett-Packard Company 6000 Irwin Road Mount Laurel, NJ 08054 Phone: 856-638-6021 Fax: 856-638-6190 E-mail: Jem.Treadwell(a)hp.com

1 0

Teleconference minutes - 6 February 2006
by Andreas Savva 07 Feb '06

07 Feb '06

Minutes attached. https://forge.gridforum.org/projects/ogsa-wg/document/minutes-20060206/en/1 -- Andreas Savva OGSA Teleconference Minutes - 6 February 2006 ============================================= * Participants Mike Behrens (R2AD LLC) Dave Berry (NeSC) Hiro Kishimoto (Fujitsu) Fred Maciel (Hitachi) Tom Maguire (EMC) Takuya Mori (NEC) Andreas Savva (Fujitsu) Jem Treadwell (HP) Minutes: Andreas Savva * Summary of Actions Action: Tom will update the WSRF BP draft and do final call with next Monday as the deadline. Action: Hiro to confirm the consensus on the definition of the AbstractName (unique in space and time) Action: Dave Berry to propose additional (or other) references for Data or DAIS. Action: Andreas to prepare a new draft and issue a final call. The call will probably overlap GGF16 and to be concurrent with the Glossary final call. * February 1 minutes approved with no changes * Basic security profile - final call - Hiro sent out a few minor comments to the list - Jem is planning to read the documents this week * WSRF BP 1.0 status - New draft with some minor edits posted to gridforge. - As discussed briefly on the last call there is a proposal to delay the submission, or at least the publication of this profile, until WSRF becomes an OASIS standard. This is to avoid having to change the profile soon after it is published. - Tom and Hiro conferred with the WSRF TC chair (Dave Snelling) and clarified that when the WSRF specs become OASIS stanards there will be no namespace changes. The only change is in the location where the documents are kept. [So presumably only the references section needs to be updated.] - Proposed and agreed that the WSRF BP should be prepared and submitted for publication; and ask that the GGF Editor not publish it until the WSRF documents are published by OASIS. - In this way the WSRF BP will be assigned a GFD number and other documents now making their way through the GGF pipeline can refer to it in a stable manner. Action: Tom will update the WSRF BP draft and do final call with next Monday as the deadline. * RSM license - no update * GGF16 preparation - Unfortunately Tom cannot attend GGF16 due to work commitments. He will try to call in during the OGSA sessions. - Panel preparation: no update yet. - Hiro is looking for participants. - Proposals for candidates, etc, should be sent to Hiro before the next call. * OGSA 1.5 review Reviewed draft 5 uploaded to gridforge before the call. - Infrastructure: Approved text for Naming (also needs Andrew's review); transactions (with minor changes to references); and workflow. - For the references: In the case of unpublished drafts that have been submitted to a standards body then refer to the WG or TC home page. For example refer to the OASIS WS-TX TC in the case of WS-BusinessActivity. Action: Hiro to confirm the consensus on the definition of the AbstractName (unique in space and time is best effort?) - EMS: Approved deletion of Figure 4 and associated text; changes in terminology to use EPRs; confirmed that 'resource handle' is no longer used and deleted it from the Glossary; change of figure for BLAST job scenario; deletion of PSHS; change in sections in interactions with OGSA (logging). Minor comments: - "WSDM managed resource" and other mentions of WSDM should be cast as examples. - Figure 4: 'configuration' is truncated; check fonts - Data: Approved new text and figures. - Information services: Minor revision to Logging section to highlight persistency. - log aggregation is a topic that some people expected to see discussed in this section. Agreed to leave as future work. - INFOD: requires a document reference - References: Confirmed new style for references for GGF published documents. Yellow highlighted entries need to be double checked using the rule described earlier. - DAIS reference might need update. Action: Dave Berry to propose additional (or other) references for Data or DAIS. Action: Andreas to prepare a new draft and issue a final call. The call will probably overlap GGF16 and to be concurrent with the Glossary final call. * Other business The Data architecture document is nearly ready for an initial full review by the OGSA-WG. Plan to put it on the agenda of a call after GGF.

1 0

Modeling guidelines document -- please review for teleconference on Wednesday
by Fred Maciel 07 Feb '06

07 Feb '06

Hi, I updated the modeling guidelines document. It's starting to take shape. The latest version can be found at: http://forge.gridforum.org/projects/ogsa-wg/document/Modeling_Guidelines /en/ We will review this document on the teleconference next wednesday, so please give a look. BTW, Ellen will post updates of her documents too. Regards, Fred Maciel Hitachi America R&D

1 0