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

Re: [OGSA-BES-WG] [ogsa-hpcp-wg] HPC Profile, BES and JSDL experiences document
by Steven Newhouse 07 Aug '07

07 Aug '07

All, Glenn thanks for this. In thinking how we can develop an experience document for HPCP, BES & JSDL this is an excellent start. In validating HPCP I think we need to make sure we tick boxes for the BES and JSDL specs. From a HPCP perspective the only real differences are (I think): * HPCP does not require that vector operations are support (while BES does) * JSDL has many more elements beyond the minimum for HPC Application profile. Could the JSDL group expand on how they would cover this. Do we need to develop a list of which implementations support which elements? Or have a JSDL document that exercises different JSDL feature sets? BES-Activity port types are now a non-normative component in the BES specification. The BES & HPCP specs are going through their final GFSG review before being published. So that we can move ahead on the interop testing - and expanding on Glenn's list - could someone from each group also report back on: * Are they willing and able to be involved in an interop activity leading towards SC07 * What implementation will they be using for the interop? * Will they be consuming and endpoint and/or contributing an endpoint? * Which version of the specifications does their implementation comply with? (SC06, pre public-comment, post public-comment, ...) * How long do they think it will take to update their implementation to match their final specification? * Who is the contact point and where are they - for the purposes of arranging telecons? * Are they on the HPCP list - please get on it so that can be used as the single communication point - cross-posting bad & non-archived communication very bad. * Do you support the HPCP username & password and/or the X.509 security framework? SC07 is not that far away so I feel we need to start the telecons and start driving the interop activities before we all vanish on vacation. Regards, Steven -----Original Message----- From: ogsa-hpcp-wg-bounces(a)ogf.org [mailto:ogsa-hpcp-wg-bounces@ogf.org] On Behalf Of Glenn Wasson Sent: Wednesday, August 01, 2007 8:08 AM To: ogsa-hpcp-wg(a)ogf.org Subject: [ogsa-hpcp-wg] HPC Profile, BES and JSDL experiences document Everyone, I have created a potential outline for the experiences document for HPC Profile, BES and JSDL. As you all know, each of these specs needs an experiences report as part of the OGF process and this document could satisfy that requirement for all 3. Please have a look. We are hoping to fill out the document based on experiences gained doing an interop demo for SC07. The exact scenarios for this demo are still to be decided, but right now we are looking for groups that want to be involved. Anyone who has an implementation (of the latest versions) of HPCP, BES and/or JSDL can potentially contribute to the demo and the document. Our interop demo at SC06 was very successful and we're looking forward to an expanded version this year. Please let me know if you are interested in taking part in the demo and we will set up a call/list/wiki for this. Glenn

2 1

wsa namespace typo in BES doc?
by Glenn Wasson 13 Jul '07

13 Jul '07

All, I noticed a typo in the BES v35 document. The WSA namespace given in section 1.2 (page 5) is http://www.w3.org/2005/03/addressing, while the WSA namespace used in all the example messages in appendix D is http://www.w3.org/2005/08/addressing. I assume 2005/08 is correct, but I am not sure. Glenn

2 1

Final Call on response to BES Public Comments
by Steven Newhouse 06 Jul '07

06 Jul '07

Following on from the telecon this morning the final alterations have been made to the BES specification to resolve the public comments. Minutes from the meeting taken by Mark Morgan are here - http://forge.ogf.org/sf/docman/do/downloadDocument/projects.ogsa-bes-wg/doc…. A change tracked version 35 has been uploaded to Gridforge (http://forge.ogf.org/sf/docman/do/downloadDocument/projects.ogsa-bes-wg/doc…) and a clean PDF version is attached. If you have issues as to how the public comments have been resolved now is the time to raise them. Next Friday (13th!) the document will be submitted back to the Editor for publication. Issues raised that are not related to the public comment will be left for future revisions of the document. We are nearly there. Many thanks for all your contributions over the years. Steven For the (remaining) BES Chairs.

1 0

Telecon - Friday 6th July 2007
by Steven Newhouse 06 Jul '07

06 Jul '07

Apologies for the confusion... this telecon is tomorrow (Friday) not today at 1600 UK time. I have provided some provisional responses for discussion on the telecon of the unresolved public comments. USA dialin - 1 866 500 6738 2719140 # No direct UK dialin Time: USA West Coast: 0800, UK: 1600 Duration: 1hr Agenda IPR Notice Agenda Bashing Resolved Issues from Public Comment - See responses on GridForge Unresolved Issues from Public Comment - Scope the generation of unique BES activity identifier (From BD). P21: This refers to a unique identifier provided by the client when creating an activity. If this optional extension is supported and the unique identifier is used again to create an activity then the second attempt should be considered part of the initial attempt. It is not the responsibility of the BES to maintain or monitor uniqueness of the identifier over time... just to map any provided to identifier to any previous attempts to start an activity. - JSDL Elements dealing with complex processor architectures (e.g. multi-core) (From SZ). This is a matter for JSDL to extend their processor representation model. The current BES resource model supports collections of homogeneous clusters (i.e. so BES can represent a heterogeneous resources) and this would be one approach to dealing with this issue in the interim. - Representation of queues within a BES container (from SZ). JSDL supports the specification of resource requirements and of specific hosts as part of the job specification. Queues cannot be directly specified in JSDL nor are they directly represented in the BES resource model. However, if there are specific resources represented by the BES that the job should be placed on then these can be specified in the JSDL and it is up to the BES to respect the resource request and place the activity accordingly. - Inclusion of Failed activities into TotalNumberOfActivities and failed lifetime (from SZ). See table on Page 14. The text in the box should be altered to better reflect the text in section 6.1.4. If an activity is still known to the BES then it is reported in this count - including failed or complete activities. How long these activities remain registered in the system is implementation dependent. - Author, Contributor and Acknowledgements Lists (from SN). Addition of Mark Morgan from UVa as an author and Liang ZHONG from Beihang University as a contributor. Edit and last call before submission

1 1

Telecon - 6th July 2007
by Steven Newhouse 05 Jul '07

05 Jul '07

Dialin to be provided: Time: USA West Coast: 0800, UK: 1600 (This avoid OGSA) Duration: 1hr Agenda IPR Notice Agenda Bashing Resolved Issues from Public Comment - See responses on GridForge Unresolved Issues from Public Comment - Scope the generation of unique BES activity identifier (From BD). - JSDL Elements dealing with complex processor architectures (e.g. multi-core) (From SZ). - Representation of queues within a BES container (from SZ). - Inclusion of Failed activities into TotalNumberOfActivities and failed lifetime (from SZ). - Author, Contributor and Acknowledgements Lists (from SN). Edit and last call before submission

1 1

Response to public comments
by Steven Newhouse 26 Jun '07

26 Jun '07

All, https://forge.gridforum.org/sf/docman/do/downloadDocument/projects.ogsa-bes… I have uploaded a new draft to GridForge of the specification (v34) that is fully change tracked. The PDF version attached is clean with no change tracking. This version includes editorial fixes identified through the public comments and (hopefully) non-controversial suggestions for changes. The public comments have been updated with the changes made and I believe the following items need to be resolved before resubmission. I have not propagated any changes through to the normative specification. I'll do that once these proposed changes have been accepted. A time for the telecom will be proposed shortly. Steven Telecon Agenda Scope the generation of unique BES activity identifier (From BD). JSDL Elements dealing with complex processor architectures (e.g. multi-core) (From SZ). Representation of queues within a BES container (from SZ). Inclusion of Failed activities into TotalNumberOfActivities and failed lifetime (from SZ). Author, Contributor and Acknowledgements Lists (from SN).

1 0

Specification Authors and Contributors
by Steven Newhouse 26 Jun '07

26 Jun '07

All, The BES public comment ended last week. I am currently doing a final pass over the document and the comments to identify the substantive issues for discussion at an upcoming telecon - time to be confirmed. The current author list is: Foster, Grimshaw, Lane, Lee, Newhouse, Pickles, Pulsipher, Smith & Theimer. If you are NOT on this list and believe you should be an author please let me know. Also, if you feel you have made a contribution that you feel should be acknowledged - currently there are none - then also let me know. Many thanks, Steven

3 2

JSDL documents in public comment
by Andreas Savva 20 Jun '07

20 Jun '07

[Apologies for the cross-posting.] This is a reminder that JSDL-WG has two documents in public comment until July 10. We'd appreciate people reviewing these documents and posting their comments to the public comment tracker. In particular the "JSDL HPC Profile Application Extension" document has already been implemented as part of the HPC Profile SC06 interop. It would be fine for people that have already implemented it to put in a comment to that effect. The second document "JSDL SPMD Application Extension" addresses MPI application requirements. Both documents are fairly short and should not take too long for you to review. > I'd like to alert you to two new documents that have started public > comment. Please find all documents in public comment here: > http://www.ogf.org/gf/docs/?public_comment > > For the recommendation track: > > JSDL HPC Profile Application Extension, Version 1.0. M. Humphrey > et al., via JSDL-WG. > > JSDL SPMD Application Extension, Version 1.0. A. Savva, via > JSDL-WG. > -- Andreas Savva

1 0

BES activities' states
by Aleksandr Konstantinov 25 May '07

25 May '07

Dear BES group, After reading "OGSA Basic Execution Service, Version 1.0" document I've got an impression that BES bothers about state of activity a lot. Significant amount of document is dedicated to how states are combined, represented and managed by clients. But in BES interfaces I could find almost nothing for states' management. Only related operation seems to be TerminateActivities. Are there any plans to introduce operations for states' management? Or is it supposed to be done through extensions to BES? If so, then what would be a prefered way to do that from BES point of view - separate service, additional porttype for same service, additional elements in TeminateActivities request? Best regards, A.K. --

2 1

Globus OGSA-BES
by Morris Riedel 02 Apr '07

02 Apr '07

Hi, (1) ### Action: Morris provides information from Charles about Globus OGSA-BES implementation See installer at: < <http://www-unix.mcs.anl.gov/~bacon/globus-sc06-all> http://www-unix.mcs.anl.gov/~bacon/globus-sc06-all-source.tar.gz> And scripts: < <http://www-unix.mcs.anl.gov/~bacon/sc2006> http://www-unix.mcs.anl.gov/~bacon/sc2006- scripts.tar.gz> Comment from Charles was: As a reminder, this is all demo code and not supported by the GRAM development team beyond the SC demo. (2) According to the Annex, KTH provides Globus expertise in JRA3. However, I would recommend that you get in contact with UEDIN that (according to the Annex) are responsible for Globus expertise in JRA1 - OGSA-BES. (3) I would like to thank Charles for his efforts in collecting this material. Have fun with it, Morris ---------------------------------------------------------------------------- ---- Morris Riedel SW - Engineer Distributed Systems and Grid Computing Division Central Institute of Applied Mathematics Research Centre Juelich Wilhelm-Johnen-Str. 1 D - 52425 Juelich Germany Email: <mailto:m.riedel@fz-juelich.de> m.riedel(a)fz-juelich.de Info: <http://www.fz-juelich.de/zam/ZAMPeople/riedel> http://www.fz-juelich.de/zam/ZAMPeople/riedel Phone: +49 2461 61 - 3651 Fax: +49 2461 61 - 6656 Skype: MorrisRiedel 'We work to improve ourselves and the rest of mankind.'

1 1