For those dialing in from outside the USA (why?) try 1-203-480-8000 Steven From: ogsa-bes-wg-bounces@ogf.org [mailto:ogsa-bes-wg-bounces@ogf.org] On Behalf Of Steven Newhouse Sent: Thursday, July 05, 2007 9:25 AM To: ogsa-bes-wg@ogf.org Subject: [OGSA-BES-WG] Telecon - Friday 6th July 2007 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