Re: [geclipse-dev] A question to workflows

["David Johnson" <d.johnson@xxxxxxxxxxxxx>]

2008/5/13 Stuempert, Mathias IWR <mathias.stuempert@xxxxxxxxxx>:
>
>  I agree and I am still waiting for comments from our WF experts!
>
>  Cheers, Mathias
>

I thought this discussion was finished, as what Pawel said is exactly
correct when he said:

"It is strictly middleware decision. We should just have full
worklflow description, possibly with some indications for middleware
how it should deal with such cases. "critical" or "crucial" parameter
could be good start."

g-Eclipse does not and should not orchestrate or manage the workflows,
as that's what the middleware does. This is the case with gLite, and
the failing behaviour Mathias originally described is most likely
purely up to gLite. I think the JDL is probably correct, but obviously
we can't discuss this unless you post the JDL to look at.

Indicating how the middleware should deal with cases would be nice,
but if we introduce these kinds of parameters into a workflow, there
will never be a guarantee a middleware's workflow engine will support
it. In particular, we need to ask if gLite supports this kind of
specification of workflow job criticality, along with GRIA's way of
doing things. Off the top of my head, I'm not sure they do.

-David