Re: [geclipse-dev] Information on JSDL and workflows

[Nicholas Loulloudes <loulloudes.n@xxxxxxxxxxxx>]

Hi Ashish,

Since the document has no direct connection to g-Eclipse i don't think there is a need to add it into our internal website.

But in any case i attach it to this response..

Thanks.


Ashish Thandavan wrote:

Hi Nicholas,

Sounds very interesting indeed. I'm not sure if the whole survey
document has other useful stuff, but perhaps you could post it to the
internal section of our website?

Thanks!

Regards,
Ashish

Nicholas Loulloudes wrote:
  

Hi all,

After the discussion we had during our meeting yesterday in regard to
the use of JSDL in workflows, i come across the following information
that maybe useful.

This was obtained through the JSDL experience survey that the
*"C3Grid"* project has submitted to OGF's JSDL-WG. Apparently C3Grid
is developing a Grid technology solution for Earth System Science and
one of their main concerns is the support of workflows using JSDL.
Below i quote their remarks on the above./
/

/"A major concern of our project was the support of workflows. Within
C3Grid, a simple, proprietary XML dialect for DAG-style job
definitions has been designed and implemented. However, JSDL does not
directly support the connection of output files from one job to input
files of another job./

/To overcome this deficiency, the <jsdl:DataStaging> “name” attribute
has been used for this: the workflow engine detects identical values
of this attribute and connects the corresponding data staging elements
from two JSDL definitions as input and output. Then, the scheduler
dynamically inserts data transfer tasks into the workflow depending on
job and network allocation decisions./

/To this end, the DataStaging contents are interpreted as follows:/

   *

      /No <jsdl:Source> and no <jsdl:Target> leads to an automatic
      transfer injection by the scheduler, depending on its decisions./

   *

      /A <jsdl:Source> and no <jsdl:Target> leads to an import from a
      user-defined source to a scheduler-selected target, depending on
      its decisions. This applies to data within the workflow at the
      beginning of a branch within the graph./

   *

      /No <jsdl:Source> and a <jsdl:Target> leads to an export from a
      scheduler-selected source (based on previous decisions) to a
      user-defined target. This applies to data within the workflow at
      the end of a branch within the graph./

/Regarding the <jsdl:URI> element, project-specific namespaces are used."/



If the above is considered to be useful, let me know and i can provide
you the whole survey document.


Best regards,

Nicholas
-- 
_________________________________________________

Nicholas Loulloudes
High Performance Computing Systems Laboratory (HPCL)
University of Cyprus,
Nicosia, Cyprus

Tel:  +357-22892663
Email: loulloudes.n[at]cs.ucy.ac.cy
  
------------------------------------------------------------------------

_______________________________________________
geclipse-dev mailing list
geclipse-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/geclipse-dev
  
    

_______________________________________________
geclipse-dev mailing list
geclipse-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/geclipse-dev
  

-- 
_________________________________________________

Nicholas Loulloudes
High Performance Computing Systems Laboratory (HPCL)
University of Cyprus,
Nicosia, Cyprus

Tel:  +357-22892663
Email: loulloudes.n[at]cs.ucy.ac.cy

Attachment: JSDL Experience Survey (C3Grid).doc
Description: MS-Word document

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature