[jsdl-wg] FYI: workflow discussion (was [Fwd: [ogsa-wg] Materials for tomorrows call])
Andreas Savva
andreas.savva at jp.fujitsu.com
Wed Nov 29 22:41:50 CST 2006
Please attend the OGSA-WG call. Participation is open.
As additional background, at the last OGSA F2F (just before SC06) there
was a decision to set up a design team to research workflow issues
before deciding what kind of normative work should be undertaken, and in
which group. There is also a session planned for this for OGF19.
Andreas
Ravi Madduri wrote:
> Andreas
> How can one be part of this discussion on workflow ? Please let me know
>
> Thanks
>
> Andreas Savva wrote:
>> I think the material to the attached email should be of interest to at
>> least a few people on this list.
>>
>> Note that the call referred to is today at 1pm UTC, if you would like to
>> attend.
>>
>>> The following is a proposed agenda for OGSA-WG telecon on Nov. 30th.
>>> Thursday from 7am - 9am (CST).
>>>
>>> ** attention: new international number **
>>>
>>> Dial-in numbers for Thursday:
>>> Free: +1-888-452-0308
>>> Intl/Toll: +(210) 234-7446
>>> PIN: 71815
>>> See more information:
>>> - https://forge.gridforum.org/sf/go/wiki1477
>>>
>>> Screen share service will be provided.
>>> URL: http://ogsa.glance.net
>>> Session key: 1130
>>> See more explanation:
>>> https://forge.gridforum.org/sf/go/wiki1584
>>
>>
>> The link to the full agenda:
>> http://www.ogf.org/pipermail/ogsa-wg/2006-November/002312.html
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>> Subject:
>> [ogsa-wg] Materials for tomorrows call
>> From:
>> "Andrew Grimshaw" <grimshaw at cs.virginia.edu>
>> Date:
>> Wed, 29 Nov 2006 20:52:24 -0500
>> To:
>> <ogsa-wg at gridforum.org>
>>
>> To:
>> <ogsa-wg at gridforum.org>
>>
>>
>> All,
>>
>> Steve McGough and I were asked to prepare a discussion around workflow
>> for the telecom tomorrow. Attached is a short slide deck and some XML
>> examples – to be explained during the call.
>>
>>
>>
>> I have another meeting in which I am presenting that runs from 7-9 am
>> eastern, so will miss the opening of the OGSA call. If for some reason
>> I am late, Mark can present.
>>
>>
>>
>> A
>>
>>
>>
>> Andrew Grimshaw
>>
>> Professor of Computer Science
>>
>> University of Virginia
>>
>> 434-982-2204
>>
>> grimshaw at cs.virginia.edu
>>
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>> <?xml version="1.0" encoding="UTF-8"?>
>> <wflow:Workflow xmlns="http://schemas.ggf.org/wflow"
>> xmlns:wflow="http://schemas.ggf.org/wflow"
>> xmlns:jsdl="http://schemas.ggf.org/jsdl/2005/11/jsdl"
>> xmlns:xsi="http://www.w3.org/2001/XMLSchemas-instance">
>>
>> <!-- This example is similar to WorkflowExample-1.xml (located at
>>
>> http://www.cs.virginia.edu/~mmm2a/Workflows/WorkflowExample-1.xml).
>> The differences are that we give more then one JSDL template
>> document in this one, the first of which is used to perform some
>> out-of-band initialization. We indicate this by creating an
>> artificial dependency in the second JSDL document called a flow
>> and then referencing that later in a Workflow node.
>> -->
>> <jsdl:JobDescription id="prepare-task">
>> <!-- The job identification element is standard JSDL and not
>> relevant
>> to this example
>> -->
>> <jsdl:JobIdentification>
>> <jsdl:JobName>One Generator</jsdl:JobName>
>> <jsdl:Description>A job which Generates data required for
>> using the fibonacci flow.</jsdl:Description>
>> </jsdl:JobIdentification>
>>
>> <jsdl:Application>
>> <jsdl:ApplicationName>one-generator</jsdl:ApplicationName>
>> <!-- In most cases, this element would have other information
>> inside of it (like a POSIXApplication element or
>> HPCApplication element). We leave it blank here to
>> simplify
>> the example.
>> -->
>> </jsdl:Application>
>> </jsdl:JobDescription>
>>
>> <jsdl:JobDescription id="add-task">
>> <jsdl:JobIdentification>
>> <jsdl:JobName>Adder</jsdl:JobName>
>> <jsdl:Description>A job which takes two input values
>> (integers) and produces an output value which is the sum of the
>> inputs.</jsdl:Description>
>> </jsdl:JobIdentification>
>>
>> <jsdl:Application>
>> <jsdl:ApplicationName>adder</jsdl:ApplicationName>
>> <!-- Here is where we might place elements for the JSDLPosix
>> extension, or the HPC extension, or something else -->
>> </jsdl:Application>
>>
>> <jsdl:DataStaging name="input-1">
>> <jsdl:FileName>input-1.dat</jsdl:FileName>
>> <jsdl:CreationFlag>overwrite</jsdl:CreationFlag>
>> <jsdl:Source/>
>> </jsdl:DataStaging>
>>
>> <jsdl:DataStaging name="input-2">
>> <jsdl:FileName>input-2.dat</jsdl:FileName>
>> <jsdl:CreationFlag>overwrite</jsdl:CreationFlag>
>> <jsdl:Source/>
>> </jsdl:DataStaging>
>>
>> <jsdl:DataStaging name="output">
>> <jsdl:FileName>output.dat</jsdl:FileName>
>> <jsdl:CreationFlag>overwrite</jsdl:CreationFlag>
>> <jsdl:Target/>
>> </jsdl:DataStaging>
>>
>> <wflow:DataStream name="foo">
>> </wflow:DataStream>
>> </jsdl:JobDescription>
>>
>> <wflow:Node id="initializer">
>> <wflow:JSDL jsdl-ref="prepare-task"/>
>> </wflow:Node>
>>
>> <wflow:Node id="fib-2">
>> <wflow:JSDL jsdl-ref="add-task">
>> <wflow:Dependencies>
>> <wflow:Dependency node-ref="initializer"/>
>> </wflow:Dependencies>
>>
>> <wflow:Input data-ref="input-1">
>> <wflow:URI>http://tempuri.org/data/one.dat</wflow:URI>
>> </wflow:Input>
>>
>> <wflow:Input data-ref="input-2">
>> <wflow:URI>http://tempuri.org/data/one.dat</wflow:URI>
>> </wflow:Input>
>> </wflow:JSDL>
>> </wflow:Node>
>>
>> <wflow:Node id="fib-3">
>> <wflow:JSDL jsdl-ref="add-task">
>> <wflow:Dependencies>
>> <wflow:Dependency node-ref="initializer"/>
>> </wflow:Dependencies>
>>
>> <wflow:Input data-ref="input-1">
>> <wflow:URI>http://tempuri.org/data/one.dat</wflow:URI>
>> </wflow:Input>
>>
>> <wflow:Input data-ref="input-2">
>> <wflow:Node node-ref="fib-2">
>> <wflow:Source data-ref="output"/>
>> </wflow:Node>
>> </wflow:Input>
>> </wflow:JSDL>
>> </wflow:Node>
>>
>> <wflow:Node id="fib-4">
>> <wflow:JSDL jsdl-ref="add-task">
>> <wflow:Input data-ref="input-1">
>> <wflow:Node node-ref="fib-2">
>> <wflow:Source data-ref="output"/>
>> </wflow:Node>
>> </wflow:Input>
>>
>> <wflow:Input data-ref="input-2">
>> <wflow:Node node-ref="fib-3">
>> <wflow:Source data-ref="output"/>
>> </wflow:Node>
>> </wflow:Input>
>>
>> <wflow:Output data-ref="output">
>> <wflow:Target>http://tempuri.org/fib-4.dat</wflow:Target>
>> </wflow:Output>
>> </wflow:JSDL>
>> </wflow:Node>
>>
>> <wflow:Flows>
>> <wflow:Flow node-ref="fib-4"/>
>> </wflow:Flows>
>> </wflow:Workflow>
>
--
Andreas Savva
Fujitsu Laboratories Ltd
More information about the jsdl-wg
mailing list