All, It has been brought to my attention that the BES spec is mute on how long information about the status of an activity is kept around once it has transitioned to cancelled, finished, or failed. (This is a problem with many queuing systems as well.) I propose that I add a sentence explicitly stating that it is undefined how long status information will persist once an activity enters one of those three states. Thoughts? A Andrew Grimshaw Professor of Computer Science University of Virginia 434-982-2204 grimshaw@cs.virginia.edu
I agree ________________________________ From: ogsa-bes-wg-bounces@ogf.org [mailto:ogsa-bes-wg-bounces@ogf.org] On Behalf Of Andrew Grimshaw Sent: Wednesday, September 13, 2006 7:21 PM To: ogsa-bes-wg@ggf.org Subject: [OGSA-BES-WG] Something else All, It has been brought to my attention that the BES spec is mute on how long information about the status of an activity is kept around once it has transitioned to cancelled, finished, or failed. (This is a problem with many queuing systems as well.) I propose that I add a sentence explicitly stating that it is undefined how long status information will persist once an activity enters one of those three states. Thoughts? A Andrew Grimshaw Professor of Computer Science University of Virginia 434-982-2204 grimshaw@cs.virginia.edu
Andrew: We could also make this a property of the BES, that could be discoverable. But I am ok with it being undefined. Ian. At 07:21 PM 9/13/2006 -0400, Andrew Grimshaw wrote:
All,
It has been brought to my attention that the BES spec is mute on how long information about the status of an activity is kept around once it has transitioned to cancelled, finished, or failed. (This is a problem with many queuing systems as well.) I propose that I add a sentence explicitly stating that it is undefined how long status information will persist once an activity enters one of those three states.
Thoughts?
A
Andrew Grimshaw
Professor of Computer Science
University of Virginia
434-982-2204
grimshaw@cs.virginia.edu
-- ogsa-bes-wg mailing list ogsa-bes-wg@ogf.org http://www.ogf.org/mailman/listinfo/ogsa-bes-wg
_______________________________________________________________ Ian Foster -- Weblog: http://ianfoster.typepad.com Computation Institute: www.ci.uchicago.edu & www.ci.anl.gov 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 --- Globus Alliance: www.globus.org
I propose that I add a sentence explicitly stating that it is undefined how long status information will persist once an activity enters one of those three states.
+1 Steven -- ---------------------------------------------------------------- Dr Steven Newhouse Mob:+44(0)7920489420 Tel:+44(0)23 80598789 Director, Open Middleware Infrastructure Institute-UK (OMII-UK) c/o Suite 6005, Faraday Building (B21), Highfield Campus, University of Southampton, Highfield, Southampton, SO17 1BJ, UK
participants (4)
-
Andrew Grimshaw -
Ian Foster -
Pulsipher_Darren＠emc.com -
Steven Newhouse