- ogsa-wg - lists.ogf.org

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

FINAL CALL Document: OGSA Basic Security Profile 1.0 - Core v005 (resend)
by Takuya Mori 06 Feb '06

06 Feb '06

I'm resending the final call message. Please ignore my previous final call message, because there is no voting procedure for GGF documents. (And we don't use the daylight saving time right now.) ---- The final call document for the OGSA Basic Security Profile 1.0 - Core is available for download at the link below. https://forge.gridforum.org/projects/ogsa-wg/document/draft-ggf-ogsa-basic-… Please review and positive acknowledge with an email to the mailing list with your comment for submission from the workgroup to the GGF Editor. Please send your comment on the mailing list by Monday, February 6 COB (EST). If your have a negative comment on the profile, please include precise reasons so that we may address any substantive issues you may have prior to submission. Thanks, Takuya

2 1

FINAL CALL Document: OGSA Basic Security Profile 1.0 - Secure Channel v017 (resend)
by Takuya Mori 06 Feb '06

06 Feb '06

I'm resending the final call message. Please ignore my previous final call message, because there is no voting procedure for GGF documents. (And we don't use the daylight saving time right now.) ---- The final call document for the OGSA Basic Security Profile 1.0 - Secure Channel is available for download at the link below. https://forge.gridforum.org/projects/ogsa-wg/document/draft-ggf-ogsa-basic-… Please review and positive acknowledge with an email to the mailing list with your comment for submission from the workgroup to the GGF Editor. Please send your comment on the mailing list by Monday, February 6 COB (EST). If your have a negative comment on the profile, please include precise reasons so that we may address any substantive issues you may have prior to submission. Thanks, Takuya

2 1

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

06 Feb '06

Hi all, The following is a proposed agenda for OGSA-WG telecon on Feb. 6th Monday from 4pm to 6pm (CST). The dial-in number for Monday; Free: +1-866-639-4741 Toll: +1-574-935-6703 PIN: 8980700 Screen share service will be provided. URL: http://ogsa.glance.net Session key: 0206 See more explanation: http://www-unix.gridforum.org/mail_archive/ogsa-wg/2004/06/msg00077.html 1) Early discussion (20 min) Note taker assignment Roll call Telecon minutes approval (Feb. 1st) https://forge.gridforum.org/projects/ogsa-wg/document/minutes-20060201/en/1 OGSA Basic Security Profile final call status (Takuya) OGSA WSRF BP 1.0 final call status (Tom) IBM RSM academic/SDOs license program update (Jay) Agenda bashing 2) GGF16 prep (30 min) From Feb. 1st minutes: > * 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 3) Arch 1.5 final text review (60 min) Andreas uploaded new draft to GridForge. > So here's a new draft (draft 5). It includes changes in Infrastructure, > EMS, Data, among other sections. Thanks, in particular, to Dave Berry > for pointing out a number of places that needed update. https://forge.gridforum.org/projects/ogsa-wg/document/draft-ggf-ogsa-spec-1… 4) Wrap up (10 min) AOB <NEXT CALL> Feb. 8 (Wed): Info model, EMS design team GGF16 prep GGF16 (Athens): Feb. 13-16 OGSA-WG F2F meeting (NTUA @ Athens): Feb. 17 -- Hiro Kishimoto

1 0

OGSA 1.5 draft 5
by Andreas Savva 06 Feb '06

06 Feb '06

I don't recall Hiro sending out a proposed agenda for Monday's call but I think "OGSA and Glossary 1.5" review should be on the agenda. So here's a new draft (draft 5). It includes changes in Infrastructure, EMS, Data, among other sections. Thanks, in particular, to Dave Berry for pointing out a number of places that needed update. https://forge.gridforum.org/projects/ogsa-wg/document/draft-ggf-ogsa-spec-1… -- Andreas Savva Fujitsu Laboratories Ltd

1 0