[
https://issues.apache.org/jira/browse/OODT-381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris A. Mattmann updated OODT-381:
-----------------------------------
Description: [~bfoster] built a Runner framework in wengine that we will
port over in this issue. Basically what it allows is a flexible interface for
dispatching WorkflowTasks to resources (compute nodes, clouds, grids, laptops,
etc.) to run on. One runner will allow native integration with the resource
manager, and another runner set will provide both synchronous and asynchronous
local execution. (was: [~bfoster] build a Runner framework in wengine that we
will port over in this issue. Basically what it allows is a flexible interface
for dispatching WorkflowTasks to resources (compute nodes, clouds, grids,
laptops, etc.) to run on. One runner will allow native integration with the
resource manager, and another runner set will provide both synchronous and
asynchronous local execution.)
> Create Runner framework to allow flexible WorkflowTask execution on different
> runtimes
> --------------------------------------------------------------------------------------
>
> Key: OODT-381
> URL: https://issues.apache.org/jira/browse/OODT-381
> Project: OODT
> Issue Type: Sub-task
> Components: workflow manager
> Reporter: Chris A. Mattmann
> Assignee: Chris A. Mattmann
> Labels: integration, oodt, runner, wengine, workflow2
> Fix For: 0.5
>
>
> [~bfoster] built a Runner framework in wengine that we will port over in this
> issue. Basically what it allows is a flexible interface for dispatching
> WorkflowTasks to resources (compute nodes, clouds, grids, laptops, etc.) to
> run on. One runner will allow native integration with the resource manager,
> and another runner set will provide both synchronous and asynchronous local
> execution.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira