- ogsa-bes-wg - lists.ogf.org

OGSA BES Meeting
by Pulsipher_Darren＠emc.com 22 Aug '06

22 Aug '06

When: Thursday, August 24, 2006 10:30 AM-11:30 AM (GMT-06:00) Central Time (US & Canada). Where: On Line *~*~*~*~*~*~*~*~*~* You are invited to join a meeting hosted by MR DARREN PULSIPHER. Meeting details are listed below. Instant Meeting Details: ------------------------------- Aug. 24, 2006 11:30 am EDT 8:30 am PDT If you are unable to join with the above link, please dial in using one of the phone numbers below: UNITED KINGDOM Toll Number: +44-20-7108-6316 USA Toll Free Number: 866-880-0098 Participant Passcode: 3425861 Instant Net Conference Details: ------------------------------- Meeting Number: SW124357 Meeting Passcode: GGF Meeting Host: MR DARREN PULSIPHER Join Instructions for Instant Net Conference: 1. Join the meeting now: http://www.mymeetings.com/emc/nc/join.php?i=SW124357&p=GGF&t=c 2. Enter the required fields. 3. Indicate that you have read the Privacy Policy. 4. Click on Proceed. EMC² Darren Pulsipher Director of Engineering Grid Business Unit 501-442-9074 Email: Pulsipher_Darren(a)emc.com <mailto:Pulsipher_Darren@emc.com>

1 0

Meeting Minutes
by Pulsipher_Darren＠emc.com 17 Aug '06

17 Aug '06

Aug. 17, 2006 Attendees Darren Mark Ellen Chris Marvin Glen Ian F Michel David S Agenda Go through the document Go through the tracker Action Items - Appendix to be added for general container model. (Ellen) - Trackers have been assigned to the appropriate people as tasks to be completed at this time. Notes - Meeting minutes approved without comment EMC² Darren Pulsipher Director of Engineering Grid Business Unit 501-442-9074 Email: Pulsipher_Darren(a)emc.com <mailto:Pulsipher_Darren@emc.com>

1 0

Re: [ogsa-bes-wg] Create a revised BES spec draft that reflects the decisions of the July F2F mtg
by Ian Foster 17 Aug '06

17 Aug '06

Marvin: I've claimed the pen on the document, but have been finding it hard to find time to make a lot of progress. I will try to do some work on it tomorrow morning. That said, I want to mention an important development that Dave Snelling may or may not have mentioned on calls. Dave argues that we can avoid the need for distinct renderings by defining our interfaces carefully. The basic idea, as I understand it, is that: a) the "core interface" has the basic operations for creating jobs, modifying their status, etc., and an operation for grabbing all of the factory state; b) then, if desired, a WSRF service (for example) can also implement the WS-ResourceProperties, WS-ResourceLifetime, WS-BaseNotification, operations; c) while a WS-Resource service would implement the WS-Resource equivalents of those. So we exploit the power of interface composition to avoid the need for separate bindings. The only problematic issue, as I understand it, is that of faults. The question is how we render faults. The WSRF binding must (by the spec) use WS-BaseFaults. If we can all agree to use that, then we are ok. If not, then we still have problems. Ian. At 01:29 PM 8/4/2006 -0700, Marvin Theimer wrote: >x-ms-exchange-organization-recipient-p2-type: To >Content-Type: text/plain; charset="us-ascii" > >Hi; > >The HPC Profile (HPCP) work depends critically on BES. The recent >face-to-face meeting at Argonne made substantial progress in terms of >reshaping the proposed BES specification in a way that would make it >suitable for supporting the HPCP on top of it. Are there plans to >generate a new revision of the BES specification draft in the near >future? As soon as the revised version comes into existence we'll be able >to seriously start doing the actual HPCP work (which will take place on >the hpcp-ogsa-wg mailing list and in weekly telecom calls that will be >starting shortly). > >Since the HPCP WG is effectively gated on this revised spec, having a >draft of a revised spec sometime in the next week or so would be really >helpful. I would be willing to help rewrite the BES spec if that would be >useful to the BES WG. > >Marvin. _______________________________________________________________ Ian Foster, Director, Computation Institute Argonne National Laboratory & University of Chicago Argonne: MCS/221, 9700 S. Cass Ave, Argonne, IL 60439 Chicago: Rm 405, 5640 S. Ellis Ave, Chicago, IL 60637 Tel: +1 630 252 4619. Web: www.ci.uchicago.edu. Globus Alliance: www.globus.org.

3 3

RE: Re: [ogsa-bes-wg] V21 of the BES draft
by Mark Morgan 16 Aug '06

16 Aug '06

> Let me say again that Mark has done an outstanding job. Thank you > A Q: should I add the items below as trackers? That would probably be best. I suspect that some of these issues need to be discussed in group. Thanks, Mark > > Ian. > > > > Delivered-To: grdfm-ogsa-bes-wg-outgoing(a)mailbouncer.mcs.anl.gov > X-Original-To: grdfm-ogsa-bes-wg(a)mailbouncer.mcs.anl.gov > Delivered-To: grdfm-ogsa-bes-wg(a)mailbouncer.mcs.anl.gov > X-Sender: itf(a)pop.mcs.anl.gov > X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 > Date: Tue, 15 Aug 2006 20:57:37 -0500 > To: "Mark Morgan" <mmm2a(a)virginia.edu>, <ogsa-bes-wg(a)ggf.org> > From: Ian Foster <foster(a)mcs.anl.gov> > Subject: Re: [ogsa-bes-wg] V21 of the BES draft > Sender: owner-ogsa-bes-wg(a)ggf.org > > Mark: > > You have done an outstanding job. This is looking > really very nice, IMHO. > > I'll resist the temptation to take the pen for a quick > edit, but instead just make a few comments: > > 1) I disagree with moving the BES-Activity document to > an appendix: that feels like a funny half-way house. If we > don't want it in the main body of this specification, then I > propose we move it into a separate spec. Either resolution is > fine with me. > > 2) I also disagree with moving the JSDL extension > discussion to an appendix, for the same reason. In this case, > I want to argue for restoring the material (probably just the > first two extensions) in the main body. I can work on more > detailed text if desired. > > 3) Section 5.1 is quite verbose: could we not replace > it with a table? If that is not preferred, then we should add > a table summarizing the attributes. (In both cases, the table > shculd ontain the data we had previously showing number of > occurences--that is useful information.) > > 4) Someone had commented that > Start/StopAcceptingNewActivities should allow for a > "notauthorized" fault. Was it decided that this was not required? > > 5) The description of the response from > TerminateActivities ["The Cancelled element is a boolean > value indicating whether the BES container successfully > (true) cancelled the activity or not (false)."] seems > inconsistent with the earlier text saying that the operation > only passes the request to the activity--it does not confirm > that it succeeded in cancelling it. > > 6) In F.3.2, G.1.2, and elsewhere, I propose that the > example ActivityReferences simply be shown as WS-Addresses, > leaving open the question of what reference parameters may or > may not be included in those WS-Addresses. This > representation is more consistent with our statement in > Section 3 that we do not require WS-Naming syntax, and also > give us one less thing to explain. > > 7) I thought that the text in Appendix A could be > clearer, and also would be more useful in the introduction. I > propose that we remove Appendix A, and place the following > text at the end of the Introduction, which also provides a > useful summary of the Appendices. > > We define in Appendices A-D normative XSD and WSDL for > BES-Management > and BES-Factory, respectively, and in Appendices E and > F non-normative > examples for the two interfaces. > > Recall that the OGF OGSA WG has defined the notion of a > Base Profile: > a specification that places certain constraints on how resource > modeling specifications such as the WSRF or WS-Transfer families > should be used in any OGSA-compliant specification. At > the time of > writing, only an OGSA WSRF Base Profile [OGSA WSRF BP] has been > defined, but others will presumably be produced in the future. > > We have sought to define a BES specification that while not, in > itself, compliant with any OGSA Base Profile, can be > composed with > appropriate other port-types to produce a BES that is > compliant with > any specific OGSA Base Profile. To illustrate how this > composition can > be achieved, we explain in the (non-normative) Appendix H how an > implementor can construct a BES that is compliant with > the OGSA WSRF > Base Profile. > > 8) I also propose the following alternative text for > Appendix I (Appendix H if we remove Appendix I): > > We explained in the Introduction how the BES > specification is designed > to enable the creation of BESs that are compliant with > OGSA Base Profiles > via the composition of BES port-types with other > appropiate port-types. > To illustrate how this can be done, we explain how an > implementor would > create a BES that is compliant with the OGSA WSRF Base Profile. > This material is not intended to be normative. > > 1) A BES that is to be compliant with the OGSA WSRF > Base Profile must > implement, in addition to the BES-Management and BES-Factory > port-types, the WS-ResourceProperties, WS-ResourceLifetime, and > WS-BaseNotification port-types, in a manner compliant with the > OGSA WSRF Base Profile. > > 2) Implementers MUST also ensure that all attributes > given in the > description of the attributes document appear as exactly named > WS-ResourceProperties. Exactly named here implies that > each resource > property must have the QName > > {http://schemas.ggf.org/bes/2006/08/bes-management}attr-name where > attr-name is the name of the attribute used inside the > attributes > document types (e.g., TotalNumberOfActivities, > CommonName, etc.). > > Ian. > > > At 05:26 PM 8/15/2006 -0400, Mark Morgan wrote: > > > Fellow BES'ers, > > I have uploaded to GridForge (and attached to > this email for your > convenience) my revamped version of the BES > specification as agreed to > during last week's telecon. The great majority > of changes reflect > resolutions that we reached on that telecon and > include a re-work of the > state model (both in text and xml form) as well > as a rework of the > attributes or info model (again, in text and > XML form). It is my belief > that the document now constitutes a consistent > story from English > description through XSD and WSDL though by no > means should the document be > considered fully proofed or ready for > ppublishing. The following details > apply: > > The version of the document that I uploaded is > based originally on that > received from Mr. Ian Foster and so should > include many of his changes. As > per the BES telecon discussion, some of the > material in that document has > been moved to an appendix. In particular, the > discussion on JSDL extensions > is now an appendix (in fact, I simply > cut-and-paste that chapter into the > appendix so no editing has been done there and > probably should be before we > go public). > > Also, the specification had been split into > three separate port types; > management, factory, and activity. As per our > discussions, activity is out > of scope for BES but quite reasonable as an > appendix. I therefor removed > this port type from the document proper. > However, I didn't feel like I had > the time nor the vested interest in that port > type necessary to do it > justice. It therefor has not been re-added > into an appendix and if the > group feels like it has a place there, some > work needs to be done to > re-insert it. > > In Ian's original draft, each of the separate > port types had it's own > attributes/properties. However, as per > resolutions on last week's telecon, > this no longer fit the model we had agreed > upon. I have therefor moved all > such attributes into the management port type > (which seems reasonable as one > could construe info model as a management function). > > Finally, just to be clear on how I handled the > state model (as I think this > was one of our key features), I have defined a > new data type called > OverallStatusType which contains exactly one of > bes-factory:New, > bes-factory:Pending, bes-factory:Running, > bes-factory:Cancelled, > bes-factory:Failed, and bes-factory:Finished as > a child element. Each of > these elements in turn has an xsd:any inside > which can be used for arbitrary > specialization or sub-stating. For example, > suppose I wished to reflect > that I was in the Mark Morgan Blocked sub-state > of the Uva VCGR Staging-In > sub-state of the spec. defined Running state. > My XML for that would look > like: > > <bes-factory:OverallStatus > > xmlns:bes-factory="http://schemas.ggf.org/bes/2006/08/bes-factory" > xmlns:vcgr="http://vcgr.cs.virginia.edu/bes/2006/08/states" > > xmlns:morgan="http://mark-morgan.org/bes/2006/08/states"> > > <bes-factory:Running> > <vcgr:Staging-In> > <morgan:Blocked/> > </vcgr:Staging-In> > </bes-factory:Running> > > </bes-factory:OverallStatus> > > > _______________________________________________________________ > Ian Foster, Director, Computation Institute > Argonne National Laboratory & University of Chicago > Argonne: MCS/221, 9700 S. Cass Ave, Argonne, IL 60439 > Chicago: Rm 405, 5640 S. Ellis Ave, Chicago, IL 60637 > Tel: +1 630 252 4619. Web: www.ci.uchicago.edu > <http://www.ci.uchicago.edu/> . > Globus Alliance: www.globus.org <http://www.globus.org/> . > > > _______________________________________________________________ > Ian Foster, Director, Computation Institute Argonne > National Laboratory & University of Chicago > Argonne: MCS/221, 9700 S. Cass Ave, Argonne, IL 60439 > Chicago: Rm 405, 5640 S. Ellis Ave, Chicago, IL 60637 > Tel: +1 630 252 4619. Web: www.ci.uchicago.edu > <http://www.ci.uchicago.edu/> . > Globus Alliance: www.globus.org <http://www.globus.org/> . > > >

2 2

V21 of the BES draft
by Mark Morgan 16 Aug '06

16 Aug '06

Fellow BES'ers, I have uploaded to GridForge (and attached to this email for your convenience) my revamped version of the BES specification as agreed to during last week's telecon. The great majority of changes reflect resolutions that we reached on that telecon and include a re-work of the state model (both in text and xml form) as well as a rework of the attributes or info model (again, in text and XML form). It is my belief that the document now constitutes a consistent story from English description through XSD and WSDL though by no means should the document be considered fully proofed or ready for ppublishing. The following details apply: The version of the document that I uploaded is based originally on that received from Mr. Ian Foster and so should include many of his changes. As per the BES telecon discussion, some of the material in that document has been moved to an appendix. In particular, the discussion on JSDL extensions is now an appendix (in fact, I simply cut-and-paste that chapter into the appendix so no editing has been done there and probably should be before we go public). Also, the specification had been split into three separate port types; management, factory, and activity. As per our discussions, activity is out of scope for BES but quite reasonable as an appendix. I therefor removed this port type from the document proper. However, I didn't feel like I had the time nor the vested interest in that port type necessary to do it justice. It therefor has not been re-added into an appendix and if the group feels like it has a place there, some work needs to be done to re-insert it. In Ian's original draft, each of the separate port types had it's own attributes/properties. However, as per resolutions on last week's telecon, this no longer fit the model we had agreed upon. I have therefor moved all such attributes into the management port type (which seems reasonable as one could construe info model as a management function). Finally, just to be clear on how I handled the state model (as I think this was one of our key features), I have defined a new data type called OverallStatusType which contains exactly one of bes-factory:New, bes-factory:Pending, bes-factory:Running, bes-factory:Cancelled, bes-factory:Failed, and bes-factory:Finished as a child element. Each of these elements in turn has an xsd:any inside which can be used for arbitrary specialization or sub-stating. For example, suppose I wished to reflect that I was in the Mark Morgan Blocked sub-state of the Uva VCGR Staging-In sub-state of the spec. defined Running state. My XML for that would look like: <bes-factory:OverallStatus xmlns:bes-factory="http://schemas.ggf.org/bes/2006/08/bes-factory" xmlns:vcgr="http://vcgr.cs.virginia.edu/bes/2006/08/states" xmlns:morgan="http://mark-morgan.org/bes/2006/08/states"> <bes-factory:Running> <vcgr:Staging-In> <morgan:Blocked/> </vcgr:Staging-In> </bes-factory:Running> </bes-factory:OverallStatus>

4 3

Thursday agenda
by Andrew Grimshaw 16 Aug '06

16 Aug '06

All, Proposed agenda for the Thursday call: Approve minutes - on gridforge Agenda bashing Page by page discussion and approval :-) of v21 of BES document Andrew Grimshaw Professor of Computer Science University of Virginia 434-982-2204 grimshaw(a)cs.virginia.edu

1 0

OGSA BES Meeting
by Pulsipher_Darren＠emc.com 15 Aug '06

15 Aug '06

When: Thursday, August 17, 2006 10:30 AM-11:30 AM (GMT-06:00) Central Time (US & Canada). Where: On Line *~*~*~*~*~*~*~*~*~* You are invited to join a meeting hosted by MR DARREN PULSIPHER. Meeting details are listed below. Instant Meeting Details: ------------------------------- Aug. 17, 2006 11:30 am EDT 8:30 am PDT Click on the following link to join the Audio Conference: http://wbbc.mci.com/wbbcClick2Join/servlet/WBBCClick2Join?cc=1&ph=866-880-00 98&pc=3425861&customHeader=mymeetings If you are unable to join with the above link, please dial in using one of the phone numbers below: UNITED KINGDOM Toll Number: +44-20-7108-6316 USA Toll Free Number: 866-880-0098 Participant Passcode: 3425861 Instant Net Conference Details: ------------------------------- Meeting Number: SW124357 Meeting Passcode: GGF Meeting Host: MR DARREN PULSIPHER Join Instructions for Instant Net Conference: 1. Join the meeting now: http://www.mymeetings.com/emc/nc/join.php?i=SW124357&p=GGF&t=c 2. Enter the required fields. 3. Indicate that you have read the Privacy Policy. 4. Click on Proceed. EMC² Darren Pulsipher Director of Engineering Grid Business Unit 501-442-9074 Email: Pulsipher_Darren(a)emc.com <mailto:Pulsipher_Darren@emc.com>

1 0

Initial document drafts for HPC Profile
by Christopher Smith 14 Aug '06

14 Aug '06

Hi all, I've uploaded the following documents to gridforge: - HPC Profile Application Extension - JSDL extension for describing executables, etc. (https://forge.gridforum.org/sf/go/doc13735?nav=1) - HPC Basic Profile - the skeleton of the profile document with the section for JSDL profiling filled in (for debate :-) ). https://forge.gridforum.org/sf/go/doc13736?nav=1 Please send any comments to the list to get the discussion going, and we'll use the trackers to record any issues that need to be addressed. By the way ... in future I will only use the ogsa-hpcp-wg(a)ggf.org mailing list for discussion of these documents, so please subscribe if you haven't already. Please follow up to ogsa-hpcp-wg. -- Chris

1 0

Updated BES Document
by Ian Foster 12 Aug '06

12 Aug '06

Dear All: I'm very sorry about the slow delivery of the updated BES spec. I thought that I'd be able to send it after my flight out to Vancouver prior to my vacation, but failed to get email connectivity. In any case, I enclose a new document with many changes. If you send comments before Sunday morning, I can try to address them on the flight back Sunday afternoon. I've tried to document some of the primary changes below. However, I really think it is important for people to read the document carefully, as there may well be other things that seemed unimportant to me but are in fact problematic. We should then discuss issues that seem problematic on a telecon. 1) Things that have changed: a) I've broken existing operations out into separate BES-Factory and BES-Management port-types, and added a new BES-Activity port-type. b) I've removed the material on separate WSRF and RMF renderings, and the material on notification, based on the assumption that we can do what David Snelling proposes and define BES in such a way that other desired behaviors (e.g. WSRF-specific or WS-Transfer-specific operations) can be added if/when desired via composition. To this end, I've also introduced the WS-BaseFaults faults. I realize that these changes haven't been approved, so we may need to back them out. But at least this way you can see what it looks like. c) I removed the "laststate" component from the "ActivityStatus" type, because this component seemed to be there specifically to deal with suspended activities, which are not longer part of the core specification. Presumably a BES that supports an extended state model with suspension will need to introduce "laststate" as an extension to the ActivityStatus type. 2) Things that seem problematic, or that are not done: a) We need a new state model section: I think someone is writing one? (I removed what is there.) b) I can't recall the new base states; these need to be entered. c) We need to update the BES-Factory attributes. d) I assume there should be per-activity BES-Activity attributes. I haven't entered any. e) I've introduced "subscription" and "lifetime management" elements as optional JSDL extensions. Certainly people that compose WS-Notification/WS-Eventing and WS-ResourceLifetime, respectively, with BES will want to use these. However, it may be that it is not appropriate to mention them in the BES spec, because they are specific to other WSRF/WS-Transfer specs. (I myself think that they should not be there, but I want to raise the topic to get other people's views.) f) The normative stuff in the appendices hasn't been completed. Regards -- Ian.

1 0

Agenda for telecon
by Andrew Grimshaw 09 Aug '06

09 Aug '06

All, Proposed agenda: Agenda bashing Review each of the "container attributes" - section 5.1, and define it as: MUST SHOULD MAY What is this doing here? If time permits: additional attributes conferee's may suggest - please email to group tonight if possible. If time permits - not likely - trackers A Andrew Grimshaw Professor of Computer Science University of Virginia 434-982-2204 grimshaw(a)cs.virginia.edu

1 0